PROBLEM:	(QAR 45730 and QAR 46647)	(Patch ID: OSF415-400066)
********
DDR partially builds some device records.

This problem is extremely hard to detect, as the creation of device records
usually happens silently in the kernel as it encounters new devices.  Symptoms
of this error may be slight oddities in device behavior.  Unfortunately, the
extent to which behavior is affected cannot be predicted.

The problem can be seen most easily by executing the following:

      Invoke "ddr_config -s disk DEC RZ28B".

      The (failing) output should look as follows:
         Building Device Information for:
           Type = disk
           Vendor ID: "DEC"   Product ID: "RZ28B"

         Applying Modifications from Device Record for :
           Vendor ID: "DEC"   Product ID: "RZ28"
             TagQueueDepth = 0x4a


      The (correct) output should look as follows:

         Building Device Information for:
           Type = disk
           Vendor ID: "DEC"   Product ID: "RZ28B"

         Applying Modifications from Device Record for :
           Vendor ID: "DEC"   Product ID: "RZ28"
             TagQueueDepth = 0x4a

         Applying Modifications from Device Record for :
           Vendor ID: "DEC"   Product ID: "RZ28B"
             TagQueueDepth = 0x40


PROBLEM:	(QAR 45730 and QAR 46647)	(Patch ID: OSF415-400066)
********
The "ddr_config -x" option fails to compile a cam_data.c file from a version
prior to Digital UNIX v4.0.

The following error messages will be reported:

       ddr_config.ORIG: Line 3233: Syntax Error
       ddr_config.ORIG: Line 3233: Failed parsing DENSITY_TBL entry

       Conversion of /sys/data/cam_data.c failed. 

Line numbers are relative to the temporary file /tmp/cam_data.tmp

Looking at the /tmp/cam_data.tmp file, the error occurs between two records
separated by a comma. For example:

       TYPE
       Record_A = { ....
       },                           <----- fails here
       Record_B = { ...
       };

PROBLEM:                (Patch ID: OSF415-020)
********
Provides latent support for TZS20. See the DIGITAL UNIX and TruCluster "Patch
Summary and Release Notes for Patch Kit-???" for more information on the
TZS20 tape devices.

PROBLEM:  (QAR 52217,  QAR 54680)    (Patch ID: OSF415-405376)
********
The maximum block size (MaxTransferSize) for "unknown" tape devices specified
in the /etc/ddr.dbase file was previously limited to 64 kilobytes.  This would
cause applications, such as back-up utilities, to fail if a block size of
greater than 64 kilobytes was specified.

This patch modifies the value of MaxTransferSize to 16 megabytes to support
devices and applications that can support larger block sizes.