Re: V5R2 Quality - a related question/issue

Michael,
Is it possible the part of the job stream that added the records did not
close the file? Could this not have anything to do with restore? The fact
that the OPNDBF and CLOF suddenly updated RTVMBRD, this seems more of an RPG
database update problem.
btw- I have never found that rtvmbrd or dspfd will force any records in a
buffer to update to disk. They report on whats in the physical file right
then.
Please post how this turns out.
jim

----- Original Message -----
From: "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 12, 2003 2:53 PM
Subject: RE: V5R2 Quality - a related question/issue


> Michael,
>
> I was wondering on the duration between adding the records and the
> returning of results by the RTVMBRD.  Now that you've stated that it was
> hours, it clearly sounds like a bug which should be reported to IBM and
> fixed by them.
>
> Regards,
> Andy Nolen-Parkhouse
>
> > On Behalf Of Mlpolutta@xxxxxxx
> > Subject: Re: V5R2 Quality - a related question/issue
> >
> > Jim,
> >
> > Thanks for your reply.  The restore was from a save file with
> > ACCPTH(*YES) on the save, so it should not have had to rebuild the
> > access path.
> >
> > Regardless, the part of our code that performed the check that was
> > failing was HOURS after the job had started, so even if the AP had
> > needed to be rebuilt, it should have been done by then.  Not to mention
> > that an earlier process in that job stream had added the records that
> > met the selection criteria.
> >
> > Finally - if the system could know that the AP was being built, I
> > believe that RTVMBRD should make me wait rather than LIE.
> >
> > jmho,
> > Michael
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>