Re: Problem (or should I say feature!) when using interactiveSQL(STRSQL)...

["Steve Landess" <steve_landess@xxxxxxxxxxx>]

DOH!

Problem solved (see private message I received below):

<snip>

Hello Steve,

You may wish to forward this answer on to the list for archival purposes.

You wrote:
>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.

It does work, and it's working as designed (WAD).  When you start your 
SQL session have a very close look at the messages displayed in the 
session.  You should see something like:

Session was saved and started again.                 
STRSQL parameters were ignored.                      
Current connection is to relational database xxxxxxxx.

The second message is SQL6335 and the second-level text for that message 
explains that the command parameters were ignored because a saved session 
was restarted. If you want to use the command parameters you must firstly 
STRSQL and exit it with option 2=Exit without saving session (which 
actually deletes any saved session) and you must always exit with option 
2. Once you have a saved session the STRSQL parameters will always be 
ignored.

Although this is WAD I think the design is flawed.  The STRSQL command 
should have a parameter that allows you to ignore any saved session -- 
preferably without deleting it. Ideally the default values for the STRSQL 
parameters would be *SAME or *PRV.  You are unlikely to get the current 
behaviour changed but you might be succesful opening a DCR to add an 
Ignore saved session (IGNSSN) keyword added to STRSQL -- although given 
Rochester's infatuation with all things GUI I wouldn't hold my breath.

Regards,

</snip>