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

TKM001
Explanation: (hard abend) An invalid event code was
passed to HCPTKMDX in R2. The event code must be
one of the codes defined for TSKEVENT in the TSKBK.
User Response: Examine the CP trace table and
storage dump to determine what module did the GOTO
to HCPTKMDX. R2 contains the invalid event code.
TKM002
Explanation: (hard abend) A module made a
reference to an address space in access-register mode
using an i-ASIT which has expired, and chose not to
handle this situation in an exit routine.
User Response: Examine the CP trace table and
storage dump to determine what module made the
reference.
TKM003
Explanation: A module made a reference to an
address space using an invalid virtual address, and
chose not to handle this situation in an exit routine.
User Response: Examine the CP trace table and
storage dump to determine what module made the
reference.
TKM004
Explanation: A module made a reference to an
address in an address space which has been damaged
because of a paging or storage error, and chose not to
handle this situation in an exit routine.
User Response: Examine the CP trace table and
storage dump to determine what module made the
reference.
TKM005
Explanation: A task has resumed execution
dispatched on a different VMDBK than was dispatched
when the task was suspended.
User Response: Examine the CP trace table and
storage dump to determine what processing occurred
between the time the task was suspended (call to
HCPTKMSU) and the time the task was resumed (call
to HCPTKMRS). R9 points to the TSKBK. TSKRNUSR
contains the VMDBK dispatched at the time the task
was suspended. R0 points to the PFXPG. PFXRNUSR
contains the VMDBK dispatched at the time the task
was resumed.
TKM006
Explanation: The deferred work counter has been
mismanaged. It would have become negative if
decremented.
User Response: Examine the CP trace table and
storage dump to determine which module(s) most
recently changed the deferred work counter. The
deferred work counter was decremented once more
than it should have been. Check to see if processing
decremented it twice or if it was decremented without
having first been incremented. R11 points to the
VMDBK. VMDDFRWK is the deferred work counter.
TKM007
Explanation: HCPTKMDX was called to drive an
exception-handling exit established by an HCPSPIE or
HCPSAC macro. The routine in which the exception
occurred was running in 64-bit addressing mode.
However, the TSKBK containing the state at the time of
the exception did not include 64-bit register contents; it
was not marked “long-reg.”
This is probably an error in either the caller of
HCPTKMDX (passing an improper TSKBK) or in the
first level exception handler that filled in the TSKBK
(HCPPRGIN for program interruptions).
User Response: Examine the TSKBK passed to
HCPTKMDX in R1. Determine whether it is well-formed,
and whether TSKGPSW, including the
extended-addressing mode bit, is correct. If so,
determine which module was responsible for setting
TSKLONGR (based on the value of TSKEVENT) and
why it was not set.
TMR080
Explanation: (soft abend) The interval timer residue
counter has a negative value.
User Response: Look at the modules that manipulate
the field VMDHIRES to determine why the residue
counter has a negative value. The fields in the TRQBK
at entry to HCPTMR are used to update VMDHIRES;
they may be incorrect.
TPY010
Explanation: An incorrect PER trap code was
received.
User Response: Contact your IBM support personnel.
TRD007
TKM001 TRD007
Explanation: The module that issues this abend is
distributed as object code only; therefore, no source
program materials are available.
User Response: Refer to z/VM: Diagnosis Guide for
Chapter 2. System Codes 107