Re: Using SQL SEQUENCE for Next Number Operations

I checked the help text in Navigator as to what they can use. Some of that looks interesting - *LIBL is a default for default schema, even when using *SQL naming. So I googled "sql default library jdbc iseries" and go to the spot on InfoCenter that explains things - as I cite here -

If *SQL Naming* is being used:

* The first entry (unless it is *LIBL) becomes the default SQL schema
* When the first entry is *LIBL, the second entry becomes the default
SQL schema
* When you do not set this property or when it contains only *LIBL,
the user profile becomes the default SQL schema

There's more for when SYS naming is used.

Some things are used for resolving unqualified tables and the like, other things are used for resolving functions and stored procedures. Details in the SQL manuals, of course, and several knowledge base articles.

No contradiction to Chuck's response, just clarifying some interesting terms and settings.

HTH
Vern

On 10/20/2013 5:18 PM, CRPence wrote:

On 10/20/13 2:14 PM, Vernon Hamberg wrote:

<<SNIP>> I believe that with *SQL naming, JDBC driver can be set to
use more than the "user name" library - take a look at the JDBC
settings in the SQL statement processor in Navigator for an example.

Take care not to confuse the CURRENT PATH with the CURRENT SCHEMA.

The unqualified sequence will be "implicitly qualified by the default
schema" [though testing shows /current schema/ as qualifier instead].
The unqualified sequence-name is *not* located via the PATH. The
default schema for *SYS naming is the library list (*LIBL). There is no
similar Library List concept in the *SQL naming for the SCHEMA, only for
the PATH.