How To Supply the Actual Key Range to a Multi-Thread Batch Job
(Doc ID 736350.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Utilities Customer Care and Billing - Version 220.127.116.11 and later
Information in this document applies to any platform.
Tried to run a Cobol batch job in multiple threads. They need to process 2.8 million To Do records of a certain To Do Type. The records' Ids for this To Do Type are in the range from <00000 and 6 digits number> to <00000 and 9 digits number>, which makes breaking them into a reasonable number of threads impossible; all records fall into the first thread. The customer used the base To Do maintenance program CIPQTDEN to create these entries.
The Cobol side would generate a random parent key, OR use the drill key as the parent key. When there is no parent key, the first 5 digits of the To Do Entry Id are all zeroes, rendering breaking such records into threads impossible.
This issue affects older batch jobs (not only related to To Do) written in Cobol, because they use for threading the full possible key range from all zeroes to all nines. Batch jobs written in java are not affected; threading in them is done based on the actual number of records to process, which allows more even record distribution among threads.
Runs a job which adds batch run, thread and instance data to the database so that they can name the range of data to be processed by the run in each batch thread’s restart data.
There is no named status with which to define these records, so only ERROR can be used to force a restart of this particular batch run. This is not suitable, and should be replaced with a more meaningful status that can be used for this purpose.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document