CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

1. We checked basic IP connectivity from our Windows workstation to the z/OS
system using the ping command from a Windows 2000 prompt. As shown in
Example 5-2, we successfully received a reply from z/OS.
Example 5-2 Output from the ping command on Windows
C:\>ping wtsc66.itso.ibm.com
Pinging wtsc66.itso.ibm.com [9.12.6.6] with 32 bytes of data:
Reply from 9.12.6.6: bytes=32 time=130ms TTL=52
Reply from 9.12.6.6: bytes=32 time=120ms TTL=52
Reply from 9.12.6.6: bytes=32 time=120ms TTL=52
Reply from 9.12.6.6: bytes=32 time=120ms TTL=52
Ping statistics for 9.12.6.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 130ms, Average = 122ms
2. We started the CICS region SCSCPJA1 on z/OS.
3. Using the ScanPort utility, we then checked that CICS was listening on the
TCP/IP port configured in the CICS TG server connection definition. See
page 52 in Chapter 3 for more details on how we used the ScanPort utility.
4. We started the CICS TG connection to the CICS region using the command
CICSCLI /S=SCSCPJA1. (SCSCPJA1 is the Server name given in the Client
configuration step in Figure 5-5 on page 87.)
5. We checked the status of the connection to the CICS region using the
command CICSCLI /L. The connection status is available, as shown in
Example 5-3.
Example 5-3 Checking Client daemon connection status
CCL8001I CICSCLI - CICS Client Control Program
CCL0002I (C) Copyright IBM Corporation 1994, 2002. All rights reserved.
CCL8041I The CICS Client is using the following servers:
CCL8042I Server 'SCSCPJA1' (using 'TCPIP' to 'wtsc66.itso.ibm.com') is
available
6. We launched the ecib1.vbs test application. This showed the window in
Figure 5-7 on page 90, which displays the server connections defined to the
Client daemon. We entered 1 to select SCSCPJA1 and clicked OK.
Chapter 5. TCP/IP connections to CICS 89