![]() |
![]() |
![]() |
![]() |
![]() |
Table 1 Revision History Oracle Tuxedo Application Runtime for CICS and Batch provides a runtime environment for IBM CICS applications, and a runtime environment for IBM z/OS-compatible batch jobs.
• A production environment based on Oracle Tuxedo that executes CICS programs and transactions, and provides required functions and services.
•
• Batch operations, monitoring, and management facilities that include ISPF extensions for ART Batch operation, support real-time monitoring and alerting in TSAM Plus Manager, and integrate with extensive batch operations and management functions provided by TSAM Plus plug-in for Oracle Enterprise Manager (including in-depth availability and performance metrics, on-demand provisioning, and elastic scale-out).
•
• Native database connection support in ARTDPL server
•
•
•
•
• Synchronous job submission mode in artjesadmin
• Native JCL job submission via artjesadmin
• artjesadmin sub-command for dynamic priority change of a job in waiting status
• ABEND capture and alerting through OEM Incident Manager (configurable policies)
•
• Extended support for sort utility JOINKEYS command
• DSN resolution within volumes using File Catalog and related functionality, including IDCAMS LISTCAT (requires database)
•
• Support for running dynamically loadable C programs in m_ProgramExec function
• Integration with uni-SPF and ARTISPF extensions for batch operations, administration, and management, which provides the following functions through ISPF panels (requires uni-SPF and uni-REXX from The Workstation Group, Ltd.):* Archival of job logs and SYSOUTs to OEM management repository, with extended search capability through OEM* Configure ABEND alerting policies for triggering OEM Incidents and Rule sets* Extended log/SYSOUT viewer and search capability for active and archived jobsThe use of ISPF extensions for batch operations (ARTISPF) requires uni-SPF and uni-REXX from The Workstation Group, Ltd. (http://www.wrkgrp.com/index.html).For more information, see the Oracle Tuxedo Application Runtime for CICS and Batch Installation Guide.Oracle Tuxedo Application Runtime for CICS and Batch 12c Release 2 (12.1.3) supported platforms are listed in the Supported Platforms in the Oracle Tuxedo Application Runtime for CICS and Batch Installation Guide.If upgrading from release 11.1.1.2 or earlier, you must ensure the ARTADM server is configured at CICS Runtime.If using COBOL-IT, you must specify the -fthread-safe option when compiling CICS programs.
•
• When using Micro Focus Visual COBOL 2.2, we recommend you set COBOL runtime tunable parameter subsystem_cancel_mode=1, which specifies logical cancel for CBL_SUBSYSTEM cancels. See Micro Focus documentation for more information.
•
• The ARTSRM server is required for many enhancements introduced in 12c Release 2 (12.1.3). You must ensure it is configured in the Oracle Tuxedo UBBCONFIG file for CICS runtime if you use any of the following enhancements:
•
• IEBGENER GENERATE with MEMBER is not supported.
•
• Using DISP=SHR to add a new member in a PDS is not supported.
•
• All the RBA and Generic options for CICS commands are not supported in file-to-file scenarios when using COBOL-IT.
•
•
• When using a COBOL-IT compiler, you must configure variable COB_ENABLE_XA before booting up ARTSTRN.
• When using a COBOL-IT compiler, you must make sure PROGRAM-ID is the same as the COBOL program name. Different COBOL programs must define different PROGRAM-ID.
• Profile resource definition is not supported. Default profile DFHCICSA is assumed; there is no timeout mechanism for this profile.
• Sending the data with state in one transmission using the SEND command is not supported.
• For scenarios 3 and 4, the SEND CONFIRM/ISSUE CONFIRMATION commands must be added to the server and client code respectively in a transactional conversation.
• Implementations of SYNCPOINT in internal ART CICS and TMA-based ART CICS are different; these two types of sync-level conversation cannot occur in the same transaction.
• TMA conversation server is terminated using tpreturn(); however, in scenario 2 and 4, TMA-based ART CICS can only map SEND LAST (or FREE), in sync level 0 and SEND CONFIRM in sync level 2 to tpreturn(). As a result, all subsequent operations are not executed.
• Sync level 1 operation is not supported in Oracle TMA conversation. SEND CONFIRM/ISSUE CONFIRMATION is not supported except in scenarios 3 and 4.