home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!mimbres.cs.unm.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!jsue
- From: jsue@ncsa.uiuc.edu (Jeffrey L. Sue)
- Newsgroups: comp.os.vms
- Subject: Re: command procedure calling
- Message-ID: <C1IvCE.H1x@news.cso.uiuc.edu>
- Date: 27 Jan 93 17:02:37 GMT
- Article-I.D.: news.C1IvCE.H1x
- References: <ERMIMWEI.20@er.ele.tue.nl?> <1k4p20INNjbq@gap.caltech.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: The Dow Chemical Company
- Lines: 17
- Originator: jsue@troon.ncsa.uiuc.edu
-
-
- |> In article <ERMIMWEI.20@er.ele.tue.nl?>, ERMIMWEI@er.ele.tue.nl (Wim Beckers) writes:
- |> >When a command procedure is called by another command procedure their is
- |> >always a return to the calling command procedure.
- |> >Is there a possibility to NOT return to the calling procedure?
- |>
-
- Hmm...
-
- I've always used the $STOP command to completely exit a DCL procedure.
- Something like ON CONTROL_Y THEN STOP has proven useful in many
- different applications.
-
- --
- -----
- Jeff Sue
- - All opinions are mine - (and you can't have any, nya nya nya)
-