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

Note: This message will be reissued as many times as
necessary to show all paths and devices affected
by the request. In most cases, it will only be
issued once per path, but if there is a list of more
than eight rdevs affected on the same path, the
message can be issued multiple times per path.
HCP6402I Quiesce request failed because {of a
vary processing failure on path yy|an
error was detected in the request for
path yy|path yy is the last path} to
[online] device(s) {rdev|rdev rdev..}
Explanation: Referring to the displayed message text,
the attempt to quiesce the path or paths failed for one
of these reasons:
v The specified path is reserved.
v A vary command processing failure occurred during
the quiesce request.
v An error was detected in the quiesce request.
v The specified path is the last path available to the
online devices. Quiesce processing does not have
the ability to remove all contact with an online device.
To quiesce the last path available to a device, the
operator must either vary the last path to the device,
or the device itself, offline.
Quiescing paths varies the paths offline (if not already
offline). They cannot be varied online and are
unavailable for use while a service action is being
performed.
The variable definitions are:
yy The channel path ID of the path that failed the
quiesce request
rdev The real device number of a device attached to
the path that caused the quiesce to fail.
System Action: Processing for the quiesce request is
terminated, but system operation continues.
Operator Response: Your action depends on the
nature of the failure. In the case of:
The specified path being reserved:
To satisfy the request, you could cancel any
task that may have the path reserved, or wait
for those tasks to complete.
A vary command processing failure during the
quiesce request:
If the vary command processor failed, the
service representative should retry the request.
If it fails again, notify the system programmer
or the IBM Support Center.
An error detected in the quiesce request:
The service representative should retry the
request. If it fails again, notify the system
programmer or the IBM Support Center.
HCP6402I HCP6403I
The problem might persist until the next IPL.
The specified path being the last path available to
the online device:
Vary another path online to the devices, vary
the last path offline to the devices, or vary the
devices offline.
If the problem is resolved, the request may be
reinitialized or resubmitted by the service representative.
Note: This message will be reissued as many times as
necessary to show all paths and devices affected
by the request. In most cases, it will only be
issued once per path, but if there is a list of more
than eight rdevs affected on the same path, then
the message can be issued multiple times per
path.
HCP6403I Quiesce request failed because guest
userid {did not respond|issued an
unsuccessful response} for path yy to
device {rdev|rdev rdev..}
Explanation: Attempt to quiesce the paths failed
because one or more guests either:
v Did not respond to a quiesce request within the
allotted time.
v Issued a failing response code to a quiesce request.
Quiescing paths varies the paths offline (if not already
offline). They cannot be varied online and are
unavailable for use while a service action is being
performed. The variable definitions are:
userid The user ID of the guest that failed the quiesce
request
yy The channel path ID of the path that failed the
quiesce request
rdev The real device number of a device attached to
the path that caused the quiesce to fail.
System Action: Processing for the quiesce request is
terminated, but system operation continues.
Operator Response: Your action depends on the
nature of the failure. In the case of:
One or more guests not responding to a quiesce
request within the allotted time:
If I/O timed out during path validation, it could
be a hardware error, or a guest does not
support quiesce/resume requests.
One or more guests issuing a failing response code
to a quiesce request:
Contact the guest system operator for more
information.
After the problem is resolved, the request may be
re-submitted by the service representative.
Chapter 3. System Messages 375