/osprey/crayf90/fe90/cf95.msgs

Large files files are truncated, but you can click here to view the full file

$
$  Copyright (C) 2006. QLogic Corporation. All Rights Reserved.
$
$  Copyright 2003, 2004, 2005, 2006 PathScale, Inc.  All Rights Reserved.
$
$  Copyright (C) 2000, 2001 Silicon Graphics, Inc.  All Rights Reserved.
$
$  This program is free software; you can redistribute it and/or modify it
$  under the terms of version 2 of the GNU General Public License as
$  published by the Free Software Foundation.
$
$  This program is distributed in the hope that it would be useful, but
$  WITHOUT ANY WARRANTY; without even the implied warranty of
$  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  
$
$  Further, this software is distributed without any warranty that it is
$  free of the rightful claim of any third person regarding infringement 
$  or the like.  Any license provided herein, whether implied or 
$  otherwise, applies only to this software file.  Patent licenses, if 
$  any, provided herein do not apply to combinations of this program with 
$  other software, or any other product whatsoever.  
$
$  You should have received a copy of the GNU General Public License along
$  with this program; if not, write the Free Software Foundation, Inc., 59
$  Temple Place - Suite 330, Boston MA 02111-1307, USA.
$
$  Contact information:  Silicon Graphics, Inc., 1600 Amphitheatre Pky,
$  Mountain View, CA 94043, or:
$
$  http://www.sgi.com
$
$  For further information regarding this notice, see:
$
$  http://oss.sgi.com/projects/GenInfo/NoticeExplan
$
$
$ |**************************************************************************|
$ |**                                                                      **|
$ |**                     MESSAGE AND EXPLANATION FILE                     **|
$ |**                                                                      **|
$ |**************************************************************************|
$ \**************************************************************************/
$
$
$ MESSAGE GROUPINGS:
$   0000 - 1999 : Front-end messages.  There is no particular order.
$                 The largest front-end message number is recorded in
$                 MAX_FE_MSG in messages.m.  If the front-end message number
$                 range changes, MAX_FE_MSG must also be updated.
$   2000 - 2099 : arith.a (folder) messages.  The largest folder message 
$                 number is recorded in MAX_FOLDER_MSG in messages.m.  If the 
$                 folder message number range changes, MAX_FOLDER_MSG must 
$                 also be updated.
$   2100 - 2499 : f90 command.
$   2500 - 4999 : Currently unused.
$   5000 - 5999 : Reserved for lint (will not be used by compilers).
$   6000 - 7999 : PDGCS messages.
$   8000 - 9999 : Compiler back-end (CCG, MPPCG, CMCS) messages.
$
$ Since message texts do not reflect the message level, a comment defining 
$ the level should precede each message entry.
$ --------------------------------------------------------------------------
$
$$ DO NOT REMOVE THIS LINE, psm USES IT TO FIND THE FIRST MESSAGE
$
$ Internal : 0001
$msg  0001 Message number %d, exceeds allowed range.
$nexp 0001
Internal : Message number %d, exceeds allowed range.
.PP
The message number exceeds the allowed maximum size.  It is either larger
than the maximum allowed message number for the front end or is less than 1.
.PP
This message should never be generated.  There is something wrong with the
message catalog or installation of the compiler.  Please notify your product
support organization with this error message number and any supporting
information.  This message does not indicate a problem with your code.
You may be able to change your code, so that the compiler does not try to
issue this message.
.ME
$
$ Internal : 0002
$msg  0002 Message level %d, is out of range.
$nexp 0002
Internal : Message level %d, is out of range.
.PP
The message level exceeds the allowed range.  It is not in the valid range
of message levels for the message system.
.PP
This message should never be generated.  There is something wrong with the
message catalog or installation of the compiler.  Please notify your product
support organization with this error message number and any supporting
information.  This message does not indicate a problem with your code.
You may be able to change your code, so that the compiler does not try to
issue this message.
.ME
$
$ Internal : 0003
$msg  0003 Message system failed trying to issue message %d
$nexp 0003
Internal : Message system failed trying to issue message %d
.PP
The message system was unable to issue the message indicated by the message
number included in this message.  This internal error can arise for a number
of possible reasons, including:

  * The message number is not in the message system messages file.

    It is probable that either the message number does not exist in the
    message catalog or the message catalog has been corrupted.

  * The message catalog is out of date or does not match the release of
    the compiler that tried to issue the message. 

  * The \*CNLSPATH\fR environment variable is not set correctly.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that the compiler does not try to issue this
