CICS has native support (CMF - CICS Monitoring Facility) for
generating SMF records documenting errors, transaction detail
(performance class), and region interval activity. These can (and
usually do) go to SMF, but can go to other log files. Other monitors
have that capability of capturing this same information and writing
the data to their own style of data stores.
Note that transaction detail records are written by each CICS region
that processes any portion of a transaction (MRO). So your have the
choice of reporting activity within a single region or consolidating
all transaction detail segments by unit of work ID.
Performance class detail records (110.1.3) are self-defining records
based on the CMF dictionary records (110.1.1) and an array of bytes
in the header portion of the 110.1.3 records that document what
statistics are to be written out for a CICS region.
Net of all this that generating that file single-record
-per-"transaction" is non-trivial. For CMF (110) records, the most
popular tools are MXG and MICS. The other CICS moniotoring vendors
have their own facilities for generating reports transaction detail.
Michael
At 02:40 PM 8/2/2021, you wrote:
I've worked at a number of mainframe installations, and at many of
them I've encountered a dataset that logs usage of CICS
transactions. Usually it's a GDG, either weekly or monthly, wherein
each record contains a transaction, a user ID and a count. I'm not
a CICS support guru -- in fact in my 15 years of COBOL development,
before I got into security, somehow I managed to avoid CICS even on
the coding side -- so I'm ignorant of how it was done, but I surmise
CICS can produce this log periodically. Can anyone tell me how it's invoked?
Or if you're about to tell me it's not CICS but SMF, then a
different question: Last I heard, SMF records are VBS and REXX
won't read VBS records. How does one cross that bridge? Is there
an SMF utility that can be persuaded to write out selected records
in some other RECFM?
---
Bob Bridges, [email protected], cell 336 382-7313
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
