Details of error codes

Storage Management Software for Mainframe Messages

Version
9.8.9
Audience
anonymous
Part Number
MK-92HC227-21

This section lists the details on the storage system sense byte information (error codes) that are output to messages. If an error code not listed in this table is output, contact customer support for assistance.

The legend is as follows:

  • CMD: Command device

  • PATH: Logical path

  • HDT and HDT MF: Dynamic Tiering for Mainframe

  • HDP MF: Dynamic Provisioning for Mainframe

  • Y: Produces output

  • N: Produces no output

Table. Details of error codes 20xx - 22xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

201E

An SI copy pair cannot be resynchronized (QuickRestore) because, of the specified P-VOL and S-VOL, only one is an ESE-VOL copy pair.

Y

N

N

N

N

N

N

2026

An SI copy pair cannot be resynchronized (QuickRestore) because all of the following conditions are met:

  • System option mode 561 is ON.

  • The P-VOL and S-VOL are external volumes.

  • The P-VOL and S-VOL CacheMode settings do not match.

Y

N

N

N

N

N

N

2043

The specified SI copy pair cannot be resynchronized (ReverseCopy or QuickRestore) because the P-VOL of the SI copy pair is a UR copy pair volume for which multiple mirror IDs are defined.

Y

N

N

N

N

N

N

2044

The specified SI copy pair cannot be created because the S-VOL of the SI copy pair is a UR copy pair volume for which multiple mirror IDs are defined.

Y

N

N

N

N

N

N

204E

An SI copy pair cannot be resynchronized (QuickRestore) because Cache Residency is set for the specified P-VOL.

Y

N

N

N

N

N

N

204F

The specified SI copy pair cannot be suspended because the S-VOL of the SI copy pair is a migration-source volume and Volume Migration is currently in a state where processing cannot be stopped (COPY status). Check the status of Volume Migration in Storage Navigator or Command Control Interface, wait until the COPY status is released, and then try the suspension operation again.

Y

N

N

N

N

N

N

2054

The SI copy pair status cannot be changed because Cache Residency is set for the specified S-VOL.

Y

N

N

N

N

N

N

205E

The specified SI copy pair cannot be suspended because the P-VOL or S-VOL of the SI copy pair is a migration-source volume and Volume Migration is currently in a state where processing cannot be stopped (COPY status). Check the status of Volume Migration in Storage Navigator or Command Control Interface, wait until the COPY status is released, and then try the suspension operation again.

Y

N

N

N

N

N

N

2060

An SI copy pair cannot be created or resynchronized. The following are possible causes:

  • The SI copy pair status cannot be changed because the P-VOL has already been created as a UR copy pair.

  • The P-VOL is a journal volume.

Y

N

N

N

N

N

N

2061

An SI copy pair cannot be created. The following are possible causes:

  • The S-VOL has already been created as a UR copy pair.

  • The S-VOL is a journal volume.

Y

N

N

N

N

N

N

2067

An SI copy pair cannot be resynchronized because the specified volume is part of a TC and UR common volume configuration, and neither the TC nor UR copy pair are in the suspend status.

Y

N

N

N

N

N

N

2071

The specified SI copy pair cannot be suspended because the P-VOL of the SI copy pair is a migration-source volume and Volume Migration is currently in a state where processing cannot be stopped (COPY status). Check the status of Volume Migration in Storage Navigator or Command Control Interface, wait until the COPY status is released, and then try the suspension operation again.

Y

N

N

N

N

N

N

2078

An SI copy pair cannot be created because the status of the P-VOL for the specified SI copy pair does not meet all of the following conditions:

  • The S-VOL is part of a delta resync pair.

  • The delta resync pair is in the HOLD status.

  • A UR copy pair that is linked with the delta resync pair is in the suspend status.

Y

N

N

N

N

N

N

2079

The SI copy pair cannot be created because the specified S-VOL of SI copy pair is a part of a delta resync pair.

Y

N

N

N

N

N

N

2086

The command cannot be executed because initialization processing for the SI copy type is being performed.

Y

N

N

N

N

N

N

2089

An SI copy pair cannot be resynchronized (QuickRestore) because the P-VOL of the specified SI copy pair is being quick formatted.

Y

N

N

N

N

N

N

208A

An SI copy pair cannot be resynchronized (QuickRestore) because the S-VOL of the specified SI copy pair is being quick formatted.

Y

N

N

N

N

N

N

208C

The SI copy pair status cannot be changed because the specified S-VOL is a Mainframe Fibre Data Migration volume.

Y

N

N

N

N

N

N

2097

The SI copy pair cannot be resynchronized (QuickRestore) because the copy pair is made up of an HDP MF volume and a non-HDP MF volume.

Y

N

N

N

N

N

N

2098

An SI copy pair cannot be resynchronized (Quick Restore) because all of the following conditions are met:

  • The P-VOL of the SI copy pair is an HDP MF volume, but the S-VOL is not an HDP MF volume. Alternatively, the P-VOL of the SI copy pair is not an HDP MF volume, but the S-VOL is an HDP MF volume.

  • The P-VOL is linked with a TC copy pair or a UR copy pair.

  • The differential data of a TC copy pair or a UR copy pair is managed by the control cylinder in the volume that belongs to the TC copy pair or the UR copy pair that is linked with the P-VOL.

Y

N

N

N

N

N

N

209A

An SI copy pair cannot be resynchronized (Quick Restore) because all of the following conditions are met:

  • The P-VOL of the SI copy pair is an HDP MF volume, but the S-VOL is not an HDP MF volume. Alternatively, the P-VOL of the SI copy pair is not an HDP MF volume, but the S-VOL is an HDP MF volume.

  • The S-VOL is linked with a TC copy pair or a UR copy pair.

  • The differential data of a TC copy pair or a UR copy pair is managed by the control cylinder in the volume that belongs to the TC copy pair or the UR copy pair that is linked with the S-VOL.

Y

N

N

N

N

N

N

209E

The SI copy pair status cannot be changed because the specified P-VOL is a Mainframe Fibre Data Migration volume.

Y

N

N

N

N

N

N

20A2

A copy pair cannot be created because the HDP MF volume specified for the P-VOL of the SI copy pair is being expanded.

Y

N

N

N

N

N

N

20A3

A copy pair cannot be created because the HDP MF volume specified for the S-VOL of the SI copy pair is being expanded.

Y

N

N

N

N

N

N

20B4

A copy pair cannot be created because the HDP MF volume specified for the P-VOL of the SI copy pair is not assigned to the pool.

Y

N

N

N

N

N

N

20B5

A copy pair cannot be created because the HDP MF volume specified for the S-VOL of the SI copy pair is not assigned to the pool.

Y

N

N

N

N

N

N

20BD

A copy pair cannot be created because the P-VOL of the specified SI copy pair is an emulation type (3390-V) that is not supported.

Y

N

N

N

N

N

N

20BE

A copy pair cannot be created because the S-VOL of the specified SI copy pair is an emulation type (3390-V) that is not supported.

Y

N

N

N

N

N

N

20C5

An SI copy pair operation cannot be performed because power-off processing is in progress.

Y

N

N

N

N

N

N

20C9

If the emulation type of the P-VOL of the specified SI copy pair is 3390-A or 6588-A, a copy pair cannot be created due to one of the following causes:

  • No mainframe Fibre Channel adapter is installed.

  • All of the Mainframe Fibre Channel adapters are blocked.

Y

N

N

N

N

N

N

20CA

If the emulation type of the S-VOL of the specified SI copy pair is 3390-A or 6588-A, a copy pair cannot be created due to one of the following causes:

  • No Mainframe Fibre Channel adapter is installed.

  • All of the Mainframe Fibre Channel adapters are blocked.

Y

N

N

N

N

N

N

20D0

A copy pair cannot be created because the pool of the HDP MF volume specified for the P-VOL of the SI copy pair is being initialized.

Y

N

N

N

N

N

N

20D1

A copy pair cannot be created because the pool of the HDP MF volume specified for the S-VOL of the SI copy pair is being initialized.

Y

N

N

N

N

N

N

20D5

An SI copy pair cannot be resynchronized (QuickRestore) because the specified P-VOL is in a TC-TC Multi-Target configuration or a Cascade configuration.

Y

N

N

N

N

N

N

20D6

A copy pair cannot be created due to one of the following causes:

  • The P-VOL of the specified SI copy pair is being used for FlashCopy SE.

  • The P-VOL of the specified SI copy pair is a TSE-VOL.

Y

N

N

N

N

N

N

20D7

A copy pair cannot be created due to one of the following causes:

  • The S-VOL of the specified SI copy pair is being used for FlashCopy SE.

  • The S-VOL of the specified SI copy pair is a TSE-VOL.

Y

N

N

N

N

N

N

20D8

An SI copy pair cannot be resynchronized (QuickRestore) because the specified S-VOL is in a TC-TC Multi-Target configuration or a Cascade configuration.

Y

N

N

N

N

N

N

20E4

A copy pair with a C/T group ID cannot be created because the P-VOL of the specified SI copy pair meets both of the following conditions:

  • The P-VOL is the S-VOL of a UR copy pair.

  • The P-VOL is being used by another program product as the P-VOL of an SI copy pair with a C/T group ID.

Y

N

N

N

N

N

N

20F0

An SI copy pair operation cannot be performed, because soft fence is set for the P-VOL.

Y

N

N

N

N

N

N

20F1

An SI copy pair operation cannot be performed, because soft fence is set for the S-VOL.

Y

N

N

N

N

N

N

20F3

An SI copy pair cannot be created because NOCOPY is not supported.

Y

N

N

N

N

N

N

213E

Processing to copy an SI copy pair has been temporarily suspended, because soft fence is set for the S-VOL.

Y

N

N

N

N

N

N

22F6

An SI copy pair cannot be created because the specified P-VOL is an S-VOL for FlashCopy.

Y

N

N

N

N

N

N

22F7

An SI copy pair cannot be created because the specified S-VOL is either a P-VOL or S-VOL for FlashCopy.

Y

N

N

N

N

N

N

22F9

An SI copy pair cannot be resynchronized (by either ReverseResync or QuickRestore) because the volume is of a common volume configuration consisting of a P-VOL of SI and a P-VOL of FlashCopy.

Y

N

N

N

N

N

N

Table. Details of error codes 23xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

2301

The command cannot be executed because an SI program product was not installed.

Y

N

N

N

N

N

N

2309

An SI copy pair cannot be created or suspended. The following are possible causes:

  • The maximum number of SI copy pairs is exceeded.

  • The shared memory that can be used as Differential Tables is insufficient.

  • The shared memory that can be used as Pair Tables is insufficient.

Y

N

N

N

N

N

N

2310

An SI copy pair status cannot be changed because the status of the copy pair does not allow status transitions. The following are possible causes:

  • The combination of the request command and the status of the specified copy pair do not allow status transitions. For information on combinations, see the Hitachi ShadowImage for Mainframe User Guide.

  • The copy pairs cannot be suspended collectively because a copy pair that is not in the DUPLEX status is among the specified copy pairs.

  • The copy pairs cannot be suspended collectively because a copy pair for which transition is not possible is among the specified copy pairs.

  • An ATTIME suspend time cannot be set because a copy pair that is not in the PENDING or DUPLEX status is included in the C/T group.

  • The ATTIME suspend time cannot be set because the specified C/T group contains a copy pair that was created by using Command Control Interface to specify the SI C/T group ID.

If the reason why the copy pair status cannot be changed is not one of the above, the ATTIME suspend time cannot be set. Execute the YKSUSPND command with the CANCEL parameter specified, and then set the ATTIME suspend time again.

Y

N

N

N

N

N

N

2311

The copy pair cannot be dissolved because the copy pair is in the SIMPLEX status.

Y

N

N

N

N

N

N

2312

The command cannot be executed because the S-VOL of an SI copy pair is online.

Y

N

N

N

N

N

N

2313

An SI copy pair cannot be suspended because the copy pair is in the Split status.

Y

N

N

N

N

N

N

2314

An SI copy pair cannot be created because the copy pair is in the Split status.

Y

N

N

N

N

N

N

2316

A Volume Migration pair operation cannot be performed, because soft fence is set for the P-VOL.

Y

N

N

N

N

N

N

2317

A Volume Migration pair operation cannot be performed, because soft fence is set for the S-VOL.

Y

N

N

N

N

N

N

231B

An SI copy pair status cannot be changed. The following are possible causes:

  • The status of another copy pair that shares the P-VOL is SUSPVS.

  • There is a FlashCopy pair that shares the P-VOL.

Y

N

N

N

N

N

N

231F

An SI copy pair cannot be resynchronized because the P-VOL is online.

Y

N

N

N

N

N

N

2323

An SI copy pair cannot be resynchronized (QuickRestore) because the pool ID and CU number of the ESE-VOL of the specified P-VOL and S-VOL are not both even numbers or are not both odd numbers.

Y

N

N

N

N

N

N

232A

An SI copy pair cannot be created because the charging limit of the program product was exceeded.

Y

N

N

N

N

N

N

2331

An SI copy pair cannot be created. The following are possible causes:

  • The volume size of the P-VOL does not match that of the S-VOL.

  • The shared memory capacity is insufficient for copy pair creation.

Y

N

N

N

N

N

N

2332

An SI copy pair status cannot be transitioned because the maximum multiplicity of the copy pairs for the P-VOL was exceeded.

Y

N

N

N

N

N

N

2333

An SI copy pair cannot be suspended or dissolved because the copy pair is in the SIMPLEX status.

Y

N

N

N

N

N

N

2334

An SI copy pair cannot be created because the emulation type of the specified volume is not supported.

Y

N

N

N

N

N

N

2335

An SI copy pair cannot be created because the RAID level or emulation type of the volume is not supported.

Y

N

N

N

N

N

N

2336

An SI copy pair status cannot be changed because the combination of the drive emulation type of the P-VOL and S-VOL is not appropriate.

Y

N

