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

Once the file was created, we went into OMVS and marked EciB1Test as
executable with the following command: chmod +x EciB1Test. You can verify
this worked by doing a ls -l and verifying the last character in the first
column is “x”.
– You can see the first parameter after the name of the Java class is the
location of the Gateway daemon (tcp://wtsc66oe.itso.ibm.com). Since the
Gateway daemon was running on the same host as our Java client we
could also have used the loopback IP address of 127.0.0.1 or “loopback” if
it is defined in the TCP/IP configuration.
– The final parameter on the EciB1 line is the TCP/IP port used by the
Gateway daemon. This defaults to 2006, but we added it anyway.
With the script marked as executable, we ran it by entering EciB1Test. The
results of our tests are shown in Example 7-14.
Example 7-14 OMVS EciB1 test output
$ [SC66] /u/cicsrs2: EciB1Test
Usage: java com.ibm.ctg.samples.eci.EciB1 [Gateway Url] [Gateway Port Number]
Gateway tcp://wtsc66oe.itso.ibm.com port:2006
CICS Servers Defined:
1. SCSCPJA1 -
2. SCSCPJA2 -
Choose Server to connect to, or q to quit:
1
Program EC01 returned with data:-
Hex: 32342f30362f30322031353a30363a32300
ASCII text: 24/06/02 15:06:20
6. Once we knew the basic CICS TG functions were working, we tested the
transaction EXCI functions using the supplied EciI1 sample class. We used
ISHELL to create /u/cicsrs2/EciI1Test. This will be an executable script file
with the contents shown in Example 7-15.
Example 7-15 OMVS 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.EciI1 tcp://wtsc66oe.itso.ibm.com 2006
Once the file was created, we went into OMVS and marked EciI1Test as
executable with the following command: chmod +x EciI1Test. You can verify
Chapter 7. TCP connections to the Gateway daemon on z/OS 161