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

Hex:
20202020202020203173742072756e204f462045433032202020202020202020202020202020200
0000000000000000000000000000000000000000
-------------------------------------------------
Do you wish to run the program again in this Logical Unit of Work? - (Y/N)
N
C - Commit or R - rollback?
C
Committed logical unit of work on SCSCPJA1
Gateway closed
7. When we knew that basic and transactional EXCI was functional on z/OS, we
tested the transactional functions in Windows 2000. We went into Windows
and created a CMD file that contained the statements shown in
Example 7-17. We set up a CMD file to make it easy to alter our classpath
during testing.
You will note the parameters passed to EciI1 includes the desired Gateway
URL. In this case it is the hostname of our z/OS host. If you do not have DNS
enabled, you could as easily include the TCP/IP address of the z/OS system
or set up the name in your hosts file.
The final parameter passed to EciI1 is the TCP/IP port that the Gateway
daemon on z/OS is listening on. This defaults to 2006, but we specify it here
for clarity.
Example 7-17 Windows test EciI1Test.cmd file
set CLASSPATH=.;C:\Program Files\IBM\IBM CICS Transaction Gateway\samples\java
set CLASSPATH=%CLASSPATH%;C:\Program Files\IBM\IBM CICS Transaction
Gateway\classes\ctgclient.jar
java com.ibm.ctg.samples.eci.EciI1 tcp://wtsc66oe.itso.ibm.com 2006
Example 7-18 shows the successful output from our Windows test.
Example 7-18 Windows EciI1 test
C:\EciI1Test.CMD
--------------------------------------------------
CICS Transaction Gateway Intermediate ECI Sample
--------------------------------------------------
Usage: java com.ibm.ctg.samples.eci.EciI1 [GatewayUrl] [Port]
Gateway: tcp://wtsc66oe.itso.ibm.com:2006/
WTSC66OE.ITSO.IBM.COMGateway opened...
Number of systems = 2
-------------------------------------------------
Chapter 7. TCP connections to the Gateway daemon on z/OS 163