RE: SQL select seems to be creating a lock on a file

Hi Chuck
My "attempting to update FILEA" means that the file is defined as update on the f-spec
The program doesn't time-out (production work, with time constraints), we have to end the program with the SQL so that the second program that updates the file can proceed.

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, July 23, 2013 12:44 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SQL select seems to be creating a lock on a file

On 23 Jul 2013 04:50, Alan Shore wrote:

Before I forget, we are on V5r4
I have an RPG program (PGM01) with embedded SQL The ONLY SQL in this
program is exec sql Set Option Commit = *None; exec SQL Select
count(*) Into :Reccount from FILEA; and there are NO F-specs for this
file (or one of its logical files) within PGM01

When another program (PGM02) is running, it is attempting to update
FILEA, but FILEA is locked by PGM01. The only way that I can get
PGM02 to continue is by ending PGM01 <<SNIP>>

Define explicitly what "attempting to update FILEA" means, and what is the error(s) [from the spooled joblog] when processing of the PGM02 is allowed to timeout, and if the timeout takes sufficiently long to allow DSPJOB OUTPUT(*PRINT) on the job running the PGM02 then obtain that to reveal minimally its awaited lock and program stack.