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.

DGB001 DGG002<br />

failure) after the current task incremented the counter,<br />

but before the current decrement.<br />

Since the deferred execution counter is the general<br />

mechanism to record outst<strong>and</strong>ing <strong>CP</strong> work, its<br />

mismanagement can result in:<br />

v A hung (or ″ghost″) user. This can occur if<br />

<strong>VM</strong>DDFRWK is incremented <strong>and</strong> never decremented.<br />

v This DFR017 abend (when <strong>VM</strong>DDFRWK is<br />

decremented without a prior increment).<br />

v A STK017 abend. This can occur if <strong>VM</strong>DDFRWK is<br />

not used when <strong>CP</strong> work is deferred. If the user (or<br />

<strong>VM</strong>DBK) completes logoff, the abend occurs on<br />

resumption of the deferred work (see the STK017<br />

abend description).<br />

DGB001<br />

Explanation: (soft abend) The number of active I/O<br />

requests (<strong>VM</strong>DIOACT) exceeded the number of defined<br />

devices (<strong>VM</strong>DDEVCT), or <strong>VM</strong>DIOACT was not a<br />

positive number while I/O was active.<br />

<strong>System</strong> operation continues.<br />

User Response: Examine the VDEV blocks for the<br />

virtual machine to determine how many requests were<br />

active at the time of the dump. Examine the system<br />

trace table to determine when the active requests were<br />

started, <strong>and</strong> what requests became inactive during this<br />

interval. Analyze the modules that incremented <strong>and</strong>/or<br />

decremented the <strong>VM</strong>DIOACT count. If the modules that<br />

update the field <strong>VM</strong>DIOACT contain correct logic, try to<br />

determine how the data in the field was destroyed.<br />

DGB002<br />

Explanation: (soft abend) The system is unable to<br />

continue processing because of an internal <strong>CP</strong> error.<br />

The code found in R14 indicates which error was<br />

detected.<br />

The following is a description of these codes:<br />

R14 = 1<br />

R14 = 2<br />

R14 = 3<br />

An unexpected return code was received from<br />

H<strong>CP</strong>DBIGL. Either the SBILIST length passed<br />

was greater than 4KB, or an undocumented<br />

return code was passed. Examine R15 to<br />

determine what return code was returned from<br />

H<strong>CP</strong>DBIGL.<br />

An unexpected return code was received from<br />

H<strong>CP</strong>DPSRW. DVICHSIZ field has been<br />

corrupted.<br />

An unexpected return code was received from<br />

H<strong>CP</strong>DPSTB. Examine R15 to see the return<br />

code.<br />

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

R14 = 4<br />

An unexpected return code was received from<br />

H<strong>CP</strong>DBIA4. Examine R15 to see the return<br />

code.<br />

User Response: Examine R15 to see the return code,<br />

<strong>and</strong> determine why this occurred.<br />

DGD001<br />

Explanation: The channel programs initiated by<br />

DIAGNOSE code x’18’ received a nonzero return code<br />

from the untranslation routine.<br />

User Response: Examine the host channel program,<br />

the CSW untranslation routine, <strong>and</strong> module H<strong>CP</strong>DGD to<br />

determine why this occurred.<br />

DGD002<br />

Explanation: (soft abend) The number of active I/O<br />

requests (<strong>VM</strong>DIOACT) exceeded the number of defined<br />

devices (<strong>VM</strong>DDEVCT), or <strong>VM</strong>DIOACT was not a<br />

positive number while I/O was active.<br />

<strong>System</strong> operation continues.<br />

User Response: Examine the VDEV blocks for the<br />

virtual machine to determine how many requests were<br />

active at the time of the dump. Examine the system<br />

trace table to determine when the active requests were<br />

started, <strong>and</strong> what requests became inactive during this<br />

interval. Analyze the modules that incremented <strong>and</strong>/or<br />

decremented the <strong>VM</strong>DIOACT count. If the modules that<br />

update the field <strong>VM</strong>DIOACT contain correct logic, try to<br />

determine how the data in the field was destroyed.<br />

DGG001<br />

Explanation: When the device simulator was invoked<br />

using the virtual channel simulator, the device simulator<br />

signaled that it could not simulate a CCW.<br />

User Response: Examine the device simulation<br />

module to determine why it did not simulate the<br />

comm<strong>and</strong>. R6 points to the VDEV block that contains<br />

the address of the simulation routine in the field<br />

VDEVSIMA. R10 points to the IORBK that contains the<br />

guest absolute address of the problem CCW in the field<br />

IOR<strong>CP</strong>A.<br />

DGG002<br />

Explanation: Module H<strong>CP</strong>DGG received an indication<br />

from the untranslation routine that the host channel<br />

program ended on a CCW corresponding to a guest<br />

CCW with the “suspend” flag validly set. The “suspend”<br />

flag can never be validly on in a channel program<br />

initiated by a DIAGNOSE code x’A8’ request.<br />

User Response: Examine the guest channel program,<br />

the host channel program, the CCW translation routines,<br />

the CSW untranslation routine, <strong>and</strong> module H<strong>CP</strong>DGG to

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

Saved successfully!

Ooh no, something went wrong!