Impact of having no paths in a class
- There are no signaling paths that are assigned to that class that lead to the other system.
- All the signaling paths that are assigned to that class that lead to the other system have temporarily or permanently failed.
When “ALL PATHS UNAVAIL” is not zero, there is interference between the transport classes. This means that the intended partitioning of message traffic is not obtained. Generally, you want to avoid this condition by assigning signaling paths to the transport class that lead to the intended target system. Messages migrated to an alternative signaling path incur more overhead for XCF to select an alternative transport class. Furthermore, these messages can degrade the performance of messages that are sent in the transport classes that are chosen as alternates; particularly if the buffer size that is used by the alternative class is smaller than the buffer size required by the migrated message.
Thus “ALL PATHS UNAVAIL” can be an indicator of severe problems with the transport class definitions and/or the resources that are assigned to the class. For example, if the transport class did have signaling paths that are defined for the target system but none are working due to a "stall" condition, then it is a possible sympathy sickness indication.
However, the severity of the interference between classes must be considered in light of the
number of message requests in the transport class as listed under REQ OUT
. If these messages
occur relatively infrequently, it might not be worth providing a signaling path for their exclusive
use.