See https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad400/bam12plan.htm and https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad400/bam12appl.htm.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Charles Mills <charl...@mcn.org> Sent: Monday, July 29, 2019 3:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: XTIOT impact? The recent discussion here of TIOT lookup failing prompted me to inventory my code. I hear you all on GETDSAB but I have working code written in C++ that scans the TIOT, and it would be a lot less impact to resolve any problems there rather than calling out to a new GETDSAB routine. The existing code goes PSATOLD to TCBTIO to TIOT and scans looking for particular DD names. It only cares about DD exists or does not exist and a couple of flags; it does not chain to the JFCB. (Yeah, I know about SWA's.) What *exactly* is the difference/impact of an XTIOT? It looks to me like an XTIOT is just a regular TIOT but above the line. Is that right? If my code always runs AMODE 31 and makes no assumptions about the high-order bits of any pointers, will it be adversely impacted by an XTIOT? Thanks, Charles ---------------------------------------------------------------------- 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
