-2132767453	5	5	The operation cannot be performed because the total number of Thin Image pairs that \\nshare the selected primary volume exceeds 32,768.\\nVerify the number of Thin Image pairs that share the selected primary volume.
-2132678025	5	5	A pair cannot be created because of the migration attribute of the volume specified \\nas the primary volume or the secondary volume.\\nRelease the migration attribute, or specify a different volume.
-2132678024	5	5	The operation cannot be performed because of the migration attribute of the volume \\nspecified as the primary volume or the secondary volume.\\nRelease the migration attribute.
-2132678023	5	5	A pair consisting of three secondary volumes cannot be created because of the migration \\nattribute of the volume specified as the primary volume.\\nCreate a pair consisting of one or two secondary volumes, or specify a different \\nvolume for the primary volume.
-2132678022	5	5	The operation cannot be performed because of the migration attribute of the secondary \\nvolume of the specified pair.\\nRelease the migration attribute.
-2132678021	5	5	The volume specified as the primary volume is a migration volume of nondisruptive \\nmigration. The operation cannot be performed because the setting of the online data \\nmigration for the volume is not valid.\\nVerify the setting of the online data migration.
-2132678019	5	5	The command cannot be run because the volume specified as the primary volume is a \\nreserved volume of global-active device, or the status of the global-active device \\npair is not valid.\\nSpecify a different volume, or verify whether the pair status is available for this \\noperation by referring to the ShadowImage User Guide, and then retry the operation.
-2132678018	5	5	The command cannot be run because the volume specified as the secondary volume is \\na reserved volume of global-active device, or the volume is used by the global-active \\ndevice pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
-2132678017	5	5	The command cannot be run because the volume specified as the primary volume is a \\nreserved volume of global-active device, or the status of the global-active device \\npair is not valid.\\nSpecify a different volume, or verify whether the pair status is available for this \\noperation by referring to the Thin Image User Guide, and then retry the operation.
-2132677995	5	5	The command cannot be run because the volume specified as the secondary volume is \\na reserved volume of global-active device, or the volume is used by the global-active \\ndevice pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
-2132677994	5	5	The command cannot be run because the specified primary volume is not a primary volume \\nof a Thin Image pair.\\nRefresh the window, and then retry the operation.
-2132677993	5	5	The command cannot be run because the specified pair does not exist.\\nRefresh the window, and then retry the operation.
-2132677992	5	5	The command cannot be run because the specified pair cannot be identified.\\nRefresh the window, and then retry the operation.
-2132677991	5	5	The command cannot be run because the specified pair has a secondary volume.\\nRefresh the window, and then retry the operation.
-2132677990	5	5	The command cannot be run because the specified pair has no secondary volume.\\nRefresh the window, and then retry the operation.
-2132677989	5	5	The command cannot be run because the specified pair has no secondary volume.\\nRefresh the window, and then retry the operation.
-2132677988	5	5	The operation cannot be performed because the DKCMAIN firmware version and the Storage \\nNavigator software version do not match.\\nVerify the DKCMAIN firmware version and the Storage Navigator software version.
-2132677987	5	5	The command cannot be run because the specified pair has a secondary volume.\\nRefresh the window, and then retry the operation.
-2132677986	1	5	The processing cannot continue due to an internal logic contradiction.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
-2132677964	1	5	The processing cannot continue due to an internal logic contradiction.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
-2132677957	5	5	The operation cannot be performed because the specified primary volume is being migrated \\nby Volume Migration.\\nWait until the migration is complete, and then retry the operation.
-2132677955	5	5	The operation cannot be performed because the specified secondary volume is being \\nmigrated by Volume Migration.\\nWait until the migration is complete, and then retry the operation.
-2132677931	5	0	The operation cannot be performed because the specified primary volume is an external \\nvolume with the data direct mapping enabled or a volume that belongs to a parity \\ngroup with the accelerated compression enabled.\\nVerify the specified volume.
-2132677930	5	0	The operation cannot be performed because the specified secondary volume is an external \\nvolume with the data direct mapping enabled or a volume that belongs to a parity \\ngroup with the accelerated compression enabled.\\nVerify the specified volume.
-2132677928	5	0	The pair operation cannot be performed because the T10 PI setting does not match \\nbetween the specified primary volume and secondary volume.\\nSpecify a primary volume and a secondary volume with the same T10 PI setting, and \\nthen retry the operation.
-2132677927	5	5	A pair cannot be created, because the number of cascade pair layers exceeds 64.\\nVerify the settings.
-2132677926	5	5	A pair with the clone attribute cannot be created, because three such pairs exist \\nin the layers from the specified primary volumes to the root volume in the highest layer.\\nVerify the pair configuration.
-2132677925	5	5	A pair cannot be created, because the snapshot groups contain both pairs with the \\nsnapshot attribute and pairs with the clone attribute.\\nVerify the pairs added to the snapshot groups, and then retry the operation.
-2132677924	5	5	One or more pairs cannot be created, because a Thin Image pair that uses the specified \\nprimary volume as the secondary volume is not in the PAIR or PSUS status.\\nChange the status of the pair to PAIR or PSUS, and then retry the operation.
-2132677902	5	5	A pair cannot be created, because a pair belonging to the specified CTG exists in \\none of the layers from the specified primary volume to the root volume.\\nSpecify a different CTG, and then retry the operation.
-2132677901	5	5	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\\nVerify the specified pairs.
-2132677900	5	5	The following operations cannot be performed, because one or more Thin Image pairs \\nare using the secondary volume of the specified pair as a primary volume:\\n- Deleting the secondary volume\\n- Changing the secondary volume\\nDelete the Thin Image pairs that use the secondary volume of the specified pair as \\na primary volume, and then retry the operation.
-2132677899	5	5	One or more pairs cannot be split, because a Thin Image pair that uses the primary \\nvolume of the specified pairs as the secondary volume is not in the PSUS status.\\nSplit the Thin Image pair that uses the primary volume of the specified pairs as \\nthe secondary volume, and then retry the operation.
-2132677898	5	5	The specified pairs with the clone attribute cannot be split, because the configuration \\nof those pairs does not match the actual configuration.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
-2132677897	5	5	The pair cannot be deleted, because one or more Thin Image pairs are using the secondary \\nvolume of the specified pair as a primary volume.\\nDelete the Thin Image pairs that use the secondary volume of the specified pair as \\na primary volume, and then retry the operation.
-2132677896	5	5	The selected pairs cannot be resynchronized or restored, because one or more pairs \\nwhose status is not PAIR exist in layers lower than the layers of the selected pairs.\\nChange the statuses of all pairs in layers lower than the layers of the selected \\npairs to PAIR, and then retry the operation.
-2132677895	5	5	The command cannot be run, because the shared memory needed to perform operations \\non Thin Image cascade pairs or pairs with the clone attribute is not installed.\\nInstall the shared memory.
-2132677894	5	5	The current DKCMAIN firmware version does not support the specified operation.\\nVerify the DKCMAIN firmware version. The DKCMAIN firmware version might not match \\nthe SVP software version. Verify whether the DKCMAIN firmware version matches the \\nSVP software version.
-2132677893	5	5	Pairs cannot be created, because the secondary volumes are not Dynamic Provisioning volumes.\\nSpecify Dynamic Provisioning volumes for the secondary volumes.
-2132677871	5	5	An internal error occurred.\\nContact the HSSC.
-2132677870	5	5	Pairs with the clone attribute cannot be created, because no secondary volumes are \\nspecified.\\nSpecify secondary volumes.
-2132677866	5	5	The command cannot be run, because zero pages are being reclaimed on the specified \\nsecondary volumes.\\nWait until the processing to reclaim zero pages is complete, and then retry the operation.
-2132677865	5	5	The command cannot be run, because the capacities of the specified secondary volumes \\nare being expanded.\\nWait until the processing to expand the capacities of the volumes is complete, and \\nthen retry the operation.
-2132677864	5	5	The command cannot be run, because the statuses of the specified secondary volumes \\nare being changed.\\nWait until the processing to change the statuses is complete, and then retry the \\noperation.
-2132677863	5	5	A pair cannot be created, because the cascade attribute setting differs from the \\nsettings of the pairs under the root volume. A pair for which the cascade attribute \\nis enabled and a pair for which the cascade attribute is disabled cannot exist under \\nthe root volume.\\nVerify the cascade attribute settings of the pairs under the root volume, and then \\nretry the operation.
-2132677862	5	5	Dynamic Provisioning volumes with the SLU attribute cannot be assigned as secondary volumes.\\nSpecify Dynamic Provisioning volumes without the SLU attribute.
-2132677189	5	5	The command cannot be run, because the specified primary volumes are being deleted.\\nSpecify different LDEVs as the primary volumes.
-2132677188	5	5	The command cannot be run, because the specified secondary volumes are being deleted.\\nSpecify different LDEVs as the secondary volumes.
-2132677187	5	5	The operation cannot be performed, because the specified S-VOL is a V-VOL for Thin Image.\\nSelect a different volume.
-2132675012	5	5	Pairs cannot be created, because deduplication system data volumes are specified \\nas the primary volumes.\\nSelect different LDEVs.
-2132675011	5	5	Pairs cannot be created, because deduplication system data volumes are specified \\nas the secondary volumes.\\nSelect different LDEVs.
-2132674981	5	5	The Quick Restore operation cannot be performed, because the capacity saving status \\nof the primary volumes of the selected pairs is not Disabled.\\nPerform the Reverse Copy operation to restore the selected pairs.
-2132674980	5	5	The Quick Restore operation cannot be performed, because the capacity saving status \\nof the secondary volumes of the selected pairs is not Disabled.\\nPerform the Reverse Copy operation to restore the selected pairs.
-2132674117	5	5	The specified operation cannot be performed, because the pool capacity exceeds the \\nsubscription limit of the pool.\\nVerify the subscription limit of the pool, and then retry the operation.
-2132673215	5	0	The operation cannot be performed because the selected secondary volume is used as \\na primary volume of a TrueCopy pair or a Universal Replicator pair.\\nSelect a different volume, and then retry the operation.
-2129900794	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\nis bound to an LDEV with the ALU attribute.\\nUnbind the specified LDEV with the SLU attribute from the LDEV with the ALU attribute, \\nand then retry the operation.
-2107110749	1	2	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
-2107110715	5	3	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-2107109661	5	3	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-2107080957	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2107021347	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2107021090	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2107016542	5	3	The storage system is in internal process, or some other user is changing the configuration.\\nPlease wait for a while, and then select [Refresh].
-2106991587	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106991554	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106991522	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-2106991488	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106991463	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-2106991432	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106991431	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106986688	5	3	The Storage Navigator is busy.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-2106961610	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106960803	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-2106932004	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-2106931044	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-2104073690	5	5	Two or more commands which were not able to be processed were demanded.\\nVerify the settings, and then retry the operation.
-2104043965	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-2104043899	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-2104013990	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-2104013989	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-2071154899	5	6	Invalid character is included in the e-mail addresses or the server addresses.\\nDelete the characters that cannot be used.
-2071154898	5	6	The number of characters specified in an e-mail address or a server address exceeds \\n255 characters.\\nEnter with 1 to 255 characters.
-2071154897	5	6	An attribute of the registered destination of messages is invalid.\\nCheck the setting(s).
-2071154896	5	6	The SMTP authentication is enabled, but Account or Password is not specified.\\nEnter a correct value.
-2071154895	5	6	The same e-mail addresses are specified. \\nExclude the duplicated setting, then retry the operation.
-2071124242	5	5	There is no e-mail address information file.\\nRetry the operation. If this problem persists, contact the HSSC.
-2071124241	5	5	The contents of the e-mail address information file are invalid.\\nRetry the operation. If this problem persists, contact the HSSC.
-2071124240	5	5	A failure occurred while communicating with the SMTP server.\\nRetry the operation. If this problem persists, contact the HSSC.
-2064711931	5	2	An error occurred in the storage system. The configuration may be inconsistent. \\nClick [Refresh All] on the [File] menu, then refresh the configuration.
-2063875962	5	6	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-2063852061	1	3	The login could not be performed because a function failed to start during Storage \\nNavigator initialization.\\nCall the HSSC.
-2062924659	5	5	The resource group definition is being changed.\\nWait, and then retry the operation.
-2032223620	5	5	The number of characters for the password is not valid.\\nEnter the password using from 6 to 255 characters.
-2032223616	5	5	The serial number of the encryption key does not match the serial number of this \\nstorage system because the key is restored by using the backup file created by a \\ndifferent storage system.\\nUse the correct encryption key.
-2003593509	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
-1987001676	5	5	A communication time-out error occurred between the local storage system and the \\nremote storage system.\\nWait for a while, and then retry the operation.
-1986075212	1	0	The operation failed, because there was an error in the specified parameter.\\nIf this problem persists, contact the HSSC.
-1986075210	5	5	The specified volume has already been set to the quorum disk. Or, the specified quorum \\ndisk ID has already registered.\\nSpecify a different volume or quorum disk ID.
-1986075055	5	5	The operation cannot be performed because the specified volume is a pool volume.\\nSelect a different volume, or release the pool volume setting.
-1986075033	1	5	The operation failed, because the specified volume was used for Volume Migration.\\nSelect another volume, or release the Volume Migration setting.
-1986075031	5	5	The operation cannot be performed because the quorum disk is not accessible.\\nIf this problem persists, contact the HSSC. If this is a Remove Quorum Disks operation, \\nperform LDEV formatting on the specified quorum disk.
-1986075024	1	0	The operation failed, because the quorum disk was blocked.\\nRestore the specified quorum disk.
-1986075001	5	5	The operation cannot be performed because the specified quorum disk ID does not match \\nthe one set on the remote storage system.\\nSpecify the same quorum disk ID as the one set on the remote storage system.
-1985248785	5	0	The selected LDEV or an LDEV in the selected consistency group belongs to a resource \\ngroup that you do not have permission to access.\\nAsk the administrator for resource assignment.
-1985248751	5	5	The operation cannot be performed because the port for the remote path on the local \\nstorage system belongs to a resource group that you do not have permission to access.\\nAsk the administrator for resource assignment.
-1985159447	5	5	The operation cannot be performed because the current DKCMAIN firmware version does \\nnot support the capacity of the specified primary volume.\\nVerify the DKCMAIN firmware version of the local storage system.
-1985159446	5	5	The operation cannot be performed because the current DKCMAIN firmware version does \\nnot support the capacity of the specified secondary volume.\\nVerify the DKCMAIN firmware version of the remote storage system.
-1985158417	5	5	The operation cannot be performed because the specified volume is in the online data \\nmigration process.\\nSpecify a volume other than the one in the online data migration process.
-1985158416	5	5	The operation cannot be performed because the specified primary volume is an external \\nvolume that is mapped for the online data migration and its cache mode is set to Through.\\nPerform either of the following operations:\\n- Specify a volume other than the external volume that is mapped for the online data \\nmigration.\\n- Change the cache mode of the volume specified as the primary volume.
-1985158394	5	5	The operation cannot be performed because the specified secondary volume is an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration.
-1976658968	5	5	LDEVs cannot be created because there is not enough free area in the pool.\\nIncrease the free area of the pool.
-1948152984	5	5	An LDEV, for which Full Allocation is enabled, cannot be created with the specified \\nemulation type.\\nSpecify an emulation type with which Full Allocation can be enabled, or disable Full \\nAllocation.
-1948152983	5	5	The specified pool is not a Dynamic Provisioning pool.\\nVerify the type of the specified pool.
-1948093402	5	5	An LDEV, for which Full Allocation is enabled, cannot be created because the specified \\npool is in shrinking operation.\\nWait until the shrinking operation is complete, and then retry the operation.
-1947944447	5	5	The operation cannot be performed because the capacity of the specified LDEV is different \\nfrom that of the selected external volume.\\nSpecify the same capacity as that of the external volume for the LDEV.
-1947944446	5	5	Data Direct Mapping cannot be enabled because the specified emulation type is not OPEN-V.\\nSpecify a volume whose emulation type is OPEN-V.
-1947944445	5	5	The specified LDEV ID of the pool volume is outside the setting range.\\nVerify the LDEV ID of the pool volume, and then retry the operation.
-1947944444	5	5	The operation cannot be performed because the specified pool volume is not associated \\nwith a pool with the Data Direct Mapped attribute.\\nSpecify a volume that is associated with a pool whose attribute is Data Direct Mapped.
-1947944443	5	5	The operation cannot be performed because the specified pool volume is associated \\nwith a different Dynamic Provisioning volume.\\nSpecify a different pool volume, or delete the Dynamic Provisioning volume, and then \\nretry the operation.
-1947944440	5	5	No volumes can be created because the Data Direct Mapped attribute differs between \\nthe specified volume and pool.\\nVerify the setting.
-1947944439	5	5	Full Allocation and Data Direct Mapping cannot be enabled at the same time.\\nVerify the setting.
-1947944417	5	5	T10 PI cannot be enabled because the specified emulation type is not OPEN-V.\\nTo enable T10 PI, specify LDEVs whose emulation type is OPEN-V.
-1947944416	5	5	No DP-VOLs can be created because the specified pool volumes are blocked.\\nRestore the specified pool volumes, and then retry the operation.
-1947944415	5	5	The operation cannot be performed because the specified volumes are associated with \\na pool volume whose Data Direct Mapping is enabled and an external volume used as \\nthe pool volume is not disconnected.\\nBlock the specified volumes, disconnect the external volume used as the pool volume \\nassociated with the specified volumes on the Disconnect External Storage Systems \\nwindow or the Disconnect External Volumes window, and then retry the operation.
-1947944414	5	5	An LDEV with the full allocation enabled cannot be created because the selected pool \\ncontains pool volumes that belong to parity groups with the accelerated compression enabled.\\nSelect a pool without pool volumes that belong to parity groups with the accelerated \\ncompression enabled, or disable the full allocation.
-1947943448	1	5	The specified function is not supported.\\nUpdate the DKCMAIN microcode to a version that supports the specified function.
-1947941529	5	5	The operation cannot be performed, because deduplication system data volumes have \\nalready been allocated to the specified pools.\\nRelease the allocations of the deduplication system data volumes to the specified \\npools, and then retry the operation.
-1947941528	5	5	Deduplication system data volumes are not allocated to the specified pools.\\nClick the refresh button to display the latest information on the window, and then \\nverify the settings of the specified pools.
-1947941526	5	5	The operation cannot be performed, because DP-VOLs whose capacity saving setting \\nis Deduplication and Compression are contained in the specified pools.\\nChange the capacity saving setting to Disabled or Compression for all DP-VOLs in \\nthe specified pools, and then retry the operation.
-1947941525	5	5	The deduplication system data volume cannot be unassigned, because the deduplication \\nrate (%) of the specified pool is greater than 0.\\nPerform the following actions, and then retry the operation:\\n- If the data of the DP-VOLs associated with the pool is not necessary or has been \\nbacked up, format the deduplication system data volume.\\n- ?In other cases, change the capacity saving setting to Disabled or Compression \\nfor the DP-VOLs whose setting is currently Deduplication and Compression.
-1947941502	1	5	The operation cannot be performed because there is not enough installed shared memory.\\nAdd more shared memory.
-1947941501	5	5	The program product required for using the dedupe and compression function is not \\ninstalled.\\nInstall the required program product.
-1947941472	1	5	An error occurred during communication with the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1947941471	5	5	The emulation type of the specified volume cannot be used.\\nVerify the emulation type of the specified volume.
-1947941470	5	5	No deduplication system data volume is allocated to the specified pool.\\nClick the refresh button to display the latest information on the window, and then \\nverify the pool setting.
-1947941469	5	5	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 Dynamic Provisioning volumes associated with the pool is high.\\nPerform either of the operations below, and then retry the operation. If this problem \\npersists, contact the HSSC.\\n- Restore the pool volumes to the normal status.\\n- Reduce the I/O load of the Dynamic Provisioning volumes associated with the pool.
-1947941468	5	5	The operation cannot be performed because the required number of cache management \\ndevices cannot be allocated.\\nSee the following sections in the Provisioning Guide, and reserve the required number \\nof cache management devices:\\n- Description of cache management devices\\n- Troubleshooting for cache management devices\\nIf the required number of cache management devices is already reserved, contact the HSSC.
-1947941467	5	5	The specified operation cannot be performed because there is not enough shared memory \\nfor the V-VOL management area.\\nAdd more shared memory for the V-VOL management area, and then retry the operation. \\nIf shared memory for the V-VOL management area has already been added, the capacity \\nof pools and virtual volumes has reached the maximum. In this case, delete unnecessary \\npools and virtual volumes, and then retry the operation.
-1947941466	5	5	The capacity saving setting cannot be enabled, because a pool with the data direct \\nmapping attribute is specified.\\nDisable either the data direct mapping attribute for the specified pool or the capacity \\nsaving setting.
-1947941465	5	5	The full allocation setting and the capacity saving setting cannot be enabled at \\nthe same time.\\nDisable either the full allocation setting or the capacity saving setting
-1947941464	1	5	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.\\nVerify the following items, and then retry the operation:\\n- The pool capacity\\n- The threshold for the pool usage\\n- The pool status
-1947941463	5	5	The operation cannot be performed because the specified parameter is not valid.\\nVerify the setting for Data Saving. If this problem persists, contact the HSSC.
-1947941440	5	5	The deduplication system data volume cannot be allocated, because a pool with the \\ndata direct mapping attribute is specified.\\nDisable the data direct mapping attribute for the specified pool, and then retry \\nthe operation.
-1947941403	5	5	The deduplication system data volumes cannot be allocated, because pools for which \\nthe full allocation setting is enabled are specified.\\nDisable Full Allocation for the specified pools, and then retry the operation.
-1947941402	5	5	The capacity saving setting cannot be applied to DP-VOLs.\\nRestore the selected DP-VOLs, and then change the capacity saving setting to the \\nsetting selected when the DP-VOLs were created.
-1947941379	5	5	The specified LDEV is already being used as a JNL volume by Universal Replicator \\nor Universal Replicator for Mainframe.\\nSpecify a different LDEV, and then retry the operation.
-1947941378	5	5	The operation cannot be performed, because the specified LDEV is in a state in which \\nthe capacity saving setting cannot be changed.\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Retry the deletion operation.\\n(6) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool of the selected \\nDP-VOLs, block and format the DP-VOLs, and then retry the operation.
-1947941376	5	5	The operation cannot be performed, because the deduplication system data volume of \\nthe pool associated with the specified LDEV is blocked.\\nRestore the deduplication system data volume, and then retry the operation.
-1947941370	5	5	The operation cannot be performed, because the selected DP-VOLs are associated with \\na pool for which the multi-tier pool setting is enabled.\\nDisable the multi-tier pool setting for the pool associated with the selected DP-VOLs, \\nand then retry the operation.
-1947941284	5	5	The selected pool volumes cannot be added to a pool with the data direct mapping \\nattribute, because they are deduplication system data volumes.\\nSelect different LDEVs.
-1947941281	5	5	The specified LDEVs cannot be deleted, because the LDEVs contain data used by the \\ncapacity saving functions (compression function or deduplication function).\\nFormat the LDEVs or change the capacity saving setting of the LDEVs to Disabled, \\nand then retry the operation.
-1947940571	5	5	The mapping information for the specified LDEVs is not correct.\\nContact the HSSC.
-1947940570	5	5	LDEVs cannot be deleted, because deduplication system data volumes are specified.\\nSelect different LDEVs.
-1947940569	5	5	The specified number of the deduplication system data volumes exceeds the maximum \\nnumber that can be specified for a single pool.\\nVerify that the specified information is correct.
-1922220499	1	5	Another user is downloading the file or transferring the file to the FTP server. \\nPlease wait for a while, and then retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
-1910507839	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1910507585	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1910502040	5	0	An internal logic error occurred.\\nContact the HSSC.
-1910502039	5	0	The specified volume cannot be used because it is write-protected by Data Retention Utility.\\nRelease the write-protection by the Data Retention Utility.
-1910501947	5	5	The capacities of the volumes specified as the primary volume and the secondary volume \\ndo not match.\\nSpecify volumes with the same capacity.
-1910500122	5	0	This operation has been rejected.\\nThe Data Retention Utility setting does not allow the specified volume(s) to be specified \\nas S-VOL(s).\\nChange the setting of Data Retention Utility so that the specified volumes can be \\nused as S-VOLs.
-1910478049	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1910478017	5	3	The Storage Navigator is busy. \\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-1910473275	5	0	Processing in progress. Please wait for a while, and then retry the operation.\\nWait for a while, and then retry the operation.
-1910473274	5	0	The target volume status is being changed to SMPL.  \\nWait for a while, and then retry the operation.
-1910473177	5	5	The setting could not be applied because there is an error in a different setting.\\nVerify the error factor in another setting and then retry the operation.
-1910445377	5	0	This error code is not registered.\\nIf this problem persists, contact the HSSC.
-1910418500	5	4	A time-out error occurred. \\nIf the problem persists despite retrying, please call the HSSC.
-1910418499	5	4	A time-out error occurred. \\nVerify the status of the controller, and then retry the operation.
-1910417539	5	4	A time-out error occurred. \\nIf the problem persists despite retrying, please call the HSSC.
-1910413695	5	0	Sufficient amount of shared memory is not installed or \\nthe program product is not installed.\\nAdd shared memory or confirm whether the necessary program product key is installed.
-1910413694	5	0	The command has been rejected, because the command specified last time is being processed.\\nWait for a while, and then retry the operation.
-1910413692	5	0	You cannot create the new pair, because a remote copy pair exists in the same storage \\nsystem frame.\\nDelete the Remote Copy pair.
-1910413691	5	0	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 \\nrequirements for the operation.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and \\nL2 pairs at the same time.\\nTake either of the following actions.\\n- See the ShadowImage User Guide to verify the pair configuration or status, or the \\nvolume status, and then retry the operation.\\n- Perform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
-1910413690	1	0	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 \\nL2 pairs at the same time.\\nSee the ShadowImage User Guide for the relation between the pair status and the operation \\nthat can be performed.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
-1910413689	5	0	The command cannot be run because the specified secondary volume is used by the host.\\nVary the secondary volume offline from the host, and then retry the operation.
-1910413688	5	0	The Pairsplit (Split Pairs) command was issued to the pairs in a PSUS status.\\nThe Pairsplit command cannot be run because the pair is already in the PSUS status.
-1910413687	5	0	The Paircreate (Create Pairs) command was issued to the pairs in the PSUS status.\\nThe Paircreate command cannot be run because the pair is already in the PSUS status.
-1910413686	5	0	The Pairsplit (Split Pairs) command with the QUIESCE specification was issued to \\na secondary boot device.\\nVerify the settings, and then retry the operation.
-1910413664	5	0	The P-VOL Suspend command was issued to a secondary boot device.  \\nVerify the settings, and then retry the operation.
-1910413662	5	0	Cannot perform Pairresync (Resync Pairs) or Pairsplit-E (Suspend Pairs) operation \\nbecause of the path group setting.\\nDetach the S-VOL from the host, or delete the Remote Copy path.
-1910413655	5	5	The capacities of the volumes specified as the primary volume and the secondary volume \\ndo not match.\\nSpecify volumes with the same capacity.
-1910413632	5	0	The number of multiple copy jobs exceeded the maximum.\\nVerify the settings, and then retry the operation.
-1910413628	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413627	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413626	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413625	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413624	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413602	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413601	1	0	An internal logic error occurred.\\nContact the HSSC.
-1910413600	5	0	The command has been rejected, because the P-VOL or the S-VOL is being used by the host.\\nStop the usage by the host.
-1910413597	1	0	A processor failure was detected.  \\nContact the HSSC.
-1910413596	1	0	A cache failure was detected.  \\nContact the HSSC.
-1910413595	1	0	The cache capacities do not match.  \\nContact the HSSC.
-1910413594	1	0	An SM failure was detected.  \\nContact the HSSC.
-1910413593	1	0	There is not enough shared memory on the local storage system to create 4096 pairs.\\nThe shared memory on the local storage system is not enough. Contact the HSSC.
-1910413571	1	0	There is sufficient shared memory to create 4096 pairs, but initial storage system \\nsetup is required before creating pairs.\\nContact the HSSC.
-1910413570	3	0	There is sufficient shared memory to create 4096 pairs, and the initial storage system \\nsetup is complete.\\nClose the message box.
-1910413569	1	0	Failed to complete the initial shared memory setup.  \\nContact the HSSC.
-1910413568	1	0	The shared memory size is different.  \\nContact the HSSC.
-1910413567	3	0	16 Mbytes of shared memory is available.\\n-
-1910413566	1	0	A power supply failure is detected.  \\nContact the HSSC.
-1910413565	5	0	The command was rejected.  The PS OFF is in progress.  \\nRetry the operation with power ON.
-1910413564	1	0	A data transfer failure is detected (CHB).\\nContact the HSSC.
-1910413563	1	0	A data transfer failure is detected (DKB).\\nContact the HSSC.
-1910413562	5	0	The P-VOL is not implemented.  \\nOperations cannot be performed on unconfigured volumes.
-1910413540	1	0	The command cannot be run because the specified primary volume is blocked.\\nRestore the blocked volume, and then retry the operation.
-1910413539	5	0	The primary volume is being formatted or shredded.\\nWait until the volume is formatted, and then retry the operation. 
-1910413538	5	0	This volume cannot be specified as an P-VOL because it is used as a command device.\\nCheck the target volume.
-1910413537	5	0	The S-VOL is not implemented.  \\nOperations cannot be performed on unconfigured volumes.
-1910413536	5	0	The command cannot be run because the specified secondary volume is blocked.\\nRestore the blocked volume, and then retry the operation.
-1910413535	5	0	The secondary volume is being formatted or shredded.\\nWait until the volume is formatted, and then retry the operation. 
-1910413534	5	0	This volume cannot be specified as an S-VOL because it is used as a command device.\\nA volume that is not used as a command device shall be specified as an S-VOL.
-1910413533	5	0	The volume is not implemented.  \\nOperations cannot be performed on unconfigured volumes.
-1910413531	5	0	The volume is being formatted.  \\nWait until the volume is formatted, and then retry the operation. 
-1910413509	5	0	This volume cannot be specified because it is used as a command device.\\nSpecify a volume that is not used as a command device.
-1910413508	1	0	The command code is invalid.  \\nContact the HSSC.
-1910413507	1	0	The command code sender is invalid.  \\nContact the HSSC.
-1910413506	5	0	The volume type is invalid.  \\nVerify the settings, and then retry the operation.
-1910413505	5	0	The volume type is invalid.  \\nVerify the settings, and then retry the operation.
-1910413504	1	0	The command code sender is invalid.  \\nContact the HSSC.
-1910413502	1	0	The number of effective lists is invalid.  \\nContact the HSSC.
-1910413500	5	0	The command cannot be run because the area of the differential table or the pair \\ntable to set pairs is not enough.\\nSee the ShadowImage User Guide or the Thin Image User Guide for the relation between \\nthe number of pairs that can be created and the shared memory.
-1910413478	5	0	The selected volume does not exist.  \\nRefresh the window, and then retry the operation.
-1910413476	5	0	The volume is already defined as a P-VOL.  \\nCheck the status of the volume.
-1910413475	5	0	The volume is defined as a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910413474	5	0	The volume is defined as a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910413447	5	0	The specified volume is for backup servers only.   \\nSelect a different volume, and then retry the operation.
-1910413446	5	0	The specified volume is not for backup servers only.   \\nVerify the settings, and then retry the operation.
-1910413444	5	0	The RAID level of the specified volume is not supported.  \\nSpecify a volume of the supported RAID level.
-1910413441	5	0	The number of groups that can be set in the same storage system is invalid.\\nVerify the settings, and then retry the operation.
-1910413440	5	0	The number of pairs that can be set in the same group is invalid.  \\nVerify the settings, and then retry the operation.
-1910413439	5	0	The specified group number is not set.  \\nVerify the settings, and then retry the operation.
-1910413438	5	0	The specified group name is invalid.  \\nVerify the settings, and then retry the operation.
-1910413416	5	0	The group name and the number do not match.  \\nVerify the settings, and then retry the operation.
-1910413415	5	0	The specified pair is already set in another group.  \\nVerify the settings, and then retry the operation.
-1910413414	5	0	The command was rejected because the licensed capacity was exceeded.\\nCheck the capacity of the installed license key. To create more pairs, purchase a \\nlicense key for larger capacity.
-1910413413	5	0	The P-VOL is a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910413412	5	0	The P-VOL is a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910413411	5	0	The specified P-VOL does not exist.  \\nRefresh the window, and then retry the operation.
-1910413409	5	0	No more pairs can be created with the specified primary volume.\\nSee the ShadowImage User Guide or the Thin Image User Guide for the pair configuration.
-1910413408	5	0	The specified volume is not a P-VOL.  \\nCheck the status of the volume.
-1910413407	5	0	The specified volume is already used as a primary volume.\\nSelect a different volume, and then retry the operation, or release the pair of the \\nselected volume, and then retry the operation.
-1910412734	5	0	The RAID level of the specified volume is not supported.  \\nSelect a volume of the supported RAID level, and then retry the operation.
-1910412733	5	0	The specified S-VOL (Primary Volume) cannot be paired with a backup server volume.\\nVerify the settings, and then retry the operation.
-1910412732	5	0	The command has been rejected, because the specified P-VOL has already been used \\nas S-VOL of the other pair.\\nThe volume used as S-VOL of the other pair cannot be used as P-VOL.
-1910412731	1	0	The target volume is set as a primary volume for Data Migration.  \\nPlease delete a Data Migration pair.
-1910412730	1	0	The target volume is set as a secondary volume for Data Migration.  \\nPlease delete a Data Migration pair.
-1910412729	5	0	The Pairresync (Resync Pairs) command was issued to a device in the SMPL status.\\nCheck the pair status.
-1910412728	5	0	The operation to create an L2 pair was rejected because the P-VOL of the L1 pair \\nis used as the P-VOL of a TrueCopy pair.\\nWhen the P-VOL of the L1 pair is used as a P-VOL of a TrueCopy pair, the L2 pair \\ncannot be created.
-1910412727	5	0	The operation cannot be performed because the selected secondary volume is used as \\na primary volume of a TrueCopy pair or a Universal Replicator pair.\\nSee the TrueCopy User Guide or the Universal Replicator User Guide for the operations \\nthat can be performed in configurations where a ShadowImage pair is combined with \\na TrueCopy pair or a Universal Replicator pair.
-1910412726	5	0	The specified S-VOL is not defined.\\nRefresh the window, and then retry the operation.
-1910412703	5	0	The S-VOL is a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910412702	5	5	The operation failed because the specified S-VOL was used as S-VOL of other pairs.\\nSpecify another volume.
-1910412701	5	0	The specified volume is not an S-VOL.  \\nCheck the status of the volume.
-1910412700	5	0	The RAID level of the specified S-VOL is not supported.  \\nSpecify a volume of the supported RAID level.
-1910412699	5	0	The operation cannot be performed because the selected secondary volume is used as \\na primary volume of a TrueCopy pair or a Universal Replicator pair.\\nTo create a ShadowImage pair, select a different secondary volume. To combine a ShadowImage \\npair with a TrueCopy pair or a Universal Replicator pair, create the ShadowImage \\npair first.
-1910412698	5	0	The command cannot be run because the specified secondary volume is used as a secondary \\nvolume of a TrueCopy pair.\\nSpecify a different volume.
-1910412697	1	0	The S-VOL is used as a primary volume for Data Migration.  \\nPlease delete a Data Migration pair.
-1910412696	1	0	The target S-VOL is used as a secondary volume for Data Migration.\\nPlease delete a Data Migration pair.
-1910412695	5	0	The S-VOL is already defined as a P-VOL.  \\nCheck the volume number.
-1910412694	5	0	The specified S-VOL is defined as a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1910412668	5	0	The command has been rejected, because there is no pair to be operated.\\nVerify if the specified P-VOL and S-VOL are correct.
-1910412667	5	0	The primary volume and secondary volume have the same LDEV ID.  \\nVerify the selected LDEV ID.
-1910412666	5	0	The SMPL command could not be executed because the quick split operation is in progress.\\nWait until the quick split operation is complete, and then retry the operation. 
-1910412665	5	0	The Pairresync operation has been rejected, because pair status is COPY(SP)/COPY.\\nWait until the status of the pair changes to PSUS.
-1910412664	5	0	The operation of the L1 pair failed because the L2 pair was in COPY(SP)/COPY status \\nor PSUS(SP)/COPY status.\\nWait until the L2 pair status changes to PSUS, and then retry the operation.
-1910412663	5	0	The status mode specification is invalid.  \\nVerify the settings, and then retry the operation.
-1910412641	5	0	The status mode type is invalid.  \\nVerify the settings, and then retry the operation.
-1910412640	5	0	The specified CU number is invalid.  \\nContact the HSSC.
-1910412639	1	0	The timing of issuing the command is invalid.  \\nContact the HSSC.
-1910412638	1	0	The abnormal status is invalid.  \\nContact the HSSC.
-1910412634	5	0	The specified P-VOL is used as a source volume for Volume Migration.\\nSpecify other volume(s), or release the Volume Migration Setting.
-1910412610	5	0	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 \\nshare a primary volume.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and \\nL2 pairs at the same time.\\nWait until the Reverse Copy or Quick Restore operation is complete, and then retry \\nthe operation.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
-1910412609	5	0	The L1 pairs include a pair in the status of Reverse Copy or Quick Restore.\\nWait until the Reverse Copy or Quick Restore operation is complete, and then retry \\nthe operation.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
-1910412608	5	0	The command has been rejected, because the specified S-VOL is shared as the P-VOL \\nof the other pair and the pair is in the COPY(RS-R)/RCPY status.\\nWait until the status of the pair sharing the primary volume  becomes PAIR, and then \\nretry the operation. See the section "Operations permitted for L1, L2 pairs" in the \\nShadowImage User Guide for the relation between the status of pairs and ShadowImage \\noperations.
-1910412607	5	0	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 \\nL2 pairs at the same time.\\nSee the section "Pair resynchronization" in the ShadowImage User Guide for the relation \\nbetween the pair status and the ShadowImage operations.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
-1910412606	5	0	The operation failed because the pairs sharing a P-VOL contain a pair in other than \\nPSUS or PSUE status.\\nVerify the status of the pairs that share the P-VOL.
-1910412605	5	0	The Reverse Copy command could not be executed because the primary volume was shared \\nwith the primary volume of a remote replication pair.\\nRelease the remote replication pair, and then retry the operation.
-1910412604	5	0	The Reverse Copy request was rejected, because the P-VOL was shared with a Remote \\nCopy pair in the non-suspend status.\\nDelete the Remote Copy pair.
-1910412603	5	0	The Reverse Copy command could not be executed because the secondary volume was shared \\nwith the primary volume of a remote replication pair.\\nRelease the remote replication pair, and then retry the operation.
-1910412602	5	0	The boot device and the P-VOL do not match in the Paircreate (Create Pairs) command.\\nCheck the specified volume number.
-1910412601	5	0	Because the boot device is the S-VOL in the Pairsplit-S (Delete Pairs) command, the \\nflag does not match.\\nCheck the specified volume number.
-1910412579	5	0	The boot device and the P-VOL do not match in the Paircreate (Create Pairs), Pairresync \\n(Resync Pairs), or Pairsplit-S (Delete Pairs) command.\\nCheck the target volume number.
-1910412577	5	0	The boot device is not a P-VOL nor S-VOL.  \\nCheck the target volume number.
-1910412576	5	0	Because the boot device is the P-VOL in the Pairsplit-S (Delete Pairs) command, the \\nflag does not match.\\nCheck the target volume number.
-1910412575	5	0	Boot device and S-VOL do not match in Paircreate (Create Pairs), Pairresync (Resync \\nPairs), or Pairsplit-S (Delete Pairs) instruction.\\nCheck the target volume number.
-1910412572	1	0	The Swap&Freeze option cannot be specified, because the mode 80 is on.\\nContact the HSSC.
-1910412450	5	0	The specified MU number is not less than or equal to 2.\\nCorrect the MU number, and then retry the operation.
-1910409789	5	0	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 \\nis not in the PSUS status.\\n- The pair operation was performed on some pairs of one-to-multiple volumes or L1 \\nand L2 pairs at the same time.\\nWait until the L1 pair changes to the PSUS status, and then retry the operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1875571791	5	5	An invalid CLPR No. was detected.\\nCorrect the CLPR No., and then retry the operation. If this problem persists, contact the HSSC.
-1875571769	1	5	An invalid SLPR No. was detected.\\nIf the problem persists despite retrying, please call the HSSC.
-1875571768	5	5	The entered CLPR name is not valid. It is the same as a CLPR name reserved for a \\ndifferent CLPR ID or includes characters other than alphanumeric ones.\\nCorrect the CLPR name. For reserved CLPR names, see the Virtual Partition Manager \\nUser Guide.
-1875571766	1	5	Invalid logon information is detected.\\nContact the HSSC.
-1875571765	5	5	The entered CLPR name is already used.\\nEnter a different CLPR name, and then retry the operation. If this problem persists, \\ncontact the HSSC.
-1875571762	1	5	The total of the values registered as the maximum number of users that can connect \\nto each SLPR exceeds the value set as the maximum number of connections to the storage system. \\nIf the problem persists despite retrying, please call the HSSC.
-1875571737	5	5	The specified CU number is invalid.\\nCorrect the CU number, and then retry the operation. If this problem persists, contact the HSSC.
-1875571736	5	5	An attempt has been made to either register newly a CLPR that is already registered, \\nor delete a CLPR that is not registered.\\nCorrect the CLPR settings, and then retry the operation. If this problem persists, \\ncontact the HSSC.
-1875571735	1	5	An attempt has been made to either register newly a SLPR that is already registered, \\nor delete a SLPR that is not registered.\\nIf the problem persists despite retrying, please call the HSSC.
-1875571734	5	5	The configuration of the CLPR is already changed, or some parity groups or some virtual \\nvolumes are registered in a different CLPR.\\nSelect a different parity group, and then retry the operation. If this problem persists, \\ncontact the HSSC.
-1875571733	5	5	The configuration of the CLPR is already changed, or the settings of the parity group \\nor the virtual volume are not valid.\\nCorrect the parity group settings, and then retry the operation. If this problem \\npersists, contact the HSSC. 
-1875571732	5	5	The specified port name (port number) is invalid.\\nCorrect the port name (port number), and then retry the operation. If this problem \\npersists, contact the HSSC. 
-1875571731	1	5	The configuration of the CLPR is already changed, or the cache size is not valid.\\nCorrect the cache size setting, and then retry the operation. If this problem persists, \\ncontact the HSSC. 
-1875571730	5	5	The configuration of the CLPR is already changed, or the specified cache size is \\nless than the minimum.\\nSet the cache size to be equal to or greater than the minimum, and then retry the \\noperation. If this problem persists, contact the HSSC.
-1875571729	5	5	The configuration of the CLPR is already changed, or the total cache size is not valid.\\nCorrect the cache size, and then retry the operation. If this problem persists, contact the HSSC.
-1875571704	1	5	The same port is already registered in a different SLPR.\\nIf the problem persists despite retrying, please call the HSSC.
-1875569808	5	5	This function is not available. Virtual Partition Manager is required to create CLPR.\\nInstall the program product.
-1875537203	3	4	The logon information of the partition management function has been initialized because \\nthe conflicting information is detected.\\nContact the storage administrator. (To the storage administrator: Reconfigure the \\nlogon information. If this problem persists, contact the HSSC.)
-1875537202	1	4	The operation to set the maximum number of connections has been cancelled because \\nan attempt has been made to specify this value to less than the number of users who \\nare currently connected. Check the maximum permissible number of connections.\\nReduce the number of users currently logged on, and then retry the setting, or specify \\na value larger than the number of users currently logged on.
-1875537138	1	2	This function cannot be used by the storage partition administrator.\\nIf the problem persists despite retrying, please call the HSSC.
-1875537105	5	0	The licensed capacity exceeds the maximum because of the configuration change.\\nCorrect the licensed capacity on the License Key Partition Definition panel.
-1875512216	1	4	An unknown error was detected.\\nIf this problem persists, contact the HSSC.
-1875479513	5	6	Some of the shared memories of the storage system may be blocked, or the storage \\nsystem is being maintained.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-1875479512	5	6	Some of the cache memories of the storage system may be blocked, or the storage system \\nis being maintained.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-1875479511	1	5	The configuration cannot be changed because the write pending rate of the intended \\nCLPR is too high. \\nWait until the write pending rate falls, and then retry the operation.
-1875479508	5	6	A maintenance job (correction copy, drive copy, LDEV formatting, or LDEV shredding) \\nis running on the storage system.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-1875479507	1	5	Parity groups in CLPR are being migrated in the storage system. \\nWait until the parity group migration is complete, and then retry the operation.
-1875479506	1	5	The CLPR capacity is being changed on the storage system.\\nWait for a while, and then retry the operation.
-1875479505	1	3	An error occurred on the DKC while obtaining information about the progress of CLPR \\nprocessing.\\nIf this problem persists, contact the HSSC.
-1875479442	5	5	The CLPR to which the specified parity groups belong cannot be changed, because the \\nparity groups do not contain all of the journal volumes in a journal of Universal \\nReplicator.\\nSpecify parity groups so as to contain all of the journal volumes in the journal.
-1874641428	5	6	The operation cannot be performed because a configuration change is in progress on \\nthe local storage system.\\nWait until the configuration change performed by RAID Manager or Volume Migration, \\nor the Quick Restore operation is complete, and then retry the operation.
-1873724722	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-1873724690	5	0	The specified parity group or virtual volume cannot be used because you do not have \\npermission to access a resource group to which the parity group or the virtual volume belongs.\\nVerify the resources allocation for the user with security administrator role.
-1873605586	5	5	The selected CLPR cannot be deleted.\\nSelect [Refresh All] on the [File] menu, and then retry the operation. If this problem \\npersists, contact the HSSC.
-1873605585	5	5	The parity group that you attempt to migrate has a Thin Image pool volume defined.\\nDelete the Thin Image pool volume belonging to the selected parity group, and then \\nretry the operation.
-1853219747	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1853188996	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1713994334	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1713964544	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1713964512	5	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please contact the HSSC.
-1713959672	5	5	The setting cannot be applied because there is an error in a different setting.\\nVerify and correct the error in the other setting, and then retry the operation.
-1713904995	5	4	A time-out error occurred. \\nVerify that all of the settings have been applied. Retry the setting on the items \\nthat are not applied if there is any. If this problem persists, contact the HSSC.
-1713904994	5	4	A time-out error occurred. \\nVerify that all of the settings have been applied. Retry the setting on the items \\nthat are not applied if there is any. If this problem persists, contact the HSSC.
-1713904034	5	4	The operation cannot be performed, or a communication time-out error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-1713904030	5	4	The storage system has accepted the request normally, but the pair status change \\nrequires some time.\\nVerify that the pair status has been changed. If the status is not changed, verify \\nthe local storage system or remote storage system configuration and the condition \\nof the paths between the local storage system and the remote storage system. If this \\nmessage is displayed after the Create Pairs or Resync Pairs operation, perform the \\nSplit Pairs operation for the pair in the Copy status, and then perform the Resync \\nPairs operation. 
-1713898268	5	4	Please retry operation.\\nRetry the operation.
-1713898267	5	4	The remote path between the local storage system and the remote storage system is \\nnot active.\\nVerify the remote path status. For use by an open system, verify that a path whose \\nconnection type is System is registered.
-1713898266	5	4	The status of the primary volume is not valid.\\nWait for a while, and then retry the operation.
-1713898265	5	4	The specified number of remote paths is less than the minimum number of paths.\\nVerify the number of normal remote paths.
-1713898264	5	4	The specified number of remote paths is less than the minimum number of paths due \\nto a communication error between the local storage system and the remote storage system.\\nVerify the remote path status, and then restore the paths.
-1713898263	5	4	The remote paths cannot be deleted due to a communication error between the local \\nstorage system and the remote storage system.\\nVerify the CHB status of the local storage system. If the CHB is blocked, contact the HSSC.
-1713898262	5	4	The parameter entered in the remote replication operation is not valid.\\nEnter a correct value. When the status of the specified volume is SMPL (Simplex), \\ndelete the pair by specifying Delete Pair by Force, and then retry the operation.
-1713898260	5	4	The pair status of the secondary volume is invalid for the specified operation.\\nVerify the pair status of the secondary volume.
-1713898259	1	4	The TrueCopy or Universal Replicator operation cannot be performed.\\nContact the HSSC to replace the CHB.
-1713898237	5	4	The pair status of the specified volume is not valid.\\nThe pair status does not permit this operation. Verify the pair status, and if the \\noperation is permitted retry.
-1713898236	5	4	The port name, host group ID, LUN ID, CU, or LDEV of the specified volume is invalid.\\nVerify if the specified port name, host group ID, LUN ID, CU, or LDEV exists in the \\nlocal storage system.
-1713898235	5	4	The operation was rejected due to a 'FREEZE' state.\\nIf this is a remote connection operation, recover from the freeze status, and then \\nretry the operation. If this is a pair operation for remote replication, recover \\nthe remote path status, and then retry the operation.
-1713898234	5	4	The port group already exists on the specified port.\\nThe port type could not be changed because the port group was set in the specified \\npackage. Delete the group setting, then change the port type.
-1713898233	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713898232	5	4	The number of remote paths is invalid.\\nVerify the specified number of paths, and then retry the operation.
-1713898229	5	4	The specified remote path already exists.\\nVerify all remote paths, and then select a different port name.
-1713898228	5	4	The serial number or model of the remote storage system is not valid.\\nVerify the serial numbers and models of the specified remote storage system and the \\nregistered remote storage systems, and select the correct values. If the values are \\ncorrect, verify the cable connection of the remote storage system, and then retry \\nthe operation. If this problem persists, contact the HSSC.
-1713898206	5	4	The operation cannot be performed because the number of remote storage systems is \\nin 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.\\nReduce the number of registered remote storage systems, and then retry the operation.
-1713898205	5	4	The remote path creation was incomplete.\\nVerify the path connections between the local storage system and the remote storage \\nsystem, and then retry the operation.
-1713898204	5	4	The remote path could not be created.\\nVerify the path connections between the local storage system and the remote storage \\nsystem, and then retry the operation.
-1713898203	5	4	The operation cannot be performed because the specified remote path is the last path \\nof the pair volume of any of the following:\\n- TrueCopy\\n- Universal Replicator\\n- global-active device\\nCreate a different remote path or delete all pair volumes on the remote storage system, \\nand then retry the operation.
-1713898202	5	4	The specified number of remote paths is less than the minimum number of paths.\\nIncrease the number of remote paths or specify the minimum number of paths smaller.
-1713898199	5	4	The number of normal remote paths is less than the minimum number of paths.\\nAdd normal remote paths, and then set the minimum number of paths, or reduce the \\nminimum number of paths, and then delete the remote path.
-1713898198	5	4	The number of normal remote paths is less than the minimum number of paths.\\nPlease take either of the following actions: Add normal paths, then delete the paths. \\nDecrease the number of minimum paths, then delete the paths.
-1713898197	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713898174	5	4	The existing logical addresses are not equal.\\nRemove the remote connection, specify the same logical address, and then register \\na remote connection again.
-1713898172	1	4	The remote replication function is not installed on the local storage system.\\nInstall the required program product.
-1713898171	1	4	The remote replication function is not installed on the remote storage system.\\nInstall the required program product.
-1713898170	5	4	The serial number or model of the remote storage system is not valid.\\nVerify the serial numbers and models of the specified remote storage system and the \\nregistered remote storage systems, and select the correct values. If the values are \\ncorrect, verify the cable connection of the remote storage system, and then retry \\nthe operation. If this problem persists, contact the HSSC.
-1713898169	5	4	The operation cannot be performed because a pair volume of any of the following exists \\non the specified remote storage system:\\n- TrueCopy\\n- Universal Replicator\\n- global-active device\\n\\nDelete all pair volumes on the remote storage system, and then retry the operation.
-1713898168	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713898166	5	4	The NVS status of the local storage system connected to the host is not active.\\nVerify the NVS status of the local storage system, and then retry the setting. If \\nyou cannot set up, contact the HSSC.
-1713898144	5	4	The NVS status of the remote storage system connected to the host is not active.\\nVerify the NVS status of the remote storage system, and then retry the setting. If \\nyou cannot set up, contact the HSSC.
-1713898143	5	4	The remote paths between the local storage system and the remote storage system are \\nnot established.\\nCheck the remote paths status between the local storage system and the remote storage system.
-1713898142	5	4	Pinned tracks exist in the primary volume.\\nRestore the pinned tracks in the primary volume.
-1713898141	5	4	Pinned tracks exist in the secondary volume.\\nRestore the pinned tracks in the secondary volume.
-1713898140	5	4	The specified primary volume cannot be used.\\nVerify if the primary volume is in any of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in the correction access condition.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.
-1713898139	5	4	A volume cannot be used as a secondary volume when:\\n- It is used by TrueCopy.\\n- It is used by Universal Replicator.\\nSpecify a different volume.
-1713898110	1	4	An internal error occurred. \\nToo many pairs might be specified. Verify the pairs whose statuses are unchanged \\nfrom those before the operation, reduce the number of pairs to be specified, and \\nthen retry the operation on the pairs. If this problem persists, contact the HSSC.
-1713898109	5	4	The serial number of the local storage system is not valid.\\nVerify the serial number of the local storage system, and then retry the operation \\nwith the correct parameter.
-1713898107	5	4	The cache of the local storage system is not active.\\nVerify the cache status of the storage system connected to the host. If the cache \\nis disabled, enable the cache. If you cannot enable the cache, contact the HSSC.
-1713898106	1	4	One side of the cache or the shared memory is blocked in the local storage system.\\nVerify the status of the cache and the shared memory in the local storage system, \\nand then contact the HSSC.
-1713898105	1	4	An unexpected error occurred in the local storage system.\\nContact the HSSC.
-1713898104	5	4	The cache of the remote storage system is not active.\\nVerify the cache status of the local storage system connected to the host. If the \\ncache is disabled, enable the cache. If  you cannot enable the cache, contact the HSSC.
-1713898081	5	4	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.\\nSpecify a different volume for the primary volume or the secondary volume.
-1713898080	5	4	The cache of the secondary volume is not active.\\nVerify the cache status of the secondary volume connected to the host. If the cache \\nis disabled, enable the cache. If you cannot enable the cache, contact the HSSC.
-1713898078	5	4	The specified secondary volume cannot be used.\\nVerify the status of the specified secondary volume.
-1713898076	5	4	TrueCopy does not support the emulation type of the secondary volume.\\nVerify that the emulation type of the secondary volume is OPEN-V.
-1713898074	5	4	The remote storage system is still used by a different remote replication program product.\\nIf the remote storage system is used by a different remote replication program product, \\ndelete the remote storage system if necessary, and then retry the operation.
-1713898051	5	4	The cache on the local storage system is automatically recovering.\\nWait for a few minutes, and then retry the operation.
-1713898049	5	4	The operation cannot be performed because a communication error occurred or the secondary \\nvolume status is not valid.\\nWait until the communication error is recovered or the secondary volume becomes normal \\nstatus, and then retry the operation.
-1713898048	5	4	The operation cannot be performed because the primary volume is in the Split status.\\nResynchronize the primary volume, and then retry the operation.
-1713898046	5	4	The multi platform feature is already installed in the remote storage system.\\nRemove the multi platform feature from the remote storage system.
-1713898045	5	4	The volume specified as the primary volume is used by Universal Replicator.\\nSpecify a different volume.
-1713898044	5	4	The local storage system does not support connection with the specified remote storage system.\\nSee the user guide to verify whether the local storage system supports the connection \\nwith the specified remote storage system.
-1713898043	1	4	One side of the cache or the shared memory of the local storage system is blocked.\\nVerify the status of the cache and shared memory of the remote storage system, and \\nthen contact the HSSC.
-1713898012	5	4	The pair operation cannot be performed because the specified secondary volume applies \\nto one of the following:\\n- A LUN path is not defined.\\n- Its emulation type is not supported.\\nVerify the configuration of the remote storage system, and then specify an existing \\nvolume for the secondary volume. Or verify the emulation type of the specified secondary volume.
-1713898011	5	4	The combination of the primary and secondary volume configurations is not valid.\\nVerify the configurations of both the primary and secondary volumes.
-1713897986	5	4	The TrueCopy function is not installed in the local storage system or the remote \\nstorage system.\\nInstall the TrueCopy function in the local storage system and the remote storage \\nsystem, and then retry the operation.
-1713897984	5	4	The operation cannot be performed because the specified primary volume applies to \\neither of the following:\\n- A secondary volume of ShadowImage, which is not in the PSUS status.\\n- A volume used by ShadowImage in the Reverse Copy status.\\nVerify the status of the specified primary volume.
-1713897983	5	4	The operation cannot be performed because the specified secondary volume applies \\nto either of the following:\\n- A secondary volume of ShadowImage.\\n- A volume of ShadowImage in the Reverse Copy status.\\nVerify the status of the specified secondary volume.
-1713897982	5	4	If the specified primary volume is a secondary volume of ShadowImage, one primary \\nvolume must be paired with one secondary volume.\\nVerify the status of the specified primary volume.
-1713897981	5	4	The pair cannot be registered because the local storage system is already used by \\nShadowImage.\\nVerify the use status of ShadowImage on the local storage system.
-1713897980	5	4	The primary volume is already used in Volume Migration.\\nVerify the status of the primary volume.
-1713897307	5	4	The secondary volume is already used in Volume Migration.\\nVerify the status of the secondary volume.
-1713897306	5	4	The remote path or the remote storage system is in a high load state.\\nWait for a while, and then retry the operation.
-1713897299	5	4	The operation cannot be performed because the pair status of the specified volume \\nin the local storage system is changing.\\nWait until the pair status of the specified volume becomes available, and then retry \\nthe operation.
-1713897298	5	4	The operation cannot be performed because the pair status of the specified volume \\nin the remote storage system is changing.\\nWait until the pair status of the specified volume becomes available, and then retry \\nthe operation.
-1713897267	5	4	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 ShadowImage.\\nSpecify a different volume.
-1713897245	5	4	The TrueCopy operation cannot be performed because the specified secondary volume \\nis 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.\\nVerify the status of the secondary volume.
-1713897244	5	4	The specified secondary volume cannot be recognized from the connection port.\\nVerify the configuration of the specified secondary volume.
-1713897243	5	4	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 \\nof the local storage system.\\n\\nVerify that the secondary volume is in usable condition. If it is usable, verify \\nthat the microcode version of the local storage system supports this function or \\nconfiguration. If the DKCMAIN firmware version supports this function or configuration, \\ncontact the HSSC.
-1713897239	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897238	5	4	The local storage system cannot accept the pair operation.\\nWait for a while, and then retry the operation.
-1713897213	5	4	The specified secondary volume is already used as a reserved volume of Volume Migration.\\nSpecify a different volume.
-1713897212	5	4	The specified secondary volume is used by a Volume Migration pair whose status is changing.\\nWait for a few minutes, and then retry the operation.
-1713897211	5	4	The specified secondary volume is used by a Volume Migration pair whose status is changing.\\nWait for a few minutes, and then retry the operation.
-1713897210	5	4	The pair cannot be created because the used capacity exceeds the licensed capacity. \\nSee the license key and confirm the licensed capacity of the volumes. To create more \\npairs, purchase a license key that allows you to use a larger capacity.
-1713897209	5	4	The pair cannot be created because the used capacity exceeds the licensed capacity \\nof the remote storage system.\\nVerify the licensed capacity of the remote storage system. To create more pairs, \\npurchase a license key that allows you to use a larger capacity.
-1713897208	5	4	No additional volume pairs waiting for copy.\\nCheck the pair status and retry.
-1713897207	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897206	5	4	The selected volume is not used by a TrueCopy pair.\\nSelect a volume used by a TrueCopy pair, and then retry the operation.
-1713897183	5	4	The pair split operation for the secondary volume is invalid.\\nVerify the pair status of the secondary volume.
-1713897182	5	4	The specified volume is not a secondary volume.\\nVerify the secondary volume setting, and then retry the operation.
-1713897181	5	4	The secondary volume status change failed after the primary volume status changed.\\nVerify the secondary volume status.
-1713897180	5	4	The pair cannot be split because the specified volume is not available.\\nVerify the pair status of the specified volume.
-1713897177	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897176	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897175	5	4	Please wait a few minutes and retry the Suspend Pair(Pairsplit-r) operation.\\nThe suspend pair (Pairsplit-r) operation failed. A few minutes later, refresh the \\nwindow, confirm if the specified volumes are in the permissible status, then retry \\nthe operation.
-1713897174	5	4	The specified volume is not a TrueCopy pair volume.\\nVerify the TrueCopy pair setting, and then retry the operation.
-1713897121	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897120	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897119	5	4	Please wait a few minutes and retry the Delete Pair(Pairsplit-S) operation.\\nA few minutes later, retry the operation.
-1713897118	1	4	Unknown Error Code. \\nPlease call the HSSC.
-1713897117	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897116	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897115	1	4	An internal error occurred. \\nIf this problem persists, please contact the HSSC.
-1713897114	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897083	1	4	An internal error occurred. \\nIf this problem persists, please contact the HSSC.
-1713897058	1	4	An internal error occurred. \\nIf this problem persists, please contact the HSSC.
-1713897056	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897055	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897054	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713897053	1	4	An internal error occurred. \\nIf this problem persists, please call the HSSC.
-1713896343	1	4	Unknown Error Code. \\nIf this problem persists, please call the HSSC.
-1713896342	1	5	No more space is left in the local storage system for the differential management.\\nContact the HSSC.
-1713896341	1	5	The extended shared memory is not installed in the local storage system.\\nContact the HSSC.
-1713896340	1	5	No more space is left in the remote storage system for the differential management.\\nContact the HSSC.
-1713896339	1	5	The extended shared memory is not installed in the remote storage system.\\nContact the HSSC.
-1713896338	5	4	Invalid parameter. \\nSpecify a correct value.
-1713896315	1	4	A Port exchange error occurred. \\nIf this problem persists, please call the HSSC.
-1713896313	5	4	Logical paths exist on the port. \\nDelete the LUs defined on the specified port, then retry the operation.
-1713896312	5	4	Invalid port type. \\nRefresh the window, and then retry the operation. If this problem persists, call the HSSC.
-1713896311	5	4	Multi platform feature is already installed in the storage system.\\nCheck the configuration of the storage system.
-1713896310	5	4	The port type exchange operation is rejected because the host(s) is(are) processing \\nthe port type exchange. \\nRefresh the window, and then retry the operation. If this problem persists, call the HSSC.
-1713896283	5	4	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 ShadowImage.\\nVerify the status of the specified primary volume.
-1713896275	5	4	Invalid port type. \\nRefresh the window, and then retry the operation. If this problem persists, call the HSSC.
-1713896251	5	5	The remote path cannot be established because the configuration definition of the \\nspecified CU number does not exist.\\nSpecify a CU number that is defined in the configuration of the local storage system.
-1713896247	1	4	The Create Pairs operation cannot be performed. The DKCMAIN firmware version of the \\nspecified remote storage system does not support the remote replication function \\nusing NAS volumes.\\nVerify the DKCMAIN firmware version of the remote storage system.
-1713896218	5	4	The specified secondary volume cannot be used because of the access attribute changed \\nby Data Retention Utility.\\nVerify the Data Retention Utility setting of the specified secondary volume.
-1713896217	5	4	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)\\nAny 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)
-1713896124	5	4	The pair cannot be created because the secondary volume is LUN path-defined from \\nthe iSCSI port.\\nSpecify a different volume.
-1713896096	5	4	The pair cannot be created because the specified primary volume is a command device.\\nSpecify a different volume.
-1713896095	5	4	The pair cannot be created because the specified secondary volume is a command device.\\nSpecify a different volume.
-1689775870	5	5	A deduplication system data volume cannot be set as the source volume.\\nSelect a different LDEV.
-1689775848	5	5	A deduplication system data volume cannot be set as the target volume.\\nSelect a different LDEV.
-1689775839	5	5	The operation cannot be performed, because DP-VOLs whose capacity saving status is \\nnot Disabled are selected.\\nDisable the capacity saving setting for the selected DP-VOLs. Verify that the capacity \\nsaving status is Disabled, and then retry the operation.
-1689774078	5	7	The volume specified as a migration source cannot be used because it is a secondary \\nvolume of a ShadowImage pair whose primary volume has the nondisruptive migration \\nattribute.\\nSelect a different volume, and then retry the operation.
-1689774077	5	7	The volume specified as a migration target cannot be used because of the nondisruptive \\nmigration attribute of the volume.\\nSelect a different volume, and then retry the operation.
-1689774076	5	7	Nondisruptive migration is not installed.\\nInstall nondisruptive migration.
-1689774075	5	5	The extended shared memory for Volume Migration is not installed.\\nSee the manual to verify the condition for this operation.
-1689774073	5	7	The specified migration plan cannot be canceled because the volume migration is already \\nin the final step.\\nWait until the volume migration is complete.
-1689773244	5	5	The volumes specified as migration source volumes cannot be migrated because they \\nare external volumes with the data direct mapping enabled or belong to parity groups \\nwith the accelerated compression enabled.\\nSpecify external volumes without the data direct mapping attribute or volumes that \\nbelong to parity groups with the accelerated compression disabled, and then retry \\nthe operation.
-1689773243	5	5	The volumes specified as migration target volumes cannot be migrated because they \\nare external volumes with the data direct mapping enabled or belong to parity groups \\nwith the accelerated compression enabled.\\nSpecify external volumes without the data direct mapping attribute or volumes that \\nbelong to parity groups with the accelerated compression disabled, and then retry \\nthe operation.
-1689773242	5	5	The migration cannot be performed because T10 PI setting values differ between the \\nspecified source volume and target volume.\\nApply the same T10 PI setting to both volumes, and then retry the operation.
-1662279639	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662279607	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662279576	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662279575	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662249663	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662248886	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662248885	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662248857	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247926	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247925	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247924	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247923	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247922	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247921	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247920	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247919	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247918	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1662247896	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-1656706275	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1656706273	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1656706242	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1656706211	5	3	The Storage Navigator is busy.\\nWait for a while, then retry the operation.
-1656706210	5	3	The Storage Navigator is busy.\\nWait for a while, then retry the operation.
-1656706209	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1656706176	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1656646692	1	4	A time-out error occurred. \\nIf the problem persists despite retrying, please call the HSSC.
-1593976557	5	5	The pair operation cannot be performed due to either of the following reasons:\\n- The specified primary volume is used by Universal Replicator.\\n- A storage system that does not support the specified pair configuration is included.\\nRemove the storage system that does not support the specified pair configuration, \\nor specify a different volume, and then retry the operation.
-1593976535	5	5	The pair operation cannot be performed due to either of the following reasons:\\n- The specified secondary volume is used by Universal Replicator.\\n- A storage system that does not support the specified pair configuration is included.\\nIf the Create Pairs operation cannot be performed, take the following action:\\n- If the remote storage system is in a 2DC configuration in which Universal Replicator \\nis combined with TrueCopy, wait until the status of the Universal Replicator pair \\nchanges to PAIR, and then retry the operation.\\n- If the remote storage system is not in a 2DC configuration, specify a different \\nvolume for the secondary volume, and then retry the operation.\\n- If one of the storage systems does not support the specified pair configuration, \\nremove the storage system, and then retry the operation. If the Resync Pairs operation \\ncannot be performed, restore the Universal Replicator pair first, and then retry \\nthe operation.
-1593976533	5	5	The Create Pairs operation cannot be performed because the specified secondary volume \\nis a LUSE volume that is set across multiple CLPRs.\\nSpecify a different volume for the secondary volume.
-1593976435	5	5	A pair cannot be created, because you tried to create a volume pair formed with a \\nvolume to which VMA is set by Data Retention Utility and a volume without VMA.\\nCheck to ensure that you did not mistakenly attempt to create a volume with or without VMA.
-1593976434	5	5	A pair cannot be created using the specified primary volume because the setting process \\nof VMA that is used for Data Retention Utility is not yet complete.\\nWait for a while, then retry the operation.
-1593976433	5	5	A pair cannot be created using the specified secondary volume because the setting \\nprocess of VMA that is used for Data Retention Utility is not yet complete.\\nWait for a while, then retry the operation.
-1593975480	5	0	The storage system is in internal process. Please retry the operation. \\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-1593975479	5	5	The operation cannot be performed because the licensed capacity of Data Retention \\nUtility on the remote storage system is not enough or Data Retention Utility is not \\ninstalled on the remote storage system.\\nVerify the licensed capacity of Data Retention Utility on the remote storage system \\nor if Data Retention Utility is installed on the remote storage system. To perform \\nthis operation, purchase a license key that allows you to use a larger capacity or \\ninstall Data Retention Utility on the remote storage system.
-1593975477	5	5	The operation cannot be performed because the licensed capacity of Data Retention \\nUtility on the remote storage system is not enough or Data Retention Utility is not \\ninstalled on the local storage system.\\nVerify the licensed capacity of Data Retention Utility on the local storage system \\nor if Data Retention Utility is installed on the local storage system. To perform \\nthis operation, purchase a license key that allows you to use a larger capacity or \\ninstall Data Retention Utility on the local storage system.
-1593975450	5	5	The specified primary volume is already used as a primary volume for Universal Replicator.\\nSpecify a different volume, or create the Universal Replicator pair again using a \\nmirror ID other than 0, and then retry the operation.
-1593975353	5	0	A pair cannot be created because the specified primary volume is being used by Thin Image.\\nSpecify another volume.
-1593975352	5	5	A pair cannot be created because the specified secondary volume is being used by \\nThin Image or Copy-on-Write Snapshot.\\nSpecify another volume.
-1593975351	5	5	A pair cannot be created because the specified primary volume is a virtual volume.\\nSpecify another volume.
-1593975350	5	5	A pair cannot be created because the specified secondary volume is a virtual volume.\\nSpecify another volume.
-1593975349	5	5	A pair cannot be created because the specified primary volume is being used as a \\npool volume.\\nSpecify another volume.
-1593975348	5	5	A pair cannot be created because the specified secondary volume is being used as \\na pool volume.\\nSpecify another volume.
-1593974666	5	5	A communication time-out error occurred between the local storage system and the \\nremote storage system.\\nWait a while, then retry the operation.
-1593974481	5	5	A pair cannot be created because the specified primary volume is being shredded by \\nData Retention Utility.\\nVerify that the shredding is complete, and then retry the operation.
-1593974480	5	5	A pair cannot be created because the specified secondary volume is being shredded \\nby Data Retention Utility.\\nVerify that the shredding is complete, and then retry the operation.
-1593974421	5	5	The operation cannot be performed because the specified volume cannot be used as \\na secondary volume due to a host setting.\\nVerify whether the specified volume number is correct or the usage status of the \\nhost for the specified secondary volume.
-1593972720	5	5	The licensed capacity of TrueCopy on the remote storage system is not enough.\\nVerify the licensed capacity of TrueCopy, and then purchase a license key that allows \\nyou to use a larger capacity.
-1593972718	5	5	The licensed capacity of TrueCopy on the local storage system is not enough.\\nVerify the licensed capacity of TrueCopy, and then purchase a license key that allows \\nyou to use a larger capacity.
-1593138481	5	6	The operation cannot be performed because a configuration change is in progress in \\nthe local storage system.\\nWait until the configuration change performed by Command Control Interface or Volume \\nMigration and so on is complete, and then retry the operation.
-1593055927	5	0	The operation cannot be performed because the specified primary volume is being used \\nas a Dynamic Provisioning volume.\\nVerify the primary volume setting, and then retry the operation.
-1593055926	5	0	The operation cannot be performed because the specified secondary volume is being \\nused as a Dynamic Provisioning volume.\\nVerify the setting of the specified secondary volume, and then retry the operation.
-1593055897	5	0	The setting of Maximum Initial Copy Activities (CU) cannot be changed to Enable or \\nDisable, because there are pairs in the  COPY or Pending status.\\nConfirm that no pairs are in COPY or Pending status, then retry the operation.
-1593055895	5	0	The specified primary volume is used as a pair volume of Universal Replicator. The \\noperation cannot be performed because Disaster Recovery Extended is not installed \\non the local storage system.\\nInstall Disaster Recovery Extended on the local storage system.
-1593055894	5	0	The specified secondary volume is used as a pair volume of Universal Replicator. \\nThe operation cannot be performed because Disaster Recovery Extended is not installed \\non the remote storage system.\\nInstall Disaster Recovery Extended on the remote storage system.
-1593055890	5	0	The operation cannot be performed because the remote storage system does not support \\nthe CU or the LUN ID of the specified primary volume.\\nVerify the CU or the LUN ID of the specified primary volume.
-1593049070	5	0	The pair cannot be created because the specified secondary volume, which is a Dynamic \\nProvisioning volume, is already used by a different program product.\\nSelect a different volume that is not used by different program products or cancel \\nthe use of the volume operated by different program products, and then retry the \\noperation.
-1593049069	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nsecondary volume is a system disk.\\nSelect a different volume or release the setting of a system disk for the secondary \\nvolume, and then retry the operation.
-1593048977	5	0	The operation failed because the TrueCopy function was not installed.\\nInstall the TrueCopy function to the storage system.
-1593048975	5	0	The pair cannot be created because the TrueCopy function is not installed on the \\nremote storage system.\\nInstall the TrueCopy function on the remote storage system.
-1593048952	5	0	The operation cannot be performed because the specified volume is not a secondary volume.\\nVerify the setting of the specified volume and then retry the operation.
-1593048950	5	0	The Reverse Resync operation failed because the status of the specified volume was not SSWS.\\nRefresh the window, and confirm whether the status of the specified volume is SSWS.
-1593048948	1	0	The operation cannot be performed. The shared memory might not be enough.\\nSee the manual to verify the condition for this operation.
-1593048947	5	0	The operation failed. The operation cannot be accepted in the pair status of the \\nspecified volume.\\nRefresh the window, and confirm the pair status of the specified volume.
-1593048238	5	0	A pair cannot be created because the specified secondary volume is a Dynamic Provisioning \\nvolume whose capacity is being changed.\\nWait until the capacity change of the secondary volume is complete, verify each capacity \\nof the primary volume and the secondary volume, and then make a combination of volumes \\nfor pair creation again.
-1593048237	5	0	A pair cannot be created because the specified primary volume is a Dynamic Provisioning \\nvolume whose capacity is being changed.\\nWait until the capacity change of the primary volume is complete, verify each capacity \\nof the primary volume and the secondary volume, and then make a combination of volumes \\nfor pair creation again.
-1593048234	5	0	A pair cannot be created because the specified volume is used as a primary volume \\nof Universal Replicator.\\nThe specified volume is a primary volume of Universal Replicator used in the 2DC \\nconfiguration in which TrueCopy is combined. Select a different volume.
-1593048203	5	0	The operation failed, because the Universal Volume Manager function was not installed.\\nInstall the Universal Volume Manager, then retry the operation.
-1593048202	1	0	The operation failed, because there was an error in the specified parameter.\\nIf the problem persists despite retrying, please call the HSSC.
-1593048143	5	0	The operation cannot be performed because the specified primary volume is a volume \\nof Dynamic Provisioning in the zero page reclamation.\\nWait until the zero page reclamation on the specified volume is complete, and then \\nretry the operation.
-1593048142	5	0	The operation cannot be performed because the specified secondary volume is a volume \\nof Dynamic Provisioning in the zero page reclamation.\\nWait until the zero page reclamation on the specified volume is complete, and then \\nretry the operation.
-1593048141	5	0	The operation cannot be performed because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the primary volume is being initialized.\\nWait until the pool initialization is complete, and then retry the operation.
-1593048140	5	0	The operation cannot be performed because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the secondary volume is being initialized.\\nWait until the pool initialization is complete, and then retry the operation.
-1593048051	1	0	The operation failed, because the specified volume was defined in the LU path.\\nSee the manual to verify the condition for this operation.
-1593048045	1	0	The operation failed, because the specified volume was a pool volume.\\nSelect another volume, or release the pool volume setting.
-1593048023	1	0	The operation failed, because the specified volume was used for Volume Migration.\\nSelect another volume, or release the Volume Migration setting.
-1593047987	5	0	The operation cannot be performed because the other program product is specified \\nfor the TrueCopy pair.\\nConfirm the program product of the specified pair.
-1593047240	5	0	The operation cannot be performed because the specified remote storage system supports \\nonly the remote path of the system.\\nSelect the remote paths of the system, and then retry the operation.
-1592241659	5	5	The I/O operation with the host connected via iSCSI is in progress.\\nStop the I/O operation, and then retry the operation.
-1592221775	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-1592221742	5	0	The specified port cannot be used because you do not have permission to access a \\nresource group to which the port belongs.\\nVerify the resources allocation for the user with security administrator role.
-1592221741	5	0	The operation cannot be performed because the port belonging to a resource group \\nthat you do not have permission to access is used by the remote path of the local \\nstorage system.\\nVerify the resources allocation for the user with security administrator role.
-1592221718	5	0	The operation cannot be performed because the specified port or the port that is \\nused by the remote path of the local storage system belongs to a resource group that \\nyou do not have permission to access.\\nVerify the resources allocation for the user with security administrator role.
-1592213790	5	5	Some entries are not valid.\\nIf this problem persists, contact the HSSC.
-1592181148	5	5	The CHB for iSCSI is not mounted.\\nVerify the selected port ID, and then retry the operation.
-1592181125	5	5	The firmware exchange is in progress on the storage system.\\nWait until the firmware exchange is complete, and then retry the operation.
-1592181124	1	5	The specified port is blocked.\\nRestore the blocked status of the port, and then retry the operation. If the blocked \\nstatus cannot be restored, contact the HSSC.
-1592132437	5	0	The operation cannot be performed because the current DKCMAIN firmware version does \\nnot support the capacity of the specified primary volume.\\nVerify the DKCMAIN firmware version of the local storage system.
-1592132436	5	0	The operation cannot be performed because the current DKCMAIN firmware version does \\nnot support the capacity of the specified secondary volume.\\nVerify the DKCMAIN firmware version of the remote storage system.
-1592132246	5	0	The operation cannot be performed because no CHB is mounted or all CHBs are blocked \\non the remote storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-1592131406	5	0	The operation cannot be performed because the specified primary volume is an external \\nvolume that is mapped for the online data migration and its cache mode is set to Through.\\nPerform either of the following operations:\\n- Specify a volume other than the external volume that is mapped for the online data \\nmigration.\\n- Change the cache mode of the volume specified as the primary volume.
-1592131384	5	0	The operation cannot be performed because the specified secondary volume is an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration.
-1592131377	5	0	The operation cannot be performed because the combination of the models of the local \\nstorage system and the remote storage system is not supported.\\nVerify the models of the local storage system and the remote storage system.
-1592130291	5	0	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 \\nsystem and the remote storage system.\\n- The DKCMAIN firmware version of the local storage system or the remote storage \\nsystem does not support a pair creation by using these models.\\n\\nSee the user guide and verify whether the combination of the models of the local \\nstorage system and the remote storage system is supported. If it is supported, take \\na note of the DKCMAIN firmware versions of both the local storage system and the \\nremote storage system, and then contact the HSSC.
-1592130290	5	0	The specified serial number or the controller ID is invalid.\\nCheck the specified serial number and the controller ID.
-1571785743	5	5	An internal logic error occurred.\\nContact the Hitachi Data Systems Support Center.
-1571785742	5	5	The specified volume cannot be used because it is write-protected by Data Retention Utility.\\nRelease the write-protection by the Data Retention Utility.
-1571785650	5	5	The capacities of the volumes specified as the primary volume and the secondary volume \\ndo not match.\\nSpecify volumes with the same capacity.
-1571783825	5	5	This operation has been rejected.\\nThe Data Retention Utility setting does not allow the specified volume(s) to be specified \\nas S-VOL(s).\\nChange the setting of Data Retention Utility so that the specified volumes can be \\nused as S-VOLs.
-1571756978	5	5	Processing in progress. Please wait for a while, and then retry the operation.\\nWait for a while, and then retry the operation.
-1571756977	5	5	The target volume status is being changed to SMPL.\\nWait for a while, and then retry the operation.
-1571756918	5	5	The command has been rejected, because the specified volume was registered in the \\nSecurity Group that cannot specify T-VOL(Secondary Volume).\\nPerform either of the following operations:\\n- Change the attribute of the security group so that the secondary volume can be \\nspecified.\\n- Remove the specified volume from the security group.
-1571756880	5	5	The setting could not be applied because there is an error in a different setting.\\nVerify the error factor in another setting and then retry the operation.
-1571729080	5	5	This error code is not registered.\\nIf this problem persists, contact the HSSC.
-1571702202	5	5	A time-out error occurred.\\nVerify the status of the controller, and then retry the operation.
-1571697398	5	5	Sufficient amount of shared memory is not installed or \\nthe program product is not installed.\\nAdd shared memory or confirm whether the necessary program product key is installed.
-1571697397	5	5	The command has been rejected, because the command specified last time is being processed.\\nWait for a while, and then retry the operation.
-1571697395	5	5	You cannot create the new pair, because a remote copy pair exists in the same storage \\nsystem frame.\\nDelete the Remote Copy pair.
-1571697394	5	5	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 \\nfor the command.\\n- A pair operation is performed on some pairs of one-to-multiple volumes or L1 and \\nL2 pairs at the same time.\\nTake either of the following actions, and then retry the operation.\\n- See the ShadowImage User Guide to verify the pair configuration or status, or the \\nvolume status.\\n- Perform the pair operation respectively on the pairs of one-to-multiple volumes \\nor the L1 and L2 pairs.
-1571697393	1	1	The command cannot be run because the pair operation cannot be performed in the current \\npair status, or because there is a pair operation that cannot be performed if it \\nis done on some pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.\\nSee the ShadowImage User Guide for the relation between the pair status and the operation \\nthat can be performed.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1571697392	5	5	The command cannot be run because the specified secondary volume is used by the host.\\nVary the secondary volume offline from the host, and then retry the operation.
-1571697391	5	5	The Pairsplit (Split Pairs) command was issued to the pairs in a PSUS status.\\nThe Pairsplit command cannot be run because the pair is already in the PSUS status.
-1571697390	5	5	The Paircreate (Create Pairs) command was issued to the pairs in the PSUS status.\\nThe Paircreate command cannot be run because the pair is already in the PSUS status.
-1571697389	5	5	The Pairsplit (Split Pairs) command with the QUIESCE specification was issued to \\na secondary boot device.\\nVerify the settings, and then retry the operation.
-1571697367	5	5	The P-VOL Suspend command was issued to a secondary boot device.\\nVerify the settings, and then retry the operation.
-1571697365	5	5	Cannot perform Pairresync (Resync Pairs) or Pairsplit-E (Suspend Pairs) operation \\nbecause of the path group setting.\\nDetach the S-VOL from the host, or delete the Remote Copy path.
-1571697364	5	5	The command could not be executed because the specified primary volume is used by the host.\\nRun the vary offline command to disable the primary volume from the mainframe host, \\nand then retry the operation.
-1571697361	5	5	The number of P-VOL cylinders exceeds the maximum.\\nVerify the settings, and then retry the operation.
-1571697360	5	5	The number of S-VOL cylinders exceeds the maximum.\\nVerify the settings, and then retry the operation.
-1571697359	5	5	You cannot create a pair because the track format is different.\\nCheck if the specified emulation type is the same or not.
-1571697358	5	5	The capacities of the volumes specified as the primary volume and the secondary volume \\ndo not match.\\nSpecify volumes with the same capacity.
-1571697336	5	5	The pair cannot be created because the volume types are different.\\nSelect volumes with the same emulation type, and then retry the operation.
-1571697335	5	5	The number of multiple copy jobs exceeded the maximum.\\nVerify the settings, and then retry the operation.
-1571697334	5	5	The emulation type of the P-VOL is not supported.\\nSpecify the emulation type supported in HOMRCF.
-1571697333	5	5	The emulation type of the S-VOL is not supported.\\nSpecify the emulation type supported in HOMRCF.
-1571697331	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697330	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697329	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697328	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697327	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697305	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697304	1	1	An internal logic error occurred.\\nContact the HSSC.
-1571697303	5	5	The command has been rejected, because the P-VOL or the S-VOL is being used by the host.\\nStop the usage by the host.
-1571697300	1	1	A processor failure was detected.\\nContact the HSSC.
-1571697299	1	1	A cache failure was detected.\\nContact the HSSC.
-1571697298	1	1	The cache capacities do not match.\\nContact the HSSC.
-1571697297	1	1	An SM failure was detected.\\nContact the HSSC.
-1571697296	1	1	There is not enough shared memory on the local storage system to create 4096 pairs.\\nThe shared memory on the local storage system is not enough. Contact the HSSC.
-1571697274	1	1	There is sufficient shared memory to create 4096 pairs, but initial storage system \\nsetup is required before creating pairs.\\nContact the HSSC.
-1571697273	3	5	There is sufficient shared memory to create 4096 pairs, and the initial storage system \\nsetup is complete.\\nClose the message box.
-1571697272	1	1	Failed to complete the initial shared memory setup.\\nContact the HSSC.
-1571697271	1	1	The shared memory size is different.\\nContact the HSSC.
-1571697270	3	5	16 Mbytes of shared memory is available.\\n-
-1571697269	1	1	A power supply failure is detected.\\nContact the HSSC.
-1571697268	5	5	The command was rejected.  The PS OFF is in progress.\\nRetry the operation with power ON.
-1571697267	1	1	A data transfer failure is detected (CHA).\\nContact the HSSC.
-1571697266	1	1	A data transfer failure is detected (DKA).\\nContact the HSSC.
-1571697265	5	5	The P-VOL is not implemented.\\nOperations cannot be performed on unconfigured volumes.
-1571697243	1	1	The command could not be executed because the specified primary volume is blocked \\nor used as a system disk.\\nRestore the blocked volume, or select a volume that is not a system disk, and then \\nretry the operation.
-1571697242	5	5	The primary volume is being formatted or shredded.\\nWait until the volume is formatted, and then retry the operation. 
-1571697241	5	5	This volume cannot be specified as an P-VOL because it is used as a command device.\\nCheck the target volume.
-1571697240	5	5	The S-VOL is not implemented.\\nOperations cannot be performed on unconfigured volumes.
-1571697239	5	5	The command could not be executed because the specified secondary volume is blocked \\nor used as a system disk.\\nRestore the blocked volume, or select a volume that is not a system disk, and then \\nretry the operation.
-1571697238	5	5	The secondary volume is being formatted or shredded.\\nWait until the volume is formatted, and then retry the operation.
-1571697237	5	5	This volume cannot be specified as an S-VOL because it is used as a command device.\\nA volume that is not used as a command device shall be specified as an S-VOL.
-1571697236	5	5	The volume is not implemented.\\nOperations cannot be performed on unconfigured volumes.
-1571697234	5	5	The volume is being formatted.\\nWait until the volume is formatted, and then retry the operation. 
-1571697212	5	5	This volume cannot be specified because it is used as a command device.\\nSpecify a volume that is not used as a command device.
-1571697203	5	5	The command cannot be run because the area of the differential table or the pair \\ntable to set pairs is not enough.\\nSee the ShadowImage User Guide or the Thin Image User Guide for the relation between \\nthe number of pairs that can be created and the shared memory.
-1571697181	5	5	The selected volume does not exist.\\nRefresh the window, and then retry the operation.
-1571697179	5	5	The volume is already defined as a P-VOL.\\nCheck the status of the volume.
-1571697178	5	5	The volume is defined as a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571697177	5	5	The volume is defined as a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571697148	5	5	The emulation type of the target volume is being changed.\\nWait for a while, and then retry the operation.
-1571697147	5	5	The RAID level of the specified volume is not supported.\\nSpecify a volume of the supported RAID level.
-1571697144	5	5	The number of groups that can be set in the same storage system is invalid.\\nVerify the settings, and then retry the operation.
-1571697143	5	5	The number of pairs that can be set in the same group is invalid.\\nVerify the settings, and then retry the operation.
-1571697142	5	5	The specified group number is not set.\\nVerify the settings, and then retry the operation.
-1571697141	5	5	The specified group name is invalid.\\nVerify the settings, and then retry the operation.
-1571697119	5	5	The group name and the number do not match.\\nVerify the settings, and then retry the operation.
-1571697118	5	5	The specified pair is already set in another group.\\nVerify the settings, and then retry the operation.
-1571697117	5	5	The command was rejected because the licensed capacity was exceeded.\\nCheck the capacity of the installed license key. To create more pairs, purchase a \\nlicense key for larger capacity.
-1571697116	5	5	The P-VOL is a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571697115	5	5	The P-VOL is a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571697114	5	5	The specified P-VOL does not exist.\\nRefresh the window, and then retry the operation.
-1571697112	5	5	No more pairs can be created with the specified primary volume.\\nSee the ShadowImage User Guide or the Thin Image User Guide for the pair configuration.
-1571697111	5	5	The specified volume is not a P-VOL.\\nCheck the status of the volume.
-1571697110	5	5	The specified volume is already used as a primary volume.\\nSelect a different volume, and then retry the operation, or release the pair of the \\nselected volume, and then retry the operation.
-1571696437	5	5	The specified volume is already used as a primary volume.\\nSelect a volume of the supported RAID level, and then retry the operation.
-1571696436	5	5	The specified S-VOL (Primary Volume) cannot be paired with a backup server volume.\\nVerify the settings, and then retry the operation.
-1571696435	5	5	The command has been rejected, because the specified P-VOL has already been used \\nas S-VOL of the other pair.\\nThe volume used as S-VOL of the other pair cannot be used as P-VOL.
-1571696434	1	1	The target volume is set as a primary volume for Data Migration.\\nPlease delete a Data Migration pair.
-1571696433	1	1	The target volume is set as a secondary volume for Data Migration.\\nPlease delete a Data Migration pair.
-1571696432	5	5	The Pairresync (Resync Pairs) command was issued to a device in the SMPL status.\\nCheck the pair status.
-1571696431	5	5	The operation to create an L2 pair was rejected because the P-VOL of the L1 pair \\nis used as the P-VOL of a TrueCopy pair.\\nWhen the P-VOL of the L1 pair is used as a P-VOL of a TrueCopy pair, the L2 pair \\ncannot be created.
-1571696430	5	5	The command cannot be run because the specified secondary volume is used as a primary \\nvolume of a TrueCopy pair.\\nSee the ShadowImage User Guide for the relation between the pair status of TrueCopy \\nand the ShadowImage operations. See the Thin Image User Guide for the relation between \\nthe pair status of TrueCopy and the Thin Image operations.
-1571696429	5	5	The specified S-VOL is not defined.\\nRefresh the window, and then retry the operation.
-1571696406	5	5	The S-VOL is a target volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571696405	5	5	The operation failed because the specified S-VOL was used as S-VOL of other pairs.\\nSpecify another volume.
-1571696404	5	5	The specified volume is not an S-VOL.\\nCheck the status of the volume.
-1571696403	5	5	The RAID level of the specified T-VOL(Secondary Volume) is not supported.\\nSpecify a volume of the supported RAID level.
-1571696402	5	5	The T-VOL(Secondary Volume) is used as a Remote Copy M-VOL.\\nThe requested command cannot be executed in the current TrueCopy pair status. See \\nthe ShadowImage User Guide for the relation between the TrueCopy pair statuses and \\nthe ShadowImage operations.
-1571696401	5	5	The T-VOL(Secondary Volume) is used as a Remote Copy R-VOL.\\nSpecify a different volume.
-1571696400	1	1	The T-VOL(Secondary Volume) is used as a primary volume for Data Migration.\\nPlease delete a Data Migration pair.
-1571696399	1	1	The target T-VOL(Secondary Volume) is used as a secondary volume for Data Migration.\\nPlease delete a Data Migration pair.
-1571696398	5	5	The T-VOL(Secondary Volume) is already defined as an S-VOL(Primary Volume).\\nCheck the volume number.
-1571696397	5	5	The specified T-VOL(Secondary Volume) is defined as a source volume for Volume Migration.\\nRelease the Volume Migration setting.
-1571696371	5	5	The command has been rejected, because there is no pair to be operated.\\nVerify if the specified P-VOL and S-VOL are correct.
-1571696370	5	5	The P-VOL(S-VOL) and S-VOL(T-VOL) have the same number.\\nCheck the specified volume number.
-1571696369	5	5	The SMPL command could not be executed because the quick split operation is in progress.\\nWait until the quick split operation is complete, and then retry the operation.
-1571696368	5	5	The Pairresync operation has been rejected, because pair status is COPY(SP)/COPY.\\nWait until the status of the pair changes to PSUS.
-1571696367	5	5	The operation of the L1 pair failed because the L2 pair was in COPY(SP)/COPY status \\nor PSUS(SP)/COPY status.\\nWait until the L2 pair status changes to PSUS, and then retry the operation.
-1571696343	5	5	The specified CU number is invalid.\\nContact the HSSC.
-1571696342	1	1	The timing of issuing the command is invalid.\\nContact the HSSC.
-1571696341	1	1	The abnormal status is invalid.\\nContact the HSSC.
-1571696337	5	5	The specified P-VOL is used as a source volume for Volume Migration.\\nSpecify other volume(s), or release the Volume Migration Setting.
-1571696336	5	5	The command could not be executed because the specified primary volume is set for \\nuse in Cache Residency Manager.\\nRelease the Cache Residency Manager setting, or select a different volume, and then \\nretry the operation.
-1571696335	5	5	The command could not be executed because the specified secondary volume is set for \\nuse in Cache Residency Manager.\\nRelease the Cache Residency Manager setting, or select a different volume, and then \\nretry the operation.
-1571696313	5	5	The command cannot be run because there is a pair in the status of Reverse Copy or \\nQuick Restore among pairs that share a primary volume, or because there is a pair \\noperation that cannot be performed if it is done on some pairs of one-to-multiple \\nvolumes or L1 and L2 pairs at the same time.\\nWait until the Reverse Copy or Quick Restore operation is complete, and then retry \\nthe operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1571696312	5	5	The L1 pairs contain a pair in the Reverse Copy or Quick Restore status.\\nWait until the Reverse Copy or Quick Restore operation is complete, and then retry \\nthe operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1571696311	5	5	The command has been rejected, because the specified S-VOL is shared as the P-VOL \\nof the other pair and the pair is in the COPY(RS-R)/RCPY status.\\nWait until the status of the pair sharing the primary volume  becomes PAIR, and then \\nretry the operation. See the section "Operations permitted for L1, L2 pairs" in the \\nShadowImage User Guide for the relation between the status of pairs and ShadowImage \\noperations.
-1571696310	5	5	The Resync Pairs operation cannot be performed because the specified pair is not \\nin the PSUS status. Or the command cannot be run because there is a pair operation \\nthat cannot be performed if it is done on some pairs of one-to-multiple volumes or \\nL1 and L2 pairs at the same time.\\nSee the section "Pair resynchronization" in the ShadowImage User Guide for the relation \\nbetween the pair status and the ShadowImage operations.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1571696309	5	5	The operation failed because the pairs sharing a P-VOL contain a pair in other than \\nPSUS or PSUE status.\\nVerify the status of the pairs that share the P-VOL.
-1571696308	5	5	The Reverse Copy command could not be executed because the primary volume was shared \\nwith the primary volume of a remote replication pair.\\nRelease the remote replication pair, and then retry the operation.
-1571696307	5	5	The Reverse Copy request was rejected, because the P-VOL was shared with a Remote \\nCopy pair in the non-suspend status.\\nDelete the Remote Copy pair.
-1571696306	5	5	The Reverse Copy command could not be executed because the secondary volume was shared \\nwith the primary volume of a remote replication pair.\\nRelease the remote replication pair, and then retry the operation.
-1571696305	5	5	The boot device and the P-VOL do not match in the Paircreate (Create Pairs) command.\\nCheck the specified volume number.
-1571696304	5	5	Because the boot device is the S-VOL in the Pairsplit-S (Delete Pairs) command, the \\nflag does not match.\\nCheck the specified volume number.
-1571696282	5	5	The boot device and the P-VOL do not match in the Paircreate (Create Pairs), Pairresync \\n(Resync Pairs), or Pairsplit-S (Delete Pairs) command.\\nCheck the target volume number.
-1571696281	5	5	The SSID is invalid.\\nVerify the settings, and then retry the operation.
-1571696280	5	5	The boot device is not a P-VOL nor S-VOL.\\nCheck the target volume number.
-1571696279	5	5	Because the boot device is the P-VOL in the Pairsplit-S (Delete Pairs) command, the \\nflag does not match.\\nCheck the target volume number.
-1571696278	5	5	Boot device and S-VOL do not match in Paircreate (Create Pairs), Pairresync (Resync \\nPairs), or Pairsplit-S (Delete Pairs) instruction.\\nCheck the target volume number.
-1571696277	5	5	An invalid secondary SSID is specified for the Paircreate (Create Pairs) or Pairresync \\n(Resync Pairs) command.\\nVerify the settings, and then retry the operation.
-1571696276	5	5	The secondary SSID specified for the Pairsplit-S(Delete Pairs) or Pairsplit(Split \\nPairs) command is invalid.\\nVerify the settings, and then retry the operation.
-1571696275	1	1	The Swap&Freeze option cannot be specified, because the mode 80 is on.\\nPlease call the HSSC.
-1571696153	5	5	The specified MU number is not less than or equal to 2.\\nCorrect the MU number, and then retry the operation.
-1571696152	5	5	The command has been rejected, because the specified S-VOL(Primary Volume) is being \\nused as a volume of a Compatible FlashCopy(R) V2 pair or a Compatible Software for \\nIBM(R) FlashCopy(R) SE pair.\\nDelete the Compatible FlashCopy(R) V2 pair or Compatible Software for IBM(R) FlashCopy(R) \\nSE pair, or specify another volume.
-1571696151	5	5	The command has been rejected, because the specified T-VOL(Secondary Volume) is being \\nused as the volume of a Compatible FlashCopy(R) V2 pair a Compatible Software for \\nIBM(R) FlashCopy(R) SE pair.\\nDelete the Compatible FlashCopy(R) V2 pair or Compatible Software for IBM(R) FlashCopy(R) \\nSE pair, or specify another volume.
-1571696150	5	5	The command could be executed because the specified volume is being used as a volume \\nof a Compatible FlashCopy(R) V2 pair or a Compatible Software for IBM(R) FlashCopy(R) SE pair.\\nDelete the Compatible FlashCopy(R) V2 pair or Compatible Software for IBM(R) FlashCopy(R) \\nSE pair, or specify another volume.
-1571696149	5	5	The command of Reverse Copy or Quick Restore has been rejected, because the specified \\nS-VOL(Primary Volume) is being shared with the volume of a Compatible FlashCopy(R) \\nV2 pair or a Compatible Software for IBM(R) FlashCopy(R) SE pair.\\nDelete the Compatible FlashCopy(R) V2 pair or Compatible Software for IBM(R) FlashCopy(R) \\nSE pair, or specify another volume.
-1571693492	5	5	The operation on the L2 pair cannot be performed because the L1 pair is not in the \\nPSUS status. Or the command cannot be run because there is a pair operation that \\ncannot be performed if it is done on some pairs of one-to-multiple volumes or L1 \\nand L2 pairs at the same time.\\nWait until the L1 pair changes to the PSUS status, and then retry the operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1571693429	1	1	Failed to make or cancel a reservation of consistency group.\\nRefresh the window, and then verify the status of the consistency group.
-1571693424	5	5	A pair status cannot be changed because the Split time of Consistency Group is set.\\nReset the Split time of Consistency Group from the mainframe host.
-1571693274	5	5	The command has been rejected, because the Compatible FlashCopy(R) V2 relationship exists.\\nWithdraw the Compatible FlashCopy(R) V2 relationship.
-1571693273	1	1	The command has been rejected, because sufficient amount of shared memory is not \\ninstalled.\\nInstall additional shared memory.
-1571693272	1	1	The command has been rejected, because the shared memory is not set for Compatible \\nFlashCopy(R) V2.\\nSet the shared memory extension setting for Compatible FlashCopy(R) V2.
-1571693271	5	5	The command has been rejected, because the storage system is busy.\\nWait for a while, and then retry the operation.
-1571693270	5	5	The command has been rejected, because the Compatible FlashCopy(R) V2 relationship exists.\\nWithdraw the Compatible FlashCopy(R) V2 relationship.
-1571693269	5	5	The command has been rejected, because the storage system is busy.\\nWait for a while, and then retry the operation.
-1560696290	5	5	The specified volume cannot be used as a quorum disk because the capacity of the \\nvolume is not enough.\\nSee the user guide to verify the capacity necessary for the quorum disk.
-1560696289	5	5	The specified volume is not an external volume.\\nSpecify a external volume.
-1560696288	5	5	A LUN path is set to the specified volume.\\nDelete the LUN path of the specified volume, or specify a different volume.
-1560696287	5	5	Two or more LDEVs are set in the parity group to which the specified volume belongs.\\nSpecify a volume that belongs to the parity group consisting of an LDEV.
-1560696286	5	5	The specified volume is a journal volume.\\nSpecify a different volume.
-1560696285	5	5	The specified volume is a command device.\\nSpecify a different volume.
-1560696284	5	5	A virtual LDEV ID is set on the specified volume.\\nDelete the virtual LDEV ID of the specified volume, or specify a different volume.
-1560696283	5	5	The specified volume is not a quorum disk, or the specified quorum disk ID is not \\nregistered.\\nVerify the settings.
-1560696282	5	5	The specified quorum disk is in internal process.\\nWait for a while, and then retry the operation.
-1560696260	5	5	The operation cannot be performed because the specified quorum disk is used by a \\nglobal-active device pair.\\nDelete all of the global-active device pairs using the specified quorum disk, and \\nthen retry the operation.
-1560696259	5	5	Shared memory required for the specified operation is not installed on the local \\nstorage system.\\nSee the manual to verify the detailed requirements for this operation.
-1560696258	1	0	The operation failed, because there was an error in the specified parameter.\\nVerify the settings, and then retry the operation with the correct parameter. If \\nthis problem persists, contact the HSSC.
-1560696257	5	5	The specified remote path cannot be used for global-active device.\\nSpecify the remote paths of the system, and then retry the operation.
-1560696256	5	5	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\\nVerify the status of the cache and the shared memory on the local storage system. \\nif the cache or the shared memory is blocked, contact the HSSC. If it is not, wait \\nfor a few minutes, and then retry the operation.
-1560696255	5	5	The operation cannot be performed because the specified primary volume is an external \\nvolume that is mapped for the online data migration.\\nSpecify a different volume.
-1560696254	5	5	The pair status of the primary volume is not valid for the specified operation.\\nVerify the pair status. If the pair is in operable status, retry the operation.
-1560696253	5	0	The operation cannot be performed because the provisioning type of the volume that \\nis selected as the primary volume is not supported.\\nSee the user guide to verify the supported provisioning types.
-1560696252	5	5	The operation cannot be performed because the specified primary volume is a reserved \\nvolume of global-active device.\\nRelease the reserved volume setting, or specify a different volume.
-1560696251	5	5	The specified primary or secondary volume is used by Thin Image. The operation cannot \\nbe performed due to one of the following reasons:\\n- The status of the Thin Image pair is invalid for being shared with a global-active \\ndevice pair.\\n- The attribute of the Thin Image pair is invalid for being shared with a global-active \\ndevice pair.\\n\\nWait until the status transition of the Thin Image pair is complete, and then retry \\nthe operation, or specify a different volume. See the global-active device User Guide \\nfor the relation between the Thin Image pair and the global-active device pair.
-1560696229	5	5	No virtual LDEV ID is set in the specified primary volume.\\nSet a virtual LDEV ID in the specified volume.
-1560696228	5	5	The specified secondary volume cannot be used.\\nVerify if the secondary volume is in any of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in the correction access condition.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.
-1560696227	5	5	The vendors of the local storage system and the remote storage system do not match.\\nConnect a remote storage system of the same vendor as the local storage system.
-1560696226	5	0	The operation cannot be performed because the provisioning type of the volume that \\nis selected as the secondary volume is not supported.\\nSee the user guide to verify the supported provisioning types.
-1560696225	5	5	The specified primary volume and secondary volume are on the same storage system.\\nSpecify a volume on the storage system other than the specified local storage system \\nfor the secondary volume.
-1560696224	5	5	The operation cannot be performed because the specified secondary volume is not a \\nreserved volume of global-active device.\\nSet the reservation attribute on the volume, or specify a different volume.
-1560696223	5	5	The operation cannot be performed because different versions of DKCMAIN firmware \\ncoexist on the storage system.\\nUpdate the DKCMAIN firmware, and then retry the operation.
-1560696222	5	5	A virtual LDEV ID is set on the specified secondary volume.\\nRelease the virtual LDEV ID in the specified volume.
-1560696221	5	5	The specified operation cannot be performed because the pair operation that the local \\nstorage system has accepted is not complete.\\nWait until the pair status of the specified volume becomes available, and then retry \\nthe operation.
-1560696220	5	5	The operation cannot be performed because the specified volume is changing to the \\nSuspend status due to failure.\\nVerify the pair status, wait until the volume changes to the Suspend status, and \\nthen restore the volume.
-1560696198	5	5	Shared memory required for the specified operation is not installed on the remote \\nstorage system.\\nSee the manual to verify the detailed requirements for this operation.
-1560696197	5	5	The emulation type of the secondary volume is not supported.\\nSee the user guide to verify whether the emulation type of the specified volume is \\nsupported.
-1560696196	5	5	The specified primary or secondary volume is used by ShadowImage. The ShadowImage \\npair volume in the current pair status or pair attribute cannot be shared by a global-active \\ndevice pair.\\nSee the user guide to verify the pair status or pair attribute that allows the volume \\nto be shared by a global-active device pair.
-1560696195	5	5	The remote storage system does not support global-active device.\\nVerify the model and the microcode version of the remote storage system.
-1560696194	5	5	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.\\nSpecify a different volume.
-1560696193	5	5	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\\nVerify that the secondary volume is in usable condition, and then retry the operation.
-1560696192	5	5	The pair status of the secondary volume is not valid for the specified operation.\\nVerify the pair status of the secondary volume.
-1560696191	5	5	Global-active device is not installed on the remote storage system.\\nInstall the required program product.
-1560696190	5	5	The capacities of the primary and secondary volumes do not match.\\nSpecify a different volume for the primary volume or the secondary volume.
-1560696189	5	5	This function is not available. Resource Partition Manager is required.\\nInstall the necessary program product license key.
-1560696167	5	5	Resource Partition Manager is not installed on the remote storage system.\\nInstall the necessary program product license key.
-1560696166	5	5	The operation cannot be performed because the pool associated with the Dynamic Provisioning \\nvolume 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\\nWait until the pool initialization is complete, and then retry the operation. Or, \\nwait until the capacity expansion is complete, and then verify the capacity of the \\nspecified volume.
-1560696165	5	5	The operation cannot be performed because the pool associated with the Dynamic Provisioning \\nvolume 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\\nWait until the pool initialization is complete, and then retry the operation. Or, \\nwait until the capacity expansion is complete, and then verify the capacity of the \\nspecified volume.
-1560696164	5	5	The I/O mode setting of the specified secondary volume is not valid for the specified \\noperation.\\nVerify the I/O mode setting of the specified secondary volume.
-1560696163	5	5	The I/O mode setting of the specified primary volume is not valid for the specified \\noperation.\\nVerify the I/O mode setting of the specified primary volume.
-1560696162	5	5	The operation cannot be performed because the specified primary or secondary volume \\nis 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\\nVerify the pair status and the I/O mode setting of the specified primary or secondary \\nvolume. If the I/O mode setting is not Local, delete the pair by specifying Delete \\nPair by Force.
-1560696161	5	5	The specified primary or secondary volume is used by TrueCopy. The TrueCopy pair \\nvolume in the current pair status or pair attribute cannot be shared by a global-active \\ndevice pair.\\nSee the user guide to verify the pair status or pair attribute that allows the volume \\nto be shared by a global-active device pair.
-1560696160	5	5	The specified primary or secondary volume is used by Universal Replicator. The Universal \\nReplicator pair volume in the current pair status or pair attribute cannot be shared \\nby a global-active device pair.\\nSee the user guide to verify the pair status or pair attribute that allows the volume \\nto be shared by a global-active device pair.
-1560696159	5	5	Global-active device is not installed on the remote storage system.\\nInstall the required program product.
-1560696158	5	5	The virtual LDEV ID same as that set on the specified primary volume is defined on \\na virtual storage machine on the remote storage system.\\nSpecify a different primary volume, or release the definition of the virtual LDEV \\nID on the virtual storage machine on the remote storage system.
-1560696136	5	5	The specified primary volume is used by a global-active device pair.\\nSpecify a different volume.
-1560696135	5	5	The specified secondary volume is used by a global-active device pair.\\nSpecify a different volume.
-1560696134	5	5	The attribute (primary or secondary) of the specified volume is not valid for the \\nspecified operation.\\nVerify the specified operation and the attribute of the specified volume.
-1560696133	5	5	The attribute (primary or secondary) of the other paired volume of the specified \\nvolume is not valid for the specified operation.\\nVerify the specified operation and the attribute of the other paired volume.
-1560696132	5	5	The pair status of the primary or secondary volume is not valid for the specified \\noperation.\\nVerify the pair status of the primary or secondary volume.
-1560696131	5	0	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 \\ncondition.\\n- The quorum disk is not accessible.\\n- The pair is changing to the Suspend status.\\n\\nIf this message is displayed when creating pairs, verify that the specified remote \\nstorage system is the same as the one that has been specified to add the quorum disk.\\nIf the quorum disk or the connection path between the quorum disk and the storage \\nsystem is blocked, restore the disk or the path first, and then retry the operation.\\nIf the pair status is changing to Suspend, wait until the status of all pairs using \\nthe quorum disk change to Suspend, and then retry the operation. If the problem is \\nnone of the above, just retry the operation.
-1560696130	5	0	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 \\ncondition.\\n- The quorum disk is not accessible.\\n- The pair is changing to the Suspend status.\\n\\nIf this message is displayed when creating pairs, verify that the specified remote \\nstorage system is the same as the one that has been specified to add the quorum disk.\\nIf the quorum disk or the connection path between the quorum disk and the storage \\nsystem is blocked, restore the disk or the path first, and then retry the operation.\\nIf the pair status is changing to Suspend, wait until the status of all pairs using \\nthe quorum disk change to Suspend, and then retry the operation. If the problem is \\nnone of the above, just retry the operation.
-1560696129	5	5	The operation cannot be performed because the serial numbers or models of the virtual \\nstorage machines of the specified primary and secondary volumes do not match.\\nVerify the serial numbers or the models.
-1560696128	5	5	The setting information of Data Retention Utility on the primary volume cannot be \\ntransmitted because Data Retention Utility is not installed on the remote storage system.\\nInstall Data Retention Utility on the remote storage system.
-1560696127	5	5	The operation cannot be performed because the specified secondary volumes is used \\nas a global-active device pair volume.\\nSpecify a different volume.
-1560696105	5	5	The operation cannot be performed because the specified primary volume is a command device.\\nSpecify a different volume.
-1560696104	5	5	The operation cannot be performed because the specified secondary volume is a command device.\\nSpecify a different volume.
-1560696103	5	5	The operation cannot be performed because the access attribute of Data Retention \\nUtility has been changed.\\nSpecify a different volume.
-1560696101	5	5	The operation cannot be performed because the selected volume access for the volume \\nin the COPY status is not valid.\\nTo delete volumes in the COPY status, select the volume access as follows:\\n- Enable for the primary volume.\\n- Disable for the secondary volume.
-1560696100	5	5	The operation cannot be performed because the pair volume on the remote storage system \\nis used by ShadowImage.\\nDelete the ShadowImage pair, and then retry the operation.
-1560696099	5	5	The operation cannot be performed because the pair volume on the remote storage system \\nis used by Thin Image.\\nDelete the Thin Image pair, and then retry the operation.
-1560696098	5	0	The operation cannot be performed because the current firmware version does not support \\nconsistency groups.\\nVerify the firmware version of the local storage system.
-1560696097	5	0	The operation cannot be performed because the firmware version of the remote storage \\nsystem does not support consistency groups.\\nVerify the firmware version of the remote storage system.
-1560696096	5	0	The operation cannot be performed because a different pair operation is being performed \\non volumes that belong to the specified consistency group.\\nWait until the pair operation being performed on the consistency group is complete, \\nand then retry the operation.
-1560696074	5	0	The operation cannot be performed because a different pair operation is being performed \\non the consistency group that contains the specified volume.\\nWait until the pair operation being performed on the consistency group is complete, \\nand then retry the operation.
-1560696073	5	0	The operation cannot be performed because a different pair operation is being performed \\non the specified consistency group.\\nWait until the pair operation being performed on the consistency group is complete, \\nand then retry the operation.
-1560696072	5	0	The operation cannot be performed because the specified volume or its paired volume \\nis used by Universal Replicator.\\nDelete the Universal Replicator pair, and then retry the operation.
-1560696071	5	0	The operation cannot be performed because a different pair operation is being performed \\non the consistency group to which the specified pair belongs.\\nWait until the pair operation being performed on the consistency group is complete, \\nand then retry the operation.
-1560696070	5	0	The operation cannot be performed because pairs in the specified consistency group \\nare changing to the Suspend status due to failure.\\nWait until all of the pairs in the consistency group change to the Suspend status \\ndue to failure, and then retry the operation.
-1560696069	5	0	The operation cannot be performed because the entered consistency group number is \\nnot valid.\\nEnter the correct consistency group number, and then retry the operation.
-1560696068	5	0	The operation cannot be performed because the number of pairs in the specified mirror \\nexceeds the maximum.\\nVerify the number of pairs in the specified mirror.
-1560696067	5	0	The operation cannot be performed because the combination of the specified consistency \\ngroup number and quorum disk ID is different from the existing combination.\\nSpecify the existing combination of the consistency group number and quorum disk \\nID, and then retry the operation.
-1560696066	5	0	The operation cannot be performed because the combination of the specified consistency \\ngroup number and mirror ID is different from the existing combination.\\nSpecify the existing combination of the consistency group number and mirror ID, and \\nthen retry the operation.
-1560696065	5	0	The operation with a consistency group specified cannot be performed because the \\npair configurations in the consistency group have changed.\\nRetry the operation on  the GAD Pairs tab in the Remote Replication window.
-1560696043	5	0	The operation with a  volume specified cannot be performed because the pair configurations \\nin the consistency group have changed.\\nRetry the operation on the GAD Consistency Groups tab in the Remote Replication window.
-1560696042	5	0	The operation cannot be performed because an invalid relation is detected between \\nthe consistency group number and the volume number.\\nClick the refresh button to have the latest information displayed on the window, \\nand then retry the operation.
-1560696041	5	0	The operation cannot be performed because the I/O mode differs between the specified \\nglobal-active device pair and the global-active device pairs in the consistency group.\\nSet the same I/O mode for all of the pairs in the consistency group.
-1560696040	5	0	The operation cannot be performed because the following requirements are not met.\\n- The primary volume of a global-active device pair is the primary volume of a Universal \\nReplicator pair.\\n- The secondary volume of a global-active device pair is the primary volume of a \\ndelta resync pair of Universal Replicator.\\n\\nVerify the pair configurations of global-active device, Universal Replicator, and \\nUniversal Replicator delta resync.
-1560696039	5	0	The operation cannot be performed because the firmware version of the remote storage \\nsystem does not support the provisioning type of the volume selected as the secondary volume.\\nVerify the firmware version of the remote storage system.
-1560696038	5	0	The operation cannot be performed because the Provisioning type or the attribute \\ndiffers between the primary volume and the secondary volume.\\nSelect volumes with the same Provisioning type and attribute as the primary volume \\nand the secondary volume.
-1560696037	5	0	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.\\nWait for a while, and then retry the operation. If the problem persists, contact the HSSC.
-1560696036	5	0	The operation cannot be performed because the specified external volume is not formatted.\\nPerform LDEV formatting, and then retry the operation.
-1560696035	5	0	The operation cannot be performed because the specified external volume is not accessible.\\nVerify the following conditions.\\n- The selected external volume is in normal status.\\n- The volume of the external storage system is in normal status.\\n- The external path is in normal status.\\nRestore all abnormal states back to normal, and then retry the operation.
-1560696034	5	5	The operation cannot be performed because any of the specified parameters is not valid.\\nVerify the specified LDEV number and mirror ID of the primary volume, and then retry \\nthe operation with the correct parameter.
-1560696012	5	5	The operation cannot be performed because the specified primary or secondary volume \\nis used by Volume Migration.\\nSpecify a different volume.
-1560696011	5	0	The operation cannot be performed because the number of LUN paths set for the other \\npaired volume exceeds the maximum that is available for ALUA.\\nReduce the number of LUN paths set for the other paired volume, or disable the ALUA \\nmode of the selected volume.
-1560696010	5	0	The operation cannot be performed because the specified volume is an external volume \\nwith Data Direct Mapping enabled.\\nSpecify a different volume.
-1560696009	5	0	The operation cannot be performed because Data Direct Mapping is enabled on the specified \\nprimary volume but the remote storage system does not support Data Direct Mapping.\\nThe Data Direct Mapping setting must be the same on the primary volume and the secondary \\nvolume. Update the DKCMAIN firmware on the remote storage system to a version that \\nsupports Data Direct Mapping.
-1560696007	5	0	The operation cannot be performed because T10 PI is set for the selected volume.\\nSpecify a different volume.
-1560696005	5	0	The operation cannot be performed because the storage system is in the process of \\nsetting ALUA.\\nWait for a while, and then retry the operation.
-1560696004	5	0	Swap suspending with pairs specified cannot be performed because the selected pairs \\nbelong to a consistency group.\\nPerform the suspending operation on the consistency group on the GAD Consistency \\nGroups tab in the Remote Replication window.
-1560696003	5	0	One or more of the LDEVs set as the specified quorum disks belong to a resource group \\nthat you do not have permission to access.\\nAsk the administrator to provide permission.
-1560695330	5	0	The value that is set for Read Response Guaranteed Time When Quorum Disk Blocked \\nis outside the available range.\\nVerify the setting.
-1560695329	5	0	The operation cannot be performed because the specified quorum disks do not exist.\\nCreate quorum disks, and then retry the operation.
-1560695328	5	0	The current DKCMAIN firmware version does not support this operation.\\nUpdate the DKCMAIN firmware on the local storage system to a version that supports \\nthe quorum disk edit function.
-1560691417	5	0	The operation cannot be performed because the T10 PI setting differs between the \\nprimary volume and the secondary volume.\\nSpecify volumes with the same T10 PI setting as the primary volume and the secondary volume.
-1480747485	5	5	The command was rejected because you tried to create a pair with a volume to which \\nVMA is set by Data Retention Utility and a volume without VMA.\\nYou cannot create a pair with these volumes. If you want to create a pair, you must \\nuse the volumes to both of which VMA is set or not.
-1480746713	5	5	You cannot create the pair because the licensed capacity of Data Retention Utility \\nis insufficient.\\nIncrease the licensed capacity of Data Retention Utility, and then retry the operation.
-1480743702	5	5	Quick Restore cannot be performed because the specified pair is composed of the external \\nvolumes with different cache mode settings.\\nUse the Reverse Resync option.
-1480660224	5	5	The command has been rejected because the cascade request for creating cascade pairs \\ncomposed of volumes belonging to the same consistency group was issued.\\nSelect a different volume or release the consistency group setting.
-1480660223	5	5	The operation on the L2 pair cannot be performed because the L1 pair is in the COPY(SP)/COPY, \\nPSUS(SP)/COPY, or COPY(RS-R)/RCPY status. Or the command cannot be run because there \\nis a pair operation that cannot be performed if it is done on some pairs of one-to-multiple \\nvolumes or L1 and L2 pairs at the same time.\\nWait until the L1 pair changes to the PSUS or PAIR status, and then retry the operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1480660222	5	5	The Quick Restore command has been rejected because the specified pair is composed \\nof a normal volume and a customized volume (CV).\\nThe quick restore operation cannot be performed when the pair is composed of a normal \\nvolume and a customized volume (CV). Select a different pair.
-1480660221	5	5	The command has been rejected because a Remote Copy pair exists in the same storage \\nsystem frame.\\nTo continue the operation, delete the remote copy pair.
-1480658138	5	5	The Quick Restore command could not be executed because the specified pair contains \\nexternal volumes and also is used as a remote replication pair.\\nDelete the remote replication pair or perform the operation on other pairs.
-1480658116	5	5	The command was rejected because the specified P-VOL is used as a P-VOL of a TrueCopy pair.\\nThe requested command cannot be executed in the current TrueCopy pair status. See \\nthe ShadowImage User Guide for the relation between the TrueCopy pair statuses and \\nthe ShadowImage operations.
-1480658115	5	5	The command has been rejected, because the specified P-VOL is used as S-VOL of TrueCopy pair.\\nThe requested command cannot be executed in the current status of TrueCopy pair. \\nSee the section "Sharing ShadowImage volumes" in the ShadowImage User Guide for the \\nrelation between the state of TrueCopy pair and the ShadowImage operations.
-1480658114	3	5	A pair cannot be created because shared memory for differential tables is in sufficient.\\nAdd sufficient shared memory to create a pair.
-1480658014	5	5	The operation failed because the specified P-VOL was a data volume of Universal Replicator. \\nCheck the requirements for using the volume with Universal Replicator.\\nCheck the requirements for using the volume with Universal Replicator.
-1480657341	5	5	The operation failed, because the specified S-VOL was a data volume of Universal \\nReplicator.\\nRelease the Universal Replicator setting or specify another volume.
-1480657185	5	5	The Quick Restore command could not be executed because the specified pair contains \\nexternal volumes, and also is used as a Universal Replicator pair.\\nDelete the Universal Replicator pair, or perform the operation on a different pair.
-1480657180	5	5	The command was rejected because the specified volume is used by the Universal Replicator \\nand the TrueCopy.\\nRelease the pair of Universal Replicator or the pair of TrueCopy, and then retry \\nthe operation.
-1480656224	5	5	The storage system is busy (internal processing).\\nIf the problem persists despite retrying, please call the HSSC.
-1480656157	5	5	The operation cannot be performed, because the specified P-VOL is a P-VOL for Thin Image.\\nRelease the Thin Image pair, or select another volume.
-1480656156	5	5	The operation cannot be performed, because the specified P-VOL is an S-VOL or a V-VOL \\nfor Thin Image.\\nSpecify a different volume.
-1480656155	5	5	The operation cannot be performed, because the specified P-VOL is a pool volume.\\nRelease the pool volume or select another volume.
-1480656154	5	5	The operation cannot be performed because the specified secondary volume is a primary \\nvolume of ShadowImage or Thin Image.\\nDelete the ShadowImage pair or the Thin Image pair, or select a different volume.
-1480656132	5	5	The operation cannot be performed, because the specified S-VOL is an S-VOL or a V-VOL \\nfor Thin Image.\\nSpecify a different volume.
-1480656131	5	5	The operation cannot be performed, because the specified S-VOL is a pool volume.\\nRelease the pool volume or select another volume.
-1480655380	5	5	The operation failed, because the Thin Image pair(s) existed.\\nTo continue the operation, delete all Thin Image pair(s) and retry.
-1480655379	5	5	The operation failed, because the Thin Image pair(s) existed.\\nTo continue the operation, delete all Thin Image pair(s) and retry.
-1480655357	1	1	The operation failed, because different versions of microcodes coexisted in the storage system.\\n\\nReplace the microcode, and then retry the operation.
-1480655323	5	5	The operation failed, because the specified P-VOL was a journal volume.\\nRelease the journal volume setting, or specify another volume.
-1480655322	5	5	The operation failed, because the specified S-VOL was a journal volume.\\nRelease the journal volume setting, or specify another volume.
-1480655320	5	5	The operation could not be performed because the specified secondary volume is a \\nUniversal Replicator volume.\\nCheck the requirements for using the volume with Universal Replicator.
-1480655193	5	5	The operation could not be performed because the specified volume is being shredded \\nby Data Retention Utility.\\nVerify that the shredding is complete in the Data Retention Utility window, and then \\nretry the operation.
-1480655169	5	5	The command has been rejected, because the specified S-VOL is used as P-VOL of Thin \\nImage or the specified MU number is already used.\\nThe specified command cannot be executed with the current pair composition. See the \\nsection about the Interoperability with other products and functions and the ShadowImage \\ndescribed in the Thin Image User Guide for the condition of sharing the volumes between \\nThin Image and ShadowImage.
-1480655168	5	5	The operation failed because the volume was shared by a Thin Image pair.\\nTo continue the operation, release the Thin Image setting.
-1480655167	5	5	The operation failed because the volume was shared by a Thin Image pair in COPY (RS-R)/RCPY status.\\nCheck the conditions for using ShadowImage in conjunction with Thin Image.
-1480655166	5	5	The operation failed because the CU group of the specified volume is not supported.\\nVolumes that do not belong to CU group 0 are currently not supported. Specify another volume.
-1480654365	5	5	The operation cannot be performed because the specified primary volume is used by \\na delta resync pair of Universal Replicator.\\nSee the ShadowImage User Guide for the relation between the pair status of Universal \\nReplicator and the ShadowImage operations. See the Thin Image User Guide for the \\nrelation between the pair status of Universal Replicator and the Thin Image operations.
-1480654364	5	5	The operation failed because the specified S-VOL was used by Delta resync of Universal \\nReplicator.\\nThe P-VOL of Universal Replicator pair for Delta resync cannot be specified as S-VOL. \\nSpecify another volume.
-1480653465	5	5	The operation could not be performed because the specified MU number is already used.\\nRefresh the ShadowImage window, and check the MU number that can be used.
-1480651569	5	5	The operation failed because the volume specified as the P-VOL was used as the S-VOL \\nof another pair and the volume specified as the S-VOL was used as the P-VOL of another \\npair already.\\nVerify the pair configurations. See the ShadowImage User Guide for the relation between \\nthe configuration and the operation of pairs.
-1479736640	5	5	"0" cannot be specified as the MU number of L2 pair.\\nSpecify other MU numbers.
-1479729876	5	5	The command has been rejected, because the specified P-VOL is a Dynamic Provisioning \\nvolume not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, and then retry the operation.
-1479729875	5	5	The command has been rejected, because the specified S-VOL is a Dynamic Provisioning \\nvolume not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, and then retry the operation.
-1479729849	5	5	The command has been rejected, because Quick Format is performed on the specified P-VOL.\\nRetry the operation after quick formatting is complete.
-1479729848	5	5	The command has been rejected, because Quick Format is performed on the specified S-VOL.\\nRetry the operation after quick formatting is complete.
-1479729847	5	5	Mainframe Fibre Data Migration Source Volume is specified as a T-VOL. Mainframe Fibre \\nData Migration Source Volume cannot be used as a T-VOL.\\nMainframe Fibre Data Migration source volume cannot be used as a T-VOL. Use other volumes.
-1479729846	5	5	The command has been rejected because the pair uses Mainframe Fibre Data Migration \\nSource Volume.\\nThe specified pair cannot be operated because the pair uses Mainframe Fibre Data \\nMigration source volume.
-1479729845	5	5	The command has been rejected because the Mainframe Fibre Data Migration source volume \\nis used in the specified pair, and T-VOL is used by one of the following program products.\\n- TrueCopy for Mainframe\\n- Universal Replicator for Mainframe\\n- Compatible FlashCopy(R) V2\\n- Volume Retention Manager\\nRelease the setting in which the secondary volume is used by different program products, \\nand then retry the operation.
-1479729843	1	1	The command has been rejected, because the specified TrueCopy Asynchronous pair was \\nnot in PSUS status.\\nThe Command cannot be executed because the TrueCopy Asynchronous pair is not in the \\nstate of  PSUS. See the section about the Interoperability with other products and \\nfunctions described in the ShadowImage User Guide for the relation between the state \\nof TrueCopy Asynchronous pair and the ShadowImage operations.
-1479729821	5	5	The Quick Restore command has been rejected, because the specified pair is composed \\nof the Dynamic Provisioning volume and the volumes other than Dynamic Provisioning volume.\\nQuick Restore cannot be performed in the current pair configuration.
-1479729816	5	5	The Quick Restore command has been rejected, because device information (Inquiry \\ninformation) of P-VOL and S-VOL was different in the specified pair.\\nQuick Restore cannot be performed in the current pair configuration. Select a pair \\nwhose device information (Inquiry information) is the same, and then perform Quick Restore.
-1479729790	5	5	Quick Restore cannot be performed because the configuration is being backed up in \\nthe target volume.\\nWait for a while, and then retry the operation.
-1479729783	5	5	The SI Operation for Mainframe Fibre Data Migration failed because the specified \\npair consists of either a primary volume other than a Mainframe Fibre Data Migration \\nsource volume or a secondary volume that is a Mainframe Fibre Data Migration source volume.\\nThe SI Operation for Mainframe Fibre Data Migration cannot be performed in the current \\npair configuration. Select Mainframe Fibre Data Migration source volume for the primary \\nvolume and other than Mainframe Fibre Data Migration source volume for the secondary volume.
-1479729782	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because the pair status \\nof the specified pair was not SIMPLEX or DUPLEX.\\nThe SI Operation for Mainframe Fibre Data Migration cannot be performed in the current \\npair status. Change the status of the pair to SIMPLEX or DUPLEX, and then retry the \\noperation.
-1479729781	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because the pair status \\nof the specified pair was not Suspend(Mig.).\\nThe SI Operation for Mainframe Fibre Data Migration cannot be performed in the current \\npair status. Change the status of the pair to Suspend(Mig.), and then retry the operation.
-1479729759	5	5	The SI Operation for Mainframe Fibre Data Migration failed because the Cache Residency \\nManager for Mainframe setting was set in the T-VOL of the specified pair.\\nRelease the Cache Residency Manager for Mainframe setting in the T-VOL.
-1479729758	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because the Volume Retention \\nManager setting was set in the T-VOL of the specified pair.\\nRelease the Volume Retention Manager setting in the T-VOL or specify another volume, \\nand then retry the operation.
-1479729757	5	5	The SI Operation for Mainframe Fibre Data Migration failed because the T-VOL of the \\nspecified pair was used by Universal Replicator for Mainframe.\\nDelete the Universal Replicator for Mainframe pair, or select a different volume, \\nand then retry the operation.
-1479729756	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because the T-VOL of \\nthe specified pair was used by TrueCopy for Mainframe.\\nDelete the TrueCopy for Mainframe pair or specify another volume, and then retry \\nthe operation.
-1479729755	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because the T-VOL of \\nthe specified pair was used by Universal Volume Manager.\\nUniversal Volume Manager volume cannot be used as a T-VOL. Specify another volume.
-1479729754	5	5	The command could not be executed because the primary volume of the specified pair \\nis a Mainframe Fibre Data Migration source volume.\\nThe specified operation cannot be performed in the current pair configuration. Select \\nvolumes other than Mainframe Fibre Data Migration source volume for the primary volume, \\nand then retry the operation.
-1479729753	5	5	The command could not be executed because the secondary volume of the specified pair \\nis a Mainframe Fibre Data Migration source volume.\\nThe specified operation cannot be performed in the current pair configuration. Select \\nvolumes other than Mainframe Fibre Data Migration source volume for the secondary \\nvolume, and then retry the operation.
-1479729752	5	5	The command has been rejected, because the specified volume is a Mainframe Fibre \\nData Migration Source Volume.\\nThe specified operation cannot be performed for Mainframe Fibre Data Migration source \\nvolume. Select a volume other than Mainframe Fibre Data Migration source volume, \\nand then retry the operation.
-1479729007	5	5	The command was rejected because the specified S-VOL(Primary Volume) was a Dynamic \\nProvisioning for Mainframe volume whose capacity was being added.\\nThe operation is not available because the target volume has capacity changes. Verify \\nthe capacity of the volume, and then apply the setting.
-1479729006	5	5	The command was rejected because the specified T-VOL(Secondary Volume) was a Dynamic \\nProvisioning for Mainframe volume whose capacity was being added.\\nThe operation is not available because the target volume has capacity changes. Verify \\nthe capacity of the volume, and then apply the setting.
-1479728920	5	5	The command has been rejected, \\nbecause the specified CTG is used by Thin Image.\\nUse another CTG, or release the pair of Thin Image where the specified CTG is in use.
-1479728918	5	5	The command has been rejected, because the specified CTG is used by ShadowImage.\\nUse another CTG, or release the pair of ShadowImage where the specified CTG is in use.
-1479728917	5	5	The command could not be executed because the specified primary volume is used by \\na pair of Thin Image that is registered in the CTG.\\nRelease the pair of Thin Image that is using the specified P-VOL, then retry the \\noperation.
-1479728916	5	5	The command has been rejected, \\nbecause the specified S-VOL is used by a pair of Thin Image, which is registered \\nin the CTG.\\nRelease the pair of Thin Image that is using the specified S-VOL, then retry the \\noperation.
-1479728915	5	5	The command has been rejected, because the specified P-VOL is a volume of Dynamic \\nProvisioning whose zero page is being reclaimed.\\nWait until the zero page reclamation is completed, and then retry the operation.
-1479728914	5	5	The command has been rejected, because the specified S-VOL is a volume of Dynamic \\nProvisioning whose zero page is being reclaimed.\\nWait until the zero page reclamation is completed, and then retry the operation.
-1479728856	5	5	The SI Operation for Mainframe Fibre Data Migration failed, because more than one \\nT-VOL was assigned for the specified S-VOL.\\nSpecify the volume not used as S-VOL of SI Operation for Mainframe Fibre Data Migration, \\nor retry the operation after deleting the current pair.
-1479728822	5	5	The command has been rejected, because the volume specified as P-VOL is a quorum disk.\\nSpecify another volume.
-1479728821	5	5	The command has been rejected, because the volume specified as S-VOL is a quorum disk.\\nSpecify another volume.
-1479727990	5	5	The specified P-VOL is a volume of using two mirrors, which are included in 3DC cascade, \\n3DC multi target, or Delta resync configuration. The operation for this P-VOL failed \\ndue to one of the following reasons.\\n- The specified volume was used by Delta resync of Universal Replicator.\\n- The specified volume was used by a data volume of Universal Replicator.\\n\\nThe operation cannot be performed in the current status of Universal Replicator pair. \\nSee the section "Interoperability with other products and functions" in the ShadowImage \\nUser Guide for the relation between the state of Universal Replicator pair and the \\nShadowImage operations.
-1479727989	5	5	The specified secondary volume is a volume of using two mirrors, which is included \\nin the 3DC cascade, the 3DC multi-target, or the delta resync configuration. The \\noperation 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 Universal Replicator.\\n- The specified volume is used by a data volume of Universal Replicator.\\nThe operation cannot be performed in the current status of Universal Replicator pair. \\nSee the section "Interoperability with other products and functions" in the ShadowImage \\nUser Guide for the relation between the state of Universal Replicator pair and the \\nShadowImage operations.
-1479727988	5	5	The specified volume is a volume of using two mirrors, which are included in 3DC \\ncascade, 3DC multi target, or Delta resync configuration. The operation for this \\nvolume failed due to one of the following reasons.\\n- The specified volume was used by Delta resync of Universal Replicator.\\n- The specified volume was used by a data volume of Universal Replicator.\\n\\nSpecify another volume.
-1478902553	5	5	The command was rejected, because the Dynamic Provisioning volume specified as P-VOL \\nwas not associated with a pool.\\nAssociate the specified Dynamic Provisioning volume with a pool, and then retry the \\noperation.
-1478902552	5	5	The command was rejected, because the Dynamic Provisioning volume specified as S-VOL \\nwas not associated with a pool.\\nAssociate the specified Dynamic Provisioning volume with a pool, and then retry the \\noperation.
-1478902550	5	5	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 \\nwith the cascade attribute disabled.\\n- Performing a pair split or pair resync operation on a pair for which the cascade \\nattribute is disabled and whose primary volume has no LUN paths.\\nVerify the statuses of all the specified pairs, or set LUN paths, and then retry \\nthe operation.
-1478902549	5	5	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 \\na 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 \\nwith the cascade attribute disabled.\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing \\na secondary volume for a pair for which the cascade attribute is disabled and whose \\nsecondary volume has no LUN paths.\\nVerify the statuses of all the specified pairs, or set LUN paths, and then retry \\nthe operation.
-1478902547	5	5	The specified operation cannot be performed, because pairs under root volumes are \\nbeing deleted.\\nWait until all of the pairs under the root volumes are deleted, and then retry the \\noperation.
-1478813024	5	5	The operation failed because the current microcode version does not support the capacity \\nof specified P-VOL.\\nCheck the microcode version of the storage system.
-1478813023	5	5	The operation failed because the current microcode version does not support the capacity \\nof specified S-VOL.\\nCheck the microcode version of the storage system.
-1478812987	5	5	The operation failed because the emulation type of the specified S-VOL(Primary Volume) \\nwas 3390-V.\\nSpecify another volume.
-1478812965	5	5	The operation failed because the emulation type of the specified T-VOL(Secondary \\nVolume) was 3390-V.\\nSpecify another volume.
-1478812964	5	5	The operation failed because the emulation type of the specified volume was 3390-V.\\nSpecify another volume.
-1478812963	5	5	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\\nIf no Mainframe Fibre CHA is mounted on the storage system, mount a Mainframe Fibre \\nCHA. If all the Mainframe Fibre CHAs are blocked, restore those Mainframe Fibre CHAs.
-1478812962	5	5	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\\nIf no Mainframe Fibre CHA is mounted on the storage system, mount a Mainframe Fibre \\nCHA. If all the Mainframe Fibre CHAs are blocked, restore those Mainframe Fibre CHAs.
-1478812213	5	5	The command was rejected, because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the P-VOL was being initialized.\\nWait until the initialization of the pool is completed, and then retry the operation.
-1478812212	5	5	The command was rejected, because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the S-VOL was being initialized.\\nWait until the initialization of the pool is completed, and then retry the operation.
-1478812158	5	5	The operation failed because the specified S-VOL(Primary Volume) was used by Compatible \\nSoftware for IBM(R) FlashCopy(R) SE, or was a TSE volume.\\nSelect a different volume.
-1478812157	5	5	The operation failed because the specified T-VOL(Secondary Volume) was a TSE volume.\\nSelect a different volume.
-1478812151	5	5	The operation cannot be performed because the specified volume is in the online data \\nmigration process.\\nSpecify volumes other than those in the online data migration process.
-1478812150	5	5	The operation cannot be performed because the volume specified as the primary volume \\nis in the online data migration process.\\nSpecify volumes other than those in the online data migration process.
-1478812128	5	5	The operation cannot be performed because the volume specified as the secondary volume \\nis a migration volume of nondisruptive migration.\\nSpecify a different volume.
-1478812119	5	5	The operation cannot be done because a pool cannot be used.\\nVerify the status of the specified pool.
-1478812097	5	5	The operation cannot be performed because the specified pool number is not the same \\nas the pool number for the existing pairs.\\nWhen you create multiple Thin Image pairs by specifying two or more secondary volumes \\nto one primary volume, be sure to specify the same pool number as the existing pairs. 
-1478812096	5	5	The operation cannot be done because the specified primary volume is a secondary \\nvolume of Thin Image.\\nRelease the Thin Image pair setting or specify another volume.
-1478812095	5	5	The operation cannot be done because the specified secondary volume is a secondary \\nvolume of Thin Image.\\nRelease the Thin Image pair setting or specify another volume.
-1478812094	5	5	The specified snapshot number is used in another pair of Thin Image.\\nSpecify another snapshot number or release the Thin Image pair setting.
-1478812093	5	5	The operation cannot be done because the license capacity has been exceeded.\\nInstall additional license keys to expand the license capacity of the program product.
-1478812092	5	5	The command cannot be run in the current pair status.\\nRefresh the window, and then retry the operation.
-1478812091	5	5	The command cannot be run because the command previously specified could not be run \\nin the current pair status. Or the command cannot be run because there is a pair \\noperation that cannot be performed if it is done on some pairs of one-to-multiple \\nvolumes or L1 and L2 pairs at the same time.\\nVerify the status of the specified pair.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1478812090	5	5	The operation cannot be performed, because a pool whose pool type is not Thin Image \\nis selected.\\nSelect a pool whose pool type is Thin Image.
-1478812089	5	5	The command was rejected because the specified volume was set unavailable to specify \\nas a secondary volume.\\nRelease the secondary volume unavailable setting, and then retry the operation.
-1478812088	5	5	An error occurred during Thin Image 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 Thin Image is depleted.\\nPerform one of the following, and then retry the operation. \\n-Specify another LDEV number. \\n-Verify the status of the specified pair. \\n-Specify another MU number. \\n-Verify the status of the specified pool. \\n-Verify the license capacity of the Thin Image. \\n-See the section "Planning number of Thin Image pairs" in the Thin Image User Guide \\nfor the relation between the number of pairs that can be created and the shared memories.
-1478812066	5	5	The command was rejected because the program product of ShadowImage was not installed.\\nInstall the necessary program product.
-1478812065	5	5	The command was rejected because the shared memory (FC, TPF, or Extension1) of necessary \\ncapacity was not installed.\\nAdd sufficient shared memory.
-1478812064	5	5	The command was rejected because the shared memory (SS1 or more) of necessary capacity \\nwas not installed.\\nAdd sufficient shared memory.
-1478812063	5	5	The LDEV number that is specified as a primary volume is invalid.\\nSpecify another LDEV number.
-1478812062	5	5	The command was rejected because the emulation type of the specified primary volume \\nwas not OPEN-V.\\nSpecify a volume of supported emulation type.
-1478812061	5	5	The operation cannot be done because the primary volume of Thin Image is used as \\nthe primary volume of TrueCopy, and the pair status of TrueCopy is other than PSUS or PSUE.\\nChange the status of the TrueCopy pair to PSUS or PSUE, and then retry the operation.
-1478812060	5	5	The operation cannot be done because the primary volume of Thin Image is used as \\nthe primary volume of Universal Replicator, and the pair status of Universal Replicator \\nis other than PSUS or PSUE.\\nChange the status of the Universal Replicator pair to PSUS or PSUE, and then retry \\nthe operation.
-1478812059	5	5	The operation cannot be done because a volume is used as the primary volume of Thin \\nImage and the secondary volume of TrueCopy.\\nSelect a different volume.
-1478812058	5	5	The operation cannot be done because the primary volume of Thin Image is used as \\nthe secondary volume of Universal Replicator.\\nSelect a different volume.
-1478812057	5	5	The operation cannot be done because VMA is set for the specified primary volume.\\nVerify the setting of the specified volume.
-1478812035	5	5	The command was rejected because the emulation type of the specified secondary volume \\nwas not OPEN-V.\\nSpecify a volume whose emulation type is supported.
-1478812034	5	5	The operation cannot be done because the specified secondary volume is an external volume.\\nSpecify another volume.
-1478812033	5	5	The operation cannot be done because the specified secondary volume is not a virtual volume.\\nSpecify another volume.
-1478812032	5	5	The command was rejected because the specified secondary volume was used as a primary \\nvolume of Universal Replicator.\\nSpecify another volume.
-1478812031	5	5	The command was rejected because the specified secondary volume was used as a secondary \\nvolume of Universal Replicator.\\nSpecify another volume.
-1478812030	5	5	The command was rejected because the specified volume was set unavailable to specify \\nas a secondary volume.\\nRelease the secondary volume unavailable setting, and then retry the operation.
-1478812029	5	5	The operation cannot be done because VMA is set for the specified secondary volume.\\nVerify the setting of the specified volume.
-1478812028	5	5	The command was rejected because the Max LBA size of the specified primary and the \\nsecondary volumes was different.\\nVerify the Max LBA size of the volume.
-1478812027	5	5	The command was rejected because the number of slots is different between the specified \\nprimary and the secondary volumes. \\nVerify the number of slots of the volume. 
-1478812026	5	5	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 Dynamic Provisioning virtual volume as a secondary volume to create \\na pair with the cascade attribute disabled.\\n- Specifying a Dynamic Provisioning virtual volume as a secondary volume of a pair \\nwith the cascade attribute disabled to assign or change the secondary volume.\\nVerify the statuses of all the specified pairs, or specify different volumes, and \\nthen retry the operation.
-1478812003	5	5	The command was rejected because the specified secondary volume was used as a primary \\nvolume of ShadowImage.\\nSpecify another volume.
-1478812002	5	5	The command was rejected because the specified secondary volume was used as a secondary \\nvolume of ShadowImage.\\nSpecify another volume.
-1478812000	5	5	A pair of Thin Image 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. \\nInstall additional shared memory, or wait until the initializing process is complete \\nand then retry the operation.
-1478811999	5	5	The specified operation cannot be done.\\nContact the HSSC.
-1478811998	5	5	The operation cannot be done because the PSUE option is specified.\\nContact the HSSC.
-1478811997	5	5	The operation cannot be done because a volume is used as the primary volume of Thin \\nImage and the secondary volume of TrueCopy, and the pair status of TrueCopy is COPY.\\nChange the status of the TrueCopy pair to other than COPY, and then retry the operation.
-1478811996	5	5	The operation cannot be done because a volume is used as the primary volume of Thin \\nImage and the secondary volume of Universal Replicator, and the pair status of Universal \\nReplicator is COPY.\\nChange the status of the Universal Replicator pair to other than COPY, and then retry \\nthe operation.
-1478811995	5	5	When the primary volume of Thin Image and the primary volume of ShadowImage  volume \\nshare the volume, the MU number currently used by ShadowImage cannot be specified.\\nSelect a different MU number.
-1478811973	5	5	When the primary volume of Thin Image and the secondary volume of ShadowImage share \\nthe volume, 0 cannot be specified as a MU number of the primary volume for Thin Image.\\nSelect a different MU number.
-1478811972	5	5	The command was rejected because the primary volume of Thin Image and the primary \\nvolume of ShadowImage share a volume, and the pair of ShadowImage was in re-synchronizing \\nprocessing.\\nWait for the status of the ShadowImage pair to change to PAIR, and then retry the \\noperation.
-1478811971	5	5	The command was rejected because the primary volume of Thin Image and the secondary \\nvolume of ShadowImage share a volume, and the pair of ShadowImage was not in the \\nstate of PSUS.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
-1478811970	5	5	The operation cannot be done because the primary volume of Thin Image and the primary \\nvolume of ShadowImage share a volume, and the pair status of ShadowImage is other \\nthan PSUS or PSUE.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
-1478811969	5	5	The operation cannot be done because the primary volume of Thin Image and the secondary \\nvolume of ShadowImage share a volume, and the pair status of ShadowImage is other \\nthan PSUS.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
-1478811968	5	5	The operation cannot be done because the pools or the pool volumes are blocked.\\nRestore the blocked pools or pool volumes, and then retry the operation.
-1478811967	5	5	A Thin Image pair cannot be restored due to one of the following reasons.\\n- Snapshot data of restore target Thin Image pair is being obtained per consistency group.\\n- Snapshot data of another pair whose primary volume is the restore target Thin Image \\nprimary volume is being obtained.\\nWait for a while, and then retry the operation.
-1478811966	5	5	A Thin Image pair with consistency group number specified cannot be created due to \\none of the following reasons. \\n- The specified consistency group number is used by the ShadowImage. \\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 \\nconsistency group.\\nVerify the specified consistency group number.
-1478811965	5	5	The specified consistency group number is invalid.\\nVerify the consistency group number.
-1478811964	5	5	The operation cannot be done because the primary volume of Thin Image and the secondary \\nvolume of TrueCopy asynchronous pair share a volume, and the status of TrueCopy asynchronous \\npair is other than PSUS or PSUE.\\nChange the status of the TrueCopy Asynchronous pair to PSUS, and then retry the operation.
-1478811942	5	5	The operation cannot be done because the specified secondary volume is incorrect.\\nVerify the setting of the specified volume.
-1478811941	5	5	The command was rejected because the program product of Thin Image was not installed.\\nInstall the necessary program product.
-1478811937	5	5	The command was rejected because the primary volume is used as an external volume \\nthat is mapped for online data migration.\\nSelect a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-1478811936	5	5	The command was rejected because the secondary volume is used as an external volume \\nthat is mapped for online data migration.\\nSelect a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-1478811259	5	5	The operation cannot be performed due to one of the following reasons:\\n- With the current DKCMAIN firmware version, a HDP pool cannot be used to store snapshot data.\\n- For the specified pool, Enable is selected for Multi-Tier Pool.\\n- For the specified pool, Enable is selected for Data Direct Mapping.\\nVerify the DKCMAIN firmware version and the software version of Storage Navigator, \\nand then match them up.\\nA pair cannot be created if Enable is set for Data Direct Mapping for the specified pool.\\nIf Enable is set for Multi-Tier Pool, select Disable, and then retry the operation.
-1478811258	5	5	The operation failed because the Thin Image program product is not installed.\\nInstall the Thin Image program product.
-1478811257	5	5	The operation failed because the microcode versions of SVP and DKCMAIN do not match.\\nCheck the microcode versions of SVP and DKCMAIN.
-1478811256	5	5	The operation failed because there are not enough cache management devices.\\nDelete unnecessary external volumes or virtual volumes, and then retry the operation. \\nWhen there is a Thin Image pair, delete all the pairs related to the unnecessary \\nprimary volumes, and then retry the operation. If this problem persists, call the HSSC.
-1478811255	5	5	The operation failed because the capacity of the specified volume exceeds 4 TB.\\nSpecify a volume whose capacity is 4TB or less.
-1478811253	5	5	The operation cannot be performed because there is a pair in the status of Quick \\nRestore among ShadowImage pairs that share a primary volume. Or the command cannot \\nbe run because there is a pair operation that cannot be performed if it is done on \\nsome pairs of one-to-multiple volumes or L1 and L2 pairs at the same time.\\nWait until the Quick Restore operation is complete, and then retry the operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
-1478811252	5	5	The operation failed because the specified pool number is wrong.\\nCheck the pool number.
-1478811229	5	5	A Thin Image pair cannot be created because the consistency group used by the specified \\nsnapshot group is one of the following:\\n- The consistency group number is used by ShadowImage. \\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.\\nVerify the consistency group of the pairs that belong to the snapshot group.
-1478811100	5	5	The operation failed because the volume specified as the S-VOL is a root volume.\\nVerify the status of the volume.
-1478811099	5	5	The operation failed because the volume specified as the S-VOL is a node volume.\\nVerify the status of the volume.
-1478811098	5	5	The operation failed because the volume specified as the P-VOL is a leaf volume.\\nVerify the status of the volume.
-1478811097	5	5	The operation failed because the volume specified as the S-VOL is a leaf volume.\\nVerify the status of the volume.
-1478811096	5	5	The operation failed because the specified P-VOL that uses two mirrors in 3DC cascade, \\n3DC multi target, or Delta resync configuration is in one of the following statuses.\\n- The volume is in the Universal Replicator Delta resync configuration.\\n- The volume is a Universal Replicator data volume.\\nThe operation cannot be performed in the current pair status of Universal Replicator. \\nSee section "Interoperability with other products and functions" in the Thin Image \\nUser Guide for the relation between the pair status of Universal Replicator and the \\nThin Image operations.
-1478811074	5	5	The operation failed because the specified S-VOL that uses two mirrors in 3DC cascade, \\n3DC multi target, or Delta resync configuration is in one of the following statuses.\\n- The volume is in the Universal Replicator Delta resync configuration.\\n- The volume is a Universal Replicator data volume.\\nThe operation cannot be performed in the current pair status of Universal Replicator. \\nSee section "Interoperability with other products and functions" in the Thin Image \\nUser Guide for the relation between the pair status of Universal Replicator and the \\nThin Image operations.
-1478811073	5	5	The command ended abnormally because the specified MU number is out of the range \\nthat can be specified.\\nMake sure the MU number can be specified.
-1478811003	5	5	A Thin Image pair with the CTG mode specified cannot be created because all the consistency \\ngroups have already been defined.\\nCheck the respective consistency group status or create a Thin Image pair without \\nspecifying the CTG mode.
-1478810981	5	5	A Thin Image pair cannot be created because the snapshot ID (MU number) that can \\nbe used for the volume specified as the primary volume is depleted.\\nSelect a different volume.
-1478810980	5	5	A Thin Image pair cannot be created because all the snapshot groups have already \\nbeen defined, or the number of pairs that can be registered in the specified snapshot \\ngroup has exceeded the maximum.\\nCheck the defined snapshot groups or select a different snapshot group.
-1478810979	5	5	A Thin Image pair in which a V-VOL of Dynamic Provisioning is set as the primary \\nvolume cannot be created because the Dynamic Provisioning pool is being initialized.\\nWait until the initialization of the pool is complete, and then retry the operation.
-1478810978	5	5	Failed to create a Thin Image pair because the Dynamic Provisioning pool is being \\ninitialized.\\nWait until the initialization of the pool is complete, and then retry the operation.
-1478810977	5	5	The Add Pair (Paircreate) operation failed because the specified pair type does not \\nmatch the specified pool type.\\nCheck the specified pair type.
-1478810268	5	5	The Thin Image pair operation cannot be performed because all Thin Image pairs that \\nshare the specified primary volume are in PSUE status.\\nChange the status of pairs related to the specified primary volume to enable the \\npair operation, and then retry the operation.
-1284231287	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284231281	5	6	The specified volume is used as a reserved volume of Volume Migration.\\nRelease the reserved volume setting or specify a different volume.
-1284203417	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284203416	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284203415	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284201462	5	5	An emulation type that cannot be added is specified.\\nCheck the emulation type. If you want to change the cache segment size to set the \\nspecified emulation type, please call the HSSC.
-1284201460	5	5	The Disconnect External Storage Systems or the Disconnect External Volumes is not \\nexecuted for the target volume.\\nExecute the Disconnect External Storage Systems or the Disconnect External Volumes, \\nthen retry the operation.
-1284201459	5	5	A pair of TrueCopy is defined.\\nRelease the pair definition, and then retry the operation.
-1284201458	5	5	A pair of ShadowImage or Thin Image is defined.\\nRelease the pair definition, and then retry the operation.
-1284175548	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284175547	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1284142869	5	5	A pair of Universal Replicator is defined.\\nRelease the pair definition, and then retry the operation.
-1284142868	5	5	A volume is defined as a journal volume of Universal Replicator.\\nRelease the journal volume setting for Universal Replicator, and then retry the operation.
-1284142654	5	5	The specified operation cannot be performed because there is not enough memory available \\non the shared memory for the V-VOL management area.\\nInstall the additional shared memory for the V-VOL management area, and then retry \\nthe operation. If the additional shared memory is already installed, the capacity \\nof pools and V-VOLs has reached the maximum. In this case, delete unnecessary pools \\nand V-VOLs, and then retry the operation.
-1284141695	1	5	An error occurred during communication with the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1284141694	1	5	This function is not supported.\\nVerify the microcode versions of the DKCMAIN and the SVP.
-1284141693	1	5	An error occurred during communication with the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1284141692	1	5	An error occurred during communication with the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1284141691	1	5	A communication time-out error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1284140889	5	5	The configuration of Pool VOL is defined.\\nRelease the configuration definition of Pool VOL, then retry the operation.
-1283305720	5	5	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-1283305561	5	5	The specified virtual volume is not mounted.\\nVerify the target virtual volume.
-1283277974	5	5	The number of LDEVs that can be defined in an external volume has exceeded the maximum value.\\nCheck the number of LDEVs.
-1283277973	5	5	Specified ExG has already been used.\\nCheck the setting of ExG.
-1283277972	5	5	The LDKC, CU, and LDEV are not set within the available range.\\nVerify the settings of the specified LDKC, CU, and LDEV.
-1283277971	5	5	Specified LDKC:CU:LDEV has already been used.\\nCheck the setting of LDKC, CU, and LDEV.
-1283277970	5	5	The specified LDEV number has already been assigned to another emulation group within \\nthe range grouped by 32 LDEV numbers.\\nCheck the setting of emulation groups within the range grouped by 32LDEV numbers.
-1283277969	5	5	The specified SSID is already used within a different range grouped by 32 LDEV numbers.\\nVerify the SSID settings.
-1283277968	5	5	The target external volume is blocked or not set within the range of capacity that \\ncan be used.\\nCheck the status and the capacity of target external volume.
-1283277967	5	5	The specified LDEV capacity is not within the available range for creation.\\nVerify the settings of the LDEV capacity.
-1283277942	5	5	Specified CLPR is not mounted.\\nCheck the setting of CLPR.
-1283275922	5	5	The value of SSID is not set within the available range.\\nCheck the value of the specified SSID.
-1283275921	5	5	The specified SSID differs from the one already used within the range grouped by \\n32 LDEV numbers. \\nVerify the SSID settings.
-1283216406	1	2	An internal logic contradiction occurred on the storage system.\\nContact the HSSC.
-1283216405	5	6	Shared memory is not installed.\\nInstall the shared memory.
-1283216404	5	5	The specified operation cannot be performed because there is not enough memory available \\non the shared memory for the V-VOL management area.\\nInstall the additional shared memory for the V-VOL management area, and then retry \\nthe operation. If the additional shared memory is already installed, the capacity \\nof pools and V-VOLs has reached the maximum. In this case, delete unnecessary pools \\nand V-VOLs, and then retry the operation.
-1283216403	5	0	The capacity of the specified DP-VOL is not within the available range for creation.\\nVerify the capacity of the DP-VOL.
-1283216402	5	6	Shared memory is being initialized.\\nWait for a while, and then retry the operation.
-1283216401	5	5	The pool is in an abnormal state.\\nRecover the pool, then retry the operation.
-1283216339	5	5	The number of Dynamic Provisioning volumes that can be made in a single pool has \\nexceeded the maximum.\\nCheck the configuration of the current DP-VOL.
-1283216315	5	5	The storage system is in process to delete DP-VOL.\\nWait for a while, then retry the operation.
-1283215510	5	5	Volume migration or Quick Restore is in progress.\\nWait for the migrating volume or the Quick Restore to be completed, then retry the \\noperation.
-1283215447	1	6	The specified volume is currently used by ShadowImage.\\nWait until the processing of ShadowImage is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-1283215446	1	6	The specified volume is currently used by Thin Image.\\nWait until the processing of Thin Image is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-1283215445	1	6	The specified volume is currently used by Volume Migration or nondisruptive migration.\\nRelease the Volume Migration or nondisruptive migration setting, and then retry the \\noperation. If this problem persists, contact the HSSC.
-1283215444	1	6	The specified volume is currently used by TrueCopy.\\nWait until the processing of TrueCopy is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-1283215443	1	6	The specified volume is currently used by Universal Replicator.\\nWait until the processing of Universal Replicator is complete, and then retry the \\noperation. \\nIf this problem persists, call the HSSC.
-1283215258	5	5	Quorum disks are included in the items to be maintained.\\nRelease the quorum disks, then retry the operation.
-1283215224	5	5	The operation cannot be performed, because pools are blocked on the storage system.\\nContact the HSSC.
-1283214487	5	5	The total capacity of DP-VOLs defined in the specified pool exceeds the value that \\nhad been permitted to the pool.\\nCheck the total capacity of DP-VOLs defined in the specified pool and its pool settings. \\nIf this problem persists, please call the HSSC.
-1282299672	5	6	The specified operation cannot be executed, because the LDEV capacity exceeds the \\nmaximum reserved pool capacity.\\nCheck the specified LDEV capacity, then retry the operation.
-1282299671	5	5	The capacity of the specified LDEV is not within the available range for LDEV expansion.\\nVerify the available range for LDEV expansion, and then retry the operation.
-1282299670	5	6	Failed to expand the V-VOLs, because it took time for the processing. \\nRetry the operation.
-1282299668	5	6	The capacities of the virtual volumes that are being used by the following program \\nproducts cannot be expanded:\\n- ShadowImage\\n- Thin Image\\n- Volume Migration\\n- TrueCopy\\n- Universal Replicator\\n- Global-active device\\nVerify the settings.
-1282299637	5	6	The operation cannot be executed, because the specified logical volume is not a Dynamic \\nTiering volume.\\nCheck the specified logical volume, then retry the operation.
-1282299582	5	5	The specified MP Unit is not mounted.\\nVerify the specified MP Unit.
-1282299546	5	5	Enough cache management devices cannot be allocated to the target volumes.\\nDelete unnecessary volumes, and then retry the operation. When there is a Thin Image \\npair, delete all the pairs related to the unnecessary primary volumes, and then retry \\nthe operation. If this problem persists, call the HSSC.
-1282299544	5	6	The operation cannot be performed because the storage system is in the power-off process.\\nPower on the storage system, and then retry the operation.
-1282299490	5	5	The specified emulation type is different from the emulation type of the selected pool.\\nSpecify the same emulation type as the pool.
-1282299489	5	5	The specified values of CU and pool ID do not follow the rule to create a volume \\nof TSE attribute.\\nSet the values of CU and pool ID to the odd or the even number.
-1282299488	5	5	A TSE-VOL cannot be associated with a pool where the multi tier pool setting is enabled.\\nSpecify a pool where the multi tier pool setting is disabled.
-1282299486	5	5	The storage system is in internal process, or a different user is changing the configuration.\\nWait for a while, and then retry the operation.
-1282299454	5	6	The operation cannot be performed because the specified virtual volume is set to \\nonline from the OS that does not support EAV.\\nSet the specified virtual volume to offline, and then retry the operation.
-1282298430	5	6	The operation cannot be performed because the additional shared memory is  being \\ninstalled.\\nWait until the installation of additional shared memory is complete, and then retry \\nthe operation.
-1282298429	5	6	The specified page range is not valid.\\nSpecify the start page number and the length of the page range within the available \\nrange of the volume.
-1282298428	5	6	The specified page tiering level of the tiering policy is invalid.\\nVerify the specified page tiering level.
-1282297755	5	6	The processing of this page cannot be performed because an error occurred during \\nthe process of a different page.\\nVerify and correct the error in the different setting, and then retry the operation.
-1282297565	5	6	The operation cannot be performed because the monitoring data is changing.\\nWait for a while, and then retry the operation.
-1282297563	5	5	The specified pool is not a Dynamic Provisioning pool.\\nVerify the settings for the specified pool.
-1247088406	5	5	The operation cannot be performed, because the configuration is being changed or \\na different application is in process.\\nWait for a while, and then retry the operation.
-1247088405	5	5	This function is not supported.\\nCheck whether the DKCMAIN firmware version and the Storage Navigator software version \\nare mismatched.
-1247088404	5	5	The specified LDEV with the SLU attribute cannot be deleted because it is bound to \\nan LDEV with the ALU attribute.\\nUnbind the LDEV with the SLU attribute from the LDEV with the ALU attribute, and \\nthen retry the operation.
-1247028824	5	0	The number of LDEVs with the ALU attribute will exceed the maximum.\\nReduce the number of LDEVs with the ALU attribute, and then retry the operation.
-1247028823	5	5	The operation cannot be performed because a virtual LDEV ID is not set for the specified LDEV ID.\\nSet a virtual LDEV ID for the specified LDEV ID, and then retry the operation.
-1247028822	5	5	The specified ALU ID or SLU ID does not exist.\\nVerify the configuration of the LDEV with the ALU attribute or the LDEV with the \\nSLU attribute, specify an existing ALU ID or SLU ID, and then retry the operation.
-1247028821	5	5	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do \\nnot match.\\nSpecify the same virtual LDEV ID as the LDEV ID, and then retry the operation.
-1247028820	5	5	No commands are issued.\\nIf the problem persists despite retrying, please call the HSSC.
-1247028819	5	0	The same IDs are included in the specified ALU IDs or SLU IDs.\\nVerify the ALU IDs or SLU IDs.
-1247028818	5	5	The specified volume cannot be used as an LDEV with the ALU attribute or that with \\nthe SLU attribute because it is used by Compatible PAV.\\nSpecify a different LDEV ID or release the Compatible PAV setting, and then retry \\nthe operation.
-1247028817	5	5	An LDEV with the SLU attribute cannot be created because the specified pool is in \\nshrinking operation.\\nWait until the shrinking operation is complete, and then retry the operation.
-1247028816	5	5	The specified volume is not a virtual volume of Thin Image.\\nSpecify a virtual volume of Thin Image.
-1246909660	5	5	An error occurred during processing.\\nVerify the details of the error.
-1246909659	1	5	An error occurred during SVP processing.\\nContact the HSSC.
-1246909658	5	5	The binding information cannot be acquired because the number of bound LDEVs with \\nthe ALU attribute and the SLU attribute exceeds the maximum that can be operated at once.\\nRetry the operation.
-1246909630	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-1246909629	1	5	This function is not supported.\\nVerify the DKCMAIN firmware version and the Storage Navigator software version., \\nand then get them matched up properly.
-1246879870	5	5	An error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
-1246879869	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879868	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879867	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879866	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879865	5	5	The specified LUN path does not exist.\\nVerify the settings, and then retry the operation.
-1246879864	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879863	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879862	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879861	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879839	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879838	5	5	The snapshot data of the Thin Image pair is not assigned to the virtual volume of \\nThin Image.\\nAssign the snapshot data of the Thin Image pair to the virtual volume of Thin Image, \\nand then retry the operation.
-1246879837	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879836	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879835	1	5	The operation cannot be performed because different microcode versions coexist on \\nthe storage system.\\nContact the HSSC to change the microcode, and then retry the operation.
-1246879808	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879807	1	5	An error occurred on the storage system.\\nContact the HSSC.
-1246879806	5	5	The specified LDEV does not exist.\\nSpecify an existing LDEV ID, and then retry the operation.
-1246879805	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246879746	5	6	The specified volume is currently used by global-active device.\\nRelease the global-active device setting, and then retry the operation. If this problem \\npersists, contact the HSSC.
-1246879745	5	6	The capacity of the specified DP-VOL cannot be expanded because the configuration \\nof the journal volume is changing.\\nWait until the operation on the journal volume is complete, and then retry the operation.
-1246879744	5	5	No LDEVs with the SLU attribute can be created because the specified pools have the \\nData Direct Mapped attribute.\\nVerify the setting for the pools.
-1246878909	1	5	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246878908	1	5	An internal error occurred.\\nContact the HSSC.
-1246878907	5	5	The operation cannot be performed because the specified volume is:\\n- not contained;\\n- not an HDT volume; or\\n- blocked.\\nVerify the volume status and setting, and then retry the operation. If the volume \\nis blocked, restore it, and then retry the operation.
-1246878903	5	5	The operation cannot be performed because any of the specified parameters is not valid.\\nVerify the following settings., and then retry the operation.\\n- Session information\\n- Control information\\n- HDT volume ID\\n- Monitoring data
-1246878902	5	5	Monitoring data is not properly set.\\nMonitoring data must be set in the order in which it is collected from the remote \\nstorage system. For monitoring data over multiple pages, verify the order of pages, \\nand then set the data from the first page. If this problem persists, retry the operation \\nfrom collecting the monitoring data.
-1246878878	5	5	The operation cannot be performed because the specified pool is:\\n- not contained; or\\n- not an HDT pool.\\nVerify the pool status and setting, and then retry the operation.
-1246878877	5	5	The specified pool is not in a state available for operation.\\nVerify the pool status. If the pool is blocked, restore it, and then retry the operation.
-1246878876	5	5	The monitoring data is not set or not valid.\\nSet the monitoring data again.
-1246878847	5	5	The operation cannot be performed because the storage system is in the power-off process.\\nPower on the storage system, and then retry the operation. For monitoring data over \\nmultiple pages, set the data from the first page.
-1246878816	5	5	Monitoring data cannot be collected from or set on the pool to which the specified \\nvolume belongs.\\nVerify the pool status, and then retry the operation. For monitoring data over multiple \\npages, collect or set the data from the first page.
-1246878815	5	5	Monitoring data cannot be collected from or set on the specified volume.\\nVerify the volume status, and then retry the operation. For monitoring data over \\nmultiple pages, collect or set the data from the first page.
-1246878814	5	5	The specified session ID or volume might not be valid, or this function might be \\nperformed on the specified volume by a different processing.\\nVerify whether the session ID and volume are properly specified. If they are correct, \\nwait for three minutes or longer until the session times out, and then retry the \\noperation.
-1246878813	5	5	The processing cannot continue because three minutes or longer have passed since \\nthe last operation.\\nFor monitoring data over multiple pages, collect or set the data from the first page.
-1246878785	5	5	The operation cannot be performed because any of the specified parameters is not valid.\\nVerify the following settings., and then retry the operation.\\n- Session information\\n- Control information\\n- HDT volume ID\\n- Monitoring data
-1246877948	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
-1246876986	5	5	The specified LDEVs do not exist.\\nVerify the settings.
-1246876985	5	5	The specified LDEVs are not Dynamic Provisioning volumes.\\nSpecify Dynamic Provisioning volumes.
-1246876956	5	5	The LDEV ID specified for the pool volume is outside the setting range.\\nVerify the specified LDEV ID of the pool volume.
-1246876954	5	5	The operation cannot be performed because the required number of cache management \\ndevices cannot be allocated.\\nSee the following sections in the Provisioning Guide, and reserve the required number \\nof cache management devices:\\n- Description of cache management devices\\n- Troubleshooting for cache management devices\\nIf the required number of cache management devices is already reserved, contact the HSSC.
-1246876953	5	5	The specified pool ID is outside the setting range.\\nVerify the specified pool ID.
-1246876952	1	5	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.\\nVerify the following items, and then retry the operation:\\n- The pool capacity\\n- The threshold for pool usage\\n- The pool status
-1246876951	5	5	The operation cannot be performed, because deduplication system data volumes have \\nalready been allocated to the specified pools.\\nRelease the allocations of the deduplication system data volumes to the specified \\npools, and then retry the operation.
-1246876950	5	5	Deduplication system data volumes are not allocated to the specified pools.\\nClick the refresh button to display the latest information on the window, and then \\nverify the settings of the specified pools.
-1246876949	5	5	The operation cannot be performed because the preceding operation is being processed.\\nWait for a while, and then retry the operation.
-1246876948	5	5	The operation cannot be performed, because the selected pool is associated with DP-VOLs \\nwhose capacity saving status is Deduplication and Compression.\\nDisable the capacity saving setting for DP-VOLs that are associated with the selected \\npool and whose capacity saving setting is Deduplication and Compression. Verify that \\nthe capacity saving statuses of all DP-VOLs are Disabled and/or Enabled, and then \\nretry the operation.
-1246876947	5	5	The deduplication system data volume cannot be unassigned, because the deduplication \\nrate (%) of the specified pool is greater than 0.\\nDisable the capacity saving setting for DP-VOLs that are associated with the selected \\npool and whose capacity saving setting is Deduplication and Compression. Verify that \\nthe capacity saving status of all DP-VOLs is Disabled or Enabled, and then retry \\nthe operation.
-1246876925	5	5	The specified pool does not exist.\\nClick the refresh button to display the latest information on the window, and then \\nverify the settings.
-1246876924	1	5	The operation cannot be performed because there is not enough installed shared memory.\\nAdd more shared memory.
-1246876923	5	5	The program product required for using the dedupe and compression function is not \\ninstalled.\\nInstall the required program product.
-1246876922	5	5	The specified LDEV ID is already in use.\\nSpecify a different LDEV ID, and then retry the operation.
-1246876919	5	5	The operation cannot be performed, because the deduplication system data volume and \\nthe pool volumes are allocated to different resource groups.\\nAllocate the deduplication system data volume and the pool volumes to the same resource group.
-1246876894	1	5	DP-VOLs cannot be deleted.\\nRetry the operation. If this problem persists, contact the HSSC.
-1246876889	5	5	The specified operation cannot be performed because there is not enough shared memory \\nfor the V-VOL management area.\\nAdd more shared memory for the V-VOL management area, and then retry the operation. \\nIf shared memory for the V-VOL management area has already been added, the capacity \\nof pools and virtual volumes has reached the maximum. In this case, delete unnecessary \\npools and virtual volumes, and then retry the operation.
-1246876863	5	5	The capacity saving setting cannot be enabled, because the full allocation setting \\nis enabled.\\nDisable the full allocation setting, and then retry the operation.
-1246876862	5	5	The deduplication system data volume cannot be allocated, because a pool with the \\ndata direct mapping attribute is specified.\\nDisable the data direct mapping attribute for the specified pool, and then retry \\nthe operation.
-1246876861	5	5	The operation cannot be performed because the SVP software version does not match \\nthe DKCMAIN firmware version.\\nVerify the firmware version of the DKCMAIN and the software version of the SVP.
-1246876860	1	5	An internal error occurred.\\nContact the HSSC.
-1246876859	5	5	The specified operation cannot be performed because the maximum reserved pool capacity \\nis not enough.\\nChange the maximum reserved pool capacity, and then retry the operation.
-1246876858	5	5	The operation cannot be performed, because the multi-tier pool setting of the pool \\nassociated with the specified LDEV is enabled.\\nDisable the multi-tier pool setting of the pool associated with the specified LDEV, \\nand then retry the operation.
-1246876857	5	5	The specified operation cannot be performed, because the cache memory is blocked.\\nIf an error occurred on the storage system or SVP, refer to the manual and perform \\nrecovery. If no such error occurred and the problem persists, contact the HSSC.
-1246876856	5	6	The specified volume is not valid.\\nVerify the LDKC, CU, and LDEV settings.
-1246876855	5	6	The number of DP-VOLs to be set for the storage system exceeds the maximum number \\nof DP-VOLs that can be set for a storage system.\\nRevise the settings, and then retry the operation.
-1246876854	5	5	The specified LDEV ID is already in use.\\nSpecify a different LDEV ID, and then retry the operation.
-1246876831	5	5	The specified LDEV ID is not valid.\\nSpecify an LDEV ID such that the emulation type of all LDEVs in the group of 32 LDEV \\nIDs including the specified LDEV ID is the same.
-1246876829	5	2	An error occurred on the storage system. The configuration might not be consistent.\\nFrom the File menu, click Refresh All to refresh the configuration information.
-1246876827	5	5	The operation cannot be performed because the specified pool is a Thin Image pool.\\nSpecify a Dynamic Provisioning pool.
-1246876825	5	5	The deduplication system data volumes cannot be allocated, because pools for which \\nthe full allocation setting is enabled are specified.\\nDisable Full Allocation for the specified pools, and then retry the operation.
-1246876824	5	5	The capacity saving setting cannot be changed, because the specified LDEV is blocked.\\nRestore the specified LDEV, and then retry the operation.
-1246876823	5	5	The emulation type of the specified LDEV cannot be used.\\nVerify that the specified information is correct.
-1246876801	5	5	The operation cannot be performed, because journal volumes are selected.\\nDelete the setting of the journal volume for the selected DP-VOLs, and then retry \\nthe operation.
-1246876800	5	5	The operation cannot be performed, because the specified LDEV is in a state in which \\nthe capacity saving setting cannot be changed.\\nVerify the capacity saving status of the specified LDEV. The status of the LDEV should \\nbe one of the following:\\n- Enabled\\n- Rehydrating\\nIf the capacity saving status is Rehydrating, wait for a while, and then retry the \\noperation.
-1246876799	5	5	The operation cannot be performed, because DP-VOLs with the data direct mapping attribute \\nenabled are selected.\\nDP-VOLs with the data direct mapping attribute enabled cannot be selected.
-1246876798	5	5	The operation cannot be performed, because the deduplication system data volume of \\nthe pool associated with the selected DP-VOLs is blocked.\\nRestore the deduplication system data volume, and then retry the operation.
-1246876797	5	5	The capacity saving setting for the selected DP-VOLs cannot be changed.\\nPerform the following operations:\\n- If the pool is blocked, see the Provisioning Guide, restore the pool, and then \\nretry the operation.\\n- If shared memory is insufficient, see the Provisioning Guide, resolve the problem, \\nand then retry the operation.\\n- If the multi-tier pool setting is enabled for a pool with which the selected DP-VOLs \\nare associated, disable the setting, and then retry the operation.\\n- In other cases, configuration change processes conflict on the storage system. \\nVerify that no configuration change process is running, click Refresh All in the \\nFile menu, and then retry the operation.
-1246876796	5	5	The operation cannot be performed, because the deduplication system data volumes \\nare selected.\\nDeduplication system data volumes cannot be selected.
-1246876795	5	6	The operation cannot be performed, because one or more MPs are blocked.\\nRestore all blocked MPs, and then retry the operation.
-1246876794	5	5	The operation cannot be performed, because the specified LDEVs belong to "NAS_Platform_System_RSG".\\nMove the selected LDEVs to a different resource group from "NAS_Platform_System_RSG" , \\nand then retry the operation.
-1246876793	5	5	The operation cannot be performed, because the storage system is performing internal \\nprocessing or another user is changing the configuration.\\nWait for a while, and then retry the operation.
-1246876792	5	5	The specified number of the deduplication system data volumes exceeds the maximum \\nnumber that can be specified for a single pool.\\nVerify that the specified information is correct.
-1246876770	5	5	The operation cannot be performed, because the same pool ID was specified more than once.\\nVerify that the specified information is correct.
-1246876769	5	5	The operation cannot be performed, because the specified LDEV is being used as the \\nsource or target volume by Volume Migration.\\nVerify that the specified LDEV is correct, and then retry the operation.
-1246876768	5	5	The operation cannot be performed, because a Quick Restore operation is being performed \\non the specified LDEV.\\nWait until the Quick Restore operation is complete, and then retry the operation.
-1246876020	5	5	The capacity saving setting of the specified LDEVs cannot be changed to Compression \\nor Deduplication and Compression.\\nFor DP-VOLs whose capacity saving status is Deleting Volume:\\nWait until the DP-VOL deletion is complete.\\nFor DP-VOLs whose capacity saving status is Rehydrating:\\nWait until the capacity saving status changes to Disabled, and then retry the operation.\\nIn case there is any DP-VOL whose capacity saving status is Failed:\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Retry the capacity saving setting change.\\n(6) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool, block and \\nformat the selected DP-VOLs, and then retry the operation.
-1246876018	5	5	The capacity saving setting of the selected DP-VOLs cannot be changed, because the \\ncapacity saving status of at least one DP-VOL is any of the following.\\n- Deleting Volume\\n- Failed\\nFor DP-VOLs whose capacity saving status is Deleting Volume:\\nWait until the DP-VOL deletion is complete.\\nIn case there is any DP-VOL whose capacity saving status is Failed:\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Retry the capacity saving setting change.\\n(6) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool, block and \\nformat the selected DP-VOLs, and then retry the operation.
-1246876017	5	5	The capacity saving setting cannot be changed from Deduplication and Compression \\nto Compression for the selected DP-VOLs.\\nDisable the capacity saving setting. Verify that the capacity saving status is Disabled, \\nand then change the capacity saving setting to Compression.
-1246875993	5	5	The mapping information for the specified LDEVs is not correct.\\nContact the HSSC.
-1246875992	5	5	The operation cannot be performed, because a deduplication system data volume is selected.\\nDelete the deduplication system data volume by editing the pool associated with the \\nselected deduplication system data volume.
-1246875871	5	5	The selected DP-VOLs cannot be deleted.\\nContact the HSSC.
-1246875870	5	5	The operation cannot be performed, because the capacity saving setting of the selected \\nDP-VOLs is Disabled.\\nDP-VOLs whose capacity saving setting is Disabled cannot be selected.
-1246875869	5	5	The specified LDEVs cannot be deleted, because the LDEVs are blocked and not formatted.\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Retry the deletion operation.\\n(6) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool, block and \\nformat the selected DP-VOLs, and then retry the operation.
-1246875868	5	5	The operation cannot be performed, because the specified LDEV is in a state in which \\nthe capacity saving setting cannot be changed.\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Retry the deletion operation.\\n(6) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool of the selected \\nDP-VOLs, block and format the DP-VOLs, and then retry the operation.
-1246875867	5	5	The specified LDEVs cannot be bound to an LDEV with the ALU attribute, because the \\nLDEVs are being deleted.\\nSelect different LDEVs.
-1246875864	5	5	The selected LDEVs cannot be expanded, because they are being deleted.\\nSelect different LDEVs.
-1246875863	5	5	The operation cannot be performed, because the used capacity of the pool associated \\nwith the selected DP-VOLs exceeds the depletion threshold.\\nPerform either of the following operations, and then retry the operation.\\n- Add pool volumes to expand the pool capacity.\\n- Perform the zero page reclaiming for DP-VOLs associated with the same pool of the \\nselected DP-VOLs to reduce the pool used capacity.
-1199244722	1	6	The configuration information being set does not match the current configuration \\ninformation.\\nCheck the settings, and then retry the operation.
-1199241845	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199241687	5	6	The specified port is not a fibre port.\\nCheck the setting.
-1199241686	5	6	The specified WWN is not registered.\\nCheck the setting.
-1199241685	5	6	The value of the WWN is not specified or is set to zero.\\nCheck the setting.
-1199241658	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199241653	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199241650	5	6	The specified Group-ID is already registered.\\nCheck the setting.
-1199241627	5	6	The target cannot be set because the number of targets exceeds the maximum that can \\nbe set in a port.\\nCheck the setting.
-1199241624	5	6	The settings of the selected port cannot be changed because the port is connected \\nto a remote storage system or an external storage system.\\nDisconnect the remote storage system or the external storage system, and then retry \\nthe operation.
-1199213975	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199213974	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199213973	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199186106	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199186105	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1199152253	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-1199152252	1	3	This function is not supported.\\nVerify the DKCMAIN firmware version and the Storage Navigator software version.
-1199152251	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-1199152250	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-1199152249	1	3	A communication time-out error occurred in the storage system.\\nIf this problem persists, please call the HSSC.
-1199152190	5	0	The storage system has accepted the request normally, however the processing requires \\nsome time.\\nIf this problem persists, close the windows, verify that the internal processing \\nor the configuration change has been complete, and then retry the operation.  If \\nthe internal processing or the configuration change takes much time to complete, \\ncontact the HSSC.
-1198317177	5	6	The Dynamic Provisioning volume is not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, then retry the operation.
-1197399599	5	6	The selected WWN was registered in a host group.\\nCheck the settings, then retry the operation.
-1197399480	1	6	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
-1197399479	5	6	The setting process has not been executed because there is no error in this setting, \\nbut an error in the other settings.\\nCheck the error factor in the other settings.
-1197364981	5	6	The specified port belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified port.
-1197364980	5	6	The specified host group belongs to a resource group that you do not have permission \\nto access.\\nLog out, and then log back in with access to the resource group containing the specified \\nhost group.
-1197364979	5	6	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-1124564337	5	6	The specified volume contains a Thin Image pair.\\nCheck the setting of the specified volumes.
-1124564336	5	6	The specified volume contains Pool-VOLs. \\nCheck the setting of the specified volumes.
-1124543194	1	3	The status of the storage system requires maintenance (for example, the storage system \\nis blocked, the shared memory is inconsistent, or some other factor).\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-1124543190	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-1124542973	5	6	Copying is in progress for a pair of TrueCopy, Universal Replicator, ShadowImage, \\nVolume Migration, or Thin Image.\\nWait for a while, and then retry the operation.
-1124542972	5	6	The configuration of TrueCopy, Universal Replicator, ShadowImage, Volume Migration, \\nor Thin Image has been defined.\\nRelease the configuration definition, and then retry the operation.
-1124542970	5	6	The Remote Copy pair is suspended.\\nAdd an alternative path.
-1124542969	5	6	The corresponding CHB might contain the last path between the MCU and RCU of TrueCopy \\nor Universal Replicator.\\nMake sure that there is an alternative path from the MCU.
-1124542947	5	6	ShadowImage or Thin Image setting exists. \\nRelease the settings or stop the I/Os, and then retry the operation.
-1124542946	5	6	The backup server of ShadowImage or Thin Image is running. \\nStop the backup server, and then retry the operation.
-1124542945	5	6	Some pairs of ShadowImage or Thin Image exist. \\nSplit the pair of ShadowImage or Thin Image.
-1124542944	5	6	Some pairs of ShadowImage or Thin Image exist. \\nResynchronize the pair of ShadowImage or Thin Image.
-1124542943	5	6	Some pairs of ShadowImage or Thin Image exist. \\nChange the volume status to Simplex.
-1124542942	5	6	The operation cannot be performed because one of the following maintenance operations \\nis 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\\nWait for a while, and then retry the operation.
-1124541303	5	6	Processing cannot be performed because of Data Retention Utility settings.\\nCheck the settings, then retry the operation.
-1124541300	5	6	Devices to be maintained include journal volumes.\\nDelete or suspend all pairs belonging to journal volumes to be maintained.
-1124541299	5	6	Devices to be maintained include journal volumes.\\nDelete all pairs belonging to journal volumes to be maintained.
-1124538389	5	6	The restore operation has been failed, because the specified LDEV was not shredded \\nor formatted.\\nShred or format the specified LDEV. If the specified LDEV is Dynamic Provisioning \\nvolume (DP-VOL), recover the pool first.
-1124538388	1	2	The restore operation has been failed, because the system cannot access the specified LDEV.\\nCall the HSSC.
-1124538385	5	6	A TrueCopy pair or a Universal Replicator pair is defined. \\nRelease the pair definition, and then retry the operation.
-1124538384	5	6	A TrueCopy pair or a Universal Replicator pair is defined. \\nDelete the pair definition or suspend the pair, and then retry the operation.
-1124538383	5	6	The target volume is defined as a pair volume of ShadowImage or Thin Image.\\nSplit the pair, and then retry the operation. If the Quick Split mode is on, suspend \\nand then split the pair.
-1124538382	5	6	A pair of ShadowImage or Thin Image is defined. \\nSplit the pair, and then retry the operation. If the Quick Split mode is on, suspend \\nand then split the pair.
-1124538359	5	6	A Volume Migration pair is defined.\\nDelete the pair definition, and then retry the operation.
-1124538358	5	6	A Volume Migration pair is defined.\\nRelease the pair definition.
-1124513432	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124453822	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124453819	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124453565	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124445944	5	6	The program product required for using the shredding function is not installed.\\nInstall the required program product.
-1124445943	5	6	The specified volume is formatting or shredding.\\nRetry the operation later.
-1124424062	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124424029	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124423998	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124423997	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124423996	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124423963	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124423907	1	2	An error occurred during Storage Navigator processing.\\nIf nothing changes despite retrying, call the HSSC.
-1124419161	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124419157	5	5	There is an error in another setting and the setting processing has not been executed.\\nCheck the error factor in the others settings.
-1124394085	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124393278	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124391357	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124364480	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124364479	1	3	A communication time-out error occurred in the storage system.\\nIf this problem persists, please call the HSSC.
-1124364478	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1124363519	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-1124363517	1	3	This function is not supported.\\nCheck whether the DKCMAIN firmware version and Storage Navigator software version \\nare mismatched.
-1124355613	5	2	An error occurred while connecting to the storage system.\\nIf the problem persists despite retrying, please call the HSSC.
-1124355605	5	6	The operation of the external volume has been failed because all the paths to the \\nexternal volume are blocked.\\nRestore more than one path to the external volume, and then perform the operation \\nof the external volume.
-1087717782	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1087687923	1	3	The resources of other SLPR(s) cannot be accessed.\\nAn error occurred during processing. If this problem persists, please call the HSSC.
-1086793113	5	6	There are no changes in the current configuration and the setting.\\nCheck the setting.
-1086793083	5	6	The volumes registered in a Dynamic Provisioning Pool Group are included in the items \\nto be maintained.\\nDelete the Dynamic Provisioning Pool Group that includes the items to be maintained.
-1086793082	5	6	The pool volumes associated with the Dynamic Provisioning volume is included in the \\nitems to be maintained.\\nRelease the association between the pool volume and the Dynamic Provisioning volume.
-1086793020	5	6	Preparing for quick format.\\nCheck the status and wait until the status changes to a status that maintenance is possible.
-1086792269	5	2	The specified volume is not available to execute VLL operation (Create LDEVs, Delete LDEVs).\\nRelease the quorum disk, and then retry the operation.
-1086792215	5	6	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-1086792214	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1086792213	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-1086792145	5	3	The storage system is in internal process, or some other user is changing the configuration.\\nWait for a while, then click [Refresh] on the [File] menu. When an error occurs during \\nlogin, wait for a while and login again.
-1086792090	5	6	The specified volume contains a quorum disk.\\nRelease the quorum disk, and then retry the operation.
-1086792089	5	6	The specified volumes contain a global-active device pair volume.\\nDelete the global-active device pair, and then retry the operation.
-1086792088	5	6	The specified volumes contain a global-active device pair volume.\\nDelete the global-active device pair, and then retry the operation.
-1086792060	5	6	The specified volume includes a remote command device being used by a mirror of the \\njournal group.\\nRelease the quorum disk, and then retry the operation.
-1085875418	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-1085840942	5	6	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-1085840941	5	6	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-1085786077	5	6	The selected MP unit is not mounted.\\nVerify the configuration, and then select a mounted MP unit.
-1085786076	5	6	The Auto cannot be specified because the attribute of Fixed has been added to all \\nof the MP Units.\\nRelease the Fixed attribute, or specify a mounted MP Unit.
-1084885491	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
-1033935964	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-1033906207	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-1033906174	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-1033906142	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-1033901302	5	5	The setting cannot be applied because there is an error in a different setting.\\nVerify and correct the error in the other setting, and then retry the operation.
-1033846625	5	4	A time-out error occurred. \\nVerify that all of the settings have been applied. Retry the setting on the items \\nthat are not applied if there is any. If this problem persists, contact the HSSC.
-1033846624	5	4	A time-out error occurred. \\nVerify that all of the settings have been applied. Retry the setting on the items \\nthat are not applied if there is any. If this problem persists, contact the HSSC.
-1033845664	5	5	The operation cannot be performed, or a communication time-out error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-1033845660	5	4	The storage system has accepted the request normally, but the pair status change \\nrequires some time.\\nVerify that the pair status has been changed. If the status is not changed, verify \\nthe local storage system or remote storage system configuration and the condition \\nof the paths between the local storage system and the remote storage system, wait \\nfor a while, and then retry the operation.
-1033839894	5	5	The number of specified remote paths is less than the minimum number of paths due \\nto a communication error between the local storage system and the remote storage system.\\nVerify the remote path status, and then restore the paths.
-1033839890	5	5	The pair status of the secondary volume is not valid for the specified operation.\\nVerify the pair status of the secondary volume.
-1033839863	1	4	An internal error occurred. \\nIf this problem persists, contact the HSSC.
-1033839829	5	5	The number of normal remote paths is less than the minimum number of paths.\\nAdd normal remote paths, and then set the minimum number of paths, or reduce the \\nminimum number of paths, and then delete the remote path.
-1033839773	5	4	The remote paths between the local storage system and the remote storage system are \\nnot established.\\nVerify the remote path status between the local storage system and the remote storage system.
-1033839772	5	4	Pinned tracks exist in the primary volume.\\nRestore the pinned tracks in the primary volume.
-1033839771	5	4	Pinned tracks exist in the secondary volume.\\nRestore the pinned tracks in the secondary volume.
-1033839770	5	4	The specified primary volume cannot be used.\\nVerify if the primary volume is in any of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in the correction access condition.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.
-1033839768	5	4	The emulation type of the primary volume is not supported.\\nSee the user guide to verify whether the emulation type of the specified volume is \\nsupported.
-1033839735	5	5	An unexpected error occurred on the local storage system.\\nContact the HSSC.
-1033839642	5	4	The pair operation cannot be performed because the specified secondary volume applies \\nto one of the following:\\n- A LUN path is not defined.\\n- Its emulation type is not supported.\\nVerify the configuration of the remote storage system, and then specify an existing \\nvolume for the secondary volume. Or verify the emulation type of the specified secondary volume.
-1033838874	5	4	The specified secondary volume cannot be recognized from the connection port.\\nVerify the configuration of the specified secondary volume.
-1033838868	5	4	The local storage system cannot accept the pair operation.\\nWait for a while, and then retry the operation.
-1033838840	5	4	The pair cannot be created because the used capacity exceeds the licensed capacity. \\nSee the license key information and verify the licensed capacity of the volumes. \\nTo create more pairs, purchase a license key that allows you to use a larger capacity.
-1033838839	5	4	The pair cannot be created because the used capacity exceeds the licensed capacity \\nof the remote storage system.\\nVerify the licensed capacity of the remote storage system. To create more pairs, \\npurchase a license key that allows you to use a larger capacity.
-1033837972	5	5	No more space is left in the difference management area of the local storage system.\\nContact the HSSC.
-1033837970	5	5	No more space is left in the difference management area of the remote storage system.\\nContact the HSSC.
-961244819	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961244565	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961215030	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961215029	1	3	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961214997	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961214963	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961185085	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961182357	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961155480	1	3	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-961155479	1	3	A communication time-out error occurred.\\nIf the same problem persists despite retrying, please call the HSSC.
-961154519	1	3	An error occurred while connecting to the storage system.\\nIf the same problem persists despite retrying, please call the HSSC.
-933063448	5	5	The operation cannot be performed because the capacity of the specified LDEV is different \\nfrom that of the selected external volume.\\nSpecify the same capacity as that of the external volume for the LDEV.
-933063447	5	5	Data Direct Mapping cannot be enabled because the specified emulation type is not OPEN-V.\\nSpecify a volume whose emulation type is OPEN-V.
-933063446	5	5	The specified LDEV ID of the pool volume is outside the setting range.\\nVerify the LDEV ID of the pool volume, and then retry the operation.
-933063445	5	5	The operation cannot be performed because the specified pool volume is not associated \\nwith a pool with the Data Direct Mapped attribute.\\nSpecify a volume that is associated with a pool whose attribute is Data Direct Mapped.
-933063444	5	5	The operation cannot be performed because the specified pool volume is associated \\nwith a different Dynamic Provisioning volume.\\nSpecify a different pool volume, or delete the Dynamic Provisioning volume, and then \\nretry the operation.
-933063442	5	5	No volumes with the Data Direct Mapped attribute can be created because the specified \\ncapacity of the external volumes does not satisfy the requirements for the pool volume.\\nDisable the Data Direct Mapped attribute of the volumes, or verify the capacity of \\nthe external volumes.
-933063441	5	5	No volumes can be created because the Data Direct Mapped attribute differs between \\nthe specified volume and pool.\\nVerify the setting.
-933063440	5	5	Full Allocation and Data Direct Mapping cannot be enabled at the same time.\\nVerify the setting.
-933063417	5	5	The operation cannot be performed because the PCIe channel board is in the blocking process.\\nWait until the blocking process is complete, verify the PCIe channel board status, \\nrestore it, and then retry the operation.
-933063416	5	5	The operation cannot be performed because the PCIe channel board is blocked.\\nVerify the PCIe channel board status, restore it, and then retry the operation.
-933059415	5	5	The operation cannot be performed, because Thin Image pairs exist in the pool to \\nwhich the selected pool volumes or external volumes belong.\\nDelete the Thin Image pairs in the pool to which the selected pool volumes or external \\nvolumes belong, and then retry the operation.
-933059414	5	5	The operation cannot be performed, because Thin Image pairs and DP-VOLs whose LDEV \\nstatus is Normal exist in the pool to which the selected pool volumes or external \\nvolumes belong.\\nDelete the Thin Image pairs and block the DP-VOLs in the pool to which the selected \\npool volumes or external volumes belong, and then retry the operation.
-928059449	5	3	The specified volume does not exist. \\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-928054419	5	6	This functionality is not available. Open Volume Management \\nor LUN Manager is required.\\nInstall the necessary P.P. license key.
-928053746	5	6	This functionality is not available. LUN Manager is required.\\nInstall the necessary P.P. license key.
-928053745	5	6	This functionality is not available. Open Volume Management is required.\\nInstall the necessary P.P. license key.
-928050769	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-928029470	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-928029469	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-892971600	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-892971599	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-892971598	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-892943731	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-892909878	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-892909877	1	3	This function is not supported.\\nIf the problem persists despite retrying, please call the HSSC.
-892909876	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-892909875	1	3	An error occurred while connecting to the storage system.\\nWait, then retry the operation. If the same problem persists despite retrying, please \\ncall the HSSC.
-892909874	1	3	A communication time-out error occurred in the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-892073958	5	3	The password is different from the one that was input at the time of backup. Or, \\nthe backup file might be broken.\\nCheck the password and the backup file.
-891984467	1	3	An error occurred on the DKC side.\\nIf the problem persists despite retrying, please call the HSSC.
-891984462	5	3	The serial number of the encryption key does not match.\\nUse the correct encryption key.
-891174449	5	5	A pair of TrueCopy is defined.\\nRelease the pair definition, and then retry the operation.
-891174448	5	5	A pair of ShadowImage or Thin Image is defined.\\nRelease the pair definition, and then retry the operation.
-891115859	5	5	A pair of Universal Replicator is defined.\\nRelease the pair definition, and then retry the operation.
-891115858	5	5	A volume is defined as a journal volume of Universal Replicator.\\nRelease the journal volume setting for Universal Replicator, and then retry the operation.
-891115644	5	5	The specified operation cannot be performed because there is not enough memory available \\non the shared memory for the V-VOL management area.\\nInstall the additional shared memory for the V-VOL management area, and then retry \\nthe operation. If the additional shared memory is already installed, the capacity \\nof pools and V-VOLs has reached the maximum. In this case, delete unnecessary pools \\nand V-VOLs, and then retry the operation.
-890278710	5	5	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-890278551	5	5	The specified V-VOL is not mounted.\\nCheck the specified V-VOL.
-890278550	5	5	The specified V-VOL has already been specified.\\nExclude the duplicated setting, then retry the operation.
-890250962	5	5	The LDKC, CU, and LDEV are not set within the available range.\\nVerify the settings of the specified LDKC, CU, and LDEV.
-890250961	5	5	Specified LDKC:CU:LDEV has already been used.\\nCheck the setting of LDKC, CU, and LDEV.
-890250960	5	5	The specified LDEV number has already been assigned to another emulation group within \\nthe range grouped by 32 LDEV numbers.\\nCheck the setting of emulation groups within the range grouped by 32LDEV numbers.
-890250959	5	5	Specified SSID has already been used.\\nCheck the setting of SSID.
-890250957	5	5	The specified LDEV capacity is invalid.\\nCheck the setting of LDEV capacity.
-890250934	5	5	The specified emulation type cannot be used.\\nCheck the setting of the specified emulation type.
-890250932	5	5	Specified CLPR is not mounted.\\nCheck the setting of CLPR.
-890248912	5	5	The value of SSID is not set within the available range.\\nCheck the value of the specified SSID.
-890248911	5	5	A value different from SSID that has already been set is specified. \\nCheck the setting of SSID.
-890189394	5	5	The specified operation cannot be performed because there is not enough memory available \\non the shared memory for the V-VOL management area.\\nInstall the additional shared memory for the V-VOL management area, and then retry \\nthe operation. If the additional shared memory is already installed, the capacity \\nof pools and V-VOLs has reached the maximum. In this case, delete unnecessary pools \\nand V-VOLs, and then retry the operation.
-890189393	5	5	The capacity of Dynamic Provisioning volume (DP-VOL) is invalid.\\nCheck the capacity of Dynamic Provisioning volume (DP-VOL).
-890189391	5	5	The pool is in an abnormal state.\\nRecover the pool, then retry the operation.
-890189329	5	5	The number of Dynamic Provisioning volumes that can be made in a single pool has \\nexceeded the maximum.\\nCheck the configuration of the current DP-VOL.
-890189305	5	5	The storage system is in process to delete DP-VOL.\\nWait for a while, then retry the operation.
-890188500	5	5	Volume migration or Quick Restore is in progress.\\nWait for the migrating volume or the Quick Restore to be completed, then retry the \\noperation.
-890188214	5	5	There is a pool that has been blocked. And the item to be operated includes a Dynamic \\nProvisioning volume (DP-VOL).\\nRestore the pool that has been blocked by the Dynamic Provisioning function, then \\nretry the operation.
-890187477	5	5	The total capacity of DP-VOLs defined in the specified pool exceeds the value that \\nhad been permitted to the pool.\\nCheck the total capacity of DP-VOLs defined in the specified pool and its pool settings. \\nIf this problem persists, please call the HSSC.
-890167179	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
-889272572	5	5	The specified MP Blade is not mounted.\\nVerify the specified MP blade.
-889272536	5	5	Enough cache management devices cannot be allocated to the target volumes.\\nDelete unnecessary volumes, and then retry the operation. When there is a Thin Image \\npair, delete all the pairs related to the unnecessary primary volumes, and then retry \\nthe operation. If this problem persists, call the HSSC.
-889272535	5	5	An error occurred while accessing the user information.\\nTry again. If this problem persists, call the HSSC.
-889272505	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-889272503	5	5	The pool associated with the specified LDEV contains LDEVs that belong to a resource \\ngroup that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the LDEVs \\nin the associated pool.
-889272480	5	5	The specified emulation type is different from the emulation type of the selected pool.\\nSpecify the same emulation type as the pool.
-889272476	5	5	The storage system is in internal process, or a different user is changing the configuration.\\nWait for a while, and then retry the operation.
-837541402	5	6	The volume specified as a migration target is being formatted or shredded.\\nRetry the operation after the formatting or the shredding is complete.
-837540658	5	6	The volume specified as a migration source is already used as a volume of Concurrent Copy.\\nSelect a different volume, and then retry the operation.
-837540657	5	6	The volume specified as a migration target is already used as a volume of Concurrent Copy.\\nSelect a different volume, and then retry the operation.
-837539728	5	6	The volume types do not match.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539704	5	6	The shared memory to set a plan is insufficient.\\nInstall the shared memory if it is possible.\\nIf it is impossible to install the shared memory, the plan cannot be set any further.\\nSee the section about the computational methods of the number of movement plans described \\nin the Volume Migration User Guide for the relation between the number of plans that \\ncan be made and the shared memory.
-837539702	5	6	The source volume(s) is not equipped.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539701	5	6	The command was rejected due to one of the following reasons.\\n- The volume specified as a migration source was blocked.\\nRecover the blocked volume, and then retry the operation.
-837539700	5	6	The volume specified as a migration source is being formatted or shredded.\\nRetry the operation after the formatting or the shredding is complete.
-837539699	5	6	The volume specified as a migration source is a command device.\\nSelect a different volume, and then retry the operation.
-837539698	5	6	The target volume(s) is not equipped.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539697	5	6	The command was rejected due to one of the following reasons.\\n- The volume specified as a migration target was blocked.\\nRecover the blocked volume, and then retry the operation.
-837539696	5	6	The volume specified as a migration target is being formatted or shredded.\\nRetry the operation after the formatting or the shredding is complete.
-837539695	5	6	The volume specified as a migration target is a command device.\\nSelect a different volume, and then retry the operation.
-837539672	5	6	The volume(s) are already used by Volume Migration.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539671	5	6	The number of the ShadowImage pair volumes has reached the maximum.\\nSee "Supported and prohibited source and target volumes" in the Volume Migration \\nUser Guide if the volumes of ShadowImage can be migrated.
-837539670	5	6	The volume(s) are already used by Volume Migration.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539669	5	6	The volume(s) are already used by Volume Migration.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539668	5	6	The selected source volume and destination volume are the same volume.\\nRetry the operation. If this problem persists, contact the HSSC.
-837539664	5	6	The specified volume(s) are already used by ShadowImage.\\nSee "Supported and prohibited source and target volumes" in the Volume Migration \\nUser Guide if the volumes of ShadowImage can be migrated.
-837539642	5	6	The specified volume(s) are already used by ShadowImage.\\nSelect a different volume, and then retry the operation.
-837539641	5	6	The volume(s) is already being used by Data Migration.\\nRelease the Data Migration.
-837539640	5	6	The specified volume(s) are already used by ShadowImage.\\nSelect a different volume, and then retry the operation.
-837539639	5	6	The specified volume(s) are already used by ShadowImage.\\nSelect a different volume, and then retry the operation.
-837539638	5	6	The volume specified as a migration target cannot be migrated because it is used \\nas P-VOL of TrueCopy.\\nSelect a different volume, and then retry the operation.
-837539637	5	6	The volume specified as a migration target cannot be migrated because it is used \\nas S-VOL of TrueCopy.\\nSelect a different volume, and then retry the operation.
-837539635	5	6	The specified volume(s) are already used by ShadowImage.\\nSelect a different volume, and then retry the operation.
-837539634	5	6	The specified volume(s) are already used by ShadowImage.\\nSelect a different volume, and then retry the operation.
-837539633	5	6	The volume(s) is already being used by Data Migration.\\nRelease the Data Migration.
-837535885	5	6	The program product of Volume Migration is not installed.\\nInstall the Volume Migration program product.
-837535859	5	6	The specified volume has Read Only/Protect/SVOL Disable setting of Data Retention Utility.\\nRelease the Read Only/Protect/S-VOL Disable setting of Data Retention Utility.
-837511863	5	5	The operation cannot be performed because the storage system is being maintained, \\nor in internal process.\\nWait for a while, and then retry the operation.
-837511834	1	3	The storage system is busy.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-837482072	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837422459	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837422205	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837420568	5	6	This functionality is not available because Volume Migration is not installed.\\nInstall the Volume Migration program product.
-837417684	5	6	The specified volume cannot be migrated because it is used as S-VOL in the following status.\\n- A volume of TrueCopy in the Pending status.\\nFor the relation between TrueCopy and Volume Migration, see the description of Volume \\nMigration with TrueCopy and Universal Replicator DP-VOLs in the Volume Migration \\nUser Guide.
-837417683	5	6	The volume(s) is already being used by Remote Copy.\\nPlease Release the Remote Copy Pair.
-837417682	5	6	The specified volume cannot be migrated because it is used as P-VOL in the following status.\\n- A volume of TrueCopy in the Pending status.\\nFor the relation between TrueCopy and Volume Migration, see the description of Volume \\nMigration with TrueCopy and Universal Replicator DP-VOLs in the Volume Migration \\nUser Guide.
-837417681	5	6	The specified volume is not defined as the target volume of Volume Migration.\\nRetry the operation. If this problem persists, contact the HSSC.
-837417657	1	6	This function is already in progress.\\nWait for a while, and then retry the operation.
-837392702	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837392669	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-837392638	1	2	The system failed to access the file.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837392637	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837392603	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837392547	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837387895	5	0	Processing in progress. \\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837387866	1	3	The storage system is busy.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-837387865	5	3	Please check pair status.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-837387864	5	3	Please check pair status.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-837362725	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837361918	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-837333119	1	3	An error occurred while connecting to the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837333118	1	2	The storage system status is invalid.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-837328248	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837328247	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837328245	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837328244	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837328222	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837328221	1	0	An internal logic error occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
-837327136	5	6	The sizes of the source and the target volumes are not equal.\\nSelect the volumes with the same size for the migration source and target, and then \\nretry the operation.
-731546005	5	6	The specified volume cannot be set as a command device because it is used as a volume \\nof TrueCopy, Universal Replicator, ShadowImage, Volume Migration, Thin Image, or \\nglobal-active device.\\nSpecify a different volume.
-731546004	5	6	You are trying to set multiple paths to the same volume from one group.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731546003	5	6	Multiple volumes are specified to a single port, group or LUN combination.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731546002	5	6	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 Volume Migration.\\nSpecify a different volume, and then retry the operation.
-731546000	5	6	The one and only normal path for the volume used by TrueCopy, Universal Replicator, \\nShadowImage, Volume Migration, Thin Image, or global-active device cannot be removed.\\nVerify the setting.
-731545998	5	6	An operation is specified for a volume that does not exist.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545976	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731545968	5	6	The specified port does not exist.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545945	5	6	Invalid LUN.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545944	5	3	The specified volume does not exist. \\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545943	5	6	Invalid host mode.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545942	5	6	Invalid Fibre address.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545941	5	6	Invalid Fibre topology information.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545940	5	6	The specified LU path does not exist.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545843	5	6	LUN security setting has been made to a non-Fibre port. LUN security is a function \\nof LUN Manager.\\nCheck the specified content, and retry.
-731545820	5	6	Security Switch Off operation and path adding operation cannot be performed simultaneously.\\nFirst, add paths, then click Apply. Next, turn off the security switch, then click Apply.
-731545818	5	6	The specified WWN is already in use.\\nCorrect the specified contents, and request the setting of the configuration information again.
-731545817	5	6	You are trying to register the same WWN that is already registered.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545816	5	6	The specified host name or the host group name is already registered. (The host name \\nand the host group name cannot be the same.)\\nCorrect the specified contents, and request the setting of the configuration information again.
-731545815	5	6	The unregistered WWN number is specified.  (When deleting or changing)\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545814	5	6	You are trying to register the same host group number as the already registered one.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545813	5	6	The specified host group or iSCSI target is not registered.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731545038	5	6	The following volume cannot be specified to change the command device configuration:\\n- A volume that is used by Volume Migration.\\nSpecify a different volume, and then retry the operation.
-731545015	5	6	Invalid characters are specified in the nickname to be used in HOST GROUP and WWN.\\nCheck the settings, and then retry the operation.
-731545014	5	6	When requesting a configuration change of LUN-Security, a nickname is not specified. \\nSpecify the nickname of HOST GROUP.\\nCheck the settings, and then retry the operation.
-731545009	5	6	When registering WWN, the value is not specified. Or, zero is set as the value of \\nWWN. Be sure to set the WWN value before requesting the configuration change.\\nCheck the settings, and then retry the operation.
-731544981	5	6	Command device security cannot be set to the specified volume because the volume \\nis not a command device.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731544979	5	6	There are no host groups where the WWN will be registered.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731544976	5	6	The specified channel speed cannot be set for the target channel board.\\nCheck the settings, and then retry the operation.
-731544953	5	6	You cannot specify the default nickname when setting the nickname of a host group \\nor a host.\\nCorrect the specified contents, and request again.
-731544952	5	6	Failed to set the host group because the number of host groups exceeds the maximum \\nthat can be set in a port.\\nNo more host groups can be set, because the number of host groups has reached the \\nmaximum (254) that can be set in a port. Reduce the number of host groups, then retry \\nthe operation.
-731544951	5	6	Failed to set the WWN because the number of WWNs exceeds the maximum that can be \\nset in a port. \\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731544950	5	6	Failed to set the host mode because the number of host modes exceeds the maximum \\nthat can be set in a port.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731544949	5	6	Failed to set the path because the number of paths exceeds the maximum that can be \\nset in a port.\\nThe configuration information has already been changed.\\nCheck the settings, and request the configuration information setting again.
-731544948	5	6	When setting the port information (Fibre Address/Fibre Topology/Channel Speed), multiple \\nchange instructions are set to the same port.\\nCheck the settings, and then retry the operation.
-731544945	5	6	You specified same setting using LUNM operation.\\nThe specified port does not exist. You have specified a wrong port number. Or the \\nspecified port type cannot be processed in this agent. The error does not occur normally \\nbecause it cannot be modified in the window. In the unlikely event that this error \\noccurs, please call the HSSC.
-731544922	5	6	Because the Port Group setting is done, it is impossible to change.\\nRelease the Port Group setting.
-731544829	5	6	The volume cannot be configured as a command device because the volume does not have \\nRead/Write attribute.\\nCorrect settings, then retry.
-731544825	5	6	The specified host ID is already registered.\\nCorrect the settings, then retry.
-731544822	5	6	The specified host is already registered.\\nCorrect the settings, then retry.
-731544821	5	6	An incorrect host name was specified.\\nCorrect the settings, then retry.
-731544798	1	6	An error occurred during Storage Navigator processing.\\nIf this problem persists please call the HSSC.
-731544797	1	6	The specified path cannot be added, because the volume is used by a Remote Copy pair.\\nCorrect the specification, then retry the operation.
-731544763	5	6	The settings of the selected port cannot be changed because the port is connected \\nto an external storage system.\\nDelete external volumes that are mapped to the selected port, or disconnect the external \\nstorage system.
-731544758	5	6	The path cannot be set to the specified volume because the volume is not an open-systems volume.\\nCheck the setting.
-731542969	5	6	A LUN path cannot be added because the selected port is connected to a remote storage \\nsystem or an external storage system.\\nDisconnect the remote storage system or the external storage system, and then retry \\nthe operation.
-731542967	5	6	The operation cannot be performed, because remote paths are set on the MCU port.\\nDelete any remote paths, and then retry the operation.
-731542966	5	6	The settings of the selected port cannot be changed because the port is connected \\nto a remote storage system.\\nRemove LUN paths of a secondary volume, which are set to the selected port, and then \\nretry the operation. 
-731542965	5	6	A WWN cannot be added because the selected port is connected to a remote storage \\nsystem or an external storage system.\\nDisconnect the remote storage system or the external storage system, and then retry \\nthe operation.
-731542964	5	6	The host mode of the host group that is connected to a port of a remote storage system \\nor an external storage system cannot be changed.\\nDisconnect the remote storage system or the external storage system, and then retry \\nthe operation.
-731542963	5	6	A host group cannot be added because the selected port is connected to a remote storage \\nsystem or an external storage system.\\nDisconnect the remote storage system or the external storage system, and then retry \\nthe operation.
-731542962	5	6	The settings of the selected port cannot be changed because the port is connected \\nto a remote storage system.\\nDisconnect the remote storage system, and then retry the operation.
-731542937	5	2	The number of User LU settings exceeds the maximum.\\nReduce the number of user LU settings, then retry the operation.
-731542935	5	6	You cannot add paths to journal volumes.\\nSee the manual to verify the condition for this operation.
-731542934	5	2	The port type is incorrect.\\nCheck the port type, then retry the operation.
-731542931	5	6	The host mode "4C" is used for a host group connecting to volumes that cannot be \\nused for Universal Volume Manager.\\nCheck the settings, then retry.
-731542930	5	6	The host mode "4C" can only be used with Universal Volume Manager volumes.\\nCheck the settings, then retry.
-731542929	5	3	The host mode options cannot be set because the selected port is connected to a remote \\nstorage system.\\nDisconnect the remote storage system, and then retry the operation.
-731540241	5	6	This functionality is not available. LUN Manager is required.\\nInstall the necessary P.P. license key.
-731540240	5	6	This functionality is not available. Open Volume Management is required.\\nInstall the necessary P.P. license key.
-731537354	5	6	The specified volume cannot be assigned as a command device, and the path of the \\nvolume cannot be set because it is being used as a Pool volume.\\nSelect a different volume.
-731537352	5	6	The specified volume cannot be set as a command device because the volume is being \\nused as a V-VOL for Thin Image.\\nSelect another volume.
-731537325	5	6	The specified volume is a remote command device, and therefore the command device \\nsetting or the command device security setting cannot be set or released.\\nSee the manual to verify the condition for this operation.
-731537319	5	6	The settings of the selected port cannot be changed because an external volume is \\nmapped to the port.\\nDelete the external volume mapped to the port, and then retry the operation.
-731537288	5	6	Paths cannot be added or deleted for LUN0, because Host Mode Option 60 is enabled. \\nAlso, changing the setting of Host Mode Option 60 and changing the path setting (addition \\nor deletion) for LUN0 cannot be performed at the same time.\\nDisable Host Mode Option 60, and then add or delete paths for LUN0. 
-731537287	5	6	Releasing the Host Mode Option 61 is disabled.\\nCall the HSSC.
-731537265	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-731537263	5	5	The path definition between the resources included in different Virtual Storage Machines \\ncannot be performed.\\nPerform the path definition by specifying resources on the same Virtual Storage Machine.
-731537262	5	6	Releasing the Host Mode Option 72 is disabled.\\nSee the manual to verify the condition for this operation.
-731516211	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation later.
-731516207	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731516185	5	6	The LDEV is being used by the host, or an error occurred during Storage Navigator \\nprocessing.\\nThe recovery processing might take about 1 minute. Wait for a little while.
-731516182	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731516180	1	3	An error occurred while connecting to the storage system.\\nA communication error occurs. If the same error occurs despite retrying, please call the HSSC.
-731516121	1	3	An error occurred while connecting to the storage system.\\nA communication error occurs. If the same error occurs despite retrying, please call the HSSC.
-731515966	5	6	Processing is disabled because the host is mounted or the device is reserved.\\nUnmount the host and cancel reservation of the device. If the host is an AIX host, \\nunmount the host, and execute the varyoffvg command.
-731515965	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-731515964	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-731515930	5	6	The host specified by the WWN is performing I/O operations.\\nCheck the settings, then retry the operation.
-731515929	1	3	The operation cannot be performed, because the DKCMAIN firmware version does not \\nmatch the Storage Navigator software version.\\nWhen the same problem persists, please call the HSSC.
-731515928	5	3	The operation cannot be performed, because an inoperative MP exists.\\nWait a while, then retry the operation. If the same problem persists. Please call the HSSC.
-731515255	5	2	An error occurred while connecting to the storage system. The configuration may be \\ninconsistent.\\nClick [Refresh All] on the [File] menu, then refresh the configuration.
-731511410	5	6	The volume cannot be configured as a command device because the volume does not have \\nRead/Write attribute.\\nCorrect the settings, then retry.
-731486423	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731486422	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731486419	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731486418	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731426812	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731426809	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, please call the HSSC.
-731426555	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-731397052	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731397019	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731396987	1	2	A file access error has occurred.\\nIf this problem persists, please call the HSSC.
-731396953	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731396928	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731396897	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731392245	5	0	Processing in progress. Please wait for a while, and then retry the operation.\\nWait for a while, and then retry the operation.
-731367075	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731366268	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731364347	1	5	An unregistered error occurred.\\nIf this problem persists, contact the HSSC.
-731337470	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731337469	1	3	An error occurred while connecting to the storage system.\\nRetry the same operation several times. If the same error occurs, please call the HSSC.
-731337468	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-731336509	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-731336507	1	3	This function is not supported.\\nRetry the same operation several times. If the same error occurs, please call the HSSC.
-649549106	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649549105	1	2	A time-out error occurred.\\nThe array controller reboots automatically. If the same error occurs despite retrying, \\nplease call the HSSC.
-649549104	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649549103	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649549102	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649519315	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649519314	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649519313	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649519310	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649489524	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649489523	1	4	The number of set operations exceeds the maximum (20000).\\nPlease reduce the number of set operations, and perform again.
-649489522	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649459732	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649459727	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649459726	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649459725	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-649459724	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-649459702	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-649459701	1	1	A network error occurred. The probable cause is: \\n- A timeout error occurred during communication with the Storage Navigator.\\nLog on again. A network error may occur when the load of another application program \\nworking on the same PC with Storage Navigator is high. Increase the value of the \\nRMI time-out period when network error occurs.
-649459700	1	2	The number of clients logged on to the RMI server has exceeded 32.\\nLog on again after a while.
-649459699	1	2	The Storage Navigator configuration is invalid.\\nIf the problem persists despite retrying, please call the HSSC.
-649459671	5	2	Network error detected; exclusive lock is released.\\nLock is removed. Lock again.
-649429908	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649429907	1	0	The user ID or password is invalid.\\nEnter a correct user name or a password.
-649429720	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649429654	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649428886	1	2	The specified user ID is already logged on, or the previous logon was not properly \\nterminated. Please try again later. (By default, the session/RMI time-out is one minute.)\\nLog in with a different user name. Or, there is a possibility that the previous termination \\nprocess might be invalid. (Terminated by clicking the end button of the browser.) \\nIn this case, log in again after the RMI Time-out (default 1 min.).
-649427059	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649427058	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649426098	5	6	Failed to access the monitoring data because accessing the monitoring data on the \\nStorage Navigator is busy.\\nA different user might open one of the following windows or run the export tool. \\nIn this case, wait until one of the users moves to a different window or exits the \\nexport tool.\\n- [Usage Monitor] window of the True Copy\\n- [Usage Monitor] window of the Universal Replicator\\n- Volume Migration window\\n- Server Priority Manager window
-649425129	1	1	An administrator is changing a system environment file. Please log on again after \\nwaiting for a while.\\nIf the problem persists despite retrying, please call the HSSC.
-649425128	1	9	Modify mode released due to inactivity. Do you want to get back to the Modify mode?\\nTo get back to the Modify mode, click [OK]. Otherwise, click [Cancel].
-649425102	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425101	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425100	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425099	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425098	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425097	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425075	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649425074	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649425073	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649425072	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424078	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424077	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424076	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424075	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424074	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649424052	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-649422222	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
-649422220	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649422219	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649400149	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649400147	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649400118	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-649400087	1	2	A file open error has occurred.\\nIf the problem persists despite retrying, please call the HSSC.
-649400086	1	2	Failed to access the file. Check the setting, and then retry the operation. If the \\nsame problem persists despite retrying, please call the HSSC.\\nIf the problem persists despite retrying, please call the HSSC.
-649400049	1	2	An error occurred during Storage Navigator processing. If this problem persists, \\nplease call the HSSC.\\nIf the problem persists despite retrying, please call the HSSC.
-649370357	1	3	The content of the management file of the audit log is invalid.\\nIf the problem persists despite retrying, please call the HSSC.
-649370205	1	2	An error occurred during processing. The software version of Storage Navigator on \\nthe client PC might not match that of the destination SVP.\\nClear the caches of the JRE and the browser on the client PC, restart the browser, \\nand then retry the operation. If this problem persists, contact your network administrator \\nbecause the proxy server might cause the problem. If there is no problem in the network \\nand this problem persists, contact the HSSC.
-620890163	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-620890162	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890161	5	2	The SVP is busy.\\nClick [Refresh All] on the File menu and refresh the configuration.
-620890160	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890159	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890158	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890157	5	5	The storage system is refreshing or some other user is changing the setting.\\nWait and then retry the operation.
-620890156	1	3	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620890155	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620890133	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890132	1	2	The Storage Navigator configuration is invalid.\\nIf the problem persists despite retrying, please call the HSSC.
-620890130	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620890128	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620890127	5	6	The array is refreshing, or some other user is registering the setting.\\nWait, then retry the operation.
-620889074	5	3	An error occurred while communicating with the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620860370	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620800760	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620800667	5	6	The number of requests exceeds the maximum number that can be processed.\\nReduce the number of requests, then retry the operation.
-620795955	5	3	The storage system is in the internal process, or some other user is changing the \\nconfiguration.\\nWait for a while, click Refresh on the File menu or log in again, and then retry \\nthe operation.
-620771000	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620770998	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620770967	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-620770936	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620770935	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620770845	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620766193	5	0	Processing is in progress.\\nIf the problem persists despite retrying, please call the HSSC.
-620741116	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620741023	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620711418	1	3	An error occurred while connecting to the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620711417	1	3	A communication time-out error occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-620711413	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-620710457	1	3	An error occurred while connecting to the storage system.\\nVerify the software version of the storage system.
-620681627	5	5	Another user is accessing with Modify mode.\\nWait, then retry the operation.
-620672690	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-592282155	5	3	The operation cannot be performed because the storage system is being maintained.\\nWait until the maintenance operation is complete, and then retry the operation.
-592261012	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-592261010	5	3	Such as Volume Migration and QuickRestore are in progress.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-592261009	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-592261008	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-592261007	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-592261004	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-592260981	1	3	The status of the storage system requires maintenance (for example, the storage system \\nis blocked, the shared memory is inconsistent, or some other factor).\\nIf the problem persists despite retrying, please call the HSSC.
-592260979	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-592260977	1	3	An error occurred while connecting to the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-592260976	5	3	A service engineer is accessing the system in Modify mode.\\nRetry the operation later.
-592260975	5	2	Network error detected; exclusive lock is released.\\nRe-execute the request for starting exclusive lock.
-592260918	5	3	Communication busy.\\nRetry the operation later.
-592260917	5	3	The Storage Navigator is not ready yet, or an internal processing is being executed.\\nWait, then click [Refresh] on the [File] menu. When an error occurs during a login, \\nwait, then log in again.
-592260762	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-592260761	1	2	The storage system status is invalid.\\nCheck the DKC status and the current status of the configuration setting. If necessary, \\nre-execute the setting operation.
-592260052	5	2	An error occurred while connecting to the storage system. The configuration may be \\ninconsistent.\\nClick [Refresh All] on the [File] menu, then refresh the configuration.
-592231219	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-581341689	5	5	The Disconnect External Storage Systems or the Disconnect External Volumes is not \\nexecuted for the target volume.\\nExecute the Disconnect External Storage Systems or the Disconnect External Volumes, \\nthen retry the operation.
-581341688	5	5	A pair of TrueCopy is defined.\\nRelease the pair definition, and then retry the operation.
-581341687	5	5	A pair of ShadowImage or Thin Image is defined.\\nRelease the pair definition, and then retry the operation.
-581284863	5	5	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.\\nRestore the blocked path status or set the paths so as to remain at least one path \\navailable, and then retry the operation.
-581284837	5	5	No paths will be available, if you change the setting of paths.\\nMake the setting of the paths to keep at least one path available, then retry the \\noperation.
-581283972	5	5	After executing the Disconnect External Storage Systems or the Disconnect External \\nVolumes, neither the Reconnect External Paths nor the Disconnect External Paths can \\nbe executed.\\nExecute the Reconnect External Storage Systems or the Reconnect External Volumes, \\nthen retry the operation.
-581283971	5	5	The specified External Path is not registered.\\nCheck the specified External Path.
-581283970	5	5	The external volume is blocked.\\nEnsure that the external volume is not blocked, then retry the operation.
-581283098	5	5	A pair of Universal Replicator is defined.\\nRelease the pair definition, and then retry the operation.
-581283097	5	5	A volume is defined as a journal volume of Universal Replicator.\\nRelease the journal volume setting for Universal Replicator, and then retry the operation.
-581283095	5	5	The cache mode cannot be changed when the Disconnect External Storage Systems or \\nthe Disconnect External Volume is in progress.\\nExecute the Reconnect External Storage Systems or the Reconnect External Volumes, \\nput the external volume in normal status, then retry the operation.
-581283073	5	5	The cache mode cannot be changed because the bind mode is set to the specified volume.\\nRelease the bind mode setting, then retry the operation.
-581281118	5	5	The configuration of Pool VOL is defined.\\nRelease the configuration definition of Pool VOL, then retry the operation.
-581281113	5	5	A Thin Image pool volume is included in the items.\\nDelete pools to which the Thin Image pool volumes belong, and then retry the operation.
-581278294	5	5	The extended shared memory for Universal Volume Manager is not installed.\\nThe extended shared memory for Universal Volume Manager needs to be installed.\\nPlease call the HSSC.
-580445949	5	5	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-580445793	5	5	The specified External Path Group is not mounted.\\nCheck the specified External Path Group.
-580445792	5	5	The specified External Path Group has already been mounted.\\nCheck the specified External Path Group.
-580445791	5	5	The specified External Path Group has already been used.\\nClear the duplicated setting, then retry the operation.
-580445790	5	5	The specified external volume is not mounted.\\nCheck the specified external volume.
-580445789	5	5	The specified external volume has already been specified.\\nExclude the duplicated setting, then retry the operation.
-580445788	5	5	The External Path Group specified as a migration source has already been used as \\na migration target.\\nClear the duplicated setting, then retry the operation.
-580445787	5	5	The External Path Group specified as a migration target has already been used as \\na migration source.\\nClear the duplicated setting, then retry the operation.
-580445786	5	5	The path configuration of the External Path Group between the migration source and \\nthe migration target is different.\\nCheck the specified External Path Group.
-580445785	5	5	There are no setting lines of NewPathGroup.\\nCheck the contents of the spreadsheet.
-580445112	5	5	The number of NewPathGroup setting lines exceeds the limit.\\nCheck the contents of the spreadsheet.
-580445111	5	5	There are no setting lines of the ExG.\\nCheck the setting of ExG.
-580445110	5	5	There are no setting lines of TargetPathGroup.\\nCheck the contents of the spreadsheet.
-580422977	5	5	The number of external LUs that can be connected from a single port has exceeded \\nthe maximum value.\\nDelete unnecessary external LU(s), then retry the operation.
-580422976	5	5	The number of registered ports of the external storage system has exceeded the maximum.\\nOperate within the ports of the connected external storage system.
-580418203	5	5	The number of LDEVs that can be defined in an external volume has exceeded the maximum value.\\nCheck the number of LDEVs.
-580418202	5	5	Specified ExG has already been used.\\nCheck the setting of ExG.
-580418201	5	5	The LDKC, CU, and LDEV are not set within the available range.\\nVerify the settings of the specified LDKC, CU, and LDEV.
-580418200	5	5	Specified LDKC:CU:LDEV has already been used.\\nCheck the setting of LDKC, CU, and LDEV.
-580418199	5	5	The specified LDEV number has already been assigned to another emulation group within \\nthe range grouped by 32 LDEV numbers.\\nCheck the setting of emulation groups within the range grouped by 32LDEV numbers.
-580418198	5	5	Specified SSID has already been used.\\nCheck the setting of SSID.
-580418197	5	5	The target external volume is blocked or not set within the range of capacity that \\ncan be used.\\nCheck the status and the capacity of target external volume.
-580418196	5	5	The specified LDEV capacity is invalid.\\nCheck the setting of LDEV capacity.
-580418195	5	5	The total LDEV capacity defined in the external volume exceeds the external volume size.\\nCheck the setting of LDEV capacity.
-580418173	5	5	The specified emulation type cannot be used.\\nCheck the setting of the specified emulation type.
-580418171	5	5	Specified CLPR is not mounted.\\nCheck the setting of CLPR.
-580418166	5	5	The target external volume has already been mapped or set for mapping.\\nCheck the configuration and the setting of external volume.
-580418165	5	5	The External Path configuration of the target external volume is not corresponding \\nto that of another external volume in the same External Path Group.\\nCheck the setting of path configuration.
-580418010	5	5	Multiple operation tags are defined.\\nCheck the contents of the spreadsheet.
-580417021	5	5	The syntax of parameter is invalid.\\nCheck the syntax of parameter.
-580416962	5	5	The volume in the local storage system cannot be operated.\\nSpecify the volume in an external storage system.
-580416961	5	5	A correct parameter as a data transfer volume is not set.\\nCheck the setting of target external volume. 
-580416960	5	5	A correct parameter as RemoteCommandDevice is not set.\\nCheck the setting of target external volume. 
-580416957	5	5	The value entered as PathMode is outside the setting range.\\nCheck the value entered as PathMode.
-580416956	5	5	The number of alternate Path definitions that can be set to the external volume has \\nexceeded the maximum.\\nCheck the number of alternate Path definitions.
-580416955	5	5	The number of LDEV definitions that can be set to the external volume has exceeded \\nthe maximum.\\nCheck the number of LDEV definitions.
-580416280	5	5	The value of External Path Group is not set within the available range.\\nCheck the setting of External Path Group.
-580416277	5	5	Invalid port number.\\nCheck the setting of the port number.
-580416251	5	5	It is not set within the range where LUN can be used.\\nCheck the setting of LUN.
-580416248	5	5	The value of ExG is not set within the available range.\\nCheck the setting of ExG.
-580416246	5	5	Attribute is invalid.\\nCheck the setting of Attribute.
-580416243	5	5	It is not set within the range where CLPR can be used.\\nCheck the setting of CLPR.
-580416220	5	5	It is not emulation type that can be specified.\\nCheck the setting of emulation type.
-580416218	5	5	CacheMode is invalid.\\nCheck the setting of CacheMode.
-580416216	5	5	InflowControl is invalid.\\nCheck the setting of InflowControl.
-580416183	5	5	It is not set within the range where LDKC can be used.\\nCheck the setting of LDKC.
-580416180	5	5	It is not set within the range where CU can be used.\\nCheck the setting of CU.
-580416156	5	5	It is not set within the range where LDEV can be used.\\nCheck the setting of LDEV.
-580416154	5	5	It is not set within the range where LDEV capacity can be used.\\nCheck the setting of LDEV capacity.
-580416151	5	5	The value of SSID is not set within the available range.\\nCheck the value of the specified SSID.
-580416150	5	5	A value different from SSID that has already been set is specified. \\nCheck the setting of SSID.
-580416149	5	5	The number of paths has reached the maximum number.\\nCheck the setting of path.
-580416127	5	5	The specified WWN is not registered.\\nCheck the specified WWN.
-580416126	5	5	The specified WWN has already been specified.\\nExcluding the overlapping setting, then retry the operation.
-580416125	5	5	The specified external volume is a volume of the storage system that cannot be used \\nas an external storage.\\nCheck the type of the storage system.
-580415995	5	5	Specified WWN was not found.\\nCheck the specified WWN.
-580415994	5	5	Specified external volume was not found.\\nCheck the specified external volume.
-580356604	5	5	The volumes registered in a Dynamic Provisioning Pool are included in the items to \\nbe maintained.\\nDelete the Dynamic Provisioning Pool in which the volume included in the items to \\nbe maintained is registered, then retry the operation.
-580356575	5	5	Disconnect External Storage Systems or Disconnect External Volumes cannot be performed \\nfor one or more external volumes used as pool volumes. The pool to which those pool \\nvolumes were added is associated with DP-VOLs in a normal status or with a deduplication \\nsystem data volume in a normal status.\\nBlock the associated DP-VOLs and the deduplication system data volume, and then retry \\nthe operation.
-580356574	5	5	Set the same cache mode to all the volumes that compose a Pool VOL.\\nIf there is a volume whose cache mode cannot be changed due to its bind mode setting, \\nrelease the bind mode setting first.
-580355739	5	5	Volume migration or Quick Restore is in progress.\\nWait for the migrating volume or the Quick Restore to be completed, then retry the \\noperation.
-580355521	5	5	The specified volumes include remote command devices being used with mirrors in the \\nJournal of the Universal Replicator.\\nRelease the allocation of mirrors in the Journal for the remote command device, and \\nthen retry the operation.
-580355487	5	5	Quorum disks are included in the items to be maintained.\\nRelease the quorum disks, and then retry the operation.
-580354777	5	5	An external volume was not able to be recovered.\\nCheck the status of the mapping path and resolve the root cause of blockade, then \\nretry the operation.
-580354776	5	5	The external volume was able to be restored, but some of mapping paths were not able \\nto be restored normally.\\nCheck the status of the mapping path and resolve the root cause of blockade if needed, \\nthen retry the operation.
-580354775	5	5	Failed to disconnect from the external volume.\\nCheck the states of the external volume and the mapping path, and do not retry the \\noperation until the states return to normal.\\nIf the states cannot be restored to normal, or if the problem persists despite retrying, \\nplease call the HSSC.
-579468612	5	5	The operation cannot be performed because the device name or the virtual LDEV information \\ndiffers between volumes of the migration source storage system and the migration \\ntarget storage system.\\nVerify the settings.
-579468610	5	0	The operation cannot be performed because the global storage virtualization function \\nof the specified LDEV ID is enabled.\\nDisable the global storage virtualization function, and then retry the operation.
-579468609	5	5	The specified LDEV capacity is not valid.\\nVerify the setting of the LDEV capacity.
-579468607	5	5	This function is not available. Nondisruptive migration is required.\\nInstall the necessary program product license key.
-579439812	5	5	The specified MP Unit is blocked.\\nRecover the blocked MP Unit, and then specify it.
-579439811	5	5	The specified MP Unit is not mounted.\\nCheck the specified MP Unit.
-579439775	5	5	Enough cache management devices cannot be allocated to the target volumes.\\nDelete unnecessary volumes, and then retry the operation. When there is a Thin Image \\npair, delete all the pairs related to the unnecessary primary volumes, and then retry \\nthe operation. If this problem persists, call the HSSC.
-579439774	5	5	An error occurred while accessing the user information.\\nTry again. If this problem persists, call the HSSC.
-579439773	5	5	The port that is connected to the specified external volume belongs to a resource \\ngroup that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the port \\nthat is connected to the specified external volume.
-579439751	5	5	The port that is connected to the specified external path belongs to a resource group \\nthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the port \\nthat is connected to the specified external path.
-579439750	5	5	The port that is connected to the specified external path group belongs to a resource \\ngroup that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the port \\nthat is connected to the specified external path group.
-579439749	5	5	The port that is connected to the specified external WWN belongs to a resource group \\nthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the port \\nthat is connected to the specified external WWN.
-579439748	5	5	The specified external volume belongs to a resource group that you do not have permission \\nto access.\\nLog out, and then log back in with access to the resource group containing the specified \\nexternal volume.
-579439747	5	5	The specified external path contains an external volume in a resource group that \\nyou do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the external \\nvolumes on the specified external path.
-579439746	5	5	The specified external path group contains an external volume in a resource group \\nthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the external \\nvolumes on the specified external path group.
-579439745	5	5	The specified external WWN is used for an external volume in a resource group that \\nyou do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the external \\nvolume that uses the specified external WWN.
-579439744	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-579439743	5	5	The specified external volume contains an LDEV that belongs to a resource group that \\nyou do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the LDEV \\nin the specified external volume.
-579439720	5	5	The cache mode cannot be changed because the LDEV of the specified external volume \\nis 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 multi tier pool setting is enabled.\\nVerify the LDEV of the specified external volume.
-579439716	5	5	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-579439715	5	5	The storage system is in internal process, or a different user is changing the configuration.\\nWait for a while, and then retry the operation.
-579439714	5	5	The load balance mode cannot be changed because the path mode of the specified external \\nvolume is "Single."\\nSpecify a different external volume whose path mode is not "Single," and then retry \\nthe operation.
-579437734	5	5	The specified operation cannot be performed because the external volume mapped for \\nthe online data migration is reserved by the host.\\nDelete the external volume, and then retry the operation.
-563512698	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512697	1	2	A time-out error occurred.\\nThe array controller reboots automatically. If the same error occurs despite retrying, \\nplease call the HSSC.
-563512696	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512695	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512667	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512666	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512665	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-563512664	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512633	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-563512598	1	2	The storage system status is invalid.\\nIf the problem persists despite retrying, please call the HSSC.
-535002704	5	5	The storage system is refreshing or some other user is changing the setting.\\nWait and then retry the operation.
-534913050	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-518794016	5	5	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-517965692	5	5	The specified operation type is not supported.\\nSpecify an operation type that is supported.
-517876384	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-517846593	1	5	The number of requests exceeds the maximum number that can be processed.\\nReduce the number of requests, and then retry the operation.
-517846592	5	5	An incorrect ResourceGroupID was specified.\\nSpecify the registered ResourceGroupID, and then retry the operation.
-517846591	5	5	The specified ResourceGroupID has already been specified.\\nRelease the duplicated settings, and then retry the operation. 
-517846590	5	5	The number of characters for resource group name should be from 1 to 32.\\nCorrect the number of characters to be within the range.
-517846589	5	5	Invalid characters are used in the specified resource group name. \/:,;*?"<>| and \\nany spaces on the beginning and ending of the name cannot be used.\\nDelete the characters that cannot be used.
-517846588	5	5	The specified resource group name is already registered.\\nSpecify another resource group name.
-517846587	5	5	The specified number of resources has reached the upper limit.\\nReduce the number of resources to be specified, then retry the operation.
-517846586	5	5	The resource to be migrated is not specified.\\nSelect a resource, and then retry the operation.
-517846585	5	5	The LDKC, CU, and LDEV are not set within the available range.\\nVerify the settings of the specified LDKC, CU, and LDEV.
-517846563	5	5	The specified resource is already used.\\nRelease the duplicated settings, and then retry the operation. 
-517846562	5	5	The parity group ID is not set within the available range.\\nCheck the setting of the specified parity group ID. 
-517846561	5	5	The specified parity group is not mounted.\\nCheck the specified parity group ID. 
-517846560	5	5	The specified resource is already used.\\nRelease the duplicated settings, and then retry the operation. 
-517846559	5	5	Invalid port number.\\nCheck the setting of the port number.
-517846558	5	5	The specified resource is already used.\\nRelease the duplicated settings, and then retry the operation. 
-517846557	5	5	The host group ID is not set within the available range.\\nCheck the setting of the specified host group ID.
-517846556	5	5	The specified resource is already used.\\nRelease the duplicated settings, and then retry the operation. 
-517846555	5	5	The specified LDEVs cannot be migrated because they are a part of a Pool-VOL.  \\nSpecify all LDEVs if you want to migrate LDEVs that belong to a Pool-VOL.
-517846531	5	5	The specified LDEVs cannot be migrated because they are a part of a journal group.\\nSpecify all LDEVs if you want to migrate LDEVs that  belong to a journal group.
-517846530	5	5	The specified parity groups cannot be migrated because they are registered as a part \\nof a RAID Group.\\nSpecify all parity groups if you want to migrate parity groups registered in a RAID Group.
-517846529	5	5	Migration of resources that belong to different resource groups cannot be done.\\nA part of specified resources might be migrated. Verify the configuration of the \\nresource group to which the resources belong, and then retry the operation to migrate \\nthe resources that belong to one resource group.
-517846526	5	5	The LUSE value of the specified virtual LDEV is invalid.\\nCheck the LUSE setting of the specified virtual LDEV.
-517846525	5	5	The specified emulation type cannot be used.\\nCheck the setting of the specified emulation type.
-517816802	5	5	Any of the virtual storage system number, resource group number, or resource group \\nname is not valid.\\nVerify the settings.
-517816801	5	5	The specified resource group name has already been specified.\\nRelease the duplicated settings, and then retry the operation. 
-517816800	5	5	The specified resource group does not exist in the configuration.\\nRefresh the window, and then retry the operation. If this problem persists, call the HSSC.
-517816799	5	5	A resource group cannot be deleted because resources are included in the specified \\nresource group. \\nRelease all the resources in the specified resource group, then retry the operation.
-517816797	5	5	A resource group is not specified or the number of resource groups that can be specified \\nat a time exceeds the maximum.\\nAdjust the number of resource groups to be within the range of 1 to 1024, and then \\nretry the operation. 
-517816795	5	5	The resources on which LU paths are set cannot be added to or removed from the resource \\ngroup whose virtual mode is set to ON.\\nSelect resources on which LU paths are not set.
-517816794	5	5	The specified resource cannot be set because the resource belongs to a resource group \\nwhose virtual mode is not set to ON. \\nSelect a resource belonging to the resource group whose virtual mode is set to ON.
-517816772	5	5	The specified virtual fiber address is invalid.\\nCheck the setting of the specified virtual fibre address. 
-517816771	5	5	The channel package of the port to which the specified host group belongs is not \\nsupported.\\nCheck the setting of the specified port.
-517816770	5	5	Two or more resource groups are specified. \\nSet the resource in the same resource group.
-517816769	5	5	The resources on which LU paths are set cannot be added to or removed from the resource \\ngroup whose virtual mode is set to ON.\\nSelect resources on which LU paths are not set.
-517816768	5	5	The specified resource is already used.\\nRelease the duplicated settings, and then retry the operation. 
-517816767	5	5	The value of SSID is not set within the available range.\\nCheck the value of the specified SSID.
-517816766	5	5	The specified Virtual Storage Machine does not exist.\\nVerify the settings.
-517816765	5	5	There is a locked resource in the specified resource group.\\nUnlock the resource, and then retry the operation. 
-517816764	5	5	The number of Virtual Storage Machines exceeds the maximum that can be registered.\\nDelete unnecessary Virtual Storage Machines, and then retry the operation. If this \\nproblem persists, contact the HSSC.
-517816763	5	5	The specified model is not supported.\\nSpecify a model that is supported.
-517816741	5	5	The operation cannot be performed because the specified combination is already used \\nby a different Virtual Storage Machine.\\nSpecify a different model or serial number, and then retry the operation.
-517816740	5	5	The operation cannot be performed because the specified LDEV IDs include an LDEV \\nID that belongs to a different virtual storage machine.\\nSpecify LDEV IDs that belong to the same virtual storage machine, and then retry \\nthe operation.
-517816739	5	5	The device name or the virtual LDEV information is not set for the specified LDEV ID.\\nVerify the LDEV ID, set the device name or the virtual LDEV information, and then \\nretry the operation.
-517816738	5	5	The device name or the virtual LDEV information is defined for the specified LDEV ID.\\nVerify the LDEV ID, delete the device name or the virtual LDEV information, and then \\nretry the operation.
-517816736	5	0	The operation cannot be performed because the global storage virtualization function \\nis not enabled.\\nEnable the global storage virtualization function, and then retry the operation.
-517816735	5	5	The operation cannot be performed because the specified LDEV belongs to the Virtual \\nStorage Machine number 0.\\nChange the Virtual Storage Machine number, and then retry the operation.
-517816734	5	5	The operation cannot be performed because the specified LDEV belongs to other than \\nthe Virtual Storage Machine number 0.\\nChange the Virtual Storage Machine number, and then retry the operation.
-517816733	5	5	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do \\nnot match.\\nSpecify the same virtual LDEV ID as the LDEV ID, and then retry the operation.
-517816732	5	5	The operation cannot be performed because the LDEV ID and the virtual LDEV ID match.\\nSpecify a virtual LDEV ID that is different from the LDEV ID, and then retry the \\noperation.
-517816710	5	5	The operation cannot be performed because the LDEV ID and the virtual LDEV ID do \\nnot match.\\nSpecify the same virtual LDEV ID as the LDEV ID, and then retry the operation.
-517816709	5	5	The operation cannot be performed because the specified LDEV is used by a global-active \\ndevice pair.\\nDelete the Global Active Device pair, and then retry the operation.
-517816708	5	5	The operation cannot be performed because the specified LDEV is used by a Volume \\nMigration pair.\\nDelete the Volume Migration pair, and then retry the operation.
-517816707	5	5	The operation cannot be performed because the Virtual Attribute is GAD Reserved.\\nSet the attribute to Normal, and then retry the operation.
-517816706	5	5	The operation cannot be performed because the Virtual Attribute is not Normal.\\nSet the attribute to Normal, and then retry the operation.
-517816705	5	5	The operation cannot be performed because the host I/O operation is performed for \\nthe specified LDEV ID.\\nWait for a while, and then retry the operation.
-517816704	5	5	The operation cannot be performed because an LDEV is assigned to the specified LDEV ID.\\nVerify the settings.
-517816703	5	5	Host groups and LDEVs or iSCSI targets and LDEVs, to which LU paths are set, cannot \\nbe migrated to different virtual storage machines.\\nRelease the LU path setting of the selected host groups or iSCSI targets, and then \\nretry the operation.
-517816702	5	5	LDEVs, to which device names or virtual LDEV information is set, cannot be migrated \\nbetween resource groups of different Virtual Storage Machines. \\nVerify the settings.
-517816701	5	5	The operation cannot be performed because the resource lock of Resource Group ID \\n0 is not set.\\nSet the resource lock of Resource Group ID 0, and then retry the operation.
-517816675	5	5	This function is not available. Resource Partition Manager is required.\\nInstall the necessary program product license key.
-517816673	5	5	No more resource groups can be deleted because no resource group remains on the virtual \\nstorage machine.\\nTo delete all resource groups on the virtual storage machine, delete the virtual \\nstorage machine itself.
-517816672	5	5	The operation cannot be performed because the specified LDEV is used by a TrueCopy pair.\\nDelete the TrueCopy pair, and then retry the operation.
-517816671	5	5	The operation cannot be performed because the specified LDEV is used by a Universal \\nReplicator pair.\\nDelete the Universal Replicator pair, and then retry the operation.
-517816670	5	5	The operation cannot be performed because LU paths are set to the specified LDEV ID.\\nSpecify an LDEV ID to which LU paths are not set.
-517816648	5	5	The specified virtual LDEV ID is already used.\\nSpecify a different virtual LDEV ID, and then retry the operation.
-517816647	5	5	The operation cannot be performed because the specified LDEV is used as a journal volume.\\nRelease the journal volume setting, and then retry the operation.
-517816646	5	5	The specified serial number or the controller ID is invalid.\\nVerify the settings.
-517816645	5	5	Quorum disks are included in the items to be maintained.\\nRelease the quorum disks, and then retry the operation.
-517816644	5	5	The operation cannot be performed because the volume with the specified LDEV ID is \\nan LDEV with the ALU attribute.\\nDelete the volume with the specified LDEV ID, or specify a different LDEV ID.
-517816643	5	5	The operation cannot be performed because the volume with the specified LDEV ID is \\nan LDEV with the SLU attribute.\\nDelete the volume with the specified LDEV ID, or specify a different LDEV ID.
-517816617	5	5	Virtual Configuration (Emulation Type, CVS Settings, Number of Concatenated LDEVs, \\nand SSID) cannot be set to the specified LDEVs that belong to the virtual storage machine.\\nSelect Not Set for Virtual Configuration.
-517816616	5	5	The S-VOL attribute cannot be assigned to the specified LDEVs that belong to the \\nvirtual storage machine.\\nVerify the specified LDEV settings.
-517787782	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
-506403346	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-506403345	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-506403344	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-506403342	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-506313978	1	2	The Storage Navigator configuration is invalid.\\nIf the problem persists despite retrying, please call the HSSC.
-498177262	5	6	The operation cannot be performed because the CLPR that is specified to migrate the \\nselected pool volume is different from a CLPR to which other pool volumes in the \\nsame pool belong.\\nVerify the setting.
-498177260	5	6	The specified volume is used as a command device.\\nRelease the command device setting or specify another volume.
-498177236	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498177234	5	6	The specified volume is an external volume.\\nSpecify another volume.
-498177233	5	6	The selected volume is used as a virtual volume of Thin Image.\\nSpecify another volume.
-498177232	5	6	The specified volume is not configured.\\nSpecify another volume.
-498177230	5	6	This function is not available, because the program product is not installed.\\nInstall Open Volume Management.
-498177229	5	6	The specified volume is used as a Pool-VOL.\\nDelete the Pool-VOL, or specify a different volume.
-498177227	5	6	The specified pool does not exist.\\nCheck the settings.
-498176984	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498149397	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-498149396	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498149395	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498121528	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498121527	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-498088669	5	6	The logical volume cannot be registered, because it is not installed.\\nInstall the logical volume, or specify a different volume.
-498088668	5	6	The specified operation cannot be done, because the logical volume is blocked.\\nRestore the blockade status of the logical volume.
-498088667	5	6	The logical volume cannot be registered, because it is defined as a Pool-VOL.\\nDelete the Pool-VOL, or specify a different volume.
-498088666	5	6	The specified logical volume cannot be registered, because the CLPR number of the \\nvolume does not match the number of the logical volume already registered to the Pool.\\nMatch the CLPR number of the logical volumes.
-498088665	5	6	The specified logical volume cannot be registered, because it is a V-VOL.\\nSpecify another logical volume.
-498088664	5	6	The volume set as a Command Device cannot be set as a component of a Pool-VOL.\\nDelete the command device, or specify a different volume.
-498088663	5	6	The specified logical volume cannot be registered, because a LUN path is set to the \\nlogical volume.\\nSpecify another logical volume.
-498088662	5	6	The operation cannot be performed because one of the following licenses is not installed \\nor any licensed capacity is not enough.\\n- Dynamic Provisioning\\n- Dynamic Tiering\\n- active flash\\n- Thin Image\\nInstall the required license or add the required licensed capacity, and then retry \\nthe operation.
-498088660	5	6	The specified logical volume is being used by another program product.\\nSpecify another logical volume.
-498088638	5	6	The operation cannot be performed because the usage of the specified pool is 100% (full).\\nAdd some Pool-VOLs, or decrease the data for Thin Image by restoring or deleting \\nthe Thin Image pairs.
-498088637	5	6	The shared memory for the V-VOL management area is insufficient.\\nInstall additional shared memory for the V-VOL management area.
-498088636	5	6	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.\\nVerify the installation status of the virtual volume management area.
-498088635	5	6	An error occurred when setting the Pool.\\nCheck the error message of the logical volume(s) in the Pool.
-498088634	5	6	The specified operation cannot be performed because there is not enough memory available \\non the shared memory for the V-VOL management area.\\nInstall the additional shared memory for the V-VOL management area, and then retry \\nthe operation. If the additional shared memory is already installed, the capacity \\nof pools and V-VOLs has reached the maximum. In this case, delete unnecessary pools \\nand V-VOLs, and then retry the operation.
-498088633	5	6	The PCB for fibre port is not installed.\\nInstall the PCB for fiber port, and retry the operation.
-498088575	1	3	A communication time-out error occurred in the storage system.\\nIf this problem persists, please call the HSSC.
-498087677	5	6	The V-VOL management area is being used.\\nDelete the Thin Image pairs, and then retry the operation.
-498087676	5	6	The specified operation cannot be executed because the Pool-VOL is not mounted.\\nCheck the Pool-VOL setting.
-498087675	1	6	An error occurred while communicating with the storage system.\\nIf the problem persists despite retrying, please call the HSSC.
-498087674	1	3	This function is not supported.\\nThe DKCMAIN firmware version and Storage Navigator software version might not match. \\nVerify each software version.
-498087673	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-498087672	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, please call the HSSC.
-498087671	1	3	A communication time-out error occurred in the storage system.\\nIf this problem persists, please call the HSSC.
-498087669	5	2	An error occurred on the storage system. The configuration might not be consistent.\\nClick Refresh All on the File menu, and then refresh the configuration information.
-498086868	5	6	The specified operation cannot be performed because the Thin Image pair using the \\npool volumes to be maintained is in PSUS status or being restored.\\nResynchronize the pair or release the pair definition, and then retry the operation.
-498086865	5	6	A Thin Image pair is defined.\\nCancel the pair definition, and then retry the operation.
-498085966	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-497252621	5	6	The specified volume is used as a Dynamic Provisioning volume.\\nSpecify a different volume.
-497252567	5	6	The pool volumes associated with the Dynamic Provisioning volume is included in the \\nitems to be maintained.\\nRelease the association between the pool volume and the Dynamic Provisioning volume.
-497252563	5	6	The LDEV to be operated is not included in the specified parity group.\\nCheck the setting and status of the LDEV in the specified parity group.
-497252562	5	6	The association cannot be made because the pool is in a different CLPR.\\nConfirm that it is associated with a pool in the same CLPR.
-497252529	5	6	A failure occurred while formatting.\\nCancel the format processing from the Storage Navigator, then retry the formatting \\nprocessing again.
-497252528	5	6	A failure occurred while quick formatting.\\nCancel the quick formatting processing from the Storage Navigator, then execute the \\nquick formatting processing again.
-497252506	5	6	The specified volumes contain volumes that are being quick formatted.\\nRetry the operation later.
-497252505	5	6	Preparing for quick format.\\nCheck the status and wait until the status changes to a status that maintenance is possible.
-497252504	5	6	The specified volumes contain volumes that quick format cannot be executed.\\nSelect only the volumes that quick format can be executed and execute quick format.
-497252502	5	6	The specified quick formatting operation cannot be performed, because the total number \\nof 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.\\nChange the setting or wait until the quick formatting operations for other parity \\ngroups is complete, and then retry the operation. \\nSee the Provisioning Guide for the details of quick formatting.
-497252501	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-497251786	5	6	The specified volumes contain volumes that cannot be formatted.\\nSelect only the volumes that can be formatted and format the volumes.
-497251700	5	6	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-497251631	5	6	The specified volumes contain a quorum disk.\\nVerify the specified volumes.
-497251545	5	6	The specified volume includes a remote command device being used by a mirror of the \\njournal group.\\nRelease the quorum disk, and then retry the operation.
-497162387	5	6	The specified volume is not a Dynamic Provisioning volume.\\nSpecify a different volume.
-497162386	1	2	An internal logic contradiction occurred on the DKC side.\\nCall the HSSC.
-497162385	5	6	Shared memory is not installed.\\nInstall the shared memory.
-497162384	5	6	The shared memory for the V-VOL management area is insufficient.\\nDelete the unnecessary Dynamic Provisioning pools (DP pools) and Dynamic Provisioning \\nvolumes (DP-VOLs), and then retry the operation. If this problem persists, call the HSSC.
-497162383	5	6	The capacity of Dynamic Provisioning volume (DP-VOL) is insufficient.\\nCheck volume capacity for the DP-VOL.
-497162382	5	6	Shared memory is being initialized.\\nWait for a while, and then retry the operation.
-497162381	5	6	The pool is in an abnormal state.\\nRecover the pool, then retry the operation.
-497162380	5	6	LDEV format is being executed in the specified volume.\\nRetry the operation after the formatting operation has completed.
-497162352	1	6	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-497162319	5	6	The number of Dynamic Provisioning volumes that can be associated with a single pool \\nexceeds the maximum.\\nVerify the current configuration of association.
-497162295	5	6	The storage system is releasing the association internally.\\nWait for a while, and then retry the operation.
-497162264	1	3	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
-497162198	5	3	A parity group that is not mounted is included in the specified parity groups.\\nSpecify a different parity groups.
-497162197	5	3	A parity group that is not blocked is included in the specified parity groups.\\nCheck the status of the specified parity groups.
-497162165	5	6	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.\\nWait for a while, click [Refresh] or [Refresh All] on the [File] menu of the Storage \\nNavigator window, and then verify the pool status on the pool window. If this problem \\npersists, call the HSSC.
-497162164	5	6	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 Thin Image 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 Dynamic Provisioning volume is in operation.\\nIf the pool cannot be deleted, do the following.\\n- Check the installation status of the V-VOL management area when the V-VOL management \\narea is not initialized.\\n- Check the installation status of the V-VOL management area when the V-VOL management \\narea is not installed.\\n- Delete the Thin Image pair if it still remains in the pool.\\n- Delete the Thin Image pair if the P-VOL still remains in the pool.\\n- Restore the status of Pool-VOLs in the pool when the pool is blocked, and then \\nretry the operation.\\n- Update the display content and confirm that the usage rate of the pool is zero, \\nand then retry the operation.
-497162163	5	6	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.\\nWhen the pool threshold cannot be changed, do the following:\\n- Update the display content and confirm the usage rate of the pool.\\n- Wait for shrinking the pool to end if it is shrinking. Then retry the operation.\\n- Check the status of the Pool-VOL in the pool and restore it if it is blocked. Then \\nretry the operation.
-497161451	5	6	The pool is blocked.\\nRecover the pool, then retry the operation.
-497161450	5	6	The specified volume cannot be processed because it is blocked.\\nRecover the volume, then retry the operation. 
-497161428	1	6	The specified volume cannot be processed, because it is not associated with a pool.\\nAssociate the volume with a pool, then retry the operation. If this problem persists, \\nplease call the HSSC.
-497161427	1	6	The specified volume is currently used by ShadowImage.\\nWait until the processing of ShadowImage is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-497161426	1	6	The specified volume is currently used by Thin Image.\\nWait until the processing of Thin Image is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-497161425	1	6	The specified volume is currently used by Volume Migration or nondisruptive migration.\\nRelease the Volume Migration or nondisruptive migration setting, and then retry the \\noperation. If this problem persists, contact the HSSC.
-497161424	1	6	The specified volume is currently used by TrueCopy.\\nWait until the processing of TrueCopy is complete, and then retry the operation. \\nIf this problem persists, call the HSSC.
-497161423	1	6	The specified volume is currently used by Universal Replicator.\\nWait until the processing of Universal Replicator is complete, and then retry the \\noperation. \\nIf this problem persists, call the HSSC.
-497161238	5	6	The specified volumes contain a quorum disk.\\nRelease the quorum disk, and then retry the operation.
-497161237	5	6	The specified volumes contain a global-active device pair volume.\\nDelete the global-active device pair, and then retry the operation.
-497161236	5	6	The specified volumes contain a global-active device pair volume.\\nDelete the global-active device pair, and then retry the operation.
-497161209	5	6	The item to be formatted includes a Dynamic Provisioning volume (DP-VOL). However, \\nthe DP-VOL cannot be formatted because there is a pool that has been blocked.\\nRestore the pool that has been blocked by the Dynamic Provisioning function.
-497161203	1	6	The zero page reclaiming is disabled on the storage system.\\nCall the HSSC.
-496334994	5	6	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-496334904	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-496334900	5	6	The specified volume is invalid.\\nVerify the setting of LDKC, CU, and LDEV.
-496334899	5	6	The number of the specified page ranges is invalid.\\nVerify the specified page ranges.
-496334898	5	6	The number of pages is invalid.\\nVerify the total length of each specified page range.
-496300425	5	6	The specified LDEV or parity group belongs to a resource group that you do not have \\npermission to access.\\nLog out, and then log back in with access to the resource group containing the specified \\nLDEV or parity group.
-496300396	5	6	The specified operation cannot be performed because there is an LDEV that has been \\nset to a different resource group.\\nSelect an LDEV allocated to the same resource group.
-496245652	5	6	The specified operation cannot be executed, because the LDEV capacity exceeds the \\nmaximum reserved pool capacity.\\nCheck the specified LDEV capacity, then retry the operation.
-496245651	5	6	The specified LDEV capacity is invalid.\\nCheck the specified LDEV capacity, and then retry the operation.
-496245650	5	6	Failed to expand the V-VOLs, because it took time for the processing. \\nRetry the operation.
-496245649	5	6	The specified LDEV capacity exceeds the threshold. \\nCheck the specified LDEV capacity, then retry the operation.
-496245648	5	6	You cannot expand the V-VOLs for the volumes that are being used in the following \\nprogram products:\\n- ShadowImage\\n- Thin Image\\n- Volume Migration\\n- TrueCopy\\n- Universal Replicator\\n- Global-active device\\nChange the setting not to use the volumes of the following program products as a \\ntarget of expanding V-VOL, and then retry the operation. \\n- ShadowImage\\n- Thin Image\\n- Volume Migration\\n- TrueCopy\\n- Universal Replicator\\n- Global-active device
-496245626	5	6	The specified operation cannot be executed, because the maximum reserved pool capacity \\nis incorrect.\\nCheck the maximum reserved pool capacity, then retry the operation.
-496245625	5	6	The specified operation cannot be executed, because the pool status is invalid.\\nCheck the pool status.
-496245624	5	6	The specified operation cannot be executed, because the threshold of the pool exceeds \\nthe maximum.\\nCheck the threshold of the pool, then retry the operation.
-496245623	5	6	The specified operation cannot be executed, because it exceeds the maximum reserved \\npool capacity.\\nCheck the maximum reserved pool capacity, then retry the operation.
-496245622	5	6	The operation cannot be performed because the specified logical volume is a quorum disk.\\nVerify the specified logical volume, and then retry the operation.
-496245621	5	6	The operation cannot be executed, because RAID levels of the specified logical volumes \\ndo not match. \\nCheck the specified logical volume, then retry the operation.
-496245620	5	6	The operation cannot be executed, because a blocked pool volume exists in the pool \\nto which the specified logical volume is to be added. \\nRelease the blocked status of the pool volume in the pool, then retry the operation. 
-496245619	5	6	The operation cannot be executed, because the specified logical volume is the top \\npool volume.\\nCheck the specified logical volume, then retry the operation.
-496245618	5	6	The operation cannot be executed, because the number of tiers of the specified logical \\nvolume is incorrect.\\nCheck the specified logical volume, then retry the operation.
-496245617	5	6	The operation cannot be performed because Dynamic Tiering is disabled for the pool \\nassociated with the specified DP-VOLs.\\nVerify the setting for the pool associated with the specified DP-VOLs.
-496245595	5	6	The operation cannot be performed because the available period to stop shrinking \\npools has passed.\\nVerify the pool status.
-496245588	5	5	The frequency distribution data cannot be obtained because it is not complete.\\nWait for a while, then retry the operation.
-496245587	5	5	The frequency distribution data cannot be obtained. There is no monitoring information \\nof the specified pool or DP-VOL.\\nCollect the information, and then retry the operation.
-496245586	5	5	The frequency distribution data cannot be obtained. There is no monitoring information \\nof the specified DP-VOL because it is created after collecting monitoring information \\nof a pool.\\nCollect the information, and then retry the operation.
-496245564	5	5	The frequency distribution data cannot be obtained. There is no monitoring information \\nof the specified DP-VOL because one of the following is performed:\\n- Quick Restore of ShadowImage\\n- Volume Migration\\n- Initial copy of True Copy\\n- Initial copy of global-active device\\nCollect the information, and then retry the operation.
-496245563	5	6	The specified MP Unit has been blocked.\\nRecover the blocked MP Unit, and then specify the unit again.
-496245562	5	6	The selected MP unit is not mounted.\\nSpecify a different MP Unit.
-496245560	5	5	The specified POOL ID or the LDEV ID does not exist.\\nClick [Refresh], then check the configuration information again.
-496245559	5	5	The frequency distribution data cannot be obtained. There is no monitoring information \\nof the specified DP-VOL because the shared memory for collecting monitoring information \\nis depleted.\\nVerify the total capacity of Dynamic Provisioning volumes, and then retry the operation.
-496245558	5	6	The specified operation cannot be performed due to the following reasons:\\n - The specified logical volume is not blocked.\\nCheck the specified logical volume status.
-496245557	5	5	The pool is blocked.\\nRecover the pool.
-496245556	5	5	Dynamic Tiering is disabled for the specified pool or a pool associated with the \\nspecified DP-VOL.\\nVerify the pool setting.
-496245555	1	6	The DKC is set to the state of suppression of pool shrinking.\\nContact the HSSC.
-496245533	1	6	The DKC is set to the state of suppression of tier relocation starting.\\nPlease call the HSSC.
-496245532	5	6	The operation cannot be executed because the specified pool is now in zero page reclaiming process.\\nWait until the zero pages are reclaimed, and then retry, or cancel the operation.
-496245531	5	6	The operation cannot be executed because the pool where the Dynamic Provisioning \\nVolume belongs to is now in pool shrinking or tier relocation process.\\nWait until the pool is shrunk or the tier is relocated, or abort it.
-496245530	1	6	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.\\nVerify the following items, and then retry the operation. \\n- The threshold value of the pool.\\n- The pool status.
-496245529	1	6	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 DP-VOL associated with the specified pool is high.\\nTake any of the following actions, and then retry the operation. If this problem \\npersists, contact the HSSC.\\n- Restore the pool volume to the normal status.\\n- Reduce the I/O load of the DP-VOL.
-496245528	1	6	The operation cannot be performed because the DP-VOL or the Thin Image pair of the \\nspecified pool has one of the following problems.\\n- The DP-VOL is blocked.\\n- The DP-VOL is being formatted.\\n- The Thin Image pair is being deleted.\\nVerify the status of the DP-VOL or the Thin Image pair, and then retry the operation. \\nIf this problem persists, contact the HSSC.
-496245527	1	3	The storage system requires maintenance (the cache memory is blocked, or the pool \\nis in the pool shrinking suppression status.)\\nCall the HSSC.
-496245526	5	5	A sufficient Cache Control Device cannot be allocated to the target volume.\\nDelete unnecessary volumes, then retry the operation. If this problem persists, please \\ncall the HSSC.
-496245525	5	6	The pool shrinking was aborted because the operation to stop pool shrinking was executed.\\nCheck the pool status.
-496245524	5	6	The operation cannot be executed because the storage system is in the process of \\nshutting down. \\nPower on the storage system, then retry the operation.
-496245500	5	6	The operation cannot be executed because the specified pool is in the process of \\npool shrinking.\\nWait until the pool is shrunk, or stop the operation.
-496245499	5	5	The operation failed because the specified resource was not installed.\\nCheck if the specified resource is installed or not.
-496245498	5	5	The operation failed because the specified name was already registered.\\nChange the name to another one, then retry the operation.
-496245493	5	6	A pool volume cannot be set to the specified pool because the number of drive types \\nexceeds the supported number. \\nCheck the number of the supported drive types, then retry the operation.
-496245471	5	6	The multi tier pool cannot be disabled because the RAID level of each tier is different.\\nCheck the configuration of the supported RAID levels, then retry the operation.
-496245470	5	6	Failed to delete the pool. Pools cannot be deleted when they are in the following status:\\n- Deleting a pair of Thin Image is in progress.\\n- Deleting a volume of Dynamic Provisioning is in progress.\\nWait until the processing is complete, and then retry the operation.
-496245469	5	6	Failed to delete the pool. Pools cannot be deleted when they are in the following status:\\n- Pairs of Thin Image are remaining.\\n- Volumes of Dynamic Provisioning are remaining.\\nDelete the following pairs or volumes if any, and then retry the operation.\\n- Thin Image pairs\\n- Dynamic Provisioning volumes
-496245468	5	6	The pool cannot be deleted because pools are not deleted when any pool volume of \\nthe specified pool is being formatted.\\nWait until the formatting is complete, and then retry the operation.
-496245467	5	6	Failed to delete the pool volume because the specified pool volume had one of the \\nfollowing problems.\\n- It is not a pool volume.\\n- The pool volume is not set to the specified pool.\\nSpecify a pool volume, or, specify a pool volume that is set to the specified pool, \\nthen retry the operation.
-496245466	5	6	The LDEV ID of the specified pool volume is invalid.\\nSpecify a different LDEV ID.
-496245464	5	6	The maintenance operation cannot be performed on the specified DP-VOLs because the \\nDP-VOLs include blocked pool volumes.\\nRestore the blocked pool VOLs.
-496245435	1	3	The software does not support the specified operation.\\nCall the HSSC.
-496245434	5	6	The operation cannot be done because the specified V-VOL is online from an EAV unsupported OS. \\nSet the specified LDEV to OFFLINE.
-496244689	5	6	An internal volume and an external volume cannot be set as pool VOLs in the specified pool.\\nVerify the pool VOLs to be set in the specified pool.
-496244664	5	6	External volumes with mixed cache mode setting, enabled and disabled, cannot be used \\nas pool volumes in an HDP pool.\\nVerify the cache mode of the subject external volumes.
-496244663	5	6	External volumes with cache mode disabled cannot be specified as pool volumes for the pool.\\nVerify the cache mode of the subject external volumes.
-496244662	1	6	The pools cannot be initialized due to one of the following reasons:\\n- The DP-VOL is used by a different program product.\\n- There is a Thin Image pair on the storage system.\\nPerform all of the following tasks, and then retry the operation.\\n- Release all settings of DP-VOL in the different program product.\\n- Release all Thin Image pairs.
-496244661	5	6	The operation failed, because the start of tier relocation operation was specified \\nfor a pool in tier relocation operation, or the stop of tier relocation operation \\nwas specified for a pool not in tier relocation operation.\\nCheck the status of the pool, then retry the operation.
-496244660	5	6	The operation cannot be done because the specified pool is using monitoring information \\nfor the tier relocation.\\nWait until the tier relocation is complete or stop the tier relocation processing, \\nand then retry the operation.
-496244659	1	2	The processing cannot continue due to an internal logical contradiction.\\nIf the same problem persists despite retrying, please call the HSSC.
-496244599	5	6	All the pool volumes cannot be deleted at the same time.\\nIf you want to delete pool volumes, leave at least one or more pool volumes.
-496244597	5	6	The specified LDEV cannot be set as a pool volume because it is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration \\nfor the pool volume, and then retry the operation.
-496244415	5	1	The setting value of Dynamic Tiering is not valid.\\nSelect a valid value for Dynamic Tiering, and then retry the operation.
-496244414	5	7	The execution mode cannot be changed because the storage system is preparing to execute \\nperformance monitoring.\\nWait for a while, and then retry the operation.
-496244410	5	6	The operation cannot be performed because the additional shared memory is  being \\ninstalled.\\nWait until the installation of additional shared memory is complete, and then retry \\nthe operation.
-496244409	5	6	The specified page range is invalid.\\nSpecify the start page number and the length of the page range within an available \\npage range of the specified volume.
-496244408	5	6	The specified page tiering level of the tiering policy is invalid.\\nVerify the specified page tiering level.
-496243735	5	6	The processing of the subject page failed because an error occurs in a different \\npage processing.\\nRetry the operation after recovering from the error.
-496243545	5	5	The operation cannot be performed because monitoring information is being changed.\\nWait for a while, and then retry the operation.
-496243543	5	5	The specified pool is not a Dynamic Provisioning pool.\\nVerify the setting of the specified pool.
-496243542	5	5	The specified volume is an internal volume.\\nSelect a different volume.
-496243541	5	5	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.\\nSpecify a pool volume, or specify a pool volume that is set to the specified pool, \\nand then retry the operation.
-496243540	5	7	The specified pool ID is invalid.\\nVerify the specified pool ID, and then retry the operation.
-496243484	5	5	The tiering policy ID or the threshold value is invalid.\\nVerify the tiering policy ID or the threshold value, and then retry the operation.
-496243483	5	5	The specified volume cannot be set as a Pool-VOL because the volume capacity does \\nnot satisfy the requirements for the Pool-VOL.\\nSelect a volume that satisfies the requirements for the Pool-VOL.
-496243481	5	5	The storage system configuration does not comply with the tiering policy.\\nAdd some pool volumes to have the configuration comply with the tiering policy, or \\nchange the set tiering policy.
-496243480	5	5	The number of the specified tiering policies is invalid.\\nVerify the number of the specified tiering policies, and then retry the operation.
-496243479	5	5	The specified tiering policies cannot be changed because the current DKCMAIN microcode \\nversion does not support the setting for the tiering policy name and for values of \\nTier 1 and Tier 3 in 1% increments.\\nContact the HSSC to update the DKCMAIN microcode. If not updating the DKCMAIN microcode, \\nfollow the directions below.\\n- Do not change the tiering policy name.\\n- Specify values of Tier 1 and Tier 3 in 10% increments.
-496243451	5	5	The operation failed because the required capacity of cache control device cannot \\nbe allocated.\\nSee the troubleshooting section in the Thin Image User Guide and reserve the cache \\ncontrol device required for the creation of Thin Image pools. If the required capacity \\nof cache control device is already reserved, call the HSSC.
-496243450	5	5	A Thin Image pool cannot be created because there are not enough resources depending \\non cache management devices.\\nDelete resources requiring cache management (external volumes, virtual volumes, and \\nP-VOLs of Thin Image pairs) so that the total number of resources is less than or \\nequal to 55,040, and then retry the operation. If this problem persists, call the HSSC.
-496242769	5	5	The operation cannot be performed because the pool volume with a system area is blocked.\\nRestore the blocked status of the pool volume with a system area, and then retry \\nthe operation.
-495344976	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
-477655002	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-477625212	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-477625181	1	5	File access error is occurred. If a file is transferred between Storage Navigator \\nand client PC, confirm that the file name does not contain invalid characters. In \\nother cases, please wait for a while, and retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
-477625180	1	5	File access error is occurred. If a file is transferred between Storage Navigator \\nand client PC, confirm that the file name does not contain invalid characters. In \\nother cases, please wait for a while, and retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
-477624965	1	5	An error occurred while compressing a file.\\nIf the problem persists despite retrying, please call the HSSC.
-477624964	1	5	An error occurred while reading a file.\\nIf the problem persists despite retrying, please call the HSSC.
-477624963	1	5	The specified file was not found. \\nIf the problem persists despite retrying, please call the HSSC.
-444484824	1	5	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or \\nsome other factor).\\nCheck the status of the storage system\\n(if the storage system is blocked, shared memory is inconsistent, or some other factor).\\nIf this problem persists, please call the HSSC.
-444484820	1	5	An error occurred while communicating with the storage system.\\nIf the same problem persists despite retrying, please call the HSSC.
-444484572	5	5	The specified operation cannot be performed due to one of the following maintenance \\noperations:\\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.\\nWait for a while, and then retry the operation.
-444482933	5	5	Processing cannot be performed because of Data Retention Utility settings.\\nRelease the setting of Data Retention Utility, then retry the operation.
-444479989	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
-444479988	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
-444455062	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444395449	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444395195	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444390646	5	5	A necessary program product is not installed.\\nInstall the necessary program product(s).
-444387726	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444387725	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444365659	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444365628	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444360791	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444360790	5	5	The number of V-VOLs that can be registered in the storage system has reached the maximum.\\nReduce the number of V-VOLs registered in the storage system, then retry the configuration \\noperation.
-444360789	5	5	The configuration cannot be changed because the LUN Path is remained in the target volume. \\nRelease the LUN Path, then change the configuration again.
-444360787	5	5	The setting process has not been executed because there is no error in this setting, \\nbut an error in the others settings. \\nCheck the error factor in the others settings.
-444306110	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444306109	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-444305147	5	5	This function is not supported.\\nCheck whether the DKCMAIN firmware version and the Storage Navigator software version \\nare mismatched.
-444297298	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
-444297269	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
-386653204	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
-386625334	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-386625333	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-386625332	1	2	An error occurred during Storage Navigator processing.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386623347	1	2	This function cannot be used by the storage partition administrator.\\nSelect another window. If you want to set this function, please contact the storage \\nadministrator.
-386623346	1	3	Because the settings across the multiple SLPRs are contained, the authority has been \\nshifted to the storage administrator from the storage partition administrator.\\nTo continue the operation, please contact the storage administrator and have the \\nsettings across the multiple SLPRs cancelled, then retry the operation. To perform \\nother operations, please select a function button.
-386623345	1	3	The resources of other SLPR(s) cannot be accessed.\\nAn error occurred during processing. If this problem persists, please call the HSSC.
-386597465	1	2	An error occurred during Storage Navigator processing.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386597464	1	2	An error occurred during Storage Navigator processing.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386563612	1	3	An error occurred while connecting to the storage system.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386563610	1	3	An error occurred while connecting to the storage system.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386563609	1	3	An error occurred while connecting to the storage system.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-386563608	1	3	A communication time-out error occurred in the storage system.\\nThe error may be caused by a temporary communication failure. Reboot the SVP or click \\n[Refresh All] on the File menu of Storage Navigator and refresh the configuration \\ninformation to recover from the error. If this problem persists, please call the HSSC.
-384810843	1	6	This functionality is not available because Server Priority Manager is not installed.\\nInstall the necessary program product.
-384776340	5	6	The specified port belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified port.
-384720595	1	5	Server Priority Manager cannot be operated from Storage Navigator because settings \\nfor Server Priority Manager have been made on this storage system from RAID Manager.\\nMake the settings from RAID Manager.\\nTo make the settings from Storage Navigator, delete all settings of Server Priority \\nManager done from RAID Manager.
-383820913	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
-263359739	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263359680	5	5	No commands are issued.\\nIf the problem persists despite retrying, please call the HSSC.
-263359648	1	5	The number of issued commands exceeds the maximum.\\nReduce the number of set demands.
-263354936	1	6	The program product is not installed.\\nInstall the program product.
-263329949	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263329917	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263329881	1	2	The mistake is found in the set parameter.\\nIf the problem persists despite retrying, please call the HSSC.
-263325175	5	5	Processing in progress.\\nWait for a while, then retry the operation.
-263325081	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263325077	5	5	The setting process has not been executed because there is no error in this setting, \\nbut an error in the others settings. \\nCheck the error factor in the others settings.
-263300005	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263299198	1	3	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-263297277	1	5	This error code is not registered.\\nIf the problem persists despite retrying, please call the HSSC.
-263270399	1	3	An error occurred while connecting to the storage system. Please retry a little later.\\nWait for a while, then retry the operation.
-263270398	1	3	A communication time-out error occurred in the storage system. Please wait for a \\nwhile, and then retry the operation.\\nWait for a while, then retry the operation.
-263269437	1	3	This function is not supported.\\nSoftware versions of DKCMAIN firmware version and Storage Navigator may not match \\neach other. Verify the software version.
-263269377	5	5	The specified logical volume does not exist.\\nSpecify an open-system volume.
-263269375	5	5	This logical volume is busy.\\nVerify the logical volume, and then retry the operation.
-263269374	1	5	This function is not supported.\\nSoftware versions of DKCMAIN firmware version and Storage Navigator may not match \\neach other. Verify the software version.
-263269372	5	5	The attribute of the logical volume has been changed by RAID Manager.\\nReview LDEV information, then retry.
-263269371	5	5	This logical volume is configured as a command device.\\nVerify the logical volume, and then retry the operation.
-263269369	1	5	A parameter error occurred.\\nIf the problem persists despite retrying, please call the HSSC.
-263269344	1	5	This error code is not registered.\\nIf the problem persists despite retrying, please call the HSSC.
-263269342	1	5	The attribute of this logical volume cannot be changed to Read/Write.\\nTo change the attribute, please call the HSSC.
-263269341	5	5	The specified volume is a TrueCopy secondary volume in COPY or PAIR status or a ShadowImage \\nsecondary volume in COPY, PAIR, COPY (SP), COPY (RS), or COPY (RS-R) status.\\nIf the pair is TrueCopy, change the status to PSUS, and then retry the operation. \\nIf the pair is ShadowImage, change the status to PSUS or PSUS (SP), and then retry \\nthe operation.
-263269340	5	5	The command was rejected, because the licensed capacity was exceeded.\\nThe currently licensed capacity is insufficient. To increase the licensed capacity, \\nbuy a new license key.
-263269338	1	5	The Reserved setting of the specified volume cannot be released.\\nTo release the Reserved setting, please call the HSSC.
-263269337	5	5	The attribute of the ShadowImage primary volume cannot be changed because the pair \\nstatus is COPY (RS-R).\\nWait until the status of the pair changes to PAIR, and then retry the operation.
-263269313	5	5	You cannot select this logical volume because it is used as a Universal Replicator volume.\\nVerify the logical volume, and then retry the operation.
-263269284	5	5	You tried to set a retention term to a logical volume whose access attribute is not \\nRead Only or Protect.\\nVerify the logical volume, and then retry the operation.
-263269283	5	5	The retention term of the logical volume cannot be shortened.\\nTo change the attribute, please call the HSSC.
-263269281	5	5	The specified retention term exceeds the maximum.\\nCorrect the retention term, then retry the operation.
-263269280	5	5	The retention term of the logical volume has been changed by RAID Manager.\\nCheck the retention term of the logical volume, then retry the operation.
-263269279	5	5	You cannot change the access attribute because a retention term is set to the specified \\nlogical volume.\\nTo change the access attribute of the logical volume to Read/Write, please call the HSSC.
-263269278	5	5	You cannot change the access attribute because the expiration lock is set to Enable.\\nSet the expiration lock to Disable, then change the access attribute.
-190144340	5	6	The specified volumes cannot be used for migration, because the specified source \\nvolume is a TrueCopy volume, and the specified target volume is an external volume.\\nSelect a different volume, and then retry the operation.
-190144318	5	6	The specified volume migration plan cannot be performed because a volume on which \\nVMA for Data Retention Utility is set is paired with a volume on which VMA is not set.\\nConfirm the settings of the specified volumes.
-190142581	1	6	If the migration source volume is a normal volume, a CVS volume of the same capacity \\nas the migration source volume cannot be specified as the migration target volume. \\nIf the migration source volume is a CVS volume, a normal volume of the same capacity \\nas the migration source volume cannot be specified as the migration target volume.\\nCheck the setting of the migration source volume and the migration target volume.
-190142575	1	5	The auto migration plans cannot be created because "None" is specified in "Sampling Term".\\nSpecify the parameters other.
-190142517	5	6	The owner ID of the storage system used by the user does not match the owner ID of \\nthe specified target volume.\\nSelect a volume that has the same owner ID.
-190142515	5	6	The specified plan is the one created by other than Storage Navigator.\\nThe specified plan cannot be released with Storage Navigator.
-190142514	5	6	The specified plan is the one created by other than Storage Navigator.\\nThe specified migration plan cannot be stopped with Storage Navigator.
-190142419	5	6	The volume(s) are already being as a data volume used by Universal Replicator.\\nSelect a different volume, and then retry the operation.
-190142418	5	6	The volume(s) are already being as a data volume used by Universal Replicator.\\nSelect a different volume, and then retry the operation.
-190139699	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190139636	5	6	The specified volumes are already used as the volumes of Thin Image.\\nSelect a different volume, and then retry the operation.
-190139635	5	6	The specified volume(s) are already being used as V-VOL(s).\\nSelect a different volume, and then retry the operation.
-190139634	5	6	The specified volume(s) are already being used as Pool-VOL(s).\\nSelect a different volume, and then retry the operation.
-190139633	5	6	The specified volumes are already used as the volumes of Thin Image.\\nSelect a different volume, and then retry the operation.
-190139632	5	6	The specified volume(s) are already being used as V-VOL(s).\\nSelect a different volume, and then retry the operation.
-190139631	5	6	The specified volume(s) are already being used as Pool-VOL(s).\\nSelect a different volume, and then retry the operation.
-190139606	5	6	The specified volumes are already used as the volumes of Thin Image.\\nSelect a different volume, and then retry the operation.
-190139544	5	6	The volume(s) are already being used as a JNL volume by Universal Replicator.\\nSelect a different volume, and then retry the operation.
-190139543	5	6	The volume(s) are already being used as a JNL volume by Universal Replicator.\\nSelect a different volume, and then retry the operation.
-190139542	5	6	The specified source volume is a Universal Replicator volume, andthe specified target \\nvolume is an external volume. Therefore, the specified volumes cannot be used for \\nmigration.\\nSelect a different volume, and then retry the operation.
-190139445	5	6	The specified volume cannot be migrated, because it is in the shredding operation.\\nRetry the operation after the shredding is completed.
-190139418	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190139417	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190139412	5	6	The specified volume is used as a Delta resync volumefor Universal Replicator.\\nSelect a different volume, and then retry the operation.
-190139411	5	6	The volume specified as a migration target is used as a volume of Delta resync for \\nUniversal Replicator.\\nThe volume of Delta resync cannot be specified as a migration target. See "Supported \\nand prohibited source and target volumes" in the Volume Migration User Guide.
-190138608	5	6	Migration between external volumes with different cache modes is invalid.\\nSelect a different volume, and then retry the operation.
-190111829	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
-190111828	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-190111827	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190109842	1	2	This function cannot be used by the storage partition administrator.\\nSelect a different window. If you want to use this function, contact the HSSC.
-190083960	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190083959	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
-190051131	5	6	The storage system is busy (internal processing).\\nRetry the operation. If this problem persists, contact the HSSC.
-190050107	1	3	An error occurred on the DKC side.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
-190050105	1	3	An error occurred while connecting to the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-190050104	1	3	An error occurred while connecting to the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-190050103	1	3	A communication time-out error occurred in the storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
-189217042	5	6	The specified volume(s) are the leaf volume(s) of ShadowImage.\\nSelect a different volume, and then retry the operation.
-189214997	5	6	The specified volume(s) are already being used as of Dynamic Provisioning volume \\n(DP-VOL) (s).\\nSelect a different volume, and then retry the operation.
-189214996	5	6	The specified volume(s) are already being used as of Dynamic Provisioning volume \\n(DP-VOL) (s).\\nSelect a different volume, and then retry the operation.
-189214931	5	6	The volume specified as a migration source cannot be used, because it is in quick \\nformatting.\\nRetry the operation after the quickformat is completed.
-189214930	5	6	The volume specified as a migration target cannot be used, because it is in quick \\nformatting.\\nRetry the operation after the quickformat is completed.
-189214251	5	6	The specified volume cannot be moved because it is a Dynamic Provisioning volume \\nthat is not associated with a pool.\\nSelect a different volume, and then retry the operation.
-189214250	5	6	The specified volume cannot be moved because it is a Dynamic Provisioning volume \\nthat is not associated with a pool.\\nSelect a different volume, and then retry the operation.
-189214248	5	6	Migration cannot be performed because the Dynamic Provisioning volume that is the \\nmigration source and the Dynamic Provisioning volume that is the migration target \\nare contained in the same pool.\\nCheck the setting of the specified volume.
-189214247	5	6	The specified following volumes cannot be migrated. The migration source volume is \\nshared by a P-VOL or an S-VOL of Universal Replicator or TrueCopy, and the migration \\ntarget volume is a Dynamic Provisioning volume.\\nSelect a different volume, and then retry the operation.
-189214221	5	6	Because the composition is being backed up, a volume concerned cannot be moved.\\nWait for a while, and then retry the operation.
-189214156	5	6	The specified volume cannot be used, because it is a volume of Dynamic Provisioning \\nwhose capacity is being added.\\nCheck the specified volume capacity after the completion of the capacity expanding \\noperation.
-189214155	5	6	The volume specified as a migration target cannot be used, because it is a volume \\nof Dynamic Provisioning in capacity expanding.\\nConfirm the capacity of the volume specified as a migration target after the capacity \\nexpanding operation is completed.
-189214132	5	6	The configuration changing processes are conflicting at DKC.\\nCheck if the configuration changing process by the RAID Manager, the Volume Migration, \\nor the Quick Restore is not in operation, and then retry the operation.
-189214124	5	6	The volume specified as a migration source cannot be used, because it is a volume \\nof Dynamic Provisioning in zero page reclaiming.\\nRetry the operation after the zero data page reclaiming is completed.
-189214123	5	6	The volume specified as a migration target cannot be used, because it is a volume \\nof Dynamic Provisioning in zero page reclaiming.\\nRetry the operation after the zero data page reclaiming is completed.
-189214004	5	6	The volume specified as a migration source cannot be used because it is a quorum disk.\\nVerify the specified volume.
-189214003	5	6	The volume specified as a migration target cannot be used because it is a quorum disk.\\nVerify the specified volume.
-189214002	5	6	The pair operation cannot be performed because the volume specified as a migration \\nsource is a reserved volume of global-active device or used by a global-active device pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
-189214001	5	6	The pair operation cannot be performed because the volume specified as a migration \\ntarget is a reserved volume of global-active device or used by a global-active device pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
-189213259	5	6	The specified volume is a volume of using two mirrors, which is included in the multi-target, \\nthe cascade, or the Delta resync configuration of a Universal Replicator pair.\\nSpecify a different volume.
-189213258	5	6	The specified volume is a volume of using two mirrors, which is included in the multi-target, \\nthe cascade, or the Delta resync configuration of a Universal Replicator pair.\\nSpecify a different volume.
-189213257	5	6	The specified volume is a volume of using two mirrors, which is included in the multi-target, \\nthe cascade, or the Delta resync configuration of a Universal Replicator pair.\\nSpecify a different volume.
-188297454	5	6	The volume specified as a migration target volume has an LU path setting.\\nSelect a different volume, and then retry the operation.
-188297431	5	6	The number of target volumes that could be executed at once exceeds the maximum.\\nCorrect the number of manual migration instructions to 8 or less, and then retry \\nthe operation.
-188297364	5	6	The volume specified as a migration source cannot be used, because the DP Pools are \\nbeing initialized.\\nWait until the initialization of the DP pools is completed, and then retry the operation.
-188297363	5	6	The volume specified as a migration target cannot be used, because the DP Pools are \\nbeing initialized.\\nWait until the initialization of the DP pools is completed, and then retry the operation.
-188262863	5	6	The specified LDEV belongs to a resource groupthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-188262862	5	6	The specified LDEV belongs to a resource groupthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-188262861	5	6	The specified LDEV belongs to a resource groupthat you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
-188262860	5	6	The specified parity group belongs to a resource groupthat you do not have permission \\nto access.\\nLog out, and then log back in with access to the resource group containing the specified \\nparity group.
-188262804	5	6	LDEVs specified as migration source volume and target volume, or parity groups contain \\nthe LDEVs, belong to different resource groups.\\nMake the auto migration plan again.
-188207928	5	6	The operation failed, because the current firmware version does not support the capacity \\nof the specified source volume.\\nCheck the firmware version of the storage system.
-188207927	5	6	The operation failed, because the current firmware version does not support the capacity \\nof the specified target volume.\\nCheck the firmware version of the storage system.
-188207898	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
-188207034	5	6	The volume specified as a migration source cannot be used because the volume settings \\nfor the online data migration are not valid.\\nVerify the settings for the online data migration, and then retry the operation.
-188207033	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-188207032	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
-187307408	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
-186412705	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
-66816444	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-66816413	1	3	An error occurred during SVP processing. If this problem persists, please call the HSSC.\\nIf the problem persists despite retrying, please call the HSSC.
-66786500	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
-51338649	5	5	An error occurred during SVP processing.\\nIf this problem persists, contact the HSSC.
-51338617	5	5	The SVP is busy.\\nWait for a while, and then retry the operation.
-51333875	5	5	An error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
-51333777	5	5	The setting cannot be applied because there is an error in a different setting.\\nVerify and correct the error in the other setting, and then retry the operation.
-51308705	5	5	An internal logic contradiction occurred.\\nIf this problem persists, contact the HSSC.
-51307898	5	5	The SVP is busy.\\nWait for a while, and then retry the operation.
-51305977	5	5	An unregistered error occurred.\\nIf this problem persists, contact the HSSC.
-51279100	5	5	An unexpected error occurred on the external module.\\nIf this problem persists, contact the HSSC.
-51279099	1	3	A communication time-out error occurred.\\nWait for a while, and then retry the operation.
-51279098	5	5	A communication error occurred.\\nWait for a while, and then retry the operation.
-51278139	5	5	An error occurred during communication with the storage system.\\nIf this problem persists, contact the HSSC.
-51278137	1	5	The specified function is not supported.\\nVerify the firmware version of the DKCMAIN and the software version of the SVP.
-51271133	5	5	The specified port is being initialized.\\nWait for a while, and then retry the operation.
6369996	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
6369997	5	6	There is no monitoring data. It might be deleted by another user's operation.\\nChange the monitoring switch to "Enable" for collecting data, then perform the operation.
6373806	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
6373807	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
6403663	1	2	This function cannot be used by the storage partition administrator.\\nSelect another window. If you want to set this function, please contact the storage \\nadministrator.
6403664	1	3	Because the settings across the multiple SLPRs are contained, the authority has been \\nshifted to the storage administrator from the storage partition administrator.\\nTo continue the operation, please contact the storage administrator and have the \\nsettings across the multiple SLPRs cancelled, then retry the operation. To perform \\nother operations, please select a function button.
6403665	1	3	The resources of other SLPR(s) cannot be accessed.\\nAn error occurred during processing. If this problem persists, please call the HSSC.
7322350	1	5	A monitoring switch cannot be enabled with the specified gathering interval.\\nChange the gathering interval, and retry the operation.
7322351	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
8198857	1	3	Because the settings across the multiple SLPRs are contained, the authority has been \\nshifted to the storage administrator from the storage partition administrator.\\nIf the problem persists despite retrying, please call the HSSC.
8198858	1	3	The resources of other SLPR(s) cannot be accessed.\\nIf the problem persists despite retrying, please call the HSSC.
9093734	1	5	0 cannot be specified in all the fields.\\nCorrect the settings, and then retry the operation.
9093735	1	5	The Management Server does not support IPv6.\\nCorrect the settings, then retry the operation.
9206097	1	6	The operation cannot be performed because a resource group is not locked.\\nIf the same problem persists despite retrying, please call the HSSC.
235573546	1	5	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or \\nsome other factor).\\nCheck the status of the storage system\\n(if the storage system is blocked, shared memory is inconsistent, or some other factor).\\nIf this problem persists, please call the HSSC.
235573550	1	5	An error occurred while communicating with the storage system.\\nIf the same problem persists despite retrying, please call the HSSC.
235573798	5	5	The specified operation cannot be performed due to one of the following maintenance \\noperations:\\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.\\nWait for a while, and then retry the operation.
235575437	5	5	Processing cannot be performed because of Data Retention Utility settings.\\nRelease the setting of Data Retention Utility, then retry the operation.
235578381	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
235578382	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
235662921	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235670644	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235670645	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235692711	1	5	An error occurred during SVP processing.\\nContact the HSSC.
235692742	1	2	An error occurred while opening the file.\\nIf the problem persists despite retrying, please call the HSSC.
235692743	1	2	An error occurred while deleting the file.\\nIf the problem persists despite retrying, please call the HSSC.
235692777	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235692958	1	5	An error occurred while compressing the file.\\nIf the problem persists despite retrying, please call the HSSC.
235697579	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235697580	5	5	The number of V-VOLs that can be registered in the storage system has reached the maximum.\\nReduce the number of V-VOLs registered in the storage system, then retry the configuration \\noperation.
235697581	5	5	The configuration cannot be changed because the LUN Path is remained in the target volume. \\nRelease the LUN Path, then change the configuration again.
235697583	5	5	The setting cannot be applied because there is no error in this setting but an error \\nin a different setting.\\nVerify and correct the error in the different setting, and then retry the operation.
235752260	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
235753223	5	5	This function is not supported.\\nCheck whether the DKCMAIN firmware version and the Storage Navigator software version \\nare mismatched.
235761072	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
235761101	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
268211270	5	6	The selected MP unit is not mounted.\\nVerify the configuration, and then select a mounted MP unit.
268211271	5	6	The selected MP unit is blocked.\\nRecover the blocked MP unit, and then retry the operation.
268266047	5	6	The selected MP unit is not mounted.\\nVerify the configuration, and then select a mounted MP unit.
268266048	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
268266049	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
325191627	5	5	The configuration information of the Virtual Storage Machine has changed.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
380381033	5	6	The operation cannot be performed because the specified volume is used as an external \\nvolume that is mapped for the online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
398782550	1	5	An error occurred while communicating with the storage system.\\nIf the same problem persists despite retrying, please call the HSSC.
398871921	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398872175	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398879644	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398879645	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398901711	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398901742	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398906579	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398906583	5	5	The setting process has not been executed because there is no error in this setting, \\nbut an error in the others settings. \\nCheck the error factor in the others settings.
398961260	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
398962223	5	5	This function is not supported.\\nCheck whether the DKCMAIN firmware version and the Storage Navigator software version \\nare mismatched.
398970101	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
403127810	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
426023853	5	5	The specified operation cannot be executed because the LDEV shredding or the LDEV \\nformat is being executed.\\nRetry the operation after the process is completed.
426023882	5	5	The attribute of the pool volume cannot be changed.\\nSelect another logical volume.
426023883	5	5	The attribute of the Thin Image secondary volume cannot be changed, because the pair \\nstatus is not PAIR or PSUS.\\nChange the status of the Thin Image pair to PAIR or PSUS, and then retry the operation.
426023884	5	5	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 Thin Image pair whose status is RCPY.\\n-The specified volume is the secondary volume of a Thin Image pair whose status is \\nnot PAIR or PSUS.\\nChange the status of the Thin Image pair to PAIR or PSUS, and then retry the operation.
426023888	5	5	The access attribute cannot be changed, because the status of the specified Universal \\nReplicator volume is in PAIR or in COPY.\\nRelease or suspend the Universal Replicator volume.
426023913	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
426023914	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
426023915	1	5	The specified logical volume is blocked.\\nRestore the blockade status of the logical volume.
426023920	5	5	The protection period is set to this logical volume.\\nMake the setting to another logical volume.
426023946	5	5	This logical volume is busy.\\nWait for a while, then retry the operation.
426023947	5	5	This logical volume is busy.\\nVerify the logical volume, and then retry the operation.
426023948	5	5	The access attribute of the logical volume has already been changed.\\nSee the Data Retention Utility window and check the following about the logical volume \\nyou have selected.\\n- The access attribute must be Read/Write\\n- The logical volume must be able to be specified as an S-VOL\\n- You must be able to set a path to the logical volume using the RAID Manager or \\nStorage Navigator\\n- No mode is set using the RAID Manager
426023950	5	5	This logical volume is configured as a command device.\\nVerify the logical volume, and then retry the operation.
426023975	5	5	The emulation type of the logical volume is not OPEN-V.\\nSelect a logical volume whose emulation type is OPEN-V.
426023981	5	5	The specified logical volume is blocked, or the LDEV is being formatted or shredded.\\nRetry the operation after the logical volume has recovered from the blocked status \\nor after the LDEV has been formatted or shredded.
426024004	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
427777710	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
427812305	5	5	The setting operation cannot be done because all LDEVs allocated to the resource \\ngroup have no access right for the resource group.\\nVerify the available LDEVs.
427896869	5	5	The attribute cannot be changed because the selected LDEVs belong to a parity group \\nwith the accelerated compression enabled.\\nSelect different LDEVs.
427896870	5	5	The attribute of deduplication system data volumes cannot be changed.\\nSelect different LDEVs.
549982117	5	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
549982118	5	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
549982119	5	5	The parity group ID of the selected parity group is not valid.\\nVerify the parity group ID, and then retry the operation.
549982120	5	5	The selected drive is not valid.\\nVerify the drive, and then retry the operation.
549982121	5	5	The specified RAID level or number of concatenated parity groups is not valid.\\nVerify the RAID level or the number of concatenated parity groups, and then retry \\nthe operation.
549982122	5	5	The entered parity group ID is not valid.\\nVerify the parity group ID, and then retry the operation.
549982123	5	5	No drive box is specified.\\nSpecify a drive box, and then retry the operation.
549982124	5	5	The number of the specified drive boxes is not valid.\\nVerify the number of drive boxes that can be set, and then retry the operation.
549982125	5	5	The specified drive box does not exist.\\nSpecify a drive box that can be set, and then retry the operation.
549982147	5	6	An error occurred during communication with the storage system.\\nRetry the operation. If the problem persists, contact the HSSC.
550071489	5	5	An error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
550071490	5	5	The specified operation cannot be performed because the volume is being formatted \\nor shredded, or the quick format is being prepared.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071491	5	5	The specified operation cannot be performed because the volume is in the data copy \\nprocess (drive copy).\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071492	5	5	The specified operation cannot be performed because the cache status is changing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071493	5	5	The specified operation cannot be performed because the status of the MP unit is changing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071494	5	5	The specified operation cannot be performed because the status of the DKB is changing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071495	5	5	The specified operation cannot be performed because the status of the CHB is changing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071496	5	5	The specified operation cannot be performed because Verify LDEVs is in process.\\nIf this problem persists, contact the HSSC.
550071497	5	5	The specified operation cannot be performed because the volume is in the PIN status.\\nIf this problem persists, contact the HSSC.
550071498	5	5	The specified operation cannot be performed because the drive box power supply is \\nin the abnormal state.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071520	5	5	The specified operation cannot be performed because the controller board of the MP \\nunit is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071521	5	5	The specified operation cannot be performed because the MP unit is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071522	5	5	The specified operation cannot be performed because the CHB is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071523	5	5	The specified operation cannot be performed because the port is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071524	5	5	The specified operation cannot be performed because the DKB is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071525	5	5	The specified operation cannot be performed because the SAS port is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071526	5	5	The specified operation cannot be performed because the drive is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071527	5	5	The specified operation cannot be performed because the cache memory is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
550071528	5	5	An encryption key cannot be obtained from the key management server.\\nIf this problem persists, contact the HSSC.
550071529	5	5	The specified operation cannot be performed because there are not enough encryption \\nkeys that are not used.\\nIf this problem persists, contact the HSSC.
550071551	5	5	The specified operation cannot be performed because the selected parity group uses \\na spare drive.\\nWhen creating a parity group, specify drives in the free status, and then retry the \\noperation.\\n-When deleting a parity group, restore the drive in the data status, and then retry \\nthe operation.
550071553	5	5	The parity group ID of the selected parity group is not valid.\\nVerify the parity group ID.
550071554	5	5	The RAID level of the selected parity group is not valid.\\nVerify the RAID level.
550071555	5	5	The CLPR of the selected parity group is not valid.\\nVerify the CLPR.
550071556	5	5	The selected drive box or drive is not valid.\\nVerify the drive box or drive.
550071557	5	5	The operation cannot be performed because an error occurred on the storage system.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550071558	5	5	The specified parity group does not exist.\\nVerify the settings.
550071559	5	5	The specified parity group cannot be deleted because it contains a pair of Volume \\nMigration, ShadowImage, or Thin Image.\\nDelete the pair of Volume Migration, ShadowImage or Thin Image, and then retry the \\noperation.
550071560	5	5	The specified parity group cannot be deleted because it contains an LDEV containing \\na command device defined by a remote replication pair.\\nRemove the command device defined by the remote replication pair, and then retry \\nthe operation.
550071583	5	5	The specified parity group or LDEV cannot be deleted because it contains a primary \\nvolume of a global-active device pair.\\nDelete the global-active device pair, and then retry the operation.
550071584	5	5	The specified parity group or LDEV cannot be deleted because it contains a secondary \\nvolume of a global-active device pair.\\nDelete the global-active device pair, and then retry the operation.
550071585	5	5	The specified operation cannot be performed because the specified parity groups or \\nvolumes contain quorum disks used by global-active device pairs.\\nRelease the quorum disks, and then retry the operation.
550071586	5	5	The specified parity group cannot be deleted because it contains a pool volume.\\nDelete the pool volume, and then retry the operation.
550071587	5	5	The specified parity group cannot be deleted because it contains a volume on which \\nVolume Security is set.\\nRelease the Volume Security setting, and then retry the operation.
550071588	5	5	The specified parity group cannot be deleted because it contains a volume on which \\nData Retention Utility is set.\\nRelease the Data Retention Utility setting, and then retry the operation.
550071589	5	5	The operation cannot be performed because a different application is running.\\nWait until the processing of the application is complete, and then retry the operation.
550071590	5	5	The resource group to which the selected parity group or LDEV belongs is locked by \\na different user.\\nUnlock the resource group.
550071591	5	5	The user authentication is not performed.\\nLog in again.
550071613	5	5	The specified operation cannot be performed because the specified parity groups or \\nvolumes contain journal volumes.\\nDelete the journal volumes and the Universal Replicator pairs that belong to the \\njournal volumes, and then retry the operation.
550071614	5	5	The selected parity group or LDEVs cannot be deleted because they contain a command \\ndevice that is used by an extended consistency group of Universal Replicator.\\nDelete journal groups that use the command device from the extended consistency group, \\nand then retry the operation.
550071615	5	5	The selected parity group or LDEVs cannot be deleted because they contain a remote \\ncommand device that is used by a mirror of a journal group.\\nRelease the assignment of the remote command device to the mirror of the journal \\ngroup, and then retry the operation.
550071616	5	5	The selected parity group or LDEVs cannot be deleted because they contain a volume \\non which LDEV formatting is not performed.\\nFormat the volume, and then retry the operation.
550071617	5	5	The operation cannot be performed because powering off the storage system is in process.\\nAfter the powering off process is complete, power on the storage system, and then \\nretry the operation.
550071618	5	5	The selected parity group or LDEVs cannot be deleted because they contain an LDEV \\nwhose encryption key information is not valid.\\nRestore the encryption key from a backup file, and then retry the operation.
550071619	5	5	The selected parity group or LDEVs cannot be deleted because they contain an LDEV \\nwhose encryption key information is not valid.\\nRestore the encryption key from a backup file, and then retry the operation.
550071620	5	5	The operation cannot be performed because the storage system is busy.\\nWait for a while, and then retry the operation.
550071621	5	5	No more spare drives can be set because the number of spare drives that are set has \\nreached the maximum.\\nVerify the number of the spare drives, and then retry the operation.
550071622	5	5	The selected drive is not mounted.\\nVerify the selected drive.
550071644	5	5	The entered parity group ID is already used.\\nVerify the parity group ID, and then retry the operation.
550071645	5	5	The selected CLPR is not mounted.\\nVerify the selected CLPR.
550071646	5	5	The selected drive is already used.\\nSelect a different drive.
550071647	5	5	The selected drive is not a spare drive.\\nSelect a spare drive.
550071676	5	5	The specified LDEV ID is not valid.\\nVerify the specified LDEV.
550071677	5	5	The entered LDEV capacity is not valid.\\nVerify the LDEV capacity.
550071680	5	5	The entered LDEV capacity is not valid.\\nVerify the LDEV capacity.
550071684	5	5	An external volume mapped for the online data migration or an external volume with \\nthe Data Direct Mapped attribute cannot be created because the entered LDEV capacity \\nis not the same as the external volume group.\\nEnter a value of the LDEV capacity the same as the external volume group.
550071706	5	5	An LDEV with the same capacity as the parity group or external volume group cannot \\nbe created because there is an LDEV in the parity group or the external volume group.\\nChange the LDEV capacity.
550071709	1	5	The LDEV created in the external volume group cannot be restored.\\nVerify that there is any blocked part.
550071710	5	5	The specified MP unit ID is outside the setting range.\\nVerify the specified MP unit.
550071712	5	5	The specified LDEV is used as a system disk.\\nVerify the specified LDEV.
550071713	5	5	The operation cannot be performed because any of the following items differs between \\nLDEVs on the migration source storage system and the migration target storage system:\\n- Serial number\\n- Controller ID\\n- SSID\\n- CVS configuration\\n- LDEV number\\nVerify the settings.
550071737	5	5	A volume cannot be added because the encryption key is not valid.\\nContact the HSSC.
550071738	5	5	There is an LDEV that is being shredded in the specified parity group.\\nWait until the shredding is complete, and then retry the operation.
550071739	5	5	There is an LDEV that is being formatted in the specified parity group.\\nWait until the formatting is complete, and then retry the operation.
550071740	5	5	There is an LDEV that is being quick formatted in the specified parity group.\\nWait until the quick formatting is complete, and then retry the operation.
550071741	5	5	The specified parity group is in the data copy process (correction copy).\\nWait until the correction copy is complete, and then retry the operation.
550071742	5	5	The operation cannot be performed because the parity group or the external volume \\ngroup is being used by a different operation.\\nWait for a while, and then retry the operation.
550071743	5	5	The operation cannot be performed because the storage system is in internal process.\\nWait for a while, and then retry the operation.
550071745	5	5	The specified LDEV is not mounted.\\nVerify the specified LDEV.
550071746	5	5	The specified MP unit is not mounted.\\nVerify the specified MP unit.
550071768	5	5	A necessary program product is not installed.\\nInstall Open Volume Management.
550071769	5	5	A necessary program product is not installed.\\nInstall Open Volume Management.
550071770	5	5	The specified LDEV ID is already used.\\nVerify the specified LDEV.
550071771	5	5	A volume cannot be created because the capacity of the specified external volume \\ngroup exceeds the maximum capacity for an external volume that is mapped for the \\nonline data migration.\\nVerify the capacity of the external volume group.
550071772	5	5	The specified number of LDEVs exceeds the maximum that can be created in the current \\nconfiguration.\\nVerify the number of LDEVs per free space.
550071773	5	5	The specified parity groups or volumes contain volumes to which LU paths are set.\\nSpecify parity groups or volumes without volumes to which LU paths are set.
550071774	5	5	The specified LDEV is used as a quorum disk.\\nVerify the specified LDEV.
550071775	5	5	The specified LDEV is used as a journal volume.\\nVerify the specified LDEV.
550071776	5	5	The specified LDEV is used as a remote command device.\\nVerify the specified LDEV.
550072453	5	5	The specified number of LDEVs exceeds the maximum that can be created in the parity \\ngroup or the external volume group.\\nSpecify a different parity group or external volume group.
550072454	5	5	Volume Retention Manager settings exist on the specified volume.\\nVerify the specified LDEV.
550072455	5	5	The specified LDEV is used as a command device of an extended consistency group of \\nUniversal Replicator.\\nVerify the specified LDEV.
550072456	5	5	The specified LDEV is used as an external volume that is mapped for the online data \\nmigration.\\nVerify the specified LDEV.
550072457	5	5	There is not enough space left for the specified capacity in the parity group or \\nthe external volume group.\\nSpecify a different parity group or external volume group.
550072458	5	5	The specified location is outside the setting range.\\nVerify the specified location.
550072459	1	3	An error occurred on the Storage Navigator side.\\nPlease contact the HSSC when it is a same deal even if it operates it again.
550072482	5	0	An unregistered error occurred.\\nIf the problem persists despite retrying, please call the HSSC.
550072483	1	3	A communication time-out error occurred.\\nWait for a while, then retry the operation.
550072484	1	3	An error occurred on the storage system.\\nIf this problem persists, please call the HSSC.
550072485	5	5	The Storage Navigator is busy.\\nWait for a while, then retry the operation.
550072486	1	3	The Storage Navigator is busy.\\nWait for a while, then retry the operation.
550072487	1	2	An internal logic contradiction occurred.\\nIf the problem persists despite retrying, please call the HSSC.
550072488	5	5	A communication error occurred.\\nWait for a while, then retry the operation.
550072489	1	5	The specified function is not supported.\\nVerify the DKCMAIN firmware version and the Storage Navigator software version.
550072490	1	3	The storage system has accepted the request normally, but the processing requires \\nsome time.\\nIf this problem persists, close the windows, verify that the internal processing \\nor the configuration change has been complete, and then retry the operation.  If \\nthe internal processing or the configuration change takes much time to complete, \\ncontact the HSSC.
550072512	1	3	An error occurred during communication with the storage system.\\nIf this problem persists, please call the HSSC.
550072513	1	6	An internal error occurred.\\nContact the HSSC.
550072514	1	6	The accelerated compression cannot be changed because different versions of DKCMAIN \\nfirmware coexist on the storage system.\\nUpdate the DKCMAIN firmware.
550072515	5	6	The specified parity groups do not support accelerated compression.\\nSpecify parity groups that support accelerated compression.
550072516	5	6	The accelerated compression cannot be changed because the specified parity groups \\nare in the data copy process (correction copy).\\nWait until the correction copy is complete, and then retry the operation.
550072517	5	6	The accelerated compression cannot be changed because the specified parity groups \\nare in the dynamic sparing process.\\nWait until the dynamic sparing is complete, and then retry the operation.
550072518	5	6	The accelerated compression cannot be changed because the specified parity groups \\nare in the copy back process.\\nWait until the copy back is complete, and then retry the operation.
550072519	5	6	The accelerated compression cannot be changed because the specified parity groups \\ncontain pools with Full Allocation enabled.\\nSpecify parity groups without pools whose Full Allocation is enabled.
550072520	5	6	The accelerated compression cannot be changed because the specified parity groups \\ncontain volumes that belong to blocked pools.\\nSpecify parity groups without volumes that belong to blocked pools.
550072521	5	6	The accelerated compression cannot be changed because the RAID levels of the specified \\nparity groups do not support pool creation.\\nSpecify parity groups with RAID levels that support pool creation.
550072543	5	6	The accelerated compression cannot be changed because the specified parity groups \\ncontain volumes that belong to multiple pools.\\nSpecify parity groups without volumes that belong to multiple pools.
550072544	5	6	The accelerated compression cannot be changed because the specified parity groups \\nare in the correction access status.\\nWait until the correction access is complete, and then retry the operation.
550072545	5	6	The accelerated compression cannot be enabled because the specified parity groups \\ncontain volumes protected by Data Retention Utility settings.\\nVerify volumes contained in the specified parity groups, cancel the volume protection \\nof Data Retention Utility, and then retry the operation.
550072546	5	6	The accelerated compression cannot be changed because volumes exist in the expanded \\nspace of the specified parity groups.\\nSpecify parity groups that do not contain LDEVs in their expanded space.
550072547	5	6	The firmware version of the specified drive does not support accelerated compression.\\nSpecify a drive with a firmware version that supports accelerated compression.
550072548	1	6	An internal error occurred.\\nContact the HSSC.
550072549	5	6	No parity groups can be created because the specified drives contain drives that \\ndo not support accelerated compression.\\nSpecify drives that support accelerated compression.
550072550	5	6	No parity groups can be created because the specified parity groups that are concatenated \\ncontain parity groups without support for accelerated compression.\\nSpecify parity groups that support accelerated compression.
550072551	5	6	The current DKCMAIN firmware version does not support changing the accelerated compression.\\nUpdate the DKCMAIN firmware to a version that supports accelerated compression.
550072552	5	6	The specified parity groups contain volumes that are used by Cache Residency Manager.\\nSpecify parity groups without volumes used by Cache Residency Manager.
550072574	5	6	The specified parity groups contain volumes with capacity less than needed for pool volumes.\\nSpecify parity groups consisting of volumes with enough capacity to be used as pool volumes.
550072575	5	6	The specified parity groups contain volumes that are set as pair volumes.\\nSpecify parity groups without volumes that are set as pair volumes.
550072576	5	6	The specified parity groups contain volumes that are mapped for the online data migration.\\nSpecify parity groups without volumes that are mapped for online data migration.
550072577	5	6	The specified operation cannot be performed because data remains in the expanded \\nspace of the parity groups.\\nFormat the parity groups.
550072578	5	6	The parity group with the encryption and the accelerated compression enabled cannot \\nbe created.\\nDisable the encryption or the accelerated compression.
550072579	5	6	The accelerated compression cannot be enabled on the specified parity groups because \\nthe encryption is enabled.\\nDisable the encryption, and then enable the accelerated compression.
550072580	5	6	The specified LDEVs are being used by a different operation.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
550072581	1	6	An internal error occurred.\\nContact the HSSC.
550072582	5	6	Only LDEVs to be used as pool volumes can be created in a parity group with the accelerated \\ncompression enabled. LDEVs cannot be created because the specified capacity does \\nnot meet the requirement for pool volumes.\\nSee the Provisioning Guide to verify the requirements for pool volumes.
550072583	1	6	The delete operation cannot be completed.\\nRetry the operation. If this problem persists, contact customer support provided \\nin the manual.
550073411	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
550073412	5	5	T10 PI cannot be enabled because the specified LDEV is an external volume.\\nSpecify an internal volume, and then enable the T10 PI setting on the volume.
550076294	5	5	Accelerated Compression cannot be enabled, because LDEVs that are not registered \\nto the pool exist in the selected FMC parity group.\\nPerform either of the following actions on the LDEVs in the FMC parity group for \\nwhich Accelerated Compression is to be enabled:\\n- Add unregistered LDEVs to the pool.\\n- Format and then delete all LDEVs.
598658983	1	3	This function could not be used because a function failed to start during Storage \\nNavigator initialization.\\nClick [Refresh All] on the [File] menu, then retry the operation. If the same problem \\npersists despite retrying, please call the HSSC.
613212133	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613212136	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613212141	5	7	No more report can be made.\\nDelete unnecessary reports, then retry the operation.
613212390	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613241893	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613241926	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613241958	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613241959	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613241992	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613242173	1	5	An error occurred while compressing a file.\\nIf the problem persists despite retrying, please call the HSSC.
613242174	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
613242175	5	7	The report(s) has already been deleted.\\nRefresh the both task window and report window, then confirm that the report(s) has \\nbeen deleted. 
613301476	1	6	Making report was not completed within the prescribed time.\\nWait, then retry the operation.
804364242	1	7	Failed to create a report.\\nCheck the environment.
804364243	1	7	Failed to create a report.\\nCheck the environment.
804364244	1	7	Failed to create a report.\\nCheck the environment.
804364245	1	7	Failed to read the log preference.\\nCheck the environment.
804364246	1	7	The parameter is specified incorrectly.\\nSpecify a correct value.
804364247	1	7	Failed to read the preference.\\nCheck the environment.
804364248	1	7	There is no report to be created.\\nCheck the environment.
804364249	1	7	There is no input directory.\\nCheck the environment.
804364250	1	7	The contents of csv file are incorrect.\\nCheck the csv file.
804364272	1	7	Failed to create a report.\\nIf this problem persists, please call the HSSC.
804364273	1	7	Failed to create a report.\\nCheck the environment.
804364274	1	7	Failed to create a report.\\nCheck the environment.
804364275	1	7	Failed to create a report.\\nCheck the environment.
804364276	1	7	Failed to create a report.\\nCheck the environment.
804364277	1	7	Failed to create a report.\\nCheck the environment.
804364278	1	7	Failed to create a report.\\nCheck the environment.
804364279	1	7	Failed to create a report.\\nCheck the environment.
804364280	1	7	Failed to create a report.\\nCheck the environment.
804364281	1	7	Failed to create a report.\\nCheck the environment.
804365202	3	7	Succeeded to create a report file.\\nClick [OK].
804365209	5	7	Failed to create a report file.\\nCheck the environment.
804423824	3	7	Succeeded to create a report.\\nClick [OK].
804423825	5	7	Succeeded to create a report except for a few report files.\\nClick [OK].
825203436	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825203623	5	3	The specified program product ID is not valid.\\nSpecify a correct program product ID.
825233226	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825233258	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825263170	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825263173	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825263977	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
825295659	1	2	The information of the license cannot be collected.\\nIf this problem persists, contact the HSSC.
882461738	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
882491528	1	3	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
882491560	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
882522279	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
903949196	5	0	The command was rejected because you tried to create a pair with a volume to which \\nVMA is set by Data Retention Utility and a volume without VMA.\\nYou cannot create a pair with these volumes. If you want to create a pair, you must \\nuse the volumes to both of which VMA is set or not.
903952979	5	5	Quick Restore cannot be performed because the specified pair is composed of the external \\nvolumes with different cache mode settings.\\nUse the Reverse Resync option.
903979759	5	3	The storage system is in internal process, or some other user is changing the configuration.\\nWait for a while, and then click [Refresh].
903979760	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
903979761	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
904007628	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
904007629	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
904036457	5	0	The command has been rejected because the cascade request for creating cascade pairs \\ncomposed of volumes belonging to the same consistency group was issued.\\nSelect a different volume or release the consistency group setting.
904036458	5	0	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 \\nis 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 \\nand L2 pairs at the same time.\\nWait until the L1 pair changes to the PSUS or PAIR status, and then retry the operation.\\nPerform the pair operation respectively on the pairs of one-to-multiple volumes or \\nthe L1 and L2 pairs.
904036459	5	0	The Quick Restore command has been rejected because the specified pair is composed \\nof a normal volume and a customized volume (CV).\\nThe quick restore operation cannot be performed when the pair is composed of a normal \\nvolume and a customized volume (CV). Select a different pair.
904036460	5	0	The command has been rejected because a Remote Copy pair exists in the same storage \\nsystem frame.\\nTo continue the operation, delete the remote copy pair.
904038543	5	0	The Quick Restore command could not be executed because the specified pair contains \\nexternal volumes and also is used as a remote replication pair.\\nDelete the remote replication pair or perform the operation on other pairs.
904038565	5	0	The command was rejected because the specified P-VOL is used as a P-VOL of a TrueCopy pair.\\nThe requested command cannot be executed in the current TrueCopy pair status. See \\nthe ShadowImage User Guide for the relation between the TrueCopy pair statuses and \\nthe ShadowImage operations.
904038566	5	0	The command has been rejected, because the specified P-VOL is used as S-VOL of TrueCopy pair.\\nThe requested command cannot be executed in the current status of TrueCopy pair. \\nSee the section "Sharing ShadowImage volumes" in the ShadowImage User Guide for the \\nrelation between the state of TrueCopy pair and the ShadowImage operations.
904038567	3	0	A pair cannot be created because shared memory for differential tables is in sufficient.\\nAdd sufficient shared memory to create a pair.
904038667	5	5	The operation failed because the specified P-VOL was a data volume of Universal Replicator. \\nCheck the requirements for using the volume with Universal Replicator.\\nCheck the requirements for using the volume with Universal Replicator.
904039340	5	5	The operation failed, because the specified S-VOL was a data volume of Universal \\nReplicator.\\nRelease the Universal Replicator setting or specify another volume.
904039496	5	0	The Quick Restore command could not be executed because the specified pair contains \\nexternal volumes, and also is used as a Universal Replicator pair.\\nDelete the Universal Replicator pair, or perform the operation on a different pair.
904039501	5	0	The command was rejected because the specified volume is used by the Universal Replicator \\nand the TrueCopy.\\nRelease the pair of Universal Replicator or the pair of TrueCopy, and then retry \\nthe operation.
904040457	5	0	The storage system is busy (internal processing).\\nIf the problem persists despite retrying, please call the HSSC.
904040524	5	5	The operation cannot be performed because the specified P-VOL is a P-VOL for Thin Image.\\nRelease the Thin Image pair, or select a different volume.
904040525	5	5	The operation cannot be performed because the specified P-VOL is a V-VOL for Thin Image.\\nSelect a different volume.
904040526	5	5	The operation cannot be performed, because the specified P-VOL is a pool volume.\\nRelease the pool volume or select another volume.
904040527	5	5	The operation cannot be performed because the specified S-VOL is a P-VOL for Thin Image.\\nRelease the Thin Image pair, or select a different volume.
904040549	5	5	The operation cannot be performed because the specified S-VOL is a V-VOL for Thin Image.\\nSelect a different volume.
904040550	5	5	The operation cannot be performed, because the specified S-VOL is a pool volume.\\nRelease the pool volume or select another volume.
904040582	5	5	The Pairsplit-S (Delete Pairs) operation has failed.\\nRefresh the window, and check whether the pair exists.
904040583	1	5	The PCB required for this operation is not mounted. \\nMount the required PCB, and then retry the operation.
904041324	1	2	The operation failed, because different versions of softwares coexisted in the storage system.\\nReplace the software, and then retry the operation.
904041358	5	5	The operation failed, because the specified P-VOL was a journal volume.\\nRelease the journal volume setting, or specify another volume.
904041359	5	5	The operation failed, because the specified S-VOL was a journal volume.\\nRelease the journal volume setting, or specify another volume.
904041361	5	5	The operation could not be performed because the specified secondary volume is a \\nUniversal Replicator volume.\\nCheck the requirements for using the volume with Universal Replicator.
904041481	1	3	An error occurred on the DKC side.\\nIf this problem persists, contact the HSSC.
904041482	1	3	This function is not supported.\\nCheck if the DKCMAIN firmware version and Storage Navigator software version are \\nmismatched.
904041483	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, contact the HSSC.
904041484	1	3	An error occurred while connecting to the storage system.\\nIf this problem persists, contact the HSSC.
904041485	1	3	A communication time-out error occurred in the storage system.\\nIf the problem persists despite retrying, please call the HSSC.
904041488	5	0	The operation could not be performed because the specified volume is being shredded \\nby Data Retention Utility.\\nVerify that the shredding is complete in the Data Retention Utility window, and then \\nretry the operation.
904041512	5	0	The command has been rejected because the specified S-VOL is used as P-VOL of Thin \\nImage, or the specified MU number is already used.\\nThe specified command cannot be executed with the current pair configuration. See \\nthe section "Interoperability with other products and functions" and "ShadowImage" \\ndescribed in the Thin Image User Guide for the conditions of sharing the volumes \\nbetween Thin Image and ShadowImage.
904041513	5	0	The operation failed because the volume was shared by a Thin Image pair.\\nTo continue the operation, release the Thin Image setting.
904041514	5	0	The operation failed because the volume was shared by a Thin Image pair in COPY (RS-R)/RCPY status.\\nCheck the conditions for using ShadowImage in conjunction with Thin Image.
904041515	5	0	The operation failed because the CU group of the specified volume is not supported.\\nVolumes that do not belong to CU group 0 are currently not supported. Specify another volume.
904042316	5	5	The operation cannot be performed because the specified primary volume is used by \\na delta resync pair of Universal Replicator.\\nSee the ShadowImage User Guide for the relation between the pair status of Universal \\nReplicator and the ShadowImage operations. See the Thin Image User Guide for the \\nrelation between the pair status of Universal Replicator and the Thin Image operations.
904042317	5	5	The operation failed because the specified S-VOL was used by Delta resync of Universal \\nReplicator.\\nThe P-VOL of Universal Replicator pair for Delta resync cannot be specified as S-VOL. \\nSpecify another volume.
904043216	5	0	The operation could not be performed because the specified MU number is already used. \\nRefresh the ShadowImage window, and check the MU number that can be used.
904045112	5	5	The operation failed because the volume specified as the P-VOL was used as the S-VOL \\nof another pair and the volume specified as the S-VOL was used as the P-VOL of another \\npair already.\\nVerify the pair configurations. See the ShadowImage User Guide for the relation between \\nthe configuration and the operation of pairs.
904960041	5	0	"0" cannot be specified as the MU number of L2 pair.\\nSpecify other MU numbers.
904966805	5	5	The command has been rejected, because the specified P-VOL is a Dynamic Provisioning \\nvolume not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, and then retry the operation.
904966806	5	5	The command has been rejected, because the specified S-VOL is a Dynamic Provisioning \\nvolume not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, and then retry the operation.
904966832	5	0	The command has been rejected, because Quick Format is performed on the specified P-VOL.\\nRetry the operation after quick formatting is complete.
904966833	5	0	The command has been rejected, because Quick Format is performed on the specified S-VOL.\\nRetry the operation after quick formatting is complete.
904966860	5	0	The Quick Restore command has been rejected, because the specified pair is composed \\nof the Dynamic Provisioning volume and the volumes other than Dynamic Provisioning volume.\\nQuick Restore cannot be performed in the current pair configuration.
904966865	5	0	The Quick Restore command has been rejected, because device information (Inquiry \\ninformation) of P-VOL and S-VOL was different in the specified pair.\\nQuick Restore cannot be performed in the current pair configuration. Select a pair \\nwhose device information (Inquiry information) is the same, and then perform Quick Restore.
904966891	5	0	Quick Restore cannot be performed because the configuration is being backed up in \\nthe target volume. \\nWait for a while, and then retry the operation.
904967674	5	0	The command has been rejected, because the specified P-VOL is a Dynamic Provisioning \\nvolume whose capacity is being added.\\nThe operation is not available because the target volume has capacity changes. Verify \\nthe capacity of the volume, and then apply the setting.
904967675	5	0	The command has been rejected, because the specified S-VOL is a Dynamic Provisioning \\nvolume whose capacity is being added.\\nThe operation is not available because the target volume has capacity changes. Verify \\nthe capacity of the volume, and then apply the setting.
904967701	5	0	The initialization function cannot be performed because a TrueCopy pair or a Universal \\nReplicator pair is created by using Dynamic Provisioning volumes.\\nDelete the TrueCopy or Universal Replicator pair that is using Dynamic Provisioning \\nvolumes, and then retry the operation.
904967764	5	0	The command has been rejected because the specified P-VOL is used by a pair of Thin \\nImage that is registered in the CTG.\\nRelease the pair of Thin Image that is using the specified P-VOL, and then retry \\nthe operation.
904967765	5	0	The command has been rejected because the specified S-VOL is used by a pair of Thin \\nImage that is registered in the CTG.\\nRelease the pair of Thin Image that is using the specified S-VOL, and then retry \\nthe operation.
904967766	5	0	The command has been rejected, because the specified P-VOL is a volume of Dynamic \\nProvisioning whose zero page is being reclaimed.\\nWait until the zero page reclamation is completed, and then retry the operation.
904967767	5	0	The command has been rejected, because the specified S-VOL is a volume of Dynamic \\nProvisioning whose zero page is being reclaimed.\\nWait until the zero page reclamation is completed, and then retry the operation.
904968691	5	5	The specified primary volume is a volume using two mirrors in the 3DC cascade, the \\n3DC multi-target, or the delta resync configuration. The operation for the specified \\nvolume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Universal Replicator delta resync pair volume.\\n- The specified volume is used as a Universal Replicator pair data volume.\\nSee the ShadowImage User Guide for the relation between the pair status of Universal \\nReplicator and the ShadowImage operations.
904968692	5	5	The specified secondary volume is a volume using two mirrors in the 3DC cascade, \\nthe 3DC multi-target, or the delta resync configuration. The operation for the specified \\nvolume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Universal Replicator delta resync pair volume.\\n- The specified volume is used as a Universal Replicator pair data volume.\\nSee the ShadowImage User Guide for the relation between the pair status of Universal \\nReplicator and the ShadowImage operations.
905794128	5	5	The command was rejected, because the Dynamic Provisioning volume specified as P-VOL \\nwas not associated with a pool.\\nAssociate the specified Dynamic Provisioning volume with a pool, and then retry the \\noperation.
905794129	5	5	The command was rejected, because the Dynamic Provisioning volume specified as S-VOL \\nwas not associated with a pool.\\nAssociate the specified Dynamic Provisioning volume with a pool, and then retry the \\noperation.
905794131	5	5	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 \\nwith the cascade attribute disabled.\\n- Performing a pair split or pair resync operation on a pair for which the cascade \\nattribute is disabled and whose primary volume has no LUN paths.\\nVerify the statuses of all the specified pairs, or set LUN paths, and then retry \\nthe operation.
905794132	5	5	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 \\na 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 \\nwith the cascade attribute disabled.\\n- Performing a pair split or pair resync operation, or assigning, deleting, or changing \\na secondary volume for a pair for which the cascade attribute is disabled and whose \\nsecondary volume has no LUN paths.\\nVerify the statuses of all the specified pairs, or set LUN paths, and then retry \\nthe operation.
905794134	5	5	The specified operation cannot be performed, because pairs under root volumes are \\nbeing deleted.\\nWait until all of the pairs under the root volumes are deleted, and then retry the \\noperation.
905794162	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
905794256	5	5	The LDEVs of a specified pool contain an LDEV that belongs to a resource group that \\nyou do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
905883657	5	5	The operation failed because the current software version does not support the capacity \\nof specified P-VOL.\\nCheck the software version of the storage system.
905883658	5	5	The operation failed because the current software version does not support the capacity \\nof specified S-VOL.\\nCheck the software version of the storage system.
905884468	5	0	The command was rejected, because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the P-VOL was being initialized.\\nWait until the initialization of the pool is completed, and then retry the operation.
905884469	5	0	The command was rejected, because the pool associated with the Dynamic Provisioning \\nvolume that is specified as the S-VOL was being initialized.\\nWait until the initialization of the pool is completed, and then retry the operation.
905884530	5	0	The operation cannot be performed because the specified volume is in the online data \\nmigration process.\\nSpecify volumes other than those in the online data migration process.
905884531	5	0	The operation cannot be performed because the volume specified as the primary volume \\nis in the online data migration process.\\nSpecify volumes other than those in the online data migration process.
905884553	5	0	The operation cannot be performed because the volume specified as the secondary volume \\nis a migration volume of nondisruptive migration.\\nSpecify a different volume.
905884562	5	5	The operation cannot be done because a pool cannot be used.\\nVerify the status of the specified pool.
905884584	5	5	The operation cannot be performed because the specified pool number is not the same \\nas the pool number for the existing pairs.\\nWhen creating multiple Thin Image pairs by assigning two or more secondary volumes \\nto one primary volume, you must specify the same pool number as the existing pairs.
905884585	5	5	The operation cannot be performed because the specified primary volume is a secondary \\nvolume for Thin Image.\\nRelease the Thin Image pair, or select a different volume.
905884586	5	5	The operation cannot be performed because the specified secondary volume is a secondary \\nvolume for Thin Image.\\nRelease the Thin Image pair, or select a different volume.
905884587	5	5	The specified snapshot number is used in a different pair for Thin Image.\\nRelease the Thin Image pair, or select a different snapshot number.
905884588	5	5	The operation cannot be done because the license capacity has been exceeded.\\nInstall additional license keys to expand the license capacity of the program product.
905884589	5	5	The command cannot be run in the current pair status.\\nRefresh the window, and then retry the operation.
905884590	5	5	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 \\nL2 pairs at the same time.\\nVerify the status of the specified pair.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
905884591	5	5	The operation cannot be performed, because a pool whose pool type is not Thin Image \\nis selected.\\nSelect a pool whose pool type is Thin Image.
905884592	5	5	The command was rejected because the specified volume was set unavailable to specify \\nas a secondary volume.\\nRelease the secondary volume unavailable setting, and then retry the operation.
905884593	5	5	An error occurred during Thin Image 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 \\nwhere 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 Thin Image is depleted.\\nPerform one of the following, and then retry the operation:\\n- Specify the correct LDEV number.\\n- Change the status of the specified pair, or specify a different pair.\\n- Specify the correct MU number.\\n- Change the status of the specified pool, or specify a different pool.\\n- Increase the license capacity of Thin Image.\\n-See the Thin Image User Guide for the relation between the number of pairs that \\ncan be created and shared memory.
905884616	5	5	The command was rejected because the shared memory (FC, TPF, or Extension1) of necessary \\ncapacity was not installed.\\nAdd sufficient shared memory.
905884617	5	5	The command was rejected because the shared memory (SS1 or more) of necessary capacity \\nwas not installed.\\nAdd sufficient shared memory.
905884618	5	5	The LDEV number that is specified as a primary volume is invalid.\\nSpecify another LDEV number.
905884620	5	5	The operation cannot be performed because the Thin Image primary volume is used as \\na TrueCopy primary volume, and the status of the TrueCopy pair is not PSUS or PSUE.\\nChange the status of the TrueCopy pair to PSUS or PSUE, and then retry the operation.
905884621	5	5	The operation cannot be performed because the Thin Image primary volume is used as \\na Universal Replicator primary volume, and the status of the Universal Replicator \\npair is not PSUS or PSUE.\\nChange the status of the Universal Replicator pair to PSUS or PSUE, and then retry \\nthe operation.
905884622	5	5	The operation cannot be performed because the Thin Image primary volume is also a \\nTrueCopy secondary volume.\\nSelect a different volume.
905884623	5	5	The operation cannot be performed because the Thin Image primary volume is also a \\nUniversal Replicator secondary volume.\\nSelect a different volume.
905884624	5	5	The operation cannot be done because VMA is set for the specified primary volume.\\nVerify the setting of the specified volume.
905884647	5	5	The operation cannot be done because the specified secondary volume is an external volume.\\nSpecify another volume.
905884648	5	5	The operation cannot be done because the specified secondary volume is not a virtual volume.\\nSpecify another volume.
905884649	5	5	The command was rejected because the specified secondary volume was used as a primary \\nvolume of Universal Replicator.\\nSpecify another volume.
905884650	5	5	The command was rejected because the specified secondary volume was used as a secondary \\nvolume of Universal Replicator.\\nSpecify another volume.
905884651	5	5	The command was rejected because the specified volume was set unavailable to specify \\nas a secondary volume.\\nRelease the secondary volume unavailable setting, and then retry the operation.
905884652	5	5	The operation cannot be done because VMA is set for the specified secondary volume.\\nVerify the setting of the specified volume.
905884653	5	5	The command was rejected because the Max LBA size of the specified primary and the \\nsecondary volumes was different.\\nVerify the Max LBA size of the volume.
905884654	5	5	The command was rejected because the number of slots is different between the specified \\nprimary and the secondary volumes. \\nVerify the number of slots of the volume. 
905884655	5	5	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 Dynamic Provisioning virtual volume as a secondary volume to create \\na pair with the cascade attribute disabled.\\n- Specifying a Dynamic Provisioning virtual volume as a secondary volume of a pair \\nwith the cascade attribute disabled to assign or change the secondary volume.\\nVerify the statuses of all the specified pairs, or specify different volumes, and \\nthen retry the operation.
905884678	5	5	The command was rejected because the specified secondary volume was used as a primary \\nvolume of ShadowImage.\\nSpecify another volume.
905884679	5	5	The command was rejected because the specified secondary volume was used as a secondary \\nvolume of ShadowImage.\\nSpecify another volume.
905884681	5	5	The Thin Image 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.\\nInstall additional shared memory, or wait until the initializing process is complete \\nand then retry the operation.
905884682	5	5	The specified operation cannot be done.\\nContact the HSSC.
905884683	5	5	The operation cannot be done because the PSUE option is specified.\\nContact the HSSC.
905884684	5	5	The operation cannot be performed because the Thin Image primary volume and the TrueCopy \\nsecondary volume share the same volume, and the TrueCopy pair status is COPY.\\nChange the status of the TrueCopy pair to other than COPY, and then retry the operation.
905884685	5	5	The operation cannot be performed because the Thin Image primary volume and the Universal \\nReplicator secondary volume share the same volume, and the Universal Replicator pair \\nstatus is COPY.\\nChange the status of the Universal Replicator pair to other than COPY, and then retry \\nthe operation.
905884686	5	5	The ShadowImage MU number cannot be specified when the Thin Image primary volume \\nand the ShadowImage primary volume share the same volume.\\nSelect a different MU number.
905884708	5	5	"0" cannot be specified as the MU number of the Thin Image primary volume when the \\nThin Image primary volume and the ShadowImage secondary volume share the same volume.\\nSelect a different MU number.
905884709	5	5	The command was rejected because the Thin Image primary volume and the ShadowImage \\nprimary volume share the same volume, and the ShadowImage pair is in the re-synchronizing process.\\nWait for the status of the ShadowImage pair to change to PAIR, and then retry the \\noperation.
905884710	5	5	The command was rejected because the Thin Image primary volume and the ShadowImage \\nsecondary volume share the same volume, and the ShadowImage pair status is not PSUS.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
905884711	5	5	The operation cannot be performed because the Thin Image primary volume and the ShadowImage \\nprimary volume share the same volume, and the ShadowImage pair status is not PSUS or PSUE.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
905884712	5	5	The operation cannot be performed because the Thin Image primary volume and the ShadowImage \\nsecondary volume share the same volume, and the ShadowImage pair status is not PSUS.\\nChange the status of the ShadowImage pair to PSUS, and then retry the operation.
905884713	5	5	The operation cannot be done because the pools or the pool volumes are blocked.\\nRestore the blocked pools or pool volumes, and then retry the operation. 
905884714	5	5	The Thin Image pair cannot be restored due to one of the following reasons:\\n- The snapshot data of the restore target Thin Image pair is being obtained per consistency group.\\n- The snapshot data is being obtained for a different pair whose primary volume is \\nthe restore target Thin Image primary volume.\\nWait for a while, and then retry the operation.
905884715	5	5	The Thin Image pair with the specified consistency group number cannot be created \\ndue to one of the following reasons:\\n- The specified consistency group number is used by ShadowImage.\\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.\\nVerify the specified consistency group number.
905884716	5	5	The specified consistency group number is invalid.\\nVerify the consistency group number.
905884739	5	5	The operation cannot be done because the specified secondary volume is incorrect.\\nVerify the setting of the specified volume.
905884740	5	5	The command was rejected because the program product of Thin Image is not installed.\\nInstall the necessary program product.
905884744	5	5	The command was rejected because the primary volume is used as an external volume \\nthat is mapped for online data migration.\\nSelect a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
905884745	5	5	The command was rejected because the secondary volume is used as an external volume \\nthat is mapped for online data migration.\\nSelect a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
905885422	5	5	The operation cannot be performed due to one of the following reasons:\\n- With the current DKCMAIN firmware version, a HDP pool cannot be used to store snapshot data.\\n- For the specified pool, Enable is selected for Multi-Tier Pool.\\n- For the specified pool, Enable is selected for Data Direct Mapping.\\nVerify the DKCMAIN firmware version and the software version of Storage Navigator, \\nand then match them up.\\nA pair cannot be created if Enable is set for Data Direct Mapping for the specified pool.\\nIf Enable is set for Multi-Tier Pool, select Disable, and then retry the operation.
905885423	5	5	The operation failed because the Thin Image program product is not installed. \\nInstall the Thin Image program product.
905885424	5	5	The operation failed because the software version of Storage Navigator and firmware \\nversion of DKCMAIN do not match. \\nCheck the software version of Storage Navigator and the firmware version of DKCMAIN.
905885425	5	5	The operation failed because there are not enough cache management devices.\\nDelete unnecessary external volumes or virtual volumes, and then retry the operation. \\nWhen there is a Thin Image pair, delete all the pairs related to the unnecessary \\nprimary volumes, and then retry the operation. If this problem persists, call the HSSC.
905885426	5	5	The operation failed because the capacity of the specified volume exceeds 4 TB.\\nSpecify a volume whose capacity is 4TB or less.
905885428	5	5	The operation cannot be performed due to either of the following reasons:\\n- There is a pair in the status of Quick Restore among ShadowImage pairs that share \\na primary volume.\\n- The operation was performed on some pairs of one-to-multiple volumes or L1 and \\nL2 pairs at the same time.\\nWait until the Quick Restore operation is complete, and then retry the operation.\\nPerform the operation respectively on the pairs of one-to-multiple volumes or the \\nL1 and L2 pairs.
905885429	5	5	The operation failed because the specified pool number is wrong.\\nCheck the pool number.
905885452	5	5	A Thin Image pair cannot be created because the consistency group used by the specified \\nsnapshot group is one of the following:\\n- The consistency group number is used by ShadowImage. \\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 .  \\nVerify the consistency group of the pairs that belong to the snapshot group.
905885581	5	5	The operation failed because the volume specified as the S-VOL is a root volume.\\nVerify the status of the volume.
905885582	5	5	The operation failed because the volume specified as the S-VOL is a node volume.\\nVerify the status of the volume.
905885583	5	5	The operation failed because the volume specified as the P-VOL is a leaf volume.\\nVerify the status of the volume.
905885584	5	5	The operation failed because the volume specified as the S-VOL is a leaf volume.\\nVerify the status of the volume.
905885585	5	5	The specified primary volume is a volume using two mirrors in the 3DC cascade, the \\n3DC multi-target, or the delta resync configuration. The operation for the specified \\nvolume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Universal Replicator delta resync pair volume.\\n- The specified volume is used as a Universal Replicator pair data volume.\\nSee the Thin Image User Guide for the relation between the pair status of Universal \\nReplicator and the Thin Image operations.
905885607	5	5	The specified secondary volume is a volume using two mirrors in the 3DC cascade, \\nthe 3DC multi-target, or the delta resync configuration. The operation for the specified \\nvolume cannot be performed due to one of the following reasons:\\n- The specified volume is used as a Universal Replicator delta resync pair volume.\\n- The specified volume is used as a Universal Replicator pair data volume.\\nSee the Thin Image User Guide for the relation between the pair status of Universal \\nReplicator and the Thin Image operations.
905885608	5	5	The command ended abnormally because the specified MU number is out of the range \\nthat can be specified.\\nMake sure the MU number can be specified.
905885678	5	5	A Thin Image pair with the CTG mode specified cannot be created because all the consistency \\ngroups have already been defined.\\nCheck the respective consistency group status or create a Thin Image pair without \\nspecifying the CTG mode.
905885700	5	5	A Thin Image pair cannot be created because the snapshot ID (MU number) that can \\nbe used for the volume specified as the primary volume is depleted.\\nSelect a different volume.
905885701	5	5	A  Thin Image pair cannot be created because all the snapshot groups have already \\nbeen defined, or the number of pairs that can be registered in the specified snapshot \\ngroup has exceeded the maximum.\\nCheck the defined snapshot groups or select a different snapshot group.
905885702	5	5	A Thin Image pair in which a V-VOL of Dynamic Provisioning is set as the primary \\nvolume cannot be created because the Dynamic Provisioning pool is being initialized.\\nWait until the initialization of the pool is complete, and then retry the operation.
905885703	5	5	Failed to create a Thin Image pair because the Dynamic Provisioning pool is being \\ninitialized.\\nWait until the initialization of the pool is complete, and then retry the operation.
905885704	5	5	The Add Pair (Paircreate) operation failed because the specified pair type is invalid.\\nCheck the specified pair type.
905886413	5	5	The Thin Image pair operation cannot be performed because all Thin Image pairs that \\nshare the specified primary volume are in PSUE status. \\nChange the status of pairs related to the specified primary volume to enable the \\npair operation, and then retry the operation.
969942600	1	2	An error occurred during Storage Navigator processing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
969942604	1	2	An error occurred during Storage Navigator processing.\\nClick the refresh button to have the latest information displayed on the window, \\nand then retry the operation. If this problem persists, contact the HSSC.
969942633	1	6	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
969943687	1	6	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
970032001	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970032004	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970032258	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970033894	1	6	This function is not available.Performance Monitor is required.\\nInstall the required program product.
970035814	5	6	Failed to access the monitoring data because accessing the monitoring data on the \\nStorage Navigator is busy.\\nWait for a while, and then retry the operation. If this problem persists, call the HSSC.
970061761	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970061763	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970061793	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970061794	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
970061825	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
970061826	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
970061860	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970062042	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
970066567	5	5	There is no monitoring data.\\nChange the monitor switch to ON, and accumulate the data.
970091559	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970092545	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
970121345	1	2	The storage system status is invalid.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
978149642	5	5	The operation cannot be performed, because the following LDEVs do not belong to the \\nsame 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 \\ndeduplication setting is enabled\\nVerify the settings, and then retry the operation.
1027290560	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1027320096	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1199128817	5	5	Characters or the number of characters for the user name is not valid.\\nEnter the user name using 1 to 256 characters with alphanumeric characters and the \\nfollowing symbols: ! # $ % & ' * + - . / = ? @ ^ _ ` { | } ~
1199156780	5	5	No more users can be created because the number of registered users has reached the maximum.\\nReduce the number of registered users, and then retry the operation.
1199156782	5	5	The password cannot be changed because the authentication method of the specified \\nuser is not Local.\\nChange the password on the external authentication server.
1199156809	5	5	The number of user groups to which the user belongs has reached the maximum.\\nReduce the number of user groups to which the user belongs, and then retry the operation.
1199156840	5	5	Characters or the number of characters for the user group name is not valid.\\nEnter the user group name using 1 to 64 characters with alphanumeric characters, \\nspaces, and the following symbols: ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~
1199156848	5	5	The specified user cannot be removed from the user group because the user will belong \\nto no user group.\\nVerify the settings.
1199158575	5	5	The authentication method is not valid.\\nVerify the settings.
1199158576	5	5	All users in Administrator User Group cannot be disabled.\\nEnable any other users in Administrator User Group, and then retry the operation.
1199158577	5	5	The specified user does not belong to the specified user group.\\nVerify the settings.
1199158578	5	5	The specified user already belongs to the specified user group.\\nVerify the settings.
1199186444	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186445	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186446	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186447	1	7	Decryption failed.\\nCheck if the decryption parameter is correct.
1199186448	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186449	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186450	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186451	1	7	Decryption failed.\\nCheck if the decryption parameter is correct.
1199186452	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186453	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186475	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186476	1	5	The parameter is invalid.\\nSpecify a correct value.
1199186477	1	5	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186478	1	7	Failed to get an IP address.\\nCheck the connection environment.
1199186479	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186480	1	2	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186481	1	2	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186482	1	2	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186483	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186484	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186506	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186507	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186508	1	7	The same path is specified in the output source and the output target.\\nSet a different path.
1199186509	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186510	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186511	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186512	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186513	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186514	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186515	1	7	A file or a directory of the specified path does not exist, or the access is rejected.\\nCheck the environment of file or directory of the specified path.
1199186537	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186538	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186539	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186540	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186541	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186542	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186543	5	7	The capacity of a memory is insufficient to login.\\nWait for a while, then retry the operation.
1199186544	5	7	The number of sessions per IP address exceeds the maximum.\\nLog out the unnecessary sessions, then retry the operation.
1199186545	5	7	The number of sessions per Tomcat session exceeds the maximum.\\nLog out the unnecessary sessions, then retry the operation.
1199186546	5	7	The number of sessions in the entire system exceeds the maximum.\\nLog out the unnecessary sessions, then retry the operation.
1199186568	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186569	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186570	1	7	Failed to start the session due to no user authority.\\nConfirm whether you are authorized.
1199186571	1	7	Failed to save the specific information of user.\\nCheck the environment.
1199186572	1	7	Failed to save the specific information of user.\\nCheck the environment.
1199186573	1	7	Failed to save the specific information of user.\\nCheck the environment.
1199186574	1	7	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.\\nTake the following actions:\\n- Verify the IP address. If the IP address is correct, close the browser, wait for \\na while, and then log in again.\\n- The software version of Storage Navigator might not match that of the destination \\nSVP. Clear the caches of the JRE and the browser, restart the browser, and then retry \\nthe operation.\\n- Storage Navigator runs a software after downloading it via the network. If you \\nuse a proxy server, an old version of the software remains in the cache of the proxy \\nserver, and it might be downloaded and run instead of a new version. If this problem \\npersists, contact your network administrator.\\nIf this problem persists, contact customer support provided in the manual.
1199186575	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186576	5	7	The capacity of a memory is insufficient to handle requests.\\nContact customer support provided in the manual.
1199186577	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186599	1	7	An error occurred during Storage Navigator processing.\\nContact customer support provided in the manual.
1199186600	5	7	Failed to login.\\nSpecify a correct value.
1199186601	1	7	Failed to convert an XML file.\\nCheck if the specified XML file is valid.
1199186602	1	7	The parameter is specified incorrectly.\\nSpecify a correct value.
1199186603	1	7	The parameter is specified incorrectly.\\nSpecify a correct value.
1199186604	1	7	The number of onetime keys has exceeded the maximum.\\nWait for a while, then retry the operation.
1199186605	1	7	The specified onetime key already exists.\\nRetry the operation.
1199186606	1	7	The certificate does not exist.\\nCheck the environment.
1199186607	1	7	Failed to create a certificate object.\\nCheck the environment.
1199186608	1	7	The key store file does not exist.\\nCheck the environment.
1199186630	1	7	Failed to get a certificate.\\nCheck the environment.
1199186631	1	7	Failed to access the key store file.\\nCheck the environment.
1199186632	1	7	Failed to initialize the key store file.\\nCheck the environment.
1199186633	1	7	Failed to access the key store file.\\nCheck the environment.
1199186634	1	7	Failed to get a certificate.\\nCheck the environment.
1199186635	1	7	The key store file does not exist.\\nCheck the environment.
1199186636	1	7	Failed to read the key store file.\\nCheck the environment.
1199186637	1	7	The specified alias does not exist.\\nCheck the environment.
1199186638	1	7	The key store file does not exist.\\nCheck the environment.
1199186639	1	7	The specified alias does not exist.\\nCheck the environment.
1199186661	1	7	Failed to read the key store file.\\nCheck the environment.
1199186662	1	7	Failed to get a certificate.\\nCheck the environment.
1199186663	1	7	The key store file does not exist.\\nCheck the environment.
1199186664	1	7	The specified alias does not exist.\\nCheck the environment.
1199186665	1	7	Failed to access the key store file.\\nCheck the environment.
1199186666	1	7	Failed to delete a certificate.\\nCheck the environment.
1199186667	1	7	Failed to read a key store object.\\nCheck the environment.
1199186668	1	7	Failed to read a key store object.\\nCheck the environment.
1199186669	1	7	Failed to read a key store object.\\nCheck the environment.
1199186670	1	7	Failed to read a key store object.\\nCheck the environment.
1199186692	1	7	Failed to read a key store object.\\nCheck the environment.
1199186693	1	7	Failed to store a key store object.\\nCheck the environment.
1199186694	1	7	Failed to store a key store object.\\nCheck the environment.
1199186695	1	7	Failed to store a key store object.\\nCheck the environment.
1199186696	1	7	Failed to store a key store object.\\nCheck the environment.
1199186697	1	7	Failed to store a key store object.\\nCheck the environment.
1199186698	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186699	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186700	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186701	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186723	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186724	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186725	1	7	Failed to authenticate the onetime key.\\nCheck the environment.
1199186726	1	7	Failed to register a onetime key.\\nCheck the environment.
1199186727	1	7	The number of onetime keys has exceeded the maximum.\\nWait for a while, then retry the operation.
1199186728	1	7	Failed to authenticate the user account. \\nCheck the environment.
1199186729	1	7	The specified group ID does not exist.\\nCheck the environment.
1199186730	1	7	Failed to store the user information.\\nCheck the environment.
1199186731	1	7	The user information of the specified onetime key does not exist.\\nCheck the environment.
1199186732	1	7	Failed to get the user information from the specified onetime key.\\nCheck the environment.
1199187405	1	7	The user information of the specified global session ID does not exist.\\nCheck the environment.
1199187406	1	7	Failed to get the user information from the specified global session ID.\\nCheck the environment.
1199187407	1	1	The user session was interrupted. \\nLog in again.
1199187410	1	7	NAS Unified Firmware Configuration Backup cannot be performed.\\nVerify the following conditions.\\n- The storage system is in the normal state.\\n- The network connection between the SVP and the storage system is normal.\\nIf this problem persists when the conditions are normal, contact customer support.
1199216235	1	6	TheThe application cannot be started or was terminated forcibly.\\nContact and ask the SVP administrator to take action appropriate to the situation, \\nas follows:\\n- If this error occurs when the application starts:\\nA different application might be using the SVP port number. Verify the state of each \\napplication using the background service log, see the Gx00/Fx00 user guide, and then \\nperform troubleshooting.\\n- If this error occurs at a time other than when the application starts:\\nSee the System Administrator Guide, and then perform troubleshooting.\\nIf this problem persists, contact the HSSC.
1213921258	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
1227756014	5	5	Characters or the number of characters for the role name is not valid.\\nEnter the role name using 1 to 64 characters with alphanumeric characters, spaces, \\nand the following symbols: ! # $ % & ' ( ) + - . = @ [ ] ^ _ ` { } ~
1227756015	5	5	The specified user group does not exist.\\nVerify the settings.
1227756016	5	5	The specified user does not exist.\\nVerify the settings.
1227756017	5	5	The resource group assignment cannot be changed because the specified user group \\napplies to All Resource Groups Assigned.\\nSpecify a user group that does not apply to All Resource Groups Assigned.
1227785805	5	5	No more user groups can be registered because the number of registered user groups \\nhas reached the maximum.\\nReduce the number of registered user groups, and then retry the operation.
1227785806	5	5	The same user group name is already registered.\\nSpecify a different user group name.
1227815596	5	5	The specified role does not exist.\\nVerify the information of the specified role.
1227815597	5	5	The specified user account cannot be changed because it is a built-in account.\\nVerify the settings.
1227815598	5	5	The specified user group cannot be changed because it is a built-in group.\\nVerify the settings.
1227815599	5	5	The specified user group cannot be deleted because there will be users that belong \\nto no user group.\\nVerify the information of the users that belong to the specified user group.
1227815600	5	5	The user name or password is not valid.\\nVerify the user name or password.
1227815601	5	5	You do not have permission to change the password.\\nVerify the user authority.
1227815603	1	5	An internal error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
1227815604	1	2	An internal error occurred on the RMI server.\\nRetry the operation. If this problem persists, contact the HSSC.
1227845387	1	5	An error occurred between the RMI server and the storage system.\\nIf this problem persists, contact the HSSC.
1251046764	5	5	The operation cannot be performed, because the total number of Thin Image pairs under \\nthe specified root volumes exceeds 32,768.\\nVerify the number of Thin Image pairs under the specified root volume.
1251136192	5	5	A pair cannot be created because of the migration attribute of the volume specified \\nas the primary volume or the secondary volume.\\nRelease the migration attribute, or specify a different volume.
1251136193	5	5	The operation cannot be performed because of the migration attribute of the volume \\nspecified as the primary volume or the secondary volume.\\nRelease the migration attribute.
1251136194	5	5	A pair consisting of three secondary volumes cannot be created because of the migration \\nattribute of the volume specified as the primary volume.\\nCreate a pair consisting of one or two secondary volumes, or specify a different \\nvolume for the primary volume.
1251136195	5	5	The operation cannot be performed because of the migration attribute of the secondary \\nvolume of the specified pair.\\nRelease the migration attribute.
1251136196	5	5	The volume specified as the primary volume is a migration volume of nondisruptive \\nmigration. The operation cannot be performed because the setting of the  online data \\nmigration for the volume is not valid.\\nVerify the setting of the online data migration.
1251136198	5	5	The command cannot be run because the volume specified as the primary volume is a \\nreserved volume of global-active device, or the status of the global-active device \\npair is not valid.\\nSpecify a different volume, or verify the status of the global-active device pair, \\nand then retry the operation.
1251136199	5	5	The command cannot be run because the volume specified as the secondary volume is \\na reserved volume of global-active device, or the volume is used by the global-active \\ndevice pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
1251136200	5	5	The command cannot be run because the volume specified as the primary volume is a \\nreserved volume of global-active device, or the status of the global-active device \\npair is not valid.\\nSpecify a different volume, or verify the status of the global-active device pair, \\nand then retry the operation.
1251136222	5	5	The command cannot be run because the volume specified as the secondary volume is \\na reserved volume of global-active device, or the volume is used by the global-active \\ndevice pair.\\nSpecify a different volume, or delete the global-active device pair, and then retry \\nthe operation.
1251136223	5	5	The command cannot be run because the specified primary volume is not a primary volume \\nof a Thin Image pair.\\nRefresh the window, and then retry the operation.
1251136224	5	5	The command cannot be run because the specified pair does not exist.\\nRefresh the window, and then retry the operation.
1251136226	5	5	The command cannot be run because the specified pair has a secondary volume.\\nRefresh the window, and then retry the operation.
1251136227	5	5	The command cannot be run because the specified pair has no secondary volume.\\nRefresh the window, and then retry the operation.
1251136228	5	5	The command cannot be run because the specified pair has no secondary volume.\\nRefresh the window, and then retry the operation.
1251136229	5	5	The operation cannot be performed because the microcode versions of the SVP and the \\nDKCMAIN do not match.\\nVerify the microcode versions of the SVP and the DKCMAIN.
1251136230	5	5	The command cannot be run because the specified pair has a secondary volume.\\nRefresh the window, and then retry the operation.
1251136231	5	5	The processing cannot continue due to an internal logic contradiction.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
1251136253	5	5	The processing cannot continue due to an internal logic contradiction.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
1251136260	5	5	The operation cannot be performed because the specified primary volume is being migrated \\nby Volume Migration.\\nWait until the migration is complete, and then retry the operation.
1251136262	5	5	The operation cannot be performed because the specified secondary volume is being \\nmigrated by Volume Migration.\\nWait until the migration is complete, and then retry the operation.
1251136285	5	5	The pair operation cannot be performed because local replication pairs are being \\ninitialized.\\nWait until the initialization of the local replication pairs is complete, and then \\nretry the operation.
1251136286	5	0	The operation cannot be performed because the specified primary volume is an external \\nvolume with the data direct mapping enabled or a volume that belongs to a parity \\ngroup with the accelerated compression enabled.\\nVerify the specified volume.
1251136287	5	0	The operation cannot be performed because the specified secondary volume is an external \\nvolume with the data direct mapping enabled or a volume that belongs to a parity \\ngroup with the accelerated compression enabled.\\nVerify the specified volume.
1251136289	5	0	The pair operation cannot be performed because the T10 PI setting does not match \\nbetween the specified primary volume and secondary volume.\\nSpecify a primary volume and a secondary volume with the same T10 PI setting, and \\nthen retry the operation.
1251136290	5	5	A pair cannot be created, because the number of cascade pair layers exceeds 64.\\nVerify the settings.
1251136291	5	5	A pair with the clone attribute cannot be created, because three such pairs exist \\nin the layers from the specified primary volumes to the root volume in the highest layer.\\nVerify the pair configuration.
1251136292	5	5	A pair cannot be created, because the snapshot groups contain both pairs with the \\nsnapshot attribute and pairs with the clone attribute.\\nVerify the pairs added to the snapshot groups, and then retry the operation.
1251136293	5	5	One or more pairs cannot be created, because a Thin Image pair that uses the specified \\nprimary volume as the secondary volume is not in the PAIR or PSUS status.\\nChange the status of the pair to PAIR or PSUS, and then retry the operation.
1251136315	5	5	A pair cannot be created, because a pair belonging to the specified CTG exists in \\none of the layers from the specified primary volume to the root volume.\\nSpecify a different CTG, and then retry the operation.
1251136316	5	5	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\\nVerify the specified pairs.
1251136317	5	5	The following operations cannot be performed, because one or more Thin Image pairs \\nare using the secondary volume of the specified pair as a primary volume:\\n- Deleting the secondary volume\\n- Changing the secondary volume\\nDelete the Thin Image pairs that use the secondary volume of the specified pair as \\na primary volume, and then retry the operation.
1251136318	5	5	One or more pairs cannot be split, because a Thin Image pair that uses the primary \\nvolume of the specified pairs as the secondary volume is not in the PSUS status.\\nSplit the Thin Image pair that uses the primary volume of the specified pairs as \\nthe secondary volume, and then retry the operation.
1251136319	5	5	The specified pairs with the clone attribute cannot be split, because the configuration \\nof those pairs does not match the actual configuration.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
1251136320	5	5	The pair cannot be deleted, because one or more Thin Image pairs are using the secondary \\nvolume of the specified pair as a primary volume.\\nDelete the Thin Image pairs that use the secondary volume of the specified pair as \\na primary volume, and then retry the operation.
1251136321	5	5	The selected pairs cannot be resynchronized or restored, because one or more pairs \\nwhose status is not PAIR exist in layers lower than the layers of the selected pairs.\\nChange the statuses of all pairs in layers lower than the layers of the selected \\npairs to PAIR, and then retry the operation.
1251136322	5	5	The command cannot be run, because the shared memory needed to perform operations \\non Thin Image cascade pairs or pairs with the clone attribute is not installed.\\nInstall the shared memory.
1251136323	5	5	The current DKCMAIN firmware version does not support the specified operation.\\nVerify the DKCMAIN firmware version. The DKCMAIN firmware version might not match \\nthe SVP software version. Verify whether the DKCMAIN firmware version matches the \\nSVP software version.
1251136324	5	5	Pairs cannot be created, because the secondary volumes are not Dynamic Provisioning volumes.\\nSpecify Dynamic Provisioning volumes for the secondary volumes.
1251136346	5	5	An internal error occurred.\\nContact the HSSC.
1251136347	5	5	Pairs with the clone attribute cannot be created, because no secondary volumes are \\nspecified.\\nSpecify secondary volumes.
1251136351	5	5	The command cannot be run, because zero pages are being reclaimed on the specified \\nsecondary volumes.\\nWait until the processing to reclaim zero pages is complete, and then retry the operation.
1251136352	5	5	The command cannot be run, because the capacities of the specified secondary volumes \\nare being expanded.\\nWait until the processing to expand the capacities of the volumes is complete, and \\nthen retry the operation.
1251136353	5	5	The command cannot be run, because the statuses of the specified secondary volumes \\nare being changed.\\nWait until the processing to change the statuses is complete, and then retry the \\noperation.
1251136354	5	5	A pair cannot be created, because the cascade attribute setting differs from the \\nsettings of the pairs under the root volume. A pair for which the cascade attribute \\nis enabled and a pair for which the cascade attribute is disabled cannot exist under \\nthe root volume.\\nVerify the cascade attribute settings of the pairs under the root volume, and then \\nretry the operation.
1251136355	5	5	Dynamic Provisioning volumes with the SLU attribute cannot be assigned as secondary volumes.\\nSpecify Dynamic Provisioning volumes without the SLU attribute.
1251137028	5	5	The command cannot be run, because the specified primary volumes are being deleted.\\nSpecify different LDEVs as the primary volumes.
1251137029	5	5	The command cannot be run, because the specified secondary volumes are being deleted.\\nSpecify different LDEVs as the secondary volumes.
1251137030	5	5	The operation cannot be performed, because the specified S-VOL is a V-VOL for Thin Image.\\nSelect a different volume.
1251140005	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\nis not a DP-VOL.\\nSpecify an LDEV that is a DP-VOL with the SLU attribute.
1251140100	5	5	The specified operation cannot be performed, because the pool capacity exceeds the \\nsubscription limit of the pool.\\nVerify the subscription limit of the pool, and then retry the operation.
1251140873	5	5	The operation cannot be performed because a virtual LDEV ID is set for the specified LDEV.\\nSpecify a volume for which a virtual LDEV ID is not set.
1251144904	5	5	The operation cannot be performed because the DKCMAIN firmware version and the Storage \\nNavigator software version do not match.\\nUpdate the DKCMAIN firmware version to the latest, and then retry the operation.
1253913358	5	5	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 Thin Image pair.\\n- The Thin Image pair using the specified LDEV with the SLU attribute is not in the \\nPAIR status.\\n- The specified LDEV with the SLU attribute is a volume of a Thin Image pair with \\nthe fast clone attribute.\\nSpecify an LDEV with the SLU attribute that meets the following conditions.\\n- A volume used in a Thin Image pair\\n- The Thin Image pair volume in the PAIR status\\n- The volume used in the Thin Image pair whose attribute is not fast clone
1253913394	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\ndoes not exist. The LDEV might be deleted by a different user or application.\\nSpecify a different LDEV with the SLU attribute.
1253913422	5	5	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 Thin Image pair.\\n- The Thin Image pair using the specified LDEV with the SLU attribute is not in the \\nPAIR status.\\nSpecify an LDEV with the SLU attribute that meets the following conditions.\\n- A volume used in a Thin Image pair\\n- The Thin Image pair volume in the PAIR status
1253913423	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\nis bound to an LDEV with the ALU attribute.\\nUnbind the specified LDEV with the SLU attribute from the LDEV with the ALU attribute, \\nand then retry the operation.
1253913458	5	5	The operation cannot be performed because the capacity of the specified LDEV does \\nnot match that of the assigned LDEV.\\nSpecify an LDEV with the same capacity as the assigned LDEV.
1253913481	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\nis a DP-VOL.\\nSpecify an LDEV that is not a DP-VOL with the SLU attribute.
1253914446	1	1	An error occurred during internal processing on the storage system.\\nContact the HSSC.
1253914475	5	5	The operation cannot be performed because the specified pool is not a Thin Image pool.\\nSpecify a Thin Image pool.
1253914504	5	5	The operation cannot be performed because the specified pool number is not set within \\nthe available range.\\nSpecify an existing pool with pool number within the range from 0 to 127.
1256590027	5	5	The operation cannot be performed because the specified SLU ID is not in valid format.\\nContact the HSSC.
1256590028	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\ndoes not exist. The LDEV might be deleted by a different user or application.\\nSpecify a different LDEV with the SLU attribute.
1256590029	5	5	The operation cannot be performed because the specified SLU ID is not in valid format.\\nContact the HSSC.
1256590030	5	5	The operation cannot be performed because the specified LDEV with the SLU attribute \\ndoes not exist. The LDEV might be deleted by a different user or application.\\nSpecify a different LDEV with the SLU attribute.
1256590703	1	1	An error occurred during internal processing on the storage system.\\nContact the HSSC.
1256590704	5	5	The operation cannot be performed because the specified start slot number exceeds \\nthe maximum slot number of the volume.\\nVerify the start slot number.
1256590705	5	5	The operation cannot be performed because the specified end slot number exceeds the \\nmaximum slot number of the volume.\\nVerify the end slot number.
1256590706	5	5	The operation cannot be performed because the specified number of slots exceeds the \\nmaximum for search.\\nSet the number of slots within the range from 1 to 131072.
1256590707	5	5	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 Thin Image pair.\\n- The Thin Image pair using the specified LDEV with the SLU attribute is not in the \\nPAIR status.\\nSpecify an LDEV with the SLU attribute that meets the following conditions.\\n- A volume used in a Thin Image pair\\n- The Thin Image pair volume in the PAIR status
1256590708	5	5	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 Thin Image pair.\\n- The Thin Image pair using the specified LDEV with the SLU attribute is not in the \\nPAIR status.\\nSpecify an LDEV with the SLU attribute that meets the following conditions.\\n- A volume used in a Thin Image pair\\n- The Thin Image pair volume in the PAIR status
1256590709	5	5	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 Thin Image pair.\\n- The Thin Image pair using the specified LDEV with the SLU attribute is not in the \\nPAIR status.\\nSpecify an LDEV with the SLU attribute that meets the following conditions.\\n- A volume used in a Thin Image pair\\n- The Thin Image pair volume in the PAIR status
1299698760	5	6	The Dynamic Provisioning volume is not associated with a pool.\\nAssociate the Dynamic Provisioning volume with a pool, then retry the operation.
1299699539	5	6	The Dynamic Provisioning volumes are not associated with the same pool.\\nAssociate the Dynamic Provisioning volumes with the same pool, then retry the operation.
1300650958	5	6	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
1342657378	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
1342657409	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
1342659203	1	2	An internal logical error occurred.\\nIf the problem persists despite retrying, please call the HSSC.
1342692006	1	5	The operation failed because the audit log is being processed. Please wait for a \\nwhile, and then retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
1342692009	1	5	The Storage Navigator is transferring the file to the FTP server. Wait for a while, \\nthen retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
1342692010	1	5	Another user is downloading the file or transferring the file to the FTP server. \\nPlease wait for a while, and then retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
1342692032	1	5	Transfer to the FTP server is disabled. Check the setting.\\nIf the problem persists despite retrying, please call the HSSC.
1342692033	1	5	Failed to connect to the FTP server. Check the IP address, or the connection between \\nthe Storage Navigator and the FTP server.\\nIf the problem persists despite retrying, please call the HSSC.
1342692034	1	5	The file transfer to the FTP server failed. Check the user ID and the password.\\nIf the problem persists despite retrying, please call the HSSC.
1342692035	1	5	The file transfer to the FTP server failed. Check the output folder and the status \\nof the FTP server.\\nIf the problem persists despite retrying, please call the HSSC.
1342692036	1	5	The file transfer to the FTP server failed. If this problem persists, please call the HSSC.\\nIf the problem persists despite retrying, please call the HSSC.
1342692037	1	5	The complete operation is performed to all SIMs related to Audit Log.\\nIf the problem persists despite retrying, please call the HSSC.
1342692038	1	5	Complete operation of SIMs failed because the number of audit logs that had not been \\ntransferred exceeded the threshold.\\nIf the problem persists despite retrying, please call the HSSC.
1342692039	1	5	The complete operation of the SIM may not have completed since the SVP is busy.\\nIf the problem persists despite retrying, please call the HSSC.
1342717830	1	3	An invalid value is included in the management file of the audit log. Please retry \\nthe operation.\\nIf the problem persists despite retrying, please call the HSSC.
1343587626	1	2	CVAE version information ID is invalid. Check the setting, and then retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
1343611554	1	3	The login could not be performed because a function failed to start during Storage \\nNavigator initialization.\\nIf the problem persists despite retrying, please call the HSSC.
1343615562	1	5	The operation failed because the SVP OS does not support IPv6.\\nIf the problem persists despite retrying, please call the HSSC.
1343618283	1	2	No more CVAE version infomasion can be registered, because the number of registered \\nCVAE version infomasion reached the maximum. Reduce the number of CVAE version infomasion \\nand then retry the operation.\\nIf the problem persists despite retrying, please call the HSSC.
1387643877	1	4	An unknown error was detected.\\nIf nothing changes despite retrying, call the HSSC.
1387703459	5	5	Paths cannot be added because the specified host group and LDEV belong to different \\nVirtual Storage Machines.\\nSpecify a host group and an LDEV, both of which belong to the same Virtual Storage Machine.
1387703460	5	5	The path definition on the external volume that has the nondisruptive migration attribute \\ncannot be performed because the ID of the specified host group is 0 and the security \\nswitch of the specified port is off.\\nSpecify a host group whose ID is 1 or larger, or turn the security switch on, and \\nthen retry the operation.
1387703461	5	5	The specified port does not exist. Or the specified port type is not the Fibre or \\niSCSI port.\\nThe configuration information has already been changed. Verify the settings, and \\nthen request the configuration information setting again.
1387703462	5	5	The Fibre port settings cannot be applied to the iSCSI port.\\nVerify the settings, and then retry the operation.
1387703463	5	5	Host Mode Option 51 cannot be set because the number of ports on which Host Mode \\nOption 51 is set has reached the maximum.\\nVerify the ports on which Host Mode Option 51 is set, and then retry the operation.
1387703464	5	5	Host Mode Option 51 can be set for only one host group on a port.\\nVerify the ports on which Host Mode Option 51 is set, and then retry the operation.
1387703465	5	5	Characters or the number of characters for the iSCSI target name, iSCSI target alias, \\niSCSI name, or the nickname of the iSCSI name is not valid.\\nEnter the item using the valid characters or number of characters.
1387703466	5	5	An invalid user authentication is specified.\\nVerify the settings, and then retry the operation.
1387703467	5	5	The specified iSCSI target is not registered.\\nVerify the settings, and then retry the operation.
1387703468	1	5	The composition information operation failed.\\nVerify the configuration information.
1387703490	5	5	LU path information cannot be acquired.\\nWait for a while, and then retry the operation.
1387703491	1	2	The mistake is found in the set parameter.\\nCall the HSSC.
1387703492	1	6	The specified iSCSI name is not registered.\\nCheck the setting.
1387703493	5	5	No more iSCSI names can be added to the port because the number of iSCSI names has \\nreached the maximum.\\nRemove unnecessary iSCSI names, and then retry the operation.
1387703494	1	5	The characters used for the user ID or the number of the characters of the user ID \\nis invalid. \\nCheck the setting, and then retry the operation. \\nCorrect the specified contents, and request again.
1387703495	5	5	The secret is incorrect.\\nCorrect the specified contents, and request again.
1387703496	5	5	The specified user name is already used on the same port.\\nSpecify a different user name.
1387703497	5	5	The specified user name is not registered.\\nVerify the settings, and then retry the operation.
1387703498	5	5	The CHAP user cannot be set because the user authentication of the iSCSI target is disabled.\\nEnable the user authentication.
1387703499	5	5	No more CHAP user IDs can be added to the port because the number of CHAP user IDs \\nhas reached the maximum.\\nRemove unnecessary CHAP user IDs, and then retry the operation.
1387703521	5	6	This port is not properly equipped.\\nCheck the setting.
1387703522	5	6	The target cannot be set because the number of targets exceeds the maximum that can \\nbe set in a port.\\nCheck the setting.
1387703523	5	5	The specified iSCSI target name or target alias is already used on the same port.\\nSpecify a different iSCSI target name or target alias.
1387703524	5	5	The specified iSCSI target name or target alias cannot be registered because it is \\nreserved for iSCSI target #00.\\nSpecify a different iSCSI target name or target alias.
1387703525	1	3	An error occurred while connecting to the storage system.\\nIf nothing changes despite retrying, call the HSSC.
1387703526	1	6	The specified port is not an iSCSI port.\\nCheck the setting.
1387703527	5	5	The operation cannot be performed because RAID Manager is in process.\\nWait for a while, and then retry the operation. If this problem persists, call the HSSC.
1387703528	5	5	The specified Host Name cannot be registered, because it is already used in this port.\\nCheck the setting.
1387703529	1	6	The operation cannot be performed because a resource group is not locked.\\nIf this problem persists, contact the HSSC.
1387703530	5	6	The specified LDEV numbers are not valid.\\nSpecify different LDEV numbers.
1387703552	5	6	The status of the global-active device pair that uses the specified LDEV is not PSUS.\\nChange the status of the global-active device pairs to PSUS, and then retry the operation.
1387703553	5	6	The resource group to which the selected host groups or LDEVs belong is locked by \\na different user.\\nWait until the resource groups is unlocked by the different user, and then retry \\nthe operation.
1387703554	5	6	The specified LDEVs do not exist.\\nClick the refresh button to have the latest information displayed on the window, \\nand then verify whether the specified LDEVs exist.
1387703555	5	6	The operation cannot be performed because the number of host groups with LUN paths \\nto LDEVs on which ALUA is enabled exceeds the maximum on the storage system.\\nDisable the ALUA mode of LDEVs that do not need the setting.
1387703556	5	6	The user authentication cannot be performed.\\nVerify the setting, and then log in again.
1387703557	5	6	An error occurred on the storage system.\\nRetry the operation. If this problem persists, contact the HSSC.
1387703558	5	6	No LUN paths are set to the selected host groups.\\nSet LUN paths to the selected host groups, and then retry the operation.
1387703559	5	6	The specified host group IDs are not valid.\\nSpecify different host group IDs.
1387703560	5	6	The specified host groups do not exist.\\nClick the refresh button to have the latest information displayed on the window, \\nand then verify whether the specified host groups exist.
1387703561	5	6	The operation cannot be performed because the specified Asymmetric Access States \\nis not supported.\\nVerify the setting, and then retry the operation.
1387703583	5	6	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
1387703584	5	6	The specified host groups or LDEVs cannot be used because you do not have permission \\nto access a resource group to which the specified host groups or LDEVs belong.\\nRetry the operation with permission to access the resource group containing the specified \\nhost groups or LDEVs, or ask the administrator for access permission.
1387703585	5	6	The operation cannot be performed because any blocked MP exists.\\nRestore the blocked MP, and then retry the operation.
1387703586	5	6	The operation cannot be performed because different microcode versions coexist on \\nthe storage system.\\nContact the HSSC to change the microcode, and then retry the operation.
1387703587	5	6	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
1387703588	1	5	The operation cannot be performed because the specified volume is an external volume \\nwith Data Direct Mapping enabled.\\nSpecify a volume on which Data Direct Mapping is disabled.
1387703589	5	5	The current DKCMAIN microcode version does not support the specified operation.\\nVerify the microcode versions of the DKCMAIN and the SVP.
1387703590	1	5	No LUN paths can be created because the specified LDEVs belong to a parity group \\nwith accelerated compression enabled.\\nSpecify LDEVs that belong to a parity group with accelerated compression disabled.
1387703614	5	5	LUN paths using LDEVs with T10 PI enabled cannot be added because T10 PI is disabled \\non the specified ports.\\nEnable T10 PI on the specified ports, or disable T10 PI on the LDEVs.
1387703615	5	5	The specified LDEVs cannot be operated because T10 PI is enabled.\\nSpecify LDEVs on which T10 PI is disabled.
1387703616	5	7	No SFP module that supports the specified channel speed is installed.\\nPerform either of the following:\\n- Replace the installed SFP module with one that supports the specified channel speed.\\n- Verify which channel speeds are supported by the installed SFP module, and then \\nspecify one of those channel speeds.
1387704420	5	6	The operation cannot be performed because the selected ports are virtual ones.\\nVerify the specified ports.
1387704421	5	6	The operation cannot be performed because the selected LDEVs belong to "NAS_Platform_System_RSG" \\nwith resource group ID 1023 or LUN paths are set to the NAS platform (User LU).\\nMove the selected LDEVs to a different resource group from "NAS_Platform_System_RSG" \\nwith resource group ID 1023 or delete the LUN paths to the NAS platform (User LU) \\nfrom the selected LDEVs.
1387704422	5	6	A LUN path to the LDEV that is set as a command device cannot be set to the specified port.\\nDisable the command device setting on the specified LDEV, or specify a different LDEV.
1387792833	5	5	The specified ports do not support T10 PI Mode.\\nSpecify ports that support T10 PI Mode.
1387792834	5	5	The operation cannot be performed because the storage system is in internal process, \\nor a different user is changing the configuration.\\nWait for a while, and then retry the operation.
1387792835	1	5	The specified port is blocked.\\nRestore the blocked status of the port, and then retry the operation. If the blocked \\nstatus cannot be restored, contact the HSSC.
1387792836	5	5	The operation cannot be performed because the resource group to which the specified \\nports belong is used by a different user.\\nWait for the resource lock to be released, and then retry the operation.
1387792837	1	5	The operation cannot be performed because the storage system requires maintenance, \\nsuch as that the storage system is blocked, or that the shared memory is inconsistent.\\nContact the HSSC.
1387792838	5	5	The operation cannot be performed because an error occurred on the storage system.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
1387792839	5	5	The operation cannot be performed because the specified ports are not installed.\\nSpecify ports that are installed, and then retry the operation.
1387792840	5	5	The T10 PI mode cannot be disabled for all or some of the specified ports due to \\none 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 \\nT10 PI enabled.\\nVerify that the settings for the specified ports and the associated ports are applied. \\nIf they are not applied, delete the LUN paths set to LDEVs with T10 PI enabled.
1387793021	5	5	Host Mode Option 51 (Round Trip Set Up Option) cannot be set for the specified host \\ngroup because the channel board of 16FC2 does not support Host Mode Option 51.\\nIt is required to mount a channel board that supports Host Mode Option 51. Contact the HSSC.
1387793023	5	5	The host mode option cannot be released because a path is defined on an LDEV that \\nbelongs to a different virtual storage machine from the one to which the specified \\nhost group belongs.\\nRelease the path definition on the LDEV that belongs to a different virtual storage \\nmachine from the one to which the specified host group belongs, and then retry the \\noperation.
1387795997	5	5	Paths cannot be set, because deduplication system data volumes are specified.\\nSelect different LDEVs.
1387795998	5	5	Command devices cannot be set, because deduplication system data volumes are specified.\\nSelect different LDEVs.
1387796836	5	5	The LUN paths cannot be set, because the specified LDEVs are being deleted.\\nSelect different LDEVs.
1387797769	5	5	The path definition between a host group and two or more LDEVs with the ALU attribute \\ncannot be performed.\\nVerify the settings, and then retry the operation.
1387797770	5	5	The path cannot be removed because there is an LDEV with the ALU attribute, to which \\nan LDEV with the SLU attribute is bound. \\nUnbind the LDEV with the SLU attribute from the LDEV with the ALU attribute, and \\nthen retry the operation.
1505172431	1	5	The status of the storage system requires the maintenance\\n(for example, the storage system is blocked, the shared memory is inconsistent, or \\nsome other factor).\\nCheck the status of the storage system\\n(if the storage system is blocked, shared memory is inconsistent, or some other factor).\\nIf this problem persists, please call the HSSC.
1505172435	1	5	An error occurred while communicating with the storage system.\\nIf the same problem persists despite retrying, please call the HSSC.
1505172683	5	5	The specified operation cannot be performed due to one of the following maintenance \\noperations:\\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.\\nWait for a while, and then retry the operation.
1505174322	5	5	Processing cannot be performed because of Data Retention Utility settings.\\nRelease the setting of Data Retention Utility, then retry the operation.
1505174326	5	5	Journal volumes are included in the external volumes to be maintained.\\nDelete all the pairs that are using the journal volumes to be maintained. 
1505177236	5	5	The restore operation has been failed, because the specified LDEV was not shredded \\nor formatted.\\nShred or format the specified LDEV. If the specified LDEV is a Dynamic Provisioning \\nvolume (DP-VOL), recover the pool first.
1505177240	5	5	A pair of TrueCopy or Universal Replicator is defined.\\nRelease the pair definition, and then retry the operation.
1505177241	5	5	A pair of TrueCopy or Universal Replicator is defined.\\nDelete the pair definition or suspend the pair, and then retry the operation.
1505177242	5	5	A pair of ShadowImage or Thin Image is defined.\\nRelease the pair definition, and then retry the operation. When quick split is in \\nprogress, suspend the pair, and then release it.
1505177243	5	5	A pair of ShadowImage is defined.\\nRelease the pair definition, and then retry the operation. When quick split is in \\nprogress, suspend the pair, and then release it.
1505177266	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
1505177267	5	5	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
1505202193	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505261806	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505262060	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505266609	5	5	Necessary program products are not installed.\\nInstall the following program products:\\n- Universal Volume Manager\\n- Open Volume Management (necessary for mapping and creating an LDEV at the same time)
1505269529	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505269530	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505291596	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505291627	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505296464	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505296465	5	5	The number of external volumes that can be registered in the storage system has reached \\nthe maximum.\\nReduce the number of external volumes registered in the storage system, then retry \\nthe configuration operation.
1505296466	5	5	The configuration cannot be changed because the LUN Path is remained in the target volume. \\nRelease the LUN Path, then change the configuration again.
1505296468	5	5	The setting process has not been executed because there is no error in this setting, \\nbut an error in the others settings. \\nCheck the error factor in the others settings.
1505351145	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505351146	1	5	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1505352108	5	5	This function is not supported.\\nCheck whether the DKCMAIN firmware version and the Storage Navigator software version \\nare mismatched.
1505352170	5	5	Another maintenance processing is in progress.\\nWait for a while, then retry the operation.
1505352205	5	5	The command was rejected, because the licensed capacity has exceeded the maximum.\\nCheck the licensed capacity, then specify it within the licensed capacity or add \\nthe licensed capacity.    
1505359957	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
1505359986	1	5	An error occurred on the DKC side.\\nIf this problem persists, please call the HSSC.
1505360020	5	5	The operation of the external volume has been failed because all the paths to the \\nexternal volume are blocked.\\nRestore more than one path to the external volume, then perform the operation of \\nthe external volume.
1617270503	5	5	The operation cannot be executed because the specified pool has no monitoring data.\\nCheck the status of the pool, and then retry the operation.
1617270505	5	5	The operation cannot be executed because there is only one tier in the specified pool.\\nCheck the configuration of tier in the pool.
1617300289	1	5	This function cannot be used because the encryption function is not supported.\\nMount the encryption DKA.
1617300290	1	5	The specified operation cannot be performed because the SAS controller is blocked.\\nContact the HSSC to restore the blocked status of the SAS controller, and then retry \\nthe operation.
1617300291	5	5	The encryption environmental settings are performed repeatedly.\\nVerify the settings.
1617300292	5	3	This function is not available. Encryption License Key is required.\\nInstall the required program product.
1617330080	1	5	A parameter error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
1617330082	5	5	The number of created keys exceeds the maximum.\\nVerify the setting.
1617330083	5	5	The key cannot be deleted.\\nSpecify a free key.
1617330084	5	5	There are not enough free keys.\\nCreate free keys.
1617330086	1	5	Some blocked parts exist because an error occurred on the DKC side.\\nContact the HSSC to have the blockage restored.
1617330087	1	5	Some blocked parts exist because an error occurred on the DKC side.\\nContact the HSSC to have the blockage restored.
1617330088	5	5	An error occurred on the DKC side. A parity group that is not blocked is included \\nin the specified parity groups.\\nBlock all of the specified parity groups, and then retry the operation.
1617330089	5	5	An error occurred on the DKC side. The encryption environmental settings cannot be \\ninitialized because there is an encrypted parity group.\\nDisable the encryption settings for the parity group, and then retry the operation.
1617330111	5	5	An error occurred on the DKC side during the encryption environmental settings.\\nInitialize the encryption environmental settings, and then retry the operation. If \\nthis problem persists, contact the HSSC.
1617330112	5	5	Some blocked parts exist because an error occurred on the DKC side during the encryption \\nenvironmental settings.\\nContact the HSSC to have the blockage restored. After that initialize the encryption \\nenvironmental settings, and then retry the operation.
1617330113	1	5	The specified operation cannot be performed because the SAS controller is blocked.\\nContact the HSSC to have the blockage restored. After that initialize the encryption \\nenvironmental settings, and then retry the operation.
1617330114	1	2	An error occurred during Storage Navigator processing.\\nInitialize the encryption environmental settings, and then retry the operation. If \\nthis problem persists, contact the HSSC.
1638384228	5	0	The pair operation of Universal Replicator cannot be performed because the firmware \\nexchange is in progress or interrupted.\\nWait until the firmware exchange is complete, and then retry the operation.
1638384229	5	0	The operation of Universal Replicator cannot be performed because the shared memory \\nis not installed on the storage system.\\nInstall shared memory.
1638384231	5	0	The specified pair or journal does not exist.\\nRefresh the window, and check the pair status or journal status.
1638384233	5	5	The operation cannot be performed because the specified volume is being maintained.\\nWait until the maintenance is complete, and then retry the operation.
1638384286	5	0	The Create Pairs operation cannot be performed because the specified primary volume \\nis used by global-active device.\\nSelect a different volume, and then retry the operation.
1638384287	5	0	The Create Pairs operation cannot be performed because the reservation attribute \\nof global-active device is set on the specified primary volume.\\nSelect a different volume, and then retry the operation.
1638384288	5	0	The Create Pairs operation cannot be performed because the specified secondary volume \\nis used by global-active device.\\nSelect a different volume, and then retry the operation.
1638384289	5	0	The Create Pairs operation cannot be performed because the reservation attribute \\nof global-active device is set on the specified secondary volume.\\nSelect a different volume, and then retry the operation.
1638385185	5	0	The remote command device cannot be assigned because Universal Replicator pairs in \\nthe selected mirror ID share the same volumes with global-active device pairs.\\nVerify the selected mirror ID. If the correct mirror ID is selected, delete the global-active \\ndevice pairs that share the same volumes with Universal Replicator pairs in the mirror \\nID, and then retry the operation.
1638385186	5	5	A Universal Replicator pair for delta resync cannot be created. The selected primary \\nvolume of the Universal Replicator pair for delta resync must meet either of the \\nfollowing requirements:\\n- The volume is the secondary volume of a global-active device pair and the global-active \\ndevice pair is in the PAIR status.\\n- The volume is the primary volume of a global-active device pair and the I/O mode is Block.\\nVerify the setting to have the requirements met, and then retry the operation.
1638385187	5	5	A Universal Replicator pair cannot be created due to either of the following reasons:\\n- A global-active device pair that uses the selected primary volume does not belong \\nto a consistency group.\\n- A global-active device pair that shares the same volume with a different Universal \\nReplicator pair using the selected journal belongs to a different consistency group \\nof global-active device.\\nVerify the configurations of the global-active device pair and the Universal Replicator \\npair, and then retry the operation.
1638385188	5	5	A delta resync pair cannot be created. The selected mirror ID is used by a global-active \\ndevice pair that uses the selected primary volume.\\nVerify the selected primary volume. If the correct volume is selected, select a mirror \\nID that is not used by a global-active device pair, and then retry the operation.
1638385189	5	5	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 \\nof global-active device.\\n- A global-active device pair that shares the same volume with a different delta \\nresync pair using the selected journal belongs to a different consistency group of \\nglobal-active device.\\nVerify that all of the global-active device pairs that share the same volumes with \\ndelta resync pairs with the selected journal ID belong to the same consistency group \\nof global-active device, and then retry the operation.
1638385190	5	5	A Universal Replicator pair cannot be created. The selected primary volume of the \\nUniversal Replicator pair must meet the following requirement:\\n- The volume is the primary volume of a global-active device pair and the global-active \\ndevice pair is in the PAIR status.\\nVerify that the selected primary volume is used as the primary volume of the global-active \\ndevice pair, change the status of the global-active device pair to PAIR, and then \\nretry the operation.
1638385191	5	5	A delta resync pair cannot be created due to either of the following reasons:\\n- A global-active device pair that uses the selected primary volume does not belong \\nto a consistency group.\\n- A global-active device pair that shares the same volume with a different delta \\nresync pair using the selected journal belongs to a different consistency group of \\nglobal-active device.\\nVerify the configurations of the global-active device pair and the delta resync pair, \\nand then retry the operation.
1638385192	5	5	A Universal Replicator pair cannot be created. The selected mirror ID is used by \\na global-active device pair that uses the selected primary volume.\\nVerify the selected primary volume. If the correct volume is selected, select a mirror \\nID that is not used by a global-active device pair, and then retry the operation.
1638385193	5	5	A Universal Replicator 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 \\nof global-active device.\\n- A global-active device pair that shares the same volume with a different Universal \\nReplicator pair using the selected journal belongs to a different consistency group \\nof global-active device.\\nVerify that all of the global-active device pairs that share the same volumes with \\nUniversal Replicator pairs with the selected journal ID belong to the same consistency \\ngroup of global-active device, and then retry the operation.
1638385194	5	5	A Universal Replicator pair cannot be created. The secondary volume of the global-active \\ndevice pair that uses the selected primary volume of the Universal Replicator pair \\nand the primary volume of the Universal Replicator pair for delta resync that uses \\nthe selected secondary volume of the Universal Replicator pair do not match.\\nVerify the selected primary and secondary volumes of the Universal Replicator pair. \\nThe primary and secondary volumes of the Universal Replicator pair must meet all \\nof the following requirements:\\n- The primary volume of the Universal Replicator pair uses the secondary volume (A) \\nof the global-active device pair.\\n- The secondary volume of the Universal Replicator pair is used by a different Universal \\nReplicator pair for delta resync, and the primary volume (B) of this pair is the \\nsecondary volume of the global-active device pair.\\n- Volume A and volume B are on the same storage system.
1638385216	5	5	The resync operation cannot be performed because the pair in which the selected volume \\nis used applies to either of the following:\\n- The status of the global-active device pair is not PAIR, COPY, PSUS, PSUE, or SSWS.\\n- The status of the delta resync pair is not HLDE.\\nVerify the selected volume. If the correct volume is selected, change the status \\nof the global-active device pair or the delta resync pair, and then retry the operation.
1638385217	5	5	The delta resync operation cannot be performed because the status of the global-active \\ndevice pair that uses the selected primary volume is not SSWS.\\nVerify the selected volume. If the correct volume is selected, change the status \\nof the global-active device pair to SSWS, and then retry the operation.
1638385218	5	5	A Universal Replicator pair or a delta resync pair cannot be created because the \\nselected remote storage system does not support the connection configuration of global-active \\ndevice and Universal Replicator.\\nVerify the selected primary volume. If the correct volume is selected, take a note \\nof the DKCMAIN microcode version of the remote storage system, and then contact the HSSC.
1638385219	5	5	The operation cannot be performed because the storage system is in internal process.\\nWait for a while, and then retry the operation.
1638385225	5	5	A Universal Replicator pair cannot be created because the secondary volume of a global-active \\ndevice pair that uses the selected primary volume is not shared with a delta resync pair.\\nVerify the selected primary and secondary volumes. If the correct volumes are selected, \\nshare the secondary volume of the global-active device pair with the delta resync \\npair, and then retry the operation.
1638385247	5	5	A Universal Replicator pair for delta resync cannot be created because either of \\nthe following requirements is not met.\\n- The primary volume of the Universal Replicator pair for data resync uses the primary \\nvolume of the global-active device pair.\\n- The secondary volume of the Universal Replicator pair for delta resync is used \\nby a Universal Replicator pair that is created by a different mirror.\\nVerify the selected primary and secondary volumes of the Universal Replicator pair \\nfor delta resync. The primary and secondary volumes of the Universal Replicator pair \\nfor delta resync must meet all of the following requirements:\\n- The primary volume of the Universal Replicator pair for delta resync uses the primary \\nvolume of the global-active device pair.\\n- The secondary volume of the Universal Replicator pair for delta resync is used \\nby a Universal Replicator pair that is created in a different mirror.
1638385340	5	5	A Universal Replicator pair for delta resync cannot be created. The secondary volume \\nof the global-active device pair that uses the selected primary volume of the Universal \\nReplicator pair for delta resync and the primary volume of the Universal Replicator \\npair that uses the selected secondary volume of the Universal Replicator pair for \\ndelta resync do not match.\\nVerify the selected primary and secondary volumes of the Universal Replicator pair \\nfor delta resync. The primary and secondary volumes of Universal Replicator pair \\nfor delta resync must meet all of the following requirements:\\n- The primary volume of the Universal Replicator pair for delta resync uses the secondary \\nvolume (A) of the global-active device pair.\\n- The secondary volume of the Universal Replicator pair for delta resync is used \\nby a different Universal Replicator pair and the primary volume (B) of this pair \\nis the secondary volume of the global-active device pair.\\n- Volume A and volume B are on the same storage system.
1638385342	5	5	Universal Replicator pairs in cascading configuration cannot be created. To create \\nthe specified Universal Replicator 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 \\nof Universal Replicator pairs in a different mirror.\\n- The primary volume is not a Dynamic Provisioning volume.\\n- The secondary volume is not a Dynamic Provisioning volume.\\nVerify the status of the specified primary and secondary volumes. To create a 3DC \\ncascading configuration of three Universal Replicator sites, create a Universal Replicator \\npair between the primary and intermediate sites first, and then create one between \\nthe intermediate and secondary sites.
1638385344	5	5	A Universal Replicator pair cannot be created because the specified primary volume \\nis an external volume with Data Direct Mapping enabled.\\nVerify the setting for the specified primary volume.
1638385345	5	5	A Universal Replicator pair cannot be created because the microcode version on the \\nsecondary storage system does not support Data Direct Mapping.\\nVerify whether the secondary storage system supports Data Direct Mapping.
1638385346	5	5	A Universal Replicator pair cannot be created because the specified secondary volume \\nis an external volume with Data Direct Mapping enabled.\\nVerify the setting for the specified secondary volume.
1638385347	5	5	A Universal Replicator pair cannot be created because the microcode version on the \\nprimary storage system does not support Data Direct Mapping.\\nDisable Data Direct Mapping on the secondary volume.
1638385348	5	5	A Universal Replicator pair cannot be created because the primary storage system \\ndoes not support the pair creation function.\\nContact the HSSC.
1638385349	5	5	A Universal Replicator pair cannot be created because the specified primary volume \\nis an external volume with Data Direct Mapping enabled.\\nVerify the setting for the specified primary volume.
1638385371	5	5	The operation cannot be performed because the T10 PI setting differs between the \\nspecified primary volume and secondary volume.\\nApply the same T10 PI setting to the specified primary and secondary volumes, and \\nthen retry the operation.
1638385372	5	5	A pair cannot be created.\\nVerify the status of the Universal Replicator pair that uses the specified secondary \\nvolume. If the pair status is SIMPLEX, create a pair again. If it is not SIMPLEX, \\ncontact the HSSC.
1638387387	5	5	The operation cannot be performed, because DP-VOLs whose capacity saving status is \\nnot Disabled or deduplication system data volumes are selected.\\nVerify the setting. The operation cannot be performed for deduplication system data volumes.\\nDisable the capacity saving setting for DP-VOLs whose capacity saving status is not \\nDisabled. Verify that the capacity saving status is Disabled, and then retry the \\noperation.
1638389122	5	5	The Create Pairs operation cannot be performed because no virtual LDEV ID is set \\non the volume specified as the secondary volume.\\nVerify the status of the specified secondary volume.
1638389123	5	5	The specified local storage system does not support nondisruptive migration.\\nVerify the firmware version of the local storage system. Or specify an LDEV on which \\nthe virtualization management is disabled.
1638389124	5	5	The specified remote storage system does not support nondisruptive migration.\\nVerify the firmware version of the remote storage system. Or specify an LDEV on which \\nthe virtualization management is disabled.
1638389125	5	5	The Create Pairs operation cannot be performed because no virtual LDEV ID is set \\non the volume specified as the primary volume.\\nVerify the status of the specified primary volume.
1638389126	5	5	The specified volume cannot be registered as a journal volume because it is an LDEV \\non which the virtualization management is enabled.\\nVerify the status of the specified volume.
1638389127	5	5	The specified volume cannot be registered as a journal volume because it is an LDEV \\non which the virtualization management is enabled.\\nVerify the status of the specified volume.
1638389128	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary 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 \\nmanagement 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 \\nmanagement 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, \\non which the virtualization management is enabled, is not valid.\\nVerify the status of the specified primary or secondary volume, or the serial number \\nor model of the virtual storage machine.
1638389129	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary 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 \\nthe virtualization management is disabled, but the specified volume is one on which \\nit is enabled.\\n- The volume already registered in the selected journal group is an LDEV on which \\nthe virtualization management is enabled, but the specified volume is one on which \\nit is disabled.\\n- The serial number or model of the virtual storage machine of the specified LDEV, \\non which the virtualization management is enabled, is not valid.\\nVerify the status of the specified primary or secondary volume, or the serial number \\nor model of the virtual storage machine.
1638389130	5	5	The Create Pairs operation cannot be performed because the cache mode of the external \\nvolume that is mapped for online data migration and is specified as the primary volume \\nis set to Through.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation. Or specify an external volume mapped for the online \\ndata migration, whose cache mode is other than Through, and then retry the operation.
1638389131	5	5	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume is an external volume mapped for the online data migration, and is \\nalso used as the pair volume of Volume Migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation. Or delete the Volume Migration pair, and then retry \\nthe operation.
1645779525	5	6	The LDEV cannot be formatted because one of the following maintenance operations \\nis 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\\nWait for a while, and then retry the operation.
1645779526	5	6	The LDEV cannot be restored because one of the following maintenance operations is \\nin 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\\nWait for a while, and then retry the operation.
1645779527	5	6	The LDEVs cannot be formatted because Verify LDEVs is in process.\\nWait for a while, and then retry the operation. If the problem persists, contact the HSSC.
1645779528	5	6	The LDEVs cannot be restored because Verify LDEVs is in process.\\nWait for a while, and then retry the operation. If the problem persists, contact the HSSC.
1645779529	1	3	The LDEV cannot be formatted because the storage system is in the state where a maintenance \\noperation is required (such as blockage or shared memory inconsistency).\\nRestore the storage system referring to the manual, and then retry the operation. \\nIf this problem persists, contact the HSSC.
1645779530	1	3	The LDEV cannot be restored because the storage system is in the state where a maintenance \\noperation is required (such as blockage or shared memory inconsistency).\\nRestore the storage system referring to the manual, and then retry the operation. \\nIf this problem persists, contact the HSSC.
1645898688	1	2	A file open error has occurred.\\nIf the same error occurs despite retrying, please call the HSSC.
1645898689	1	2	A file access error has occurred.\\nIf the same error occurs despite retrying, please call the HSSC.
1645958270	5	5	An invalid relocation speed was specified.\\nSpecify a supported relocation speed, and then retry the operation. If this problem \\npersists, contact the HSSC.
1645958271	5	5	The tier with heavy I/O load exists in the monitoring pool.\\nVerify the device configuration of the storage system.
1645958272	5	5	The zero page reclamation cannot be performed because the specified Dynamic Provisioning \\nvolume is used as a journal volume.\\nRelease the journal volume setting.
1645958273	5	5	The capacity of the specified Dynamic Provisioning volume cannot be expanded because \\nthe configuration of journal volume is changing.\\nWait until the configuration change is complete, and then retry the operation.
1645958274	5	6	The encryption cannot be enabled on the specified parity groups because the accelerated \\ncompression is enabled.\\nDisable the accelerated compression, and then enable the encryption.
1645958276	5	5	To use a pool with the Dynamic Tiering function enabled, it is required to install \\nthe additional shared memory.\\nInstall shared memory.
1645958277	5	5	The specified operation cannot be performed because Verify LDEVs is in process.\\nRetry the operation. If this problem persists, contact the HSSC.
1645958333	5	5	The operation cannot be performed because a Dynamic Provisioning volume exists in \\nthe specified pool.\\nSpecify a different pool, or delete the Dynamic Provisioning volume, and then retry \\nthe operation.
1645958334	5	5	The operation cannot be performed because the pool does not have enough free space \\nfor Data Direct Mapping.\\nAdd a volume whose attribute is not Data Direct Mapped to the pool, and then retry \\nthe operation.
1645958335	5	5	The specified volume cannot be added to any pool other than Dynamic Provisioning \\npools because its attribute is Data Direct Mapped .\\nSpecify a volume whose attribute is not Data Direct Mapped.
1645958336	5	5	The emulation type of the specified volume is not OPEN-V.\\nSpecify a volume whose emulation type is OPEN-V.
1645958337	5	5	A pool with Data Direct Mapping enabled cannot be created because all of the selected \\nvolumes have the Data Direct Mapped attribute.\\nSelect at least one volume whose attribute is not Data Direct Mapped.
1645958338	5	5	The operation cannot be performed because the attribute of the specified volume is \\nData Direct Mapped.\\nVerify the attribute of the specified volume.
1645958339	5	5	The operation cannot be performed because the specified pools have volumes with the \\nData Direct Mapped attribute.\\nSpecify different pools or delete volumes with the Data Direct Mapped attribute, \\nand then retry the operation.
1645958340	5	5	Data Direct Mapping cannot be enabled because the value of Warning Threshold or Depletion \\nThreshold is not set to 100.\\nSet the value of Warning Threshold or Depletion Threshold to 100.
1645958341	5	5	The values of Warning Threshold and Depletion Threshold cannot be changed on the \\nspecified pool with the Date Direct Mapped attribute.\\nDisable Data Direct Mapping, and then retry the operation.
1645958363	5	5	The tiering policy name contains characters that are not valid.\\nEnter a tiering policy name without using symbols ( ; * ? " < > | ) and placing spaces \\nat the start and end of the name.
1645958394	5	5	The specified volume is currently used by global-active device.\\nRelease the global-active device setting, and then retry the operation. If this problem \\npersists, contact the HSSC.
1645958395	5	7	Quick Format cannot be performed because the selected parity groups contain pool volumes.\\nSelect Normal Format.
1645958425	5	5	The interruption process cannot be done because the formatting was completed.\\nClick [OK].
1645958457	5	5	The following cannot be set for the specified pool, because it is not a Dynamic Provisioning \\npool 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 TI pairs when depletion threshold is exceeded\\nVerify the requirements to set the following:\\n- Protect V-VOLs when I/O fails to Blocked Pool VOL\\n- Protect V-VOLs when I/O fails to Full Pool\\nIf Yes is selected for "Suspend TI pairs when depletion threshold is exceeded", verify \\nthat the following items are not set:\\n- Thin Image for Pool Type\\n- Data Direct Mapping\\n- Multi-Tier Pool
1645958458	5	5	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\\nVerify the requirements to set the following:\\n- Protect V-VOLs when I/O fails to Blocked Pool VOL\\n- Protect V-VOLs when I/O fails to Full Pool
1645959262	5	5	The specified volume cannot be set as a pool volume because the RAID level is not \\nsupported.\\nVerify the requirements for the pool volume.
1645959267	5	5	Page Reservation cannot be enabled for some DP-VOLs.\\nTo enable Page Reservation, set the ratio of the pool capacity to the total of the \\nused and reserved capacities lower than the depletion threshold.
1645959268	5	5	The setting processing of Page Reservation has not been performed because an error \\noccurred during the processing.\\nVerify the settings of Page Reservation. To enable Page Reservation, set the ratio \\nof the pool capacity to the total of the used and reserved capacities lower than \\nthe depletion threshold.
1645959269	5	5	Full Allocation cannot be enabled for the specified DP-VOL because the pool is in \\nshrinking operation.\\nWait until the shrinking operation is complete, and then retry the operation.
1645959270	5	5	Full Allocation cannot be enabled for the specified DP-VOL because the emulation \\ntype is not supported.\\nVerify the emulation type.
1645959294	5	0	The operation cannot be performed because the specified LDEV contains a journal volume.\\nDelete all pairs belonging to the journal volume, delete the journal, and then retry \\nthe operation.
1645959295	5	0	The operation cannot be performed because the specified LDEV contains a pool volume \\nof Thin Image.\\nDelete all pairs belonging to the pool volume of Thin Image, delete the pool, and \\nthen retry the operation.
1645959296	5	0	The operation cannot be performed because a DP-VOL that is not blocked is included \\nin the DP-VOLs associated with the pool to which the pool volume in the specified \\nLDEV belongs.\\nBlock all of the DP-VOLs associated with the pool to which the pool volume belongs.
1645959300	1	6	The specified operation cannot be performed because parity group formatting has not \\nbeen performed on the target parity groups.\\nPerform parity group formatting on the target parity groups.
1645959301	5	5	The operation cannot be performed because the installed firmware does not support \\nactive flash.\\nUpdate the firmware to a version that supports active flash.
1645959302	5	5	Active flash cannot be enabled because the pool volume does not contain an LDEV whose \\ndrive type is SSD.\\nContain at least one LDEV whose drive type is SSD as a pool volume in the pool.
1645959324	5	5	The specified LDEVs cannot be deleted from the DT (Active Flash) pool that requires \\nto contain at least one LDEV as a pool volume whose drive type is SSD.\\nLeave at least one LDEV whose drive type is SSD in the pool.
1645959325	1	6	Quick Format cannot be performed because the specified volumes contain volumes that \\nbelong to parity groups with accelerated compression enabled.\\nPerform Normal Format for the volumes that belong to parity groups with accelerated \\ncompression enabled.
1645959389	5	5	The specified LDEV cannot be operated because LUN paths are set to host groups on \\nwhich Host Mode Option 97 is enabled.\\nDisable Host Mode Option 97 on the host groups from which the LUN path is set to \\nthe specified LDEV, or delete the LUN path to the specified LDEV from the host groups \\non which Host Mode Option 97 is enabled.
1645959390	5	5	LDEVs that belong to a parity group with accelerated compression enabled cannot be \\nadded because the specified pool contains DP-VOLs with Page Allocation enabled.\\nSpecify LDEVs that belong to a parity group with accelerated compression disabled.
1645959391	5	5	No pool can be created or expanded because the specified LDEVs belong to a parity \\ngroup that is used by a different pool and is in accelerated compression.\\nPerform one of the following actions:\\n- Specify LDEVs that belong to a parity group that is used by no pool and is in accelerated \\ncompression.\\n- Specify LDEVs that belong to a parity group with accelerated compression disabled.
1645959392	5	5	Page Allocation cannot be enabled because a pool to which the specified DP-VOLs belong \\ncontains pool volumes with accelerated compression enabled.\\nDelete pool volumes with accelerated compression enabled, and then retry the operation.
1645960192	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
1645961153	5	5	The operation cannot be performed, because deduplication system data volumes are \\nspecified.\\nSpecify volumes that are not deduplication system data volumes.
1645961189	5	5	The operation cannot be performed, because deduplication system data volumes are \\nallocated to the specified pools.\\nRelease the allocations of the deduplication system data volumes to the specified \\npools, and then retry the operation.
1645961376	5	5	The LDEV cannot be formatted, because the specified deduplication system data volume \\nis not blocked.\\nBlock the deduplication system data volume, and then retry the operation.
1645961377	5	5	Multiple deduplication system data volumes cannot be formatted at the same time.\\nPerform the operation for deduplication system data volumes one by one.
1645961378	5	5	LDEV formatting cannot be performed for the specified DP-VOLs whose capacity saving \\nsetting is enabled, because the deduplication system data volumes for the pools with \\nwhich the specified DP-VOLs are associated are blocked.\\nBlock DP-VOLs, and then retry the operation.
1645961379	5	5	The LDEVs cannot be formatted, because both deduplication system data volumes and \\nLDEVs that are not deduplication system data volumes are specified.\\nVerify the specified LDEVs.
1645961401	5	5	LDEV formatting cannot be performed for the specified DP-VOLs whose capacity saving \\nsetting is Deduplication and Compression, because the deduplication system data volumes \\nfor the pools with which the specified DP-VOLs are associated are blocked.\\nRestore the deduplication system data volume, and then retry the operation.
1645961402	5	5	The specified LDEVs cannot be formatted, because the capacity saving status of at \\nleast one LDEV is "Failed".\\nFor DP-VOLs whose capacity saving status is Deleting Volume:\\nWait until the DP-VOL deletion is complete.\\nFor DP-VOLs whose capacity saving status is Failed:\\nIf a deduplication system data volume is associated with the pool of the selected \\nDP-VOLs, take the following actions.\\n(1) Back up the data of all DP-VOLs that are associated with the pool and for which \\nDeduplication Data shows Enabled.\\n(2) Block the deduplication system data volume and all DP-VOLs for which Deduplication \\nData shows Enabled and both of which are associated with the same pool.\\n(3) Format the deduplication system data volume.\\n(4) Format all DP-VOLs that are associated with the pool and for which Deduplication \\nData shows Enabled.\\n(5) Restore the backup data.\\nIf a deduplication system data volume is not associated with the pool, contact the HSSC.
1645961403	5	5	The operation cannot be performed, because DP-VOLs whose capacity saving status is \\nnot Disabled are selected.\\nDisable the capacity saving setting for the selected DP-VOLs. Verify that the capacity \\nsaving status is Disabled, and then retry the operation.
1645961404	5	5	The LDEVs cannot be shredded, because deduplication system data volumes are specified.\\nSelect different LDEVs.
1645961405	5	5	Zero pages cannot be reclaimed, because deduplication system data volumes are specified.\\nSelect different LDEVs.
1645961407	5	5	Full Allocation cannot be enabled, because deduplication system data volumes are \\nspecified.\\nSelect different LDEVs.
1645962115	5	2	The selected deduplication system data volume cannot be formatted, because some DP-VOLs \\nthat are associated with the pool and for which Deduplication Data shows Enabled \\nare not blocked.\\nBlock all of the following DP-VOLs associated with the same pool, and then retry \\nthe operation:\\n- The deduplication system data volume\\n- All DP-VOLs for which Deduplication Data shows Enabled
1645962116	5	2	Shared memory is being initialized.\\nWait for a while, and then retry the operation. If the problem persists, contact the HSSC.
1645962117	5	2	The selected deduplication system data volume cannot be formatted.\\nDP-VOLs that are associated with the pool of the selected deduplication system data \\nvolume and for which Deduplication Data shows Enabled are used in one of the following pairs.\\n- ShadowImage pairs\\n- Thin Image pairs\\n- Volume Migration pairs\\n- TrueCopy pairs\\n- Universal Replicator pairs\\n- Global-active device pairs\\nDelete the following pairs if they use the DP-VOLs, and then retry the operation:\\n- ShadowImage pairs\\n- Thin Image pairs\\n- Volume Migration pairs\\n- TrueCopy pairs\\n- Universal Replicator pairs\\n- Global-active device pairs
1645962118	5	5	The multi-tier pool setting cannot be enabled for a Dynamic Provisioning pool with \\nwhich a deduplication system data volume is associated.\\nSelect a different pool.
1645962145	5	5	The operation cannot be performed, because a deduplication system data volume is \\nallocated to the specified pool.\\nDeallocate the deduplication system data volume, and then retry the operation.
1645962146	5	5	The operation cannot be performed, because the selected pool is associated with DP-VOLs \\nwhose capacity saving status is not Disabled.\\nDisable the capacity saving setting for all DP-VOLs associated with the selected \\npool. Verify that the capacity saving status is Disabled, and then retry the operation.
1645962275	5	5	The specified LDEVs cannot be restored, because the LDEVs are being deleted.\\nSelect different LDEVs.
1645962276	5	5	The selected LDEVs cannot be expanded, because they are being deleted.\\nSelect different LDEVs.
1645962301	5	5	The pool edit operation cannot be performed due to one of the following reasons.\\n- Enable is selected for Multi-Tier Pool for a Dynamic Provisioning pool that contains \\nThin Image pairs.\\n- Enable is selected for Data Direct Mapping for a Dynamic Provisioning pool that \\ncontains Thin Image pairs.\\nDelete the Thin Image pairs in the specified Dynamic Provisioning pools, and then \\nretry the operation.
1645962302	5	5	Yes cannot be selected for Suspend TI pairs when depletion threshold is exceeded, \\nbecause the used capacity of the specified Dynamic Provisioning pools exceeds the \\ndepletion threshold.\\nPerform either of the following actions, and then retry the operation.\\n- Add pool volumes to expand the pool capacity.\\n- Reclaim zero pages for DP-VOLs associated with the pool to reduce the used capacity \\nof the pool.
1645962304	5	5	The operation cannot be performed, because Thin Image pairs exist in the pool to \\nwhich the selected pool volumes or external volumes belong.\\nDelete the Thin Image pairs in the pool to which the selected pool volumes or external \\nvolumes belong, and then retry the operation.
1645962305	5	5	The operation cannot be performed, because Thin Image pairs and DP-VOLs whose LDEV \\nstatus is Normal exist in the pool to which the selected pool volumes or external \\nvolumes belong.\\nDelete the Thin Image pairs and block the DP-VOLs in the pool to which the selected \\npool volumes or external volumes belong, and then retry the operation.
1645962306	5	5	The operation cannot be performed, because Thin Image pairs exist in the selected \\nDynamic Provisioning pool.\\nDelete the Thin Image pairs, and then retry the operation.
1645962307	5	5	The operation cannot be performed, because one of the following settings is specified \\nfor a pool for which Yes is selected for "Suspend TI pairs when depletion threshold \\nis exceeded":\\n- Enable is selected for Multi-Tier Pool.\\n- Enable is selected for Data Direct Mapping.\\nTo apply the following settings, select No for "Suspend TI pairs when depletion threshold \\nis exceeded", and then retry the operation:\\n- Enable is selected for Multi-Tier Pool.\\n- Enable is selected for Data Direct Mapping.
1649971366	5	6	The specified WWN is already being used.\\nCorrect the specified contents, and request the setting of the configuration information again.
1649973261	5	6	This port is not properly equipped.\\nRetry the same operation. If nothing changes, please call the HSSC.
1650000969	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650001003	5	3	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650002057	5	3	A connection error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650030761	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650090340	5	2	The WWN should be input with hex digits (0-9 and A-F) and 16 characters.\\nCorrect the specified content, and retry.
1650090371	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650090374	1	2	An error occurred during Storage Navigator processing.\\nRetry the same operation. If the same error occurs, please call the HSSC.
1650090628	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650091302	5	6	The target WWN is not registered.\\nCheck the specified content, and retry.
1650091303	5	6	The specified SPM group is not registered.\\nCheck the specified content, and retry.
1650091305	5	6	The specified SPM group is already registered.\\nCheck the specified content, and retry.
1650091306	5	6	The target port(s) does not equip the monitored WWN(s).\\nCheck the specified content, and retry.
1650091307	5	6	The target WWN is already registered in the port.\\nCheck the specified content, and retry.
1650091308	5	6	The specified Name is already used.\\nCheck the specified content, and retry.
1650091309	5	6	The specified Name is already used.\\nCheck the specified content, and retry.
1650091310	5	6	The number of WWN(s) that is monitored exceeds the maximum in the port.\\nCheck the specified content, and retry.
1650091332	5	6	The number of WWN(s) that is monitored exceeds the maximum.\\nCheck the specified content, and retry.
1650091333	5	6	The number of the WWNs exceeds the maximum number that can be registered on an SPM group.\\nCheck the specified content, and retry.
1650091334	5	6	The specified WWN is registered on a SPM group.\\nCheck the specified content, and retry.
1650091335	5	6	The specified WWN is registered on a SPM group.\\nCheck the specified content, and retry.
1650091336	5	6	The target WWNs have different attributes.\\nCheck the specified content, and retry.
1650092266	1	6	This function is not available.Performance Monitor is required.\\nInstall the necessary program product.
1650120131	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650120164	1	2	An error occurred during Storage Navigator processing.\\nRestart the SVP, and then retry the operation. If this problem persists, contact the HSSC.
1650120195	1	2	A file open error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650120196	1	2	A file access error has occurred.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650120230	1	2	An error occurred during Storage Navigator processing.\\nIf the same error occurs despite retrying, please call the HSSC.
1650120286	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650120287	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650150915	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650153836	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650179715	1	2	The storage system status is invalid.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1650188401	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1650188402	1	2	The storage system status is invalid.\\nRetry the same operation several times. If the same error occurs, please call the HSSC.
1650188580	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1707348930	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1707349605	5	6	The specified SPM group is not registered.\\nCheck the specified content, and retry.
1707349673	1	6	The number of the SPM groups exceeds the maximum number that can be registered.\\nCheck the specified content, and retry.
1707378466	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1718365580	1	2	This function cannot be used by the storage partition administrator.\\nSelect another window. If you want to set this function, please contact the storage \\nadministrator.
1718365612	5	5	The Assign Remote Command Devices operation cannot be performed due to a temporary \\npath failure.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
1718420296	5	0	Too many requests.\\nReduce the number of requests to be processed at one time, and then retry the operation.
1718420297	5	0	Invalid parameter (LDEV ID).\\nVerify the specified LDEV ID.
1718420298	5	0	The parameter (Journal ID) is not valid or the specified journal is not registered.\\nVerify whether;\\n- the specified journal ID is correct, and\\n- the specified journal is registered. 
1718420299	1	0	The command was rejected by the storage system because the command is unknown.\\nIf this problem persists, contact the HSSC.
1718420300	5	0	No more remote storage systems can be registered.\\nReduce the number of registered remote storage systems, and then retry the operation.
1718420322	5	0	Invalid parameter (path group ID).\\nCheck the specified path group ID.
1718420323	5	0	The specified operation failed due to the mirror status of the journal.\\nRefresh the window, and check the mirror status of the journal.
1718420324	5	0	Invalid parameter (number of initial copy activities).\\nCheck the specified number of initial copy activities.
1718420325	5	0	The specified volume does not exist or is unusable.\\nCheck the status of the specified volume.
1718420326	1	0	Pinned slot(s) exists.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1718420327	1	0	The specified volume is blocked.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1718420328	1	0	The cache or the shared memory is in an abnormal state.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1718420331	5	0	The specified volume is already used by another program product.\\nUse the program product to check the status of the specified volume.
1718420356	5	0	The specified CLPR ID is invalid.\\nVerify the specified CLPR ID.
1718420357	5	0	The specified cache value for master journal is invalid.  \\nCheck the specified cache value for master journal.
1718420358	5	0	The specified cache value for restore journal groups is invalid.  \\nCheck the specified cache value for restore journal.
1718420359	5	0	The specified threshold for ending creation of asynchronous journal is invalid.\\nCheck the threshold for ending creation of asynchronous journal.
1718420360	5	0	The specified threshold for ending creation synchronous journal is invalid.\\nCheck the threshold for ending creation of synchronous journal.
1718420361	5	0	The specified threshold for starting creation of asynchronous journal is invalid.\\nCheck the threshold for ending creation of synchronous journal.
1718420362	5	0	The specified threshold for starting creation synchronous journal is invalid.\\nCheck the threshold for starting creation of synchronous journal.
1718420384	5	0	The threshold for starting creation of synchronous journal must be larger than the \\nthreshold for starting creation of asynchronous journal.\\nEnsure that the threshold for starting creation of synchronous journal is larger \\nthan the threshold for starting creation of asynchronous journal.
1718420385	5	0	The threshold for starting creation of asynchronous journal must be larger than the \\nthreshold for ending creation of asynchronous journal.\\nEnsure that the threshold for starting creation of asynchronous journal is larger \\nthan the threshold for ending creation of asynchronous journal.
1718420386	5	0	The threshold for starting creation of synchronous journal must be larger than the \\nthreshold for ending creation of synchronous journal.\\nEnsure that the threshold for starting creation of synchronous journal is larger \\nthan the threshold for ending creation of synchronous journal.
1718420387	5	0	The total cache capacity is incorrect.\\nVerify the cache capacity of the local and remote storage systems.
1718420388	5	0	The operation is impossible because the storage system is being powered on.\\nWait until the storage system is ready.
1718420389	5	0	No more journal volumes can be registered, or too many volumes are selected.\\nVerify the number of journal volumes in the specified journal and the number of the \\nselected volumes.
1718420391	5	0	The specified journal cannot be deleted because a data volume exists.\\nVerify the status of the specified journal.
1718420392	5	0	No more path group IDs can be registered.\\nCheck the number of registered path group IDs.
1718420393	5	0	The specified volume is already used as a journal volume or a data volume.\\nSpecify a different volume.
1718420481	5	0	Too many requests.\\nReduce the number of requests to be processed at one time, and then retry the operation.
1718420482	5	0	Invalid parameter (LDEV ID).\\nVerify the specified LDEV ID.
1718420483	5	0	The parameter (Journal ID) is not valid or the specified journal is not registered.\\nVerify whether;\\n- the specified journal ID is correct, and\\n- the specified journal is registered. 
1718420484	5	0	Invalid parameter (Mirror ID).\\nCheck the specified mirror ID.
1718420485	5	0	Invalid parameter (Journal Control).\\nCheck the specified JNL Control parameter.
1718420486	5	0	Invalid parameter (Suspend Condition - Journal Full).\\nVerify the specified suspend condition parameter.
1718420508	5	0	Invalid parameter (Suspend Condition - Master Journal Failure).\\nVerify the specified suspend condition parameter.
1718420509	5	0	Invalid parameter (Suspend Condition - Restore Journal Failure).\\nVerify the specified suspend condition parameter.
1718420510	5	4	The pair status has not changed yet. \\nThe current configuration of the storage systems and the current status of lines \\nconnecting the storage systems may not satisfy the operating conditions. Check the \\nconfiguration of the storage systems and the status of lines connecting the storage \\nsystems, then check whether the status of the Remote Copy pair is changed.
1718420511	5	6	The storage system is busy.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
1718420513	5	0	The specified serial number is incorrect.\\nCheck the specified serial number.
1718420516	5	0	The specified volume does not exist or is unusable.\\nCheck the status of the specified volume.
1718420541	5	0	The specified consistency group is already used.\\nVerify the consistency group status on the Universal Replicator window of the local \\nand remote storage systems.
1718420542	5	0	The specified master journal is not registered.\\nCheck the status of the specified master journal.
1718420543	5	0	The pair cannot be registered because the volume specified as the primary volume \\nis already used as a journal volume.\\nVerify the status of the volume specified as the primary volume.
1718420544	5	0	The specified primary volume is not registered in the specified journal.\\nVerify the data volumes in the specified master journal.
1718420545	5	0	The specified master journal is not registered.\\nCheck the status of the specified master journal
1718420546	5	0	The emulation type of the volume specified as the primary volume is invalid due to \\none 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\\nVerify the emulation type of the volume specified as the primary volume.
1718420547	5	0	The specified mirror ID differs from the registered mirror ID.\\nCheck the specified mirror ID.
1718420548	5	0	A pair cannot be created because the selected mirror ID of the master journal is \\nalready used by a mirror of a different restore journal.\\nVerify the journals and mirror ID, and then retry the operation.
1718420570	1	0	The SLPR number of the specified data volume does not match the SLPR number of the \\njournal volume in the specified journal.\\nCheck the SLPR number of the specified data volume and the journal volume in the journal.
1718420571	5	0	The specified primary volume is already registered.\\nVerify the status of the specified primary volume.
1718420572	5	0	No more pairs can be registered in the specified master journal.\\nCheck the number of pairs in the specified master journal.
1718420573	5	0	The volume specified as the primary volume is already registered in a different journal.\\nVerify the journal in which the volume specified as the primary volume is registered.
1718420574	5	0	The specified primary volume cannot be deleted because the volume is already registered \\nin a different journal.\\nVerify the journal in which the specified primary volume is registered.
1718420577	5	0	Universal Replicator is not installed on the local storage system.\\nInstall Universal Replicator on the local storage system, and then retry the operation.
1718420578	1	0	The cache or the shared memory is in an abnormal state.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1718420579	1	0	The cache or the shared memory is in an abnormal state.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
1718421252	5	0	The serial number or the model of the remote storage system is invalid.\\nVerify the serial numbers and the models of the specified remote storage system and \\nthe already registered remote storage system, and then enter the correct values. \\nIf the specified values are correct, verify the cable connection of the remote storage \\nsystem. If this problem persists, contact the HSSC.
1718421253	5	0	The pair status is incorrect.\\nRefresh the window, and then verify the pair status.
1718421254	1	4	An internal error occurred. \\nThe pair status might be different between the local and remote storage systems. \\nWait for a while, and then retry the operation. If the pair status does not match \\nbetween the local and remote storage systems, contact the HSSC.
1718421257	5	4	Paths or pairs cannot be created because Universal Replicator is not installed on \\nthe remote storage system.\\nInstall Universal Replicator on the remote storage system.
1718421258	5	4	The operation cannot be performed because the specified volumes are in either of \\nthe 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.\\nVerify the following for the specified primary and secondary volumes:\\n- The capacities of primary volume and secondary volume are the same.\\n- The current firmware version supports the specified capacity of the secondary volume.
1718422403	5	0	Journal volumes cannot be registered because the program product license of Universal \\nReplicator is not installed.\\nInstall the program product license of Universal Replicator.
1718422408	5	0	The specified restore journal is not registered.\\nCheck the status of the specified restore journal.
1718422430	1	0	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 \\nDelta resync volume pairs is already used by the ordinary (not Delta resync) volume pairs.\\n\\nCheck the mirror status and the mirror ID of the specified restore journal.
1718422431	5	0	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 Utility.\\n- The VMA setting differs between the primary volume and the secondary volume.\\nPerform either of the following operations on the Data Retention Utility window:\\n- If S-VOL Disable is set to the volume, specify a different volume, and then retry \\nthe operation.\\n- If the VMA setting differs between the primary volume and the secondary volume, \\napply the same VMA setting to them.
1718422435	5	0	The specified restore journal is not registered.\\nCheck the specified restore journal.
1718422436	5	0	The pair cannot be registered because the volume specified as the secondary volume \\nis already used as a journal volume.\\nVerify the status of the volume specified as the secondary volume.
1718422437	5	0	The specified secondary volume is not registered in the specified journal.\\nVerify the data volumes in the specified restore journal.
1718422438	5	0	The specified restore journal is not registered.\\nCheck the specified restore journal.
1718422439	5	0	The emulation type of the volume specified as the secondary volume or of the restore \\njournal 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 \\nis invalid.\\n- The emulation types of the primary and secondary volumes do not match.\\n\\nVerify the emulation type of the volume specified as the secondary volume or of the \\nrestore journal volume.
1718422461	5	0	The specified secondary volume is already registered.\\nVerify the status of the specified secondary volume.
1718422462	5	0	No more pairs can be registered in the specified restore journal.\\nCheck the number of pairs in the specified restore journal.
1718422463	5	0	The specified secondary volume is already registered in a different journal.\\nVerify the journal in which the specified secondary volume is registered.
1718422464	5	0	The specified secondary volume cannot be deleted because the volume is already registered \\nin a different journal.\\nVerify the journal in which the specified secondary volume is registered.
1718422465	1	4	An internal error occurred. \\nIf this problem persists, contact the HSSC.
1718422466	5	0	No more pairs can be registered because the number of pairs will exceed the maximum.\\nCheck the number of pairs.
1718422467	5	0	The command cannot be executed because the command that should be issued to the secondary \\nvolume is issued to the primary volume.\\nCheck the command parameters.
1718422468	5	0	The command cannot be executed because the command that should be issued to the primary \\nvolume is issued to the secondary volume.\\nCheck the command parameters.
1718422469	5	0	The specified primary volume is already paired with a different volume.\\nIf the status of the primary volume is Simplex (SMPL), delete the pair by selecting \\n[Force] for the Delete Mode, and then retry the operation.
1718422470	5	0	The specified secondary volume is already paired with a different volume.\\nIf the status of the secondary volume is Simplex (SMPL), delete the pair by selecting \\n[Force] for the Delete Mode, and then retry the operation.
1718422492	5	0	The specified primary volume is not paired with any volumes.\\nVerify the status of the specified primary volume.
1718422493	5	0	The specified secondary volume is not paired with any volumes.\\nVerify the status of the specified secondary volume.
1718422494	5	0	The specified volume cannot be used as a journal volume.\\nVerify that the specified volume is in any of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in correction access condition.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.
1718422495	5	0	The specified operation cannot be performed on the data volume pair.\\nCheck the status of the specified pair.
1718422496	5	0	The specified operation cannot be performed because the status of the data volume \\npair is changing.\\nCheck the status of the specified pair.
1718422497	1	4	An internal error occurred. \\nIf this problem persists, contact the HSSC.
1718423176	5	0	The specified volume is used as a command device.\\nCheck the configuration of the specified volume.
1718423179	5	0	A path is defined to the specified volume.\\nCheck the configuration of the specified volume.
1718423180	5	0	The volume specified as the secondary volume is used as a command device.\\nVerify the configuration of the volume specified as the secondary volume.
1718423181	5	0	The volume specified as the secondary volume is an On-Demand (Just in Time)volume.\\nVerify the configuration of the volume specified as the secondary volume.
1718423182	5	0	The volume specified as the primary volume is used as a command device.\\nVerify the configuration of the volume specified as the primary volume.
1718423241	5	0	The volume specified as the primary volume is used by TrueCopy. The operation cannot \\nbe performed because the status of the TrueCopy pair is not valid.\\nVerify the status of the volume specified as the primary volume from the TrueCopy \\nwindow. If the primary volume is in PSUS, PSUE, or Suspend status, restore the volume, \\nand then retry the operation. If the primary volume is in COPY or Pending status, \\nwait until the status of the volume changes to PAIR or Duplex, and then retry the \\noperation.
1718423244	1	0	The operation of Create Pairs or Resync Pairs cannot be performed because data remains \\nin the journal cache for the restore journal.\\nIf this problem persists, contact the HSSC.
1718423270	5	0	The parameter related to the inflow cannot be changed because the specified journal \\nis other than the master journal.\\nCheck the attribute of the specified journal.
1718423271	5	0	The parameter related to the inflow cannot be changed, because the status of the \\nspecified journal is neither "Initial" nor "Stopped".\\nVerify the status of the specified journal.
1718423272	5	0	The timer type cannot be changed, because the status of the specified journal is \\nnot "Initial". \\nVerify the status of the specified journal.
1718423273	5	0	The specified volume cannot be registered as a journal volume because the CLPR number \\nof the specified volume is different from the CLPR number of the journal volume that \\nhas already been registered.\\nCheck the CLPR number of the registered journal volume, and specify the volume that \\nhas the same CLPR number.
1718423274	5	0	The operation cannot be performed because the CLPR number of the volume specified \\nas the primary volume is different from the CLPR number of the journal volume in \\nthe specified master journal.\\nCheck the CLPR number of the journal volume in the specified master journal, and \\nthen select a volume that has the same CLPR number.
1718423275	5	0	The operation cannot be performed because the CLPR number of the volume specified \\nas the secondary volume is different from the CLPR number of the journal volume in \\nthe specified restore journal.\\nCheck the CLPR number of the journal volume in the specified master journal, and \\nthen select a volume that has the same CLPR number.
1718423299	5	0	The specified volume cannot be used as a journal volume because the specified volume \\nis an external volume.\\nCheck the specified volume and specify a non-external volume.
1718423303	5	0	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.\\nVerify whether the IO suppression mode of the specified secondary volume is enabled \\nfrom the Universal Volume Manager window. If the IO suppression mode is disabled, \\ntake a note of the DKCMAIN firmware version of the remote storage system, and then \\ncontact the HSSC.
1718423304	5	0	The Create Pairs operation cannot be performed because VMA of Data Retention Utility \\nis set on the volume specified as the secondary volume.\\nVerify the settings of the volume specified as the secondary volume from the Data \\nRetention Utility window.
1718423332	5	0	The operation cannot be performed because the volume specified as the secondary volume \\napplies to any of the following:\\n- A secondary volume of ShadowImage.\\n- A primary volume of ShadowImage in the Swap or Reverse Copy status.\\n- A primary volume of ShadowImage used in conjunction with TrueCopy.\\n- A Dynamic Provisioning volume used as a primary volume of ShadowImage.\\n- A Dynamic Provisioning volume and a source volume of Volume Migration.\\n- A Dynamic Provisioning volume used as a primary volume of Thin Image.\\nExtract a possible combination of program products from the program products combinations \\ndescribed in the message, and then verify the status of the volume specified as the \\nsecondary volume from the program product window.\\nTo use the Dynamic Provisioning volume as the secondary volume, release the attribute \\nof a program product combined with the Dynamic Provisioning volume, and then retry \\nthe operation.
1718423333	5	0	The specified volume cannot be used as a primary volume because it is being used \\nby any of the following program products:\\n- ShadowImage\\n- TrueCopy\\n- Volume Migration\\n\\nRelease the setting of the different program product that uses the specified volume \\nand then retry the operation, or select a different volume.
1718423334	5	0	The pair operation cannot be performed because the volume specified as the secondary \\nvolume is being used by one of the following program products:\\n- ShadowImage\\n- Thin Image\\n- TrueCopy\\n- Volume Migration\\nSelect a different volume, or delete the pair whose volume is used by a different \\nprogram product, and then retry the operation.
1718424291	5	0	The storage system is in internal process.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
1718424297	5	0	The specified primary volume is used by TrueCopy.\\nSelect a mirror ID other than zero (0), and then retry the operation.
1718424298	5	0	A different mirror ID has already been registered in the specified master journal. \\nSpecify the same mirror ID, because only one mirror ID can be registered in one journal.\\nSpecify the same mirror ID as the registered mirror ID, then retry the operation.
1718424388	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume applies to either of the following:\\n- A primary volume of Thin Image in Reverse Copy status.\\n- A secondary volume of Thin Image.\\n\\nVerify the status of the volume specified as the primary volume from the Local Replication window.
1718424389	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume is a virtual volume of Thin Image.\\nSelect a different volume, and then retry the operation.
1718424390	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume is a pool volume.\\nVerify the status of the volume specified as the primary volume.
1718424414	1	0	The pair option of the primary volume was updated, but that of the secondary volume \\ncannot be updated. The firmware of the remote storage system might not support the \\nchange pair option function, or a communication error between the local and remote \\nstorage systems might have occurred.\\nTake a note of the DKCMAIN firmware of the remote storage system, and then contact \\nthe HSSC to verify that the firmware supports the change pair option function. If \\nthe firmware supports the function, verify the cable connection of the local storage \\nsystem and the remote storage system, and then retry the operation. If this problem \\npersists, contact the HSSC.
1718425096	5	0	The Create Pairs operation cannot be performed because the Universal Replicator function \\nof the remote storage system does not support external volumes.\\nTake a note of the DKCMAIN firmware version of the remote storage system, and then \\ncontact the HSSC to verify whether the Universal Replicator function supports external volumes.
1718425097	5	0	The Create Pairs operation failed because the Universal Replicator function of the \\nRemote Storage System does not support VMA of Data Retention Utility.\\nTake a note of the DKCMAIN firmware version of the remote storage system, and then \\ncontact the HSSC to verify whether the Universal Replicator function supports VMA \\nof Data Retention Utility.
1718425098	5	0	The operation cannot be performed because the volume capacity of the remote storage \\nsystem exceeds the licensed capacity of Data Retention Utility.\\nVerify the licensed capacity of Data Retention Utility for the remote storage system. \\nTo perform the specified operation, purchase a license key that allows you to use \\na capacity larger than the current capacity.
1718425099	5	0	The specified operation failed due to the attribute or the mirror status in the journal.\\nCheck the attribute and the mirror status of the journal.
1718425100	5	0	The operation cannot be performed.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
1718425104	5	0	The Create Pairs operation cannot be performed because the IO suppression mode of \\nthe volume specified as the primary volume is enabled.\\nDisable the IO suppression mode of the volume specified as the primary volume from \\nthe Universal Volume Manager window.
1718425127	5	0	The Create Pairs operation cannot be performed. The combination of the specified \\nprimary volume and the mirror ID is the same as the combination specified from a \\ndifferent local storage system. \\nVerify the mirror ID assigned to the specified primary volume from the remote storage \\nsystem, assign a mirror ID that is not used, and then retry the operation.
1718425189	5	0	The capacity of the specified volume is too small.\\nVerify the capacity of the volume, and specify a volume with larger capacity.
1718425251	5	0	The operation to add journal volumes failed due to the mirror status of the specified journal.\\nVerify the status of the mirrors in the specified journal.
1718425282	1	0	A journal volume cannot be added because the capacity of shared memory is insufficient.\\nSee the manual to verify the condition for this operation.
1718425283	5	0	The Create Pairs operation or the Resync Pairs operation cannot be performed because \\nthe timer type of the master journal is different from that of the restore journal.\\nCheck the timer type of the master and the restore journal.
1718425284	5	0	The specified volumes or the volumes in the specified journal were deleted, but the \\nvolumes could not be blocked.\\nBlock the volumes that could not be blocked. If this operation cannot be performed, \\ncontact the HSSC.
1718425285	5	0	The specified volume could not be registered because the volume failed to recover \\nfrom blockade.\\nIf the problem persists despite retrying, execute Format LDEVs.
1718425286	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume is being shredded.\\nWait until the shredding of the specified volume is complete, and then retry the \\noperation.
1718425287	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nsecondary volume is being shredded.\\nWait until the shredding of the specified volume is complete, and then retry the \\noperation.
1718425288	5	0	The specified volume cannot be registered as a journal volume because the volume \\nis being shredded by Data Retention Utility.\\nWait until the shredding is complete, and then retry the operation.
1718425375	5	0	The Create Pairs or the Resync Pairs operation cannot be performed because the journal \\nvolumes of the specified master journal are blocked.\\nCheck the journal volumes statuses of the specified master journal.
1718425376	5	0	The Create Pairs or the Resync Pairs operation cannot be performed because the journal \\nvolumes of the specified restore journal are blocked.\\nCheck the journal volumes statuses of the specified restore journal.
1718425377	5	0	The specified operation failed because the storage system was being powered on or \\npowered off.\\nCheck the status of the storage system. Retry the operation after the storage system \\nhas started.
1718425378	5	0	The storage system has accepted the request normally, however the processing requires \\nsome time.\\nRefresh the window. If this message is displayed after:\\n- the setting operation, verify that the setting is reflected.\\n- the operation of changing pair status, verify the status of the primary and secondary \\nvolumes. If the settings are not reflected, retry the operation.\\n- the Create Pairs or Resync Pairs operation, perform the Split Pairs operation for \\nthe pair in the Copy status, and then perform the Resync Pairs operation.
1718425379	5	0	The Create Pairs operation cannot be performed because the specified secondary volume \\nis in LUSE configuration.\\nRelease the LUSE configuration or specify a different volume.
1718425381	5	0	The operation to change the status to the status ready for delta resync cannot be \\nperformed because At-Time Split is set to the specified restore journal.\\nCheck if the At-Time Split is set to the specified restore journal with Business \\nContinuity Manager.
1718426058	5	0	Journals cannot be added to the extended consistency group (EXCTG), because the additional \\nshared memory is not installed.\\nSee the manual to verify the condition for this operation.
1718426059	5	0	Journals cannot be added to the extended consistency group (EXCTG), because the number \\nof storage systems in the EXCTG exceeds the maximum.\\nCheck the number of storage systems in the specified extended consistency group (EXCTG).
1718426060	5	0	Journals cannot be added to the extended consistency group (EXCTG), because the number \\nof journals in the EXCTG exceeds the maximum.\\nCheck the number of journals in the specified extended consistency group (EXCTG).
1718426062	5	0	Journals cannot be added to the extended consistency group (EXCTG) because the specified \\nmirror ID is different from the mirror ID existed in the EXCTG.\\nCheck the mirror ID of the specified extended consistency group (EXCTG).
1718426063	5	0	Journals cannot be deleted from the extended consistency group (EXCTG), because the \\nspecified EXCTG is not registered.\\nCheck the status of the specified extended consistency group (EXCTG).
1718426064	5	0	Journal groups cannot be deleted from the extended consistency group (EXCTG), because \\nthe specified journal group was not registered.\\nVerify the journals in the specified extended consistency group (EXCTG).
1718426065	5	0	The Resync Pairs operation cannot be performed. The restore journal belongs to an \\nextended consistency group (EXCTG), but the local storage system does not support \\nthe EXCTG function.\\nUpdate the firmware of the local storage system to the version that supports the \\nEXCTG function.
1718426066	5	0	The timer type cannot be changed, because the specified journal belongs to an extended \\nconsistency group (EXCTG).\\nRelease the setting of the extended consistency group (EXCTG) in the specified journal, \\nand then retry the operation. 
1718426089	5	0	The specified operation cannot be performed because the firmware exchange is in progress \\nor interrupted on the storage system in the extended consistency group (EXCTG).\\nWait until all of the firmware exchanges are complete, and then retry the operation.
1718426090	5	0	The previously performed update processing of the extended consistency group (EXCTG) \\nis not complete.\\nWait for a while, and then retry the operation.
1718426091	5	0	The command device is specified incorrectly.\\nVerify whether the specified LDEV ID indicates a command device.
1718426308	5	0	The operation cannot be performed because Universal Replicator of the remote storage \\nsystem does not support the delta resync function.\\nTake a note of the DKCMAIN microcode version of the remote storage system, and then \\ncontact the HSSC and ask whether Universal Replicator supports the Delta resync function.
1718426309	5	0	The operation to change the status to Ready for Delta resync cannot be performed. \\nThe specified primary volume should meet the following conditions:\\n- It is a secondary volume of TrueCopy.\\n- The TrueCopy pair is in PAIR status.\\nOn the Replication window and Remote Replication window, verify the status of the \\nspecified primary volume.
1718426310	5	0	The delta resync operation cannot be performed. The specified primary volume should \\nmeet the following conditions:\\n- If it is shared as the primary volume of TrueCopy, the status of the TrueCopy pair is PAIR.\\n- If it is shared as the secondary volume of TrueCopy, the status of the TrueCopy \\npair is SSWS.\\nOn the Remote Replication window or RAID Manager, verify the status of the TrueCopy \\npair that uses the specified primary volume.
1718426311	5	0	The specified operation failed, because the attribute of the journal of the remote \\nstorage system was not "restore".\\nCheck the attribute of the journal of the remote storage system.
1718426312	5	0	The status of the other mirror of the Delta resync did not change.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
1718426313	5	0	The delta resync operation cannot be performed because the specified primary volume \\nis not ready for delta resync.\\nVerify the status of the specified primary volume.
1718426314	5	0	The operation cannot be performed because the status of some mirrors in the master \\nor restore journal is invalid.\\nVerify the status of the mirrors in the specified journal.
1718426336	5	0	The recovery to the status ready for delta resync cannot be made because the specified \\nprimary 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\\nVerify the status of the specified primary volume.
1718426337	5	0	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 \\nwhile 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 \\nwhile specifying the mirror ID used by delta resync pairs.\\n\\nSpecify a different mirror ID, or verify the pair operation for the specified mirror ID.
1718426338	5	0	The specified master journal cannot be used for Delta resync, because it is registered \\nin the extended consistency group (EXCTG).\\nCheck the status of the specified master journal.
1718426339	5	0	The specified restore journal cannot be used for Delta resync, because it is registered \\nin the extended consistency group (EXCTG).\\nCheck the status of the specified restore journal.
1718426340	5	0	The delta resync operation cannot be performed.\\nVerify the status of the secondary volume or the connected communication line. If \\nno abnormality is found in the status, contact the HSSC.
1718426342	5	0	The specified volume cannot be used as a journal volume because the volume is an \\nexternal volume to which the I/O suppression mode is enabled.\\nCheck the I/O suppression mode of the specified volume.
1718426343	5	0	The journal volume cannot be deleted from the specified journal due to the mirror status.\\nVerify the status of the mirrors in the specified journal.
1718426344	5	0	The operation cannot be performed because the specified secondary volume is used \\nby delta resync.\\nVerify the status of the specified secondary volume.
1718426345	5	0	The operation to change the status to Ready for Delta resync cannot be performed \\nbecause the specified secondary volume is used by either of the following program products:\\n- ShadowImage\\n- Thin Image\\nVerify the status of the specified secondary volume from the Local Replication window.
1718427018	5	0	The operation to change the status to Ready for Delta resync cannot be performed. \\nThe 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\\nVerify the status of the specified secondary volume.
1718427019	5	0	The Universal Replicator pair for delta resync cannot be resynchronized due to one \\nof the following reasons.\\n- Updated data for the TrueCopy pair and that for the Universal Replicator pair do \\nnot match.\\n- An I/O is issued from the host to the secondary volume of the Universal Replicator.\\nDelete the pair that is ready for delta resync, and then copy all data of the primary \\nvolume to the secondary volume.
1718427020	5	0	The delta resync operation cannot be performed because the number of Universal Replicator \\npairs and that of Universal Replicator delta resync pairs are different in the restore journal.\\nAs a result, the Universal Replicator delta resync pair that did not share the same \\nvolume with a Universal Replicator pair was automatically deleted.\\nVerify the configuration of the Universal Replicator pairs and the Universal Replicator \\ndelta resync pairs.
1718427021	5	0	The delta resync operation cannot be performed because the secondary volume has been updated.\\nDelete the Ready for Delta resync pair, and then copy all data into the primary volume.
1718427022	5	0	The operation to change the status to Ready for Delta resync cannot be performed \\nbecause the primary volume is not shared by TrueCopy and Universal Replicator.\\nOn the Replication window, verify the status of the volume.
1718427023	5	0	The delta resync operation cannot be performed. The specified secondary volume should \\nmeet 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\\nVerify the status of the specified secondary volume.
1718427025	5	0	The Create Pairs operation or the Resync Pairs operation cannot be performed because \\nthe status of the specified secondary volume is Not Ready.\\nVerify the status of the specified secondary volume.
1718427026	5	0	The Create Pairs operation with Delta specified, or the Resync Pairs operation on \\nthe pair in Ready for Delta resync status cannot be performed.\\nIf this problem persists, contact the HSSC.
1718427055	5	5	The licensed capacity of TrueCopy on the remote storage system is not enough. \\nVerify the licensed capacities of TrueCopy and Universal Replicator. See the TrueCopy \\nUser Guide for the remote storage system for the details of the licensed capacities.
1718427057	5	5	The licensed capacity of Universal Replicator on the remote storage system is not enough.\\nVerify the licensed capacities of Universal Replicator and TrueCopy. See the Universal \\nReplicator User Guide for the remote storage system for the details of the licensed \\ncapacities.
1718427058	5	5	The licensed capacity of TrueCopy on the local storage system is not enough.\\nVerify the licensed capacities of TrueCopy and Universal Replicator. See the TrueCopy \\nUser Guide for the local storage system for the details of the licensed capacities.
1718427081	5	5	The licensed capacity of Universal Replicator on the local storage system is not enough.\\nVerify the licensed capacities of Universal Replicator and TrueCopy. See the Universal \\nReplicator User Guide for the local storage system for the details of the licensed \\ncapacities.
1719343815	5	0	The operation failed, because the specified journal was not registered.\\nCheck if the specified journal is registered.
1719343816	5	0	The operation failed, because the number of journals exceeded the maximum.\\nCheck the number of registered journal.
1719343817	5	0	The operation failed, because more than one LDKC numbers cannot coexist in one journal.\\nCheck if the LDKC number of the journal to be registered and the LDKC number of the \\nspecified volume is the same.
1719343818	5	0	The Create Pairs operation cannot be performed because the LDKC number of the volume \\nspecified as the primary volume is different from the LDKC number of the master journal.\\nSpecify a volume with the same LDKC number as that of the master journal, and then \\nretry the operation.
1719343819	5	0	The Create Pairs operation failed. The LDKC number of the volume specified as the \\nsecondary volume is different from the LDKC number of the specified restore journal.\\nSpecify a volume with the same LDKC number as that of the restore journal, and then \\nretry the operation.
1719343820	1	0	The Create Pairs operation cannot be performed because the capacity of the shared \\nmemory of the local storage system is not enough.\\nVerify the capacity of the shared memory of the local storage system.
1719343821	1	0	The Create Pairs operation cannot be performed because the capacity of the shared \\nmemory of the remote storage system is not enough.\\nVerify the capacity of the shared memory of the remote storage system.
1719343846	5	0	The operation cannot be performed due to any of the following reasons.\\n- The specified volume is not a Dynamic Provisioning volume.\\n- Data Direct Mapping is enabled on the specified volume.\\nVerify the specified volume setting.
1719343847	5	0	The operation failed because the specified volume was a pool volume of Dynamic Provisioning.\\nCheck whether the specified volume is a pool volume of Dynamic Provisioning.
1719343850	5	0	The operation cannot be performed because the volume specified as the secondary volume \\nis a Dynamic Provisioning volume.\\nSpecify a volume other than a Dynamic Provisioning volume, and then retry the operation. 
1719343851	5	0	The operation cannot be performed because the volume specified as the secondary volume \\nis a pool volume of Dynamic Provisioning.\\nSpecify a volume other than a pool volume of Dynamic Provisioning, and then retry \\nthe operation.
1719343852	5	0	The remote storage system does not support the LDEV ID of the specified primary volume.\\nSpecify the LDEV ID that is supported by the remote storage system, and then retry \\nthe operation.
1719343878	5	0	The operation failed because the current firmware version does not support Delta Resync.\\nCheck the connected storage system's firmware version.
1719343879	5	0	The volume specified as the primary volume is used as a pair volume of TrueCopy. \\nThe operation cannot be performed because the program product license of Disaster \\nRecovery Extended is not installed on the local storage system.\\nInstall Disaster Recovery Extended on the local storage system.
1719343880	5	0	The volume specified as the secondary volume is used as a pair volume of TrueCopy. \\nThe operation cannot be performed because the program product license of Disaster \\nRecovery Extended is not installed on the remote storage system.\\nInstall Disaster Recovery Extended on the remote storage system.
1719343882	5	0	Journals cannot be added to the extended consistency group (EXCTG), because the current \\nfirmware version does not support LDKC numbers other than 0.\\nConfirm the LDKC number of the specified extended consistency group.
1719350703	5	0	The status of the specified volume is Simplex or SMPL.\\nVerify that the LDEV ID or LUN ID, and the mirror ID of the specified volume are correct.
1719350765	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nsecondary volume is a system disk.\\nSelect a different volume or release the setting of a system disk for the secondary \\nvolume, and then retry the operation.
1719350788	5	0	The specified operation cannot be performed because LU is specified for the error level.\\nThe specified master journal runs in the 2DC configuration in which TrueCopy is combined. \\nSpecify Mirror for the error level.
1719350789	5	0	The Create Pair operation cannot be performed because (0) is specified for the mirror ID.\\nThe specified master journal runs in the 2DC configuration in which TrueCopy is combined. \\nSpecify other than (0) for the mirror ID, and then retry the operation.
1719350790	5	0	The Create Pairs operation cannot be performed because the specified primary volume \\nis used by TrueCopy.\\nThe specified master journal runs in the 2DC configuration in which TrueCopy is combined. \\nDelete the TrueCopy pair, and then retry the operation, or specify the volume that \\nis not used by TrueCopy.
1719350791	5	0	The Resync Pairs operation cannot be performed because the status of the specified \\nprimary volume is either of the following.\\n- The volume is not used by TrueCopy.\\n- The volume is used by TrueCopy, but the pair status is not PSUS or PSUE.\\n\\nThe master journal of the specified primary volume runs in the 2DC configuration \\nin which TrueCopy is combined. Delete or suspend the TrueCopy pair . 
1719351505	5	4	The operation cannot be performed because the specified secondary volume is used \\nas a volume of Data Migration.\\nVerify the status of the secondary volume from the host or SVP.
1719351533	5	0	A pair cannot be created because the specified secondary volume is a Dynamic Provisioning \\nvolume whose capacity is being changed.\\nCheck the volume capacity after the capacity change of the volume ends, and then \\nplan again a combination of volumes to form a pair.
1719351534	5	0	A pair cannot be created because the volume specified as the primary volume is a \\nDynamic Provisioning volume whose capacity is being changed.\\nCheck the volume capacity after the capacity change of the volume ends, and then \\nplan again a combination of volumes to form a pair.
1719351536	5	0	The pair cannot be released because the specified volume is used as the pair volume \\nof TrueCopy.\\nThe specified volume is being used in the 2DC configuration in which TrueCopy is \\ncombined. Delete the TrueCopy pair, and then retry the operation.
1719351626	5	0	The operation cannot be performed because the volume specified as the secondary volume \\nis a volume of Dynamic Provisioning in zero page reclaiming.\\nWait until the zero page reclamation on the specified volume is complete, and then \\nretry the operation.
1719351632	1	0	The operation cannot be performed because a pool associated with a volume for Dynamic \\nProvisioning specified as the primary volume is being initialized.\\nWait until the initialization processing is complete, and then retry the operation.
1719351633	5	0	The operation cannot be performed because the pool associated with the volume of \\nDynamic Provisioning that is specified as the secondary volume is being initialized.\\nWait until the initialization of the pool is complete, and then retry the operation.
1719351655	5	0	The operation cannot be performed because the consistency group of the specified \\ndata volume is shared with multiple local and remote storage systems, and LU is specified \\nfor Range.\\nSpecify "Mirror" for the [Range], then retry the operation.
1719351656	5	0	The operation cannot be performed because the specified consistency group is shared \\nwith multiple local and remote storage systems.\\nSelect a different consistency group, and then retry the operation.
1719351658	5	0	The operation cannot be performed because the specified journal is shared with multiple \\nlocal and remote storage systems.\\nSelect a different journal, and then retry the operation.
1719351662	5	0	The operation failed, because a remote command device has already been assigned to \\nthe specified mirror.\\nCheck if a remote command device is assigned to the specified mirror.
1719351663	5	0	The operation failed, because the specified mirror was invalid.\\nCheck the status of the specified mirror.
1719351664	1	0	The operation failed, because the specified remote command device was blocked.\\nCheck the status of the specified remote command device.
1719351686	5	0	The operation cannot be performed because the serial numbers of the remote command \\ndevice and the mirror do not match.\\nVerify that the serial number of the external volume that is used as a remote command \\ndevice matches the one of the storage system connected to the mirror.
1719351687	5	0	The operation failed, because the specified journal was not in the configuration \\nof 3DC cascade or 3DC multi target.\\nCheck the status of the specified journal.
1719351688	5	0	The specified remote command device cannot be assigned to a mirror any further.\\nSpecify another remote command device, then retry the operation.
1719351689	5	0	The operation failed, because the number of assignable remote command device to a \\nmirror exceeded the maximum.\\nCheck the number of remote command devices which has been assigned to a mirror.
1719351717	5	0	The operation failed, because a remote command device was not assigned to the specified mirror.\\nCheck if a remote command device was assigned to the specified mirror.
1719351754	5	5	The operation cannot be performed because the remote storage system does not support \\nthe setting operation of remote command devices.\\nContact the HSSC to verify that the firmware version supports the setting operation \\nof remote command devices.
1719352465	5	5	The operation to create a pair of the second mirror cannot be performed because the \\nspecified restore journal applies to either of the following.\\n - A master journal of the first mirror.\\n - A restore journal of the first mirror.\\nVerify the restore journal specified for the second mirror.
1719352466	5	5	The operation cannot be performed because the specified journal is either a master \\njournal or a restore journal.\\nThe following options cannot be changed with master and restore journals.\\n- Data overflow watch.\\n- Use of cache.\\n\\nVerify the attribute of the specified journal.
1719352467	5	5	A journal volume cannot be added to the specified journal in the operation environment \\nof the current storage system.\\nIf this problem persists, contact the HSSC.
1719352468	5	5	The operation failed because the number of mirrors registered in the specified journal \\nexceeded the upper limit.\\nVerify the number of mirrors in the specified journal.
1719352470	5	5	The operation failed because the restore journal specified for the second mirror \\nwas used as the restore journal of the first mirror.\\nVerify the specified restore journal.
1719352492	5	5	The operation cannot be performed because the specified restore journal does not \\nsupport Universal Replicator 3DC.\\nVerify the specified restore journal.
1719352493	5	5	The operation failed because the specified master journal does not support Universal \\nReplicator 3DC.\\nVerify the specified master journal.
1719352494	5	5	The operation cannot be performed because the program product license of Disaster \\nRecovery Extended is not installed on the local storage system.\\nInstall the program product license of Disaster Recovery Extended on the local storage \\nsystem, and then retry the operation.
1719352495	5	5	The operation cannot be performed because the program product license of Disaster \\nRecovery Extended is not installed on the remote storage system.\\nInstall the program product license of Disaster Recovery Extended on the remote storage \\nsystem, and then retry the operation.
1719352496	5	5	The operation failed because the specified primary volume was used by another mirror \\nof the journal and the pair status of the mirror was in transition (COPY/ Suspending/ \\nDeleting/ HOLDING).\\nVerify the status of the pair in the different mirror, wait until the status transition \\nis complete, and then retry the operation.
1719352497	5	5	The Create Pairs operation cannot be performed because the status of a different \\nmirror in the journal to which the volume specified as the secondary volume belongs \\nis not Initial or Stopped.\\nVerify the pair operations, or select a different volume, and then retry the operation.
1719352498	5	5	The pair operation cannot be performed because the specified primary volume applies \\nto one of the following:\\n- Its consistency group is shared by multiple local and remote storage systems.\\n- Being used by TrueCopy.\\n- Being used by Thin Image.\\n- Being used by Volume Migration.\\nRelease the setting of the different program product that uses the specified volume \\nand then retry the operation, or select a different volume.
1719352499	5	5	The pair operation cannot be performed because the specified secondary volume applies \\nto one of the following:\\n- Its consistency group is shared by multiple local and remote storage systems.\\n- Being used by TrueCopy.\\n- Being used by Thin Image.\\n- Being used by Volume Migration.\\nRelease the setting of the different program product that uses the specified volume \\nand then retry the operation, or select a different volume.
1719352501	5	5	The pair operation cannot be performed because the mirror status between the primary \\nand intermediate sites in the 3DC cascading configuration with Universal Replicator \\nis Active.\\nChange the mirror status between the primary and intermediate sites to Stopped, and \\nthen retry the operation.
1719352528	5	5	The operation to create a pair for delta resync cannot be performed because the pair \\nstatus of the specified primary volume is not PAIR.\\nVerify the status of the specified primary volume.
1719352529	5	5	The delta resync operation cannot be performed because the pair status of the specified \\nprimary volume is not appropriate.\\nVerify that the specified primary volume applies to the following:\\n- The volume is a primary volume of a different mirror but the pair status is not \\nPAIR, PSUS, PSUE, or Suspending on the Universal Replicator window or the RAID Manager.\\n- The volume is a secondary volume of a different mirror but the pair status is not \\nSSWS on the RAID Manager.
1720177996	5	5	The specified LDEV belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified LDEV.
1720178023	5	5	The specified operation cannot be done because there is an LDEV that has been set \\nto a different resource group.\\nSpecify LDEVs defined in a same resource group.
1720178029	5	0	The specified port cannot be used because the user has no access right to a resource \\ngroup to which the port belongs.\\nVerify the resources allocation for the user with security administrator role.
1720178030	5	0	The operation cannot be performed because the port belonging to a resource group \\nthat you do not have permission to access is used by the remote path of the local \\nstorage system.\\nVerify the resources allocation for the user with security administrator role.
1720267336	5	5	The specified journal cannot be used.\\nCheck the specified journal.
1720267337	5	5	The specified consistency group cannot be used.\\nCheck the specified consistency group.
1720267488	5	5	The operation failed because the specified capacity of the primary volume is not \\nsupported by the current firmware version.\\nVerify the specified capacity of the primary volume and the current firmware version.
1720267524	5	5	The operation cannot be performed because the storage system is in internal process, \\nor the configuration is being changed by a different operation.\\nWait for a while, and then retry the operation.
1720268396	5	0	The specified LDEV cannot be set as a journal volume because the volume is used as \\nan external volume that is mapped for online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
1720268418	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nprimary volume is used as an external volume that is mapped for online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
1720268419	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nsecondary volume is used as an external volume that is mapped for online data migration.\\nSpecify a volume other than the external volume mapped for the online data migration, \\nand then retry the operation.
1720268480	5	5	The journal registration failed because the 2DC cascade was specified as enabled.\\nSet the 2DC Cascade as disabled, and then retry the operation.
1720269446	5	5	A request to create a pair using a journal in the configuration consisting of three \\nUniversal Replicator sites was received. However, the operation failed because a \\npair creation for the Delta resync is specified.\\nVerify the settings.
1720269472	5	5	A Create Pairs failed because the serial number, the model, or the path group ID \\nof the specified Remote Storage System is invalid.\\nVerify the serial number, the model, and the path group ID of the specified secondary \\nstorage system.
1720269474	5	5	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 \\nconnection with the local storage system.\\n- The specified secondary volume is already used by TrueCopy.\\nVerify the firmware version of the specified remote storage system. If the firmware \\nversion supports the connection with the local storage system, select a different \\nvolume, and then retry the operation.
1720269475	5	5	The Create Pairs operation cannot be performed because the local storage system is \\nin 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.\\nVerify the firmware version of the local storage system and the models of the local \\nand remote storage systems.
1720269476	5	5	The Create Pairs operation cannot be performed because the local storage system is \\nin 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.\\nVerify the firmware version of the local storage system and the models of the local \\nand remote storage systems.
1720269478	5	5	The Resync Pairs operation cannot be performed because the specified secondary volume \\nis already used as a secondary volume of a pair in a different mirror and the pair \\nstatus is not applicable to the operation.\\nDelete a pair, whose secondary volume is also used for a pair in the specified mirror, \\nin a different mirror, and then retry the operation.
1720269479	5	5	The specified volume cannot be used as a journal volume because the capacity of the \\nvolume is not enough.\\nSpecify a volume with capacity of 1.5 GB or more, and then retry the operation.
1720269504	5	5	The Create Pairs operation cannot be performed because the remote storage system \\ndoes not support the specified path group ID.\\nVerify the firmware version of the remote storage system. If the firmware version \\nonly supports Default for the path group ID, specify Default for the ID, and then \\nperform the Create Pairs operation.
1720269508	5	5	A pair operation cannot be performed because a different mirror of the specified \\nrestore journal is in status transition (Halting/ Stopping).\\nWait until the status transition of the different mirror is complete (Initial/Stopped), \\nand then retry the operation.
1720269538	5	5	The Create Pairs operation cannot be performed because there is not enough space \\nleft in the difference management area of the local storage system.\\nIf the extended shared memory is not installed on the local storage system, install \\nit, and then retry the operation. If the extended shared memory is already installed \\non the local storage system, a new pair cannot be created because the number of pairs \\nthat can be created on the system exceeds the maximum.
1720269539	5	5	The Create Pairs operation cannot be performed because the extended shared memory \\nis not installed on the local storage system.\\nInstall the extended shared memory on the local storage system, and then retry the \\noperation.
1720269540	5	5	The Create Pairs operation failed because there is not enough space left in the difference \\nmanagement area of the Remote Storage System.\\nIf the extended shared memory is not installed on the remote storage system, install \\nit, and then retry the operation. If the extended shared memory is already installed \\non the remote storage system, a new pair cannot be created because the number of \\npairs that can be created on the system exceeds the maximum.
1720269541	5	5	The Create Pairs operation failed because the extended shared memory is not installed \\nin the Remote Storage System.\\nInstall the extended shared memory in the Remote Storage System, and then retry the \\noperation.
1720269543	5	5	Failed to change the journal option because the parameter of Inflow Control is invalid.\\nVerify the parameter of the specified Inflow Control.
1720270216	5	5	Failed to change the journal option because the parameter of Data Overflow Watch \\nis invalid.\\nVerify the parameter of the specified Data Overflow Watch.
1720270217	5	5	Failed to change the mirror option because the parameter of Copy Pace is invalid.\\nVerify the parameter of the specified Copy Pace.
1720270218	5	5	Failed to change the mirror option because the parameter of Path Watch Time is invalid.\\nVerify the parameter of the specified Path Watch Time.
1720270219	5	5	Failed to change the mirror option because the parameter of Transfer Speed is invalid.\\nVerify the parameter of the specified Transfer Speed.
1720270220	5	5	Failed to change the journal option because the parameter of Timer Type is invalid.\\nVerify the parameter of the specified Timer Type.
1740608483	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740638018	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740638019	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740638050	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740638052	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740638087	1	0	The operation cannot be performed because any of the specified parameters is not valid.\\nIf this problem persists, contact the HSSC.
1740668769	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
1740697569	5	3	A communication time-out error occurred.\\nIf this problem persists, contact the HSSC.
1740697570	1	3	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
1740701413	1	3	The storage system requires maintenance.\\nVerify the status of the storage system (if the storage system is blocked, shared \\nmemory is inconsistent, or some other factor). If this problem persists, contact the HSSC.
1797896321	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
1797926296	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
1797926297	1	2	An error occurred during Storage Navigator processing.\\nIf the same problem persists despite retrying, please call the HSSC.
1952539916	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
1952629319	1	2	An error occurred during Storage Navigator processing.\\nIf the problem persists despite retrying, please call the HSSC.
2033206435	5	5	The shared memory required for the specified operation is not installed on the local \\nstorage system.\\nSee the manual to verify the condition for this operation.
2033206458	5	5	The shared memory required for the specified operation is not installed on the remote \\nstorage system.\\nSee the manual to verify the condition for this operation.
2033206466	5	0	The operation cannot be performed because the specified primary volume is a reserved \\nvolume of global-active device.\\nRelease the reserved volume setting, or specify a different volume.
2033206467	5	0	The operation cannot be performed because the specified secondary volume is a reserved \\nvolume of global-active device.\\nRelease the reserved volume setting, or specify a different volume.
2033206582	5	0	The specified primary volume is used by a global-active device pair.\\nSpecify a different volume.
2033206583	5	0	The specified secondary volume is used by a global-active device pair.\\nSpecify a different volume.
2033206584	5	5	The operation cannot be performed because different firmware versions coexist on \\nthe storage system.\\nChange the firmware, and then retry the operation.
2033206709	5	0	The operation cannot be performed because Data Direct Mapping is enabled on the specified \\nprimary volume but the remote storage system does not support Data Direct Mapping.\\nUpdate the DKCMAIN firmware on the remote storage system to a version that supports \\nData Direct Mapping.
2033211295	5	5	The operation cannot be performed because the specified primary volume is a nondisruptive \\nmigration volume.\\nSpecify a different volume.
2033211296	5	5	The local storage system does not support nondisruptive migration.\\nVerify the DKCMAIN firmware version of the local storage system. Or, specify an LDEV \\non which the virtual access mode is disabled.
2033211297	5	5	The remote storage system does not support nondisruptive migration.\\nVerify the DKCMAIN firmware version of the remote storage system. Or, specify an \\nLDEV on which the virtual access mode is disabled.
2033211298	5	5	The Create Pairs operation cannot be performed because no virtual LDEV ID is set \\non the volume specified as the secondary volume.\\nSet a virtual LDEV ID on the specified volume, or specify a different volume.
2033211299	5	5	The Create Pairs operation cannot be performed because no virtual LDEV ID is set \\non the volume specified as the primary volume.\\nSet a virtual LDEV ID on the specified volume, or specify a different volume.
2033211301	5	0	The operation cannot be performed because the T10 PI setting differs between the \\nprimary volume and the secondary volume.\\nSpecify volumes with the same T10 PI setting as the primary volume and the secondary volume.
2042998285	5	2	The size of the specified volume is outside the setting range.\\nCheck the setting range of the volume size, and then change the size of the volume.
2042998286	1	6	The free space remaining in the parity group is not enough to install a customized \\nvolume (CV).\\nThe error does not occur normally because it cannot be modified in the window. In \\nthe unlikely event that this error occurs, please call the HSSC.
2042998288	5	2	A path is defined to the specified volume. \\nCheck the setting.
2042998311	5	6	The CU number and the LDEV number set in the VLL operation are the same as those \\nof other volumes.\\nCheck and correct the settings.
2042998313	5	2	An operation is specified for the uninstalled VDEV.\\nCorrect the settings, then retry the operation.
2042998314	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2042998319	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2042998407	5	2	The specified CU number cannot be set.\\nCorrect the settings.
2042998408	1	2	In the VLL operation (Create LDEVs, Delete LDEVs), there are some operations which \\ncannot be set together are specified.\\nSpecify one or more than one operations of Create LDEVs, Delete LDEVs in the VLL \\noperation.
2042999148	5	2	An operation is specified for the uninstalled volume.\\nCorrect the settings, then retry the operation.
2042999150	5	2	An operation is specified for the uninstalled Parity Group.\\nCorrect the settings, then retry the operation.
2042999152	5	2	The number of volumes exceeds the maximum that can be set.\\nCheck the settings.
2043003953	5	6	This functionality is not available. Open Volume Management is required.\\nInstall the necessary P.P. license key.
2043006835	5	3	The operation cannot be performed because the storage system is being maintained.\\nWait until the maintenance operation is complete, and then retry the operation.
2043006866	5	6	The specified volume contains a Thin Image pair.\\nCheck the setting of the specified volume.
2043006867	5	6	The specified volume contains Pool-VOLs. \\nSelect another volume.
2043006869	5	6	The setting cannot be made because the specified LDEV is a remote command device.\\nCheck the setting.
2043006870	5	6	The number of DP-VOL(s) has exceeded the maximum number of DP-VOL(s) that can be \\nset in a storage system.\\nCorrect the settings, then retry the operation.
2043027981	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043027982	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043028009	1	3	The status of the storage system requires maintenance (for example, the storage system \\nis blocked, the shared memory is inconsistent, or some other factor).\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
2043028013	1	3	An error occurred while connecting to the storage system.\\nA communication error occurs. If the same error occurs despite retrying, please call the HSSC.
2043028041	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043028226	1	6	An error occurred during a VLL operation to add or delete customized volumes. Please \\nwait for a while, and then retry the operation.\\nIf this problem persists, please call the HSSC. To perform a VLL operation on an \\nexternal volume, check the status of the path to the external volume.
2043028230	5	6	Copying is in progress for a pair of TrueCopy, Universal Replicator, ShadowImage, \\nVolume Migration, or Thin Image.\\nWait for a while, and then retry the operation.
2043028231	5	6	The configuration of TrueCopy, Universal Replicator, ShadowImage, Volume Migration, \\nor Thin Image has been defined.\\nRelease the configuration definition, and then retry the operation.
2043028233	5	6	The Remote Copy pair is suspended.\\nAdd an alternative path.
2043028234	5	6	The corresponding CHB might contain the last path between the MCU and RCU of TrueCopy \\nor Universal Replicator.\\nBe sure there is an alternative path from the MCU.
2043028256	5	6	ShadowImage or Thin Image setting exists. \\nRelease the settings or stop the I/Os, and then retry the operation.
2043028257	5	6	The backup server of ShadowImage or Thin Image is running. \\nStop the backup server, and then retry the operation.
2043028258	5	6	Some pairs of ShadowImage or Thin Image exist. \\nSplit the pair of ShadowImage or Thin Image.
2043028259	5	6	Some ShadowImage pairs exist. \\nResynchronize the ShadowImage pairs.
2043028260	5	6	Some ShadowImage pairs exist. \\nChange the status of the volumes to Simplex.
2043028261	5	6	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.\\nWait for a while, and then retry the operation.
2043029900	5	6	Processing cannot be performed because of Data Retention Utility settings.\\nCheck the settings, then retry the operation.
2043029903	5	6	Devices to be maintained include journal volumes.\\nDelete or suspend all pairs to which the journal volumes belong.
2043029904	5	6	Devices to be maintained include journal volumes.\\nDelete all pairs to which the journal volumes belong.
2043032818	5	6	A TrueCopy pair or a Universal Replicator pair is defined. \\nRelease the pair definition, and then retry the operation.
2043032819	5	6	A TrueCopy pair or a Universal Replicator pair is defined. \\nDelete the pair definition or suspend the pair, and then retry the operation.
2043032820	5	6	The target volume is defined as a pair volume of ShadowImage or Thin Image.\\nSplit the pair, and then retry the operation. If the Quick Split mode is on, suspend \\nand then split the pair.
2043032821	5	6	A ShadowImage pair is defined.\\nSplit the pair, and then retry the operation. If the Quick Split mode is on, suspend \\nand then split the pair.
2043032844	5	6	A Volume Migration pair is defined.\\nRelease the pair definition, then retry the operation.
2043032845	5	6	A Volume Migration pair is defined.\\nRelease the pair definition.
2043057770	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043057771	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043057774	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043057776	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043117384	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043147142	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043147173	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043147174	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2043147205	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
2043147206	1	2	An error occurred during Storage Navigator processing.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
2043147422	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, please call the HSSC.
2088768037	5	5	The Ethernet MTU size is not valid.\\nIf this problem persists, contact the HSSC.
2088768038	5	5	The VLAN tagging mode is not valid.\\nIf this problem persists, contact the HSSC.
2088768039	5	5	The VLAN ID is not valid.\\nIf this problem persists, contact the HSSC.
2088768040	5	5	A network address, a loopback address, a broadcast address, or an address whose first \\nsegment is 255 cannot be specified for the IPv4 IP address.\\nVerify the settings, and then retry the operation.
2088768041	5	5	The IPv6 mode is not valid.\\nIf this problem persists, contact the HSSC.
2088768042	5	5	The IPv6 link local address is not valid.\\nIf this problem persists, contact the HSSC.
2088768043	5	5	The IPv6 link local address is not valid.\\nIf this problem persists, contact the HSSC.
2088768044	5	5	The IP address set for Global Address 1 or Global Address 2 is not correct.\\nVerify whether the global address of IPv6 is set. If this problem persists, contact the HSSC.
2088768045	5	5	A multicast or loopback address cannot be set for Global Address 1 of IPv6.\\nVerify the settings.
2088768046	5	5	A multicast address or a loopback address cannot be specified for the IPv6 default gateway.\\nVerify the settings, and then retry the operation.
2088768068	5	5	The TCP port number is not valid.\\nIf this problem persists, contact the HSSC.
2088768069	5	5	The selective ACK is not valid.\\nIf this problem persists, contact the HSSC.
2088768070	5	5	The delayed ACK is not valid.\\nIf this problem persists, contact the HSSC.
2088768071	5	5	The maximum window size is not valid.\\nIf this problem persists, contact the HSSC.
2088768072	5	5	The entered keep alive timer is not valid.\\nIf this problem persists, contact the HSSC.
2088768073	5	5	The iSNS server is not valid.\\nIf this problem persists, contact the HSSC.
2088768074	5	5	The IP address of the iSNS server is not valid.\\nIf this problem persists, contact the HSSC.
2088768075	5	5	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 \\n255 cannot be specified for the IPv4 IP address.\\n - An unspecified address, a multicast address, or a loopback address cannot be specified \\nfor the IPv6 address.\\nVerify the settings, and then retry the operation.
2088768076	5	5	The TCP port number of the iSNS server is not valid.\\nIf this problem persists, contact the HSSC.
2088768077	5	5	To disable the IPv6 setting, it is required to remove all remote paths to avoid a \\nremote replication error.\\nDelete the remote paths, and then retry the operation.
2088768099	5	5	The same IPv6 address cannot be specified on the same port.\\nVerify the settings, and then retry the operation.
2088768100	5	5	The VLAN tagging mode cannot be set because the VLAN ID is not entered.\\nEnter the VLAN ID, and then retry the operation.
2088768101	5	6	The specified port belongs to a resource group that you do not have permission to access.\\nLog out, and then log back in with access to the resource group containing the specified port.
2088768102	5	5	The configuration information cannot be updated on the storage system.\\nIf this problem persists, contact the HSSC.
2088768103	5	5	The entered VLAN ID is already registered.\\nVerify the settings, and then retry the operation.
2088768104	5	5	A VLAN ID is already set on the specified iSCSI port.\\nDelete the VLAN ID, and then retry the operation.
2088768105	5	5	The setting of Subnet Mask for IPv4 is not valid.\\nVerify the setting, and then retry the operation.
2088768106	1	5	An error occurred on the storage system.\\nIf this problem persists, contact the HSSC.
2088768107	5	5	The specified iSCSI target is already added.\\nClick the refresh button to have the latest information displayed on the window, \\nand then retry the operation.
2088768108	5	5	The specified iSCSI target does not exist.\\nClick the refresh button to have the latest information displayed on the window, \\nand then retry the operation.
2088768130	5	5	The following symbols and spaces cannot be used for iSCSI Target Name:\\n! " # $ % & ' ( ) = ~ ^ | \ ` @ { } [ ] ; + * < > , ? / _\\nVerify the setting.
2088768131	5	5	The following symbols cannot be used for CHAP User Name or Secret:\\n! " # $ % & ' ( ) ^ | \ ` { } ; * < > , ?\\nVerify the setting.
2088768132	5	5	No more iSCSI paths or remote paths using iSCSI can be added because the total of \\niSCSI paths and remote paths using iSCSI reaches the maximum that can be added to \\nthe storage system.\\nDelete unnecessary iSCSI paths or remote paths using iSCSI, and then retry the operation.
2088768133	5	5	The operation cannot be performed because the processing of iSCSI Targets Discovery \\nto be simultaneously performed reaches the maximum.\\nWait for a while, and then retry the operation.
2088768134	5	5	The test login to the iSCSI target cannot be performed.\\nVerify the following, and then retry the operation.\\n- The iSCSI ports on the local storage system and on the external storage system \\nare connected.\\n- The iSCSI target with the specified IP address and TCP port number exists on the \\nexternal storage system.\\n- The ports on the local storage system and on the iSCSI target have the same settings \\nfor Authentication Method and Mutual CHAP.\\n- If CHAP is selected as an authentication method, the same User Name and Secret \\nare set on the ports on the local storage system and the iSCSI target . If Mutual \\nCHAP is enabled, the same User Name and Secret are also set on the iSCSI path and \\nthe iSCSI target.
2088768135	5	5	The operation cannot be performed because the number of login tests of iSCSI targets \\nsimultaneously performed reaches the maximum.\\nWait for a while, and then retry the operation.
2088768136	5	5	The operation cannot be performed because the specified port is not an iSCSI port.\\nVerify the type of the specified port.
2088768137	5	5	The operation cannot be performed because the storage system is in internal process, \\nor a different user is changing the configuration.\\nWait for a while, and then retry the operation.
2088768138	5	5	The operation cannot be performed because the resource group that the specified iSCSI \\nport, host group, or the LDEV is belongs to is locked by a different user.\\nWait for the resource lock to be released, and then retry the operation.
2088768139	1	5	The operation cannot be performed because the storage system requires maintenance, \\nsuch as that the storage system is blocked, or that the shared memory is inconsistent.\\nContact the HSSC.
2088768161	5	5	No more iSCSI paths or remote paths can be added to the specified port because the \\ntotal of iSCSI paths and remote paths using iSCSI reaches the maximum that can be \\nadded to a port.\\nDelete unnecessary iSCSI paths or external paths connected to the specified port, \\nand then retry the operation.
2088768162	5	5	The specified iSCSI port or iSCSI path cannot be edited or deleted because it is \\nused for an external path.\\nDelete the external path, and then retry the operation.
2088768163	5	7	Discover iSCSI Targets cannot be performed.\\nVerify the following, and then retry the operation.\\n- The iSCSI ports on the local storage system and on the external storage system \\nare connected.\\n- The iSCSI port with the specified remote IP address and the specified remote TCP \\nport number exists on the external storage system.\\n- If Port Security for the iSCSI port on the external storage system is enabled, \\nthere is an iSCSI target with the iSCSI name of the local port set as a host.\\n- The same combination of the iSCSI port of the local storage system and the iSCSI \\nport of the external storage system corresponding to the remote IP address is not \\nadded in the Discovery List.
2088768164	5	5	The selected iSCSI path cannot be edited because it is used as a remote path.\\nRemove the remote path, and then retry the operation.
2088768165	5	5	The specified ports, iSCSI targets, or host groups cannot be used because you do \\nnot have permission to access a resource group to which they belong.\\nAsk the administrator for resource assignment.
2088768166	5	5	The current DKCMAIN microcode version does not support the specified operation.\\nVerify the microcode versions of the DKCMAIN and the SVP.
2088768167	5	5	The following addresses cannot be specified for the IP address: a network address, \\na broadcast address, a multicast address, a loopback address, and an address consisting \\nof all zeros (0).\\nVerify the setting, and then retry the operation.
2088768194	5	5	In the current DKCMAIN firmware version, an IPv6 address cannot be set for Global \\nAddress 2.\\nContact the HSSC to update the DKCMAIN firmware, and then retry the operation.\\nIf you do not want to update the DKCMAIN firmware, do not set Global Address 2.
2088768195	5	5	Global Address 2 cannot be set because Global Address 1 is not set.\\nSet Global Address 1. If necessary, set Global Address 2.
2088768196	5	5	A multicast or loopback address cannot be set for Global Address 2 of IPv6.\\nVerify the settings.
2088768197	5	5	The settings of the specified port cannot be changed, because the iSCSI virtual port \\nmode is enabled.\\nVerify the settings, and then retry the operation.
2088768198	5	7	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.\\nVerify the settings, and then retry the operation.
2088768199	5	7	The operation cannot be performed, because the specified virtual port does not exist.\\nVerify the specified virtual port ID, and then retry the operation.
2088768200	5	5	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 \\niSCSI port.\\n- The same iSCSI target is specified for multiple virtual ports of an iSCSI port.\\nVerify the settings, and then retry the operation.
2088827620	5	5	An error occurred during processing.\\nVerify the details of the error.
2088857410	5	5	The storage system has accepted the request normally, but the processing requires \\nsome time.\\nIf this problem persists, close the windows, verify that the internal processing \\nor the configuration change has been completed, and then retry the operation.  If \\nthe internal processing or the configuration change takes much time to complete, \\ncontact the HSSC.
2133575626	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
2133635239	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, contact the HSSC.
2133635329	5	0	Too many objects are specified.\\nSpecify fewer objects, and then retry the operation.
2133640042	5	5	The program product is not installed.\\nInstall the program product.
2133664996	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, contact the HSSC.
2133664997	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, contact the HSSC.
2133665029	1	3	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, contact the HSSC.
2133665060	1	2	A file open error has occurred.\\nRetry the operation. If this problem persists, contact the HSSC.
2133665061	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
2133669803	5	5	Processing in progress.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
2133669901	3	5	There is no error in this setting.\\nHowever, there is an error in another setting and the setting processing has not \\nbeen executed.\\nCorrect the error in the other setting, and then retry the operation.
2133694973	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
2133695780	1	2	An error occurred during Storage Navigator processing.\\nIf this problem persists, contact the HSSC.
2133697701	1	5	This error code is not registered.\\nPlease contact the HSSC when it is a same deal even if it operates it again.
2133724578	1	3	An error occurred during Storage Navigator processing.\\nWait for a while, and then retry the operation. If this problem persists, contact the HSSC.
2133724579	5	3	A communication time-out error occurred in the local storage system.\\nWait for a while, and then retry the operation.
2133724580	5	3	A communication time-out error occurred in the local storage system.\\nWait for a while, and then retry the operation.
2133725539	1	2	An error occurred during Storage Navigator processing.\\nRetry the operation. If this problem persists, contact the HSSC.
2133725541	1	3	This function is not supported.\\nVerify the DKCMAIN firmware version and the Storage Navigator software version.
2133731305	5	4	Please retry operation. \\nWait for a while, and then retry the operation.
2133731306	5	4	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 \\nis not valid.\\n- The status of the specified secondary volume is SMPL.\\nVerify the status of the remote path on the local storage system and the status of \\nthe remote path and the pair on the remote storage system, and then perform the following \\noperations:\\n- If the remote path is not valid, reestablish the remote path by an Add Path operation.\\n- If the status of the secondary volume is SMPL, delete the pair from the primary \\nsite containing the primary volume, and then retry Create Pairs.
2133731307	5	0	The status of the primary volume is invalid.\\nRefresh the window, and then verify the status of the primary volume. Retry the operation \\nif the primary volume is available.
2133731308	5	4	The specified number of remote paths is less than the minimum number of paths.\\nVerify the number of remote paths, and then retry the operation.
2133731309	5	4	The specified number of remote paths was less than the minimum number of paths due \\nto a communication error between the local storage system and the remote storage system.\\nVerify the status of the remote paths, and then recover the paths.
2133731311	5	4	Parameter specified by Remote Copy operation is invalid. \\nEnter the correct data.
2133731313	5	0	The pair status of the secondary volume is invalid.\\nRefresh the window, and then verify the pair status. Retry the operation if the secondary \\nvolume is available.
2133731336	5	0	The pair status of the specified data volume is incorrect.\\nRefresh the window, and then verify the pair status. If the pair is in operable status, \\nretry the operation.
2133731337	5	4	The specified parameter is incorrect.\\nVerify if the specified port name, host group ID, iSCSI target ID, LUN ID, CU, or \\nLDEV exists in the local storage system.
2133731338	5	4	The operation was rejected due to a 'FREEZE' state.\\nIf it is a remote path operation, recover from the freeze status, and then retry \\nthe operation.\\nIf  it is a remote replication pair operation, recover the remote path status, and \\nthen retry the operation.
2133731339	5	4	The port group already exists on the specified port.\\nExchange the port type after deleting the group setting.
2133731340	1	4	An internal error occurred. \\nIf this problem persists, contact the HSSC.
2133731341	5	4	The number of remote paths is invalid.\\nVerify the number of remote paths, and then retry the operation.
2133731367	5	4	The number of registered remote storage systems already reached the maximum (64).\\nReduce the number of registered remote storage systems, and then retry the operation.
2133731368	5	4	The remote path creation is not complete yet.\\nVerify the remote path connections between the local and the remote storage systems, \\nand then retry the operation.
2133731369	5	4	The remote path could not be created.\\nVerify the remote path connections between the local and the remote storage systems, \\nand then retry the operation.
2133731370	5	4	The operation could not be performed because the specified remote path is the last \\npath of the remote replication pairs.\\nAdd a different remote path, or delete all remote replication pairs on the remote \\nstorage system, and then retry the operation.
2133731371	5	4	The specified number of remote paths is less than the minimum number of paths.\\nIncrease the number of remote paths, or reduce the minimum number of paths.
2133731374	5	4	The Minimum Number of Paths exceeds the number of normal Remote Paths.\\nAdd normal remote paths, and then set the minimum number of paths, or reduce the \\nminimum number of paths, and then delete the remote paths.
2133731375	5	4	The number of normal remote paths is less than the minimum number of paths.\\nAdd normal remote paths, and then set the minimum number of paths, or reduce the \\nminimum number of paths, and then delete the remote paths.
2133731376	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133731399	5	4	The existing logical addresses are not the same. \\nDelete the remote storage systems, then add the remote storage systems using the \\nsame logical address.
2133731404	5	4	The specified remote storage system contains journals or pairs for remote replication.\\nDelete pairs for the specified remote storage system. After that, delete journals \\nif any. Verify that there are no pairs or journals, and then retry the operation.
2133731405	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133731431	5	4	Pinned tracks exist in the primary volume.\\nRestore the pinned tracks in the primary volume.
2133731432	5	4	Pinned tracks exist in the secondary volume.\\nRestore the pinned tracks in the secondary volume.
2133731433	5	4	The specified primary volume cannot be used.\\nVerify that the primary volume is in any of the following conditions:\\n- The volume is in data copy process (correction copy or drive copy).\\n- The volume is in correction access condition.\\n- The volume is blocked.\\n- The volume is being maintained.\\n- The access attribute of the volume is Read Only.
2133731435	5	4	The emulation type of the primary volume is not supported.\\nSee the user guides to verify if the emulation type of the specified volume is supported.
2133731463	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133731467	1	4	One side of the cache or the shared memory is blocked in the local storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
2133731468	1	4	An unexpected error occurred in the local storage system.\\nContact the HSSC.
2133731495	5	4	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.\\nVerify that the secondary volume is not blocked, the restore journal is registered, \\nor the journal volumes of the restore journal are not blocked, respectively.
2133731522	5	4	The cache in the local storage system is automatically recovering.\\nWait for a few minutes, and then retry the operation.
2133731530	1	4	One side of the cache or the shared memory is blocked in the remote storage system.\\nIf there is an error found on the storage system or the SVP, see the manual to remove \\nthe error. If there is no error found on the storage system or the SVP, and this \\nproblem persists, contact the HSSC.
2133731561	5	0	The specified volume is not defined in the remote storage system.\\nVerify if the specified port name, host group ID, iSCSI target ID, LUN ID, CU, or \\nLDEV exists in the remote storage system.
2133731589	5	4	The operation cannot be performed because the volume specified as the primary volume \\nis used by ShadowImage 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.\\nVerify the status of the primary volume from the host or SVP.
2133732306	5	4	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 ShadowImage secondary volume.\\n- It is in use by Volume Migration.\\n- It is a ShadowImage primary volume in the Swap or Reverse Copy status.\\n- It belongs to "NAS_Platform_System_RSG" with resource group ID 1023.\\nVerify the status of the volume specified as a secondary volume.
2133732330	1	4	An I/O error occurred in the secondary volume.\\nVerify the SSB log, and then contact the HSSC.
2133732361	5	4	The Create Pairs operation cannot be performed because data volume migration by Volume \\nMigration is in progress on the specified primary volume.\\nWait for a while, and then retry the operation.
2133732362	5	4	The Create Pairs operation cannot be performed because data volume migration by Volume \\nMigration is in progress on the specified secondary volume.\\nWait for a while, and then retry the operation.
2133732363	5	4	The operation failed because you tried to create volume pairs which exceeded the \\nlicensed capacity.\\nSee the license key and confirm the licensed capacity of the volumes. To create more \\npairs, purchase a license key that allows you to use a larger capacity.
2133732364	5	0	The operation failed because you tried to create volume pairs which exceeded the \\nlicensed capacity of the Remote Storage System.\\nSee the license key information of the remote storage system and verify the licensed \\nvolume capacity. To create more pairs, purchase a license key that allows you to \\nuse a larger capacity.
2133732521	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133732522	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133732523	5	4	The specified port is not equipped.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
2133732545	5	4	The specified port is being initialized. \\nWait until the initialization of the specified port is complete, and then retry the \\noperation.
2133732546	5	4	LUN paths are defined on the specified port.\\nDelete the LUN paths on the specified port, and then retry the operation.
2133732548	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133732549	5	4	Jobs exist on the specified port.\\nStop the jobs from the host, and then retry the operation.
2133732550	5	4	Jobs exist on the port of the remote storage system.\\nStop the jobs from the host, and then retry the operation.
2133732551	5	4	A parameter error occurred.\\nRefresh the window, and then retry the operation. If this problem persists, contact the HSSC.
2133732552	5	4	LUs exist on the port. \\nDelete the LUN paths defined on the port, and then retry the operation.
2133732553	5	4	Pending data exists on the port. \\nRetry the operation.
2133732554	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133733227	1	4	An error occurred during the port change. \\nIf this problem persists, contact the HSSC.
2133733228	1	4	An error occurred during the port change. \\nIf this problem persists, contact the HSSC.
2133733229	1	4	An error occurred during the port change. \\nIf this problem persists, contact the HSSC.
2133733230	1	4	Unknown Error Code. \\nIf this problem persists, contact the HSSC.
2133733263	5	0	Storage Navigator attempted to change the port type. However, this attempt could \\nnot be made because the same operation was in progress from a host.\\nVerify the status of the port, and then retry the operation.
2133733293	5	4	LUN paths are defined to the port on the remote storage system.\\nDelete the LUN paths on the specified port, and then retry the operation.
2133733298	5	4	Invalid port type. \\nVerify the port type of the specified port, and then retry the operation.
2133733320	5	4	LUN paths are defined to the port on the remote storage system.\\nDelete the LUN paths on the specified port, and then retry the operation.
2133733321	5	4	LUN paths are defined to the port on the remote storage system.\\nDelete the LUN paths on the specified port, and then retry the operation.
2133733324	5	0	The Create Pairs operation cannot be performed because the volume specified as the \\nsecondary volume is a NAS system volume.\\nVerify the configuration of the volume specified as the secondary volume.
2133733326	5	0	The Create Pairs operation cannot be performed. The firmware version of the specified \\nremote storage system does not support the remote replication function using NAS volumes.\\nVerify the firmware version of the remote storage system.
2133733355	5	4	The specified secondary volume cannot be used because of the access attribute changed \\nby Data Retention Utility.\\nVerify the access attribute of the specified secondary volume.
2133733358	5	4	The external volume that is mapped to an internal volume is connected to the port.\\nRelease the setting of the external volume, then retry the operation.
2133733359	5	4	The specified port is receiving I/O requests.\\nStop the I/O operations, and then retry the operation.
2133733360	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
2133733382	1	4	An internal error occurred. \\nVerify the SSB log, and then contact the HSSC.
