jcs_odf.create_scheduler

on-site-related topic PL/SQL API jcs_odf.create_scheduler

Summary

Create a scheduler.

Specification

Copy 
procedure create_scheduler(name in varchar2,
description in varchar2 default const.def_str,
cpu_weight in number default const.def_num,
job_weight in number default const.def_num,
dispatcher_weight in number default const.def_num,
comment_text in varchar2 default const.def_str,
application_name in varchar2 default const.def_str,
type in varchar2 default const.def_str,
startup_cmd in varchar2 default const.def_str,
keep_until in varchar2 default const.def_str,
configuration in varchar2 default const.def_str,
partition in varchar2 default const.def_str,
application_partition in varchar2 default const.def_str,
nt_service_name in varchar2 default const.def_str,
execution_size in number default const.def_num,
os_user in varchar2 default const.def_str,
starttype in varchar2 default const.def_str,
odf_weight in number default const.def_num,
db_user in varchar2 default const.def_str,
hold_delete in varchar2 default const.def_str)

Parameters

  • name - the name of the scheduler
  • description - a description for the scheduler
  • cpu_weight - the CPU load of the Process Server host is multiplied by cpu_weight in load balancing calculations
  • job_weight - the number of jobs running on the host of the Process Server is multiplied by job_weight in load balancing calculations
  • dispatcher_weight - the dispatcher agent is located on the Process Server with the highest dispatcher_weight. A Process Server with a higher dispatcher_weight than another Process Server is more suitable to run the dispatcher agent.
  • comment_text - a comment with the scheduler
  • application_name - the name of the application the scheduler belongs to
  • type - the type of scheduler, 'NATIVE' or 'JAVA'
  • startup_cmd - the startup command for a java scheduler
  • keep_until - how long will the scheduler trace files will be kept on the server - null means unlimited. This must be an Oracle date expression
  • configuration - configuration string for the scheduler
  • partition - the partition of the scheduler
  • application_partition - the partition of the application the scheduler belongs to
  • nt_service_name - if this is filled and the scheduler runs on Windows NT it specifies the name of the service connected to this scheduler
  • execution_size - the maximum number of concurrent jobs in the Queue (with status RUNNING, WAITING or CONSOLE)
  • os_user - the OS user starting the NT service (null for localsystem account)
  • starttype - the starttype of the related NT service (MANUAL or AUTOMATIC)
  • odf_weight - the preference to execute Redwood explorer commands
  • db_user - the Oracle user that the MA uses to log into the database
  • hold_delete - should the delete agent run?

Note: The scheduler type depends on the startup command: when the startup command is empty, the scheduler type is 'NATIVE', otherwise it is 'JAVA'. You cannot edit the scheduler_type directly.

See Also