Why you may be seeing the CA-7.3XXX STOPPING CAPTURE OF SMF nn RECORDS messages between IPLs.

Products

• CA 7 Workload Automation

Issue/Introduction

If you see the CA-7.3XXX STOPPING CAPTURE OF SMF nn RECORDS message between IPLs of your system, this means that for some reason, CA 7 has encountered a situation where too many SMF records have become chained in CSA and will no longer do so. This document discusses one reason we have found for this message being repeatedly logged between IPLs.

 

 

Environment

Release:
Component: 7

Resolution

Some clients initialize more than one copy of CA 7 with the CAS9 CAIRIM procedure. This is not an issue if you either have an ICOM started for each instance or if you do not specifically have SMF(26) on the ADD statement for that instance in the sysfile (data set named on the L2OPTS DD in the CAS9 CAIRIM procedure).

If you do have SMF(26) on an "inactive" instance of CA 7, then you are collecting SMF 26 (job purge) records for the that instance (by default that would not happen). All SMF type 26 records are collected, not just for CA 7 submitted tasks.

ICOM is the facility that writes the records to the Communications Data Set (UCC7CMDS DD in CA 7 and ICOM procedures) and deletes them from CSA. Thus each instance of ICOM takes care of all records for the CA 7 instance that submitted the jobs and all 26 records for every task.

Even though you don't start a second instance of CA 7, SMF type 26 records are still being collected for this instance and chained in CSA and there is just no ICOM to write them to the UCC7CMDS and free the CSA. 

Remove the SMF(26) from the ADD statement for the inactive CA 7 instance using CAS9 CAIRIM.

 

Additional Information

For more information on the CAS9 CAIRIM initialization of CA 7.