Yes, #2 is where I'm coming from (my last experience with VM service).
So, yes this is SLICK!

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  76710
        
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Thursday, September 03, 2009 10:41 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: RSU0902 problem with SERVICE

Ah... that's a LOT clearer, thanks.

1) Did you run PUT2PROD before IPLing?  Running SERVICE only gets the 
files to the BUILD disks, not onto the PROD disks.

2) In the good old days, before SERVICE and PUT2PROD, VM sysprogs had to

manually execute myriad VMSES/E commands, and manually check the results

of each before going on to the next step.  There were LOTS of steps, and

it required doing them for each individual VM component (CP, CMS, GCS, 
etc.) - again checking the results of every command for every component.

An experienced VM sysprog could apply an RSU with service to every 
component in a couple days.  But it was very, VERY easy to miss an error

message - continuing with the steps (many,MANY steps and it was VERY
easy 
to miss one of those, too!) until after the IPL, one or more components 
failed due to the missed error message(s).

Last fall when in the z/BM 540 ESP, and sitting in the back of a CAVMEN 
session, I received an RSU, ran SERVICE and PUT2PROD, and IPLed the 2nd 
level build system in about 30 minutes -- without looking up any
commands. 
 Before SERVICE and PUT2PROD that would have at least a while taken more

or more tedious days, and would not have been possible without carefully

following the manuals with their gazillions (OK, that's a slight 
exaggeration) of manually entered commands and manually checked results.

No problem (now), be happy!  Count your blessings; SERVICE and PUT2PROD 
are certainly two of them!

VMSES/E usurping the console log *IS* irritating, but it does not delete

it.  It just places it in the appropriate $MSGLOG along with the other 
related messages so there is only ONE place to look for each VMSES/E 
process.  No hunting the $MSGLOG for CMS messages and (if you can find
the 
right one) the SPOOLed console log for other related messages.

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/03/2009 10:24 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: RSU0902 problem with SERVICE






Like I said originally, I did the SERVICE with the RSU0902 yesterday,
then this morning I did a 'SERVICE CP STATUS'.  Now VMFVIEW SERVICE
shows only:

------------------------------------------------------------------------
--
    ===> VMFVIEW - Message Log Browse of $VMFSRV  $MSGLOG  A1 <=== 
You are viewing ALL messages from the LAST run. 
Number of messages shown = 6 <===> Number of messages not shown = 0 
************************************************************************
****             SERVICE               USERID: MAINT                ****
************************************************************************
****            Date: 09/03/09            Time: 07:25:28            ****
************************************************************************
ST:VMFSRV2195I SERVICE CP STATUS 
ST:VMFSRV2760I SERVICE processing started 
ST:VMFSRV1225I CP (5VMCPR40%CP) status: 
ST:VMFSRV1225I    Service Level     RSU-0902 
ST:VMFSRV1225I    Production Level  RSU-0801 
ST:VMFSRV2760I SERVICE processing completed successfully 
* * * End of File * * * 
  :
  :
------------------------------------------------------------------------
IMHO, I don't see why this was logged.


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  76710
 

 


-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Thursday, September 03, 2009 9:58 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: RSU0902 problem with SERVICE

> but the "VMFVIEW /n" only the STATUS process. 

Without "eyes on" your terminal, that post is rather terse.  What do you

mean by "only STATUS process"?

Did you try pressing the PF2 ("All") key, and then scroll (PF7 and PF8)
up 
and down the results?

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/03/2009 09:28 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: RSU0902 problem with SERVICE






Cool, I can see it in there, but the "VMFVIEW /n" only the STATUS
process.   :(


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  76710
 
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Thursday, September 03, 2009 9:06 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: RSU0902 problem with SERVICE

For now, enter: FILELIST  *  $MSGLOG  *
Look through the results with BROWSE, XEDIT (but do NOT change
anything!), 
or VMFVIEW (from the FILELIST prefix area, enter: VMFVIEW /n).

From now on, after VMSES/E commands complete, always enter: FILELIST * *
* 
(TODAY
(the "TODAY" option is one of my favorite, often overlooked commands)
then look through the recently updated files.  It will give you a better

idea of what files VMSES/E just updated, and a little better feel for
what 
all those mysterious commands do in general.

When using VMFVIEW, carefully examine all the possible PFkeys, they add
a 
lot of value.

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/03/2009 08:46 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
RSU0902 problem with SERVICE






Guess I messed up.  I ran the SERVICE against the RSU0902 and it ran to
completion (with return code 4).  I closed to console to preserve the
entire session (especially since the set TERM MORE 0 0).  This was
yesterday.

Today, I came in and started reviewing the manuals and found this nifty
command SERVICE compid STATUS.  So, I issued that.  Next, I went back to
review the SERVICE from the day before, but unfortunately the VMFVIEW
SERVICE only showed the results from the SERVICE/STATUS command.

Then I thought, at least I have my CONSOLE log.  Unfortunately that was
not to be found.   Does SERVICE turn this off?

So, I have no way to review what transpired yesterday (well, that I know
of).  I know there were some warning messages that I wanted to
investigate.

Thoughts?  Ideas?

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  76710
 

_____________________________________________________

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.






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.






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.

Reply via email to