Re: How to determine SYSRES
-Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dale R. Smith Sent: Wednesday, November 10, 2010 2:49 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES I have a local mod to CP that I originally got from Melinda Varian thru VMSHARE, (that I have maintained thru all the versions/releases of VM since), that adds an extra line to the reponse from QUERY CPLEVEL, (for Class E users), that display the IPL, CheckPoint, and Warm Volsers and Addresses. Requirement coming soon to a IBM database near you. 8-) -- db
Re: How to determine SYSRES
In a single PIPE: PIPE (endchar ?), | LITERAL CP Q ALLOC ALL , | CP, | TAKE LAST 1 , | SPECS W6 1 , |l:LOOKUP W1, | DROP FIRST 1, | CONSOLE, ?, LITERAL QUERY CPOWNED, | CP, | SPEC W2-*, |l: Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Ackerman Sent: Tuesday, November 09, 2010 10:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' This won't work. You cannot set the REXX variable and use it in the same pipe. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' 'PIPE CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Not tested. But then the first pipe wasn't tested either. Alan Ackerman _ 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 privacy...@ailife.com.
Re: How to determine SYSRES
Not tested. But then the first pipe wasn't tested either. Au contraire mon ami. My first Pipe was tested, albeit not quite correctly. I had used a home-grown REXX EXEC to test it. Until QUIT is entered, the REXX EXEC repeatedly prompts for a rexx command, executes it, and continues to prompts again. I didn't believe that using a rexx variable would work either, not even inside a rexx exec. But I had recently re-learned that inside a pipe one can read an existing stem, make changes, use the BUFFER stage, and then re-write the same stem name. I re-learn more every day. So I wondered if recent changes to Pipes might let me use a variable as part of the processing, after all, the Piper is very clever. I again re-learned that it is not possible because when rexx interprets that pipe command, the variable has not yet been set, and will still be an uninitialized variable when processed at its second reference in the pipe. But that REXX EXEC provided a quite surprise. The first time I entered that erroneous Pipe command, the results were as expected: it did not work. But it silently set the sysres variable before failing. Not realizing that the sysres var had been set, and not leaving the REXX EXEC prompts, I decided to try adding the 'BUFFER' stage to see if that might help the way it does when reading and writing the same stem. So I pressed the RETRIEVE PFkey, inserted the 'BUFFER' stage and pressed Enter. That time it worked perfectly. So I removed the BUFFER stage and tried again (there might have been a few other attempts that failed due to typos). It continued to work perfectly, but unbeknownst to me only because the sysres var was still set. So the tested results were posted, with me confident that I had learned something new. After Richard replied that it could not work, I tried again so that I could show a console list of it working. Naturally that test was doomed to failure, since the command was copied and pasted from the post (with no typos). But it worked when I pressed the RETRIEVE PFkey and pressed Enter again, unchanged! WTH!!??? It took a couple minutes for the proper synapses to fire before I understood why. :-) Moral of the story: ah... you figure it out - consider it a learning experience. The corrected, complete pipe was posted November 4: pipe cp q alloc all | take last | cons | spec /q dasd/ 1 w-1 nw | cp | pick w3 == /CP/ | cons Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Alan Ackerman alan.acker...@bankofamerica.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/09/2010 10:22 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' This won't work. You cannot set the REXX variable and use it in the same pipe. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' 'PIPE CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Not tested. But then the first pipe wasn't tested either. Alan Ackerman 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.
Re: How to determine SYSRES
True, but you can use the value in another cp command that you construct in the Pipe (tested): 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS /QUERY DASD/ 1 W-1 NW' , '| CP', '| LOCATE / CP /', '| CONSOLE', '| SPECS W2 1 WRITE W5 1', '| VAR IPLDEV', '| DROP 1', '| VAR IPLVOL' There is no need for more than 1 invocation of Pipes or for multi-stream Pipes. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Ackerman Sent: Tuesday, November 09, 2010 8:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES This won't work. You cannot set the REXX variable and use it in the same = pipe. Not tested. But then the first pipe wasn't tested either. Alan Ackerman
Re: How to determine SYSRES
This pipe below can never work as the author apparently expected, whatever the piper might implement 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Just think a bit. It is a REXX EXEC, so REXX is reading the source lines, and replaces all variables by their contents (or the uppercased variable name). In the case above: only 'sysres' is outside the quotes and replaced by whatever value it has at that time. All lines (but the last) end with a , so REXX joins it to the presvious string with 1 blnk in between. When REXX built this long string (from the 9 source lines), it sees it is not an assigment, not an IF, So it passes the string to the current address (those that know me a bit know that I tell it should better be COMMAND). So the CMS command processor starts the PIPE command, and it gets this long string to handle. PIPE simply cannot know that part of the PICK parameters ever were a runtime variable. And, there is even a second error: the second CP stage. It will first pass QUERY CPOWNED as command to CP, and then the records it finds in its input stream. In this case the 6th word of the last line of Q ALLOC. I guess your IPL volser is not labeled LOGOFF ... you would have been very surprised ... -- Kris Buelens, IBM Belgium, VM customer support
Re: How to determine SYSRES
I have a local mod to CP that I originally got from Melinda Varian thru
VMSHARE, (that I have maintained thru all the versions/releases of VM
since), that adds an extra line to the reponse from QUERY CPLEVEL, (for
Class E users), that display the IPL, CheckPoint, and Warm Volsers and
Addresses. The output looks like this:
query cplevel
z/VM Version 5 Release 4.0, service level 1002 (64-bit)
Generated at 2010-09-22 15:15:16 EST
IPL at 2010-11-07 03:45:01 EST
SYSIPL=VMSY02(5B00), SYSCKP=VMSY01(5700), SYSWRM=VMSY02(5B00)
IBM could easily add this same info. The IPL Volume information is store
d
in HCPSYSCM and can be retrieved and displayed with a REXX Exec, (assumin
g
you have Class E or the equivalent CP Privilege class. Here is sample
Exec that does this. (This is not a fully roubust Exec with all the erro
r
checking/messages built-in. That is left as an exercise to the reader!
:-) It should work for most people.)
/**/
/*SYSRES EXEC */
/* Display the VM System IPL Volume Volser and Address from HCPSYSCM. */
/**/
SYSRES:
Address COMMAND
Parse Source . ctype ename etype emode .
Numeric Digits 12
eol = '15'x
asysvold = '60.6'/* Offset.Length of SYSRES Volser */
asysdvno = '730.2' /* Offset.Length of SYSRES Device Address */
locsyslc = 'LOCATE SYMBOL HCPSYSLC'
cpver= C2D(SubStr(Diag(00),11,1))
If cpver 4 Then
display = 'DISPLAY HLS'
Else
display = 'DISPLAY HS'
Parse Value Diagrc(08,locsyslc) With rc cc . . asyscm .
If rc \= 0 Then Exit rc
Parse Var asysvold offset '.' length .
dispcmd = display||D2X(X2D(asyscm) + X2D(offset))'.'length
Parse Value Diagrc(08,dispcmd) With rc cc . sysvold . (eol) .
If rc \= 0 Then Exit rc
sysvold = X2C(sysvold)
Parse Var asysdvno offset '.' length .
dispcmd = display||D2X(X2D(asyscm) + X2D(offset))'.'length
Parse Value Diagrc(08,dispcmd) With rc cc . sysdvno . (eol) .
If rc \= 0 Then Exit rc
Say 'SYSIPL='sysvold'('sysdvno')'
Exit 0
--
Dale R. Smith
Re: How to determine SYSRES
Are my posts not getting through, is the list not sending everything on the same day it is sent, or are members responding to old posts before reading all the way through the posts to see if there are already corrections? OK, so I had a bad day on 4 Nov 2010 when I posted that erroneous piece of code. Richard Schuh replied within minutes, pointing out a different problem. I responded by re-posting with Richard's fine suggestion in a slightly different way. Then on 9 Nov Alan Ackerman said what I had posted originally back on 4 Nov would not work for the reasons of the variable usage. That was true, but since a different solution had been posted late 4 Nov I did not elaborate on the variable problem back then. Earlier today 10 Nov, I explained why the use of the variable had seemed to work when I actually did test it before the erroneous post back early on 4 Nov. Hasn't this particular horse been beaten to death for long enough by now? Can we claim it dead and buried? The red blush on my cheeks faded over a week ago, c'mon already - give me a break! :-( Dale Smith's post on this subject is an altogether better solution anyway. One should expect that critical DASD volume information that was used during an IPL would be displayed as a documentary I-level message during IPL anyway. Some of this is already displayed, but a clean, concise display of the volsers and rdev of the sysres, checkpoint, warmstart, directory, parm disk, and the cylinder extents of each (even the sysres since it could be a 2nd level system) would be useful diagnostic information in the console log at a later date. Some of that is already available in various messages (displayed as they are discovered), but a single set of messages, perhaps in response to a command would be useful when things go bump in the dark. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Kris Buelens kris.buel...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/10/2010 01:37 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES This pipe below can never work as the author apparently expected, whatever the piper might implement 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Just think a bit. It is a REXX EXEC, so REXX is reading the source lines, and replaces all variables by their contents (or the uppercased variable name). In the case above: only 'sysres' is outside the quotes and replaced by whatever value it has at that time. All lines (but the last) end with a , so REXX joins it to the presvious string with 1 blnk in between. When REXX built this long string (from the 9 source lines), it sees it is not an assigment, not an IF, So it passes the string to the current address (those that know me a bit know that I tell it should better be COMMAND). So the CMS command processor starts the PIPE command, and it gets this long string to handle. PIPE simply cannot know that part of the PICK parameters ever were a runtime variable. And, there is even a second error: the second CP stage. It will first pass QUERY CPOWNED as command to CP, and then the records it finds in its input stream. In this case the 6th word of the last line of Q ALLOC. I guess your IPL volser is not labeled LOGOFF ... you would have been very surprised ... -- Kris Buelens, IBM Belgium, VM customer support 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.
Re: How to determine SYSRES
Most likely someone waking up from a long nap and looking at digests instead of e-mail. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, November 10, 2010 12:14 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES Are my posts not getting through, is the list not sending everything on the same day it is sent, or are members responding to old posts before reading all the way through the posts to see if there are already corrections? OK, so I had a bad day on 4 Nov 2010 when I posted that erroneous piece of code. Richard Schuh replied within minutes, pointing out a different problem. I responded by re-posting with Richard's fine suggestion in a slightly different way. Then on 9 Nov Alan Ackerman said what I had posted originally back on 4 Nov would not work for the reasons of the variable usage. That was true, but since a different solution had been posted late 4 Nov I did not elaborate on the variable problem back then. Earlier today 10 Nov, I explained why the use of the variable had seemed to work when I actually did test it before the erroneous post back early on 4 Nov. Hasn't this particular horse been beaten to death for long enough by now? Can we claim it dead and buried? The red blush on my cheeks faded over a week ago, c'mon already - give me a break! :-( Dale Smith's post on this subject is an altogether better solution anyway. One should expect that critical DASD volume information that was used during an IPL would be displayed as a documentary I-level message during IPL anyway. Some of this is already displayed, but a clean, concise display of the volsers and rdev of the sysres, checkpoint, warmstart, directory, parm disk, and the cylinder extents of each (even the sysres since it could be a 2nd level system) would be useful diagnostic information in the console log at a later date. Some of that is already available in various messages (displayed as they are discovered), but a single set of messages, perhaps in response to a command would be useful when things go bump in the dark. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Kris Buelens kris.buel...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/10/2010 01:37 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES This pipe below can never work as the author apparently expected, whatever the piper might implement 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Just think a bit. It is a REXX EXEC, so REXX is reading the source lines, and replaces all variables by their contents (or the uppercased variable name). In the case above: only 'sysres' is outside the quotes and replaced by whatever value it has at that time. All lines (but the last) end with a , so REXX joins it to the presvious string with 1 blnk in between. When REXX built this long string (from the 9 source lines), it sees it is not an assigment, not an IF, So it passes the string to the current address (those that know me a bit know that I tell it should better be COMMAND). So the CMS command processor starts the PIPE command, and it gets this long string to handle. PIPE simply cannot know that part of the PICK parameters ever were a runtime variable. And, there is even a second error: the second CP stage. It will first pass QUERY CPOWNED as command to CP, and then the records it finds in its input stream. In this case the 6th word of the last line of Q ALLOC. I guess your IPL volser is not labeled LOGOFF ... you would have been very surprised ... -- Kris Buelens, IBM Belgium, VM customer support 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.
Re: How to determine SYSRES
'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' This won't work. You cannot set the REXX variable and use it in the same pipe. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' 'PIPE CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Not tested. But then the first pipe wasn't tested either. Alan Ackerman
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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com. 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.
Re: How to determine SYSRES
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:ib...@listserv.uark.edu] On Behalf Of Heinz-Josef Glaser Sent: Thursday, November 04, 2010 12:58 AM To: IBMVM@LISTSERV.UARK.EDU 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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com. 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
Re: How to determine SYSRES
CP Query CPLOAD also tells you the volser of the IPL volume - on the first line of its 3-line display. But I like Richard's use of the last line returned from Q ALLOC ALL Unfortunately, it does not tell you the rdev. This is another good reason to never have DASD with duplicate volsers. The HMC had the rdev of the volume used to IPL.. but that was then and this is now - someone could have changed the HMC since then. Since there CAN be more than one DASD with the same volser, you want to find the one with that volser in the CPOWNED list. Extending Richard's suggestion, the following should give you the rdev of the volser actually IPLed, since there can't be a duplicate volser in the CPOWNED list and the sysres must be in the CPOWNED list. The following has to run from an EXEC since it uses a variable within the pipeline. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Schuh, Richard rsc...@visa.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/04/2010 10:32 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES 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:ib...@listserv.uark.edu] On Behalf Of Heinz-Josef Glaser Sent: Thursday, November 04, 2010 12:58 AM To: IBMVM@LISTSERV.UARK.EDU 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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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
Re: How to determine SYSRES
Mike, The Pipe-generated Q DASD volser does tell you the RDEV. If you want to quibble about the possibility of a second device that is FREE, then add a | locate / CP / Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Thursday, November 04, 2010 8:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD also tells you the volser of the IPL volume - on the first line of its 3-line display. But I like Richard's use of the last line returned from Q ALLOC ALL Unfortunately, it does not tell you the rdev. This is another good reason to never have DASD with duplicate volsers. The HMC had the rdev of the volume used to IPL.. but that was then and this is now - someone could have changed the HMC since then. Since there CAN be more than one DASD with the same volser, you want to find the one with that volser in the CPOWNED list. Extending Richard's suggestion, the following should give you the rdev of the volser actually IPLed, since there can't be a duplicate volser in the CPOWNED list and the sysres must be in the CPOWNED list. The following has to run from an EXEC since it uses a variable within the pipeline. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Schuh, Richard rsc...@visa.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/04/2010 10:32 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES 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:ib...@listserv.uark.edu] On Behalf Of Heinz-Josef Glaser Sent: Thursday, November 04, 2010 12:58 AM To: IBMVM@LISTSERV.UARK.EDU 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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU
Re: How to determine SYSRES
Hi, These commands can help? q cpd Label Userid Vdev Mode Stat Vol-ID Rdev Type StartLoc EndLoc MNTCF1 MAINT0CF1 A R/O CACVRS A100 CKD 39158 MNTCF2 MAINT0CF2 B R/O CACVRS A100 CKD 159278 MNTCF3 MAINT0CF3 C R/O CACVRS A100 CKD 279398 Maint; T=0.01/0.01 13:40:36 q cpload Module CPLOAD was loaded from minidisk on volume CACVRS at cylinder 39. Parm disk number 1 is on volume CACVRS, cylinders 39 through 158. Last start was a system IPL. Maint; T=0.01/0.01 13:40:40 __ Clovis | | From: | | --| |Heinz-Josef Glaser hjgla...@de.ibm.com | --| | | To:| | --| |IBMVM@LISTSERV.UARK.EDU | --| | | Date: | | --| |04/11/2010 05:59 | --| | | Subject: | | --| |Re: How to determine SYSRES | --| | | Sent by: | | --| |The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU | --| 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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep
Re: How to determine SYSRES
Richard, After further review you are right. Two volumes with the same volser cannot be attached to CP. Since the sysres is attached during IPL, it's the only CP-attached sysres volser that matters. To provide the complete answer, using your Pipe (which has the advantage of not needing to run under rexx): pipe cp q alloc all | take last | cons | spec /q dasd/ 1 w-1 nw | cp | pick w3 == /CP/ | cons Thanks! Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Schuh, Richard rsc...@visa.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/04/2010 11:04 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES Mike, The Pipe-generated Q DASD volser does tell you the RDEV. If you want to quibble about the possibility of a second device that is FREE, then add a | locate / CP / Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Thursday, November 04, 2010 8:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD also tells you the volser of the IPL volume - on the first line of its 3-line display. But I like Richard's use of the last line returned from Q ALLOC ALL Unfortunately, it does not tell you the rdev. This is another good reason to never have DASD with duplicate volsers. The HMC had the rdev of the volume used to IPL.. but that was then and this is now - someone could have changed the HMC since then. Since there CAN be more than one DASD with the same volser, you want to find the one with that volser in the CPOWNED list. Extending Richard's suggestion, the following should give you the rdev of the volser actually IPLed, since there can't be a duplicate volser in the CPOWNED list and the sysres must be in the CPOWNED list. The following has to run from an EXEC since it uses a variable within the pipeline. 'PIPE CP Q ALLOC ALL' , '| TAKE LAST 1' , '| CONSOLE' , '| SPECS W6 1' , '| VAR sysres' , '| CP QUERY CPOWNED' , '| PICK W2 == /'sysres'/' , '| SPECS W2-* 1' , '| CONSOLE' Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Schuh, Richard rsc...@visa.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/04/2010 10:32 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES 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:ib...@listserv.uark.edu] On Behalf Of Heinz-Josef Glaser Sent: Thursday, November 04, 2010 12:58 AM To: IBMVM@LISTSERV.UARK.EDU 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: hjgla...@de.ibm.com IBM Deutschland Infrastructure Technology Services GmbH Geschäftsführung: Ulrike Hetzel Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 727973 From: Mike Walter mike.wal...@hewitt.com To: IBMVM@LISTSERV.UARK.EDU Date: 27.09.10 19:27 Subject:Re: How to determine SYSRES Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 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 framaek...@ailife.com Sent by: The IBM z/VM Operating
How to determine SYSRES
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 privacy...@ailife.com.
Re: How to determine SYSRES
CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.comwrote: 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 privacy...@ailife.com. -- Gregg Reed No Plan, survives execution
Re: How to determine SYSRES
Try CP Q CPLOAD ... Scott Rohling On Mon, Sep 27, 2010 at 10:50 AM, Frank M. Ramaekers framaek...@ailife.comwrote: 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 privacy...@ailife.com.
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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com.
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: Or, simply: CP QUERY DASD volser Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com. 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.
Re: How to determine SYSRES
...and find the CP OWNED on in that list (if you have more than one): DASD 06F8 CP OWNED 540RES 103 DASD 9180 540RES DASD 9192 ATTACHED TO AILPROD 19E0 R/W 540RES Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Monday, September 27, 2010 12:27 PM To: IBMVM@LISTSERV.UARK.EDU 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: Or, simply: CP QUERY DASD volser Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com. 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. _ 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 privacy...@ailife.com.
Re: How to determine SYSRES
cp q dasd 540res DASD 0902 CP SYSTEM 540RES 0 DASD 0903 540RES , DASD 0907 540RES (We relabel IBM's installation volsers before going into production. But I clipped those three shown above just to show that CP Q DASD volser will show duplicate volsers, even those not in the CPOWNED list). Of course this list has recently had long discussions on the merits and demerits of having duplicate DASD volsers (especially IPL DASD). Your gun, your foot. :-) Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:56 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: How to determine SYSRES ...and find the CP OWNED on in that list (if you have more than one): DASD 06F8 CP OWNED 540RES 103 DASD 9180 540RES DASD 9192 ATTACHED TO AILPROD 19E0 R/W 540RES Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Monday, September 27, 2010 12:27 PM To: IBMVM@LISTSERV.UARK.EDU 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: Or, simply: CP QUERY DASD volser Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Frank M. Ramaekers framaek...@ailife.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/27/2010 12:20 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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:ib...@listserv.uark.edu] On Behalf Of Gregg Sent: Monday, September 27, 2010 11:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine SYSRES CP Query CPLOAD? On Mon, Sep 27, 2010 at 12:50 PM, Frank M. Ramaekers framaek...@ailife.com 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 privacy...@ailife.com. -- 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 privacy...@ailife.com. 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. _ 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
