You must satisfy these system requirements.
Here are the system requirements for CICS® TS
for z/OS®:
- The server must be CICS V3.2
or later because IPIC is not available in earlier releases of CICS.
- TCP/IP services must be active in the CICS server.
- To activate these services, set the TCP system initialization
parameter to YES.
- To check the status of these services, issue a CEMT INQ TCPIP
command and check that the status is open.
- The CICS server must have
access to a TCP/IP stack running on the same LPAR.
- You must set the SEC system initialization parameter to YES to
enable security.
- You must have valid RACF® user
IDs and passwords.
Here are the system requirements for CICS TG:
- CICS TG must be installed.
To test that the scenario works successfully you can use either
the supplied samples, or your own applications. If you use the supplied
samples, this scenario requires the following:
- The sample CICS TG server
program EC01 must be compiled, defined, and installed on CICS.
- The CICS TG supplied Java™ sample EciB2 available on the
client machine.
Testing your TCP/IP network
At the transport
layer, issue ping requests between the operating system that is hosting
your CICS TG and the LPAR where
your CICS server resides. The
ping request response, as shown in the example, confirms that the
TCP/IP communications are working. The ping request also works if you are using multiple IP stacks on the same
LPAR.
ping cicssrv2.company.com
Pinging cicssrv2.company.com [1.23.456.789] with 32 bytes of data:
Reply from 1.23.456.789: bytes=32 time<1ms TTL=61
Reply from 1.23.456.789: bytes=32 time<1ms TTL=61
Reply from 1.23.456.789: bytes=32 time<1ms TTL=61
Reply from 1.23.456.789: bytes=32 time<1ms TTL=61
Ping statistics for 1.23.456.789:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms