Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Preparing for configuration

This topic explains all tasks that are required to initiate the configuration for ECC, whether it is for an upgrade to an existing installation, or for a new product installation. This will assist you to prepare for either upgrading your existing ECC to the current release, or to install the current release of ECC.

Important

Role involved: z/OS Systems Programmer

Task 1: Verifying APF-authorize SLCXAUTH load library

We recommend that the ECC SLCXAUTH library is APF-authorized to z/OS. Certain ECC components require some modules to be in an APF-authorized library. BMC has provided a load library, SLCXAUTH, that contains those modules. APF-authorization is applicable to SLCXAUTH load library only. To complete this task, follow IBM procedures.

Task 2: Defining the BMC Common Parameter Library data set

BMC's Common Parameter Library (PARMLIB) feature requires a partitioned data set to be allocated on your system to keep PARMLIBs for those BMC AMI products that employ this configuration tool.

A minimum of one BMC PARMLIB data set must exist in order to contain BMC AMI product PARMLIB members, which are accessed by CMSC. If you have allocated the PARMLIB data set, skip this task. Otherwise, define a library following the given instructions:

  1. Modify the sample JCL member CMSCALCP, located in library SLCXCNTL, to allocate the PARMLIB data set.
  2. Update the JCL:
    1. Add a job card.
    2. Specify an appropriate data set name for the CPWRPARM DD statement by changing the CPWR.PARMLIB name. We recommend that you add a high-level qualifier to the provided data set name.
  3. Submit the job and review the output to verify successful completion.

Task 3: Defining the HCI default user ID

The DEFAULT_USER parameter specifies the name of a valid RACF (ACF/2 or TOPSECRET) user ID to be used by the Host Communication Interface (HCI) when Transaction Process (TP) jobs are submitted or started and when there is no other user ID available. The user ID must be assigned within the security system and granted authority to perform any processing that the TP requires, until the TP issues one of the set security calls. Till that time, the new user ID is in effect.

Example

Ensure that the default user ID has either ACCESS(READ) or ACCESS(EXECUTE) to the //STEPLIB DD used in the TP JCL and that it has appropriate access to any other data sets that it processes under the default user ID.

Important

After the TP has issued a security call, the default user ID is no longer used for access, because the TP starts running under the user ID passed in the security call.

Task 4: Upgrading or installing

If you are upgrading an existing release of ECC, continue with Upgrading.

If you are installing ECC for the first time, continue with Configuring-LMS-for-a-new-install.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*