Rick,

To optimize performance the SQL engine keeps files open as long as it can, even when a cursor is explicitly closed. First thing to do is try to allocate the file from within another job with ALCOBJ OBJ((library/file *FILE *EXCL)) CONFLICT(*RQSRLS). If this succeeds (don't forget to deallocate) the other lock has gone away; it was just the SQL engine. If it doesn't, you will have to delve into the SQL settings of your Net.Data configuration file.

Joep Beckeringh


rick baird wrote:
hey all,

Why does a simple SQL select statement lock a file when run from net.data?

I deployed my first production net.data macro - a simple vendor
lookup.  It runs a select statement (joining 3 files) and displays the
results.

After running the macro from a browser, the request processor job
retains the lock on the file.

Why doesn't it release the file when it's finished?   Is there any way
to force it to let go of the file?

Thanks,

Rick


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.