HP XP P9000 for Business Continuity Manager Software Messages

ManualsBrandsHP ManualsStorageHP XP P9500 Disk Array

XP P9000 for Business Continuity Manager

Software Messages

Abstract

This guide describes the messages and error codes that are produced by HP Business Continuity Manager Software. In this

manual, these products are collectively referred to as Business Continuity Manager: HP Business Continuity Manager Basic

and HP Business Continuity Manager Continuous Access Journal 4x4 Extended CTG. The intended audience is a storage system

administrator or authorized service provider with independent knowledge of HP XP P9000 disk arrays and the HP Remote

Web Console.

HP Part Number: T5253-96087

Published: November 2013

Edition: Sixteenth

Summary of content (261 pages)

PAGE 1
HP XP P9000 for Business Continuity Manager Software Messages Abstract This guide describes the messages and error codes that are produced by HP Business Continuity Manager Software. In this manual, these products are collectively referred to as Business Continuity Manager: HP Business Continuity Manager Basic and HP Business Continuity Manager Continuous Access Journal 4x4 Extended CTG.
PAGE 2
© Copyright 2007, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Edition Date Description Tenth September 2011 This document revision applies to Business Continuity Manager version 6.61 and higher. Eleventh November 2011 This document revision applies to Business Continuity Manager version 6.70 and higher. Twelfth April 2012 This document revision applies to Business Continuity Manager version 6.71 and higher. Thirteenth August 2012 This document revision applies to Business Continuity Manager version 7.3 and higher.
PAGE 4
Contents 1 Messages..................................................................................................5 Message format.......................................................................................................................5 Message output format.........................................................................................................5 Notations used to describe messages.....................................................................................
PAGE 5
1 Messages This chapter describes the messages that are issued by Business Continuity Manager: The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser. Actual windows may differ depending on the operating system and browser used. GUI contents also vary with licensed program products, storage system models, and firmware versions.
PAGE 6
• YKK:YKINSCHK • YKL: YKLOAD • YKM: YKMAKE, messages displayed in the ISPF panel, or ISPFLOG • YKN: YKRUN • YKP: YKSTATS • YKQ: YKQUERY • YKR: YKRESYNC • YKS: YKSTORE • YKT: YKALCSVC, YKSETENV, or YKSDPENV • YKU: YKSUSPND • YKV: YKRECVER • YKW: YKWATCH • YKX: YKBLDCMD, YKDELCMD, or YKQRYDEV • YKY: Business Continuity Manager agent • YKZ: All commands or tools Severity levels indicate: • T: Fatal • E: Error • W: Warning • I: Notification of information Notations used to
PAGE 7
• PRT: SYSPRINT or SYSTSPRT • LOG: ISPF log • ISPF: ISPF panel • XML: HP XP P9000 Command View Advanced Edition Software log and window 1 1 If MSGID ON is specified using the ISPF system command, the message ID and message text are displayed in the ISPF panel. However, if MSGID OFF is specified, only the message text is displayed at the beginning without the message ID.
PAGE 8
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions RC=0 Count: count YKBTSCAN. count Number of scanned devices YK7032I PRT HP storage systems The number of HP storage-system devices scanned RC=0 Devices Found: count by executing YKBTSCAN.
PAGE 9
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions • 40: The prefix specified in the YKMONCG file is being used by the Business Continuity Manager agent. • 44: An attempt to initialize the subtask failed. YK8009E CON Task(task-ID) abended: completion-code. The task terminated abnormally during startup of BCM Monitor. BCM Monitor will stop.
PAGE 10
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions command-name Name of the waiting command The full name of the command is displayed, even if the abbreviated name of the command was entered. parameter Parameter specified in the waiting command The full name of the parameter is displayed, even if the abbreviated name of the parameter was specified.
PAGE 11
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions IRXINIT returns the abnormal termination code in the two trailing bytes of R0 and returns the reason code for abnormal termination in the two leading bytes of R0. If the reason code for abnormal termination is larger than two bytes, IRXINIT returns only the two trailing bytes for the reason code for abnormal termination.
PAGE 12
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions contents-of-register-6 contents-of-register-7 This is displayed in one of the following formats: 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 • y'y'.m'm'.
PAGE 13
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions This is only displayed when the output destination is SYSTSPRT. label Label at which BCM Monitor goes to sleep sleep-time Sleep duration YK8043I PRT CON time STOPPOINT 'label' reached. BCM Monitor has reached the point label. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 14
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text YK8048I PRT CON time Set CYCLETIME to : cycletime. Explanation and recommended actions BCM Monitor set CYCLETIME to the value identified by cycletime. time Message output time This is only displayed when the output destination is SYSTSPRT. YK8049I PRT CON time Set WAITTIMEOUT to : BCM Monitor set WAITTIMEOUT to the value identified by timeout. timeout.
PAGE 15
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions time Message output time This is only displayed when the output destination is SYSTSPRT. dd-name DD name of the file where the error occurred YK8071E PRT time File Close error : dd-name. The file dd-name could not be closed. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 16
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions Message output time This is only displayed when the output destination is SYSTSPRT. file Name of the file where the error occurred rec# Line number in the file where the error was detected YK8077E PRT time Invalid value was specified for param parameter : file : rec#. The parameter value param is invalid.
PAGE 17
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions cgid CGID parameter value that is specified more than once YK8081E PRT time Combination of STATUS The combination of STATUS and ACTION specified in the and ACTION is invalid : YKMONCG file is invalid. rec#. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 18
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions DD name of the file where the error occurred YK8100I PRT CON time sendmsg The message identified by sendmsg appears. The message is specified in SENDMSG with the CONS level designated. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 19
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions YK8223W PRT CON time cmd (RC=4) : Some volumes with invalid status found. Invalid volumes were detected in the copy group during the execution of the CLI command cmd. Processing of these volumes was skipped. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 20
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions This is only displayed when the output destination is SYSTSPRT. YK8304I PRT CON time Copy Group is in 'status' status. Wait until status has changed. BCM Monitor will wait until the copy group status identified by status changes to another status.
PAGE 21
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions Percentage of copy pairs whose copy direction is secondary-to-primary attime ATTIME suspend time attms ATTIME suspend status YK8312I See “YK8312I PRT” (page 166). N/A YK8313I CON REPORT DETAIL: This message indicates the results of REPORT(DETAIL).
PAGE 22
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions Consistency time for each consistency group YK8314I See “YK8314I PRT” (page 167). N/A YK8315I CON REPORT RPO: This message indicates the results of REPORT(RPO).
PAGE 23
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions p-rsf-all Primary reserve sidefile cache-usage rate p-rsf-ct Primary reserve sidefile consistency cache-usage rate p-wpr-all Primary write pending rate s-rsf-all Secondary reserve sidefile cache-usage rate s-rsf-ct Secondary reserve sidefile consistency cache-usage rate s-wpr-all Secondary write pending rate mcu-to-rcu-kbps
PAGE 24
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions Serial number of primary storage system ssn Serial number of secondary storage system mcu-to-rcu-kbps Data transfer rate (Kbps) between the main control unit and the remote control unit p-jnl-meta Metadata % used in master journal volume p-jnl-data Data % used in master journal volume s-jnl-meta Metadata % used in restore jo
PAGE 25
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text YK8324I PRT CON time All volumes are in 'HOLDER' status. Explanation and recommended actions All volumes are in the HOLDER status. time Message output time This is only displayed when the output destination is SYSTSPRT. YK8325I PRT CON time Copy Group 'cgid' is 'status' now. The copy group identified by cgid entered the status identified by status.
PAGE 26
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text YK8404I PRT CON time Execute action 'action err-action' Explanation and recommended actions BCM Monitor will execute the action identified by action err-action specified in the ACTION parameter for STATUS. time Message output time This is only displayed when the output destination is SYSTSPRT.
PAGE 27
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text ONACTIONERROR : err-action STOP AT STOPPOINT : stoppt SLEEP AT STOPPOINT : sleeppt Explanation and recommended actions 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 See “YK8413I PRT” (page 169).
PAGE 28
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions These parameters appear a specified number of times. YK9001I ISPF The license key has been installed The license key was installed. YK9051E ISPF An error occurred in the license information dataset An error occurred with the license information dataset.
PAGE 29
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK80x) (continued) Message ID Message text Explanation and recommended actions A permanent license for Business Continuity Manager Basic is required. If function is Cnt Ac-S Z Sync Extended CTG: A permanent license for Business Continuity Manager Extended CT Group is required.
PAGE 30
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x) (continued) Message ID Message text Explanation and recommended actions the message specified in the MSGID parameter of the YKCONMSG command has not yet arrived. Re-execute the YKCONMSG command with OP(GET) specified after the system becomes ready to receive messages.
PAGE 31
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x) (continued) Message ID Message text Explanation and recommended actions parameter-name Check the following, and then re-execute the command: • Make sure that the required parameter indicated by parameter-name was specified. • Make sure that the value specified for the required parameter indicated by parameter-name is valid.
PAGE 32
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x) (continued) Message ID Message text Explanation and recommended actions The device number of the volume whose information acquisition was skipped YKB202W TSO Unable to resolve primary volume information. Pair=CopyType, DEVN=Devn, SN=SerialNum, CU=CU#, CCA= CCA# A P-VOL not defined in the disk configuration definition file was detected among the PPRC copy pairs detected by the YKP2B command.
PAGE 33
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x) (continued) Message ID Message text Explanation and recommended actions YKC000T TSO RC=48 Supplied parameters invalid Invalid parameters are specified. YKC001E MSG SC=48 RC=48 No controller ARRAYS() supplied YKC001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter.
PAGE 34
Table 3 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKC0x) (continued) Message ID Message text Explanation and recommended actions YKC008E MSG SC=48 RC=48 Starting FROM() not valid hex The value specified in the FROM parameter is not in hexadecimal format. YKC009E MSG SC=48 RC=48 Specify DEV# and VOLSER parm exclusively You cannot specify a device number and a volume serial number at the same time.
PAGE 35
Table 4 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKD0x) Message ID Message text Explanation and recommended actions YKD000T TSO RC=48 Supplied parameters invalid Invalid parameters are specified. YKD001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter. YKD001E MSG SC=48 RC=48 No results STEM() supplied YKD002E MSG SC=48 RC=48 Copy Group STEM(stem) The last character of the STEM parameter is not a period.
PAGE 36
Table 5 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKE0x) Message ID Message text Explanation and recommended actions YKE000T TSO RC=48 Supplied parameters invalid Invalid parameters are specified. YKE001E MSG SC=48 RC=48 GOTO() not supplied YKE001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter. YKE001E MSG SC=48 RC=48 No results STEM() supplied Nothing is assigned to the STEM parameter.
PAGE 37
Table 5 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKE0x) (continued) Message ID Message text Explanation and recommended actions Version 2.0 or later: Copy group number and copy pair number For details about identifying a volume with the copy group number and the copy pair number, see “Identifying the volume to be processed” (page 170).
PAGE 38
Table 6 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKF0x) (continued) Message ID Message text Explanation and recommended actions YKF010E TSO RC=40 REXX failure return code=nnnn starting with variable name Access to the REXX variable identified by name failed. For details about the return code, see IKJCT441 in the TSO/E Programming Services.
PAGE 39
Table 7 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG0x) (continued) Message ID Message text Explanation and recommended actions YKG005E 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 YKG006E MSG SC=48 RC=48 Unable to execute without valid PREFIX() parameter. Nothing or an invalid value is assigned to the PREFIX parameter.
PAGE 40
Table 7 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG0x) (continued) Message ID Message text Explanation and recommended actions Number of the line in the file identified by file where the error was detected YKG054E MSG SC=36 RC=36 (file:rec#) Unexpected termination of element: name The XML element name that exists on the line with the line number identified by rec# in the file identified by file has not been correctly created.
PAGE 41
Table 7 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG0x) (continued) Message ID Message text Explanation and recommended actions XML attribute name value XML attribute value file Name of the XML file where the error was detected rec# Number of the line in the file identified by file where the error was detected YKG077W MSG SC=4 RC=4 (file:rec#) APIInfo Level=level invalid. Supported level isv.r.m.
PAGE 42
Table 7 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG0x) (continued) Message ID Message text Explanation and recommended actions YKG089E MSG SC=40 RC=40 (file) File Close error: dsstate. An attempt to close the XML file identified by file failed. dsstate Status of the input XML file file Name of the XML file where the error was detected YKG090E MSG SC=40 RC=40 (file) File Allocation Failed: dsstate.
PAGE 43
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKG203E MSG SC=48 RC=48 "SYSAUTH." cannot be specified in STEM() parameter. SYSAUTH. cannot be specified for the STEM parameter. Specify a different name. YKG204E TSO RC=48 name parameter is too long. The parameter identified by name is too long. YKG205E MSG SC=48 RC=48 name parameter is too long.
PAGE 44
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKG253E MSG SC=36 RC=36 (file:rec#) This kind of elements element can't be defined more than once. The XML element element cannot be defined more than once. Correct the specification on the line with the line number identified by rec# in the file identified by file.
PAGE 45
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions Number of the line in the file identified by file where the error was detected YKG274E MSG SC=36 RC=36 (file:rec#) ETag name is mismatch. /correct-ETag-name is expected, but /incorrect-ETag-name is specified. The specified ETag name /incorrect-ETag-name is not the expected ETag name /correct-ETag-name.
PAGE 46
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions Correct the specification on the line with the line number identified by rec# in the file identified by file.
PAGE 47
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKH001I TSO YKH2B completed. The YKH2B command terminated. RC=return-code return-code The return code of the YKH2B command 0: The command ended successfully. One or more copy group definition files were created. 4: Indicates that one of the following occurred: • The command ended successfully.
PAGE 48
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKH101E TSO The specified PREFIX is being used by another program. The specified prefix is being used by another program. Error occurred during execution. Cmd=info An error occurred during execution of the YKH2B command.
PAGE 49
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions The storage system of the detected undefined volume CU# The control unit number of the detected undefined volume CCA# The command control address number of the detected undefined volume YKH203W TSO Unable to resolve secondary volume information.
PAGE 50
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions name Parameter name YKJ002E TSO RC=48 The specified PREFIX is being used by another program. The specified prefix is being used by another program. YKJ051E TSO RC=32 Error occurred during execution. Cmd= info An error occurred during execution of the YKIMPORT command or YKEXPORT command.
PAGE 51
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKJ102E TSO RC=32 name is not specified in Copy Group definition specified by BASEGROUP. The copy group definition file specified by the BASEGROUP parameter does not include the element identified by name. Set the necessary elements in the copy group definition file that is to be used as the base, and then retry.
PAGE 52
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions 10) number) indicates a reason code (maintenance information). YKJ200E TSO RC=32 name is not specified in Pair The item identified by name is not included in the pair information information CSV file: CSV file.
PAGE 53
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKJ205E TSO RC=32 Secondary volume is not No S-VOL is specified in the pair information CSV file.
PAGE 54
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions copy-type Copy Group: dd-name: rec# Hitachi TrueCopy™ for Mainframe, Hitachi TrueCopy™ Asynchronous for Mainframe, HP Storage Business Copy for Mainframe, or HP Storage Continuous Access Synchronous for Mainframe.
PAGE 55
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions DD name of the CSV file where the error was detected rec# Number of the line in the file identified by dd-name where the error was detected YKJ214W TSO RC=8 A copy pair capacity check could not be performed because the capacity of a volume could not be acquired.
PAGE 56
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions name Name of the item in the EXCTG information CSV file dd-name DD name of the CSV file where the error was detected rec# Number of the line in the file identified by dd-name where the error was detected YKJ252E TSO RC=32 The number of items The number of items specified on one line of the EXCTG information specified for a
PAGE 57
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKJ257E TSO RC=32 Multiple entries that specify the same Copy Group are defined in EXCTG information CSV file: dd-name: rec# The EXCTG information CSV file contains multiple entries (lines) that specify the same copy group.
PAGE 58
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions information CSV file is invalid: dd-name: rec# dd-name DD name of the CSV file where the error was detected rec# Line number in the file dd-name where the error was detected YKJ273E TSO RC=32 This entry does not have any corresponding Copy Group in Pair information CSV file: dd-name: rec# The pair information CSV file i
PAGE 59
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x) (continued) Message ID Message text Explanation and recommended actions YKK102E TSO RC=32 Failed to get user SVC routine information, service=service-name, code=code1, code2 . User SVC routine information could not be acquired.
PAGE 60
Table 9 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL0x) (continued) Message ID Message text Explanation and recommended actions YKL006E MSG SC=48 RC=48 Unable to execute without valid PREFIX parameter. Specify a valid PREFIX parameter. YKL007E MSG SC=48 RC=48 Unable to execute without valid GROUP parameter. Specify a valid GROUP parameter.
PAGE 61
Table 9 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL0x) (continued) Message ID Message text Explanation and recommended actions rec# Number of the line in the file identified by file where the error was detected YKL074E MSG SC=36 RC=36 (file:rec#) Invalid "&" character discovered in quoted string. string An invalid entity reference was found on the line with the line number identified by rec# in the file identified by file.
PAGE 62
Table 9 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL0x) (continued) Message ID Message text Explanation and recommended actions YKL077W MSG SC=4 RC=4 (file:rec#) APIInfo Level=level invalid. Supported level is v.r.m. The system does not recognize the Level attribute level of the APIInfo element that exists on the line with the line number identified by rec# in the file identified by file.
PAGE 63
Table 9 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL0x) (continued) Message ID Message text Explanation and recommended actions current host device address domain is used. The situation represented by this message is not always fatal. Many CLI commands can be successfully executed by using only the P-VOL unit address. pair-index See the pair index description in the explanation of the YKE003E message.
PAGE 64
Table 9 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL0x) (continued) Message ID Message text Explanation and recommended actions file Name of the XML file where the error was detected YKL091E MSG File Deallocation Failed: SC=40 RC=40 (file) dsstate. An attempt to deallocate the XML file identified by file failed. dsstate Status of the input XML file Name of the XML file where the error was detected YKL092E MSG File Read error: dsstate.
PAGE 65
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text Explanation and recommended actions YKL241W MSG SC=4 RC=4 (file:rec#) The attribute attname is already defined. The XML attribute identified by attname has already been defined. Review the file name identified by file and the attname value on the line with the line number identified by rec#.
PAGE 66
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text Explanation and recommended actions rec# Number of the line in the file identified by file where the error was detected YKL254E MSG SC=36 RC=36 (file:rec#) The value value of attribute name is not match with filename. The value value of the XML attribute name does not match the name in the file name.
PAGE 67
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text Explanation and recommended actions Name of the XML file where the error was detected rec# Number of the line in the file identified by file where the error was detected YKL274E MSG SC=36 RC=36 (file:rec#) ETag name is mismatch. /correct-ETag-name is expected, but /incorrect-ETag-name is specified.
PAGE 68
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text YKL280E MSG No command devices were SC=36 RC=36 (file) found. Explanation and recommended actions No command devices were found. Correct the route definition in the route list definition file shown in file.
PAGE 69
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text Explanation and recommended actions YKL290E MSG SC=44 RC=44 (result) YKVGET program failure for: vn An attempt to acquire the variable vn failed with the result value identified by result. This error can be caused by an invalid value being specified for the STEM parameter.
PAGE 70
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x) (continued) Message ID Message text YKL298E MSG TSO CLI-name encountered an SC=44 RC=44 unexpected error. (detailed-info) Explanation and recommended actions An unexpected error has occurred. This error might have occurred with another error. If another error message was output at the same time as this one, follow the instructions in that message to fix the corresponding problem.
PAGE 71
Table 11 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM0x) (continued) Message ID Message text Explanation and recommended actions YKM002E TSO Messages MSG(stem) does not include trailing "." The last character of the MSG parameter is not a period. stem Stem name assigned to the MSG parameter YKM008E MSG SC=48 DEVN() not valid hex The value specified in the DEVN parameter is not in hexadecimal format.
PAGE 72
Table 11 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM0x) (continued) Message ID Message text Explanation and recommended actions YKM021E ISPF Check either Device num or Volser Select either Device Num or Volser. YKM022E ISPF The End Volser value must not The End Volser value is lower than the Start Volser value. be lower than the Start Volser YKM023E ISPF Invalid value The value is invalid. YKM024E ISPF Choose any one Choose one.
PAGE 73
Table 11 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM0x) (continued) Message ID Message text Explanation and recommended actions YKM040E ISPF A Consistency Group ID (C/T For the Cnt Ac-J Z copy group definition, you need to specify a ID,sub C/T ID) is required for C/T group ID and a sub C/T group ID. CAJ Copy Group definition. YKM041E ISPF A sub Consistency Group ID cannot be specified for BC Z/CA/TCA Copy Group definition.
PAGE 74
Table 11 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM0x) (continued) Message ID Message text Explanation and recommended actions Re-execute the YKMAKE command without specifying the NOCOPY parameter. YKM058E MSG SC=36 RC=48 Some pairs in this group do not support TCA services One or more devices in the HP XP 256 Disk Array storage system do not support TCA copy groups.
PAGE 75
Table 12 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM1x – YKM5x) (continued) Message ID Message text Explanation and recommended actions YKM506E ISPF You cannot define inter-DKC In this interface version, the user cannot define inter-DKC paths. path with this interface version. YKM507E ISPF The number of connections of inter-CU paths exceeds the maximum number of connections that is allowed within the same CU.
PAGE 76
Table 12 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM1x – YKM5x) (continued) Message ID Message text Explanation and recommended actions and secondary side of an inter-DKC path. YKM520E ISPF These device number remdevn The device number or storage system serial number has not yet or storage system S/N remsn been scanned in the device address domain ID. are not discovered on Device remdevn Address Domain remdad.
PAGE 77
Table 13 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM7x) (continued) Message ID Message text Explanation and recommended actions YKM703E ISPF Enter hexadecimal characters (0-9, A-F, a-f). Enter hexadecimal characters (0-9, A-F, a-f). YKM704E ISPF Enter alphanumeric characters Enter alphanumeric characters (0-9, A-Z, a-z). (0-9, A-Z, a-z). YKM705E ISPF Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z), the first alphabetic.
PAGE 78
Table 13 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM7x) (continued) 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 (numerical characters: 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.
PAGE 79
Table 13 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM7x) (continued) Message ID Message text Explanation and recommended actions YKM757E ISPF The 4-digit year (YYYY) or 2-digit month (MM) or 2-digit day (DD) was not numeric. Valid year values are 1970–2042, valid month values are 01-12, and valid day values are 01-31. The value for the year (YYYY), month (MM), or day (DD) was not numeric.
PAGE 80
Table 13 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM7x) (continued) Message ID Message text Explanation and recommended actions YKM770E ISPF Enter unique value in a storage Enter a value that is unique within the storage system. system. YKM771I ISPF Panel could not scroll because The panel cannot be scrolled because the start of the data is it shows beginning of data. already being displayed.
PAGE 81
Table 14 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKM9x) (continued) Message ID Message text Explanation and recommended actions If DBCS (Double-Byte Character Set) is enabled for the environment, concatenate the Business Continuity Manager dataset to the alternate panel library (dd name: ISPPALT). For details, see the HP XP P9000 for Business Continuity Manager Software Installation Guide.
PAGE 82
Table 15 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKN0x) (continued) Message ID Message text Explanation and recommended actions YKN050E MSG SC=48 RC=48 (attribute-value) Invalid Copy Group attribute name The specified copy group attribute value is invalid for this command. Correct the value and then re-execute the command.
PAGE 83
Table 16 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKP0x) (continued) Message ID Message text Explanation and recommended actions For details about the return code, see IKJCT441 in the TSO/E Programming Services. nnnn Error code for REXX access YKP065E MSG SC=36 The storage system The storage system identified by serial-number is paired with RC=36 (serial-number) pairs with more more than four storage systems within the C/T group.
PAGE 84
Table 17 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKQ0x) (continued) Message ID Message text Explanation and recommended actions For details about the return code, see IKJCT441 in the TSO/E Programming Services. nnnn Error code for REXX access YKQ018E MSG SC=16 RC=16 (pair-index) BC Z PAIR deficiency.
PAGE 85
Table 17 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKQ0x) (continued) Message ID Message text Explanation and recommended actions 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 BC Z Primary is simplex, Check that the S-VOL status is SIMPLEX. secondary not.
PAGE 86
Table 17 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKQ0x) (continued) Message ID Message text Explanation and recommended actions 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. YKQ099I TSO YKQUERY command return code=nnnn, reason code=rrrr The YKQUERY command terminated with the return code nnnn and the reason code rrrr.
PAGE 87
Table 18 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKR0x) (continued) Message ID Message text Explanation and recommended actions YKR050E MSG SC=36 RC=48 (attribute-value) Invalid Copy Group attribute name The specified copy group attribute value is invalid for this command. Correct the value and then re-execute the command.
PAGE 88
Table 19 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKS0x) (continued) Message ID Message text Explanation and recommended actions YKS005E 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 YKS006E MSG SC=48 RC=48 Unable to execute without valid Specify a valid PREFIX parameter. PREFIX parameter.
PAGE 89
Table 19 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKS0x) (continued) Message ID Message text Explanation and recommended actions configuration file, see the HP XP P9000 for Business Continuity Manager Software Reference Guide. • UNAVAILABLE DATASET The configuration file is being used. Check the usage of the configuration file. XX displays the file attribute value that caused the error and YY displays the correct file attribute value.
PAGE 90
Table 20 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKS2x) (continued) Message ID Message text Explanation and recommended actions the environment, and then create the configuration file again. For details about what action to take, see the message that was output and the HP XP P9000 for Business Continuity Manager Software User’s Guide.
PAGE 91
Table 20 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKS2x) (continued) Message ID Message text Explanation and recommended actions Status of the configuration file • EXTENT=extent The number of extents of the dataset that is currently allocated extent indicates the number of extents that are allocated to the dataset indicated by dataset-name. • DSORG=VSAM The dataset format is VSAM. A dataset whose format is VSAM cannot be used as a configuration file.
PAGE 92
Table 20 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKS2x) (continued) Message ID Message text Explanation and recommended actions If no other error message was output, collect the following materials and contact service representative: • The script from which this command was executed (not necessary if this command was executed from the ISPF panel). • The ISPF log (not necessary if this command was executed from a script).
PAGE 93
Table 21 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKT0x) (continued) Message ID Message text Explanation and recommended actions YKT021E CON RC=20 Invalid parameter A value specified in the PARM parameter is invalid. Check the specification of the PARM parameter. YKT022E CON RC=4 SVC routine is already inserted The user SVC routine is already registered. YKT023E CON RC=16 Couldn't delete SVC routine The user SVC routine deletion failed.
PAGE 94
Table 22 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKT2x) (continued) Message ID Message text Explanation and recommended actions Specify a valid keyword and then re-execute the command. YKT221E CON RC=4 Specified HOST ID is invalid The value assigned to the YKCMDIF parameter is invalid. The program ignores the specification and continues processing.
PAGE 95
Table 23 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKT4x) (continued) Message ID Message text Explanation and recommended actions variable Environment variables for Business Continuity Manager • Host ID: The host ID • License info DSN prefix: Prefix of the license information dataset • BCM log output method: Output method of the BCM log • CLI log output settings: Output settings for the CLI command-execution logs value Value set for each of the Busine
PAGE 96
Table 24 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKU0x) (continued) Message ID Message text Explanation and recommended actions codes, see IKJPARS in the TSO/E Programming Services. YKU001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter. YKU001E MSG SC=48 RC=48 No results STEM() supplied Nothing is assigned to the STEM parameter. YKU002E MSG SC=48 RC=48 Copy Group STEM(stem) does not include trailing ".
PAGE 97
Table 24 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKU0x) (continued) Message ID Message text Explanation and recommended actions nnnn Error code returned upon REXX access YKU050E MSG SC=36 RC=48 (attribute-value) Invalid Copy Group attribute name The specified copy group attribute value is invalid for this command. Correct the value and then re-execute the command.
PAGE 98
Table 25 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKV0x) (continued) Message ID Message text Explanation and recommended actions For details, see the reason code in the YKV099I message that will appear after this message. For reason codes, see IKJPARS in the TSO/E Programming Services. YKV001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter.
PAGE 99
Table 26 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKW0x) Message ID Message text Explanation and recommended actions YKW001W TSO Timeout limit has expired without The specified copy group copy-group did not reach the group copy-group reaching state requested status state within the specified time limit. state. YKW002E TSO Primary Devices OFFLINE. Unable Because the specified copy group contains a copy pair to receive IEA494I messages.
PAGE 100
Table 26 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKW0x) (continued) Message ID Message text Explanation and recommended actions YKW009W TSO Terminated due to Operator attention. An interrupt occurred during execution of the YKWATCH command. The TSO/E command issued within the YKWATCH command cannot be completed. Re-execute the command. YKW010E TSO Processing error encountered.
PAGE 101
Table 27 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKX0x) (continued) Message ID Message text Explanation and recommended actions (APID=apid) If multiple command devices are defined for the storage system, processing continues. Operate according to the I/O error messages issued simultaneously. serial-number Serial number of the corresponding storage system.
PAGE 102
Table 28 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKX1x) (continued) Message ID Message text Explanation and recommended actions YKX103E MSG SC=48 Parameter combination is invalid The specified parameter combination is invalid. For details about the combination of parameters, see the description of the YKBLDCMD command or the YKDELCMD command in the HP XP P9000 for Business Continuity Manager Software Reference Guide.
PAGE 103
Table 29 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKX2x) (continued) Message ID Message text Explanation and recommended actions YKX201E MSG SC=48 No serial# SN() supplied Nothing is assigned to the SN parameter. YKX201E MSG SC=48 No serial# SSN() supplied Nothing is assigned to the SSN parameter. YKX202E TSO RC=48 Messages MSG(stem) does not include trailing "." The last character of the MSG parameter is not a period.
PAGE 104
Table 30 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY0x) (continued) Message ID Message text Explanation and recommended actions Version number rr Revision number zz Exception YKY002I CON INVALID INITIALIZATION PARAMETER: parameter-name The specified parameter has not been defined in the initialization parameters, or the initialization parameter shown as parameter-name is invalid. The Business Continuity Manager agent has been terminated.
PAGE 105
Table 30 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY0x) (continued) Message ID Message text Explanation and recommended actions 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 not found. The Business Continuity Manager agent will be terminated. Make sure that the indicated load module was installed correctly.
PAGE 106
Table 31 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY1x) Message ID Message text Explanation and recommended actions YKY100I CON MODIFY COMMAND ACCEPTED The MODIFY command was accepted. YKY101I CON STOP COMMAND ACCEPTED The STOP command was accepted. YKY102I CON INVALID error-type: text After an entry of the MODIFY command, an error was detected in the command or operand shown as text. Check, and, if necessary, revise the command.
PAGE 107
Table 31 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY1x) (continued) Message ID Message text Explanation and recommended actions port-number • When LOCAL is displayed in host-type: The port number of the local host • When REMOTE is displayed in host-type: The port number of the remote host IP-address • When LOCAL is displayed in host-type: The IP address of the local host • When REMOTE is displayed in host-type: The IP address of the remote host YKY
PAGE 108
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x) (continued) Message ID Message text Explanation and recommended actions Number used to identify the processing task that output the message YKY301I SYS hh:mm:ss task-ID,TCP CONNECTION ENDED NORMALLY The TCP connection was released successfully.
PAGE 109
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x) (continued) Message ID Message text Explanation and recommended actions Number used to identify the processing task that output the message IP-address IP address of the remote host remote-port-number Port number of the remote host local-port-number Port number of the local host YKY315I CON task-ID,COMMUNICATION ERROR,@API[,request-name [,RC=response-code]] [,EC=event-code] [,SRC= local-IP-add
PAGE 110
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x) (continued) Message ID Message text Explanation and recommended actions IP address of the connection target host connection-target-port-number Port number of the connection target host YKY321I CON task-ID,COMMUNICATION TIMED There is no response within the specified response OUT wait time. The connection will be released. Check the cause of the response timeout.
PAGE 111
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x) (continued) Message ID Message text Explanation and recommended actions If the configuration file failed to be updated, see the other error message that was output with this one and take appropriate action. result Indicates the result • SUCCESS: The update succeeded. • FAILURE: The update failed. YKY501E XML Disk configuration definition error-type error.
PAGE 112
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x) (continued) Message ID Message text Explanation and recommended actions restart the Business Continuity Manager agent, and then refresh the configuration file from Replication Manager. If the error type is something other than RENAME and the temporary file exists, delete the temporary file.
PAGE 113
Table 33 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY6x) (continued) Message ID Message text Explanation and recommended actions cataloged procedure used for starting the Business Continuity Manager agent. Check, and, if necessary, revise JCL, and then re-execute. return-code • 20: Processing failed. The EXEC processing was not performed. • 20021: The parameter list passed to IRXJCL was invalid.
PAGE 114
Table 33 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY6x) (continued) Message ID Message text Explanation and recommended actions For details about the return code, see the TSO/E REXX Reference. abnormal-termination-code-andreason-code-for-abnormal-termination R0 includes the abnormal termination code and the reason code for abnormal termination. IRXTERM returns the abnormal termination code set in the two trailing bytes of R0.
PAGE 115
Table 33 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY6x) (continued) Message ID Message text Explanation and recommended actions ABENDED-MODULE=module-name Contact the center administrator. C-DATE=module-creation-date Sxxx BASE=bbbbbbbb DISP=dddd System completion code when the [CALLING-MODULE=module-name task terminated abnormally C-DATE=y'y'.m'm'.
PAGE 116
Table 33 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY6x) (continued) Message ID Message text Explanation and recommended actions Interrupt code during the abnormal termination Table 34 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY7x) Message ID Message text Explanation and recommended actions YKY703E XML XML translation error: The sent entity This is an XML error. The sent entity is not XML.
PAGE 117
Table 34 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY7x) (continued) Message ID Message text Explanation and recommended actions in the XML request element 'parent-element-name'. element name cannot be acquired, parent-element-name is set to null. Check, and, if necessary, revise the specified request. parent-element-name Parent element name child-element-name Child element name YKY717E XML A required element is missing from the request.
PAGE 118
Table 34 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY7x) (continued) Message ID Message text Explanation and recommended actions error-type • ALLOCATE: An allocation error Make sure that the copy group cgname configuration file exists. • EXECIO: An input error Make sure that the configuration file of the copy group cgname has not been broken. • format: An XML format error Make sure that the XML description does not contain an error.
PAGE 119
Table 35 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ0x) Message ID Message text Explanation and recommended actions YKZ000T TSO SC=48 Supplied parameters invalid Invalid parameters were specified. For details, see the reason code in the YKZ099I message displayed after this message. For more information about reason codes, see IKJPARS in the TSO/E Programming Services.
PAGE 120
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) Message ID Message text Explanation and recommended actions YKZ103E MSG SC=48 Parameters combination is invalid The parameter combination is invalid. YKZ201E MSG CON PRT A GETMAIN error occurred. (return The command cannot be executed because a SC=44 RC=441 code=nnn, size=mmm, area=area, GETMAIN error occurred.
PAGE 121
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) (continued) Message ID Message text Explanation and recommended actions Reason code (maintenance information) xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information YKZ203E TSO RC=401 A REXX read error occurred.
PAGE 122
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) (continued) Message ID Message text Explanation and recommended actions YKZ204E TSO RC=401 A REXX write error occurred. (return The command cannot be executed because a REXX code=nnn, name= name, write error occurred. value=value, cmd=xxx, • If the nnn value is 32: pos=YKZ239E MSG SC=48 Expand the job execution area, and then re-execute RC=48yyy) the command.
PAGE 123
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) (continued) Message ID Message text Explanation and recommended actions YKZ206E TSO RC=0 An I/O error occurred. (detail=message-text, cmd=xxx, pos=yyy) The command cannot be executed because an I/O error occurred.
PAGE 124
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) (continued) Message ID Message text Explanation and recommended actions eeeee, nnn: Maintenance information • If this message is displayed as maintenance information (2): ENTRYID ( eeeee ) for TYPE ( ttt ), LEVEL ( lll ) is invalid eeeee, ttt, lll: Maintenance information xxx (decimal number) Command code of the command that was executing when the error occurred See the command code d
PAGE 125
Table 36 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ10x – YKZ20x) (continued) Message ID Message text Explanation and recommended actions ttt (string) GMT time format xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
PAGE 126
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information 1 If this message is output when the log and trace are obtained, the RC is 0.
PAGE 127
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions yyy (string) Maintenance information YKZ216E TSO RC=0 The Trace table is not initialized. (cmd=xxx, pos=yyy) The trace table is not initialized. xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
PAGE 128
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information YKZ220T MSG SC=36 RC=361 Copy type value null or invalid. The copy type is NULL or invalid.
PAGE 129
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions YKZ222E MSG SC=36 RC=361 (pair-index) volume DEVN device-number invalid The device number of the volume is invalid. If the volume is not connected to the host in use, check the values of the DAD and ROUTE parameters specified in the YKLOAD command and the contents of the route list definition file.
PAGE 130
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions 1 If this message is output while the YKLOAD command is being executed, the RC is 44. YKZ227E MSG SC=36 RC=361 stemTCA_FLOWCONTROL=N not supported by some group pairs. Some copy pairs in this group do not support TCA_FLOWCONTROL=N. Correct the configuration file, and then re-execute the YKLOAD command.
PAGE 131
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions 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.
PAGE 132
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions Device address domain ID 1 If this message is output while the YKLOAD command is being executed, the RC is 44. YKZ236E MSG SC=36 RC=361 dad-id Interface number is null. No interface number is registered. Correct the content of the configuration file.
PAGE 133
Table 37 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ21x – YKZ24x) (continued) Message ID Message text Explanation and recommended actions YKZ243E MSG SC=48 RC=48 Supplied parameters invalid ATTIME or CANCEL is specified together with SVOL. YKZ244E MSG SC=36 RC=36 Storage system serial-number is not found in Routelist. Correct the YKSUSPND command parameter values, and then re-execute the command.
PAGE 134
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) Message ID Message text Explanation and recommended actions YKZ250E MSG SC=40 RC=44 A NAME/TOKEN delete error occurred. (return code=nnn, name= name, cmd=xxx, pos=yyy) The command cannot be executed because a NAME/TOKEN delete error occurred.
PAGE 135
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions yyy (string) Maintenance information pair-index See the pair index description in the explanation of the YKE003E message. YKZ252E MSG SC=8 RC=8 DASD device device-number-1(device-number-2) management error, message-text.
PAGE 136
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions When CC=0 and CSW=0000000006xxxx where x indicates a value: MIH might have occurred or a logical path might not be connected. device-number-1 (string) The device that issued I/O device-number-2 (string) The device to be manipulated If the device number of the device to be operated is not found, **** is displayed.
PAGE 137
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions When CC=0 and CSW=00000000060000: MIH might have occurred or a logical path might not be connected. device-number-1 (string) The device that issued I/O device-number-2 (string) The device to be manipulated code1 (decimal number) CC information code2 (Hexadecimal number) CSW Information.
PAGE 138
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions yyy (string) Maintenance information pair-index See the pair index description in the explanation of the YKE003E message. YKZ256E MSG SC=8 RC=8 DASD device device-number-1(device-number-2) sense: diagnostic-information (cmd=xxx, pos=yyy) Detailed information on the I/O error is displayed.
PAGE 139
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions code4 (Hexadecimal number) Subcommand code xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
PAGE 140
Table 38 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ25x) (continued) Message ID Message text Explanation and recommended actions Maintenance information YKZ259E MSG SC=48 RC=481 This product is already executing. The command cannot be executed because Business Continuity Manager is running for another panel or script. 1 If this message is output while the YKLOAD command is being executed, the RC is 44.
PAGE 141
Table 39 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ26x) (continued) Message ID Message text Explanation and recommended actions text Message acquired by the SYNADAF macro xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information YKZ264E MSG CON SC=0 RC=0 A YKLOGnn close error occurred.
PAGE 142
Table 39 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ26x) (continued) Message ID Message text Explanation and recommended actions Return code from the DEVTYPE macro mmm (decimal number) Reason code from the DEVTYPE macro xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
PAGE 143
Table 40 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ27x) (continued) Message ID Message text Explanation and recommended actions Delete one of these definitions or make sure that the duplicated logical path definitions are correct, and then re-execute the command.
PAGE 144
Table 40 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ27x) (continued) Message ID Message text Explanation and recommended actions YKZ273E MSG SC=36 RC=36 No path to be operated exist within the range specified by the supplied parameter. No paths to be operated exist within the range specified by the parameter. Duplicate ports exist in FORWARD. In the logical path definition for FORWARD index1, the index2 and index3 port numbers are duplicated.
PAGE 145
Table 40 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ27x) (continued) Message ID Message text Explanation and recommended actions IFType are X'11' or higher). Also, if scanning was not performed after the storage system microcode was replaced, perform another scan. YKZ277W MSG SC=4 RC=4 Some paths are in the NOPATH state. There is a logical path without a physical path established. YKZ278W MSG SC=8 RC=8 Some paths are in the MISMATCH state.
PAGE 146
Table 41 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ28x) (continued) Message ID Message text Explanation and recommended actions models (or later) where the first two digits of the IFType are X'04' or higher. YKZ282E MSG SC=36 RC=361 Primary device IFType does not support CAJ. Cnt Ac-J Z cannot be used on a storage system that has a P-VOL or uses the remote DKC control function. Use a device2 that supports Cnt Ac-J Z.
PAGE 147
Table 41 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ28x) (continued) Message ID Message text Explanation and recommended actions To execute one of these commands against a logical path, correct the configuration file and then execute the YKLOAD command. index Index number of the logical path without a port element YKZ286E MSG SC=36 RC=36 (index) YKQRYPTH command cannot be executed if the volume on the CU type path has not been scanned.
PAGE 148
Table 42 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ29x) (continued) Message ID Message text Explanation and recommended actions 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 was executing when the log dataset became full See the description for the command code in the YKZ201E message.
PAGE 149
Table 42 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ29x) (continued) Message ID Message text Explanation and recommended actions YKZ295E MSG SC=36 RC=36 The version of this configuration file is not supported. The version of this configuration file is not supported. YKZ296E MSG SC=44 RC=44 A JNLG is not registered in EXCTG. (JNLG=jj, MIRROR=m, EXCTG=e, SN=ssssssssssss) The journal group is not registered in EXCTG for the storage system.
PAGE 150
Table 42 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ29x) (continued) Message ID Message text Explanation and recommended actions JNLG (string) The journal type not being registered (the journal type of the definition, rather than of the storage system) R-JNL: Journal of the secondary site M-JNL: Journal of the primary site jj (hexadecimal number) The journal group number (00-FF) specified by the C/T group ID or sub C/T group ID m (decimal number) Mi
PAGE 151
Table 42 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ29x) (continued) Message ID Message text Explanation and recommended actions cccc (hexadecimal number) Arbitration command device number (0000-3FFF) FFFF is displayed for the supervisor DKC. nnnn (hexadecimal number) Error code For details about the error codes, see “Storage system sense byte information” (page 171).
PAGE 152
Table 42 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ29x) (continued) Message ID Message text Explanation and recommended actions The journal group number registered to the storage system (00-FF) m (decimal number) The mirror ID registered to the storage system (0-3) e (decimal number) The EXCTG ID registered to the storage system (0-3) ssssssssssss (decimal number) The serial number registered to the storage system cccc (hexadecimal number) The arbi
PAGE 153
Table 43 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ3x) (continued) Message ID Message text Explanation and recommended actions Time the CLI command was issued (local time) command Issued CLI command name and its parameters A maximum of 109 characters can be output. If 109 is exceeded, the remainder are discarded. YKZ311I SYS hh:mm:ss command RC=rc This log data indicates the result of a CLI command execution.
PAGE 154
Table 43 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ3x) (continued) Message ID Message text Explanation and recommended actions For details, see the TSO/E REXX User's Guide or the TSO/E Programming Services. YKZ331E TSO RC=64 command terminated with an invalid The CLI command terminated with an invalid return return code. (r). code. command Issued CLI command name. r Return code that the CLI command created.
PAGE 155
Table 43 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ3x) (continued) Message ID Message text Explanation and recommended actions YKZ352E TSO RC=16 The specified error code is invalid. The specified error code is invalid. A possible cause is as follows: • The specified value is not a four-digit hexadecimal value. YKZ353E TSO RC=64 Load module is not found. The load module cannot be found.
PAGE 156
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions Use a device which supports the parameter indicated by param. Also, if a scan has not been performed after the storage system microcode was replaced, perform another scan. param (string) The parameter name which is not supported YKZ402E MSG SC=44 RC=44 Unexpected transition occurred while adding JNLG to EXCTG.
PAGE 157
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions The journal group number specified by the C/T group ID (00-FF) kk (hexadecimal number) The journal group number specified by the sub C/T group ID (00-FF) 1 If this message is output while the YKLOAD command is being executed, the RC is 44. YKZ406E MSG SC=36 RC=361 Primary device IFType does not support EXCTG.
PAGE 158
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions 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.
PAGE 159
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions YYYY: Year MM: Month DD: Day HH: Hour MM: Minute SS.NNNNNN: Second YKZ408E MSG SC=24 RC=24 An unexpected CAJ pair status existed during suspension of CAJ ATTIME.
PAGE 160
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions 3: The suspend processing ended abnormally. uu (decimal number) Status of Cnt Ac-J Z (0 or 1) 0: All Cnt Ac-J Z copy pairs were in the DUPLEX status during the suspension. 1: During the suspension, there was a Cnt Ac-J Z copy pair whose status was not DUPLEX.
PAGE 161
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ91x) (continued) Message ID Message text Explanation and recommended actions jj (hexadecimal number) Journal group number specified for the sub C/T group ID for the Cnt Ac-J Z that links with BC Z. 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.
PAGE 162
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions SUPFnc (hexadecimal number) Value for the version of the storage system support function used in the copy group (minimum) 1 The CAJ ATTIME suspend function can be used in a storage system where the version of the storage system support function are X'14' or higher.
PAGE 163
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions • AttimeSplitMode=QUICK: Quick suspend mode for the CAJ ATTIME suspend function • UR_PathID: Path group specification for Cnt Ac-J Z 1 If this message is output while the YKLOAD command is being executed, the RC is 44.
PAGE 164
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions storage system in the disk configuration definition file. For this reason, a NG scan cannot be executed. Check the device address domain ID specified in the disk configuration definition file or the Set Defaults panel.
PAGE 165
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions YKZ420E MSG SC=48 RC=48 EXCTG information could not be acquired because no EXCTG ID is specified for copying in the forward direction. EXCTG information could not be acquired because no EXCTG ID for copying in the forward direction is specified.
PAGE 166
REVERSED% DUPLEX ATTIME SUSPEND -STATUS OTHER : : : : : : The results of REPORT(SUMMARY)are displayed.
PAGE 167
: Restore journal group ID : Consistency delta value for each consistency group : Consistency time for each consistency group YK8314I PRT REPORT COPY C/T ID RPO: GROUP : SUB PRI- SECC/T SN SN C/T C/T DELTA TIME The results of REPORT(RPO)are displayed.
PAGE 168
: Remote control unit ready timer : Copy pending timer YK8318I PRT REPORT STATS: COPY GROUP : PREFIX : DAD-ID : TYPE : MJNL RJNL C/T SUB PRI- SECID C/T SN SN PRI %S SEC %S - PRI GB - - SEC GB TRANS JNL-VOL JNL-VOL -- JNL-VOL -- JNL-VOL KBYTES/S MET DAT MET DAT DAT DAT The results of REPORT(STATS) for the CAJ copy group are displayed.
PAGE 169
YK8413I PRT COPY GROUP DEFINITIONS: ID : PREFIX : DAD-ID : ROUTE LIST : [,] MONITOR STATUS : STARTUP STATUS : ,, [ WHEN STATUS DO ACTION '' ] The values specified in the YKMONCG file are displayed. This message appears a number of times, equal to the number of copy groups specified.
PAGE 170
Table 46 User completion codes (continued) Completion code Explanation The user who attempted to execute the command has not been granted view permissions for the STGADMIN.YKA.BCM.COMMANDS profile or the STGADMIN.YKA.BCM.YKQUERY profile. Therefore, the user cannot execute CLI commands to view the operations or status of copy pairs, paths, or command devices.
PAGE 171
2 Storage system sense byte information This chapter describes storage system sense byte information (error codes) contained in messages that are output by Business Continuity Manager. Details of error codes This section lists the details on the storage system sense byte information (error codes) that are output to messages. If an error code not listed in this table is output, contact service representative.
PAGE 172
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details 2060 A BC copy pair cannot be made or resynchronized. The reason might be one of the following: Type of error BC CA Output Not output • The BC copy pair status cannot be changed because the P-VOL has already been made into a copy pair by using CAJ. 2061 A BC copy pair cannot be made.
PAGE 173
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details 2093 A BC copy pair cannot be suspended if the following two conditions exist: Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output • The P-VOL of the specified BC copy pair is the S-VOL of a CAA. • A CAA copy pair is not in the Suspend status.
PAGE 174
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details Type of error BC CA created for one of the following reasons: • No mainframe Fibre Channel adapter is installed. • All of the mainframe Fibre Channel adapters are blocked. 20CA If the emulation type of the S-VOL Output Not output of the specified BC copy pair is 3390-A, a copy pair could not be created for one of the following reasons: • No mainframe Fibre Channel adapter is installed.
PAGE 175
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details Type of error 22F6 A BC copy pair cannot be made because the specified P-VOL is an S-VOL for Compatible FlashCopy. Output Not output 22F7 A BC copy pair cannot be made because the specified S-VOL is either a P-VOL or S-VOL for Compatible FlashCopy.
PAGE 176
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA DUPLEX status is included in the C/T group. • The ATTIME suspend time cannot be set because the specified C/T group contains a copy pair that was created by using RAID Manager to specify the BC C/T group ID. 2311 The copy pair cannot be dissolved Output Not output because the copy pair is in the SIMPLEX status. 2312 The command could not be executed because the S-VOL of a BC copy pair is online.
PAGE 177
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others the copy pair is in the SIMPLEX status. 2334 A BC copy pair cannot be made Output Not output because the emulation type of the specified volume is not supported. 2335 A BC copy pair cannot be made Output Not output because the RAID level or emulation type of the volume is not supported.
PAGE 178
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA specified to be the S-VOL is already the P-VOL of a BC copy pair or the one for FlashCopy. 2351 A BC copy pair status cannot be Output Not output changed because the same volume was specified for the P-VOL and the S-VOL. 2352 A BC copy pair cannot be Output Not output resynchronized with Reverse or Quick specified because the P-VOL and S-VOL are online.
PAGE 179
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others specified to be the P-VOL is a command device. 237B A BC copy pair cannot be resynchronized (QuickRestore) because all of the following conditions exist: Output Not output • The specified P-VOL is an internal volume. • The specified S-VOL is an external volume. • The specified P-VOL has a shared configuration with the P-VOL of the CA.
PAGE 180
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error 239B A BC copy pair cannot be Output Not output resynchronized (including Reverse) because the specified P-VOL is the S-VOL of a CA copy pair. 239C A BC copy pair cannot be Output Not output resynchronized (including Reverse) because the specified S-VOL is the P-VOL of a CA copy pair. 239D The command cannot be executed Output Not output because the specified P-VOL is protected by the LDEV guard.
PAGE 181
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error 23F3 The command could not be Output Not output executed because the specified ATTIME suspend time is in the past. 23F4 The command used to request that Output Not output the ATTIME suspend time information be acquired could not be executed due to the following reasons: BC CA CAA CAJ CMD PATH THPz Others • The command was issued to the P-VOL. • The status of the copy pair is SIMPLEX.
PAGE 182
Table 49 Details of error codes 36xx (continued) Error code Error details 3621 Type of error BC CA CAA CAJ CMD PATH Registration to EXCTG has failed Not output because the number of journal groups exceeded the maximum number that can be assigned to the specified arbitration command device. Retry the operation using another arbitration command device. Output Not output 3640 Registration to EXCTG has failed due to a temporary path failure. Retry the operation.
PAGE 183
Table 49 Details of error codes 36xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others group to be registered is different from the attribute of the EXCTG. 368A Registration to EXCTG has failed because the timer type of the journal group to be registered is not System. Not output Output Not output 3694 Registration to EXCTG has failed because the combination of the serial number and device on the specified arbitration command device is incorrect.
PAGE 184
Table 50 Details of error codes 37xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH specified for the delta resync pair in the specified R-JNL group. 370B A CAJ copy pair cannot be Not output resynchronized (with the DELTAJNL parameter) because the specified P-VOL is not in the HOLD status or HOLDTRNS status.
PAGE 185
Table 50 Details of error codes 37xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others (CAJxCAJ) configuration because a CAJ copy pair with a different mirror ID than the specified CAJ copy pair is in a transitional state (Suspending or Deleting). 3738 A CAJ copy pair cannot be made because the Disaster Recovery Extended program product has not been installed in the MCU.
PAGE 186
Table 50 Details of error codes 37xx (continued) Error code Error details 3753 3755 Type of error BC CA CAA CAJ CMD PATH A CAJ copy pair cannot be Not output created with the HOLD parameter in a 3DC (CAJxCAJ) configuration because the delta resync function is not supported. Output Not output A CAJ copy pair cannot be Not output resynchronized.
PAGE 187
Table 51 Details of error codes 46xx (continued) Error code Error details 4602 A CAJ copy pair cannot be resynchronized. Possible reasons include one or both of the following: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output Not output Output Not output THPz Others • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system. • The SSID for the S-VOL in the parameter does not match the SSID of the local storage system.
PAGE 188
Table 51 Details of error codes 46xx (continued) Error code Error details 4613 Type of error BC CAJ CMD A CAJ copy pair cannot be made Not output because the specified M-JNL group is not registered. Output Not output 4614 A CAJ copy pair cannot be made Not output because no logical path has been made between the specified primary storage system and secondary storage system.
PAGE 189
Table 51 Details of error codes 46xx (continued) Error code Error details Type of error 4621 The command could not be Not output executed because the remote DKC Control Function is not supported. Output 4630 The command could not be executed because the 3-site function is not supported. Output 4633 A CAJ copy pair status cannot be Not output changed because an attribute of the P-VOL or S-VOL differs from the actual volume attribute.
PAGE 190
Table 51 Details of error codes 46xx (continued) Error code Error details 4660 The CAJ ATTIME suspend time cannot be set. The reason might be one of the following: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output • The specified parameter is invalid. • The storage system does not support the CAJ ATTIME suspend function in Quick mode. 4661 The CAJ ATTIME suspend time cannot be set because shared memory is not implemented.
PAGE 191
Table 51 Details of error codes 46xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others following procedure to set the CAJ ATTIME suspend time again. Suspend the CAJ copy pair. Change the timer type. Resynchronize the CAJ copy pair. Set the CAJ ATTIME suspend time again. 466B The CAJ ATTIME suspend time Not output cannot be set because the C/T group ID of the specified BC copy pair is incorrect.
PAGE 192
Table 52 Details of error codes 47xx – 49xx Error code Error details 47A3 Type of error BC CA CAA CAJ A CA or CAA copy pair cannot be suspended because SVOL(PERMIT) or Reverse Resync is not supported. Not output Output 47A4 A CAA copy pair cannot be resynchronized with Reverse specified because either the C/T group ID or the C/T group timer type is incorrect.
PAGE 193
Table 53 Details of error codes 4Axx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others CAA cannot be changed because there is a copy pair in this C/T group. 4A30 The C/T group ID defined in the Not output CAA copy group, and the C/T group ID set by the copy pair do not match.
PAGE 194
Table 53 Details of error codes 4Axx (continued) Error code Error details Type of error BC CA CAA CAJ CA or CAA copy pair is being changed. 4A8D The command could not be Not executed because the status of the output CA or CAA copy pair is invalid. Output Not output 4A8E The command could not be Not executed because the status of the output CA or CAA copy pair is being changed.
PAGE 195
Table 54 Details of error codes 4Bxx Error code Error details Type of error 4B02 A copy pair cannot be Not resynchronized because the copy output pair is in a status that cannot be changed. The reason might be one of the following: BC CA CAA CAJ Output Not output Not output CMD PATH THPz Others • The copy pair cannot be resynchronized because the copy group definition contains a C/T group ID, but the actual copy group does not.
PAGE 196
Table 54 Details of error codes 4Bxx (continued) Error code Error details Type of error BC CA CAA CAJ Output Not output because the C/T group IDs do not match. 4B09 A copy pair that is in a CA copy Not group with a C/T group ID output specified cannot be dissolved because the copy pair status does not allow the status to be changed. The reason might be one of the following: • The specified volume is not in a CA copy group with a C/T group ID specified. • The copy pair is in the SIMPLEX status.
PAGE 197
Table 54 Details of error codes 4Bxx (continued) Error code Error details Type of error 4B15 RUN (releasing FREEZE) cannot Not be executed for a CA copy group output with a C/T group ID specified. The reason might be one of the following: BC CA CAA CAJ Output Not output CMD PATH THPz Others • The specified volume is not in a CA copy group with a C/T group ID specified. • The specified volume is using the Open/MF Consistency Preservation Function. • The copy pair is in the SIMPLEX status.
PAGE 198
Table 54 Details of error codes 4Bxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others is not registered in the storage system. 4BB1 No timestamp transfer mode CA Not copy pair can be made because output the specified volume is not a CA copy pair. Output Not output 4BB2 A timestamp transfer mode CA copy pair cannot be made because the specified volume is an XRC pair.
PAGE 199
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others that does not support the FREEZE command is connected. 64FA The command cannot be executed Not output because the host ID is invalid (not within the valid range). Output Not output 64FB The command device cannot be Not output defined. Possible reasons include one or more of the following: Output Not output • The corresponding volume does not exist.
PAGE 200
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details 69E7 The command cannot be executed. The reason might be one of the following: Type of error BC CA CAA CAJ CMD PATH THPz Others Not output Output 69E8 The command cannot be executed Not output because the specified volume is blocked. Output 69E9 The command cannot be executed. The reason might be one of the following: • The command cannot be executed because the specified volume does not exist.
PAGE 201
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details 69F7 A suspension cannot be made. The reason might be one of the following: Type of error BC CA Output CAA CAJ CMD PATH THPz Others Not output • The specified parameter is invalid. • The storage system does not support the Open/MF Consistency Preservation Function. 69F8 A suspension cannot be made because there is an invalid parameter.
PAGE 202
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others command was executed while the command device was not defined. 6A14 The command could not be Not output executed because it was specified to be remotely executed, but this command cannot be executed as a remote command.
PAGE 203
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others executed because of either of the following reasons • The specified serial number and the serial number of the target storage system do not match. • The specified CU number and the CU number of the target device do not match. • The specified volume number and the volume number of the target device do not match. • The target device does not exist.
PAGE 204
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others processing error occurred in the storage system. 6ECB The information of the pool for Not output THPz that was specified by the pool ID could not be acquired due to a logical error.
PAGE 205
Table 56 Details of error codes 7Fxx – 8Cxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH Output Not output THPz Others • The path between the primary site and the secondary site is in the BUSY status. • The emulation type of the P-VOL and the S-VOL do not match. Alternatively, the number of cylinders in the S-VOL is less than the P-VOL. • Either the status of the P-VOL is being changed, or there is a copy pair in the group with the status being changed.
PAGE 206
Table 56 Details of error codes 7Fxx – 8Cxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others remote DKC control function is not set. 8CEB The command could not be Not output executed because the path for the Remote DKC Control Function is not set. Output Not output 8CFB The command could not be Not output executed because in the instruction to transfer to a remote storage system, there is an error in the storage system serial number.
PAGE 207
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others specified by the host command parameter is in the NOT READY status. 8D12 The command could not be Not output executed because the logical volume of the specified volume by the host command parameter is blocked. 8D14 The command could not be Output executed because the BC, CA, or CAA program product is not installed.
PAGE 208
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others specified by the host command parameter is the S-VOL. 8D1B A status cannot be changed Not because the status of the specified output copy pair does not match the actual status. Output Not output 8D1C A CA or CAA copy pair cannot be made or resynchronized.
PAGE 209
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others systems in the host command parameter is incorrect. 8D20 The host command parameter is incorrect. Output Not output 8D21 The command cannot be executed Not output because the volume specified by the host command parameter is in the NOT READY status.
PAGE 210
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA include one or more of the following: • The specified volume is in the SIMPLEX status. • The P-VOL number in the parameter and bootup volume number do not match. • The S-VOL number in the parameter is incorrect. • The serial number or SSID of the primary storage system in the parameter does not match the storage system serial number or SSID of the local CU.
PAGE 211
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8D2C The serial numbers for the primary Not output and the secondary storage systems in the host command parameter is incorrect. 8D30 The host command parameter is incorrect. 8D31 Multiple BC copy pairs cannot be Output Not output suspended because there is a copy pair that does not allow the status transition in the specified copy pairs.
PAGE 212
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others command as a command device. • The corresponding volume is part of a CA or CAA copy pair. 8D46 The command device cannot be Not output deleted. The reason might be one of the following: Output Not output • The corresponding volume is executing a remote control command as a command device. • The corresponding volume is part of a CA or CAA copy pair.
PAGE 213
Table 57 Details of error codes 8Dxx (continued) Error code Error details 8D57 A BC copy pair cannot be dissolved. Possible reasons include one or more of the following: Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output • The status of the copy pair does not allow the status transition. For details, see error code 2310. • The copy pair is in the V-Split status. • The specified C/T group ID is not registered.
PAGE 214
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others transition. For details, see error code 2310. • The copy pair is in the V-Split status. • The specified C/T group ID is not registered. 8D70 The host command parameter is incorrect. Not output 8D71 A CAA C/T group cannot be registered or changed.
PAGE 215
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8DD1 A BC copy pair cannot be made, Output Not output resynchronized, or suspended because the CAJ ATTIME suspend time has been set for the specified BC C/T group. 8DF0 The command could not be executed because the sub-command code is incorrect. Not output Output 8DF1 The host command parameter is incorrect.
PAGE 216
Table 58 Details of error codes 8Fxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH and cannot be used for this combination. 8F14 A CAJ copy pair cannot be made because the specified volume is a Reserve volume. Not output Output Not output 8F17 A CAJ copy pair cannot be made because the specified volume is online.
PAGE 217
Table 58 Details of error codes 8Fxx (continued) Error code Error details 8F25 A CAJ copy pair cannot be made or resynchronized because the specified volume contains PIN data. 8F28 Type of error BC CA CAA CAJ CMD PATH Not output Output Not output A CAJ copy pair cannot be made or resynchronized because the specified P-VOL or S-VOL cannot be accessed. Not output Output Not output 8F29 A CAJ copy pair cannot be made because the P-JNL group cannot be used.
PAGE 218
Table 58 Details of error codes 8Fxx (continued) Error code Error details 8F53 8F58 Type of error BC CA CAA CAJ CMD PATH A CAJ copy pair cannot be Not output made because the configuration does not allow the status transition. (For example, the specified volume has already been made as a BC copy pair and cannot be used for this combination.) Output Not output A CAJ copy pair cannot be made or resynchronized.
PAGE 219
Table 59 Details of error codes C0xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others serial number or SSID of the primary storage system does not match the storage system serial number or SSID of the local CU. C04C The command cannot be executed because the specified serial number or SSID of the secondary storage system does not match the storage system serial number or SSID of the RCU, or the path is not registered.
PAGE 220
Table 59 Details of error codes C0xx (continued) Error code Error details Type of error C065 The serial number or SSID of the Not secondary storage system in the output CA or CAA parameter does not match the storage system serial number or SSID of the local CU. Output Not output C06A The command could not be Not executed because the CA or output CAA volume is in the SIMPLEX status.
PAGE 221
Table 59 Details of error codes C0xx (continued) Error code Error details Type of error C0B6 The command could not be Not executed because the specified output volume is in the SIMPLEX status. Output Not output C0C5 A copy pair cannot be Not suspended because it is already output in the suspend status. Output Not output C0C6 The command could not be executed because it is already in the SIMPLEX status.
PAGE 222
Table 60 Details of error codes C1xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output • A cable is not connected properly. • The specified port is invalid. C128 An attempt to establish or delete Not output all the specified multiple paths has failed. Possible reasons include one or more of the following: • The specified parameter is invalid. • The port or MP status is abnormal. • A cable is not connected properly.
PAGE 223
Table 60 Details of error codes C1xx (continued) Error code Error details C12F The command cannot be executed. The reason might be one of the following: Type of error BC CA CAA CAJ Not output CMD PATH THPz Others Output Not output • The specified CU number is not defined. • An LDEV is not defined for the specified CU number. C162 A copy pair cannot be Not resynchronized because the output corresponding bootup pair is not in the suspend status.
PAGE 224
Table 60 Details of error codes C1xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others set up between CUs (SSIDs) in the copy pair, or the path is in an error status. Table 61 Details of error codes C2xx Error code Error details C211 A copy pair cannot be made because the specified copy pair is already in the DUPLEX status.
PAGE 225
Table 61 Details of error codes C2xx (continued) Error code Error details Type of error C2A0 A copy pair cannot be made Not because the charging limit of output the MCU program product has been exceeded. Output Not output C2A3 A copy pair cannot be made Not because the charging limit of output CA in the MCU has been exceeded. Check the license capacity of this and all related program products.
PAGE 226
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error BC CA CAA CAJ exceeded. Check the license capacity of this and all related program products. C30D The specified volume within the Not RCU, or another volume which output belongs to the same group is in transition to a SIMPLEX or suspend status. Try the operation again in a few minutes. Output Not output C310 The MCU is not NVS ON.
PAGE 227
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C321 The condition setting for the Not number of the Minimum Path output between the MCU and the RCU is invalid. Output Not output C322 The MCU is a storage system Not type that is not supported by CA output or CAA. Output Not output C324 The RCU sequence (number, SSID or CU) is incorrect. Not output Output Not output C325 The RCU is not NVS ON.
PAGE 228
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C338 An intervention request has been Not issued for the S-VOL (S-VOL or output reserve volume of BC). Output Not output C339 The S-VOL is in the FCP status. Not output Output Not output C33A A copy pair cannot be made because the specified S-VOL does not support CA. Not output Output Not output C33B The S-VOL is an S-VOL of another copy pair.
PAGE 229
Table 62 Details of error codes C3xx (continued) Error code Error details C37D Type of error BC CA The RCU is not NVS ON. Not output Output Not output C37E The device level cache of the S-VOL is not valid. Not output Output Not output C37F The S-VOL is not DFW ON. Not output Output Not output C380 The cache for the MCU is blocked on one side (in transition). Not output Output Not output C381 The cache for the MCU is being Not recovered.
PAGE 230
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error BC CA CAA CAJ within which a copy pair can be made. C3A0 The P-VOL device is not supported by CA or CAA. Not output Output Not output C3A4 RCU does not support the S-VOL Not host online check indication output function. Output Not output C3A5 The S-VOL is online. Not output Output Not output C3A6 The specified SSID, or CU number of RCU is incorrect.
PAGE 231
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others Resync status, and the S-VOL for FlashCopy cannot be specified. C3BF The S-VOL of a BC copy pair or Not a Reserve volume cannot be output specified as the S-VOL of a CA or CAA copy pair. Also, a P-VOL in the Reverse Resync status and the S-VOL for FlashCopy cannot be specified.
PAGE 232
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C3CB The CAA program product has not been installed on the RCU. C3CD The S-VOL of a CA or CAA copy Not pair is a BC pair volume. output C3D1 Another C/T group ID is already Not output registered or made in the RCU. C3D2 The storage system type of the RCU is not supported by CA or CAA. Not output Output Not output C3D3 The specified SSID, or CU number of the RCU is incorrect.
PAGE 233
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others (YKBLDCMD) cannot be executed because the specified volume does not exist. Table 63 Details of error codes CBxx Error code Error details Type of error CB10 A copy pair cannot be made because there was an attempt to make a copy pair for both directions with the same C/T group ID.
PAGE 234
Table 63 Details of error codes CBxx (continued) Error code Error details Type of error CB7E A CA or CAA copy pair cannot Not be made because the CLPR that output the specified S-VOL belongs to differs from the one registered in the C/T group. For details on the CLPR, see the storage system documentation.
PAGE 235
Table 63 Details of error codes CBxx (continued) Error code Error details CBEE A CA/CAA copy pair cannot be created for one of the following reasons: Type of error BC CA Not output Output Not output Output CAA CAJ CMD PATH THPz PATH THPz Others Not output • The specified P-VOL is already created as a P-VOL in a delta resync CAJ copy pair. • The specified P-VOL is created as a P-VOL in a copy pair in a 3DC Multi-Target (CAJxCAJ) configuration.
PAGE 236
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details DB08 Type of error BC CA CAA CAJ CMD PATH A CAJ copy pair status cannot Not output be changed because the power-off process is in progress. Output Not output DB09 A CAJ copy pair cannot be made because the specified volume is a CAA copy pair. Not output Output Not output DB0C A CAJ copy pair cannot be resynchronized (with the DELTAJNL parameter or ALLJNL parameter) because the volume is specified.
PAGE 237
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others directions) have not been defined. Make sure that inter-DKC logical paths have already been established in both directions. E876 A CAJ copy pair cannot be Not output made because the storage system serial number specified for the S-VOL is invalid.
PAGE 238
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH M-JNL group has already been made into a copy pair with another R-JNL group. E889 A CAJ copy pair cannot be Not output made because the specified journal group has already been made into a CAJ copy pair by using another mirror ID.
PAGE 239
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others be used in 3DC (CAJxCAJ) configurations. • The specified R-JNL group is already in use. • Another mirror ID is already defined for the specified journal group. E898 A CAJ copy pair cannot be Not output resynchronized because the specified R-JNL group is in use as an R-JNL group for a CAJ copy pair with another mirror ID.
PAGE 240
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details E8A8 Type of error BC CAJ CMD The specified copy pair cannot Not output be suspended because it is not a CAJ copy pair, or the P-VOL and S-VOL for journal group do not match. Output Not output E8A9 A CAJ copy pair cannot be Not output suspended because the storage system is being turned on.
PAGE 241
Table 65 Details of error codes EAxx Error code Error details EA00 The CAJ copy pair cannot be operated for each EXCTG because of the following reasons: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output A CAJ copy pair cannot be Not output made for either of the following reasons: Output Not output THPz Others • The JNLG specified in the copy group is not registered in the EXCTG. • There is a copy pair whose status is TRANS.
PAGE 242
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA15 A CAJ copy pair cannot be Not output resynchronized because the volume specified for the S-VOL is the P-VOL of the CAJ copy pair. Output Not output EA18 A CAJ copy pair cannot be Not output resynchronized because the copy pair is not in the suspend status. Output Not output EA19 A CAJ copy pair cannot be Not output resynchronized because the journal group is not in the Stop status.
PAGE 243
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA2C A CAJ copy pair cannot be dissolved because the R-JNL group is not in the Active or Stop status. Not output Output Not output EA33 A CAJ copy pair cannot be Not output suspended because the M-JNL group is not in the Active status. Output Not output EA36 A CAJ copy pair cannot be suspended because the R-JNL group is not in the Active status.
PAGE 244
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA95 A copy pair cannot be created Not output because the pool of the THPz volume specified for the P-VOL of a CAJ copy pair is being initialized. Output Not output EAA0 The CAJ copy pair cannot be operated for each EXCTG because of the following reasons: Not output Output Not output EAA1 A CAJ copy pair cannot be Not output made because the charging limit of CAA in the MCU has been exceeded.
PAGE 245
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EAB7 A copy pair cannot be made Not output because the shared memory required for making a CAJ copy pair does not exist in the primary storage system. Output Not output EAB8 A copy pair cannot be made because insufficient space is left in the shared memory that manages the differential table of the secondary storage system.
PAGE 246
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH not support 4x4 configuration. EB09 Registration to or deletion from EXCTG has failed because the entered parameter was incorrect. Not output Output Not output EB0A Registration to or deletion from EXCTG has failed because another EXCTG registration or deletion process is in progress.
PAGE 247
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others This error occurs if there is more than one secondary storage system in the same copy group or when the specified journal group number and mirror ID are used for another copy group. EB3B The batch pair status Not output command cannot be executed because the CU number specified by the YKEWAIT command or YKRSCAN command is not supported by this model.
PAGE 248
Table 66 Details of error codes EBxx (continued) Error code Error details EB50 A CAJ copy pair cannot be made because the specified volume does not exist. EB51 Type of error BC CAJ CMD Not output Output Not output A CAJ copy pair cannot be made because the specified S-VOL has PIN data. Not output Output Not output EB52 A CAJ copy pair cannot be made because the specified S-VOL cannot be accessed.
PAGE 249
Table 66 Details of error codes EBxx (continued) Error code Error details EB64 A CAJ copy pair cannot be made because the charging limit of the program product has been exceeded. EB6B Type of error BC CA CAA CAJ CMD PATH Not output Output Not output A CAJ copy pair cannot be Not output created because the specified S-VOL satisfies one of the following conditions: Output Not output THPz Others • The S-VOL is being used for FlashCopy. • The S-VOL is being used for FlashCopy SE.
PAGE 250
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH • The specified S-VOL is being used for the S-VOL of a BC copy pair, and is being resynchronized in the reverse direction or is being shared with the CA copy pair. • The specified S-VOL is a Reserve volume. • The specified S-VOL is a THPz volume and is being used by another program product.
PAGE 251
Table 66 Details of error codes EBxx (continued) Error code Error details EB94 Type of error BC CA CAA CAJ CMD PATH A CAJ copy pair status cannot Not output be changed because the status of the specified copy pair does not allow the status transition. Output Not output EBA0 A CAJ copy pair status cannot Not output be changed because the specified S-VOL is not installed.
PAGE 252
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error EBD3 The path for the remote Not output command transfer route for the second site onwards, or for the command device, might not be set, or a failure occurred in the remote command transfer route. Make sure that the path and the command device are set, available, and have not failed, and then re-execute the operation.
PAGE 253
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others because the journal volume of the specified R-JNL is blocked. EBEB A CAJ copy pair cannot be Not output made or resynchronized because the emulation type of the specified volume is 3390-9A. Output Not output EBF2 Resynchronization in the Not output reverse copy direction cannot be performed for a CAJ copy pair because the CAJ ATTIME suspend time is already set.
PAGE 254
3 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
PAGE 255
• MVS System Commands, GC28-1781 • MVS Programming: Assembler Services Reference, GC28-1910 • Communications Server: IP User's Guide and Commands, GC31-8514 • Program Directory for IBM Library for REXX on zSeries Alternate Library, GI10-3243 • DFSMSdfp Utilities, SC26-7343 • MVS Initialization and Tuning Reference, SC28-1752 • SecureWay Security Server RACF Security Administrator's Guide, SC28-1915 • TSO/E Customization, SC28-1965 • TSO/E Programming Services, SC28-1971 • TSO/E System Pro
PAGE 256
In the Storage section, click Storage Software and then select a product. HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
PAGE 257
Table 67 Document conventions (continued) Convention Element Bold text • Keys that are pressed • Text typed into a GUI element, such as a box • GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Italic text Text emphasis Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE
PAGE 258
4 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
PAGE 259
Glossary A API Application programming interface. B BC Manager A generic name for the following products: • HP XP P9000 for Business Continuity Manager Software • HP XP P9000 for Business Continuity Manager Extended CT Group • HP XP P9000 for Business Continuity Manager 4x4 Extended CT Software C CAA Continuous Access Asynchronous CCA Command control address. CSB Channel status byte. CU Control unit. D DAD Device address domain. DASD Direct access storage device.
PAGE 260
LPAR Logical partition. A virtual server that can share resources. M M-JNL Master journal. Mainframe Agent HP Device Manager Mainframe Agent. MCU Main control unit. MIH Missing interrupt handler. P P-VOL Primary volume. PPRC Peer-to-peer remote copy. PSW Program status word. R R-JNL Restore journal. RACF Resource access control facility. RCU Remote control unit. RECFM Record format. REXX Restructured extended executor. RPO Recovery point objective.
PAGE 261
X XML eXtensible markup language. XRC Extended remote copy. Z z/Linux Linux on IBM System z.