Commitment control during normal routing step end

 

The system ends all commitment definitions for a job when a routing step is normally ended.

The following information applies only to commitment definitions with job-scoped locks.

A routing step ends normally by one of the following situations:

• A normal end for a batch job.

• A normal sign-off for an interactive job.

• The Reroute Job (RRTJOB), Transfer Job (TFRJOB), or Transfer Batch Job (TFRBCHJOB) command ends the current routing step and starts a new routing step.

Any other end of a routing step is considered abnormal and is recognized by a nonzero completion code in job completion message CPF1164 in the job log.

Before ending a commitment definition during routing step end, the system performs an implicit rollback operation if the commitment definition has pending changes. This includes calling the API commit and rollback exit program for each API commitment resource associated with the commitment definition. The exit program must complete its processing within 5 minutes. After the API commit and rollback exit program is called, the system automatically removes the API commitment resource.

If a notify object is defined for the commitment definition, it can be updated.

 

Parent topic:

System-initiated end of commitment control

 

Related concepts

Updates to the notify object