The behavior of the backup_dump does not match documentation w.r.t. '-nohold'

[anonymous]

The backup utilities are documented as unloading tapes by default, but do not.

complete_dump.info, backup_dump.info, catchup_dump.info:

-nohold
   rewinds and unloads the hierarchy dump tape or tapes at the end of
   the current dump pass.  This is the default.

start_dump.info:

-nohold
   rewinds and unloads the hierarchy dump tape or tapes at the end of
   the current dump pass.  This is the default for all hierarchy dump
   modes except incremental.

bk_ss_.cds:       2 holdsw bit (1),				/* ON => do not unmount tape when done */
bk_ss_.cds:	bk_static.holdsw = "0"b;

bk_arg_reader_:

               else if op = "hold" then bk_ss_$holdsw = "1"b; /* do not dismount */
               else if op = "nohold" then bk_ss_$holdsw = ""b; /* dismount, default */

then in start_dump.pl1, after 'examine_arguments:' (the "join" for complete_dump, catchup_dump, start_dump):

          bk_ss_$holdsw = "1"b;

"-nohold" is also the documented behavior for 'retreive' and 'reload', but I have not tested the actual behavior.

retrieve.info, reload.info:

The following defaults are in effect for the reloader and retriever
before any backup commands are given; they are not, however, reset to
these values at the start of each backup command, except as noted
below.

      -all                    -noquota
      -error_of               -primary
      -map                    -reload
      -nodebug                -setlvid
      -nohold                 -trim