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

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—544536-007
11-19
Checking Module Dependencies with DISPLAY USE
OF
7. Alternatively, the SUPER.SUPER user can make sure that all modules in the local
directory can be written to only by their respective owners by entering:
chmod 0644 /usr/local-directory/*
8. Make sure that all future modules that you create are writable only by you or the
owner of the local directory owner by entering:
umask 022
This command makes module files (and OSS files in general) that the user creates
readable by all but writable only by the module owner and creator.
9. Put this command into the shell script you use to invoke the SQL/MX compiler:
umask 022
mxcmp $*
Checking Module Dependencies with DISPLAY USE OF
Use the SQL/MX DISPLAY USE OF command to display usage information about user
modules and their dependent objects that are used in conjunction with static
embedded SQL applications. It can also be used to know the source SQL file (with
path), from which the module file was created. It can also be used to know all the
modules which became invalid due to DDL changes on the dependent objects (after
the module was created).
DISPLAY USE OF tracks dependencies between modules and:
•
SQL/MX objects (for example, tables, indexes, and SQL/MP aliases)
•
SQL/MP objects (for example, tables and indexes)
•
Source SQL files.
Information about dependencies between these object types is inferred from the
EXPLAIN section of the module and also from Source name section and object names
section. Use this information to identify tables and indexes that are used by specific
modules.Please note that the "DISPLAY USE OF SOURCE" and "DISPLAY USE OF
ALL|INVALID MODULES FOR" commands do not use the EXPLAIN architecture. Also,
these commands do not work on SQL/MP objects (tables and index), though they do
provide information about the SQL/MP aliases.
Use the DISPLAY USE OF command to:
•
Assess the impact of DDL changes on module files before changes are performed.
•
Identify modules that need to be recompiled.
•
Identify the source SQL files which are to be used for compilation.
•
Identify the Invalid modules due to DDL operations on their dependent Objects.
Note. The SQL/MX version of DISPLAY USE OF has a different implementation than that of
the SQL/MP version of DISPLAY USE OF. The SQL/MX version gives information only for
compiled modules.