HP XP7 for Business Continuity Manager Messages Abstract This guide describes the messages and error codes that are produced by HP XP7 Business Continuity Manager software. In this manual, these products are collectively referred to as Business Continuity Manager: HP XP7 Business Continuity Manager Basic and HP XP7 Business Continuity Manager Continuous Access Journal 4x4 Extended CTG.
© Copyright 2007, 2014 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.
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.
Contents 1 Messages..................................................................................................5 Message format.......................................................................................................................5 Message output format.........................................................................................................5 Notations used to describe messages.....................................................................................
1 Messages This chapter describes the messages that are issued by Business Continuity Manager (BCM): 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.
• 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
• LOG: ISPF log • ISPF: ISPF panel • XML: HP XP7 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. If the sequence of REXX message variables is specified correctly in the MSG parameter common to all CLI commands, the message will be saved in the sequence.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text YK7032I PRT RC=0 HP storage systems Devices Found: count Explanation and recommended actions The number of HP storage-system devices scanned by executing YKBTSCAN.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions • 32: An error occurred while loading the process module. • 36: No profile is defined in the FACILITY class of RACF. • 40: The prefix specified in the YKMONCG file is being used by the BCM agent. • 44: An attempt to initialize the subtask failed. YK8009E CON Task(task-ID) abended: completion-code.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions YK8020I CON nn: command-name [parameter]. Information is displayed for the command waiting to be executed. nn Number assigned to the waiting command command-name Name of the waiting command The full name of the command is displayed, even if the abbreviated name of the command was entered.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions includes the abnormal termination code and the reason code for abnormal termination. abnormal-termination -ode-and-reason-code -or-abnormal-termination IRXINIT returns the abnormal termination code in the two trailing bytes of R0 and returns the reason code for abnormal termination in the two leading bytes of R0.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions y'y'.m'm'.d'd' and bbbbbbbb are invalid. contents-of-register-2 contents-of-register-3 GR 04-07 module-creation-date contents-of-register-4 contents-of-register-5 This is displayed in one of the following formats: contents-of-register-6 • y'y'.m'm'.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions for max 'sleep-time' minutes. Entering the WAKEUP command resumes copy group monitoring before the duration identified by sleep-time has elapsed. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions status • START: The monitoring status of the copy group was set to ACTIVE. • STOP: The monitoring status of the copy group was set to INACTIVE. YK8048I PRT CON time Set CYCLETIME to : cycletime. BCM Monitor set CYCLETIME to the value identified by cycletime.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text YK8056E PRT CON time Failed to execute operator command. Explanation and recommended actions BCM Monitor failed to execute an operator command. time Message output time This is only displayed when the output destination is SYSTSPRT. YK8070E PRT time File Open error : dd-name. The file dd-name could not be opened.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions Name of the file where the error occurred rec# Line number in the file where the error was detected YK8076E PRT time Invalid parameter was An invalid parameter was specified. specified : file :rec#. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions YK8080E PRT time Duplicate CGID parameters found : cgid. The copy group cgid is specified more than once in the YKMONCG file. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions YK8085E PRT time File record format is invalid : dd-name. The record format of the file indicated by dd-name is invalid. The valid record format is F, FB, V, or VB. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions Timeout value YK8222E PRT CON time YKEWAIT (RC=8) : An unexpected group status was reached during execution of the Unexpected status reached. YKEWAIT command. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions time Message output time This is only displayed when the output destination is SYSTSPRT. YK8303I PRT CON time Waiting for status 'status'. BCM Monitor will wait until the copy group being monitored enters the status identified by status.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions Number of copy pairs in other statuses status Copy group status match Copy progress percentage rev% Percentage of copy pairs whose copy direction is secondary-to-primary attime ATTIME suspend time attms ATTIME suspend status YK8312I See “YK8312I PRT” (page 167).
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions sub-ctid Restore journal group ID ctdelta Consistency delta value for each consistency group cttime 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).
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions Serial number of primary storage system ssn Serial number of secondary storage system sidefile-threshold Sidefile threshold value p-rsf-all Primary reserve sidefile cache-usage rate p-rsf-ct Primary reserve sidefile consistency cache-usage rate p-wpr-all Primary write pending rate s-rsf-all Secondary reserve sidefile
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions p-jnl-data-capacity s-jnl-data-capacity ctid Master journal group ID sub-ctid Restore journal group ID psn 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 % us
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text YK8323I PRT CON time Some volumes are not in a 'HOLDER' status. Explanation and recommended actions Some volumes are not in the HOLDER status. time Message output time This is only displayed when the output destination is SYSTSPRT. YK8324I PRT CON time All volumes are in 'HOLDER' status. All volumes are in the HOLDER status.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text YK8403I PRT CON time Start monitoring Copy Group. Explanation and recommended actions BCM Monitor will start monitoring the copy group. time Message output time This is only displayed when the output destination is SYSTSPRT.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions YK8411I See “YK8411I PRT” (page 169). N/A YK8412I CON SYSTEM OPTIONS: This message indicates the values specified in the YKMONOPT file.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions cgsaopt Option information of the CGSTARTUPSTATUS parameter status action err-action Status, action, and error action for the copy group specified in STATUS and ACTION These parameters appear a specified number of times. YK9001I ISPF The license key has been installed The license key was installed.
Table 1 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YK70x –YK90x) (continued) Message ID Message text Explanation and recommended actions A permanent license for Business Continuity Manager Cnt Ac-J Z 4x4 Extended CTG is required. YK9081W CON Your function license will expire in n days. The license (function) will expire in n days. To continue using this product after the expiry date, you need a permanent license.
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x – YKB20x) (continued) Message ID Message text Explanation and recommended actions YKA010E TSO MSGID() parameter cannot be specified for this operation If GET or CLOSE is specified in the OP parameter, you cannot specify the MSGID parameter.
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x – YKB20x) (continued) Message ID Message text Explanation and recommended actions YKB002I TSO No copy pair was discovered. No copy pair was detected within the specified range. Check the operating range and status of the copy pair that you want to acquire, and execute the YKP2B command again. If the copy pair status is SIMPLEX, the YKP2B command does not detect any copy pair.
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x – YKB20x) (continued) Message ID Message text Explanation and recommended actions YKB201W TSO No I/O paths are available No copy pair information was acquired from the volume to which for the specified devices. the device number Devn was assigned because no I/O paths are DEVN=Devn available. Verify the I/O path settings.
Table 2 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKA0x – YKB20x) (continued) Message ID Message text Explanation and recommended actions Device number being processed when a dynamic change was detected in an I/O configuration definition YKC000T TSO RC=48 Supplied parameters invalid Invalid parameters are specified.
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 Starting FROMVSN() value invalid The value specified in the FROMVSN parameter is invalid. YKC008E MSG SC=48 Ending TOVSN() value invalid The value specified in the TOVSN parameter is invalid.
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.
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.
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 171).
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.
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.
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.
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.
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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (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.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (continued) Message ID Message text Explanation and recommended actions 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 line in EXCTG CSV file is incorrect.
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (continued) Message ID Message text defined in EXCTG information CSV file: dd-name: rec# 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 YKJ258E TSO RC=32 The EXCTG information is The following entries specified as EXCTG information are inconsistent: dd-name:
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (continued) Message ID Message text Explanation and recommended actions 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 includes no entries (lines) corresponding to the entries (lines) specified in the CTG information CSV
Table 8 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKG2x – YKK10x) (continued) Message ID Message text service=service-name, code=code1, code2 . Explanation and recommended actions Name of the OS service that encountered an error code1 Return code of the OS service that encountered an error code2 Reason code of the OS service that encountered an error If no reason code is returned for an OS service, 0 is output.
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.
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.
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.
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.
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.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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#.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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.
Table 10 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKL2x – YKL4x) (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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 XP7 for Business Continuity Manager Installation Guide. nn Return code of the service YKM904E TSO Message library was not found.
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.
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.
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.
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.
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.
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.
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.
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 XP7 for Business Continuity Manager 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.
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 XP7 for Business Continuity Manager User’ Guide.
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.
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).
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.
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.
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
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 ".
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.
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.
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.
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.
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.
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 XP7 for Business Continuity Manager Reference Guide.
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.
Table 30 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY0x) (continued) Message ID Message text Explanation and recommended actions r 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.
Table 30 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY0x) (continued) Message ID Message text Explanation and recommended actions 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.
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.
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
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x – XKY5x) (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.
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x – XKY5x) (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= loca
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x – XKY5x) (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.
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x – XKY5x) (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.
Table 32 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY3x – XKY5x) (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.
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.
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.
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'.
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 – XKY9x) Message ID Message text Explanation and recommended actions YKY703E XML XML translation error: The sent entity This is an XML error.
Table 34 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY7x – XKY9x) (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.
Table 34 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKY7x – XKY9x) (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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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 172).
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
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.
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.
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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
Table 44 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ40x) (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.
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.
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions • UR_PathID: Path group specification for Cnt Ac-J Z • GroupID=consistencygroup-ID-of-TrueCopy-copygroup-(hexadecimal-number): Consistency group ID for the Cnt Ac-S Z copy group that exceeds X'7F' 1 If this message is output while the YKLOAD command is being executed, the RC is 44.
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions • Quick suspend mode for the CAJ ATTIME suspend function ◦ XP24000/XP20000 disk array Version of the storage system support function: X'23' or higher • Path group ID specification for Cnt Ac-J Z ◦ XP P9500 Version of the storage system support function: X'33' or higher • Consistency group ID for the Cnt Ac-S Z copy g
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions systems with the following versions of the storage system support function: • XP12000/XP10000 disk array Version of the storage system support function: X'11' or higher • XP24000/XP20000 disk array Version of the storage system support function: X'20' or higher YKZ417E MSG SC=48 RC=48 This command is invalid for CA Copy
Table 45 Business Continuity Manager error messages and corresponding troubleshooting actions (message ID YKZ41x) (continued) Message ID Message text Explanation and recommended actions characters exceeds 118, the excess part will be truncated. YKZ911I CON command RC=rc This log message gives the execution results of a CLI command. command The name of the CLI command rc Return code of the CLI command See the CLI command descriptions in the HP XP7 Business Continuity Manager Reference Guide.
: ATTIME suspend time : ATTIME suspend status YK8312I PRT REPORT DETAIL: COPY GROUP: PREFIX : DAD-ID : TYPE : PRI VOLSER DEVN DIR SEC DEVN STATUS MATCH RATE% C/T ID SUB C/T C/T DELTA C/T TIME The results of REPORT(DETAIL)are displayed.
YK8316I PRT REPORT STATS: COPY GROUP : PREFIX : DAD-ID : TYPE : C/T ID PRISN SECSN --- PRI %S ---SFT RSF RSF WPR TOT C/T TOT - SEC %S -RSF RSF WPR TOT C/T TOT --- TIMERS --TRANS OFLD RCUR CPND KBYTES/S SEC MIN MIN The results of REPORT(STATS) for the TCA copy group are displayed.
: Serial number of the primary storage system : Serial number of the secondary storage system : Data transfer rate (Kbps) between the main control unit and the remote control unit : Master journal volume metadata percent usage : Master journal volume data percent usage : Restore journal volume metadata percent usage : Restore journal volume data percent usage : Master journal volume data capacity (GB) : Restore journal volume data capacity (GB) YK8411I PRT SYSTEM OPTIONS: CYCLE T
: Startup action executed if the copy pair status for starting BCM Monitor is different from the specified startup status : Option information of the CGSTARTUPSTATUS parameter : Status, action, and error action for the copy group specified in STATUS and ACTION. These parameters appear a specified number of times. User completion codes Table 46 (page 170) provides details about the user completion codes.
Identifying the volume to be processed The volume to be processed is determined by the copy group number and copy pair number output in a message as follows: Identifying the volume serial number from the REXX script Display the following STEM variable. stem-name.CopyGroup..copy-group-number..Pair..copy-pair-number.Volser Identifying the volume serial number from the configuration file Use the following steps to acquire the volume serial number from the configuration file: 1.
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.
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 CAA CAJ CMD PATH THPz Others 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.
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 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.
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details Type of error 20C9 If the emulation type of the P-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: BC CA CAA CAJ CMD PATH THPz Others • No mainframe Fibre Channel adapter is installed. • All of the mainframe Fibre Channel adapters are blocked.
Table 47 Details of error codes 20xx – 22xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others CAA CAJ CMD PATH THPz Others P-VOL of a BC copy pair with a C/T group ID. 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.
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others is not in the PENDING or DUPLEX status is included in the C/T group. • The ATTIME suspend time cannot be set because the specified C/T group contains a copy pair that was created by using RAID Manager to specify the BC C/T group ID. If the reason why the copy pair status cannot be changed is not one of the above, the ATTIME suspend time cannot be set.
Table 48 Details of error codes 23xx (continued) Error code Error details 2331 A BC copy pair cannot be made. The reason might be one of the following: Type of error BC CA Output Not output • P-VOL is a Reserve volume. • The volume size of P-VOL differs from that of S-VOL. • The shared memory capacity is insufficient for copy pair creation. 2332 A BC copy pair status cannot be Output Not output transitioned because the maximum multiplicity of the copy pairs for the P-VOL was exceeded.
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others transition. The reason might be one of the following: • The volume specified to be the S-VOL is already the P-VOL of a BC copy pair. • The volume specified to be the S-VOL is in the SIMPLEX status. 2346 A BC copy pair status cannot be Output Not output changed because the volume specified to be the S-VOL is already the P-VOL of a CA or CAA copy pair.
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error BC CA Quick specified because the P-VOL is the S-VOL of a CA or CAA copy pair that is not in the suspend status. 235D A BC copy pair cannot be Output Not output resynchronized with Reverse or Quick specified because the S-VOL is the P-VOL of a CA or CAA copy pair that is not in the suspend status. 2370 A BC copy pair status cannot be changed because the specified volume does not exist.
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error 2395 A BC copy pair status cannot be Output Not output changed because the volume specified to be the BC P-VOL is in the Reverse Resync status with another copy pair which shares the P-VOL. 2398 A BC copy pair cannot be Output Not output resynchronized (including Reverse) because the copy pair is not in the Split status.
Table 48 Details of error codes 23xx (continued) Error code Error details Type of error 23EF A BC copy pair cannot be deleted Output Not output because the specified BC copy pair is in SUSPVS status. 23F1 The command could not be executed because the specified C/T group ID is out of the valid range. 23F2 The command cannot be executed. Output Not output The reason might be one of the following: BC CA Output Not output • The specified C/T group ID is not registered.
Table 49 Details of error codes 36xx Error code Error details 3613 Registration to EXCTG has failed because the specified arbitration command device is not an arbitration command device. 3614 Registration to EXCTG has failed.
Table 49 Details of error codes 36xx (continued) Error code Error details 3685 Registration to EXCTG has failed because the specified storage system model name is invalid. 3686 3688 Type of error BC CA CAA CAJ CMD PATH Not output Output Not output Registration to EXCTG has failed because the journal group to be registered is already registered to another EXCTG.
Table 50 Details of error codes 37xx (continued) Error code Error details 3705 Type of error BC CA CAA CAJ CMD PATH The command for delta resync Not output cannot be executed because the device on the S-VOL does not support delta resync. Output Not output 3706 A delta resync pair cannot be Not output made because the command target volume is the S-VOL of a CA copy pair and the copy pair status is not Duplex. Output Not output 3707 A delta resync pair cannot be executed.
Table 50 Details of error codes 37xx (continued) Error code Error details 3711 A CAJ copy pair cannot be resynchronized (with the PREPARE parameter) because the journal volume is blocked. 3720 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 journal volume in M-JNL is blocked.
Table 50 Details of error codes 37xx (continued) Error code Error details 3739 The CAJ copy pair cannot be created for the following reasons: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output Not output Output Not output 373E A CAJ copy pair cannot be Not output created between the primary site and the intermediate site in a 3DC Cascade (CAJxCAJ) configuration because the mirror status of the CAJ copy group between the intermediate site and the remote site is not Initial or
Table 50 Details of error codes 37xx (continued) Error code Error details Type of error 3755 A CAJ copy pair cannot be Not output resynchronized. Possible reasons include both of the following: BC CA CAA CAJ CMD PATH Output Not output Output Not output THPz Others • The specified S-VOL is already in use as an S-VOL in a CAJ copy pair that has another mirror ID. • Another CAJ copy pair using the specified S-VOL is not in the SWAPPING status.
Table 51 Details of error codes 46xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH Not output Output Not output THPz Others 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. 4603 A CAJ copy pair cannot be dissolved. Possible reasons include one or both of the following: • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system.
Table 51 Details of error codes 46xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others primary storage system and secondary storage system. 4615 A CAJ copy pair status cannot be Not output changed because the I/O execution volume and the P-VOL for the parameter do not match.
Table 51 Details of error codes 46xx (continued) Error code Error details Type of error 4630 The command could not be executed because the 3-site function is not supported. 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. The command might have failed because the YKQUERY command was not executed in advance.
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.
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.
Table 52 Details of error codes 47xx – 49xx Error code Error details 47A3 Type of error BC CA 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.
Table 53 Details of error codes 4Axx Error code Error details Type of error 4A08 The C/T group ID specified for the CAA C/T group option change is incorrect. Not output Output Not output 4A0B The C/T group ID specified for the CAA C/T group option change is not registered. Not output Output Not output 4A0C The C/T group timer type Not output (SYSTEM/LOCAL/NONE) for the CAA cannot be changed because there is a copy pair in this C/T group.
Table 53 Details of error codes 4Axx (continued) Error code Error details 4A82 The C/T group cannot be registered because the CAA program product is not installed. 4A8B The command could not be Not executed because the status of the output CA or CAA copy pair is invalid. Output Not output 4A8C The command could not be Not executed because the status of the output CA or CAA copy pair is being changed.
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.
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.
Table 54 Details of error codes 4Bxx (continued) Error code Error details Type of error 4B11 FREEZE cannot be executed for a Not copy pair that is in a CA copy output group 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.
Table 54 Details of error codes 4Bxx (continued) Error code Error details Type of error 4B49 The remote command cannot be executed because the path between the specified storage system or CU (SSID) and the command target storage system is not set, or an error has occurred on the path. 4B85 The CA copy pair that specified Not a C/T group ID cannot be created output because the specified volume is a FlashCopy pair.
Table 55 Details of error codes 50xx – 6Exx Error code Error details Type of error 501C The command device cannot be defined because the specified volume is a journal volume. Alternatively, a CAJ copy pair cannot be made. Not output 64E2 A command device cannot be deleted because the APID differs from the defined APID. Not output Output Not output 64E3 The remote DKC control function cannot be executed because the command device is not set.
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error 64FF A command device cannot be defined because the APID specified by the parameter does not match the APID defined for the command device. Not output 69E4 A parameter error occurred. This error might occur during a storage system configuration change or operation after the microcode is changed. If this occurs, scan the storage system by using Business Continuity Manager to obtain volume information again.
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error 69F3 A copy pair cannot be created or Output resynchronized. The reason might be one of the following: BC CA CAA CAJ CMD PATH THPz Others Not output • The storage system serial number of the P-VOL is incorrect. • The SSID of the P-VOL is incorrect. • The CU number is not supported. • The storage system does not support the Open/MF Consistency Preservation Function.
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error 6A07 The command could not be Not output executed because the corresponding volume is not the P-VOL of a CAA copy pair or it is a Non Gen'ed volume. Output Not output 6A08 An ATTIME suspend time for CAA Not output cannot be set because there is a copy pair that is not in the DUPLEX status.
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output contains invalid information, or a specified value is out of the supported range. 6EC2 The setting or status acquisition Not output command for THP could not be executed because of either of the following reasons: • The volume or pool ID that was specified does not exist. • The attribute of the pool that belongs to the target device is not THP.
Table 55 Details of error codes 50xx – 6Exx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others or stop) of the pool for THPz failed. • An attempt to change the monitoring status (to start or stop) of the pool for THPz failed. 6EC7 The setting of the pool for THPz failed due to a logical error. Not output Output Not output 6EC8 Configuration of the THP volume failed because an internal processing error occurred in the storage system.
Table 56 Details of error codes 7Fxx – 8Cxx Error code Error details Type of error 7F86 The command cannot be executed Not output because no program product for copying is installed. Output 7FD4 This command is not supported. Not output Output 8C12 A CA or CAA copy pair status cannot be changed. Possible reasons include one or more of the following: Not output BC CA Output CAA CAJ Not output CMD PATH Output THPz Not output Others Output • The specified S-VOL is online.
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 documented by error codes C120 to C12F.) 8C1E A CAJ copy pair cannot be made. Not output Possible reasons include one or both of the following: • The micro version on the specified primary storage system does not support a connection with the specified secondary storage system.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output Output Not output parameter. Alternatively, path establishment is not supported. 8D09 A path cannot be deleted because Not output there is an invalid parameter. Alternatively, path deletion is not supported. 8D10 A copy pair cannot be made.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ reasons include one or more of the following: • The status of the copy pair does not allow the status transition. For details, see error code 2310. • The charging limit of the program product was exceeded. • The copy pair is in the Pending status. • The copy pair is not in the Split status. • The specified C/T group ID is not registered.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others reasons include one or more of the following: • The S-VOL is online. • The status of the copy pair does not allow the status transition. For details, see error code 2310. • The P-VOL is online. • The charging limit of the program product was exceeded. • The copy pair is in the Pending status. • The copy pair is not in the Split status.
Table 57 Details of error codes 8Dxx (continued) Error code Error details 8D27 A BC copy pair cannot be suspended. Possible reasons include one or more of the following: Type of error BC CA CAA CAJ 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 SIMPLEX status. • The copy pair is in the Split status. • The specified C/T group ID is not registered.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others Output Not output Output • The S-VOL is in the Pending status. • The status is invalid. • The status of the copy pair is being changed. 8D2A A BC copy pair cannot be suspended. Possible reasons include one or more of the following: Output Not output • The status of the copy pair does not allow the status transition. For details, see error code 2310.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8D42 The command cannot be executed Not output because the volume specified as a command device is a volume used in the open system. Output Not output 8D43 The command could not be Not output executed because the logical volume of the specified volume is blocked. Output Not output 8D44 The command could not be executed because the specified volume has PIN data.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8D52 The command could not be Not output executed because the logical volume of the specified volume is blocked. 8D56 A BC copy pair cannot be dissolved. Possible reasons include one or more of the following: BC CA CAA CAJ CMD PATH THPz Others Output Not output Output Not output • The status of the copy pair does not allow the status transition. For details, see error code 2310.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others • The serial number or SSID of the secondary storage system in the parameter does not match the storage system serial number or SSID of RCU. • The S-VOL number in the parameter and bootup volume number do not match. • The status of the copy pair is invalid. • The status of the copy pair is being changed. 8D5B A BC copy pair cannot be dissolved.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8D78 The host command parameter is incorrect. 8D79 A CAA C/T group cannot be Not output deleted. Possible reasons include one or more of the following: BC CA CAA CAJ CMD PATH THPz Not output Others Output Output Not output • The C/T group ID is incorrect. • The C/T group is not registered. • There is a CAA copy pair in the corresponding C/T group.
Table 57 Details of error codes 8Dxx (continued) Error code Error details Type of error 8DF7 The command could not be Not output executed because the SSID of the host command parameter and the local storage system do not match. Output 8DFF The command could not be executed because the sub-command code is incorrect.
Table 58 Details of error codes 8Fxx (continued) Error code Error details Type of error 8F21 A CAJ copy pair cannot be Not output made. The reason might be one of the following: BC CA CAA CAJ CMD PATH Output Not output THPz Others • The configurations cannot be combined because the specified volume is the P-VOL of a CA or CAA copy pair, or the specified volume is part of a BC copy pair. • 0 (zero) is specified as the mirror ID in the CA or CAA configurations.
Table 58 Details of error codes 8Fxx (continued) Error code Error details 8F35 A CAJ copy pair cannot be made because the specified volume is blocked. Type of error BC CA CAA CAJ CMD PATH Not output Output Not output 8F39 A CAJ copy pair cannot be Not output made because the CAJ program product is not installed. Output Not output 8F4D A CAJ copy pair cannot be made or resynchronized.
Table 59 Details of error codes C0xx Error code Error details Type of error C023 The specified serial number or Not output SSID of the primary storage system is different from the storage system serial number or SSID of the local CU. Output Not output C026 A path cannot be set because Not output the specified CU number for the secondary site is not supported for the primary or secondary storage system. Output Not output C02B The specified P-VOL does not match the startup volume.
Table 59 Details of error codes C0xx (continued) Error code Error details Type of error C05A The serial number or SSID of the Not primary 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 C05D 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 RCU.
Table 59 Details of error codes C0xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others match the storage system serial number or SSID of the RCU. C074 No CA copy pair can be made Not because the CA program output product is not installed Output Not output C078 The S-VOL number in the CA or Not CAA parameter does not match output the bootup volume number.
Table 60 Details of error codes C1xx Error code Error details C120 An attempt to establish a path has failed. Possible reasons include either of the following: Type of error BC CA CAA CAJ CMD PATH THPz Others Not output Output Not output • For an inter-CU logical path, the number of RCUs registered in the MCU exceeds 4. • For an inter-DKC logical path, the number of path group IDs registered in one storage system exceeds 64.
Table 60 Details of error codes C1xx (continued) Error code Error details C12A Type of error BC CA CAA CAJ CMD PATH THPz Others The command could not be Not output executed because the device-identifying code of an RCU for which path deletion is specified is invalid, or because the RCU type (FIBRE/ESCON) is invalid. Output Not output C12B The command could not be Not output executed because there are one or more paths that have a different serial number.
Table 60 Details of error codes C1xx (continued) Error code Error details C194 A copy pair cannot be suspended because the S-VOL status is being changed. Type of error BC CA CAA CAJ Not output Output Not output C195 A copy pair cannot be Not suspended because the specified output copy pair is already in the suspend status. Output Not output C198 The command cannot be Not executed because there is no output copy pair that can be suspended in the group.
Table 61 Details of error codes C2xx (continued) Error code Error details Type of error C215 A copy pair cannot be made Not because the specified S-VOL is output in use by another copy pair. Output Not output C21A A copy pair cannot be Not resynchronized because the output specified copy pair is not in the suspend status.
Table 61 Details of error codes C2xx (continued) Error code Error details Type of error C2B3 A copy pair cannot be created Not because the THPz volume output specified for the P-VOL is being expanded. Output Not output C2B6 A copy pair cannot be created Not because the pages of the THPz output volume specified for the P-VOL are being released.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C314 The P-VOL is not in the SIMPLEX Not output status. Output Not output C315 The P-VOL has PIN data. Not output Output Not output C316 The drive copy is being performed on the P-VOL (troubleshooting). Not output Output Not output C317 The drive copy is being performed on the P-VOL (SVP request). Not output Output Not output C318 The copy task ending process is Not being performed on the P-VOL.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C32A The S-VOL is protected by LDEV Not security. output Output Not output C32B The P-VOL is protected by LDEV security. Not output Output Not output C32C The S-VOL is protected by LDEV Not guard. output Output Not output C32E A copy pair cannot be made Not because connection with the output specified S-VOL is not supported.
Table 62 Details of error codes C3xx (continued) Error code Error details C370 Type of error BC CA CAA CAJ The condition setting for the number of the Minimum Path is incorrect (path problem or invalid path). Not output Output Not output C371 Recovery processing for cache memory or shared memory is being performed. Wait a few minutes, and then execute again. Not output Output Not output C372 Recovery processing for cache memory or shared memory is being performed.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error C382 The cache for the MCU is being Not blocked on one side (in output transition) or it is being recovered on one side. Output Not output C388 A copy pair cannot be made Not because the P-VOL is not output supported for the emulation type. Output Not output C38B RCU is already in use by CA or Not CAA. output Output Not output C38D A CA copy pair cannot be defined or resynchronized.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error 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. Not output Output Not output C3A8 A copy pair cannot be created Not because the specified copy pair output is made up of volumes whose emulation types are 3390-A and non-3390-A.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error BC CA CAA CAJ or CAA copy pair. Also, a P-VOL in the Reverse Resync status and the S-VOL for FlashCopy cannot be specified. C3C0 When the P-VOL of a CA or Not CAA copy pair is also the S-VOL output of a BC copy pair, both S-VOLs must be a copy pair in a one-to-one combination. Output Not output C3C1 The S-VOL is not made under the Not output C/T group.
Table 62 Details of error codes C3xx (continued) Error code Error details Type of error 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. Not output Output Not output C3D6 The specified S-VOL cannot be Not used because the device cannot output be recognized from the connection port.
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.
Table 63 Details of error codes CBxx (continued) Error code Error details CB68 Type of error BC CA CAA CAJ A CA copy pair cannot be made because the necessary difference area does not exist in the MCU. Not output Output Not output CB69 The upper limit of 4,096 (or more) copy pairs cannot be made within the same C/T group by RCU. Not output CB78 A copy pair cannot be made Not because the specified S-VOL is output defined as a command device.
Table 63 Details of error codes CBxx (continued) Error code Error details Type of error CBE3 A copy pair cannot be created Not because the specified S-VOL is output a pool volume. Output Not output CBED A CA/CAA copy pair cannot Not be made.
Table 64 Details of error codes DBxx – E8xx Error code Error details Type of error DB02 A CAJ copy pair status cannot Not output be changed because the status transition is not allowed. BC CA CAA CAJ CMD PATH Output Not output THPz Others In the following examples, status transition is not allowed: • When an attempt to create a copy pair is made for a copy pair whose status is not SIMPLEX.
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH Not output Output Not output E86B A CAJ copy pair cannot be Not output dissolved because the specified volume is not a CAJ copy pair. Output Not output E86D A CAJ copy pair cannot be dissolved because the storage system is being turned on.
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details E87E A CAJ copy pair cannot be made because the specified P-VOL or S-VOL is a volume comprising a journal group. Type of error BC CAJ CMD Not output Output Not output E880 A CAJ copy pair cannot be Not output made because the emulation type for the specified P-VOL or S-VOL does not match the emulation type for a volume comprising a journal group.
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH mirror ID in the journal group. E891 A CAJ copy pair cannot be Not output made because the maximum number of copy pairs has already been registered in the specified M-JNL or R-JNL group. Output Not output E894 A CAJ copy pair cannot be Not output created in a 3DC (CAJxCAJ) configuration because the third mirror ID is specified in the same journal group.
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details E8A2 A CAJ copy pair cannot be made for one of the following reasons: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output E8A6 A resynchronization that Not output reverses the copy direction for CAJ copy pairs cannot be performed because the journal group of the specified volume is not registered in the storage system.
Table 64 Details of error codes DBxx – E8xx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others number which can be registered. Table 65 Details of error codes EAxx Error code Error details Type of error EA00 The CAJ copy pair cannot be Not output operated for each EXCTG because of the following reasons: BC CA CAA CAJ CMD PATH Output Not output Not output Output Not output • The JNLG specified in the copy group is not registered in the EXCTG.
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA0A A CAJ copy pair cannot be made because the status of the R-JNL group is incorrect. Not output Output Not output EA12 The CAJ copy pair could not Not output be resynchronized in the reverse direction because the copy pair is not in the SWAPPING status. Output Not output EA13 A CAJ copy pair cannot be Not output resynchronized because the volume specified for the P-VOL is the S-VOL of the CAJ copy pair.
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA22 A CAJ copy pair resynchronization, which causes a copy direction reversal, cannot be made because the journal group is not in the Stop status. Not output Output Not output EA25 A CAJ copy pair resynchronization, which causes a copy direction reversal, cannot be made because the copy pair is not in the SWAPPING status.
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error EA46 A CAJ copy pair between the Not output intermediate site and the remote site cannot be deleted or suspended because the journal group of the CAJ copy pair between the primary site and the intermediate site in a 3DC Cascade (CAJxCAJ) configuration is in the Active status. Output Not output EA4D The CAJ copy pair cannot be Not output suspended because it is a delta resync pair.
Table 65 Details of error codes EAxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others THPz Others license capacity of this and all related program products. EAA6 A CAJ copy pair cannot be Not output made because the charging limit of CA in the MCU has been exceeded. Check the license capacity of this and all related program products.
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 entered parameter was incorrect. EB0A Registration to or deletion from EXCTG has failed because another EXCTG registration or deletion process is in progress. Not output Output Not output EB0F Registration to or deletion Not output from EXCTG has failed because the specified device is not an arbitration command device.
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others specify a secondary storage system that differs from the secondarystorage system of the existing copy pair. Therefore, a CAJ copy pair cannot be made. 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.
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error BC CA CAA CAJ CMD PATH THPz Others M-JNL group is not registered in the storage system. EB4F A CAJ copy pair cannot be Not output made because the timer type for M-JNLG differs from that for R-JNLG. Output Not output EB50 A CAJ copy pair cannot be made because the specified volume does not exist. Not output Output Not output EB51 A CAJ copy pair cannot be made because the specified S-VOL has PIN data.
Table 66 Details of error codes EBxx (continued) Error code Error details EB62 A CAJ copy pair cannot be made because the specified P-VOL is a command device. EB63 Type of error BC CA CAA CAJ CMD PATH Not output Output Not output A CAJ copy pair cannot be made because another journal group pair has been already made in the R-JNL group. Not output Output Not output EB64 A CAJ copy pair cannot be made because the charging limit of the program product has been exceeded.
Table 66 Details of error codes EBxx (continued) Error code Error details EB7D A CAJ copy pair cannot be made because the specified S-VOL is an external volume. EB7E A CAJ copy pair cannot be made. The reason might be one of the following: Type of error BC CA CAA CAJ CMD PATH Not output Output Not output Not output Output Not output EB7F A CAJ copy pair cannot be Not output made because the emulation type of the specified S-VOL is not supported.
Table 66 Details of error codes EBxx (continued) Error code Error details Type of error EB88 A CAJ copy pair could not be Not output made because of one the following reasons: BC CA CAA CAJ CMD PATH Output Not output • The specified S-VOL is already being used as the S-VOL of a BC copy pair. • The specified volume is in Not Ready status. • The LDEV guard (PROTECT) is set for the S-VOL.
Table 66 Details of error codes EBxx (continued) Error code Error details EBC6 Type of error BC CA CAA CAJ CMD PATH A delta resync pair cannot be Not output made because the S-VOL of the specified copy pair is used by another program product (BC/FlashCopy). Output Not output EBCE A CAJ copy pair cannot be Not output resynchronized (with the DELTAJNL parameter) because the specified S-VOL has old differential information. Execute the CAJ copy pair resynchronization (with the ALLJNL parameter).
Table 66 Details of error codes EBxx (continued) Error code Error details EBE1 EBE2 Type of error BC CA CAA CAJ CMD PATH A delta resync cannot be Not output executed because none of the S-VOLs of the delta resync pair are the S-VOLs of the other CAJ. Output Not output A delta resync cannot be Not output executed because the differential bitmap information is not ready status to delta resync.
3 Support and other resources Contacting HP For worldwide technical support information, see the HP Support Center: http://www.hp.com/go/hpsc Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages • Operating system type and revision level • Detailed questions Related information This manual is part of a related set of manuals.
• MVS System Codes, GC28-1780 • 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
http://www.hp.com/support/manuals 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.
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
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.
Glossary A API Application programming interface. B BC Manager BCM A generic name for the following products: • HP XP7 for Business Continuity Manager Software • HP XP7 for Business Continuity Manager Extended CT Group • HP XP7 for Business Continuity Manager 4x4 Extended CT Software Business Continuity Manager 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.
L LD, LDEV Logical device. An LDEV is created when a RAID group is carved into pieces according to the selected host emulation mode (that is, OPEN-3, OPEN-8, OPEN-9). The number of resulting LDEVs depends on the selected emulation mode. The term LDEV is also known as term volume. 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.
U UR Hitachi Universal Replicator. Also known as HP XP Continuous Access Journal (Cnt Acc-J). V VM Virtual Machine. X XML eXtensible markup language. XRC Extended remote copy. Z z/Linux 264 Glossary Linux on IBM System z.
