Re: CP Owned Volume Question
Some extra remarks 1. To be precise: the 1 means there is one active minidisk on that pack. If 2 would be shown, it could be 2 different minidisks or two users linked to the same minidisk (or even 1 user with 2 links to a single minidisk. 2. CP Q SYSTEM addr will tell you which minidisks are active. Example (shortened): *q system 400* DASD 0400 ATTACHED CPVOL 0077 530RES MAINT05C2 R/W , MAINT05A6 R/W MAINT05A2 R/W , MAINT04C4 R/W VMSERVS 0190 R/O , VMSERVU 0190 R/O DTCVSW1 0190 R/O , DTCVSW2 0190 R/O 3. As can be seen: there are many 190 minidisks here. Because of the address, we can assume it is a LINK to MAINT 190. To know that for sure: *CP Q MDISK USER VMSERVU 190* 4. A disk with only user minidisks does not need to be CPOWNED, only disks on which CP has some areas need to be. That is: disks with PAGE,SPOOL, DRCT, or TDISK. On CPOWNED disks, CP will read the allocation map, on other disks it is ignored by CP. To see if CP has some areas on a disk: - *CP Q ALLOC volser*: reveals what CP has obtained from the allocation map. CP reads it only at the time that the disk is getting ATTACHED to SYSTEM (e.g. during IPL) - *CPFMTXA vdev volser Alloc*: displays the current allocation map and allows to change it Before you can use CPFMTXA, you must get access to the disk, in fullpack mode - *CP ATTACH rdev vdev **: but then you need to be the exclusive user - *CP DEFINE MDISK vdev 0 END volser** *(need good priviledges) - *CP LINK xxx vdev myvdev MW|RR*: if the pack is defined as fullpack minidisk in the CP directory. P.S. As opposed to what has been suggested: there is no need at all to DETACH a disk from SYSTEM before updating the CP directory. The CP directory defines which users and minidisks are available; either linked as part of a user's LOGON, either linked by an explicit LINK command later on. For a minidisk to be linkable, the pack on which it is defined must be ATTACHed to SYSTEM, either thanks to SYSTEM CONFIG entries, either later on with a CP ATTACH to SYSTEM. 2008/7/9 Howard Rifkind [EMAIL PROTECTED]: Thanks folks. The directory showed that the disk is allocated 100% to one user id. I'll have to find out if that user id really needs a whole 3390/9. Thanks again. Huegel, Thomas [EMAIL PROTECTED] 7/8/2008 5:50 PM Well the 1 means there is 1 user linked to that disk.. that user is probably maint's minidisk. CPFMTXA 499 VPWK03 the 499 is a virtual address I don't remember, but you may need to: a) det it from maint (the mdisk) b) det it from the system (real addr) c) att to maint d) CPFMTXA -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Howard Rifkind Sent: Tuesday, July 08, 2008 4:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CP Owned Volume Question I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. -- Kris Buelens, IBM Belgium, VM customer support
Re: CP Owned Volume Question
The fact that it is ³CP OWNED² and not ³CP SYSTEM² would lead me to wonder about your statement ³Being that the volume is already labeled should I assume that it has allocated to lets say PERM?². I wouldn¹t make such an assumption, especially if someone took the trouble to put it in the CP Owned list. Get a read-only link to the volume and run ICKDSF to get a list of the allocation map of the device. A sample follows: link vmtestp ca05 ca05 rr DASD CA05 LINKED R/O; R/W BY 2 USERS Ready; T=0.01/0.01 07:32:44 ickdsf ICK030E DEFINE INPUT DEVICE: FN FT FM, CONSOLE, OR READER console CONSOLE ICK031E DEFINE OUTPUT DEVICE: FN FT FM, CONSOLE, OR PRINTER console CONSOLE ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0TIME: 07:32:5107/09/08 PAGE 1 ENTER INPUT COMMAND: cpvol list unit(ca05) nvfy CPVOL LIST UNIT(CA05) NVFY ICK00700I DEVICE INFORMATION FOR CA05 IS CURRENTLY AS FOLLOWS: PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 3990 STORAGE CONTROL DESCRIPTOR = E9 DEVICE DESCRIPTOR = 0C ADDITIONAL DEVICE INFORMATION = 48001F3C TRKS/CYL = 15, # PRIMARY CYLS = 32760 ICK04030I DEVICE IS A PEER TO PEER REMOTE COPY VOLUME ICK00703I DEVICE IS OPERATED AS A MINIDISK ICK03090I VOLUME SERIAL = 540RES ICK03024I DEVICE IS CURRENTLY FORMATTED WITHOUT FILLER RECORDS ICK03000I CPVOL REPORT FOR CA05 FOLLOWS: ICK03021I CA05 IS FORMATTED FOR VM/ESA MODE CYLINDER ALLOCATION CURRENTLY IS AS FOLLOWS: TYPE START ENDTOTAL - ---- PERM 0 38 39 PARM 39 158120 PARM 159278120 PARM 279398120 PERM 39932759 32361 ICK1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 07:33:1407/09/08 ENTER INPUT COMMAND: end END ICK2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0 Ready; T=0.01/0.01 07:33:16 If you find something other than PERM in the allocation map, then you¹d best not monkey with the volume unless you really know what you¹re doing. Systems will go down for much less. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/8/08 5:03 PM, Howard Rifkind [EMAIL PROTECTED] wrote: Thanks folks. The directory showed that the disk is allocated 100% to one user id. I'll have to find out if that user id really needs a whole 3390/9. Thanks again. Huegel, Thomas [EMAIL PROTECTED] 7/8/2008 5:50 PM Well the 1 means there is 1 user linked to that disk.. that user is probably maint's minidisk. CPFMTXA 499 VPWK03 the 499 is a virtual address I don't remember, but you may need to: a) det it from maint (the mdisk) b) det it from the system (real addr) c) att to maint d) CPFMTXA -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Howard Rifkind Sent: Tuesday, July 08, 2008 4:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CP Owned Volume Question I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your
CP Owned Volume Question
I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash.
Re: CP Owned Volume Question
Howard, First you have to find who has the current link to this volume. If it belongs to MAINT, then you can detach the virtual device number for this volume that is in use by MAINT. Once the query command shows that there are no users currently linked to this volume, then you can do the following: 1)detach 499 system 2)update your directory as needed for the additional mini disks on this volume 3)attach 499 system 4)directxa user - bring your updated directory online 5)either logoff and logon Maint to allocate the new mini disks to your virtual machine - or - use the LINK command to gain access to your new mini disks. Hope this helps. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Howard Rifkind Sent: Tuesday, July 08, 2008 2:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CP Owned Volume Question I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash.
Re: CP Owned Volume Question
Well the 1 means there is 1 user linked to that disk.. that user is probably maint's minidisk. CPFMTXA 499 VPWK03 the 499 is a virtual address I don't remember, but you may need to: a) det it from maint (the mdisk) b) det it from the system (real addr) c) att to maint d) CPFMTXA -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Howard Rifkind Sent: Tuesday, July 08, 2008 4:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CP Owned Volume Question I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash.
Re: CP Owned Volume Question
Thanks folks. The directory showed that the disk is allocated 100% to one user id. I'll have to find out if that user id really needs a whole 3390/9. Thanks again. Huegel, Thomas [EMAIL PROTECTED] 7/8/2008 5:50 PM Well the 1 means there is 1 user linked to that disk.. that user is probably maint's minidisk. CPFMTXA 499 VPWK03 the 499 is a virtual address I don't remember, but you may need to: a) det it from maint (the mdisk) b) det it from the system (real addr) c) att to maint d) CPFMTXA -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Howard Rifkind Sent: Tuesday, July 08, 2008 4:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CP Owned Volume Question I have a volume with a label of VPWK03 at address 499. Being that the volume is already labeled should I assume that it has allocated to lets say PERM? Volume shows up as follows: q 499 DASD 0499 CP OWNED VPWK03 1 I would think that being it is showing a '1' it is in use by system. I want to allocate a bunch of minidisks on the volume but am having problems getting it to be available. In the directory I have it define as a full pack mini under Maint. I'm getting the following: CPFMTXA 499 VPWK03 HCPCCF0040E DEVICE 0499 DOES NOT EXIST I haven't done this for a while. How can I get this resolved so I can start to allocate minidisks on the volume? Any help is appreciated. Thanks _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash.
