At job termination, the IEFACTRT exit is called again. The exit normally has logic to handle both step termination and job termination in slightly different ways. The exit usually produces output in the JES log showing job totals for resource usage, condition codes and timestamps.
A type 30, subtype 5 record is produced at job termination, with the IEFU83/84/85 exit being invoked before the record is written. Major differences between step termination records and job termination records include:
• CPU totals are job totals, not step totals.
• EXCP totals are job totals, not step totals and include LINKLIST activity, JES2 I/O (for JES), catalog management and OPEN/CLOSE.
• Job termination contains job card info such as account codes, programmer name field, job class, etc. while step termination doesn’t.
After the job terminates, it will remain on the JES spool until all of the output is printed or purged. This could take days or even weeks.
A type 6 record is written for every SYSOUT data set that is printed or routed to another location. The IEFU83/84/85 exit is invoked before the type 6 record is written. The type 6 provides line and page counts, as well as information on form usage. This information is used for charge back to recover printer costs; by capacity planners to determine print volumes by printer, location and form; and by service level management to determine when SYSOUT completed printing. Some studies can also be done on the length of time to print output.
There are five subtypes for the type 6 record, depending on the type of output created:
• 0 - External Writer
• 2 - JES2 Output Writer
• 5 - JES3 Output Writer
• 7 - Print Services Facility (PSF) Output
• 9 - IP Printway Output.
Routing information includes the output route code and the output form number. Several studies can be made on number of lines per form or output location. This can be done for daily or weekly totals, as well as hourly totals. One of the major pieces of information that is not available is when the SYSOUT was released from HOLD status. The problem with service level management and report output is that the user could specify a held SYSOUT class, and not release or delete the data set for days. If you are trying to provide batch turnaround (including printing) within one hour, you’ll never make your objectives due to held SYSOUT. For that reason, most service levels today are based on the time the job is read in until the job terminates (but not until the output has been printed). Another item to note with type 6 records is that they can be produced before the step terminates if FREE=CLOSE was specified on the JCL.
The JES2 JOBCLASS parameter can indicate that a type 6 record is not to be created for certain job classes, all started tasks and/or all TSO users.