5. FILES › 5.2 Batch Information Area Files › 5.2.2 Batch User Job Suspend File (BAT_JS) › 5.2.2.3 BAT_JS Usage Considerations

5.2.2.3 BAT_JS Usage Considerations

If a type 26 record is not present with the other essential
records needed to construct a completed job observation in
the Batch User Job Activity File (BATJOB), this incomplete
observation will be stored in a suspend file, the Batch User
Job Suspend File (BAT_JS).

In each successive update, information about this job (i.e.,
later Writer Sysout records) will be merged with the
incomplete job observation.  This job observation will stay
in the suspend file until the type 26 record is present or
the allowable retention limit has expired.  When the type 26
record is present in an update, information from that record
and the incomplete job observation are merged and the now
complete job observation is written to the BATJOB file.

You specify the allowable retention limit (usually seven
days) that this job will stay in the suspend file.  Once that
time has passed, the partially complete record is written to
the BATJOB file regardless of what information is in the
file.  The JOBMASK data element indicates what records were
used to construct the data in the job observation.

Special considerations or techniques related to using the
BAT_JS file are provided below.

1.  All of the special considerations/techniques listed for
    BATJOB apply to this file as well.

2.  This file is contains all elements in the BATJOB and the
    BATSFH files.  It also contains some additional elements
    unique to the BAT_JS file.  For reporting purposes, it is
    acceptable to use BATJOB file processing macros (e.g.,
    %JOBSUM).  For retrofit purposes, you must use the BAT_JS
    file processing macros (e.g., %_JSKEEP, %_JSSEQ, etc.).

3.  There are times when the BAT_JS file must be used in
    combination with the BATJOB 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 job 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 job's activity as is available at the time.

4.  The JOBSUSPN data element is the indicator that is
    necessary in using BAT_JS individually, as well as in
    combination with the BATJOB file.

    JOBSUSPN is equal to 0 in the BATJOB file.  A zero
    defines this as a job completely processed by CA MICS.
    JOBSUSPN is a number from 1 to 10 when the job has not
    been completely processed and therefore has all its data
    still maintained in the job data suspension process.  The
    numeric value of JOBSUSPN defines the number of days the
    data for the job has been suspended.  A value of 1, for
    instance, indicates that this was the first update cycle
    in which data for the job was suspended.

5.  Note that there is only one cycle of the BAT_JS file and
    that the file is updated with each CA MICS daily update
    run.