Summarized IRUFs
Summarized IRUF records contain only cumulative information. The record types (transaction, program, and terminal) contain information for the entire time period being summarized, not just for a single execution run. For example, terminal records are summarized by LTERM name within the BMC AMI Ops Monitor for IMS Offline customer ID. One record per BMC AMI Ops Monitor for IMS Offline customer ID quantifies all resource usage and reflects all activity that has occurred for an individual terminal in the specified time span. The time span is determined by the data in the input IRUF.
A major benefit of TASCOSTR summarization is that it substantially reduces the volume of records that must be processed, yet retains much of the critical information about transactions, programs, and terminals.
Summarization for each record type is as follows:
- Transaction records are summarized by customer ID and transaction code.
- Program records are summarized by program name.
- Terminal (LTERM) records are summarized by customer ID and LTERM name.
The following figure shows how six detail transaction records can be reduced to three summarized transaction records. In this example, two separate customers (Customer 1 and Customer 2) submit transactions to the IMS environment.
Customer 1 submits three transactions (1, 3, and 6) under the same transaction code (ABC). These three transactions are later summarized into a single record for Customer 1. This summarized record contains the BMC AMI Ops Monitor for IMS Offline customer ID and the transaction code ABC. The transaction code indicates that three occurrences of the particular transaction code existed for Customer 1 over the time span of the input data. The detail transaction records for these three transactions indicate the specific start and stop time for each occurrence of the transaction code. The summarized record for this transaction code for Customer 1 identifies the time span in which the transaction code occurred.
For example, the start time in the summarized record indicates the time, within the time span of the input data, of the first occurrence of a particular transaction code for a designated customer; the end time indicates the last time, within the time span of the input data, that the transaction code occurred for this customer.
Similarly, the transactions (2 and 5) submitted by Customer 2 are summarized into a second IRUF record, and transaction occurrence number 4 is summarized into a third IRUF record.
Example of IRUF summarization
IRUF summarization
A detailed IRUF can be summarized by using the TASCOSTR program.
You can create the JCL for TASCOSTR:
- Manually by using the provided information
- Online by using the JCL Generator (see JCL-Generator)
IRUF summarization overview
A summarized IRUF contains information derived from measurements made on a cumulative basis rather than on a one-to-one basis. When a detailed IRUF is processed to create a summarized IRUF, information is summarized so that the three IRUF record types contain information covering the entire time period of the input IRUF, not just a single process or execution.
For more information about IRUFs and summarization, see IMS resource utilization files (IRUFs).
Additionally, you can create an extracted IRUF from a detailed or summarized IRUF. For information about using the PRSSELEC utility to create an extracted IRUF, see IRUF utilities.
The following figure illustrates the summarization process:
Effects of summarization on accounting records
The types of accounting records are affected by the summarization process in the following ways:
Transaction accounting record (TAR)
Transaction accounting records are summarized by transaction name within BMC AMI Ops Monitor for IMS Offline customer ID.
One record for a transaction per BMC AMI Ops Monitor for IMS Offline customer ID quantifies all costs and resource usage on that transaction for the time period covered by the input IRUF or IRUFs.
In each summarized transaction accounting record, the database and terminal segments are summarized by unique identifiers. Each unique DBD name accessed by the transaction, has its own database segment. Each LTERM from which the transaction was submitted, has its own terminal segment.
Terminal (LTERM) accounting record (LAR)
Terminal accounting records are summarized by LTERM name within BMC AMI Ops Monitor for IMS Offline customer ID. One record for a terminal per BMC AMI Ops Monitor for IMS Offline customer ID quantifies all resource usage for that terminal according to the time period covered by the input IRUF or IRUFs.
Program accounting record (PAR)
Program accounting records are summarized by program name. One record for a program name quantifies all resource usage by that program for the time period covered by the input IRUF or IRUFs.