5. FILES › 5.2 Batch Information Area Files › 5.2.6 APPC/MVS TP Activity File (BAT_TP) › 5.2.6.3 BAT_TP Usage Considerations
5.2.6.3 BAT_TP Usage Considerations
Special considerations or techniques related to using the
BAT_TP file are provided below.
1. Each BAT_TP DETAIL time-span observation represents the
resource utilization of an APPC/MVS transaction program
(TP) for the duration of the TP execution in an APPC
initiator. APPC/MVS TPs can be of two types, standard
and multi-trans, with standard being the default. An
exception to the one BAT_TP DETAIL time-span observation
per TP execution occurs when interval recording is
specified for the ASCH subsystem, and the execution time
of the TP exceeds the specified interval amount. When
this happens, two or more DETAIL time-span BAT_TP
observations will be present for the TP.
2. The PGMINTVL data element determines whether the raw SMF
record that generated the DETAIL time-span BAT_TP
observation was an interval or single step end SMF type
30 record. When interval recording is specified for the
ASCH workload, and an ASCH scheduled TP has executed in
an APPC initiator for more than the specified interval
amount, two or more interval records will be present,
instead of a single step record. Unlike the batch, TSO,
and started task workloads, only SMF type 30 records
record ASCH workload activity. The valid values for
PGMINTVL in the DETAIL time-span BAT_TP records are:
PGMINTVL='SE24' standard complete program record built
from SMF type 30 subtype 4 step record.
PGMINTVL='SE22' standard full interval record built from
SMF type 30 subtype 2 record.
PGMINTVL='SE23' standard incomplete, last interval record
built from SMF type 30 subtype 3 record.
When interval recording is selected, and a program, TSO
session, started task, or APPC/MVS ASCH scheduled TP
executes for less than the specified interval, both a
type 30 subtype 3 (last or partial interval record) and a
type 30 subtype 4 (step end) record are generated by SMF.
CA MICS always uses the interval records over step end
records when both are present in the raw data. So, when
interval recording is specified for any workload, you
should expect to see PGMINTVL values of 'SE22' and 'SE23'
in the DETAIL time-span records. An exception to this
rule is found for the SMF type 30 records produced for
JES and ASCH initiators, the programs that accept and
initiate batch jobs and ASCH scheduled TPs. Even if
interval recording is specified for all workloads SMF
does not produce interval records for initiators. Only
SMF type 30 subtype 4 records are produced for initiators
when the initiators are terminated.
3. This file is physically identical to the BATPGM file and
has the same data element names, labels, and formats. An
exception is data element PGMLOCTP, Local ASCH Scheduled
TPs, which is found only in the BAT_TP file.
4. The BAT_TP file provides an address space perspective of
APPC/MVS TP execution. In the case of a multi-trans TP,
the resource utilization data of a single BAT_TP DETAIL
observation is the summary of all conversations with the
TP by all partner TPs that requested it during its
execution. This address space summary also includes the
resources consumed when the TP executes in the multi-
trans shell mode between actual conversations with
partner TPs.
In the case of a standard scheduled TP, the BAT_TP DETAIL
timespan observation does represent the total resource
utilization of a single instance of the TP execution.
The BAT_TP file does not provide any information that
identifies the requesting partner TP.
5. There is no explicit way to determine whether a BAT_TP
DETAIL time-span observation was created from the
execution of a standard or multi-trans TP. This may be
inferred, however, from the value of data element Local
ASCH Scheduled TPs (PGMLOCTP). PGMLOCTP represents the
number of individual requests for conversations with the
TP plus executions of the multi-trans shell for multi-
trans TPs. It is therefore expected that for standard
TPs, the value of PGMLOCTP should be 1 for a DETAIL time-
span BAT_TP observation created from a standard scheduled
TP, and greater than 1 for one created from a multi-trans
scheduled TP.
6. The BAT_TP file is related to the BATATP APPC/MVS
Transaction 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 file provides a transaction orientated view of TP
execution, while the BAT_TP file provides an address
space view.
7. The BAT_TP file is useful for analyzing the performance
of ASCH scheduled TPs from an address space perspective.
Performance studies of paging, swapping, memory
utilization, and related metrics can be performed from
this file. This file is not useful for for APPC/MVS TP
accounting for two reasons.
o The partner TP that requested execution of the
APPC/MVS ASCH scheduled TP is not identified, and
therefore cannot be charged for the resources used.
o For multi-trans scheduled TPs the resource
utilization required for many instances of the TPs
execution by many different requesting partner TPs
are summarized together in a single SMF type 30
record and therefore summarized together in the
DETAIL time-span BAT_TP observation as well.
8. 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 TP, STARTTS is the time
the multi-trans shell begins to initialize the TP
environment.
ENDTS represents TP execution end time
In the case of a multi-trans TP, ENDTS is the time the
multi-trans shell completes the clean-up phase after
the last requested TP has executed.
For interval records, where PGMINTVL='SE22', STARTTS and
ENDTS represent the beginning and end of the recording
interval independently of when the TP actually began
execution (except for the first interval record where
STARTTS is also execution start time).
