Why the hell ADDPFTRG ... TRGEVENT(*DELETE) & ADDPFCST ... DLTRULE(*CASCADE) can't Coexist on the same file???

Hi to all and sorry for my poor english.

We're trying to add both the instruction in subject to a PF (which is dependent
of another file) and ended up with CPD321C - Reason 5: cannot have a a DELETE
trigger on a CASCADE file. We've waiting to move up to 5.1.0 to see if it is
fixed, but still no luck.

Is there any rasonable motivation to do so?? I mean, i expect i can do this in
order to have record for file MYFILE in order to get record deleted
automagically when his "father" is deleted *and* the system do perform some
operation in the meanwhile (mainly, update some other file & write deletions to
a log). Seem to me logic, basing on what i understand costraint & trigger are
for.

I thought that, when i delete FILEA, the system will check for every record
matching the costraint to FILEB, delete it and so activate the appropriate
trigger. Seems i'm wrong, but cant' understand why...

We tried, of course, the reverse: first add the trigger, then add the costraint,
but still (umpah !!!) no luck. IBM checked even this  :-(

Is there any hope this can be fixed/circumvent in any way or we must modify
programs so that depending file are manually deleted insted of automatically??
(i know i can do this by a trigger on the first file, but i think it's the
system that ahve to take care of this, not me....)

Thank you.