Oracle Tuxedo Application Runtime for CICS and Batch 12c Release 1 (12.1.1)
This topic contains the following sections:
Oracle Tuxedo Application Runtime for CICS and Batch supports IBM mainframe applications to be rehosted to Oracle Tuxedo. It provides a combination of APIs and services that allows OLTP and Batch mainframe applications to run unchanged, preserving years of business logic and data investment. It protects application users from change by supporting standard 3270 terminal emulators. It also provides familiar APIs and functions that developers use in their mainframe applications.
The result is the ability to quickly (and with low risk), migrate legacy mainframe applications to open systems running COBOL and C/C++ application server. This provides substantial cost savings and greater flexibility.
Oracle Tuxedo Application Runtime for CICS and Batch major features are as follows:
This release includes the following new features and enhancements:
Rolling Patch 001 includes the following new features and enhancements:
Rolling Patch 003 includes the following new features and enhancements:
Rolling Patch 007 includes the following new features and enhancements:
Rolling Patch 012 includes the following new features and enhancements:
prepro-cics-C.plfor CICS/COBOL APIs translation
ARTLOGNfor CICS region (APPL) logon
Rolling Patch 013 includes the following new features and enhancements:
CONNECT PROCESS CONVID/PROCLENGTH/PROCNAME/STATE/SYNCLEVEL
EXTRACT PROCESS CONVID/SYNCLEVEL
HANDLE AID OPERID
INQUIRE CONNECTION ACCESSMETHOD/CONNSTATUS/NETNAME
ISSUE CONFIRMATION CONVID/STATE
SET CONNECTION CONNSTATUS
WAIT CONVID(APPC) CONVID/STATE
Rolling Patch 015 includes the following new features and enhancements:
SEND TEXT PRINT/NLEOM
SEND CONTROL PRINT
SEND MAP ERASEAUP/PRINT
SPOOLOPEN OUTPUT NOCC/NODE
INQUIRE FILE ACCESSMETHOD/DSNAME/EMPTYSTATUS/ENABLESTATUS/LSRPOOLID/MAXNUMRECS/OPENSTATUS/TABLE/TYPE
INQUIRE PROGRAM RESCOUNT
INQUIRE TRANSACTION PROGRAM
INQUIRE TERMINAL ACCESSMETHOD/CREATESESS/NEXTTRANSID/REMOTESYSTEM/SERVSTATUS/SIGNONSTATUS/TRACING/TRANSACTION/USERID
INQUIRE SYSTEM SHUTSTATUS
SET FILE CLOSED/DISABLED/DSNAME/ENABLED/ENABLESTATUS/OPEN/OPENSTATUS
SET TERMINAL ATI/ATISTATUS/INSERVICE/OUTSERVICE/TTI/TTISTATUS /SERVSTATUS/NOATI/NOTTI
CONVERSE ASIS/ALTERNATE/CTLCHAR/ERASE/FROM/FROMFLENGTH /FROMLENGTH/INTO/MAXLENGTH/MAXFLENGTH/NOTRUNCATE/STRFIELD/SET/TOLENGTH/TOFLENGTH
HANDLE CONDITION ERROR
Oracle Tuxedo Application Runtime for CICS and Batch software consists of the following components:
ISSUE PASS, and
REQIDrequire Oracle Tuxedo 12c Release 1 (12.1.1) Rolling Patch 008 or above, and Oracle Tuxedo Application Rehosting Workbench 12c Release 1 (12.1.1) Rolling Patch 009 or above.
SYNCPOINTsupport requires Oracle Tuxedo 12c Release 1 (12.1.1) Rolling Patch 019 or above, and requires to rebuild TMS.
For more information, see the.
Oracle Tuxedo Application Runtime for CICS and Batch 12c Release 1 (12.1.1) supported platforms are listed in thein the .
When you upgrade Oracle Tuxedo Application Runtime for CICS and Batch from an older release to a newer release, you must rerun the CICS Preprocessor against the CICS COBOL programs, and then recompile the COBOL programs.
If upgrading from release 18.104.22.168 or before, you must ensure the
ARTADM server is configured in CICS Runtime.
$KIXDIR/include/msgflds32is changed from 30002700 to 30001100.
ARTSRMare required for many enhancements which are introduced in previous 12.1.1 rolling patches. For more information, see and in .
The following sections describe the limitations and known issues with Oracle Tuxedo Application Runtime for CICS and Batch.
CICS SEND MAPand
Genericoptions for CICS commands are not supported in File-to-File scenarios when using COBOL-IT.
ISC_ENABLE=YESis set, ART CICS cannot validate
LUNAMEacross multi-CICS regions.
COB_ENABLE_XAbefore booting up
PROGRAM-IDis the same as the COBOL program name and different COBOL programs must define different
DFHCICSAis assumed; there is no timeout mechanism in that profile.
SENDcommand is not supported.
SEND CONFIRM/ISSUE CONFIRMATIONcommands must be added to the server and client code respectively in a transactional conversation.
SYNCPOINTin internal ART CICS and TMA-based ART CICS are different; these two kinds of sync level conversation cannot occur in the same transaction.
tpreturn(), however, in scenario 2 and 4, TMA-based ART CICS can only map
FREE) in sync level 0 and
SEND CONFIRMin sync level 2 to
tpreturn(), as a result, all subsequent operations in user’s code are lost.
SEND CONFIRM/ISSUE CONFIRMATIONis not supported except in scenarios 3 and 4.