How does an RSP access and return DB2 data?

This section explains how RSPs access data within the Enterprise Connect structure. The following figure shows how RSPs access and return DB2 data.

Figure 1-1: How RSPs access and return DB2 data

The figure shows how RSPs access and return DB2 data.

Figure 1-1 shows how RSPs reside with Open ServerConnect. When one of your client applications invokes an RSP (using Open Client), the request passes to a DirectConnect server. At this point, depending on your configuration, either Transaction Router Service (TRS) Library or the DB2/MVS Access Service Library (hereafter called Access Service Library) invokes the RSP.

TRS accesses DB2 data by directly invoking an RSP through Open ServerConnect. Access Service Library accesses DB2 data by invoking an RSP through MainframeConnect. The software installed on your network determines your application request options and capabilities.

Using TCP/IP for communications allows your client to access the Mainframe environment directly without going through DirectConnect (gateway-less) as indicated in Figure 1-2.

Figure 1-2: Mainframe access without using DirectConnect (gateway-less)

The figure shows mainframe access without DirectConnect.

You must have Open ServerConnect installed to implement RSPs.

Table 1-1 summarizes the functions available with the possible software configurations.

**Table 1-1: Software configuration options**
If installed:	You can access:	This software does not support:
DirectConnect and Open ServerConnect	TRS RSPs and RPCs through TRS only	Dynamic SQL access to DB2 SPTEST utility The mainframe as a client, either through Open Client or CSAs
DirectConnect, Open ServerConnect, and MainframeConnect	TRS and Access Service Library RSPs and RPCs through TRS RSPs through Access Service Library Dynamic SQL access to DB2 SPTEST utility to test RSPs	The mainframe as a client, either through Open Client or CSAs