Hitachi Business Continuity Manager Messages

7/23/2019 Hitachi Business Continuity Manager Messages

http://slidepdf.com/reader/full/hitachi-business-continuity-manager-messages 1/274

Hitachi Business Continuity Manager

Messages

MK-94RD262-2

Document Organization

Product Version

Getting Help

Contents



© 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 retrievalsystem 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 andassumes no responsibility for its use. This document contains the most current information availableat 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 mostrecent product announcement for information about feature and product availability, or contactHitachi 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 isgoverned 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. HitachiData Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States andother countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,

Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered 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 InternationalBusiness Machines Corporation.

All other trademarks, service marks, and company names in this document or web site areproperties 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 besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

ii

Hitachi Business Continuity Manager Messages

https://portal.hds.com/



Contents

Preface...................................................................................................vIntended audience.................................................................................................... viProduct version.........................................................................................................viRelease notes........................................................................................................... viDocument revision level.............................................................................................vi

Document organization............................................................................................. viiRelated documents.................................................................................................. viiiDocument conventions.............................................................................................. ixConventions for storage capacity values...................................................................... x

Accessing product documentation...............................................................................xiGetting help..............................................................................................................xiComments................................................................................................................ xi

1 Messages............................................................................................. 1-1Message format......................................................................................................1-2

Message output format.....................................................................................1-2

Notations used to describe messages.................................................................1-3Message output destination...............................................................................1-3List of Messages..................................................................................................... 1-4

Message Details................................................................................................1-4Multi-line messages output to SYSTSPRT starting from YK............................... 1-161Identifying the volume to be processed.......................................................... 1-166

Identifying the volume serial number from the REXX script.....................1-166Identifying the volume serial number from the configuration file.............1-166

User completion codes.........................................................................................1-166

2 Storage system sense byte information.................................................. 2-1Details of error codes..............................................................................................2-2

Acronyms and Abbreviations

Index

iii




iv




Preface

This document describes the messages and error codes that are output bythe following program products. In this manual, these products arecollectively 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 v




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 G1000storage systems.

• Method for configuring a system using Hitachi Replication Manager forlinking to Hitachi Replication Manager.

Product version

This document revision applies to Hitachi Business Continuity Managerversion 8.0.0 or later.

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document.

Document revision level

Revision Date Description

MK-94RD262-00 April 2005 Initial Release

MK-94RD262-01 June 2005 Revision 1, supersedes and replacesMK-94RD262-00

MK-94RD262-02 October 2005 Revision 2, supersedes and replacesMK-94RD262-01

MK-94RD262-03 May 2006 Revision 3, supersedes and replacesMK-94RD262-02


MK-94RD262-05 January 2007 Revision 5, supersedes and replacesMK-94RD262-04

MK-94RD262-06 June 2007 Revision 6, supersedes and replacesMK-94RD262-05

MK-94RD262-07 December 2007 Revision 7, supersedes and replacesMK-94RD262-06


vi Preface




Revision Date Description

MK-94RD262-09 December 2008 Revision 9, supersedes and replacesMK-94RD262-08

MK-94RD262-10 July 2009 Revision 10, supersedes and replacesMK-94RD262-09

MK-94RD262-11 December 2009 Revision 11, supersedes and replaces

MK-94RD262-10MK-94RD262-12 June 2010 Revision 12, supersedes and replaces

MK-94RD262-11


MK-94RD262-14 April 2011 Revision 14, supersedes and replacesMK-94RD262-13

MK-94RD262-15 August 2011 Revision 15, supersedes and replacesMK-94RD262-14

MK-94RD262-16 November 2011 Revision 16, supersedes and replacesMK-94RD262-15

MK-94RD262-17 February 2012 Revision 17, supersedes and replacesMK-94RD262-16

MK-94RD262-18 July 2012 Revision 18, supersedes and replacesMK-94RD262-17

MK-94RD262-19 November 2012 Revision 19, supersedes and replacesMK-94RD262-18



MK-94RD262-22 January 2014 Revision 22 (internal release only), supersedes andreplaces MK-94RD262-21

MK-94RD262-23 April 2014 Revision 23, supersedes and replacesMK-94RD262-22

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 Description

Chapter 1, Messages onpage 1-1

Describes the messages.

Preface vii




Chapter/Appendix Description

Chapter 2, Storagesystem sense byteinformation on page 2-1

Describes storage system sense byte information (errorcodes) contained in messages.

Related documentsManuals 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:

• 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

viii 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 User’s 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, includingmenus, menu options, buttons, fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text provided bythe 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

< > angledbrackets

Indicates a variable, which is a placeholder for actual text provided bythe user or system. Example: # pairdisplay -g <group>

Note: Italic font is also used to indicate variables.

[ ] squarebrackets

Indicates optional values. Example: [ a | b ] indicates that you canchoose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicatesthat 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, ornothing. { 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 forperforming 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) arecalculated 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) arecalculated 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

x Preface




Accessing product documentation

The Business Continuity Manager user documentation is available on theHitachi Data Systems Portal: https://portal.hds.com . Check this site for

the most current documentation, including important updates that may havebeen made after the release of the product.

Getting helpHitachi Data Systems Support Portal is the destination for technical support of your current or previously-sold storage systems, midrange and enterpriseservers, and combined solution offerings. The Hitachi Data Systems customersupport staff is available 24 hours a day, seven days a week. If you needtechnical support, log on to the Hitachi Data Systems Support Portal forcontact information: https://portal.hds.com.

Hitachi Data Systems Community is a new global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is an open discussion among these groups about the HDSportfolio of products and services. It is the destination to get answers,discover insights, and make connections. The HDS Community complementsour existing Support Portal and support services by providing an area whereyou can get answers to non-critical issues and questions. Join theconversation today! Go to community.hds.com, register, and complete

your profile.

Comments

Please send us your comments on this document: [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!

Preface xi


http://community.hds.com/





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 inthis 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¢ 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

1-2 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, andthe message format. Messages are listed in the order of message IDs.

Message ID Message text Description

message-ID message-output-destination

SC= xx #1 RC= xx #2(additional-information)#3,4message-text #4 message-description

#1

Severity code, which indicates the severity level. If the output destinationis 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 returncodes were output for the message during command processing, thelargest value is set as the command return code.

#3

Detailed information used to confirm specific issues such as the errorlocation or volume identification information. If the output destination isMSG, this value is set to Value in the message structure.

#4

Character strings enclosed in square brackets ([ ]) might be omitted.

Message output destinationThe 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 messageID and message text are displayed in the ISPF panel. However, if MSGIDOFF is specified, only the message text is displayed at the beginningwithout 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 thesequence.

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 theuser's TSO/E terminal.

For details about the CLI commands, see the Hitachi Business Continuity Manager Reference Guide.

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 takingcorrective action.

Table 1-1 List of messages (message ID YK70x - YK90x)

Message ID Message text Explanation and recommended actions

YK7000T PRTRC=16

Supplied parameters invalid:line

An invalid parameter was specified. Revise the valuespecified on the line number identified by line.

YK7001E PRTRC=16

No parameter-nameparameter supplied.

The parameter parameter-name is not specified.

YK7003E PRT

RC=16

The parameter parameter-

name is invalid: line

The value assigned to the parameter-name parameter

is invalid. Revise the value specified on the line numberidentified by line.

YK7004E PRTRC=16

The parameter parameter-name is invalid.

The value assigned to the parameter-name parameteris invalid.

YK7014I PRT RC: rc CMD: command The command indicated by command was issued, andended with the return code rc .

1-4 Messages





YK7015I PRT RC: rc CMD: command

Severity: Severity

Text: Text

Value: Value

The command indicated by command was issued, andended with the return code rc .

Severity

Severity code stored in Severity for the message

structure

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 numberof messages included in the message structure.

YK7031I PRTRC=0

Scanned DASD DeviceCount: count

The number of devices scanned by executingYKBTSCAN.

count

Number of scanned devices

YK7032I PRTRC=0

Hitachi storage systemsDevices Found: count

The number of Hitachi storage-system devices scannedby executing YKBTSCAN.

count

Number of scanned Hitachi storage-system devices

YK7033I PRTRC=4

The specified devices that donot have any available I/Opaths were skipped: count

As a result of a scan, information acquisition wasskipped for the devices on which no I/O paths wereavailable.

count

Number of devices for which informationacquisition was skipped

YK7099I PRT YKBTSCAN returncode=nnnn

YKBTSCAN terminated with the return code nnnn. This

message is always displayed to indicate the returncode.

nnnn

Maximum value among the output return codes

YK8001I CON BCM Monitor started. (v.r.m-nn)

BCM Monitor has started.

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 destinationis SYSTSPRT.

Messages 1-5





YK8007I PRTCON

time Synchronizationpercentage decreased, CopyGroup: cgid .

The copy progress percentage for the copy groupidentified by cgid is decreasing.

time

Message output time


cgid

Copy group ID

YK8008E CON BCM Monitor initializationfailed: termination-code.

An attempt to start BCM Monitor failed because of thereason indicated in a preceding message that wasoutput to either the console or dd SYSTSPRT.

Contact the center administrator. If you are the centeradministrator, take action that is appropriate to thepreviously output message, and then restart BCMMonitor.

termination-code (decimal number)

• 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 Manageragent.

• 44: An attempt to initialize the subtask failed.

YK8009E CON Task(task-ID) abended:completion-code.

The task terminated abnormally during startup of BCMMonitor. BCM Monitor will stop.

task-ID

Name for identifying the task

completion-code

System completion code

YK8010E CON Module not found: load-module-name.

The load module identified by load-module-namecannot be found. BCM Monitor will stop.

Check whether the load module has been properlyinstalled.

YK8011E CON The profile is not defined inthe facility class of RACF: xxxxxxxx .

The STGADMIN.YKA.BCM.YKQUERY profile or theSTGADMIN.YKA.BCM.COMMANDS profile is not defined in

the FACILITY class of RACF.

Review the RACF settings, and then restart BCMMonitor.

xxxxxxxx

1-6 Messages





Maintenance information

YK8012E CON The specified prefix is beingused by another program: prefix-name.

The specified prefix prefix-name is being used byanother program.

Review the YKMONCG file.

YK8013E CON BCM Monitor abended. BCM Monitor terminated abnormally.

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 toinvestigate the problem.

YK8014I CON MODIFY command accepted:command-name.

BCM Monitor accepted the MODIFY 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 Invalid command:command-name.

There is an error in the command-name command.

Make sure that the entered command is valid.

YK8018E CON Operand is incorrect:command-name.

There is an error in an operand of the command-namecommand.

Correct the operand, and then re-enter the command.

YK8019E CON The number of commands of execution waiting exceed theupper limit: command-name.

An attempt to execute the command identified bycommand-name failed because the number of commands waiting to be executed has reached theupper limit.

Wait until all the waiting commands are finishedexecuting, and then re-execute the command.

YK8020I CON nn: command-name[ parameter ].

Information is displayed for the command waiting to beexecuted.

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 wasentered.

parameter

Parameter specified in the waiting command

The full name of the parameter is displayed, evenif the abbreviated name of the parameter was

specified. If an omittable parameter was omitted,the default value is displayed.

YK8021I CON Execution waiting commandnone.

There is no command waiting to be executed.

YK8022I CON The state of sleep wasreleased.

BCM Monitor returned from the sleep state.

Messages 1-7





YK8023W CON The WAKEUP command wasnot executed because it isnot 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

• 20: EXEC processing failed.

• 20021: There was an error in the parameter listthat was passed to IRXJCL.

YK8026E CON IRXINIT module error:code=return-code,R0=abnormal-termination-code-and-reason-code-for-abnormal-termination,PARM7=reason-code.

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 mightoutput multiple messages reporting abnormal

termination. R0 includes the abnormal terminationcode and the reason code for abnormaltermination.

abnormal-termination-code-and-reason-code-for-abnormal-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 leadingbytes of R0. If the reason code for abnormal

termination is larger than two bytes, IRXINIT

returns only the two trailing bytes for the reasoncode for abnormal termination. For details on theabnormal 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





YK8027E CON IRXTERM module error:code=return-code,R0=abnormal-termination-code-and-reason-code-for-abnormal-termination.

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 twotrailing 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 abnormaltermination. For details about the abnormaltermination code and reason code, see MVSSystem Codes.

YK8028E CON BCM Monitor function abend:code=Sxxx Uxxxx

abended-module=module-name C-Date=module-creation-date

base=bbbbbbbb disp=dddd

[calling-module=module-name C-Date=y'y'.m'm'.d'd' base=bbbbbbbb disp=dddd ]

PSW= pppppppp ppppppppILC=ll INTC= xx

Registers at time of failureGR 00-03 contents-of-register-0 contents-of-register-1 contents-of-register-2 contents-of-register-3

GR 04-07 contents-of-register-4 contents-of-register-5 contents-of-register-6 contents-of-register-7

GR 08-11 contents-of-register-8 contents-of-

register-9 contents-of-register-10 contents-of-register-11


The main task or subtask terminated abnormally duringBCM Monitor processing. If the task cannot berecovered, BCM Monitor will stop.

Contact the center administrator.

Sxxx (hexadecimal number)

System completion code when the task terminatedabnormally

Uxxxx (decimal number)

User completion code when the task terminatedabnormally

module-name

Section name of the BCM Monitor module or loadmodule name.

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 moduleidentified by module-name

• y'y'/m'm'/d'd' : Creation date of the moduleidentified 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





pppppppp pppppppp

PSW during the abnormal termination

ll

Length of the command during the abnormaltermination

xx

Interrupt code during the abnormal termination

YK8031W CON The specified error-type isinvalid: command-name.

The value identified by error-type, which was specifiedin the command-name command, is invalid.

error-type

• 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.

YK8040I PRT

CON

time BCM Monitor will stop

at STOPPOINT 'label '.

BCM Monitor will stop at the point label .

time

Message output time


label

Label at which BCM Monitor stops

YK8041I PRTCON

time BCM Monitor will stopat the end of monitor cycle.

BCM Monitor will stop at the end of a cycle.

time

Message output time

This is only displayed when the output destination

is SYSTSPRT.

YK8042I PRTCON

time BCM Monitor will sleepat STOPPOINT 'label ' for max'sleep-time' minutes.

BCM Monitor will go to sleep at the point label .

Entering the WAKEUP command resumes copy group

monitoring before the duration identified by sleep-timehas elapsed.

time

Message output time


label

Label at which BCM Monitor goes to sleep

sleep-time

Sleep duration

YK8043I PRTCON

time STOPPOINT 'label 'reached.

BCM Monitor has reached the point label.

time

Message output time

1-10 Messages






YK8044I PRTCON

time BCM Monitor will sleepnow for max 'sleep-time'minutes.

BCM Monitor will sleep for the duration identified bysleep-time.


monitoring before the duration identified by sleep-time

has elapsed.time

Message output time


sleep-time

Sleep duration

YK8045I PRTCON

time BCM Monitor reachedthe end of the monitoringcycle.

BCM Monitor has reached the end of a cycle.

time

Message output time


YK8046I PRTCON

time Execute operatorcommand 'opcmd '.

BCM Monitor will execute the operator commandidentified by opcmd .

time

Message output time


YK8047I PRTCON

time Set MONITOR=statusfor Copy Group 'cgid '.

BCM Monitor set the monitoring status of the copygroup cgid to the status status.

time

Message output timeThis is only displayed when the output destinationis SYSTSPRT.

status

• START: The monitoring status of the copy group

was set to ACTIVE.

• STOP: The monitoring status of the copy group was

set to INACTIVE.

YK8048I PRTCON

time Set CYCLETIME to :cycletime.

BCM Monitor set CYCLETIME to the value identified by

cycletime.

time


YK8049I PRTCON

time Set WAITTIMEOUT to :timeout .

BCM Monitor set WAITTIMEOUT to the value identified by

timeout .

time

Messages 1-11





Message output time


YK8050I PRTCON

time Set MSGLEVEL to :MSGLEVEL=lvllog,lvlcons.

BCM Monitor set MSGLEVEL to the values identified by

lvllog and lvlcons.

time

Message output time


lvllog

Level of messages to be output to SYSTSPRT

lvlcons

Level of messages to be output to the console

YK8054I PRTCON

time BCM Monitor resumemonitoring.

BCM Monitor resumed processing.

time

Message output time


YK8055I PRTCON

time BCM Monitor will pausenow for 'sleep-time' minutes.

BCM Monitor will go to sleep because the PAUSE action

was executed.


monitoring before the sleep time of sleep-time haselapsed.

time

Message output time


sleep-time

Sleep duration

YK8056E PRTCON

time Failed to executeoperator command.

BCM Monitor failed to execute an operator command.

time

Message output time


YK8070E PRT time File Open error : dd-name.

The file dd-name could not be opened.

time

Message output time


dd-name

dd name of the file where the error occurred

YK8071E PRT time File Close error : dd-name.

The file dd-name could not be closed.

time

1-12 Messages





Message output time


dd-name


YK8073E PRT time A GETMAIN erroroccurred. return code=nnn. A GETMAIN error occurred. The program will stoprunning.

Contact Technical Support for assistance.

time

Message output time


nnn (decimal number)

Return code of the GETMAIN macro

YK8074E PRT time A FREEMAIN erroroccurred. return code=nnn.

A FREEMAIN error occurred. The program will stop

running.


time

Message output time



Return code of the FREEMAIN macro

YK8075E PRT time Parameter syntaxerror : file : rec#.

There is a syntax error in a parameter.

time

Message output time


file

Name of the file where the error occurred

rec#

Line number in the file file where the error wasdetected

YK8076E PRT time Invalid parameter wasspecified : file : rec#.

An invalid parameter was specified.

time

Message output time


is SYSTSPRT.file


rec#


Messages 1-13





YK8077E PRT time Invalid value wasspecified for paramparameter : file : rec#.

The parameter value param is invalid.

time

Message output time


fileName of the file where the error occurred

rec#


YK8078E PRT time A required parameter ismissing : file : param-name.

The required parameter param-name is not specified.

time

Message output time


file


param-name

Name of the required parameter

YK8079E PRT time CGID parameter mustbe specified first : rec#.

Specify the CGID parameter at the beginning of the

copy group parameters in the YKMONCG file.

time

Message output time


rec#

Line number where the error was detectedYK8080E PRT time Duplicate CGID

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

time

Message output time


cgid

CGID parameter value that is specified more than

once

YK8081E PRT time Combination of STATUS

and ACTION is invalid :rec#.

The combination of STATUS and ACTION specified in the

YKMONCG file is invalid.time

Message output time


rec#

1-14 Messages





Line number where the error was detected

YK8082E PRT time Combination of StartupStatus and NOCANCEL isinvalid : rec#.

The combination of NOCANCEL and the startup status

specified for the CGSTARTUPSTATUS parameter in the

YKMONCG file is invalid.

time

Message output time


rec#

Line number where the error was detected

YK8083E PRT time The correspondingCGID parameter is notdefined : cgid .

The copy group cgid specified in the ACTION parameter

of the YKMONCG file is not defined.

time

Message output time


cgid Copy group ID specified in the ACTION parameter

YK8084E PRT time The continuationsymbol can not be specifiedin the final record : file.

The continuation symbol was specified for the finalrecord.

time

Message output time


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


dd-name


YK8100I PRTCON

time sendmsg The message identified by sendmsg appears. Themessage is specified in SENDMSG with the CONS level

designated.

time

Message output time


Messages 1-15





YK8200I PRTCON

time sendmsg The message identified by sendmsg appears. Themessage is specified in SENDMSG with the ERROR level

designated.

time

Message output time


YK8220E PRTCON

time cmd error for CopyGroup 'cgid '

time return code rc receivedfrom cmd

time COMMAND : 'cmd- parm'

time MSG:

time ['err-msg'].

An error occurred during execution of the cmd command for the copy group identified by cgid .

time

Message output time


cmd-parm

Executed CLI command

rc

Return code from the CLI commanderr-msg

Message included in the message structure for theCLI command

The number of lines equal to the number of messages included in the message structure aredisplayed.

YK8221I PRTCON

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


timeout

Timeout value

YK8222E PRTCON

time YKEWAIT (RC=8) :Unexpected status reached.

An unexpected group status was reached duringexecution of the YKEWAIT command.

time

Message output time


YK8223W PRT

CON

time cmd (RC=4) : Some

volumes with invalid statusfound.

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


1-16 Messages





YK8230E PRTCON

time REPORT type is onlyvalid for TCA or UR CopyGroups.

type, which was specified for the REPORT parameter, is

only valid for TrueCopy Asynchronous or UniversalReplicator copy groups.

time

Message output time


type

Report type

YK8231E PRTCON

time BCM Monitor can notadjust Copy Group status.

BCM Monitor could not set the copy group to thespecified startup status.

time

Message output time


YK8300I PRT

CON

time sendmsg The message identified by sendmsg appears. The

message is specified in SENDMSG with the STATUS leveldesignated.

time

Message output time


YK8301I PRTCON

time Not all volumes are in'status'. action requested.

The action identified by action will be executed becausethere is a volume that is not in the status identified bystatus.

time

Message output time


YK8302I PRTCON

time Trying to cmd CopyGroup 'cgid '.

The CLI command identified by cmd will be executedfor the copy group identified by cgid .

time

Message output time


YK8303I PRTCON

time Waiting for status'status'.

BCM Monitor will wait until the copy group beingmonitored enters the status identified by status.

time


YK8304I PRTCON

time Copy Group is in'status' status. Wait untilstatus has changed.

BCM Monitor will wait until the copy group statusidentified by status changes to another status.

time

Messages 1-17





Message output time


YK8305I PRTCON

time Status ok. The copy group entered the expected status.

time


YK8310I See YK8310I PRT on page1-161.

N/A

YK8311I CON REPORT SUMMARY:

COPY GROUP : cgid TYPE :cgtype

DAD-ID : dad PREFIX : prefix

SIMPLEX : simplexct PENDING : pendingct DUPLEX : duplexct SUSPEND : suspendallct OTHER : otherct

GROUP STATUS : statusMATCHING% : matchREVERSED% : rev%

ATTIME(GMT) : attime -STATUS : attms

This message indicates the results of REPORT(SUMMARY).

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 issecondary-to-primary

attime

ATTIME suspend time

attms

ATTIME suspend status

1-18 Messages


N/A

YK8313I CON REPORT DETAIL:



VOLSER PDEVN DIR SDEVNSTATUS MATCH% C/TSUBC/T DELTA CTTIME

volser pdevn dir sdevnstatus match ctid sub-ctid ctdelta cttime

This message indicates the results of REPORT(DETAIL).

cgid

Copy group ID

cgtype

Copy group type

dad


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


N/A

YK8315I CON REPORT RPO:

COPY GROUP : cgid

C/T SUBC/T PSN SSN DELTACTTIME

ctid sub-ctid psn ssn ctdeltacttime

This message indicates the results of REPORT(RPO).

cgid

Copy group ID

ctid

Consistency group ID or master journal group ID

sub-ctid


Messages 1-19




psn

Serial number of the primary storage system

ssn

Serial number of the secondary storage system

ctdelta

Consistency delta valuecttime

Consistency time


N/A

YK8317I CON REPORT STATS:



C/T PSN SSN SFT PRSFTOT

PRSFC/T PWPRTOT SRSFTOTSRSFC/T SWPRTOT TRANSOFLD RCUR CPND

ctid psn ssn sidefile-threshold p-rsf-all p-rsf-ct p-wpr-all s-rsf-all s-rsf-ct s-wpr-all mcu-to-rcu-kbpsoffload-timer rcu-ready-timer copy-pending-timer

This message indicates the results of REPORT(STATS)

for the TrueCopy Asynchronous copy group.

cgid

Copy group ID

cgtype

Copy group type

dad


prefix

Prefix

ctid

Consistency group ID

psn


ssn

Serial number of the secondary storage system

sidefile-threshold

Sidefile threshold value

p-rsf-all

Primary reserve sidefile cache-usage rate

p-rsf-ct

Primary reserve sidefile consistency cache-usagerate

p-wpr-all

Primary write pending rate

s-rsf-all

Secondary reserve sidefile cache-usage rate

s-rsf-ct

Secondary reserve sidefile consistency cache-usage rate

s-wpr-all

Secondary write pending rate

mcu-to-rcu-kbps

1-20 Messages





Data transfer rate (Kbps) between the maincontrol unit and the remote control unit

offload-timer

Offloading timer

rcu-ready-timer

Remote control unit ready timer

copy-pending-timer

Copy pending timer


N/A

YK8319I CON REPORT STATS:



C/T SUBC/T PSN SSN TRANSPJMET% PJDAT% SJMET%SJDAT% PJDATA SJDATA

ctid sub-ctid psn ssn mcu-to-rcu-kbps p-jnl-meta p-jnl-data s-jnl-meta s-jnl-data p- jnl-data-capacity s-jnl-data-capacity

This message indicates the results of REPORT(STATS)

for the Universal Replicator copy group.

cgid

Copy group ID

cgtype

Copy group type

dad


prefix

Prefix

ctid

Master journal group ID

sub-ctid


psn


ssnSerial number of the secondary storage system

mcu-to-rcu-kbps

Data transfer rate (Kbps) between the maincontrol 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





YK8320I PRTCON

time Copy Group 'cgid ' hasreached target status'status'.

The copy group identified by cgid has switched to thetarget status identified by status.

time

Message output time


YK8321I PRTCON

time Some volumes are in a'TRANSITION' status.

Some volumes are in the TRANSITION status.

time

Message output time


YK8322I PRTCON

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 PRTCON

time Some volumes are notin a 'HOLDER' status.

Some volumes are not in the HOLDER status.

time

Message output time


YK8324I PRTCON

time All volumes are in'HOLDER' status.

All volumes are in the HOLDER status.

time

Message output time


is SYSTSPRT.

YK8325I PRTCON

time Copy Group 'cgid ' is'status' now.

The copy group identified by cgid entered the statusidentified by status.

time

Message output time


YK8326I PRTCON

time Copy Group 'cgid ' willbe suspended at: atparm.

The copy group identified by cgid is set to suspend atthe time indicated by atparm.

time

Message output time


atparm

ATTIME suspend time

1-22 Messages





YK8400I PRTCON

time sendmsg The message identified by sendmsg appears. Themessage is specified in SENDMSG with the INFO level

designated.

time

Message output time


YK8401I PRTCON

time Check Startup Status of Copy Group 'cgid ':

BCM Monitor will start checking the status of the copygroup identified by cgid .

time

Message output time


YK8402I PRTCON

time Startup Status check of Copy Group 'cgid ' finished.

The status check of the copy group identified by cgid iscomplete.

time


YK8403I PRTCON

time Start monitoring CopyGroup.

BCM Monitor will start monitoring the copy group.

time

Message output time


YK8404I PRTCON

time Execute action 'actionerr-action'

BCM Monitor will execute the action identified by actionerr-action specified in the ACTION parameter for

STATUS.

timeMessage output time


action

Action to be executed

err-action

Error action to be executed

YK8405I PRTCON

time The return code of theaction is RC=rc .

Error rc occurred for a Business Continuity Manager CLIcommand executed by an action.

time

Message output time


rc

Return code of the Business Continuity ManagerCLI command executed by the action

Messages 1-23





YK8406I PRTCON

time Execute error action'err-action'.

BCM Monitor will execute the error action identified byerr-action.

time

Message output time


err-action


YK8410I PRTCON

time ---- date ---- The date is displayed when BCM Monitor is started orwhen the date changes while BCM Monitor is running.

time

Message output time


date

New date

For example, Thursday, 21 Jan 2010 is displayed.


N/A

YK8412I CON SYSTEM OPTIONS:

CYCLE TIME : cycletimeWAITFOR TIMEOUT :timeout MSGLEVEL :lvllog,lvlconsONACTIONERROR : err-action

STOP AT STOPPOINT :stoppt SLEEP AT

STOPPOINT : sleeppt

This message indicates the values specified in theYKMONOPT file.

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


N/A

YK8414I CON COPY GROUP DEFINITIONS:

ID : cgid PREFIX : prefix

DAD-ID : dad ROUTE LIST :route[,route-label ]

MONITOR STATUS :cgmonstat STARTUP

This message indicates the values specified in theYKMONCG file. This message appears a number of times, equal to the number of copy groups specified.

cgid

Copy group ID

prefix

1-24 Messages





STATUS :cgsastat ,cgsaact ,cgsaopt

WHEN STATUS status DOACTION '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 whenBCM Monitor starts

cgsaact

Startup action executed if the copy pair status forstarting BCM Monitor is different from the specifiedstartup status

cgsaopt

Option information of the CGSTARTUPSTATUS

parameter

status action err-action

Status, action, and error action for the copy groupspecified in STATUS and ACTION

These parameters appear a specified number of times.

YK9001I ISPF The license key(s) has beeninstalled

The license key was installed.

YK9051E ISPF An error occurred in thelicense information dataset

An error occurred with the license information dataset.

Check that the prefix of the license information datasetis registered correctly, and that the license informationdataset is created correctly. If necessary, recreate thelicense information dataset and re-register the licensekeys in the order in which they were issued.

For details about registering a prefix name of thelicense information dataset, see the Hitachi BusinessContinuity Manager Reference Guide.

YK9052E ISPF An error occurred in thelicense key dataset

An error occurred with the license key dataset.

Check that the dataset name of the license key datasetis correct, and that the license key dataset is createdcorrectly. If necessary, transfer the license key file

again and recreate the license key dataset.

YK9071W ISPF A license key was not found An attempt was made to install a license key, but noinstallable license key was found in the license keydataset.

Make sure that none of the following conditions exist:

• The license key you attempted to install wasalready installed.

Messages 1-25





• The license key you attempted to install was notfor this product.

• The dataset you specified was not a license keydataset.

YK9072W ISPF The license key could not beinstalled.

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 wasalready installed.

• The license key you attempted to install was notfor this product.

YK9080E CON The expiration date for yourlicense key (function).

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 ContinuityManager Basic is required.

If function is UR 4x4 Extended CTG:

A permanent license for Business ContinuityManager UR 4x4 Extended CTG is required.

YK9081W CON Your function license willexpire in n day(s).

The license (function) will expire in n days.





A permanent license for Business Continuity

Manager UR 4x4 Extended CTG is required.

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


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() parameterrequired 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) requestin the YKA098I message.

YKA003E TSO OP(OPEN|GET|CLOSE)option required

The OP parameter is missing.

Specify the OP parameter.

YKA004E TSO Buffer full; messagesdiscarded

An attempt to acquire the IEA494I console message,

IOSHM0414I console message, or the message specified

1-26 Messages





in the MSGID parameter of the YKCONMSG command

failed. This problem might occur when consolemessage 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() parametercannot be specified for thisoperation

If GET or CLOSE is specified in the OP parameter, you

cannot specify the TIMEOUT parameter.

Specify OPEN in the OP parameter, and then specify the

TIMEOUT parameter.

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

YKA010E TSO MSGID() parameter cannotbe specified for thisoperation

If GET or CLOSE is specified in the OP parameter, you

cannot specify the MSGID parameter.

Specify OPEN in the OP parameter, and then specify the

MSGID parameter.

YKA096I TSO No message found 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 receivemessages.

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) parameterspecified 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





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 pairwas detected within the range of the specifieddevice numbers.

- A copy group definition file was created, butvolume information not defined in the diskconfiguration definition file for the site specified inthe DAD parameter was detected among copy pairs

within the range specified in the DEVN parameter.

- A copy group definition file was created, but achange was detected in the I/O configuration whenthe 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 wascreated for the volume that was successfullydetected.

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 pairthat 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: parameter-name

The parameter specification was invalid or missing.

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 requiredparameter indicated by parameter-name is valid.

• Make sure that different device address domainIDs for the primary and secondary sites arespecified for the DAD parameter.

parameter-name

Name of the invalid or missing parameter

YKB101E TSO The specified PREFIX isbeing used by anotherprogram.

The specified prefix is being used by another program.

Check the value specified for the prefix.

YKB102E TSO Error occurred duringexecution. Cmd=command-name

An error occurred during execution of the YKP2B

command.

See the explanation corresponding to the message IDof the error message indicated by message-text andtake appropriate action. Also see the additional

1-28 Messages





msg=message-text :message-value: message-severity

information indicated by message-value and message-severity and take appropriate action. If the problem isnot resolved, contact your Hitachi Data Systemsrepresentative 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 isdisplayed.

message-severity



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 acquiredfor DEVN=device-number

No copy pair information was acquired from the volumeto which the device number device-number wasassigned.

There might not be a volume for the specified devicenumber. If the volume exists for the specified devicenumber, check the channel settings.

device-number

Device number assigned to the volume from whichno copy pair information was acquired

YKB201W TSO No I/O paths are available

for the specified devices.DEVN=Devn

No copy pair information was acquired from the volume

to which the device number Devn was assignedbecause no I/O paths are available.

Verify the I/O path settings.

Devn

The device number of the volume on whichinformation acquisition was skipped

YKB202W TSO Unable to resolve primaryvolume information.Pair=CopyType,DEVN=Devn,SN=SerialNum,CU=CU#,CCA=CCA#

A P-VOL not defined in the disk configuration definitionfile was included among the PPRC copy pairs detectedby the YKP2B command.

Check whether this P-VOL is defined in the diskconfiguration definition file.

CopyType

The copy type of the detected undefined volume

Devn

The device number of the detected undefinedvolume

SerialNum

Messages 1-29





The serial number of storage system of thedetected undefined volume

CU#

The control unit number of the detected undefinedvolume

CCA#

The command control address number of thedetected undefined volume

YKB203W TSO Unable to resolve secondaryvolume information.Pair=CopyType,SN=SerialNum,CU=CU#,CCA=CCA#

An S-VOL not defined in the disk configurationdefinition file was included among the PPRC copy pairsdetected by the YKP2B command.

Check whether this S-VOL is defined in the diskconfiguration definition file.

CopyType

The copy type of the detected undefined volume

SerialNum

The storage system serial number of the detected

undefined volumeCU#


CCA#


YKB204W TSO A dynamic configurationchange was detected.DEVN=device-number

A dynamic change was detected in an I/O configurationdefinition 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 thecommand.

device-number

Device number being processed when a dynamicchange was detected in an I/O configurationdefinition

Table 1-3 List of messages (message ID YKC0x)


YKC000T TSO

RC=48

Supplied parameters invalid Invalid parameters are specified.

For details, see the reason code in the YKC099I

message displayed after this message. For reasoncodes, see IKJPARS in the TSO/E ProgrammingServices.

YKC001E MSGSC=48 RC=48

No controller ARRAYS()supplied

Nothing is assigned to the ARRAYS parameter.

1-30 Messages





YKC001E TSORC=48

No message MSG() supplied Nothing is assigned to the MSG parameter.


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.


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 TSORC=48

Messages MSG(stem) doesnot include trailing "."

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

stem

Stem name assigned to the MSG parameter


Results STEM(stem) doesnot include trailing "."

The last character of the STEM parameter is not a

period.

stemStem name assigned to the STEM parameter


Ending TO() not valid hex The value specified in the TO parameter is not in

hexadecimal format.

YKC008E MSGSC=48

Starting FROMVSN() valueinvalid

The value specified in the FROMVSN parameter is invalid.

YKC008E MSGSC=48

Ending TOVSN() valueinvalid

The value specified in the TOVSN parameter is invalid.


Starting FROM() not validhex

The value specified in the FROM parameter is not in

hexadecimal format.

YKC009E MSGSC=48 RC=48 Specify DEV# and VOLSERparm exclusively You cannot specify a device number and a volumeserial number at the same time.


Starting FROM() exceedsending TO()

The value specified in the FROM parameter exceeds the

value of the TO parameter.


Starting FROMVSN() exceedsending TOVSN()

The value specified in the FROMVSN parameter exceeds

the value of the TOVSN parameter.

YKC010E TSORC=40

REXX failure returncode=nnnn starting withvariable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in theTSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKC031I MSGSC=0 (count )

Scanned DASD Device Count The number of DASD devices scanned by the YKSCAN

command.

count

Number of scanned DASD devices


Hitachi storage systemsDevices Found

The number of Hitachi storage-system devices scannedby the YKSCAN command.

Messages 1-31





count

Number of Hitachi storage-system devices


The specified devices that donot have any available I/Opaths were skipped.

As a result of the device scan, information acquisitionon devices for which no I/O path is available wasskipped.

count

The number of devices skipped when the deviceinformation was acquired


A dynamic configurationchange was detected duringYKSCAN commandprocessing.

A dynamic change to an I/O configuration definitionwas detected during processing of the YKSCAN

command. This error may be due to the volume serialnumber in the acquired volume information differingfrom that in the actual configuration.

Check the disk configuration definition file after thescan is complete. If the volume serial number isdifferent from the one in the actual configuration, re-execute the scan.

YKC099I TSO YKSCAN command return

code=nnnn, reasoncode=rrrr

The YKSCAN command terminated with the return code

nnnn and the reason code rrrr .

This message is always displayed to indicate the returncode and the reason code.

nnnn

Maximum among the severity codes returnedduring command execution

Table 1-4 List of messages (message ID YKD0x)


YKD000T TSORC=48


For details, see the reason code in the YKD099I

message that will appear after this message. Forreason codes, see IKJPARS in the TSO/E ProgrammingServices.

YKD001E TSORC=48


YKD001E MSGSC=48 RC=48



Copy Group STEM(stem)does not include trailing "."


period.

stem

Stem name assigned to the STEM parameter

YKD002E MSGSC=48

DEVN() value invalid The value assigned to the DEVN parameter is invalid.

YKD002E TSORC=48



stem

1-32 Messages






YKD008E MSGSC=48

DEVN() not valid hex The value specified in the DEVN parameter is not in

hexadecimal format.

YKD010E TSORC=40



