I just read through this string of appends (sorry I didn't see this soone r!) and there are a couple of things I'll point out for future reference, sin ce you have already arrived at the correct answer. Keeping these in mind ma y save you some time "the next time".
First, service levels are ONLY updated when you install an RSU. You can install as many PTFs you like, but without a new RSU, the service level w ill not change. And you can be sure that if you have installed an RSU the service levels of the serviced components will be updated, as I specifica lly test that. ;-) Second, George's SERVICE log (below) shows that he installed COR service (just a bunch of PTFs), not an RSU. Note these messages: >ST:VMFREC2760I VMFREC processing started >ST:VMFREC1852I Volume 1 of 1 of COR ENVELOPE created on 22 September 10 >ST:VMFREC2159I Loading COR 0922 to 2CC (C) >ST:VMFREC2159I Loading COR DOC to 2CC (C) You do not get any messages about loading COR files when you are installi ng an RSU. Also, the apply messages are a tip off, as the service on an RSU is pre-applied and pre-built: >ST:VMFAPP2105I VMFAPPLY processing completed successfully. >ST: The Apply list HCPVM contains 77 PTFs. >ST: 24 PTFs were already applied. >ST: 53 PTFs applied successfully. <=== should be 0 f or RSUs The apply messages for an RSU should always say that all the PTFs were already applied. Finally, the files we ship for RSUs are usually named RSUvrmn, e.g. RSU54 07. A SERVLINK file with a name that doesn't follow that convention is proba bly not an RSU. Carol Everitt, z/VM Development ========================= ========================= ========================= On Thu, 21 Oct 2010 11:27:07 -0400, George Henke/NYLIC <george_he...@newyorklife.com> wrote: >I don't think so. > >According to $VMFSRV $MSGLOG, 84 PTFs were applied. > >Here is my $VMFSRV $MSGLOG followed by the contents of MAINT 500 where I >pick up my input to SERVICE ALL, 9357956P. > >************************************************************************ >**** SERVICE USERID: MAINT **** >************************************************************************ >**** Date: 10/14/10 Time: 12:01:38 **** >************************************************************************ >ST:VMFSRV2195I SERVICE ALL 9357956P >ST:VMFSRV2760I SERVICE processing started >ST:VMFSUI2760I VMFSUFIN processing started >ST:VMFSUI2760I VMFSUFIN processing started for product 5VMCPR40%CP >ST:VMFSET2760I VMFSETUP processing started for SERVP2P CP >ST:VMFUTL2205I Minidisk³Directory Assignments: >ST: String Mode Stat Vdev Label/Directory >ST:VMFUTL2205I LOCALMOD E R/W 2C4 MNT2C4 >ST:VMFUTL2205I LOCALSAM F R/W 2C2 MNT2C2 >ST:VMFUTL2205I APPLY G R/W 2A6 MNT2A6 >ST:VMFUTL2205I H R/W 2A4 MNT2A4 >ST:VMFUTL2205I I R/W 2A2 MNT2A2 >ST:VMFUTL2205I DELTA J R/W 2D2 MNT2D2 >ST:VMFUTL2205I BUILD7 K R/W 493 MNT493 >ST:VMFUTL2205I BUILD6 L R/W 490 MNT490 >ST:VMFUTL2205I BUILD5 M R/W 19D MNT19D >ST:VMFUTL2205I BUILD9 N R/W 402 MNT402 >ST:VMFUTL2205I BASE2 O R/W 194 MNT194 >ST:VMFUTL2205I -------- A R/W 191 MNT191 >ST:VMFUTL2205I -------- B R/W 5E5 MNT5E5 >ST:VMFUTL2205I -------- C R/W 2CC MNT2CC >ST:VMFUTL2205I -------- D R/W 51D MNT51D >ST:VMFUTL2205I -------- S R/O 190 MNT190 >ST:VMFUTL2205I -------- T R/W 500 MNT500 >ST:VMFUTL2205I -------- Y/S R/O 19E MNT19E >ST:VMFSET2760I VMFSETUP processing completed successfully >ST:VMFMRD2760I VMFMRDSK processing started >ST:VMFMRD1937I Merge of APPLY started >ST:VMFMRD2063I Not merging APPLY 2A6 to 2A4 because 2A6 is empty >ST:VMFMRD1939I Merge of APPLY completed >ST:VMFMRD2760I VMFMRDSK processing completed successfully >ST:VMFREC2760I VMFREC processing started >ST:VMFREC1852I Volume 1 of 1 of COR ENVELOPE created on 22 September 10 >ST:VMFREC2159I Loading COR 0922 to 2CC (C) >ST:VMFREC2159I Loading COR DOC to 2CC (C) >ST:VMFREC2159I Loading SES MEMO to 2CC (C) >ST:VMFREC2160I There are 3 tape file(s) for 5VMCPR40 CP on volume 1 >ST:VMFREC2160I There are 3 tape file(s) for 6VMCPR10 CP on volume 1 >ST:VMFREC2760I VMFREC processing completed successfully >ST:VMFREC2760I VMFREC processing started >ST:VMFREC1852I Volume 1 of 1 of COR ENVELOPE created on 22 September 10 >ST:VMFREC1851I (1 of 3) VMFRCAXL processing AXLIST >ST:VMFRCX2159I Loading 4 part(s) to DELTA 2D2 (J) >ST:VMFRCX2193I Appending new Apply list HCPVM $APPLIST to the existing >ST: list on DELTA 2D2 (J) >ST:VMFRCX2193I Appending new Exclude list HCPVM $EXCLIST to the existing >ST: list on DELTA 2D2 (J) >ST:VMFREC1851I (2 of 3) VMFRCPTF processing PARTLST >ST:VMFRCP2159I Loading 56 part(s) to DELTA 2D2 (J) >ST:VMFREC1851I (3 of 3) VMFRCCOM processing DELTA >ST:VMFRCC2159I Loading 1249 part(s) to DELTA 2D2 (J) >ST:VMFREC2189I Updating Requisite table 5VMCPR40 SRVREQT, Description >ST: table 5VMCPR40 SRVDESCT and Receive Status table 5VMCPR40 >ST: SRVRECS with 56 new PTFs from COR 0922 >ST:VMFREC2760I VMFREC processing completed successfully >ST:VMFAPP2760I VMFAPPLY processing started >ST:VMFAPP2106I Apply list HCPVM contains 53 PTFs that need to be applied >ST: and 24 PTFs that are already applied >ST:VMFAPP2102I 10 of 53 PTFs processed >ST:VMFAPP2102I 20 of 53 PTFs processed >CK:VMFAPP2104I PTF UM32616 contains user information. Review the :UMEMO >CK: section in file UM32616 $PTFPART >ST:VMFAPP2102I 30 of 53 PTFs processed >ST:VMFAPP2102I 40 of 53 PTFs processed >ST:VMFAPP2102I 50 of 53 PTFs processed >ST:VMFAPP2102I 53 of 53 PTFs processed >ST:VMFAPP2105I VMFAPPLY processing completed successfully. >ST: The Apply list HCPVM contains 77 PTFs. >ST: 24 PTFs were already applied. >ST: 53 PTFs applied successfully. >ST: 0 PTFs were included. >ST: 0 PTFs were excluded or require excluded PTFs. >ST: 0 PTFs failed >ST:VMFAPP2103I The Software Inventory has been updated on the 2A6 (G) >ST: disk >ST:VMFBLD2760I VMFBLD processing started >ST:VMFSIP2453I Table 5VMCPR40 SRVAPPS H is a subset of table 5VMCPR40 >ST: SRVAPPS G >ST:VMFBLD1851I Reading build lists >ST:VMFBLD2182I Identifying new build requirements >ST:VMFBLD2182I New build requirements identified >ST:VMFBLD2180I There are 129 build requirements remaining >ST:VMFBLD2760I VMFBLD processing completed successfully >ST:VMFBLD2760I VMFBLD processing started >ST:VMFSIP2453I Table 5VMCPR40 SRVAPPS H is a subset of table 5VMCPR40 >ST: SRVAPPS G >ST:VMFBLD1851I Reading build lists >ST:VMFBLD2182I Identifying new build requirements >ST:VMFBLD2182I No new build requirements identified >ST:VMFBLD1851I (1 of 18) VMFBDCOM processing HCPBLSRC EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFBDC2219I Processing object =.$EXEC >ST:VMFBDC2219I Processing object =.$REXX >ST:VMFBDC2219I Processing object =.ASSEMBLE >ST:VMFBDC2219I Processing object =.COPY >ST:VMFBDC2219I Processing object =.PLXCOPY >ST:VMFBLD1851I (1 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (2 of 18) VMFBDMLB processing HCPGPI EXEC O, target is >ST: BUILD6 490 (L) >ST:VMFMLB2219I Processing object HCPCSIBK >ST:VMFMLB2219I Processing object HCPSGIOP >ST:VMFMLB2219I Processing object IRAQVS >ST:VMFMLB2219I Processing object VRDCBLOK >ST:VMFMLB2219I Processing object HCPMDLAT >ST:VMFMLB2220I Updating service history member for HCPGPI MACLIB >ST:VMFBLD1851I (2 of 18) VMFBDMLB completed with return code 0 >ST:VMFBLD1851I (3 of 18) VMFBDMLB processing HCPPSI EXEC O, target is >ST: BUILD6 490 (L) >ST:VMFMLB2219I Processing object HCPEQUAT >ST:VMFMLB2219I Processing object HCPPFXPG >ST:VMFMLB2219I Processing object HCPENTER >ST:VMFMLB2219I Processing object HCPLENTR >ST:VMFMLB2219I Processing object HCPPROLG >ST:VMFMLB2219I Processing object HCPRELST >ST:VMFMLB2220I Updating service history member for HCPPSI MACLIB >ST:VMFBLD1851I (3 of 18) VMFBDMLB completed with return code 0 >ST:VMFBLD1851I (4 of 18) VMFBDMLB processing HCPOM1 EXC33092 J, target i s >ST: BUILD7 493 (K) >ST:VMFMLB2219I Processing object CBITABLE >ST:VMFMLB2219I Processing object HCP28BIT >ST:VMFMLB2219I Processing object HCPACOBK >ST:VMFMLB2219I Processing object HCPASCBK >ST:VMFMLB2219I Processing object HCPBCPRG >ST:VMFMLB2219I Processing object HCPCLASS >ST:VMFMLB2219I Processing object HCPCRWBK >ST:VMFMLB2219I Processing object HCPCUIBK >ST:VMFMLB2219I Processing object HCPDEARG >ST:VMFMLB2219I Processing object HCPDGQBK >ST:VMFMLB2219I Processing object HCPDVTYP >ST:VMFMLB2219I Processing object HCPDXDA >ST:VMFMLB2219I Processing object HCPEDEV >ST:VMFMLB2219I Processing object HCPFCTBK >ST:VMFMLB2219I Processing object HCPFRMTE >ST:VMFMLB2219I Processing object HCPHPVBK >ST:VMFMLB2219I Processing object HCPIORBK >ST:VMFMLB2219I Processing object HCPLANBK >ST:VMFMLB2219I Processing object HCPLRARG >ST:VMFMLB2219I Processing object HCPMONSK >ST:VMFMLB2219I Processing object HCPMXRBK >ST:VMFMLB2219I Processing object HCPNIDBK >ST:VMFMLB2219I Processing object HCPPAGBK >ST:VMFMLB2219I Processing object HCPPCCBK >ST:VMFMLB2219I Processing object HCPPFCR >ST:VMFMLB2219I Processing object HCPRCCBK >ST:VMFMLB2219I Processing object HCPRDCBK >ST:VMFMLB2219I Processing object HCPRDEV >ST:VMFMLB2219I Processing object HCPRSMBK >ST:VMFMLB2219I Processing object HCPSCEQU >ST:VMFMLB2219I Processing object HCPSCFBK >ST:VMFMLB2219I Processing object HCPSFXBK >ST:VMFMLB2219I Processing object HCPSHABK >ST:VMFMLB2219I Processing object HCPSHOBK >ST:VMFMLB2219I Processing object HCPSLMBK >ST:VMFMLB2219I Processing object HCPSRMBK >ST:VMFMLB2219I Processing object HCPSRXBK >ST:VMFMLB2219I Processing object HCPSSHBK >ST:VMFMLB2219I Processing object HCPSSIBK >ST:VMFMLB2219I Processing object HCPSTFLE >ST:VMFMLB2219I Processing object HCPSWIBK >ST:VMFMLB2219I Processing object HCPSYSCM >ST:VMFMLB2219I Processing object HCPSZQBK >ST:VMFMLB2219I Processing object HCPTRXBK >ST:VMFMLB2219I Processing object HCPVDEV >ST:VMFMLB2219I Processing object HCPVMDBK >ST:VMFMLB2219I Processing object SDMMDR >ST:VMFMLB2219I Processing object SDMOBR >ST:VMFMLB2219I Processing object SVMREC >ST:VMFMLB2219I Processing object HCQCOMB >ST:VMFMLB2220I Updating service history member for HCPOM1 MACLIB >ST:VMFBLD1851I (4 of 18) VMFBDMLB completed with return code 0 >ST:VMFBLD1851I (5 of 18) VMFBDMLB processing HCPOM2 EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFMLB2219I Processing object BLDCPRLE >ST:VMFMLB2219I Processing object BLDCPWLE >ST:VMFMLB2219I Processing object HCPDGNDF >ST:VMFMLB2219I Processing object HCPDPCUT >ST:VMFMLB2219I Processing object HCPDVTBL >ST:VMFMLB2219I Processing object HCPENTR >ST:VMFMLB2219I Processing object HCPEXCP >ST:VMFMLB2219I Processing object HCPFNDPS >ST:VMFMLB2219I Processing object HCPGPAGE >ST:VMFMLB2219I Processing object HCPGTWKA >ST:VMFMLB2219I Processing object HCPINVOK >ST:VMFMLB2219I Processing object HCPIORCC >ST:VMFMLB2219I Processing object HCPMONMV >ST:VMFMLB2219I Processing object HCPPARSE >ST:VMFMLB2219I Processing object HCPRLWKA >ST:VMFMLB2219I Processing object HCPSI2GB >ST:VMFMLB2219I Processing object HCPSSKE >ST:VMFMLB2219I Processing object HCPTZRQ >ST:VMFMLB2219I Processing object RDEVICE >ST:VMFMLB2220I Updating service history member for HCPOM2 MACLIB >ST:VMFBLD1851I (5 of 18) VMFBDMLB completed with return code 0 >ST:VMFBLD1851I (6 of 18) HCPBDUTL processing HCPBLUTL EXEC O, target is >ST: BUILD6 490 (L) >ST:VMFBDU2219I Processing object IPL.DDRXA >ST:VMFBDU2219I Processing object IPL.SALIPL >ST:VMFBLD1851I (6 of 18) HCPBDUTL completed with return code 0 >ST:VMFBLD1851I (7 of 18) VMFBDCOM processing HCPBL490 EXC32616 J, target >ST: is BUILD6 490 (L) >ST:VMFBDC2219I Processing object C2461029.PDF >ST:VMFBDC2219I Processing object CPFMTXA.EXEC >ST:VMFBDC2219I Processing object DUMPLD2.EXEC >ST:VMFBDC2219I Processing object HCPDL2A.REXX >ST:VMFBDC2219I Processing object HCPDL2B.REXX >ST:VMFBDC2219I Processing object HCPDL2C.REXX >ST:VMFBDC2219I Processing object HCPDL2D.REXX >ST:VMFBDC2219I Processing object HCPDL2E.REXX >ST:VMFBDC2219I Processing object HCPDL2F.REXX >ST:VMFBLD1851I (7 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (8 of 18) VMFBDCOM processing HCPBLSAM EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFBDC2219I Processing object INSTPIPE.MODULE >ST:VMFBLD1851I (8 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (9 of 18) VMFBDCOM processing HCPBLRAS EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFBDC2219I Processing object =.VMDTDATA >ST:VMFBLD1851I (9 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (10 of 18) VMFBDCOM processing HCPBLHLP EXEC O, target is >ST: BUILD5 19D (M) >ST:VMFBDC2219I Processing object =.HELPCP >ST:VMFBDC2219I Processing object =.HELPCPQU >ST:VMFBDC2219I Processing object =.HELPCPSE >ST:VMFBDC2219I Processing object =.HELPMSG >ST:VMFBDC2219I Processing object =.HELPDEFI >ST:VMFBDC2219I Processing object =.HELPTRAC >ST:VMFBDC2219I Processing object =.HELPTRSO >ST:VMFBDC2219I Processing object =.HELPMENU >ST:VMFBDC2219I Processing object =.HELPABBR >ST:VMFBDC2219I Processing object =.HELPRDEV >ST:VMFBDC2219I Processing object =.HELPVMDU >ST:VMFBLD1851I (10 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (11 of 18) VMFBDCOM processing HCPBLUCE EXEC O, target is >ST: BUILD9 402 (N) >ST:VMFBDC2219I Processing object =.HELPCP >ST:VMFBDC2219I Processing object =.HELPCPQU >ST:VMFBDC2219I Processing object =.HELPCPSE >ST:VMFBDC2219I Processing object =.HELPMSG >ST:VMFBDC2219I Processing object =.HELPDEFI >ST:VMFBDC2219I Processing object =.HELPTRAC >ST:VMFBDC2219I Processing object =.HELPTRSO >ST:VMFBDC2219I Processing object =.HELPMENU >ST:VMFBDC2219I Processing object =.HELPABBR >ST:VMFBDC2219I Processing object =.HELPRDEV >ST:VMFBDC2219I Processing object =.HELPVMDU >ST:VMFBLD1851I (11 of 18) VMFBDCOM completed with return code 0 >ST:VMFBLD1851I (12 of 18) VMFBDMOD processing HCPMLOAD EXC32603 J, targe t >ST: is BUILD6 490 (L) >ST:VMFBDM2219I Processing object DDR.MODULE >ST:VMFBDM2219I Processing object HCPDL2G.MODULE >ST:VMFBDM2219I Processing object SALIPL.MODULE >ST:VMFBLD1851I (12 of 18) VMFBDMOD completed with return code 0 >ST:VMFBLD1851I (13 of 18) VMFBDMOD processing HCQMLOAD EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFBDM2219I Processing object HCQ540.MODULE >ST:VMFBLD1851I (13 of 18) VMFBDMOD completed with return code 0 >ST:VMFBLD1851I (14 of 18) VMFBDMOD processing HCPXLOAD EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFBDM2219I Processing object CPSYNCHK.MODULE >ST:VMFBLD1851I (14 of 18) VMFBDMOD completed with return code 0 >ST:VMFBLD1851I (15 of 18) VMFBDNUC processing CPLOAD EXC33151 J, target >ST: is BUILD7 493 (K) >ST:LOAD LIST: $$$TLL$$ EXEC A1 10/14/10 12:05 (MNT191) >ST: >ST:CSECT'S WITH SIZE GREATER THAN CONDITIONAL PAGE BOUNDARY >ST: >ST:@MAPSTRT 031E60 >ST: >ST:VMFBLD1851I (15 of 18) VMFBDNUC completed with return code 0 >ST:VMFBLD1851I (16 of 18) VMFBDSBR processing HCPSBHLP EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFSBR2000I Objects in segment build list HCPSBHLP EXEC have been >ST: built or deleted. Any segments using this build list will >ST: have to be rebuilt. >ST:VMFBLD1851I (16 of 18) VMFBDSBR completed with return code 0 >ST:VMFBLD1851I (17 of 18) VMFBDSBR processing HCPSBUCE EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFSBR2000I Objects in segment build list HCPSBUCE EXEC have been >ST: built or deleted. Any segments using this build list will >ST: have to be rebuilt. >ST:VMFBLD1851I (17 of 18) VMFBDSBR completed with return code 0 >ST:VMFBLD1851I (18 of 18) VMFBDSBR processing HCPSBAME EXEC O, target is >ST: BUILD7 493 (K) >ST:VMFSBR2000I Objects in segment build list HCPSBAME EXEC have been >ST: built or deleted. Any segments using this build list will >ST: have to be rebuilt. >ST:VMFBLD1851I (18 of 18) VMFBDSBR completed with return code 0 >ST:VMFBLD2180I There are 0 build requirements remaining >ST:VMFBLD2760I VMFBLD processing completed successfully >ST:VMFSET2760I VMFSETUP processing started for DETACH CP >ST:VMFSET2760I VMFSETUP processing completed successfully >ST:VMFSUI2760I VMFSUFIN processing completed successfully for product >ST: 5VMCPR40%CP >ST:VMFSUI2760I VMFSUFIN processing started for product 6VMCPR10%CP >ST:VMFSUI1200I No SERVICE record was found for product 6VMCPR10%CP >ST: in table VM SYSSUF >ST:VMFSUI1206I Service was not installed for product 6VMCPR10%CP >ST:VMFSUI2760I VMFSUFIN processing completed successfully for product >ST: 6VMCPR10%CP >ST:VMFSUI2760I VMFSUFIN processing completed successfully >ST:VMFSRV2760I SERVICE processing started for CP BUILD >ST:VMFSET2760I VMFSETUP processing started for SERVP2P CP >ST:VMFUTL2205I Minidisk³Directory Assignments: >ST: String Mode Stat Vdev Label/Directory >ST:VMFUTL2205I LOCALMOD E R/W 2C4 MNT2C4 >ST:VMFUTL2205I LOCALSAM F R/W 2C2 MNT2C2 >ST:VMFUTL2205I APPLY G R/W 2A6 MNT2A6 >ST:VMFUTL2205I H R/W 2A4 MNT2A4 >ST:VMFUTL2205I I R/W 2A2 MNT2A2 >ST:VMFUTL2205I DELTA J R/W 2D2 MNT2D2 >ST:VMFUTL2205I BUILD7 K R/W 493 MNT493 >ST:VMFUTL2205I BUILD6 L R/W 490 MNT490 >ST:VMFUTL2205I BUILD5 M R/W 19D MNT19D >ST:VMFUTL2205I BUILD9 N R/W 402 MNT402 >ST:VMFUTL2205I BASE2 O R/W 194 MNT194 >ST:VMFUTL2205I -------- A R/W 191 MNT191 >ST:VMFUTL2205I -------- B R/W 5E5 MNT5E5 >ST:VMFUTL2205I -------- C R/W 2CC MNT2CC >ST:VMFUTL2205I -------- D R/W 51D MNT51D >ST:VMFUTL2205I -------- S R/O 190 MNT190 >ST:VMFUTL2205I -------- Y/S R/O 19E MNT19E >ST:VMFSET2760I VMFSETUP processing completed successfully >ST:HCPZAC6730I CPRELEASE request for disk C completed. >ST:DMSACP723I X (CF1) R/O >ST:HCPZAC6732I CPACCESS request for MAINT's 0CF3 in mode C completed. >ST:HCPZAC6730I CPRELEASE request for disk B completed. >ST:HCPZAC6732I CPACCESS request for MAINT's 0CF2 in mode B completed. >ST:VMFSRV2760I SERVICE processing completed successfully for CP BUILD >ST:VMFSUT2760I VMFSUFTB processing started >ST:VMFSUT2760I VMFSUFTB processing completed successfully >ST:VMFSRV2760I SERVICE processing completed successfully > > >My files on my 500 mdisk are: > > 9357955P SERVLINK T1 V 4005 16757 13643 10/14/10 >11:15:41 > 9357955D SERVLINK T1 V 4005 155 136 10/14/10 >11:14:47 > 9348747D SERVLINK T1 V 4005 113 99 10/14/10 >11:14:26 > 9348747P SERVLINK T1 V 4005 15342 11749 10/14/10 >11:12:17 > 9348747P SHIPTFSS T1 F 1024 13790 3448 10/14/10 >11:06:14 > 9348747D SHIPDOCS T1 F 1024 59 15 10/14/10 >11:06:01 > 9357955P SHIPTFSS T1 F 1024 19074 4769 10/14/10 >11:05:14 > 9357955D SHIPDOCS T1 F 1024 87 22 10/14/10 >11:04:54 > 9357956P SERVLINK T1 V 4005 15342 11749 9/23/10 >17:45:33 > 9357956D SERVLINK T1 V 4005 113 99 9/23/10 >17:44:37 > 9357956P SHIPTFSS T1 F 1024 13790 3448 9/23/10 >17:34:59 > 9357956D SHIPDOCS T1 F 1024 59 15 9/23/10 >17:34:35 > 5402RSU1 SERVLINK T1 V 65535 1118126 29466 12/05/08 >10:40:44 > > > >Ray Waters <ray.wat...@opensolutions.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/21/2010 10:41 AM >Please respond to >The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > >To >IBMVM@LISTSERV.UARK.EDU >cc > >Subject >Re: RSU or PSU? > > > > > > >George, > >The only way I can see this happening is your input to the SERVICE exec >was the old RSU file, not 507RSU.. > >Ray Waters > >From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On >Behalf Of George Henke/NYLIC >Sent: Thursday, October 21, 2010 9:38 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: RSU or PSU? > > >No, yet cplevel shows it picked up the current Date/Time of the generate d >CPLOAD: > >q cmslevel >CMS Level 24, Service Level 802 >Ready; T=0.01/0.01 10:31:53 >netstat level >VM TCP/IP Netstat Level 540 TCP/IP Server Name: TCPIP > >IBM 2094; z/VM Version 5 Release 4.0, service level 0802 (64-bit), VM >TCP/IP Lev >el 540; RSU 0802 running TCPIP MODULE E2 dated 10/15/10 at 17:55 >TCP/IP Module Load Address: 00C1A000 >Ready; T=0.01/0.01 10:32:01 >q cplevel >z/VM Version 5 Release 4.0, service level 0802 (64-bit) >Generated at 10/15/10 17:54:37 EDT >IPL at 10/21/10 09:31:14 EDT >Ready; T=0.01/0.01 10:35:01 > > > >Ray Waters <ray.wat...@opensolutions.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/21/2010 10:28 AM > > >Please respond to >The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > > >To >IBMVM@LISTSERV.UARK.EDU >cc > >Subject >Re: RSU or PSU? > > > > > > > > > >George, > >Are the rest of your products now at the new service level? > >q cmslevel >CMS Level 24, Service Level 002 >Ready; T=0.01/0.01 09:31:01 > >netstat level >VM TCP/IP Netstat Level 540 TCP/IP Server Name: TCPIP > >IBM 2096; z/VM Version 5 Release 4.0, service level 1002 (64-bit), VM >TCP/IP Lev >el 540; RSU 1002 running TCPIP MODULE E2 dated 06/22/10 at 02:40 >TCP/IP Module Load Address: 00C1E000 >Ready; T=0.01/0.01 10:26:41 > >Ray Waters > >From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On >Behalf Of George Henke/NYLIC >Sent: Thursday, October 21, 2010 9:23 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: RSU or PSU? > > >tyvm, Ray, my HCPCPE AUXVM looks like this: > >00001 KRSU05HP SLU UMRSU05 * UPDATE CP SERVICE LVL TO '0802' >(AVAILABLE ON 0802 >RSU ON >00002 * LY). >00003 KRSU02HP SLU UMRSU05 * UPDATE CP SERVICE LVL TO '0801' >(AVAILABLE ON 0801 >RSU ON >00004 * LY). > >Clearly, I have done something wrong. > >I did not specify any PPF override for CP. > >Where would I look, which $MSGLOG, to see if there was an override. > >Ray Waters <ray.wat...@opensolutions.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/21/2010 09:20 AM > > > >Please respond to >The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > > > > >To >IBMVM@LISTSERV.UARK.EDU >cc > >Subject >Re: RSU or PSU? > > > > > > > > > > > > >George, > >Could you maybe have an override PPF for CP? > > HCPCPE AUXVM H1 F 80 14 2 6/22/10 >2:39:59 > HCPCPE TXTRSU20 J1 F 80 40 1 6/22/10 >1:51:06 > HCPCPE KRSU20HP J1 F 80 2 1 6/22/10 >1:50:59 > HCPCPE TXTRSU17 J1 F 80 37 1 1/24/10 >22:48:43 > HCPCPE KRSU17HP J1 F 80 2 1 1/24/10 >22:43:47 > HCPCPE TXTRSU14 J1 F 80 34 1 10/02/09 >14:50:07 > HCPCPE KRSU14HP J1 F 80 2 1 10/02/09 >14:50:04 > HCPCPE AUXVM I1 F 80 8 1 6/05/09 >18:43:03 > HCPCPE KRSU11HP J1 F 80 2 1 6/05/09 >18:13:51 > HCPCPE TXTRSU11 J1 F 80 31 1 6/05/09 >18:13:51 > HCPCPE TXTRSU08 J1 F 80 28 1 3/09/09 >22:03:13 > HCPCPE KRSU08HP J1 F 80 2 1 3/09/09 >22:03:12 > HCPCPE TXTRSU05 J1 F 80 25 1 11/25/08 >23:06:01 > HCPCPE KRSU05HP J1 F 80 2 1 11/25/08 >23:06:00 > HCPCPE TXTRSU02 J1 F 80 22 1 7/28/08 >21:47:41 > HCPCPE KRSU02HP J1 F 80 2 1 7/28/08 >21:47:40 > HCPCPE TEXT O1 F 80 23 1 6/10/08 >8:20:14 > >Here is what my 1002 CP HCPCPE AUXVM H (2A4) looks like: > >KRSU20HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '1002' (AVAILABLE ON >1002RSU ON >* LY). >KRSU17HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '1001' (AVAILABLE ON >1001RSU ON >* LY). >KRSU14HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '0903' (AVAILABLE ON >0903RSU ON >* LY). >KRSU11HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '0902' (AVAILABLE ON >0902RSU ON >* LY). >KRSU08HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '0901' (AVAILABLE ON >0901RSU ON >* LY). >KRSU05HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '0802' (AVAILABLE ON >0802RSU ON >* LY). >KRSU02HP SLU UMRSU20 * UPDATE CP SERVICE LVL TO '0801' (AVAILABLE ON >0801RSU ON >* LY). > >Ray Waters > >From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On >Behalf Of George Henke/NYLIC >Sent: Wednesday, October 20, 2010 4:18 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: RSU or PSU? > > >I notice my CPLOAD $NUCEXEC (See below) with a current Date/Time stamp >shows: > >00184 &1 &2 &3 HCPCPE TXTRSU05 > >Trying to find where HCPCPE TXTRSU05 is and what it contains. > > >I did 3 P2Ps so all 3 CF's have been updated: > > > CPLOAD MODULE M1 V 65535 149 2364 2010-10-15 >17:54:37 > CPLOAD MODULE N1 V 65535 149 2364 2010-10-15 >17:54:37 > CPLOLD MODULE M1 V 65535 149 2363 2010-10-14 >12:05:41 > CPLOLD MODULE N1 V 65535 149 2363 2010-10-14 >12:05:41 > CPLOAD MODULE O1 V 65535 149 2363 2010-10-14 >12:05:41 > CPLOLD MODULE O1 V 65535 149 2363 2010-10-14 >12:05:41 > >These CF's are from the Level 1 DDR of 540RES. >I have not changed them since. > >q mdisk cf1 loc >TargetID Tdev OwnerID Odev Dtype Vol-ID Rdev StartLoc Size >MAINT 0CF1 MAINT 0CF1 3390 54XRES 125B 39 120 >Ready; T=0.01/0.01 17:12:19 >q mdisk cf2 loc >TargetID Tdev OwnerID Odev Dtype Vol-ID Rdev StartLoc Size >MAINT 0CF2 MAINT 0CF2 3390 54XRES 125B 159 120 >Ready; T=0.01/0.01 17:12:23 >q mdisk cf3 loc >TargetID Tdev OwnerID Odev Dtype Vol-ID Rdev StartLoc Size >MAINT 0CF3 MAINT 0CF3 3390 54XRES 125B 279 120 > > > > > CPLOAD $NUCEXEC A1 F 80 Trunc=80 Size=1720 Line=180 Col =1 Alt=0 > > >00180 &1 &2 &3 HCPCNL TEXT >00181 &1 &2 &3 HCPCPA TEXT >00182 &1 &2 &3 HCPCPC TEXT >00183 &1 &2 &3 HCPCPD TEXT >00184 &1 &2 &3 HCPCPE TXTRSU05 >00185 &1 &2 &3 HCPCPG TXT32894 >00186 &1 &2 &3 HCPCPO TEXT >00187 &1 &2 &3 HCPCPV TEXT >00188 &1 &2 &3 HCPCPW TEXT >00189 &1 &2 &3 HCPCQE TEXT >00190 &1 &2 &3 HCPCQO TEXT >00191 &1 &2 &3 HCPCQT TEXT >00192 &1 &2 &3 HCPCRA TEXT >00193 &1 &2 &3 HCPCRC TEXT >00194 &1 &2 &3 HCPCRL TEXT >00195 &1 &2 &3 HCPCRM TEXT >00196 &1 &2 &3 HCPCRP TEXT >00197 &1 &2 &3 HCPCRR TEXT >00198 &1 &2 &3 HCPCRS TEXT >00199 &1 &2 &3 HCPCRT TEXT >00200 &1 &2 &3 HCPCSE TEXT > >Mike Walter <mike.wal...@hewitt.com> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >10/20/2010 05:05 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? > > > > > > > > > > > > > > >George, > >If you LINK and ACCESS each of your CF1, CF2, and CF3 disks on 54XRES, a nd > >issue: LISTFILE * MODULE * (ISO >What response do you get? If you see the CPLOAD MODULE with the same da te > >and time as the IPL message, but still SLU 0802 it may shed more light o n >this situation. > >And for each CF1, CF2, and CF3 disk, what do you get from: CP QUERY MDIS K >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 goo d. > > > >It does not seem that SES even tried to update the CPLEVEL on HCPCPE AUX VM > > > >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 o ld > >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 $MSGLO G, > >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 "stack ed > > >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 aler t >the sender by reply e-mail and then delete this message, including any >attachments. Any dissemination, distribution or other use of the content s >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-mai ls >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 . > > > > >NOTICE: >This e-mail is intended solely for the use of the individual to whom it is >addressed and may contain information that is privileged, confidential o r >otherwise exempt from disclosure. If the reader of this e-mail is not th e >intended recipient or the employee or agent responsible for delivering t he >message to the intended recipient, you are hereby notified that any >dissemination, distribution, or copying of this communication is strictl y >prohibited. If you have received this communication in error, please >immediately notify us by replying to the original message at the listed >email address. Thank You. > > >NOTICE: >This e-mail is intended solely for the use of the individual to whom it is >addressed and may contain information that is privileged, confidential o r >otherwise exempt from disclosure. If the reader of this e-mail is not th e >intended recipient or the employee or agent responsible for delivering t he >message to the intended recipient, you are hereby notified that any >dissemination, distribution, or copying of this communication is strictl y >prohibited. If you have received this communication in error, please >immediately notify us by replying to the original message at the listed >email address. Thank You. > >NOTICE: >This e-mail is intended solely for the use of the individual to whom it is >addressed and may contain information that is privileged, confidential o r >otherwise exempt from disclosure. If the reader of this e-mail is not th e >intended recipient or the employee or agent responsible for delivering t he >message to the intended recipient, you are hereby notified that any >dissemination, distribution, or copying of this communication is strictl y >prohibited. If you have received this communication in error, please >immediately notify us by replying to the original message at the listed >email address. Thank You. >
