A module detected an inoperative condition for a resource. This message follows message IST1222I, IST1501I, or IST1717I.
trlename is the name of the TRLE definition statement in the TRL major node that defines the MPC connection, or the system-generated TRLE that represents the 10GbE RoCE Express interface.
modname is the name of the module that detected the inoperative condition.
The inoperative condition was issued because of a VTAM internal logic error.
The inoperative condition was probably generated due to unexpected channel status presented to VTAM from the hardware.
This condition could not be categorized into either a software or hardware error.
VTAM provides the ability to take a diagnostic dump when an inoperative condition is detected. The INOPDUMP and INOPCODE start options and commands are used to enable the dump function for specific resources, modules, and codes. See z/OS Communications Server: SNA Operation for information about the INOPDUMP command and the INOPCODE command.
If modname is ISTTSC8W and code is 200, this indicates a failure when VTAM is trying to send data to another node in a sysplex via the Cross-system Coupling Facility (XCF). If this message is preceded by MVS™ message IXC409D, an XCF signaling path between the two nodes was lost. The resource, trlename, is the name of the dynamic XCF TRLE used by VTAM for connectivity between the two nodes. A display of the corresponding dynamic XCF PU will show the CP name of the other node. The VTAM in this other node might not be aware of the inoperative condition. The loss of the XCF signaling path might be transient or permanent. When the signaling path is restored, the VTAM in the other node will be informed of the inoperative condition of this connection, and the corresponding PU in that node will go inoperative. Connectivity can be restored at that time by reactivating one of the PUs.
If inoptype is DEVICE and trlename represents an MPC connection, the channel listed in the preceding message is deactivated. The device might be dynamically added back to the active group without disruption using APPN host-to-host channel dynamics.
If inoptype is DEVICE and trlename represents a 10GbE RoCE Express interface, the 10GbE RoCE Express interface listed in the preceding message is deactivated. The TCP/IP stack might attempt recovery of the 10GbE RoCE Express interface.
If inoptype is HARD, resource trlename is deactivated and all service access points (SAPs) for trlename are notified of the condition.
If inoptype is SOFT, resource trlename is deactivated and all service access points (SAP) for trlename are notified of the condition. VTAM attempts to reactivate trlename.
If inoptype is DEVICE and trlename represents an MPC connection, no further action is required.
If inoptype is DEVICE and trlename represents a 10GbE RoCE Express interface, no further action is required. If recovery fails, save the system log for problem determination.
If inoptype is HARD, reactivate resource trlename. If the activation fails, and the MPC group is critical to your network, save the system log for problem determination.
If inoptype is SOFT, and this is the first occurrence of the message, no further action is required. If inoptype is SOFT, and this is not the first occurrence of the message, attempt to reactivate trlename. If the activation fails, and the MPC group is critical to your network, save the system log for problem determination.
For code values in the "probable hardware error" category, contact the appropriate hardware support organization to analyze this error.
2
5