Re: Net.Data locking a file

Jeop,

Thanks for the reply.    My net.data INI file already has:

DTW_SQL_ISOLATION DTW_SQL_NO_COMMIT

can you recommend another setting I can try?   The manuals are sorely
lacking in this regard.   None of our files are journaled.

Thanks,

Rick

On Apr 8, 2005 9:33 AM, Joep Beckeringh <joep@xxxxxxxxxxxxxxxxxxx> wrote:
> 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
> 
> --
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
> 
>