Bruce, You bring up many of the limitations of IEBUPDTE, which leads to another option. Stop using IEBUPDTE and go to full ++SRC for user exits. This means the sample is the entire exit with comment blocks were we suggest you place your user-code. The downside is that if we (the vendor) change the entry/exit processing or the parsing of the input parameter list for some reason, the entire source is changed and you need to re-incorporate your changes manually.
And should these user-exits be SMP controlled to begin with? Or should we simply give sample assemble/linkedit JCL along with the source and let the end user control their own destiny? The downside is that it might not always be obvious to new sysprog's which exit(s) are actually installed and active or where the source is for the active and installed exits. At least with SMP you know which usermod was last applied; which should give you the last set of updates or source for the exit. Russell Witt CA-1 Level-2 Support Manager -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Bruce Hewson Sent: Thursday, June 14, 2007 2:50 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SMP/E, IEBUPDTE, and SuperC (was: CA-1 install - user exits?) ...<snip>... ++SRCUPD and ++MACUPD via IEPUPDTE is only usable when the original data is supplied with line numbers that are "guaranteed" never to be changed. Regards Bruce Hewson ---------------------------------------------------------------------- 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
