Oracle Tuxedo Application Runtime for IMS supports IBM IMS applications on Mainframes to be migrated to Oracle Tuxedo. It provides a combination of APIs, tools, and services that allows both online and batch IMS applications to run unchanged, preserving years of IMS business logic and data investment in. 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 servers. This provides substantial cost savings and greater flexibility.
a set of DL/I calls that can be called by the COBOL programs migrated from Mainframe.
a robust session environment based on Oracle Tuxedo to handle concurrent connections from several 3270 terminals.
a robust execution environment to provide OLTP to process the transaction codes received from 3270 terminals via calling the migrated COBOL applications.
a DB plug-in on open system side and an ODBA proxy on z/OS to provide a mainframe IMS/DB support solution.
Interoperability
Oracle Tuxedo Application Runtime for IMS maintains full interoperability with:
Oracle Tuxedo 12.1.1.0 on all supported platforms
Oracle Tuxedo Application Runtime for Batch 12.1.1.0
COBOL: MicroFocus COBOL 5.1 and COBOL-IT COBOL 3.3.13
Installation Notes
The installation of Oracle Tuxedo Application Runtime for IMS does not require Oracle Tuxedo installation, but Oracle Tuxedo is a prerequisite at runtime.
Only one input message from a terminal is allowed in a single transaction.
You cannot reply to more than one output messages to terminal in a single transaction.
You cannot switch to a terminal other than the originator.
You cannot restore the symbolic CHKP data after the ARTIBMP server is rebooted.
Only Message formatting option 1 is supported.
You cannot deploy across heterogeneous machines.
Do not support IMS default system MOD - DFSMO2 which is used when MOD does not specify both in the application program and the MID "nxt" field. ARTIMS displays the output message as plain text in the terminal, user need to clear the terminal firstly.
Because there is different byte Ordering (Big Endian or Little Endian) in COBOL on different open systems, during 'Dynamic Attribute Modification' you cannot specify a decimal integer to attribute bytes directly in a program. It is s suggested to specify a hexadecimal value to byte in 'attribute bytes' one at a time.
ART Workbench may incorrectly convert the hexadecimal value in COBOL according the tr-hexa.map configuration file. You must create the tr-hexa.map configuration file according the project itself.
