← jcs.add_job_notejcs.add_job_wait_event →

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

Summary

Make a job raise an additional event on a particular status.

Privileges

the caller must be able to see the job. If the job is owned by the user, the user must have the ADD_JOB_RAISE_EVENT system privilege. If the job is owned by someone else, the user must have the ADD_ANY_JOB_RAISE_EVENT system privilege and UPDATE privilege on the job's queue.

Specification

procedure add_job_raise_event(job_id in number,
status in varchar2,
return_code in number default null,
event_name in varchar2,
can_commit in boolean default false,
event_partition in varchar2 default null)

Used with languages that support the boolean datatype.

Parameters

  • job_id - the ID of the job
  • status - the status or statuscode that the job should get
  • return_code - in case of ERROR, the exact return_code that the job should get
  • event_name - the name of the event that will be raised
  • can_commit - should this be committed immediately?
  • event_partition - the partition of the event to wait for 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.

can_commit_autonomous

Specification

procedure add_job_raise_event(job_id in number,
status in varchar2,
return_code in number default null,
event_name in varchar2,
can_commit in varchar2,
event_partition in varchar2 default null)

Used with languages that do not support the boolean datatype; can_commit is passed as const.jcs_yes or const.jcs_no.

Parameters

  • job_id - the ID of the job
  • status - the status or statuscode that the job should get
  • return_code - in case of ERROR, the exact return_code that the job should get
  • event_name - the name of the event that will be raised
  • can_commit - should this be committed immediately?
  • event_partition - the partition of the event to wait for If it is not filled in the default partition is assumed

Specification

procedure add_job_raise_event(script in varchar2,
status in varchar2,
return_code in number default null,
event_name in varchar2,
event_partition in varchar2 default null)

Parameters

  • script - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
  • status - the status or statuscode that the job should get
  • return_code - in case of ERROR, the exact return_code that the job should get
  • event_name - the name of the event to wait for
  • event_partition - the partition of the event to wait for 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.

database_modified

plsqlTopic

onsiteTopic

← jcs.add_job_notejcs.add_job_wait_event →