Those are not the messages I would like to see 1) Provide the APPLY Statement in full. 2) Provide all messages from the APPLY Function from SMOUT DD statement
This will help us see what the issues might be. Sometimes when you do an APPLY it is for the incorrect FMID or the wrong SREL. We would like to see something like this . APPLY . GROUP . PTFS . BYPASS ( . HOLDSYSTEM . ) . NOJCLINREPORT . RETRY ( YES ) . . . .GIM42001I THE FOLLOWING CONDITIONS FOR SYSMOD UI68880 WERE NOT SATISFIED, BUT . WERE IGNORED BECAUSE THE BYPASS OPERAND WAS SPECIFIED. PROCESSING . CONTINUES. .GIM35966I SYSTEM HOLD ACTION ORIGINATED BY SYSMOD UI68880 WAS BYPASSED. .GIM35966I SYSTEM HOLD DOC ORIGINATED BY SYSMOD UI68880 WAS BYPASSED. .GIM42001I THE FOLLOWING CONDITIONS FOR SYSMOD UI68931 WERE NOT SATISFIED, BUT . WERE IGNORED BECAUSE THE BYPASS OPERAND WAS SPECIFIED. PROCESSING . CONTINUES. Liette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Bill Giannelli Sent: Thursday, June 11, 2020 10:27 AM To: [email protected] Subject: Re: SMPe Apply not working GIM59603I ENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS1 FOR GIM59603I ENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS2 FOR GIM24801S ** NO SYSMODS SATISFIED THE OPERANDS SPECIFIED ON THE APPLY COMMAND. GIM59606I DEQ WAS SUCCESSFUL FOR EXCLUSIVE USE OF OEMPP.DB2.V12R02M0.GLOBAL.C GIM59607I DEQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS FOR ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
