Caveat: Moved on to other products, so it's been a few years since I was a db2 sysprog so I may just being dense.
It isn't clear what "damage" you're trying to reverse, or perhaps I don't understand what obsolete means in this context. Why would the SMP/E defined SDNSEXIT dsn be classified on an APPLLY as missing or obsolete in your current CSI? If you ran step DSNTIMQ and it found a DSN to put the member in, why is it obsolete? tom -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of David Booher Sent: Wednesday, September 14, 2011 10:34 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Question for SMP/E gurus with DB2 knowledge Yes, on my new DB2 installs, I simply omit the step from DSNTIJUZ, but once it's run, the damage is done. You pin-pointed my problem on older systems, the APPLY CHECK works fine, but when you actually run the APPLY, it can fail because of a reference to an obsolete SDSNEXIT library. Your suggestion is worth a try. Unfortunately, once the damage is done to SMP, it's hard to reverse it. Thanks, Dave ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
