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

Commands for Displaying Information
Topics in this subsection:
• “DISPLAY USE OF Command” (page 106)
• “mxtool INFO Command” (page 106)
• “SHOWLABEL Command” (page 106)
• “mxtool VERIFY command” (page 106)
• “SHOWDDL Command” (page 107)
DISPLAY USE OF Command
Use the MXCI DISPLAY USE OF command to display a list of modules and, for each module, to
display a list of dependent objects (tables and indexes) that are used by the module. This command
is especially useful for assessing the impact of DDL changes on module files before the changes
are performed.
By using the wild-card character (*), you can obtain information for a single module file or for a
set of module files.
This command has no impact during the execution of SQL queries.
For more information, see the SQL/MX Reference Manual.
mxtool INFO Command
Use the mxtool INFO command to display information about a database, including
SQL/MX-related information for a given Guardian file set list.
Because access to metadata is open to all users, anyone can run the mxtool INFO command.
For more information, see the SQL/MX Reference Manual.
SHOWLABEL Command
Use the MXCI SHOWLABEL command to display file-label information about SQL/MX objects
(tables, trigger temporary tables, views, and indexes), including the version and physical location.
The SHOWLABEL command also displays information about utility operations in progress that
affect the current state of a specified object. SHOWLABEL does not support SQL/MP objects or
SQL/MP aliases.
The SHOWLABEL command is similar to the SQL/MP FILEINFO, DETAIL command.
For more information, see the SQL/MX Reference Manual.
mxtool VERIFY command
Use the mxtool VERIFY command to detect and display inconsistencies in the database, including:
• Inconsistencies between an SQL/MX table, view, or stored procedure in Java (SPJ) and its
structural representation in the resource fork.
• Inconsistencies between an SQL/MX table, view, or SPJ and its structural representation in
the corresponding file labels.
• Inconsistencies between an SQL/MX table and its dependent indexes.
• Incorrectly defined dependent partitionable objects.
The mxtool VERIFY command is similar to the SQL/MP VERIFY command.
For more information, see the SQL/MX Reference Manual.
106 Querying SQL/MX Metadata