HP3000-L Archives

November 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
Date:
Fri, 17 Nov 2000 13:07:44 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
I was skeptical earlier when Greg Stigers wrote that ESCAPE will not force an
abort if HPAUTOCONT is TRUE. I tested it, and Greg is correct.

Isn't this counter intuitive? I have job with, say, 7 steps. If any of them
terminates abnormally, I want to take some action and perhaps/probably abort the
job. Instead of tediously coding CONTINUE before each step, I code SETVAR
HPAUTOCONT TRUE at the top of the job. However, if step 3 is crucial and it
fails, I want to ESCAPE. But escape will not do that. When I code ESCAPE, I mean
it!

However, ESCAPE will force an abort if the offending command is preceded by
CONTINUE.

===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431

ATOM RSS1 RSS2