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

v No VSMs matching pattern userid_pattern logged
on.
v VSM userid not logged on.
Explanation: You issued a CP REFRESH LOGOVSM
command to change the logo configuration information
for terminals logged on through one or more VTAM
service machines (VSMs), and the VSMs you specified
are not logged on to the system.
System Action: CP ignores the command; system
operation continues.
User Response: Issue a CP QUERY NAMES
command to find out which VTAM service machines are
logged on to your system. Then enter another CP
REFRESH LOGOVSM command.
HCP6785E Unable to identify device rdev
dynamically.
Explanation: You issued a CP VARY ONLINE
command, and one of two things is wrong:
v You specified a device whose class or type has not
been set, and which does not respond with enough
information to enable CP to determine its class and
type.
v You specified a device that is not powered on.
System Action: CP rejects the CP VARY ONLINE
command; system operation continues.
User Response: You can define the device to CP in
one of three ways:
v Using the CP SET RDEVICE command,
v Adding an RDEVICE statement to the system
configuration file (SYSTEM CONFIG), or
v Adding an RDEVICE entry to the real I/O
configuration file (HCPRIO ASSEMBLE).
HCP6786E system cannot be resolved because
system ID is undefined -- logo
configuration file cannot be read.
Explanation: The LOGO_CONFIG statement in the
system configuration file contains a statement of the
form, system filetype. The system acts as a variable
and takes the value of the system name. Unfortunately,
the SYSTEM_IDENTIFIER statement or the
SYSTEM_IDENTIFIER_DEFAULT statement or both
were not defined in the system configuration file or on
the SYSID macro in HCPSYS. Therefore, the system
variable is undefined.
System Action: System operation continues, but CP
does not read the logo configuration file. Subsequently,
all of the logo definitions come from HCPBOX.
User Response: Define a system identifier in the
system configuration file and re-IPL the system so it can
take effect.
HCP6787E The variations of this message are
explained below.
MESSAGES:
v No VSMs support dynamic logo updates.
v No VSMs matching pattern userid_pattern support
dynamic logo updates.
v VSM userid does not support dynamic logo
updates.
Explanation: A CP REFRESH LOGOVSM command
was issued to change the logo configuration information
for terminals logged on through one or more VTAM
service machines (VSMs). The VSMs specified do not
support dynamic logo updates.
System Action: CP ignores the command. System
operation continues.
User Response: Determine which logged on VTAM
service machines support dynamic logo updates. Then
enter another CP REFRESH LOGOVSM command.
HCP6789E The variations of this message are
explained below.
MESSAGES:
v Diagnose code diag is already defined
v Requested CP Exit number exit is already defined
Explanation: CP rejected the request to define a new
DIAGNOSE code or CP Exit because the DIAGNOSE
code or CP Exit number you chose is the number of an
existing DIAGNOSE code or CP Exit.
System Action: CP rejects the command; system
operation continues.
User Response: If you want to define a new
DIAGNOSE code or CP Exit, enter the DEFINE
DIAGNOSE or DEFINE EXIT command again and
specify a DIAGNOSE code or CP Exit number that does
not currently exist on your system. If you want to
override an existing DIAGNOSE code or CP Exit, use
the MODIFY DIAGNOSE or MODIFY EXIT command
instead of the DEFINE command.
HCP6790I command processing halted. The next
{device|location} that would have been
processed is {rdev|address}.
Explanation: You issued a CPHX command to stop
one of the following commands:
v CP ATTACH
v CP LOCATE CPREAL
v CP LOCATEVM
HCP6785E HCP6790I
v CP VARY ONLINE|OFFLINE (only for devices)
System Action: CP has halted execution of the
command and sends you a version of this message to
tell you how much of the command it completed.
System operation continues.
Chapter 3. System Messages 401