Re: Close SQL Cursor without Ending Module

On 05 Dec 2012 11:51, Charles Wilt wrote:

The real problem as Chuck alludes to is the "other" programs that
expect the file to not be in use... While that may have been the
case 20yrs ago, it is no longer true.

Let me guess...the "other" programs are doing a CLRPFM?

CLRPFM simply doesn't play well in a 24x7 connected systems
environment, IMHO.

I've replaced it with a SQL DELETE using a command front end
(CLRPFMSQL)..

FWiW the CLRPFM signals the close event so the request can complete as long as the job holding the pseudo-closed open actually closes the member in a timely fashion as does not immediately reopen, for example, if in a coded loop repeating the cursor opening so possibly beating the Clear PFM requester in the race to allocate; verified on v5r3.

One must keep in mind that the DELETE FROM TABLE_NAME honors override to database file [OVRDBF] that are scoped to the procedure performing that SQL DML request, but the CLRPFM does not. That impact can end up being a nice feature or a horrible flaw, depending on how\what is replaced by the noted CLRPFMSQL request; so... just a word of caution.

IBM i 7.1 Information Center -> Files and file systems -> Database file management -> Working with database files -> Overrides -> Overview:
_Overrides_
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/dm/rbal3eoscd.htm
"Effect of overrides on some commands

Some commands ignore overrides entirely, while others allow overrides only for certain parameters.

The following commonly used commands ignore overrides entirely:
...
CLRPFM
..."