EYUXL0138I I   EYU9XLOP waiting for workload

Explanation

This message occurs in a region that has specified EYU9XLOP as the distributed or dynamic routing exit, when that region is not connected to a workload.

System action

If EYU9XLOP was specified, and there is no workload associated with the region, then any request to CICS that drives the appropriate routing exit causes CICS to invoke EYU9XLOP, which then goes into a wait state. Requests that may drive one of the routing exits include, for example, dynamic and undefined transactions, EXEC CICS START commands, CICS BTS activities, and dynamic program link requests.

User response

Ensure that you only specify EYU9XLOP when you have a workload associated with the region, by using one of the following procedures:
  • Change the specified routing module
  • Associate the region with a workload, then activate WLM in the region in one of the following ways:
    • Recycle the region
    • Stop and restart the MAS agent code in the region. For example, use the COSH transaction to stop the MAS agent code and the COLM transaction to restart the MAS agent code.

Module

EYU9XLOP

Destination

Console and SYSPRINT



EYUXL0138I.html | Timestamp icon Last updated: Sunday, 4 June 2017