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.
Table 2‑1 JCL Card Equivalences m_FileAssign -e m_JobBegin -c (with TuxJES). m_JobBegin -p (with TuxJES). m_JobBegin -t (with TuxJES)
Table 2‑2 DCB Parameter of DD Statement
Table 2‑3 SYSOUT Parameter of DD Statement 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.The concatenation of files (or in-stream files) is supported using the m_FileAssign function with the -C parameter.Use the m_UtilityExec function in order to execute commands stored in a file.
Table 2‑4 Supported Parameters 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-upabcode: the ABEND code.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.
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.
Table 2‑5 General Utility Commands Equivalences
Table 2‑6 Sort Utilities Equivalences
Table 2‑7 ICETOOL Equivalences 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.
•
Table 2‑8 DB2 Utilities 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.
Table 2‑9 Supported Data Types
Note: Only supports the default format "YYYY-MM-DD-HH24.MI.SS.FF6".
Note: Only supports the default format "HH24.MI.SS".
Note: Only supports the default format "YYYY-MM-DD".
• 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).For more information, see Setting Environment Variables in Oracle Tuxedo Application Runtime for Batch User Guide.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.
• 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".