Setting up connection pooling

If any of the client HTTP connections in your CICS® regions are good candidates for connection pooling, you can use CICS resources to set it up.

1. Specify the SOCKETCLOSE attribute in the URIMAP resource definitions for the selected client HTTP connections for CICS web support, CICS web services, or CICS event processing. You can choose the length of time for which CICS keeps each pooled connection open before discarding it.
   For information about the SOCKETCLOSE attribute, see URIMAP resources.
2. For CICS web support and web services applications, ensure that CICS applications are specifying the URIMAP resource definitions on the commands to open the client HTTP connections.
   CICS web support applications open a client HTTP connection by using the WEB OPEN command. CICS web services applications open a client HTTP connection by using the INVOKE SERVICE command, or its synonym INVOKE WEBSERVICE. The applications must not specify the URI directly in the command, or for service requesters, use a URI from the web service description.
3. For CICS web support applications only, verify that the application does not use the option CLOSESTATUS(CLOSE) on any of the WEB SEND or WEB CONVERSE commands that it issues. CLOSESTATUS(CLOSE) requests the server to close the connection, and closed connections cannot be pooled.
4. For CICS web support applications only, verify that the application is issuing a WEB CLOSE command when it finishes using the client HTTP connection.
   CICS does not place connections in the pool if CICS web support applications do not issue the WEB CLOSE command, in case the connections are not in a good state. In CICS web services applications, the INVOKE SERVICE command completes the use of the connection by the application, so CICS web services applications do not have to issue any additional commands to complete their use of the connection.