SQL/MX 3.x Installation and Management Guide (H06.22+, J06.11+)

Querying SQL/MX Metadata
HP NonStop SQL/MX Installation and Management Guide—640325-001
8-12
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=$DATA02
1 RECORDS TRANSFERRED
2> volume $data02.zsd0
$DATA02 ZSD0 3> files
$DATA02.ZSD0
CATREF00 CATREF01 CATSYS00 CATSYS01 SCHEMA00 SCHEMA01
SCHREP00 SCHREP01
4> fup info catref00, detail
$DATA02.ZSD0.CATREF00 27 Jan 2011, 19:05
SQL METADATA TABLE
ANSI NAME
NONSTOP_SQLMX_DMR15.SYSTEM_SCHEMA.CAT_REFERENCES
RESOURCE FORK \DMR15.$DATA02.ZSD0.CATREF01
SYSTEM METADATA \DMR15.$DATA02.ZSD0
VERSION 1200
TYPE K
FORMAT 2
CODE 564
EXT ( 128 PAGES, 256 PAGES, MAXEXTENTS 512 )
PACKED REC 30
BLOCK 32768
KEY ( COLUMN 0, ASC ,
COLUMN 1, ASC )
AUDIT
BUFFERED
AUDITCOMPRESS
OWNER -1
SECURITY (RWEP): *SQL
DATA MODIF: 27 Jan 2011, 16:42, OPEN
CREATION DATE: 27 Nov 2009, 19:40
REDEFINITION DATE: 27 Nov 2009, 19:40
LAST OPEN: 27 Jan 2011, 17:14
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.