Alan,
A "mass purge" of database records could impact your applications performance if those physical files are not using REUSEDLT(*YES), so that a RGZPFM is needed to reorganize the PF member(s) to reclaim the space used by the deleted records.
After such a RGZPFM, any and all Logical File access paths over those PF members need to be updated; if the Logical Files (or physical files with keys) were not set to MAINT(*IMMED), this access path rebuild will occur on the next OPEN of that file. This could significantly slow down your applications, the first time each file is used after such a "re-org."
HTH,
Mark S. Waterbury
On Tuesday, July 6, 2021, 11:30:44 AM EDT, Alan Shore via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Thanks for your reply Vern
I am wading my way through the document that Jack sent, and it's a LOT of information to soak in
My problem is that a job that's presently running is still running from last night
Its been running for about 5 weeks or so - taking different times to complete - but NOTHING like it is today
However - in my analysis I have discovered that I believe a purge was recently run on a couple of the files
There are quite a number of deleted rows in these files
My question is - would the deleted rows impact SQL queries?
Forgive my ignorance as I haven't had a decent nights sleep in quite a few days and Im not thinking straight
Alan Shore
Solutions Architect
IT Supply Chain Execution
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx
'If you're going through hell, keep going.' --Winston Churchill
midrange.com
