Compaq Fortran provides certain include library modules in the text library FORSYSDEF.TLB. Users can create a text library and populate it with include library modules (see Section 2.4). Within a library, text library modules are identified by a library module name (no file type).

To include a text library module, the INCLUDE statement specifies the name of the library module within parentheses, as follows:

INCLUDE '(name)'

You can specify the library name before the library module name in the INCLUDE statement. For example:

INCLUDE 'MYLIB(PROJINC)'

Use one of the following methods to access a source library module in a text library:

• Specify only the name of the library module in an INCLUDE statement in your Compaq Fortran source program. You use FORTRAN command qualifiers and logical names to control the directory search for the library.
• Specify the name of both the library and library module in an INCLUDE statement in your Compaq Fortran source program.
• When the INCLUDE statement does not specify the library name, you can define a default library by using the logical name FORT$LIBRARY.
• When the INCLUDE statement does not specify the library name, you can specify the name of the library using the /LIBRARY qualifier on the FORTRAN command line that you use to compile the source program.

When the library is named in the INCLUDE statement, the FORTRAN command searches various directories for the named library, similar to the search for an include file.

Compaq Fortran allows you to use multiple methods to specify which directories are searched for named text libraries:

• You can request that the Compaq Fortran compiler search either in the current process default directory or in the directory where the source file resides that references the text library. To do this, specify the /ASSUME=NOSOURCE_INCLUDE (process default directory) or /ASSUME=SOURCE_INCLUDE qualifier (source file directory).
• You can specify one or more additional directories for the compiler to search by using the /INCLUDE=directory qualifier.
• You can specify one or more additional directories for the compile to search by defining the logical name FORT$INCLUDE. To search multiple additional directories with FORT$INCLUDE, define it as a search list. Like other logical names, FORT$INCLUDE can be for:
  • A system-wide location (such as a group or system logical name)
  • A private or project location (such as a process, job, or group logical name)
• You can prevent the compiler from searching in the directory specified by the FORT$INCLUDE logical name by using the /NOINCLUDE qualifier.

The Compaq Fortran compiler searches directories in the following order:

1. The current process default directory or the directory that the source file resides in (depending on whether /ASSUME=SOURCE_INCLUDE was specified)
2. Each directory specified by the /INCLUDE qualifier
3. The directory specified by the logical name FORT$INCLUDE (unless /NOINCLUDE was specified).

You can specify /LIST or /NOLIST after the library module name. For example:

INCLUDE 'PROJLIB(MYINC)/LIST'

You can also specify the /SHOW=INCLUDE or /SHOW=NOINCLUDE qualifier to control whether source lines from included files or library modules appear in the listing file (see Section 2.3.40).

For More Information:

• On the /ASSUME=[NO]SOURCE_INCLUDE qualifier, see Section 2.3.6.
• On the /INCLUDE qualifier, see Section 2.3.22.
• On creating and using text libraries, see Section 2.4.

When the INCLUDE statement does not specify the library, you can specify additional text libraries to be searched on the FORTRAN command line or by defining a logical name. The order in which the compiler searches for a library file follows:

• Specify the library name on the FORTRAN command line, appended with the /LIBRARY positional qualifier. The /LIBRARY qualifier identifies a file specification as a text library.
  Concatenate the name of the text library to the name of the source file and append the /LIBRARY qualifier to the text library name (use the plus sign (+)) separator. For example:

  $ FORTRAN APPLIC+DATAB/LIBRARY

  
  Whenever an INCLUDE statement occurs in APPLIC.FOR, the compiler searches the library DATAB.TLB for the source text module identified in the INCLUDE statement and incorporates it into the compilation.
  When more than one library is specified on a FORTRAN command line, the Compaq Fortran compiler searches the libraries each time it processes an INCLUDE statement that specifies a text module name. The compiler searches the libraries in the order specified on the command line. For example:

  $ FORTRAN APPLIC+DATAB/LIBRARY+NAMES/LIBRARY+GLOBALSYMS/LIBRARY

  
  When the Compaq Fortran compiler processes an INCLUDE statement in the source file APPLIC.FOR, it searches the libraries DATAB.TLB, NAMES.TLB, and GLOBALSYMS.TLB, in that order, for source text modules identified in the INCLUDE statement.
  When the FORTRAN command requests multiple compilations, a library must be specified for each compilation in which it is needed. For example:

  $ FORTRAN METRIC+DATAB/LIBRARY, APPLIC+DATAB/LIBRARY

  
  In this example, Compaq Fortran compiles METRIC.FOR and APPLIC.FOR separately and uses the library DATAB.TLB for each compilation.
  If the text library is not in the current process default directory, specify the device and/or directory. For example:

  $ FORTRAN PROJ_MAIN+$DISK2:[PROJ.LIBS]COMMON_LIB/LIBRARY

  
  Instead of specifying the device and directory name, you can use the /ASSUME=SOURCE_INCLUDE and /INCLUDE qualifiers and FORT$INCLUDE logical name to control the directory search.

