LMS overview
LMS enables you to manage access to all the BMC AMI products used by your organization.
LMS advantages
LMS provides the following advantages:
- Electronically-delivered License Certificates that contain product access parameters in a human-readable text format.
- Programs and reports to verify the contents of the License File and LMS runtime environment.
- Easy updates to License Certificates and the License File with no disruption to your BMC AMI products.
- No production impact from the testing of LMS runtime systems, installation and validation of new License Certificates, or installation of new or updated LMS software.
- Optional e-mail alerts and SMF logging when licensing events occur.
Operating environment
LMS operates under IBM MVS/ESA Release 4.3 and more current, and all OS/390 and z/OS releases.
License management process
The license management process begins when you acquire a BMC AMI product through a license agreement, trial agreement, or beta agreement.
Information gathering
BMC obtains the relevant information for license management from you at the time of the agreement. Your organization supplies information such as name and the sites and CPUs for which the product is being licensed. Information about the BMC AMI product licensed, such as product name, release number, and options licensed, is obtained from your BMC representative.
License certificate
Upon the completion of an agreement, BMC creates a License Certificate representing a portion of the information in that agreement. The License Certificate is used by LMS to provide access to BMC AMI products. The License Certificate is not the same thing as a license agreement. You are still responsible for abiding by your license agreement, and although not its primary role, you will find that the LMS can help in that effort.
The License Certificate, LMS, and the BMC AMI product are all delivered to you by BMC. Typically, you receive the License Certificate via email, but other methods can be used, if necessary.
Installation
LMS is included as part of the ECC single install image. First, set up your LMS environment, import your License Certificate into a License File, execute the CMSC address space, and install your BMC AMI products. From then on, access to your BMC AMI mainframe products occurs transparently.
After you accomplish the initial LMS installation, you would typically only need to import a new product License Certificate and re-initialize the LMS runtime environment in conjunction with events such as the following:
- Obtaining a new release of a product under the terms of your software maintenance agreement.
- Adding new products through additional license agreements.
- Amending your agreement to include new options.
- Changing the CPUs licensed in your original agreement.
The tasks you need to perform will depend on whether or which version of LMS has already been enabled at your site.
The following is a list of items you might want to consider:
- Running more that one license management system.
- Managing more than one BMC customer number.
Running more than one License Management System
Under certain circumstances, a site may decide to run more than one instance of LMS. For instance, you might want both test and production LMS environments on the same system. BMC supports the environment of multiple LMS systems on a particular LPAR, though for all but the most unusual implementations it is not necessary to run more than one LMS subsystem on any particular LPAR. One possible exception would be the installation of a complete new release of LMS, where it is desired that existing BMC AMI products continue to execute normally during the time that the new release is installed and tested.
Managing more than one BMC customer number
A site that manages multiple BMC customer numbers, for example a service bureau, will have a License File for each BMC customer number.
Migration considerations
The following items should be considered when upgrading from an earlier release of LMS to LMS release 17.02 or later:
- Starting with release 17.02, LMS runs under the new BMC AMI Common Mainframe Services Controller (CMSC) address space. The initialization jobs no longer run independently. Starting with the January 2019 Release of ECC 17.02, the Central Licensing Facility (CLF) will no longer be supported.
Creating a License File
If you have previously installed BMC's License Management System software, see Verify the License File.
In this step, you will use the LAU to create a License File.
- Execute the LMSPREP CLIST to update the CWLMA CLIST.
Start the LAU by selecting the ISPF menu item that was added by executing the CLIST CWLMA. The License File Selection is displayed.
License File Selection---------------------- BMC AMI License Management 17.02.00 --- Row 1 to 5 of 5
Command ===> SCROLL ===> PAGE
License File Selection
Current Selection:
Enter New DSN . .
(fully qualified without quotes)
Delete/Define . N (Y|N)
OR select below:-
Action DSN Added by
- LICENSE.FILE1 USERID1 2022-12-30
- LICENSE.FILE2 USERID2 2023-03-07
********************************* Bottom of data ********************************- Type the name you want to use for your License File (fully-qualified, without quotes) in the Enter New DSN field.
- Type Y in the Delete/Define field.
Press Enter. The Delete/Define and Initialize License File figure is displayed, and the file name you specified above will be shown in the New License File field.
Delete/Define and Initialize License File figure
--------------------- BMC AMI License Management 17.02.00 -- Row 1 to 2 of 2
Command ===> SCROLL ===> PAGE
Delete/Define and Initialize License File
New License File . : TSOID01.License.File.New
Unit . . . . . . . . _________ (required for JES3 only)
Volume Serial . . . _______ (blank for system determined volume)
Edit JCL . . . . . . Y (Y-Yes,N-No)
Press END Key to skip this process
Jobcard:
//Job Card information line 1
//Job Card information line 2
//Job Card information line 3
//Job Card information line 4
Select Node Description
******************************* Bottom of data ********************************- Type Y in the Edit JCL field.
Type the information for your jobcard using the four lines of the Jobcard field.
Press Enter. The Edit Delete/Define JCL figure is displayed.
Edit Delete/Define JCL figure
File Edit Confirm Menu Utilities Compilers Test Help
-------------------------------------------------------------------------------
EDIT SYS98274.T095731.RA000.TSOID01.R0111344 Columns0000100080
Command ===> Scroll ===>CSR
*************************************** Top of Data ***************************
000001 //Job Card information line 1
000002 //Job Card information line 2
000003 //Job Card information line 3
000004 //Job Card information line 4
000005 //*
000006 //*********************************************************************
000007 //* DELETE/DEFINE BMC AMI LICENSE FILE
000008 //*
000009 //* JCL GENERATED BY TSOID01 ON 2001-05-17 AT 15:22
000010 //*********************************************************************
000011 //*
000012 //LFDELDEF EXEC PGM=IDCAMS
000013 //*
000014 //SYSPRINT DD SYSOUT=*
000015 //SYSIN DD *
000016 DELETE (TSOID01.License.File.New)
000017 SET MAXCC = 0
000018 DEF CL(NAME(TSOID01.License.File.New)
000019 IXD- Make any necessary edits, then enter the END command. A Confirm Submission window will be displayed over the Delete/Define and Initialize License File figure.
- Type Y in the Confirm Submission window and press Enter. The JCL to create your License File will be submitted.
- Enter the END command. The License File Selection figure will be displayed.
- After your job has completed with a good return code, type S in the Action field next to your new License File and press Enter. Your License File name will appear in the Current Selection field.
- Enter the END command.
- If you are a first-time user, the Main License Management figure will appear.
- If you are an established user, the Parameter Option figure will appear. To access the main License Management figure, enter the END command.
Verify the License File
In this step, you will use the LAU to verify which License File you will be using.
- Start the LAU by selecting the ISPF menu by executing the CLIST CWLMA. Because the LAU has been run before and a License File already exists, the Main License Management figure will be displayed. If the data set name of the License file that you want to use is displayed next to the Browse option, see Define Nodes.
Type 0 in the Option field and press Enter. The Parameter Option figure will be displayed.
Parameter Option figure
--------------------- BMC AMI License Management 17.02.00 -------------------
Option ===>
1) Select License File - TSOID01.LICENSE.FILE
2) Node Specify System Nodes
X) Exit Return to previous panel
(C) Copyright 2023, BMC Corp. All Rights Reserved.Type 1 in the Option field and press Enter. The License File Selection figure will be displayed.
License File Selection figure--------------------- BMC AMI License Management 17.02.00 -- Row 1 to 2 of 2
Command ===> SCROLL ===> PAGE
License File Selection
Current Selection:
Enter New DSN . .
(fully qualified without quotes)
Delete/Define . N (Y|N)
OR select below:-
Action DSN Added by
_ LICENSE.FILE1 USERID1 2000-08-07
_ LICENSE.FILE2 USERID1 2000-08-07
******************************* Bottom of data ********************************- Type S in the Action field next to the file that you want to use and press Enter. Your selected file should appear in the current selection field.
Define nodes
If your installation does not consist of multiple nodes in a JES network, or if you do not require the ability to route License Management work (Import, Export, or Reporting) from one JES node to another in your network, see Import License Certificate.
In this step, you will use the LAU to define (to LMS) the network nodes on which License Management maintenance or reporting tasks could be dispatched. If you are unsure of nodes defined on your system, system PARMLIB member JES2PARM contains NODE statements defined to JES.
Main License Management figure
Option ===>
0) Parameters Specify System Parameters
1) Browse License File - TSOID01.License.File
2) Update License File
3) IMPORT Import License Certificate
4) EXPORT Export License Certificate
5) Reports Run Reports
6) Disaster Enable Disaster Site
7) Emergency Emergency Password
X) Exit License Management
Copyright (c) 2023 BMC Corporation. All Rights Reserved.
Unpublished rights reserved under the Copyright Laws of the United States.
Enter HELP for Copyright/Trade Secret Notice information.
Type 0 in the Option field and press Enter. The Parameter Option figure will be displayed.
Parameter Option figure--------------------- BMC AMI License Management 17.02.00 -------------------
Option ===>
1) Select License File - TSOID01.LICENSE.FILE
2) Node Specify System Nodes
X) Exit Return to previous panel
(C) Copyright 2023, BMC Corp. All Rights Reserved.Type 2 in the Option field and press Enter. The Maintain Nodes Table figure is displayed.
Maintain Nodes Table figure
--------------------- BMC AMI License Management 17.02.00 -- Row 1 to 6 of 6
Command ===> SCROLL ===> PAGE
Maintain Nodes Table
Enter new node . . . ________
Description . . . . ____________________
OR
(C-Change,D-Delete)
Action Node Description Added by
_ Node1 Production TSOID01 2001-05-06 08:51
_ Node2 MVS Test1 TSOID01 2001-05-05 10:44
_ Node3 QA Test TSOID01 2001-05-22 10:38
******************************* Bottom of data ********************************- In the Enter new node field on the Maintain Nodes Table, specify the name of the network node you want to add to the display list. This name identifies your installation’s local JES in a network of systems or system complexes being used for network job entry (NJE) tasks. The node name can be up to eight alphanumeric characters.
- Describe the new node briefly in the Description field. This description can be up to 20 alphanumeric characters.
- Press Enter. The figure will be redisplayed with the new node in the selection list at the bottom of the figure. Repeat tasks step 3 through step 5 until you have defined all of the required nodes.
- Enter the END command. The Parameter Option figure will be displayed.
- Enter the END command again. The Main License Management figure will be displayed.
Import License Certificate
In this step the License Certificate for the BMC AMI product being installed will be imported into your site’s License File.
On the Main License Management figure, type 3 in the Option field and press Enter. The first of two Import License Certificate figures will be displayed.
First Import License Certificate figure
--------------------- BMC AMI License Management 17.02.00 -------------------
Command ===>
IMPORT License Certificate
Process DSN . : TSOID01.License.File
IMPORT From . . LICENSE.CERTIF__________________
(fully qualified without quotes)
Preview Only . . N (Y|N)
Reminder . . N (Y|N)- Type the name of the data set used for your License Certificate file (fully-qualified, without quotes) in the IMPORT From field.
Type N in the Preview Only field.
- If you type Y in the Reminder field you will see the message. If you type N, the reminder message will not appear.
Press Enter. The second Import License Certificate figure is displayed.
The second Import License Certificate figure
--------------------- BMC AMI License Management 17.02.00 -- Row 1 to 5 of 6
Command ===> SCROLL ===> PAGE
IMPORT License Certificate
Process DSN . : TSOID01.License.File
IMPORT From . . LICENSE.CERTIF
Preview Only . . N
Reminder . . N
Edit JCL . . . . Y (Y-Yes,N-No)
Jobcard:
//Job Card information line 1
//Job Card information line 2
//Job Card information line 3
//Job Card information line 4
Select Node Description
_ Node1 Production
_ Node2 MVS Test1
_ Node3 QA Test
****************************** Bottom of data ***********************- Type Y in the Edit JCL field.
Type the information for your job card in the four lines of the Jobcard field.
Type S next to the nodes on which you want the Import job to run. If no node is selected, the job is submitted without any specific routing.
Press Enter. The Edit JCL figure is displayed.
Edit JCL figure
File Edit Confirm Menu Utilities Compilers Test Help
-------------------------------------------------------------------------------
EDIT SYS98274.T095731.RA000.TSOID01.R0111344 Columns0000100080
Command ===> Scroll ===>CSR
************************************ Top of Data ******************************
000001 //Job Card information line 1
000002 //Job Card information line 2
000003 //Job Card information line 3
000004 //Job Card information line 4
000005//*
000006//*********************************************************************
000007//* IMPORT BMC AMI LICENSE CERTIFICATE
000008//*
000009//* JCL GENERATED BY TSOID01 ON 2001-07-08 AT 15:32:17
000010//*********************************************************************
000011//*
000012//IMPORT EXEC PGM=LMALFIM,
000013// PARM=’UPDATE’
000014//STEPLIB DD DSN=LM.DEVL.LOAD,
000015// DISP=SHR
000016//*
000017//CWLF0000 DD DSN=TSOID01.License.File,
000018// DISP=SHR
000019//CWLFIMP DD DSN=LICENSE.CERTIF,- Make any necessary edits, then enter the END command. A Confirm Submission window will be displayed over the second Import License Certificate figure.
- Type Y in the Confirm Submission window and press Enter. The JCL to create your License File will be submitted.
- Enter the END command. The Main License Management figure is displayed.
- Type X in the Option field and press Enter to exit the LAU.
Sample LMS Parameters data set
You will find a sample LMS parameter data set in the sample data set shipped to you and installed with ECC. The member name is LMCL00 and should be used as a skeleton for parameters for you particular installation. Since this member can change with PTF maintenance, it is not listed here.
In releases of LMS prior to 16.05, the LMINPARM member found in the hlq.SLMSCNTL library was customized. For the current release of ECC, the hlq.SLCXCNTL library contains an additional module, LMCL00, which needs to be customized. This module reads from the common PARMLIB data set. If you are an established user, compare the existing LMINPARM member with the LMCL00. You should only see one new parm: LICENSE_DSNAME. You may be able to simply copy the previous parm into the LMCL00 member if they are the same. If you copied your previous release’s LMINPARM member to LMCL00, add the LICENSE_DSNAME parm, in which you should include the name of your license file.
However, please be aware of any additional parms that may be added due to maintenance for ECC release 17.02.
- To ensure access to BMC AMI products is automatically enabled, establish a procedure in your SYS1.PROCLIB to launch your CMSC as a started task during IPL and IML processing. Consult your site’s MVS system programmer for details. Edit the sample proc provided in SLCXCNTL(CMSC). Change the data set names to match those used at your site, including the PARMLIB data set you saved your site specific LMS parameter data set.
- Specify the license file data set name in the LMCL00 member, under the LICENSE_DSNAME parameter.
- 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. Refer to CMSC Start-Up Parameters.