Table 8-2 Run-Time Error Messages and Explanations | |
Number | Severity Level, Number, and Message Text; Condition Symbol and Explanation |
None 1 | info: Fortran error message number is nnn The DIGITAL Fortran 90 message catalog file was not found on this system. For information about the message file location, e Section 8.1.2 or your DIGITAL Fortran installation guide. This error has no condition symbol. |
None 1 | warning: Could not open message catalog: for_msg.cat 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. |
None 1 | info: Check environment variable NLSPATH and protection of path-name/for_msg.dat The DIGITAL Fortran 90 message catalog file was not found. For more information, e Section 8.1.2 or your DIGITAL Fortran installation guide. This error has no condition symbol. |
None 1 | Insufficient memory to open Fortran RTL catalog: message 41 The DIGITAL Fortran 90 message catalog file could not be opened becau of insufficient virtual memory. To overcome this problem, increa the per-process data limit by using the limit (C shell) or ulimit (Bourne and Korn shells) commands (e Section 1.1) before running the program again. For more information, e error 41. This error has no condition symbol. |
1 1 | vere (1): Not a Fortran-specific error FOR$IOS_NOTFORSPE. An error in the ur program or in the RTL was not a DIGITAL Fortran 90-specific error and was not reportable 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, e the DIGITAL Fortran Language Reference Manual). |
8 | vere (8): Internal consistency check failure FOR$IOS_BUG_CHECK. Internal error. Plea check that the program is correct. Recompile if an error existed in the program. If this error persists, submit an SPR. |
9 | vere (9): Permission to access file denied FOR$IOS_PERACCFIL. Check the mode (protection) of the specified file. Make sure the correct file was being accesd. Change the protection, specified file, or process ud before rerunning program. |
10 | vere (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: ∙ 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. |
11 | info (11) 1: Unit not connected FOR$IOS_UNINOTCON. The specified unit was not open at the time of the attempted I/O operation. Check if correct unit number was specified. If appropriate, u an OPEN statement to explicitly open the file (connect the file to the unit number). |
17 | vere (17): Syntax error in NAMELIST input FOR$IOS_SYNERRNAM. The syntax of input to a namelist-directed READ statement was incorrect. |
18 | vere (18): Too many values for NAMELIST variable FOR$IOS_TOOMANVAL. An attempt was made to assign too many values to a variable during a namelist READ statement. |
19 | vere (19): Invalid reference to variable in NAMELIST input FOR$IOS_INVREFVAR. One of the following conditions occurred: ∙ 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. |
20 | vere (20): REWIND error FOR$IOS_REWERR. One of the following conditions occurred: ∙ The file was not a quential file. ∙ The file was not opened for quential or append access. ∙ The DIGITAL Fortran 90 RTL I/O system detected an error condition during execution of a REWIND statement. |
21 | vere (21): Duplicate file specifications FOR$IOS_DUPFILSPE. Multiple attempts were made to specify file attributes without an intervening clo operation. A DEFINE FILE statement was followed by another DEFINE FILE statement or an OPEN statement |
22 | vere (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, u an OPEN statement with a RECL= value (record length) of the appropriate size. |
23 smart phone | vere (23): BACKSPACE error FOR$IOS_BACERR. The DIGITAL Fortran 90 RTL I/O system detected an error condition during execution of a BACKSPACE statement. |
24 1 | vere (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. ∙ 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. |
25 | vere (25): Record number outside range FOR$IOS_RECNUMOUT. A direct access READ, WRITE, or FIND statement specified a record number outside the range specified when the file was opened. |
26 | vere (26): OPEN or DEFINE FILE required FOR$IOS_OPEDEFREQ. A direct access READ, WRITE, or FIND statement was attempted for a file when no prior DEFINE FILE or OPEN statement with ACCESS= ' DIRECT ' was performed for that file. |
27 | vere (27): Too many records in I/O statement FOR$IOS_TOOMANREC. An attempt was made to do one of the following: ladyship ∙ Read or write more than one record with an ENCODE or DECODE statement. ∙ Write more records than existed. |
28 | vere (28): CLOSE error FOR$IOS_CLOERR. An error condition was detected by the DIGITAL Fortran 90 RTL I/O system during execution of a CLOSE statement. |
29 | bornvere (29): File not found FOR$IOS_FILNOTFOU. A file with the specified name could not be found during an open operation. |
30 | vere (30): Open failure FOR$IOS_OPEFAI. An error was detected by the DIGITAL Fortran 90 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 clod |
李阳疯狂英语mp331 | vere (31): Mixed file access modes FOR$IOS_MIXFILACC. An attempt was made to u any of the following combinations: ∙ Formatted and unformatted operations on the same unit ∙ An invalid combination of access modes on a unit, such as direct and quential ∙ A DIGITAL Fortran 90 RTL I/O statement on a logical unit that was opened by a program coded in another language |
32 | vere (32): Invalid logical unit number FOR$IOS_INVLOGUNI. A logical unit number greater than 2,147,483,647 or less than zero was ud in an I/O statement. |
33 | vere (33): ENDFILE error avrFOR$IOS_ENDFILERR. One of the following conditions occurred: ∙ The file was not a quential organization file with variable-length records. ∙ The file was not opened for quential or append access. ∙ An unformatted file did not contain gmented records. ∙ The DIGITAL Fortran 90 RTL I/O system detected an error during execution of an ENDFILE statement. |
34 | vere (34): Unit already open FOR$IOS_UNIALROPE. A DEFINE FILE statement specified a logical unit that was already opened. |
35 | vere (35): Segmented record format error FOR$IOS_SEGRECFOR. An invalid gmented record control data word was detected in an unformatted quential 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. |
36 | vere (36): Attempt to access non-existent record FOR$IOS_ATTACCNON. A direct-access READ or FIND statement attempted to access beyond the end of a relative file (or a quential file on disk with fixed-length records) or access a record that was previously deleted in a relative file. |
37 | vere (37): Inconsistent record length FOR$IOS_INCRECLEN. An attempt was made to open a direct access file without specifying a record length. |
38 | vere (38): Error during write FOR$IOS_ERRDURWRI. The DIGITAL Fortran 90 RTL I/O system detected an error condition during execution of a WRITE statement. |
39 | vere (39): Error during read FOR$IOS_ERRDURREA. The DIGITAL Fortran 90 RTL I/O system detected an error condition during execution of a READ statement. |
40 | vere (40): Recursive I/O operation FOR$IOS_RECIO_OPE. While processing an I/O statement for a logical unit, another I/O operation on the same logical unit was attempted, 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. |
41 | vere (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, increa the per-process data limit by using the limit (C shell) or ulimit (Bourne and Korn shell) commands before you run this program again (e Section 1.1). 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, increa 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, e 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. |
42 | vere (42): No such device FOR$IOS_NO_SUCDEV. A pathname included an invalid or unknown device name when an OPEN operation was attempted. |
43 | vere (43): File name specification error FOR$IOS_FILNAMSPE. A pathname or file name given to an OPEN or INQUIRE statement was not acceptable to the DIGITAL Fortran 90 RTL I/O system. |
44 | vere (44): Inconsistent record type FOR$IOS_INCRECTYP. The RECORDTYPE value in an OPEN statement did not match the record type attribute of the existing file that was opened. |
45 | vere (45): Keyword value error in OPEN statement FOR$IOS_KEYVALERR. An improper value was specified for an OPEN or CLOSE statement specifier requiring a value. |
46 | vere (46): Inconsistent OPEN/CLOSE parameters FOR$IOS_INCOPECLO. Specifications in an OPEN or CLOSE statement were inconsistent. Some invalid combinations follow: ∙ READONLY or ACTION= ' READ ' with STATUS= ' NEW ' or STATUS= ' SCRATCH ' ∙ READONLY with STATUS= ' REPLACE ' , ACTION= ' WRITE ' , or ACTION= ' READWRITE ' ∙ ACCESS= ' APPEND ' with READONLY, ACTION= ' READ ' , STATUS= ' NEW ' , or STATUS= ' SCRATCH ' ∙ DISPOSE= ' SAVE ' , ' PRINT ' , or ' 中学生英语学习报SUBMIT ' with STATUS= ' SCRATCH ' ∙ DISPOSE= ' DELETE ' with READONLY ∙ CLOSE statement STATUS= ' DELETE ' with OPEN statement READONLY ∙ ACCESS= ' APPEND ' with STATUS= ' REPLACE ' ∙ ACCESS= ' DIRECT ' or jascha' KEYED ' with POSITION= ' APPEND ' , ' ASIS ' , or ' REWIND ' |
47 | vere (47): Write to READONLY file FOR$IOS_WRIREAFIL. A write operation was attempted to a file that was declared ACTION= ' READ ' or READONLY in the OPEN statement that is currently in effect. |
48 | vere (48): Invalid argument to Fortran Run-Time Library FOR$IOS_INVARGFOR. The compiler pasd an invalid or improperly coded argument to the DIGITAL Fortran 90 RTL. This can occur if the compiler is newer than the RTL in u. |
51 | vere (51): Inconsistent file organization FOR$IOS_INCFILORG. The file organization specified in an OPEN statement did not match the organization of the existing file. |
53 | vere (53): No current record FOR$IOS_NO_CURREC. Attempted to execute a REWRITE statement to rewrite a record when the current record was undefined. To define the current record, execute a successful READ statement. You can optionally perform an INQUIRE statement on the logical unit after the READ statement and before the REWRITE statement. No other operations on the logical unit may be performed between the READ and REWRITE statements. |
55 | vere (55): DELETE error FOR$IOS_DELERR. An error condition was detected by the DIGITAL Fortran 90 RTL I/O system during execution of a DELETE statement. |
57 | vere (57): FIND error FOR$IOS_FINERR. The DIGITAL Fortran 90 RTL I/O system detected an error condition during execution of a FIND statement. |
58 1 | info (58): Format syntax error at or near xx FOR$IOS_FMTSYN. Check the statement containing xx, a character substring from the format string, for a format syntax error. For information about FORMAT statements, refer to the DIGITAL Fortran Language Reference Manual. |
59 | vere (59): List-directed I/O syntax error FOR$IOS_LISIO_SYN 2. The data in a list-directed input record had an invalid format, or the type of the constant was incompatible with the corresponding variable. The value of the variable was unchanged. |
60 | vere (60): Infinite format loop FOR$IOS_INFFORLOO. The format associated with an I/O statement that included an I/O list had no field descriptors to u in transferring tho values. |
61 | vere or info 3 (61): Format/variable-type mismatch FOR$IOS_FORVARMIS 2. An attempt was made either to read or write a real variable with an integer field descriptor (I, L, O, Z, B), or to read or write an integer or logical variable with a real field descriptor (D, E, or F). To suppress this error message, e Section 3.15. |
62 | vere (62): Syntax error in format FOR$IOS_SYNERRFOR. A syntax error was encountered while the RTL was processing a format stored in an array or character variable. |
63 | error or info 3 (63): Output conversion error FOR$IOS_OUTCONERR 2. During a formatted output operation, the value of a particular number could not be output in the specified field length without loss of significant digits. When this situation is encountered, the overflowed field is filled with asterisks to indicate the error in the output record. If no ERR address has been defined for this error, the program continues after the error message is displayed. To suppress this error message, e Section 3.16. |
64 | vere (64): Input conversion error FOR$IOS_INPCONERR 2. During a formatted input operation, an invalid character was detected in an input field, or the input value overflowed the range reprentable in the input variable. The value of the variable was t to zero. |
65 | error (65): Floating invalid 英语外教FOR$IOS_FLTINV. During an arithmetic operation, the floating-point values ud in a calculation were invalid for the type of operation requested or invalid exceptional values. For example, when requesting a log of the floating-point values 0.0 or a negative number. For certain arithmetic expressions, specifying the -check nopower option can suppress this message (e Section 3.17). For information on allowing exceptional IEEE values, e Section 3.33. |
66 | vere (66): Output statement overflows record FOR$IOS_OUTSTAOVE. An output statement attempted to transfer more data than would fit in the maximum record size. |
67 | vere (67): Input statement requires too much data FOR$IOS_INPSTAREQ. Attempted to read more data than exists in a record with an unformatted READ statement or with a formatted quential READ statement from a file opened with a PAD specifier value of ' NO ' . |
68 | vere (68): Variable format expression value error FOR$IOS_VFEVALERR 2. The value of a variable format expression was not within the range acceptable for its intended u; for example, a field width was less than or equal to zero. A value of 1 was assumed, except for a P edit descriptor, for which a value of zero was assumed. |
69 1 | error (69): Process interrupted (SIGINT) FOR$IOS_SIGINT. The process received the signal SIGINT. Determine source of this interrupt signal (described in signal(3) ). |
70 1 | vere (70): Integer overflow FOR$IOS_INTOVF. During an arithmetic operation, an integer value exceeded byte, word, or longword range. The result of the operation was the correct low-order part. See Chapter 9 for ranges of the various integer data types. Consider specifying a larger integer data size (modify source program or, for an INTEGER declaration, possibly u the f90 option -integer_size nn ). |
71 1 | vere (71): Integer divide by zero FOR$IOS_INTDIV. During an integer arithmetic operation, an attempt was made to divide by zero. The result of the operation was t to the dividend, which is equivalent to division by 1. |
72 1 | error (72): Floating overflow FOR$IOS_FLTOVF. During an arithmetic operation, a floating-point value exceeded the largest reprentable value for that data type. See Chapter 9 for ranges of the various data types. |
73 1 | error (73): Floating divide by zero FOR$IOS_FLTDIV. During a floating-point arithmetic operation, an attempt was made to divide by zero. |
74 1 | error (74): Floating underflow FOR$IOS_FLTUND. During an arithmetic operation, a floating-point value became less than the smallest finite value for that data type. Depending on the values of the -fpe n option (e Section 3.33), the underflowed result was either t to zero or allowed to gradually underflow. See Chapter 9 for ranges of the various data types. |
75 1 | error (75): Floating point exception FOR$IOS_SIGFPE. A floating-point exception occurred. Core dump file created. Possible caus include: ∙ Division by zero ∙ Overflow ∙ Invalid operation, such as subtraction of infinite values, multiplication of zero by infinity (without signs), division of zero by zero or infinity by infinity ∙ Conversion of floating-point to fixed-point format when an overflow prevents conversion |
76 1 | error (76): IOT trap signal FOR$IOS_SIGIOT. Core dump file created. Examine core dump for possible cau of this IOT signal. For more information about signals, e Section 8.3. |
77 1 | vere (77): Subscript out of range FOR$IOS_SUBRNG. An array reference was detected outside the declared array bounds. |
78 1 | error (78): Process killed (SIGTERM) FOR$IOS_SIGTERM. The process received the signal SIGTERM. Determine source of this software termination signal (described in signal(3) ). |
79 1 | error (79): Process quit (SIGQUIT) FOR$IOS_SIGQUIT. The process received the signal SIGQUIT. Core dump file created. Determine source of this quit signal (described in signal(3) ). |
95 1 | info (95): Floating-point conversion failed FOR$IOS_FLOCONFAI. The attempted unformatted read or write of nonnative floating-point data failed becau the floating-point value: ∙ Exceeded the allowable maximum value for the equivalent native format and was t equal to infinity (plus or minus) ∙ Was infinity (plus or minus) and was t to infinity (plus or minus) ∙ Was invalid and was t to not a number (NaN) Very small numbers are t to zero (0). This error could be caud by the specified nonnative floating-point format not matching the floating-point format found in the specified file. Check the following: ∙ The correct file was specified. ∙ The record layout matches the format DIGITAL Fortran 90 is expecting. ∙ The ranges for the data being ud (Chapter 9) ∙ The correct nonnative floating-point data format was specified (Chapter 10). |
108 | vere (108): Cannot stat file FOR$IOS_CANSTAFIL. Attempted stat operation on the indicated file failed. Make sure correct file and unit were specified. |
120 | vere (120): Operation requires ek ability FOR$IOS_OPEREQSEE. Attempted an operation on a file that requires the ability to perform ek operations on that file. Make sure the correct unit, directory path, and file were specified. |
130 1 | vere (130): Ur breakpoint (SIGTRAP) FOR$IOS_BRK_USERBP. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. Examine core dump for possible cau. |
131 1 | vere (131): Kernel breakpoint (SIGTRAP) FOR$IOS_BRK_KERNELBP. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. Examine core dump for possible cau. |
135 1 | vere (135): Ur single step (SIGTRAP) FOR$IOS_BRK_SSTEPBP. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. Examine core dump for possible cau. |
136 1 | vere (136): Overflow check (SIGTRAP) FOR$IOS_BRK_OVERFLOW. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. The cau is an integer overflow. Try recompiling with the -check overflow option (perhaps with the decfort_dump_flag environment variable t) or examine the core dump file to determine the source code in error. |
137 1 | vere (137): Divide by zero check (SIGTRAP) FOR$IOS_BRK_DIVZERO. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. Examine core dump file for possible cau. |
138 1 | vere (138): Array index out of bounds (SIGTRAP) FOR$IOS_BRK_RANGE. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. The cau is an array subscript that is outside the dimensioned boundaries of that array. Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable t) or examine the core dump file to determine the source code in error. |
139 1 | vere (139): Array index out of bounds for index nn (SIGTRAP) FOR$IOS_BRK_RANGE2. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created. The cau is an array subscript that is outside the dimensioned boundaries of the array index n. Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable t) or examine the core dump file to determine the source code in error. |
140 1 | vere (140): Floating inexact FOR$IOS_FLTINE. A floating-point arithmetic or conversion operation gave a result that differs from the mathematically exact result. This trap is reported if the rounded result of an IEEE operation is not exact. |
144 1 | vere (144): rerved operand FOR$IOS_ROPRAND. The DIGITAL Fortran RTL encountered an rerved operand. Plea |
本文发布于:2023-07-22 19:41:08，感谢您对本站的认可！
本文链接：https://www.wtabcd.cn/fanwen/fan/90/185516.html
版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系，我们将在24小时内删除。
| 留言与评论（共有 0 条评论） |
