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 firstname.lastname@example.org.
ENDJOBABN is not a good idea, in this case for two reasons:
1) The OP said that this is an interactive job that shouldn't be
cancelled; only the current (and/or previous) program.
2) IIRC, ENDJOBABN can negatively affect the application of PTF's during
the next IPL (I don't recall the exact details of those rules), so it
shouldn't be used unless there's a stubborn job that's not getting
cancelled via the ENDJOB command.
Just a clarification re CPF9898/CPF9897, it's not the message ID that
ends the message, rather the value in the MSGTYPE() parm of the sender.
On 1/9/2023 1:35 PM, dfreinkel@xxxxxxxxxxxxxxxxx wrote:
This needs confirming but if you send a message with message ID CPF9898 or CPF9897, one of those will end the job abnormal.
You could also issue the CL command ENDJOBABN - end job abnormal.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.