Thank you Peter, I will check installation LE options and set up new ones including TRAP(OFF,NOSPIE) before running the script again if needed.
Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Relson Sent: Monday, July 17, 2023 2:14 PM To: [email protected] Subject: Re: How to set a SLIP to catch S0C4 in OMVS separate AS <snip> SLIP SET,ID=PJF1,JOBNAME=Z02446*,COMP=0C4,ACTION=SVCD,AL=(H,P,S),SDATA=(ALLNUC,PSA,RGN,LPA,CSA,SQA,TRT,GRSQ,SUM),END </snip> As far as I know, the jobname for a fork-child is related to the jobname for a fork-parent (appending ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd <snip> SLIP SET,ID=PJF1,JOBNAME=Z02446*,COMP=0C4,ACTION=SVCD,AL=(H,P,S),SDATA=(ALLNUC,PSA,RGN,LPA,CSA,SQA,TRT,GRSQ,SUM),END </snip> As far as I know, the jobname for a fork-child is related to the jobname for a fork-parent (appending a single digit unless the original name was 8 characters, or something like that). I know nothing about the environment of the OP, but in a vanilla job that happened to be jobname "RUNJOB" that invokes "Fork", the fork child jobname was "RUNJOB1", and a SLIP trap with JOBNAME=RUNJOB* for a program check in the child matched as expected. Given the trap shown above, either an 0C4 did not happen, or the only 0C4's happened when running not under a job with the first six characters of Z02446 (or, as Jim Mulder reminded me, LE has been told to use ESPIE for recovery and LE has handled this 0C4 and has not given it to RTM to process - the application configuration can define whether or not to use this, I believe). None of the other SLIP traps are "filtering" so none would affect if the trap would hit or not. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
