Restarting jobs

If a reorganization fails, BMC AMI Reorg requires only that you resubmit the job. You do not need to make changes. BMC AMI Reorg determines that the prior execution terminated prematurely and resumes processing.

Serialization and concurrency

To prevent two incompatible utilities from executing on the same object concurrently, BMC AMI Reorg uses the following mechanisms:

• An internal matrix of utility IDs and processing objects

• The common BMC utility tables, BMCSYNC and BMCUTIL.

It is often necessary to address a previously failed utility ID before running a utility with a different utility ID on the same object. You can run the previous utility with a RESTART or with QUICKEXIT to clean up temporary files. If the utility is in a "must complete" state and a QUICKEXIT is run, the utility simply completes. BMC AMI Reorg ensures that no damage occurs by resubmitting. BMC AMI Reorg always runs with the object in RW status and leaves the original table space and indexes untouched until the reorganization is complete. For more information, see Concurrent-access-control.

Utility ID considerations

BMC AMI Reorg accepts 16 characters or less in the utility ID as part of the PARM field on the JCL EXEC statement.

If BMC AMI Reorg determines that a prior job using this same utility ID ended prematurely, then the current job proceeds as follows:

• If no restart option is specified, processing resumes from the most recent successful checkpoint, which is typically the last completed table space or partition.
• If a restart option is specified, then:
  • If your choice is feasible for the reorganization, processing proceeds as dictated.
  • If the restart option is incompatible with the reorganization, then processing stops.

The key to this process is the utility ID. Note the following considerations:

• BMC AMI Reorg resumes the reorganization of the original set of objects. If you change the control statements before resubmitting the utility, the new statements are ignored.
• Two BMC AMI Reorg steps using the same utility ID in different jobs cannot run concurrently. This can happen when two steps appear in inadvertent duplicates of the same job or in unrelated jobs that use the same utility ID. The second step to begin execution fails.

The checkpoint data set

Every execution of BMC AMI Reorg requires access to a linear VSAM data set named during the installation procedure and configured with the NGTCKPT parameter or the //NGTCKPT DD statement. This checkpoint data set (NGTCKPT) contains all the restart information for utilities.

The checkpoint data set includes the following information:

• The list of objects to be reorganized and the status of each
• The internal tables required for restart
• The list of objects being renamed
• The RUNSTATS values

For more information about the checkpoint data set, see Maintaining the BMC AMI Utilities checkpoint data set.

Utility in a Must Complete state

BMC AMI Reorg fails with a return code 16 and leave the Utility ID (UID) in a Must Complete state. This usually occurs when the Reorg phase is complete and posted to Db2 and a failure occurred while writing the copy data set from the utilities internal work file to the users copy data set. This can occur for multiple reasons, primarily if the user’s copy data set name is invalid or if there was a space allocation issue. The user must refer to the SYSERROR and address the issue and RESTART the utility. 

BMC AMI Reorg can also end with an object in a Must Complete state due to errors during the narrow window for fastswitch/rename. In this case, no action is required other than a RESTART or QUICKEXIT of the UID.

BMC AMI Utilities have three options for the restart parameter when restarting the UID.

1. RESTART–Restart the UID and process any incomplete or failed objects including any object that is in a Must Compete state.
2. QUICKEXIT – Back out failed objects and complete any object that in a Must Complete state before starting a new job.
3. NORESTART – You cannot use this option if UID is in a Must Complete state and this produces an error message in SYSERROR.