home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!agate!ucbvax!TGV.COM!mcmahon
- From: mcmahon@TGV.COM (Midnight at U Street Metro Station)
- Newsgroups: comp.os.vms
- Subject: Re: DCL: ? Continuing execution after -?- severity message.
- Message-ID: <930123170035.44a00553@code-z.tgv.com>
- Date: 24 Jan 93 01:00:35 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 32
-
- In article <01GTTGNJRFXC00114F@HOPE.CIT.HOPE.EDU> you write:
- =>What commands to I need to use to insure that a command
- =>procedure doesn't quit running after any warning/error conditions?
-
- $ SET NOON
-
- =>I have a procedure which must run to completion even if one of
- =>the commands generates a warning/error condition and at the
- =>beginning I have:
- =>
- =>$ ON SEVERE_ERROR THEN CONTINUE
-
- This sets up a handler for severe errors only. What you want
- is one to handle all conditions. For that, use the lowest
- catagory ON WARNING.
-
- You second problem with using ON SEVERE is that once the handler fires,
- it's no longer in effect. The result is the second error will cause
- the procedure to exit, unless you execute another ON statement.
-
- For your purposes, SET NOON will cover you. See HELP ON and
- HELP SET ON for details.
-
- --
- John 'Fast-Eddie' McMahon ()
- TGV, Incorporated () "Any networking problem can be solved by
- 603 Mission Street () the application of 33 miles of Unshielded
- Santa Cruz, California 95060 () Twisted Pair (UTP)"
- 408-427-4366 or 800-TGV-3440 () [InterOp Spring 1992]
- E-Mail: MCMAHON@TGV.COM ()
-
-
-