Yes, that is my intention. I will heed your and Alan's advice. Thanks for the help.
--- On Fri, 17/12/10, Mueller, David <[email protected]> wrote: From: Mueller, David <[email protected]> Subject: Re: PROBLEMS DELETING MULTI VOLUME VSAM DSN To: [email protected] Received: Friday, 17 December, 2010, 5:50 AM I am assuming that you are wanting to get rid of everything that is still on the volumes. That is what the volume-targeted DEL VVR commands would do. Allen Staller has already given a more-detailed response. David Mueller | Systems Programmer SSRC (Southwood Shared Resource Center) 4070 Esplanade Way, Room 360D Phone: 850-414-9134 || Fax: 850-488-3600 E-mail: [email protected] Please Note: Florida has a very broad public records law. Most written communications to or from state officials regarding state business are public records available to the public and media upon request. Your e-mail communications may therefore be subject to public disclosure. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Dawes Sent: Thursday, December 16, 2010 1:44 PM To: [email protected] Subject: Re: PROBLEMS DELETING MULTI VOLUME VSAM DSN Wouldn't that cause a problem because the DATA and INDEX portions will still remain on the third volume? The CLUSTER, DATA & INDEX components are still allocated on the third volume. --- On Fri, 17/12/10, Mueller, David <[email protected]> wrote: From: Mueller, David <[email protected]> Subject: Re: PROBLEMS DELETING MULTI VOLUME VSAM DSN To: [email protected] Received: Friday, 17 December, 2010, 5:36 AM It should be possible to do volume-targeted DELETE VVR commands for the remaining data / index components and DELETE VSAM NOSCRATCH for the catalog entry. David Mueller | Systems Programmer SSRC (Southwood Shared Resource Center) 4070 Esplanade Way, Room 360D Phone: 850-414-9134 || Fax: 850-488-3600 E-mail: [email protected] Please Note: Florida has a very broad public records law. Most written communications to or from state officials regarding state business are public records available to the public and media upon request. Your e-mail communications may therefore be subject to public disclosure. -----Original Message----- <snip> I am trying to delete a multi-volume VSAM dataset. I receive the following error: DATA SET CICSPROD.CICS.UBSP.DFHTEMP.OLD NOT ALLOCATED, VOLUME NOT AVAILABLE VOLUME NECESSARY TO SATISFY YOUR REQUEST NOT ON SYSTEM, AND CANNOT BE MOUNTED ** ENTRY CICSPROD.CICS.UBSP.DFHTEMP.OLD NOT DELETED >From what the user told me that the dsn used to span 3 volumes and the 2 of >the dasds have been reused. He doesn't remember to volume names. Is there a >way of deleting the dsn without having to re-init the 2 volumes (if I do find >out the names)? I did a LISTCAT of the dsn to see if the volsers were still >available but I was unsuccessful : IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-5 Could anybody suggest a way of deleting them? <end-snip) ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
