Servicing Your Product

Service is a process that includes the following:
vmx32besp
Service is a process that includes the following:
  • Correcting a software problem
  • Circumventing a software problem
  • Adding function to a previously installed product
There are two basic types of service,
corrective
and
preventive
.
  • Corrective service is intended to resolve a specific software defect. A corrective service envelope contains a specific Program Temporary Fix (PTF) for one specific problem, plus any requisite fixes.
  • Preventive service is a collection of fixes as of a certain calendar date. It might contain all published PTFs, or some subset of them (for example, high impact fixes). The procedure for processing either type of service is identical, so the procedures below work for either type. In a collection of fixes, VMSES will ignore any fixes in the collection which have already been applied to your product materials.
For more information about VMSES Service Process, see the chapter "Using VMSES/E for Service" in the IBM
VMSES/E Introduction and Reference
manual.
Servicing VMSES/E components consists of the following steps; each step is described in detail in later sections.
  1. Prepare to Receive Service
    Load informational files from the PTF envelope file. Establish the search order for working with the product code. Optionally, you may merge the alternate APPLY disk to the production APPLY disk to isolate the new service you are about to receive.
  2. Receive the Service
    Load the product service from the PTF envelope file, using the VMSES VMFREC command.
  3. Apply the Service
    Define a new service level by applying the PTFs. The VMSES VMFAPPLY command validates the loaded PTFs before adding them to the maintenance level.
  4. Update the Build Status Table
    Use the VMSES VMFBLD command with the STATUS option to update the Build Status Table.
  5. Build Serviced Objects
    Use the VMSES VMFBLD command with the SERVICED option to build the serviced objects.
  6. Deploy Service to Production
    Use the VMDEPLOY command to copy the serviced code to the production disks.
