SQL/MX 3.2 Programming Manual for C and COBOL (H06.25+, J06.14+)

Program and Module Management
HP NonStop SQL/MX Release 3.2 Programming Manual for C and COBOL—663854-002
17-13
Effect of Module Management Naming
For embedded SQL COBOL programs, the limit on a fully qualified three-part module
name is 160-characters because COBOL restricts nonumeric literals to at most 160
characters. For more information, see the HP COBOL85 for NonStop Systems Manual.
Examples
This example is invalid:
cat.sch.grp.modname.target.ver
However, this example is valid:
cat.sch."grp^modname^target^ver”
Note that the third part of the name (“grp^modname^target^ver”) is a delimited
identifier.
Effect of Module Management Naming
Module management features qualify the name for the module that is encoded in the
module definition file and the C-annotated source file. By changing the name of the
module in the module definition file, the name of the module-file is also changed.
Table 17-3 lists the effects of combinations of group (MGSS), target or table set
(MTSS), and version (MVSS) attributes on the module file name.
Specifying the search locations of the module files
You can specify the user module search locations in one of the following ways:

Using the Guardian or OSS DEFINE name — This option is supported for both
OSS and Guardian SQL/MX applications.

Using the OSS environment variable — This option is supported only for the OSS
SQL/MX applications.
Table 17-3. Module Management Naming
Group
Specified?
TableSet
Specified?
Version
Specified? Module Management Qualified Name
Yes Yes Yes CAT.SCH.GRP^MOD^TABLESET^VER
Yes Yes No CAT.SCH.GRP^MOD^TABLESET^
Yes No Yes CAT.SCH.GRP^MOD^^VER
Yes No No CAT.SCH.GRP^MOD^^
No Yes Yes CAT.SCH.^MOD^TABLESET^VER
No Yes No CAT.SCH.^MOD^TABLESET^
No No Yes CAT.SCH.^MOD^^VER
No No No CAT.SCH.MOD
A bold circumflex (^) represents a module management attribute (group, table set, or version) that you did not
specify during preprocessing.