Overview of the Batch Runtime Environment

Oracle Tuxedo Application Runtime for Batch presentation and structure

The purpose of the Batch Runtime is to provide functions enabling a robust production environment on a UNIX/Linux platform.

Oracle Tuxedo Application Runtime for Batch is composed of:

•	Technical functions

•	High-level functions

•	Interface-level functions

Technical functions

The technical level contains simple one-action functions: easy to write, easy to maintain and easy to debug. For example, GDG (Generation Data Group) management belongs to this level. This technical level is the robust base of the Batch Runtime.

High-level functions

The high-level functions provide entry points to the Batch Runtime. This level homogenizes the behavior of functions, in order for them to be called in a production script. A high-level function follows a skeleton which provide robust logical workflow (execution on/off, options check, predefined return codes …).

In this level, we find functions to:

•	Manage files (creation, copy, assignation…)

•	Launch programs (COBOL, executable …)

•	Access Databases (connection/disconnection/commit/rollback for program, SQL execution)

•	Produce reports

•	Run utilities

Interface-level functions

The interface level allow users to interact with the Batch Runtime job management: submission, holding and releasing, class management, reporting, monitoring …

Oracle Tuxedo Application Runtime for Batch offers robust and useful production functions. With these functions, you can easily reproduce JCL and JES2 features, and have extra features like "no exec mode", return code predefinition (customizable), internationalization.

Oracle Tuxedo Application Runtime for Batch uses a native shell interpreter for high level functions. This approach enables you to add new runtime functions for specific production needs

Script execution phases

When submitted for execution within the Batch Runtime, a Korn shell script is processed through three separate phases:

Input Phase

In this phase, the JOB card parameters are analyzed.

Conversion Phase

During this phase, the Batch Runtime performs the following actions:

•	Expand all the external Korn shell scripts (procedures and/or includes) that are used within the script so as to produce a single complete script.

•	Resolve all the symbols that are used in the script replacing them by their current values.

Execution Phase

The script is executed by the Batch Runtime.