RE: ADDPFTRG fails with CPF32C6/CPD32E7

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

There's am extensive thread on this in the archives. Concensus is, it does 
not take long for the DBXREF. Tom Liotta said:

> by limiting the function to the simpler *DBXREF, your reclaim time will 
> almost certainly be measured in minutes rather than hours or days.
>
> Most likely, a *DBXREF is all you'll need. And it's _relatively_ painless 
> and gives excellent bang-for-the-buck.

I searched on DBXREF in the archives.

HTH
Vern

At 08:08 PM 4/3/2004 +0200, you wrote:
> Thanx.
>
> RCLSTG is 'a long running function'
>
> I know that RCLSTG *ALL is (used to be) a matter of hours (depending 
> of...) in dedicated mode.
> My feeling is that RCLSTG *DBXREF should be much less 'expencive'. Do you 
> have any practical expierence?
>
> Henrik
>
> > date: Fri, 2 Apr 2004 17:25:07 -0600
> > from: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > subject: RE: ADDPFTRG fails with CPF32C6/CPD32E7
> >
> > Try RCLSTG *DBXREF on the failing machine.
> >
> >
> > -----Original Message-----
> >  Subject: ADDPFTRG fails with CPF32C6/CPD32E7
> >
> > I have two intended identical AS/400's with intended almost identical
> > environments. On one I can do an ADDPFTRF without problems.
> >
> > On the other it fails with CPF32C6 and the diagnostic CPD32E7  "Cause
> >  . . . . :   The trigger operation for file <file> in library <lib>,
> > for trigger *N in library *N, failed because of errors. The operation
> > was 1. The reason code is 6. ..... 06 - Cross Reference failed with
> > return code X'10A2' and diagnostic code 0".
> >
> > Any ideas about what the reason might be?