jcs.job_pin_to_scheduler

on-site-related topic PL/SQL API jcs.job_pin_to_scheduler

Summary

Force the job that is being submitted to run on a specific scheduler, also referred to as pin to scheduler or force scheduler.

Note: You need to call jcs.clear_parameters('<script>') first or jcs.job_pin_to_scheduler will have no effect.

Specification

procedure job_pin_to_scheduler(scheduler_name in varchar2,
scheduler_partition in varchar2 default null)

Parameters

  • scheduler_name - the name of the scheduler where the job must run
  • scheduler_partition - the Partition of the scheduler where the job must run If it is not filled in the default Partition is assumed

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

submit_buffer

Specification

procedure job_pin_to_scheduler(from_job_id in number)

Parameters

  • from_job_id - the job ID where the scheduler name is taken from

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

submit_buffer

Specification

procedure job_pin_to_scheduler(job_id in number,
scheduler_name in varchar2,
scheduler_partition in varchar2 default null,
can_commit in varchar2 default const.jcs_no,
do_commit in varchar2 default const.jcs_yes)

Parameters

  • job_id - the job that is being force
  • scheduler_name - the scheduler where the job must run
  • scheduler_partition - the Partition of the scheduler where the job must run If it is not filled in the default Partition is assumed
  • can_commit -
  • if true, and do_commit is also true, commit the current transaction
  • if false, and do_commit is true, commit using an autonomous transaction
  • do_commit -
  • if true, commit in accordance with the can_commit parameter
  • if false, do not commit. Caller is responsible for committing, or rolling back.

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

can_commit_autonomous

Specification

procedure job_pin_to_scheduler(job_id in number,
from_job_id in number,
can_commit in varchar2 default const.jcs_no,
do_commit in varchar2 default const.jcs_yes)

Parameters

  • job_id - the job that is being force
  • from_job_id - the job ID where the scheduler name is taken from
  • can_commit -
  • if true, and do_commit is also true, commit the current transaction
  • if false, and do_commit is true, commit using an autonomous transaction
  • do_commit -
  • if true, commit in accordance with the can_commit parameter
  • if false, do not commit. Caller is responsible for committing, or rolling back.

Transaction keyword

The transaction keyword defines how and/or when the changes are committed to the database. A definition of the various transaction keywords can be found on the jcs package summary page.

can_commit_autonomous