Contents
A local service consists of changes made to source maintained parts to alter the function of a product. This section documents the procedures and tool used to create a local modification and update the VMSES/E Product Inventory to incorporate it into your environment.
The CMS multi-level update process is used to update source maintained parts. The installation media for CA VM products contains sequenced source base files for all REXX parts. Source updates are included with each PTF that change REXX parts. A CNTRL file is supplied with each product to support customer source changes.
Create Local Service
This section documents the steps to create a REXX source update file.
Issue the following command to setup the VMSES/E search order for the product on the VMANAGER user ID:
VMFSETUP ppfname component ( LINK
- Assign a local tracking number to this modification. The suggested format of this tracking modification identifier is the letter L followed by a four-digit number. In this example, we will use L0001 as the modification identifier (MODID).
- Create an AUX file for the local modification or add an entry to the AUX file if it already exists. The filename of the AUX file is the same as the filename of the source file being modified. The AUX file filetype is determined by the LCL entry in the CNTRL file for the product being updated. It is defined to be AUXLCL. In this example, we will update source file MYFILE $EXEC$. Therefore we will first create or update the MYFILE AUXLCL file.
Add a line at the top of the file using XEDIT. The line is of the form:
UPL0001 LCL LCL0001 * Test Local Modification
The record consists of three tokens followed by a comment describing the update. The required tokens are specified in this order:
- The first token is the filetype of the actual update file.
- The second token is the Service Level Identifier. The required identifier is LCL.
- The third token is composed of the letters LC followed by the five character MODID value.
- The comment is any string beginning with an asterisk.
Use the XEDIT command with the CTL option, and the filename of the product specific CNTRL file to create the update file. The filename of the CNTRL file is defined by the value on the CNTRL tag in the Product Parameter File for the product. In this example, we will use the VMX CNTRL file. Issue the following command:
XEDIT MYFILE $EXEC$ ( CTL VMX
Add, delete, or modify lines in the file to program the desired update. When you file the changes, XEDIT will produce a standard CMS UPDATE file. The file must be created on or moved to the LOCALMOD disk in the product search order.
Apply Local Service
The CA Mainframe VM Product Manager provides the REXXUPD tool to apply the local modification update, along with updates included with any PTFs, to the base source file for the part being updated. Use the following format of the command to apply the update to the base file:
REXXUPD MYFILE $EXEC$ ppfname component
This command uses a VMSES/E filetype abbreviation to construct the filetype for the output file. The filetype abbreviation for each type of source file is defined on the REXXUPD CONFIG file found on the VMANAGER 195 minidisk. The abbreviation is concatenated with the MODID value to construct the output filetype. In our example the REXXUPD command creates file MYFILE EXCL0001 on the LOCALMOD disk. It also adds an entry in the VVTLCL file and updates the SRVBLDS file on the APPLY disk.
Build and Deploy Local Service
The local service is built by using the VMSES VMFBLD command. Issue the following command to build the newly updated part:
VMFBLD PPF ppfname component ( SERVICED
The last step is to deploy the updated product files to the desired runtime disks. Use the VMDEPLOY command, as documented in the section "Servicing Your Product" in the appropriate product Installation Guide.