Default language.

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Load for Db2 13.1.

Restarting jobs (for BMC AMI Load)

If a job fails, the correct method of recovery depends on the type of job that you are running.


Recovery methods

Type of job

Recovery method

Restart the job from the last commit point during the failed load

You do not need to perform recovery. Instead, perform one of the following steps:

  • Use the QUICKEXIT parameter on the EXEC card to terminate the utility.The table space becomes available without the new data.
  • Use the RESTART parameter on the EXEC card to continue the load process.

Restart the job. If the table space was not empty, it will be available in read/write status.

Recover by using one of the following options:

If you are loading a partitioned table space and have a mixture of RESUME YES and REPLACE on the INTO statement

Perform one of the following steps:

  • Use the QUICKEXIT parameter on the EXEC card to terminate the utility.Partitions with a RESUME YES specification are restored to their original status. Partitions with a REPLACE specification must be recovered.
  • Restart the job.Partitions with a RESUME YES specification are restored to their original status and the job starts from the beginning.

Utility in a Must Complete state

BMC AMI Load can fail with a return code 16 and leave the UID in a Must Complete state. You can safely use LOAD RESUME SHRLEVEL NONE. If an error occurs, running QUICKEXIT leaves the object as it was before the error, avoiding the need to recover the object.  The failure leaves the UID in a Must Complete state which leaves you with the option to RESTART or QUICKEXIT. If you specify +CLEANUP(YES,rc), the Must Complete state and the RC=16 is avoided and the UID is cleaned by itself and ends with the rc that you requested. If you did not specify any rc, then it ends with rc=4. We recommend +CLEANUP(YES, RC).

When BMC AMI Load has errant records to discard and discarding is allowed, the load phase can complete, but a space issue can prevent the discards from being written to the user’s data set. In this case the UID is in a Must Complete state and upon RESTART or QUICKEXIT, the discards are written. An advantage of BMC AMI Utilities is that any restrictive state from the load is released before the discard phase. Although the UID is Must Complete, the Db2 objects are online and available and the UID no longer needs access to them to restart and complete the job.

Important

The restarted UID must have the SYSREC file available to obtain the records to discard.

(SPE2104) 

If a BMC AMI Load UID is in a Must Complete state because of an error in the discarding phase, you can run QUICKEXIT without the original SYSREC file. Running QUICKEXIT is accepted as a request to clean up the UID without writing the discards that were originally requested.

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

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


Related topics

RESUME-INTO-TABLE-option

Restart-limitations



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*