• After the compiler has searched all libraries specified on the command line, it searches the default user library (if any) specified by the logical name FORT$LIBRARY. When you want to define one of your private text libraries as a default library for the Compaq Fortran compiler to search, consider using the FORT$LIBRARY logical name.
  For example, define a default library using the logical name FORT$LIBRARY before compilation, as in the following example of the DCL command DEFINE:

  $ DEFINE FORT$LIBRARY $DISK2:[LIB]DATAB $ FORTRAN PROJ_MAIN

  
  While this assignment is in effect, the compiler automatically searches the library $DISK2:[LIB]DATAB.TLB for any include library modules that it cannot locate in libraries explicitly specified, if any, on the FORTRAN command line.
  You can define the logical name FORT$LIBRARY in any logical name table defined in the logical name table search list LMN$FILE_DEV. For example:

  $ DEFINE /GROUP FORT$LIBRARY $DISK2:[PROJ.LIBS]APPLIB.TLB $ FORTRAN PROJ_MAIN

  
  If the name is defined in more than one table, the Compaq Fortran compiler uses the equivalence for the first match it finds in the normal order of search---first the process table, then intermediate tables (job, group, and so on), and finally the system table. If the same logical name is defined in both the process and system logical name tables, the process logical name table assignment overrides the system logical name table assignment.
  If FORT$LIBRARY is defined as a search list, the compiler opens the first text library specified in the list. If the include library module is not found in that text library, the search is terminated and an error message is issued.
  The logical name FORT$LIBRARY is recognized by both Compaq Fortran 77 and Compaq Fortran.

• When the Compaq Fortran compiler cannot find the include library modules in libraries specified on the FORTRAN command line or in the default library defined by FORT$LIBRARY, it then searches the standard text library supplied by Compaq Fortran. This library resides in SYS$LIBRARY with a file name of FORSYSDEF.TLB and simplifies calling OpenVMS system services.
  SYS$LIBRARY identifies the device and directory containing system libraries and is normally defined by the system manager. FORSYSDEF.TLB is a library of include library modules supplied by Compaq Fortran. It contains local symbol definitions and structures required for use with system services and return status values from system services.
  For more information on the contents of FORSYSDEF, see Appendix D.

You can specify /LIST or /NOLIST after the library module name. For example:

INCLUDE '(MYINC)/NOLIST'

You can also specify the /SHOW=INCLUDE or /SHOW=NOINCLUDE qualifier to control whether source lines from included files or library modules appear in the listing file (see Section 2.3.40).

For More Information:

• On the /ASSUME=[NO]SOURCE_INCLUDE qualifier, see Section 2.3.6.
• On the /INCLUDE qualifier, see Section 2.3.22.
• On creating and using text libraries, see Section 2.4.

The output produced by the compiler includes the object and listing files. You can control the production of these files by using the appropriate qualifiers on the FORTRAN command line.

The production of listing files depends on whether you are operating in interactive mode or batch mode:

• In interactive mode, the compiler does not generate listing files by default; you must use the /LIST qualifier to generate the listing file.
• In batch mode, the compiler generates a listing file by default. To suppress it, you must use the /NOLIST qualifier.

For command procedures that compile the application in either batch or interactive mode, consider explicitly specifying /NOLIST (or /LIST).

The compiler generates an object file by default. During the early stages of program development, you may find it helpful to use the /SYNTAX_ONLY or /NOOBJECT qualifiers to prevent the creation of object files until your source program compiles without errors. If you omit /NOOBJECT, the compiler generates object files as follows:

• If you specify one source file, one object file is generated.
• If you specify multiple source files separated by commas, each source file is compiled separately, and an object file is generated for each source file.
• If you specify multiple source files separated by plus signs, the source files are concatenated and compiled, and one object file is generated.

You can use both commas and plus signs in the same command line to produce different combinations of concatenated and separate object files (see the examples of the FORTRAN command at the end of this section).

To name an object file, use the /OBJECT qualifier in the form /OBJECT=file-spec. Otherwise, the object file has the file name of its corresponding source file and a file type of OBJ. By default, the object file produced from concatenated source files has the name of the first source file. All other file specification fields (node, device, directory, and version) assume the default values.

When creating object files that will be placed in an object library, consider using the /SEPARATE_COMPILATION qualifier, which places individual compilation units in a source file as separate components in the object file. This minimizes the size of the routines included by the linker as it creates the executable image. However, to allow more interprocedure optimizations, use the default /NOSEPARATE_COMPILATION.

For More Information:

• On creating and naming object files, see Section 2.2.6.1 and Section 2.3.30.
• On the /SEPARATE_COMPILATION qualifier, see Section 2.3.38.
• On using object libraries, see Chapter 3.

The following examples show the use of the FORTRAN command.

2.2.6.1 Naming the Object File

The following FORTRAN command compiles the Compaq Fortran free-form source file (CIRCLE.F90) into an object file:

$ FORTRAN /OBJECT=[BUILD]SQUARE /NOLIST [Return] _File: CIRCLE

The source file CIRCLE.F90 is compiled, producing an object file named SQUARE.OBJ in the [BUILD] directory, but no listing file.

2.2.6.2 Compiler Source Checking Only (No Object File)

The following FORTRAN command examines Compaq Fortran fixed-form source file (ABC.FOR) without creating an object file:

$ FORTRAN /NOOBJECT ABC.FOR

The source file ABC.FOR is compiled, syntax checking occurs, but no object file is produced. The /NOOBJECT qualifier performs full compilation checking without creating an object file.

2.2.6.3 Requesting a Listing File and Contents

The following FORTRAN command compiles Compaq Fortran free-form source file (XYZ.F90) and requests a listing file:

$ FORTRAN /LIST /SHOW=INCLUDE /MACHINE_CODE XYZ.F90

The source file XYZ.F90 is compiled, and the listing file XYZ.LIS and object file XYZ.OBJ are created. The listing file contains the optional included source files (/SHOW=INCLUDE) and machine code representation (/MACHINE_CODE).

The default is /NOLIST for interactive use and /LIST for batch use, so consider explicitly specifying either /LIST or /NOLIST.

2.2.6.4 Compiling Multiple Files

The following FORTRAN command compiles the Compaq Fortran free-form source files (AAA.F90, BBB.F90, and CCC.F90) into separate object files:

$ FORTRAN/LIST AAA.F90, BBB.F90, CCC.F90

Source files AAA.F90, BBB.F90, and CCC.F90 are compiled as separate files, producing:

• Object files named AAA.OBJ, BBB.OBJ, and CCC.OBJ.
• Listing files named AAA.LIS, BBB.LIS, and CCC.LIS.

The default level of optimization is used (/OPTIMIZE=LEVEL=4), but interprocedure optimizations are less effective because the source files are compiled separately.

The following FORTRAN command compiles the Compaq Fortran fixed-form source files XXX.FOR, YYY.FOR, and ZZZ.FOR into a single object file named XXX.OBJ:

$ FORTRAN XXX.FOR+YYY.FOR+ZZZ.FOR

Source files XXX.FOR, YYY.FOR, and ZZZ.FOR are concatenated and compiled as one file, producing an object file named XXX.OBJ. The default level of optimization is used, allowing interprocedure optimizations since the files are compiled together (see Section 5.1.2). In interactive mode, no listing file is created; in batch mode, a listing file named XXX.LIS would be created.

