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.

Configuring CMSC for a new install

This topic will assist you to customize the CMSC, which will provide support to all the other BMC mainframe products that require the use of the BMC PARMLIB.

Task 1: Preparing for simple deploy

  1. Copy the DDSN00 sample from hlq.SLCXCNTL(DDSN00) into the common PARMLIB data set.
  2. Uncomment the DD_INFO blocks for products that are installed or will be installed.

  3. Update the DSNAME parm in the DD_INFO block to match the actual data set names on your LPAR.

    Tip

    You can use System Symbols and the CMSC will resolve the names.

  4. Modules MSCUDDRX and MSCUDDCL must be made available to the TSO user executing the BMC CLISTs and REXX execs. This can be accomplished with one of the following options.
  • Option 1: (Recommended) Put the SLCXLOAD data set (or modules MSCUDDRX and MSCUDDCL) in the STEPLIB concatenation in the TSO LOGON procedure for users of BMC CLISTs and REXX execs.

Important

Option 1 is recommended if your system is set up with LNKAUTH=LNKLST (which is the default setting) in SYS1.PARMLIB member IEASYSxx.

  • Option 2: Copy modules MSCUDDRX and MSCUDDCL to a library that is on LNKLST.
  • Option 3: Put the SLCXLOAD data set on LNKLST.

Task 2: Customizing CMSC parameters

BMC provides a default CMSC PARMLIB member (CMSC00), located in library SLCXCNTL, that includes the core parameters for getting a viable CMSC started. BMC provides a second CMSC PARMLIB member (CMSCALL), also located in library SLCXCNTL, that includes all the possible parameters defined for use by the CMSC, and may include parameters with default values.

  1. Copy the sample PARMLIB member CMSC00, located in library SLCXCNTL, to your BMC PARMLIB data set (created in Task 2 Define the BMC Common Parameter Library data set).

  2. Edit the copied member (CMSC00) to provide values for the following parameter:

    CMSC_ID=CMSC

    This parameter specifies the name of the CMSC. This parameter must be a 1 to 4-character string. The string must consist of letters (A-Z), digits (0-9), or national symbols (@, #, $). It must begin with a letter or national symbol.

    CMSC_ID=CMSC must be specified for the primary CMSC.

    Important

    If you defined each of the LMCL, HCI, and CSS PARMLIB members with the default suffix 00 (LMCL00, HCI00, and CSS00), then there is no need to add these PARMLIB member names to the CMSCxx PARMLIB member, because CMSC automatically assumes these default member names.

Task 3: Starting the CMSC

This task will assist you to copy the sample CMSC JCL to a system PROCLIB. This JCL, once customized, will be used to start the CMSC. The CMSC can be submitted as a batch job, however, we recommend that the PROC be setup as a started task and added to your installation’s IPL process.

Member CMSC in the SLCXCNTL library contains sample JCL to run the CMSC. Copy the sample JCL to your system PROCLIB, follow the instructions in the member and modify the JCL to your site’s requirements. The JCL can be submitted as a batch job or can be executed as a started task.

CMSC initialization process

Configuration_CMSC00003.jpg

BMC AMI mainframe product parameter retrieval flowchart

ECCMilestone6_ProductParameterRetrievalFlowchart.png

  1. Copy the sample JCL member CMSC, located in library SLCXCNTL, to a system PROCLIB. 
  2. Update the JCL:

    1. On the CMSC00 EXEC statement, update the PARM

      PARM=’name,CMSC,ssss’

      – name is the name of the CMSC. This can be any unique name of your choosing, up to eight characters in length. The only restrictions are that it must begin with a letter or national character, and contain letters, digits, or national characters.

      – CMSC identifies the address space being initialized by this JCL as a CMSC.– ssss specifies the one to four-character suffix for the CMSC PARMLIB member. This parameter will be concatenated with the prefix ‘CMSC’ to construct the name of the PARMLIB member to be used for the CMSC startup parameters. The suffix must follow the rules for PDS members.

    2. On the CMSC00 step’s STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.
    3. On the CMSC00 step’s FDBDRPL DD statement, update the SLCXLOAD library to your installation’s fully qualified data set name.
    4. On the CMSC00 step’s CWPARM statement, update the CPWR.PARMLIB to your installation’s fully qualified BMC PARMLIB data set name.
  3. Start the PROC as a started task or for testing purposes, submit as a batch job.

Task 4: Verifying CMSC

  1. View the executing CMSC’s job output: 

    1. Look for the following messages in the FDBDLOG:

      FDBRC1999I REGION INITIALIZATION COMPLETE FOR SERVER CMSC

      This message signifies that the CMSC Server was initialized and is ready

      MSCSC2512I THE LMS TASK HAS TERMINATED. DETACHING.

      This message indicates the LMS task that started the LMS subsystem has ended and is detaching.

    2. Look for the following messages in the LMCPRINT:

          LM6012I UPDATE OF CHECKPOINT DATA SET COMPLETED
          LM5020I SUBSYSTEM LMS1 HAS BEEN UPDATED ON SYSTEM CW99
          LM5003I HIGHEST RETURN CODE WAS 00000000 AND REASON CODE WAS 0

      These messages signify that the LMS subsystem was successfully loaded into the CMSC address space and is available for license validation by the BMC AMI product requiring it.

      Important

      • If you are performing this task as a part of Upgrading ECC version, continue your ECC upgrade with verifying LMS subsystems. For more information, see Upgrading.
      • If the CMSC controls your HCIPROC, complete the HCI verification. Once the HCI verification is complete, continue to configuring CSS.

      We do not recommend that the CMSC be used to control the HCI when an automated procedure such as a JES3 reader file, or an automated operations product, is being used to shut down the CMSC and HCI.

Where to go from here?

To configure CSS, perform the tasks mentioned in Configuring-CSS-for-a-new-install.

 

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