Errors that occur during execution of your program are reported by diagnostic messages from the Run-Time Library. These messages can 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 Run-Time Library, problems in array descriptions, and conditions detected by the operating system. This section lists the run-time diagnostic messages without the prefixes FOR, SS, and MTH. For each mnemonic, the following information is provided: the message number, an error code (F for fatal, E for error, and I for information), the message text, and an explanation of the message.
1 – ADJARRDIM
NUMBER: 93
ERROR CODE: F
MESSAGE TEXT: adjustable array dimension error
EXPLANATION: Upon entry to a subprogram, one of the following
errors was detected during the evaluation of dimensioning
information:
o An upper-dimension bound was less than a lower-dimension bound.
o The dimensions implied an array that was larger than
addressable memory.
2 – ARRSIZEOVF
NUMBER: 179 ERROR CODE: F MESSAGE TEXT: Cannot allocate array - overflow on array size calculation EXPLANATION: An attempt to dynamically allocate storage for an array failed because the required storage size exceeds addressable memory. This error is not returned by IOSTAT. However, this error can be returned by STAT in an ALLOCATE statement.
3 – ASSERTERR
NUMBER: 145 ERROR CODE: F MESSAGE TEXT: assertion error EXPLANATION: The HP Fortran RTL encountered an assertion error. Please report the problem to HP. This error is not returned by IOSTAT.
4 – ATTACCNON
NUMBER: 36
ERROR CODE: F
MESSAGE TEXT: attempt to access non-existent record
EXPLANATION: One of the following conditions occurred:
o A direct access READ, FIND, or DELETE statement attempted to
access a nonexistent record from a relative organization file.
o A direct access READ or FIND statement attempted to access
beyond the end of a sequential organization file.
o A keyed access READ statement attempted to access a nonexistent
record from an indexed organization file.
5 – BACERR
NUMBER: 23
ERROR CODE: F
MESSAGE TEXT: BACKSPACE error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file.
o The file was not opened for sequential access. (A unit opened
for append access may not be backspaced until a REWIND
statement is executed for that unit.)
o RMS detected an error condition during execution of a BACKSPACE
statement.
6 – BUG_CHECK
NUMBER: 8 ERROR CODE: F MESSAGE TEXT: internal consistency check failure EXPLANATION: Internal severe error. Please check that the program is correct. Recompile if an error existed in the program. If this error persists, report the problem to HP.
7 – CLOERR
NUMBER: 28 ERROR CODE: F MESSAGE TEXT: CLOSE error EXPLANATION: An error condition was detected by RMS during execution of a CLOSE statement.
8 – DELERR
NUMBER: 55
ERROR CODE: F
MESSAGE TEXT: DELETE error
EXPLANATION: One of the following conditions occurred:
o On a direct access DELETE, the file that did not have relative
organization.
o On a current record DELETE, the file did not have relative or
indexed organization, or the file was opened for direct access.
o RMS detected an error condition during execution of a DELETE
statement.
9 – DIRIO_KEY
NUMBER: 258 ERROR CODE: F MESSAGE TEXT: direct-access I/O to unit open for keyed access EXPLANATION: The OPEN statement for this unit number specified keyed access and the I/O statement specifies direct access. Check the OPEN statement and make sure the I/O statement uses the correct unit number and type of access. (For more information on statements, see the HP Fortran for OpenVMS Language Reference Manual.)
10 – DIV
NUMBER: 178 ERROR CODE: F MESSAGE TEXT: Divide by zero EXPLANATION: A floating-point or integer divide-by-zero exception occurred. This error is not returned by IOSTAT.
11 – DUPFILSPE
NUMBER: 21 ERROR CODE: F MESSAGE TEXT: duplicate file specifications EXPLANATION: Multiple attempts were made to specify file attributes without an intervening close operation. A DEFINE FILE statement was followed by another DEFINE FILE statement or an OPEN statement.
12 – ENDDURREA
NUMBER: 24
ERROR CODE: F
MESSAGE TEXT: end-of-file during read
EXPLANATION: One of the following conditions occurred:
o An RMS end-of-file condition was encountered during execution
of a READ statement that did not contain an END, ERR, or IOSTAT
specification.
o 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.
o 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 not returned by IOSTAT.
13 – ENDFILERR
NUMBER: 33
ERROR CODE: F
MESSAGE TEXT: ENDFILE error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file with
variable-length records.
o The file was not opened for sequential, append, or direct
access.
o An unformatted file did not contain segmented records.
o RMS detected an error during execution of an ENDFILE statement.
14 – ENDRECDUR
NUMBER: 268 ERROR CODE: F MESSAGE TEXT: end of record during read EXPLANATION: An end-of-record condition was encountered during execution of a nonadvancing I/O READ statement that did not specify the EOR branch specifier. This error is not returned by IOSTAT.
15 – ERRDURREA
NUMBER: 39 ERROR CODE: F MESSAGE TEXT: error during read EXPLANATION: RMS detected an error condition during execution of a READ statement.
16 – ERRDURWRI
NUMBER: 38 ERROR CODE: F MESSAGE TEXT: error during write EXPLANATION: RMS detected an error condition during execution of a WRITE statement.
17 – FILNAMSPE
NUMBER: 43 ERROR CODE: F MESSAGE TEXT: file name specification error EXPLANATION: A file-name specification given to an OPEN or INQUIRE statement was not acceptable to RMS.
18 – FILNOTFOU
NUMBER: 29 ERROR CODE: F MESSAGE TEXT: file not found EXPLANATION: A file with the specified name could not be found during an open operation.
19 – FINERR
NUMBER: 57 ERROR CODE: F MESSAGE TEXT: FIND error EXPLANATION: RMS detected an error condition during execution of a FIND statement.
20 – FLOCONFAI
NUMBER: 95
ERROR CODE: E
MESSAGE TEXT: floating point conversion failed
EXPLANATION: The attempted unformatted read or write of non-native
floating-point data failed. One of the following conditions
occurred for a non-native floating-point value:
o When using VAX data types in memory (/FLOAT=G_FLOAT or
/FLOAT=D_FLOAT), the value exceeded the allowable maximum value
for the equivalent native format and was set equal to invalid.
o When using VAX data types in memory (/FLOAT=G_FLOAT or
/FLOAT=D_FLOAT), the value was infinity (plus or minus),
Not-a-Number (NaN), or otherwise invalid and was set to
invalid.
o When using IEEE data types in memory (/FLOAT=IEEE_FLOAT), the
value exceeded the allowable maximum value for the equivalent
native format and was set equal to infinity (plus or minus).
o When using IEEE data types in memory (/FLOAT=IEEE_FLOAT), the
value was infinity (plus or minus) and was set to infinity
(plus or minus).
o When using IEEE data types in memory (/FLOAT=IEEE_FLOAT), the
value was invalid and was set to Not-a-Number (NaN).
Make sure the correct file was specified. Make sure the record
layout matches the format VSI Fortran is expecting. Check that
the correct non-native floating-point data format was specified, as
described in the HP Fortran for OpenVMS User Manual.
This error is not returned by IOSTAT.
21 – FLODIV0EXC
NUMBER: 299 ERROR CODE: I MESSAGE TEXT: nn divide-by-zero traps EXPLANATION: The total number of floating-point divide-by-zero traps encountered during program execution was nn. This summary message appears at program completion. This error is not returned by IOSTAT.
22 – FLOINCEXC
NUMBER: 297 ERROR CODE: I MESSAGE TEXT: nn floating invalid traps EXPLANATION: The total number of floating-point invalid data traps encountered during program execution was nn. This summary message appears at program completion. This error is not returned by IOSTAT.
23 – FLOINEEXC
NUMBER: 296 ERROR CODE: I MESSAGE TEXT: nn floating inexact traps EXPLANATION: The total number of floating-point inexact data traps encountered during program execution was nn. This summary message appears at program completion. This error is not returned by IOSTAT.
24 – FLOOVEMAT
NUMBER: 88 ERROR CODE: F MESSAGE TEXT: floating overflow in math library EXPLANATION: A floating overflow condition was detected during execution of a math library procedure.
25 – FLOOVREXC
NUMBER: 298 ERROR CODE: I MESSAGE TEXT: nn floating overflow traps EXPLANATION: The total number of floating-point overflow traps encountered during program execution was nn. This summary message appears at program completion. This error is not returned by IOSTAT.
26 – FLOUNDEXC
NUMBER: 300 ERROR CODE: I MESSAGE TEXT: nn floating underflow traps EXPLANATION: The total number of floating-point underflow traps encountered during program execution was nn. This summary message appears at program completion. This error is not returned by IOSTAT.
27 – FLOUNDMAT
NUMBER: 89 ERROR CODE: E MESSAGE TEXT: floating underflow in math library EXPLANATION: A floating underflow condition was detected during execution of a math library procedure. The result returned was zero.
28 – FLTDIV
NUMBER: 73 ERROR CODE: E MESSAGE TEXT: zero divide EXPLANATION: During a floating-point or decimal arithmetic operation, an attempt was made to divide by 0.0. This error is not returned by IOSTAT.
29 – FLTINE
NUMBER: 140 ERROR CODE: E MESSAGE TEXT: floating inexact EXPLANATION: 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. This error is not returned by IOSTAT.
30 – FLTINV
NUMBER: 65 ERROR CODE: E MESSAGE TEXT: Floating invalid EXPLANATION: During an arithmetic operation, the floating-point values used in a calculation were invalid for the type of operation requested, or invalid exceptional values. For example, this occurs when requesting a log of the floating-point values 0.0 or a negative number. For certain arithmetic expressions, specifying the /CHECK=NOPOWER qualifier can suppress this message. For information on allowing exceptional IEEE values, see the HP Fortran for OpenVMS User Manual.
31 – FLTOVF
NUMBER: 72 ERROR CODE: E MESSAGE TEXT: arithmetic trap, floating overflow EXPLANATION: During an arithmetic operation, a floating-point value exceeded the largest representable value for that data type. The result returned was the reserved operand, -0 for VAX-format floating-point and NaN for IEEE-format floating-point. This error is not returned by IOSTAT.
32 – FLTUND
NUMBER: 74 ERROR CODE: E MESSAGE TEXT: Floating underflow EXPLANATION: During an arithmetic operation, a floating-point value became less than the smallest finite value for that data type. The underflowed result was either set to zero or, depending on the value of the /IEEE_MODE qualifier when /FLOAT=IEEE_FLOAT was specified, allowed to gradually underflow. This error is not returned by IOSTAT. For ranges of the various data types, see the Data Representation chapter in the HP Fortran for OpenVMS User Manual.
33 – FMTIO_UNF
NUMBER: 257 ERROR CODE: F MESSAGE TEXT: formatted I/O to unit open for unformatted transfers EXPLANATION: Attempted formatted I/O (such as list-directed or namelist I/O) to a unit where the OPEN statement indicated the file was unformatted (FORM specifier). Check that the correct unit (file) was specified. If the FORM specifier was not specified in the OPEN statement and the file should contain formatted data, specify FORM='FORMATTED' in the OPEN statement. Otherwise, if appropriate, use unformatted I/O.
34 – FMYSYN
NUMBER: 58 ERROR CODE: I MESSAGE TEXT: format syntax error at or near xx EXPLANATION: Check the statement containing xx, a character substring from the format string, for a format syntax error. For information about FORMAT statements, see the HP Fortran for OpenVMS Language Reference Manual. This error is not returned by IOSTAT.
35 – FORVARMIS
NUMBER: 61 ERROR CODE: F or I MESSAGE TEXT: format/variable-type mismatch EXPLANATION: An attempt was made either to read or write a real variable with an integer edit descriptor (I, L, B, O, or Z), or to read or write an integer or logical variable with a real field descriptor (D, E, or F). If /CHECK=NOFORMAT is in effect, the severity is I. If execution continued, the following actions occurred: o If I, L, B, O, or Z, conversion as if INTEGER(KIND=4). o If D, E, or F, conversion as if REAL(KIND=4). The ERR transfer is taken after completion of the I/O statement for this error number. The resulting file status and record position are the same as if no error had occurred. However, other I/O errors take the ERR transfer as soon as the error is detected, so file states and record position are undefined.
36 – INCFILORG
NUMBER: 51
ERROR CODE: F
MESSAGE TEXT: inconsistent file organization
EXPLANATION: One of the following conditions occurred:
o The file organization specified in an OPEN statement did not
match the organization of the existing file.
o The file organization of the existing file was inconsistent
with the specified access mode; that is, direct access was
specified with an indexed organization file, or keyed access
was specified with a sequential or relative organization file.
37 – INCKEYCHG
NUMBER: 50 ERROR CODE: F MESSAGE TEXT: inconsistent key change or duplicate key EXPLANATION: A WRITE or REWRITE statement accessing an indexed organization file caused a key field to change or be duplicated. This condition was not allowed by the attributes of the file, as established when the file was created.
38 – INCOPECLO
NUMBER: 46
ERROR CODE: F
MESSAGE TEXT: inconsistent OPEN/CLOSE parameters
EXPLANATION: Specifications in an OPEN or CLOSE statement were
inconsistent. Some invalid combinations follow:
o READONLY or ACTION='READ' with STATUS='NEW' or STATUS='SCRATCH'
o ACCESS='APPEND' with READONLY, ACTION='READ', STATUS='NEW', or
STATUS='SCRATCH'
o DISPOSE='SAVE', 'PRINT', or 'SUBMIT' with STATUS='SCRATCH'
o DISPOSE='DELETE' with READONLY or ACTION='READ'
o ACCESS='APPEND' with STATUS='REPLACE'
o ACCESS='DIRECT' or 'KEYED' with POSITION='APPEND' or 'ASIS'
o ACCESS='KEYED' with POSITION='REWIND'
39 – INCRECLEN
NUMBER: 37
ERROR CODE: F
MESSAGE TEXT: inconsistent record length
EXPLANATION: One of the following occurred:
o An attempt was made to create a new relative, indexed, or
direct access file without specifying a record length.
o An existing file was opened in which the record length did not
match the record size given in an OPEN or DEFINE FILE
statement.
o An attempt was made to write to a relative, indexed, or direct
access file that was not correctly created or opened.
40 – INCRECTYP
NUMBER: 44 ERROR CODE: F MESSAGE TEXT: inconsistent record type EXPLANATION: The RECORDTYPE value in an OPEN statement did not match the record type attribute of the existing file that was opened.
41 – INFFORLOO
NUMBER: 60 ERROR CODE: F MESSAGE TEXT: infinite format loop EXPLANATION: The format associated with an I/O statement that included an I/O list had no field descriptors to use in transferring those values.
42 – INPCONERR
NUMBER: 64 ERROR CODE: F MESSAGE TEXT: input conversion error EXPLANATION: During a formatted input operation, an invalid character was detected in an input field, or the input value overflowed the range representable in the input variable. The value of the variable was set to zero. The ERR transfer is taken after completion of the I/O statement for this error number. The resulting file status and record position are the same as if no error had occurred. However, other I/O errors take the ERR transfer as soon as the error is detected, so file states and record position are undefined.
43 – INPRECTOO
NUMBER: 22 ERROR CODE: F MESSAGE TEXT: input record too long EXPLANATION: 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 of the appropriate size.
44 – INPSTAREQ
NUMBER: 67 ERROR CODE: F MESSAGE TEXT: input statement requires too much data EXPLANATION: An attempt was made to read more data than exists in a record by using an unformatted READ statement or a formatted sequential READ statement from a file opened with PAD='NO'.
45 – INSVIRMEM
NUMBER: 41 ERROR CODE: F MESSAGE TEXT: insufficient virtual memory EXPLANATION: The HP Fortran Run-Time Library attempted to exceed its virtual page limit while dynamically allocating space. Inform your system manager that process quotas and/or system parameters need to be increased. This error can be returned by STAT in an ALLOCATE or DEALLOCATE statement.
46 – INTDIV
NUMBER: 71 ERROR CODE: F MESSAGE TEXT: integer zero divide EXPLANATION: During an integer arithmetic operation, an attempt was made to divide by zero. The result of the operation was set to the dividend, which is equivalent to division by one (1). This error is not returned by IOSTAT.
47 – INTOVF
NUMBER: 70 ERROR CODE: F MESSAGE TEXT: integer overflow EXPLANATION: During an arithmetic operation, an integer value exceeded its range. The result of the operation was the correct low-order part. Consider specifying a larger integer data size (or use the /INTEGER_SIZE qualifier for INTEGER declarations without a kind or specifier.) See the HP Fortran for OpenVMS User Manual for ranges of the various integer data types. This error is not returned by IOSTAT.
48 – INVARGFOR
NUMBER: 48 ERROR CODE: F MESSAGE TEXT: invalid argument to Fortran Run-Time Library EXPLANATION: The VSI Fortran compiler passed an invalid coded argument to the Run-Time Library. This can occur if the compiler is newer than the VSI Fortran Run-Time Library in use.
49 – INVARGMAT
NUMBER: 81 ERROR CODE: F MESSAGE TEXT: invalid argument to math library EXPLANATION: One of the mathematical procedures detected an invalid argument value.
50 – INVDEALLOC
NUMBER: 153 ERROR CODE: S MESSAGE TEXT: Allocatable array or pointer is not allocated EXPLANATION: A Fortran 90 allocatable array or pointer must already be allocated when you attempt to deallocate it. You must allocate the array or pointer before it can again be deallocated. This error is not returned by IOSTAT. However, this error can be returned by STAT in a DEALLOCATE statement.
51 – INVDEALLOC2
NUMBER: 173 ERROR CODE: S MESSAGE TEXT: A pointer passed to DEALLOCATE points to an array that cannot be deallocated EXPLANATION: A pointer that was passed to DEALLOCATE pointed to an explicit array, an array slice, or some other type of memory that could not be deallocated in a DEALLOCATE statement. Only whole arrays previous allocated with an ALLOCATE statement can be validly passed to DEALLOCATE. This error is not returned by IOSTAT. However, this error can be returned by STAT in a DEALLOCATE statement.
52 – INVKEYSPE
NUMBER: 49 ERROR CODE: F MESSAGE TEXT: invalid key specification EXPLANATION: A key specification in an OPEN statement or in a keyed-access READ statement was invalid. For example, the key length may have been zero or greater than 255 bytes, or the key length may not conform to the key specification of the existing file.
53 – INVLOGUNI
NUMBER: 32 ERROR CODE: F MESSAGE TEXT: invalid logical unit number EXPLANATION: A logical unit number less than zero or greater than 2,147,483,647 was used in an I/O statement.
54 – INVMATKEY
NUMBER: 94 ERROR CODE: F MESSAGE TEXT: invalid key match specifier for key direction EXPLANATION: A keyed READ used an invalid key match specifier for the direction of that key. Use KEYGE and KEYGT only on ascending keys. Use KEYLE and KEYLT only on descending keys. Use KEYNXT and KEYNXTNE to avoid enforcement of key direction and match specifier.
55 – INVREALLOC
NUMBER: 151 ERROR CODE: F MESSAGE TEXT: allocatable array is already allocated EXPLANATION: A Fortran 95/90 allocatable array must not already be allocated when you attempt to allocate it. You must deallocate the array before it can again be allocated. This error is not returned by IOSTAT. However, this error can be returned by STAT in an ALLOCATE statement.
56 – INVREFVAR
NUMBER: 19
ERROR CODE: F
MESSAGE TEXT: invalid reference to variable in NAMELIST input
EXPLANATION: The variable in error is shown as "varname" in the
message text. One of the following conditions occurred:
o The variable was not a member of the namelist group.
o An attempt was made to subscript a scalar variable.
o A subscript of the array variable was out-of-bounds.
o An array variable was specified with too many or too few
subscripts for the variable.
o An attempt was made to specify a substring of a noncharacter
variable or array name.
o A substring specifier of the character variable was
out-of-bounds.
o A subscript or substring specifier of the variable was not an
integer constant.
o An attempt was made to specify a substring using an
unsubscripted array variable.
57 – KEYIO_DIR
NUMBER: 260 ERROR CODE: F MESSAGE TEXT: keyed-access I/O to unit open for direct access EXPLANATION: The OPEN for this unit number specified direct access and the I/O statement specifies keyed access. Check the OPEN statement and make sure the I/O statement uses the correct unit number and type of access. (For more information on statements, see the HP Fortran for OpenVMS Language Reference Manual.)
58 – KEYVALERR
NUMBER: 45 ERROR CODE: F MESSAGE TEXT: keyword value error in OPEN statement EXPLANATION: An improper value was specified for an OPEN or CLOSE statement keyword requiring a value.
59 – LISIO_SYN
NUMBER: 59 ERROR CODE: F MESSAGE TEXT: list-directed I/O syntax error EXPLANATION: 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. The ERR transfer is taken after completion of the I/O statement for this error number. The resulting file status and record position are the same as if no error had occurred. However, other I/O errors take the ERR transfer as soon as the error is detected, so file states and record position are undefined.
60 – LOGZERNEG
NUMBER: 83 ERROR CODE: F MESSAGE TEXT: logarithm of zero or negative value EXPLANATION: An attempt was made to take the logarithm of zero or a negative number. The result returned was the reserved operand, -0 for VAX-format floating-point and NaN for IEEE-format floating-point.
61 – MIXFILACC
NUMBER: 31
ERROR CODE: F
MESSAGE TEXT: mixed file access modes
EXPLANATION: One of the following conditions occurred:
o An attempt was made to use both formatted and unformatted
operations on the same unit.
o An attempt was made to use an invalid combination of access
modes on a unit, such as direct and sequential. The only valid
combination is sequential and keyed access on a unit opened
with ACCESS='KEYED'.
o An attempt was made to execute a Fortran I/O statement on a
logical unit that was opened by a program coded in a language
other than Fortran.
62 – NO_CURREC
NUMBER: 53 ERROR CODE: F MESSAGE TEXT: no current record EXPLANATION: A REWRITE or current record DELETE operation was attempted when no current record was defined.
63 – NO_SUCDEV
NUMBER: 42 ERROR CODE: F MESSAGE TEXT: no such device EXPLANATION: A file specification included an invalid or unknown device name when an OPEN operation was attempted.
64 – NOTFORSPE
NUMBER: 1 ERROR CODE: F MESSAGE TEXT: not a Fortran-specific error EXPLANATION: An error occurred in the user program or in the VSI Fortran RTL that was not a Fortran-specific error and was not reportable through any other VSI Fortran run-time messages. This error is not returned by IOSTAT.
65 – NULPTRERR
NUMBER: 146 ERROR CODE: F MESSAGE TEXT: null pointer error EXPLANATION: An attempt was made to use a pointer that does not contain an address. Modify the source program, recompile, and relink. This error is not returned by IOSTAT.
66 – OPEDEFREQ
NUMBER: 26
ERROR CODE: F
MESSAGE TEXT: OPEN or DEFINE FILE required for keyed or direct
access
EXPLANATION: One of the following conditions occurred:
o A direct access READ, WRITE, FIND, or DELETE statement
specified a file that was not opened with a DEFINE FILE
statement or with an OPEN statement specifying ACCESS='DIRECT'.
o A keyed access READ statement specified a file that was not
opened with an OPEN statement specifying ACCESS='KEYED'.
67 – OPEFAI
NUMBER: 30 ERROR CODE: F MESSAGE TEXT: open failure EXPLANATION: An error was detected by RMS 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 is attempted for one of the following: o A segmented file that was not on a disk or a raw magnetic tape o A standard process I/O file that has been closed
68 – OPEREQSEQ
NUMBER: 265 ERROR CODE: F MESSAGE TEXT: operation requires sequential file organization and access EXPLANATION: Attempted BACKSPACE operation for a unit that is not connected to a sequential file opened for sequential access. Make sure the BACKSPACE statement specified the right unit number and the OPEN statement specified the correct file and access.
69 – OPERREQDIS
NUMBER: 264 ERROR CODE: F MESSAGE TEXT: operation requires file to be on disk or tape EXPLANATION: Attempted BACKSPACE operation for a unit that is not connected to a disk or tape device. Make sure the BACKSPACE statement specified the right unit number and the OPEN statement specified the correct device.
70 – OUTCONERR
NUMBER: 63 ERROR CODE: E or I MESSAGE TEXT: output conversion error EXPLANATION: 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. If /CHECK=NOOUTPUT_CONVERSION is in effect, the severity is I. In this case (or if no ERR address is defined for the I/O statement encountering this error), the program continues and the entire overflowed field is filled with asterisks (*) to indicate the error in the output record. The ERR transfer is taken after completion of the I/O statement for this error number. The resulting file status and record position are the same as if no error had occurred. However, other I/O errors take the ERR transfer as soon as the error is detected, so file states and record position are undefined.
71 – OUTSTAOVE
NUMBER: 66 ERROR CODE: F MESSAGE TEXT: output statement overflows record EXPLANATION: An output statement attempted to transfer more data than would fit in the maximum record size.
72 – RANGEERR
NUMBER: 150 ERROR CODE: F MESSAGE TEXT: range error EXPLANATION: An integer value appears in a context where the value of the integer is outside the permissible range. This error is not returned by IOSTAT.
73 – RECIO_OPE
NUMBER: 40
ERROR CODE: F
MESSAGE TEXT: recursive I/O operation
EXPLANATION: While processing an I/O statement for a logical unit,
another I/O operation on the same logical unit was attempted. One
of the following conditions may have occurred:
o A function subprogram that performs I/O to the same logical
unit was referenced in an expression in an I/O list or variable
format expression.
o An I/O statement was executed at AST level for the same logical
unit.
o An exception handler (or a procedure it called) executed an I/O
statement in response to a signal from an I/O statement for the
same logical unit.
74 – RECNUMOUT
NUMBER: 25 ERROR CODE: F MESSAGE TEXT: record number outside range EXPLANATION: A direct access READ, WRITE, or FIND statement specified a record number outside the range specified when the file was created.
75 – RESACQFAI
NUMBER: 152 ERROR CODE: F MESSAGE TEXT: unresolved contention for VSI Fortran RTL global resource EXPLANATION: Failed to acquire a VSI Fortran RTL global resource for a reentrant routine. For a multithreaded program, the requested global resource is held by a different thread in your program. For a program using asynchronous handlers, the requested global resource is held by the calling part of the program (such as the main program) and your asynchronous handler attempted to acquire the same global resource. This error is not returned by IOSTAT.
76 – REWERR
NUMBER: 20
ERROR CODE: F
MESSAGE TEXT: REWIND error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file.
o The file was not opened for sequential or append access.
o RMS detected an error condition during execution of a REWIND
statement.
77 – REWRITERR
NUMBER: 54 ERROR CODE: F MESSAGE TEXT: REWRITE error EXPLANATION: RMS detected an error condition during execution of a REWRITE statement.
78 – ROPRAND
NUMBER: 144 ERROR CODE: F MESSAGE TEXT: reserved operand EXPLANATION: VSI Fortran encountered a reserved operand. Please report the problem to HP. This error is not returned by IOSTAT.
79 – SEGRECFOR
NUMBER: 35 ERROR CODE: F MESSAGE TEXT: segmented record format error EXPLANATION: An invalid segmented record control data word 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.
80 – SEQIO_DIR
NUMBER: 259 ERROR CODE: F MESSAGE TEXT: sequential-access I/O to unit open for direct access EXPLANATION: The OPEN for this unit number specified direct access and the I/O statement specifies sequential access. Check the OPEN statement and make sure the I/O statement uses the correct unit number and type of access. (For more information on statements, see the HP Fortran for OpenVMS Language Reference Manual.)
81 – SHORTDATEARG
NUMBER: 175 ERROR CODE: F MESSAGE TEXT: DATE argument to DATE_AND_TIME is too short (LEN=n), required LEN=8 EXPLANATION: The number of characters associated with the DATE argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 8 characters in length. Verify that the TIME and ZONE arguments also meet their minimum lengths. This error is not returned by IOSTAT.
82 – SHORTTIMEARG
NUMBER: 176 ERROR CODE: F MESSAGE TEXT: TIME argument to DATE_AND_TIME is too short (LEN=n), required LEN=10 EXPLANATION: The number of characters associated with the TIME argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 10 characters in length. Verify that the DATE and ZONE arguments also meet their minimum lengths. This error is not returned by IOSTAT.
83 – SHORTZONEARG
NUMBER: 177 ERROR CODE: F MESSAGE TEXT: ZONE argument to DATE_AND_TIME is too short (LEN=n), required LEN=5 EXPLANATION: The number of characters associated with the ZONE argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 5 characters in length. Verify that the DATE and TIME arguments also meet their minimum lengths. This error is not returned by IOSTAT.
84 – SIGLOSMAT
NUMBER: 87 ERROR CODE: F MESSAGE TEXT: significance lost in math library EXPLANATION: The magnitude of an argument or the magnitude of the ratio of the arguments to a math library function was so large that all significance in the result was lost. The result returned was the reserved operand, -0.
85 – SPERECLOC
NUMBER: 52 ERROR CODE: F MESSAGE TEXT: specified record locked EXPLANATION: A read operation or direct access write, find, or delete operation was attempted on a record that was locked by another user.
86 – SQUROONEG
NUMBER: 84 ERROR CODE: F MESSAGE TEXT: square root of negative value EXPLANATION: An argument required the evaluation of the square root of a negative value. The result returned was the reserved operand, -0 for VAX-format floating-point and NaN for IEEE-format floating-point.
87 – STKOVF
NUMBER: 147 ERROR CODE: F MESSAGE TEXT: stack overflow EXPLANATION: The VSI Fortran RTL encountered a stack overflow while executing your program. This error is not returned by IOSTAT.
88 – STRLENERR
NUMBER: 148 ERROR CODE: F MESSAGE TEXT: string length error EXPLANATION: During a string operation, an integer value appears in a context where the value of the integer is outside the permissible string length range. Try recompiling with /CHECK=BOUNDS or examine the source code. This error is not returned by IOSTAT.
89 – SUBRNG
NUMBER: 77 ERROR CODE: F MESSAGE TEXT: subscript out of range EXPLANATION: An array reference was detected outside the declared array bounds. This error is not returned by IOSTAT.
90 – SUBSTRERR
NUMBER: 149 ERROR CODE: F MESSAGE TEXT: substring error EXPLANATION: An array subscript is outside the dimensioned boundaries of an array. Try recompiling with /CHECK=BOUNDS or examine source code. This error is not returned by IOSTAT.
91 – SYNERRFOR
NUMBER: 62 ERROR CODE: F MESSAGE TEXT: syntax error in format EXPLANATION: A syntax error was encountered while the HP Fortran RTL was processing a format stored in an array or character variable.
92 – SYNERRNAM
NUMBER: 17 ERROR CODE: F MESSAGE TEXT: syntax error in NAMELIST input "text" EXPLANATION: The syntax of input to a namelist READ statement was incorrect. (The part of the record in which the error was detected is shown as "text" in the message text.)
93 – TOOMANREC
NUMBER: 27
ERROR CODE: F
MESSAGE TEXT: too many records in I/O statement
EXPLANATION: One of the following conditions occurred:
o An attempt was made to read or write more than one record with
an ENCODE or DECODE statement.
o An attempt was made to write more records than existed.
94 – TOOMANVAL
NUMBER: 18 ERROR CODE: F MESSAGE TEXT: too many values for NAMELIST variable "varname" EXPLANATION: An attempt was made to assign too many values to a variable during a namelist READ statement. (The name of the variable is shown as "varname" in the message text.)
95 – UNDEXP
NUMBER: 82 ERROR CODE: F MESSAGE TEXT: undefined exponentiation EXPLANATION: An exponentiation that is mathematically undefined was attempted, for example, 0.**0. The result returned for floating-point operations was the reserved operand, -0 for VAX-format floating-point and NaN for IEEE-format floating-point. For integer operations, zero is returned.
96 – UNFIO_FMT
NUMBER: 256 ERROR CODE: F MESSAGE TEXT: unformatted I/O to unit open for formatted transfers EXPLANATION: Attempted unformatted I/O to a unit where the OPEN statement indicated the file was formatted (FORM specifier). Check that the correct unit (file) was specified. If FORM was not specified in the OPEN statement and the file should contain unformatted data, specify FORM='UNFORMATTED' in the OPEN statement. Otherwise, if appropriate, use formatted I/O (such as list-directed or namelist I/O).
97 – UNIALROPE
NUMBER: 34 ERROR CODE: F MESSAGE TEXT: unit already open EXPLANATION: A DEFINE FILE statement specified a logical unit that was already opened.
98 – UNLERR
NUMBER: 56 ERROR CODE: F MESSAGE TEXT: UNLOCK error EXPLANATION: RMS detected an error condition during execution of an UNLOCK statement.
99 – VFEVALERR
NUMBER: 68 ERROR CODE: F MESSAGE TEXT: variable format expression value error EXPLANATION: The value of a variable format expression was not within the range acceptable for its intended use; for example, a field width was less than or equal to zero. A value of one was assumed, except for a P edit descriptor, for which a value of zero was assumed. The ERR transfer is taken after completion of the I/O statement for this error number. The resulting file status and record position are the same as if no error had occurred. However, other I/O errors take the ERR transfer as soon as the error is detected, so file states and record position are undefined.
100 – WRIREAFIL
NUMBER: 47 ERROR CODE: F MESSAGE TEXT: write to READONLY file EXPLANATION: A write operation was attempted to a file that was declared ACTION='READ' or READONLY in the OPEN statement that is currently in effect.
101 – WRONUMARG
NUMBER: 80 ERROR CODE: F MESSAGE TEXT: wrong number of arguments EXPLANATION: An improper number of arguments was used to call a math library procedure.