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

EciB1 is written so that it will initially make a call to the specified CICS region
without a user ID and password, and then if it receives a security error it will then
prompt you for a user ID and password. It also allows trace to be activated by
specifying -Dgateway.T.trace=on. This will trace the CICS TG calls made in the
Java application and is particularly useful in showing the user ID and
COMMAREA flowed to and from the CICS TG.
When we ran EciB1 with trace on, we saw the following input on the first ECI call
to the CICS TG specifying SCSCPJA4 as the CICS region. As seen in
Example 6-4, the user ID at offset 57 is not set (low values), because we have
not been prompted for it as yet.
Example 6-4 EciB1 object/COMMAREA on initial call (created with -Dgateway.T.trace=on)
S-C: CCL6603I: # 00000: 47 61 74 65 00 40 00 00 00 00 00 01 00 00 00 00 Gate.@..........
S-C: CCL6603I: # 00016: 00 00 00 00 00 00 00 03 45 43 49 00 00 00 00 60 ........ECI....`
S-C: CCL6603I: # 00032: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................
S-C: CCL6603I: # 00048: 00 53 43 53 43 50 4A 41 34 00 00 00 00 00 00 00 .SCSCPJA4.......
S-C: CCL6603I: # 00064: 00 00 00 00 00 00 00 00 00 2A 2A 2A 2A 2A 2A 2A .........*******
In Example 6-5, we see the second ECI request to the CICS TG, after we had
been prompted for a user ID and password. This time the user ID (CICSRS2) is
contained in the ECI request and you can see the password (********) is masked
for security reasons.
Example 6-5 EciB1 object/COMMAREA after ID and password input (created with -Dgateway.T.trace=on)
S-C: CCL6603I: # 00000: 47 61 74 65 00 40 00 00 00 00 00 01 00 00 00 00 Gate.@..........
S-C: CCL6603I: # 00016: 00 00 00 00 00 00 00 03 45 43 49 00 00 00 00 60 ........ECI....`
S-C: CCL6603I: # 00032: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................
S-C: CCL6603I: # 00048: 00 53 43 53 43 50 4A 41 34 63 69 63 73 72 73 32 .SCSCPJA4CICSRS2
S-C: CCL6603I: # 00064: 00 00 00 00 00 00 00 00 00 2A 2A 2A 2A 2A 2A 2A .........*******
Chapter 6. CICS TG security scenarios 111