Skip to end of metadata
Go to start of metadata

Batch jobs can have different start conditions defining how the jobs are scheduled:


In the case of an immediate start, the batch job may possibly be scheduled directly in the context of the function call that created the entry in database table TBTCO, without involvement of the actual batch scheduler.


The start mechanism of immediate start job is : 

  • First, an attempt is made to find a suitable server instance that has a free batch work process (either among the specified target servers or among all servers)
  • If such a server is found, a BTC request is directly submitted to that server instance so that the job can run immediately
  • Otherwise, the batch job is transformed into a time based job with the current time as start time (with target server if specified), will be picked up and be executed when time scheduler runs next time.



Please keep in mind:

Usually if a ‘start immediate’ job does not find a free resource, it’s transformed in a time-based job with the current start date and picked up by the batch scheduler.

However,  there is an argument named DIRECT_START in function module JOB_CLOSE .

when function module JOB_CLOSE is called with DIRECT_START='X' in customer coding,

This means:

"X" - Start Without Converting to Time-Based Job



  • If this parameter is set to 'X', a job scheduled with immediate start is not converted to a time-driven job. Instead, the exception CANT_START_IMMEDIATE is triggered, to return control to the caller. The job then remains in the status "planned" without any start conditions.

    DIRECT_START can only be used together with STRTIMMED.