SQL/MX Programming Manual for Java

Program and Module Management
HP NonStop SQL/MX Programming Manual for Java—523726-003
6-11
Managing Program Files
Managing Program Files
You probably develop, test, and debug applications on a development or test system
and then move the applications to a production system for actual use. On the
development system, you would typically test and tune applications by using a
database modeled after the database on the production system.
On the production system, program management tasks include:
•
Moving programs from development to production
•
Distributing programs across nodes
•
Ensuring proper name resolution
•
Assigning permissions for running database applications
•
Maintaining query plan validity
•
Migrating programs to subsequent releases of SQL/MX
•
Backing up and restoring programs
For more information, see the SQL/MX Installation and Management Guide.
Managing Modules
For an SQLJ application to run properly, you must maintain the modules of that
application in the /usr/tandem/sqlmx/USERMODULES directory. For information
about the consequences of mismanaged modules, see SQL/MX Compiler Errors on
page 4-5.
Module management tasks include:
•
Securing the modules
•
Checking module dependencies by using the DISPLAY USE OF command
•
Removing modules
For more information, see the SQL/MX Installation and Management Guide.
Note. SQL/MX does not support locally placed modules for SQLJ applications.