Installation Guide › Installing Product Materials

Installing Product Materials

This section contains the following topics:

Installation Process Overview

Step 1. Plan Your Installation

Step 2. Allocate Product Resources

Step 3. Install the Product Materials

Step 4. Update the Software Inventory

Installation Process Overview

The following is a brief description of the main steps in installing this product using VMSES/E.

Plan your Installation
Use the VMFINS command to load several VMSES/E files from the product envelope and to obtain product resource requirements.
Allocate Product Resources
The information obtained from the previous step is used to allocate the appropriate minidisks (or SFS directories) and a user ID to own them. This set of disks contains the loaded product materials and is where the code is serviced. The allocation of resources used to deploy the product is described separately in the chapter Deploying the Product.
Install the Product Materials
Use the VMFINS command to load the product files from the envelope to the test BUILD and BASE minidisks/directories. VMFINS is then used to update the VM SYSBLDS file used by VMSES/E for software inventory management.
Update the Software Inventory
Use the VMFINS command to update the software inventory to prepare the product materials for later service application by updating the Software Inventory status tables.

Step 1. Plan Your Installation

Follow these steps to obtain planning information for this product.

Step 1.1 Prepare SERVLKPK Files for Product Installation

The product download file is in SERVLKPK format. The SERVLKPK files are VMFPLC-format VMSES/E product envelope files that have been compressed using the CMS COPYFILE command with the PACK option.

Follow these steps:

Upload the packed product envelope file to your mainframe z/VM ID, using a file transfer program, such as IND$FILE or an FTP client.
The packed product envelope file that you extracted from the zip file product package has a name similar to nnnnnnnnnnn.SERVLKPK. The file transfer must use a binary protocol. Rename the file during the file transfer to conform to the z/VM file name file type naming conventions. Use a file type of SERVLKPK.

Note: For more information about the required file names, see your product Cover Letter.
Unpack the file using the CMS PIPE command with the UNPACK option:
```
PIPE < ifn ift ifm | FBLOCK 1024 | UNPACK | > ofn SERVLINK ofm 
```
where:

ifn: Indicates the file name of the packed envelope.
ift: Indicates the file type of the packed envelope.
fm: Indicates the file mode of the packed envelope.
ofn: Indicates the file name to give to the unpacked envelope file. For this release, the CMS filename is ZVMB036A.
ofm: Indicates the file mode to give to the unpacked envelope file.

Note: SERVLINK appears for the unpacked file type because VMSES/E requires an envelope file to have a file type of SERVLINK.

Step 1.2 Establish the CA Mainframe VM Product Manager Environment

Follow these steps to establish the CA Mainframe VM Product Manager environment:

Log on to the VMANAGER user ID to access the CA Mainframe VM Product Manager environment.
Make the SERVLINK file available to the VMANAGER user ID. The SERVLINK file must be on a minidisk or Shared File System directory accessed as file mode A or C.

Note: The PROFILE EXEC on the VMANAGER user ID will access the disks or SFS directories needed for the CA Mainframe VM Product Manager environment as follows:

The work disk is accessed as file mode A.
The CA Mainframe VM Product Manager code is accessed as file mode B.
The VMSES CA Software Inventory disk is accessed as file mode D.
The CA Mainframe VM Product Manager database is accessed as file mode V.
The CA Mainframe VM Product Manager Common disk is accessed as file mode W.
The IBM VMSES system disk is accessed as file mode X.

Step 1.3 Load Product Control Files and VMFINS PRODLIST

The product control files include the following:

Memo-to-Users file (MEMO)
Product Parameter File (PPF)
PRODPART file

The VMFINS PRODLIST contains a list of products on the installation envelope file.

The VMFINS command loads the control files to the Software Inventory Disk and creates the VMFINS PRODLIST file on the A-Disk. VMFINS loads from an envelope file. The envelope is either downloaded or retrieved from a DVD media.

Issue the following command to install the product control files and create the VMFINS PRODLIST file:

