3 Installing VM Client

This chapter describes how to install VM Client software.

Before installing ELS, verify ELS requirements and review pre-installation considerations described in Chapter 2, "Preparing for Installation".

After the VM Client is installed, you must obtain and install VM Client cumulative maintenance. See Chapter 4, "Installing VM Client Maintenance" for more information.

IBM VMSES/E

VM Client 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 installation steps. Each step is described in detail in the sections that follow.

  1. Determine VM client resource requirements.

    Use the VMFINS command to load several VMSES/E files from the product SRVLINK file to obtain VM Client resource requirements.

  2. Allocate VM client resources.

    Use the information obtained from the previous step to allocate the appropriate minidisks and user IDs needed to install and use VM Client.

  3. Install VM Client product files.

    Use the VMFINS command to load the VM Client product files from the product SRVLINK file to the BASE minidisk.

  4. Build the VM Client executable code.

    Use the VMFINS command to build the VM Client test BUILD minidisk.

  5. Create the VM Client service machine.

    Create a directory entry for the VM Client Service Machine.

  6. Customize VM Client service machine files.

    Edit the VM Client Service Machine samples.

  7. Test the VM Client.

    Test the VM Client on the test build disk.

  8. Place the VM Client into Production.

    After VM Client testing, copy the VM Client files from the test build disk to the production build disk.

Step 1: Determine VM Client Resource Requirements

Use the VMFINS command to determine VM Client resource requirements.

  1. Log on as the installer/planner.

    Use any user ID with read access to MAINT 5E5 and write access to the 51D disk that will contain the VM Client software inventory.

  2. Enter the following commands to establish read access to the VMSES/E code:

    LINK MAINT 5E5 5E5 RR
ACCESS 5E5 B

  3. Enter the following commands to establish write access to the Software Inventory disk, MAINT 51D in this example.

    LINK MAINT 51D 51D M
