HP XP7 Smart Manager for Mainframe Messages Part number: TK916-96002 First edition: April 2014
Legal and notice information © Copyright 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.
Contents Preface ................................................................................................ 7 1 Messages ......................................................................................... 9 Message format .......................................................................................................................... 9 Message output format .........................................................................................................
Tables 1 List of messages (message ID KTx) ............................................................................. 11 2 List of messages (message ID YK70x - YK90x) ............................................................ 52 3 List of messages (message ID YKA0x - YKB20x) .......................................................... 73 4 List of messages (message ID YKC0x) ........................................................................ 77 5 List of messages (message ID YKD0x) .................
33 List of messages (message ID YKY3x - YKY5x) .......................................................... 151 34 List of messages (message ID YKY6x) ...................................................................... 156 35 List of messages (message ID YKY7x - YKY9x) .......................................................... 159 36 List of messages (message ID YKZ0x) ...................................................................... 162 37 List of messages (message ID YKZ10x - YKZ20x) ...............
Preface This document describes the messages and error codes that are output by the following program products. - HP XP7 Smart Manager for Mainframe Hereafter, the above product is simply called Smart Manager for Mainframe.
Preface
1 Messages This chapter describes the messages. Message format This section describes the format of the messages and the notations used in this manual. Message output format Each message consists of a message ID and message text. The message format is as follows: YYYnnnZ message-text The message ID format is as follows: • YYY Indicates the message type.
• YKH: YKH2B • YKJ: YKIMPORT, or YKEXPORT • YKK: YKINSCHK or KTINSCHK • YKL: YKLOAD • YKM: YKMAKE, messages displayed in the ISPF panel, or ISPFLOG • YKN: YKRUN • YKP: YKSTATS • YKQ: YKQUERY • YKR: YKRESYNC • YKS: YKSTORE • YKT: YKALCSVC, KTALCSVC, YKSETENV, or YKDSPENV • YKU: YKSUSPND • YKV: YKRECVER • YKW: YKWATCH • YKX: YKBLDCMD, YKDELCMD, or YKQRYDEV • YKY: Business Continuity Manager agent • YKZ: All commands or tools • nnn Indicates the serial number of the message.
#3 Detailed information used to confirm specific issues such as the error location or volume identification information. If the output destination is MSG, this value is set to Value in the message structure. #4 Character strings enclosed in square brackets ([ ]) might be omitted.
Message ID Message text Description An error occurred in the license key dataset. KTA052E ISPF An error occurred in the license key dataset. Make sure that the name of the license key dataset is correct, and that the license key dataset has been created correctly. If necessary, re-create the license key dataset and transfer the license key file again. An attempt was made to install a license key, but a license key that could be installed in the license key dataset was not found.
Message ID Message text Description This message indicates Smart Manager for Mainframe environment settings. variable - License info DSN prefix: Prefix of the license information dataset KTA401I CON variable: value - Event log output method: Event log output method - CLI log output settings: CLI command execution log output settings value Environment settings This message indicates the specified values for the Smart Manager for Mainframe environment variables and system symbols.
Message ID Message text Description KTC007E TSO SC=48 RC=48 Starting parameter-name-1 parameter value exceeds ending parameter-name-2. The starting value (minimum value) specified by parameter-name-1 exceeds the exit value (maximum value) specified by parameter-name-2. KTC008E TSO SC=48 RC=48 parameter-name parameter value is not valid hex. The value specified by parameter-name is not in hexadecimal format. The specified combination of parameters is invalid.
Message ID Message text Description This log message gives the execution results of a CLI command. command KTC911I CON command RC=rc The name of the issued CLI command rc Return code of the CLI command See the description of CLI commands in the manual HP XP7 Smart Manager for Mainframe User Guide. The configuration file could not be read because the record length is too long. file KTD085E MSG SC=40 RC=40 (file:rec#) Unable to read the configuration file.
Message ID Message text Description The configuration file file cannot be used. If the message IKJ58211I is displayed at the same time as this message, check the value of the DYNAMNBR parameter specified in the JCL EXEC statement. For details about the value to be specified, see the description of the KTSTORE or KTIMPORT command in HP XP7 Smart Manager for Mainframe User Guide.
Message ID Message text Description An attempt to close the configuration file indicated by file failed. KTD089E MSG SC=40 RC=40 (file) dsstate File Close error: dsstate. Status of the configuration file file Name of the configuration file in which the error was detected Configuration file file could not be allocated. Make sure that configuration file file has been created correctly. KTD090E MSG SC=40 RC=40 (file) File Allocation Failed: dsstate.
Message ID Message text Description The value of item name in the tiering policy information CSV file is not correct. value Value specified for item name name KTD201E MSG SC=32 RC=32 (file rec#) The value of name in the tiering policy information CSV file is invalid.
Message ID Message text Description The specified volume does not exist in the disk configuration definition file. The volume specified in the tiering policy information CSV file must exist in the disk configuration definition file. Scan the target volumes before executing the KTIMPORT command. Alternatively, execute the KTIMPORT command with the SCAN parameter specified. KTD206E MSG SC=32 RC=32 (file rec# device) file The specified volume does not exist in the disk configuration definition file.
Message ID Message text Description The attempt to output the record to the dataset failed because the length of the record record exceeds 252 characters. KTD260E MSG SC=44 RC=44 Too long record:record. The value of the REXX variable is incorrect. Check and revise the REXX variable so that the length of the record is no more than 252 characters. record Record that could not be output Creation of the configuration file will stop because an error occurred during creation.
Message ID Message text Description dsstate Status of the configuration file: DSORG = XX. The DSORG attribute value of the dataset RECFM = XX. The RECFM attribute value of the dataset LRECL = XX. The LRECL attribute value of the dataset BLKSIZE = XX. KTD270E MSG TSO SC=40 RC=40 The BLKSIZE attribute value of the dataset EXTENT=XX. Number of currently allocated dataset extents XX is the number of extents allocated to dataset-name.
Message ID Message text Description The command cannot be executed because a log stream process error occurred. message-text (character string) Message text, which indicates the following information. - If an OS macro error occurred: xxxxxxxx macro error, rc = rr xxxxxxxx: OS macro name rr: Macro return code - If the log stream definition is not for DASD only: KTG207E MSG TSO CON SC=52 RC=0 A log stream process error occurred.
Message ID Message text Description An error occurred in the system logger service. nnn (decimal number) Return code of the system logger service macro mmm (decimal number) Reason code of the system logger service macro (maintenance information) KTG217E MSG CON PRT SC=0 RC=0 A Logger error occurred.
Message ID Message text Description A YKLOG01 or YKLOG02 I/O error occurred. YKLOGnn YKLOG01 or YKLOG02 text Message acquired by using the SYNADAF macro KTG263E MSG CON SC=0 RC=0 A YKLOGnn I/O error. (text, cp=xxx:yyy) xxx (decimal number) Command code of the command that was being executed when the error occurred See the description of command codes for the KTZ201E message. yyy (character string) Maintenance information A YKLOG01 or YKLOG02 close error occurred.
Message ID Message text Description The log dataset is full. ddd Name of the log dataset that became full If the log dataset name cannot be acquired, * is displayed. KTG291I CON SC=0 RC=0 The log dataset is full. (DSN=ddd, cp=xxx:yyy) xxx (decimal number) Command code of the command that was being executed when the log dataset became full See the description of command codes for the KTZ201E message. yyy (character string) Maintenance information The log dataset was switched.
Message ID Message text Description The requested processing could not be performed. This device was skipped and processing continued. Check the status of the device that caused the error, correct any error in the configuration or execution conditions, and then re-execute the command. device-number-1 (character string) Device that issued an I/O device-number-2 (character string) Operation-target device If the device number of the operation-target device was not found, **** is displayed.
Message ID Message text Description An I/O error occurred. This device was skipped and processing continued. If sense byte information has been set, the KTH255E message displays the sense byte information. For CC=3: The indicated device might not have been installed or might not have been connected. For CC=0 and CSW=nnnnnn0000nnnn (DSB=00 and CSB=00) where n indicates a value: The indicated device might not have been installed or might not have been connected.
Message ID Message text Description This message displays detailed information for an I/O error. device-number-1 (character string) Device that issued an I/O device-number-2 (character string) Operation-target device If the device number of the operation-target device is not found, **** is displayed.
Message ID Message text Description The requested processing could not be performed. This device was skipped and processing continued. Check the status of the device that caused the error, correct any error in the configuration or execution conditions, and then re-execute the command. device-number-1 (character string) Device that issued an I/O device-number-2 (character string) Operation-target device If the device number of the operation-target device is not found, **** is displayed.
Message ID Message text Description KTM012E ISPF The End Devn value must not be lower than the Start Devn The device number specified in End is lower than the device number specified in Start. KTM014E ISPF The member name specified in COMMAND is invalid. Check the specified member name, or check whether the specified member exists. The member name specified in COMMAND is invalid. Check the specified member name, and check whether the specified member exists.
Message ID Message text Description KTM524E ISPF Please enter alphanumeric characters to Key Code field. The value specified in the Key Code field is neither a number nor alphabetic characters. KTM525E ISPF Invalid Key Code is entered. Please re-enter the Key Code. The key code is invalid. Enter the key code again. KTM526E ISPF Invalid dataset name is specified. The specified dataset name is invalid. KTM527E ISPF You cannot specify the license information dataset.
Message ID Message text KTM731E ISPF ISPF service error occurred. info Description An error occurred in the ISPF service. info Maintenance information An IKJPARS macro error occurred. IKJPARS error occurred. info KTM732E ISPF info Maintenance information No description for the specified error code was found. KTM765I ISPF A description for the specified error code was not found. KTM901E TSO ISPF service is not available. KTM902E TSO Load module is not found.
Message ID KTR010E TSO RC=40 Message text REXX failure return code=nnnn starting with variable name Description An attempt to access REXX variable name failed. The return code -2 indicates that the area for the REXX variable is insufficient. Check and revise the region size, and then re-execute the command. For details about the return codes, see the IRXEXCOM macro specifications in the manual TSO/E Programming Services.
Message ID Message text Description The command cannot be executed because a REXX write error occurred. nnn (decimal number) Return code of the OS REXX variable access routine - If the value of nnn is -2: The area for the REXX variable is insufficient. Check and, if necessary, review the region size, and then re-execute the command. For details about the return code, see the specifications for the IRXEXCOM macro in TSO/E Programming Services.
Message ID Message text Description The value (value) of name is invalid. Contact maintenance personnel. KTR250E MSG SC=36 RC=36 The value in the variable name is an invalid format. Value=value name Name of the REXX variable value Value of the REXX variable The variable value (value) indicated by name is invalid, so processing was canceled. The probable causes of the error are as follows: • An invalid value was specified for the parameter of the KTSTORE command.
Message ID Message text Description The version attribute value of the XML element on line number rec# in file is not recognized. KTX053W MSG SC=4 RC=4 (file:rec#) Unrecognized Version attribute value: value Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual HP XP7 Smart Manager for Mainframe User Guide.
Message ID Message text Description The encoding attribute value of the XML element on line number rec# in file is not recognized. KTX075W MSG SC=4 RC=4 (file:rec#) Unrecognized Encoding attribute value: value Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual HP XP7 Smart Manager for Mainframe User Guide.
Message ID Message text Description The Level attribute level of the APIInfo element on line number rec# in file is invalid. Check the indicated line, and then identify the cause of the error by referring to the description of the XML document type definition of the configuration file in the manual HP XP7 Smart Manager for Mainframe User Guide. file Name of the configuration file in which the error was detected KTX077W MSG SC=4 RC=4 (file:rec#) APIInfo Level=level invalid. Supported level is v.r.m.
Message ID Message text Description The necessary XML attribute name was not found. Revise the specification on line number rec# in file. file KTX251E MSG SC=36 RC=36 (file:rec#) name attribute missing. Name of the configuration file in which the error was detected rec# Number of the line in file where the error was detected The specification of an XML attribute is invalid. Revise the specification on line number rec# in file.
Message ID Message text Description Element DiskDevice, which is not included in the disk configuration definition file, was detected. Revise the specification on line number rec# in file. KTX256E MSG SC=36 RC=36 (file:rec#) The disk device information could not be resolved. file Name of the configuration file in which the error was detected rec# Number of the line in file where the error was detected The necessary XML element name was not found. Revise the specification on line number rec# in file.
Message ID Message text Description The XML element name-1 that cannot be specified is found in the XML element indicated in name-2. Revise the specification on line number rec# in file. KTX276E MSG SC=36 RC=36 (file:rec#) The element name-1 is not a content of the element name-2. file Name of the configuration file in which the error was detected rec# Number of the line in file where the error was detected The XML element name is not found. Revise the specification on line number rec# in file.
Message ID Message text Description The command cannot be executed because a macro error occurred. macro-name OS macro name xxx (decimal number) KTZ007E MSG SC=44 RC=44 Command code of the command that was being executed when the error occurred macro-name macro error occurred. (cmd=xxx, return code=nnn, reason code=mmm) See the description of command codes for the KTZ201E message.
Message ID Message text Description The SMS storage group information for storage-group-name could not be acquired. The probable causes of the failure are as follows. • The SMS storage group storage-group-name has not been defined. • The KTQRYSMS command is not registered as a TSO/E authorized command. KTZ100E MSG SC=36 RC=36 Information about the storage group storage-group-name could not be retrieved.
Message ID Message text Description A list of the active SMS storage groups could not be retrieved. The probable causes of the failure are as follows: • The KTQRYSMS command is not registered as a TSO/E authorized command. KTZ103E LOG SC=36 RC=36 A list of the active storage groups could not be retrieved. Follow the Smart Manager for Mainframe installation procedure to register the KTQRYSMS command with the IKJTSOxx parmlib member.
Message ID Message text Description The command cannot be executed because a GETMAIN error occurred. Expand the job execution area, and then re-execute the command. nnn (decimal number) GETMAIN macro return code mmm (decimal number) Area size area (character string) HIGH means 16 MB or more. LOW means less than 16 MB. xxx (decimal number) Command code of the command that was being executed when the error occurred 80: KTSCAN KTZ201E MSG TSO CON PRT SC=44 RC=44# 81: KTIMPORT A GETMAIN error occurred.
Message ID Message text Description The command cannot be executed because a parameter error occurred. message-text (character string) Message text KTZ205E PRT RC=0 A Parameter error occurred. (detail=message-text, cmd=xxx, pos=yyy) xxx (decimal number) Command code of the command being executed when the error occurred. For details, see the command code description for the KTZ201E message. yyy (character string) Maintenance information The command cannot be executed because an I/O error occurred.
Message ID Message text Description The command cannot be executed because a Core processing error occurred. message-text (character string) Message text, which provides the following information.
Message ID Message text Description Core processing ended. process (character string) Process name yyyy/mm/dd (character string) GMT date hh:mm:ss.th (character string) KTZ209I CON PRT RC=0 The Core processing( process ) ended. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) GMT time ttt (character string) Format of GMT time xxx (decimal number) Command code of the executed command For details, see the command code description for the KTZ201E message.
Message ID Message text Description A FREEMAIN error occurred. Contact maintenance personnel. nnn (decimal number) FREEMAIN macro return code xxx (decimal number) Command code of the command that was being executed when the error occurred KTZ212W CON# RC=0 A FREEMAIN error occurred. (return code=nnn, cmd=xxx, pos=yyy) See the description of command codes for the KTZ201E message.
Message ID Message text Description Parameters were input from SYSIN. nnn (decimal number) KTZ266I PRT RC=0 Parameters were input. ( nnn, xxx ) Number of lines xxx (character string) Parameter input The dataset format is invalid. ddd DD name KKK If DSORG is abnormal: DSORG If RECFM is abnormal: RECFM If LRECL is abnormal: LRECL If BLKSIZE is abnormal: BLKSIZE AAA KTZ268E MSG CON PRT SC=0 RC=0 File attribute value that caused the error.
Message ID Message text Description An unexpected error occurred. This error might have occurred with another error. If another error message was output concurrently with this error message, first resolve the problem indicated in that message. KTZ298E MSG TSO SC=44 RC=44 (detailed-info) cli-name encountered an unexpected error. If no other error messages were output, the version for the registered user SVC might not satisfy the prerequisite conditions for the user SVC version.
List of messages starting with YK The following tables list and describe messages starting with YK. Wait until all pending commands have finished execution before taking corrective action. Table 2 List of messages (message ID YK70x - YK90x) Message ID Message text Explanation and recommended actions YK7000T PRT RC=16 Supplied parameters invalid: line An invalid parameter was specified. Revise the value specified on the line number identified by line.
Message ID YK7099I PRT Message text YKBTSCAN return code=nnnn Explanation and recommended actions YKBTSCAN terminated with the return code nnnn. This message is always displayed to indicate the return code. nnnn Maximum value among the output return codes BCM Monitor has started. YK8001I CON BCM Monitor started. (v.r.m-nn) v.r.m-nn Version and revision number YK8002I CON BCM Monitor terminated. BCM Monitor has stopped. BCM Monitor set the monitoring status of all copy groups to INACTIVE.
Message ID Message text YK8010E CON Module not found: load-modulename. YK8011E CON The profile is not defined in the facility class of RACF: xxxxxxxx. Explanation and recommended actions The load module identified by load-module-name cannot be found. BCM Monitor will stop. Check whether the load module has been properly installed. The STGADMIN.YKA.BCM.YKQUERY profile or the STGADMIN.YKA.BCM.COMMANDS profile is not defined in the FACILITY class of RACF.
Message ID Message text Explanation and recommended actions YK8021I CON Execution waiting command none. There is no command waiting to be executed. YK8022I CON The state of sleep was released. BCM Monitor returned from the sleep state. YK8023W CON The WAKEUP command was not executed because it is not in a sleep status. The WAKEUP command cannot be executed because BCM Monitor is not in the sleep state. YK8024E CON Insufficient space available: maintenance-information.
Message ID Message text Explanation and recommended actions The IRXTERM routine returned an error with the return code identified by return-code. BCM Monitor will stop. Check the return code. return-code YK8027E CON IRXTERM module error: code=return-code,R0=abnormal-termination-code-and-reasoncode-for-abnormal-termination. BCM Monitor function abend: code=Sxxx Uxxxx For details about the return code, see TSO/E REXX Reference.
Message ID Message text Explanation and recommended actions The value identified by error-type, which was specified in the command-name command, is invalid. YK8031W CON The specified error-type is invalid: command-name. error-type • label: The label name is invalid. Check the label name for ACTION=STOPPOINT specified in the YKMONCG file. • copy group: The copy group ID is invalid. Check the copy group ID for CGID specified in the YKMONCG file. BCM Monitor will stop at the point label.
Message ID Message text Explanation and recommended actions BCM Monitor has reached the end of a cycle. YK8045I PRT CON time BCM Monitor reached the end of the monitoring cycle. time Message output time This is only displayed when the output destination is SYSTSPRT. BCM Monitor will execute the operator command identified by opcmd. YK8046I PRT CON time Execute operator command 'opcmd'. time Message output time This is only displayed when the output destination is SYSTSPRT.
Message ID Message text Explanation and recommended actions BCM Monitor will go to sleep because the PAUSE action was executed. Entering the WAKEUP command resumes copy group monitoring before the sleep time of sleep-time has elapsed. YK8055I PRT CON time BCM Monitor will pause now for 'sleep-time' minutes. time Message output time This is only displayed when the output destination is SYSTSPRT. sleep-time Sleep duration BCM Monitor failed to execute an operator command.
Message ID Message text Explanation and recommended actions There is a syntax error in a parameter. time Message output time YK8075E PRT time Parameter syntax error : file : rec#. This is only displayed when the output destination is SYSTSPRT. file Name of the file where the error occurred rec# Line number in the file file where the error was detected An invalid parameter was specified. time Message output time YK8076E PRT time Invalid parameter was specified : file : rec#.
Message ID Message text Explanation and recommended actions The copy group cgid is specified more than once in the YKMONCG file. time YK8080E PRT time Duplicate CGID parameters found : cgid. Message output time This is only displayed when the output destination is SYSTSPRT. cgid CGID parameter value that is specified more than once The combination of STATUS and ACTION specified in the YKMONCG file is invalid. time YK8081E PRT time Combination of STATUS and ACTION is invalid : rec#.
Message ID Message text Explanation and recommended actions The message identified by sendmsg appears. The message is specified in SENDMSG with the CONS level designated. YK8100I PRT CON time sendmsg time Message output time This is only displayed when the output destination is SYSTSPRT. The message identified by sendmsg appears. The message is specified in SENDMSG with the ERROR level designated.
Message ID Message text Explanation and recommended actions type, which was specified for the REPORT parameter, is only valid for Continuous Access Asynchronous or Continuous Access Journal copy groups. YK8230E PRT CON time REPORT type is only valid for CAA or CAJ Copy Groups. time Message output time This is only displayed when the output destination is SYSTSPRT. type Report type BCM Monitor could not set the copy group to the specified startup status.
Message ID Message text Explanation and recommended actions The copy group entered the expected status. YK8305I PRT CON time Status ok. time Message output time This is only displayed when the output destination is SYSTSPRT. YK8310I See YK8310I PRT. N/A This message indicates the results of REPORT(SUMMARY).
Message ID Message text Explanation and recommended actions This message indicates the results of REPORT(DETAIL).
Message ID Message text Explanation and recommended actions This message indicates the results of REPORT(RPO).
Message ID Message text Explanation and recommended actions This message indicates the results of REPORT(STATS) for the Continuous Access Asynchronous copy group.
Message ID Message text Explanation and recommended actions This message indicates the results of REPORT(STATS) for the Continuous Access Journal copy group.
Message ID YK8322I PRT CON Message text time Some volumes are in a 'TRANSITION', 'SIMPLEX', 'HOLD' OR ERROR status. Explanation and recommended actions Some volumes are in the TRANSITION, SIMPLEX, HOLD status, or an abnormal status. time Message output time This is only displayed when the output destination is SYSTSPRT. Some volumes are not in the HOLDER status. YK8323I PRT CON time Some volumes are not in a 'HOLDER' status.
Message ID Message text Explanation and recommended actions BCM Monitor will start monitoring the copy group. YK8403I PRT CON time Start monitoring Copy Group. time Message output time This is only displayed when the output destination is SYSTSPRT. BCM Monitor will execute the action identified by action err-action specified in the ACTION parameter for STATUS.
Message ID Message text Explanation and recommended actions This message indicates the values specified in the YKMONOPT file.
Message ID Message text Explanation and recommended actions An error occurred with the license information dataset. YK9051E ISPF An error occurred in the license information dataset Check that the prefix of the license information dataset is registered correctly, and that the license information dataset is created correctly. If necessary, recreate the license information dataset and re-register the license keys in the order in which they were issued.
Message ID Message text Explanation and recommended actions The license (function) will expire in n days. To continue using this product after the expiry date, you need a permanent license. YK9081W CON Your function license will expire in n day(s). If function is Basic: A permanent license for Business Continuity Manager Basic is required. If function is CAJ 4x4 Extended CTG: A permanent license for Business Continuity Manager CAJ 4x4 Extended CTG is required.
Message ID Message text YKA010E TSO MSGID() parameter cannot be specified for this operation YKA096I TSO No message found Explanation and recommended actions If GET or CLOSE is specified in the OP parameter, you cannot specify the MSGID parameter. Specify OPEN in the OP parameter, and then specify the MSGID parameter.
Message ID Message text Explanation and recommended actions The YKP2B command terminated. return-code The return code of the YKP2B command: 0: The command ended successfully. The copy group definition file was output. 4: Indicates that one of the following occurred. - The command ended successfully. No copy pair was detected within the range of the specified device numbers. YKB001I TSO YKP2B completed.
Message ID Message text Explanation and recommended actions An error occurred during execution of the YKP2B command. See the explanation corresponding to the message ID of the error message indicated by message-text and take appropriate action. Also see the additional information indicated by message-value and message-severity and take appropriate action. If the problem is not resolved, contact your HP Technical Support or authorized service provider. command-name Error occurred during execution.
Message ID Message text Explanation and recommended actions A P-VOL not defined in the disk configuration definition file was included among the PPRC copy pairs detected by the YKP2B command. Check whether this P-VOL is defined in the disk configuration definition file. CopyType The copy type of the detected undefined volume YKB202W TSO Unable to resolve primary volume information.
Message ID Message text Explanation and recommended actions YKC001E MSG SC=48 RC=48 No controller ARRAYS() supplied Nothing is assigned to the ARRAYS parameter. YKC001E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter. YKC001E MSG SC=48 RC=48 No results STEM() supplied Nothing is assigned to the STEM parameter. YKC001E MSG SC=48 RC=48 No starting FROM() supplied Nothing is assigned to the FROM parameter.
Message ID YKC032I MSG SC=0 (count) Message text HP storage systems Devices Found Explanation and recommended actions The number of HP storage-system devices scanned by the YKSCAN command. count Number of HP storage-system devices YKC033I MSG SC=4 (count) YKC034E MSG SC=32 RC=32 The specified devices that do not have any available I/O paths were skipped. A dynamic configuration change was detected during YKSCAN command processing.
Message ID Message text Explanation and recommended actions YKD008E MSG SC=48 DEVN() not valid hex The value specified in the DEVN parameter is not in hexadecimal format. Access to the REXX variable identified by name failed. REXX failure return code=nnnn starting with variable name YKD010E TSO RC=40 For details about the return code, see IKJCT441 in the TSO/E Programming Services. nnnn Error code returned upon REXX access The specified copy group attribute value is invalid for this command.
Message ID Message text Explanation and recommended actions Processing is terminating because the timeout limit has expired. YKE001W MSG SC=4 RC=4 Timeout limit has expired, waiting for group copy-group to reach state state. Correct the timeout value or check that the status to be monitored is correctly specified. Use the YKQUERY command to check the status of the copy pairs. If there is a copy pair where a transition has not taken place, the S-VOL of that copy pair might be ONLINE.
Message ID Message text Explanation and recommended actions The YKEWAIT command terminated with the return code nnnn and the reason code rrrr. YKEWAIT command return code=nnnn, reason code=rrrr YKE099I TSO This message is always displayed to indicate the return code and the reason code. nnnn Maximum among the severity codes returned during command execution Table 7 List of messages (message ID YKF0x) Message ID Message text Explanation and recommended actions Invalid parameters are specified.
Message ID Message text Explanation and recommended actions The YKFREEZE command terminated with the return code nnnn and the reason code rrrr. YKF099I TSO YKFREEZE command return code=nnnn, reason code=rrrr This message is always displayed to indicate the return code and the reason code.
Message ID Message text Explanation and recommended actions The system does not recognize the XML element name that exists on the line with the line number identified by rec# in the file identified by file. YKG050W MSG SC=4 RC=4 (file:rec#) Unrecognized element encountered: name Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the HP XP7 for Business Continuity Manager Software Reference Guide.
Message ID Message text Explanation and recommended actions The & character string that exists on the line with the line number identified by rec# in the file identified by file has not been correctly escaped. YKG074E MSG SC=36 RC=36 (file:rec#) Invalid "&" character discovered in quoted string. string See the description of Extensible Markup Language (XML) 1.0 at http://www.w3.org.
Message ID Message text Explanation and recommended actions 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. Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the HP XP7 for Business Continuity Manager Software Reference Guide.
Message ID Message text Explanation and recommended actions An attempt to deallocate the configuration file identified by file failed. YKG091E MSG SC=40 RC=40 (file) dsstate File Deallocation Failed: dsstate. Status of the configuration file file Name of the configuration file in which the error was detected An attempt to read the configuration file identified by file failed. YKG092E MSG SC=40 RC=40 (file) dsstate File Read error: dsstate.
Message ID Message text Explanation and recommended actions The value value of the XML attribute name is in an invalid format. Correct the specification on the line with the line number identified by rec# in the file identified by file. YKG250E MSG SC=36 RC=36 (file:rec#) The value value of the attribute name is an invalid format.
Message ID Message text Explanation and recommended actions The XML element name-1 with the value value specified for the XML attribute name-2 was not found. YKG255E MSG SC=36 RC=36 (file:rec#) The element name-1, for which the value value was specified for the attribute name-2, was not found. Revise the specification on line number rec# in file.
Message ID Message text Explanation and recommended actions The XML element identified by name2 contained the XML element name1 that cannot be specified. Correct the specification on the line with the line number identified by rec# in the file identified by file. YKG276E MSG SC=36 RC=36 (file:rec#) The element name1 is not a content of the element name2.
Message ID Message text Explanation and recommended actions The internal routine encountered a shortage of work space. Contact Technical Support for assistance. YKG295E MSG SC=44 RC=44 (file:rec#) file The element stack was overflowed. Name of the configuration file where the error was detected rec# Number of the line in the file identified by file where the error was detected An unexpected error has occurred. This error might have occurred with another error.
Message ID Message text Explanation and recommended actions No copy pairs were detected within the specified range. YKH002I TSO No copy pair was discovered. Check the operating range and status of the copy pair that you want to acquire, and execute the YKH2B command again. If the copy pair status is SIMPLEX, the YKH2B command will not detect the copy pair.
Message ID YKH201W TSO Message text No I/O paths are available for the specified devices. DEVN=Devn Explanation and recommended actions No copy pair information was acquired from the volume to which the device number Devn was assigned because no I/O paths are available. Verify the I/O path settings.
Message ID Message text This copygroup does not support LinkageOption=HS. SUPFNC=SUPFnc YKH205W TSO Explanation and recommended actions Continuous Access with the HyperSwap attribute cannot be used in this storage system because 2DC configuration with HyperSwap and Continuous Access Journal is not supported. Use a device# in which 2DC configuration with HyperSwap and Continuous Access Journal can be used. Also, if scanning was not performed after the storage system microcode was updated, perform a scan.
Message ID Message text YKJ099I TSO RC=0 cmd command completed. RC= return-code Explanation and recommended actions The command identified by cmd has ended with a return code identified by return-code. cmd Command name YKJ100E TSO RC=32 Error occurred during reading/writing configuration file: file An error occurred while reading data from or writing data to the configuration file.
Message ID Message text Explanation and recommended actions The CSV file operation will stop because an error occurred when using the CSV file. Refer to the information output in the message to review the environment, and then update the CSV file again. For details about troubleshooting, see the accompanying message and the HP XP7 for Business Continuity Manager Software User Guide.
Message ID Message text Explanation and recommended actions The number of items specified on one line of the pair information CSV file is incorrect. YKJ203E TSO RC=32 The number of items specified for a line in Pair information CSV file is invalid: dd-name: rec# 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 No P-VOL is specified in the pair information CSV file.
Message ID Message text Explanation and recommended actions The S-VOL specified with the device number differs from the S-VOL specified with the storage system serial number, control unit number, and command control address number. YKJ208W TSO RC=8 Inconsistencies exist among the values used to specify the secondary volume: dd-name: rec# Although the copy group definition file was created, the settings therein might contain an error.
Message ID Message text Explanation and recommended actions The combination of the copy groups is one of the following: • The serial numbers of the primary site storage systems are the same; the serial numbers of the secondary site storage systems are different; and copy pairs with the same consistency group ID exist.
Message ID Message text Explanation and recommended actions No value is assigned to the item identified by name in the EXCTG information CSV file.
Message ID Message text Explanation and recommended actions The pair information CSV file includes no entry (line) corresponding to the entry (line) specified in the EXCTG information CSV file.
Message ID Message text Explanation and recommended actions An invalid number of items was specified on one line in the CTG information CSV file.
Message ID Message text Explanation and recommended actions User SVC information could not be acquired. service-name Name of the OS service that encountered an error YKK102E TSO RC=32 Failed to get user SVC routine information,service=servicename,code=code1,code2. code1 Return code of the OS service that encountered an error code2 Reason code of the OS service that encountered an error If no reason code is returned for an OS service, code2 is 0. Host ID setting information could not be acquired.
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. If the error still exists, contact HP Technical Support for assistance.
Message ID Message text Explanation and recommended actions An invalid entity reference was found on the line with the line number identified by rec# in the file identified by file. YKL074E MSG SC=36 RC=36 (file:rec#) Use only defined entity references as specified in Extensible Markup Language (XML) 1.0 at http://www.w3.org. Invalid "&" character discovered in quoted string.
Message ID Message text Explanation and recommended actions 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. Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the HP XP7 for Business Continuity Manager Software Reference Guide.
Message ID YKL082W MSG SC=8 RC=8 (pairindex) Message text Unable to resolve secondary device address. Explanation and recommended actions The YKLOAD program failed to resolve the unit number (device address) of the S-VOL in the specified CopyPair. For configuration definition, this process uses the Host Discovered Array object in the secondary device address domain. For other purposes, the current host device address domain is used. The situation represented by this message is not always fatal.
Message ID Message text Explanation and recommended actions An attempt to allocate the configuration file identified by file failed. Verify that the configuration file identified by file is correctly created. YKL090E MSG SC=40 RC=40 (file) File Allocation Failed: dsstate. dsstate Status of the configuration file file Name of the configuration file in which the error was detected An attempt to deallocate the configuration file identified by file failed.
Message ID Message text Explanation and recommended actions The XML attribute identified by attname has already been defined. Review the file name identified by file and the attname value on the line with the line number identified by rec#. attname YKL241W MSG SC=4 RC=4 (file:rec#) The attribute attname is already defined.
Message ID Message text Explanation and recommended actions The value value of the XML attribute name does not match the name in the file name. YKL254E MSG SC=36 RC=36 (file:rec#) Correct the specification on the line with the line number identified by rec# in the file identified by file, or correct the file name. The value value of attribute name is not match with filename.
Message ID Message text Explanation and recommended actions The specified ETag name /incorrect-ETag-name is not the expected ETag name /correct-ETag-name. YKL274E MSG SC=36 RC=36 (file:rec#) ETag name is mismatch. /correctETag-name is expected, but /incorrect-ETag-name is specified. Correct the specification on the line with the line number identified by rec# in the file identified by file.
Message ID Message text Explanation and recommended actions No command device was found that is defined in the route for remote command issuance or with the specified route label. YKL281E MSG SC=36 RC=36 (file:rec#) No command devices are defined for routes that issue remote commands or for route labels. Correct the route definition in the route list definition file identified by file.
Message ID Message text Explanation and recommended actions The license (function) has expired. To continue using this product, you need a permanent license. If function is Basic: YKL292E MSG CON SC=36 RC=36 The expiration date for your license key(function). A permanent license for Business Continuity Manager Basic is required. If function is CAJ 4x4 Extended CTG: A permanent license for Business Continuity Manager CAJ 4x4 Extended CTG is required. The license (function) will expire in n days.
Message ID Message text Explanation and recommended actions The values attribute1 and attribute2 conflict. YKL419E MSG SC=48 RC=48 The values of attribute1 and attribute2 conflict. Make sure that both of these values are valid, and then retry the operation.
Message ID Message text Explanation and recommended actions YKM014E ISPF This Copy Group ID is already defined. Choose a different ID. The copy group ID is already defined. Please use another ID. YKM015I LOG RC:nn CMD:command The command terminated with the return code nnnn after issuing the command identified by command. nn Return code of this command The command output the nn as Severity, message-text as message ID/message text, and message-value as additional information, and then terminated.
Message ID Message text Explanation and recommended actions YKM030E ISPF File not found. The file was not found. YKM031E ISPF Refresh SMS key is not available in case of Copy Group Creation. The Refresh SMS key is not available while a new copy group is being created. YKM032E ISPF Invalid operation. The operation is invalid. YKM033E ISPF Can not edit. This cannot be edited. YKM034E ISPF Press F10 key and select C/T ID. Press the F10 key, and then select a consistency group ID.
Message ID Message text YKM047E ISPF Processing to insert or edit a storage system was denied because the storage system has already been discovered by the selected DADID. Explanation and recommended actions A storage system cannot be inserted into, or edited in a route because the storage system has already been scanned via the specified device address domain ID. Correct the specified device address domain ID and serial number of the storage system.
Message ID Message text YKM500E ISPF You cannot perform a remote scan if the specified DADID matches a local or Non Gen'ed DADID or if the loaded HDA file is not for remote scan or if the Preset RouteListID, which is in the Set Defaults panel, is not enabled. Explanation and recommended actions A Remote Scan cannot be performed in the following cases: • The specified device address domain ID is equivalent to the local device address domain ID or a Non Gen'ed device address domain ID.
Message ID Message text Explanation and recommended actions YKM514E ISPF CCA could not be assigned because either the path is already defined in another logical path, or the list of CCA could not be retrieved. A command control address could not be assigned because the path is already defined in another logical path, or because a list of command control addresses could not be obtained.
Message ID Message text Explanation and recommended actions YKM527E ISPF You cannot specify the license information dataset. The license information dataset cannot be specified. YKM528E ISPF Enter the value that you wish to find with the LOCATE command on a sorted field "field-name". YKM529E ISPF You cannot specified except '00' as PathID with this interface version. Enter the value that you want to find in the sorted field field-name by using the LOCATE command.
Message ID Message text Explanation and recommended actions Specify correct values for the pattern parameter. Make sure that none of the following conditions exist: • A value greater than value 1 was specified for value 2, as the range specification condition. YKM722E ISPF Invalid pattern is specified. • NULL was specified for value 1, as the range specification condition. • A value containing an asterisk (*) was specified for value 1 or value 2, as the range specification condition.
Message ID Message text Explanation and recommended actions YKM754E ISPF Route List ID must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Route List ID must be 1-8. The route list ID must be a combination of one or more qualifiers.
Message ID Message text Explanation and recommended actions YKM765I ISPF A description for the specified error code was not found. For details about error codes, see XXX. If the error code is not listed in the manual, contact your HP Technical Support or authorized service provider. YKM766E ISPF Specified Prefix is being used by another program. The specified prefix is being used by another program. YKM767E ISPF This command is invalid for Continuous Access Copy Groups linkaged with HyperSwap.
Message ID Message text Explanation and recommended actions YKM776E ISPF Route Label must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Route Label must be 1-8. The route label must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must start with an alphabetic character (A-Z, a-z).
Message ID Message text Explanation and recommended actions YKM906E TSO A FREEMAIN error occurred. A FREEMAIN error occurred. However, the program will continue to run. Contact Technical Support for assistance. Table 16 List of messages (message ID YKN0x) Message ID Message text Explanation and recommended actions Invalid parameters are specified. For details, see the reason code in the YKN099I message that will appear after this message.
Message ID Message text Explanation and recommended actions The YKRUN command terminated with the return code nnnn and the reason code rrrr. YKRUN command return code=nnnn, reason code=rrrr YKN099I TSO This message is always displayed to indicate the return code and the reason code. nnnn Maximum among the severity codes returned during command execution Table 17 List of messages (message ID YKP0x) Message ID Message text Explanation and recommended actions Invalid parameters are specified.
Message ID Message text YKP065E MSG SC=36 RC=36 The storage system serial number pairs with more than 4 storage systems. Explanation and recommended actions The storage system identified by serial-number is paired with more than four storage systems within the consistency group group. Correct the copy pair configuration within the consistency group group. serial-number Storage system serial number (12 digits) The YKSTATS command terminated with the return code nnnn and the reason code rrrr.
Message ID Message text Explanation and recommended actions In a Business Copy copy group, the volume in the target copy pair has already been paired with three volumes other than the pairing volume specified in the copy group definition. Review the applicable copy pair definition in the copy group definition. device# Device number If the device cannot be identified, **** is displayed. SN Storage system serial number YKQ018E MSG SC=16 RC=16 (pair-index) BC PAIR deficiency.
Message ID Message text Explanation and recommended actions Check that the S-VOL status is SIMPLEX. device# Device number If the device cannot be identified, **** is displayed. SN Storage system serial number YKQ021E MSG SC=12 RC=20 (pair-index) CAA or BC Primary is simplex, secondary not. DEVN device#(SN,CU#,CCA#) If the device cannot be identified, ************ is displayed. CU# Control unit number If the device cannot be identified, ** is displayed.
Message ID Message text Explanation and recommended actions The YKQUERY command terminated with the return code nnnn and the reason code rrrr. YKQUERY command return code=nnnn, reason code=rrrr YKQ099I TSO This message is always displayed to indicate the return code and the reason code.
Message ID Message text YKR058E MSG SC=36 RC=48 Some pairs in this group do not support CAA services. Explanation and recommended actions One or more devices in the 7700E storage system does not support Continuous Access Asynchronous copy groups. Check whether the command can be executed on this copy group, and then re-execute the command. The YKRESYNC command terminated with the return code nnnn and the reason code rrrr.
Message ID Message text Explanation and recommended actions YKS085E MSG SC=44 RC=44 Error reported during file output. EXECIO RC =n Because the EXECIO TSO/E REXX command failed (return code = n), the YKSTORE command is unavailable for creating or updating the configuration file. For details, see the TSO/E REXX User's Guide. The input configuration file identified by file is unavailable.
Message ID Message text Explanation and recommended actions YKSTORE command processing has completed. YKS099I MSG TSO SC=max-severity RC=max-value This message is always displayed. YKSTORE Processing Complete.
Message ID Message text Explanation and recommended actions Creation of the configuration file is stopped because an error occurred during the creation of the configuration file. Refer to the information output in the message to review the environment, and then create the configuration file again. For details about what action to take, see the message that was output and the HP XP7 for Business Continuity Manager Software User Guide.
Message ID Message text Explanation and recommended actions dsstate 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 with the format VSAM cannot be used as a configuration file. Change the dataset format of the configuration file into PS.
Message ID Message text 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. If no other error message was output, collect the following materials and contact your HP Technical Support or authorized service provider: YKS298E MSG SC=44 RC=44 (detailed-info) YKSTORE encountered an unexpected error.
Message ID Message text YKT008E CON RC=20 System task started without START from TSO. YKT012E CON RC=16 Name/token error YKT021E CON RC=20 Invalid parameter YKT022E CON RC=4 SVC routine is already inserted YKT023E CON RC=16 Couldn't delete SVC routine YKT024E CON Couldn't copy load module Explanation and recommended actions The YKALCSVC command was executed in the TSO/E environment. Execute the YKALCSVC command using the START command or a batch job.
Message ID Message text Explanation and recommended actions YKT212E CON RC=12 Couldn't register Name/Token An error occurred during Name/Token registration. The program stops processing. YKT213E CON RC=4 Couldn't take Name/Token Contact HP Technical Support for assistance. An error occurred during acquisition of Name/Token. The program stops processing. Contact HP Technical Support for assistance.
Message ID Message text Explanation and recommended actions YKT299I CON SC=0 command command return code=nnnn. The command identified by command terminated with the return code nnnn. Table 24 List of messages (message ID YKT4x) Message ID Message text YKT400I CON BC Manager environment variables (version) Explanation and recommended actions This message displays the Business Continuity Manager environment variables.
Message ID Message text Explanation and recommended actions YKT403I CON HP XP7 for Business Continuity Manager Software This message displays the program product name. Table 25 List of messages (message ID YKU0x) Message ID Message text Explanation and recommended actions Invalid parameters are specified. For details, see the reason code in the YKU099I message that will appear after this message. For reason codes, see IKJPARS in the TSO/E Programming Services.
Message ID Message text Explanation and recommended actions YKU008E MSG SC=48 GENID() not valid hex The value specified in the GENID parameter is not in hexadecimal format. YKU009E MSG SC=48 Specify ATTIME() and DEVN() parm exclusively You cannot specify the ATTIME parameter and the DEVN parameter at the same time. YKU009E MSG SC=48 Specify ATTIME() and VOLUNIT parm exclusively You cannot specify the ATTIME parameter and the VOLUNIT parameter at the same time.
Message ID Message text Explanation and recommended actions The YKSUSPND command terminated with the return code nnnn and the reason code rrrr. YKSUSPND command return code=nnnn, reason code=rrrr YKU099I TSO This message is always displayed to indicate the return code and the reason code. nnnn Maximum among the severity codes returned during command execution Table 26 List of messages (message ID YKV0x) Message ID Message text Explanation and recommended actions Invalid parameters are specified.
Message ID Message text YKV058E MSG SC=36 RC=48 Some pairs in this group do not support CAA services. Explanation and recommended actions One or more devices in the 7700E storage system does not support Continuous Access Asynchronous copy groups. Check that the command can be executed on this copy group, and then re-execute the command. The YKRECVER command terminated with the return code nnnn and the reason code rrrr.
Message ID Message text Explanation and recommended actions The YKWATCH command uses the YKCONMSG command to monitor the console message traffic of IEA494I copy status messages. An error occurred during execution of the YKCONMSG command. YKW008E TSO YKCONMSG error return code = nnnn nnnn Return code of the YKCONMSG command For details, see the description for the YKCONMSG command in the HP XP7 for Business Continuity Manager Software Reference Guide. YKW009W TSO Terminated due to Operator attention.
Message ID Message text Explanation and recommended actions Access to the REXX variable identified by name failed. YKX010E TSO RC=40 REXX failure return code=nnnn starting with variable name For details about the return code, see IKJCT441 in the TSO/E Programming Services. nnnn Error code returned upon REXX access The command device definition for the storage system identified by serial-number failed. YKX065W MSG SC=4 RC=0 Storage system serial-number Command Device Definition Failed.
Message ID Message text Explanation and recommended actions YKX101E MSG SC=48 No serial# SN() supplied Nothing is assigned to the SN parameter. YKX102E TSO RC=48 Messages MSG(stem) does not include trailing "." The last character of the MSG parameter is not a period. stem Stem name assigned to the MSG parameter The specified parameter combination is invalid.
Message ID Message text Explanation and recommended actions YKX201E MSG SC=48 No device# DEVN() supplied Nothing is assigned to the DEVN parameter. YKX201E TSO RC=48 No message MSG() supplied Nothing is assigned to the MSG parameter. YKX201E MSG SC=48 No model SMODEL() supplied Nothing is assigned to the SMODEL parameter. YKX201E MSG SC=48 No results STEM() supplied Nothing is assigned to the STEM parameter. YKX201E MSG SC=48 No serial# SN() supplied Nothing is assigned to the SN parameter.
Message ID Message text Explanation and recommended actions YKX299I TSO YKQRYDEV command return code=nnnn, reason code=rrrr The YKQRYDEV command terminated with the return code nnnn and the reason code rrrr. Table 31 List of messages (message ID YKY0x) Message ID Message text Explanation and recommended actions The Business Continuity Manager agent has started. v Version number YKY001I CON AGENT STARTED (v.r.
Message ID YKY016I CON Message text TASK(task-ID) ABENDED,CODE=completioncode Explanation and recommended actions A task terminated abnormally during the Business Continuity Manager agent start up. The Business Continuity Manager agent will be terminated.
Message ID Message text Explanation and recommended actions 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. YKY102I CON INVALID error-type: text error-type • COMMAND: Indicates that an error was detected in the command. • OPERAND: Indicates that an error was detected in the operand.
Message ID Message text Explanation and recommended actions This message displays the last transmission or reception time in the corresponding TCP/IP session. data-direction-type YKY133I CON LAST data-direction-type TIME=YYYY/MM/DD hh:mm:ss The direction of the data that was sent at the time displayed in YYYY/MM/DD hh:mm:ss • SEND: Indicates that the data was sent. • RECV: Indicates that the data was received.
Message ID Message text Explanation and recommended actions The TCP connection was lost during TCP/IP processing for the reason shown as reason-for-disconnection. Determine the cause of disconnection from the remote host. task-ID YKY305I CON task-ID,TCP CONNECTION LOST DURING EVENT PROCESSING,TCPSTATUS=(reason-for-disconnection) Number used to identify the processing task that output the message reason-for-disconnection • FIN ACCEPT: A disconnection request (TCP-FIN) from the remote host was received.
Message ID Message text Explanation and recommended actions A communication error was detected. The message displays the request name, the target IP address:target port number (decimal number), and the local IP address:local port number (decimal number). The currently executing process is canceled. If necessary, check the YKY330I message that was displayed immediately before this message to determine the cause of the error.
Message ID Message text Explanation and recommended actions The request shown as request-type resulted in an error on the socket interface for IBM® TCP/IP for MVS®. return-code and error-number indicate the error information. Check the cause of the error and take appropriate action. If TCP/IP has stopped due to the error, stop the Business Continuity Manager agent. Once the error is corrected, start the TCP/IP program, and then start the Business Continuity Manager agent.
Message ID Message text Explanation and recommended actions An error occurred in the disk configuration definition file. See the error-type, and then remove the error. After that, retry the operation from Replication Manager. error-type • ALLOCATE: An allocation error Make sure that the file indicated by file exists. YKY501E XML Disk configuration definition errortype error. file • EXECIO: An input error Make sure that the file indicated by file has not been broken.
Message ID Message text Explanation and recommended actions An error occurred in the route list definition file. See the error-type, and then remove the error. After that, retry the operation from Replication Manager. error-type • ALLOCATE: An allocation error YKY507E XML Routelist configuration file error error-type. file Make sure that the file indicated by file exists. • EXECIO: An input error Make sure that the file indicated by file has not been broken.
Message ID Message text Explanation and recommended actions The IRXINIT routine returned an error with the return code shown as return-code. The Business Continuity Manager agent will terminate the processing. Check the return code. return-code • 20: Processing failed due to an error. Check the reason code that was returned to PARM7 by IRXINIT.
Message ID Message text Explanation and recommended actions A command that was issued by the Business Continuity Manager agent ended with return-code. Messages for detected errors are output to text. If the number of characters in the message output by the command exceeds 126, it will be displayed on multiple lines. The maximum number of message lines for a single command is 10.
Message ID Message text Explanation and recommended actions The main task or subtask terminated abnormally during the Business Continuity Manager agent processing. If the task cannot be recovered, the Business Continuity Manager agent will be terminated. Contact the center administrator. AGENT FUNCTION ABEND CODE=Sxxx Uxxxx DATE=yy-mm-dd TIME=hh:mm:nn ABENDED-MODULE=module-name C-DATE=module-creation-date BASE=bbbbbbbb DISP=dddd [CALLING-MODULE=module-name C-DATE=y'y'.m'm'.
Message ID Message text Explanation and recommended actions YKY705E XML End of request was detected in an element. The end of the XML request was detected in an element. YKY706E XML The number of elements exceeded the allowed limit. Check, and, if necessary, revise the last element in the XML request. The number of element hierarchies exceeded the permitted maximum value (16). Check, and, if necessary, revise the request. The API version of the XML request is not supported.
Message ID Message text Explanation and recommended actions A required parameter is missing in the element. YKY718E XML A required parameter is missing from the element 'element-name' of the request. 'parameter-name' Check, and, if necessary, revise the corresponding element specification in the request. element-name Element name parameter-name Name of the required parameter YKY719E XML There is a conflict with element 'element-name'.
Message ID Message text YKY728E XML The information in configuration file was updated after you obtained it. Explanation and recommended actions The information in the configuration file has been updated since it was last obtained. Refresh the configuration file from Replication Manager, and then retry the operation. The contents of the configuration file are invalid. Configuration file is invalid.
Message ID Message text Explanation and recommended actions The value of the REXX variable with the name identified by name is invalid. Correct the value and then re-execute the command. YKZ050E MSG SC=36 RC=36# (attribute-value) name Invalid attribute name REXX variable name attribute-value REXX variable value # If this message is output while the YKLOAD command is being executed, the RC is 44. The route list to be processed cannot be found.
Message ID Message text Explanation and recommended actions The command cannot be executed because a GETMAIN error occurred. Expand the job execution area, and then re-execute the command. nnn (decimal number) Return code from the GETMAIN macro mmm (decimal number) Area size area (string) HIGH must be equal to or greater than 16 MB; LOW must be less than 16 MB.
Message ID Message text Explanation and recommended actions Logical contradiction occurred. nnn (decimal number) Reason code (maintenance information) xxx (decimal number) YKZ202E MSG TSO CON SC=52 RC=0 A Logical error occurred. (reason code=nnn, cmd=xxx, pos=yyy) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
Message ID Message text Explanation and recommended actions The command cannot be executed because an REXX write error occurred. • If the nnn value is 32: Expand the job execution area, and then re-execute the command. • If the nnn value is 40: Check that the REXX program is running in the TSO/E environment, and then re-execute the command. • If the nnn value is not 32 or 40: Correct the configuration file (XML) and the values assigned to the parameters.
Message ID Message text Explanation and recommended actions The command cannot be executed because an I/O error occurred. message-text (string) Message text xxx (decimal number) YKZ206E TSO RC=0 An I/O error occurred. (detail=message-text, cmd=xxx, pos=yyy) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message.
Message ID Message text Explanation and recommended actions Core processing is starting. process (string) Processing name yyyy/mm/dd (string) GMT date hh:mm:ss.th (string) YKZ208I TSO CON PRT RC=0 The Core processing( process ) started. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) GMT time 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.
Message ID Message text Explanation and recommended actions Core processing is terminating. process (string) Processing name yyyy/mm/dd (string) GMT date hh:mm:ss.th (string) YKZ209I TSO CON PRT RC=0 The Core processing( process ) ended. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) GMT time 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.
Message ID Message text Explanation and recommended actions The command cannot be executed because a NAME/TOKEN write error occurred. nnn (decimal number) Return code set by the NAME/TOKEN registration routine (IEANTCR) name (string) Name registered in the Name/Token service YKZ211E MSG CON SC=40 RC=44# A NAME/TOKEN write error occurred.
Message ID Message text Explanation and recommended actions The trace table is not initialized. xxx (decimal number) YKZ216E TSO RC=0 The Trace table is not initialized. (cmd=xxx, pos=yyy) 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 A system logger service error occurred. Without outputting the event log, processing for the CLI command continues.
Message ID Message text Explanation and recommended actions A LOAD macro error occurred. nnn (decimal number) Return code from the LOAD macro mmm (decimal number) Reason code from the LOAD macro (maintenance information) YKZ219W CON RC=0 A LOAD error occurred.
Message ID Message text Explanation and recommended actions The number of routes related to dad-id is invalid. YKZ220T MSG SC=36 RC=44 Number of Route dad-id is invalid. Check whether the device address domain ID specified in the YKLOAD command is invalid or correct the configuration file, and then re-execute the YKLOAD command. dad-id Device address domain ID The device number of the volume is invalid.
Message ID Message text Explanation and recommended actions For the specified model, TRK cannot be specified for TCA_MAP in the Continuous Access Asynchronous options. Correct the contents of the configuration file. YKZ226E MSG SC=36 RC=48# stemTCA_MAP=TRK not supported by some group pairs stem Stem name # If this message is output while the YKLOAD command is being executed, the RC is 44. Some copy pairs in this group do not support TCA_FLOWCONTROL=N.
Message ID Message text Explanation and recommended actions Processing for the volume was skipped because the status of the volume did not allow this command to be executed. If 0 is displayed in the location that indicates the copy pair corresponding to the pair-index, multiple volumes within the copy group have been skipped. Change the status of the copy pairs to a status that allows this command to be executed. device# Device number If the device cannot be identified, **** is displayed.
Message ID Message text Explanation and recommended actions No APID value is registered. Correct the content of the configuration file. YKZ235E MSG SC=36 RC=36# dad-id APID is null. dad-id Device address domain ID # If this message is output while the YKLOAD command is being executed, the RC is 44. No interface number is registered. Correct the content of the configuration file. YKZ236E MSG SC=36 RC=36# dad-id Interface number is null.
Message ID Message text YKZ243E MSG SC=48 RC=48 Supplied parameters invalid YKZ244E MSG SC=36 RC=36 Serial number of storage system is not found in Routelist. Explanation and recommended actions ATTIME or CANCEL is specified together with SVOL. YKZ245E MSG SC=48 RC=48 CopyGroup attribute combination is invalid. YKZ246E MSG SC=48 RC=48 This operation (operation) does not support remote command. Correct the YKSUSPND command parameter values, and then re-execute the command.
Message ID Message text Explanation and recommended actions The DAD or ROUTE parameter specified on the YKLOAD command is invalid. YKZ249E MSG SC=48 RC=48# (pair-index) Correct the specification. Specified DAD or ROUTE is invalid. pair-index See the pair index description in the explanation of the YKE003E message. # If this message is output while the YKLOAD command is being executed, the RC is 44.
Message ID Message text Explanation and recommended actions Business Continuity Manager failed to complete the requested processing. Processing will continue with this device skipped. Check the status of the error device, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and recommended actions Business Continuity Manager failed to complete the requested processing. This device is skipped and processing continues. Check the status of the error device, and fix the problem in the configuration or execution condition if any.
Message ID Message text Explanation and recommended actions An I/O error occurred. Processing will continue with this device skipped. If a sense byte is set, the sense byte is indicated in the YKZ255E message. When CC=3: The corresponding device might not be configured or connected. When CC=0 and CSW=xxxxxx0000xxxx (DSB=00, CSB=00) where x indicates a value: The corresponding device might not be configured or connected.
Message ID Message text Explanation and recommended actions An I/O error occurred. Business Continuity Manager might not support this device. Processing will continue with this device skipped. If a sense byte is set, the sense byte is indicated in the YKZ256E message. When CC=3: The corresponding device might not be configured or connected. When CC=0 and CSW=xxxxxx0000xxxx (DSB=00, CSB=00): The corresponding device might not be configured or connected.
Message ID Message text Explanation and recommended actions Detailed information on the I/O error is displayed. 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.
Message ID Message text Explanation and recommended actions Business Continuity Manager failed to complete the requested processing. Processing will continue with this device skipped. Check the status of the device involving the error, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and recommended actions Business Continuity Manager failed to complete the requested processing. Business Continuity Manager might not support this device. Processing will continue with this device skipped. Check the status of the device involving the error, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and recommended actions An open error occurred in YKLOG01 or YKLOG02. YKLOGnn YKLOG01 or YKLOG02 nnn (decimal number) Return code from the OPEN macro YKZ262E MSG CON SC=0 RC=0 A YKLOGnn open error occurred. (rc=nnn, cp=xxx:yyy) xxx (decimal number) Command code of the command that was executed when the error occurred See the command code description in the explanation of the YKZ201E message.
Message ID Message text Explanation and recommended actions A parameter was entered from SYSIN. YKZ266I PRT RC=0 Parameters were input. ( nnn, xxx ) nnn (decimal number) Number of lines xxx (character string) Input parameter An error occurred in the DEVTYPE macro for YKLOG01 or YKLOG02. YKLOGnn YKLOG01 or YKLOG02 nnn (decimal number) Return code from the DEVTYPE macro YKZ267E MSG CON SC=0 RC=0 A YKLOGnn DEVTYPE macro error occurred.
Message ID Message text Explanation and recommended actions The format of the dataset is invalid. ddd dd name KKK If DSORG is abnormal: DSORG If RECFM is abnormal: RECFM If LRECL is abnormal: LRECL If BLKSIZE is abnormal: BLKSIZE YKZ268E MSG CON PRT SC=0 RC=0 Incorrect dataset format.
Message ID Message text Explanation and recommended actions The group definition does not match the actual pair configuration. If GROUPID is displayed for unmatched items or * is displayed on the device number, storage system serial number, control unit number, or CCA number, there is a copy pair which is not defined in the copy group definition parameter, and which belongs to the same consistency group in the same control unit as the P-VOL or S-VOL.
Message ID Message text Explanation and recommended actions In the logical path definition for REVERSE index1, the index2 and index3 port numbers are duplicated. YKZ274E MSG SC=36 RC=36 (index1, index2, index3) Delete one of the definitions or make sure that the duplicated port numbers are correct, and then re-execute the command. index1 Duplicate ports exist in REVERSE.
Message ID YKZ280W MSG SC=0 RC=0 Message text Secondary volume's IFType is larger than Remote control's IFType value. Explanation and recommended actions The IFType of a storage system using the Remote DKC Control Function is smaller than the IFType of the S-VOL defined in the copy group. As such, the smaller of the two will be used when each command is executed. Note that on some machine types, some functionality might be lost.
Message ID Message text Explanation and recommended actions subCTGroupID in the copy group structure is either NULL or invalid. Correct the configuration file, and then execute the YKLOAD command. YKZ283T MSG SC=36 RC=36# subCTGroupID value null or invalid. value REXX variable value # If this message is output while the YKLOAD command is being executed, the RC is 44. UR_MirrorID in the copy group structure is either NULL or invalid. Correct the configuration file, and then execute the YKLOAD command.
Message ID Message text Explanation and recommended actions A path-controlled storage system does not support path group IDs (path IDs for which values other than 00 are specified). Revise the definition YKZ288E MSG SC=36 RC=36 Some of the storage systems do not support Path Group ID. associated with whether the storage system can use path group IDs#. Also, if a scan was not performed after the storage system microcode was changed, perform a scan.
Message ID Message text YKZ294E MSG CON SC=0 RC=0 An error occurred while acquiring the system symbol &YKLOGPT. (rc=rr) Explanation and recommended actions An error occurred while acquiring the &YKLOGPT system symbol. The program continues processing while assuming LOGR. Revise the value specified for the &YKLOGPT system symbol. rr The return code of the ASASYMBM macro YKZ295E MSG SC=36 RC=36 The version of this configuration file is not supported.
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 consistency group ID or sub consistency group ID YKZ296E MSG SC=44 RC=44 m (decimal number) Mirror ID (0-3) e (decimal number) EXCTG ID (0-3) ssssssssssss (decimal number) Storag
Message ID Message text Explanation and recommended actions Processing is terminating because the timeout limit has expired while waiting for the EXCTG registration with the YKEWAIT command. YKZ298W MSG SC=4 RC=4 Timeout limit has expired while waiting for EXCTG registration process. Correct the timeout value or check that the status to be monitored is correctly specified. Also, check if the journal group is registered to EXCTG.
Message ID Message text Explanation and recommended actions EXCTG information defined in the copy group and EXCTG information registered in the storage system do not match. Correct the copy group definition file. This message might be output when the EXCTG ID specified in the copy group definition is being used by another copy group. After removing the cause of the problem, execute the YKMAKE command again with a SELECT(COND) specification to register the journal group to EXCTG.
Message ID Message text Explanation and recommended actions The user SVC is not registered, or the &YKSVCNO system symbol of the IEASYMxx parmlib member is specified incorrectly. When the user SVC is defined in SVCPARM: YKZ300E MSG TSO SC=44 RC=44 SVC # is null or invalid. Make sure that the &YKSVCNO system symbol of the IEASYMxx parmlib member is specified correctly. When the user SVC is not defined in SVCPARM: Register the user SVC by YKALCSVC command.
Message ID Message text Explanation and recommended actions This log data indicates that a CLI command has been issued. hh:mm:ss Time the CLI command was issued (local time) YKZ310I SYS hh:mm:ss command command Issued CLI command name and its parameters A maximum of 109 characters can be output. If 109 is exceeded, the remainder are discarded.
Message ID Message text Explanation and recommended actions An abnormal system termination was detected during the REXX service processing. command Issued CLI command name rexx-service YKZ332E TSO RC=64 command detected the system abend during rexx-service processing. (code=sss, reason=rrrr) Name of the REXX service where the abnormal system termination was detected sss (hexadecimal number) System completion code For details, see the MVS System Codes.
Message ID Message text Explanation and recommended actions A dynamic change in an I/O configuration definition was detected during processing of the command. YKZ370E MSG SC=32 RC=32 A dynamic configuration change was detected during specified command processing. DEVN device# Check the status of the device targeted by the command, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and recommended actions The copy pair entered an unexpected status while registering the journal group to EXCTG. Check that the status to be monitored is correctly specified. If the status is correctly specified, execute the YKQUERY command to determine the cause of the problem and rectify the error. jj (hexadecimal number) Unexpected transition occurred while adding JNLG to EXCTG.
Message ID Message text Explanation and recommended actions EXCTG cannot be used on a storage system that has a P-VOL or uses the Remote DKC Control Function. Use a device#2 that supports EXCTG. Also, if a scan has not been performed after the storage system microcode was replaced, perform another scan. YKZ406E MSG SC=36 RC=36#1 IFType Primary device IFType does not support EXCTG. IFType value #1 If this message is output while the YKLOAD command is being executed, the RC is 44.
Message ID Message text Explanation and recommended actions An error occurred while the suspend processing using the CAJ ATTIME Suspend Function was being performed. Check the error information, and remove the cause of the error. If necessary, also check information such as the storage system log. After that, use the YKSUSPND command to cancel the ATTIME suspend time, and then acquire a backup again.
Message ID Message text Explanation and recommended actions eeee (hexadecimal number) Error information on suspend processing 0001: Suspension is not possible because the Business Copy copy pair status is invalid. 0002: Suspension is not possible because an error occurred due to a problem in storage system. YKZ407E MSG SC=24 RC=24 ATTIME-suspend-time (GMT) ATTIME suspend time: YYYYMMDD-HH:MM:SS.NNNNNN YYYY: Year MM: Month DD: Day HH: Hour MM: Minute SS.
Message ID Message text Explanation and recommended actions The status of the Continuous Access Journal copy pair was invalid while the suspend processing using the CAJ ATTIME Suspend Function was being performed. Check the status of the Continuous Access Journal copy pair, and remove the problem. After that, use the YKSUSPND command to cancel the ATTIME suspend time, and then acquire the backup again.
Message ID Message text Explanation and recommended actions eeee (hexadecimal number) Error information on the suspend processing 0000: The suspend processing has not been started or is being executed. Alternatively, the suspend processing has ended normally. For details, see the Business Copy status. 0001: Suspension is not possible because the Business Copy copy pair status is invalid.
Message ID Message text Explanation and recommended actions The suspend processing started when the timeout period elapsed because this period elapsed before the journal of the ATTIME suspend times for the ATTIME suspend function was acquired, or the suspend processing started at the ATTIME suspend time because the Continuous Access Journal copy pair was in the suspend status at the ATTIME suspend time.
Message ID Message text Explanation and recommended actions You cannot use the Errorlevel attribute for this storage system. In this case, use a device#2 that supports the Errorlevel attribute for Continuous Access Journal. Also, if a scan was not performed after the storage system microcode was replaced, perform another scan.
Message ID Message text Explanation and recommended actions The timestamp transfer mode cannot be used with this storage system. Use a device#2 that supports the timestamp transfer mode. Also, if scanning was not performed after the storage system microcode was replaced, perform another scan. SUPFnc (hexadecimal number) Value for the version of the storage system support function used in the copy group #1 YKZ413E MSG SC=36 RC=36#1 Copygroup SUPFnc does not support the timestamp transfer mode.
Message ID Message text Explanation and recommended actions The function indicated by parameter-name cannot be used. Use a device#2 that supports the parameter-name function or configuration. Also, if scanning was not performed after the storage system microcode was replaced, perform another scan.
Message ID Message text Explanation and recommended actions The device defined in the disk configuration definition file exists on a storage system that differs from the storage system in the disk configuration definition file. For this reason, an NG Scan cannot be executed. YKZ415E MSG SC=48 RC=48 The device indicated by devn in the disk configuration definition file is on a storage system that differs from sn.
Message ID YKZ420E MSG SC=48 RC=48 YKZ421E MSG SC=48 RC=48 Message text Explanation and recommended actions EXCTG information could not be acquired because no EXCTG ID is specified for copying in the forward direction. EXCTG information could not be acquired because no EXCTG ID for copying in the forward direction is specified.
The results of REPORT(SUMMARY) are displayed.
: Copy pair matching percentage : Consistency group ID or master journal group ID : Restore journal group ID : Consistency delta value for each consistency group : Consistency time for each consistency group YK8314I PRT REPORT RPO: COPY GROUP : C/T SUB PRI- SECID C/T SN SN [ C/T DELTA C/T TIME ] The results of REPORT(RPO) are displayed.
: Consistency group ID : Serial number of the primary storage system : Serial number of the secondary storage system : Sidefile threshold value : Primary reserve sidefile cache-usage rate : Primary reserve sidefile consistency cache-usage rate : Primary write pending rate : Secondary reserve sidefile cache-usage rate : Secondary reserve sidefile consistency cache-usage rate : Secondary write pending rate : Data transfer rate (Kbps) between the main control unit and the remot
: Restore journal volume metadata usage rate : Restore journal volume data usage rate : Master journal volume data capacity (GB) : Restore journal volume data capacity (GB) YK8411I PRT SYSTEM OPTIONS: CYCLE TIME WAITFOR TIMEOUT MSGLEVEL ONACTIONERROR STOP AT STOPPOINT SLEEP AT STOPPOINT : : : : : : , The values specified in the YKMONOPT file are displayed.
: Route list ID : Route label : Copy group monitoring status (ACTIVE or INACTIVE) : Copy group startup status to be checked for starting BCM Monitor : 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 paramete
Completion codes Explanation The user does not have the permission to execute CLI commands. The user might not have been given permissions to view the profile required for executing the CLI command, or an RACF error occurred.
Messages
2 Storage system sense byte information This chapter describes storage system sense byte information (error codes) contained in messages. 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.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N Y N N N N N N N Y N N N N N N N A BC copy pair cannot be made. The reason might be one of the following: 2061 • The S-VOL has already been made into a copy pair by using CAJ. • The S-VOL is a journal volume.
Type of error Error code Error details 20BD BC CA CAA CAJ CMD PATH SMART Other A copy pair could not be created because the PVOL of the specified BC copy pair is an emulation type (3390-V) that is not supported. Y N N N N N N N 20BE A copy pair could not be created because the SVOL of the specified BC copy pair is an emulation type (3390-V) that is not supported. Y N N N N N N N 20C5 A BC copy-pair operation cannot be performed because power-off processing is in progress.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N A copy pair with a C/T group ID could not be created because the P-VOL of the specified BC copy pair meets both of the following conditions: 20E4 • The P-VOL is the S-VOL of a CAJ copy pair. • The P-VOL is being used by another program product as the 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 FlashCopy.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N A BC copy pair status cannot be changed because the status of the copy pair does not allow a status transition. The reason may be one of the following: • The combination of the request command and the status of the specified copy pair do not allow the status transition. For information on combinations, see the Business Copy for Mainframe Systems User Guide.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N A BC copy pair cannot be made. The reason might be one of the following: 2331 • 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 transitioned because the maximum multiplicity of the copy pairs for the P-VOL was exceeded.
Type of error Error code Error details 2347 BC CA CAA CAJ CMD PATH SMART Other A BC copy pair status cannot be changed because the volume specified to be the S-VOL is already the S-VOL of a CA or CAA copy pair. Y N N N N N N N 234A A BC copy pair status cannot be changed because the volume specified to be the S-VOL is already the P-VOL of a BC copy pair or the one for FlashCopy.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N A BC copy pair cannot be resynchronized (QuickRestore) because all of the following conditions exist: 237B • The specified P-VOL is an internal volume. • The specified S-VOL is an external volume. • The specified P-VOL has a shared configuration with the P-VOL of the CA. 2381 A BC copy pair cannot be made because the volume specified to be the S-VOL is a system residence volume.
Type of error Error code Error details 239D 239E BC CA CAA CAJ CMD PATH SMART Other The command cannot be executed because the specified P-VOL is protected by the LDEV guard. Y N N N N N N N The command cannot be executed because the specified S-VOL is protected by the LDEV guard. Y N N N N N N N Y N N N N N N N The command could not be executed. The reason might be one of the following: • The specified volume is inconsistent with the volume that received the command.
Type of error Error code Error details 23FF A BC copy pair status cannot be changed because the specified BC copy pair status does not allow the status to be changed. BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N Table 50 Details of error codes 36xx Type of error Error code Error details 3613 Registration to EXCTG has failed because the specified arbitration command device is not an arbitration command device.
Type of error Error code Error details 3682 BC CA CAA CAJ CMD PATH SMART Other Registration to EXCTG has failed because the attribute of the journal group to be registered is different from the attribute of the EXCTG. N N N Y N N N N 3685 Registration to EXCTG has failed because the specified storage system model name is invalid. N N N Y N N N N 3686 Registration to EXCTG has failed because the journal group to be registered is already registered to another EXCTG.
Type of error Error code Error details 3705 3706 BC CA CAA CAJ CMD PATH SMART Other The command for delta resync cannot be executed because the device on the S-VOL does not support delta resync. N N N Y N N N N A delta resync pair cannot be made because the command target volume is the S-VOL of a CA copy pair and the copy pair status is not Duplex.
Type of error Error code Error details 3728 BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be made because an unsupported volume was specified when making a copy pair between different models. N N N Y N N N N 3729 A CAJ copy pair that is to be linked with CA cannot be made because the Disaster Recovery Extended program product has not been installed in the MCU.
Type of error Error code Error details 3753 A CAJ copy pair cannot be created with the HOLD parameter in a 3DC (CAJxCAJ) configuration because the delta resync function is not supported. BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N N N N Y N N N N N N N Y N N N N A CAJ copy pair cannot be resynchronized. Possible reasons include both of the following: 3755 • The specified S-VOL is already in use as an S-VOL in a CAJ copy pair that has another mirror ID.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N A CAJ copy pair cannot be dissolved. Possible reasons include one or both of the following: 4603 • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system. • The SSID for the S-VOL in the parameter does not match the SSID of the local storage system. 4606 The CAJ copy pair status could not be acquired because the specified CU number is unsupported.
Type of error Error code Error details 4617 BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be suspended, resynchronized or dissolved because the specified volume is not a CAJ copy pair. N N N Y N N N N 4618 A CAJ copy pair cannot be suspended because it was a suspend request with Volume and Purge specifications. N N N Y N N N N 4619 A CA, CAA, or CAJ copy pair cannot be suspended with Reverse specified because the command is issued to the P-VOL.
Type of error Error code Error details 4645 BC CA CAA CAJ CMD PATH SMART Other A CA or CAA copy pair status cannot be changed because a logical path has not been established between the P-VOL and S-VOL. N Y Y N N N N N 4649 CAA copy pair operations cannot be performed because the specified storage system does not support CAA. N N Y N N N N N 4650 A delta resync cannot be executed because volumes are specified within the range of the operation.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N The CAJ ATTIME suspend time cannot be set. The reason might be one of the following: • The specified time is earlier than the consistency time. • The timer type remains Local because the CAJ copy pair has not been resynchronized after the timer type was changed from Local to System. 466A When changing the timer type from Local to System, you need to suspend the CAJ copy pair.
Type of error Error code Error details 4684 The CAJ ATTIME suspend time cannot be set because the specified volume is currently being used in a CAJ Open/MF consistency group. BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N Table 53 Details of error codes 47xx - 49xx Type of error Error code Error details 47A3 BC CA CAA CAJ CMD PATH SMART Other A CA or CAA copy pair cannot be suspended because SVOL(PERMIT) or Reverse Resync is not supported.
Type of error Error code Error details 4A0B BC CA CAA CAJ CMD PATH SMART Other The C/T group ID specified for the CAA C/T group option change is not registered. N N Y N N N N N 4A0C The C/T group timer type (SYSTEM/LOCAL/NONE) for the CAA cannot be changed because there is a copy pair in this C/T group. N N Y N N N N N 4A30 The C/T group ID defined in the CAA copy group, and the C/T group ID set by the copy pair do not match.
Type of error Error code Error details 4A8E BC CA CAA CAJ CMD PATH SMART Other The command could not be executed because the status of the CA or CAA copy pair is being changed. N Y Y N N N N N 4A96 A CA or CAA copy pair cannot be made because the CLPR that the specified P-VOL belongs to differs from the one registered in the C/T group. For details on the CLPR, see the storage system documentation.
Type of error Error code Error details 4AFB A CA or CAA copy pair cannot be made because the CLPR that the specified S-VOL belongs to differs from the one registered in the C/T group. For details on the CLPR, see the storage system documentation.
Error code 4B09 Type of error Error details A copy pair that is in a CA copy group with a C/T group ID 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: BC CA CAA CAJ CMD PATH SMART Other N Y N N N N N N • 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.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N A copy pair cannot be created or resynchronized because the specified P-VOL satisfies one of the following conditions: 4B32 • The P-VOL is being used for FlashCopy. • The P-VOL is being used for FlashCopy SE. • The P-VOL is a TSE-VOL. 4B35 A path cannot be set because the CU number for the specified MCU is not supported.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other 4BDE The specified operation cannot be performed because either the local storage system or the remote storage system does not support inter-CU logical paths. N N N N N Y N N 4BE0 A CA copy pair cannot be made because the necessary shared memory is not implemented in the MCU.
Type of error Error code Error details 64FC BC CA CAA CAJ CMD PATH SMART Other A command device cannot be re-defined because the APID that was already defined does not match the APID you attempted to define. N N N N Y N N N 64FD The command device cannot be defined because a command device with the same APID has been defined for another device.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y Y Y N N N N N N Y Y N N N N N Y Y Y N N N N N A copy pair cannot be created or resynchronized. The reason might be one of the following: • The storage system serial number of the P-VOL is incorrect. 69F3 • 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.
Type of error Error code Error details 6A0F BC CA CAA CAJ CMD PATH SMART Other The command could not be executed because the CAA program product is not installed. N N Y N N N N N 6A13 The command could not be executed because a remote command was executed while the command device was not defined. N N N N N N N Y 6A14 The command could not be executed because it was specified to be remotely executed, but this command cannot be executed as a remote command.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N N N N N Y N The setting or status acquisition command for SMART could not be executed because of either of the following reasons: • The specified SSID and the SSID of the target storage system do not match. • The specified serial number and the serial number of the target storage system do not match. 6EC4 • The specified CU number and the CU number of the target device do not match.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N Y N Y N N N Y N N N N N N N N N N N Y A CA or CAA copy pair status cannot be changed. Possible reasons include one or more of the following: • The specified S-VOL is online. • The specified volume is either a CA or CAA pair volume, or the S-VOL of a BC copy pair. • All paths to the RCU are blocked.
Type of error Error code Error details 8CE9 BC CA CAA CAJ CMD PATH SMART Other The command could not be executed because the path for the Remote DKC Control Function is not set. N N N N N N N Y 8CEB The command could not be executed because the path for the Remote DKC Control Function is not set. N N N N Y N N N 8CFB The command could not be executed because in the instruction to transfer to a remote storage system, there is an error in the storage system serial number.
Type of error Error code Error details 8D14 The command could not be executed because the BC, CA, or CAA program product is not installed. BC CA CAA CAJ CMD PATH SMART Other Y Y Y N N N N N Y N N N N N N N Y N N N N N N N A BC copy pair cannot be made or resynchronized. Possible reasons include one or more of the following: 8D15 • The status of the copy pair does not allow the status transition. For details, see error code 2310.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N Y N N N N N N N A CA or CAA copy pair cannot be made or resynchronized. Possible reasons include one or more of the following: • The P-VOL is a command device. • The specified serial number of the primary storage system or SSID does not match the storage system serial number or SSID of the local CU. 8D1C • The specified P-VOL does not match the bootup volume. • The C/T group ID is incorrect.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other Y N N N N N N N Y N N N N N N N N Y Y N N N N N A BC copy pair cannot be suspended. Possible reasons include one or more of the following: 8D26 • 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.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N Y N N N N N N N A CA or CAA copy pair cannot be suspended. Possible reasons include one or more of the following: • The specified volume is in the SIMPLEX status. • The P-VOL number in the parameter and bootup volume number do not match. • The S-VOL number in the parameter is incorrect.
Type of error Error code Error details 8D38 BC CA CAA CAJ CMD PATH SMART Other The command could not be executed because the specified volume is not in the SIMPLEX status. N N N N Y N N N 8D39 A command device cannot be defined because it differs from the APID that was already registered. N N N N Y N N N 8D3A A command device cannot be defined because the specified APID is in use by another DEV.
Type of error Error code Error details 8D4F BC CA CAA CAJ CMD PATH SMART Other The command could not be executed because the specified volume is online. N N N N Y N N N 8D50 The host command parameter is incorrect. N N N N N N N Y 8D51 The command could not be executed because the logical volume of the specified volume is blocked or the specified volume is in the NOT READY status.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N Y N N N N N N N N N N N N N N Y N N Y N N N N N A CA or CAA copy pair cannot be dissolved. Possible reasons include one or more of the following: • It is already in the SIMPLEX status. • The P-VOL in the parameter and the bootup volume number do not match. • The S-VOL number in the parameter is incorrect.
Type of error Error code Error details 8D78 The host command parameter is incorrect. BC CA CAA CAJ CMD PATH SMART Other N N N N N N N Y N N Y N N N N N A CAA C/T group cannot be deleted. Possible reasons include one or more of the following: • The C/T group ID is incorrect. 8D79 • The C/T group is not registered. • There is a CAA copy pair in the corresponding C/T group. • There is a copy pair that is being dissolved or suspended in the specified C/T group.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other 8F10 A CAJ copy pair cannot be made because the specified volume has been made as a copy pair for BC or FlashCopy and cannot be used for this combination. N N N Y N N N N 8F14 A CAJ copy pair cannot be made because the specified volume is a Reserve volume. N N N Y N N N N 8F17 A CAJ copy pair cannot be made because the specified volume is online.
Type of error Error code Error details 8F29 A CAJ copy pair cannot be made because the PJNL group cannot be used. BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N N N N Y N N N N A CAJ copy pair cannot be created because the specified P-VOL satisfies one of the following conditions: 8F2A • The P-VOL is being used as the S-VOL for FlashCopy. • The P-VOL is being used for FlashCopy SE. • The P-VOL is a TSE-VOL.
Type of error Error code Error details 8F6D A CAJ copy pair cannot be made because the specified volume is a command device. BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N Table 60 Details of error codes C0xx Type of error Error code Error details C023 BC CA CAA CAJ CMD PATH SMART Other The specified serial number or SSID of the primary storage system is different from the storage system serial number or SSID of the local CU.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other C05A The serial number or SSID of the primary storage system in the CA or CAA parameter does not match the storage system serial number or SSID of the local CU. N Y Y N N N N N C05D The serial number or SSID of the secondary storage system in the CA or CAA parameter does not match the storage system serial number or SSID of the RCU.
Type of error Error code Error details C078 BC CA CAA CAJ CMD PATH SMART Other The S-VOL number in the CA or CAA parameter does not match the bootup volume number. N Y Y N N N N N C079 The serial number or SSID of the secondary storage system in the CA or CAA parameter does not match the storage system serial number or SSID of the RCU.
Type of error Error code Error details C126 The command to delete a path could not be executed because there is a CA, CAA, or CAJ copy pair or journal volume in the target CU. BC CA CAA CAJ CMD PATH SMART Other N N N N N Y N N N N N N N Y N N N N N N N Y N N An attempt to establish or delete some of the specified multiple paths have failed. Possible reasons include one or more of the following: C127 • The specified parameter is invalid.
Type of error Error code Error details C162 BC CA CAA CAJ CMD PATH SMART Other A copy pair cannot be resynchronized because the corresponding bootup pair is not in the suspend status. N Y Y N N N N N C184 A copy pair cannot be dissolved because an attempt to change the S-VOL status failed. N Y Y N N N N N C189 A CA or CAA copy pair cannot be dissolved because the copy pair status is invalid. N Y Y N N N N N N Y Y N N N N N The copy pair cannot be dissolved.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other C213 The command cannot be executed because the serial number or SSID of the primary storage system for the parameter does not match the actual serial number or SSID of the primary storage system.
Type of error Error code Error details C2B6 A copy pair cannot be created because the pages of the THPz volume specified for the P-VOL are being released.
Type of error Error code Error details C319 BC CA CAA CAJ CMD PATH SMART Other The collection copy is being performed on the PVOL. N Y Y N N N N N C31A The P-VOL is in a collection access status. N Y Y N N N N N C31B The logical volume of the P-VOL is blocked (PDEV blocking factor). N Y Y N N N N N C31C The P-VOL cannot be accessed (because the LDEV is blocked or in the NOT READY status).
Type of error Error code Error details C333 BC CA CAA CAJ CMD PATH SMART Other The S-VOL is not DFW ON. N Y Y N N N N N C335 The S-VOL is a CAA P-VOL. N Y Y N N N N N C336 The S-VOL has PIN data. N Y Y N N N N N C337 The S-VOL is in the Reserve status. N Y Y N N N N N C338 An intervention request has been issued for the SVOL (S-VOL or reserve volume of BC). N Y Y N N N N N C339 The S-VOL is in the FC status.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N A CA copy pair cannot be defined or resynchronized. The reason might be one of the following: C37B • The S-VOL is in an unusable state. • The microprogram version of the MCU or RCU does not support the function or configuration. C37C The subsystem level cache of the RCU is not valid. N Y Y N N N N N C37D The RCU is not NVS ON.
Type of error Error code Error details C398 BC CA CAA CAJ CMD PATH SMART Other A copy pair cannot be made because the S-VOL is not supported for the emulation type. N Y Y N N N N N C39E The P-VOL capacity exceeds the volume capacity within which a copy pair can be made. N Y Y N N N N N C39F The P-VOL or S-VOL capacity exceeds the volume capacity within which a copy pair can be made. N Y Y N N N N N C3A0 The P-VOL device is not supported by CA or CAA.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other C3BF The S-VOL of a BC copy pair or a Reserve volume cannot be specified as the S-VOL of a CA or CAA copy pair. Also, a P-VOL in the Reverse Resync status and the S-VOL for FlashCopy cannot be specified. N Y Y N N N N N C3C0 When the P-VOL of a CA or CAA copy pair is also the S-VOL of a BC copy pair, both S-VOLs must be a copy pair in a one-to-one combination.
Type of error Error code Error details C3D3 BC CA CAA CAJ CMD PATH SMART Other The specified SSID, or CU number of the RCU is incorrect. N Y Y N N N N N C3D6 The specified S-VOL cannot be used because the device cannot be recognized from the connection port. N Y Y N N N N N C3D7 The status of the S-VOL in the RCU is incorrect. N Y Y N N N N N C3D8 A CA/CAA copy pair cannot be made because the volume specified to be the S-VOL is a system residence volume.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N Y N N N N N A CAA copy pair cannot be created for one of the following reasons: CB12 • The C/T group ID specified in the RCU is already used for CAJ(OPEN). • A total of 128 C/T groups are used in the RCU for CAJ(OPEN) and CAA(MF/OPEN). CB18 A copy pair cannot be added to a C/T group where the P-VOL and the S-VOL are being swapped. N N Y N N N N N CB1D A dummy volume cannot be created on the S-VOL.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N N Y Y N N N N N N Y Y N N N N N A copy pair cannot be made because the specified S-VOL does not support either one or both of the following: CB9E • The timestamp transfer mode • The Open/MF Consistency Preservation Function CBD8 A copy pair cannot be made because the specified P-VOL is not a P-VOL for CAJ.
Type of error Error code Error details CBFC A CA copy pair cannot be made or resynchronized because the C/T group ID is not in the supported range. BC CA CAA CAJ CMD PATH SMART Other N Y Y N N N N N Table 65 Details of error codes DBxx - E8xx Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N A CAJ copy pair status cannot be changed because the status transition is not allowed.
Error code Type of error Error details BC CA CAA CAJ CMD PATH SMART Other N N N Y N N N N A CAJ copy pair cannot be resynchronized. Possible reasons include both of the following: E869 • The R-JNL of the specified CAJ copy pair is being used by a CAJ copy pair that has another mirror ID. • The mirror status of another CAJ copy pair that is using the specified CAJ copy pair is Halting or Stopping.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other E882 A CAJ copy pair cannot be made because the emulation type for the volumes comprising the specified M-JNL group does not match that of the R-JNL group. N N N Y N N N N E885 A CAJ copy pair cannot be made because the specified R-JNL group has already been made into a copy pair with another M-JNL group.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other E898 A CAJ copy pair cannot be resynchronized because the specified R-JNL group is in use as an RJNL group for a CAJ copy pair with another mirror ID. N N N Y N N N N E89A A CAJ copy pair cannot be made because an interDKC logical path has not been established in the forward or reverse direction. Make sure that interDKC logical paths have already been established in both directions.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other E8BD Registration to EXCTG has failed because the number of journal groups to be registered exceeded the maximum number which can be registered. N N N Y N N N N E8BF Registration to EXCTG has failed because the number of subordinate storage systems has exceeded the maximum number which can be registered.
Type of error Error code Error details EA13 BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be resynchronized because the volume specified for the P-VOL is the SVOL of the CAJ copy pair. N N N Y N N N N EA15 A CAJ copy pair cannot be resynchronized because the volume specified for the S-VOL is the PVOL of the CAJ copy pair. N N N Y N N N N EA18 A CAJ copy pair cannot be resynchronized because the copy pair is not in the suspend status.
Type of error Error code Error details EA3A BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be dissolved because the specified S-VOL status is being changed at the moment. N N N Y N N N N EA3B A CAJ copy pair resynchronization, which causes a copy direction reversal, cannot be made because the copy pair is in the TRANS status.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other EAA3 A CAJ copy pair cannot be made because the charging limit of CA in the RCU has been exceeded. Check the license capacity of this and all related program products. N N N Y N N N N EAA5 A CAJ copy pair cannot be made because the charging limit of CAJ in the RCU has been exceeded. Check the license capacity of this and all related program products.
Type of error Error code Error details EB0A EB0F BC CA CAA CAJ CMD PATH SMART Other Registration to or deletion from EXCTG has failed because another EXCTG registration or deletion process is in progress. N N N Y N N N N Registration to or deletion from EXCTG has failed because the specified device is not an arbitration command device.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other EB3C A CAJ copy pair status cannot be changed because the specified serial number or SSID of the primary storage system does not match the actual serial number or SSID of the primary storage system. N N N Y N N N N EB3D A CAJ copy pair status cannot be changed because the specified serial number or SSID of the secondary storage system does not match the actual serial number or SSID of the secondary storage system.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other EB5E A CAJ copy pair cannot be made because the SVOL is not in the SIMPLEX status. Alternatively, a CAJ copy pair cannot be resynchronized because the S-VOL is not in the suspend status. N N N Y N N N N EB5F A CAJ copy pair cannot be made because the CAJ program product is not installed on the secondary storage system.
Type of error Error code Error details EB79 BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be made or resynchronized because the S-VOL is online. N N N Y N N N N EB7A A CAJ copy pair cannot be made because a journal cache remains in the R-JNL group. N N N Y N N N N EB7D A CAJ copy pair cannot be made because the specified S-VOL is an external volume.
Type of error Error code Error details EB8A BC CA CAA CAJ CMD PATH SMART Other A CAJ copy pair cannot be made because the emulation types of the specified M-JNL group and R-JNL group do not match. N N N Y N N N N EB94 A CAJ copy pair status cannot be changed because the status of the specified copy pair does not allow the status transition. N N N Y N N N N EBA0 A CAJ copy pair status cannot be changed because the specified S-VOL is not installed.
Type of error Error code Error details BC CA CAA CAJ CMD PATH SMART Other EBD9 A CAJ copy pair cannot be made because the charging limit of CA in the RCU has been exceeded. Check the license capacity of this and all related program products. N N N Y N N N N EBDA A CAJ copy pair cannot be made because the charging limit of CAA in the RCU has been exceeded. Check the license capacity of this and all related program products.
3 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This guide follows the conventions shown in Table 68.
Product reference Full name or meaning LRECL Logical RECord Length MIH Missing Interrupt Handler OS Operating System RACF Resource Access Control Facility RAID Redundant Array of Independent Disks RECFM RECord ForMat REXX REstructured eXtended eXecutor ROI Return On Investment SAF System Authorization Facility SAS Serial Attached SCSI SATA Serial Advanced Technology Attachment SCSI Small Computer System Interface SLA Service Level Agreement Smart Manager for Mainframe HP XP7 Sma
Support and other resources
Index D Details of error codes, 221 I Identifying the volume to be processed, 218 M Message format, 9 Message output destination, 11 Message output format, 9 Messages starting with KT, 11 Messages starting with YK, 51 Multi-line messages output to SYSTSPRT starting from YK, 213 N Notations used to describe messages, 10 U User completion codes, 218 Messages 295
