01.01.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note that when a single <strong>CICS</strong> TG for z/OS region is configured to connect to<br />

more than one <strong>CICS</strong> region, you must use the same NETNAME for all of the<br />

EXCI connections.<br />

Note: It is quite possible to use the same DFHJVPIPE for multiple address<br />

spaces (that is, multiple <strong>Gateway</strong> daemons). However, in this way if all the<br />

address spaces connect to the same region, they will share the same<br />

connection, and this may adversely affect your ability to monitor traffic<br />

across the connection, and will also require a higher RECEIVECOUNT to<br />

be defined in the SESSIONS definition.<br />

► ACCESSMETHOD<br />

For EXCI connections, this must be specified as inter-region communication<br />

(IRC). EXCI is implemented through the IRC program (DFHIRP), using the<br />

supervisor call (SVC) mode of DFHIRP (as opposed to cross memory).<br />

DFHIRP can use the cross-system coupling facility (XCF) MRO links, but<br />

cannot use MVS cross-memory services (XM).<br />

► PROTOCOL<br />

For EXCI, this must be specified as EXCI.<br />

► CONNTYPE<br />

This is the type of EXCI connection used for non-<strong>CICS</strong> jobs to communicate<br />

with a <strong>CICS</strong> region on z/OS. It is a type of MRO request and must be<br />

specified as either specific or generic.<br />

– SPECIFIC: An MRO link with one or more sessions dedicated to a single<br />

user in a client program. For a specific connection, the NETNAME<br />

attribute is mandatory.<br />

– GENERIC: An MRO link with a number of sessions to be shared by<br />

multiple EXCI users. Only one generic EXCI connection can be installed in<br />

each region. For a generic connection, the NETNAME attribute must be<br />

left blank.<br />

► ATTACHSEC<br />

Controls the security checks made using the flowed user ID.<br />

– IDENTIFY: Specifies to <strong>CICS</strong> that a user ID will be flowed on every<br />

request, but no password is expected as <strong>CICS</strong> will trust the user ID as<br />

having been already authenticated. When using the <strong>CICS</strong> TG for z/OS the<br />

user ID will be either the user named in the ECIRequest object or, if null,<br />

the user ID of the thread the ECI request runs under.<br />

Chapter 4. EXCI connections to <strong>CICS</strong> 69

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!