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

COBOL Program Compilation
HP NonStop SQL/MX Release 3.2 Programming Manual for C and COBOL—663854-002
16-39
ecobol or nmcobol Utility: Using One Command for
All Compilation Steps

If the -Wsqlconnect= secure_warn is specified, a warning is returned.

Using the secure connection mode can increase the compilation time of
modules with embedded SQL/MX, by up to a factor of two. This is due to the
cost of performing encryption and decryption by using Secure Shell (SSH) or
Secure Sockets Layer(SSL), or both. (SQL/MX compilations use only SSH.)
HP_NSK_CONNECT_MODE
This environment variable is introduced in H06.25/J06.07 RVU and can be set to
any of the following values:

legacy

secure_quiet

secure_warn

secure_err
If the environment variable is set to any of the previous values, these values are used
by the compiler to set the connection mode. If the environment variable is set to any
other value, the compiler returns an error.
If both the –Wsqlconnect option is specified and the environment variable is set, the
value specified in the option overrides the value set in the environment variable.
SQL/MX Preprocessing
Use the -Wsqlmx[=args] command to invoke the SQL/MX preprocessor. For a full
description of how the OSS-hosted SQL/MX preprocessor works, see OSS-Hosted
SQL/MX COBOL Preprocessor on page 16-13.
Compiling COBOL Statements
Use the ecobol utility to compile COBOL statements in a preprocessed file to create a
TNS/E native object file. On systems running H06.05 or later RVUs, use the nmcobol
utility to compile COBOL statements in a preprocessed file to create a TNS/R native
object file.
Your application program can run in the OSS or Guardian environment. Use the
ecobol or nmcobol -Wsystype=oss option (which is the default) if you want your
application to be an OSS program. Use the ecobol or nmcobol
-Wsystype=guardian option if you want your application to be a Guardian program.
For more information, see Building SQL/MX Guardian Applications in the OSS
Environment on page 16-49.