HP P4000 9.0 HP StorageWorks P4000 SAN/iQ Command-Line Interface User Manual - Page 7

Syntax - code

Page 7 highlights

Syntax CLIQ is the command-line interface (CLI) for the HP P4000 Storage Solution. The CLI specifies parameters in the form parameter= (specification), rather than dictating a particular order (positional) notation. Parameter ordering Ordering of parameters is not specified. Any order will do. For example: cliq deleteVolume volumeName=theVolume userName=user passWord=secret login=10.1.2.3 is equivalent to cliq deleteVolume login=10.1.2.3 passWord=secret userName=user volumeName=theVolume The method parameter may be optionally specified as "method=": cliq userName=user passWord=secret login=10.1.2.3 volumeName=theVolume method=deleteVolume Case sensitivity All commands and parameter names are case-insensitive. "createVolume" is the same as "CreateVolume" is the same as "CREATEVOLUME". In some cases, parameter values, while not sensitive, are case significant as the system will preserve the case specified. For example, the description parameter value in the createVolume command will preserve the case specified by the caller, and impose this on the newly created volume. True/False Any parameter that indicates true/false, may be specified as "1|0" or "true|false". Command abbreviation There is no command or parameter abbreviation in the CLI when scripted. All commands and parameter names must be fully specified. This is to prevent ambiguity in legacy scripts if new commands or parameters are added. OS error code integration 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158

7
Syntax
CLIQ is the command-line interface (CLI) for the HP P4000 Storage Solution.
The CLI
specifies parameters in the form parameter=<parameter> (specification), rather than
dictating a particular order (positional) notation.
Parameter ordering
Ordering of parameters is not specified.
Any order will do.
For example:
cliq deleteVolume volumeName=theVolume userName=user passWord=secret
login=10.1.2.3
is equivalent to
cliq deleteVolume login=10.1.2.3 passWord=secret userName=user
volumeName=theVolume
The method parameter may be optionally specified as "method=<command>":
cliq userName=user passWord=secret login=10.1.2.3 volumeName=theVolume
method=deleteVolume
Case sensitivity
All commands and parameter names are case-insensitive.
"createVolume" is the same
as "CreateVolume" is the same as "CREATEVOLUME".
In some cases, parameter
values, while not sensitive, are case significant as the system will preserve the case
specified.
For example, the description parameter value in the createVolume
command will preserve the case specified by the caller, and impose this on the newly
created volume.
True/False
Any parameter that indicates true/false, may be specified as "1|0" or "true|false".
Command abbreviation
There is no command or parameter abbreviation in the CLI when scripted.
All
commands and parameter names must be fully specified.
This is to prevent ambiguity
in legacy scripts if new commands or parameters are added.
OS error code integration