Resetting the Async Jobs (RBJC)

Purpose: Use this menu option if there is an error occurred with the background job asyncs and the asyncs require a reset.

Before you run the async reset: Before you run the async reset, make sure that the async jobs are NOT running. Use the Display Active Batch Jobs Screen to verify that the jobs are not running. If the async jobs do not display on this screen, they are not running.

If the async job is not running, but still displays on the Job Management Screen in a RUN, MSG, or END status, you can select Remove for the job to remove it from the screen.

Reset ASYNCs Screen

How to display this screen: Enter RBJC in the Fast path field or select Reset ASYNC Jobs from a menu.

Running the Async Reset

At the Reset ASYNCs Screen, select OK to submit the reset async job.

The reset asyncs job:

• Updates the status of each background async job to *INACTIVE.

• Clears all pending transactions from the data queue work tables.

• Submits an async reorganization; see Reorganizing the ASYNC Job Data Queues.

Once the reset async job completes, you can restart the background async jobs; see Starting the Background ASYNC Jobs.

If the async jobs remain in JOBQ status: If the async jobs remains in a JOBQ status at the Work with Background Jobs screen when you try to start them, you will need to contact your Order Management System representative. Be prepared to check recent activity in the log files, as described in the Logs topic.

If the async jobs end again when you restart them: If there has been more than one attempt to end the async jobs, there might be multiple END records in the async data queues. In this situation, the async jobs might process a few records before reaching an END record, which causes them to end again. You can work through the END records by re-running the async reset and restarting the background async jobs until the async jobs remain in a RUN status.

SO01_02 OMSCS 19.0 December 2019 OHC