Algorithms that Submit a Batch Job Updated to Reduce Duplicate Submissions

The product supplies two base algorithm types that submit a batch job for a given batch control. The algorithms use the default parameter values and mark the batch submission with a submission type of Generated. In this release, both algorithm types have been enhanced to check first if there is a already Pending, "Generated" batch job for the batch control. If one is found, the algorithm will not add another one.

The following algorithm types were impacted:

• F1-SCHEDJOB - Create Batch Job Submission Entry for Batch Control (Business Object Status - Enter plug-in)
• F1-NEXTJOB - Create Batch Job Submission Entry for Batch Control (Batch Control - Post-Processing plug-in)

The base product provides algorithms for the above algorithm types for several steps related to Content Migration Assistant (CMA). If you created several Migration Data Set Import records at once, you may have found that each one created a batch job submission for the Data Set Monitor batch. However, the batch framework only processes one at a time, so the extra batches queued up in Pending status. All the data sets were processed by the first batch run. As a result, subsequent batch runs did not have anything to process.

If your implementation has plugged in any of the base delivered algorithms to help orchestrate the CMA processing, you will see a change, especially when creating multiple Migration Data Sets in a short period of time. Now, the system will ensure that no more than one pending batch job is generated.

If your implementation has not used the base algorithms for CMA and has not created any custom algorithms for the above algorithm types for your own use cases, you are not affected by this change.

Reducing the creation of unnecessary batch job submission records ensures that processing time is not spent on these extraneous submissions.

Steps to enable and configure

You don't need to do anything to enable this feature.