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
