Knowledge Base > Automation Engine and Target Systems > z/OS > JCL Exit

JCL Exit

JCL Exits are available when processing z/OS jobs. These exits are supplied in the form of a module which can be used to modify the generated jobAn Automation Engine object type for a process that runs on a target system. before it is processed.

Create a z/OS job in the AE as usual. Its start causes the generated job to be sent to 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 which completes it and executes the job in the target system. When using the JCL Exit, the agent calls the specified module before executing the job. In doing so, the JCL in z/OS can be changed subsequently.  You can add, change or evaluate JCL lines, thereby preventing the start of particular programs, for example.

You can either create the JCL Exit module in Assembler code or in the programming language C. The module is specified in the agent's INI-file section JCL Exit. Note that there are different INI-file parameters for the Assembler-based and the C-based JCL Exit (see configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. instructions below).
The agents only loads one JCL Exit module. By default, the system uses the c-based JCL Exit if it has been specified.

The supplied CD contains a folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. for z/OS agents. It includes a sample module in the file uc4jcle.asm (Assembler) which inserts comment lines. It also contains a description about how the module is used.

The JCL Exit module can be individually activated for each z/OS agent. The module is loaded when the agent starts.

Configuring the C Module

(JCL-Exit)
ExitModul=Module name
ExitFunction=ExitFunction name
InitFunction=InitFunction name (optional)
CloseFunction=CloseFunction name (optional)

Configuring the Assembler Module

(JCL Exit)
name=Module name
maxJclRecords=1000

 

See also:

INI file

 


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

Copyright © 2016 Automic Software GmbH