For details about the return code, see IKJCT441 in the

TSO/E Programming Services.nnnn


YKD050E MSGSC=36 RC=48(attribute-value)

Invalid Copy Group attributename

The specified copy group attribute value is invalid forthis command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value


Some pairs in this group donot support TCA services.

One or more devices in the 7700E storage system doesnot support TrueCopy Asynchronous copy groups.

Check that the command can be executed on this copygroup, and then re-execute the command.

YKD099I TSO YKDELETE command returncode=nnnn, reasoncode=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)


YKE000T TSORC=48


For details, see the reason code in the YKE099I


YKE001E MSGSC=48 RC=48

GOTO() not supplied Nothing is assigned to the GOTO parameter.

YKE001E TSO

RC=48





TIMEOUT() not supplied Nothing is assigned to the TIMEOUT parameter.

Messages 1-33





YKE001W MSGSC=4 RC=4

Timeout limit has expired,waiting for group copy-groupto reach state state.

Processing is terminating because the timeout limit hasexpired.

Correct the timeout value or check that the status tobe monitored is correctly specified. Use the YKQUERY

command to check the status of the copy pairs. If thereis a copy pair where a transition has not taken place,

the S-VOL of that copy pair might be ONLINE. Make itOFFLINE and re-execute.

copy-group

Copy group ID

state

Status to be monitored




period.

stem


YKE002E MSG

SC=48


YKE002E TSORC=48



stem



TIMEOUT() value invalid The value assigned to the TIMEOUT parameter is

invalid.


GOTO value 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.

YKE003E MSG

SC=8 RC=8

Unexpected transition of

group copy-group pair index to state state.

The copy pair in the copy group entered an unexpected

status.

Check that the status to be monitored is correctlyspecified.

copy-group

Copy group ID

index

Pair index

Before version 2.0: Copy pair number

Version 2.0 or later: Copy group number and copypair number

For details about identifying a volume with the

copy group number and the copy pair number, seeIdentifying the volume to be processed on page1-166

state

The status after the transition

1-34 Messages





YKE008E MSGSC=48


hexadecimal format.

YKE010E TSORC=40




nnnnError code returned upon REXX access

YKE099I TSO YKEWAIT command returncode=nnnn, reasoncode=rrrr

The YKEWAIT command terminated with the return code



nnnn


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


YKF000T TSORC=48


For details, see the reason code in the YKF099I


YKF001E TSORC=48


YKF001E MSGSC=48 RC=48




The last character of the STEM parameter is not aperiod.

stem


YKF002E TSORC=48



stem




invalid.

YKF010E TSO

RC=40

REXX failure return

code=nnnn starting withvariable name



nnnn


Messages 1-35





YKF050E MSGSC=48 RC=48(attribute-value)




name

REXX variable name

attribute-valueREXX variable value

YKF099I TSO YKFREEZE command returncode=nnnn, reasoncode=rrrr

The YKFREEZE command terminated with the return



nnnn


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


YKG000T TSOSC=48

Supplied parameters invalid. Invalid parameters have been specified.

YKG001E TSORC=48

Unable to execute withoutvalid MSG() parameter.

Specify a valid MSG parameter.

YKG002E TSORC=48

MSG(stem) does not includetrailing "." character.


stem


YKG003E TSO

RC=52

Unable to update MSG(stem)

in Caller's environment.YKVSET result = result

An attempt to assign a value to a Message structure

variable failed. The resulting value is displayed inresult . This error can be caused by an invalid valuebeing specified for the MSG parameter.

stem


YKG004E MSGSC=48 RC=48

Unable to execute withoutvalid STEM() parameter.

Specify a valid STEM parameter.


STEM(stem) does notinclude trailing "." character.


period.

stem



Unable to execute withoutvalid PREFIX() parameter.

Nothing or an invalid value is assigned to the PREFIX

parameter.

To correct the error, see the CLI command descriptionsin the Hitachi Business Continuity Manager ReferenceGuide, and then re-execute the command.

1-36 Messages






Unable to execute withoutvalid SN() parameter.

An invalid value is assigned to the internal parameterSN that indicates the storage system serial number

contained in the disk configuration definition file name.

Check the disk configuration definition file name.

YKG050W MSGSC=4 RC=4

(file:rec#)

Unrecognized elementencountered: name

The system does not recognize the XML element namethat 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 inthe XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error wasdetected

rec#

Number of the line in the file identified by filewhere the error was detected

YKG051E MSGSC=36 RC=36(file:rec#)

End of file encountered incomment. XML input analysis detected a syntax error on the linewith the line number identified by rec# in the fileidentified by file.


file


rec#


YKG053W MSGSC=4 RC=4(file:rec#)

Unrecognized Versionattribute value: value

The system does not recognize the version attributevalue of the XML element that exists on the line withthe line number identified by rec# in the file identifiedby file.


file


rec#



Unexpected termination of element: name

The XML element name that exists on the line with theline number identified by rec# in the file identified byfile has not been correctly created.

Messages 1-37






file


rec#



Invalid "&" characterdiscovered in quoted string.string

The & character string that exists on the line with theline number identified by rec# in the file identified byfile has not been correctly escaped.

See the description of Extensible Markup Language(XML) 1.0 at http://www.w3.org.

file


rec#



Unrecognized Encodingattribute value: value

The system does not recognize the encoding attributevalue of the XML element that exists on the line withthe line number identified by rec# in the file identifiedby file.


file


rec#



Unrecognized attribute:name = value

The system does not recognize the XML attribute thatexists on the line with the line number identified byrec# in the file identified by file.


name

XML attribute name

value

XML attribute value

file

1-38 Messages






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 theline number identified by rec# in the file identified byfile.


file


rec#

Number of the line in the file identified by file

where the error was detectedv .r .m

API level

For details about this value, see the informationabout the XML document type definitions in theHitachi Business Continuity Manager ReferenceGuide.

YKG079E MSGSC=44 RC=44(result )

YKVSET program failure for:name = value

An attempt to assign the value value to the variablename failed with the result value identified by result .This error can be caused by an invalid value beingspecified for the STEM parameter.


Unable to read configurationfile.

The configuration file could not be read, because therecord length is too long.

file

Name of the configuration file where the erroroccurred

rec#

Number of the line in the file file where the errorwas detected

YKG088E MSGSC=40 RC=40(file)

File Open error: dsstate. An attempt to open the configuration file identified byfile failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the errorwas detected


File Close error: dsstate. An attempt to close the configuration file identified byfile failed.

dsstate

Messages 1-39






file



(file)

File Allocation Failed:dsstate.

An attempt to allocate the configuration file identifiedby file failed.

dsstate


file



File Deallocation Failed:dsstate.

An attempt to deallocate the configuration fileidentified by file failed.

dsstate


file



File Read error: dsstate. An attempt to read the configuration file identified byfile failed.

dsstate


file


YKG099I MSGTSO

YKGETHDA command returncode=max-value,reasoncode=reason-code.

The reading of the disk configuration definition file hasfinished.

This message is issued when an invalid diskconfiguration definition file is read in ISPF. If thismessage cannot be output to the REXX structure, it isoutput 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)



Unable to execute withoutvalid name parameter.

Nothing or an invalid value is assigned to theparameter identified by name.

YKG202E TSORC=48

"SYSAUTH". cannot bespecified in MSG()parameter.

SYSAUTH. cannot be specified in the MSG parameter.

Specify a different name.

1-40 Messages






"SYSAUTH." cannot bespecified in STEM()parameter.

SYSAUTH. cannot be specified for the STEM parameter.


YKG204E TSORC=48

name parameter is too long. The parameter identified by name is too long.

YKG205E MSGSC=48 RC=48 name parameter is too long. The parameter identified by name is too long.


The attribute attname isalready defined.

The XML attribute identified by attname has alreadybeen defined.

Review the file name identified by file and the attnamevalue on the line with the line number identified byrec#.

attname

XML attribute name

file


rec#



The value value of theattribute name is an invalidformat.

The value value of the XML attribute name is in aninvalid format.

Correct the specification on the line with the linenumber identified by rec# in the file identified by file.

file


rec#



name attribute missing. The required XML attribute name is missing.


file


rec#



The attribute statements areinvalid.

The XML attribute description is invalid.


file


Messages 1-41





rec#



This kind of elementselement can't be definedmore than once.

The XML element element cannot be defined more thanonce.

Correct the specification on the line with the line

number identified by rec# in the file identified by file.

file


rec#



The value value of attributename is not match withfilename.

The value value of the XML attribute name does notmatch the name in the file name.


fileName of the configuration file where the error wasdetected

rec#



The element name-1, forwhich the value value wasspecified for the attributename-2, was not found.

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

Revise the specification on line number rec# in file.

file

Name of the configuration file in which the error

was detectedrec#

Number of the line in file where the error wasdetected


The element name isrequired, but no elementwas found.

The required XML element name is missing.


file


rec#



The element statements areinvalid.

The XML element description is invalid.


file

1-42 Messages






rec#


YKG274E MSG

SC=36 RC=36(file:rec#)

ETag name is mismatch. /

correct-ETag-name isexpected, but /incorrect-ETag-name is specified.

The specified ETag name /incorrect-ETag-name is not

the expected ETag name /correct-ETag-name.


file


rec#


YKG275W MSGSC=4 RC=4

(file:rec#)

Extra ETag is specified:ETag-name

An extra ETag-name is specified.


number identified by rec# in the file identified by file.file


rec#



The element name1 is not acontent of the elementname2.

The XML element identified by name2 contained theXML element name1 that cannot be specified.



rec#



name element missing. The XML element name is missing.


file


rec#



Serial Number HDASN isrequired, but Serial NumberDDSN is found.

The disk device element's SerialNum must be the sameas the SerialNum value (HDASN ) of the disk

Messages 1-43





configuration element, but DDSN is defined for thisvalue.


file

Name of the configuration file where the error was

detectedrec#



Specify the local DADID of the primary site for theDAD() parameter.

A device address domain ID created by a Remote Scanor NG Scan is specified.

Specify the local device address domain ID of theprimary site in the DAD parameter. For details about the

NG Scan, see the Hitachi Business Continuity Manager User Guide.

file


rec#

Number of the line where the error was detected inthe file identified by file

YKG290E MSGSC=44 RC=44(result )

YKVGET program failure for:vn

An attempt to acquire the variable vn failed with theresult value identified by result . This error can becaused by an invalid value being specified for the STEM

parameter.


The element stack wasoverflowed.

The internal routine encountered a shortage of workspace.


file


rec#


YKG298E MSGTSO SC=44RC=44 (detailed-info)

YKGETHDA encountered anunexpected error.

An unexpected error has occurred.

This error might have occurred with another error.

If another error message was output at the same timeas this one, follow the instructions in that message tofix the corresponding problem.

If no other error message was output, collect thefollowing materials and contact your Hitachi DataSystems representative or authorized service provider:

• The script from which this command was executed(not necessary if this command was executed fromthe ISPF panel).

1-44 Messages





• The ISPF log (not necessary if this command wasexecuted from a script).

• The definition files operated on from the script orISPF panel (the copy group definition file, diskconfiguration definition file, command devicedefinition file and route list definition file).

detailed-info

Information displayed to assist the Hitachi DataSystems representative or authorized serviceprovider 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 specifieddevice numbers.

- A copy group definition file was created, butvolume information not defined in the diskconfiguration definition file for the site specified inthe DAD parameter was detected among copy pairs

within the range specified in the DEVN parameter.

- A copy group definition file was created, but achange was detected in the I/O configuration whenthe YKH2B command was executed without

specifying the HS parameter or the YKH2B

command was executed by specifying HS(CHECK).

- A copy group definition file was created, but a

storage system that does not support 2DCconfiguration with HyperSwap and UniversalReplicator was detected.

8: An I/O error occurred with a volume within the

scan range. Copy group definition files werecreated for the volumes that were successfullydetected.

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 pairthat 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





specifying HS(CHECK) while HyperSwap is disabled,

copy pairs cannot be detected.

YKH100E TSO Missing or invalid parameter: parameter-name

Check the following, and then re-execute thecommand:

• Make sure that the required parameter indicatedby parameter-name was specified.

• Make sure that the value specified for the requiredparameter indicated by parameter-name is valid.

parameter-name

Name of the invalid or missing parameter

YKH101E TSO The specified PREFIX isbeing used by anotherprogram.



YKH102E TSO Error occurred duringexecution. Cmd=info

msg=message-text :message-value: message-

severity

An error occurred during execution of the YKH2B

command.

See the explanation corresponding to the message IDof the error message indicated by message-text and

take appropriate action. Also see the additionalinformation indicated by message-value and message-severity and take appropriate action. If the problem isnot resolved, contact your Hitachi Data Systemsrepresentative or authorized service provider.

info


message-text

Error message

message-value


If no additional information is available, a space is

displayed.

message-severity



The error messages message-text , message-value, andmessage-severity are displayed on the TSO/E terminal.Depending on the length of the error messages, theymight extend over several lines.

YKH200W TSO No information was acquiredfor DEVN=Devn

No copy pair information was acquired from the volumewith the device number indicated by Devn. There mightnot 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 whichno copy pair information was acquired

1-46 Messages





YKH201W TSO No I/O paths are availablefor the specified devices.DEVN=Devn

No copy pair information was acquired from the volumeto which the device number Devn was assignedbecause 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 Unable to resolve primaryvolume information.DEVN=Devn,SN=SerialNum,CU=CU#,CCA=CCA#

A P-VOL not defined in the disk configuration definitionfile was included among the PPRC copy pairs detectedby the YKH2B command.

Check whether this P-VOL is defined in the diskconfiguration definition file.

Devn

The device number of the detected undefinedvolume

SerialNum

The storage system serial number of the detected

undefined volumeCU#


CCA#


YKH203W TSO Unable to resolve secondaryvolume information.SN=SerialNum,CU=CU#,CCA=CCA#

An S-VOL not defined in the disk configurationdefinition file was included among the PPRC copy pairsdetected by the YKH2B command.

Check whether the detected S-VOL is defined in thedisk configuration definition file.

SerialNum

The storage system serial number of the detectedundefined volume

CU#


CCA#


YKH204W TSO A dynamic configurationchange was detected.

DEVN=device-number

A dynamic change was detected in an I/O configurationdefinition 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 orexecution conditions (such as the parameter setting orthe times at which the command has been executed),and then re-execute the command.

device-number

Messages 1-47





Device number being processed when a dynamicchange was detected in an I/O configurationdefinition

YKH205W TSO This copygroup does notsupport LinkageOption=HS.SUPFNC=SUPFnc

TrueCopy with the HyperSwap attribute cannot be usedin this storage system because 2DC configuration withHyperSwap and Universal Replicator is not supported.

Use a device#

in which 2DC configuration withHyperSwap and Universal Replicator can be used. Also,if scanning was not performed after the storage systemmicrocode was updated, perform a scan.

SUPFnc (hexadecimal number)

Value for the version (minimum value) of thestorage system support function used in the copygroup

#: The storage systems for which 2DC configurationswith HyperSwap and Universal Replicator can be usedare USP Vs with a storage system support functionversion of X'22' or later.

YKJ000E TSORC=48



name

Parameter name

YKJ001E TSORC=48


name

Parameter name

YKJ002E TSORC=48

The specified PREFIX isbeing used by anotherprogram.



YKJ051E TSO

RC=32

Error occurred during

execution. Cmd= infomsg= message-text :message-value: message-severity

An error occurred during execution of the YKIMPORT

command or YKEXPORT command.See the error message message-text and resolve theproblem. Also see the additional information indicatedby message-value and message-severity and takeappropriate action.

If the acquisition of information denoted by message-text , message-value, or message-severity fails, FATAL

is displayed instead of the information that should beacquired. The reasons for FATAL to be displayed include

an insufficient region size. Review the current regionsize, and then retry executing the command.

If the problem is not resolved, contact TechnicalSupport for assistance.

info


message-text

Error message

message-value


1-48 Messages






message-severity



The error messages message-text , message-value, andmessage-severity are displayed on the TSO/E terminal.Depending on the length of the error messages, theymight extend over several lines.

YKJ099I TSORC=0

cmd command completed.RC= return-code

The command identified by cmd has ended with areturn code identified by return-code.

cmd

Command name

YKJ100E TSORC=32

Error occurred duringreading/writing configurationfile: file

An error occurred while reading data from or writingdata to the configuration file.

file


YKJ101I TSORC=4

No copy pair is defined inspecified Copy Groupdefinition: file

No copy pair is defined for the specified copy group. Nodata was written in the CSV file.

file

Name of the specified copy group definition file

YKJ102E TSORC=32

name is not specified inCopy Group definitionspecified by BASEGROUP.

The copy group definition file specified by theBASEGROUP parameter does not include the element

identified by name.

Set the necessary elements in the copy group definitionfile that is to be used as the base, and then retry.

nameName of an element in the copy group definitionfile

YKJ150E TSORC=40

Error reported during fileinput/output. EXECIO RC=n: dd-name

Processing ended due to the EXECIO TSO/E REXX

command failure (return code = n). For details, see theTSO/E REXX User's Guide.

The probable causes are as follows:

• No CSV file is assigned to the dd name required forthe command.

• The dataset format of the CSV file is notsupported.

dd-name

dd name of the CSV file where the error wasdetected

YKJ151E TSORC=40

File format is invalid:DSORG= XX . DSORG mustbe PS: dd-name

The dataset format of the CSV file identified by dd-name is invalid.

Delete the current CSV file and create a CSV file that isin the correct dataset format.

Messages 1-49





For details about the CSV file dataset format, see theHitachi Business Continuity Manager Reference Guide.

XX

DSORG of the CSV file where the error wasdetected

dd-name


YKJ152E TSORC=40

Failed to operate csv file:dd-name: dsstate

The CSV file operation will stop because an erroroccurred when using the CSV file.

Refer to the information output in the message toreview the environment, and then update the CSV fileagain. For details about troubleshooting, see theaccompanying message and the Hitachi BusinessContinuity Manager User Guide.

dd-name


dsstate

CSV file status

• EXTENT= extent

The number of extents of the dataset that iscurrently allocated

extent indicates the number of extents that areallocated to the dataset indicated by dd-name.

• CANNOT GET DSSTATE, reason code= nnnn

The dataset information cannot be obtained, or theCSV file is not allocated.

nnnn (decimal (base 10) number) indicates a

reason code (maintenance information).

YKJ200E TSORC=32

name is not specified in Pairinformation CSV file: dd-name: rec#

The item identified by name is not included in the pairinformation CSV file.

name

Name of the item in the pair information CSV file

dd-name


rec#

Number of the line in the file identified by dd-namewhere the error was detected

YKJ201E TSORC=32

The value value of name inPair information CSV file isinvalid: dd-name: rec#

The value assigned to name in the pair informationCSV 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





dd-name


rec#


YKJ202I TSORC=4

No copy pair is defined inspecified Pair informationCSV file.

No copy pair is defined in the pair information CSV file.No data was written in the copy group definition file.

YKJ203E TSORC=32

The number of itemsspecified for a line in Pairinformation CSV file isinvalid: dd-name: rec#

The number of items specified on one line of the pairinformation CSV file is incorrect.

dd-name


rec#


YKJ204E TSORC=32

Primary volume is notspecified in Pair informationCSV file: dd-name: rec#

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

dd-name


rec#


YKJ205E TSORC=32

Secondary volume is notspecified in Pair informationCSV file: dd-name: rec#

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

dd-name


rec#


YKJ206E TSORC=32

The specified volume doesnot exist in the diskconfiguration definition file:dd-name: rec#: device

The specified volume does not exist in the diskconfiguration definition file.

dd-name


rec#


device

One of the following is displayed. If both arespecified, the device number is displayed.

• Device number

• Storage system serial number, control unitnumber, and command control address number

Messages 1-51





The display format is storage-system-serial-number :CU-number :CCA-number .

YKJ207W TSORC=8

Inconsistencies exist amongthe values used to specifythe primary volume: dd-name: rec#

The P-VOL specified with the device number differsfrom the P-VOL specified with the storage system serialnumber, control unit number, and command controladdress number.

Although the copy group definition file was created, thesettings therein might contain an error.

dd-name


rec#


YKJ208W TSORC=8

Inconsistencies exist amongthe values used to specifythe secondary volume: dd-name: rec#

The S-VOL specified with the device number differsfrom the S-VOL specified with the storage system serialnumber, control unit number, and command controladdress number.

Although the copy group definition file was created, thesettings therein might contain an error.

dd-name


rec#


YKJ209E TSORC=32

Sub C/T group ID cannot bespecified for a copy-typeCopy Group: dd-name: rec#

A sub consistency group ID is specified for a copygroup of the copy type identified by copy-type. No subconsistency group ID can be specified if the copy typeis ShadowImage, TrueCopy, or TrueCopyAsynchronous.

copy-type

Copy type

dd-name


rec#


YKJ210E TSORC=32

The value specified forNumber-of-Pairs exceeds the

range in which volumesexist: Number-Of-Pairs: dd-name: rec#

No volume exists in the range of the Number-Of-Pairsrepetitions.

Number-Of-Pairs

Number of pair repetitions

dd-name


rec#

1-52 Messages






YKJ211E TSORC=32

PVOL & SVOL of SI pair is inthe different storage system:dd-name: rec#

A copy pair, which has a P-VOL storage system serialnumber and an S-VOL storage system serial numberthat do not match, was found in a copy group of copytype ShadowImage.

dd-namedd name of the CSV file where the error wasdetected

rec#


YKJ212E TSORC=32

A specific combination of astorage system serialnumber and a C/T group IDis used for multiple UR CopyGroups: dd-name: rec#

The combination of the copy groups is one of thefollowing:

• The serial numbers of the primary site storagesystems are the same; the serial numbers of thesecondary site storage systems are different; andcopy pairs with the same consistency group ID

exist.• The serial numbers of the primary site storage

systems are different; the serial numbers of thesecondary site storage systems are the same; andcopy pairs with the same sub consistency group IDexist.

If the copy type is Universal Replicator, thesecombinations are not supported.

dd-name


rec#


YKJ213E TSORC=32

Secondary volume is alreadyspecified in another copypair as a secondary device:dd-name: rec#

The volume specified as the S-VOL is also specified asthe S-VOL for other copy pairs. The same volumecannot be specified as the S-VOL for multiple copypairs.

dd-name


rec#


YKJ214W TSORC=8

A copy pair capacity checkcould not be performedbecause the capacity of avolume could not beacquired.

A copy pair capacity check could not be performedbecause the capacity of a volume could not beacquired. A capacity check cannot be performed ineither of the following cases:

• When a volume capacity has not been acquiredduring a Local Scan, Remote Scan, or NG Scan.

Messages 1-53





• When a volume is in any of the storage systemsbelow and a Remote Scan or NG Scan has beenperformed on the volume. In this case, thecapacity of the volume cannot be acquired.

- Lightning 9900V series

- USP

- USP VA copy group definition file was created, but thesettings might contain incorrect information.

YKJ215E TSORC=32

The capacities of the copypair volumes are different:dd-name: rec#

The capacities of the copy pair volumes are different. Acopy pair whose P-VOL and S-VOL capacities aredifferent cannot be defined.

To create a copy pair whose P-VOL and S-VOLcapacities are different for migration, specify NOCHECK

for the CAPACITY parameter, and execute the YKIMPORT

command. For details, see Hitachi Business Continuity Manager Reference Guide.

dd-name

The dd name of the CSV file where the error wasdetected

rec#

Number of the line in the file indicated by dd-namewhere the error was detected

YKJ250E TSORC=32

name is not specified inEXCTG information CSV file:dd-name: rec#

No value is assigned to the item identified by name inthe EXCTG information CSV file.

name

Name of the item in the EXCTG information CSVfile

dd-name


rec#


YKJ251E TSORC=32

The value value of name inEXCTG information CSV fileis invalid: dd-name: rec#

The format of the value assigned to name in the EXCTGinformation CSV file is invalid.

value

Value assigned to the item identified by name

name

Name of the item in the EXCTG information CSV

filedd-name


rec#


1-54 Messages





YKJ252E TSORC=32

The number of itemsspecified for a line in EXCTGinformation CSV file isinvalid: dd-name: rec#

The number of items specified on one line of theEXCTG information CSV file is incorrect.

dd-name


rec#


YKJ253E TSORC=32

Multiple EXCTG IDs arespecified in EXCTGinformation CSV file: dd-name

Multiple EXCTG IDs are specified in the EXCTGinformation CSV file.

dd-name


YKJ254E TSORC=32

The specified supervisor DKCor arbitration commanddevice is invalid: dd-name:rec#

The supervisor disk controller or arbitration commanddevice specification is incorrect.

dd-name


rec#


If the EXCTG information CSV file does not includea line that specifies the supervisor disk controller,nothing is displayed for rec#.

YKJ255E TSORC=32

A Copy Group that does nothave any correspondingentry in EXCTG informationCSV file is found: dd-name

The EXCTG information CSV file includes no entry (line)corresponding to the entry (line) specified in the pairinformation CSV file.

dd-name


YKJ256E TSORC=32

This entry does not have anycorresponding Copy Group inPair information CSV file:dd-name: rec#

The pair information CSV file includes no entry (line)corresponding to the entry (line) specified in theEXCTG information CSV file.

dd-name


rec#


YKJ257E TSORC=32

Multiple entries that specifythe same Copy Group aredefined in EXCTGinformation CSV file: dd-name: rec#

The EXCTG information CSV file contains multipleentries (lines) that specify the same copy group.

dd-name


rec#

Messages 1-55






YKJ258E TSORC=32

The EXCTG information isinconsistent: dd-name: rec#

The following entries specified as EXCTG informationare contradictory:

• EXCTG ID

• Supervisor disk controller

• Arbitration command device

It is likely that different combinations of copy directions(forward direction only, reverse direction only, orforward and reverse directions) exist in the EXCTGinformation CSV file.

dd-name


rec#


YKJ270E TSORC=32

name is not specified in CTGinformation CSV file: dd-name: rec#

No value is assigned to name in the CTG informationCSV file.

name

Name of an item in the CTG information CSV file

dd-name

DD name of the CSV file where the error wasdetected

rec#

Line number in the file dd-name where the errorwas detected

YKJ271E TSO

RC=32

The value value of name in

CTG information CSV file isinvalid: dd-name: rec#

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


rec#


YKJ272E TSORC=32

The number of itemsspecified for a line in CTGinformation CSV file isinvalid: dd-name: rec#

An invalid number of items was specified on one line inthe CTG information CSV file.

dd-name


rec#

1-56 Messages






YKJ273E TSORC=32

This entry does not have anycorresponding Copy Group inPair information CSV file:dd-name: rec#

The pair information CSV file includes no entries (lines)corresponding to the entries (lines) specified in theCTG information CSV file.

dd-name


rec#


YKJ274E TSORC=32

Multiple entries that specifythe same Copy Group aredefined in CTG informationCSV file: dd-name: rec#

The CTG information CSV file contains multiple entries(lines) in which the same copy group is specified.

dd-name


rec#


YKK001I PRT YKINSCHK completed.RC=return-code, V/R=version-number ,execution-date

The YKINSCHK command terminated.

return-code

Return code of the YKINSCHK command

version-number

Current Business Continuity Manager versionnumber

execution-date

Time at which the YKINSCHK command was

executed

The time is indicated in the format YYYY /MM /DD

HH :MM :SS

YKK101E TSORC=32

Failed to get security settinginformation,service=service-name,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 anerror

code2

Reason code of the OS service that encountered anerror

If no reason code is returned for an OS service,code2 is 0.

YKK102E TSORC=32

Failed to get user SVCroutineinformation,service=service-name,code=code1,code2.

User SVC information could not be acquired.

service-name


code1

Messages 1-57






code2


If no reason code is returned for an OS service,

code2 is 0.

YKK103E TSORC=32

Acquisition of host IDsettingsfailed,service=service-name,code=code1,code2.

Host ID setting information could not be acquired.

service-name


code1


code2


If no reason code is returned for an OS service,

code2 is 0.

Table 1-9 List of messages (message ID YKL0x)


YKL000T TSOSC=48

Supplied parameters invalid. Invalid parameters have been specified.

YKL001E TSORC=48



YKL002E TSORC=48

MSG(stem) does not includetrailing "." character.


stemStem name assigned to the MSG parameter

YKL003E TSORC=52

Unable to update MSG(stem)in Caller's environment.YKVSET result = result

An attempt to assign a value to a Message structurevariable failed. The resulting value is displayed inresult . This error can be caused by an invalid valuebeing specified for the MSG parameter.

stem


YKL004E MSGSC=48 RC=48



YKL005E MSG

SC=48 RC=48

STEM(stem) does not

include trailing "." character.


period.

stem



Unable to execute withoutvalid PREFIX parameter.

Specify a valid PREFIX parameter.

1-58 Messages






Unable to execute withoutvalid GROUP parameter.

Specify a valid GROUP parameter.

YKL050W MSGSC=4 RC=4(file:rec#)

Unrecognized elementencountered: name

Correct the specification on the line with the linenumber identified by rec# in the file identified by file. If the error still exists, contact HDS Technical Support forassistance.

name

XML element name

file


rec#


YKL051E MSGSC=36 RC=36(file:rec#)

End of file encountered incomment.

Check that the XML comments are balanced. Be carefulto ensure that any XML comments will not be nested. If the error still exists, contact HDS Technical Support for

assistance.file


rec#



Unrecognized Versionattribute value: value

The system does not recognize the version attributevalue of the XML element that exists on the line withthe line number identified by rec# in the file identifiedby file.

Check the indicated line, and then identify the cause of

the problem by referring to information contained inthe XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file


rec#



Unexpected termination of element: name

The XML element name that exists on the line with theline number identified by rec# in the file identified byfile has not been correctly created.


file


Messages 1-59





rec#



Invalid "&" characterdiscovered in quoted string.string

An invalid entity reference was found on the line withthe line number identified by rec# in the file identifiedby file.

Use only defined entity references as specified inExtensible Markup Language (XML) 1.0 at http://www.w3.org.

file


rec#



Unrecognized Encodingattribute value: value

The system does not recognize the encoding attributevalue of the XML element that exists on the line withthe line number identified by rec# in the file identified

by file.


file


rec#



Unrecognized attribute:name = value The system does not recognize the XML attribute thatexists on the line with the line number identified byrec# in the file identified by file.


name

XML attribute name

value

XML attribute value

file


rec#


1-60 Messages






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 theline number identified by rec# in the file identified byfile.


file


rec#


v .r .m

API level

For details about this value, see the informationabout the XML document type definitions in the

Hitachi Business Continuity Manager ReferenceGuide.

YKL079E MSGSC=44 RC=44(result )

YKVSET program failure for:name = value

An attempt to assign the value value to the variablename failed with the result value identified by result .This error can be caused by an invalid value beingspecified for the STEM parameter.


More than two DiskDeviceElements in CopyPair.

Only two copy pair elements are allowed: the firstelement for the P-VOL and the second element for theS-VOL.

Check the line with the line number identified by rec#in the file identified by file, and then identify the causeof the problem by referring to information contained in

the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file


rec#


YKL081W MSGSC=16 RC=16( pair-index )

Unable to resolve primarydevice address.

The YKLOAD program failed to resolve the unit number

(device address) of the P-VOL in the specifiedCopyPair. For configuration definition, this process usesthe Host Discovered Array object in the primary device

address domain. For other purposes, the current hostdevice address domain is used. The situationrepresented by this message is not always fatal. SomeCLI commands, such as YKSUSPND, can be successfully

executed by using only the S-VOL unit address.

pair-index

Messages 1-61





See the pair index description in the explanation of the YKE003E message.


Unable to resolve secondarydevice address.

The YKLOAD program failed to resolve the unit number

(device address) of the S-VOL in the specifiedCopyPair. For configuration definition, this process usesthe Host Discovered Array object in the secondary

device address domain. For other purposes, the currenthost device address domain is used. The situationrepresented by this message is not always fatal. ManyCLI commands can be successfully executed by usingonly the P-VOL unit address.

pair-index



Unable to resolve volumeserial number.

The YKLOAD program failed to resolve the volume serial

number of the P-VOL in the specified CopyPair. Forconfiguration definition, this process uses the HostDiscovered Array object in the primary device addressdomain. For other purposes, the current host device

address domain is used. The situation represented bythis message is not always fatal. At present, thevolume serial number is used only for display andwarning.

pair-index



Unable to read configurationfile.

The configuration file could not be read, because therecord length is too long.

file


rec#

Number of the line in the file file where the errorwas detected

YKL087E MSGSC=40 RC=40(file)

The license informationdataset could not be read.

An attempt to read the license information dataset hasfailed.

Check that the dataset name of the license key datasetis correct, and that the license key dataset was createdcorrectly. If necessary, transfer the license key fileagain and recreate the license key dataset.


File Open error: dsstate. An attempt to open the configuration file identified byfile failed.

dsstateStatus of the configuration file

file


1-62 Messages






File Close error: dsstate. An attempt to close the configuration file identified byfile failed.

dsstate


file



File Allocation Failed:dsstate.

An attempt to allocate the configuration file identifiedby file failed.

Verify that the configuration file identified by file iscorrectly created.

dsstate


file



File Deallocation Failed:dsstate. An attempt to deallocate the configuration fileidentified by file failed.

dsstate


file



File Read error: dsstate. An attempt to read the configuration file identified byfile failed.

dsstate


fileName of the configuration file in which the errorwas detected

YKL099I MSGTSO

process-name commandreturn 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 commanddevice definition file have been read. This messageis output when an invalid route list definition file orinvalid command device definition file is read inISPF.

reason-code

Reason code for the returned max-value

max-value


Messages 1-63




Table 1-10 List of messages (message ID YKL2x - YKL4x)





YKL202E TSORC=48

"SYSAUTH". cannot bespecified in MSG()

parameter.

SYSAUTH. cannot be specified in the MSG parameter.



"SYSAUTH." cannot bespecified in STEM()parameter.

SYSAUTH. cannot be specified in the STEM parameter.


YKL204E TSORC=48





Route parameter is allowedonly on 1st call of YKLOAD

The ROUTE parameter is allowed only on the first call of

the YKLOAD command.


The attribute attname isalready defined.

The XML attribute identified by attname has alreadybeen defined.

Review the file name identified by file and the attnamevalue on the line with the line number identified byrec#.

attname

XML attribute name

file


rec#


where the error was detected


The value value of theattribute name is an invalidformat.

The value value of the XML attribute name is in aninvalid format.


file


rec#



name attribute missing. The required XML attribute name is missing.Correct the specification on the line with the linenumber identified by rec# in the file identified by file.

file


rec#

1-64 Messages







The attribute statements areinvalid.

The XML attribute description is invalid.


file


rec#



This kind of elementselement can't be definedmore than once.

The XML element element is defined more than once.


file


rec#



The value value of attributename is not match withfilename.

The value value of the XML attribute name does notmatch the name in the file name.

Correct the specification on the line with the linenumber identified by rec# in the file identified by file,or correct the file name.

file


rec#Number of the line in the file identified by filewhere the error was detected


The element name-1, forwhich the value value wasspecified for the attributename-2, was not found.

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


file


rec#

Number of the line in file where the error wasdetected


name is not specified orinvalid.

The system symbol identified by name has not beendefined or has been assigned an invalid value.

If name is YKCMDIF:

Messages 1-65





The host ID that identifies the host on whichBusiness Continuity Manager is running is invalidor missing. Define YKCMDIF correctly.

For details about the host ID definition (YKCMDIF),

see the Hitachi Business Continuity Manager Installation Guide.


The element name isrequired, but no elementwas found.

The required XML element name is missing.Correct the specification on the line with the linenumber identified by rec# in the file identified by file.

file


rec#



The element statements areinvalid.

The XML element description is invalid.


number identified by rec# in the file identified by file.file


rec#



ETag name is mismatch. /correct-ETag-name isexpected, but /incorrect-ETag-name is specified.

The specified ETag name /incorrect-ETag-name is notthe expected ETag name /correct-ETag-name.


file


rec#



Extra ETag is specified:Etag-name

An extra Etag-name is specified.


file


rec#



The element name1 is not acontent of the elementname2.

The XML element identified by name2 contained theXML element name1 that cannot be specified.

1-66 Messages






file


rec#



name element missing. The XML element name is missing.


file


rec#



No command devices werefound.

No command devices were found.

Correct the route definition in the route list definitionfile shown in file.

file



No command devices aredefined for routes that issueremote commands or forroute labels.

No command device was found that is defined in theroute for remote command issuance or with thespecified route label.

Correct the route definition in the route list definitionfile identified by file.


rec#



The route label specified forthe ROUTE parameter hasnot been defined.

The route label specified for the ROUTE parameter is not

defined.

Correct the route definition in the route list definitionfile identified by file.

file



A route label is not specifiedfor the ROUTE parameter,even though a route label isdefined for all the commanddevices.

An attempt was made to load command device lines forwhich no route label is specified because no route labelis specified for the ROUTE parameter. However, route

labels are defined for all the command devices in theroute list definition file shown in file.

Messages 1-67





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 theroute list definition file shown in file.

file

Name of the configuration file where the error was

detectedYKL284E MSGSC=36 RC=36(file:rec#)

PVOL & SVOL of SI pair is inthe different storage system.

In a file for a copy group of the ShadowImage copytype, a copy pair has been discovered for which thestorage system serial numbers of the P-VOL and S-VOLdo not match.

Correct the line with the line number identified by rec#in the file identified by file.

file


rec#


where the error was detected

YKL290E MSGSC=44 RC=44(result )

YKVGET program failure for:vn

An attempt to acquire the variable vn failed with theresult value identified by result . This error can becaused by an invalid value being specified for the STEM

parameter.


function-name is notlicensed for use on thissystem.

The license key for the function identified by function-name has not been installed, has expired, or is notcorrectly recognized.

Check whether the license key is available for thisversion.

If function-name is This product:

Business Continuity Manager commands cannot beused because the Business Continuity Managerlicense key has not been installed.

If function-name is UR 4x4 Extended CTG:

The function for preserving consistency on anEXCTG basis cannot be used because the licensekey required for a 4x4 configuration has not beeninstalled.

YKL292E MSGCON SC=36RC=36

The expiration date for yourlicense key(function).

The license (function) has expired.

To continue using this product, you need a permanentlicense.





1-68 Messages





YKL293W MSGCON SC=0 RC=0

Your function license willexpire in n day(s).

The license (function) will expire in n days.







The element stack wasoverflowed.

The internal routine encountered a shortage of workspace.


file


rec#


YKL298E MSGTSO SC=44RC=44 (detailed-info)

CLI-name encountered anunexpected error.

An unexpected error has occurred. This error mighthave occurred with another error.





• The definition files operated on from the script orISPF panel (the copy group definition file, diskconfiguration definition file, command devicedefinition file and route list definition file).

CLI-name

The name of the executed CLI command

detailed-info

Detailed information displayed to assist yourHitachi Data Systems representative or authorizedservice provider in resolving the problem


The values of attribute1 andattribute2 conflict.

The values attribute1 and attribute2 conflict.

Make sure that both of these values are valid, and thenretry the operation.

attribute1

Attribute name 1 included in the copy groupdefinition

Messages 1-69





attribute2

Attribute name 2 included in the copy groupdefinition

Table 1-11 List of messages (message ID YKM0x)


YKM000T TSORC=48


For details, see the reason code in the YKM099I


YKM001E TSORC=48


YKM001E MSGSC=48 RC=48


YKM002E MSGSC=48 RC=48 Copy Group STEM(stem)does not include trailing "." The last character of the STEM parameter is not aperiod.

stem


YKM002E MSGSC=48


YKM002E TSO Messages MSG(stem) doesnot include trailing "."


stem


YKM008E MSGSC=48


hexadecimal format.

YKM010E TSORC=40




nnnn


YKM011E ISPF This device number msgdevnhas not been discovered onmsgdad .

The device number indicated by msgdevn has not beenscanned in the device address domain indicated bymsgdad .

msgdevn

Device number

msgdad Device address domain

YKM012E ISPF The End Devn value mustnot be lower than the StartDevn

The End device number is lower than the Start devicenumber.

1-70 Messages





YKM014E ISPF This Copy Group ID isalready defined. Choose adifferent ID.

The copy group ID is already defined. Please useanother ID.

YKM015I LOG RC:nn CMD:command The command terminated with the return code nnnnafter 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 asadditional 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 whenissuing the command.

YKM018E ISPF A Consistency Group ID (C/TID) is required for TrueCopyAsync Copy Group definition.

To define a TrueCopy Asynchronous copy group, aconsistency group ID is required.

YKM020E ISPF Please supply the requiredinformation.

Enter the required information.

YKM021E ISPF Check either Device num orVolser

Select either Device Num or Volser.

YKM022E ISPF The End Volser value mustnot be lower than the Start

Volser

The End Volser value is lower than the Start Volservalue.

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 aCopyGroup Containerwithout C/T ID.

You cannot add a copy group to a copy group containerif no consistency group ID is specified for the copygroup.

YKM026E ISPF The secondary device sdevnis already paired to primarydevice pdevn.

The secondary device indicated by sdevn is alreadydefined as a copy pair in the primary device indicatedby pdevn.

sdevn


pdevn


YKM027E ISPF The primary device pdevnand secondary device sdevnare on different storagesystem.

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

pdevn


Messages 1-71





sdevn


YKM030E ISPF File not found. The file was not found.

YKM031E ISPF Refresh SMS key is notavailable in case of Copy

Group Creation.

The Refresh SMS key is not available while a new copygroup 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/TID.

Press the F10 key, and then select a consistency groupID.

YKM035E ISPF inputfld is not specified orinvalid.

No value is specified in inputfld , or the specified valueis 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 notallowed.

Changing a local device address domain ID is notallowed.

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

YKM039E ISPF Specified device is notcommand device becauseAPID is not available.

The device you specified is not a command devicebecause the APID cannot be used.

YKM040E ISPF A Consistency Group ID (C/TID,sub C/T ID) is requiredfor Universal Replicator CopyGroup definition.

For the Universal Replicator copy group definition, youneed to specify a consistency group ID and a subconsistency group ID.

YKM041E ISPF A sub Consistency Group IDcannot be specified forSI/TC/TCA Copy Groupdefinition.

For the ShadowImage/TrueCopy/TrueCopyAsynchronous copy group definition, you cannot specifya sub consistency group ID.

YKM042E ISPF This Consistency Group ID(C/T ID,sub C/T ID) isalready defined. Choose adifferent ID.

This consistency group ID is already defined. Pleasechoose a different ID.

YKM043E ISPF A Mirror ID is required forUniversal Replicator CopyGroup definition.

For the Universal Replicator copy group definition, youneed to specify a mirror ID.

YKM044E ISPF This Path Set ID is alreadydefined.

This path set ID is already defined.

YKM045E ISPF Physical path ( priport secport ) is already defined inthis logical path.

The physical path is already defined as a logical path.

priport

The primary port you specified

secport

1-72 Messages





The secondary port you specified

YKM046E ISPF The end CU/CCA value mustnot be lower than the startCU/CCA.

The end control unit/command control address value islower than the start control unit/command controladdress value.

YKM047E ISPF Processing to insert or edit astorage system was denied

because the storage systemhas already been discoveredby the selected DADID.

A storage system cannot be inserted into, or edited in aroute because the storage system has already been

scanned via the specified device address domain ID.

Correct the specified device address domain ID andserial number of the storage system.

YKM048E ISPF You cannot perform a devicescan because a remoteDADID or Non Gen'edDADID was specified as thelocal DADID in the SetDefaults panel.

Devices cannot be scanned because the remote deviceaddress domain ID or Non Gen'ed device addressdomain ID has been specified as the local deviceaddress domain ID in the Set Defaults panel.

YKM049E ISPF A Path ID is required forUniversal Replicator CopyGroup definitions.

To define a Universal Replicator copy group, a pathgroup ID is required.

YKM050E MSGSC=36 RC=48(attribute-value)




name

REXX variable name

attribute-value

REXX variable value


NOCOPY option invalid forShadowImage Copy Group

The YKMAKE command with the NOCOPY parameter

specified was executed on a ShadowImage copy group.This parameter is invalid on ShadowImage copygroups.

Re-execute the YKMAKE command without specifying

the NOCOPY parameter.


Some pairs in this group donot support TCA services



YKM099I TSO YKMAKE command returncode=nnnn, reasoncode=rrrr

The YKMAKE command terminated with the return code



nnnn


Messages 1-73




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


YKM103E MSGSC=48

The parameter combinationis invalid

The parameter combination is invalid.

YKM500E ISPF You cannot perform aremote scan if the specified

DADID matches a local orNon Gen'ed DADID or if theloaded HDA file is not forremote scan or if the PresetRouteListID, which is in theSet Defaults panel, is notenabled.

A Remote Scan cannot be performed in the followingcases:

• The specified device address domain ID isequivalent to the local device address domain IDor a Non Gen'ed device address domain ID.

• When the HDA file is not a file used for a RemoteScan

• When the Preset RouteListID set in the SetDefaults panel is not valid.

YKM501E ISPF You cannot edit the devicenumber for a volume thatwas not found by remotescan or NG scan.

The device number cannot be edited because thevolume was not found by a Remote Scan or an NGScan. For details about the NG Scan, see the Hitachi Business Continuity Manager User Guide.

YKM502E ISPF You cannot exit until alldiscovered devices areassigned dummy devn.

The exit operation cannot be performed until a devicenumber is assigned to all discovered devices.

YKM503E ISPF The number of connectionsof inter-DKC paths exceedsthe maximum number of connections that is allowedwithin the same storagesystem.

The number of connections of inter-disk controllerpaths exceeded the maximum that is allowed withinthe same storage system.

YKM504E ISPF The number of connectionsof inter-DKC paths of thesame PathID exceeds themaximum number of

connections that is allowedwithin the same storagesystem.

The number of connections of inter-disk controllerpaths of the same PathID exceeded the maximum thatis allowed within the same storage system.

YKM505E ISPF This inter-DKC path isalready defined in anotherlogical path.

This inter-disk controller path is already defined inanother logical path.

YKM506E ISPF You cannot define inter-DKCpath with this interfaceversion.

In this interface version, the user cannot define inter-disk controller paths.

YKM507E ISPF The number of connectionsof inter-CU paths exceedsthe maximum number of connections that is allowedwithin the same CU.

The number of connections of inter- control unit pathsexceeded the maximum that is allowed within the samecontrol unit.

YKM508E ISPF This inter-CU path is alreadydefined in another logicalpath.

This inter- control unit path is already defined inanother logical path.

YKM509E ISPF The number of physicalpaths that are defined in the

The number of physical paths exceeded the maximumthat is allowed within the same logical path.

1-74 Messages





same logical path exceedsthe limit.

YKM510E ISPF This Model is not supportedfor this Path Type.

This model does not support this path type.

YKM511E ISPF The value of CU exceeds thenumber of CUs that is

allowed in this Model.

The number of control units exceeds the maximumnumber for this model.

YKM512E ISPF The number of logical pathsthat are using this portexceeds the limit.

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

YKM513E ISPF The number of connectionsexceeds the limit that isallowed within this port.

The number of connections exceeded the limit that isallowed within this port.

YKM514E ISPF CCA could not be assignedbecause either the path isalready defined in anotherlogical path, or the list of CCA could not be retrieved.

A command control address could not be assignedbecause the path is already defined in another logicalpath, or because a list of command control addressescould not be obtained.

YKM515E ISPF You cannot specify the sameserial number to the primaryside and the secondary sideof the same logical path.

The same serial number cannot be specified for boththe primary and secondary sides of the same logicalpath.

YKM516E ISPF Port errport is alreadydefined 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 exceedsthe value that is allowed inthis Model.

The value of PathID exceeds the maximum for thismodel.

YKM518E ISPF Port errport exceeds thelimit that is allowed in thiscomposition.

The number of ports exceeds the maximum number forthis composition.

errport

The port that you specified

YKM519E ISPF Different PathIDs cannot bespecified for the primary sideand secondary side of aninter-DKC path.

The path ID that is different for the primary site and forthe secondary site cannot be specified to the inter-diskcontroller logical path.

YKM520E ISPF These device numberremdevn or storage system

S/N remsn are notdiscovered on DeviceAddress Domain remdad .

The device number or storage system serial numberhas 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





The device address domain ID you specified

YKM521E ISPF You cannot exit this paneluntil you define a commanddevice.

The exit operation cannot be performed until youdefine a command device.

YKM522E ISPF Please supply the requiredinformation.

Enter the necessary information.

YKM523E ISPF You cannot enter values toboth License Key DatasetName field and Key Codefield at the same time.

The License Key Dataset Name and Key Code fieldscannot be specified simultaneously.

YKM524E ISPF Please enter alphanumericcharacters to Key Code field.

The value specified in the Key Code field containscharacters that are not numbers or letters.

YKM525E ISPF Invalid Key Code is entered.Please re-enter the KeyCode.

The key code is incorrect. Please re-enter the key code.

YKM526E ISPF Invalid dataset name isspecified.

An incorrect dataset name is specified.

YKM527E ISPF You cannot specify thelicense information dataset.

The license information dataset cannot be specified.

YKM528E ISPF Enter the value that youwish to find with the LOCATEcommand on a sorted field"field-name".

Enter the value that you want to find in the sorted fieldfield-name by using the LOCATE command.

field-name

field name

YKM529E ISPF You cannot specified except'00' as PathID with thisinterface version.

Only 00 can be specified for a path ID in this interface

version.

Table 1-13 List of messages (message ID YKM7x)Message ID Message text Explanation and recommended actions

YKM700E ISPF Enter one of the listedvalues.

Please enter one of the listed values.

YKM701E ISPF Enter required field at thecursor position.

Enter the required information at the cursor position.

YKM702E ISPF The length of the data mustbe = 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 alphanumericcharacters (0-9, A-Z, a-z).

Enter alphanumeric characters (0-9, A-Z, a-z).

YKM705E ISPF Each qualifier must be 1-8alphanumeric characters

Each qualifier must be from 1 to 8 alphanumericcharacters (0-9, A-Z, a-z), and must begin with analphabetic character.

1-76 Messages





(0-9, A-Z, a-z), the firstalphabetic.

YKM706E ISPF The length of the "field-name" field data must be nomore than loclen.

The length of the input entered into the field-namefield 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) tosearch for.

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

YKM708E ISPF Enter the number (numericalcharacters: 0-9) to searchfor.

Enter the numeric values (0-9) that you want to searchfor.

YKM709E ISPF Execute the sort commandbefore executing the locatecommand.

Execute the SORT command before executing the

LOCATE command.

YKM710E ISPF Enter one of the followingcharacters(P, S, N/A) tosearch for.

Enter the character you want to search for (P, S, or

N/A).

YKM720E ISPF Required parameter is notspecified.

Enter the required parameters.

YKM721E ISPF Invalid field name isspecified.

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 forvalue 2, as the range specification condition.

• NULL was specified for value 1, as the rangespecification condition.

• A value containing an asterisk (*) was specified forvalue 1 or value 2, as the range specificationcondition.

• The specified value contained two or moreasterisks.

• An asterisk (*) was specified in a location otherthan before or after the value.

YKM723E ISPF Invalid action name isspecified.

Enter the valid action name.

YKM724E ISPF The length of the "field-name" field data must be nomore than value-length.

The length of the input entered into the field-namefield must be equal to or less than value-length.

field-name

field name

value-length

Input length

Messages 1-77





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 (numericalcharacters: 0-9).

Enter a numeric value (0-9).

YKM727E ISPF Range specification is not

supported for the field.

A range cannot be specified for the field.

YKM728E ISPF The specified patternproduced no matching lines.

A line that matches the specified pattern was notfound.

YKM731E ISPF ISPF service error occurred.info

An error occurred in the ISPF service.

info


YKM750E ISPF Serial number must be a 5-digit 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 acombination of one or more

qualifiers. Each qualifiermust be 1-8 alphanumericcharacters (0-9, A-Z, a-z)with the first character beingan alphabetic character (A-Z, a-z). The length of DADIDmust be 1-28.

The device address domain ID must be a combinationof one or more qualifiers. Each qualifier must be from 1

to 8 alphanumeric characters (0-9, A-Z, a-z), and mustbegin with an alphabetic character (A-Z, a-z). Thelength of the device address domain ID must be from 1to 28 characters.

YKM752E ISPF DEVN must be 4hexadecimal characters(0-9, A-F, a-f).

The device number must be a four-digit hexadecimalnumber (0-9, A-F, a-f).

YKM753E ISPF APID must be 4 hexadecimalcharacters (0-9, A-F, a-f).

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

YKM754E ISPF Route List ID must be acombination of one or morequalifiers. Each qualifiermust be 1-8 alphanumericcharacters (0-9, A-Z, a-z)with the first character beingan alphabetic character (A-Z, a-z). The length of RouteList ID must be 1-8.

The route list ID must be a combination of one or morequalifiers. Each qualifier must be from 1 to 8alphanumeric characters (0-9, A-Z, a-z), and mustbegin with an alphabetic character (A-Z, a-z). Thelength of the route list ID must be from 1 to 8characters.

YKM755E ISPF Configuration File Prefixmust be a combination of one or more qualifiers. Eachqualifier must be 1-8alphanumeric characters(0-9, A-Z, a-z) with the firstcharacter being analphabetic character (A-Z, a-z). The length of Configuration File Prefixmust be 1-16.

The prefix of the configuration file name must be acombination of one or more qualifiers. Each qualifiermust 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 configuration file nameprefix must be from 1 to 16 characters.

1-78 Messages





YKM756E ISPF Copy Group ID must be acombination of one or morequalifiers. Each qualifiermust be 1-8 alphanumericcharacters (0-9, A-Z, a-z)with the first character beingan alphabetic character (A-

Z, a-z). The length of CopyGroup ID must be 1-40.

The copy group ID must be a combination of one ormore qualifiers. Each qualifier must be from 1 to 8alphanumeric characters (0-9, A-Z, a-z), and mustbegin with an alphabetic character (A-Z, a-z). Thelength of the copy group ID must be from 1 to 40characters.

YKM757E ISPF The 4-digit year (YYYY) or 2-digit month (MM) or 2-digitday (DD) was not numeric.Valid year values are1970-2042, valid monthvalues are 01-12, and validday 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 secondvalue is not numeric. Validvalues are 00-23 for hour,00-59 for minute, and 00-59for second.

The value for the hour, minute, or second was notnumeric. Specify a value for the hour, minute, andsecond 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 usedwhen C/T ID is not specified.

You cannot set the Preset Mode without specifying aconsistency group ID.

YKM761E ISPF Check Device Num, Volser,or Non Gen'ed.

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

YKM762E ISPF You cannot perform an NGscan because the specifiedDADID matches a local orremote DADID.

You cannot perform an NG Scan, because the specifieddevice address domain ID is the same as the localdevice address domain ID or remote device addressdomain ID. For details about the NG Scan, see the

Hitachi Business Continuity Manager User Guide.

YKM763E ISPF You cannot perform an NGscan because no local scanhas been performed for thespecified storage system.

You cannot perform an NG Scan, because a Local Scanhas not been performed for the specified storagesystem. For details about the NG Scan, see the Hitachi Business Continuity Manager User Guide.

YKM764E ISPF Select one of the displayedlines.

Select one of the displayed lines.

YKM765I ISPF A description for thespecified error code was notfound.

A description for the specified error code was notfound.

For details about error codes, see XXX. If the errorcode is not listed in the manual, contact your HitachiData Systems representative or authorized serviceprovider.

YKM766E ISPF Specified Prefix is being usedby another program.



YKM767E ISPF This command is invalid forTrueCopy Copy Groupslinkaged with HyperSwap.

The command cannot be executed for TrueCopy copygroups with the HyperSwap attribute.

Messages 1-79





Execute the PPRC copy pair operation from TPC-R.

YKM768E ISPF HS cannot be used when C/TID is specified.

If a consistency group ID is specified, you cannotspecify HS for the linkage option.

YKM769E ISPF Route Label must be anasterisk (*), or acombination of one or more

qualifiers. Each qualifiermust be 1-8 alphanumericcharacters (0-9, A-Z, a-z)with the first character beingan alphabetic character (A-Z, a-z). The length of RouteLabel must be 1-8.

The route label must be an asterisk (*), or acombination of one or more qualifiers. Each qualifiermust 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 route label must be from1 to 8 characters.

YKM770E ISPF Enter unique value in astorage system.

Enter a value that is unique within the storage system.

YKM771I ISPF Panel could not scrollbecause it shows beginningof data.

The panel cannot be scrolled because the start of thedata is already being displayed.

YKM772I ISPF Panel could not scrollbecause it shows end of data.

The panel cannot be scrolled because the end of thedata is already being displayed.

YKM773E ISPF DADID must be shortened sothat dataset name of diskconfiguration file is no morethan 44 characters.

The dataset name of the disk configuration fileexceeded the 44-character limit. Shorten the deviceaddress domain ID.

YKM774E ISPF Specified storage system isdefined in the same route.

The specified storage system is already defined in theroute. Select a different storage system.

YKM775E ISPF Panel could not proceed theinsert action becausenumber of the route entry

has reached maximum.

The storage system cannot be added because thenumber of storage systems defined in the route isalready at the maximum.

YKM776E ISPF Route Label must be acombination of one or morequalifiers. Each qualifiermust be 1-8 alphanumericcharacters (0-9, A-Z, a-z)with the first character beingan alphabetic character (A-Z, a-z). The length of RouteLabel must be 1-8.

The route label must be a combination of one or morequalifiers. Each qualifier must be from 1 to 8alphanumeric characters (0-9, A-Z, a-z), and muststart with an alphabetic character (A-Z, a-z). Thelength of the route label must be from 1 to 8characters.

Table 1-14 List of messages (message ID YKM90x)


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





After that, you can execute whichever BusinessContinuity Manager commands you need to.

YKM902E TSO Load module is not found. The Business Continuity Manager load module was notfound. The Business Continuity Manager dataset mightnot be concatenated to the LNKLST.

Revise the settings for the LNKLST, and then execute

the YKSTART command.After that, you can execute whichever BusinessContinuity Manager commands you need to.

YKM903E TSO SELECT service terminatedabnormally. RC=nn

The SELECT service terminated abnormally with thereturn code nn.

If this message is displayed immediately afterexecuting the YKSTART command, the Business

Continuity Manager dataset might not be concatenatedto the panel library (dd name: ISPPLIB), the tablelibrary (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 ContinuityManager dataset to the alternate panel library (ddname: ISPPALT). For details, see the Hitachi BusinessContinuity Manager Installation Guide.

nn

Return code of the service

YKM904E TSO Message library was notfound.

The message library was not found.

The Business Continuity Manager dataset might not beconcatenated to the message library (dd name:ISPMLIB).

If DBCS (Double-Byte Character Set) is enabled for theenvironment, concatenate the Business Continuity

Manager dataset to the alternate message library (ddname: ISPMALT). For details, see the Hitachi BusinessContinuity Manager Installation Guide.

YKM905E TSO A GETMAIN error occurred. A GETMAIN error occurred. The program will stoprunning.


YKM906E TSO A FREEMAIN error occurred. A FREEMAIN error occurred. However, the program willcontinue to run.


Table 1-15 List of messages (message ID YKN0x)


YKN000T TSORC=48


For details, see the reason code in the YKN099I


Messages 1-81





YKN001E TSORC=48


YKN001E MSGSC=48 RC=48


YKN002E MSG

SC=48 RC=48

Copy Group STEM(stem)

does not include trailing "."


period.stem


YKN002E TSORC=48



stem


YKN010E TSORC=40




nnnn

Error code returned upon REXX accessYKN050E MSGSC=48 RC=48(attribute-value)




name

REXX variable name

attribute-value

REXX variable value

YKN099I TSO YKRUN command returncode=nnnn, reasoncode=rrrr

The YKRUN command terminated with the return code


This message is always displayed to indicate the return

code and the reason code.

nnnn


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


YKP000T TSORC=48


For details, see the reason code in the YKP099I

message that will appear after this message. For

reason codes, see IKJPARS in the TSO/E ProgrammingServices.

YKP001E TSORC=48


YKP001E MSGSC=48 RC=48


1-82 Messages








period.

stem


YKP002E TSO

RC=48

Messages MSG(stem) does

not include trailing "."


stem



This command is only validfor TCA or UR Copy Groups

The YKSTATS command was executed on a copy group

that is neither TrueCopy Asynchronous nor UniversalReplicator. This command works only on TrueCopyAsynchronous or Universal Replicator copy groups.



Some storage systems inthis Copy Group do notsupport TCA statisticsreports

The TrueCopy Asynchronous copy group on which theYKSTATS command has been executed contains an

unsupported IFType.


YKP010E TSORC=40


Access to the REXX variable indicated by name failed.


nnnn

Error code for REXX access


The storage system serial number pairs with more than4 storage systems.

The storage system identified by serial-number ispaired with more than four storage systems within theconsistency group group.

Correct the copy pair configuration within theconsistency group group.

serial-number

Storage system serial number (12 digits)

YKP099I TSO YKSTATS command returncode=nnnn, reasoncode=rrrr

The YKSTATS command terminated with the return code



nnnn


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


YKQ000T TSORC=48


For details, see the reason code in the YKQ099I

message that will appear after this message. For

Messages 1-83





reason codes, see IKJPARS in the TSO/E ProgrammingServices.

YKQ001E TSORC=48


YKQ001E MSGSC=48 RC=48





period.

stem


YKQ002E MSGSC=48


YKQ002E TSORC=48



stem


YKQ003E MSGSC=48 Parameters combination isinvalid The parameter combination is invalid.

YKQ008E MSGSC=48


hexadecimal format.

YKQ010E TSORC=40


Access to the REXX variable indicated by name failed.


nnnn

Error code for REXX access


( pair-index )

SI PAIR deficiency. DEVNdevice#(SN ,CU#,CCA#)

In a ShadowImage copy group, the volume in thetarget copy pair has already been paired with three

volumes other than the pairing volume specified in thecopy group definition.

Review the applicable copy pair definition in the copygroup 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






pair-index


YKQ019W MSGSC=12 RC=0( pair-index )

Primary volume serialchanged. DEVNdevice#(SN ,CU#,CCA#)

Although the P-VOL is online, the current volume serialnumber does not match the volume serial numberdefined for the copy group. Processing will continue.

Check that the copy group indicates the correctvolumes 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.DEVNdevice#(SN ,CU#,CCA#)

Check that the S-VOL status is SIMPLEX.

device#

Device number


displayed.

SN



displayed.

CU#

Control unit number


CCA#



pair-index


Messages 1-85





YKQ026W MSGSC=8 RC=8( pair-index )

Primary volume is offline.DEVNdevice#(SN ,CU#,CCA#)

The volume serial number of the P-VOL cannot beobtained because the P-VOL is offline.

Check that the copy group indicates the correctvolumes and is not being used for other purposes,make the P-VOL online, and then re-execute theYKQUERY command.

device#Device number


displayed.

SN



displayed.

CU#

Control unit number


CCA#



pair-index


YKQ099I TSO YKQUERY command returncode=nnnn, reasoncode=rrrr

The YKQUERY command terminated with the return code



nnnn


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


YKR000T TSORC=48


For details, see the reason code in the YKR099I


YKR001E TSORC=48


YKR001E MSGSC=48 RC=48





period.

1-86 Messages





stem


YKR002E MSGSC=48


YKR002E TSO

RC=48

Messages MSG(stem) does

not include trailing "."


stem


YKR008E MSGSC=48


hexadecimal format.

YKR010E TSORC=40




nnnn


YKR050E 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




Check whether the command can be executed on thiscopy group, and then re-execute the command.

YKR099I TSO YKRESYNC command return

code=nnnn, reasoncode=rrrr

The YKRESYNC command terminated with the return



nnnn


YKR103E MSGSC=48

Parameters combination isinvalid


Table 1-19 List of messages (message ID YKS0x)


YKS001E TSORC=48



YKS002E TSORC=48

MSG(stem) does not includetrailing "."


stem

Messages 1-87






YKS003E TSORC=52

Invoke YKSTORE REXXScript via YKSTOREAssembler 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 inthe previous YKS003E message.

YKS003E TSORC=52

Unable to update MSG(stem)in Caller's environment.YKVSET result = result

An attempt to assign a value to a variable of theMessage structure failed with the result value indicatedby result . This implies that the YKSTORE REXX

subroutine has not properly been invoked or thatBusiness Continuity Manager has not properly beeninstalled.

stem


YKS004E MSGSC=48 RC=48




STEM(stem) does notinclude trailing "." character.


period.

stemStem name assigned to the STEM parameter


Unable to execute withoutvalid PREFIX parameter.

Specify a valid PREFIX parameter.

YKS079E MSGSC=44 RC=44(result )

YKVSET program failure for:variable =value.

An attempt to assign the value value to the variablevariable failed with the result value identified by result .This error can be caused by the YKSTORE REXX

subroutine's compiled REXX module being directlyexecuted.

Use the YKSTORE REXX subroutine, instead of directly

executing the compiled REXX module.


Error reported during fileoutput. EXECIO RC =n

Because the EXECIO TSO/E REXX command failed(return code = n), the YKSTORE command is

unavailable for creating or updating the configurationfile. For details, see the TSO/E REXX User's Guide.

YKS086E MSGSC=44 RC=44(file)

File status is:dsstate The input configuration file identified by file isunavailable.

dsstate

Status of the input configuration file

The following messages are output if the attributeof 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 currentconfiguration file, and then recreate a newconfiguration file that has correct file attributes.

• RECFM = XX . RECFM must be YY

The file is unavailable because the RECFM attribute

value is abnormal. Therefore, delete the current

1-88 Messages





configuration file, and then recreate a newconfiguration file that has correct file attributes.

• LRECL = XX . LRECL must be YY

The file is unavailable because the LRECL attribute

value is abnormal. Therefore, delete the currentconfiguration file, and then recreate a new

configuration file that has correct file attributes.• BLKSIZE = XX . BLKSIZE must be YY

The file is unavailable because the BLKSIZE

attribute value is abnormal. Therefore, delete thecurrent configuration file, and then recreate a newconfiguration file that has correct file attributes.

• ALLOCATION FAILED

Creation of a configuration file failed. Check thefree device capacity and the available size of VTOC.

For details about the required device capacity for aconfiguration file, see the Hitachi BusinessContinuity Manager Reference Guide.

• UNAVAILABLE DATASETThe configuration file is being used. Check theusage of the configuration file.

XX displays the file attribute value that caused theerror and YY displays the correct file attribute value.

file



Specified STEM() is notCopyGroup object.

The prefix of the REXX variable name specified in theSTEM parameter does not comply with the copy group

structure described in the Hitachi Business Continuity Manager Reference Guide.

YKS099I MSGTSO SC=max-severity RC=max-value

YKSTORE ProcessingComplete.

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)


YKS203E TSORC=52

Invoke YKSTORE REXXScript via YKSTOREAssembler subroutine.

The YKSTORE REXX program can only be invoked viathe YKSTORE assembler REXX subroutine. This message

indicates the most likely cause of the error indicated inthe previous YKS203E message.

YKS203E TSORC=52

The MSG(stem) value cannotbe acquired in the caller's

An attempt to acquire the variable value of theMessage structure failed with the result value identifiedby result . This implies that the YKSTORE REXX

Messages 1-89





environment. (YKVGET result= result )

subroutine has not properly been invoked or thatBusiness Continuity Manager has not properly beeninstalled.

stem


YKS250E MSG

SC=36 RC=36

The value value of the

variable name is an invalidformat.

The value value of the variable identified by name is

invalid.


Too long record:record . An attempt to output record to a dataset failed becauserecord was too long.

Correct the variable setting so that the length of record becomes 256 characters or shorter.


Failed to operationconfiguration file. (name=dataset-name, dsstate)

Creation of the configuration file is stopped because anerror occurred during the creation of the configurationfile. Refer to the information output in the message toreview the environment, and then create theconfiguration file again. For details about what actionto 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 theconfiguration file.

• UPDATE

An error occurred during the update of the existingconfiguration file.

• ALLOCATION

An error occurred during the allocation of the

configuration file. Check the free capacity on thedevice and the available size of VTOC. For details

about the required capacity on the device for aconfiguration file, see the Hitachi BusinessContinuity Manager Reference Guide.

• CHECK

An error occurred during the check of the existingconfiguration file. Check the status of theconfiguration file. The error might have occurredbecause the configuration file is in an unusablestate, or the dataset format is invalid. If thedataset format is invalid, check the message thatwas output simultaneously.

• EXECIOAn error occurred while writing to the configurationfile. For the cause of the error, check the messagethat was output simultaneously.

• RENAME

An error occurred when the YKBTSCAN command

was executed, and the configuration file was being

1-90 Messages





renamed to the name displayed in dataset-name.Check whether the dataset name displayed indataset-name actually exists in the system, andthen execute the command again.

Information about the file with the name to bechanged 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 iscurrently allocated

extent indicates the number of extents that areallocated to the dataset indicated by dataset-name.

• DSORG=VSAM

The dataset format is VSAM. A dataset with theformat VSAM cannot be used as a configurationfile. Change the dataset format of theconfiguration 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 theconfiguration file is not assigned.

nnnn (decimal (base 10) number) indicates areason code (maintenance information).

This message indicates that, if dataset-namecontains NEW or OLD, an error occurred while

processing the temporary file used for creating orupdating the configuration file.


file-name is too long for afilename.

The file name identified by file-name is too long. Thefile name must consist of 44 or fewer characters.

YKS290E MSGSC=44 RC=44(result )

YKVGET program failurefor:vn

An attempt to acquire the variable vn failed with theresult value identified by result . This error can becaused 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 MSGSC=44 RC=44(detailed-info)

YKSTORE encountered anunexpected error.

An unexpected error has occurred. This error mighthave occurred with another error.

Messages 1-91









• The configuration files operated on from the scriptor ISPF panel (the copy group definition file, diskconfiguration definition file, command devicedefinition file and route list definition file).

detailed-info

Detailed information displayed to assist yourHitachi Data Systems representative or authorizedservice provider in resolving the problem

Table 1-21 List of messages (message ID YKT0x)


YKT001E CON Can't find SVCTABLE The "SVCTABLE" search in the NUCLKUP macro failed.The program abnormally terminates with usercompletion code 996.


YKT002E CON Can't find IGCERROR The "IGCERROR" search in the NUCLKUP macro failed.The program abnormally terminates with usercompletion code 996.


YKT003E CON No SVC #'s available No SVC number available. The program abnormallyterminates with user completion code 996.

YKT004E CON Couldn't add SVC entry SVC number addition failed in the SVCUPDTE macro.The program abnormally terminates with usercompletion code 996.


YKT005E CON Couldn't create name/token Name/Token registration failed. The programabnormally terminates with user completion code 996.


YKT006W CONRC=16 Couldn't delete name/token Name/Token deletion failed.Contact HDS Technical Support for assistance.

YKT007W CONRC=16

Couldn't delete SVC entry SVC number deletion failed in the SVCUPDTE macro.


YKT008E CONRC=20

System task started withoutSTART from TSO.

The YKALCSVC command was executed in the TSO/E

environment.

1-92 Messages





Execute the YKALCSVC command using the START

command or a batch job.

YKT012E CONRC=16

Name/token error An error occurred in the Name/Token service.


YKT021E CON

RC=20

Invalid parameter A value specified in the PARM parameter is invalid.

Check the specification of the PARM parameter.

YKT022E CONRC=4

SVC routine is alreadyinserted

The user SVC is already registered.

YKT023E CONRC=16

Couldn't delete SVC routine The user SVC deletion failed.


YKT024E CON Couldn't copy load module Copying of the load module failed. The programabnormally terminates with user completion code 996.


YKT025E CONRC=4

SVC routine is alreadydeleted

The user SVC is not registered or is deleted.

YKT026E CON SVC # is already used The specified SVC number is already used. Theprogram abnormally terminates with user completioncode 996.

Specify an unassigned SVC number in the PARM

parameter of the YKALCSVC command, or re-execute

without the PARM parameter.

YKT032E CONRC=20

The task is not APF-authorized.

The dataset name of the Business Continuity Managerload library was not registered in SYS1.PARMLIB.Alternately, the execution of the command failedbecause authorized/unauthorized datasets co-existedwhile concatenating DD statements in the load library,and they were handled as unauthorized datasets.

YKT098I CONRC=0

SVC routine is deleted The user SVC deletion succeeded.

YKT099I CONRC=0

SVC routine is inserted The user SVC registration succeeded.



YKT210E CONRC=8

System task started withoutSTART from TSO.

The command was invoked from the TSO/Eenvironment. The program stops processing.

Invoke the command using the START command, or as

a batch JOB.

YKT211E CONRC=12

Failed to allocate space inCSA

A GETMAIN error occurred in CSA. The program stopsprocessing.


YKT212E CONRC=12

Couldn't register Name/Token

An error occurred during Name/Token registration. Theprogram stops processing.

Messages 1-93






YKT213E CONRC=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.Contact HDS Technical Support for assistance.

YKT220E CONRC=8

Unknown keyword isspecified

The specified keyword is unknown. The program stopsprocessing.

Specify a valid keyword and then re-execute thecommand.

YKT221E CONRC=4

Specified HOST ID is invalid The value assigned to the YKCMDIF parameter is

invalid. The program ignores the specification andcontinues 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 CONRC=4

Specified YKLCNSE is invalid The value assigned to the YKLCNSE parameter is

invalid. The program ignores the specification andcontinues processing.

You can specify a character string containing up toeight characters. Specify a correct value and retry theprocess.

YKT223E CONRC=4

Specified LOGPUT is invalid The value assigned to the LOGPUT parameter is invalid.

The program ignores the specification and continuesprocessing.

Valid values are either LOGR or SAM. Specify a valid

value and retry the process.

YKT226E CONRC=4

The specified SYSLOG valueis invalid.

The value specified for the SYSLOG parameter is invalid.

The program ignores the specification and continuesprocessing.

Valid values are either YES or NO. Specify a valid value

and retry the process.

YKT230E CONRC=4

The specified YKLCNS2 valueis invalid.

The value specified for the YKLCNS2 parameter is

invalid. The program will ignore the specification andcontinue processing.

A maximum of 8 characters can be specified. Specify acorrect value, and then retry the operation.

YKT232E CON

RC=12

The task is not APF-

authorized.

The dataset name of the Business Continuity Manager

load library is not registered in SYS1.PARMLIB.Alternately, the execution of the command has failedbecause authorized/unauthorized datasets co-existedwhile concatenating DD statements in the load libraryand they were handled as unauthorized datasets.

YKT299I CONSC=0

command command returncode=nnnn.

The command identified by command terminated withthe return code nnnn.

1-94 Messages






YKT400I CON BC Manager environmentvariables (version)

This message displays the Business Continuity Managerenvironment variables.

version

Version of Business Continuity Manager

YKT401I CON variable : value This message displays the Business Continuity Managerenvironment variables.

variable

Environment variables for Business ContinuityManager

• 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 ContinuityManager environment variables

YKT402I CON varname = value1 (symbol = value2)

This message displays the details of the BusinessContinuity Manager environment variables.

varname

Name of the Business Continuity Managerenvironment variable that is set by using theYKSETENV command

value1

Value of the Business Continuity Managerenvironment variable that is set by using theYKSETENV command

If no value has been set for the BusinessContinuity Manager environment variable by usingthe 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 ContinuityManager

This message displays the program product name.

Messages 1-95




Table 1-24 List of messages (message ID YKU0x)


YKU000T TSORC=48


For details, see the reason code in the YKU099I

message that will appear after this message. Forreason codes, see IKJPARS in the TSO/E Programming

Services.

YKU001E TSORC=48


YKU001E MSGSC=48 RC=48





period.

stem


YKU002E MSGSC=48


YKU002E MSGSC=48

GENID() value invalid The value assigned to the GENID parameter is invalid.

YKU002E TSORC=48



stem


YKU002E MSGSC=48


invalid.


ATTIME Specification attimeis 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 Manager Reference Guide.

attime

Time value assigned to the ATTIME parameter


SVOL(PROTECT|PERMIT)option required

Either PROTECT or PERMIT must be specified for the

SVOL parameter.


ATTIME Specification isbefore current time.

The time assigned to the ATTIME parameter is earlier

than the present time.


ATTIME Specification is morethan 45.5 days into thefuture.

The time assigned to the ATTIME parameter is more

than 65,535 minutes (45.5 days) past the presenttime.

YKU008E MSGSC=48


hexadecimal format.

YKU008E MSGSC=48

GENID() not valid hex The value specified in the GENID parameter is not in

hexadecimal format.

1-96 Messages





YKU009E MSGSC=48

Specify ATTIME() andDEVN() parm exclusively

You cannot specify the ATTIME parameter and the DEVN

parameter at the same time.

YKU009E MSGSC=48

Specify ATTIME() andVOLUNIT parm exclusively

You cannot specify the ATTIME parameter and the

VOLUNIT parameter at the same time.

YKU010E TSO

RC=40

REXX failure return

code=nnnn starting withvariable name



nnnn


YKU050E MSGSC=36 RC=48(attribute-value)




name

REXX variable name

attribute-value

REXX variable value


ATTIME parameter invalidfor TrueCopy Copy Group

The YKSUSPND command with the ATTIME parameter

specified was executed on a TrueCopy copy group. Thisparameter is invalid on TrueCopy copy groups.

Re-execute the YKSUSPND command without specifying

the ATTIME parameter.


Specify PURGE and DEVNparameter exclusively for URCopy Group

The PURGE and DEVN parameters cannot be specified

simultaneously for a Universal Replicator copy group.


Specify PURGE and VOLUNITparameter exclusively for URCopy Group

The PURGE and VOLUNIT parameters cannot be specified

simultaneously for a Universal Replicator copy group.


DRAIN parameter cannot bespecified for UR Copy Group

The DRAIN parameter cannot be specified for a

Universal Replicator copy group.


ATTIME and CANCELparameters are invalid forUR 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.




Check that the command can be executed on this copy

group, and then re-execute the command.

YKU099I TSO YKSUSPND command returncode=nnnn, reasoncode=rrrr

The YKSUSPND command terminated with the return



nnnn

Messages 1-97






Table 1-25 List of messages (message ID YKV0x)


YKV000T TSORC=48


For details, see the reason code in the YKV099I


YKV001E TSORC=48


YKV001E MSGSC=48 RC=48





period.

stem


YKV002E MSGSC=48


YKV002E TSORC=48



stem


YKV008E MSGSC=48


hexadecimal format.

YKV010E TSORC=40 REXX failure returncode=nnnn starting withvariable name

Access to the REXX variable identified by name failed.For details about the return code, see IKJCT441 in theTSO/E Programming Services.

nnnn


YKV050E MSGSC=36 RC=48(attribute-value)




name

REXX variable name

attribute-value

REXX variable value





1-98 Messages





YKV099I TSO YKRECVER command returncode=nnnn, reasoncode=rrrr

The YKRECVER command terminated with the return



nnnn


Table 1-26 List of messages (message ID YKW0x)


YKW001W TSO Timeout limit has expiredwithout group copy-groupreaching state state.

The specified copy group copy-group did not reach therequested status state within the specified time limit.

YKW002E TSO Primary Device(s) OFFLINE.Unable to receive IEA494Imessages.

Because the specified copy group contains a copy pairwith a P-VOL that is offline, the IEA494I message is

not issued.

Make all P-VOLs within the specified copy group online,and then re-execute the command.

YKW003E TSO Unexpected transition of group copy-group pair index device xxxx to state state.

One or more copy pairs identified by index within thespecified copy group copy group entered a statusidentified by state that does not lead to the requestedGOTO status. It is probable that this status transition

was triggered manually.

Conduct an investigation using the ISPF panelinterface'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 occurredduring execution of the YKLOAD command.

Conduct an investigation using the ISPF panelinterface's load function.

nnnn

Return code of YKLOAD command

For details, see the description for the YKLOAD

command in the Hitachi Business Continuity Manager Reference Guide.

YKW007E TSO YKQUERY error return code= nnnn.

The YKWATCH command uses the YKQUERY command to

establish the copy group status start baseline. An erroroccurred during execution of the YKQUERY command.

Conduct an investigation using the ISPF panel

interface's load function.nnnn

Return code of the YKQUERY command

For details, see the description for the YKQUERY


Messages 1-99





YKW008E TSO YKCONMSG error returncode = 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 Operatorattention.

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 errorencountered. Reason code =rrrr

An error occurred during execution of the YKWATCH

command. The YKCONMSG command issued within the

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-reason-message

The YKWATCH command detected an invalid startup

parameter.

YKW099I TSO Group copy-group hasreached the desired statestate.

This message is issued to notify the user that the copygroup identified by copy-group entered the requestedstatus identified by state.

copy-group

Copy group ID

Table 1-27 List of messages (message ID YKX0x)


YKX000T TSO Supplied parameters invalid Invalid parameters are specified.

For details, see the reason code in the YKX099I


YKX001E TSO No message MSG() supplied Nothing is assigned to the MSG parameter.

YKX001E MSGSC=48 No serial# SN() supplied Nothing is assigned to the SN parameter.

YKX002E TSO Messages MSG(stem) doesnot include trailing "."


stem


1-100 Messages





YKX010E TSORC=40




nnnn


YKX065W MSGSC=4 RC=0

Storage system serial-number Command DeviceDefinition Failed.(APID=apid )

The command device definition for the storage systemidentified by serial-number failed.

If multiple command devices are defined for thestorage system, processing continues.

Operate according to the I/O error messages issuedsimultaneously.

serial-number

Serial number of the corresponding storage system

apid

APID of the command device that failed to bedefined

YKX066E MSGSC=48 RC=48 Necessary Route List is notfound. The route list to be processed was not found.Check the ROUTE parameter, DAD parameter, route list

definition file, and command device definition filespecified in the YKLOAD command. Check that the

information corresponding to the storage system serialnumber specified in the YKBLDCMD command is set.

YKX099I TSO YKBLDCMD command returncode=nnnn, reasoncode=rrrr

The YKBLDCMD command terminated with the return



nnnn

Maximum among the severity codes returned

during command execution



YKX100T TSORC=48




YKX101E MSG

SC=48

No application id APID()

supplied

Nothing is assigned to the APID parameter.

YKX101E MSGSC=48

No command control addressCCA() supplied

Nothing is assigned to the CCA parameter.

YKX101E MSGSC=48

No control unit# CU()supplied

Nothing is assigned to the CU parameter.

Messages 1-101





YKX101E MSGSC=48

No device# DEVN() supplied Nothing is assigned to the DEVN parameter.

YKX101E TSORC=48


YKX101E MSG

SC=48

No serial# SN() supplied Nothing is assigned to the SN parameter.

YKX102E TSORC=48



stem


YKX103E MSGSC=48

Parameter combination isinvalid

The specified parameter combination is invalid.

For details about the combination of parameters, seethe description of the YKBLDCMD command or the

YKDELCMD command in the Hitachi Business Continuity

Manager Reference Guide.

YKX104E MSGSC=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 MSGSC=48

APID() not valid hex The value specified in the APID parameter is not in

hexadecimal format.

YKX108E MSGSC=48

CCA() not valid hex The value specified in the CCA parameter is not in

hexadecimal format.

YKX108E MSGSC=48

CU() not valid hex The value specified in the CU parameter is not in

hexadecimal format.

YKX108E MSGSC=48


hexadecimal format.

YKX110E TSORC=40




nnnn


YKX166E MSGSC=48

Necessary Route List is notfound.

The route list to be processed was not found.

Review the ROUTE and DAD parameters, route list

definition file, and command device definition file youspecified when executing the YKLOAD command.

YKX199I TSO YKDELCMD command returncode=nnnn, reasoncode=rrrr

The YKDELCMD command terminated with the return




YKX200T TSORC=48


1-102 Messages







YKX201E MSGSC=48

No command control addressCCA() supplied

Nothing is assigned to the CCA parameter.

YKX201E MSGSC=48

No control unit# CU()supplied

Nothing is assigned to the CU parameter.

YKX201E MSGSC=48

No device# DEVN() supplied Nothing is assigned to the DEVN parameter.

YKX201E TSORC=48


YKX201E MSGSC=48

No model SMODEL()supplied

Nothing is assigned to the SMODEL parameter.

YKX201E MSGSC=48


YKX201E MSGSC=48 No serial# SN() supplied Nothing is assigned to the SN parameter.

YKX201E MSGSC=48

No serial# SSN() supplied Nothing is assigned to the SSN parameter.

YKX202E TSORC=48



stem


YKX202E MSGSC=48

Results STEM(stem) doesnot include trailing "."


period.

stem


YKX203E MSGSC=48

Parameter combination isinvalid

The specified parameter combination is invalid.

For details about the combination of parameters, seethe description of the YKQRYDEV command in the

Hitachi Business Continuity Manager Reference Guide.

YKX204E MSGSC=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 ALIASvolume has been specified.

YKX208E MSGSC=48

CCA() not valid hex The value specified in the CCA parameter is not in

hexadecimal format.

YKX208E MSGSC=48

CU() not valid hex The value specified in the CU parameter is not in

hexadecimal format.

YKX208E MSGSC=48


hexadecimal format.

YKX210E TSORC=40



For details about the return code, see IKJCT441 in theTSO/E Programming Services

Messages 1-103





nnnn


YKX266E MSGSC=48


The route list to be processed was not found.

Review the ROUTE and DAD parameters, route list

definition file, and command device definition file youspecified when executing the YKLOAD command.

YKX299I TSO YKQRYDEV command returncode=nnnn, reasoncode=rrrr

The YKQRYDEV command terminated with the return


Table 1-30 List of messages (message ID YKY0x)


YKY001I CON AGENT STARTED (v .r .r [- zz ]) The Business Continuity Manager agent has started.

v

Version number

r

Revision number

zz

Exception

YKY002I CON INVALID INITIALIZATIONPARAMETER: parameter-name

The specified parameter has not been defined in theinitialization parameters, or the initialization parametershown as parameter-name is invalid. The BusinessContinuity Manager agent has been terminated.

Correct the initialization parameters and then restartthe Business Continuity Manager agent.

YKY003I CON INVALID CONTINUATION

LINE FOUND. PARAMETERSCAN TERMINATED

The initialization parameters contain the specification

for a continuation line, but no parameter is continued.The Business Continuity Manager agent will beterminated.

Correct the initialization parameters and then restartthe Business Continuity Manager agent.

YKY005I CON AGENT INITIALIZATIONFAILED P=termination-code

The Business Continuity Manager agent cannot start forthe reason indicated in the message that was displayedbefore this message.

Contact the center administrator. The centeradministrator must take appropriate action for themessage that was displayed before this message andthen restart the Business Continuity Manager agent.

termination-code (decimal number)

• 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.

1-104 Messages





• 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.

YKY008I CON INSUFFICIENT SPACEAVAILABLE FORINITIALIZATION

Initialization parameters analysis failed due to ashortage of work space. The Business ContinuityManager agent will be terminated.

Check, and, if necessary, revise the specification of theuser region in the job step in the Business ContinuityManager agent startup cataloged procedure, correctthe memory requirements, and then restart theBusiness Continuity Manager agent.

YKY016I CON TASK(task-ID)ABENDED,CODE=completion-code

A task terminated abnormally during the BusinessContinuity Manager agent start up. The BusinessContinuity Manager agent will be terminated.

task-ID

Name of the task

completion-code


YKY018I CON MODULE(load-module-name) NOT FOUND

The load module shown as load-module-name was notfound. The Business Continuity Manager agent will beterminated.

Make sure that the indicated load module was installedcorrectly.

YKY019I CON dd-name DD STATEMENTNOT 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 ContinuityManager agent.

YKY020I CON THE PROFILE IS NOTDEFINED IN THE FACILITYCLASS 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 BusinessContinuity Manager agent.

xxxxxxxx


YKY021I CON A NAME/TOKEN WRITEERROROCCURRED,RC=return-code,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





YKY022I CON THE SPECIFIED PREFIX ISBEING USED BY ANOTHERPROGRAM


Check the initialization parameters.

YKY051I CON AGENT ENDED The Business Continuity Manager agent wasterminated.

YKY052I CON AGENT IN SCHEDULEDSHUTDOWN The Business Continuity Manager agent terminationprocessing has begun.

YKY053I CON AGENT ABENDED The Business Continuity Manager agent terminatedabnormally.

If the cause is unknown, collect the ABEND dump inthe SYSABEND dump format and then contact customer

support for investigation.



YKY100I CON MODIFY COMMANDACCEPTED 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

• COMMAND: Indicates that an error was detected in

the command.

• OPERAND: Indicates that an error was detected in

the operand.

YKY103I CON COMMAND SYNTAX ERROR 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 WASCHANGED

The value of the initialization parameter has beenchanged. The parameter name is given in parameter-name.

YKY114I CON parameter-name= parameter-value

This message displays the current value of theinitialization parameter.

parameter-name

Initialization parameter name parameter-value

Initialization parameter value

YKY130I CON SESSION NO.=session-number

This message displays the TCP/IP session number. Thismessage is followed by the TCP/IP session information.

session-number

1-106 Messages





Session identification number

YKY131I CON host-type PORT= port-number HOST=IP-address

This message displays the port number and IP addressof the local or remote host. This message is followed bythe 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 STARTTIME=YYYY/MM/DDhh:mm:ss

This message displays the time the correspondingTCP/IP session was established. This message isfollowed by the TCP/IP session information.

YYYY/MM/DD hh:mm:ss

Time (local time)

YKY133I CON LAST data-direction-typeTIME=YYYY/MM/DDhh:mm:ss

This message displays the last transmission orreception time in the corresponding TCP/IP session.

data-direction-type

The direction of the data that was sent at the timedisplayed 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)


YKY300I SYS hh:mm:ss task-ID,TCPCONNECTION ACCEPTED

The TCP connection request was accepted. Informationabout the communication with the remote host isdisplayed in the YKY307I message.

hh:mm:ss

Message output time (local time)

task-ID

Messages 1-107





Number used to identify the processing task thatoutput the message

YKY301I SYS hh:mm:ss task-ID,TCPCONNECTION ENDEDNORMALLY

The TCP connection was released successfully.

hh:mm:ss


task-IDNumber used to identify the processing task thatoutput the message

YKY304I SYS hh:mm:ss task-ID,REQUESTDENIED,REASON=(reason-for-denial )

The request was received, but was denied.

hh:mm:ss


task-ID


reason-for-denial

• INVALID FORMAT: The format is invalid.

• VERSION MISMATCH: The version does not match.

YKY305I CON task-ID,TCP CONNECTIONLOST DURING EVENTPROCESSING,TCP-STATUS=(reason-for-disconnection)

The TCP connection was lost during TCP/IP processingfor the reason shown as reason-for-disconnection.

Determine the cause of disconnection from the remotehost.

task-ID


reason-for-disconnection

• 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.

YKY307I SYS hh:mm:ss task-ID,TCPCONNECTIONINFORMATION,REMOTE-HOST=IP-address,REMOTE-PORT=remote-port-number ,LOCAL-PORT=local- port-number

The TCP connection request was accepted.

Take appropriate action according to the message thatwas displayed before this message.

hh:mm:ss


task-ID


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





YKY315I CON task-ID,COMMUNICATION ERROR,@API[,request-name[,RC=response-code]][,EC=event-code][,SRC=local-IP-address:local-port-number][,DST=connection-target-IP-

address:connection-targetport-number]

A communication error was detected. The messagedisplays the request name, the target IP address:targetport number (decimal number), and the local IPaddress:local port number (decimal number).

The currently executing process is canceled. If necessary, check the YKY330I message that was

displayed immediately before this message todetermine the cause of the error.

task-ID


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 asrequest-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,COMMUNICATIONTIMED OUT

There is no response within the specified response waittime. The connection will be released.

Check the cause of the response timeout.

task-ID

Number used to identify the processing task that

output the message

YKY330I CON SOCKET API FAILURE(maintenance-information,request-type,return-code,error-number )

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 errorinformation.

Check the cause of the error and take appropriateaction. If TCP/IP has stopped due to the error, stop the

Messages 1-109





Business Continuity Manager agent. Once the error iscorrected, start the TCP/IP program, and then start theBusiness Continuity Manager agent.


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 therequest type and the error number (ERRNO), see the

Communications Server IP API Guide.

YKY362I CON RECEIVED DATA SIZEINVALID,DST=connection-target-IP-address:connection-targetport-number

The Business Continuity Manager agent received aninvalid size of data from connection-target-IP-address:connection-target-port-number . Thecorresponding receive processing will be stopped.

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.

YKY500I SYS RESULT OF UPDATING THECONFIGURATION FILE:

result

This message indicates whether the configuration filewas successfully updated.

If the configuration file failed to be updated, see theother error message that was output with this one andtake appropriate action.

result

Indicates the result.

• SUCCESS: The update succeeded.

• FAILURE: The update failed.

YKY501E XML Disk configuration definitionerror-type error. file

An error occurred in the disk configuration definitionfile. See the error-type, and then remove the error.After that, retry the operation from ReplicationManager.

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 notbeen broken.

1-110 Messages





• format: An XML format error

Make sure that the XML description does notcontain an error.

file

Name of the disk configuration definition file inwhich an error occurred

YKY502E XML Configuration file DELETEerror. file

During the update process for the configuration file, anerror occurred during the attempt to delete the oldconfiguration file. Remove the error, and then take thefollowing action:

1. If the configuration file in which the error occurredstill exists, delete it.

2. Change the name of the temporary file to thename indicated by file.

For details on names of temporary files, see thechapter that explains linking with ReplicationManager in the Hitachi Business Continuity Manager Installation Guide.

3. Restart the Business Continuity Manager agent,and then refresh the configuration file fromReplication Manager.

file

Name of the configuration file in which an erroroccurred

YKY503E XML Temporary file error-typeerror. file

An error occurred in the temporary file. Check whetherthe temporary file indicated by file exists. If the errortype is RENAME and the temporary file exists, change

the name of the temporary file to the name of theconfiguration file that you want to update. After that,restart the Business Continuity Manager agent, andthen refresh the configuration file from ReplicationManager. If the error type is something other thanRENAME 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 erroroccurred

YKY507E XML Routelist configuration fileerror error-type. file

An error occurred in the route list definition file. Seethe 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






Make sure that the file indicated by file has notbeen broken.



file

Name of the route list definition file in which anerror occurred



YKY600I CON INSUFFICIENT SPACEAVAILABLE. maintenance-information

The area allocation by the Business Continuity Manageragent failed. The Business Continuity Manager agentwill be terminated.

Increase the region size and then restart the Business

Continuity Manager agent.


Detailed information used for error analysis

YKY604I CON IRXJCL MODULEERROR,CODE=return-code

The IRXJCL routine returned an error with the return

code shown as return-code. The Business ContinuityManager 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 BusinessContinuity Manager agent. Check, and, if necessary,revise JCL, and then re-execute.

return-code

• 20: Processing failed. The EXEC processing was not

performed.

• 20021: The parameter list passed to IRXJCL was

invalid.

YKY605I CON IRXINIT MODULEERROR,CODE=return-code,R0=abnormal-termination-code-and-reason-code-for-abnormal-termination,PARM7=reason-code

The IRXINIT routine returned an error with the return

code shown as return-code. The Business ContinuityManager 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 mightoutput multiple messages reporting abnormaltermination. R0 includes the abnormal termination

1-112 Messages





code and the reason code for abnormaltermination.


IRXINIT returns the abnormal termination code set

in the two trailing bytes of R0. IRXINIT returns the

reason code for abnormal termination set in thetwo 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 detailsabout the abnormal termination code and reasoncode, see the MVS System Codes.

reason-code

For details about the reason code, see the TSO/E REXX Reference.

YKY606I CON IRXTERM MODULEERROR,CODE=return-code,R0=abnormal-

termination-code-and-reason-code-for-abnormal-termination

The IRXTERM routine returned an error with the

indicated return code. The Business Continuity Manageragent 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 thetwo trailing bytes of R0. IRXTERM returns the

reason code for abnormal termination set in thetwo 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 detailsabout the abnormal termination code and reasoncode, see the MVS System Codes.

YKY680I SYS hh:mm:ss task-ID,command ,RC=return-code[,text ]

A command that was issued by the Business ContinuityManager agent ended with return-code. Messages fordetected errors are output to text .

If the number of characters in the message output bythe command exceeds 126, it will be displayed onmultiple lines. The maximum number of message linesfor a single command is 10.

hh:mm:ss


task-ID

Identification number of the processing task towhich the message was output

command

Messages 1-113





Name of the command that the BusinessContinuity Manager agent executed

return-code

Return code from the command that the BusinessContinuity Manager agent executed

text

Message (maintenance information) that wasoutput by the command that the BusinessContinuity Manager agent executed

YKY699I CON AGENT FUNCTION ABENDCODE=Sxxx Uxxxx DATE=yy-mm-dd TIME=hh:mm:nn

ABENDED-MODULE=module-name C-DATE=module-creation-dateBASE=bbbbbbbb DISP=dddd

[CALLING-MODULE=module-

name C-DATE=y'y'.m'm'.d'd' BASE=bbbbbbbbDISP=dddd ]

PSW= pppppppp ppppppppILC=ll INTC= xx

REGISTERS AT TIME OFFAILURE


GR 04-07 contents-of-

register-4 contents-of-register-5 contents-of-register-6 contents-of-register-7



The main task or subtask terminated abnormally duringthe Business Continuity Manager agent processing. If the task cannot be recovered, the Business ContinuityManager agent will be terminated.

Contact the center administrator.

Sxxx (hexadecimal)

System completion code when the task terminatedabnormally

Uxxxx (decimal number)

User completion code when the task terminatedabnormally

yy-mm-dd

Date the task terminated abnormally

hh:mm:nn

Time the task terminated abnormally

module-name

Section name of the Business Continuity Manageragent 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 notcorrect.

module-creation-date

This is displayed in one of the following formats:

y'y'.m'm'.d'd' : Creation date of the moduleindicated by module-name

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

bbbbbbbb

Contents of the base register

dddd

• ABENDED-MODULE: Location where ABENDED-MODULEwas called, relative to the top of the module

• CALLING-MODULE: Location where CALLING-MODULE


pppppppp pppppppp

PSW during the abnormal termination

1-114 Messages





ll

Length of command during the abnormaltermination

xx

Interrupt code during the abnormal termination

Table 1-34 List of messages (message ID YKY7x - YKY9x)


YKY703E XML XML translation error: Thesent entity is not XML.

This is an XML error. The sent entity is not XML.

Check, and, if necessary, revise the request coding.

YKY704E XML End of request was detectedin the comment.

The end of the XML request was detected in thecomment.

Check, and, if necessary, revise the comment.

YKY705E XML End of request was detectedin an element.

The end of the XML request was detected in anelement.

Check, and, if necessary, revise the last element in theXML request.

YKY706E XML The number of elementsexceeded the allowed limit.

The number of element hierarchies exceeded thepermitted maximum value (16).

Check, and, if necessary, revise the request.

YKY707E XML The request version is amismatch.

The API version of the XML request is not supported.

Make sure that the version is supported by theBusiness Continuity Manager agent.

YKY713E XML An invalid element 'element-name' was specified in theXML request.

An invalid element-name was specified in the XMLrequest.

Check, and, if necessary, revise the specified request.

element-name

Element name

YKY714E XML An invalid parameter' parameter-name' wasspecified in the XML requestelement 'element-name'.

An invalid parameter-name was specified in the XMLrequest 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 XMLrequest element 'element-name'.

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





YKY716E XML An invalid child element'child-element-name' wasspecified in the XML requestelement ' parent-element-name'.

An invalid child element child-element-name wasspecified for the parent element name parent-element-name in the XML request. If the parent element namecannot be acquired, parent-element-name is set tonull.


parent-element-nameParent element name

child-element-name

Child element name

YKY717E XML A required element ismissing from the request.'element '

A required element is missing in the request.

Check, and, if necessary, revise the elementspecification in the request.

element

Name of the missing element

YKY718E XML A required parameter ismissing from the element'element-name' of therequest. ' parameter-name'

A required parameter is missing in the element.

Check, and, if necessary, revise the correspondingelement specification in the request.

element-name

Element name

parameter-name

Name of the required parameter

YKY719E XML There is a conflict withelement 'element-name'.

The end tag for the element shown as element-namedoes not have a paired start tag, or thecorrespondence between the end and start tags isinvalid.

Check, and, if necessary, revise the correspondingelement specification in the request.

element-name

Element name

YKY720E XML The request failed becausethe prefix ' prefix ' was notfound in the Agentinitialization parameter.

The requested prefix was not found among theBusiness Continuity Manager agent initializationparameters.

Check and if necessary revise the specified request.

prefix

Requested prefix

YKY726E XML Configuration file errorCGname 'cgname' error-type.

The copy group definition information could not beacquired because the error indicated by error-typeoccurred in the configuration file.

cgname

Copy group name

error-type


Make sure that the copy group cgnameconfiguration file exists.

1-116 Messages






Make sure that the configuration file of the copygroup cgname has not been broken.



• version: A version error

Make sure that the definition information version iscorrect.

• YKP2A: A definition-creation program error

The requested operation cannot be performedbecause the configuration file of the copy groupcgname was created by the mainframe agentYKP2A command.

YKY727E XML This request cannot beexecuted without validauthorization.

The user does not have authorization to perform therequested operation.

Change the MODE parameter in the initialization

parameters to EDIT, and then retry the operation.

YKY728E XML The information inconfiguration file wasupdated after you obtainedit.

The information in the configuration file has beenupdated since it was last obtained.

Refresh the configuration file from Replication Manager,and then retry the operation.

YKY729E XML Configuration file is invalid.file

The contents of the configuration file are invalid.

See the other error message that was output with thismessage, and then use Replication Manager to correctthe error. After that, update the configuration fileagain.

file

Name of the configuration file in which an errorwas detected

YKY730E XML INVALID CT Group isspecified.

The specified consistency group is invalid.

Make sure that the specified C/T group exists in thecopy group definition file.

YKY999E TSOCON

MFAgent cannot use thisREXX exec library.

A REXX script that cannot be used by mainframe agentwas executed.

Check the REXX Exec library connected to SYSEXEC dd

name.

Table 1-35 List of messages (message ID YKZ0x)


YKZ000T TSOSC=48

Supplied parameters invalid Invalid parameters were specified.

For details, see the reason code in the YKZ099I

message displayed after this message. For moreinformation about reason codes, see IKJPARS in theTSO/E Programming Services.

Messages 1-117





YKZ001E TSOMSG SC=48

No parameter-name()supplied

Nothing is assigned to the parameter identified by parameter-name.

YKZ002E MSGSC=48

parameter-name() does notinclude trailing "."

The last character of the string assigned to theparameter identified by parameter-name is not aperiod.

YKZ003E MSGSC=48 parameter-name() valueinvalid The value assigned to the parameter identified by parameter-name is invalid.

YKZ004E MSGSC=48

Device# DEVN() is notfound.

The device specified in the DEVN parameter does not

exist, or a device other than DASD or a PAV ALIASvolume has been specified.

YKZ008E MSGSC=48

parameter-name() not validhex

The value specified in the parameter identified by parameter-name is not in hexadecimal format.

YKZ010E MSGSC=48


An attempt to access the REXX variable identified byname has failed.


nnnn


YKZ050E MSG

SC=36 RC=36#

(attribute-value)

Invalid attribute name The value of the REXX variable with the name identifiedby 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 MSGSC=48 RC=48


The route list to be processed cannot be found.

Check the ROUTE parameter, DAD parameter, route list

definition file, and command device definition filespecified in the YKLOAD command execution.

YKZ099I TSOSC=0

command-name commandreturn code=nnnn, reasoncode=rrrr

The command identified by command-name terminatedwith the return code nnnn, and the reason code rrrr .This message is always displayed to indicate the returncode and the reason code.

nnnn


Table 1-36 List of messages (message ID YKZ10x - YKZ20x)


YKZ103E MSGSC=48

Parameters combination isinvalid


1-118 Messages





YKZ201E MSGCON PRT SC=44

RC=44#

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-executethe 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 wasexecuting when the error occurred

0: YKLOAD, tool, or any command

1: YKMAKE

2: YKSCAN3: 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 areobtained, the RC is 0.

YKZ202E MSGTSO CON SC=52RC=0

A Logical error occurred.(reason code=nnn,cmd= xxx , pos=yyy )

Logical contradiction occurred.


Reason code (maintenance information)

Messages 1-119







See the command code description in theexplanation 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 REXXread error occurred.

• If the nnn value is 40:

Check that the REXX program is running in theTSO/E environment, and then re-execute thecommand.

• If the nnn value is not 40:

Correct the configuration file (XML) and the valuesassigned to the parameters.

If the value is 52, it is probable that a

configuration file (XML) being edited is specified.nnn (decimal number)

Return code from the OS's REXX variable accessroutine

name (string)

REXX variable name




yyy (string)Maintenance information

# If the REXX variable that the system tried to readdoes 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.(return code=nnn, name=name, value=value,cmd= xxx , pos=yyy )

The command cannot be executed because an REXXwrite error occurred.


Expand the job execution area, and then re-execute the command.


Check that the REXX program is running in theTSO/E environment, and then re-execute thecommand.

• If the nnn value is not 32 or 40:

Correct the configuration file (XML) and the valuesassigned to the parameters.

1-120 Messages





If the error still exists after the above action has beentaken, contact your Hitachi Data Systemsrepresentative or authorized service provider.


Return code from the OS's REXX variable accessroutine

name (string)REXX variable name

value (string)

REXX variable value




yyy (string)


# If this message is output while the YKLOAD commandis being executed, the RC is 44.

YKZ205E TSORC=0

A Parameter error occurred.(detail=message-text ,cmd= xxx , pos=yyy )

The command cannot be executed because aparameter error occurred.

message-text (string)

Message text




yyy (string)


YKZ206E TSORC=0

An I/O error occurred.(detail=message-text ,cmd= xxx , pos=yyy )

The command cannot be executed because an I/Oerror occurred.


Message text




yyy (string)


YKZ207E MSGTSO CON SC=52

RC=44#

A Core process erroroccurred. (detail=message-text , cmd= xxx , pos=yyy )

The command cannot be executed because a Coreprocessing error occurred.


Message text

Messages 1-121





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 ) isinvalid

eeeee, nnn: Maintenance information

• If this message is displayed as maintenanceinformation (2):

ENTRYID ( eeeee ) for TYPE ( ttt ), LEVEL

( lll ) is invalid

eeeee, ttt , lll : Maintenance information




yyy (string)



YKZ208I TSOCON PRT RC=0

The Coreprocessing( 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 datehh:mm:ss.th (string)

GMT time

ttt (string)

GMT time format


1-122 Messages







yyy (string)


YKZ209I TSOCON PRT RC=0

The Coreprocessing( process ) ended.(DATE=yyyy /mm /dd ,TIME=hh:mm:ss.th,TOD=ttt , cmd= xxx ,pos=yyy )

Core processing is terminating.

process (string)

Processing name

yyyy /mm /dd (string)

GMT date

hh:mm:ss.th (string)

GMT time

ttt (string)

GMT time format




yyy (string)




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





YKZ211E MSGCON SC=40

RC=44#

A NAME/TOKEN write erroroccurred. (return code=nnn,name= name, cmd= xxx ,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

A FREEMAIN error occurred.(return code=nnn,cmd= xxx , pos=yyy )

A FREEMAIN error occurred.nnn (decimal number)

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 isnot output to the console, but is recorded in LOG and

TRACE. Processing will then continue.

YKZ215W MSGCON 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 GTFtraces for the USR trace (TRACE=USR). If the cause of the error is insufficient capacity in the trace buffer ortrace data set, increase the capacity, and then restartGTF.


Return code of the GTRACE macro


Event ID

lll (decimal number)

Length of trace data



1-124 Messages






yyy (string)


YKZ216E TSORC=0

The Trace table is notinitialized. (cmd= xxx ,

pos=yyy )

The trace table is not initialized.

xxx (decimal number)Command code of the command that wasexecuting when the error occurred


yyy (string)


YKZ217E MSGCON PRT SC=0RC=0

A Logger error occurred.(return code=nnn, reasoncode=mmm, name=name,cmd= xxx , pos=yyy )

A system logger service error occurred. Withoutoutputting the BCM log, processing for the CLIcommand 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 CONPRT RC=0

Output log count=nnn. The number of output log data records is nnn.


Number of log data records

YKZ219W CONRC=0

A LOAD error occurred.(return code=nnn, reasoncode=mmm, name=name,cmd= xxx , pos=yyy )

A LOAD macro error occurred.


Return code from the LOAD macro


Reason code from the LOAD macro (maintenanceinformation)

name (string)

Load module name



Messages 1-125






yyy (string)


YKZ220T MSG

SC=36 RC=36#

Copy type value null orinvalid.

The copy type is NULL or invalid.

Correct the configuration file, and then re-execute theYKLOAD command.

value

REXX variable value



YKZ220T MSG

SC=36 RC=36#

Group ID value null orinvalid.

The consistency group ID of the copy group structure isNULL or invalid.


value

REXX variable value# If this message is output while the YKLOAD command


YKZ220T MSG

SC=36 RC=36#

Minimum interface levelvalue 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 valuenull or invalid.

The number of copy pairs contained in the copy groupstructure is NULL or invalid. Correct the configuration

file, and then re-execute the YKLOAD command.

value

REXX variable value



YKZ220T MSGSC=36 RC=44

Number of Route dad-id isinvalid.

The number of routes related to dad-id is invalid.

Check whether the device address domain ID specifiedin 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 )

volume DEVN device-number invalid

The device number of the volume is invalid.

If the volume is not connected to the host in use, checkthe values of the DAD and ROUTE parameters specified

in the YKLOAD command and the contents of the route

list definition file.

1-126 Messages





volume

If volume is Primary: P-VOL.

If volume is Secondary: S-VOL.

device-number

Device number

pair-index See the pair index description in the explanation of the YKE003E message.



YKZ224E MSG

SC=8 RC=36#

( pair-index )

Primary device does notsupport TCA

TrueCopy Asynchronous cannot be used on a storagesystem with a P-VOL.

Use a device that supports TrueCopy Asynchronous.

pair-index



YKZ224E MSG

SC=12 RC=36#

( pair-index )

Secondary device does notsupport TCA

TrueCopy Asynchronous cannot be used on a storagesystem with an S-VOL.

Use a device that supports TrueCopy Asynchronous.

pair-index




YKZ225E MSG

SC=36 RC=36#

Some pairs in this group do

not support SI or TC GroupID membership.

This group contains copy pairs that do not support

ShadowImage or TrueCopy Group ID.Correct the configuration file, and then re-execute theYKLOAD command.



YKZ226E MSG

SC=36 RC=48#

stemTCA_MAP=TRK notsupported by some grouppairs

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=Nnot supported by somegroup pairs.

Some copy pairs in this group do not supportTCA_FLOWCONTROL=N.


stem

Messages 1-127





Stem name



YKZ228E MSG

SC=36 RC=36#

( pair-index )

Invalid pair attribute name =value

The value of the REXX variable is invalid.

Check that the value is specified according to thefollowing rules:

• The command control address must consist of 2digits.

• 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 MSGSC=0 RC=0

The time specified withATTIME has past. Thespecification of ATTIME isignored.

The time assigned to the ATTIME parameter has

elapsed. Processing will continue, ignoring thespecification of the ATTIME parameter.

YKZ230W MSG

SC=4 RC=4( pair-index )

Management for the relevant

volume was skipped. DEVNdevice#(SN ,CU#,CCA#)

Processing for the volume was skipped because the

status of the volume did not allow this command to beexecuted. If 0 is displayed in the location that indicates

the copy pair corresponding to the pair-index , multiplevolumes within the copy group have been skipped.

Change the status of the copy pairs to a status thatallows this command to be executed.

device#

Device number


displayed.

SN



displayed.

CU#

Control unit number


CCA#

1-128 Messages







pair-index


YKZ231E MSGSC=44 RC=44 Necessary Routelist or DEVNinformation is not found. The route list or device number information is missingalthough it is required for processing to continue.

Correct the value assigned to the ROUTE or DAD

parameter passed to the YKLOAD command.

YKZ232T MSGSC=36 RC=44

Number of Copy Groupsvalue invalid.

The number of copy groups is invalid.


value

Number of copy groups

YKZ233E MSG

SC=36 RC=36#

(attribute-value)



Correct the configuration file, and then re-execute the

YKLOAD command.

name

REXX variable name

attribute-value

REXX variable value



YKZ234E MSG

SC=36 RC=36#

Storage system model valuenull or invalid

The storage system model value is NULL or invalid.

Correct the storage system model in the configurationfile, 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





YKZ237E MSG

SC=36 RC=36#

Routelist attribute name isnull.

The command device group identified by name is notspecified.

Correct the contents of the configuration file.

name

REXX variable name



ATTIME SUSPEND remains inplace. Pair operation processis canceled.

Suspension initiated by YKSUSPND ATTIME is still in

effect. Copy pair operation is canceled.

Re-execute the command after YKSUSPND ATTIME

processing ends.


The specified Copy Grouphas no TrueCopySynchronous Group.

The specified copy group is not a TrueCopy copy groupwith consistency group ID specified.

Confirm that the copy group is a TrueCopy copy groupwith consistency group ID specified and is a TrueCopycopy group for which the Open/MF Consistencyattribute is not set. After that, re-execute the

command.

YKZ240E MSGSC=48

The specified pair was notfound in the Copy Group.(DEVN=P-VOL-device-number ,S-VOL-device-number )

A copy pair corresponding to the device numberspecified in the DEVN parameter was not found in the

copy group.

YKZ241W MSGSC=4 RC=0

No I/O issued volume is inCopy Group(s).

There is no volume eligible for I/O issuance.

Check the volume status, correct errors involved in theconfiguration or execution conditions if any, and thenre-execute the command.


The pair needs to beswapping, 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 copypairs has not been acquired.

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.


Supplied parameters invalid ATTIME or CANCEL is specified together with SVOL.

Correct the YKSUSPND command parameter values, and

then re-execute the command.


Serial number of storagesystem is not found inRoutelist.

The specified storage system does not exist in theroute list.

serial-number


1-130 Messages






CopyGroup attributecombination is invalid.

The combination of the specified command or theoperand, and copy group attribute is invalid.

Check the configuration file to make sure that theconfiguration allows command execution, and executethe command again.

YKZ246E MSG

SC=48 RC=48

This operation (operation)

does not support remotecommand.

This operation is not supported when a remote function

is in use.

operation

Operation name


STEM(stem) information forCore Processing is not found.

Information on the specified stem name is missing.

The YKLOAD command has not been executed or the

stem name does not match the stem name specifiedfor the YKLOAD command.

stem

Stem name


Necessary information forCore Processing is notstored. (STEM = stem)

Certain information required for CLI commandexecution has not been registered.

Execute the YKLOAD command to register the

information.

stem#

Stem name

# The (STEM = stem) portion is displayed only whenthe stem is obtained.

YKZ249E MSG

SC=48 RC=48#

( pair-index )

Specified DAD or ROUTE isinvalid.

The DAD or ROUTE parameter specified on the YKLOAD

command is invalid.

Correct the specification.

pair-index







A NAME/TOKEN delete erroroccurred. (return code=nnn,name= name, cmd= xxx ,pos=yyy )


TOKEN delete error occurred.


Return code from the NAME/TOKEN registrationroutine (IEANTCR)

name (string)

Name to be registered in the NAME/TOKEN service


Messages 1-131







yyy (string)


YKZ251E MSGSC=32 RC=32( pair-index )

DASD device device-number-1(device-number-2)management error,message-text . (code1 code2,cmd= xxx , pos=yyy )

Business Continuity Manager failed to complete therequested processing.

Processing will continue with this device skipped.

Check the status of the error device, correct any errorsrelated to the configuration or execution conditions,and then re-execute the command.

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



DASD device device-number-1(device-number-2)management error,message-text . (code1 code2,

cmd= xxx , pos=yyy )

Business Continuity Manager failed to complete therequested processing.

This device is skipped and processing continues.

Check the status of the error device, and fix theproblem in the configuration or execution condition if any.





1-132 Messages






Message text


Subcommand code


Error codeFor details about the error codes, see XXX.




yyy (string)



DASD device device-number-1(device-number-2)I/O error. (CC=code1CSW=code2 code3 code4code5 , cmd= xxx , pos=yyy ).

An I/O error occurred. Processing will continue withthis device skipped.

If a sense byte is set, the sense byte is indicated in theYKZ255E message.

When CC=3:

The corresponding device might not be configuredor connected.

When CC=0 and CSW= xxxxxx 0000 xxxx (DSB=00,

CSB=00) where x indicates a value:


When CC=0 and CSW=0000000006 xxxx where x

indicates a value:

MIH might have occurred or a logical path might

not be connected.





If the device number of the device to be operatedis not found, **** is displayed.

code1 (decimal number)

CC information


CSW information


Subcommand code


Completion code


Messages 1-133





Detailed code




yyy (string)


pair-index



DASD device device-number-1(device-number-2)I/O error. (CC=code1CSW=code2 code3 code4code5 , cmd= xxx , pos=yyy ).

An I/O error occurred. Business Continuity Managermight not support this device. Processing will continuewith this device skipped.

If a sense byte is set, the sense byte is indicated in theYKZ256E message.

When CC=3:


When CC=0 and CSW= xxxxxx 0000 xxxx (DSB=00,

CSB=00):


When CC=0 and CSW=00000000060000:

MIH might have occurred or a logical path mightnot be connected.



device-number-2 (string)The device to be manipulated

code1 (decimal number)

CC information


CSW Information.


Subcommand code


Completion code


Detailed code




1-134 Messages





yyy (string)



DASD device device-number-1(device-number-2)sense: diagnostic-information (cmd= xxx ,

pos=yyy )

Detailed information on the I/O error is displayed.



device-number-2 (string)The device to be manipulated


diagnostic-information (Hexadecimal number)

Sense byte information




yyy (string)Maintenance information

pair-index



DASD device device-number-1(device-number-2)sense: diagnostic-information (cmd= xxx ,pos=yyy )

Detailed information on the I/O error is displayed.





diagnostic-information (Hexadecimal number)

Sense byte information




yyy (string)



DASD device device-number-1(device-number-2)management error.

(Message type: code1Reason code: code2 Errorcode: code3 code4,cmd= xxx , pos=yyy )

Business Continuity Manager failed to complete therequested processing. Processing will continue with thisdevice skipped.

Check the status of the device involving the error,correct any errors related to the configuration orexecution conditions, and then re-execute thecommand.



Messages 1-135









Message type


Reason code


Error code

For details about the error codes, see XXX.


Subcommand code




yyy (string)


pair-index



DASD device device-number-1(device-number-2)management error.(Message type: code1Reason code: code2 Error

code: code3 code4,cmd= xxx , pos=yyy )

Business Continuity Manager failed to complete therequested processing. Business Continuity Managermight not support this device. Processing will continuewith this device skipped.

Check the status of the device involving the error,correct any errors related to the configuration orexecution conditions, and then re-execute thecommand.






Message type.


Reason code


Error code

For details about the error codes, see XXX.


Subcommand code


1-136 Messages







yyy (string)


YKZ259E MSG

SC=48 RC=48#

This product is alreadyexecuting.

The command cannot be executed because BusinessContinuity Manager is running for another panel orscript.






The volume has alreadyreached the target status.

Processing of some volumes was skipped because avolume that has already reached the target status

exists.

YKZ261E MSGCON SC=0 RC=0

The YKLOGnn DD statementis not specified.(cp= xxx :yyy )

No DD statement is specified in YKLOG01 or YKLOG02.

YKLOGnn

YKLOG01 or YKLOG02




yyy (string)



A YKLOGnn open erroroccurred. (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 executedwhen the error occurred


yyy (string)



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





text

Message acquired by the SYNADAF macro



See the command code description in the

explanation of the YKZ201E message.

yyy (string)



A YKLOGnn close erroroccurred. (rc=nnn,cp= xxx :yyy )

A close error occurred in YKLOG01 or YKLOG02.

YKLOGnn

YKLOG01 or YKLOG02


Return code from the CLOSE macro


Command code of the command that was

executing when the error occurred


yyy (string)



This operation (operation)does not support thereverse-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


A YKLOGnn DEVTYPE macroerror 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






yyy (string)


YKZ268E MSGCON 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 orimmediately after dataset allocation)

BBB

Valid file attribute




yyy (string)




YKZ270E MSGSC=36 RC=36(index1, index2)

Duplicate logical paths exist. The logical path definitions for index1 and index2 areduplicated.

Delete one of these definitions or make sure that theduplicated logical path definitions are correct, and thenre-execute the command.

index1

The index number of one duplicated logical path

index2

The index number of the other duplicated logical

path


Definition of xxxxxxxx doesnot match the actualconfiguration. DEVNdevice#(SN ,CU#,CCA#)

The group definition does not match the actual pairconfiguration. If GROUPID is displayed for unmatched

items or * is displayed on the device number, storage

system serial number, control unit number, or CCAnumber, there is a copy pair which is not defined in thecopy group definition parameter, and which belongs to

Messages 1-139





the same consistency group in the same control unit asthe P-VOL or S-VOL.

Check and correct the values of the copy groupdefinition 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#




Variable(s) were changed forthe number of paths or

portID.

For the port numbers and number of physical paths,update the REXX variable, which indicates the port

numbers and number of physical paths, to match thesettings on the storage system.


No path to be operated existwithin the range specified bythe supplied parameter.

No paths to be operated exist within the rangespecified by the parameter.

Check the parameters specified during commandexecution, the path set name specified during theYKLOAD command execution, and the attributes of the

path set (path type, shared attributes, storage systemserial numbers, and control unit numbers).

YKZ274E MSGSC=36 RC=36(index1, index2,index3)

Duplicate ports exist inFORWARD.

In the logical path definition for FORWARD index1, theindex2 and index3 port numbers are duplicated.

Delete one of the definitions or make sure that the

duplicated port numbers are correct, and then re-execute the command.

index1

Index number of the duplicated logical path

index2

Index number of one of the duplicated ports

1-140 Messages





index3

Index number of the other duplicated port

YKZ274E MSGSC=36 RC=36(index1, index2,index3)

Duplicate ports exist inREVERSE.

In the logical path definition for REVERSE index1, theindex2 and index3 port numbers are duplicated.

Delete one of the definitions or make sure that theduplicated port numbers are correct, and then re-

execute 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


Necessary Routelist or DEVNinformation is not found.

The route list or device number information, requiredfor 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, becausethis message is output when the volume for CU and CCA

specified in the path set definition file has not beenscanned.


Some of the storage systemsdo not support DKC typepaths.

A storage system using a path-controlled device orremote disk controller control contains an IFType,

which is not supported for disk controller-type pathcontrol.

In the configuration file, make sure that the storagesystem is controllable (that the first two digits of theIFType are X'11' or higher). Also, if scanning was not

performed after the storage system microcode was

replaced, perform another scan.YKZ277W MSGSC=4 RC=4

Some paths are in theNOPATH state.

There is a logical path without a physical pathestablished.


Some paths are in theMISMATCH state.

Logical paths were detected for which the portinformation stored in the REXX variable did not matchthe port information set on the storage system. Theport number or number of ports that have been set isincorrect.


Some paths are in theINVALID state.

Logical paths containing physical paths in the INVALIDstatus were detected from a storage system.

Table 1-41 List of messages (message ID YKZ28x)Message ID Message text Explanation and recommended actions


Primary volume's IFType islarger than Remote control'sIFType value.

The IFType of a storage system using the Remote DKC

Control Function is smaller than the IFType of the P-

VOL defined in the copy group. As such, the smaller of

Messages 1-141





the two will be used when each command is executed.Note that on some machine types, some functionalitymight be lost. Also, if a scan was not performed afterthe storage system microcode was replaced, performanother scan.

value

IFType value of the remote storage system


Secondary volume's IFTypeis larger than Remotecontrol's IFType value.

The IFType of a storage system using the Remote DKC

Control Function is smaller than the IFType of the S-

VOL 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 functionalitymight be lost. Also, if a scan was not performed afterthe storage system microcode was replaced, performanother scan.

value

IFType value of the remote storage system

YKZ281E MSG

SC=36 RC=36#1(StorageSystem's-IFType)

Some of the storage systems

do not support RemoteControl.

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 DKCControl 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 (orlater) where the first two digits of the IFType are

X'04' or higher.

YKZ282E MSG

SC=36 RC=36#1

Primary device IFType doesnot support UR.

Universal Replicator cannot be used on a storagesystem that has a P-VOL or uses the Remote DKCControl Function.

Use a device#2 that supports Universal Replicator. Also,if a scan was not performed after the storage systemmicrocode was replaced, perform another scan.

IFType

IFType value

#1



#2

The Universal Replicator is used in a storagesystem where the first two digits of the IFType are

X'11' or higher.

1-142 Messages





YKZ282E MSG

SC=36 RC=36#1

Secondary device IFTypedoes not support UR.

Universal Replicator cannot be used on a storagesystem that has an S-VOL or uses the Remote DKCControl Function.

Use a device#2 that supports Universal Replicator. Also,if a scan was not performed after the storage systemmicrocode was replaced, perform another scan.

IFType

IFType value

#1



#2

The Universal Replicator is used in a storagesystem where the first two digits of the IFType are

X'11' or higher.

YKZ283T MSG

SC=36 RC=36#

subCTGroupID value null orinvalid.

subCTGroupID in the copy group structure is either

NULL or invalid.

Correct the configuration file, and then execute theYKLOAD command.

value

REXX variable value



YKZ284T MSG

SC=36 RC=36#

UR_MirrorID value null orinvalid.

UR_MirrorID in the copy group structure is either NULL

or invalid.

Correct the configuration file, and then execute theYKLOAD command.

value

REXX variable value



YKZ285I MSGSC=0 RC=0(index )

This command cannot beexecuted 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. Onlythe 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 logicalpath, correct the configuration file and then executethe YKLOAD command.

index

Index number of the logical path without a port element

YKZ286E MSGSC=36 RC=36(index )

YKQRYPTH command cannotbe executed if the volume on

When the YKQRYPTH command is executed on a storage

system that has not been directly connected to thehost for the path set of an inter-control unit logicalpath, the volume belonging to the originally established

Messages 1-143





the CU type path has notbeen scanned.

inter- control unit of the inter-control unit logical pathmust have been scanned at least once.

Make sure that the volume belonging to the targetedcontrol unit has been scanned at least once, and thecontrol unit and command control address defined forthe path set are correct. If the command controladdress is not defined for the path set, from the Edit

Logical Path Definition panel, specify the commandcontrol address of the volume scanned in the targetcontrol unit for path control.

index

Index number of the logical path that cannot beexecuted

YKZ287T MSG

SC=36 RC=36#

UR_PathID value null orinvalid.

UR_PathID in the copy group structure is either NULL

or invalid. Correct the configuration file, and thenexecute the YKLOAD command.

value

REXX variable value

#If this message is output while the YKLOAD



Some of the storage systemsdo not support Path GroupID.

A path-controlled storage system does not supportpath group IDs (path IDs for which values other than00 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 storagesystem microcode was changed, perform a scan.

#

Path group IDs can be used for storage systemsfor which IFType is X'3333' or higher.




FROMCU() exceeds numberof CU that storage systemsupported.

The FROMCU has exceeded the maximum number of

control units that are supported by storage system.

Specify the maximum supported number of controlunits or less.

YKZ291I CONSC=0 RC=0

The log dataset is full.(DSN=ddd , cp= xxx :yyy )

The log dataset is full.

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 wasexecuting when the log dataset became full

1-144 Messages





See the description for the command code in theYKZ201E message.

yyy (string)


YKZ292I CONSC=0 RC=0

The log dataset wasswitched. (from=YKLOGmm,

to=YKLOGnn, job= jjj ,cp= xxx :yyy )

The log dataset was switched.

YKLOGmmPrevious log dataset (YKLOG01 or YKLOG02)

YKLOGnn

New log dataset (YKLOG01 or YKLOG02)

jjj

Job name


Command code for the command that wasexecuting when the log dataset was switched

See the description for the command code in theYKZ201E message.

yyy (string)



The specified value for thesystem symbol &YKLOGPT isinvalid.

The value specified for the &YKLOGPT system symbol is

invalid. The program continues processing whileassuming LOGR.

Revise the value specified for the &YKLOGPT system

symbol.


An error occurred whileacquiring the system symbol&YKLOGPT. (rc=rr )

An error occurred while acquiring the &YKLOGPT system

symbol. The program continues processing whileassuming LOGR.

Revise the value specified for the &YKLOGPT system

symbol.rr

The return code of the ASASYMBM macro


The version of thisconfiguration file is notsupported.

The version of this configuration file is not supported.


A JNLG is not registered inEXCTG. ( JNLG= jj ,MIRROR=m, EXCTG=e,SN=ssssssssssss)

The journal group is not registered in EXCTG for thestorage system.

The journal group might not be registered in EXCTGbecause 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 byexecuting 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





register the journal group in EXCTG for the storagesystem.

Note that, to register an existing journal group inEXCTG, 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 hascompleted normally.

Also, if you execute the YKQUERY command to obtain

the status while a copy pair in EXCTG is dissolved, theYKZ296E message sometimes appears when the

dissolving of the copy pair is detected at a differenttime from the dissolving of EXCTG, but this does notmean that an error has occurred. In this case, waituntil 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 copypairs in EXCTG whose copy direction is from theprimary site to the remote site are dissolved, the

journal groups whose copy direction is from the localsite to the remote site are also dissolved from EXCTGregistration. For example, if a Delta Resync is executedand 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 journalgroups whose status is DUPLEX and copy direction is

from the local site to the remote site are dissolvedfrom EXCTG registration. As a result, the YKZ296E

message is output if the YKQUERY command is executed

to obtain the status of Universal Replicator copy pairswhose copy direction is from the local site to theremote site. In this case, perform either of thefollowing operations to register journal groups inEXCTG for the storage system:

• Execute the YKMAKE HOLD command for Universal

Replicator copy pairs whose copy direction is fromthe 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 localsite to the remote site.

JNLG (string)

The journal type not being registered (the journaltype of the definition, rather than of the storagesystem)

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





Mirror ID (0-3)

e (decimal number)

EXCTG ID (0-3)

ssssssssssss (decimal number)



An error occurred whileadding JNLG to EXCTG.( JNLG= jj , MIRROR=m,EXCTG=e, SN=ssssssssssss,CDEV=cccc , CODE=nnnn)

An error occurred while registering the journal group toEXCTG.

Register the error code and determine the cause of theproblem. 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 EXCTGregistration 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 storagesystem)




The journal group number specified by theconsistency group ID or the sub consistency groupID (00-FF)

m (decimal number)

Mirror ID (0-3)

e (decimal number)

EXCTG ID (0-3)ssssssssssss (decimal number)


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


Timeout limit has expiredwhile waiting for EXCTGregistration process.

Processing is terminating because the timeout limit hasexpired while waiting for the EXCTG registration withthe YKEWAIT command.

Correct the timeout value or check that the status tobe monitored is correctly specified. Also, check if the journal group is registered to EXCTG.

The REXX variable is invalid (remains as it was prior tothe YKEWAIT command) if this message is output.

Messages 1-147






Definition of xxxxxxxx doesnot match the actualconfiguration. ( JNLG= jj ,MIRROR=m, EXCTG=e,SN=ssssssssssss,CDEV=cccc )

EXCTG information defined in the copy group andEXCTG information registered in the storage system donot match.

Correct the copy group definition file. This messagemight be output when the EXCTG ID specified in thecopy group definition is being used by another copygroup.

After removing the cause of the problem, execute theYKMAKE command again with a SELECT(COND)

specification to register the journal group to EXCTG.

This message is output until the corresponding EXCTGregistration 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 indicatedby e. However, it was not found in theconfiguration file.

JNLG (string)

The journal type registered to the storage system(the journal type of the storage system, ratherthan of the definition)




The journal group number registered to thestorage 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 registeredto the storage system (0000-3FFF)

FFFF is displayed for the supervisor disk controller.

1-148 Messages






YKZ300E MSGTSO SC=44RC=44

SVC # is null or invalid. The user SVC is not registered, or the &YKSVCNO

system symbol of the IEASYM xx parmlib member is

specified incorrectly.

When the user SVC is defined in SVCPARM:

Make sure that the &YKSVCNO system symbol of theIEASYM xx 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 theHitachi Business Continuity Manager Installation Guide.

YKZ301E CONRC=128

The task is not authorized toexecute the request. (reasoncode=reason)

The task is not authorized to execute a CLI command.The program will terminate abnormally with usercompletion code 128 or will return an error.

reason

Reason code

For details, see the description for that usercompletion code.

For details about how to set CLI command executionpermissions, see the Hitachi Business Continuity Manager Installation Guide.

YKZ310I SYS hh:mm:ss command This log data indicates that a CLI command has beenissued.

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 commandexecution

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

Hitachi Business Continuity Manager ReferenceGuide.

YKZ320E TSO Supplied parameters invalid. 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 parmexclusively.

The SEC and MIN parameters cannot be specified at the

same time.

Messages 1-149





YKZ330E TSOCON RC=64

command detected theservice service error. (returncode=r [, reason code=n][,abend code=a])

An error was detected in the REXX service.

command


service

Name of the REXX service or TSO/E service where

an error was detectedr (decimal number)

Return code from the REXX service or TSO/Eservice

For details, see the TSO/E REXX User's Guide orthe TSO/E Programming Services.

n (decimal number)

Reason code from the REXX service or TSO/Eservice


a (decimal number)

ABEND code from the REXX service or TSO/Eservice


YKZ331E TSORC=64

command terminated withan invalid return code. (r )

The CLI command terminated with an invalid returncode.

command


r

Return code that the CLI command created

YKZ332E TSORC=64 command detected thesystem abend during rexx-service processing.(code=sss, reason=rrrr )

An abnormal system termination was detected duringthe REXX service processing.

command


rexx-service

Name of the REXX service where the abnormalsystem termination was detected

sss (hexadecimal number)


For details, see the MVS System Codes.

rrrr (hexadecimal number)

Reason code

YKZ333E TSORC=64

command detected the userabend during rexx-serviceprocessing. (code=uuuu,reason=rrrr )

An abnormal user termination was detected during theREXX service processing.

command


rexx-service

1-150 Messages





Name of the REXX service where the abnormaluser termination was detected

uuuu (decimal number)

User completion code

For details, see the MVS System Codes.

rrrr (hexadecimal number)

Reason code

YKZ340T TSORC=48

Supplied parameters invalid. Invalid parameters are specified.

YKZ341E TSORC=48

No DEVN() supplied. Nothing is assigned to the DEVN parameter.

YKZ343E TSORC=48

DEVN() value invalid. The value specified in the DEVN parameter is invalid.

YKZ350T TSORC=16

Invalid parameters havebeen specified.

Invalid parameters have been specified.

YKZ351E TSO

RC=16

No error code has been

specified.

No error code has been specified.

YKZ352E TSORC=16

The specified error code isinvalid.

The specified error code is invalid. A possible cause isas follows:

• The specified value is not a four-digit hexadecimalvalue.

YKZ353E TSORC=64

Load module is not found. The load module cannot be found. Possible causes areas follows:

• The library dataset has not been concatenated.

• The module is protected by the RACF programcontrol function.

YKZ354I TSO

RC=8

A description for the

specified error code was notfound.

A description for the specified error code was not

found.

For details on error codes, see XXX. If the error code isnot listed in the manual, contact your Hitachi DataSystems representative or authorized service provider.


A dynamic configurationchange was detected duringspecified commandprocessing. DEVN device#

A dynamic change in an I/O configuration definitionwas detected during processing of the command.

Check the status of the device targeted by thecommand, correct any errors related to theconfiguration or execution conditions, and then re-execute the command.

device#

Device number being processed when a dynamic

change was detected in an I/O configurationdefinition

YKZ371I TSO YKENV command returncode=return-code.

The YKENV command terminated.

return-code

Return code issued by the YKENV command

Messages 1-151







param parameter cannot bespecified for copy-type CopyGroup.

The parameter indicated by param cannot be specifiedfor 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


Some of the storage systemsdo not support param.

The storage system which the command is issued onto,or the storage system which uses the Remote DKCControl Function, does not support the parameterindicated by param.

Use a device which supports the parameter indicatedby param. Also, if a scan has not been performed afterthe storage system microcode was replaced, performanother scan.

param (string)

The parameter name which is not supported


Unexpected transitionoccurred while adding JNLGto EXCTG. (CT ID= jj , sub CTID=kk , MIRROR=m,SN=ssssssssssss,STATE=nnnn)

The copy pair entered an unexpected status whileregistering the journal group to EXCTG.

Check that the status to be monitored is correctlyspecified. If the status is correctly specified, executethe YKQUERY command to determine the cause of the

problem and rectify the error.


The journal group number specified by theconsistency group ID (00-FF)

kk (hexadecimal number)

The journal group number specified by the subconsistency group ID (00-FF)

m (decimal number)

Mirror ID (0-3)


The storage system serial number

nnnn (string)

The status after the transition


No pair processed in CopyGroup(s).

The target copy pair was not found.

Check the volume status, correct errors involved in the

configuration or execution conditions if any, and thenre-execute the command.

If the YKMAKE SELECT(COND) command is issued on a

copy group container with EXCTG ID specified butwithout specifying the DEVN parameter, the EXCTG

registration I/O is issued even if this message isoutput.

1-152 Messages






An error occurred duringsuspension of UR ATTIME.(CT ID=ii , R-JNL= jj ,GENID=gg, ATTSTS=aa,SISTS=ss, URSTS=uu,CODE=eeee, TIME= ATTIME-suspend-time)

An error occurred while the suspend processing usingthe UR ATTIME Suspend Function was beingperformed.

Check the error information, and remove the cause of the error. If necessary, also check information such asthe storage system log. After that, use the YKSUSPND

command to cancel the ATTIME suspend time, andthen acquire a backup again.

ii (hexadecimal number)

consistency group ID for ShadowImage (00-7F)


Journal group number specified for the subconsistency group ID for the Universal Replicatorthat 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 Replicatorcopy pair was in the suspend status at the ATTIMEsuspend 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 UniversalReplicator 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





0002: Suspension is not possible because an error

occurred due to a problem in storage system.

ATTIME-suspend-time (GMT)

ATTIME suspend time: YYYYMMDD-HH:MM:SS.NNNNNN

YYYY : Year

MM : Month

DD: Day

HH : Hour

MM : Minute

SS.NNNNNN : Second


An unexpected UR pairstatus existed duringsuspension of UR ATTIME.(CT ID=ii , R-JNL= jj ,GENID=gg, ATTSTS=aa,SISTS=ss, URSTS=uu,CODE=eeee, TIME= ATTIME-suspend-time)

The status of the Universal Replicator copy pair wasinvalid while the suspend processing using the URATTIME 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.ii (hexadecimal number)



Journal group number specified for the subconsistency group ID for the Universal Replicatorthat 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 Replicatorcopy pair was in the suspend status at the ATTIMEsuspend 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





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, thesuspend processing has ended normally. Fordetails, 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


The timeout limit expiredduring the wait for thereservation time of the UR

ATTIME suspension. (CTID=ii , R-JNL= jj , GENID=gg,TIME= ATTIME-suspend-time)

The suspend processing started when the timeoutperiod elapsed because this period elapsed before the journal of the ATTIME suspend times for the ATTIME

suspend function was acquired, or the suspendprocessing started at the ATTIME suspend timebecause the Universal Replicator copy pair was in thesuspend status at the ATTIME suspend time.

Check the following because the backup for thespecified 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 andstatus during the suspension)

• Status of the Universal Replicator copy pairvolumes

After checking the results, if necessary, use theYKSUSPND command to cancel the ATTIME suspend

information, and then re-acquire the backup.

ii (hexadecimal number)


1-156 Messages






Journal group number specified for the subconsistency group ID for the Universal Replicatorthat links with ShadowImage





YYYY : Year

MM : Month

DD: Day

HH : Hour

MM : Minute

SS.NNNNNN : Second



YKZ410E MSG

SC=36 RC=36#1

Copygroup SUPFnc does notsupport UR Errorlevel.

You cannot use the Errorlevel attribute for this storagesystem.

In this case, use a device#2 that supports theErrorlevel attribute for Universal Replicator. Also, if ascan was not performed after the storage systemmicrocode was replaced, perform another scan.


Value for the version of the storage systemsupport function used in the copy group

(minimum)#1



#2

The Errorlevel for Universal Replicator can be usedin a storage system where the version of thestorage system support function is X'12' or higher.


ATOPT(UR) parameter isonly valid for SI CopyGroups with C/T ID.

The YKSUSPND command with the ATOPT(UR) parameter

specified was executed on a copy group other than aShadowImage copy group with the consistency groupID specified. The ATOPT(UR) parameter is only valid on

ShadowImage copy groups with the consistency groupID specified.


the ATOPT parameter, or with the ATOPT(NORMAL)

parameter specified.

Messages 1-157






This device SUPFnc does notsupport UR ATTIME.

The UR ATTIME Suspend Function is not available forthis storage system.

Use a device# for which the UR ATTIME SuspendFunction is supported. Also, if scanning was notperformed after the storage system microcode wasreplaced, perform another scan.


Value for the version of the storage systemsupport function used in the copy group(minimum)

# The UR ATTIME Suspend Function can be used in astorage system where the version of the storagesystem support function are X'14' or higher.

YKZ413E MSG

SC=36 RC=36#1

Copygroup SUPFnc does notsupport the timestamptransfer mode.

The timestamp transfer mode cannot be used with thisstorage system.

Use a device#2 that supports the timestamp transfermode. Also, if scanning was not performed after thestorage system microcode was replaced, perform

another scan.SUPFnc (hexadecimal number)


#1



#2

The timestamp transfer mode can be used for thestorage system models listed below. You cannotuse the timestamp transfer mode when using theLightning 9900V Series.

• USPs with a storage system support functionversion of X'16' or later.

• USP Vs with a storage system support functionversion of X'21' or later.

YKZ414E MSG

SC=36 RC=48#1

Copygroup SUPFnc does notsupport parameter-name.

The function indicated by parameter-name cannot beused.

Use a device#2 that supports the parameter-namefunction or configuration. Also, if scanning was notperformed after the storage system microcode wasreplaced, perform another scan.



parameter-name

Function or configuration that cannot be used:

- UR_CTTIMEMODE: Consistency time mode for

Universal Replicator

1-158 Messages





- 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 forUniversal Replicator

- GroupID=consistency-group-ID-of-TrueCopy-

copy-group-(hexadecimal-number): Consistencygroup ID of the TrueCopy copy group that exceedsX'7F'

#1



#2

The following are the storage system models forwhich you can use parameter-name:

• Consistency time mode for Universal Replicator:USPs with a storage system support functionversion 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 forTrueCopy: USP Vs with a storage system supportfunction version of X'22' or later, or VSPs and VSP

G1000s with a storage system support functionversion of X'31' or later

• 2DC configurations with HyperSwap and UniversalReplicator: USP Vs with a storage system supportfunction version of X'22' or later, and VSPs and

VSP G1000s with a storage system supportfunction version of X'31' or later

• Quick suspend mode for the UR ATTIME SuspendFunction: USP Vs with a storage system supportfunction version of X'23' or later

• Path group ID specification for UniversalReplicator: VSPs and VSP G1000s with a storagesystem support function version of X'33' or later

• Consistency group ID of the TrueCopy group thatexceeds X'7F': VSP G1000s with a storage system

support function version of X'40' or later


The device indicated by devnin the disk configurationdefinition file is on a storagesystem that differs from sn.

The device defined in the disk configuration definitionfile exists on a storage system that differs from thestorage system in the disk configuration definition file.For this reason, an NG Scan cannot be executed.

Check the device address domain ID specified in thedisk configuration definition file or the Set Defaultspanel. For details about the NG Scan, see the Hitachi Business Continuity Manager User Guide.

devn (hexadecimal number)

Messages 1-159





Device number defined in the disk configurationdefinition file

sn

Serial number of the storage system on which thedevice indicated by devn actually exists

YKZ416E MSG

SC=36 RC=36#1

Copygroup SUPFnc does not

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 differential-data management units to be specified. Also, if scanning was not performed after the storage systemmicrocode was replaced, perform another scan.


Value for the version of the storage systemsupport function used in the copy group(minimum)

#1



#2

TrueCopy data differential-data management unitscan be specified on storage systems with thefollowing versions of the storage system supportfunction:

• USPs with a storage system support functionversion of X'11' or later

• USP Vs with a storage system support functionversion of X'20' or later


This command is invalid forTrueCopy Copy Groupslinkaged with HyperSwap.

The command cannot be executed for TrueCopy copygroups with the HyperSwap attribute.

Execute the PPRC copy pair operation from TPC-R.YKZ418E MSGSC=48 RC=48

OPENMFUPDATE cannot usewith reverse-resync.

A resynchronization that reverses the copy directioncannot be performed with the OPENMFUPDATE parameter

specified. (The OPENMFUPDATE parameter is used to

modify the Open/MF Consistency attribute.)


This command is valid onlyfor copy group containerswith 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 containerswith an EXCTG ID. Confirm that the command can beexecuted on the copy group, and then re-execute thecommand.

YKZ420E MSG

SC=48 RC=48

EXCTG information could not

be acquired because noEXCTG ID is specified forcopying in the forwarddirection.

EXCTG information could not be acquired because no

EXCTG ID for copying in the forward direction isspecified. The YKQEXCTG command with the

TO(SECONDARY) parameter is valid only when copying

in the forward direction and for copy group containerswith an EXCTG ID for the forward direction. Check thecopy direction of the copy group container and theEXCTG ID direction (Forward or Reverse), and then re-execute the command.

1-160 Messages


EXCTG information could notbe acquired because noEXCTG ID is specified forcopying in the reversedirection.

EXCTG information could not be acquired because noEXCTG ID for copying in the reverse direction isspecified. The YKQEXCTG command with the

TO(PRIMARY) parameter is valid only when copying in

the reverse direction and for copy group containerswith an EXCTG ID for the reverse direction. Check thecopy direction of the copy group container and the

EXCTG ID direction (Forward or Reverse), and then re-execute the command.


This operation(operation) isnot available for a NonGen'ed volume.

This operation cannot be performed for a Non Gen'edvolume.

operation

Operation name

YKZ910I CON command This log message indicates that a CLI command wasissued.

command

The name of the issued CLI command and itsparameters

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 CLIcommand.

command

The name of the CLI command

rc

Return code of the CLI command

See the CLI command descriptions in the Hitachi Business Continuity Manager Reference Guide.

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 (< >) arevariables.

YK8310I PRT

REPORT SUMMARY: COPY GROUP : <cgid>

PREFIX : <prefix> DAD-ID : <dad> TYPE : <cgtype> GROUP STATUS : <status> SIMPLEX : <simplexct> MATCHING% : <match> PENDING : <pendingct> REVERSED% : <rev%> DUPLEX : <duplexct> ATTIME : <attime> SUSPEND : <suspendall> -STATUS : <attms> OTHER : <otherct>

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-to-primary

<attime>: ATTIME suspend time

<attms>: ATTIME suspend status

YK8312I PRT

REPORT DETAIL: COPY GROUP : <a> PREFIX : DAD-ID : <c> TYPE : <d>

PRI SEC MATCH C/T SUB C/T C/TVOLSER DEVN DIR DEVN STATUS RATE% ID C/T DELTA TIME

[ <e> <f> <g> <h> <j> <k> <l> <m> <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

¢ >: Primary-to-secondary

1-162 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- SEC- C/T C/T ID C/T SN SN DELTA TIME[ <c> <d> <e> <f> <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 : <a> PREFIX : DAD-ID : <c> TYPE : <d>

--- PRI %S ---- - SEC %S -- --- TIMERS --- C/T PRI- SEC- SFT RSF RSF WPR RSF RSF WPR TRANS OFLD RCUR CPND

ID SN SN TOT C/T TOT TOT C/T TOT KBYTES/S SEC MIN MIN[ <e> <f> <g> <h> <j> <k> <l> <m> <n> <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 remotecontrol 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 PRI %S SEC %S - PRI GB - - SEC GB - C/T SUB PRI- SEC- TRANS JNL-VOL JNL-VOL -- JNL-VOL -- JNL-VOL ID C/T SN SN KBYTES/S MET DAT MET DAT DAT DAT[ <e> <f> <g> <h> <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 remotecontrol 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 : <cycletime> WAITFOR TIMEOUT : <timeout> MSGLEVEL : <lvllog>,<lvlcons> ONACTIONERROR : <err-action> STOP AT STOPPOINT : <stoppt> SLEEP AT STOPPOINT : <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 messageappears 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 BCMMonitor

<cgsaact>: Startup action executed if the copy pair status for starting BCMMonitor 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 andcopy 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 theconfiguration file:

1. Count the CopyGroupContainer tags from the beginning of the file andidentify the CopyGroupContainer tag.

2. From the identified CopyGroupContainer tag, count the CopyPair tagsfrom the beginning of the file and identify the CopyPair tag.

3. The SerialNum under the identified CopyPair tag is the volume serialnumber to be processed.

User completion codes

The following table provides details about the user completion codes.

1-166 Messages



Table 1-46 User completion codes

Completion codes Explanation

U0003 There is a problem with the issued CCW.

The version of the registered user SVC might be old. Check whether the latest userSVC 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 mightnot have been given permissions to view the profile required for executing the CLIcommand, 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: theSTGADMIN.YKA.BCM.COMMANDS profile or the STGADMIN.YKA.BCM.YKQUERY profile

- A command that cannot be executed: a CLI command for viewing theoperations 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: theSTGADMIN.YKA.BCM.COMMANDS profile

- A command that cannot be executed: a CLI command for operating copypairs, 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 aproblem 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

Storage system sense byte information 2-1




Details of error codes

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 thistable is output, contact your Hitachi Data Systems representative orauthorized 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

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

2026 An SI copy pair cannot beresynchronized (QuickRestore) becauseall of the following conditions exist:

• System option mode 561 is ON.

• The P-VOL and S-VOL are externalvolumes.

• The P-VOL and S-VOL CacheModesetting are different.

Y N N N N N N N

2043 The specified SI copy pair cannot beresynchronized (ReverseCopy orQuickRestore) because the P-VOL of

the SI copy pair is a UR copy pairvolume for which multiple mirror IDsare defined.

Y N N N N N N N

2044 The specified SI copy pair cannot becreated because the S-VOL of the SIcopy pair is a UR copy pair volume forwhich multiple mirror IDs are defined.

Y N N N N N N N

2060 An SI copy pair cannot be made orresynchronized. The reason might beone of the following:

• The SI copy pair status cannot bechanged because the P-VOL has

already been made into a copy pairby using UR.

• The P-VOL is a journal volume.

Y N N N N N N N

2061 An SI copy pair cannot be made. Thereason might be one of the following:

• The S-VOL has already been madeinto a copy pair by using UR.

Y N N N N N N N

2-2 Storage system sense byte information




Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The S-VOL is a journal volume.

2067 An SI copy pair cannot beresynchronized because the specifiedvolume is part of a TC and UR commonvolume configuration and neither theTC nor UR copy pair are in the suspendstatus.

Y N N N N N N N

2078 An SI copy pair could not be madebecause the status of the P-VOL for thespecified SI copy pair does not meet allof the following conditions:

• The S-VOL is part of a delta resyncpair

• The delta resync pair is in the HOLD

status

• A UR copy pair that is linked with

the delta resync pair is in thesuspend status

Y N N N N N N N

2079 The SI copy pair could not be madebecause the specified S-VOL of SI copypair is a part of a delta resync pair.

Y N N N N N N N

2086 The command cannot be executedbecause initialization processing for theSI copy type is being performed.

Y N N N N N N N

2089 An SI copy pair cannot beresynchronized (QuickRestore) becausethe P-VOL of the specified SI copy pairis being quick formatted.

Y N N N N N N N

208A An SI copy pair cannot beresynchronized (QuickRestore) becausethe S-VOL of the specified SI copy pairis being quick formatted.

Y N N N N N N N

2097 The SI copy pair cannot beresynchronized (QuickRestore) becausethe copy pair is made up of an HDPzvolume and a non-HDPz volume.

Y N N N N N N N

20A2 A copy pair could not be createdbecause the HDPz volume specified forthe P-VOL of the SI copy pair is beingexpanded.

Y N N N N N N N

20A3 A copy pair could not be createdbecause the HDPz volume specified forthe S-VOL of the SI copy pair is beingexpanded.

Y N N N N N N N

20B4 A copy pair could not be createdbecause the HDPz volume specified for

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

the P-VOL of the SI copy pair is notassigned to the pool.

20B5 A copy pair could not be createdbecause the HDPz volume specified forthe S-VOL of the SI copy pair is notassigned to the pool.

Y N N N N N N N

20BD A copy pair could not be createdbecause the P-VOL of the specified SIcopy pair is an emulation type (3390-V) that is not supported.

Y N N N N N N N

20BE A copy pair could not be createdbecause the S-VOL of the specified SIcopy pair is an emulation type (3390-V) that is not supported.

Y N N N N N N N

20C5 An SI copy-pair operation cannot beperformed because power-off processing is in progress.

Y N N N N N N N

20C9 If the emulation type of the P-VOL of the specified SI copy pair is 3390-A, acopy pair could not be created for oneof the following reasons:

• No mainframe Fibre Channeladapter is installed.

• All of the Mainframe Fibre Channeladapters are blocked.

Y N N N N N N N

20CA If the emulation type of the S-VOL of the specified SI copy pair is 3390-A, acopy pair could not be created for one

of the following reasons:


• All of the Mainframe Fibre Channeladapters are blocked.

Y N N N N N N N

20D0 A copy pair could not be createdbecause the pool of the HDPz volumespecified for the P-VOL of the SI copypair is being initialized.

Y N N N N N N N

20D1 A copy pair could not be createdbecause the pool of the HDPz volumespecified for the S-VOL of the SI copy

pair is being initialized.

Y N N N N N N N

20D6 A copy pair could not be created forone of the following reasons:

• The P-VOL of the specified SI copypair is being used for FlashCopySE.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The P-VOL of the specified SI copypair is a TSE-VOL.

20D7 A copy pair could not be created forone of the following reasons:

• The S-VOL of the specified SI copypair is being used for FlashCopySE.

• The S-VOL of the specified SI copypair is a TSE-VOL.

Y N N N N N N N

20E4 A copy pair with a C/T group ID couldnot 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 URcopy pair.

• The P-VOL is being used byanother program product as the P-VOL of an SI copy pair with a C/Tgroup ID.

Y N N N N N N N

22F6 An SI copy pair cannot be madebecause the specified P-VOL is an S-VOL for FlashCopy.

Y N N N N N N N

22F7 An SI copy pair cannot be madebecause the specified S-VOL is either aP-VOL or S-VOL for FlashCopy.

Y N N N N N N N

22F9 An SI copy pair cannot beresynchronized (by eitherReverseResync or QuickRestore)because the volume is of a commonvolume configuration consisting of a P-VOL of SI and a P-VOL of FlashCopy.

Y N N N N N N N

Table 2-2 Details of error codes 23xx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

2301 The command could not be executedbecause an SI program product has not

been installed.

Y N N N N N N N

2309 The command could not be executedbecause an attempt was made to makea copy pair that exceeded themaximum number of SI copy pairs.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

2310 An SI copy pair status cannot bechanged because the status of the copypair does not allow a status transition.The reason may be one of the

following:

• The combination of the requestcommand and the status of thespecified copy pair do not allow thestatus transition. For informationon combinations, see theShadowImage for IBM z/OS User Guide.

• The copy pairs cannot besuspended collectively because acopy pair that is not in the DUPLEX

status is among the specified copypairs.

• The copy pairs cannot besuspended collectively because acopy pair for which transition is notpossible is among the specifiedcopy pairs.

• An ATTIME suspend time cannot beset because a copy pair that is notin the PENDING or DUPLEX status is

included in the C/T group.

• The ATTIME suspend time cannotbe set because the specified C/Tgroup contains a copy pair thatwas created by using RAID

Manager to specify the SI C/Tgroup ID.

If the reason why the copy pair statuscannot be changed is not one of theabove, the ATTIME suspend timecannot be set. Execute the YKSUSPND

command with the CANCEL parameter

specified, and then set the ATTIMEsuspend time again.

Y N N N N N N N

2311 The copy pair cannot be dissolvedbecause the copy pair is in the SIMPLEX

status.

Y N N N N N N N

2312 The command could not be executedbecause the S-VOL of an SI copy pair isonline.

Y N N N N N N N

2313 An SI copy pair cannot be suspendedbecause the copy pair is in the Splitstatus.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

2314 An SI copy pair cannot be madebecause the copy pair is in the Splitstatus.

Y N N N N N N N

231B An SI copy pair status cannot bechanged. The reason might be one of the following:

• The status of another copy pairthat shares the P-VOL is SUSPVS.

• There is a FlashCopy pair thatshares the P-VOL.

Y N N N N N N N

231F An SI copy pair cannot beresynchronized because the P-VOL isonline.

Y N N N N N N N

232A An SI copy pair cannot be madebecause the charging limit of the

program product was exceeded.

Y N N N N N N N

2331 An SI copy pair cannot be made. Thereason might be one of the following:

• The volume size of P-VOL differsfrom that of S-VOL.

• The shared memory capacity isinsufficient for copy pair creation.

Y N N N N N N N

2332 An SI copy pair status cannot betransitioned because the maximummultiplicity of the copy pairs for the P-VOL was exceeded.

Y N N N N N N N

2333 An SI copy pair cannot be suspended ordissolved because the copy pair is inthe SIMPLEX status.

Y N N N N N N N

2334 An SI copy pair cannot be madebecause the emulation type of thespecified volume is not supported.

Y N N N N N N N

2335 An SI copy pair cannot be madebecause the RAID level or emulationtype of the volume is not supported.

Y N N N N N N N

2336 An SI copy pair status cannot bechanged because the combination of the drive emulation type of the P-VOLand S-VOL is not appropriate.

Y N N N N N N N

2337 An SI copy pair status cannot bechanged because the volume specifiedto be the P-VOL is already the S-VOL.

Y N N N N N N N

233A An SI copy pair cannot beresynchronized because the copy pair isin the SIMPLEX status.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

233F An SI copy pair cannot beresynchronized with Reverse specifiedbecause a TC or TCA copy pair is not inthe suspend status.

Y N N N N N N N

2343 An SI copy pair status cannot bechanged because the volume specifiedto be the S-VOL is already the S-VOL of an SI copy pair.

Y N N N N N N N

2344 An SI copy pair status cannot bechanged because the status of the copypair does not allow the statustransition. The reason might be one of the following:

• The volume specified to be the S-VOL is already the P-VOL of an SIcopy pair.

• The volume specified to be the S-VOL is in the SIMPLEX status.

Y N N N N N N N

2346 An SI copy pair status cannot bechanged because the volume specifiedto be the S-VOL is already the P-VOL of a TC or TCA copy pair.

Y N N N N N N N

2347 An SI copy pair status cannot bechanged because the volume specifiedto be the S-VOL is already the S-VOL of a TC or TCA copy pair.

Y N N N N N N N

234A An SI copy pair status cannot bechanged because the volume specified

to be the S-VOL is already the P-VOL of an SI copy pair or the one forFlashCopy.

Y N N N N N N N

2351 An SI copy pair status cannot bechanged because the same volume wasspecified for the P-VOL and the S-VOL.

Y N N N N N N N

2352 An SI copy pair cannot beresynchronized with Reverse or Quickspecified because the P-VOL and S-VOLare online.

Y N N N N N N N

2353 An SI copy pair cannot be dissolvedbecause the copy pair is in the V-Split

status.

Y N N N N N N N

2354 An SI copy pair cannot beresynchronized because the copy pair isin the Pending status.

Y N N N N N N N

2358 An SI copy pair status cannot bechanged. The reason might be one of the following:

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The status of another copy pairthat shares the P-VOL or S-VOL isTRANS.

• There is a FlashCopy pair that

shares the P-VOL or S-VOL.

235B An SI copy pair cannot beresynchronized with Reverse or Quickspecified because the P-VOL is the P-VOL of a TC or TCA copy pair that isnot in the suspend status.

Y N N N N N N N

235C An SI copy pair cannot beresynchronized with Reverse or Quickspecified because the P-VOL is the S-VOL of a TC or TCA copy pair that isnot in the suspend status.

Y N N N N N N N

235D An SI copy pair cannot be

resynchronized with Reverse or Quickspecified because the S-VOL is the P-VOL of a TC or TCA copy pair that isnot in the suspend status.

Y N N N N N N N

2370 An SI copy pair status cannot bechanged because the specified volumedoes not exist.

Y N N N N N N N

2371 An SI copy pair cannot be madebecause the volume specified to be theP-VOL is a system residence volume.

Y N N N N N N N

2373 An SI copy pair status cannot bechanged because the volume specified

to be the P-VOL is a command device.

Y N N N N N N N

237B An SI copy pair cannot beresynchronized (QuickRestore) becauseall of the following conditions exist:

• The specified P-VOL is an internalvolume.

• The specified S-VOL is an externalvolume.

• The specified P-VOL has a sharedconfiguration with the P-VOL of theTC.

Y N N N N N N N

2381 An SI copy pair cannot be madebecause the volume specified to be theS-VOL is a system residence volume.

Y N N N N N N N

2383 An SI copy pair status cannot bechanged because the volume specifiedto be the S-VOL is a command device.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

2390 An SI copy pair cannot be madebecause the volume specified to be theP-VOL is being quick formatted.

Y N N N N N N N

2391 An SI copy pair cannot be madebecause the volume specified to be theS-VOL is being quick formatted.

Y N N N N N N N

2394 An SI copy pair cannot be madebecause the number of copy pairs inthe specified C/T group exceeded themaximum number of copy pairs in aC/T group.

Y N N N N N N N

2395 An SI copy pair status cannot bechanged because the volume specifiedto be the SI P-VOL is in the ReverseResync status with another copy pairwhich shares the P-VOL.

Y N N N N N N N

2398 An SI copy pair cannot beresynchronized (including Reverse)because the copy pair is not in the Splitstatus.

Y N N N N N N N

2399 An SI copy pair status cannot bechanged because another copy pairthat shares the P-VOL or S-VOL is aFlashCopy pair or not in the suspendstatus.

Y N N N N N N N

239A An SI copy pair cannot beresynchronized (including Reverse)because the specified P-VOL is the P-

VOL of a TC copy pair.

Y N N N N N N N

239B An SI copy pair cannot beresynchronized (including Reverse)because the specified P-VOL is the S-VOL of a TC copy pair.

Y N N N N N N N

239C An SI copy pair cannot beresynchronized (including Reverse)because the specified S-VOL is the P-VOL of a TC copy pair.

Y N N N N N N N

239D The command cannot be executedbecause the specified P-VOL isprotected by the LDEV guard.

Y N N N N N N N

239E The command cannot be executedbecause the specified S-VOL isprotected by the LDEV guard.

Y N N N N N N N

23A0 The command could not be executed.The reason might be one of thefollowing:

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The specified volume isinconsistent with the volume thatreceived the command.

• A copy pair exists that shares the

specified C/T group ID and TC S-VOL, and the ATTIME suspendfunction cannot be executed.

• The ATTIME suspend functioncannot be executed because the P-VOL is a Non Gen'ed volume.

23BB An SI copy pair cannot be madebecause the LDEV security is set for thespecified S-VOL.

Y N N N N N N N

23EF An SI copy pair cannot be deletedbecause the specified SI copy pair is inSUSPVS status.

Y N N N N N N N

23F1 The command could not be executedbecause the specified C/T group ID isout of the valid range.

Y N N N N N N N

23F2 The command cannot be executed. Thereason might be one of the following:

• The specified C/T group ID is notregistered.

• The copy pair is in the SIMPLEX

status.

• The specified C/T group contains acopy pair that was created byusing RAID Manager to specify the

SI C/T group ID.

Y N N N N N N N

23F3 The command could not be executedbecause the specified ATTIME suspendtime is in the past.

Y N N N N N N N

23F4 The command used to request that theATTIME suspend time information beacquired could not be executed due tothe following reasons:

• The command was issued to the P-VOL.

• The status of the copy pair isSIMPLEX.

Make sure that the command isproperly issued and the copy groupdefinition file has been correctlyconfigured.

Y N N N N N N N

23F5 The command could not be executedbecause the ATTIME suspend time isalready set. If you want to change the

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

configuration of the copy groupdefinition file, first cancel ATTIMEsuspension.

23FF An SI copy pair status cannot bechanged because the specified SI copypair status does not allow the status tobe changed.

Y N N N N N N N


Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

3613 Registration to EXCTG has failedbecause the specified arbitration

command device is not an arbitrationcommand device.

N N N Y N N N N

3614 Registration to EXCTG has failed. Thereason might be one of the following:

• The specified arbitration commanddevice is not defined.

• The specified arbitration commanddevice is blocked.

N N N Y N N N N

3616 Registration to EXCTG has failedbecause the journal group to beregistered is also subject to deletionfrom EXCTG.

N N N Y N N N N

3617 Registration to EXCTG has failedbecause the status is currently beingchanged.

N N N Y N N N N

3618 Registration to EXCTG has failedbecause M-JNL groups and R-JNLgroups co-exist within the EXCTG.

N N N Y N N N N

3621 Registration to EXCTG has failedbecause the number of journal groupsexceeded the maximum number thatcan be assigned to the specifiedarbitration command device. Retry theoperation using another arbitration

command device.

N N N Y N N N N

3640 Registration to EXCTG has failed due toa temporary path failure. Please retrythe operation.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

3641 The EXCTG cannot be registeredbecause the specified EXCTG ID, journal group number, and mirror IDare invalid.

N N N Y N N N N

3642 Registration to EXCTG has failedbecause the journal group attribute isincorrect.

N N N Y N N N N

3680 Registration to EXCTG has failedbecause the journal group to beregistered was not found.

N N N Y N N N N

3681 Registration to EXCTG has failedbecause the mirror ID of the journalgroup to be registered is different fromthe specified mirror ID.

N N N Y N N N N

3682 Registration to EXCTG has failed

because the attribute of the journalgroup to be registered is different fromthe attribute of the EXCTG.

N N N Y N N N N

3685 Registration to EXCTG has failedbecause the specified storage systemmodel name is invalid.

N N N Y N N N N

3686 Registration to EXCTG has failedbecause the journal group to beregistered is already registered toanother EXCTG.

N N N Y N N N N

3688 Registration to EXCTG has failed forone of the following reasons:

• The mirror status of the specified journal group is not Active or

Stop.

• The Disaster Recovery Extendedprogram product is not installed.

• The specified journal group isalready registered in a UROpen/MF consistency group.

• The specified journal group is setto be used in 3DC (URxUR)configurations.

N N N Y N N N N

3689 Registration to EXCTG has failed

because the attribute of the journalgroup to be registered is different fromthe attribute of the EXCTG.

N N N Y N N N N

368A Registration to EXCTG has failedbecause the timer type of the journalgroup to be registered is not System.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

3694 Registration to EXCTG has failedbecause the combination of the serialnumber and device on the specifiedarbitration command device is

incorrect.

N N N Y N N N N

3695 Registration to EXCTG has failedbecause the journal group to beregistered is an open-system journalgroup.

N N N Y N N N N


Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

3703 A UR copy pair cannot beresynchronized (with the PREPARE

parameter) because the journal volumehas PIN data.

N N N Y N N N N

3704 The UR copy pair cannot be madebecause the emulation type for thespecified M-JNL group does not matchthat of the R-JNL group.

N N N Y N N N N

3705 The command for delta resync cannotbe executed because the device on theS-VOL does not support delta resync.

N N N Y N N N N

3706 A delta resync pair cannot be madebecause the command target volume isthe S-VOL of a TC copy pair and thecopy pair status is not Duplex.

N N N Y N N N N

3707 A delta resync pair cannot be executed.The reason might be one of thefollowing:

• The command target volume is theP-VOL of a TC copy pair and thecopy pair status is not Duplex.

• The command target volume is theS-VOL of a TC copy pair and thecopy pair status is not SSWS.

N N N Y N N N N

3709 The delta resync command cannot beexecuted because there are no UR copypairs with a mirror ID other than theone specified for the delta resync pairin the specified R-JNL group.

N N N Y N N N N

370B A UR copy pair cannot beresynchronized (with the DELTAJNL

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

parameter) because the specified P-VOL is not in the HOLD status or

HOLDTRNS status. Alternatively, a UR

copy pair cannot be resynchronized

(with the ALLJNL parameter) becausethe specified P-VOL is not in the HOLD

status, HOLDTRNS status, or NODELTA

status.

370C A UR copy pair cannot be made orresynchronized. The reason might beone of the following:

• The specified M-JNL group or R-JNLgroup does not allow the status tobe changed.

• The specified M-JNL group or R-JNLgroup is in progress of the statusto be changed.

N N N Y N N N N

370D A UR copy pair cannot beresynchronized (with the PREPARE

parameter) because the journal volumecannot be accessed.

N N N Y N N N N

3711 A UR copy pair cannot beresynchronized (with the PREPARE

parameter) because the journal volumeis blocked.

N N N Y N N N N

3720 A UR copy pair cannot be made orresynchronized because the journalvolume in M-JNL is blocked.

N N N Y N N N N

3726 A UR copy pair cannot be madebecause the volume specified to be theP-VOL is a system residence volume.

N N N Y N N N N

3728 A UR copy pair cannot be madebecause an unsupported volume wasspecified when making a copy pairbetween different models.

N N N Y N N N N

3729 A UR copy pair that is to be linked withTC cannot be made because theDisaster Recovery Extended programproduct has not been installed in theMCU.

N N N Y N N N N

3734 The UR copy pair cannot be recreatedbecause the P-VOL of the UR copy pairmeets both of the following conditions:

• The P-VOL of the UR copy pair isthe S-VOL for FlashCopy.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The P-VOL of the UR copy pair isthe P-VOL of a TC copy group witha C/T group ID specified, and theTC copy pair is in the suspend

status.3735 The UR copy pair cannot be recreated

because the P-VOL of the UR copy pairis the S-VOL for FlashCopy and afailure might have occurred inFlashCopy.

N N N Y N N N N

3737 The specified UR copy pair cannot becreated in a 3DC (URxUR) configurationbecause a UR copy pair with a differentmirror ID than the specified UR copypair is in a transitional state(Suspending or Deleting).

N N N Y N N N N

3738 A UR copy pair cannot be madebecause the Disaster RecoveryExtended program product has notbeen installed in the MCU.

N N N Y N N N N

3739 The UR copy pair cannot be created forthe following reasons:

• The UR copy pair is defined with adifferent mirror ID.

• The journal group that thespecified S-VOL belongs to is notset to be used in a 3DC (URxUR)configuration.

N N N Y N N N N

373D The specified UR copy pair cannot becreated in a 3DC (URxUR) configurationbecause the S-VOL of the UR copy pairis used in the following programproducts:

• TC

• FCV2/FCSE

• Volume Migration

• HDPz pool volume

N N N Y N N N N

373E A UR copy pair cannot be createdbetween the primary site and theintermediate site in a 3DC Cascade

(URxUR) configuration because themirror status of the UR copy groupbetween the intermediate site and theremote site is not Initial or Stop.

N N N Y N N N N

3744 The specified UR copy pair cannot becreated in a 3DC (URxUR) configuration

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

because the P-VOL of the UR copy pairis in use by another program product.

3745 A UR copy pair cannot be createdbetween the primary site and theintermediate site in a 3DC Cascade(URxUR) configuration because thespecified M-JNL is not set to be used ina 3DC (URxUR) configuration.

N N N Y N N N N

3753 A UR copy pair cannot be created withthe HOLD parameter in a 3DC (URxUR)

configuration because the delta resyncfunction is not supported.

N N N Y N N N N

3755 A UR copy pair cannot beresynchronized. Possible reasonsinclude both of the following:

• The specified S-VOL is already in

use as an S-VOL in a UR copy pairthat has another mirror ID.

• Another UR copy pair using thespecified S-VOL is not in theSWAPPING status.

N N N Y N N N N

3756 A UR copy pair cannot be made with avalue other than 0 specified for the

path group ID because the secondarystorage system does not support valuesother than 0 for path group IDs.

N N N Y N N N N


Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4600 A UR copy pair cannot be made.Possible reasons include one or both of the following:

• The serial number of the primarystorage system in the parameterdoes not match the serial numberof the local storage system.

• The SSID for the P-VOL in theparameter does not match theSSID of the local storage system.

• The CU number specified in theparameter is not supported.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4601 A UR copy pair cannot be suspended.Possible reasons include one or both of the following:


• The SSID for the S-VOL in theparameter does not match theSSID of the local storage system.

N N N Y N N N N

4602 A UR copy pair cannot beresynchronized. Possible reasonsinclude one or both of the following:


• The SSID for the S-VOL in the

parameter does not match theSSID of the local storage system.

N N N Y N N N N

4603 A UR copy pair cannot be dissolved.Possible reasons include one or both of the following:


• The SSID for the S-VOL in theparameter does not match theSSID of the local storage system.

N N N Y N N N N

4606 The UR copy pair status could not be

acquired because the specified CUnumber is unsupported.

N N N Y N N N N

4607 A batch pair status of a UR copy paircould not be acquired because thespecified CU number is unsupported.

N N N Y N N N N

4608 Performance information about a UR journal group could not be acquiredbecause the specified CU number isunsupported.

N N N Y N N N N

460B Registration to or deletion from theEXCTG has failed because the specifiedarbitration command device number (a

non-existent value), EXCTG ID, mirrorID, journal group number, or serialnumber is incorrect.

N N N Y N N N N

460C The copy pair cannot be resynchronizedbecause the C/T group attributedefined in the copy group definition

N Y N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

does not match the C/T group attributeset for the specified device.

4612 A UR copy pair cannot be madebecause the specified P-VOL hasalready been made as a UR copy pair.

N N N Y N N N N

4613 A UR copy pair cannot be madebecause the specified M-JNL group isnot registered.

N N N Y N N N N

4614 A UR copy pair cannot be madebecause no logical path has been madebetween the specified primary storagesystem and secondary storage system.

N N N Y N N N N

4615 A UR copy pair status cannot bechanged because the I/O executionvolume and the P-VOL for theparameter do not match.

N N N Y N N N N

4616 A UR copy pair cannot be suspended,resynchronized or dissolved becauseboth the specified serial number of theprimary storage system and serialnumber of the secondary storagesystem do not match the serial numberof the local storage system.

N N N Y N N N N

4617 A UR copy pair cannot be suspended,resynchronized or dissolved becausethe specified volume is not a UR copypair.

N N N Y N N N N

4618 A UR copy pair cannot be suspended

because it was a suspend request withVolume and Purge specifications.

N N N Y N N N N

4619 A TC, TCA, or UR copy pair cannot besuspended with Reverse specifiedbecause the command is issued to theP-VOL.

N Y Y Y N N N N

461A A TC, TCA, or UR copy pair cannot beresynchronized with Reverse specifiedbecause the command is issued to theP-VOL.

N Y Y Y N N N N

461E The command device cannot bedefined. The reason might be one of

the following:

• The command device is executinga remote control command.

• The volume is part of a TC or TCAcopy pair.

N N N N Y N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

461F The command device cannot bedeleted. The reason might be one of the following:

• The command device is executinga remote control command.

• The volume is part of a TC or TCAcopy pair.

N N N N Y N N N

4621 The command could not be executedbecause the Remote DKC ControlFunction is not supported.

N N N N N N N Y

4630 The command could not be executedbecause the 3-site function is notsupported.

N N N N N N N Y

4633 A UR copy pair status cannot bechanged because an attribute of the P-

VOL or S-VOL differs from the actualvolume attribute. The command mighthave failed because the YKQUERY

command was not executed inadvance.

N N N Y N N N N

4639 The command device could not bedefined because the specified volume isa UR copy pair volume or journalvolume.

N N N N Y N N N

463C Due to either of the following reasons,UR ATTIME suspensions cannot bescheduled in Quick mode:

• The storage system does notsupport the UR ATTIME suspendfunction in Quick mode.

• The microcode of the storagesystem is currently being changedto one that supports the URATTIME suspend function in Quickmode.

N N N N Y N N N

4645 A TC or TCA copy pair status cannot bechanged because a logical path has notbeen established between the P-VOLand S-VOL.

N Y Y N N N N N

4649 TCA copy pair operations cannot be

performed because the specifiedstorage system does not support TCA.

N N Y N N N N N

4650 A delta resync cannot be executedbecause volumes are specified withinthe range of the operation.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4651 A delta resync cannot be executed inthe reversed copy direction.

N N N Y N N N N

4660 The UR ATTIME suspend time cannot

be set. The reason might be one of thefollowing:

• The specified parameter is invalid.

• The storage system does notsupport the UR ATTIME suspendfunction in Quick mode.

N N N Y N N N N

4661 The UR ATTIME suspend time cannotbe set because shared memory is notimplemented.

N N N Y N N N N

4662 The UR ATTIME suspend time cannotbe set because the specified volume isnot the S-VOL of a UR copy pair.

N N N Y N N N N

4663 The UR ATTIME suspend time cannotbe set due to either of the followingcauses:

• The UR copy pair is in the Simplexstatus.

• The copy pair is a delta resync URcopy pair.

N N N Y N N N N

4665 The UR ATTIME suspend time cannotbe set because the timer type of thespecified R-JNL group is not System.

N N N Y N N N N

4668 The UR ATTIME suspend time cannotbe set because three generations of suspend time have already been set forthe specified R-JNL group.

N N N Y N N N N

4669 The UR ATTIME suspend time cannotbe set because another suspend timehas already been set for the C/T groupof the specified SI copy pair.

N N N Y N N N N

466A The UR ATTIME suspend time cannotbe set. The reason might be one of thefollowing:

• The specified time is earlier thanthe consistency time.

• The timer type remains Local

because the UR copy pair has notbeen resynchronized after thetimer type was changed fromLocal to System.

When changing the timer type fromLocal to System, you need to suspend

the UR copy pair. If the UR ATTIME

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

suspend time has already been set,perform the following procedure to setthe 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 timeagain.

466B The UR ATTIME suspend time cannotbe set because the C/T group ID of thespecified SI copy pair is incorrect.

N N N Y N N N N

4672 The UR ATTIME suspend time cannotbe set because power-off processing isin progress.

N N N Y N N N N

4678 The UR ATTIME suspend time cannot

be set for the following reasons:

• The specified volume is not part of an SI copy pair.

• The specified C/T group does notcontain an SI copy pair thatcontains the specified volume.

• The specified C/T group is not usedby an SI copy pair created with BCManager.

N N N Y N N N N

467A The NORMAL ATTIME suspend timecannot be set because the UR ATTIMEsuspend time has already been set for

the specified SI C/T group.

N N N Y N N N N

467B The UR ATTIME suspend time cannotbe set because the NORMAL ATTIMEsuspend time has already been set forthe specified SI C/T group.

N N N Y N N N N

467C The UR ATTIME suspend time cannotbe set because a copy pair that is notin the Duplex status is included in thespecified SI C/T group.

N N N Y N N N N

4681 An SI copy pair cannot be made,resynchronized, or suspended becausethe UR ATTIME suspend time has been

set for the specified SI C/T group.

N N N Y N N N N

4684 The UR ATTIME suspend time cannotbe set because the specified volume iscurrently being used in a UR Open/MFconsistency group.

N N N Y N N N N





Table 2-6 Details of error codes 47xx - 49xx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

47A3 A TC or TCA copy pair cannot besuspended because SVOL(PERMIT) or

Reverse Resync is not supported.

N Y Y N N N N N

47A4 A TCA copy pair cannot beresynchronized with Reverse specifiedbecause either the C/T group ID or theC/T group timer type is incorrect.

N N Y N N N N N

47A6 A TC or TCA copy pair cannot beresynchronized with Reverse specifiedbecause the S-VOL is not suspended inthe Reverse Resync status.

N Y Y N N N N N

47A7 A TC or TCA copy pair cannot beresynchronized with Reverse specifiedbecause the specified volume is the P-

VOL.

N Y Y N N N N N

47BA A TC or TCA copy pair cannot be madebecause the specified volume is the S-VOL of an SI copy pair or subject to anintervention request.

N Y Y N N N N N

4993 A TC or TCA copy pair could not besuspended with Flush specified becausethe specified volume is the S-VOL.

N Y Y N N N N N

4995 The Flush settings cannot besuspended because the commandtarget is not a TCA copy pair.

N N Y N N N N N

49F8 A copy pair cannot be made in thiscopy group because the ATTIMEsuspend time for TCA is set.

N N Y N N N N N

49F9 A copy pair cannot be resynchronizedin this copy group because the ATTIMEsuspend time for TCA is set.

N N Y N N N N N

49FA A copy pair cannot be suspended in thiscopy group because the ATTIMEsuspend time for TCA is set.

N N Y N N N N N

Table 2-7 Details of error codes 4Axx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4A08 The C/T group ID specified for the TCAC/T group option change is incorrect.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4A0B The C/T group ID specified for the TCAC/T group option change is notregistered.

N N Y N N N N N

4A0C The C/T group timer type (SYSTEM /LOCAL /NONE) for the TCA cannot be

changed because there is a copy pair inthis C/T group.

N N Y N N N N N

4A30 The C/T group ID defined in the TCAcopy group, and the C/T group ID setby the copy pair do not match.

N N Y N N N N N

4A31 Copy pair resynchronization failed forone of the following reasons:

• TC copy pair resynchronization wasperformed on a TCA copy group.

• TCA copy pair resynchronization

was performed on a TC copygroup.

N Y Y N N N N N

4A33 The C/T group ID defined in the TCAcopy group is not registered.

N N Y N N N N N

4A34 A TCA copy pair cannot be madebecause the P-VOL is already made asa copy pair.

N N Y N N N N N

4A36 A TCA copy pair cannot beresynchronized because thecorresponding C/T group ID is notregistered in the RCU.

N N Y N N N N N

4A37 A TCA copy pair cannot beresynchronized because the specified P-VOL has not been made as a copy pair.

N N Y N N N N N

4A45 A TCA copy pair cannot be made orresynchronized because there is a copypair that is being dissolved orsuspended in the corresponding C/Tgroup.

N N Y N N N N N

4A50 A TCA copy pair cannot beresynchronized because the P-VOL hasnot been made for the correspondingC/T group ID.

N N Y N N N N N

4A5C The TCA copy pair cannot be madebecause the TCA program product isnot installed.

N N Y N N N N N

4A82 The C/T group cannot be registeredbecause the TCA program product isnot installed.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4A8B The command could not be executedbecause the status of the TC or TCAcopy pair is invalid.

N Y Y N N N N N

4A8C The command could not be executedbecause the status of the TC or TCAcopy pair is being changed.

N Y Y N N N N N

4A8D The command could not be executedbecause the status of the TC or TCAcopy pair is invalid.

N Y Y N N N N N

4A8E The command could not be executedbecause the status of the TC or TCAcopy pair is being changed.

N Y Y N N N N N

4A96 A TC or TCA copy pair cannot be madebecause the CLPR that the specified P-VOL belongs to differs from the one

registered in the C/T group. For detailson the CLPR, see the storage systemdocumentation.

N Y Y N N N N N

4AB7 A TCA copy pair cannot be made orresynchronized because there is a copypair that is being dissolved orsuspended in the corresponding group.

N N Y N N N N N

4ABD The option that was changed by theTCA C/T group definition cannot beupdated because there is a copy pairthat is not in the SIMPLEX or suspend

status in the corresponding group.

N N Y N N N N N

4AC7 The C/T group ID specified at the TCAprimary site cannot be registeredbecause it is in use at the secondarysite.

N N Y N N N N N

4AE2 The TC type of the C/T group alreadyregistered for TCA (MF/OPEN) andspecified by the command do notmatch.

N N Y N N N N N

4AFB A TC or TCA copy pair cannot be madebecause the CLPR that the specified S-VOL belongs to differs from the oneregistered in the C/T group. For detailson the CLPR, see the storage system

documentation.

N Y Y N N N N N





Table 2-8 Details of error codes 4Bxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4B02 A copy pair cannot be resynchronizedbecause the copy pair is in a status

that cannot be changed. The reasonmight be one of the following:

• The copy pair cannot beresynchronized because the copygroup definition contains a C/Tgroup ID, but the actual copygroup does not.

• A resynchronization cannot beperformed if it changes a copygroup that has a C/T group ID butdoes not have an Open/MFConsistency attribute to a copygroup without a C/T group ID.

• A resynchronization cannot beperformed if it changes a copygroup without a C/T group ID to acopy group that has a C/T groupID but does not have an Open/MFConsistency attribute.


status.

N Y N N N N N N

4B03 A copy pair that is in a TC copy groupwith a C/T group ID specified cannot beresynchronized because the C/T groupIDs do not match.

N Y N N N N N N

4B04 A TC or TCA copy pair cannot be madebecause the P-VOL is a commanddevice.

N Y Y N N N N N

4B06 A copy pair that is in a TC copy groupwith a C/T group ID specified cannot besuspended because the copy pairstatus does not allow the status to bechanged. The reason might be one of the following:

• The specified volume is not in a TCcopy group with a C/T group IDspecified.

• The Open/MF Consistency attribute

for the specified volume is differentfrom the copy group definitioninformation.


status.

N Y N N N N N N

4B07 A copy pair that is in a TC copy groupwith a C/T group ID specified cannot be

N Y N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

suspended because the C/T group IDsdo not match.

4B09 A copy pair that is in a TC copy groupwith a C/T group ID specified cannot bedissolved because the copy pair statusdoes not allow the status to bechanged. The reason might be one of the following:



status.

N Y N N N N N N

4B0A A copy pair that is in a TC copy groupwith a C/T group ID specified cannot bedissolved because the C/T group IDs do

not match.

N Y N N N N N N

4B0B RUN (releasing FREEZE) cannot beexecuted for a TC copy group with aC/T group ID specified because thespecified copy pair is not in the FREEZEor SCP status.

This error is reported when the timespecified in the TIMEOUT parameter

when the YKFREEZE command is

executed has passed, and when theYKRUN command is executed. Check the

following:

• After executing the YKFREEZE

command, did you execute anycommand, such as the YKQUERY or

YKEWAIT command, that takes a

long time to execute beforeexecuting the YKRUN command?

• Does the copy group contain asystem volume that is used by theoperating system or BC Managerapplications for control purposes?And is the BC Manager itself is inthe FREEZE status?

N Y N N N N N N

4B0F FREEZE cannot be executed for a copypair that is in a TC copy group with aC/T group ID specified because thevalue specified for TIMEOUT is outsidethe valid range.

N Y N N N N N N

4B10 FREEZE cannot be executed for a TCcopy group with a C/T group IDspecified because the specified volumeis not the P-VOL.

N Y N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4B11 FREEZE cannot be executed for a copypair that is in a TC copy group with aC/T group ID specified. The reasonmight be one of the following:


• The specified volume is using theOpen/MF Consistency PreservationFunction.


status.

N Y N N N N N N

4B14 RUN (releasing FREEZE) cannot beexecuted for a TC copy group with aC/T group ID specified because thespecified volume is not the P-VOL.

N Y N N N N N N

4B15 RUN (releasing FREEZE) cannot beexecuted for a TC copy group with aC/T group ID specified. The reasonmight be one of the following:


• The specified volume is using theOpen/MF Consistency PreservationFunction.


status.

N Y N N N N N N

4B32 A copy pair cannot be created orresynchronized because the specified P-VOL satisfies one of the followingconditions:

• The P-VOL is being used forFlashCopy.

• The P-VOL is being used forFlashCopy SE.

• The P-VOL is a TSE-VOL.

N Y Y N N N N N

4B35 A path cannot be set because the CUnumber for the specified MCU is notsupported.

N N N N N Y N N

4B36 A path cannot be set because the portnumber for the specified MCU is notsupported.

N N N N N Y N N

4B37 A path cannot be set because the portnumber for the specified RCU is notsupported.

N N N N N Y N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

4B38 A path cannot be set because the CUnumber for the specified RCU is notsupported.

N N N N N Y N N

4B49 The remote command cannot beexecuted because the path between thespecified storage system or CU (SSID)and the command target storagesystem is not set, or an error hasoccurred on the path.

N N N N N Y N Y

4B85 The TC copy pair that specified a C/Tgroup ID cannot be created becausethe specified volume is a FlashCopypair.

N Y N N N N N N

4B86 A TC copy pair cannot be madebecause the specified volume is aFlashCopy pair and differential-data

management unit is cylinder.

N Y N N N N N N

4BA9 A TCA copy pair cannot be madebecause the specified CTID is notregistered in the storage system.

N N Y N N N N N

4BB1 No timestamp transfer mode TC copypair can be made because the specifiedvolume is not a TC copy pair.

N Y Y N N N N N

4BB2 A timestamp transfer mode TC copypair cannot be made because thespecified volume is an XRC pair.

N Y Y N N N N N

4BD1 A TC copy pair resynchronization that

makes it possible to use the Open/MFConsistency Preservation Functioncannot be performed because thespecified C/T group ID is invalid.

N Y N N N N N N

4BD2 A TC copy pair cannot be made andresynchronized because the specifiedvolume does not support the Open/MFConsistency Preservation Function.

N Y N N N N N N

4BDE The specified operation cannot beperformed because either the localstorage system or the remote storagesystem does not support inter-CUlogical paths.

N N N N N Y N N

4BE0 A TC copy pair cannot be madebecause the necessary shared memoryis not implemented in the MCU.

N Y N N N N N N





Table 2-9 Details of error codes 50xx - 6Exx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

501C The command device cannot be definedbecause the specified volume is a

journal volume. Alternatively, a URcopy pair cannot be made.

N N N Y N N N N

64E2 A command device cannot be deletedbecause the APID differs from thedefined APID.

N N N N Y N N N

64E3 The Remote DKC Control Functioncannot be executed because thecommand device is not set.

N N N N Y N N N

64E8 A command device cannot be definedbecause the specified CU number is notsupported.

N N N N Y N N N

64EA The paths between CUs, which containcommand devices, are not set.

N N N N Y N N N

64EE The FREEZE command cannot be

executed for TC copy groups with C/Tgroup IDs because a host that does notsupport the FREEZE command is

connected.

N Y N N N N N N

64FA The command cannot be executedbecause the host ID is invalid (notwithin the valid range).

N N N N Y N N N

64FB The command device cannot bedefined. Possible reasons include one

or more of the following:• The corresponding volume does

not exist.

• The corresponding volume isonline.

• The corresponding volume is asystem residence volume.

• The emulation type of thecorresponding volume is 3390-V.

• The corresponding volume is beingused by another program productsuch as SI, TC, TCA, UR or

FlashCopy.• The emulation type of the

corresponding volume is 6588-A.

N N N N Y N N N

64FC A command device cannot be re-defined because the APID that wasalready defined does not match theAPID you attempted to define.

N N N N Y N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

64FD The command device cannot be definedbecause a command device with thesame APID has been defined foranother device.

N N N N Y N N N

64FF A command device cannot be definedbecause the APID specified by theparameter does not match the APIDdefined for the command device.

N N N N Y N N N

69E4 A parameter error occurred. This errormight occur during a storage systemconfiguration change or operation afterthe microcode is changed. If this erroroccurs, scan the storage system byusing BC Manager to obtain volumeinformation again.

N N N Y N N N Y

69E6 A path cannot be deleted because there

is an invalid parameter.

N N N N N Y N N

69E7 The command cannot be executed. Thereason might be one of the following:

• The command cannot be executedbecause the specified volume doesnot exist.

• The Protection attribute has been

set by Hitachi Volume RetentionManager software.

N N N N N N N Y

69E8 The command cannot be executedbecause the specified volume isblocked.

N N N N N N N Y

69E9 The command cannot be executed. Thereason might be one of the following:

• The corresponding volume is in theSimplex status.

• The corresponding volume is notpart of a TCA copy pair.

• The corresponding volume is not aP-VOL.

N N Y N N N N N

69F2 A path cannot be established becausethere is an invalid parameter.

• The storage system serial number

is incorrect.• The SSID is incorrect.

• The CU number is not supported.

N N N N N Y N N

69F3 A copy pair cannot be created orresynchronized. The reason might beone of the following:

Y Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The storage system serial numberof the P-VOL is incorrect.

• The SSID of the P-VOL is incorrect.


• The storage system does notsupport the Open/MF ConsistencyPreservation Function.

69F5 A status cannot be changed becausethe specified volume is the S-VOL.

N Y Y N N N N N

69F7 A suspension cannot be made. Thereason might be one of the following:


• The storage system does notsupport the Open/MF ConsistencyPreservation Function.

Y Y Y N N N N N

69F8 A suspension cannot be made becausethere is an invalid parameter.

Y N N N N N N N

69F9 A copy pair cannot be dissolvedbecause there is an invalid parameter.

Y Y Y N N N N N

69FB A copy pair cannot be dissolvedbecause the volume that received thecommand is an SI S-VOL.

Y Y Y N N N N N

69FC A TCA copy pair cannot beresynchronized, suspended, ordissolved because a volume other thanTCA has been specified.

N N Y N N N N N

69FE A TCA copy pair cannot be dissolvedwith Consistent specified because thespecified volume is not the S-VOL.

N N Y N N N N N

69FF A copy pair cannot be made becausethe program product necessary for theoperation is not installed.

Y Y Y N N N N N

6A00 A C/T group ID cannot be registeredbecause there is an invalid parameter.

N N Y N N N N N

6A07 The command could not be executedbecause the corresponding volume isnot the P-VOL of a TCA copy pair or itis a Non Gen'ed volume.

N N Y N N N N N

6A08 An ATTIME suspend time for TCAcannot be set because there is a copypair that is not in the DUPLEX status.

N N Y N N N N N

6A09 An ATTIME suspend time for TCAcannot be set because the specified C/Tgroup timer type is not System.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

6A0F The command could not be executedbecause the TCA program product isnot installed.

N N Y N N N N N

6A13 The command could not be executedbecause a remote command wasexecuted while the command devicewas not defined.

N N N N N N N Y

6A14 The command could not be executedbecause it was specified to be remotelyexecuted, but this command cannot beexecuted as a remote command.

N N N N N N N Y

6A16 The command could not be executedbecause an instruction to delete acommand device was issued against avolume that is not a command device.

N N N N Y N N N

6A18 The command cannot be executedbecause an unimplemented CU numberwas specified when the commanddevice was defined or deleted.

N N N N N N N Y

6A19 The command could not be executedbecause a remote control commandhas been received for a volume that isnot a command device.

N N N N N N N Y

6A1E The command could not be executedbecause the APID specified by theremote command does not match theAPID that was already registered.

N N N N Y N N Y

6EC0 The setting or status acquisitioncommand for HDTz could not beexecuted because the specifiedparameter is invalid.

N N N N N N Y N

6EC1 The setting or status acquisitioncommand could not be executedbecause the command for HDTzcontains invalid information, or a valueout of range.

N N N N N N Y N

6EC3 The setting or status acquisitioncommand for HDTz could not beexecuted because of either of thefollowing reasons:

• The volume or pool ID that wasspecified does not exist.

• The attribute of the pool thatbelongs to the target device is notHDTz.

N N N N N N Y N

6EC4 The setting or status acquisitioncommand for HDTz could not be

N N N N N N Y N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

executed because of either of thefollowing reasons:

• The specified SSID and the SSID of the target storage system do not

match.

• The specified serial number andthe serial number of the targetstorage system do not match.

• The specified CU number and theCU number of the target device donot match.

• The specified volume number andthe volume number of the targetdevice do not match.

• The target device does not exist.

The setting or status acquisition

command could not be executedbecause an invalid SSID was specifiedfor the command for HDTz.

6EC8 Configuration of the HDTz volume failedbecause an internal processing erroroccurred in the storage system.

N N N N N N Y N

6ECA Configuration of the HDTz pool failedbecause an internal processing erroroccurred in the storage system.

N N N N N N Y N

6ECC The tiering setting information andrelocation status of the HDTz volumecould not be acquired because an

internal processing error occurred inthe storage system.

N N N N N N Y N

6ECE The performance information of theHDTz volume could not be acquiredbecause an internal processing erroroccurred in the storage system.

N N N N N N Y N

Table 2-10 Details of error codes 7Fxx - 8Cxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

7F86 The command cannot be executedbecause no program product forcopying is installed.

N N N N N N N Y

7FD4 This command is not supported. N N N N N N N Y





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8C12 A TC or TCA copy pair status cannot bechanged. Possible reasons include oneor more of the following:

• The specified S-VOL is online.

• The specified volume is either a TCor TCA pair volume, or the S-VOLof an SI copy pair.

• All paths to the RCU are blocked.

• The status of the copy pair is notpossible for the requestedtransition (it is possible that it isalready in requested copy pairstatus).

• The logical volume of the specifiedvolume is blocked.

• The path between the primary site

and the secondary site is in theBUSY status.

• The emulation type of the P-VOLand the S-VOL do not match.Alternatively, the number of cylinders in the S-VOL is less thanthe P-VOL.

• Either the status of the P-VOL isbeing changed, or there is a copypair in the group with the statusbeing changed.

• The command could not beexecuted because the specified TC

or TCA volume is in the SIMPLEXstatus.

• The S-VOL is not in the SWAPPING

status.

• Either the status of the P-VOL isbeing changed, or there is a copypair in the group with the statusbeing changed.

• A copy pair cannot be madebecause the same C/T group ID isset in both the MCU and RCU.

• The specified C/T group ID is not

registered.• Alternatively, a path cannot be

defined and deleted because eitherthe copy pair status or theparameter is invalid. (The possiblereasons are documented by errorcodes C120 through C12F.)

N Y Y N N Y N Y





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8C1E A UR copy pair cannot be made.Possible reasons include one or both of the following:

• The micro version on the specifiedprimary storage system does notsupport a connection with thespecified secondary storagesystem.

• The specified primary storagesystem does not support aconnection with the specifiedsecondary storage system.

N N N Y N N N N

8CE8 The command could not be executedbecause in the instruction to transfer toa remote storage system, there is anerror in the parameter specification forthe host command.

N N N N N N N Y

8CE9 The command could not be executedbecause the path for the Remote DKCControl Function is not set.

N N N N N N N Y

8CEB The command could not be executedbecause the path for the Remote DKCControl Function is not set.

N N N N Y N N N

8CFB The command could not be executedbecause in the instruction to transfer toa remote storage system, there is anerror in the storage system serialnumber.

N N N N Y N N N

8CFC The command could not be executedbecause the command device is notdefined.

N N N N Y N N N

Table 2-11 Details of error codes 8Dxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8D00 A path cannot be established becausethere is an invalid parameter.

• The storage system serial numberis incorrect.

• The SSID is incorrect.


N N N N N Y N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8D01 A path cannot be established becausethere is an invalid parameter.Alternatively, path establishment is notsupported.

N N N N N Y N N

8D09 A path cannot be deleted because thereis an invalid parameter. Alternatively,path deletion is not supported.

N N N N N Y N N

8D10 A copy pair cannot be made. Thereason might be one of the following:

• An inter-CU logical path has notbeen set between the specifiedCUs.

• The storage system serial numberof the P-VOL is incorrect.

• The SSID of the P-VOL is incorrect.


Y Y Y N N N N N

8D11 The command could not be executedbecause the volume specified by thehost command parameter is in the NOTREADY status.

N N N N Y N N N

8D12 The command could not be executedbecause the logical volume of thespecified volume by the host commandparameter is blocked.

N N N N Y N N N

8D14 The command could not be executedbecause the SI, TC, or TCA programproduct is not installed.

Y Y Y N N N N N

8D15 An SI copy pair cannot be made orresynchronized. Possible reasonsinclude one or more of the following:

• The status of the copy pair doesnot allow the status transition. Fordetails, see error code 2310.

• The charging limit of the programproduct was exceeded.

• The copy pair is in the Pendingstatus.

• The copy pair is not in the Splitstatus.


Y N N N N N N N

8D16 An SI copy pair cannot be made orresynchronized. Possible reasonsinclude one or more of the following:

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r


• The charging limit of the program

product was exceeded.




8D17 The command could not be executedbecause the SI, TC, or TCA programproduct is not installed.

Y Y Y N N N N N

8D1A The command could not be executedbecause the volume specified by thehost command parameter is the S-VOL.

N Y Y N N N N N

8D1B A status cannot be changed becausethe status of the specified copy pairdoes not match the actual status.

N Y Y N N N N N

8D1C A TC or TCA copy pair cannot be madeor resynchronized. Possible reasonsinclude one or more of the following:

• The P-VOL is a command device.

• The specified serial number of theprimary storage system or SSIDdoes not match the storage systemserial number or SSID of the localCU.

• The specified P-VOL does notmatch the bootup volume.

• The C/T group ID is incorrect.

• The P-VOL has not been made inthe corresponding C/T group.

• The S-VOL is not in the ReverseResync status.

• Either C/T group ID or the C/Tgroup timer type is incorrect.

N Y Y N N N N N

8D1D An SI copy pair cannot be made or

resynchronized. Possible reasonsinclude one or more of the following:

• The S-VOL is online.


• The P-VOL is online.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The charging limit of the programproduct was exceeded.




• The number of copy pairs in thespecified C/T group ID exceeds themaximum number.

8D1E The serial numbers for the primary andthe secondary storage systems in thehost command parameter is incorrect.

N N N N N N N Y

8D20 The host command parameter isincorrect.

Y Y Y N N N N N

8D21 The command cannot be executedbecause the volume specified by thehost command parameter is in the NOTREADY status.

N N N N Y N N N

8D22 The command cannot be executedbecause the logical volume of thevolume specified by the host commandparameter is blocked.

N N N N Y N N N

8D25 The command could not be executedbecause the TC, TCA, or SI programproduct is not installed.

Y Y Y N N N N N

8D26 An SI copy pair cannot be suspended.Possible reasons include one or more of the following:



status.

• The copy pair is in the Split status.


Y N N N N N N N

8D27 An SI copy pair cannot be suspended.

Possible reasons include one or more of the following:



status.

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r



8D28 The command cannot be executedbecause the copy types of the specifiedcopy pair do not match.

N Y Y N N N N N

8D29 A TC or TCA copy pair cannot besuspended. Possible reasons includeone or more of the following:

• The specified volume is in theSIMPLEX status.

• The P-VOL number in theparameter and bootup volumenumber do not match.

• The S-VOL number in theparameter is incorrect.

• The serial number of the primarystorage system or SSID in theparameter does not match thestorage system serial number orSSID of the local CU.

• The serial number or SSID of thesecondary storage system in theparameter does not match thestorage system serial number orSSID of the RCU.

• The S-VOL number in theparameter and bootup volumenumber do not match.

• The serial number or SSID of thesecondary storage system in theparameter does not match thestorage system serial number orSSID of the local CU.

• 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 beingchanged.

N Y Y N N N N N

8D2A An SI copy pair cannot be suspended.Possible reasons include one or more of the following:

Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r



status.



8D2C The serial numbers for the primary andthe secondary storage systems in thehost command parameter is incorrect.

N N N N N Y N Y


N N N N N N N Y

8D31 Multiple SI copy pairs cannot besuspended because there is a copy pair

that does not allow the status transitionin the specified copy pairs.

Y N N N N N N N

8D38 The command could not be executedbecause the specified volume is not inthe SIMPLEX status.

N N N N Y N N N

8D39 A command device cannot be definedbecause it differs from the APID thatwas already registered.

N N N N Y N N N

8D3A A command device cannot be definedbecause the specified APID is in use byanother DEV.

N N N N Y N N N

8D3D A command device cannot be deletedbecause the specified volume is not acommand device.

N N N N Y N N N

8D3E A command device cannot be madebecause the specified CU number is notsupported.

N N N N Y N N N

8D41 The command cannot be executedbecause the volume specified as thecommand device is already part of acopy pair, or is a journal volume.

N N N N Y N N N

8D42 The command cannot be executedbecause the volume specified as acommand device is a volume used inthe open system.

N N N N Y N N N

8D43 The command could not be executedbecause the logical volume of thespecified volume is blocked.

N N N N Y N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8D44 The command could not be executedbecause the specified volume has PINdata.

N N N N Y N N N

8D45 The command device cannot bedefined. The reason might be one of the following:

• The corresponding volume isexecuting a remote controlcommand as a command device.

• The corresponding volume is partof a TC or TCA copy pair.

N N N N Y N N N

8D46 The command device cannot bedeleted. The reason might be one of the following:

• The corresponding volume isexecuting a remote controlcommand as a command device.

• The corresponding volume is partof a TC or TCA copy pair.

N N N N Y N N N

8D47 The command could not be executedbecause the specified volume is an SIvolume.

N N N N Y N N N

8D4D The command could not be executedbecause the specified volume does notexist.

N N N N Y N N N

8D4E A command device cannot be definedbecause it differs from the APID that

was already registered.

N N N N Y N N N

8D4F The command could not be executedbecause the specified volume is online.

N N N N Y N N N


N N N N N N N Y

8D51 The command could not be executedbecause the logical volume of thespecified volume is blocked or thespecified volume is in the NOT READYstatus.

N N N N Y N N N

8D52 The command could not be executedbecause the logical volume of thespecified volume is blocked.

N N N N Y N N N

8D56 An SI copy pair cannot be dissolved.Possible reasons include one or more of the following:


Y N N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The copy pair is in the V-Splitstatus.


8D57 An SI copy pair cannot be dissolved.Possible reasons include one or more of the following:




Y N N N N N N N

8D58 The command cannot be executedbecause the copy types of the specifiedcopy pair do not match.

N Y Y N N N N N

8D59 A TCA copy pair cannot be dissolvedwith Consistent specified because thespecified volume is not the S-VOL.

N N Y N N N N N

8D5A A TC or TCA copy pair cannot bedissolved. Possible reasons include oneor more of the following:

• It is already in the SIMPLEX status.

• The P-VOL in the parameter andthe bootup volume number do notmatch.

• The S-VOL number in theparameter is incorrect.

• The serial number or SSID of theprimary storage system in theparameter does not match thestorage system serial number orSSID of the local CU.

• The serial number of the secondarystorage system or SSID in theparameter does not match thestorage system serial number orSSID of RCU.

• The S-VOL number in the

parameter and bootup volumenumber do not match.

• The status of the copy pair isinvalid.

• The status of the copy pair is beingchanged.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8D5B An SI copy pair cannot be dissolved.Possible reasons include one or more of the following:




Y N N N N N N N


N N N N N N N Y

8D71 A TCA C/T group cannot be registeredor changed. Possible reasons includeone or more of the following:

• The specified C/T group ID isincorrect.

• You cannot specify System as the

timer type.

• The timer type is incorrect (notSystem, Local or None).

• The C/T group ID is alreadyregistered.

• 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 astatus that is neither SIMPLEX nor

suspend.

• The copy types of the specified C/Tgroup and the types of bootup C/Tgroup do not match.

N N Y N N N N N


N N N N N N N Y

8D79 A TCA C/T group cannot be deleted.Possible reasons include one or more of

the following:• The C/T group ID is incorrect.

• The C/T group is not registered.

• There is a TCA copy pair in thecorresponding C/T group.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• There is a copy pair that is beingdissolved or suspended in thespecified C/T group.


N N N N N N N Y

8DD1 An SI copy pair cannot be made,resynchronized, or suspended becausethe UR ATTIME suspend time has beenset for the specified SI C/T group.

Y N N N N N N N

8DF0 The command could not be executedbecause the sub-command code isincorrect.

N N N N N N N Y

8DF1 The host command parameter isincorrect.

N N N N N N N Y

8DF2 The command could not be executed

because the specified volume is eithernot a TCA volume, or not the P-VOL.

N N N N N N N Y

8DF3 The command could not be executedbecause the specified volume is in theNOT READY status.

N N N N Y N N N

8DF4 The command could not be executedbecause the logical volume of thespecified volume is blocked.

N N N N Y N N N

8DF5 The command could not be executedbecause the SSID and CU number inthe host command parameter do notmatch.

N N N N N N N Y

8DF6 The command could not be executedbecause the serial numbers of the hostcommand parameter and the localstorage system do not match.

N N N N N N N Y

8DF7 The command could not be executedbecause the SSID of the host commandparameter and the local storage systemdo not match.

N N N N N N N Y

8DFF The command could not be executedbecause the sub-command code isincorrect.

N N N N N N N Y





Table 2-12 Details of error codes 8Fxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

8F00 A UR copy pair cannot be madebecause the specified volume is an

external volume.

N N N Y N N N N

8F10 A UR copy pair cannot be madebecause the specified volume has beenmade as a copy pair for SI orFlashCopy and cannot be used for thiscombination.

N N N Y N N N N

8F14 A UR copy pair cannot be madebecause the specified volume is aReserve volume.

N N N Y N N N N

8F17 A UR copy pair cannot be madebecause the specified volume is online.

N N N Y N N N N

8F18 A UR copy pair cannot be madebecause the specified volume has beenmade as a copy pair for anotherprogram product.

N N N Y N N N N

8F19 A UR copy pair cannot be madebecause the emulation type of thespecified volume cannot be used in UR.

N N N Y N N N N

8F1B A UR copy pair cannot be madebecause the specified P-VOL is not inthe SIMPLEX status.

N N N Y N N N N

8F1C A UR copy pair cannot beresynchronized because the specified P-

VOL is not in the suspend status.

N N N Y N N N N

8F1E A UR copy pair cannot be madebecause the cache or shared memory isbeing recovered.

N N N Y N N N N

8F1F A UR copy pair cannot be madebecause the cache or shared memory isblocked.

N N N Y N N N N

8F21 A UR copy pair cannot be made. Thereason might be one of the following:

• The configurations cannot becombined because the specifiedvolume is the P-VOL of a TC or TCA

copy pair, or the specified volumeis 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 beresynchronized because the

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

configuration does not allow the statusto be changed.

8F24 A UR copy pair cannot be madebecause a path has not beenestablished between the devices.

N N N Y N N N N

8F25 A UR copy pair cannot be made orresynchronized because the specifiedvolume contains PIN data.

N N N Y N N N N

8F28 A UR copy pair cannot be made orresynchronized because the specified P-VOL or S-VOL cannot be accessed.

N N N Y N N N N

8F29 A UR copy pair cannot be madebecause the P-JNL group cannot beused.

N N N Y N N N N

8F2A A UR copy pair cannot be created

because the specified P-VOL satisfiesone of the following conditions:

• The P-VOL is being used as the S-VOL for FlashCopy.

• The P-VOL is being used forFlashCopy SE.

• The P-VOL is a TSE-VOL.

N N N Y N N N N

8F2B A UR copy pair cannot be madebecause the specified P-VOL isprotected by the LDEV guard.

N N N Y N N N N

8F33 A UR copy pair cannot be madebecause the specified volume has beenmade as a copy pair for anotherprogram product.

N N N Y N N N N

8F35 A UR copy pair cannot be madebecause the specified volume isblocked.

N N N Y N N N N

8F39 A UR copy pair cannot be madebecause the UR program product is notinstalled.

N N N Y N N N N

8F4D A UR copy pair cannot be made orresynchronized. The reason might beone of the following:

• The R-JNL group is not registered.• The R-JNL volume is blocked.

• The specified S-VOL is blocked.

N N N Y N N N N

8F50 A UR copy pair could not be made orresynchronized because of heavyworkload in the specified storage

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

system. Re-execute the operation afterwaiting for 5 to 6 minutes.

8F53 A UR copy pair cannot be madebecause the configuration does notallow the status transition. (Forexample, the specified volume hasalready been made as an SI copy pairand cannot be used for thiscombination.)

N N N Y N N N N

8F58 A UR copy pair cannot be made orresynchronized. The reason might beone of the following:

• The pair statuses of the specifiedS-VOL and P-VOL do not match.

• The statuses of the R-JNL groupand M-JNL group do not match.

N N N Y N N N N

8F67 A UR copy pair cannot be madebecause the specified S-VOL does notsupport external volumes.

N N N Y N N N N

8F6D A UR copy pair cannot be madebecause the specified volume is acommand device.

N N N Y N N N N

Table 2-13 Details of error codes C0xx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

H

HDT

z

Othe

r

C023 The specified serial number or SSID of the primary storage system is differentfrom the storage system serial numberor SSID of the local CU.

N N N N N Y N N

C026 A path cannot be set because thespecified CU number for the secondarysite is not supported for the primary orsecondary storage system.

N N N N N Y N N

C02B The specified P-VOL does not match thestartup volume.

N N N N N Y N N

C02C The specified serial number or SSID of the primary storage system is differentfrom the storage system serial numberor SSID of the local CU.

N N N N N Y N N

C032 The copy type for making a TC or TCAcopy pair is incorrect. (You can specifyNOCOPY, Full Copy, or Resync only.)

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C048 The command cannot be executedbecause the specified serial number orSSID of the primary storage systemdoes not match the storage system

serial number or SSID of the local CU.

N N N N N Y N N

C04C The command cannot be executedbecause the specified serial number orSSID of the secondary storage systemdoes not match the storage systemserial number or SSID of the RCU, orthe path is not registered.

N N N N N Y N N

C04D The command cannot be executedbecause the specified serial number orSSID of the secondary storage systemdoes not match the storage systemserial number or SSID of the RCU.

N N N N N Y N N

C055 The command could not be executedbecause the TC or TCA volume is in theSIMPLEX status.

N Y Y N N N N N

C058 The P-VOL number in the TC or TCAparameter does not match the bootupvolume number.

N Y Y N N N N N

C059 The serial number or SSID of theprimary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the local CU.

N Y Y N N N N N

C05A The serial number or SSID of the

primary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the local CU.

N Y Y N N N N N

C05D The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the RCU.

N Y Y N N N N N

C05E The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSID

of the RCU.

N Y Y N N N N N

C063 The S-VOL number in the TC or TCAparameter does not match the bootupvolume number.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C064 The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSID

of the local CU.

N Y Y N N N N N

C065 The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the local CU.

N Y Y N N N N N

C06A The command could not be executedbecause the TC or TCA volume is in theSIMPLEX status.

N Y Y N N N N N

C06D The P-VOL number in the TC or TCAparameter does not match the bootupvolume number.

N Y Y N N N N N

C06E The serial number or SSID of theprimary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the local CU.

N Y Y N N N N N

C06F The serial number or SSID of theprimary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the local CU.

N Y Y N N N N N

C072 The serial number or SSID of thesecondary storage system in the TC or

TCA parameter does not match thestorage system serial number or SSIDof the RCU.

N Y Y N N N N N

C073 The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the RCU.

N Y Y N N N N N

C074 No TC copy pair can be made becausethe TC program product is not installed.

N Y Y N N N N N

C078 The S-VOL number in the TC or TCAparameter does not match the bootup

volume number.

N Y Y N N N N N

C079 The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSIDof the RCU.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C07A The serial number or SSID of thesecondary storage system in the TC orTCA parameter does not match thestorage system serial number or SSID

of the RCU.

N Y Y N N N N N

C0A1 The S-VOL number in the TC or TCAparameter is incorrect.

N Y Y N N N N N

C0A2 The S-VOL number in the TC or TCAparameter is incorrect.

N Y Y N N N N N

C0B6 The command could not be executedbecause the specified volume is in theSIMPLEX status.

N Y Y N N N N N

C0C5 A copy pair cannot be suspendedbecause it is already in the suspendstatus.

N Y Y N N N N N

C0C6 The command could not be executedbecause it is already in the SIMPLEX

status.

N Y Y N N N N N

C0C7 The command could not be executedbecause it is already in the SIMPLEX

status.

N Y Y N N N N N

C0F1 The command to suspend could not beexecuted because the S-VOL for TC isin the Pending status.

N Y Y N N N N N


Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C120 An attempt to establish a path hasfailed. Possible reasons include eitherof the following:

• For an inter-CU logical path, thenumber of RCUs registered in theMCU exceeds 4.

• For an inter-DKC logical path, thenumber of path group IDsregistered in one storage systemexceeds 64.

N N N N N Y N N

C122 The command could not be executedbecause the specified RCU parameter isinvalid.

N N N N N Y N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C123 The specified RCU is not registered (thepath is not established).

N N N N N Y N N

C126 The command to delete a path could

not be executed because there is a TC,TCA, or UR copy pair or journal volumein the target CU.

N N N N N Y N N

C127 An attempt to establish or delete someof the specified multiple paths havefailed. Possible reasons include one ormore of the following:


• The port or MP status is abnormal.

• A cable is not connected properly.

• The specified port is invalid.

N N N N N Y N N

C128 An attempt to establish or delete all thespecified multiple paths has failed.Possible reasons include one or more of the following:


• The port or MP status is abnormal.

• A cable is not connected properly.

• The specified port is invalid.

N N N N N Y N N

C129 The command could not be executedbecause the number of SSIDsregistered in the RCU exceeds four.

N N N N N Y N N

C12A The command could not be executed

because the device-identifying code of an RCU for which path deletion isspecified is invalid, or because the RCUtype (FIBRE/ESCON) is invalid.

N N N N N Y N N

C12B The command could not be executedbecause there are one or more pathsthat have a different serial number.

N N N N N Y N N

C12C The command could not be executedbecause automatic port switchingcannot be performed for the specifiedpath.

N N N N N Y N N

C12D The command could not be executed

because the device-identifying code of an RCU for which path registration isspecified is invalid, or because the RCUtype (FIBRE/ESCON) is invalid.

N N N N N Y N N

C12E The command could not be executedbecause all CU numbers of an RCU for

N N N N N Y N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

which path creation or deletion isspecified are not the same.

C12F The command cannot be executed. Thereason might be one of the following:

• The specified CU number is notdefined.

• An LDEV is not defined for thespecified CU number.

N N N N N Y N N

C162 A copy pair cannot be resynchronizedbecause the corresponding bootup pairis not in the suspend status.

N Y Y N N N N N

C184 A copy pair cannot be dissolvedbecause an attempt to change the S-VOL status failed.

N Y Y N N N N N

C189 A TC or TCA copy pair cannot be

dissolved because the copy pair statusis invalid.

N Y Y N N N N N

C18A The copy pair cannot be dissolved. Thereason might be one of the following:

• The status of the bootup volume isbeing changed.

• There is a copy pair in the groupthat has a status that is beingchanged.

N Y Y N N N N N

C194 A copy pair cannot be suspendedbecause the S-VOL status is beingchanged.

N Y Y N N N N N

C195 A copy pair cannot be suspendedbecause the specified copy pair isalready in the suspend status.

N Y Y N N N N N

C198 The command cannot be executedbecause there is no copy pair that canbe suspended in the group.

N Y Y N N N N N

C199 The copy pair cannot be suspended.The reason might be one of thefollowing:

• The status of the bootup volume isbeing changed.

• There is a copy pair in the groupthat has a status that is beingchanged.

N Y Y N N N N N

C1BE A TC or TCA copy pair status cannot bechanged because the storage system isbeing turned on.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C1D1 The specified copy pair cannot besuspended, resynchronized, or deletedbecause a path is not set up betweenCUs (SSIDs) in the copy pair, or the

path is in an error status.

N Y Y N N N N N


Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C211 A copy pair cannot be made becausethe specified copy pair is already in theDUPLEX status.

N Y Y N N N N N

C213 The command cannot be executedbecause the serial number or SSID of the primary storage system for theparameter does not match the actualserial number or SSID of the primarystorage system.

N Y Y N N N N N

C214 The command cannot be executedbecause the serial number or SSID of the secondary storage system in theparameter is different from the onealready registered with the path(including ones without a path).

N Y Y N N N N N

C215 A copy pair cannot be made because

the specified S-VOL is in use byanother copy pair.

N Y Y N N N N N

C21A A copy pair cannot be resynchronizedbecause the specified copy pair is not inthe suspend status.

N Y Y N N N N N

C22A A copy pair cannot be dissolvedbecause the status of the specifiedvolume is SIMPLEX.

N Y Y N N N N N

C23E A copy pair cannot be suspendedbecause the specified copy pair is in thePending status.

N Y Y N N N N N

C28B Copy pair resynchronization, whichcauses a copy direction reversal,cannot be made because the specifiedcopy pair is not in the SWAPPING status.

N Y Y N N N N N

C28C Copy pair resynchronization, whichcauses a copy direction reversal,

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

cannot be made because a path in thereverse copy direction is not set.

C2A0 A copy pair cannot be made becausethe charging limit of the MCU programproduct has been exceeded.

N Y Y N N N N N

C2A3 A copy pair cannot be made becausethe charging limit of TC in the MCU hasbeen exceeded. Check the licensecapacity of this and all related programproducts.

N Y Y N N N N N

C2A4 A copy pair cannot be made becausethe charging limit of TCA in the MCUhas been exceeded. Check the licensecapacity of this and all related programproducts.

N Y Y N N N N N

C2A8 A copy pair cannot be made becausethe charging limit of the RCU programproduct has been exceeded.

N Y Y N N N N N

C2B3 A copy pair cannot be created becausethe HDPz volume specified for the P-VOL is being expanded.

N Y Y N N N N N

C2B6 A copy pair cannot be created becausethe pages of the HDPz volume specifiedfor the P-VOL are being released.

N Y Y N N N N N

Table 2-16 Details of error codes C3xx - C8xx

Errorcode

Error detailsType of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C300 A TC/TCA copy pair that is to be linkedwith UR cannot be made because theDisaster Recovery Extended programproduct has not been installed in theMCU.

N Y Y N N N N N

C301 A TC/TCA copy pair that is to be linkedwith UR cannot be made because theDisaster Recovery Extended programproduct has not been installed in the

RCU.

N Y Y N N N N N

C305 A copy pair cannot be made becausethe charging limit of TC in the RCU hasbeen exceeded. Check the licensecapacity of this and all related programproducts.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C306 A copy pair cannot be made becausethe charging limit of TCA in the RCUhas been exceeded. Check the licensecapacity of this and all related program

products.

N Y Y N N N N N

C30D The specified volume within the RCU,or another volume which belongs to thesame group is in transition to aSIMPLEX or suspend status. Please try

the operation again in a few minutes.

N Y Y N N N N N

C310 The MCU is not NVS ON. N Y Y N N N N N

C311 The subsystem level cache of the MCUis not valid.

N Y Y N N N N N

C312 The P-VOL is not in the SIMPLEX status. N Y Y N N N N N

C313 The P-VOL is not in the suspend status. N Y Y N N N N N

C314 The P-VOL is not in the SIMPLEX status. N Y Y N N N N N

C315 The P-VOL has PIN data. N Y Y N N N N N

C316 The drive copy is being performed onthe P-VOL (troubleshooting).

N Y Y N N N N N

C317 The drive copy is being performed onthe P-VOL (SVP request).

N Y Y N N N N N

C318 The copy task ending process is beingperformed on the P-VOL.

N Y Y N N N N N

C319 The collection copy is being performed

on the P-VOL.

N Y Y N N N N N

C31A The P-VOL is in a collection accessstatus.

N Y Y N N N N N

C31B The logical volume of the P-VOL isblocked (PDEV blocking factor).

N Y Y N N N N N

C31C The P-VOL cannot be accessed(because the LDEV is blocked or in theNOT READY status).

N Y Y N N N N N

C31D Formatting of the logical volume isbeing performed on the P-VOL.

N Y Y N N N N N

C31E The P-VOL is in the READ ONLY status. N Y Y N N N N N

C320 The logical path between the MCU andthe RCU is not set (number of path =0).

N Y Y N N N N N

C321 The condition setting for the number of the Minimum Path between the MCUand the RCU is invalid.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C322 The MCU is a storage system type thatis not supported by TC or TCA.

N Y Y N N N N N

C324 The RCU sequence (number, SSID or

CU) is incorrect.

N Y Y N N N N N

C325 The RCU is not NVS ON. N Y Y N N N N N

C326 The subsystem level cache of the RCUis not valid.

N Y Y N N N N N

C327 A copy pair cannot be made becausethe status of the P-VOL does not permitremote copy.

N Y Y N N N N N

C328 The track format of the P-VOL and S-VOL do not match.

N Y Y N N N N N

C32A The S-VOL is protected by LDEVsecurity.

N Y Y N N N N N

C32B The P-VOL is protected by LDEVsecurity.

N Y Y N N N N N

C32C The S-VOL is protected by LDEV guard. N Y Y N N N N N

C32E A copy pair cannot be made becauseconnection with the specified S-VOL isnot supported.

N Y Y N N N N N

C32F The condition for the number of cylinders for TC or TCA volumes isincorrect (the number of cylinders inthe P-VOL > the number of cylinders inthe S-VOL).

N Y Y N N N N N

C330 The condition for the TC or TCA volumecapacity is incorrect (not P-VOL=S-VOL).

N Y Y N N N N N

C332 The device level cache of the S-VOL isnot valid.

N Y Y N N N N N

C333 The S-VOL is not DFW ON. N Y Y N N N N N

C335 The S-VOL is a TCA P-VOL. N Y Y N N N N N

C336 The S-VOL has PIN data. N Y Y N N N N N

C337 The S-VOL is in the Reserve status. N Y Y N N N N N

C338 An intervention request has beenissued for the S-VOL (S-VOL or reservevolume of SI).

N Y Y N N N N N

C339 The S-VOL is in the FC status. N Y Y N N N N N

C33A A copy pair cannot be made becausethe specified S-VOL does not supportTC.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C33B The S-VOL is an S-VOL of another copypair.

N Y Y N N N N N

C33C A copy pair cannot be made because

the specified S-VOL is not installed.

N Y Y N N N N N

C33E An intervention request has beenissued for the S-VOL (DEV NOT READYstatus).

N Y Y N N N N N

C33F The S-VOL is a TC or TCA pair volume. N Y Y N N N N N

C35C The P-VOL cannot be accessed. N Y Y N N N N N

C370 The condition setting for the number of the Minimum Path is incorrect (pathproblem or invalid path).

N Y Y N N N N N

C371 Recovery processing for cache memoryor shared memory is being performed.

Wait a few minutes, and then executeagain.

N Y Y N N N N N

C372 Recovery processing for cache memoryor shared memory is being performed.Wait a few minutes, and then executeagain.

N Y Y N N N N N

C373 A copy pair cannot be made becausethe specified S-VOL is a Reservevolume.

N Y Y N N N N N

C374 A copy pair cannot be made becausethe specified P-VOL is a Reservevolume.

N Y Y N N N N N

C378 The condition setting for the number of the Minimum Path is incorrect (multipleCU number setting or path blockingissue).

N Y Y N N N N N

C379 The condition setting for the number of the Minimum Path is incorrect (pathproblem or invalid path).

N Y Y N N N N N

C37B A TC copy pair cannot be defined orresynchronized. The reason might beone of the following:

• The S-VOL is in an unusable state.

• The microprogram version of theMCU or RCU does not support thefunction or configuration.

N Y Y N N N N N

C37C The subsystem level cache of the RCUis not valid.

N Y Y N N N N N

C37D The RCU is not NVS ON. N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C37E The device level cache of the S-VOL isnot valid.

N Y Y N N N N N

C37F The S-VOL is not DFW ON. N Y Y N N N N N

C380 The cache for the MCU is blocked onone side (in transition).

N Y Y N N N N N

C381 The cache for the MCU is beingrecovered.

N Y Y N N N N N

C382 The cache for the MCU is being blockedon one side (in transition) or it is beingrecovered on one side.

N Y Y N N N N N

C388 A copy pair cannot be made becausethe P-VOL is not supported for theemulation type.

N Y Y N N N N N

C38B The RCU is already in use by TC or

TCA.

N Y Y N N N N N

C38D A TC copy pair cannot be defined orresynchronized. The reason might beone of the following:

• The S-VOL is in an unusable state.

• The microprogram version of theMCU or RCU does not support thefunction or configuration.

N Y Y N N N N N

C38E The S-VOL device is not supported byTC or TCA.

N Y Y N N N N N

C390 The S-VOL is not in the suspend status. N Y Y N N N N N

C391 The S-VOL is in a copy pair status thatdoes not permit copying.

N Y Y N N N N N

C392 The S-VOL is online. Alternatively, acopy pair was already made for a copytype other than TC or TCA.

N Y Y N N N N N

C393 The S-VOL has PIN data. N Y Y N N N N N

C394 The S-VOL is online. N Y Y N N N N N

C395 The S-VOL cannot be used (because of a logical volume being blocked,collection access, etc.).

N Y Y N N N N N

C398 A copy pair cannot be made becausethe S-VOL is not supported for theemulation type.

N Y Y N N N N N

C39E The P-VOL capacity exceeds the volumecapacity within which a copy pair canbe made.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C39F The P-VOL or S-VOL capacity exceedsthe volume capacity within which acopy pair can be made.

N Y Y N N N N N

C3A0 The P-VOL device is not supported byTC or TCA.

N Y Y N N N N N

C3A4 The RCU does not support the S-VOLhost online check indication function.

N Y Y N N N N N

C3A5 The S-VOL is online. N Y Y N N N N N

C3A6 The specified SSID, or CU number of the RCU is incorrect.

N Y Y N N N N N

C3A8 A copy pair cannot be created becausethe specified copy pair is made up of volumes whose emulation types are3390-A and non-3390-A.

N Y Y N N N N N

C3AA The RCU has its cache (one side)blocked (NVS).

N Y Y N N N N N

C3AB The RCU has its cache (one side)blocked.

N Y Y N N N N N

C3AD The RCU has exceeded the charginglimit for the TC or TCA programproduct.

N Y Y N N N N N

C3AE The TC or TCA program product has notbeen installed on the RCU.

N Y Y N N N N N

C3AF The storage system type for the RCU isnot supported by TC or TCA, or the C/T

group value for TCA is incorrect.

N Y Y N N N N N

C3B1 The condition setting of the number of the Minimum Path is incorrect.

N Y Y N N N N N

C3B6 The TC or TCA P-VOL is an SI pairvolume.

N Y Y N N N N N

C3B7 The TC or TCA S-VOL is an SI pairvolume.

N Y Y N N N N N

C3BA A copy pair cannot be made becausethe specified SSID or CU number forthe RCU is not supported for theprimary and secondary site.

N Y Y N N N N N

C3BD The P-VOL is online. N Y Y N N N N N

C3BE When the P-VOL of a TC or TCA copypair is also the S-VOL of an SI copypair, it must be in the Split status.Also, a reserve volume, a P-VOL in theReverse Resync status, and the S-VOLfor FlashCopy cannot be specified.

N Y Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C3BF The S-VOL of an SI copy pair or aReserve volume cannot be specified asthe S-VOL of a TC or TCA copy pair.Also, a P-VOL in the Reverse Resync

status and the S-VOL for FlashCopycannot be specified.

N Y Y N N N N N

C3C0 When the P-VOL of a TC or TCA copypair is also the S-VOL of an SI copypair, both S-VOLs must be a copy pairin a one-to-one combination.

N Y Y N N N N N

C3C1 The S-VOL is not made under the C/Tgroup.

N N Y N N N N N

C3C2 The C/T group ID specified in making acopy pair is already in use in the S-VOL.

N N Y N N N N N

C3C3 The 4MCU is already registered ormade under the subjected C/T group. N N Y N N N N N

C3C4 The option information (timer type,timeout) for an operating (alreadybeing made a copy pair) C/T groupcannot be changed.

N N Y N N N N N

C3C5 A copy pair could not be made becausethere are multiple storage systems atthe primary site, but the timer type isnot System.

N N Y N N N N N

C3C6 The command cannot be executedbecause the update timeout option is

different for copy pairs that alreadyexist and those that have not yet beenmade on the primary site that hasmultiple storage systems.

N N Y N N N N N

C3C7 A TC or TCA copy pair cannot be made.The reason might be one of thefollowing:

• The specified volume is part of aTC, TCA, or UR copy pair withanother volume.

• The specified volume is a journalvolume.

N N Y N N N N N

C3C9 The C/T group is not registered in theRCU. N N Y N N N N N

C3CA The S-VOL is in the reserve status orthe RCU, the S-VOL or the M-R path isin the BUSY status.

N Y Y N N N N N

C3CB The TCA program product has not beeninstalled on the RCU.

N N Y N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

C3CD The S-VOL of a TC or TCA copy pair isan SI pair volume.

N Y Y N N N N N

C3D1 Another C/T group ID is already

registered or made in the RCU.

N N Y N N N N N

C3D2 The storage system type of the RCU isnot supported by TC or TCA.

N Y Y N N N N N

C3D3 The specified SSID, or CU number of the RCU is incorrect.

N Y Y N N N N N

C3D6 The specified S-VOL cannot be usedbecause the device cannot berecognized from the connection port.

N Y Y N N N N N

C3D7 The status of the S-VOL in the RCU isincorrect.

N Y Y N N N N N

C3D8 A TC/TCA copy pair cannot be made

because the volume specified to be theS-VOL is a system residence volume.

N Y Y N N N N N

C3D9 A copy pair cannot be created becausethe HDPz volume specified for the S-VOL satisfies one of the followingconditions:

• The HDPz volume is being used byother program product.

• The capacity is being changed.

• The pages are being released.

• The pool is being initialized.

N Y Y N N N N N

C3DA A TC/TCA copy pair cannot be madebecause the volume specified to be theP-VOL is a system residence volume.

N Y Y N N N N N

C3DB The S-VOL is not in the suspend status. N Y Y N N N N N

C3FE A copy pair cannot be made becauseTCA and TC cannot be specifiedsimultaneously.

N N Y N N N N N

C4FC A TC or TCA copy pair cannot be madeor resynchronized because thenecessary shared memory is notimplemented in the RCU.

N Y Y N N N N N

C825 Commands that use TC copy pairs, URcopy pairs, or the Remote DKC ControlFunction cannot be executed becausethe number of executable paths is lessthan the minimum value.

N Y Y Y N N N Y

C8D1 The command for registering commanddevices via the Remote DKC ControlFunction (YKBLDCMD) cannot be

N N N N Y N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

executed because the specified volumedoes not exist.

Table 2-17 Details of error codes CBxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

CB10 A copy pair cannot be made becausethere was an attempt to make a copypair for both directions with the sameC/T group ID.

N N Y N N N N N

CB12 A TCA copy pair cannot be created forone of the following reasons:

• The C/T group ID specified in theRCU is already used for UR(OPEN).

• A total of 128 C/T groups are usedin the RCU for UR(OPEN) andTCA(MF/OPEN).

N N Y N N N N N

CB18 A copy pair cannot be added to a C/Tgroup where the P-VOL and the S-VOLare being swapped.

N N Y N N N N N

CB1D A dummy volume cannot be created onthe S-VOL.

N Y Y N N N N N

CB1F The current RCU version does notsupport Fibre TC or TCA.

N Y Y N N N N N

CB60 Fibre TC or TCA has not been installedon the RCU.

N Y Y N N N N N

CB61 Copy pairs with Fibre and ESCON pathscannot exist within the same C/Tgroup.

N N Y N N N N N

CB62 Copy pairs with Fibre and ESCON pathscannot exist within the same storagesystem.

N Y Y N N N N N

CB64 The storage system type of the MCU isnot supported (not 3990-6/6E, or is2105).

N Y Y N N N N N

CB66 A TC copy pair cannot be madebecause the necessary difference areadoes not exist in the RCU.

N Y N N N N N N

CB67 A TC copy pair cannot be madebecause extended shared memory isnot implemented in the RCU.

N Y N N N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• The specified S-VOL is the S-VOLof a UR copy pair.

• The specified S-VOL is a journalvolume.

CBEE A TC/TCA copy pair cannot be createdfor one of the following reasons:

• The specified P-VOL is alreadycreated as a P-VOL in a deltaresync UR copy pair.

• The specified P-VOL is created as aP-VOL in a copy pair in a 3DCMulti-Target (URxUR)configuration.

N Y Y N N N N N

CBF8 A TC copy pair cannot be created forone of the following reasons:

• The MCU or RCU microcode versiondoes not support the connection.

• The MCU or RCU model does notsupport the connection.

• This RCU model does not supportdifferential-data management bycylinders.

N Y N N N N N N

CBFA A TC copy pair cannot be operated onfor one of the following reasons:


• All of the mainframe Fibre Channeladapters are blocked.

N Y N N N N N N

CBFC A TC copy pair cannot be made orresynchronized because the C/T groupID is not in the supported range.

N Y Y N N N N N

Table 2-18 Details of error codes DBxx - E8xx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

DB02 A UR copy pair status cannot be

changed because the status transitionis not allowed.

In the following examples, statustransition is not allowed:

• When an attempt to create a copypair is made for a copy pair with astatus is not SIMPLEX.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

• When an attempt to re-create acopy pair is made for a copy pairwith a status is not in the suspendstatus.

Check the status of the copy pair againbecause there is a possibility thatstatus transition has been performedcorrectly.

DB03 A UR copy pair status cannot bechanged because the copy pair statusis being changed (Suspending orDeleting).

N N N Y N N N N

DB07 A UR copy pair status cannot bechanged because the power-on processis in progress.

N N N Y N N N N

DB08 A UR copy pair status cannot be

changed because the power-off processis in progress.

N N N Y N N N N

DB09 A UR copy pair cannot be madebecause the specified volume is a TCAcopy pair.

N N N Y N N N N

DB0C A UR copy pair cannot beresynchronized (with the DELTAJNL

parameter or ALLJNL parameter)

because the volume is specified.

N N N Y N N N N

E80B Registration to EXCTG has failedbecause the expanded shared memorytable necessary for the EXCTG

registration has not been initialized.

N N N Y N N N N

E826 Deletion from EXCTG has failedbecause the specified EXCTG is notregistered.

N N N Y N N N N

E82F Deletion from EXCTG has failedbecause the specified journal group isnot registered.

N N N Y N N N N

E843 A UR copy pair cannot be madebecause the CLPR number of thespecified volume and the CLPR numberof the journal group do not match.

N N N Y N N N N

E869 A UR copy pair cannot beresynchronized. Possible reasonsinclude both of the following:

• The R-JNL of the specified UR copypair is being used by a UR copypair that has another mirror ID.

• The mirror status of another URcopy pair that is using the specified

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

UR copy pair is Halting or

Stopping.

E86B A UR copy pair cannot be dissolvedbecause the specified volume is not aUR copy pair.

N N N Y N N N N

E86D A UR copy pair cannot be dissolvedbecause the storage system is beingturned on.

N N N Y N N N N

E86E A UR copy pair cannot be madebecause a specified volume's SM is notpresent.

N N N Y N N N N

E871 A UR copy pair cannot be madebecause inter-DKC logical paths (forboth directions) have not been defined.Make sure that inter-DKC logical pathshave already been established in bothdirections.

N N N Y N N N N

E876 A UR copy pair cannot be madebecause the storage system serialnumber specified for the S-VOL isinvalid.

N N N Y N N N N

E878 A UR copy pair could not be madebecause there is mix of volumes withemulation types are 3390-9A andnon-3390-9A in the specified journalgroup.

N N N Y N N N N

E87B A UR copy pair cannot be madebecause the specified journal group isnot registered.

N N N Y N N N N

E87C A UR copy pair cannot be madebecause a journal volume is notregistered in the specified journalgroup.

N N N Y N N N N

E87D A UR copy pair cannot beresynchronized because the specifiedvolume is not a UR copy pair.

N N N Y N N N N

E87E A UR copy pair cannot be madebecause the specified P-VOL or S-VOLis a volume comprising a journal group.

N N N Y N N N N

E880 A UR copy pair cannot be madebecause the emulation type for thespecified P-VOL or S-VOL does notmatch the emulation type for a volumecomprising a journal group.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

E881 A UR copy pair cannot be made orresynchronized because the storagesystem is being turned on.

N N N Y N N N N

E882 A UR copy pair cannot be madebecause the emulation type for thevolumes comprising the specified M-JNLgroup does not match that of the R-JNLgroup.

N N N Y N N N N

E885 A UR copy pair cannot be madebecause the specified R-JNL group hasalready been made into a copy pairwith another M-JNL group.

N N N Y N N N N

E888 A UR copy pair cannot be madebecause the specified M-JNL group hasalready been made into a copy pairwith another R-JNL group.

N N N Y N N N N

E889 A UR copy pair cannot be madebecause the specified journal group hasalready been made into a UR copy pairby using another mirror ID.

N N N Y N N N N

E890 A UR copy pair cannot be made for oneof the following reasons:

• The specified volume is alreadyregistered in another journalgroup.

• The specified volume is alreadyregistered in the same journalgroup by using the same mirror ID.

• The specified S-VOL is alreadyregistered in the same journalgroup by using another mirror ID.

• The specified journal group is notset to be used in a 3DC (URxUR)configuration, but there is a copypair that has another mirror ID inthe journal group.

N N N Y N N N N

E891 A UR copy pair cannot be madebecause the maximum number of copypairs has already been registered in thespecified M-JNL or R-JNL group.

N N N Y N N N N

E894 A UR copy pair cannot be created in a3DC (URxUR) configuration becausethe third mirror ID is specified in thesame journal group.

N N N Y N N N N

E896 Registration to EXCTG has failedbecause the UR program product or the

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

Disaster Recovery Extended programproduct has not been installed.

E897 A UR copy pair cannot be created forone of the following reasons:

• The specified M-JNL and R-JNLgroups are not set to be used in3DC (URxUR) configurations.

• The specified R-JNL group isalready in use.

• Another mirror ID is alreadydefined for the specified journalgroup.

N N N Y N N N N

E898 A UR copy pair cannot beresynchronized because the specifiedR-JNL group is in use as an R-JNLgroup for a UR copy pair with another

mirror ID.

N N N Y N N N N

E89A A UR copy pair cannot be madebecause an inter-DKC logical path hasnot been established in the forward orreverse direction. Make sure that inter-DKC logical paths have already beenestablished in both directions.

N N N Y N N N N

E89B A UR copy pair cannot be madebecause the status from the previousconnection with another storagesystem remains in the specified M-JNLor R-JNL group.

Specify a different journal group, ordelete the specified journal group andthen register it again.

N N N Y N N N N

E8A2 A UR copy pair cannot be made for oneof the following reasons:

• The serial number of the storagesystem specified for the S-VOL isincorrect.

• Another path group ID is alreadyassigned for the specified journalgroup.

N N N Y N N N N

E8A6 A resynchronization that reverses the

copy direction for UR copy pairs cannotbe performed because the journalgroup of the specified volume is notregistered in the storage system.

N N N Y N N N N

E8A7 A resynchronization that reverses thecopy direction for UR copy pairs cannotbe performed because a journal volumeis not registered in the storage system

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

for the journal group of the specifiedvolume.

E8A8 The specified copy pair cannot besuspended because it is not a UR copypair, or the P-VOL and S-VOL for journal group do not match.

N N N Y N N N N

E8A9 A UR copy pair cannot be suspendedbecause the storage system is beingturned on.

N N N Y N N N N

E8B6 A delta resync pair cannot be madebecause the mirror ID of the specifiedR-JNL group is used by another URcopy pair.

N N N Y N N N N

E8B9 A delta resync pair cannot be madebecause the specified journal group isregistered to EXCTG.

N N N Y N N N N

E8BB Registration to EXCTG has failedbecause the mirror ID is different fromthe registered mirror ID.

N N N Y N N N N

E8BD Registration to EXCTG has failedbecause the number of journal groupsto be registered exceeded themaximum number which can beregistered.

N N N Y N N N N

E8BF Registration to EXCTG has failedbecause the number of subordinatestorage systems has exceeded themaximum number which can be

registered.

N N N Y N N N N

Table 2-19 Details of error codes EAxx

Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EA00 A UR copy pair cannot be madebecause the specified volumecomprises an R-JNL group.

N N N Y N N N N

EA01 A UR copy pair cannot be made foreither of the following reasons:

• An attempt was made to make acopy pair that already exists.

• The specified P-VOL or S-VOL forthat UR copy pair is already in useby another copy pair.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EA02 A UR copy pair cannot be madebecause the specified volumecomprises an M-JNL group.

N N N Y N N N N

EA03 A UR copy pair cannot be madebecause the specified S-VOL is alreadyin use as another UR copy pair.

N N N Y N N N N

EA07 A UR copy pair cannot be madebecause the number of copy pairs thatcan be registered in the specified M-JNLgroup has exceeded the maximumlimit.

N N N Y N N N N

EA08 A UR copy pair cannot be madebecause the number of copy pairs thatcan be registered in the specified R-JNLgroup has exceeded the maximumlimit.

N N N Y N N N N

EA09 A UR copy pair cannot be madebecause the M-JNL group is not in theInitial, Active, or Stop status.

N N N Y N N N N

EA0A A UR copy pair cannot be madebecause the status of the R-JNL groupis incorrect.

N N N Y N N N N

EA12 The UR copy pair could not beresynchronized in the reverse directionbecause the copy pair is not in theSWAPPING status.

N N N Y N N N N

EA13 A UR copy pair cannot be

resynchronized because the volumespecified for the P-VOL is the S-VOL of the UR copy pair.

N N N Y N N N N

EA15 A UR copy pair cannot beresynchronized because the volumespecified for the S-VOL is the P-VOL of the UR copy pair.

N N N Y N N N N

EA18 A UR copy pair cannot beresynchronized because the copy pair isnot in the suspend status.

N N N Y N N N N

EA19 A UR copy pair cannot beresynchronized because the journal

group is not in the Stop status.

N N N Y N N N N

EA1B The YKRESYNC command with the

PREPARE parameter could not be

executed because the specified journalgroup is either not in the suspendstatus to obtain the journal data as

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

differential data, or not in failurestatus.

EA1C A UR copy pair resynchronization,which causes a copy direction reversal,cannot be made because the R-JNLgroup of the S-VOL is not in the Stopstatus.

N N N Y N N N N

EA1E A resynchronization that reverses thecopy direction for UR copy pairs cannotbe performed because the specified S-VOL is not the S-VOL of the UR copypair.

N N N Y N N N N

EA20 A resynchronization that reverses thecopy direction for UR copy pairs cannotbe performed because the specified P-VOL is not the P-VOL of the UR copy

pair.

N N N Y N N N N

EA22 A UR copy pair resynchronization,which causes a copy direction reversal,cannot be made because the journalgroup is not in the Stop status.

N N N Y N N N N

EA25 A UR copy pair resynchronization,which causes a copy direction reversal,cannot be made because the copy pairis not in the SWAPPING status.

N N N Y N N N N

EA29 A UR copy pair cannot be dissolvedbecause the M-JNL group is not in theActive or Stop status.

N N N Y N N N N

EA2C A UR copy pair cannot be dissolvedbecause the R-JNL group is not in theActive or Stop status.

N N N Y N N N N

EA33 A UR copy pair cannot be suspendedbecause the M-JNL group is not in theActive status.

N N N Y N N N N

EA36 A UR copy pair cannot be suspendedbecause the R-JNL group is not in theActive status.

N N N Y N N N N

EA3A A UR copy pair cannot be dissolvedbecause the specified S-VOL status isbeing changed at the moment.

N N N Y N N N N

EA3B A UR copy pair resynchronization,which causes a copy direction reversal,cannot be made because the copy pairis in the TRANS status.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EA3C A suspension that reverses the copydirection cannot be performed for theUR copy pair, because the specified S-VOL belongs to the M-JNL group.

N N N Y N N N N

EA40 A UR copy pair cannot be madebecause the charging limit of the MCUprogram product has been exceeded.

N N N Y N N N N

EA41 A UR copy pair cannot be madebecause the charging limit of the RCUprogram product has been exceeded.

N N N Y N N N N

EA46 A UR copy pair between theintermediate site and the remote sitecannot be deleted or suspendedbecause the journal group of the URcopy pair between the primary site andthe intermediate site in a 3DC Cascade

(URxUR) configuration is in the Activestatus.

N N N Y N N N N

EA4D The UR copy pair cannot be suspendedbecause it is a delta resync pair.

N N N Y N N N N

EA89 The status cannot be changed fromerror status to the delta resyncpreparatory status, because thespecified P-VOL is not in HOLDER status.

N N N Y N N N N

EA8A The status of a UR copy pair cannot bechanged because the primary storagesystem is currently being turned on orturned off.

N N N Y N N N N

EA95 A copy pair cannot be created becausethe pool of the HDPz volume specifiedfor the P-VOL of a UR copy pair is beinginitialized.

N N N Y N N N N

EAA0 The UR copy pair cannot be operatedfor each EXCTG because of thefollowing reasons:

• The JNLG specified in the copygroup is not registered in theEXCTG.

• There is a copy pair with a statusthat is TRANS.

N N N Y N N N N

EAA2 A UR copy pair cannot be madebecause the charging limit of UR in theMCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EAA3 A UR copy pair cannot be madebecause the charging limit of TC in theRCU has been exceeded. Check thelicense capacity of this and all related

program products.

N N N Y N N N N

EAA5 A UR copy pair cannot be madebecause the charging limit of UR in theRCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N

EAA6 A UR copy pair cannot be madebecause the charging limit of TC in theMCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N

EABC A UR copy pair cannot be made

because shared memory is notimplemented for the specified LDEVnumber.

N N N Y N N N N

EAD0 A UR copy pair cannot be made withthe HOLD parameter specified because

the micro does not support the deltaresync function.

N N N Y N N N N

EAE5 A copy pair cannot be created becausethe HDPz volume specified for the P-VOL of a UR copy pair is beingexpanded.

N N N Y N N N N

EAE7 A UR copy pair cannot be dissolved

because mode 707 of a storage systemoption is ON and the specified volumeis part of a TC copy pair.

N N N Y N N N N

EAF6 A UR copy pair could not be made withthe HOLD parameter, or a UR copy pair

could not be resynchronized becausethe copy pair was in a status for whichstatus transition could not beperformed.

N N N Y N N N N

Table 2-20 Details of error codes EBxx

Errorcode

Error detailsType of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB02 A UR copy pair status cannot bechanged because the specified journalgroup number is invalid.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB08 Registration to or deletion from EXCTGhas failed because the micro is beingreplaced, or there are intermixedmicros which do not support 4x4

configuration.

N N N Y N N N N

EB09 Registration to or deletion from EXCTGhas failed because the enteredparameter was incorrect.

N N N Y N N N N

EB0A Registration to or deletion from EXCTGhas failed because another EXCTGregistration or deletion process is inprogress.

N N N Y N N N N

EB0F Registration to or deletion from EXCTGhas failed because the specified deviceis not an arbitration command device.

N N N Y N N N N

EB24 A delta resync pair cannot be madebecause the S-VOL of the specifiedcopy pair is in one of the followingstatuses:

• It is not the S-VOL of a UR deltaresync copy pair.

• The status of the UR delta resynccopy pair is not Duplex.

N N N Y N N N N

EB25 A delta resync pair cannot be executedbecause the S-VOL of the specifiedcopy pair is in one of the followingstatuses.

• It is not the S-VOL of a UR deltaresync copy pair.

• The status of the UR delta resynccopy pair is not Duplex, SuspOp,SuspEr, or SuspCu.

N N N Y N N N N

EB28 A UR copy pair cannot be madebecause the Disaster RecoveryExtended program product has notbeen installed in the RCU.

N N N Y N N N N

EB2D A UR copy-pair operation cannot beperformed because the shared memorynecessary for using UR is notimplemented.

N N N Y N N N N

EB30 A UR copy pair status cannot bechanged because the specified mirrorID is invalid.

N N N Y N N N N

EB37 A UR copy-pair operation cannot beperformed because the microcode iscurrently being changed.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB38 When making a copy pair using thesame journal group number and mirrorID as an existing copy pair, you cannotspecify a secondary storage system

that differs from the secondary storagesystem of the existing copy pair.Therefore, a UR copy pair cannot bemade.

This error occurs if there is more thanone secondary storage system in thesame copy group or when the specified journal group number and mirror IDare used for another copy group.

N N N Y N N N N

EB3B The batch pair status command cannotbe executed because the CU numberspecified by the YKEWAIT command or

YKRSCAN command is not supported by

this model.

N N N N N N N Y

EB3C A UR copy pair status cannot bechanged because the specified serialnumber or SSID of the primary storagesystem does not match the actual serialnumber or SSID of the primary storagesystem.

N N N Y N N N N

EB3D A UR copy pair status cannot bechanged because the specified serialnumber or SSID of the secondarystorage system does not match theactual serial number or SSID of thesecondary storage system.

N N N Y N N N N

EB48 A delta resync pair cannot be made.The reason might be one of thefollowing:

• The P-VOL of a TC copy pair andanother P-VOL of a UR copy pair donot match.

• The storage system serial numberon the copy source is incorrect.

N N N Y N N N N

EB49 A delta resync pair cannot be madebecause the delta resync function is notsupported in the RCU.

N N N Y N N N N

EB4C A UR copy pair cannot be madebecause the specified R-JNL group isnot registered.

N N N Y N N N N

EB4D A UR copy pair cannot be madebecause the specified M-JNL group isnot registered in the storage system.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB4F A UR copy pair cannot be madebecause the timer type for M-JNLGdiffers from that for R-JNLG.

N N N Y N N N N

EB50 A UR copy pair cannot be madebecause the specified volume does notexist.

N N N Y N N N N

EB51 A UR copy pair cannot be madebecause the specified S-VOL has PINdata.

N N N Y N N N N

EB52 A UR copy pair cannot be madebecause the specified S-VOL cannot beaccessed.

N N N Y N N N N

EB53 A UR copy pair cannot be madebecause the specified S-VOL is blocked.

N N N Y N N N N

EB56 A UR copy pair cannot be madebecause the status of the cache isabnormal.

N N N Y N N N N

EB5B A UR copy pair cannot be madebecause the LDEV guard is set for thespecified P-VOL or S-VOL.

N N N Y N N N N

EB5D A UR copy pair cannot be madebecause the LDEV security is set for thespecified P-VOL or S-VOL.

N N N Y N N N N

EB5E A UR copy pair cannot be madebecause the S-VOL is not in theSIMPLEX status. Alternatively, a UR

copy pair cannot be resynchronizedbecause the S-VOL is not in thesuspend status.

N N N Y N N N N

EB5F A UR copy pair cannot be madebecause the UR program product is notinstalled on the secondary storagesystem.

N N N Y N N N N

EB60 A UR copy pair cannot be madebecause the capacities of the P-VOLand S-VOL do not match.

N N N Y N N N N

EB61 A UR copy pair cannot be madebecause the path between the primarystorage system and the secondarystorage system is invalid.

N N N Y N N N N

EB62 A UR copy pair cannot be madebecause the specified P-VOL is acommand device.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB63 A UR copy pair cannot be madebecause another journal group pair hasbeen already made in the R-JNL group.

N N N Y N N N N

EB64 A UR copy pair cannot be madebecause the charging limit of theprogram product has been exceeded.

N N N Y N N N N

EB6B A UR copy pair cannot be createdbecause the specified S-VOL satisfiesone of the following conditions:

• The S-VOL is being used forFlashCopy.

• The S-VOL is being used forFlashCopy SE.

• The S-VOL is a TSE-VOL.

N N N Y N N N N

EB6E A UR copy pair cannot be made

because the UR program product is notinstalled on the primary storagesystem.

N N N Y N N N N

EB6F A UR copy pair cannot beresynchronized because the microversion on the primary storage systemdoes not support the 4x4 configuration.

N N N Y N N N N

EB70 A UR copy pair cannot be madebecause the S-VOL had already beenpaired by another program product.

N N N Y N N N N

EB73 A UR copy pair cannot be madebecause the S-VOL is a system

residence volume.

N N N Y N N N N

EB74 A UR copy pair cannot be madebecause all of the channel adaptersconnected to the mainframe areblocked.

N N N Y N N N N

EB78 A UR copy pair cannot be madebecause the S-VOL is a commanddevice.

N N N Y N N N N

EB79 A UR copy pair cannot be made orresynchronized because the S-VOL isonline.

N N N Y N N N N

EB7A A UR copy pair cannot be madebecause a journal cache remains in theR-JNL group.

N N N Y N N N N

EB7D A UR copy pair cannot be madebecause the specified S-VOL is anexternal volume.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EB7E A UR copy pair cannot be made. Thereason might be one of the following:

• The specified S-VOL is being usedin a FlashCopy relation.

• The specified S-VOL is being usedfor the S-VOL of an SI copy pair.

• The specified S-VOL is being usedfor the S-VOL of an SI copy pair,and is being resynchronized in thereverse direction or is being sharedwith the TC copy pair.

• The specified S-VOL is a Reservevolume.

• The specified S-VOL is an HDPzvolume and is being used byanother program product.

• The specified S-VOL is being usedas the P-VOL of an SI copy pairwith a C/T group ID, and is alsobeing used by another programproduct as the P-VOL of an SI copypair with a C/T group ID.

N N N Y N N N N

EB7F A UR copy pair cannot be madebecause the emulation type of thespecified S-VOL is not supported.

N N N Y N N N N

EB87 A UR copy pair cannot be made. Thereason might be one of the following:

• The path from the secondary

storage system to the primarystorage system is not set.

• The S-VOL is in the SIMPLEX

status.

N N N Y N N N N

EB88 A UR copy pair could not be madebecause of one the following reasons:

• The specified S-VOL is alreadybeing used as the S-VOL of an SIcopy pair.

• The specified volume is in NotReady status.

• The LDEV guard (PROTECT) is set

for the S-VOL.

N N N Y N N N N

EB89 A UR copy pair cannot be madebecause the emulation types of thespecified P-VOL and S-VOL do notmatch.

N N N Y N N N N

EB8A A UR copy pair cannot be madebecause the emulation types of the

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

specified M-JNL group and R-JNL groupdo not match.

EB94 A UR copy pair status cannot bechanged because the status of thespecified copy pair does not allow thestatus transition.

N N N Y N N N N

EBA0 A UR copy pair status cannot bechanged because the specified S-VOL isnot installed.

N N N Y N N N N

EBA7 A UR copy pair cannot be madebecause the HDPz volume specified forthe S-VOL satisfies one of the followingconditions:

• The capacity is being expanded.

• The pages are being released.

• The pool of the correspondingHDPz is being initialized.

N N N Y N N N N

EBA8 The command could not be executedbecause the remote command hasbeen issued to a volume that is notinstalled.

N N N Y N N N N

EBB3 The remote command cannot beexecuted because the command devicehas not been defined.

N N N N Y N N N

EBBD The command could not be executedbecause the command device is underLDEV guard.

N N N N Y N N N

EBC6 A delta resync pair cannot be madebecause the S-VOL of the specifiedcopy pair is used by another programproduct (SI/FlashCopy).

N N N Y N N N N

EBCE A UR copy pair cannot beresynchronized (with the DELTAJNL

parameter) because the specified S-VOL has old differential information.Execute the UR copy pairresynchronization (with the ALLJNL

parameter).

N N N Y N N N N

EBD0 The remote command cannot be

executed because the path between thespecified storage system or CU (SSID)and the command target storagesystem is not set, or because an errorhas occurred on the path.

N N N N N Y N Y

EBD3 The path for the remote commandtransfer route for the second siteonwards, or for the command device,

N N N N N N N Y





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

might not be set, or a failure occurredin the remote command transfer route.Make sure that the path and thecommand device are set, available, and

have not failed, and then re-executethe operation.

EBD9 A UR copy pair cannot be madebecause the charging limit of TC in theRCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N

EBDA A UR copy pair cannot be madebecause the charging limit of TCA inthe RCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N

EBDB A UR copy pair cannot be madebecause the charging limit of UR in theRCU has been exceeded. Check thelicense capacity of this and all relatedprogram products.

N N N Y N N N N

EBE0 A UR copy pair cannot be madebecause the specified S-VOL is part of adelta resync UR copy pair.

N N N Y N N N N

EBE1 A delta resync cannot be executedbecause none of the S-VOLs of thedelta resync pair are the S-VOLs of theother UR.

N N N Y N N N N

EBE2 A delta resync cannot be executedbecause the differential bitmapinformation is not in the ready status todelta resync. To overwrite the S-VOL of the delta resync pair with the P-VOL'sdata, execute the YKRESYNC command

with the ALLJNL parameter.

This error may occur because the TCupdate data (master journal of thedelta UR pair) and the update data of the restore journal maintained by theUR pair is inconsistent.

N N N Y N N N N

EBE5 A UR copy pair cannot be made or

resynchronized because the journalvolume of the specified R-JNL isblocked.

N N N Y N N N N

EBEB A UR copy pair cannot be made orresynchronized because the emulationtype of the specified volume is3390-9A.

N N N Y N N N N





Errorcode

Error details

Type of error

SI TC TCA UR CMDPAT

HHDT

zOthe

r

EBF2 Resynchronization in the reverse copydirection cannot be performed for a URcopy pair because the UR ATTIMEsuspend time is already set.

N N N Y N N N N

EBF3 A delta resync pair cannot be madebecause the UR ATTIME suspend timeis already set.

N N N Y N N N N

EBFD A UR copy pair cannot be madebecause the specified sub C/T ID is notregistered in the storage system.

N N N Y N N N N





Acronyms and Abbreviations

The following acronyms and abbreviations might be used in this guide.

A

APIapplication programming interface

B

Business Continuity ManagerA generic name for the following products:Hitachi Business Continuity Manager BasicHitachi Business Continuity Manager Universal Replicator 4x4 Extended CTG

C

C/T IDconsistency group ID

CCAcommand control address

CHA

channel adapter

CLIcommand line interface

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Acronyms-1




CSBchannel status byte

CUcontrol unit

DDAD

device address domain

DASDdirect access storage device

DBCSdouble byte character set

Device Manager

Hitachi Device Manager

DKCdisk controller

DSBdevice status byte

DSORGdata set organization

E

EXCTGextended consistency group

G

GTFgeneralized trace facility


Acronyms-2




H

HDPzHitachi Dynamic Provisioning Software for Mainframe

HDTzHitachi Dynamic Tiering Software for Mainframe

HTTPHyperText Transfer Protocol

HTTPSHyperText Transfer Protocol Security

I

IBM® HTTP Server

IBM® HTTP Server for z/OS®

IDIdentifier

IPv4Internet Protocol Version 4

IPv6Internet Protocol Version 6

ISPFinteractive system productivity facility

L

LDEVlogical device

LPAR logical partition


Acronyms-3




M

M-JNLmaster journal

Mainframe AgentHitachi Device Manager Mainframe Agent

MCUmain control unit

MIHmissing interrupt handler

O

OS

operating system

P

P-VOLprimary volume

PPRCPeer to Peer Remote Copy

PSWprogram status word

R

R-JNLrestore journal

RACFresource access control facility

RAIDredundant array of independent disks


Acronyms-4





Acronyms-8




Index

D

Details of error codes 2-2

IIdentifying 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

User completion codes 1-166

Index-1




Index-2


Hitachi Business Continuity Manager Messages

Documents

Transcript of Hitachi Business Continuity Manager Messages