|
|
|
The CA MICS Batch and Operations Analyzer divides its data
logically into the Batch Information Area (BAT) and the
Operations Information Area (OPS). Job, program, TSO
session, system task, APPC/MVS TPs, spooling, and device
workload information comprise the Batch Information Area data
files. IPL, outage, and configuration data are in the
Operation Information Area files. Figure 5-1 lists the
product's files and the timespans that are activated for each
file. The chart in Figure 5-2 describes the files supported
by the Batch and Operations Analyzer and their data sources.
The table below identifies the individual database files and
categorizes them by the information area to which they
belong. For each file in an information area, the following
data is provided:
XDWMYT - This entry defines the timespans in which the file
is supported. A nonblank indicates that the file is
supported. A period (.) indicates that the file is
not supported. The timespans indicated by XDWMYT
are as follows:
X - DETAIL
D - DAYS
W - WEEKS
M - MONTHS
Y - YEARS
T - TABLES AREA
File - The name used to access this file.
File Name - The descriptive label for the file.
NOTE: The timespans in which a file is supported are
defined by each installation when CA MICS is
installed. Therefore, this table has been generated
as part of the installation process to accurately
reflect the CA MICS system at your installation.
+----------------------------------------+------------------+
| Batch Activity | Date Generated: |
| Information Area |Tue, May 12, 2009 |
+----------------------------------------+------------------+
| |
| XDWMYT File File Name |
| |
| X..... BAT_JS BATCH USER JOB SUSPEND FILE |
| X..M.. BAT_OE OPEN EDITION/MVS PROGRAM FILE |
| X..M.. BAT_SA SYSTEM ADDRESS SPACE ACTIVITY FILE |
| X..M.. BAT_ST SYSTEM TASK PROGRAM ACTIVITY FILE |
| X..M.. BAT_TP APPC/MVS TP ACTIVITY FILE |
| X..M.. BAT_TS SMF USER TSO ACTIVITY FILE |
| X..M.. BATATP APPC/MVS TRANSACTION FILE |
| X..MY. BATJOB BATCH USER JOB ACTIVITY FILE |
| X..M.. BATMUA MEASURED USAGE ADDRESS SPACE FILE |
| XD.M.. BATMUG MEASURED USAGE GLOBAL FILE |
| X..... BATOEP OPEN EDITION PROCESS ACTIVITY FILE |
| X..M.. BATPGM BATCH USER PROGRAM ACTIVITY FILE |
| X..M.. BATREN MULTISYSTEM ENCLAVE ACTIVITY FILE |
| X..... BATSFH JOB ACCOUNT DERIVATION HOLD FILE |
| X..MY. BATSPL BATCH USER SPOOL ACTIVITY FILE |
| .D.... BATWDA BATCH WORKLOAD DEVICE ACTIVITY FILE |
+----------------------------------------+------------------+
| Operations | Date Generated: |
| Information Area |Tue, May 12, 2009 |
+----------------------------------------+------------------+
| |
| XDWMYT File File Name |
| |
| X..... OPSAVL OPERATIONS AVAILABILITY FILE |
| X..... OPSCON OPERATIONS CONFIGURATION FILE |
| .....T OPSCTF OPERATIONS CHANGE TRACKING FILE |
| X..... OPSOPI OPERATIONS INCIDENT FILE |
| |
+-----------------------------------------------------------+
Figure 5-1. Batch and Operations Files
+---------+-------------------+---------------------------------------------+--------------------------------+ | File | File Name | Description | Derivation | +---------+-------------------+---------------------------------------------+--------------------------------+ | BATJOB | Batch User | Quantifies user batch service (turnaround) | Output Writer (6) | | | Job | load, and usage for an individual job | Job Purge (26) | | | Activity | execution in the DETAIL time-span, and | Type 30 (Subtypes 1,2,3,4,5) | | | | total usage in the summary timespans | JES3 Allocation (25) | | | | | | | BAT_JS | Batch User | Same as BATJOB observation for jobs still | Same as BATJOB file except | | | Job Suspend | executing or waiting for sysout | no Job Purge (26) record | | | | | | | BATPGM | Batch User | Quantifies user batch program resources, | Type 30 (Subtypes 2, 3, or 4) | | | Program | load, and usage for individual program | | | | Activity | (step) executions in the DETAIL timespans, | | | | and total usage in the summary timespans | | | | | | | | BAT_TS | SMF User TSO | Quantifies TSO user resources, load, and | Type 30 (Subtypes 2, 3, or 4) | | | Activity | usage consumed during TSO sessions in | | | | | the DETAIL timespans, and total usage in | | | | | the summary timespans | | | | | | | | BAT_ST | System Task | Quantifies system task resources, load, | Type 30 (Subtypes 2, 3, or 4) | | | Program | and usage in the DETAIL timespans, and | | | | Activity | total usage in the summary timespans | | | | | | | | BAT_TP | APPC/MVS TP | Quantifies APPC/MVS ASCH scheduled TP | Type 30 (Subtypes 2, 3, or 4) | | | Activity | address space load and usage in the DETAIL | | | | | timespans, and total usage in the summary | | | | | timespans | | | | | | | | BATATP | APPC/MVS TP | Quantifies individual APPC/MVS ASCH | APPC/MVS TP Accounting | | | Transaction | scheduled TP resource usage in the DETAIL | (Type 33) | | | | timespan, and total usage in the summary | | | | | timespans | | | | | | | | BATSPL | Batch User | Quantifies printer resource usage for | Output Writer (6) | | | Spool Activity | printed sysout in the DETAIL timespan and | | | | Activity | total usage in the summary timespans | | | | | | | | BATWDA | Batch Workload | Quantifies DASD device usage by workload | Type 30 (Subtypes 2, 3, or 4) | | | Device | component (performance group) by hour of | | | | Activity | the day in the DAYS timespan | | | | | | | | BATSFH | Job Account | Contains accounting information for sysout | Customized by User | | | Derivation Hold | records processed after CA MICS has | | | | File | discarded the execution records | | | | | | | | BATREN |Multisystem Enclave| Quantifies program, task,and load resource | Type 30 (Subtypes 2, 3, or 4) | | | Activity File | in the DETAIL timespans and in the summary | | | | | timespans for all multisystem enclaves | | | | | created by the address space executed. | | +---------+-------------------+---------------------------------------------+--------------------------------+
Figure 5-2. File Descriptions (Part 1 of 2)
+---------+-------------------+---------------------------------------------+--------------------------------+ | | | | | | File | File Name | Description | Derivation | +---------+-------------------+---------------------------------------------+--------------------------------+ | | | | | | OPSOPI | Operations | Identifies major operational incidents | IPL (0) | | | Incident | by SYSID and when they occurred | Data Lost (7) | | | | | SMF Status (23) | | | | | TIOC Initialization (31) | | | | | Start JES (43) | | | | | Stop JES (45) | | | | | System Status (90) | | | | | | | OPSCON | Operations | Identifies configuration changes by | I/O Configuration (8) | | | Configuration | SYSID and when they occurred | Vary Online (9) | | | | | Allocation Recovery (10) | | | | | Vary Offline (11) | | | | | Configuration (22) | | | | | | | OPSAVL | System | Quantifies the amount of time that the | System Status (90, subtype 8) | | | Availability | MVS control program was not active | Manual Update | | | | | | | | | | | | | | | | | OPSCTF | Operations | Identifies computer center changes or | Manual Update | | | Change Tracking | events that are not automatically | | | | | tracked by standard SMF records | | | | | | | | | | | | +---------+-------------------+---------------------------------------------+--------------------------------+
Figure 5-2. File Descriptions (Part 2 of 2) This chapter presents the Batch and Operations Analyzer data files as they are seen in the online database structure. The files may also be located offline in either audit or history archive files. The PIOM and the Database Structure and Contents Guide discuss these other structures.
This section contains the following topics:
5.1 Data Element Naming Conventions
5.2 Batch Information Area Files
5.3 Operations Information Area Files
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |