Hi,
have you tried to close your results?
--> Edit --> Close All Results?
After having closed the results the file lock should be removed.
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: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Kurt Anderson
Gesendet: Thursday, 26. May 2011 00:17
An: Midrange Systems Technical Discussion
Betreff: RE: Run SQL Scripts and File Locks
When I bring up a file in STRSQL via Select, the moment I return to the
statement the lock is gone.
In Run SQL Scripts, once a statement is ran, I don't see how to get out of
that file short of performing another SQL Statement or closing the program.
(There isn't a way to close out a statement.) In addition to that, if I
open up a statement that was run into its own window b/c I want to view the
result set for that statement later, that seems to keep the file locked
(open, as you say) regardless if I actually run another statement or not.
Why is Run SQL Scripts keeping the open? Yes, thank you, a file that is
opened can't be cleared - that's obvious. What's not obvious is that Run
SQL Scripts is keeping the file open. How should I know that? How can I
prevent that?
STRSQL's exit message in 7.1 that suggests that we should be using Run SQL
Scripts. We saw that once before, and now SEU is being stabilized. Maybe
that's the future for STRSQL, so I'd like to get a good understanding of Run
SQL Scripts, and quite honestly I've been meaning to play with it for quite
some time.
Rob - turns out FOR FETCH ONLY doesn't change the situation. The job still
keeps the file open.
Thanks,
-Kurt
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, May 25, 2011 4:28 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Run SQL Scripts and File Locks
On 25-May-2011 13:31 , Kurt Anderson wrote:
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?
A file.mbr open in Job-A [except as psuedo-closed by SQL] should prevent
that same file.mbr from being cleared [by CLRPFM] in Job-N irrespective of
language used to open the file. For what reason would the Run SQL scripts
not be expected to effect the same?
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
