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 LMS for a new install

This topic describes tasks for setting and customizing LMS for use by the BMC AMI products licensed to your organization.

Task 1: Transferring License Certificate to host system

LMS uses License Certificate files to configure access to BMC AMI products licensed by your organization. Contracts Password Administration team sends the license certificates as email attachments. In order to be used by LMS, a License Certificate must be accessible to z/OS. To transfer License Certificate to host system, perform the steps as follows:

  1. Locate the License Certificate for the BMC AMI products being installed. A License Certificate file can contain licensing for more than one BMC AMI product.
  2. Allocate a target data set on the host system for the License Certificate. Use the DCB parameters RECFM=FB, LRECL=80, and whatever BLKSIZE you prefer.

  3. Transfer the License Certificate to the host using File Transfer Protocol (FTP), IND$FILE, cut and paste, or any other method desired.

    Important

    If you open the License Certificate data set in an IPSF editor or transfer it using cut and paste, make sure NUMBERS is set to OFF.

  4. If you have more than one License Certificate file, repeat the process as many times as required.

Task 2: Creating a license file

This task assists you to create the VSAM License File required to store your License Certificates for all licensed BMC software. The License File is fully compatible across all releases of LMS.

  1. Modify the sample JCL LMDELDEF, located in library SLCXCNTL, to allocate and initialize the VSAM License File.
  2. Update the JCL as required:
    1. Add a job card.
    2. Modify all instances of CPWR.LICENSE.FILE to the name you prefer. We recommend just changing the high-level qualifier, CPWR.
    3. Specify a DASD volume or use VOL(*) to let the system assign one for you.
    4. On the INITLF step’s STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.
  3. Submit the job and review the output to verify successful completion.
Warning

This job performs an IDCAMS DELETE on the specified LICENSE FILE. Use with caution.

Task 3: Importing license certificates

  1. Modify the sample JCL member LMIMPORT, located in library SLCXCNTL, to import BMC software license certificates (transferred in Task 1: to transfer License Certificate to host system) to the License File (created in Task 2: To create a License file).
  2. Update the JCL:
    1. Add a job card.
    2. On the IMPORT step STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.
    3. Modify CPWR.LICENSE.FILE to the name specified in Task 2: To create a License file.
    4. Modify CPWR.CERTIF.FILE to the name specified in Task 1: to transfer License Certificate to host system.
  3. Submit the job and review the output to verify successful completion.

Important

If you have more than one License Certificate file, repeat until all License Certificate files have been imported to the LMS License File.

Task 4: Verifying license file

  1. Modify the sample JCL member LMLFCRPT, located in library SLCXCNTL, to list the contents of the LMS License File.
  2. Update the JCL:
    1. Add a job card.
    2. On the LMAREPT step’s STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.
    3. Modify CPWR.LICENSE.FILE .
  3. Submit the job and review the output to verify successful completion. Also, verify that all your BMC License Certificates are listed.

Task 5: Creating LMS exit procedure

The Exit PROC is used by LMS to establish with z/OS a request for it to be notified when any of the following events occur on the LPAR:

  • A dynamic CPU upgrades.
  • A change to the defined capacity of the LPAR.
  • The first SMF interval to expire each midnight.

Each of these system events causes LMS to be notified via a standard z/OS Event Manager Exit. This exit code examines the state of the LPAR and determines whether it should invoke the PROC named in the EXIT_PROC parameter of the LMS client parameters.

You will notice that the EXIT_PROC is invoked once each day, just after midnight (based upon your installation’s SMF Interval). It is necessary for LMS to update the checkpoint data set with values consistent with the change of date. Perform the steps as follows:

  1. Copy the sample JCL member LMSEXIT, located in library SLCXCNTL, to a system PROCLIB.
  2. Update the JCL: On the EVENT step’s STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.

Task 6: Customizing LMS parameters

