George,

If you LINK and ACCESS each of your CF1, CF2, and CF3 disks on 54XRES, and 
issue: LISTFILE * MODULE * (ISO
What response do you get?  If you see the CPLOAD MODULE with the same date 
and time as the IPL message, but still SLU 0802 it may shed more light on 
this situation.

And for each CF1, CF2, and CF3 disk, what do you get from: CP QUERY MDISK 
CFx LOCation

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



"George Henke/NYLIC" <george_he...@newyorklife.com> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
10/20/2010 03:54 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: RSU or PSU?







Thank you very much, Alan. 

I really did everything by the book, RC=0 on everything including the 
PSPs. 

I just do not understand why CP still says 0802 for my CPLEVEL. 

I looked at $VMFP2P $MSGLOG and $VMFSRV $MSGLOG and everything looks good. 


It does not seem that SES even tried to update the CPLEVEL on HCPCPE AUXVM 


The IPL shows the old Service Level but the current date/time stamp. 

                19:09:15 z/VM  V5 R4.0  SERVICE LEVEL 0802 (64-BIT)        

        19:09:16 SYSTEM NUCLEUS CREATED ON 2010-10-14 AT 12:05:41, LOADED 
FROM 54XRES 

It is the same whether I IPL from CF1 or CF2, but CF3 shows the 2 year old 
version. 

I did run Service and P2P 3 times once for the RSU, once for the COR for 
the 3 z196 compatibility APARs, and finally once again for the PSPs. 

I did IPL between the 3 Service sessions. 

SERVICE ALL STATUS shows these APARs were applied, built, and PUT2PROD. 

service all status vm64798   
VMFSRV2760I SERVICE processing started 
VMFSRV1226I CP (5VMCPR40%CP) APAR VM64798 (PTF UM33151) status:       
VMFSRV1226I    RECEIVED  10/14/10 12:02:44                           
VMFSRV1226I    APPLIED   10/14/10 12:03:24  
VMFSRV1226I    BUILT     10/14/10 12:06:15 
VMFSRV1226I    PUT2PROD  10/14/10 12:23:28 
VMFSRV2760I SERVICE processing completed successfully                 
                                  
service all status vm64879   
VMFSRV2760I SERVICE processing started 
VMFSRV1226I CP (5VMCPR40%CP) APAR VM64879 (PTF UM33171) status:       
VMFSRV1226I    RECEIVED  10/14/10 12:02:44                           
VMFSRV1226I    APPLIED   10/14/10 12:03:24                           
VMFSRV1226I    BUILT     10/14/10 12:06:15 
VMFSRV1226I    PUT2PROD  10/14/10 12:23:28 
VMFSRV2760I SERVICE processing completed successfully 
                
service all status vm64881    
VMFSRV2760I SERVICE processing started 
VMFSRV1226I CP (5VMCPR40%CP) APAR VM64881 (PTF UM33183) status:   
VMFSRV1226I    RECEIVED  10/14/10 12:02:44                       
VMFSRV1226I    APPLIED   10/14/10 12:03:24 
VMFSRV1226I    BUILT     10/14/10 12:06:15 
VMFSRV1226I    PUT2PROD  10/14/10 12:23:28 
VMFSRV2760I SERVICE processing completed successfully             
                                                                  

But that is no assurance that I am running with them. 

PTFs did get applied and I do see the correct SES envelop fn's in $MSGLOG, 
so I know I did not just rerun with the old SERVLINK. 
Is there anyway of mapping CPLOAD so I can be sure that I will really be 
IPLing with these APARs when the z196 arrives?. 



Alan Altmark <alan_altm...@us.ibm.com> 
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 
10/20/2010 04:37 PM 

Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>


To
IBMVM@LISTSERV.UARK.EDU 
cc

Subject
Re: RSU or PSU?








On Wednesday, 10/20/2010 at 02:06 EDT, George Henke/NYLIC 
<george_he...@newyorklife.com> wrote:

> The Service Guide talks of a PSU (Product Service Upgrade), not an RSU. 
> 
> Was this a PSU and not an RSU? 
> 
> Then why does SHOPZ call it an RSU, even Stacked 5407 RSU?

"PSU" is a *procedure* that you use to apply the Recommended Service 
Upgrade (RSU).  See Chapter 2 of the Service Guide.  (IMO, it doesn't 
deserve an abbreviation.)

The term "stacked RSU" is historical.  Back in VM/ESA Version 2 the RSU 
for each component (CP, CMS, TCP/IP, etc.) was orderable separately in 
addition to a "stacked" RSU that contained all of the most recent 
component RSUs.  In z/VM V3, individual component RSUs were dropped, but 
the "stacked" moniker persisted.

My friends in Development will take it under advisement that perhaps it is 

time to retire the term "stacked" as it adds no value.  "RSU" and "stacked 

RSU" are the same thing now days.   As a reminder, 
http://www.vm.ibm.com/service/rsu/ is your friend.

Alan Altmark

z/VM and Linux on System z Consultant
IBM System Lab Services and Training 
ibm.com/systems/services/labservices 
office: 607.429.3323
alan_altm...@us.ibm.com
IBM Endicott





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. 

Reply via email to