SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

MXCI Commands
HP NonStop SQL/MX Reference Manual—544517-008
4-15
DISPLAY USE OF ALL | INVALID MODULES
DISPLAY USE OF ALL | INVALID MODULES
Considerations for DISPLAY USE OF ALL | INVALID MODULES
Examples of ALL | INVALID MODULES
If the INVALID keyword is specified in the command, it displays all the dependent
modules along with their source SQL files for a given object that has become invalid
because of the DDL changes to the object, after the module was created. If the ALL
keyword is specified in the command, it displays all the dependent modules along with
their source SQL files for a given object..
NOE
directs NonStop SQL/MX to scan modules only in the local node and not the nodes
on the Expand network.
module-directory-path
is the path name of a directory, enclosed in single quotes.
module-directory-path 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.
All of these specifications are valid:
[module_dir 'd1']
[module_dir './d1']
[module_dir '../d1']
[module_dir '/usr/tandem/sqlmx/USERMODULES/../d1']
[module_dir '*']
[module_dir '/*']
[module_dir '*/d1']
[module_dir '/*/d1']
[module_dir 'd1/*']
[module_dir '/d1/*']
object-name
is the fully qualified name of an object, such as SQL/MX object (tables, indexes,
and SQL/MP aliases).
DISPLAY USE OF [NOE] [MODULE_DIR 'module-directory-path']
ALL|INVALID MODULES FOR 'object-name'
Note. The current DISPLAY USE OF command does not support module names to be
searched inside the guardian location (that is, path names starting with /G/). Similarly, this
command also does not support modules to be searched inside the guardian location.