Use the ESCAPE command:

DEV:HELP ESCAPE OPERATION
OPERATION

     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.

<snip>

Before the ESCAPE command, under the aegis of your IF...END that tests various JCWs
and CIERRORs, you can

     SHOWVAR HPCIERR
     SHOWVAR HPCIERRMSG

If you are using, e. g., Maestro, ESCAPE will make the job look as is the job
terminated abnormally and a job dependent on the successful completion of the first
job will have to wait or be release manually.

If you do not want the job to appear to terminate abnormally, you can just put EOJ
into the IF....ENDIF section.

In either case, you can execute lots of stuff if the condition for which you test is
true and before the ESCAPE or early EOJ.

I would also recommend clear messages for the operators and some training or
instructions so that they can distinguish among the various kinds of errors:
programmatic, data base, etc. and call the correct working stiff in the middle of the
night.

If you really want to get fancy, you can purchase beeper software and beep the proper
person depending on what kind of error you encounter.
========================
Leonard S. Berkowitz
mailto:[log in to unmask]
phone: (617) 972-9400 ext. 3250
fax:   (617) 923-5555