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

an incorrect parameter, and report the entry point which
is interfacing incorrectly.
TSH002
Explanation: (soft abend) The originator of the trace,
either by default or specified as the ″FOR″ user, must
be logged on. HCPTSHDI requires the caller to ensure
that the user is logged on.
User Response: Examine the TSDBK and determine
if it is valid or determine how the originator got logged
off while a trace was still active for it.
TSH003
Explanation: (soft abend) HCPTSH called
HCPSDFCL or HCPSDFCH while dispatched on a user
ID other than the originator.
User Response: Examine the TSDBK and determine
if it is valid or determine why HCPTSH did not switch
itself to be dispatched on the originator’s user ID.
TSH004
Explanation: (soft abend) HCPTSH called
HCPSDFCH, which reported that the file was empty and
that it became closed. If the file became closed because
it was empty, it should have been purged when
HCPTSH called HCPSDFCL.
User Response: Examine the TSDBK and determine
if it is valid or determine how all records in the SDF
were deleted after it was closed.
TSH005
Explanation: (soft abend) HCPTSH detected HCPTSR
reported an abend situation. HCPTSR detected that the
TSDRECLK was already locked by the processing unit
that HCPTSR is dispatched on. HCPTSR did not issue
an abend at the time of the error because the
environment under which it was running did not allow a
soft abend to be issued.
User Response: Determine how the lock was left
locked by the CPUID.
TSH006
Explanation: (soft abend) HCPTSH determined that
HCPTSR previously received a return code (R15 = 8)
from HCPBMSBP indicating that HCPTSR returned too
many buffers. HCPTSR did not issue an abend at the
time of the error because the environment under which
it was running did not allow a soft abend to be issued.
User Response: Determine how HCPTSR could have
put more buffers on the pending buffer queue than it got
using HCPBMSGA.
TSH007
Explanation: (soft abend) HCPTSH determined that
HCPTSR previously received an incorrect TRCTYPE
value within a TRCBK. HCPTSR did not issue an abend
at the time of the error because the environment under
which it was running did not allow a soft abend to be
issued.
User Response: Determine if the TRCBK is valid, or
how the TRCTYPE field was destroyed.
TSH008
Explanation: (soft abend) HCPTSH determined that
HCPTSR previously received an incorrect return code
from a module which HCPTSR called. HCPTSR did not
issue an abend at the time of the error because the
environment under which it was running did not allow a
soft abend to be issued.
User Response: Determine if the return code is a
valid one to be recognized from the entry point, or
whether HCPTSH should be changed to recognize the
return code. See the TSDTDRRC and TSDTDREP
fields for more information about which entry point
HCPTSH received the unexpected return code from.
TSH009
Explanation: (soft abend) The TSDTSRCD contained
an incorrect code.
User Response: Determine if the TSDBK is valid, or
why the TSDTSRCD field contains the incorrect code.
TSH010
Explanation: (soft abend) HCPTSH was about to call
HCPLCKAX to destroy the TSDWRTLK, and
HCPCLKAX returned a lock destroyed (R15 = 12).
HCPTSH expects the lock to exist until it is dropped.
User Response: Examine the HCPTSDBK to
determine if it is valid or not, or determine how the lock
could have been destroyed before the trace ID was
dropped.
TSH011
TSH002 TSH011
Explanation: (soft abend) HCPTSHDI 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.
Chapter 2. System Codes 111