The following FORTRAN command compiles the Compaq Fortran free-form source files AAA.F90, BBB.F90, and CCC.F90 into two object files:

$ FORTRAN AAA+BBB,CCC/LIST

Two object files are produced: AAA.OBJ (comprising AAA.F90 and BBB.F90) and CCC.OBJ (comprising CCC.F90). One listing file is produced: CCC.LIS (comprising CCC.F90), since the positional /LIST qualifier follows a specific file name (and not the FORTRAN command). Because the default level of optimization is used, interprocedure optimizations for both AAA.F90 and BBB.F90 occur. Only interprocedure optimizations within CCC.F90 occur.

The following FORTRAN command compiles the Compaq Fortran free-form source files ABC.F90, CIRC.F90, and XYZ.F90, but no object file is produced:

$ FORTRAN ABC+CIRC/NOOBJECT+XYZ

The /NOOBJECT qualifier applies to all files in the concatenated file list and suppresses object file creation. Source files ABC.F90, CIRC.F90, and XYZ.F90 are concatenated and compiled, but no object file is produced.

2.2.6.5 Requesting Additional Compile-Time and Run-Time Checking

The following FORTRAN command compiles the Compaq Fortran free-form source file TEST.F90, requesting all possible compile-time diagnostic messages (/WARN=ALL) and run-time checking (/CHECK=ALL):

$ FORTRAN /WARNINGS=ALL /CHECK=ALL TEST.F90

This command creates the object file TEST.OBJ and can result in more informational or warning compilation messages than the default level of warning messages. Additional run-time messages can also occur.

2.2.6.6 Checking Fortran 90 or 95 Standard Conformance

The following FORTRAN command compiles the Compaq Fortran free-form source file PROJ_STAND.F90, requesting compile-time diagnostic messages when extensions to the Fortran 90 language are detected without creating an object file:

$ FORTRAN /STANDARD=F90 /NOOBJECT PROJ_STAND.F90

This command does not create an object file but issues additional compilation messages about the use of any nonstandard extensions to the Fortran 90 standard it detects.

To check for Fortran 95 standard conformance, specify /STANDARD=F95 instead of /STANDARD=F90.

2.2.6.7 Requesting Additional Optimizations

The following FORTRAN command compiles the Compaq Fortran free-form source files (M_APP.F90 and SUB.F90) as a single concatenated file into one object file:

$ FORTRAN /OPTIMIZE=(LEVEL=5,UNROLL=3) M_APP.F90+SUB.F90/NOLIST

The source files are compiled together, producing an object file named M_APP.OBJ. The software pipelining optimization (/OPTIMIZE=LEVEL=5) is requested. Loops within the program are unrolled three times (UNROLL=3). Loop unrolling occurs at optimization level three (LEVEL=3) or above.

For More Information:

• On linking object modules into an executable image (program) and running the program, see Chapter 3.
• On requesting debugger symbol table information, see Section 4.2.1.
• On requesting additional directories to be searched for module files or included source files, see Section 2.3.22 and Section 2.4.
• On the FORTRAN command qualifiers, see Section 2.3.

FORTRAN command qualifiers influence the way in which the compiler processes a file. In some cases, the simplest form of the FORTRAN command is sufficient. Use optional qualifiers when needed.

You can override some qualifiers specified on the command line by using the OPTIONS statement. The qualifiers specified by the OPTIONS statement affect only the program unit where the statement occurs. For more information about the OPTIONS statement, see the Compaq Fortran Language Reference Manual.

2.3.1 FORTRAN Command Qualifier Syntax

Normal DCL parsing rules apply to the FORTRAN command, allowing you to abbreviate qualifier names and keywords as long as they are unique. For example, the following use of the FORTRAN command to specify the /ALIGNMENT qualifier as NATURAL and the /LIST qualifier is valid:

$ FORTRAN /ALIG=NAT /LIS EXTRAPOLATE.FOR