N

N

N

N

N

2337

An SI copy pair status cannot be changed because the volume specified to be the P-VOL is already the S-VOL.

Y

N

N

N

N

N

N

233A

An SI copy pair cannot be resynchronized because the copy pair is in the SIMPLEX status.

Y

N

N

N

N

N

N

233F

An SI copy pair cannot be resynchronized with Reverse specified because a TC copy pair is not in the suspend status.

Y

N

N

N

N

N

N

2343

An SI copy pair status cannot be changed because the volume specified to be the S-VOL is already the S-VOL of an SI copy pair.

Y

N

N

N

N

N

N

2344

An SI copy pair status cannot be changed because the status of the copy pair does not allow status transitions. The following are possible causes:

  • The volume specified to be the S-VOL is already the P-VOL of an SI copy pair.

  • The volume specified to be the S-VOL is in the SIMPLEX status.

Y

N

N

N

N

N

N

2346

An SI copy pair status cannot be changed because the volume specified to be the S-VOL is already the P-VOL of a TC copy pair.

Y

N

N

N

N

N

N

2347

An SI copy pair status cannot be changed because the volume specified to be the S-VOL is already the S-VOL of a TC copy pair.

Y

N

N

N

N

N

N

234A

An SI copy pair status cannot be changed because the volume specified to be the S-VOL is already the P-VOL of an SI copy pair or the P-VOL for FlashCopy.

Y

N

N

N

N

N

N

2351

An SI copy pair status cannot be changed because the same volume was specified for the P-VOL and the S-VOL.

Y

N

N

N

N

N

N

2352

An SI copy pair cannot be resynchronized with Reverse or Quick specified because the P-VOL and S-VOL are online.

Y

N

N

N

N

N

N

2353

An SI copy pair cannot be dissolved because the copy pair is in the V-Split status.

Y

N

N

N

N

N

N

2354

An SI copy pair cannot be resynchronized because the copy pair is in the Pending status.

Y

N

N

N

N

N

N

2358

An SI copy pair status cannot be changed. The following are possible causes:

  • The status of another copy pair that shares the P-VOL or S-VOL is TRANS.

  • There is a FlashCopy pair that shares the P-VOL or S-VOL.

Y

N

N

N

N

N

N

235B

An SI copy pair cannot be resynchronized with Reverse or Quick specified because the P-VOL is the P-VOL of a TC copy pair that is not in the suspend status.

Y

N

N

N

N

N

N

235C

An SI copy pair cannot be resynchronized with Reverse or Quick specified because the P-VOL is the S-VOL of a TC copy pair that is not in the suspend status.

Y

N

N

N

N

N

N

235D

An SI copy pair cannot be resynchronized with Reverse or Quick specified because the S-VOL is the P-VOL of a TC copy pair that is not in the suspend status.

Y

N

N

N

N

N

N

2370

An SI copy pair status cannot be changed because the specified volume does not exist.

Y

N

N

N

N

N

N

2371

The command cannot be executed due to one of the following causes.

  • An SI copy pair cannot be created because the volume specified to be the P-VOL cannot be used or is a system residence volume.

    The volume cannot be used due to one of the following causes.

    • The P-VOL is blocked.
    • If the P-VOL is a DP volume, the pool volume for the associated pool is blocked.
    • If the P-VOL is an externally connected volume, the UVM path is disconnected.
  • An internal error occurred in the report processing for the SI copy pair status.

Y

N

N

N

N

N

N

2373

An SI copy pair status cannot be changed because the volume specified to be the P-VOL is a command device.

Y

N

N

N

N

N

N

2374

A copy pair cannot be created because the differential-data management method is different from that of another SI copy pair that shares the specified P-VOL.

Y

N

N

N

N

N

N

237B

An SI copy pair cannot be resynchronized (QuickRestore) because all of the following conditions are met:

  • The specified P-VOL is an internal volume.

  • The specified S-VOL is an external volume.

  • The specified P-VOL has a shared configuration with the P-VOL of the TC.

Y

N

N

N

N

N

N

2381

An SI copy pair cannot be created because the volume specified to be the S-VOL cannot be used or is a system residence volume.

The volume cannot be used due to one of the following causes.

  • The S-VOL is blocked.
  • If the S-VOL is a DP volume, the pool volume for the associated pool is blocked.
  • If the S-VOL is an externally connected volume, the UVM path is disconnected.

Y

N

N

N

N

N

N

2383

An SI copy pair status cannot be changed because the volume specified to be the S-VOL is a command device.

Y

N

N

N

N

N

N

2390

An SI copy pair cannot be created because the volume specified to be the P-VOL is being quick formatted.

Y

N

N

N

N

N

N

2391

An SI copy pair cannot be created because the volume specified to be the S-VOL is being quick formatted.

Y

N

N

N

N

N

N

2394

An SI copy pair cannot be created because the number of copy pairs in the specified C/T group exceeded the maximum number of copy pairs in a C/T group.

Y

N

N

N

N

N

N

2395

An SI copy pair status cannot be changed because the volume specified to be the SI P-VOL is in the Reverse Resync status with another copy pair that shares the P-VOL.

Y

N

N

N

N

N

N

2398

An SI copy pair cannot be resynchronized (including Reverse) because the copy pair is not in the Split status.

Y

N

N

N

N

N

N

2399

An SI copy pair status cannot be changed because another copy pair that shares the P-VOL or S-VOL is a FlashCopy pair or is not in the suspend status.

Y

N

N

N

N

N

N

239A

An SI copy pair cannot be resynchronized (including Reverse) because the specified P-VOL is the P-VOL of a TC copy pair.

Y

N

N

N

N

N

N

239B

An SI copy pair cannot be resynchronized (including Reverse) because the specified P-VOL is the S-VOL of a TC copy pair.

Y

N

N

N

N

N

N

239C

An SI copy pair cannot be resynchronized (including Reverse) because the specified S-VOL is the P-VOL of a TC copy pair.

Y

N

N

N

N

N

N

239D

The command cannot be executed because the specified P-VOL is protected by the LDEV guard.

Y

N

N

N

N

N

N

239E

The command cannot be executed because the specified S-VOL is protected by the LDEV guard.

Y

N

N

N

N

N

N

23A0

The command cannot be executed. The following are possible causes:

  • The specified volume is inconsistent with the volume that received the command.

  • A copy pair exists that shares the specified C/T group ID and TC S-VOL, and the ATTIME suspend function cannot be executed.

  • The ATTIME suspend function cannot be executed because the P-VOL is a Non Gen'ed volume.

Y

N

N

N

N

N

N

23B1

An SI copy pair cannot be dissolved because of one of the following causes:

  • An incorrect P-VOL or S-VOL was specified.

  • The volume specified as the P-VOL of the SI copy pair to be dissolved is already in Simplex status and is the S-VOL of a TC copy pair that is in Duplex status.

Y

N

N

N

N

N

N

23B7

An SI copy pair cannot be created because the differential-data management method is different from that of the TC copy pair with which the specified P-VOL is to be shared.

Y

N

N

N

N

N

N

23B8

An SI copy pair cannot be created because the differential-data management method is different from that of the TC copy pair with which the specified S-VOL is to be shared.

Y

N

N

N

N

N

N

23BB

An SI copy pair cannot be created because the LDEV security is set for the specified S-VOL.

Y

N

N

N

N

N

N

23BE

An SI copy pair cannot be created because the differential-data management method is different from that of the UR copy pair with which the specified P-VOL is to be shared.

Y

N

N

N

N

N

N

23BF

An SI copy pair cannot be created because the differential-data management method is different from that of the UR copy pair with which the specified S-VOL is to be shared.

Y

N

N

N

N

N

N

23EF

An SI copy pair cannot be deleted because the specified SI copy pair is in the SUSPVS status.

Y

N

N

N

N

N

N

23F1

The command cannot be executed because the specified C/T group ID is out of the valid range.

Y

N

N

N

N

N

N

23F2

The command cannot be executed. The following are possible causes:

  • The specified C/T group ID is not registered.

  • The copy pair is in the SIMPLEX status.

  • The specified C/T group contains a copy pair that was created by using Command Control Interface to specify the SI C/T group ID.

Y

N

N

N

N

N

N

23F3

The command cannot be executed because the specified ATTIME suspend time is in the past.

Y

N

N

N

N

N

N

23F4

The command used to request that the ATTIME suspend time information be acquired cannot be executed. The following are possible causes:

  • The command was issued to the P-VOL.

  • The status of the copy pair is SIMPLEX.

  • The copy pair does not belong to the C/T group.

Make sure that the command is properly issued and the copy group definition file was correctly configured.

Y

N

N

N

N

N

N

23F5

The command cannot be executed because the ATTIME suspend time is already set. If you want to change the configuration of the copy group definition file, first cancel the ATTIME suspension.

Y

N

N

N

N

N

N

23FF

An SI copy pair status cannot be changed because the specified SI copy pair status does not allow the status to be changed.

Y

N

N

N

N

N

N

Table. Details of error codes 36xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

3613

An attempt to register to EXCTG failed because the specified arbitration command device is not an arbitration command device.

N

N

Y

N

N

N

N

3614

An attempt to register to EXCTG failed. The following are possible causes:

  • The specified arbitration command device is not defined.

  • The specified arbitration command device is blocked.

N

N

Y

N

N

N

N

3616

An attempt to register to EXCTG failed because the journal group to be registered is also subject to deletion from EXCTG.

N

N

Y

N

N

N

N

3617

An attempt to register to EXCTG failed because the status is currently being changed.

N

N

Y

N

N

N

N

3618

An attempt to register to EXCTG failed because M-JNL groups and R-JNL groups co-exist within the EXCTG.

N

N

Y

N

N

N

N

3621

An attempt to register to EXCTG failed because the number of journal groups exceeded the maximum number that can be assigned to the specified arbitration command device. Retry the operation using another arbitration command device.

N

N

Y

N

N

N

N

3640

An attempt to register to EXCTG failed due to a temporary path failure. Retry the operation.

N

N

Y

N

N

N

N

3641

An attempt to register to EXCTG failed because the specified EXCTG ID, journal ID, and mirror ID are invalid.

N

N

Y

N

N

N

N

3642

An attempt to register to EXCTG failed because the journal group attribute is incorrect.

N

N

Y

N

N

N

N

3680

An attempt to register to EXCTG failed because the journal group to be registered was not found.

N

N

Y

N

N

N

N

3681

An attempt to register to EXCTG failed because the mirror ID of the journal group to be registered does not match the specified mirror ID.

N

N

Y

N

N

N

N

3682

An attempt to register to EXCTG failed because the attribute of the journal group to be registered does not match the attribute of the EXCTG.

N

N

Y

N

N

N

N

3685

An attempt to register to EXCTG failed because the specified storage system model name is invalid.

N

N

Y

N

N

N

N

3686

An attempt to register to EXCTG failed because the journal group to be registered is already registered to another EXCTG.

N

N

Y

N

N

N

N

3688

An attempt to register to EXCTG failed due to one of the following causes:

  • The mirror status of the specified journal group is neither Active nor Stop.

  • The Disaster Recovery Extended program product is not installed.

  • The specified journal group is already registered in a UR Open/MF consistency group.

  • The specified journal group is set to be used in 3DC (URxUR) configurations.

N

N

Y

N

N

N

N

3689

An attempt to register to EXCTG failed because the attribute of the journal group to be registered does not match the attribute of the EXCTG.

N

N

Y

N

N

N

N

368A

An attempt to register to EXCTG failed because the timer type of the journal group to be registered is not System.

N

N

Y

N

N

N

N

3694

An attempt to register to EXCTG failed because the combination of the serial number and device on the specified arbitration command device is incorrect.

N

N

Y

N

N

N

N

3695

An attempt to register to EXCTG failed because the journal group to be registered is an open-system journal group.

N

N

Y

N

N

N

N

Table. Details of error codes 37xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

3703

A UR copy pair cannot be resynchronized (with the PREPARE parameter specified) because the journal volume has PIN data.

N

N

Y

N

N

N

N

3704

The UR copy pair cannot be created because the emulation type for the specified M-JNL group does not match that of the R-JNL group.

N

N

Y

N

N

N

N

3705

The command for delta resync cannot be executed because the device on the S-VOL does not support the delta resync function.

N

N

Y

N

N

N

N

3706

A delta resync pair cannot be created due to one of the following causes:

  • The command target volume is the S-VOL of a TC copy pair and the copy pair status is not Duplex.

  • The configuration is a TC-TC Multi-Target configuration.

N

N

Y

N

N

N

N

3707

A delta resync cannot be executed due to one of the following causes:

  • The command target volume is the P-VOL of a TC copy pair and the copy pair status is not Duplex.

  • The command target volume is the S-VOL of a TC copy pair and the copy pair status is not SSWS.

N

N

Y

N

N

N

N

3709

The delta resync command cannot be executed because there are no UR copy pairs with a mirror ID other than the one specified for the delta resync pair in the specified R-JNL group.

N

N

Y

N

N

N

N

370B

A UR copy pair cannot be resynchronized (with the DELTAJNL parameter specified) because the specified P-VOL is not in the HOLD status or HOLDTRNS status. Alternatively, a UR copy pair cannot be resynchronized (with the ALLJNL parameter specified) because the specified P-VOL is not in the HOLD status, HOLDTRNS status, or NODELTA status.

N

N

Y

N

N

N

N

370C

A UR copy pair cannot be created or resynchronized. The following are possible causes:

  • The specified M-JNL group or R-JNL group does not allow the status to be changed.

  • The status of the specified M-JNL group or R-JNL group is currently being changed.

N

N

Y

N

N

N

N

370D

A UR copy pair cannot be resynchronized (with the PREPARE parameter specified) because the journal volume cannot be accessed.

N

N

Y

N

N

N

N

3711

A UR copy pair cannot be resynchronized (with the PREPARE parameter specified) because the journal volume is blocked.

N

N

Y

N

N

N

