There is some relief for that particular problem now Andy in case you had not already seen it.
http://www.redbooks.ibm.com/abstracts/tips0531.html?Open You can now split the SMSPDSE address space into a non-restartable one which supports LNKLST and a restartable one which supports everything else. Best Regards, Sam Knutson, GEICO Performance and Availability Management mailto:[EMAIL PROTECTED] (office) 301.986.3574 Agnes' Law: Almost everything in life is easier to get into than out of. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Andy Corpes Sent: Friday, September 09, 2005 11:58 AM To: [email protected] Subject: Re: Possible problem with PDSE's Thanks for all of your replies, very useful, i think i can now show to my employee i was not being too irresponsible by defining our 2000 + source/object/load/JCL libraries as PDSE's, some of you may remember, i asked similar questions 2-3 years ago, when i started this work. In the past two years, we have had 2 problems such as this,, but only the most recent forced us to IPL,, the reason stated was that SMSPDSE STC could not be stop/started As to how such a sweeping conclusion (PDSE's unstable) was arrived at? I really don't know, i think someone read it somewhere and thought it sounded knowledgeable,, thankfully, this list exists where the truth can be found out. Thanks to everyone again., Andy (070 340 4569) <> ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- 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
