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

HP NonStop SQL/MX Installation and Management Guide523723-004
B-1
B
Using Guardian Names With TMF,
RDF, and Measure
The TMF, RDF, and Measure subsystems provide important infrastructure and
management support to NonStop SQL/MX. Currently, however, the user interfaces to
these subsystems require Guardian physical file names, whereas SQL/MX tables can
be referenced by their ANSI logical names:
Guardian physical file name format:
[\node.][[$volume.]subvolume.]filename
ANSI logical file name format: [[catalog.]schema.]name
For subsystems that do not currently support ANSI names and do not use the
MXGNAMES utility, use the SHOWDDL or SHOWLABEL commands to return
Guardian names for the SQL/MX objects.
Conversion from ANSI logical to Guardian physical names is semiautomated by the
MXGNAMES utility. You can use the MXGNAMES utility (for example, in OBEY
command files) to generate the physical file names required by these subsystems from
the ANSI logical names of SQL/MX tables.
Using the MXGNAMES Utility
The MXGNAMES utility is a Guardian program run from a TACL prompt or OBEY
command file. Use MXGNAMES to generate the portions of the subsystem command
lines that contain Guardian file names. These portions can then be used directly to
form complete subsystem commands, without additional editing that might be
cumbersome and error-prone.
For example, to use TMF RECOVER FILES without MXGNAMES, you would have to:
1. Run SHOWDDL and capture output in an OSS edit file.
2. Use MXCI to obey the file and re-create the table.
3. Execute the RECOVER FILES command.
You can specify table names either on individual MXGNAMES command lines or in an
input file. In either case, one or more tables might not be found. If you specify a list of
table names, MXGNAMES processes valid table names in the list and returns a
warning to standard output for those not found.
For information about MXGNAMES command syntax and parameters, see the
SQL/MX Reference Manual.
For detailed descriptions of MXGNAMES error messages, see the SQL/MX Messages
Manual.