000/01/1000	An error occurred during Remote Web Console processing.
000/01/1001	A time-out error occurred.
000/01/1002	An error occurred during Remote Web Console processing.
000/01/1003	An error occurred during Remote Web Console processing.
000/01/1004	An error occurred during Remote Web Console processing.
000/01/2000	An error occurred during Remote Web Console processing.
000/01/2001	An error occurred during Remote Web Console processing.
000/01/2002	An error occurred during Remote Web Console processing.
000/01/2005	An error occurred during Remote Web Console processing.
000/01/3000	An error occurred during Remote Web Console processing.
000/01/3001	The number of set operation exceeds maximum (20000).
000/01/3002	An error occurred during Remote Web Console processing.
000/01/4001	An error occurred during SVP processing.
000/01/4006	An error occurred during Remote Web Console processing.
000/01/4007	An error occurred during Remote Web Console processing.
000/01/4008	An error occurred during Remote Web Console processing.
000/01/4009	An error occurred during Remote Web Console processing.
000/01/4010	An error occurred during Remote Web Console processing.
000/01/4011	A network error occurred. The probable cause is: \\n- A timeout error occurred during communication with the SVP.
000/01/4012	The number of clients logged on to the RMI server has exceeded 32.
000/01/4013	The SVP configuration is invalid.
000/01/4020	Network error detected; exclusive lock is released.
000/01/5013	An error occurred during Remote Web Console processing.
000/01/5014	The user ID or password is invalid.
000/01/5075	An error occurred during Remote Web Console processing.
000/01/5099	An error occurred during Remote Web Console processing.
000/01/5132	The specified user ID is already logged on, or the previous logon was not properly terminated. Please try again later. (By default, the session/RMI time-out is one minute.)
000/01/5300	An error occurred during Remote Web Console processing.
000/01/5301	An error occurred during Remote Web Console processing.
000/01/5400	Failed to access the monitoring data because accessing the monitoring data on the SVP is busy.
000/01/55034	An error occurred during Remote Web Console processing.
000/01/55044	An error occurred during Remote Web Console processing.
000/01/5508	An administrator is changing a system environment file. Please log on again after waiting for a while.
000/01/5509	Modify mode released due to inactivity. Do you want to get back to the Modify mode?
000/01/5514	An error occurred during Remote Web Console processing.
000/01/5515	An error occurred during Remote Web Console processing.
000/01/5516	An error occurred during Remote Web Console processing.
000/01/5517	An error occurred during Remote Web Console processing.
000/01/5518	An error occurred during Remote Web Console processing.
000/01/5519	An error occurred during Remote Web Console processing.
000/01/5520	An error occurred during Remote Web Console processing.
000/01/55200	An internal logical error occurred.
000/01/5521	An error occurred during Remote Web Console processing.
000/01/5522	An error occurred during Remote Web Console processing.
000/01/5523	An error occurred during Remote Web Console processing.
000/01/5635	An error occurred during Remote Web Console processing.
000/01/5636	An error occurred during Remote Web Console processing.
000/01/5637	An error occurred during Remote Web Console processing.
000/01/5638	An error occurred during Remote Web Console processing.
000/01/5639	An error occurred during Remote Web Console processing.
000/01/5640	An error occurred during Remote Web Console processing.
000/01/56545	The operation failed because the audit log is being processed. Please wait for a while, and then retry the operation.
000/01/56548	The SVP is transferring the file to the FTP server. Wait for a while, then retry the operation.
000/01/56549	Another user is downloading the file or transferring the file to the FTP server. Please wait for a while, and then retry the operation.
000/01/56550	Transfer to the FTP server is disabled. Check the setting.
000/01/56551	Failed to connect to the FTP server. Check the IP address, or the connection between the SVP and the FTP server.
000/01/56552	The file transfer to the FTP server failed. Check the user ID and the password.
000/01/56553	The file transfer to the FTP server failed. Check the output folder and the status of the FTP server.
000/01/56554	The file transfer to the FTP server failed. If this problem persists, please call the HSSC.
000/01/56555	The complete operation is performed to all SIMs related to Audit Log.
000/01/56556	Complete operation of SIMs failed because the number of audit logs that had not been transferred exceeded the threshold.
000/01/56557	The complete operation of the SIM may not have completed since the SVP is busy.
000/01/57106	An invalid value is included in the management file of the audit log. Please retry the operation.
000/01/5811	An error occurred during Remote Web Console processing.
000/01/5813	An error occurred during Remote Web Console processing.
000/01/5814	An error occurred during Remote Web Console processing.
000/01/6002	An error occurred during Remote Web Console processing.
000/01/6004	An error occurred during Remote Web Console processing.
000/01/6012	An error occurred during Remote Web Console processing.
000/01/6022	A file open error has occurred.
000/01/6023	Failed to access the file. Check the setting, and then retry the operation. If the same problem persists despite retrying, please call the HSSC.
000/01/6039	An error occurred during SVP processing. If this problem persists, please call the HSSC.
000/01/65734	CVAE version information ID is invalid. Check the setting, and then retry the operation.
000/01/66100	The login could not be performed because a function failed to start during SVP initialization.
000/01/66559	The operation failed because the SVP OS does not support IPv6.
000/01/66802	No more CVAE version information can be registered, because the number of registered CVAE version information reached the maximum. Reduce the number of CVAE version information and then retry the operation.
000/01/7003	The content of the management file of the audit log is invalid.
000/01/7050	An error occurred during processing. The software version of Remote Web Console on the client PC might not match that of the destination SVP.
000/02/2001	An error occurred during Remote Web Console processing.
000/02/2002	An error occurred during Remote Web Console processing.
000/02/2003	The SVP is busy.
000/02/2004	An error occurred during Remote Web Console processing.
000/02/2005	An error occurred during Remote Web Console processing.
000/02/2006	An error occurred during Remote Web Console processing.
000/02/2007	The storage system is refreshing or some other user is changing the setting.
000/02/2008	An error occurred during SVP processing.
000/02/2009	An error occurred during Remote Web Console processing.
000/02/2010	An error occurred during Remote Web Console processing.
000/02/2011	The SVP configuration is invalid.
000/02/2013	An error occurred during Remote Web Console processing.
000/02/2015	An error occurred during Remote Web Console processing.
000/02/2016	The array is refreshing, or some other user is registering the setting.
000/02/206500	The configuration information of the Virtual Storage Machine has changed.
000/02/2145	An error occurred while communicating with the storage system.
000/02/3003	An error occurred during Remote Web Console processing.
000/02/5010	An error occurred during Remote Web Console processing.
000/02/5040	The number of requests exceeds the maximum number that can be processed.
000/02/5510	The storage system is in the internal process, or some other user is changing the configuration.
000/02/58578	An error occurred in the storage system. The configuration may be inconsistent. 
000/02/6000	An error occurred during Remote Web Console processing.
000/02/6002	An error occurred during Remote Web Console processing.
000/02/6012	An error occurred during Remote Web Console processing.
000/02/6022	An error occurred during Remote Web Console processing.
000/02/6023	An error occurred during Remote Web Console processing.
000/02/6050	An error occurred during Remote Web Console processing.
000/02/6502	Processing is in progress.
000/02/65740	The configuration changing processes are conflicting at DKC.
000/02/66100	The login could not be performed because a function failed to start during SVP initialization.
000/02/7030	An error occurred during Remote Web Console processing.
000/02/7060	An error occurred during Remote Web Console processing.
000/02/76516	The resource group definition is being changed.
000/02/8000	An error occurred while connecting to the storage system.
000/02/8001	A communication time-out error occurred.
000/02/8005	An error occurred during Remote Web Console processing.
000/02/8100	An error occurred while connecting to the storage system.
000/02/9000	Another user is accessing with Modify mode.
000/02/9999	An error occurred during Remote Web Console processing.
000/03/1900	The operation cannot be performed because the storage system is being maintained.
000/03/2001	An error occurred during Remote Web Console processing.
000/03/2003	Such as Auto LUN and QuickRestore are in progress.
000/03/2004	An error occurred during Remote Web Console processing.
000/03/2005	An error occurred during Remote Web Console processing.
000/03/2006	An error occurred during Remote Web Console processing.
000/03/2009	An error occurred during Remote Web Console processing.
000/03/2011	The status of the storage system requires maintenance. (for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
000/03/2013	An error occurred during Remote Web Console processing.
000/03/2015	An error occurred while connecting to the storage system.
000/03/2016	A service engineer is accessing the system in Modify mode.
000/03/2017	Network error detected; exclusive lock is released.
000/03/2032	Communication busy.
000/03/2033	The SVP is not ready yet, or an internal processing is being executed.
000/03/2083	The storage system status is invalid.
000/03/2084	The storage system status is invalid.
000/03/2100	An error occurred while connecting to the storage system. The configuration may be inconsistent.
000/03/3003	An error occurred during Remote Web Console processing.
000/04/6000	An error occurred during Remote Web Console processing.
000/04/6001	A time-out error occurred.
000/04/6002	An error occurred during Remote Web Console processing.
000/04/6003	An error occurred during Remote Web Console processing.
000/04/6010	An error occurred during Remote Web Console processing.
000/04/6011	An error occurred during Remote Web Console processing.
000/04/6012	An error occurred during Remote Web Console processing.
000/04/6013	An error occurred during Remote Web Console processing.
000/04/6023	An error occurred during Remote Web Console processing.
000/04/6037	The storage system status is invalid.
000/05/2007	The storage system is refreshing or some other user is changing the setting.
000/05/5099	An error occurred during Remote Web Console processing.
000/05/66101	This function could not be used because a function failed to start during SVP initialization.
000/06/1005	An error occurred during Remote Web Console processing.
000/06/1006	An error occurred during Remote Web Console processing.
000/06/1007	An error occurred during Remote Web Console processing.
000/06/1009	An error occurred during Remote Web Console processing.
000/06/4000	The SVP configuration is invalid.
000/07/5013	An error occurred during Remote Web Console processing.
000/07/56546	Another user is downloading the file or transferring the file to the FTP server. Please wait for a while, and then retry the operation.
000/07/6012	An error occurred during Remote Web Console processing.
000/07/6022	File access error is occurred. If a file is transferred between SVP and client PC, confirm that the file name does not contain invalid characters. In other cases, please wait for a while, and retry the operation.
000/07/6023	File access error is occurred. If a file is transferred between SVP and client PC, confirm that the file name does not contain invalid characters. In other cases, please wait for a while, and retry the operation.
000/07/6091	An error occurred while compressing a file.
000/07/6092	An error occurred while reading a file.
000/07/6093	The specified file was not found. 
000/10/6027	A network error occurred. The causes might be one of the following.\\n- The SVP was not ready.\\n- An error occurred in the SVP.\\n- A timeout error occurred while communicating with the SVP.
000/21/105001	No table rows are selected.
000/21/109006	Are you sure you want to apply the setting information?
000/22/107001	The process cannot be continued due to an internal logical contradiction.
000/22/107002	The processing cannot continue due to an internal logic contradiction.
000/22/107003	The processing cannot continue due to an internal logic contradiction.
000/22/107004	The process cannot be continued due to an internal logical contradiction.
000/22/107005	The processing cannot continue due to an internal logic contradiction.
000/22/400001	Either of the two options, No.5 or No.6, can be enabled.
001/05/3003	An error occurred during Remote Web Console processing.
001/05/6012	An error occurred during Remote Web Console processing.
001/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
001/10/5030	The displayed information has not been changed. Try again.
001/10/55045	The installation status of program products has been changed.\\nTo update the status immediately, click [Refresh] on the File menu.
001/10/56503	The unsupported JRE version is used.\\nInstall the supported version of JRE, then retry the operation.
001/10/56558	Modify mode released due to inactivity. Another user or service engineer may have changed the configuration while the Modify mode was released. Get back to the Modify mode and change the configuration again. Set the "RMI time-out period for Modify" by using the "Set Env." dialog box located on the Control Panel of the Remote Web Console to change the time-out period for Modify mode.
001/10/57011	An error occurred regarding screen display. \\nPlease log off from Remote Web Console. After that, \\nplease log on to Remote Web Console again and \\ncheck whether configuration changes have been made correctly.
001/10/59002	The storage system is in internal process, or some other user is changing the configuration.\\nWait, then click [OK] and change the mode to Modify. Do you want to change the mode to Modify again?
001/10/59003	Succeeded to change the mode to Modify.
001/10/59105	Do you want to refresh all the configuration information?
001/10/65092	An error occurred regarding screen display. Select the window you wish to display from the [Go] menu.
001/10/67005	Configuration information on the storage system and the configuration information\\non the SVP became inconsistent. Click [Refresh All] on the File menu and refresh\\nthe configuration information.
001/10/69007	Another user is accessing in Modify mode. Please wait for a while, then retry the operation.
001/10/69024	No function can be used.
001/10/69028	The setting may not be applied when another user is applying the setting.\\nWhen the setting is not applied, wait a while and retry the operation.\\nDo you want to continue?
001/10/7060	An error occurred in the client logic.
001/10/7440	An error occurred during processing. If this problem persists, please call the HSSC.
001/10/8100	A SIM occurred.
001/10/9002	The requested operation is complete.
001/10/9100	Do you want to exit?
001/10/9101	Do you want to cancel?
001/10/9102	Do you want to apply?
001/10/9104	Do you want to change the mode?
001/10/9105	The value that is under setup is not reflected yet.\\nDo you want to exit?
001/10/9106	The value that is under setup is not reflected yet. \\nDo you want to change the mode?
001/10/9107	The value that is under setup is not reflected yet. \\nDo you want to continue the operation?
001/22/105260	The free space for storing audit log files is running out. \\nUsage Rate {0}% 
001/22/105261	The free space for storing audit log files has run out. The old audit log information will be overwritten. \\nUsage Rate {0}%
001/22/107016	The audit log is not reset because the file of the audit log is not saved.
001/22/107017	An error occurred while accessing the alert information.
001/22/107020	The state of Audit Log cannot be acquired.
001/22/107021	The lock status of the resource cannot be obtained.
001/22/109011	The free space for storing audit log files is normal value. \\nUsage Rate {0}%
002/21/105007	The re-entered password does not match the one entered previously.
002/21/105008	The re-entered secret does not match the one entered previously.
002/22/105212	The characters used for the user name or the number of the characters of the user name is invalid.
002/22/105213	A radio button for Account Status is not selected.
002/22/105214	A radio button for authentication is not selected.
002/22/105215	The characters used for the password or the number of the characters of the password is invalid.
002/22/105216	The re-entered password does not match the password which entered previously.
002/22/105217	The specified current password is incorrect.
002/22/105218	The new password is identical to the current password.
002/22/105219	The characters used for the new password or the number of the characters of the new password is invalid.
002/22/105220	The re-entered new password does not match the new password entered previously.
002/22/105221	No check box is selected.
002/22/105222	The user to be registered is not selected.
002/22/105223	No table row, or two or more table rows are selected.
002/22/105224	Two or more table rows are selected.
002/22/105225	No table rows are selected.
002/22/105316	No certification file is selected.
002/22/105317	Invalid characters are used in the certification file name.
002/22/105318	The domain name of authentication server is not input.
002/22/105319	The domain name of authentication server is too long.
002/22/105320	Invalid characters are used in the domain name of authentication server.
002/22/105321	The user name attribute of authentication server is not input.
002/22/105322	Invalid characters are used in the specified user name attribute of authentication server.
002/22/105323	The timeout of authentication server is not input.
002/22/105324	Other than the numeric characters are input to the specified timeout of authentication server.
002/22/105325	The value that can be input to the timeout of authentication server is 1 to 120.
002/22/105326	The retry interval for the authentication server is not input.
002/22/105327	Other than the numeric characters are input to the retry interval of authentication server.
002/22/105328	The value that can be input to the retry interval of authentication server is 1 to 60.
002/22/105329	The number of retries for the authentication server is not input.
002/22/105330	Other than the numeric characters are input to the specified number of retries of authentication server.
002/22/105331	The value that can be input to the number of retries of authentication server is 1 to 50.
002/22/105332	The base DN of authentication server is not input.
002/22/105333	The base DN of authentication server is too long.
002/22/105334	Invalid characters are used in the specified base DN of authentication server.
002/22/105335	The user DN of authentication server for searching is not input. 
002/22/105336	The user DN of authentication server for searching is too long. 
002/22/105337	Invalid characters are used in the specified user DN of authentication server for searching.
002/22/105338	The password of authentication server is not input.
002/22/105339	The password of authentication server is too long.
002/22/105340	Invalid characters are used in the specified password of authentication server.
002/22/105341	The Re-enter Password of authentication server is not input.
002/22/105342	The re-entered password of authentication server is too long.
002/22/105343	Invalid characters are used in the re-entered password of authentication server.
002/22/105344	The re-entered password does not match the one entered previously.
002/22/105345	A secondary server cannot be enabled because DNS Lookup of authentication server is enabled.
002/22/105346	LDAP over SSL/TLS for protocol cannot be selected because DNS Lookup of authentication server is enabled.
002/22/105347	The primary host name of authentication server is not input.
002/22/105348	The primary host name of authentication server is too long.
002/22/105349	Invalid characters are used in the specified primary host name of authentication server.
002/22/105350	The primary port number of authentication server is not input.
002/22/105351	Other than the numeric characters are input to the specified primary port number of authentication server.
002/22/105352	The value that can be input to the primary port number of authentication server is 1 to 65535.
002/22/105353	The secondary host name of authentication server is not input.
002/22/105354	The secondary host name of authentication server is too long.
002/22/105355	Invalid characters are used in the specified secondary host name of authentication server.
002/22/105356	The secondary port number of authentication server is not input.
002/22/105357	Other than the numeric characters are input to the secondary port number of authentication server.
002/22/105358	The value that can be input to the secondary port number of the authentication server is 1 to 65535.
002/22/105359	The secret of authentication server is not input.
002/22/105360	The secret of authentication server is too long.
002/22/105361	Invalid characters are used in the specified secret of authentication server.
002/22/105362	The Re-enter Secret of authentication server is not entered.
002/22/105363	The re-entered secret of authentication server is too long.
002/22/105364	Invalid characters are used in the Re-enter Secret of authentication server.
002/22/105365	The re-entered secret does not match the one entered previously.
002/22/105366	The NAS address of authentication server is not input.
002/22/105367	The NAS address of authentication server is too long.
002/22/105368	Invalid characters are used in the specified NAS address of authentication server.
002/22/105371	The realm name of authentication server is not input.
002/22/105372	The realm name of authentication server is too long.
002/22/105373	Invalid characters are used in the specified realm name of authentication server.
002/22/105374	The clock skew of authentication server is not input.
002/22/105375	Other than the numeric characters are input to the specified clock skew of authentication server.
002/22/105376	The value that can be input to the clock skew of authentication server is 1 to 120.
002/22/105377	The domain name of external user group mapping is not input.
002/22/105378	The domain name of external user group mapping is too long.
002/22/105379	Invalid characters are used in the specified domain name of external user group mapping.
002/22/105380	The base DN of external user group mapping is not input.
002/22/105381	The base DN of external user group mapping is too long.
002/22/105382	Invalid characters are used in the specified base DN of external user group mapping.
002/22/105383	The user DN of external user group mapping for searching is not input.
002/22/105384	The user DN of external user group mapping for searching is too long.
002/22/105385	Invalid characters are used in the specified user DN of external user group mapping for searching.
002/22/105386	The password of external user group mapping is not input.
002/22/105387	The password of external user group mapping is too long.
002/22/105388	Invalid characters are used in the specified password of external user group mapping.
002/22/105389	The Re-enter Password of external user group mapping is not input.
002/22/105390	The re-entered password of external user group mapping is too long.
002/22/105391	Invalid characters are used in the re-entered password of external user group mapping.
002/22/105392	The timeout value of external user group mapping is not input.
002/22/105393	Other than the numeric characters are input to the specified timeout value of external user group mapping.
002/22/105394	The value that can be set for the timeout of external user group mapping is 1 to 120.
002/22/105395	The retry interval for the external user group mapping is not input.
002/22/105396	Other than the numeric characters are input to the retry interval of external user group mapping.
002/22/105397	The value that can be input to the retry interval of external user group mapping is 1 to 60.
002/22/105398	The number of retries for the external user group mapping is not input.
002/22/105399	Other than the numeric characters are input to the specified number of retries of authentication server.
002/22/105400	The value that can be input to the number of retries of external user group mapping is 1 to 50.
002/22/105401	A secondary server cannot be enabled because DNS Lookup of external user group mapping is enabled.
002/22/105402	LDAP over SSL/TLS for protocol cannot be selected because DNS Lookup of external user group mapping is enabled.
002/22/105403	The primary host name of external user group mapping is not input.
002/22/105404	The primary host name of external user group mapping is too long.
002/22/105405	Invalid characters are used in the specified primary host name of external user group mapping.
002/22/105406	The primary port number of external user group mapping is not input.
002/22/105407	Other than the numeric characters are input to the specified primary port number of external user group mapping.
002/22/105408	The value that can be input to the primary port number of external user group mapping is 1 to 65535.
002/22/105409	The secondary host name of external user group mapping is not input.
002/22/105410	The secondary host name of external user group mapping is too long.
002/22/105411	Invalid characters are used in the specified secondary host name of external user group mapping.
002/22/105412	The secondary port number of external user group mapping is not input.
002/22/105413	Other than the numeric characters are input to the specified secondary port number of external user group mapping.
002/22/105414	The value that can be input to primary port number of external user group mapping is 1 to 65535.
002/22/105415	The user name for connecting test is not input.
002/22/105416	The user name for connecting test is too long.
002/22/105417	Invalid characters are used in the specified user name for connecting test.
002/22/105418	The password for connecting test is not input.
002/22/105419	The password for connecting test is too long.
002/22/105420	Invalid characters are used in the specified password for connecting test.
002/22/106043	No more users can be registered, because the number of registered users has reached the maximum.
002/22/106044	The same User Name is already registered.
002/22/106045	The specified operation cannot be done, because the authentication type of the selected user is not local.
002/22/106046	You cannot disable your account by yourself.
002/22/106047	Neither disabling nor deleting the user account is permitted.
002/22/106048	Only the local authentication setting can be specified for the built-in user.
002/22/106049	Failed to change the user information.
002/22/106050	There is no user who can belong to the specified user group. 
002/22/106051	The number of user groups that can be associated with a user has reached the maximum.
002/22/106052	Failed to change the user account information.
002/22/106053	A built-in user cannot be deleted.
002/22/106054	You cannot delete your own account.
002/22/106055	Failed to delete the user account.
002/22/106056	No more user groups can be registered because the number of registered user groups has reached the maximum. 
002/22/106057	A built-in group cannot be deleted.
002/22/106058	A built-in group cannot be specified.
002/22/106059	A user group where the "All Resource Groups Assigned" is set to "Yes" cannot be specified.
002/22/106060	There are no resource groups that can be allocated to the specified user group. 
002/22/106061	Characters or the number of characters for user group name are invalid.
002/22/106062	The same user group name is already registered.
002/22/106063	Failed to change the user information.
002/22/106064	Failed to change the user information.
002/22/106065	Failed to delete the user group.
002/22/106066	The role of Storage Administrator (View Only) cannot be removed.
002/22/106067	"All Resource Groups Assigned" becomes enabled.
002/22/106068	You cannot remove the selected users, because "Administrator User Group" will have no enabled users who have the local authentication setting.
002/22/106069	You cannot remove the selected users, because they will not belong to any groups.
002/22/106070	The Built-in user cannot be removed.
002/22/106071	The selected users could not be removed.
002/22/106072	"All Resource Groups Assigned" becomes disabled. Assign resource groups.
002/22/106073	There are some user groups to which an unmounted resource group is allocated. 
002/22/106074	There is no selected resource group.
002/22/106075	It is important to backup your settings. \\nUse the "Download File" window located on the Control Panel of the Remote Web Console, and then backup your setting information.
002/22/106076	The password cannot be changed due to one of the following reasons.  \\n- The selected user does not exist in local accounts . \\n- The user who logged in is registered in the external authentication server.\\n
002/22/106077	Failed to connect to the authentication server.
002/22/106078	The specified user group cannot be deleted because the user group has a user who will not belong to any groups. 
002/22/107001	An error occurred while accessing the user information.
002/22/107005	The processing cannot continue due to an internal logic contradiction.
002/22/107010	The process cannot be continued due to internal logic contradiction.
002/22/107011	The selected user group does not exist.
002/22/107012	The selected user does not exist.
002/22/107013	Failed to get the user information.
002/22/107014	Failed to get the user group information.
002/22/107017	An error occurred while accessing the alert information.
002/22/107024	An error occurred during Remote Web Console processing.
002/22/109023	A logic contradiction is detected in the setting.
002/22/109024	Any external authentication server is not set up.
002/22/205421	The user ID or the password is not valid.
002/22/205422	The selected user [{0}] is registered in the Storage Device List. If the operation continues, communication with the Storage Device List is not available.
003/05/56525	Because the settings across the multiple SLPRs are contained, the authority has been shifted to the storage administrator from the storage partition administrator.
003/05/56526	The resources of other SLPR(s) cannot be accessed.
003/05/6001	An error occurred during Remote Web Console processing.
003/05/6012	An error occurred during Remote Web Console processing.
003/05/6022	An error occurred during Remote Web Console processing.
003/05/6023	An error occurred during Remote Web Console processing.
003/05/65685	0 cannot be specified in all the fields.
003/05/65686	The Management Server does not support IPv6.
003/05/7060	An error occurred during Remote Web Console processing.
003/05/7102	An error occurred during Remote Web Console processing.
003/05/7103	An error occurred during Remote Web Console processing.
003/05/7110	An error occurred during Remote Web Console processing.
003/05/7201	An error occurred during Remote Web Console processing.
003/05/7202	An error occurred during Remote Web Console processing.
003/05/7203	An error occurred during Remote Web Console processing.
003/05/7204	An error occurred during Remote Web Console processing.
003/05/7205	An error occurred during Remote Web Console processing.
003/05/7206	An error occurred during Remote Web Console processing.
003/05/7207	An error occurred during Remote Web Console processing.
003/05/7208	An error occurred during Remote Web Console processing.
003/05/7209	An error occurred during Remote Web Console processing.
003/05/7210	An error occurred during Remote Web Console processing.
003/21/209013	Are you sure you want to send a test SNMP trap based on the applied information?
003/21/209014	Are you sure you want to remove all the community settings in the selected rows?
003/21/209015	Are you sure you want to remove the trap destinations in the selected rows?
003/22/205025	No more communities can be registered because the number of registered communities has reached the maximum. 
003/22/205026	The IP address is already used.
003/22/205027	The community is already used.
003/22/205028	No more trap destinations can be registered because the number of registered trap destinations in the community has reached the maximum. 
003/22/205029	The combination of the selected rows is invalid.
003/22/205030	The form of the community is wrong.
003/22/205031	No more managers can be registered because the number of registered IP addresses has reached the maximum. 
003/22/205040	Failed to send a test trap.
003/22/209003	A test trap was sent.
004/05/5013	An error occurred during Remote Web Console processing.
004/05/5074	The specified program product ID is not valid.
004/05/6012	An error occurred during Remote Web Console processing.
004/05/6023	An error occurred during Remote Web Console processing.
004/05/7060	An error occurred during Remote Web Console processing.
004/05/7063	An error occurred during Remote Web Console processing.
004/05/7111	An error occurred during Remote Web Console processing.
004/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
004/05/8301	The information of the license cannot be collected.
004/07/5013	An error occurred during Remote Web Console processing.
004/07/6012	An error occurred during Remote Web Console processing.
004/07/6023	An error occurred during Remote Web Console processing.
004/07/7111	An error occurred during Remote Web Console processing.
004/21/209001	Are you sure you want to clear all rows in the [Selected License Keys] table?
004/22/205002	No table rows are selected.
004/22/205003	No key code.
004/22/205004	The license key file is not selected.
004/22/205005	The license key file name exceeds 200 characters.
004/22/205006	The specified program product is not installed.
004/22/205007	The specified program product cannot be enabled because the status is not Install (Disable).
004/22/205008	The specified program product cannot be disabled because the status is not Term.
004/22/205009	The specified program product cannot be disabled because the status is not Install.
004/22/205010	The operation cannot be performed because a license setting task is being queued.
004/22/205012	The specified program product cannot be enabled because the status is not Installed (Disabled).
004/22/205013	The specified program product cannot be disabled because the status is not Installed.
004/22/205052	The operation cannot be performed because the storage system is in internal process, or the configuration change is being performed by a different operation.
004/22/207001	The processing cannot continue due to an internal logic contradiction.
004/22/207002	The processing cannot continue due to an internal logic contradiction.
004/22/207003	The processing cannot continue due to an internal logic contradiction.
004/22/207004	The processing cannot continue due to an internal logic contradiction.
004/22/209001	No licenses whose status update is required.
006/05/2011	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
006/05/2015	An error occurred while communicating with the storage system.
006/05/208001	The operation cannot be performed because the capacity of the specified LDEV is different from that of the selected external volume.
006/05/208002	Data Direct Mapping cannot be enabled because the specified emulation type is not OPEN-V.
006/05/208003	The specified LDEV ID of the pool volume is outside the setting range.
006/05/208004	The operation cannot be performed because the specified pool volume is not associated with a pool with the Data Direct Mapped attribute.
006/05/208005	The operation cannot be performed because the specified pool volume is associated with a different Thin Provisioning volume.
006/05/208007	No volumes with the Data Direct Mapped attribute can be created because the specified capacity of the external volumes does not satisfy the requirements for the pool volume.
006/05/208008	No volumes can be created because the Data Direct Mapped attribute differs between the specified volume and pool.
006/05/208009	Full Allocation and Data Direct Mapping cannot be enabled at the same time.
006/05/208011	The operation cannot be performed because the PCIe channel board is in the blocking process.
006/05/208012	The operation cannot be performed because the PCIe channel board is blocked.
006/05/208464	The operation cannot be performed, because Fast Snap pairs exist in the pool to which the selected pool volumes or external volumes belong.
006/05/208465	The operation cannot be performed, because Fast Snap pairs and THP V-VOLs whose LDEV status is Normal exist in the pool to which the selected pool volumes or external volumes belong.
006/05/2095	The specified operation cannot be performed due to one of the following maintenance operations:\\n- LDEV formatting is in progress.\\n- The CHB/DKB status is changing.\\n- The processor status is changing.\\n- The cache status is changing.\\n- LDEV shredding is in progress.\\n- The configuration is changing.
006/05/2201	Processing cannot be performed because of Data Retention settings.
006/05/2205	Journal volumes are included in the external volumes to be maintained.
006/05/2511	The restore operation has been failed, because the specified LDEV was not shredded or formatted.
006/05/2515	A pair of Continuous Access Synchronous or Continuous Access Journal is defined.
006/05/2516	A pair of Continuous Access Synchronous or Continuous Access Journal is defined.
006/05/2517	A pair of Business Copy or Fast Snap is defined.
006/05/2518	A pair of Business Copy is defined.
006/05/2520	An Auto LUN pair is defined.
006/05/2521	An Auto LUN pair is defined.
006/05/3003	An error occurred during Remote Web Console processing.
006/05/5013	An error occurred during Remote Web Console processing.
006/05/5099	An error occurred during Remote Web Console processing.
006/05/5511	Necessary program products are not installed.
006/05/56515	The Disconnect External Storage Systems or the Disconnect External Volumes is not executed for the target volume.
006/05/56516	A pair of Continuous Access Synchronous is defined.
006/05/56517	A pair of Business Copy or Fast Snap is defined.
006/05/58258	The operation cannot be performed due to one of the following reasons:\\n- All the paths to the external volume are blocked.\\n- No paths will be available if this operation is performed.
006/05/58263	No paths will be available, if you change the setting of paths.
006/05/5827	An error occurred during Remote Web Console processing.
006/05/5828	An error occurred during Remote Web Console processing.
006/05/58330	After executing the Disconnect External Storage Systems or the Disconnect External Volumes, neither the Reconnect External Paths nor the Disconnect External Paths can be executed.
006/05/58331	The specified External Path is not registered.
006/05/58332	The external volume is blocked.
006/05/58406	A pair of Continuous Access Journal is defined.
006/05/58407	A volume is defined as a journal volume of Continuous Access Journal.
006/05/58409	The cache mode cannot be changed when the Disconnect External Storage Systems or the Disconnect External Volume is in progress.
006/05/58410	The cache mode cannot be changed because the bind mode is set to the specified volume.
006/05/58622	The configuration of Pool VOL is defined.
006/05/58627	A Fast Snap pool volume is included in the items.
006/05/58905	The extended shared memory for External Storage is not installed.
006/05/6012	An error occurred during Remote Web Console processing.
006/05/6022	An error occurred during Remote Web Console processing.
006/05/6533	An error occurred during Remote Web Console processing.
006/05/6534	The number of external volumes that can be registered in the storage system has reached the maximum.
006/05/6535	The configuration cannot be changed because the LUN Path is remained in the target volume. 
006/05/6537	The setting process has not been executed because there is no error in this setting, but an error in the others settings. 
006/05/65740	The configuration changing processes are conflicting at DKC.
006/05/65791	The specified External Path Group is not mounted.
006/05/65792	The specified External Path Group has already been mounted.
006/05/65793	The specified External Path Group has already been used.
006/05/65794	The specified external volume is not mounted.
006/05/65795	The specified external volume has already been specified.
006/05/65796	The External Path Group specified as a migration source has already been used as a migration target.
006/05/65797	The External Path Group specified as a migration target has already been used as a migration source.
006/05/65798	The path configuration of the External Path Group between the migration source and the migration target is different.
006/05/65799	There are no setting lines of NewPathGroup.
006/05/65800	The number of NewPathGroup setting lines exceeds the limit.
006/05/65801	There are no setting lines of the ExG.
006/05/65802	There are no setting lines of TargetPathGroup.
006/05/66011	The number of external LUs that can be connected from a single port has exceeded the maximum value.
006/05/66012	The number of registered ports of the external storage system has exceeded the maximum.
006/05/66501	The number of LDEVs that can be defined in an external volume has exceeded the maximum value.
006/05/66502	Specified ExG has already been used.
006/05/66503	The LDKC, CU, and LDEV are not set within the available range.
006/05/66504	Specified LDKC:CU:LDEV has already been used.
006/05/66505	The specified LDEV number has already been assigned to another emulation group within the range grouped by 32 LDEV numbers.
006/05/66506	Specified SSID has already been used.
006/05/66507	The target external volume is blocked or not set within the range of capacity that can be used.
006/05/66508	The specified LDEV capacity is invalid.
006/05/66509	The total LDEV capacity defined in the external volume exceeds the external volume size.
006/05/66510	The specified emulation type cannot be used.
006/05/66512	Specified CLPR is not mounted.
006/05/66517	The target external volume has already been mapped or set for mapping.
006/05/66518	The External Path configuration of the target external volume is not corresponding to that of another external volume in the same External Path Group.
006/05/66568	Multiple operation tags are defined.
006/05/66675	The syntax of parameter is invalid.
006/05/66692	The volume in the local storage system cannot be operated.
006/05/66693	A correct parameter as a data transfer volume is not set.
006/05/66694	A correct parameter as RemoteCommandDevice is not set.
006/05/66697	The value entered as PathMode is outside the setting range.
006/05/66698	The number of alternate Path definitions that can be set to the external volume has exceeded the maximum.
006/05/66699	The number of LDEV definitions that can be set to the external volume has exceeded the maximum.
006/05/66702	The value of External Path Group is not set within the available range.
006/05/66705	Invalid port number.
006/05/66710	It is not set within the range where LUN can be used.
006/05/66713	The value of ExG is not set within the available range.
006/05/66715	Attribute is invalid.
006/05/66718	It is not set within the range where CLPR can be used.
006/05/66720	It is not emulation type that can be specified.
006/05/66722	CacheMode is invalid.
006/05/66724	InflowControl is invalid.
006/05/66736	It is not set within the range where LDKC can be used.
006/05/66739	It is not set within the range where CU can be used.
006/05/66742	It is not set within the range where LDEV can be used.
006/05/66744	It is not set within the range where LDEV capacity can be used.
006/05/66747	The value of SSID is not set within the available range.
006/05/66748	A value different from SSID that has already been set is specified. 
006/05/66749	The number of paths has reached the maximum number.
006/05/66750	The specified WWN is not registered.
006/05/66751	The specified WWN has already been specified.
006/05/66752	The specified external volume is a volume of the storage system that cannot be used as an external storage.
006/05/66798	Specified WWN was not found.
006/05/66799	Specified external volume was not found.
006/05/68733	The volumes registered in a Thin Provisioning Pool are included in the items to be maintained.
006/05/68741	Disconnect External Storage Systems or Disconnect External Volumes cannot be performed for one or more external volumes used as pool volumes. The pool to which those pool volumes were added is associated with THP V-VOLs in a normal status or with a deduplication system data volume in a normal status.
006/05/68742	Set the same cache mode to all the volumes that compose a Pool VOL.
006/05/68800	Volume migration or Quick Restore is in progress.
006/05/68871	The specified volumes include remote command devices being used with mirrors in the Journal of the Continuous Access Journal.
006/05/68884	Quorum disks are included in the items to be maintained.
006/05/68901	An external volume was not able to be recovered.
006/05/68902	The external volume was able to be restored, but some of mapping paths were not able to be restored normally.
006/05/68903	Failed to disconnect from the external volume.
006/05/77140	The operation cannot be performed because the device name or the virtual LDEV information differs between volumes of the migration source storage system and the migration target storage system.
006/05/77142	The operation cannot be performed because the multi-array virtualization function of the specified LDEV ID is enabled.
006/05/77143	The specified LDEV capacity is not valid.
006/05/77145	This function is not available. Online Migration is required.
006/05/78031	The specified MP Unit is blocked.
006/05/78032	The specified MP Unit is not mounted.
006/05/78047	Enough cache management devices cannot be allocated to the target volumes.
006/05/78048	An error occurred while accessing the user information.
006/05/78049	The port that is connected to the specified external volume belongs to a resource group that you do not have permission to access.
006/05/78050	The port that is connected to the specified external path belongs to a resource group that you do not have permission to access.
006/05/78051	The port that is connected to the specified external path group belongs to a resource group that you do not have permission to access.
006/05/78052	The port that is connected to the specified external WWN belongs to a resource group that you do not have permission to access.
006/05/78053	The specified external volume belongs to a resource group that you do not have permission to access.
006/05/78054	The specified external path contains an external volume in a resource group that you do not have permission to access.
006/05/78055	The specified external path group contains an external volume in a resource group that you do not have permission to access.
006/05/78056	The specified external WWN is used for an external volume in a resource group that you do not have permission to access.
006/05/78057	The specified LDEV belongs to a resource group that you do not have permission to access.
006/05/78058	The specified external volume contains an LDEV that belongs to a resource group that you do not have permission to access.
006/05/78060	The cache mode cannot be changed because the LDEV of the specified external volume is one of the following:\\n- The LDEV is a Pool VOL of a pool containing external and internal volumes.\\n- The LDEV is a Pool VOL of a pool for which the smart pool setting is enabled.
006/05/78064	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
006/05/78065	The storage system is in internal process, or a different user is changing the configuration.
006/05/78066	The load balance mode cannot be changed because the path mode of the specified external volume is "Single."
006/05/78282	The specified operation cannot be performed because the external volume mapped for the online data migration is reserved by the host.
006/05/8000	An error occurred during Remote Web Console processing.
006/05/8001	An error occurred during Remote Web Console processing.
006/05/8102	This function is not supported.
006/05/8122	Another maintenance processing is in progress.
006/05/8136	The command was rejected, because the licensed capacity has exceeded the maximum.
006/05/8958	An error occurred on the DKC side.
006/05/8966	An error occurred on the DKC side.
006/05/8979	The operation of the external volume has been failed because all the paths to the external volume are blocked.
006/21/109214	If you enable the use of internal volume, the local storage system and internal volumes are displayed as external storage. Are you sure you want to change the setting? 
006/22/105009	All the check boxes are cleared.
006/22/105040	[Detail] is clicked without selecting any row.
006/22/105042	[Delete] is clicked without selecting any row.
006/22/105084	The setting cannot be changed, because an invalid value has been input.
006/22/105204	A necessary program product is not installed, or insufficient permissions to execute editorial operation.
006/22/105234	A radio button is not selected.
006/22/105235	The operation cannot be done because no row is selected.
006/22/105236	The operation cannot be executed because no target item is selected.
006/22/105237	External path group creation has not finished yet.
006/22/105238	The parity group ID cannot be assigned due to either of the following reasons:\\n- The total number of external volumes and virtual volumes has reached the maximum.\\n- There are no available parity group IDs that are subsequent to the specified initial parity group ID.
006/22/105239	The number of alternate paths that can be set to an external volume exceeds the maximum.
006/22/105240	Failed to allocate an External Path Group ID.
006/22/105241	An external volume that can be added was not found by the result of Volume Discovery.
006/22/105242	An external volume is selected, where Volume Discovery executed ends with an error.
006/22/105244	The specified external volume cannot be set because the path configuration is different.
006/22/105245	The LDEV ID cannot be assigned.
006/22/105251	The external volume is not supported.
006/22/105255	Only one LDEV can be set because the attribute of the specified external volume is Remote Command Device.
006/22/105256	Only one LDEV can be set because the specified external volume is in the data transfer mode.
006/22/105257	LDEV Name cannot be set because the value is out of range.
006/22/105258	The path cannot be changed because there will be no normal path for the external volume.
006/22/105262	LDEV Name can not be registered because there is a volume that failed to be created as an external volume.
006/22/105265	Insufficient logical volumes to map the external volumes.
006/22/105266	Insufficient logical volumes to map the external volumes.
006/22/105267	The port that is connected to the specified external path belongs to a resource group that you do not have permission to access.
006/22/105268	The port that is connected to the specified external path group belongs to a resource group that you do not have permission to access.
006/22/105269	The specified external volume belongs to a resource group that you do not have permission to access.
006/22/105270	The specified external volume contains an LDEV that belongs to a resource group that you do not have permission to access.
006/22/105271	The port that is connected to the specified external WWN belongs to a resource group that you do not have permission to access.
006/22/105272	The specified external WWN is used for an external volume in a resource group that you do not have permission to access.
006/22/105273	The port that is connected to the specified external WWN belongs to a resource group that you do not have permission to access.
006/22/105274	The specified external WWN is used for an external volume in a resource group that you do not have permission to access.
006/22/105275	The specified external path contains an external volume in a resource group that you do not have permission to access.
006/22/105276	The port that is connected to the specified external path belongs to a resource group that you do not have permission to access.
006/22/105277	The specified external path contains an external volume in a resource group that you do not have permission to access.
006/22/105278	The port that is connected to the specified external volume belongs to a resource group that you do not have permission to access.
006/22/105461	No valid value is set to the item whose check box is checked.
006/22/106057	The cache mode cannot be enabled because a command device is set to an external volume.
006/22/106086	The processing cannot continue because the configuration having been set doesn't consist with the current configuration information.
006/22/106525	The specified external storage system does not exist in the configuration.
006/22/106526	The specified mapping path does not exist in the configuration.
006/22/106527	The specified external path group does not exist in the configuration.
006/22/106528	The specified WWN does not exist in the configuration.
006/22/106529	The specified external volume does not exist in the configuration.
006/22/106530	The specified parity group does not exist in the configuration.
006/22/106531	The specified LUN does not exist in the configuration.
006/22/106532	The specified LDEV does not exist in the configuration.
006/22/107001	The processing cannot continue due to an internal logic contradiction.
006/22/107002	The processing cannot continue due to an internal logic contradiction.
006/22/107003	The processing cannot continue due to an internal logic contradiction.
006/22/107004	The processing cannot continue due to an internal logic contradiction.
006/22/107005	The processing cannot continue due to an internal logic contradiction.
006/22/107018	The processing cannot continue due to an internal logic contradiction.
006/22/109016	The filter was set to the table because an external volume that could not be used was found as a result of Volume Discovery.
006/22/109020	External volume discovering succeeded.
006/22/205070	Necessary program products are not installed.
006/22/205149	Different types of external paths are selected.
006/22/205150	An external path connected to the iSCSI port is selected.
006/22/205151	An external path connected to the fibre port is selected.
006/22/205153	The port that is connected to the specified external storage system port belongs to a resource group that you do not have permission to access.
006/22/205154	The specified external storage system port is used for an external volume in a resource group that you do not have permission to access.
006/22/205184	LDEV names cannot be allocated to all specified LDEVs because the number of characters for LDEV names that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for an LDEV name.
006/22/205201	Data Direct Mapping cannot be enabled because the capacity of the external volumes does not satisfy the requirements for the pool volume.
006/22/209013	The selected external volumes contain pool volumes. If different volume types or cache modes are used in the same pool, the entire performance might be affected by the LDEVs with the lowest performance. In a Fast Snap pool, different cache modes cannot be used or cache modes cannot be disabled if internal and external volumes coexist. Do you want to continue this operation?
007/21/205008	A radio button for Transfer Protocol is not selected.
007/21/209016	Are you sure you want to download the Audit Log?
007/21/209017	Are you sure you want to send a test message based on the entered information in the window?
007/22/205042	The Primary Server and the Secondary Server have the same settings.
007/22/205043	The value you entered for the Port Number is not within the allowable range (1 to 65535).
007/22/205044	The value you entered for the Timout is not within the allowable range (1 to 120).
007/22/205045	The value you entered for the Retry Interval is not within the allowable range (1 to 60).
007/22/205046	The value you entered for the Number of Retries is not within the allowable range (1 to 50).
007/22/205047	The form of the Password is wrong.
007/22/205056	The client certificate for syslog transfer of the ({0}) is not uploaded.
007/22/205057	The root certificate for syslog transfer of the ({0}) is not uploaded.
007/22/209004	Audit Log downloading has started.
007/26/205000	The transmission to the {0} succeeded.
007/26/205001	The client certificate for syslog transfer of the correct {0} is not uploaded, or the password of the client certificate is invalid.
007/26/205002	The root certificate for syslog transfer of the correct {0} is not uploaded.
007/26/205003	Failed to connect to the {0}.
007/26/205004	Failed to connect to the {0} by TLS.
007/26/205005	Failed to authenticate {0}.
007/26/205006	Failed to send a test message to {0}.
007/26/205007	The client certificate or root certificate of the correct {0} is not uploaded, or a password of the Client Certificate is invalid.
007/26/205008	The IP address of the {0} is invalid.
007/26/207001	The client certificate upload for syslog transfer failed.
007/26/207002	The root certificate upload for syslog transfer failed.
007/26/207003	The setting of a certificate for syslog transfer failed.
007/26/207004	An error occurred during the syslog test transmission processing to a {0}.
007/26/207005	The acquisition of the client certificate for syslog transfer of the {0} failed.
007/26/207006	The acquisition of the root certificate for syslog transfer of the {0} failed.
008/10/65645	Enter up to 2,048 alphanumeric characters.
008/10/65646	Enter alphanumeric characters only.
010/05/1002	The specified volume cannot be set as a command device because it is used as a volume of Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN, Fast Snap, or High Availability.
010/05/1003	You are trying to set multiple paths to the same volume from one group.
010/05/1004	Multiple volumes are specified to a single port, group or LUN combination.
010/05/1005	The following volumes cannot be specified to change the path configuration:\\n- A volume that does not exist.\\n- A volume that is used by Auto LUN.
010/05/1007	The one and only normal path for the volume used by Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN, Fast Snap, or High Availability cannot be removed.
010/05/1009	An operation is specified for a volume that does not exist.
010/05/1010	An error occurred during Remote Web Console processing.
010/05/1018	The specified port does not exist. Or the specified port type is not Fibre port.
010/05/1020	Invalid LUN.
010/05/1021	The specified volume does not exist. 
010/05/1022	Invalid host mode.
010/05/1023	Invalid Fibre address.
010/05/1024	Invalid Fibre topology information.
010/05/1025	The specified LU path does not exist.
010/05/1059	LUN security setting has been made to a non-Fibre port. LUN security is a function of LUN Manager.
010/05/1061	Security Switch Off operation and path adding operation cannot be performed simultaneously.
010/05/1063	The specified WWN is already in use.
010/05/1064	You are trying to register the same WWN that is already registered.
010/05/1065	The specified host name or the host group name is already registered. (The host name and the host group name cannot be the same.)
010/05/1066	The unregistered WWN number is specified.  (When deleting or changing)
010/05/1067	You are trying to register the same host group number as the already registered one.
010/05/1068	The specified host group or iSCSI target is not registered.
010/05/1108	The following volume cannot be specified to change the command device configuration:\\n- A volume that is used by Auto LUN.
010/05/1110	Invalid characters are specified in the nickname to be used in HOST GROUP and WWN.
010/05/1111	When requesting a configuration change of LUN-Security, a nickname is not specified. Specify the nickname of HOST GROUP.
010/05/1116	When registering WWN, the value is not specified. Or, zero is set as the value of WWN. Be sure to set the WWN value before requesting the configuration change.
010/05/1123	Command device security cannot be set to the specified volume because the volume is not a command device.
010/05/1125	There are no host groups where the WWN will be registered.
010/05/1128	The specified channel speed cannot be set for the target channel board.
010/05/1130	You cannot specify the default nickname when setting the nickname of a host group or a host.
010/05/1131	Failed to set the host group because the number of host groups exceeds the maximum that can be set in a port.
010/05/1132	Failed to set the WWN because the number of WWNs exceeds the maximum that can be set in a port. 
010/05/1133	Failed to set the host mode because the number of host modes exceeds the maximum that can be set in a port.
010/05/1134	Failed to set the path because the number of paths exceeds the maximum that can be set in a port.
010/05/1135	When setting the port information (Fibre Address/Fibre Topology/Channel Speed), multiple change instructions are set to the same port.
010/05/1138	You specified same setting using LUNM operation.
010/05/1140	Because the Port Group setting is done, it is impossible to change.
010/05/1170	The volume cannot be configured as a command device because the volume does not have Read/Write attribute.
010/05/1174	The specified host ID is already registered.
010/05/1177	The specified host is already registered.
010/05/1178	An incorrect host name was specified.
010/05/1180	An error occurred during Remote Web Console processing.
010/05/1181	The specified path cannot be added, because the volume is used by a Remote Copy pair.
010/05/1194	The settings of the selected port cannot be changed because the port is connected to an external storage system.
010/05/1199	The path cannot be set to the specified volume because the volume is not an open-systems volume.
010/05/1350	A LUN path cannot be added because the selected port is connected to a remote storage system or an external storage system.
010/05/1352	The operation cannot be performed, because remote paths are set on the MCU port.
010/05/1353	The settings of the selected port cannot be changed because the port is connected to a remote storage system.
010/05/1354	A WWN cannot be added because the selected port is connected to a remote storage system or an external storage system.
010/05/1355	The host mode of the host group that is connected to a port of a remote storage system or an external storage system cannot be changed.
010/05/1356	A host group cannot be added because the selected port is connected to a remote storage system or an external storage system.
010/05/1357	The settings of the selected port cannot be changed because the port is connected to a remote storage system.
010/05/1361	The number of User LU settings exceeds the maximum.
010/05/1363	You cannot add paths to journal volumes.
010/05/1364	The port type is incorrect.
010/05/1367	The host mode "4C" is used for a host group connecting to volumes that cannot be used for External Storage.
010/05/1368	The host mode "4C" can only be used with External Storage volumes.
010/05/1369	The host mode options cannot be set because the selected port is connected to a remote storage system.
010/05/1600	This functionality is not available. Open System Array Management is required.
010/05/1601	This functionality is not available. Open System Array Management is required.
010/05/1904	The specified volume cannot be assigned as a command device, and the path of the volume cannot be set because it is being used as a Pool volume.
010/05/1906	The specified volume cannot be set as a command device because the volume is being used as a V-VOL for Fast Snap.
010/05/1912	The specified volume is a remote command device, and therefore the command device setting or the command device security setting cannot be set or released.
010/05/1918	The settings of the selected port cannot be changed because an external volume is mapped to the port.
010/05/1928	Paths cannot be added or deleted for LUN0, because Host Mode Option 60 is enabled. Also, changing the setting of Host Mode Option 60 and changing the path setting (addition or deletion) for LUN0 cannot be performed at the same time.
010/05/1929	Releasing the Host Mode Option 61 is disabled.
010/05/1930	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
010/05/1932	The path definition between the resources included in different Virtual Storage Machines cannot be performed.
010/05/1933	Releasing the Host Mode Option 72 is disabled.
010/05/2005	An error occurred during Remote Web Console processing.
010/05/2009	An error occurred during Remote Web Console processing.
010/05/2010	The LDEV is being used by the host, or an error occurred during Remote Web Console processing.
010/05/2013	An error occurred during Remote Web Console processing.
010/05/2015	An error occurred while connecting to the storage system.
010/05/203000	An unknown error was detected.
010/05/2032	An error occurred while connecting to the storage system.
010/05/205000	Paths cannot be added because the specified host group and LDEV belong to different Virtual Storage Machines.
010/05/205001	The path definition on the external volume that has the Online Migration attribute cannot be performed because the ID of the specified host group is 0 and the security switch of the specified port is off.
010/05/205002	The specified port does not exist. Or the specified port type is not the Fibre or iSCSI port.
010/05/205003	The Fibre port settings cannot be applied to the iSCSI port.
010/05/205004	Host Mode Option 51 cannot be set because the number of ports on which Host Mode Option 51 is set has reached the maximum.
010/05/205005	Host Mode Option 51 can be set for only one host group on a port.
010/05/205006	Characters or the number of characters for the iSCSI target name, iSCSI target alias, iSCSI name, or the nickname of the iSCSI name is not valid.
010/05/205007	An invalid user authentication is specified.
010/05/205008	The specified iSCSI target is not registered.
010/05/205009	The composition information operation failed.
010/05/205010	LU path information cannot be acquired.
010/05/205011	The mistake is found in the set parameter.
010/05/205012	The specified iSCSI name is not registered.
010/05/205013	No more iSCSI names can be added to the port because the number of iSCSI names has reached the maximum.
010/05/205014	The characters used for the user ID or the number of the characters of the user ID is invalid. \\nCheck the setting, and then retry the operation. 
010/05/205015	The secret is incorrect.
010/05/205016	The specified user name is already used on the same port.
010/05/205017	The specified user name is not registered.
010/05/205018	The CHAP user cannot be set because the user authentication of the iSCSI target is disabled.
010/05/205019	No more CHAP user IDs can be added to the port because the number of CHAP user IDs has reached the maximum.
010/05/205020	This port is not properly equipped.
010/05/205021	The target cannot be set because the number of targets exceeds. the maximum that can be set in a port.
010/05/205022	The specified iSCSI target name or target alias is already used on the same port.
010/05/205023	The specified iSCSI target name or target alias cannot be registered because it is reserved for iSCSI target #00.
010/05/205024	An error occurred while connecting to the storage system.
010/05/205025	The specified port is not an iSCSI port.
010/05/205026	The operation cannot be performed because RAID Manager is in process.
010/05/205027	The specified Host Name cannot be registered, because it is already used in this port.
010/05/205028	The operation cannot be performed because a resource group is not locked.
010/05/205029	The specified LDEV numbers are not valid.
010/05/205030	The status of the High Availability pair that uses the specified LDEV is not PSUS.
010/05/205031	The resource group to which the selected host groups or LDEVs belong is locked by a different user.
010/05/205032	The specified LDEVs do not exist.
010/05/205033	The operation cannot be performed because the number of host groups with LUN paths to LDEVs on which ALUA is enabled exceeds the maximum on the storage system.
010/05/205034	The user authentication cannot be performed.
010/05/205035	An error occurred on the storage system.
010/05/205036	No LUN paths are set to the selected host groups.
010/05/205037	The specified host group IDs are not valid.
010/05/205038	The specified host groups do not exist.
010/05/205039	The operation cannot be performed because the specified Asymmetric Access States is not supported.
010/05/205040	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
010/05/205041	The specified host groups or LDEVs cannot be used because you do not have permission to access a resource group to which the specified host groups or LDEVs belong.
010/05/205042	The operation cannot be performed because any blocked MP exists.
010/05/205043	The operation cannot be performed because different microcode versions coexist on the storage system.
010/05/205044	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
010/05/205045	The operation cannot be performed because the specified volume is an external volume with Data Direct Mapping enabled.
010/05/205046	The current DKCMAIN microcode version does not support the specified operation.
010/05/205047	No LUN paths can be created because the specified LDEVs belong to a parity group with capacity expansion enabled.
010/05/205050	LUN paths using LDEVs with T10 PI enabled cannot be added because T10 PI is disabled on the specified ports.
010/05/205051	The specified LDEVs cannot be operated because T10 PI is enabled.
010/05/205052	No SFP module that supports the specified channel speed is installed.
010/05/205100	The operation cannot be performed because the selected ports are virtual ones.
010/05/205101	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with resource group ID 1023 or LUN paths are set to the NAS platform (User LU).
010/05/205102	A LUN path to the LDEV that is set as a command device cannot be set to the specified port.
010/05/208001	The specified ports do not support T10 PI Mode.
010/05/208002	The operation cannot be performed because the storage system is in internal process, or a different user is changing the configuration.
010/05/208003	The specified port is blocked.
010/05/208004	The operation cannot be performed because the resource group to which the specified ports belong is used by a different user.
010/05/208005	The operation cannot be performed because the storage system requires maintenance, such as that the storage system is blocked, or that the shared memory is inconsistent.
010/05/208006	The operation cannot be performed because an error occurred on the storage system.
010/05/208007	The operation cannot be performed because the specified ports are not installed.
010/05/208008	The T10 PI mode cannot be disabled for all or some of the specified ports due to one of the following reasons.\\n- LUN paths are set between the specified ports and LDEVs with T10 PI enabled.\\n- LUN paths are set between different ports on the same channel board and LDEVs with T10 PI enabled.
010/05/208063	Host Mode Option 51 (Round Trip Set Up Option) cannot be set for the specified host group because the channel board of 16FC2 does not support Host Mode Option 51.
010/05/208065	The host mode option cannot be released because a path is defined on an LDEV that belongs to a different virtual storage machine from the one to which the specified host group belongs.
010/05/2082	Processing is disabled because the host is mounted or the device is reserved.
010/05/2083	The storage system status is invalid.
010/05/208393	Paths cannot be set, because deduplication system data volumes are specified.
010/05/208394	Command devices cannot be set, because deduplication system data volumes are specified.
010/05/2084	The storage system status is invalid.
010/05/208455	The LUN paths cannot be set, because the specified LDEVs are being deleted.
010/05/208548	The path definition between a host group and two or more LDEVs with the ALU attribute cannot be performed.
010/05/208549	The path cannot be removed because there is an LDEV with the ALU attribute, to which an LDEV with the SLU attribute is bound. 
010/05/2097	The host specified by the WWN is performing I/O operations.
010/05/2098	The operation cannot be performed, because the DKCMAIN firmware version does not match the Remote Web Console software version.
010/05/2099	The operation cannot be performed, because an inoperative MP exists.
010/05/2100	An error occurred while connecting to the storage system. The configuration may be inconsistent.
010/05/2501	The volume cannot be configured as a command device because the volume does not have Read/Write attribute.
010/05/3002	An error occurred during Remote Web Console processing.
010/05/3003	An error occurred during Remote Web Console processing.
010/05/3006	An error occurred during Remote Web Console processing.
010/05/3007	An error occurred during Remote Web Console processing.
010/05/5010	An error occurred during Remote Web Console processing.
010/05/5013	An error occurred during Remote Web Console processing.
010/05/5099	An error occurred during Remote Web Console processing.
010/05/55206	The configuration information being set does not match the current configuration information.
010/05/55500	An error occurred during Remote Web Console processing.
010/05/55553	The specified port is not a fibre port.
010/05/55554	The specified WWN is not registered.
010/05/55555	The value of the WWN is not specified or is set to zero.
010/05/55561	An error occurred during Remote Web Console processing.
010/05/55566	An error occurred during Remote Web Console processing.
010/05/55569	The specified Group-ID is already registered.
010/05/55571	The target cannot be set because the number of targets exceeds. the maximum that can be set in a port.
010/05/55574	The settings of the selected port cannot be changed because the port is connected to a remote storage system or an external storage system.
010/05/56301	An error occurred during Remote Web Console processing.
010/05/56302	An error occurred during Remote Web Console processing.
010/05/56303	An error occurred during Remote Web Console processing.
010/05/57101	An error occurred during Remote Web Console processing.
010/05/57102	An error occurred during Remote Web Console processing.
010/05/58572	An error occurred while connecting to the storage system.
010/05/58573	This function is not supported.
010/05/58574	An error occurred while connecting to the storage system.
010/05/58575	An error occurred while connecting to the storage system.
010/05/58576	A communication time-out error occurred in the storage system.
010/05/58593	The storage system has accepted the request normally, however the processing requires some time.
010/05/6000	An error occurred during Remote Web Console processing.
010/05/6012	An error occurred during Remote Web Console processing.
010/05/6023	File access error occurred.
010/05/6036	An error occurred during Remote Web Console processing.
010/05/6040	An error occurred during Remote Web Console processing.
010/05/6050	An error occurred during Remote Web Console processing.
010/05/6502	Processing in progress. 
010/05/65660	The Thin Provisioning volume is not associated with a pool.
010/05/7060	An error occurred during Remote Web Console processing.
010/05/7111	An error occurred during Remote Web Console processing.
010/05/7310	An unregistered error occurred.
010/05/75009	The selected WWN was registered in a host group.
010/05/75044	An error occurred on the DKC side.
010/05/75045	The setting process has not been executed because there is no error in this setting, but an error in the other settings.
010/05/76510	The specified port belongs to a resource group that you do not have permission to access.
010/05/76511	The specified host group belongs to a resource group that you do not have permission to access.
010/05/76512	The specified LDEV belongs to a resource group that you do not have permission to access.
010/05/8000	An error occurred during Remote Web Console processing.
010/05/8001	An error occurred while connecting to the storage system.
010/05/8002	An error occurred during Remote Web Console processing.
010/05/8100	An error occurred while connecting to the storage system.
010/05/8102	This function is not supported.
010/21/205005	The re-entered secret does not match the one entered previously.
010/21/209033	This operation causes the following to occur:\\n- The T10 PI Mode setting of the port and the paired port changes.\\n- I/O requests cannot be accepted.\\n- If T10 PI Mode is enabled, I/O performance degrades.
010/22/105009	All the check boxes are cleared.
010/22/105010	The host group name is not set.
010/22/105011	The number of characters specified in the host group name has exceed the maximum.
010/22/105012	Invalid characters are used in the specified host group name. You cannot use the following characters: \/:,;*?"<>|.  
010/22/105013	The specified host group name is already used by another host group, which is on the same port. 
010/22/105014	The default host group name cannot be used for the host group setting.
010/22/105016	Detail button pressing detection without line selection. 
010/22/105017	The Detail button pressing is detected by two or more-line selection. 
010/22/105018	Multiple host groups are selected on the same port.
010/22/105020	Hosts cannot be added because none of [Available Hosts] table rows is selected.
010/22/105021	No more HBA WWNs can be registered, because the number of registered HBA WWNs has reached the maximum. 
010/22/105022	The selected information cannot be added, because a duplicated HBA WWN is in the information being selected.  
010/22/105023	The selected information cannot be added because a duplicated host name is in the information being selected.
010/22/105024	The specified HBA WWN cannot be added because it is already used in the same port, or it exists in the [Selected Hosts] table.
010/22/105025	The specified host name cannot be added because it is already used in the same port, or it exists in the [Selected Hosts] table.
010/22/105026	The processing cannot be done because of no data in the [Selected Hosts] table.
010/22/105027	[Detail] is clicked in the state that no row is selected. 
010/22/105028	[Detail] is clicked in the state that multiple rows are selected.
010/22/105030	No more host groups can be added, because the number of registered host groups that can be added to the subject port has reached the maximum. 
010/22/105031	The host group cannot be added because no row is selected in any of the [Available Hosts] table and the [Available Ports] table.
010/22/105033	No more host groups can be added, because the number of registered hosts that can be added to the subject port has reached the maximum. 
010/22/105037	The specified name of the host group is incorrect.
010/22/105038	The default host group name cannot be used for the host group setting.
010/22/105040	[Detail] is clicked without selecting any row.
010/22/105041	[Detail] is clicked in the state of selecting multiple table rows.
010/22/105042	[Delete] is clicked without selecting any row.
010/22/105043	The processing cannot be done because there is no data in the [Selected Host Groups] table.
010/22/105044	[Detail] is clicked without selecting table rows.
010/22/105045	[Detail] is clicked in the state of selecting multiple table rows.
010/22/105046	HBA WWN cannot be converted into hexadecimal. 
010/22/105047	The length of the host name is incorrect. 
010/22/105048	An invalid character is used in the host name.
010/22/105049	You are trying to register the same host that has already existed as a candidate.
010/22/105050	The specified HBA WWN cannot be registered, because it is already used in this port.
010/22/105051	The specified Host Name cannot be registered, because it is already used in this port.
010/22/105052	There is no port information on the copy target.
010/22/105070	The same host is specified at the same time.
010/22/105072	The same host cannot be added in the same port.
010/22/105073	[Finish] is clicked without completing the setting.
010/22/105074	All the check boxes are being cleared. 
010/22/105075	The HBA WWN about to be changed has already existed in the same port. 
010/22/105076	The host name about to be changed has already existed in the same port.
010/22/105077	The specified port type is not Fibre Port.
010/22/105080	The attribute of the specified port cannot be changed.
010/22/105081	The setting cannot be changed because of the unsupported port speed.
010/22/105082	The specified port does not exist in the configuration.
010/22/105083	There is a radio button that is not selected.
010/22/105084	The setting cannot be changed, because an invalid value has been input.
010/22/105085	The setting cannot be changed, because the value of UUID is outside the range. 
010/22/105086	The input value of the starting LUN ID is outside the range.
010/22/105087	The LUN ID cannot be set, because the value is outside the range.
010/22/105088	The table column is not selected. 
010/22/105089	The number of LUNs that can be set to the specified port has exceeded the maximum. 
010/22/105090	The specified LDEV and an LDEV with LUN registered to the specified host group have the same ID.
010/22/105091	The number of selected host groups exceeds the maximum that can be operated at a time.
010/22/105094	The length of the HBA WWN is incorrect.
010/22/105204	The operation cannot be performed because the program product is not installed or you do not have permission to access.
010/22/105207	The number of LUNs that can be set to the specified port has exceeded the maximum.
010/22/105208	The specified host cannot be added because the HBA WWN or the host name is used in the same port, or, it is used in the item that has been moved in the [Selected Host Groups] table.
010/22/105209	The host mode is left blank.
010/22/105210	There are blank items in the Host Mode Options Table.
010/22/105277	Some LDEVs or Host Groups that are not available for LUN path setting are excluded from the choices.
010/22/105296	The specified port belongs to a resource group that you do not have permission to access.
010/22/105297	The specified host group or iSCSI target belongs to a resource group that you do not have permission to access.
010/22/105298	The specified LDEV belongs to a resource group that you do not have permission to access.
010/22/105304	The specified host group belongs to a resource group that you do not have permission to access.
010/22/105423	The operation cannot be executed because you have no editorial permission. 
010/22/105424	The specified LDEV cannot be used because you have no access right to a resource group to which the LDEV belongs. 
010/22/105425	Some LUN paths were excluded from the list because the LUN paths were defined to the host groups in the resource groups where you cannot access.
010/22/105505	The operation cannot be performed because the selected host group where LUN pass is not defined.
010/22/106501	The specified port does not exist in the configuration.
010/22/106502	The specified host group does not exist in the configuration.
010/22/106503	The process cannot be continued, because there is no necessary data for the configuration.
010/22/106504	No more host groups cannot be added to this port, because the number of hosts that can be set to the target port has reached the maximum. 
010/22/106505	No more host groups cannot be set, because the number of host groups that can be set to the port has reached the maximum.
010/22/106506	The specified LU does not exist in the configuration.
010/22/106510	The specified host does not exist in the configuration.
010/22/106511	The specified path does not exist in the configuration.
010/22/106514	The specified host does not exist in the configuration.
010/22/106519	The specified LDEV does not exist in the configuration.
010/22/106520	Failed to get the configuration information.
010/22/106523	The specified host group is not registered.
010/22/106524	The specified LDEV has no LU path.
010/22/106533	The configuration may have changed.
010/22/107001	The processing cannot continue due to an internal logic contradiction.
010/22/107002	The processing cannot continue due to an internal logic contradiction.
010/22/107003	The processing cannot continue due to an internal logic contradiction.
010/22/107004	The processing cannot continue due to an internal logic contradiction.
010/22/107005	The processing cannot continue due to an internal logic contradiction.
010/22/107006	The type of the specified port is not fibre port.
010/22/108003	The volume, which is allocated as LDEV in the target path information, is set as reserved by Data Retention. 
010/22/108004	The volume, which is allocated as LDEV in the path information that is set under the target host group, is set as reserved by Data Retention.
010/22/108005	There is a volume, which is set as reserved by Data Retention, in the target path information.
010/22/108006	The specified LDEV is a reserved volume of Data Retention.
010/22/108007	The specified LDEV is set other than the Read/Write (S-VOL enabled) of Data Retention.
010/22/108011	The specified LDEV is a journal volume of Continuous Access Journal.
010/22/108012	The specified LDEV is a pool volume.
010/22/108013	The specified LDEV is a V-VOL.
010/22/108014	The specified LDEV is a remote command device.
010/22/108016	The specified LDEV is a reserved volume of Data Retention.
010/22/108027	An error occurred.
010/22/108028	An error occurred.
010/22/108034	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
010/22/109201	When you switched the host mode option 33 from Enabled to Disabled, access to an LU where a UUID is allocated is disabled. 
010/22/109202	When you switched the host mode option 33 from Disabled to Enabled, access to LU where UUID is not allocated is disabled. 
010/22/109203	Consecutive LUN IDs could not be assigned from the specified number. However, unused LUN IDs after the specified number were assigned.
010/22/205019	FC-AL cannot be selected as the connection type for ports whose speed is 16 Gbps.
010/22/205053	The operation cannot be performed because LDEVs that belong to different virtual storage machines are selected.
010/22/205054	The virtual storage machine to which the selected host groups or iSCSI targets belong is different from the one to which the LDEVs selected in the previous window belong.
010/22/205055	LDEVs whose virtual model types or serial numbers are different cannot coexist in the same host group.
010/22/205058	A host group cannot be created. To create a host group, the following conditions are required.\\n- A host group ID that is not assigned to any host group exists for a resource group that you have permission to access.\\n- The number of host groups assigned to one port does not reach the maximum.
010/22/205105	The selected HBA iSCSI names have already been added to the [Selected Hosts] table.
010/22/205106	The selected information cannot be added, because a duplicated HBA iSCSI name is in the information being selected.  
010/22/205107	The setting items of IPv6 are specified, but the check box of IPv6 Mode is cleared.
010/22/205108	The setting items of iSNS Server are specified, but the check box of iSNS Server is cleared.
010/22/205140	Multiple iSCSI targets are selected on the same port.
010/22/205141	No more HBA iSCSI names can be registered because the number of registered HBA iSCSI names has reached the maximum. 
010/22/205142	The entered HBA iSCSI name already exists in the same iSCSI target.
010/22/205143	The LDEV specified on the previous window and an LDEV whose LUN is registered to the specified iSCSI target have the same ID.
010/22/205144	The number of selected iSCSI targets exceeds the maximum that can be operated at a time.
010/22/205145	The specified host group or iSCSI target belongs to a resource group that you do not have permission to access.
010/22/205146	LUN paths cannot be added because host groups that belong to different virtual storage machines are selected.
010/22/205164	The operation cannot be performed because the selected host groups belong to "NAS_Platform_System_RSG" with the resource group ID 1023.
010/22/205165	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with the resource group ID 1023.
010/22/205166	The operation cannot be performed because the selected ports are virtual ones.
010/22/205167	To delete LUN paths of the NAS Platform (User LU), all mapped paths must be deleted.
010/22/205179	The operation cannot be performed because LUN paths to NAS platforms are assigned to the selected LDEVs.
010/22/205188	UUIDs cannot be allocated to all specified LUNs because the number of characters for UUIDs that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for a UUID.
010/22/205202	The operation cannot be performed because the selected LDEV is an external volume with Data Direct Mapping enabled.
010/22/205203	The specified or associated ports belong to resource groups that you do not have permission to access.
010/22/205204	The operation cannot be executed, because the specified logical volume is not a Smart Tiers volume.
010/22/205207	The operation cannot be performed because capacity expansion is enabled on the selected LDEV.
010/22/205209	With NAS Platform (User LU) for the port type, only host group 0 can be operated.
010/22/205220	The operation cannot be performed, because one or more deduplication system data volumes are specified.
010/22/205230	FC-AL cannot be selected as the connection type for ports whose speed is 32 Gbps.
010/22/206001	The re-entered secret does not match the one entered previously.
010/22/206288	The operation cannot be performed because the fibre port is not installed.
010/22/206294	The specified ports do not support T10 PI Mode.
010/22/206295	The specified LDEVs cannot be operated because T10 PI is enabled.
010/22/206517	Invalid port type.
010/22/206518	Invalid port type.
010/22/206519	Invalid port type.
010/22/206521	The specified iSCSI target does not exist in the configuration.
010/22/206522	The specified iSCSI target is not registered.
010/22/208004	The volume that is assigned as an LDEV in the path information of the specified host group or iSCSI target is reserved by Data Retention.
012/05/205000	The Ethernet MTU size is not valid.
012/05/205001	The VLAN tagging mode is not valid.
012/05/205002	The VLAN ID is not valid.
012/05/205003	A network address, a loopback address, a broadcast address, or an address whose first segment is 255 cannot be specified for the IPv4 IP address.
012/05/205004	The IPv6 mode is not valid.
012/05/205005	The IPv6 link local address is not valid.
012/05/205006	The IPv6 link local address is not valid.
012/05/205007	The IP address set for Global Address 1 or Global Address 2 is not correct.
012/05/205008	A multicast or loopback address cannot be set for Global Address 1 of IPv6.
012/05/205009	A multicast address or a loopback address cannot be specified for the IPv6 default gateway.
012/05/205010	The TCP port number is not valid.
012/05/205011	The selective ACK is not valid.
012/05/205012	The delayed ACK is not valid.
012/05/205013	The maximum window size is not valid.
012/05/205014	The entered keep alive timer is not valid.
012/05/205015	The iSNS server is not valid.
012/05/205016	The IP address of the iSNS server is not valid.
012/05/205017	The entered IP address of the iSNS server is not valid because of the following:\\n - A loopback address, a broadcast address, or an address whose first segment is 255 cannot be specified for the IPv4 IP address.\\n - An unspecified address, a multicast address, or a loopback address cannot be specified for the IPv6 address.
012/05/205018	The TCP port number of the iSNS server is not valid.
012/05/205019	To disable the IPv6 setting, it is required to remove all remote paths to avoid a remote replication error.
012/05/205020	The same IPv6 address cannot be specified on the same port.
012/05/205021	The VLAN tagging mode cannot be set because the VLAN ID is not entered.
012/05/205022	The specified port belongs to a resource group that you do not have permission to access.
012/05/205023	The configuration information cannot be updated on the storage system.
012/05/205024	The entered VLAN ID is already registered.
012/05/205025	A VLAN ID is already set on the specified iSCSI port.
012/05/205026	The setting of Subnet Mask for IPv4 is not valid.
012/05/205027	An error occurred on the storage system.
012/05/205028	The specified iSCSI target is already added.
012/05/205029	The specified iSCSI target does not exist.
012/05/205030	The following symbols and spaces cannot be used for iSCSI Target Name:\\n! " # $ % & ' ( ) = ~ ^ | \ ` @ { } [ ] ; + * < > , ? / _
012/05/205031	The following symbols cannot be used for CHAP User Name or Secret:\\n! " # $ % & ' ( ) ^ | \ ` { } ; * < > , ?
012/05/205032	No more iSCSI paths or remote paths using iSCSI can be added because the total of iSCSI paths and remote paths using iSCSI reaches the maximum that can be added to the storage system.
012/05/205033	The operation cannot be performed because the processing of iSCSI Targets Discovery to be simultaneously performed reaches the maximum.
012/05/205034	The test login to the iSCSI target cannot be performed.
012/05/205035	The operation cannot be performed because the number of login tests of iSCSI targets simultaneously performed reaches the maximum.
012/05/205036	The operation cannot be performed because the specified port is not an iSCSI port.
012/05/205037	The operation cannot be performed because the storage system is in internal process, or a different user is changing the configuration.
012/05/205038	The operation cannot be performed because the resource group that the specified iSCSI port, host group, or the LDEV is belongs to is locked by a different user.
012/05/205039	The operation cannot be performed because the storage system requires maintenance, such as that the storage system is blocked, or that the shared memory is inconsistent.
012/05/205040	No more iSCSI paths or remote paths can be added to the specified port because the total of iSCSI paths and remote paths using iSCSI reaches the maximum that can be added to a port.
012/05/205041	The specified iSCSI port or iSCSI path cannot be edited or deleted because it is used for an external path.
012/05/205042	Discover iSCSI Targets cannot be performed.
012/05/205043	The selected iSCSI path cannot be edited because it is used as a remote path.
012/05/205044	The specified ports, iSCSI targets, or host groups cannot be used because you do not have permission to access a resource group to which they belong.
012/05/205045	The current DKCMAIN microcode version does not support the specified operation.
012/05/205046	The following addresses cannot be specified for the IP address: a network address, a broadcast address, a multicast address, a loopback address, and an address consisting of all zeros (0).
012/05/205052	In the current DKCMAIN firmware version, an IPv6 address cannot be set for Global Address 2.
012/05/205053	Global Address 2 cannot be set because Global Address 1 is not set.
012/05/205054	A multicast or loopback address cannot be set for Global Address 2 of IPv6.
012/05/205055	The settings of the specified port cannot be changed, because the iSCSI virtual port mode is enabled.
012/05/205056	The operation cannot be performed due to one of the following reasons:\\n- An iSCSI port for which the iSCSI virtual port mode is disabled is specified.\\n- The current DKCMAIN firmware version does not support virtualization of iSCSI ports.
012/05/205057	The operation cannot be performed, because the specified virtual port does not exist.
012/05/205058	The iSCSI path cannot be added due to one of the following reasons:\\n- The specified iSCSI target is already set on a different virtual port of the specified iSCSI port.\\n- The same iSCSI target is specified for multiple virtual ports of an iSCSI port.
012/05/207001	An error occurred during processing.
012/05/208000	The storage system has accepted the request normally, but the processing requires some time.
012/05/56299	The I/O operation with the host connected via iSCSI is in progress.
012/05/57099	Some entries are not valid.
012/05/58388	The CHB for iSCSI is not mounted.
012/05/58390	The firmware exchange is in progress on the storage system.
012/05/58391	The specified port is blocked.
012/05/6012	An error occurred during SVP processing.
012/05/6023	The SVP is busy.
012/05/6502	An error occurred on the storage system.
012/05/6537	The setting cannot be applied because there is an error in a different setting.
012/05/7060	An internal logic contradiction occurred.
012/05/7111	The SVP is busy.
012/05/7310	An unregistered error occurred.
012/05/8000	An unexpected error occurred on the external module.
012/05/8001	A communication time-out error occurred.
012/05/8002	A communication error occurred.
012/05/8100	An error occurred during communication with the storage system.
012/05/8102	The specified function is not supported.
012/05/8890	The specified port is being initialized.
012/21/105001	No table rows are selected.
012/21/105003	No table row, or two or more table rows are selected.
012/21/105007	No table row is selected.
012/21/109001	Are you sure you want to remove the selected rows?
012/21/209024	If this operation is performed while a host I/O is running, the I/O operation to the specified iSCSI target will end abnormally. To avoid this, stop the host I/O operation first, and then perform the operation. Do you want to continue this operation?
012/21/209025	If this operation is performed while a host I/O is running, the I/O operation from the host that uses the specified CHAP user will end abnormally. To avoid this, stop the host I/O operation first, and then perform the operation. Do you want to continue this operation?
012/21/209026	If this operation is performed while a host I/O is running, the I/O operation from the specified host will end abnormally. To avoid this, stop the host I/O operation first, and then perform the operation. Do you want to continue this operation?
012/21/209027	If any of the following is changed while a host I/O is running, the I/O operation to the specified iSCSI target will end abnormally:\\n- iSCSI target name\\n- Host mode\\n- Authentication Method\\n- Mutual CHAP\\n- CHAP user name\\n- Secret\\nDo you want to continue this operation?
012/21/209029	If any of the following is changed while a host I/O is running, the I/O operation to the selected iSCSI path will end abnormally. Do you want to continue this operation?\\n- Authentication Method\\n- Mutual CHAP\\n- CHAP User Name\\n- Secret
012/21/209030	No more discovery targets can be added because the number of rows reaches the maximum.
012/22/107001	The processing cannot continue due to an internal logic contradiction.
012/22/107002	The processing cannot continue due to an internal logic contradiction.
012/22/107003	The processing cannot continue due to an internal logic contradiction.
012/22/107004	The processing cannot continue due to an internal logic contradiction.
012/22/107005	The processing cannot continue due to an internal logic contradiction.
012/22/206196	The number of characters for the iSCSI target alias is not valid.
012/22/206197	The number of characters for the user name is not valid.
012/22/206199	The operation cannot be performed because there is no available iSCSI target ID on the selected port.
012/22/206200	No more CHAP users can be added to the specified iSCSI target because the number of CHAP users has reached the maximum.
012/22/206201	No more CHAP users can be added to the specified iSCSI target because the number of CHAP users has reached the maximum.
012/22/206202	No more iSCSI targets can be added to the port because the number of iSCSI targets has reached the maximum.
012/22/206203	No more hosts can be added to the port because the number of hosts has reached the maximum.
012/22/206204	No more CHAP users can be added to the port because the number of CHAP users has reached the maximum.
012/22/206205	The default iSCSI target alias cannot be used for the specified iSCSI target.
012/22/206206	The specified iSCSI target alias is already used by a different iSCSI target on the same port.
012/22/206207	The default iSCSI target name cannot be used for the specified iSCSI target.
012/22/206208	The specified iSCSI target name is already used by a different iSCSI target on the same port.
012/22/206209	There are some hosts that cannot be added because the same HBA iSCSI name is used for them.
012/22/206210	There are some hosts that cannot be added because the same host name is used for them.
012/22/206211	The selected host cannot be added because the host name is already used on the same port, or used for the item that has been moved to the [Selected iSCSI Targets] table.
012/22/206212	The selected host cannot be added because the HBA iSCSI name is already used on the same port, or used for the item that has been moved to the [Selected iSCSI Targets] table.
012/22/206213	The selected CHAP users cannot be added because the same user name is used for them.
012/22/206214	The selected CHAP user cannot be added because the user name is already used on the same port, or used for the item that has been moved to the [Selected iSCSI Targets] table.
012/22/206215	The specified user name is already used on the same port.
012/22/206216	The specified user name is already used or reserved.
012/22/206217	The specified combination of the user name and secret is already used.
012/22/206218	The specified user name is already used by a different iSCSI target on the same port.
012/22/206219	The operation cannot be performed because a host group is selected.
012/22/206220	The operation cannot be performed because a host other than that of the iSCSI port is selected.
012/22/206221	The re-entered secret does not match the one entered previously.
012/22/206222	The operation cannot be performed because no target CHAP user is assigned to the selected iSCSI target.
012/22/206223	It is required to enter the user name and secret because Mutual CHAP is set to Enable.
012/22/206224	It is required to set the user name and secret at the same time.
012/22/206225	The target CHAP user cannot be removed because Mutual CHAP of the selected iSCSI target is set to Enable.
012/22/206226	The iSCSI target, to which the specified host belongs, belongs to a resource group that you do not have permission to access.
012/22/206227	The specified LDEV belongs to a resource group that you do not have permission to access.
012/22/206228	The specified LDEV is a reserved volume of Data Retention.
012/22/206229	The settings are applied, but they are not effective until the security switch is turned on.
012/22/206230	There is a blank item in the Host Mode Options Table.
012/22/206231	The LU, to which no UUID is assigned, will not be accessible if Host Mode Option 33 is switched from Disabled to Enabled.
012/22/206232	The LU, to which a UUID is assigned, will not be accessible if Host Mode Option 33 is switched from Enabled to Disabled.
012/22/206233	4C is specified for the host mode of the specified iSCSI target. However, the iSCSI target is connected to a volume that cannot be used for External Storage.
012/22/206234	The multicast address format cannot be specified for the IP address.
012/22/206235	The operation cannot be performed because the iSCSI port is not installed.
012/22/206236	The iSCSI target to which the specified CHAP user is assigned belongs to a resource group that you do not have permission to access.
012/22/206237	iSCSI targets were created, but an error occurred during the CHAP user setting.
012/22/206238	iSCSI targets were created, but an error occurred during the setting of the host.
012/22/206239	No more iSCSI targets can be added to the specified port because the number of iSCSI targets has reached the maximum.
012/22/206240	An iSCSI target cannot be created. To create an iSCSI target, the following conditions are required.\\n- An iSCSI target ID that is not assigned to any iSCSI target exists for a resource group that you have permission to access.\\n- The number of iSCSI targets assigned to one port does not reach the maximum.
012/22/206241	If Authentication Method is set to None, all of the assigned CHAP users will be removed. Do you want to continue this operation?
012/22/206242	A CHAP user cannot be added because the selected iSCSI targets include an iSCSI target whose Authentication Method is set to None.
012/22/206243	A CHAP user cannot be added because the selected iSCSI targets include an iSCSI target whose Authentication Method is set to None.
012/22/206244	No available CHAP users table rows are selected.
012/22/206245	The selected iSCSI targets include an iSCSI target to which no CHAP user is assigned. Even if Authentication Method is set to CHAP, the user authentication of the iSCSI target, to which no CHAP user is assigned, cannot be performed.
012/22/206246	The selected iSCSI targets cannot be allocated to LDEVs because the iSCSI targets have different virtual storage machines.
012/22/206266	The selected port belongs to a resource group that you do not have permission to access.
012/22/206267	The selected port cannot be removed because the CHAP user name is not set.
012/22/206268	The selected port cannot be removed because the CHAP user name is not set.
012/22/206269	The selected port cannot be removed because an iSCSI path with CHAP authentication is registered in that port.
012/22/206270	The selected port cannot be removed because it is not an iSCSI port.
012/22/206271	The selected port cannot be removed because it is not an iSCSI port.
012/22/206272	The selected port cannot be removed because it is used as an external path for External Storage.
012/22/206273	The specified discovery target cannot be added to the Discovery List because the same discovery target exists in the list.
012/22/206274	The operation cannot be performed because there is no iSCSI port that belongs to a resource group with permission to access.
012/22/206275	No more iSCSI paths can be added because the number of iSCSI paths exceeds the maximum for registration.
012/22/206276	The entered IP address is not valid.
012/22/206277	The user name and secret cannot be edited because the authentication method is not set to CHAP.
012/22/206278	The user name and secret are not entered.
012/22/206279	Either the user name or secret is entered.
012/22/206512	The specified port does not exist in the configuration.
012/22/206513	The specified iSCSI target does not exist in the configuration.
012/22/206514	The specified host does not exist in the configuration.
012/22/206515	The specified CHAP user does not exist in the configuration.
012/22/206524	The selected iSCSI path does not exist in the configuration.
012/22/209010	Are you sure you want to start the test login to the iSCSI target?
012/22/209011	The test login to the iSCSI target succeeds.
013/10/55601	The specified time out period is invalid.
013/10/55602	The specified authentication interval is invalid.
013/10/55603	The specified number of times of authentication is invalid.
013/10/5832	The user name is incorrect.
013/10/5833	The secret is incorrect.
013/10/5834	The reentered secret does not match the previously entered secret.
013/10/5836	The user name or the secret has not been changed.
013/10/9366	If a host is connected, the connection will be disconnected. Do you want to continue?
020/05/1021	The specified volume does not exist. 
020/05/1599	This functionality is not available. Open Volume Management \\nor LUN Manager is required.
020/05/1600	This functionality is not available. Open System Array Management is required.
020/05/1601	This functionality is not available. Open System Array Management is required.
020/05/1931	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
020/05/2083	The storage system status is invalid.
020/05/2084	The storage system status is invalid.
020/05/65660	The Thin Provisioning volume is not associated with a pool.
020/05/65704	The Thin Provisioning volumes are not associated with the same pool.
020/05/76512	The specified LDEV belongs to a resource group that you do not have permission to access.
030/05/106105	The operation cannot be executed because the specified pool has no monitoring data.
030/05/106107	The operation cannot be executed because there is only one tier in the specified pool.
030/05/107100	This function cannot be used because the encryption function is not supported.
030/05/107101	The specified operation cannot be performed because the SAS controller is blocked.
030/05/107102	The encryption environmental settings are performed repeatedly.
030/05/107103	This function is not available. DKA Encryption is required.
030/05/108100	A parameter error occurred on the storage system.
030/05/108102	The number of created keys exceeds the maximum.
030/05/108103	The key cannot be deleted.
030/05/108104	There are not enough free keys.
030/05/108106	Some blocked parts exist because an error occurred on the DKC side.
030/05/108107	Some blocked parts exist because an error occurred on the DKC side.
030/05/108108	An error occurred on the DKC side. A parity group that is not blocked is included in the specified parity groups.
030/05/108109	An error occurred on the DKC side. The encryption environmental settings cannot be initialized because there is an encrypted parity group.
030/05/108110	An error occurred on the DKC side during the encryption environmental settings.
030/05/108111	Some blocked parts exist because an error occurred on the DKC side during the encryption environmental settings.
030/05/108112	The specified operation cannot be performed because the SAS controller is blocked.
030/05/108113	An error occurred during Remote Web Console processing.
030/05/1910	The specified volume contains a Fast Snap pair.
030/05/1911	The specified volume contains Pool-VOLs. 
030/05/2011	The status of the storage system requires maintenance (for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
030/05/2015	An error occurred while connecting to the storage system.
030/05/202001	The LDEV cannot be formatted because one of the following maintenance operations is in progress.\\n- LDEV formatting\\n- Correction copy\\n- Drive copy\\n- CHB status change\\n- Cache status change\\n- PCIe channel board status change\\n- OEM Drive microcode replacement\\n- LDEV Shredding
030/05/202002	The LDEV cannot be restored because one of the following maintenance operations is in progress.\\n- LDEV formatting\\n- Correction copy\\n- Drive copy\\n- CHB status change\\n- Cache status change\\n- PCIe channel board status change\\n- OEM Drive microcode replacement\\n- LDEV Shredding
030/05/202003	The LDEVs cannot be formatted because Verify LDEVs is in process.
030/05/202004	The LDEVs cannot be restored because Verify LDEVs is in process.
030/05/202005	The LDEV cannot be formatted because the storage system is in the state where a maintenance operation is required (such as blockage or shared memory inconsistency).
030/05/202006	The LDEV cannot be restored because the storage system is in the state where a maintenance operation is required (such as blockage or shared memory inconsistency).
030/05/206000	A file open error has occurred.
030/05/206001	File access error occurred.
030/05/208000	An invalid relocation speed was specified.
030/05/208001	The tier with heavy I/O load exists in the monitoring pool.
030/05/208002	The zero page reclamation cannot be performed because the specified Thin Provisioning virtual volume is used as a journal volume.
030/05/208003	The capacity of the specified Thin Provisioning virtual volume cannot be expanded because the journal volume configuration is changing.
030/05/208004	The encryption cannot be enabled on the specified parity groups because the capacity expansion is enabled.
030/05/208006	To use a pool with the Smart Tiers function enabled, it is required to install the additional shared memory.
030/05/208007	The specified operation cannot be performed because Verify LDEVs is in process.
030/05/208021	The operation cannot be performed because a Thin Provisioning volume exists in the specified pool.
030/05/208022	The operation cannot be performed because the pool does not have enough free space for Data Direct Mapping.
030/05/208023	The specified volume cannot be added to any pool other than Thin Provisioning pools because its attribute is Data Direct Mapped .
030/05/208024	The emulation type of the specified volume is not OPEN-V.
030/05/208025	A pool with Data Direct Mapping enabled cannot be created because all of the selected volumes have the Data Direct Mapped attribute.
030/05/208026	The operation cannot be performed because the attribute of the specified volume is Data Direct Mapped.
030/05/208027	The operation cannot be performed because the specified pools have volumes with the Data Direct Mapped attribute.
030/05/208028	Data Direct Mapping cannot be enabled because the value of Warning Threshold or Depletion Threshold is not set to 100.
030/05/208029	The values of Warning Threshold and Depletion Threshold cannot be changed on the specified pool with the Date Direct Mapped attribute.
030/05/208030	The tiering policy name contains characters that are not valid.
030/05/208040	The specified volume is currently used by High Availability.
030/05/208041	Quick Format cannot be performed because the selected parity groups contain pool volumes.
030/05/208050	The interruption process cannot be done because the formatting was completed.
030/05/208061	The following cannot be set for the specified pool, because it is not a Thin Provisioning pool of an open system:\\n- Protect V-VOLs when I/O fails to Blocked Pool VOL\\n- Protect V-VOLs when I/O fails to Full Pool\\n- Suspend FS pairs when depletion threshold is exceeded
030/05/208062	The following cannot be set for a pool because Data Retention Utility is not installed:\\n- Protect V-VOLs when I/O fails to Blocked Pool VOL\\n- Protect V-VOLs when I/O fails to Full Pool
030/05/208110	The specified volume cannot be set as a pool volume because the RAID level is not supported.
030/05/208115	Page Reservation cannot be enabled for some THP V-VOLs.
030/05/208116	The setting processing of Page Reservation has not been performed because an error occurred during the processing.
030/05/208117	Full Allocation cannot be enabled for the specified THP V-VOL because the pool is in shrinking operation.
030/05/208118	Full Allocation cannot be enabled for the specified THP V-VOL because the emulation type is not supported.
030/05/208121	The operation cannot be performed because the specified LDEV contains a journal volume.
030/05/208122	The operation cannot be performed because the specified LDEV contains a pool volume of Fast Snap.
030/05/208123	The operation cannot be performed because a THP V-VOL that is not blocked is included in the THP V-VOLs associated with the pool to which the pool volume in the specified LDEV belongs.
030/05/208127	The specified operation cannot be performed because parity group formatting has not been performed on the target parity groups.
030/05/208128	The operation cannot be performed because the installed firmware does not support Real Time Smart Tier.
030/05/208129	Real Time Smart Tier cannot be enabled because the pool volume does not contain an LDEV whose drive type is SSD.
030/05/208130	The specified LDEVs cannot be deleted from the Smart (Real Time Smart Tier) pool that requires to contain at least one LDEV as a pool volume whose drive type is SSD.
030/05/208131	Quick Format cannot be performed because the specified volumes contain volumes that belong to parity groups with capacity expansion enabled.
030/05/208153	The specified LDEV cannot be operated because LUN paths are set to host groups on which Host Mode Option 97 is enabled.
030/05/208154	LDEVs that belong to a parity group with capacity expansion enabled cannot be added because the specified pool contains THP V-VOLs with Page Allocation enabled.
030/05/208155	No pool can be created or expanded because the specified LDEVs belong to a parity group that is used by a different pool and is in capacity expansion.
030/05/208156	Page Allocation cannot be enabled because a pool to which the specified THP V-VOLs belong contains pool volumes with capacity expansion enabled.
030/05/208200	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
030/05/208300	The operation cannot be performed, because deduplication system data volumes are specified.
030/05/208315	The operation cannot be performed, because deduplication system data volumes are allocated to the specified pools.
030/05/208376	The LDEV cannot be formatted, because the specified deduplication system data volume is not blocked.
030/05/208377	Multiple deduplication system data volumes cannot be formatted at the same time.
030/05/208378	LDEV formatting cannot be performed for the specified THP V-VOLs whose capacity saving setting is enabled, because the deduplication system data volumes for the pools with which the specified THP V-VOLs are associated are blocked.
030/05/208379	The LDEVs cannot be formatted, because both deduplication system data volumes and LDEVs that are not deduplication system data volumes are specified.
030/05/208380	LDEV formatting cannot be performed for the specified THP V-VOLs whose capacity saving setting is Deduplication and Compression, because the deduplication system data volumes for the pools with which the specified THP V-VOLs are associated are blocked.
030/05/208381	The specified LDEVs cannot be formatted, because the capacity saving status of at least one LDEV is "Failed".
030/05/208382	The operation cannot be performed, because THP V-VOLs whose capacity saving status is not Disabled are selected.
030/05/208383	The LDEVs cannot be shredded, because deduplication system data volumes are specified.
030/05/208384	Zero pages cannot be reclaimed, because deduplication system data volumes are specified.
030/05/208386	Full Allocation cannot be enabled, because deduplication system data volumes are specified.
030/05/208401	The selected deduplication system data volume cannot be formatted, because some THP V-VOLs that are associated with the pool and for which Deduplication Data shows Enabled are not blocked.
030/05/208402	Shared memory is being initialized.
030/05/208403	The selected deduplication system data volume cannot be formatted.\\nTHP V-VOLs that are associated with the pool of the selected deduplication system data volume and for which Deduplication Data shows Enabled are used in one of the following pairs.\\n- Business Copy pairs\\n- Fast Snap pairs\\n- Auto LUN pairs\\n- Continuous Access Synchronous pairs\\n- Continuous Access Journal pairs\\n- High Availability pairs
030/05/208404	The smart pool setting cannot be enabled for a Thin Provisioning pool with which a deduplication system data volume is associated.
030/05/208410	The operation cannot be performed, because a deduplication system data volume is allocated to the specified pool.
030/05/208411	The operation cannot be performed, because the selected pool is associated with THP V-VOLs whose capacity saving status is not Disabled.
030/05/208456	The specified LDEVs cannot be restored, because the LDEVs are being deleted.
030/05/208457	The selected LDEVs cannot be expanded, because they are being deleted.
030/05/208461	The pool edit operation cannot be performed due to one of the following reasons:\\n- Enable is selected for Smart Pool for the Thin Provisioning pools that contain Fast Snap pairs.\\n- Enable is selected for Data Direct Mapping for the Thin Provisioning pools that contain Fast Snap pairs.
030/05/208462	Yes cannot be selected for Suspend FS pairs when depletion threshold is exceeded, because the used capacity of the specified Thin Provisioning pools exceeds the depletion threshold.
030/05/208464	The operation cannot be performed, because Fast Snap pairs exist in the pool to which the selected pool volumes or external volumes belong.
030/05/208465	The operation cannot be performed, because Fast Snap pairs and THP V-VOLs whose LDEV status is Normal exist in the pool to which the selected pool volumes or external volumes belong.
030/05/208466	The operation cannot be performed, because Fast Snap pairs exist in the selected Thin Provisioning pool.
030/05/208467	The operation cannot be performed, because one of the following settings is specified for a pool for which Yes is selected for "Suspend FS pairs when depletion threshold is exceeded":\\n- Enable is selected for Smart Pool.\\n- Enable is selected for Data Direct Mapping.
030/05/2085	Copying is in progress for a pair of Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN , or Fast Snap.
030/05/2086	The configuration of Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN, or Fast Snap has been defined.
030/05/2088	The Remote Copy pair is suspended.
030/05/2089	The corresponding CHB might contain the last path between the MCU and RCU of Continuous Access Synchronous or Continuous Access Journal.
030/05/2090	Business Copy or Fast Snap setting exists. 
030/05/2091	The backup server of Business Copy or Fast Snap is running.
030/05/2092	Some pairs of Business Copy or Fast Snap exist. 
030/05/2093	Some pairs of Business Copy or Fast Snap exist. 
030/05/2094	Some pairs of Business Copy or Fast Snap exist. 
030/05/2095	The operation cannot be performed because one of the following maintenance operations is in progress.\\n- LDEV formatting\\n- Correction copy\\n- Drive copy\\n- CHB status change\\n- Cache status change\\n- PCIe channel board status change\\n- OEM Drive microcode replacement\\n- LDEV Shredding
030/05/2201	Processing cannot be performed because of Data Retention settings.
030/05/2204	Devices to be maintained include journal volumes.
030/05/2205	Devices to be maintained include journal volumes.
030/05/2511	The restore operation has been failed, because the specified LDEV was not shredded or formatted.
030/05/2512	The restore operation has been failed, because the system cannot access the specified LDEV.
030/05/2515	A Continuous Access Synchronous pair or a Continuous Access Journal pair is defined. 
030/05/2516	A Continuous Access Synchronous pair or a Continuous Access Journal pair is defined. 
030/05/2517	The target volume is defined as a pair volume of Business Copy or Fast Snap.
030/05/2518	A pair of Business Copy or Fast Snap is defined. 
030/05/2520	A Auto LUN pair is defined.
030/05/2521	An Auto LUN pair is defined.
030/05/3003	An error occurred during Remote Web Console processing.
030/05/5010	An error occurred during Remote Web Console processing.
030/05/5013	An error occurred during Remote Web Console processing.
030/05/5099	An error occurred during Remote Web Console processing.
030/05/55505	The operation cannot be performed because the CLPR that is specified to migrate the selected pool volume is different from a CLPR to which other pool volumes in the same pool belong.
030/05/55507	The specified volume is used as a command device.
030/05/55510	An error occurred during Remote Web Console processing.
030/05/55512	The specified volume is an external volume.
030/05/55513	The selected volume is used as a virtual volume of Fast Snap.
030/05/55514	The specified volume is not configured.
030/05/55516	This function is not available, because the program product is not installed.
030/05/55517	The specified volume is used as a Pool-VOL.
030/05/55519	The specified pool does not exist.
030/05/55594	An error occurred during Remote Web Console processing.
030/05/56301	An error occurred during Remote Web Console processing.
030/05/56302	An error occurred during Remote Web Console processing.
030/05/56303	An error occurred during Remote Web Console processing.
030/05/57101	An error occurred during Remote Web Console processing.
030/05/57102	An error occurred during Remote Web Console processing.
030/05/58460	The logical volume cannot be registered, because it is not installed.
030/05/58461	The specified operation cannot be done, because the logical volume is blocked.
030/05/58462	The logical volume cannot be registered, because it is defined as a Pool-VOL.
030/05/58463	The specified logical volume cannot be registered, because the CLPR number of the volume does not match the number of the logical volume already registered to the Pool.
030/05/58464	The specified logical volume cannot be registered, because it is a V-VOL.
030/05/58465	The volume set as a Command Device cannot be set as a component of a Pool-VOL.
030/05/58466	The specified logical volume cannot be registered, because a LUN path is set to the logical volume.
030/05/58467	The operation cannot be performed because one of the following licenses is not installed or any licensed capacity is not enough.\\n- Thin Provisioning\\n- Smart Tiers\\n- Real Time Smart Tier\\n- Fast Snap
030/05/58469	The specified logical volume is being used by another program product.
030/05/58470	The operation cannot be performed because the usage of the specified pool is 100% (full).
030/05/58471	The shared memory for the V-VOL management area is insufficient.
030/05/58472	The pool information cannot be acquired because pool information is not acquired when:\\n- The virtual volume management area is not initialized.\\n- The virtual volume management area is not installed.
030/05/58473	An error occurred when setting the Pool.
030/05/58474	The specified operation cannot be performed because there is not enough memory available on the shared memory for the V-VOL management area.
030/05/58475	The PCB for fibre port is not installed.
030/05/58491	A communication time-out error occurred in the storage system.
030/05/58570	The V-VOL management area is being used.
030/05/58571	The specified operation cannot be executed because the Pool-VOL is not mounted.
030/05/58572	An error occurred while communicating with the storage system.
030/05/58573	This function is not supported.
030/05/58574	An error occurred while connecting to the storage system.
030/05/58575	An error occurred while connecting to the storage system.
030/05/58576	A communication time-out error occurred in the storage system.
030/05/58578	An error occurred on the storage system. The configuration might not be consistent.
030/05/58623	The specified operation cannot be performed because the Fast Snap pair using the pool volumes to be maintained is in PSUS status or being restored.
030/05/58626	A Fast Snap pair is defined.
030/05/58706	An error occurred during Remote Web Console processing.
030/05/5874	The program product required for using the shredding function is not installed.
030/05/5875	The specified volume is formatting or shredding.
030/05/6000	An error occurred during Remote Web Console processing.
030/05/6012	An error occurred during Remote Web Console processing.
030/05/6022	An error occurred during Remote Web Console processing.
030/05/6023	An error occurred during Remote Web Console processing.
030/05/6024	An error occurred during Remote Web Console processing.
030/05/6036	An error occurred during Remote Web Console processing.
030/05/6050	An error occurred during Remote Web Console processing.
030/05/6533	An error occurred during Remote Web Console processing.
030/05/6537	There is an error in another setting and the setting processing has not been executed.
030/05/65659	The specified volume is used as a Thin Provisioning volume.
030/05/65671	The pool volumes associated with the Thin Provisioning volume is included in the items to be maintained.
030/05/65675	The LDEV to be operated is not included in the specified parity group.
030/05/65676	The association cannot be made because the pool is in a different CLPR.
030/05/65688	A failure occurred while formatting.
030/05/65689	A failure occurred while quick formatting.
030/05/65690	The specified volumes contain volumes that are being quick formatted.
030/05/65691	Preparing for quick format.
030/05/65692	The specified volumes contain volumes that quick format cannot be executed.
030/05/65694	The specified quick formatting operation cannot be performed, because the total number of either of the following parity groups exceeds the maximum for quick formatting.\\n- Parity groups containing LDEVs that are in quick formatting operations\\n- Parity groups containing LDEVs that are blocked during quick formatting operations.
030/05/65695	An error occurred during Remote Web Console processing.
030/05/65717	The specified volumes contain volumes that cannot be formatted.
030/05/65740	The configuration changing processes are conflicting at DKC.
030/05/65767	The specified volumes contain a quorum disk.
030/05/65790	The specified volume includes a remote command device being used by a mirror of the journal group.
030/05/68722	The specified volume is not a Thin Provisioning volume.
030/05/68723	An internal logic contradiction occurred on the DKC side.
030/05/68724	Shared memory is not installed.
030/05/68725	The shared memory for the V-VOL management area is insufficient.
030/05/68726	The capacity of THP V-VOL is insufficient.
030/05/68727	Shared memory is being initialized.
030/05/68728	The pool is in an abnormal state.
030/05/68729	LDEV format is being executed in the specified volume.
030/05/68736	An error occurred during Remote Web Console processing.
030/05/68748	The number of Thin Provisioning volumes that can be associated with a single pool exceeds the maximum.
030/05/68751	The storage system is releasing the association internally.
030/05/68761	An error occurred on the DKC side.
030/05/68785	A parity group that is not mounted is included in the specified parity groups.
030/05/68786	A parity group that is not blocked is included in the specified parity groups.
030/05/68797	The pool cannot be restored because pools are not restored when:\\n- The restore processing is taking time because there are blocked parts on the storage system.\\n- One or more pool volume is blocked.
030/05/68798	Failed to delete the pool. A pool cannot be deleted when:\\n- The V-VOL management area is not initialized.\\n- The V-VOL management area is not installed.\\n- A Fast Snap pair still remains in the pool.\\n- A P-VOL still remains in the pool.\\n- A Pool-VOL in the pool is blocked.\\n- The process to delete a Thin Provisioning volume is in operation.
030/05/68799	Failed to change the threshold of the pool.\\nThe threshold of the pool cannot be changed when: \\n- the threshold is set below the usage rate of the pool.\\n- the pool is shrinking.\\n- the Pool-VOL in the pool is blocked.
030/05/68818	The pool is blocked.
030/05/68819	The specified volume cannot be processed because it is blocked.
030/05/68820	The specified volume cannot be processed, because it is not associated with a pool.
030/05/68821	The specified volume is currently used by Business Copy.
030/05/68822	The specified volume is currently used by Fast Snap.
030/05/68823	The specified volume is currently used by Auto LUN or Online Migration.
030/05/68824	The specified volume is currently used by Continuous Access Synchronous.
030/05/68825	The specified volume is currently used by Continuous Access Journal.
030/05/68884	The specified volumes contain a quorum disk.
030/05/68885	The specified volumes contain a High Availability pair volume.
030/05/68886	The specified volumes contain a High Availability pair volume.
030/05/68892	The item to be formatted includes a THP V-VOL. However, the THP V-VOL cannot be formatted because there is a pool that has been blocked.
030/05/68898	The zero page reclaiming is disabled on the storage system.
030/05/7060	An error occurred during Remote Web Console processing.
030/05/7111	An error occurred during Remote Web Console processing.
030/05/7310	An error occurred during Remote Web Console processing.
030/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
030/05/75042	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
030/05/75046	The specified volume is invalid.
030/05/75047	The number of the specified page ranges is invalid.
030/05/75048	The number of pages is invalid.
030/05/76509	The specified LDEV or parity group belongs to a resource group that you do not have permission to access.
030/05/76517	The specified operation cannot be performed because there is an LDEV that has been set to a different resource group.
030/05/78005	The specified operation cannot be executed, because the LDEV capacity exceeds the maximum reserved pool capacity.
030/05/78006	The specified LDEV capacity is invalid.
030/05/78007	Failed to expand the V-VOLs, because it took time for the processing. 
030/05/78008	The specified LDEV capacity exceeds the threshold. 
030/05/78009	You cannot expand the V-VOLs for the volumes that are being used in the following program products:\\n- Business Copy\\n- Fast Snap\\n- Auto LUN\\n- Continuous Access Synchronous\\n- Continuous Access Journal\\n- High Availability
030/05/78010	The specified operation cannot be executed, because the maximum reserved pool capacity is incorrect.
030/05/78011	The specified operation cannot be executed, because the pool status is invalid.
030/05/78012	The specified operation cannot be executed, because the threshold of the pool exceeds the maximum.
030/05/78013	The specified operation cannot be executed, because it exceeds the maximum reserved pool capacity.
030/05/78014	The operation cannot be performed because the specified logical volume is a quorum disk.
030/05/78015	The operation cannot be executed, because RAID levels of the specified logical volumes do not match. 
030/05/78016	The operation cannot be executed, because a blocked pool volume exists in the pool to which the specified logical volume is to be added. 
030/05/78017	The operation cannot be executed, because the specified logical volume is the top pool volume.
030/05/78018	The operation cannot be executed, because the number of tiers of the specified logical volume is incorrect.
030/05/78019	The operation cannot be performed because Smart Tiers is disabled for the pool associated with the specified THP-VOLs.
030/05/78020	The operation cannot be performed because the available period to stop shrinking pools has passed.
030/05/78027	The frequency distribution data cannot be obtained because it is not complete.
030/05/78028	The frequency distribution data cannot be obtained. There is no monitoring information of the specified pool or THP V-VOL.
030/05/78029	The frequency distribution data cannot be obtained. There is no monitoring information of the specified THP V-VOL because it is created after collecting monitoring information of a pool.
030/05/78030	The frequency distribution data cannot be obtained. There is no monitoring information of the specified THP V-VOL because one of the following is performed:\\n- Quick Restore of Business Copy\\n- Auto LUN\\n- Initial copy of Continuous Access Synchronous\\n- Initial copy of High Availability
030/05/78031	The specified MP Unit has been blocked.
030/05/78032	The selected MP unit is not mounted.
030/05/78034	The specified POOL ID or the LDEV ID does not exist.
030/05/78035	The frequency distribution data cannot be obtained. There is no monitoring information of the specified THP V-VOL because the shared memory for collecting monitoring information is depleted.
030/05/78036	The specified operation cannot be performed due to the following reasons:\\n - The specified logical volume is not blocked.
030/05/78037	The pool is blocked.
030/05/78038	Smart Tiers is disabled for the specified pool or a pool associated with the specified THP-VOL.
030/05/78039	The DKC is set to the state of suppression of pool shrinking.
030/05/78040	The DKC is set to the state of suppression of tier relocation starting.
030/05/78041	The operation cannot be executed because the specified pool is now in zero page reclaiming process.
030/05/78042	The operation cannot be executed because the pool where the Thin Provisioning Volume belongs to is now in pool shrinking or tier relocation process.
030/05/78043	The operation cannot be executed because the specified pool has following problems.\\n- The pool usage exceeds the threshold.\\n- The pool status is invalid.
030/05/78044	The operation cannot be executed because the specified pool has one of the following problems.\\n- The status of the specified Pool-VOL is not normal.\\n- The I/O load of the THP V-VOLs associated with the specified pool is high.
030/05/78045	The operation cannot be performed because the THP V-VOL or the Fast Snap pair of the specified pool has one of the following problems.\\n- The THP V-VOL is blocked.\\n- The THP V-VOL is being formatted.\\n- The Fast Snap pair is being deleted.
030/05/78046	The storage system requires maintenance (the cache memory is blocked, or the pool is in the pool shrinking suppression status.)
030/05/78047	A sufficient Cache Control Device cannot be allocated to the target volume.
030/05/78048	The pool shrinking was aborted because the operation to stop pool shrinking was executed.
030/05/78049	The operation cannot be executed because the storage system is in the process of shutting down. 
030/05/78052	The operation cannot be executed because the specified pool is in the process of pool shrinking.
030/05/78053	The operation failed because the specified resource was not installed.
030/05/78054	The operation failed because the specified name was already registered.
030/05/78059	A pool volume cannot be set to the specified pool because the number of drive types exceeds the supported number. 
030/05/78060	The multi tier pool cannot be disabled because the RAID level of each tier is different.
030/05/78061	Failed to delete the pool. Pools cannot be deleted when they are in the following status:\\n- Deleting a pair of Fast Snap is in progress.\\n- Deleting a volume of Thin Provisioning is in progress.
030/05/78062	Failed to delete the pool. Pools cannot be deleted when they are in the following status:\\n- Pairs of Fast Snap are remaining.\\n- Volumes of Thin Provisioning are remaining.
030/05/78063	The pool cannot be deleted because pools are not deleted when any pool volume of the specified pool is being formatted.
030/05/78064	Failed to delete the pool volume because the specified pool volume had one of the following problems.\\n- It is not a pool volume.\\n- The pool volume is not set to the specified pool.
030/05/78065	The LDEV ID of the specified pool volume is invalid.
030/05/78067	The maintenance operation cannot be performed on the specified THP V-VOLs because the THP V-VOLs include blocked pool volumes.
030/05/78075	The software does not support the specified operation.
030/05/78076	The operation cannot be done because the specified V-VOL is online from an EAV unsupported OS. 
030/05/78107	An internal volume and an external volume cannot be set as pool VOLs in the specified pool.
030/05/78111	External volumes with mixed cache mode setting, enabled and disabled, cannot be used as pool volumes in a THP pool.
030/05/78112	External volumes with cache mode disabled cannot be specified as pool volumes for the pool.
030/05/78113	The pools cannot be initialized due to one of the following reasons:\\n- The THP V-VOL is used by a different program product.\\n- There is a Fast Snap pair on the storage system.
030/05/78114	The operation failed, because the start of tier relocation operation was specified for a pool in tier relocation operation, or the stop of tier relocation operation was specified for a pool not in tier relocation operation.
030/05/78115	The operation cannot be done because the specified pool is using monitoring information for the tier relocation.
030/05/78116	The processing cannot continue due to an internal logical contradiction.
030/05/78134	All the pool volumes cannot be deleted at the same time.
030/05/78136	The specified LDEV cannot be set as a pool volume because it is used as an external volume that is mapped for the online data migration.
030/05/78192	The setting value of Smart Tiers is not valid.
030/05/78193	The execution mode cannot be changed because the storage system is preparing to execute performance monitoring.
030/05/78197	The operation cannot be performed because the additional shared memory is  being installed.
030/05/78198	The specified page range is invalid.
030/05/78199	The specified page tiering level of the tiering policy is invalid.
030/05/78200	The processing of the subject page failed because an error occurs in a different page processing.
030/05/78264	The operation cannot be performed because monitoring information is being changed.
030/05/78266	The specified pool is not a Thin Provisioning pool.
030/05/78267	The specified volume is an internal volume.
030/05/78268	The operation cannot be performed due to one of the following reasons:\\n- The specified volume is not a pool volume.\\n- The specified pool volume is not set to the specified pool.
030/05/78269	The specified pool ID is invalid.
030/05/78283	The tiering policy ID or the threshold value is invalid.
030/05/78284	The specified volume cannot be set as a Pool-VOL because the volume capacity does not satisfy the requirements for the Pool-VOL.
030/05/78286	The storage system configuration does not comply with the tiering policy.
030/05/78287	The number of the specified tiering policies is invalid.
030/05/78288	The specified tiering policies cannot be changed because the current DKCMAIN microcode version does not support the setting for the tiering policy name and for values of Tier 1 and Tier 3 in 1% increments.
030/05/78295	The operation failed because the required capacity of cache control device cannot be allocated.
030/05/78296	A Fast Snap pool cannot be created because there are not enough resources depending on cache management devices.
030/05/78305	The operation cannot be performed because the pool volume with a system area is blocked.
030/05/8000	An error occurred during Remote Web Console processing.
030/05/8001	A communication time-out error occurred in the storage system.
030/05/8002	An error occurred during SVP processing.
030/05/8100	An error occurred while connecting to the storage system.
030/05/8102	This function is not supported.
030/05/87777	The operation cannot be performed because a resource group is not locked.
030/05/8971	An error occurred while connecting to the storage system.
030/05/8979	The operation of the external volume has been failed because all the paths to the external volume are blocked.
030/22/105132	Short of {0} LDEV ID(s).
030/22/105133	The processing cannot continue due to an internal logic contradiction.
030/22/105134	The specified LDEV does not exist in the configuration.
030/22/105135	The selected LDEV has an LUN path setting.
030/22/105136	The specified LDEV is a pool volume.
030/22/105137	The selected LDEV has an LDEV Security setting.
030/22/105140	The specified LDEV is a remote command device.
030/22/105141	The selected LDEV has been set as a journal volume.
030/22/105143	The selected LDEV has an access attribute setting.
030/22/105146	The target LDEV is not associated with a pool.
030/22/105147	The target LDEV is blocked.
030/22/105148	The combo box is not selected.
030/22/105149	An error occurred while accessing the user information.
030/22/105150	Select a table.
030/22/105151	The processing cannot continue due to an internal logic contradiction.
030/22/105152	An LDEV in Normal or Quick Formatting status is selected.
030/22/105153	The specified value is outside the range.
030/22/105154	0 cannot be specified.
030/22/105155	A value other than the numerical value is specified.
030/22/105156	The processing cannot continue due to an internal logical contradiction.
030/22/105159	Multiple rows are selected.
030/22/105161	LDEVs with different RAID levels are selected.
030/22/105162	LDEV names cannot be allocated to all the selected LDEVs with the specified numerical value of the Initial Number.
030/22/105163	Insufficient free space to create LDEV.
030/22/105165	LDEVs with different RAID levels are selected.
030/22/105166	No more volumes can be created because the free space of the specified parity group is insufficient or the number of LDEVs that can be set has already reached the maximum.
030/22/105168	The selected parity group has no LDEV ID to specify.
030/22/105169	Data in the table is not selected.
030/22/105170	A different parity group is selected.
030/22/105171	The processing cannot continue due to an internal logic contradiction.
030/22/105173	All the check boxes are being cleared. 
030/22/105174	The number of characters for the LDEV name exceeds the maximum (32 characters).
030/22/105175	An invalid character was specified in the LDEV name.
030/22/105176	A value other than the numerical value was entered in the initial number.
030/22/105177	The specified initial number exceeds nine digits.
030/22/105178	An unblocked LDEV is selected for the target LDEV to be operated.
030/22/105179	An LDEV in Normal or Quick Formatting status is selected.
030/22/105181	Quick formatting cannot be performed, because the number of parity groups exceeds the maximum.
030/22/105184	Quick formatting cannot be performed because the number of parity groups exceeds 72.
030/22/105185	Pools of different types are specified.
030/22/105186	No more V-VOLs can be added to the selected pool.
030/22/105187	A pool in the abnormal state is selected.
030/22/105188	There is no LDEV ID that can be set in the selected pool.
030/22/105189	An LDEV cannot be added because the free space in the selected pool is insufficient.
030/22/105191	LDEV that has already been set has been selected. 
030/22/105192	LDEV not set has been selected. 
030/22/105193	The number of data patterns exceeds the setting range.
030/22/105194	An error occurred or an interruption request was made while formatting.
030/22/105195	An error occurred while preparing the quick format.
030/22/105205	Any further, the Pool that selects it cannot set the volume. 
030/22/105231	An error occurred in the shredding processing.
030/22/105248	The processing cannot continue due to an internal logical contradiction.
030/22/105249	The LDEV cannot be created in the parity group that is specified in Parity Group Selection because the parity group applies to either of the following:\\n(1) There is not enough free space to create an LDEV or the number of LDEVs that are already created reaches the maximum in the parity group.\\n(2) An LDEV is already being created in the parity group.
030/22/105250	Two or more Basic exists together to External. 
030/22/105259	There is no output file.
030/22/105263	An LDEV that the Snapshot is set has been selected.
030/22/105267	Volumes that can be shredded in the selected volumes will be displayed.
030/22/105270	The selected status will be canceled because the number of free spaces that exist in the selected parity group exceeds the number that can be set.
030/22/105271	The number of free spaces that exist in the selected parity group exceeds the number of volumes that can be set.
030/22/105272	Data Output cannot be set more than 3.
030/22/105273	The interruption process cannot be done because there is an unexecuted specified task.
030/22/105274	The interruption processing was completed.
030/22/105275	With the current setting, the number of parity groups exceeds the maximum for a quick formatting operation.
030/22/105280	This functionality is not available. \\nOpen Volume Management is required.
030/22/105281	There is no LDEV that can be formatted. 
030/22/105299	The specified LDEV cannot be used because the user has no access right to a resource group to which the LDEV belongs.
030/22/105300	The specified parity group cannot be used because the user has no access right to a resource group to which the parity group belongs.
030/22/105301	The operation cannot be done because the parity group which belongs to a resource group to which the user has no access right includes the specified LDEV.
030/22/105302	The operation cannot be done because the specified parity group contains the LDEV that belongs to a resource group to which the user has no access right.
030/22/105308	The operation cannot be done because the specified THP V-VOL is included in the pool that belongs to a resource group to which the user has no access right.
030/22/105309	The specified pool cannot be used because the user has no access right to a resource group to which the pool belongs. 
030/22/105313	An LDEV cannot be created because the free space that is available to set has already been registered in the task.  
030/22/105314	In the selected parity group, there is an area where LDEV cannot be made by default. 
030/22/105436	The LDEV that is not in the state of Normal or Quick Formatting is chosen.
030/22/105437	The parity group to be operated contains LDEVs that are not blocked.
030/22/105438	The specified parity group contains a volume on which the access attribute is set.
030/22/105439	The parity group to be operated contains LDEVs where Pool-VOLs are set. 
030/22/105440	The parity group to be operated contains LDEVs where journal volumes are set. 
030/22/105445	The selected LDEV is an external volume that is mapped for online data migration.
030/22/105446	The selected parity group contains an external volume that is mapped for online data migration.
030/22/105447	The specified capacity is larger than the selected free area.
030/22/105448	No more LDEVs can be created because the selected free area is too small.
030/22/105449	No more LDEVs can be created.
030/22/105450	A parity group in which no more LDEVs can be created is included in the selected free area.
030/22/105451	There are no usable LDEV IDs.
030/22/105452	The number of virtual volumes that can be registered in the storage system has reached the maximum. 
030/22/105453	There are not enough usable LDEV IDs in the selected free area.
030/22/105454	LDEVs cannot be created in all the free areas.
030/22/105455	LDEVs cannot be created because there is not enough free area in the pool.
030/22/105456	No more LDEVs can be created in the selected area.
030/22/105458	A volume for which the tier relocation is disabled is included.
030/22/105459	A radio button is not selected.
030/22/107002	The processing cannot continue due to an internal logic contradiction.
030/22/205014	A parity group to be operated contains LDEVs that are remote command devices.
030/22/205015	A parity group to be operated contains LDEVs that are not in Normal or Quick Formatting status.
030/22/205016	No LDEVs that can be shredded.
030/22/205017	No LDEVs that can be restored.
030/22/205018	No LDEVs that can be blocked.
030/22/205068	A LUN path cannot be added because models and serial numbers of different virtual storage machines coexist.
030/22/205071	Quick formatting will have an impact on the host I/O performance. Do you want to continue this operation?
030/22/205094	A pool volume belongs to the parity group to be formatted.
030/22/205095	The volume to be formatted contains a pool volume.
030/22/205096	The volume to be restored contains a virtual volume (DP-VOL).
030/22/205101	The specified operation cannot be performed because formatting is not in process.
030/22/205102	The specified operation cannot be performed because shredding is not in process.
030/22/205103	No LDEVs for force restoration in the selected parity groups.
030/22/205122	The specified parity group contains a volume on which the access attribute is set.
030/22/205123	An error occurred during communication with the storage system. The displayed resource information may not be the latest.
030/22/205124	The operation cannot be performed because the selected parity group has no LDEV.
030/22/205125	The operation cannot be performed because External is selected.
030/22/205126	No LDEVs for verification in the selected parity groups.
030/22/205127	17 or more table rows are selected.
030/22/205128	The selected parity groups include volumes that are not normal volumes.
030/22/205129	The selected volume is not a normal volume.
030/22/205130	The selected parity groups do not contain LDEVs that are in the Normal or Quick Formatting status.
030/22/205131	The selected parity groups contain LDEVs that are in neither the Normal nor Quick Formatting status, and these LDEVs will not be verified.
030/22/205139	The selected parity group contains a blocked volume.
030/22/205146	The LDEV cannot be created in the parity group that is specified in Parity Group Selection because the parity group applies to either of the following:\\n(1) There is not enough free space to create an LDEV or the number of LDEVs that are already created reaches the maximum in the parity group.\\n(2) An LDEV is already being created in the parity group.
030/22/205155	No ALU ID is assigned to the selected LDEV. Even though the LDEV might be being deleted, it is selectable on the window.
030/22/205156	No SLU ID is assigned to the selected LDEV. Even though the LDEV might be being deleted, it is selectable on the window.
030/22/205157	The selected LDEV cannot be shredded because the ALU attribute is set on it.
030/22/205158	A volume whose attribute is not ALU or SLU is included in the selected LDEVs.
030/22/205163	LDEV names cannot be allocated to all specified LDEVs because the number of characters for LDEV names that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for an LDEV name.
030/22/205164	The number of LDEVs with the ALU attribute that can be added to the storage system has reached the maximum.
030/22/205176	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with the resource group ID 1023.
030/22/205177	The operation cannot be performed because the LDEVs that belong to the selected parity group belong to "NAS_Platform_System_RSG" with the resource group ID 1023.
030/22/205198	The specified parity groups contain volumes with the capacity expansion enabled.
030/22/205199	The capacity expansion is enabled on the specified LDEVs.
030/22/205200	There is not enough free space to create LDEVs.
030/22/205203	Pools with Data Direct Mapping enabled and disabled coexist.
030/22/205204	Parity groups with Data Direct Mapping enabled and disabled coexist.
030/22/205205	There is no pool volumes that can be set as a DP-VOL in the selected pool.
030/22/205207	The operation cannot be executed, because the specified logical volume is not a Smart Tiers volume.
030/22/205211	The operation can be forcibly continued by ignoring the errors described in the following list.
030/22/205217	The full allocation setting and the capacity saving setting cannot be enabled at the same time.
030/22/205218	The operation cannot be performed, because the capacity saving status of the specified THP V-VOLs is not Disabled.
030/22/205219	The operation cannot be performed, because the capacity saving status of the specified THP V-VOLs is not Disabled.
030/22/205220	The operation cannot be performed, because one or more deduplication system data volumes are specified.
030/22/205221	LDEV formatting cannot be performed for THP V-VOLs whose capacity saving setting is Deduplication and Compression, because the deduplication system data volumes for the pools with which the specified THP V-VOLs are associated are blocked.
030/22/205222	The selected THP V-VOLs cannot be formatted, because the capacity saving status of at least one THP V-VOL is Failed.
030/22/205223	The operation cannot be performed, because the capacity saving status of the specified THP V-VOLs is not Disabled.
030/22/205224	The user does not have permission to perform this operation.
030/22/205225	The specified deduplication system data volume cannot be formatted, because some of the THP V-VOLs, which are associated with the pool of the deduplication system data volume, and for which Deduplication Data shows Enabled, are not blocked.
030/22/205226	Multiple deduplication system data volumes cannot be formatted at the same time.
030/22/205227	The LDEVs cannot be formatted, because both deduplication system data volumes and LDEVs that are not deduplication system data volumes are specified.
030/22/205229	The specified LDEVs include LDEVs whose capacity saving status is Deleting Volume.
030/22/205230	LDEVs whose capacity saving status is Deleting Volume are associated with the pool with which the specified deduplication system data volume is associated.
030/22/205231	The specified LDEV cannot be deleted, because the deduplication system data volume in the pool with which the specified LDEV is associated is blocked.
030/22/205232	The operation cannot be performed, because the specified LDEV is in a state in which the capacity saving setting cannot be changed.
030/22/205233	The specified LDEV cannot be deleted, because the capacity saving status of the LDEV is Rehydrating.
030/22/205234	The selected THP V-VOLs cannot be deleted.
030/22/205235	THP V-VOLs cannot be deleted.
030/22/205236	An internal error occurred.
030/22/205237	Processing to delete THP V-VOLs was interrupted because a format operation was performed during deletion.
030/22/205238	Disabling the capacity saving setting for THP V-VOLs with Deduplication and Compression set might take many days to complete. Also, the pool usage increases due to the data expansion processing. Once the processing to disable the setting starts, it cannot be stopped.
030/22/205239	Formatting THP V-VOLs with Deduplication and Compression set might take many days to complete. Also, the pool usage might increase due to the format processing. Once the format processing starts, it cannot be stopped.
030/22/205240	Deleting THP V-VOLs with Deduplication and Compression set might take many days to complete. Also, the pool usage might increase due to the deletion processing. Once the processing starts, it cannot be stopped.
030/22/205241	THP V-VOLs cannot be deleted.
030/22/205422	The operation might not be performed because the storage system is being maintained or in the state where a maintenance operation is required. Do you want to cancel this operation?
030/22/206001	The specified operation cannot be performed because verification is not in process.
030/22/206262	The ALU attribute is not set on the selected LDEV.
030/22/206264	The selected LDEV is not bound to an LDEV with the SLU attribute.
030/22/206265	The selected LDEV does not exist in the configuration.
030/22/207001	An unexpected error occurred.
030/22/208001	Verification ended abnormally.
030/22/208002	Verification was interrupted.
030/22/209001	You are trying to create LDEVs that exceed the physical capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to change the LDEV capacity to match the recommended capacity shown in this message, which means to set the LDEV capacity that does not exceed the physical capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can create LDEVs in addition to the physical capacity of the parity group.
030/22/209002	You are trying to create LDEVs that exceed the recommended capacity.\\nBecause this may increase the risk of accidental over use, it is recommended to change the LDEV capacity to match the recommended capacity shown in this message.
030/22/209003	You are trying to create LDEVs that exceed the physical capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to change the LDEV capacity to match the recommended capacity shown in the Parity Groups table, which means to set the LDEV capacity that does not exceed the physical capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can create LDEVs in addition to the physical capacity of the parity group.
030/22/209004	You are trying to create LDEVs that exceed the recommended capacity.\\nBecause this may increase the risk of accidental over use, it is recommended to change the LDEV capacity to match the recommended capacity shown in the Parity Groups table.
030/22/209005	Check the error details with the error code from the following list.
031/21/105001	The specified Tiering Policy cannot be set due to one of the following reasons:\\n- The Tier1 Min value exceeds the Tier1 Max value.\\n- The Tier3 Min value exceeds the Tier3 Max value.\\n- The total value of the Tier1 Min value and the Tier3 Min value exceeds 100%.
031/21/109205	Are you sure you want to initialize all the THP and FS pools?
031/22/105132	Short of {0} LDEV ID(s).
031/22/105133	The processing cannot continue due to an internal logic contradiction.
031/22/105148	The combo box is not selected.
031/22/105248	The processing cannot continue due to an internal logical contradiction.
031/22/105483	The specified Tiering Policy cannot be set due to one of the following reasons:\\n- The Tier1 Min value exceeds the Tier1 Max value.\\n- The Tier3 Min value exceeds the Tier3 Max value.\\n- The total value of the Tier1 Min value and the Tier3 Min value exceeds 100%.
031/22/105485	The selected policy cannot be edited because the policy is defined by the system.
031/22/106005	No more pools can be registered, because the number of registered pools has reached the maximum.
031/22/106006	There exist no volumes available for pool volumes.
031/22/106007	The setting cannot be performed, because the number of pools exceeds the maximum.
031/22/106008	The volume to be set as a pool volume is not selected.
031/22/106009	The setting cannot be performed, because the number of pool volumes that can be set to a pool exceeds the maximum.
031/22/106010	The specified pool subscription limit value cannot be set.
031/22/106011	The number of prefix characters of the pool name is invalid.
031/22/106012	The specified prefix characters for a pool name contain an invalid character(s).
031/22/106013	The initial number of specified pool name is not input.
031/22/106014	The specified initial number of pool name contains a character other than the numerical value.
031/22/106015	The specified initial number of pool name exceeds the maximum.
031/22/106016	The number of characters that can be set for the pool name exceeds the maximum, or some spaces are set.
031/22/106017	The specified pool name is already used.
031/22/106018	The specified pool ID is invalid.
031/22/106019	The allocation cannot be done from the specified pool ID.
031/22/106022	The selected volumes cannot be specified as a pool volume, because the cache modes of the selected volumes coexist.   
031/22/106024	The operation cannot be executed, because the specified pool is blocked.
031/22/106025	The operation cannot be executed, because the specified pool is blocked.
031/22/106026	The operation cannot be executed, because the pool volume is blocked.
031/22/106027	The operation cannot be executed, because the pool usage exceeds the threshold.
031/22/106028	The operation cannot be executed, because the specified pool is in shrinking operation.
031/22/106029	The operation cannot be executed, because the specified pool is in Normal status.
031/22/106030	The operation cannot be executed, because the specified pool is associated with a Thin Provisioning volume.
031/22/106031	The selected pool cannot be deleted, because the pool is being used or the data in the pool is being discarded.
031/22/106032	The operation cannot be executed, because the specified pool is not in shrinking operation.
031/22/106033	The operation cannot be performed because the specified pool is for Fast Snap.
031/22/106034	The shrinking operation cannot be performed on the specified pool due to either of the following reasons:\\n- The ratio of the used capacity to the total pool capacity after shrinking becomes higher than the higher one of the depletion threshold or the warning threshold.\\n- There is no pool volume that has enough free space required to delete the pool volume with system area.
031/22/106035	The operation cannot be executed, because the top pool volume has been selected.
031/22/106036	The operation cannot be executed, because the specified pool volumes contain an abnormal pool volume.
031/22/106037	The setting cannot be executed, because the specified pool has no free space.
031/22/106038	No table row, or two or more table rows are selected.
031/22/106041	There are no valid volumes, because the pools are blocked.
031/22/106042	The shrinking operation cannot be performed on the specified pool.
031/22/106062	The pool cannot be restored.
031/22/106063	The pool cannot be restored.
031/22/106064	The pool cannot be restored.
031/22/106078	The specified function is not available because the necessary program product is not installed.
031/22/106087	The operation cannot be done because there is no pool that can be associated with a THP V-VOL.
031/22/106090	The depletion threshold is set lower than the warning threshold. 
031/22/106091	The warning threshold is not input.
031/22/106093	The depletion threshold is not input.
031/22/106094	Different volume types (such as drive types, RAID levels, and internal/external volumes) or cache modes coexist in the LDEVs selected as pool volumes. If different volume types or cache modes are used in the same pool, the entire performance might be affected by the LDEVs with the lowest performance. Do you want to continue this operation?
031/22/106095	The operation cannot be performed because the tier management of the specified pools is not in manual operation.
031/22/106096	Failed to get the pool information.
031/22/106097	The operation cannot be done because the specified pool is in monitoring operation.
031/22/106098	The operation cannot be done because the specified pool is calculating the monitor information.
031/22/106099	The processing cannot continue due to an internal logic contradiction.
031/22/106100	The operation cannot be done because the specified pool is not in the monitoring operation.
031/22/106101	The operation cannot be done because the configuration of the specified pools does not meet the conditions below.\\n- The smart pool is enabled.\\n- The tier management is in manual operation.
031/22/106102	The operation cannot be done because the specified pool is in tier relocating operation.
031/22/106103	The operation cannot be done because the specified pool is in monitoring operation.
031/22/106104	The operation cannot be done because the specified pool is calculating the monitor information.
031/22/106105	The operation cannot be executed because the specified pool has no monitoring data.
031/22/106106	The operation cannot be done because the specified pool is not in tier relocating operation.
031/22/106107	The operation cannot be executed because there is only one tier in the specified pool.
031/22/106108	The specified LDEVs cannot be set as pool volumes in the same pool because the LDEVs are allocated to different resource groups.
031/22/106111	There is an empty field in the following items.\\n- Tier Management\\n- Cycle Time\\n- Monitoring Period\\n- Monitoring Mode\\n- Relocation Speed\\n- Buffer Space for New page assignment\\n- Buffer Space for Tier relocation
031/22/106112	There is no check in the check box of Smart Pool.
031/22/106139	This operation will delete the currently stored monitor data.
031/22/106140	Enabling and disabling the Smart Pool setting may impact the host I/O performance of each Thin Provisioning volume associated with the pool.
031/22/106163	Do you switch to the setting of the selected row?
031/22/106164	The operation cannot be performed with this pool.
031/22/106165	This operation cannot be performed because the pool volumes are not external LDEVs.  
031/22/106168	A required program product is not installed, or you do not have permission to perform the operation.
031/22/106169	If the tier configuration changes by performing this operation, the currently stored monitor data will be deleted.
031/22/107007	An internal logic error occurred.
031/22/107008	The processing cannot continue due to an internal logic contradiction.
031/22/107009	An internal logic error occurred.
031/22/107023	The processing cannot continue due to an internal logic contradiction.
031/22/200001	The pool of the specified capacity cannot be created.
031/22/205133	The radio button for Protect V-VOLs when I/O fails to Blocked Pool VOL (Yes/No) is not selected.
031/22/205134	The radio button for Protect V-VOLs when I/O fails to Full Pool (Yes/No) is not selected.
031/22/205185	Pool names cannot be allocated to all specified pools because the number of characters for pool names that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for a pool name.
031/22/205212	Pool volumes in the selected pools cannot be shredded because the pool volumes belong to parity groups with the capacity expansion enabled.
031/22/205213	The subscription limits of the pools for assigning deduplication system data volumes are too low.
031/22/205214	The subscription limits of the pools for assigning deduplication system data volumes are too low. The subscription limits must be {0}% or more.
031/22/205215	Some of the settings for the pool cannot be applied due to errors occurring in different pools during pool creation with the same task.
031/22/205216	Some of the settings for the pool cannot be applied due to errors occurring in different pools during pool delete with the same task.
031/22/205217	Deduplication system data volumes cannot be assigned to Smart Tiers pools.
031/22/205218	Deduplication system data volumes cannot be assigned to pools that have the data direct mapping attribute.
031/22/205219	Deduplication system data volumes cannot be assigned to Smart (Real Time Smart Tier) pools.
031/22/205220	The radio button for Assign Deduplication System Data Volume is not selected.
031/22/205221	The deduplication system data volumes have already been assigned.
031/22/205222	The assignments of deduplication system data volumes have already been released.
031/22/206140	The operation can not be performed due to one of the following reasons:\\n- The Smart Tiers function is not enabled.\\n- The shared memory for the Smart Tiers function is not installed.
031/22/206283	A pool where Data Direct Mapping is enabled cannot be created because volumes with the attribute other than Data Direct Mapped are not selected.
031/22/206284	The pool cannot be shrunk with the currently selected pool volumes.
031/22/206285	The pool cannot be shrunk because Data Direct Mapped LDEV is set to the selected pool volumes.
031/22/206293	The selected pool volumes cannot be shrunk due to one of the following reasons.\\n- The proportion of the used pool capacity after shrinking to the total physical pool capacity is greater than the depletion threshold.\\n- No pool volumes have space required for setting a new volume with the system area.
031/22/206297	The check box of Warning Threshold or Depletion Threshold is not selected.
031/22/206298	The values of Warning Threshold and Depletion Threshold cannot be changed on the specified pool with the Data Direct Mapping attribute.
031/22/206299	The number of characters entered in the tiering policy name exceeds the maximum (32 characters), or a tiering policy name is not entered.
031/22/206300	The tiering policy name contains characters that are not valid.
031/22/206330	The operation cannot be performed, because Fast Snap pairs exist in the selected Thin Provisioning pool.
031/22/206331	The operation cannot be performed, because Fast Snap pairs exist in the selected Thin Provisioning pool.
031/22/206332	The operation cannot be performed, because the license for Fast Snap is not installed.
031/22/209014	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table, which means to select pool volumes that do not exceed the recommended capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can add pool volumes in addition to the recommended capacity of the parity group.
031/22/209015	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table, which means to select pool volumes that do not exceed the recommended capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can add pool volumes in addition to the recommended capacity of the parity group.
031/22/209016	The total capacity of pool volumes defined from the parity group exceeds the recommended capacity.
031/22/209017	The total capacity of pool volumes defined from the parity group exceeds the recommended capacity.
031/22/209018	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table, which means to select pool volumes that do not exceed the recommended capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can add pool volumes in addition to the recommended capacity of the parity group.
031/22/209019	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\n- If the Saving (%) value is unknown at this time, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table, which means to select pool volumes that do not exceed the recommended capacity of the parity group so as to reduce the risk of accidental over use.\\n- If the Saving (%) value is known or can be predicted, then you can add pool volumes in addition to the recommended capacity of the parity group.
031/22/209020	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\nBecause this may increase the risk of accidental over use, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table.
031/22/209021	You are trying to add pool volumes that exceed the recommended capacity of the parity group.\\nBecause this may increase the risk of accidental over use, it is recommended to select pool volumes that match the capacity of what is shown in the Pool Volumes table.
031/22/306258	Realtime Tier Relocation cannot be used because a volume whose drive type is SSD is not selected.
031/22/306259	The RT pool cannot be shrunk because of the selected pool volumes.
031/22/306260	Realtime Tier Relocation cannot be enabled because a pool that does not contain a volume whose drive type is SSD is selected for a pool volume.
031/22/306261	Realtime Tier Relocation cannot be enabled because necessary program products are not installed.
032/05/105455	LDEVs cannot be created because there is not enough free area in the pool.
032/05/201001	An LDEV, for which Full Allocation is enabled, cannot be created with the specified emulation type.
032/05/201002	The specified pool is not a Thin Provisioning pool.
032/05/2011	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
032/05/2015	An error occurred while communicating with the storage system.
032/05/203001	An LDEV, for which Full Allocation is enabled, cannot be created because the specified pool is in shrinking operation.
032/05/208001	The operation cannot be performed because the capacity of the specified LDEV is different from that of the selected external volume.
032/05/208002	Data Direct Mapping cannot be enabled because the specified emulation type is not OPEN-V.
032/05/208003	The specified LDEV ID of the pool volume is outside the setting range.
032/05/208004	The operation cannot be performed because the specified pool volume is not associated with a pool with the Data Direct Mapped attribute.
032/05/208005	The operation cannot be performed because the specified pool volume is associated with a different Thin Provisioning volume.
032/05/208008	No volumes can be created because the Data Direct Mapped attribute differs between the specified volume and pool.
032/05/208009	Full Allocation and Data Direct Mapping cannot be enabled at the same time.
032/05/208010	T10 PI cannot be enabled because the specified emulation type is not OPEN-V.
032/05/208011	No THP V-VOLs can be created because the specified pool volumes are blocked.
032/05/208012	The operation cannot be performed because the specified volumes are associated with a pool volume whose Data Direct Mapping is enabled and an external volume used as the pool volume is not disconnected.
032/05/208013	An LDEV with the full allocation enabled cannot be created because the selected pool contains pool volumes that belong to parity groups with the capacity expansion enabled.
032/05/208118	The specified function is not supported.
032/05/208315	The operation cannot be performed, because deduplication system data volumes have already been allocated to the specified pools.
032/05/208316	Deduplication system data volumes are not allocated to the specified pools.
032/05/208318	The operation cannot be performed, because THP V-VOLs whose capacity saving setting is Deduplication and Compression are contained in the specified pools.
032/05/208319	The deduplication system data volume cannot be unassigned, because the deduplication rate (%) of the specified pool is greater than 0.
032/05/208321	The operation cannot be performed because there is not enough installed shared memory.
032/05/208322	The program product required for using the Compression Deduplication function is not installed.
032/05/208330	An error occurred during communication with the storage system.
032/05/208331	The emulation type of the specified volume cannot be used.
032/05/208332	No deduplication system data volume is allocated to the specified pool.
032/05/208333	The operation cannot be performed because the specified pool has the following problems:\\n- The status of the pool volumes is not normal.\\n- The I/O load of the Thin Provisioning volumes associated with the pool is high.
032/05/208334	The operation cannot be performed because the required number of cache management devices cannot be allocated.
032/05/208335	The specified operation cannot be performed because there is not enough shared memory for the V-VOL management area.
032/05/208336	The capacity saving setting cannot be enabled, because a pool with the data direct mapping attribute is specified.
032/05/208337	The full allocation setting and the capacity saving setting cannot be enabled at the same time.
032/05/208338	The operation cannot be performed because the specified pool has the following problems:\\n- The pool usage exceeds the threshold.\\n- The pool status is not valid.
032/05/208339	The operation cannot be performed because the specified parameter is not valid.
032/05/208341	The deduplication system data volume cannot be allocated, because a pool with the data direct mapping attribute is specified.
032/05/208357	The deduplication system data volumes cannot be allocated, because pools for which the full allocation setting is enabled are specified.
032/05/208358	The capacity saving setting cannot be applied to THP V-VOLs.
032/05/208360	The specified LDEV is already being used as a JNL volume by Continuous Access Journal or Continuous Access Journal for Mainframe.
032/05/208361	The operation cannot be performed, because the specified LDEV is in a state in which the capacity saving setting cannot be changed.
032/05/208363	The operation cannot be performed, because the deduplication system data volume of the pool associated with the specified LDEV is blocked.
032/05/208369	The operation cannot be performed, because the selected THP V-VOLs are associated with a pool for which the smart pool setting is enabled.
032/05/208392	The selected pool volumes cannot be added to a pool with the data direct mapping attribute, because they are deduplication system data volumes.
032/05/208395	The specified LDEVs cannot be deleted, because the LDEVs contain data used by the capacity saving functions (compression function or deduplication function).
032/05/208412	The mapping information for the specified LDEVs is not correct.
032/05/208413	LDEVs cannot be deleted, because deduplication system data volumes are specified.
032/05/208414	The specified number of the deduplication system data volumes exceeds the maximum number that can be specified for a single pool.
032/05/2095	The specified operation cannot be performed due to one of the following maintenance operations:\\n- LDEV formatting is in progress.\\n- The CHB/DKB status is changing.\\n- The processor status is changing.\\n- The cache status is changing.\\n- LDEV shredding is in progress.\\n- The configuration is changing.
032/05/2201	Processing cannot be performed because of Data Retention settings.
032/05/2520	An Auto LUN pair is defined.
032/05/2521	An Auto LUN pair is defined.
032/05/3003	An error occurred during Remote Web Console processing.
032/05/5013	An error occurred during Remote Web Console processing.
032/05/5099	An error occurred during Remote Web Console processing.
032/05/5511	A necessary program product is not installed.
032/05/56516	A pair of Continuous Access Synchronous is defined.
032/05/56517	A pair of Business Copy or Fast Snap is defined.
032/05/5827	An error occurred during Remote Web Console processing.
032/05/5828	An error occurred during Remote Web Console processing.
032/05/58406	A pair of Continuous Access Journal is defined.
032/05/58407	A volume is defined as a journal volume of Continuous Access Journal.
032/05/58474	The specified operation cannot be performed because there is not enough memory available on the shared memory for the V-VOL management area.
032/05/6012	An error occurred during Remote Web Console processing.
032/05/6022	An error occurred during Remote Web Console processing.
032/05/6533	An error occurred during Remote Web Console processing.
032/05/6534	The number of V-VOLs that can be registered in the storage system has reached the maximum.
032/05/6535	The configuration cannot be changed because the LUN Path is remained in the target volume. 
032/05/6537	The setting process has not been executed because there is no error in this setting, but an error in the others settings. 
032/05/65740	The configuration changing processes are conflicting at DKC.
032/05/65794	The specified V-VOL is not mounted.
032/05/65795	The specified V-VOL has already been specified.
032/05/66503	The LDKC, CU, and LDEV are not set within the available range.
032/05/66504	Specified LDKC:CU:LDEV has already been used.
032/05/66505	The specified LDEV number has already been assigned to another emulation group within the range grouped by 32 LDEV numbers.
032/05/66506	Specified SSID has already been used.
032/05/66508	The specified LDEV capacity is invalid.
032/05/66510	The specified emulation type cannot be used.
032/05/66512	Specified CLPR is not mounted.
032/05/66747	The value of SSID is not set within the available range.
032/05/66748	A value different from SSID that has already been set is specified. 
032/05/68725	The specified operation cannot be performed because there is not enough memory available on the shared memory for the V-VOL management area.
032/05/68726	The capacity of THP V-VOL is invalid.
032/05/68728	The pool is in an abnormal state.
032/05/68748	The number of Thin Provisioning volumes that can be made in a single pool has exceeded the maximum.
032/05/68751	The storage system is in process to delete THP V-VOL.
032/05/68800	Volume migration or Quick Restore is in progress.
032/05/68897	There is a pool that has been blocked. And the item to be operated includes a THP V-VOL.
032/05/68920	The total capacity of THP V-VOLs defined in the specified pool exceeds the value that had been permitted to the pool.
032/05/78032	The specified MP Blade is not mounted.
032/05/78047	Enough cache management devices cannot be allocated to the target volumes.
032/05/78048	An error occurred while accessing the user information.
032/05/78057	The specified LDEV belongs to a resource group that you do not have permission to access.
032/05/78059	The pool associated with the specified LDEV contains LDEVs that belong to a resource group that you do not have permission to access.
032/05/78061	The specified emulation type is different from the emulation type of the selected pool.
032/05/78065	The storage system is in internal process, or a different user is changing the configuration.
032/05/8000	An error occurred during Remote Web Console processing.
032/05/8001	An error occurred during Remote Web Console processing.
032/05/8102	This function is not supported.
032/05/8958	An error occurred on the DKC side.
032/05/8966	An error occurred on the DKC side.
032/22/105190	There is no data.
032/22/105191	The processing cannot continue due to an internal logic contradiction.
032/22/105192	The association information of the specified LDEV does not exist in the configuration.
032/22/105193	The status of the specified LDEV is not normal.
032/22/105194	The input value is out of the setting range.
032/22/105195	Zero is set in the size.
032/22/105196	The size is not specified.
032/22/105197	Other than the numerical value is set in the size.
032/22/105198	The specified LDEV is not a THP V-VOL.
032/22/105199	The specified LDEV is not in the state of zero page reclaiming.
032/22/105200	The specified LDEV is in the state of zero page reclaiming.
032/22/105201	The specified LDEV does not exist in the configuration.
032/22/105202	The status information of the specified LDEV does not exist in the configuration.
032/22/105203	The detailed information of the pool that is associated with the specified LDEV does not exist in the configuration.
032/22/105211	The selected volume cannot be enhanced any further.
032/22/105484	Different pools are associated with the specified LDEVs.
032/22/205051	The selected LDEV has been set as a journal volume.
032/22/205136	The specified LDEV cannot be expanded because the used capacity of the pool associated with the LDEV exceeds the depletion threshold and Full Allocation is enabled for the LDEV.
032/22/205201	The specified LDEV cannot be operated because LUN paths are set to host groups on which Host Mode Option 97 is enabled.
032/22/205206	Data Direct Mapping is enabled on the selected LDEVs.
032/22/205220	The operation cannot be performed, because one or more deduplication system data volumes are specified.
033/05/1036	The size of the specified volume is outside the setting range.
033/05/1037	The free space remaining in the parity group is not enough to install a customized volume (CV).
033/05/1039	A path is defined to the specified volume. 
033/05/1041	The CU number and the LDEV number set in the VLL operation are the same as those of other volumes.
033/05/1043	An operation is specified for the uninstalled VDEV.
033/05/1044	An error occurred during Remote Web Console processing.
033/05/1049	An error occurred during Remote Web Console processing.
033/05/1074	The specified CU number cannot be set.
033/05/1075	In the VLL operation (Create LDEVs, Delete LDEVs), there are some operations which cannot be set together are specified.
033/05/1101	An operation is specified for the uninstalled volume.
033/05/1103	An operation is specified for the uninstalled Parity Group.
033/05/1105	The number of volumes exceeds the maximum that can be set.
033/05/1601	This functionality is not available. Open System Array Management is required.
033/05/1900	The operation cannot be performed because the storage system is being maintained.
033/05/1910	The specified volume contains a Fast Snap pair.
033/05/1911	The specified volume contains Pool-VOLs. 
033/05/1913	The setting cannot be made because the specified LDEV is a remote command device.
033/05/1914	The number of V-VOL(s) has exceeded the maximum number of V-VOL(s) that can be set in a storage system.
033/05/2004	An error occurred during Remote Web Console processing.
033/05/2005	An error occurred during Remote Web Console processing.
033/05/2011	The status of the storage system requires maintenance (for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
033/05/2015	An error occurred while connecting to the storage system.
033/05/2022	An error occurred during Remote Web Console processing.
033/05/205001	An error occurred during Remote Web Console processing.
033/05/205002	An error occurred during Remote Web Console processing.
033/05/205003	The parity group ID of the selected parity group is not valid.
033/05/205004	The selected drive is not valid.
033/05/205005	The specified RAID level or number of concatenated parity groups is not valid.
033/05/205006	The entered parity group ID is not valid.
033/05/205007	No drive box is specified.
033/05/205008	The number of the specified drive boxes is not valid.
033/05/205009	The specified drive box does not exist.
033/05/205010	An error occurred during communication with the storage system.
033/05/208000	An error occurred on the storage system.
033/05/208001	The specified operation cannot be performed because the volume is being formatted or shredded, or the quick format is being prepared.
033/05/208002	The specified operation cannot be performed because the volume is in the data copy process (drive copy).
033/05/208003	The specified operation cannot be performed because the cache status is changing.
033/05/208004	The specified operation cannot be performed because the status of the MP unit is changing.
033/05/208005	The specified operation cannot be performed because the status of the DKB is changing.
033/05/208006	The specified operation cannot be performed because the status of the CHB is changing.
033/05/208007	The specified operation cannot be performed because Verify LDEVs is in process.
033/05/208008	The specified operation cannot be performed because the volume is in the PIN status.
033/05/208009	The specified operation cannot be performed because the drive box power supply is in the abnormal state.
033/05/208010	The specified operation cannot be performed because the controller board of the MP unit is blocked.
033/05/208011	The specified operation cannot be performed because the MP unit is blocked.
033/05/208012	The specified operation cannot be performed because the CHB is blocked.
033/05/208013	The specified operation cannot be performed because the port is blocked.
033/05/208014	The specified operation cannot be performed because the DKB is blocked.
033/05/208015	The specified operation cannot be performed because the SAS port is blocked.
033/05/208016	The specified operation cannot be performed because the drive is blocked.
033/05/208017	The specified operation cannot be performed because the cache memory is blocked.
033/05/208018	An encryption key cannot be obtained from the key management server.
033/05/208019	The specified operation cannot be performed because there are not enough encryption keys that are not used.
033/05/208020	The specified operation cannot be performed because the selected parity group uses a spare drive.
033/05/208022	The parity group ID of the selected parity group is not valid.
033/05/208023	The RAID level of the selected parity group is not valid.
033/05/208024	The CLPR of the selected parity group is not valid.
033/05/208025	The selected drive box or drive is not valid.
033/05/208026	The operation cannot be performed because an error occurred on the storage system.
033/05/208027	The specified parity group does not exist.
033/05/208028	The specified parity group cannot be deleted because it contains a pair of Auto LUN, Business Copy, or Fast Snap.
033/05/208029	The specified parity group cannot be deleted because it contains an LDEV containing a command device defined by a remote replication pair.
033/05/208031	The specified parity group or LDEV cannot be deleted because it contains a primary volume of a High Availability pair.
033/05/208032	The specified parity group or LDEV cannot be deleted because it contains a secondary volume of a High Availability pair.
033/05/208033	The specified operation cannot be performed because the specified parity groups or volumes contain quorum disks used by High Availability pairs.
033/05/208034	The specified parity group cannot be deleted because it contains a pool volume.
033/05/208035	The specified parity group cannot be deleted because it contains a volume on which Volume Security is set.
033/05/208036	The specified parity group cannot be deleted because it contains a volume on which Data Retention is set.
033/05/208037	The operation cannot be performed because a different application is running.
033/05/208038	The resource group to which the selected parity group or LDEV belongs is locked by a different user.
033/05/208039	The user authentication is not performed.
033/05/208040	The specified operation cannot be performed because the specified parity groups or volumes contain journal volumes.
033/05/208041	The selected parity group or LDEVs cannot be deleted because they contain a command device that is used by an extended consistency group of Universal Replicator.
033/05/208042	The selected parity group or LDEVs cannot be deleted because they contain a remote command device that is used by a mirror of a journal group.
033/05/208043	The selected parity group or LDEVs cannot be deleted because they contain a volume on which LDEV formatting is not performed.
033/05/208044	The operation cannot be performed because powering off the storage system is in process.
033/05/208045	The selected parity group or LDEVs cannot be deleted because they contain an LDEV whose encryption key information is not valid.
033/05/208046	The selected parity group or LDEVs cannot be deleted because they contain an LDEV whose encryption key information is not valid.
033/05/208047	The operation cannot be performed because the storage system is busy.
033/05/208048	No more spare drives can be set because the number of spare drives that are set has reached the maximum.
033/05/208049	The selected drive is not mounted.
033/05/208050	The entered parity group ID is already used.
033/05/208051	The selected CLPR is not mounted.
033/05/208052	The selected drive is already used.
033/05/208053	The selected drive is not a spare drive.
033/05/208061	The specified LDEV ID is not valid.
033/05/208062	The entered LDEV capacity is not valid.
033/05/208065	The selected emulation type does not support the entered LDEV capacity.
033/05/208069	An external volume mapped for the online data migration or an external volume with the Data Direct Mapped attribute cannot be created because the entered LDEV capacity is not the same as the external volume group.
033/05/208070	An LDEV with the same capacity as the parity group or external volume group cannot be created because there is an LDEV in the parity group or the external volume group.
033/05/208073	The LDEV created in the external volume group cannot be restored.
033/05/208074	The specified MP unit ID is outside the setting range.
033/05/208076	The specified LDEV is used as a system disk.
033/05/208077	The operation cannot be performed because any of the following items differs between LDEVs on the migration source storage system and the migration target storage system:\\n- Serial number\\n- Controller ID\\n- Emulation type\\n- SSID\\n- LUSE configuration\\n- CVS configuration\\n- LDEV number
033/05/208080	A volume cannot be added because the encryption key is not valid.
033/05/208081	There is an LDEV that is being shredded in the specified parity group.
033/05/208082	There is an LDEV that is being formatted in the specified parity group.
033/05/208083	There is an LDEV that is being quick formatted in the specified parity group.
033/05/208084	The specified parity group is in the data copy process (correction copy).
033/05/208085	The operation cannot be performed because the parity group or the external volume group is being used by a different operation.
033/05/208086	The operation cannot be performed because the storage system is in internal process.
033/05/208088	The specified LDEV is not mounted.
033/05/208089	The specified MP unit is not mounted.
033/05/208090	A necessary program product is not installed.
033/05/208091	A necessary program product is not installed.
033/05/208092	The specified LDEV ID is already used.
033/05/208093	A volume cannot be created because the capacity of the specified external volume group exceeds the maximum capacity for an external volume that is mapped for the online data migration.
033/05/208094	The specified number of LDEVs exceeds the maximum that can be created in the current configuration.
033/05/208095	The specified parity groups or volumes contain volumes to which LU paths are set.
033/05/208096	The specified LDEV is used as a quorum disk.
033/05/208097	The specified LDEV is used as a journal volume.
033/05/208098	The specified LDEV is used as a remote command device.
033/05/2081	An error occurred during a VLL operation to add or delete customized volumes. Please wait for a while, and then retry the operation.
033/05/208103	The specified number of LDEVs exceeds the maximum that can be created in the parity group or the external volume group.
033/05/208104	System Array Management settings exist on the specified volume.
033/05/208105	The specified LDEV is used as a command device of an extended consistency group of Continuous Access Journal.
033/05/208106	The specified LDEV is used as an external volume that is mapped for the online data migration.
033/05/208107	There is not enough space left for the specified capacity in the parity group or the external volume group.
033/05/208108	The specified location is outside the setting range.
033/05/208109	An error occurred on the management server side.
033/05/208111	An unregistered error occurred.
033/05/208112	A communication time-out error occurred.
033/05/208113	An error occurred on the storage system.
033/05/208114	The management server is busy.
033/05/208115	The management server is busy.
033/05/208116	An internal logic contradiction occurred.
033/05/208117	A communication error occurred.
033/05/208118	The specified function is not supported.
033/05/208119	The storage system has accepted the request normally, but the processing requires some time.
033/05/208120	An error occurred during communication with the storage system.
033/05/208121	An internal error occurred.
033/05/208122	The capacity expansion cannot be changed because different versions of DKCMAIN firmware coexist on the storage system.
033/05/208123	The specified parity groups do not support capacity expansion.
033/05/208124	The capacity expansion cannot be changed because the specified parity groups are in the data copy process (correction copy).
033/05/208125	The capacity expansion cannot be changed because the specified parity groups are in the dynamic sparing process.
033/05/208126	The capacity expansion cannot be changed because the specified parity groups are in the copy back process.
033/05/208127	The capacity expansion cannot be changed because the specified parity groups contain pools with Full Allocation enabled.
033/05/208128	The capacity expansion cannot be changed because the specified parity groups contain volumes that belong to blocked pools.
033/05/208129	The capacity expansion cannot be changed because the RAID levels of the specified parity groups do not support pool creation.
033/05/208130	The capacity expansion cannot be changed because the specified parity groups contain volumes that belong to multiple pools.
033/05/208131	The capacity expansion cannot be changed because the specified parity groups are in the correction access status.
033/05/208132	The capacity expansion cannot be enabled because the specified parity groups contain volumes protected by Data Retention settings.
033/05/208133	The capacity expansion cannot be changed because volumes exist in the expanded space of the specified parity groups.
033/05/208134	The firmware version of the specified drive does not support capacity expansion.
033/05/208135	An internal error occurred.
033/05/208136	No parity groups can be created because the specified drives contain drives that do not support capacity expansion.
033/05/208137	No parity groups can be created because the specified parity groups that are concatenated contain parity groups without support for capacity expansion.
033/05/208138	The current DKCMAIN firmware version does not support changing the capacity expansion.
033/05/208139	The specified parity groups contain volumes that are used by Cache Residency.
033/05/208140	The specified parity groups contain volumes with capacity less than needed for pool volumes.
033/05/208141	The specified parity groups contain volumes that are set as pair volumes.
033/05/208142	The specified parity groups contain volumes that are mapped for the online data migration.
033/05/208143	The specified operation cannot be performed because data remains in the expanded space of the parity groups.
033/05/208144	The parity group with the encryption and the capacity expansion enabled cannot be created.
033/05/208145	The capacity expansion cannot be enabled on the specified parity groups because the encryption is enabled.
033/05/208146	The specified LDEVs are being used by a different operation.
033/05/208147	An internal error occurred.
033/05/208148	Only LDEVs to be used as pool volumes can be created in a parity group with the capacity expansion enabled. LDEVs cannot be created because the specified capacity does not meet the requirement for pool volumes.
033/05/208149	The delete operation cannot be completed.
033/05/208200	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
033/05/208201	T10 PI cannot be enabled because the specified LDEV is an external volume.
033/05/2085	Copying is in progress for a pair of Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN , or Fast Snap.
033/05/208500	Capacity Expansion cannot be enabled, because LDEVs that are not registered to the pool exist in the selected FMC parity group.
033/05/2086	The configuration of Continuous Access Synchronous, Continuous Access Journal, Business Copy, Auto LUN, or Fast Snap has been defined.
033/05/2088	The Remote Copy pair is suspended.
033/05/2089	The corresponding CHB might contain the last path between the MCU and RCU of Continuous Access Synchronous or Continuous Access Journal.
033/05/2090	Business Copy or Fast Snap setting exists. 
033/05/2091	The backup server of Business Copy or Fast Snap is running.
033/05/2092	Some pairs of Business Copy or Fast Snap exist. 
033/05/2093	Some Business Copy pairs exist. 
033/05/2094	Some Business Copy pairs exist. 
033/05/2095	A maintenance operation is in progress. For example: \\n -  LDEV formatting is in progress \\n -  Correction Copy is in progress \\n -  Drive Copy is in progress \\n -  The CHB/DKB status is changing \\n -  The cache status is changing \\n -  Replacement of an OEM drive firmware is in progress \\n -  LDEV Shredding is in progress.\\nTherefore the specified operation cannot be executed.
033/05/2201	Processing cannot be performed because of Data Retention settings.
033/05/2204	Devices to be maintained include journal volumes.
033/05/2205	Devices to be maintained include journal volumes.
033/05/2515	A Continuous Access Synchronous pair or a Continuous Access Journal pair is defined. 
033/05/2516	A Continuous Access Synchronous pair or a Continuous Access Journal pair is defined. 
033/05/2517	The target volume is defined as a pair volume of Business Copy or Fast Snap.
033/05/2518	A Business Copy pair is defined.
033/05/2520	A Auto LUN pair is defined.
033/05/2521	An Auto LUN pair is defined.
033/05/3002	An error occurred during Remote Web Console processing.
033/05/3003	An error occurred during Remote Web Console processing.
033/05/3006	An error occurred during Remote Web Console processing.
033/05/3008	An error occurred during Remote Web Console processing.
033/05/5013	An error occurred during Remote Web Console processing.
033/05/55500	An error occurred during Remote Web Console processing.
033/05/56526	The resources of other SLPR(s) cannot be accessed.
033/05/6001	An error occurred during Remote Web Console processing.
033/05/6011	An error occurred during Remote Web Console processing.
033/05/6012	An error occurred during Remote Web Console processing.
033/05/6022	An error occurred during Remote Web Console processing.
033/05/6023	An error occurred during Remote Web Console processing.
033/05/6092	An error occurred during Remote Web Console processing.
033/05/65661	There are no changes in the current configuration and the setting.
033/05/65670	The volumes registered in a Thin Provisioning Pool Group are included in the items to be maintained.
033/05/65671	The pool volumes associated with the Thin Provisioning volume is included in the items to be maintained.
033/05/65691	Preparing for quick format.
033/05/65728	The specified volume is not available to execute VLL operation (Create LDEVs, Delete LDEVs).
033/05/65740	The configuration changing processes are conflicting at DKC.
033/05/65741	An error occurred during Remote Web Console processing.
033/05/65742	An error occurred during Remote Web Console processing.
033/05/65768	The storage system is in internal process, or some other user is changing the configuration.
033/05/65781	The specified volumes contain a quorum disk.
033/05/65782	The specified volumes contain a High Availability pair volume.
033/05/65783	The specified volumes contain a High Availability pair volume.
033/05/65790	The specified volume includes a remote command device being used by a mirror of the journal group.
033/05/75043	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
033/05/76507	The specified LDEV belongs to a resource group that you do not have permission to access.
033/05/76508	The specified LDEV belongs to a resource group that you do not have permission to access.
033/05/78032	The selected MP unit is not mounted.
033/05/78033	The Auto cannot be specified because the attribute \\nof Fixed has been added to all of the MP Units.
033/05/87777	The operation cannot be performed because a resource group is not locked.
034/05/201001	The operation cannot be performed, because the configuration is being changed or a different application is in process.
034/05/201002	This function is not supported.
034/05/201003	The specified LDEV with the SLU attribute cannot be deleted because it is bound to an LDEV with the ALU attribute.
034/05/2011	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or some other factor).
034/05/2015	An error occurred while communicating with the storage system.
034/05/203001	The number of LDEVs with the ALU attribute will exceed the maximum.
034/05/203002	The operation cannot be performed because a virtual LDEV ID is not set for the specified LDEV ID.
034/05/203003	The specified ALU ID or SLU ID does not exist.
034/05/203004	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do not match.
034/05/203005	No commands are issued.
034/05/203006	The same IDs are included in the specified ALU IDs or SLU IDs.
034/05/203007	The specified volume cannot be used as an LDEV with the ALU attribute or that with the SLU attribute because it is used by Parallel Access Volumes.
034/05/203008	An LDEV with the SLU attribute cannot be created because the specified pool is in shrinking operation.
034/05/203009	The specified volume is not a virtual volume of Fast Snap.
034/05/207001	An error occurred during processing.
034/05/207002	An error occurred during SVP processing.
034/05/207003	The binding information cannot be acquired because the number of bound LDEVs with the ALU attribute and the SLU attribute exceeds the maximum that can be operated at once.
034/05/207010	An error occurred during Remote Web Console processing.
034/05/207011	This function is not supported.
034/05/208000	An error occurred on the storage system.
034/05/208001	An error occurred on the storage system.
034/05/208002	An error occurred on the storage system.
034/05/208003	An error occurred on the storage system.
034/05/208004	An error occurred on the storage system.
034/05/208005	The specified LUN path does not exist.
034/05/208006	An error occurred on the storage system.
034/05/208007	An error occurred on the storage system.
034/05/208008	An error occurred on the storage system.
034/05/208009	An error occurred on the storage system.
034/05/208010	An error occurred on the storage system.
034/05/208011	The snapshot data of the Fast Snap pair is not assigned to the virtual volume of Fast Snap.
034/05/208012	An error occurred on the storage system.
034/05/208013	An error occurred on the storage system.
034/05/208014	The operation cannot be performed because different microcode versions coexist on the storage system.
034/05/208020	An error occurred on the storage system.
034/05/208021	An error occurred on the storage system.
034/05/208022	The specified LDEV does not exist.
034/05/208023	An error occurred on the storage system.
034/05/208040	The specified volume is currently used by High Availability.
034/05/208041	The capacity of the specified THP V-VOL cannot be expanded because the configuration of the journal volume is changing.
034/05/208042	No LDEVs with the SLU attribute can be created because the specified pools have the Data Direct Mapped attribute.
034/05/208100	An error occurred on the storage system.
034/05/208101	An internal error occurred.
034/05/208102	The operation cannot be performed because the specified volume is:\\n- not contained;\\n- not a Smart volume; or\\n- blocked.
034/05/208106	The operation cannot be performed because any of the specified parameters is not valid.
034/05/208107	Monitoring data is not properly set.
034/05/208110	The operation cannot be performed because the specified pool is:\\n- not contained; or\\n- not a Smart pool.
034/05/208111	The specified pool is not in a state available for operation.
034/05/208112	The monitoring data is not set or not valid.
034/05/208120	The operation cannot be performed because the storage system is in the power-off process.
034/05/208130	Monitoring data cannot be collected from or set on the pool to which the specified volume belongs.
034/05/208131	Monitoring data cannot be collected from or set on the specified volume.
034/05/208132	The specified session ID or volume might not be valid, or this function might be performed on the specified volume by a different processing.
034/05/208133	The processing cannot continue because three minutes or longer have passed since the last operation.
034/05/208140	The operation cannot be performed because any of the specified parameters is not valid.
034/05/208200	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
034/05/208301	The specified LDEVs do not exist.
034/05/208302	The specified LDEVs are not Thin Provisioning volumes.
034/05/208310	The LDEV ID specified for the pool volume is outside the setting range.
034/05/208312	The operation cannot be performed because the required number of cache management devices cannot be allocated.
034/05/208313	The specified pool ID is outside the setting range.
034/05/208314	The operation cannot be performed because the specified pool has the following problems:\\n- The pool usage exceeds the threshold. \\n- The pool status is not valid.
034/05/208315	The operation cannot be performed, because deduplication system data volumes have already been allocated to the specified pools.
034/05/208316	Deduplication system data volumes are not allocated to the specified pools.
034/05/208317	The operation cannot be performed because the preceding operation is being processed.
034/05/208318	The operation cannot be performed, because the selected pool is associated with THP V-VOLs whose capacity saving status is Deduplication and Compression.
034/05/208319	The deduplication system data volume cannot be unassigned, because the deduplication rate (%) of the specified pool is greater than 0.
034/05/208320	The specified pool does not exist.
034/05/208321	The operation cannot be performed because there is not enough installed shared memory.
034/05/208322	The program product required for using the Compression Deduplication function is not installed.
034/05/208323	The specified LDEV ID is already in use.
034/05/208326	The operation cannot be performed, because the deduplication system data volume and the pool volumes are allocated to different resource groups.
034/05/208330	THP V-VOLs cannot be deleted.
034/05/208335	The specified operation cannot be performed because there is not enough shared memory for the V-VOL management area.
034/05/208340	The capacity saving setting cannot be enabled, because the full allocation setting is enabled.
034/05/208341	The deduplication system data volume cannot be allocated, because a pool with the data direct mapping attribute is specified.
034/05/208342	The operation cannot be performed because the SVP software version does not match the DKCMAIN firmware version.
034/05/208343	An internal error occurred.
034/05/208344	The specified operation cannot be performed because the maximum reserved pool capacity is not enough.
034/05/208345	The operation cannot be performed, because the smart pool setting of the pool associated with the specified LDEV is enabled.
034/05/208346	The specified operation cannot be performed, because the cache memory is blocked.
034/05/208347	The specified volume is not valid.
034/05/208348	The number of THP V-VOLs to be set for the storage system exceeds the maximum number of THP V-VOLs that can be set for a storage system.
034/05/208349	The specified LDEV ID is already in use.
034/05/208351	The specified LDEV ID is not valid.
034/05/208353	An error occurred on the storage system. The configuration might not be consistent.
034/05/208355	The operation cannot be performed because the specified pool is a Fast Snap pool.
034/05/208357	The deduplication system data volumes cannot be allocated, because pools for which the full allocation setting is enabled are specified.
034/05/208358	The capacity saving setting cannot be changed, because the specified LDEV is blocked.
034/05/208359	The emulation type of the specified LDEV cannot be used.
034/05/208360	The operation cannot be performed, because journal volumes are selected.
034/05/208361	The operation cannot be performed, because the specified LDEV is in a state in which the capacity saving setting cannot be changed.
034/05/208362	The operation cannot be performed, because THP V-VOLs with the data direct mapping attribute enabled are selected.
034/05/208363	The operation cannot be performed, because the deduplication system data volume of the pool associated with the selected THP V-VOLs is blocked.
034/05/208364	The capacity saving setting for the selected THP V-VOLs cannot be changed.
034/05/208365	The operation cannot be performed, because the deduplication system data volumes are selected.
034/05/208366	The operation cannot be performed, because one or more MPs are blocked.
034/05/208367	The operation cannot be performed, because the specified LDEVs belong to "NAS_Platform_System_RSG".
034/05/208368	The operation cannot be performed, because the storage system is performing internal processing or another user is changing the configuration.
034/05/208369	The specified number of the deduplication system data volumes exceeds the maximum number that can be specified for a single pool.
034/05/208370	The operation cannot be performed, because the same pool ID was specified more than once.
034/05/208371	The operation cannot be performed, because the specified LDEV is being used as the source or target volume by Auto LUN.
034/05/208372	The operation cannot be performed, because a Quick Restore operation is being performed on the specified LDEV.
034/05/208406	The capacity saving setting of the specified LDEVs cannot be changed to Compression or Deduplication and Compression.
034/05/208408	The capacity saving setting of the selected THP V-VOLs cannot be changed, because the capacity saving status of at least one THP V-VOL is any of the following.\\n- Deleting Volume\\n- Failed
034/05/208409	The capacity saving setting cannot be changed from Deduplication and Compression to Compression for the selected THP V-VOLs.
034/05/208412	The mapping information for the specified LDEVs is not correct.
034/05/208413	The operation cannot be performed, because a deduplication system data volume is selected.
034/05/208450	The selected THP V-VOLs cannot be deleted.
034/05/208451	The operation cannot be performed, because the capacity saving setting of the selected THP V-VOLs is Disabled.
034/05/208452	The specified LDEVs cannot be deleted, because the LDEVs are blocked and not formatted.
034/05/208453	The operation cannot be performed, because the specified LDEV is in a state in which the capacity saving setting cannot be changed.
034/05/208454	The specified LDEVs cannot be bound to an LDEV with the ALU attribute, because the LDEVs are being deleted.
034/05/208457	The selected LDEVs cannot be expanded, because they are being deleted.
034/05/208458	The operation cannot be performed, because the used capacity of the pool associated with the selected THP V-VOLs exceeds the depletion threshold.
034/05/2095	The specified operation cannot be performed due to one of the following maintenance operations:\\n- LDEV formatting is in progress.\\n- The CHB/DKB status is changing.\\n- The processor status is changing.\\n- The cache status is changing.\\n- LDEV shredding is in progress.\\n- The configuration is changing.
034/05/2201	Processing cannot be performed because of Data Retention settings.
034/05/2520	An Auto LUN pair is defined.
034/05/2521	An Auto LUN pair is defined.
034/05/5013	An error occurred during Remote Web Console processing.
034/05/55500	An error occurred during SVP processing.
034/05/55506	The specified volume is used as a reserved volume of Auto LUN.
034/05/56301	An error occurred during SVP processing.
034/05/56302	An error occurred during SVP processing.
034/05/56303	An error occurred during SVP processing.
034/05/56513	An emulation type that cannot be added is specified.
034/05/56515	The Disconnect External Storage Systems or the Disconnect External Volumes is not executed for the target volume.
034/05/56516	A pair of Continuous Access Synchronous is defined.
034/05/56517	A pair of Business Copy or Fast Snap is defined.
034/05/57101	An error occurred during SVP processing.
034/05/57102	An error occurred during SVP processing.
034/05/5827	An error occurred during Remote Web Console processing.
034/05/5828	An error occurred during Remote Web Console processing.
034/05/58406	A pair of Continuous Access Journal is defined.
034/05/58407	A volume is defined as a journal volume of Continuous Access Journal.
034/05/58474	The specified operation cannot be performed because there is not enough memory available on the shared memory for the V-VOL management area.
034/05/58572	An error occurred during communication with the storage system.
034/05/58573	This function is not supported.
034/05/58574	An error occurred during communication with the storage system.
034/05/58575	An error occurred during communication with the storage system.
034/05/58576	A communication time-out error occurred on the storage system.
034/05/58622	The configuration of Pool VOL is defined.
034/05/6012	An error occurred during SVP processing.
034/05/6022	An error occurred while opening the file.
034/05/6023	An error occurred while deleting the file.
034/05/6036	An error occurred during Remote Web Console processing.
034/05/6091	An error occurred while compressing the file.
034/05/6533	An error occurred during Remote Web Console processing.
034/05/6534	The number of V-VOLs that can be registered in the storage system has reached the maximum.
034/05/6535	The configuration cannot be changed because the LUN Path is remained in the target volume. 
034/05/6537	The setting cannot be applied because there is no error in this setting but an error in a different setting.
034/05/65740	The configuration changing processes are conflicting at DKC.
034/05/65794	The specified virtual volume is not mounted.
034/05/66501	The number of LDEVs that can be defined in an external volume has exceeded the maximum value.
034/05/66502	Specified ExG has already been used.
034/05/66503	The LDKC, CU, and LDEV are not set within the available range.
034/05/66504	Specified LDKC:CU:LDEV has already been used.
034/05/66505	The specified LDEV number has already been assigned to another emulation group within the range grouped by 32 LDEV numbers.
034/05/66506	The specified SSID is already used within a different range grouped by 32 LDEV numbers.
034/05/66507	The target external volume is blocked or not set within the range of capacity that can be used.
034/05/66508	The specified LDEV capacity is not within the available range for creation.
034/05/66512	Specified CLPR is not mounted.
034/05/66747	The value of SSID is not set within the available range.
034/05/66748	The specified SSID differs from the one already used within the range grouped by 32 LDEV numbers. 
034/05/68723	An internal logic contradiction occurred on the storage system.
034/05/68724	Shared memory is not installed.
034/05/68725	The specified operation cannot be performed because there is not enough memory available on the shared memory for the V-VOL management area.
034/05/68726	The capacity of the specified THP V-VOL is not within the available range for creation.
034/05/68727	Shared memory is being initialized.
034/05/68728	The pool is in an abnormal state.
034/05/68748	The number of Thin Provisioning volumes that can be made in a single pool has exceeded the maximum.
034/05/68751	The storage system is in process to delete THP V-VOL.
034/05/68800	Volume migration or Quick Restore is in progress.
034/05/68821	The specified volume is currently used by Business Copy.
034/05/68822	The specified volume is currently used by Fast Snap.
034/05/68823	The specified volume is currently used by Auto LUN or Online Migration.
034/05/68824	The specified volume is currently used by Continuous Access Synchronous.
034/05/68825	The specified volume is currently used by Continuous Access Journal.
034/05/68884	Quorum disks are included in the items to be maintained.
034/05/68897	The operation cannot be performed, because pools are blocked on the storage system.
034/05/68920	The total capacity of THP V-VOLs defined in the specified pool exceeds the value that had been permitted to the pool.
034/05/78005	The specified operation cannot be executed, because the LDEV capacity exceeds the maximum reserved pool capacity.
034/05/78006	The capacity of the specified LDEV is not within the available range for LDEV expansion.
034/05/78007	Failed to expand the V-VOLs, because it took time for the processing. 
034/05/78009	The capacities of the virtual volumes that are being used by the following program products cannot be expanded:\\n- Business Copy\\n- Fast Snap\\n- Auto LUN\\n- Continuous Access Synchronous\\n- Continuous Access Journal\\n- High Availability
034/05/78019	The operation cannot be executed, because the specified logical volume is not a Smart Tiers volume.
034/05/78032	The specified MP Unit is not mounted.
034/05/78047	Enough cache management devices cannot be allocated to the target volumes.
034/05/78049	The operation cannot be performed because the storage system is in the power-off process.
034/05/78061	The specified emulation type is different from the emulation type of the selected pool.
034/05/78062	The specified values of CU and pool ID do not follow the rule to create a volume of TSE attribute.
034/05/78063	A TSE-VOL cannot be associated with a pool where the smart pool setting is enabled.
034/05/78065	The storage system is in internal process, or a different user is changing the configuration.
034/05/78076	The operation cannot be performed because the specified virtual volume is set to online from the OS that does not support EAV.
034/05/78197	The operation cannot be performed because the additional shared memory is  being installed.
034/05/78198	The specified page range is not valid.
034/05/78199	The specified page tiering level of the tiering policy is invalid.
034/05/78200	The processing of this page cannot be performed because an error occurred during the process of a different page.
034/05/78264	The operation cannot be performed because the monitoring data is changing.
034/05/78266	The specified pool is not a Thin Provisioning pool.
034/05/8000	An error occurred during Remote Web Console processing.
034/05/8102	This function is not supported.
034/05/8958	An error occurred on the DKC side.
034/05/8966	An error occurred on the DKC side.
035/05/205028	The operation cannot be performed, because the total number of Fast Snap pairs under the specified root volumes exceeds 32,768.
035/05/208041	A pair cannot be created because of the migration attribute of the volume specified as the primary volume or the secondary volume.
035/05/208042	The operation cannot be performed because of the migration attribute of the volume specified as the primary volume or the secondary volume.
035/05/208043	A pair consisting of three secondary volumes cannot be created because of the migration attribute of the volume specified as the primary volume.
035/05/208044	The operation cannot be performed because of the migration attribute of the secondary volume of the specified pair.
035/05/208045	The volume specified as the primary volume is a migration volume of Online Migration. The operation cannot be performed because the setting of the  online data migration for the volume is not valid.
035/05/208047	The command cannot be run because the volume specified as the primary volume is a reserved volume of High Availability, or the status of the High Availability pair is not valid.
035/05/208048	The command cannot be run because the volume specified as the secondary volume is a reserved volume of High Availability, or the volume is used by the High Availability pair.
035/05/208049	The command cannot be run because the volume specified as the primary volume is a reserved volume of High Availability, or the status of the High Availability pair is not valid.
035/05/208050	The command cannot be run because the volume specified as the secondary volume is a reserved volume of High Availability, or the volume is used by the High Availability pair.
035/05/208051	The command cannot be run because the specified primary volume is not a primary volume of a Fast Snap pair.
035/05/208052	The command cannot be run because the specified pair does not exist.
035/05/208054	The command cannot be run because the specified pair has a secondary volume.
035/05/208055	The command cannot be run because the specified pair has no secondary volume.
035/05/208056	The command cannot be run because the specified pair has no secondary volume.
035/05/208057	The operation cannot be performed because the microcode versions of the SVP and the DKCMAIN do not match.
035/05/208058	The command cannot be run because the specified pair has a secondary volume.
035/05/208059	The processing cannot continue due to an internal logic contradiction.
035/05/208060	The processing cannot continue due to an internal logic contradiction.
035/05/208067	The operation cannot be performed because the specified primary volume is being migrated by Auto LUN.
035/05/208069	The operation cannot be performed because the specified secondary volume is being migrated by Auto LUN.
035/05/208071	The pair operation cannot be performed because local replication pairs are being initialized.
035/05/208072	The operation cannot be performed because the specified primary volume is an external volume with the data direct mapping enabled or a volume that belongs to a parity group with the capacity expansion enabled.
035/05/208073	The operation cannot be performed because the specified secondary volume is an external volume with the data direct mapping enabled or a volume that belongs to a parity group with the capacity expansion enabled.
035/05/208075	The pair operation cannot be performed because the T10 PI setting does not match between the specified primary volume and secondary volume.
035/05/208076	A pair cannot be created, because the number of cascade pair layers exceeds 64.
035/05/208077	A pair with the clone attribute cannot be created, because three such pairs exist in the layers from the specified primary volumes to the root volume in the highest layer.
035/05/208078	A pair cannot be created, because the snapshot groups contain both pairs with the snapshot attribute and pairs with the clone attribute.
035/05/208079	One or more pairs cannot be created, because a Fast Snap pair that uses the specified primary volume as the secondary volume is not in the PAIR or PSUS status.
035/05/208080	A pair cannot be created, because a pair belonging to the specified CTG exists in one of the layers from the specified primary volume to the root volume.
035/05/208081	Pairs with the clone attribute are specified.\\nThe following operations cannot be performed on pairs with the clone attribute:\\n- Deleting secondary volumes\\n- Changing secondary volumes\\n- Resynchronization\\n- Restoration
035/05/208082	The following operations cannot be performed, because one or more Fast Snap pairs are using the secondary volume of the specified pair as a primary volume:\\n- Deleting the secondary volume\\n- Changing the secondary volume
035/05/208083	One or more pairs cannot be split, because a Fast Snap pair that uses the primary volume of the specified pairs as the secondary volume is not in the PSUS status.
035/05/208084	The specified pairs with the clone attribute cannot be split, because the configuration of those pairs does not match the actual configuration.
035/05/208085	The pair cannot be deleted, because one or more Fast Snap pairs are using the secondary volume of the specified pair as a primary volume.
035/05/208086	The selected pairs cannot be resynchronized or restored, because one or more pairs whose status is not PAIR exist in layers lower than the layers of the selected pairs.
035/05/208087	The command cannot be run, because the shared memory needed to perform operations on Fast Snap cascade pairs or pairs with the clone attribute is not installed.
035/05/208088	The current DKCMAIN firmware version does not support the specified operation.
035/05/208089	Pairs cannot be created, because the secondary volumes are not Thin Provisioning volumes.
035/05/208090	An internal error occurred.
035/05/208091	Pairs with the clone attribute cannot be created, because no secondary volumes are specified.
035/05/208095	The command cannot be run, because zero pages are being reclaimed on the specified secondary volumes.
035/05/208096	The command cannot be run, because the capacities of the specified secondary volumes are being expanded.
035/05/208097	The command cannot be run, because the statuses of the specified secondary volumes are being changed.
035/05/208098	A pair cannot be created, because the cascade attribute setting differs from the settings of the pairs under the root volume. A pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled cannot exist under the root volume.
035/05/208099	Thin Provisioning volumes with the SLU attribute cannot be assigned as secondary volumes.
035/05/208100	The command cannot be run, because the specified primary volumes are being deleted.
035/05/208101	The command cannot be run, because the specified secondary volumes are being deleted.
035/05/208102	The operation cannot be performed, because the specified S-VOL is a V-VOL for Snapshot.
035/05/208431	The operation cannot be performed because the specified LDEV with the SLU attribute is not a THP V-VOL.
035/05/208463	The specified operation cannot be performed, because the pool capacity exceeds the subscription limit of the pool.
035/05/208501	The operation cannot be performed because a virtual LDEV ID is set for the specified LDEV.
035/05/208962	The operation cannot be performed because the DKCMAIN firmware version and the Remote Web Console software version do not match.
035/05/238701	The operation cannot be performed due to one of the following reasons:\\n- The specified LDEV with the SLU attribute is not a volume of a Fast Snap pair.\\n- The Fast Snap pair using the specified LDEV with the SLU attribute is not in the PAIR status.\\n- The specified LDEV with the SLU attribute is a volume of a Fast Snap pair with the fast clone attribute.
035/05/238716	The operation cannot be performed because the specified LDEV with the SLU attribute does not exist. The LDEV might be deleted by a different user or application.
035/05/238723	The operation cannot be performed due to one of the following reasons:\\n- The specified LDEV with the SLU attribute is not a volume of a Fast Snap pair.\\n- The Fast Snap pair using the specified LDEV with the SLU attribute is not in the PAIR status.
035/05/238724	The operation cannot be performed because the specified LDEV with the SLU attribute is bound to an LDEV with the ALU attribute.
035/05/238738	The operation cannot be performed because the capacity of the specified LDEV does not match that of the assigned LDEV.
035/05/238740	The operation cannot be performed because the specified LDEV with the SLU attribute is a THP V-VOL.
035/05/238844	An error occurred during internal processing on the storage system.
035/05/238852	The operation cannot be performed because the specified pool is not a Fast Snap pool.
035/05/238860	The operation cannot be performed because the specified pool number is not set within the available range.
035/05/265296	The operation cannot be performed because the specified SLU ID is not in valid format.
035/05/265297	The operation cannot be performed because the specified LDEV with the SLU attribute does not exist. The LDEV might be deleted by a different user or application.
035/05/265298	The operation cannot be performed because the specified SLU ID is not in valid format.
035/05/265299	The operation cannot be performed because the specified LDEV with the SLU attribute does not exist. The LDEV might be deleted by a different user or application.
035/05/265300	An error occurred during internal processing on the storage system.
035/05/265301	The operation cannot be performed because the specified start slot number exceeds the maximum slot number of the volume.
035/05/265302	The operation cannot be performed because the specified end slot number exceeds the maximum slot number of the volume.
035/05/265303	The operation cannot be performed because the specified number of slots exceeds the maximum for search.
035/05/265304	The operation cannot be performed due to one of the following reasons:\\n- The specified LDEV with the SLU attribute is not a volume of a Fast Snap pair.\\n- The Fast Snap pair using the specified LDEV with the SLU attribute is not in the PAIR status.
035/05/265305	The operation cannot be performed due to one of the following reasons:\\n- The specified LDEV with the SLU attribute is not a volume of a Fast Snap pair.\\n- The Fast Snap pair using the specified LDEV with the SLU attribute is not in the PAIR status.
035/05/265306	The operation cannot be performed due to one of the following reasons:\\n- The specified LDEV with the SLU attribute is not a volume of a Fast Snap pair.\\n- The Fast Snap pair using the specified LDEV with the SLU attribute is not in the PAIR status.
035/05/55264	The command was rejected because you tried to create a pair using a volume with VMA setting by Data Retention and a volume without VMA setting.
035/05/55301	You cannot create the pair because the licensed capacity of Open System Array Management is insufficient.
035/05/55645	Quick Restore cannot be performed because the specified pair is composed of the external volumes with different cache mode settings.
035/05/5625	An internal logic error occurred.
035/05/5626	The specified volume cannot be used because it is write-protected by Data Retention.
035/05/5655	The capacities of the volumes specified as the primary volume and the secondary volume do not match.
035/05/58000	The command has been rejected because the cascade request for creating cascade pairs composed of volumes belonging to the same consistency group was issued.
035/05/58001	The operation on the L2 pair cannot be performed because the L1 pair is in the COPY(SP)/COPY, PSUS(SP)/COPY, or COPY(RS-R)/RCPY status. Or the command cannot be run because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/58002	The Quick Restore command has been rejected because the specified pair is composed of a normal volume and a customized volume (CV).
035/05/58003	The command has been rejected because a Remote Copy pair exists in the same storage system frame.
035/05/5821	This operation has been rejected.\\nThe Data Retention setting does not allow the specified volume(s) to be specified as S-VOL(s).
035/05/58259	The Quick Restore command could not be executed because the specified pair contains external volumes and also is used as a remote replication pair.
035/05/58260	The command was rejected because the specified P-VOL is used as a P-VOL of a Continuous Access Synchronous pair.
035/05/58261	The command has been rejected, because the specified P-VOL is used as S-VOL of Continuous Access Synchronous pair.
035/05/58262	A pair cannot be created because shared memory for differential tables is in sufficient.
035/05/58299	The operation failed because the specified P-VOL was a data volume of Continuous Access Journal. \\nCheck the requirements for using the volume with Continuous Access Journal.
035/05/58300	The operation failed, because the specified S-VOL was a data volume of Continuous Access Journal.
035/05/58351	The Quick Restore command could not be executed because the specified pair contains external volumes, and also is used as a Continuous Access Journal pair.
035/05/58356	The command was rejected because the specified volume is used by the Continuous Access Journal and the Continuous Access Synchronous.
035/05/58451	The storage system is busy (internal processing).
035/05/58476	The operation cannot be performed, because the specified P-VOL is a P-VOL for Fast Snap.
035/05/58477	The operation cannot be performed, because the specified P-VOL is an S-VOL or a V-VOL for Fast Snap.
035/05/58478	The operation cannot be performed, because the specified P-VOL is a pool volume.
035/05/58479	The operation cannot be performed because the specified secondary volume is a primary volume of Business Copy or Fast Snap.
035/05/58480	The operation cannot be performed, because the specified S-VOL is an S-VOL or a V-VOL for Fast Snap.
035/05/58481	The operation cannot be performed, because the specified S-VOL is a pool volume.
035/05/58518	The operation failed, because the Fast Snap pair(s) existed.
035/05/58519	The operation failed, because the Fast Snap pair(s) existed.
035/05/58520	The operation failed, because different versions of microcodes coexisted in the storage system.\\n
035/05/58533	The operation failed, because the specified P-VOL was a journal volume.
035/05/58534	The operation failed, because the specified S-VOL was a journal volume.
035/05/58536	The operation could not be performed because the specified secondary volume is a Continuous Access Journal volume.
035/05/58579	The operation could not be performed because the specified volume is being shredded by Data Retention.
035/05/58582	The command has been rejected, because the specified S-VOL is used as P-VOL of Fast Snap or the specified MU number is already used.
035/05/58583	The operation failed because the volume was shared by a Fast Snap pair.
035/05/58584	The operation failed because the volume was shared by a Fast Snap pair in COPY (RS-R)/RCPY status.
035/05/58585	The operation failed because the CU group of the specified volume is not supported.
035/05/58630	The operation cannot be performed because the specified primary volume is used by a delta resync pair of Continuous Access Journal.
035/05/58631	The operation failed because the specified S-VOL was used by Delta resync of Continuous Access Journal.
035/05/58711	The operation could not be performed because the specified MU number is already used. 
035/05/58906	The operation failed because the volume specified as the P-VOL was used as the S-VOL of another pair and the volume specified as the S-VOL was used as the P-VOL of another pair already.
035/05/6502	Processing in progress. 
035/05/6503	The target volume status is being changed to SMPL.
035/05/6520	The command has been rejected, because the specified volume was registered in the Security Group that cannot specify T-VOL(Secondary Volume).
035/05/6537	The setting could not be applied because there is an error in a different setting.
035/05/68021	0 cannot be specified as the MU number of L2 pair.
035/05/68737	The command has been rejected, because the specified P-VOL is a Thin Provisioning volume not associated with a pool.
035/05/68738	The command has been rejected, because the specified S-VOL is a Thin Provisioning volume not associated with a pool.
035/05/68743	The command has been rejected, because Quick Format is performed on the specified S-VOL(Primary Volume).
035/05/68744	The command has been rejected, because Quick Format is performed on the specified S-VOL.
035/05/68745	FICON(R) Data Migration Source Volume is specified as a T-VOL. FICON(R) Data Migration Source Volume cannot be used as a T-VOL.
035/05/68746	The command has been rejected because the pair uses FICON(R) Data Migration Source Volume.
035/05/68747	The command has been rejected because the FICON(R) Data Migration source volume is used in the specified pair, and T-VOL is used by one of the following program products.\\n- Continuous Access Synchronous Z\\n- Continuous Access Journal Z\\n- Compatible FlashCopy Mainframe\\n- Array Management
035/05/68749	The command has been rejected, because the specified Continuous Access Asynchronous pair was not in PSUS status.
035/05/68750	The Quick Restore command has been rejected, because the specified pair is composed of the Thin Provisioning volume and the volumes other than Thin Provisioning volume.
035/05/68755	The Quick Restore command has been rejected, because device information (Inquiry information) of P-VOL and S-VOL was different in the specified pair.
035/05/68760	Quick Restore cannot be performed because the configuration is being backed up in the target volume. 
035/05/68767	The BC Operation for FICON(R) Data Migration failed because the specified pair consists of either a primary volume other than a FICON(R) Data Migration source volume or a secondary volume that is a FICON(R) Data Migration source volume.
035/05/68768	The SI Operation for FICON(R) Data Migration failed, because the pair status of the specified pair was not SIMPLEX or DUPLEX.
035/05/68769	The SI Operation for FICON(R) Data Migration failed, because the pair status of the specified pair was not Suspend(Mig.).
035/05/68770	The SI Operation for FICON(R) Data Migration failed because the Cache Residency Z setting was set in the T-VOL of the specified pair.
035/05/68771	The SI Operation for FICON(R) Data Migration failed, because the Volume Retention setting was set in the T-VOL of the specified pair.
035/05/68772	The SI Operation for FICON(R) Data Migration failed because the T-VOL of the specified pair was used by Continuous Access Journal Z.
035/05/68773	The SI Operation for FICON(R) Data Migration failed, because the T-VOL of the specified pair was used by Continuous Access Synchronous Z.
035/05/68774	The SI Operation for FICON(R) Data Migration failed, because the T-VOL of the specified pair was used by External Storage.
035/05/68775	The command could not be executed because the primary volume of the specified pair is a FICON(R) Data Migration source volume.
035/05/68776	The command could not be executed because the secondary volume of the specified pair is a FICON(R) Data Migration source volume.
035/05/68777	The command has been rejected, because the specified volume is a FICON(R) Data Migration Source Volume.
035/05/68808	The command has been rejected, because the specified P-VOL is a Thin Provisioning volume whose capacity is being added.
035/05/68809	The command has been rejected, because the specified S-VOL is a Thin Provisioning volume whose capacity is being added.
035/05/68832	The command has been rejected, \\nbecause the specified CTG is used by Fast Snap.
035/05/68834	The command has been rejected, because the specified CTG is used by Business Copy.
035/05/68835	The command could not be executed because the specified primary volume is used by a pair of Fast Snap that is registered in the CTG.
035/05/68836	The command has been rejected, \\nbecause the specified S-VOL is used by a pair of Snapshot, which is registered in the CTG.
035/05/68837	The command has been rejected, because the specified P-VOL is a volume of Thin Provisioning whose zero page is being reclaimed.
035/05/68838	The command has been rejected, because the specified S-VOL is a volume of Thin Provisioning whose zero page is being reclaimed.
035/05/68854	The SI Operation for FICON(R) Data Migration failed, because more than one T-VOL was assigned for the specified S-VOL.
035/05/68867	The command has been rejected, because the volume specified as P-VOL is a quorum disk.
035/05/68868	The command has been rejected, because the volume specified as S-VOL is a quorum disk.
035/05/68922	The specified P-VOL is a volume of using two mirrors, which are included in 3DC cascade, 3DC multi target, or Delta resync configuration. The operation for this P-VOL failed due to one of the following reasons.\\n- The specified volume was used by Delta resync of Continuous Access Journal.\\n- The specified volume was used by a data volume of Continuous Access Journal.\\n
035/05/68923	The specified secondary volume is a volume of using two mirrors, which is included in the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The operation for this secondary volume cannot be performed due to one of the following reasons:\\n- The specified volume is used by a delta resync pair of Continuous Access Journal.\\n- The specified volume is used by a data volume of Continuous Access Journal.
035/05/68924	The specified volume is a volume of using two mirrors, which are included in 3DC cascade, 3DC multi target, or Delta resync configuration. The operation for this volume failed due to one of the following reasons.\\n- The specified volume was used by Delta resync of Continuous Access Journal.\\n- The specified volume was used by a data volume of Continuous Access Journal.\\n
035/05/7310	This error code is not registered.
035/05/75002	The command was rejected, because the Thin Provisioning volume specified as P-VOL was not associated with a pool.
035/05/75003	The command was rejected, because the Thin Provisioning volume specified as S-VOL was not associated with a pool.
035/05/75005	The specified operation cannot be performed due to one of the following reasons:\\n- Performing a pair split or pair resync operation on a pair in the SMPL status.\\n- Specifying a volume with no LUN paths set as a primary volume to create a pair with the cascade attribute disabled.\\n- Performing a pair split or pair resync operation on a pair for which the cascade attribute is disabled and whose primary volume has no LUN paths.
035/05/75006	The specified operation cannot be performed due to one of the following reasons:\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing a secondary volume for a pair in the SMPL status.\\n- Specifying a volume with no LUN paths set for a secondary volume to create a pair with the cascade attribute disabled.\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing a secondary volume for a pair for which the cascade attribute is disabled and whose secondary volume has no LUN paths.
035/05/75008	The specified operation cannot be performed, because pairs under root volumes are being deleted.
035/05/78053	The operation failed because the current microcode version does not support the capacity of specified P-VOL.
035/05/78054	The operation failed because the current microcode version does not support the capacity of specified S-VOL.
035/05/78069	The operation failed because the emulation type of the specified S-VOL(Primary Volume) was 3390-V.
035/05/78070	The operation failed because the emulation type of the specified T-VOL(Secondary Volume) was 3390-V.
035/05/78071	The operation failed because the emulation type of the specified volume was 3390-V.
035/05/78072	3390-A cannot be used as an S-VOL(Primary Volume) due to one of the following reasons:\\n- The Mainframe Fibre CHA is not mounted.\\n- All the Mainframe Fibre CHAs are blocked.\\n
035/05/78073	3390-A cannot be used as a T-VOL(Secondary Volume) due to one of the following reasons:\\n- The Mainframe Fibre CHA is not mounted.\\n- All the Mainframe Fibre CHAs are blocked.\\n
035/05/78108	The command was rejected, because the pool associated with the Thin Provisioning volume that is specified as the P-VOL was being initialized.
035/05/78109	The command was rejected, because the pool associated with the Thin Provisioning volume that is specified as the S-VOL was being initialized.
035/05/78121	The operation failed because the specified S-VOL(Primary Volume) was used by Compatible FlashCopy SE, or was a TSE volume.
035/05/78122	The operation failed because the specified T-VOL(Secondary Volume) was a TSE volume.
035/05/78128	The operation cannot be performed because the specified volume is in the online data migration process.
035/05/78129	The operation cannot be performed because the volume specified as the primary volume is in the online data migration process.
035/05/78130	The operation cannot be performed because the volume specified as the secondary volume is a migration volume of Online Migration.
035/05/78139	The operation cannot be done because a pool cannot be used.
035/05/78140	The operation cannot be performed because the specified pool number is not the same as the pool number for the existing pairs.
035/05/78141	The operation cannot be done because the specified primary volume is a secondary volume of Fast Snap.
035/05/78142	The operation cannot be done because the specified secondary volume is a secondary volume of Fast Snap.
035/05/78143	The specified snapshot number is used in another pair of Fast Snap.
035/05/78144	The operation cannot be done because the license capacity has been exceeded.
035/05/78145	The command cannot be run in the current pair status.
035/05/78146	The command cannot be run because the command previously specified could not be run in the current pair status. Or the command cannot be run because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/78147	The operation cannot be performed, because a pool whose pool type is not Fast Snap is selected.
035/05/78148	The command was rejected because the specified volume was set unavailable to specify as a secondary volume.
035/05/78149	An error occurred during Fast Snap operations due to one of the following reasons:\\n- The LDEV number specified for the primary volume or secondary volume is wrong. \\n- The LDEV specified as the primary volume or secondary volume is not paired.\\n- The pair status of the specified primary volume or secondary volume is wrong.\\n- The specified Snapshot ID (MU number) is wrong.\\n- The specified Snapshot ID (MU number) is already used.\\n- The specified pool is not in a usable status.\\n- The license capacity has exceeded the maximum.\\n- The control table for Fast Snap or Snapshot is depleted.
035/05/78150	The command was rejected because the program product of Fast Snap or Business Copy was not installed.
035/05/78151	The command was rejected because the shared memory (FC, TPF, or Extension1) of necessary capacity was not installed.
035/05/78152	The command was rejected because the shared memory (SS1 or more) of necessary capacity was not installed.
035/05/78153	The LDEV number that is specified as a primary volume is invalid.
035/05/78154	The command was rejected because the emulation type of the specified primary volume was not OPEN-V.
035/05/78155	The operation cannot be done because the primary volume of Fast Snap is used as the primary volume of Continuous Access Synchronous, and the pair status of Continuous Access Synchronous is other than PSUS or PSUE.
035/05/78156	The operation cannot be done because the primary volume of Fast Snap is used as the primary volume of Continuous Access Journal, and the pair status of Continuous Access Journal is other than PSUS or PSUE.
035/05/78157	The operation cannot be done because a volume is used as the primary volume of Fast Snap and the secondary volume of Continuous Access Synchronous.
035/05/78158	The operation cannot be done because the primary volume of Fast Snap is used as the secondary volume of Continuous Access Journal.
035/05/78159	The operation cannot be done because VMA is set for the specified primary volume.
035/05/78160	The command was rejected because the emulation type of the specified secondary volume was not OPEN-V.
035/05/78161	The operation cannot be done because the specified secondary volume is an external volume.
035/05/78162	The operation cannot be done because the specified secondary volume is not a virtual volume.
035/05/78163	The command was rejected because the specified secondary volume was used as a primary volume of Continuous Access Journal.
035/05/78164	The command was rejected because the specified secondary volume was used as a secondary volume of Continuous Access Journal.
035/05/78165	The command was rejected because the specified volume was set unavailable to specify as a secondary volume.
035/05/78166	The operation cannot be done because VMA is set for the specified secondary volume.
035/05/78167	The command was rejected because the Max LBA size of the specified primary and the secondary volumes was different.
035/05/78168	The command was rejected because the number of slots is different between the specified primary and the secondary volumes. 
035/05/78169	The specified operation cannot be performed due to one of the following reasons:\\n- Assigning or changing a secondary volume for a pair in the SMPL status.\\n- Specifying a Thin Provisioning virtual volume as a secondary volume to create a pair with the cascade attribute disabled.\\n- Specifying a Thin Provisioning virtual volume as a secondary volume of a pair with the cascade attribute disabled to assign or change the secondary volume.
035/05/78171	The command was rejected because the specified secondary volume was used as a primary volume of Business Copy.
035/05/78172	The command was rejected because the specified secondary volume was used as a secondary volume of Business Copy.
035/05/78174	A pair of Fast Snap cannot be created due to one of the following reasons. \\n- The required capacity of shared memory is not installed. \\n- It is in the initializing process. 
035/05/78175	The specified operation cannot be done.
035/05/78176	The operation cannot be done because the PSUE option is specified.
035/05/78177	The operation cannot be done because a volume is used as the primary volume of Fast Snap and the secondary volume of Continuous Access Synchronous, and the pair status of Continuous Access Synchronous is COPY.
035/05/78178	The operation cannot be done because a volume is used as the primary volume of Fast Snap and the secondary volume of Continuous Access Journal, and the pair status of Continuous Access Journal is COPY.
035/05/78179	When the primary volume of Fast Snap and the primary volume of Business Copy volume share the volume, the MU number currently used by Business Copy cannot be specified.
035/05/78180	When the primary volume of Fast Snap and the secondary volume of Business Copy share the volume, 0 cannot be specified as a MU number of the primary volume for Fast Snap.
035/05/78181	The command was rejected because the primary volume of Fast Snap and the primary volume of Business Copy share a volume, and the pair of Business Copy was in re-synchronizing processing.
035/05/78182	The command was rejected because the primary volume of Fast Snap and the secondary volume of Business Copy share a volume, and the pair of Business Copy was not in the state of PSUS.
035/05/78183	The operation cannot be done because the primary volume of Fast Snap and the primary volume of Business Copy share a volume, and the pair status of Business Copy is other than PSUS or PSUE.
035/05/78184	The operation cannot be done because the primary volume of Fast Snap and the secondary volume of Business Copy share a volume, and the pair status of Business Copy is other than PSUS.
035/05/78185	The operation cannot be done because the pools or the pool volumes are blocked.
035/05/78186	A Snapshot pair cannot be restored due to one of the following reasons.\\n- Snapshot data of a restore target Snapshot pair is being obtained per consistency group.\\n- Snapshot data of another pair whose primary volume is the restore target Snapshot primary volume is being obtained.
035/05/78187	A Snapshot pair with consistency group number specified cannot be created due to one of the following reasons.\\n- The specified consistency group number is used by the Business Copy.\\n- The number of pairs defined in a consistency group exceeds the maximum.\\n- The pair created by using the same primary volume already exists in the specified consistency group.
035/05/78188	The specified consistency group number is invalid.
035/05/78189	The operation cannot be done because the primary volume of Fast Snap and the secondary volume of Continuous Access Synchronous asynchronous pair share a volume, and the status of Continuous Access Synchronous asynchronous pair is other than PSUS or PSUE.
035/05/78190	The operation cannot be done because the specified secondary volume is incorrect.
035/05/78191	The command was rejected because the program product of Fast Snap was not installed.
035/05/78195	The command was rejected because the primary volume is used as an external volume that is mapped for online data migration.
035/05/78196	The command was rejected because the secondary volume is used as an external volume that is mapped for online data migration.
035/05/78201	The operation cannot be performed due to one of the following reasons:\\n- With the current DKCMAIN firmware version, a THP pool cannot be used to store snapshot data.\\n- For the specified pool, Enable is selected for Smart Pool.\\n- For the specified pool, Enable is selected for Data Direct Mapping.
035/05/78202	The operation failed because the Fast Snap program product is not installed. 
035/05/78203	The operation failed because the microcode versions of SVP and DKCMAIN do not match.
035/05/78204	The operation failed because there are not enough cache management devices.
035/05/78205	The operation failed because the capacity of the specified volume exceeds 4 TB.
035/05/78207	The operation cannot be performed because there is a pair in the status of Quick Restore among Business Copy pairs that share a primary volume. Or the command cannot be run because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/78208	The operation failed because the specified pool number is wrong.
035/05/78210	A Fast Snap pair cannot be created because the consistency group used by the specified snapshot group is one of the following:\\n- The consistency group number is used by Business Copy. \\n- The number of pairs that can be defined in a consistency group exceeds the maximum.\\n- A pair created by using the same primary volume already exists in the consistency group .  
035/05/78255	The operation failed because the volume specified as the S-VOL is a root volume.
035/05/78256	The operation failed because the volume specified as the S-VOL is a node volume.
035/05/78257	The operation failed because the volume specified as the P-VOL is a leaf volume.
035/05/78258	The operation failed because the volume specified as the S-VOL is a leaf volume.
035/05/78259	The operation failed because the specified P-VOL that uses two mirrors in 3DC cascade, 3DC multi target, or Delta resync configuration is in one of the following statuses.\\n- The volume is in the Continuous Access Journal Delta resync configuration.\\n- The volume is a Continuous Access Journal data volume.
035/05/78260	The operation failed because the specified S-VOL that uses two mirrors in 3DC cascade, 3DC multi target, or Delta resync configuration is in one of the following statuses.\\n- The volume is in the Continuous Access Journal Delta resync configuration.\\n- The volume is a Continuous Access Journal data volume.
035/05/78261	The command ended abnormally because the specified MU number is out of the range that can be specified.
035/05/78289	A Fast Snap pair with the CTG mode specified cannot be created because all the consistency groups have already been defined.
035/05/78290	A Fast Snap pair cannot be created because the snapshot ID (MU number) that can be used for the volume specified as the primary volume is depleted.
035/05/78291	A Fast Snap pair cannot be created because all the snapshot groups have already been defined, or the number of pairs that can be registered in the specified snapshot group has exceeded the maximum.
035/05/78292	A Fast Snap pair in which a V-VOL of Thin Provisioning is set as the primary volume cannot be created because the Thin Provisioning pool is being initialized.
035/05/78293	Failed to create a Fast Snap pair because the Thin Provisioning pool is being initialized.
035/05/78294	The Add Pair (Paircreate) operation failed because the specified pair type does not match the specified pool type.
035/05/78310	The Fast Snap pair operation cannot be performed because all Fast Snap pairs that share the specified primary volume are in PSUE status.
035/05/8001	Time out error.
035/05/8500	Sufficient amount of shared memory is not installed or the program product is not installed.
035/05/8501	The command has been rejected, because the command specified last time is being processed.
035/05/8503	You cannot create the new pair, because a remote copy pair exists in the same storage system frame.
035/05/8504	The specified command cannot be run due to one of the following reasons:\\n- The current pair configuration or status, or volume status dose not meet the requirements for the command.\\n- A pair operation is performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time."
035/05/8505	The command cannot be run because the pair operation cannot be performed in the current pair status, or because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time."
035/05/8506	The command cannot be run because the specified secondary volume is used by the host.
035/05/8507	The Pairsplit (Split Pairs) command was issued to the pairs in a PSUS status.
035/05/8508	The Paircreate (Create Pairs) command was issued to the pairs in the PSUS status.
035/05/8509	The Pairsplit (Split Pairs) command with the QUIESCE specification was issued to a secondary boot device.
035/05/8510	The P-VOL Suspend command was issued to a secondary boot device.
035/05/8512	Cannot perform Pairresync (Resync Pairs) or Pairsplit-E (Suspend Pairs) operation because of the path group setting.
035/05/8513	The command could not be executed because the specified primary volume is used by the host.
035/05/8516	The number of P-VOL cylinders exceeds the maximum.
035/05/8517	The number of S-VOL cylinders exceeds the maximum.
035/05/8518	You cannot create a pair because the track format is different.
035/05/8519	The capacities of the volumes specified as the primary volume and the secondary volume do not match.
035/05/8520	The pair cannot be created because the volume types are different.
035/05/8521	The number of multiple copy jobs exceeded the maximum.
035/05/8522	The emulation type of the P-VOL is not supported.
035/05/8523	The emulation type of the S-VOL is not supported.
035/05/8525	An internal logic error occurred.
035/05/8526	An internal logic error occurred.
035/05/8527	An internal logic error occurred.
035/05/8528	An internal logic error occurred.
035/05/8529	An internal logic error occurred.
035/05/8530	An internal logic error occurred.
035/05/8531	An internal logic error occurred.
035/05/8532	The command has been rejected, because the P-VOL or the S-VOL is being used by the host.
035/05/8535	A processor failure was detected.
035/05/8536	A cache failure was detected.
035/05/8537	The cache capacities do not match.
035/05/8538	An SM failure was detected.
035/05/8539	There is not enough shared memory on the local storage system to create 4096 pairs.
035/05/8540	There is sufficient shared memory to create 4096 pairs, but initial storage system setup is required before creating pairs.
035/05/8541	There is sufficient shared memory to create 4096 pairs, and the initial storage system setup is complete.
035/05/8542	Failed to complete the initial shared memory setup.
035/05/8543	The shared memory size is different.
035/05/8544	16 Mbytes of shared memory is available.
035/05/8545	A power supply failure is detected.
035/05/8546	The command was rejected.  The PS OFF is in progress.
035/05/8547	A data transfer failure is detected (CHA).
035/05/8548	A data transfer failure is detected (DKA).
035/05/8549	The P-VOL is not implemented.
035/05/8550	The command could not be executed because the specified primary volume is blocked or used as a system disk.
035/05/8551	The primary volume is being formatted or shredded.
035/05/8552	This volume cannot be specified as an P-VOL because it is used as a command device.
035/05/8553	The S-VOL is not implemented.
035/05/8554	The command could not be executed because the specified secondary volume is blocked or used as a system disk.
035/05/8555	The secondary volume is being formatted or shredded.
035/05/8556	This volume cannot be specified as an S-VOL because it is used as a command device.
035/05/8557	The volume is not implemented.
035/05/8559	The volume is being formatted.
035/05/8560	This volume cannot be specified because it is used as a command device.
035/05/8569	The command cannot be run because the area of the differential table or the pair table to set pairs is not enough.
035/05/8570	The selected volume does not exist.
035/05/8572	The volume is already defined as a P-VOL.
035/05/8573	The volume is defined as a source volume for Auto LUN.
035/05/8574	The volume is defined as a target volume for Auto LUN.
035/05/8582	The emulation type of the target volume is being changed.
035/05/8583	The RAID level of the specified volume is not supported.
035/05/8586	The number of groups that can be set in the same storage system is invalid.
035/05/8587	The number of pairs that can be set in the same group is invalid.
035/05/8588	The specified group number is not set.
035/05/8589	The specified group name is invalid.
035/05/8590	The group name and the number do not match.
035/05/8591	The specified pair is already set in another group.
035/05/8592	The command was rejected because the licensed capacity was exceeded.
035/05/8593	The P-VOL is a source volume for Auto LUN.
035/05/8594	The P-VOL is a target volume for Auto LUN.
035/05/8595	The specified P-VOL does not exist.
035/05/8597	No more pairs can be created with the specified primary volume.
035/05/8598	The specified volume is not a P-VOL.
035/05/8599	The specified volume is already used as a primary volume.
035/05/8600	The RAID level of the specified volume is not supported.  
035/05/8601	The specified S-VOL (Primary Volume) cannot be paired with a backup server volume.
035/05/8602	The command has been rejected, because the specified P-VOL has already been used as S-VOL of the other pair.
035/05/8603	The target volume is set as a primary volume for Data Migration.
035/05/8604	The target volume is set as a secondary volume for Data Migration.
035/05/8605	The Pairresync (Resync Pairs) command was issued to a device in the SMPL status.
035/05/8606	The operation to create an L2 pair was rejected because the P-VOL of the L1 pair is used as the P-VOL of a Continuous Access Synchronous pair.
035/05/8607	The command cannot be run because the specified secondary volume is used as a primary volume of a Continuous Access Synchronous pair.
035/05/8608	The specified S-VOL is not defined.
035/05/8610	The S-VOL is a target volume for Auto LUN.
035/05/8611	The operation failed because the specified S-VOL was used as S-VOL of other pairs.
035/05/8612	The specified volume is not an S-VOL.
035/05/8613	The RAID level of the specified S-VOL is not supported.
035/05/8614	The command was rejected because the specified S-VOL is used as a P-VOL of a Continuous Access Synchronous pair.
035/05/8615	The command cannot be run because the specified secondary volume is used as a secondary volume of a Continuous Access Synchronous pair.
035/05/8616	The S-VOL is used as a primary volume for Data Migration.  
035/05/8617	The target S-VOL is used as a secondary volume for Data Migration.
035/05/8618	The S-VOL is already defined as a P-VOL.
035/05/8619	The specified S-VOL is defined as a source volume for Auto LUN.
035/05/8624	The command has been rejected, because there is no pair to be operated.
035/05/8625	The P-VOL(S-VOL) and S-VOL(T-VOL) have the same number.
035/05/8626	The SMPL command could not be executed because the quick split operation is in progress.
035/05/8627	The Pairresync operation has been rejected, because pair status is COPY(SP)/COPY.
035/05/8628	The operation of the L1 pair failed because the L2 pair was in COPY(SP)/COPY status or PSUS(SP)/COPY status.
035/05/8631	The specified CU number is invalid.
035/05/8632	The timing of issuing the command is invalid.
035/05/8633	The abnormal status is invalid.
035/05/8637	The specified P-VOL is used as a source volume for Auto LUN.
035/05/8638	The command could not be executed because the specified primary volume is set for use in Cache Residency.
035/05/8639	The command could not be executed because the specified secondary volume is set for use in Cache Residency.
035/05/8640	The command cannot be run because there is a pair in the status of Reverse Copy or Quick Restore among pairs that share a primary volume, or because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/8641	The L1 pairs contain a pair in the Reverse Copy or Quick Restore status.
035/05/8642	The command has been rejected, because the specified S-VOL is shared as the P-VOL of the other pair and the pair is in the COPY(RS-R)/RCPY status.
035/05/8643	The Resync Pairs operation cannot be performed because the specified pair is not in the PSUS status. Or the command cannot be run because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/8644	The operation failed because the pairs sharing a P-VOL contain a pair in other than PSUS or PSUE status.
035/05/8645	The Reverse Copy command could not be executed because the primary volume was shared with the primary volume of a remote replication pair.
035/05/8646	The Reverse Copy request was rejected, because the P-VOL was shared with a Remote Copy pair in the non-suspend status.
035/05/8647	The Reverse Copy command could not be executed because the secondary volume was shared with the primary volume of a remote replication pair.
035/05/8648	The boot device and the P-VOL do not match in the Paircreate (Create Pairs) command.
035/05/8649	Because the boot device is the S-VOL in the Pairsplit-S (Delete Pairs) command, the flag does not match.
035/05/8650	The boot device and the P-VOL do not match in the Paircreate (Create Pairs), Pairresync (Resync Pairs), or Pairsplit-S (Delete Pairs) command.
035/05/8651	The SSID is invalid.
035/05/8652	The boot device is not a P-VOL nor S-VOL.
035/05/8653	Because the boot device is the P-VOL in the Pairsplit-S (Delete Pairs) command, the flag does not match.
035/05/8654	Boot device and S-VOL do not match in Paircreate (Create Pairs), Pairresync (Resync Pairs), or Pairsplit-S (Delete Pairs) instruction.
035/05/8655	An invalid secondary SSID is specified for the Paircreate (Create Pairs) or Pairresync (Resync Pairs) command.
035/05/8656	The secondary SSID specified for the Pairsplit-S(Delete Pairs) or Pairsplit(Split Pairs) command is invalid.
035/05/8657	The Swap&Freeze option cannot be specified, because the mode 80 is on.
035/05/8695	The specified MU number is not less than or equal to 2.
035/05/8696	The command has been rejected, because the specified S-VOL(Primary Volume) is being used as a volume of a Compatible FlashCopy pair or a Compatible FlashCopy SE pair.
035/05/8697	The command has been rejected, because the specified T-VOL(Secondary Volume) is being used as the volume of a Compatible FlashCopy pair or a Compatible FlashCopy SE pair.
035/05/8698	The command could not be executed because the specified volume is being used as a volume of a Compatible FlashCopy pair or a Compatible FlashCopy SE pair.
035/05/8699	The command of Reverse Copy or Quick Restore has been rejected, because the specified S-VOL(Primary Volume) is being shared with the volume of a Compatible FlashCopy pair or a Compatible FlashCopy SE pair.
035/05/8920	The operation on the L2 pair cannot be performed because the L1 pair is not in the PSUS status. Or the command cannot be run because there is a pair operation that cannot be performed if it is done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
035/05/8941	Failed to make or cancel a reservation of consistency group. 
035/05/8946	A pair status cannot be changed because the Split time of Consistency Group is set.
035/05/8991	The command has been rejected, because the Compatible FlashCopy relationship exists.
035/05/8992	The command has been rejected, because sufficient amount of shared memory is not installed.
035/05/8993	The command has been rejected, because the shared memory is not set for Compatible FlashCopy.
035/05/8994	The command has been rejected, because the storage system is busy.
035/05/8995	The command has been rejected, because the Compatible FlashCopy relationship exists.
035/05/8996	The command has been rejected, because the storage system is busy.
040/10/2080	Prestaging not completed.
051/05/2003	An error occurred during Remote Web Console processing.
051/05/2007	An error occurred during Remote Web Console processing.
051/05/2015	Connection error.
051/05/2145	Connection error.
051/05/5010	An error occurred during Remote Web Console processing.
051/05/5013	An error occurred during Remote Web Console processing.
051/05/5099	An error occurred during Remote Web Console processing.
051/05/5202	This function is not available.Performance Monitor is required.
051/05/5400	Failed to access the monitoring data because accessing the monitoring data on the SVP is busy.
051/05/55113	An error occurred during Remote Web Console processing.
051/05/55114	There is no monitoring data. It might be deleted by another user's operation.
051/05/55500	An error occurred during Remote Web Console processing.
051/05/55501	An error occurred during Remote Web Console processing.
051/05/56524	This function cannot be used by the storage partition administrator.
051/05/56525	Because the settings across the multiple SLPRs are contained, the authority has been shifted to the storage administrator from the storage partition administrator.
051/05/56526	The resources of other SLPR(s) cannot be accessed.
051/05/6000	An error occurred during Remote Web Console processing.
051/05/6002	An error occurred during Remote Web Console processing.
051/05/6011	An error occurred during Remote Web Console processing.
051/05/6012	An error occurred during Remote Web Console processing.
051/05/6022	An error occurred during Remote Web Console processing.
051/05/6023	An error occurred during Remote Web Console processing.
051/05/6036	An error occurred during Remote Web Console processing.
051/05/6092	An error occurred during Remote Web Console processing.
051/05/6501	There is no monitoring data.
051/05/66016	A monitoring switch cannot be enabled with the specified gathering interval.
051/05/66017	An error occurred during SVP processing.
051/05/7007	An error occurred during Remote Web Console processing.
051/05/7111	An error occurred during Remote Web Console processing.
051/05/8002	The storage system status is invalid.
051/05/87777	The operation cannot be performed because a resource group is not locked.
051/07/5099	An error occurred during Remote Web Console processing.
051/07/6012	An error occurred during Remote Web Console processing.
051/21/105001	No table rows are selected.
051/21/105002	Two or more table rows are selected.
051/21/105003	No table row, or two or more table rows are selected.
051/21/107001	An internal logic error occurred.
051/21/109001	Are you sure you want to remove the selected row(s)?
051/21/109203	Are you sure you want to close the graph?
051/21/109204	The graph data will be deleted. Do you want to continue?
051/21/109206	The monitored CUs will be deleted. Do you want to continue?
051/21/109207	The monitored WWNs will be deleted. Do you want to continue?
051/21/109209	Some of Short-Range graphs cannot be displayed because no WWN to be monitored is set. Do you want to continue?
051/22/105101	The specified term of displaying graph is invalid.
051/22/105102	The content has not been edited.
051/22/105103	The specified HBA WWN is duplicated in the DKC.
051/22/105104	The specified WWN Name is duplicated in the WWN to be monitored.
051/22/105105	There is no editable WWN as a target of monitoring.
051/22/105106	The WWN cannot be added, because that WWN Name is duplicated in the WWN to be monitored.
051/22/105107	The content has not been edited.
051/22/105108	There is no available port to specify.
051/22/105109	There are no monitoring WWNs to be deleted.
051/22/105110	A new graph cannot be added, because the number of graph display objects has reached the maximum. 
051/22/105111	No more graph items can be added because the total number of graph items that can be displayed in all of the panels has reached the maximum.
051/22/105112	The graph cannot be displayed, because there is no graph data.
051/22/105113	The real time graph display will end due to changing the monitoring switch. 
051/22/105114	A CU to be monitored cannot be added because the number of CUs that can be specified exceeds the maximum.
051/22/105115	A WWN to be monitored cannot be added, because the number of graph display objects exceeds the maximum.
051/22/105116	A WWN to be monitored cannot be added, because the number of graph display objects per one port exceeds the maximum.
051/22/105226	The Graph Display Term cannot be changed, because there is no graph data.
051/22/105227	The HBA WWN is unedited.
051/22/105228	The WWN Name is unedited.
051/22/105229	No more WWNs to be monitored can be added, because the number of monitoring WWNs has reached the maximum.
051/22/105230	There are no selectable parity groups.
051/22/105247	The storage system is in internal process, or some other user is changing the configuration. Wait, then retry the operation.
051/22/105254	No more graph items can be added because the number of graph items that can be displayed in one graph panel has reached the maximum.
051/22/107001	The processing cannot continue due to an internal logic contradiction.
051/22/107002	The processing cannot continue due to an internal logic contradiction.
051/22/107003	The processing cannot continue due to an internal logic contradiction.
051/22/107004	The processing cannot continue due to an internal logic contradiction.
051/22/107005	The processing cannot continue due to an internal logic contradiction.
051/22/107015	The processing cannot continue due to an internal logic contradiction.
051/22/205024	The specified term of displaying graph is invalid.
051/22/205096	A CU to be monitored cannot be added because the number of CUs that can be specified exceeds the maximum.
052/05/1087	The volume specified as a migration target is being formatted or shredded.
052/05/1117	The volume specified as a migration source is already used as a volume of Concurrent Copy.
052/05/1118	The volume specified as a migration target is already used as a volume of Concurrent Copy.
052/05/1207	The volume types do not match.
052/05/1210	The shared memory to set a plan is insufficient.
052/05/1212	The source volume(s) is not equipped.
052/05/1213	The command was rejected due to one of the following reasons.\\n- The volume specified as a migration source was blocked.
052/05/1214	The volume specified as a migration source is being formatted or shredded.
052/05/1215	The volume specified as a migration source is a command device.
052/05/1216	The target volume(s) is not equipped.
052/05/1217	The command was rejected due to one of the following reasons.\\n- The volume specified as a migration target was blocked.
052/05/1218	The volume specified as a migration target is being formatted or shredded.
052/05/1219	The volume specified as a migration target is a command device.
052/05/1221	The volume(s) are already used by Auto LUN.
052/05/1222	The number of the Business Copy Z or Business Copy pair volumes has reached the maximum.
052/05/1223	The volume(s) are already used by Auto LUN.
052/05/1224	The volume(s) are already used by Auto LUN.
052/05/1225	The selected source volume and destination volume are the same volume.
052/05/1229	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1230	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1231	The volume(s) is already being used by Data Migration.
052/05/1232	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1233	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1234	The volume specified as a migration target cannot be migrated because it is used as P-VOL of Continuous Access Synchronous, or Continuous Access Synchronous Z.
052/05/1235	The volume specified as a migration target cannot be migrated because it is used as S-VOL or R-VOL of  Continuous Access Synchronous, or Continuous Access Synchronous Z.
052/05/1237	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1238	The specified volume(s) are already used by Business Copy Z or Business Copy.
052/05/1239	The volume(s) is already being used by Data Migration.
052/05/1606	The program product of Auto LUN is not installed.
052/05/1611	The specified volume has Read Only/Protect/SVOL Disable setting of Data Retention.
052/05/2003	The operation cannot be performed because the storage system is being maintained, or in internal process.
052/05/2011	The storage system is busy.
052/05/208389	A deduplication system data volume cannot be set as the source volume.
052/05/208390	A deduplication system data volume cannot be set as the target volume.
052/05/208399	The operation cannot be performed, because THP V-VOLs whose capacity saving status is not Disabled are selected.
052/05/208543	The volume specified as a migration source cannot be used because it is a secondary volume of a Business Copy pair whose primary volume has the nondisruptive migration attribute.
052/05/208544	The volume specified as a migration target cannot be used because of the nondisruptive migration attribute of the volume.
052/05/208545	Online Migration is not installed.
052/05/208546	The extended shared memory for Auto LUN is not installed.
052/05/208548	The specified migration plan cannot be canceled because the volume migration is already in the final step.
052/05/208600	The volumes specified as migration source volumes cannot be migrated because they are external volumes with the data direct mapping enabled or belong to parity groups with the capacity expansion enabled.
052/05/208601	The volumes specified as migration target volumes cannot be migrated because they are external volumes with the data direct mapping enabled or belong to parity groups with the capacity expansion enabled.
052/05/208602	The migration cannot be performed because T10 PI setting values differ between the specified source volume and target volume.
052/05/3003	An error occurred during SVP processing.
052/05/5013	An error occurred during SVP processing.
052/05/5099	An error occurred during SVP processing.
052/05/5203	This functionality is not available because Auto LUN is not installed.
052/05/5504	The specified volume cannot be migrated because it is used as S-VOL in the following status.\\n- A volume of Continuous Access Synchronous, or Continuous Access Synchronous Z in the Pending status.
052/05/5505	The volume(s) is already being used by Remote Copy.
052/05/55059	The specified volumes cannot be used for migration, because the specified source volume is a Continuous Access Synchronous volume, or a Continuous Access Synchronous Z volume, and the specified target volume is an external volume.
052/05/5506	The specified volume cannot be migrated because it is used as P-VOL in the following status.\\n- A volume of Continuous Access Synchronous, or Continuous Access Synchronous Z in the Pending status.
052/05/55060	The specified volume migration plan cannot be performed because a volume on which VMA for Data Retention is set is paired with a volume on which VMA is not set.
052/05/5507	The specified volume is not defined as the target volume of Auto LUN.
052/05/5510	This function is already in progress.
052/05/55201	If the migration source volume is a normal volume, a CVS volume of the same capacity as the migration source volume cannot be specified as the migration target volume. If the migration source volume is a CVS volume, a normal volume of the same capacity as the migration source volume cannot be specified as the migration target volume.
052/05/55207	The auto migration plans cannot be created because "None" is specified in "Sampling Term".
052/05/55223	The owner ID of the storage system used by the user does not match the owner ID of the specified target volume.
052/05/55225	The specified plan is the one created by other than Remote Web Console.
052/05/55226	The specified plan is the one created by other than Remote Web Console.
052/05/55258	The volume(s) are already being used as a data volume by Continuous Access Journal or Continuous Access Journal Z.
052/05/55259	The volume(s) are already being used as a data volume by Continuous Access Journal or Continuous Access Journal Z.
052/05/55500	An error occurred during SVP processing.
052/05/55521	The specified volumes are already usedas the volumes of Fast Snap.
052/05/55522	The specified volume(s) are already being used as V-VOL(s).
052/05/55523	The specified volume(s) are already being used as Pool-VOL(s).
052/05/55524	The specified volumes are already usedas the volumes of Fast Snap.
052/05/55525	The specified volume(s) are already being used as V-VOL(s).
052/05/55526	The specified volume(s) are already being used as Pool-VOL(s).
052/05/55530	The specified volumes are already usedas the volumes of Fast Snap.
052/05/55550	The volume(s) are already being used as a JNL volume by Continuous Access Journal or Continuous Access Journal Z.
052/05/55551	The volume(s) are already being used as a JNL volume by Continuous Access Journal or Continuous Access Journal Z.
052/05/55552	The specified source volume is a Continuous Access Journal volume or a Continuous Access Journal Z volume, andthe specified target volume is an external volume. Therefore, the specified volumes cannot be used for migration.
052/05/55586	The specified volume cannot be migrated, because it is in the shredding operation.
052/05/55592	An error occurred during SVP processing.
052/05/55593	An error occurred during SVP processing.
052/05/55598	The specified volume is used as a Delta resync volumefor Continuous Access Journal or Continuous Access Journal Z.
052/05/55599	The volume specified as a migration target is used as a volume of Delta resync for Continuous Access Journal or Continuous Access Journal Z.
052/05/55646	Migration between external volumes with different cache modes is invalid.
052/05/56301	An error occurred during SVP processing.
052/05/56302	An error occurred during SVP processing.
052/05/56303	An error occurred during SVP processing.
052/05/56524	This function cannot be used by the storage partition administrator.
052/05/57101	An error occurred during SVP processing.
052/05/57102	An error occurred during SVP processing.
052/05/58451	The storage system is busy (internal processing).
052/05/58572	An error occurred on the DKC side.
052/05/58574	An error occurred while connecting to the storage system.
052/05/58575	An error occurred while connecting to the storage system.
052/05/58576	A communication time-out error occurred in the storage system.
052/05/6000	An error occurred during SVP processing.
052/05/6012	An error occurred during SVP processing.
052/05/6022	The system failed to access the file.
052/05/6023	An error occurred during SVP processing.
052/05/6036	An error occurred during SVP processing.
052/05/6050	An error occurred during SVP processing.
052/05/6502	Processing in progress. 
052/05/6510	The storage system is busy.
052/05/6511	Please check pair status.
052/05/6512	Please check pair status.
052/05/65434	The specified volume(s) are the leaf volume(s) of Business Copy.
052/05/65673	The specified volume(s) are already being used as of THP V-VOL(s).
052/05/65674	The specified volume(s) are already being used as of THP V-VOL(s).
052/05/65697	The volume specified as a migration source cannot be used, because it is in quick formatting.
052/05/65698	The volume specified as a migration target cannot be used, because it is in quick formatting.
052/05/65705	The specified volume cannot be moved because it is a Thin Provisioning volume that is not associated with a pool.
052/05/65706	The specified volume cannot be moved because it is a Thin Provisioning volume that is not associated with a pool.
052/05/65708	Migration cannot be performed because the Thin Provisioning volume that is the migration source and the Thin Provisioning volume that is the migration target are contained in the same pool.
052/05/65709	The specified following volumes cannot be migrated. The migration source volume is shared by a P-VOL or an S-VOL of Continuous Access Journal or Continuous Access Synchronous, and the migration target volume is a Thin Provisioning volume.
052/05/65714	Because the composition is being backed up, a volume concerned cannot be moved.
052/05/65737	The specified volume cannot be used, because it is a volume of Thin Provisioning whose capacity is being added.
052/05/65738	The volume specified as a migration target cannot be used, because it is a volume of Thin Provisioning in capacity expanding.
052/05/65740	The configuration changing processes are conflicting at DKC.
052/05/65748	The volume specified as a migration source cannot be used, because it is a volume of Thin Provisioning in zero page reclaiming.
052/05/65749	The volume specified as a migration target cannot be used, because it is a volume of Thin Provisioning in zero page reclaiming.
052/05/65784	The volume specified as a migration source cannot be used because it is a quorum disk.
052/05/65785	The volume specified as a migration target cannot be used because it is a quorum disk.
052/05/65786	The pair operation cannot be performed because the volume specified as a migration source is a reserved volume of High Availability or used by a High Availability pair.
052/05/65787	The pair operation cannot be performed because the volume specified as a migration target is a reserved volume of High Availability or used by a High Availability pair.
052/05/65815	The specified volume is a volume of using two mirrors, which is included in the multi-target, the cascade, or the Delta resync configuration of a Continuous Access Journal pair.
052/05/65816	The specified volume is a volume of using two mirrors, which is included in the multi-target, the cascade, or the Delta resync configuration of a Continuous Access Journal pair.
052/05/65817	The specified volume is a volume of using two mirrors, which is included in the multi-target, the cascade, or the Delta resync configuration of a Continuous Access Journal pair.
052/05/7060	An error occurred during SVP processing.
052/05/7111	An error occurred during SVP processing.
052/05/75008	The volume specified as a migration target volume has an LU path setting.
052/05/75010	The number of target volumes that could be executed at once exceeds the maximum.
052/05/75035	The volume specified as a migration source cannot be used, because the THP Pools are being initialized.
052/05/75036	The volume specified as a migration target cannot be used, because the THP Pools are being initialized.
052/05/76503	The specified LDEV belongs to a resource groupthat you do not have permission to access.
052/05/76504	The specified LDEV belongs to a resource groupthat you do not have permission to access.
052/05/76505	The specified LDEV belongs to a resource groupthat you do not have permission to access.
052/05/76506	The specified parity group belongs to a resource groupthat you do not have permission to access.
052/05/76520	LDEVs specified as migration source volume and target volume, or parity groups contain the LDEVs, belong to different resource groups.
052/05/78056	The operation failed, because the current microcode version does not support the capacity of the specified source volume.
052/05/78057	The operation failed, because the current microcode version does not support the capacity of the specified target volume.
052/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
052/05/78131	The volume specified as a migration source cannot be used because the volume settings for the online data migration are not valid.
052/05/78132	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
052/05/78133	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
052/05/8001	An error occurred while connecting to the storage system.
052/05/8002	The storage system status is invalid.
052/05/8525	An internal logic error occurred.
052/05/8526	An internal logic error occurred.
052/05/8528	An internal logic error occurred.
052/05/8529	An internal logic error occurred.
052/05/8530	An internal logic error occurred.
052/05/8531	An internal logic error occurred.
052/05/8671	The sizes of the source and the target volumes are not equal.
052/05/87777	The operation cannot be performed because a resource group is not locked.
052/21/205001	No table rows are selected.
052/21/205007	No table row is selected.
052/21/209009	Are you sure you want to delete the selected migration plans?
052/21/209011	Are you sure you want to delete the selected rows?
052/22/206086	There is no operational history that can be displayed on the select page.
052/22/206088	There is no migration plan.
052/22/206089	The selected migration plan cannot be deleted because the migration plan is created by a different program.
052/22/206090	Nine or more migration plans are selected. You can only delete up to eight migration plans at once.
052/22/206091	The selected migration plan cannot be deleted because the source volume belongs to a resource group that you do not have permission to access.
052/22/206092	The selected migration plan cannot be deleted because the target volume belongs to a resource group that you do not have permission to access.
052/22/206093	The selected migration plan cannot be deleted because it does not exist anymore.
052/22/206094	The operation cannot be performed because the program product is not installed or you do not have permission to edit.
052/22/206095	The selected LDEV does not exist in the configuration.
052/22/206096	Migration plans cannot be created because the target volume for the selected volume does not exist.
052/22/206097	The volume that can be used to create migration plans does not exist.
052/22/206098	You can only create up to eight migration plans.
052/22/206099	If the migration plan is performed, the ratio of the used capacity to the total pool capacity will exceed the depletion threshold for a pool that is associated with the target volume. Do you want to continue this operation?
052/22/206100	If the migration plan is performed, the ratio of the used capacity to the total pool capacity will exceed the warning threshold for a pool that is associated with the target volume. Do you want to continue this operation?
052/22/206101	The migration plan cannot be performed because the ratio of the used capacity to the total pool capacity is equal to or greater than 100% for a pool that is associated with the target volume.
052/22/206103	The operation cannot be performed because the selected volume is not an external volume, an internal volume, or a THP-VOL.
052/22/206104	This volume cannot be selected because it is used as a pool volume.
052/22/206105	This volume cannot be selected because it is used as a journal volume.
052/22/206107	This volume cannot be selected because the volume belongs to a resource group that you do not have permission to access.
052/22/206108	This volume cannot be selected because it is being migrated.
052/22/206109	This migration plan extends across multiple CLPRs. Do you want to continue this operation?
052/22/206111	This volume cannot be selected because it is set as a command device.
052/22/206114	This volume cannot be selected because it is an external volume mapped for online data migration.
052/22/206115	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with resource group ID 1023.
052/22/206170	The specified LDEV is a reserved volume of High Availability.
052/22/206172	The selected LDEV cannot be migrated because the capacity expansion is enabled.
052/22/206220	The operation cannot be performed, because one or more deduplication system data volumes are specified.
052/22/207006	An internal logic error occurred.
053/05/1064	The specified WWN is already being used.
053/05/1258	This port is not properly equipped.
053/05/2002	An error occurred during SVP processing.
053/05/2015	A connection error has occurred.
053/05/2145	A connection error has occurred.
053/05/3003	An error occurred during Remote Web Console processing.
053/05/5000	The WWN should be input with hex digits (0-9 and A-F) and 16 characters.
053/05/5010	An error occurred during Remote Web Console processing.
053/05/5013	An error occurred during SVP processing.
053/05/5099	An error occurred during Remote Web Console processing.
053/05/5101	Target WWN not registered.
053/05/5102	The specified PFC group is not registered.
053/05/5104	The specified PFC group is already registered.
053/05/5105	Target Port(s) not equipped with monitored WWN(s).
053/05/5106	Target WWN already registered with port.
053/05/5107	Specified name already in use.
053/05/5108	Specified name already in use.
053/05/5109	Number of WWN(s) exceeds the maximum in the port.
053/05/5110	Number of WWN(s) exceeds the maximum.
053/05/5111	The number of the WWNs exceeds the maximum number that can be registered on a PFC group.
053/05/5112	The specified WWN is registered on a PFC group.
053/05/5113	The specified WWN is registered on a PFC group.
053/05/5114	Target WWNs have different attribute.
053/05/5204	This function is not available.Performance Monitor is required.
053/05/55500	An error occurred during Remote Web Console processing.
053/05/56301	An error occurred during Remote Web Console processing.
053/05/56302	An error occurred during Remote Web Console processing.
053/05/56303	An error occurred during Remote Web Console processing.
053/05/56524	This function cannot be used by the storage partition administrator.
053/05/56525	Because the settings across the multiple SLPRs are contained, the authority has been shifted to the storage administrator from the storage partition administrator.
053/05/56526	The resources of other SLPR(s) cannot be accessed.
053/05/57101	An error occurred during Remote Web Console processing.
053/05/57102	An error occurred during Remote Web Console processing.
053/05/58572	An error occurred while connecting to the storage system.
053/05/58574	An error occurred while connecting to the storage system.
053/05/58575	An error occurred while connecting to the storage system.
053/05/58576	A communication time-out error occurred in the storage system.
053/05/6000	An error occurred during Remote Web Console processing.
053/05/6012	An error occurred during Remote Web Console processing.
053/05/6022	A file open error has occurred.
053/05/6023	File access error occurred.
053/05/6036	An error occurred during SVP processing.
053/05/6050	An error occurred during Remote Web Console processing.
053/05/6051	An error occurred during Remote Web Console processing.
053/05/7111	An error occurred during Remote Web Console processing.
053/05/7428	An error occurred during Remote Web Console processing.
053/05/75040	This functionality is not available because Performance Control is not installed.
053/05/76510	The specified port belongs to a resource group that you do not have permission to access.
053/05/78117	Performance Control cannot be operated from Remote Web Console because settings for Performance Control have been made on this storage system from RAID Manager.
053/05/8002	The storage system status is invalid.
053/05/87777	The operation cannot be performed because a resource group is not locked.
053/05/8918	An error occurred during Remote Web Console processing.
053/05/8919	The storage system status is invalid.
053/05/8971	An error occurred during Remote Web Console processing.
053/07/5099	An error occurred during Remote Web Console processing.
053/07/5102	The specified PFC group is not registered.
053/07/5128	The number of the PFC groups exceeds the maximum number that can be registered.
053/07/6012	An error occurred during Remote Web Console processing.
053/10/1110	You can not use the following characters for the name:\ / , : ; * ? " < > | You cannot use leading and trailing spaces in the name.
053/10/5000	The specified WWN is invalid.
053/10/5067	The maximum value is not set for the non-priority port.
053/10/5068	The value is not set for the overall control.
053/10/5069	The maximum value is not set for the non-priority WWN.
053/10/5107	The specified name is already used.
053/10/5108	The specified name is already used.
053/10/5109	The number of WWNs of the specified port exceeds the maximum that can be monitored.
053/10/5110	The number of WWNs to be monitored exceeds the maximum that can be registered in the entire storage system.
053/10/5111	The entered value exceeds the maximum number of WWNs that can be registered in a Performance Control group.
053/10/5128	The entered value exceeds the maximum number of Performance Control groups that can be registered.
053/10/5129	The specified WWN is already registered in another Performance Control group.
053/10/5134	The attribute of the WWN is different from that of the Performance Control group.
053/10/5136	The input WWN is already registered as a different nickname.
053/10/59000	The Performance Control group extends across multiple SLPRs. Do you want to continue?
053/10/6518	Delete the WWN from the Performance Control group first.
053/10/6519	Do you want to change the WWNs of other ports too?
053/10/65733	WWN cannot be registered because the number of WWNs of one of the ports to be monitored at the same time exceeds the maximum.
053/10/9077	Are you sure you want to delete the WWN?
053/10/9078	Are you sure you want to delete the Performance Control group?
053/10/9079	The Performance Control group is deleted because no WWN is registered in the Performance Control group.
053/10/9312	The control status will change to "Port Control".
053/10/9313	The control status will change to "WWN Control".
053/10/9315	The monitoring switch is turned OFF.
053/10/9326	The control status will change to "No Control".
053/10/9328	The settings for the removed ports remain.
053/10/9329	Next, the initialization for the settings on Port control will be performed.
053/10/9330	Next, the initialization for the settings on WWN control will be performed.
053/10/9331	The specified WWN is already in use.
053/10/9333	Do you want to change the control status to Port Control?
053/10/9334	Do you want to change the control status to WWN Control?
053/10/9335	Do you want to change the control status to No Control?
060/05/208008	The shared memory required for the specified operation is not installed on the local storage system.
060/05/208010	The shared memory required for the specified operation is not installed on the remote storage system.
060/05/208018	The operation cannot be performed because the specified primary volume is a reserved volume of High Availability.
060/05/208019	The operation cannot be performed because the specified secondary volume is a reserved volume of High Availability.
060/05/208050	The specified primary volume is used by a High Availability pair.
060/05/208051	The specified secondary volume is used by a High Availability pair.
060/05/208052	The operation cannot be performed because different firmware versions coexist on the storage system.
060/05/208093	The operation cannot be performed because Data Direct Mapping is enabled on the specified primary volume but the remote storage system does not support Data Direct Mapping.
060/05/208521	The operation cannot be performed because the specified primary volume is an Online Migration volume.
060/05/208522	The local storage system does not support Online Migration.
060/05/208523	The remote storage system does not support Online Migration.
060/05/208524	The Create Pairs operation cannot be performed because no virtual LDEV ID is set on the volume specified as the secondary volume.
060/05/208525	The Create Pairs operation cannot be performed because no virtual LDEV ID is set on the volume specified as the primary volume.
060/05/208527	The operation cannot be performed because the T10 PI setting differs between the primary volume and the secondary volume.
060/05/5013	An error occurred during Remote Web Console processing.
060/05/58319	The pair operation cannot be performed due to either of the following reasons:\\n- The specified primary volume is used by Continuous Access Journal.\\n- A storage system that does not support the specified pair configuration is included.
060/05/58320	The pair operation cannot be performed due to either of the following reasons:\\n- The specified secondary volume is used by Continuous Access Journal.\\n- A storage system that does not support the specified pair configuration is included.
060/05/58322	The Create Pairs operation cannot be performed because the specified secondary volume is a LUSE volume that is set across multiple CLPRs.
060/05/58357	A pair cannot be created, because you tried to create a volume pair formed with a volume to which VMA is set by Data Retention and a volume without VMA.
060/05/58358	A pair cannot be created using the specified primary volume because the setting process of VMA that is used for Data Retention is not yet complete.
060/05/58359	A pair cannot be created using the specified secondary volume because the setting process of VMA that is used for Data Retention is not yet complete.
060/05/58451	The storage system is in internal process. Please retry the operation. 
060/05/58452	The operation cannot be performed because the licensed capacity of Open Array Management on the remote storage system is not enough or Open Array Management is not installed on the remote storage system.
060/05/58454	The operation cannot be performed because the licensed capacity of Open Array Management on the remote storage system is not enough or Open Array Management is not installed on the local storage system.
060/05/58460	The specified primary volume is already used as a primary volume for Continuous Access Journal.
060/05/58494	A pair cannot be created because the specified primary volume is being used by Fast Snap.
060/05/58495	A pair cannot be created because the specified secondary volume is being used by Fast Snap or Snapshot.
060/05/58496	A pair cannot be created because the specified primary volume is a virtual volume.
060/05/58497	A pair cannot be created because the specified secondary volume is a virtual volume.
060/05/58498	A pair cannot be created because the specified primary volume is being used as a pool volume.
060/05/58499	A pair cannot be created because the specified secondary volume is being used as a pool volume.
060/05/58509	A communication time-out error occurred between the local storage system and the remote storage system.
060/05/58568	A pair cannot be created because the specified primary volume is being shredded by Data Retention.
060/05/58569	A pair cannot be created because the specified secondary volume is being shredded by Data Retention.
060/05/58586	The operation cannot be performed because the specified volume cannot be used as a secondary volume due to a host setting.
060/05/58712	The licensed capacity of TrueCopy on the remote storage system is not enough.
060/05/58714	The licensed capacity of Continuous Access Synchronous on the local storage system is not enough.
060/05/6012	An error occurred during Remote Web Console processing.
060/05/6023	An error occurred during Remote Web Console processing.
060/05/6537	The setting cannot be applied because there is an error in a different setting.
060/05/65740	The operation cannot be performed because a configuration change is in progress in the local storage system.
060/05/68011	The operation cannot be performed because the specified primary volume is being used as a Thin Provisioning volume.
060/05/68012	The operation cannot be performed because the specified secondary volume is being used as a Thin Provisioning volume.
060/05/68020	The setting of Maximum Initial Copy Activities (CU) cannot be changed to Enable or Disable, because there are pairs in the  COPY or Pending status.
060/05/68022	The specified primary volume is used as a pair volume of Continuous Access Journal. The operation cannot be performed because Cont Access Journal 3DC & 4x4 Open MF is not installed on the local storage system.
060/05/68023	The specified secondary volume is used as a pair volume of Continuous Access Journal. The operation cannot be performed because Cont Access Journal 3DC & 4x4 Open MF is not installed on the remote storage system.
060/05/68027	The operation cannot be performed because the remote storage system does not support the CU or the LUN ID of the specified primary volume.
060/05/68757	The pair cannot be created because the specified secondary volume, which is a Thin Provisioning volume, is already used by a different program product.
060/05/68758	The Create Pairs operation cannot be performed because the volume specified as the secondary volume is a system disk.
060/05/68787	The operation failed because the Continuous Access Synchronous function was not installed.
060/05/68789	The pair cannot be created because the Continuous Access Synchronous function is not installed on the remote storage system.
060/05/68791	The operation cannot be performed because the specified volume is not a secondary volume.
060/05/68793	The Reverse Resync operation failed because the status of the specified volume was not SSWS.
060/05/68795	The operation cannot be performed. The shared memory might not be enough.
060/05/68796	The operation failed. The operation cannot be accepted in the pair status of the specified volume.
060/05/68812	A pair cannot be created because the specified secondary volume is a Thin Provisioning volume whose capacity is being changed.
060/05/68813	A pair cannot be created because the specified primary volume is a Thin Provisioning volume whose capacity is being changed.
060/05/68816	A pair cannot be created because the specified volume is used as a primary volume of Continuous Access Journal.
060/05/68826	The operation failed, because the External Storage function was not installed.
060/05/68827	The operation failed, because there was an error in the specified parameter.
060/05/68844	The operation cannot be performed because the specified primary volume is a volume of Thin Provisioning in the zero page reclamation.
060/05/68845	The operation cannot be performed because the specified secondary volume is a volume of Thin Provisioning in the zero page reclamation.
060/05/68846	The operation cannot be performed because the pool associated with the Thin Provisioning volume that is specified as the primary volume is being initialized.
060/05/68847	The operation cannot be performed because the pool associated with the Thin Provisioning volume that is specified as the secondary volume is being initialized.
060/05/68873	The operation failed, because the specified volume was defined in the LU path.
060/05/68879	The operation failed, because the specified volume was a pool volume.
060/05/68880	The operation failed, because the specified volume was used for Auto LUN.
060/05/68895	The operation cannot be performed because the other program product is specified for the Continuous Access Synchronous pair.
060/05/68928	The operation cannot be performed because the specified remote storage system supports only the remote path of the system.
060/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
060/05/75027	The specified port cannot be used because you do not have permission to access a resource group to which the port belongs.
060/05/75028	The operation cannot be performed because the port belonging to a resource group that you do not have permission to access is used by the remote path of the local storage system.
060/05/75030	The operation cannot be performed because the specified port or the port that is used by the remote path of the local storage system belongs to a resource group that you do not have permission to access.
060/05/78001	The operation cannot be performed because the current DKCMAIN firmware version does not support the capacity of the specified primary volume.
060/05/78002	The operation cannot be performed because the current DKCMAIN firmware version does not support the capacity of the specified secondary volume.
060/05/78066	The operation cannot be performed because no CHB is mounted or all CHBs are blocked on the remote storage system.
060/05/78129	The operation cannot be performed because the specified primary volume is an external volume that is mapped for the online data migration and its cache mode is set to Through.
060/05/78130	The operation cannot be performed because the specified secondary volume is an external volume that is mapped for the online data migration.
060/05/78137	The operation cannot be performed because the combination of the models of the local storage system and the remote storage system is not supported.
060/05/78278	The operation cannot be performed due to one of the following reasons:\\n- A pair cannot be created due to the combination of the models of the local storage system and the remote storage system.\\n- The DKCMAIN firmware version of the local storage system or the remote storage system does not support a pair creation by using these models.\\n
060/05/78279	The specified serial number or the controller ID is invalid.
060/05/8000	Time out error. 
060/05/8001	Time out error. 
060/05/8100	The operation cannot be performed, or a communication time-out error occurred.
060/05/8104	The storage system has accepted the request normally, but the pair status change requires some time.
060/05/8700	Please retry operation.
060/05/8701	The remote path between the local storage system and the remote storage system is not active.
060/05/8702	The status of the primary volume is not valid.
060/05/8703	The specified number of remote paths is less than the minimum number of paths.
060/05/8704	The specified number of remote paths is less than the minimum number of paths due to a communication error between the local storage system and the remote storage system.
060/05/8705	The remote paths cannot be deleted due to a communication error between the local storage system and the remote storage system.
060/05/8706	The parameter entered in the remote replication operation is not valid.
060/05/8708	The pair status of the secondary volume is invalid for the specified operation.
060/05/8709	The Continuous Access Synchronous or Continuous Access Journal operation cannot be performed.
060/05/8710	The pair status of the specified volume is not valid.
060/05/8711	The port name, host group ID, LUN ID, CU, or LDEV of the specified volume is invalid.
060/05/8712	The operation was rejected due to a 'FREEZE' state.
060/05/8713	The port group already exists on the specified port.
060/05/8714	An internal error occurred. 
060/05/8715	The number of remote paths is invalid.
060/05/8718	The specified remote path already exists.
060/05/8719	The serial number or model of the remote storage system is not valid.
060/05/8720	The operation cannot be performed because the number of remote storage systems is in one of the following statuses:\\n- Maximum 4 remote storage systems are already registered in one CU.\\n- Maximum 64 remote storage systems are already registered while System is selected.
060/05/8721	The remote path creation was incomplete.
060/05/8722	The remote path could not be created.
060/05/8723	The operation cannot be performed because the specified remote path is the last path of the pair volume of any of the following:\\n- Continuous Access Synchronous\\n- Continuous Access Journal\\n- High Availability
060/05/8724	The specified number of remote paths is less than the minimum number of paths.
060/05/8727	The number of normal remote paths is less than the minimum number of paths.
060/05/8728	The number of normal remote paths is less than the minimum number of paths.
060/05/8729	An internal error occurred. 
060/05/8731	The existing logical addresses are not equal.
060/05/8733	The remote replication function is not installed on the local storage system.
060/05/8734	The remote replication function is not installed on the remote storage system.
060/05/8735	The serial number or model of the remote storage system is not valid.
060/05/8736	The operation cannot be performed because a pair volume of any of the following exists on the specified remote storage system:\\n- Continuous Access Synchronous\\n- Continuous Access Journal\\n- High Availability\\n
060/05/8737	An internal error occurred. 
060/05/8739	The NVS status of the local storage system connected to the host is not active.
060/05/8740	The NVS status of the remote storage system connected to the host is not active.
060/05/8741	The remote paths between the local storage system and the remote storage system are not established.
060/05/8742	Pinned tracks exist in the primary volume.
060/05/8743	Pinned tracks exist in the secondary volume.
060/05/8744	The specified primary volume cannot be used.
060/05/8745	A volume cannot be used as a secondary volume when:\\n- It is used by Continuous Access Synchronous.\\n- It is used by Continuous Access Journal.
060/05/8753	An internal error occurred. 
060/05/8754	The serial number of the local storage system is not valid.
060/05/8756	The cache of the local storage system is not active.
060/05/8757	One side of the cache or the shared memory is blocked in the local storage system.
060/05/8758	An unexpected error occurred in the local storage system.
060/05/8759	The cache of the remote storage system is not active.
060/05/8761	The operation cannot be performed due to one of the following reasons:\\n- The emulation types of the primary and secondary volumes do not match.\\n- The capacities of the primary and secondary volumes do not match.\\n- The secondary volume is a LUSE volume.
060/05/8762	The cache of the secondary volume is not active.
060/05/8764	The specified secondary volume cannot be used.
060/05/8766	Continuous Access Synchronous does not support the emulation type of the secondary volume.
060/05/8768	The remote storage system is still used by a different remote replication program product.
060/05/8770	The cache on the local storage system is automatically recovering.
060/05/8772	The operation cannot be performed because a communication error occurred or the secondary volume status is not valid.
060/05/8773	The operation cannot be performed because the primary volume is in the Split status.
060/05/8775	The multi platform feature is already installed in the remote storage system.
060/05/8776	The volume specified as the primary volume is used by Continuous Access Journal.
060/05/8777	The local storage system does not support connection with the specified remote storage system.
060/05/8778	One side of the cache or the shared memory of the local storage system is blocked.
060/05/8788	The pair operation cannot be performed because the specified secondary volume applies to one of the following:\\n- A LUN path is not defined.\\n- Its emulation type is not supported.
060/05/8789	The combination of the primary and secondary volume configurations is not valid.
060/05/8793	The Continuous Access Synchronous function is not installed in the local storage system or the remote storage system.
060/05/8795	The operation cannot be performed because the specified primary volume applies to either of the following:\\n- A secondary volume of Business Copy, which is not in the PSUS status.\\n- A volume used by Business Copy in the Reverse Copy status.
060/05/8796	The operation cannot be performed because the specified secondary volume applies to either of the following:\\n- A secondary volume of Business Copy.\\n- A volume of Business Copy in the Reverse Copy status.
060/05/8797	If the specified primary volume is a secondary volume of Business Copy, one primary volume must be paired with one secondary volume. 
060/05/8798	The pair cannot be registered because the local storage system is already used by Business Copy.
060/05/8799	The primary volume is already used in Auto LUN.
060/05/8800	The secondary volume is already used in Auto LUN.
060/05/8801	The remote path or the remote storage system is in a high load state.
060/05/8808	The operation cannot be performed because the pair status of the specified volume in the local storage system is changing.
060/05/8809	The operation cannot be performed because the pair status of the specified volume in the remote storage system is changing.
060/05/8819	A volume cannot be used as a secondary volume when:\\n- It is in an intervention-required condition.\\n- It is in a protection condition.\\n- It is in an unusable condition.\\n- It is a secondary volume of Business Copy.
060/05/8820	The Continuous Access Synchronous operation cannot be performed because the specified secondary volume is in any of the following conditions:\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in the correction access condition.
060/05/8821	The specified secondary volume cannot be recognized from the connection port.
060/05/8822	The operation cannot be performed due to one of the following reasons:\\n- An I/O error occurred in the secondary volume.\\n- The secondary volume is in unusable condition.\\n- This function or configuration is not supported by the DKCMAIN firmware version of the local storage system.\\n
060/05/8826	An internal error occurred. 
060/05/8827	The local storage system cannot accept the pair operation.
060/05/8831	The specified secondary volume is already used as a reserved volume of Auto LUN.
060/05/8832	The specified secondary volume is used by an Auto LUN pair whose status is changing.
060/05/8833	The specified secondary volume is used by an Auto LUN pair whose status is changing.
060/05/8834	The pair cannot be created because the used capacity exceeds the licensed capacity. 
060/05/8835	The pair cannot be created because the used capacity exceeds the licensed capacity of the remote storage system.
060/05/8836	No additional volume pairs waiting for copy.
060/05/8837	An internal error occurred. 
060/05/8838	The selected volume is not used by a Continuous Access Synchronous pair.
060/05/8840	The pair split operation for the secondary volume is invalid.
060/05/8841	The specified volume is not a secondary volume.
060/05/8842	The secondary volume status change failed after the primary volume status changed.
060/05/8843	The pair cannot be split because the specified volume is not available.
060/05/8846	An internal error occurred. 
060/05/8847	An internal error occurred. 
060/05/8848	Please wait a few minutes and retry the Suspend Pair(Pairsplit-r) operation.
060/05/8849	The specified volume is not a Continuous Access Synchronous pair volume.
060/05/8860	An internal error occurred. 
060/05/8861	An internal error occurred. 
060/05/8862	Please retry the Delete Pair(Pairsplit-S) operation later.
060/05/8863	Unknown Error Code. 
060/05/8864	An internal error occurred. 
060/05/8865	An internal error occurred. 
060/05/8866	An internal error occurred. 
060/05/8867	An internal error occurred. 
060/05/8877	An internal error occurred. 
060/05/8881	An internal error occurred. 
060/05/8883	An internal error occurred. 
060/05/8884	An internal error occurred. 
060/05/8885	An internal error occurred. 
060/05/8886	An internal error occurred. 
060/05/8903	Unknown Error Code. 
060/05/8904	No more space is left in the local storage system for the differential management.
060/05/8905	The extended shared memory is not installed in the local storage system.
060/05/8906	No more space is left in the remote storage system for the differential management.
060/05/8907	The extended shared memory is not installed in the remote storage system.
060/05/8908	Invalid parameter. 
060/05/8910	A Port exchange error occurred. 
060/05/8912	Logical paths exist on the port. 
060/05/8913	Invalid port type. 
060/05/8914	Multi platform feature is already installed in the storage system.
060/05/8915	The port type exchange operation is rejected because the host(s) is(are) processing the port type exchange. 
060/05/8921	A volume cannot be used as a primary volume when:\\n- It is in an intervention-required condition.\\n- It is in a protection condition.\\n- It is in an unusable condition.\\n- It is a secondary volume of Business Copy.
060/05/8929	Invalid port type. 
060/05/8932	The remote path cannot be established because the configuration definition of the specified CU number does not exist.
060/05/8936	The Create Pairs operation cannot be performed. The DKCMAIN firmware version of the specified remote storage system does not support the remote replication function using NAS volumes.
060/05/8944	The specified secondary volume cannot be used because of the access attribute changed by Data Retention.
060/05/8945	Any of the following is not valid:\\n- Primary volume parameters (CU, port name, host group ID, LUN ID)\\n- CU of the remote storage system\\n- Secondary volume parameters (port name, host group ID, LUN ID)
060/05/8975	The pair cannot be created because the secondary volume is LUN path-defined from the iSCSI port.
060/05/8982	The pair cannot be created because the specified primary volume is a command device.
060/05/8983	The pair cannot be created because the specified secondary volume is a command device.
060/07/6000	An error occurred during Remote Web Console processing.
060/07/6002	An error occurred during Remote Web Console processing.
060/07/6012	An error occurred during Remote Web Console processing.
060/07/6022	Remote Web Console is busy.
060/07/6023	Remote Web Console is busy.
060/07/6024	An error occurred during Remote Web Console processing.
060/07/6036	An error occurred during Remote Web Console processing.
060/07/8001	A time-out error occurred. 
062/05/208001	The specified volume cannot be used as a quorum disk because the capacity of the volume is not enough.
062/05/208002	The specified volume is not an external volume.
062/05/208003	A LUN path is set to the specified volume.
062/05/208004	Two or more LDEVs are set in the parity group to which the specified volume belongs.
062/05/208005	The specified volume is a journal volume.
062/05/208006	The specified volume is a command device.
062/05/208007	A virtual LDEV ID is set on the specified volume.
062/05/208008	The specified volume is not a quorum disk, or the specified quorum disk ID is not registered.
062/05/208009	The specified quorum disk is in internal process.
062/05/208010	The operation cannot be performed because the specified quorum disk is used by a High Availability pair.
062/05/208011	Shared memory required for the specified operation is not installed on the local storage system.
062/05/208012	The operation failed, because there was an error in the specified parameter.
062/05/208013	The specified remote path cannot be used for High Availability.
062/05/208014	The operation cannot be performed due to one of the following reasons:\\n- The cache on the local storage system is automatically recovering.\\n- One side of the cache or the shared memory is blocked on the local storage system.\\n
062/05/208015	The operation cannot be performed because the specified primary volume is an external volume that is mapped for the online data migration.
062/05/208016	The pair status of the primary volume is not valid for the specified operation.
062/05/208017	The operation cannot be performed because the provisioning type of the volume that is selected as the primary volume is not supported.
062/05/208018	The operation cannot be performed because the specified primary volume is a reserved volume of High Availability.
062/05/208019	The specified primary or secondary volume is used by Fast Snap. The operation cannot be performed due to one of the following reasons:\\n- The status of the Fast Snap pair is invalid for being shared with a High Availability pair.\\n- The attribute of the Fast Snap pair is invalid for being shared with a High Availability pair.\\n
062/05/208020	No virtual LDEV ID is set in the specified primary volume.
062/05/208021	The specified secondary volume cannot be used.
062/05/208022	The vendors of the local storage system and the remote storage system do not match.
062/05/208023	The operation cannot be performed because the provisioning type of the volume that is selected as the secondary volume is not supported.
062/05/208024	The specified primary volume and secondary volume are on the same storage system.
062/05/208025	The operation cannot be performed because the specified secondary volume is not a reserved volume of High Availability.
062/05/208026	The operation cannot be performed because different versions of DKCMAIN firmware coexist on the storage system.
062/05/208027	A virtual LDEV ID is set on the specified secondary volume.
062/05/208028	The specified operation cannot be performed because the pair operation that the local storage system has accepted is not complete.
062/05/208029	The operation cannot be performed because the specified volume is changing to the Suspend status due to failure.
062/05/208030	Shared memory required for the specified operation is not installed on the remote storage system.
062/05/208031	The emulation type of the secondary volume is not supported.
062/05/208032	The specified primary or secondary volume is used by Business Copy. The Business Copy pair volume in the current pair status or pair attribute cannot be shared by a High Availability pair.
062/05/208033	The remote storage system does not support High Availability.
062/05/208034	A volume cannot be used as a secondary volume when:\\n- It is in an intervention-required condition.\\n- It is in a protection condition.\\n- It is in an unusable condition.
062/05/208035	The operation cannot be performed due to one of the following reasons:\\n- An I/O error occurred in the secondary volume.\\n- The secondary volume is in unusable condition.\\n
062/05/208036	The pair status of the secondary volume is not valid for the specified operation.
062/05/208037	High Availability is not installed on the remote storage system.
062/05/208038	The capacities of the primary and secondary volumes do not match.
062/05/208039	This function is not available. Resource Partition is required.
062/05/208040	Resource Partition is not installed on the remote storage system.
062/05/208041	The operation cannot be performed because the pool associated with the Thin Provisioning volume that is specified as the primary volume is in either of the following conditions:\\n- It is being initialized.\\n- The capacity is being expanded.\\n
062/05/208042	The operation cannot be performed because the pool associated with the Thin Provisioning volume that is specified as the secondary volume is in either of the following conditions:\\n- It is being initialized.\\n- The capacity is being expanded.\\n
062/05/208043	The I/O mode setting of the specified secondary volume is not valid for the specified operation.
062/05/208044	The I/O mode setting of the specified primary volume is not valid for the specified operation.
062/05/208045	The operation cannot be performed because the specified primary or secondary volume is in either of the following conditions:\\n- The pair status is not PSUS or PSUE.\\n- The I/O mode setting is not Local.\\n
062/05/208046	The specified primary or secondary volume is used by Continuous Access Synchronous. The Continuous Access Synchronous pair volume in the current pair status or pair attribute cannot be shared by a High Availability pair.
062/05/208047	The specified primary or secondary volume is used by Continuous Access Journal. The Continuous Access Journal pair volume in the current pair status or pair attribute cannot be shared by a High Availability pair.
062/05/208048	High Availability is not installed on the local storage system.
062/05/208049	The virtual LDEV ID same as that set on the specified primary volume is defined on a virtual storage machine on the remote storage system.
062/05/208050	The specified primary volume is used by a High Availability pair.
062/05/208051	The specified secondary volume is used by a High Availability pair.
062/05/208052	The attribute (primary or secondary) of the specified volume is not valid for the specified operation.
062/05/208053	The attribute (primary or secondary) of the other paired volume of the specified volume is not valid for the specified operation.
062/05/208054	The pair status of the primary or secondary volume is not valid for the specified operation.
062/05/208055	The primary volume detects one of the following conditions:\\n- A quorum disk is not registered.\\n- The quorum disk ID is not valid.\\n- The registered information of the remote storage system does not match the actual condition.\\n- The quorum disk is not accessible.\\n- The pair is changing to the Suspend status.\\n
062/05/208056	The secondary volume detects one of the following conditions:\\n- A quorum disk is not registered.\\n- The quorum disk ID is not valid.\\n- The registered information of the remote storage system does not match the actual condition.\\n- The quorum disk is not accessible.\\n- The pair is changing to the Suspend status.\\n
062/05/208057	The operation cannot be performed because the serial numbers or models of the virtual storage machines of the specified primary and secondary volumes do not match.
062/05/208058	The setting information of Data Retention on the primary volume cannot be transmitted because Data Retention is not installed on the remote storage system.
062/05/208059	The operation cannot be performed because the specified secondary volumes is used as a High Availability pair volume.
062/05/208060	The operation cannot be performed because the specified primary volume is a command device.
062/05/208061	The operation cannot be performed because the specified secondary volume is a command device.
062/05/208062	The operation cannot be performed because the access attribute of Data Retention has been changed.
062/05/208064	The operation cannot be performed because the selected volume access for the volume in the COPY status is not valid.
062/05/208065	The operation cannot be performed because the pair volume on the remote storage system is used by Business Copy.
062/05/208066	The operation cannot be performed because the pair volume on the remote storage system is used by Fast Snap.
062/05/208067	The operation cannot be performed because the current firmware version does not support consistency groups.
062/05/208068	The operation cannot be performed because the firmware version of the remote storage system does not support consistency groups.
062/05/208069	The operation cannot be performed because a different pair operation is being performed on volumes that belong to the specified consistency group.
062/05/208070	The operation cannot be performed because a different pair operation is being performed on the consistency group that contains the specified volume.
062/05/208071	The operation cannot be performed because a different pair operation is being performed on the specified consistency group.
062/05/208072	The operation cannot be performed because the specified volume or its paired volume is used by Continuous Access Journal.
062/05/208073	The operation cannot be performed because a different pair operation is being performed on the consistency group to which the specified pair belongs.
062/05/208074	The operation cannot be performed because pairs in the specified consistency group are changing to the Suspend status due to failure.
062/05/208075	The operation cannot be performed because the entered consistency group number is not valid.
062/05/208076	The operation cannot be performed because the number of pairs in the specified mirror exceeds the maximum.
062/05/208077	The operation cannot be performed because the combination of the specified consistency group number and quorum disk ID is different from the existing combination.
062/05/208078	The operation cannot be performed because the combination of the specified consistency group number and mirror ID is different from the existing combination.
062/05/208079	The operation with a consistency group specified cannot be performed because the pair configurations in the consistency group have changed.
062/05/208080	The operation with a  volume specified cannot be performed because the pair configurations in the consistency group have changed.
062/05/208081	The operation cannot be performed because an invalid relation is detected between the consistency group number and the volume number.
062/05/208082	The operation cannot be performed because the I/O mode differs between the specified High Availability pair and the High Availability pairs in the consistency group.
062/05/208083	The operation cannot be performed because the following requirements are not met.\\n- The primary volume of a High Availability pair is the primary volume of a Continuous Access Journal pair.\\n- The secondary volume of a High Availability pair is the primary volume of a delta resync pair of Continuous Access Journal.\\n
062/05/208084	The operation cannot be performed because the firmware version of the remote storage system does not support the provisioning type of the volume selected as the secondary volume.
062/05/208085	The operation cannot be performed because the Provisioning type or the attribute differs between the primary volume and the secondary volume.
062/05/208086	The operation cannot be performed due to one of the following reasons:\\n- A temporary failure on the storage system.\\n- The storage system is in internal processing.\\m- The storage system is being maintained.
062/05/208087	The operation cannot be performed because the specified external volume is not formatted.
062/05/208088	The operation cannot be performed because the specified external volume is not accessible.
062/05/208089	The operation cannot be performed because any of the specified parameters is not valid.
062/05/208090	The operation cannot be performed because the specified primary or secondary volume is used by Auto LUN.
062/05/208091	The operation cannot be performed because the number of LUN paths set for the other paired volume exceeds the maximum that is available for ALUA.
062/05/208092	The operation cannot be performed because the specified volume is an external volume with Data Direct Mapping enabled.
062/05/208093	The operation cannot be performed because Data Direct Mapping is enabled on the specified primary volume but the remote storage system does not support Data Direct Mapping.
062/05/208095	The operation cannot be performed because T10 PI is set for the selected volume.
062/05/208097	The operation cannot be performed because the storage system is in the process of setting ALUA.
062/05/208098	Swap suspending with pairs specified cannot be performed because the selected pairs belong to a consistency group.
062/05/208099	One or more of the LDEVs set as the specified quorum disks belong to a resource group that you do not have permission to access.
062/05/208100	The value that is set for Read Response Guaranteed Time When Quorum Disk Blocked is outside the available range.
062/05/208101	The operation cannot be performed because the specified quorum disks do not exist.
062/05/208102	The current DKCMAIN firmware version does not support this operation.
062/05/208527	The operation cannot be performed because the T10 PI setting differs between the primary volume and the secondary volume.
062/05/5013	An error occurred during Remote Web Console processing.
062/05/58509	A communication time-out error occurred between the local storage system and the remote storage system.
062/05/6000	An error occurred during Remote Web Console processing.
062/05/6012	An error occurred during Remote Web Console processing.
062/05/6023	An error occurred during Remote Web Console processing.
062/05/6537	The setting cannot be applied because there is an error in a different setting.
062/05/68827	The operation failed, because there was an error in the specified parameter.
062/05/68829	The specified volume has already been set to the quorum disk. Or, the specified quorum disk ID has already registered.
062/05/68879	The operation cannot be performed because the specified volume is a pool volume.
062/05/68880	The operation failed, because the specified volume was used for Auto LUN.
062/05/68882	The operation cannot be performed because the quorum disk is not accessible.
062/05/68889	The operation failed, because the quorum disk was blocked.
062/05/68891	The operation cannot be performed because the specified quorum disk ID does not match the one set on the remote storage system.
062/05/75015	The selected LDEV or an LDEV in the selected consistency group belongs to a resource group that you do not have permission to access.
062/05/75028	The operation cannot be performed because the port for the remote path on the local storage system belongs to a resource group that you do not have permission to access.
062/05/78001	The operation cannot be performed because the current DKCMAIN firmware version does not support the capacity of the specified primary volume.
062/05/78002	The operation cannot be performed because the current DKCMAIN firmware version does not support the capacity of the specified secondary volume.
062/05/78128	The operation cannot be performed because the specified volume is in the online data migration process.
062/05/78129	The operation cannot be performed because the specified primary volume is an external volume that is mapped for the online data migration and its cache mode is set to Through.
062/05/78130	The operation cannot be performed because the specified secondary volume is an external volume that is mapped for the online data migration.
062/05/8000	Time out error. 
062/05/8001	Time out error. 
062/05/8100	The operation cannot be performed, or a communication time-out error occurred.
062/05/8104	The storage system has accepted the request normally, but the pair status change requires some time.
062/05/8704	The number of specified remote paths is less than the minimum number of paths due to a communication error between the local storage system and the remote storage system.
062/05/8708	The pair status of the secondary volume is not valid for the specified operation.
062/05/8714	An internal error occurred. 
062/05/8727	The number of normal remote paths is less than the minimum number of paths.
062/05/8741	The remote paths between the local storage system and the remote storage system are not established.
062/05/8742	Pinned tracks exist in the primary volume.
062/05/8743	Pinned tracks exist in the secondary volume.
062/05/8744	The specified primary volume cannot be used.
062/05/8746	The emulation type of the primary volume is not supported.
062/05/8758	An unexpected error occurred on the local storage system.
062/05/8788	The pair operation cannot be performed because the specified secondary volume applies to one of the following:\\n- A LUN path is not defined.\\n- Its emulation type is not supported.
062/05/8821	The specified secondary volume cannot be recognized from the connection port.
062/05/8827	The local storage system cannot accept the pair operation.
062/05/8834	The pair cannot be created because the used capacity exceeds the licensed capacity. 
062/05/8835	The pair cannot be created because the used capacity exceeds the licensed capacity of the remote storage system.
062/05/8904	No more space is left in the difference management area of the local storage system.
062/05/8906	No more space is left in the difference management area of the remote storage system.
065/05/208004	The pair operation of Continuous Access Journal cannot be performed because the firmware exchange is in progress or interrupted.
065/05/208005	The operation of Continuous Access Journal cannot be performed because the shared memory is not installed on the storage system.
065/05/208007	The specified pair or journal does not exist.
065/05/208009	The operation cannot be performed because the specified volume is being maintained.
065/05/208020	The Create Pairs operation cannot be performed because the specified primary volume is used by High Availability.
065/05/208021	The Create Pairs operation cannot be performed because the reservation attribute of High Availability is set on the specified primary volume.
065/05/208022	The Create Pairs operation cannot be performed because the specified secondary volume is used by High Availability.
065/05/208023	The Create Pairs operation cannot be performed because the reservation attribute of High Availability is set on the specified secondary volume.
065/05/208100	The remote command device cannot be assigned because Continuous Access Journal pairs in the selected mirror ID share the same volumes with High Availability pairs.
065/05/208101	A Continuous Access Journal pair for delta resync cannot be created. The selected primary volume of the Continuous Access Journal pair for delta resync must meet either of the following requirements:\\n- The volume is the secondary volume of a High Availability pair and the High Availability pair is in the PAIR status.\\n- The volume is the primary volume of a High Availability pair and the I/O mode is Block.
065/05/208102	A Continuous Access Journal pair cannot be created due to either of the following reasons:\\n- A High Availability pair that uses the selected primary volume does not belong to a consistency group.\\n- A High Availability pair that shares the same volume with a different Continuous Access Journal pair using the selected journal belongs to a different consistency group of High Availability.
065/05/208103	A delta resync pair cannot be created. The selected mirror ID is used by a High Availability pair that uses the selected primary volume.
065/05/208104	A delta resync pair cannot be created due to either of the following reasons:\\n- The selected journal ID does not match the one associated with a consistency group of High Availability.\\n- A High Availability pair that shares the same volume with a different delta resync pair using the selected journal belongs to a different consistency group of High Availability.
065/05/208105	A Continuous Access Journal pair cannot be created. The selected primary volume of the Continuous Access Journal pair must meet the following requirement:\\n- The volume is the primary volume of a High Availability pair and the High Availability pair is in the PAIR status.
065/05/208106	A delta resync pair cannot be created due to either of the following reasons:\\n- A High Availability pair that uses the selected primary volume does not belong to a consistency group.\\n- A High Availability pair that shares the same volume with a different delta resync pair using the selected journal belongs to a different consistency group of High Availability.
065/05/208107	A Continuous Access Journal pair cannot be created. The selected mirror ID is used by a High Availability pair that uses the selected primary volume.
065/05/208108	A Continuous Access Journal pair cannot be created due to either of the following reasons:\\n- The selected journal ID does not match the one associated with a consistency group of High Availability.\\n- A High Availability pair that shares the same volume with a different Continuous Access Journal pair using the selected journal belongs to a different consistency group of High Availability.
065/05/208109	A Continuous Access Journal pair cannot be created. The secondary volume of the High Availability pair that uses the selected primary volume of the Continuous Access Journal pair and the primary volume of the Continuous Access Journal pair for delta resync that uses the selected secondary volume of the Continuous Access Journal pair do not match.
065/05/208110	The resync operation cannot be performed because the pair in which the selected volume is used applies to either of the following:\\n- The status of the High Availability pair is not PAIR, COPY, PSUS, PSUE, or SSWS.\\n- The status of the delta resync pair is not HLDE.
065/05/208111	The delta resync operation cannot be performed because the status of the High Availability pair that uses the selected primary volume is not SSWS.
065/05/208112	A Continuous Access Journal pair or a delta resync pair cannot be created because the selected remote storage system does not support the connection configuration of High Availability and Continuous Access Journal.
065/05/208113	The operation cannot be performed because the storage system is in internal process.
065/05/208119	A Continuous Access Journal pair cannot be created because the secondary volume of a High Availability pair that uses the selected primary volume is not shared with a delta resync pair.
065/05/208120	A Continuous Access Journal pair for delta resync cannot be created because either of the following requirements is not met.\\n- The primary volume of the Continuous Access Journal pair for data resync uses the primary volume of the High Availability pair.\\n- The secondary volume of the Continuous Access Journal pair for delta resync is used by a Continuous Access Journal pair that is created by a different mirror.
065/05/208150	A Continuous Access Journal pair for delta resync cannot be created. The secondary volume of the High Availability pair that uses the selected primary volume of the Continuous Access Journal pair for delta resync and the primary volume of the Continuous Access Journal pair that uses the selected secondary volume of the Continuous Access Journal pair for delta resync do not match.
065/05/208152	Continuous Access Journal pairs in cascading configuration cannot be created. To create the specified Continuous Access Journal pairs, one of the following requirements must be met.\\n- The journal to which the secondary volume belongs is not used as the primary volume of Continuous Access Journal pairs in a different mirror.\\n- The primary volume is not a Thin Provisioning volume.\\n- The secondary volume is not a Thin Provisioning volume.
065/05/208154	A Continuous Access Journal pair cannot be created because the specified primary volume is an external volume with Data Direct Mapping enabled.
065/05/208155	A Continuous Access Journal pair cannot be created because the microcode version on the secondary storage system does not support Data Direct Mapping.
065/05/208156	A Continuous Access Journal pair cannot be created because the specified secondary volume is an external volume with Data Direct Mapping enabled.
065/05/208157	A Continuous Access Journal pair cannot be created because the microcode version on the primary storage system does not support Data Direct Mapping.
065/05/208158	A Continuous Access Journal pair cannot be created because the primary storage system does not support the pair creation function.
065/05/208159	A Continuous Access Journal pair cannot be created because the specified primary volume is an external volume with Data Direct Mapping enabled.
065/05/208160	The operation cannot be performed because the T10 PI setting differs between the specified primary volume and secondary volume.
065/05/208161	A pair cannot be created.
065/05/208391	The operation cannot be performed, because THP V-VOLs whose capacity saving status is not Disabled or deduplication system data volumes are selected.
065/05/208530	The Create Pairs operation cannot be performed because no virtual LDEV ID is set on the volume specified as the secondary volume.
065/05/208531	The specified local storage system does not support Online Migration.
065/05/208532	The specified remote storage system does not support Online Migration.
065/05/208533	The Create Pairs operation cannot be performed because no virtual LDEV ID is set on the volume specified as the primary volume.
065/05/208534	The specified volume cannot be registered as a journal volume because it is an LDEV on which the virtualization management is enabled.
065/05/208535	The specified volume cannot be registered as a journal volume because it is an LDEV on which the virtualization management is enabled.
065/05/208536	The Create Pairs operation cannot be performed because the volume specified as the primary volume or the secondary volume applies to any of the following:\\n- The volume already registered in the selected mirror is an LDEV on which the virtualization management is disabled, but the specified volume is one on which it is enabled.\\n- The volume already registered in the selected mirror is an LDEV on which the virtualization management is enabled, but the specified volume is one on which it is disabled.\\n- The serial number or model of the virtual storage machine of the specified LDEV, on which the virtualization management is enabled, is not valid.
065/05/208537	The Create Pairs operation cannot be performed because the volume specified as the primary volume or the secondary volume applies to any of the following:\\n- The volume already registered in the selected journal group is an LDEV on which the virtualization management is disabled, but the specified volume is one on which it is enabled.\\n- The volume already registered in the selected journal group is an LDEV on which the virtualization management is enabled, but the specified volume is one on which it is disabled.\\n- The serial number or model of the virtual storage machine of the specified LDEV, on which the virtualization management is enabled, is not valid.
065/05/208538	The Create Pairs operation cannot be performed because the cache mode of the external volume that is mapped for online data migration and is specified as the primary volume is set to Through.
065/05/208539	The Create Pairs operation cannot be performed because the volume specified as the primary volume is used as an external volume that is mapped for the online data migration, and is also used as the pair volume of Auto LUN.
065/05/3003	An error occurred during Remote Web Console processing.
065/05/5013	An error occurred during Remote Web Console processing.
065/05/5040	Too many objects are specified.
065/05/5511	The program product is not installed.
065/05/56524	This function cannot be used by the storage partition administrator.
065/05/56535	The Assign Remote Command Devices operation cannot be performed due to a temporary path failure.
065/05/58005	Too many requests.
065/05/58006	Invalid parameter (LDEV ID).
065/05/58007	The parameter (Journal ID) is not valid or the specified journal is not registered.
065/05/58008	The command was rejected by the storage system because the command is unknown.
065/05/58009	No more remote storage systems can be registered.
065/05/58010	Invalid parameter (path group ID).
065/05/58011	The specified operation failed due to the mirror status of the journal.
065/05/58012	Invalid parameter (number of initial copy activities).
065/05/58013	The specified volume does not exist or is unusable.
065/05/58014	Pinned slot(s) exists.
065/05/58015	The specified volume is blocked.
065/05/58016	The cache or the shared memory is in an abnormal state.
065/05/58019	The specified volume is already used by another program product.
065/05/58023	The specified CLPR ID is invalid.
065/05/58024	The specified cache value for master journal is invalid.  
065/05/58025	The specified cache value for restore journal groups is invalid.  
065/05/58026	The specified threshold for ending creation of asynchronous journal is invalid.
065/05/58027	The specified threshold for ending creation synchronous journal is invalid.
065/05/58028	The specified threshold for starting creation of asynchronous journal is invalid.
065/05/58029	The specified threshold for starting creation synchronous journal is invalid.
065/05/58030	The threshold for starting creation of synchronous journal must be larger than the threshold for starting creation of asynchronous journal.
065/05/58031	The threshold for starting creation of asynchronous journal must be larger than the threshold for ending creation of asynchronous journal.
065/05/58032	The threshold for starting creation of synchronous journal must be larger than the threshold for ending creation of synchronous journal.
065/05/58033	The total cache capacity is incorrect.
065/05/58034	The operation is impossible because the storage system is being powered on.
065/05/58035	No more journal volumes can be registered, or too many volumes are selected.
065/05/58037	The specified journal cannot be deleted because a data volume exists.
065/05/58038	No more path group IDs can be registered.
065/05/58039	The specified volume is already used as a journal volume or a data volume.
065/05/58064	Too many requests.
065/05/58065	Invalid parameter (LDEV ID).
065/05/58066	The parameter (Journal ID) is not valid or the specified journal is not registered.
065/05/58067	Invalid parameter (Mirror ID).
065/05/58068	Invalid parameter (Journal Control).
065/05/58069	Invalid parameter (Suspend Condition - Journal Full).
065/05/58070	Invalid parameter (Suspend Condition - Master Journal Failure).
065/05/58071	Invalid parameter (Suspend Condition - Restore Journal Failure).
065/05/58072	The pair status has not changed yet. 
065/05/58073	The storage system is busy.
065/05/58075	The specified serial number is incorrect.
065/05/58078	The specified volume does not exist or is unusable.
065/05/58082	The specified consistency group is already used.
065/05/58083	The specified master journal is not registered.
065/05/58084	The pair cannot be registered because the volume specified as the primary volume is already used as a journal volume.
065/05/58085	The specified primary volume is not registered in the specified journal.
065/05/58086	The specified master journal is not registered.
065/05/58087	The emulation type of the volume specified as the primary volume is invalid due to one of the following reasons:\\n- The emulation type is not supported.\\n- The combination of emulation types within the journal is invalid.\\n- The combination of emulation types between journals is invalid.\\n
065/05/58088	The specified mirror ID differs from the registered mirror ID.
065/05/58089	A pair cannot be created because the selected mirror ID of the master journal is already used by a mirror of a different restore journal.
065/05/58090	The SLPR number of the specified data volume does not match the SLPR number of the journal volume in the specified journal.
065/05/58091	The specified primary volume is already registered.
065/05/58092	No more pairs can be registered in the specified master journal.
065/05/58093	The volume specified as the primary volume is already registered in a different journal.
065/05/58094	The specified primary volume cannot be deleted because the volume is already registered in a different journal.
065/05/58097	Continuous Access Journal is not installed on the local storage system.
065/05/58098	The cache or the shared memory is in an abnormal state.
065/05/58099	The cache or the shared memory is in an abnormal state.
065/05/58100	The serial number or the model of the remote storage system is invalid.
065/05/58101	The pair status is incorrect.
065/05/58102	An internal error occurred. 
065/05/58105	Paths or pairs cannot be created because Continuous Access Journal is not installed on the remote storage system.
065/05/58106	The operation cannot be performed because the specified volumes are in either of the following conditions:\\n- The capacities of the primary and secondary volumes do not match.\\n- The current firmware version does not support the specified capacity of the secondary volume.
065/05/58264	Journal volumes cannot be registered because the program product license of Continuous Access Journal is not installed.
065/05/58269	The specified restore journal is not registered.
065/05/58270	The pair cannot be created due to one of the following reasons:\\n- The specified restore journal is already paired with a different journal.\\n- The combination of the restore journal and the mirror ID specified when creating Delta resync volume pairs is already used by the ordinary (not Delta resync) volume pairs.\\n
065/05/58271	The volume specified as the secondary volume cannot be used due to one of the following reasons:\\n- S-VOL Disable is set by Data Retention.\\n- The VMA setting differs between the primary volume and the secondary volume.
065/05/58275	The specified restore journal is not registered.
065/05/58276	The pair cannot be registered because the volume specified as the secondary volume is already used as a journal volume.
065/05/58277	The specified secondary volume is not registered in the specified journal.
065/05/58278	The specified restore journal is not registered.
065/05/58279	The emulation type of the volume specified as the secondary volume or of the restore journal volume is invalid due to one of the following reasons:\\n- The emulation type is not supported.\\n- The combination of the emulation types within the journal is invalid.\\n- The combination of the emulation types between the master and restore journal volumes is invalid.\\n- The emulation types of the primary and secondary volumes do not match.\\n
065/05/58280	The specified secondary volume is already registered.
065/05/58281	No more pairs can be registered in the specified restore journal.
065/05/58282	The specified secondary data volume is already registered\\nin another journal group.
065/05/58283	The specified secondary volume cannot be deleted because the volume is already registered in a different journal.
065/05/58284	An internal error occurred. 
065/05/58285	No more pairs can be registered because the number of pairs will exceed the maximum.
065/05/58286	The command cannot be executed because the command that should be issued to the secondary volume is issued to the primary volume.
065/05/58287	The command cannot be executed because the command that should be issued to the primary volume is issued to the secondary volume.
065/05/58288	The specified primary volume is already paired with a different volume.
065/05/58289	The specified secondary volume is already paired with a different volume.
065/05/58290	The specified primary volume is not paired with any volumes.
065/05/58291	The specified secondary volume is not paired with any volumes.
065/05/58292	The specified volume cannot be used as a journal volume.
065/05/58293	The specified operation cannot be performed on the data volume pair.
065/05/58294	The specified operation cannot be performed because the status of the data volume pair is changing.
065/05/58295	An internal error occurred. 
065/05/58302	The specified volume is used as a command device.
065/05/58305	A path is defined to the specified volume.
065/05/58306	The volume specified as the secondary volume is used as a command device.
065/05/58307	The volume specified as the secondary volume is an On-Demand (Just in Time)volume.
065/05/58308	The volume specified as the primary volume is used as a command device.
065/05/58325	The volume specified as the primary volume is used by Continuous Access Synchronous. The operation cannot be performed because the status of the Continuous Access Synchronous pair is not valid.
065/05/58328	The operation of Create Pairs or Resync Pairs cannot be performed because data remains in the journal cache for the restore journal.
065/05/58333	The parameter related to the inflow cannot be changed because the specified journal is other than the master journal.
065/05/58334	The parameter related to the inflow cannot be changed, because the status of the specified journal is neither "Initial" nor "Stopped".
065/05/58335	The timer type cannot be changed, because the status of the specified journal is not "Initial". 
065/05/58336	The specified volume cannot be registered as a journal volume because the CLPR number of the specified volume is different from the CLPR number of the journal volume that has already been registered.
065/05/58337	The operation cannot be performed because the CLPR number of the volume specified as the primary volume is different from the CLPR number of the journal volume in the specified master journal.
065/05/58338	The operation cannot be performed because the CLPR number of the volume specified as the secondary volume is different from the CLPR number of the journal volume in the specified restore journal.
065/05/58341	The specified volume cannot be used as a journal volume because the specified volume is an external volume.
065/05/58345	The Create Pairs operation cannot be performed due to one of the following reasons:\\n- The IO suppression mode of the specified secondary volume is enabled.\\n- The firmware version of the secondary storage system does not support external volumes.
065/05/58346	The Create Pairs operation cannot be performed because VMA of Data Retention is set on the volume specified as the secondary volume.
065/05/58353	The operation cannot be performed because the volume specified as the secondary volume applies to any of the following:\\n- A secondary volume of Business Copy.\\n- A primary volume of Business Copy in the Swap or Reverse Copy status.\\n- A primary volume of Business Copy used in conjunction with Continuous Access Synchronous.\\n- A Thin Provisioning volume used as a primary volume of Business Copy.\\n- A Thin Provisioning volume and a source volume of Auto LUN.\\n- A Thin Provisioning volume used as a primary volume of Fast Snap.
065/05/58354	The specified volume cannot be used as a primary volume because it is being used by any of the following program products:\\n- Business Copy\\n- Continuous Access Synchronous\\n- Auto LUN\\n
065/05/58355	The pair operation cannot be performed because the volume specified as the secondary volume is being used by one of the following program products:\\n- Business Copy\\n- Fast Snap\\n- Continuous Access Synchronous\\n- Auto LUN
065/05/58451	The storage system is in internal process.
065/05/58457	The specified primary volume is used by Continuous Access Synchronous.
065/05/58458	A different mirror ID has already been registered in the specified master journal. Specify the same mirror ID, because only one mirror ID can be registered in one journal.
065/05/58485	The Create Pairs operation cannot be performed because the volume specified as the primary volume applies to either of the following:\\n- A primary volume of Fast Snap in Reverse Copy status.\\n- A secondary volume of Fast Snap.\\n
065/05/58486	The Create Pairs operation cannot be performed because the volume specified as the primary volume is a virtual volume of Fast Snap.
065/05/58487	The Create Pairs operation cannot be performed because the volume specified as the primary volume is a pool volume.
065/05/58490	The pair option of the primary volume was updated, but that of the secondary volume cannot be updated. The firmware of the remote storage system might not support the change pair option function, or a communication error between the local and remote storage systems might have occurred.
065/05/58500	The Create Pairs operation cannot be performed because the Continuous Access Journal function of the remote storage system does not support external volumes.
065/05/58501	The Create Pairs operation failed because the Continuous Access Journal  function of the Remote Storage System does not support VMA of Data Retention.
065/05/58502	The operation cannot be performed because the volume capacity of the remote storage system exceeds the licensed capacity of Open Array Management.
065/05/58503	The specified operation failed due to the attribute or the mirror status in the journal.
065/05/58504	The operation cannot be performed.
065/05/58508	The Create Pairs operation cannot be performed because the IO suppression mode of the volume specified as the primary volume is enabled.
065/05/58510	The Create Pairs operation cannot be performed. The combination of the specified primary volume and the mirror ID is the same as the combination specified from a different local storage system. 
065/05/58530	The capacity of the specified volume is too small.
065/05/58550	The operation to add journal volumes failed due to the mirror status of the specified journal.
065/05/58560	A journal volume cannot be added because the capacity of shared memory is insufficient.
065/05/58561	The Create Pairs operation or the Resync Pairs operation cannot be performed because the timer type of the master journal is different from that of the restore journal.
065/05/58562	The specified volumes or the volumes in the specified journal were deleted, but the volumes could not be blocked.
065/05/58563	The specified volume could not be registered because the volume failed to recover from blockade.
065/05/58564	The Create Pairs operation cannot be performed because the volume specified as the primary volume is being shredded.
065/05/58565	The Create Pairs operation cannot be performed because the volume specified as the secondary volume is being shredded.
065/05/58566	The specified volume cannot be registered as a journal volume because the volume is being shredded by Data Retention.
065/05/58590	The Create Pairs or the Resync Pairs operation cannot be performed because the journal volumes of the specified master journal are blocked.
065/05/58591	The Create Pairs or the Resync Pairs operation cannot be performed because the journal volumes of the specified restore journal are blocked.
065/05/58592	The specified operation failed because the storage system was being powered on or powered off.
065/05/58593	The storage system has accepted the request normally, however the processing requires some time.
065/05/58594	The Create Pairs operation cannot be performed because the specified secondary volume is in LUSE configuration.
065/05/58596	The operation to change the status to the status ready for delta resync cannot be performed because At-Time Split is set to the specified restore journal.
065/05/58601	Journals cannot be added to the extended consistency group (EXCTG), because the additional shared memory is not installed.
065/05/58602	Journals cannot be added to the extended consistency group (EXCTG), because the number of storage systems in the EXCTG exceeds the maximum.
065/05/58603	Journals cannot be added to the extended consistency group (EXCTG), because the number of journals in the EXCTG exceeds the maximum.
065/05/58605	Journals cannot be added to the extended consistency group (EXCTG) because the specified mirror ID is different from the mirror ID existed in the EXCTG.
065/05/58606	Journals cannot be deleted from the extended consistency group (EXCTG), because the specified EXCTG is not registered.
065/05/58607	Journal groups cannot be deleted from the extended consistency group (EXCTG), because the specified journal group was not registered.
065/05/58608	The Resync Pairs operation cannot be performed. The restore journal belongs to an extended consistency group (EXCTG), but the local storage system does not support the EXCTG function.
065/05/58609	The timer type cannot be changed, because the specified journal belongs to an extended consistency group (EXCTG).
065/05/58611	The specified operation cannot be performed because the firmware exchange is in progress or interrupted on the storage system in the extended consistency group (EXCTG).
065/05/58612	The previously performed update processing of the extended consistency group (EXCTG) is not complete.
065/05/58613	The command device is specified incorrectly.
065/05/58683	The operation cannot be performed because Continuous Access Journal of the remote storage system does not support the delta resync function.
065/05/58684	The operation to change the status to Ready for Delta resync cannot be performed. The specified primary volume should meet the following conditions:\\n- It is a secondary volume of Continuous Access Synchronous.\\n- The Continuous Access Synchronous pair is in PAIR status.
065/05/58685	The delta resync operation cannot be performed. The specified primary volume should meet the following conditions:\\n- If it is shared as the primary volume of Continuous Access Synchronous, the status of the Continuous Access Synchronous pair is PAIR.\\n- If it is shared as the secondary volume of Continuous Access Synchronous, the status of the Continuous Access Synchronous pair is SSWS.
065/05/58686	The specified operation failed, because the attribute of the journal of the remote storage system was not "restore".
065/05/58687	The status of the other mirror of the Delta resync did not change.
065/05/58688	The delta resync operation cannot be performed because the specified primary volume is not ready for delta resync.
065/05/58689	The operation cannot be performed because the status of some mirrors in the master or restore journal is invalid.
065/05/58690	The recovery to the status ready for delta resync cannot be made because the specified primary volume is in one of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in correction access status.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.\\n
065/05/58691	The pair operation cannot be performed due to one of the following reasons:\\n- The Create Pairs or Resync Pairs operation (for delta resync pairs) is performed while specifying the mirror ID used by pairs other than delta resync pairs.\\n- The Create Pairs or Resync Pairs operation (not for delta resync pairs) is performed while specifying the mirror ID used by delta resync pairs.\\n
065/05/58692	The specified master journal cannot be used for Delta resync, because it is registered in the extended consistency group (EXCTG).
065/05/58693	The specified restore journal cannot be used for Delta resync, because it is registered in the extended consistency group (EXCTG).
065/05/58694	The delta resync operation cannot be performed.
065/05/58696	The specified volume cannot be used as a journal volume because the volume is an external volume to which the I/O suppression mode is enabled.
065/05/58697	The journal volume cannot be deleted from the specified journal due to the mirror status.
065/05/58698	The operation cannot be performed because the specified secondary volume is used by delta resync.
065/05/58699	The operation to change the status to Ready for Delta resync cannot be performed because the specified secondary volume is used by either of the following program products:\\n- Business Copy\\n- Fast Snap
065/05/58700	The operation to change the status to Ready for Delta resync cannot be performed. The specified secondary volume should meet the following conditions:\\n- It is a secondary volume of a different mirror.\\n- It is in PAIR or Duplex status.\\n
065/05/58701	The Continuous Access Journal pair for delta resync cannot be resynchronized due to one of the following reasons.\\n- Updated data for the Continuous Access Synchronous pair and that for the Continuous Access Journal pair do not match.\\n- An I/O is issued from the host to the secondary volume of the Continuous Access Journal.
065/05/58702	The delta resync operation cannot be performed because the number of Continuous Access Journal pairs and that of Continuous Access Journal delta resync pairs are different in the restore journal.\\nAs a result, the Continuous Access Journal delta resync pair that did not share the same volume with a Continuous Access Journal pair was automatically deleted.
065/05/58703	The delta resync operation cannot be performed because the secondary volume has been updated.
065/05/58704	The operation to change the status to Ready for Delta resync cannot be performed because the primary volume is not shared by Continuous Access Synchronous and Continuous Access Journal.
065/05/58705	The delta resync operation cannot be performed. The specified secondary volume should meet the following conditions:\\n- It is a secondary volume of a different mirror.\\n- It is in PSUS, PSUE, Suspend, PAIR, or Duplex status.\\n
065/05/58707	The Create Pairs operation or the Resync Pairs operation cannot be performed because the status of the specified secondary volume is Not Ready.
065/05/58708	The Create Pairs operation with Delta specified, or the Resync Pairs operation on the pair in Ready for Delta resync status cannot be performed.
065/05/58716	The licensed capacity of Continuous Access Synchronous on the remote storage system is not enough. 
065/05/58718	The licensed capacity of Continuous Access Journal on the remote storage system is not enough.
065/05/58719	The licensed capacity of Continuous Access Synchronous on the local storage system is not enough.
065/05/58721	The licensed capacity of Continuous Access Journal on the local storage system is not enough.
065/05/6000	An error occurred during Remote Web Console processing.
065/05/6001	An error occurred during Remote Web Console processing.
065/05/6012	An error occurred during Remote Web Console processing.
065/05/6022	A file open error has occurred.
065/05/6023	An error occurred during Remote Web Console processing.
065/05/6502	Processing in progress.
065/05/6537	There is no error in this setting.\\nHowever, there is an error in another setting and the setting processing has not been executed.
065/05/68003	The operation failed, because the specified journal was not registered.
065/05/68004	The operation failed, because the number of journals exceeded the maximum.
065/05/68005	The operation failed, because more than one LDKC numbers cannot coexist in one journal.
065/05/68006	The Create Pairs operation cannot be performed because the LDKC number of the volume specified as the primary volume is different from the LDKC number of the master journal.
065/05/68007	The Create Pairs operation failed. The LDKC number of the volume specified as the secondary volume is different from the LDKC number of the specified restore journal.
065/05/68008	The Create Pairs operation cannot be performed because the capacity of the shared memory of the local storage system is not enough.
065/05/68009	The Create Pairs operation cannot be performed because the capacity of the shared memory of the remote storage system is not enough.
065/05/68013	The operation cannot be performed due to any of the following reasons.\\n- The specified volume is not a Thin Provisioning volume.\\n- Data Direct Mapping is enabled on the specified volume.
065/05/68014	The operation failed because the specified volume was a pool volume of Thin Provisioning.
065/05/68017	The operation cannot be performed because the volume specified as the secondary volume is a Thin Provisioning volume.
065/05/68018	The operation cannot be performed because the volume specified as the secondary volume is a pool volume of Thin Provisioning.
065/05/68019	The remote storage system does not support the LDEV ID of the specified primary volume.
065/05/68024	The operation failed because the current firmware version does not support Delta Resync.
065/05/68025	The volume specified as the primary volume is used as a pair volume of Continuous Access Synchronous. The operation cannot be performed because the program product license of Cont Access Journal 3DC & 4x4 Open MF is not installed on the local storage system.
065/05/68026	The volume specified as the secondary volume is used as a pair volume of Continuous Access Synchronous. The operation cannot be performed because the program product license of Cont Access Journal 3DC & 4x4 Open MF is not installed on the remote storage system.
065/05/68028	Journals cannot be added to the extended consistency group (EXCTG), because the current firmware version does not support LDKC numbers other than 0.
065/05/68759	The status of the specified volume is Simplex or SMPL.
065/05/68779	The Create Pairs operation cannot be performed because the volume specified as the secondary volume is a system disk.
065/05/68781	The specified operation cannot be performed because LU is specified for the error level.
065/05/68782	The Create Pair operation cannot be performed because (0) is specified for the mirror ID.
065/05/68783	The Create Pairs operation cannot be performed because the specified primary volume is used by Continuous Access Synchronous.
065/05/68784	The Resync Pairs operation cannot be performed because the status of the specified primary volume is either of the following.\\n- The volume is not used by Continuous Access Synchronous.\\n- The volume is used by Continuous Access Synchronous, but the pair status is not PSUS or PSUE.\\n
065/05/68805	The operation cannot be performed because the specified secondary volume is used as a volume of Data Migration.
065/05/68812	A pair cannot be created because the specified secondary volume is a Thin Provisioning volume whose capacity is being changed.
065/05/68813	A pair cannot be created because the volume specified as the primary volume is a Thin Provisioning volume whose capacity is being changed.
065/05/68815	The pair cannot be released because the specified volume is used as the pair volume of Continuous Access Synchronous.
065/05/68842	The operation cannot be performed because the volume specified as the secondary volume is a volume of Thin Provisioning in zero page reclaiming.
065/05/68848	The operation cannot be performed because a pool associated with a volume for Thin Provisioning specified as the primary volume is being initialized.
065/05/68849	The operation cannot be performed because the pool associated with the volume of Thin Provisioning that is specified as the secondary volume is being initialized.
065/05/68850	The operation cannot be performed because the consistency group of the specified data volume is shared with multiple local and remote storage systems, and LU is specified for Range.
065/05/68851	The operation cannot be performed because the specified consistency group is shared with multiple local and remote storage systems.
065/05/68853	The operation cannot be performed because the specified journal is shared with multiple local and remote storage systems.
065/05/68857	The operation failed, because a remote command device has already been assigned to the specified mirror.
065/05/68858	The operation failed, because the specified mirror was invalid.
065/05/68859	The operation failed, because the specified remote command device was blocked.
065/05/68860	The operation cannot be performed because the serial numbers of the remote command device and the mirror do not match.
065/05/68861	The operation failed, because the specified journal was not in the configuration of 3DC cascade or 3DC multi target.
065/05/68862	The specified remote command device cannot be assigned to a mirror any further.
065/05/68863	The operation failed, because the number of assignable remote command device to a mirror exceeded the maximum.
065/05/68870	The operation failed, because a remote command device was not assigned to the specified mirror.
065/05/68886	The operation cannot be performed because the remote storage system does not support the setting operation of remote command devices.
065/05/68904	The operation to create a pair of the second mirror cannot be performed because the specified restore journal applies to either of the following.\\n- A master journal of the first mirror.\\n- A restore journal of the first mirror.
065/05/68905	The operation cannot be performed because the specified journal is either a master journal or a restore journal.\\nThe following options cannot be changed with master and restore journals.\\n- Data overflow watch.\\n- Use of cache.\\n
065/05/68906	A journal volume cannot be added to the specified journal in the operation environment of the current storage system.
065/05/68907	The operation failed because the number of mirrors registered in the specified journal exceeded the upper limit.
065/05/68909	The operation failed because the restore journal specified for the second mirror was used as the restore journal of the first mirror.
065/05/68910	The operation cannot be performed because the specified restore journal does not support Continuous Access Journal 3DC.
065/05/68911	The operation failed because the specified master journal does not support Continuous Access Journal 3DC.
065/05/68912	The operation cannot be performed because the program product license of Cont Access Journal 3DC & 4x4 Open MF is not installed on the local storage system.
065/05/68913	The operation cannot be performed because the program product license of Cont Access Journal 3DC & 4x4 Open MF is not installed on the remote storage system.
065/05/68914	The operation failed because the specified primary volume was used by another mirror of the journal and the pair status of the mirror was in transition (COPY/ Suspending/ Deleting/ HOLDING).
065/05/68915	The Create Pairs operation cannot be performed because the status of a different mirror in the journal to which the volume specified as the secondary volume belongs is not Initial or Stopped.
065/05/68916	The pair operation cannot be performed because the specified primary volume applies to one of the following:\\n- Its consistency group is shared by multiple local and remote storage systems.\\n- Being used by Continuous Access Synchronous.\\n- Being used by Fast Snap.\\n- Being used by Auto LUN.
065/05/68917	The pair operation cannot be performed because the specified secondary volume applies to one of the following:\\n- Its consistency group is shared by multiple local and remote storage systems.\\n- Being used by Continuous Access Synchronous.\\n- Being used by Fast Snap.\\n- Being used by Auto LUN.
065/05/68919	The pair operation cannot be performed because the mirror status between the primary and intermediate sites in the 3DC cascading configuration with Continuous Access Journal is Active.
065/05/68925	The operation to create a pair for delta resync cannot be performed because the pair status of the specified primary volume is not PAIR.
065/05/68926	The delta resync operation cannot be performed because the pair status of the specified primary volume is not appropriate.
065/05/7060	An error occurred during Remote Web Console processing.
065/05/7111	An error occurred during Remote Web Console processing.
065/05/7310	This error code is not registered.
065/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
065/05/75021	The specified operation cannot be done because there is an LDEV that has been set to a different resource group.
065/05/75027	The specified port cannot be used because the user has no access right to a resource group to which the port belongs.
065/05/75028	The operation cannot be performed because the port belonging to a resource group that you do not have permission to access is used by the remote path of the local storage system.
065/05/78003	The specified journal cannot be used.
065/05/78004	The specified consistency group cannot be used.
065/05/78050	The operation failed because the specified capacity of the primary volume is not supported by the current firmware version.
065/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
065/05/78139	The specified LDEV cannot be set as a journal volume because the volume is used as an external volume that is mapped for online data migration.
065/05/78140	The Create Pairs operation cannot be performed because the volume specified as the primary volume is used as an external volume that is mapped for online data migration.
065/05/78141	The Create Pairs operation cannot be performed because the volume specified as the secondary volume is used as an external volume that is mapped for online data migration.
065/05/78160	The journal registration failed because the 2DC cascade was specified as enabled.
065/05/78265	A request to create a pair using a journal in the configuration consisting of three Continuous Access Journal sites was received. However, the operation failed because a pair creation for the Delta resync is specified.
065/05/78270	A Create Pairs failed because the serial number, the model, or the path group ID of the specified Remote Storage System is invalid.
065/05/78272	The Create Pairs operation cannot be performed due to either of the following reasons:\\n- The firmware version of the specified remote storage system does not support the connection with the local storage system.\\n- The specified secondary volume is already used by Continuous Access Synchronous.
065/05/78273	The Create Pairs operation cannot be performed because the local storage system is in either of the following conditions:\\n- Its firmware version does not support the connection with the remote storage system.\\n- It is a storage system that cannot be connected with the remote storage system.
065/05/78274	The Create Pairs operation cannot be performed because the local storage system is in either of the following conditions:\\n- Its firmware version does not support the connection with the remote storage system.\\n- It is a storage system that cannot be connected with the remote storage system.
065/05/78276	The Resync Pairs operation cannot be performed because the specified secondary volume is already used as a secondary volume of a pair in a different mirror and the pair status is not applicable to the operation.
065/05/78277	The specified volume cannot be used as a journal volume because the capacity of the volume is not enough.
065/05/78281	The Create Pairs operation cannot be performed because the remote storage system does not support the specified path group ID.
065/05/78285	A pair operation cannot be performed because a different mirror of the specified restore journal is in status transition (Halting/ Stopping).
065/05/78294	The Create Pairs operation cannot be performed because there is not enough space left in the difference management area of the local storage system.
065/05/78295	The Create Pairs operation cannot be performed because the extended shared memory is not installed on the local storage system.
065/05/78296	The Create Pairs operation failed because there is not enough space left in the difference management area of the Remote Storage System.
065/05/78297	The Create Pairs operation failed because the extended shared memory is not installed in the Remote Storage System.
065/05/78299	Failed to change the journal option because the parameter of Inflow Control is invalid.
065/05/78300	Failed to change the journal option because the parameter of Data Overflow Watch is invalid.
065/05/78301	Failed to change the mirror option because the parameter of Copy Pace is invalid.
065/05/78302	Failed to change the mirror option because the parameter of Path Watch Time is invalid.
065/05/78303	Failed to change the mirror option because the parameter of Transfer Speed is invalid.
065/05/78304	Failed to change the journal option because the parameter of Timer Type is invalid.
065/05/8000	An error occurred during Remote Web Console processing.
065/05/8001	A communication time-out error occurred in the local storage system.
065/05/8002	A communication time-out error occurred in the local storage system.
065/05/8100	An error occurred during Remote Web Console processing.
065/05/8102	This function is not supported.
065/05/8700	Please retry operation. 
065/05/8701	The pair operation cannot be performed due to one of the following reasons:\\n- The remote path between the local storage system and the remote storage system is not valid.\\n- The status of the specified secondary volume is SMPL.
065/05/8702	The status of the primary volume is invalid.
065/05/8703	The specified number of remote paths is less than the minimum number of paths.
065/05/8704	The specified number of remote paths was less than the minimum number of paths due to a communication error between the local storage system and the remote storage system.
065/05/8706	Parameter specified by Remote Copy operation invalid. 
065/05/8708	The pair status of the secondary volume is invalid.
065/05/8710	The pair status of the specified data volume is incorrect.
065/05/8711	The specified parameter is incorrect.
065/05/8712	The operation was rejected due to a 'FREEZE' state.
065/05/8713	The port group already exists on the specified port.
065/05/8714	An internal error occurred. 
065/05/8715	The number of remote paths is invalid.
065/05/8720	The number of registered remote storage systems already reached the maximum (64).
065/05/8721	The remote path creation is not complete yet.
065/05/8722	The remote path could not be created.
065/05/8723	The operation could not be performed because the specified remote path is the last path of the remote replication pairs.
065/05/8724	The specified number of remote paths is less than the minimum number of paths.
065/05/8727	The Minimum Number of Paths exceeds the number of normal Remote Paths.
065/05/8728	The number of normal remote paths is less than the minimum number of paths.
065/05/8729	An internal error occurred. 
065/05/8731	The existing logical addresses are not the same. 
065/05/8736	The specified remote storage system contains journals or pairs for remote replication.
065/05/8737	An internal error occurred. 
065/05/8742	Pinned tracks exist in the primary volume.
065/05/8743	Pinned tracks exist in the secondary volume.
065/05/8744	The specified primary volume cannot be used.
065/05/8746	The emulation type of the primary volume is not supported.
065/05/8753	An internal error occurred. 
065/05/8757	One side of the cache or the shared memory is blocked in the local storage system.
065/05/8758	An unexpected error occurred in the local storage system.
065/05/8764	The operation could not be performed due to one of the following reasons:\\n- The secondary volume is blocked.\\n- The restore journal is not registered.\\n- The journal volumes of the restore journal are blocked.
065/05/8770	The cache in the local storage system is automatically recovering.
065/05/8778	One side of the cache or the shared memory is blocked in the remote storage system.
065/05/8788	The specified volume is not defined in the remote storage system.
065/05/8795	The operation cannot be performed because the volume specified as the primary volume is used by Business Copy and applies to either of the following:\\n- A secondary volume, which is not in the PSUS status.\\n- A volume in the Reverse Copy status.
065/05/8819	A volume cannot be used as a secondary volume when:\\n- It is in an intervention-requested condition.\\n- It is in a protection condition.\\n- It is in an unusable condition.\\n- It is a Business Copy secondary volume.\\n- It is in use by Auto LUN.\\n- It is a Business Copy primary volume in the Swap or Reverse Copy status.\\n- It belongs to "NAS_Platform_System_RSG" with resource group ID 1023.
065/05/8822	An I/O error occurred in the secondary volume.
065/05/8832	The Create Pairs operation cannot be performed because data volume migration by Auto LUN is in progress on the specified primary volume.
065/05/8833	The Create Pairs operation cannot be performed because data volume migration by Auto LUN is in progress on the specified secondary volume.
065/05/8834	The operation failed because you tried to create volume pairs which exceeded the licensed capacity.
065/05/8835	The operation failed because you tried to create volume pairs which exceeded the licensed capacity of the Remote Storage System.
065/05/8887	An internal error occurred. 
065/05/8888	An internal error occurred. 
065/05/8889	The specified port isn't equipped.
065/05/8890	The specified port is being initialized. 
065/05/8891	LUN paths are defined on the specified port.
065/05/8893	An internal error occurred. 
065/05/8894	Jobs exist on the specified port.
065/05/8895	Jobs exist on the port of the remote storage system.
065/05/8896	A parameter error occurred.
065/05/8897	LUs exist on the port. 
065/05/8898	Pending data exists on the port. 
065/05/8899	An internal error occurred. 
065/05/8900	An error occurred during the port change. 
065/05/8901	An error occurred during the port change. 
065/05/8902	An error occurred during the port change. 
065/05/8903	Unknown Error Code. 
065/05/8915	Remote Web Console attempted to change the port type. However, this attempt could not be made because the same operation was in progress from a host.
065/05/8924	LUN paths are defined to the port on the remote storage system.
065/05/8929	Invalid port type. 
065/05/8930	LUN paths are defined to the port on the remote storage system.
065/05/8931	LUN paths are defined to the port on the remote storage system.
065/05/8934	The Create Pairs operation cannot be performed because the volume specified as the secondary volume is a NAS system volume.
065/05/8936	The Create Pairs operation cannot be performed. The firmware version of the specified remote storage system does not support the remote replication function using NAS volumes.
065/05/8944	The specified secondary volume cannot be used because of the access attribute changed by Data Retention.
065/05/8947	The external volume that is mapped to an internal volume is connected to the port.
065/05/8948	The specified port is receiving I/O requests.
065/05/8949	An internal error occurred. 
065/05/8950	An internal error occurred. 
065/07/5036	Two or more commands which were not able to be processed were demanded.
065/07/6012	An error occurred during Remote Web Console processing.
065/07/6036	An error occurred during Remote Web Console processing.
065/07/7070	An error occurred during Remote Web Console processing.
065/07/7071	An error occurred during Remote Web Console processing.
070/05/205028	The operation cannot be performed because the total number of Fast Snap pairs that share the selected primary volume exceeds 32,768.
070/05/208041	A pair cannot be created because of the migration attribute of the volume specified as the primary volume or the secondary volume.
070/05/208042	The operation cannot be performed because of the migration attribute of the volume specified as the primary volume or the secondary volume.
070/05/208043	A pair consisting of three secondary volumes cannot be created because of the migration attribute of the volume specified as the primary volume.
070/05/208044	The operation cannot be performed because of the migration attribute of the secondary volume of the specified pair.
070/05/208045	The volume specified as the primary volume is a migration volume of Online Migration. The operation cannot be performed because the setting of the online data migration for the volume is not valid.
070/05/208047	The command cannot be run because the volume specified as the primary volume is a reserved volume of High Availability, or the status of the High Availability pair is not valid.
070/05/208048	The command cannot be run because the volume specified as the secondary volume is a reserved volume of High Availability, or the volume is used by the High Availability pair.
070/05/208049	The command cannot be run because the volume specified as the primary volume is a reserved volume of High Availability, or the status of the High Availability pair is not valid.
070/05/208050	The command cannot be run because the volume specified as the secondary volume is a reserved volume of High Availability, or the volume is used by the High Availability pair.
070/05/208051	The command cannot be run because the specified primary volume is not a primary volume of a Fast Snap pair.
070/05/208052	The command cannot be run because the specified pair does not exist.
070/05/208053	The command cannot be run because the specified pair cannot be identified.
070/05/208054	The command cannot be run because the specified pair has a secondary volume.
070/05/208055	The command cannot be run because the specified pair has no secondary volume.
070/05/208056	The command cannot be run because the specified pair has no secondary volume.
070/05/208057	The operation cannot be performed because the DKCMAIN firmware version and the Remote Web Console software version do not match.
070/05/208058	The command cannot be run because the specified pair has a secondary volume.
070/05/208059	The processing cannot continue due to an internal logic contradiction.
070/05/208060	The processing cannot continue due to an internal logic contradiction.
070/05/208067	The operation cannot be performed because the specified primary volume is being migrated by Auto LUN.
070/05/208069	The operation cannot be performed because the specified secondary volume is being migrated by Auto LUN.
070/05/208072	The operation cannot be performed because the specified primary volume is an external volume with the data direct mapping enabled or a volume that belongs to a parity group with the capacity expansion enabled.
070/05/208073	The operation cannot be performed because the specified secondary volume is an external volume with the data direct mapping enabled or a volume that belongs to a parity group with the capacity expansion enabled.
070/05/208075	The pair operation cannot be performed because the T10 PI setting does not match between the specified primary volume and secondary volume.
070/05/208076	A pair cannot be created, because the number of cascade pair layers exceeds 64.
070/05/208077	A pair with the clone attribute cannot be created, because three such pairs exist in the layers from the specified primary volumes to the root volume in the highest layer.
070/05/208078	A pair cannot be created, because the snapshot groups contain both pairs with the snapshot attribute and pairs with the clone attribute.
070/05/208079	One or more pairs cannot be created, because a Fast Snap pair that uses the specified primary volume as the secondary volume is not in the PAIR or PSUS status.
070/05/208080	A pair cannot be created, because a pair belonging to the specified CTG exists in one of the layers from the specified primary volume to the root volume.
070/05/208081	Pairs with the clone attribute are specified.\\nThe following operations cannot be performed on pairs with the clone attribute:\\n- Deleting secondary volumes\\n- Changing secondary volumes\\n- Resynchronization\\n- Restoration
070/05/208082	The following operations cannot be performed, because one or more Fast Snap pairs are using the secondary volume of the specified pair as a primary volume:\\n- Deleting the secondary volume\\n- Changing the secondary volume
070/05/208083	One or more pairs cannot be split, because a Fast Snap pair that uses the primary volume of the specified pairs as the secondary volume is not in the PSUS status.
070/05/208084	The specified pairs with the clone attribute cannot be split, because the configuration of those pairs does not match the actual configuration.
070/05/208085	The pair cannot be deleted, because one or more Fast Snap pairs are using the secondary volume of the specified pair as a primary volume.
070/05/208086	The selected pairs cannot be resynchronized or restored, because one or more pairs whose status is not PAIR exist in layers lower than the layers of the selected pairs.
070/05/208087	The command cannot be run, because the shared memory needed to perform operations on Fast Snap cascade pairs or pairs with the clone attribute is not installed.
070/05/208088	The current DKCMAIN firmware version does not support the specified operation.
070/05/208089	Pairs cannot be created, because the secondary volumes are not Thin Provisioning volumes.
070/05/208090	An internal error occurred.
070/05/208091	Pairs with the clone attribute cannot be created, because no secondary volumes are specified.
070/05/208095	The command cannot be run, because zero pages are being reclaimed on the specified secondary volumes.
070/05/208096	The command cannot be run, because the capacities of the specified secondary volumes are being expanded.
070/05/208097	The command cannot be run, because the statuses of the specified secondary volumes are being changed.
070/05/208098	A pair cannot be created, because the cascade attribute setting differs from the settings of the pairs under the root volume. A pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled cannot exist under the root volume.
070/05/208099	Thin Provisioning volumes with the SLU attribute cannot be assigned as secondary volumes.
070/05/208100	The command cannot be run, because the specified primary volumes are being deleted.
070/05/208101	The command cannot be run, because the specified secondary volumes are being deleted.
070/05/208102	The operation cannot be performed, because the specified S-VOL is a V-VOL for Snapshot.
070/05/208387	Pairs cannot be created, because deduplication system data volumes are specified as the primary volumes.
070/05/208388	Pairs cannot be created, because deduplication system data volumes are specified as the secondary volumes.
070/05/208397	The Quick Restore operation cannot be performed, because the capacity saving status of the primary volumes of the selected pairs is not Disabled.
070/05/208398	The Quick Restore operation cannot be performed, because the capacity saving status of the secondary volumes of the selected pairs is not Disabled.
070/05/208463	The specified operation cannot be performed, because the pool capacity exceeds the subscription limit of the pool.
070/05/208546	The operation cannot be performed because the selected secondary volume is used as a primary volume of a Continuous Access Synchronous pair or a Continuous Access Journal pair.
070/05/238724	The operation cannot be performed because the specified LDEV with the SLU attribute is bound to an LDEV with the ALU attribute.
070/05/5013	An error occurred during Remote Web Console processing.
070/05/5099	An error occurred during Remote Web Console processing.
070/05/55264	The command was rejected because you tried to create a pair using a volume with VMA setting by Data Retention and a volume without VMA setting.
070/05/55645	Quick Restore cannot be performed because the specified pair is composed of the external volumes with different cache mode settings.
070/05/5625	An internal logic error occurred.
070/05/5626	The specified volume cannot be used because it is write-protected by Data Retention.
070/05/56301	The storage system is in internal process, or some other user is changing the configuration.
070/05/56302	An error occurred during Remote Web Console processing.
070/05/56303	An error occurred during Remote Web Console processing.
070/05/5655	The capacities of the volumes specified as the primary volume and the secondary volume do not match.
070/05/57101	An error occurred during Remote Web Console processing.
070/05/57102	An error occurred during Remote Web Console processing.
070/05/58000	The command has been rejected because the cascade request for creating cascade pairs composed of volumes belonging to the same consistency group was issued.
070/05/58001	The pair operation cannot be performed due to either of the following reasons:\\n- The requirements for the operation on the L2 pair are not met because the L1 pair is in the COPY(SP)/COPY, PSUS(SP)/COPY, or COPY(RS-R)/RCPY status.\\n- The pair operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/58002	The Quick Restore command has been rejected because the specified pair is composed of a normal volume and a customized volume (CV).
070/05/58003	The command has been rejected because a Remote Copy pair exists in the same storage system frame.
070/05/5821	This operation has been rejected.\\nThe Data Retention setting does not allow the specified volume(s) to be specified as S-VOL(s).
070/05/58259	The Quick Restore command could not be executed because the specified pair contains external volumes and also is used as a remote replication pair.
070/05/58260	The command was rejected because the specified P-VOL is used as a P-VOL of a Continuous Access Synchronous pair.
070/05/58261	The command has been rejected, because the specified P-VOL is used as S-VOL of Continuous Access Synchronous pair.
070/05/58262	A pair cannot be created because shared memory for differential tables is in sufficient.
070/05/58299	The operation failed because the specified P-VOL was a data volume of Continuous Access Journal. \\nCheck the requirements for using the volume with Continuous Access Journal.
070/05/58300	The operation failed, because the specified S-VOL was a data volume of Continuous Access Journal.
070/05/58351	The Quick Restore command could not be executed because the specified pair contains external volumes, and also is used as a Continuous Access Journal pair.
070/05/58356	The command was rejected because the specified volume is used by the Continuous Access Journal and the Continuous Access Synchronous.
070/05/58451	The storage system is busy (internal processing).
070/05/58476	The operation cannot be performed because the specified P-VOL is a P-VOL for Fast Snap.
070/05/58477	The operation cannot be performed because the specified P-VOL is a V-VOL for Fast Snap.
070/05/58478	The operation cannot be performed, because the specified P-VOL is a pool volume.
070/05/58479	The operation cannot be performed because the specified S-VOL is a P-VOL for Fast Snap.
070/05/58480	The operation cannot be performed because the specified S-VOL is a V-VOL for Fast Snap.
070/05/58481	The operation cannot be performed, because the specified S-VOL is a pool volume.
070/05/58492	The Pairsplit-S (Delete Pairs) operation has failed.
070/05/58493	The PCB required for this operation is not mounted. 
070/05/58520	The operation failed, because different versions of softwares coexisted in the storage system.
070/05/58533	The operation failed, because the specified P-VOL was a journal volume.
070/05/58534	The operation failed, because the specified S-VOL was a journal volume.
070/05/58536	The operation could not be performed because the specified secondary volume is a Continuous Access Journal volume.
070/05/58572	An error occurred on the DKC side.
070/05/58573	This function is not supported.
070/05/58574	An error occurred while connecting to the storage system.
070/05/58575	An error occurred while connecting to the storage system.
070/05/58576	A communication time-out error occurred in the storage system.
070/05/58579	The operation could not be performed because the specified volume is being shredded by Data Retention.
070/05/58582	The command has been rejected because the specified S-VOL is used as P-VOL of Fast Snap, or the specified MU number is already used.
070/05/58583	The operation failed because the volume was shared by a Fast Snap pair.
070/05/58584	The operation failed because the volume was shared by a Fast Snap pair in COPY (RS-R)/RCPY status.
070/05/58585	The operation failed because the CU group of the specified volume is not supported.
070/05/58630	The operation cannot be performed because the specified primary volume is used by a delta resync pair of Continuous Access Journal.
070/05/58631	The operation failed because the specified S-VOL was used by Delta resync of Continuous Access Journal.
070/05/58711	The operation could not be performed because the specified MU number is already used. 
070/05/58906	The operation failed because the volume specified as the P-VOL was used as the S-VOL of another pair and the volume specified as the S-VOL was used as the P-VOL of another pair already.
070/05/6012	An error occurred during Remote Web Console processing.
070/05/6023	The Remote Web Console is busy. 
070/05/6502	Processing in progress. 
070/05/6503	The target volume status is being changed to SMPL.  
070/05/6537	The setting could not be applied because there is an error in a different setting.
070/05/68021	"0" cannot be specified as the MU number of L2 pair.
070/05/68737	The command has been rejected, because the specified P-VOL is a Thin Provisioning volume not associated with a pool.
070/05/68738	The command has been rejected, because the specified S-VOL is a Thin Provisioning volume not associated with a pool.
070/05/68743	The command has been rejected, because Quick Format is performed on the specified P-VOL.
070/05/68744	The command has been rejected, because Quick Format is performed on the specified S-VOL.
070/05/68750	The Quick Restore command has been rejected, because the specified pair is composed of the Thin Provisioning volume and the volumes other than Thin Provisioning volume.
070/05/68755	The Quick Restore command has been rejected, because device information (Inquiry information) of P-VOL and S-VOL was different in the specified pair.
070/05/68760	Quick Restore cannot be performed because the configuration is being backed up in the target volume. 
070/05/68808	The command has been rejected, because the specified P-VOL is a Thin Provisioning volume whose capacity is being added.
070/05/68809	The command has been rejected, because the specified S-VOL is a Thin Provisioning volume whose capacity is being added.
070/05/68814	The initialization function cannot be performed because a Continuous Access Synchronous pair or a Continuous Access Journal pair is created by using Thin Provisioning volumes.
070/05/68835	The command has been rejected because the specified P-VOL is used by a pair of Fast Snap that is registered in the CTG.
070/05/68836	The command has been rejected because the specified S-VOL is used by a pair of Fast Snap that is registered in the CTG.
070/05/68837	The command has been rejected, because the specified P-VOL is a volume of Thin Provisioning whose zero page is being reclaimed.
070/05/68838	The command has been rejected, because the specified S-VOL is a volume of Thin Provisioning whose zero page is being reclaimed.
070/05/68922	The specified primary volume is a volume using two mirrors in the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The operation for the specified volume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Continuous Access Journal delta resync pair volume.\\n- The specified volume is used as a Continuous Access Journal pair data volume.
070/05/68923	The specified secondary volume is a volume using two mirrors in the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The operation for the specified volume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Continuous Access Journal delta resync pair volume.\\n- The specified volume is used as a Continuous Access Journal pair data volume.
070/05/7310	This error code is not registered.
070/05/75002	The command was rejected, because the Thin Provisioning volume specified as P-VOL was not associated with a pool.
070/05/75003	The command was rejected, because the Thin Provisioning volume specified as S-VOL was not associated with a pool.
070/05/75005	The specified operation cannot be performed due to one of the following reasons:\\n- Performing a pair split or pair resync operation on a pair in the SMPL status.\\n- Specifying a volume with no LUN paths set as a primary volume to create a pair with the cascade attribute disabled.\\n- Performing a pair split or pair resync operation on a pair for which the cascade attribute is disabled and whose primary volume has no LUN paths.
070/05/75006	The specified operation cannot be performed due to one of the following reasons:\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing a secondary volume for a pair in the SMPL status.\\n- Specifying a volume with no LUN paths set for a secondary volume to create a pair with the cascade attribute disabled.\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing a secondary volume for a pair for which the cascade attribute is disabled and whose secondary volume has no LUN paths.
070/05/75008	The specified operation cannot be performed, because pairs under root volumes are being deleted.
070/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
070/05/75046	The LDEVs of a specified pool contain an LDEV that belongs to a resource group that you do not have permission to access.
070/05/78053	The operation failed because the current software version does not support the capacity of specified P-VOL.
070/05/78054	The operation failed because the current software version does not support the capacity of specified S-VOL.
070/05/78108	The command was rejected, because the pool associated with the Thin Provisioning volume that is specified as the P-VOL was being initialized.
070/05/78109	The command was rejected, because the pool associated with the Thin Provisioning volume that is specified as the S-VOL was being initialized.
070/05/78128	The operation cannot be performed because the specified volume is in the online data migration process.
070/05/78129	The operation cannot be performed because the volume specified as the primary volume is in the online data migration process.
070/05/78130	The operation cannot be performed because the volume specified as the secondary volume is a migration volume of Online Migration.
070/05/78139	The operation cannot be done because a pool cannot be used.
070/05/78140	The operation cannot be performed because the specified pool number is not the same as the pool number for the existing pairs.
070/05/78141	The operation cannot be performed because the specified primary volume is a secondary volume for Fast Snap.
070/05/78142	The operation cannot be performed because the specified secondary volume is a secondary volume for Fast Snap.
070/05/78143	The specified snapshot number is used in a different pair for Fast Snap.
070/05/78144	The operation cannot be done because the license capacity has been exceeded.
070/05/78145	The command cannot be run in the current pair status.
070/05/78146	The pair operation cannot be performed due to either of the following reasons:\\n- The operation previously specified cannot be performed in the current pair status.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/78147	The operation cannot be performed, because a pool whose pool type is not Fast Snap is selected.
070/05/78148	The command was rejected because the specified volume was set unavailable to specify as a secondary volume.
070/05/78149	An error occurred during Fast Snap operations due to one of the following reasons:\\n- The LDEV number specified for the primary volume or secondary volume is wrong.\\n- The LDEV specified as the primary volume or secondary volume is not paired.\\n- The pair of the specified primary volume or secondary volume is not in the status where the operation can be executed.\\n- The specified Snapshot ID (MU number) is wrong.\\n- The specified Snapshot ID (MU number) is already used.\\n- The specified pool is not in a usable status.\\n- The license capacity has exceeded the maximum.\\n- The control table for Fast Snap is depleted.
070/05/78151	The command was rejected because the shared memory (FC, TPF, or Extension1) of necessary capacity was not installed.
070/05/78152	The command was rejected because the shared memory (SS1 or more) of necessary capacity was not installed.
070/05/78153	The LDEV number that is specified as a primary volume is invalid.
070/05/78155	The operation cannot be performed because the Fast Snap primary volume is used as a Continuous Access Synchronous primary volume, and the status of the Continuous Access Synchronous pair is not PSUS or PSUE.
070/05/78156	The operation cannot be performed because the Fast Snap primary volume is used as a Continuous Access Journal primary volume, and the status of the Continuous Access Journal pair is not PSUS or PSUE.
070/05/78157	The operation cannot be performed because the Fast Snap primary volume is also a Continuous Access Synchronous secondary volume.
070/05/78158	The operation cannot be performed because the Fast Snap primary volume is also a Continuous Access Journal secondary volume.
070/05/78159	The operation cannot be done because VMA is set for the specified primary volume.
070/05/78161	The operation cannot be done because the specified secondary volume is an external volume.
070/05/78162	The operation cannot be done because the specified secondary volume is not a virtual volume.
070/05/78163	The command was rejected because the specified secondary volume was used as a primary volume of Continuous Access Journal.
070/05/78164	The command was rejected because the specified secondary volume was used as a secondary volume of Continuous Access Journal.
070/05/78165	The command was rejected because the specified volume was set unavailable to specify as a secondary volume.
070/05/78166	The operation cannot be done because VMA is set for the specified secondary volume.
070/05/78167	The command was rejected because the Max LBA size of the specified primary and the secondary volumes was different.
070/05/78168	The command was rejected because the number of slots is different between the specified primary and the secondary volumes. 
070/05/78169	The specified operation cannot be performed due to one of the following reasons:\\n- Assigning or changing a secondary volume for a pair in the SMPL status.\\n- Specifying a Thin Provisioning virtual volume as a secondary volume to create a pair with the cascade attribute disabled.\\n- Specifying a Thin Provisioning virtual volume as a secondary volume of a pair with the cascade attribute disabled to assign or change the secondary volume.
070/05/78171	The command was rejected because the specified secondary volume was used as a primary volume of Business Copy.
070/05/78172	The command was rejected because the specified secondary volume was used as a secondary volume of Business Copy.
070/05/78174	The Fast Snap pair cannot be created due to one of the following reasons:\\n- The required shared memory capacity is not installed.\\n- The shared memory is in the initializing process.
070/05/78175	The specified operation cannot be done.
070/05/78176	The operation cannot be done because the PSUE option is specified.
070/05/78177	The operation cannot be performed because the Fast Snap primary volume and the Continuous Access Synchronous secondary volume share the same volume, and the Continuous Access Synchronous pair status is COPY.
070/05/78178	The operation cannot be performed because the Fast Snap primary volume and the Continuous Access Journal secondary volume share the same volume, and the Continuous Access Journal pair status is COPY.
070/05/78179	The Business Copy MU number cannot be specified when the Fast Snap primary volume and the Business Copy primary volume share the same volume.
070/05/78180	"0" cannot be specified as the MU number of the Fast Snap primary volume when the Fast Snap primary volume and the Business Copy secondary volume share the same volume.
070/05/78181	The command was rejected because the Fast Snap primary volume and the Business Copy primary volume share the same volume, and the Business Copy pair is in the re-synchronizing process.
070/05/78182	The command was rejected because the Fast Snap primary volume and the Business Copy secondary volume share the same volume, and the Business Copy pair status is not PSUS.
070/05/78183	The operation cannot be performed because the Fast Snap primary volume and the Business Copy primary volume share the same volume, and the Business Copy pair status is not PSUS or PSUE.
070/05/78184	The operation cannot be performed because the Fast Snap primary volume and the Business Copy secondary volume share the same volume, and the Business Copy pair status is not PSUS.
070/05/78185	The operation cannot be done because the pools or the pool volumes are blocked.
070/05/78186	The Fast Snap pair cannot be restored due to one of the following reasons:\\n- The snapshot data of the restore target Fast Snap pair is being obtained per consistency group.\\n- The snapshot data is being obtained for a different pair whose primary volume is the restore target Fast Snap primary volume.
070/05/78187	The Fast Snap pair with the specified consistency group number cannot be created due to one of the following reasons:\\n- The specified consistency group number is used by Business Copy.\\n- The number of pairs in the consistency group exceeds the maximum.\\n- A pair with the same primary volume already exists in the specified consistency group.
070/05/78188	The specified consistency group number is invalid.
070/05/78190	The operation cannot be done because the specified secondary volume is incorrect.
070/05/78191	The command was rejected because the program product of Fast Snap is not installed.
070/05/78195	The command was rejected because the primary volume is used as an external volume that is mapped for online data migration.
070/05/78196	The command was rejected because the secondary volume is used as an external volume that is mapped for online data migration.
070/05/78201	The operation cannot be performed due to one of the following reasons:\\n- With the current DKCMAIN firmware version, a THP pool cannot be used to store snapshot data.\\n- For the specified pool, Enable is selected for Smart Pool.\\n- For the specified pool, Enable is selected for Data Direct Mapping.
070/05/78202	The operation failed because the Fast Snap program product is not installed. 
070/05/78203	The operation failed because the software version of Remote Web Console and firmware version of DKCMAIN do not match. 
070/05/78204	The operation failed because there are not enough cache management devices.
070/05/78205	The operation failed because the capacity of the specified volume exceeds 4 TB.
070/05/78207	The operation cannot be performed due to either of the following reasons:\\n- There is a pair in the status of Quick Restore among Business Copy pairs that share a primary volume.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/78208	The operation failed because the specified pool number is wrong.
070/05/78210	A Fast Snap pair cannot be created because the consistency group used by the specified snapshot group is one of the following:\\n- The consistency group number is used by Business Copy. \\n- The number of pairs that can be defined in a consistency group exceeds the maximum.\\n- A pair created by using the same primary volume already exists in the consistency group .  
070/05/78255	The operation failed because the volume specified as the S-VOL is a root volume.
070/05/78256	The operation failed because the volume specified as the S-VOL is a node volume.
070/05/78257	The operation failed because the volume specified as the P-VOL is a leaf volume.
070/05/78258	The operation failed because the volume specified as the S-VOL is a leaf volume.
070/05/78259	The specified primary volume is a volume using two mirrors in the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The operation for the specified volume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Continuous Access Journal delta resync pair volume.\\n- The specified volume is used as a Continuous Access Journal pair data volume.
070/05/78260	The specified secondary volume is a volume using two mirrors in the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The operation for the specified volume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Continuous Access Journal delta resync pair volume.\\n- The specified volume is used as a Continuous Access Journal pair data volume.
070/05/78261	The command ended abnormally because the specified MU number is out of the range that can be specified.
070/05/78289	A Fast Snap pair with the CTG mode specified cannot be created because all the consistency groups have already been defined.
070/05/78290	A Fast Snap pair cannot be created because the snapshot ID (MU number) that can be used for the volume specified as the primary volume is depleted.
070/05/78291	A Fast Snap pair cannot be created because all the snapshot groups have already been defined, or the number of pairs that can be registered in the specified snapshot group has exceeded the maximum.
070/05/78292	A Fast Snap pair in which a V-VOL of Thin Provisioning is set as the primary volume cannot be created because the Thin Provisioning pool is being initialized.
070/05/78293	Failed to create a Fast Snap pair because the Thin Provisioning pool is being initialized.
070/05/78294	The Add Pair (Paircreate) operation failed because the specified pair type is invalid.
070/05/78310	The Fast Snap pair operation cannot be performed because all Fast Snap pairs that share the specified primary volume are in PSUE status.
070/05/8000	A time-out error occurred. 
070/05/8001	Time out error. 
070/05/8100	A time-out error occurred. 
070/05/8500	Sufficient amount of shared memory is not installed or the program product is not installed.
070/05/8501	The command has been rejected, because the command specified last time is being processed.
070/05/8503	You cannot create the new pair, because a remote copy pair exists in the same storage system frame.
070/05/8504	The operation cannot be performed due to either of the following reasons:\\n- The current pair configuration or status, or the volume status does not meet the requirements for the operation.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/8505	The operation cannot be performed due to either of the following reasons:\\n- The current pair status does not meet the requirements for the operation.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/8506	The command cannot be run because the specified secondary volume is used by the host.
070/05/8507	The Pairsplit (Split Pairs) command was issued to the pairs in a PSUS status.
070/05/8508	The Paircreate (Create Pairs) command was issued to the pairs in the PSUS status.
070/05/8509	The Pairsplit (Split Pairs) command with the QUIESCE specification was issued to a secondary boot device.
070/05/8510	The P-VOL Suspend command was issued to a secondary boot device.  
070/05/8512	Cannot perform Pairresync (Resync Pairs) or Pairsplit-E (Suspend Pairs) operation because of the path group setting.
070/05/8519	The capacities of the volumes specified as the primary volume and the secondary volume do not match.
070/05/8521	The number of multiple copy jobs exceeded the maximum.
070/05/8525	An internal logic error occurred.
070/05/8526	An internal logic error occurred.
070/05/8527	An internal logic error occurred.
070/05/8528	An internal logic error occurred.
070/05/8529	An internal logic error occurred.
070/05/8530	An internal logic error occurred.
070/05/8531	An internal logic error occurred.
070/05/8532	The command has been rejected, because the P-VOL or the S-VOL is being used by the host.
070/05/8535	A processor failure was detected.  
070/05/8536	A cache failure was detected.  
070/05/8537	The cache capacities do not match.  
070/05/8538	An SM failure was detected.  
070/05/8539	There is not enough shared memory on the local storage system to create 4096 pairs.
070/05/8540	There is sufficient shared memory to create 4096 pairs, but initial storage system setup is required before creating pairs.
070/05/8541	There is sufficient shared memory to create 4096 pairs, and the initial storage system setup is complete.
070/05/8542	Failed to complete the initial shared memory setup.
070/05/8543	The shared memory size is different.  
070/05/8544	16 Mbytes of shared memory is available.
070/05/8545	A power supply failure is detected.  
070/05/8546	The command was rejected.  The PS OFF is in progress.  
070/05/8547	A data transfer failure is detected (CHB).
070/05/8548	A data transfer failure is detected (DKB).
070/05/8549	The P-VOL is not implemented.  
070/05/8550	The command cannot be run because the specified primary volume is blocked.
070/05/8551	The primary volume is being formatted or shredded.
070/05/8552	This volume cannot be specified as an P-VOL because it is used as a command device.
070/05/8553	The S-VOL is not implemented.  
070/05/8554	The command cannot be run because the specified secondary volume is blocked.
070/05/8555	The secondary volume is being formatted or shredded.
070/05/8556	This volume cannot be specified as an S-VOL because it is used as a command device.
070/05/8557	The volume is not implemented.  
070/05/8559	The volume is being formatted.  
070/05/8560	This volume cannot be specified because it is used as a command device.
070/05/8561	The command code is invalid.  
070/05/8562	The command code sender is invalid.  
070/05/8563	The volume type is invalid.  
070/05/8564	The volume type is invalid.  
070/05/8565	The command code sender is invalid.  
070/05/8567	The number of effective lists is invalid.  
070/05/8569	The command cannot be run because the area of the differential table or the pair table to set pairs is not enough.
070/05/8570	The selected volume does not exist.  
070/05/8572	The volume is already defined as a P-VOL.  
070/05/8573	The volume is defined as a source volume for Auto LUN.  
070/05/8574	The volume is defined as a target volume for Auto LUN.  
070/05/8580	The specified volume is for backup servers only.   
070/05/8581	The specified volume is not for backup servers only.   
070/05/8583	The RAID level of the specified volume is not supported.  
070/05/8586	The number of groups that can be set in the same storage system is invalid.
070/05/8587	The number of pairs that can be set in the same group is invalid.  
070/05/8588	The specified group number is not set.  
070/05/8589	The specified group name is invalid.  
070/05/8590	The group name and the number do not match.  
070/05/8591	The specified pair is already set in another group.  
070/05/8592	The command was rejected because the licensed capacity was exceeded.
070/05/8593	The P-VOL is a source volume for Auto LUN.
070/05/8594	The P-VOL is a target volume for Auto LUN.
070/05/8595	The specified P-VOL does not exist.  
070/05/8597	No more pairs can be created with the specified primary volume.
070/05/8598	The specified volume is not a P-VOL.  
070/05/8599	The specified volume is already used as a primary volume.
070/05/8600	The RAID level of the specified volume is not supported.  
070/05/8601	The specified S-VOL (Primary Volume) cannot be paired with a backup server volume.
070/05/8602	The command has been rejected, because the specified P-VOL has already been used as S-VOL of the other pair.
070/05/8603	The target volume is set as a primary volume for Data Migration.  
070/05/8604	The target volume is set as a secondary volume for Data Migration.  
070/05/8605	The Pairresync (Resync Pairs) command was issued to a device in the SMPL status.
070/05/8606	The operation to create an L2 pair was rejected because the P-VOL of the L1 pair is used as the P-VOL of a Continuous Access Synchronous pair.
070/05/8607	The operation cannot be performed because the selected secondary volume is used as a primary volume of a Continuous Access Synchronous pair or a Continuous Access Journal pair.
070/05/8608	The specified S-VOL is not defined.
070/05/8610	The S-VOL is a target volume for Auto LUN.
070/05/8611	The operation failed because the specified S-VOL was used as S-VOL of other pairs.
070/05/8612	The specified volume is not an S-VOL.  
070/05/8613	The RAID level of the specified S-VOL is not supported.  
070/05/8614	The operation cannot be performed because the selected secondary volume is used as a primary volume of a Continuous Access Synchronous pair or a Continuous Access Journal pair.
070/05/8615	The command cannot be run because the specified secondary volume is used as a secondary volume of a Continuous Access Synchronous pair.
070/05/8616	The S-VOL is used as a primary volume for Data Migration.  
070/05/8617	The target S-VOL is used as a secondary volume for Data Migration.
070/05/8618	The S-VOL is already defined as a P-VOL.  
070/05/8619	The specified S-VOL is defined as a source volume for Auto LUN.
070/05/8624	The command has been rejected, because there is no pair to be operated.
070/05/8625	The primary volume and secondary volume have the same LDEV ID.  
070/05/8626	The SMPL command could not be executed because the quick split operation is in progress.
070/05/8627	The Pairresync operation has been rejected, because pair status is COPY(SP)/COPY.
070/05/8628	The operation of the L1 pair failed because the L2 pair was in COPY(SP)/COPY status or PSUS(SP)/COPY status.
070/05/8629	The status mode specification is invalid.  
070/05/8630	The status mode type is invalid.  
070/05/8631	The specified CU number is invalid.  
070/05/8632	The timing of issuing the command is invalid.  
070/05/8633	The abnormal status is invalid.  
070/05/8637	The specified P-VOL is used as a source volume for Auto LUN.
070/05/8640	The operation cannot be performed due to either of the following reasons:\\n- There is a pair in the status of Reverse Copy or Quick Restore among pairs that share a primary volume.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/8641	The L1 pairs include a pair in the status of Reverse Copy or Quick Restore.
070/05/8642	The command has been rejected, because the specified S-VOL is shared as the P-VOL of the other pair and the pair is in the COPY(RS-R)/RCPY status.
070/05/8643	The Resync Pairs operation cannot be performed due to either of the following reasons:\\n- The specified pair is not in the PSUS status.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/05/8644	The operation failed because the pairs sharing a P-VOL contain a pair in other than PSUS or PSUE status.
070/05/8645	The Reverse Copy command could not be executed because the primary volume was shared with the primary volume of a remote replication pair.
070/05/8646	The Reverse Copy request was rejected, because the P-VOL was shared with a Remote Copy pair in the non-suspend status.
070/05/8647	The Reverse Copy command could not be executed because the secondary volume was shared with the primary volume of a remote replication pair.
070/05/8648	The boot device and the P-VOL do not match in the Paircreate (Create Pairs) command.
070/05/8649	Because the boot device is the S-VOL in the Pairsplit-S (Delete Pairs) command, the flag does not match.
070/05/8650	The boot device and the P-VOL do not match in the Paircreate (Create Pairs), Pairresync (Resync Pairs), or Pairsplit-S (Delete Pairs) command.
070/05/8652	The boot device is not a P-VOL nor S-VOL.  
070/05/8653	Because the boot device is the P-VOL in the Pairsplit-S (Delete Pairs) command, the flag does not match.
070/05/8654	Boot device and S-VOL do not match in Paircreate (Create Pairs), Pairresync (Resync Pairs), or Pairsplit-S (Delete Pairs) instruction.
070/05/8657	The Swap&Freeze option cannot be specified, because the mode 80 is on.
070/05/8695	The specified MU number is not less than or equal to 2.
070/05/8920	The pair operation cannot be performed due to either of the following reasons:\\n- The requirements for the operation on the L2 pair are not met because the L1 pair is not in the PSUS status.\\n- The pair operation was performed on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.
070/07/6012	An error occurred during Remote Web Console processing.
070/07/7111	An error occurred during Remote Web Console processing.
080/05/108101	The number of characters for the password is not valid.
080/05/108105	The serial number of the encryption key does not match the serial number of this storage system because the key is restored by using the backup file created by a different storage system.
080/05/2002	An error occurred during Remote Web Console processing.
080/05/2015	A connection error has occurred.
080/05/208200	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
080/05/2145	A connection error has occurred.
080/05/3003	An error occurred during Remote Web Console processing.
080/05/5010	An error occurred during Remote Web Console processing.
080/05/5099	An error occurred during Remote Web Console processing.
080/05/5510	The storage system is in internal process, or some other user is changing the configuration.
080/05/56301	An error occurred during Remote Web Console processing.
080/05/56302	An error occurred during Remote Web Console processing.
080/05/56303	An error occurred during Remote Web Console processing.
080/05/57101	An error occurred during Remote Web Console processing.
080/05/58572	An error occurred while connecting to the storage system.
080/05/58573	This function is not supported.
080/05/58574	An error occurred while connecting to the storage system.
080/05/58575	An error occurred while connecting to the storage system.
080/05/58576	A communication time-out error occurred in the storage system.
080/05/6000	An error occurred during Remote Web Console processing.
080/05/6012	An error occurred during Remote Web Console processing.
080/05/6023	An error occurred during Remote Web Console processing.
080/05/6036	An error occurred during Remote Web Console processing.
080/05/6040	An error occurred while connecting to the storage system.
080/05/6050	An error occurred during Remote Web Console processing.
080/05/6051	An error occurred during Remote Web Console processing.
080/05/6531	The SVP is busy.
080/05/65727	The password is different from the one that was input at the time of backup. Or, the backup file might be broken.
080/05/68761	An error occurred on the DKC side.
080/05/68766	The serial number of the encryption key does not match.
080/05/7060	An error occurred during Remote Web Console processing.
080/05/7111	An error occurred during Remote Web Console processing.
080/05/8001	An error occurred while connecting to the storage system.
080/05/8100	An error occurred while connecting to the storage system.
080/05/87777	The operation cannot be performed because a resource group is not locked.
081/05/1930	The operation cannot be performed because the specified volume is used as an external volume that is mapped for the online data migration.
082/22/105001	The form of Storage System Name is wrong. \\nPlease input the alphanumeric character and the sign (except \ / : , ; * ? " < > | % & ^) from 1 to 180 characters.
082/22/105002	The location form is wrong. Enter it with less than 180 alphanumeric characters and symbols (except \ / : , ; * ? " < > | % & ^).
082/22/105003	The form of where to make contact is wrong. Enter it with less than 180 alphanumeric characters and symbols (except \ / : , ; * ? " < > | % & ^).
085/05/5099	An error occurred during Remote Web Console processing.
085/05/55009	An invalid CLPR No. was detected.
085/05/55010	An invalid SLPR No. was detected.
085/05/55011	The entered CLPR name is not valid. It is the same as a CLPR name reserved for a different CLPR ID or includes characters other than alphanumeric ones.
085/05/55013	Invalid logon information is detected.
085/05/55014	The entered CLPR name is already used.
085/05/55017	The total of the values registered as the maximum number of users that can connect to each SLPR exceeds the value set as the maximum number of connections to the storage system. 
085/05/55021	The specified CU number is invalid.
085/05/55022	An attempt has been made to either register newly a CLPR that is already registered, or delete a CLPR that is not registered.
085/05/55023	An attempt has been made to either register newly a SLPR that is already registered, or delete a SLPR that is not registered.
085/05/55024	The configuration of the CLPR is already changed, or some parity groups or some virtual volumes are registered in a different CLPR.
085/05/55025	The configuration of the CLPR is already changed, or the settings of the parity group or the virtual volume are not valid.
085/05/55026	The specified port name (port number) is invalid.
085/05/55027	The configuration of the CLPR is already changed, or the cache size is not valid.
085/05/55028	The configuration of the CLPR is already changed, or the specified cache size is less than the minimum.
085/05/55029	The configuration of the CLPR is already changed, or the total cache size is not valid.
085/05/55033	The same port is already registered in a different SLPR.
085/05/55228	This function is not available. Open System Array Management is required to create CLPR.
085/05/56501	The logon information of the partition management function has been initialized because the conflicting information is detected.
085/05/56502	The operation to set the maximum number of connections has been cancelled because an attempt has been made to specify this value to less than the number of users who are currently connected. Check the maximum permissible number of connections.
085/05/56524	This function cannot be used by the storage partition administrator.
085/05/56536	The licensed capacity exceeds the maximum because of the configuration change.
085/05/57002	An unknown error was detected.
085/05/58310	Some of the shared memories of the storage system may be blocked, or the storage system is being maintained.
085/05/58311	Some of the cache memories of the storage system may be blocked, or the storage system is being maintained.
085/05/58312	The configuration cannot be changed because the write pending rate of the intended CLPR is too high. 
085/05/58315	A maintenance job (correction copy, drive copy, LDEV formatting, or LDEV shredding) is running on the storage system.
085/05/58316	Parity groups in CLPR are being migrated in the storage system. 
085/05/58317	The CLPR capacity is being changed on the storage system.
085/05/58318	An error occurred on the DKC while obtaining information about the progress of CLPR processing.
085/05/58339	The CLPR to which the specified parity groups belong cannot be changed, because the parity groups do not contain all of the journal volumes in a journal of Continuous Access Journal.
085/05/6011	An error occurred during Remote Web Console processing.
085/05/6012	An error occurred during Remote Web Console processing.
085/05/6022	An error occurred during Remote Web Console processing.
085/05/6024	An error occurred during Remote Web Console processing.
085/05/6038	The operation cannot be performed because any of the specified parameters is not valid.
085/05/65740	The operation cannot be performed because a configuration change is in progress on the local storage system.
085/05/7110	An error occurred during Remote Web Console processing.
085/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
085/05/75026	The specified parity group or virtual volume cannot be used because you do not have permission to access a resource group to which the parity group or the virtual volume belongs.
085/05/79008	The selected CLPR cannot be deleted.
085/05/79009	The parity group that you attempt to migrate has a Fast Snap pool volume defined.
085/05/8001	A communication time-out error occurred.
085/05/8002	An error occurred during Remote Web Console processing.
085/05/8401	The storage system requires maintenance.
085/07/6012	An error occurred during Remote Web Console processing.
085/07/7070	An error occurred during Remote Web Console processing.
085/07/7071	An error occurred during Remote Web Console processing.
085/21/105001	No parity group or virtual volume is selected.
085/21/105002	No CLPR is selected.
085/22/105001	No table row is selected.
085/22/105002	No table rows are selected.
085/22/105003	A CLPR name is not entered or the entered name is too long.
085/22/105004	The specified CLPR name cannot be used because it is reserved by the system.
085/22/105005	The value set for Total Cache Size is invalid.
085/22/105006	The value set for Resident Cache Size is invalid.
085/22/105007	The value set for Number of Resident Extents is invalid.
085/22/105009	The same CLPR name already exists.
085/22/105011	The value of Initial Number is not entered.
085/22/105017	No more CLPRs can be created because the number of CLPRs that can be created has reached the maximum.
085/22/105018	No parity groups or virtual volumes are selected in the Available Parity Groups or Available Virtual Volumes table.
085/22/105019	No CLPR is selected.
085/22/105020	CLPR names cannot be assigned to all of the selected CLPRs with the specified value of Initial Number.
085/22/105022	The capacity of CLPR might not reach the recommended value. Performance may be affected by this setup. Are you sure you want to continue this operation?
085/22/106001	No more CLPRs can be created because the number of CLPRs that can be created has reached the maximum.
085/22/106003	CLPR ID=0 cannot be deleted.
085/22/106004	A CLPR in which parity groups or virtual volumes are set cannot be deleted.
085/22/106006	A CLPR cannot be created because the cache capacity cannot be divided any further.
085/22/106007	There are no resources that can be migrated.
085/22/106008	There are no CLPRs with resources that can be migrated.
085/22/107001	The processing cannot continue due to an internal logic contradiction.
085/22/107002	The processing cannot continue due to an internal logic contradiction.
085/22/205187	CLPR names cannot be allocated to all specified CLPRs because the number of characters for CLPR names that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for a CLPR name.
086/05/6012	An error occurred during Remote Web Console processing.
086/05/6022	An error occurred during SVP processing. If this problem persists, please call the HSSC.
086/05/65753	Invalid character is included in the e-mail addresses or the server addresses.
086/05/65754	The number of characters specified in an e-mail address or a server address exceeds 255 characters.
086/05/65755	An attribute of the registered destination of messages is invalid.
086/05/65756	The SMTP authentication is enabled, but Account or Password is not specified.
086/05/65757	The same e-mail addresses are specified. 
086/05/66821	There is no e-mail address information file.
086/05/66822	The contents of the e-mail address information file are invalid.
086/05/66823	A failure occurred while communicating with the SMTP server.
086/05/7060	An error occurred during Remote Web Console processing.
086/21/209012	Are you sure you want to send a test e-mail based on the entered information in the window?
086/22/205032	No more e-mail address can be registered because the number of registered e-mail addresses has reached the maximum. 
086/22/205033	No destination addresses are registered.
086/22/205034	The e-mail address is already being used.
086/22/205035	A list of e-mail address attributes is not selected.
086/22/205036	The form of the e-mail address is wrong.
086/22/205037	The form of the Identifier is wrong.
086/22/205038	The form of the Account is wrong.
086/22/205039	The form of Password is wrong.
086/22/209002	A test e-mail was sent.
088/05/5010	An error occurred during Remote Web Console processing.
088/05/5013	An error occurred during Remote Web Console processing.
088/05/5018	No more report can be made.
088/05/5099	An error occurred during Remote Web Console processing.
088/05/6000	An error occurred during Remote Web Console processing.
088/05/6012	An error occurred during Remote Web Console processing.
088/05/6023	An error occurred during Remote Web Console processing.
088/05/6024	An error occurred during Remote Web Console processing.
088/05/6036	An error occurred during Remote Web Console processing.
088/05/6091	An error occurred while compressing a file.
088/05/6092	An error occurred during Remote Web Console processing.
088/05/6093	The report(s) has already been deleted.
088/05/8001	Making report was not completed within the prescribed time.
092/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
096/05/5013	An error occurred during Remote Web Console processing.
096/05/5030	No commands are issued.
096/05/5041	The number of issued commands exceeds the maximum.
096/05/5511	The program product is not installed.
096/05/58404	The specified operation cannot be executed because the LDEV shredding or the LDEV format is being executed.
096/05/58412	The attribute of the pool volume cannot be changed.
096/05/58413	The attribute of the Fast Snap secondary volume cannot be changed, because the pair status is not PAIR or PSUS.
096/05/58414	The attribute of the specified volume cannot be changed due to one of the following reasons:\\n-The specified volume is the primary volume of a Fast Snap pair whose status is RCPY.\\n-The specified volume is the secondary volume of a Fast Snap pair whose status is not PAIR or PSUS.
096/05/58418	The access attribute cannot be changed, because the status of the specified Continuous Access Journal volume is in PAIR or in COPY.
096/05/58422	An error occurred during Remote Web Console processing.
096/05/58423	An error occurred during Remote Web Console processing.
096/05/58424	The specified logical volume is blocked.
096/05/58429	The protection period is set to this logical volume.
096/05/58434	This logical volume is busy.
096/05/58435	This logical volume is busy.
096/05/58436	The access attribute of the logical volume has already been changed.
096/05/58438	This logical volume is configured as a command device.
096/05/58442	The emulation type of the logical volume is not OPEN-V.
096/05/58448	The specified logical volume is blocked, or the LDEV is being formatted or shredded.
096/05/58450	An error occurred during Remote Web Console processing.
096/05/6012	An error occurred during Remote Web Console processing.
096/05/6023	An error occurred during Remote Web Console processing.
096/05/6038	The mistake is found in the set parameter.
096/05/6502	Processing in progress.
096/05/6533	An error occurred during Remote Web Console processing.
096/05/6537	The setting process has not been executed because there is no error in this setting, but an error in the others settings. 
096/05/7060	An error occurred during Remote Web Console processing.
096/05/7111	An error occurred during Remote Web Console processing.
096/05/7310	This error code is not registered.
096/05/75015	The specified LDEV belongs to a resource group that you do not have permission to access.
096/05/76514	The setting operation cannot be done because all LDEVs allocated to the resource group have no access right for the resource group.
096/05/79010	The attribute cannot be changed because the selected LDEVs belong to a parity group with the capacity expansion enabled.
096/05/79011	The attribute of deduplication system data volumes cannot be changed.
096/05/8001	An error occurred while connecting to the storage system. Please retry a little later.
096/05/8002	A communication time-out error occurred in the storage system. Please wait for a while, and then retry the operation.
096/05/8102	This function is not supported.
096/05/8120	The specified logical volume does not exist.
096/05/8122	This logical volume is busy.
096/05/8123	This function is not supported.
096/05/8125	The attribute of the logical volume has been changed by RAID Manager.
096/05/8126	This logical volume is configured as a command device.
096/05/8128	A parameter error occurred.
096/05/8132	This error code is not registered.
096/05/8134	The attribute of this logical volume cannot be changed to Read/Write.
096/05/8135	The specified volume is a Continuous Access Synchronous secondary volume in COPY or PAIR status or a Business Copy secondary volume in COPY, PAIR, COPY (SP), COPY (RS), or COPY (RS-R) status.
096/05/8136	The command was rejected, because the licensed capacity was exceeded.
096/05/8138	The Reserved setting of the specified volume cannot be released.
096/05/8139	The attribute of the Business Copy primary volume cannot be changed because the pair status is COPY (RS-R).
096/05/8142	You cannot select this logical volume because it is used as a Continuous Access Journal volume.
096/05/8150	You tried to set a retention term to a logical volume whose access attribute is not Read Only or Protect.
096/05/8151	The retention term of the logical volume cannot be shortened.
096/05/8153	The specified retention term exceeds the maximum.
096/05/8154	The retention term of the logical volume has been changed by RAID Manager.
096/05/8155	You cannot change the access attribute because a retention term is set to the specified logical volume.
096/05/8156	You cannot change the access attribute because the expiration lock is set to Enable.
096/10/7060	An error occurred during Remote Web Console processing.
096/10/7442	There is an invalid value in the Volume Retention information.
096/10/8112	There is no valid volume.
096/10/9107	The value that is under setup is not reflected yet. Do you want to continue the operation?
096/10/9362	Do you want to change the expiration lock mode?
096/10/9363	The specified retention term exceeds the maximum.
100/21/209018	Are you sure you want to transfer the Audit Log to the Primary Server based on the applied information?
100/21/209019	Are you sure you want to transfer the Audit Log to the Secondary Server based on the applied information?
100/22/205041	The Primary Server and the Secondary Server have the same settings.
100/22/205048	The form of the User Name is wrong.
100/22/205049	The form of the Password is wrong.
100/22/205050	The form of the Output Folder is wrong.
101/21/109208	It is restored by the encryption key of the specified file.\\nAre you sure you want to overwrite the encryption key information?
101/21/109210	Creating encryption keys should be limited to 30 in case of necessity for updating those keys.  
101/21/209021	Are you sure you want to initialize the encryption settings?
101/22/105194	An error occurred or an interruption request was made while formatting.
101/22/105195	An error occurred while preparing the quick format.
101/22/105196	The specified encryption key cannot be deleted because it is not created.
101/22/105197	The specified encryption key cannot be deleted because it is already used.
101/22/105204	The operation cannot be performed because the program product is not installed or you do not have permission to edit.
101/22/105235	There is no parity group available for making or releasing encryption settings.
101/22/105237	Format Type is not selected.
101/22/105239	The encryption settings have not changed.
101/22/105240	The selected parity group is not blocked.
101/22/105276	The encryption cannot be set for the specified parity group because it is for an external volume.
101/22/105461	Completed successfully.
101/22/105462	The key management server is not set.
101/22/105463	Invalid port number.
101/22/105464	Invalid time-out value.
101/22/105465	Invalid retry interval.
101/22/105466	The number of retries is invalid.
101/22/105467	The password cannot be entered.
101/22/105470	The key management server is disabled. 
101/22/105471	There are no encryption keys already created.
101/22/105480	The total of the entered values exceeds the maximum.
101/22/105481	The value in the Total column was updated because the total of the respective minimum number of characters below exceeded the value in the Total column.\\n- Numeric Characters (0-9)\\n- Uppercase Characters (A-Z)\\n- Lowercase Characters (a-z)\\n- Symbols
101/22/105482	You have not agreed to the notice for the key generation protection.
101/22/105490	The setting of the key management server is changed.
101/22/105491	The key encryption key cannot be registered.
101/22/105493	The operation cannot be performed because the encryption environmental settings are initialized.
101/22/105494	The specified encryption key cannot be deleted because it is being used.
101/22/105495	The encryption setting cannot be performed because there are not enough encryption keys available for the setting.
101/22/105496	There are no certificate encryption keys.
101/22/105497	An encryption key is not created on the key management server.
101/22/105498	A key encryption key is not created on the key management server.
101/22/105499	A key encryption key cannot be acquired from the key management server.
101/22/105500	Reacquisition of a key encryption key is unnecessary.
101/22/105501	The edit encryption environmental settings cannot be initialized because there is a parity group being encrypted. 
101/22/105502	The backup information of the encryption key does not exist on the key management server.
101/22/105503	The backup information of the encryption key does not exist on the key management server.
101/22/105504	No more encryption keys can be created.
101/22/106081	The re-entered password does not match the one entered previously.
101/22/106082	The operation cannot be performed because a task is in progress.
101/22/106084	The size of the specified file is too large.
101/22/106088	All LDEVs in a parity group on which encryption is enabled are not blocked.
101/22/107001	An internal logic error occurred.
101/22/107002	An internal logic error occurred.
101/22/109029	Be sure to back up after the task is complete.
101/22/205196	Quick Format cannot be specified as Format Type because the parity groups with the capacity expansion enabled are contained.
101/22/206336	A regular backup of the encryption key cannot be performed, because the key management server is not set, or the KMIP mode of the key management server is off.
101/22/206337	The regular backup user cannot be authenticated.
101/22/206338	A regular backup of the encryption key cannot be performed, because the Security Administrator (View & Modify) role is not assigned to the regular backup user.
101/22/206339	A regular backup of the encryption key cannot be performed, because the license for DKA Encryption is not installed.
101/22/206340	No time is selected for Regular Backup Time.
101/22/206341	The name of the current user is entered in the User Name field of Regular Backup User.
101/22/206342	Regular backups are now set.
101/22/206343	The user name or password for the regular backup user is not entered.
101/22/206344	RegularBackup_ cannot be included in any character string entered in the Description field.
101/26/105001	The upper limit of encryption key backup is 256.
101/26/105002	The client certificate file or the password of client certificate file is invalid.
101/26/105003	The root certificate file is invalid.
101/26/105004	A message is returned from the server.
101/26/105005	Failed to communicate with the key management server.
101/26/105006	Failed to communicate with the key management server.
101/26/105007	The specified encryption key information is damaged.
101/26/105008	The key wrapping key information of the specified encryption key is damaged.
101/26/105009	The specified encryption key was not found in the key management server.
101/26/105010	Failed to delete the specified encryption key from the key management server.
101/26/105011	The deletion operation of the encryption key stopped because the key wrapping key of the specified encryption key cannot be deleted from the key management server.
101/26/105012	Failed to delete the specified encryption key from the key management server.
101/26/105013	Failed to delete the key wrapping key of the specified encryption key from the key management server. 
101/26/105014	Deleting the specified encryption key has been executed, but the processing result could not be obtained.
101/26/105015	The deletion operation of the encryption key stopped because the processing result could not be obtained when deleting the key wrapping key of the specified encryption key from the key management server.
101/26/105016	The "Setup Key Management Server" is not configured.
101/26/105017	The "Setup Key Management Server" is not configured.
101/26/105018	The "Setup Key Management Server" is not configured.
101/26/105019	The "Setup Key Management Server" is not configured.
101/26/105020	The "Key Management Server" is disabled.
101/26/105021	A time-out error occurred during communication with the key management server.
101/26/105022	The connected key management server does not support the required functions.
101/26/107001	The processing cannot continue due to an internal logic contradiction.
101/26/107002	The processing cannot continue due to an internal logic contradiction.
101/26/107003	The processing cannot continue due to an internal logic contradiction.
101/26/107004	The processing cannot continue due to an internal logic contradiction.
200/20/105212	Characters or the number of characters for the user name is not valid.
200/20/106043	No more users can be created because the number of registered users has reached the maximum.
200/20/106045	The password cannot be changed because the authentication method of the specified user is not Local.
200/20/106051	The number of user groups to which the user belongs has reached the maximum.
200/20/106061	Characters or the number of characters for the user group name is not valid.
200/20/106069	The specified user cannot be removed from the user group because the user will belong to no user group.
200/20/106200	The authentication method is not valid.
200/20/106201	All users in Administrator User Group cannot be disabled.
200/20/106202	The specified user does not belong to the specified user group.
200/20/106203	The specified user already belongs to the specified user group.
200/20/107000	An error occurred during Remote Web Console processing.
200/20/107001	An error occurred during Remote Web Console processing.
200/20/107002	An error occurred during Remote Web Console processing.
200/20/107003	Decryption failed.
200/20/107004	An error occurred during Remote Web Console processing.
200/20/107005	An error occurred during Remote Web Console processing.
200/20/107006	An error occurred during Remote Web Console processing.
200/20/107007	Decryption failed.
200/20/107008	An error occurred during Remote Web Console processing.
200/20/107009	An error occurred during Remote Web Console processing.
200/20/107010	An error occurred during Remote Web Console processing.
200/20/107011	The parameter is invalid.
200/20/107012	An error occurred during Remote Web Console processing.
200/20/107013	Failed to get an IP address.
200/20/107014	An error occurred during Remote Web Console processing.
200/20/107015	An error occurred during Remote Web Console processing.
200/20/107016	An error occurred during Remote Web Console processing.
200/20/107017	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107018	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107019	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107020	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107021	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107022	The same path is specified in the output source and the output target.
200/20/107023	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107024	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107025	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107026	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107027	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107028	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107029	A file or a directory of the specified path does not exist, or the access is rejected.
200/20/107030	An error occurred during Remote Web Console processing.
200/20/107031	An error occurred during Remote Web Console processing.
200/20/107032	An error occurred during Remote Web Console processing.
200/20/107033	An error occurred during Remote Web Console processing.
200/20/107034	An error occurred during Remote Web Console processing.
200/20/107035	An error occurred during Remote Web Console processing.
200/20/107036	The capacity of a memory is insufficient to login.
200/20/107037	The number of sessions per IP address exceeds the maximum.
200/20/107038	The number of sessions per Tomcat session exceeds the maximum.
200/20/107039	The number of sessions in the entire system exceeds the maximum.
200/20/107040	An error occurred during Remote Web Console processing.
200/20/107041	An error occurred during Remote Web Console processing.
200/20/107042	Failed to start the session due to no user authority.
200/20/107043	Failed to save the specific information of user.
200/20/107044	Failed to save the specific information of user.
200/20/107045	Failed to save the specific information of user.
200/20/107046	A network error occurred. The cause might be one of the following.\\n- The SVP is not ready.\\n- An error occurred on the SVP.\\n- A time-out error occurred during communication with the SVP.
200/20/107047	An error occurred during Remote Web Console processing.
200/20/107048	The capacity of a memory is insufficient to handle requests.
200/20/107049	An error occurred during Remote Web Console processing.
200/20/107050	An error occurred during Remote Web Console processing.
200/20/107051	Failed to login.
200/20/107052	Failed to convert an XML file.
200/20/107053	The parameter is specified incorrectly.
200/20/107054	The parameter is specified incorrectly.
200/20/107055	The number of onetime keys has exceeded the maximum.
200/20/107056	The specified onetime key already exists.
200/20/107057	The certificate does not exist.
200/20/107058	Failed to create a certificate object.
200/20/107059	The key store file does not exist.
200/20/107060	Failed to get a certificate.
200/20/107061	Failed to access the key store file.
200/20/107062	Failed to initialize the key store file.
200/20/107063	Failed to access the key store file.
200/20/107064	Failed to get a certificate.
200/20/107065	The key store file does not exist.
200/20/107066	Failed to read the key store file.
200/20/107067	The specified alias does not exist.
200/20/107068	The key store file does not exist.
200/20/107069	The specified alias does not exist.
200/20/107070	Failed to read the key store file.
200/20/107071	Failed to get a certificate.
200/20/107072	The key store file does not exist.
200/20/107073	The specified alias does not exist.
200/20/107074	Failed to access the key store file.
200/20/107075	Failed to delete a certificate.
200/20/107076	Failed to read a key store object.
200/20/107077	Failed to read a key store object.
200/20/107078	Failed to read a key store object.
200/20/107079	Failed to read a key store object.
200/20/107080	Failed to read a key store object.
200/20/107081	Failed to store a key store object.
200/20/107082	Failed to store a key store object.
200/20/107083	Failed to store a key store object.
200/20/107084	Failed to store a key store object.
200/20/107085	Failed to store a key store object.
200/20/107086	Failed to authenticate the onetime key.
200/20/107087	Failed to authenticate the onetime key.
200/20/107088	Failed to authenticate the onetime key.
200/20/107089	Failed to authenticate the onetime key.
200/20/107090	Failed to authenticate the onetime key.
200/20/107091	Failed to authenticate the onetime key.
200/20/107092	Failed to authenticate the onetime key.
200/20/107093	Failed to register a onetime key.
200/20/107094	The number of onetime keys has exceeded the maximum.
200/20/107095	Failed to authenticate the user account. 
200/20/107096	The specified group ID does not exist.
200/20/107097	Failed to store the user information.
200/20/107098	The user information of the specified onetime key does not exist.
200/20/107099	Failed to get the user information from the specified onetime key.
200/20/107100	The user information of the specified global session ID does not exist.
200/20/107101	Failed to get the user information from the specified global session ID.
200/20/107102	The user session was interrupted. 
200/20/107105	NAS Unified Firmware Configuration Backup cannot be performed.
200/20/108000	The application cannot be started or was terminated forcibly.
200/20/205001	Characters or the number of characters for the role name is not valid.
200/20/205002	The specified user group does not exist.
200/20/205003	The specified user does not exist.
200/20/205004	The resource group assignment cannot be changed because the specified user group applies to All Resource Groups Assigned.
200/20/206001	No more user groups can be registered because the number of registered user groups has reached the maximum.
200/20/206002	The same user group name is already registered.
200/20/207001	The specified role does not exist.
200/20/207002	The specified user account cannot be changed because it is a built-in account.
200/20/207003	The specified user group cannot be changed because it is a built-in group.
200/20/207004	The specified user group cannot be deleted because there will be users that belong to no user group.
200/20/207005	The user name or password is not valid.
200/20/207006	You do not have permission to change the password.
200/20/207008	An internal error occurred on the storage system.
200/20/207009	An internal error occurred on the RMI server.
200/20/208001	An error occurred between the RMI server and the storage system.
201/21/105001	No table rows are selected.
201/21/105002	Two or more table rows are selected.
201/21/105003	No table row, or two or more table rows are selected.
201/21/105004	Other than the numeric value is input.
201/21/105005	Become the object of the automatic deletion.
201/21/105006	Please specify two digits or four digits for a value specified for the data pattern. 
201/21/105007	No table row is selected.
201/21/106001	There is an error in the input content.
201/21/107021	An internal logic error occurred.
201/21/107022	An error occurred during SVP processing.
201/21/107023	An internal logic error occurred.
201/21/107024	A communication error has occurred.
201/21/107025	The user session was interrupted. 
201/21/107026	An internal logic error occurred.
201/21/107027	The window cannot be opened.
201/21/107090	An internal logic error occurred.
201/21/107091	An I/O error occurred during downloading.
201/21/107092	A security error occurred during downloading.
201/21/107093	An internal logic error occurred.
201/21/107094	An I/O error occurred during uploading.
201/21/107095	A security error occurred during uploading.
201/21/107096	A time-out error occurred on the Flash Player.
201/21/107097	No response from the Flash Player.
201/21/107098	No response from the Flash Player.
201/21/107099	The Flash Player memory is not enough.
201/21/109001	Are you sure you want to remove the selected row(s)?
201/21/109002	Do you want to cancel?
201/21/109003	The settings that have been done in the following windows will be discarded or cancelled. Are you sure you want to continue?
201/21/109004	Do you want to log out?
201/21/109005	Do you want to apply?
201/21/109007	Forcibly releasing the system lock might have a significant impact on the operation of the storage system. Resource groups locked not from the SVP are not released. Before releasing the system lock, contact the administrator of the storage system to verify that there is no problem to do it. Are you sure you want to forcibly release the system lock?
201/21/109096	This download process cannot be canceled.
201/21/209020	Do you want to close this window? 
201/22/105054	The task cannot be changed to the specified status.
201/22/105055	The number of registered tasks has reached the maximum.
201/22/105056	The task execution is inhibited.
201/22/105059	The task cannot be deleted. 
201/22/105061	The task cannot be suspended.
201/22/105063	The task cannot be restarted. 
201/22/105065	The task cannot be aborted.
201/22/105066	This task cannot be aborted.
201/22/105068	The auto delete has already been set to disable.
201/22/105069	The auto delete has already been set to enable.
201/22/105278	This operation has a possibility to cause conflict of setting items with the task of "In progress" or "Not run". Note the conflict of set items.\\nDo you want to continue?
201/22/105369	IP address is not input in the form of IPv4.
201/22/105370	IP address is not input in the form of IPv6.
201/22/105477	The entered password is outside the setting range.
201/22/105478	The entered password does not meet the password policy.
201/22/105479	Writing into the password policy file cannot be performed.
201/22/105489	The entered task name is invalid.
201/22/106004	An unexpected error occurred.
201/22/106039	An error occurred.
201/22/106056	An error occurred.
201/22/106057	An error occurred.
201/22/106058	An error occurred.
201/22/106059	An error occurred.
201/22/106060	An error occurred.
201/22/106061	An error occurred.
201/22/106072	The tree node cannot be expanded any further.
201/22/106073	Only a host registered in a group is allowed to access a LUN that is defined in the target group. A host that is not registered in any group is not allowed to access any LUN. Do you want to continue this operation?
201/22/106074	All the hosts connected to the target ports are only allowed to access a LUN that is defined in the group #00. This will lead the possibility that LUNs, which are defined in the group other than #00 being used at present, cannot be recognized, then the file system might be destroyed. Do you want to continue this operation? 
201/22/106075	The configuration does not become effective until the security switch is turned on.
201/22/106079	The specified resources cannot be displayed due to either of the following reasons.\\n- Changed configuration\\n- No permission to access the resources
201/22/106089	Are you sure to execute "Shred LDEVs" ? This task execution deletes all of the target LDEV data and the data cannot be recovered.
201/22/107019	An internal logic error occurred.
201/22/108029	Remote Web Console cannot be used because there is no license of Remote Web Console. 
201/22/108030	There is a license that {0} day(s) remain to end.
201/22/108031	There is a license that {0} day(s) remain to end, or a license whose capacity is insufficient.
201/22/108032	Remote Web Console cannot be used because there is no reference authority of Remote Web Console. 
201/22/108033	A time-out error occurred. 
201/22/109001	The processing is terminated normally.
201/22/109002	The processing is not executed.
201/22/109003	The number of tasks with auto delete disabled has reached the maximum. Therefore, the execution of the tasks are inhibited at present.
201/22/109015	The task could not complete execution. because the Remote Web Console stopped.
201/22/109025	This operation resets your view settings such as table columns and filter conditions that you customized. Are you sure you want to execute "Reset View Settings"?
201/22/205072	There are no resources necessary to perform the specified operation.
201/22/205073	You do not have permission to perform the specified operation.
201/22/205074	The program products necessary to perform the specified operation are not installed.
201/22/205135	The password is not valid.
201/22/205147	The user ID or the password is not valid.
201/22/205148	The user ID or the password with which the task was registered is not valid.
201/22/205156	Remote Web Console cannot be used because there is no license of Remote Web Console. 
201/22/205157	Remote Web Console cannot be used because there is no reference authority of Remote Web Console. 
201/22/206520	The password of the user currently logged in will be changed. The operation will be failed after the password changed.
201/22/207001	An error occurred during communication with the storage system.
201/22/207005	In the process of re-registering tasks in queue due to Remote Web Console restart, a task could not be registered because an operation target in the task is included in an already registered task.
201/22/208001	In the process of re-registering tasks in queue due to Remote Web Console restart, a task could not be registered because the Remote Web Console software version is changed.
201/22/208003	A communication error occurred during processing.
201/23/107000	An internal logic error occurred.
201/23/107001	An internal logic error occurred.
201/23/107002	An internal logic error occurred.
201/23/107003	An internal logic error occurred.
201/23/107004	An internal logic error occurred.
201/23/107005	An internal logic error occurred.
201/23/107006	An internal logic error occurred.
201/23/107007	Refresh is being processed.
201/23/107008	An error occurred while refreshing.
201/23/107009	An error occurred while refreshing.
201/23/107010	An error occurred while refreshing.
201/23/107011	Failed to get the RMI Lock.
201/23/107012	Failed to release the RMI Lock.
201/23/107013	An error occurred while refreshing.
201/23/107014	An error occurred while refreshing.
201/23/107015	A network error occurred. It is not possible to connect with the SVP due to one of the following reasons.\\n- The SVP was not ready.\\n- An error occurred in the SVP.\\n- A timeout error occurred while communicating with the SVP.
201/23/107016	A network error occurred. It is not possible to connect with the SVP due to one of the following reasons.\\n- The SVP was not ready.\\n- An error occurred in the SVP.
201/23/107017	An error occurred during Remote Web Console processing.
201/23/107018	A network error occurred. It is not possible to connect with the SVP because a timeout error occurred while communicating with the SVP.
201/23/107019	Failed to restore the user account list file.
201/23/107020	An unsupported version of JRE is used. 
201/23/107021	An internal logic error occurred.
201/23/107022	An internal logic error occurred.
201/23/107023	An internal logic error occurred.
201/23/107024	The content of a task conflicts with a task already in process.
201/23/107025	The operation failed, because the configuration information was being changed.
201/23/107026	The operation failed because the storage system performed refreshing internally.
201/23/107027	The refreshing operation was not completed because the configuration was changing.
201/23/107028	A network error occurred. The cause might be one of the following.\\n- The SVP is not ready.\\n- An error occurred on the SVP.\\n- A time-out error occurred during communication with the SVP.
201/23/108000	An internal logic error occurred.
201/23/108001	An internal logic error occurred.
201/23/108002	An internal logic error occurred.
201/23/108003	An internal logic error occurred.
201/23/108004	An error occurred in the disk storage system. The configuration may be inconsistent.
202/22/105004	The task for the operation is not selected.
202/22/105005	A task which is not in the state of suspend is in the specified task. Or, you have not a permission to operate the task status.
202/22/105006	A task which is not in the state of waiting is in the specified task. Or, you have not a permission to operate the task status.
202/22/105007	A task which is being executed is in the specified task. Or, you have not permission to operate the task operations.
202/22/105008	Failed to execute the task operation.
202/22/105206	Failed to restore the confirmation data.
202/22/105306	You do not have permission to view the detailed information for the specified task.
202/22/105307	You do not have permission to view the status of the specified task.
202/22/106040	Detailed information cannot be displayed due to status unknown.
202/22/109004	The task ({0}) is not performed.
202/22/109005	The task ({0}) is in progress.
202/22/109006	The task ({0}) is complete.
202/22/109007	An error occurred during the task ({0}) processing.
202/22/109008	An error occurred during the task ({0}) processing. \\nVerify the details of the error with the error code in the following list.
202/22/109009	The task ({0}) is aborted.
202/22/109010	The task ({0}) is suspended.
202/22/109011	An error occurred during the task ({0}) processing. Due to the error, some settings cannot be applied because the internal processing has been interrupted.\\nVerify all configuration settings of the task, including ones applied normally, and then retry the operation.
202/22/109017	The task ({0}) to request a start of processing is complete.
202/22/109021	Check the error details with the error code from the following list.
203/05/5013	An error occurred during Remote Web Console processing.
203/05/5099	An error occurred during Remote Web Console processing.
203/05/6011	An error occurred during Remote Web Console processing.
203/05/6012	An error occurred during Remote Web Console processing.
203/05/6023	An error occurred during Remote Web Console processing.
203/05/6036	An error occurred during Remote Web Console processing.
203/05/7060	An error occurred during Remote Web Console processing.
203/05/7310	An error occurred during Remote Web Console processing.
203/05/76500	The selected MP unit is not mounted.
203/05/76501	The selected MP unit is blocked.
203/05/78000	The selected MP unit is not mounted.
203/05/78001	An error occurred during Remote Web Console processing.
203/05/78002	An error occurred during Remote Web Console processing.
203/05/8000	An error occurred during Remote Web Console processing.
203/05/8001	A communication time-out error occurred.
203/05/8100	An error occurred while connecting to the storage system.
203/22/107001	The processing cannot continue due to an internal logic contradiction.
204/22/105241	The operation can not be performed due to one of the following reasons:\\n- The Smart Tiers function is not enabled.\\n- The shared memory for the Smart Tiers function is not installed.
204/22/105242	The operation can not be performed due to one of the following reasons:\\n- The Smart Tiers function is not enabled.\\n- The shared memory for the Smart Tiers function is not installed.
204/22/105243	There is no pool information.
204/22/105244	There is no V-VOL information.
204/22/105247	There is no pool or V-VOL information.
204/22/105486	The operation cannot be performed because the Smart Tiers function is not enabled.
204/22/106076	The specified monitoring period cannot be set.
204/22/106077	Four or more drive types cannot be added to the specified pool.
204/22/106080	A volume of different RAID level cannot be specified in the same drive type.
204/22/106110	The current monitoring data will be deleted due to one of the following reasons. Do you want to continue? \\n- The tier management is changed from Auto to Manual. \\n- The monitoring mode is changed.
204/22/107001	The processing cannot continue due to an internal logic contradiction.
204/22/107002	The processing cannot continue due to an internal logic contradiction.
205/20/107001	Failed to create a report.
205/20/107002	Failed to create a report.
205/20/107003	Failed to create a report.
205/20/107004	Failed to read the log preference.
205/20/107005	The parameter is specified incorrectly.
205/20/107006	Failed to read the preference.
205/20/107007	There is no report to be created.
205/20/107008	There is no input directory.
205/20/107009	The contents of csv file are incorrect.
205/20/107010	Failed to create a report.
205/20/107011	Failed to create a report.
205/20/107012	Failed to create a report.
205/20/107013	Failed to create a report.
205/20/107014	Failed to create a report.
205/20/107015	Failed to create a report.
205/20/107016	Failed to create a report.
205/20/107017	Failed to create a report.
205/20/107018	Failed to create a report.
205/20/107019	Failed to create a report.
205/20/107100	Succeeded to create a report file.
205/20/107107	Failed to create a report file.
205/20/109001	Succeeded to create a report.
205/20/109002	Succeeded to create a report except for a few report files.
205/22/105268	Failed to delete the report.
205/22/105269	Failed to create a report.
205/22/105282	A report cannot be created any more because the number of reports that can be created has reached the maximum.
205/22/105310	You do not have permission to access the specified report.
205/25/107001	The specified report does not exist.
205/25/107002	You do not have permission to execute the specified command.
205/25/107003	The specified parameters are incorrect.
205/25/107004	An internal logic error occurred.
205/25/107005	No more reports can be made.
205/25/107006	Failed to get a list of reports.
205/25/107007	The current software version does not support the specified command.
205/25/107008	The specified function is not available because the necessary program product is not installed.
205/25/107009	You do not have permission to perform operations on the specified resources.
205/25/107010	An internal logic error occurred.
205/25/107011	You do not need to delete the report because the number of created reports does not reach the maximum.
205/25/107012	There is no created report.
205/25/107013	The specified report name is too long.
205/25/107014	The specified report name is invalid.
205/25/107015	There is no downloadable report.
205/25/107016	The specified report cannot be downloaded.
205/25/107017	There is no deletable report.
205/25/107018	The specified report cannot be deleted.
205/25/107019	The specified relocation log does not exist.
205/25/107020	There is no relocation log.
205/25/107021	The specified relocation log name exceeds 32 characters.
205/25/107022	The specified relocation log name is not valid.
205/25/107023	The operation cannot be performed because a relocation log is being added.
205/25/107024	The operation cannot be performed because a relocation log is being downloaded.
205/25/107025	The operation cannot be performed because a relocation log is being deleted.
205/25/107026	No more relocation logs can be added.
205/25/107027	There is no relocation log.
206/24/107000	Failed to login.
206/24/107001	An internal logic error occurred.
206/24/107002	Failed to access the system property.
206/24/107003	An internal logic error occurred.
206/24/107004	An error occurred while connecting to the session control server.
206/24/107005	An internal logic error occurred.
206/24/107006	Login cannot be performed because the load on the SVP is high.\\nRestart the SVP. If this problem persists, contact the HSSC.
206/24/107007	Logout cannot be performed because the load on the SVP is high.\\nRestart the SVP. If this problem persists, contact the HSSC.
207/05/2015	An error occurred while communicating with the storage system.
207/05/208396	The operation cannot be performed, because the following LDEVs do not belong to the same resource group:\\n- Pool volumes of pools for which the deduplication setting is enabled\\n- Deduplication system data volumes that are associated with pools for which the deduplication setting is enabled
207/05/5013	An error occurred during Remote Web Console processing.
207/05/5099	An error occurred during Remote Web Console processing.
207/05/5827	An error occurred during Remote Web Console processing.
207/05/5828	An error occurred during Remote Web Console processing.
207/05/6012	An error occurred during Remote Web Console processing.
207/05/6022	An error occurred during Remote Web Console processing.
207/05/6533	An error occurred during Remote Web Console processing.
207/05/6537	The setting process has not been executed because there is no error in this setting, but an error in the others settings. 
207/05/65740	The configuration changing processes are conflicting at DKC.
207/05/72124	The specified operation type is not supported.
207/05/75101	An error occurred during Remote Web Console processing.
207/05/76101	The number of requests exceeds the maximum number that can be processed.
207/05/76102	An incorrect ResourceGroupID was specified.
207/05/76103	The specified ResourceGroupID has already been specified.
207/05/76104	The number of characters for resource group name should be from 1 to 32.
207/05/76105	Invalid characters are used in the specified resource group name. \/:,;*?"<>| and any spaces on the beginning and ending of the name cannot be used.
207/05/76106	The specified resource group name is already registered.
207/05/76107	The specified number of resources has reached the upper limit.
207/05/76108	The resource to be migrated is not specified.
207/05/76109	The LDKC, CU, and LDEV are not set within the available range.
207/05/76110	The specified resource is already used.
207/05/76111	The parity group ID is not set within the available range.
207/05/76112	The specified parity group is not mounted.
207/05/76113	The specified resource is already used.
207/05/76114	Invalid port number.
207/05/76115	The specified resource is already used.
207/05/76116	The host group ID is not set within the available range.
207/05/76117	The specified resource is already used.
207/05/76118	The specified LDEVs cannot be migrated because they are a part of a Pool-VOL.  
207/05/76121	The specified LDEVs cannot be migrated because they are a part of a journal group.
207/05/76122	The specified parity groups cannot be migrated because they are registered as a part of a RAID Group.
207/05/76123	Migration of resources that belong to different resource groups cannot be done.
207/05/76126	The LUSE value of the specified virtual LDEV is invalid.
207/05/76127	The specified emulation type cannot be used.
207/05/77101	Any of the virtual storage system number, resource group number, or resource group name is not valid.
207/05/77102	The specified resource group name has already been specified.
207/05/77103	The specified resource group does not exist in the configuration.
207/05/77104	A resource group cannot be deleted because resources are included in the specified resource group. 
207/05/77106	A resource group is not specified or the number of resource groups that can be specified at a time exceeds the maximum.
207/05/77108	The resources on which LU paths are set cannot be added to or removed from the resource group whose virtual mode is set to ON.
207/05/77109	The specified resource cannot be set because the resource belongs to a resource group whose virtual mode is not set to ON. 
207/05/77110	The specified virtual fiber address is invalid.
207/05/77111	The channel package of the port to which the specified host group belongs is not supported.
207/05/77112	Two or more resource groups are specified. 
207/05/77113	The resources on which LU paths are set cannot be added to or removed from the resource group whose virtual mode is set to ON.
207/05/77114	The specified resource is already used.
207/05/77115	The value of SSID is not set within the available range.
207/05/77116	The specified Virtual Storage Machine does not exist.
207/05/77117	There is a locked resource in the specified resource group.
207/05/77118	The number of Virtual Storage Machines exceeds the maximum that can be registered.
207/05/77119	The specified model is not supported.
207/05/77120	The operation cannot be performed because the specified combination is already used by a different Virtual Storage Machine.
207/05/77121	The operation cannot be performed because the specified LDEV IDs include an LDEV ID that belongs to a different virtual storage machine.
207/05/77122	The device name or the virtual LDEV information is not set for the specified LDEV ID.
207/05/77123	The device name or the virtual LDEV information is defined for the specified LDEV ID.
207/05/77125	The operation cannot be performed because the multi-array virtualization function is not enabled.
207/05/77126	The operation cannot be performed because the specified LDEV belongs to the Virtual Storage Machine number 0.
207/05/77127	The operation cannot be performed because the specified LDEV belongs to other than the Virtual Storage Machine number 0.
207/05/77128	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do not match.
207/05/77129	The operation cannot be performed because the LDEV ID and the virtual LDEV ID match.
207/05/77130	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do not match.
207/05/77131	The operation cannot be performed because the specified LDEV is used by a High Availability pair.
207/05/77132	The operation cannot be performed because the specified LDEV is used by an Auto LUN pair.
207/05/77133	The operation cannot be performed because the Virtual Attribute is HA Reserved.
207/05/77134	The operation cannot be performed because the Virtual Attribute is not Normal.
207/05/77135	The operation cannot be performed because the host I/O operation is performed for the specified LDEV ID.
207/05/77136	The operation cannot be performed because an LDEV is assigned to the specified LDEV ID.
207/05/77137	Host groups and LDEVs or iSCSI targets and LDEVs, to which LU paths are set, cannot be migrated to different virtual storage machines.
207/05/77138	LDEVs, to which device names or virtual LDEV information is set, cannot be migrated between resource groups of different Virtual Storage Machines. 
207/05/77139	The operation cannot be performed because the resource lock of Resource Group ID 0 is not set.
207/05/77144	This function is not available. Resource Partition is required.
207/05/77146	No more resource groups can be deleted because no resource group remains on the virtual storage machine.
207/05/77147	The operation cannot be performed because the specified LDEV is used by a Continuous Access Synchronous pair.
207/05/77148	The operation cannot be performed because the specified LDEV is used by a Continuous Access Journal pair.
207/05/77149	The operation cannot be performed because LU paths are set to the specified LDEV ID.
207/05/77150	The specified virtual LDEV ID is already used.
207/05/77151	The operation cannot be performed because the specified LDEV is used as a journal volume.
207/05/77152	The specified serial number or the controller ID is invalid.
207/05/77153	Quorum disks are included in the items to be maintained.
207/05/77154	The operation cannot be performed because the volume with the specified LDEV ID is an LDEV with the ALU attribute.
207/05/77155	The operation cannot be performed because the volume with the specified LDEV ID is an LDEV with the SLU attribute.
207/05/77160	Virtual Configuration (Emulation Type, CVS Settings, Number of Concatenated LDEVs, and SSID) cannot be set to the specified LDEVs that belong to the virtual storage machine.
207/05/77161	The S-VOL attribute cannot be assigned to the specified LDEVs that belong to the virtual storage machine.
207/05/78065	The operation cannot be performed because the storage system is in internal process, or the configuration is being changed by a different operation.
207/05/8000	An error occurred during Remote Web Console processing.
207/05/8102	This function is not supported.
207/05/8966	An error occurred on the DKC side.
207/21/105001	No table rows are selected.
207/21/105003	No table row, or two or more table rows are selected.
207/21/105007	No table row is selected.
207/21/109001	Are you sure you want to remove the selected row(s)?
207/22/105283	"meta_resource" cannot be specified to the resource group name.
207/22/105284	The specified resource group name is already used or reserved.
207/22/105285	No more resource groups can be created.
207/22/105286	No more resource groups can be created.
207/22/105287	The resource group name has not been changed.
207/22/105288	There are no resources that can be added.
207/22/105289	There are no resources that can be added.
207/22/105290	A resource group cannot be deleted because resources are included in the specified resource group.
207/22/105291	meta_resource cannot be deleted.
207/22/105292	meta_resource cannot be edited.
207/22/105293	Resources cannot be added to meta_resource.
207/22/105294	Resources cannot be deleted from meta_resource.
207/22/105295	An error occurred during the resource addition. Although the resource group was created, the resource was not added.
207/22/105303	The specified resource group does not exist in the configuration.
207/22/105311	You cannot delete the resource group that has been assigned to a user group.
207/22/105315	You cannot create a resource group because an unregistered resource group has been assigned to the user group.
207/22/106039	An error occurred.
207/22/106109	The setting process has not been executed because there is no error in this setting, but an error in another setting.
207/22/107001	The processing cannot continue due to an internal logic contradiction.
207/22/107002	The processing cannot continue due to an internal logic contradiction.
207/22/107003	The processing cannot continue due to an internal logic contradiction.
207/22/107004	The processing cannot continue due to an internal logic contradiction.
207/22/107005	The processing cannot continue due to an internal logic contradiction.
207/22/205059	The selected LDEV cannot be deleted because it belongs to a virtual storage machine other than that of meta_resource and a virtual LDEV ID is defined to it.
207/22/205061	The selected host group or iSCSI target cannot be deleted because it belongs to a virtual storage machine other than that of meta_resource and an LUN path is set to it.
207/22/205062	There are no resources that can be added.
207/22/205063	The selected LDEV cannot be deleted because it belongs to a virtual storage machine other than that of meta_resource and a virtual LDEV ID is defined to it.
207/22/205064	The selected LDEV cannot be deleted because it belongs to a virtual storage machine other than that of meta_resource and an LUN path is set to it.
207/22/205066	The resource groups that belong to different virtual storage machines cannot be deleted at the same time.
207/22/205067	The resource groups that belong to different virtual storage machines cannot be deleted at the same time.
207/22/205097	The operation cannot be performed because a virtual LDEV ID is set on the selected LDEV.
207/22/205098	The operation cannot be performed because a virtual LDEV ID is set on the selected LDEV.
207/22/205099	The operation cannot be performed because the virtual attribute of the selected LDEV is HA Reserved.
207/22/205100	The operation cannot be performed because the virtual attribute of the selected LDEV is HA Reserved.
207/22/205101	The operation cannot be performed because the virtual attribute of the selected LDEV is HA Reserved.
207/22/205102	The operation cannot be performed because the virtual attribute of the selected LDEV is not HA Reserved.
207/22/205103	The operation cannot be performed because the virtual attribute of the selected LDEV is not HA Reserved.
207/22/205104	The operation cannot be performed because the selected LDEV is used by Data Migration.
207/22/205105	The operation cannot be performed because the selected LDEV is used by Data Migration.
207/22/205106	The operation cannot be performed because the selected LDEV is used by Data Migration.
207/22/205107	This function is not available. Resource Partition is required.
207/22/205109	The operation cannot be performed because the selected LDEV is used as an intermediate volume.
207/22/205110	The operation cannot be performed because a LUN path is set to the selected LDEV.
207/22/205111	The operation cannot be performed because the selected LDEV is used as a journal volume.
207/22/205112	The operation cannot be performed because the selected LDEV is used as a quorum disk.
207/22/205113	The operation cannot be performed for the combination of selected LDEVs.
207/22/205120	There are ({0}) LDEVs on which a virtual LDEV ID cannot be set.
207/22/205168	The operation cannot be performed because the selected resource group is "NAS_Platform_System_RSG" with resource group ID 1023.
207/22/205169	"NAS_Platform_System_RSG" with resource group ID 1023 can be operated only by the service engineer.
207/22/205170	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with resource group ID 1023.
207/22/205171	The operation cannot be performed because the selected resource group is "NAS_Platform_System_RSG" with resource group ID 1023.
207/22/205172	"NAS_Platform_System_RSG" with resource group ID 1023 can be operated only by the service engineer.
207/22/205173	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with resource group ID 1023.
207/22/205174	"NAS_Platform_System_RSG" with resource group ID 1023 can be operated only by the service engineer.
207/22/205175	The operation cannot be performed, because the following LDEVs do not belong to the same resource group:\\n- The pool volumes of a pool for which the deduplication setting is enabled\\n- A deduplication system data volume that is associated with a pool for which the deduplication setting is enabled
208/25/107001	An internal logic error occurred.
208/25/107002	An internal logic error occurred.
208/25/107003	An internal logic error occurred.
208/25/107004	The specified command is invalid.
208/25/107005	The user session is not effective.
208/25/107006	Remote Web Console is busy.
208/25/107007	An internal logic error occurred.
208/25/107008	The specified command is invalid.
208/25/107009	Failed to download the specified file.
209/21/105001	No table rows are selected.
209/21/105009	The name of the new snapshot group is identical to one of the existing snapshot groups.
209/21/109211	The CLPRs of the primary and secondary volumes are different. Do you want to continue this operation?
209/21/109212	When you return to the top window, the latest status may not be displayed.
209/21/109213	Some of the specified pairs do not exist in the configuration. The window only displays the existing pairs.
209/21/205001	The password is invalid.
209/21/205002	No LDEVs are selected.
209/21/205003	No snapshot groups are selected.
209/21/205004	Two or more snapshot groups are selected.
209/21/209008	Are you sure you want to initialize all of the Business Copy, Auto LUN, and Fast Snap pairs?
209/21/209009	An attempt was made to delete a pair for which cloning is being performed. If you continue the processing to delete this pair, the integrity of the data on the secondary volume cannot be guaranteed. Do you want to continue?
209/22/105223	No table row, or two or more table rows are selected.
209/22/105225	No table rows are selected.
209/22/105442	This functionality is not available because there is no Business Copy program product installed.
209/22/105472	The form of Snapshot Group is wrong.
209/22/105474	This functionality is not available because there is no Thin Provisioning or Fast Snap program product installed.
209/22/105475	The name of the new snapshot group is identical to one of the existing snapshot groups.
209/22/105488	The specified number of pairs exceeds the maximum that can be operated at a time.
209/22/105490	When a pair volume is set as a secondary volume, multiple rows cannot be set at the same time.
209/22/106113	The operation cannot be done because there is no volume available for pair creation.
209/22/106114	The operation cannot be performed because the selected pairs have different copy types. 
209/22/106116	A pool is not selected for the selected LDEV.
209/22/106117	The configuration information may have been changed.
209/22/106118	The input value is incorrect.
209/22/106119	There is no primary volume that can be used to create a pair.
209/22/106120	The Mirror Unit of a pair that is already created cannot be changed.
209/22/106121	No more pairs can be created because the number of created pairs has reached the maximum.
209/22/106123	The setting cannot be done because too many LDEVs are selected.
209/22/106124	The setting cannot be done because the number of pairs shown under the selected row is few at the [Selected Pairs] table.
209/22/106126	No LDEV is added to the [Selected LDEVs] table.
209/22/106127	The number of available secondary volumes is not enough for the number of selected primary volumes. 
209/22/106128	The setting cannot be done because the number of selected LDEVs exceeds the number that can be set. 
209/22/106129	The selected number of rows does not match between [Available LDEVs] table and [Selected Pairs] table.
209/22/106130	The capacity of the selected LDEV does not match with that of selected pair.
209/22/106132	The pair cannot be set because the secondary volume is already set to the selected pair.
209/22/106133	The selected pair cannot be edited because the L2 pair is already set to the selected pair.
209/22/106134	The selected pair cannot be edited  because the Mirror Unit is already fixed.
209/22/106135	A pair, whose setting is not completed, remains in the [Selected Pairs] table. 
209/22/106136	The selected volume cannot be displayed because the setting is not yet completed.
209/22/106137	The selected LDEV can not be set because the L2 configuration of pair is already fixed.
209/22/106141	The operation cannot be performed because the status of the selected pair is incorrect.
209/22/106142	The Fast Snap pair cannot be suspended.
209/22/106143	The operation cannot be performed because the selected pairs have different copy types. 
209/22/106144	The specified pair cannot be used because the user has no permission to access a resource group to which a primary volume of the specified pair belongs.
209/22/106147	The operation cannot be performed because the status of the selected pair is incorrect.
209/22/106151	The pool volume of the selected Fast Snap pair belongs to a resource group that you do not have permission to access. 
209/22/106154	No more pairs can be created because the number of created pairs has reached the maximum.
209/22/106155	The operation cannot be done because the status of L2 pair in the selected pair is incorrect.
209/22/106156	The operation cannot be done because the status of L1 pair in the selected pair is incorrect.
209/22/106157	The operation cannot be done because the status of a pair that shares a primary volume and is within the selected pairs is incorrect.
209/22/106158	The operation cannot be done because the status of a pair within the selected pairs and in a cascade configuration is incorrect.
209/22/106159	The setting cannot be done because the number of pairs to be created exceeds the maximum.
209/22/106160	Multiple mirror units in one pair configuration cannot be edited at a time.
209/22/106166	No more snapshot groups can be registered because the number of snapshot groups will exceed the maximum.
209/22/106167	A pair cannot be added to the specified snapshot group because the number of pairs in one snapshot group will exceed the maximum.
209/22/106170	The selected consistency group is not in the reserved status.
209/22/106534	The specified pair does not exist in the configuration.
209/22/107001	The processing cannot continue due to an internal logic contradiction.
209/22/107002	The processing cannot continue due to an internal logic contradiction.
209/22/107003	The processing cannot continue due to an internal logic contradiction.
209/22/107004	The processing cannot continue due to an internal logic contradiction.
209/22/107005	The processing cannot continue due to an internal logic contradiction.
209/22/109026	The deleted items cannot be restored. To retry the operation, select the primary volume again in the Select Primary Volumes window. Are you sure you want to delete the selected rows?
209/22/205022	The Window cannot be displayed because the selected pairs configuration has been changed.
209/22/205023	The password is invalid.
209/22/205082	No LDEVs are added in the [Selected Primary Volumes] table.
209/22/205083	The snapshot data cannot be added to and under the root volume, because the number of snapshot data items exceeds the maximum.
209/22/205084	Characters that are not numeric are entered into Number of Snapshot Data per Primary Volume.
209/22/205085	The value entered into Number of Snapshot Data per Primary Volume is outside the specified setting range.
209/22/205087	It is required to enter an initial number if multiple snapshot groups are created.
209/22/205088	If the number of digits of a snapshot group name increases due to the combination of values specified for Initial Number and Number of Snapshot Data per Primary Volume, the snapshot group name cannot be assigned. If the same snapshot group name is already assigned to a different snapshot group, the next snapshot group name in order is assigned.
209/22/205090	Multiple snapshot groups are selected.
209/22/205092	No LDEVs are assigned to the secondary volume.
209/22/205093	Zero (0) cannot be specified for Number of Snapshot Groups.
209/22/205121	33 or more primary volumes are selected.
209/22/205132	The secondary volume of the selected pair cannot be removed because it does not exist.
209/22/205137	If the number of digits of a snapshot group name increases due to the combination of values specified for Initial Number and the number of primary volumes selected in the Available Primary Volumes table, the snapshot group name cannot be assigned. If the same snapshot group name is already assigned to a different snapshot group, the next snapshot group name in order is assigned.
209/22/205138	If the number of digits of a snapshot group name increases, the snapshot group name cannot be assigned. If the same snapshot group name is already assigned to a different snapshot group, the next snapshot group name in order is assigned.
209/22/205152	The selected pairs cannot be removed because they contain at least one pair whose secondary volume does not exist.
209/22/205159	The operation cannot be performed, because the total number of Fast Snap pairs under the selected root volume exceeds 32,768.
209/22/205160	The operation cannot be performed because the total number of Fast Snap pairs in the selected snapshot group exceeds 32,768.
209/22/205161	The operation cannot be performed, because the total number of Fast Snap pairs under the selected root volume exceeds 32,768.
209/22/205162	The operation cannot be performed because the total number of Fast Snap pairs in the selected snapshot group exceeds 32,768.
209/22/205186	Snapshot group names cannot be allocated to all specified snapshot groups because the number of characters for snapshot group names that are automatically generated from the characters entered in Prefix and Initial Number exceeds the maximum that can be used for a snapshot group name.
209/22/206121	The pool volumes registered in the selected pool belong to a resource group that you do not have permission to access.
209/22/206162	There is no available pool.
209/22/206163	Pairs cannot be created due to one of the following reasons:\\n- There is no LDEV usable by Fast Snap pairs.\\n- The number of pairs created under the selected root volumes would exceed the maximum.\\n- The number of pairs created under the root volumes of the selected pairs would exceed the maximum.
209/22/206164	There is no available snapshot group.
209/22/206165	There is no pair to which a secondary volume can be assigned.
209/22/206167	At least one pair has a secondary volume assigned.
209/22/206168	There is no LDEV that can be assigned to a secondary volume.
209/22/206169	The selected LDEV is not a secondary volume of a Business Copy pair.
209/22/206296	The operation cannot be performed because the T10 PI settings of the specified secondary volumes differ from those of the primary volumes.
209/22/206298	One or more pairs with the clone attribute cannot be created, because the cascade attribute of one or more of the selected LDEVs are disabled.
209/22/206299	One or more LDEVs cannot be added, because the setting for the cascade attribute of at least one of the selected LDEVs differs from that of the cascade attribute of LDEVs in Available Primary Volumes. A pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled cannot both exist under the root volume.
209/22/206300	The selected LDEVs cannot be used to create pairs because of one of the following reasons:\\n- There are no LDEVs that can be used as the secondary volumes of pairs with the clone attribute.\\n- There are not enough LDEVs that can be used as the secondary volumes of pairs with the clone attribute. An LDEV that can be used as the secondary volume of a clone attribute pair whose primary volume is one of the LDEVs that have been added to the Selected Primary Volumes table is also selected as the primary volume of a different pair.
209/22/206301	The pair cannot be created, because the pair type of the pair to be created differs from the pair type of another pair in the selected snapshot group.\\nA snapshot group cannot contain both a pair with the snapshot attribute and a pair with the clone attribute.
209/22/206302	One or more pairs with the snapshot attribute set and the cascade attribute disabled cannot be created, because no path is defined for the selected LDEVs.
209/22/206303	One or more pairs with the clone attribute cannot be created, because three such pairs exist in the layers from the selected primary volumes to the root volume in the highest layer.
209/22/206304	No secondary volume is assigned for a pair with the clone attribute.
209/22/206305	The operation cannot be performed, because there are pairs in multiple layers under one or more of the selected root volumes.
209/22/206306	The operation cannot be performed, because the selected pairs include both a pair with the snapshot attribute and a pair with the clone attribute.
209/22/206307	The operation cannot be performed, because the selected pairs include both a pair with the snapshot attribute and a pair with the clone attribute.
209/22/206308	The operation cannot be performed, because a pair that is being restored exists in the same layer as one or more of the selected pairs.
209/22/206309	The operation cannot be performed, because a pair that is being restored exists in the same layer as one or more of the selected pairs.
209/22/206310	The operation cannot be performed, because the selected pairs include one or more pairs with the clone attribute.
209/22/206311	The operation cannot be performed, because the selected pairs include one or more pairs with the clone attribute.
209/22/206312	The selected pairs cannot be resynchronized, because one or more pairs whose status is not PAIR exist in layers lower than the layers of the selected pairs.
209/22/206313	The selected pairs cannot be resynchronized, because one or more pairs whose status is not PAIR exist in layers lower than the layers of the selected pairs.
209/22/206314	The operation cannot be performed, because the snapshot group contains both a pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled.
209/22/206315	The operation cannot be performed, because the selected pairs contain both a pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled.
209/22/206316	The operation cannot be performed, because at least one Fast Snap pair is using the secondary volume of the selected pair as its primary volume.
209/22/206317	The operation cannot be performed, because at least one Fast Snap pair is using the secondary volume of the selected pair as its primary volume.
209/22/206318	LDEVs for which the cascade attribute is enabled are selected in Available Primary Volumes, but Disable is selected for Cascade.
209/22/206319	The operation cannot be performed, because there are pairs in multiple layers under one or more of the selected root volumes.
209/22/206320	One or more pairs cannot be split, because a Fast Snap pair that uses the primary volume of the selected pairs as the secondary volume is not in the PSUS or PSUS(SP) status.
209/22/206321	One or more pairs cannot be split, because a Fast Snap pair that uses the primary volume of the selected pairs as the secondary volume is not in the PSUS or PSUS(SP) status.
209/22/206324	The operation cannot be performed, because a Business Copy pair that uses the primary volume of the selected pair as the primary volume is not in a valid status.
209/22/206325	The operation cannot be performed, because a Business Copy pair that uses the primary volume of the selected pair as the primary volume is not in a valid status.
209/22/206326	The operation cannot be performed, because a Business Copy pair that uses the primary volume of the selected pair as the secondary volume is not in a valid status.
209/22/206327	The operation cannot be performed, because a Business Copy pair that uses the primary volume of the selected pair as the secondary volume is not in a valid status.
209/22/206328	The operation cannot be performed, because the selected pairs contain both a pair for which the cascade attribute is enabled and a pair for which the cascade attribute is disabled.
209/22/206329	The specified pair cannot be used because the user has no permission to access a resource group to which a primary volume of the specified pair belongs.
209/22/206333	A necessary program product is not installed, or insufficient permissions to execute editorial operation.
209/22/206508	The specified pool does not exist in the configuration.
209/22/206525	One or more selected root volumes do not exist in the configuration.
209/22/206530	The process cannot be continued, because attributes is Clone .
209/22/206532	The process cannot be continued, because there is other than Leaf pairs.
209/22/206533	The process cannot be continued, because attributes is Clone.
209/22/206537	The process cannot be continued, because attributes is Clone .
209/22/206538	The process cannot be continued, because there is other than Leaf pairs.
209/22/206539	The process cannot be continued, because attributes is Clone.
209/22/207007	Pair information cannot be acquired.
209/22/209005	There is no LDEV that can be assigned to a secondary volume.
209/22/209006	The specified snapshot group name is already used. The next snapshot group name in order will be assigned to the snapshot group.
209/22/209008	The data in the selected LDEV will not be recognized from the host. It might be required to unmount and then mount the LDEV from the host to recognize the data again. Do you want to continue this operation?
210/21/105001	No table rows are selected.
210/21/105003	No table row, or two or more table rows are selected.
210/21/105007	No table row is selected.
210/21/109001	Are you sure you want to remove the selected row(s)?
210/21/209001	Pairs whose Initial Copy Type is "None" are included. Initial Copy is not performed for the pairs.
210/21/209002	Some of the specified pairs do not exist in the configuration. The window only displays the existing pairs.
210/21/209003	When you return to the top window, the latest status may not be displayed.
210/21/209004	Through this operation, the volumes on this storage system will change to the SMPL status forcibly, but the statuses of the volumes on the other storage system will not change. Do you want to continue this operation?
210/21/209005	Copying might not be complete because the specified pair is in the PSUS or PSUE status. Do you want to continue this operation?
210/21/209008	Journal option information will be initialized if all of the assigned journal volumes are released.
210/21/209010	Copying might not be complete because the specified pair is suspended. Do you want to continue this operation?
210/21/209011	Copying might not be complete for pairs in the Suspend status, and the selected pairs will be deleted, depending on their status, with their settings changed as follows.\\n- For the pairs in the Suspend status and whose I/O mode is BLOCK, the Delete Mode setting will change to Force and the Volume Access setting will change to Disabled.\\n- For the pairs in the Copy status, the Delete Mode setting will change to Force and the Volume Access setting for the primary volume and the secondary volume will change to Enable and Disable respectively.\\n- For the pairs not in the Suspend or Copy status, the Delete Mode setting will change to Force and the Volume Access setting will change to Disabled.\\nDo you want to continue this operation to delete the pairs?
210/21/209028	This operation will forcibly delete the selected HA pairs. The volumes on the local storage system will be forcibly changed to the SMPL status, but the statuses of the volumes on the remote storage system will not be changed. The settings for the pairs in the COPY status will be changed to the following, and then the pairs will be deleted:\\n- Volume Access for the primary volume is enabled.\\n- Volume Access for the secondary volume is disabled.\\nYou can forcibly delete a pair only when the I/O mode of both the primary and secondary volumes is Block.If you want to forcibly delete a pair when the I/O mode is not Block, contact the HSSC.\\nFor details, see the online manual.\\nDo you want to continue this operation?
210/21/209031	The setting for remote paths will be discarded. Do you want to continue this operation?
210/22/107001	The processing cannot continue due to an internal logic contradiction.
210/22/107002	The processing cannot continue due to an internal logic contradiction.
210/22/107003	The processing cannot continue due to an internal logic contradiction.
210/22/107004	The processing cannot continue due to an internal logic contradiction.
210/22/107005	The processing cannot continue due to an internal logic contradiction.
210/22/205001	A pair cannot be created because any of the following program products is not installed:\\n- Continuous Access Synchronous\\n- Continuous Access Journal
210/22/205075	This function is not available. Continuous Access Journal or Continuous Access Synchronous is required.
210/22/205077	This function is not available. High Availability is required.
210/22/205078	A pair cannot be created because Continuous Access Synchronous is not installed.
210/22/205079	A pair cannot be created because High Availability is not installed.
210/22/205080	This function is not available. Continuous Access Synchronous is required.
210/22/205094	No more journals can be created because the number of created journals has reached the maximum.
210/22/205095	No more journals can be created because the number of registered journals has reached the maximum.
210/22/205175	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" with resource group ID 1023.
210/22/206001	The selected volume cannot be added because its CLPR is different from the CLPR of the added volume.
210/22/206002	The selected volume cannot be added because its resource group is different from the resource group of the added volume.
210/22/206004	The operation cannot be performed because the pair position of the selected pair is incorrect.
210/22/206005	The operation cannot be performed because the pair position of the selected pair is incorrect.
210/22/206006	The operation cannot be performed because the attribute of the selected mirror is incorrect.
210/22/206007	The operation cannot be performed because the attribute of the selected mirror is incorrect.
210/22/206013	The operation cannot be performed because the status of the selected pair is incorrect.
210/22/206014	The operation cannot be performed because the status of the selected pair is incorrect.
210/22/206015	The operation cannot be performed because the status of the selected mirror is incorrect.
210/22/206016	The operation cannot be performed because the status of the selected mirror is incorrect.
210/22/206017	The operation cannot be performed because the attribute of the selected journal is incorrect.
210/22/206018	The operation cannot be performed because the attribute of the selected journal is incorrect.
210/22/206020	No more remote connections can be added because the number of remote connections has reached the maximum.
210/22/206021	The operation cannot be performed because there is no local port ID available to set.
210/22/206022	Remote connections are not set.
210/22/206023	The status of the port where the LUN is set is incorrect.
210/22/206024	There is no journal.
210/22/206025	The operation cannot be done because there is no volume available for pair creation.
210/22/206026	No more pairs can be created because the number of created pairs has reached the maximum.
210/22/206027	No more pairs can be created because the number of created pairs has reached the maximum in the selected journal.
210/22/206029	No more pairs can be created because the number of registered pairs has reached the maximum in the selected CTG.
210/22/206033	Delta cannot be specified as an initial copy type in the selected journal status.
210/22/206034	Only Delta can be specified as an initial copy type in the selected journal status.
210/22/206037	The selected mirror contains pairs with a different remote storage system or a different path group ID.
210/22/206038	The operation cannot be performed because the remote storage system (RCU) of the pairs is different.
210/22/206040	No more remote path can be removed from the selected remote connection because the number of remote paths set to the remote connection is the same as the minimum number of paths.
210/22/206041	The ports that are registered to the selected remote connection belong to a resource group that you do not have permission to access.
210/22/206045	The specified volume is used by a Continuous Access Synchronous.
210/22/206046	The specified volume is used by a Continuous Access Journal.
210/22/206047	There is no volume that can be set as a journal volume.
210/22/206048	Journals cannot be created because there is no free journal ID.
210/22/206049	Volumes cannot be added to or removed from the selected journal.
210/22/206050	The operation cannot be performed because the status of the selected mirror is incorrect.
210/22/206051	Volumes cannot be removed from the selected journal and there is no volume that can be set as a journal volume.
210/22/206052	The journal volume of the selected journal belongs to a resource group that you do not have permission to access.
210/22/206055	No more remote path can be added to the selected remote connection because the number of remote paths has reached the maximum.
210/22/206057	There is no volume that can be set as a journal volume.
210/22/206058	No more remote path can be added to the specified connection because the number of remote paths has reached the maximum.
210/22/206059	No more remote path can be removed from the selected remote connection because the number of remote paths set to the remote connection is the same as the minimum number of paths.
210/22/206063	The combination of the selected parameters is not allowed.
210/22/206064	No remote command device is assigned to the selected mirror.
210/22/206065	No more pairs can be created because the number of created pairs has reached the maximum.
210/22/206067	The operation cannot be performed because the attribute of the selected mirror is incorrect.
210/22/206070	The operation cannot be performed because the selected journal has a mirror in invalid status.
210/22/206071	The operation cannot be performed because there is no remote command device to set.
210/22/206074	The operation cannot be performed because the status of the mirror in the selected journal is incorrect.
210/22/206075	The selected volumes contain volumes that cannot be removed.
210/22/206076	There is no change to the journal volume.
210/22/206077	No more volumes can be added because the number of journal volumes has reached the maximum.
210/22/206078	The journal creation failed.
210/22/206079	An error occurred during the journal creation. Although the journal was created, some journal volumes were not registered.
210/22/206080	The combination of the specified local port ID and remote port ID is already used.
210/22/206082	The operation cannot be performed because the selected remote connection already exists.
210/22/206083	The operation cannot be performed because the attribute of the selected journal is "initial".
210/22/206085	The number of specified pairs exceeds the maximum.
210/22/206115	The ports that are registered to the remote connection used by the selected pair belong to a resource group that you do not have permission to access.
210/22/206116	The ports that are registered to the remote connection used by a pair in the selected mirror belong to a resource group that you do not have permission to access.
210/22/206117	The journal volumes that are registered to the journal of the selected mirror belong to a resource group that you do not have permission to access.
210/22/206118	The pair volumes that are registered to the selected journal belong to a resource group that you do not have permission to access.
210/22/206119	The pair volumes that are registered to the journal of the selected mirror belong to a resource group that you do not have permission to access.
210/22/206120	The journal volumes that are registered to the selected journal belong to a resource group that you do not have permission to access.
210/22/206121	The pool volumes registered in the selected pool belong to a resource group that you do not have permission to access.
210/22/206122	The remote command device that is assigned to the selected mirror belongs to a resource group that you do not have permission to access.
210/22/206123	The setting process has not been executed because there is no error in this setting, but an error in another setting.
210/22/206124	The value of Blocked Path SIM Monitoring must be larger than that of Blocked Path Monitoring.
210/22/206142	No more remote paths can be removed from the selected remote connection because the number of remote paths set to the remote connection is less than the minimum number of paths.
210/22/206145	The option of the selected remote connection cannot be edited because the number of remote paths set to the remote connection is less than the minimum number of paths.
210/22/206146	No more remote paths can be removed from the selected remote connection because the number of remote paths set to the remote connection is less than the minimum number of paths.
210/22/206149	The option of the selected remote connection cannot be edited because the number of remote paths set to the remote connection is less than the minimum number of paths.
210/22/206150	The ports that are registered to the remote connection used by the selected pair belong to a resource group that you do not have permission to access.
210/22/206152	A quorum disk cannot be added because there is no free quorum disk ID.
210/22/206153	The operation cannot be performed because there is no volume available to add a quorum disk.
210/22/206154	There is no available Remote Connection.
210/22/206155	The quorum disk that is registered to the selected pair belongs to a resource group that you do not have permission to access.
210/22/206156	The specified LDEV is used by a High Availability pair.
210/22/206157	The specified volume cannot be deleted because the emulation type is not OPEN-V.
210/22/206158	The operation cannot be performed because there is no available quorum disk.
210/22/206159	The operation cannot be performed because there is no quorum disk on which the remote storage system registered as the remote connection is set.
210/22/206160	The operation cannot be performed because the combination of the status and I/O mode of the selected pair is not valid.
210/22/206161	The operation cannot be performed because the combination of the status and I/O mode of the selected pair is not valid.
210/22/206244	The operation cannot be performed because there is no pair in the selected consistency group.
210/22/206245	The operation cannot be performed because there is no pair in the selected consistency group.
210/22/206246	The operation cannot be performed because a consistency group that cannot be suspended is selected.
210/22/206247	The operation cannot be performed because a consistency group that cannot be suspended is selected.
210/22/206248	The operation cannot be performed because the consistency group that contains a pair whose volumes belong to a resource group that you do not have permission to access is selected.
210/22/206249	The operation cannot be performed because a consistency group in which a pair that cannot be suspended is registered is selected.
210/22/206252	The selected LDEVs cannot be added because the virtual storage machines of the selected LDEVs and consistency group do not match.
210/22/206253	The selected LDEVs cannot be added because the virtual storage machines of the selected LDEVs and consistency group do not match.
210/22/206254	The selected LDEVs cannot be added because the number of registered pairs in the consistency group exceeds the maximum.
210/22/206255	The operation cannot be performed because a consistency group that cannot be resynchronized is selected.
210/22/206256	The operation cannot be performed because a consistency group that cannot be resynchronized is selected.
210/22/206257	The pair cannot be resynchronized with the pair status and the I/O mode registered in the selected consistency group.
210/22/206280	The IP address and TCP port number of the registered remote path will be overwritten. Do you want to continue this operation?
210/22/206281	The performance of the remote connection might be affected because different types of ports coexist. Do you want to continue this operation?
210/22/206282	The specified remote storage system does not support iSCSI ports.
210/22/206286	No more pairs can be created because the number of created pairs has reached the maximum in the selected mirror.
210/22/206287	The resync operation cannot be performed because the selected pairs have the same primary volume or the mirrors of the specified pairs have the same primary volume.
210/22/206288	The resync operation cannot be performed because the selected mirrors contain pairs that have the same primary volume.
210/22/206289	The selected LDEVs cannot be added because the journal ID or the mirror ID does not match.
210/22/206291	The selected paired LDEVs cannot be added because the mirror ID of the LDEVs is the same as the mirror ID in Mirror Selection.
210/22/206292	A delta resync pair is being created in the multi-target configuration. If the operation is properly complete, the volumes specified as primary volumes change to secondary volumes and the journals specified as master journals change to restore journals.
210/22/206293	The operation cannot be performed because remote command devices are assigned to the selected mirrors.
210/22/206294	The current DKCMAIN firmware version does not support the setting for Read Response Guaranteed Time When Quorum Disk Blocked.
210/22/206501	The selected remote connection does not exist in the configuration.
210/22/206502	The specified pair does not exist in the configuration.
210/22/206503	The specified mirror does not exist in the configuration.
210/22/206504	The specified journal does not exist in the configuration.
210/22/206505	The LDEV assigned to the selected journal does not exist in the configuration.
210/22/206506	The specified LDEV does not exist in the configuration.
210/22/206507	The specified journal does not exist in the configuration.
210/22/206508	The specified pool does not exist in the configuration.
210/22/206511	The specified quorum disk does not exist in the configuration.
211/22/207001	The processing cannot continue due to an internal logic contradiction.
213/22/205097	Parity groups cannot be added because one or more of the specified items are not valid.
213/22/205098	Parity groups cannot be combined because the number of the specified parity groups is not valid.
213/22/205099	Parity groups cannot be added because one or more of the specified items are not valid.
213/22/205100	Parity groups cannot be combined because the selected RAID level does not support combining parity groups.
213/22/205130	The specified parity groups cannot be edited because they are for external volumes.
213/22/205131	The specified parity group cannot be deleted because it is for an external volume.
213/22/205155	The specified parity group does not exist in the configuration.
213/22/205178	The operation cannot be performed because the LDEVs that belong to the selected parity group belong to "NAS_Platform_System_RSG" with the resource group ID 1023.
213/22/205197	Compression might not work because the used rate of the pool capacity is 90% or greater.
213/22/205210	The parity group with the encryption and the capacity expansion enabled cannot be created.
213/22/206170	Parity groups cannot be added because there are not enough parity group IDs.
213/22/206171	Parity groups cannot be added because the number of drives is not enough.
213/22/206172	Parity groups cannot be combined because parity groups of different RAID levels coexist.
213/22/206173	Parity groups cannot be combined because parity groups of different drive types coexist.
213/22/206174	Parity groups cannot be combined because parity groups of different encryption settings coexist.
213/22/206175	Parity groups cannot be combined because parity groups of different copy back modes coexist.
213/22/206176	The setting cannot be changed because there are not enough parity group IDs to create the specified parity groups.
213/22/206177	The status of the selected drive is not Normal.
213/22/206178	The specified number of spare drives exceeds the maximum number of the spare drives on the storage system.
213/22/206182	The specified parity groups cannot be deleted because you do not have permission to access a resource group to which the parity group belongs.
213/22/206183	The specified parity group cannot be deleted because a LUN path is set to it.
213/22/206184	The specified parity group cannot be deleted because it contains a pool volume.
213/22/206185	The specified parity group cannot be deleted because it contains a journal volume.
213/22/206188	The specified parity group cannot be deleted because it contains a volume that is set as a remote command device.
213/22/206190	The specified parity group cannot be deleted because it contains an external volume that is mapped for the online data migration.
213/22/206191	The specified parity group cannot be deleted because you do not have permission to access a resource group to which a volume in the parity group belongs.
213/22/206193	A drive other than the spare or free drive is specified.
213/22/206194	The current storage system does not support the specified operation.
213/22/206195	Parity groups cannot be combined because the number of the specified parity groups is not valid.
213/22/206286	The specified parity groups cannot be concatenated because different capacity expansion settings coexist.
213/22/207009	An internal logic contradiction occurred.
213/22/209022	Are you sure you want to combine the parity groups?
214/40/205503	The configuration file format for SMI-S is not valid.
214/40/205504	The user ID or the password is not valid.
214/40/205505	An error occurred during the listener information acquisition.
214/40/205506	No listeners are subscribed to the provider.
214/40/205507	The artificial indication cannot be sent to some listeners.
214/40/207504	A time-out error occurred.
214/40/207505	An internal error occurred.
214/40/209501	The artificial indication has been sent to listeners.
