|
|
|
This section defines the use and content of each CA MICS file
in the Batch Information Area and the Operations Information
Area.
BATCH INFORMATION AREA
BATJOB--Batch User Job Activity File
Quantifies the resource consumption, status, and
execution of jobs executed in batch that have been
completely processed by CA MICS. This file is derived
from the Output Writer (type 6), Job Purge (type 26),
and Common Address Work Space (type 30 subtypes 1
through 5) records. For JES3, this file is derived
from JES3 Allocation (type 25) records.
BAT_JS--Batch User Job Suspend File
Quantifies the resource consumption, status, and
execution of jobs executed in batch for jobs that
have not been purged and still have data to be
collected for full job accountability. This file is
derived from the Output Writer (type 6), JES3
Allocation (type 25; JES3 only), Job Purge (type 26),
and Common Address Work Space (type 30 subtypes 1
through 5) records.
BATPGM--Batch User Program Activity File
Quantifies the resource consumption and use of
programs executed in batch. This file is derived
from the Common Address Work Space (type 30 subtypes
2 through 4) record for batch.
BAT_TS--SMF User TSO Activity File
Quantifies the resource consumption and use of TSO
as measured by SMF. This optional file is derived
from the Common Address Work Space (type 30 subtypes
2 through 4) record for TSO.
BAT_ST--System Task Program Activity File
Quantifies the resource consumption and use of system
tasks. This file is derived from the Common Address
Work Space (type 30 subtypes 2 through 4) record for
system tasks.
BAT_TP--APPC/MVS TP Activity File
Quantifies the resource consumption and use of
APPC/MVS Transaction Programs (TPs) at the address
space level. This file is derived from the Common
Address Work Space (type 30 subtypes 2 through 4)
record for system tasks.
BATATP--APPC/MVS TP Transaction File
Quantifies the resource consumption and use of
APPC/MVS Transaction Programs (TPs) at the
transaction level. This file is derived from the
APPC/MVS TP Accounting (type 33) record.
BATSPL--Batch User Spool Activity File
Quantifies the spool usage in terms of lines printed,
remotes used, and forms used by individual batch
account. This file also maintains data on
SMF-reported TSO usage as JOBGROUP=199. This file is
derived from the Output Writer (type 6) record.
BATWDA--Batch Workload Device Activity File
Quantifies the use of a DASD device address by
user-defined workload categories. This file is
derived from the Common Address Space Work (type 30)
record.
BATSFH--Job Account Derivation Hold File
Provides extended accountability for NJE SYSOUT and
"late" SYSOUT. This optional file is customized by
each site to reflect your account field derivation
requirements.
BATMUG--Measured Usage Global File
Quantifies resource usage measures for products
registered with IBM's Measured Usage License Charging
(MULC) subsystem. Resource collection is interval
driven at the system identifier level. This file is
derived from the Usage Data (type 89) record.
BATMUA--Measured Usage Address Space File
Quantifies resource usage measures for products
registered with IBM's Measured Usage License Charging
(MULC) subsystem. Resource collection is at the
address space step or interval level. This file is
derived from the Common Address Space Work (type 30)
record.
BAT_OE--Open Edition/MVS Program File
Quantifies the resource consumption and use of Open
Edition/MVS address spaces. This file is derived
from the Common Address Work Space (type 30 subtypes
2 through 4) record for Open Edition/MVS address
spaces.
BATOEP--Open Edition/MVS Process Activity File
Quantifies the resource consumption and use of
individual Open Edition/MVS processes. This file is
derived from the Open Edition/MVS Process segments in
the Common Address Work Space (type 30 subtypes 2
through 4) record.
BATREN--Multisystem Enclave Activity File
Quantifies the resource consumption and use of
Multisystem Enclave Remote System processes. This
file is derived from the Multisystem Enclave Remote
System Data segments in the Common Address Work Space
(type 30 subtypes 2 through 4) record.
BAT_SA--System Address Space Activity File
Quantifies the resource consumption and usage of
system address spaces. This file is derived from the
Common Address Work Space type 30 subtype 6 record
for system address spaces.
OPERATIONS INFORMATION AREA
OPSOPI--Operations Incident File
Identifies the incidents or events that affect the
operational environment. This file is derived from
the IPL, Data Lost, SMF Status, TIOC Initialization,
Start JES, Stop JES, and System Status records.
OPSCON--Operations Configuration File
Identifies changes in the hardware configuration and
when they occurred. This file is derived from the
I/O Configuration, Vary Online, Allocation Recovery,
Vary Offline, and Configuration records.
OPSAVL--System Availability File
Quantifies the amount of time the MVS Control Program
was not active and includes reasons for the lack of
availability. It may be updated manually to enable
you to record post-IPL analysis comments. This file
is derived from the System Status record and can be
updated using a separate manual process.
OPSCTF--Operations Change Tracking File
Identifies actions that are of significance to the
data center. It contains installation-dependent
information and is built and maintained using a
manual update process.
Figure 1-2 illustrates the data sources and files of the Batch Information Area. Figure 1-3 illustrates the structure of the Operations Information Area.
+-----------------+ +-----------------+ +-----------------+ +-----------------+ | SMF Job | | SMF Job | | SMF Output | | SMF Usage | | Initiation | | Termination | | Writer | | Data | | Records | | Records | | Records | | Records | | (SMF T30, | | (SMF T30 | | (SMF T6) | | (SMF T89) | | S/T 1) | | S/T 5) | | | | | +-----------------+ +-----------------+ +-----------------+ +-----------------+ | | | | INPUT | | | | DATA | +-----------------+ | +-----------------+ | +-----------------+ | +-----------------+ SOURCES | | SMF Step | | | SMF Purge | | | SMF JES3 | | | APPC/MVS | | | Termination | | | Records | | | Device | | | TP Accounting | | | Records | | | (SMF T26) | | | Allocation | | | Records | | | (SMF T30 | | | | | | Records | | | (SMF T33) | | | S/T 2, 3, 4) | | | | | | (SMF T25) | | | | | +--------+--------+ | +--------+--------+ | +--------+--------+ | +--------+--------+ | | | | | | | | +-----------------------------------------+-----------------------------------------------------+ | +-----------------------+ PRODUCT | CA MICS Batch and | PROCESSING | Operations Analyzer | | | +-----------------------+ | +-----------------------------------------+--------------------------------------------------------------+ | | | | | | | | +-----------------+ | +-----------------+ | +------------------+ | +-----------------------+ | | Batch User Job | | | Batch User Job | | | Batch User Spool | | | Batch Workload Device | | | Activity File | | | Suspend File | | | Activity File | | | Activity File | | | (BATJOB) | | | (BAT_JS) | | | (BATSPL) | | | (BATWDA) | | +-----------------+ | +-----------------+ | +------------------+ | +-----------------------+ | | | | | +---------------------+ | +---------------------+ | | | | | | | +-----------------+ +-----------------+ +-----------------+ +-----------------+ +-----------------+ | | Batch User | | SMF User TSO | | Started Task | | APPC/MVS | | APPC/MVS | | | Program Activity| | Activity File | | Program Activity| | TP Activity | | Transaction | | | File | | (BAT_TS) | | File | | File | | File | | | (BATPGM) | | | | (BAT_ST) | | (BAT_TP) | | (BATATP) | | +-----------------+ +-----------------+ +-----------------+ +-----------------+ +-----------------+ | | +----------------------+-------------------------------------------------------------+ | | +---------------------+---------------------+ | | | +-------------------+ +-----------------+ +--------------------+ | Multisys Enclave | | Measured Usage | | Measured Usage | | Activity FIle | | Global File | | Address Space File | | (BATREN) | | (BATMUG) | | (BATMUA) | +-------------------+ +-----------------+ +--------------------+
+-----------------+ +-----------------+ +-----------------+ +-----------------+ | SMF Incident | | SMF | | IPL Availability| | User Terminal | INPUT | Records | | Configuration | | Records | | Entry | DATA | (SMF T0,T7,T23, | | Records | | (SMF T90, S/T 8)| | (SAS/FSP) | SOURCE | T31,T43,T45,T90 | | (SMF T8, T9, | | | | | | S/T 1-18, 23, 24| | T10, T11, T22) | | | | | +-----------------+ +-----------------+ +-----------------+ +-----------------+ | | | | | | | | | | | | +-----------------------------------------------------------------------------------+ | | | +-----------------------+ PRODUCT | CA MICS Batch and | PROCESSING | Operations Analyzer | | | +-----------------------+ | | | | +-------------------------------------------------------+---------------------------+ | | | | +-----------------+ +-----------------+ +-----------------+ +-----------------+ | Operations | | Operations | | Operations | | Operations | PRODUCT | Incident File | | Configuration | | Availability | | Change Tracking | FILES | (OPSOPI) | | File | | File | | File | | | | (OPSCON) | | (OPSAVL) | | (OPSCTF) | +-----------------+ +-----------------+ +-----------------+ +-----------------+
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |