SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

(select schema_uid
from nonstop_sqlmx_figaro.system_schema.schemata
where schema_name = 'SALES' and cat_uid =
(select cat_uid
from nonstop_sqlmx_figaro.system_schema.catsys
where cat_name = 'my " catalog'
)
)
for read uncommitted access
order by object_name;
Note that "my "" catalog" is in external format, and 'SALES'and 'my " catalog'are in
internal format. The query does not work correctly if the internal and external names are incorrect.
Displaying System Schema Information
Topics in this subsection:
• “Locating System Schema Tables” (page 112)
• “Locating System Defaults Schema Tables” (page 114)
• “Locating MXCS Schema Tables” (page 117)
This table shows the locations of system schema information:
Schema Location on Each NodeSchema Table Type
NONSTOP_SQLMX_nodename.SYSTEM_SCHEMASystem schema tables
NONSTOP_SQLMX_nodename.SYSTEM_DEFAULTS_SCHEMASystem defaults schema tables
NONSTOP_SQLMX_nodename.MXCS_SCHEMAMXCS (ODBC) schema tables
For more information about system schema tables, see the SQL/MX Reference Manual.
Schema NONSTOP_SQLMX_nodename.SYSTEM_SQLJ_SCHEMA on each node contains only
an SPJ; no tables are associated with it. For more information, see the SQL/MX Reference Manual.
Locating System Schema Tables
On a local node, the anchor file $SYSTEM.ZSQLMX.MXANCHOR contains a pointer to the location
of the system catalog. The system catalog contains the SYSTEM_SCHEMA, which contains tables
that define the location of all the catalogs and schemas visible on the local node. The underlying
Guardian names of the tables in this schema have preassigned names and belong to the preassigned
subvolume ZSD0.
• This example uses the Guardian FILES command from a TACL prompt to list the locations of
the associated Guardian files for system schema tables on a local node.
NOTE: Beginning with SQL/MX Release 2.2, you can specify fully-qualified ANSI names
for SQL/MX tables and indexes in the FUP INFO command. FUP will perform a FUP INFO on
each of the corresponding Guardian files for that object as if the Guardian names had been
entered directly.
If you do use ANSI names with FUP INFO, the FUP command line cannot exceed 132
characters. Do not use ANSI names that span more than one input line and require an
embedded “&” line continuation character. One alternative would be to accept an input file
and read the ANSI names out of that file, limiting it to names of 255 characters or less because
EDIT files have that limit.
1> fup copy $system.zsqlmx.mxanchor
SQLMX_MetaData_Loc=$DATA02
1 RECORDS TRANSFERRED
112 Querying SQL/MX Metadata