|
<snip> 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, </snip> Steve, it works as designed ! The parameters on the STRSQL command are IGNORED if you have a saved SQL session: in this case, the options of the saved session are overriding the parameters, in order to stay consistent, when using F9 for example. In order to use the STRSQL parameters, you need to get rid of the SQL interactive session (select option 2 when leaving SQL) HTH Bonne réception/Best regards Richard THEIS iSeries Education, France
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.