IOS125I

Explanation
During NIP, multiple devices have not responded
in a reasonable amount of time to an I/O request for path validation
that was initiated down a specific channel path. This might have occurred
due to a hardware malfunction.
In the message text: cc
The channel path causing the I/O timeouts.

System action
The system purges the outstanding I/O requests
and does not take any action on the channel path specified in the
message.  If no external action is taken, timeouts might continue
to occur for devices which use the affected channel path.

Operator response
Contact the system programmer.

System programmer response
If there are many devices attached
to this channel path, you can take action to prevent the system from
continuing to experience timeouts on this channel path. To do this,
the channel path can be configured offline from the Hardware Management
Console (HMC).
Note: Be aware that configuring a channel path offline
from the HMC at this time might have some adverse effects on the system:When a channel path is configured on or off via the HMC, the operating
system might not be notified causing the operating system's (S/W)
view of the channel path's state to be out of sync with the actual
state (H/W). Therefore, as IPL continues after this point, there might
be inconsistencies between hardware and software with respect to the
channel path causing possible software errors. You can use the D M=CHP(cc) MVS™ operator command to determine
if such inconsistencies are present.
In certain circumstances, there is a chance the console might
become flooded with IOS error messages. One case where this might
occur is when the last path to a set of devices is configured offline
by the HMC.

Due to these effects, a re-IPL should be done after
action has been taken at the HMC to configure the faulty channel path.
 Note that as NIP path validation continues, timeouts as a result
of other faulty channel paths might cause additional IOS125I messages
to be issued.  Therefore, the re-IPL should be done when action has
been taken to address all faulty channel paths. As the channel paths
are now offline, they will not be used for the re-IPL and will not
cause additional timeouts. If a re-IPL absolutely cannot be tolerated,
it is possible to sync up the operating system's (S/W) view of the
channel path with the actual state (H/W) of the channel path by issuing
a CONFIG CHP(cc),OFFLINE MVS operator
command after IPL has completed and MVS is
ready to accept commands.  However, take note that allowing the system
to continue to IPL at this point may result in software errors during
IPL due to the inconsistencies explained in the note above.
You
should determine the cause of the hardware problem. If an IPL is needed
prior to fixing the problem, keep the problematic CHPID out of the
configuration, or ensure it is offline prior to IPL.
Note: In all
other circumstances, IBM® strongly
recommends that you use the operating system facilities, when fully
available, rather than the Hardware Management Console to configure
channel paths on and off.  See the z/OS® Hardware
Management Console Operations Guide for more information.

Problem determination
Contact hardware support.

Source
Input/output supervisor (IOS)

Module
IEAVNP02

Routing code
2

Descriptor code
12