RE: Persistent File Locks when using SQLRPGLE for Neverending Programs

The database manager wants to keep that ODP Open so it doesn't have to create it each time. If it's causing you problems somewhere you can use the ALCOBJ with the CONFLICT parameter set to *RQSRLS. That will close the ODP in your NEP. Also certain commands will close that ODP such as CLRPFM. You could also wrap that select statement with the SQL statements 'Connect Current' and 'Disconnect Current'... not a good idea but it would keep the ODP from staying open. Just out of curiosity, what problems is that causing?

~Zach
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rick DuVall
Sent: Tuesday, July 07, 2009 3:24 PM
To: RPG400-L@midrange. com
Subject: Persistent File Locks when using SQLRPGLE for Neverending Programs

Hi everybody,

I have a number of NEPs that used to

1. Open files
2. perform all processing
3. Close files
4. Sleep for x minutes
5. repeat.

Since we have begun using sql, these programs maintain file locks, on those
files opened by SQL, while sleeping.

Since the program is not run by a CL wrapper, there appears to be no
clear way to relinquish the locks during the sleep period. The only
SQL option that appears to apply is the CloSqlCsr and it only supports
*ENDMOD or *ENDACTGRP neither of which ever occur. Am I missing something?

Thanks!