Thanks for the comments. I have only a few months before I retire after more than 50 yrs doing ASM.
I found part of the problem. I was testing out of a library that caused a test version (from 2011) of my subroutine to be used. It works. The production version (from 2005) does not. The difference revolves around an AMODE ANY statement. So it looks like I have to tiptoe around a code change I don't own. -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Christopher Y. Blaicher Sent: Wednesday, July 24, 2019 11:45 AM To: [email protected] Subject: Re: old code failing Maybe the system put the TIOT entry in the extended TIOT. Look up EXTRACT and GETDSAB macros. Chris Blaicher Technical Architect Syncsort, Inc. -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of retired mainframer Sent: Wednesday, July 24, 2019 11:42 AM To: MVS List Server 2 <[email protected]> Subject: Re: old code failing Can you show us the code that does the looking? > -----Original Message----- > From: IBM Mainframe Assembler List <[email protected]> > On Behalf Of Richard Kuebbing > Sent: Wednesday, July 24, 2019 8:24 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. 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.
