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

View status of EXCI calls
To view the status of active EXCI calls, issue the command CEMT INQ EXCI. The
results are shown in Figure 4-7.
INQ EXCI
STATUS: RESULTS
Exc(SCSCTG55.*OMVSEX. - SC66 ) Tas(0001608)
SYSID=PJA1 APPLID=SCSCPJA1
RESPONSE: NORMAL TIME: 19.30.26 DATE: 05.28.02
PF 1 HELP 3 END 5 VAR 7 SBH 8 SFH 9 MSG 10 SB 11 SF
Figure 4-7 Displaying an EXCI connection
The results in Figure 4-7 show that there is currently an EXCI request active
(task 1608) associated with the region SCSCTG55, which is one of the
processes used by our CICS TG, SCSCTG5.
XCF group membership
An important consideration when the CICS TG is used with the EXCI is the
usage of slots in the DFHIR000 XCF (cross-system coupling facility) group in the
sysplex couple data set. This XCF group is used by CICS when two address
spaces on different LPARs communicate by means of MRO or EXCI. The
maximum possible limit for group membership is 1023 members per group (it
was raised from 511 by APAR OW21511), but the actual limit is defined in the
MAXMEMBER parameter when the couple data set is formatted. To display this
limit, the MVS command /D XCF,COUPLE can be used. The output of this
command when we moved our Gateway region SCSCTG5 to another LPAR in
our sysplex is shown in Example 4-2. You can see that all the CICS regions in our
sysplex are listed as individual members (such as SCSCPJA1), but our Gateway
region has a member named for the thread under which the EXCI is running
(T02CEF40SC66), and not for the Gateway address space.
Example 4-2 Displaying XCF connections
IXC332I 13.47.38 DISPLAY XCF 105
GROUP DFHIR000: SCSCCOB1 SCSCERW1 SCSCERW2
SCSCERW3 SCSCLSA5 SCSCPAAS
SCSCPAAY SCSCPAA2 SCSCPAA6
SCSCPAGV SCSCPAME SCSCPJA1
SCSCPJA2 SCSCPJA4 T02CEF40SC66
Chapter 4. EXCI connections to CICS 79