6. DATA SOURCES › 6.1 SMF Data › 6.1.2 SMF Data Categories › 6.1.2.2 SMF for APPC/MVS Transaction Programs(TPs)

6.1.2.2 SMF for APPC/MVS Transaction Programs(TPs)

APPC/MVS (Advanced Program to Program Communication/MVS),
uses the SNA architecture and LU6.2 to support cooperative
processing in an MVS environment.  Transaction Programs (TPs)
are programs that use APPC communication calls.  APPC/MVS
allows an MVS TP to establish a conversation with another
LU6.2 TP located anywhere in an SNA network to perform a task
as a single cooperative application.

The implementation of APPC/MVS introduces a new workload to
the MVS environment.  In addition to batch, TSO, and started
tasks, a new unit of work called the TP is introduced.
APPC/MVS TPs are managed by ASCH, the APPC scheduler address
space, and execute in full-function address spaces called
subordinate address spaces.  APPC initiators are controlled
by ASCH and, in a manner similar to JES initiators, only
allow TPs of the appropriate class to execute.

The SMF type 30 Common Address Space Work records are
generated for all TPs executing in the subordinate address
spaces.  The type 30 records present an address space
perspective of an APPC/MVS ASCH scheduled TP.  TPs can be of
two types (standard and multi-trans) however, and the type
30 records do not provide the granularity necessary for
individual TP analysis of multi-trans TPs.

The SMF type 33 APPC/MVS TP Accounting are produced for each
individual TP execution.  A multi-trans TP, once initiated,
may process hundreds of individual transactions before ending
execution, and the resource utilization at the address space
level will be reflected in a single SMF type 30 subtype 4
step end record.  In contrast, each individual request for
the TP from a partner TP results in an SMF type 33 APPC/MVS
TP Accounting record that provides accountability back to the
requesting program.  APPC/MVS is discussed in detail in
section 6.10.