message.
.ME
$
$ Error : 0004
$msg  0004 The MODULE PROCEDURE statement is only allowed in a generic interface block.
$nexp 0004
Error : The MODULE PROCEDURE statement is only allowed in a generic interface block.
.PP
A \*CMODULE PROCEDURE\fR statement can
only be specified in an interface block that has a \fIgeneric_spec\fR.
The compiler found
a \*CMODULE PROCEDURE\fR statement in an interface block that does not have a generic
specification.
.ME
$
$ Error : 0005
$msg  0005 The %s statement is out of order.
$nexp 0005
Error : The %s statement is out of order.
.PP
The current statement violates the Fortran standard statement ordering rules.
See the \fICFortran Language Reference Manual\fR, publication SR-3902, for details.
.ME
$
$ Error : 0006
$msg  0006 A keyword or identifier must follow the label or construct name.
$nexp 0006
Error : A keyword or identifier must follow the label or construct name.
.PP
The compiler has found a label or construct name.  A keyword or identifier 
must follow the label or construct name.  The following examples may clarify this.
.CS
10          ! This is an illegal statement
10 CONTINUE ! This is legal; a keyword follows 10
.CE
.ME
$
$ Error : 0007
$msg  0007 A construct name is not allowed on a %s statement.
$nexp 0007
Error : A construct name is not allowed on a %s statement.
.PP
A construct name can only appear on an \*CIF-THEN\fR statement, a \*CDO\fR statement, or
a \*CSELECT CASE\fR statement.  This error is generated when a construct name is
found on a statement other than those listed above.
.ME
$
$ Error : 0008
$msg  0008 The %s statement must precede all component definitions in derived type definition "%s".
$nexp 0008
Error : The %s statement must precede all component definitions in derived type definition "%s".
.PP
This \*CPRIVATE\fR or \*CSEQUENCE\fR statement follows one or more component definitions
in the  derived type definition.  The \*CPRIVATE\fR and \*CSEQUENCE\fR statements
must precede any component definitions.
.ME
$
$ Internal : 0009
$msg  0009 No forward reference entries exist for label %s even though it is undefined.
$nexp 0009
Internal : No forward reference entries exist for label %s even though it is undefined.
.PP
If an attribute entry exists for the label then it must be referenced in
the scoping unit.  If it was referenced but was never defined, there must be at
least one forward reference entry to represent the unresolved forward reference.
However, the forward reference chain for the label is empty.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Error : 0010
$msg  0010 Dummy argument "%s" is already defined in this argument list.
$nexp 0010
Error : Dummy argument "%s" is already defined in this argument list.
.PP
The name of a dummy argument appears more than once in the argument list on a
\*CFUNCTION\fR, \*CSUBROUTINE\fR, \*CENTRY\fR or statement function definition statement. 
.ME
$
$ Log_Warning : 0011
$msg  0011 The line size option is ignored because free source form is in effect.
$nexp 0011
Log_Warning : The line size option is ignored because free source form is in effect.
.PP
The line size option is ignored when the source form is set to \*Cfree\fR, because
the line may contain up to 132 characters.  With fixed source form the line
size option is valid, because the Fortran standard limits the line to 72
characters.  The option allows the line length to be extended to 80 characters.
.ME
$
$ Internal : 0012
$msg  0012 %s underflow.
$nexp 0012
Internal : %s underflow.
.PP
This message is generated from \*CPOP_SRC\fR macro in \*Csrc_input.m\fR.
The source stack has underflowed.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Ansi : 0013
$msg  0013 The Fortran standard requires multiple entry point function results "%s" and "%s" to both be default intrinsic types.
$nexp 0013
Ansi : The Fortran standard requires multiple entry point function results "%s" and "%s" to both be default intrinsic types.
.PP
A multiple entry point function (a function with one or more \*CENTRY\fR 
statements) can have entry points which return results of differing 
declared types only if all entry points return results which are scalar
and of type default real, default logical, double precision real, default
complex, or default integer.  If the entry point has the \*CPOINTER\fR attribute,
all entry points must be the same type and be pointers. The compiler allows
the entry points with the same declared types to have different kind parameters.
.ME
$
$ Limit : 0014
$msg  0014 Insufficient memory is available for compilation to continue.
$nexp 0014
Limit : Insufficient memory is available for compilation to continue.
.PP
The compiler ran out of memory during compilation of the program.  Check
with your product support organization and request more memory for the job.
Remember that program compilation may be only one of several processes
executing in the job space.
.ME
$
$ Error : 0015
$msg  0015 The %s statement is not allowed in a block data program unit.
$nexp 0015
Error : The %s statement is not allowed in a block data program unit.
.PP
Derived type definitions, type declaration statement and
the following statements are allowed in a block data program unit:
.CS
	COMMON
	DATA
	DIMENSION
	END BLOCK DATA
	EQUIVALENCE
	IMPLICIT
	IMPLICIT NONE
	INTRINSIC
	PARAMETER
	POINTER
	SAVE
	TARGET
	TASK COMMON
	USE
.CE
.PP
\fRThe \*CSEQUENCE\fR statement must be specified in a derived type definition
to be in a block data program unit.
.ME
$
$ Error : 0016
$msg  0016 The %s statement is not allowed in a main program unit.
$nexp 0016
Error : The %s statement is not allowed in a main program unit.
.PP
The following statements are not allowed in a main program unit:
.CS
	ENTRY
	INTENT
	OPTIONAL
	PRIVATE
	PUBLIC
	RETURN
.CE
.PP
These statements must be inside a construct or contained scoping unit to be in a main program unit:
.BL
\*CSEQUENCE\fR, \*CEND TYPE \fRin a derived type definition
.BL
\*CMODULE PROCEDURE \fRin a generic interface block
.BL
\*CELSE\fR, \*CELSE IF\fR, \*CEND IF\fR in an \*CIF\fR construct 
.BL
\*CCASE\fR, \*CEND SELECT\fR in a \*CCASE\fR construct 
.BL
\*CELSEWHERE\fR, \*CEND WHERE\fR in a \*CWHERE\fR construct 
.BL
\*CCYCLE\fR, \*CEXIT\fR, \*CEND DO\fR in a \*CDO\fR construct  
.BL
\*CFUNCTION\fR, \*CSUBROUTINE\fR in an interface block
.BL
\*CEND FUNCTION\fR in an interface body 
.BL
\*CEND SUBROUTINE\fR in an interface body 
.BL
\*CEND INTERFACE \fR in an interface block
.ME
$
$ Error : 0017
$msg  0017 Cannot open "%s" file.  It is needed for debugging or tracing.
$nexp 0017
Error : Cannot open "%s" file.  It is needed for debugging or tracing.
.PP
The compiler cannot open the debug file or the trace file.
.ME
$
$ Error : 0018
$msg  0018 The %s statement must not follow a MODULE PROCEDURE statement in a generic interface block.
$nexp 0018
Error : The %s statement must not follow a MODULE PROCEDURE statement in a generic interface block.
.PP
The syntax for an interface block is:
.CS
        interface_stmt
          [interface_body]...
          [module_procedure_stmt]...
        end_interface_stmt
.CE
.ME
$
$ Error : 0019
$msg  0019 The %s statement is not allowed in a module.
$nexp 0019
Error : The %s statement is not allowed in a module.
.PP
Derived-type definitions, type declaration statements and the
following statements are allowed in a module (before the \*CEND MODULE\fR or
the \*CCONTAINS\fR statement):
.CS
	ALLOCATABLE
	COMMON
	DATA
	DIMENSION
	EQUIVALENCE
	EXTERNAL
	IMPLICIT
	IMPLICIT NONE
	INTERFACE
	INTRINSIC
	NAMELIST
	PARAMETER
	POINTER
	PUBLIC
	PRIVATE
	SAVE
	TARGET
	USE
.CE
.PP
\fRThese statements must be in an interface block or contained scoping unit to be in a module program unit.
.BL
\*CMODULE PROCEDURE\fR in a generic interface block
.BL
\*CSEQUENCE\fR, \*CEND TYPE\fR in a derived-type definition
.BL
\*CFUNCTION\fR, \*CSUBROUTINE\fR, \*CEND FUNCTION\fR, \*CEND SUBROUTINE\fR, \*CEND INTERFACE\fR
in an interface block
.ME
$
$ Ansi : 0020
$msg  0020 The use of DOUBLE COMPLEX is an extension to the Fortran standard.
$nexp 0020
Ansi : The use of DOUBLE COMPLEX is an extension to the Fortran standard.
.PP
The \*CDOUBLE COMPLEX\fR statement is not part of the Fortran standard.
.ME
$
$ Error : 0021
$msg  0021 The type attributes for entry points "%s" and "%s" conflict.
$nexp 0021
Error : The type attributes for entry points "%s" and "%s" conflict.
.PP
If the result of any entry point of a multiple entry function (a function with
one or more \*CENTRY\fR statements) is of type character, or a derived type 
then all entry points in that function must return a result that is of the same
type.  If the function result is of type character, all entry points must
return a result with the same declared character length.  If the result is of
a derived type, then all entries must be the same derived type.
.ME
$
$ Ansi : 0022
$msg  0022 The type of function result "%s" must be a default intrinsic type if it does not match the type of other entry points.
$nexp 0022
Ansi : The type of function result "%s" must be a default intrinsic type if it does not match the type of other entry points.
.PP
A multiple entry point function (a function with one or more \*CENTRY\fR 
statements) may have entry points which return results of differing
declared types only if all entry points return  results which are scalar
and of type default real, default logical, double precision real, default
complex, or default integer.  If the entry point has the \*CPOINTER\fR attribute,
all entry points must be of the same type and have the \*CPOINTER\fR attribute.
.PP
The compiler allows the mix of default and non-default real, logical, double 
precision, complex and integer.
.ME
$
$ Error : 0023
$msg  0023 Label %s is not defined in this scoping unit.
$nexp 0023
Error : Label %s is not defined in this scoping unit.
.PP
When a statement label is referenced, the label must be the statement label of a
branch target statement that appears in the same scoping unit as the label 
reference.  For example, if the following \*CGO TO\fR statement appears in a subprogram,
label 10 must be defined in the same subprogram.
.CS
     GO TO 10
.CE
.ME
$
$ Error : 0024
$msg  0024 The character constant "%s", for the I/O control information list item %s, is not allowed.
$nexp 0024
Error : The character constant "%s", for the I/O control information list item %s, is not allowed.
.PP
Many I/O control information list items allow only a limited set of valid
character constants.  A character constant was encountered that is not
valid for this control list item.  Following are the I/O control items and
their valid character constants:
.CS
OPEN I/O control                         
 list item                   Character constants
 STATUS    OLD, NEW, SCRATCH, REPLACE, UNKNOWN
 ACCESS    SEQUENTIAL, DIRECT
 FORM      FORMATTED, UNFORMATTED
 BLANK     NULL, ZERO
 POSITION  ASIS, REWIND, APPEND
 ACTION    READ, WRITE, READWRITE
 DELIM     APOSTROPHE, QUOTE, NONE
 PAD       YES, NO
.CE
.PP
For the \*CCLOSE\fR I/O control list item \*CSTATUS\fR, the 
allowed character constants are \*CKEEP\fR and \*CDELETE\fR.
.PP
For the \*CREAD/WRITE\fR I/O control list item \*CADVANCE\fR, 
the allowed character constants are \*CYES\fR and \*CNO\fR.
.ME
$
$ Error : 0025
$msg  0025 This statement is not allowed in a derived type definition.
$nexp 0025
Error : This statement is not allowed in a derived type definition.
.PP
The only statements allowed in a derived type definition are \*CPRIVATE\fR, \*CSEQUENCE\fR
and the component definition statement.  \*CPRIVATE\fR is only allowed if the
derived type definition is in a module program unit.
.ME
$
$ Error : 0026
$msg  0026 The %s statement is not allowed in an interface block; expected SUBROUTINE, FUNCTION, MODULE PROCEDURE or END statement.
$nexp 0026
Error : The %s statement is not allowed in an interface block; expected SUBROUTINE, FUNCTION, MODULE PROCEDURE or END statement.
.PP
The only statements allowed in an interface block are \*CFUNCTION\fR,
\*CSUBROUTINE\fR, \*CMODULE PROCEDURE\fR, and \*CEND INTERFACE\fR.
\*CFUNCTION\fR and \*CSUBROUTINE\fR start an interface body.
\*CEND INTERFACE\fR ends the interface block.
\*CMODULE PROCEDURE\fR can be specified if the interface block is a generic
interface.  A generic interface contains a list of module procedures that can
be referenced with the generic name.
.ME
$
$ Error : 0027
$msg  0027 Function entry "%s" has result name "%s".  It must be used when declaring the result to be an array.
$nexp 0027
Error : Function entry "%s" has result name "%s".  It must be used when declaring the result to be an array.
.PP
If a function has a result name, the result name must be used when declaring
the result to be an array.
.ME
$
$ Error : 0028
$msg  0028 A trailing ")" is missing in the program string.
$nexp 0028
Error : A trailing ")" is missing in the program string.
.PP
The parentheses groups do not match in the optional parenthesized list that can appear on 
the \*CPROGRAM\fR statement.
.ME
$
$ Error : 0029
$msg  0029 The maximum number of unnamed block data program units is 26 and has been exceeded.
$nexp 0029
Error : The maximum number of unnamed block data program units is 26 and has been exceeded.
.PP
The Fortran standard limits unnamed block data program units to 1 in an
executable program.  However, the compiler extends this limit to 26.  The
compiler detected more than 26 unnamed block data program units.
.ME
$
$ Ansi : 0030
$msg  0030 The Fortran standard does not allow more than one unnamed BLOCK DATA program unit.
$nexp 0030
Ansi : The Fortran standard does not allow more than one unnamed BLOCK DATA program unit.
.PP
The Fortran standard does not allow more than one unnamed block data 
program unit.
.ME
$
$ Ansi : 0031
$msg  0031 Arguments to a PROGRAM statement are an extension to the Fortran standard.
$nexp 0031
Ansi : Arguments to a PROGRAM statement are an extension to the Fortran standard.
.PP
A \*CPROGRAM\fR statement contains an argument list enclosed in parentheses.  The
Fortran standard does not provide for actual arguments to a main program.
.ME
$
$ Error : 0032
$msg  0032 The type specification "CHARACTER*(*)" is not allowed in an IMPLICIT statement.
$nexp 0032
Error : The type specification "CHARACTER*(*)" is not allowed in an IMPLICIT statement.
.PP
Assumed-length character type declarations are not allowed in \*CIMPLICIT\fR statements.
.ME
$
$ Error : 0033
$msg  0033 If the component is being typed as the derived type being defined, it must have the POINTER attribute.
$nexp 0033
Error : If the component is being typed as the derived type being defined, it must have the POINTER attribute.
.PP
The Fortran standard requires that a component of a derived type may not be
declared to be of the derived type, unless it is a pointer.  For example:
.CS
      TYPE BB
        TYPE(BB) :: A
      END TYPE
