VMS Help FORTRAN, /WARNINGS  *Conan The Librarian (sorry for the slow response - running on an old VAX)

  /[NO]WARNINGS[=(option[,...])]  D=/WARNINGS=(GEN,UNCAL,UNINI,UNREA,UNUS,USAGE)

  Controls whether the compiler generates certain classes of optional
  diagnostic messages.

  Specifying /WARNINGS without arguments has the same effect as
  specifying /WARNINGS=ALL; specifying /NOWARNINGS has the same
  effect as specifying /WARNINGS=NONE.

  The default is:  /WARNINGS=(NOALIGNMENT, NOAlpha,
  NODECLARATIONS, GENERAL, NOINLINE, NOTRUNCATED_SOURCE, NOULTRIX,
  UNCALLED, UNINITIALIZED, UNREACHABLE, UNUSED, USAGE, NOVAXELN).

1 - ALIGNMENT

  Controls whether the compiler produces diagnostic messages when
  variables or arrays (created in COMMON or EQUIVALENCE statements)
  are declared in such a way that they cross natural boundaries for
  their data size.  For example, a diagnostic message is issued if
  /WARNINGS=ALIGNMENT is in effect and the virtual address of a
  REAL*8 variable is not a multiple of 8.

  The default is /WARNINGS=NOALIGNMENT.

  It is recommended that you specify /WARNINGS=ALIGNMENT if data in
  COMMON blocks (or which appears in EQUIVALENCE declarations) is to
  be used in a vectorized program.

  Eliminating unaligned data can improve performance on VAX and is
  very important for applications being migrated to the Alpha
  architecture.

  Alignment warnings for specific STRUCTURE and COMMON declarations can
  be controlled using the /WARNINGS=ALIGNMENT qualifier on the
  CDEC$ OPTIONS directive.

2 - Alpha

  Controls whether the compiler generates diagnostics for language
  features not supported by Compaq Fortran 77 on Alpha systems.

3 - DECLARATIONS

  Controls whether the compiler issues diagnostic messages
  for any untyped data items used in the program.  This option acts
  as an external IMPLICIT NONE declaration.  See your language
  reference manual for more information on IMPLICIT NONE.

4 - GENERAL

  Controls whether the compiler issues diagnostic messages for
  W-level (warning) and I-level (informational) conditions.

  To suppress I-level and W-level diagnostic messages, specify the
  negative form of this qualifier (/WARNINGS=NOGENERAL).

5 - INLINE

  Controls whether the compiler prints informational diagnostic
  messages when it is unable to generate inline code for a reference
  to an intrinsic routine.  This option only applies to the BLAS
  intrinsics for which inline expansion is supported (all except
  xNRM2 and xROTG), and only if /BLAS=INLINE is in effect.

6 - TRUNCATED_SOURCE

  Controls whether the compiler issues a warning diagnostic message
  (EXCCHASRC) when it reads a source line with a statement field that
  exceeds the maximum column width.  The maximum column width is
  either 72 or 132 characters, depending on the value of the
  /EXTEND_SOURCE qualifier or the OPTIONS statement qualifier in
  effect.

  This option has no effect on truncation; lines that exceed the
  maximum column width are always truncated.

7 - ULTRIX

  Controls whether the compiler generates diagnostics for language
  features not supported by DEC Fortran on ULTRIX RISC systems.

8 - UNCALLED

  Controls whether the compiler generates informational diagnostics
  for statement functions that are defined but not called.

9 - UNINITIALIZED

  Controls whether the compiler generates diagnostics for uses of
  variables that the compiler believes do not have a defined value.

10 - UNREACHABLE

  Controls whether the compiler generates diagnostics for unreachable
  code.

11 - UNUSED

  Controls whether the compiler generates informational diagnostics
  for variables that are declared but not used.

12 - USAGE

  Controls whether the compiler generates informational diagnostics
  for questionable programming practices which, though allowed, often
  are the result of programming errors.

  The current set of questionable usages that the compiler detects
  are:

   o  A branch into a DO loop or IF block from outside the loop or
      block.  (Note that use of the Fortran 66 "extended range of a
      DO loop" feature will result in a diagnostic.)

   o  Passing an identifier, which had previously been used as an
      intrinsic routine, as an actual argument without naming that
      identifier in an INTRINSIC statement.

   o  Use of the DATE or IDATE intrinsics which may cause problems
      after the year 2000.

   o  Having a COMMON block with the same name as another global
      entity such as a SUBROUTINE, FUNCTION, ENTRY or EXTERNAL.

13 - VAXELN

  Controls whether the compiler issues diagnostics for language
  features not supported by Compaq Fortran 77 on a VAXELN system.

14 - ALL

  Causes the compiler to print all informational and warning
  messages, including warning messages for any untyped data items.

15 - NONE

  Suppresses all informational and warning messages.