Re: SQL Insert Row as last RRN

CHGPF MYSQLTABLE REUSEDLT(*NO) with the default SRCFILE(*NONE) will leave the database physical *FILE as an SQL TABLE. That changed file will merely have a specific attribute that is inconsistent with the typical SQL TABLE. Depending on how the file is used, the performance impact for having effected that change to row reuse could be either positive or negative. The bigger issue typically is the maintenance to the database file which would typically be performed outside and thus possibly in conflict with the application; i.e. reorganizing the data with RGZPFM.

Regards, Chuck

On 12-Sep-2011 08:33 , Kurt Anderson wrote:

If you do the CHGPF thing as mentioned below you are changing the
object from a Table to a Physical File. This may be of little
importance to you, however doing this would be considered a
performance impact (although probably minimal).

Schutte, Michael on Monday, September 12, 2011 9:42 AM wrote:

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Fsqlp%2Frbafyinsert.htm

A table created by SQL is created with the Reuse Deleted Records
parameter of *YES. This allows the database manager to reuse any
rows in the table that were marked as deleted. The CHGPF command
can be used to change the attribute to *NO. This causes INSERT to
always add rows to the end of the table.