-1 [SY:PE.TXT] 13-Mar-84 Latest Update: 25-Apr-86 -1 -1 This file contains the source Verbose-Error-Text for all supported -1 error messages and all supported compilers. At present, the only -1 error messages supported are: -1 -1 1) F4 - Runtime Error Messages for FORTRAN-IV (V2.1 thru V2.6) -1 2) F77 - Runtime Error Messages for FORTRAN-77 (V5.0). -1 -1 The information in this file was made available by a generous grant -1 from Digital Equipment Corporation. It is free to all and may not be -1 sold. A reasonable facsimile of the text in this file can be found in -1 Digital Equipment Corporations: -1 -1 RT-11, RSTS/E FORTRAN-IV User's Guide (order # AA-5749-TC) and the -1 PDP-11 FORTRAN-77/RT-11 User's Guide (order # AA-BR70A-TC). -1 -1 It is intended that this file be used with the Program-Error number -1 decoder "PE", for RT-11 and TSX-Plus. PE translates compiler specific -1 error numbers (either runtime or compiletime) into the Error-Text -1 defined in this file and displays the text on the user's terminal (for -1 those of us too lazy to look them up). PE requires that the file -1 "PE.BIN" reside on SY:. -1 -1 Copyright 1984, 1985 by Digital Software Systems, Inc. -1 -1 Author: Daniel P. Graham -1 Digital Software Systems, Inc. -1 20 Bendix Place -1 Lindenhurst, NY 11757 -1 -1 ------- NO CHARACTERS SHOULD BE IN THIS FILE. ------- -1 -1 Format of an error message: -1 Columns Description -1 ======= =========== -1 1 - 3 Error Number (with leading Zeros), or one of the following: -1 " -1" for COMMENT lines; cols 4-80 are treated as comment. -1 " -2" for a COMPILER DEFINITION line. These lines specify -1 a Compiler-Switch-Name in columns 4 thru 9, and a -1 one-line compiler description in columns 10 thru 80. -1 " -3" for the DEFAULT Compiler-Switch-Name definition. -1 This line must specify one of the Compiler-Switch- -1 Names defined in a COMPILER DEFINITION line in -1 columns 4 trhu 9. Columns 10 thru 80 are treated as -1 a comment. Only one " -3" line may be in this file. -1 4 Blank always -1 5 Error-Type (severity level); one of:I, F, W, or C for Ignore, -1 Fatal, Warning, or Count respectively. -1 6 If Error-Type="C" then a colon (:) appears here, otherwise it -1 should be left blank. -1 7 If Error-Type="C" then the (the number of times -1 error can occur before its Fatal) should appear here; -1 otherwise it should be blank. -1 8 - 80 The Error Message text as it appears in the appropriate -1 compiler documentation (or a reasonable facsimile thereof). -1 -2F4 FORTRAN-IV Object-Time (runtime) Error Messages. -3F4 Decode FORTRAN-IV errors by default. 000 F NON-FORTRAN ERROR CALL 000 This message indicates an error condition (not internal to the 000 FORTRAN run-time system) that may have been caused by one of four 000 situations: 000 000 (RT-11 only) 000 1. A foreground job using SYSLIB completion routines was not 000 allocated enough space (using the FRUN /N option) for the 000 initial call to a completion routine. 000 000 Check Chapter 4 (SYSTEM SUBROUTINE LIBRARY) of the RT-11 000 Advanced Programmers Guide for the formula used to allocate 000 more space. 000 000 (RT-11 only) 000 2. There was not sufficient memory for the background job. 000 000 Make more memory available by unloading unnecessary handlers, 000 deleting unwanted files, compressing the device. 000 000 (RT-11 only) 000 3. Under the single-job monitor, a SYSLIB completion routine 000 interrupted another completion routine. 000 000 Use the FB Monitor to allow more than one active completion 000 routine. 000 000 4. An assembly language module linked with a FORTRAN program 000 issued a TRAP instruction with an error handler. 000 000 Check the program logic. 001 F INTEGER OVERFLOW 001 During an integer multiplication, division, or exponentiation 001 operation, the value of the result exceeded 32767 in magnitude. 001 001 Correct the program logic. 002 F INTEGER ZERO DIVIDE 002 During an integer mode arithmetic operation, an attempt was made 002 to divide by zero. 002 002 Correct the program logic. 003 F COMPILER GENERATED ERROR 003 An attempt was made to execute a FORTRAN statement in which the 003 compiler had previously detected errors. 003 003 Consult the program listing generated by the compiler (if one was 003 requested) and correct the program for the errors detected at 003 compile time. 004 W COMPUTED GOTO OUT OF RANGE 004 The value of the integer variable or expression in a computed GOTO 004 statement was less than one or greater than the number of statement 004 label references in the list. 004 004 Control is passed to the next executable statement. Examine the 004 source program and correct the program logic. 005 C:3 INPUT CONVERSION ERROR 005 During a formatted input operation, an illegal character was 005 detected in an input field. 005 005 A value of zero is returned. Examine the input data and correct 005 the invalid record. 006 I OUTPUT CONVERSION ERROR 006 During a formatted output operation, the value of a particular 006 number could not be output in the specified field length without 006 loss of significant digits. 006 006 The field is filled with asterisks ('*'). Correct the FORMAT 006 statement to allow a greater field length. 010 C:3 FLOATING OVERFLOW 010 During an arithmetic operation, the absolute value of a floating- 010 point expression exceeded the largest representable real number. 010 010 A value of zero is returned. Correct the program logic. 011 I FLOATING UNDERFLOW 011 During an arithmetic operation, the absolute value of a floating-point 011 expression became less than the smallest representable real number. 011 011 The real number is replaced with a value of zero. Correct the 011 program logic. 012 F FLOATING ZERO DIVIDE 012 During a REAL mode arithmetic operation an attempt was made to 012 divide by zero. 012 012 The result of the operation is set to zero. Correct the program logic. 013 C:3 SQRT OF NEGATIVE NUMBER 013 An attempt was made to take the square root of a negative number. 013 013 The result is replaced by zero. Correct the program logic. 014 F UNDEFINED EXPONENTIATION OPERATION 014 An attempt was made to perform an illegal exponentiation operation. 014 (For example, -3.**.5 is illegal because the result would be an 014 imaginary number.) 014 014 The result of the operation is set to zero. Correct the program logic. 015 F LOG OF ZERO OR NEGATIVE NUMBER 015 An attempt was made to take the logarithm of a negative number or zero. 015 015 The result of the operation is set to zero. Correct the program logic. 016 F WRONG NUMBER OF ARGUMENTS 016 One of the FORTRAN Library functions, or one of the system 016 subroutines that checks for such an occurrence, was called with 016 an improper number of arguments. Check the format of the particular 016 library function or system subroutine call, and correct the call. 020 F INVALID LOGICAL UNIT NUMBER 020 An illegal logical unit number was specified in an I/O statement. 020 020 A logical unit number must be an integer within the range 1 to 99. 020 Correct the statement in error. 021 F OUT OF AVAILABLE LOGICAL UNITS 021 An attempt was made to have too many logical units simultaneously 021 open for I/O. 021 021 The maximum number of active logical units is six by default. 021 To increase the maximum, recompile the main program using the 021 /UNITS (/N) option to specify a larger number of available channels. 022 F INPUT RECORD TOO LONG 022 During an input operation, a record was encountered that was 022 longer than the maximum record length. 022 022 The default maximum record length is 136 (decimal) bytes. To 022 increase the maximum, recompile the mail program using the 022 /RECORDS (/R) option to specify a larger run-time record buffer 022 (the legal range is 4 to 4095). 023 F HARDWARE I/O ERROR 023 A hardware error was detected during an I/O operation. 023 023 Check the volume for an off-line or write-locked condition, and 023 retry the operation. Try another unit or drive if possible, or 023 use another device. 024 F ATTEMPT TO READ/WRITE PAST END OF FILE 024 During a sequential READ operation, an attempt was made to read 024 beyond the last record of the file. During a random access READ, 024 this message indicates that an attempt was made to reference a 024 record number that was not within the bounds of the file. 024 024 Use the "END=" parameter to detect this condition, or correct the 024 program logic so that no request is made for a record outside the 024 bounds of the file. 024 024 During a WRITE operation, this message indicates that the space 024 available for the file is insufficient. 024 024 (RT-11 action) 024 Try to make more file space available by deleting unnecessary 024 files and compressing the device, or by using another device. 024 024 (RSTS/E action) 024 This condition is equivalent to the "NO ROOM FOR USER ON DEVICE 024 system error. Make more space available by deleting files from 024 the current account, or use another device. 025 F ATTEMPT TO READ AFTER WRITE 025 An attempt was made to read after writing on a sequential file 025 located on a file-structured divide. 025 025 A write operation must be followed by a REWIND or BACKSPACE 025 before a read operation can be performed. Correct the program logic. 026 F RECURSIVE I/O NOT ALLOWED 026 An expression in the I/O list of WRITE statement caused initiation 026 of another READ or WRITE operation. (This can happen if a FUNCTION 026 that performs I/O is referenced within an expression in an I/O list.) 026 026 Correct the program logic. 027 F ATTEMPT TO USE DEVICE NOT IN SYSTEM 027 An attempt was made to access a device that was not legal for the 027 system in use. 027 027 Use the system ASSIGN command to create the required logical 027 device name, or change the statement in error. 028 F OPEN FAILED FOR FILE 028 The file specified was not found, there was no room on the device, 028 or there was an attempt to create a file which already exists as a 028 protected file. 028 028 Verify that the file exists as specified. Delete unnecessary files 028 from the device, or use another device. 029 F NO ROOM FOR DEVICE HANDLER (RT-11 only) 029 There was not enough free memory left to accommodate a specific 029 device handler. 029 029 Move the file to the system device or to a device whose handler is 029 resident. Make more memory available by unloading unnecessary 029 handlers, unloading the foreground job, using the single-job 029 Monitor, or SET USR SWAP, if possible. 030 F NO ROOM FOR BUFFERS 030 There was not enough free memory left to set up required I/O buffers. 030 030 (RT-11 only) 030 Reduce the number of logical units that are open simultaneously at 030 the time of the error. If using double buffering or if another 030 file is currently open, use single buffering. Make more memory 030 available by unloading unnecessary handlers, unloading the foreground 030 job, using the single-job Monitor, or SET USR SWAP, if possible. 030 030 (RSTS/E only) 030 Increase the space available for buffering by specifying the 030 appropriate value for the /K switch to LINK, or reduce the number 030 of logical units that are open simultaneously at the time of the error. 031 F NO AVAILABLE I/O CHANNEL 031 More than the maximum number of channels available to the FORTRAN 031 IV run-time system (15 for RT-11; 14 for RSTS/E, exclusive of the 031 terminal) were requested to be simultaneously opened for I/O. 031 031 Close any logical units previously opened that need not be open 031 at this time. 032 F FMTD-UNFMTD-RANDOM I/O TO SAME FILE 032 An attempt was made to perform any combination of formatted, 032 unformatted, or random access I/O to the same file. 032 032 Correct the program logic. 033 F ATTEMPT TO READ PAST END OR RECORD 033 An attempt was made to read a larger record than actually existed 033 in a file. 033 033 Check the construction of the data file; correct the program logic. 034 F UNFMTD I/O TO TT OR LP 034 An attempt was made to perform an unformateed write operation on 034 the terminal or line printer. 034 034 Assign the logical unit in question to the appropriate device, using 034 the ASSIGN system command, the OPEN statement, the ASSIGN or OPEN 034 FORTRAN library routine, or (RT-11 only) the IASIGN SYSLIB routine. 035 F ATTEMPT TO OUTPUT TO READ ONLY FILE 035 An attempt was made to write on a file designated as read only. 035 035 Check the OPEN statement, the ASSIGN or OPEN (RSTS/E only) system 035 routine, or IASIGN SYSLIB function (RT-11 only) to ensure that the 035 correct arguments were used. Check for a possible programming error. 036 F BAD FILE SPECIFICATION STRING 036 The Hollerith or literal string specifying the device/file name 036 OPEN statement, in the CALL ASSIGN or CALL OPEN system subroutine, 036 could not be interpreted. 036 036 Check the format of the OPEN statement, CALL ASSIGN, or CALL OPEN 036 statement. 037 F RANDOM ACCESS READ/WRITE BEFORE DEFINE FILE 037 A random access read or write operation was attempted before a 037 DEFINE FILE was performed. 037 037 Correct the program so that the DEFINE FILE operation is executed 037 before any random-access read or write operation. 038 F RANDOM I/O NOT ALLOWED ON TT OR LP 038 Random access I/O was illegally attempted on the terminal or line 038 printer. 038 038 Assign the logical unit in question to the appropriate device, using 038 the ASSIGN keyboard monitor command, OPEN statement, the ASSIGN or 038 OPEN FORTRAN library routine, or (RT-11 only) the IASIGN SYSLIB 038 routine. 039 F RECORD LARGER THAN RECORD SIZE IN DEFINE FILE 039 A record was encountered that was larger than that specified in the 039 DEFINE FILE statement for a random access file. 039 039 Shorten the I/O list or redefine the file specifying larger records. 040 F REQUEST FOR A BLOCK LARGER THAN 65535 040 An attempt was made to reference an absolute disk block address 040 greater than 65535. 040 040 Correct the program logic. 041 F DEFINE FILE ATTEMPTED ON AN OPEN UNIT 041 A file was open on a unit and another DEFINE FILE was attempted on 041 that unit. 041 041 Close the open file using the CLOSE statement before attempting 041 another DEFINE FILE. 042 F MEMORY OVERFLOW COMPILING OBJECT TIME FORMAT 042 The OTS ran out of free memory while scanning an array format 042 generated at run time. 042 042 (RT-11 only) 042 Use a FORMAT statement specification at compile time rather than 042 object-time formatting, or make more memory available by unloading 042 unnecessary handlers, unloading the foreground job if possible, 042 using the single-job Monitor, or SET USR SWAP, if possible. 042 042 (RSTS/E only) 042 Use a FORMAT statement specification at compile time rather than 042 object-time formatting, or allocate more space by using the /K 042 switch to LINK. 043 F SYNTAX ERROR IN OBJECT TIME FORMAT 043 A syntax error was encountered while the OTS was scanning an 043 array format generated at run time. 043 043 Correct the programming error. 044 F 2ND RECORD REQUEST IN ENCODE/DECODE 044 An attempt was made to use ENCODE and DECODE on more than one record. 044 044 Correct the FORMAT statement associated with the ENCODE or DECODE so 044 that it specifies only one record. 045 F INCOMPATIBLE VARIABLE AND FORMAT TYPES 045 An attempt was made to output a real variable with an integer field 045 descriptor or an integer variable with a real field descriptor. 045 045 Correct the FORMAT statement associated with the READ or WRITE, 045 ENCODE or DECODE. 046 F INFINITE FORMAT LOOP 046 The format associated with an I/O statement, which includes an I/O 046 list, had no field descriptors to use in transferring those variables. 046 046 Correct the FORMAT statement in error. 047 F ATTEMPT TO STORE OUTSIDE PARTITION (RT-11 only) 047 In an attempt to store data into a subscripted variable, the address 047 calculated for the array element in question did not lie within the 047 section of memory allocated to the job. The subscript in question 047 was out of bounds. (This message is issued only when bounds checking 047 modules have been installed in FORLIB and threaded code is selected 047 at compile time.) 047 047 Correct the program logic. 048 F UNIT ALREADY OPEN 048 An attempt was made to perform an illegal operation on an open file. 049 F ENDFILE ON RANDOM FILE 049 An ENDFILE statement contains a unit number of a file that is open 049 as a random access file. 050 F KEYWORD VALUE ERROR IN OPEN STATEMENT 050 A numeric value specified for a keyword in the OPEN statement is 050 not within the accepted range. 050 050 Check the expression in the OPEN statement, and modify to yield a 050 valid value. 051 F INCONSISTENT OPEN/CLOSE STATEMENT SPECIFICATIONS 051 The specifications in an OPEN or subsequent CLOSE statement have 051 indicated one or more of the following: 051 051 * A 'NEW' or 'SCRATCH' file that is 'READONLY'. 051 051 * 'APPEND' to a 'NEW', 'SCRATCH', or 'READONLY' file. 051 051 * 'SAVE' or 'PRINT' of a 'SCRATCH' file. 051 051 * 'DELETE' or 'PRINT' of a 'READONLY' file. 051 051 Correct the OPEN or CLOSE statement to remove the conflict. 052 W ATTEMPT TO DELETE A PROTECTED FILE (RT-11 only) 052 052 An attempt was made through a DISP= 'DELETE' option in an OPEN 052 or CLOSE statement to delete a protected file. Either unprotect 052 the file or correct the conflict in the OPEN and/or CLOSE statement. 053 W LIST DIRECTED I/O SYNTAX ERROR 053 The repeat count of the input record has the wrong type or value. 053 The repeat count must be a positive non-zero integer. 059 W USR NOT LOCKED (RT-11 only) 059 This message is issued when the FORTRAN program is started. If the 059 program was running in the foreground, the /NOSWAP option was used 059 during compilation, and the USR was swapping (for example, a SET 059 USR NOSWAP command has not been done). 059 059 Reexamine the intent of the /NOSWAP option at compile time and 059 either compile without /NOSWAP or issue a SET USR NOSWAP command. 060 F STACK OVERFLOWED 060 The hardware stack overflowed. More stack space may be required 060 for subprogram calls and opening of file. Proper traceback is 060 impaired. This message occurs in the background only. Allocate 060 additional space by using the /BOTTOM (/B) option at link time. 060 Check for a programming error. 061 F ILLEGAL MEMORY REFERENCE 061 Some type of bus error occurred, most probably an illegal memory 061 address reference. 061 061 If an assembly language routine was called, check for a coding 061 error in the routine. Otherwise, insure that the correct FORTRAN 061 library was called. 062 F FORTRAN START FAIL 062 The program was loaded into memory but there was not enough free 062 memory remaining for the OTS to initialize work space and buffers. 062 062 (RT-11 only) 062 If running a background job, make more memory available by unloading 062 unnecessary handlers, using the single-job Monitor. If running a 062 foreground job, specify a larger value using the FRUN /N option. 062 Refer to Chapter 4 (SYSTEM SUBROUTINE LIBRARY) of the RT-11 Advanced 062 Programmers Guide for the correct formula. 062 062 (RSTS/E only) 062 Allocate more space by using the /K switch to LINK. 063 F ILLEGAL INSTRUCTION 063 The program attempted to execute an illegal instruction (for example, 063 floating-point arithmetic instruction on a machine with no floating- 063 point hardware). 063 063 If an assembly language routine was called, check for a coding 063 error in the routine. Otherwise, ensure that the correct FORTRAN 063 library was called. 064 F VIRTUAL ARRAY INITIALIZATION FAILURE 064 * The total storage requirements for VIRTUAL arrarys in the program 064 exceeds the currently available memory on the system. 064 064 * Another job is currently using VIRTUAL support under the FB or 064 SJ monitor. 064 064 * PLAS VIRTUAL array support is attempted under the FB or SJ monitor. 064 064 * Any non-PLAS VIRTUAL array support is attempted under XM monitor. 064 064 * PLAS support is attempted without EIS hardware. 064 064 * VIRTUAL array support is attempted without OTS Library VIRTUAL 064 support. 064 064 If another job is currently executing (under XM monitor with PLAS 064 VIRTUAL support), make sure that the total VIRTUAL storage demands 064 for both programs are satisfied by the available memory on the machine. 064 064 Reduce VIRTUAL storage requirements by decreasing the size of VIRTUAL 064 arrays declared in the program. 065 F VIRTUAL ARRAY MAPPING ERROR 065 An attempt has been made to reference outside the bounds of the 065 extended memory region allocated to VIRTUAL arrays in this program, 065 probably caused by a subscript out of bounds. 065 065 Verify that the subscripts of the VIRTUAL arrays referenced in the 065 statement indicated are within the declared bounds. 066 F UNSUPPORTED OPEN/CLOSE KEYWORD OR OPTION 066 A keyword or keyword value in the OPEN or CLOSE statement indicated 066 is invalid under this particular operating system. 066 066 Refer to Section 3.1.1 for the system-dependent restrictions. 067 W UNSUPPORTED OPEN/CLOSE KEYWORD OR OPTION 067 A keyword or keyword value in the OPEN or CLOSE statement indicated 067 is not meaningful in the current operating system environment. 067 067 The pressure of the keyword or option is ignored. 068 F DIRECT ACCESS RECORD SIZE ERROR 068 The size of a direct access record exceeds 32767 double words. 068 068 Correct the program logic. 069 F CANNOT SEND TO QUEMAN (RSTS/E only). 069 An error occurred when closing a file with attribute DISPOSE='PRINT'. -1 -1 -1 **** End of FORTRAN-IV Object-Time (runtime) Error Messages. **** -1 --------------------------------------------------------- -1 **** Start of FORTRAN-77 Object-Time (runtime) Error Messages. **** -1 -2F77 FORTRAN-77 Object-Time (runtime) Error Messages. -1 -1 001 F INVALID ERROR CALL 001 A TRAP instruction has been executed whose low byte is within the 001 range used by the OTS for error reporting but for which no error 001 condition is defined. 002 F NOT ENOUGH MEMORY FOR OTS TABLES 002 Not enough dynamic memory remains for the OTS to establish its 002 buffers. Unload handlers, SYSTEM or FOREGROUND jobs,or use 002 overlay techniques to provice more space for the OTS. 003 F ODD ADDRESS TRAP 003 The program has made a word reference to an odd byte address. 004 F SEGMENT FAULT 004 The program has referenced a nonexistent address, most likely due 004 to a subscript value out of range on an array reference. 005 F T-BIT OR BPT TRAP 005 A trap has occurred as a result of the trace bit being set in the 005 processor status word or of the execution of BPT instruction. 006 F IOT TRAP 006 A trap has occurred as a result of the execution of an IOT instruction. 007 F RESERVED INSTRUCTION TRAP 007 The program has attempted to execute an illegal instruction. 008 F NON-FORTRAN ERROR CALL 008 This message indicates an error condition (not internal to the 008 Fortran-77 run-time system) that may have been caused by one of 008 four situations: 008 008 1. A foreground job using SYSLIB completion routines was not 008 allocated enough spaced (using the FRUN /U option) for the 008 initial call to a completion routine. 008 Check the RT-11 Programmer's Reference Manual for the 008 formula used to allocate more space. 008 2. There was not sufficient memory for the background job. 008 Make more memory available by unloading unnecessary 008 handlers, deleting unwanted files, compressing the device. 008 3. Under the single-job monitor, a SYSLIB completion routine 008 interrupted another completion routine. 008 Use the FB Monitor to allow more than one active completion 008 routine. 008 4. An assembly language module linked with a FORTRAN program 008 issued a TRAP instruction with an error code that was not 008 recognized by the Fortran-77 error handler. 008 Check the program logic. 009 F TRAP INSTRUCTION TRAP 009 A TRAP instruction has been executed whose low byte is outside 009 the range used for OTS error messages. 010 F PDP-11/40 FIS TRAP 011 F FPP HARDWARE FAULT 011 The FPP Floating Exception Code (FEC) register contained the 011 value 0 following an FPP interrupt. This is probably a hardware 011 malfunction. 012 F FPP ILLEGAL OPCODE TRAP 012 The FPP has detected an illegal floating-point instruction. 013 F FPP UNDEFINED VARIABLE TRAP 013 The FPP loaded an illegal value (-0.0). This trap should not 013 occur since the OTS initialization routine does not enable this 013 trap condition. A negative zero value should never be produced 013 by any FORTRAN operation. 014 F FPP MAINTENANCE TRAP 014 The FPP Floating Exception Code register contained the value 14 014 (octal) following a FPP interrupt. This is probably a hardware 014 malfunction. 020 F INVALID LOGICAL UNIT NUMBER 020 A logical unit number was used that is greater than 99, less 020 than 0, or outside the range specified by the compiler 020 UNITS option (see Section 1.2.6.2 of the Fortran-77 User's Guide). 021 F NO AVAILABLE CHANNELS 021 All available channels are already in use. 022 F INPUT RECORD TOO LONG 022 A record too large to fit into the user record buffer has been read. 022 Recompile with the /R switch and specify a larger record length. 023 F BACKSPACE ERROR 023 One of the following errors has occurred: 023 023 * BACKSPACE was attempted on a relative or indexed file or a file 023 opened for append access (see Section 2.3 of the Fortran-77 User's 023 Guide). 023 023 * an error condition while rewinding the file has been detected. 023 023 * an error condition while reading forward to the desired record 023 has been detected. 024 F END-OF-FILE DURING READ 024 Either an end-file record produced by the ENDFILE statement or an 024 end-of-file condition has been encountered during a READ 024 statement, and no END= transfer specification was provided. 025 F RECORD NUMBER OUTSIDE RANGE 025 A direct access I/O statement has specified a record number 025 outside the range specified in a DEFINEFILE statement or in the 025 MAXREC keyword of the OPEN statement. 026 F ACCESS MODE NOT SPECIFIED 026 The access mode of an I/O statement was inconsistent with the access 026 specified by a DEFINEFILE or OPEN statement for the logical unit. 027 F TOO MANY RECORDS IN I/O STATEMENT 027 An attempt was made to process more than a single record in a 027 REWRITE statement or in an ENCODE or DECODE statement. 028 F CLOSE ERROR 028 An error condition has been detected during the close, delete, or 028 print operation of an attempt to close a file. 029 F NO SUCH FILE 029 A file with the specified name could not be found during an open 029 operation. 030 F OPEN FAILURE 030 An error condition during an open operation was detected. (This 030 message is used when the error condition is not one of the more 030 common condition for which specific error messages are provided.) 031 F MIXED FILE ACCESS MODES 031 An attempt was made to use both formatted and unformatted operations, 031 or both sequential and direct access operations, on the same unit. 032 F DUPLICATE FILE SPECIFICATIONS 032 Multiple attempts to specify file attributes have been attempted, 032 without an intervening close operation, by one of the following: 032 032 * DEFINEFILE followed by DEFINEFILE. 032 032 * DEFINEFILE, CALL ASSIGN, or CALL FDBSET followed by an OPEN 032 statement. 033 F ENDFILE ERROR 033 An end-file record may not be written to a direct access file, a 033 relative file, an indexed file, or an unformatted file that does 033 not contain segmented records. 034 F UNIT ALREADY OPEN 034 An OPEN statement or DEFINEFILE statement was attempted that 034 specified a logical unit already opened for input/output. 035 F RANDOM I/O TO NON-FILE STRUCTURED DEVICE. 035 Random access I/O was illegally attempted to a device incapable 035 of this activity. 035 035 Assign the logical unit inquestion an appropriate device using 035 the ASSIGN keyboard monitor commanc, OPEN statement, the ASSIGN 035 or OPEN Fortran-77 library routine, or the IASIGN SYSLIB routine. 036 F ATTEMPT TO ACCESS NON-EXISTENT RECORD 036 One of the following conditions has occurred: 036 036 * A nonexistent record was specified in a direct access READ or FIND 036 statement. The nonexistent record might have been deleted or was 036 never written. 036 036 * A record located beyond the end-of-file was specified in a direct 036 access READ or FIND statement. 037 F INCONSISTENT RECORD LENGTH 037 An invalid or inconsistent record length specification occurred for 037 one of the following reasons: 037 037 * The record length specified is too large to fit in the user 037 record buffer. Rebuild the task with a larger TASK Builder 037 MAXBUF value. 037 037 * The record length specified does not match the record length 037 attribute of an existing fixed-length file. 037 037 * The record length specification was omitted when an attempt was 037 made to create a relative file or a file with fixed-length records. 038 F ERROR DURING WRITE 038 An error condition has been detected during execution of a WRITE 038 statement. 039 F ERROR DURING READ 039 The file system has detected an error condition during execution 039 of a READ statement. 040 F RECURSIVE I/O OPERATION 040 An expression in the I/O list of an I/O statement has caused initiation 040 of another I/O operation. This can happen if a function that performs 040 I/O is referenced in an expression in an I/O list. 041 F NO BUFFER ROOM 041 There is not enough free memory left in the OTS buffer area to 041 set up required I/O control blocks and buffers. 042 F NO SUCH DEVICE 042 A file name specification has included an invalide device name or a 042 device for which no handler is available when an open operation is 042 is attempted. 043 F FILE NAME SPECIFICATION ERROR 043 The file name string used in a CALL ASSIGN or OPEN statement contains 043 a qualifier specification, is syntactically invalid, references an 043 undefined device, or is otherwise unacceptable to the operating system. 044 F INCONSISTENT RECORD TYPE 044 The RECORDTYPE specification does not match the record type of an 044 existing file. 045 F KEYWORD VALUE ERROR IN OPEN STATEMENT 045 An OPEN statement keyword that requires a value has an illegal value. 045 The following values are accepted: 045 045 BLOCKSIZE: 0 to 32767 045 EXTENDSIZE: -32768 to 32767 045 INITIALSIZE: -32768 to 32767 045 MAXREC: 0 to 2**31-1 045 BUFFERCOUNT: 0 to 127 045 RECL: up to 32766 for sequential organization 045 16360 for relative or indexed organization 045 9999 for magnetic tape 046 F INCONSISTENT OPEN/CLOSE PARAMETERS 046 The specificatione in an OPEN and/or subsequent CLOSE statement 046 have incorrectly specified one or more of the following: 046 046 * A 'NEW' or 'SCRATCH' file which is 'READONLY' 046 046 * 'APPEND' to a 'NEW', 'SCRATCH' or 'READONLY' file 046 046 * 'SAVE' or 'PRINT' on a 'SCRATCH' file 046 046 * 'DELETE or 'PRINT on a 'READONLY' file. 047 F WRITE TO A READ-ONLY FILE 047 A write operation has been attempted to a file which was declared 047 to be READONLY. 048 F UNSUPPORTED I/O OPERATION 048 An I/O operation (such as direct or keyed access) has been specified 048 which is not supported by the OTS being used. 049 F REWIND ERROR 050 F HARD I/O ERROR 050 A hardware error was detected during an I/O operation. 050 050 Check the volume for an off-line or write-locked condition, and retry 050 the operation. Try another unit or drive if possible, or use another 050 device. 051 F LIST-DIRECTED I/O SYNTAX ERROR 051 The repeat count of the input record has the wrong type or value. 051 The repeat count must be a positive non-zero integer. 052 F INFINITE FORMAT LOOP 052 The format associated with an I/O statement, which includes an I/O 052 list, had no field descriptors to use in transferring those variables. 052 052 Correct the FORMAT statement in error. 053 F FORMAT/VARIABLE-TYPE MISMATCH 053 An attempt was made to input or output a real variable with an integer 053 field descriptor (I or L), or an integer or logical variable with a 053 real field descriptor (D, E, F, or G). The data type of the value is 053 ignored, and the value is processed as if it were of the correct data 053 type. 054 F SYNTAX ERROR IN FORMAT 054 A syntax error was encountered while the OTS was processing a 054 format stored in an array. 055 W OUTPUT CONVERSION ERROR 055 During a formatted output operation, the value of a particular number 055 could not be output in the specified field length without loss of 055 signification digits. The field is filled with asterisks (*). 056 F INPUT CONVERSION ERROR 056 During a formatted input operation, an invalid character was detected 056 in an input field, or the input value overflowed the range representable 056 in the input variable. The value of the variable is set to zero. 057 F FORMAT TOO BIG FOR 'FMTBUF' 057 The OTS has run out of memory while scanning an array format that 057 was generated at run time. The default internal format buffer 057 length is 64 bytes. 058 F OUTPUT STATEMENT OVERFLOWS RECORD 058 An output operation has specified a record that exceeds the 058 maximum record size specified. The maximum record length is 058 specified by the DEFINEFILE statement, by the RECL keyword of the 058 OPEN statement, or by the record length attribute of an existing 058 file. See statement F.1.7 in the Fortran-77 User's Guide. 059 F RECORD TOO SMALL FOR I/O LIST 059 A READ statement has attempted to input more data than existed in 059 the record being read. For example, the I/O list might have too 059 many elements. 060 F VARIABLE FORMAT EXPRESSION VALUE ERROR 060 The value of a variable format expression is not within the range 060 acceptable for its intended use: for example, a field width that 060 is less than or equal to zero. A value of 1 is used. 070 F INTEGER OVERFLOW 070 During an arithmetic operation, an integer's value has exceeded 070 INTEGER*4 range. (Note: Overflow of INTEGER*2 range involving 070 INTEGER*2 variables is not detected.) 071 F INTEGER ZERO DIVIDE 071 During an integer mode arithmetic operation, an attempt was made 071 to divide by zero. (Note: A zero-divide operation involving 071 INTEGER*2 variables is rarely detected.) 072 F FLOATING OVERFLOW 072 During an arithmetic operation, a real value has exceeded the largest 072 representable real number. The result of the operation is set to zero. 073 F FLOATING ZERO DIVIDE 073 During a real mode arithmetic operation, an attempt was made to 073 divide by zero. The result of theoperation is set to zero. 074 F FLOATING UNDERFLOW 074 During an arithmetic operation, a real value has become less than 074 the smallest representable real number and has been replaced with 074 a value of zero. 075 F FPP FLOATING TO INTEGER CONVERSION OVERFLOW 075 The conversion of a floating-point value to an integer has 075 resulted in a value that overflows the range representable in an 075 integer. The result of the operation is zero. 080 F WRONG NUMBER OF ARGUMENTS 080 One of the FORTRAN library functions of system subroutines has 080 been called with an improper number of arguments (see Table 4-1 080 or Appendix-D of the Fortran-77 User's Guide). 081 F INVALID ARGUMENT 081 One of the FORTRAN library functions or system subroutines has 081 detected an invalid argument value. (see Table 4-1 or Appendix-D 081 of the Fortran-77 User's Guide). 082 F UNDEFINED EXPONENTIATION 082 An exponentiation (for example, 0.**0.) has been attempted that 082 is mathematically undefined. The result returned to zero. 083 F LOGARITHM OF ZERO OR NEGATIVE VALUE 083 An attempt was made to take the logarithm of zero or a negative 083 number. The result returned is zero. 084 F SQUARE ROOT OF NEGATIVE VALUE 084 An argument required the evaluation of the square root of a negative 084 value. The square root of the absolute value is computed and returned. 085 F INVALID ERROR NUMBER 085 091 F COMPUTED GOTO OUT OF RANGE 091 The integer variable or expression in a computed GO TO statement was 091 less than 1 or greater than the number of statement label references 091 in the list. Control is transferred to the next executable statement. 092 F ASSIGNED LABEL NOT IN LIST 092 An assigned GOTO has been executed in which the label assigned to 092 the variable is not one of the labels in the list. Control is 092 transferred to the next executable statement. 093 F ADJUSTABLE ARRAY DIMENSION ERROR 093 Upon entry to a subprogram, the evaluation of dimesioning information 093 has detected an array in which one of the following occurs: 093 093 * An upper dimension bound is less than a lower dimension bound. 093 093 * The dimensions imply an array which exceeds the addressable memory. 094 W ARRAY REFERENCE OUTSIDE ARRAY 094 An array reference has been detected that is outside the array as 094 described by the array declarator. Execution continues. (This 094 checking is performed only for program units compiled with the /I 094 switch in effect.) 095 F INCOMPATIBLE FORTRAN OBJECT MODULE IN JOB 095 An object module produced by another PDP-11 FORTRAN compiler has 095 been linked with a Fortran-77 job (see Section 1.2.5.1 of the 095 Fortran-77 User's Guide). 096 F MISSING FORMAT CONVERSION ROUTINE 096 A format conversion code has been used for which the corresponding 096 conversion routine is not loaded (see Section 3.4 of in the 096 Fortran-77 User's Guide). 101 F VIRTUAL ARRAY INITIALIZATION FAILURE 101 The mapped array area could not be initialized. The operating system 101 does not support the memory management directives required, or no 101 memory management registers are available for use. 102 W VIRTUAL ARRAY MAPPING ERROR 102 A virtual-array address was invalid, probable due to a subscript 102 out of bounds. Execution continues. -1 [End-of-File PE.TXT]