CSA processing

A CSA is invoked like any other CICS transaction. The following figure illustrates CSA processing:

Figure 1-3: CSA processing

The figure shows the CSA processing flow.

As Figure 1-3 shows, CSA processing has the following general flow:

  1. A CSA calls Open ClientConnect, specifying the server name and the address of the request to be executed at the remote LAN service.

    NoteThe server name is validated in the Open ClientConnect server/connection administrative facilities. The server/connection definitions provide information on the APPC connection and the desired LAN service. See the Mainframe Connect Client Option for CICS Installation and Administration Guide for details.

  2. Open ClientConnect initiates an APPC conversation with Mainframe Client Connect using the connection parameters specified in the server definition.

  3. Open ClientConnect sends the request (for example, SQL statements, such as SELECT or TRANSFER statements) to Mainframe Client Connect.

  4. Mainframe Client Connect sends the request across the LAN to the target remote database.

  5. The remote database processes the request and returns results to Mainframe Client Connect.

  6. Mainframe Client Connect sends the results across the APPC link to Open ClientConnect.

  7. Using an input pipe, Mainframe Client Connect passes results to the CSA for processing. In the case of a transfer, the results returned to the CSA consist of status information only.

    Figure 1-4: CSA Gateway-less processing

    The figure shows CSA gateway-less processing flow.

As Figure 1-4shows, CSA Gatewayless processing has the following general flow:

  1. A CSA calls Open ClientConnect, specifying the server name and the address of the request to be executed at the remote LAN service.

    NoteThe server/connection definitions provide information on the TCP/IP connection and the desired LAN service. See the Mainframe Connect Client Option for CICS Installation and Administration Guide for details.

  2. Open ClientConnect initiates a conversation using the connection parameters specified in the server definition.

  3. Open ClientConnect sends the request across the LAN (for example, SQL statements, such as SELECT or TRANSFER statements) directly to Adaptive Server Enterprise or the DirectConnect Server.

  4. The remote database processes the request and returns results.

  5. The results are sent across the TCP/IP link to Open ClientConnect.