• The TMA TCP product supports dynamic configuration updates for some of the TMA TCP configuration parameters. You can modify the configuration without shutting down and restarting the TMA TCP product. For more information about dynamic configuration, refer to the “Dynamically Configuring TMA TCP for CICS” section.The TMA TCP for CICS supports automatic enabling of a given Requester which is already disabled. The AUTO ENABLE LMID option is provided in the Requester configuration. When the option is set to E (Enable), the Pre-Requester automatically enables the LMID and starts the Requester and processes the request.
•
• An administrative tool (BDWN) for terminating the four programs listed aboveThe Connection file, BEAVCON, defaults to a user maintained table (UMT). If you choose to change this file to a VSAM file you must add the transaction BDWN to PLTSI for CICS. This transaction’s primary function is to shut down all the active Requesters, but one of its secondary functions is to remove all the entries from the Connection file. The Connection file must be empty before initializing activity.As Figure 1‑1 shows, TMA TCP for CICS extends this transparent access by routing Oracle Tuxedo’s requests for CICS program services through TCP/IP network software.Figure 1‑1 Oracle Tuxedo to TMA TCP for CICS RoutingAs Figure 1‑1 shows, TMA TCP for CICS fits between the CICS user application and TCP/IP.The mechanism used to send requests initiated from a CICS program to a remote Oracle Tuxedo domain is invisible to the user and significantly abstracted from the CICS programmer. Your company’s CICS program issues an EXEC CICS LINK command to the Oracle TMA gateway. In the data passed with the EXEC CICS LINK command, the programmer supplies the name of the service and the data to be used as input to that service. When the EXEC CICS LINK command returns, the reply to the request is placed in that same data area. If there was a problem satisfying the service request, meaningful return codes are sent back.Figure 1‑2 Oracle TMA Client Gateway ConfigurationFigure 1‑2 shows the configuration of the Oracle TMA client gateway. A client program (your CICS program) issues an EXEC CICS LINK command to the Pre-requester. The Pre-requester verifies that the service name is valid and identifies the Requester to which it should it should pass the request. The Pre-requester starts a different Requester for each configured remote endpoint. The Requester then sends the request to the remote Oracle Tuxedo domain and waits for a response. Once the response is returned, the Requester notifies the Pre-requester and hands the response to the Pre-requester, which then returns the response to the client program.
•
• Using the administration tool (described in “Configuring and Administering Oracle TMA TCP for CICS”) define the services and remote endpoints for use by TMA TCP. The best way to approach this is to talk to the Oracle Tuxedo administrator and choose one service only. Attempting to set up all the services at once would be a complex task, but after you learn how to set up one service, you should have no difficulty setting up the others.
• Add an EXEC LINK statement to one of your CICS programs and set up the data area as described in “Understanding How Oracle TMA TCP for CICS Works”.