Previous Topic: Modify RACFNext Topic: Start CAIRIM

CAIRIM Configuration › LMP Seat License Registration Setup

LMP Seat License Registration Setup

CA Technologies Products can use the LMP Seat License Registration common service to perform these actions:

LMP Seat License Registration is used with the existing license management common service that uses LMP keys for each licensed CA Technologies product.

The IBM z/OS Product Registration component is used to record and report on maximum concurrent product usage for a specified time period. Therefore, the LMP Seat License Registration common service can use facilities and procedures that are already on your system to validate seat license usage. Reporting on maximum concurrent seat license use for any CA Technologies product which requires validation is a relatively easy task to perform.

Important! Verify that SMF is recording type 89 records.

Use the IBM standard utility program IFAURP to produce a report to validate the maximum number of concurrent users of a CA Technologies product. IFAURP uses the SMF type 89 records that the z/OS Product Registration component produces. Verify that SMF type 89 records are being recorded on each z/OS system that IFAURP lists in the Software Product Registration Report. For information regarding the use of IFAURP, see the IBM publication titled z/OS MVS Product Management.

Specification of which SMF records to record is made in the logical PARMLIB SMFPRMxx member. The IFAURP report utility requires the SMF type 89, subtype 2 records as input. Select SMF type 89 in the SMFPRMxx member, or minimally, select the SMF type 89, subtype 2 records. For information describing recording of SMF type 89 records, see the IBM publication titled z/OS MVS System Management Facilities (SMF).

Typically an installation has existing procedures and methodologies for collecting and archiving the SMF records for later retrieval and reporting. Verify that the SMF type 89, subtype 2, records are included in the installation managed SMF historical data sets. Keep these records for at least as long as the required reporting period of the Software Product Registration Report.