Thanks Just tried sysstate macro with amode64=yes and read gave me a mnote that I couldn’t do it the buffer is 64 bits but I switch before doing the read the SF64 code expands to do a STG for the register I had for the I/O area
> On Nov 17, 2019, at 2:03 AM, Greg Price <[email protected]> wrote: > > On 2019-11-17 5:40 PM, Joseph Reichman wrote: >> I normally do all I/O in amode 24 because of the EODAD of AL3 the open >> having an AL3 for the DCB > > Unless you have an old ESA or even older XA system, there's no need to do I/O > in amode24 these days. Just use amode31. > > The AL3 pointers will restrict you to rmode24, but that's a different story. > > If the only DCB exits you use are EODAD and/or SYNAD, and you want to go > rmode31 (or rmodeany if you prefer) then you can supply their 4-byte address > in the DCBE macro. But you do not need 4-byte pointers to them to use > amode31. > > About the only amode24 code for z/OS I write these days is for exits where > only amode24 is supported. DCB exits pointed to by DCBEXLST may be in this > boat, as are the SYSIN and SYSPRINT (and other DD ??) exits used for > supplying data to and consuming data from calls to the IDCAMS program. > > Sometimes in rmode31 programs I GETMAIN BTL storage and load the code for DCB > exits, but this technique is not required for EODAD and SYNAD exits due to > their DCBE support. > > Cheers, > Greg > > ---------------------------------------------------------------------- > 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
