If you have many page and spool packs, you get a lot more than you need with that and it does not specifically indicate the IPL device. If either the DRCT or PARM space is on the sysres, then Q ALLOC DRCT or Q ALLOC PARM will give you what you need. Q ALLOC ALL will tell you which device was IPLed; however, it is like Q ALLOC MAP on steroids and its specification of the IPL volume is the last line in the display.
Pipe cp q alloc all | take last | cons | spec /q dasd/ 1 w-1 nw | cp | cons IPL NUCLEUS ACTIVE ON VOLUME VM3RES DASD 1FA6 CP OWNED VM3RES 13 The above pipe will tell you what you need to know. If there had been a second VM3RES, it would have been in the response to the Q DASD, but it would not have been CP OWNED or ATTACHED TO SYSTEM. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Heinz-Josef Glaser > Sent: Thursday, November 04, 2010 12:58 AM > To: [email protected] > Subject: Re: How to determine SYSRES > > try to locate the CP-Dasds with > > Q ALLOC MAP > > You will see the VOLIDs and RDEVs from all CP-Dasds then. > > Mit freundlichen Grüssen / Best regards > Heinz-Josef Glaser > Systemspezialist z/OS, z/VM, z/VSE > Global Technology Services > GE Server Services SPL8 Manag Serv Sys Z IBM Deutschland > Rathausstrasse 7 > 09111 Chemnitz > Tel.: +49 371 6978 2876 > Fax: +49 371 6978 2280 > Mobile: +49 172 668 3018 > E-Mail: [email protected] > > IBM Deutschland Infrastructure Technology Services GmbH > Geschäftsführung: Ulrike Hetzel > Sitz der Gesellschaft: Ehningen / Registergericht: > Amtsgericht Stuttgart, HRB 727973 > > > > From: Mike Walter <[email protected]> > To: [email protected] > Date: 27.09.10 19:27 > Subject: Re: How to determine SYSRES > Sent by: The IBM z/VM Operating System <[email protected]> > > > > I guess you can match that up to the CPOWNED list to get the > real CCUU, since it is listed only as Volume Serial Number: > > Or, simply: CP QUERY DASD volser > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > > > "Frank M. Ramaekers" <[email protected]> > > Sent by: "The IBM z/VM Operating System" > <[email protected]> 09/27/2010 12:20 PM Please respond > to "The IBM z/VM Operating System" <[email protected]> > > > > To > [email protected] > cc > > Subject > Re: How to determine SYSRES > > > > > > > I guess you can match that up to the CPOWNED list to get the > real CCUU, since it is listed only as Volume Serial Number: > > Module CPLOAD was loaded from minidisk on volume 540RES at > cylinder 39. > Parm disk number 1 is on volume 540RES, cylinders 39 through 158. > Last start was a system restart from SHUTDOWN REIPL. > > > > Frank M. Ramaekers Jr. > > > > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Gregg > Sent: Monday, September 27, 2010 11:53 AM > To: [email protected] > Subject: Re: How to determine SYSRES > > CP Query CPLOAD? > On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers < > [email protected]> wrote: > How can you determine the SYSRES volume? (Other that > interrogating the > SYSTEM CONFIG under System_Residence) > (I know it?s within the CPOWNED list, but I don?t want to > depend on the VolSer to find it) (Too bad there?s not a CP Q SYSRES) > > > Frank M. Ramaekers Jr. > > Systems Programmer > MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. > Phone: (254)761-6649 > 1200 Wooded Acres Dr. > Fax: (254)741-5777 > Waco, Texas 76701 > > > _____________________________________________________ This > message contains information which is privileged and > confidential and is solely for the use of the intended > recipient. If you are not the intended recipient, be aware > that any review, disclosure, copying, distribution, or use of > the contents of this message is strictly prohibited. If you > have received this in error, please destroy it immediately > and notify us at [email protected]. > > > > -- > Gregg Reed > "No Plan, survives execution" > _____________________________________________________ This > message contains information which is privileged and > confidential and is solely for the use of the intended > recipient. If you are not the intended recipient, be aware > that any review, disclosure, copying, distribution, or use of > the contents of this message is strictly prohibited. If you > have received this in error, please destroy it immediately > and notify us at [email protected]. > > > > > The information contained in this e-mail and any accompanying > documents may contain information that is confidential or > otherwise protected from disclosure. If you are not the > intended recipient of this message, or if this message has > been addressed to you in error, please immediately alert the > sender by reply e-mail and then delete this message, > including any attachments. Any dissemination, distribution or > other use of the contents of this message by anyone other > than the intended recipient is strictly prohibited. All > messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to > ensure compliance with our internal policies and to protect > our business. E-mails are not secure and cannot be guaranteed > to be error free as they can be intercepted, amended, lost or > destroyed, or contain viruses. You are deemed to have > accepted these risks if you communicate with us by e-mail. >