BMC provides LMS PARMLIB member (LMCL00), located in SLCXCNTL, that include the core parameters for getting a viable LMS subsystem loaded. BMC provides other LMS PARMLIB member (LMCLALL) that include all the possible parameters defined for use by LMS and may include parameters with default values.

  1. Copy the sample PARMLIB member LMCL00, located in library SLCXCNTL, to your BMC PARMLIB data set.

  2. Edit the copied member (LMCL00) to provide values for the following parameters:

    LMCL00 Parameters

    Description

    FUNCTION=UPDATE

    This parameter, with the UPDATE value, will define a new SUBSYSTEM_ID value to the table of subsystems.

    LICENSE_DSNAME

    This parameter specifies the license file data set name to be used.

    SITE

    This parameter specifies a site number that is required for LMS execution. This number tells LMS which site to load from the license file into the license cache. DD statements must be included in the LMS JCL named CWLFxxxx DD, where xxxx can be any alphanumeric characters.

    SUBSYSTEM_ID

    This parameter specifies the subsystem identifier that this invocation of LMS will process. This value can contain only uppercase letters and numbers. Although the operating system allows subsystem names to contain lowercase letters and special characters, LMS does not because the subsystem name may need to be included in the DDNAME of a CWIDssss DD DUMMY statement. Therefore, the value chosen for this parameter must also be valid in a DDNAME. You must coordinate the use of the subsystem identifier, because duplicate names are not allowed, either within the set of License Management subsystems, or across all subsystems defined. Verify that the subsystem value chosen is not already in use.

    DEFAULT

    This parameter specifies whether this SUBSYSTEM_ID will be declared the default subsystem. Your choices are NO|YES|FORCE.

    CHKPT_DSNAME

    This parameter specifies the name of a checkpoint data set. LMS requires a checkpoint data set to be available for LMS and to certain operating system exits at all times. This data set is created automatically by LMS if it does not already exist, or it is updated if it does exist. You must specify the 1- to 38-character name of this data set.

    Important

    The CMSC user ID (used to run LMS) must have ALTER access to the entity named by this parameter. The IDCAMS utility is dynamically invoked to define this data set. The same user ID is used for LMSEXIT.

    EXIT_PROC

    This parameter specifies the 1- to 8-character member name in your system PROCLIB, of the PROC which LMS automatically starts whenever an event occurs which drives the event notification exit. The events which will cause this PROC to start are:

    • A dynamic CPU upgrade (CPU upgrade on demand).
    • A change to the defined capacity of the LPAR.
    • The first SMF interval to expire each midnight.

    SMF_ID

    Specifies the SMF Record ID number to be used on all SMF records written by LMS. The SMF_ID must be a three-digit number in the range of 128 through 255. SMF_ID is required before any SMF recording can occur. If SMF_ID is not specified, then SMF recording will not take place regardless of the specification on any license file concerning this recording. SMF identifiers mush be unique numbers. Duplicate numbers cannot be defined to any program or system writing SMF records. Ensure that the SMF_ID value chosen is not already in use. The Record ID specified by the SMF_ID parameter must be recorded by SMF. A z/OS systems programmer must specify the SMF_ID on the SYS option in the SMFPRMxx SYS1. PARMLIB member.

    Example

    The values allowed for LMS, SMF record IDs are 128 through 255, which fall within the range 100:255 on the SYS option shown below; and therefore are eligible to be written by LMS.

    SYS(TYPE(0:18,20:68,100:255),EXITS(IEFUSI,IEFU84,IEFUJV,IEFACTRT,IEFU83,IEFUJI,IEFUTL,IEFU29,IEFU85),INTERVAL(SMF,SYNC),DETAIL) 

    If the value for the SMF_ID LMS parameter is not specified on the SYS option in SMFPRMxx, the following warning message will be issued by LMS during initialization: LM6095W SMF RECORD nnn IS NOT BEING RECORDED BY SMF. VERIFY IN SMFPRMXX Where nnn equals the SMF_ID.


    Important

    Specifying an SMF_ID does not automatically start SMF recording. SMF recording is performed on a product-by-product basis and is activated via an indicator within the file itself. This parameter and its value only state which SMF_ID will be used when SMF recording is activated.

  3. To ensure access to BMC AMI products is automatically enabled, establish a procedure in your system PROCLIB to launch your CMSC as a started task during IPL and IML processing.
  4. Specify the license file data set name in the LMCL00 module, under the LICENSE_DSNAME parameter.
  5. If you changed your LMS PARMLIB member name from the default LMCL00 (for example: LMCL0005), update your CMSC PARMLIB member to contain the suffix of the new LMS PARMLIB member, LMCL=0005.

Where to go from here?

If you have any BMC AMI products that use Host Communication Interface (HCI), continue with the tasks in Configuring-HCI-for-a-new-install—otherwise, go to Configuring-CMSC-for-a-new-install.


 

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