Hitachi Business Continuity Manager Messages

Hitachi Business Continuity Manager
Messages
Document Organization
Product Version
Getting Help
Contents
MK-94RD262-23
2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying and recording, or stored in a database or retrieval
system for any purpose without the express written permission of Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and
assumes no responsibility for its use. This document contains the most current information available
at the time of publication. When new or revised information becomes available, this entire
document will be updated and distributed to all registered users.
Some of the features described in this document might not be currently available. Refer to the most
recent product announcement for information about feature and product availability, or contact
Hitachi Data Systems Corporation at https://portal.hds.com
Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of
the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is
governed by the terms of your agreements with Hitachi Data Systems Corporation.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi
Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and
other countries.
Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,
Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are
registered trademarks of Hitachi Data Systems.
AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,
FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA,
z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International
Business Machines Corporation.
All other trademarks, service marks, and company names in this document or web site are
properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
Notice on Export Controls. The technical data and technology inherent in this Document may be
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to
obtain licenses to export, re-export, or import the Document and any Compliant Products.
ii
Hitachi Business Continuity Manager Messages
Contents
Preface...................................................................................................v
Intended audience.................................................................................................... vi
Product version......................................................................................................... vi
Release notes........................................................................................................... vi
Document revision level.............................................................................................vi
Document organization............................................................................................. vii
Related documents.................................................................................................. viii
Document conventions.............................................................................................. ix
Conventions for storage capacity values...................................................................... x
Accessing product documentation...............................................................................xi
Getting help..............................................................................................................xi
Comments................................................................................................................ xi
1 Messages............................................................................................. 1-1
Message format...................................................................................................... 1-2

Message output format..................................................................................... 1-2
Notations used to describe messages.................................................................1-3
Message output destination...............................................................................1-3
List of Messages..................................................................................................... 1-4
Message Details................................................................................................1-4
Multi-line messages output to SYSTSPRT starting from YK............................... 1-161
Identifying the volume to be processed.......................................................... 1-166
Identifying the volume serial number from the REXX script..................... 1-166
Identifying the volume serial number from the configuration file............. 1-166
User completion codes.........................................................................................1-166
2 Storage system sense byte information.................................................. 2-1

Details of error codes.............................................................................................. 2-2
Acronyms and Abbreviations

Index
iii
iv
Preface
This document describes the messages and error codes that are output by
the following program products. In this manual, these products are
collectively referred to as Business Continuity Manager:
- Hitachi Business Continuity Manager Basic
- Hitachi Business Continuity Manager UR 4x4 Extended CTG
This preface includes the following information:
Intended audience
Product version
Release notes
Document revision level
Document organization
Related documents
Document conventions
Conventions for storage capacity values
Accessing product documentation
Getting help
Comments
Preface
Intended audience
This document is intended for those who:
Want to use Business Continuity Manager to improve the performance of

their storage systems.
This manual assumes that the reader has the following knowledge:
Functions of Lightning 9900V Series, USP, USP V, VSP or VSP G1000

storage systems.
Method for configuring a system using Hitachi Replication Manager for

linking to Hitachi Replication Manager.
Product version
This document revision applies to Hitachi Business Continuity Manager
version 8.0.0 or later.
Release notes
Read the release notes before installing and using this product. They may
contain requirements or restrictions that are not fully described in this
document or updates or corrections to this document.
Document revision level

Revision
vi
Date
Description
MK-94RD262-00
April 2005
Initial Release
MK-94RD262-01
June 2005
Revision 1, supersedes and replaces

MK-94RD262-00
MK-94RD262-02
October 2005

MK-94RD262-01
MK-94RD262-03
May 2006

MK-94RD262-02
MK-94RD262-04
October 2006

MK-94RD262-03
MK-94RD262-05
January 2007

MK-94RD262-04
MK-94RD262-06
June 2007

MK-94RD262-05
MK-94RD262-07
December 2007 Revision 7, supersedes and replaces

MK-94RD262-06
MK-94RD262-08
May 2008

MK-94RD262-07
Preface
Revision
Date
Description
MK-94RD262-09

MK-94RD262-08
MK-94RD262-10
July 2009
MK-94RD262-11

MK-94RD262-10
MK-94RD262-12
June 2010

MK-94RD262-11
MK-94RD262-13
October 2010

MK-94RD262-12
MK-94RD262-14
April 2011

MK-94RD262-13
MK-94RD262-15
August 2011

MK-94RD262-14
MK-94RD262-16
November 2011 Revision 16, supersedes and replaces

MK-94RD262-15
MK-94RD262-17
February 2012

MK-94RD262-16
MK-94RD262-18
July 2012

MK-94RD262-17
MK-94RD262-19
November 2012 Revision 19, supersedes and replaces

MK-94RD262-18
MK-94RD262-20
May 2013

MK-94RD262-19
MK-94RD262-21
October 2013

MK-94RD262-20
MK-94RD262-22
January 2014
Revision 22 (internal release only), supersedes and

replaces MK-94RD262-21
MK-94RD262-23
April 2014

MK-94RD262-22

MK-94RD262-09
Document organization
The following table provides an overview of the contents and organization of
this document. Click the chapter title in the left column to go to that chapter.
The first page of each chapter provides links to the sections in that chapter.
Chapter/Appendix
Chapter 1, Messages on
page 1-1
Description
Describes the messages.
Preface
vii
Chapter/Appendix
Chapter 2, Storage
system sense byte
information on page 2-1
Description
Describes storage system sense byte information (error
codes) contained in messages.
Related documents
Manuals related to Business Continuity Manager:
Hitachi Business Continuity Manager User Guide, MK-94RD247
Hitachi Business Continuity Manager Installation Guide, MK-95HC104
Hitachi Business Continuity Manager Reference Guide, MK-96HC135
Manuals related to Hitachi Command Suite products:
Hitachi Command Suite Tiered Storage Manager for Mainframe User

Guide, MK-92HC207
Hitachi Command Suite Replication Manager Configuration Guide,

MK-98HC151
Hitachi Command Suite Replication Manager User Guide, MK-99HC166
Manuals related to storage systems:
Hitachi Virtual Storage Platform Hitachi TrueCopy for IBM(R) z/OS(R) User
Guide, MK-94RD214
Hitachi Virtual Storage Platform Hitachi Universal Replicator for IBM(R) z/

OS(R) User Guide, MK-94RD224
Hitachi Command Control Interface User and Reference Guide,

MK-90RD011
Hitachi Virtual Storage Platform Hitachi Storage Navigator User Guide,

MK-94RD206
Hitachi Virtual Storage Platform Hitachi ShadowImage for IBM(R) z/OS(R)

User Guide, MK-94RD212
Hitachi Virtual Storage Platform Hitachi Universal Volume Manager User

Guide, MK-94RD220
Manuals related to z/OS:
viii
MVS Initialization and Tuning Reference, SA22-7592
MVS Programming: Assembler Services Reference, SA22-7606,

SA22-7607
MVS Setting Up a Sysplex, SA22-7625
MVS System Codes, SA22-7626
MVS System Commands, SA22-7627
Security Server RACF Security Administrator's Guide, SA22-7683
Security Server RACROUTE Macro Reference, SA88-8621
Preface
TSO/E Customization, SA22-7783
TSO/E Programming Services, SA22-7789
TSO/E REXX Reference, SA22-7790
TSO/E System Programming Command Reference, SA22-7793
MVS Programming: Assembler Services Guide, SA88-8577
DFSMS: Using Data Sets, SC26-7410
DFSMSdfp Utilities, SC26-7414
IBM Tivoli Storage Productivity Center for Replication Users Guide,

SC27-2322
Communications Server IP Configuration Guide, SC31-8775
Communications Server IP Configuration Reference, SC31-8776
Communications Server IP User's Guide & Commands, SC31-8780
Communications Server IP API Guide, SC31-8788
ISPF User's Guide Volume I, SC34-4822
DFSMS Advanced Copy Services, SC35-0428
Document conventions
This document uses the following typographic conventions:
Convention
Description
Bold
Indicates text on a window, other than the window title, including

menus, menu options, buttons, fields, and labels. Example: Click OK.
Italic
Indicates a variable, which is a placeholder for actual text provided by

the user or system. Example: copy source-file target-file
Note: Angled brackets (< >) are also used to indicate variables.
Monospace
Indicates text that is displayed on screen or entered by the user.

Example: # pairdisplay -g oradb
< > angled

brackets
Indicates a variable, which is a placeholder for actual text provided by

the user or system. Example: # pairdisplay -g <group>
Note: Italic font is also used to indicate variables.
[ ] square
brackets
Indicates optional values. Example: [ a | b ] indicates that you can

choose a, b, or nothing.
{ } braces
Indicates required or expected values. Example: { a | b } indicates

that you must choose either a or b.
| vertical bar
Indicates that you have a choice between two or more options or

arguments. Examples: [ a | b ] indicates that you can choose a, b, or
nothing. { a | b } indicates that you must choose either a or b.
This document uses the following icons to draw attention to information:
Preface
ix
Icon
Label
Description
Note
Calls attention to important and/or additional information.
Tip
Provides helpful information, guidelines, or suggestions for

performing tasks more effectively.
Caution
Warns the user of adverse conditions and/or consequences

(e.g., disruptive operations).
WARNING
Warns the user of severe conditions and/or consequences

(e.g., destructive operations).
Conventions for storage capacity values

Physical storage capacity values (for example, disk drive capacity) are
calculated based on the following values:
Physical capacity unit
Value
1 kilobyte (KB)
1,000 (103) bytes
1 megabyte (MB)
1,000 KB or 1,0002 bytes
1 gigabyte (GB)
1,000 MB or 1,0003 bytes
1 terabyte (TB)
1,000 GB or 1,0004 bytes
1 petabyte (PB)
1,000 TB or 1,0005 bytes
1 exabyte (EB)
1,000 PB or 1,0006 bytes
Logical storage capacity values (for example, logical device capacity) are
calculated based on the following values:
Logical capacity unit
Value
1 block
512 bytes
1 KB
1,024 (210) bytes
1 MB
1,024 KB or 1,0242 bytes
1 GB
1,024 MB or 1,0243 bytes
1 TB
1,024 GB or 1,0244 bytes
1 PB
1,024 TB or 1,0245 bytes
1 EB
1,024 PB or 1,0246 bytes
Preface
Accessing product documentation

The Business Continuity Manager user documentation is available on the
Hitachi Data Systems Portal: https://portal.hds.com. Check this site for
the most current documentation, including important updates that may have
been made after the release of the product.
Getting help
Hitachi Data Systems Support Portal is the destination for technical support of
your current or previously-sold storage systems, midrange and enterprise
servers, and combined solution offerings. The Hitachi Data Systems customer
support staff is available 24 hours a day, seven days a week. If you need
technical support, log on to the Hitachi Data Systems Support Portal for
contact information: https://portal.hds.com.
Hitachi Data Systems Community is a new global online community for HDS
customers, partners, independent software vendors, employees, and
prospects. It is an open discussion among these groups about the HDS
portfolio of products and services. It is the destination to get answers,
discover insights, and make connections. The HDS Community complements
our existing Support Portal and support services by providing an area where
you can get answers to non-critical issues and questions. Join the
conversation today! Go to community.hds.com, register, and complete
your profile.
Comments
Please send us your comments on this document: doc.comments@hds.com.
Include the document title and number, including the revision level (for
example, -07), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi Data Systems
Corporation.
Thank you!
Preface
xi
xii
Preface
1
Messages
This chapter describes the messages.
Message format
List of Messages
User completion codes
Messages
1-1
Message format
This section describes the format of the messages and the notations used in
this manual.
Message output format

Each message consists of a message ID and message text. The message
format is as follows:
YYYnnnZ message-text
The message ID format is as follows:
YYY
Indicates the message type.
YK7: YKBTSCAN
YK8: BCM Monitor
YK9: License
YKA: YKCONMSG
1-2
YKB: Messages output by the Copy Group Definition Generation

Function
YKC: YKSCAN
YKD: YKDELETE
YKE: YKEWAIT
YKF: YKFREEZE
YKG: YKHDAX (an internal program of YKLOAD)
YKH: YKH2B
YKJ: YKIMPORT, or YKEXPORT
YKK: YKINSCHK
YKL: YKLOAD
YKM: YKMAKE, messages displayed in the ISPF panel, or ISPFLOG
YKN: YKRUN
YKP: YKSTATS
YKQ: YKQUERY
YKR: YKRESYNC
YKS: YKSTORE
YKT: YKALCSVC, YKSETENV, or YKDSPENV
YKU: YKSUSPND
YKV: YKRECVER
YKW: YKWATCH
YKX: YKBLDCMD, YKDELCMD, or YKQRYDEV
Messages
YKY: Business Continuity Manager agent
YKZ: All commands or tools
nnn
Indicates the serial number of the message.
Z
Indicates the severity of the message.
T: Fatal
E: Error
W: Warning
I: Notification of information
Notations used to describe messages

Following are the notations used to describe messages in this manual, and
the message format. Messages are listed in the order of message IDs.
Message ID
message-ID message-output-destination
SC=xx#1 RC=xx#2(additional-information)#3,4
Message text
Description
message-text#4 message-description
#1
Severity code, which indicates the severity level. If the output destination
is MSG, this value is set to Severity in the message structure. For details
about the message structure, see the Hitachi Business Continuity
Manager Reference Guide.
#2
Return code, which is set when the message is output. If multiple return
codes were output for the message during command processing, the
largest value is set as the command return code.
#3
Detailed information used to confirm specific issues such as the error
location or volume identification information. If the output destination is
MSG, this value is set to Value in the message structure.
#4
Character strings enclosed in square brackets ([ ]) might be omitted.
Message output destination

The following destinations appear in messages:
MSG: Message structure
TSO: TSO/E terminal
CON: Console
Messages
1-3
SYS: SYSLOG
PRT: SYSPRINT or SYSTSPRT
LOG: ISPF log
ISPF: ISPF panel#
XML: Hitachi Command Suite product's log and window
#
If MSGID ON is specified using the ISPF system command, the message
ID and message text are displayed in the ISPF panel. However, if MSGID
OFF is specified, only the message text is displayed at the beginning
without the message ID.
If the sequence of REXX message variables is specified correctly in the MSG
parameter common to all CLI commands, the message will be saved in the
sequence.
If the MSG parameter is specified incorrectly, or an error occurs while the CLI
command is using the REXX interface, the message will be displayed at the
user's TSO/E terminal.
For details about the CLI commands, see the Hitachi Business Continuity
List of Messages
The following describes and gives corrective actions for messages.
Message Details
The following describes and gives corrective actions for messages.
Wait until all pending commands have finished execution before taking
corrective action.
Table 1-1 List of messages (message ID YK70x - YK90x)

Message ID
Message text
Explanation and recommended actions
YK7000T PRT
RC=16
Supplied parameters invalid: An invalid parameter was specified. Revise the value
line
specified on the line number identified by line.
YK7001E PRT
RC=16
No parameter-name
parameter supplied.
The parameter parameter-name is not specified.
YK7003E PRT
RC=16
The parameter parametername is invalid: line
The value assigned to the parameter-name parameter

is invalid. Revise the value specified on the line number
identified by line.
YK7004E PRT
RC=16
The parameter parametername is invalid.
The value assigned to the parameter-name parameter

is invalid.
YK7014I PRT
RC: rc CMD: command
The command indicated by command was issued, and

ended with the return code rc.
1-4
Messages
Message ID
YK7015I PRT
Message text
RC: rc CMD: command
Severity: Severity
Text: Text

The command indicated by command was issued, and
ended with the return code rc.
Severity
Severity code stored in Severity for the message
structure
Value: Value
Text
Message ID and message text stored in Text for

the message structure
Value
Detailed information stored in Value for the
message structure
Severity: Severity, Text: Text, and Value: Value
are displayed an amount of times equal to the number
of messages included in the message structure.
YK7031I PRT
RC=0
Scanned DASD Device

Count: count
The number of devices scanned by executing

YKBTSCAN.
count
Number of scanned devices
YK7032I PRT
RC=0
Hitachi storage systems

Devices Found: count
The number of Hitachi storage-system devices scanned

by executing YKBTSCAN.
count
Number of scanned Hitachi storage-system devices
YK7033I PRT
RC=4
The specified devices that do As a result of a scan, information acquisition was

not have any available I/O
skipped for the devices on which no I/O paths were
paths were skipped: count
available.
count
Number of devices for which information
acquisition was skipped
YK7099I PRT
YKBTSCAN return
code=nnnn
YKBTSCAN terminated with the return code nnnn. This

message is always displayed to indicate the return
code.
nnnn
Maximum value among the output return codes
YK8001I CON
BCM Monitor started. (v.r.m- BCM Monitor has started.

nn)
v.r.m-nn
Version and revision number
YK8002I CON
BCM Monitor terminated.
BCM Monitor has stopped.
YK8003I PRT
CON
time BCM Monitor stopped

monitoring Copy Groups.
BCM Monitor set the monitoring status of all copy

groups to INACTIVE.
time
Message output time
This is only displayed when the output destination
is SYSTSPRT.
Messages
1-5
Message ID
YK8007I PRT
CON
Message text
time Synchronization
percentage decreased, Copy
Group: cgid.

The copy progress percentage for the copy group
identified by cgid is decreasing.
time
Message output time
is SYSTSPRT.
cgid
Copy group ID
YK8008E CON
BCM Monitor initialization

failed: termination-code.
An attempt to start BCM Monitor failed because of the

reason indicated in a preceding message that was
output to either the console or dd SYSTSPRT.
Contact the center administrator. If you are the center
administrator, take action that is appropriate to the
previously output message, and then restart BCM
Monitor.
termination-code (decimal number)
YK8009E CON
Task(task-ID) abended:
completion-code.
04: An attempt was made to start BCM Monitor

without using IKJEFT01.
20: An attempt to analyze the YKMONOPT file

failed.
24: An attempt to analyze the YKMONCG file failed.
32: An error occurred while loading the process

module.
36: No profile is defined in the FACILITY class of

RACF.
40: The prefix specified in the YKMONCG file is

being used by the Business Continuity Manager
agent.
44: An attempt to initialize the subtask failed.
The task terminated abnormally during startup of BCM

Monitor. BCM Monitor will stop.
task-ID
Name for identifying the task
completion-code
System completion code
YK8010E CON
Module not found: loadmodule-name.
The load module identified by load-module-name

cannot be found. BCM Monitor will stop.
Check whether the load module has been properly
installed.
YK8011E CON
The profile is not defined in

the facility class of RACF:
xxxxxxxx.
The STGADMIN.YKA.BCM.YKQUERY profile or the

STGADMIN.YKA.BCM.COMMANDS profile is not defined in
the FACILITY class of RACF.
Review the RACF settings, and then restart BCM
Monitor.
xxxxxxxx
1-6
Messages
Message ID
Message text

Maintenance information
YK8012E CON
YK8013E CON
The specified prefix is being

used by another program:
prefix-name.
The specified prefix prefix-name is being used by

another program.
BCM Monitor abended.
BCM Monitor terminated abnormally.
Review the YKMONCG file.

If you cannot determine the cause of this problem,
obtain an ABEND dump in SYSABEND dump format,
and then make a request to the Support Center to
investigate the problem.
YK8014I CON
MODIFY command accepted: BCM Monitor accepted the MODIFY command-name

command-name.
command.
YK8015I CON
STOP command accepted.
BCM Monitor accepted the STOP command.
YK8016E CON
Command syntax error.
There is an error in the command syntax.

Make sure that the entered command is valid.
YK8017E CON
YK8018E CON
Invalid command:
command-name.
There is an error in the command-name command.
Operand is incorrect:
command-name.
There is an error in an operand of the command-name

command.
Make sure that the entered command is valid.
Correct the operand, and then re-enter the command.

YK8019E CON
The number of commands of

execution waiting exceed the
upper limit: commandname.
An attempt to execute the command identified by

command-name failed because the number of
commands waiting to be executed has reached the
upper limit.
Wait until all the waiting commands are finished
executing, and then re-execute the command.
YK8020I CON
nn: commandname[ parameter].
Information is displayed for the command waiting to be

executed.
nn
Number assigned to the waiting command
command-name
Name of the waiting command
The full name of the command is displayed, even if
the abbreviated name of the command was
entered.
parameter
Parameter specified in the waiting command
The full name of the parameter is displayed, even
if the abbreviated name of the parameter was
specified. If an omittable parameter was omitted,
the default value is displayed.
YK8021I CON
Execution waiting command

none.
There is no command waiting to be executed.
YK8022I CON
The state of sleep was

released.
BCM Monitor returned from the sleep state.
Messages
1-7
Message ID
Message text
YK8023W CON
The WAKEUP command was

not executed because it is
not in a sleep status.
The WAKEUP command cannot be executed because

BCM Monitor is not in the sleep state.
YK8024E CON
Insufficient space available:

maintenance-information.
An attempt to allocate space to BCM Monitor failed.

BCM Monitor will stop.
Increase the region size, and then restart BCM Monitor.
maintenance-information
Detailed information to assist in analyzing the error
YK8025E CON
IRXJCL module error:

return-code.
The IRXJCL routine returned an error with the return

code identified by return-code. BCM Monitor will stop.
Check the return code. If the code is 20, the SYSEXEC
DD statement might be invalid in the cataloged
procedure for startup for BCM Monitor.
Check the JCL, and then re-execute IRXJCL.
return-code
YK8026E CON
IRXINIT module error:

code=returncode,R0=abnormaltermination-code-andreason-code-for-abnormaltermination,PARM7=reasoncode.
20: EXEC processing failed.
20021: There was an error in the parameter list

that was passed to IRXJCL.
The IRXINIT routine returned an error with the return

Check the return code.
return-code
20: Processing failed due to an error. Check the

reason code returned to PARM7 by IRXINIT.
100: Processing failed because the system

abnormally terminated while IRXINIT was
checking the environment. The system might
output multiple messages reporting abnormal
termination. R0 includes the abnormal termination
code and the reason code for abnormal
termination.
abnormal-termination-code-and-reason-code-forabnormal-termination
IRXINIT returns the abnormal termination code in
the two trailing bytes of R0 and returns the reason
code for abnormal termination in the two leading
bytes of R0. If the reason code for abnormal
termination is larger than two bytes, IRXINIT
returns only the two trailing bytes for the reason
code for abnormal termination. For details on the
abnormal termination code and reason code, see
MVS System Codes.
reason-code
For details about the reason code, see TSO/E REXX
Reference.
1-8
Messages
Message ID
YK8027E CON
Message text
IRXTERM module error:
code=returncode,R0=abnormaltermination-code-andreason-code-for-abnormaltermination.

The IRXTERM routine returned an error with the return
return-code
For details about the return code, see TSO/E REXX
Reference.
R0 includes the abnormal termination code and the
reason code for abnormal termination. IRXTERM
returns the abnormal termination code in the two
trailing bytes of R0 and returns the reason code for
abnormal termination in the two leading bytes of
R0. If the reason code for abnormal termination is
larger than two bytes, IRXTERM returns only the
two trailing bytes of the reason code for abnormal
termination. For details about the abnormal
termination code and reason code, see MVS
System Codes.
YK8028E CON
BCM Monitor function abend: The main task or subtask terminated abnormally during
code=Sxxx Uxxxx
BCM Monitor processing. If the task cannot be
recovered, BCM Monitor will stop.
abended-module=modulename C-Date=modulecreation-date
base=bbbbbbbb disp=dddd
[calling-module=modulename C-Date=y'y'.m'm'.d'd'
base=bbbbbbbb disp=dddd]
PSW=pppppppp pppppppp
ILC=ll INTC=xx
Registers at time of failure
Contact the center administrator.

Sxxx (hexadecimal number)
System completion code when the task terminated

abnormally
Uxxxx (decimal number)
User completion code when the task terminated
abnormally
module-name
Section name of the BCM Monitor module or load
module name.
GR 00-03 contents-ofregister-0 contents-ofregister-1 contents-ofregister-2 contents-ofregister-3

If the module cannot be identified, UNKNOWN is

displayed. In this case, the values of y'y'.m'm'.d'd'
and bbbbbbbb are invalid.
module-creation-date
This is displayed in one of the following formats:
y'y'.m'm'.d'd': Creation date of the module

identified by module-name
y'y'/m'm'/d'd': Creation date of the module

identified by module-name
bbbbbbbb
Contents of the base register
dddd
ABENDED-MODULE: Location where ABENDED-MODULE

was called, relative to the top of the module
CALLING-MODULE: Location where CALLING-MODULE

Messages
1-9
Message ID
Message text

pppppppp pppppppp
PSW during the abnormal termination
ll
Length of the command during the abnormal
termination
xx
Interrupt code during the abnormal termination
YK8031W CON
The specified error-type is

invalid: command-name.
The value identified by error-type, which was specified

in the command-name command, is invalid.
error-type
YK8040I PRT
CON
time BCM Monitor will stop

at STOPPOINT 'label'.
label: The label name is invalid. Check the label

name for ACTION=STOPPOINT specified in the
YKMONCG file.
copy group: The copy group ID is invalid. Check

the copy group ID for CGID specified in the
YKMONCG file.
BCM Monitor will stop at the point label.

time
Message output time
is SYSTSPRT.
label
Label at which BCM Monitor stops
YK8041I PRT
CON
time BCM Monitor will stop

at the end of monitor cycle.
BCM Monitor will stop at the end of a cycle.

time
Message output time
is SYSTSPRT.
YK8042I PRT
CON
time BCM Monitor will sleep

BCM Monitor will go to sleep at the point label.
at STOPPOINT 'label' for max Entering the WAKEUP command resumes copy group
'sleep-time' minutes.
monitoring before the duration identified by sleep-time
has elapsed.
time
Message output time
is SYSTSPRT.
label
Label at which BCM Monitor goes to sleep
sleep-time
Sleep duration
YK8043I PRT
CON
time STOPPOINT 'label'

reached.
BCM Monitor has reached the point label.

time
Message output time
1-10
Messages
Message ID
Message text

is SYSTSPRT.
YK8044I PRT
CON
time BCM Monitor will sleep

now for max 'sleep-time'
minutes.
BCM Monitor will sleep for the duration identified by

sleep-time.
Entering the WAKEUP command resumes copy group
monitoring before the duration identified by sleep-time
has elapsed.
time
Message output time
is SYSTSPRT.
sleep-time
Sleep duration
YK8045I PRT
CON
time BCM Monitor reached

the end of the monitoring
cycle.
BCM Monitor has reached the end of a cycle.

time
Message output time
is SYSTSPRT.
YK8046I PRT
CON
time Execute operator

command 'opcmd'.
BCM Monitor will execute the operator command

identified by opcmd.
time
Message output time
is SYSTSPRT.
YK8047I PRT
CON
time Set MONITOR=status

for Copy Group 'cgid'.
BCM Monitor set the monitoring status of the copy

group cgid to the status status.
time
Message output time
is SYSTSPRT.
status
YK8048I PRT
CON
time Set CYCLETIME to :

cycletime.
START: The monitoring status of the copy group

was set to ACTIVE.
STOP: The monitoring status of the copy group was

set to INACTIVE.
BCM Monitor set CYCLETIME to the value identified by

cycletime.
time
Message output time
is SYSTSPRT.
YK8049I PRT
CON
time Set WAITTIMEOUT to :

timeout.
BCM Monitor set WAITTIMEOUT to the value identified by

timeout.
time
Messages
1-11
Message ID
Message text

Message output time
is SYSTSPRT.
YK8050I PRT
CON
time Set MSGLEVEL to :

MSGLEVEL=lvllog,lvlcons.
BCM Monitor set MSGLEVEL to the values identified by

lvllog and lvlcons.
time
Message output time
is SYSTSPRT.
lvllog
Level of messages to be output to SYSTSPRT
lvlcons
Level of messages to be output to the console
YK8054I PRT
CON
time BCM Monitor resume

monitoring.
BCM Monitor resumed processing.

time
Message output time
is SYSTSPRT.
YK8055I PRT
CON
time BCM Monitor will pause BCM Monitor will go to sleep because the PAUSE action
now for 'sleep-time' minutes. was executed.
Entering the WAKEUP command resumes copy group
monitoring before the sleep time of sleep-time has
elapsed.
time
Message output time
is SYSTSPRT.
sleep-time
Sleep duration
YK8056E PRT
CON
time Failed to execute

operator command.
BCM Monitor failed to execute an operator command.

time
Message output time
is SYSTSPRT.
YK8070E PRT
time File Open error : ddname.
The file dd-name could not be opened.

time
Message output time
is SYSTSPRT.
dd-name
dd name of the file where the error occurred
YK8071E PRT
1-12
time File Close error : ddname.
The file dd-name could not be closed.

time
Messages
Message ID
Message text

Message output time
is SYSTSPRT.
dd-name
YK8073E PRT
time A GETMAIN error

occurred. return code=nnn.
A GETMAIN error occurred. The program will stop

running.
Contact Technical Support for assistance.
time
Message output time
is SYSTSPRT.
nnn (decimal number)
Return code of the GETMAIN macro
YK8074E PRT
time A FREEMAIN error

occurred. return code=nnn.
A FREEMAIN error occurred. The program will stop

running.
time
Message output time
is SYSTSPRT.
Return code of the FREEMAIN macro
YK8075E PRT
time Parameter syntax

error : file : rec#.
There is a syntax error in a parameter.

time
Message output time
is SYSTSPRT.
file
Name of the file where the error occurred
rec#
Line number in the file file where the error was
detected
YK8076E PRT
time Invalid parameter was

specified : file : rec#.
An invalid parameter was specified.

time
Message output time
is SYSTSPRT.
file
rec#
detected
Messages
1-13
Message ID
YK8077E PRT
Message text
time Invalid value was
specified for param
parameter : file : rec#.

The parameter value param is invalid.
time
Message output time
is SYSTSPRT.
file
rec#
detected
YK8078E PRT
time A required parameter is The required parameter param-name is not specified.

missing : file : param-name. time
Message output time
is SYSTSPRT.
file
param-name
Name of the required parameter
YK8079E PRT
time CGID parameter must

be specified first : rec#.
Specify the CGID parameter at the beginning of the

copy group parameters in the YKMONCG file.
time
Message output time
is SYSTSPRT.
rec#
Line number where the error was detected
YK8080E PRT
time Duplicate CGID

parameters found : cgid.
The copy group cgid is specified more than once in the

YKMONCG file.
time
Message output time
is SYSTSPRT.
cgid
CGID parameter value that is specified more than
once
YK8081E PRT
time Combination of STATUS The combination of STATUS and ACTION specified in the
and ACTION is invalid :
YKMONCG file is invalid.
rec#.
time
Message output time
is SYSTSPRT.
rec#
1-14
Messages
Message ID
Message text

YK8082E PRT
time Combination of Startup

Status and NOCANCEL is
invalid : rec#.
The combination of NOCANCEL and the startup status

specified for the CGSTARTUPSTATUS parameter in the
YKMONCG file is invalid.
time
Message output time
is SYSTSPRT.
rec#
YK8083E PRT
time The corresponding

CGID parameter is not
defined : cgid.
The copy group cgid specified in the ACTION parameter

of the YKMONCG file is not defined.
time
Message output time
is SYSTSPRT.
cgid
Copy group ID specified in the ACTION parameter
YK8084E PRT
time The continuation

symbol can not be specified
in the final record : file.
The continuation symbol was specified for the final

record.
time
Message output time
is SYSTSPRT.
file
YK8085E PRT
time File record format is

invalid : dd-name.
The record format of the file indicated by dd-name is

invalid.
The valid record format is F, FB, V, or VB.
time
Message output time
is SYSTSPRT.
dd-name
YK8100I PRT
CON
time sendmsg
The message identified by sendmsg appears. The

message is specified in SENDMSG with the CONS level
designated.
time
Message output time
is SYSTSPRT.
Messages
1-15
Message ID
YK8200I PRT
CON
Message text
time sendmsg

message is specified in SENDMSG with the ERROR level
designated.
time
Message output time
is SYSTSPRT.
YK8220E PRT
CON
time cmd error for Copy

Group 'cgid'
An error occurred during execution of the cmd

command for the copy group identified by cgid.
time return code rc received

from cmd
time
Message output time
time COMMAND : 'cmdparm'

time MSG:
time ['err-msg'].

is SYSTSPRT.
cmd-parm
Executed CLI command
rc
Return code from the CLI command
err-msg
Message included in the message structure for the
CLI command
The number of lines equal to the number of
messages included in the message structure are
displayed.
YK8221I PRT
CON
time YKEWAIT (RC=4) :

TIMEOUT value (timeout)
reached.
The YKEWAIT command timed out before the transition

to the expected group status.
time
Message output time
is SYSTSPRT.
timeout
Timeout value
YK8222E PRT
CON
time YKEWAIT (RC=8) :

Unexpected status reached.
An unexpected group status was reached during

execution of the YKEWAIT command.
time
Message output time
is SYSTSPRT.
YK8223W PRT
CON
time cmd (RC=4) : Some

volumes with invalid status
found.
Invalid volumes were detected in the copy group

during the execution of the CLI command cmd.
Processing of these volumes was skipped.
time
Message output time
is SYSTSPRT.
1-16
Messages
Message ID
YK8230E PRT
CON
Message text
time REPORT type is only
valid for TCA or UR Copy
Groups.

type, which was specified for the REPORT parameter, is
only valid for TrueCopy Asynchronous or Universal
Replicator copy groups.
time
Message output time
is SYSTSPRT.
type
Report type
YK8231E PRT
CON
time BCM Monitor can not

adjust Copy Group status.
BCM Monitor could not set the copy group to the

specified startup status.
time
Message output time
is SYSTSPRT.
YK8300I PRT
CON
time sendmsg

message is specified in SENDMSG with the STATUS level
designated.
time
Message output time
is SYSTSPRT.
YK8301I PRT
CON
time Not all volumes are in

'status'. action requested.
The action identified by action will be executed because

there is a volume that is not in the status identified by
status.
time
Message output time
is SYSTSPRT.
YK8302I PRT
CON
time Trying to cmd Copy

Group 'cgid'.
The CLI command identified by cmd will be executed

for the copy group identified by cgid.
time
Message output time
is SYSTSPRT.
YK8303I PRT
CON
time Waiting for status

'status'.
BCM Monitor will wait until the copy group being

monitored enters the status identified by status.
time
Message output time
is SYSTSPRT.
YK8304I PRT
CON
time Copy Group is in

'status' status. Wait until
status has changed.
BCM Monitor will wait until the copy group status

identified by status changes to another status.
time
Messages
1-17
Message ID
Message text

Message output time
is SYSTSPRT.
YK8305I PRT
CON
time Status ok.
The copy group entered the expected status.

time
Message output time
is SYSTSPRT.
YK8310I
See YK8310I PRT on page

1-161.
N/A
YK8311I CON
REPORT SUMMARY:
This message indicates the results of

REPORT(SUMMARY).
COPY GROUP : cgid TYPE :

cgtype
DAD-ID : dad PREFIX :
prefix
SIMPLEX : simplexct
PENDING : pendingct
DUPLEX : duplexct
SUSPEND : suspendallct
OTHER : otherct
GROUP STATUS : status
MATCHING% : match
REVERSED% : rev%
ATTIME(GMT) : attime STATUS : attms
cgid
Copy group ID
cgtype
Copy group type
dad
Copy group host device address domain ID
prefix
Prefix
simplexct
Number of copy pairs in SIMPLEX status
pendingct
Number of copy pairs in PENDING status
duplexct
Number of copy pairs in DUPLEX status
suspendallct
Number of copy pairs in SUSPEND status
otherct
Number of copy pairs in other statuses
status
Copy group status
match
Copy progress percentage
rev%
Percentage of copy pairs whose copy direction is
secondary-to-primary
attime
ATTIME suspend time
attms
ATTIME suspend status
1-18
Messages
Message ID
Message text
YK8312I

1-162.
N/A
YK8313I CON
REPORT DETAIL:
This message indicates the results of REPORT(DETAIL).

cgtype
cgid
Copy group ID

prefix
cgtype
VOLSER PDEVN DIR SDEVN

STATUS MATCH% C/T
SUBC/T DELTA CTTIME
dad
volser pdevn dir sdevn

status match ctid sub-ctid
ctdelta cttime
Copy group type

prefix
Prefix
volser
Volume serial number
pdevn
Primary device number
dir
Copy direction
>: Primary-to-secondary
<: Secondary-to-primary
sdevn
Secondary device number
status
Copy pair status
match
Copy pair matching percentage
ctid
Consistency group ID or master journal group ID
sub-ctid
Restore journal group ID
ctdelta
Consistency delta value for each consistency group
cttime
Consistency time for each consistency group
YK8314I

1-163.
N/A
YK8315I CON
REPORT RPO:
This message indicates the results of REPORT(RPO).
COPY GROUP : cgid
cgid
C/T SUBC/T PSN SSN DELTA

CTTIME
ctid sub-ctid psn ssn ctdelta
cttime
Copy group ID
ctid
Consistency group ID or master journal group ID
sub-ctid
Messages
1-19
Message ID
Message text

psn
Serial number of the primary storage system
ssn
Serial number of the secondary storage system
ctdelta
Consistency delta value
cttime
Consistency time
YK8316I

1-163.
N/A
YK8317I CON
REPORT STATS:
This message indicates the results of REPORT(STATS)

for the TrueCopy Asynchronous copy group.

cgtype
cgid

prefix
Copy group ID
cgtype
C/T PSN SSN SFT PRSFTOT
Copy group type
PRSFC/T PWPRTOT SRSFTOT
dad
SRSFC/T SWPRTOT TRANS
OFLD RCUR CPND
ctid psn ssn sidefileprefix
threshold p-rsf-all p-rsf-ct pPrefix
wpr-all s-rsf-all s-rsf-ct sctid
wpr-all mcu-to-rcu-kbps
offload-timer rcu-readyConsistency group ID
timer copy-pending-timer
psn
ssn
sidefile-threshold
Sidefile threshold value
p-rsf-all
Primary reserve sidefile cache-usage rate
p-rsf-ct
Primary reserve sidefile consistency cache-usage
rate
p-wpr-all
Primary write pending rate
s-rsf-all
Secondary reserve sidefile cache-usage rate
s-rsf-ct
Secondary reserve sidefile consistency cacheusage rate
s-wpr-all
Secondary write pending rate
mcu-to-rcu-kbps
1-20
Messages
Message ID
Message text

Data transfer rate (Kbps) between the main
control unit and the remote control unit
offload-timer
Offloading timer
rcu-ready-timer
Remote control unit ready timer
copy-pending-timer
Copy pending timer
YK8318I

1-164.
N/A
YK8319I CON
REPORT STATS:
This message indicates the results of REPORT(STATS)

for the Universal Replicator copy group.

cgtype
cgid

prefix
Copy group ID
cgtype
C/T SUBC/T PSN SSN TRANS
Copy group type
PJMET% PJDAT% SJMET%
dad
SJDAT% PJDATA SJDATA
ctid sub-ctid psn ssn mcuto-rcu-kbps p-jnl-meta p-jnl- prefix
data s-jnl-meta s-jnl-data pPrefix
jnl-data-capacity s-jnl-datactid
capacity
Master journal group ID
sub-ctid
psn
ssn
mcu-to-rcu-kbps
Data transfer rate (Kbps) between the main
control unit and the remote control unit
p-jnl-meta
Metadata % used rate in master journal volume
p-jnl-data
Data % used rate in master journal volume
s-jnl-meta
Metadata % used rate in restore journal volume
s-jnl-data
Data % used rate in restore journal volume
p-jnl-data-capacity
Master journal volume data capacity (GB)
s-jnl-data-capacity
Restore journal volume data capacity (GB)
Messages
1-21
Message ID
YK8320I PRT
CON
Message text
time Copy Group 'cgid' has
reached target status
'status'.

The copy group identified by cgid has switched to the
target status identified by status.
time
Message output time
is SYSTSPRT.
YK8321I PRT
CON
time Some volumes are in a

'TRANSITION' status.
Some volumes are in the TRANSITION status.

time
Message output time
is SYSTSPRT.
YK8322I PRT
CON
time Some volumes are in a

'TRANSITION', 'SIMPLEX',
'HOLD' OR ERROR status.
Some volumes are in the TRANSITION, SIMPLEX, HOLD

status, or an abnormal status.
time
Message output time
is SYSTSPRT.
YK8323I PRT
CON
time Some volumes are not

in a 'HOLDER' status.
Some volumes are not in the HOLDER status.

time
Message output time
is SYSTSPRT.
YK8324I PRT
CON
time All volumes are in

'HOLDER' status.
All volumes are in the HOLDER status.

time
Message output time
is SYSTSPRT.
YK8325I PRT
CON
time Copy Group 'cgid' is

'status' now.
The copy group identified by cgid entered the status

identified by status.
time
Message output time
is SYSTSPRT.
YK8326I PRT
CON
time Copy Group 'cgid' will

be suspended at: atparm.
The copy group identified by cgid is set to suspend at

the time indicated by atparm.
time
Message output time
is SYSTSPRT.
atparm
ATTIME suspend time
1-22
Messages
Message ID
YK8400I PRT
CON
Message text
time sendmsg

message is specified in SENDMSG with the INFO level
designated.
time
Message output time
is SYSTSPRT.
YK8401I PRT
CON
time Check Startup Status of BCM Monitor will start checking the status of the copy
Copy Group 'cgid':
group identified by cgid.
time
Message output time
is SYSTSPRT.
YK8402I PRT
CON
time Startup Status check of

Copy Group 'cgid' finished.
The status check of the copy group identified by cgid is

complete.
time
Message output time
is SYSTSPRT.
YK8403I PRT
CON
time Start monitoring Copy

Group.
BCM Monitor will start monitoring the copy group.

time
Message output time
is SYSTSPRT.
YK8404I PRT
CON
time Execute action 'action

err-action'
BCM Monitor will execute the action identified by action

err-action specified in the ACTION parameter for
STATUS.
time
Message output time
is SYSTSPRT.
action
Action to be executed
err-action
Error action to be executed
YK8405I PRT
CON
time The return code of the

action is RC=rc.
Error rc occurred for a Business Continuity Manager CLI

command executed by an action.
time
Message output time
is SYSTSPRT.
rc
Return code of the Business Continuity Manager
CLI command executed by the action
Messages
1-23
Message ID
YK8406I PRT
CON
Message text
time Execute error action
'err-action'.

BCM Monitor will execute the error action identified by
err-action.
time
Message output time
is SYSTSPRT.
err-action
YK8410I PRT
CON
time ---- date ----
The date is displayed when BCM Monitor is started or

when the date changes while BCM Monitor is running.
time
Message output time
is SYSTSPRT.
date
New date
For example, Thursday, 21 Jan 2010 is displayed.
YK8411I

1-165.
N/A
YK8412I CON
SYSTEM OPTIONS:
This message indicates the values specified in the

YKMONOPT file.
CYCLE TIME : cycletime

WAITFOR TIMEOUT :
timeout MSGLEVEL :
lvllog,lvlcons
ONACTIONERROR : erraction
STOP AT STOPPOINT :
stoppt SLEEP AT
STOPPOINT : sleeppt
cycletime
Cycle time
timeout
Timeout value
lvllog
Level of messages to be output to SYSTSPRT
lvlcons
Level of messages to be output to the console
err-action
stoppt
Stop point
sleeppt
Sleep point
YK8413I

1-165.
N/A
YK8414I CON
COPY GROUP DEFINITIONS:
This message indicates the values specified in the

YKMONCG file. This message appears a number of
times, equal to the number of copy groups specified.
ID : cgid PREFIX : prefix

DAD-ID : dad ROUTE LIST :
route[,route-label]
MONITOR STATUS :
cgmonstat STARTUP
1-24
cgid
Copy group ID
prefix
Messages
Message ID
Message text
STATUS :
cgsastat,cgsaact,cgsaopt
WHEN STATUS status DO
ACTION 'action;err-action;'

Prefix
dad
route
Route list ID
route-label
Route label
cgmonstat
Copy group monitoring status (ACTIVE or
INACTIVE)
cgsastat
Copy group startup status to be checked when
BCM Monitor starts
cgsaact
Startup action executed if the copy pair status for
starting BCM Monitor is different from the specified
startup status
cgsaopt
Option information of the CGSTARTUPSTATUS
parameter
status action err-action
Status, action, and error action for the copy group
specified in STATUS and ACTION
These parameters appear a specified number of
times.
YK9001I ISPF
The license key(s) has been

installed
The license key was installed.
YK9051E ISPF
An error occurred in the

license information dataset
An error occurred with the license information dataset.

Check that the prefix of the license information dataset
is registered correctly, and that the license information
dataset is created correctly. If necessary, recreate the
license information dataset and re-register the license
keys in the order in which they were issued.
For details about registering a prefix name of the
license information dataset, see the Hitachi Business
Continuity Manager Reference Guide.
YK9052E ISPF
YK9071W ISPF
An error occurred in the

license key dataset
An error occurred with the license key dataset.
A license key was not found
An attempt was made to install a license key, but no

installable license key was found in the license key
dataset.
Check that the dataset name of the license key dataset

is correct, and that the license key dataset is created
correctly. If necessary, transfer the license key file
again and recreate the license key dataset.
Make sure that none of the following conditions exist:
The license key you attempted to install was

already installed.
Messages
1-25
Message ID
YK9072W ISPF
YK9080E CON
Message text
The license key could not be

installed.
The expiration date for your

license key (function).
The license key you attempted to install was not

for this product.
The dataset you specified was not a license key

dataset.
An attempt to install the license key has failed.

Check if one of the following conditions is applicable. If
none is applicable, make sure the key code is correct:
The license key you attempted to install was

already installed.
The license key you attempted to install was not

for this product.
The license (function) has expired.

To continue using this product after the expiry date,
you need a permanent license.
If function is Basic:
A permanent license for Business Continuity
Manager Basic is required.
If function is UR 4x4 Extended CTG:
Manager UR 4x4 Extended CTG is required.
YK9081W CON
Your function license will

expire in n day(s).
The license (function) will expire in n days.

Table 1-2 List of messages (message ID YKA0x - YKB20x)

Message ID
Message text
YKA000T TSO
Supplied parameters invalid
An error was detected during parameter analysis.
YKA001E TSO
HANDLE() value not valid
The handle value assigned to the HANDLE parameter is

invalid.
YKA002E TSO
HANDLE() parameter
required for this operation
The OP(GET) and OP(CLOSE) requests require the

HANDLE parameter to be specified.
Use the handle value returned by the OP(OPEN) request
in the YKA098I message.
YKA003E TSO
YKA004E TSO
1-26
OP(OPEN|GET|CLOSE)
option required
The OP parameter is missing.
Buffer full; messages

discarded
An attempt to acquire the IEA494I console message,

IOSHM0414I console message, or the message specified
Specify the OP parameter.
Messages
Message ID
Message text

in the MSGID parameter of the YKCONMSG command
failed. This problem might occur when console
message traffic is too high or when the YKCONMSG
command issuance interval is too long.
When you receive this message, issue the YKQUERY
command to check the copy pair status.
YKA006E TSO
SYSTEM ERROR. error-type
A system error was detected.

Contact HDS Technical Support for assistance.
error-type
Type of system error
YKA007E TSO
TIMEOUT() value not valid
The value specified in the TIMEOUT parameter is invalid.
YKA008E TSO
TIMEOUT() parameter
cannot be specified for this
operation
If GET or CLOSE is specified in the OP parameter, you

cannot specify the TIMEOUT parameter.
YKA009E TSO
MSGID() value not valid
The value specified in the MSGID parameter is invalid.
YKA010E TSO
MSGID() parameter cannot

be specified for this
operation
If GET or CLOSE is specified in the OP parameter, you

cannot specify the MSGID parameter.
YKA096I TSO
No message found
Specify OPEN in the OP parameter, and then specify the

TIMEOUT parameter.
Specify OPEN in the OP parameter, and then specify the

MSGID parameter.
Processing of the YKCONMSG command with OP(GET)
specified exceeded the time specified in the TIMEOUT
parameter, but the IEA494I console message,
IOSHM0414I console message, or the message specified
in the MSGID parameter of the YKCONMSG command
have not yet been displayed.
Re-execute the YKCONMSG command with OP(GET)
specified after the system becomes ready to receive
messages.
YKA097I TSO
message-text
The YKCONMSG command with OP(GET) specified

returned the IEA494I console message, IOSHM0414I
console message, or the message message-text
specified in the MSGID parameter of the YKCONMSG
command in the order in which the messages arrived.
YKA098I TSO
HANDLE(x'handle')
The YKCONMSG command with the OP(OPEN) parameter

specified was executed successfully.
From now on, if you execute the YKCONMSG command
with the OP(GET) or OP(CLOSE) parameter specified,
use the returned handle value in handle.
YKA099I TSO
Close operation complete
The YKCONMSG command with the OP(OPEN) parameter

specified terminated normally.
YKB001I TSO
YKP2B completed.
RC=return-code
The YKP2B command terminated.

return-code
The return code of the YKP2B command:
Messages
1-27
Message ID
Message text

0: The command ended successfully. The copy
group definition file was output.
4: Indicates that one of the following occurred.
- The command ended successfully. No copy pair
was detected within the range of the specified
device numbers.
- A copy group definition file was created, but
volume information not defined in the disk
configuration definition file for the site specified in
the DAD parameter was detected among copy pairs
within the range specified in the DEVN parameter.
- A copy group definition file was created, but a
change was detected in the I/O configuration when
the YKP2B command was executed with CHECK
specified in the HS parameter.
8: An I/O error occurred in a volume within the
search range. The copy group definition file was
created for the volume that was successfully
detected.
44: The processing was canceled due to an error.
The copy group definition file was not created.
48: The command ended due to an invalid
parameter.
YKB002I TSO
No copy pair was discovered. No copy pair was detected within the specified range.
Check the operating range and status of the copy pair
that you want to acquire, and execute the YKP2B
command again. If the copy pair status is SIMPLEX, the
YKP2B command does not detect any copy pair.
YKB100E TSO
Missing or invalid parameter: The parameter specification was invalid or missing.

parameter-name
Check the following, and then re-execute the
command:
Make sure that the required parameter indicated

by parameter-name was specified.
Make sure that the value specified for the required

parameter indicated by parameter-name is valid.
Make sure that different device address domain

IDs for the primary and secondary sites are
specified for the DAD parameter.
parameter-name
Name of the invalid or missing parameter
YKB101E TSO
YKB102E TSO
1-28
The specified PREFIX is

being used by another
program.
The specified prefix is being used by another program.
Error occurred during

execution. Cmd=commandname
An error occurred during execution of the YKP2B

command.
Check the value specified for the prefix.
See the explanation corresponding to the message ID

of the error message indicated by message-text and
take appropriate action. Also see the additional
Messages
Message ID
Message text
msg=message-text:
message-value: messageseverity

information indicated by message-value and messageseverity and take appropriate action. If the problem is
not resolved, contact your Hitachi Data Systems
representative or authorized service provider.
command-name
CLI command name
message-text
Error message
message-value
Additional information about the error message
If no additional information is available, a space is
displayed.
message-severity
displayed.
The error messages message-text, message-value, and
message-severity are displayed on the TSO/E terminal.
Long error messages may extend over several lines.
YKB200W TSO
No information was acquired

for DEVN=device-number
No copy pair information was acquired from the volume

to which the device number device-number was
assigned.
There might not be a volume for the specified device
number. If the volume exists for the specified device
number, check the channel settings.
device-number
Device number assigned to the volume from which
no copy pair information was acquired
YKB201W TSO
No I/O paths are available

for the specified devices.
DEVN=Devn

to which the device number Devn was assigned
because no I/O paths are available.
Verify the I/O path settings.
Devn
The device number of the volume on which
information acquisition was skipped
YKB202W TSO
Unable to resolve primary

volume information.
Pair=CopyType,DEVN=Devn,
SN=SerialNum,CU=CU#,CC
A=CCA#
A P-VOL not defined in the disk configuration definition

file was included among the PPRC copy pairs detected
by the YKP2B command.
Check whether this P-VOL is defined in the disk
configuration definition file.
CopyType
The copy type of the detected undefined volume
Devn
The device number of the detected undefined
volume
SerialNum
Messages
1-29
Message ID
Message text

The serial number of storage system of the
detected undefined volume
CU#
The control unit number of the detected undefined
volume
CCA#
The command control address number of the
YKB203W TSO
Unable to resolve secondary An S-VOL not defined in the disk configuration

volume information.
definition file was included among the PPRC copy pairs
Pair=CopyType,SN=SerialNu detected by the YKP2B command.
m,CU=CU#,CCA=CCA#
Check whether this S-VOL is defined in the disk
CopyType
The copy type of the detected undefined volume
SerialNum
The storage system serial number of the detected
undefined volume
CU#
volume
CCA#
YKB204W TSO
A dynamic configuration
change was detected.
DEVN=device-number
A dynamic change was detected in an I/O configuration

definition while the YKP2B command was executing
with CHECK specified for the HS parameter.
Check the status of the device targeted by the YKP2B
command, correct any errors in the configuration or
execution conditions, and then re-execute the
command.
device-number
Device number being processed when a dynamic
change was detected in an I/O configuration
definition
Table 1-3 List of messages (message ID YKC0x)

Message ID
Message text
YKC000T TSO
RC=48
YKC001E MSG
SC=48 RC=48
No controller ARRAYS()
supplied
1-30

Invalid parameters are specified.
For details, see the reason code in the YKC099I
message displayed after this message. For reason
codes, see IKJPARS in the TSO/E Programming
Services.
Nothing is assigned to the ARRAYS parameter.
Messages
Message ID
Message text
YKC001E TSO
RC=48
No message MSG() supplied
Nothing is assigned to the MSG parameter.
YKC001E MSG
SC=48 RC=48
No results STEM() supplied
Nothing is assigned to the STEM parameter.
YKC001E MSG
SC=48 RC=48
No starting FROM() supplied
Nothing is assigned to the FROM parameter.
YKC002E MSG
SC=48 RC=48
Controller ARRAYS(stem)
does not include trailing "."
The last character of the ARRAYS parameter is not a

period.
stem
Stem name assigned to the ARRAYS parameter
YKC002E TSO
RC=48
Messages MSG(stem) does

not include trailing "."
The last character of the MSG parameter is not a period.

stem
Stem name assigned to the MSG parameter
YKC002E MSG
SC=48 RC=48
Results STEM(stem) does

The last character of the STEM parameter is not a

period.
stem
Stem name assigned to the STEM parameter
YKC008E MSG
SC=48 RC=48
Ending TO() not valid hex
The value specified in the TO parameter is not in

hexadecimal format.
YKC008E MSG
SC=48
Starting FROMVSN() value

invalid
The value specified in the FROMVSN parameter is invalid.
YKC008E MSG
SC=48
Ending TOVSN() value

invalid
The value specified in the TOVSN parameter is invalid.
YKC008E MSG
SC=48 RC=48
Starting FROM() not valid

hex
The value specified in the FROM parameter is not in

hexadecimal format.
YKC009E MSG
SC=48 RC=48
Specify DEV# and VOLSER

parm exclusively
You cannot specify a device number and a volume

serial number at the same time.
YKC009E MSG
SC=48 RC=48
Starting FROM() exceeds

ending TO()
The value specified in the FROM parameter exceeds the

value of the TO parameter.
YKC009E MSG
SC=48 RC=48
Starting FROMVSN() exceeds The value specified in the FROMVSN parameter exceeds
ending TOVSN()
the value of the TOVSN parameter.
YKC010E TSO
RC=40
REXX failure return

code=nnnn starting with
variable name
Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the
TSO/E Programming Services.
nnnn
Error code returned upon REXX access
YKC031I MSG
SC=0 (count)
Scanned DASD Device Count The number of DASD devices scanned by the YKSCAN
command.
count
Number of scanned DASD devices
YKC032I MSG
SC=0 (count)
Hitachi storage systems

Devices Found
The number of Hitachi storage-system devices scanned

by the YKSCAN command.
Messages
1-31
Message ID
Message text

count
Number of Hitachi storage-system devices
YKC033I MSG
SC=4 (count)
The specified devices that do As a result of the device scan, information acquisition
not have any available I/O
on devices for which no I/O path is available was
paths were skipped.
skipped.
count
The number of devices skipped when the device
information was acquired
YKC034E MSG
SC=32 RC=32
change was detected during
YKSCAN command
processing.
A dynamic change to an I/O configuration definition

was detected during processing of the YKSCAN
command. This error may be due to the volume serial
number in the acquired volume information differing
from that in the actual configuration.
Check the disk configuration definition file after the
scan is complete. If the volume serial number is
different from the one in the actual configuration, reexecute the scan.
YKC099I TSO
YKSCAN command return

code=nnnn, reason
code=rrrr
The YKSCAN command terminated with the return code

nnnn and the reason code rrrr.
This message is always displayed to indicate the return
code and the reason code.
nnnn
Maximum among the severity codes returned
during command execution
Table 1-4 List of messages (message ID YKD0x)

Message ID
Message text
YKD000T TSO
RC=48
YKD001E TSO
RC=48
YKD001E MSG
SC=48 RC=48
YKD002E MSG
SC=48 RC=48
Copy Group STEM(stem)


period.
For details, see the reason code in the YKD099I

message that will appear after this message. For
reason codes, see IKJPARS in the TSO/E Programming
Services.
stem
YKD002E MSG
SC=48
DEVN() value invalid
The value assigned to the DEVN parameter is invalid.
YKD002E TSO
RC=48

1-32
stem
Messages
Message ID
Message text

YKD008E MSG
SC=48
DEVN() not valid hex
The value specified in the DEVN parameter is not in

hexadecimal format.
YKD010E TSO
RC=40
REXX failure return

variable name

nnnn
YKD050E MSG
SC=36 RC=48
(attribute-value)
Invalid Copy Group attribute

name
The specified copy group attribute value is invalid for

this command.
Correct the value and then re-execute the command.
name
REXX variable name
attribute-value
REXX variable value
YKD058E MSG
SC=36 RC=48
Some pairs in this group do

not support TCA services.
One or more devices in the 7700E storage system does

not support TrueCopy Asynchronous copy groups.
Check that the command can be executed on this copy
group, and then re-execute the command.
YKD099I TSO
YKDELETE command return

code=nnnn, reason
code=rrrr
The YKDELETE command terminated with the return

code nnnn and the reason code rrrr.
nnnn
Table 1-5 List of messages (message ID YKE0x)

Message ID
Message text
YKE000T TSO
RC=48
YKE001E MSG
SC=48 RC=48
GOTO() not supplied
Nothing is assigned to the GOTO parameter.
YKE001E TSO
RC=48
YKE001E MSG
SC=48 RC=48
YKE001E MSG
SC=48 RC=48
TIMEOUT() not supplied
Nothing is assigned to the TIMEOUT parameter.
For details, see the reason code in the YKE099I

Services.
Messages
1-33
Message ID
YKE001W MSG
SC=4 RC=4
Message text
Timeout limit has expired,

Processing is terminating because the timeout limit has
waiting for group copy-group expired.
to reach state state.
Correct the timeout value or check that the status to
be monitored is correctly specified. Use the YKQUERY
command to check the status of the copy pairs. If there
is a copy pair where a transition has not taken place,
the S-VOL of that copy pair might be ONLINE. Make it
OFFLINE and re-execute.
copy-group
Copy group ID
state
Status to be monitored
YKE002E MSG
SC=48 RC=48


period.
stem
YKE002E MSG
SC=48
YKE002E TSO
RC=48


stem
YKE002E MSG
SC=48 RC=48
TIMEOUT() value invalid
YKE003E MSG
SC=48 RC=48
GOTO value is invalid.
YKE003E MSG
SC=8 RC=8
Unexpected transition of
group copy-group pair index
to state state.
The value assigned to the TIMEOUT parameter is

invalid.
The value assigned to the GOTO parameter is invalid.
For the GOTO parameter, specify the DUPLEX, SUSPEND,
SIMPLEX, SUSPVS, HOLD or SWAPPING option.
The copy pair in the copy group entered an unexpected
status.
Check that the status to be monitored is correctly
specified.
copy-group
Copy group ID
index
Pair index
Before version 2.0: Copy pair number
Version 2.0 or later: Copy group number and copy
pair number
For details about identifying a volume with the
copy group number and the copy pair number, see
Identifying the volume to be processed on page
1-166
state
The status after the transition
1-34
Messages
Message ID
Message text
YKE008E MSG
SC=48

hexadecimal format.
YKE010E TSO
RC=40
REXX failure return

variable name

nnnn
YKE099I TSO
YKEWAIT command return

code=nnnn, reason
code=rrrr
The YKEWAIT command terminated with the return code

nnnn
Table 1-6 List of messages (message ID YKF0x)

Message ID
Message text
YKF000T TSO
RC=48
YKF001E TSO
RC=48
YKF001E MSG
SC=48 RC=48
YKF002E MSG
SC=48 RC=48


period.
For details, see the reason code in the YKF099I

Services.
stem
YKF002E TSO
RC=48


stem
YKF002E MSG
SC=48 RC=48

invalid.
YKF010E TSO
RC=40
REXX failure return

variable name

nnnn
Messages
1-35
Message ID
Message text
YKF050E MSG
SC=48 RC=48
(attribute-value)

name

this command.
name
REXX variable name
attribute-value
REXX variable value
YKF099I TSO
YKFREEZE command return

code=nnnn, reason
code=rrrr
The YKFREEZE command terminated with the return

nnnn
Table 1-7 List of messages (message ID YKG0x)

Message ID
Message text
YKG000T TSO
SC=48
Supplied parameters invalid.
Invalid parameters have been specified.
YKG001E TSO
RC=48
Unable to execute without

valid MSG() parameter.
Specify a valid MSG parameter.
YKG002E TSO
RC=48
MSG(stem) does not include

trailing "." character.

stem
YKG003E TSO
RC=52
Unable to update MSG(stem) An attempt to assign a value to a Message structure

in Caller's environment.
variable failed. The resulting value is displayed in
YKVSET result = result
result. This error can be caused by an invalid value
being specified for the MSG parameter.
stem
YKG004E MSG
SC=48 RC=48

valid STEM() parameter.
Specify a valid STEM parameter.
YKG005E MSG
SC=48 RC=48
STEM(stem) does not

include trailing "." character. period.
stem
YKG006E MSG
SC=48 RC=48

valid PREFIX() parameter.
Nothing or an invalid value is assigned to the PREFIX

parameter.
To correct the error, see the CLI command descriptions
in the Hitachi Business Continuity Manager Reference
Guide, and then re-execute the command.
1-36
Messages
Message ID
YKG008E MSG
SC=48 RC=48
Message text
valid SN() parameter.

An invalid value is assigned to the internal parameter
SN that indicates the storage system serial number
contained in the disk configuration definition file name.
Check the disk configuration definition file name.
YKG050W MSG
SC=4 RC=4
(file:rec#)
Unrecognized element
encountered: name
The system does not recognize the XML element name

that exists on the line with the line number identified
by rec# in the file identified by file.
Check the indicated line, and then identify the cause of
the problem by referring to information contained in
the XML document type definitions, in the Hitachi
Business Continuity Manager Reference Guide.
file
Name of the configuration file where the error was
detected
rec#
Number of the line in the file identified by file
where the error was detected
YKG051E MSG
SC=36 RC=36
(file:rec#)
End of file encountered in

comment.
XML input analysis detected a syntax error on the line

with the line number identified by rec# in the file
identified by file.
file
detected
rec#
YKG053W MSG
SC=4 RC=4
(file:rec#)
Unrecognized Version
attribute value: value
The system does not recognize the version attribute

value of the XML element that exists on the line with
the line number identified by rec# in the file identified
by file.
file
detected
rec#
YKG054E MSG
SC=36 RC=36
(file:rec#)
Unexpected termination of
element: name
The XML element name that exists on the line with the
line number identified by rec# in the file identified by
file has not been correctly created.
Messages
1-37
Message ID
Message text

file
detected
rec#
YKG074E MSG
SC=36 RC=36
(file:rec#)
Invalid "&" character

discovered in quoted string.
string
The & character string that exists on the line with the
file has not been correctly escaped.
See the description of Extensible Markup Language
(XML) 1.0 at http://www.w3.org.
file
detected
rec#
YKG075W MSG
SC=4 RC=4
(file:rec#)
Unrecognized Encoding
The system does not recognize the encoding attribute

by file.
file
detected
rec#
YKG076W MSG
SC=4 RC=4
(file:rec#)
Unrecognized attribute:
name = value
The system does not recognize the XML attribute that

exists on the line with the line number identified by
rec# in the file identified by file.
name
XML attribute name
value
XML attribute value
file
1-38
Messages
Message ID
Message text

detected
rec#
YKG077W MSG
SC=4 RC=4
(file:rec#)
APIInfo Level=level invalid.

Supported level is v.r.m.
The system does not recognize the Level attribute level

of the APIInfo element that exists on the line with the
file.
file
detected
rec#
v.r.m
API level
For details about this value, see the information
about the XML document type definitions in the
Hitachi Business Continuity Manager Reference
Guide.
YKG079E MSG
SC=44 RC=44
(result)
YKVSET program failure for:

name = value
An attempt to assign the value value to the variable

name failed with the result value identified by result.
This error can be caused by an invalid value being
specified for the STEM parameter.
YKG085E MSG
SC=40 RC=40
(file:rec#)
Unable to read configuration

file.
The configuration file could not be read, because the

record length is too long.
file
Name of the configuration file where the error
occurred
rec#
Number of the line in the file file where the error
was detected
YKG088E MSG
SC=40 RC=40
(file)
File Open error: dsstate.
An attempt to open the configuration file identified by

file failed.
dsstate
Status of the configuration file
file
Name of the configuration file in which the error
was detected
YKG089E MSG
SC=40 RC=40
(file)
File Close error: dsstate.
An attempt to close the configuration file identified by

file failed.
dsstate
Messages
1-39
Message ID
Message text

file
was detected
YKG090E MSG
SC=40 RC=40
(file)
File Allocation Failed:

dsstate.
An attempt to allocate the configuration file identified

by file failed.
dsstate
file
was detected
YKG091E MSG
SC=40 RC=40
(file)
File Deallocation Failed:

dsstate.
An attempt to deallocate the configuration file

identified by file failed.
dsstate
file
was detected
YKG092E MSG
SC=40 RC=40
(file)
File Read error: dsstate.
An attempt to read the configuration file identified by

file failed.
dsstate
file
was detected
YKG099I MSG
TSO
YKGETHDA command return

code=max-value,reason
code=reason-code.
The reading of the disk configuration definition file has

finished.
This message is issued when an invalid disk
configuration definition file is read in ISPF. If this
message cannot be output to the REXX structure, it is
output to the TSO/E terminal.
reason-code
Reason code for the returned max-value
max-value
Table 1-8 List of messages (message ID YKG2x - YKK10x)

Message ID
Message text
YKG201E MSG
SC=48 RC=48

valid name parameter.
Nothing or an invalid value is assigned to the

parameter identified by name.
YKG202E TSO
RC=48
"SYSAUTH". cannot be
specified in MSG()
parameter.
SYSAUTH. cannot be specified in the MSG parameter.

Specify a different name.
1-40
Messages
Message ID
Message text
YKG203E MSG
SC=48 RC=48
"SYSAUTH." cannot be
specified in STEM()
parameter.
SYSAUTH. cannot be specified for the STEM parameter.

YKG204E TSO
RC=48
name parameter is too long.
The parameter identified by name is too long.
YKG205E MSG
SC=48 RC=48
YKG241W MSG
SC=4 RC=4
(file:rec#)
The attribute attname is

already defined.
The XML attribute identified by attname has already

been defined.
Review the file name identified by file and the attname
value on the line with the line number identified by
rec#.
attname
XML attribute name
file
detected
rec#
YKG250E MSG
SC=36 RC=36
(file:rec#)
The value value of the

attribute name is an invalid
format.
The value value of the XML attribute name is in an

invalid format.
Correct the specification on the line with the line
number identified by rec# in the file identified by file.
file
detected
rec#
YKG251E MSG
SC=36 RC=36
(file:rec#)
name attribute missing.
The required XML attribute name is missing.

file
detected
rec#
YKG252E MSG
SC=36 RC=36
(file:rec#)
The attribute statements are The XML attribute description is invalid.

invalid.
file
detected
Messages
1-41
Message ID
Message text

rec#
YKG253E MSG
SC=36 RC=36
(file:rec#)
This kind of elements

element can't be defined
more than once.
The XML element element cannot be defined more than

once.
file
detected
rec#
YKG254E MSG
SC=36 RC=36
(file:rec#)
The value value of attribute

name is not match with
filename.
The value value of the XML attribute name does not

match the name in the file name.
file
detected
rec#
YKG255E MSG
SC=36 RC=36
(file:rec#)
The element name-1, for

which the value value was
specified for the attribute
name-2, was not found.
The XML element name-1 with the value value

specified for the XML attribute name-2 was not found.
Revise the specification on line number rec# in file.
file
was detected
rec#
Number of the line in file where the error was
detected
YKG271E MSG
SC=36 RC=36
(file:rec#)
The element name is

required, but no element
was found.
The required XML element name is missing.

file
detected
rec#
YKG273E MSG
SC=36 RC=36
(file:rec#)
The element statements are

invalid.
The XML element description is invalid.

file
1-42
Messages
Message ID
Message text

detected
rec#
YKG274E MSG
SC=36 RC=36
(file:rec#)
ETag name is mismatch. /

correct-ETag-name is
expected, but /incorrectETag-name is specified.
The specified ETag name /incorrect-ETag-name is not

the expected ETag name /correct-ETag-name.
file
detected
rec#
YKG275W MSG
SC=4 RC=4
(file:rec#)
Extra ETag is specified:

ETag-name
An extra ETag-name is specified.

file
detected
rec#
YKG276E MSG
SC=36 RC=36
(file:rec#)
The element name1 is not a

content of the element
name2.
The XML element identified by name2 contained the

XML element name1 that cannot be specified.
file
detected
rec#
YKG277E MSG
SC=36 RC=36
(file:rec#)
name element missing.
The XML element name is missing.

file
detected
rec#
YKG285E MSG
SC=36 RC=36
(file:rec#)
Serial Number HDASN is

required, but Serial Number
DDSN is found.
The disk device element's SerialNum must be the same

as the SerialNum value (HDASN) of the disk
Messages
1-43
Message ID
Message text

configuration element, but DDSN is defined for this
value.
file
detected
rec#
YKG286E MSG
SC=36 RC=36
(file:rec#)
Specify the local DADID of

the primary site for the
DAD() parameter.
A device address domain ID created by a Remote Scan

or NG Scan is specified.
Specify the local device address domain ID of the
primary site in the DAD parameter. For details about the
NG Scan, see the Hitachi Business Continuity Manager
User Guide.
file
detected
rec#
Number of the line where the error was detected in
the file identified by file
YKG290E MSG
SC=44 RC=44
(result)
YKVGET program failure for:

vn
An attempt to acquire the variable vn failed with the

result value identified by result. This error can be
caused by an invalid value being specified for the STEM
parameter.
YKG295E MSG
SC=44 RC=44
(file:rec#)
The element stack was

overflowed.
The internal routine encountered a shortage of work

space.
file
detected
rec#
YKG298E MSG
YKGETHDA encountered an
TSO SC=44
unexpected error.
RC=44 (detailedinfo)
An unexpected error has occurred.

This error might have occurred with another error.
If another error message was output at the same time
as this one, follow the instructions in that message to
fix the corresponding problem.
If no other error message was output, collect the
following materials and contact your Hitachi Data
Systems representative or authorized service provider:
1-44
The script from which this command was executed

(not necessary if this command was executed from
the ISPF panel).
Messages
Message ID
Message text
The ISPF log (not necessary if this command was

executed from a script).
The definition files operated on from the script or

ISPF panel (the copy group definition file, disk
configuration definition file, command device
definition file and route list definition file).
detailed-info
Information displayed to assist the Hitachi Data
Systems representative or authorized service
provider in resolving the problem.
YKH001I TSO
YKH2B completed.
RC=return-code
The YKH2B command terminated.

return-code
Return code of the YKH2B command:
0: The command ended successfully. One or more
copy group definition file was created.
4: One of the following occurred:
- The command ended successfully. No copy pairs
were detected within the range of the specified
device numbers.
- A copy group definition file was created, but
volume information not defined in the disk
configuration definition file for the site specified in
the DAD parameter was detected among copy pairs
within the range specified in the DEVN parameter.
change was detected in the I/O configuration when
the YKH2B command was executed without
specifying the HS parameter or the YKH2B
command was executed by specifying HS(CHECK).
storage system that does not support 2DC
configuration with HyperSwap and Universal
Replicator was detected.
8: An I/O error occurred with a volume within the
scan range. Copy group definition files were
created for the volumes that were successfully
detected.
44: The processing was canceled due to an error.
The copy group definition file was not created.
48: The command ended due to an invalid
parameter.
YKH002I TSO
No copy pair was discovered. No copy pairs were detected within the specified range.
Check the operating range and status of the copy pair
that you want to acquire, and execute the YKH2B
command again. If the copy pair status is SIMPLEX, the
YKH2B command will not detect the copy pair. In
addition, if you execute the YKH2B command without
specifying the HS parameter or execute the YKH2B by
Messages
1-45
Message ID
Message text

specifying HS(CHECK) while HyperSwap is disabled,
copy pairs cannot be detected.
YKH100E TSO
Missing or invalid parameter: Check the following, and then re-execute the
parameter-name
command:
Make sure that the required parameter indicated

by parameter-name was specified.
Make sure that the value specified for the required

parameter indicated by parameter-name is valid.
parameter-name
Name of the invalid or missing parameter
YKH101E TSO
YKH102E TSO

program.

execution. Cmd=info
An error occurred during execution of the YKH2B

command.
msg=message-text:
See the explanation corresponding to the message ID

of the error message indicated by message-text and
take appropriate action. Also see the additional
information indicated by message-value and messageseverity and take appropriate action. If the problem is
not resolved, contact your Hitachi Data Systems
info
message-text
Error message
message-value
displayed.
message-severity
displayed.
Depending on the length of the error messages, they
might extend over several lines.
YKH200W TSO
No information was acquired

for DEVN=Devn

with the device number indicated by Devn. There might
not be a volume for the specified device number.
If a volume does exist for the specified device number,
check the channel settings.
Devn
Device number assigned to the volume from which
no copy pair information was acquired
1-46
Messages
Message ID
YKH201W TSO
Message text
No I/O paths are available
for the specified devices.
DEVN=Devn

to which the device number Devn was assigned
because no I/O paths are available.
Verify the I/O path settings.
Devn
The device number of the volume on which
information acquisition was skipped
YKH202W TSO

volume information.
DEVN=Devn,SN=SerialNum,
CU=CU#,CCA=CCA#
A P-VOL not defined in the disk configuration definition

file was included among the PPRC copy pairs detected
by the YKH2B command.
Check whether this P-VOL is defined in the disk
Devn
The device number of the detected undefined
volume
SerialNum
undefined volume
CU#
volume
CCA#
YKH203W TSO
Unable to resolve secondary

volume information.
SN=SerialNum,CU=CU#,CC
A=CCA#
An S-VOL not defined in the disk configuration

definition file was included among the PPRC copy pairs
detected by the YKH2B command.
Check whether the detected S-VOL is defined in the
disk configuration definition file.
SerialNum
undefined volume
CU#
volume
CCA#
YKH204W TSO
change was detected.
DEVN=device-number
A dynamic change was detected in an I/O configuration

definition when the YKH2B command was executed
either without the HS parameter or with HS(CHECK).
Check the status of the device targeted by the YKH2B
command, correct any errors in the configuration or
execution conditions (such as the parameter setting or
the times at which the command has been executed),
and then re-execute the command.
device-number
Messages
1-47
Message ID
Message text

definition
YKH205W TSO
This copygroup does not

support LinkageOption=HS.
SUPFNC=SUPFnc
TrueCopy with the HyperSwap attribute cannot be used

in this storage system because 2DC configuration with
HyperSwap and Universal Replicator is not supported.
Use a device# in which 2DC configuration with
HyperSwap and Universal Replicator can be used. Also,
if scanning was not performed after the storage system
microcode was updated, perform a scan.
SUPFnc (hexadecimal number)
Value for the version (minimum value) of the
storage system support function used in the copy
group
#: The storage systems for which 2DC configurations
with HyperSwap and Universal Replicator can be used
are USP Vs with a storage system support function
version of X'22' or later.
YKJ000E TSO
RC=48


name
Parameter name
YKJ001E TSO
RC=48

name
Parameter name
YKJ002E TSO
RC=48

program.
YKJ051E TSO
RC=32

execution. Cmd= info
An error occurred during execution of the YKIMPORT

command or YKEXPORT command.
msg= message-text:
See the error message message-text and resolve the

problem. Also see the additional information indicated
by message-value and message-severity and take
appropriate action.
If the acquisition of information denoted by messagetext, message-value, or message-severity fails, FATAL

is displayed instead of the information that should be
acquired. The reasons for FATAL to be displayed include
an insufficient region size. Review the current region
size, and then retry executing the command.
If the problem is not resolved, contact Technical
Support for assistance.
info
message-text
Error message
message-value
1-48
Messages
Message ID
Message text

displayed.
message-severity
displayed.
Depending on the length of the error messages, they
might extend over several lines.
YKJ099I TSO
RC=0
cmd command completed.

RC= return-code
The command identified by cmd has ended with a

return code identified by return-code.
cmd
Command name
YKJ100E TSO
RC=32

An error occurred while reading data from or writing
reading/writing configuration data to the configuration file.
file: file
file
detected
YKJ101I TSO
RC=4
No copy pair is defined in

specified Copy Group
definition: file
No copy pair is defined for the specified copy group. No

data was written in the CSV file.
file
Name of the specified copy group definition file
YKJ102E TSO
RC=32
name is not specified in

Copy Group definition
specified by BASEGROUP.
The copy group definition file specified by the

BASEGROUP parameter does not include the element
identified by name.
Set the necessary elements in the copy group definition
file that is to be used as the base, and then retry.
name
Name of an element in the copy group definition
file
YKJ150E TSO
RC=40
Error reported during file

input/output. EXECIO RC=
n: dd-name
Processing ended due to the EXECIO TSO/E REXX

command failure (return code = n). For details, see the
TSO/E REXX User's Guide.
The probable causes are as follows:
No CSV file is assigned to the dd name required for

the command.
The dataset format of the CSV file is not

supported.
dd-name
dd name of the CSV file where the error was
detected
YKJ151E TSO
RC=40
File format is invalid:

DSORG= XX. DSORG must
be PS: dd-name
The dataset format of the CSV file identified by ddname is invalid.

Delete the current CSV file and create a CSV file that is
in the correct dataset format.
Messages
1-49
Message ID
Message text

For details about the CSV file dataset format, see the
Hitachi Business Continuity Manager Reference Guide.
XX
DSORG of the CSV file where the error was
detected
dd-name
detected
YKJ152E TSO
RC=40
Failed to operate csv file:

dd-name: dsstate
The CSV file operation will stop because an error

occurred when using the CSV file.
Refer to the information output in the message to
review the environment, and then update the CSV file
again. For details about troubleshooting, see the
accompanying message and the Hitachi Business
Continuity Manager User Guide.
dd-name
detected
dsstate
CSV file status
EXTENT= extent
The number of extents of the dataset that is
currently allocated
extent indicates the number of extents that are
allocated to the dataset indicated by dd-name.
CANNOT GET DSSTATE, reason code= nnnn

The dataset information cannot be obtained, or the
CSV file is not allocated.
nnnn (decimal (base 10) number) indicates a
reason code (maintenance information).
YKJ200E TSO
RC=32
name is not specified in Pair

information CSV file: ddname: rec#
The item identified by name is not included in the pair

information CSV file.
name
Name of the item in the pair information CSV file
dd-name
detected
rec#
Number of the line in the file identified by dd-name
YKJ201E TSO
RC=32
The value value of name in

Pair information CSV file is
invalid: dd-name: rec#
The value assigned to name in the pair information

CSV file is in an invalid format.
value
Value assigned to the item identified by name
name
Name of the item in the pair information CSV file
1-50
Messages
Message ID
Message text

dd-name
detected
rec#
YKJ202I TSO
RC=4
No copy pair is defined in

specified Pair information
CSV file.
No copy pair is defined in the pair information CSV file.

No data was written in the copy group definition file.
YKJ203E TSO
RC=32
The number of items

specified for a line in Pair
information CSV file is
The number of items specified on one line of the pair

information CSV file is incorrect.
dd-name
detected
rec#
YKJ204E TSO
RC=32
Primary volume is not

specified in Pair information
CSV file: dd-name: rec#
No P-VOL is specified in the pair information CSV file.

dd-name
detected
rec#
YKJ205E TSO
RC=32
Secondary volume is not

specified in Pair information
No S-VOL is specified in the pair information CSV file.

dd-name
detected
rec#
YKJ206E TSO
RC=32
The specified volume does

not exist in the disk
configuration definition file:
dd-name: rec#: device
The specified volume does not exist in the disk

dd-name
detected
rec#
device
One of the following is displayed. If both are
specified, the device number is displayed.
Device number
Storage system serial number, control unit

number, and command control address number
Messages
1-51
Message ID
Message text

The display format is storage-system-serialnumber:CU-number:CCA-number.
YKJ207W TSO
RC=8
Inconsistencies exist among

the values used to specify
the primary volume: ddname: rec#
The P-VOL specified with the device number differs

from the P-VOL specified with the storage system serial
number, control unit number, and command control
address number.
Although the copy group definition file was created, the
settings therein might contain an error.
dd-name
detected
rec#
YKJ208W TSO
RC=8
Inconsistencies exist among

the values used to specify
the secondary volume: ddname: rec#
The S-VOL specified with the device number differs

from the S-VOL specified with the storage system serial
number, control unit number, and command control
address number.
Although the copy group definition file was created, the
settings therein might contain an error.
dd-name
detected
rec#
YKJ209E TSO
RC=32
Sub C/T group ID cannot be

specified for a copy-type
Copy Group: dd-name: rec#
A sub consistency group ID is specified for a copy

group of the copy type identified by copy-type. No sub
consistency group ID can be specified if the copy type
is ShadowImage, TrueCopy, or TrueCopy
Asynchronous.
copy-type
Copy type
dd-name
detected
rec#
YKJ210E TSO
RC=32
The value specified for

No volume exists in the range of the Number-Of-Pairs
Number-of-Pairs exceeds the repetitions.
range in which volumes
Number-Of-Pairs
exist: Number-Of-Pairs: ddNumber of pair repetitions
name: rec#
dd-name
detected
rec#
1-52
Messages
Message ID
Message text

YKJ211E TSO
RC=32
PVOL & SVOL of SI pair is in A copy pair, which has a P-VOL storage system serial
the different storage system: number and an S-VOL storage system serial number
dd-name: rec#
that do not match, was found in a copy group of copy
type ShadowImage.
dd-name
detected
rec#
YKJ212E TSO
RC=32
A specific combination of a
storage system serial
number and a C/T group ID
is used for multiple UR Copy
Groups: dd-name: rec#
The combination of the copy groups is one of the

following:
The serial numbers of the primary site storage

systems are the same; the serial numbers of the
secondary site storage systems are different; and
copy pairs with the same consistency group ID
exist.
The serial numbers of the primary site storage

systems are different; the serial numbers of the
secondary site storage systems are the same; and
copy pairs with the same sub consistency group ID
exist.
If the copy type is Universal Replicator, these

combinations are not supported.
dd-name
detected
rec#
YKJ213E TSO
RC=32
Secondary volume is already

specified in another copy
pair as a secondary device:
dd-name: rec#
The volume specified as the S-VOL is also specified as

the S-VOL for other copy pairs. The same volume
cannot be specified as the S-VOL for multiple copy
pairs.
dd-name
detected
rec#
YKJ214W TSO
RC=8
A copy pair capacity check

could not be performed
because the capacity of a
volume could not be
acquired.
A copy pair capacity check could not be performed

because the capacity of a volume could not be
acquired. A capacity check cannot be performed in
either of the following cases:
When a volume capacity has not been acquired

during a Local Scan, Remote Scan, or NG Scan.
Messages
1-53
Message ID
Message text
When a volume is in any of the storage systems

below and a Remote Scan or NG Scan has been
performed on the volume. In this case, the
capacity of the volume cannot be acquired.
- Lightning 9900V series
- USP
- USP V
A copy group definition file was created, but the

settings might contain incorrect information.
YKJ215E TSO
RC=32
The capacities of the copy

pair volumes are different:
dd-name: rec#
The capacities of the copy pair volumes are different. A

copy pair whose P-VOL and S-VOL capacities are
different cannot be defined.
To create a copy pair whose P-VOL and S-VOL
capacities are different for migration, specify NOCHECK
for the CAPACITY parameter, and execute the YKIMPORT
command. For details, see Hitachi Business Continuity
dd-name
The dd name of the CSV file where the error was
detected
rec#
Number of the line in the file indicated by dd-name
YKJ250E TSO
RC=32
name is not specified in

EXCTG information CSV file:
dd-name: rec#
No value is assigned to the item identified by name in

the EXCTG information CSV file.
name
Name of the item in the EXCTG information CSV
file
dd-name
detected
rec#
YKJ251E TSO
RC=32

EXCTG information CSV file
is invalid: dd-name: rec#
The format of the value assigned to name in the EXCTG

information CSV file is invalid.
value
Value assigned to the item identified by name
name
Name of the item in the EXCTG information CSV
file
dd-name
detected
rec#
1-54
Messages
Message ID
YKJ252E TSO
RC=32
Message text
The number of items
specified for a line in EXCTG

The number of items specified on one line of the
EXCTG information CSV file is incorrect.
dd-name
detected
rec#
YKJ253E TSO
RC=32
YKJ254E TSO
RC=32
Multiple EXCTG IDs are

specified in EXCTG
information CSV file: ddname
Multiple EXCTG IDs are specified in the EXCTG

dd-name
detected
The specified supervisor DKC The supervisor disk controller or arbitration command
or arbitration command
device specification is incorrect.
device is invalid: dd-name:
dd-name
rec#
detected
rec#
If the EXCTG information CSV file does not include
a line that specifies the supervisor disk controller,
nothing is displayed for rec#.
YKJ255E TSO
RC=32
A Copy Group that does not

have any corresponding
entry in EXCTG information
CSV file is found: dd-name
The EXCTG information CSV file includes no entry (line)

corresponding to the entry (line) specified in the pair
dd-name
detected
YKJ256E TSO
RC=32
This entry does not have any

corresponding Copy Group in
Pair information CSV file:
dd-name: rec#
The pair information CSV file includes no entry (line)

corresponding to the entry (line) specified in the
EXCTG information CSV file.
dd-name
detected
rec#
YKJ257E TSO
RC=32
Multiple entries that specify

the same Copy Group are
defined in EXCTG
The EXCTG information CSV file contains multiple

entries (lines) that specify the same copy group.
dd-name
detected
rec#
Messages
1-55
Message ID
Message text

YKJ258E TSO
RC=32
The EXCTG information is

The following entries specified as EXCTG information
inconsistent: dd-name: rec# are contradictory:
EXCTG ID
Supervisor disk controller
Arbitration command device
It is likely that different combinations of copy directions

(forward direction only, reverse direction only, or
forward and reverse directions) exist in the EXCTG
dd-name
detected
rec#
YKJ270E TSO
RC=32
name is not specified in CTG

No value is assigned to name in the CTG information

CSV file.
name
Name of an item in the CTG information CSV file
dd-name
DD name of the CSV file where the error was
detected
rec#
Line number in the file dd-name where the error
was detected
YKJ271E TSO
RC=32

CTG information CSV file is
The value assigned to name in the CTG information

CSV file is invalid.
value
Value assigned to name
name
Name of an item in the CTG information CSV file
dd-name
detected
rec#
was detected
YKJ272E TSO
RC=32
The number of items

specified for a line in CTG
An invalid number of items was specified on one line in

the CTG information CSV file.
dd-name
detected
rec#
1-56
Messages
Message ID
Message text

was detected
YKJ273E TSO
RC=32
This entry does not have any

corresponding Copy Group in
Pair information CSV file:
dd-name: rec#
The pair information CSV file includes no entries (lines)

corresponding to the entries (lines) specified in the
CTG information CSV file.
dd-name
detected
rec#
was detected
YKJ274E TSO
RC=32
Multiple entries that specify

the same Copy Group are
defined in CTG information
The CTG information CSV file contains multiple entries

(lines) in which the same copy group is specified.
dd-name
detected
rec#
was detected
YKK001I PRT
YKINSCHK completed.
RC=return-code, V/
R=versionnumber,execution-date
The YKINSCHK command terminated.

return-code
Return code of the YKINSCHK command
version-number
Current Business Continuity Manager version
number
execution-date
Time at which the YKINSCHK command was
executed
The time is indicated in the format YYYY/MM/DD
HH:MM:SS
YKK101E TSO
RC=32
Failed to get security setting

information,service=servicename,code=code1,code2.
Security setting information could not be acquired.

service-name
Name of the OS service that encountered an error
code1
Return code of the OS service that encountered an
error
code2
Reason code of the OS service that encountered an
error
If no reason code is returned for an OS service,
code2 is 0.
YKK102E TSO
RC=32
Failed to get user SVC

routine
information,service=servicename,code=code1,code2.
User SVC information could not be acquired.

service-name
code1
Messages
1-57
Message ID
Message text

error
code2
error
code2 is 0.
YKK103E TSO
RC=32
Acquisition of host ID
settings
failed,service=servicename,code=code1,code2.
Host ID setting information could not be acquired.

service-name
code1
error
code2
error
code2 is 0.
Table 1-9 List of messages (message ID YKL0x)

Message ID
Message text
YKL000T TSO
SC=48
YKL001E TSO
RC=48

YKL002E TSO
RC=48

trailing "." character.

stem
YKL003E TSO
RC=52
Unable to update MSG(stem) An attempt to assign a value to a Message structure

variable failed. The resulting value is displayed in
result. This error can be caused by an invalid value
being specified for the MSG parameter.
stem
YKL004E MSG
SC=48 RC=48

YKL005E MSG
SC=48 RC=48
STEM(stem) does not

stem
YKL006E MSG
SC=48 RC=48
1-58

valid PREFIX parameter.
Specify a valid PREFIX parameter.
Messages
Message ID
Message text
YKL007E MSG
SC=48 RC=48

valid GROUP parameter.
Specify a valid GROUP parameter.
YKL050W MSG
SC=4 RC=4
(file:rec#)
Unrecognized element
encountered: name

number identified by rec# in the file identified by file. If
the error still exists, contact HDS Technical Support for
assistance.
name
XML element name
file
detected
rec#
YKL051E MSG
SC=36 RC=36
(file:rec#)
End of file encountered in

comment.
Check that the XML comments are balanced. Be careful

to ensure that any XML comments will not be nested. If
the error still exists, contact HDS Technical Support for
assistance.
file
detected
rec#
YKL053W MSG
SC=4 RC=4
(file:rec#)
Unrecognized Version
The system does not recognize the version attribute

by file.
file
detected
rec#
YKL054E MSG
SC=36 RC=4
(file:rec#)
Unexpected termination of
element: name
The XML element name that exists on the line with the
file has not been correctly created.
file
detected
Messages
1-59
Message ID
Message text

rec#
YKL074E MSG
SC=36 RC=36
(file:rec#)
Invalid "&" character

discovered in quoted string.
string
An invalid entity reference was found on the line with

by file.
Use only defined entity references as specified in
Extensible Markup Language (XML) 1.0 at http://
www.w3.org.
file
detected
rec#
YKL075W MSG
SC=4 RC=4
(file:rec#)
Unrecognized Encoding
The system does not recognize the encoding attribute

by file.
file
detected
rec#
YKL076W MSG
SC=4 RC=4
(file:rec#)
Unrecognized attribute:
name = value
The system does not recognize the XML attribute that

exists on the line with the line number identified by
rec# in the file identified by file.
name
XML attribute name
value
XML attribute value
file
detected
rec#
1-60
Messages
Message ID
YKL077W MSG
SC=4 RC=4
(file:rec#)
Message text
APIInfo Level=level invalid.
Supported level is v.r.m.

The system does not recognize the Level attribute level
of the APIInfo element that exists on the line with the
file.
file
detected
rec#
v.r.m
API level
For details about this value, see the information
about the XML document type definitions in the
Guide.
YKL079E MSG
SC=44 RC=44
(result)

name = value

name failed with the result value identified by result.
This error can be caused by an invalid value being
specified for the STEM parameter.
YKL080E MSG
SC=36 RC=36
(file:rec#)
More than two DiskDevice

Elements in CopyPair.
Only two copy pair elements are allowed: the first

element for the P-VOL and the second element for the
S-VOL.
Check the line with the line number identified by rec#
in the file identified by file, and then identify the cause
of the problem by referring to information contained in
file
detected
rec#
YKL081W MSG
SC=16 RC=16
(pair-index)

device address.
The YKLOAD program failed to resolve the unit number

(device address) of the P-VOL in the specified
CopyPair. For configuration definition, this process uses
the Host Discovered Array object in the primary device
address domain. For other purposes, the current host
device address domain is used. The situation
represented by this message is not always fatal. Some
CLI commands, such as YKSUSPND, can be successfully
executed by using only the S-VOL unit address.
pair-index
Messages
1-61
Message ID
Message text

See the pair index description in the explanation of
the YKE003E message.
YKL082W MSG
SC=8 RC=8
(pair-index)
Unable to resolve secondary

device address.
The YKLOAD program failed to resolve the unit number

(device address) of the S-VOL in the specified
CopyPair. For configuration definition, this process uses
the Host Discovered Array object in the secondary
device address domain. For other purposes, the current
host device address domain is used. The situation
represented by this message is not always fatal. Many
CLI commands can be successfully executed by using
only the P-VOL unit address.
pair-index
YKL083W MSG
SC=12 RC=12
(pair-index)
Unable to resolve volume

serial number.
The YKLOAD program failed to resolve the volume serial

number of the P-VOL in the specified CopyPair. For
configuration definition, this process uses the Host
Discovered Array object in the primary device address
domain. For other purposes, the current host device
address domain is used. The situation represented by
this message is not always fatal. At present, the
volume serial number is used only for display and
warning.
pair-index
YKL085E MSG
SC=40 RC=40
(file:rec#)
Unable to read configuration

file.
The configuration file could not be read, because the

record length is too long.
file
detected
rec#
Number of the line in the file file where the error
was detected
YKL087E MSG
SC=40 RC=40
(file)
The license information

dataset could not be read.
YKL088E MSG
SC=40 RC=40
(file)
File Open error: dsstate.
An attempt to read the license information dataset has

failed.
Check that the dataset name of the license key dataset
is correct, and that the license key dataset was created
correctly. If necessary, transfer the license key file
again and recreate the license key dataset.
An attempt to open the configuration file identified by
file failed.
dsstate
file
was detected
1-62
Messages
Message ID
YKL089E MSG
SC=40 RC=40
(file)
Message text
File Close error: dsstate.

An attempt to close the configuration file identified by
file failed.
dsstate
file
was detected
YKL090E MSG
SC=40 RC=40
(file)
File Allocation Failed:

dsstate.
An attempt to allocate the configuration file identified

by file failed.
Verify that the configuration file identified by file is
correctly created.
dsstate
file
was detected
YKL091E MSG
SC=40 RC=40
(file)
File Deallocation Failed:

dsstate.
An attempt to deallocate the configuration file

identified by file failed.
dsstate
file
was detected
YKL092E MSG
SC=40 RC=40
(file)
File Read error: dsstate.
An attempt to read the configuration file identified by

file failed.
dsstate
file
was detected
YKL099I MSG
TSO
process-name command
return code=max-value,
reason code=reason-code.
If process-name is YKLOAD:
The YKLOAD command has finished. This message
is always displayed.
If process-name is YKGETRUT:
The route list definition file and the command
device definition file have been read. This message
is output when an invalid route list definition file or
invalid command device definition file is read in
ISPF.
reason-code
Reason code for the returned max-value
max-value
Messages
1-63
Table 1-10 List of messages (message ID YKL2x - YKL4x)

Message ID
Message text
YKL201E MSG
SC=48 RC=48


YKL202E TSO
RC=48
"SYSAUTH". cannot be
specified in MSG()
parameter.
SYSAUTH. cannot be specified in the MSG parameter.

YKL203E MSG
SC=48 RC=48
"SYSAUTH." cannot be
specified in STEM()
parameter.
SYSAUTH. cannot be specified in the STEM parameter.

YKL204E TSO
RC=48
YKL205E MSG
SC=48 RC=48
YKL206E MSG
SC=48 RC=48
Route parameter is allowed

only on 1st call of YKLOAD
The ROUTE parameter is allowed only on the first call of

the YKLOAD command.
YKL241W MSG
SC=4 RC=4
(file:rec#)
The attribute attname is

already defined.
The XML attribute identified by attname has already

been defined.
Review the file name identified by file and the attname
value on the line with the line number identified by
rec#.
attname
XML attribute name
file
detected
rec#
YKL250E MSG
SC=36 RC=36
(file:rec#)

attribute name is an invalid
format.
The value value of the XML attribute name is in an

invalid format.
file
detected
rec#
YKL251E MSG
SC=36 RC=36
(file:rec#)
name attribute missing.
The required XML attribute name is missing.

file
detected
rec#
1-64
Messages
Message ID
Message text

YKL252E MSG
SC=36 RC=36
(file:rec#)
The attribute statements are The XML attribute description is invalid.

invalid.
file
detected
rec#
YKL253E MSG
SC=36 RC=36
(file:rec#)
This kind of elements

element can't be defined
more than once.
The XML element element is defined more than once.

file
detected
rec#
YKL254E MSG
SC=36 RC=36
(file:rec#)
The value value of attribute

name is not match with
filename.
The value value of the XML attribute name does not

match the name in the file name.
number identified by rec# in the file identified by file,
or correct the file name.
file
detected
rec#
YKL255E MSG
SC=36 RC=36
(file:rec#)
The element name-1, for

which the value value was
specified for the attribute
name-2, was not found.
The XML element name-1 with the value value

specified for the XML attribute name-2 was not found.
file
was detected
rec#
Number of the line in file where the error was
detected
YKL262E MSG
SC=36 RC=36
name is not specified or

invalid.
The system symbol identified by name has not been

defined or has been assigned an invalid value.
If name is YKCMDIF:
Messages
1-65
Message ID
Message text

The host ID that identifies the host on which
Business Continuity Manager is running is invalid
or missing. Define YKCMDIF correctly.
For details about the host ID definition (YKCMDIF),
see the Hitachi Business Continuity Manager
Installation Guide.
YKL271E MSG
SC=36 RC=36
(file:rec#)
The element name is

required, but no element
was found.
The required XML element name is missing.

file
detected
rec#
YKL273E MSG
SC=36 RC=36
(file:rec#)
The element statements are

invalid.
The XML element description is invalid.

file
detected
rec#
YKL274E MSG
SC=36 RC=36
(file:rec#)
ETag name is mismatch. /

correct-ETag-name is
expected, but /incorrectETag-name is specified.
The specified ETag name /incorrect-ETag-name is not

the expected ETag name /correct-ETag-name.
file
detected
rec#
YKL275W MSG
SC=4 RC=4
(file:rec#)
Extra ETag is specified:

Etag-name
An extra Etag-name is specified.

file
detected
rec#
YKL276E MSG
SC=36 RC=36
(file:rec#)
1-66
The element name1 is not a

content of the element
name2.
The XML element identified by name2 contained the

XML element name1 that cannot be specified.
Messages
Message ID
Message text

file
detected
rec#
YKL277E MSG
SC=36 RC=36
(file:rec#)
name element missing.
The XML element name is missing.

file
detected
rec#
YKL280E MSG
SC=36 RC=36
(file)
No command devices were

found.
No command devices were found.

Correct the route definition in the route list definition
file shown in file.
file
detected
YKL281E MSG
SC=36 RC=36
(file:rec#)
No command devices are

defined for routes that issue
remote commands or for
route labels.
No command device was found that is defined in the

route for remote command issuance or with the
specified route label.
file identified by file.
file
detected
rec#
YKL282E MSG
SC=36 RC=36
(file)
The route label specified for

the ROUTE parameter has
not been defined.
The route label specified for the ROUTE parameter is not

defined.
file identified by file.
file
detected
YKL283E MSG
SC=36 RC=36
(file)
A route label is not specified

for the ROUTE parameter,
even though a route label is
defined for all the command
devices.
An attempt was made to load command device lines for

which no route label is specified because no route label
is specified for the ROUTE parameter. However, route
labels are defined for all the command devices in the
route list definition file shown in file.
Messages
1-67
Message ID
Message text

Set an appropriate route label for the ROUTE parameter
of the YKLOAD command, or use the Edit Attribute panel
to delete the route labels of command devices in the
route list definition file shown in file.
file
detected
YKL284E MSG
SC=36 RC=36
(file:rec#)
PVOL & SVOL of SI pair is in In a file for a copy group of the ShadowImage copy
the different storage system. type, a copy pair has been discovered for which the
storage system serial numbers of the P-VOL and S-VOL
do not match.
Correct the line with the line number identified by rec#
in the file identified by file.
file
detected
rec#
YKL290E MSG
SC=44 RC=44
(result)
YKVGET program failure for:

vn

caused by an invalid value being specified for the STEM
parameter.
YKL291E MSG
SC=36 RC=36
function-name is not
licensed for use on this
system.
The license key for the function identified by functionname has not been installed, has expired, or is not
correctly recognized.
Check whether the license key is available for this
version.
If function-name is This product:
Business Continuity Manager commands cannot be
used because the Business Continuity Manager
license key has not been installed.
If function-name is UR 4x4 Extended CTG:
The function for preserving consistency on an
EXCTG basis cannot be used because the license
key required for a 4x4 configuration has not been
installed.
YKL292E MSG
CON SC=36
RC=36
The expiration date for your

license key(function).
The license (function) has expired.

To continue using this product, you need a permanent
license.
1-68
Messages
Message ID
YKL293W MSG
CON SC=0 RC=0
Message text
Your function license will
expire in n day(s).

The license (function) will expire in n days.
YKL295E MSG
SC=44 RC=44
(file:rec#)
The element stack was

overflowed.
The internal routine encountered a shortage of work

space.
file
detected
rec#
YKL298E MSG
CLI-name encountered an
TSO SC=44
unexpected error.
RC=44 (detailedinfo)
An unexpected error has occurred. This error might

have occurred with another error.

the ISPF panel).

The definition files operated on from the script or

ISPF panel (the copy group definition file, disk
CLI-name
The name of the executed CLI command
detailed-info
Detailed information displayed to assist your
Hitachi Data Systems representative or authorized
service provider in resolving the problem
YKL419E MSG
SC=48 RC=48
The values of attribute1 and

attribute2 conflict.
The values attribute1 and attribute2 conflict.

Make sure that both of these values are valid, and then
retry the operation.
attribute1
Attribute name 1 included in the copy group
definition
Messages
1-69
Message ID
Message text

attribute2
Attribute name 2 included in the copy group
definition
Table 1-11 List of messages (message ID YKM0x)

Message ID
Message text
YKM000T TSO
RC=48
YKM001E TSO
RC=48
YKM001E MSG
SC=48 RC=48
YKM002E MSG
SC=48 RC=48


period.
For details, see the reason code in the YKM099I

Services.
stem
YKM002E MSG
SC=48
YKM002E TSO


stem
YKM008E MSG
SC=48

hexadecimal format.
YKM010E TSO
RC=40
REXX failure return

variable name

nnnn
YKM011E ISPF
This device number msgdevn The device number indicated by msgdevn has not been
has not been discovered on
scanned in the device address domain indicated by
msgdad.
msgdad.
msgdevn
Device number
msgdad
Device address domain
YKM012E ISPF
1-70
The End Devn value must

not be lower than the Start
Devn
The End device number is lower than the Start device

number.
Messages
Message ID
Message text
YKM014E ISPF
This Copy Group ID is

already defined. Choose a
different ID.
The copy group ID is already defined. Please use

another ID.
YKM015I LOG
RC:nn CMD:command
The command terminated with the return code nnnn

after issuing the command identified by command.
nn
Return code of this command
YKM016W LOG
SEV:nn TEXT:message-text
VALUE:message-value
The command output the nn as Severity, message-text

as message ID/message text, and message-value as
additional information, and then terminated.
nn
Value set for Severity in the Message structure
message-text
Value set for Text in the Message structure
message-value
Value set for Value in the Message structure
YKM017I LOG
message-text
The console message message-text was output when

issuing the command.
YKM018E ISPF
A Consistency Group ID (C/T To define a TrueCopy Asynchronous copy group, a

ID) is required for TrueCopy consistency group ID is required.
Async Copy Group definition.
YKM020E ISPF
Please supply the required

information.
Enter the required information.
YKM021E ISPF
Check either Device num or

Volser
Select either Device Num or Volser.
YKM022E ISPF
The End Volser value must

not be lower than the Start
Volser
The End Volser value is lower than the Start Volser

value.
YKM023E ISPF
Invalid value
The value is invalid.
YKM024E ISPF
Choose any one
Please choose one.
YKM025E ISPF
C/T ID cannot be added to a

CopyGroup Container
without C/T ID.
You cannot add a copy group to a copy group container

if no consistency group ID is specified for the copy
group.
YKM026E ISPF
The secondary device sdevn

is already paired to primary
device pdevn.
The secondary device indicated by sdevn is already

defined as a copy pair in the primary device indicated
by pdevn.
sdevn
pdevn
YKM027E ISPF
The primary device pdevn

and secondary device sdevn
are on different storage
system.
The primary device pdevn and the secondary device

sdevn are on different storage system.
pdevn
Messages
1-71
Message ID
Message text

sdevn
YKM030E ISPF
File not found.
The file was not found.
YKM031E ISPF
Refresh SMS key is not

available in case of Copy
Group Creation.
The Refresh SMS key is not available while a new copy

group is being created.
YKM032E ISPF
Invalid operation.
The operation is invalid.
YKM033E ISPF
Can not edit.
This cannot be edited.
YKM034E ISPF
Press F10 key and select C/T Press the F10 key, and then select a consistency group
ID.
ID.
YKM035E ISPF
inputfld is not specified or

invalid.
No value is specified in inputfld, or the specified value

is invalid.
inputfld
The attribute name or the input field name
YKM036E ISPF
Specified APID is defined to

another DADID.
The APID you specified is already defined in another

device address domain ID.
YKM037E ISPF
Changing a local Device

Address Domain ID is not
allowed.
Changing a local device address domain ID is not

allowed.
YKM038E ISPF
Specified DEVN is not found.
The device number you specified was not found.
YKM039E ISPF
Specified device is not

command device because
APID is not available.
The device you specified is not a command device

because the APID cannot be used.
YKM040E ISPF
A Consistency Group ID (C/T For the Universal Replicator copy group definition, you
ID,sub C/T ID) is required
need to specify a consistency group ID and a sub
for Universal Replicator Copy consistency group ID.
Group definition.
YKM041E ISPF
A sub Consistency Group ID

cannot be specified for
SI/TC/TCA Copy Group
definition.
For the ShadowImage/TrueCopy/TrueCopy

Asynchronous copy group definition, you cannot specify
a sub consistency group ID.
YKM042E ISPF
This Consistency Group ID

(C/T ID,sub C/T ID) is
already defined. Choose a
different ID.
This consistency group ID is already defined. Please

choose a different ID.
YKM043E ISPF
A Mirror ID is required for

Universal Replicator Copy
Group definition.
For the Universal Replicator copy group definition, you

need to specify a mirror ID.
YKM044E ISPF
This Path Set ID is already

defined.
This path set ID is already defined.
YKM045E ISPF
Physical path (priport

The physical path is already defined as a logical path.
secport) is already defined in priport
this logical path.
The primary port you specified
secport
1-72
Messages
Message ID
Message text

The secondary port you specified
YKM046E ISPF
The end CU/CCA value must

not be lower than the start
CU/CCA.
The end control unit/command control address value is

lower than the start control unit/command control
address value.
YKM047E ISPF
Processing to insert or edit a

storage system was denied
because the storage system
has already been discovered
by the selected DADID.
A storage system cannot be inserted into, or edited in a

route because the storage system has already been
scanned via the specified device address domain ID.
YKM048E ISPF
You cannot perform a device

scan because a remote
DADID or Non Gen'ed
DADID was specified as the
local DADID in the Set
Defaults panel.
Devices cannot be scanned because the remote device

address domain ID or Non Gen'ed device address
domain ID has been specified as the local device
address domain ID in the Set Defaults panel.
YKM049E ISPF
A Path ID is required for

Universal Replicator Copy
Group definitions.
To define a Universal Replicator copy group, a path

group ID is required.
YKM050E MSG
SC=36 RC=48
(attribute-value)

name

this command.
Correct the specified device address domain ID and

serial number of the storage system.

name
REXX variable name
attribute-value
REXX variable value
YKM056E MSG
SC=36 RC=48
NOCOPY option invalid for

ShadowImage Copy Group
The YKMAKE command with the NOCOPY parameter

specified was executed on a ShadowImage copy group.
This parameter is invalid on ShadowImage copy
groups.
Re-execute the YKMAKE command without specifying
the NOCOPY parameter.
YKM058E MSG
SC=36 RC=48

not support TCA services

YKM099I TSO
YKMAKE command return

code=nnnn, reason
code=rrrr
The YKMAKE command terminated with the return code

nnnn
Messages
1-73
Table 1-12 List of messages (message ID YKM1x - YKM5x)

Message ID
Message text
YKM103E MSG
SC=48
The parameter combination

is invalid
The parameter combination is invalid.
YKM500E ISPF
You cannot perform a

remote scan if the specified
DADID matches a local or
Non Gen'ed DADID or if the
loaded HDA file is not for
remote scan or if the Preset
RouteListID, which is in the
Set Defaults panel, is not
enabled.
A Remote Scan cannot be performed in the following

cases:
YKM501E ISPF
You cannot edit the device

number for a volume that
was not found by remote
scan or NG scan.
The device number cannot be edited because the

volume was not found by a Remote Scan or an NG
Scan. For details about the NG Scan, see the Hitachi
Business Continuity Manager User Guide.
YKM502E ISPF
You cannot exit until all

discovered devices are
assigned dummy devn.
The exit operation cannot be performed until a device

number is assigned to all discovered devices.
YKM503E ISPF
The number of connections

of inter-DKC paths exceeds
the maximum number of
connections that is allowed
within the same storage
system.
The number of connections of inter-disk controller

paths exceeded the maximum that is allowed within
the same storage system.
YKM504E ISPF

of inter-DKC paths of the
same PathID exceeds the
maximum number of
within the same storage
system.
The number of connections of inter-disk controller

paths of the same PathID exceeded the maximum that
is allowed within the same storage system.
YKM505E ISPF
This inter-DKC path is

already defined in another
logical path.
This inter-disk controller path is already defined in

another logical path.
YKM506E ISPF
You cannot define inter-DKC

path with this interface
version.
In this interface version, the user cannot define interdisk controller paths.
YKM507E ISPF

of inter-CU paths exceeds
the maximum number of
within the same CU.
The number of connections of inter- control unit paths

exceeded the maximum that is allowed within the same
control unit.
YKM508E ISPF
This inter-CU path is already

defined in another logical
path.
This inter- control unit path is already defined in

another logical path.
YKM509E ISPF
The number of physical

paths that are defined in the
The number of physical paths exceeded the maximum

that is allowed within the same logical path.
1-74
The specified device address domain ID is

equivalent to the local device address domain ID
or a Non Gen'ed device address domain ID.
When the HDA file is not a file used for a Remote

Scan
When the Preset RouteListID set in the Set

Defaults panel is not valid.
Messages
Message ID
Message text
same logical path exceeds

the limit.
YKM510E ISPF
This Model is not supported

for this Path Type.
This model does not support this path type.
YKM511E ISPF
The value of CU exceeds the

number of CUs that is
allowed in this Model.
The number of control units exceeds the maximum

number for this model.
YKM512E ISPF
The number of logical paths

that are using this port
exceeds the limit.
The number of logical paths that are using this port

exceeded the limit.
YKM513E ISPF

exceeds the limit that is
allowed within this port.
The number of connections exceeded the limit that is

allowed within this port.
YKM514E ISPF
CCA could not be assigned

because either the path is
already defined in another
logical path, or the list of
CCA could not be retrieved.
A command control address could not be assigned

because the path is already defined in another logical
path, or because a list of command control addresses
could not be obtained.
YKM515E ISPF
You cannot specify the same The same serial number cannot be specified for both
serial number to the primary the primary and secondary sides of the same logical
side and the secondary side path.
of the same logical path.
YKM516E ISPF
Port errport is already

defined as portdir port.
The port errport is already defined as portdir.

errport
The port that you specified
portdir
The port that is already defined
YKM517E ISPF
The value of PathID exceeds

the value that is allowed in
this Model.
The value of PathID exceeds the maximum for this

model.
YKM518E ISPF
Port errport exceeds the

limit that is allowed in this
composition.
The number of ports exceeds the maximum number for

this composition.
errport
The port that you specified
YKM519E ISPF
Different PathIDs cannot be The path ID that is different for the primary site and for
specified for the primary side the secondary site cannot be specified to the inter-disk
and secondary side of an
controller logical path.
inter-DKC path.
YKM520E ISPF
These device number

remdevn or storage system
S/N remsn are not
discovered on Device
Address Domain remdad.
The device number or storage system serial number

has not yet been scanned in the device address domain
ID.
remdevn
The device number you specified
remsn
The storage system serial number you specified
remdad
Messages
1-75
Message ID
Message text

The device address domain ID you specified
YKM521E ISPF
You cannot exit this panel

until you define a command
device.
The exit operation cannot be performed until you

define a command device.
YKM522E ISPF
Please supply the required

information.
Enter the necessary information.
YKM523E ISPF
You cannot enter values to

both License Key Dataset
Name field and Key Code
field at the same time.
The License Key Dataset Name and Key Code fields

cannot be specified simultaneously.
YKM524E ISPF
Please enter alphanumeric

The value specified in the Key Code field contains
characters to Key Code field. characters that are not numbers or letters.
YKM525E ISPF
Invalid Key Code is entered.

Please re-enter the Key
Code.
The key code is incorrect. Please re-enter the key code.
YKM526E ISPF
Invalid dataset name is

specified.
An incorrect dataset name is specified.
YKM527E ISPF
You cannot specify the

license information dataset.
The license information dataset cannot be specified.
YKM528E ISPF
Enter the value that you

Enter the value that you want to find in the sorted field
wish to find with the LOCATE field-name by using the LOCATE command.
command on a sorted field
field-name
"field-name".
field name
YKM529E ISPF
You cannot specified except

'00' as PathID with this
interface version.
Only 00 can be specified for a path ID in this interface

version.

Message ID
Message text
YKM700E ISPF
Enter one of the listed

values.
Please enter one of the listed values.
YKM701E ISPF
Enter required field at the

cursor position.
Enter the required information at the cursor position.
YKM702E ISPF
The length of the data must

be = crtlen.
The length of the input data must be crtlen.

crtlen
Necessary data length
YKM703E ISPF
Enter hexadecimal
characters (0-9, A-F, a-f).
Enter hexadecimal characters (0-9, A-F, a-f).
YKM704E ISPF
Enter alphanumeric
characters (0-9, A-Z, a-z).
Enter alphanumeric characters (0-9, A-Z, a-z).
YKM705E ISPF
Each qualifier must be 1-8

alphanumeric characters
Each qualifier must be from 1 to 8 alphanumeric

characters (0-9, A-Z, a-z), and must begin with an
alphabetic character.
1-76
Messages
Message ID
Message text
(0-9, A-Z, a-z), the first

alphabetic.
YKM706E ISPF
The length of the "fieldname" field data must be no

more than loclen.
The length of the input entered into the field-name

field must be no more than loclen.
field-name
field name
loclen
Input length
YKM707E ISPF
Enter the number (hex.

characters: 0-9, A-F, a-f) to
search for.
Enter the hexadecimal characters (0-9, A-F, a-f) that

you want to search for.
YKM708E ISPF
Enter the number (numerical Enter the numeric values (0-9) that you want to search
characters: 0-9) to search
for.
for.
YKM709E ISPF
Execute the sort command

before executing the locate
command.
Execute the SORT command before executing the

LOCATE command.
YKM710E ISPF
Enter one of the following

characters(P, S, N/A) to
search for.
Enter the character you want to search for (P, S, or

N/A).
YKM720E ISPF
Required parameter is not

specified.
Enter the required parameters.
YKM721E ISPF
Invalid field name is

specified.
Enter the name of the field that specifies the condition.
YKM722E ISPF
Invalid pattern is specified.
Specify correct values for the pattern parameter.

Make sure that none of the following conditions exist:
A value greater than value 1 was specified for

value 2, as the range specification condition.
NULL was specified for value 1, as the range

specification condition.
A value containing an asterisk (*) was specified for

value 1 or value 2, as the range specification
condition.
The specified value contained two or more

asterisks.
An asterisk (*) was specified in a location other

than before or after the value.
YKM723E ISPF
Invalid action name is

specified.
Enter the valid action name.
YKM724E ISPF
The length of the "fieldname" field data must be no

more than value-length.
The length of the input entered into the field-name

field must be equal to or less than value-length.
field-name
field name
value-length
Input length
Messages
1-77
Message ID
Message text
YKM725E ISPF
Enter the number (hex.

characters: 0-9, A-F, a-f).
Enter the hexadecimal characters (0-9, A-F, a-f).
YKM726E ISPF
Enter the number (numerical Enter a numeric value (0-9).

characters: 0-9).
YKM727E ISPF
Range specification is not

supported for the field.
A range cannot be specified for the field.
YKM728E ISPF
The specified pattern

produced no matching lines.
A line that matches the specified pattern was not

found.
YKM731E ISPF
ISPF service error occurred.

info
An error occurred in the ISPF service.

info
YKM750E ISPF
Serial number must be a 5digit combination of

alphanumeric characters.
Serial numbers must be a five-digit combination of

alphanumeric characters (0-9, A-Z, a-z).
YKM751E ISPF
DADID must be a
combination of one or more
qualifiers. Each qualifier
must be 1-8 alphanumeric
characters (0-9, A-Z, a-z)
with the first character being
an alphabetic character (AZ, a-z). The length of DADID
must be 1-28.
The device address domain ID must be a combination

of one or more qualifiers. Each qualifier must be from 1
to 8 alphanumeric characters (0-9, A-Z, a-z), and must
begin with an alphabetic character (A-Z, a-z). The
length of the device address domain ID must be from 1
to 28 characters.
YKM752E ISPF
DEVN must be 4
hexadecimal characters
(0-9, A-F, a-f).
The device number must be a four-digit hexadecimal

number (0-9, A-F, a-f).
YKM753E ISPF
APID must be 4 hexadecimal The APID must be a four-digit hexadecimal number

characters (0-9, A-F, a-f).
(0-9, A-F, a-f).
YKM754E ISPF
Route List ID must be a

an alphabetic character (AZ, a-z). The length of Route
List ID must be 1-8.
The route list ID must be a combination of one or more

qualifiers. Each qualifier must be from 1 to 8
alphanumeric characters (0-9, A-Z, a-z), and must
length of the route list ID must be from 1 to 8
characters.
YKM755E ISPF
Configuration File Prefix

must be a combination of
one or more qualifiers. Each
qualifier must be 1-8
alphanumeric characters
(0-9, A-Z, a-z) with the first
character being an
alphabetic character (A-Z, az). The length of
Configuration File Prefix
must be 1-16.
The prefix of the configuration file name must be a

combination of one or more qualifiers. Each qualifier
must be from 1 to 8 alphanumeric characters (0-9, AZ, a-z), and must begin with an alphabetic character
(A-Z, a-z). The length of the configuration file name
prefix must be from 1 to 16 characters.
1-78
Messages
Message ID
Message text
YKM756E ISPF
Copy Group ID must be a

an alphabetic character (AZ, a-z). The length of Copy
Group ID must be 1-40.
The copy group ID must be a combination of one or

more qualifiers. Each qualifier must be from 1 to 8
length of the copy group ID must be from 1 to 40
characters.
YKM757E ISPF
The 4-digit year (YYYY) or 2digit month (MM) or 2-digit

day (DD) was not numeric.
Valid year values are
1970-2042, valid month
values are 01-12, and valid
day values are 01-31.
The value for the year (YYYY), month (MM), or day

(DD) was not numeric. Specify a value for the year,
month, and day in the range 1970 to 2042, 01 to 12,
and 01 to 31, respectively.
YKM758E ISPF
The hour, minute, or second

value is not numeric. Valid
values are 00-23 for hour,
00-59 for minute, and 00-59
for second.
The value for the hour, minute, or second was not

numeric. Specify a value for the hour, minute, and
second in the range 00 to 23, 00 to 59, and 00 to 59,
respectively.
YKM759E ISPF
Enter numeric characters

(0-9).
Please enter a numeric value (0-9).
YKM760E ISPF
Preset Mode cannot be used You cannot set the Preset Mode without specifying a
when C/T ID is not specified. consistency group ID.
YKM761E ISPF
Check Device Num, Volser,

or Non Gen'ed.
Check the value specified in Device Num, Volser, or

Non Gen'ed.
YKM762E ISPF
You cannot perform an NG

scan because the specified
DADID matches a local or
remote DADID.
You cannot perform an NG Scan, because the specified

device address domain ID is the same as the local
device address domain ID or remote device address
domain ID. For details about the NG Scan, see the
Hitachi Business Continuity Manager User Guide.
YKM763E ISPF
You cannot perform an NG

scan because no local scan
has been performed for the
specified storage system.
You cannot perform an NG Scan, because a Local Scan

has not been performed for the specified storage
system. For details about the NG Scan, see the Hitachi
YKM764E ISPF
Select one of the displayed

lines.
Select one of the displayed lines.
YKM765I ISPF
A description for the

specified error code was not
found.
A description for the specified error code was not

found.
For details about error codes, see XXX. If the error
code is not listed in the manual, contact your Hitachi
Data Systems representative or authorized service
provider.
YKM766E ISPF
Specified Prefix is being used The specified prefix is being used by another program.
by another program.
YKM767E ISPF
This command is invalid for

TrueCopy Copy Groups
linkaged with HyperSwap.
The command cannot be executed for TrueCopy copy

groups with the HyperSwap attribute.
Messages
1-79
Message ID
Message text

Execute the PPRC copy pair operation from TPC-R.
YKM768E ISPF
HS cannot be used when C/T If a consistency group ID is specified, you cannot

ID is specified.
specify HS for the linkage option.
YKM769E ISPF
Route Label must be an

asterisk (*), or a
Label must be 1-8.
The route label must be an asterisk (*), or a

combination of one or more qualifiers. Each qualifier
must be from 1 to 8 alphanumeric characters (0-9, AZ, a-z), and must begin with an alphabetic character
(A-Z, a-z). The length of the route label must be from
1 to 8 characters.
YKM770E ISPF
Enter unique value in a

storage system.
Enter a value that is unique within the storage system.
YKM771I ISPF
Panel could not scroll

because it shows beginning
of data.
The panel cannot be scrolled because the start of the

data is already being displayed.
YKM772I ISPF
Panel could not scroll

because it shows end of
data.
The panel cannot be scrolled because the end of the

data is already being displayed.
YKM773E ISPF
DADID must be shortened so The dataset name of the disk configuration file
that dataset name of disk
exceeded the 44-character limit. Shorten the device
configuration file is no more address domain ID.
than 44 characters.
YKM774E ISPF
Specified storage system is

defined in the same route.
The specified storage system is already defined in the

route. Select a different storage system.
YKM775E ISPF
Panel could not proceed the

insert action because
number of the route entry
has reached maximum.
The storage system cannot be added because the

number of storage systems defined in the route is
already at the maximum.
YKM776E ISPF
Route Label must be a

Label must be 1-8.
The route label must be a combination of one or more

qualifiers. Each qualifier must be from 1 to 8
start with an alphabetic character (A-Z, a-z). The
length of the route label must be from 1 to 8
characters.

Message ID
Message text
YKM900E ISPF
Start YKSTART command.
Start the YKSTART command.
YKM901E TSO
ISPF service is not available.
The ISPF service is not available.

Execute the YKSTART command in an ISPF
environment.
1-80
Messages
Message ID
Message text

After that, you can execute whichever Business
Continuity Manager commands you need to.
YKM902E TSO
Load module is not found.
The Business Continuity Manager load module was not

found. The Business Continuity Manager dataset might
not be concatenated to the LNKLST.
Revise the settings for the LNKLST, and then execute
the YKSTART command.
After that, you can execute whichever Business
Continuity Manager commands you need to.
YKM903E TSO
SELECT service terminated

abnormally. RC=nn
The SELECT service terminated abnormally with the

return code nn.
If this message is displayed immediately after
executing the YKSTART command, the Business
Continuity Manager dataset might not be concatenated
to the panel library (dd name: ISPPLIB), the table
library (dd name: ISPTLIB), or the REXX exec library
(dd name: SYSEXEC).
If DBCS (Double-Byte Character Set) is enabled for the
environment, concatenate the Business Continuity
Manager dataset to the alternate panel library (dd
name: ISPPALT). For details, see the Hitachi Business
Continuity Manager Installation Guide.
nn
Return code of the service
YKM904E TSO
Message library was not

found.
The message library was not found.

The Business Continuity Manager dataset might not be
concatenated to the message library (dd name:
ISPMLIB).
If DBCS (Double-Byte Character Set) is enabled for the
environment, concatenate the Business Continuity
Manager dataset to the alternate message library (dd
name: ISPMALT). For details, see the Hitachi Business
Continuity Manager Installation Guide.
YKM905E TSO
A GETMAIN error occurred.
A GETMAIN error occurred. The program will stop

running.
YKM906E TSO
A FREEMAIN error occurred.
A FREEMAIN error occurred. However, the program will

continue to run.
Table 1-15 List of messages (message ID YKN0x)

Message ID
YKN000T TSO
RC=48
Message text

For details, see the reason code in the YKN099I
Services.
Messages
1-81
Message ID
Message text
YKN001E TSO
RC=48
YKN001E MSG
SC=48 RC=48
YKN002E MSG
SC=48 RC=48


period.
stem
YKN002E TSO
RC=48


stem
YKN010E TSO
RC=40
REXX failure return

variable name

nnnn
YKN050E MSG
SC=48 RC=48
(attribute-value)

name

this command.
name
REXX variable name
attribute-value
REXX variable value
YKN099I TSO
YKRUN command return

code=nnnn, reason
code=rrrr
The YKRUN command terminated with the return code

nnnn
Table 1-16 List of messages (message ID YKP0x)

Message ID
Message text
YKP000T TSO
RC=48
YKP001E TSO
RC=48
YKP001E MSG
SC=48 RC=48
1-82

For details, see the reason code in the YKP099I
Services.
Messages
Message ID
YKP002E MSG
SC=48 RC=48
Message text

period.
stem
YKP002E TSO
RC=48


stem
YKP002E MSG
SC=48 RC=48
This command is only valid

for TCA or UR Copy Groups
The YKSTATS command was executed on a copy group

that is neither TrueCopy Asynchronous nor Universal
Replicator. This command works only on TrueCopy
Asynchronous or Universal Replicator copy groups.
YKP003E MSG
SC=48 RC=48
YKP010E TSO
RC=40
Some storage systems in

this Copy Group do not
support TCA statistics
reports
The TrueCopy Asynchronous copy group on which the

YKSTATS command has been executed contains an
unsupported IFType.
REXX failure return

variable name
Access to the REXX variable indicated by name failed.

nnnn
Error code for REXX access
YKP065E MSG
SC=36 RC=36
The storage system serial

The storage system identified by serial-number is
number pairs with more than paired with more than four storage systems within the
4 storage systems.
consistency group group.
Correct the copy pair configuration within the
consistency group group.
serial-number
Storage system serial number (12 digits)
YKP099I TSO
YKSTATS command return

code=nnnn, reason
code=rrrr
The YKSTATS command terminated with the return code

nnnn
Table 1-17 List of messages (message ID YKQ0x)

Message ID
YKQ000T TSO
RC=48
Message text

For details, see the reason code in the YKQ099I
Messages
1-83
Message ID
Message text

Services.
YKQ001E TSO
RC=48
YKQ001E MSG
SC=48 RC=48
YKQ002E MSG
SC=48 RC=48


period.
stem
YKQ002E MSG
SC=48
YKQ002E TSO
RC=48


stem
YKQ003E MSG
SC=48
Parameters combination is
invalid
YKQ008E MSG
SC=48

hexadecimal format.
YKQ010E TSO
RC=40
REXX failure return

variable name
Access to the REXX variable indicated by name failed.

nnnn
Error code for REXX access
YKQ018E MSG
SC=16 RC=16
(pair-index)
SI PAIR deficiency. DEVN

device#(SN,CU#,CCA#)
In a ShadowImage copy group, the volume in the

target copy pair has already been paired with three
volumes other than the pairing volume specified in the
copy group definition.
Review the applicable copy pair definition in the copy
group definition.
device#
Device number
If the device cannot be identified, **** is
displayed.
SN
Storage system serial number
If the device cannot be identified, ************ is
displayed.
CU#
Control unit number
If the device cannot be identified, ** is displayed.
CCA#
Command control address number
1-84
Messages
Message ID
Message text

pair-index
YKQ019W MSG
SC=12 RC=0
(pair-index)
Primary volume serial

changed. DEVN
Although the P-VOL is online, the current volume serial

number does not match the volume serial number
defined for the copy group. Processing will continue.
Check that the copy group indicates the correct
volumes and is not being used for other purposes.
device#
Device number
displayed.
SN
displayed.
CU#
Control unit number
CCA#
pair-index
YKQ021E MSG
SC=12 RC=20
(pair-index)
TCA or SI Primary is
simplex, secondary not.
DEVN
Check that the S-VOL status is SIMPLEX.

device#
Device number
displayed.
SN
displayed.
CU#
Control unit number
CCA#
pair-index
Messages
1-85
Message ID
YKQ026W MSG
SC=8 RC=8
(pair-index)
Message text
Primary volume is offline.
DEVN

The volume serial number of the P-VOL cannot be
obtained because the P-VOL is offline.
Check that the copy group indicates the correct
volumes and is not being used for other purposes,
make the P-VOL online, and then re-execute the
YKQUERY command.
device#
Device number
displayed.
SN
displayed.
CU#
Control unit number
CCA#
pair-index
YKQ099I TSO
YKQUERY command return

code=nnnn, reason
code=rrrr
The YKQUERY command terminated with the return code

nnnn
Table 1-18 List of messages (message ID YKR0x - YKR10x)

Message ID
Message text
YKR000T TSO
RC=48
YKR001E TSO
RC=48
YKR001E MSG
SC=48 RC=48
YKR002E MSG
SC=48 RC=48


period.
1-86

For details, see the reason code in the YKR099I
Services.
Messages
Message ID
Message text

stem
YKR002E MSG
SC=48
YKR002E TSO
RC=48


stem
YKR008E MSG
SC=48

hexadecimal format.
YKR010E TSO
RC=40
REXX failure return

variable name

nnnn
YKR050E MSG
SC=36 RC=48
(attribute-value)

name

this command.
name
REXX variable name
attribute-value
REXX variable value
YKR058E MSG
SC=36 RC=48


Check whether the command can be executed on this
copy group, and then re-execute the command.
YKR099I TSO
YKRESYNC command return

code=nnnn, reason
code=rrrr
The YKRESYNC command terminated with the return

nnnn
YKR103E MSG
SC=48
invalid
Table 1-19 List of messages (message ID YKS0x)

Message ID
Message text
YKS001E TSO
RC=48

YKS002E TSO
RC=48

trailing "."

stem
Messages
1-87
Message ID
Message text

YKS003E TSO
RC=52
Invoke YKSTORE REXX

Script via YKSTORE
Assembler subroutine.
The YKSTORE REXX program can only be invoked via

the YKSTORE assembler REXX subroutine. This message
indicates the most likely cause of the error indicated in
the previous YKS003E message.
YKS003E TSO
RC=52
Unable to update MSG(stem) An attempt to assign a value to a variable of the

Message structure failed with the result value indicated
by result. This implies that the YKSTORE REXX
subroutine has not properly been invoked or that
Business Continuity Manager has not properly been
installed.
stem
YKS004E MSG
SC=48 RC=48

YKS005E MSG
SC=48 RC=48
STEM(stem) does not

stem
YKS006E MSG
SC=48 RC=48

valid PREFIX parameter.
Specify a valid PREFIX parameter.
YKS079E MSG
SC=44 RC=44
(result)

variable =value.

variable failed with the result value identified by result.
This error can be caused by the YKSTORE REXX
subroutine's compiled REXX module being directly
executed.
Use the YKSTORE REXX subroutine, instead of directly
executing the compiled REXX module.
YKS085E MSG
SC=44 RC=44
Error reported during file

output. EXECIO RC =n
Because the EXECIO TSO/E REXX command failed

(return code = n), the YKSTORE command is
unavailable for creating or updating the configuration
file. For details, see the TSO/E REXX User's Guide.
YKS086E MSG
SC=44 RC=44
(file)
File status is:dsstate
The input configuration file identified by file is

unavailable.
dsstate
Status of the input configuration file
The following messages are output if the attribute
of the input configuration file is abnormal:
DSORG = XX. DSORG must be YY

The file is unavailable because the DSORG attribute
value is abnormal. Therefore, delete the current
configuration file, and then recreate a new
configuration file that has correct file attributes.
RECFM = XX. RECFM must be YY

The file is unavailable because the RECFM attribute
1-88
Messages
Message ID
Message text

LRECL = XX. LRECL must be YY

The file is unavailable because the LRECL attribute
BLKSIZE = XX. BLKSIZE must be YY

The file is unavailable because the BLKSIZE
attribute value is abnormal. Therefore, delete the
current configuration file, and then recreate a new
ALLOCATION FAILED
Creation of a configuration file failed. Check the
free device capacity and the available size of VTOC.
For details about the required device capacity for a
configuration file, see the Hitachi Business
UNAVAILABLE DATASET
The configuration file is being used. Check the
usage of the configuration file.
XX displays the file attribute value that caused the

error and YY displays the correct file attribute value.
file
detected
YKS098E MSG
SC=36 RC=36
Specified STEM() is not

CopyGroup object.
The prefix of the REXX variable name specified in the

STEM parameter does not comply with the copy group
structure described in the Hitachi Business Continuity
YKS099I MSG
TSO SC=maxseverity
RC=max-value
YKSTORE Processing
Complete.
YKSTORE command processing has completed.

This message is always displayed.
max-severity
Maximum value among the output severity codes
max-value
Table 1-20 List of messages (message ID YKS2x)

Message ID
Message text
YKS203E TSO
RC=52
Invoke YKSTORE REXX

Script via YKSTORE
Assembler subroutine.
The YKSTORE REXX program can only be invoked via

the YKSTORE assembler REXX subroutine. This message
indicates the most likely cause of the error indicated in
the previous YKS203E message.
YKS203E TSO
RC=52
The MSG(stem) value cannot An attempt to acquire the variable value of the
be acquired in the caller's
Message structure failed with the result value identified
by result. This implies that the YKSTORE REXX
Messages
1-89
Message ID
Message text
environment. (YKVGET result subroutine has not properly been invoked or that
= result)
Business Continuity Manager has not properly been
installed.
stem
YKS250E MSG
SC=36 RC=36

variable name is an invalid
format.
The value value of the variable identified by name is

invalid.
YKS260E MSG
SC=44 RC=44
Too long record:record.
An attempt to output record to a dataset failed because

record was too long.
Correct the variable setting so that the length of record
becomes 256 characters or shorter.
YKS270E MSG
SC=44 RC=44
Failed to operation
configuration file. (name
=dataset-name, dsstate)
Creation of the configuration file is stopped because an

error occurred during the creation of the configuration
file. Refer to the information output in the message to
review the environment, and then create the
configuration file again. For details about what action
to take, see the message that was output and the
Hitachi Business Continuity Manager User Guide.
operation
The operation performed for the configuration file
CREATE
An error occurred during the creation of the
configuration file.
UPDATE
An error occurred during the update of the existing
configuration file.
ALLOCATION
An error occurred during the allocation of the
configuration file. Check the free capacity on the
device and the available size of VTOC. For details
about the required capacity on the device for a
configuration file, see the Hitachi Business
CHECK
An error occurred during the check of the existing
configuration file. Check the status of the
configuration file. The error might have occurred
because the configuration file is in an unusable
state, or the dataset format is invalid. If the
dataset format is invalid, check the message that
was output simultaneously.
EXECIO
An error occurred while writing to the configuration
file. For the cause of the error, check the message
that was output simultaneously.
RENAME
An error occurred when the YKBTSCAN command
was executed, and the configuration file was being
1-90
Messages
Message ID
Message text

renamed to the name displayed in dataset-name.
Check whether the dataset name displayed in
dataset-name actually exists in the system, and
then execute the command again.
Information about the file with the name to be
changed is displayed in dsstate.
dataset-name
Name of the configuration file to be created
dsstate
EXTENT=extent
The number of extents of the dataset that is
currently allocated
extent indicates the number of extents that are
allocated to the dataset indicated by datasetname.
DSORG=VSAM
The dataset format is VSAM. A dataset with the
format VSAM cannot be used as a configuration
file. Change the dataset format of the
configuration file into PS.
RECFM=XX
RECFM value of the dataset
LRECL=XX
LRECL value of the dataset
BLKSIZE=XX
BLKSIZE value of the dataset
CANNOT GET DSSTATE, reason code=nnnn

The dataset information cannot be obtained, or the
configuration file is not assigned.
nnnn (decimal (base 10) number) indicates a
reason code (maintenance information).
This message indicates that, if dataset-name
contains NEW or OLD, an error occurred while
processing the temporary file used for creating or
updating the configuration file.
YKS285E MSG
SC=48 RC=48
file-name is too long for a

filename.
The file name identified by file-name is too long. The

file name must consist of 44 or fewer characters.
YKS290E MSG
SC=44 RC=44
(result)
YKVGET program failure

for:vn

caused by the YKSTORE REXX subroutine's compiled
REXX module being directly executed.
Use the YKSTORE REXX subroutine, instead of directly
executing the compiled REXX module.
YKS298E MSG
SC=44 RC=44
(detailed-info)
YKSTORE encountered an
unexpected error.
An unexpected error has occurred. This error might

have occurred with another error.
Messages
1-91
Message ID
Message text


the ISPF panel).

The configuration files operated on from the script

or ISPF panel (the copy group definition file, disk
detailed-info
Detailed information displayed to assist your
Hitachi Data Systems representative or authorized
service provider in resolving the problem
Table 1-21 List of messages (message ID YKT0x)

Message ID
YKT001E CON
Message text
Can't find SVCTABLE

The "SVCTABLE" search in the NUCLKUP macro failed.
The program abnormally terminates with user
completion code 996.
YKT002E CON
Can't find IGCERROR
The "IGCERROR" search in the NUCLKUP macro failed.

YKT003E CON
No SVC #'s available
No SVC number available. The program abnormally

terminates with user completion code 996.
YKT004E CON
Couldn't add SVC entry
SVC number addition failed in the SVCUPDTE macro.

YKT005E CON
Couldn't create name/token
Name/Token registration failed. The program

abnormally terminates with user completion code 996.
YKT006W CON
RC=16
Couldn't delete name/token
YKT007W CON
RC=16
Couldn't delete SVC entry
YKT008E CON
RC=20
System task started without

START from TSO.
1-92
Name/Token deletion failed.

SVC number deletion failed in the SVCUPDTE macro.
The YKALCSVC command was executed in the TSO/E
environment.
Messages
Message ID
Message text

Execute the YKALCSVC command using the START
command or a batch job.
YKT012E CON
RC=16
Name/token error
An error occurred in the Name/Token service.
YKT021E CON
RC=20
Invalid parameter
YKT022E CON
RC=4
SVC routine is already

inserted
The user SVC is already registered.
YKT023E CON
RC=16
Couldn't delete SVC routine
The user SVC deletion failed.
YKT024E CON
Couldn't copy load module

A value specified in the PARM parameter is invalid.
Check the specification of the PARM parameter.

Copying of the load module failed. The program
abnormally terminates with user completion code 996.
YKT025E CON
RC=4
SVC routine is already

deleted
The user SVC is not registered or is deleted.
YKT026E CON
SVC # is already used
The specified SVC number is already used. The

program abnormally terminates with user completion
code 996.
Specify an unassigned SVC number in the PARM
parameter of the YKALCSVC command, or re-execute
without the PARM parameter.
YKT032E CON
RC=20
The task is not APFauthorized.
The dataset name of the Business Continuity Manager

load library was not registered in SYS1.PARMLIB.
Alternately, the execution of the command failed
because authorized/unauthorized datasets co-existed
while concatenating DD statements in the load library,
and they were handled as unauthorized datasets.
YKT098I CON
RC=0
SVC routine is deleted
The user SVC deletion succeeded.
YKT099I CON
RC=0
SVC routine is inserted
The user SVC registration succeeded.

Message ID
YKT210E CON
RC=8
Message text
System task started without
START from TSO.

The command was invoked from the TSO/E
environment. The program stops processing.
Invoke the command using the START command, or as
a batch JOB.
YKT211E CON
RC=12
Failed to allocate space in

CSA
A GETMAIN error occurred in CSA. The program stops

processing.
YKT212E CON
RC=12
Couldn't register Name/

Token
An error occurred during Name/Token registration. The

program stops processing.
Messages
1-93
Message ID
Message text

YKT213E CON
RC=4
Couldn't take Name/Token
An error occurred during acquisition of Name/Token.

The program stops processing.
YKT219E CON
RC=16
Processing ended abnormally Processing terminated abnormally before completion.

The program stops processing.
YKT220E CON
RC=8
Unknown keyword is
specified
The specified keyword is unknown. The program stops

processing.
Specify a valid keyword and then re-execute the
command.
YKT221E CON
RC=4
Specified HOST ID is invalid
The value assigned to the YKCMDIF parameter is

invalid. The program ignores the specification and
continues processing.
In HOST ID, you can either omit specification (Delete)
or specify a hexadecimal value (two characters)
between 00 and 1F. Specify a correct value and retry
the process.
YKT222E CON
RC=4
Specified YKLCNSE is invalid
The value assigned to the YKLCNSE parameter is

invalid. The program ignores the specification and
continues processing.
You can specify a character string containing up to
eight characters. Specify a correct value and retry the
process.
YKT223E CON
RC=4
Specified LOGPUT is invalid
The value assigned to the LOGPUT parameter is invalid.

The program ignores the specification and continues
processing.
Valid values are either LOGR or SAM. Specify a valid
value and retry the process.
YKT226E CON
RC=4
The specified SYSLOG value

is invalid.
The value specified for the SYSLOG parameter is invalid.

The program ignores the specification and continues
processing.
Valid values are either YES or NO. Specify a valid value
and retry the process.
YKT230E CON
RC=4
The specified YKLCNS2 value The value specified for the YKLCNS2 parameter is
is invalid.
invalid. The program will ignore the specification and
continue processing.
A maximum of 8 characters can be specified. Specify a
correct value, and then retry the operation.
YKT232E CON
RC=12
The task is not APFauthorized.
The dataset name of the Business Continuity Manager

load library is not registered in SYS1.PARMLIB.
Alternately, the execution of the command has failed
because authorized/unauthorized datasets co-existed
while concatenating DD statements in the load library
and they were handled as unauthorized datasets.
YKT299I CON
SC=0
command command return

code=nnnn.
The command identified by command terminated with

the return code nnnn.
1-94
Messages

Message ID
YKT400I CON
Message text
BC Manager environment
variables (version)

This message displays the Business Continuity Manager
environment variables.
version
Version of Business Continuity Manager
YKT401I CON
variable : value
This message displays the Business Continuity Manager

environment variables.
variable
Environment variables for Business Continuity
Manager
Host ID: The host ID
License info DSN prefix: Prefix of the license

information dataset
BCM log output method: Output method of the

BCM log
CLI log output settings: Output settings for

the CLI command-execution logs
value
Value set for each of the Business Continuity
Manager environment variables
YKT402I CON
varname = value1 (symbol

= value2)
This message displays the details of the Business

Continuity Manager environment variables.
varname
Name of the Business Continuity Manager
environment variable that is set by using the
YKSETENV command
value1
Value of the Business Continuity Manager
environment variable that is set by using the
YKSETENV command
If no value has been set for the Business
Continuity Manager environment variable by using
the YKSETENV command, N/A is displayed.
symbol
Name of the system symbol
value2
Value set for the symbol system symbol
If no value is set for the system symbol, N/A is
displayed.
YKT403I CON
Hitachi Business Continuity

Manager
This message displays the program product name.
Messages
1-95
Table 1-24 List of messages (message ID YKU0x)

Message ID
Message text
YKU000T TSO
RC=48
YKU001E TSO
RC=48
YKU001E MSG
SC=48 RC=48
YKU002E MSG
SC=48 RC=48


period.
For details, see the reason code in the YKU099I

Services.
stem
YKU002E MSG
SC=48
YKU002E MSG
SC=48
GENID() value invalid
The value assigned to the GENID parameter is invalid.
YKU002E TSO
RC=48


stem
YKU002E MSG
SC=48

invalid.
YKU003E MSG
SC=48 RC=48
ATTIME Specification attime

is invalid.
The time value assigned to the ATTIME parameter is

invalid.
For the correct format, see the description of the
YKSUSPND command in the Hitachi Business Continuity
attime
Time value assigned to the ATTIME parameter
YKU003E MSG
SC=48 RC=48
SVOL(PROTECT|PERMIT)
option required
Either PROTECT or PERMIT must be specified for the

SVOL parameter.
YKU004E MSG
SC=48 RC=48
ATTIME Specification is
before current time.
The time assigned to the ATTIME parameter is earlier

than the present time.
YKU005E MSG
SC=48 RC=48
ATTIME Specification is more The time assigned to the ATTIME parameter is more
than 45.5 days into the
than 65,535 minutes (45.5 days) past the present
future.
time.
YKU008E MSG
SC=48

hexadecimal format.
YKU008E MSG
SC=48
GENID() not valid hex
The value specified in the GENID parameter is not in

hexadecimal format.
1-96
Messages
Message ID
Message text
YKU009E MSG
SC=48
Specify ATTIME() and

DEVN() parm exclusively
You cannot specify the ATTIME parameter and the DEVN

parameter at the same time.
YKU009E MSG
SC=48
Specify ATTIME() and

VOLUNIT parm exclusively
You cannot specify the ATTIME parameter and the

VOLUNIT parameter at the same time.
YKU010E TSO
RC=40
REXX failure return

variable name

nnnn
YKU050E MSG
SC=36 RC=48
(attribute-value)

name

this command.
name
REXX variable name
attribute-value
REXX variable value
YKU054E MSG
SC=36 RC=48
ATTIME parameter invalid

for TrueCopy Copy Group
The YKSUSPND command with the ATTIME parameter

specified was executed on a TrueCopy copy group. This
parameter is invalid on TrueCopy copy groups.
Re-execute the YKSUSPND command without specifying
the ATTIME parameter.
YKU055E MSG
SC=48 RC=48
Specify PURGE and DEVN

The PURGE and DEVN parameters cannot be specified
parameter exclusively for UR simultaneously for a Universal Replicator copy group.
Copy Group
YKU055E MSG
SC=48 RC=48
Specify PURGE and VOLUNIT The PURGE and VOLUNIT parameters cannot be specified
parameter exclusively for UR simultaneously for a Universal Replicator copy group.
Copy Group
YKU056E MSG
SC=48 RC=48
DRAIN parameter cannot be

specified for UR Copy Group
The DRAIN parameter cannot be specified for a

Universal Replicator copy group.
YKU057E MSG
SC=36 RC=48
ATTIME and CANCEL

parameters are invalid for
UR Copy Group
The YKSUSPND command was executed on a Universal

Replicator copy group with the ATTIME parameter or
CANCEL parameter specified. These parameters are
invalid on Universal Replicator copy groups.
the ATTIME or CANCEL parameter.
YKU058E MSG
SC=36 RC=48


YKU099I TSO
YKSUSPND command return

code=nnnn, reason
code=rrrr
The YKSUSPND command terminated with the return

nnnn
Messages
1-97
Message ID
Message text

Table 1-25 List of messages (message ID YKV0x)

Message ID
Message text
YKV000T TSO
RC=48
YKV001E TSO
RC=48
YKV001E MSG
SC=48 RC=48
YKV002E MSG
SC=48 RC=48


period.
For details, see the reason code in the YKV099I

Services.
stem
YKV002E MSG
SC=48
YKV002E TSO
RC=48


stem
YKV008E MSG
SC=48

hexadecimal format.
YKV010E TSO
RC=40
REXX failure return

variable name

nnnn
YKV050E MSG
SC=36 RC=48
(attribute-value)

name

this command.
name
REXX variable name
attribute-value
REXX variable value
YKV058E MSG
SC=36 RC=48


1-98
Messages
Message ID
YKV099I TSO
Message text
YKRECVER command return
code=nnnn, reason
code=rrrr

The YKRECVER command terminated with the return
nnnn
Table 1-26 List of messages (message ID YKW0x)

Message ID
Message text
YKW001W TSO
Timeout limit has expired

without group copy-group
reaching state state.
The specified copy group copy-group did not reach the

requested status state within the specified time limit.
YKW002E TSO
Primary Device(s) OFFLINE.

Unable to receive IEA494I
messages.
Because the specified copy group contains a copy pair

with a P-VOL that is offline, the IEA494I message is
not issued.
Make all P-VOLs within the specified copy group online,
YKW003E TSO
Unexpected transition of
group copy-group pair index
device xxxx to state state.
One or more copy pairs identified by index within the

specified copy group copy group entered a status
identified by state that does not lead to the requested
GOTO status. It is probable that this status transition
was triggered manually.
Conduct an investigation using the ISPF panel
interface's monitor function.
YKW006E TSO
YKLOAD error return code =

nnnn
The YKWATCH command uses the YKLOAD command to

obtain the copy group configuration. An error occurred
during execution of the YKLOAD command.
interface's load function.
nnnn
Return code of YKLOAD command
For details, see the description for the YKLOAD
command in the Hitachi Business Continuity
YKW007E TSO
YKQUERY error return code

= nnnn.
The YKWATCH command uses the YKQUERY command to

establish the copy group status start baseline. An error
occurred during execution of the YKQUERY command.
interface's load function.
nnnn
Return code of the YKQUERY command
For details, see the description for the YKQUERY
Messages
1-99
Message ID
YKW008E TSO
Message text
YKCONMSG error return
code = nnnn

The YKWATCH command uses the YKCONMSG command to
monitor the console message traffic of IEA494I copy
status messages. An error occurred during execution of
the YKCONMSG command.
nnnn
Return code of the YKCONMSG command
For details, see the description for the YKCONMSG
YKW009W TSO
Terminated due to Operator

attention.
An interrupt occurred during execution of the YKWATCH

command. The TSO/E command issued within the
YKWATCH command cannot be completed.
Re-execute the command.
YKW010E TSO
Processing error
An error occurred during execution of the YKWATCH
encountered. Reason code = command. The YKCONMSG command issued within the
rrrr
YKWATCH command cannot be executed correctly.
rrrr
Return code of the YKCONMSG command
For details, see the description for the YKCONMSG
YKW098E TSO
Invalid parameter-reasonmessage
The YKWATCH command detected an invalid startup

parameter.
YKW099I TSO
Group copy-group has

reached the desired state
state.
This message is issued to notify the user that the copy

group identified by copy-group entered the requested
status identified by state.
copy-group
Copy group ID
Table 1-27 List of messages (message ID YKX0x)

Message ID
YKX000T TSO
Message text

For details, see the reason code in the YKX099I
Services.
YKX001E TSO
YKX001E MSG
SC=48
No serial# SN() supplied
Nothing is assigned to the SN parameter.
YKX002E TSO


stem
1-100
Messages
Message ID
YKX010E TSO
RC=40
Message text
REXX failure return
variable name

nnnn
YKX065W MSG
SC=4 RC=0
Storage system serialnumber Command Device

Definition Failed.
(APID=apid)
The command device definition for the storage system

identified by serial-number failed.
If multiple command devices are defined for the
storage system, processing continues.
Operate according to the I/O error messages issued
simultaneously.
serial-number
Serial number of the corresponding storage system
apid
APID of the command device that failed to be
defined
YKX066E MSG
SC=48 RC=48
Necessary Route List is not

found.
The route list to be processed was not found.
YKX099I TSO
YKBLDCMD command return

code=nnnn, reason
code=rrrr
The YKBLDCMD command terminated with the return

Check the ROUTE parameter, DAD parameter, route list

definition file, and command device definition file
specified in the YKLOAD command. Check that the
information corresponding to the storage system serial
number specified in the YKBLDCMD command is set.

nnnn

Message ID
Message text
YKX100T TSO
RC=48
YKX101E MSG
SC=48
No application id APID()
supplied
YKX101E MSG
SC=48
No command control address Nothing is assigned to the CCA parameter.

CCA() supplied
YKX101E MSG
SC=48
No control unit# CU()

supplied

Services.
Nothing is assigned to the APID parameter.
Nothing is assigned to the CU parameter.
Messages
1-101
Message ID
Message text
YKX101E MSG
SC=48
No device# DEVN() supplied
Nothing is assigned to the DEVN parameter.
YKX101E TSO
RC=48
YKX101E MSG
SC=48
YKX102E TSO
RC=48


stem
YKX103E MSG
SC=48
Parameter combination is
invalid
The specified parameter combination is invalid.
YKX104E MSG
SC=48
Device# DEVN() is not found The device specified in the DEVN parameter does not
exist, or a device other than DASD or a PAV ALIAS
volume has been specified.
YKX108E MSG
SC=48
APID() not valid hex
The value specified in the APID parameter is not in

hexadecimal format.
YKX108E MSG
SC=48
CCA() not valid hex
The value specified in the CCA parameter is not in

hexadecimal format.
YKX108E MSG
SC=48
CU() not valid hex
The value specified in the CU parameter is not in

hexadecimal format.
YKX108E MSG
SC=48

hexadecimal format.
YKX110E TSO
RC=40
REXX failure return

variable name
For details about the combination of parameters, see

the description of the YKBLDCMD command or the
YKDELCMD command in the Hitachi Business Continuity

nnnn
YKX166E MSG
SC=48

found.
YKX199I TSO
YKDELCMD command return

code=nnnn, reason
code=rrrr

Review the ROUTE and DAD parameters, route list
definition file, and command device definition file you
specified when executing the YKLOAD command.
The YKDELCMD command terminated with the return

Message ID
YKX200T TSO
RC=48
1-102
Message text

Messages
Message ID
Message text

Services.
YKX201E MSG
SC=48
No command control address Nothing is assigned to the CCA parameter.

CCA() supplied
YKX201E MSG
SC=48
No control unit# CU()

supplied
Nothing is assigned to the CU parameter.
YKX201E MSG
SC=48
No device# DEVN() supplied
YKX201E TSO
RC=48
YKX201E MSG
SC=48
No model SMODEL()
supplied
Nothing is assigned to the SMODEL parameter.
YKX201E MSG
SC=48
YKX201E MSG
SC=48
YKX201E MSG
SC=48
No serial# SSN() supplied
Nothing is assigned to the SSN parameter.
YKX202E TSO
RC=48


stem
YKX202E MSG
SC=48
Results STEM(stem) does


period.
stem
YKX203E MSG
SC=48
Parameter combination is
invalid
The specified parameter combination is invalid.
YKX204E MSG
SC=48
Device# DEVN() is not found The device specified in the DEVN parameter does not
YKX208E MSG
SC=48
CCA() not valid hex
The value specified in the CCA parameter is not in

hexadecimal format.
YKX208E MSG
SC=48
CU() not valid hex
The value specified in the CU parameter is not in

hexadecimal format.
YKX208E MSG
SC=48

hexadecimal format.
YKX210E TSO
RC=40
REXX failure return

variable name
For details about the combination of parameters, see

the description of the YKQRYDEV command in the
Hitachi Business Continuity Manager Reference Guide.

TSO/E Programming Services
Messages
1-103
Message ID
Message text

nnnn
YKX266E MSG
SC=48

found.
YKX299I TSO
YKQRYDEV command return

code=nnnn, reason
code=rrrr

Review the ROUTE and DAD parameters, route list
definition file, and command device definition file you
specified when executing the YKLOAD command.
The YKQRYDEV command terminated with the return
Table 1-30 List of messages (message ID YKY0x)

Message ID
YKY001I CON
Message text
AGENT STARTED (v.r.r[-zz])

The Business Continuity Manager agent has started.
v
Version number
r
Revision number
zz
Exception
YKY002I CON
INVALID INITIALIZATION
PARAMETER: parametername
The specified parameter has not been defined in the

initialization parameters, or the initialization parameter
shown as parameter-name is invalid. The Business
Continuity Manager agent has been terminated.
Correct the initialization parameters and then restart
the Business Continuity Manager agent.
YKY003I CON
INVALID CONTINUATION
LINE FOUND. PARAMETER
SCAN TERMINATED
The initialization parameters contain the specification

for a continuation line, but no parameter is continued.
The Business Continuity Manager agent will be
terminated.
Correct the initialization parameters and then restart
the Business Continuity Manager agent.
YKY005I CON
AGENT INITIALIZATION
FAILED P=termination-code
The Business Continuity Manager agent cannot start for

the reason indicated in the message that was displayed
before this message.
Contact the center administrator. The center
administrator must take appropriate action for the
message that was displayed before this message and
then restart the Business Continuity Manager agent.
termination-code (decimal number)
1-104
04: An attempt was made to start without using

IKJEFT01.
08: Initialization parameter analysis processing

failed.
48: A process module loading error occurred.
52: A NAME/TOKEN write error occurred.
Messages
Message ID
Message text
YKY008I CON
INSUFFICIENT SPACE
AVAILABLE FOR
INITIALIZATION
56: No profile is defined in the FACILITY class of

the RACF.
60: Subtask initialization processing failed.
68: An error occurred in the PREFIX exclusion

processing.
Initialization parameters analysis failed due to a

shortage of work space. The Business Continuity
Manager agent will be terminated.
Check, and, if necessary, revise the specification of the
user region in the job step in the Business Continuity
Manager agent startup cataloged procedure, correct
the memory requirements, and then restart the
Business Continuity Manager agent.
YKY016I CON
TASK(task-ID)
A task terminated abnormally during the Business
ABENDED,CODE=completion Continuity Manager agent start up. The Business
-code
Continuity Manager agent will be terminated.
task-ID
Name of the task
completion-code
YKY018I CON
MODULE(load-modulename) NOT FOUND
The load module shown as load-module-name was not

found. The Business Continuity Manager agent will be
terminated.
Make sure that the indicated load module was installed
correctly.
YKY019I CON
dd-name DD STATEMENT
NOT FOUND
The DD statement shown as dd-name is missing. The

Business Continuity Manager agent will be terminated.
Specify the DD statement in the cataloged procedure
used for starting the Business Continuity Manager
agent and then restart the Business Continuity
Manager agent.
YKY020I CON
THE PROFILE IS NOT

DEFINED IN THE FACILITY
CLASS OF RACF: xxxxxxxx
The STGADMIN.YKA.BCM.YKQUERY or
STGADMIN.YKA.BCM.COMMANDS profile is not defined in
the FACILITY class of the RACF.
Review the RACF settings and then restart the Business
Continuity Manager agent.
xxxxxxxx
YKY021I CON
A NAME/TOKEN WRITE
ERROR
OCCURRED,RC=returncode,NAME=name
The command cannot be executed because a NAME/

TOKEN write error occurred. The Business Continuity
Manager agent will now stop.
return-code
Return code set by the NAME/TOKEN registration
routine (IEANTCR)
name
Name registered in the NAME/TOKEN service
Messages
1-105
Message ID
YKY022I CON
Message text
THE SPECIFIED PREFIX IS

BEING USED BY ANOTHER
PROGRAM
YKY051I CON
AGENT ENDED
The Business Continuity Manager agent was

terminated.
YKY052I CON
AGENT IN SCHEDULED
SHUTDOWN
The Business Continuity Manager agent termination

processing has begun.
YKY053I CON
AGENT ABENDED
The Business Continuity Manager agent terminated

abnormally.
Check the initialization parameters.
If the cause is unknown, collect the ABEND dump in

the SYSABEND dump format and then contact customer
support for investigation.

Message ID
Message text
YKY100I CON
MODIFY COMMAND
ACCEPTED
The MODIFY command was accepted.
YKY101I CON
STOP COMMAND ACCEPTED
The STOP command was accepted.
YKY102I CON
INVALID error-type: text
After an entry of the MODIFY command, an error was

detected in the command or operand shown as text.
Check, and, if necessary, revise the command.
error-type
YKY103I CON
COMMAND SYNTAX ERROR
COMMAND: Indicates that an error was detected in

the command.
OPERAND: Indicates that an error was detected in

the operand.
The entered command has a syntax error.

Check, and, if necessary, revise the command.
YKY104I CON
OPERAND IS INCORRECT
The specified operand is invalid.

Correct the error and then re-enter the operand.
YKY111I CON
parameter-name WAS
CHANGED
The value of the initialization parameter has been

changed. The parameter name is given in parametername.
YKY114I CON
parametername=parameter-value
This message displays the current value of the

initialization parameter.
parameter-name
Initialization parameter name
parameter-value
Initialization parameter value
YKY130I CON
SESSION NO.=sessionnumber
This message displays the TCP/IP session number. This

message is followed by the TCP/IP session information.
session-number
1-106
Messages
Message ID
Message text

Session identification number
YKY131I CON
host-type PORT=portnumber HOST=IP-address
This message displays the port number and IP address

of the local or remote host. This message is followed by
the TCP/IP session information.
host-type
The type of host with the TCP/IP session
information displayed
LOCAL: Indicates that the host is a local host.
REMOTE: Indicates that the host is a remote host.
port-number
When LOCAL is displayed in host-type:

The port number of the local host
When REMOTE is displayed in host-type:

The port number of the remote host
IP-address
When LOCAL is displayed in host-type:

The IP address of the local host
When REMOTE is displayed in host-type:

The IP address of the remote host
YKY132I CON
CONNECTING START
TIME=YYYY/MM/DD
hh:mm:ss
This message displays the time the corresponding

TCP/IP session was established. This message is
followed by the TCP/IP session information.
YYYY/MM/DD hh:mm:ss
Time (local time)
YKY133I CON
LAST data-direction-type
TIME=YYYY/MM/DD
hh:mm:ss
This message displays the last transmission or

reception time in the corresponding TCP/IP session.
data-direction-type
The direction of the data that was sent at the time
displayed in YYYY/MM/DD hh:mm:ss
SEND: Indicates that the data was sent.
RECV: Indicates that the data was received.
YYYY/MM/DD hh:mm:ss
Time (local time)
Table 1-32 List of messages (message ID YKY3x - YKY5x)

Message ID
YKY300I SYS
Message text
hh:mm:ss task-ID,TCP
CONNECTION ACCEPTED

The TCP connection request was accepted. Information
about the communication with the remote host is
displayed in the YKY307I message.
hh:mm:ss
Message output time (local time)
task-ID
Messages
1-107
Message ID
Message text

Number used to identify the processing task that
output the message
YKY301I SYS
CONNECTION ENDED
NORMALLY
The TCP connection was released successfully.

hh:mm:ss
task-ID
output the message
YKY304I SYS
hh:mm:ss task-ID,REQUEST
DENIED,REASON=(reasonfor-denial)
The request was received, but was denied.

hh:mm:ss
task-ID
output the message
reason-for-denial
YKY305I CON
task-ID,TCP CONNECTION
LOST DURING EVENT
PROCESSING,TCPSTATUS=(reason-fordisconnection)
INVALID FORMAT: The format is invalid.
VERSION MISMATCH: The version does not match.
The TCP connection was lost during TCP/IP processing

for the reason shown as reason-for-disconnection.
Determine the cause of disconnection from the remote
host.
task-ID
output the message
reason-for-disconnection
YKY307I SYS
CONNECTION
INFORMATION,REMOTEHOST=IP-address,REMOTEPORT=remote-portnumber,LOCAL-PORT=localport-number
FIN ACCEPT: A disconnection request (TCP-FIN)

from the remote host was received.
RST ACCEPT: A disconnection request (TCP-RST)

from the remote host was received.
The TCP connection request was accepted.

Take appropriate action according to the message that
was displayed before this message.
hh:mm:ss
task-ID
output the message
IP-address
IP address of the remote host
remote-port-number
Port number of the remote host
local-port-number
Port number of the local host
1-108
Messages
Message ID
YKY315I CON
Message text
task-ID,COMMUNICATION
ERROR,@API[,requestname[,RC=response-code]]
[,EC=event-code]
[,SRC=local-IPaddress:local-port-number]
[,DST=connection-target-IPaddress:connection-targetport-number]
A communication error was detected. The message

displays the request name, the target IP address:target
port number (decimal number), and the local IP
address:local port number (decimal number).
The currently executing process is canceled. If
necessary, check the YKY330I message that was
displayed immediately before this message to
determine the cause of the error.
task-ID
output the message
request-name
@OPNSAP: Preprocessing
@OPEN: Processing for establishing a connection
@SEND: Send processing
@RECV: Receive processing
@CLOSE: Processing for releasing the connection
@QUERY: Remote address search processing
@ABORT: Forcibly releasing the connection
@QUIT: Postprocessing
response-code
Code generated during the request shown as
request-name
event-code
Event that occurred during the TCP/IP session
local-IP-address
IP address of the local host
local-port-number
Port number of the local host
connection-target-IP-address
IP address of the connection target host
connection-target-port-number
Port number of the connection target host
YKY321I CON
task-ID,COMMUNICATION
TIMED OUT
There is no response within the specified response wait

time. The connection will be released.
Check the cause of the response timeout.
task-ID
output the message
YKY330I CON
SOCKET API FAILURE

(maintenanceinformation,requesttype,return-code,errornumber)
The request shown as request-type resulted in an error

on the socket interface for IBM TCP/IP for MVS.
return-code and error-number indicate the error
information.
Check the cause of the error and take appropriate
action. If TCP/IP has stopped due to the error, stop the
Messages
1-109
Message ID
Message text

Business Continuity Manager agent. Once the error is
corrected, start the TCP/IP program, and then start the
Detailed information used for error analysis
request-type
One of the following request types is displayed:
"ACCEPT "
"BIND "
"CLOSE "
"INITAPI "
"IOCTL "
"LISTEN "
"RECV "
"SETSOCKOPT "
"SOCKET "
For details about the return code (RETCODE) for the

request type and the error number (ERRNO), see the
Communications Server IP API Guide.
YKY362I CON
YKY500I SYS
RECEIVED DATA SIZE

INVALID,DST=connectiontarget-IPaddress:connection-targetport-number
The Business Continuity Manager agent received an

invalid size of data from connection-target-IPaddress:connection-target-port-number. The
corresponding receive processing will be stopped.
RESULT OF UPDATING THE

CONFIGURATION FILE:
result
This message indicates whether the configuration file

was successfully updated.
The size of data that can be received is 4,096 bytes.

Check, and, if necessary, revise the received data size,
and then re-execute the operation.
If the configuration file failed to be updated, see the

other error message that was output with this one and
take appropriate action.
result
Indicates the result.
YKY501E XML
Disk configuration definition

error-type error. file
SUCCESS: The update succeeded.
FAILURE: The update failed.
An error occurred in the disk configuration definition

file. See the error-type, and then remove the error.
After that, retry the operation from Replication
Manager.
error-type
ALLOCATE: An allocation error

Make sure that the file indicated by file exists.
EXECIO: An input error

Make sure that the file indicated by file has not
been broken.
1-110
Messages
Message ID
Message text
format: An XML format error

Make sure that the XML description does not
contain an error.
file
Name of the disk configuration definition file in
which an error occurred
YKY502E XML
Configuration file DELETE

error. file
During the update process for the configuration file, an

error occurred during the attempt to delete the old
configuration file. Remove the error, and then take the
following action:
1.
If the configuration file in which the error occurred

still exists, delete it.
2.
Change the name of the temporary file to the

name indicated by file.
For details on names of temporary files, see the
chapter that explains linking with Replication
Manager in the Hitachi Business Continuity
Manager Installation Guide.
3.
Restart the Business Continuity Manager agent,

and then refresh the configuration file from
Replication Manager.
file
Name of the configuration file in which an error
occurred
YKY503E XML
Temporary file error-type

error. file
An error occurred in the temporary file. Check whether

the temporary file indicated by file exists. If the error
type is RENAME and the temporary file exists, change
the name of the temporary file to the name of the
configuration file that you want to update. After that,
restart the Business Continuity Manager agent, and
then refresh the configuration file from Replication
Manager. If the error type is something other than
RENAME and the temporary file exists, delete the
temporary file.
error-type
READWRITE: An I/O error
DELETE: A deletion error
RENAME: A renaming error
file
Name of the temporary file in which an error
occurred
YKY507E XML
Routelist configuration file

error error-type. file
An error occurred in the route list definition file. See

the error-type, and then remove the error. After that,
retry the operation from Replication Manager.
error-type

Make sure that the file indicated by file exists.
Messages
1-111
Message ID
Message text

Make sure that the file indicated by file has not
been broken.

contain an error.
file
Name of the route list definition file in which an
error occurred

Message ID
YKY600I CON
Message text
INSUFFICIENT SPACE
AVAILABLE. maintenanceinformation

The area allocation by the Business Continuity Manager
agent failed. The Business Continuity Manager agent
will be terminated.
Increase the region size and then restart the Business
Continuity Manager agent.
Detailed information used for error analysis
YKY604I CON
IRXJCL MODULE
ERROR,CODE=return-code
The IRXJCL routine returned an error with the return

code shown as return-code. The Business Continuity
Manager agent will terminate the processing.
Check the return code. If the return code is 20, the
SYSEXEC DD statement might be invalid in the
cataloged procedure used for starting the Business
Continuity Manager agent. Check, and, if necessary,
revise JCL, and then re-execute.
return-code
YKY605I CON
1-112
IRXINIT MODULE
ERROR,CODE=returncode,R0=abnormaltermination-code-andreason-code-for-abnormaltermination,PARM7=reasoncode
20: Processing failed. The EXEC processing was not

performed.
20021: The parameter list passed to IRXJCL was

invalid.
The IRXINIT routine returned an error with the return

code shown as return-code. The Business Continuity
Manager agent will terminate the processing.
return-code
20: Processing failed due to an error. Check the

reason code that was returned to PARM7 by
IRXINIT.
100: Processing failed because the system

terminated abnormally while IRXINIT was
checking the environment. The system might
output multiple messages reporting abnormal
termination. R0 includes the abnormal termination
Messages
Message ID
Message text

code and the reason code for abnormal
termination.
IRXINIT returns the abnormal termination code set
in the two trailing bytes of R0. IRXINIT returns the
reason code for abnormal termination set in the
two leading bytes of R0. If the reason code for
abnormal termination is larger than two bytes,
IRXINIT returns only the two trailing bytes of the
reason code for abnormal termination. For details
about the abnormal termination code and reason
code, see the MVS System Codes.
reason-code
For details about the reason code, see the TSO/E
REXX Reference.
YKY606I CON
IRXTERM MODULE
ERROR,CODE=returncode,R0=abnormaltermination-code-andreason-code-for-abnormaltermination
The IRXTERM routine returned an error with the

indicated return code. The Business Continuity Manager
agent terminates the processing.
return-code
For details about the return code, see the TSO/E
REXX Reference.
R0 includes the abnormal termination code and the
reason code for abnormal termination. IRXTERM
returns the abnormal termination code set in the
two trailing bytes of R0. IRXTERM returns the
reason code for abnormal termination set in the
two leading bytes of R0. If the reason code for
abnormal termination is larger than two bytes,
IRXTERM returns only the two trailing bytes of the
reason code for abnormal termination. For details
about the abnormal termination code and reason
code, see the MVS System Codes.
YKY680I SYS
hh:mm:ss taskID,command,RC=returncode[,text]
A command that was issued by the Business Continuity

Manager agent ended with return-code. Messages for
detected errors are output to text.
If the number of characters in the message output by
the command exceeds 126, it will be displayed on
multiple lines. The maximum number of message lines
for a single command is 10.
hh:mm:ss
task-ID
Identification number of the processing task to
which the message was output
command
Messages
1-113
Message ID
Message text

Name of the command that the Business
Continuity Manager agent executed
return-code
Return code from the command that the Business
text
Message (maintenance information) that was
output by the command that the Business
YKY699I CON
AGENT FUNCTION ABEND

CODE=Sxxx Uxxxx
DATE=yy-mm-dd
TIME=hh:mm:nn
The main task or subtask terminated abnormally during

the Business Continuity Manager agent processing. If
the task cannot be recovered, the Business Continuity
Manager agent will be terminated.
ABENDED-MODULE=module- Contact the center administrator.

name C-DATE=moduleSxxx (hexadecimal)
creation-date
System completion code when the task terminated
BASE=bbbbbbbb DISP=dddd
abnormally
[CALLING-MODULE=modulename C-DATE=y'y'.m'm'.d'd' Uxxxx (decimal number)
BASE=bbbbbbbb
DISP=dddd]
User completion code when the task terminated

abnormally
PSW=pppppppp pppppppp
ILC=ll INTC=xx
yy-mm-dd
REGISTERS AT TIME OF
FAILURE
hh:mm:nn

Date the task terminated abnormally

Time the task terminated abnormally
module-name
Section name of the Business Continuity Manager
agent module or the load module name
If the module cannot be identified, UNKNOWN is
displayed. When UNKNOWN is displayed, the values
indicated by y'y'.m'm'.d'd' and bbbbbbbb are not
correct.
module-creation-date
This is displayed in one of the following formats:

y'y'.m'm'.d'd': Creation date of the module

indicated by module-name
y'y'/m'm'/d'd': Creation date of the module
indicated by module-name
bbbbbbbb
Contents of the base register
dddd
ABENDED-MODULE: Location where ABENDED-MODULE

CALLING-MODULE: Location where CALLING-MODULE

pppppppp pppppppp
PSW during the abnormal termination
1-114
Messages
Message ID
Message text

ll
Length of command during the abnormal
termination
xx
Interrupt code during the abnormal termination
Table 1-34 List of messages (message ID YKY7x - YKY9x)

Message ID
YKY703E XML
YKY704E XML
Message text
XML translation error: The

sent entity is not XML.
This is an XML error. The sent entity is not XML.
End of request was detected

in the comment.
The end of the XML request was detected in the

comment.
Check, and, if necessary, revise the request coding.
Check, and, if necessary, revise the comment.

YKY705E XML
End of request was detected

in an element.
The end of the XML request was detected in an

element.
Check, and, if necessary, revise the last element in the
XML request.
YKY706E XML
The number of elements

exceeded the allowed limit.
The number of element hierarchies exceeded the

permitted maximum value (16).
Check, and, if necessary, revise the request.
YKY707E XML
YKY713E XML
The request version is a

mismatch.
The API version of the XML request is not supported.

Make sure that the version is supported by the
An invalid element 'element- An invalid element-name was specified in the XML

name' was specified in the
request.
XML request.
Check, and, if necessary, revise the specified request.
element-name
Element name
YKY714E XML
An invalid parameter
'parameter-name' was
specified in the XML request
element 'element-name'.
An invalid parameter-name was specified in the XML

request element element-name.
element-name
Element name
parameter-name
Parameter name
YKY715E XML
An invalid value was

specified for the parameter
'parameter-name' in the XML
request element 'elementname'.
An invalid value was specified for parameter-name in

the XML request element element-name.
element-name
Element name
parameter-name
Parameter name
Messages
1-115
Message ID
YKY716E XML
Message text
An invalid child element

'child-element-name' was
specified in the XML request
element 'parent-elementname'.
An invalid child element child-element-name was

specified for the parent element name parent-elementname in the XML request. If the parent element name
cannot be acquired, parent-element-name is set to
null.
parent-element-name
Parent element name
child-element-name
Child element name
YKY717E XML
A required element is
missing from the request.
'element'
A required element is missing in the request.

Check, and, if necessary, revise the element
specification in the request.
element
Name of the missing element
YKY718E XML
A required parameter is
missing from the element
'element-name' of the
request. 'parameter-name'
A required parameter is missing in the element.

Check, and, if necessary, revise the corresponding
element specification in the request.
element-name
Element name
parameter-name
Name of the required parameter
YKY719E XML
There is a conflict with

element 'element-name'.
The end tag for the element shown as element-name

does not have a paired start tag, or the
correspondence between the end and start tags is
invalid.
Check, and, if necessary, revise the corresponding
element specification in the request.
element-name
Element name
YKY720E XML
The request failed because

the prefix 'prefix' was not
found in the Agent
initialization parameter.
The requested prefix was not found among the

Business Continuity Manager agent initialization
parameters.
Check and if necessary revise the specified request.
prefix
Requested prefix
YKY726E XML
Configuration file error

CGname 'cgname' errortype.
The copy group definition information could not be

acquired because the error indicated by error-type
occurred in the configuration file.
cgname
Copy group name
error-type

Make sure that the copy group cgname
configuration file exists.
1-116
Messages
Message ID
Message text

Make sure that the configuration file of the copy
group cgname has not been broken.

contain an error.
version: A version error

Make sure that the definition information version is
correct.
YKP2A: A definition-creation program error

The requested operation cannot be performed
because the configuration file of the copy group
cgname was created by the mainframe agent
YKP2A command.
YKY727E XML
YKY728E XML
YKY729E XML
This request cannot be

executed without valid
authorization.
The user does not have authorization to perform the

requested operation.
The information in
configuration file was
updated after you obtained
it.
The information in the configuration file has been

updated since it was last obtained.
Configuration file is invalid.

file
The contents of the configuration file are invalid.
Change the MODE parameter in the initialization

parameters to EDIT, and then retry the operation.
Refresh the configuration file from Replication Manager,

and then retry the operation.
See the other error message that was output with this
message, and then use Replication Manager to correct
the error. After that, update the configuration file
again.
file
Name of the configuration file in which an error
was detected
YKY730E XML
YKY999E TSO
CON
INVALID CT Group is
specified.
The specified consistency group is invalid.
MFAgent cannot use this

REXX exec library.
A REXX script that cannot be used by mainframe agent

was executed.
Make sure that the specified C/T group exists in the

copy group definition file.
Check the REXX Exec library connected to SYSEXEC dd

name.
Table 1-35 List of messages (message ID YKZ0x)

Message ID
YKZ000T TSO
SC=48
Message text

Invalid parameters were specified.
For details, see the reason code in the YKZ099I
message displayed after this message. For more
information about reason codes, see IKJPARS in the
Messages
1-117
Message ID
Message text
YKZ001E TSO
MSG SC=48
No parameter-name()
supplied
Nothing is assigned to the parameter identified by

parameter-name.
YKZ002E MSG
SC=48
parameter-name() does not

include trailing "."
The last character of the string assigned to the

parameter identified by parameter-name is not a
period.
YKZ003E MSG
SC=48
parameter-name() value
invalid
The value assigned to the parameter identified by

parameter-name is invalid.
YKZ004E MSG
SC=48
Device# DEVN() is not

found.
The device specified in the DEVN parameter does not

YKZ008E MSG
SC=48
parameter-name() not valid

hex
The value specified in the parameter identified by

parameter-name is not in hexadecimal format.
YKZ010E MSG
SC=48
REXX failure return

variable name
An attempt to access the REXX variable identified by

name has failed.
nnnn
YKZ050E MSG
SC=36 RC=36#
(attribute-value)
Invalid attribute name
The value of the REXX variable with the name identified

by name is invalid.
name
REXX variable name
attribute-value
REXX variable value
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
YKZ066E MSG
SC=48 RC=48

found.
The route list to be processed cannot be found.
YKZ099I TSO
SC=0
command-name command
return code=nnnn, reason
code=rrrr
The command identified by command-name terminated

with the return code nnnn, and the reason code rrrr.
Check the ROUTE parameter, DAD parameter, route list

definition file, and command device definition file
specified in the YKLOAD command execution.
nnnn
Table 1-36 List of messages (message ID YKZ10x - YKZ20x)

Message ID
YKZ103E MSG
SC=48
1-118
Message text
invalid

Messages
Message ID
YKZ201E MSG
CON PRT SC=44
RC=44#
Message text
A GETMAIN error occurred.
(return code=nnn,
size=mmm, area=area,
cmd=xxx, pos=yyy)

The command cannot be executed because a GETMAIN
error occurred.
Expand the job execution area, and then re-execute
the command.
Return code from the GETMAIN macro
mmm (decimal number)
Area size
area (string)
HIGH must be equal to or greater than 16 MB; LOW
must be less than 16 MB.
xxx (decimal number)
Command code of the command that was
executing when the error occurred
0: YKLOAD, tool, or any command
1: YKMAKE
2: YKSCAN
3: YKQUERY
4: YKRESYNC
5: YKSUSPND
6: YKDELETE
7: YKEWAIT
8: YKRECVER
9: YKSTATS
10: Remote Scan Function, NG Scan Function
11: YKBLDPTH
12: YKDELPTH
13: YKQRYPTH
14: YKFCSTAT
15: YKQEXCTG
16: YKFREEZE
17: YKRUN
18: YKBLDCMD
19: YKQRYDEV
20: YKDELCMD
yyy (character string)
# If this message is output when the log and trace are
obtained, the RC is 0.
YKZ202E MSG
TSO CON SC=52
RC=0
A Logical error occurred.

(reason code=nnn,
cmd=xxx, pos=yyy)
Logical contradiction occurred.

Reason code (maintenance information)
Messages
1-119
Message ID
Message text

See the command code description in the
explanation of the YKZ201E message.
yyy (string)
YKZ203E TSO
RC=40#
A REXX read error occurred.

(return code=nnn, name=
name, cmd=xxx, pos=yyy)
The command cannot be executed because an REXX

read error occurred.
If the nnn value is 40:

Check that the REXX program is running in the
TSO/E environment, and then re-execute the
command.
If the nnn value is not 40:

Correct the configuration file (XML) and the values
assigned to the parameters.
If the value is 52, it is probable that a
configuration file (XML) being edited is specified.

Return code from the OS's REXX variable access
routine
name (string)
REXX variable name
yyy (string)
# If the REXX variable that the system tried to read
does not exist, 36 is returned. Also, if this message is
output while the YKLOAD command is being executed,
the RC is 44.
YKZ204E TSO
RC=40#
A REXX write error occurred. The command cannot be executed because an REXX
(return code=nnn, name=
write error occurred.
name, value=value,

cmd=xxx, pos=yyy)
Expand the job execution area, and then reexecute the command.

Check that the REXX program is running in the
TSO/E environment, and then re-execute the
command.
If the nnn value is not 32 or 40:

Correct the configuration file (XML) and the values
assigned to the parameters.
1-120
Messages
Message ID
Message text

If the error still exists after the above action has been
taken, contact your Hitachi Data Systems
Return code from the OS's REXX variable access
routine
name (string)
REXX variable name
value (string)
REXX variable value
yyy (string)
YKZ205E TSO
RC=0
A Parameter error occurred.

(detail=message-text,
cmd=xxx, pos=yyy)
The command cannot be executed because a

parameter error occurred.
message-text (string)
Message text
yyy (string)
YKZ206E TSO
RC=0
An I/O error occurred.

(detail=message-text,
cmd=xxx, pos=yyy)
The command cannot be executed because an I/O

error occurred.
Message text
yyy (string)
YKZ207E MSG
TSO CON SC=52
RC=44#
A Core process error

occurred. (detail=messagetext, cmd=xxx, pos=yyy)
The command cannot be executed because a Core

processing error occurred.
Message text
Messages
1-121
Message ID
Message text

The message text will be as shown below:
If an OS macro error occurred:

xxxxxxxx macro error, return code = rr, devn
= dddd
xxxxxxxx: OS macro name
rr: Return code from the macro
dddd: device number
If system name acquisition failed:

ASASYMBM macro error, rc = rr
rr: Return code of ASASYMBM macro
If the log stream definition is not DASD-dedicated:

Not DASD-only Logger definition
If the MAXBUFSIZE of the log stream definition is

not 64000:
MAXBUFSIZE of Logger definition invalid
If this message is displayed as maintenance

information (1):
ENTRYID ( eeeee ) for MSGID ( nnn ) is
invalid
eeeee, nnn: Maintenance information
If this message is displayed as maintenance

information (2):
ENTRYID ( eeeee ) for TYPE ( ttt ), LEVEL
( lll ) is invalid
eeeee, ttt, lll: Maintenance information

yyy (string)
YKZ208I TSO
CON PRT RC=0
The Core
processing( process )
started.
(DATE=yyyy/mm/dd,
TIME=hh:mm:ss.th,
TOD=ttt, cmd=xxx,
pos=yyy)
Core processing is starting.

process (string)
Processing name
yyyy/mm/dd (string)
GMT date
hh:mm:ss.th (string)
GMT time
ttt (string)
GMT time format
1-122
Messages
Message ID
Message text

yyy (string)
YKZ209I TSO
CON PRT RC=0
The Core
Core processing is terminating.
processing( process ) ended. process (string)
(DATE=yyyy/mm/dd,
Processing name
TIME=hh:mm:ss.th,
TOD=ttt, cmd=xxx,
yyyy/mm/dd (string)
pos=yyy)
GMT date
hh:mm:ss.th (string)
GMT time
ttt (string)
GMT time format
yyy (string)

Message ID
Message text
YKZ210E MSG
TSO CON SC=40
RC=44#
A NAME/TOKEN read error

occurred. (return code=nnn,
name= name, cmd=xxx,
pos=yyy)

TOKEN read error occurred.
Check that the YKLOAD command terminated normally.
Return code set by the NAME/TOKEN read routine
(IEANTRT)
name (string)
Name registered in the Name/Token service
yyy (string)
Messages
1-123
Message ID
YKZ211E MSG
CON SC=40
RC=44#
Message text
A NAME/TOKEN write error
pos=yyy)

TOKEN write error occurred.
Return code set by the NAME/TOKEN registration
routine (IEANTCR)
name (string)
Name registered in the Name/Token service
yyy (string)
YKZ212W CON#
RC=0

(return code=nnn,
cmd=xxx, pos=yyy)

Return code of the FREEMAIN macro
yyy (string)
# If this message is output at a time other than when
the log and trace are obtained, the YKZ212W message is
not output to the console, but is recorded in LOG and
TRACE. Processing will then continue.
YKZ215W MSG
CON SC=0 RC=0
A GTRACE error occurred.

(return code=nnn, id=mmm,
length=lll, cmd=xxx,
pos=yyy)
A GTRACE macro error occurred.

If this message appears frequently, stop acquiring GTF
traces for the USR trace (TRACE=USR). If the cause of
the error is insufficient capacity in the trace buffer or
trace data set, increase the capacity, and then restart
GTF.
Return code of the GTRACE macro
Event ID
lll (decimal number)
Length of trace data
1-124
Messages
Message ID
Message text

yyy (string)
YKZ216E TSO
RC=0
The Trace table is not

initialized. (cmd=xxx,
pos=yyy)
The trace table is not initialized.

yyy (string)
YKZ217E MSG
CON PRT SC=0
RC=0
A Logger error occurred.

(return code=nnn, reason
code=mmm, name=name,
cmd=xxx, pos=yyy)
A system logger service error occurred. Without

outputting the BCM log, processing for the CLI
command continues.
Return code of the system logger service macro
Reason code from the system logger service macro
(maintenance information)
name (string)
System logger service macro name
yyy (string)
YKZ218I CON
PRT RC=0
Output log count=nnn.
The number of output log data records is nnn.

Number of log data records
YKZ219W CON
RC=0
A LOAD error occurred.

(return code=nnn, reason
code=mmm, name=name,
cmd=xxx, pos=yyy)
A LOAD macro error occurred.

Return code from the LOAD macro
Reason code from the LOAD macro (maintenance
information)
name (string)
Load module name
Messages
1-125
Message ID
Message text

yyy (string)
YKZ220T MSG
SC=36 RC=36#
Copy type value null or

invalid.
The copy type is NULL or invalid.

Correct the configuration file, and then re-execute the
YKLOAD command.
value
REXX variable value
YKZ220T MSG
SC=36 RC=36#
Group ID value null or

invalid.
The consistency group ID of the copy group structure is

NULL or invalid.
YKLOAD command.
value
REXX variable value
YKZ220T MSG
SC=36 RC=36#
Minimum interface level

value null or invalid.
IFType is NULL or invalid.

Correct the content of the configuration file.
value
IFtype
YKZ220T MSG
SC=36 RC=36#
Number of pair-groups value The number of copy pairs contained in the copy group
null or invalid.
structure is NULL or invalid. Correct the configuration
file, and then re-execute the YKLOAD command.
value
REXX variable value
YKZ220T MSG
SC=36 RC=44
Number of Route dad-id is

invalid.
The number of routes related to dad-id is invalid.

Check whether the device address domain ID specified
in the YKLOAD command is invalid or correct the
configuration file, and then re-execute the YKLOAD
command.
dad-id
Device address domain ID
YKZ222E MSG
SC=36 RC=36#
(pair-index)
1-126
volume DEVN devicenumber invalid
The device number of the volume is invalid.

If the volume is not connected to the host in use, check
the values of the DAD and ROUTE parameters specified
in the YKLOAD command and the contents of the route
list definition file.
Messages
Message ID
Message text

volume
If volume is Primary: P-VOL.
If volume is Secondary: S-VOL.
device-number
Device number
pair-index
YKZ224E MSG
SC=8 RC=36#
(pair-index)
Primary device does not

support TCA
TrueCopy Asynchronous cannot be used on a storage

system with a P-VOL.
Use a device that supports TrueCopy Asynchronous.
pair-index
YKZ224E MSG
SC=12 RC=36#
(pair-index)
Secondary device does not

support TCA
TrueCopy Asynchronous cannot be used on a storage

system with an S-VOL.
Use a device that supports TrueCopy Asynchronous.
pair-index
YKZ225E MSG
SC=36 RC=36#

not support SI or TC Group
ID membership.
This group contains copy pairs that do not support

ShadowImage or TrueCopy Group ID.
YKLOAD command.
YKZ226E MSG
SC=36 RC=48#
stemTCA_MAP=TRK not
supported by some group
pairs
For the specified model, TRK cannot be specified for

TCA_MAP in the TrueCopy Asynchronous options.
Correct the contents of the configuration file.
stem
Stem name
YKZ227E MSG
SC=36 RC=36#
stemTCA_FLOWCONTROL=N Some copy pairs in this group do not support

not supported by some
TCA_FLOWCONTROL=N.
group pairs.
YKLOAD command.
stem
Messages
1-127
Message ID
Message text

Stem name
YKZ228E MSG
SC=36 RC=36#
(pair-index)
Invalid pair attribute name = The value of the REXX variable is invalid.
value
Check that the value is specified according to the
following rules:
The command control address must consist of 2

digits.
The control unit number must consist of 2 digits.
The storage subsystem ID (SSID) must consist of

4 digits.
The storage system serial number must consist of

5 digits.
The device number must consist of up to 4 digits.
name
REXX variable name
value
Value
pair-index
YKZ229I MSG
SC=0 RC=0
The time specified with

ATTIME has past. The
specification of ATTIME is
ignored.
The time assigned to the ATTIME parameter has

elapsed. Processing will continue, ignoring the
specification of the ATTIME parameter.
YKZ230W MSG
SC=4 RC=4
(pair-index)
Management for the relevant Processing for the volume was skipped because the
volume was skipped. DEVN
status of the volume did not allow this command to be
executed. If 0 is displayed in the location that indicates
the copy pair corresponding to the pair-index, multiple
volumes within the copy group have been skipped.
Change the status of the copy pairs to a status that
allows this command to be executed.
device#
Device number
displayed.
SN
displayed.
CU#
Control unit number
CCA#
1-128
Messages
Message ID
Message text

pair-index
YKZ231E MSG
SC=44 RC=44
Necessary Routelist or DEVN

information is not found.
The route list or device number information is missing

although it is required for processing to continue.
Correct the value assigned to the ROUTE or DAD
parameter passed to the YKLOAD command.
YKZ232T MSG
SC=36 RC=44
Number of Copy Groups

value invalid.
The number of copy groups is invalid.

value
Number of copy groups
YKZ233E MSG
SC=36 RC=36#
(attribute-value)

name

this command.
YKLOAD command.
name
REXX variable name
attribute-value
REXX variable value
YKZ234E MSG
SC=36 RC=36#
Storage system model value

null or invalid
The storage system model value is NULL or invalid.

Correct the storage system model in the configuration
file, and then re-execute the command.
value
Storage system model
YKZ235E MSG
SC=36 RC=36#
dad-id APID is null.
No APID value is registered.

dad-id
YKZ236E MSG
SC=36 RC=36#
dad-id Interface number is

null.
No interface number is registered.

dad-id
Messages
1-129
Message ID
YKZ237E MSG
SC=36 RC=36#
Message text
Routelist attribute name is
null.

The command device group identified by name is not
specified.
Correct the contents of the configuration file.
name
REXX variable name
YKZ238E MSG
SC=36 RC=44
ATTIME SUSPEND remains in Suspension initiated by YKSUSPND ATTIME is still in

place. Pair operation process effect. Copy pair operation is canceled.
is canceled.
Re-execute the command after YKSUSPND ATTIME
processing ends.
YKZ239E MSG
SC=48 RC=48
The specified Copy Group

has no TrueCopy
Synchronous Group.
The specified copy group is not a TrueCopy copy group

with consistency group ID specified.
YKZ240E MSG
SC=48
The specified pair was not

found in the Copy Group.
(DEVN=P-VOL-devicenumber,S-VOL-devicenumber)
A copy pair corresponding to the device number

specified in the DEVN parameter was not found in the
copy group.
YKZ241W MSG
SC=4 RC=0
No I/O issued volume is in

Copy Group(s).
There is no volume eligible for I/O issuance.
YKZ242E MSG
SC=48 RC=48
The pair needs to be

swapping, but is not.
You cannot execute the YKRESYNC command to change

the copy direction before suspension, because the copy
pair status is not SWAPPING or the status of the copy
pairs has not been acquired.
Confirm that the copy group is a TrueCopy copy group

with consistency group ID specified and is a TrueCopy
copy group for which the Open/MF Consistency
attribute is not set. After that, re-execute the
command.
Check the volume status, correct errors involved in the

configuration or execution conditions if any, and then
re-execute the command.
Check the status of the volumes in the copy group,

correct the YKRESYNC command parameter
specification, and then re-execute the command.
When executing the YKRESYNC command with the
FORWARD/REVERSE parameter, execute the YKQUERY
command or YKEWAIT command to acquire the status
of the copy pairs immediately before the YKRESYNC
command.
YKZ243E MSG
SC=48 RC=48
YKZ244E MSG
SC=36 RC=36
Serial number of storage

system is not found in
Routelist.
ATTIME or CANCEL is specified together with SVOL.

Correct the YKSUSPND command parameter values, and
then re-execute the command.
The specified storage system does not exist in the
route list.
serial-number
1-130
Messages
Message ID
YKZ245E MSG
SC=48 RC=48
Message text
CopyGroup attribute
combination is invalid.
The combination of the specified command or the

operand, and copy group attribute is invalid.
Check the configuration file to make sure that the
configuration allows command execution, and execute
the command again.
YKZ246E MSG
SC=48 RC=48
This operation (operation)

does not support remote
command.
This operation is not supported when a remote function

is in use.
operation
Operation name
YKZ247E MSG
SC=44 RC=44
STEM(stem) information for Information on the specified stem name is missing.

Core Processing is not found. The YKLOAD command has not been executed or the
stem name does not match the stem name specified
for the YKLOAD command.
stem
Stem name
YKZ248E MSG
SC=44 RC=0
Necessary information for

Core Processing is not
stored. (STEM = stem)
Certain information required for CLI command

execution has not been registered.
Execute the YKLOAD command to register the
information.
stem#
Stem name
# The (STEM = stem) portion is displayed only when
the stem is obtained.
YKZ249E MSG
SC=48 RC=48#
(pair-index)
Specified DAD or ROUTE is

invalid.
The DAD or ROUTE parameter specified on the YKLOAD

command is invalid.
Correct the specification.
pair-index

Message ID
YKZ250E MSG
SC=40 RC=44
Message text
A NAME/TOKEN delete error
pos=yyy)

TOKEN delete error occurred.
Return code from the NAME/TOKEN registration
routine (IEANTCR)
name (string)
Name to be registered in the NAME/TOKEN service
Messages
1-131
Message ID
Message text

yyy (string)
YKZ251E MSG
SC=32 RC=32
(pair-index)
DASD device devicenumber-1(device-number-2)

management error,
message-text. (code1 code2,
cmd=xxx, pos=yyy)
Business Continuity Manager failed to complete the

requested processing.
Processing will continue with this device skipped.
Check the status of the error device, correct any errors
related to the configuration or execution conditions,
device-number-1 (string)
The device that issued I/O
The device to be manipulated
If the device number of the device to be operated
is not found, **** is displayed.
Message text
code1 (Hexadecimal number)
Subcommand code
Error code
For details about error codes, see XXX.
yyy (string)
pair-index
YKZ252E MSG
SC=8 RC=8

management error,
message-text. (code1 code2,
cmd=xxx, pos=yyy)

requested processing.
This device is skipped and processing continues.
Check the status of the error device, and fix the
problem in the configuration or execution condition if
any.
1-132
Messages
Message ID
Message text

Message text
Subcommand code
Error code
For details about the error codes, see XXX.
yyy (string)
YKZ253E MSG
SC=32 RC=32
(pair-index)

I/O error. (CC=code1
CSW=code2 code3 code4
code5, cmd=xxx, pos=yyy).
An I/O error occurred. Processing will continue with

this device skipped.
If a sense byte is set, the sense byte is indicated in the
YKZ255E message.
When CC=3:
The corresponding device might not be configured
or connected.
When CC=0 and CSW=xxxxxx0000xxxx (DSB=00,
CSB=00) where x indicates a value:
or connected.
When CC=0 and CSW=0000000006xxxx where x
indicates a value:
MIH might have occurred or a logical path might
not be connected.
code1 (decimal number)
CC information
CSW information
Subcommand code
Completion code
Messages
1-133
Message ID
Message text

Detailed code
yyy (string)
pair-index
YKZ254E MSG
SC=8 RC=8

I/O error. (CC=code1
CSW=code2 code3 code4
code5, cmd=xxx, pos=yyy).
An I/O error occurred. Business Continuity Manager

might not support this device. Processing will continue
with this device skipped.
If a sense byte is set, the sense byte is indicated in the
YKZ256E message.
When CC=3:
or connected.
When CC=0 and CSW=xxxxxx0000xxxx (DSB=00,
CSB=00):
or connected.
When CC=0 and CSW=00000000060000:
MIH might have occurred or a logical path might
not be connected.
code1 (decimal number)
CC information
CSW Information.
Subcommand code
Completion code
Detailed code
1-134
Messages
Message ID
Message text

yyy (string)
YKZ255E MSG
SC=32 RC=32
(pair-index)
DASD device deviceDetailed information on the I/O error is displayed.

number-1(device-number-2) device-number-1 (string)
sense: diagnosticThe device that issued I/O
information (cmd=xxx,
pos=yyy)
diagnostic-information (Hexadecimal number)
Sense byte information
yyy (string)
pair-index
YKZ256E MSG
SC=8 RC=8
DASD device deviceDetailed information on the I/O error is displayed.

number-1(device-number-2) device-number-1 (string)
sense: diagnosticThe device that issued I/O
information (cmd=xxx,
pos=yyy)
diagnostic-information (Hexadecimal number)
Sense byte information
yyy (string)
YKZ257E MSG
SC=32 RC=32
(pair-index)

management error.
(Message type: code1
Reason code: code2 Error
code: code3 code4,
cmd=xxx, pos=yyy)

requested processing. Processing will continue with this
device skipped.
Check the status of the device involving the error,
correct any errors related to the configuration or
command.
Messages
1-135
Message ID
Message text

Message type
Reason code
Error code
Subcommand code
yyy (string)
pair-index
YKZ258E MSG
SC=8 RC=8

management error.
(Message type: code1
Reason code: code2 Error
code: code3 code4,
cmd=xxx, pos=yyy)

requested processing. Business Continuity Manager
might not support this device. Processing will continue
with this device skipped.
Check the status of the device involving the error,
correct any errors related to the configuration or
command.
Message type.
Reason code
Error code
Subcommand code
1-136
Messages
Message ID
Message text

yyy (string)
YKZ259E MSG
SC=48 RC=48#
This product is already

executing.
The command cannot be executed because Business

Continuity Manager is running for another panel or
script.

Message ID
Message text
YKZ260I MSG
SC=0 RC=0
The volume has already

reached the target status.
Processing of some volumes was skipped because a

volume that has already reached the target status
exists.
YKZ261E MSG
CON SC=0 RC=0
The YKLOGnn DD statement

is not specified.
(cp=xxx:yyy)
No DD statement is specified in YKLOG01 or YKLOG02.

YKLOGnn
YKLOG01 or YKLOG02
yyy (string)
YKZ262E MSG
CON SC=0 RC=0
A YKLOGnn open error

occurred. (rc=nnn,
cp=xxx:yyy)
An open error occurred in YKLOG01 or YKLOG02.

YKLOGnn
YKLOG01 or YKLOG02
Return code from the OPEN macro
Command code of the command that was executed
when the error occurred
yyy (string)
YKZ263E MSG
CON SC=0 RC=0
A YKLOGnn I/O error. (text,

cp=xxx:yyy)
An I/O error occurred in YKLOG01 or YKLOG02.

YKLOGnn
YKLOG01 or YKLOG02
Messages
1-137
Message ID
Message text

text
Message acquired by the SYNADAF macro
yyy (string)
YKZ264E MSG
CON SC=0 RC=0
A YKLOGnn close error

occurred. (rc=nnn,
cp=xxx:yyy)
A close error occurred in YKLOG01 or YKLOG02.

YKLOGnn
YKLOG01 or YKLOG02
Return code from the CLOSE macro
yyy (string)
YKZ265E MSG
SC=48 RC=48
This operation (operation)

does not support the
reverse-resync mode.
The YKSUSPND command, which reverses the TrueCopy

Asynchronous or Universal Replicator copy direction,
does not support this operation.
operation
Operation name
YKZ266I PRT
RC=0
Parameters were input.

( nnn, xxx )
A parameter was entered from SYSIN.

Number of lines
xxx (character string)
Input parameter
YKZ267E MSG
CON SC=0 RC=0
A YKLOGnn DEVTYPE macro

error occurred. (rc=nnn,
reason=mmm, cp=xxx:yyy)
An error occurred in the DEVTYPE macro for YKLOG01 or

YKLOG02.
YKLOGnn
YKLOG01 or YKLOG02
Return code from the DEVTYPE macro
Reason code from the DEVTYPE macro
1-138
Messages
Message ID
Message text

yyy (string)
YKZ268E MSG
CON PRT SC=0
RC=0
Incorrect dataset format.

(DD name=ddd, KKK=AAA
must be BBB, cp=xxx:yyy)
The format of the dataset is invalid.

ddd
dd name
KKK
If DSORG is abnormal: DSORG
If RECFM is abnormal: RECFM
If LRECL is abnormal: LRECL
If BLKSIZE is abnormal: BLKSIZE
AAA
File attribute that encountered an error (* is
displayed when the file attribute is undefined or
immediately after dataset allocation)
BBB
Valid file attribute
yyy (string)

Message ID
YKZ270E MSG
SC=36 RC=36
(index1, index2)
Message text
Duplicate logical paths exist.

The logical path definitions for index1 and index2 are
duplicated.
Delete one of these definitions or make sure that the
duplicated logical path definitions are correct, and then
index1
The index number of one duplicated logical path
index2
The index number of the other duplicated logical
path
YKZ271E MSG
SC=12 RC=12
Definition of xxxxxxxx does

not match the actual
configuration. DEVN
The group definition does not match the actual pair

configuration. If GROUPID is displayed for unmatched
items or * is displayed on the device number, storage
system serial number, control unit number, or CCA
number, there is a copy pair which is not defined in the
copy group definition parameter, and which belongs to
Messages
1-139
Message ID
Message text

the same consistency group in the same control unit as
the P-VOL or S-VOL.
Check and correct the values of the copy group
definition parameters and re-execute the command.
xxxxxxxx
Items that do not match
COPYTYPE: Copy type
GROUPID: Consistency group ID or Open/MF
Consistency attribute
PAIR: Copy pair configuration
PATHID: Path group ID
device#
Device number
displayed.
SN
displayed.
CU#
Control unit number
CCA#
YKZ272W MSG
SC=8 RC=8
Variable(s) were changed for For the port numbers and number of physical paths,
the number of paths or
update the REXX variable, which indicates the port
portID.
numbers and number of physical paths, to match the
settings on the storage system.
YKZ273E MSG
SC=36 RC=36
No path to be operated exist No paths to be operated exist within the range

within the range specified by specified by the parameter.
the supplied parameter.
Check the parameters specified during command
execution, the path set name specified during the
YKLOAD command execution, and the attributes of the
path set (path type, shared attributes, storage system
serial numbers, and control unit numbers).
YKZ274E MSG
SC=36 RC=36
(index1, index2,
index3)
Duplicate ports exist in

FORWARD.
In the logical path definition for FORWARD index1, the

index2 and index3 port numbers are duplicated.
Delete one of the definitions or make sure that the
duplicated port numbers are correct, and then reexecute the command.
index1
Index number of the duplicated logical path
index2
Index number of one of the duplicated ports
1-140
Messages
Message ID
Message text

index3
Index number of the other duplicated port
YKZ274E MSG
SC=36 RC=36
(index1, index2,
index3)
Duplicate ports exist in

REVERSE.
In the logical path definition for REVERSE index1, the

index2 and index3 port numbers are duplicated.
Delete one of the definitions or make sure that the
duplicated port numbers are correct, and then reexecute the command.
index1
Index number of the duplicated logical path
index2
Index number of one of the duplicated ports
index3
Index number of the other duplicated port
YKZ275E MSG
SC=36 RC=36
Necessary Routelist or DEVN

information is not found.
The route list or device number information, required

for processing to continue, is missing.
Correct the value assigned to the ROUTE, DAD or PATH
parameter passed to the YKLOAD command. Make sure
that the specified volume has been scanned, because
this message is output when the volume for CU and CCA
specified in the path set definition file has not been
scanned.
YKZ276E MSG
SC=36 RC=36
Some of the storage systems A storage system using a path-controlled device or

do not support DKC type
remote disk controller control contains an IFType,
paths.
which is not supported for disk controller-type path
control.
In the configuration file, make sure that the storage
system is controllable (that the first two digits of the
IFType are X'11' or higher). Also, if scanning was not
performed after the storage system microcode was
replaced, perform another scan.
YKZ277W MSG
SC=4 RC=4
Some paths are in the

NOPATH state.
There is a logical path without a physical path

established.
YKZ278W MSG
SC=8 RC=8

MISMATCH state.
Logical paths were detected for which the port

information stored in the REXX variable did not match
the port information set on the storage system. The
port number or number of ports that have been set is
incorrect.
YKZ279W MSG
SC=12 RC=12

INVALID state.
Logical paths containing physical paths in the INVALID

status were detected from a storage system.

Message ID
YKZ280W MSG
SC=0 RC=0
Message text
Primary volume's IFType is

larger than Remote control's
IFType value.
The IFType of a storage system using the Remote DKC

Control Function is smaller than the IFType of the PVOL defined in the copy group. As such, the smaller of
Messages
1-141
Message ID
Message text

the two will be used when each command is executed.
Note that on some machine types, some functionality
might be lost. Also, if a scan was not performed after
the storage system microcode was replaced, perform
another scan.
value
IFType value of the remote storage system
YKZ280W MSG
SC=0 RC=0
Secondary volume's IFType

is larger than Remote
control's IFType value.
The IFType of a storage system using the Remote DKC

Control Function is smaller than the IFType of the SVOL defined in the copy group. As such, the smaller of
the two will be used when each command is executed.
Note that on some machine types, some functionality
might be lost. Also, if a scan was not performed after
another scan.
value
IFType value of the remote storage system
YKZ281E MSG
Some of the storage systems
SC=36 RC=36#1 do not support Remote
Control.
(Storage
System's-IFType)
The device specified during command device usage

does not support the Remote DKC Control Function.
Check whether the device can use the Remote DKC
Control Function #2, and then revise the Remote DKC
Control Function definitions.
Storage System's-IFType
IFType value of the storage system
#1
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#2
The Remote DKC Control Function can be used in a
storage system on the Lightning 9900V models (or
later) where the first two digits of the IFType are
X'04' or higher.
YKZ282E MSG
SC=36 RC=36#1
Primary device IFType does

not support UR.
Universal Replicator cannot be used on a storage

system that has a P-VOL or uses the Remote DKC
Control Function.
Use a device#2 that supports Universal Replicator. Also,
if a scan was not performed after the storage system
microcode was replaced, perform another scan.
IFType
IFType value
#1
#2
The Universal Replicator is used in a storage
system where the first two digits of the IFType are
X'11' or higher.
1-142
Messages
Message ID
YKZ282E MSG
SC=36 RC=36#1
Message text
Secondary device IFType
does not support UR.

Universal Replicator cannot be used on a storage
system that has an S-VOL or uses the Remote DKC
Control Function.
Use a device#2 that supports Universal Replicator. Also,
if a scan was not performed after the storage system
IFType
IFType value
#1
#2
The Universal Replicator is used in a storage
system where the first two digits of the IFType are
X'11' or higher.
YKZ283T MSG
SC=36 RC=36#
subCTGroupID value null or

invalid.
subCTGroupID in the copy group structure is either

NULL or invalid.
Correct the configuration file, and then execute the
YKLOAD command.
value
REXX variable value
YKZ284T MSG
SC=36 RC=36#
UR_MirrorID value null or

invalid.
UR_MirrorID in the copy group structure is either NULL

or invalid.
Correct the configuration file, and then execute the
YKLOAD command.
value
REXX variable value
YKZ285I MSG
SC=0 RC=0
(index)
This command cannot be

executed without a port.
The YKBLDPTH, YKDELPTH, and YKQRYPTH commands

cannot be executed for a logical path without a port
element both on primary and secondary direction. Only
the YKQRYPTH command with a RESTRUCT parameter
can be executed on a logical path without a port
element.
To execute one of these commands against a logical
path, correct the configuration file and then execute
the YKLOAD command.
index
Index number of the logical path without a port
element
YKZ286E MSG
SC=36 RC=36
(index)
YKQRYPTH command cannot When the YKQRYPTH command is executed on a storage

be executed if the volume on system that has not been directly connected to the
host for the path set of an inter-control unit logical
path, the volume belonging to the originally established
Messages
1-143
Message ID
Message text
the CU type path has not
been scanned.

inter- control unit of the inter-control unit logical path
must have been scanned at least once.
Make sure that the volume belonging to the targeted
control unit has been scanned at least once, and the
control unit and command control address defined for
the path set are correct. If the command control
address is not defined for the path set, from the Edit
Logical Path Definition panel, specify the command
control address of the volume scanned in the target
control unit for path control.
index
Index number of the logical path that cannot be
executed
YKZ287T MSG
SC=36 RC=36#
UR_PathID value null or

invalid.
UR_PathID in the copy group structure is either NULL

or invalid. Correct the configuration file, and then
execute the YKLOAD command.
value
REXX variable value
#
YKZ288E MSG
SC=36 RC=36
Some of the storage systems A path-controlled storage system does not support
do not support Path Group
path group IDs (path IDs for which values other than
ID.
00 are specified). Revise the definition associated with
whether the storage system can use path group IDs#.
Also, if a scan was not performed after the storage
system microcode was changed, perform a scan.
#
Path group IDs can be used for storage systems
for which IFType is X'3333' or higher.

Message ID
YKZ290E MSG
SC=48 RC=48
YKZ291I CON
SC=0 RC=0
Message text
FROMCU() exceeds number

of CU that storage system
supported.
The FROMCU has exceeded the maximum number of

control units that are supported by storage system.
The log dataset is full.

(DSN=ddd, cp=xxx:yyy)
The log dataset is full.
Specify the maximum supported number of control

units or less.
ddd
Name of the log dataset that became full
If a log dataset name cannot be collected, * is
displayed.
Command code for the command that was
executing when the log dataset became full
1-144
Messages
Message ID
Message text

See the description for the command code in the
YKZ201E message.
yyy (string)
YKZ292I CON
SC=0 RC=0
The log dataset was

switched. (from=YKLOGmm,
to=YKLOGnn, job=jjj,
cp=xxx:yyy)
The log dataset was switched.

YKLOGmm
Previous log dataset (YKLOG01 or YKLOG02)
YKLOGnn
New log dataset (YKLOG01 or YKLOG02)
jjj
Job name
Command code for the command that was
executing when the log dataset was switched
See the description for the command code in the
YKZ201E message.
yyy (string)
YKZ293E MSG
CON SC=0 RC=0
The specified value for the

system symbol &YKLOGPT is
invalid.
The value specified for the &YKLOGPT system symbol is

invalid. The program continues processing while
assuming LOGR.
Revise the value specified for the &YKLOGPT system
symbol.
YKZ294E MSG
CON SC=0 RC=0
An error occurred while

An error occurred while acquiring the &YKLOGPT system
acquiring the system symbol symbol. The program continues processing while
&YKLOGPT. (rc=rr)
assuming LOGR.
Revise the value specified for the &YKLOGPT system
symbol.
rr
The return code of the ASASYMBM macro
YKZ295E MSG
SC=36 RC=36
The version of this

configuration file is not
supported.
The version of this configuration file is not supported.
YKZ296E MSG
SC=44 RC=44
A JNLG is not registered in

EXCTG. (JNLG=jj,
MIRROR=m, EXCTG=e,
SN=ssssssssssss)
The journal group is not registered in EXCTG for the

storage system.
The journal group might not be registered in EXCTG
because the YKMAKE command has not been executed
for EXCTG, or an error occurred during the execution of
the YKMAKE command. Alternatively, the journal group
might be dissolved from EXCTG registration by
executing the YKRECVER command.
Remove the cause of the problem if the YKZ297E
message is output during the execution of the YKEWAIT
or YKQUERY command after executing the YKMAKE
command for EXCTG. Then execute the YKMAKE
command again with a SELECT(COND) specification to
Messages
1-145
Message ID
Message text

register the journal group in EXCTG for the storage
system.
Note that, to register an existing journal group in
EXCTG, you need to execute the YKQUERY command
before executing the YKMAKE command with a
SELECT(COND) specified. In this case, the YKZ296E
message will appear until the registration has
completed normally.
Also, if you execute the YKQUERY command to obtain
the status while a copy pair in EXCTG is dissolved, the
YKZ296E message sometimes appears when the
dissolving of the copy pair is detected at a different
time from the dissolving of EXCTG, but this does not
mean that an error has occurred. In this case, wait
until the copy pair status changes to SIMPLEX, and then
re-execute the YKQUERY command. The message will no
longer appear.
In 4x4x4 Delta Resync configurations, when all copy
pairs in EXCTG whose copy direction is from the
primary site to the remote site are dissolved, the
journal groups whose copy direction is from the local
site to the remote site are also dissolved from EXCTG
registration. For example, if a Delta Resync is executed
and then the YKDELETE command is executed when
EXCTG is in the HOLD status and the copy direction is
from the primary site to the remote site, the journal
groups whose status is DUPLEX and copy direction is
from the local site to the remote site are dissolved
from EXCTG registration. As a result, the YKZ296E
message is output if the YKQUERY command is executed
to obtain the status of Universal Replicator copy pairs
whose copy direction is from the local site to the
remote site. In this case, perform either of the
following operations to register journal groups in
EXCTG for the storage system:
Execute the YKMAKE HOLD command for Universal

Replicator copy pairs whose copy direction is from
the primary site to the remote site.
Execute the YKMAKE command with a

SELECT(COND) specified for Universal Replicator
copy pairs whose copy direction is from the local
site to the remote site.
JNLG (string)
The journal type not being registered (the journal
type of the definition, rather than of the storage
system)
R-JNL: Journal of the secondary site
M-JNL: Journal of the primary site
jj (hexadecimal number)
The journal group number (00-FF) specified by the
consistency group ID or sub consistency group ID
m (decimal number)
1-146
Messages
Message ID
Message text

Mirror ID (0-3)
e (decimal number)
EXCTG ID (0-3)
ssssssssssss (decimal number)
YKZ297E MSG
SC=44 RC=44
An error occurred while

adding JNLG to EXCTG.
(JNLG=jj, MIRROR=m,
EXCTG=e, SN=ssssssssssss,
CDEV=cccc, CODE=nnnn)
An error occurred while registering the journal group to

EXCTG.
Register the error code and determine the cause of the
problem. After removing the cause of the problem,
execute the YKMAKE command again with a
SELECT(COND) specification to register the journal
group to EXCTG.
This message is output until the corresponding EXCTG
registration process is executed using the YKMAKE
command again.
JNLG (string)
The journal type not being registered (the journal
type of the definition, rather than of the storage
system)
The journal group number specified by the
consistency group ID or the sub consistency group
ID (00-FF)
m (decimal number)
Mirror ID (0-3)
e (decimal number)
EXCTG ID (0-3)
cccc (hexadecimal number)
Arbitration command device number (0000-3FFF)
FFFF is displayed for the supervisor disk controller.
nnnn (hexadecimal number)
Error code
For details about the error codes, see XXX
YKZ298W MSG
SC=4 RC=4
Timeout limit has expired

while waiting for EXCTG
registration process.
Processing is terminating because the timeout limit has

expired while waiting for the EXCTG registration with
the YKEWAIT command.
Correct the timeout value or check that the status to
be monitored is correctly specified. Also, check if the
journal group is registered to EXCTG.
The REXX variable is invalid (remains as it was prior to
the YKEWAIT command) if this message is output.
Messages
1-147
Message ID
YKZ299E MSG
SC=36 RC=36
Message text
Definition of xxxxxxxx does
not match the actual
configuration. (JNLG=jj,
MIRROR=m, EXCTG=e,
SN=ssssssssssss,
CDEV=cccc)

EXCTG information defined in the copy group and
EXCTG information registered in the storage system do
not match.
Correct the copy group definition file. This message
might be output when the EXCTG ID specified in the
copy group definition is being used by another copy
group.
After removing the cause of the problem, execute the
YKMAKE command again with a SELECT(COND)
specification to register the journal group to EXCTG.
This message is output until the corresponding EXCTG
registration process is executed using the YKMAKE
command again.
xxxxxxxx
Items that do not match
CDEV: Arbitration command device number
JNLG: The storage system serial number identified
by ssssssssssss and the journal group number
identified by jj is registered to the EXCTG indicated
by e. However, it was not found in the
configuration file.
JNLG (string)
The journal type registered to the storage system
(the journal type of the storage system, rather
than of the definition)
The journal group number registered to the
storage system (00-FF)
m (decimal number)
The mirror ID registered to the storage system
(0-3)
e (decimal number)
The EXCTG ID registered to the storage system
(0-3)
The serial number registered to the storage system
cccc (hexadecimal number)
The arbitration command device number registered
to the storage system (0000-3FFF)
FFFF is displayed for the supervisor disk controller.
1-148
Messages

Message ID
YKZ300E MSG
TSO SC=44
RC=44
Message text
SVC # is null or invalid.

The user SVC is not registered, or the &YKSVCNO
system symbol of the IEASYMxx parmlib member is
specified incorrectly.
When the user SVC is defined in SVCPARM:
Make sure that the &YKSVCNO system symbol of the
IEASYMxx parmlib member is specified correctly.
When the user SVC is not defined in SVCPARM:
Register the user SVC by YKALCSVC command.
For details about registering a user SVC, see the
Hitachi Business Continuity Manager Installation Guide.
YKZ301E CON
RC=128
The task is not authorized to The task is not authorized to execute a CLI command.
execute the request. (reason The program will terminate abnormally with user
code=reason)
completion code 128 or will return an error.
reason
Reason code
For details, see the description for that user
completion code.
For details about how to set CLI command execution
permissions, see the Hitachi Business Continuity
Manager Installation Guide.
YKZ310I SYS
hh:mm:ss command
This log data indicates that a CLI command has been

issued.
hh:mm:ss
Time the CLI command was issued (local time)
command
Issued CLI command name and its parameters
A maximum of 109 characters can be output. If
109 is exceeded, the remainder are discarded.
YKZ311I SYS
hh:mm:ss command RC=rc
This log data indicates the result of a CLI command

execution
hh:mm:ss
Time the CLI command was issued (local time)
command
Issued CLI command name
rc
Return code for the CLI command
For details, see the command descriptions in the
Guide.
YKZ320E TSO
An error was detected during parameter analysis.
YKZ321E TSO
Time value is invalid.
The specified time value is invalid.
YKZ322E TSO
Specify SEC and MIN parm

exclusively.
The SEC and MIN parameters cannot be specified at the

same time.
Messages
1-149
Message ID
YKZ330E TSO
CON RC=64
Message text
command detected the

An error was detected in the REXX service.
service service error. (return command
code=r[, reason code=n][,
abend code=a])
service
Name of the REXX service or TSO/E service where
an error was detected
r (decimal number)
Return code from the REXX service or TSO/E
service
For details, see the TSO/E REXX User's Guide or
the TSO/E Programming Services.
n (decimal number)
Reason code from the REXX service or TSO/E
service
a (decimal number)
ABEND code from the REXX service or TSO/E
service
YKZ331E TSO
RC=64
command terminated with

an invalid return code. (r)
The CLI command terminated with an invalid return

code.
command
r
Return code that the CLI command created
YKZ332E TSO
RC=64
command detected the

system abend during rexxservice processing.
(code=sss, reason=rrrr)
An abnormal system termination was detected during

the REXX service processing.
command
rexx-service
Name of the REXX service where the abnormal
system termination was detected
sss (hexadecimal number)
For details, see the MVS System Codes.
rrrr (hexadecimal number)
Reason code
YKZ333E TSO
RC=64
command detected the user

abend during rexx-service
processing. (code=uuuu,
reason=rrrr)
An abnormal user termination was detected during the

REXX service processing.
command
rexx-service
1-150
Messages
Message ID
Message text

Name of the REXX service where the abnormal
user termination was detected
uuuu (decimal number)
User completion code
For details, see the MVS System Codes.
rrrr (hexadecimal number)
Reason code
YKZ340T TSO
RC=48
YKZ341E TSO
RC=48
No DEVN() supplied.
YKZ343E TSO
RC=48
DEVN() value invalid.
The value specified in the DEVN parameter is invalid.
YKZ350T TSO
RC=16
Invalid parameters have

been specified.
YKZ351E TSO
RC=16
No error code has been

specified.
No error code has been specified.
YKZ352E TSO
RC=16
The specified error code is

invalid.
The specified error code is invalid. A possible cause is

as follows:
YKZ353E TSO
RC=64
YKZ354I TSO
RC=8
YKZ370E MSG
SC=32 RC=32
Load module is not found.
The specified value is not a four-digit hexadecimal

value.
The load module cannot be found. Possible causes are

as follows:
The library dataset has not been concatenated.
The module is protected by the RACF program

control function.
A description for the

specified error code was not
found.
A description for the specified error code was not

found.
change was detected during
specified command
processing. DEVN device#
A dynamic change in an I/O configuration definition

was detected during processing of the command.
For details on error codes, see XXX. If the error code is

not listed in the manual, contact your Hitachi Data
Systems representative or authorized service provider.
Check the status of the device targeted by the

command, correct any errors related to the
configuration or execution conditions, and then reexecute the command.
device#
definition
YKZ371I TSO
YKENV command return

code=return-code.
The YKENV command terminated.

return-code
Return code issued by the YKENV command
Messages
1-151

Message ID
YKZ400E MSG
SC=48 RC=48
Message text
param parameter cannot be
specified for copy-type Copy
Group.

The parameter indicated by param cannot be specified
for a copy group with a copy type of copy-type.
Check the copy type and the parameter.
param (string)
The parameter name which cannot be specified
copy-type (string)
The copy type specified for the copy group
YKZ401E MSG
SC=48 RC=48
Some of the storage systems The storage system which the command is issued onto,
do not support param.
or the storage system which uses the Remote DKC
Control Function, does not support the parameter
indicated by param.
Use a device which supports the parameter indicated
by param. Also, if a scan has not been performed after
another scan.
param (string)
The parameter name which is not supported
YKZ402E MSG
SC=44 RC=44
Unexpected transition
occurred while adding JNLG
to EXCTG. (CT ID=jj, sub CT
ID=kk, MIRROR=m,
SN=ssssssssssss,
STATE=nnnn)
The copy pair entered an unexpected status while

registering the journal group to EXCTG.
Check that the status to be monitored is correctly
specified. If the status is correctly specified, execute
the YKQUERY command to determine the cause of the
problem and rectify the error.
consistency group ID (00-FF)
kk (hexadecimal number)
The journal group number specified by the sub
m (decimal number)
Mirror ID (0-3)
The storage system serial number
nnnn (string)
The status after the transition
YKZ403I MSG
SC=0 RC=0
No pair processed in Copy

Group(s).
The target copy pair was not found.

Check the volume status, correct errors involved in the
configuration or execution conditions if any, and then
If the YKMAKE SELECT(COND) command is issued on a
copy group container with EXCTG ID specified but
without specifying the DEVN parameter, the EXCTG
registration I/O is issued even if this message is
output.
1-152
Messages
Message ID
YKZ404E MSG
SC=36 RC=36#
Message text
Number of JNLG in the
EXCTG exceeds the limit.

The number of journal groups in the EXCTG exceeded
the maximum number allowed.
YKZ405E MSG
SC=36 RC=36#
Duplicate JNLG number in

Duplicate journal group numbers were found in the
the Copy Group is found. (CT copy group.
ID=jj, sub CT ID=kk)
In order to make the journal group pairs over multiple
storage systems correspond to copy groups which
configure a container, use different numbers in one of
the pairs of consistency group ID and sub consistency
group ID which describe the journal group number.
kk (hexadecimal number)
The journal group number specified by the sub
YKZ406E MSG
SC=36 RC=36#1
Primary device IFType does

not support EXCTG.
EXCTG cannot be used on a storage system that has a

P-VOL or uses the Remote DKC Control Function.
Use a device#2 that supports EXCTG. Also, if a scan
has not been performed after the storage system
IFType
IFType value
#1
#2
EXCTG is used in a storage system where the first
two digits of the IFType are X'13' or higher.
YKZ406E MSG
SC=36 RC=36#1
Secondary device IFType

does not support EXCTG.
EXCTG cannot be used on a storage system that has an

S-VOL or uses the Remote DKC Control Function.
Use a device#2 that supports EXCTG. Also, if a scan
has not been performed after the storage system
IFType
IFType value
#1
#2
EXCTG is used in a storage system where the first
two digits of the IFType are X'13' or higher.
Messages
1-153
Message ID
YKZ407E MSG
SC=24 RC=24
Message text
An error occurred during
suspension of UR ATTIME.
(CT ID=ii, R-JNL=jj,
GENID=gg, ATTSTS=aa,
SISTS=ss, URSTS=uu,
CODE=eeee, TIME=ATTIMEsuspend-time)

An error occurred while the suspend processing using
the UR ATTIME Suspend Function was being
performed.
Check the error information, and remove the cause of
the error. If necessary, also check information such as
the storage system log. After that, use the YKSUSPND
command to cancel the ATTIME suspend time, and
then acquire a backup again.
ii (hexadecimal number)
consistency group ID for ShadowImage (00-7F)
Journal group number specified for the sub
consistency group ID for the Universal Replicator
that links with SI (00-FF)
gg (hexadecimal number)
Generation ID (00-FF)
aa (decimal number)
Status of ATTIME suspension (0-4)
0: No ATTIME suspend time has been set.
1: The ATTIME suspend time has been set, but
suspension has not been performed yet.
2: Suspension was performed because the ATTIME
suspend time expired.
3: Suspension was performed because the timeout
period expired, or because the Universal Replicator
copy pair was in the suspend status at the ATTIME
suspend time.
4: Suspension was performed because the system
detected a no-update journal.
ss (decimal number)
Status of ShadowImage (0-3)
0: The suspend processing has not started.
1: The suspend processing is in progress.
2: The suspend processing ended successfully.
3: The suspend processing ended abnormally.
uu (decimal number)
Status of Universal Replicator (0-1)
0: All Universal Replicator copy pairs were in the
DUPLEX status during the suspension.
1: During the suspension, there was a Universal
Replicator copy pair whose status was not DUPLEX.
eeee (hexadecimal number)
Error information on suspend processing
0001: Suspension is not possible because the
ShadowImage copy pair status is invalid.
1-154
Messages
Message ID
Message text

0002: Suspension is not possible because an error
occurred due to a problem in storage system.
ATTIME-suspend-time (GMT)
ATTIME suspend time: YYYYMMDDHH:MM:SS.NNNNNN
YYYY: Year
MM: Month
DD: Day
HH: Hour
MM: Minute
SS.NNNNNN: Second
YKZ408E MSG
SC=24 RC=24
An unexpected UR pair
status existed during
suspension of UR ATTIME.
(CT ID=ii, R-JNL=jj,
GENID=gg, ATTSTS=aa,
SISTS=ss, URSTS=uu,
CODE=eeee, TIME=ATTIMEsuspend-time)
The status of the Universal Replicator copy pair was

invalid while the suspend processing using the UR
ATTIME Suspend Function was being performed.
Check the status of the Universal Replicator copy pair,
and remove the problem. After that, use the YKSUSPND
command to cancel the ATTIME suspend time, and
then acquire the backup again.
that links with ShadowImage
aa (decimal number)
Status of ATTIME suspension (0-4)
0: No ATTIME suspend time has been set.
1: The ATTIME suspend time has been set, but
suspension has not been performed yet.
2: Suspension was performed because the ATTIME
suspend time expired.
3: Suspension was performed because the timeout
period expired, or because the Universal Replicator
copy pair was in the suspend status at the ATTIME
suspend time.
4: Suspension was performed because the system
detected a no-update journal.
ss (decimal number)
Status of ShadowImage (0-3)
0: The suspend processing has not started.
1: The suspend processing is in progress.
2: The suspend processing ended successfully.
3: The suspend processing ended abnormally.
Messages
1-155
Message ID
Message text

uu (decimal number)
Status of Universal Replicator (0 or 1)
0: All Universal Replicator copy pairs were in the
DUPLEX status during the suspension.
1: During the suspension, there was a Universal
Replicator copy pair whose status was not DUPLEX.
eeee (hexadecimal number)
Error information on the suspend processing
0000: The suspend processing has not been
started or is being executed. Alternatively, the
suspend processing has ended normally. For
details, see the ShadowImage status.
0001: Suspension is not possible because the
ShadowImage copy pair status is invalid.
0002: Suspension is not possible because an error
occurred due to a problem in storage system.
YYYY: Year
MM: Month
DD: Day
HH: Hour
MM: Minute
SS.NNNNNN: Second
YKZ409E MSG
SC=24 RC=24
The timeout limit expired

during the wait for the
reservation time of the UR
ATTIME suspension. (CT
ID=ii, R-JNL=jj, GENID=gg,
TIME=ATTIME-suspendtime)
The suspend processing started when the timeout

period elapsed because this period elapsed before the
journal of the ATTIME suspend times for the ATTIME
suspend function was acquired, or the suspend
processing started at the ATTIME suspend time
because the Universal Replicator copy pair was in the
suspend status at the ATTIME suspend time.
Check the following because the backup for the
specified time might not have been acquired:
Status of the Universal Replicator copy pair path
Value specified for the TIMEOUT parameter of the

YKSUSPND command
Status of the ShadowImage copy pair volumes

(the Universal Replicator consistency time and
status during the suspension)
Status of the Universal Replicator copy pair

volumes
After checking the results, if necessary, use the

YKSUSPND command to cancel the ATTIME suspend
information, and then re-acquire the backup.
1-156
Messages
Message ID
Message text

that links with ShadowImage
YYYY: Year
MM: Month
DD: Day
HH: Hour
MM: Minute
SS.NNNNNN: Second

Message ID
Message text
YKZ410E MSG
SC=36 RC=36#1
Copygroup SUPFnc does not

support UR Errorlevel.
You cannot use the Errorlevel attribute for this storage

system.
In this case, use a device#2 that supports the
Errorlevel attribute for Universal Replicator. Also, if a
scan was not performed after the storage system
Value for the version of the storage system
support function used in the copy group
(minimum)
#1
#2
The Errorlevel for Universal Replicator can be used
in a storage system where the version of the
storage system support function is X'12' or higher.
YKZ411E MSG
SC=36 RC=48
ATOPT(UR) parameter is
only valid for SI Copy
Groups with C/T ID.
The YKSUSPND command with the ATOPT(UR) parameter

specified was executed on a copy group other than a
ShadowImage copy group with the consistency group
ID specified. The ATOPT(UR) parameter is only valid on
ShadowImage copy groups with the consistency group
ID specified.
the ATOPT parameter, or with the ATOPT(NORMAL)
parameter specified.
Messages
1-157
Message ID
YKZ412E MSG
SC=36 RC=48
Message text
This device SUPFnc does not
support UR ATTIME.

The UR ATTIME Suspend Function is not available for
this storage system.
Use a device# for which the UR ATTIME Suspend
Function is supported. Also, if scanning was not
(minimum)
# The UR ATTIME Suspend Function can be used in a
storage system where the version of the storage
system support function are X'14' or higher.
YKZ413E MSG
SC=36 RC=36#1

support the timestamp
transfer mode.
The timestamp transfer mode cannot be used with this

storage system.
Use a device#2 that supports the timestamp transfer
mode. Also, if scanning was not performed after the
storage system microcode was replaced, perform
another scan.
#1
#2
The timestamp transfer mode can be used for the
storage system models listed below. You cannot
use the timestamp transfer mode when using the
Lightning 9900V Series.
YKZ414E MSG
SC=36 RC=48#1

support parameter-name.
USPs with a storage system support function

USP Vs with a storage system support function

The function indicated by parameter-name cannot be

used.
Use a device#2 that supports the parameter-name
function or configuration. Also, if scanning was not
parameter-name
Function or configuration that cannot be used:
- UR_CTTIMEMODE: Consistency time mode for
Universal Replicator
1-158
Messages
Message ID
Message text

- TC_OPENMF: Open/MF Consistency Preservation
Function for TrueCopy
- LinkageOption=HS: 2DC configuration with
HyperSwap and Universal Replicator
- AttimeSplitMode=QUICK: Quick suspend mode
for the UR ATTIME Suspend Function
- UR_PathID: Path group ID specification for
- GroupID=consistency-group-ID-of-TrueCopycopy-group-(hexadecimal-number): Consistency
group ID of the TrueCopy copy group that exceeds
X'7F'
#1
#2
The following are the storage system models for
which you can use parameter-name:
YKZ415E MSG
SC=48 RC=48
The device indicated by devn

in the disk configuration
definition file is on a storage
system that differs from sn.
Consistency time mode for Universal Replicator:

version of X'16' or later, and USP Vs with a storage
system support function version of X'21' or later
Open/MF Consistency Preservation Function for

TrueCopy: USP Vs with a storage system support
function version of X'22' or later, or VSPs and VSP
G1000s with a storage system support function
version of X'31' or later
2DC configurations with HyperSwap and Universal

Replicator: USP Vs with a storage system support
function version of X'22' or later, and VSPs and
VSP G1000s with a storage system support
function version of X'31' or later
Quick suspend mode for the UR ATTIME Suspend

Function: USP Vs with a storage system support
function version of X'23' or later
Path group ID specification for Universal

Replicator: VSPs and VSP G1000s with a storage
system support function version of X'33' or later
Consistency group ID of the TrueCopy group that

exceeds X'7F': VSP G1000s with a storage system
support function version of X'40' or later
The device defined in the disk configuration definition

file exists on a storage system that differs from the
storage system in the disk configuration definition file.
For this reason, an NG Scan cannot be executed.
Check the device address domain ID specified in the
disk configuration definition file or the Set Defaults
panel. For details about the NG Scan, see the Hitachi
devn (hexadecimal number)
Messages
1-159
Message ID
Message text

Device number defined in the disk configuration
definition file
sn
Serial number of the storage system on which the
device indicated by devn actually exists
YKZ416E MSG
SC=36 RC=36#1

support TC Map (DIF UNIT).
This storage system does not allow TrueCopy data

differential-data management units to be specified.
Use a device#2 that allows TrueCopy data differentialdata management units to be specified. Also, if
scanning was not performed after the storage system
(minimum)
#1
#2
TrueCopy data differential-data management units
can be specified on storage systems with the
following versions of the storage system support
function:
YKZ417E MSG
SC=48 RC=48

USP Vs with a storage system support function

This command is invalid for

TrueCopy Copy Groups
linkaged with HyperSwap.
The command cannot be executed for TrueCopy copy

groups with the HyperSwap attribute.
YKZ418E MSG
SC=48 RC=48
OPENMFUPDATE cannot use

with reverse-resync.
A resynchronization that reverses the copy direction

cannot be performed with the OPENMFUPDATE parameter
specified. (The OPENMFUPDATE parameter is used to
modify the Open/MF Consistency attribute.)
YKZ419E MSG
SC=48 RC=48
This command is valid only

for copy group containers
with EXCTG ID specified.
The YKQEXCTG command cannot be executed because

the copy group container does not have an EXCTG ID.
This command is valid only for copy group containers
with an EXCTG ID. Confirm that the command can be
executed on the copy group, and then re-execute the
command.
YKZ420E MSG
SC=48 RC=48
EXCTG information could not EXCTG information could not be acquired because no
be acquired because no
EXCTG ID for copying in the forward direction is
EXCTG ID is specified for
specified. The YKQEXCTG command with the
copying in the forward
TO(SECONDARY) parameter is valid only when copying
direction.
in the forward direction and for copy group containers
with an EXCTG ID for the forward direction. Check the
copy direction of the copy group container and the
EXCTG ID direction (Forward or Reverse), and then reexecute the command.
1-160
Execute the PPRC copy pair operation from TPC-R.
Messages
Message ID
Message text
YKZ421E MSG
SC=48 RC=48
EXCTG information could not EXCTG information could not be acquired because no
be acquired because no
EXCTG ID for copying in the reverse direction is
EXCTG ID is specified for
specified. The YKQEXCTG command with the
copying in the reverse
TO(PRIMARY) parameter is valid only when copying in
direction.
the reverse direction and for copy group containers
with an EXCTG ID for the reverse direction. Check the
copy direction of the copy group container and the
EXCTG ID direction (Forward or Reverse), and then reexecute the command.
YKZ422E MSG
SC=48 RC=48
This operation(operation) is
not available for a Non
Gen'ed volume.
This operation cannot be performed for a Non Gen'ed

volume.
operation
Operation name
YKZ910I CON
command
This log message indicates that a CLI command was

issued.
command
The name of the issued CLI command and its
parameters
A maximum of 118 characters can be output. If
118 is exceeded, the remainder are discarded.
YKZ911I CON
command RC=rc
This log message gives the execution results of a CLI

command.
command
The name of the CLI command
rc
Return code of the CLI command
See the CLI command descriptions in the Hitachi
Multi-line messages output to SYSTSPRT starting from YK

This section describes the multi-line messages that are output to SYSTSPRT.
In this section, character strings enclosed in angle brackets (< >) are
variables.
YK8310I PRT
REPORT SUMMARY:
COPY GROUP : <cgid>
PREFIX : <prefix>
DAD-ID : <dad>
TYPE : <cgtype>
GROUP STATUS
SIMPLEX : <simplexct>
MATCHING%
PENDING : <pendingct>
REVERSED%
DUPLEX : <duplexct>
ATTIME
SUSPEND : <suspendall>
-STATUS
OTHER : <otherct>
:
:
:
:
:
<status>
<match>
<rev%>
<attime>
<attms>
Messages
1-161
The results of REPORT(SUMMARY) are displayed.

<cgid>: Copy group ID
<prefix>: Prefix
<dad>: Copy group host device address domain ID
<cgtype>: Copy group type
<simplexct>: Number of copy pairs in SIMPLEX status
<pendingct>: Number of copy pairs in PENDING status
<duplexct>: Number of copy pairs in DUPLEX status
<suspendall>: Number of copy pairs in SUSPEND status
<otherct>: Number of copy pairs in other statuses
<status>: Copy group status
<match>: Copy progress percentage
<rev%>: Percentage of copy pairs whose copy direction is secondary-toprimary
<attime>: ATTIME suspend time
<attms>: ATTIME suspend status
YK8312I PRT
REPORT DETAIL:
COPY GROUP : <a>
PREFIX : 
DAD-ID : <c>
TYPE : <d>
PRI
SEC
VOLSER DEVN DIR DEVN STATUS
[ <e>
<f> <g> <h> 
MATCH C/T SUB C/T

RATE% ID C/T DELTA
<j>
<k> <l> <m>
C/T
TIME
<n> ]
The results of REPORT(DETAIL) are displayed.

<a>: Copy group ID
: Prefix
<c>: Copy group host device address domain ID
<d>: Copy group type
<e>: Volume serial number
<f>: Primary device number
<g>: Copy direction
1-162
>: Primary-to-secondary
Messages
<: Secondary-to-primary
<h>: Secondary device number

: Copy pair status
<j>: Copy pair matching percentage
<k>: Consistency group ID or master journal group ID
<l>: Restore journal group ID
<m>: Consistency delta value for each consistency group
<n>: Consistency time for each consistency group
YK8314I PRT
REPORT RPO:
COPY GROUP : <a>
C/T SUB PRI- SECID C/T SN
SN
[ <c> <d>
<e>
C/T
DELTA
<f>
C/T
TIME
<g> ]
The results of REPORT(RPO) are displayed.

<a>: Copy group ID
: Consistency group ID or master journal group ID
<c>: Restore journal group ID
<d>: Serial number of the primary storage system
<e>: Serial number of the secondary storage system
<f>: Consistency delta value
<g>: Consistency time
YK8316I PRT
REPORT STATS:
COPY GROUP :
PREFIX :
DAD-ID :
TYPE :
C/T
ID
[ <e>
PRISN
<f>
<a>

<c>
<d>
SECSN
<g>
--- PRI %S ---SFT RSF RSF WPR

TOT C/T TOT
<h> <j> <k>
- SEC %S -RSF RSF WPR

TOT C/T TOT
<l> <m> <n>
--- TIMERS --TRANS

OFLD RCUR CPND
KBYTES/S SEC MIN MIN
<o> <q> <r> ]
The results of REPORT(STATS) for the TrueCopy Asynchronous copy group are
displayed.
<a>: Copy group ID
Messages
1-163
: Prefix
<e>: Consistency group ID
<f>: Serial number of the primary storage system
<g>: Serial number of the secondary storage system
<h>: Sidefile threshold value
: Primary reserve sidefile cache-usage rate
<j>: Primary reserve sidefile consistency cache-usage rate
<k>: Primary write pending rate
<l>: Secondary reserve sidefile cache-usage rate
<m>: Secondary reserve sidefile consistency cache-usage rate
<n>: Secondary write pending rate
<o>: Data transfer rate (Kbps) between the main control unit and the remote
control unit
: Offloading timer
<q>: Remote control unit ready timer
<r>: Copy pending timer
YK8318I PRT
REPORT STATS:
COPY GROUP : <a>
PREFIX : 
DAD-ID : <c>
TYPE : <d>
MJNL RJNL
C/T SUB PRI- SECID
C/T SN
SN
[ <e> <f> <g>
<h>
PRI %S SEC %S - PRI GB - - SEC GB TRANS

JNL-VOL JNL-VOL -- JNL-VOL -- JNL-VOL
KBYTES/S MET DAT MET DAT
DAT
DAT
 <j> <k> <l> <m>
<n>
<o>]
The results of REPORT(STATS) for the Universal Replicator copy group are
displayed.
<a>: Copy group ID
: Prefix
<e>: Master journal group ID
1-164
Messages
<f>: Restore journal group ID

<g>: Serial number of the primary storage system
<h>: Serial number of the secondary storage system
: Data transfer rate (Kbps) between the main control unit and the remote
control unit
<j>: Master journal volume metadata usage rate
<k>: Master journal volume data usage rate
<l>: Restore journal volume metadata usage rate
<m>: Restore journal volume data usage rate
<n>: Master journal volume data capacity (GB)
<o>: Restore journal volume data capacity (GB)
YK8411I PRT
SYSTEM OPTIONS:
CYCLE TIME
WAITFOR TIMEOUT
MSGLEVEL
ONACTIONERROR
STOP AT STOPPOINT
SLEEP AT STOPPOINT
:
:
:
:
:
:
<cycletime>
<timeout>
<lvllog>,<lvlcons>
<err-action>
<stoppt>
<sleeppt>
The values specified in the YKMONOPT file are displayed.

<cycletime>: Cycle time
<timeout>: Timeout value
<lvllog>: Level of messages to be output to SYSTSPRT
<lvlcons>: Level of messages to be output to the console
<err-action>: Error action to be executed
<stoppt>: Stop point
<sleeppt>: Sleep point
YK8413I PRT
COPY GROUP DEFINITIONS:
ID : <cgid>
PREFIX : <prefix>
DAD-ID : <dad>
ROUTE LIST : <route>[,<route-label>]
MONITOR STATUS : <cgmonstat>
STARTUP STATUS : <cgsastat>,<cgsaact>,<cgsaopt>
[
WHEN STATUS <status> DO ACTION '<action><err-action>']
Messages
1-165
The values specified in the YKMONCG file are displayed. This message
appears a number of times, equal to the number of copy groups specified.
<cgid>: Copy group ID
<prefix>: Prefix
<dad>: Copy group host device address domain ID
<route>: Route list ID
<route-label>: Route label
<cgmonstat>: Copy group monitoring status (ACTIVE or INACTIVE)
<cgsastat>: Copy group startup status to be checked for starting BCM
Monitor
<cgsaact>: Startup action executed if the copy pair status for starting BCM
Monitor is different from the specified startup status
<cgsaopt>: Option information of the CGSTARTUPSTATUS parameter
<status> <action><err-action>:
Status, action, and error action for the copy group specified in STATUS
and ACTION
These parameters appear a specified number of times.
Identifying the volume to be processed

The volume to be processed is determined by the copy group number and
copy pair number output in a message as follows.
Identifying the volume serial number from the REXX script

Display the following STEM variable.
stem-name.CopyGroup.copy-group-number.Pair.copy-pair-number.Volser
Identifying the volume serial number from the configuration file

Use the following steps to acquire the volume serial number from the
configuration file:
1.
Count the CopyGroupContainer tags from the beginning of the file and
identify the CopyGroupContainer tag.
2.
From the identified CopyGroupContainer tag, count the CopyPair tags

from the beginning of the file and identify the CopyPair tag.
3.
The SerialNum under the identified CopyPair tag is the volume serial
number to be processed.

The following table provides details about the user completion codes.
1-166
Messages
Table 1-46 User completion codes

Completion codes
U0003
Explanation
There is a problem with the issued CCW.
The version of the registered user SVC might be old. Check whether the latest user
SVC is registered by performing the following operations:
Using a CLI command:

Execute the YKINSCHK command, and check that OK is displayed for User SVC
Routine.
From the ISPF panel:

From the Installation Verification Summary panel, check that OK is displayed for
User SVC Routine.
U0128
The user does not have the permission to execute CLI commands. The user might
not have been given permissions to view the profile required for executing the CLI
command, or an RACF error occurred.
The reason code is displayed in the following format:
XX: Lower byte of SAF RC of the RACROUTE macro
YY: Lower byte of RACF RC of the RACROUTE macro
ZZZZ: Lower 2 bytes of RACF Reason Code of the RACROUTE macro
If the reason code is 00000010 or 00000030:

- A profile to which view permissions have not been granted: the
STGADMIN.YKA.BCM.COMMANDS profile or the STGADMIN.YKA.BCM.YKQUERY profile
- A command that cannot be executed: a CLI command for viewing the
operations or status of copy pairs, paths, or command devices
If the reason code is 00000040, 00000050, or 00000070
- A profile to which view permissions have not been granted: the
STGADMIN.YKA.BCM.COMMANDS profile
- A command that cannot be executed: a CLI command for operating copy
pairs, paths, or command devices
If the reason code is a value other than the above:
The information returned from the RACROUTE REQUEST=AUTH macro is displayed.
For details, see the Security Server RACROUTE Macro Reference.
U1009
An attempt was made to call a module that cannot be executed. There might be a
problem in the LINKLIB library settings. Specify the installation dataset for the
LINKLIB library.
Messages
1-167
1-168
Messages
2
Storage system sense byte information
This chapter describes storage system sense byte information (error codes)
contained in messages.
Details of error codes

2-1

This section lists the details on the storage system sense byte information
(error codes) that are output to messages. If an error code not listed in this
table is output, contact your Hitachi Data Systems representative or
authorized service provider.
The legend is as follows:
CMD: Command device
PATH: Logical path
HDTz: Dynamic Tiering for Mainframe
Y: Produces output
N: Produces no output
Table 2-1 Details of error codes 20xx - 22xx

Type of error
Error
code
2026
Error details
An SI copy pair cannot be
resynchronized (QuickRestore) because
all of the following conditions exist:
System option mode 561 is ON.
The P-VOL and S-VOL are external

volumes.
The P-VOL and S-VOL CacheMode

setting are different.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
2043
The specified SI copy pair cannot be

resynchronized (ReverseCopy or
QuickRestore) because the P-VOL of
the SI copy pair is a UR copy pair
volume for which multiple mirror IDs
are defined.
2044
The specified SI copy pair cannot be

created because the S-VOL of the SI
copy pair is a UR copy pair volume for
which multiple mirror IDs are defined.
2060
An SI copy pair cannot be made or

resynchronized. The reason might be
one of the following:
2061
The SI copy pair status cannot be

changed because the P-VOL has
already been made into a copy pair
by using UR.
The P-VOL is a journal volume.
An SI copy pair cannot be made. The

reason might be one of the following:
2-2
The S-VOL has already been made

into a copy pair by using UR.

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
The S-VOL is a journal volume.
2067

resynchronized because the specified
volume is part of a TC and UR common
volume configuration and neither the
TC nor UR copy pair are in the suspend
status.
2078
An SI copy pair could not be made

because the status of the P-VOL for the
specified SI copy pair does not meet all
of the following conditions:
The S-VOL is part of a delta resync

pair
The delta resync pair is in the HOLD

status
A UR copy pair that is linked with

the delta resync pair is in the
suspend status
2079
The SI copy pair could not be made

because the specified S-VOL of SI copy
pair is a part of a delta resync pair.
2086
The command cannot be executed

because initialization processing for the
SI copy type is being performed.
2089

the P-VOL of the specified SI copy pair
is being quick formatted.
208A

the S-VOL of the specified SI copy pair
is being quick formatted.
2097
The SI copy pair cannot be

the copy pair is made up of an HDPz
volume and a non-HDPz volume.
20A2
A copy pair could not be created

because the HDPz volume specified for
the P-VOL of the SI copy pair is being
expanded.
20A3

the S-VOL of the SI copy pair is being
expanded.
20B4


2-3
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
the P-VOL of the SI copy pair is not

assigned to the pool.
20B5

the S-VOL of the SI copy pair is not
assigned to the pool.
20BD

because the P-VOL of the specified SI
copy pair is an emulation type (3390V) that is not supported.
20BE

because the S-VOL of the specified SI
copy pair is an emulation type (3390V) that is not supported.
20C5
An SI copy-pair operation cannot be

performed because power-off
processing is in progress.
20C9
If the emulation type of the P-VOL of

the specified SI copy pair is 3390-A, a
copy pair could not be created for one
of the following reasons:
20CA
No mainframe Fibre Channel

adapter is installed.
All of the Mainframe Fibre Channel

adapters are blocked.
If the emulation type of the S-VOL of

the specified SI copy pair is 3390-A, a
copy pair could not be created for one

All of the Mainframe Fibre Channel

20D0

because the pool of the HDPz volume
specified for the P-VOL of the SI copy
pair is being initialized.
20D1

because the pool of the HDPz volume
specified for the S-VOL of the SI copy
pair is being initialized.
20D6
A copy pair could not be created for

one of the following reasons:
2-4
The P-VOL of the specified SI copy

pair is being used for FlashCopy
SE.

Type of error
Error
code
Error details
20D7
20E4
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
The P-VOL of the specified SI copy

pair is a TSE-VOL.
A copy pair could not be created for

The S-VOL of the specified SI copy

pair is being used for FlashCopy
SE.
The S-VOL of the specified SI copy

pair is a TSE-VOL.
A copy pair with a C/T group ID could

not be created because the P-VOL of
the specified SI copy pair meets both of
the following conditions:
The P-VOL is the S-VOL of a UR

copy pair.
The P-VOL is being used by

another program product as the PVOL of an SI copy pair with a C/T
group ID.
22F6
An SI copy pair cannot be made

because the specified P-VOL is an SVOL for FlashCopy.
22F7

because the specified S-VOL is either a
P-VOL or S-VOL for FlashCopy.
22F9

resynchronized (by either
ReverseResync or QuickRestore)
because the volume is of a common
volume configuration consisting of a PVOL of SI and a P-VOL of FlashCopy.
Table 2-2 Details of error codes 23xx

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
2301
The command could not be executed

because an SI program product has not
been installed.
2309

because an attempt was made to make
a copy pair that exceeded the
maximum number of SI copy pairs.

2-5
Type of error
Error
code
2310
Error details
An SI copy pair status cannot be
changed because the status of the copy
pair does not allow a status transition.
The reason may be one of the
following:
The combination of the request

command and the status of the
specified copy pair do not allow the
status transition. For information
on combinations, see the
ShadowImage for IBM z/OS User
Guide.
The copy pairs cannot be

suspended collectively because a
copy pair that is not in the DUPLEX
status is among the specified copy
pairs.
The copy pairs cannot be

suspended collectively because a
copy pair for which transition is not
possible is among the specified
copy pairs.
An ATTIME suspend time cannot be

set because a copy pair that is not
in the PENDING or DUPLEX status is
included in the C/T group.
The ATTIME suspend time cannot

be set because the specified C/T
group contains a copy pair that
was created by using RAID
Manager to specify the SI C/T
group ID.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
If the reason why the copy pair status

cannot be changed is not one of the
above, the ATTIME suspend time
cannot be set. Execute the YKSUSPND
command with the CANCEL parameter
specified, and then set the ATTIME
suspend time again.
2311
The copy pair cannot be dissolved

because the copy pair is in the SIMPLEX
status.
2312

because the S-VOL of an SI copy pair is
online.
2313
An SI copy pair cannot be suspended

because the copy pair is in the Split
status.
2-6

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
2314

because the copy pair is in the Split
status.
231B

changed. The reason might be one of
the following:
The status of another copy pair

that shares the P-VOL is SUSPVS.
There is a FlashCopy pair that

shares the P-VOL.
231F

resynchronized because the P-VOL is
online.
232A

because the charging limit of the
program product was exceeded.
2331
An SI copy pair cannot be made. The

The volume size of P-VOL differs

from that of S-VOL.
The shared memory capacity is

insufficient for copy pair creation.
2332

transitioned because the maximum
multiplicity of the copy pairs for the PVOL was exceeded.
2333
An SI copy pair cannot be suspended or

dissolved because the copy pair is in
the SIMPLEX status.
2334

because the emulation type of the
specified volume is not supported.
2335

because the RAID level or emulation
type of the volume is not supported.
2336

changed because the combination of
the drive emulation type of the P-VOL
and S-VOL is not appropriate.
2337

changed because the volume specified
to be the P-VOL is already the S-VOL.
233A

resynchronized because the copy pair is
in the SIMPLEX status.

2-7
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
233F

resynchronized with Reverse specified
because a TC or TCA copy pair is not in
the suspend status.
2343

to be the S-VOL is already the S-VOL of
an SI copy pair.
2344

changed because the status of the copy
pair does not allow the status
transition. The reason might be one of
the following:
The volume specified to be the SVOL is already the P-VOL of an SI

copy pair.
The volume specified to be the SVOL is in the SIMPLEX status.
2346

to be the S-VOL is already the P-VOL of
a TC or TCA copy pair.
2347

to be the S-VOL is already the S-VOL of
a TC or TCA copy pair.
234A

to be the S-VOL is already the P-VOL of
an SI copy pair or the one for
FlashCopy.
2351

changed because the same volume was
specified for the P-VOL and the S-VOL.
2352

resynchronized with Reverse or Quick
specified because the P-VOL and S-VOL
are online.
2353
An SI copy pair cannot be dissolved

because the copy pair is in the V-Split
status.
2354

in the Pending status.
2358

the following:
2-8

Type of error
Error
code
Error details
The status of another copy pair

that shares the P-VOL or S-VOL is
TRANS.
There is a FlashCopy pair that

shares the P-VOL or S-VOL.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
235B

specified because the P-VOL is the PVOL of a TC or TCA copy pair that is
not in the suspend status.
235C

specified because the P-VOL is the SVOL of a TC or TCA copy pair that is
235D

specified because the S-VOL is the PVOL of a TC or TCA copy pair that is
2370

changed because the specified volume
does not exist.
2371

because the volume specified to be the
P-VOL is a system residence volume.
2373

to be the P-VOL is a command device.
237B

all of the following conditions exist:
The specified P-VOL is an internal

volume.
The specified S-VOL is an external

volume.
The specified P-VOL has a shared

configuration with the P-VOL of the
TC.
2381

S-VOL is a system residence volume.
2383

to be the S-VOL is a command device.

2-9
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
2390

P-VOL is being quick formatted.
2391

S-VOL is being quick formatted.
2394

because the number of copy pairs in
the specified C/T group exceeded the
maximum number of copy pairs in a
C/T group.
2395

to be the SI P-VOL is in the Reverse
Resync status with another copy pair
which shares the P-VOL.
2398

resynchronized (including Reverse)
because the copy pair is not in the Split
status.
2399

changed because another copy pair
that shares the P-VOL or S-VOL is a
FlashCopy pair or not in the suspend
status.
239A

because the specified P-VOL is the PVOL of a TC copy pair.
239B

because the specified P-VOL is the SVOL of a TC copy pair.
239C

because the specified S-VOL is the PVOL of a TC copy pair.
239D

because the specified P-VOL is
protected by the LDEV guard.
239E

because the specified S-VOL is
23A0
The command could not be executed.

The reason might be one of the
following:
2-10

Type of error
Error
code
Error details
The specified volume is

inconsistent with the volume that
received the command.
A copy pair exists that shares the

specified C/T group ID and TC SVOL, and the ATTIME suspend
function cannot be executed.
The ATTIME suspend function

cannot be executed because the PVOL is a Non Gen'ed volume.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
23BB

because the LDEV security is set for the
specified S-VOL.
23EF
An SI copy pair cannot be deleted

because the specified SI copy pair is in
SUSPVS status.
23F1

because the specified C/T group ID is
out of the valid range.
23F2
The command cannot be executed. The

The specified C/T group ID is not

registered.
The copy pair is in the SIMPLEX

status.
The specified C/T group contains a

copy pair that was created by
using RAID Manager to specify the
SI C/T group ID.
23F3

because the specified ATTIME suspend
time is in the past.
23F4
The command used to request that the

ATTIME suspend time information be
acquired could not be executed due to
the following reasons:
The command was issued to the PVOL.
The status of the copy pair is

SIMPLEX.
Make sure that the command is

properly issued and the copy group
definition file has been correctly
configured.
23F5

because the ATTIME suspend time is
already set. If you want to change the

2-11
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
configuration of the copy group

definition file, first cancel ATTIME
suspension.
23FF

changed because the specified SI copy
pair status does not allow the status to
be changed.

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
3613
Registration to EXCTG has failed

because the specified arbitration
command device is not an arbitration
command device.
3614
Registration to EXCTG has failed. The

The specified arbitration command

device is not defined.
The specified arbitration command

device is blocked.
3616

because the journal group to be
registered is also subject to deletion
from EXCTG.
3617

because the status is currently being
changed.
3618

because M-JNL groups and R-JNL
groups co-exist within the EXCTG.
3621

because the number of journal groups
exceeded the maximum number that
can be assigned to the specified
arbitration command device. Retry the
operation using another arbitration
command device.
3640
Registration to EXCTG has failed due to

a temporary path failure. Please retry
the operation.
2-12

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
3641
The EXCTG cannot be registered

because the specified EXCTG ID,
journal group number, and mirror ID
are invalid.
3642

because the journal group attribute is
incorrect.
3680

registered was not found.
3681

because the mirror ID of the journal
group to be registered is different from
the specified mirror ID.
3682

because the attribute of the journal
the attribute of the EXCTG.
3685

because the specified storage system
model name is invalid.
3686

registered is already registered to
another EXCTG.
3688
Registration to EXCTG has failed for

The mirror status of the specified

journal group is not Active or
Stop.
The Disaster Recovery Extended

program product is not installed.
The specified journal group is

already registered in a UR
Open/MF consistency group.
The specified journal group is set

to be used in 3DC (URxUR)
configurations.
3689

because the attribute of the journal
the attribute of the EXCTG.
368A

because the timer type of the journal
group to be registered is not System.

2-13
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
3694

because the combination of the serial
number and device on the specified
arbitration command device is
incorrect.
3695

registered is an open-system journal
group.

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
3703
A UR copy pair cannot be

resynchronized (with the PREPARE
parameter) because the journal volume
has PIN data.
3704
The UR copy pair cannot be made

because the emulation type for the
specified M-JNL group does not match
that of the R-JNL group.
3705
The command for delta resync cannot

be executed because the device on the
S-VOL does not support delta resync.
3706
A delta resync pair cannot be made

because the command target volume is
the S-VOL of a TC copy pair and the
copy pair status is not Duplex.
3707
A delta resync pair cannot be executed.

following:
The command target volume is the

P-VOL of a TC copy pair and the
copy pair status is not Duplex.
The command target volume is the

S-VOL of a TC copy pair and the
copy pair status is not SSWS.
3709
The delta resync command cannot be

executed because there are no UR copy
pairs with a mirror ID other than the
one specified for the delta resync pair
in the specified R-JNL group.
370B

resynchronized (with the DELTAJNL
2-14

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
parameter) because the specified PVOL is not in the HOLD status or

HOLDTRNS status. Alternatively, a UR
copy pair cannot be resynchronized
(with the ALLJNL parameter) because
the specified P-VOL is not in the HOLD
status, HOLDTRNS status, or NODELTA
status.
370C
A UR copy pair cannot be made or

The specified M-JNL group or R-JNL

group does not allow the status to
be changed.
The specified M-JNL group or R-JNL

group is in progress of the status
to be changed.
370D

cannot be accessed.
3711

is blocked.
3720

resynchronized because the journal
volume in M-JNL is blocked.
3726
A UR copy pair cannot be made

3728

because an unsupported volume was
specified when making a copy pair
between different models.
3729
A UR copy pair that is to be linked with

TC cannot be made because the
Disaster Recovery Extended program
product has not been installed in the
MCU.
3734
The UR copy pair cannot be recreated

because the P-VOL of the UR copy pair
meets both of the following conditions:
The P-VOL of the UR copy pair is

the S-VOL for FlashCopy.

2-15
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
The P-VOL of the UR copy pair is

the P-VOL of a TC copy group with
a C/T group ID specified, and the
TC copy pair is in the suspend
status.
3735
The UR copy pair cannot be recreated

is the S-VOL for FlashCopy and a
failure might have occurred in
FlashCopy.
3737
The specified UR copy pair cannot be

created in a 3DC (URxUR) configuration
because a UR copy pair with a different
mirror ID than the specified UR copy
pair is in a transitional state
(Suspending or Deleting).
3738

because the Disaster Recovery
Extended program product has not
been installed in the MCU.
3739
The UR copy pair cannot be created for

the following reasons:
373D
The UR copy pair is defined with a

different mirror ID.
The journal group that the

specified S-VOL belongs to is not
set to be used in a 3DC (URxUR)
configuration.

because the S-VOL of the UR copy pair
is used in the following program
products:
TC
FCV2/FCSE
Volume Migration
HDPz pool volume
373E
A UR copy pair cannot be created

between the primary site and the
intermediate site in a 3DC Cascade
(URxUR) configuration because the
mirror status of the UR copy group
between the intermediate site and the
remote site is not Initial or Stop.
3744

2-16

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r

is in use by another program product.
3745

between the primary site and the
intermediate site in a 3DC Cascade
(URxUR) configuration because the
specified M-JNL is not set to be used in
a 3DC (URxUR) configuration.
3753
A UR copy pair cannot be created with

the HOLD parameter in a 3DC (URxUR)
configuration because the delta resync
function is not supported.
3755

resynchronized. Possible reasons
include both of the following:
3756
The specified S-VOL is already in

use as an S-VOL in a UR copy pair
that has another mirror ID.
Another UR copy pair using the

specified S-VOL is not in the
SWAPPING status.
A UR copy pair cannot be made with a

value other than 0 specified for the
path group ID because the secondary
storage system does not support values
other than 0 for path group IDs.

Type of error
Error
code
4600
Error details
A UR copy pair cannot be made.
Possible reasons include one or both of
the following:
The serial number of the primary

storage system in the parameter
does not match the serial number
of the local storage system.
The SSID for the P-VOL in the

parameter does not match the
SSID of the local storage system.
The CU number specified in the

parameter is not supported.
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
N
2-17
Type of error
Error
code
4601
4602
4603
Error details
A UR copy pair cannot be suspended.
the following:

The SSID for the S-VOL in the


include one or both of the following:


A UR copy pair cannot be dissolved.

the following:


SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4606
The UR copy pair status could not be

acquired because the specified CU
number is unsupported.
4607
A batch pair status of a UR copy pair

could not be acquired because the
specified CU number is unsupported.
4608
Performance information about a UR

journal group could not be acquired
because the specified CU number is
unsupported.
460B
Registration to or deletion from the

EXCTG has failed because the specified
arbitration command device number (a
non-existent value), EXCTG ID, mirror
ID, journal group number, or serial
number is incorrect.
460C
The copy pair cannot be resynchronized

because the C/T group attribute
defined in the copy group definition
2-18

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
does not match the C/T group attribute

set for the specified device.
4612

because the specified P-VOL has
already been made as a UR copy pair.
4613

because the specified M-JNL group is
not registered.
4614

because no logical path has been made
between the specified primary storage
system and secondary storage system.
4615
A UR copy pair status cannot be

changed because the I/O execution
volume and the P-VOL for the
parameter do not match.
4616
A UR copy pair cannot be suspended,

resynchronized or dissolved because
both the specified serial number of the
primary storage system and serial
number of the secondary storage
system do not match the serial number
of the local storage system.
4617
A UR copy pair cannot be suspended,

resynchronized or dissolved because
the specified volume is not a UR copy
pair.
4618
A UR copy pair cannot be suspended

because it was a suspend request with
Volume and Purge specifications.
4619
A TC, TCA, or UR copy pair cannot be

suspended with Reverse specified
because the command is issued to the
P-VOL.
461A
A TC, TCA, or UR copy pair cannot be

because the command is issued to the
P-VOL.
461E
The command device cannot be

defined. The reason might be one of
the following:
The command device is executing

a remote control command.
The volume is part of a TC or TCA

copy pair.

2-19
Type of error
Error
code
461F
Error details
deleted. The reason might be one of
the following:
The command device is executing

a remote control command.
The volume is part of a TC or TCA

copy pair.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4621

because the Remote DKC Control
Function is not supported.
4630

because the 3-site function is not
supported.
4633

changed because an attribute of the PVOL or S-VOL differs from the actual
volume attribute. The command might
have failed because the YKQUERY
command was not executed in
advance.
4639
The command device could not be

defined because the specified volume is
a UR copy pair volume or journal
volume.
463C
Due to either of the following reasons,

UR ATTIME suspensions cannot be
scheduled in Quick mode:
The storage system does not

support the UR ATTIME suspend
function in Quick mode.
The microcode of the storage

system is currently being changed
to one that supports the UR
ATTIME suspend function in Quick
mode.
4645
A TC or TCA copy pair status cannot be

changed because a logical path has not
been established between the P-VOL
and S-VOL.
4649
TCA copy pair operations cannot be

performed because the specified
storage system does not support TCA.
4650
A delta resync cannot be executed

because volumes are specified within
the range of the operation.
2-20

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4651
A delta resync cannot be executed in

the reversed copy direction.
4660
The UR ATTIME suspend time cannot

be set. The reason might be one of the
following:
The specified parameter is invalid.

support the UR ATTIME suspend
function in Quick mode.
4661

be set because shared memory is not
implemented.
4662

be set because the specified volume is
not the S-VOL of a UR copy pair.
4663

be set due to either of the following
causes:
The UR copy pair is in the Simplex

status.
The copy pair is a delta resync UR

copy pair.
4665

be set because the timer type of the
specified R-JNL group is not System.
4668

be set because three generations of
suspend time have already been set for
the specified R-JNL group.
4669

be set because another suspend time
has already been set for the C/T group
of the specified SI copy pair.
466A

be set. The reason might be one of the
following:
The specified time is earlier than

the consistency time.
The timer type remains Local

because the UR copy pair has not
been resynchronized after the
timer type was changed from
Local to System.
When changing the timer type from

Local to System, you need to suspend
the UR copy pair. If the UR ATTIME

2-21
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
suspend time has already been set,

perform the following procedure to set
the UR ATTIME suspend time again.
1.
Suspend the UR copy pair.
2.
Change the timer type.
3.
Resynchronize the UR copy pair.
4.
Set the UR ATTIME suspend time

again.
466B

be set because the C/T group ID of the
specified SI copy pair is incorrect.
4672

be set because power-off processing is
in progress.
4678

be set for the following reasons:
The specified volume is not part of

an SI copy pair.
The specified C/T group does not

contain an SI copy pair that
contains the specified volume.
The specified C/T group is not used

by an SI copy pair created with BC
Manager.
467A
The NORMAL ATTIME suspend time

cannot be set because the UR ATTIME
suspend time has already been set for
the specified SI C/T group.
467B

be set because the NORMAL ATTIME
suspend time has already been set for
the specified SI C/T group.
467C

be set because a copy pair that is not
in the Duplex status is included in the
specified SI C/T group.
4681
An SI copy pair cannot be made,

resynchronized, or suspended because
the UR ATTIME suspend time has been
set for the specified SI C/T group.
4684

be set because the specified volume is
currently being used in a UR Open/MF
consistency group.
2-22

Table 2-6 Details of error codes 47xx - 49xx

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
47A3
A TC or TCA copy pair cannot be

suspended because SVOL(PERMIT) or
Reverse Resync is not supported.
47A4
A TCA copy pair cannot be

because either the C/T group ID or the
C/T group timer type is incorrect.
47A6

because the S-VOL is not suspended in
the Reverse Resync status.
47A7

because the specified volume is the PVOL.
47BA
A TC or TCA copy pair cannot be made

because the specified volume is the SVOL of an SI copy pair or subject to an
intervention request.
4993
A TC or TCA copy pair could not be

suspended with Flush specified because
the specified volume is the S-VOL.
4995
The Flush settings cannot be

suspended because the command
target is not a TCA copy pair.
49F8
A copy pair cannot be made in this

copy group because the ATTIME
suspend time for TCA is set.
49F9
A copy pair cannot be resynchronized

in this copy group because the ATTIME
49FA
A copy pair cannot be suspended in this

copy group because the ATTIME
Table 2-7 Details of error codes 4Axx

Error
code
4A08
Type of error
Error details
The C/T group ID specified for the TCA
C/T group option change is incorrect.
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
N
2-23
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4A0B
The C/T group ID specified for the TCA

C/T group option change is not
registered.
4A0C
The C/T group timer type (SYSTEM/

LOCAL/NONE) for the TCA cannot be
changed because there is a copy pair in
this C/T group.
4A30
The C/T group ID defined in the TCA

copy group, and the C/T group ID set
by the copy pair do not match.
4A31
Copy pair resynchronization failed for

TC copy pair resynchronization was

performed on a TCA copy group.
TCA copy pair resynchronization

was performed on a TC copy
group.
4A33
The C/T group ID defined in the TCA

copy group is not registered.
4A34
A TCA copy pair cannot be made

because the P-VOL is already made as
a copy pair.
4A36

resynchronized because the
corresponding C/T group ID is not
registered in the RCU.
4A37

resynchronized because the specified PVOL has not been made as a copy pair.
4A45
A TCA copy pair cannot be made or

resynchronized because there is a copy
pair that is being dissolved or
suspended in the corresponding C/T
group.
4A50

resynchronized because the P-VOL has
not been made for the corresponding
C/T group ID.
4A5C
The TCA copy pair cannot be made

because the TCA program product is
not installed.
4A82
The C/T group cannot be registered

not installed.
2-24

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4A8B

because the status of the TC or TCA
copy pair is invalid.
4A8C

copy pair is being changed.
4A8D

copy pair is invalid.
4A8E

copy pair is being changed.
4A96

because the CLPR that the specified PVOL belongs to differs from the one
registered in the C/T group. For details
on the CLPR, see the storage system
documentation.
4AB7
A TCA copy pair cannot be made or

resynchronized because there is a copy
pair that is being dissolved or
suspended in the corresponding group.
4ABD
The option that was changed by the

TCA C/T group definition cannot be
updated because there is a copy pair
that is not in the SIMPLEX or suspend
status in the corresponding group.
4AC7
The C/T group ID specified at the TCA

primary site cannot be registered
because it is in use at the secondary
site.
4AE2
The TC type of the C/T group already

registered for TCA (MF/OPEN) and
specified by the command do not
match.
4AFB

because the CLPR that the specified SVOL belongs to differs from the one
documentation.

2-25
Table 2-8 Details of error codes 4Bxx

Type of error
Error
code
4B02
Error details
because the copy pair is in a status
that cannot be changed. The reason
might be one of the following:
The copy pair cannot be

resynchronized because the copy
group definition contains a C/T
group ID, but the actual copy
group does not.
A resynchronization cannot be
performed if it changes a copy
group that has a C/T group ID but
does not have an Open/MF
Consistency attribute to a copy
group without a C/T group ID.
A resynchronization cannot be
performed if it changes a copy
group without a C/T group ID to a
copy group that has a C/T group
ID but does not have an Open/MF
Consistency attribute.

status.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4B03
A copy pair that is in a TC copy group

with a C/T group ID specified cannot be
resynchronized because the C/T group
IDs do not match.
4B04

because the P-VOL is a command
device.
4B06

suspended because the copy pair
status does not allow the status to be
the following:
4B07
2-26
The specified volume is not in a TC

copy group with a C/T group ID
specified.
The Open/MF Consistency attribute

for the specified volume is different
from the copy group definition
information.

status.


Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
suspended because the C/T group IDs

do not match.
4B09

dissolved because the copy pair status
does not allow the status to be
the following:

specified.

status.
4B0A

dissolved because the C/T group IDs do
not match.
4B0B
RUN (releasing FREEZE) cannot be

executed for a TC copy group with a
C/T group ID specified because the
specified copy pair is not in the FREEZE
or SCP status.
This error is reported when the time

specified in the TIMEOUT parameter
when the YKFREEZE command is
executed has passed, and when the
YKRUN command is executed. Check the
following:
After executing the YKFREEZE

command, did you execute any
command, such as the YKQUERY or
YKEWAIT command, that takes a
long time to execute before
executing the YKRUN command?
Does the copy group contain a

system volume that is used by the
operating system or BC Manager
applications for control purposes?
And is the BC Manager itself is in
the FREEZE status?
4B0F
FREEZE cannot be executed for a copy

pair that is in a TC copy group with a
value specified for TIMEOUT is outside
the valid range.
4B10
FREEZE cannot be executed for a TC

specified because the specified volume
is not the P-VOL.

2-27
Type of error
Error
code
4B11
Error details
FREEZE cannot be executed for a copy
pair that is in a TC copy group with a
C/T group ID specified. The reason

specified.
The specified volume is using the

Open/MF Consistency Preservation
Function.

status.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4B14

specified volume is not the P-VOL.
4B15

C/T group ID specified. The reason
4B32

specified.
The specified volume is using the

Open/MF Consistency Preservation
Function.

status.
A copy pair cannot be created or

resynchronized because the specified PVOL satisfies one of the following
conditions:
The P-VOL is being used for

FlashCopy.

FlashCopy SE.
The P-VOL is a TSE-VOL.
4B35
A path cannot be set because the CU

number for the specified MCU is not
supported.
4B36
A path cannot be set because the port

number for the specified MCU is not
supported.
4B37
A path cannot be set because the port

number for the specified RCU is not
supported.
2-28

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
4B38
A path cannot be set because the CU

number for the specified RCU is not
supported.
4B49
The remote command cannot be

executed because the path between the
specified storage system or CU (SSID)
and the command target storage
system is not set, or an error has
occurred on the path.
4B85
The TC copy pair that specified a C/T

group ID cannot be created because
the specified volume is a FlashCopy
pair.
4B86
A TC copy pair cannot be made

because the specified volume is a
FlashCopy pair and differential-data
management unit is cylinder.
4BA9
A TCA copy pair cannot be made

because the specified CTID is not
registered in the storage system.
4BB1
No timestamp transfer mode TC copy

pair can be made because the specified
volume is not a TC copy pair.
4BB2
A timestamp transfer mode TC copy

pair cannot be made because the
specified volume is an XRC pair.
4BD1
A TC copy pair resynchronization that

makes it possible to use the Open/MF
Consistency Preservation Function
cannot be performed because the
specified C/T group ID is invalid.
4BD2
A TC copy pair cannot be made and

volume does not support the Open/MF
Consistency Preservation Function.
4BDE
The specified operation cannot be

performed because either the local
storage system or the remote storage
system does not support inter-CU
logical paths.
4BE0

because the necessary shared memory
is not implemented in the MCU.

2-29
Table 2-9 Details of error codes 50xx - 6Exx

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
501C
The command device cannot be defined

journal volume. Alternatively, a UR
copy pair cannot be made.
64E2
A command device cannot be deleted

because the APID differs from the
defined APID.
64E3
The Remote DKC Control Function

cannot be executed because the
command device is not set.
64E8
A command device cannot be defined

because the specified CU number is not
supported.
64EA
The paths between CUs, which contain

command devices, are not set.
64EE
The FREEZE command cannot be

executed for TC copy groups with C/T
group IDs because a host that does not
support the FREEZE command is
connected.
64FA

because the host ID is invalid (not
within the valid range).
64FB

defined. Possible reasons include one
or more of the following:
64FC
2-30
The corresponding volume does

not exist.
The corresponding volume is

online.
The corresponding volume is a

system residence volume.
The emulation type of the

corresponding volume is 3390-V.
The corresponding volume is being

used by another program product
such as SI, TC, TCA, UR or
FlashCopy.
The emulation type of the

corresponding volume is 6588-A.
A command device cannot be redefined because the APID that was

already defined does not match the
APID you attempted to define.

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
64FD
The command device cannot be defined

because a command device with the
same APID has been defined for
another device.
64FF

because the APID specified by the
parameter does not match the APID
defined for the command device.
69E4
A parameter error occurred. This error

might occur during a storage system
configuration change or operation after
the microcode is changed. If this error
occurs, scan the storage system by
using BC Manager to obtain volume
information again.
69E6
A path cannot be deleted because there

is an invalid parameter.
69E7


because the specified volume does
not exist.
The Protection attribute has been

set by Hitachi Volume Retention
Manager software.
69E8

because the specified volume is
blocked.
69E9

69F2
69F3
The corresponding volume is in the

Simplex status.
The corresponding volume is not

part of a TCA copy pair.
The corresponding volume is not a

P-VOL.
A path cannot be established because

there is an invalid parameter.

is incorrect.
The SSID is incorrect.
The CU number is not supported.
A copy pair cannot be created or


2-31
Type of error
Error
code
Error details

of the P-VOL is incorrect.
The SSID of the P-VOL is incorrect.

support the Open/MF Consistency
Preservation Function.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
69F5
A status cannot be changed because

the specified volume is the S-VOL.
69F7
A suspension cannot be made. The


support the Open/MF Consistency
Preservation Function.
69F8
A suspension cannot be made because

69F9
A copy pair cannot be dissolved

because there is an invalid parameter.
69FB

because the volume that received the
command is an SI S-VOL.
69FC

resynchronized, suspended, or
dissolved because a volume other than
TCA has been specified.
69FE
A TCA copy pair cannot be dissolved

with Consistent specified because the
specified volume is not the S-VOL.
69FF
A copy pair cannot be made because

the program product necessary for the
operation is not installed.
6A00
A C/T group ID cannot be registered

because there is an invalid parameter.
6A07

because the corresponding volume is
not the P-VOL of a TCA copy pair or it
is a Non Gen'ed volume.
6A08
An ATTIME suspend time for TCA

cannot be set because there is a copy
pair that is not in the DUPLEX status.
6A09
An ATTIME suspend time for TCA

cannot be set because the specified C/T
group timer type is not System.
2-32

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
6A0F

not installed.
6A13

because a remote command was
executed while the command device
was not defined.
6A14

because it was specified to be remotely
executed, but this command cannot be
executed as a remote command.
6A16

because an instruction to delete a
command device was issued against a
volume that is not a command device.
6A18

because an unimplemented CU number
was specified when the command
device was defined or deleted.
6A19

because a remote control command
has been received for a volume that is
not a command device.
6A1E

because the APID specified by the
remote command does not match the
APID that was already registered.
6EC0
The setting or status acquisition

command for HDTz could not be
executed because the specified
parameter is invalid.
6EC1

command could not be executed
because the command for HDTz
contains invalid information, or a value
out of range.
6EC3

executed because of either of the
following reasons:
6EC4
The volume or pool ID that was

specified does not exist.
The attribute of the pool that

belongs to the target device is not
HDTz.


2-33
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
executed because of either of the

following reasons:
The specified SSID and the SSID of

the target storage system do not
match.
The specified serial number and

the serial number of the target
storage system do not match.
The specified CU number and the

CU number of the target device do
not match.
The specified volume number and

the volume number of the target
device do not match.
The target device does not exist.

command could not be executed
because an invalid SSID was specified
for the command for HDTz.
6EC8
Configuration of the HDTz volume failed

because an internal processing error
occurred in the storage system.
6ECA
Configuration of the HDTz pool failed

6ECC
The tiering setting information and

relocation status of the HDTz volume
could not be acquired because an
internal processing error occurred in
the storage system.
6ECE
The performance information of the

HDTz volume could not be acquired
Table 2-10 Details of error codes 7Fxx - 8Cxx

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
7F86

because no program product for
copying is installed.
7FD4
This command is not supported.
2-34

Type of error
Error
code
8C12
Error details
changed. Possible reasons include one
The specified S-VOL is online.
The specified volume is either a TC

or TCA pair volume, or the S-VOL
of an SI copy pair.
All paths to the RCU are blocked.
The status of the copy pair is not

possible for the requested
transition (it is possible that it is
already in requested copy pair
status).
The logical volume of the specified

volume is blocked.
The path between the primary site

and the secondary site is in the
BUSY status.
The emulation type of the P-VOL

and the S-VOL do not match.
Alternatively, the number of
cylinders in the S-VOL is less than
the P-VOL.
Either the status of the P-VOL is

being changed, or there is a copy
pair in the group with the status
being changed.
The command could not be

executed because the specified TC
or TCA volume is in the SIMPLEX
status.
The S-VOL is not in the SWAPPING

status.
Either the status of the P-VOL is

being changed, or there is a copy
pair in the group with the status
being changed.
A copy pair cannot be made

because the same C/T group ID is
set in both the MCU and RCU.

registered.
Alternatively, a path cannot be

defined and deleted because either
the copy pair status or the
parameter is invalid. (The possible
reasons are documented by error
codes C120 through C12F.)
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
N
2-35
Type of error
Error
code
8C1E
Error details
A UR copy pair cannot be made.
the following:
The micro version on the specified

primary storage system does not
support a connection with the
specified secondary storage
system.
The specified primary storage

system does not support a
connection with the specified
secondary storage system.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8CE8

because in the instruction to transfer to
a remote storage system, there is an
error in the parameter specification for
the host command.
8CE9

because the path for the Remote DKC
Control Function is not set.
8CEB

because the path for the Remote DKC
Control Function is not set.
8CFB

because in the instruction to transfer to
a remote storage system, there is an
error in the storage system serial
number.
8CFC

because the command device is not
defined.
Table 2-11 Details of error codes 8Dxx

Type of error
Error
code
8D00
2-36
Error details

is incorrect.
The SSID is incorrect.
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
N
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D01

Alternatively, path establishment is not
supported.
8D09
A path cannot be deleted because there

is an invalid parameter. Alternatively,
path deletion is not supported.
8D10
A copy pair cannot be made. The

An inter-CU logical path has not

been set between the specified
CUs.

of the P-VOL is incorrect.
The SSID of the P-VOL is incorrect.
8D11

because the volume specified by the
host command parameter is in the NOT
READY status.
8D12

because the logical volume of the
specified volume by the host command
parameter is blocked.
8D14

because the SI, TC, or TCA program
product is not installed.
8D15

include one or more of the following:
8D16
The status of the copy pair does

not allow the status transition. For
details, see error code 2310.
The charging limit of the program

product was exceeded.
The copy pair is in the Pending

status.
The copy pair is not in the Split

status.

registered.


2-37
Type of error
Error
code
Error details



status.

status.

registered.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D17

because the SI, TC, or TCA program
8D1A

host command parameter is the S-VOL.
8D1B
A status cannot be changed because

the status of the specified copy pair
does not match the actual status.
8D1C

or resynchronized. Possible reasons
8D1D
2-38
The P-VOL is a command device.
The specified serial number of the

primary storage system or SSID
does not match the storage system
serial number or SSID of the local
CU.
The specified P-VOL does not

match the bootup volume.
The C/T group ID is incorrect.
The P-VOL has not been made in

the corresponding C/T group.
The S-VOL is not in the Reverse

Resync status.
Either C/T group ID or the C/T

group timer type is incorrect.

The S-VOL is online.

The P-VOL is online.

Type of error
Error
code
Error details


status.

status.

registered.
The number of copy pairs in the

specified C/T group ID exceeds the
maximum number.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D1E
The serial numbers for the primary and

the secondary storage systems in the
host command parameter is incorrect.
8D20
The host command parameter is

incorrect.
8D21

host command parameter is in the NOT
READY status.
8D22

volume specified by the host command
parameter is blocked.
8D25

because the TC, TCA, or SI program
8D26
An SI copy pair cannot be suspended.

Possible reasons include one or more of
the following:
8D27


status.
The copy pair is in the Split status.

registered.

the following:


status.

2-39
Type of error
Error
code
Error details

registered.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D28

because the copy types of the specified
copy pair do not match.
8D29

suspended. Possible reasons include
one or more of the following:
8D2A
2-40
The specified volume is in the

SIMPLEX status.
The P-VOL number in the

parameter and bootup volume
number do not match.
The S-VOL number in the

parameter is incorrect.
The serial number of the primary

storage system or SSID in the
storage system serial number or
SSID of the local CU.
The serial number or SSID of the

secondary storage system in the
SSID of the RCU.


secondary storage system in the
SVOL(PERMIT)/Reverse Resync is
not supported.
The specified volume is the P-VOL.
It is already in the suspend status.
The S-VOL is in the Pending status.
The status is invalid.
The status of the copy pair is being

changed.

the following:

Type of error
Error
code
Error details


status.

registered.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D2C
The serial numbers for the primary and

the secondary storage systems in the
host command parameter is incorrect.
8D30

incorrect.
8D31
Multiple SI copy pairs cannot be

suspended because there is a copy pair
that does not allow the status transition
in the specified copy pairs.
8D38

because the specified volume is not in
the SIMPLEX status.
8D39

because it differs from the APID that
was already registered.
8D3A

because the specified APID is in use by
another DEV.
8D3D
A command device cannot be deleted

because the specified volume is not a
command device.
8D3E
A command device cannot be made

because the specified CU number is not
supported.
8D41

because the volume specified as the
command device is already part of a
copy pair, or is a journal volume.
8D42

because the volume specified as a
command device is a volume used in
the open system.
8D43

specified volume is blocked.

2-41
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D44

because the specified volume has PIN
data.
8D45

defined. The reason might be one of
the following:
8D46

executing a remote control
command as a command device.
The corresponding volume is part

of a TC or TCA copy pair.

deleted. The reason might be one of
the following:

executing a remote control
command as a command device.
The corresponding volume is part

of a TC or TCA copy pair.
8D47

because the specified volume is an SI
volume.
8D4D

because the specified volume does not
exist.
8D4E

because it differs from the APID that
was already registered.
8D4F

because the specified volume is online.
8D50

incorrect.
8D51

specified volume is blocked or the
specified volume is in the NOT READY
status.
8D52

8D56
An SI copy pair cannot be dissolved.

the following:
2-42


Type of error
Error
code
8D57
Error details
The copy pair is in the V-Split

status.

registered.

the following:


status.

registered.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D58

because the copy types of the specified
copy pair do not match.
8D59
A TCA copy pair cannot be dissolved

with Consistent specified because the
specified volume is not the S-VOL.
8D5A

dissolved. Possible reasons include one
It is already in the SIMPLEX status.
The P-VOL in the parameter and

the bootup volume number do not
match.


primary storage system in the
The serial number of the secondary

storage system or SSID in the
SSID of RCU.

The status of the copy pair is

invalid.
The status of the copy pair is being

changed.

2-43
Type of error
Error
code
8D5B
Error details
the following:


status.

registered.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8D70

incorrect.
8D71
A TCA C/T group cannot be registered

or changed. Possible reasons include
one or more of the following:
The specified C/T group ID is

incorrect.
You cannot specify System as the

timer type.
The timer type is incorrect (not

System, Local or None).
The C/T group ID is already

registered.
The C/T group ID is not registered.
The timer type (System, Local, or

None) cannot be changed because
there is a copy pair in the specified
C/T group.
There is a copy pair in the

corresponding C/T group that has a
status that is neither SIMPLEX nor
suspend.
The copy types of the specified C/T

group and the types of bootup C/T
group do not match.
8D78

incorrect.
8D79
A TCA C/T group cannot be deleted.

the following:
2-44
The C/T group ID is incorrect.
The C/T group is not registered.
There is a TCA copy pair in the

corresponding C/T group.

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
There is a copy pair that is being

dissolved or suspended in the
specified C/T group.
8D80

incorrect.
8DD1
An SI copy pair cannot be made,

resynchronized, or suspended because
the UR ATTIME suspend time has been
set for the specified SI C/T group.
8DF0

because the sub-command code is
incorrect.
8DF1

incorrect.
8DF2

because the specified volume is either
not a TCA volume, or not the P-VOL.
8DF3

because the specified volume is in the
NOT READY status.
8DF4

8DF5

because the SSID and CU number in
the host command parameter do not
match.
8DF6

because the serial numbers of the host
command parameter and the local
storage system do not match.
8DF7

because the SSID of the host command
parameter and the local storage system
do not match.
8DFF

because the sub-command code is
incorrect.

2-45
Table 2-12 Details of error codes 8Fxx

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
8F00

because the specified volume is an
external volume.
8F10

because the specified volume has been
made as a copy pair for SI or
FlashCopy and cannot be used for this
combination.
8F14

Reserve volume.
8F17

because the specified volume is online.
8F18

made as a copy pair for another
program product.
8F19

specified volume cannot be used in UR.
8F1B

because the specified P-VOL is not in
the SIMPLEX status.
8F1C

resynchronized because the specified PVOL is not in the suspend status.
8F1E

because the cache or shared memory is
being recovered.
8F1F

because the cache or shared memory is
blocked.
8F21
A UR copy pair cannot be made. The

The configurations cannot be

combined because the specified
volume is the P-VOL of a TC or TCA
copy pair, or the specified volume
is part of an SI copy pair.
(Zero) 0 is specified as the mirror

ID in the TC or TCA configurations.
Alternatively, a UR copy pair cannot be

resynchronized because the
2-46

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
configuration does not allow the status

to be changed.
8F24

because a path has not been
established between the devices.
8F25

volume contains PIN data.
8F28

resynchronized because the specified PVOL or S-VOL cannot be accessed.
8F29

because the P-JNL group cannot be
used.
8F2A

because the specified P-VOL satisfies
one of the following conditions:
The P-VOL is being used as the SVOL for FlashCopy.

FlashCopy SE.
The P-VOL is a TSE-VOL.
8F2B

because the specified P-VOL is
8F33

made as a copy pair for another
program product.
8F35

because the specified volume is
blocked.
8F39

because the UR program product is not
installed.
8F4D

8F50
The R-JNL group is not registered.
The R-JNL volume is blocked.
The specified S-VOL is blocked.
A UR copy pair could not be made or

resynchronized because of heavy
workload in the specified storage

2-47
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
system. Re-execute the operation after

waiting for 5 to 6 minutes.
8F53

because the configuration does not
allow the status transition. (For
example, the specified volume has
already been made as an SI copy pair
and cannot be used for this
combination.)
8F58

The pair statuses of the specified

S-VOL and P-VOL do not match.
The statuses of the R-JNL group

and M-JNL group do not match.
8F67

because the specified S-VOL does not
support external volumes.
8F6D

command device.
Table 2-13 Details of error codes C0xx

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C023
The specified serial number or SSID of

the primary storage system is different
from the storage system serial number
or SSID of the local CU.
C026
A path cannot be set because the

specified CU number for the secondary
site is not supported for the primary or
C02B
The specified P-VOL does not match the

startup volume.
C02C
The specified serial number or SSID of

the primary storage system is different
from the storage system serial number
or SSID of the local CU.
C032
The copy type for making a TC or TCA

copy pair is incorrect. (You can specify
NOCOPY, Full Copy, or Resync only.)
2-48

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C048

because the specified serial number or
SSID of the primary storage system
serial number or SSID of the local CU.
C04C

SSID of the secondary storage system
serial number or SSID of the RCU, or
the path is not registered.
C04D

SSID of the secondary storage system
serial number or SSID of the RCU.
C055

because the TC or TCA volume is in the
SIMPLEX status.
C058
The P-VOL number in the TC or TCA

parameter does not match the bootup
volume number.
C059

primary storage system in the TC or
TCA parameter does not match the
storage system serial number or SSID
of the local CU.
C05A

of the local CU.
C05D

secondary storage system in the TC or
of the RCU.
C05E

of the RCU.
C063
The S-VOL number in the TC or TCA

volume number.

2-49
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C064

of the local CU.
C065

of the local CU.
C06A

because the TC or TCA volume is in the
SIMPLEX status.
C06D
The P-VOL number in the TC or TCA

volume number.
C06E

of the local CU.
C06F

of the local CU.
C072

of the RCU.
C073

of the RCU.
C074
No TC copy pair can be made because

the TC program product is not installed.
C078

volume number.
C079

of the RCU.
2-50

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C07A

of the RCU.
C0A1

C0A2

C0B6

because the specified volume is in the
SIMPLEX status.
C0C5
A copy pair cannot be suspended

because it is already in the suspend
status.
C0C6

because it is already in the SIMPLEX
status.
C0C7

because it is already in the SIMPLEX
status.
C0F1
The command to suspend could not be

executed because the S-VOL for TC is
in the Pending status.

Type of error
Error
code
C120
C122
Error details
An attempt to establish a path has
failed. Possible reasons include either
of the following:
For an inter-CU logical path, the

number of RCUs registered in the
MCU exceeds 4.
For an inter-DKC logical path, the

number of path group IDs
registered in one storage system
exceeds 64.

because the specified RCU parameter is
invalid.
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
2-51
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C123
The specified RCU is not registered (the

path is not established).
C126
The command to delete a path could

not be executed because there is a TC,
TCA, or UR copy pair or journal volume
in the target CU.
C127
An attempt to establish or delete some

of the specified multiple paths have
failed. Possible reasons include one or
more of the following:
C128
The port or MP status is abnormal.
A cable is not connected properly.
The specified port is invalid.
An attempt to establish or delete all the

specified multiple paths has failed.
the following:
The port or MP status is abnormal.
A cable is not connected properly.
The specified port is invalid.
C129

because the number of SSIDs
registered in the RCU exceeds four.
C12A

because the device-identifying code of
an RCU for which path deletion is
specified is invalid, or because the RCU
type (FIBRE/ESCON) is invalid.
C12B

because there are one or more paths
that have a different serial number.
C12C

because automatic port switching
cannot be performed for the specified
path.
C12D

because the device-identifying code of
an RCU for which path registration is
specified is invalid, or because the RCU
type (FIBRE/ESCON) is invalid.
C12E

because all CU numbers of an RCU for
2-52

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
which path creation or deletion is

specified are not the same.
C12F

The specified CU number is not

defined.
An LDEV is not defined for the

specified CU number.
C162

because the corresponding bootup pair
is not in the suspend status.
C184

because an attempt to change the SVOL status failed.
C189

dissolved because the copy pair status
is invalid.
C18A
The copy pair cannot be dissolved. The

The status of the bootup volume is

being changed.
There is a copy pair in the group

that has a status that is being
changed.
C194

because the S-VOL status is being
changed.
C195

because the specified copy pair is
already in the suspend status.
C198

because there is no copy pair that can
be suspended in the group.
C199
The copy pair cannot be suspended.

following:
C1BE
The status of the bootup volume is

being changed.
There is a copy pair in the group

that has a status that is being
changed.

changed because the storage system is
being turned on.

2-53
Error
code
C1D1
Type of error
Error details
The specified copy pair cannot be
suspended, resynchronized, or deleted
because a path is not set up between
CUs (SSIDs) in the copy pair, or the
path is in an error status.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
N

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C211

the specified copy pair is already in the
DUPLEX status.
C213

because the serial number or SSID of
the primary storage system for the
parameter does not match the actual
serial number or SSID of the primary
storage system.
C214

because the serial number or SSID of
the secondary storage system in the
parameter is different from the one
already registered with the path
(including ones without a path).
C215

the specified S-VOL is in use by
another copy pair.
C21A

because the specified copy pair is not in
the suspend status.
C22A

because the status of the specified
volume is SIMPLEX.
C23E

because the specified copy pair is in the
Pending status.
C28B
Copy pair resynchronization, which

causes a copy direction reversal,
cannot be made because the specified
copy pair is not in the SWAPPING status.
C28C
Copy pair resynchronization, which

causes a copy direction reversal,
2-54

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
cannot be made because a path in the

reverse copy direction is not set.
C2A0

the charging limit of the MCU program
product has been exceeded.
C2A3

the charging limit of TC in the MCU has
been exceeded. Check the license
capacity of this and all related program
products.
C2A4

the charging limit of TCA in the MCU
has been exceeded. Check the license
products.
C2A8

the charging limit of the RCU program
product has been exceeded.
C2B3
A copy pair cannot be created because

the HDPz volume specified for the PVOL is being expanded.
C2B6

the pages of the HDPz volume specified
for the P-VOL are being released.
Table 2-16 Details of error codes C3xx - C8xx

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C300
A TC/TCA copy pair that is to be linked

with UR cannot be made because the
MCU.
C301
A TC/TCA copy pair that is to be linked

with UR cannot be made because the
RCU.
C305

the charging limit of TC in the RCU has
been exceeded. Check the license
products.

2-55
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C306

the charging limit of TCA in the RCU
has been exceeded. Check the license
products.
C30D
The specified volume within the RCU,

or another volume which belongs to the
same group is in transition to a
SIMPLEX or suspend status. Please try
the operation again in a few minutes.
C310
The MCU is not NVS ON.
C311
The subsystem level cache of the MCU

is not valid.
C312
The P-VOL is not in the SIMPLEX status.
C313
The P-VOL is not in the suspend status.
C314
The P-VOL is not in the SIMPLEX status.
C315
The P-VOL has PIN data.
C316
The drive copy is being performed on

the P-VOL (troubleshooting).
C317
The drive copy is being performed on

the P-VOL (SVP request).
C318
The copy task ending process is being

performed on the P-VOL.
C319
The collection copy is being performed

on the P-VOL.
C31A
The P-VOL is in a collection access

status.
C31B
The logical volume of the P-VOL is

blocked (PDEV blocking factor).
C31C
The P-VOL cannot be accessed

(because the LDEV is blocked or in the
NOT READY status).
C31D
Formatting of the logical volume is

being performed on the P-VOL.
C31E
The P-VOL is in the READ ONLY status.
C320
The logical path between the MCU and

the RCU is not set (number of path =
0).
C321
The condition setting for the number of

the Minimum Path between the MCU
and the RCU is invalid.
2-56

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C322
The MCU is a storage system type that

is not supported by TC or TCA.
C324
The RCU sequence (number, SSID or

CU) is incorrect.
C325
The RCU is not NVS ON.
C326
The subsystem level cache of the RCU

is not valid.
C327

the status of the P-VOL does not permit
remote copy.
C328
The track format of the P-VOL and SVOL do not match.
C32A
The S-VOL is protected by LDEV

security.
C32B
The P-VOL is protected by LDEV

security.
C32C
The S-VOL is protected by LDEV guard.
C32E

connection with the specified S-VOL is
not supported.
C32F
The condition for the number of

cylinders for TC or TCA volumes is
incorrect (the number of cylinders in
the P-VOL > the number of cylinders in
the S-VOL).
C330
The condition for the TC or TCA volume

capacity is incorrect (not P-VOL=SVOL).
C332
The device level cache of the S-VOL is

not valid.
C333
The S-VOL is not DFW ON.
C335
The S-VOL is a TCA P-VOL.
C336
The S-VOL has PIN data.
C337
The S-VOL is in the Reserve status.
C338
An intervention request has been

issued for the S-VOL (S-VOL or reserve
volume of SI).
C339
The S-VOL is in the FC status.
C33A

the specified S-VOL does not support
TC.

2-57
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C33B
The S-VOL is an S-VOL of another copy

pair.
C33C

the specified S-VOL is not installed.
C33E
An intervention request has been

issued for the S-VOL (DEV NOT READY
status).
C33F
The S-VOL is a TC or TCA pair volume.
C35C
The P-VOL cannot be accessed.
C370

the Minimum Path is incorrect (path
problem or invalid path).
C371
Recovery processing for cache memory

or shared memory is being performed.
Wait a few minutes, and then execute
again.
C372
Recovery processing for cache memory

or shared memory is being performed.
Wait a few minutes, and then execute
again.
C373

the specified S-VOL is a Reserve
volume.
C374

the specified P-VOL is a Reserve
volume.
C378

the Minimum Path is incorrect (multiple
CU number setting or path blocking
issue).
C379

the Minimum Path is incorrect (path
problem or invalid path).
C37B
A TC copy pair cannot be defined or

The S-VOL is in an unusable state.
The microprogram version of the

MCU or RCU does not support the
function or configuration.
C37C
The subsystem level cache of the RCU

is not valid.
C37D
The RCU is not NVS ON.
2-58

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C37E
The device level cache of the S-VOL is

not valid.
C37F
The S-VOL is not DFW ON.
C380
The cache for the MCU is blocked on

one side (in transition).
C381
The cache for the MCU is being

recovered.
C382
The cache for the MCU is being blocked

on one side (in transition) or it is being
recovered on one side.
C388

the P-VOL is not supported for the
emulation type.
C38B
The RCU is already in use by TC or

TCA.
C38D
A TC copy pair cannot be defined or

The S-VOL is in an unusable state.
The microprogram version of the

MCU or RCU does not support the
function or configuration.
C38E
The S-VOL device is not supported by

TC or TCA.
C390
The S-VOL is not in the suspend status.
C391
The S-VOL is in a copy pair status that

does not permit copying.
C392
The S-VOL is online. Alternatively, a

copy pair was already made for a copy
type other than TC or TCA.
C393
The S-VOL has PIN data.
C394
C395
The S-VOL cannot be used (because of

a logical volume being blocked,
collection access, etc.).
C398

the S-VOL is not supported for the
emulation type.
C39E
The P-VOL capacity exceeds the volume

capacity within which a copy pair can
be made.

2-59
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C39F
The P-VOL or S-VOL capacity exceeds

the volume capacity within which a
copy pair can be made.
C3A0
The P-VOL device is not supported by

TC or TCA.
C3A4
The RCU does not support the S-VOL

host online check indication function.
C3A5
C3A6
The specified SSID, or CU number of

the RCU is incorrect.
C3A8

the specified copy pair is made up of
volumes whose emulation types are
3390-A and non-3390-A.
C3AA
The RCU has its cache (one side)

blocked (NVS).
C3AB
The RCU has its cache (one side)

blocked.
C3AD
The RCU has exceeded the charging

limit for the TC or TCA program
product.
C3AE
The TC or TCA program product has not

been installed on the RCU.
C3AF
The storage system type for the RCU is

not supported by TC or TCA, or the C/T
group value for TCA is incorrect.
C3B1
The condition setting of the number of

the Minimum Path is incorrect.
C3B6
The TC or TCA P-VOL is an SI pair

volume.
C3B7
The TC or TCA S-VOL is an SI pair

volume.
C3BA

the specified SSID or CU number for
the RCU is not supported for the
primary and secondary site.
C3BD
The P-VOL is online.
C3BE
When the P-VOL of a TC or TCA copy

pair is also the S-VOL of an SI copy
pair, it must be in the Split status.
Also, a reserve volume, a P-VOL in the
Reverse Resync status, and the S-VOL
for FlashCopy cannot be specified.
2-60

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C3BF
The S-VOL of an SI copy pair or a

Reserve volume cannot be specified as
the S-VOL of a TC or TCA copy pair.
Also, a P-VOL in the Reverse Resync
status and the S-VOL for FlashCopy
cannot be specified.
C3C0
When the P-VOL of a TC or TCA copy

pair is also the S-VOL of an SI copy
pair, both S-VOLs must be a copy pair
in a one-to-one combination.
C3C1
The S-VOL is not made under the C/T

group.
C3C2
The C/T group ID specified in making a

copy pair is already in use in the SVOL.
C3C3
The 4MCU is already registered or

made under the subjected C/T group.
C3C4
The option information (timer type,

timeout) for an operating (already
being made a copy pair) C/T group
cannot be changed.
C3C5
A copy pair could not be made because

there are multiple storage systems at
the primary site, but the timer type is
not System.
C3C6

because the update timeout option is
different for copy pairs that already
exist and those that have not yet been
made on the primary site that has
multiple storage systems.
C3C7
A TC or TCA copy pair cannot be made.

following:
The specified volume is part of a

TC, TCA, or UR copy pair with
another volume.
The specified volume is a journal

volume.
C3C9
The C/T group is not registered in the

RCU.
C3CA
The S-VOL is in the reserve status or

the RCU, the S-VOL or the M-R path is
in the BUSY status.
C3CB
The TCA program product has not been

installed on the RCU.

2-61
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
C3CD
The S-VOL of a TC or TCA copy pair is

an SI pair volume.
C3D1
Another C/T group ID is already

registered or made in the RCU.
C3D2
The storage system type of the RCU is

not supported by TC or TCA.
C3D3
The specified SSID, or CU number of

the RCU is incorrect.
C3D6
The specified S-VOL cannot be used

because the device cannot be
recognized from the connection port.
C3D7
The status of the S-VOL in the RCU is

incorrect.
C3D8
A TC/TCA copy pair cannot be made

S-VOL is a system residence volume.
C3D9

the HDPz volume specified for the SVOL satisfies one of the following
conditions:
The HDPz volume is being used by

other program product.
The capacity is being changed.
The pages are being released.
The pool is being initialized.
C3DA

C3DB
The S-VOL is not in the suspend status.
C3FE

TCA and TC cannot be specified
simultaneously.
C4FC

or resynchronized because the
necessary shared memory is not
implemented in the RCU.
C825
Commands that use TC copy pairs, UR

copy pairs, or the Remote DKC Control
Function cannot be executed because
the number of executable paths is less
than the minimum value.
C8D1
The command for registering command

devices via the Remote DKC Control
Function (YKBLDCMD) cannot be
2-62

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
HDT Othe
z
r
executed because the specified volume

does not exist.
Table 2-17 Details of error codes CBxx

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
CB10

there was an attempt to make a copy
pair for both directions with the same
C/T group ID.
CB12
A TCA copy pair cannot be created for

The C/T group ID specified in the

RCU is already used for UR(OPEN).
A total of 128 C/T groups are used

in the RCU for UR(OPEN) and
TCA(MF/OPEN).
CB18
A copy pair cannot be added to a C/T

group where the P-VOL and the S-VOL
are being swapped.
CB1D
A dummy volume cannot be created on

the S-VOL.
CB1F
The current RCU version does not

support Fibre TC or TCA.
CB60
Fibre TC or TCA has not been installed

on the RCU.
CB61
Copy pairs with Fibre and ESCON paths

cannot exist within the same C/T
group.
CB62
Copy pairs with Fibre and ESCON paths

cannot exist within the same storage
system.
CB64
The storage system type of the MCU is

not supported (not 3990-6/6E, or is
2105).
CB66

because the necessary difference area
does not exist in the RCU.
CB67

because extended shared memory is
not implemented in the RCU.

2-63
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
CB68

because the necessary difference area
does not exist in the MCU.
CB69
The upper limit of 4,096 (or more) copy

pairs cannot be made within the same
C/T group by RCU.
CB78

the specified S-VOL is defined as a
command device.
CB7E

because the CLPR that the specified SVOL belongs to differs from the one
documentation.
CB9E

the specified S-VOL does not support
either one or both of the following:
The timestamp transfer mode
The Open/MF Consistency

Preservation Function
CBD8

the specified P-VOL is not a P-VOL for
UR.
CBD9

the specified S-VOL satisfies one of the
following conditions:
The S-VOL is being used for

FlashCopy.

FlashCopy SE.
The S-VOL is a TSE-VOL.
CBDC

because the mirror ID of UR is 0 when
linked with UR.
CBDD

because a UR copy pair is being copied
in a TC-UR Multi-Target configuration.
CBE2

the specified P-VOL is a pool volume.
CBE3

the specified S-VOL is a pool volume.
CBED
A TC/TCA copy pair cannot be made.

following:
2-64

Type of error
Error
code
CBEE
CBF8
CBFA
CBFC
Error details
The specified S-VOL is the S-VOL

of a UR copy pair.
The specified S-VOL is a journal

volume.
A TC/TCA copy pair cannot be created

for one of the following reasons:
The specified P-VOL is already

created as a P-VOL in a delta
resync UR copy pair.
The specified P-VOL is created as a

P-VOL in a copy pair in a 3DC
Multi-Target (URxUR)
configuration.
A TC copy pair cannot be created for

The MCU or RCU microcode version

does not support the connection.
The MCU or RCU model does not

support the connection.
This RCU model does not support

differential-data management by
cylinders.
A TC copy pair cannot be operated on

for one of the following reasons:

All of the mainframe Fibre Channel

A TC copy pair cannot be made or

resynchronized because the C/T group
ID is not in the supported range.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
Table 2-18 Details of error codes DBxx - E8xx

Type of error
Error
code
DB02
Error details
changed because the status transition
is not allowed.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
N
In the following examples, status

transition is not allowed:
When an attempt to create a copy

pair is made for a copy pair with a
status is not SIMPLEX.

2-65
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
When an attempt to re-create a

copy pair is made for a copy pair
with a status is not in the suspend
status.
Check the status of the copy pair again

because there is a possibility that
status transition has been performed
correctly.
DB03

changed because the copy pair status
is being changed (Suspending or
Deleting).
DB07

changed because the power-on process
is in progress.
DB08

changed because the power-off process
is in progress.
DB09

because the specified volume is a TCA
copy pair.
DB0C

parameter or ALLJNL parameter)
because the volume is specified.
E80B

because the expanded shared memory
table necessary for the EXCTG
registration has not been initialized.
E826
Deletion from EXCTG has failed

because the specified EXCTG is not
registered.
E82F
Deletion from EXCTG has failed

because the specified journal group is
not registered.
E843

because the CLPR number of the
specified volume and the CLPR number
of the journal group do not match.
E869

include both of the following:
2-66
The R-JNL of the specified UR copy

pair is being used by a UR copy
pair that has another mirror ID.
The mirror status of another UR

copy pair that is using the specified

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
UR copy pair is Halting or

Stopping.
E86B
A UR copy pair cannot be dissolved

because the specified volume is not a
UR copy pair.
E86D

because the storage system is being
turned on.
E86E

because a specified volume's SM is not
present.
E871

because inter-DKC logical paths (for
both directions) have not been defined.
Make sure that inter-DKC logical paths
have already been established in both
directions.
E876

because the storage system serial
number specified for the S-VOL is
invalid.
E878
A UR copy pair could not be made

because there is mix of volumes with
emulation types are 3390-9A and
non-3390-9A in the specified journal
group.
E87B

not registered.
E87C

because a journal volume is not
registered in the specified journal
group.
E87D

volume is not a UR copy pair.
E87E

because the specified P-VOL or S-VOL
is a volume comprising a journal group.
E880

specified P-VOL or S-VOL does not
match the emulation type for a volume
comprising a journal group.

2-67
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
E881

resynchronized because the storage
system is being turned on.
E882

volumes comprising the specified M-JNL
group does not match that of the R-JNL
group.
E885

because the specified R-JNL group has
with another M-JNL group.
E888

because the specified M-JNL group has
with another R-JNL group.
E889

because the specified journal group has
already been made into a UR copy pair
by using another mirror ID.
E890
A UR copy pair cannot be made for one

The specified volume is already

registered in another journal
group.
The specified volume is already

registered in the same journal
group by using the same mirror ID.
The specified S-VOL is already

registered in the same journal
group by using another mirror ID.
The specified journal group is not

set to be used in a 3DC (URxUR)
configuration, but there is a copy
pair that has another mirror ID in
the journal group.
E891

because the maximum number of copy
pairs has already been registered in the
specified M-JNL or R-JNL group.
E894
A UR copy pair cannot be created in a

3DC (URxUR) configuration because
the third mirror ID is specified in the
same journal group.
E896

because the UR program product or the
2-68

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r

product has not been installed.
E897
A UR copy pair cannot be created for

The specified M-JNL and R-JNL

groups are not set to be used in
3DC (URxUR) configurations.
The specified R-JNL group is

already in use.
Another mirror ID is already

defined for the specified journal
group.
E898

R-JNL group is in use as an R-JNL
group for a UR copy pair with another
mirror ID.
E89A

because an inter-DKC logical path has
not been established in the forward or
reverse direction. Make sure that interDKC logical paths have already been
established in both directions.
E89B

because the status from the previous
connection with another storage
system remains in the specified M-JNL
or R-JNL group.
Specify a different journal group, or

delete the specified journal group and
then register it again.
E8A2
A UR copy pair cannot be made for one

The serial number of the storage

system specified for the S-VOL is
incorrect.
Another path group ID is already

assigned for the specified journal
group.
E8A6
A resynchronization that reverses the

copy direction for UR copy pairs cannot
be performed because the journal
group of the specified volume is not
E8A7

be performed because a journal volume
is not registered in the storage system

2-69
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
for the journal group of the specified

volume.
E8A8
The specified copy pair cannot be

suspended because it is not a UR copy
pair, or the P-VOL and S-VOL for
journal group do not match.
E8A9

because the storage system is being
turned on.
E8B6

because the mirror ID of the specified
R-JNL group is used by another UR
copy pair.
E8B9

registered to EXCTG.
E8BB

because the mirror ID is different from
the registered mirror ID.
E8BD

because the number of journal groups
to be registered exceeded the
maximum number which can be
registered.
E8BF

because the number of subordinate
storage systems has exceeded the
maximum number which can be
registered.
Table 2-19 Details of error codes EAxx

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EA00

because the specified volume
comprises an R-JNL group.
EA01
A UR copy pair cannot be made for

either of the following reasons:
2-70
An attempt was made to make a

copy pair that already exists.
The specified P-VOL or S-VOL for

that UR copy pair is already in use
by another copy pair.

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EA02

because the specified volume
comprises an M-JNL group.
EA03

because the specified S-VOL is already
in use as another UR copy pair.
EA07

because the number of copy pairs that
can be registered in the specified M-JNL
group has exceeded the maximum
limit.
EA08

because the number of copy pairs that
can be registered in the specified R-JNL
group has exceeded the maximum
limit.
EA09

because the M-JNL group is not in the
Initial, Active, or Stop status.
EA0A

because the status of the R-JNL group
is incorrect.
EA12
The UR copy pair could not be

resynchronized in the reverse direction
because the copy pair is not in the
SWAPPING status.
EA13

resynchronized because the volume
specified for the P-VOL is the S-VOL of
the UR copy pair.
EA15

resynchronized because the volume
specified for the S-VOL is the P-VOL of
the UR copy pair.
EA18

EA19

group is not in the Stop status.
EA1B
The YKRESYNC command with the

PREPARE parameter could not be
executed because the specified journal
group is either not in the suspend
status to obtain the journal data as

2-71
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
differential data, or not in failure

status.
EA1C
A UR copy pair resynchronization,

which causes a copy direction reversal,
cannot be made because the R-JNL
group of the S-VOL is not in the Stop
status.
EA1E

be performed because the specified SVOL is not the S-VOL of the UR copy
pair.
EA20

be performed because the specified PVOL is not the P-VOL of the UR copy
pair.
EA22

cannot be made because the journal
group is not in the Stop status.
EA25

cannot be made because the copy pair
is not in the SWAPPING status.
EA29

Active or Stop status.
EA2C

because the R-JNL group is not in the
Active or Stop status.
EA33

Active status.
EA36

because the R-JNL group is not in the
Active status.
EA3A

because the specified S-VOL status is
being changed at the moment.
EA3B

cannot be made because the copy pair
is in the TRANS status.
2-72

Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EA3C
A suspension that reverses the copy

direction cannot be performed for the
UR copy pair, because the specified SVOL belongs to the M-JNL group.
EA40

because the charging limit of the MCU
program product has been exceeded.
EA41

because the charging limit of the RCU
EA46
A UR copy pair between the

intermediate site and the remote site
cannot be deleted or suspended
because the journal group of the UR
copy pair between the primary site and
the intermediate site in a 3DC Cascade
(URxUR) configuration is in the Active
status.
EA4D
The UR copy pair cannot be suspended

because it is a delta resync pair.
EA89
The status cannot be changed from

error status to the delta resync
preparatory status, because the
specified P-VOL is not in HOLDER status.
EA8A
The status of a UR copy pair cannot be

changed because the primary storage
system is currently being turned on or
turned off.
EA95

the pool of the HDPz volume specified
for the P-VOL of a UR copy pair is being
initialized.
EAA0
The UR copy pair cannot be operated

for each EXCTG because of the
following reasons:
EAA2
The JNLG specified in the copy

group is not registered in the
EXCTG.
There is a copy pair with a status

that is TRANS.

because the charging limit of UR in the
MCU has been exceeded. Check the
license capacity of this and all related
program products.

2-73
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EAA3

because the charging limit of TC in the
RCU has been exceeded. Check the
program products.
EAA5

program products.
EAA6

MCU has been exceeded. Check the
program products.
EABC

because shared memory is not
implemented for the specified LDEV
number.
EAD0
A UR copy pair cannot be made with

the HOLD parameter specified because
the micro does not support the delta
resync function.
EAE5

the HDPz volume specified for the PVOL of a UR copy pair is being
expanded.
EAE7

because mode 707 of a storage system
option is ON and the specified volume
is part of a TC copy pair.
EAF6
A UR copy pair could not be made with

the HOLD parameter, or a UR copy pair
could not be resynchronized because
the copy pair was in a status for which
status transition could not be
performed.
Table 2-20 Details of error codes EBxx

Error
code
EB02
2-74
Type of error
Error details
changed because the specified journal
group number is invalid.
SI
TC
TCA
UR
CMD
PAT
H

HDT Othe
z
r
N
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EB08
Registration to or deletion from EXCTG

has failed because the micro is being
replaced, or there are intermixed
micros which do not support 4x4
configuration.
EB09

has failed because the entered
parameter was incorrect.
EB0A

has failed because another EXCTG
registration or deletion process is in
progress.
EB0F

has failed because the specified device
is not an arbitration command device.
EB24

because the S-VOL of the specified
copy pair is in one of the following
statuses:
EB25
It is not the S-VOL of a UR delta

resync copy pair.
The status of the UR delta resync

copy pair is not Duplex.
A delta resync pair cannot be executed

copy pair is in one of the following
statuses.
It is not the S-VOL of a UR delta

resync copy pair.
The status of the UR delta resync

copy pair is not Duplex, SuspOp,
SuspEr, or SuspCu.
EB28

because the Disaster Recovery
Extended program product has not
been installed in the RCU.
EB2D
A UR copy-pair operation cannot be

performed because the shared memory
necessary for using UR is not
implemented.
EB30

changed because the specified mirror
ID is invalid.
EB37
A UR copy-pair operation cannot be

performed because the microcode is
currently being changed.

2-75
Type of error
Error
code
EB38
Error details
When making a copy pair using the
same journal group number and mirror
ID as an existing copy pair, you cannot
specify a secondary storage system
that differs from the secondary storage
system of the existing copy pair.
Therefore, a UR copy pair cannot be
made.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
This error occurs if there is more than

one secondary storage system in the
same copy group or when the specified
journal group number and mirror ID
are used for another copy group.
EB3B
The batch pair status command cannot

be executed because the CU number
specified by the YKEWAIT command or
YKRSCAN command is not supported by
this model.
EB3C

changed because the specified serial
number or SSID of the primary storage
system does not match the actual serial
number or SSID of the primary storage
system.
EB3D

changed because the specified serial
number or SSID of the secondary
storage system does not match the
actual serial number or SSID of the
EB48
A delta resync pair cannot be made.

following:
The P-VOL of a TC copy pair and

another P-VOL of a UR copy pair do
not match.

on the copy source is incorrect.
EB49

because the delta resync function is not
supported in the RCU.
EB4C

because the specified R-JNL group is
not registered.
EB4D

because the specified M-JNL group is
not registered in the storage system.
2-76

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EB4F

because the timer type for M-JNLG
differs from that for R-JNLG.
EB50

because the specified volume does not
exist.
EB51

because the specified S-VOL has PIN
data.
EB52

because the specified S-VOL cannot be
accessed.
EB53

because the specified S-VOL is blocked.
EB56

because the status of the cache is
abnormal.
EB5B

because the LDEV guard is set for the
specified P-VOL or S-VOL.
EB5D

because the LDEV security is set for the
specified P-VOL or S-VOL.
EB5E

because the S-VOL is not in the
SIMPLEX status. Alternatively, a UR
copy pair cannot be resynchronized
because the S-VOL is not in the
suspend status.
EB5F

installed on the secondary storage
system.
EB60

because the capacities of the P-VOL
and S-VOL do not match.
EB61

because the path between the primary
storage system and the secondary
storage system is invalid.
EB62

because the specified P-VOL is a
command device.

2-77
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EB63

because another journal group pair has
been already made in the R-JNL group.
EB64

because the charging limit of the
EB6B

because the specified S-VOL satisfies
one of the following conditions:

FlashCopy.

FlashCopy SE.
The S-VOL is a TSE-VOL.
EB6E

installed on the primary storage
system.
EB6F

resynchronized because the micro
version on the primary storage system
does not support the 4x4 configuration.
EB70

because the S-VOL had already been
paired by another program product.
EB73

because the S-VOL is a system
residence volume.
EB74

because all of the channel adapters
connected to the mainframe are
blocked.
EB78

because the S-VOL is a command
device.
EB79

resynchronized because the S-VOL is
online.
EB7A

because a journal cache remains in the
R-JNL group.
EB7D

because the specified S-VOL is an
external volume.
2-78

Type of error
Error
code
EB7E
Error details
The specified S-VOL is being used

in a FlashCopy relation.

for the S-VOL of an SI copy pair.

for the S-VOL of an SI copy pair,
and is being resynchronized in the
reverse direction or is being shared
with the TC copy pair.
The specified S-VOL is a Reserve

volume.
The specified S-VOL is an HDPz

volume and is being used by
another program product.

as the P-VOL of an SI copy pair
with a C/T group ID, and is also
being used by another program
product as the P-VOL of an SI copy
pair with a C/T group ID.
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EB7F

specified S-VOL is not supported.
EB87

EB88
The path from the secondary

storage system to the primary
storage system is not set.
The S-VOL is in the SIMPLEX

status.
A UR copy pair could not be made

because of one the following reasons:
The specified S-VOL is already

being used as the S-VOL of an SI
copy pair.
The specified volume is in Not

Ready status.
The LDEV guard (PROTECT) is set

for the S-VOL.
EB89

because the emulation types of the
specified P-VOL and S-VOL do not
match.
EB8A

because the emulation types of the

2-79
Type of error
Error
code
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
specified M-JNL group and R-JNL group

do not match.
EB94

changed because the status of the
specified copy pair does not allow the
status transition.
EBA0

changed because the specified S-VOL is
not installed.
EBA7

the S-VOL satisfies one of the following
conditions:
The capacity is being expanded.
The pages are being released.
The pool of the corresponding

HDPz is being initialized.
EBA8

because the remote command has
been issued to a volume that is not
installed.
EBB3

executed because the command device
has not been defined.
EBBD

because the command device is under
LDEV guard.
EBC6

copy pair is used by another program
product (SI/FlashCopy).
EBCE

parameter) because the specified SVOL has old differential information.
Execute the UR copy pair
resynchronization (with the ALLJNL
parameter).
EBD0

executed because the path between the
specified storage system or CU (SSID)
and the command target storage
system is not set, or because an error
has occurred on the path.
EBD3
The path for the remote command

transfer route for the second site
onwards, or for the command device,
2-80

Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
might not be set, or a failure occurred

in the remote command transfer route.
Make sure that the path and the
command device are set, available, and
have not failed, and then re-execute
the operation.
EBD9

program products.
EBDA

because the charging limit of TCA in
the RCU has been exceeded. Check the
program products.
EBDB

program products.
EBE0

because the specified S-VOL is part of a
delta resync UR copy pair.
EBE1

because none of the S-VOLs of the
delta resync pair are the S-VOLs of the
other UR.
EBE2

because the differential bitmap
information is not in the ready status to
delta resync. To overwrite the S-VOL of
the delta resync pair with the P-VOL's
data, execute the YKRESYNC command
with the ALLJNL parameter.
This error may occur because the TC

update data (master journal of the
delta UR pair) and the update data of
the restore journal maintained by the
UR pair is inconsistent.
EBE5

volume of the specified R-JNL is
blocked.
EBEB

resynchronized because the emulation
type of the specified volume is
3390-9A.

2-81
Error
code
Type of error
Error details
SI
TC
TCA
UR
CMD
PAT
H
HDT Othe
z
r
EBF2
Resynchronization in the reverse copy

direction cannot be performed for a UR
copy pair because the UR ATTIME
suspend time is already set.
EBF3

because the UR ATTIME suspend time
is already set.
EBFD

because the specified sub C/T ID is not
2-82

Acronyms and Abbreviations

The following acronyms and abbreviations might be used in this guide.
A
API
application programming interface
B
Business Continuity Manager
A generic name for the following products:
Hitachi Business Continuity Manager Basic
Hitachi Business Continuity Manager Universal Replicator 4x4 Extended CTG
C
C/T ID
consistency group ID
CCA
command control address
CHA
channel adapter
CLI
command line interface
W X
Acronyms-1
CSB
channel status byte
CU
control unit
D
DAD
device address domain
DASD
direct access storage device
DBCS
double byte character set
Device Manager
Hitachi Device Manager
DKC
disk controller
DSB
device status byte
DSORG
data set organization
E
EXCTG
extended consistency group
G
GTF
generalized trace facility
Acronyms-2
W X
H
HDPz
Hitachi Dynamic Provisioning Software for Mainframe
HDTz
Hitachi Dynamic Tiering Software for Mainframe
HTTP
HyperText Transfer Protocol
HTTPS
HyperText Transfer Protocol Security
I
IBM HTTP Server
IBM HTTP Server for z/OS
ID
Identifier
IPv4
Internet Protocol Version 4
IPv6
Internet Protocol Version 6
ISPF
interactive system productivity facility
L
LDEV
logical device
LPAR
logical partition
W X
Acronyms-3
M
M-JNL
master journal
Mainframe Agent
Hitachi Device Manager Mainframe Agent
MCU
main control unit
MIH
missing interrupt handler
O
OS
operating system
P
P-VOL
primary volume
PPRC
Peer to Peer Remote Copy
PSW
program status word
R
R-JNL
restore journal
RACF
resource access control facility
RAID
redundant array of independent disks
Acronyms-4
W X
RCU
remote control unit
RECFM
record format
Replication Manager
Hitachi Replication Manager
REXX
restructured extended executor
RPO
Recovery Point Objective
S
S-VOL
secondary volume
SAF
system authorization facility
SCP
state change pending
ShadowImage
ShadowImage for Mainframe
SM
shared memory
SMP/E
system modification program extended
SSID
storage system ID
SVC
supervisor call interruption
SVP
service processor
W X
Acronyms-5
T
TC
TrueCopy for Mainframe (TrueCopy Synchronous)
TCA
TrueCopy for Mainframe (TrueCopy Asynchronous)
Tiered Storage Manager for Mainframe
Hitachi Tiered Storage Manager for Mainframe
TPC-R
IBM Tivoli Storage Productivity Center for Replication for System z
TSE
track space-efficient
TSO/E
Time Sharing Option/Extensions
U
Universal Replicator for Mainframe
USP
Hitachi Universal Storage Platform
Hitachi Network Storage Controller
USP V
Hitachi Universal Storage Platform V
Hitachi Universal Storage Platform VM
V
VM
virtual machine
VSP
Hitachi Virtual Storage Platform
Acronyms-6
W X
VSP G1000
Hitachi Virtual Storage Platform G1000
X
XML
extensible markup language
XRC
extended remote copy
Z
z/Linux
Linux on IBM System z
W X
Acronyms-7
Acronyms-8
W X
Index
D
2-2
I
Identifying the volume to be processed
1-166
L
List of Messages
1-4
M
Message format 1-2
Message output destination 1-3
Message output format 1-2
Multi-line messages output to SYSTSPRT starting
from YK 1-161
N
Notations used to describe messages
1-3
U
1-166
Index-1
Index-2
Hitachi Data Systems

Corporate Headquarters
2845 Lafayette Street
Santa Clara, California 95050-2639
U.S.A.
www.hds.com
Regional Contact Information
Americas
+1 408 970 1000
info@hds.com
Europe, Middle East, and Africa
+44 (0)1753 618000
info.emea@hds.com
Asia Pacific
+852 3189 7900
hds.marketing.apac@hds.com
MK-94RD262-23

Hitachi Business Continuity Manager Messages

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hitachi Business Continuity Manager Messages

Uploaded by

Copyright:

Available Formats

Hitachi Business Continuity Manager

2014 Hitachi, Ltd. All rights reserved.

Message format...................................................................................................... 1-2

2 Storage system sense byte information.................................................. 2-1

Acronyms and Abbreviations

Want to use Business Continuity Manager to improve the performance of

Functions of Lightning 9900V Series, USP, USP V, VSP or VSP G1000

Method for configuring a system using Hitachi Replication Manager for

Document revision level

Revision 1, supersedes and replaces

Revision 2, supersedes and replaces

Revision 3, supersedes and replaces

Revision 4, supersedes and replaces

Revision 5, supersedes and replaces

Revision 6, supersedes and replaces

December 2007 Revision 7, supersedes and replaces

Revision 8, supersedes and replaces

December 2008 Revision 9, supersedes and replaces

December 2009 Revision 11, supersedes and replaces

Revision 12, supersedes and replaces

Revision 13, supersedes and replaces

Revision 14, supersedes and replaces

Revision 15, supersedes and replaces

November 2011 Revision 16, supersedes and replaces

Revision 17, supersedes and replaces

Revision 18, supersedes and replaces

November 2012 Revision 19, supersedes and replaces

Revision 20, supersedes and replaces

Revision 21, supersedes and replaces

Revision 22 (internal release only), supersedes and

Revision 23, supersedes and replaces

Revision 10, supersedes and replaces

Hitachi Business Continuity Manager User Guide, MK-94RD247

Hitachi Business Continuity Manager Installation Guide, MK-95HC104

Hitachi Business Continuity Manager Reference Guide, MK-96HC135

Manuals related to Hitachi Command Suite products:

Hitachi Command Suite Tiered Storage Manager for Mainframe User

Hitachi Command Suite Replication Manager Configuration Guide,

Hitachi Command Suite Replication Manager User Guide, MK-99HC166

Manuals related to storage systems:

Hitachi Virtual Storage Platform Hitachi Universal Replicator for IBM(R) z/

Hitachi Command Control Interface User and Reference Guide,

Hitachi Virtual Storage Platform Hitachi Storage Navigator User Guide,

Hitachi Virtual Storage Platform Hitachi ShadowImage for IBM(R) z/OS(R)

Hitachi Virtual Storage Platform Hitachi Universal Volume Manager User

Manuals related to z/OS:

MVS Initialization and Tuning Reference, SA22-7592

MVS Programming: Assembler Services Reference, SA22-7606,

MVS Setting Up a Sysplex, SA22-7625

MVS System Codes, SA22-7626

MVS System Commands, SA22-7627

Security Server RACF Security Administrator's Guide, SA22-7683

Security Server RACROUTE Macro Reference, SA88-8621

TSO/E Customization, SA22-7783

TSO/E Programming Services, SA22-7789

TSO/E REXX Reference, SA22-7790

TSO/E System Programming Command Reference, SA22-7793

MVS Programming: Assembler Services Guide, SA88-8577

DFSMS: Using Data Sets, SC26-7410

DFSMSdfp Utilities, SC26-7414

IBM Tivoli Storage Productivity Center for Replication Users Guide,

Communications Server IP Configuration Guide, SC31-8775

Communications Server IP Configuration Reference, SC31-8776

Communications Server IP User's Guide & Commands, SC31-8780