Re: stupid SQL message...

On 11/11/2010 1:09 PM, Tommy Holden:

But that's kinda my point Paul. I rarely need the other functionality
(read bloat) that comes with opening Navigator so it's an unnecessary
resource hog. Since I rarely use any of the application why fire it up
daily "just in case"? I almost always have a telnet session up so it's
just faster for me. To each his/her own, the only real nice thing about
using scripts is the ability to copy/paste without having to modify the
statements so they fit STRSQL's command/statement line.

I'm on IBM i 5.4 so I don't see those messages. Although I don't use
STRSQL either. I wrote my own command line version back when we were
still writing flowcharts on cave walls with blackened sticks. So I
haven't any advice on the message. I'd call IBM Support and report it
as a bug.

Having said that, my colleagues don't share my... preference, and so
they tend to use SQL Scripts in iNav. That means I have to occasionally
use SQL Scripts. I rarely, if ever fire up the full blown iNav.
Somewhere along the line, iSeries Access bound the PC file extension
'.SQL' to the SQL Script runner. To open my colleagues' scripts (which
are stored on the i) all I need to do is use Windows Explorer to
navigate to the IBM i directory and double click on the script file.
The Script runner fires up and Bob's yer uncle.

Hope that helps someone.
--buck