=head1 NAME
backup_jobs - Lists pending and running operations in interactive mode
=head1 SYNOPSIS
=for html
B [B<-help>]
B [B<-h>]
=for html
=head1 DESCRIPTION
The B command lists the job ID number and status of each
B operation running or pending in the current interactive session.
This command can be issued in interactive mode only. If the issuer of the
B command included the B<-localauth> flag, the
B<-cell> argument, or both, those settings apply to this command also.
To terminate operations that appear in the output, issue the B command and identify the operation to cancel with the job ID number
from this command's output.
To check the status of a Tape Coordinator, rather than of a certain
operation, use the B command.
=head1 OPTIONS
=over 4
=item B<-help>
Prints the online help for this command. All other valid options are
ignored.
=back
=head1 OUTPUT
The output always includes the expiration date and time of the tokens that
the B command interpreter is using during the current interactive
session, in the following format:
: TOKEN EXPIRATION
If the execution date and time specified for a scheduled dump operation is
later than , then its individual line (as described in the
following paragraphs) appears below this line to indicate that the current
tokens will not be available to it.
If the issuer of the backup command included the B<-localauth> flag when
entering interactive mode, the line instead reads as follows:
: TOKEN NEVER EXPIRES
The entry for a scheduled dump operation has the following format:
Job : : dump
where
=over 4
=item
Is a job identification number assigned by the Backup System.
=item
Indicates the date and time the dump operation is to begin, in the format
I/I/I I:I (in 24-hour format)
=item
Indicates the volume set to dump.
=item
Indicates the dump level at which to perform the dump operation.
=back
The line for a pending or running operation of any other type has the
following format:
Job :
where
=over 4
=item
Is a job identification number assigned by the Backup System.
=item
Identifies the operation the Tape Coordinator is performing, which is
initiated by the indicated command:
=over 4
=item Dump (I)
Initiated by the backup dump command. The I has the following
format:
.
=item Restore
Initiated by the B, B, or B command.
=item Labeltape (I)
Initiated by the Bn command. The I is the
name specified by the B command's B<-name> or B<-pname>
argument.
=item Scantape
Initiated by the B command.
=item SaveDb
Initiated by the B command.
=item RestoreDb
Initiated by the B command.
=back
=item
Indicates the job's current status in one of the following messages. If no
message appears, the job is either still pending or has finished.
=over 4
=item I Kbytes, volume I
For a running dump operation, indicates the number of kilobytes copied to
tape or a backup data file so far, and the volume currently being dumped.
=item I Kbytes, restore.volume
For a running restore operation, indicates the number of kilobytes copied
into AFS from a tape or a backup data file so far.
=item [abort requested]
The B command was issued, but the termination signal has yet
to reach the Tape Coordinator.
=item [abort sent]
The operation is canceled by the B command. Once the Backup
System removes an operation from the queue or stops it from running, it no
longer appears at all in the output from the command.
=item [butc contact lost]
The backup command interpreter cannot reach the Tape Coordinator. The
message can mean either that the Tape Coordinator handling the operation
was terminated or failed while the operation was running, or that the
connection to the Tape Coordinator timed out.
=item [done]
The Tape Coordinator has finished the operation.
=item [drive wait]
The operation is waiting for the specified tape drive to become free.
=item [operator wait]
The Tape Coordinator is waiting for the backup operator to insert a tape
in the drive.
=back
=back
=head1 EXAMPLES
The following example shows that two restore operations and one dump
operation are running (presumably on different Tape Coordinators) and that
the B command interpreter's tokens expire on 22 April 1999 at
10:45 am:
backup> jobs
Job 1: Restore, 1306 Kbytes, restore.volume
Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
Job 3: Restore, 2498 Kbytes, restore.volume
04/22/1999 10:45: TOKEN EXPIRATION
=head1 PRIVILEGE REQUIRED
None. However, queuing any operation requires privilege, and it is
possible to issue this command only within the interactive session in
which the jobs are queued.
=head1 SEE ALSO
L,
L,
L,
L
=head1 COPYRIGHT
IBM Corporation 2000.