Mike - did you consider changing the sysval QQRYDEGREE (parallel
processing option) to *NONE.  If the change takes effect immediately
(that's a big IF), then the RQZPFM would only run on one of your 8
processors, but the down side is the reorg would have probably taken
much longer.  Just a thought..... 

Glenn Birnbaum
Platform Engineering, REI
253-395-8206
"Get Outside Yourself":  http://www.rei.com


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Sent: Tuesday, December 28, 2004 3:26 PM
To: MIDRANGE-L Listserv
Subject: RGZPFM Question


Folks,

 

Over the holiday one of our developers deleted 20,000,000 records from a
physical file as they were no longer needed.  This HUGE physical file (
even after 20 M records deleted) has 19 logicals built over it.  On
Sunday morning, a scheduled job ran (which was not planned), that did a
RGZPFM over this mess.  The end result was that it put an 870 8-Way
running SMP on it's
knees for 13 hours.   No matter what I tried, I could not get the
IDX-<access path name> running under QDBSRVxx jobs to ease up.

 

I did find the following Knowledge Base document (after the fact):

 

http://www-912.ibm.com/s_dir/slkbase.NSF/ce197905697c4c6086256a4f007978f
7/17
bb5f5d63273150862565c2007ce9e5?OpenDocument

 

Now for my $64 K questions:  Had I used the EDTRBDAP command, could I
have
put the active access path rebuilds on hold?   Would the active IDX
entries
have to have completed before the *HLD entries would have taken effect?
I
am trying to understand how I could have got this under control in the
least amount of time.

 

Any and all comment appreciated.  Thanks!

 

Mike Shaw 



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.