Rich, That is what I have been trying to drum into their heads. However, users being users refuse to listen. The quickest way for them to fix their problem is to reach for the phone and call STORAGE SUPPORT.
________________________________ From: "Habres, Richard J" <[email protected]> To: [email protected] Sent: Friday, November 4, 2011 10:38:45 AM Subject: Re: DSN NOT RELEASING OVER ALLOCATED SPACE We had users who had the same problem. If the data set is not opened, it will not release the unused space. The way around it was to code a very small primary space and a larger secondary space. If not opened, it would be small. If opened, it would use what it needs and release when closed. Rich Richard J Habres VP - Bank of America/Merrill Lynch -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of willie bunter Sent: Friday, November 04, 2011 10:04 AM To: [email protected] Subject: DSN NOT RELEASING OVER ALLOCATED SPACE Good Day To All, We are trying to figure out this problem. Job A executes, it creates several dsns and many of these dsns are empty. We have the RLSE parm coded however it doesn't seem release the unused space for the empty dsns. Is there a way of fixing this problem or a work around? We are running RELEASE z/OS 01.11.00 Thanks for your help in advance. ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
