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

228 CICS Transaction Gateway V5
To enable client tracing, run the sample with the following Java option:
-Dgateway.T.trace=on
The address of the Gateway has been set to tcp://vmlinux1.itso.ibm.com
Port:2006
CICS Servers Defined:
1. SCSCPJA1 -SCSCPJA1 TCPIP
Choose Server to connect to, or q to quit:
1
Program EC01 returned with data:-
Hex: 30342f30362f30322031383a31313a30380
ASCII text: 04/06/02 18:11:08
Note: We used the TCP protocol to connect to the Gateway daemon on our
Linux system. If we did not specify the address of the CICS TG to connect to,
EciB1 would have used local mode and would still run the CICS program
successfully. However, local mode does not use the Gateway daemon and
would therefore not have tested the Gateway daemon we had running on
Linux.
8. Once connectivity from Linux was working, we then tested from a Windows
2000 workstation. We set the CLASSPATH on Windows 2000 to include
ctgclient.jar and ctgsamples.jar using the following command:
set CLASSPATH=C:\Program Files\IBM\IBM CICS Transaction
Gateway\classes\ctgclient.jar;c:\Program Files\IBM\IBM CICS Transaction
Gateway\classes\ctgsamples.jar;
9. We then ran the EciB1 Java application on our Windows 2000 workstation
using the following command:
java com.ibm.ctg.samples.eci.EciB1 tcp://vmlinux1.itso.ibm.com
This again ran the compiled version of EciB1 inside ctgsamples.jar and
connected to the CICS TG on our Linux system. We entered 1 at the prompt
to select our CICS server. The successful output of EciB1 was almost
identical to that shown in Example 9-17 on page 227, apart from the date
returned by EC01.