Re: what is worklight and data studio

That is what I meant - that so far as SQL is concerned, these are not tables.

Nonetheless, the database component of Navigator DOES list them in the tables under a schema (library). Therefore, I will use Navigator, especially in a system that has a lot of older stuff.

And I don't want anyone to tell me to modernize - that decision is far above my pay grade and would have not even close to adequate ROI to justify it.

Later
Vern

On 11/19/2013 3:26 PM, CRPence wrote:

On 19-Nov-2013 12:09 -0800, Vernon Hamberg wrote:

DS will not show you tables that are created without DDS or DDL -
where you use CRTPF with record length - that makes it a bit
unhelpful.
I know, some might say those are not tables! Sobeit!
<<SNIP>>

Any SQL tooling dependent upon, implemented using, the SQL catalogs,
will suffer the same issue... as well as being unable to list the files
created in the QTEMP library. FWiW: The non-externally-described [aka
program-described] database files are not only those created using
RCDLEN() on the Create Physical File (CRTPF) command. And they are all
excluded from SYSTABLES [SQLTables() API] requests irrespective the
means used to create them, because of the WHERE clause logic which
includes DBXREL='Y'; i.e. only the potentially /relational/ database
files, those that are externally described by DDL or DDS, are provided
to a client\requester, and all conspicuously non-relational database
[physical or logical] *flat files* are not provided to a requester.