quantity什么意思fortran常见错误代码

2021年1月19日发(作者：躲藏)
If you have installed the Parallel Software Environment and compiled a
program
for
parallel
execution,
additional
messages
specific
to
parallel
execution
may
appear
(see
the
DIGITAL
High
Performance
Fortran
90
HPF
and
PSE Manual
).

Table 8-2 Run-Time Error Messages and Explanations

Severity Level, Number, and Message Text; Condition Symbol and
Number
Explanation
info: Fortran error message number is
nnn


The
DIGITAL
Fortran
90
message
catalog
file
was
not
found
on
this
None
1


system. For information about the message file location, see
Section
or your DIGITAL Fortran installation guide. This error
has no condition symbol.

warning: Could not open message catalog:


None
1

The

DIGITAL
Fortran
90
message
catalog
file
was
not
found
on
this
system. See
Section
or your DIGITAL Fortran installation guide
for further information. This error has no condition symbol.

info: Check environment variable NLSPATH and protection of
path-name
/

None
1


The
DIGITAL
Fortran
90
message
catalog
file
was
not
found.
For
more
information, see
Section
or your DIGITAL Fortran installation
guide. This error has no condition symbol.

Insufficient memory to open Fortran RTL catalog: message 41


None


The DIGITAL Fortran 90 message catalog file could not be opened
because
of
insufficient
virtual
memory.
To
overcome
this
problem,
1
increase the per-process data limit by using the limit

(C shell)
or
ulimit

