Re: Should short name always be equal to long name for object_statistics?

I opened a ticket with this.
I'm getting the impression that someone totally misread the
Retrieve Short Name (QDBRTVSN) API
and thought they could use that to 'retrieve' the long name. (This API
was mentioned in the ticket.)

I think they now realize their mistake. I think they're going to take
baby steps to fix this. First step will be to get this to work for
'Table' objects. They will query against SYSTABLES to get the long table
name. (again, mentioned in the ticket). I'd like to think about this
before this really starts to get to be one huge CASE statement, or worse,
becomes a permanent restriction.

Keeping in mind that this is only for 'objects' so there must be some stub
in the qsys.lib file system outside of just the system catalogs.

*FILE, PF, search SYSTABLES
*FILE, LF, search SYSINDEX, failing that, search SYSVIEWS
*FILE, DDMF, search SYSALIASES (first you'll have to create that)
*PGM, search SYSPROCS, failing that, search SYSTRIGGERS
*LIB, search SYSSCHEMAS
*DTAARA, search SYSSEQUENCES
*SQLUDT, search SYSTYPES

CREATE ALIAS ROB.MYREALLYLONGALIAS FOR ROB.MYFILE (MYFILE)
Alias MYREALLYLONGALIAS created in ROB.
Object Type Library Attribute
MYREA00001 *FILE ROB DDMF

See this:
CREATE VIEW SYSALIASES AS (
SELECT DBXFIL as SYSTEM_ALIAS_NAME,
DBXLIB as SYSTEM_SCHEMA_NAME,
DBXLFQ as SYSTEM_SCHEMA_NAME_QUOTED,
DBXLB2 as SCHEMA_NAME,
DBXADB as RDB_NAME,
DBXALB as SCHEMA_NAME,
DBXAFL as TABLE_NAME,
DBXAMB as PARTITION_NAME,
DBXLFI as ALIAS_NAME,
DBXADB as ALIAS_RDB_NAME,
DBXALB as ALIAS_SCHEMA_NAME,
DBXAFL as ALIAS_TABLE_NAME,
DBXAMB as ALIAS_PARTITION_NAME
FROM qsys.qadbxref
WHERE dbxatr='AL'
)

I suppose if they don't accept SYSALIASES into the pmr I'll have to DCR
(and COMMON requirement) that.


Rob Berendt