Knowledge Base > Automation Engine and Target Systems > z/OS > Recognizing and Assessing Job Ends

Recognizing and Assessing Job Ends

The agent can also use SMF records in order to recognize job or STEP ends.

Activate this function in the INI file of the agents or the Event Monitor if it runs as an independent started task:

(CONSOLE)
SMFJob=1

By default, the Job Messenger is used to recognize job ends. Therefore, the agent variable UC_EX_JOB_MD must be adjusted in the agent's INI-file section (Variables). Replace the component "UCXJM25M " by "UC4START" and restart the agent.

(VARIABLES)
UC_EX_JOB_MD=UC4START

The advantage of using this function is that jobs can be assessed on the basis of the return codes the job steps supply. You can specify in the Job object whether the highest return code or the last one to occur is considered for the job end.

Make sure in your z/OS system that the SMF module logs the entries 30.

Each LPAR must run an EM if the jobs are distributed in the SYSPLEX with WLM, as otherwise recognition does not work.

Note that changing between the two Job Messenger types TCP/IP and SMF does not affect active or generated jobs. Do not change the Job Messenger if jobs are active or have been generated. Otherwise, these jobs obtain the end status ENDED_VANISHED. Despite this end status, these jobs ended successfully; it is only the end message which could not be sent to the agent. Thus, all of a system's jobs should have ended before the Job Messenger type is changed.