The z/OS agent works together with the AE system via a TCP/IP interface.
It communicates within z/OS exclusively with JES2 or JES3.
The z/OS agent provides the following functions:
- Jobs processing
- Execution of file transfers
- Event handling
- CallAPI
Job Processing
In the AE, jobs are defined and maintained in the form of objects that include various tabs. The JCL is stored in the Process tab. Its logic can be very complex if you make use ofthe AE's script elements.
See: Job Object (JOBS) as well as Executing Jobs
In the AE, you can start jobs either manually or via control mechanisms such as Workflow objects or Schedule objects. The Automation Engine then generates an executable job and sends it to the MPE agent via a file transfer.
See: Inside AE Guide - Executing Objects
In z/OS, the job is read and put to the Internal Reader. The Internal Reader starts the job. Monitoring takes place through SSL.
The job notifies the agent about the beginning and end of an execution. The agent then passes this information on to the Automation Engine.
The agent monitors the job's status in regular intervals. This ensures that an abnormal end can be determined if a job vanishes ABEND or CANCEL). The job's return code is available in AE.
The job report (MSGCLASS) which includes the JES statistics and the complete job output is stored in a file that is specified by the Automation Engine. If specified in the job, the agent transfers the report to the Automation Engine which stores it in the AE database. Because JES requests the job output, you must use a MSGCLASS with the status HOLD.
Special Options for Job Handling Improvement
Duplicate Job Name Check
Scenario:
You may want to start multiple z/OS Jobs in AE that have the same z/OS job name but different Automation Engine job names. Such jobs would be queued in z/OS, although they will be started in the AE.
In addition z/OS jobs with different z/OS job names would not start either, if a resource limit for a maximum number of concurrent jobs has been set in the AE.
What you can do:
Set the parameter DuplicateJobCheck of the z/OS agent's INI file to "YES".
That way the Automation Engine will only start one of the jobs with the same z/OS job name.
Adjust Number of Jobs (available WLM initiators)
Scenario:
You may want to avoid that the Automic z/OS agent starts additional jobs in case all z/OS initiators are busy.
The WLM in z/OS has the capability to adjust the number of available initiators. Therefore the agent needs to check the number of available initiators to be able to determine the maximum number of jobs to start at a point in time.
What you can do:
Use the parameter InitiatorCheck in the agent's INI file. For more details on how to use this parameter refer to the section WLM.
Check Availability of Scheduling Environment
Scenario:
You want to prevent a job from being submitted to the JES (z/OS), if the scheduling environment that was defined for the job is not available on any of the suitable systems.
What you can do:
Set the parameter SCHENVCheck in the agent's INI file to "YES". For more details on how to use this parameter please refer to the section WLM.
Executing File Transfers
In the AE, file transfers are defined and maintained in the form of objects that include various tabs. They are executed with the character conversions that are defined in these tabs (such as IBM_3270_INTERNATIONAL).
See: User Guide - FileTransfer
See: Knowledge Base AE and z/OS - Agent
- FileTransfer Support
Event Handling
In the AE, events are defined and maintained in the form of objects that include various tabs.
The z/OS agent also supports events of type FileSystem and Console.
See: User Guide - Event
CallAPI
You can use the CallAPI with a utility that can be called by using a job.
See: User Guide - CallAPI for z/OS