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-28
Backing Up and Restoring Programs
SQL compiling the application as specified in the SQL/MX Programming Manual
for C and COBOL.
4. If a module definition file was not found for a Release 2.1 or Release 2.0
application in Step 1, preprocess the application’s source file from Release 1.8 to
generate a module definition file.
5. From Release 1.8, host-language compile the Release 1.8 annotated source file
created in Step 4. For more information about host language compilation, see the
SQL/MX Programming Manual for C and COBOL.
6. From Release 1.8, use mxcmp to SQL compile every Release 2.1 or Release 2.0
application’s module definition file to generate a new globally placed module. New
module files are automatically placed in the
/usr/tandem/sqlmx/USERMODULES directory.
7. Remove the shared local copies of the now unused modules. See Removing
Modules on page 11-22.
Backing Up and Restoring Programs
Make backing up and restoring programs part of both the day-to-day maintenance of
program files and the high-level strategy for backing up and restoring the entire
database. The former should include periodically storing copies of programs to safe
locations (such as another disk, magnetic tape, or another system). As a rule, you
should back up programs before you make major changes to the database.
For information about the strategies and procedures for backing up and restoring
database files, see Using Backup and Restore 2 for Database Recovery on page 5-27.