Limitations and Known Issues

1.7 Limitations and Known Issues

Oracle Tuxedo Application Runtime for CICS limitations and known issues are as follows:

BMS file name cannot be used as MAPSET name in CICS SEND MAP and RECEIVE MAP commands.
All the RBA and Generic options for CICS commands are not supported in file-to-file scenarios when using COBOL-IT.
When ISC_ENABLE=YES is set, ART CICS cannot validate LUNAME across multi-CICS regions.
There are some restrictions when users implement and run CICS applications in C language. For more information, see Implementing CICS Applications.
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 ensure PROGRAM-ID is the same as the COBOL program name. Different COBOL programs must define different PROGRAM-ID.
APPC session negotiation is not supported.
Profile resource definition is not supported. Default profile DFHCICSA is assumed; there is no timeout mechanism for this profile.
Applications communicating via DTP must run within the same Oracle Tuxedo domain.
Communication between ART CICS and Mainframe CICS via TMA SNA inherits the following limitations from TMA:
- LUTYPE6.1 protocol is not supported.
- Only the following APPC conversational programming model scenarios are supported:
  1. ART CICS DTP client Request/Response to Mainframe CICS DTP server (server gets control)
  2. Mainframe CICS DTP client Request/Response to ART CICS DTP server (client relinquishes control)
  3. Transactional ART CICS DTP client Request/Response to Mainframe CICS DTP server (server gets control)
  4. Transactional Mainframe CICS DTP client Request/Response to ART CICS DTP Server (client relinquishes control)
    For more information, see Oracle® Tuxedo Mainframe Adapter for SNA Reference Guide.
- 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.
- Oracle TMA copybook from Mainframe (via ART Workbench), must be aligned before it can be used in ART CICS applications.
Every node in the same ART for CICS application (no matter how many domains it is deployed on) must run on homogeneous platforms (for example, CICS Runtime supports this scenario: one node runs on Oracle Linux 6.3 platform while the other node runs on Oracle Linux 6.5 platform. However, CICS Runtime does not support this scenario: one node runs on Oracle Linux platform while the other node runs on Oracle Solaris platform). For all ART for CICS supported platforms, see Supported Platforms in Oracle Tuxedo Application Runtimes Installation Guide.