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

7.3 Testing the configuration
158 CICS Transaction Gateway V5
To test our configuration we used the CICS TG sample Java applications, EciB1
and EciI1 from z/OS UNIX System Services and EciI1 from a Windows 2000
workstation. (The fourth character in EciI1 is an I as in Intermediate.) Both
applications flow an ECI request to a connected CICS region through a CICS TG
for z/OS (Figure 7-7). The CICS TG gateway and port are specified as input
parameters.
Windows NT
ctgsamples.jar
ctgclient.jar
JVM
EciI1
TCP/IP
ECI request
Gateway
daemon
Figure 7-7 CICS TG for z/OS, software configuration
wtsc66oe.itso.ibm.com
z/OS
CICS TG
EXCI
via IRC
The EciB1 application tests basic communications capability to the CICS region.
(The “B” stands for “basic”.) The output of this application is simply the date and
time as formatted by the CICS region.
The EciI1 application makes ECI calls in Extend_Mode. This causes the
application to be transactional, allowing two-phase commit.
When called, the EciI1 application prompts the user for the target CICS region.
Once that is input, the application starts a transaction, asking if they want to run
again. When the user decides not to run the transaction, the application asks if
the transaction should be committed or rolled back, performs the desired action,
and ends.
EXCI
We verified that our configuration was correctly set up as follows:
JNI
UNIX System Services
JVM
EciB1,
EciI1
ECI request
ctgclient.jar
ctgsamples.jar
CICS
CICS
Application
EC01,
EC02