×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




The good news is that it is consistently wrong, even on V5R2.  Meaning 
that if you do a 
STRSQL NAMING(*sys)
and your session attributes are set to *SQL, you'll get the same error.

Perhaps session attributes needs another option.  Instead of just *SYS and 
*SQL they need a *whatevertheheckthecommandwassetto

You can try submitting a DCR.  Since more people will be getting the SQL 
development kit (and Quickplace, Sametime, TSM, etc) with the Enterprise 
Edition this could mean one of two things:  1)  More people are using this 
product, thus it needs more support,  2) Less people are buying this 
product individually, thus it's dead as nails.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Steve Landess" <steve_landess@hotmail.com>
Sent by: midrange-l-bounces@midrange.com
01/29/2003 12:42 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     <midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        Problem (or should I say feature!) when using 
interactive SQL (STRSQL)...


All - 

I was just playing around, and used the command STRSQL NAMING(*SQL) to 
start interactive SQL.

Then, on the "Enter SQL Statements" screen, I tried:
 Select *from SJL001.CUSMST

I received the error "Qualified object name CUSMST not valid." (SQL5016). 

If I use F13, then option 1 (Change Session Attributes), the value of 
"Naming convention" says *SYS...so I changed it to *SQL.  Then, when I use 
the above SQL statement, it runs fine.   What's the deal?  Does STRSQL 
NAMING(*SQL) _not_ work?  I tried this on a V4R4 system at work (TL01072) 
and on my V5R1 (TL03007) AS/400 at home...same results on both systems.

This is just a minor detail, but sign me-

Confused in Austin,

Steve Landess
(512) 423-0935
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.