5. FILES › 5.2 Batch Information Area Files › 5.2.7 APPC/MVS Transaction File (BATATP) › 5.2.7.3 BATATP Usage Considerations

5.2.7.3 BATATP Usage Considerations

Special considerations or techniques related to using the
BATATP file are provided below.

1.  Each BATATP DETAIL time-span observation represents the
    resource utilization of one execution instance of an
    APPC/MVS transaction program (TP).  One BATATP DETAIL
    time-span record is produced for each SMF type 33
    APPC/MVS TP Accounting record.

2.  APPC/MVS TPs can be of two types, standard and multi-
    trans, with standard being the default.  Data element
    ATPTYPE identifies the type of TP execution represented
    BY each BATATP record as follows:

     'STP'  - Standard schedule type, Standard user
     'MTP'  - Multi-trans schedule type, Standard user
     'MSH'  - Multi-trans schedule type, Multi-trans shell
              user

3.  Each BATATP DETAIL time-span record provides complete
    identification of the partner TP that requested the
    execution of the TP for ATPTYPE='STP' and 'MTP'.  In the
    case of BATATP records of ATPTYPE='MSH', representing the
    generic multi-trans shell portion of the TP, there is no
    partner TP responsible for the execution.

4.  There is no concept of interval recording for the BATATP
    file observations.  Each DETAIL time-span BATATP record
    represents the complete resource utilization of the
    APPC/MVS ASCH scheduled TP for the duration of the TP
    execution.

5.  The BATATP file is related to the BAT_TP APPC/MVS TP
    Activity file in that both are created from SMF records
    written for ASCH scheduled TP executions.  The initial
    IBM implementation of APPC/MVS, however, provides no
    means of tying the two files together.  The BATATP file
    provides a transaction orientated view of TP execution,
    while the BAT_TP file provides an address space view.

6.  The BATATP file is useful for chargeback and response
    time performance analysis of APPC/MVS ASCH scheduled TPs.
    For chargeback purposes, complete accountability back to
    the requesting TP is present in the record.  For response
    time analysis, timestamps and durations are present that
    quantify the start, stop, and durations of each important
    event from the initial request of the TP through the end
    of execution.

7.  The ENDTS and STARTTS, when appearing in the MONTHS time-
    spans, bound the span of time over which the data has
    been summarized, with STARTTS being the lowest date and
    time, and ENDTS the highest date and time for the data
    summarized.  The data elements STARTTS and ENDTS have
    different meanings when used in the DETAIL time-span
    versus their role in the MONTHS time-spans.  Their
    purpose in DETAIL is described below:

    STARTTS represents TP execution start time

      In the case of a multi-trans shell, when ATPTYPE='MSH',
      STARTTS is either the time the multi-trans shell begins
      to initialize the TP environment, if just initiated, or
      the time that the TP portion of the multi-trans TP
      returned control to the shell.

    ENDTS represents TP execution end time

      In the case of a multi-trans shell, when ATPTYPE='MSH',
      ENDTS is either the time the multi-trans shell returns
      control back to the TP portion of the multi-trans TP
      or, if no requests for conversations with the TP have
      occurred over a 5 minute period, the time the multi-
      trans TP ends execution and frees up the APPC
      initiator.