To get HELP on a given error number nn, type HELP FOR ERROR Rnn (run time errors) or HELP FOR ERROR Cx (compile errors) 3 R1 INVALID ERROR CALL A TRAP instruction has occurred whose low byte is in the range used by the OTS for error reporting, but for which no error condition exists. 3 R2 TASK INITIALISATION FAILURE The most common error is to require an FPP unit on a machine without one. 3 R3 ODD ADDRESS TRAP THE PROGRAM HAS MADE A WORD REFERENCE TO AN ODD BYTE ADDRESS 3 R4 SEGMENT FAULT THIS MOST LIKELY DUE TO A SUBSCRIPT VALUE OUT OF RANGE ON AN ARRAY REFERENCE. 3 R5 T-BIT OR BPT TRAP(SST2) A trap has occurred as a result of the trace bit being set in the processor status word or the execution of a BPT instruction. 3 R6 IOT TRAP 3 R7 RESERVED INSTRUCTION TRAP 3 R8 NON-RSX EMT TRAP 3 R9 TRAP INSTRUCTION TRAP 3 R10 PDP 11/40 FIS TRAP 3 R11 FPP HARDWARE FAULT 3 R12 FPP ILLEGAL OPCODE TRAP 3 R13 FPP UNDEFINED VARIABLE TRAP 3 R14 FPP MAINTENANCE MODE TRAP 3 R20 REWIND ERROR An error condition was detected by FCS during the .POINT operation used to position at the beginning of a file. 3 R21 DEFINEFILE ALREADY DONE Multiple attempts to specify file attributes have been attempted without an intervening close operation by either, a) DEFINEFILE followed by DEFINEFILE b) DEFINEFILE, CALL ASSIGN or CALL FDBSET followed by an OPEN statement. 3 R22 RECORD TOO LONG A record has been read which is too large to fit into the user record buffer. Rebuild the task using a larger Task Builder MAXBUF specification. 3 R23 BACKSPACE ERROR One of the following happened. a) BACKSPACE was attempted on a file opened for appending. b) FCS has detected an error condition during the .POINT operation used to rewind the file. c) FCS has detected an error condition while reading forward to the desired record. 3 R24 END-OF-FILE DURING READ Either an end-file recored produced by the ENDFILE statement or the FCS end of file condition has been encountered during a READ statement and no END= transfer specification was provided. 3 R25 INVALID RECORD NUMBER A direct access READ, WRITE, or FIND statement has specified a record number outside the range from one to the value specified in a DEFINEFILE statement or in the MAXREC keyword of the OPEN statement. 3 R26 DEFINEFILE NOT DONE A direct access READ, WRITE, or FIND operation was attempted before a DEFINEFILE or an OPEN statement with ACCESS = 'DIRECT' was performed. 3 R27 MORE THAN ONE RECORD An attempt was made to read or write more than a single record in a direct access READ or WRITE statement, or an ENCODE or DECODE statement. 3 R28 CLOSE ERROR An error condition has been detected by FCS during a CLOSE$, .DLFNB, or .PRINT operation when trying to close a file. 3 R29 NO SUCH FILE A file with the specified name could not be found during an OPEN operation. 3 R30 OPEN FAILURE FCS has detected an error condition during an open operation. 3 R31 MIXED ACCESS MODES An attempt was made to use both formatted and unformatted I/O, or both sequential and direct access operations on the same logical unit number(ie file). 3 R32 INVALID LOGICAL UNIT NUMBER You have specified a LUN outside the range specified by the Task Builder with its UNITS option. 3 R33 ENDFILE TO DIRECT ACCESS FILE End-of-file records may not be written to direct access files. 3 R34 UNIT ALREADY OPEN An OPEN,DEFINEFILE, CALL ASSIGN, or CALL FDBSET was attempted on a file which was already opened for I/O. 3 R37 INCONSISTENT RECORD LENGTH An existing direct access file has been opened whose record length attribute is not the same as specified in the DEFINEFILE or OPEN statement. It is possible that the file was not created as a direct access file. 3 R38 ERROR DURING WRITE FCS has detected an error condition while writing. 3 R39 ERROR DURING READ FCS has detected an error condition while reading. 3 R40 RECURSIVE I/O ATTEMPT An expression in the I/O list of an I/o statement has caused initiation of another I/O operation. This can happen if a function that performs I/o is referenced in an I/O list. 3 R41 NO FCS BUFFER ROOM There is not enough free memory left in the FCS buffer area to set up required I/O buffers. Rebuild the task with a larger Task Builder ACTFIL declaration or reduce the level of multibuffering. 3 R42 DEVICE HANDLER NOT RESIDENT A filename specification has included an illegal device name or a device for which no handler task(driver) is loaded when when an open operation is attempted. 3 R43 FILE NAME SPECIFICATION ERROR The filename string used in a CALL ASSIGN or OPEN statement is syntactically invalid, contains a switch specification, references an undefined device mnemonic, or is otherwise not acceptable to the operating system. 3 R44 RECORDSIZE TOO BIG FOR 'MAXBUF' A DEFINEFILE or OPEN statement has specified a record size which exceeds the size available in the record buffer. Rebuild the task using a larger Task Builder MAXBUF specification. 3 R45 UNSUPPORTED OPEN/CLOSE KEYWORD OR OPTION An OPEN statement keyword that requires a value has an illegal value. The following values are accepted. a. INITIALSIZE -32768 to 32767 b. EXTENDSIZE -32768 to 32767 c. BLOCKSIZE 0 to 32767 3 R46 INCONSISTANT OPEN/CLOSE STATEMENT SPECIFICATIONS The specifications in an OPEN and/or subsequent CLOSE statements have incorrectly specified one or more of the following: a. A 'NEW' or 'SCRATCH' file which is 'READONLY' b. 'APPEND' to a 'NEW', 'SCRATCH', or 'READONLY' file. c. 'SAVE' or 'PRINT' of a 'SCRATCH' file. d. 'DELETE' or 'PRINT' of a 'READONLY' file. 3 R60 INFINITE FORMAT LOOP The format associated with an I/O statement that includes an I/O list has no field descriptors to use in transferring those variables. 3 R61 FORMAT/VARIABLE-TYPE MISMATCH An attempt was made to input or output a real variable with an integer field descriptor (I, O, or L), or an integer or logical variable with a real field descriptor (D, E, F, or G). 3 R62 SYNTAX ERROR IN FORMAT A syntax error was encountered while the OTS was processing a format stored in an array. 3 R63 OUTPUT CONVERSION ERROR 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. The field width is filled with *'s. 3 R64 INPUT CONVERSION ERROR During a formatted input operation an illegal character was detected in an input filed or the input value overflowed the range representable in the input variable. The value of the variable is set to zero. 3 R65 FORMAT TOO BIG FOR 'FMTBUF' The OTS has run out of memory while scanning an array format that was generated at run time. The default internal format buffer length is 64 bytes. This may be increased by using the Task Builder FMTBUF option. 3 R66 RECORD TOO BIG FOR 'MAXBUF' An output operation has specified a record which exceeds the maximum length permitted for that type of operation. For direct access oper- ations, record length is specified ty the DEFINEFILE statement, the RECORDSIZE keyword of the OPEN statement, or by the record length attribute of an existing file. Fo formatted sequential operations, the maximum length is determined by the Task Builder MAXBUF option. There is no length limitation on unformatted sequential records. 3 R67 RECORD TWO SMALL FOR I/O LIST Read statement has attempted to input more data than existed in the record being read. For example, the I/O list might have too many elements. 3 R69 LIST DIRECTED I/O SYNTAX ERROR A syntax error was encountered while the OTS was processing an I/O list. 3 R70 INTEGER OVERFLOW During an arithmetic operation an integer's value has exceeded Integer*4 range. (Note: Overflow of Integer*2 range involving Integer*2 variables in generally not detected.) 3 R71 INTEGER ZERO DIVIDE During an integer mode arithmetic operation an attempt was made to divide by zero. 3 R72 FLOATING OVERFLOW During an arithmetic operation a real value has exceeded the largest representable real number. The result of the operation is set to zero. 3 R73 FLOATING ZERO DIVIDE During a real mode arithmetic operation an attempt was made to divide by zero. The result of the operation is set to zero. 3 R74 FLOATING UNDERFLOW During an arithmetic operation a real value has become less than the smallest representable real number, and has been replaced with a value of zero. 3 R75 FPP FLOATING TO INTEGER CONVERSION OVERFLOW The conversion of a floating point value to an integer has resulted in a value which overflows the range representable in an integer. The resulting value is unpredictable. 3 R80 WRONG NUMBER OF ARGUEMENTS One of the FORTRAN Library Functions or System Subroutines which checks for such an occurrence, has been called with an improper number of arguments. 3 R81 INVALID ARGUMENT One of the FORTRAN Library Functions or System Subroutines has detected an invalid argument value. 3 R82 UNDEFINED EXPONENTIATION An exponentiation has been attempted which is mathematically undefined; e.g., 0.**0. 3 R83 LOGARITHM OF ZERO OR NEGATIVE VALUE An attempt was made to take the logarithm of zero or a negative number. The result returned is zero. 3 R84 SQUARE ROOT OF NEGATIVE VALUE An argument required the evaluation of the square root of a negative value. The square root of the absolute value is computed and returned. 3 R85 INVALID ARGUMENT TO LIBRARY FUNCTION An invalid argument was used in a call to a FORTRAN library function. 3 R86 INVALID ERROR NUMBER The error number argument to one of the subroutines ERRSET, ERRSNS, or ERRTST is not a valid error number. 3 R90 COMPILER DETECTED ERROR An attempt is made to link and run an object file with errors, generated by the FORTRAN compiler, reported during compilation. 3 R91 COMPUTED GOTO OUT OF RANGE The integer variable or expression in a computed GO TO statement was less than 1 or greater than the number of statement label references in the list. Control is transferred to the next executable statement. 3 R100 DIRECTIVE: MISSING ARGUMENT(S) A call to a system directive subroutine was made in which one or more of the arguments required for directive execution was not given. 3 R101 DIRECTIVE: INVALID EVENT FLAG NUMBER A call to a system directive subroutine was made in which the argument used for event flag specification was not in the valid range(1 to 64). 3 R111 VIRTUAL ARRAY INITIALISATION FAILURE a)The total storage required for VIRTUAL arrays in the system exceeds the currently available memory on the system. b)Memory Management Directive support is attempted without EIS hardware. c)Memory Management Directive support is attempted on a system which does not support them. 3 R112 VIRTUAL ARRAY MAPPING ERROR An attempt is made to reference outside the bounds of the extended memory region allocated to VIRTUAL arrays. 3 CB Columns 1-5 of a continuation line are not blank. Columns 1-5 of a continuation line must be blank except for a possible 'D' in column 1. The columns are ignored (W). 3 CC Illegal continuation. Comments cannot be continued, and the first line in a program unit cannot be a continuation. If a line has a label field, it must have a statement field. The line is deleted (W). 3 CE Missing END statement. An END statement is supplied when End-of-File is encountered (W). 3 CH Hollerith string or quoted literal string is too long. Maximum length is 255 characters, and all strings must be terminated. The statement is ignored. 3 CI Non-FORTRAN character used. The line contains a character that is not in the FORTRAN character set, yet which is not in a Hollerith string or comment. The character is ignored (W). 3 CK Illegal statement label definition. Statement labels must be numeric. The label is ignored (W). 3 CL Line too long to print. No line may be longer than 80 characters (including tabs and spaces). Note: this diagnostic precedes the line in question. The line is truncated to 80 characters (W). 3 CM Multiply defined label. The label is ignored (W). 3 CP Statement contains unbalanced parentheses. The statement is ignored. 3 CS Syntax error. The statement is not of the standard FORTRAN form. The statement is ignored. 3 CU Statement could not be identified as a legal FORTRAN statement. The statement is ignored.