z/VM: System Messages and Codes Š CP - z/VM - IBM

ICL002 IFI002
and determine how it became unacceptable.
ICL002
Explanation: (Soft abend) No ICLBK located for
dynamic loaded entry.
User Response: Examine the chain of ICLBKs to
determine why the external symbol, which was marked
as having been loaded by CPXLOAD, was not in the
chain of ICLBKs.
IDS001
Explanation: (soft abend) When receiving a message
complete after a *IDENT IUCV SEND, the address to
which to return is zero.
User Response: Processing is ended, because there
is no way to return to the issuer of the IUCV SEND.
Refer to z/VM: Diagnosis Guide for information on
gathering the documentation you need to assist IBM in
diagnosing the problem, then contact your IBM support
personnel.
IFH001
Explanation: HCPIFHIN; while processing an interrupt
from a subchannel type other than type 0, it was
determined the subchannel ID field contained in the
RDEV (RDEVSID) did not match the interrupt
parameter.
User Response: Examine the I/O interrupt parameter
stored by the hardware at location x’B8’. This I/O
interrupt parameter consists of a subchannel ID and the
associated RDEV address. Check the data that the
second word of the interrupt parameter points to for the
following possibilities:
v The interrupt parameter points to the RDEV
associated with the interrupt subchannel, but the
RDEVSID field does not match the interrupting
subchannel ID. Most likely the RDEVSID field was
overlaid.
v The interrupt parameter points to an RDEV that is not
associated with the interrupting subchannel ID.
HCPIOS may have issued Start Subchannel (SSCH)
with an incorrect RDEV address specified in the
Operation Request Block (ORB). Examine the CP
trace table entries to see if a SSCH was issued for
the interrupting subchannel ID and look at the ORB.
v The interrupt parameter does not point to an RDEV.
Either the entire RDEV was overlaid, or HCPIOS may
have issued a SSCH with an incorrect RDEV address
specified in the ORB. Examine the CP trace table
entries to see if a SSCH was issued for the
interrupting subchannel ID and look at the ORB.
48 z/VM: System Messages and Codes — CP
IFH004
Explanation: HCPIFHIN was attempting to transfer
control to the interrupt response address specified in the
IORBK field IORIRA, but it contained zeros.
User Response: Check R10 to ensure it is pointing to
a valid IORBK. If R10 contains the address of an
IORBK, the interrupt response address was probably
destroyed or never set when the request was initiated.
Also examine the status in the IORBK.
IFI001
Explanation: HCPIFIIN, while processing an I/O
interrupt, determined that the subchannel ID field
contained in the RDEV (RDEVSID) did not match the
interrupt parameter.
User Response: Examine the I/O interrupt parameter
that the hardware stored at location x’B8’. This I/O
interrupt parameter consists of a subchannel ID and the
associated RDEV address. Check the data that the
second word of the interrupt parameter points to for the
following possibilities:
v The interrupt parameter points to the RDEV
associated with the interrupt subchannel, but the
RDEVSID field does not match the interrupting
subchannel ID. Most likely the RDEVSID field was
overlaid.
v The interrupt parameter points to an RDEV that is not
associated with the interrupting subchannel ID.
HCPIOS may have issued SSCH (Start Subchannel)
with an incorrect RDEV address specified in the ORB
(Operation Request Block). Examine the CP trace
table entries to see if a SSCH was issued for the
interrupting subchannel ID and look at the ORB.
v The interrupt parameter does not point to an RDEV.
Either the entire RDEV was overlaid, or HCPIOS may
have issued a SSCH with an incorrect RDEV address
specified in the ORB. Examine the CP trace table
entries to see if a SSCH was issued for the
interrupting subchannel ID and look at the ORB.
IFI002
Explanation: HCPIFI attempted to initiate an I/O
operation while another one was in progress for the
same real device. An I/O condition code 2 was received
in response to a SSCH (Start Subchannel) for a Sense
operation.
User Response: Examine the CP trace table to
analyze other events relating to that subchannel. Look
at the RDEV (pointed to by R8) HCPIFI uses to manage
the real device. The active IORBK pointer (RDEVAIOR)
may have been reset to zero prior to I/O completion,
causing HCPIFI to prematurely initiate the Sense
operation. Another possibility is that the system did not
hold onto a previously initiated operation.