TRS is a component of DirectConnect. It routes requests from remote clients to Open ServerConnect and returns results to the clients. For more information on TRS, see the Mainframe Connect DirectConnect for z/OS Option User's Guide for Transaction Router Services.
Figure 1-3 illustrates RSP processing through TRS.
Figure 1-3: RSP processing through TRS
The following explains each step in Figure 1-3:
The client application requests a remote procedure call (RPC) with the following command:
EXEC rpcname @VARNAME1=’value’
In TRS, you invoke an RSP using the remote procedure
call (RPC) name.
TRS searches the RPC name for the TP name (transaction program name) and passes the request to DirectConnect. The TP name (which is associated with the RSP program) is invoked in the CICS region.
(The RSP and the Open ServerConnect API use the Stored Procedure Communication Area (SPAREA). For more information on the SPAREA, see “SPAREA”.
DirectConnect invokes the RSP.
The RSP performs the desired processing (for example, accessing DB2 data).
Open ServerConnect packages the data and messages produced by the RSP.
The RSP returns results to TRS.
TRS returns the results to the client application.
The RSP must call RPSETUP and RPDONE.
