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

152 CICS Transaction Gateway V5
use the EciI1 transactional ECI sample, which uses classes supplied in
ctgsamples.jar. To enable use of EciI1, we set the CTG_CLASSPATH in
ctgenvvar as follows:
CTG_CLASSPATH="${CTGSTART_HOME}/../classes/ctgclient.jar:${CTGSTART_HOME}
/../classes/ctgserver.jar:${CTGSTART_HOME}/../classes/cfwk.zip:
${CTGSTART_HOME}/../classes/ctgsamples.jar"
► CTG_RRMNAME
This is the name that the CICS TG registers with Resource Recovery
Services (RRS) for transactional EXCI requests to CICS. You will only need to
modify this if using transactional EXCI requests. The default RRMNAME is
CCL.CTG.IBM.UA. If you choose not to use the default name, you must obey
the naming rules for RRS groups.
The name can consist of the following printable characters:
– Alphanumeric characters: A-Z and 0-9
– National characters: $ (X'5B'), # (X'7B'), @ (X'7C')
– The period (.)
– The underscore (_)
RRM name restrictions include:
– The name cannot start with a blank or contain embedded blanks.
– Lowercase characters are converted to uppercase characters.
– To avoid naming conflicts, use A-C or G-I as the first character.
– The length of CTG_RRMNAME must not exceed 32 characters and must
end with the characters IBM.UA
Transactional EXCI: Transactional EXCI is an application programming
interface (API) that allows the CICS server unit of work to be continued over
multiple EXCI calls, until the EXCI client decides to commit or back out the unit
of work. This means that multiple ECI requests from the CICS TG for z/OS in
Extend_Mode can be part of the same logical unit of work, and can be
coordinated using a two-phase commit mechanism from the CICS TG for
z/OS to the CICS server.
The EXCI requests can only be transactional if the CICS TG started task using
the EXCI and the CICS region execute in the same z/OS image.