N

3726

A UR copy pair cannot be created because the volume specified to be the P-VOL is a system residence volume.

N

N

Y

N

N

N

N

3728

A UR copy pair cannot be created because an unsupported volume was specified when creating a copy pair between different models.

N

N

Y

N

N

N

N

3729

A UR copy pair that is to be linked with TC cannot be created because the Disaster Recovery Extended program product was not installed in the MCU.

N

N

Y

N

N

N

N

372C

A UR copy pair cannot be created or resynchronized because the P-VOL is blocked.

N

N

Y

N

N

N

N

3734

The UR copy pair cannot be recreated because the P-VOL of the UR copy pair meets both of the following conditions:

  • The P-VOL of the UR copy pair is the S-VOL for FlashCopy.

  • The P-VOL of the UR copy pair is the P-VOL of a TC copy group with a C/T group ID specified, and the TC copy pair is in the suspend status.

N

N

Y

N

N

N

N

3735

The UR copy pair cannot be recreated because the P-VOL of the UR copy pair is the S-VOL for FlashCopy and a failure might have occurred in FlashCopy.

N

N

Y

N

N

N

N

3737

A UR copy pair operation cannot be performed in a 3DC (URxUR) configuration because a UR copy pair with a different mirror ID than the specified UR copy pair is in a transitional status (Suspending or Deleting).

N

N

Y

N

N

N

N

3738

A UR copy pair cannot be created because the Disaster Recovery Extended program product was not installed in the MCU.

N

N

Y

N

N

N

N

3739

The UR copy pair cannot be created for the following causes:

  • The UR copy pair is defined with a different mirror ID.

  • The journal group that the specified S-VOL belongs to is not set to be used in a 3DC (URxUR) configuration.

N

N

Y

N

N

N

N

373D

The specified UR copy pair cannot be created in a 3DC (URxUR) configuration because the S-VOL of the UR copy pair is used in the following program products:

  • TC

  • FCV2/FCSE

  • Volume Migration

  • HDP MF pool volume

N

N

Y

N

N

N

N

373E

Operations on a UR copy pair between the primary site and the intermediate site cannot be performed in a 3DC Cascade (URxUR) configuration because the mirror status of the UR copy group between the intermediate site and the remote site is not Initial or Stop.

N

N

Y

N

N

N

N

3744

The specified UR copy pair cannot be created in a 3DC (URxUR) configuration because the P-VOL of the UR copy pair is in use by another program product.

N

N

Y

N

N

N

N

3745

A UR copy pair cannot be created between the primary site and the intermediate site in a 3DC Cascade (URxUR) configuration because the specified M-JNL is not set to be used in a 3DC (URxUR) configuration.

N

N

Y

N

N

N

N

374A

A UR copy pair cannot be created or resynchronized because the capacity of the specified P-VOL is not supported by the current microcode version.

N

N

Y

N

N

N

N

3753

A UR copy pair cannot be created in a 3DC configuration because a storage system that does not support 3DC configurations exists.

N

N

Y

N

N

N

N

3755

A UR copy pair cannot be resynchronized. The following are possible causes:

  • The specified S-VOL is already in use as an S-VOL in a UR copy pair that has another mirror ID.

  • Another UR copy pair using the specified S-VOL is not in the SWAPPING status.

N

N

Y

N

N

N

N

3756

A UR copy pair cannot be created with a value other than 0 specified for the path group ID because the secondary storage system does not support values other than 0 for path group IDs.

N

N

Y

N

N

N

N

376B

The UR copy pair cannot be created or resynchronized because the differential area is not available due to one of the following causes:

  • The shared memory area in the primary site is insufficient.

  • The HDP MF pool of the specified P-VOL is insufficient.

N

N

Y

N

N

N

N

37B8

A UR copy pair operation cannot be performed because the copy pair status of the specified S-VOL is SIMPLEX.

N

N

Y

N

N

N

N

37BB

A UR copy pair operation cannot be performed, because soft fence is set for the P-VOL.

N

N

Y

N

N

N

N

37BC

A UR copy pair operation cannot be performed, because soft fence is set for the S-VOL.

N

N

Y

N

N

N

N

37BD

A delta resync pair cannot be created, because it is in a TC-TC Multi-Target configuration.

N

Y

N

N

N

N

N

37D8

The operation cannot be performed on the UR copy pair because the differential-data management method is different from that of the SI copy pair with which the volume is to be shared.

N

N

Y

N

N

N

N

Table. Details of error codes 46xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

4600

A UR copy pair cannot be created. The following are possible causes:

  • The serial number of the primary storage system in the parameter does not match the serial number of the local storage system.

  • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system.

  • The CU number specified in the parameter is not supported.

N

N

Y

N

N

N

N

4601

A UR copy pair cannot be suspended. The following are possible causes:

  • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system.

  • The SSID for the S-VOL in the parameter does not match the SSID of the local storage system.

N

N

Y

N

N

N

N

4602

A UR copy pair cannot be resynchronized. The following are possible causes:

  • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system.

  • The SSID for the S-VOL in the parameter does not match the SSID of the local storage system.

N

N

Y

N

N

N

N

4603

A UR copy pair cannot be dissolved. The following are possible causes:

  • The SSID for the P-VOL in the parameter does not match the SSID of the local storage system.

  • The SSID for the S-VOL in the parameter does not match the SSID of the local storage system.

N

N

Y

N

N

N

N

4606

The UR copy pair status cannot be acquired because the specified CU number is unsupported.

N

N

Y

N

N

N

N

4607

A batch pair status of a UR copy pair cannot be acquired because the specified CU number is unsupported.

N

N

Y

N

N

N

N

4608

Performance information about a UR journal group cannot be acquired because the specified CU number is unsupported.

N

N

Y

N

N

N

N

460B

An attempt to register to or delete from the EXCTG failed because the specified arbitration command device number (a non-existent value), EXCTG ID, mirror ID, journal ID, or serial number is incorrect.

N

N

Y

N

N

N

N

460C

The copy pair cannot be resynchronized because the C/T group attribute defined in the copy group definition does not match the C/T group attribute set for the specified device.

N

Y

N

N

N

N

N

4612

A UR copy pair cannot be created because the specified P-VOL has already been created as a UR copy pair.

N

N

Y

N

N

N

N

4613

A UR copy pair cannot be created because the specified M-JNL group is not registered.

N

N

Y

N

N

N

N

4614

A UR copy pair cannot be created because a logical path was not established between the specified primary storage system and secondary storage system.

N

N

Y

N

N

N

N

4615

A UR copy pair status cannot be changed because the I/O execution volume and the P-VOL for the parameter do not match.

N

N

Y

N

N

N

N

4616

A UR copy pair cannot be suspended, resynchronized, or dissolved because both the specified serial number of the primary storage system and serial number of the secondary storage system do not match the serial number of the local storage system.

N

N

Y

N

N

N

N

4617

A UR copy pair cannot be suspended, resynchronized, or dissolved because the specified volume is not a UR copy pair.

N

N

Y

N

N

N

N

4618

A UR copy pair cannot be suspended because it was a suspend request with Volume and Purge specifications.

N

N

Y

N

N

N

N

4619

A TC or UR copy pair cannot be suspended with Reverse specified because the command is issued to the P-VOL.

N

Y

Y

N

N

N

N

461A

A TC or UR copy pair cannot be resynchronized with Reverse specified because the command is issued to the P-VOL.

N

Y

Y

N

N

N

N

461E

The command device cannot be defined. The following are possible causes:

  • The command device is executing a remote control command.

  • The volume is part of a TC copy pair.

N

N

N

Y

N

N

N

461F

The command device cannot be deleted. The following are possible causes:

  • The command device is executing a remote control command.

  • The volume is part of a TC copy pair.

N

N

N

Y

N

N

N

4621

The command cannot be executed because the Remote DKC Control function is not supported.

N

N

N

N

N

N

Y

4630

The command cannot be executed because the 3-site function is not supported.

N

N

N

N

N

N

Y

4633

A UR copy pair status cannot be changed because an attribute of the P-VOL or S-VOL does not match the actual volume attribute. The command might have failed because the YKQUERY command was not executed in advance.

N

N

Y

N

N

N

N

4639

The command device cannot be defined because the specified volume is a UR copy pair volume or journal volume.

N

N

N

Y

N

N

N

463C

UR ATTIME suspensions cannot be scheduled in Quick mode due to one of the following causes:

  • The storage system does not support the UR ATTIME suspend function in Quick mode.

  • The microcode of the storage system is currently being changed to one that supports the UR ATTIME suspend function in Quick mode.

N

N

N

Y

N

N

N

4645

A TC copy pair status cannot be changed because a logical path was not established between the P-VOL and S-VOL.

N

Y

N

N

N

N

N

4650

A delta resync cannot be executed because volumes are specified within the range of the operation.

N

N

Y

N

N

N

N

4651

A delta resync cannot be executed in the reversed copy direction.

N

N

Y

N

N

N

N

4660

The UR ATTIME suspend time cannot be set due to one of the following causes:

  • The specified parameter is invalid.

  • The storage system does not support the UR ATTIME suspend function in Quick mode.

N

N

Y

N

N

N

N

4661

The UR ATTIME suspend time cannot be set because shared memory is not implemented.

N

N

Y

N

N

N

N

4662

The UR ATTIME suspend time cannot be set because the specified volume is not the S-VOL of a UR copy pair.

N

N

Y

N

N

N

N

4663

The UR ATTIME suspend time cannot be set due to one of the following causes:

  • The UR copy pair is in the Simplex status.

  • The copy pair is a delta resync UR copy pair.

N

N

Y

N

N

N

N

4665

The UR ATTIME suspend time cannot be set because the timer type of the specified R-JNL group is not System.

N

N

Y

N

N

N

N

4668

The UR ATTIME suspend time cannot be set because three generations of suspend time have already been set for the specified R-JNL group.

N

N

Y

N

N

N

N

4669

The UR ATTIME suspend time cannot be set because another suspend time has already been set for the C/T group of the specified SI copy pair.

N

N

Y

N

N

N

N

466A

The UR ATTIME suspend time cannot be set. The following are possible causes:

  • The specified time is earlier than the consistency time.

  • The timer type remains Local because the UR copy pair was not resynchronized after the timer type was changed from Local to System.

When changing the timer type from Local to System, you need to suspend the UR copy pair. If the UR ATTIME suspend time has already been set, perform the following procedure to set the UR ATTIME suspend time again.

  1. Suspend the UR copy pair.

  2. Change the timer type.

  3. Resynchronize the UR copy pair.

  4. Set the UR ATTIME suspend time again.

N

N

Y

N

N

N

N

466B

The UR ATTIME suspend time cannot be set because the C/T group ID of the specified SI copy pair is incorrect.

N

N

Y

N

N

N

N

4672

The UR ATTIME suspend time cannot be set because power-off processing is in progress.

N

N

Y

N

N

N

N

4678

The UR ATTIME suspend time cannot be set due to the following causes:

  • The specified volume is not part of an SI copy pair.

  • The specified C/T group does not contain an SI copy pair that contains the specified volume.

  • The specified C/T group is not used by an SI copy pair created with BC Manager.

N

N

Y

N

N

N

N

467A

The NORMAL ATTIME suspend time cannot be set because the UR ATTIME suspend time has already been set for the specified SI C/T group.

N

N

Y

N

N

N

N

467B

The UR ATTIME suspend time cannot be set because the NORMAL ATTIME suspend time has already been set for the specified SI C/T group.

N

N

Y

N

N

N

N

467C

The UR ATTIME suspend time cannot be set because a copy pair that is not in the Duplex status is included in the specified SI C/T group.

N

N

Y

N

N

N

N

4681

An SI copy pair cannot be created, resynchronized, or suspended because the UR ATTIME suspend time was set for the specified SI C/T group.

N

N

Y

N

N

N

N

4684

The UR ATTIME suspend time cannot be set because the specified volume is currently being used in a UR Open/MF consistency group.

N

N

Y

N

N

N

N

4687

A suspension operation that cancels the SWAPPING status of the UR copy pair cannot be performed because the specified volume is not an S-VOL.

N

N

Y

N

N

N

N

46B0

LDEV operating information cannot be acquired because the parameter is invalid.

N

N

N

N

N

N

Y

46B2

MPB operating information cannot be acquired because the parameter is invalid.

N

N

N

N

N

N

Y

46B6

Parity group operating information cannot be acquired because the parameter is invalid.

N

N

N

N

N

N

Y

46B8

Port operating information cannot be acquired because the parameter is invalid.

N

N

N

N

N

N

Y

46BA

Information about the top 20 resources with the highest MP usage cannot be acquired because the parameter is invalid.

N

N

N

N

N

N

Y

Table. Details of error codes 47xx - 49xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

47A3

A TC copy pair could not be suspended by using the command with the SVOL(PERMIT) parameter specified, or by using the Reverse Resync function. The following are possible causes:

  • The size of the specified P-VOL and the size of the specified S-VOL are different.

  • (When the Reverse Resync function is used) The emulation type of the specified P-VOL and the specified S-VOL is a combination of 3390-A and a type other than 3390-A.

  • (When the Reverse Resync function is used) The emulation type of the specified P-VOL and the specified S-VOL is a combination of 6588-A and a type other than 6588-A.

  • (When the Reverse Resync function is used) The emulation type of the specified S-VOL is 3380-A, and the emulation type of the specified P-VOL is not 3380-A.

N

Y

N

N

N

N

N

47A6

A TC copy pair cannot be resynchronized with Reverse specified because the S-VOL is not suspended in the Reverse Resync status.

N

Y

N

N

N

N

N

47A7

The following suspension operations cannot be performed for the TC copy pair because the specified volume is not an S-VOL.

  • A suspension operation that reverses the copy direction

  • A suspension operation that cancels the SWAPPING status

N

Y

N

N

N

N

N

47BA

A TC copy pair cannot be created because the specified volume is the S-VOL of an SI copy pair or subject to an intervention request.

