Consider that I have a program running in private storage which issues a GETMAIN to acquire working storage. The GETMAIN is unsuccessful. I now wish to issue a WTO to the console to inform the system operator of the condition and to supply diagnostic information (return code, reason code).
In a reentrant situation, I would copy the WTO PLIST to working storage, insert the substitution data, and then issue a WTO MF=(E,plist). However, I have no working storage. In this case, I am left with no choice but to modify the real PLIST, which is not a problem since I am running in private storage, and the CSECT has no requirement to be reentrant. John P Baker Software Engineer -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Edward Jaffe Sent: Saturday, October 21, 2006 10:59 To: [email protected] Subject: Re: Is the teaching of non-reentrant HLASM coding practices ever defensible? John P Baker wrote: > I always -try- to write reentrant code. However, I sometimes find > that a non-reentrant coding technique is a more suitable approach. > Could you please describe such a situation? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