When creating command procedures, avoid using abbreviations for qualifiers and their keywords. Compaq Fortran might add new qualifiers and keywords for a subsequent release that makes an abbreviated qualifier and keyword nonunique in a subsequent release.

If you specify multiple keywords for a qualifier, enclose the keywords in parentheses:

$ FORTRAN /WARN=(ALIGN, DECLARATION) EXTRAPOLATE.FOR

To concatenate source files, separate file names with a plus sign (+) instead of a comma (,) (see Section 2.2.2).

2.3.2 Summary of FORTRAN Command Qualifiers

Table 2-1 lists the FORTRAN Command qualifiers, including their default values.

Section 2.3.3 through Section 2.3.48 describe each qualifier in detail.

Table 2-1 FORTRAN Command Qualifiers

Qualifier	Default
/ALIGNMENT or /NOALIGNMENT or /ALIGNMENT= rule class = rule ( class = rule [, ...]) ALL (or NATURAL) NONE (or PACKED) where: class = COMMONS RECORDS STRUCTURES and rule = NATURAL PACKED STANDARD 2 [NO]MULTILANGUAGE 2	/ALIGNMENT=(COMMONS=(PACKED 1, NOMULTILANGUAGE), RECORDS=NATURAL)
/ANALYSIS_DATA[=filename] or /NOANALYSIS_DATA	/NOANALYSIS_DATA
/ARCHITECTURE= GENERIC HOST EV4 EV5 EV56 PCA56 EV6	/ARCHITECTURE=GENERIC
/NOASSUME or /ASSUME= [NO]ACCURACY_SENSITIVE [NO]ALTPARAM [NO]BUFFERED_IO [NO]BYTERECL [NO]DUMMY_ALIASES [NO]FP_CONSTANT [NO]INT_CONSTANT [NO]MINUS0 [NO]SOURCE_INCLUDE [, ...] ALL NONE	/ASSUME=(ACCURACY_SENSITIVE 1, ALTPARAM, NOBUFFERED_IO, NOBYTERECL, NODUMMY_ALIASES, NOFP_CONSTANT, NOINT_CONSTANT, NOMINUS0, NOSOURCE_INCLUDE)
/AUTOMATIC or /NOAUTOMATIC	/NOAUTOMATIC
/BY_REF_CALL=( routine-list)	No default
/NOCHECK or /CHECK= [NO]BOUNDS [NO]FORMAT [NO]FP_EXCEPTIONS [NO]OUTPUT_CONVERSION [NO]OVERFLOW [NO]POWER [NO]UNDERFLOW [, ...] ALL NONE	/CHECK=(NOBOUNDS, FORMAT 3, NOFP_EXCEPTIONS, OUTPUT_CONVERSION 3, NOOVERFLOW, POWER, NOUNDERFLOW)
/CONVERT= BIG_ENDIAN CRAY FDX FGX IBM LITTLE_ENDIAN NATIVE VAXD VAXG	/CONVERT=NATIVE
/D_LINES or /NOD_LINES	/NOD_LINES
/DEBUG or /NODEBUG or /DEBUG= [NO]SYMBOLS [NO]TRACEBACK [, ...] ALL NONE	/DEBUG=(NOSYMBOLS, TRACEBACK)
/DIAGNOSTICS[=filename] or /NODIAGNOSTICS	/NODIAGNOSTICS
/DOUBLE_SIZE= 64 128	/DOUBLE_SIZE=64
/ERROR_LIMIT= n or /NOERROR_LIMIT	/ERROR_LIMIT=30
/EXTEND_SOURCE or /NOEXTEND_SOURCE	/NOEXTEND_SOURCE
/F77 or /NOF77	/F77
/FAST	No default
/FLOAT= D_FLOAT G_FLOAT IEEE_FLOAT	/FLOAT=G_FLOAT 4
/GRANULARITY= BYTE LONGWORD QUADWORD	/GRANULARITY=QUADWORD
/IEEE_MODE= FAST UNDERFLOW_TO_ZERO DENORM_RESULTS	/IEEE_MODE=FAST
/INCLUDE= directory [, ...] or /NOINCLUDE	/NOINCLUDE
/INTEGER_SIZE= 16 32 64	/INTEGER_SIZE=32 4
/LIBRARY	No default
/LIST[=file-spec] or /NOLIST	/NOLIST (interactive) /LIST (batch)
/MACHINE_CODE or /NOMACHINE_CODE	/NOMACHINE_CODE
/MATH_LIBRARY= ACCURATE FAST	/MATH_LIBRARY=ACCURATE 1
/MODULE=directory or /NOMODULE	/NOMODULE
/NAMES= UPPERCASE LOWERCASE AS_IS	/NAMES=UPPERCASE
/OBJECT[=file-spec] or /NOOBJECT	/OBJECT
/OLD_F77	Omitted
/OPTIMIZE or /NOOPTIMIZE or /OPTIMIZE= LEVEL= n INLINE= NONE MANUAL SIZE SPEED ALL NOINLINE LOOPS PIPELINE TUNE= GENERIC HOST EV4 EV5 EV56 PCA56 EV6 UNROLL= n [, ...]	/OPTIMIZE (same as /OPTIMIZE= (LEVEL=4, INLINE=SPEED, NOLOOPS, NOPIPELINE, TUNE=GENERIC, UNROLL=0))
/PAD_SOURCE or /NOPAD_SOURCE	/NOPAD_SOURCE
/REAL_SIZE= 32 64 128	/REAL_SIZE=32
/RECURSIVE or /NORECURSIVE	/NORECURSIVE
/NOREENTRANCY or /REENTRANCY= ASYNC NONE THREADED	/REENTRANCY=NONE
/ROUNDING_MODE= NEAREST CHOPPED DYNAMIC MINUS_INFINITY	/ROUNDING_MODE=NEAREST
/SEPARATE_COMPILATION or /NOSEPARATE_COMPILATION	/NOSEPARATE_COMPILATION
/SEVERITY=WARNINGS= WARNING ERROR STDERROR	/SEVERITY=WARNINGS=(WARNING)
/SHOW or /NOSHOW or /SHOW= [NO]INCLUDE [NO]MAP [, ...] ALL NONE	/SHOW=(NOINCLUDE, MAP )
/SOURCE_FORM= FREE FIXED	Depends on file type (F90 for free form and FOR or F for fixed form)
/STANDARD= F90 F95 or /NOSTANDARD	/NOSTANDARD
/SYNCHRONOUS_EXCEPTIONS or /NOSYNCHRONOUS_EXCEPTIONS	/NOSYNCHRONOUS_EXCEPTIONS
/SYNTAX_ONLY or /NOSYNTAX_ONLY	/NOSYNTAX_ONLY
/TIE or /NOTIE	/NOTIE
/VERSION	Omitted
/VMS or /NOVMS	/VMS
/WARNINGS or /NOWARNINGS or /WARNINGS= [NO]ALIGNMENT [NO]ARGUMENT_CHECKING [NO]DECLARATIONS [NO]GENERAL [NO]GRANULARITY [NO]TRUNCATED_SOURCE [NO]UNCALLED [NO]UNINITIALIZED [NO]UNUSED [NO]USAGE [, ...] ALL NONE	/WARNINGS=(ALIGNMENT, NOARGUMENT_CHECKING, NODECLARATIONS, GENERAL, GRANULARITY, NOTRUNCATED_SOURCE, UNCALLED, UNINITIALIZED, NOUNUSED, USAGE )

