Process Pages

As a developer and object designer you add functional logic to your objects on their Process pages using the Automation Engine scripting language. All executable objects have at least a Process page. Some object types also have pre-process, post-process, and child-post process pages.

An object definition consists of several pages. The Process page is available for all executable objects. Jobs objects have two additional process pages, the Pre Process and the Post Process page. Each Process page can contain up to 32767 lines. However, if the script generates more than 1000 JCL lines, its generation is canceled. If your script generates more JCL lines, you can change this limit using the MAX_JCL_LINES in the :PUT_ATT.

The scripts on the process pages are processed either when the object is activated or when it is generated. The order in which the pages process in Jobs is processes is important. For more information, see:

To access the Process page, click or expand the Process tab on the left pane of the object definition.

Tip: Read Working with the Script Editor before starting to write your scripts to learn about the script editor functions.

This page includes the following:

Process Page

The Process page is available in all executable objects. The script on this page is processed during the Generation stage. More specifically, the scripts on this and on the Pre Process pages are processed together during the generation stage, first the script on the Pre Process and then the script on the Process page. For detailed information about what happens during the script generation, see Script Generation in Detail.

For JMX, PeopleSoft, SAP, and SQL Jobs, the Process page provides two options to create scripts:

For more information, see Forms View on the Process Page.

Platform-Specific Information

For more information, see Configuring Include Objects for External Interpreter Calls.

Pre-Process Page

Available for Job objects (JOBS) only. On the Pre-Process page you enter statements that prepare the Job for execution. A typical example is the :PUT_ATT statement, which sets attributes such as the Agent. The script on this page is processed at the same time as the script on the Process page.

Since pre-process statements are executed in the Job header, you can add statements that are executed before the Job Messenger gets involved in the execution. For more information, see Agent Job Messenger.

Tip: Use the :INC_SCRIPT script statement to insert the content of this page on any other process page.

z/OS

On the Pre-Process page, you can define all JCL commands (e.g. JCLLIB, JOBCAT, JOBLIB, OUTPUT etc.). These commands must be defined after the Job statement but before the first step in the script.

The Event Monitor considers steps on the Pre-Process page only if the first step has the same name as the Automation Engine system. Otherwise, canceled pre-processing Job steps do not affect the end status of an Automation Engine Job.

Example:

In this example, the name of the Automation Engine system is UC4PROD.

Pre-Process page:

//JOBLIB DD DISP=SHR,DSN=.....

// DD DISP=SHR,DSN=....

//UC4PROD EXEC PGM=modname

Process page:

//STEP01 EXEC PGM=IEFBR14

//STEP01 EXEC PGM=IEBGENER

Post Process Page

Available for Jobs (JOBS) and File Transfers (JOBF) only. Scripts on the Post Process page are processed after the Job has ended normally or after a partial completion. A Job has partially completed if, for example, it is canceled. With post-processing commands you influence how a Job ends.

The following rules apply:

Tips: 

Child Post-Process Page

SAP and PeopleSoft Jobs usually contain statements that start multiple processes (sub jobs) in the target systems. To replicate this job structure in the Automic Web Interface, SAP and PeopleSoft Jobs have an extra Child Post Process page. The SAP or PeopleSoft Job you create in the Automation Engine is the parent of those sub Jobs (child processes) and serves as their container.

The script you enter on the Child Post-Process page is processed for each individual child process immediately after it has finished.

See also: