SQL/MX 2.x Reference Manual (H06.04+)

MXCI Commands
HP NonStop SQL/MX Reference Manual—540440-003
4-10
Considerations for DISPLAY USE OF
/usr/tandem/sqlmx/USERMODULES or in the directory you specified with
module_dir.
module-name is case-sensitive.
You can look for similar values by specifying only part of the characters of
module-name combined with the “*” (asterisk) wild-card characters.
If you omit the module clause, DISPLAY USE OF will search for all modules.
All of these specifications are valid:
module 'CAT.SCH.M1'
module 'CAT.sch.*'
module 'CAT.*.*M'
object-name
is the fully qualified name of an object, such as a table or index name in SQL/MP
alias name or Guardian format, enclosed in single quotes. object-name can be
an SQL/MX object (tables, indexes, and SQL/MP aliases) or an SQL/MP object
(tables and indexes.) The node is required for SQL/MP objects.
object-name is case-sensitive. Wild-card characters are not allowed.
These are valid specifications:
object 'TPCC.OE.CUSTOMER'
object '\SAMDBCAT.$PERSNL.EMPLOYEE.SALARY'
If you omit the 'object object-name' clause, DISPLAY USE OF searches all
objects (tables and indexes) in the matching modules.
Considerations for DISPLAY USE OF
Object Types
DISPLAY USE OF tracks dependencies among these types of objects when they are
used with a static embedded SQL application written in either C, C++, COBOL, or
Java:
•
Compiled modules produced by the SQL/MX compiler
•
SQL/MX objects: tables, indexes, and SQL/MP aliases
•
SQL/MP objects: tables, and indexes
Information about the dependencies among these object types is derived from the
Explain section of the compiled module.
If the module could not be loaded because the module name is not valid or the module
name is valid but has been corrupted, NonStop SQL/MX displays an error. If the
module could not be loaded because the name is valid but the module cannot be
found, NonStop SQL/MX displays a warning.