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

Owner: SUPER.SUPER
RedefTimestamp: 27 Nov, 2009 19:40:05 ( 212126091005566063
)
CreationTimeStamp: 27 Nov, 2009 19:40:17 ( 212126091017586769
)
LastModTimestamp: 19 Jan, 2011 16:35:46 ( 212162195146818505
)
LastOpenTimeStamp: 28 Jan, 2011 12:12:35 ( 212162956955297202
)
SMDtable: F
File Organization: Key-sequenced
Block Length: 4096
File Code: 563
Row Format: PACKED FORMAT
AuditCompress: T
Audited: T (If F, a Utility operation is in progress or has failed)
Broken: F
Buffered: T
ClearOnPurge: F
Corrupt: F (If T, a Utility operation is in progress or has failed)
CrashLabel: F
CrashOpen: F
IndexCompress: F
IncompletePartBoundChg: F (If T, a Utility operation is in progress or has failed)
RedoNeeded: F
RollfwdNeeded: F
UndoNeeded: F
UnreclaimedSpace: F (If T, a Utility operation is in progress or has failed)
Primary Extent Size: 128 Pages
Secondary Extent Size: 256 Pages
Max Extents: 512
Extents Allocated: 1
EOF: 32768
Index Levels: 1
Locating MXCS 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 MXCS_SCHEMA, which contains tables
used by MXCS and the user metadata tables. The MXCS schema tables are located on the same
volume as the system schema tables, but in the subvolume ZSD1. The underlying Guardian names
of the tables in this schema have preassigned names.
This example uses TACL commands to locate the MXCS schema tables.
1> fup copy $system.zsqlmx.mxanchor
SQLMX_MetaData_Loc=$DATA02
1 RECORDS TRANSFERRED
2> volume $data02.zsd1
3> files
$DATA02.ZSD1
ASSOC200 ASSOC201 DATASO00 DATASO01 ENVIRO00 ENVIRO01
NAME2I00 NAME2I01 RESOUR00 RESOUR01
4> fup info assoc200, detail
$DATA02.ZSD1.ASSOC200 28 Jan 2011, 12:25
SQL ANSI TABLE
ANSI NAME NONSTOP_SQLMX_DMR15.MXCS_SCHEMA.ASSOC2DS
RESOURCE FORK \DMR15.$DATA02.ZSD1.ASSOC201
SYSTEM METADATA \DMR15.$DATA02.ZSD0
VERSION 1200
TYPE K
Displaying System Schema Information 117