Many APs run ABL-based Batch Jobs, at production (such as “Queues” for e. g. print jobs) and at installation/migration time (e. g. compile and data migration jobs). These jobs may be run as a sequence and/or hierarchy of jobs. For job control it is imperative to check for execution errors after a job finished.
A progress client executable should provide an exit code:
(a) 0 for success
(b) 1 for an (untrapped) stop condition (therefor no way of assigning a return code by ABL).
(c) and allow to set any other arbitrary positive exit code by ABL in order to allow the batch job to pass information to the outer job control, i. e. to the command shell.