Restarting catalog and directory copy jobs

Under this scenario, BMC AMI Copy fails and cannot restart without manual intervention. BMC AMI Copy issues messages BMC30125 and BMC47309, and you must perform the following steps before restarting:

1. Wait for the status of the space to change from stop pending (STOPP) to stopped (STOP) (per message BMC47310). Use the Db2 -DISPLAY DATABASE command to monitor the status.

2. After the space has stopped, proceed as follows:

   • If the space is DSNDB01.SCT02, issue the following Db2 command with ACCESS(RO) if you are planning to restart the utility:

     -START DATABASE(DSNDB01) SPACENAM(SCT02)

     If you are planning to start the utility over, start the space in its original status. Performing this step allows BMC AMI Copy to access the Db2 plan to read the BMCUTIL table that contains the restart information.

   • If the space is DSNDB06.SYSDBAUT, DSNDB06.SYSGPAUT, or DSNDB06.SYSUSER, you must do one of the following:
     • If you are planning to restart the utility, issue the Db2 -START command for database DSNDB06 and space SYSDBAUT, SYSGPAUT, or SYSUSER (as appropriate) with ACCESS(RO). If you are planning to start the utility over, start the space in its original status.
     • Use an authorization ID that includes installation SYSADM or installation SYSOPR authority under the primary ID.

   Performing this step allows Db2 to check the authorization of the BMC AMI Copy user when BMC AMI Copy issues SQL statements or Db2 commands.

3. Restart the utility from the beginning or point of failure, as required. For more information, see Restarting-a-failed-BMC-AMI-Copy-job.
4. Consider using RESETMOD NO in the future to avoid -STOP command failure issues. For more information, see RESETMOD.