SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)

Querying SQL/MX Metadata
HP NonStop SQL/MX Installation and Management Guide—544536-007
8-13
Locating System Schema Tables
•
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.
1> fup copy $system.zsqlmx.mxanchor
SQLMX_MetaData_Loc=$data08
2> volume $data08.zsd0
3> files
$DATA08.ZSD0
ALLUID00 ALLUID01 CATREF00 CATREF01 CATSYS00 CATSYS01
SCHEMA00 SCHEMA01 SCHREP00 SCHREP01
4> fup info alluid00, detail
$DATA08.ZSD0.ALLUID00 4 Dec 2003, 8:10
SQL METADATA TABLE
ANSI NAME NONSTOP_SQLMX_FIGARO.SYSTEM_SCHEMA.ALL_UIDS
RESOURCE FORK \FIGARO.$DATA08.ZSD0.ALLUID01
SYSTEM METADATA \FIGARO.$DATA08.ZSD0
VERSION 1200
TYPE K
FORMAT 2
CODE 564
EXT ( 256 PAGES, 1024 PAGES, MAXEXTENTS 512 )
PACKED REC 150
BLOCK 4096
KEY ( COLUMN 256, TYPE 0, LENGTH 0, DESC )
AUDIT
BUFFERED
AUDITCOMPRESS
OWNER 0,0
SECURITY (RWEP): *SQL
DATA MODIF: 3 Dec 2003, 15:16
CREATION DATE: 24 Oct 2003, 15:45
REDEFINITION DATE: 24 Oct 2003, 15:44
LAST OPEN: 3 Dec 2003, 15:15
EOF: 454656 (0.0% USED)
EXTENTS ALLOCATED: 1
INDEX LEVELS: 1
PARTITION ARRAY FORMAT2ENABLED
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.