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

TSZ001 UDR001
TSZ001
Explanation: (soft abend) HCPTSZ called an
HCPLCK entry point to get a lock, and the entry point
returned information that the lock is destroyed (R15 =
12). HCPTSZ does not expect the lock to be destroyed.
User Response: Determine which instance of the call
to HCPLCKAS or HCPLCKAX returned the unexpected
return code. Then determine if the entry points are
interfacing correctly, or determine how the lock was
destroyed.
TSZ002
Explanation: (soft abend) HCPTSZ determined that
the VMDBK it was trying to get dispatched was not
logged on. HCPTSZ does not expect the virtual
machine to be able to log off before the trace ID has
been disabled.
User Response: Determine which instance of the call
to HCPDSPSW returned the unexpected return code.
Then determine if the entry points are interfacing
correctly, or determine how the user logged off while the
trace was enabled.
TSZ003
Explanation: (soft abend) HCPTSZDI was passed an
origin ID to use in searching for a TSDBK in the TSDBK
chain. Unexpectedly, no TSDBK with a matching origin
ID was found.
User Response: Determine if the caller passed a bad
origin ID, or if the TSDBK chain has been corrupted.
TSZ098
Explanation: (soft abend) HCPTSZ called an entry
point, and the entry point returned a condition code that
HCPTSZ did not recognize.
User Response: Determine which instance of a call
returned the unexpected condition code. Then
determine if the condition code is a valid one to be
recognized from the called entry point, or whether
HCPTSZ should be changed to recognize the condition
code.
TSZ099
Explanation: (soft abend) HCPTSZ called an entry
point, and the entry point returned a return code that
HCPTSZ did not recognize.
User Response: Determine which instance of a call
returned the unexpected return code. Then determine if
the return code is a valid one to be recognized from the
called entry point, or whether HCPTSZ should be
changed to recognize the return code.
116 z/VM: System Messages and Codes — CP
TXE001
Explanation: An SVC 28 or SVC 32 interrupt occurred
at a location in the CP nucleus for which there is not an
enabled data trace.
User Response: Registers 2 and 3 contain the SVC
old PSW of the interrupt. R4 contains the interrupt code.
The registers at the time of the interrupt are saved in
the SSADTR of the abending processor. Examine the
PSW in registers 2 and 3 to determine why the SVC call
was made. SVC 28 is allowed only at trace points that
are defined and enabled through the TRSOURCE
command. SVC 32 is the data trace mechanism for
returning control to the interrupted trace point.
TXE002
Explanation: A dynamic exit was invoked at a point
where no dynamic exit is defined.
User Response: Contact your IBM support personnel.
TXW001
Explanation: (soft abend) HCPTSEND called
HCPBMSTM to return all buffers to the system, but
some of the allocated buffers are not on either the
pending queue or the available stack.
User Response: Before trace service termination is
invoked, HCPTSM should have ensured that all
allocated buffers were returned to either the pending
queue or the available stack. R8 should contain the
BMSBK address. Check the buffer counts and review
the HCPTSM code associated with returning buffers to
determine why the buffers were lost.
UDP001
Explanation: (soft abend) Module HCPUDP detected
that the in-storage portion of the CP object directory has
been corrupted or that a control block read from the CP
object directory is not valid.
User Response: R7 identifies the location within
HCPUDP where the error was detected. Determine
which portion of the object directory HCPUDP found to
be not valid and why. DDR can be used to examine the
object directory on DASD.
There could be a mismatch between the service levels
of the directory write and read routines. Ensure that the
DIRECTXA module is at the same service level as the
CP nucleus. Then issue the DIRECTXA command to
create a new object directory.
UDR001
Explanation: (soft abend) Module HCPUDR detected
that it did not read a valid HCPDUNDX, HCPDVMD, or
HCPDDEV from the CP directory. If the directory page
that was read appears to be correct, it is likely that the