RE: RGZPFM

Ryan,
You'll want to look at the KEYFILE parameter of the RGZPFM command.  We
use the *FILE keyword to make sure the records are placed in the order
of the file's key.  This should give faster access.

Phil

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US)
Sent: Thursday, March 30, 2006 2:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: RGZPFM

Remove deleted records, yes.  Defragment the disks, no.  To defrag,
check the STRDSKRGZ command.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ryan Hunt
Sent: Thursday, March 30, 2006 2:21 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RGZPFM

We've had our AS400 for 6 years now and we've never performed an RGZPFM
on our production database. Our AS400 serves as our Enterprise Server
for a JDE OneWorld ERP so there is LOTS of activity on this thing.

I'm under the impression that the running RGZPFM again my production DB
library with no other parameters will remove deleted records from all
members and place the members/files into contiguous sectors of my disks
(thus making sequential I/O more likely).  Is this correct?

Thanks in advance.

Ryan Hunt



--
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 email is for the use of the intended recipient(s) only.  If you
have received this email in error, please notify the sender immediately
and then delete it.  If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this email without the author's
prior permission.  We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message.  We cannot accept
liability for any loss or damage caused by software viruses.  The
information contained in this communication may be confidential and may
be subject to the attorney-client privilege. If you are the intended
recipient and you do not wish to receive similar electronic messages
from us in future then please respond to the sender to this effect.