The 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 can also use SMF records in order to recognize jobAn Automation Engine object type for a process that runs on a target system. or STEP ends.
Activate this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… in the INI file of the agents or the Event Monitor if it runs as an independent started taskAn executable object that is running. Tasks are also referred to as activities.:
(CONSOLE)
SMFJob=1
By default, the Job Messenger is used to recognize job ends. Therefore, the agent variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_EX_JOB_MD must be adjusted in the agent's INI-file section (Variables). Replace the componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. "UCXJM25M " by "UC4START" and restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. 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 codeThe value that represents the result of tasks and script functions. 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 statusThis represents the condition of a task (such as active, blocked, generating). 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.
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |