5. FILES › 5.2 Batch Information Area Files › 5.2.1 Batch User Job Activity File (BATJOB) › 5.2.1.3 BATJOB Usage Considerations
5.2.1.3 BATJOB Usage Considerations
The BAT_JS01 file contains data about all address spaces
(e.g., batch jobs, started tasks, TSO sessions, APPC/MVS
Transaction Programs (TPs)) that either have not terminated
or have not yet had their output purged from the system. If
the missing SMF data for a job appears in CA MICS input data
after the job has passed the allowable retention limit and
has been written from the BAT_JS file to the BATJOB file,
the result depends on the record types encountered:
o A Step Termination Record (type 30 subtypes 2, 3, or 4)
will cause CA MICS to treat this as a new job and record
it separately from that associated with the job taken out
of suspension. (In addition, a record for the step will
be written to the BATPGM file.)
o A Job Termination Record (type 30 subtype 5) will cause
CA MICS to treat this as a new job, recorded separately
from that associated with the job taken out of suspension.
o An Output Writer Record (type 6) will be written to the
BATSPL file, but will not cause CA MICS to create a new
job record in the BATJOB file, unless it is accompanied by
an SMF type 26 purge record and you have specified the
NJEJOB or LATEJOB option statements in
prefix.MICS.PARMS(SMFOPS).
o A Purge Record (type 26) with no other records associated
with it is checked to see if it represents a job which
failed with a JCL error, or one that never entered MVS
execution because of a TYPRUN=SCAN or TYPRUN=COPY
specification on the JOB card. Records are created in the
BATJOB file for such jobs because the Purge record is the
only one encountered. Standalone Purge Records from jobs
that executed are discarded. They may be encountered when
the other records from the job exceeded the suspend limit
and were already used to create the BATJOB observation.
Special considerations or techniques related to using the
BATJOB file are provided below.
1. The identity of a batch job's execution may be made
through one or more of the following data elements:
JOB - Jobname
RDRTS - Reader Time Stamp
2. The values of the following data elements depend on the
CA MICS options and exits used at your site.
JOBWPETM - Pseudo Elapsed Time
JOBWSRU - System Resource Units
JOBCOST - Processing Charges
JOBCOSTL - Processing Charges Lost
3. There are times when the BATJOB file must be used in
combination with the BAT_JS file for processing job data
in the DETAIL time-span. The BATJOB01-nn files in the
DETAIL time-span contain a record for each job that has
been processed for which a job purge has been found or
the job data has been suspended longer than the
user-defined suspension limit. The BAT_JS01 file in the
DETAIL time-span is updated each day and contains a
record for each address space that is still within the
data suspension limit and has not been written to the
standard BATJOB file. A record in BAT_JS accounts for
as much of the address space's activity as is available
at the time.
4. ENDTS and STARTTS, when appearing in the MONTHS or YEARS
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 and YEARS time-spans.
Their purpose in DETAIL is described below.
STARTTS represents job initiation time.
ENDTS represents job termination time.
5. Incomplete records are written to the BATJOB file after
the number of days specified by the SUSPENDLIMIT
statement in prefix.MICS.PARMS(SMFOPS) unless CA MICS
encounters a new step or interval record for the address
space. The suspend limit is subsequently ignored until a
daily update processes SMF data that contains no new step
or interval records for the address space.
