When extended mode base Java™ requests,
or J2EE requests are being issued, the CICS® Transaction Gateway must
be on the same MVS® image
as the CICS region
it is sending requests to. The same restriction also applies to applications
that use the local protocol. These applications must be running on the same MVS image as the CICS region they
are sending requests to.
Certain restrictions affect where the Gateway daemon and
local applications can run:
- When J2EE transactions or extended LUW requests are being issued using
EXCI connections, the CICS® Transaction Gateway instance must execute on the
same MVS™ image as the CICS region that it is sending requests to.
- Each Gateway daemon that is configured as part of a Gateway group must
be run on the same MVS image.
- In a Gateway group, the ctgmaster process and all Gateway
daemon instances must use the same HFS installation.
- A maximum of 255 Gateway groups is allowed in an MVS image.