Table of Contents Previous Next PDF


Z/OS JCL in the Batch Runtime Environment

Z/OS JCL in the Batch Runtime Environment
This chapter contains the following topics:
Introduction to z/OS JCL in the Batch Runtime Environment
This section describes how to find equivalents for z/OS JCL statements in the target environment. Some of these equivalents point to the Batch Runtime functions, other equivalents may rely directly on UNIX or Tuxedo features. In some cases, there may be no equivalent and a work-around solution may be necessary.
It is not the purpose of this document to describe z/OS JCL, for any explanation of JCL statements, please see the z/OS Internet Library.
z/OS JCL Cards in the Batch Runtime Environment
The following tables lists the JCL card parameters and the related command in the Batch Runtime:
In the column “status”, the following abbreviations are used:
N.R. means “not relevant”
N.S. means “not supported”
JCL Card Equivalence Table
 
m_JobBegin -c (with TuxJES).
m_JobBegin -p (with TuxJES).
m_JobBegin -t (with TuxJES)
DCB Parameter of DD Statement
 
SYSOUT Parameter of DD Statement
 
DATACLAS Parameter of DD Statement
The DATACLAS parameter is taken into account at WB JCL level only.
Using the DATACLASS informations, extracted from z/OS, the WB JCL updates the m_FileAssign function (or m_FileBuild from DATACLAS parameter in IDCAMS DEFINE commands).
RESTART Parameter of JOB Statement
Only the Deferred Step Restart type is managed.
The other types, Automatic Restart (Step or Checkpoint) and Deferred Checkpoint Restart, are not managed.
A deferred step restart of a job is caused by coding the function m_JobBegin with the -r parameter containing a job step and by submiting the job again.
In-Stream File
The in-stream files are supported using the m_FileAssign function with the -i parameter.
Concatenation of Files
The concatenation of files (or in-stream files) is supported using the m_FileAssign function with the -C parameter.
Override of Files
The overriding feature is supported.
Use the m_FileOverride function for the files managed by the m_FileAssign function.
Use the m_OutputOverride function for the files managed by the m_OutputAssign function.
Execution of External Sysin
Use the m_UtilityExec function in order to execute commands stored in a file.
Network Job Entry (NJE)
The following table describes the supported JES2 control statements and parameters in Oracle Tuxedo Application Rehosting Workbench and Batch Runtime.
 
ABEND Routine
Captures terminations abnormally or normally from user program. It provides three COBOL programs, ILBOABN0, CEE3ABD and ART3ABD, which can be called in specific conditions to ABEND the program by itself. When the ABEND routine calls stop run, stop run terminates the process after Batch Runtime performs necessary cleanup.
abcode: the ABEND code.
CEE3ABD abcode, clean-up
abcode: the ABEND code.
The possible values are:
0: Issue the ABEND. Batch Runtime will capture ABEND and do clean-up work. Job failed.
1: Issue the ABEND. Batch Runtime will capture ABEND and store a system dump in a file, then do clean-up work. Job failed.
abcode: the ABEND code.
The ILBOABN0.cbl source is in the Batch_RT/ejr/SAMPLE directory.
Note:
For Micro Focus COBOL, Batch Runtime provides two ABEND-handling routines, ILBOABN0 and ART3ABD, that are called to force ABEND. Micro Focus COBOL provides its own ABEND-handling routine, CEE3ABD. It works as defined by Micro Focus COBOL.
For COBOL-IT COBOL, Batch Runtime provides two ABEND routines, ILBOABN0 and CEE3ABD.
General Utility Commands Equivalence Table
 
 
Sort Utilities
Sort Utilities Equivalence Tables
SORT, SORTD, DFSORT, ICEMAN, SYNCSORTT
 
ICETOOL
 
Sort Limitations
when using syncsort utility, there are some limitations:
DFSORT (DATE3) format has no equivalent on syncsort.
DFSORT statements (outrec, inrec) are not fully suppported in the following situations:
If a key or a filed definition of an outrec field cut a field constant type, an error shows up (MT_ERROR in SYSIN translation) and :#PHX in ksh.
If a key or a field definition of an outrec field is not included in the inrec, an error shows up.
DB2 Utilities
Only DB2 Connect 9.7 or above is supported.
 
Table 2‑8 DB2 Utilities
DSNTIAUL
On mainframe, DSNTIAUL program is used to unload data from DB2 tables into sequential data sets. The data is copied to the data sets and is not deleted from the table.
To unload data from Oracle Database tables, Batch runtime provides you DSNTIAUL utility, which has the same functionality as DSNTIAUL program on mainframe with DB2.
The following table shows the supported DB2 data types and their conversion to the Oracle Database target.
 
Note:
Only supports the default format "YYYY-MM-DD-HH24.MI.SS.FF6".
DSNTIAUL Limitations
When applying equivalent SQL functions in select statement for the same database table column, the data type that Batch runtime DSNTIAUL outputs for Oracle Database may be different from the data type that mainframe DSNTIAUL outputs for DB2.
For real, Float(n) (1<=n<=21), Float(n) (22<=n<=53), and Double data types in DB2, they are converted to BINARY_DOUBLE data type (with eight bytes) in Oracle Database. You can retrieve the field in target file to COMP-2 variable in COBOL program by using Micro Focus COBOL (COBOL-IT COBOL may produce incorrect results).
DSNTIAUL Configuration
Do the followings to configure Batch Runtime DSNTIAUL.
1.
For more information, see Setting Environment Variables in Oracle Tuxedo Application Runtime for Batch User Guide.
2.
To enable it, you can either use export MT_DB_SQL_PREPROCESS="${JESDIR}/tools/sql/oracle/BatchSQLConverter.sh" or configure MT_DB_SQL_PREPROCESS in $JESDIR/ejr/CONF/BatchRT.conf.
3.
Configure MT_DSNTIAUL=Y.
The default value of MT_DSNTIAUL is "Y". For more information, see Table 3-3 Oracle Tuxedo Application Runtime for Batch Environment Variables (Optional) in Oracle Tuxedo Application Runtime for Batch User Guide.
4.
Set DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE format.
Environment "DSNTIAUL_DATE_FORMAT" defines date format. If it is not set, use the default value "YYYY-MM-dd HH24:MI:SS".
Environment "DSNTIAUL_TIMESTAMP_FORMAT" defines timestamp format. If it is not set, use the default value "YYYY-MM-DD-HH24.MI.SS.FF6".
Environment "DSNTIAUL_TIMESTAMP_TZ_FORMAT" defines timestamp with time zone format. If it is not set, use the default value "YYYY-MM-DD-HH24.MI.SS.FF6".
Environment "DSNTIAUL_TIMESTAMP_LTZ_FORMAT" defines timestamp with local time zone format. If it is not set, use the default value "YYYY-MM-DD-HH24.MI.SS.FF6".
5.
Environment variable "NLS_LANG" defines language and territory. If it is not set, use the default value "American".

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.