Old code in JES Exit 6
The following code has been in our JES2 exit 6 since before I started (so like maybe 40 years :) ?). The intent is to cause jobs with special forms to print on ordinary paper when their JCL fails. With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. SIS and Google for JPCEIOT is not helpful. It's probably no longer an issue due to less forms, less actual printing and less failures. Still, I'd like to fix it instead of just whacking the code. Any JES knowledge out there to help me :) ENDJCL DS0H L R2,X6CTRC Address of Convertor's RC L R2,0(R2)Convertor's RC C R2,=A(JCTCOK) Check Convertor's RC JECONVOK Ok now make our checks BRASL R3,SETSTD Failed so force to STD forms J RETURN And get out .. * * FORCE OUTPUT TO STANDARD * SETSTD DS0H L R1,X6DTEADR ADDRESS OF DTE USING DTE,R1 L R1,DTEPCE ADDRESS OF PCE USING PCE,R1 LTR R1,R1 IS THE PCE THERE ? BZR R3skip L R2,JPCEIOT GET ADDRESS OF 1ST IOT DROP R1 ALR2,$IOTPDDB OF 1ST PDDB MVC PDBFORMS,$STDFORMLOG AHR2,PDBSIZE ADVANCE TO SECOND PDDB MVC PDBFORMS,$STDFORMIMAGES AHR2,PDBSIZE ADVANCE TO THIRD PDDB MVC PDBFORMS,$STDFORMMESSAGES DROP R2 BRR3 * DROP R9,R10,R12 Dave Gibney Information Technology Services Washington State University -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
On 2/11/2016 2:42 PM, Gibney, David Allen,Jr wrote: With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. Ugh! There is no record whatsoever in the macro prolog of this field being removed. There are, however, two change IDs of folks that might have been responsible for doing so: $Z21LCLS=CLASS8 HJE7790 27 SJS: 8 character jobclass $Z21LCNV=JES2CI HJE7790 121115 TJW: Back to back C/I The last one I recognize as Tom Wasik -- frequent SHARE presenter and sometime contributor to this list. He is more likely to be found on JES2-L though, so you might want to redirect your query there. Or you could email him directly at wa...@us.ibm.com. HTH -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
Thanks Ed. I cross-posted, but did not say so to JES2-L I remember Tom from the last time I made it to SHARE. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Thursday, February 11, 2016 4:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Old code in JES Exit 6 > > On 2/11/2016 2:42 PM, Gibney, David Allen,Jr wrote: > > With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. > > Ugh! There is no record whatsoever in the macro prolog of this field being > removed. There are, however, two change IDs of folks that might have been > responsible for doing so: > > $Z21LCLS=CLASS8 HJE7790 27 SJS: 8 character jobclass > $Z21LCNV=JES2CI HJE7790 121115 TJW: Back to back C/I > > The last one I recognize as Tom Wasik -- frequent SHARE presenter and > sometime contributor to this list. He is more likely to be found on JES2-L > though, so you might want to redirect your query there. Or you could email > him directly at wa...@us.ibm.com. > > HTH > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.phoenixsoftware.com_&d=CwICaQ&c=C3yme8gMkxg_ihJNXS06Zy > Wk4EJm8LdrrvxQb- > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=cqlGWuRT7eb6ZnFKh- > MYeMh5pvBZAfOdyHi4tu6- > jKI&s=2H3C48zFxp8RDKg9AfqAq2cgcKSZA37rwf5TbQ44cC8&e= > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
Ed Jaffe wrote: > Gibney, David Allen,Jr wrote: > > With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. > Ugh! There is no record whatsoever in the macro prolog of this field being > removed. There are, however, two change IDs of folks that might have been > responsible for doing so: > $Z21LCLS=CLASS8 HJE7790 27 SJS: 8 character jobclass > $Z21LCNV=JES2CI HJE7790 121115 TJW: Back to back C/I I have seen that. Is this because JPCECLAS and JPCEPRIO and 'reserved for future use' fields increased in size? Perhaps something else also changed too? I have also looked around and checked if JPCEIOT has been moved/renamed to somewhere else, but found nothing... Migration to z/OS v2.1 books does not give me hints. Yes, I have reviewed the very latest migration guide. Searches on IBM.com gave me nothing. Perhaps I used wrong search arguments? Perhaps it is time to submit a formal note to IBM to resolve that exit code problem? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
>The following code has been in our JES2 exit 6 since before I started (so like >maybe 40 years :) ?). The intent is to cause jobs with special forms to print >on ordinary paper when their JCL fails. > >With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. Dave, It looks as if many of the fields have been move to two new local work areas, CIWORK / CIWORKB. There's some comment in: http://publibz.boulder.ibm.com/epubs/pdf/has2r900.pdf (See Chapter 73) And the data areas books shows, for example, 372 (174) ADDRESS 4 CIWIOTAddress of allocation IOT Geoff Rousell IBM SE (not a JES2 expert, but found some internal comment...) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
You have some code to write. Look at "z/OS MVS Using the Functional Subsystem Interface" SA38-0678-00 (for z/OS 2.1) More and more of the stuff that used to be in JES CB's is being moved to the FSS(SAPI) and can only be obtained via this method. It is not too difficult to write, but the trick will be integrating it with your existing exit code. HTH and Good luck! The following code has been in our JES2 exit 6 since before I started (so like maybe 40 years :) ?). The intent is to cause jobs with special forms to print on ordinary paper when their JCL fails. With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. SIS and Google for JPCEIOT is not helpful. It's probably no longer an issue due to less forms, less actual printing and less failures. Still, I'd like to fix it instead of just whacking the code. Any JES knowledge out there to help me :) ...remainder snipped This email including attachments may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
On 2/12/2016 5:55 AM, Staller, Allan wrote: You have some code to write. Look at "z/OS MVS Using the Functional Subsystem Interface" SA38-0678-00 (for z/OS 2.1) More and more of the stuff that used to be in JES CB's is being moved to the FSS(SAPI) and can only be obtained via this method. It is not too difficult to write, but the trick will be integrating it with your existing exit code. The SSI cannot be used to access the needed work areas from within exit 6. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Geoff Rousell > Sent: Friday, February 12, 2016 2:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Old code in JES Exit 6 > > > >The following code has been in our JES2 exit 6 since before I started (so > >like > maybe 40 years :) ?). The intent is to cause jobs with special forms to print > on > ordinary paper when their JCL fails. > > > >With z/OS 2.1, the field JPCEIOT is no longer in $CNVWORK. > > > Dave, > > It looks as if many of the fields have been move to two new local work areas, > CIWORK / CIWORKB. > > There's some comment in: > > https://urldefense.proofpoint.com/v2/url?u=http- > 3A__publibz.boulder.ibm.com_epubs_pdf_has2r900.pdf&d=CwIFaQ&c=C3ym > e8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb- > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=s0N5wx2BcHnh0uTa5W9IOvznFNxn > 0x6KnOdmJfipkSo&s=TxRV0hx29UiLf2pAHV8PE_5BRiJUaffUm-VykpAJZZc&e= > (See Chapter 73) Thanks Russell, there is a lot of info in that chapter. Now I am disappointed that this (Check out your JES Exits) didn't get at least a passing mention in the z/OS Migration book. Like in the chapter JES2 actions to preform before the first IPL of z/OS V2R1. Still, I guess I should have known and looked myself. Or insisted on a SHARE trip :) I need to more closely evaluate all our exits. (01,02,03,04,05,20,46,47,50,52,53,54,56,57). Fortunately, it can't be as big a deal as when I had to add the 5x series, as there was more IBM-MAIN buzz about that back then > > And the data areas books shows, for example, > > > 372 (174) ADDRESS 4 CIWIOTAddress of > allocation IOT > > Geoff Rousell > IBM SE (not a JES2 expert, but found some internal comment...) > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Old code in JES Exit 6
Just an observation that historically JES2 (and maybe JES3) have meticulously accompanied control block changes with macro label changes. For example, if a field changes from halfword to fullword, then the name is changed as well. The resulting user mod/exit assembly error is a huge red flag that customer code has to change. Somehow. Nothing is/would be worse than trying to debug errors resulting from unmarked control block changes. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ed Jaffe > Sent: Friday, February 12, 2016 08:20 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Old code in JES Exit 6 > > On 2/12/2016 5:55 AM, Staller, Allan wrote: > > You have some code to write. > > Look at "z/OS MVS Using the Functional Subsystem Interface" > > SA38-0678-00 (for z/OS 2.1) > > > > More and more of the stuff that used to be in JES CB's is being moved to the > FSS(SAPI) and can only be obtained via this method. > > > > It is not too difficult to write, but the trick will be integrating it with > > your > existing exit code. > > The SSI cannot be used to access the needed work areas from within exit 6. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
