RE: Run SQL Scripts and File Locks

Ahhh, ok. I don't do a whole lot of CLRPFM unless I'm testing so I guess
I wouldn't really ever see this.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"jim@xxxxxxx" <jim@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/26/2011 09:32 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Run SQL Scripts and File Locks






Bryce

I've seen the behavior with FROG but only when trying to CLRPFM on the
file I'm currently viewing.

-Jim


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Thursday, May 26, 2011 8:00 AM
To: Midrange Systems Technical Discussion
Subject: RE: Run SQL Scripts and File Locks

I have not seen this behavior when using FROG. I use it to query
production files all the time and we have not had any issues....


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"jim@xxxxxxx" <jim@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/25/2011 04:46 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Run SQL Scripts and File Locks






Kurt

I use an open source SQL Utility called FROG and it does the same thing.
Seems to lock the file even when you were just running a select.
Unfortunately, I can only confirm the behavior and don't have a solution
for you.

-Jim

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Wednesday, May 25, 2011 3:31 PM
To: 'Midrange Systems Technical Discussion' (midrange-l@xxxxxxxxxxxx)
Subject: Run SQL Scripts and File Locks

Last weekend we upgraded to a Power 720 from a 520.
After using and exiting STRSQL for the first time in a session, a message
appears suggesting to give Run SQL Scripts a try, so I did.

The utility has its pros and cons, and I'm trying to use it so I can get
used to it. However today a job ran into an issue clearing a file because

apparently the SQL connection had the file in use. I had only been doing
SELECT statements in the SQL utility, so now I'm concerned. I showed a
couple of our power-users this tool, but if it's going to end up keeping a

file in use, I'm going to have to take it away.

Any thoughts on the matter?

Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems