General troubleshooting

True Copy for Mainframe User Guide for VSP One Block 85
Version
10.5.x
File Size
2745 KB
Audience
anonymous
Part Number
MK-26VSP1B036-02
ft:lastEdition
2026-06-23

The following table lists general error conditions and provides recommended action for each condition.

Error

Corrective action

TrueCopy operations do not function properly.

  • Make sure that all TrueCopy for Mainframe requirements and restrictions are met (for example, Track format, LVI, VOLSER, DFW).
  • Make sure that the primary and secondary systems are powered on and fully operational (NVS, cache, DFW).
  • Make sure that all values ​​and parameters you have entered are correct, and then run the raidcom get rcu, raidcom get ldev, or pairdisplay command, or verify the contents of the configuration definition file to check the serial number, ID, path parameters, P-VOL ID, S-VOL ID, and so on of the remote storage system.

An initiator channel-enabled LED indicator (on the storage system control panel) is off or flashing.

Contact customer support.

The pairs or paths to the remote storage system are not displaying correctly.

Make sure that the correct CU is selected.

A TrueCopy for Mainframe error message is displayed on the computer Resolve the error, and then try the TrueCopy for Mainframe operation again.

There is a problem with TrueCopy for Mainframe software.

Try restarting the computer and reconnecting to the storage system.

The status of the path to the remote storage system is not normal.

Check the path status, and see Remote path status problems.

Pair status is Suspend (pair suspended-error).

See Split pair problems.

A pair cannot be created or resynchronized. Check if the controller board is blocked on the primary storage system or the secondary storage system. Restore the blocked controller board, and then retry the operation.
The pair status remains unchanged as follows when creating a pair or resynchronizing a pair:
  • The pair status remains COPY.
  • The pair resynchronization rate remains 0%.
  • If a hardware failure occurs, a SIM is generated. Contact customer support, and retry TrueCopy for Mainframe operations after the problem is resolved.
  • If no hardware failure occurs but the processing load is high, retry TrueCopy for Mainframe operations when the processing load on the storage system is low.
  • If the pair status remains unchanged when no hardware failure occurs (no SIM is generated) and the processing load is low, contact customer support.
  • If the pair status remains unchanged when no hardware failure occurs (no SIM is generated) and the processing load is low, contact customer support.
The pair information remains on the volume after trying to delete the pair, even if the pair is not created using the volume.

The pair information remaining means that the volume cannot be used as a volume of a different pair.

 If the pair cannot be deleted or if the pair remains when the pair status is verified after the pair deletion, perform the following procedure:
  1. Retry the normal pair deletion according to the following conditions:
    • If the pair to be deleted remains on both of the primary and secondary storage systems, perform the normal pair deletion on the primary storage system first.
    • If the pair to be deleted remains on either of the primary and secondary storage systems, perform the normal pair deletion on the storage system on which the pair remains.
  2. Verify the pair status.
    • If the pair has been successfully deleted, skip this step.
    • If the normal pair deletion cannot be performed or the pair status remains, perform the forced deletion of the remaining pair. See Forcibly deleting pairs.