The following document explains the platform-specific settings for a z/OS jobAn Automation Engine object type for a process that runs on a target system..
All z/OS host attributesPlatform-independent attributes of the Job object. are stored in upper-case letters.
AE provides various settings for the efficient use of message classes.
Field/Control |
Description |
---|---|
Job Report |
Depending on your particular settings, the Job Report protocol consists of the JES statisticsThis is a list of a task's previous runs. and the job output. |
Database |
The Job Report is managed by AE. When the job has been processed, the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. takes the Job Report protocol which has been stored on 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 computer and stores it to the AE databaseA database is an organized collection of data including relevant data structures.. |
File |
The Job Report protocol is managed by AE. After job execution, the Job Report protocol is available in the target system as a file. |
Generate on error only |
Only when the job aborts, the Job Report protocol will be stored in the AE database and/or as a file in the target system (only available when "Database" and/or "File" has been selected). |
Type |
|
Automation Engine (AE) |
The job's JCL is stored in the "Pre-Process" and/or "Process" tab. |
z/OS JCL |
The job's JCL is available on z/OS. When you select this option the input field File Name becomes active. Select the dataset which contains the JCL here. The job card is generated from the host attributes defined here. The Pre-Process JCL is added before the first step. The scriptA particular Automation Engine object type. must be empty. The Automation Engine systemAn environment that is managed by Automation Engine components. [Formerly called "UC4 system."] will insert the job card defined in this Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, whether the JCL contains a job card or not. |
JCL incl. z/OS job card |
The complete JCL including the job card is used from the dataset which has been specified in the input field File Name. No runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). options are available, as the definitions made in the job card apply. When generating a job, the JCL from the Pre-Process tab is added before the first step. The script must be empty. |
Report Selection |
More details are provided in the documentation message classes. |
With non-JES output |
Complexity of job log Allowed values: "Default value", "Yes" and "No" "Default value" - The job-log complexity
depends on the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. made in the agent's INI file (parameter
completeJobout=). |
Obtain the following message class/classes |
Message classes which should be read and routed Specify one or several message classes. Examples: "A", "ABC", "X1". Any order is possible. The following values are also allowed: "*DEFAULT" and "*ALL", "*DEFAULT" - The message classes which
should be read depend on the configuration made in the agent's INI
file (parameter getMsgClass=). If this setting is used "*DEFAULT"
must also be specified in the field "Route to message class/classes". |
Report handling on hostComputer, target system. |
More details are provided in the documentation about message classes. |
Purge |
This deletes the job log in the JES spool. Allowed values: "Default value", "Yes" and "No" "Default value" - whether the
job log is deleted depends on the configuration made in the agent's
INI file (parameter jobPurge=). |
Release |
The job-log releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked. for printing. Allowed values: "Default value", "Yes" and "No" "Default value" - whether the
job log is deleted depends on the configuration made in the agent's
INI file (parameter relMsgClass=). |
Route message class/classes to |
Message classes that should be routed. After it has been transferred to AE, the job log can be routed to the specified message classes (e.g. for an Output Management System). Enter either one or the number of message classes specified in the field "Obtain the following message class/classes". The order is significant. For example: The following message classes are read: "ABC" Class "A" is routed to class "D", "B" to "E" and "C" to "F". For example: The following message classes are read: "ABC" Class "A", "B" and "C" are routed to class "D". The following values can be used instead of message classes: "*DEFAULT" and "*NO" "*DEFAULT" - The message classes which
should be routed depend on the configuration made in the agent's INI
file (parameter routeMsgClass=). This setting must be specified if "*DEFAULT"
has also been specified in the field "Read the following message
class/classes". |
Runtime options |
|
Job name |
The name of the job in the system. |
Program name |
The programmer's name - it identifies the job ownerEntities are owned by a specific user or team. Only this user//users inside the team may change the entity. or its groupAn Automation Engine object type that integrates tasks so that they can be processed together. (optional). The name is recorded in the job's job card. A maximum 20 characters is allowed. |
Job class |
The specification of the job class in which the job should run (optional). |
Account |
Accounting information about the job. A maximum of 40 characters is allowed. |
Priority |
The specification of the job's priority (optional). A value between "0" and "15" can be specified. |
MSGCLASS |
The assignment of the job log's message class (optional). |
MSGLEVEL |
The trace option for the job log (optional). Possibly a numerical value for command and message separated by a comma. Allowed formats: "Command,Message", ",Message" or "Command" Allowed values for outputting commands: Allowed values for outputting messages: |
Notify |
The specification of a notificationAn Automation Engine object type used to send messages to users and user groups. [Formerly called "CallOperator."] on z/OS. A maximum of 17 characters is allowed. |
Job parameters |
The specification of additional job parameters such as "TIME=1440". |
z/OS file name |
The name of the dataset or member which contains: For example: SYSS.UC4.JCL.JOB1 or SYSS.UC4.JCLLIB(UC4JOB1) Jobs can also derive from the source administration system Librarian. The following syntax applies: *LIBRARIAN(Dataset, Member). A maximum of 225 characters is allowed. Example: IBMUSER.SYSS.UC4.JCL.JOB1 The agent ignores the first file line if type "z/OS JCL" is selected because it expects the job card in it. |
Return code |
This setting is relevant if the job end should be monitored via SMF Records. The return codes of the job STEPS are collected in this case. The setting "Highest" uses the highest return codeThe value that represents the result of tasks and script functions. when the job ends. "Latest" considers only the return code which has occurred last. The administrator can specify whether SMF Records should be used for monitoring job ends. The relevant parameter is SMFJob= in the Event Monitor's INI file and the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_EX_JOB_MD=UC4START in the agent's INI file. |
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |