 





















                  HP_Fortran__________________________________________
                  Release Notes for OpenVMS Integrity Systems


                  October 2007

                  This document contains information about new and
                  changed features in this version of HP Fortran for
                  OpenVMS Integrity Systems.






                  Software Version:             HP Fortran Version 8.2

                  Operating System:             OpenVMS Integrity Systems
                                                Version 8.2-1 or later









                  Hewlett-Packard Company
                  Palo Alto, California

 






            ________________________________________________________________
            October 2007

            Copyright 2007 Hewlett-Packard Development Company, L.P.

            Confidential computer software. Valid license from HP
            required for possession, use or copying. Consistent with
            FAR 12.211 and 12.212, Commercial Computer Software,
            Computer Software Documentation, and Technical Data for
            Commercial Items are licensed to the U.S. Government under
            vendor's standard commercial license.

            The information contained herein is subject to change
            without notice. The only warranties for HP products and
            services are set forth in the express warranty statements
            accompanying such products and services. Nothing herein
            should be construed as constituting an additional warranty.
            HP shall not be liable for technical or editorial errors or
            omissions contained herein.

            Intel and Itanium are trademarks or registered trademarks
            of Intel Corporation its subsidiaries in the United States
            and other countries.


 














   __________________________________________________________________

                                                             Contents



   1  HP Fortran Version V8.2 Overview

         1.1   Operating System Compatibility................     1-1
         1.2   Web Page......................................     1-2
         1.3   Getting Help and Reporting Problems...........     1-2

   2  New and Changed Features

         2.1   New and Changed Features in V8.2..............     2-1
         2.1.1   New /ALIGN=COMMON=PAD_ALIGN_SIZE qualifier..     2-1
         2.1.2   New /[NO]ASSUME=64BIT_STRING_PARAMS
                 qualifier...................................     2-1
         2.1.3   Additional changes and corrected 
                 problems in V8.2............................     2-2

   3  New and Changed Features in Previous Releases

         3.1   New and Changed Features in V8.1 ECO 01.......     3-1
         3.2   New and Changed Features in V8.1..............     3-3
         3.2.1   IA64 and _IA64_ Predefines Implemented......     3-3
         3.2.2   Additional changes and corrected
                 problems in V8.1............................     3-3
         3.3   New and Changed Features in V8.0..............     3-5

   4  Differences from HP Fortran for OpenVMS Alpha Systems

         4.1   Floating-Point Arithmetic.....................     4-1
         4.2   No F77 Compiler...............................     4-3
         4.3   Dirty Zeros Trigger Exceptions................     4-3
         4.4   Math Algorithm Differences....................     4-4
         4.5   Math Library Exceptions.......................     4-4
         4.6   /ARCH and /OPT=TUNE qualifiers................     4-4



                                                                  iii










   5  Known Problems and Incomplete Functionality

         5.1   Bugs Not Fixed   
         5.2   Disabled
               /CHECK=ARG_INFO,FP_EXCEPTIONS,UNDERFLOW.......     5-1
         5.3   IEEE Exceptions Detected During Compilation...     5-1

   6  Documentation Overview

         6.1  HP Fortran Documentation and Online
              Information....................................     6-1































      iv

 










                                                                      1
      _________________________________________________________________

                                       HP Fortran Version V8.2 Overview


            HP Fortran Version 8.2 provides a new version of the HP
            Fortran which includes new features as well as corrections to 
            problems discovered in earlier versions.

            This chapter provides general information about the HP
            Fortran product. The remaining chapters provide the
            following information:

            o  Chapter 2 highlights new and changed features in this
               version of HP Fortran for Integrity Systems.

            o  Chapter 3 highlights new and changed features in
               previous versions of HP Fortran for Integrity Systems.

            o  Chapters 4 and 5 highlight differences between HP Fortran for
               Alpha Systems and HP Fortran for Integrity Systems.

            o  Chapter 6 lists the organization of the HP Fortran
               documentation set.

      1.1 Operating System Compatibility

            HP Fortran is supported on OpenVMS I64 Version V8.2-1
            through V8.3 (which is the latest that has been released
            at this time). It is likely that HP Fortran will work 
            correctly on all later versions of OpenVMS I64. If you 
            have questions about version compatibility, please contact 
            us as described in Section 1.3.








                                  HP Fortran Version V8.2 Overview 1-1








      1.2 The HP Fortran Home Page

            If you have Internet access and a web browser, you are
            welcome to view the following:

            o  The HP Fortran home page, located at the following URL:

                  http://hp.com/go/fortran/

            o  The Hewlett-Packard Company home page, located at the
                 following URL:

                  http://www.hp.com/

      1.3 Getting Help and Reporting Problems

            If you encounter a problem while using HP Fortran, report
            it to HP.

            If an error occurs while HP Fortran is in use and you
            believe the error is caused by a problem with HP Fortran,
            take one of the following actions:

            o  If you have a Software Product Services Support
               Agreement, consider contacting HP Global Services by
               telephone (in the United States, 1-800-354-9000) or by
               using the electronic means provided with your support
               agreement.

            o  Customers without a service contract can arrange for
               per-call support.













      1-2 HP Fortran Version V8.2 Overview







            When you initially contact HP Global Services, please
            indicate the following:

            o  The name (OpenVMS I64) and version number of the
               operating system you are using

            o  The name (HP Fortran) and complete version number of the
               compiler you are using (The version number is displayed
               at the end of a compiler listing file)

            o  The hardware system you are using (such as a model
               number)

            o  How critical the problem is

            o  A very brief description of the problem (one sentence if
               possible)

            When you submit information electronically or are speaking
            on the phone to the appropriate support specialist, you
            can provide more detailed information. This includes the
            specific commands used to compile and link the program, the
            error messages displayed, and relevant detailed information
            (possibly including source program listings). Please try to
            narrow the cause of the problem to a specific source module
            or lines of code.

            Support personnel might ask for additional information,
            such as listings of any command files, INCLUDE files,
            relevant data files, and so forth. If the program is
            longer than 50 lines, submit a copy of it electronically
            or provide machine-readable media.

            Experience shows that problem reports sometimes do not
            contain enough information to duplicate or identify the
            problem. Concise, complete information helps HP give
            accurate and timely service to software problems.

            To obtain information about purchasing HP support services,
            please contact your local HP sales representative.

            You can also send comments, questions and suggestions about
            the HP Fortran product to fortran@hp.com. Note that this
            address is for informational inquiries and is not a formal
            support channel.




                                   HP Fortran Version V8.2 Overview 1-3

 










                                                                      2
      _________________________________________________________________
                                              New and Changed Features


         2.1   New and Changed Features in V8.2

         This section provides highlights of new and changed 
         features and problems corrected in HP Fortran V8.2.

         The image identification string for the Fortran 95 
         compiler is V8.2-104939-50H96.

         2.1.1   New /ALIGN=COMMON=PAD_ALIGN_SIZE qualifier

               When the qualifier /ALIGN=COMMON=MULTILANGUAGE is in effect,
               COMMON blocks within the compiled Fortran source are padded
               at the end of each such COMMON block in the same way that the
	       C compiler would pad it, i.e. by a pad size based on the
               data types in the block.

               HP Fortran 95 previously contained an error (fixed in V7.6)
               which caused the padding to be based on the alignment 
               specified in a directive. This error would cause a COMMON 
               block that was aligned on an 8K boundary to also be padded 
               out to an 8K size, for example.

               The new /ALIGN=COMMON=PAD_ALIGN_SIZE qualifier provides the
               previous padding behavior.

         2.1.2   New /ASSUME=64BIT_STRING_PARAMS qualifier

               By default, when a string variable is passed as an argument,
               it is passed with a 32-bit descriptor. When a 64-bit
               descriptor is desired (for example, when calling a routine
               written in another language using 64-bit descriptors),
               you need to individually designate each string variable
               for which you would like the 64-bit descriptor.

               Some customers have requested an option to allow all such
               string variables used within a source file to be passed
               or received with 64-bit descriptors without needing to
               so specify for each individual string variable.



                                            New and Changed Features 2-1








               The new [NO]64BIT_STRING_PARAMS keyword for the /ASSUME
               qualifier can be used to specify that requested behavior.
	       When /ASSUME=64BIT_STRING_PARAMS is in effect, then all
               string variables used as parameters will be so used with
               64-bit descriptors.

               ** This feature must be used with caution, as unexpected
               side effects may cause you problems. For example, 
               because the Fortran Runtime Library expects 
               to receive parameters with 32-bit addresses, statements 
               that access the RTL either implicitly (e.g. print statements) 
               or explicitly may fail when passed string parameters with 
               64-bit addresses.

               The default is /ASSUME=NO64BIT_STRING_PARAMS.

         2.1.3   Additional changes and corrected problems in V8.2

            o  QXCM1000375413: aka Fortran 3248: V8.0 no longer allows
               OPEN/CLOSE file= clause to refer to an array.

            o  QXCM1000378452: aka IF448:  Using the DEC$FORRTL that comes 
               with V8.3, the user's application fails when calling 
               LIB$SIGNAL.

            o  QXCM1000453936: aka IF467: Compilation fails erroneously on
               complex structure symbol.

            o  QXCM1000413720: aka IF457: Unexpected compiler errors when 
               using complex structures in V7.6 and above.

            o  QXCM1000403722:  aka IF455: Unexpected compiler errors
               moving from F77 to F90

            o  QXCM1000443205: aka IF465: Integrity only. VMS Fortran RTL
               changes floating point trap bits. 











      2-2 New and Changed Features










                                                                      3
      _________________________________________________________________
                          New and Changed Features in Previous Releases


      3.1 Problems corrected in V8.1 ECO 01

      This section provides highlights of problems corrected in
      HP Fortran V8.1 ECO 01

      The image identification string for the Fortran compiler
      is HP Fortran V8.1-1-104930-50GBS.

           o  75-115-26 (Fortran Run-Time Library bug, fixed in
               OpenVMS Integrity Servers Version 8.3R): Interaction
               problems with LIB$ESTABLISH(LIB$SIG_TO_RET) and CLI$DCL_
               PARSE.

            o  QXCM1000372297: Erroneous %SYSTEM-F-NOCALLTRANS: A
               program trying to call a VAX subroutine processed
               through the VEST binary translator-although compiled
               with the correct switch (/TIE) and linked with the
               correct option (/NONATIVE)-results in an erroneous
               %SYSTEM-F-NOCALLTRANS failure.

            o  QXCM1000362711: Erroneous FATAL error when defining 21
               or more CDD dictionaries: When a source file defines 21
               or more CDD dictionaries, the compiler fails with F90-F-
               FATAL, Include files and/or DICTIONARY statements nested
               too deeply although the DICTIONARY statements are not
               nested.

            o  QXCM1000353431: Fortran compiler generates bad code
               involving stack pointer GB11074.

            o  QXCM1000349663: Integrity only: Erroneous %DEBUG-E-
               NOSYMBOL, symbol 'A': Look for a GB-what fixed this?

            o  QXCM1000343352: Array element argument passed
               incorrectly when the code is compiled nooptimized.

               When the argument being passed is an array element using
               a constant subscript, and the code is compiled /NOOPT,
               the first element of the array is passed rather than
               the specified element. When compiled /OPT, the correct
               argument is passed.
        

                         New and Changed Features in Previous Releases 3-1








            o  QXCM1000340837: Erroneous syntax errors are generated
               for logical statements containing 2-level structure
               records.

               When the source code contains logical expressions that
               are not fully qualified with parentheses and those
               expressions contain 2-level deep structure records,
               incorrect error messages are generated by the compiler.

            o  IF425: Internal compiler error after processing an
               INTENT attribute on an entry point name.

               Although the compiler correctly diagnoses the invalid
               statement, it continues on to fail with an internal
               compiler error.

            o  IF424: Erroneous syntax errors are generated for logical
               statements using .not. and multi-level structure syntax.

            o  PTR 75-13-1667: %F90-F-FATAL internal compiler error
               occurs following this valid I message. %F90-I-INFO, A
               name that identifies a global entity is used to identify
               another global entity in the same program. [JSCT]

            o  IF417: Declaring an EXTERNAL routine with the same name
               as a common block results in %F90-E-ERROR instead of the
               expected %F90-I-INFO.

            o  IF415: F90 asserts when compiling an initialized UNION
               definition.

            o  IF412: /SHOW=MAP emits no information for modules.











      3-2 New and Changed Features in Previous Releases







      3.2 New and Changed Features in V8.1

      This section provides highlights of problems corrected in
      HP Fortran V8.1

      The image identification string for the Fortran compiler
      is HP Fortran V8.1-104922-50G4H.

         3.2.1   IA64 and _IA64_ predefines are implemented.

         3.2.2   Additional changes and corrected problems in V8.1
                 
            o  PTR 75-102-1771: The compiler incorrectly reports an
               error for a statement where a record-separator single
               quote has a partner in a comment following an I/O
               statement.

            o  PTR 75-102-1783: Use of /NOI4 causes an OPEN statement
               to result in "%FOR-F-INVARGFOR, invalid argument to
               FORTRAN Run-Time Library." For KEY= in OPEN statement,
               the data_type should be either longword or byte_string
               (integer or character), independent of the kind of
               integer. Thus, /NOI4 should have no effect on the data_
               type in the key block.

            o  PTR 221-2-876: A program aborts at run time when it
               initializes the elements of an allocatable array before
               the array has been allocated.

            o  PTR 221-2-1067, QXCM1000208533: Compile-time (Unix) or
               run-time failure due to problems with ACTPOS. Generally
               an ACTPOS is treated as a variable, but when it is an
               expression under the covers, we need to be more careful
               in handling it. In this particual example, a character
               function result gets its size from a call to another
               function, passing an expression (the ACTPOS) as its
               argument.

            o  QXCM1000330109: Compiler gets an access violation
               on certain instances of BLOCK DATA programs which
               initialize records.

            o  QXCM1000314367: Erroneous syntax errors are generated
               for certain combinations of parentheses and single
               quotes.

            o  QXCM1000214854: F90-F-FATAL: ICE when compiling program
               with a record named "OR".


                      New and Changed Features in Previous Releases 3-3







            o  QXCM1000221329: Run-time failure due to incorrectly
               computing the address of the character structure
               component X%ARRAY(1)%STRING that is passed to CTRIM.

            o  QXCM1000221087: Public components of an object are not
               accessible in certain cases.

            o  QXCM1000226426: F90 does not pad/align the same as F77
               and C when compiled with the /ALIGN=COMMON=MULTILANGUAGE
               option.

            o  QXCM1000242932: The compiler loops infinitely while
               loading a module in certain cases.

            o  QXCM1000246439: %SIZEOF (i) gives %F90-F-FATAL,
               **Internal compiler error**. Occurs for function
               references which have '%' prefix and which are not %LOC,
               %LOC2, %REF, %VAL or %DESCR.

            o  QXCM1000283038: Problems when a statement function
               reference occurs while in a hoisting context. Ensure
               that the code to set up the statement function arguments
               precedes the code that uses them. Example is obscure:
               A(I:I,J)=SF(M,J)

            o  QXCM1000296751: In some cases, /CHECK=BOUNDS is
               subverted by optimization and the program continues
               past the specified bound.

            o  QXCM1000303300: The HP Fortran for OpenVMS User Manual
               had incorrect information about form feeds in column
               1 in a source code listing. The manual has been
               corrected to say: "If a source line contains a form-
               feed character, that line is printed but the form-feed
               character is ignored (does not generate a new page)."

            o  IF323: The second line of FDML warnings are occasionally
               included in the listing file (though not in the code) as
               if they were in the actual source.






      3-4 New and Changed Features in Previous Releases








            o  IF351: -nowarn only catches front end warnings and
               informationals. Suppress the middle end warnings and
               informationals as well.

            o  IF354: Floating-point test runs slower on Integrity than
               on Alpha.

            o  IF390: Compiler is "slow" and/or ends abnormally with
               an "insufficient virtual memory" error when a record
               containing a pointer field pointing to another record is
               copied.

      3.3 New and Changed Features in V8.0

      HP Fortran V8.0 was the initial version of HP Fortran provided for
      OpenVMS for Integrity Servers.















                      New and Changed Features in Previous Releases 3-5










                                                                      4
      _________________________________________________________________

                  Differences from HP Fortran for OpenVMS Alpha Systems


            HP Fortran for OpenVMS I64 Systems features the same
            command-line options and language features as HP Fortran
            for OpenVMS Alpha Systems with a few exceptions. A new
            appendix has been added to the HP Fortran for OpenVMS
            User Manual called "Differences Between HP Fortran on
            OpenVMS I64 and OpenVMS Alpha Systems," which fully details
            those exceptions. This chapter highlights only the major
            differences.

      4.1 Floating-Point Arithmetic

            The white paper "OpenVMS floating-point arithmetic on the
            Intel Itanium architecture" is essential reading. This
            document is at:

            http://www.hp.com/products1/evolution/alpha_retaintrust/
            download/i64-floating-pt-wp.pdf

            Note: the URL is one continuous line (broken here to fit).

            That white paper, together with these release notes,
            describes how HP Fortran for OpenVMS I64 Systems handles
            floating-point issues. Here are some highlights to keep in
            mind:

            o  IEEE is the default floating-point datatype (that is,
               the default is /FLOAT=IEEE_FLOAT)

               HP Fortran for OpenVMS Alpha Systems defaults to the
               VAX G_float floating-point format (/FLOAT=G_FLOAT).
               On OpenVMS I64 systems, however, there is no hardware
               support for floating-point representations other than
               IEEE. Instead, the compiler supports VAX floating-
               point formats by generating run-time code which
               converts operands to IEEE format, performs the needed
               arithmetic operations, and then converts the IEEE result
               back to the appropriate VAX format. Depending on the



              Differences from HP Fortran for OpenVMS Alpha Systems 4-1

 







               application, this may impose significant additional
               run-time overhead and some loss of accuracy compared to
               performing the operations in hardware on an Alpha (or
               VAX).

               This software support for the VAX formats is an
               important functional compatibility requirement for
               certain applications that need to deal with on-
               disk binary floating-point data, but its use should
               be strongly discouraged. This change is similar to
               the change in default from /FLOAT=D_FLOAT on VAX to
               /FLOAT=G_FLOAT on Alpha.

               If at all possible, users should use /FLOAT=IEEE_FLOAT
               (the default) for the highest performance and accuracy.

               Note that the changed /FLOAT default will have
               implications for the use of /CONVERT=NATIVE (the
               default). This switch causes unformatted data to remain
               unconverted on input, on the assumption that it matches
               the prevailing floating-point datatype.

               Files written from Fortran applications built with
               /FLOAT=G_FLOAT/CONVERT=NATIVE (the default) on Alpha
               can be read by I64 applications built with /FLOAT=G_
               FLOAT/CONVERT=NATIVE or /FLOAT=IEEE/CONVERT=VAXG.

            o  The /IEEE_MODE qualifier defaults to /IEEE_MODE=DENORM_
               RESULTS This differs from Alpha, where the default is
               /IEEE_MODE=FAST. Despite the name, /IEEE_MODE=FAST does
               not have a significant effect on run-time performance on
               I64 (or on Alpha processors from EV6 onward).

            o  On I64, users will have to pick one compile-time /FLOAT
               value and one compile-time /IEEE_MODE value and stick
               with it for the whole of their application. This is
               because mixed-mode applications will not (in general)
               work on OpenVMS I64 systems as a result of architectural
               differences in the hardware. This is a change from
               OpenVMS Alpha systems, where mixed-mode applications
               work. In particular, per-routine/per-file/per-library
               settings of a mode will not work.

            o  If your code changes the floating-point exception
               mode at runtime, it is your responsibility to change
               it back on routine-exit, including exits by means
               of exception handlers. Failure to do so may lead to


      4-2 Differences from HP Fortran for OpenVMS Alpha Systems

 







               unexpected results, as the compilers will assume that
               that no called routine changes the current mode. This
               is also a requirement on user-written libraries. The
               new appendix in the HP Fortran for OpenVMS User Manual
               explains in detail how to perform this exception-mode
               change. Please note that this requirement is also in
               effect for user-written libraries.

            o  Exception handlers will be entered with the floating-
               point mode in effect at the time the exception was
               raised, not the mode with which the handler was
               compiled.

      4.2 No F77 Compiler

            Only the F90 compiler is supported on OpenVMS I64. The
            F77 compiler, invoked on OpenVMS Alpha with the /OLD_F77
            qualifier, is not available. To ease the transition from
            F77 to F90, CDD (Common Data Dictionary) and DML (Data
            Manipulation Language) support, which were previously
            available only in the Alpha F77 compiler, have now been
            implemented in the F90 compiler for OpenVMS I64.

            Code previously compiled with the F77 compiler that does
            not compile with the F90 compiler should be reported
            through standard problem reporting mechanisms. Although
            it may not be possible to eliminate all differences between
            the two compiler versions, the HP Fortran development team
            will attempt to minimize these differences by enhancing the
            F90 compiler.

            Note: The unsupported /OLD_F77 qualifier should not be
            confused with the /F77 qualifier, which instructs the
            compiler to use FORTRAN-77 interpretation rules for those
            statements that have a meaning incompatible with FORTRAN-
            66; /F77 is still fully supported.

      4.3 Dirty Zeros Trigger Exceptions

            VAX-format "dirty zeros" (bit patterns which represent the
            value 0.0 but have some bits set in should-be-zero fields)
            may trigger exceptions where the equivalent Alpha program
            would not.


              Differences from HP Fortran for OpenVMS Alpha Systems 4-3

 







      4.4 Math Algorithm Differences

            Typically, the true function result for a math library
            function such as sin, atan, log, or exp is irrational,
            and cannot be represented exactly in any binary floating-
            point format (whether VAX or IEEE). In addition, because
            of architectural considerations, some of the algorithms
            used in the I64 math library differ from the algorithms
            used on Alpha. As a result of these factors, various I64
            mathematics builtins may produce rounded floating-point
            results that are very accurate, but slightly different from
            the equivalent Alpha results.

      4.5 Math Library Exceptions

            User code built with any of the three IEEE modes (FAST,
            UNDERFLOW, or DENORM_RESULTS) will work with the math
            library provided with the OpenVMS I64 release. Exceptions
            will be raised by the math library as specified by the
            mode. For example, if you specify /IEEE_MODE=DENORM_
            RESULTS, a denormal or NaN result will not cause an
            exception; if you specify FAST, a NaN will cause an
            exception and a denormal result will be set to zero.

            The math library runs using its own exception mode, not
            the mode currently in effect when a math library routine
            is called. The math library checks the operands and the
            mode set by the user. When a calculation would cause an
            exception for the user, the math library will raise a math
            library exception, as it does on Alpha.

            Other system libraries provided with this release run in
            the exception mode in effect when the library routine is
            called.

      4.6 /ARCH and /OPT=TUNE qualifiers

            o  HP Fortran for OpenVMS I64 is tuned by default for
               Itanium 2 processors, which are included in all systems
               supported by OpenVMS I64 Version 8.2. Therefore, the use
               of /ARCH and /OPT=TUNE qualifiers is not supported in
               this release.



      4-4 Differences from HP Fortran for OpenVMS Alpha Systems

 







            o  For the sake of "compile-and-go" compatibility,
               Alpha values for the /ARCH and /OPT=TUNE qualifiers
               are accepted on the compiler invocation command. An
               informational is printed saying they are ignored.









































              Differences from HP Fortran for OpenVMS Alpha Systems 4-5

 










                                                                      5
      _________________________________________________________________

                            Known Problems and Incomplete Functionality


      5.1 Bugs Not Fixed

            o QXCM1000416852: VMS DST Specification and DST 
              records are not in sync.

            o 3431: INVREALLOC error due to allocation too large
              for the Fortran Runtime Library.

            o IF431: Unexpected error during port: Conflicting 
              attributes or multiple declaration of name stops 
              compilation previously allowed.

      5.2 Disabled /CHECK=ARG_INFO,FP_EXCEPTIONS,UNDERFLOW

            The full frameworks needed to provide run-time checks of
            argument types and counting of IEEE exceptions are not
            yet available on OpenVMS I64 systems. As a result, the
            ARG_INFO, FP_EXCEPTIONS, and UNDERFLOW keywords have been
            disabled for the /CHECK qualifier. A warning to this effect
            will be issued during compilation if these keywords are
            specified on the command line. In addition, these checks
            are not currently enabled by specifying /CHECK=ALL.

      5.3 IEEE Exceptions Detected During Compilation

            If the compiler detects that a calculation will result in
            an exceptional IEEE value (such as a denormalized number),
            it may issue a compilation warning or error regardless of
            the IEEE exception mode chosen when compiling the program.










                      Known Problems and Incomplete Functionality 5-1

 










                                                                      6
      _________________________________________________________________

                                   Documentation and Online Information


            The HP Fortran documentation set contains the following:

            o  HP Fortran Installation Guide for OpenVMS I64 Systems
               (AA-PU3AF-TE)

               This guide explains how to install HP Fortran on the
               OpenVMS I64 operating system.

            o  HP Fortran for OpenVMS Language Reference Manual (AA-
               Q66SD-TK)

               This manual contains the complete description of the HP
               Fortran programming language, which includes Fortran 95
               and Fortran 90 features. It contains information about
               language syntax and semantics, adherence to various
               Fortran standards, and extensions to those standards.

               This document is included with the HP Fortran
               documentation kit, BA368MN. It is also on the Online
               Documentation Library CD-ROM, and is on the HP Fortran
               web site.

            o  HP Fortran for OpenVMS User Manual (AA-QJRWD-TE)

               This manual provides information about HP Fortran
               program development and the run-time environment. It
               describes compiling, linking, running, and debugging
               HP Fortran programs, run-time error-handling and
               I/O, performance guidelines, data types, numeric
               data conversion, calling other procedures and library
               routines, and compatibility with Compaq Fortran 77.

               This document is included with the HP Fortran
               documentation kit, BA368MN. It is also on the Online
               Documentation Library CD-ROM, and is on the HP Fortran
               web site.

            The HP Fortran Software Product Description (SPD) is
            provided on the Software Product Library CD-ROM.


                               Documentation and Online Information 6-1

 







            The following HP Fortran online information is available
            (once installed on the system):

            o  HP Fortran online release notes

               Provide more information on this version of HP Fortran,
               including known problems.

               To display or print the HP Fortran release notes before
               installing, use the PRODUCT EXTRACT RELEASE_NOTES
               FORTRAN command (see the HP Fortran Installation Guide
               for OpenVMS I64 Systems).

               Once installed, the ASCII version of the online release
               notes are located in:

                  SYS$HELP:FORTRAN.RELEASE_NOTES

               Other forms of the release notes (PostScript and
               Bookreader) are also provided, using the file name:

                  SYS$HELP:FORTRAN_RELEASE_NOTES.*

            o  HP Fortran online help

               The HP Fortran HELP module in SYS$HELP:HELPLIB.HLB
               provides online access to HP Fortran help, including
               descriptions of command qualifiers, a summary of the
               language elements (statements, intrinsic procedures,
               and so on), error message descriptions, and other
               information.

               To view the online HP Fortran help file using the HELP
               command, type:

               $ HELP FORTRAN

               You can specify topics to navigate the help hierarchy.
               For example:

               $ HELP FORTRAN /ALIGN






      6-2 Documentation and Online Information
