RE: EDTOBJAUT in CL program?

Jim,

IMO, the "performance hit" is negligible (I could see no real change to
performance), and really shouldn't be the primary consideration.  For us,
the real issue was scheduling the reorgs.  When it started running over into
the next business day, keeping the users from using the system, the reuse
deleted records option was the only solution.  Timestamps (or possibly
journaling) would solve the time sequencing problem.

Eric DeLong
Sally Beauty Company
MIS-Sr. Programmer/Analyst
940-898-7863 or ext. 1863



-----Original Message-----
From: Jim Langston [mailto:jlangston@celsinc.com]
Sent: Wednesday, October 17, 2001 12:34 PM
To: 'rpg400-l@midrange.com'
Subject: Re: EDTOBJAUT in CL program?


Already used the GRTOBJAUT command as a submitted job so the
issue is resolved but to answer your question:

Yes, we have considered using the reuse deleted records function, but
dismissed it for a few reasons.
The main reason is that there is a performance hit when using deleted
records, albeit a slight one.
The second reason is that there are times when you want to know what were
the last records added to a database file, and the easiest way is to view
the file and scroll to the bottom and look.  This is a secondary reason,
however, and if it wasnt' for the performance hit we would be reusing
deleted records I think.

Regards,

Jim Langston

From: barsa@barsaconsulting.com
Subject: Re: EDTOBJAUT in CL program?
To: midrange-l@midrange.com
Date: Tue, 16 Oct 2001 21:55:30 -0400
Reply-To: midrange-l@midrange.com


I would compile with the appropriate user (object owner of QSECOFR)
adopting authority.  I would not attempt to change authorities for such an
event.

Why do a reorg?  Have you considered the reuse deleted records function?

Al

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.