As of $Date: 2002/05/08 11:31:51 $ the list of things we'd like to add to this
package are:
- Do something useful with bplist.  But what?
- Make sure we can answer the age old question: "When I restore <xyzzy> which
  tapes will I need?"
- Determine which robot a tape was in when it filled up.  Part of an effort to
  monitor tape consumption by robot to help manage their contents.
- Add XML configuration files to:
	- comment on robot contents (see current require technique in 
	  examples/robot-snapshot.pl)
	- manage behavior of notify and exit scripts
- Build database interface to centralized drive and media failure tracking
  system.  (bperror is nice but it doesn't carry info on DOWNED drives.)
  the vmglob command, new with 3.4, allows us to uniquely identify drives and
  robots (except that replacing drives does not update their serial numbers!)
- Investigate additional information provided by vmquery -X; a value of 0x0 in
  the flags field indicates the tape has been marked for deletion.  This format
  though carries more information and might be better used than the current -w
  layout
- loadJobs and now refreshJobs leverage the -stay_alive feature of bpdbjobs;
  the next level of job detail and progress monitoring will have to come from
  perusing the contents of the files in the /usr/openv/netbackup/db/jobs
  directory.  Especially the *.t files carry immensely useful data on instan-
  taneous job throughput.  However, with the advent of NBU 4.5 these files will
  no longer be available... :-(
- For Media, load information using bpmedialist and vmquery on a single volume
  basis if circumstances warrant, i.e. if the NBU::Media->populate factory
  method has not been invoked yet...