Table 2-2 shows the functional groupings of the FORTRAN command qualifiers and the section in which they are described in more detail.

Table 2-2 FORTRAN Command Flags and Categories

Category	Flag Name and Section in this Manual
Code generation for specific Alpha chip	/ARCHITECTURE (see Section 2.3.5)
Convert Nonnative Data Files	/CONVERT (see Section 2.3.10) /ASSUME=BYTERECL (see Section 2.3.6) Also see Chapter 9.
Data Size	/DOUBLE_SIZE (see Section 2.3.14) /INTEGER_SIZE (see Section 2.3.23) /REAL_SIZE (see Section 2.3.34) Also see Chapter 8.
Data Storage and Recursion	/AUTOMATIC (see Section 2.3.7) /RECURSIVE (see Section 2.3.35)
Debugging and Symbol Table	/D_LINES (see Section 2.3.11) /DEBUG (see Section 2.3.12) Also see Chapter 4.
Floating-Point Exceptions and Accuracy	/ASSUME=([NO]ACCURACY_SENSITIVE, [NO]FP_CONSTANT, [NO]MINUS0) (Section 2.3.6) /CHECK=([NO]FP_EXCEPTIONS, [NO]POWER, [NO]UNDERFLOW) (see Section 2.3.9) /DOUBLE_SIZE (see Section 2.3.14) /FAST (see Section 2.3.18) /FLOAT (see Section 2.3.19) /IEEE_MODE (see Section 2.3.21) /MATH_LIBRARY (see Section 2.3.27) /REAL_SIZE (see Section 2.3.34) /ROUNDING_MODE (see Section 2.3.37) /SYNCHRONOUS_EXCEPTIONS (see Section 2.3.43)
Floating-Point Format in Memory	/FLOAT (see Section 2.3.19)
Language Compatibility	/F77 (see Section 2.3.17) /ALIGNMENT=COMMONS=STANDARD (see Section 2.3.3) /ASSUME=( [NO]ALTPARAM, [NO]DUMMY_ALIASES, [NO]INT_CONSTANT) (see Section 2.3.6) /BY_REF_CALL (see Section 2.3.8) /OLD_F77 (see Section 2.3.31) /PAD_SOURCE (see Section 2.3.41) /SEVERITY (see Section 2.3.39) /STANDARD (see Section 2.3.42) /VMS (see Section 2.3.47)
Language-Sensitive Editor Use	/DIAGNOSTICS (see Section 2.3.13)
Listing File and Contents	/LIST (see Section 2.3.25) /MACHINE_CODE (see Section 2.3.26) /SHOW (see Section 2.3.40) Also see Section 2.6.
Module File Searching and Placement; Include File Searching	/INCLUDE (see Section 2.3.22) /ASSUME=[NO]SOURCE_INCLUDE (see Section 2.3.6) /LIBRARY (see Section 2.3.24) /MODULE (see Section 2.3.28) Also see Section 2.2.3 (modules), Section 2.2.4 (include files), and Section 2.4 (text libraries).
Multithreaded Applications	/REENTRANCY (see Section 2.3.36)
Object File Creation, Contents, Naming, and External Names	/OBJECT (see Section 2.3.30) /NAMES (see Section 2.3.29) /SEPARATE_COMPILATION (see Section 2.3.38) /SYNTAX_ONLY (see Section 2.3.44) /TIE (see Section 2.3.46)
Performance Optimizations and Alignment	/ALIGNMENT (see Section 2.3.3) /ASSUME=(NOACCURACY_SENSITIVE, NODUMMY_ALIASES) (see Section 2.3.6) /ARCHITECTURE (see Section 2.3.5) /FAST (see Section 2.3.18) /MATH_LIBRARY (see Section 2.3.27) /OPTIMIZE (see Section 2.3.32) Also see Chapter 5.
Recursion and Shared Access to Data	/GRANULARITY (see Section 2.3.20) /RECURSIVE (see Section 2.3.35) /REENTRANCY (see Section 2.3.36) /WARNINGS=GRANULARITY (see Section 2.3.48)
Source Code Analyzer Use	/ANALYSIS_DATA (see Section 2.3.4)
Source Form and Column Use	/D_LINES (see Section 2.3.11) /EXTEND_SOURCE (see Section 2.3.16) /PAD_SOURCE (see Section 2.3.33) /SOURCE_FORM (see Section 2.3.41) /WARNINGS=TRUNCATED_SOURCE (see Section 2.3.48)
Warning Messages and Run-Time Checking	/CHECK (see Section 2.3.9) /IEEE_MODE (see Section 2.3.21) /ERROR_LIMIT (see Section 2.3.15) /SEVERITY (see Section 2.3.39) /WARNINGS (see Section 2.3.48) Also see the qualifiers related to "Floating-Point Exceptions and Accuracy" in this table.