Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-14 Thread Mike Walter
> Shimon, 
> Thanks for the corrections!  They have all been included in V1R1. Before 
sending V1R1 to the list,
...
Oops! 

Note to self: check the "To:" address very carefully before replying!  :-(

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.




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: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-08 Thread Schuh, Richard
If you override the console device on the SAPL screen at IPL time, it 
overrides, as in negates, the lists in the SYSTEM CONFIG, both 
Operator_Consoles and Emergency_Operator_Consoles. AFAIR, this is true whether 
you have the CONS= parameter in the default or override SAPL parameters. If you 
want the config file lists to remain active, you cannot use the SAPL to specify 
the console address. At least, that is how it works in 5.3. 

I hope that either 5.4 or the looming 6.1 corrects this design flaw. The one 
specified should, IMHO, be inserted at the head of the lists, rather than 
replacing them. The treatment of the IPL pack is a good example - it is 
inserted as the first CP_Owned volume if it is not in the list. 

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Shimon Lebowitz
> Sent: Saturday, September 05, 2009 11:21 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
> 
> Good work Mike!
> A few comments after a brief scan of your document are embedded below:
> 
> 
> >   6) When the "STAND ALONE PROGRAM LOADER:" screen
> >   appears, under the
> > line "IPL PARAMETERS" enter:  
> >
> >  cons=console_vdev
> >
> >
> > E.g. cons=0009
> >
> >
> > Then press F10 to IPL with that virtual console
> >   address used as your
> > OPERATOR console.
> >  
> >
> >   7) If you receive a Wait State 1010, it means that
> >   the SYSTEM CONFIG
> > file does not have the console_vdev you entered
> >   listed as one of the
> > "Operator_Consoles".  Change the console virtual
> >   address to match one
> > of those specified in SYSTEM CONFIG.  
> >
> > Nota bene: The SYSTEM CONFIG distributed by IBM
> >   for z/VM 5.4.0 had:  
> >
> > Operator_Consoles 0020 0021 0022 0023 0E20
> >   0E21 1020 ,  
> >   System_3270 System_Console  
> 
> AFAIR - the SAPL option CONS= acts as if the address 
> was added to that list. The reason for a 1010 would be
> forgetting the conmode 3270.
> 


Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-05 Thread Shimon Lebowitz
Good work Mike!
A few comments after a brief scan of your 
document are embedded below:


>   6) When the "STAND ALONE PROGRAM LOADER:" screen
>   appears, under the
> line "IPL PARAMETERS" enter:  
>
>  cons=console_vdev
>
>
> E.g. cons=0009
>
>
> Then press F10 to IPL with that virtual console
>   address used as your
> OPERATOR console.
>  
>
>   7) If you receive a Wait State 1010, it means that
>   the SYSTEM CONFIG
> file does not have the console_vdev you entered
>   listed as one of the
> "Operator_Consoles".  Change the console virtual
>   address to match one
> of those specified in SYSTEM CONFIG.  
>
> Nota bene: The SYSTEM CONFIG distributed by IBM
>   for z/VM 5.4.0 had:  
>
> Operator_Consoles 0020 0021 0022 0023 0E20
>   0E21 1020 ,  
>   System_3270 System_Console  

AFAIR - the SAPL option CONS= acts as if the address 
was added to that list. The reason for a 1010 would be
forgetting the conmode 3270.

>
>   9) Once the IPL is completed skip over the "1st
>   level procedure",below.
> jump to the "Post-IPL procedures:"
>
>
>   2nd level procedure:
>  
>   
>  
>
>   1) IPL from the HMC, using the LOAD ADDRESS of the
>   existing (example
> 540RES) sysres, and a LOADPARM of your console
>   real device (rdev)
> address.  

Umm... didn't you mean to title this section 
"1st level procedure" ?

>
>
> If you don't have a local non-SNA 3270 console
>   (perhaps an emulator)
> attached to this LPAR, you can use the Integrated
>   3270 Console on
> the HMC as the console address.  
>  
>
> In either case, include during the IPL on the HMC,
>   the LOADPARM  
> of either the local non-SNA 3270 terminal (or
>   emulator),
> or "System_3270" (maybe "System_Console", but I
>   never tried that).  

I believe the loadparm value needed to have SAPL come up 
on the integrated 3270 in the HMC is "SYSG".


>   Post-IPL procedures:
... ... 
>Enter: XEDIT SYSTEM CONFIG W  
>  
>
> 6) Change the old new to new volser.  
>
>Enter: TOP
>  
>Enter: C/540RES/VMR540/ * *
>

That should be "the old volser to new volser"

> 3) Edit the file, changing 540RES to VMR540 (just
>   an example).  
>Enter: XEDIT USER DIRECT C
>  
>
> 4) Change the old new to new volser.  
>
>Enter: TOP
>  
>Enter: C/540RES/VMR540/ * *
>

Same typo again.



> You do not need to shut the system down to change
>   the PAGE and  
> SPOOL DASD volsers.  CP only reads the volsers
>   when the DASD is  

*attached*... 

> to the system.  So they can be changed ahead of
>   time for the next IPL.  
>

Hmmm... you seem to have attached the same document *twice*, 
and the second version has this line which was missing 
in the first version:

> varied online, and the Allocation Bitmaps when the
>   DASD is ATTACHed  

So it goes where I commented "attached" above.

Thanks,
Shimon


Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-05 Thread Dave Jones

Sorry, Howard, I left off the ":-)" at the end of the note

DJ

Howard Rifkind wrote:

  Easy there big fella...

--- On *Fri, 9/4/09, Dave Jones //* wrote:


