Earlier I wrote:
 
> ESCAPE returns control to the statement after an active CONTINUE.  
> If there is not an active CONTINUE then jobs are terminated and 
> sessions stay alive. The CIERR and HPCIERR variables can be set by 
> ESCAPE too.
...
> I don't believe any of the above commands will cause an abnormal 
> termination.

Greg wrote to tell me that a job which escapes is selected by LISTSPF
... [jobabort=true]. I checked the CI code (which I wrote long ago) and
he is right.

Here's my reply to Greg:

An ESCAPE not "protected" by a CONTINUE in a job will flush the job.
This includes printing a "job flushed" message to $stdlist and setting
JCW to %100000 which informs the spooler that the job was aborted.

Thanks,
 Jeff

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