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

HCP296E
few minutes and retry the operation. If the error
persists, contact the appropriate hardware service
personnel.
v the control unit had insufficient message buffer
space.
Explanation: Space in the message buffer cannot be
made available.
System Action: The command is rejected.
Operator Response: Contact the appropriate
hardware service personnel.
v pinned tracks are not identifiable, code = code.
Explanation: A request to “Read Pinned Tracks” has
failed. The pinned tracks are not identifiable because
their location and data are in failed nonvolatile
storage, as opposed to the cache.
The code is the format code in sense byte 8 that
describes the error condition:
Code Reason
X'2D' A request to “Read Pinned Tracks” with the
cache storage available or pending, but data
for the device, which is in “Data in Failed
NVS” status, is not in the cache storage.
System Action: The command is rejected.
Operator Response: Contact the appropriate
hardware service personnel.
v the device is undergoing media maintenance,
code = code.
Explanation: The command entered cannot be
accepted because the device is in media
maintenance mode.
The code is the format code in sense byte 8 that
describes the error condition:
Code Reason
X'3E' A READ or WRITE command without device
support or diagnostic authorization was
received on a device that is in track
emulation transition.
X'41' A command chain operating with normal
authorization was received on a device that
is in media maintenance mode.
X'42' A media maintenance Query order was
received for a device in media maintenance
reserve or track emulation transition state.
System Action: The command is rejected.
Operator Response: Contact the appropriate
hardware service personnel.
v duplex pair could not be established, code =
code.
Explanation: The Establish Duplex Pair command
has failed for one of several reasons. The code is the
160 z/VM: System Messages and Codes — CP
hexadecimal format code in sense byte 8 that
describes the error condition:
Code Reason
X'0F' Space is not available in the non-volatile
storage for the “out-of-sync” cylinder bit
map.
X'10' The addressed device is not failed duplex
(resynchronization of the entire volume
failed).
X'11' The devices were not in failed duplex
(resynchronization of the out-of-sync
cylinders logged by the storage director has
failed).
X'12' The devices were not simplex.
X'13' The secondary/alternate device was busy,
reserved to another path-group, participating
in a Concurrent Copy (CONCOPY) session,
or a response message was owed for the
device.
X'14' The device specified in byte 3 is not simplex
or the secondary of the duplex pair.
X'15' Volume has pinned data.
X'17' The established path-groups on the
secondary or alternate are not the same as
the primary. See z/VM: System Operation for
information about ungrouping storage paths.
X'21' Caching is active for any of the specified
simplex devices.
X'26' The two devices do not have the same
geometry.
System Action: The command is rejected.
Operator Response: If code is 13, and the device is
not reserved to another path-group, retry the
command. In all other cases, contact a system
operator or the appropriate hardware service
personnel.
v a duplex state error occurred, code = code.
Explanation: The state of a duplex pair is not valid
for the given command. The code is the hexadecimal
format code in sense byte 8 that describes the error
condition:
Code Reason
X'16' Address specified as the secondary of an
existing duplex pair, failed duplex, or duplex
pending is not correct.
X'18' An operation is attempted to a duplex pair
with direct I/O to one device of the duplex
pair, and the access is not one of the
following:
– To a diagnostic track