HP XP P9500 HP P9000 Business Continuity Manager Reference Guide (T5253-96058, - Page 194

YKDELCMD Command, Table 104 YKCONMSG Command Return Code List

Page 194 highlights

NOTE: • In some configurations such as when BC and CA share volumes or a 1 to n (n is greater than 1) configuration of BC, the status transitions of each copy pair might not be correctly monitored. • When using a copy pair on a remote site (a site that is not channel-connected directly from the local host), there are the following restrictions: ◦ Even if a copy pair status changes, the IEA494I message is not displayed on the MVS console. Thus, the YKCONMSG command cannot monitor status transitions of a copy pair on a remote site. ◦ The IOSHM0414I message or user-specified messages are not displayed on the MVS console even when a HyperSwap is completed. Consequently, the YKCONMSG command cannot monitor the completion of HyperSwaps of a copy pair at a remote site. • When using a CAJ copy pair, even if the copy pair status changes, the IEA494I message is not displayed on the MVS console. Thus, the YKCONMSG command cannot monitor the status transitions of the CAJ copy pair. • The YKCONMSG command cannot monitor Non Gen'ed volumes. Return Codes Table 104 (page 194) lists the return codes to be returned when the YKCONMSG command terminates. Table 104 YKCONMSG Command Return Code List Return Code -3 Meaning The module cannot be loaded. Possible causes are as follows: • The library dataset has not been linked. • APF grant has not been registered. • The module is protected by the RACF program control function. -1 An interruption occurred during execution. 0 Open processing terminated normally. 1 Message specified by the MSGID parameter was returned (IEA494I message if the MSGID parameter was omitted). 2 Although the system waited for the number of seconds specified for the TIMEOUT parameter, no message was found. 4 Message lost since previous invocation. 6 Close successful. 8 Invalid parameter. 9 System error. YKDELCMD Command Applies to CMD. Format YKDELCMD { 1SN(storage system-serial-number)| 1SN(storage system-serial-number) 1CU(cu-number) 1CCA(cca-number) 1APID(apid)| 1DEVN(device-number) 1APID(apid)} 1MSG(stem-name-1) 194 CLI Commands

  • 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392

NOTE:
In some configurations such as when BC and CA share volumes or a 1 to
n
(
n
is greater than
1) configuration of BC, the status transitions of each copy pair might not be correctly monitored.
When using a copy pair on a remote site (a site that is not channel-connected directly from
the local host), there are the following restrictions:
Even if a copy pair status changes, the
IEA494I
message is not displayed on the MVS
console. Thus, the
YKCONMSG
command cannot monitor status transitions of a copy pair
on a remote site.
The
IOSHM0414I
message or user-specified messages are not displayed on the MVS
console even when a HyperSwap is completed. Consequently, the
YKCONMSG
command
cannot monitor the completion of HyperSwaps of a copy pair at a remote site.
When using a CAJ copy pair, even if the copy pair status changes, the
IEA494I
message
is not displayed on the MVS console. Thus, the
YKCONMSG
command cannot monitor the status
transitions of the CAJ copy pair.
The
YKCONMSG
command cannot monitor Non Gen'ed volumes.
Return Codes
Table 104 (page 194)
lists the return codes to be returned when the
YKCONMSG
command terminates.
Table 104 YKCONMSG Command Return Code List
Meaning
Return Code
The module cannot be loaded. Possible causes are as follows:
-3
The library dataset has not been linked.
APF grant has not been registered.
The module is protected by the RACF program control function.
An interruption occurred during execution.
-1
Open processing terminated normally.
0
Message specified by the
MSGID
parameter was returned (
IEA494I
message if
the
MSGID
parameter was omitted).
1
Although the system waited for the number of seconds specified for the
TIMEOUT
parameter, no message was found.
2
Message lost since previous invocation.
4
Close successful.
6
Invalid parameter.
8
System error.
9
YKDELCMD Command
Applies to CMD.
Format
YKDELCMD
{
1
SN(
storage system-serial-number
)|
1
SN(
storage system-serial-number
)
1
CU(
cu-number
)
1
CCA(
cca-number
)
1
APID(
apid
)|
1
DEVN(
device-number
)
1
APID(
apid
)}
1
MSG(
stem-name-1
)
194
CLI Commands