SQL/MX 3.2.1 Programming Manual for C and COBOL (H06.26+, J06.15+)

Program and Module Management
HP NonStop SQL/MX Release 3.2.1 Programming Manual for C and COBOL—663854-005
17-23
Grouping
If the environmental variable is set both for V1 and for V2, after the build script is run
for each version, an executable exists in subdirectories V1 and V2. These two module
files will coexist:
/usr/tandem/sqlmx/USERMODULES/CAT.SCH.^EMP_CNT_MODULE^^V1
/usr/tandem/sqlmx/USERMODULES/CAT.SCH.^EMP_CNT_MODULE^^V2
Versioning Example: COBOL Set Up
In this example, an environment variable ThisVersion is set, and a build script is
invoked:
mxsqlco empcnt.ecbl -c $ThisVersion/empcnt.cbl \
-m $ThisVersion/empcnt.m \
-g moduleVersion=$ThisVersion
If the environmental variable is set, once for V1 and once for V2, after the entire build
script finishes twice, an executable exists in two subdirectories V1 and V2. These
two module files will coexist:
/usr/tandem/sqlmx/USERMODULES/CAT.SCH.^EMP_CNT_MODULE^^V1
/usr/tandem/sqlmx/USERMODULES/CAT.SCH.^EMP_CNT_MODULE^^V2
Grouping
All the module files that are generated globally on a particular NonStop system are
stored in the /usr/tandem/sqlmx/USERMODULES directory, making it difficult to
identify, or group, the modules that are associated with a particular application. By
using the group attribute for module management, you can match module files to an
application and perform basic file management tasks more easily. For example, you
can list, copy, or delete all the modules associated with the given application by using a
single OSS command.
You can also use the group attribute to create module subsets and perform multiple
DISPLAY USE OF operations in much less time than it would take to run a single
DISPLAY USE OF operation on all the modules. For more information about grouping
modules to run multiple DISPLAY USE OF operations, see the SQL/MX Release 3.2
Management Manual.
Instead of using the group attribute for globally placed module management, you can
use the locally placed module features to generate modules in directories other than
USERMODULES. For more information on locally placed modules, see Generating
Locally or Globally Placed Modules on page 17-3.
Setting Up Grouping
Grouping requires you to:

Use the C/C++ or COBOL preprocessor option -g and specify the same Module-
Group-Specification-String (MGSS) name for each of the modules that
you want to manage as a group.
COBOL