Maintaining MRO/ISC Environment › MRO/ISC Transaction Routing

MRO/ISC Transaction Routing

This MRO/ISC setup is where each transaction is defined to the TOR as a remote transaction. You enter the desired transaction and through internal CICS definitions it is routed to the defined AOR CICS.

A transaction defined in the TOR can be defined as the same transaction in the AOR. This method requires the user to remember which transaction is associated to which AOR CICS. Also, this method requires a separate DBCVTPR macro be defined in each AOR CICS to allow processing to proceed. For example, the following table illustrates a TOR connected to three AORs defined as SYSA, SYSB and SYSC with transactions DBC1, DBC2, and DBC3 being DBOC in each AOR CICS respectively. The following table graphically shows that when DBC2 is entered in the TOR it is routed to AOR CICS name SYSB and runs transaction DBC2 in that AOR.

A transaction defined in the TOR can be defined as another transaction in the AOR. If DBOC is not renamed in the AORs, it is not necessary to supply the DBOC parameter in the DBCVTPR macro for the AORs. In the TOR, each transaction definition that routes a DBOC to an AOR must have a remote name of DBOC, as illustrated in the following table.

DBC1 would then route a DBOC to AOR SYSA, and DBC2 would route a DBOC to AOR SYSB, and so on.