Errors involving locked types or checked-out files

You can restart the relocatecommand after errors caused by locked types or checked-out files. When you encounter one of these errors:

  1. Stop and fix the problem. For example, if a type in the target VOB is locked, unlock it. If it a version in the relocate set is checked out, resolve the checkout.
  2. Restart relocate. When started with an identical command line, therelocate command resumes processing from the interrupt point if all of these conditions are met:
    • You have not released source VOB element locks that the relocate command sets automatically.
    • No user has modified the source elements (new checked-in versions, new labels, and so on).
    • (–qall only) You answer all relocate this object? queries the same way.

    If any of these conditions is not met, relocate starts processing from the beginning.

Parent topic: Handling errors during a relocate operation
Feedback