COBOL Manual for TNS and TNS/R Programs

Program Compilation
HP COBOL Manual for TNS and TNS/R Programs—522555-006
11-12
CALL and ENTER Statement Processing: Overview
COBOL85 Compiler
By default, the COBOL85 compiler creates its temporary files on the current default
volume. The BINSERV and SYMSERV processes create their temporary files on the
volume where the target file is located, unless that volume is on another node. If the
volume is on another node, the BINSERV and SYMSERV processes create their
temporary files on the current default volume of the node on which they execute. For
example, suppose you are executing on \MYSYS and your default volume is $CURR. If
you execute the command:
COBOL85 /IN MYSRC, OUT $S.#MYLST/ \ALIEN.$FAR.XX.MYOBJ
the BINSERV and SYMSERV processes use $CURR for any temporary files, instead
of using volume $FAR on system \ALIEN.
NMCOBOL Compiler
By default, the NMCOBOL compiler creates its temporary files on the current default
volume. If called by the NMCOBOL compiler, the processes COBOLFE, UGEN, and
AS1 and the linker create their temporary files on the current default volume.
Specifying a Volume for Temporary Files
The PARAM SWAPVOL command specifies the volume on which the compiler and its
processes will create temporary files (if possible). It does not determine where the
operating system creates the compiler’s own swap file. For details, see PARAM
SWAPVOL.
The RUN option SWAP specifies one volume for both the temporary files that the
compiler and its processes will create and for the compiler’s own swap file. For more
information on SWAP and other RUN options, see the TACL Reference Manual.
CALL and ENTER Statement Processing: Overview
Any TNS HP COBOL program can call TNS HP COBOL programs with CALL
statements. Any TNS/R HP COBOL program can call TNS/R HP COBOL programs
with CALL statements. Any HP COBOL program can call non-COBOL programs with
ENTER statements. A HP COBOL program that runs in the CRE and was compiled
with the PORT directive can also call non-COBOL programs with X/Open CALL
statements.
In the CALL statement, the called program must be a COBOL program. It can be part
of the same compilation unit as the calling program, or it can be an external reference
to a COBOL program outside the compilation unit (but in the same object file). All
ENTER statements cause external references, because they call programs compiled
from source languages other than COBOL.