> What do you mean about the "companion non-exit code"? You can't "do much" in the exit code itself because the code path has to be short, and various exits impose constraints like "no SVCs." So there has to be a companion piece of code that "does the slow stuff" (writes to a file, etc.) based on work received from the exit code itself.
There may also be initialization code, parameter file scanning code, etc., all of which cannot be in the exit code itself. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Miklos Szigetvari Sent: Monday, July 19, 2010 7:04 AM To: [email protected] Subject: Re: Best practices for SMF exit routines > - What's the best way for the IEFU8x code to pass messages to its companion > non-exit code? The current code uses GETMAIN SP=241, CS, and an x-memory > POST. It looks pretty good to me but is there a more recommended way? > > What do you mean about the "companion non-exit code " ? ---------------------------------------------------------------------- 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
