CA Mainframe VM Product Manager - 1.2 : Servicing Your Product

This section provides information on how to perform service updates using VMSES/E.

Contents

VMSES/E Service Overview

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 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.
Icon
Note: 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

Follow these steps to prepare to receive service.

Icon
Note: The ppfname used throughout these servicing instructions is ZVMN012A, which assumes that you are using the PPF supplied for CA Mainframe VM Product Manager. If you have created your own PPF override file for the product, you must use your override file name instead of ZVMN012A. The ppfname must be used throughout the rest of this procedure, unless otherwise stated.

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 CA Mainframe VM Product Manager 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.

Setup 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 ZVMN012A. 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 MANAGER for installing on minidisks. Use the name MANAGERSFS for installing on SFS.
Icon
Important! 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 ZVMN012A 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 ZVMN012A. 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 MANAGER for installing on minidisks. Use the name MANAGERSFS 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
Icon
Note: For more information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.

Back to Top of Step 1

Back to Top of Page

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 ZVMN012A. 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 MANAGER for installing on minidisks. Specify MANAGERSFS 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
Icon
Note: For more information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.

Back to Top of Page

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 ZVMN012A. 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 MANAGER for installing on minidisks. Specify MANAGERSFS for installing on Shared File System directories.

Review the receive message log ($VMFREC $MSGLOG). If necessary, correct any problems before proceeding.

VMFVIEW APPLY
Icon
Note: For information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.

Back to Top of Page

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 ZVMN012A. 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 MANAGER for installing on minidisks. Specify MANAGERSFS for installing on Shared File System directories.

Use VMFVIEW to review the build status messages.

VMFVIEW BUILD

Back to Top of Page

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 ZVMN012A. 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 MANAGER for installing on minidisks. Specify MANAGERSFS for installing on Shared File System directories.

Review the build message log ($VMFBLD $MSGLOG). If necessary, correct any problems before proceeding.

VMFVIEW BUILD
Icon
Note: For information about handling specific error messages, see the appropriate VM Messages and Codes publication, or use online HELP.

Back to Top of Page

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
  • name
    Specifies the user ID of the CA Mainframe VM Product Manager administrator.
  • PRIMARY
    Copies product files to the administrator primary disk space. This value results in overwriting the deployed Product Materials from the older product release or version with the new release materials.

We recommend that you backup the VMANAGER runtime minidisk before using this command. Restoring the backup could be used to revert to the older release, if needed.

Back to Top of Page