Clairify bscan doc

diff --git a/docs/manuals/en/utility/progs.tex b/docs/manuals/en/utility/progs.tex
index 90c9db662b2e019bb9e2127da933989e4465ca2f..88ed2b006f8506753b6d7e16440c31139dbe606a 100644 (file)
--- a/docs/manuals/en/utility/progs.tex
+++ b/docs/manuals/en/utility/progs.tex
@@ -583,6 +583,10 @@ Volume=Vol003
 \end{verbatim}
 \normalsize
 
 \end{verbatim}
 \normalsize
 

+Note: {\bf bscan} does not support supplying Volume names on the
+command line and at the same time in a bootstrap file.  Please
+use only one or the other.
+

 You should, always try to specify the tapes in the order they are written.
 If you do not, any Jobs that span a volume may not be fully or properly
 restored. However, bscan can handle scanning tapes that are not sequential.  Any
 You should, always try to specify the tapes in the order they are written.
 If you do not, any Jobs that span a volume may not be fully or properly
 restored. However, bscan can handle scanning tapes that are not sequential.  Any


@@ -595,7 +599,6 @@ records that span two volumes.  In other words, it is much better to
 specify two or three volumes on a single bscan command (or in a .bsr file)
 rather than run bscan two or three times, each with a single volume.
 
 specify two or three volumes on a single bscan command (or in a .bsr file)
 rather than run bscan two or three times, each with a single volume.
 

-

 Note, the restoration process using bscan is not identical to the original
 creation of the catalog data. This is because certain data such as Client
 records and other non-essential data such
 Note, the restoration process using bscan is not identical to the original
 creation of the catalog data. This is because certain data such as Client
 records and other non-essential data such