Re: CEE4ABN

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

----- Original Message -----
From: "Leif Svalgaard" <leif@leif.org>
To: <midrange-l@midrange.com>

> Anyone of the programs might discover a fatal error
> and decide to quit altogether. One way is to return
> with a return-code that says 'fatal error'; the caller
> checks that and returns with 'fatal error', etc all the
> way up to A that returns and the job ends (if in batch).
>
> All this checking is cumbersome, so I'm looking for
> a shortcut that ends the job immediately, like CEE4ABN.
>

Leif,

Your job starts from a main cl pgm, call it "MAINCL".  This cl pgm calls
your PgmA, which calls PgmB, PgmC and PgmD.

PgmC discovers the fatal error. In PgmC, call cl pgm LEIF4ABN with 2 parms:
ErrorMsg, NameOfMainCl.

LEIF4ABN is coded as such:

PGM  ( &ErrMsg &MainPgmNam )
DCL &ErrMsg *char 80
DCL &MainPgmNam *char 10

SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA(&ErrMsg')   TOPGMQ(*SAME
(&MainPgmNam)) MSGTYPE(*ESCAPE)

EndPgm

Your main cl pgm has a global monitor for CPF9898 like so:
MONMSG MsgId(CPF9898) Exec( GoTo PgmAbnEnd)

When LEIF4ABN sends the *Escape message to the MainCl pgm, all the pgms in
the call stack above the target pgm are ended automatically.  ( This is one
of the many incredibly  well thought out features built into the System38 by
its long gone genius creators. )

You can even send the *Escape msg to *PRV of MainCL.  This will end all the
pgms including MainCl. The receiving pgm in this case will be QCMD. When it
receives an *Escape message, it ends the job and send the "job ended
abnormally" msg to user who submitted the job.

Another variable could be to send the *Escape message direct to QCMD.  This
removes any special coding from MainCl. Only side affect:  You will get the
"job ended abnormally" msg when maybe you are doing more of a controlled end
that you want MainCl to handle in a customized way.

hth,

Steve Richter