N

Y

N

N

N

N

N

4993

A TC copy pair cannot be suspended with Flush specified because the specified volume is the S-VOL.

N

Y

N

N

N

N

N

Table. Details of error codes 4Axx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

4A8B

The command cannot be executed because the status of the TC copy pair is invalid.

N

Y

N

N

N

N

N

4A8C

The command cannot be executed because the status of the TC copy pair is being changed.

N

Y

N

N

N

N

N

4A8D

The command cannot be executed because the status of the TC copy pair is invalid.

N

Y

N

N

N

N

N

4A8E

The command cannot be executed because the status of the TC copy pair is being changed.

N

Y

N

N

N

N

N

4A96

A TC copy pair cannot be created because the CLPR that the specified P-VOL belongs to does not match the one registered in the C/T group. For details on the CLPR, see the storage system documentation.

N

Y

N

N

N

N

N

4AB5

A copy pair cannot be resynchronized because it is an MTIR pair.

N

Y

N

N

N

N

N

4AB6

A copy pair cannot be resynchronized because it is an MTIR pair.

N

Y

N

N

N

N

N

4AE6

A copy pair cannot be created, because two copy pairs in a TC-TC Multi-Target configuration have already been created for the specified volume.

N

Y

N

N

N

N

N

4AF0

A path cannot be established or deleted, because soft fence is set for the specified volume.

N

N

N

N

Y

N

N

4AF1

A path cannot be deleted, because soft fence is set for the specified volume.

N

N

N

N

Y

N

N

4AF3

A TC copy pair cannot be suspended, because soft fence is set for the specified volume.

N

Y

N

N

N

N

N

4AF4

A TC copy pair cannot be dissolved, because soft fence is set for the specified volume.

N

Y

N

N

N

N

N

4AF5

A TC copy pair cannot be created, because soft fence is set for the specified volume.

N

Y

N

N

N

N

N

4AFB

A TC copy pair cannot be created because the CLPR that the specified S-VOL belongs to does not match the one registered in the C/T group. For details on the CLPR, see the storage system documentation.

N

Y

N

N

N

N

N

Table. Details of error codes 4Bxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

4B00

A TC copy pair cannot be created because the C/T group ID specified for the MCU is invalid.

N

Y

N

N

N

N

N

4B01

A TC copy pair cannot be created because the C/T group ID specified for the RCU is invalid.

N

Y

N

N

N

N

N

4B02

A copy pair cannot be resynchronized because the copy pair is in a status that cannot be changed. The following are possible causes:

  • The copy pair cannot be resynchronized because the copy group definition contains a C/T group ID, but the actual copy group does not.

  • A resynchronization cannot be performed if it changes a copy group that has a C/T group ID but does not have an Open/MF Consistency attribute to a copy group without a C/T group ID.

  • A resynchronization cannot be performed if it changes a copy group without a C/T group ID to a copy group that has a C/T group ID but does not have an Open/MF Consistency attribute.

  • The copy pair is in the SIMPLEX status.

  • In a 3DC Multi-Target (TCxTC) configuration, a resynchronization cannot be performed if it changes a copy group that has an Open/MF Consistency attribute to a copy group with no consistency group ID specified.

  • In a 3DC Multi-Target (TCxTC) configuration, a resynchronization cannot be performed if it changes a copy group with no consistency group ID specified to a copy group that has an Open/MF Consistency attribute.

N

Y

N

N

N

N

N

4B03

A copy pair that is in a TC copy group with a C/T group ID specified cannot be resynchronized because the C/T group IDs do not match.

N

Y

N

N

N

N

N

4B04

A TC copy pair cannot be created because the P-VOL is a command device.

N

Y

N

N

N

N

N

4B06

A copy pair that is in a TC copy group with a C/T group ID specified cannot be suspended because the copy pair status does not allow the status to be changed. The following are possible causes:

  • The specified volume is not in a TC copy group with a C/T group ID specified.

  • The Open/MF Consistency attribute for the specified volume does not match the copy group definition information.

  • The copy pair is in the SIMPLEX status.

N

Y

N

N

N

N

N

4B07

A copy pair that is in a TC copy group with a C/T group ID specified cannot be suspended because the C/T group IDs do not match.

N

Y

N

N

N

N

N

4B09

A copy pair that is in a TC copy group with a C/T group ID specified cannot be dissolved because the copy pair status does not allow the status to be changed. The following are possible causes:

  • The specified volume is not in a TC copy group with a C/T group ID specified.

  • The copy pair is in the SIMPLEX status.

N

Y

N

N

N

N

N

4B0A

A copy pair that is in a TC copy group with a C/T group ID specified cannot be dissolved because the C/T group IDs do not match.

N

Y

N

N

N

N

N

4B0B

RUN (releasing FREEZE) cannot be executed for a TC copy group with a C/T group ID specified because the specified copy pair is not in the FREEZE or SCP status.

This error is reported when the time specified in the TIMEOUT parameter when the YKFREEZE command is executed has passed, and when the YKRUN command is executed.

  • After executing the YKFREEZE command, confirm that a command such as the YKQUERY or YKEWAIT command that takes a long time to execute was not executed before executing the YKRUN command.

  • Confirm that the BC Manager is not in the FREEZE status because the copy group contains a system volume that is used by the OS or applications such as BC Manager for control purposes.

N

Y

N

N

N

N

N

4B0F

FREEZE cannot be executed for a copy pair that is in a TC copy group with a C/T group ID specified because the value specified for TIMEOUT is outside the valid range.

N

Y

N

N

N

N

N

4B10

FREEZE cannot be executed for a TC copy group with a C/T group ID specified because the specified volume is not the P-VOL.

N

Y

N

N

N

N

N

4B11

FREEZE cannot be executed for a copy pair that is in a TC copy group with a C/T group ID specified. The following are possible causes:

  • The specified volume is not in a TC copy group with a C/T group ID specified.

  • The specified volume is using the Open/MF Consistency Preservation function.

  • The copy pair is in the SIMPLEX status.

N

Y

N

N

N

N

N

4B14

RUN (releasing FREEZE) cannot be executed for a TC copy group with a C/T group ID specified because the specified volume is not the P-VOL.

N

Y

N

N

N

N

N

4B15

RUN (releasing FREEZE) cannot be executed for a TC copy group with a C/T group ID specified. The following are possible causes:

  • The specified volume is not in a TC copy group with a C/T group ID specified.

  • The specified volume is using the Open/MF Consistency Preservation function.

  • The copy pair is in the SIMPLEX status.

N

Y

N

N

N

N

N

4B32

A copy pair cannot be created or resynchronized because the specified P-VOL satisfies one of the following conditions:

  • The P-VOL is being used for FlashCopy.

  • The P-VOL is being used for FlashCopy SE.

  • The P-VOL is a TSE-VOL.

N

Y

N

N

N

N

N

4B35

A path cannot be set because the CU number for the specified MCU is not supported.

N

N

N

N

Y

N

N

4B36

A path cannot be set because the port number for the specified MCU is not supported.

N

N

N

N

Y

N

N

4B37

A path cannot be set because the port number for the specified RCU is not supported.

N

N

N

N

Y

N

N

4B38

A path cannot be set because the CU number for the specified RCU is not supported.

N

N

N

N

Y

N

N

4B49

The remote command cannot be executed because the path between the specified storage system or CU (SSID) and the command target storage system is not set, or an error occurred on the path.

N

N

N

N

Y

N

Y

4B85

The TC copy pair that specified a C/T group ID cannot be created because the specified volume is a FlashCopy pair.

N

Y

N

N

N

N

N

4B86

A TC copy pair cannot be created because the specified volume is a FlashCopy pair and differential-data management unit is cylinder.

N

Y

N

N

N

N

N

4BB1

A timestamp transfer mode TC copy pair cannot be created because the specified volume is not a TC copy pair.

N

Y

N

N

N

N

N

4BB2

A timestamp transfer mode TC copy pair cannot be created because the specified volume is an XRC pair.

N

Y

N

N

N

N

N

4BD1

A TC copy pair resynchronization that makes it possible to use the Open/MF Consistency Preservation function cannot be performed because the specified C/T group ID is invalid.

N

Y

N

N

N

N

N

4BD2

A TC copy pair cannot be created and resynchronized because the specified volume does not support the Open/MF Consistency Preservation function.

N

Y

N

N

N

N

N

4BDE

The specified operation cannot be performed because either the local storage system or the remote storage system does not support inter-CU logical paths.

N

N

N

N

Y

N

N

4BE0

A TC copy pair cannot be created because the necessary shared memory is not implemented in the MCU.

N

Y

N

N

N

N

N

Table. Details of error codes 50xx - 6Exx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

501C

The command device cannot be defined because the specified volume is a journal volume. Alternatively, a UR copy pair cannot be created.

N

N

Y

N

N

N

N

501F

The command timed out and could not be executed, because the storage system is under a high load.

N

N

N

N

N

N

Y

64E2

A command device cannot be deleted because the APID does not match the defined APID.

N

N

N

Y

N

N

N

64E3

The Remote DKC Control function cannot be executed because the command device is not set.

N

N

N

Y

N

N

N

64E8

A command device cannot be defined because the specified CU number is not supported.

N

N

N

Y

N

N

N

64EA

The paths between CUs, which contain command devices, are not set.

N

N

N

Y

N

N

N

64EE

The FREEZE command cannot be executed for TC copy groups with C/T group IDs because a host that does not support the FREEZE command is connected.

N

Y

N

N

N

N

N

64FA

The command cannot be executed because the host ID is invalid (not within the valid range).

N

N

N

Y

N

N

N

64FB

The command device cannot be defined due to one of the following causes:

  • The corresponding volume does not exist.

  • The corresponding volume is online.

  • The corresponding volume is a system residence volume.

  • The emulation type of the corresponding volume is 3390-V.

  • The corresponding volume is being used by another program product such as SI, TC, UR or FlashCopy.

  • The emulation type of the corresponding volume is 6588-A.

N

N

N

Y

N

N

N

64FC

The command device cannot be redefined due to one of the following causes:

  • The APID that was already defined does not match the APID you attempted to define.

  • The site type (P/L/R) that was already defined does not match the site type (P/L/R) you attempted to define.

    P site: The storage system that directly receives instructions from BC Manager

    L site: The storage system that remotely receives instructions from the storage system of the P site

    R site: The storage system that remotely receives instructions from the storage system of the L site

N

N

N

Y

N

N

N

64FD

The command device cannot be defined because a command device with the same APID was defined for another device.

N

N

N

Y

N

N

N

64FF

A command device cannot be defined because the APID specified by the parameter does not match the APID defined for the command device.

N

N

N

Y

N

N

N

69E4

A parameter error occurred. This error might occur during a storage system configuration change or operation after the microcode is changed. If this error occurs, scan the storage system by using BC Manager to obtain volume information again.

N

N

Y

N

N

N

Y

69E6

A path cannot be deleted because there is an invalid parameter.

N

N

N

N

Y

N

N

69E7

The command cannot be executed due to one of the following causes:

  • The command cannot be executed because the specified volume does not exist.

  • The Protection attribute was set by Hitachi Volume Retention Manager software.

N

N

N

N

N

N

Y

69E8

The command cannot be executed because the specified volume is blocked.

N

N

N

N

N

N

Y

69F2

A path cannot be established because there is an invalid parameter.

  • The storage system serial number is incorrect.

  • The SSID is incorrect.

  • The CU number is not supported.

N

N

N

N

Y

N

N

69F3

A copy pair cannot be created or resynchronized due to one of the following causes:

  • The storage system serial number of the P-VOL is incorrect.

  • The SSID of the P-VOL is incorrect.

  • The CU number is not supported.

  • The storage system does not support the Open/MF Consistency Preservation function.

Y

Y

N

N

N

N

N

69F5

A status cannot be changed because the specified volume is the S-VOL.

N

Y

N

N

N

N

N

69F7

A copy pair cannot be suspended due to one of the following causes:

  • The specified parameter is invalid.

  • The storage system does not support the Open/MF Consistency Preservation function.

Y

Y

N

N

N

N

N

69F8

A copy pair cannot be suspended because there is an invalid parameter.

Y

N

N

N

N

N

N

69F9

A copy pair cannot be dissolved because there is an invalid parameter.

Y

Y

N

N

N

N

N

69FB

A copy pair cannot be dissolved because the volume that received the command is an SI S-VOL.

Y

Y

N

N

N

N

N

69FF

A copy pair cannot be created because the program product necessary for the operation is not installed.

Y

Y

N

N

N

N

N

6A13

The command cannot be executed because a remote command was executed while the command device was not defined.

N

N

N

N

N

N

Y

6A14

The command cannot be executed because it was specified to be remotely executed, but this command cannot be executed as a remote command.

N

N

N

N

N

N

Y

6A16

The command cannot be executed because an instruction to delete a command device was issued for a volume that is not a command device.

N

N

N

Y

N

N

N

6A18

The command cannot be executed because an unimplemented CU number was specified when the command device was defined or deleted.

N

N

N

N

N

N

Y

6A19

The command cannot be executed because a volume that is not a command device received a remote control command.

N

N

N

N

N

N

Y

6A1E

The command cannot be executed because the APID specified by the remote command does not match the APID that was already registered.

N

N

N

Y

N

N

Y

6EC0

The setting or status acquisition command for HDT MF cannot be executed because the specified parameter is invalid.

N

N

N

N

N

Y

N

6EC1

The setting or status acquisition command cannot be executed because the command for an HDT MF contains invalid information, or a value out of range.

N

N

N

N

N

Y

N

6EC3

The setting or status acquisition command for HDT MF cannot be executed due to one of the following causes:

  • The volume or pool ID that was specified does not exist.

  • The attribute of the pool that belongs to the target device is not HDT MF.

N

N

N

N

N

Y

N

6EC4

The setting or status acquisition command for HDT MF cannot be executed due to one of the following causes:

  • The specified SSID and the SSID of the target storage system do not match.

  • The specified serial number and the serial number of the target storage system do not match.

  • The specified CU number and the CU number of the target device do not match.

  • The specified volume number and the volume number of the target device do not match.

  • The target device does not exist.

N

N

N

N

N

Y

N

6EC8

An attempt to configure the HDT MF volume failed because an internal processing error occurred in the storage system.

N

N

N

N

N

Y

N

6ECA

An attempt to configure the HDT MF pool failed because an internal processing error occurred in the storage system.

N

N

N

N

N

Y

N

6ECC

The tiering setting information and relocation status of the HDT MF volume cannot be acquired because an internal processing error occurred in the storage system.

N

N

N

N

N

Y

N

6ECE

The performance information of the HDT MF volume cannot be acquired because an internal processing error occurred in the storage system.

N

N

N

N

N

Y

N

Table. Details of error codes 7Fxx - 8Cxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

7F86

The command cannot be executed because no program product for copying is installed.

N

N

N

N

N

N

Y

7FD4

This command is not supported.

N

N

N

N

N

N

Y

8C02

The command cannot be executed because the remote device does not support the host command in the instruction to transfer data to a remote location. Alternatively, a parameter in the host command is specified incorrectly.

N

N

N

N

N

N

Y

8C12

A TC copy pair status cannot be changed. The following are possible causes:

  • The specified S-VOL is online.

  • The specified volume is a TC pair volume, or the S-VOL of an SI copy pair.

  • All paths to the RCU are blocked.

  • The status of the copy pair is not possible for the requested transition (it is possible that it is already in the requested copy pair status).

  • The logical volume of the specified volume is blocked.

  • The path between the primary site and the secondary site is in the BUSY status.

  • The emulation type of the P-VOL and the S-VOL do not match. Alternatively, the number of cylinders in the S-VOL is less than the P-VOL.

  • Either the status of the P-VOL is being changed, or there is a copy pair in the group that is having its status changed.

  • The command cannot be executed because the specified TC volume is in the SIMPLEX status.

  • The S-VOL is not in the SWAPPING status.

  • A copy pair cannot be created because the same C/T group ID is set in both the MCU and RCU.

  • The specified C/T group ID is not registered.

Alternatively, a path cannot be defined and deleted because either the copy pair status or the parameter is invalid. (The possible reasons are documented by error codes C120 through C12F.)

N

Y

N

N

Y

N

Y

8C1E

A UR copy pair cannot be created. The following are possible causes:

  • The micro version on the specified primary storage system does not support a connection with the specified secondary storage system.

  • The specified primary storage system does not support a connection with the specified secondary storage system.

N

N

Y

N

N

N

N

8CE8

The command cannot be executed because in the instruction to transfer to a remote storage system, there is an error in the parameter specification for the host command.

N

N

N

N

N

N

Y

8CE9

The command cannot be executed because the path for the Remote DKC Control function is not set.

N

N

N

N

N

N

Y

8CEB

The command cannot be executed because the path for the Remote DKC Control function is not set.

N

N

N

Y

N

N

N

8CFB

The command cannot be executed because in the instruction to transfer to a remote storage system, there is an error in the storage system serial number.

N

N

N

Y

N

N

N

8CFC

The command cannot be executed because the command device is not defined.

N

N

N

Y

N

N

N

Table. Details of error codes 8Dxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

8D00

A path cannot be established because there is an invalid parameter.

  • The storage system serial number is incorrect.

  • The SSID is incorrect.

  • The CU number is not supported.

N

N

N

N

Y

N

N

8D01

A path cannot be established because there is an invalid parameter. Alternatively, path establishment is not supported.

N

N

N

N

Y

N

N

8D09

A path cannot be deleted because there is an invalid parameter. Alternatively, path deletion is not supported.

N

N

N

N

Y

N

N

8D10

A copy pair cannot be created due to one of the following causes:

  • An inter-CU logical path was not set between the specified CUs.

  • The storage system serial number of the P-VOL is incorrect.

  • The SSID of the P-VOL is incorrect.

  • The CU number is not supported.

Y

Y

N

N

N

N

N

8D11

The command cannot be executed because the volume specified by the host command parameter is in the NOT READY status.

N

N

N

Y

N

N

N

8D12

The command cannot be executed because the logical volume of the specified volume by the host command parameter is blocked.

N

N

N

Y

N

N

N

8D14

The command cannot be executed because the SI or TC program product is not installed.

Y

Y

N

N

N

N

N

8D15

An SI copy pair cannot be created or resynchronized. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The charging limit of the program product was exceeded.

  • The copy pair is in the Pending status.

  • The copy pair is not in the Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D16

An SI copy pair cannot be created or resynchronized. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The charging limit of the program product was exceeded.

  • The copy pair is in the Pending status.

  • The copy pair is not in the Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D17

The command cannot be executed because the SI or TC program product is not installed.

Y

Y

N

N

N

N

N

8D1A

The command cannot be executed because the volume specified by the host command parameter is the S-VOL.

N

Y

N

N

N

N

N

8D1B

A status cannot be changed because the status of the specified copy pair does not match the actual status.

N

Y

N

N

N

N

N

8D1C

A TC copy pair cannot be created or resynchronized. The following are possible causes:

  • The P-VOL is a command device.

  • The specified serial number of the primary storage system or SSID does not match the storage system serial number or SSID of the local CU.

  • The specified P-VOL does not match the bootup volume.

  • The C/T group ID is incorrect.

  • The P-VOL was not created in the corresponding C/T group.

  • The S-VOL is not in the Reverse Resync status.

  • Either the C/T group ID or the C/T group timer type is incorrect.

N

Y

N

N

N

N

N

8D1D

An SI copy pair cannot be created or resynchronized. The following are possible causes:

  • The S-VOL is online.

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The P-VOL is online.

  • The charging limit of the program product was exceeded.

  • The copy pair is in the Pending status.

  • The copy pair is not in the Split status.

  • The specified C/T group ID is not registered.

  • The number of copy pairs in the specified C/T group ID exceeds the maximum number.

Y

N

N

N

N

N

N

8D1E

The serial numbers for the primary and the secondary storage systems in the host command parameter are incorrect.

N

N

N

N

N

N

Y

8D20

The host command parameter is incorrect.

Y

Y

N

N

N

N

N

8D21

The command cannot be executed because the volume specified by the host command parameter is in the NOT READY status.

N

N

N

Y

N

N

N

8D22

The command cannot be executed because the logical volume of the volume specified by the host command parameter is blocked.

N

N

N

Y

N

N

N

8D25

The command cannot be executed because the TC or SI program product is not installed.

Y

Y

N

N

N

N

N

8D26

An SI copy pair cannot be suspended. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the SIMPLEX status.

  • The copy pair is in the Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D27

An SI copy pair cannot be suspended. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the SIMPLEX status.

  • The copy pair is in the Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D28

The command cannot be executed because the copy types of the specified copy pairs do not match.

N

Y

N

N

N

N

N

8D29

A TC copy pair cannot be suspended. The following are possible causes:

  • The specified volume is in the SIMPLEX status.

  • The P-VOL number in the parameter and the bootup volume number do not match.

  • The S-VOL number in the parameter is incorrect.

  • The serial number of the primary storage system or SSID in the parameter does not match the storage system serial number or SSID of the local CU.

  • The serial number or SSID of the secondary storage system in the parameter does not match the storage system serial number or SSID of the RCU.

  • The S-VOL number in the parameter and the bootup volume number do not match.

  • The serial number or SSID of the secondary storage system in the parameter does not match the storage system serial number or SSID of the local CU.

  • The SVOL(PERMIT) or the Reverse Resync function is not supported.

  • The specified volume is the P-VOL.

  • The copy pair is already in the suspend status.

  • The S-VOL is in the Pending status.

  • The status is invalid.

  • The status of the copy pair is being changed.

N

Y

N

N

N

N

N

8D2A

An SI copy pair cannot be suspended. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the SIMPLEX status.

  • The copy pair is in the Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D2C

The serial numbers for the primary and the secondary storage systems in the host command parameter are incorrect.

N

N

N

N

Y

N

Y

8D30

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8D31

Multiple SI copy pairs cannot be suspended because there is a copy pair that does not allow status transitions in the specified copy pairs.

Y

N

N

N

N

N

N

8D38

The command cannot be executed because the specified volume is not in the SIMPLEX status.

N

N

N

Y

N

N

N

8D39

A command device cannot be defined because it does not match the APID that was already registered.

N

N

N

Y

N

N

N

8D3A

A command device cannot be defined because the specified APID is in use by another DEV.

N

N

N

Y

N

N

N

8D3D

A command device cannot be deleted because the specified volume is not a command device.

N

N

N

Y

N

N

N

8D3E

A command device cannot be made because the specified CU number is not supported.

N

N

N

Y

N

N

N

8D41

The command cannot be executed because the volume specified as the command device is already part of a copy pair, or is a journal volume.

N

N

N

Y

N

N

N

8D42

The command cannot be executed because the volume specified as a command device is a volume used in the open system.

N

N

N

Y

N

N

N

8D43

The command cannot be executed because the logical volume of the specified volume is blocked.

N

N

N

Y

N

N

N

8D44

The command cannot be executed because the specified volume has PIN data.

N

N

N

Y

N

N

N

8D45

The command device cannot be defined. The following are possible causes:

  • The corresponding volume is executing a remote control command as a command device.

  • The corresponding volume is part of a TC copy pair.

N

N

N

Y

N

N

N

8D46

The command device cannot be deleted. The following are possible causes:

  • The corresponding volume is executing a remote control command as a command device.

  • The corresponding volume is part of a TC copy pair.

N

N

N

Y

N

N

N

8D47

The command cannot be executed because the specified volume is an SI volume.

N

N

N

Y

N

N

N

8D4D

The command cannot be executed because the specified volume does not exist.

N

N

N

Y

N

N

N

8D4E

A command device cannot be defined because it does not match the APID that was already registered.

N

N

N

Y

N

N

N

8D4F

The command cannot be executed because the specified volume is online.

N

N

N

Y

N

N

N

8D50

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8D51

The command cannot be executed because the logical volume of the specified volume is blocked or the specified volume is in the NOT READY status.

N

N

N

Y

N

N

N

8D52

The command cannot be executed because the logical volume of the specified volume is blocked.

N

N

N

Y

N

N

N

8D56

An SI copy pair cannot be dissolved. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the V-Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D57

An SI copy pair cannot be dissolved. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the V-Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D58

The command cannot be executed because the copy types of the specified copy pairs do not match.

N

Y

N

N

N

N

N

8D5A

A TC copy pair cannot be dissolved. The following are possible causes:

  • The copy pair is already in the SIMPLEX status.

  • The P-VOL in the parameter and the bootup volume number do not match.

  • The S-VOL number in the parameter is incorrect.

  • The serial number or SSID of the primary storage system in the parameter does not match the storage system serial number or SSID of the local CU.

  • The serial number of the secondary storage system or SSID in the parameter does not match the storage system serial number or SSID of RCU.

  • The S-VOL number in the parameter and bootup volume number do not match.

  • The status of the copy pair is invalid.

  • The status of the copy pair is being changed.

N

Y

N

N

N

N

N

8D5B

An SI copy pair cannot be dissolved. The following are possible causes:

  • The status of the copy pair does not allow status transitions. For details, see error code 2310.

  • The copy pair is in the V-Split status.

  • The specified C/T group ID is not registered.

Y

N

N

N

N

N

N

8D70

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8D78

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8D80

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8DD1

An SI copy pair cannot be created, resynchronized, or suspended because the UR ATTIME suspend time was set for the specified SI C/T group.

Y

N

N

N

N

N

N

8DF0

The command cannot be executed because the sub-command code is incorrect.

N

N

N

N

N

N

Y

8DF1

The host command parameter is incorrect.

N

N

N

N

N

N

Y

8DF2

The command cannot be executed because the specified volume is not the P-VOL.

N

N

N

N

N

N

Y

8DF3

The command cannot be executed because the specified volume is in the NOT READY status.

N

N

N

Y

N

N

N

8DF4

The command cannot be executed because the logical volume of the specified volume is blocked.

N

N

N

Y

N

N

N

8DF5

The command cannot be executed because the SSID and CU number in the host command parameter do not match.

N

N

N

N

N

N

Y

8DF6

The command cannot be executed because the serial numbers of the host command parameter and the local storage system do not match.

N

N

N

N

N

N

Y

8DF7

The command cannot be executed because the SSID of the host command parameter and the local storage system do not match.

N

N

N

N

N

N

Y

8DFF

The command cannot be executed because the sub-command code is incorrect.

N

N

N

N

N

N

Y

Table. Details of error codes 8Fxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

8F00

A UR copy pair cannot be created because the specified volume is an external volume.

N

N

Y

N

N

N

N

8F10

A UR copy pair operation cannot be performed due to one of the following causes:

  • The specified P-VOL is the S-VOL of an SI copy pair and is not in the SUSPOP (Split) status.

  • The specified P-VOL is being used for SI and is in the Reverse Copy status.

  • The specified P-VOL is being used for FlashCopy.

N

N

Y

N

N

N

N

8F14

A UR copy pair cannot be created because the specified volume is a Reserve volume.

N

N

Y

N

N

N

N

8F17

A UR copy pair cannot be created because the specified volume is online.

N

N

Y

N

N

N

N

8F18

A UR copy pair cannot be created because the specified volume was created as a copy pair for another program product.

N

N

Y

N

N

N

N

8F19

A UR copy pair cannot be created because the emulation type of the specified volume cannot be used in UR.

N

N

Y

N

N

N

N

8F1B

A UR copy pair cannot be created because the specified P-VOL is not in the SIMPLEX status.

N

N

Y

N

N

N

N

8F1C

A UR copy pair cannot be resynchronized because the specified P-VOL is not in the suspend status.

N

N

Y

N

N

N

N

8F1E

A UR copy pair cannot be created because the cache or shared memory is being recovered.

N

N

Y

N

N

N

N

8F1F

A UR copy pair cannot be created because the cache or shared memory is blocked.

N

N

Y

N

N

N

N

8F21

A UR copy pair cannot be created. The following are possible causes:

  • The configurations cannot be combined because the specified volume is the P-VOL of a TC copy pair, or the specified volume is part of an SI copy pair.

  • 0 (zero) is specified as the mirror ID in the TC configurations.

Alternatively, a UR copy pair cannot be resynchronized because the configuration does not allow the status to be changed.

N

N

Y

N

N

N

N

8F24

A UR copy pair cannot be created because a path was not established between the devices.

N

N

Y

N

N

N

N

8F25

A UR copy pair cannot be created or resynchronized because the specified volume contains PIN data.

N

N

Y

N

N

N

N

8F28

A UR copy pair cannot be created or resynchronized because the specified P-VOL or S-VOL cannot be accessed.

N

N

Y

N

N

N

N

8F29

A UR copy pair cannot be created because the P-JNL group cannot be used.

N

N

Y

N

N

N

N

8F2A

A UR copy pair cannot be created because the specified P-VOL satisfies one of the following conditions:

  • The P-VOL is being used as the S-VOL for FlashCopy.

  • The P-VOL is being used for FlashCopy SE.

  • The P-VOL is a TSE-VOL.

N

N

Y

N

N

N

N

8F2B

A UR copy pair cannot be created because the specified P-VOL is protected by the LDEV guard.

N

N

Y

N

N

N

N

8F33

A UR copy pair cannot be created because the specified volume was created as a copy pair for another program product.

N

N

Y

N

N

N

N

8F35

A UR copy pair cannot be created or resynchronized because the specified physical volume that makes up the P-VOL is blocked.

N

N

Y

N

N

N

N

8F39

A UR copy pair cannot be created because the UR program product is not installed.

N

N

Y

N

N

N

N

8F4D

A UR copy pair cannot be created or resynchronized. The following are possible causes:

  • The R-JNL group is not registered.

  • The R-JNL volume is blocked.

  • The specified S-VOL is blocked.

N

N

Y

N

N

N

N

8F50

A UR copy pair cannot be created or resynchronized due to a heavy workload in the specified storage system. Wait 5 to 6 minutes and then execute the operation again.

N

N

Y

N

N

N

N

8F53

A UR copy pair cannot be created because the configuration does not allow status transitions. For example, the specified volume has already been created as an SI copy pair and cannot be used for this combination.

N

N

Y

N

N

N

N

8F58

A UR copy pair cannot be created or resynchronized. The following are possible causes:

  • The pair statuses of the specified S-VOL and P-VOL do not match.

  • The statuses of the R-JNL group and M-JNL group do not match.

N

N

Y

N

N

N

N

8F67

A UR copy pair cannot be created because the specified S-VOL does not support external volumes.

N

N

Y

N

N

N

N

8F6D

A UR copy pair cannot be created because the specified volume is a command device.

N

N

Y

N

N

N

N

Table. Details of error codes C0xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

C023

The specified serial number or SSID of the primary storage system does not match the storage system serial number or SSID of the local CU.

N

N

N

N

Y

N

N

C025

The command failed, because the port number specified by the host command parameter is not in the supported range or does not exist.

N

N

N

N

Y

N

N

C026

A path cannot be set because the specified CU number for the secondary site is not supported for the primary or secondary storage system.

N

N

N

N

Y

N

N

C02B

The specified P-VOL does not match the startup volume.

N

N

N

N

Y

N

N

C02C

The specified serial number or SSID of the primary storage system does not match the storage system serial number or SSID of the local CU.

N

N

N

N

Y

N

N

C032

The copy type for creating a TC copy pair is incorrect. (You can specify NOCOPY, Full Copy, or Resync only.)

N

Y

N

N

N

N

N

C048

The command cannot be executed because the specified serial number or SSID of the primary storage system does not match the storage system serial number or SSID of the local CU.

N

N

N

N

Y

N

N

C04C

The command cannot be executed because the specified serial number or SSID of the secondary storage system does not match the storage system serial number or SSID of the RCU, or the path is not registered.

N

N

N

N

Y

N

N

C04D

The command cannot be executed because the specified serial number or SSID of the secondary storage system does not match the storage system serial number or SSID of the RCU.

N

N

N

N

Y

N

N

C055

The command cannot be executed because the TC volume is in the SIMPLEX status.

N

Y

N

N

N

N

N

C058

The P-VOL number in the TC parameter does not match the bootup volume number.

N

Y

N

N

N

N

N

C059

The serial number or SSID of the primary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C05A

The serial number or SSID of the primary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C05D

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C05E

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C063

The S-VOL number in the TC parameter does not match the bootup volume number.

N

Y

N

N

N

N

N

C064

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C065

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C06A

The command cannot be executed because the TC volume is in the SIMPLEX status.

N

Y

N

N

N

N

N

C06D

The P-VOL number in the TC parameter does not match the bootup volume number.

N

Y

N

N

N

N

N

C06E

The serial number or SSID of the primary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C06F

The serial number or SSID of the primary storage system in the TC parameter does not match the storage system serial number or SSID of the local CU.

N

Y

N

N

N

N

N

C072

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C073

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C074

No TC copy pair can be created because the TC program product is not installed.

N

Y

N

N

N

N

N

C078

The S-VOL number in the TC parameter does not match the bootup volume number.

N

Y

N

N

N

N

N

C079

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C07A

The serial number or SSID of the secondary storage system in the TC parameter does not match the storage system serial number or SSID of the RCU.

N

Y

N

N

N

N

N

C0A1

The S-VOL number in the TC parameter is incorrect.

N

Y

N

N

N

N

N

C0A2

The S-VOL number in the TC parameter is incorrect.

N

Y

N

N

N

N

N

C0B6

The command cannot be executed because the specified volume is in the SIMPLEX status.

N

Y

N

N

N

N

N

C0C5

A copy pair cannot be suspended because it is already in the suspend status.

N

Y

N

N

N

N

N

C0C6

The command cannot be executed because it is already in the SIMPLEX status.

N

Y

N

N

N

N

N

C0C7

The command cannot be executed because it is already in the SIMPLEX status.

N

Y

N

N

N

N

N

C0F1

The command to suspend cannot be executed because the S-VOL for TC is in the Pending status.

N

Y

N

N

N

N

N

Table. Details of error codes C1xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

C120

An attempt to establish a path failed. The following are possible causes:

  • For an inter-CU logical path, the number of RCUs registered in the MCU exceeds 4.

  • For an inter-DKC logical path, the number of path group IDs registered in one storage system exceeds 64.

N

N

N

N

Y

N

N

C122

The command cannot be executed because the specified RCU parameter is invalid.

N

N

N

N

Y

N

N

C123

The specified RCU is not registered (the path is not established).

N

N

N

N

Y

N

N

C126

The command to delete a path cannot be executed because there is a TC or UR copy pair or journal volume in the target CU.

N

N

N

N

Y

N

N

C127

An attempt to establish or delete some of the specified paths failed. The following are possible causes:

  • The specified parameter is invalid.

  • The port or MP status is abnormal.

  • A cable is not connected properly.

  • The specified port is invalid.

N

N

N

N

Y

N

N

C128

An attempt to establish or delete all of the specified paths failed. The following are possible causes:

  • The specified parameter is invalid.

  • The port or MP status is abnormal.

  • A cable is not connected properly.

  • The specified port is invalid.

N

N

N

N

Y

N

N

C129

The command cannot be executed because the number of SSIDs registered in the RCU exceeds four.

N

N

N

N

Y

N

N

C12A

The command cannot be executed because the device-identifying code of an RCU for which path deletion is specified is invalid, or because the RCU type (FIBRE/ESCON) is invalid.

N

N

N

N

Y

N

N

C12B

The command cannot be executed because one or more paths have a different serial number.

N

N

N

N

Y

N

N

C12C

The command cannot be executed because automatic port switching cannot be performed for the specified path.

N

N

N

N

Y

N

N

C12D

The command cannot be executed because the device-identifying code of an RCU for which path registration is specified is invalid, or because the RCU type (FIBRE/ESCON) is invalid.

N

N

N

N

Y

N

N

C12E

The command cannot be executed because all CU numbers of an RCU for which path creation or deletion is specified are not the same.

N

N

N

N

Y

N

N

C12F

The command cannot be executed. The following are possible causes:

  • The specified CU number is not defined.

  • An LDEV is not defined for the specified CU number.

N

N

N

N

Y

N

N

C162

A copy pair cannot be resynchronized because the corresponding bootup pair is not in the suspend status.

N

Y

N

N

N

N

N

C184

A copy pair cannot be dissolved because an attempt to change the S-VOL status failed.

N

Y

N

N

N

N

N

C189

A TC copy pair cannot be dissolved because the copy pair status is invalid.

N

Y

N

N

N

N

N

C18A

The copy pair cannot be dissolved. The following are possible causes:

  • The status of the bootup volume is being changed.

  • There is a copy pair in the group that has a status that is being changed.

N

Y

N

N

N

N

N

C194

A copy pair cannot be suspended because the S-VOL status is being changed.

N

Y

N

N

N

N

N

C195

A copy pair cannot be suspended because the specified copy pair is already in the suspend status.

N

Y

N

N

N

N

N

C198

The command cannot be executed because no copy pairs in the group can be suspended.

N

Y

N

N

N

N

N

C199

The copy pair cannot be suspended. The following are possible causes:

  • The status of the bootup volume is being changed.

  • There is a copy pair in the group that has a status that is being changed.

N

Y

N

N

N

N

N

C1BE

A TC copy pair status cannot be changed because the storage system is being turned on.

N

Y

N

N

N

N

N

C1D1

The specified copy pair cannot be suspended, resynchronized, or deleted because a path is not set up between CUs (SSIDs) in the copy pair, or an error occurred on the path.

N

Y

N

N

N

N

N

Table. Details of error codes C2xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

C211

A copy pair cannot be created because the specified copy pair is already in the DUPLEX status.

N

Y

N

N

N

N

N

C213

The command cannot be executed because the serial number or SSID of the primary storage system for the parameter does not match the actual serial number or SSID of the primary storage system.

N

Y

N

N

N

N

N

C214

The command cannot be executed because the serial number or SSID of the secondary storage system in the parameter does not match the one already registered with the path (including ones without a path).

N

Y

N

N

N

N

N

C215

A copy pair cannot be created because the specified S-VOL is in use by another copy pair.

N

Y

N

N

N

N

N

C21A

A copy pair cannot be resynchronized because the specified copy pair is not in the suspend status.

N

Y

N

N

N

N

N

C22A

A copy pair cannot be dissolved because the status of the specified volume is SIMPLEX.

N

Y

N

N

N

N

N

C233

A copy pair cannot be resynchronized because the status of the S-VOL of the specified copy pair is SIMPLEX.

N

Y

N

N

N

N

N

C23E

A copy pair cannot be suspended because the specified copy pair is in the Pending status.

N

Y

N

N

N

N

N

C28B

The copy pair resynchronization, which causes a copy direction reversal, cannot be performed because the specified copy pair is not in the SWAPPING status.

N

Y

N

N

N

N

N

C28C

The copy pair resynchronization, which causes a copy direction reversal, cannot be performed because a path in the reverse copy direction is not set.

N

Y

N

N

N

N

N

C29A

A copy pair cannot be resynchronized because it is in a TC-TC Multi-Target configuration and the operation targets LDEV numbers whose CU numbers are 0x80 or higher.

N

Y

N

N

N

N

N

C2A0

A copy pair cannot be created because the charging limit of the MCU program product was exceeded.

N

Y

N

N

N

N

N

C2A3

A copy pair cannot be created because the charging limit of TC in the MCU was exceeded. Check the license capacity of this and all related program products.

N

Y

N

N

N

N

N

C2A8

A copy pair cannot be created because the charging limit of the RCU program product was exceeded.

N

Y

N

N

N

N

N

C2B3

A copy pair cannot be created because the HDP MF volume specified for the P-VOL is being expanded.

N

Y

N

N

N

N

N

C2B6

A copy pair cannot be created because the pages of the HDP MF volume specified for the P-VOL are being released.

N

Y

N

N

N

N

N

C2C2

A copy pair cannot be created, because two copy pairs in a TC-TC Multi-Target configuration have already been created for the specified volume.

N

Y

N

N

N

N

N

C2C6

A copy pair cannot be created, because two copy pairs in a TC-TC Multi-Target configuration have already been created for the specified volume.

N

Y

N

N

N

N

N

Table. Details of error codes C3xx - C8xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

C300

A TC copy pair that is to be linked with UR cannot be created because the Disaster Recovery Extended program product was not installed in the MCU.

N

Y

N

N

N

N

N

C301

A TC copy pair that is to be linked with UR cannot be created because the Disaster Recovery Extended program product was not installed in the RCU.

N

Y

N

N

N

N

N

C305

A copy pair cannot be created because the charging limit of TC in the RCU was exceeded. Check the license capacity of this and all related program products.

N

Y

N

N

N

N

N

C30D

The specified volume within the RCU or another volume that belongs to the same group is in transition to the SIMPLEX or suspend status. Try the operation again in a few minutes.

N

Y

N

N

N

N

N

C310

The MCU is not NVS ON.

N

Y

N

N

N

N

N

C311

The subsystem level cache of the MCU is not valid.

N

Y

N

N

N

N

N

C312

The P-VOL is not in the SIMPLEX status.

N

Y

N

N

N

N

N

C313

The P-VOL is not in the suspend status.

N

Y

N

N

N

N

N

C314

The P-VOL is not in the SIMPLEX status.

N

Y

N

N

N

N

N

C315

The P-VOL has PIN data.

N

Y

N

N

N

N

N

C316

The drive copy is being performed on the P-VOL (troubleshooting).

N