ACCESS 51D D

    Note the following:

    • The Software Inventory disk can be the system Software Inventory disk. It is recommended that a 51D disk be allocated to the maintenance/install user ID (VSMC730A).

    • 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 the other 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.

  4. Load the VM Client product control files to the 51D minidisk.

    Enter the following:

    VMFINS INSTALL INFO ( NOMEMO ENV VSMC730A

    The INSTALL INFO command loads various product control files and creates the VMFINS PRODLIST file.

  5. Obtain resource planning information for VMCLIENT.

    Enter the following:

    VMFINS INSTALL PPF VSMC730A VMCLIENT ( NOMEMO PLAN ENV
VSMC730A

    The file, VMFINS PLANINFO, is created on the A-disk. This file contains information about the user IDs and minidisks required to install VM Client.

  6. Review the install message log file, $VMFINS $MSGLOG. All installation messages are written to the installation user's A-disk. Correct any errors before proceeding.

Creating a PPF Override File

If the maintenance or service machine user IDs must be changed, use the following procedure to create a PPF override file:

  1. At the following prompt, enter 1.

    VMFINS2601R Do you want to create an override for :PPF VSMC730A
VMCLIENT :PRODID VSMC730A%VMCLIENT?

Enter 0 (No), 1 (Yes) or 2 (Exit)

  2. At the following prompt, enter 0.

    VMFMKO2917R Do you want to use the defaults for this product?

Enter 0 (No), 1 (Yes) or 2 (Exit)

  3. Update only the VM Client INSTALL User, only the VM Client SERVER, or both the VM Client INSTALL User and VM Client SERVER on the Make Override Panel. Press F3 to exit this panel.

  4. Select 2 - Save as... and enter file name of the override file.

    The override $PPF and PPF files are copied to the D-disk (51D).

    The override PPF now replaces the VSMC730A PPF file. Substitute this override PPF for all instances of VSMC730A in all remaining installation steps.

Step 2: Allocate VM Client Resources

Use the planning information in the VSMC730A PLANINFO file to create the VSMC730A user directory entry.

  1. Create the VSMC730A user directory entry.

    The VSMC720A user directory is located at the bottom of the PLANINFO file. These entries contain the links and privilege classes necessary for the VSMC730A user ID. Use the directory entry found in PLANINFO as a model for the VSMC730A directory entry.

  2. Add the MDISK statements to the directory entry for VSMC720A. The minidisk layout can be found in the PLANINFO file.

  3. Add the VSMC730A directory entry to the system directory. Change the password for VSMC730A from XXXXXX to a valid password, in accordance with your security guidelines.

  4. Place the new directory online.

Step 3: Install VM Client Product Files

Use the VMFINS command to build the VM Client test BUILD minidisk.

  1. Logon to the installation user ID VSMC730A, created in Step 2.

  2. Create a PROFILE EXEC that contains the ACCESS commands for MAINT 5E5 and 51D minidisks.

    XEDIT PROFILE EXEC A
===> input /**/
===> input 'access 5e5 b'
===> input 'access 51d d'
===> file

  3. Execute the profile to access MAINT's minidisks.

    PROFILE

  4. Establish write access to the Software Inventory disk, if it is not already linked R/W.

    LINK MAINT 51D 51D M
ACCESS 51D D

    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.

  5. Copy the VMSES/E files created on the installer/planner 191 disk to the VSMC730A 191 disk. This will place all the VM Client VMSES/E files in one location. The files to copy are:

    • VSMC730A PLANINFO

    • VSMC730A PRODLIST

  6. Install VM Client.

    Enter the following:

    VMFINS INSTALL PPF VSMC730A VMCLIENT (NOMEMO NOLINK ENV
VSMC730A OVERRIDE NO

    The NOLINK option indicates that VMFINS is not to link the maintenance minidisks, only access them if they are not already accessed.

    The OVERRIDE NO option indicates that VMFINS is not to create an override PPF. If an override PPF was created above, replace VMSMC730A with the name of the PPF created.

  7. Review the install message log file, $VMFINS $MSGLOG. All installation messages are written to the installation user's A-disk. If necessary, correct any errors before proceeding.

Step 4: Build the VM Client Executable Code

Use the VMFINS command to build the VM Client test BUILD minidisk.

  1. Enter the following command to build the test BUILD minidisk.

    VMFINS BUILD PPF VSMC730A VMCLIENT (ALL NOLINK

  2. Review the install message log ($VMFINS $MSGLOG). All installation message logs are written to the installation user's A-disk. Correct any errors before proceeding.

    The following messages in the VMFINS BUILD log are normal:

    • VMFBDC2178I

      Object =.HELPMSG cannot be rebuilt because it is not serviced

    • VMFBDC2178I

      Object =.HELPSMC cannot be rebuilt because it is not serviced

    • VMFINB2173I

      No verification exec found for this product

Step 5: Create the VM Client Service Machine

Create a directory entry for the VM Client Service Machine. The VM Client Service Machine must be able to issue the CP MSGNOH command (Privilege Class B).

Refer to the VSMC730A PLANINFO file for machine and minidisk requirements.

Step 6: Customize VM Client Service Machine Files

Copy the following files from the LOCALSAM minidisk to the VM Client service machine 191 minidisk (VMSMC191):

Table 3-1 VM Client Service Machine Files

Sample Name Operational Name Use

SMCPARMS SAMPLE

SMCPARMS (FILE)

Start parameters

SMCCMDS SAMPLE

SMCCMDS (FILE)

Start commands

SMCSTART EXEC

SMCSTART EXEC

VM Client start EXEC

SMCPRO SAMPLE

PROFILE EXEC

VM Client PROFILE EXEC

The SMCPARMS and SMCCMDS contain start parameters and commands. The file names of these files must match FIILDEF names in the SMCSTART EXEC.

See "VM Client Command Files" for information about updating VM Client parameter and command files.

Step 7: Test the VM Client

VM Client is now ready for testing. The executable code to be tested is on the VSMC730A 201 minidisk. The options to run the VM Client are:

  • LINK to VSMC730A 201 and issue SMCSTART.

  • Copy VSMC730A 201 to VMSMC 200 minidisk and issue SMCSTART. The sample PROFILE EXEC (SMCPRO SAMPLE) assumes this option.

Step 8: Place the VM Client into Production

After VM Client testing, enter the following commands to copy the VM Client files from the test disk (201) to the production disk (202):

VMFSETUP VSMC730A VMCLIENT

VMFCOPY ** fm1==fm2 (PRODID VSMC720A%VMCLIENT SPRODID
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)

The VM Client service machine will need to be modified to use the PRODUCTION version. The options are:

  • LINK to VSMC730A 202 and issue SMCSTART.

  • Copy VSMC730A 202 to VMSMC 200 minidisk and issue SMCSTART. The sample PROFILE EXEC (SMCPRO SAMPLE) assumes this option.