(Bourne
and Korn
shells)
commands (see
Section
before
running the program again.

For more information, see error 41. This error has no condition
symbol.

severe (1): Not a Fortran-specific error


FOR$$IOS_NOTFORSPE.
An
error
in
the
user
program
or
in
the
RTL was
not a DIGITAL Fortran 90-specific error and was not reportable
1
1


through
any
other
DIGITAL
Fortran
90
run-time
messages.
If
you
call
ERRSNS, an error of this kind returns a value of 1 (for more
information on the ERRSNS subroutine, see the
DIGITAL Fortran
Language Reference Manual
).

severe (8): Internal consistency check failure


FOR$$IOS_BUG_CHECK.
Internal
error.
Please
check
that
the
program
8

is
correct.
Recompile
if
an
error
existed
in
the
program.
If
this
error persists, submit an SPR.

severe (9): Permission to access file denied


FOR$$IOS_PERACCFIL. Check the mode (protection) of the specified
9

file. Make sure the correct file was being accessed. Change the
protection, specified file, or process used before rerunning
program.

severe (10): Cannot overwrite existing file


10

FOR$$IOS_CAOVEEXI. Specified file
xxx
already exists when OPEN
statement specified STATUS= '

NEW '

(create new file) using I/O
unit
x
.
Make
sure
correct
file
name,
directory
path,
unit,
and so
forth were specified in the source program. Decide whether to:


Rename or remove the existing file before rerunning the
program.


Modify the source file to specify different file
specification, I/O unit, or OPEN statement STATUS.

info (11)
1
: Unit not connected

FOR$$IOS_UNINOTCON.
The
specified
unit
was
not
open
at
the
time
of
11

the attempted I/O operation. Check if correct unit number was
specified. If appropriate, use an OPEN statement to explicitly
open the file (connect the file to the unit number).

severe (17): Syntax error in NAMELIST input


17

FOR$$IOS_SYNERRNAM.
The
syntax
of
input
to
a
namelist-directed
READ
statement was incorrect.

severe (18): Too many values for NAMELIST variable


18

FOR$$IOS_TOOMANVAL. An attempt was made to assign too many values
to a variable during a namelist READ statement.

severe (19): Invalid reference to variable in NAMELIST input


FOR$$IOS_INVREFVAR. One of the following conditions occurred:

19



The variable was not a member of the namelist group.

An attempt was made to subscript a scalar variable.



A subscript of the array variable was out-of-bounds.

An array variable was specified with too many or too few
subscripts for the variable.


An
attempt
was
made
to
specify
a
substring
of
a
noncharacter
variable or array name.


A substring specifier of the character variable was
out-of-bounds.


A subscript or substring specifier of the variable was not
an integer constant.


An attempt was made to specify a substring by using an
unsubscripted array variable.

severe (20): REWIND error


FOR$$IOS_REWERR. One of the following conditions occurred:




20

The file was not a sequential file.

The file was not opened for sequential or append access.

The DIGITAL Fortran 90 RTL I/O system detected an error
condition during execution of a REWIND statement.

severe (21): Duplicate file specifications


FOR$$IOS_DUPFILSPE. Multiple attempts were made to specify file
21

attributes without an intervening close operation. A DEFINE FILE
statement
was
followed
by
another
DEFINE
FILE
statement
or
an
OPEN
statement

22
severe (22): Input record too long



FOR$$IOS_INPRECTOO. A record was read that exceeded the explicit
or default record length specified when the file was opened. To
read the file, use an OPEN statement with a RECL= value (record
length) of the appropriate size.

severe (23): BACKSPACE error


23

FOR$$IOS_BACERR.
The
DIGITAL
Fortran
90
RTL
I/O
system
detected
an
error condition during execution of a BACKSPACE statement.

severe (24): End-of-file during read


FOR$$IOS_ENDDURREA. One of the following conditions occurred:


A DIGITAL Fortran 90 RTL I/O system end-of-file condition
was encountered during execution of a READ statement that
did not contain an END, ERR, or IOSTAT specification.


An end-of-file record written by the ENDFILE statement was
encountered during execution of a READ statement that did
not contain an END, ERR, or IOSTAT specification.

24
1



An
attempt
was
made
to
read
past
the
end
of
an
internal
file
character string or array during execution of a READ
statement that did not contain an END, ERR, or IOSTAT
specification.

This error is returned by END and ERRSNS.

severe (25): Record number outside range


25

FOR$$IOS_RECNUMOUT.
A
direct
access
READ,
WRITE,
or
FIND
statement
specified
a
record
number
outside
the
range
specified
when
the
file
was opened.

severe (26): OPEN or DEFINE FILE required


FOR$$IOS_OPEDEFREQ.
A
direct
access
READ,
WRITE,
or
FIND
statement
26

was
attempted
for
a
file
when
no
prior
DEFINE
FILE
or
OPEN
statement
with ACCESS= '

DIRECT '

was performed for that file.

severe (27): Too many records in I/O statement


FOR$$IOS_TOOMANREC.
An
attempt
was
made
to
do
one
of
the
following:

27


Read
or
write
more
than
one
record
with
an
ENCODE
or
DECODE
statement.


Write more records than existed.

severe (28): CLOSE error


28

FOR$$IOS_CLOERR. An error condition was detected by the DIGITAL
Fortran 90 RTL I/O system during execution of a CLOSE statement.

severe (29): File not found


29

FOR$$IOS_FILNOTFOU. A file with the specified name could not be
found during an open operation.

severe (30): Open failure


FOR$$IOS_OPEFAI. An error was detected by the DIGITAL Fortran 90
30

RTL
I/O
system
while
attempting
to
open
a
file
in
an
OPEN,
INQUIRE,
or other I/O statement. This message is issued when the error
condition is not one of the more common conditions for which
specific error messages are provided. It can occur when an OPEN
operation was attempted for one of the following:



Segmented
file
that
was
not
on
a
disk
or
a
raw
magnetic
tape

Standard I/O file that had been closed

severe (31): Mixed file access modes


FOR$$IOS_MIXFILACC.
An
attempt
was
made
to
use
any
of
the
following
combinations:



31

Formatted and unformatted operations on the same unit

An invalid combination of access modes on a unit, such as
direct and sequential


A
DIGITAL
Fortran
90
RTL
I/O
statement
on
a
logical
unit
that
was opened by a program coded in another language

severe (32): Invalid logical unit number


32

FOR$$IOS_INVLOGUNI. A logical unit number greater than
2,147,483,647 or less than zero was used in an I/O statement.

severe (33): ENDFILE error


FOR$$IOS_ENDFILERR. One of the following conditions occurred:

33


The file was not a sequential organization file with
variable-length records.


The file was not opened for sequential or append access.



An unformatted file did not contain segmented records.

The DIGITAL Fortran 90 RTL I/O system detected an error
during execution of an ENDFILE statement.

severe (34): Unit already open


34

FOR$$IOS_UNIALROPE. A DEFINE FILE statement specified a logical
unit that was already opened.

severe (35): Segmented record format error


FOR$$IOS_SEGRECFOR.
An
invalid
segmented
record
control
data
word
35
was detected in an unformatted sequential file. The file was

probably either created with RECORDTYPE= '

FIXED '

or '

VARIABLE
'

in
effect,
or
was
created
by
a
program
written
in
a
language
other
than Fortran or Fortran 90.

severe (36): Attempt to access non- existent record


FOR$$IOS_ATTACCNON. A direct-access READ or FIND statement
36

attempted to access beyond the end of a relative file (or a
sequential file on disk with fixed-length records) or access a
record that was previously deleted in a relative file.

severe (37): Inconsistent record length


37

FOR$$IOS_INCRECLEN.
An
attempt
was
made
to
open
a
direct
access
file
without specifying a record length.

severe (38): Error during write


38

FOR$$IOS_ERRDURWRI.
The
DIGITAL
Fortran
90
RTL
I/O
system
detected
an error condition during execution of a WRITE statement.

severe (39): Error during read


39

FOR$$IOS_ERRDURREA.
The
DIGITAL
Fortran
90
RTL
I/O
system
detected
an error condition during execution of a READ statement.

severe (40): Recursive I/O operation


FOR$$IOS_RECIO_OPE.
While
processing
an
I/O
statement
for
a
logical
another
I/O
operation
on
the
same
logical
unit
was
attempted,
40
unit,

such
as
a
function
subprogram
that
performs
I/O
to
the
same
logical
unit
that
was
referenced
in
an
expression
in
an
I/O
list
or
variable
format expression.

severe (41): Insufficient virtual memory


FOR$$IOS_INSVIRMEM.
The
DIGITAL
Fortran
90
RTL
attempted
to
exceed
its
available
virtual
memory
while
dynamically
allocating
space.
To overcome this problem, increase the per-process data limit by
using the limit

(C shell) or ulimit

(Bourne and Korn shell)
commands before you run this program again (see
Section
.

41

To
determine
whether
the
maximum
per-process
data
size
is
already
allocated, check the value of the
maxdsiz
parameter in the
sysconfigtab
or
system
configuration
file.
If
necessary,
increase
its
value.
Changes
to
do
not
take
effect
until
the
system
has
been
rebooted (you do not need to rebuild the kernel if you modify
sysconfigtab).

For more information about system configuration parameters, see
the
DIGITAL UNIX System Tuning and Performance Management
guide.

Before
you
try
to
run
this
program
again,
wait
until
the
new
system
resources take effect.

severe (42): No such device


42

FOR$$IOS_NO_SUCDEV. A pathname included an invalid or unknown
device name when an OPEN operation was attempted.

severe (43): File name specification error


FOR$$IOS_FILNAMSPE. A pathname or file name given to an OPEN or
43

INQUIRE
statement
was
not
acceptable
to
the
DIGITAL
Fortran
90
RTL
I/O system.

severe (44): Inconsistent record type


FOR$$IOS_INCRECTYP. The RECORDTYPE value in an OPEN statement did
44

not
match
the
record type
attribute
of
the
existing
file
that
was
opened.

severe (45): Keyword value error in OPEN statement


45

FOR$$IOS_KEYVALERR.
An
improper
value
was
specified
for
an
OPEN
or
CLOSE statement specifier requiring a value.

severe (46): Inconsistent OPEN/CLOSE parameters


FOR$$IOS_INCOPECLO. Specifications in an OPEN or CLOSE statement
46

were inconsistent. Some invalid combinations follow:


READONLY
or
ACTION=
'

READ
'

with
STATUS=
'

NEW
'

or
STATUS=