Re: D37 for PDSE in LNKLIST in SYSPLEX
Obviously you are welcome to try anything, but please be aware that almost none of the recommendations that have been posted are things that are in any way supported and they could have unknowable effects on your system. There is no approach that will let you safely delete a data set that is in the IPL-time LNKLST. The ENQs for LLA and XCFAS are for the system's protection. If you bypass them or override them you are doing so at your own risk. The system does not support renaming a LNKLST data set that is in use. The system does not support deleting a LNKLST data set that is in use. You can use dynamic LNKLST facilities to create a new LNKLST that has a copy of the data set with a different name. You can use the unknowably risky LNKLST update operation to get users off of the old LNKLST. After purging and restarting LLA, no one will still have an ENQ on the data set and you can delete it, if it is not a PDSE that was in the IPL-time LNKLST (as of z/OS 1.8 that particular restriction goes away). But you might have compromised your system in doing the UPDATE operation. There is no way of knowing. It might well have don no harm; It might well have done harm. Peter Relson z/OS Core Technology Design -- 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
D37 for PDSE in LNKLIST in SYSPLEX
Summary: We need to delete a file that has enqueue's on the DSN in multiple LPAR's on the same Z/900. Any help would be appreciated. In performing SMP/E processing we ran into a D37-04 on the CBC.SCCNCMP that resides on a SYSRES pack. The same DSN is used on four other LPAR'S on a z/900 running various levels of Z/OS. The CBC.SCCNCMP on the other LPAR'S are files unitque to that release of the Operating System. When we attempt to delete and define the file that needs more space, we get a DATASET in use by 10 users message. The other users are LLA and XCFAS. We assume this is because the dataset is named the same on the other LPAR'S. How can I build a new PDSE named CBC.SCCNCMP on a single LPAR without having to IPL? Mark House (402) 778-1966 Technical Development Services [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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
Re: D37 for PDSE in LNKLIST in SYSPLEX
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark House Sent: Thursday, March 08, 2007 12:07 PM To: IBM-MAIN@BAMA.UA.EDU Subject: D37 for PDSE in LNKLIST in SYSPLEX Summary: We need to delete a file that has enqueue's on the DSN in multiple LPAR's on the same Z/900. Any help would be appreciated. In performing SMP/E processing we ran into a D37-04 on the CBC.SCCNCMP that resides on a SYSRES pack. The same DSN is used on four other LPAR'S on a z/900 running various levels of Z/OS. The CBC.SCCNCMP on the other LPAR'S are files unitque to that release of the Operating System. When we attempt to delete and define the file that needs more space, we get a DATASET in use by 10 users message. The other users are LLA and XCFAS. We assume this is because the dataset is named the same on the other LPAR'S. How can I build a new PDSE named CBC.SCCNCMP on a single LPAR without having to IPL? Mark House If you are using RACF, then issue the commands: RDEF FACILITY STGADMIN.DPDSRSN.CBC.SCCNCMP UACC(NONE) PE STGADMIN.DPDSRSN.CBC.SCCNCMP CLASS(FACILITY) ID(...) ACCESS(ALTER) SETROPTS RACLIST(FACILITY) REFRESH Now, go into ISPF option 3.4 and bring up the dataset you want to rename on the pack on which it resides. Do option r to rename the dataset, you'll get a prompt telling you it's in use, but you can still rename it. Now, on that volume create CBC.SCCNCMP.NEW to be the proper size and copy into it. Now rename it to CBC.SCCNCMP. Ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2s340/2.6. 3.4 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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
Re: D37 for PDSE in LNKLIST in SYSPLEX
I went back and reread the original post. It is not entirely clear that the dataset you are applying maintenance to is NOT in use by at least 1 lpar. The instructions I gave are only good if the dataset you are applying maintenance to is on a volume that is not in use. I hope you are not applying maintenance to a running system. dave Dave Jousma Principal Systems Programmer [EMAIL PROTECTED] 616.653.8429 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jousma, David Sent: Thursday, March 08, 2007 1:29 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: D37 for PDSE in LNKLIST in SYSPLEX Since the dataset you want to mess with is on a different volume than the running one. Go to ispf 3.4 and list the dataset with a volser reference. Do a rename on the dataset to .old or something. You will get a panel that says it is enqueued, but bypassable. Press enter, and the rename will occur. You can then create the new dataset as .new, reload it, and rename it back into the real name. Dave Jousma Principal Systems Programmer [EMAIL PROTECTED] 616.653.8429 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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
Re: D37 for PDSE in LNKLIST in SYSPLEX
On Thu, 8 Mar 2007 12:06:30 -0600, Mark House [EMAIL PROTECTED] wrote: Summary: We need to delete a file that has enqueue's on the DSN in multiple LPAR's on the same Z/900. Any help would be appreciated. In performing SMP/E processing we ran into a D37-04 on the CBC.SCCNCMP that resides on a SYSRES pack. The same DSN is used on four other LPAR'S on a z/900 running various levels of Z/OS. The CBC.SCCNCMP on the other LPAR'S are files unitque to that release of the Operating System. When we attempt to delete and define the file that needs more space, we get a DATASET in use by 10 users message. The other users are LLA and XCFAS. We assume this is because the dataset is named the same on the other LPAR'S. How can I build a new PDSE named CBC.SCCNCMP on a single LPAR without having to IPL? To be clear. you are trying to delete a maintenance version of the data set, correct? It that is the case, since OS/390 2.10 you can just rename it via ISPF 3.4 even though it is in use. You will be presented with an are you sure panel. Then you can delete the renamed dsn. You need to have at least read authority to the RACF facility class named STGADMIN.DPDSRN.olddsname, where olddsname is up to 23 characters of the existing data set name. The doc is hard to find on this - it is in the DFSMSdfp Advanced Services manual in the chapter on Managing the Volume Table Of Contents (it is not documented in the ISPF manuals at all). Specifically, the information can be found in chapter 2.6 - Renaming a Data Set in the VTOC under the General Considerations and Restrictions section. If you are trying to apply maintenance to a live sysres (yuck) and need to delete that version... entirely different story. You need to copy to a new dsn, point SMP/E at that dsn, and do dynamic LNKLST update to point to the newdsn without touching the original one (don't delete it). Plenty of info in the archives with various scenarios. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: D37 for PDSE in LNKLIST in SYSPLEX
NOT for the faint of heart but you should be able to amaspzap the format4 DSCB to something else and then create another dataset with a close (but different name) copy the 'zapped ds to the new dataset and then zap the dscb of the new dataset to the old dataset set name. You might have to recatalog the new dataset (don't forget to uncatalog the old dataset). This might not work for VSAM dataset. Ed On Mar 8, 2007, at 12:06 PM, Mark House wrote: Summary: We need to delete a file that has enqueue's on the DSN in multiple LPAR's on the same Z/900. Any help would be appreciated. In performing SMP/E processing we ran into a D37-04 on the CBC.SCCNCMP that resides on a SYSRES pack. The same DSN is used on four other LPAR'S on a z/900 running various levels of Z/OS. The CBC.SCCNCMP on the other LPAR'S are files unitque to that release of the Operating System. When we attempt to delete and define the file that needs more space, we get a DATASET in use by 10 users message. The other users are LLA and XCFAS. We assume this is because the dataset is named the same on the other LPAR'S. How can I build a new PDSE named CBC.SCCNCMP on a single LPAR without having to IPL? Mark House (402) 778-1966 Technical Development Services [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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
