28.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IFI004<br />

Explanation: H<strong>CP</strong>IFIIN was attempting to do one of<br />

the following:<br />

v Transfer control to the interrupt response address<br />

specified in the IORBK field IORIRA, but it contained<br />

zeros.<br />

v Call the emergency error recovery procedure, but<br />

was unable to resolve its address.<br />

User Response:<br />

v For the first case, check R10 to see that it is pointing<br />

to a valid IORBK. If R10 contains the address of an<br />

IORBK, the interrupt response address was probably<br />

destroyed or never set when the request was<br />

initiated. Also examine the status in IORBK.<br />

v For the second case, verify that the emergency error<br />

recovery procedure (H<strong>CP</strong>IEERP) was included in the<br />

system.<br />

IFI005<br />

Explanation: (soft abend) The test subchannel<br />

(TSCH) test function control bits (IRBFCTL) <strong>and</strong> activity<br />

control bits (IRBACTL) are zeros, indicating no valid<br />

status.<br />

User Response: The XA architecture expects a<br />

status. This is probably a hardware malfunction. Call<br />

your <strong>IBM</strong> hardware representative to diagnose the<br />

malfunction.<br />

IFI006<br />

Explanation: H<strong>CP</strong>IFI attempted to process an IORBK<br />

with the IORXFLG.IRO<strong>CP</strong>SUS bit on, but field<br />

IORSUSND was zero.<br />

User Response: Examine the IORBK, the RDEV, <strong>and</strong><br />

the <strong>CP</strong> trace table to determine what routine obtained<br />

the IORBK. Verify that the routine that built the IORBK<br />

correctly set both the IORSUSND field <strong>and</strong> the<br />

IOR<strong>CP</strong>SUS bit. If the routine did not, correct that<br />

routine. If it did, attempt to determine how IORSUSND<br />

was set to zero (or how IOR<strong>CP</strong>SUS was set to one).<br />

IFI007<br />

Explanation: (Soft abend) Return code 4 has been<br />

received from the error recover routine. This return code<br />

is incorrect <strong>and</strong> should not occur.<br />

User Response: This is probably a programming<br />

error. Examine the <strong>CP</strong> trace table to analyze the events<br />

relating to that subchannel which led to this incorrect<br />

return code being issued.<br />

IFI020<br />

Explanation: Start subchannel (SSCH) simulation for<br />

a Sense operation for a logical device resulted in one of<br />

the following:<br />

v A return code that was greater than 12 or not a<br />

multiple of 4.<br />

v A return code 8, which correlates to a SSCH<br />

condition code 2. An I/O operation was attempted<br />

while another one was in progress for the same<br />

logical device.<br />

User Response: Examine the <strong>CP</strong> trace table to<br />

analyze other events relating to the logical device or<br />

subchannel.<br />

Look at the RDEV (pointed to by R8), which is used by<br />

H<strong>CP</strong>IFI to manage the logical device. The RDEV field,<br />

RDEVLSOP, points to the corresponding logical<br />

subchannel.<br />

Verify that the SSCH simulation module for logical<br />

devices (H<strong>CP</strong>LCISS) is adhering to the interface defined<br />

in the prologue.<br />

IFI021<br />

Explanation: Test subchannel (TSCH) simulation for a<br />

logical device indicated one of the following:<br />

v A return code that was greater than 12 or not a<br />

multiple of 4.<br />

v A return code 8, which correlates to a TSCH<br />

condition code 2 which is undefined by the XA<br />

architecture.<br />

User Response: Look at the RDEV (pointed to by<br />

R8), which is used by H<strong>CP</strong>IFI to manage the logical<br />

device. The RDEV field RDEVLSOP points to the<br />

corresponding logical subchannel.<br />

Verify that the TSCH simulation module for logical<br />

devices (H<strong>CP</strong>LCITS) is adhering to the interface defined<br />

in the prologue.<br />

IIO001<br />

Explanation: The subchannel for the IPL device does<br />

not exist or cannot be modified.<br />

User Response: Verify that R8 contains the address<br />

of the RDEV for the IPL device. Try moving the IPL<br />

device to an address the system knows.<br />

IIO002<br />

IFI004 IIO002<br />

Explanation: The IPL device cannot be brought<br />

online.<br />

User Response: R15 contains the address of the<br />

error message describing the condition that prevented<br />

the IPL device from being brought online. Refer to the<br />

message description for the appropriate action.<br />

Chapter 2. <strong>System</strong> <strong>Codes</strong> 49

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!