Limited supportBMC 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, seeBMC AMI Ops Monitor for IMS Offline 5.5.

Data collection and preparation

MainView for IMS Offline includes all the tools needed to collect and prepare data for use as input to the MainView for IMS Offline reports.

The Event Collector captures data on IMS activity as it occurs and writes this information to the IMS system log as MainView for IMS transaction and program records. The amount of data collected for and stored in each record is determined by several data collection options specified to the Event Collector

The IMS system log data is processed by the MainView for IMS program IMFLEDIT (see Log-Edit), which extracts the MainView for IMS records and some data from IMS log records and stores the data in a detailed IMS resource utilization file (IRUF; see IMS-resource-utilization-files-IRUFs). The detailed IRUF contains one record for each transaction or program activity and one record for each logical terminal generated in IMS.

Information in an IRUF can be summarized (through the TASCOSTR program; see IRUF-summarization) for a time period, such as one day. Data is grouped into the following record types: Abstracted data is grouped as follows:

Group

Description

Terminal record

Summarized information for each logical terminal within a customer/user category per summarization period

Program record

Summarized information for each program within the summarization period

For example, one program accounting record per program per day.

Transaction record

Summarized information for each transaction code within a customer/user category per summarization period

For example, one transaction accounting record per transaction code within a customer/user category.

In addition to summarizing IRUF data, you can create a subset of an IRUF (an extracted IRUF) by using the PRSSELEC utility. For more information about PRSSELEC, see IRUF-utilities.

The Performance Reporter (see Performance-Reporter-overview) and the Transaction Accountant (see Transaction-Accountant-overview) use any form of an IRUF to analyze data and create reports.

Tip

BBSAMP member IMFIRUF provides an IRUF creation and reporting strategy and refers to other BBSAMP members that you can use to implement the strategy.


Related topic

MainView for IMS Offline overview


 

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