TCPIPSERVICE resource definitions

Start of changeA TCPIPSERVICE resource to defines which TCP/IP services are to use CICS® internal sockets support. The internal CICS services that can be defined are ECI over TCP/IP (for CICS Clients), IIOP, CICS Web support (HTTP), or a user-defined protocol.End of change

The TCPIPSERVICE definition allows you to manage these internal CICS interfaces, with CICS listening on multiple ports, with different flavors of ECI, IIOP, CICS Web support or the user-defined protocol on different ports.

Start of changeTCPIPSERVICE definitions are for use only with the CICS-provided TCP/IP services, and have nothing to do with the z/OS Communications Server IP CICS Sockets interface. The TCP/IP Socket Interface for CICS is supplied with z/OS Communications Server, which is an integral part of z/OS and does not use the CICS SO domain.End of change

To select dynamic DNS (domain name service), you need to provide a group name for the DNSGROUP attribute. The Listener registers with MVS™ workload management services (WLM) using the APPLID specified in the system initialization table (SIT). The APPLID is passed to MVS as the Server. If the APPLID=(gname,sname) format is used in the SIT, then sname is the value passed to MVS.
Note:
  1. Both the client and the CICS server must use the same TCP/IP nameserver.
  2. The nameserver must be able to perform a reverse look-up, that is, it must be able to translate the IP address of the server into a full hostname.

TCPIPSERVICE definitions that specify PROTOCOL(IIOP) must be installed in both the listener region and AOR in a CICS logical server. See Java™ Applications in CICS