.CE
.PP
Component \*CA\fR is illegal, because it is defined as the type being declared (\*CBB\fR).
.CS
      TYPE ZZ
        TYPE(ZZ), POINTER :: A
      END TYPE 
.CE
.PP
Component \*CA\fR is legal here, because it is a pointer to a structure of the type being declared (\*CZZ\fR).
.ME
$
$ Internal : 0034
$msg  0034 The name or attribute index is not valid.  It is less than 0 or greater than the table index.
$nexp 0034
Internal : The name or attribute index is not valid.  It is less than 0 or greater than the table index.
.PP
The local name table index or attribute table index is not valid.  It is
either less than zero or greater than the last table index entered.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Error : 0035
$msg  0035 The character length of "%s" has exceeded the maximum length of %d.
$nexp 0035
Error : The character length of "%s" has exceeded the maximum length of %d.
.PP
The maximum character length was exceeded.
.ME
$
$ Error : 0036
$msg  0036 Function entry "%s" has result name "%s", which must be used when declaring the result to be a pointer.
$nexp 0036
Error : Function entry "%s" has result name "%s", which must be used when declaring the result to be a pointer.
.PP
If a function has a result name, the result name must be used when declaring
the result to be a pointer.
.ME
$
$ Ansi : 0037
$msg  0037 Input lines greater than 72 characters long are an extension to the Fortran standard.
$nexp 0037
Ansi : Input lines greater than 72 characters long are an extension to the Fortran standard.
.PP
The compiler detected an input line greater than 72 characters.  The Fortran
standard does not provide for input lines greater than 72 characters long
in fixed source form.
.ME
$
$ Internal : 0038
$msg  0038 This character is not valid.  Expected keyword DO following failed parse of type spec DOUBLE.
$nexp 0038
Internal : This character is not valid.  Expected keyword DO following failed parse of type spec DOUBLE.
.PP
This error is generated when \*CDO\fR is not encountered as expected.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Error : 0039
$msg  0039 Namelist group name "%s" was referenced in an I/O statement.  It must not be specified in this NAMELIST statement.
$nexp 0039
Error : Namelist group name "%s" was referenced in an I/O statement.  It must not be specified in this NAMELIST statement.
.PP
Namelist statements may be mixed in with executable statements.  However, all
definitions of a specific namelist group must occur before the first reference to the
namelist group by an I/O statement.
.ME
$
$ Error : 0040
$msg  0040 If this main program has no PROGRAM statement specified, then no name can be specified on the END PROGRAM statement.
$nexp 0040
Error : If this main program has no PROGRAM statement specified, then no name can be specified on the END PROGRAM statement.
.PP
The compiler detected an \*CEND PROGRAM\fR statement followed by a name for 
a program unit.  This program unit has no \*CPROGRAM\fR statement
and therefore no name.
.ME
$
$ Error : 0041
$msg  0041 The %s statement must only be specified once for derived type definition "%s".
$nexp 0041
Error : The %s statement must only be specified once for derived type definition "%s".
.PP
The \*CPRIVATE\fR and \*CSEQUENCE\fR statements must only be specified once in a derived type definition.
.ME
$
$ Internal : 0042
$msg  0042 Attribute entry %d has a variant problem with field %s.
$nexp 0042
Internal : Attribute entry %d has a variant problem with field %s.
.PP
The compiler detected a variant problem.  A field is being accessed in the
attribute table, but the wrong variant is active.  The field may actually be
in the attribute auxiliary table, but it is checking the attribute table
variant.  In general whether the field actually resides in the attribute
table or the attribute auxiliary table should make no difference in resolving
the problem.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Error : 0043
$msg  0043 Only one %s statement is allowed in each %s construct.
$nexp 0043
Error : Only one %s statement is allowed in each %s construct.
.PP
Each \*CIF\fR construct must only have one \*CELSE\fR block.  Each \*CWHERE\fR construct must only
have one \*CELSEWHERE\fR block.  The compiler detected more than one \*CELSE\fR
or \*CELSE WHERE\fR statement in the \*CIF\fR or \*CWHERE\fR construct.
.ME
$
$ Error : 0044
$msg  0044 The entry point name of the host, "%s", must not be redefined in an interface body.
$nexp 0044
Error : The entry point name of the host, "%s", must not be redefined in an interface body.
.PP
Within an external subprogram one of the entry point names was specified
in an explicit interface in a contained subprogram.  Entry point names
already have explicit interfaces in the host, so they may not have another
interface specified in a contained procedure.  The following example illustrates an
illegal redefinition.
.CS
   FUNCTION ABC()
     CONTAINS
       SUBROUTINE SAM()
         INTERFACE
            FUNCTION ABC() !  Illegal re-definition
            END FUNCTION   !  of ABC's interface
         END INTERFACE
       END SUBROUTINE
   END FUNCTION
.CE
.ME
$
$ Error : 0045
$msg  0045 Component "%s" is private type "%s", therefore derived type "%s" must also be private or have private components.
$nexp 0045
Error : Component "%s" is private type "%s", therefore derived type "%s" must also be private or have private components.
.PP
If a component of a derived type is declared to be a private type, either
the derived type definition must contain the \*CPRIVATE\fR statement or the
derived type must be private.
.ME
$
$ Ansi : 0046
$msg  0046 The TASK COMMON statement is an extension to the Fortran standard.
$nexp 0046
Ansi : The TASK COMMON statement is an extension to the Fortran standard.
.PP
The \*CTASK COMMON\fR statement is an extension to the Fortran standard.
.ME
$
$ Error : 0047
$msg  0047 A '*' must only be used with the UNIT or FMT I/O control information list items.
$nexp 0047
Error : A '*' must only be used with the UNIT or FMT I/O control information list items.
.PP
An asterisk (*) was encountered in an I/O control information list in a position 
or with a keyword other than \*CUNIT\fR or \*CFMT\fR.
.ME
$
$ Error : 0048
$msg  0048 The DO variable must not be defined while it is active.
$nexp 0048
Error : The DO variable must not be defined while it is active.
.PP
The name of an active \*CDO\fR variable appeared in a statement that would change the
\*CDO\fR variable's value.  The \*CDO\fR variable can be used but not redefined within the
range of its loop.
.ME
$
$ Log_Error : 0049
$msg  0049 Cannot open source file "%s".
$nexp 0049
Log_Error : Cannot open source file "%s".
.PP
The compiler cannot open the source file.
.ME
$
$ Internal : 0050
$msg  0050 Attempt to read past end of file.
$nexp 0050
Internal : Attempt to read past end of file.
.PP
This is generated from \*Cfixed_get_line\fR in \*Csrc_input.c\fR.
The compiler has attempted to read past EOF.
The source input file may be corrupted.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that this error is not encountered.
.ME
$
$ Error : 0051
$msg  0051 A compiler directive must not be followed by a Fortran continuation line.
$nexp 0051
Error : A compiler directive must not be followed by a Fortran continuation line.
.PP
A Fortran continuation source line was encountered following
a compiler directive. Compiler directives may be continued,
but they require the directive sentinal at the beginning
of the line. Compiler directives may not be embedded within
a continued Fortran source line.
.ME
$
$ Ansi : 0052
$msg  0052 More than %d continuation lines is an extension to the Fortran standard in %s source form.
$nexp 0052
Ansi : More than %d continuation lines is an extension to the Fortran standard in %s source form.
.PP
The Fortran standard only allows for 19 continuation lines in fixed
source form and 39 continuation lines in free form.
.ME
$
$ Error : 0053
$msg  0053 The first line of an include file must not be a continuation line.
$nexp 0053
Error : The first line of an include file must not be a continuation line.
.PP
The first line of an include file must not be a continuation line.
.ME
$
$ Error : 0054
$msg  0054 The source line following an INCLUDE line must not be a continuation line.
$nexp 0054
Error : The source line following an INCLUDE line must not be a continuation line.
.PP
The line following an \*CINCLUDE\fR line must not be a continuation line.
.ME
$
$ Warning : 0055
$msg  0055 The file line does not end with a newline.
$nexp 0055
Warning : The file line does not end with a newline.
.PP
The compiler expects all lines in the source file to end with a newline
character.  This line does not end with a newline character.
.ME
$
$ Error : 0056
$msg  0056 A continuation line must not contain a label.
$nexp 0056
Error : A continuation line must not contain a label.
.PP
It is illegal to define a label on a continuation line.
.ME
$
$ Error : 0057
$msg  0057 The file name length exceeds the maximum of %d characters.
$nexp 0057
Error : The file name length exceeds the maximum of %d characters.
.PP
The length of the name of the file exceeds the maximum length.
Shorten the name of the file.
.ME
$
$ Error : 0058
$msg  0058 The INCLUDE file name is missing.
$nexp 0058
Error : The INCLUDE file name is missing.
.PP
An \*CINCLUDE\fR line does not follow the expected form.  In the following
syntax, \fIfile\fR is the name of the file to be included:
.CS
      INCLUDE 'file'
.CE
.PP
The file name must be enclosed in apostrophes or quotation marks.  Only an embedded comment can
follow the closing delimiter.
.ME
$
$ Error : 0059
$msg  0059 There is a missing delimiter on an INCLUDE file name.
$nexp 0059
Error : There is a missing delimiter on an INCLUDE file name.
.PP
An \*CINCLUDE\fR line does not follow the expected form.  In the following
syntax, \*Vfile\fR is the name of the file to be included:
.CS
      INCLUDE 'file'
.CE
.PP
The file name must be enclosed in apostrophes or quotation marks.  Only embedded comments can
follow the closing delimiter.
.ME
$
$ Error : 0060
$msg  0060 The source following the INCLUDE file name is not a comment.
$nexp 0060
Error : The source following the INCLUDE file name is not a comment.
.PP
An \*CINCLUDE\fR line does not follow the expected form.  In the following
syntax, \*Vfile\fR is the name of the file to be included:
.CS
      INCLUDE 'file'
.CE
.PP
The file name must be enclosed in apostrophes or quotation marks.  Only an embedded comment can
follow the closing delimiter.
.ME
$
$ Error : 0061
$msg  0061 The INCLUDE line must not contain a statement label.
$nexp 0061
Error : The INCLUDE line must not contain a statement label.
.PP
An \*CINCLUDE\fR line does not follow the expected form.  In the following
syntax, \*Vfile\fR is the name of the file to be included:
.CS
      INCLUDE 'file'
.CE
.PP
The file name must be enclosed in apostrophes or quotation marks.  Only an embedded comment can
follow the closing delimiter.
.ME
$
$ Error : 0062
$msg  0062 Operator "%s" is not intrinsic.  All operations in a DATA statement expression must be intrinsic.
$nexp 0062
Error : Operator "%s" is not intrinsic.  All operations in a DATA statement expression must be intrinsic.
.PP
The \*CDATA\fR statement has the general form:
.CS
  data_stmt_object_list /data_stmt_value_list/
.CE
.PP
where a \*Vdata_stmt_object\fR can be a variable or an implied-\*CDO\fR.  In a 
\*Vdata_stmt_object\fR that is a variable; each subscript, section subscript, 
substring starting point, and substring ending point must be an expression 
where each operation is intrinsic.
.PP
The \*CDATA\fR statement implied-\*CDO\fR has the form:
.CS
  (\*Vdata_i_do_object_list\*C, \*Vdata_i_do_variable\*C = 
	\*Vscalar_int_expr\*C, \*Vscalar_int_expr\*C
	[, \*Vscalar_int_expr\*C])\fR
.CE
.PP
All operations in each subscript of a \*Vdata_i_do_object\fR subscript list must be
intrinsic.  Likewise, all operations in each loop control \*Vscalar_int_expr\fR must
be intrinsic.
.ME
$
$ Error : 0063
$msg  0063 Cannot open INCLUDE file "%s".
$nexp 0063
Error : Cannot open INCLUDE file "%s".
.PP
The compiler cannot open the specified \*CINCLUDE\fR file.
.ME
$
$ Error : 0064
$msg  0064 Recursive use of INCLUDE file "%s".
$nexp 0064
Error : Recursive use of INCLUDE file "%s".
.PP
An \*CINCLUDE\fR file must not include itself.
.ME
$
$ Error : 0065
$msg  0065 A defined operator exceeds the maximum length of 31 characters.
$nexp 0065
Error : A defined operator exceeds the maximum length of 31 characters.
.PP
A defined operator must not exceed 31 characters.
.ME
$
$ Error : 0066
$msg  0066 A defined operator is missing the "." delimiter.
$nexp 0066
Error : A defined operator is missing the "." delimiter.
.PP
A defined operator must start and end with a period delimiter.  This defined
operator is missing its end delimiter.
.ME
$
$ Error : 0067
$msg  0067 Truncating identifier which exceeds the maximum of 63 characters.
$nexp 0067
Error : Truncating identifier which exceeds the maximum of 63 characters.
.PP
Due to an internal limit, when the compiler reads an identifier, it discards
characters beyond the 63rd.
.ME
$
$ Error : 0068
$msg  0068 The label length exceeds the maximum of 5 digits.
$nexp 0068
Error : The label length exceeds the maximum of 5 digits.
.PP
The Fortran standard requires labels to be 5 or less digits.  The compiler has 
detected a label with more than 5 digits.
.ME
$
$ Error : 0069
$msg  0069 A label must have at least one nonzero digit.
$nexp 0069
Error : A label must have at least one nonzero digit.
.PP
The compiler detected a label consisting of all zeros.  A label must have at 
least one nonzero digit.
.ME
$
$ Error : 0070
$msg  0070 Each control item specifier must be specified only once.
$nexp 0070
Error : Each control item specifier must be specified only once.
.PP
An I/O statement contains the same specifier more than once.  For
example, the following would cause this message to be issued, because
\*CUNIT=\fR is specified twice.
.CS
      WRITE (UNIT=101,FMT=10,UNIT=101)
.CE
.ME
$
$ Ansi : 0071
$msg  0071 The Fortran standard requires continuation lines to contain text following the & symbol in free source form.
$nexp 0071
Ansi : The Fortran standard requires continuation lines to contain text following the & symbol in free source form.
.PP
The Fortran standard requires continuation lines to contain characters other
than the continuation character.
.ME
$
$ Internal : 0072
$msg  0072 Object "%s" is host associated to itself.  Attr index is %d.
$nexp 0072
Internal : Object "%s" is host associated to itself.  Attr index is %d.
.PP
AT_ATTR_LINK(attr_idx) = attr_idx.  This causes all kinds of internal loops
during compilation.  An attribute should never link to itself.

This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that the compiler does not try to issue this
message.
.ME
$
$ Error : 0073
$msg  0073 This control item specifier is not allowed for this I/O statement.
$nexp 0073
Error : This control item specifier is not allowed for this I/O statement.
.PP
An I/O statement contains an inappropriate or unrecognized specifier.
The specifiers allowed on a \*CREAD\fR or \*CWRITE\fR statement are: 
.CS
UNIT    FMT         END         REC
ERR     IOSTAT      NML         ADVANCE
SIZE    EOR
.CE
The specifiers allowed on an \*COPEN\fR statement are: 
.CS
UNIT     FILE       STATUS      IOSTAT
ERR      FORM       ACCESS      RECL
BLANK    POSITION   ACTION      DELIM
PAD
.CE
The specifiers allowed on a \*CCLOSE\fR statement are:
.CS
UNIT     IOSTAT     STATUS      ERR
.CE
The specifiers allowed on an \*CINQUIRE\fR statement are:
.CS
FILE     IOSTAT     ERR         EXIST
OPENED   NUMBER     NAMED       RECL
NEXTREC  NAME       ACCESS      SEQUENTIAL
FORM     DIRECT     FORMATTED   UNFORMATTED
BLANK    UNIT       POSITION    ACTION
READ     WRITE      READWRITE   DELIM
PAD
.CE
.ME
$
$ Log_Warning : 0074
$msg  0074 Assembly language output (-eS or -S filename) disables binary output.  Assembly language output selected.
$nexp 0074
Log_Warning : Assembly language output (-eS or -S filename) disables binary output.  Assembly language output selected.
.PP
The compiler cannot have an assembly language file and a binary file open at the
same time.  The binary output file is disabled, because assembly language 
output is requested on the command line (\*C-eS\fR or \*C-S\fR \*Vfilename\fR).
The binary output file is on by default; therefore, specifying an assembly
language file on the command line (without turning off the binary file)
results in this warning message.
.CS
\*C-eS \fIfile.\*Cf     \fRWarning message issued
\*C-dB -eS \fIfile.\*Cf \fRNo warning, because \*C-dB\*C 
                        \fRturns off binary output\*C
\*C-eS -dS \fIfile.\*Cf \fRWarning message for \*C-eS.\*C
                        \fRBoth assembly and binary output are disabled.
.CE
.ME
$
$ Log_Warning : 0075
$msg  0075 Rounding/truncation conflict detected.  %s option selected.
$nexp 0075
Log_Warning : Rounding/truncation conflict detected.  %s option selected.
.PP
The compiler detected a rounding/truncation conflict on the command line.
The last option specified is used.
.ME
$
$ Log_Warning : 0076
$msg  0076 Inline option conflict detected.  Automatic mode selected.
$nexp 0076
Log_Warning : Inline option conflict detected.  Automatic mode selected.
.PP
This message is issued when both \*C-O inline[0-3]\fR and \*C-I \fIfilename\fR are
specified on the command line.  Automatic inlining is selected.
.ME
$
$ Log_Error : 0077
$msg  0077 Command line has an unknown option "%c".
$nexp 0077
Log_Error : Command line has an unknown option "%c".
.PP
The compiler detected an unknown option on the command line.
.ME
$
$ Log_Error : 0078
$msg  0078 -%c option has an illegal argument "%s".
$nexp 0078
Log_Error : -%c option has an illegal argument "%s".
.PP
The argument for the specified option is illegal.
.ME
$
$ Log_Error : 0079
$msg  0079 Options are not allowed after the input file name.
$nexp 0079
Log_Error : Options are not allowed after the input file name.
.PP
Nothing must follow the source input file name on the command line.
.ME
$
$ Log_Error : 0080
$msg  0080 Name must be specified for %s file when input is from stdin.
$nexp 0080
Log_Error : Name must be specified for %s file when input is from stdin.
.PP
If the source is input from \*Cstdin\fR, a name must be specified for the binary
or the assembly language file (depending on which one is requested).
.ME
$
$ Internal : 0081
$msg  0081 Unexpected attribute entry "%s" (index = %d) has been found in the local scope during use processing.
$nexp 0081
Internal : Unexpected attribute entry "%s" (index = %d) has been found in the local scope during use processing.
.PP
Routine not_visible_semantics has found an attribute in the symbol table
The only things allowed to be in the local scope during use processing
are the procedure name, function result name, dummy argument names,
use associated objects and objects used in declaration bounds expressions.
Other items that may be present, must have a declaration error.
.PP
This message should never be generated.  Please notify your product support
organization with this error message number and any supporting information.
This message does not indicate a problem with your code, although you may be
able to change your code so that the compiler does not try to issue this
message.
.ME
$
$ Log_Warning : 0082
$msg  0082 Debugging (-G) requires binary output (-eB).  Binary output is enabled.
$nexp 0082
Log_Warning : Debugging (-G) requires binary output (-eB).  Binary output is enabled.
.PP
If binary output is disabled (using the \*C-dB\fR option), the compiler can only
provide semantic and syntactic error checking.  Debugging requires binary
output to be generated.  Although binary output is on by default, it can be
turned off by specifying \*C-dB\fR or requesting an assembly language file 
(\*C-eS\fR or \*C-S\fR \*Vfilename\fR).
Following are examples to clarify this:
.nf
 \*C-dB -G0\fR   illegal - binary output is off, debug is on
 \*C-eS -G0\fR   illegal - assembly language file is on, debug is on
.fi
.ME
$
$ Error : 0083
$msg  0083 This token is missing the %c delimiter.
$nexp 0083
Error : This token is missing the %c delimiter.
.PP
The compiler detected the start of a token delimited by an apostrophe or 
a quotation mark.  The matching end delimiter is missing.
.ME
$
$ Error : 0084
$msg  0084 This Hollerith constant should have %d characters, but it only contains %d characters.
$nexp 0084
Error : This Hollerith constant should have %d characters, but it only contains %d characters.
.PP
The compiler detected an inconsistency between the count and the
number of characters actually specified in a Hollerith constant.  An example of this would be:
.CS
 4H123   \fRThe constant contains only 3 characters,\*C
         \fRbut the 4H indicates there should be 4.
.CE
.ME
$
$ Error : 0085
$msg  0085 The number of characters in the Hollerith specifier must be greater than zero.
$nexp 0085
Error : The number of characters in the Hollerith specifier must be greater than zero.
.PP
Specifying 0H is not valid.  The Hollerith constant must have a length greater than 0.
.ME
$
$ Error : 0086
$msg  0086 The END statement of this %s must be followed by %s.
$nexp 0086
Error : The END statement of this %s must be followed by %s.
.PP
The Fortran standard requires that the \*CEND\fR statement for a module 
procedure or internal procedure be \*CEND FUNCTION\fR if it is a function, and \*CEND SUBROUTINE\fR
if it is a subroutine.  The compiler detected only an \*CEND\fR statement.
.ME
$
$ Error : 0087
$msg  0087 In a real constant with a D or E following the decimal field, the D or E must be followed by an exponent.
$nexp 0087
Error : In a real constant with a D or E following the decimal field, the D or E must be followed by an exponent.
.PP
The compiler detected a missing exponent field in a real constant.
The syntax for a real constant is
.CS
   [\fIsign\*C] \fIreal_literal_constant\*C
.CE
.PP
\*Vreal_literal_constant\fR is 
\*Vsignificand\fR [\*Vexponent_letter exponent\fR] [_\*Vkind_param\fR]
.PP
     or
