Similar to the DB2 service library component of DirectConnect for z/OS Option, TRS allows users to access DB2 UDB data. They both perform protocol translation, route client requests and server results, and allow remote mainframe password management.
As shown in Figure 1-3, a DB2 access service allows the client application to access data stored in a DB2 UDB database running on z/OS through the Mainframe Connect DB2 UDB Option, a CICS transaction. However, the DB2 access service cannot invoke other CICS transactions. In direct contrast, TRS allows the client access—through Mainframe Connect—to invoke CICS, IMS, and MVS transactions that are based on Mainframe Connect Server Option APIs.
As a result, a single client connection through TRS can access many CICS transactions in multiple CICS regions.
Due to space considerations in the diagram, “Mainframe
Connect Server Option application” is shortened to “MC
Server Option application.”
Figure 1-3: TRS accessing many CICS transactions
In addition, TRS provides:
Additional security control on a user or transaction basis
Access to IMS and MVS data
Access to multiple Mainframe Connect Server Option-based CICS transactions in multiple CICS regions, including any Mainframe Connect running in the defined regions.
A DB2 access service provides:
Access to remote stored procedure (RSP) programs (TRS does not)
DB2 and SQL datatype transformation
Access to bidirectional transfer functionality
Advanced datatype conversion
Basically, you use TRS when:
Your applications invoke Mainframe Connect Server Option-based mainframe transactions through remote procedure calls (RPCs) or language requests.
You use client applications written for the TRS predecessor, Net-Gateway.
