FORTRAN Reference Manual

Program Compilation
FORTRAN Reference Manual—528615-001
9-20
Compiler Termination Codes
BINSERV does not include the XEP size in the code-area size. Also, note that
FORTRAN’s global storage size might differ from BINSERV’s: FORTRAN counts only
declared data; BINSERV includes run-time data structures in the global storage size.
Compiler Termination Codes
When the compilation ends, FORTRAN sends one of the following completion codes to
TACL:
You can use TACL to check completion codes, but this is generally useful only if you
are doing batch processing. In most cases, the simplest procedure is to check the
compiler listing to find out what happened.
Example 9-4. Compiler Listing—Completion Message
BINDER - OBJECT FILE BINDER - T9621D10 - (08JUN92) SYSTEM \USERS
Copyright Tandem Computers Incorporated 1982-1992
Object file \USERS.$TOOLS.FTNTOOLS.MYOBJ
TIMESTAMP 1992-09-05 23:06:05
47 Code pages
3 Primary data words
795 Secondary data words
4 Data pages
0 Resident code pages
0 Extended data pages
798 Top of stack location in words
1 Code segment
0 Binder Warnings
0 Binder Errors
0 Compiler errors
0 Compiler warnings
3 Primary data words
8 Secondary data words
2880 Maximum symbol table size in words
43 Lines of source text
0:00:59 Elapsed time
Completion Code Meaning
0 No errors or warnings.
1 No errors; one or more warnings. An object file was created.
2 Fatal errors; no object file was created.
3 Compilation did not complete. There may be an incomplete object file
or none at all.
Possible reasons for this are:
•
Your processor is not licensed for FORTRAN
•
A table overflowed
•
A serious I/O error occurred
5 Internal compiler error; contact your HP analyst.
8 One or more warning messages; an object file was created but its
name was changed. See the last page of the compiler listing for the
name.