Saw this at a shop once. First thing most everyone did was to discard the 'required' set and build their own. That amounted to a noticeable load on the catalogs and some serious cycles consumed in deallocation and allocation. Logons took a -long- time.
Also saw a 'bare bones' TSO that was just enough to get the TMP running and users were expected to allocate whatever they needed. Logon time was blazing fast and the power users were thrilled. Most were somewhere in the middle. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Wednesday, March 18, 2009 10:04 AM To: IBM-MAIN@bama.ua.edu Subject: Re: protecting ISPF dataset allocations Snip.. We have approached this by enforcing a standard set of concats at logon. *EVERYONE* runs this concat at logon. After that they are on their own. BTW This also extends to panel libraries. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- 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