Re: SQL Closing Files

I second Charles' comment on SQL DELETE in place of CLRPFM.

This was so effective for our nightly operations we made a
local command to have an easy alternative.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Charles Wilt
Sent: Thursday, December 26, 2013 1:51 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: SQL Closing Files

There's your real problem...

You've got a process designed back in the 80's that expects to have the
system all to itself...

Rather than handicap the new functionality, consider updating the old
process and/or system systems.

Consider one or more of the following
- adding an ALCOBJ CONFLICT(*RQSRLS) to your month-end process
- changing the WAITFILE parm of the PF/LF to something other than *IMMED
- Use non-exclusive operations, for example instead of CLRPFM use SQL
DELETE

HTH,
Charles