2024年4月27日发(作者：)

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 8.1.2 or your DIGITAL Fortran installation guide. This

error has no condition symbol.

warning: Could not open message catalog: for_

None

1

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

system. See Section 8.1.2 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

/for_

None

The DIGITAL Fortran 90 message catalog file was not found. For more

information, see Section 8.1.2 or your DIGITAL Fortran

installation guide. This error has no condition symbol.

Insufficient memory to open Fortran RTL catalog: message 41

The DIGITAL Fortran 90 message catalog file could not be opened

because of insufficient virtual memory. To overcome this problem,

increase the per-process data limit by using the limit

(C shell)

None

1

or ulimit

(Bourne and Korn shells) commands (see Section 1.1)

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

).

1

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

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:

10

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.