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

TSE001 TSH001
HCPTSD should be changed to recognize the return
code.
TSE001
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.
TSE002
Explanation: (soft abend) HCPTSEND called
HCPSDFCL to close a system trace file for CP tracing.
However, the originator of the file is not the VMDBK that
is currently running.
User Response: Both the originator of the file and the
current VMDBK should be the system VMDBK. Register
11 addresses the current VMDBK. The snap data
parameter list contains the TSDBK that describes the
DASA-related information for this invocation of TRSAVE.
The field TSDORIG contains the originator of the file
and should have the value ″SYSTEM″. The snap data
parameter list also contains the SDFBK, which
describes the system trace file that CP was attempting
to close. The field SDFORIG contains the originator of
the file and should have the value ″SYSTEM″. Examine
the VMDBK, TSDBK and SDFBK and determine
whether the contents of those control blocks are valid.
TSE004
Explanation: (soft abend) HCPTSEND called
HCPSDFCH to change the class of the system trace file
for CP tracing. However, HCPSDFCH issued a return
code indicating an error as found in input.
User Response: R15 contains the return code. A
return code of 16 indicates a parameter error. Possible
causes are an incorrect type in SDFTYPE, an incorrect
spool ID in SDFIDNUM, or an incorrect class in
SDFCLASS. The snap data parameter list contains the
SDFBK of the system trace file in error. A return code of
24 indicates the file not found. The snap data parameter
list also contains the TSDBK that describes the DASD
related information for this invocation of TRSAVE.
Examine the TSDBK and SDFBK and determine
whether the contents of those control blocks are valid. If
they are not, the code in HCPTSW and HCPTSE that
maintains and uses the addresses of the SDFBK’s for
the files associated with this trace may be in error.
110 z/VM: System Messages and Codes — CP
TSE005
Explanation: (soft abend) HCPTSE picked up 0 as the
address of the SDFBK describing an open system trace
file for CP tracing.
User Response: TSDSDFP is an array of addresses
of SDFBKs. TSDSDFPI is the index in TSDSDFP of the
SDFBK currently in use. For example, if TSDSDFPI is
2, the second address in TSDSDFP should contain the
address of the SDFBK describing the system trace file
currently being written to. Examine the values of
TSDSDFP and TSDSDFPI. The code in HCPTSW and
HCPTSE that maintains and uses the addresses of the
SDFBKs for the files associated with this trace may be
in error.
TSF001
Explanation: (soft abend) HCPTSF called HCPLCKAX
to acquire the TSDWRTLK lock. HCPLCKAX reported
that the TSDWRTLK lock was already destroyed (R15 =
12).
User Response: Examine the TSDBK and determine
if it is valid, or determine how the TSDWRTLK could
have been destroyed already.
TSF099
Explanation: (soft abend) HCPTSF called an entry
point and the entry point, returned a return code that
HCPTSF did not recognize.
User Response: Determine if the return code is a
valid one to be returned from the entry point or whether
HCPTSF should be changed to recognize the return
code.
TSG001
Explanation: (soft abend) HCPTSG was called at
system reset or at logoff to close any TRFILES that a
virtual machine may have opened for reading. However,
it received a bad return code from HCPSDFCL.
User Response: R15 contains the return code. Return
code 16 indicates HCPSDFCL found an error in the
SDFBK addressed by Register 1. Return code 24
indicates HCPSDFCL describes the file as empty.
However, since this file was opened for reading, it
should not have been empty. If the SDFBK appears to
be incorrect for either return code, examine the code in
HCPTSO, HCPTSN, and HCPTSX which sets the fields
in the TDRBK and maintains the TDRBK chain.
TSH001
Explanation: (soft abend) HCPTSH called
HCPBMSBP, which reported that it was passed an
incorrect parameter (R15 = 8).
User Response: Determine why HCPBMSBP reported