RE: "call qcmdexc parm('CLRPFM ABC' 10.00000)" in an SQL script?

Dan,

What version are you on?

A quick test on my system (v5r4) didn't leave any deleted records in the
journal.

IIRC, v5r3 was the same.  Which makes make sense given the changes made
in v5r3 to which my first post talks about.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Monday, October 23, 2006 2:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: "call qcmdexc parm('CLRPFM ABC' 10.00000)" in an 
SQL script?

On 10/23/06, Wilt, Charles <CWilt@xxxxxxxxxxxx> wrote:

Why do you not want to use SQL's DELETE?

At v5r3 or higher using DELETE to remove all rows doesn't 

(necessarily)

have to hit every row.  In other words, it works similar to CLRPFM.

<snip>

Hi Charles,

Unless I've missed something, SQL's DELETE will not clear the 
file so that
there are no deleted records.  I just tried this on a file in 
my library
that no one else is using.  FWIW, Commitment control = *NONE. 
 We do not use
REUSEDLT in our shop.  Also, these particular files are not 
being journaled.

- Dan
-- 
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.