

5. FILES › 5.2 Batch Information Area Files › 5.2.3 Batch User Program Activity File (BATPGM) › 5.2.3.3 BATPGM Usage Considerations
5.2.3.3 BATPGM Usage Considerations
Special considerations or techniques related to using the
BATPGM file are provided below.
1. The identity of the batch job that processed the program
accounted for in the BATPGMnn files in the DETAIL
timespan is given by the following:
JOB - Jobname
RDRTS - Reader Time Stamp
2. The contents of the following data elements depend on the
CA MICS options and exits used at your site.
PGMWPETM - Pseudo Elapsed Time
PGMWSRU - System Resource Units
PGMCOST - Processing Charges
3. The PGMINTVL data element is extremely important when
processing the BATPGM file in the DETAIL timespan and
interval accounting is used for batch jobs.
It is important to understand that when a program has
generated interval records, the data maintained in the
BATPGM file is a record per interval and not a single
record for the program's total execution.
PGMINTVL='SE24' standard batch full program record built
from SMF type 30 subtype 4 step record.
PGMINTVL='SE22' standard batch interval record built from
SMF type 30 subtype 2 delta record.
PGMINTVL='SE23' standard batch end interval record built
from SMF type 30 subtype 3 interval end
record.
4. The ENDTS and STARTTS, when appearing in the MONTHS
timespans, 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 timespan
versus their role in the MONTHS timespan. Their purpose
in DETAIL is described below:
STARTTS represents program initiation time
ENDTS represents program termination time
5. If you only want to report on executed steps, code a SAS
WHERE or IF logic similar to that below:
WHERE PGMEXCTM NE .;
Copyright © 2014 CA.
All rights reserved.
 
|
|