6. DATA SOURCES › 6.10 APPC/MVS Overview › 6.10.1 APPC/MVS Transaction Events and Measured Intervals

6.10.1 APPC/MVS Transaction Events and Measured Intervals

APPC/MVS ASCH-scheduled Transaction Programs (TPs) are
allocated by a partner TP, either from the same local MVS
environment or from another TP somewhere in the SNA network.

APPC/MVS ASCH-SCHEDULED TP TIME STAMPS

  The SMF type 33 TP Accounting records contain time stamps
  that trace the TP request from the first moment that
  APPC/MVS becomes aware of the request through the
  termination of the conversation.  The CA MICS data elements
  that record event time and date stamps in the APPC/MVS
  Transaction file, (BATATP), are shown below:

           RDRTS    - Reader Time Stamp
           ATPSCHTS - Scheduled Time Stamp
           STARTTS  - Start Time Stamp
           ENDTS    - End Time Stamp

  For standard TPs and the TP portion of multi-trans TPs:

  o Reader Time Stamp (RDRTS) is the date and time that the
    APPC address space first became aware of the inbound TP
    allocation request.

  o Scheduled Time Stamp (ATPSCHTS) is the date and time that
    the ASCH scheduler placed the requested TP in the
    execution queue.

  o Start Time Stamp (STARTTS) is the date and time that the
    requested TP began execution and the conversation.

  o End Time Stamp (ENDTS) is the date and time that the
    conversation terminated.

  For the shell portion of multi-trans TPs:

  o Reader Time Stamp (RDRTS) is missing.

  o Scheduled Time Stamp (ATPSCHTS) is missing.

  o Start Time Stamp (STARTTS) is estimated by subtracting
    the shell's TP TCB+SRB CPU Time (ATPCPUTM) and Total
    Device Connect Time (ATPTCNT) from ENDTS.

  o End Time Stamp (ENDTS) is the time the SMF type 33 record
    was written to the SMF buffer.

  The SMF type 33 record does not record any date/time stamp
  values for the shell portion of multi-trans TPs.  The shell
  portion cannot be attributed to a request for the TP's
  execution.  The TP Type (ATPTYPE) data element identifies
  the TP type as 'STP', 'MTP', or 'MSH' for standard TPs, TP
  portion of multi-trans TPs, or shell portion of multi-trans
  TPs, respectively.

APPC/MVS ASCH-SCHEDULED TP MEASURED INTERVALS

  The measured intervals for APPC/MVS ASCH-scheduled TPs are
  derived from the time stamps mentioned above.  They are:

           ATPTNSTM - APPC Transit Time
           ATPINQTM - ASCH Queue Time
           ATPEXCTM - TP Execution Time
           ATPTRSTM - Total Response Time
           ATPAVTTM - Average Response Time

  For standard TPs and the TP portion of multi-trans TPs:

  o APPC Transit Time (ATPTNSTM) contains the time an inbound
    request spent in the APPC/MVS address space before being
    sent to the ASCH address space for scheduling, that is,
    ATPSCHTS -RDRTS.

  o ASCH Queue Time (ATPINQTM) contains the total elapsed
    time APPC/MVS Transaction Programs (TPs) spent in the
    APPC/MVS Scheduler waiting for an initiator, that is,
    STARTTS - ATPSCHTS.

  o TP Execution Time (ATPEXCTM) contains the total elapsed
    time the APPC/MVS TP executed; that is, ENDTS - STARTTS.

  o Total Response Time (ATPTRSTM) is the sum of ATPTRSTM,
    ATPEXCTM, and ATPEXCTM; that is, ENDTS - RDRTS.

  o Average Response Time (ATPAVTTM) is equal to Total
    Response Time (ATPTRSTM) in the BATATP file DETAIL
    time-span.  At summarized time-spans, ATPAVTTM is the
    Total Response Time (ATPTRSTM) divided by TP Count
    (ATPCOUNT).

  For the shell portion of multi-trans TPs:

  o APPC Transit Time (ATPTNSTM) is missing.

  o ASCH Queue Time (ATPINQTM) is missing.

  o TP Execution Time (ATPEXCTM) is estimated as ENDTS -
    STARTTS.

  o Total Response Time (ATPTRSTM) is equal to ATPEXCTM.

  o Average Response Time (ATPAVTTM) is equal to Total
    Response Time in the BATATP file DETAIL time-span.  At
    summarized time-spans, ATPAVTTM is the Total Response
    Time divided by TP Count (ATPCOUNT).

  The APPC Transit Time (ATPTRSTM) and ASCH Queue Time
  (ATPINQTM) data elements represent the time required to
  allocate and initiate the conversation.  TP Execution Time
  (ATPEXCTM) is variable and depends on the nature of the TP
  executed.