PROBLEM: (82038) (PATCH ID: OSF510-003)
********
When a user tries to dump to a regular file he would get an
error message stating that  "dump: IO control failed for
`output_file`" . See example given below. 
# dump 0f /usr/tmp/mnt.dump /mnt

dump: Dumping from host idcssu
dump: Date of this level 0 dump: Wed Sep  6 10:14:34 2000 EDT
dump: Date of last level  dump: the start of the epoch 
dump: Dumping /dev/rdisk/dsk5a (/mnt) to /usr/tmp/mnt.dump
dump: Mapping (Pass I) [regular files]
dump: Mapping (Pass II) [directories]
dump: IO control failed for /usr/tmp/mnt.dump.
dump: NEEDS ATTENTION: Do you want to retry the open?: ("yes" or "no") no
dump: SIGTERM received 
dump: The ENTIRE dump is aborted
dump: SIGTERM received 
dump: The ENTIRE dump is aborted


PROBLEM: (85030, 86830, 86926, HPAQ3220N) (PATCH ID: OSF510-289)
********
Using the command rdump to back up data on a remote host would result in a 
core dump.  Here is an example of the output that is produced when using
the unpatched rdump utility:
# rdump -f root@unos:/dev/disk/dsk1c /dev/disk/floppy0c
rdump: Dumping from host animal.zk3.dec.com
rdump: Date of this level 9 dump: Wed Jun 27 14:46:30 2001 EDT
rdump: Date of last level 0 dump: the start of the epoch
rdump: Dumping /dev/disk/floppy0c to /dev/disk/dsk1c on host unos
rdump: Mapping (Pass I) [regular files]
rdump: Mapping (Pass II) [directories]
rdump: SIGSEGV received -- ABORTING!
rdump: Child 1188 returns low-byte status 206


PROBLEM: (91284) (PATCH ID: OSF510-534)
********
Now rdump command dumps data properly onto remote tape devices
without receiving the signal SIGSEGV and dumping core.