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

name=toro2
hostID=1
capacityInKB=0
hostType=2
statusOfDBUpdating=-1
*****: The value is encoded by the CLI.
Registering the P9000 mainframe agent running on the mainframe host in Device
Manager
To use the AddURLLink command to register the mainframe host in Device Manager:
1. Execute the AddURLLink command to register the P9000 mainframe agent running on the
mainframe host in Device Manager.
When you execute the command, specify the following parameters:
• url: In this parameter, specify the IP address and port number.
If the mainframe host is in an IPv4 environment: Specify the IP address of the mainframe host
on which P9000 mainframe agent is installed, and the port number used by P9000 mainframe
agent.
If the mainframe host is in an IPv6 environment: Specify the IP address (by enclosing it in
square brackets ([ and ])) and port number of IBM HTTP Server.
• name: In this parameter, specify the character string MainframeAgent, which indicates
P9000 mainframe agent. Note that this parameter is case-sensitive.
• linkedid: In this parameter, specify the object ID of the mainframe host output when the
mainframe host was registered using the AddHost command.
2. From the execution result of the AddURLLink command, make sure that specified information
is correctly output to the url, name, and linkedid parameters.
Notes on executing the AddURLLink command:
If the name parameter is specified incorrectly, the mainframe host is not registered as the P9000
mainframe agent information, and mainframe volume information and the logical DKC serial
number of the storage system cannot be acquired. If you specified the name parameter incorrectly,
use the DeleteURLLink command to delete the P9000 mainframe agent information, and then
use the AddURLLink command to register the information again. For details about how to delete
the P9000 mainframe agent information, see “Deleting P9000 mainframe agent information re-
gistered in Device Manager” on page 442.
Action to be taken if an error occurs during the execution of the AddURLLink command:
Use the GetURLLink command to check whether P9000 mainframe agent has been registered.
If P9000 mainframe agent has not been registered, register it by using the AddURLLink command.
If P9000 mainframe agent has been registered incorrectly, use the AddURLLink command to
correct the registered information. For details about how to correct the registered P9000 mainframe
agent information, see “Changing P9000 mainframe agent information registered in Device
Manager” on page 441.
Command format (for an IPv4 environment):
hdvmcli AddURLLink "url=http://mainframe-host-IP-address:port-number"
"name=MainframeAgent" "linkedid=mainframe-host-object-ID"
CLI Reference Guide 437