![]() ![]() ![]() ![]() ![]() ![]() |
The following topics are discussed in this document.
Oracle Tuxedo Mainframe Adapter for SNA is a domain-based product that provides bi-directional connectivity between Oracle Tuxedo clients or servers, and mainframe applications. Mainframe applications may use Customer Information Control System/Extended System Architecture (CICS TS) and Information Management System (IMS) implicit LU6.2, or any IBM-supported Application Program-to-Program Communication (APPC) or CICS TS interface.
The following new features are available in version 12c Release 2 (12.1.3) of the Oracle Tuxedo Mainframe Adapter for SNA product:
The channel and container model provides an easy and flexible mechanism for exchanging large volumes of structured parameter data between CICS programs.
For more information, see Channel/Container Support in DPL in Oracle Tuxedo Mainframe Adapter for SNA Users Guide and CICS/ESA DPL to ATMI Requests/Responses Server for Channel/Container in Oracle Tuxedo Mainframe Adapter for SNA Reference Guide.
Besides single-byte character set (SBCS) character set translation, Oracle Tuxedo Mainframe Adapter for SNA now supports multi-byte character set (MBCS) translation. This feature allows translation among more than 200 different SBCS and MBCS character sets.
For more information, see Multi-byte Character Set (MBCS) Support in Oracle Tuxedo Mainframe Adapter for SNA Users Guide.
You can retrieve customized call ID from every Oracle Tuxedo Mainframe Adapter incoming call message. Many buffer types support this feature, including CHANNEL/CONTAINER, VIEW, and FML32. Call ID is composed of fields; you can choose to put one or more fields to each call ID in configuration file. Oracle Tuxedo Mainframe Adapter for SNA Gateway loads and parses the configuration file at initialization, and generates a call ID depending on it when decoding an inbound request and sets this call ID to message.
Note: | This feature requires TSAM Plus 12.1.3.0. |
For more information, see Configurations for Customized Call ID Support in Oracle Tuxedo Mainframe Adapter for SNA Users Guide and Call Path in Oracle Tuxedo System and Applications Monitor Plus Console Users Guide.
Oracle Tuxedo Mainframe Adapter for SNA provides the flexibility for you to store and manage CRM related configurations (CICSLINKS
and SNASTACKS
) on mainframe independent of Tuxedo side configuration.
For more information, see Configuring the Oracle Tuxedo Mainframe Adapter for SNA Gateway in Oracle Tuxedo Mainframe Adapter for SNA Users Guide and Having Separate CRM Configurations on Mainframe in Oracle Tuxedo Mainframe Adapter for SNA CRM Administration Guide.
SNA gateway uses DM_LOCAL_SERVICES
and DM_REMOTE_SERVICES
sections in the DMCONFIG
file to store the import/export service attributes. This feature provides a unified and consistent service definition mechanism in Tuxedo Metadata Repository to define those services.
For more information, see Using the Oracle Tuxedo Metadata Repository in Oracle Tuxedo Mainframe Adapter for SNA Users Guide.
SNA gateway uses crmretrc
on open systems to retrieve trace from CRM. You can use crmretrc
from any machine located on the same TCP/IP network when it is running the CRM server.
For more information, see crmretrc and CRM in Oracle Tuxedo Mainframe Adapter for SNA CRM Administration Guide.
Oracle Tuxedo Mainframe Adapter for SNA supports inbound terminal initiated transaction routing. This feature allows terminals connected to a mainframe CICS system to run with transactions in a connected ART CICS system at run-time.
For more information, see Inbound Transaction Routing in Oracle Tuxedo Mainframe Adapter for SNA Users Guide.
Oracle Tuxedo Mainframe Adapter for SNA 12c Release 2 (12.1.3) is supported for the following Oracle Tuxedo releases:
For more information, see Oracle Tuxedo Mainframe Adapter for SNA Supported Platforms in Installing the Oracle Tuxedo Mainframe Adapter for SNA.
This section describes problems from the prior release of the Oracle Tuxedo Mainframe Adapter for SNA that have been fixed in the current release. Table 1 lists a bug number for each problem.
![]() ![]() ![]() |