Leonard S. Berkowitz wrote:
> Over the weekend we restored a set of production files to two
> different test accounts. The jobs are the same, just differ by the
> logon account.
>
> Our jobs check the JCWs set by BackPack to determine whether
> everything was restored satisfactorily. If not the job is supposed to
> abend via the ESCAPE command. It turns out that one of the data bases
> to be restored was not on the tape.

> The second job found the condition to be TRUE, but did not abend. Can
> anyone tell me why?

Hmmmm, an inconcludable escape.......

HELP ESCAPE OPERATION

tells me:

    The ESCAPE command causes control to leave all user commands
     (regardless of nesting levels) and return to the CI. Batch jobs
     terminate and sessions issue the prompt.

     If no CONTINUE is active, ESCAPE causes the CI to act as it would
     for any error.  For sessions the user command environment is
     cleared and the prompt is displayed.  For jobs the process is
     terminated.

     If CONTINUE is active, then ESCAPE causes the CI to execute
     the second command after the CONTINUE.

So the inescapable conclusion is that you had a CONTINUE in force when you
ran the second job, and not when you ran the first one.

As the jobs were the same, this was probably an HPCONTINUE set on the
Account UDC of the account for the second job.

--
Roy Brown

Posting with the OEnemy, tamed by OE-QuoteFix
http://jump.to/oe-quotefix

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *