Re: Library lists vs Run SQL Scripts

On Thu, Mar 28, 2019 at 10:01 AM Rob Berendt <rob@xxxxxxxxx> wrote:

You did not indicate:
1 - whether or not you are using system or sql naming.
2 - whether or not you are using STRSQL or Run SQL Scripts
STRSQL sets current path to *LIBL either way. Run SQL Scripts does not.
This may be a recent change to STRSQL. I think I read this somewhere.

I failed to see anything in the settings for Run SQL Scripts to set this.
Running this
set path = *LIBL;
Seems to resolve it.
Not sure what issues missing SYSPROC and SYSIBMADM from the path may cause.

Actually, I did say "When connected using *SYS naming and "Default SQL
schema = Use library list from server job""

Run I connect with SQL Naming, I get
CURRENT_PATH = "QSYS","QSYS2","SYSPROC","SYSIBMADM","CWILT5"

With SYS naming, I get
CURRENT_PATH = *LIBL

Charles