What to do if HP StorageWorks P9000 Storage returns DATASET_ERROR_VOLUME_DEFINITION_INVALID?
If you get a DATASET_ERROR_VOLUME_DEFINITION_INVALID error, it means the format of the volume definition file is invalid. Ensure that the Data Exchange volume definition file was created correctly.
How to resolve DATASET_ERROR_DEVICE_TYPE_NOT_SUPPORTED on HP StorageWorks P9000?
If you receive the DATASET_ERROR_DEVICE_TYPE_NOT_SUPPORTED error, it means the device emulation type is not supported. Ensure that the device emulation type (LVI) is correct in the Data Exchange volume definition file. The supported LVIs are 3390-3A, -3B, and -3C.
How to fix DATASET_ERROR_INVALID_VOLUME in HP StorageWorks P9000?
If you encounter a DATASET_ERROR_INVALID_VOLUME error, it means the actual VSN and the VSN specified in the Data Exchange volume definition file do not match. Ensure that the VSN in the Data Exchange volume definition file is correct.
How to recover from a HP StorageWorks P9000 hardware blockade?
If hardware redundancy has been lost due to some blockade condition, remove the hardware blockade or failure according to the SIM. Restore the failed volume pairs (Pairresync). If a failure occurs during execution of the RAID Manager horctakeover command, secondary volumes in SSWS pair status may remain in the master journal. If these volumes remain, execute the pairresync -swaps command on the secondary volumes whose pair status is SSWS. This operation changes all volumes in the master journal to primary volumes. After this operation, restore the volume pairs (Pairresync).
What to do if HP Storage returns DATASET_ERROR_DATASET_NOT_FOUND?
If you encounter a DATASET_ERROR_DATASET_NOT_FOUND error, verify that the actual dataset name matches the specified dataset name. To check the dataset name, you can use the MF-File list command in the FCU Help menu or the VTOC dump data on the mainframe host.
What to do if cannot find Definition statement file in HP StorageWorks P9000?
If the definition statement file cannot be found in HP Storage, check that the specified file exists. If it does not, re-execute after setting up the file.
How to fix invalid port mode error on HP StorageWorks P9000?
To fix an invalid port mode error on HP Storage, ensure the correct primary system port is configured as an initiator port and the correct secondary system port is configured as an RCU target port. Also, verify that you've entered the correct secondary system S/N, SSID, and path parameters, including port, link address, and logical address. If problems persist, delete the failed path. You may need to change the minimum paths setting or delete the secondary system to delete the path, then add the path or secondary system using Edit Path or Add RCU.
What to do if the I/O error of Definition statement file occurred in HP Storage?
If you encounter an I/O error with the Definition statement file in HP Storage, check the condition of the definition statement file or the system, and then re-execute the process.
Why can't I create or delete encryption keys on HP Storage?
If you're unable to create or delete encryption keys on your HP Storage, ensure that DKA Encryption is enabled and has not expired. Additionally, confirm that the Security Administrator (View & Modify) role is assigned to your user account.
Why LU warning message appears when migrating a parity group to another CLPR in HP StorageWorks P9000 Storage?
When attempting to migrate a parity group to another CLPR, an LU warning message appears because LUSE volumes cannot be set across more than one CLPR.
General| RAID Support | RAID 0, 1, 5, 6, 10 |
|---|---|
| Interface | Fibre Channel, iSCSI, FCoE |
| Form Factor | Rack-mountable |
| Model | P9000 |
| Operating System Compatibility | Windows, Linux, VMware, HP-UX |
| Host Interface | Fibre Channel, iSCSI, FCoE |
| Drive Interface | SAS, SSD |
| Drive Types Supported | SSD, SAS |
| Redundancy | Redundant controllers, power supplies, and fans |
| Management Software | HP StorageWorks Command View |
General introduction to the Data Exchange Code Converter functionality and its purpose.
Describes the operational flow and components involved in the Data Exchange Code Converter.
Details the process of converting alphanumeric character data, focusing on single-byte codes.
Explains double-byte character conversion, including mixed single and double-byte data.
Covers the conversion of numeric data fields, including process flow.
Lists the necessary hardware, software, and release notes for the Code Converter.
Details the files and their locations provided on the installation media for UNIX.
Step-by-step guide for installing, uninstalling, and upgrading on UNIX systems.
Explains how to input the license key required for Code Converter operation.
Illustrates the user's workflow for performing data conversion operations.
Describes the supported record formats and field positions for data files.
Introduces MTO conversion, including EBCDIC to ASCII and IBM Traditional Chinese to Big5.
Details the specific conversion of alphanumeric fields in MTO.
Introduces OTM conversion, including ASCII to EBCDIC and Big5 to IBM Traditional Chinese.
Explains how to customize the code conversion table for OTM.
Details the conversion of packed decimal numeric data.
Explains the process for converting zoned decimal numeric data.
Provides a high-level overview of the code conversion table customization process.
Describes the syntax rules for defining conversion statements used in customization.
Explains the command syntax for customizing tables on UNIX systems.
Lists and explains common error codes and their meanings.
Details the format and interpretation of messages generated by the ccnv utility.
Provides guidance on what information to gather before contacting HP support.
Lists other relevant HP documents for further information.
Information on how to obtain technical support from HP.
To Next Page