Knowledge Base > Automation Engine and Target Systems > GCOS 8 > Monitoring Abnormal Job-Messenger Ends

Monitoring Abnormal Job-Messenger Ends

The following description includes information about the GCOS8 Job Messenger and how an abnormal Job Messenger end can be identified.

The GCOS8 agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host uses three Job Messengers to obtain information about jobAn Automation Engine object type for a process that runs on a target system. states:

  1. Start messenger (for job starts)
  2. End messenger (for job ends)
  3. Report messenger (for job reports)

If available, the reportA report provides more detailed information about a task's execution or a component. messenger is generated by the RSM system. GCOS8 jobs are finished after the job report has been created. The RSM system retrieves the report from the SYSOUT, then the agent is informed that the job report is ready to be transported to the AE system.

Messenger programs are vital for the execution of jobs. AE can be used to react to an abnormal job-messenger ending.

The program Switch Word (PSW) is used to send information about an abnormal Job Messenger end. This program has a 36-bit memory area. The bits between 0 and 17 are reserved for the GCOS8 system. The remaining bits from 18 to 35 can be used in any which way. In order to display its statusThis represents the condition of a task (such as active, blocked, generating)., the Job Messenger uses only one bit. This bit is defined using the parameter SW=bit number. Set the selected bit with the JCL statement $SET. With this configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. the Job Messenger is able to check whether the bit is in status ON. It sets it to OFF as soon as it is able to end normally. If the status remains ON, the Job Messenger has ended abnormally.

Ensure that no other applications already use the selected bit.

Procedure

The following descriptions use bit number 18. However, you can use any bit between 18 and 35 that has not yet been used. Proceed as follows to activate Job Messenger monitoring.

Start messenger:

  1. Open the Header-Include objectAn Automation Engine object type for a script that is frequently used in more than one object. HEADER.GCOS8.
  2. Insert the $SET statement and the job-messenger parameter SW=. The illustration below shows the relevant areas in a red frame.
  3. The area where the bit status is checked is also shown in a frame. The start messenger has ended abnormally if it is still set; therefore, the job will be canceled. Additional statements can also be inserted.

End messenger:

  1. Open the Trailer-Include object TRAILER.GCOS8.
  2. Use the same configuration as for the start messenger. Insert the $SET statement and the job-messenger parameter SW=. The illustration shows these areas in a red frame.

Report messenger:

Refer to the RSM Documentation for detailed information about how to adjust the report messenger.

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH