Page volume not recognized after IPL
We have recently ipl'ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 IPL NUCLEUS ACTIVE ON VOLUME DVRESA q cpowned Slot Vol-ID Rdev Type Status 1 DVRESA E100 OwnOnline and attached 2 DVSPLA E101 OwnOnline and attached 3 DVPAGA E102 OwnOnline and attached 4 DVW01A E103 OwnOnline and attached 5 DVW02A E104 OwnOnline and attached 6 -- - Reserved 7 -- - Reserved 8 -- - Reserved 9 -- - Reserved 10 -- - Reserved q e100-e105 DASD E100 CP OWNED DVRESA 78 DASD E101 CP OWNED DVSPLA 1 DASD E102 CP OWNED DVPAGA 0 DASD E103 CP OWNED DVW01A 118 DASD E104 CP OWNED DVW02A 52 DASD E105 DVRESB
Re: Page volume not recognized after IPL
Ashwin, Looks like there is no page space allocated on the designated page volume. Did you run the allocation part of CPFMTXA after you had formatted the disk? Wolfgang From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bhemidhi, Ashwin Sent: Friday, November 19, 2010 10:26 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Page volume not recognized after IPL We have recently ipl'ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 IPL NUCLEUS ACTIVE ON VOLUME DVRESA q cpowned Slot Vol-ID Rdev Type Status 1 DVRESA E100 OwnOnline and attached 2 DVSPLA E101 OwnOnline and attached 3 DVPAGA E102 OwnOnline and attached 4 DVW01A E103 OwnOnline and attached 5 DVW02A E104 OwnOnline and attached 6 -- - Reserved 7 -- - Reserved 8 -- - Reserved 9 -- - Reserved 10 -- - Reserved q e100-e105 DASD E100 CP OWNED DVRESA 78 DASD E101 CP OWNED DVSPLA 1 DASD E102 CP OWNED DVPAGA 0 DASD E103 CP OWNED DVW01A 118 DASD E104 CP OWNED DVW02A 52 DASD E105 DVRESB Software AG - Group Executive Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Arnd Zinnhardt, Mark Edwards, David Broadbent, Josef Bommersbach, Dr. Wolfram Jost, Kamyar Niroumand, Ivo Totev Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany, - Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/ Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), David Broadbent, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com/
Re: Page volume not recognized after IPL
Hello, Ashwin: For the dasd to be recognized it must be formated AND allocated as PAGE with CPFMTXA, AND must be defined as Owned into SYSTEM CONFIG. Is the DVRESB a new Page dasd? To check dynamically, use these commands: CP DEFine CPOWN SLOT 6 DVRESB followed by other CP QUERY ALLOC If the Query shows the page area, the problem is in the SYSTEM CONFIG. If not, the problem was with CPFMTXA. __ Clovis From: Bhemidhi, Ashwin ashw...@ti.com To: IBMVM@LISTSERV.UARK.EDU Date: 19/11/2010 07:26 Subject: Page volume not recognized after IPL Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU We have recently ipl’ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 IPL NUCLEUS ACTIVE ON VOLUME DVRESA q cpowned Slot Vol-ID Rdev Type Status 1 DVRESA E100 OwnOnline and attached 2 DVSPLA E101 OwnOnline and attached 3 DVPAGA E102 OwnOnline and attached 4 DVW01A E103 OwnOnline and attached 5 DVW02A E104 OwnOnline and attached 6 -- - Reserved 7 -- - Reserved 8 -- - Reserved 9 -- - Reserved 10 -- - Reserved q e100-e105 DASD E100 CP OWNED DVRESA 78 DASD E101 CP OWNED DVSPLA 1 DASD E102 CP OWNED DVPAGA 0 DASD E103 CP OWNED DVW01A 118 DASD E104 CP OWNED DVW02A 52 DASD E105 DVRESB
Re: Page volume not recognized after IPL
If -at IPL time- a volume is included in the CP OWNED list, it is attached to SYSTEM automatically. At runtime: when you ATTACH a disk to SYSTEM, CP will verify if it is in the CP OWNED list. In any case, at ATTACH TO SYSTEM time: for disks in the CP OWNED list, and only for those, CP will read the ALLOC map to see what it can use (PAGE, SPOOL, etc). 2010/11/19 George Henke/NYLIC george_he...@newyorklife.com Also it must be ATTACHED to SYSTEM. I had a problem recognizing my second page pack at level 2 because it was not attached to level 2 as SYSTEM. q dev# and/or q dasd volser should show its attach status, *gclo...@br.ibm.com* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/19/2010 06:40 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Page volume not recognized after IPL Hello, Ashwin: For the dasd to be recognized it must be formated AND allocated as PAGE with CPFMTXA, AND must be defined as Owned into SYSTEM CONFIG. Is the DVRESB a new Page dasd? To check dynamically, use these commands: CP DEFine CPOWN SLOT 6 DVRESB followed by other CP QUERY ALLOC If the Query shows the page area, the problem is in the SYSTEM CONFIG. If not, the problem was with CPFMTXA. __ Clovis From: Bhemidhi, Ashwin ashw...@ti.com To: IBMVM@LISTSERV.UARK.EDU Date: 19/11/2010 07:26 Subject: Page volume not recognized after IPL Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU -- We have recently ipl’ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 IPL NUCLEUS ACTIVE ON VOLUME DVRESA q cpowned Slot Vol-ID Rdev Type Status 1 DVRESA E100 OwnOnline and attached 2 DVSPLA E101 OwnOnline and attached 3 DVPAGA E102 OwnOnline and attached 4 DVW01A E103 OwnOnline and attached 5 DVW02A E104 OwnOnline and attached 6 -- - Reserved 7 -- - Reserved 8 -- - Reserved 9 -- - Reserved 10 -- - Reserved q e100-e105 DASD E100 CP OWNED DVRESA 78 DASD E101 CP OWNED DVSPLA 1 DASD E102 CP OWNED DVPAGA 0 DASD E103 CP OWNED DVW01A 118 DASD E104 CP OWNED DVW02A 52 DASD E105 DVRESB -- Kris Buelens, IBM Belgium, VM customer support
Re: Page volume not recognized after IPL
Hello Clovis, The PAGE DASD is one of the 5 3390-3 that was initialized as part of the sysres pack when z/VM 6.1 was installed. I have not manually any additional ones to this LPAR. We have 2 sysres pack (DVxxxA and DVxxxB ) which serve as active and alternates system volumes. Current active one is DVxxxA set (E100-E104) and DVPAGB is the page volume that's part of the current alternates. I do understand that we do not need to have a dedicated PAGE volumes as part of the sysres since its just used for paging but this is the setup we follow here. I do plan to user the alternate PAGE volume so as to give the system some more PAGE space. PAGE DVPAGA volume is in the system config and attached to the system, cp q alloc does not show any page space on DVPAGA. I do not understand y. Can I display the allocation table of a volume attached to the system? Even though the PAGE volume is not being used I do not want to detach the PAGE volume in fear of causing a crash. Regards, Ashwin q cpowned Slot Vol-ID Rdev Type Status 1 DVRESA E100 OwnOnline and attached 2 DVSPLA E101 OwnOnline and attached 3 DVPAGA E102 OwnOnline and attached 4 DVW01A E103 OwnOnline and attached 5 DVW02A E104 OwnOnline and attached SYSTEM CONFIG /**/ /* CP_Owned Volume Statements */ /**/ CP_Owned Slot 1 DVRESA CP_Owned Slot 2 DVSPLA CP_Owned Slot 3 DVPAGA CP_Owned Slot 4 DVW01A CP_Owned Slot 5 DVW02A CP_Owned Slot 6 RESERVED CP_Owned Slot 7 RESERVED CP_Owned Slot 8 RESERVED CP_Owned Slot 9 RESERVED CP_Owned Slot 10 RESERVED Cp query alloc doe not show any PAGE space on DVPAGA cp q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001780 AVAIL=0001558 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 IPL NUCLEUS ACTIVE ON VOLUME DVRESA From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of gclo...@br.ibm.com Sent: Friday, November 19, 2010 5:40 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Page volume not recognized after IPL Hello, Ashwin: For the dasd to be recognized it must be formated AND allocated as PAGE with CPFMTXA, AND must be defined as Owned into SYSTEM CONFIG. Is the DVRESB a new Page dasd? To check dynamically, use these commands: CP DEFine CPOWN SLOT 6 DVRESB followed by other CP QUERY ALLOC If the Query shows the page area, the problem is in the SYSTEM CONFIG. If not, the problem was with CPFMTXA. __ Clovis From: Bhemidhi, Ashwin ashw...@ti.com To: IBMVM@LISTSERV.UARK.EDU Date: 19/11/2010 07:26 Subject: Page volume not recognized after IPL Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU We have recently ipl'ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE
Re: Page volume not recognized after IPL
Our PAGE volume is in the CP OWNED list and it is attached to the system. It just that VM does not recognize any allocation on the PAGE volume. DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 And this PAGE was initiated as a part of the vm 6.1 installation PACK. We did recently migrate the DASD from one Storage sub system to a new storage system. I just DDR'ed 'copy all' the volumes and relabeled the new sysres, shutdown and re'ipled on the new storage. Do I have manually reinitialized the PAGE volumes, will DDR copy all not copy the allocation table. Thank you, Ashwin From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Friday, November 19, 2010 9:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Page volume not recognized after IPL If -at IPL time- a volume is included in the CP OWNED list, it is attached to SYSTEM automatically. At runtime: when you ATTACH a disk to SYSTEM, CP will verify if it is in the CP OWNED list. In any case, at ATTACH TO SYSTEM time: for disks in the CP OWNED list, and only for those, CP will read the ALLOC map to see what it can use (PAGE, SPOOL, etc). 2010/11/19 George Henke/NYLIC george_he...@newyorklife.commailto:george_he...@newyorklife.com Also it must be ATTACHED to SYSTEM. I had a problem recognizing my second page pack at level 2 because it was not attached to level 2 as SYSTEM. q dev# and/or q dasd volser should show its attach status, gclo...@br.ibm.commailto:gclo...@br.ibm.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU 11/19/2010 06:40 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU cc Subject Re: Page volume not recognized after IPL Hello, Ashwin: For the dasd to be recognized it must be formated AND allocated as PAGE with CPFMTXA, AND must be defined as Owned into SYSTEM CONFIG. Is the DVRESB a new Page dasd? To check dynamically, use these commands: CP DEFine CPOWN SLOT 6 DVRESB followed by other CP QUERY ALLOC If the Query shows the page area, the problem is in the SYSTEM CONFIG. If not, the problem was with CPFMTXA. __ Clovis From: Bhemidhi, Ashwin ashw...@ti.commailto:ashw...@ti.com To: IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU Date: 19/11/2010 07:26 Subject: Page volume not recognized after IPL Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU We have recently ipl'ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E103 DVW01A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E104 DVW02A 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE
Re: Page volume not recognized after IPL
Hi Ashwin, Establish a R/O link from MAINT as vadr to that E102 and then enter: cpfmtxa vadr DVPAGA allocate This will read the allocation map directly from the volume without the risk to disturb it. I do not believe that your z/VM 6.1 would not recognize allocation records if they were written correctly and also did never made any negative experience with DDR and COPY ALL. For 2nd level systems I do quite often what you did. So probably the mother disk was not initialized correctly during the basic installation process. Best wishes, Wolfgang From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bhemidhi, Ashwin Sent: Friday, November 19, 2010 4:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Page volume not recognized after IPL Our PAGE volume is in the CP OWNED list and it is attached to the system. It just that VM does not recognize any allocation on the PAGE volume. DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=000 INUSE=000 AVAIL=000 And this PAGE was initiated as a part of the vm 6.1 installation PACK. We did recently migrate the DASD from one Storage sub system to a new storage system. I just DDR'ed 'copy all' the volumes and relabeled the new sysres, shutdown and re'ipled on the new storage. Do I have manually reinitialized the PAGE volumes, will DDR copy all not copy the allocation table. Thank you, Ashwin From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Friday, November 19, 2010 9:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Page volume not recognized after IPL If -at IPL time- a volume is included in the CP OWNED list, it is attached to SYSTEM automatically. At runtime: when you ATTACH a disk to SYSTEM, CP will verify if it is in the CP OWNED list. In any case, at ATTACH TO SYSTEM time: for disks in the CP OWNED list, and only for those, CP will read the ALLOC map to see what it can use (PAGE, SPOOL, etc). 2010/11/19 George Henke/NYLIC george_he...@newyorklife.com Also it must be ATTACHED to SYSTEM. I had a problem recognizing my second page pack at level 2 because it was not attached to level 2 as SYSTEM. q dev# and/or q dasd volser should show its attach status, gclo...@br.ibm.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/19/2010 06:40 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Page volume not recognized after IPL Hello, Ashwin: For the dasd to be recognized it must be formated AND allocated as PAGE with CPFMTXA, AND must be defined as Owned into SYSTEM CONFIG. Is the DVRESB a new Page dasd? To check dynamically, use these commands: CP DEFine CPOWN SLOT 6 DVRESB followed by other CP QUERY ALLOC If the Query shows the page area, the problem is in the SYSTEM CONFIG. If not, the problem was with CPFMTXA. __ Clovis From: Bhemidhi, Ashwin ashw...@ti.com To: IBMVM@LISTSERV.UARK.EDU Date: 19/11/2010 07:26 Subject: Page volume not recognized after IPL Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU We have recently ipl'ed one of our test z/VM 6.1 system off the our alternate sysres pack. The system does not seem to recognize the page volume. Is there something I did not configure? I am ready to add another page volume to make sure that it does not ABEND due to lack of page space. I will check the allocation on the PAGE volume after I add some PAGE DASD. Thank you, Ashwin Bhemidhi q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- * * - - 0 0 0 0% NOT FOUND Ready; T=0.01/0.01 03:07:31 q alloc DASD E100 DVRESA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=000 INUSE=000 AVAIL=000 DRCT TOTAL=020 INUSE=002 AVAIL=018, ACTIVE DASD E101 DVSPLA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000 AVAIL=000 SPOOL TOTAL=0003338 INUSE=0001775 AVAIL=0001563 DRCT TOTAL=000 INUSE=000 AVAIL=000 DASD E102 DVPAGA 3390 CKD-ECKD (UNITS IN CYLINDERS) TDISK TOTAL=000 INUSE=000 AVAIL=000 PAGE TOTAL=000 INUSE=000
PERFKIT data structure dsects
Esteemed colleagues The z/VM V5R4.0 Performance Toolkit Reference manual documents the format of the Perfkit history, summary and trend records. Are these DSECTS available in a machine readable format anywhere, or am I facing a lot of cut and pasting this afternoon? Have a good one. -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: PERFKIT data structure dsects
Hi, Alan. So they're in the FCONX MACLIB, eh? Good to know that; I'll drop a note to IBM Pubs suggesting that that bit of information be included. However I can't seem t find an FCONX MACLIB on my system (z/VM 5.4) anywhere. Do you happen to know where its located? Thanks and have a Happy Thanksgiving. On 11/19/2010 11:52 AM, Alan Altmark wrote: On Friday, 11/19/2010 at 12:16 EST, Dave Jones d...@vsoft-software.com wrote: Esteemed colleagues The z/VM V5R4.0 Performance Toolkit Reference manual documents the format of the Perfkit history, summary and trend records. Are these DSECTS available in a machine readable format anywhere, or am I facing a lot of cut and pasting this afternoon? Those sections in the book provide references to the DSECTs. E.g. TRNDRHDR and HISxxSCT, all located in FCONX MACLIB. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: PERFKIT data structure dsects
On Friday, 11/19/2010 at 01:31 EST, Dave Jones d...@vsoft-software.com wrote: So they're in the FCONX MACLIB, eh? Good to know that; I'll drop a note to IBM Pubs suggesting that that bit of information be included. However I can't seem t find an FCONX MACLIB on my system (z/VM 5.4) anywhere. Do you happen to know where its located? Nope, sure don't. The build list is FCXACLIB EXEC, and it says **START OF SPECIFICATIONS* ** * Name - FCXACLIB* ** * Descriptive Name - Buildlist for FCONX MACLIB * ** * Copyright -* * THIS MODULE IS RESTRICTED MATERIALS OF IBM * * 5741-A05 (C) COPYRIGHT IBM CORP. - 2003, 2008* * LICENSED MATERIALS - PROPERTY OF IBM * ** * Status - Performance Toolkit for VM Function Level 5.4.0 ** * Function - This file is input to VMFBLD EXEC when * * building the FCONX MACLIB (GENERAL USE * * PROGRAMMING INTERFACES MACLIB). * ** * Notes -* ** **END OF SPECIFICATIONS*** Yet, this exec is not referenced in the 5VMPTK40 PPF. HmmmUnless Mike has a solution, I suggest that you go ahead and open a PMR. Enjoy your Thanksgiving, too! Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: Page volume not recognized after IPL
On Friday, 11/19/2010 at 02:16 EST, Bhemidhi, Ashwin ashw...@ti.com wrote: You are correct there is no PAGE space allocated on the PAGE volume. I will add another PAGE device and then format and correct volume DVPAGA. Since CP is not actively using the volume, you should be able to 1. DRAIN it 2. DETACH it from SYSTEM 3. ATTACH it to yourself 4. Run CPFMTXA ALLOCATE on it 5. DETACH it from yourself 6. ATTACH it to SYSTEM 7. START it Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: Page volume not recognized after IPL
Hi Alan, I just followed your instructions and fixed it. Since the PAGE device was not being used I was able to correct it without adding another device. I will have to remember to drain a PAGE volume no matter what. I am learning new stuff every day. Thank you, Ashwin -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, November 19, 2010 1:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Page volume not recognized after IPL On Friday, 11/19/2010 at 02:16 EST, Bhemidhi, Ashwin ashw...@ti.com wrote: You are correct there is no PAGE space allocated on the PAGE volume. I will add another PAGE device and then format and correct volume DVPAGA. Since CP is not actively using the volume, you should be able to 1. DRAIN it 2. DETACH it from SYSTEM 3. ATTACH it to yourself 4. Run CPFMTXA ALLOCATE on it 5. DETACH it from yourself 6. ATTACH it to SYSTEM 7. START it Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: PERFKIT data structure dsects
Hi, Alan. Some more searching here on the system has failed to located any trace of an FCONX MACLIB file, so I believe I will open a PMR on it on Monday. Thanks for your help, Alan. DJ On 11/19/2010 01:05 PM, Alan Altmark wrote: On Friday, 11/19/2010 at 01:31 EST, Dave Jones d...@vsoft-software.com wrote: So they're in the FCONX MACLIB, eh? Good to know that; I'll drop a note to IBM Pubs suggesting that that bit of information be included. However I can't seem t find an FCONX MACLIB on my system (z/VM 5.4) anywhere. Do you happen to know where its located? Nope, sure don't. The build list is FCXACLIB EXEC, and it says **START OF SPECIFICATIONS* ** * Name - FCXACLIB* ** * Descriptive Name - Buildlist for FCONX MACLIB * ** * Copyright -* * THIS MODULE IS RESTRICTED MATERIALS OF IBM * * 5741-A05 (C) COPYRIGHT IBM CORP. - 2003, 2008* * LICENSED MATERIALS - PROPERTY OF IBM * ** * Status - Performance Toolkit for VM Function Level 5.4.0 ** * Function - This file is input to VMFBLD EXEC when * * building the FCONX MACLIB (GENERAL USE * * PROGRAMMING INTERFACES MACLIB). * ** * Notes -* ** **END OF SPECIFICATIONS*** Yet, this exec is not referenced in the 5VMPTK40 PPF. HmmmUnless Mike has a solution, I suggest that you go ahead and open a PMR. Enjoy your Thanksgiving, too! Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: z/VM 5.4 z196 Service Error
I ran into this issue when I was installing the z/VM 5.4 z196 APARs. The IBM recommendation worked fine, but I had to open an ETR to get the info. Regards, Vaggelis J. Tsagris Bank of America VM Systems/products #15863 Phone: (925) 978-2611 Fax: (925) 978-2611 e-mail: vaggelis.j.tsag...@bankofamerica.com mailto:vaggelis.j.tsag...@bankofamerica.com From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of joe.dipi...@frit.frb.org Sent: Friday, November 19, 2010 12:56 PM To: IBMVM@LISTSERV.UARK.EDU Subject: z/VM 5.4 z196 Service Error For those of you who are planning on installing the z/VM 5.4 z196 APARs, you may be interested in this information. If your installation had migrated from a earlier release of z/VM (perhaps 5.1.0 or 5.2.0), there is a good possibility that you will run into the same issue that I did when attempting SERVICE ALL for the APAR maintenance envelope file. It seems that a macro file IRAQVS MACRO was not erased during the migration procedure. The presence of this macro causes the following errors as shown below. In order to rectify this situation, IBM recommends that you erase the macro from the MNT493 minidisk prior to running SERVICE. If you have already encountered this error, then follow the IBM recommendation above and rerun SERVICE. I hope this is helpful and it saves you the time it took for me to glean this information from IBM. As well, IBM has committed to providing this work-around in a PSP bucket. ST:VMFBLD1851I (2 of 15) VMFBDMLB processing HCPGPI EXEC O, target is ST:BUILD6 490 (L) ST:VMFMLB2219I Processing object IRAQVS ST:DMSUPD178I Updating IRAQVS MACRO K2 ST:DMSUPD178I Applying IRAQVS K64798HP J1 ST: ST:File IRAQVS K64798HP J1 REC # 0 = ./ I 00031000 $ 32000 1000 WN:DMSUPD174W Sequence error introduced in output file: 00032000 to WN:00032000 ST:DMSUPD177I Warning messages issued (severity = 8); REP option ignored SV:VMFMLB1965E The command, UPDATE, failed with return code 8 while SV:processing object IRAQVS. It was operating upon file SV:IRAQVS MACRO on 493 (K) ST:VMFMLB2219I Processing object VRDCBLOK ST:VMFMLB2219I Processing object HCPMDLAT ST:VMFMLB2220I Updating service history member for HCPGPI MACLIB SV:VMFBLD1851E (2 of 15) VMFBDMLB completed with return code 100. Some SV:objects were not built Joseph Di Pippo Operating Systems Programmer III FRIT Computing Services z/OS, z/VM, Hardware Support 1-201-531-3820 -- 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.
Re: z/VM 5.4 z196 Service Error
Maybe I did not see it because I did not apply the APAR. What APAR did you get this on? Tsagris, Vaggelis J vaggelis.j.tsag...@bankofamerica.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/19/2010 04:03 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: z/VM 5.4 z196 Service Error I ran into this issue when I was installing the z/VM 5.4 z196 APARs. The IBM recommendation worked fine, but I had to open an ETR to get the info. Regards, Vaggelis J. Tsagris Bank of America VM Systems/products #15863 Phone: (925) 978-2611 Fax: (925) 978-2611 e-mail: vaggelis.j.tsag...@bankofamerica.com From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of joe.dipi...@frit.frb.org Sent: Friday, November 19, 2010 12:56 PM To: IBMVM@LISTSERV.UARK.EDU Subject: z/VM 5.4 z196 Service Error For those of you who are planning on installing the z/VM 5.4 z196 APARs, you may be interested in this information. If your installation had migrated from a earlier release of z/VM (perhaps 5.1.0 or 5.2.0), there is a good possibility that you will run into the same issue that I did when attempting SERVICE ALL for the APAR maintenance envelope file. It seems that a macro file IRAQVS MACRO was not erased during the migration procedure. The presence of this macro causes the following errors as shown below. In order to rectify this situation, IBM recommends that you erase the macro from the MNT493 minidisk prior to running SERVICE. If you have already encountered this error, then follow the IBM recommendation above and rerun SERVICE. I hope this is helpful and it saves you the time it took for me to glean this information from IBM. As well, IBM has committed to providing this work-around in a PSP bucket. ST:VMFBLD1851I (2 of 15) VMFBDMLB processing HCPGPI EXEC O, target is ST:BUILD6 490 (L) ST:VMFMLB2219I Processing object IRAQVS ST:DMSUPD178I Updating IRAQVS MACRO K2 ST:DMSUPD178I Applying IRAQVS K64798HP J1 ST: ST:File IRAQVS K64798HP J1 REC # 0 = ./ I 00031000 $ 32000 1000 WN:DMSUPD174W Sequence error introduced in output file: 00032000 to WN:00032000 ST:DMSUPD177I Warning messages issued (severity = 8); REP option ignored SV:VMFMLB1965E The command, UPDATE, failed with return code 8 while SV:processing object IRAQVS. It was operating upon file SV:IRAQVS MACRO on 493 (K) ST:VMFMLB2219I Processing object VRDCBLOK ST:VMFMLB2219I Processing object HCPMDLAT ST:VMFMLB2220I Updating service history member for HCPGPI MACLIB SV:VMFBLD1851E (2 of 15) VMFBDMLB completed with return code 100. Some SV:objects were not built Joseph Di Pippo Operating Systems Programmer III FRIT Computing Services z/OS, z/VM, Hardware Support 1-201-531-3820 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.
Re: APARs and PTFs for the z196
At least since 6/10/08. That's the date on my HCPSADMP EXEC and it checks for each of the below modules. Billy On 16 Nov 2010 at 7:30, David Boyes wrote: Secondly, you do not need HLASM to create/maintain the standalone dump program. HCPSADMP checks for HLASM, HASM, and ASSEMBLE (FASM). It can use any of them. Really? That´s cool. I´ve been continuing to order HLASM on systems that don´t need it, then. Any idea when that change went in?
