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

346 CICS Transaction Gateway V5
The next section of code enables CICS TG Java client tracing if the tracing
parameter is set to on (Figure B-8).
if(trace.equals("on"))
{
T.setDebugOn(true);
}
else
{
T.setDebugOn(false);
}
Figure B-8 Enabling CICS TG Java client tracing
The next section instantiates a JavaGateway object, using the URL and port of the
Gateway as given in the input to the servlet. This automatically connects to the
Gateway daemon so no openJavaGateway() method call is needed. Note that
this, along with the other CICS TG Java method calls, is enclosed in a try catch
block, so we catch any exceptions that occur.
We then convert the input COMMAREA data into a byte array using the encoding
specified in the form. We then create an ECIRequest object using the parameters
previously input and flow the request to the CICS server, as shown in Figure B-9.
// create the ECI Request
eciRequest =
new ECIRequest(
ECIRequest.ECI_SYNC,
cicsServer,
username,
password,
funcName,
mirror,
abCommarea,
commareaLengthInt,
ECIRequest.ECI_NO_EXTEND,
ECIRequest.ECI_LUW_NEW);
// indicate progess
progress += "Flowing ECI request to server";
// send the request to CICS
jgaConnection.flow(eciRequest);
Figure B-9 Creating an ECIRequest and flowing it to CICS