SQL/MX Programming Manual for Java

SQL/MX Programming Considerations

HP NonStop SQL/MX Programming Manual for Java—523726-003

4-14

External Qualification of the Module Name

When you customize the profile, you can externally set the target (or table set),

version, or group to create an externally qualified module name (for example,

CAT.SCH.GROUP^MODULE^TABLESET^VERSION). For more information, see Module

Management Naming on page 6-12.

Delimited Identifiers in the Module Name

You can delimit the catalog, schema, and module names within double quotation marks

("). Delimiting an identifier allows you to use these special elements in the module

name:

•

Special characters, except the @ sign, forward slash /, backward slash \, and

circumflex ^

•

Spaces, except trailing spaces, which are truncated

•

Case sensitivity

To preserve a double quotation mark in the file name, use two double quotes ("") to

specify one double quote ("). For information about delimited identifiers, see the

SQL/MX Reference Manual.

Examples

This MODULE directive specifies a module named "Çåts".Sch.Mød 2 for the ctx1

connection context:

#sql [ctx1] {MODULE """Çåts"""."Sch"."Mød 2 "};

Notice that two double quotes ("") specify one double quote (") in the file name, that

the delimited identifiers include European characters, and that the trailing spaces are

truncated.

If you do not delimit the module name, it is automatically converted to uppercase. For

example, this MODULE directive specifies a module named CAT.SCH.MOD for the

ctx2 connection context:

#sql [ctx2] {MODULE cat.sch.mod NAMES ARE ISO88591};

Note. To simplify module management, avoid using delimited identifiers in the module name.

When you specify the module name on the OSS command line, OSS requires you to use

escape sequences for special characters.