Merging Statistics Records

When STIGNCPU is set to Y (in the CTMPARM member of the IOA PARM library), the statistics merge functionality takes affect during the following execution of CTMJSA, only for jobs where a job occurrence causes the statistics file to be updated. In such a case, all the job's records, with the various CPU indicators, are merged into a single record. The merge process creates a new statistics record (whose CPUid field is set to binary zeros) for this job and up to 20 (or whatever the STENT# parameter in the CTMPARM member in the IOA PARM library is set to) slots are filled by the participating job's records. When a maximum of STENT# entries is reached the merge process for that job is terminated even if there exist later (by date) job occurrences on the same or other job records for that job.

On the following execution of CTMJSA, the later job occurrences might be accumulated, but only if the date-range of the utility is properly set to pick them up and the LOG file still contains the messages (SPY281) for these job occurrences.

BMC therefore recommends that when specifying STIGNCPU=Y that you do one of the following:

• increase STENT# to accomodate all the old merged statistics records on a single enlarged statistics record
• set the FROMDATE parameter, when accumulating statististics via CTMJSA, to enable the date-range to capture any late job occurrences that might not have been picked up in the original merge process.

Note: The size of the IOA LOG file might need to be increased to accommodate additional days of messages.