× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2018

Trying to force a job to abend

I am trying to force a job to abend but I am apparently overlooking
something.



I created message ERR9999 in MYMSGF with a severity of 99.



&MSGDTA = 'This job just will not abend'



Here is the SNDPGMMSG in my CLLE.

SNDPGMMSG MSGID(ERR9999) MSGF(MYMSGF) +

MSGDTA(&MSGDTA) MSGTYPE(*ESCAPE)





The joblog shows the error I am sending and then and end code of 0 which
says completed normally.

ERR9999 Escape 99 07/19/18 16:56:37.380742 MYMOD
JSMITH *STMT QCMD QSYS 01C8

From module . . . . . . . . : MYMOD


From procedure . . . . . . : MYMOD


Statement . . . . . . . . . : 3600


Message . . . . : This job just will
not abend.

CPF1164 Completion 00 07/19/18 16:56:37.408791 QWTMCEOJ
QSYS 014A *EXT *N

Message . . . . : Job
102144/JSMITH/ABEND ended on 07/19/18 at 16:56:37;

.027 seconds used; end code 0 .




Shouldn't sending a *ESCAPE with a severity 99 cause at least and end code
of 20? What am I missing?


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.