Once you get the coding correct, any R15 value not zero from DEVTYPE can be treated as "DD not found". Simplest solution and solid as a rock to use.
HTH Peter -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Richard Kuebbing Sent: Wednesday, July 24, 2019 1:25 PM To: [email protected] Subject: Re: old code failing I read DEVTYPE doc looking for rc meaning "not found" and did not see it. -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Mike Shaw Sent: Wednesday, July 24, 2019 11:49 AM To: [email protected] Subject: Re: old code failing The DEVTYPE macro is a much safer and simpler way to check for the presence of a DD. The old TIOT scan method may work and it may not work. Mike Shaw MVS/QuickRef Support Group Chicago-Soft, Ltd. On Wed, Jul 24, 2019 at 11:24 AM Richard Kuebbing <[email protected]> wrote: > 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. > -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
