Nondynamic transaction considerations

You do not have to include any calls through the API if a transaction is statically routed or is started by ATI. In these cases, the target region cannot be changed. The routing function is route notify. The route notify function is intended to notify the EYU9WRAM program that such a transaction is being routed.

If you do include any of these functions, the following occurs:
  • An SM_SCOPE call returns a single entry in the SCOP_VECT. The entry is the target region associated with the statically defined transaction when it was defined, or with the destination specified on the EXEC CICS START command for ATI transactions.
  • An SM_BALANCE call selects the target region associated with the transaction when it was defined to CICS. The CICSPlex® SM Workload Manager will not create any affinity for the transaction.
  • An SM_ROUTE call returns an exception response.
When EYU9WRAM is called for:
  • Notification, any existing affinity relations are ignored and none are created.
  • Route selection error, any existing affinity relations are ignored and none are created. In addition, the EYU9WRAM program as delivered will write a terminal message and terminate.
  • Routing attempt complete, for CICS BTS transactions only. Any existing affinities are ignored. Any dynamic routing API function call results in a bad response. See Non-terminal-related STARTs and CICS BTS considerations.
  • Transaction initiation, for CICS BTS transactions only. Any existing affinities are ignored. Any dynamic routing API function call results in a bad response. See Non-terminal-related STARTs and CICS BTS considerations.
  • Transaction termination, any existing affinities are ignored. Any dynamic routing API function call results in an error response.
  • Transaction abend, any existing affinities are ignored. Any dynamic routing API function call results in an error response.