VMFINS INSTALL INFO ( NOMEMO ENV ZVMB036A

NOMEMO: Specifies that the Memo-to-Users file is to be loaded, but VMSES/E will not issue a prompt to send it to the system printer. The CMS file type of this file is MEMO.
ENV: Indicates the value following this option keyword, which is the name of the envelope file for a specific product and release. For this release the CMS file name is ZVMB036A. The CMS file type of this file is SERVLINK.

Step 1.4 Load and Generate the Planning Resource File

The planning resource file (PLANINFO) contains the planning information required to install the product. The VMFINS command with the PLAN option loads the necessary components from the envelope file and generates the PLANINFO file.

Files may be loaded either to minidisks or to Shared File System (SFS) directories using the following command:

VMFINS INSTALL PPF ppfname component ( PLAN NOMEMO ENV ZVMB036A

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 ZVMB036A. 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 VMBACKUP for installing on minidisks. Specify VMBACKUPSFS for installing on the Shared File System directories.

PLAN

Creates a PLANINFO file. This file contains product requisites and resources required for the product (user IDs, minidisks, and SFS directories). PLAN does not generate, allocate, or commit any system resources.

NOMEMO

Specifies that the Memo-to-Users file is to be loaded, but VMSES/E will not issue a prompt to send it to the system printer. The CMS file type of this file is MEMO.

ENV

Indicates the value following this option keyword, which is the name of the envelope file for a specific product and release. For this release the CMS file name is ZVMB036A. The CMS file type of this file is SERVLINK.

During the execution of the VMFINS command, you are prompted to create an override for the ppfname and component you specified:

VMFINS2601R Do you want to create an override for :PPF ZVMB036A
VMBACKUP :PRODID ZVMB036A%VMBACKUP?
Enter 0 (No), 1 (Yes) or 2 (Exit)

Do one of the following:

If you are accepting the default resource names and values, specify NO to the override prompt and skip to the next section.
If you specify YES, you are presented with a panel for changing resource values such as disk owners, disk addresses, or SFS directory names. See the appendix Create Product Parameter File (PPF) Override for a sample of creating a PPF override.

Note: If you are not familiar with creating PPF overrides using VMFINS, you should review the Using the Make Override Panel section of the IBM VMSES/E Introduction and Reference before you continue.

More information:

Create Product Parameter File (PPF) Override

Step 2. Allocate Product Resources

The VMFINS command in the previous section produces a report file containing a list of the resources needed to install and service the product. The file has the same CMS file name as the PPF file, and the file type is PLANINFO. It is created on the VMANAGER A-disk. Several alternative methods are available to allocate the needed user ID entry and disk space specified in the PLANINFO file.

In this step, disk space is allocated and owned by a VM user ID created specifically for one release of this product. The default user ID for this user is the same as the PPF CMS file name.

Disk space may be allocated either on minidisks or on Shared File System (SFS) directories. Minidisk space is often easier to setup, but is more complex to manage in that they need to be enlarged when more files are added during service. SFS directories provide more automatic space management, but need more time to setup initially.

Note: For more information about how the VMALLOC command is configured and used, see the appendix Allocating User ID Entries and Disk Space, and then issue the command as described.

To create the product staging area user ID and allocate minidisk space, enter the following command:

VMALLOC PRODUCT ppfname component

ppfname: Specifies the CMS file name for the Product Parameter File for this specific version of the product. If you created a PPF override file, use its file name here. If you use the supplied PPF, its name is ZVMB036A.
component: Specifies the name of the component. Use the name VMBACKUP for installing on minidisks. Use the name VMBACKUPSFS for installing on SFS.

Depending on the configuration described in the appendix Allocating User ID Entries and Disk Space, you may have to perform additional steps to finish the allocation task using DIRECTXA or a Directory Manager product.

Allocating SFS Directories

An SFS Installation requires the following additional steps:

Enroll the user ZVMB036A in a SFS filepool using the CMS ENROLL command. This command may only be issued from a user authorized as an SFS Administrator for the filepool.

Create the necessary directories for user ZVMB036A with the CMS CREATE DIRECTORY command. The suggested fully qualified directory names are defined in the :DCL section of the VMBACKUPSFS component override section of the ZVMB036A PPF file.

Give the VMANAGER user ID WRITE and NEWWRITE access to those directories with the CMS GRANT AUTHORITY command.

Step 3. Install the Product Materials

Use the VMFINS command to load the product files from the installation media to the BUILD and BASE minidisks or SFS directories. Enter the following command:

VMFINS INSTALL PPF ppfname component ( ADD NOMEMO ENV ZVMB036A

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.

For the component value, use VMBACKUP for installing on minidisks. Specify VMBACKUPSFS for installing on Shared File System directories.

ADD

Loads the product materials onto disk areas. These materials will later be deployed to a product server for production use.

NOMEMO

Specifies that the Memo-to-Users file is to be loaded, but VMSES/E will not issue a prompt to send it to the system printer. The CMS file type of this file is MEMO.

ENV

Step 4. Update the Software Inventory

Update the software inventory to prepare the product materials for later service application by updating the Software Inventory status tables.

Enter the following command to update the software inventory:

VMFINS BUILD 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.

For the component value, use VMBACKUP for installing on minidisks. Specify VMBACKUPSFS for installing on Shared File System directories.

SERVICED

Specifies that the Software Inventory Status tables be built.