Re: Logical file keyed by active RRN

if you cannot alter the file (like it belongs to a package)
then consider adding a trigger to write new records to another file that
keeps your order,
and some way to get back to orig record in triggered file.
The trigger will then allow you to chgpf the orig file to reuse deleted
records
to get all that dead space back.
RGZPFM not an option for files in use 24x7.
jim

----- Original Message ----- 
From: "Wilt, Charles" <CWilt@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, July 22, 2005 12:36 PM
Subject: RE: Logical file keyed by active RRN


> David,
>
> I think you're SOL.
>
> The RRN is the RRN.  If you're reading by RRN then the DB is going to have
to page past all the deleted records.
>
> I suppose there is some reason why you can't do a RGZPFM?
>
> I'd follow Albert's suggestion of adding a timestamp field and creating
the logical over that.
>
> As an added benefit, you could then use REUSEDLT(*YES).
>
> Charles Wilt
> --
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of David C. Shea
> > Sent: Friday, July 22, 2005 11:37 AM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Logical file keyed by active RRN
> >
> >
> > I want to create a logical file where the key is RRN.  I only want
> > active records listed in this logical.
> >
> >
> >
> > The goal here is to be able to SETLL by key of RRN and have
> > the pointer
> > positioned either at the next record in the file or EOF.
> >
> >
> >
> > This is for a situation where there could be millions of
> > deleted records
> > in the file.  Doing a regular SETLL by RRN and a READ could end up
> > scanning thru millions of deleted records.
> >
> >
> >
> > Doing a SETLL on a logical file _keyed_ by RRN might do the trick.
> >
> >
> >
> > Any thoughts??
> >
> >
> >
> >
> >
> >
> >
> > -- 
> > 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.
> >
> >
>
> -- 
> 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.
>
>