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

160 CICS Transaction Gateway V5
Tip: In V5 of the CICS TG, the standard logging messages no longer get sent
to STDERR. Instead they are written to STDOUT and only trace and error
messages are written to STDERR. In addition, connection logging messages
are disabled by default, but can be enabled using the new parameter
connectionlogging in the CTG.INI configuration file.
3. We checked the state of the TCP/IP sockets on our UNIX System Services
TCP/IP stack using the onetstat command from OMVS. This showed us the
output in Example 7-11 and indicates the CICS TG was indeed listening on
port 2006 for TCP requests.
Example 7-11 OMVS onetstat
$ ÝSC66¨ /u/cicsrs2: onetstat
MVS TCP/IP onetstat CS V1R2 TCPIP Name: TCPIPOE 23:02:35
User Id Conn Local Socket Foreign Socket State
------- ---- ------------ -------------- -----
SCSCTG55 0001F5C3 0.0.0.0..2006 0.0.0.0..0 Listen
4. We checked basic IP connectivity from our workstation to z/OS using the ping
command from a Windows 2000 command prompt (Example 7-12).
Example 7-12 Ping to z/OS verifying hosts or DNS setup
C:\>ping wtsc66oe.itso.ibm.com
Pinging wtsc66oe.itso.ibm.com [9.12.6.29] with 32 bytes of data:
Reply from 9.12.6.29: bytes=32 time=120ms TTL=52
Reply from 9.12.6.29: bytes=32 time=110ms TTL=52
Ping statistics for 9.12.6.29:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 120ms, Average = 112ms
5. Next we performed our basic test under OMVS. First we used ISHELL to
create /u/cicsrs2/EciB1Test. This will be an executable script file with the
contents shown in Example 7-13.
Example 7-13 OMVS EciB1 test script file
export CLASSPATH=/usr/lpp/ctg500/ctg/classes/ctgsamples.jar
export CLASSPATH=$CLASSPATH:/usr/lpp/ctg500/ctg/classes/ctgclient.jar
echo $CLASSPATH
java com.ibm.ctg.samples.eci.EciB1 tcp://wtsc66oe.itso.ibm.com 2006