runjob

Purpose

Use the runjob command to control how a job is executed. The command enables you to start a job in the following ways:

• Immediately

• In an order different from that of the scheduler

• On a specific device or a device from which the job was previously restricted

Prerequisites

If you are attempting to control the execution of another user's jobs, then you must have the right to modify any job, regardless of its owner. If you are attempting to control the execution of your own jobs, then you must have the right to modify any jobs owned by user.

Syntax

runjob::=

run•job { --asap/-a | --now/-n | { --priority/-p schedule-priority } }
[ --device/-d device-name ] [ --quiet/-q | --verbose/-v ]
job-id ...

Semantics

--asap/-a

Starts the job as soon a possible by raising it to priority 1.

--now/-n

Starts the job now. If unable to start the job, Oracle Secure Backup generates an error message.

--priority/-p schedule-priority

Resets the job priority to schedule-priority.The default priority is 100. Refer to "schedule-priority" for a description of the schedule-priority placeholder.

--device/-d device-name

Runs the job on the device specified by device-name, ignoring job requirements.

--quiet/-q

Runs the job in quiet mode. --quiet directs obtool to suppress status messages it would normally write to stdout. Note that Oracle Secure Backup never suppresses error messages.

--verbose/-v

Displays output when running the job.

job-id ...

Specifies the identification number of the job you want to run. Execute the lsjob command to display job IDs.

Example

Example 2-147 lists a pending job and runs it immediately.

ob> lsjob --pending
Job ID           Sched time  Contents                       State
---------------- ----------- ------------------------------ ----------------------
sbt/23           03/22.21:00 dataset workdata.ds            future work
ob> runjob --device tape1 --now sbt/23
ob> lsjob --all sbt/23
Job ID           Sched time  Contents                       State
---------------- ----------- ------------------------------ ----------------------
sbt/23           03/22.21:00 dataset workdata.ds            completed successfully 
                                                            at 2005/03/22.18:09