SQL/MX Programming Manual for C and COBOL (G06.24+, H06.03+)

HP NonStop SQL/MX Programming Manual for C and COBOL—523627-004
17-1
17
Program and Module Management
Developing SQL/MX applications requires both a flexible and controlled development
environment. You need to be able to move program and module files from
development to a test or production environment. You also need to have control over
the development environment to effectively manage module files and modifications
made to those files. These needs become even more critical when you consider
parallel development on multiple versions of a particular SQL/MX application or when
you are testing, deploying, or upgrading SQL/MX applications in a geographically
distributed environment.
This section describes how to manage the files of C/C++ and COBOL applications:
•
Program Files on page 17-1
•
Managing Program Files on page 17-3
•
Managing Modules on page 17-6
•
Generating Locally or Globally Placed Modules on page 17-3
•
Module Management Behavior on page 17-7
•
Module Management Naming on page 17-8
Program Files
To make your SQL/MX embedded SQL source files, preprocessed files, module
definition files, and module files on both systems easier to find, use the naming
conventions listed in Table 17-1.
Note. NonStop SQL/MX does not support the ability to have different compiled modules of the
same application accessing NonStop SQL/MP and NonStop SQL/MX.
Table 17-1. File Naming Conventions (page1of2)
File Naming Convention
Embedded SQL source file in C source-file.sql
source-file.ec
Embedded SQL source file in C++ source-file.eC
source-file.ecc
source-file.ecpp
source-file.ecxx
source-file.ec++
Embedded SQL source file in COBOL source-file.ecob
source-file.ecbl
source-file.ECOB
source-file.ECBL
C preprocessed file source-file.c