How is tableBASE affected by CICSPLEX?
tableBASE is CICSPLEX compliant, but applications using tableBASE often require transaction affinities. A CICSPLEX consists of multiple CICS regions across multiple MVS images. IBMs CICSPLEX/SM makes administering such large numbers of CICS regions relatively simple by presenting a single image of the system. A key component of CICSPLEX/SM is workload balancing which is achieved by routing transactions to CICS regions that are the least busy. The dynamic transaction routing (DTR) function of CICS is used to route transactions from a TOR (Terminal Owning Region) to any one of many AORs (Application Owning Regions). Transactions that cannot be routed to any AOR have affinities. While the goal of CICSPLEX/SM is to have no transaction affinities; in practice, there will always be transactions that require some degree of affinity. In general, applications using tableBASE must be routed to the same AOR if they need to access a table that may have been updated or created in the TSR for that C
