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

We changed the following parameters:
CICS program name ECIPROG2
COMMAREA length 35
Encoding IBM037
CICS Server SCSCPJA4
276 CICS Transaction Gateway V5
We then clicked Submit, which caused the ECI request to be flowed to our CICS
region using the local CICS TG, and the successful results were displayed as
shown in Figure 10-26.
Figure 10-26 CTGTesterECI response page
The output from ECIPROG2 shows that the request ran successfully in our
secure CICS region SCSCPJA4, and ran under the user ID CBASRU2. This is
the user ID of the J2EE Server, and not the client user ID authenticated by the
HTTP Server.