SMF STCJOB/NOSTCJOB Statement

This article describes the STCJOB/NOSTCJOB statement, and includes information on the format and specification of the statement, plus tips and hints. 
micsrm140
This article describes the STCJOB/NOSTCJOB statement, and includes information on the format and specification of the statement, plus tips and hints. 

STCJOB/NOSTCJOB Statement Format

The STCJOB/NOSTCJOB statement is optional.
NOSTCJOB (Default)
or
STCJOB
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 STCJOB option statement forces
MICS
to also create BATJOB observations for started tasks.

Specifying the STCJOB/NOSTCJOB option statement

Nothing is required to specify NOSTCJOB because it is the default value. To specify an STCJOB option statement, follow these steps:
  1. Edit prefix.MICS.PARMS(SMFOPS).
  2. Insert a line as follows:
    STCJOB
  3. Execute the job in prefix.MICS.CNTL(SMFPGEN). If the STCJOB/NOSTCJOB 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 an STCJOB/NOSTCJOB option statement, MICSLOG will tell you that the option is missing and that the default (NOSTCJOB) was used.

Tips and hints

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
MICS
will summarize resource utilization fields (for example, CPU Time, Lines Printed) in the BAT_JS01 observation.
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),
MICS
will track and summarize all resource utilization fields for that address space type.
For example, if you use
MICS Accounting and Chargeback
to account for TSO sessions at the job level, then
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,
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 the SMFOPS member.
You have specified one of the xxxxJOB options.
If you have specified TSOJOB, for example, then
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,
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
MICS Accounting and Chargeback
or by specifying an xxxxJOB option in SMFOPS,
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 the change to xxxxJOB or accounting was made.