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.

IOS028 IOV103<br />

(H<strong>CP</strong>LCICS) is adhering to the interface defined in the<br />

prologue.<br />

IOS028<br />

Explanation: Store-Subchannel (STSCH) simulation<br />

for a logical device indicated a return code 12, which<br />

correlates to a condition code 3 as defined by the XA<br />

Architecture for the STSCH instruction. A condition code<br />

3 indicates the subchannel is not provided in the<br />

channel subsystem.<br />

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

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

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

corresponding logical subchannel that appears to be<br />

non-existent. Verify that STSCH simulation module for<br />

logical devices (H<strong>CP</strong>LCIST) is adhering to the interface<br />

defined in the prologue.<br />

IOV001<br />

Explanation: The simulation routine for a fully<br />

simulated device invoked H<strong>CP</strong>IOVBK to back out of<br />

channel program simulation. H<strong>CP</strong>IOVBK was called<br />

after a GOTO rather than a CALL was used to invoke<br />

H<strong>CP</strong>IOV. It is impossible to continue processing the I/O<br />

request because there is no address available to which<br />

to return control.<br />

User Response: The SAVBK chain anchored in<br />

IORSAVE indicates the environment at the time of the<br />

failure. The <strong>CP</strong>CBK (in this SAVBK) indicates the status<br />

of simulation for the current CCW. SAVEBPNT should<br />

be 0, indicating an entry using H<strong>CP</strong>IOV<strong>CP</strong>.<br />

<strong>CP</strong>CRTNAD, which addresses the simulation routine<br />

being used, should equal VDEVSIMA. If these values<br />

are correct, then correct the simulation routine so that it<br />

does not call H<strong>CP</strong>IOVBK. Otherwise, try to determine<br />

how the SAVBK or <strong>CP</strong>CBK was damaged.<br />

IOV100<br />

Explanation: (soft abend) A device simulation routine<br />

returned prematurely to the virtual channel simulator.<br />

H<strong>CP</strong>IOV recognizes this situation when the simulation<br />

routine returns before presenting (ending) status for the<br />

current channel comm<strong>and</strong> word.<br />

User Response: The SAVBK chain anchored in<br />

IORSAVE indicates the environment at the time of the<br />

failure. The <strong>CP</strong>CBK (in this SAVBK) indicates the status<br />

of simulation for the current CCW. <strong>CP</strong>CRTNAD<br />

addresses the simulation routine being used. If the logic<br />

of the simulation routine causes it to return prematurely,<br />

correct it. Otherwise, try to determine how<br />

<strong>CP</strong>CDTFLG.<strong>CP</strong>CDTEND (byte.bit) was set off<br />

incorrectly.<br />

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

IOV101<br />

Explanation: (soft abend) A device simulation routine<br />

presented ending status more than once for a CCW.<br />

This situation occurs in H<strong>CP</strong>IOV when the module is<br />

reentered after previously processing ending status for<br />

the current channel comm<strong>and</strong> word.<br />

User Response: The SAVBK chain anchored in<br />

IORSAVE indicates the environment at the time of the<br />

failure. The <strong>CP</strong>CBK (in this SAVBK) indicates the status<br />

of simulation for the current CCW. <strong>CP</strong>CRTNAD<br />

addresses the simulation routine being used. If the logic<br />

of the simulation routine causes it to present status<br />

incorrectly, correct it. Otherwise try to determine how<br />

<strong>CP</strong>CDTFLG.<strong>CP</strong>CDTEND (byte.bit) was set on<br />

incorrectly.<br />

Note: H<strong>CP</strong>IOVUS may have been entered using a<br />

CALL to H<strong>CP</strong>IOVUC.<br />

IOV102<br />

Explanation: (soft abend) A device simulation routine<br />

presented channel end more than once for a channel<br />

comm<strong>and</strong> word (CCW). This situation occurs when<br />

H<strong>CP</strong>IOV is reentered after previously processing<br />

channel end for the current CCW.<br />

User Response: The SAVBK chain anchored in<br />

IORSAVE indicates the environment at the time of the<br />

failure. <strong>CP</strong>CRTNAD addresses the simulation routine<br />

being used. If the logic of the simulation routine causes<br />

it to present channel end status more than once per<br />

CCW, correct it. Otherwise, try to determine how<br />

<strong>CP</strong>CDTFLG.<strong>CP</strong>CDTCER (byte.bit) was set on<br />

incorrectly.<br />

Note: H<strong>CP</strong>IOVUS may have been entered using a<br />

CALL to H<strong>CP</strong>IOVUC.<br />

IOV103<br />

Explanation: (soft abend) After accepting a channel<br />

comm<strong>and</strong> word (CCW), a device simulation routine<br />

presented status without channel end. This situation<br />

occurs when H<strong>CP</strong>IOV is reentered after previously<br />

processing an (explicit or implied) initial status of zero<br />

for the current CCW.<br />

User Response: The SAVBK chain anchored in<br />

IORSAVE indicates the environment at the time of the<br />

failure. The <strong>CP</strong>CBK (in this SAVBK) indicates the status<br />

of simulation for the current CCW. <strong>CP</strong>CRTNAD<br />

addresses the simulation routine being used. If the logic<br />

of the simulation routine causes it to present status<br />

incorrectly, correct it. Otherwise attempt to determine<br />

how <strong>CP</strong>CDTFLG.<strong>CP</strong>CDTBEG was set on incorrectly.<br />

Note: H<strong>CP</strong>IOVUS may have been entered using a<br />

CALL to H<strong>CP</strong>IOVUC. Any call to H<strong>CP</strong>IO<strong>VM</strong>V<br />

implies an initial status of zero.

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

Saved successfully!

Ooh no, something went wrong!