Ending a job: immediate

 

When a job ends immediately, you can get undesirable results such as application data that has been partially updated. Use the immediate end option only if a controlled end has been unsuccessful.

Before ending the job, you should verify that no logical unit of work is in an in doubt state due to a two-phase commit operation that is in progress. If it is, then the value of the Action ifENDJOB commitment option can greatly impact the ENDJOB processing. This option is part of the Change Commitment Options (QTNCHGCO) API. For example, if the Action ifENDJOB commitment option is the default value of WAIT, this job will be held up and will not complete its end of job processing until the commitment control operation is completed. This ensures database integrity on all related systems.

When you use the immediate end option, the system performs minimal end-of-job processing, which can include:

• Closing the database files

• Spooling the job log to an output queue

• Cleaning up internal objects in the operating system

• Showing the end-of-job display (for interactive jobs)

• Completing commitment control processing

 

Parent topic:

Ending a job

Related information
Change Commitment Options (QTNCHGCO) API