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
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
H<strong>CP</strong>8610E Condition code of condcode upon<br />
return from DIAGNOSE X'A0' subcode<br />
X'34' processing.<br />
Explanation: The SECTABLE application program<br />
invokes DIAGNOSE X'A0' subcode X'34'. An error<br />
(probably a paging error) occurred during the<br />
DIAGNOSE.<br />
<strong>System</strong> Action: The application terminated.<br />
User Response: Report the matter to your system<br />
administrator.<br />
H<strong>CP</strong>8611E Severe error occurred during<br />
DIAGNOSE X'A0' SUBCODE X'34'<br />
processing.<br />
Explanation: Either a specification exception,<br />
privileged operation exception, or a protection exception<br />
occurred while the SECTABLE application program was<br />
running.<br />
<strong>System</strong> Action: The application terminated.<br />
User Response: Report this event to your system<br />
programmer.<br />
<strong>System</strong> Programmer Response: If a specification<br />
exception occurred, it means that the buffer address in<br />
R x is not within the caller’s virtual machine.<br />
If a privileged operation exception occurred, it means<br />
that the user who issued the DIAGNOSE X'A0' subcode<br />
X'34' was not authorized to do so.<br />
If a protection exception occurred, it means that the<br />
buffer whose address is in R x is fetch-protected against<br />
the user who issued the DIAGNOSE.<br />
H<strong>CP</strong>8700I The variations of this message are<br />
explained below.<br />
MESSAGES:<br />
v Emulated Device rdev cannot be varied online<br />
because <strong>CP</strong> was unable to open the device.<br />
Explanation: The indicated emulated device is not<br />
brought online because <strong>CP</strong>’s attempt to initialize<br />
(open) the real SCSI device associated with it failed.<br />
<strong>System</strong> Action: The emulated device is not brought<br />
online; system operation continues.<br />
User Response: Attempt to bring the emulated<br />
device online by issuing the VARY comm<strong>and</strong>. If<br />
attempts continue to fail, there may be a hardware<br />
malfunction with the SCSI device. Contact your<br />
system support personnel.<br />
v Emulated Device rdev cannot be varied online<br />
because there are no valid paths defined to the<br />
device.<br />
Explanation: The indicated emulated device is not<br />
brought online because there are no valid paths<br />
associated with it.<br />
<strong>System</strong> Action: The emulated device is not brought<br />
online, <strong>and</strong> any invalid path definitions are no longer<br />
associated with the emulated device; system<br />
operation continues.<br />
User Response: Examine the device definition for<br />
the emulated device (EDEVICE statement or <strong>CP</strong> SET<br />
EDEVICE comm<strong>and</strong>), issue a <strong>CP</strong> SET EDEVICE<br />
comm<strong>and</strong> to add valid paths to the emulated device<br />
definition, <strong>and</strong> then attempt to bring the emulated<br />
device online by issuing the VARY comm<strong>and</strong>.<br />
v Emulated Device rdev cannot be varied online<br />
because its size is greater than 2,147,483,640<br />
512-byte blocks.<br />
Explanation: The indicated emulated device is not<br />
brought online because the size of the real SCSI<br />
device associated with it is too large.<br />
<strong>System</strong> Action: The emulated device is not brought<br />
online; system operation continues.<br />
User Response: Contact your system administrator<br />
to have the real SCSI device reconfigured to a<br />
supported size or associate the emulated device to a<br />
different smaller real SCSI device by using the <strong>CP</strong><br />
SET EDEVICE comm<strong>and</strong>.<br />
H<strong>CP</strong>8701I The variations of this message are<br />
explained below.<br />
MESSAGES:<br />
H<strong>CP</strong>8610E H<strong>CP</strong>8701I<br />
v Path F<strong>CP</strong>_DEV rdev1 WWPN wwpn LUN lun was<br />
deleted from EDEV rdev2 because device rdev1 is<br />
not an F<strong>CP</strong> Device.<br />
Explanation: The emulated device was being varied<br />
online <strong>and</strong> the specified path was deleted from the<br />
EDEV because F<strong>CP</strong>_DEV rdev1 is not an F<strong>CP</strong><br />
device.<br />
<strong>System</strong> Action: The path is deleted from the EDEV<br />
<strong>and</strong> system operation continues.<br />
User Response: Use the <strong>CP</strong> QUERY F<strong>CP</strong> comm<strong>and</strong><br />
to find an F<strong>CP</strong> device that can be used for a path to<br />
the emulated device <strong>and</strong> then issue a <strong>CP</strong> SET<br />
EDEVICE comm<strong>and</strong> to add a valid path to the<br />
emulated device.<br />
v Path F<strong>CP</strong>_DEV rdev1 WWPN wwpn LUN lun was<br />
deleted from EDEV rdev2 because F<strong>CP</strong> device<br />
rdev1 is not online.<br />
Explanation: The emulated device was being varied<br />
online <strong>and</strong> the specified path was deleted from the<br />
EDEV because F<strong>CP</strong> device rdev1 is not online.<br />
<strong>System</strong> Action: The path is deleted from the EDEV<br />
<strong>and</strong> system operation continues.<br />
User Response: Try to vary the F<strong>CP</strong> device online<br />
<strong>and</strong> then add the path back to the emulated device<br />
by issuing a <strong>CP</strong> SET EDEVICE comm<strong>and</strong>.<br />
v Path F<strong>CP</strong>_DEV rdev1 WWPN wwpn LUN lun was<br />
deleted from EDEV rdev2 because F<strong>CP</strong> device<br />
rdev1 is dedicated.<br />
Chapter 3. <strong>System</strong> <strong>Messages</strong> 451
Change language