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

MXCI Commands
HP NonStop SQL/MX Reference Manual—544517-008
4-16
Considerations for DISPLAY USE OF ALL | INVALID
MODULES
object-name is case-sensitive. Wild-card characters are not allowed.
A valid example is:
TPCC.OE.CUSTOMER
ALL | INVALID
If you specify the INVALID clause, only the modules that are invalid, because of
DDL operations performed on the object-name (after the module was created),
will be listed (along with their source SQL filename). However, if the ALL clause is
specified, there will be no timestamp comparison and all the modules that are
dependent on the object-name will be displayed along with their source SQL file
name.
Considerations for DISPLAY USE OF ALL | INVALID MODULES
Object Types
DISPLAY USE OF tracks dependencies among 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
NonStop SQL/MX displays an error if a module cannot be loaded because the module
name is not valid, or the module name is valid but has been corrupted. Also, if the
module was compiled by an older compiler and does not contain the desired
information, like the source SQL file name that is needed for these new commands,
NonStop SQL/MX displays an error.
The error message in this case would be:
Note. The current design does not support SQL/MP aliases to know about the DDL changes
performed on the underlying SQL/MP object. Hence, this command can consider a module to
be valid even if the underlying SQL/MP object has been changed after the creation of the
module.
Version of these modules is incompatible for this command.
Note. All the modules that could not be read because of this error, are listed below the
above-mentioned error message.