One thing I would also try is to issue an FCONTROL 6 call against the
"black holed" file. FCONTROL 6 forces physical writes onto a disk file by
updating EOF and a few other stats. The drawback is that it has a
performance hit.

Christian

> -----Message d'origine-----
> De:   john edwards [SMTP:[log in to unmask]]
> Date: vendredi 30 juillet 1999 11:09
> A:    [log in to unmask]
> Objet:        Re: BLACK HOLE THEOREM
>
> Hi again
>
> Fascinating! This sounds like you really have found a hole. I would
> like to hear how this ends.
>
> Are you using COBOL IO verbs or intrinsic calls?
>
> Regards
> John
>
> --- "ABOOTORAB,MICHAEL (HP-PaloAlto,ex1)"
> <[log in to unmask]> wrote:
> > I forgot to mention a crucial piece of information.
> >
> > The black holes gets removed from the file a few
> > hours later (some times 8
> > hrs) and
> > the values replacing the null are what they are
> > supposed to be !
> >
> > This suggests that there is some sort of delayed
> > caching going on.
> >
> > After I posted this message , some one informed me
> > that , HP lab is aware of
> > this problem and they can actually duplicate it ( I
> > have the engineers name
> > and will
> > contact him).
> >
> > Another e-mail informed me that HP lab has a patch
> > for it(don't think so).
> > I'll post messages as I get them.
> >
> > I still think , regardless of the reason, it would
> > be a good idea to
> > change the blocking factor of the output file to 1.
> >
>
> _____________________________________________________________
> Do You Yahoo!?
> Free instant messaging and more at http://messenger.yahoo.com