Routine only uses the TIOT entry to see if DD is present. It does that to avoid OPEN message of missing DD.
-----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Seymour J Metz Sent: Wednesday, July 24, 2019 1:15 PM To: [email protected] Subject: Re: old code failing There are hangs to the TIOT in support of SWA above the line, and later changes in support of XTIOT. Do GETDSAB and RDJFCB with an ARL give you all the data you need, or do you actually need the TIOT entry itself? You should not use the TIOT to load the JFCB address into a register; use system services. Even if your SWA is still below the line, you don't want your code to break when you move it above. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&d=DwIFAw&c=Z4P52L0foFKAY1wcP-GmiQ&r=gPyXKYfguTF6KSwWL0MXilwlmRSg_lRVheZFw_2X3Uw&m=jqVGzuz4Q3wbyPPOsgs3PMcHhqiB5cgIMie4AVXVuPU&s=E-q0y2ZFAQxFgXU8s1fx-AdO7qnsqYOSdCZRO9Gsk8E&e= ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Richard Kuebbing <[email protected]> Sent: Wednesday, July 24, 2019 11:23 AM To: [email protected] Subject: old code failing A subroutine written long ago appears to be failing. It looks for a DDname in the TIOT. Did the format of the TIOT change at some point? If yes, at what release? Does it matter if AMODE is 24 or 31? It might have something to do with the fact that the DD is a proc override instead of straight JCL or in a proc. Richard Kuebbing NOTICE: This communication is intended only for the person or entity to whom it is addressed and may contain confidential, proprietary, and/or privileged material. Unless you are the intended addressee, any review, reliance, dissemination, distribution, copying or use whatsoever of this communication is strictly prohibited. If you received this in error, please reply immediately and delete the material from all computers. Email sent through the Internet is not secure. Do not use email to send us confidential information such as credit card numbers, PIN numbers, passwords, Social Security Numbers, Account numbers, or other important and confidential information. NOTICE: This communication is intended only for the person or entity to whom it is addressed and may contain confidential, proprietary, and/or privileged material. Unless you are the intended addressee, any review, reliance, dissemination, distribution, copying or use whatsoever of this communication is strictly prohibited. If you received this in error, please reply immediately and delete the material from all computers. Email sent through the Internet is not secure. Do not use email to send us confidential information such as credit card numbers, PIN numbers, passwords, Social Security Numbers, Account numbers, or other important and confidential information.
