4 Installing VM Client Maintenance

This chapter contains instructions for installing VM client maintenance.

You must obtain and install the latest VM Client cumulative maintenance (PTFs and HOLDDATA). Download cumulative maintenance from the My Oracle Support (MOS) site at:

http://www.myoraclesupport.com

Visit this site frequently for HOLDDATA and PTF updates and install cumulative maintenance updates on a regular schedule. PTFs are released monthly to MOS.

Before attempting to install maintenance, contact Oracle Global Customer Services for information about the latest maintenance available. See "Preface" for information about contacting Oracle for assistance.

Note:

PTFs and HOLDDATA may not exist at VM Client release launch but will follow in time and are released monthly to MOS.

IBM VMSES/E

VM Client cumulative maintenance is installed using IBM's VMSES/E (Virtual Machine Serviceability Enhancements Staged/Enhanced), a component of IBM VM/ESA.

VMSES/E includes the VMFINS installation aid, designed to make installation of products consistent.

Refer to the IBM publication VMSES/E Introduction and Reference for more information about VMSES/E operation.

Summary of Installation Steps

The following is a summary of maintenance installation steps. Each step is described in detail in the sections that follow.

Prepare to Receive maintenance.

Use the VMFMRDSK command to clear the alternate apply disk before receiving new maintenance., enabling you to easily remove maintenance if a serious problem is encountered.
Receive maintenance.

The VMFREC command receives maintenance and places it on the Delta disk.
Apply maintenance.

The VMFAPPLY command updates the VMSES/E version vector table (VVT), which identifies the service level of all the serviced parts. In addition, AUX files are generated from the VVT for parts that require them.
Build new levels.

The build task generates the serviced level of an object and places the new object on a test BUILD (201) disk.
Place new maintenance into production.

After being tested, the maintenance is placed into production by copying the new service to the production disk (202).

Step 1: Prepare to Receive Maintenance

Do the following:

Log on to the VM Client service ID VSMC730A.
Establish write access to the Software Inventory disk, if it is not already linked R/W.
```
LINK MAINT 51D 51D M
ACCESS 51D D
```
Note:
If another user is currently linked to the Software Inventory disk in write mode (R/W), the LINK command will fail. If this occurs, direct this user to re-link to the Software Inventory disk in read-only mode (RR), and then re-issue the above LINK and ACCESS commands. Do not proceed until you establish a Read/Write link to the Software Inventory (51D) disk.
Establish the correct minidisk access order.
```
VMFSETUP VSMC730A VMCLIENT
```
VSMC730A is the PPF shipped with the product. If you have your own PPF override, you must substitute your PPF name for VSMC730A.
Receive the documentation. VMFREC with the INFO option loads the documentation and displays a list of all products in the package.

Enter the following:
```
VMFREC INFO ( ENV filename
```
Review the receive message log file, $VMFREC $MSGLOG, for warning and error messages.
```
VMFVIEW RECEIVE
```
Clear the alternate APPLY disk to ensure that you have a clean disk for new maintenance.
```
VMFMRDSK VSMC730A VMCLIENT APPLY
```
VSMC730A is the PPF shipped with the product. If you have your own PPF override, you must substitute your PPF name for VSMC730A.
Review the merge message log file, $VMFMRD $MSGLOG. If necessary, correct any errors before proceeding.
```
VMFVIEW MRD
```

Step 2: Receive Maintenance

Do the following:

Receive the maintenance.

Enter the following:

VMFREC PPF VSMC730A VMCLIENT ( ENV filename

Review the receive message log file, $VMFREC $MSGLOG. If necessary, correct any errors before proceeding.
```
VMFVIEW RECEIVE
```

Step 3: Apply Maintenance

Do the following:

Apply the new maintenance.
```
VMFAPPLY PPF VSMC730A VMCLIENT
```
This command applies the maintenance that you just received. The version vector table is updated with all serviced parts and all necessary AUX files are generated.
Review the apply message log file, $VMFAPP $MSGLOG. If necessary, correct any errors before proceeding.

Step 4: Build New Levels

Do the following:

Build the Build Status Table with serviced parts.
```
VMFBLD PPF VSMC730A VMCLIENT (STATUS
```
Review the build message log file, $VMFAPP $MSGLOG. If necessary, correct any errors before proceeding.
```
VMFVIEW BUILD
```
Rebuild VM Client serviced parts.
```
VMFBLD PPF VSMC730A VMCLIENT (SERVICED
```
Review the build message log file, $VMFAPP $MSGLOG. If necessary, correct any errors before proceeding.
```
VMFVIEW BUILD
```

Step 5: Place the New Maintenance into Production

After VM Client testing, copy the VM Client files from the test disk (201) to the production disk (202).

VMFSETUP VSMC730A VMCLIENT
VMFCOPY ** fm1==fm2(PRODID VSMC730A%VMCLIENT OLDDATE REPLACE

fm1 is the file mode of the TEST build disk (BUILD1 - 201).

fm2 is the file mode of the PRODUCTION build disk (BUILD2 – 202).