× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I see no problems with this - seems to me, that you could end up with a smaller file - only active records, for the most part, no wasted space for deleted records.

Just curious, do you have something in mind that might cause problems?

Vern

----- Original Message -----
What about re-using deleted record space with a file that is setup as
*NOMAX.


On Tue, Sep 10, 2013 at 1:33 PM, Needles,Stephen J <
SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

We are having an internal debate to reuse deleted records or not. The
most recent info I can find on the subject dates back to V5R4, we are on
V7R1.

Here are a few of the issues that I am aware of REUSEDLT(*YES) will...


- Cause arrival sequence processing to require attention.


- SQL cursors without an ORDER BY will give data in seemingly
random order according to the SQE's implementation of the request (don't
ask how we were bit by this :))


- May cause problems concerning access path maintenance, thus
potentially impacting performance (as of V5R4, this did not appear to be an
issue any longer?).


- Modernizing the DB to DDL (from DDS) will result in tables that
are REUSEDLT(*YES) by default as the CREATE TABLE SQL does not have
provision for restricting deleted row reuse.


- Does not completely exclude the need for periodic RGZPFM to be
run on the tables.

The question is... with enhancements to the SQE in V7R1 and such...will
REUSEDLT(*YES) provide a significant lessening of the need for RGZPFM
(perhaps annually or monthly versus weekly on select tables) without a
performance problem over time?

Steve Needles

________________________________
This communication, including attachments, is confidential, may be subject
to legal privileges, and is intended for the sole use of the addressee. Any
use, duplication, disclosure or dissemination of this communication, other
than by the addressee, is prohibited. If you have received this
communication in error, please notify the sender immediately and delete or
destroy this communication and all copies.

TRVDiscDefault::1201
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.