.PP
\*Vdigit_string exponent_letter exponent\fR [_\*Vkind_param\fR]
.PP
\*Vsignificand\fR is \*Vdigit_string\fR.[\*Vdigit_string\fR]
.PP
  or
.PP
\*Vdigit_string\fR
.PP
\*Vexponent_letter\fR is E or \*Vexponent\fR is \*Vsigned_digit_string\fR
.ME
$
$ Error : 0088
$msg  0088 The kind parameter suffix is not valid on a double precision real constant form.
$nexp 0088
Error : The kind parameter suffix is not valid on a double precision real constant form.
.PP
The compiler detected a kind parameter following a D exponent.
.PP
The syntax for a real constant is
.CS
[\*Vdigit_str\*C].\*Vdigit_str\*C[\*Vexponent_letter exponent\fR\*C]
[_\*Vkind_param\fR\*C]\fR
.CE
.PP
\*Vexponent_letter\fR is D or E; \*Vexponent\fR is \*Vsigned_digit_string\fR
with the following constraint:
if both \*Vkind_param\fR and \*Vexponent_letter\fR are present, \fIexponent_letter\fR must be E.
.ME
$
$ Error : 0089
$msg  0089 The kind parameter on a literal constant must be an integer number or named constant.
$nexp 0089
Error : The kind parameter on a literal constant must be an integer number or named constant.
.PP
If a kind parameter is specified on a literal constant, it must be an integer
number or named constant of type integer.  For example:
.CS
  r = 10.0_8    \fR! is a valid kind parameter\*C
  END

  PARAMETER (KIND=4)
  j = 10_KIND   \fR! is a valid kind parameter\*C
  END

  r = 10.0_IT   \fR! is not valid, because \*CIT\*C
                \fR! is not an integer constant value.
.CE
.ME
$
$ Ansi : 0090
$msg  0090 Boolean constants are an extension to the Fortran standard.
$nexp 0090
Ansi : Boolean constants are an extension to the Fortran standard.
.PP
Octal and hexadecimal values may be specified as Boolean constants in the
following ways:
.nf
.br
\*C1000B -->    \fRoctal   
.br
\*C'1a3'X -->   \fRhexadecimal
.fi
.PP
The Fortran standard does not support Boolean constants.
.ME
$
$ Error : 0091
$msg  0091 This constant contains %d characters.  The number of allowed characters must be > 0 and <= %d.
$nexp 0091
Error : This constant contains %d characters.  The number of allowed characters must be > 0 and <= %d.
.PP
Both nonstandard Boolean constants and Fortran BOZ constants
have limits to their size.  These limits are determined by machine type.

If the machine type has 64-bit words, the maximum lengths are as follows:

   For octal constants:        22
   For hexadecimal constants:  16
   For binary constants:       64

If the octal constant contains 22 characters, the high order (leftmost) digit
must only be a 0 or a 1.

If the machine type has 32-bit words, the maximum lengths are as follows:

   For octal constants:        11
   For hexadecimal constants:   8
   For binary constants:       32

If the octal constant contains 11 characters, the high order (leftmost) digit
must only be 0-3.
.ME
$
$ Error : 0092
$msg  0092 The value of this constant exceeds the range allowed on this machine type.
$nexp 0092
Error : The value of this constant exceeds the range allowed on this machine type.
.PP
Nonstandard Boolean constants and Fortran BOZ constants
have limits to their size.  These limits are determined by machine type.

If the machine type has 64-bit words, the maximum lengths are as follows:

   For octal constants:        22
   For hexadecimal constants:  16
   For binary constants:       64

If the octal constant contains 22 characters, the high order (leftmost) digit
must only be a 0 or a 1.

If the machine type has 32-bit words, the maximum lengths are as follows:

   For octal constants:        11
   For hexadecimal constants:   8
   For binary constants:       32

If the octal constant contains 11 characters, the high order (leftmost) digit
must only be 0-3.
.ME
$
$ Error : 0093
$msg  0093 Character '%c' is not valid in an octal constant.
$nexp 0093
Error : Character '%c' is not valid in an octal constant.
.PP
In octal constants (either BOZ or Boolean constants), the only allowed digits
are 0-7.  The compiler detected a character outside of this range.
.ME
$
$ Error : 0094
$msg  0094 A Hollerith constant must be %d characters or less when the "R" form is specified.
$nexp 0094
Error : A Hollerith constant must be %d characters or less when the "R" form is specified.
.PP
The "R" Hollerith form is specified as follows:
    '123456789'R
     9R123456789
.PP
Both of these cases are in error, because there are more than the maximum
number of characters that fit in a word specified in the Hollerith constant.
On 64 bit machines, a maximum of 8 characters is allowed. On 32 bit machines,
a maximum of 4 characters is allowed.
.ME
$
$ Error : 0095
$msg  0095 The real constant must contain digits in the whole and/or the fractional part of the constant.
$nexp 0095
Error : The real constant must contain digits in the whole and/or the fractional part of the constant.
.PP
The compiler is looking for a real constant but can only find a period.
.PP
For example:\*C
.nf
  \*C1.2       \fRLegal\*C
  \*C .2       \fRLegal\*C
  \*C1.        \fRLegal\*C
   \*C.        \fRIllegal
.fi
.ME
$
$ Ansi : 0096
$msg  0096 Hollerith constants are an extension to the Fortran standard.
$nexp 0096
Ansi : Hollerith constants are an extension to the Fortran standard.
.PP
The following specifications for a Hollerith constant are nonstandard.

    2Hab
    2Lab
    2Rab
    'ab'h
    'ab'l
    'ab'r
    "ab"H
    "ab"L
    "ab"R
.ME
$
$ Error : 0097
$msg  0097 The constant is not assignment compatible with "%s".
$nexp 0097
Error : The constant is not assignment compatible with "%s".
.PP
A variable is being initialized in either a type declaration statement or a 
\*CDATA\fR statement.  In either case, the value of the constant or structure
constructor must be compatible with its corresponding variable according to the
rules of intrinsic assignment.
.ME
$
$ Error : 0098
$msg  0098 A dot oper…