Detailed IRUFs

The Log Edit program IMFLEDIT creates detailed IRUFs from IMS log data. IMFLEDIT processes program and transaction records written to the IMS log by the Event Collector and also (optionally) selected records written by IMS.

IMFLEDIT can use the IMS log directly as input, or a subset of the log can be created and used instead (see Log-Edit-input-data).

Detailed IRUFs contain the following record types:

  • Transaction accounting records (TARs), built from Event Collector transaction records written to the log (one record per processed transaction)
  • Program accounting records (PARs), built from Event Collector program records written to the log (one record per program execution)
  • Terminal (LTERM) accounting records (LARs), built from IMS start, IMS checkpoint, IMS stop, and Event Collector records, combined with ETO terminal signon/signoff records and dial-up terminal logon and logoff records (one record per terminal session)

Note

Dial-up terminals are assumed connected from logon to logoff (or until last action if there is no logoff). Leased lines are assumed connected from IMS startup until shutdown (or until the last system activity if there is no IMS shutdown).

The attributes of each of these three record types are described in IRUF-record-layout-descriptions.

Related topic

IMS resource utilization files (IRUFs)

 

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