CA Gen 8.5 offers two TCP/IP Direct Connect for CICS products, the CICS Sockets Server implementation and the CICS Multi Sockets Server implementation. The Direct Connect for CICS implementation, TILSTNR and TICONMGR, offered in releases earlier than CA Gen 8 has been stabilized and is not included with CA Gen 8.5.
Both the CICS Sockets Server implementation and the CICS Multi Sockets Server implementation pass the socket to the CA Gen server application. The difference in the two implementations is how the processing is done when processing requests. The CICS Socket Server implementation process a single request all the way to passing the socket to the CA Gen server before accepting next request. The CICS Multi Socket Server processes multiple requests simultaneously. The CA Gen server closes the socket when it terminates. The CA Gen Client Manager and the CA Gen Communications Bridge recognize that the socket connection terminated after processing each flow.
Both the implementations can use IPv4 or IPv6 socket protocol. For specific information about installing the CICS Sockets Server feature, see either the section CICS Sockets Server or CICS Multi Sockets Server in this section.
You must configure the IBM CICS Sockets Interface to use it with CA Gen generated CICS Server applications. For more information about configuring IBM's CICS Sockets Interface, see Setting up and Configuring CICS TCP/IP in IBM's latest Communications Server IP CICS Sockets Guide.
The CICS Sockets Interface must start before the listener can initialize, and all listeners must terminate before stopping the interface. Use the IBM-provided EZACIC20 program to start or stop the CICS Sockets Interface and to initialize or terminate listener programs.
To automatically start or stop the CICS Sockets Interface at CICS startup or shut down, add the EZACIC20 program to the CICS Program Load Table (PLT). When the listener record in the configuration file states IMMED=YES, the listener automatically initiates when the interface starts and terminates before the interface terminates at CICS shut down.
Both implementations can exploit transactional security. Transactional security refers to starting the server transaction with the client application's userid, not the password. The server starts in CICS as a non-terminal task and can only use CICS transactional security with surrogate security checking.
The TCP/IP Direct Connect option of CA Gen for CICS is included in the Pax file as option CICS TCP/IP DC. Both implementations use the same user exits which are also included in the CICS TCP/IP DC option. This option is installed using CA CSM or SAMPJCL into the CEG8PLD1 dataset.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|