28.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

– To a duplex pair that is failed duplex<br />

– To a duplex (not failed duplex or duplex<br />

pending) with diagnostic or device<br />

support access authorization.<br />

X'19' An attempt was made to enter a ‘fail duplex<br />

pair’ PSF order to a volume that is failed<br />

duplex.<br />

X'1A' An attempt was made to read the output of<br />

a sync cylinder map from a device that is<br />

not a member of a duplex pair.<br />

X'1B' An attempt was made to enter a ‘terminate<br />

duplex pair,’ ‘fail duplex pair,’ or ‘direct I/O to<br />

one device of the duplex pair’ PSF order to<br />

a volume that is simplex.<br />

X'1C' An attempt was made to fail a duplex pair<br />

with the primary as the ‘failed’ device while<br />

the duplex pair is duplex pending.<br />

X'23' An attempt was made to terminate a duplex<br />

pair, <strong>and</strong> the duplex pair is DASD Fast Write<br />

pending.<br />

X'24' An attempt was made to direct I/O to one<br />

device of the duplex pair that is duplex<br />

pending.<br />

X'27' An attempt was made to write a home<br />

address or record zero on an active duplex<br />

volume.<br />

X'31' An attempt was made to direct I/O to one<br />

device of the duplex pair where the state of<br />

the duplex pair has been verified, <strong>and</strong> the<br />

state is not as expected.<br />

X'3D' A Media Maintenance Reserve was received<br />

on the primary address of a duplex pair <strong>and</strong><br />

was not preceded by a direct I/O to one<br />

device of the duplex pair, or a 3380 Track<br />

Compatibility Mode Control was received on<br />

a device that is the primary address of a<br />

duplex pair.<br />

X'40' A Media Maintenance Reserve was received<br />

on the primary address of a duplex pair that<br />

was not failed duplex.<br />

<strong>System</strong> Action: The comm<strong>and</strong> is rejected.<br />

Operator Response: Contact a system operator or<br />

the appropriate hardware service personnel.<br />

v an unexpected condition occurred while<br />

terminating a CONCOPY session, code = code.<br />

Explanation: An attempt to end a Concurrent Copy<br />

(CONCOPY) session has failed. The code is the<br />

hexadecimal format code in sense byte 8 that<br />

describes the error condition:<br />

Code Reason<br />

X'48' The device is not part of the CONCOPY<br />

session being terminated.<br />

<strong>System</strong> Action: The comm<strong>and</strong> is rejected.<br />

Operator Response: None.<br />

v an unexpected condition occurred while<br />

executing a FLASHCOPY comm<strong>and</strong>, code = code.<br />

Explanation: An attempt to execute a FLASHCOPY<br />

comm<strong>and</strong> has failed. The code is the hexadecimal<br />

format code in sense byte 8 that describes the error<br />

condition:<br />

Code Reason<br />

X'37' A comm<strong>and</strong> was received while the<br />

subsystem was attempting to install a new<br />

microcode load.<br />

X'56' The source or the target volume has pinned<br />

data.<br />

X'61' Discard not allowed to a volume with the<br />

specified extents overlapping a FlashCopy<br />

or Concurrent Copy operation.<br />

X'82' One of the following conditions must be<br />

corrected:<br />

– The resources required to complete this<br />

comm<strong>and</strong> are not available in the control<br />

unit.<br />

– The number of Flash Copy relationships<br />

exceeds the maximum allowed.<br />

– The target device is not available.<br />

X'83' The battery feature must be installed <strong>and</strong><br />

operational for this comm<strong>and</strong> to be used.<br />

X'84' One of the following conditions must be<br />

corrected:<br />

– The volumes specified are not the same<br />

track type.<br />

– The target volume has fewer tracks than<br />

the source volume.<br />

– The source <strong>and</strong> target must be in the<br />

same logical subsystem on some early<br />

models of DASD supporting FlashCopy.<br />

– The number of target extents must equal<br />

the number of source extents.<br />

X'85' The specified target volume is a<br />

Peer-to-Peer Remote Copy primary or<br />

secondary volume.<br />

H<strong>CP</strong>296E<br />

X'9C' Cannot complete due to internal hardware<br />

conditions or lack of resources to manage<br />

the relationship.<br />

X'9D' The number of FlashCopy relations exceeds<br />

the maximum allowed.<br />

X'A5' The FlashCopy operation is only valid for full<br />

volumes <strong>and</strong> does not allow specification of<br />

extents on early models of DASD supporting<br />

FlashCopy.<br />

X'A6' The number of FlashCopy target relations<br />

exceeds the maximum allowed for one or<br />

more of the source tracks.<br />

Chapter 3. <strong>System</strong> <strong>Messages</strong> 161

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!