>One administrative schedules runs something like "del volhist
>todate=today-3 type=dbbackup" and no matter if this command is scheduled or
>executed in dsmc or over the web: I get an RC of zero and the message that
>0 sequential volumes are deleted. Doing a "q volhist type=dbbackup" shows
>at least 5 volumes that are old enough to be deleted.

I'm not aware of any APARs for this problem.  One possibility, though:
I've seen *SM poorly handle the case of a full file system when trying
to write external, sequential server files.  I'd recommend checking the
place where your VOLUMEHistory server option points and see what's going
on with that file and file system.
    Richard Sims, BU