z/VM V5: Looking to see if a particular APAR or PTF or RSU Level is applied?
Starting with z/VM V5.1.0 the STATUS option was added to the SERVICE command so that you could easily find the RSU level of or application of a particular PTF or APAR for a component or product.
Examples of using this command are:
An example to check the RSU level of CP: service cp status VMFSRV2760I SERVICE processing started VMFSRV1225I CP (5VMCPR10%CP) is at service level RSU-0402 VMFSRV2760I SERVICE processing completed successfully An example to check if a PTF has been applied to a component: service vmhcd status um31044 VMFSRV2760I SERVICE processing started VMFSRV1226I PTF UM31044 is applied to VMHCD (4VMHCD40%VMHCD) VMFSRV2760I SERVICE processing completed successfully An example to check if an APAR has been applied to a component: service osa status oa07669 VMFSRV2760I SERVICE processing started VMFSRV1226I APAR OA07669 (PTF UA10955) is applied to OSA (4OSASF40%OSA) VMFSRV2760I SERVICE processing completed successfully
The default for the STATUS option is to display the RSU level. To find out if this is the latest RSU for the product/component you can cross reference it with the RSU Content Information. The RSU content information will also show you what APARs and PTFs are included on each RSU level for the product.
It is possible that you could see an ESO or SDO level for a product that is not serviced by RSU. This means that the product is in the VM SYSSUF table (gets there by running VMFSUFTB...see Appendix A 'Setting up VMSES/E Licensed Products to use the SERVICE EXEC' in the Guide for Automated Installation and Service). An ESO level corresponds to a VM Licensed product that is in VMSES/E format and is part of the z/VM SDO. ESOs consists of PTFs that close for that product in that month. SDO level corresponds to a Semi-SES product in the SDO. So it is possible that you might see some other kind of level which may or may not match what is in an ADDSERV file.) Also note that the ADDSERV file will show if any other reach ahead service was applied to the product above the ESO level.
FYI...The VMSES/E PPF file that will get used by the SERVICE EXEC in order to set up disk accesses and find service is the PPF specified on the :INSPPF tag in the VM SYSSUF table. If you create PPF overrides and want the SERVICE EXEC to use your PPF file they you need to update the information in the VM SYSSUF file using the VMFUPDAT SYSSUF command.