PROBLEM: (87802, 84422, 87576, 87802,
          90472, 92015, 93597) (PATCH ID: OSF540-135)
********
This patch addresses one problem. When the system discovers a new device,it
generates a new name for it to create the device special file (dsf). The
instance part, a number, can get quite large when doing many disk backups
using a clone-copy-delete procedure. Since the instance is always increasing,
the names quickly become hard to manage. Also, the backup program must
determine the new numbers each time it runs.
To fix this problem, the dsfmgr program has added a new option that will
minimize (or set) the instance numbers to the lowest possible value.
If your system deletes and creates a large number of devices or deletes and
creates devices often, this patch will help keep the values lower.
For systems that have a fixed configuration except for the backup procedure,
it will mean that each new set of cloned backup devices will always have the
same new names. It can simplify the backup procedure.
 - an illegal input argument causes a core dump
     This usually occurs when no arguments are entered.

 - improper error handling by the stat function
   during boot dsfmgr fails with:

    dsfmgr: NOTE: creating device special files for system at /
    dsfmgr: ERROR: stat( "/dev/disk/dsk19a" ) = kernel database - duplicate
                     device ID's +dsk19a
    /sbin/dn_setup: 1573120 Memory fault - core dumped

 - the move/exchange may cause data errors
     This occurs when it encountered a partial set of device nodes.

 - during boot the following message is seen:
   =============================
  Problem occurred again while booting all nodes of the cluster.
    The problem occurred on two nodes: tcr6b:
  Checking device naming:
  ERROR : DEC_CHW_COMP : /etc/dec_hwc_cdb: invalid database size.
             Is 412648, sb 412408.
  ERROR : DEC_CHW_COMP : /etc/dec_hwc_cdb.bak: invalid backup size.
             Is 412648, sb 412408.
  bcheckrc: Device Naming failed initial check.
      Correct errors and then continue or reboot.
   =============================
    This can be caused by a file update during the dsfmgr read of the file.
    Nothing is wrong and a ^D (ctrl D) will continue the boot again.
    This fix will detect this senerio and the system will boot without any
    operator intervention.