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

HCP6737E HCP6740E
HCP6737E Cannot find logo configuration file fn ft.
Explanation: You issued a CP REFRESH LOGOINFO
command, and the file you specified does not exist on
any disk that CP has accessed.
System Action: CP ignores the command; system
operation continues.
User Response: You can issue the CP QUERY
CPDISK command to see what minidisks CP has
accessed, and the CPLISTFILE command to list the
files on those minidisks. To refresh the logo
configuration information, place a logo configuration file
on a CP-accessed minidisk and reissue the CP
REFRESH LOGOINFO command with the name and
type of that file, or reissue the CP REFRESH
LOGOINFO command with the name and type of an
existing logo configuration file.
HCP6738A XLINK systems were specified and
system was in neither the XLINK
system inclusion nor the exclusion list.
Failure to correct this error may lead to
loss of user data.
To ignore the error and continue
normally, enter GO.
To continue with the IPL without
autologging any users, enter
NOAUTOLOG.
To abort the IPL, enter STOP.
Explanation: You used XLINK_SYSTEM_INCLUDE or
XLINK_SYSTEM_EXCLUDE statements in the system
configuration file, or the CSESYS macro in HCPSYS, to
generate lists of systems to be included in or excluded
from cross system link functions, and the system being
IPLed was not on either list. This error may result in
problems with the integrity of your system’s minidisk
data.
System Action: CP will prompt the system operator to
choose one of the following options:
v Ignore the error and continue the IPL normally.
v Continue the IPL process, but do not autolog the
seven special user IDs (two for EREP, two for
accounting, two for symptom records, and one for
start up).
v Abort the IPL process.
User Response: Choose one of the options that CP
gives you, edit the system configuration file or the
CSESYS macro, and re-IPL.
394 z/VM: System Messages and Codes — CP
HCP6739E fn MODULE not found
Explanation: When the system was IPLed, CP was
loaded from a module. Now, either it is trying to recover
automatically after a hard abend, or you entered the
SHUTDOWN command with the REIPL option, and the
system cannot find the module to reload CP.
If using the Stand-Alone Program Loader (SAPL), either
the default CPLOAD MODULE or the module name
specified with the SALIPL utility was not found.
System Action: If you received this message because
of a system bounce, the system loads a disabled wait
matching the message number. If you received it
because of a SHUTDOWN REIPL command, CP
ignores the command and system operation continues.
If using SAPL and the system enters a disabled wait
state (wait state code = 6739), the registers will contain
the following information:
R0 IPL device address (low order 2 bytes)
R1 IPL subchannel ID
R2 Offset cylinder/block
R3 Extent number
R4-R5 Name of module to load
R12 Base register
R13 Work page address.
User Response: Correct the SHUTDOWN command
or IPL the system.
If using SAPL, either place the CPLOAD MODULE on
the minidisk to be used by SAPL or specify the correct
module name on the SAPL menu screen. See the
section, “Overriding Stand-Alone Program Defaults” in
the z/VM: CP Planning and Administration.
HCP6740E Insufficient storage to complete this
request
Explanation: One of the following occurred:
v You entered a CP SET TRACEFRAMES command
that tried to allocate more storage for trace frames
than is currently available.
v CP tried to load files as directed by CPXLOAD, but
could not find sufficient contiguous free central
storage to contain the loaded files.
System Action: System operation continues.
For CP SET TRACEFRAMES-
CP ignores the command.
For CPXLOAD-
CP rejects the request.
User Response:
For CP SET TRACEFRAMES-
You can use the CP QUERY FRAMES
command to see how much storage is
available for trace frames, and then enter a
new CP SET TRACEFRAMES command.