Re: current schema

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Rob,

I doubt you'd get the DCR through.  Defaulting the schema to the user name
is a SQL standard as I understand it.

Why not just the up the default on the connection property?

Charles


On Mon, Jan 18, 2016 at 9:01 AM, <rob@xxxxxxxxx> wrote:

> I created a test user, DUMMY.
> crtlib dummy
> CRTJOBD JOBD(DUMMY/DUMMY) INLLIBL(ERPLXF)
> CRTUSRPRF USRPRF(DUMMY) CURLIB(ERPLXF) JOBD(DUMMY/DUMMY)
> I connect using the old iNav.
> My list of schemas only shows QGPL.
> I execute the old Run SQL Scripts
> values current schema
> returns DUMMY
> It did this on my first attempt also.  BEFORE I created the library DUMMY,
> the job description and set the user profile to that job description.
>           CRTUSRPRF USRPRF(DUMMY) CURLIB(ERPLXF)
> Documentation says:  The initial value of CURRENT SCHEMA is the
> authorization ID of the current session user.  You've got to be freaking
> kidding me!
>
> http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzcursch.htm?lang=en
> So, to get an initial default schema of ERPLXF I have to name the user
> ERPLXF?
>
> I just want to default people's initial ODBC connection and not have to do
> a SET SCHEMA.
>
> Would this break anything of y'all if I submit a DCR to get IBM to change
> this to the user profiles Current library?
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.