From: Dave Jones 
Subject: Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
To: IBMVM@LISTSERV.UARK.EDU
Date: Friday, September 4, 2009, 1:04 PM

EHowardit's at the bottom of Mike's note

Howard Rifkind wrote:
 >   How and where can I (we) retrieve you write up?
 >
 > --- On *Fri, 9/4/09, Mike Walter />/* wrote:
 >
 >
 >     From: Mike Walter >
     >     Subject: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
 > To: IBMVM@LISTSERV.UARK.EDU

 > Date: Friday, September 4, 2009, 12:55 PM
 >
 >
 > Howard,
 >
 > You already have your answer: Use CPFMTXA  to "Label" the output
 > volume.
 >
 > But just yesterday I completed a draft document describing how to
 > change a sysres (and page and SPOOL) volser in details sufficient
 > for most newbies. The change would let that relabeled sysres
IPL on
 > 1st of 2nd level.
 >  This document was created partly because I had recently
pointed out
 > on the list that IBM had no written documentation on how to
do that,
 > then David Boyes said that he'd add it to his "someday" list, I
 > received an off-list request for help with a problem that may
have
 > been caused by duplicate 540xxx volsers.  And then I had a
need to
 > change a sysres volser, too - perfect timing to test the process.
 >  The stars aligned, the clouds parted, and a document came out.
 >
 > The pasted document (file attachments do not make it to this
list)
 > is in a format suitable to be saved to a CMS file (ours is called
 > "RELABEL SYSRES") on a CMS minidisk or filespace.  That leads
to a
 > document which is not as pretty as one created with your
choice of
 > word processor products, but one which is always available on
your
 > VM system without any word processor software. 
 > This is V1R0, aimed at newbies, trying to give enough

information to
 > get the job done without so much information that it becomes
 > difficult to keep up to date.
 >
 > Mike Walter
 > Hewitt Associates
 > The opinions expressed herein are mine alone, not my employer's.
 >

-- Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544




--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544


Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-04 Thread Howard Rifkind
Easy there big fella...

--- On Fri, 9/4/09, Dave Jones  wrote:

From: Dave Jones 
Subject: Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
To: IBMVM@LISTSERV.UARK.EDU
Date: Friday, September 4, 2009, 1:04 PM

EHowardit's at the bottom of Mike's note

Howard Rifkind wrote:
>   How and where can I (we) retrieve you write up?
> 
> --- On *Fri, 9/4/09, Mike Walter //* wrote:
> 
> 
>     From: Mike Walter 
>     Subject: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
>     To: IBMVM@LISTSERV.UARK.EDU
>     Date: Friday, September 4, 2009, 12:55 PM
> 
> 
>     Howard,
> 
>     You already have your answer: Use CPFMTXA  to "Label" the output
>     volume.
> 
>     But just yesterday I completed a draft document describing how to
>     change a sysres (and page and SPOOL) volser in details sufficient
>     for most newbies. The change would let that relabeled sysres IPL on
>     1st of 2nd level.
>          This document was created partly because I had recently pointed out
>     on the list that IBM had no written documentation on how to do that,
>     then David Boyes said that he'd add it to his "someday" list, I
>     received an off-list request for help with a problem that may have
>     been caused by duplicate 540xxx volsers.  And then I had a need to
>     change a sysres volser, too - perfect timing to test the process.
>      The stars aligned, the clouds parted, and a document came out.
> 
>     The pasted document (file attachments do not make it to this list)
>     is in a format suitable to be saved to a CMS file (ours is called
>     "RELABEL SYSRES") on a CMS minidisk or filespace.  That leads to a
>     document which is not as pretty as one created with your choice of
>     word processor products, but one which is always available on your
>     VM system without any word processor software.  
>     This is V1R0, aimed at newbies, trying to give enough information to
>     get the job done without so much information that it becomes
>     difficult to keep up to date.
> 
>     Mike Walter
>     Hewitt Associates
>     The opinions expressed herein are mine alone, not my employer's.
> 

-- Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544



  

Re: "RELABEL SYSRES" was: Re: Backup RES Labeling Question

2009-09-04 Thread Dave Jones

EHowardit's at the bottom of Mike's note

Howard Rifkind wrote:

  How and where can I (we) retrieve you write up?

--- On *Fri, 9/4/09, Mike Walter //* wrote:


From: Mike Walter 
Subject: "RELABEL SYSRES" was: Re: Backup RES Labeling Question
To: IBMVM@LISTSERV.UARK.EDU
Date: Friday, September 4, 2009, 12:55 PM


Howard,

You already have your answer: Use CPFMTXA  to "Label" the output
volume.

But just yesterday I completed a draft document describing how to
change a sysres (and page and SPOOL) volser in details sufficient
for most newbies. The change would let that relabeled sysres IPL on
1st of 2nd level.
 
This document was created partly because I had recently pointed out

on the list that IBM had no written documentation on how to do that,
then David Boyes said that he'd add it to his "someday" list, I
received an off-list request for help with a problem that may have
been caused by duplicate 540xxx volsers.  And then I had a need to
change a sysres volser, too - perfect timing to test the process.
 The stars aligned, the clouds parted, and a document came out.

The pasted document (file attachments do not make it to this list)
is in a format suitable to be saved to a CMS file (ours is called
"RELABEL SYSRES") on a CMS minidisk or filespace.  That leads to a
document which is not as pretty as one created with your choice of
word processor products, but one which is always available on your
VM system without any word processor software.  


This is V1R0, aimed at newbies, trying to give enough information to
get the job done without so much information that it becomes
difficult to keep up to date.

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.



--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544