Fields in the Monitor-Overhead report

The following example shows a sample of a Monitor-Overhead report.

IMS MONITOR   ****MONITOR OVERHEAD****        TRACE START 1989 076  12:42:54     TRACE STOP 1989 076  12:43:07 PAGE 0013
MONITOR OVERHEAD DATA                                                                                                     M
_____________________                                                                                                     M
      13144 MILLISECONDS, TRACE INTERVAL
        550 MILLISECONDS, MONITOR MODULE TIME
        853 MONITOR RECORDS WERE PRODUCED
        645 MICROSECONDS PER MONITOR ENTRY

The meaning of the various fields in the report is as follows:

TRACE START and TRACE STOP

The trace start and trace stop fields tell you the time when the DB Monitor program was last started and stopped. The time is generated by the time-of-day clock. Clock times are read as follows:

Clock time = hh.mm.ss

Where:

hh: Hours 0 through 23
mm: Minutes
ss: Seconds

If the DB Monitor was on during an entire batch run, the trace start and trace stop times are the times at which the batch run started and stopped. If the DB Monitor was turned on and off more than once in the same batch run, the trace start and trace stop times are the times at which the monitor was last started and stopped.

MILLISECONDS, TRACE INTERVAL

This field describes how long the monitor was turned on.

MILLISECONDS, MONITOR MODULE TIME

This field describes, during the time the monitor was turned on, how long code in the monitor was actually being executed. (During this time, no IMS code can be executed, so this field tells the real overhead for using the monitor.)

MONITOR RECORDS WERE PRODUCED

This field describes how many records the monitor wrote.

MICROSECONDS PER MONITOR ENTRY

This field describes the average length of time it took the monitor to write a record.