Skip to Content

 

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for IMS Offline 5.6.

Summarized IRUFs

The TASCOSTR summarization program creates summarized IRUFs from one or more detailed IRUFs, one or more summarized IRUFs, or any combination of detailed and summarized IRUFs.

For a description of the TASCOSTR program, see IRUF-summarization.

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. For example, terminal records are summarized by LTERM name within 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. 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.
Warning

Note

Because transactions from different users can be processed in one program scheduling, the BMC AMI Ops Monitor for IMS Offline customer ID is not used in program records.

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 wh

ich 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

GUID-DADF7E53-6CD5-4722-B88A-9E06A5C979F0-low.png

Related topic

IMS resource utilization files (IRUFs)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for IMS Offline 5.5