HP P9000 Command View Advanced Edition Suite Software 7.4.0-00 CLI Reference Guide (TB581-96326, December 2012)
Table Of Contents
- CLI Reference Guide
- Table of Contents
- Preface
- 1 Overview
- 2 Environment settings
- 3 Executing commands
- 4 Command reference
- Storage system commands
- AddArrayReservation
- AddExternalArrayGroup
- AddHostStorageDomain
- AddLabel
- AddLogicalUnit
- AddLUSE
- AddPool
- AddStorageArray
- AddTieredPoolOperation
- AddVirtualVolume
- DeleteArrayReservation
- DeleteExternalArrayGroup
- DeleteHostStorageDomain
- DeleteLabel
- DeleteLogicalUnit
- DeleteLUSE
- DeletePool
- DeleteStorageArray
- DeleteVirtualVolume
- FormatLU
- GetArrayReservation
- GetPoolShrinkStatus
- GetStorageArray
- Using the GetStorageArray parameter
- GetStorageArray (subtarget not specified)
- GetStorageArray (subtarget=ArrayGroup)
- GetStorageArray (subtarget=CommParameters)
- GetStorageArray (subtarget=Component)
- GetStorageArray (subtarget=ExternalStorage)
- GetStorageArray (subtarget=Filter)
- GetStorageArray (subtarget=FreeSpace)
- GetStorageArray (subtarget=HostStorageDomain)
- GetStorageArray (subtarget=LDEV)
- GetStorageArray (subtarget=LogicalDKC)
- GetStorageArray (subtarget=LogicalUnit)
- GetStorageArray (subtarget=MFReplicationInfo)
- GetStorageArray (subtarget=Path)
- GetStorageArray (subtarget=PDEV)
- GetStorageArray (subtarget=Pool)
- GetStorageArray (subtarget=Port)
- GetStorageArray (subtarget=PortController)
- GetStorageArray (subtarget=ReplicationInfo)
- GetStorageArray (subtarget=TieringPolicy)
- GetTieredPoolStatus
- GetZeroPageReclaimStatus
- ModifyArrayReservation
- ModifyExternalTierRank
- ModifyLabel
- ModifyLogicalUnit
- ModifyPool
- ModifyPort
- ModifyPortController
- ModifyStorageArray
- ModifyTieringPolicy
- ModifyVirtualVolume
- RefreshPerformanceData
- RefreshStorageArrays
- RunZeroPageReclaim
- ShrinkPool
- Logical group commands
- LUN commands
- Host management commands
- Server management commands
- Replication commands
- Storage system commands
- 5 Output items
- Alert instance
- ArrayGroup instance
- ArrayReservation instance
- CommParameters instance
- Component instance
- ConfigFile instance
- Datastore instance
- ExternalPathInfo instance
- ExternalStorage instance
- FreeLUN instance
- FreeSpace instance
- Host instance
- HostInfo instance
- HostStorageDomain instance
- IPAddress instance
- LDEV instance
- LogicalDKC instance
- LogicalGroup instance
- LogicalUnit instance
- MFReplicationInfo instance
- ObjectLabel instance
- PairedPool instance
- PairedPortController instance
- Path instance
- PDEV instance
- PerformanceStatus instance
- Pool instance
- PoolTier instance
- Port instance
- PortController instance
- RelatedDistributedArrayGroup instance
- ReplicationControllerPair instance
- ReplicationGroup instance
- ReplicationInfo instance
- ServerInfo instance
- StorageArray instance
- TieringPolicy instance
- URLLink instance
- VirtualDisk instance
- VM instance
- VolumeConnection instance
- WWN instance
- 6 Batch functionality
- 7 Import functionality
- 8 Properties file
- Overview of the properties file
- Using the properties file to specify options
- Using the properties file to specify parameters
- Setting up the execution environment
- Specifying the log file
- Specifying a log level
- Message trace output
- Specifying the URL
- Inputting requests from XML documents
- Using the message trace file
- Output format of execution results
- Outputting execution results in CSV format
- Outputting execution results in XML format
- Specifying a DTD
- Using a DTD with the Device Manager CLI
- 9 Troubleshooting
- 10 Support and other resources
- A Connecting to P9000 mainframe agent
- About connecting to P9000 mainframe agent
- Setting up the mainframe host environment
- Setting up the Device Manager environment
- Refreshing information recognized by the mainframe host
- Acquiring P9000 mainframe agent information registered in Device Manager
- Changing P9000 mainframe agent information registered in Device Manager
- Deleting P9000 mainframe agent information registered in Device Manager
- Acquiring mainframe host information
- Changing mainframe host information
- Deleting a mainframe host
- Glossary
- Index

Y (condition-n): If the specification conditions for the parameter, condition-n, are satisfied, the
command can be executed together with other commands when this parameter is specified.
N: If this parameter is specified, the command cannot be executed together with other commands.
The command is executed by itself. By omitting this parameter, the command can be executed
together with other commands.
--: This parameter does not affect whether the command is executed together with other commands.
#1
If there is a command for which this parameter is specified and a command for which this para-
meter is omitted in the same batch file, specify the command with the parameter first. A value is
automatically set for this parameter when a value is omitted. As such, if the command with the
parameter omitted is executed first, the value that is automatically assigned during the first com-
mand execution might differ from the value specified for the parameter in the second command
execution, thus causing an error.
#2
If the emulation type of the parity group specified for this parameter is something other than
OPEN-V, an error occurs with the batch function and processing stops. Confirm the emulation
type of the specified parity group before executing the batch function.
#3
If the value specified is OPEN-V or if this parameter is omitted, the command can be executed
together with other commands.
#4
If you specify a value that corresponds to P9500 or XP24000/XP20000, the command can be
executed together with other commands.
#5
For this parameter, you can specify multiple THP/Smart volume device numbers. To specify five
or more device numbers, write them separately on multiple command lines. If you specify five or
more device numbers on one command line and then perform batch processing, an error might
occur with the error message KAIC90084-E that has the response value 413 Request Entity
Too Large.
Examples of batch file creation
The following shows an example of a batch file created according to the input rules from “Batch file
format and input rules” on page 386 to “Conditions for parameters to process commands
together” on page 387.
beginbatch
hdvmcli ADDLUN model=XP12000 serialnum=14053 portname=CL1-A domain=0 devnum=816 lun=100
hdvmcli ADDLUN model=XP12000 serialnum=14053 portname=CL1-A domain=0 devnum=817 lun=101
hdvmcli ADDLUN model=XP12000 serialnum=14053 portname=CL1-B domain=0 devnum=816 lun=102
hdvmcli ADDLUN model=XP12000 serialnum=14053 portname=CL1-B domain=0 devnum=817 lun=103
endbatch
Using the batch functionality
To use the batch functionality, specify the batch option (-b or --batch) and a batch file name.
When specifying the batch option, specify the following items from the command line or in the
properties file:
• Device Manager server URL
• Options other than -i or --input
CLI Reference Guide 391