Contents
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 ZVMN012A.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
In order to establish the environment, you must have a CA Mainframe VM Product Manager user ID.
Step 1.2.1 Create the CA Mainframe VM Product Manager Administrator User ID
If you have not previously created a VMANAGER administrator user ID then you follow these steps to do so. If you have already installed a previous release of the CA Mainframe VM Product Manager facility, then skip these steps and go directly to the section on establishing the environment.
Create a VMANAGER user ID using your installation VM directory management procedures, using this sample:
USER VMANAGER VMANAGER 16M 999M BCDEG 64 MACHINE ESA OPTION LNKNOPAS IPL CMS CONSOLE 009 3215 SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019E 019E RR LINK MAINT 019D 019D RR * IBM VMSES/E program disk LINK MAINT 5E5 5E5 RR * Work Disk * MDISK 0191 3390 startcyl 5 volser MR * MDISK 0191 3380 startcyl 6 volser MR * MDISK 0191 9336 startblk 7200 volser MR * Software Inventory disk * MDISK 051D 3390 startcyl 5 volser MR * MDISK 051D 3380 startcyl 6 volser MR * MDISK 051D 9336 startblk 7200 volser MR * Public files disk * MDISK 0193 3390 startcyl 15 volser MR * MDISK 0193 3380 startcyl 18 volser MR * MDISK 0193 9336 startblk 21600 volser MR * CA Mainframe VM Product Manager Code Disk * MDISK 0195 3390 startcyl 15 volser MR * MDISK 0195 3380 startcyl 18 volser MR * MDISK 0195 9336 startblk 21600 volser MR * LMP Key and configuration data files * MDISK 01FF 3390 startcyl 5 volser MR * MDISK 01FF 3380 startcyl 6 volser MR * MDISK 01FF 9336 startblk 7200 volser MR
Logon to the VMANAGER user ID, format the 0191, 051D, 01FF, 0193, and 0195 disks with a 4096 block size, and add a PROFILE EXEC to the VMANAGER 191 disk, using this sample:
/* CA Mainframe VM Product Manager PROFILE */ 'CP SPOOL CONSOLE * START' 'SET RDYMSG SMSG' 'ACCESS 195 B' /* VMANAGER code disk */ 'ACCESS 51D D' /* CA Software Inventory */ 'ACCESS 1FF V' /* Configuration File disk */ 'ACCESS 193 W' /* Public disk */ 'ACCESS 5E5 X' /* IBM SES code */
Step 1.2.2 Establish the 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 installation tape or SERVLINK file available to the VMANAGER user ID:
- If you are installing from tape, use your installation specific procedures or tape management system to mount the product installation tape and attach it to the VMANAGER user ID at virtual address 181.
- If you are using a product envelope SERVLINK file, make it available on the VMANAGER A-disk or on any disk or SFS directory accessed as file mode 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 mode D.
- The configuration database is accessed as file mode V.
- The public file 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 ZVMN012A
- 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 ZVMN012A. 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 ZVMN012A
- 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 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 ZVMN012A. 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 ZVMN012A MANAGER :PRODID ZVMN012A%MANAGER? 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.
Step 2. Allocate Product Resources
Use the information you obtained in the previous step 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.
Step 2.1. Allocate User ID Entry and Disk Space
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.
Because this is the initial installation of the CA Mainframe VM Product Manager, you must manually create a user ID to hold the product materials. Create the ZVMN012A user ID using this sample and your site VM directory management procedures. Link to each disk from another ID and execute the CMS FORMAT command to format each disk with a block size of 4096.
USER ZVMN012A NOLOG * Local modifications disk * MDISK 02C4 3390 startcyl 1 volser MR * MDISK 02C4 3380 startcyl 2 volser MR * MDISK 02C4 9336 startblk 1440 volser MR * AUX and Software Inventory files * MDISK 02A6 3390 startcyl 1 volser MR * MDISK 02A6 3380 startcyl 2 volser MR * MDISK 02A6 9336 startblk 1440 volser MR * AUX and Software Inventory files * MDISK 02A2 3390 startcyl 1 volser MR * MDISK 02A2 3380 startcyl 2 volser MR * MDISK 02A2 9336 startblk 1440 volser MR * MANAGER service * MDISK 02D2 3390 startcyl 1 volser MR * MDISK 02D2 3380 startcyl 2 volser MR * MDISK 02D2 9336 startblk 1440 volser MR * Test Admin code disk * MDISK 0210 3390 startcyl 15 volser MR * MDISK 0210 3380 startcyl 18 volser MR * MDISK 0210 9336 startblk 21600 volser MR * Test Public code disk * MDISK 0214 3390 startcyl 1 SPACE5 MR * MDISK 0214 3380 startcyl 2 SPACE5 MR * MDISK 0214 9336 startblk 1440 SPACE5 MR * Test Help code disk * MDISK 0216 3390 startcyl 1 SPACE5 MR * MDISK 0216 3380 startcyl 2 SPACE5 MR * MDISK 0216 9336 startblk 1440 SPACE5 MR * Sample files disk * MDISK 02C2 3390 startcyl 1 volser MR * MDISK 02C2 3380 startcyl 2 volser MR * MDISK 02C2 9336 startblk 1440 volser MR * MANAGER base source * MDISK 02B2 3390 startcyl 30 volser MR * MDISK 02B2 3380 startcyl 36 volser MR * MDISK 02B2 9336 startblk 43200 volser MR
Step 2.2. (Optional) Allocate SFS Directories
An SFS Installation requires the following additional steps:
- Enroll the user ZVMN012A 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 ZVMN012A with the CMS CREATE DIRECTORY command. The suggested fully qualified directory names are defined in the :DCL section of the MANAGERSFS component override section of the ZVMN012A 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 ZVMN012A
- 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. - 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
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 ZVMN012A. The CMS file type of this file is SERVLINK.
Step 4. Update the Product 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.
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. - SERVICED
Specifies that the Software Inventory Status tables be built.