6. DATA SOURCES › 6.10 APPC/MVS Overview › 6.10.2 APPC/MVS Transaction Response Time › 6.10.2.2 Summary APPC Transaction Response Time Analysis

6.10.2.2 Summary APPC Transaction Response Time Analysis

For CA MICS timespans other that DETAIL, the Application
Unit Identifier (ATPAPU), TP Type (ATPTYPE), and Average
Response Time (ATPAVTTM) data elements are important for
response time analysis.

The Application Unit Identifier is discussed in Sections
7.3.11 and 7.3.12.  The TP Class (ATPCLASS) data element is
the most reasonable value to use in assigning a value to
ATPAPU, but, because it is possible to set up APPC/MVS so
that all TPs run under a single TP Class, the derivation is
left to the user.

TP Type (ATPTYPE) can be either 'STP', 'MTP', or 'MSH', for
standard scheduled TPs, multi-trans scheduled TPs, or multi-
trans shells, respectively.  The data dictionary description
provides detailed information about ATPTYPE, and the APPC/MVS
Overview in Section 6.10 explains their execution
characteristics.

The summary keys for the BATATP file are shown for the
various timespans in Section 5.2.7.1.  TP Type (ATPTYPE) and
Application Unit Identifier (ATPAPU) are included in every
BATATP timespan.  This allows summary timespan response
time analysis to be performed on TPs with similar execution
characteristics.

The primary reason ATPTYPE is a BATATP file sort/sequence
element is because the response time characteristics of the
three ASCH-scheduled TP types is different.  A standard TP
must be initiated for each allocate request (conversation),
while a multi-trans TP remains initiated between consecutive
conversations with partner TPs.  The shell portion of multi-
trans TPs, (ATPTYPE 'MSH') is not associated with any
particular allocation request, and the only duration
available for this TP Type is TP Execution Time (ATPEXCTM),
which is estimated as explained in Section 6.10.1.

Average Response Time (ATPAVTTM) is the response time
measurement to be used in the CA MICS BATATP file summary
timespans.  Its value is derived by dividing Total Response
Time (ATPTRSTM) by TP Count (ATPCOUNT).  TP Count is set to
one for each DETAIL BATATP timespan record.