7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 SMF Processing Options (SMFOPS) › 7.3.1.8 APPCJOB/NOAPPCJOB Statement

7.3.1.8 APPCJOB/NOAPPCJOB Statement

The APPCJOB/NOAPPCJOB statement is optional and has the
following format:

NOAPPCJOB (Default)

or

APPCJOB

CA MICS, by default, only writes batch activity to the BATJOB
file.  An observation is written to the BATJOB file for each
batch job that executed.  Other address space types (for
example, TSO, started tasks, APPC/MVS TPs, and Open
Edition/MVS processes) are represented at the step and
interval levels in the BAT_TS, BAT_ST, BAT_TP, and BAT_OE
files, but not at the job level.

The APPCJOB option statement forces CA MICS to also create
BATJOB observations for APPC/MVS Transaction Programs (TPs).

SPECIFYING THE APPCJOB/NOAPPCJOB OPTION STATEMENT

Nothing is required to specify NOAPPCJOB.  This is the
default value.  To specify an APPCJOB option statement,
follow these steps:

1. Edit prefix.MICS.PARMS(SMFOPS).

2. Insert a line as follows:

   APPCJOB

3. Execute the job in prefix.MICS.CNTL(SMFPGEN).  If the
   APPCJOB/NOAPPCJOB option statement is coded incorrectly,
   the job will abend.  Correct the problem as explained in
   the MICSLOG and resubmit.  Verify that the job completes
   with a condition code of zero.  If your SMFOPS member
   does not contain a APPCJOB/NOAPPCJOB option statement,
   MICSLOG will tell you that the option is missing and
   that the default (NOAPPCJOB) was used.

TIPS and HINTS

CA MICS uses the BAT_JS01 file as the "information-to-date"
file for all address spaces that are still executing or
waiting for print.  Even if you do not require job-level
summarization for non-batch activity, an observation is
created and maintained in the BAT_JS01 file for purposes such
as supplying the ACCTNOx data elements to additional steps or
output.  There are only two reasons that CA MICS will
summarize resource utilization fields (for example, CPU Time,
Lines Printed) in the BAT_JS01 observation.

o You have an accounting requirement.

  If you have specified job-level accounting for non-batch
  work (for example, APPC/MVS TPs, started tasks, Open
  Edition/MVS processes), CA MICS will track and summarize
  summarize all resource utilization fields for that address
  space type.

  For example, if you use CA MICS Accounting and Chargeback
  to account for TSO sessions at the job level, then CA MICS
  will summarize all resource utilization fields from all
  interval, step, and output writer records for all TSO
  sessions in the BAT_JS01 file.  When a TSO session is
  purged or if the SUSPENDLIMIT is exceeded while the TSO
  session is waiting for output, CA MICS Accounting and
  Chargeback will create an ACTJBJ file observation for the
  session.  Output to the BATJOB file will not occur unless
  you have also specified TSOJOB in
  prefix.MICS.PARMS(SMFOPS).

o You have specified one of the xxxxJOB options.

  If you have specified TSOJOB, for example, then CA MICS
  will summarize all resource utilization fields from all
  interval, step, and output writer records for all TSO
  sessions in the BAT_JS01 file.  When a TSO session is
  purged or if the SUSPENDLIMIT is exceeded while the TSO
  session is waiting for output, a BATJOB observation is
  written with complete resource utilization.

  What happens to an existing record in the BAT_JS01 file
  when you either specify the xxxxJOB option or choose to
  account for that address space type at the job level?

  As stated earlier, CA MICS does not summarize resource
  fields to the job level in the BAT_JS01 file unless there
  is a specific need.  When you specify a need, either
  through CA MICS Accounting and Chargeback or by specifying
  an xxxxJOB option in SMFOPS, CA MICS will begin summarizing
  resource data for the specified address space type in the
  next daily update.  If an address space has previously been
  suspended and has a BAT_JS01 observation, only resources
  used in interval, step, and output writer records
  encountered after the change are collected.  When the
  BATJOB or ACTJBJ observation is created, it will not
  contain the complete resource utilization of the address
  space if any step, interval, or writer records were
  encountered prior to the change.

  All new work of the specified address space type will be
  fully accounted for.  The only BATJOB observations that
  could reflect partial resource utilization are those that
  were already in suspension when you added a xxxxJOB
  statement in SMFOPS or decided to account for non-batch
  work at the job level in CA MICS Accounting and Chargeback.