Fortran Overview Of Run Time Error Messages
pages for details. Each error is listed on the screen alone or with one of these phrases appended to it: apparent state: unit num named user filename last format: string lately (reading, writing) (sequential, direct, indexed) formatted, unformatted (external, internal) IO When the Fortran run-time system detects an error, the following actions take place: A message describing the error is written to the standard error unit (Unit 0). A core file, which can be used with dbx (the debugger) to inspect the state of the program at termination, is produced if the f77_dump_flag environment variable is defined and set to y. When a run-time error occurs, the program terminates with one of the error messages shown in the following table. The errors are https://software.intel.com/en-us/node/678472 output in the format user filename : message. Table A-1. Run-Time Error Messages Number Message/Cause 100 error in format Illegal characters are encountered in FORMAT statement. 101 out of space for I/O unit table Out of virtual space that can be allocated for the I/O unit table. 102 formatted io not allowed Cannot do formatted I/O on logical units opened for unformatted I/O. 103 unformatted io not allowed Cannot do unformatted I/O on logical units opened for formatted http://csweb.cs.wfu.edu/~torgerse/Kokua/More_SGI/007-2361-008/sgi_html/apa.html I/O. 104 direct io not allowed Cannot do direct I/O on sequential file. 106 can't backspace file Cannot perform BACKSPACE/REWIND on file. 107 null file name Filename specification in OPEN statement is null. 108 can't stat file The directory information for the file is not accessible. 109 file already connected The specified filename has already been opened as a different logical unit. 110 off end of record Attempt to do I/O beyond the end of the record. 112 incomprehensible list input Input data for list-directed read contains invalid character for its data type. 113 out of free space Cannot allocate virtual memory space on the system. 114 unit not connected Attempt to do I/O on unit that has not been opened or cannot be opened. 115 read unexpected character Unexpected character encountered in formatted or directed read. 116 blank logical input field Invalid character encountered for logical value. 117 bad variable type Specified type for the namelist element is invalid. This error is most likely caused by incompatible versions of the front end and the run-time I/O library. 118 bad namelist name The specified namelist name cannot be found in the input data file. 119 variable not in namelist The namelist variable name in the input data file does not belong to the specified namelist. 120 no end record $END is not found at the end of the namelist input data fil
detailed description of the errors. To define the condition symbol values (PARAMETER statements) in your program, include the following file: /opt/intel_fc_80/include/for_iosdef.f As http://cftcc.iccas.ac.cn/upload/doc/ifc/f_ug1/ug1l_rt_errors.htm described in the table, the severity of the message determines which of http://h30266.www3.hpe.com/odl/axplp/progtool/for9590v82/forti64um_047.html the following occurs:: program execution continues with info and warning, the results might be incorrect with error, and program execution stops (unless a recovery method is specified) with severe. In the last case, to prevent program termination, you must include either an appropriate I/O error-handling specifier time error and recompile or, for certain errors, change the default action of a signal before you run the program again. The first column lists error numbers returned to IOSTAT variables when an I/O error is detected. The first line of the second column provides the message as it is displayed (following forrtl:), including the severity level, message number, and the fortran overview of message text. The following lines of the second column contain the status condition symbol (such as FOR$IOS_INCRECTYP) and an explanation of the message. Number Severity Level, Number, and Message Text; Condition Symbol and Explanation None 1 info: Fortran error message number is nnn The Intel Fortran message catalog file was not found on this system. See Message Catalog File Location. This error has no condition symbol. None 1 warning: Could not open message catalog: for_msg.cat The Intel Fortran message catalog file was not found on this system. See Message Catalog File Location. This error has no condition symbol. None 1 info: Check environment variable NLSPATH and protection of pathname/for_msg.cat The Intel Fortran message catalog file was not found. See Message Catalog File Location. This error has no condition symbol. None 1 Insufficient memory to open Fortran RTL catalog: message 41 The Intel Fortran 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) or
software errors, and errors that require changing the FORTRAN command. Printed messages have the form: %F90-F-MNEMONIC, error_text The first line of the message contains the appropriate file specification or keyword involved in the error. The operating system supplies more specific information about the error whenever possible. For example, a file read error might produce the following error message: %F90-F-ERROR, error reading _DBA0:[SMITH]MAIN.FOR;3 -RMS-W-RTB, 512 byte record too big for user's buffer -F90-F-ABORT, abort The secondary operating system (in this case the RMS facility) message provides helpful information about the actual cause of the error, as described in the OpenVMS System Messages and Recovery Procedures Reference Manual or the equivalent OpenVMS HELP/MESSAGE facility. C.3 Messages from the HP Fortran Run-Time System Errors that occur during execution of your HP Fortran program are reported by diagnostic messages from the HP Fortran Run-Time Library (RTL). These messages may result from hardware conditions, file system errors, errors detected by RMS, errors that occur during transfer of data between the program and an internal record, computations that cause overflow or underflow, incorrect calls to the HP Fortran RTL, problems in array descriptions, and conditions detected by the operating system. As described in Section 7.2, the severity of run-time diagnostic messages can be fatal (F), error (E), warning (W), and informational (I). The following example shows how run-time messages appear: %FOR-F-ADJARRDIM, adjustable array dimension error Table C-1 is an alphabetical list of run-time diagnostic messages, without the message prefixes FOR, SS, and MTH. (Refer to Table 7-1 for a list of the messages in error-number sequence.) For each message