Job completion checker (JCC)

The job completion checker (JCC) subtask provides support for job-specific and general checking of SYSOUT data sets for jobs entering the JES output queues.

The JCC subtask is “triggeredˮ by job and started-subtask termination (3P) events. A 3P event is generated when SYSOUT is spooled. The 3P event then informs the JCC subtask that SYSOUT data sets are available for the current job in the output classes defined for JCC. The JCC subtask then starts to scan all JOBLOG and other SYSOUT data set records and tries to match these records against the message tables defined to the JCC. There are messages tables:
  • General, for all jobs
  • Specific, for the job name.

You can create these messages tables by using the EQQJCCT macro. The general message table is mandatory. The JCC subtask searches for job-specific table entries first. If it does not find any, it then searches the entries in the general table.

If a match occurs, an error code can be assigned to the operation (CA=error and EID=0) if you have coded the EQQJCCT macro accurately. This means that the 3P event has been amended with the error code set by the macro. Errors like S222 abends, and JCL errors are reported before 3P events are reported. By specifying the CA and EID, you will override anything reported by earlier events or the current 3P event. Note that a match could occur, but it does not have to be reported as an error to HCL Workload Automation for Z.

If a match does not occur, everything reported by earlier events or the current event (which is 3P) is passed to HCL Workload Automation for Z unaltered. The status for the operation is then updated accordingly.

Subtask initialization consists of:
  • Building control blocks for the JCC subtask
  • Reading and processing the parameter library member
  • Opening the JCC-message-table data set
  • Retrieving the general (default) message table member.
Subtask mainline logic provides service for the following events:
  • Timer expiration. Retry processing for all delayed jobs.
  • Subtask stop request. Return to caller.
  • Process all events (3P) on the JCC queue.