FORTRAN, Error Messages, Run Time Errors
*Conan The Librarian (sorry for the slow response - running on an old VAX)
|
VMS Help FORTRAN, Error Messages, Run Time Errors *Conan The Librarian (sorry for the slow response - running on an old VAX) |
|
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. Refer to the OpenVMS Run-Time Library Reference
Manuals for more information.
In order of greatest to least severity, the three classes of
run-time diagnostic messages are as follows:
Code Description
---- -----------
F Severe error; must be corrected. The program
cannot complete execution and is terminated when
the error is encountered.
E Error; should be corrected. The program may
continue execution, but the output from this
execution may be incorrect.
W Warning; should be investigated. The program
continues executing, but output from this execution
may be incorrect.
The following example shows how run-time messages are displayed:
%FOR-F-ADJARRDIM, adjustable array dimension error
In this Help file, the letter "C" after an error code indicates
that program execution can continue immediately after the error if
a user-written condition handler specifies that execution continue.
| 1 - General |
1.1 - ADJARRDIM
NUMBER: 93
ERROR CODE: F, C
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 the
addressable memory.
1.2 - 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.
1.3 - 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 can not be backspaced until a REWIND
statement is executed for that unit.)
o RMS detected an error condition during execution of a BACKSPACE
statement.
1.4 - CLOERR
NUMBER: 28 ERROR CODE: F MESSAGE TEXT: CLOSE error EXPLANATION: An error condition was detected by RMS during execution of a CLOSE statement.
1.5 - 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 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.
1.6 - 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. One of the following conditions occurred: o A DEFINE FILE was followed by another DEFINE FILE statement. o A DEFINE FILE was followed by an OPEN statement. o A CALL ASSIGN or CALL FDBSET was followed by an OPEN statement.
1.7 - 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.
1.8 - 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 or append access.
o An unformatted file did not contain segmented records.
o RMS detected an error during execution of an ENDFILE statement.
1.9 - ERRDURREA
NUMBER: 39 ERROR CODE: F MESSAGE TEXT: error during read EXPLANATION: RMS detected an error condition during execution of a READ statement.
1.10 - ERRDURWRI
NUMBER: 38 ERROR CODE: F MESSAGE TEXT: error during write EXPLANATION: RMS detected an error condition during execution of a WRITE statement.
1.11 - FILNAMSPE
NUMBER: 43 ERROR CODE: F MESSAGE TEXT: file name specification error EXPLANATION: A file-name specification given to OPEN, INQUIRE, or CALL ASSIGN statement was not acceptable to RMS.
1.12 - 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.
1.13 - FINERR
NUMBER: 57 ERROR CODE: F MESSAGE TEXT: FIND error EXPLANATION: RMS detected an error condition during execution of a FIND statement.
1.14 - FLOCONFAI
NUMBER: 95 ERROR CODE: E MESSAGE TEXT: floating point conversion failed EXPLANATION: The attempted unformatted read or write of nonnative floating-point data failed. A nonnative floating-point value either exceeded the allowable maximum value for the equivalent native format and was set equal to invalid, or the value was infinity (plus or minus), not a number (NaN), or otherwise invalid and was set to invalid. Very small numbers are set to zero (0). This could be caused by the specified nonnative floating-point format not matching the floating-point format found in the specified file. Make sure the correct file was specified. Make sure the record layout matches the format Compaq Fortran is expecting. Check that the correct nonnative floating-point data format was specified, as described in your user manual.
1.15 - FLOOVEMAT
NUMBER: 88 ERROR CODE: F, C MESSAGE TEXT: floating overflow in math library EXPLANATION: A floating overflow condition was detected during execution of a math library procedure. The result returned was the reserved operand, -0.
1.16 - FLOUNDMAT
NUMBER: 89 ERROR CODE: F, C 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.
1.17 - FLTDIV
NUMBER: 73 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, zero divide EXPLANATION: During a floating-point or decimal arithmetic operation, an attempt was made to divide by 0.0. If floating-point, the result returned is the the reserved operand, -0. If decimal, the result of the operation is unpredictable.
1.18 - FLTDIV_F
NUMBER: 73 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, zero divide EXPLANATION: During a floating-point arithmetic operation, an attempt was made to divide by zero.
1.19 - FLTOVF
NUMBER: 72 ERROR CODE: F, C 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 of the operation was set to the reserved operand, -0.
1.20 - FLTOVF_F
NUMBER: 72 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, floating overflow EXPLANATION: During an arithmetic operation, a floating-point value exceeded the largest representable value for that data type.
1.21 - FLTUND
NUMBER: 74 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, floating underflow EXPLANATION: During an arithmetic operation a floating-point value became less than the smallest representable value for that data type and was replaced with a value of zero.
1.22 - FLTUND_F
NUMBER: 74 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, floating underflow EXPLANATION: During an arithmetic operation a floating-point value became less than the smallest representable value for that data type.
1.23 - FORVARMIS
NUMBER: 61 ERROR CODE: F, C MESSAGE TEXT: format/variable-type mismatch EXPLANATION: An attempt was made either to read or write a real variable with an integer field descriptor (I or L), or to read or write an integer or logical variable with a real field descriptor (D, E, F, or G). If execution continued, one of the following actions occurred: o If I or L, conversion as if INTEGER*4. o If D, E, F, or G, conversion as if REAL*4.
1.24 - 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, either direct access
was specified with an indexed organization file or keyed access
was specified with a sequential or relative organization file.
1.25 - INCKEYCHG
NUMBER: 50 ERROR CODE: F MESSAGE TEXT: inconsistent key change or duplicate key EXPLANATION: A WRITE or REWRITE to 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.
1.26 - 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 are:
o READONLY with STATUS='NEW' or STATUS='SCRATCH'
o ACCESS='APPEND' with READONLY, STATUS='NEW', or
STATUS='SCRATCH'
o DISPOSE='SAVE', 'PRINT', or 'SUBMIT' with STATUS='SCRATCH'
o DISPOSE='DELETE' with READONLY
1.27 - INCRECLEN
NUMBER: 37
ERROR CODE: F
MESSAGE TEXT: inconsistent record length
EXPLANATION: One of the following conditions 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.
1.28 - 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.
1.29 - 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.
1.30 - INPCONERR
NUMBER: 64 ERROR CODE: F, C MESSAGE TEXT: input conversion error EXPLANATION: During a formatted input operation, either 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.
1.31 - INPRECTOO
NUMBER: 22 ERROR CODE: F MESSAGE TEXT: input record too long EXPLANATION: A record was read that exceeded the explicit or the default record length specified in OPEN (or by the default OPEN). To read the file, use an OPEN statement with a RECL value of the appropriate size.
1.32 - INPSTAREQ
NUMBER: 67 ERROR CODE: F MESSAGE TEXT: input statement requires too much data EXPLANATION: An unformatted READ statement attempted to read more data than existed in the record being read.
1.33 - INSVIRMEM
NUMBER: 41 ERROR CODE: F MESSAGE TEXT: insufficient virtual memory EXPLANATION: The Compaq Fortran Run-Time Library attempted to exceed its virtual page limit while dynamically allocating space.
1.34 - INTDIV
NUMBER: 71 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, 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.35 - INTOVF
NUMBER: 70 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, integer overflow EXPLANATION: During an arithmetic operation, an integer value exceeded byte, word, or longword range. The result of the operation was the correct low-order part.
1.36 - INVARGFOR
NUMBER: 48
ERROR CODE: F
MESSAGE TEXT: invalid argument to Fortran Run-Time Library
EXPLANATION: One of the following conditions occurred:
o An invalid argument was given to a PDP-11 FORTRAN compatibility
subroutine, such as ERRSET.
o The Compaq Fortran compiler passed an invalid coded argument to
the Run-Time Library. This can occur if the compiler is newer
than the Run-Time Library in use.
1.37 - INVARGMAT
NUMBER: 81 ERROR CODE: F MESSAGE TEXT: invalid argument to math library EXPLANATION: One of the mathematical procedures detected an invalid argument value.
1.38 - 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.
1.39 - INVLOGUNI
NUMBER: 32 ERROR CODE: F MESSAGE TEXT: invalid logical unit number EXPLANATION: A logical unit number greater than 119 or less than zero was used in an I/O statement.
1.40 - 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.
1.41 - INVREFVAR
NUMBER: 19
ERROR CODE: F
MESSAGE TEXT: invalid reference to variable "varname" in namelist
input
EXPLANATION: The name of the variable in error is substituted for
"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 the scalar variable.
o A subscript of the array variable was out-of-bounds.
o There were 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 is
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.
1.42 - KEYVALERR
NUMBER: 45 ERROR CODE: F MESSAGE TEXT: keyword value error in OPEN statement EXPLANATION: An OPEN or CLOSE statement keyword requiring a value had an improper value. Refer to the DEC Fortran Language Reference Manual for the allowed keyword values.
1.43 - LISIO_SYN
NUMBER: 59 ERROR CODE: F, C 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.
1.44 - LOGZERNEG
NUMBER: 83 ERROR CODE: F, C 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.
1.45 - 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 language other than Fortran.
1.46 - NO_CURREC
NUMBER: 53 ERROR CODE: F MESSAGE TEXT: no current record EXPLANATION: A REWRITE or current record DELETE was attempted when no current record was defined.
1.47 - NO_SUCDEV
NUMBER: 42 ERROR CODE: F MESSAGE TEXT: no such device EXPLANATION: A file-name specification included an invalid or unknown device name when an open operation was attempted.
1.48 - NOTFORSPE
NUMBER: 1 ERROR CODE: F MESSAGE TEXT: not a Fortran-specific error EXPLANATION: An error occurred in the user program or in the Run-Time Library that was not a Fortran-specific error. Therefore it was not reportable through any other message in the table. If you call ERRSNS, an error of this kind returns a value of 1. Use the fifth argument of the call to ERRSNS (condval) to obtain the unique system condition value that identifies the error.
1.49 - 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'.
1.50 - 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 used when the error condition is not one of the more common conditions for which specific error messages are provided.
1.51 - OUTCONERR
NUMBER: 63 ERROR CODE: E, C 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. When this error occurs, the field is filled with asterisks.
1.52 - 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.
1.53 - 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.
1.54 - 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.
1.55 - 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.
1.56 - REWRITERR
NUMBER: 54 ERROR CODE: F MESSAGE TEXT: REWRITE error EXPLANATION: RMS detected an error condition during execution of a REWRITE statement.
1.57 - 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 written in a language other that Fortran, or created with RECORDTYPE='FIXED' or 'VARIABLE' in effect.
1.58 - SIGLOSMAT
NUMBER: 87 ERROR CODE: F, C 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.
1.59 - SPERECLOC
NUMBER: 52 ERROR CODE: F MESSAGE TEXT: specified record locked EXPLANATION: A READ or direct access WRITE, FIND, or DELETE was attempted on a record that was locked by another user.
1.60 - SQUROONEG
NUMBER: 84 ERROR CODE: F, C 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.
1.61 - SUBRNG
NUMBER: 77 ERROR CODE: F, C MESSAGE TEXT: trap, subscript out of range EXPLANATION: An array reference was detected outside the declared array bounds.
1.62 - SYNERRFOR
NUMBER: 62 ERROR CODE: F MESSAGE TEXT: syntax error in format EXPLANATION: A syntax error was encountered while the Run-Time Library was processing a format stored in an array or character variable.
1.63 - 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 substituted for "text" in the message text.
1.64 - 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.
1.65 - 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 substituted for "varname" in the message text.
1.66 - UNDEXP
NUMBER: 82 ERROR CODE: F, C MESSAGE TEXT: undefined exponentiation EXPLANATION: An exponentiation that is mathematically undefined was attempted, for example, 0.**0. The result returned was the reserved operand -0 (for floating-point operations) or zero (for integer operations).
1.67 - UNIALROPE
NUMBER: 34 ERROR CODE: F MESSAGE TEXT: unit already open EXPLANATION: A DEFINE FILE statement specified a logical unit that was already opened.
1.68 - UNLERR
NUMBER: 56 ERROR CODE: F MESSAGE TEXT: UNLOCK error EXPLANATION: RMS detected an error condition during execution of an UNLOCK statement.
1.69 - VFEVALERR
NUMBER: 68 ERROR CODE: F, C 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.
1.70 - WRIREAFIL
NUMBER: 47 ERROR CODE: F MESSAGE TEXT: write to READONLY file EXPLANATION: A write operation was attempted to a file that was declared READONLY in the OPEN statement that is currently in effect.
1.71 - 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.
| 2 - Parallel Processing Specific |
2.1 - COMSHRERR
SEVERITY: F MESSAGE TEXT: Unable to share memory region from x to y EXPLANATION: The Fortran Run-Time Library could not make the specified memory region shared among the processes participating in the parallel processing environment.
2.2 - DEFVALUSED
SEVERITY: I MESSAGE TEXT: Default value of xx used for logical name EXPLANATION: A default value was used for the specified logical name.
2.3 - FAIACTCPU
SEVERITY: F MESSAGE TEXT: Failed to obtain active CPU count EXPLANATION: The Fortran Run-Time Library could not obtain the active CPU count. Thus, it was unable to set up the parallel processing environment.
2.4 - FAIDCLEXIT
SEVERITY: F MESSAGE TEXT: Failed to declare an exit handler EXPLANATION: The Fortran Run-Time Library could not declare an exit handler. Thus, it was unable to set up the parallel processing environment.
2.5 - FAIIDPRC
SEVERITY: F MESSAGE TEXT: Failed to identify the process EXPLANATION: The Fortran Run-Time Library could not identify the process. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.6 - FAIIMAGNAME
SEVERITY: F MESSAGE TEXT: Failed to obtain image name EXPLANATION: The Fortran Run-Time Library could not obtain the image name. Thus, it was unable to set up the parallel processing environment.
2.7 - FAIOWNERID
SEVERITY: F MESSAGE TEXT: Failed to obtain owner process ID EXPLANATION: The Fortran Run-Time Library could not obtain the owner process identification. Thus, it was unable to set up the parallel processing environment.
2.8 - FAIPRCID
SEVERITY: F MESSAGE TEXT: Failed to obtain process ID EXPLANATION: The Fortran Run-Time Library could not obtain the process identification. Thus, it was unable to set up the parallel processing environment.
2.9 - FAIPRCNAME
SEVERITY: F MESSAGE TEXT: Failed to obtain process name EXPLANATION: The Fortran Run-Time Library could not obtain the process name. Thus, it was unable to set up the parallel processing environment.
2.10 - FAISHRSTACK
SEVERITY: F MESSAGE TEXT: Unable to share the stack region from x to y EXPLANATION: The Fortran Run-Time Library could not make the specified stack region shared among processes participating in the parallel processing environment.
2.11 - FAISUBPRC
SEVERITY: F MESSAGE TEXT: Failed to create subprocess EXPLANATION: The Fortran Run-Time Library could not get the process identification. Thus, it was unable to set up the parallel processing environment.
2.12 - FATINTERR
SEVERITY: F MESSAGE TEXT: Fatal internal error in the Fortran Parallel Processing Run-Time Library EXPLANATION: The Fortran Run-Time Library detected an unrecoverable, inconsistent condition. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.13 - INVCOMADR
SEVERITY: F MESSAGE TEXT: Invalid memory region addresses EXPLANATION: The Fortran Run-Time Library detected invalid starting and ending addresses for a shared memory region. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.14 - INVLCLADR
SEVERITY: F MESSAGE TEXT: Invalid $LOCAL PSECT addresses EXPLANATION: The Fortran Run-Time Library detected invalid starting and ending addresses for a $LOCAL PSECT. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.15 - INVLOGNAM
SEVERITY: E MESSAGE TEXT: Invalid logical name definition EXPLANATION: A logical name was defined incorrectly.
2.16 - INVNUMPRC
SEVERITY: F MESSAGE TEXT: Invalid number of processes EXPLANATION: The Fortran Run-Time Library detected an invalid number of processes. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.17 - INVUNWIND
SEVERITY: F MESSAGE TEXT: Invalid stack unwinding encountered EXPLANATION: The Fortran Run-Time Library detected an invalid attempt to unwind the stack.
2.18 - LOCALACCESS
SEVERITY: F MESSAGE TEXT: Subprocess unable to access the shared $LOCAL PSECT EXPLANATION: A subprocess could not access the shared $LOCAL PSECT.
2.19 - LOCALSHRERR
SEVERITY: F MESSAGE TEXT: Unable to share the $LOCAL PSECT EXPLANATION: The Fortran Run-Time Library could not make the $LOCAL PSECT shared among the processes participating in the parallel processing environment.
2.20 - MEMSHRERR
SEVERITY: F MESSAGE TEXT: Memory sharing error EXPLANATION: The Fortran Run-Time Library failed to share data among the processes participating in the parallel processing environment.
2.21 - NOPARINIT
SEVERITY: I MESSAGE TEXT: Parallel processing environment was not available EXPLANATION: The Compaq Fortran main program was not compiled with /PARALLEL. As a result, the parallel processing environment was not available.
2.22 - NOTIMPRET
SEVERITY: F MESSAGE TEXT: Routine not implemented in this version of FORRTL2 EXPLANATION: An attempt was made to use a routine that is not implemented in this version of the Fortran Run-Time Library.
2.23 - NOTRUNINPP
SEVERITY: I MESSAGE TEXT: Unable to run the DO-Loop PC: xx in parallel EXPLANATION: A parallel DO loop with the specified PC address cannot run in parallel.
2.24 - STACKSHRERR
SEVERITY: F MESSAGE TEXT: Stack sharing error EXPLANATION: The Fortran Run-Time Library could not make the stack shared among the processes participating in the parallel processing environment.
2.25 - STKBUFOVR
SEVERITY: F MESSAGE TEXT: Stack buffer overflow was detected EXPLANATION: An internal limit on the number of shared stack regions that your program can have was exceeded. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2.26 - SUBPRCDIED
SEVERITY: F MESSAGE TEXT: Subprocess PID: xx terminated EXPLANATION: A subprocess with the specified process ID was terminated.
2.27 - TOOMANPRC
SEVERITY: E MESSAGE TEXT: Too many processes, allowed a maximum of 32 processes EXPLANATION: A limit on the number of processes participating in the Fortran parallel processing environment was exceeded. The limit is currently 32.
|
|