Y

N

N

N

N

N

C317

The drive copy is being performed on the P-VOL (SVP request).

N

Y

N

N

N

N

N

C318

The copy task ending process is being performed on the P-VOL.

N

Y

N

N

N

N

N

C319

The collection copy is being performed on the P-VOL.

N

Y

N

N

N

N

N

C31A

The P-VOL is in the collection access status.

N

Y

N

N

N

N

N

C31B

The logical volume of the P-VOL is blocked (PDEV blocking factor).

N

Y

N

N

N

N

N

C31C

The P-VOL cannot be accessed (because the LDEV is blocked or is in the NOT READY status).

N

Y

N

N

N

N

N

C31D

Formatting of the logical volume is being performed on the P-VOL.

N

Y

N

N

N

N

N

C31E

The P-VOL is in the READ ONLY status.

N

Y

N

N

N

N

N

C320

The logical path between the MCU and the RCU is not set (the number of paths = 0).

N

Y

N

N

N

N

N

C321

The condition setting for the number of the minimum paths between the MCU and the RCU is invalid.

N

Y

N

N

N

N

N

C322

The MCU is a storage system type that is not supported by TC.

N

Y

N

N

N

N

N

C324

The RCU sequence (number, SSID or CU) is incorrect.

N

Y

N

N

N

N

N

C325

The RCU is not NVS ON.

N

Y

N

N

N

N

N

C326

The subsystem level cache of the RCU is not valid.

N

Y

N

N

N

N

N

C327

A copy pair cannot be created because the status of the P-VOL does not permit remote copies.

N

Y

N

N

N

N

N

C328

The track format of the P-VOL and S-VOL do not match.

N

Y

N

N

N

N

N

C32A

The S-VOL is protected by LDEV security.

N

Y

N

N

N

N

N

C32B

The P-VOL is protected by LDEV security.

N

Y

N

N

N

N

N

C32C

The S-VOL is protected by LDEV guard.

N

Y

N

N

N

N

N

C32E

A copy pair cannot be created because connections with the specified S-VOL are not supported.

N

Y

N

N

N

N

N

C32F

The condition for the number of cylinders for TC volumes is incorrect (the number of cylinders in the P-VOL > the number of cylinders in the S-VOL).

N

Y

N

N

N

N

N

C330

The condition for the TC volume capacity is incorrect. (The volume capacity of the P-VOL is not the same as that of the S-VOL.)

N

Y

N

N

N

N

N

C332

The device level cache of the S-VOL is not valid.

N

Y

N

N

N

N

N

C333

The S-VOL is not DFW ON.

N

Y

N

N

N

N

N

C336

The S-VOL has PIN data.

N

Y

N

N

N

N

N

C337

The S-VOL is in the reserve status.

N

Y

N

N

N

N

N

C338

An intervention request was issued for the S-VOL (S-VOL or reserve volume of SI).

N

Y

N

N

N

N

N

C339

The S-VOL is in the FC status.

N

Y

N

N

N

N

N

C33A

A copy pair cannot be created because the specified S-VOL does not support TC.

N

Y

N

N

N

N

N

C33B

The S-VOL is an S-VOL of another copy pair.

N

Y

N

N

N

N

N

C33C

A copy pair cannot be created because the specified S-VOL is not installed.

N

Y

N

N

N

N

N

C33E

An intervention request was issued for the S-VOL (DEV NOT READY status).

N

Y

N

N

N

N

N

C33F

The S-VOL is a TC pair volume.

N

Y

N

N

N

N

N

C35C

The P-VOL cannot be accessed.

N

Y

N

N

N

N

N

C370

The condition setting for the number of the minimum paths is incorrect (path problem or invalid path).

N

Y

N

N

N

N

N

C371

Recovery processing for cache memory or shared memory is being performed. Wait a few minutes, and then try again.

N

Y

N

N

N

N

N

C372

Recovery processing for cache memory or shared memory is being performed. Wait a few minutes, and then try again.

N

Y

N

N

N

N

N

C373

A copy pair cannot be created because the specified S-VOL is a Reserve volume.

N

Y

N

N

N

N

N

C374

A copy pair cannot be created because the specified P-VOL is a Reserve volume.

N

Y

N

N

N

N

N

C378

The condition setting for the number of the minimum paths is incorrect (multiple CU number settings or path blocking issues).

N

Y

N

N

N

N

N

C379

The condition setting for the number of the minimum paths is incorrect (path problem or invalid path).

N

Y

N

N

N

N

N

C37B

A TC copy pair cannot be defined or resynchronized. The following are possible causes:

  • The S-VOL is in an unusable state.

  • The microprogram version of the MCU or RCU does not support the function or configuration.

N

Y

N

N

N

N

N

C37C

The subsystem level cache of the RCU is not valid.

N

Y

N

N

N

N

N

C37D

The RCU is not NVS ON.

N

Y

N

N

N

N

N

C37E

The device level cache of the S-VOL is not valid.

N

Y

N

N

N

N

N

C37F

The S-VOL is not DFW ON.

N

Y

N

N

N

N

N

C380

The cache for the MCU is blocked on one side (in transition).

N

Y

N

N

N

N

N

C381

The cache for the MCU is being recovered.

N

Y

N

N

N

N

N

C382

The cache for the MCU is being blocked on one side (in transition) or it is being recovered on one side.

N

Y

N

N

N

N

N

C388

A copy pair cannot be created because the P-VOL is not supported for the emulation type.

N

Y

N

N

N

N

N

C38B

The RCU is already in use by TC.

N

Y

N

N

N

N

N

C38D

A TC copy pair cannot be defined or resynchronized. The following are possible causes:

  • The S-VOL is in an unusable state.

  • The microprogram version of the MCU or RCU does not support the function or configuration.

N

Y

N

N

N

N

N

C38E

The S-VOL device is not supported by TC.

N

Y

N

N

N

N

N

C390

The S-VOL is not in the suspend status.

N

Y

N

N

N

N

N

C391

The S-VOL is in a copy pair status that does not permit copying.

N

Y

N

N

N

N

N

C392

The S-VOL is online. Alternatively, a copy pair was already created for a copy type other than TC.

N

Y

N

N

N

N

N

C393

The S-VOL has PIN data.

N

Y

N

N

N

N

N

C394

The S-VOL is online.

N

Y

N

N

N

N

N

C395

A TC copy pair cannot be created or resynchronized due to one of the following causes:

  • The specified S-VOL is blocked.

  • The physical volume that makes up the specified S-VOL is blocked.

  • The specified S-VOL is in the collection access status.

N

Y

N

N

N

N

N

C398

A copy pair cannot be created because the S-VOL is not supported for the emulation type.

N

Y

N

N

N

N

N

C39E

The P-VOL capacity exceeds the volume capacity within which a copy pair can be created.

N

Y

N

N

N

N

N

C39F

The P-VOL or S-VOL capacity exceeds the volume capacity within which a copy pair can be created.

N

Y

N

N

N

N

N

C3A0

The P-VOL device is not supported by TC.

N

Y

N

N

N

N

N

C3A4

The RCU does not support the S-VOL host online check indication function.

N

Y

N

N

N

N

N

C3A5

The S-VOL is online.

N

Y

N

N

N

N

N

C3A6

The specified SSID or CU number of the RCU is incorrect.

N

Y

N

N

N

N

N

C3A8

A copy pair cannot be created because the combination of the P-VOL and S-VOL of the specified TC copy pair is in the following status:

  • The emulation types of the specified P-VOL and S-VOL are a combination of 3390-A and a type other than 3390-A.

  • The emulation types of the specified P-VOL and S-VOL are a combination of 3380-A and a type other than 3380-A.

  • The emulation types of the specified P-VOL and S-VOL are a combination of 6588-A and a type other than 6588-A or 3390-A.

N

Y

N

N

N

N

N

C3AA

The RCU has its cache (one side) blocked (NVS).

N

Y

N

N

N

N

N

C3AB

The RCU has its cache (one side) blocked.

N

Y

N

N

N

N

N

C3AD

The RCU has exceeded the charging limit for the TC program product.

N

Y

N

N

N

N

N

C3AE

The TC program product was not installed on the RCU.

N

Y

N

N

N

N

N

C3AF

The storage system type for the RCU is not supported by TC.

N

Y

N

N

N

N

N

C3B1

The condition setting for the number of the minimum paths is incorrect.

N

Y

N

N

N

N

N

C3B6

The TC P-VOL is an SI pair volume.

N

Y

N

N

N

N

N

C3B7

The TC S-VOL is an SI pair volume.

N

Y

N

N

N

N

N

C3BA

A copy pair cannot be created because the specified SSID or CU number for the RCU is not supported for the primary and secondary site.

N

Y

N

N

N

N

N

C3BD

The P-VOL is online.

N

Y

N

N

N

N

N

C3BE

When the P-VOL of a TC copy pair is also the S-VOL of an SI copy pair, it must be in the Split status. Also, a reserve volume, a P-VOL in the Reverse Resync status, and the S-VOL for FlashCopy cannot be specified.

N

Y

N

N

N

N

N

C3BF

The S-VOL of an SI copy pair or a Reserve volume cannot be specified as the S-VOL of a TC copy pair. Also, a P-VOL in the Reverse Resync status and the S-VOL for FlashCopy cannot be specified.

N

Y

N

N

N

N

N

C3C0

When the P-VOL of a TC copy pair is also the S-VOL of an SI copy pair, both S-VOLs must be a copy pair in a one-to-one combination.

N

Y

N

N

N

N

N

C3CA

The S-VOL is in the reserve status, or the RCU, the S-VOL, or the M-R path is in the BUSY status.

N

Y

N

N

N

N

N

C3CD

The S-VOL of a TC copy pair is an SI pair volume.

N

Y

N

N

N

N

N

C3D2

The storage system type of the RCU is not supported by TC.

N

Y

N

N

N

N

N

C3D3

The specified SSID or CU number of the RCU is incorrect.

N

Y

N

N

N

N

N

C3D6

The specified S-VOL cannot be used because the device cannot be recognized from the connection port.

N

Y

N

N

N

N

N

C3D7

The status of the S-VOL in the RCU is incorrect.

N

Y

N

N

N

N

N

C3D8

A TC copy pair cannot be created because the volume specified to be the S-VOL is a system residence volume.

N

Y

N

N

N

N

N

C3D9

A copy pair cannot be created because the HDP MF volume specified for the S-VOL satisfies one of the following conditions:

  • The HDP MF volume is being used by other program product.

  • The capacity is being changed.

  • The pages are being released.

  • The pool is being initialized.

N

Y

N

N

N

N

N

C3DA

A TC copy pair cannot be created because the volume specified to be the P-VOL is a system residence volume.

N

Y

N

N

N

N

N

C3DB

The S-VOL is not in the suspend status.

N

Y

N

N

N

N

N

C410

The TC copy pair cannot be created or resynchronized due to one of or both of the following causes:

  • The S-VOL of the selected copy pair is in an extended long-busy state.

  • A timeout occurs while the local storage system and a remote storage system are communicating.

N

Y

N

N

N

N

N

C4FC

A TC copy pair cannot be created or resynchronized because the necessary shared memory is not implemented in the RCU.

N

Y

N

N

N

N

N

C825

Commands that use TC copy pairs, UR copy pairs, or the Remote DKC Control function cannot be executed because the number of executable paths is less than the minimum value.

N

Y

Y

N

N

N

Y

C8D1

The command for registering command devices via the Remote DKC Control function (YKBLDCMD) cannot be executed because the specified volume does not exist.

N

N

N

Y

N

N

N

Table. Details of error codes CBxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

CB1D

A dummy volume cannot be created on the S-VOL.

N

Y

N

N

N

N

N

CB1F

The current RCU version does not support Fibre TC.

N

Y

N

N

N

N

N

CB60

Fibre TC was not installed on the RCU.

N

Y

N

N

N

N

N

CB62

Copy pairs with Fibre and ESCON paths cannot exist within the same storage system.

N

Y

N

N

N

N

N

CB64

The storage system type of the MCU is not supported (the type is not 3990-6/6E, or it is 2105).

N

Y

N

N

N

N

N

CB66

A TC copy pair cannot be created because the differential area is not available due to one of the following causes:

  • The shared memory area in the secondary site is insufficient.

  • The HDP MF pool of the volume specified for the S-VOL is insufficient.

N

Y

N

N

N

N

N

CB67

A TC copy pair cannot be created because extended shared memory is not implemented in the RCU.

N

Y

N

N

N

N

N

CB68

A TC copy pair cannot be created because the differential area is not available due to insufficient shared memory area in the primary site.

N

Y

N

N

N

N

N

CB6E

A TC copy pair operation cannot be performed, because soft fence is set for the P-VOL.

N

Y

N

N

N

N

N

CB6F

A TC copy pair operation cannot be performed, because soft fence is set for the S-VOL.

N

Y

N

N

N

N

N

CB78

A copy pair cannot be created because the specified S-VOL is defined as a command device.

N

Y

N

N

N

N

N

CB7E

A TC copy pair cannot be created because the CLPR that the specified S-VOL belongs to does not match the one registered in the C/T group. For details on the CLPR, see the storage system documentation.

N

Y

N

N

N

N

N

CB9E

A copy pair cannot be created because the specified S-VOL does not support either one or both of the following:

  • The timestamp transfer mode

  • The Open/MF Consistency Preservation function

N

Y

N

N

N

N

N

CBD8

A copy pair cannot be created because the specified P-VOL is not a P-VOL for UR.

N

Y

N

N

N

N

N

CBD9

A copy pair cannot be created because the specified S-VOL satisfies one of the following conditions:

  • The S-VOL is being used for FlashCopy.

  • The S-VOL is being used for FlashCopy SE.

  • The S-VOL is a TSE-VOL.

N

Y

N

N

N

N

N

CBDC

A TC copy pair cannot be created because the mirror ID of UR is 0 when linked with UR.

N

Y

N

N

