With the exception of the System Library Mainline Programs, this appendix lists all Monitor System WAITS and messages. SYSUP, the DCOM update subroutine, is also available in the System Library. The errors for the user callable version of SYSUP are listed in the System Library Utility Subroutines section of the manual. All messages for stand-alone utilities are included in the writeups of the individual programs.
System Loader and FORTRAN I/O errors cause the system to WAIT at $PRET. At the WAIT, bits 2 and 3 of the OPERATION REGISTER are on. FORTRAN I/O errors can be identified by the Fxxx code in the accumulator. A $PRET WAIT also occurs when a system I/O device is required but is not ready (see Table 18).
All error tables in this appendix are listed alphabetically by prefix letter. Unless otherwise noted, the operational and error messages are printed on the principal printer. All Monitor system control records are printed on the principal printer.
The error tables in order of appearance are as follows.
|Table Number||Error Code Prefix||Program Name|
|10||D||Disk Utility Program (DUP)|
|13||M||Monitor Control Record Analyzer (MCRA)|
|14||M||Supervisor Control Record Program Supervisor|
|16||R||Core Load Builder|
At the completion of an assembly, the following messages are printed on the principal printer.
XXX OVERFLOW SECTORS SPECIFIED XXX OVERFLOW SECTORS REQUIRED XXX SYMBOLS DEFINED XX ERROR(S) FLAGGED IN ABOVE ASSEMBLY
If LIST DECK or LIST DECK E is specified, the error detection codes shown in Table 7 are punched in columns 18 and 19. For the first error detected in each statement the Assembler stores and then punches the cede in column 18; the cede for a second error is stored, overlaid by any subsequent errors, and punched in column 19. Thus, if more than two errors are detected in the same statement, only the first and last are indicated. These error detection codes will appear on the printout if the deck is listed.
Attempt made to specify displacement field, directly or indirectly, outside range of -128 to +127,
|Displacement set to zero|
|C||Condition Code Error
Character other than +, -, Z, E, C, or 0 detected in first operand of short branch or second operand of long BSC, BOSC, or BSI statement.
|Displacement set to zero|
|F||Format Code Error
Character other than L, I, X, or blank detected in col. 32, or L or I format specified for instruction valid only in short form.
|Instruction processed as if format were specified, unless that instruction is valid only in short form, in which case it is processed as if the X format were specified|
Invalid symbol detected in label field.
|M||Multiply Defined Label Error
Duplicate symbol encountered in label field.
|First occurrence of symbol in label field defines its value; subsequent occurrences of symbol in label field cause a multiply defined indicator to be inserted in symbol table entry (Bit 0 of first word).|
|O||Op Code Error|
|Unrecognized op code||Statement ignored and address counter incremented by 2.|
|ISS, ILS, ENT, LIBR, SPR, EPR, or ABS incorrectly placed.||Statement ignored|
|Expression does not have valid relocation.||Expression set to zero|
|Non-absolute displacement specified.||Displacement set to zero|
|Absolute origin specified in relocatable program.||Origin ignored|
|Non-absolute operand specified in BSS or BES.||Operand assumed to be zero|
|Non-relocatable operand in END statement of relocatable mainline program.||Cord columns 9-12 left blank; entry assumed to be relative zero|
|ENT operand non-relocatable.||Statement ignored|
|Invalid expression (e.g., invalid symbol, 'adjacent operators, illegal constant)||Expression set to zero|
|Illegal character in record.||If illegal character appears in expression, label, op code, format, or tag field, additional errors may be caused.|
|Main program entry point not specified in END operand.||Card columns 9-12 left blank; entry assumed to be relative zero|
|Incorrect syntax in EBC statement (e.g., no delimiter in card column 35, zero character count).||Card columns 9-12 not punched; address counter incremented by 17.|
|Invalid label in ENT or ISS operand,||Statement ignored|
|Card column 33 contains character other than blank, 0, 1, 2, or 3 in instruction statement.||Tag of zero assumed|
|Undefined symbol in expression||Expression set to absolute zero|
At the end of the assembly, a message is printed indicating the number of assembly errors detected in the source program (see above). Since no more than two errors are flagged per statement, the error count may exceed the actual number of flags.
Assembler error messages are listed in Table 8.
Near the end of the compilation, core usage information and the features supported (control records used) are printed out as follows:
FEATURES SUPPORTED EXTENDED PRECISION ONE WORD INTEGERS TRANSFER TRACE ARITHMETIC TRACE IOCS CORE REQUIREMENTS FOR XXXXX COMMON YYYYY VARIABLES YYYYY PROGRAM YYYYY
where XXXXX is the name of the program designated in the *NAME control record or in the SUBROUTINE or FUNCTION statement, and YYYYY is the number of words allocated for the specified parts of the program.
The following message is printed for a normal end of compilation (with or without errors):
END OF COMPILATION
|Error Number and Message||Cause of Error||Corrective Action|
|A01 MINIMUM W. S. NOT AVAILABLE...
|Available Working Storage is less than the number of overflow sectors specified plus one sector.||Reduce the number of overflow sectors specified (number specified is zero if no OVERFLOW SECTORS control record is used) or,
If more than one drive is available on the system, use the // JOB record to specify System Working Storage on the cartridge with the most Working Storage available.
|A02 SYMBOL TABLE OVERFLOW...ASSEMBLY TERMINATED||The number of sectors of symbol table overflow is greater than the number of overflow sectors available.||Use an *OVERFLOW SECTORS control record to increase the number of overflow sectors for this assembly (maximum 32 sectors).|
|A03 DISK OUTPUT EXCEEDS W. S.||Intermediate output (pass 1) or final DSF output (pass 2) exceeds the capacity of Working Storage less the number of overflow sectors specified.||If this error occurs during pass 1, the system will WAIT at location $PRET with /400E (2501) or /100E (1442) in the accumulator. Press PROGRAM START to continue the assembly in TWO PASS MODE.
For pass 2, see options on A01.
|A04 SAVE SYMBOL TABLE INHIBITED||With SAVE SYMBOL TABLE option specified:
1. Program is relocatable.
2. Program contains assembly errors.
3. Source program contains more than 100 symbols.
|1. Use ABS card and reassembly.
2. Correct source program errors and reassemble.
3. Reduce the number of symbols and reassemble.
|A05 XXX ERRONEOUS ORG, BSS, OR EQU STATEMENTS IN ABOVE ASSEMBLY||XXX is the number of ORG, BSS, BES, and/or EQU Statements that were undefined in pass 1. At the end of pass 1, these erroneous statements are printed on the principal printer. If the error was due to forward referencing, it will not be detected during pass 2.||Where forward references have been attempted, they must be corrected before the program is reassembled.|
|A06 LOAD BLANK CARDS||A card containing a non-blank column between 1-71 has been read while punching a symbol table (*PUNCH SYMBOL TABLE specified for his assembly).||The system will WAIT with /100F in the accumulator. Nonprocess run out (NPRO) the card just read. Place blank cards ahead of this card in the hopper. Press reader START and console PROGRAM START.
NOTE: If the output is being punched on a 1442-5, a non-blank card cannot be detected. In addition, the punch may be damaged if an attempt is made to punch a hole where a hole already exists.
|A07 *LEVEL CONTROL RECORD MISSING||The program listed above was assembled as an ISS subroutine without the required *LEVEL control record.||Reassemble using *LEVEL control record.|
During compilation, a check is made to determine if certain errors have occurred. If one or more of these errors have been detected the error indications are printed at the conclusion of compilation, and no object program is stored on the disk. Only one error is detected for each statement. In addition, due to the interaction of error conditions, the occurrence of some errors may prevent the detection of others until those which have been detected are corrected. With the exception of the COO error message and those noted below, the error message appears in the following format:
CNN ERROR IN STATEMENT NUMBER XXXXX+YY
NN is the error code number listed in Table 9. With the exception of specification statement errors, XXXXX is the last valid statement number preceding the erroneous statement and YYY is the count of statements from XXXXX to the statement that is in error. If the erroneous statement has a valid statement number, XXXXX will be the statement in error and YYY will not be printed. For example:
105 FORMAT (15, F8.4) 110 IF (A-B) 10, 30, 20 A=A+1.0 ABC B = B-2.0 (error CO1) 135 GO TO 105 (error C43)
This example will cause the following error messages to be printed.
C01 ERROR IN STATEMENT NUMBER 110 + 002 C43 ERROR IN STATEMENT NUMBER 135
For specification statements, XXXXX is always 00000 and YYY is the count of the number of specification statements in error. YYY is never 000, i. e., for the first error YYY is 001. Specification statements are not counted unless they contain an error. Statement numbers on specification statements and statement functions are ignored. NN is the error code. For example:
1 DIMENSION C(10,10) 2 DIMENSION D(5,5) 3 DIMENSION E(I,6,6) (error C08) 4 DIMENSION F(4,4) 5 DIMENSION G(2,2)) (error C16)
This example will cause the following error messages to be printed.
C08 ERROR AT STATEMENT 00000 + 001 C16 ERROR AT STATEMENT 00000 + 002
In addition to the CNN type of error the following error messages may be encountered:
PROGRAM LENGTH EXCEEDS CAPACITY
The error occurs when the program in internal compiler format is too large to be contained in core working storage, and the program must be reduced in size in order to compile.
SUBROUTINE INITIALIZE TOO LARGE
During compilation of Sub-programs a subroutine initialize statement (CALL SUBIN) is generated.
The CALL SUBIN statement initializes all references to "dummy" variables contained within the subprogram to the appropriate core location in the calling program.
The nature of the FORTRAN compiler limits the size of any statement in internal compiler format to 511 words. In the case of CALL SUBIN, the size is calculated by the following formula:
S = 5 + ARG + N
where ARG is the number of arguments in the subroutine parameter list and N is the total number of times the dummy arguments are used within the subprogram. S is the total size of the CALL SUBIN statement; if S ever exceeds 511, an error occurs and the above error message is printed.
If any of these errors are detected during compilation, the message:
OUTPUT HAS BEEN SUPPRESSED is also printed.
If a monitor control record is encountered prior to an END card, the message
MONITOR CONTROL RECORD ENCOUNTERED
is printed, and control is returned to the monitor supervisor.
The above error and the C00 error will interrupt the compilation. In this case the message
will be printed.
|Error Number||Cause of Error|
|C00||WORKING STORAGE EXCEEDED
The working storage area on disk is too small to accommodate the compiled program in disk system format.
|C01||Non-numeric character in statement number.|
|C02||More than five continuation cards, or continuation card out of sequence.|
|C03||Syntax error in CALL LINK or CALL EXIT Statement.|
|C04||Undeterminable, misspelled, or incorrectly formed statement.|
|C05||Statement out of sequence.|
|C06||Statement following STOP, RETURN, CALL LINK, CALL EXIT, GO TO, or IF statement does not have statement number.|
|C07||Name longer than five characters, or name not starting with an alphabetic character.|
|C08||Incorrect or missing subscript within dimension information (DIMENSION, COMMON, REAL, or INTEGER).|
|C09||Duplicate statement number.|
|C10||Syntax error in COMMON statement.|
|C11||Duplicate name in COMMON statement.|
|C12||Syntax error in FUNCTION or SUBROUTINE statement.|
|C13||Parameter (dummy argument) appears in COMMON statement.|
|C14||Name appears twice on a parameter in SUBROUTINE or FUNCTION statement.|
|C15||*IOCS control record in a subprogram.|
|C16||Syntax error in DIMENSION statement.|
|C17||Subprogram name in DIMENSION statement.|
|C18||Name dimensioned more than once, or not dimensioned on first appearance of name.|
|C19||Syntax error in REAL, INTEGER, or EXTERNAL statement.|
|C20||Subprogram name in REAL or INTEGER statement.|
|C21||Name in EXTERNAL that is also in a COMMON or DIMENSION statement.|
|C22||IFIX or FLOAT in EXTERNAL statement.|
|C23||Invalid real constant.|
|C24||Invalid integer constant.|
|C25||More than 15 dummy arguments, or duplicate dummy argument in statement function argument list.|
|C26||Right parenthesis missing from a subscript expression.|
|C27||Syntax error in FORMAT statement.|
|C28||FORMAT statement without statement number.|
|C29||Field width specification greater than 145.|
|C30||In a FORMAT statement specifying E or F conversion, w greater than 121, d greater than 31, or d greater than w, where w is an unsigned integer constant specifying the total field length of the data, and d is an unsigned integer constant specifying the number of decimal places to the right of the decimal paint.|
|C31||Subscript error in EQUIVALENCE statement.|
|C32||Subscripted variable in a statement function.|
|C33||Incorrectly formed subscript expression.|
|C34||Undefined variable in subscript expression.|
|C35||Number of subscripts in a subscript expression does not agree with the dimension information.|
|C36||Invalid arithmetic statement or variable; or, in a FUNCTION subprogram the left side of on arithmetic statement is a dummy argument or in COMMON.|
|C37||Syntax error in IF statement.|
|C38||Invalid expression in IF statement.|
|C39||Syntax error or invalid simple argument in CALL statement.|
|C40||Invalid expression in CALL statement.|
|C41||Invalid expression to the left of an equal sign in a statement function.|
|C42||Invalid expression to the right of an equal sign in a statement function.|
|C43||In on IF, GO TO, or DO statement, a statement number is missing, invalid, incorrectly placed, or is the number of a FORMAT statement.|
|C44||Syntax error in READ or WRITE statement.|
|C45||*IOCS record missing with a READ or WRITE statement (mainline program only).|
|C46||FORMAT statement number missing or incorrect in a READ or WRITE statement.|
|C47||Syntax error in input/output list; or an invalid list element; or, in a FUNCTION subprogram, the input list element is a dummy argument or in COMMON.|
|C48||Syntax error in GO TO statement.|
|C49||Index of a computed GO TO is missing, invalid, or not preceded by a comma.|
|C50||*TRANSFER TRACE or *ARITHMETIC TRACE control record present, with no *IOCS control record in a mainline program.|
|C51||Incorrect nesting of DO statements; or the terminal statement of the associated DO statement is a GO TO, IF, RETURN, FORMAT, STOP, PAUSE, or DO statement.|
|C52||More than 25 nested DO statements.|
|C53||Syntax error in DO statement.|
|C54||Initial value in DO statement is zero.|
|C55||In a FUNCTION subprogram the index of DO is a dummy argument or in COMMON.|
|C56||Syntax error in BACKSPACE statement.|
|C57||Syntax error in REWIND statement.|
|C58||Syntax error in END FILE statement.|
|C59||Syntax error in STOP statement.|
|C60||Syntax error in PAUSE statement.|
|C61||Integer constant in STOP or PAUSE statement is greater than 9999.|
|C62||Last executable statement before END statement is not a STOP, GO TO, IF, CALL LINK, CALL EXIT, or RETURN statement.|
|C63||Statement contains more than 15 different subscript expressions.|
|C64||Statement too long to be scanned, because of compiler expansion of subscript expressions or compiler addition of generated temporary storage locations.|
|C65*||All variables are undefined in an EQUIVALENCE list.|
|C66*||Variable made equivalent to an element of an array in such a manner as to cause the array to extend beyond the origin of the COMMON area.|
|C67*||Two variables or array elements in COMMON are equated, or the relative locations of two variables or array elements are assigned more than once (directly or indirectly).|
|C68||Syntax error in on EQUIVALENCE statement; or an illegal variable name in on EQUIVALENCE list.|
|C69||Subprogram does not contain a RETURN statement, or a mainline program contains a RETURN statement.|
|C70||No DEFINE FILE statement in a mainline program that has disk READ, WRITE, or FIND statements.|
|C71||Syntax error in DEFINE FILE statement.|
|C72||Duplicate DEFINE FILE statement, more than 75 DEFINE FILES, or DEFINE FILE statement in subprogram.|
|C73||Syntax error in record number of disk READ, WRITE, or FIND statement.|
|C75||Syntax error in DATA statement.|
|C76||Names and constants in o DATA statement not in a one to one correspondence.|
|C77||Mixed mode in DATA statement.|
|C78||Invalid hollerith constant in a DATA statement.|
|C79||Invalid hexadecimal specification in a DATA statement.|
|C80||Variable in a DATA statement not used elsewhere in the program.|
|C81||COMMON variable loaded with a DATA specification.|
|C82||DATA statement too long.|
* The detection of a code 65, 66, or 67 error prevents any subsequent detection of any of these three errors.
When a DUP function is performed without error, an informational message is printed on the principal printer.
On a DEFINE VOID, one of the following messages is printed.
ASSEMBLER VOIDED FORTRAN VOIDED
On a DEFINE FIXED AREA, the message is as follows,
CART ID XXXX CYLS FXA XXXX DBS AVAIL XXXX FLET SECTOR ADDR XXXX
On a dump of LET or FLET, the printout is followed by a sign-off message.
END OF DUMPLET/FLET
All other DUP operations are followed by the following message.
CART ID XXXX DB ADDR XXXX DB CNT XXXX
DUP error messages are listed in Table 10.
|Error Number and Message||Cause of Error|
|D01 NAME IS NOT PRIME ENTRY||The primary name of the program in Working Storage does not match the name on the DUP control record.|
|D02 INVALID HEADER RECORD TYPE||One of the following is detected: a non-DSP program, a mispositioned header, foreign data, or on erroneous subtype.|
|D03 INVALID HEADER LENGTH||Word six of the DSF header is outside the range of 3-45. The causes are similar to D02, except for subtype.|
|D05 SECONDARY ENTRY POINT OR NAME ALREADY IN LET||The specified secondary entry point name is already in LET. The name must be deleted before this subprogram can be stored.|
|D06 ENTRY POINT NAME ALREADY IN LET/FLET||The specified name is already in The name must be deleted before this program or data file can be stored.|
|D12 INVALID DISK I/O SPECIFIED||Disk routine code on STORECI control record (column 9) was other than 0, 1, N, Z, or blank.|
|D13 INVALID FUNCTION FIELD (CC 1-12)||An invalid DUP function is specified in columns 1-12 of the DUP control record.|
|D14 INVALID FROM FIELD (CC 13-14)||Unacceptable characters ore in columns 13 and 14 of the DUP control record. The FROM field specified is not valid with this DUP function.|
|D15 INVALID TO FIELD (CC 17-18)||Unacceptable characters are in columns 17 and 18 of the DUP control record. The TO field specified is not valid with this DUP function.|
|D16 INVALID NAME FIELD (CC 21-25)||No name specified and one required, or syntax error in construction of name.|
|D17 INVALID COUNT FIELD (CC 27-30)||Columns 27 through 30 are blank or include alphabetic characters. The count field requires o decimal number.|
|D18 INVALID FUNCTION DURING TEMPORARY JOB||This function is not allowed during the JOB T mode.|
|D19 CARTRIDGE NOT ON SYSTEM||Cartridge specified as TO or FROM cartridge was not specified on JOB record as being used in this job.|
|D2O CARTRIDGE ID OUTSIDE VALID RANGE||Correct cartridge ID and retry. (0001-7FFF)|
|D21 INVALID STOREMOD. SIZE OF REPLACEMENT EXCEEDS SIZE OF ORIGINAL||The replacement version of the program or data file is larger than the current version. The old version must be deleted before the replacement can be stored.|
|D22 PROGRAM NOT IN WORKING STORAGE||The disk block count for the requested program in Working Storage is zero. The program is not in Working Storage.|
|D23 INVALID SYSTEM OVERLAY SUBTYPE SPECIFIED||The system overlay subtype indicator (column 11) on a STORE control record is not in the range 0-9.|
|D24 COUNT FIELD TOO LARGE||The count field extends beyond column 30 of a DEFINE FIXED AREA control record or column 31 is not a minus sign.|
|D25 REQUIRED FORMAT NOT IN W. S.||During a STOREMOD, the format of the LET/FLET entry does not agree with the format in Working Storage.|
|D26 NAME NOT POUND IN LET/FLET||The name specified on a DELETE or DUMP control record is not in LET/FLET.|
|D27 SOURCE NOT IN DSF||The format indicator of the FROM cartridge indicates that Working Storage on this cartridge does not contain a DSF program.|
|D30 INVALID RECORD TYPE||An invalid type binary record has been read when storing from cards or paper tape.|
|D31 PROGRAM OR DATA EXCEEDS DESTINATION DISK AREA||The number of disk blocks required to store a program or data exceeds the amount of space available in the specified TO field.|
|D32 INVALID CORE IMAGE CONVERSION||The Core Load Builder has inhibited the continuation of STORECI. The specific reason has been printed by the Core Load Builder.|
|D33 LET/FLET OVERFLOW. A CORE DUMP FOLLOWS||A ninth sector of LET/FLET is required (or a seventh sector of LET on a non-system cartridge) far the LET/FLET entry. A deletion of a program with a LET/FLET entry of similar size is required before this program can be stored.
A core dump follows this message since the affected cartridge may hove to be reloaded. The dump allows the user to locate the condition that caused the error. Use of the affected cartridge is not recommended until the problem has been investigated.
|D41 INVALID STORECI CONTROL RECORD||The STORECI control record read was not a LOCAL, NOCAL, or FILES record, or a mainline name was specified on a LOCAL or NOCAL record.|
|D42 STORECI CONTROL RECORDS INCORRECTLY ORDERED||LOCAL, NOCAL, and FILES records were intermixed. All records of a given type must be loaded together.|
|D43 INCORRECT CONTINUATION||A comma at the end of the record indicated that it would be continued; however, it was not.|
|D44 ILLEGAL CHARACTER IN RECORD||An illegal character, probably a blank, appeared in the record.|
|D45 ILLEGAL FILE NUMBER||A non-numeric character appears in a file number, or the number is more than five characters long.|
|D46 ILLEGAL NAME||A name is more than five characters long, or contain characters other than A-Z, 0-9, or $, or a name contains embedded blanks.|
|D47 ILLEGAL CARTRIDGE ID||The cartridge ID specified is not in the range/0001-/7FFF, or contains an illegal character.|
|D48 SCRA BUFFER OVERFLOW||The Supervisor Control Record Area (SCRA) cannot contain all the LOCAL, NOCAL, or FILES information.|
|D50 NON-BLANK CARD READ ENTER BLANK CARDS||A non-blank card has been read during a dump to a 1442-6 or -7. Place blank cards in the hopper and ready the card read punch. Press PROGRAM START.|
|D70 LAST ENTRY IN LET/FLET NOT 1DUMY||DELETE cannot find the end of LET or FLET. The header for this LET/FLET sector contains the count of unused words in this sector. This count should point to the last 1DUMY entry; however, the entry to which it now points is not a 1DUMY.|
|D71 1DUMY ENTRY IN LET/FLET IS FOLLOWED BY A SECONDARY ENTRY POINT||The name on the DELETE control record points to a secondary entry point. The first entry in LET/FLET with a non-zero disk block count that precedes the secondary entry is a 1DUMY. The primary entry is not in LET/FLET.|
|D72 FIRST ENTRY IN LET/FLET SECTOR IS A SECONDARY ENTRY POINT||The LET/FLET table is improperly constructed. The first entry is not a primary entry.|
|D80 FIXED AREA PRESENT||The FORTRAN Compiler and/or Assembler cannot be eliminated if a Fixed Area has been previously defined.|
|D81 ASSEMBLER NOT IN SYSTEM||The Assembler has previously been eliminated from the system.|
|D82 FORTRAN NOT IN SYSTEM||The FORTRAN Compiler has previously been eliminated from the system.|
|D83 INCREASE VALUE IN COUNT FIELD (CC 27-30)||The count field was read as a value of zero or one. The first DEFINE requires one cylinder for FLET plus one cylinder of Fixed Area. Thereafter, as little as one cylinder of additional Fixed Area can be defined.|
|D84 DEFECTIVE SLET||Cartridge must be reloaded.|
|D85 FIXED AREA NOT PRESENT||The control record specifies a decrease in the Fixed Area and there is no Fixed Area on the cartridge.|
|D86 DECREASE VALUE IN COUNT FIELD||There is insufficient Working Storage area available to allow the Fixed Area to be defined or expanded by the amount specified in the count field (cc 27-30). This message is preceded by a count of the number of cylinders available XXXX CYLS AVAILABLE. The count is in decimal.|
|D90 CHECK SUM ERROR||Checksum error in binary cord or paper tape record, or binary cards are out of order.|
|D92 INVALID DISKZ CALL. A CORE DUMP FOLLOWS||While performing a DUP function, an attempt has been made to read or write sector 0, or to read or write with a negative word count. This is a system error.
A core dump follows this message since the affected cartridge may have to be reloaded. The dump allows the user to locate the condition that caused the error. Use of the affected cartridge is not recommended until the problem has been investigated.
|D93 CARTRIDGE OVERFLOW||While performing a DUP function, an attempt has been mode to read or write a sector beyond 1599 decimal.|
No informational messages are printed during an initial load. At the completion of a reload, the following message is printed,
Table 11 lists the System Loader Errors.
|Error Number and Message||Corrective Action|
|E01 CHECKSUM ERROR||Follow procedure A or restart initial load.|
|E02 INVALID RECORD OR BLANK||Fallow procedure A or restart initial load.|
|E03 SEQ ERROR OR MISSING RECORDS||Follow procedure A or restart initial load.|
|E04 ORG BACKWARDS||Inspect deck far cards missing or out of sequence. Correct deck and restart from card in error.|
|E05 ERROR IN LOAD MODE RECORD||Follow procedure A or restart initial load.|
|E06 INVALID DRIVE NUMBER||Set all bit switches off. Set bit switches to select physical drive number and press PROGRAM START.
|E07 ID SCTR DATA INVALID||Use DCIP or DISC and follow with initial load.|
|E08 CONFIG DECK ERROR||System configuration deck may be missing, out of place, or may contain errors in one or more cards. Correct the deck and restart initial load.|
|E09 FILE PROTECT ADDRESS TOO HIGH||This error will occur on a reload only. The last program in the User Area extends into the last two cylinders on the cartridge. These cylinders are required by the System Loader during a reload operation. The file protect address must be lowered before a reload can be accomplished.|
|E10 SYST DECK ERROR||A card containing a negative phase ID has less than four data words. Correct the deck in error and restart initial load, or reload the phase in error, starting with the sector break card which precedes the last card read.|
|E11 SCRA OVERLAY STOP||Abort. An initial load must be performed to shift she location of the Supervisor Control Record Area (SCRA) address. An attempt to perform a reload on anon-system cartridge will cause this message to be printed.|
|E12 PHASE NO. OUT OF SEQ||The Accumulator contains the phase ID of the phase that is out of sequence (from last card read). Place the decks in proper order and continue from sector break card of correct phase.|
|E13 PHID RECD ERROR||Follow procedure A or reload and restart.|
|E14 PHASE MISSING||Error occurred when phase ID (binary word 11) of last card read was processed. Inspect Load Made card, PHID card, and phase ID of previously loaded phase to determine what phase is now required. Locate missing phase, place deck in reader starting with sector break card of missing phase, and continue.|
|E15 PH. ID NOT IN PHID CARD||The Accumulator contains the extraneous phase ID. To ignore this phase, press PROGRAM START. To load this phase, correct the PHID card and perform an initial load.|
|E16 PHASE ID NOT IN SLET||If this error occurs during a reload, and the system decks have not all been loaded, the error was caused by on attempt to reload a phase not presently in the System Location Equivalence Table (SLET). The Accumulator contains the ID of the phase that cannot be found. The Extension contains 0. Press PROGRAM START to bypass this phase.
If this error occurs during reload table processing, the Accumulator contains the phase ID that is being searched for and the Extension contains the ID of the phase requesting a SLET lookup. Press PROGRAM START to go on to the next phase requested or to the next requesting phase in SLET.
|E17 DEFECTIVE SLET||Processing cannot be completed. An initial load of the system is required.|
|E18 PAPER TAPE ERROR||The paper tape System Loader has found a word count greater than 54. This is probably due to incorrect sequencing of tapes, a faulty tape, or a paper tape reader malfunction. Correct error and restart initial load.|
If cards are being read from a 1442 Card Read Punch:
If cards are being read from a 2501 Card Reader:
|Accumulator Display||Cause of Error|
|F000||No *IOCS card appeared with the mainline program and I/O was attempted in o subroutine.|
|F001||Logical unit defined incorrectly, or No *IOCS control record for specified I/O device.|
|F002||Requested record exceeds allocated buffer size.|
|F003||Illegal character encountered in input record.|
|F004||Exponent too large or too small in input field.|
|F005||More than one E encountered in input field.|
|F006||More than one sign encountered in input field.|
|F007||More than one decimal paint encountered in input field.|
|F008||Read of output-only device, or Write of input-only device.|
|F009||Real variable transmitted with an I format specification or integer variable transmitted with an E or F format specification.|
|F020||Illegal unit reference. *|
|F021||Read list exceeds length of write list. *|
|F022||Record does not exist for read list element.|
|F023||Maximum length of $$$$$ area on the disk has been exceeded. This error is unrecoverable and results in a call exit.*|
|F100||File not defined by DEFINE FILE statement.|
|F101||File record too large, equal to zero, or negative.|
|F103||Disk FIO (SDFIO) has not been initialized.|
|F10A||Subscripting has destroyed the Define File Table. This occurs when a subscript exceeds the specification in a DIMENSION statement.|
|*) Can occur in unformatted I/O operations.|
When a FORTRAN I/O error occurs, the system WAITs at $PRET with an Fxxx error code displayed in the accumulator. Table 12 lists the FORTRAN I/O errors.
The monitor Supervisor causes all Monitor system control records to be printed on the principal printer.
During a DCOM update operation (i. e., following each JOB record or user call to SYSUP) the following message is printed.
LOG DRIVE CART SPEC CART AVAIL PHY DRIVE XXXX XXXX XXXX XXXX
LOG DRIVE is the drive number specified on the JOB card (in the calling sequence of the SYSUP subroutine)
CART SPEC is specified cartridge ID
CART AVAIL Is the available cartridge ID
PHY DRIVE is the physical drive number starting with 0.
The logical drive may be different from the physical drive, e.g., physical drive 0 may be defined as logical drive 2.
One line is printed for each physical drive on the system.
Tables 13, 14, and 15 list Supervisor errors.
|Error Number and Message||Cause of Error|
|M11 INVALID MONITOR CONTROL RECORD||A // record was not recognized as a valid Monitor control record.|
|M12 EXECUTION SUPPRESSED||$NXEQ was set upon detection of an error that would prevent successful execution by the system. Execution is bypassed.|
|M13 DUP SUPPRESSED||$NDUP was set upon detection of on error that would prevent successful DUP operation. DUP is bypassed.|
|M14 SYSTEM PROGRAM DETECTED MONITOR CONTROL RECORD||A system program has detected a Monitor control record when none was expected. The control record is passed to the MCRA for processing.|
|M15 ILLEGAL CARTRIDGE ID||A cartridge ID contains an illegal character or is a negative number. The job is aborted.|
|M16 ASM AND/OR FOR VOIDED||ASM or FOR requested but the FORTRAN Compiler and/or Assembler was either not loaded by the System Loader or was voided by a DUP DEFINE.|
|Error Number and Message||Cause of Error|
|M21 ABOVE RECORD NOT A SUPERVISOR CONTROL RECORD||The last record read is not a LOCAL, NOCAL, or FILES record.|
|M22 SUPERVISOR CONTROL RECORDS INCORRECTLY ORDERED||LOCAL, NOCAL, and FILES records cannot be intermixed.|
|M23 INCORRECT CONTINUATION||A comma at the end of the record indicated that the record would be continued; however, it was not.|
|M24 ILLEGAL CHARACTER IN RECORD||An illegal character, probably a blank, appeared in the record.|
|M25 ILLEGAL FILE NUMBER||A non-numeric character appears in a file number, or the number is more than five characters long.|
|M26 ILLEGAL NAME||A name is more than five characters long, or contains characters other than A-Z, 0-9, or $, or a name contains embedded blanks.|
|M27 ILLEGAL CARTRIDGE ID||The cartridge ID specified is not in the range /0001-/7FFF, or contains an illegal character.|
|M28 SCRA BUFFER OVERFLOW||The Supervisor Control Record Area (SCRA) cannot contain all the LOCAL, NOCAL, or FILES record information.|
|M29 ILLEGAL DISK SUBROUTINE REQUESTED||A character other than 0, 1, N, Z, or blank appeared in column 19 of the XEQ card.|
|Cartridge ID and Message||Cause of Error|
|XXXX IS NOT AN AVAILABLE CARTRIDGE ID||A requested cartridge ID is not on any cartridge on the system, or the ID is not listed in #CIDN of the DCOM on the cartridge.|
|XXXX IS A DUPLICATED SPECIFIED CARTRIDGE ID||The cartridge ID was listed as appearing on more than one drive on the JOB card.|
|XXXX IS A DUPLICATED AVAILABLE CARTRIDGE ID||A specified ID appears on more than one cartridge on the system.|
|XXXX IS NOT A SYSTEM CARTRIDGE||An attempt has been made to specify a non-system cartridge as the master cartridge (logical 0).|
Except for the core load map described in the Programming Tips and Techniques section and messages R41-R45, the Core Load Builder prints no informational messages. Table 16 lists Core Load Builder Error Messages.
|Error Number and Message||Cause and Corrective Action|
|R00 LOCALS/SOCALS OVERFLOW WORK STORAGE||There is insufficient Working Storage remaining to accommodate the LOCAL and/or SOCAL overlays required by the core load.
|R01 ORIGIN BELOW 1ST WORD OF MAINLINE||The Core Load Builder has been instructed to load a word into an address lower than the first word of the mainline program.
|R02 DEFINE FILE(S) OVERFLOW WORK STORAGE||There is insufficient Working Storage remaining to accommodate even one record of the defined file(s).
|R03 NO DSF PROGRAM IN WORKING STORAGE||No program in Working Storage.
|R05 INVALID LOADING ADDR FOR ILS02||ILS02 has been loaded into low COMMON.
|R06 FILE(S) TRUNCATED (SEE FILE MAP)||At least one defined file has been truncated, either because the previously defined storage area in the User or Fixed Area was inadequate, or because there is inadequate Working Storage available to store the file.
|R07 TOO MANY ENTRIES IN LOAD TABLE||There are references to more than (approximately) 150 different entry points in the core load by CALL and/or LIBF statements.
|R08 CORE LOAD EXCEEDS 32K||The Care Load Builder has been instructed to load a word into a core address that exceeds 32767 (a negative number). The loading process is immediately terminated, since the Core Load Builder cannot process negative addresses. The error was probably caused by bad data being read from the disk.|
|R09 LIBF TV REQUIRES 82 OR MORE ENTRIES||There are at least 82 different entry points referenced in the core load by LIBF statements.
|R16 XXXXX IS NOT IN LET OR FLET||The program or data file name printed in the message cannot be found in LET or FLET.
|R17 XXXXX CANNOT BE A LOCAL/NOCAL||The program named in this message is either a type which cannot appear on a *LOCAL control card, or is a LOCAL that has been referenced, directly or indirectly, by another LOCAL.|
|R18 XXXXX LOADING HAS BEEN TERMINATED||The loading of the mainline program named in this message has been terminated as a result of the errors listed in the messages preceding this one.|
|R19 XXXXX IS NOT A DATA FILE||The area named in this message does not begin at a sector boundary, which implies that it is not a data file but a DSF program, and thus a possible error.
|R20 XXXXX COMMON EXCEEDS THAT OF ML||The length of COMMON for the subroutine named in this message is longer than that of the mainline program.
|R21 XXXXX PRECISION DIFFERENT FROM ML||The precision for the subroutine named in this message is incompatible with that of the mainline program.
|R22 XXXXX AND ANOTHER VERSION REF'ENCED||At least two different versions of the same ISS have been referenced, e.g., CARDZ and CARD0 (FORTRAN uses CARDZ). If a disk subroutine is named in the message, it is possible that the XEQ record specifies one version (e.g., DISKZ) whereas the program references another (e.g., DISKN). (A blank in column 19 of the XEQ control record causes DISKZ to be used.)
|R23 XXXXX SHOULD BE IN THE FIXED AREA||The area named in this message is in the User Area. References in DEFINE FILE and DSA statements for *STORECI functions must be to the Fixed Area.|
|R39 XXXX IS NOT CURRENTLY ON SYSTEM||XXXX is a cartridge ID appearing on an FILES record. The cartridge was not on-line when the core load was built.|
|R40 XXXX(HEX) ADDITIONAL CORE REQUIRED||If the core load was executed, /XXXX is the number of words by which it exceeded core before the Core Load Builder made it fit by creating special overlays (SOCALs).
If the core load was not executed, /XXXX equals the number of words still required after the Core Load Builder has attempted to make it fit by using SOCALs.
|R41 XXXX(HEX) WORDS UNUSED BY CORE LOAD||NOT AN ERROR. /XXXX is the number of words of core storage not used by this core load.|
|R42 XXXX(HEX) IS THE EXECUTION ADDR||NOT AN ERROR. This message follows every successful conversion from DSF to DCI when a core map has been requested.|
|R43 XXXX(HEX) = ARITH/FUNC SOCAL WD CNT||NOT AN ERROR. It has been necessary to use special overlays (SOCALs) and /XXXX is the length of the arithmetic/function overlay (see System Overlays).|
|R44 XXXX(HEX) = FI/O, I/O SOCAL WD CNT||NOT AN ERROR. It has been necessary to use special overlays (SOCALs), and /XXXX Is the length of the FORTRAN I/O, I/O, and conversion subroutine overlay (see System Overlays).|
|R45 XXXX(HEX) = DISK FI/O SOCAL WD CNT||NOT AN ERROR. It has been necessary to use special overlays (SOCALs), and /XXXX is the length of the disk FORTRAN I/O overlay, including the 320 word buffer.|
|R46 XXXX(HEX) = AN ILLEGAL ML LOAD ADDR||/XXXX is the address at which the Core Load Builder has been requested to start loading the mainline program. However, this address is lower than the highest address occupied by the version of disk I/O requested for this core load.
This error may also be caused by starting on absolute mainline program at an odd location. An ORG to an even location, followed by a BSS of an odd number of words has the same effect as on ORG to an odd location.
|R47 XXXX(HEX) TOO MANY WDS IN COMMON||The length of COMMON specified in the mainline program plus the length of the core load exceeds core storage by /XXXX words.|
|R64 XXXXX IS BOTH A LIBF AND A CALL||The subroutine named in this message either been improperly referenced, i.e., CALL instead of LIBF or vice versa, or has been referenced in both CALL and LIBF statements.|
|R65 XXXXX HAS MORE THAN 14 ENTRY POINTS||This message usually means that the subroutine has been destroyed since a subroutine is not stored if it contains more than 14 entry points.|
|R66 XXXXX HAS AN INVALID TYPE CODE||The subroutine named in this message has either
The Auxiliary Supervisor prints no informational messages. Table 17 lists Auxiliary Supervisor Error messages.
A device not ready or illegal function parameter causes a pre-operative WAIT at $PRET. The ISS subroutine WAITs are listed in Table 18.
|Error Number and Message||Cause of Error|
|S00 INVALID FUNCTION CODE||The Auxiliary Supervisor received an illegal parameter.|
|S01 XXXXX IS NOT IN LET/FLET||The Core Image Loader is unable to find the specified name in LET or FLET.|
|S02 XXXXX IS A DATA FILE||The specified name cannot be executed since it is a data file, not a program.|
|Device Causing WAIT||Contents of Accumulator||Cause of WAIT|
|1442 Card Read Punch or 1442 Card Punch||/1000||Device not ready or last card indicator on for read.|
|/1001||Illegal device, device not in system, illegal function, word count over +80, or word count zero or negative.|
|Keyboard/Console Printer||/2000||Device not ready.|
|/2001||Device not in system, illegal function, or word count zero or negative.|
|1134/1055 Paper Tape Reader/Punch||/3000||Device not ready.|
|/3001||Illegal device, illegal function, word count zero or negative, or illegal check digit.|
|2501 Card Reader||/4000||Device not ready.|
|/4001||Illegal function, word count over +80, or word count zero or negative.|
|Disk||/5000||Device not ready.|
|/5001||Illegal device, device not in system, illegal function, attempt to write in file protected area, word count zero or negative, or starting sector identification over +1599.|
|/5002||Write select/power unsafe.|
|/5003||Same as /5001 except error caused by a Monitor program (DISK1, DISKN only).|
|/5004||Disk error (DISKZ only)|
|1132 Printer||/6000||Device not ready or end of forms.|
|/6001||Illegal function, word count over +60, or word count zero or negative.|
|1627 Plotter||/7000||Device not ready.|
|/7001||Illegal device, device not in system, illegal function, or word count zero or negative.|
|SCAT||/8001||Invalid function code or invalid word count (all SCAT subroutines).|
|Invalid sub-function code for some transmit or receive operation (SCAT2 or SCAT3 only).|
|/8002||Receive operation not completed or transmit operation not completed (SCAT1 only).|
|/8003||Failure to establish synchronization before attempting to perform some transmit or receive operation, or attempting to receive before receiving INQ sequence (SCAT1 only).|
|1403 Printer||/9000||Device not ready or end of forms.|
|/9001||Illegal function, word count over +60, or word count zero or negative.|
|1231 Optical Mark Page Reader||/A000||Device not ready.|
But wait, there's MORE...