Starting and stopping the server and client

This topic explains how to start and stop the LMS server and the LMS client.

Starting the Server

You must submit batch JCL or issue a START command to initiate the LMS server. Example JCL for each of these types of executions are shown below.

If you have CERTVER<03.00.00> licenses, you are not free to execute the LMS server on any LPAR you choose. You can run the server only on the LPAR that is defined in the SERVER section of your license certificates. The SERVER_ID<> entry specifies the LPAR on which the server can run. If you have only CERTVER<01.00.02> or CERTVER<02.00.00> license certificates, then you may execute the LMS server on any LPAR in your enterprise.
For example, if your SERVER_ID<> specifies:

You must execute the server on the operating system image named ZOS1 (this is the CVTSNAME), on the LPAR named LPAR1, on the CEC with serial number nn5D0A (note that the first two digits of the last 6 digits of the serial number are ignored). If you wish to run your server on another system, LPAR or CEC, you must contact BMC and obtain another license certificate which carries the desired SERVER_ID<> parameters.

Batch JCL for Starting the LMS Server

You need to add a JOB statement to this JCL and change the data set names used in this example. See Server Start-up Parameters for more details about server startup parameters.

Started Task Procedure for Starting the LMS Server

You must change the data set names used in this example, and you must create the data set which contains the server parameters. See Server Start-up Parameters for more details about server startup parameters.

Ensuring that the Server is Executing

You may browse the SYSPRINT data set at any time using SDSF or an equivalent facility. An example of a successful server initiation is shown below:

The presence of the last message, LMZ302I, indicates that the server has successfully initialized and is ready to receive sessions from LMS client systems and the LMUSER interface.

Stopping the Server

You can stop the LMS server by entering the following on the system console or from an SDSF (or equivalent) TSO screen:
P jobname

What Happens When the Server is Stopped

You may still run BMC AMI products on an LPAR even though the LMS server has been stopped, but any product licensed with a Product/MSU license will enter the 72 hour server grace period. You must restart the server within this time limit. If 72 hours elapse and the server is not started, BMC AMI products cease to execute.

LMSINIT Client Parameters

These parameters are documented here as they only apply to the CLF environment.

LICENSE_SERVER_NAME()

Specify the name, as defined in the domain name server used by this mainframe, of the TCP/IP on the LPAR on which you are running the LMS license server.

LICENSE_SERVER_ADDR()

Specify the address, in dotted decimal notation, of the TCP/IP on the LPAR on which you are running the LMS license server. Dotted decimal notation takes the form nnn.nnn.nnn.nnn, where nnn is a decimal number ranging from 1 to 255.

LICENSE_SERVER_PORT()

Specify the port number on which the LMS server program is listening. This value MUST MATCH the value you specify in the LMZINIT parameters (which control the server execution). If these values do not match, then communication between this client and the server will not occur. The port is a decimal number from 4096 to 65535.

LPAR_MODE()

Specify the mode of sub-capacity licensing you want for this client LMS subsystem. The two choices are SIZE and UTIL. SIZE is the default and indicates that the capped size of the LPAR in MSUs is to be used as the determining factor in license conformance. UTIL can be specified to indicate that the current rolling 4-hour average MSU utilization of the LPAR is to be used as the determining factor in license conformance.

LMS 3.0 and 3.1 supported only LPAR_MODE(SIZE).

You may specify LPAR_MODE(SIZE or LPAR_MODE(UTIL).

If you wish, you may spell out utilization by specifying LPAR_MODE(UTILIZATION).

If this parameter is omitted, the LPAR_MODE(SIZE) is used by default.

If you are using an existing CLF environment (LMS 3.0 or 3.1) and you want to upgrade to LMS 4.0 using the utilization mode of licensing, then you must specify LPAR_MODE(UTIL).

LPAR_PRIORITY()

Specify the priority of this client LMS with respect to all other clients in a CLF environment. This is a value from 0 to 255. The higher the number the greater the priority of the client. When it has been determined that the sum of all LPAR’s rolling 4-hour average utilization exceeds the licensed amount, a product or option must be placed into a 14-day LPAR MSU utilization grace period. The choice of which LPAR is based upon this parameter. A very high number, 255 for instance, indicates that this is the last LPLAR to be eligible for the grace period. You would use this value for your production systems. A very low value, 0 for instance, indicates that this is the first LPAR to be chosen for the utilization grace period. You might specify this value for your test or development systems. If more than one LPAR has the same value, then the order that the clients connected with the server determines which LPAR will enter grace.

If this parameter is omitted, then a priority of 0 (very low priority) is used by default. If no LPARs in the CLF environment specify a priority, when an LPAR must be chosen to enter the 14-day utilization grace period, the LPAR which reported an MSU utilization value that caused the license value to be exceeded, will be put into the 14-day grace period.

ARM(YES|NO)

Specify ARM(YES) if you want Automatic Restart Management to be activated. Specify ARM(NO) or ARM() if you do not. ARM(NO) is the default if this parameter is omitted.

ARM_ELEMENT_NAME(xxxxx... . .xxxxxx)

Specify a sysplex unique 1-16 character name to be associated with this CLF client or server. This name must be different for the server and for each client. We strongly recommend that you use the following naming convention:
Bytes 1-3 C’LMS’
Bytes 4-7 **your SMF system ID**
Bytes 8-16 Any name of your choice but it should indicate “client” or “server”

Starting the Client

You must submit batch JCL, or issue a START command to initiate the LMS 3.0 client on each LPAR that run BMC AMI products. Below are examples of JCL for each of these types of execution.

Batch JCL for Starting an LMS Client

You need to add a JOB statement to this JCL and change the data set names used in this example. See the License Management System 4.0 User/Reference Guide for a discussion of the LMS client parameters in the section “Creating Runtime Environment”.

Started Task Procedure for Starting an LMS Client

You must change the data set names used in this example and create the data set which contains the server parameters. See the License Management System 4.0 User/Reference Guide for more information on the LMS client parameters.

Ensuring that the Client is Executing

Below is an example of the SYSPRINT data set that is created by each LMS client. Note that the parameter values are for this example only and should not be used in your environment.

To stop a client

You can stop an LMS client by entering the following on the system console, or from an SDSF (or equivalent) TSO screen:

What happens when the LMS client stops?

You may still run BMC AMI products on an LPAR even though the LMS Client for that LPAR has been stopped, but products licensed with Product/MSU licenses will enter the 72-hour server grace period. You must restart the client on each LPAR within this time limit. If 72 hours elapse and the client is not started, BMC AMI products cease to execute.