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

9.3 Testing the configuration
224 CICS Transaction Gateway V5
Note: We found that CICS TG configuration files are generally portable
between different UNIX platforms and between Windows and UNIX. However,
the name of the Client daemon TCP/IP protocol driver is different on Windows
and on UNIX. Using a Windows configuration file with a TCP/IP server
connection defined on a UNIX platform results in error messages in the Client
daemon log:
[3251] CCL:CCL3247 Error loading DLL '/opt/ctg/bin/CCLWNTIP.a'
(/opt/ctg/bin/CCLWNTIP.a: cannot open shared object file: No such file or
directory, 0)
[1149] POP:CCL3229E Cannot load protocol driver 'CCLWNTIP'
Running the Configuration Tool with the -plat option, specifying the platform
to configure for, avoids such problems.
To test our configuration we used the CICS TG sample Java application EciB1.
This is installed in the CICS TG samples directory, inside the java subdirectory.
The sample’s Java class is defined to be in the Java package
com.ibm.ctg.samples.eci, so the sample source file is stored under the following
directory structure:
com/ibm/ctg/samples/eci
The full path to the EciB1 sample on our Linux system is:
/opt/ctg/samples/java/com/ibm/ctg/samples/eci/EciB1.java
and on our Windows system it is:
C:\Program Files\IBM\IBM CICS Transaction
Gateway\samples\java\com\ibm\ctg\samples\eci\EciB1.java
The sample is also provided in a compiled form inside ctgsamples.jar.
We used EciB1 from our Linux system to call the CICS program EC01. The
EciB1 application flows an ECI request to a connected CICS region through a
specified CICS TG (Figure 9-5 on page 225) and invokes the transaction EC01.
The CICS TG URL is specified as an input parameter, and the CICS region is
entered at the interactive prompt. We then used EciB1 from a Window 2000
workstation to call the same CICS program (Figure 9-6 on page 225).