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

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—523723-004
11-20
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. 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)
Information about dependencies between these object types is inferred from the
EXPLAIN section of the module. Use this information to identify tables and indexes that
are used by specific modules.
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.
For the syntax of the SQL/MX DISPLAY USE OF command, see the SQL/MX
Reference Manual.
Displaying All Modules and Dependent Objects
When you omit the module clause and the object clause, DISPLAY USE OF returns
information about all modules and dependent objects.
>>DISPLAY USE OF;
Module: CAT.SCH.CONSTRAINTM
Object: CAT.SCH.T24
Object: CAT.SCH.T25
Object: CAT.SCH.T26
Object: CAT.SCH.T27
Object: CAT.SCH.T28