PL/SQL API jcs.run
Summary
- procedure run(name in varchar2, queue_name in varchar2, starttime in varchar2, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2)
- function run(name in varchar2, queue_name in varchar2, starttime in varchar2, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2) return number
- procedure run(name in varchar2, queue_name in varchar2, starttime in date, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2)
- function run(name in varchar2, queue_name in varchar2, starttime in date, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2) return number
- procedure run(name in varchar2, queue_name in varchar2, starttime in timestamp with time zone, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2)
- function run(name in varchar2, queue_name in varchar2, starttime in timestamp with time zone, time_window_name in varchar2, submit_frame_name in varchar2, priority in number, queue_partition in varchar2, time_window_partition in varchar2, submit_frame_partition in varchar2) return number
- procedure run(name in varchar2, job_id in out number) (Unsupported)
Schedule a job execution of a script, in a separate transaction.
It is different from jcs.submit in that it runs in a different transaction causing the job to be visible to the system immediately, without the need for the caller to commit.
This is useful in client tools that are not allowed to commit, or in circumstances where you want to log actions that have taken place, even when the caller subsequently rolls back.
note
The submit parameters queue_name, starttime, time_window_name, submit_window_name and priority are all optional and dependent on licensing restrictions. They can also be set using jcs.parameter.
note
The submit parameter recurrence_data must be set using jcs.parameter.
Privileges
You must have the SUBMIT privilege. You must have EXECUTE privilege on the script or EXECUTE ANY PROCEDURE system privilege. You must have INSERT privilege on the queue or USE_ANY_QUEUE system privilege. If a submit frame is used, you must have SELECT privilege on the submit frame or USE_ANY_SUBMIT_FRAME system privilege. If a time window is used, you must have SELECT privilege on the time window or USE_ANY_TIME_WINDOW system privilege.
Specification
procedure run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in varchar2,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
Submit a job in a separate transaction.
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job 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.
autonomous
Specification
function run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in varchar2,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
return number
Submit a job in a separate transaction and return the job_id of the job that was created.
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job If it is not filled in the default partition is assumed
- returns number - the job id of the created job.
Specification
procedure run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in date,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
Submit a job in a separate transaction
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job If it is not filled in the default partition is assumed
Specification
function run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in date,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
return number
Submit a job in a separate transaction and return the job_id of the job that was created.
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job If it is not filled in the default partition is assumed
- returns number - the job id of the created job.
Specification
procedure run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in timestamp with time zone default const.def_tstamp,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
Submit a job in a separate transaction
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job If it is not filled in the default partition is assumed
Specification
function run(name in varchar2,
queue_name in varchar2 default const.def_str,
starttime in timestamp with time zone default const.def_tstamp,
time_window_name in varchar2 default const.def_str,
submit_frame_name in varchar2 default const.def_str,
priority in number default const.def_num,
queue_partition in varchar2 default null,
time_window_partition in varchar2 default null,
submit_frame_partition in varchar2 default null)
return number
Submit a job in a separate transaction and return the job_id of the job that was created.
Parameters
- name - object name (script_name or owner.script_name), possibly with double quotes to specify lower case identifiers
- queue_name - the name of the queue that the job should run in
- starttime - requested first execution time
- time_window_name - the name of the time window that the job should start in
- submit_frame_name - the name of the submit frame that decides how to repeat the job
- priority - priority 1-100, higher has precedence; only has relevance if the resources or queue size is limited
- queue_partition - the name of the queue that the job should run in If it is not filled in the default partition is assumed
- time_window_partition - the partition of the time window that the job should start in If it is not filled in the default partition is assumed
- submit_frame_partition - the partition of the submit frame that decides how to repeat the job If it is not filled in the default partition is assumed
- returns number - the job id of the created job.
See Also
plsqlTopic
onsiteTopic