Flow of the offline process
The following figure depicts the flow of the BMC AMI Ops Monitor for IMS Offline process:
Related topic
Event Collector collects IMS data
The Event Collector writes the collected data to the IMS log as transaction records (X'FA') and program records (X'F9').
The transaction and program log records contain detailed information about elapsed timings, CPU usage, DL/I database calls and I/O per database, Db2 subsystem requests per application plan, and MQ transactions. Most resource usage data is captured at the transaction level and can therefore be attributed to the user.
For more information see:
Run Log Edit (IMFLEDIT) to create an IRUF
Log Edit is run against the IMS log to extract, edit, reformat, and write the data to an IMS resource utilization file (IRUF).
The IRUF created by Log Edit contains transaction, program, and terminal accounting records in detail format, one record per event.
For more information see:
(optional) Run TASCOSTR to summarize an IRUF
Input to TASCOSTR can be one or more detailed IRUFs, summarized IRUFs, extracted IRUFs, or any combination of these. All input to TASCOSTR must be combined before processing.
During processing, TASCOSTR calls a sort program to sort the input. TASCOSTR can use any sort program compatible with DFSORT.
The summarized IRUF created by TASCOSTR contains one record for all transactions of the same type, submitted by a single customer ID, contained in the input IRUF (or IRUFs).
For more information, see Summarized-IRUFs.
(optional) Run PRSSELEC to extract specific IRUF information
The file of selected IRUF records that PRSSELEC produces is a subset of an IRUF known as an extracted IRUF.
For more information, see IRUF-utilities.
Run programs to create reports
Performance Reporter produces reports and plots that you can use to evaluate the performance of IMS and its applications.
Transaction Accountant produces reports that provide a detailed breakdown of IMS resource usage and usage rates that can be assigned an equivalent monetary value. The Transaction Accountant also produces a summary of IMS activity, grouped by customer, customer/transaction, or transaction.
The Transaction Accountant can produce reports independently, or it can be interfaced with a site accounting system.
The print utility PRSPRINT executes as a batch program. The utility produces a formatted report of the records read from an input IRUF.
For more information see: