6. DATA SOURCES › 6.4 CPU Time Measurements › 6.4.2 Analyzer Files with CPU Time Measurements › 6.4.2.2 CPU Time in Job Level Files

6.4.2.2 CPU Time in Job Level Files

The CA MICS Batch and Operations Analyzer builds the job
level files from the step and interval records discussed in
the previous section.  Unlike the step and interval level
files, each of which contains records for a specific address
space type, the job level files can contain observations for
all address space types.  The Job Exec Type (Batch TSO STC
APPC OE SA) (JOBTYPE) data element identifies the address
space type of each observation.

The following are the CA MICS job level files:

  File    File Label
  ------  ------------------------------------
  BATJOB  Batch User Job Activity File
  BAT_JS  Batch User Job Suspend File

The BATJOB file is a summarized view of an address space
execution built from all step, interval, and JES records
processed by CA MICS.  For long running jobs whose execution
spans multiple CA MICS daily update runs, the BAT_JS file
represents job-to-date activity.

By default, the BATJOB file only contains observations for
batch address spaces.  Using prefix.MICS.PARMS(SMFOPS)
keywords, however, you can instruct CA MICS to roll up any of
the address space interval and step records for inclusion in
the BATJOB file.  Refer to section 7.3.1 for SMFOPS keywords
that control the contents of the BATJOB file.

Because the BATJOB file is built from the CA MICS step and
interval level files, it contains the identical CPU time
measurements described in the previous section.  The only
difference is that the data element names begin with the
characters "JOB" instead of "PGM".

Refer to the previous section for the list of STANDALONE,
SUBSET, and COMPUTED CPU time elements available in the
CA MICS job level address space files.  Remember that the
element names are identical, except for the prefix of "JOB"
instead of "PGM."