The z/OS 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 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:
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 scriptA particular Automation Engine object type. elements.
See: User Guide - Job and Job
- Execution
In the AE, you can start jobs either manually or via control mechanisms such
as Workflow objects or Schedule objects. The Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. then generates an executable jobAn Automation Engine object type for a process that runs on a target system. and sends it to the MPE agent via a file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object)..
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 statusThis represents the condition of a task (such as active, blocked, generating). in regular intervals. This ensures that an abnormal end can be determined if a job vanishes ABEND or CANCEL). The job's return codeThe value that represents the result of tasks and script functions. is available in AE.
The job reportA report provides more detailed information about a task's execution or a component. (MSGCLASS) which includes the JES statisticsThis is a list of a task's previous runs. 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 databaseA database is an organized collection of data including relevant data structures.. Because JES requests the job output, you must use a MSGCLASS with the status HOLD.
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
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
You can use the CallAPI with a utility that
can be called by using a job.
See: User Guide - CallAPI for z/OS
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |