This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/23/2019 Hitachi Business Continuity Manager Messages
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.
Document organization............................................................................................. viiRelated documents.................................................................................................. viiiDocument conventions.............................................................................................. ixConventions for storage capacity values...................................................................... x
Accessing product documentation...............................................................................xiGetting help..............................................................................................................xiComments................................................................................................................ xi
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
• 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-04 October 2006 Revision 4, supersedes and replacesMK-94RD262-03
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
MK-94RD262-08 May 2008 Revision 8, supersedes and replacesMK-94RD262-07
vi Preface
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
• 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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YK8007I PRTCON
time Synchronizationpercentage decreased, CopyGroup: cgid .
The copy progress percentage for the copy groupidentified by cgid is decreasing.
time
Message output time
This is only displayed when the output destinationis SYSTSPRT.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
STATUS :cgsastat ,cgsaact ,cgsaopt
WHEN STATUS status DOACTION 'action;err-action;'
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 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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
Message ID Message text Explanation and recommended actions
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
Additional information about the error message
If no additional information is available, a space isdisplayed.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
count
Number of Hitachi storage-system devices
YKC033I MSGSC=4 (count )
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
YKC034E MSGSC=32 RC=32
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)
Message ID Message text Explanation and recommended actions
YKD000T TSORC=48
Supplied parameters invalid Invalid parameters are specified.
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
No message MSG() supplied Nothing is assigned to the MSG parameter.
YKD001E MSGSC=48 RC=48
No results STEM() supplied Nothing is assigned to the STEM parameter.
YKD002E MSGSC=48 RC=48
Copy Group STEM(stem)does not include trailing "."
The last character of the STEM parameter is not a
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
Messages MSG(stem) doesnot include trailing "."
The last character of the MSG parameter is not a period.
stem
1-32 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKG008E MSGSC=48 RC=48
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.
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
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.
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
YKG054E MSGSC=36 RC=36(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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
YKG074E MSGSC=36 RC=36(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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
YKG075W MSGSC=4 RC=4(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.
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
YKG076W MSGSC=4 RC=4(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.
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.
name
XML attribute name
value
XML attribute value
file
1-38 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
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.
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 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.
YKG085E MSGSC=40 RC=40(file:rec#)
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
YKG089E MSGSC=40 RC=40(file)
File Close error: dsstate. An attempt to close the configuration file identified byfile failed.
dsstate
Messages 1-39
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Maximum value among the output return codes
Table 1-8 List of messages (message ID YKG2x - YKK10x)
Message ID Message text Explanation and recommended actions
YKG201E MSGSC=48 RC=48
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
configuration element, but DDSN is defined for thisvalue.
Correct the specification on the line with the linenumber identified by rec# in the file identified by file.
file
Name of the configuration file where the error was
detectedrec#
Number of the line in the file identified by filewhere the error was detected
YKG286E MSGSC=36 RC=36(file:rec#)
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
Name of the configuration file where the error wasdetected
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.
YKG295E MSGSC=44 RC=44(file:rec#)
The element stack wasoverflowed.
The internal routine encountered a shortage of workspace.
Contact Technical Support for assistance.
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
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
• 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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Maintenance information
message-text
Error message
message-value
Additional information about the error message
If no additional information is available, a space is
displayed.
message-severity
Additional information about the error message
If no additional information is available, a space isdisplayed.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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#
The control unit number of the detected undefinedvolume
CCA#
The command control address number of thedetected undefined volume
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#
The control unit number of the detected undefinedvolume
CCA#
The command control address number of thedetected undefined volume
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Unable to execute withoutvalid name parameter.
Nothing or an invalid value is assigned to theparameter identified by name.
name
Parameter name
YKJ001E TSORC=48
name parameter is too long. The parameter identified by name is too long.
name
Parameter name
YKJ002E TSORC=48
The specified PREFIX isbeing used by anotherprogram.
The specified prefix is being used by another program.
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
Maintenance information
message-text
Error message
message-value
Additional information about the error message
1-48 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
If no additional information is available, a space isdisplayed.
message-severity
Additional information about the error message
If no additional information is available, a space isdisplayed.
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.
Message ID Message text Explanation and recommended actions
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
dd name of the CSV file where the error wasdetected
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
dd name of the CSV file where the error wasdetected
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
dd name of the CSV file where the error wasdetected
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
1-52 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Number of the line in the file identified by dd-namewhere the error was detected
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#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
• 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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
1-54 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Number of the line in the file identified by dd-namewhere the error was detected
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
dd name of the CSV file where the error wasdetected
rec#
Number of the line in the file identified by dd-namewhere the error was detected
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
DD name of the CSV file where the error wasdetected
rec#
Line number in the file dd-name where the errorwas detected
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
DD name of the CSV file where the error wasdetected
rec#
1-56 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
YKK103E TSORC=32
Acquisition of host IDsettingsfailed,service=service-name,code=code1,code2.
Host ID 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.
Table 1-9 List of messages (message ID YKL0x)
Message ID Message text Explanation and recommended actions
YKL000T TSOSC=48
Supplied parameters invalid. Invalid parameters have been specified.
YKL001E TSORC=48
Unable to execute withoutvalid MSG() parameter.
Specify a valid MSG parameter.
YKL002E TSORC=48
MSG(stem) does not includetrailing "." character.
The last character of the MSG parameter is not a period.
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
Stem name assigned to the MSG parameter
YKL004E MSGSC=48 RC=48
Unable to execute withoutvalid STEM() parameter.
Specify a valid STEM parameter.
YKL005E MSG
SC=48 RC=48
STEM(stem) does not
include trailing "." character.
The last character of the STEM parameter is not a
period.
stem
Stem name assigned to the STEM parameter
YKL006E MSGSC=48 RC=48
Unable to execute withoutvalid PREFIX parameter.
Specify a valid PREFIX parameter.
1-58 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKL007E MSGSC=48 RC=48
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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
YKL053W 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.
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
YKL054E MSGSC=36 RC=4(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.
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
Messages 1-59
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
rec#
Number of the line in the file identified by filewhere the error was detected
YKL074E MSGSC=36 RC=36(file: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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
YKL075W MSGSC=4 RC=4(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.
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
YKL076W MSGSC=4 RC=4(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.
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.
name
XML attribute name
value
XML attribute value
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
1-60 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKL077W MSGSC=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.
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
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.
YKL080E MSGSC=36 RC=36(file:rec#)
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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
See the pair index description in the explanation of the YKE003E message.
YKL082W MSGSC=8 RC=8( pair-index )
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
See the pair index description in the explanation of the YKE003E message.
YKL083W MSGSC=12 RC=12( 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
See the pair index description in the explanation of the YKE003E message.
YKL085E MSGSC=40 RC=40(file:rec#)
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 error wasdetected
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.
YKL088E MSGSC=40 RC=40(file)
File Open error: dsstate. An attempt to open the configuration file identified byfile failed.
dsstateStatus of the configuration file
file
Name of the configuration file in which the errorwas detected
1-62 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Maximum value among the output return codes
Messages 1-63
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Table 1-10 List of messages (message ID YKL2x - YKL4x)
Message ID Message text Explanation and recommended actions
YKL201E MSGSC=48 RC=48
Unable to execute withoutvalid name parameter.
Nothing or an invalid value is assigned to theparameter identified by name.
YKL202E TSORC=48
"SYSAUTH". cannot bespecified in MSG()
parameter.
SYSAUTH. cannot be specified in the MSG parameter.
Specify a different name.
YKL203E MSGSC=48 RC=48
"SYSAUTH." cannot bespecified in STEM()parameter.
SYSAUTH. cannot be specified in the STEM parameter.
Specify a different name.
YKL204E TSORC=48
name parameter is too long. The parameter identified by name is too long.
YKL205E MSGSC=48 RC=48
name parameter is too long. The parameter identified by name is too long.
YKL206E MSGSC=48 RC=48
Route parameter is allowedonly on 1st call of YKLOAD
The ROUTE parameter is allowed only on the first call of
the YKLOAD command.
YKL241W MSGSC=4 RC=4(file:rec#)
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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by file
where the error was detected
YKL250E MSGSC=36 RC=36(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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
YKL251E MSGSC=36 RC=36(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
Name of the configuration file where the error wasdetected
rec#
1-64 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Correct the specification on the line with the linenumber identified by rec# in the file identified by file.
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
YKL277E MSGSC=36 RC=36(file:rec#)
name element missing. The XML element name is missing.
Correct the specification on the line with the linenumber identified by rec# in the file identified by file.
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
YKL280E MSGSC=36 RC=36(file)
No command devices werefound.
No command devices were found.
Correct the route definition in the route list definitionfile shown in file.
file
Name of the configuration file where the error wasdetected
YKL281E MSGSC=36 RC=36(file:rec#)
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.
fileName of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by filewhere the error was detected
YKL282E MSGSC=36 RC=36(file)
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
Name of the configuration file where the error wasdetected
YKL283E MSGSC=36 RC=36(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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Name of the configuration file where the error wasdetected
rec#
Number of the line in the file identified by file
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.
YKL291E MSGSC=36 RC=36
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.
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.
1-68 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKL293W MSGCON SC=0 RC=0
Your function license willexpire in n day(s).
The license (function) will expire in n days.
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.
YKL295E MSGSC=44 RC=44(file:rec#)
The element stack wasoverflowed.
The internal routine encountered a shortage of workspace.
Contact Technical Support for assistance.
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
YKL298E MSGTSO SC=44RC=44 (detailed-info)
CLI-name encountered anunexpected error.
An unexpected error has occurred. This error mighthave 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).
• 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).
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
YKL419E MSGSC=48 RC=48
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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)
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
YKM056E MSGSC=36 RC=48
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.
YKM058E MSGSC=36 RC=48
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.
Table 1-12 List of messages (message ID YKM1x - YKM5x)
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Maintenance information
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
The specified prefix is being used by another program.
Check the value specified for the prefix.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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)
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
Contact Technical Support for assistance.
YKM906E TSO A FREEMAIN error occurred. A FREEMAIN error occurred. However, the program willcontinue to run.
Contact Technical Support for assistance.
Table 1-15 List of messages (message ID YKN0x)
Message ID Message text Explanation and recommended actions
YKN000T TSORC=48
Supplied parameters invalid Invalid parameters are specified.
For details, see the reason code in the YKN099I
message that will appear after this message. Forreason codes, see IKJPARS in the TSO/E ProgrammingServices.
Messages 1-81
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
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
If the device cannot be identified, ** is displayed.
pair-index
See the pair index description in the explanation of the YKE003E message.
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
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
If the device cannot be identified, ** is displayed.
pair-index
See the pair index description in the explanation of the YKE003E message.
Messages 1-85
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
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
If the device cannot be identified, ** is displayed.
pair-index
See the pair index description in the explanation of the YKE003E message.
Message ID Message text Explanation and recommended actions
Stem name assigned to the MSG parameter
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
Stem name assigned to the MSG parameter
YKS004E MSGSC=48 RC=48
Unable to execute withoutvalid STEM() parameter.
Specify a valid STEM parameter.
YKS005E MSGSC=48 RC=48
STEM(stem) does notinclude trailing "." character.
The last character of the STEM parameter is not a
period.
stemStem name assigned to the STEM parameter
YKS006E MSGSC=48 RC=48
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.
YKS085E MSGSC=44 RC=44
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Name of the configuration file where the error wasdetected
YKS098E MSGSC=36 RC=36
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
Maximum value among the output return codes
Table 1-20 List of messages (message ID YKS2x)
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
environment. (YKVGET result= result )
subroutine has not properly been invoked or thatBusiness Continuity Manager has not properly beeninstalled.
stem
Stem name assigned to the MSG parameter
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.
YKS260E MSGSC=44 RC=44
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.
YKS270E MSGSC=44 RC=44
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Status of the configuration file
• 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.
Message ID Message text Explanation and recommended actions
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).
• The ISPF log (not necessary if this command wasexecuted from a script).
• 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)
Message ID Message text Explanation and recommended actions
YKT001E CON Can't find SVCTABLE The "SVCTABLE" search in the NUCLKUP macro failed.The program abnormally terminates with usercompletion code 996.
Contact HDS Technical Support for assistance.
YKT002E CON Can't find IGCERROR The "IGCERROR" search in the NUCLKUP macro failed.The program abnormally terminates with usercompletion code 996.
Contact HDS Technical Support for assistance.
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.
Contact HDS Technical Support for assistance.
YKT005E CON Couldn't create name/token Name/Token registration failed. The programabnormally terminates with user completion code 996.
Contact HDS Technical Support for assistance.
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.
Contact HDS Technical Support for assistance.
YKT008E CONRC=20
System task started withoutSTART from TSO.
The YKALCSVC command was executed in the TSO/E
environment.
1-92 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
Contact HDS Technical Support for assistance.
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.
Contact HDS Technical Support for assistance.
YKT024E CON Couldn't copy load module Copying of the load module failed. The programabnormally terminates with user completion code 996.
Contact HDS Technical Support for assistance.
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.
Table 1-22 List of messages (message ID YKT2x)
Message ID Message text Explanation and recommended actions
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.
Contact HDS Technical Support for assistance.
YKT212E CONRC=12
Couldn't register Name/Token
An error occurred during Name/Token registration. Theprogram stops processing.
Messages 1-93
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Contact HDS Technical Support for assistance.
YKT213E CONRC=4
Couldn't take Name/Token An error occurred during acquisition of Name/Token.The program stops processing.
Contact HDS Technical Support for assistance.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
This message is always displayed to indicate the returncode and the reason code.
nnnn
Maximum among the severity codes returnedduring command execution
Table 1-26 List of messages (message ID YKW0x)
Message ID Message text Explanation and recommended actions
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
command in the Hitachi Business Continuity Manager Reference Guide.
Messages 1-99
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKX010E 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
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.
Message ID Message text Explanation and recommended actions
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.
Message ID Message text Explanation and recommended actions
• 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
System 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
Maintenance information
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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-target- port-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
Number used to identify the processing task thatoutput the message
request-name
• @OPNSAP: Preprocessing
• @OPEN: Processing for establishing a connection
• @SEND: Send processing
• @RECV: Receive processing
• @CLOSE: Processing for releasing the connection
• @QUERY: Remote address search processing
• @ABORT: Forcibly releasing the connection
• @QUIT: Postprocessing
response-code
Code generated during the request shown 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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Business Continuity Manager agent. Once the error iscorrected, start the TCP/IP program, and then start theBusiness Continuity Manager agent.
maintenance-information
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-target- port-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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
• 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
• ALLOCATE: An allocation error
• 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
• ALLOCATE: An allocation error
Make sure that the file indicated by file exists.
Messages 1-111
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Message output time (local time)
task-ID
Identification number of the processing task towhich the message was output
command
Messages 1-113
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
GR 08-11 contents-of-register-8 contents-of-register-9 contents-of-register-10 contents-of-register-11
GR 12-15 contents-of-register-12 contents-of-register-13 contents-of-register-14 contents-of-register-15
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
was called, relative to the top of the module
pppppppp pppppppp
PSW during the abnormal termination
1-114 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
Check, and, if necessary, revise the specified request.
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
• ALLOCATE: An allocation error
Make sure that the copy group cgnameconfiguration file exists.
1-116 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
• EXECIO: An input error
Make sure that the configuration file of the copygroup cgname has not been broken.
• format: An XML format error
Make sure that the XML description does notcontain an error.
• 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)
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Maximum among the severity codes returnedduring command execution
Table 1-36 List of messages (message ID YKZ10x - YKZ20x)
Message ID Message text Explanation and recommended actions
YKZ103E MSGSC=48
Parameters combination isinvalid
The parameter combination is invalid.
1-118 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
nnn (decimal number)
Return code of the GTRACE macro
mmm (decimal number)
Event ID
lll (decimal number)
Length of trace data
xxx (decimal number)
Command code of the command that wasexecuting when the error occurred
1-124 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
Command control address number
If the device cannot be identified, ** is displayed.
pair-index
See the pair index description in the explanation of the YKE003E message.
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.
Correct the content of the configuration file.
value
Number of copy groups
YKZ233E MSG
SC=36 RC=36#
(attribute-value)
Invalid Copy Group attributename
The specified copy group attribute value is invalid forthis command.
Correct the configuration file, and then re-execute the
YKLOAD command.
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.
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
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
YKZ235E MSG
SC=36 RC=36#
dad-id APID is null. No APID value is registered.
Correct the content of the configuration file.
dad-id
Device address domain ID
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
YKZ236E MSG
SC=36 RC=36#
dad-id Interface number is
null.
No interface number is registered.
Correct the content of the configuration file.
dad-id
Device address domain ID
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
Messages 1-129
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Suspension initiated by YKSUSPND ATTIME is still in
effect. Copy pair operation is canceled.
Re-execute the command after YKSUSPND ATTIME
processing ends.
YKZ239E MSGSC=48 RC=48
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.
YKZ242E MSGSC=48 RC=48
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.
YKZ243E MSGSC=48 RC=48
Supplied parameters invalid ATTIME or CANCEL is specified together with SVOL.
Correct the YKSUSPND command parameter values, and
then re-execute the command.
YKZ244E MSGSC=36 RC=36
Serial number of storagesystem is not found inRoutelist.
The specified storage system does not exist in theroute list.
serial-number
Storage system serial number
1-130 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
device-number-1 (string)
The device that issued I/O
Messages 1-135
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
device-number-1 (string)
The device that issued I/O
device-number-2 (string)
The device to be manipulated
code1 (Hexadecimal number)
Message type.
code2 (Hexadecimal number)
Reason code
code3 (Hexadecimal number)
Error code
For details about the error codes, see XXX.
code4 (Hexadecimal number)
Subcommand code
xxx (decimal number)
1-136 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
See the command code description in theexplanation of the YKZ201E message.
yyy (string)
Maintenance information
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
xxx (decimal number)
Command code of the command that wasexecuting when the error occurred
See the command code description in theexplanation of the YKZ201E message.
yyy (string)
Maintenance information
Table 1-40 List of messages (message ID YKZ27x)
Message ID Message text Explanation and recommended actions
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
YKZ271E MSGSC=12 RC=12
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
YKZ275E MSGSC=36 RC=36
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.
YKZ276E MSGSC=36 RC=36
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.
YKZ278W MSGSC=8 RC=8
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.
YKZ279W MSGSC=12 RC=12
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
YKZ280W MSGSC=0 RC=0
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
YKZ280W MSGSC=0 RC=0
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
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
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
# If this message is output while the YKLOAD command
is being executed, the RC is 44.
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
command is being executed, the RC is 44.
YKZ288E MSGSC=36 RC=36
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.
Table 1-42 List of messages (message ID YKZ29x)
Message ID Message text Explanation and recommended actions
YKZ290E MSGSC=48 RC=48
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.
xxx (decimal number)
Command code for the command that wasexecuting when the log dataset became full
1-144 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKZ299E MSGSC=36 RC=36
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)
R-JNL: Journal of the secondary site
M-JNL: Journal of the primary site
jj (hexadecimal number)
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)
ssssssssssss (decimal number)
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
YKZ370E MSGSC=32 RC=32
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKZ400E MSGSC=48 RC=48
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
YKZ401E MSGSC=48 RC=48
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
YKZ402E MSGSC=44 RC=44
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.
jj (hexadecimal number)
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)
ssssssssssss (decimal number)
The storage system serial number
nnnn (string)
The status after the transition
YKZ403I MSGSC=0 RC=0
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKZ407E MSGSC=24 RC=24
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)
jj (hexadecimal number)
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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
YKZ408E MSGSC=24 RC=24
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)
consistency group ID for ShadowImage (00-7F)
jj (hexadecimal number)
Journal group number specified for the subconsistency group ID for the Universal Replicatorthat links with ShadowImage
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.
Messages 1-155
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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)
consistency group ID for ShadowImage (00-7F)
1-156 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
jj (hexadecimal number)
Journal group number specified for the subconsistency group ID for the Universal Replicatorthat links with ShadowImage
gg (hexadecimal number)
Generation ID (00-FF)
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
Table 1-45 List of messages (message ID YKZ41x - YKZ91x)
Message ID Message text Explanation and recommended actions
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.
SUPFnc (hexadecimal number)
Value for the version of the storage systemsupport function used in the copy group
(minimum)#1
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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.
YKZ411E MSGSC=36 RC=48
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.
Re-execute the YKSUSPND command without specifying
the ATOPT parameter, or with the ATOPT(NORMAL)
parameter specified.
Messages 1-157
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKZ412E MSGSC=36 RC=48
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.
SUPFnc (hexadecimal number)
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)
Value for the version of the storage systemsupport function used in the copy group
#1
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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.
SUPFnc (hexadecimal number)
Value for the version of the storage systemsupport function used in the copy group
parameter-name
Function or configuration that cannot be used:
- UR_CTTIMEMODE: Consistency time mode for
Universal Replicator
1-158 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
- 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
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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
YKZ415E MSGSC=48 RC=48
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
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.
SUPFnc (hexadecimal number)
Value for the version of the storage systemsupport function used in the copy group(minimum)
#1
If this message is output while the YKLOAD
command is being executed, the RC is 44.
#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
YKZ417E MSGSC=48 RC=48
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.)
YKZ419E MSGSC=48 RC=48
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
Message ID Message text Explanation and recommended actions
YKZ421E MSGSC=48 RC=48
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.
YKZ422E MSGSC=48 RC=48
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
<o>: Data transfer rate (Kbps) between the main control unit and the remotecontrol unit
<p>: Offloading timer
<q>: Remote control unit ready timer
<r>: Copy pending timer
YK8318I PRT
REPORT STATS:
COPY GROUP : <a> PREFIX : <b> 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> <i> <j> <k> <l> <m> <n> <o>]
The results of REPORT(STATS) for the Universal Replicator copy group are
displayed.
<a>: Copy group ID
<b>: Prefix
<c>: Copy group host device address domain ID
<d>: Copy group type
<e>: Master journal group ID
1-164 Messages
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
<h>: Serial number of the secondary storage system
<i>: 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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-3
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
• 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
Storage system sense byte information 2-5
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-6 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-8 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
• 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
Storage system sense byte information 2-9
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-10 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Table 2-3 Details of error codes 36xx
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
2-12 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Table 2-4 Details of error codes 37xx
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
2-14 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
• 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
2-16 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Table 2-5 Details of error codes 46xx
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
Storage system sense byte information 2-17
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-19
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-25
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
• The copy pair is in the SIMPLEX
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.
• The copy pair is in the SIMPLEX
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
2-26 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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:
• The specified volume is not in a TCcopy group with a C/T group IDspecified.
• The copy pair is in the SIMPLEX
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
Storage system sense byte information 2-27
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-29
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-31
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-35
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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.
• The CU number is not supported.
N N N N N Y N N
2-36 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-48 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-49
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-50 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Table 2-15 Details of error codes C2xx
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
2-54 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-55
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-56 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-57
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-60 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-62 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-67
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-68 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-69
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-72 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-73
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-74 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-76 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-79
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
2-80 Storage system sense byte information
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Storage system sense byte information 2-81
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages
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
Hitachi Business Continuity Manager Messages
7/23/2019 Hitachi Business Continuity Manager Messages