× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If you want to delete an reuseable ODP within the same activation
group/module and
if you are using *SYS-Naming with unqualified data access, you simply may
change your library list, i.e. remove the data library and add it again.
The ODPs should get closed.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Zachary Johnson
Gesendet: Wednesday, 08. July 2009 21:04
An: RPG programming on the IBM i / System i
Betreff: 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!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.