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

C/C++ Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL523627-004
15-18
OSS-Hosted SQL/MX C/C++ Preprocessor
The preprocessing timestamp of the generated code must match the
preprocessing timestamp stored in the module. Use this option with caution and
only when you need to change the source text of the embedded SQL program
without SQL-compiling the generated code.
-d flag[=value]
specifies a flag macro for later use in the conditional compilation of the source file.
flag specifies the name of the macro and must be a valid C identifier. value can
be any integer value (positive or negative). You cannot put spaces around the
equal sign if an optional value is supplied.
The use of this option corresponds, for example, to the #define directive that
might be found in a source file (that is, #define foo 1, where 1 is the value
assigned to foo). The value can then be tested in an #if directive during
preprocessing.
You can specify the option more than once on the command line.
-h
enables processing of files specified in an #include directive that have a .h
extension. The default is to ignore these files.
-i pathname
specifies a directory path to be searched for a file specified in an #include
directive. The source path is searched first.
You can specify this option for a maximum of 20 paths.
-x
directs the preprocessor to refrain from emitting embedded module definitions into
the annotated output source file.
-g {moduleGroup[=module-group-specification-string]
|moduleTableSet[=module-tableset-specification-string]
|moduleVersion[=module-version-specification-string]
|moduleCatalog[=module-catalog-name]
|moduleSchema[=module-schema-name]
}
specifies the arguments for qualifying the name given to the compiled module file.
If you use this option, you must supply at least one of the five module management
attributes. If you want to specify more than one attribute, repeat the entire -g option
for each attribute. These attribute values are used to qualify the name of the
compiled module file. See File Naming Conventions on page 17-1.
To use the -g option, you must supply a value in conjunction with the
moduleGroup, moduleTableSet, moduleVersion, moduleCatalog, or
moduleSchema attribute. The value must immediately follow the equal sign, and
the equal sign must immediately follow the attribute keyword. The value can use