RE: EDTOBJAUT in CL program?

[Jim Langston <jlangston@xxxxxxxxxxx>]

Eric,

I solved this problem with reorganizes taking too long by writing
a few CL programs.  Before I do anything, I grab a time stamp of when
the program started.  Then I load my database file with the members
in my library (DSPFD OUTFILE..) and start looking for members that
meet my reorganize criteria, currently set at 5% deleted records.

When I find a member to reorganize I reorganize it, and then look
at the time.  If an hour has passed since the program first started
I end the program.

I initally reorganized the largest file with the largest number of
deleted records on my system and found that it took roughly 1/2 hour
to reorganize.  So this 1 hour time frame gives a roughly 1 1/2 hours
that the program could run (it starts to reorganize a large file just
before the hour is up).

I run this every night starting at midnight after all the day end
processes have finished and just before the system is brought back
up.  I run this on 4 different data libraries, so in a worst case
scenario it could take up to 6 hours for all the libraries to be
reorganized, still giving us plenty of leeway to bring the system
back up before people start arriving.

I found, however, that the first few nights this ran it was hitting
the hour time limit.  After 3 or 4 days, though, the entire reorganize
of all 4 libraries is taking 15 minutes at the most.

If you want all the code, I'd be happy to supply it, just a few CLs.

Regards,

Jim Langston

-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@Sallybeauty.com]
Sent: Wednesday, October 17, 2001 11:11 AM
To: 'rpg400-l@midrange.com'
Subject: 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