home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!pacbell.com!ames!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: command procedure calling
- Date: 28 Jan 1993 01:48:29 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 27
- Message-ID: <1k7e1dINNn40@gap.caltech.edu>
- References: <1k4p20INNjbq@gap.caltech.edu>,<160@mccoy.dbaccess.com>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- >: Well, you *COULD* execute the command:
- >: $ MCR DCL
- >: (don't do this; it deletes your process, but it does *NOT* return to the
- >: calling procedure :-).
- >
- >Eh?
-
- Well, it accomplishes the stated goal of not returning to the DCL procedure
- that called the procedure that issues the MCR DCL command. Of course, it does
- so by deleting the entire process.
-
- >You could execute the STOP command (quits all command procedures. The
- >job too, if you're in batch...but then, that makes sense).
-
- Yup. I missed that one. The "HINTS Command_procedures" section of the on-line
- help mentions the EXIT command, but not the STOP command. It would be nice if
- DEC would add a "Related_topics" item to some of their HELP entries. The only
- aspect in which I think UNIX's man pages are better than VMS's HELP utility is
- in that they've frequently got a "See also: " section at the end.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-