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

124 CICS Transaction Gateway V5
new Terminal(
epiGate, // CICS TG URL
cicsRegion, // CICS server
null, // device type
null, // netname
Terminal.EPI_SIGNON_INCAPABLE,
userid, // userid for CTIN
password, // password
0, // timeout
null); // encoding
Screen scr = term.getScreen();
term.connect(); // install terminal with CTIN
term.setUserid(userid); // set userid for EPI request
term.setPassword(password); // set passowrd
scr.field(1).setText("EPIP"); // set EPIP user transaction code
scr.setAID(AID.enter);
term.send(); // start EPIP transaction
....
Figure 6-11 Using a signon incapable terminal
To enable access from our SignonIncapable application to our EPIP test
transaction, it was necessary to grant READ access for our CICSRS2 user ID to
the RACF profiles protecting both the EPIP and CTIN transactions as follows:
PERMIT SCSCPJA4.CTIN CLASS(TCICSTRN) ID(CICSUSER) ACCESS(READ)
PERMIT SCSCPJA4.EPIP CLASS(TCICSTRN) ID(CICSRS2) ACCESS(READ)
SETROPTS RACLIST(TCICSTRN) REFRESH
Tip: Unlike signon capable terminals, we found that when using signon
incapable EPI terminals, we also had to ensure the link user ID had READ
access to the TCICSTRN profile protecting the EPIP and CTIN transactions.
However, instead of creating another profile, we fixed this by making our
systems equivalent, by setting the SECURITYNAME in the CONNECTION
definition to be the same as the region user ID (SCSCPJA4), as shown in
Figure 6-8.