RE: CPYF FROMKEY/TOKEY using packed key field

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

Thanks, Charles. Good to know (we are still on V5R1 here, but looking to
upgrade soon).

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Tuesday, November 1, 2005 8:58 AM
To: Midrange Systems Technical Discussion
Subject: RE: CPYF FROMKEY/TOKEY using packed key field

 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lapeyre, Francis
Sent: Monday, October 31, 2005 3:22 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: CPYF FROMKEY/TOKEY using packed key field

Or, as long as you are using SQL, 

DELETE FROM file 

will delete the records using SQL.  Unlike a CPYF, it does not clear the
member, so deleted records are still taking up storage until you reorganize.

<snip>

Note: this is no longer always true at v5r3.

>From the SQL Reference:
"DELETE Performance: An SQL DELETE statement that does not contain a WHERE
clause will delete all rows of a table. In this case, the rows may be
deleted using either a clear operation (if not running under commitment
control) or a change file operation (if running under commitment control).
If running under commitment control, the deletes can still be committed or
rolled back. This implementation will be much faster than individually
deleting each row, but individual journal entries for each row will not be
recorded in the journal."

Some limitations apply, check the manual for more info.

HTH,

Charles