Open System Services Shell and Utilities Reference Manual (G06.28+, H06.05+)

User Commands (c) cobol(1)
• An object file in the format produced by the command cobol -c
• A library of object files in the format produced by archiving zero or more object files
using the ar command
• A library of object files produced by the Binder
• An executable file produced by the Binder
Output Files
Output files are object files or executable files (or both).
Standard Output
The standard output is a text file that contains the compiler listing, if generated.
Standard Error
Standard error is used for diagnostic and informational messages. If more than one
file operand
is specified, for each such file, "%s: \n",<file> might be written. These messages precede
the processing of each input file.
Environment Variables
The environment variables listed below affect the execution of cobol. The cobol utility and its
program components do not support locale variables.
AXCEL Determines the pathname of the Accelerator invoked by cobol. By default, the pro-
gram axcel in the directory /G/system/system is used.
BIND Determines the pathname of the Binder invoked by cobol. By default, the program
bind in the directory /G/system/system is used.
SQLCOMP
Determines the pathname of the NonStop SQL/MP compiler invoked by cobol.By
default, the program sqlcomp in the directory /G/system/system is used.
Operations
cobol is the driver program of the COBOL85 language compilation system. It accepts COBOL85
source files and generates binary files executable in the OSS environment. Depending on user-
specified flags, input file operands, and completion code at each stage, cobol invokes one or more
components of the compilation system. A program-generation process can involve the following
steps:
1. Each COBOL85 source module is compiled into an object module by the COBOL85
compiler.
2. Object modules are bound together, with additional library routines if necessary, by the
Binder into a single program file, unless flag -c or -Wnobind is specified. In this case,
processing stops after compilation of source modules.
3. If the program is to be run on TNS/R systems, the user can accelerate the program with
the Accelerator to obtain maximum performance.
4. If the program contains embedded SQL statements, it needs to be compiled by the Non-
Stop SQL/MP compiler as the final step.
With the exception of the cobol utility, all components are invoked as Guardian processes. cobol
provides terminal emulation (input from and output to) the controlling terminal for these
processes, if necessary. For Guardian processes that do not use cobol for terminal emulation or
are not interactive, the stop/continue type of OSS job control is not supported.
527188-007 Hewlett-Packard Company 2−57