In the event of an unexpected program end, a situation could occur whereby an allocated object is not released. If there is a subsequent process waiting for the object allocation, it will not receive any notification about the object reclaim from the prematurely ended job. If such is the case, it will not continue. This tool should be used to release the object and trigger the process flow.
Currently allocation methods are applied for two types of objects: Batch (OPBTCH) i.e. batches created via the Work with open batches routine, and Program (PROG). Using this tool you can manually release allocated batches and programs. A manual reclaim is allowed if the job no longer exists, not if the job is still running. A manual reclaim is primarily to be used to deallocate programs i.e. objects of type SROALOBJ.AOAOTP= “PROG”. Objects of type SROALOBJ.AOAOBT = “OPBTCH” would normally be reclaimed directly from the Work with open batches routine – by using the dedicated option 90=Unlock. Therefore, the default selection for the field Type is PROG.
Options
| Reclaim | Select this option to reclaim the object (manually release and trigger the process flow). The procedure ASWAllocation_reclaimAllocationObject is called and a message sent to either inform the user that the object was reclaimed, or it was unsuccessful because the job holding the object is still running. |
- Type
- This column lists the type of the allocation object, i.e. the SROALOBJ.AOAOBT field value.
- Object ID
- This column lists the allocation object identification, i.e the SROALOBJ.AOAOBI field value
- Description
- This column displays the allocation object description, i.e. the SROALOBJ.AOAOBT field value.
- Category
- This column displays the allocation object category i.e. the SROALOBJ.AOALCA field value
- Max
- This column displays the maximum number of allocations.