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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ISC001 IUB001<br />

will not be totally cleared as requested.<br />

Examine the internal trace table <strong>and</strong> storage dump to<br />

determine why a return code other than 8 was received<br />

from H<strong>CP</strong>IOSFD.<br />

ISC001<br />

Explanation: (soft abend) The address of the prefix<br />

page could not be found for a request to update control<br />

register 6 for a dedicated processor.<br />

User Response: Verify register 1 contains a valid<br />

processing unit address. Contact the <strong>IBM</strong> support<br />

personnel.<br />

IST001<br />

Explanation: The RDEV for the DASD on which the<br />

SYSRES volume is mounted cannot be located or is not<br />

an owned volume.<br />

User Response: Verify that the volume serial number<br />

on the SYSRES volume from which the IPL was<br />

attempted is the same as that specified in the field<br />

SYSVOL. If the volume serial number is not the same, a<br />

st<strong>and</strong>-alone utility (such as DDRXA) may have altered<br />

it, or the image of the same nucleus saved on the<br />

SYSRES may have been partially destroyed <strong>and</strong> the<br />

SYSRES specification altered. Load or restore the<br />

nucleus from a backup copy to the SYSRES volume<br />

<strong>and</strong> try to IPL again.<br />

IST002<br />

Explanation: The RDEV block for the IPLed device is<br />

not type CLASDASD or it does not have the same<br />

device type the user specified at system generation<br />

time.<br />

User Response: Check the SYSDTYP in the SYSCM<br />

area against the SYSRES volume from which the IPL<br />

was attempted. If the RDEV does not indicate the actual<br />

device type correctly, mount the pack elsewhere <strong>and</strong> try<br />

again. If SYSDTYP does not indicate the device type<br />

correctly, load <strong>and</strong> restore the nucleus from a backup<br />

copy to the SYSRES volume <strong>and</strong> try to IPL again.<br />

IST003<br />

Explanation: A call to H<strong>CP</strong>PTRSA to get a PGMBK<br />

for a segment was made with an incorrect address in<br />

R1. H<strong>CP</strong>PTRSA returned a condition code of 1.<br />

User Response: Examine the contents of the dump.<br />

Check the validity of the address in R1.<br />

ISU001<br />

Explanation: The system time-of-day (TOD) clock is<br />

not operational.<br />

User Response: Contact your <strong>IBM</strong> support personnel<br />

58 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />

for hardware support to fix the clock.<br />

ITM003<br />

Explanation: The system time-of-day (TOD) clock is<br />

not operational.<br />

User Response: Contact your <strong>IBM</strong> support personnel<br />

for hardware support to fix the clock.<br />

IUA001<br />

Explanation: (soft abend) An IUCV function was<br />

issued from <strong>CP</strong> (either by a <strong>CP</strong> system service or by<br />

IUCV itself), <strong>and</strong> <strong>CP</strong> detected a program check<br />

condition. If a virtual machine issued the IUCV function,<br />

<strong>CP</strong> would issue a program check. However, since the<br />

IUCV function was issued from within <strong>CP</strong>, this soft<br />

abend was issued instead of the exception.<br />

User Response: Determine the function executing <strong>and</strong><br />

who invoked IUCV (a <strong>CP</strong> system service or IUCV itself)<br />

using the IUSBK pointed to by R8. Refer to z/<strong>VM</strong>: <strong>CP</strong><br />

Programming Services to determine the <strong>CP</strong> system<br />

service associated with the code found in the IUSBK. If<br />

the code is 0, a virtual machine issued the function<br />

using IUCV. Examine the value in R0 to find the<br />

program interrupt code.<br />

IUA002<br />

Explanation: (soft abend) A <strong>CP</strong> system service<br />

invoked an IUCV function that required a buffer, but the<br />

<strong>CP</strong> system service did not supply one.<br />

User Response: Determine the <strong>CP</strong> system service<br />

that invoked IUCV <strong>and</strong> the function executing using the<br />

IUSBK pointed to by R8. Refer to z/<strong>VM</strong>: <strong>CP</strong><br />

Programming Services to determine the <strong>CP</strong> system<br />

service associated with the code found in the IUSBK.<br />

IUA003<br />

Explanation: (soft abend) An IUCV function was<br />

issued by a system service while an IUCV RTRVBFR<br />

was in progress.<br />

User Response: Identify the system service that is<br />

behaving incorrectly. R10 holds the IUCVB of the<br />

system service. R9 holds the address of the CCTBK of<br />

the system service. Also check the contents of<br />

SAVEWRK1, pointed to by R13, which holds the unique<br />

function code of the system service.<br />

IUB001<br />

Explanation: (soft abend) The IUCV PDEBK structure<br />

is incorrect. The target’s side does not correspond with<br />

the invoker’s side.<br />

User Response: Determine who invoked IUCV using<br />

the IUSBK pointed to by R10. Examine the condition<br />

code:

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

Saved successfully!

Ooh no, something went wrong!