Sunday 3 June 2012

Lead Time in Ca7


Lead Time/Look Back Time:

    It is the time where we can look back for the execution of the Job in the previous run where we can post the requirements if they are met.

·         Lead time varies from 0 to 99.
·     0 indicates no lead time is to be considered when satisfying this job’s requirements.
·         98 maximum lead  time value is 98 hours.
·         99 Each predecessor job must complete normally while this job is in the request queue.

       This is a special case, even though it is equivalent to zero lead time. Because, the requirement is never to be considered as already satisfied when the job enters the queues.

What is Lead Time? What are Look-back issues?

Lead Time is the period (in hours)[time-window],that a job looks back in time, to check if all its requirements(promises)are fulfilled.

Example of a Look-back issue.

Very often, there is too large a time-gap that elapses between a predecessor job A’s completion, and its dependent B’s starting out. When B is brought into the REQ(Request) Queue, if A’s completion doesn’t fall in the Look-back(Lead-time) window, B keeps waiting in the REQ Queue. These are called Look-back issues. CA-7 Look-back issues generally happen in the Production Environment, generally due to delays in Batch Cycle, holidays etc.

Lead-Time could take several values.

00-No special consideration for the amount of  time elapsed, between the pred-job and dependent job’s runs.
99-The requirement is never to be considered as already satisfied, when the job enters the Queue.
nn-Since, the last run of the job, each predecessor job must have run with in the last nn hours. Values for run may be from 1 to 98.

1 comment: