5. FILES › 5.2 Batch Information Area Files › 5.2.14 Open Edition/MVS Process Activity File(BATOEP) › 5.2.14.3 BATOEP Usage Considerations
5.2.14.3 BATOEP Usage Considerations
Special considerations or techniques related to using the
BATOEP file are provided below.
1. The identity of the Open Edition/MVS process is uniquely
determined by the following:
OEPPID - OE/MVS Process ID 00406160
OEPGID - OE/MVS Process Group ID 00406170
OEPUID - OE/MVS Process User ID 00406180
OEPUGID - OE/MVS Process User Group ID 00406190
OEPSID - OE/MVS Process Session ID 00406200
OEPPPID - OE/MVS Parent Process ID 00406210
2. Because the source for BATOEP observations is SMF type 30
step or interval records, there is a partner observation
in one of the CA MICS step-level files (BATPGM, BAT_TS,
BAT_ST, BAT_TP, BAT_OE). The following data elements
allow you to uniquely identify the CA MICS step-level
partner observation:
ENDTS - End Time Stamp
STARTTS - Start Time Stamp
RDRTS - Reader Time Stamp
JOB - Job Name
STEPNUM - Step Number
SUBSTEP - Substep Number
JESJOBNO - JES Job Number
PROGRAM - Program Name
PROGRAML - Long Program Name (OE/MVS)
PROGRMLT - Long Program Name Type (OE/MVS)
PGMINTVL - Interval Measurement Type
PGMTYPE - Program Execution Type (Batch, TSO, STC,
etc.)
Note that PGMTYPE in the BATOEP file directs you to the
appropriate CA MICS step-level database file:
PGMTYPE=1 - BATPGM (Batch)
PGMTYPE=2 - BAT_TS (TSO)
PGMTYPE=3 - BAT_ST (Started Task)
PGMTYPE=4 - BAT_TP (APPC/MVS TP)
PGMTYPE=5 - BAT_OE (Open Edition/MVS)
3. The BATOEP usage measurements consist of the CPU time
used by the Open Edition/MVS process as well as various
Open Edition/MVS resource utilization metrics.
4. The STARTTS and ENDTS values in DETAIL timespan BATOEP
file observations are identical to the same data element
values in the partner step level database observation.
They represent the start and end of the step or interval
record that contained the usage data.