How to omit the writing of usage data in SMF30 records

Products

• CA 1 Tape Management
• CA 1 Tape Management - Copycat Utility
• CA 1 Tape Management - Add-On Options
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Datacom
• DATACOM - AD
• MICS Resource Management
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description:

CAIRIM feature LMPAM=YES|NO provides ability to control writing of SMF 89 records.

Solution:

The option LMPAM was introduced in CA Common Services r11.0 with CAIRIM APAR# RO00593. Details on this enhancement was initially documented in PDC RI00594.

This feature is delivered as part of the installation of the CAIRIM components in all subsequent CA Common Services releases. By default, the feature is automatically enabled and establishes a foundation for the collection of SMF records that you will use for assisting in the periodic reporting of CA software utilization. The feature is provided for mainframe z/OS customers that have selected site license keys for managing/controlling the use of CA software in their organizations. Basically CA product LMP key checks will cause SMF 89 usage data records to be generated. As a result, an IBM IFAUSAGE report can be run to identify what CA product(s) executed on the system.

Note: This feature is only presented to identify what CA product(s) executed by means of whether an LMP check being made. There is no actual "usage" data collected.

A Usage section is generated in the SMF type 30 record for each product that registers with IFAUSAGE. There is no single trigger in SMF to suppress this section. As long as products are registered, there will be Usage sections collected for those products.

You have two possibilities to avoid writing usage data in SMF30 :

1. Define LMPAM=NO in the CARIMPRM member and schedule an IPL. No SMF89 records will be written for CA products as a result of an LMP check being issued and no usage SMF30 data
   
   
2. Define LMPAM=YES (default) and set the SMF parameter NOMULCFUNC in dataset SYS1.PARMLIB(SMFPRMxx), which indicates that users of the IFAUSAGE service that registered specifying SCOPE=FUNCTION do not need to use IFAUSAGE with the REQUEST=FUNCTIONxxx parameters, or enter:
   
   SETSMF NOMULCFUNC

This allows a measured usage program using SCOPE=FUNCTION to record only its registration data and omit recording the usage data. The default for this parameter is MULCFUNC, so the usage data will be written by default. The normal number of SMF30 records seem to be not increasing, but the length of eachrecord is increasing. So most customers do not recognize it.

Environment

Release: CA90SV00200-14-Common Services-for z/OS
Component: