You use this DBM command to display the list of all the Scheduler jobs. For each created job, the job ID, owner, status, time at which the job is to be executed, time at which it was last executed and the DBM command to be executed are displayed.
DBM operators with the server authorization SchedulerMgm can see all active and inactive jobs. DBM operators with the server authorization Scheduling only see the active and inactive jobs that they own.
If an error occurred during the execution of a job, the dbm.prt log file provides more information on it. Search for the appropriate entry using the planned time, the job ID and all DBM server PIDs displayed in the list of all Scheduler jobs.
See also:
Concepts of the Database System, Automating Administration Tasks
You have the server authorization SchedulerMgm or Scheduling.
scheduler_list_jobs
OK
ID <job_ID>
owner: <dbm_user>
status: <job_status>
runs: at: <job_time>|after: <job_id> [(once)]>
last run: <date_run> <time_run>
DBM Server PID <process_ID>
return code <message_number>
dbm_command: <dbm_command>
ID <job_ID>
owner: <dbm_user>
status: <job_status>
runs: at: <job_time>|after: <job_id> [(once)]>
last run: <date_run> <time_run>
DBM Server PID <process_ID>
return code <message_number>
dbm_command: <dbm_command>
...
Values for the Reply Fields
Value |
Description |
<job_ID> |
Job ID |
<job_status> |
Job status. Possible values are: active: the job is active. inactive: the job is inactive. |
<job_time> |
Defined time at which the job is to be executed |
(once) |
Executed once |
<date_run> |
Day on which the job was last executed |
<time_run> |
Time at which the job was last executed |
<process_ID> |
Process ID |
<message_number> |
Message number See also: Documentation, Messages |
Call the Database Manager CLI, log on as operator OLEG with password MONDAY, connect to the database instance DEMODB, display the list of all active and inactive Scheduler jobs:
>dbmcli -u OLEG,MONDAY -d DEMODB scheduler_list_jobs
OK
ID 0
owner: OLEG
status: active
runs: at 06:00:00 PM
last run: 2005-05-02 18:00:02
DBM Server PID 2632
return code OK (0)
dbm_command: db_offline
ID 1
owner: OLEG
status: active
runs: at 19:00:00
last run: 2005-05-02 19:00:01
DBM Server PID 1652
return code ERR (-24977)
dbm_command: db_onnnline
ID 2
owner: OLEG
status: active
runs: after 1
dbm_command: db_state