|
Configuration samples |
|
|
This section describe some example configurations in different scenarios, where XCICS/TS or IBM CICS may act as TOR (Terminal Oriented Region) and/or AOR (Application Oriented Region). IBM CICS TOR to XCICS AOR This example describes the case of an IBM CICS region acting as TOR, routing transaction to an XCICS/TS region acting as AOR. In this scenario users will connect to the IBM CICS region (TOR), while the transactions will be remotely executed on the XCICS/TS region (AOR). CICS definitions: DEFINE CONNECTION(SUN1) GR(XCICS001) NETNAME(XCICS001) ACCESSMETHOD(VTAM) PROTOCOL(APPC) SINGLESESS(NO) XCICS definitions: define connection sysid=P390, type=sna, netname=CICS, mode=LU62APPB, acquire, os=ebcdic; XCICS TOR to IBM CICS AOR This example describes the case of an XCICS/TS region acting as TOR, routing transaction to an IBM CICS region acting as AOR. In this scenario users will connect to the XCICS/TS region (TOR), while the transactions will be remotely executed on the IBM XCICS region (AOR). CICS definitions: DEFINE CONNECTION(SUN1) GR(XCICS001) NETNAME(XCICS001) ACCESSMETHOD(VTAM) PROTOCOL(APPC) SINGLESESS(NO)
XCICS definitions:
define connection sysid=P390, type=sna, netname=CICS, mode=LU62APPB, acquire, os=ebcdic; XCICS TOR to XCICS AOR over SNA XCICS TOR definitions: define connection sysid=HP02, type=sna, netname=CICSHP02, mode=LU62APPB, acquire, os=ascii; XCICS AOR definitions: define connection sysid=SUN1, type=sna, netname=CICSSUN1, mode=LU62APPB, acquire, os=ascii; XCICS TOR to XCICS AOR over TCP/IPXCICS TOR definitions: XCICS TOR definitions: define connection sysid=SU1T, type=tcp, netname=CICSSUN1, hostname=solaris01, port=8094; XCICS AOR definitions: define connection sysid=LNX1, type=tcp, netname=CICSLX01, hostname=linux01, port=8094; |