SQL/MX Programming Manual for Java

Program and Module Management
HP NonStop SQL/MX Programming Manual for Java—523726-003
6-20
Grouping
Grouping
All the modules that are generated 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 a given application by using a single OSS
command.
Effect of the Group Attribute
The SQLJ customizer checks for the presence of a Module Group Specification String
(MGSS), which is a regular or delimited identifier that you specify on the SQLJ
command line. For information about how to specify an MGSS on the command line,
see Options for Module Management on page 5-28. For information about identifiers,
see the SQL/MX Reference Manual.
If you specify an MGSS on the SQLJ command line, the customizer embeds the
MGSS and a trailing circumflex (^) character in the processed, three-part module
name. For example:
CAT.SCH.GRP^MOD^TABLESET^VER
If you do not specify an MGSS on the command line but do specify either a Module
TableSet Specification String (MTSS) or a Module Version Specification String (MVSS),
the customizer embeds a ^ in the module name to represent the unspecified MGSS.
For example:
CAT.SCH.^MOD^TABLESET^VER
For other combinations of group, table set, and version attributes in module names,
see Table 6-1 on page 6-15.
How to Apply Grouping
These instructions explain how to group the modules of an application.
Assumptions
For the purpose of the examples, suppose that:
•
The SQLJ source file is named MyProg.sqlj.
•
The MODULE directives for each connection context in the SQLJ source file are:
#sql [ctx1] {MODULE cat.sch.MyProgCtx1 NAMES ARE ISO88591};
#sql [ctx2] {MODULE cat.sch.MyProgCtx2 NAMES ARE ISO88591};