Controls whether an individual compilation unit becomes a separate  module
   in an object file.

   The format of the /SEPARATE_COMPILATION qualifier is as follows:

      /[NO]SEPARATE_COMPILATION

   Specifying /SEPARATE_COMPILATION will cause the  compiler  to  place  each
   routine  in  a  separate module within the output object file.  This is HP
   BASIC for OpenVMS VAX behavior.

   Specifying /NOSEPARATE_COMPILATION groups individual compilation units  as
   a single module in an object file.

   When creating modules  for  use  in  an  object  library,  consider  using
   /SEPARATE_COMPILATION to minimize the size of the routines included by the
   linker as it creates the executable  image.   Using  /SEPARATE_COMPILATION
   will  also  reduce  the compiler virtual memory requirements when a source
   contains several compilation units.

   In  most  cases  /NOSEPARATE_COMPILATION   allows   more   interprocedural
   optimizations.

   The default is /NOSEPARATE_COMPILATION.