a number of methods (subroutines) that can be called. They
are:
\begin{description}
-\item [set\_events] The set\_events takes a single
+\item [set\_events] The set\_events method takes a single
argument, which is the instantation of the Job Events class
that contains the methods that you want called. The method
names that will be called must correspond to the Bacula
started, or -1 if there was an error.
\item [write] The write method is used to be able to send
print output to the Job Report. This will be described later.
-\item [DoesVolumeExist] The DoesVolumeExist takes a single
+\item[cancel] The cancel method takes a single integer argument,
+ which is a JobId. If JobId is found, it will be canceled.
+\item [DoesVolumeExist] The DoesVolumeExist method takes a single
string argument, which is the Volume name, and returns
1 if the volume exists in the Catalog and 0 if the volume
does not exist.
\begin{description}
\item [Priority] Read or set the Job priority.
-Note, that setting a Job Priority is effective only before
-the Job actually starts. (not functional yet)
+ Note, that setting a Job Priority is effective only before
+ the Job actually starts.
+\item [Level] This attribute contains a string representing the Job
+ level, e.g. Full, Differential, Incremental, ... if read.
+ The level can also be set.
\end{description}
The following read-only attributes are available within the Director
\begin{description}
-\item [Level] This attribute contains a string representing the Job
- level, e.g. Full, Differential, Incremental, ...
\item [Type] This attribute contains a string representing the Job
type, e.g. Backup, Restore, Verify, ...
\item [JobId] This attribute contains an integer representing the