home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!ukma!asuvax!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!news.service.uci.edu!unogate!mvb.saic.com!macro32
- From: DWING@UH01.Colorado.EDU (would rather be skiing ...)
- Newsgroups: vmsnet.internals
- Subject: Re: idle terminal...
- Message-ID: <01GQR8UAHE3M00JZ53@VAXF.COLORADO.EDU>
- Date: 4 Nov 92 21:20:19 GMT
- Organization: Macro32<==>Vmsnet.Internals Gateway
- Lines: 25
- X-Gateway-Source-Info: Mailing List
-
- Bob George, BOB@AENEAS.IMS.DISA.MIL, wrote, in part:
-
- >The $FORCEX just terminates any image that you have running and returns
- >control to DCL. That wouldn't have any effect on the nodelete bit, would
- >it? Then the $DELPRC does check the nodelete bit (and other things) before
- >it trys to kill the process.
-
- You are right that your process wouldn't be deleted, but if someone does a
- $FORCEX to your process, whatever image you were running (lets say, an
- editor) will go through its regular run-down. If the run-down doesn't include
- saving the edited file, you (could have) lost everything. I say 'could have'
- because it may have a .JOU file or some sort of auto-save function that will
- allow you to recover.
-
- >Yes, but operations at one of the sites that I support has a nasty habit of
- >stopping users' processes when they are running backups. I set the nodelete
- >bit on that system and then they suspended my process. Does wonders when
- >you're a large FTP or DECnet transfer or stepping through a large program
- >that someone's having trouble with.
-
- Sweet (add appropriate sarcastic inflections towards the operators at the
- site).
-
- -Dan Wing, dwing@uh01.colorado.edu or wing_d@ucolmcc.bitnet (DGW11)
- Systems Programmer, University Hospital, Denver
-