Step 1. Prepare to Receive Service 
The
ppfname
used throughout these servicing instructions is ZVMX032A, which assumes that you are using the PPF supplied for this release of the product. If you have created your own PPF override file for the product, you must use your override file name instead of ZVMX032A. The
ppfname
must be used throughout the rest of this procedure, unless otherwise stated.
3topdisc
Step 1.1. Prepare the VMANAGER Administration User ID
Log on to VMANAGER.
The PROFILE EXEC establishes the correct search order for applying service.
It is a good practice to create a backup copy of the current product disks or SFS directories, which contain product materials. Save this backup until you have completed installing the service and you are confident that the service runs correctly.
Make the service envelope (SERVLINK) file available on the A-disk or any minidisk or SFS directory accessed as file mode C.
Set up the installed product materials access search order by issuing the VMFSETUP command as follows:
VMFSETUP 
ppfname component
 ( LINK
  • ppfname
    Specifies the value of the PPF filename. In most cases, use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, use the file name of your PPF override file.
  • component
    Specifies the name of the component. Use the name VMSECURE for installing on minidisks. Use the name VMSECURESFS for installing on SFS.
The steps in the service application procedure assume that the product search order has been established before you begin the procedure. The search order is lost if disks are released manually, if CMS is restarted by the IPL command, or if you logoff and logon again. If the search order is lost at any time, re-establish it by issuing the VMFSETUP command before proceeding to the next VMFREC, VMFMRDSK, VMFAPPLY, or VMFBLD command.
Step 1.2. Receive the Documentation
Load from an envelope file by issuing the following command:
VMFREC INFO ( ENV 
envfilename
  • INFO
    Specifies that the documentation, including the product service memo, is loaded to the A-disk.
  • ENV
    Indicates the value following this option keyword, which is the name of the envelope file for the service being applied. The CMS file type of this file is SERVLINK.
Check the receive message log ($VMFREC $MSGLOG) for warning and error messages. Use the PF5 key to show all status messages which identify the products with service.
VMFVIEW RECEIVE
Read the product memo file ZVMX032A
MEMO for the latest information about this service.
Step 1.3. (Optional) Merge the Alternate APPLY Disk
This step is optional. The APPLY string contains the files that define service levels. Before receiving a new service, you may choose to consolidate service levels by merging previously processed service from the alternate APPLY disk to the production APPLY, where it is permanently stored. The merge operation provides a clean alternate APPLY disk for new service. Issue the VMFMRDSK command as follows:
VMFMRDSK 
ppfname component
APPLY
  • ppfname
    Specifies the value of the PPF filename. In most cases, use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, use the file name of your PPF override file.
  • component
    Specifies the name of the component. Use the name VMSECURE for installing on minidisks. Use the name VMSECURESFS for installing on SFS.
If you merged your APPLY disks, review the merge message log ($VMFMRD $MSGLOG). If necessary, correct any problems before proceeding.
VMFVIEW MRD
For more information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.
Step 2. Receive the Service
Receive the service for each service electronic envelope you want to process. If you have multiple service envelopes to process, you may receive all of the service before applying and building it. Enter the following command:
VMFREC PPF 
ppfname
 
component
 ( ENV 
envfilename
  • PPF
    Indicates the values following this keyword, and the values are the Product Parameter File (PPF) file name, followed by the name of a component defined in the PPF.
    In most cases, to specify the 
    ppfname
     use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, as described below and in the appendix Create Product Parameter File (PPF) Override, you specify the file name of your PPF override file.
    For the 
    component 
    value, use VMSECURE for installing on minidisks. Specify VMSECURESFS for installing on Shared File System directories.
  • ENV
    Indicates the value following this option keyword, which is the name of the envelope file for the service being applied. The CMS file type of this file is SERVLINK.
Review the receive message log ($VMFREC $MSGLOG). If necessary, correct any problems before proceeding.
VMFVIEW RECEIVE
For more information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.
Step 3. Apply the Service
Apply all received service. This command applies the service that you just received. The version vector table (VVT) is updated with all serviced parts and all necessary AUX files are generated on the alternate APPLY disk. You must review the VMFAPPLY message log if you receive a return code (RC) of a 4, as this may indicate that you have local modifications that need to be reworked.
To apply the service, enter the following command:
VMFAPPLY PPF 
ppfname
 
component
  • PPF
    Indicates the values following this keyword, and the values are the Product Parameter File (PPF) file name, followed by the name of a component defined in the PPF.
    In most cases, to specify the 
    ppfname
     use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, as described below and in the appendix Create Product Parameter File (PPF) Override, you specify the file name of your PPF override file.
    For the 
    component 
    value, use VMSECURE for installing on minidisks. Specify VMSECURESFS for installing on Shared File System directories.
Review the receive message log ($VMFREC $MSGLOG). If necessary, correct any problems before proceeding.
VMFVIEW APPLY
For information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.
Step 4. Update the Build Status Table
To update the build status table, enter the following command:
VMFBLD PPF 
ppfname
 
component
( STATUS
  • PPF
    Indicates the values following this keyword, and the values are the Product Parameter File (PPF) file name, followed by the name of a component defined in the PPF.
    In most cases, to specify the 
    ppfname
     use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, as described below and in the appendix Create Product Parameter File (PPF) Override, you specify the file name of your PPF override file.
    For the 
    component 
    value, use VMSECURE for installing on minidisks. Specify VMSECURESFS for installing on Shared File System directories.
 
VMFBLD2185R The following source product parameter files have been serviced: VMFBLD2185R ppfname $PPF VMFBLD2185R When source product parameter files are serviced, all product parameter files built from them must be recompiled using VMFPPF before VMFBLD can be run. VMFBLD2185R Enter zero (0) to have the latest levels of the source product parameter files copied to your A-disk and exit VMFBLD so you can recompile your product parameter files with VMFPPF Enter one (1) to continue only if you have already recompiled your product parameter files with VMFPPF
You
must
Enter ZERO (0), then press ENTER to have the latest levels of the source product parameter files copied to your A-Disk. VMFBLD will complete with RC=500. Then issue the following sequence of commands:
Recompile the
product base PPF file
:
VMFPPF 
ppfname
 *
If you use a PPF override file
,
after
recompiling the product base PPF file, then you must also recompile your product override PPF file:
VMFPPF 
ppf_override
 *
Reissue this VMFBLD command
.
You will receive the VMFBLD2185R messages again
. However, this time
Enter ONE (1)
to continue; you Enter ONE (1) becuase you just completed recompiling your product parameter file(s) with VMFPPF:
VMFBLD PPF 
ppfname
 
component 
( STATUS
Use VMFVIEW to review the build status messages.
VMFVIEW BUILD
Step 5. Build Serviced Objects
To build the serviced objects, enter the following command:
VMFBLD PPF 
ppfname
 
component
( SERVICED
  • PPF
    Indicates the values following this keyword, and the values are the Product Parameter File (PPF) file name, followed by the name of a component defined in the PPF.
    In most cases, to specify the 
    ppfname
     use the name of the supplied PPF file for this release, which is ZVMX032A. If you have created a PPF Override file, as described below and in the appendix Create Product Parameter File (PPF) Override, you specify the file name of your PPF override file.
    For the 
    component 
    value, use VMSECURE for installing on minidisks. Specify VMSECURESFS for installing on Shared File System directories.
Review the build message log ($VMFBLD $MSGLOG). If necessary, correct any problems before proceeding.
VMFVIEW BUILD
For information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.
Step 6. Deploy Service to Production
To deploy serviced product materials to production, enter the following VMDEPLOY command to copy serviced product materials to the runtime disk space.
VMDEPLOY 
name
 [PRIMARY|ALTERNATE]
  • name
    Specifies the user ID of the product server machine being deployed.
  • PRIMARY 
    Copy to the product primary disk space. This value results in overwriting the deployed Product Materials from the product release or version with the new serviced materials. We suggest that you backup all deployed minidisks before using this operand. Restoring the backup could be used to remove a level of service, if needed.
  • ALTERNATE
    Copy to the alternate disk space location. This value retains your older product material deployment. Setting the Runtime Environment tag value in the VMSERVER NAMES file to PRIMARY or ALTERNATE causes that set of deployed disks to be used when the product server is next started. Testing the new service, or backing out to the old level just requires setting a new value for Runtime Environment and restarting the server.