Calculation of IMS elapsed processing time

The user-selected timings are calculated with the timestamp definitions shown in the following table:

Timestamp	Definition
Arrival Time	Arrival time of the transaction For full-function transactions, the arrival time is taken from the X'03' log record, which contains the time the message arrived on the message queue. For Fast Path transactions, the arrival time is taken from the X'FA' record. For message switches, the arrival time of both the message switch transaction and the original input transaction are available.
Start Time	Start of transaction processing The X'FA' record contains the start time for all types of transactions: full function, Fast Path, message switches, and multiple systems coupling (MSC).
Message Insert Time	Enqueue of a (first) response to the originating terminal (X'35')
Stop Time	End of transaction processing The X'FA' record contains the stop time for all types of transactions: full function, Fast Path, message switches, and MSC.
Message Sent Time	First attempt to transmit response. (communications get unique, X'31'); for Fast Path, the 5936 log record is used If this time exceeds the maximum specified by the Log Edit parameter in BBPARM member IMFLEP00, collection stops and the maximum is assigned (see the Log Edit Input Parameters section in the Log Edit topic of ).
Message DequeueTime	Free of the response message (transmission time completed, X'33'); for Fast Path, the 5936 log record is used If this time exceeds the maximum specified by the BMC AMI Ops Monitor for IMS Offline Log Edit parameter in BBPARM member IMFLEP00, collection stops and the maximum is assigned (see the Log Edit Input Parameters section in the Log Edit topic of ).

Important

A special case concerning elapsed times can occur with some applications, especially with BMPs or JBPs. BMC AMI Ops Monitor for IMS Offline defines transaction elapsed time as the amount of time that elapses between one MESSAGE GET UNIQUE and the next MESSAGE GET UNIQUE. If a program continues processing after the final MESSAGE GET UNIQUE that received a QC status code (no more transactions), the resources that were used during that processing are charged to the last transaction.

This situation could result in a transaction with a very short elapsed time showing very high resource usage. Such a transaction could cause warning messages to be produced during the Log Edit process if the accumulated CPU time exceeds the transaction elapsed time. The program elapsed time continues through program end.

The following figure shows elapsed time examples for a terminal-entered transaction (transaction A) and for a message-switch transaction (transaction B):

TRANS. A *      *     *     *      *     *     *
          *      *     *     *      *     *     *
          ---------------------------------------
          *      *     *     *      *     *     *
          *      *     *     *      *     *     *

         Orig. Start Msg MsgSw   Stop Msg   Msg
       Arrival      Insert Insert        Sent Free

          *INPUTQ*                  *
          *ARIV- *                  *
          *START *    ELAPSED       *
          *|-----||----------------|*
          *           ARIV-STOP     *
          *|-----------------------|*
          *       RESPONSE                *
          *|-----------------------------|*
          *      RSP TO DEQ                     *
          *|-----------------------------------|*
          *                               *DE- *
                       *      OUTPUT Q    *QUEUE*
                       *|-----------------||---|*
                       *        OUT TO DEQ      *
                       *|----------------------|*

TRANS. B                     *      *     *     *     *     *
(Message Switch)             *      *     *     *     *     *
                             --------------------------------
                             *      *     *     *     *     *
                             *      *     *     *     *     *

                           MsgSw Start Msg   Stop Msg   Msg
                         Arrival       Insert       Sent   Free

                             *      *           *
                             *INPUTQ*   ELAPSED *
                             *|----||----------|*
     *      ARIV-START       *
     *|----------------------------|*
     *      ARIV-STOP                           *
     *|----------------------------------------|*
     *      RESPONSE                                  *
     *|----------------------------------------------|*
     *      RSP TO DEQ                                      *
     *|----------------------------------------------------|*
                                         *            *DE- *
                                         * OUTPUT Q   *QUEUE*
                                         *|----------||----|*
                                         * OUT TO DEQ      *
                                         *|----------------|*

Calculation of IMS elapsed processing time

BMC AMI Ops Monitor for IMS Offline 5.6

On this page