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

HCQ044I HCQ050E
HCQ044I WARNING: Start time precedes oldest
trace entry for cpuno
Explanation: An inconsistency may exist in the TOD
data in the trace table.
System Action: Processing continues.
User Response: None.
HCQ045W WARNING: Trace table end reached for
cpuno
Explanation: When processing merged output, the
end of the trace table indicated was found.
System Action: Processing continues with data for
the other CPUs.
User Response: Be aware that further data from the
indicated CPU is not in the dump.
HCQ046I Trace end or ″TO″ address reached
Explanation: The TRACE subcommand has reached
the point in processing the trace request that it has
satisfied all the requirements specified.
System Action: None.
User Response: None.
HCQ047E Trace table for cpuno could not be
found
Explanation: The VM Dump Tool could not locate a
value for control register 12 for the indicated processor
in either the DFIR or the Prefix Page, so it cannot locate
the trace table for the indicated processor.
System Action: The subcommand terminates.
User Response: If you can find the address of a trace
entry by other means, use the FROM nnnn option to
format the desired trace information.
While not guaranteed to always work, one approach to
find such a trace entry is to locate the label PFXCPCRC
in the prefix page for the indicated processor. This field
should contain the address of the last trace page to be
filled. Display the trailer information of this page
(described by the TTPBK), find the chain pointer to the
next page, and search time stamps of the trace entries
in that trace page for when the time stamp gets lower in
value. The trace entry with the highest time stamp is the
most recent.
HCQ047W Trace table for cpuno could not be
found
Explanation: The VM Dump Tool could not locate a
value for control register 12 in either the DFIR or the
Prefix Page, therefore it cannot locate the trace table for
the indicated processor. This problem was encountered
476 z/VM: System Messages and Codes — CP
during processing of a TRACE subcommand with the
MERGE option.
System Action: Processing continues.
User Response: If you can find the address of a trace
entry by other means, use the FROM nnnn option to
format the desired trace information.
While not guaranteed to always work, one approach to
find such a trace entry is to locate the label PFXCPCRC
in the prefix page for the indicated processor. This field
should contain the address of the last trace page to be
filled.
Display the trailer information of this page (described by
the TTPBK), find the chain pointer to the next page, and
search time stamps of the trace entries in that trace
page for when the time stamp gets lower in value. The
trace entry with the highest time stamp is the most
recent.
HCQ048E VMDBK is for SYSTEM or SYSTEMMP,
use IUCVBK address
Explanation: The input to the MAPIUCV macro was
found to be the address of the VMDBK for SYSTEM or
SYSTEMMP. Because these VMDBKs are the logical
owner of may different IUCV services, the IUCVBK for
the specific service of interest must be specified.
System Action: The macro terminates.
User Response: Find the IUCVBK for the desired
service and enter the macro again. To determine the
IUCVBK address for the system services, use
MAPIUCV *ALL.
HCQ049E Path number is larger than the current
max of maxnum
Explanation: The path number indicated to the
MAPIUCV macro was found to be larger than the
maximum number of paths allowed for by the tables in
the dump.
System Action: The macro terminates.
User Response: Use a path number no higher than
the maximum value indicated.
HCQ050E Code table overflow
Explanation: There is a fixed-size table in the VM
Dump Tool to contain the trace entry codes for all the
types of required trace entries. The subcommand
entered is too complicated for this table to contain all
the code values needed.
System Action: The subcommand or macro
terminates.
User Response: Enter the subcommand again using
fewer parameters after the TYPE operand.