Why are the CA7 job run timestamps different in AAI compared to SMF Records?
Article ID: 273414
Updated On:
Products
Issue/Introduction
Why are the CA7 job run timestamps different in AAI compared to SMF Records?
Environment
Release : 6.4.6.1
Resolution
AAI uses the event timestamps in the RPT70 files, which is a report that is run in CA7, and not the SMF record.
It is expected that the timestamps in the RPT70 files that AAI processes may not match the SMF record.
The event timestamps in the RPT70 report are based on the time the event is written to the log where as SMF records are in memory. So it is expected that these timestamps do not match. The time difference can be greater when CA7 is under a heavier load.
In Detail:
For CA 7 the sequence of processing is as follows:
o SMF record is captured and stored in memory
o The ICOM component of CA 7 (separate task) processes the SMF record in memory and writes it to a dataset (COMMDS) for CA 7 to pick up (may take several seconds for ICOM to get to processing the record in memory)
o CA 7 task reads the SMF record from the COMMDS dataset and passes it to the Job Completion Processing sub-task (may take several seconds before CA 7 processes entries from the COMMDS dataset)
o The Job Completion Processing sub-task marks the job entry in CA 7 as complete and creates the CA 7 LOG record using the time it marks the job as complete
o This is the LOG record produced in the RPT70 data file
Feedback
