Browse Prior Art Database

Publication Date: 2016-Mar-02
Document File: 7 page(s) / 187K

Publishing Venue

The Prior Art Database


This paper demonstrates a new concept and tool to identify, define and resolve batch jobs conflicts in advance. This tool holds execution, reschedules and reruns the batch jobs based on changing environmental variables at run time well within the business requirements and technology in use.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 29% of the total text.

Page 01 of 7


Title: Automatic Conflict Resolver Tool (ACRT)

1.0 Introduction:
Operating systems and the databases are capable of handling conflict and deadlock and they do this efficiently. For resolution the operating systems (OS) or databases(DB) put the execution in a waiting queue and provide the required resources in most efficient way, sometimes this happens at lightning speed but sometime this waiting causes the execution to take unpredictable time and the scheduled jobs runs forever unless stopped manually or restarted. Most of the deadlock situations are resolved automatically by OS as well as by DB but it is evident that sometimes scheduled jobs proves to be victim of such deadlock resolution. Once stopped by agent or OS these

jobs never kick off without manual intervention or until the next schedule is run. In the environment where scheduled jobs are in hundreds, slightest delay in execution time cause cascading effect on other scheduled jobs and ultimately on the overall system.

Automated scheduled jobs perform many essentials functions on execution in the back end. Broadly these can be classified into two categories

1. Jobs related to Business logic and

2. Jobs related to Database management and automation.

In any available environment, jobs are scheduled to run on specific time and frequency. They have certain limitations like existing tools have no control on scheduled jobs once they started running. Jobs either complete successfully or error out. There is no in-between status. The disclosed tool ACRT tries to overcome this limitation. It is capable of controlling the executing jobs in run time. For this, ACRT uses analytics to find optimum path of execution, comparing the current run-time environment and decides to either keep the job running or put the job on Hold and wait for favorable conditions to re-run it within the specified time window.

2.0 Challenges with batch job scheduling

The novelty of this tool lies in the logic its implementation to prevent the situation where chances are almost certain for conflict or potentials blockings and deadlock. This tool also completely relies on the capability of Operating System (OS) and Database (DB) for Conflict resolution because it works as a part of it and NOT as a substitute.

ACRT has capability to restrict, hold and rerun the batch jobs using Job conflict matrix. Job conflict matrix is preserved and provides information to ACRT. Again this tool manages and upgrades this matrix periodically.

This tool addresses following limitations of existing technologies.

 Jobs once started, the execution scheduler has no control on the jobs


Page 02 of 7

 If conflict occurs in between it is handled by either OS or database only

 Jobs scheduler is unable to change the states of jobs once job starts execution until its completion.

 All schedulers can report job failure but they are not able to prevent failure or put

job on hold for a while i...