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

COBOL Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL—544617-003
16-23
Running the COBOL Compiler and Linker
invokeCatalog
sets the catalog for unqualified objects inside the invoke clause as catalog-
name. If a catalog is specified using the Control Query Default Catalog or
Declare Catalog, this attribute has no effect. The maximum size of the
invokeCatalog attribute is 128 characters.
invokeSchema
sets the schema for unqualified objects inside the invoke clause as schema-
name. If a schema is specified using the Control Query Default Schema or
Declare Schema, this attribute has no effect. The maximum size of the
invokeSchema attribute is 128 characters.
Examples—mxsqlco
Run the SQL/MX COBOL preprocessor using the mxsqlco command. This example
creates an annotated source file and module definition file:
mxsqlco sqlprog.ecob -c sqlprog.cbl -m sqlprog.m -g \
moduleTableSet=T1
This example creates a single-file, annotated output source file that contains an
embedded module definition:
mxsqlco sqlprog.ecob -c sqlprog.cbl \
-g moduleGroup=INVENTORY -g moduleVersion=V2
Running the COBOL Compiler and Linker
The HP NonStop COBOL compilers translate source code into machine language that
is specific to a particular NonStop system architecture. The type of COBOL compiler
that you use to compile your SQL/MX program determines the NonStop system and
environment where you can run the program.
Table 16-1 lists the COBOL compilers, the environments where you can run the
compilers, and the environments where you can run the compiled programs.
Note. TNS/R native compilation tools are available on systems running H06.05 or later RVUs.