N

N

N

CBDD

A TC copy pair cannot be created because a UR copy pair is being copied in a TC-UR Multi-Target configuration.

N

Y

N

N

N

N

N

CBE2

A copy pair cannot be created because the specified P-VOL is a pool volume.

N

Y

N

N

N

N

N

CBE3

A copy pair cannot be created because the specified S-VOL is a pool volume.

N

Y

N

N

N

N

N

CBED

A TC copy pair cannot be created due to one of the following causes:

  • The specified S-VOL is the P-VOL or S-VOL of a UR copy pair.

  • The specified S-VOL is a journal volume.

N

Y

N

N

N

N

N

CBEE

A TC copy pair cannot be created due to one of the following causes:

  • The specified P-VOL is already created as a P-VOL in a delta resync UR copy pair.

  • The specified P-VOL is created as a P-VOL in a copy pair in a 3DC Multi-Target (URxUR) configuration.

N

Y

N

N

N

N

N

CBF8

A TC copy pair cannot be created due to one of the following causes:

  • The MCU or RCU microcode version does not support the connection.

  • The MCU or RCU model does not support the connection.

  • This RCU model does not support differential-data management by cylinders.

N

Y

N

N

N

N

N

CBFA

A TC copy pair operation cannot be performed due to one of the following causes:

  • No Mainframe Fibre Channel adapter is installed.

  • All of the Mainframe Fibre Channel adapters are blocked.

N

Y

N

N

N

N

N

CBFC

A TC copy pair cannot be created or resynchronized because the C/T group ID is not in the supported range.

N

Y

N

N

N

N

N

Table. Details of error codes DBxx - E8xx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

DB02

A UR copy pair status cannot be changed because status transitions are not allowed.

In the following examples, status transitions are not allowed:

  • When an attempt to create a copy pair is made for a copy pair that is not in the SIMPLEX status.

  • When an attempt to re-create a copy pair is made for a copy pair that is not in the suspend status.

Check the status of the copy pair again because there is a possibility that the status transition was performed correctly.

N

N

Y

N

N

N

N

DB03

A UR copy pair status cannot be changed because the copy pair status is being changed (Suspending or Deleting).

N

N

Y

N

N

N

N

DB07

A UR copy pair status cannot be changed because the power-on process is in progress.

N

N

Y

N

N

N

N

DB08

A UR copy pair status cannot be changed because the power-off process is in progress.

N

N

Y

N

N

N

N

DB0C

A UR copy pair cannot be resynchronized (with the DELTAJNL parameter or ALLJNL parameter specified) because the volume is specified.

N

N

Y

N

N

N

N

E80B

An attempt to register to EXCTG failed because the expanded shared memory table necessary for the EXCTG registration was not initialized.

N

N

Y

N

N

N

N

E826

An attempt to delete from EXCTG failed because the specified EXCTG is not registered.

N

N

Y

N

N

N

N

E82F

An attempt to delete from EXCTG failed because the specified journal group is not registered.

N

N

Y

N

N

N

N

E843

A UR copy pair cannot be created because the CLPR number of the specified volume and the CLPR number of the journal group do not match.

N

N

Y

N

N

N

N

E869

A UR copy pair cannot be resynchronized because the following conditions are met:

  • The R-JNL of the specified UR copy pair is being used by a UR copy pair that has another mirror ID.

  • The mirror status of another UR copy pair that is using the specified UR copy pair is Halting or Stopping.

N

N

Y

N

N

N

N

E86B

A UR copy pair cannot be dissolved because the specified volume is not a UR copy pair.

N

N

Y

N

N

N

N

E86D

A UR copy pair cannot be dissolved because the storage system is being turned on.

N

N

Y

N

N

N

N

E86E

A UR copy pair cannot be created because the SM of a specified volume is not implemented.

N

N

Y

N

N

N

N

E871

A UR copy pair cannot be created because inter-DKC logical paths (for both directions) have not been defined. Make sure that inter-DKC logical paths have already been established in both directions.

N

N

Y

N

N

N

N

E876

A UR copy pair cannot be created because the storage system serial number specified for the S-VOL is invalid.

N

N

Y

N

N

N

N

E878

A UR copy pair cannot be created because there is mix of volumes with emulation types (3390-9A and non-3390-9A) in the specified journal group.

N

N

Y

N

N

N

N

E87B

A UR copy pair cannot be created because the specified journal group is not registered.

N

N

Y

N

N

N

N

E87C

A UR copy pair cannot be created because a journal volume is not registered in the specified journal group.

N

N

Y

N

N

N

N

E87D

A UR copy pair cannot be resynchronized because the specified volume is not a UR copy pair.

N

N

Y

N

N

N

N

E87E

A UR copy pair cannot be created because the specified P-VOL or S-VOL is a volume comprising a journal group.

N

N

Y

N

N

N

N

E880

A UR copy pair cannot be created because the emulation type for the specified P-VOL or S-VOL does not match the emulation type for a volume comprising a journal group.

N

N

Y

N

N

N

N

E881

A UR copy pair cannot be created or resynchronized because the storage system is being turned on.

N

N

Y

N

N

N

N

E882

A UR copy pair cannot be created because the emulation type for the volumes comprising the specified M-JNL group does not match that of the R-JNL group.

N

N

Y

N

N

N

N

E885

A UR copy pair cannot be created because the specified R-JNL group has already been created as a copy pair with another M-JNL group.

N

N

Y

N

N

N

N

E888

A UR copy pair cannot be created because the specified M-JNL group has already been created as a copy pair with another R-JNL group.

N

N

Y

N

N

N

N

E889

A UR copy pair cannot be created because the specified journal group has already been created as a UR copy pair by using another mirror ID.

N

N

Y

N

N

N

N

E890

A UR copy pair cannot be created due to one of the following causes:

  • The specified volume is already registered in another journal group.

  • The specified volume is already registered in the same journal group by using the same mirror ID.

  • The specified S-VOL is already registered in the same journal group by using another mirror ID.

  • The specified journal group is not set to be used in a 3DC (URxUR) configuration, but there is a copy pair that has another mirror ID in the journal group.

N

N

Y

N

N

N

N

E891

A UR copy pair cannot be created because the maximum number of copy pairs has already been registered in the specified M-JNL or R-JNL group.

N

N

Y

N

N

N

N

E894

A UR copy pair cannot be created in a 3DC (URxUR) configuration because the third mirror ID is specified in the same journal group.

N

N

Y

N

N

N

N

E896

An attempt to register to EXCTG failed because the UR program product or the Disaster Recovery Extended program product was not installed.

N

N

Y

N

N

N

N

E897

A UR copy pair cannot be created due to one of the following causes:

  • The specified M-JNL and R-JNL groups are not set to be used in 3DC (URxUR) configurations.

  • The specified R-JNL group is already in use.

  • Another mirror ID is already defined for the specified journal group.

N

N

Y

N

N

N

N

E898

A UR copy pair cannot be resynchronized because the specified R-JNL group is in use as an R-JNL group for a UR copy pair with another mirror ID.

N

N

Y

N

N

N

N

E89A

A UR copy pair cannot be created because an inter-DKC logical path was not established in the forward or reverse direction. Make sure that inter-DKC logical paths have already been established in both directions.

N

N

Y

N

N

N

N

E89B

A UR copy pair cannot be created because the status from the previous connection with another storage system remains in the specified M-JNL or R-JNL group.

Specify a different journal group or delete the specified journal group, and then register it again.

N

N

Y

N

N

N

N

E8A2

A UR copy pair cannot be created due to one of the following causes:

  • The serial number of the storage system specified for the S-VOL is incorrect.

  • Another path group ID is already assigned for the specified journal group.

N

N

Y

N

N

N

N

E8A6

A resynchronization that reverses the copy direction for UR copy pairs cannot be performed because the journal group of the specified volume is not registered in the storage system.

N

N

Y

N

N

N

N

E8A7

A resynchronization that reverses the copy direction for UR copy pairs cannot be performed because a journal volume is not registered in the storage system for the journal group of the specified volume.

N

N

Y

N

N

N

N

E8A8

The specified copy pair cannot be suspended because it is not a UR copy pair, or the P-VOL and S-VOL for journal group do not match.

N

N

Y

N

N

N

N

E8A9

A UR copy pair cannot be suspended because the storage system is being turned on.

N

N

Y

N

N

N

N

E8B6

A delta resync pair cannot be created because the mirror ID of the specified R-JNL group is used by another UR copy pair.

N

N

Y

N

N

N

N

E8B9

A delta resync pair cannot be created because the specified journal group is registered to EXCTG.

N

N

Y

N

N

N

N

E8BB

An attempt to register to EXCTG failed because the mirror ID does not match the registered mirror ID.

N

N

Y

N

N

N

N

E8BD

An attempt to register to EXCTG failed because the number of journal groups to be registered exceeded the maximum number that can be registered.

N

N

Y

N

N

N

N

E8BF

An attempt to register to EXCTG failed because the number of subordinate storage systems has exceeded the maximum number that can be registered.

N

N

Y

N

N

N

N

Table. Details of error codes EAxx

Error code

Error details

Type of error

SI

TC

UR

CMD

PATH

HDT

Other

EA00

A UR copy pair cannot be created because the specified volume comprises an R-JNL group.

N

N

Y

N

N

N

N

EA01

A UR copy pair cannot be created because the specified P-VOL or S-VOL is already in use by another UR copy pair.

N

N

Y

N

N

N

N

EA02

A UR copy pair cannot be created because the specified volume comprises an M-JNL group.

N

N

Y

N

N

N

N

EA03

A UR copy pair cannot be created because the specified S-VOL is already in use as another UR copy pair.

N

N

Y

N

N

N

N

EA07

A UR copy pair cannot be created because the number of copy pairs that can be registered in the specified M-JNL group has exceeded the maximum limit.

N

N

Y

N

N

N

N

EA08

A UR copy pair cannot be created because the number of copy pairs that can be registered in the specified R-JNL group has exceeded the maximum limit.

N

N

Y

N

N

N

N

EA09

A UR copy pair cannot be created because the M-JNL group is not in the Initial, Active, or Stop status.

N

N

Y

N

N

N

N

EA0A

A UR copy pair cannot be created because the status of the R-JNL group is incorrect.

N

N

Y

N

N

N

N

EA12

The UR copy pair cannot be resynchronized in the reverse direction because the copy pair is not in the SWAPPING status.

N

N

Y

N

N

N

N

EA13

A UR copy pair cannot be resynchronized because the volume specified for the P-VOL is the S-VOL of the UR copy pair.

N

N

Y

N

N

N

N

EA15

A UR copy pair cannot be resynchronized because the volume specified for the S-VOL is the P-VOL of the UR copy pair.

N

N

Y

N

N

N

N

EA18

A UR copy pair cannot be resynchronized because the copy pair is not in the suspend status.

N

N

Y

N

N

N

N

EA19

A UR copy pair cannot be resynchronized because the journal group is not in the Stop status.

N

N

Y

N

N

N

N

EA1B

The YKRESYNC command with the PREPARE parameter specified cannot be executed because the specified journal group is either not in the suspend status to obtain the journal data as differential data, or it is not in the failure status.

N

N

Y

N

N

N

N

EA1C

A UR copy pair resynchronization, which causes a copy direction reversal, cannot be performed because the R-JNL group of the S-VOL is not in the Stop status.

N

N

Y

N

N

N

N

EA1E

A resynchronization that reverses the copy direction for UR copy pairs cannot be performed because the specified S-VOL is not the S-VOL of the UR copy pair.

N

N

Y

N

N

N

N

EA20

A resynchronization that reverses the copy direction for UR copy pairs cannot be performed because the specified P-VOL is not the P-VOL of the UR copy pair.

N

N

Y

N

N

N

N

EA22

A UR copy pair resynchronization, which causes a copy direction reversal, cannot be performed because the journal group is not in the Stop status.

N

N

Y

N

N

N

N

EA25

A UR copy pair resynchronization, which causes a copy direction reversal, cannot be performed because the copy pair is not in the SWAPPING status.

N

N

Y

N

N

N

N

EA29

A UR copy pair cannot be dissolved because the M-JNL group is not in the Active or Stop status.

N

N

Y

N

N

N

N

EA2C

A UR copy pair cannot be dissolved because the R-JNL group is not in the Active or Stop status.

N

N

Y

N

N

N

N

EA33

A UR copy pair cannot be suspended because the M-JNL group is not in the Active status.

N

N

Y

N

N

N

N

EA36

A UR copy pair cannot be suspended because the R-JNL group is not in the Active status.

N

N

Y

N

N

N

N

EA3A

A UR copy pair cannot be dissolved because the specified S-VOL status is currently being changed.

N

N

Y

N

N

N

N

EA3B

A UR copy pair resynchronization, which causes a copy direction reversal, cannot be performed because the copy pair is in the TRANS status.

N

N

Y

N

N

N

N

EA3C

A suspension that reverses the copy direction cannot be performed for the UR copy pair because the specified S-VOL belongs to the M-JNL group.

N

N

Y

N

N

N

N

EA40

A UR copy pair cannot be created because the charging limit of the MCU program product was exceeded.

N

N

Y

N

N

N

N

EA41

A UR copy pair cannot be created because the charging limit of the RCU program product was exceeded.

N

N

Y

N

N

N

N

EA46

A UR copy pair between the intermediate site and the remote site cannot be deleted or suspended because the journal group of the UR copy pair between the primary site and the intermediate site in a 3DC Cascade (URxUR) configuration is in the Active status.

N

N

Y

N

N

N

N

EA4D

The UR copy pair cannot be suspended because it is a delta resync pair.

N

N

Y

N

N

N

N

EA89

The status cannot be changed from the error status to the delta resync preparatory status because the specified P-VOL is not in the HOLDER status.

N

N

Y

N

N

N

N

EA8A

The status of a UR copy pair cannot be changed because the primary storage system is currently being turned on or turned off.

N

N

<