Explanation
The system found the condition appearing in the
message text. One of the following occurred:
- The condition existed for a longer time than the acceptable time
defined by the installation.
- A missing interrupt handler (MIH) exit routine indicates that
the system will not reset the device with a Clear Subchannel (CSCH)
instruction.
In the message text:
- devn
- The device number. The device number is prefixed by the subchannel
set identifier when appropriate.
- chp
- The channel path identifier (CHPID) of the channel path that was
used for the I/O operation, or a residual channel path from the last
I/O operation for the device, or asterisks if a channel path cannot
be determined.
This field contains the CHPID used for the I/O operation
that appears in the message under the following conditions:
- MISSING CHANNEL AND DEVICE END appears in the message
- MISSING DEVICE END appears in the message
- START PENDING appears in the message and this is a zHPF I/O operation
- START PENDING appears in the message, this is a non-zHPF I/O operation,
and the I/O operation was directed to a specific channel path.
- HYPERSWAP INITIATED TIMEOUT appears in the message.
This field contains a residual CHPID from the last I/O operation
for the device under the following conditions. This is not necessarily
the channel path where an error occurred.
- IDLE WITH WORK QUEUED
- HALT SUBCHANNEL INTERRUPT MISSING
- CLEAR SUBCHANNEL INTERRUPT MISSING
This field contains asterisks when:
- No channel path is associated with the missing interruption.
For example, when START PENDING appears in the message, this is a
non-zHPF I/O request, and the I/O request was not directed to a specific
channel path.
- The last path used mask (LPUM) is not valid.
- jobname
- The name of the job associated with the device.
- text
- A description of the missing interruption condition. It can be
one of the following:
- MISSING CHANNEL AND DEVICE END or MISSING DEVICE END
- A hardware error occurred.
- START PENDING
A hardware error occurred. The channel has an I/O request to
process. The device is not active or it is busy on another channel
path interface. If the device is reserved by another system, message
IOS431I might follow; it identifies the system holding the reserve.
If
message IOS431I is issued, the system routes the D U,VOL and then
the D GRS,DEV commands to the failing system to identify the jobs
holding the reserve. It identifies the jobs in message ISG020I if:
- The failing system is in the sysplex
- The failing system responds to the D GRS command within 30 seconds
- No other system is attempting this at the same time.
- IDLE WITH WORK QUEUED
- A hardware or software error occurred. The channel has no active
I/O requests.
- HALT SUBCHANNEL INTERRUPT MISSING
- CLEAR SUBCHANNEL INTERRUPT MISSING
- A hardware error occurred.
- HYPERSWAP INITIATED TIMEOUT
- A HyperSwap® was in
progress. MIH detects this condition and immediately times out any
active I/O for any device being swapped. The I/O request is cancelled
and requeued for later execution once the swap is complete.
- statustext
- The state of the I/O operation prior to detecting the missing
interruption condition. It can be one of the following:
- NO I/O OPERATION IS IN PROGRESS
- The device does not know about this I/O operation. This can occur
for one of the following reasons:
- The I/O operation was lost in transit to the device.
- The I/O operation ended just before the device was
queried to determine the state.
- I/O OPERATION IS EXECUTING
- The I/O operation is currently active for this device. This might
occur for a long running channel program.
- I/O WAITING FOR I/O OPER FROM ANOTHER SYSTEM
- The I/O operation is delayed because it is waiting for the completion
of another I/O operation (other than a device reserve) from another
system.
- I/O WAITING FOR EXTENT CONFLICT
- The I/O operation is delayed because it is attempting to access
a DASD extent that is in use by another I/O operation.
- I/O WAITING FOR DEVICE DEPENDENT OPERATION
- The I/O operation is delayed because it is waiting for completion
of a device dependent operation. For example, data needs to be staged
into the cache from disk.
- DEVICE RESERVED BY ANOTHER SYSTEM
- The I/O operation is delayed because the device is reserved by
another system. Message IOS431I is also issued to identify the system
holding the reserve.
- DEVICE RESERVED TO THIS SYSTEM
- The I/O operation is delayed because the device is reserved to
this system on one or more channel paths for the device, but the I/O
operation used a different path. This occurs during a path group out
of synch condition, where some online paths are in the path group
and some are not. Recovery will be performed to correct this condition.
- DEVICE RESERVED
- The I/O operation is delayed because the device is reserved. This
message is issued when z/OS® is
running as a guest under VM and it is unable to determine whether
the current system or another system holds the reserve.
- DEVICE IS LONG BUSY
- The I/O operation is delayed because the device is in a long busy
state.
- DEVICE RECOVERY IS IN PROGRESS
- The I/O operation is delayed because device recovery is in progress.
For example, a disk drive failed and RAID recovery is in progress
to reconstruct the data.
- CONTROL UNIT IS BUSY
- The I/O operation is delayed because the control unit is busy.
- CONTROL UNIT RECOVERY IS IN PROGRESS
- The I/O operation is delayed because control unit recovery is
in progress.
System action
The system action depends on the message text.
It is one of the following:
- MISSING CHANNEL AND DEVICE END
- MISSING DEVICE END
- The system issues a Clear Subchannel (CSCH) instruction to reset
the device.
- START PENDING
- If the status text is present and indicates that the device is
reserved to another system, the I/O operation is allowed to continue,
and the system issues message IOS431I, identifying the system holding
the reserve.
Otherwise, the system resets the device and restarts
the I/O request.
- IDLE WITH WORK QUEUED
- The system resets the device and passes an I/O request to the
channel. The system sends work to the device. The system may issue
message IOS075E.
- HALT SUBCHANNEL INTERRUPT MISSING
- The system does not reset the device.
- CLEAR SUBCHANNEL INTERRUPT MISSING
- The system does not do any further processing on the device until
a clear subchannel interruption occurs.
- HYPERSWAP INITIATED TIMEOUT
- The system cancels the I/O and requeues it so the HyperSwap can proceed.
Operator response
Depending on the message text, do the following:
- START PENDING
- Do the following:
- Determine whether the affected devices are reserved
for the failing system.
- Perform the recovery procedures defined by your installation.
Note: If
no devices are reserved for the failing system, resetting the reserves
may cause integrity problems.
- If the system is in a check stop state or restartable
wait state, initiate an interface reset from the system console of
the nonoperational system.
- If the interface reset is unsuccessful, initiate a
system reset from the system console of the nonoperational system.
- Notify the system programmer.
Note: If the system issued message IOS431I, take the actions
described in the operator response for that message.
- IDLE WITH WORK QUEUED
- If the system issued message IOS075E, notify the system programmer.
- HYPERSWAP INITIATED TIMEOUT
- A HyperSwap is in
progress. No action is necessary.
For other values in the message text, contact
hardware support.
System programmer response
If the error persists, dynamically
adjust the MIH values.
Source
Input/output supervisor (IOS)
Module
Routing code
Descriptor code