Re: applying VM RSU maint - CPLEVEL
So, am I wrong thinking that I often saw a single PTF for GCS on the RSU, a PTF that brings the service level of GCS to the RSU level. After which I normally decide not to rebuild GCS... -- Sir Kris The Guide, IBM Belgium, VM customer support 2007/8/18, Dale R. Smith [EMAIL PROTECTED]: Phillip, you are getting confused between the individual VM component RSU service levels and the overall tape RSU level. The VM tape RSU contain s service for all of the components of VM and the RSU level is defined in the format: yynn. Where yy is the last two digits of the year and nn is the number of the tape for that year. In your case, RSU 0601 is/was the first RSU tape created in 2006. The VM components RSU service levels are in the format: rrnn. Where rr is the VM release number and nn is the service level number for that component. In your case, you are running z/VM 4.4.0, so your release number is 04 and your service level for CP is 03, the third RSU for CP that had any maintenance. An important thing to remember is that not all components have new service on a new RSU tape. For example, the GCS component rarel y has RSU maintenance, so while you might order a newer VM RSU tape, GCS might stay at the same internal service level. For example, lets say GCS is at service level 0401 on RSU tape 0601. There is a very good chance that on RSU tape 0701, GCS will still be at service level 0401, since i t probably will not have any maintenance applied. IIRC, the VMFPSU command will tell you what service level each of the components on the RSU tape i s at and if you need to apply maintenence for that component. Hope this information is helpful to you. -- Dale R. Smith On Fri, 17 Aug 2007 15:09:51 -0500, [EMAIL PROTECTED] wrote: Q CPLEVEL still reports 403 ... ? Also, I am still puzzled about whether this service is really on or not because NETSTAT LEVEL reports this: VM TCP/IP Netstat Level 440 IBM 2086; z/VM Version 4 Release 4.0, service level 0403 (64-bit), VM TCP/IP Lev el 440; RSU 0401 running TCPIP MODULE E1 dated 01/12/06 at 14:51 but the documentation that came with the RSU tapes says it should be LVL 0601 is there another step that i am missing? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL
Re: applying VM RSU maint - CPLEVEL
It's possible that it may have changed, I don't have access to a VM syste m right now and it's been a while since I've processed a RSU tape. :-) Certainly for VM components like AVS and TSAF that almost never have any new maintenance on RSU tapes, I believe that it applies. Since you can QUERY GCSLEVEL, IBM may have decided to include a PTF on every RSU tape that upgraded the GCS service level so that it would match CP's level on the RSU. It seems to me, (maybe it was VM/ESA), that I remember skipping several components, (including GCS), because there was no new maintenance for that component on the RSU tape. Of course, I could be losing what little mind I have left! :-) -- Dale R. Smith On Sun, 19 Aug 2007 12:59:58 +0200, Kris Buelens [EMAIL PROTECTED] wrote: So, am I wrong thinking that I often saw a single PTF for GCS on the RSU , a PTF that brings the service level of GCS to the RSU level. After which I normally decide not to rebuild GCS... -- Sir Kris The Guide, IBM Belgium, VM customer support
Re: applying VM RSU maint - CPLEVEL
Phillip, you are getting confused between the individual VM component RSU service levels and the overall tape RSU level. The VM tape RSU contain s service for all of the components of VM and the RSU level is defined in the format: yynn. Where yy is the last two digits of the year and nn is the number of the tape for that year. In your case, RSU 0601 is/was the first RSU tape created in 2006. The VM components RSU service levels are in the format: rrnn. Where rr is the VM release number and nn is the service level number for that component. In your case, you are running z/VM 4.4.0, so your release number is 04 and your service level for CP is 03, the third RSU for CP that had any maintenance. An important thing to remember is that not all components have new service on a new RSU tape. For example, the GCS component rarel y has RSU maintenance, so while you might order a newer VM RSU tape, GCS might stay at the same internal service level. For example, lets say GCS is at service level 0401 on RSU tape 0601. There is a very good chance that on RSU tape 0701, GCS will still be at service level 0401, since i t probably will not have any maintenance applied. IIRC, the VMFPSU command will tell you what service level each of the components on the RSU tape i s at and if you need to apply maintenence for that component. Hope this information is helpful to you. -- Dale R. Smith On Fri, 17 Aug 2007 15:09:51 -0500, [EMAIL PROTECTED] wrote: Q CPLEVEL still reports 403 ... ? Also, I am still puzzled about whether this service is really on or not because NETSTAT LEVEL reports this: VM TCP/IP Netstat Level 440 IBM 2086; z/VM Version 4 Release 4.0, service level 0403 (64-bit), VM TCP/IP Lev el 440; RSU 0401 running TCPIP MODULE E1 dated 01/12/06 at 14:51 but the documentation that came with the RSU tapes says it should be LVL 0601 is there another step that i am missing? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL
Re: applying VM RSU maint - CPLEVEL
Don't do the manual commands. Instead attach the tape to maint, define stor to at least 64 meg and enter the command SERVICE ALL. After the service has been applied, enter PUT2PROD ALL. These 2 commands do all necessary things. The single pretty complicated VMSES commands were necessary on older vm releases. ok - finally getting back to this. on my second level VM 4.4 I used the command SERVICE ALL 181 182 183 184 and PUT2PROD and let it run - it had one problem running out of space on CF1, so I had to delete an old CPLOAD module and rerun PUT2PROD which then finished successfully. I IPLed after PUT2PROD and VM came back up (this is second level.) Q CPLEVEL still reports 403 ... ? Also, I am still puzzled about whether this service is really on or not because NETSTAT LEVEL reports this: VM TCP/IP Netstat Level 440 IBM 2086; z/VM Version 4 Release 4.0, service level 0403 (64-bit), VM TCP/IP Lev el 440; RSU 0401 running TCPIP MODULE E1 dated 01/12/06 at 14:51 but the documentation that came with the RSU tapes says it should be LVL 0601 is there another step that i am missing? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL
Re: applying VM RSU maint - CPLEVEL
Don't do the manual commands. Instead attach the tape to maint, define stor to at least 64 meg and enter the command SERVICE ALL. After the service has been applied, enter PUT2PROD ALL. These 2 commands do all necessary things. The single pretty complicated VMSES commands were necessary on older vm releases. kind regards Franz Josef Pohlen [EMAIL PROTECTED] schrieb: List, i have RSU tapes to update my VM 4.4 system. following the service guide, i am doing the steps to prepare for service refresh. when i issue the VMFPSU ZVM CPSFS i get this output: vmfpsu zvm cpsfs VMFPSU2760I VMFPSU processing started VMFPSU1077I Comparing tables 4VMVMB40 VVT$PSU$ A and 4VMVMB40 VVTVM H VMFPSU1071I There are 0 PTFs on the Recommended Service Upgrade for PRODID 4VMVMB40%CP that are not currently applied. VMFPSU1074I There are no PTFs on the Recommended Service Upgrade to be applied for PRODID 4VMVMB40%CP. Continue with the next product. VMFPSU1070I Creating 4VMVMB40 PSUPLAN file at service level RSU-0401 for component CPSFS in PPF ZVM. VMFPSU2760I VMFPSU processing completed successfully this is puzzling since the RSU document says that z/VM CP 4.4.0 has level 0601 on it but a q cplevel says that i am at 0403: z/VM Version 4 Release 4.0, service level 0403 (64-bit) Generated at 01/12/06 14:50:57 CST how do i get to 0601 ? prg Phillip Gramly Systems Programmer Communications Data Group Champaign, IL
Re: applying VM RSU maint - CPLEVEL
On 8/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don't do the manual commands. Instead attach the tape to maint, define stor to at least 64 meg and enter the command SERVICE ALL. After the service has been applied, enter PUT2PROD ALL. These 2 commands do all necessary things. The single pretty complicated VMSES commands were necessary on older vm releases. kind regards Franz Josef Pohlen Be cautious with PUT2PROD ALL, this will take down your TCPIP stack. Be sure to do this during a down time, and try not to be logged on the a TCPIP session when you do this. -- Mark Pace Mainline Information Systems
Re: applying VM RSU maint - CPLEVEL
The native command VMFPSU seems right. Did you map the RSU, maybe the RSU is multivolume and the tape mounted was not the one with CP service. To map the RSU, use VMFINS INSTALL INFO (NOMEMO after which you'll find a VMFINS PRODLIST on yor A-disk. 2007/8/15, Mark Pace [EMAIL PROTECTED]: On 8/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Don't do the manual commands. Instead attach the tape to maint, define stor to at least 64 meg and enter the command SERVICE ALL. After the service has been applied, enter PUT2PROD ALL. These 2 commands do all necessary things. The single pretty complicated VMSES commands were necessary on older vm releases. kind regards Franz Josef Pohlen Be cautious with PUT2PROD ALL, this will take down your TCPIP stack. Be sure to do this during a down time, and try not to be logged on the a TCPIP session when you do this. -- Mark Pace Mainline Information Systems -- Kris Buelens, IBM Belgium, VM customer support
Re: applying VM RSU maint - CPLEVEL
Mark, you are right, I have forgotten to mention this. kind regards Franz Josef Pohlen Mark Pace schrieb: On 8/15/07, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Don't do the manual commands. Instead attach the tape to maint, define stor to at least 64 meg and enter the command SERVICE ALL. After the service has been applied, enter PUT2PROD ALL. These 2 commands do all necessary things. The single pretty complicated VMSES commands were necessary on older vm releases. kind regards Franz Josef Pohlen Be cautious with PUT2PROD ALL, this will take down your TCPIP stack. Be sure to do this during a down time, and try not to be logged on the a TCPIP session when you do this. -- Mark Pace Mainline Information Systems
Re: applying VM RSU maint - CPLEVEL
There is a PTF which will stop PUT2PROD from taking down the TCPIP stack.
