home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!linac!att!ucbvax!HOPE.CIT.HOPE.EDU!BAREMAN
- From: BAREMAN@HOPE.CIT.HOPE.EDU ("Steven L. Bareman")
- Newsgroups: comp.os.vms
- Subject: DCL: ? Continuing execution after -?- severity message.
- Message-ID: <01GTTGNJRFXC00114F@HOPE.CIT.HOPE.EDU>
- Date: 22 Jan 93 16:41:00 GMT
- Sender: usenet@ucbvax.BERKELEY.EDU
- Organization: The Internet
- Lines: 25
-
- Dear DCL-users,
-
- What commands to I need to use to insure that a command
- procedure doesn't quit running after any warning/error conditions?
-
- 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
-
- I thought that would cover them all but the procedure terminated
- prematurely after starting (and completing?) a backup recording pass.
-
- Do I need to have "ON" traps for each severity level, or should
- just the highest one catch it?
-
- Please respond directly to me since I am not subscribed to this list.
-
- Thank you,
-
- Steve Bareman
- BAREMAN@HOPE.CIT.HOPE.EDU
-
-
-