DATA0001 (Data Message Number I%.4d) EOF LOOKING FOR END-EXEC
 SEO encounter EOF on the COBOL source file or copy book while looking for
 the end of an EXEC statement.
 SEO Action. SEO continues to next COBOL source file or continues with the
 next statement after the COPY if the source code was in a copy book.

DATA0002 (Data Message Number I%.4d) UNKNOWN COBOL ELEMENT NAME
 SEO has found a string of characters that it cannot identify as a
 verb or data element name. Cases of hex literals (X'090A0B') will be
 converted to X" and flagged by this message. Reference modifiers in the
 form of, data1:data2 or literal1:literal2, will be flagged as unknown
 COBOL elements. If there are spaces around the colon, the colon will be
 flagged. All 78-level elements will be flagged as unknown since SEO
 does not recognize 78-level elements. All intrinstic functions will be
 flagged as unknown COBOL elements; nested intrinstic functions are
 rolled up to the highest level and that function is considered a data
 element that is unknown by SEO. The nested functions are not
 flagged.
 SEO Action: The statement is ignored.
 User Action: If the string is a valid COBOL element notify Technical
 Support

DATA0003 (Data Message Number I%.4d) PARAMETER/ARGUMENT MISMATCH
 SEO counted more arguments in the invoked subprogram than were
 passed by the invoking program.
 SEO Action: The mismatch is ignored.
 User Action: Make sure the count is correct before calling Technical
 Support.

DATA0004 (Data Message Number I%.4d) NO PERIOD SEPARATOR PRIOR TO
 PROCEDURE NAME

DATA0005 (Data Message Number I%.4d) ALTERNATE ENTRY POINT IN 'MAIN' PROGRAM.
 SEO has found 'ENTRY ' in a COBOL source file that was thought
 to be a main program.
 SEO Action: The ENTRY statement is ignored.

DATA0006 (Data Message Number I%.4d) execprgm.prg FD NAME NOT MATCHED
 SEO did not find a match between a FD name in the execprgm.prg
 file and any SELECT FD name ASSIGN [TO] clause in the COBOL source file
 SEO Action: SEO aborts
 User Action: Make sure the preprocessor has processed the COBOL program.

DATA0006 (Data Message Number I%.4d) execprgm.prg FD NAME NOT MATCHED
 SEO did not find a match between a FD name in the execprgm.prg
 file and any SELECT FD name ASSIGN [TO] clause in the COBOL source file
 SEO Action: SEO aborts

DATA0007 (Data Message Number I%.4d) ASSIGN [TO] NOT FOUND
 SEO did not find the ASSIGN [TO] clause of a SELECT statement.
 SEO Action: SEO aborts
 User Action: Make sure the SELECT statement is coded correctly.

DATA0007 (Data Message Number I%.4d) ASSIGN [TO] NOT FOUND
 SEO did not find the ASSIGN [TO] clause of a SELECT statement.
 SEO Action: SEO aborts

DATA0008 (Data Message Number I%.4d) INVALID LEVEL NUMBER
 SEO has found level number that is not valid.
 SEO Action: The statement is ignored.
 User Action: Make sure the level numbers are: 1 - 49, 66, 77, or 88.

DATA0009 (Data Message Number I%.4d) REACHED E-O-F PRIOR TO PROCEDURE DIVISION.
 SEO did not find a PROCEDURE DIVISION statement.
 SEO Action: SEO aborts
 User Action: Make sure division, section, and paragraph headers begin in
 the 'A' margin. Make sure the sequence columns (1 - 6) and the indicator
 column (7) are present in a record containing a source statement.

DATA0009 (Data Message Number I%.4d) REACHED E-O-F PRIOR TO PROCEDURE DIVISION.
 SEO did not find a PROCEDURE DIVISION statement.
 SEO Action: SEO aborts

DATA0010 (Data Message Number I%.4d) A VERB BEGINS IN THE 'A' MARGIN
 SEO has found a verb beginning in the 'A' margin.
 SEO Action: SEO aborts.
 User Action: Make sure the sequence columns (1 - 6) and the indicator
 column (7) are present in a record containing a source statement. Make
 sure all verbs begin in the 'B' margin. The 'END ....' and the 'EXIT ....'
 statements are acceptable in the 'A' margin. Make sure all paragraphs
 end with a period separator.

DATA0010 (Data Message Number I%.4d) A VERB BEGINS IN THE 'A' MARGIN
 SEO has found a verb beginning in the 'A' margin.
 SEO Action: SEO aborts.

DATA0011 (Data Message Number T%.4d) UNKNOWN STRING OF CHARACTERS
 SEO believes the string of characters should be a verb but the
 string is not a verb SEO recognizes.
 SEO Action: SEO looks for the next verb it knows.

DATA0012 (Data Message Number T%.4d) UNKNOWN STRING OF CHARACTERS
 SEO encountered a string of characters too long to be a valid COBOL
 term; or, the string was thought ot be a verb but is longer than 13 bytes.
 SEO Action: SEO aborts.
 User Action: Notify Technical Support.

DATA0012 (Data Message Number T%.4d) UNKNOWN STRING OF CHARACTERS
 SEO encountered a string of characters too long to be a valid COBOL
 term.
 SEO Action: SEO aborts.

DATA0013 (Data Message Number I%.4d) UNMATCHED PROCEDURE NAME IN GOTO/PERFORM
 SEO could not find the procedure name referenced in a GO TO or
 PERFORM statement.
 SEO Action: None.

DATA0014 (Data Message Number I%.4d) COPY ... REPLACING FORMAT IS UNKNOWN
 SEO could not process the REPLACING clause
 SEO Action: The statement is ignored.
 User Action: Make sure the format is correct before calling Technical
 Support.

DATA0015 (Data Message Number I%.4d) The highest qualifier could not be
 found.

DATA0016 (Data Message Number I%.4d) STRING FORMAT IS UNKNOWN
 SEO could not find the key word, DELIMITED.
 SEO Action: The statement is ignored.
 User Action: Make sure the format is correct before calling Technical
 Support.

DATA0017 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has written too many strings of characters to the literal
 buffer. The strings, identified as a single alphanumeric literal, exceed
 the length of the literal buffer.
 SEO Action: SEO aborts.

DATA0017 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has written too many strings of characters to the literal
 buffer. The strings, identified as a single alphanumeric literal, exceed
 the length of the literal buffer.
 SEO Action: SEO aborts.

DATA0018 (Data Message Number I%.4d) UNMATCHED PARENTHESES

DATA0019 (Data Message Number I%.4d) ITEM BEING TESTED AS A SUBSCRIPT
 IS TOO LARGE

DATA0020 (Data Message Number I%.4d) INVALID FIRST SOURCE STATEMENT
 SEO did not recognize the first (excluding comments) source
 statement in the COBOL program.
 SEO Action: SEO aborts.
 User Action: Make sure the first (excluding comments) source statement
 is a valid division, section, or paragraph header; or, a valid SELECT
 statement. Make sure the sequence columns (1 - 6) and the indicator column
 (7) are present in the source statement.

DATA0020 (Data Message Number I%.4d) INVALID FIRST SOURCE STATEMENT
 SEO did not recognize the first (excluding comments) source
 statement in the COBOL program.
 SEO Action: SEO aborts.

DATA0021 (Data Message Number I%.4d) PERFORM FORMAT NOT RECOGNIZED
 SEO could not process a PERFORM statement.
 SEO Action: The statement is ignored.
 User Action: Make sure the PERFORM statement is valid before calling
 Technical Support.

DATA0022 (Data Message Number I%.4d) NO MATCH FOR ENTRY POINT FOUND

DATA0023 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO expected a continuation, indicator column equals '-'.
 SEO Action: SEO aborts.

DATA0023 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO expected a continuation, indicator column equals '-'.
 SEO Action: SEO aborts.

DATA0024 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has found a continuation, indicator column equals '-',
 but the compress() function has nothing in buffer.
 SEO Action: SEO aborts.

DATA0024 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has found a continuation, indicator column equals '-',
 but the compress() function has nothing in buffer.
 SEO Action: SEO aborts.

DATA0025 (Data Message Number I%.4d) INVALID (UNPRINTABLE) CHARACTER
 SEO has found a TAB character or a bad character in the source
 file. The character is not part of an alphanumeric literal.
 SEO Action: SEO aborts.
 User action: Correct the source file and re-submit.

DATA0025 (Data Message Number I%.4d) INVALID (UNPRINTABLE) CHARACTER
 SEO has found a TAB character or a bad character in the source
 file. The character is not part of an alphanumeric literal.
 SEO Action: SEO aborts.

DATA0026 (Data Message Number I%.4d) RENAMES FORMAT ERROR
 SEO found a 66-level element without the keyword, RENAMES.
 SEO Action: The statement is ignored.

DATA0027 (Data Message Number I%.4d) EXPECTED STRING TO BE PROGRAM ID
 A string of characters following the PROGRAM-ID paragraph header is
 greater than 8 characters; or, a string of characters containing
 '.' or '-' characters exceeds 30 characters.
 SEO Action. The PROGRAM ID defaults to the source file name.

DATA0028 (Data Message Number I%.4d) SET FORMAT NOT RECOGNIZED
 SEO could not process a SET statement.
 SEO Action: The statement is ignored.
 User Action: Make sure the SET statement is valid before calling
 Technical Support.

DATA0029 (Data Message Number I%.4d) ALTER FORMAT ERROR
 SEO could not find the key word, TO, in a ALTER statement.
 SEO Action: The statement is ignored.
 User Action: Make sure the ALTER statement is valid before calling
 Technical Support.

DATA0030 (Data Message Number I%.4d) INVALID INDICATOR COLUMN VALUE
 SEO edits the indicator column for '-', '*', ' ', 'D', 'd', '/',
 and CR/LF.
 SEO Action: SEO aborts.
 User Action: Make sure the sequence columns (1 - 6) and the indicator
  column (7) are present in the source statement.

DATA0030 (Data Message Number I%.4d) INVALID INDICATOR COLUMN VALUE
 SEO edits the indicator column for '-', '*', ' ', 'D', 'd', '/',
 and CR/LF.
 SEO Action: SEO aborts.

DATA0031 (Data Message Number I%.4d) RECURSIVE COPY
 A nested copy book appears at the current level along the path as well as
 at a higher level.
 SEO Action. The copy book is bypassed.

DATA0032 (Data Message Number I%.4d) OUT OF MEMORY
 An attempt to allocate memory failed.
 SEO Action. SEO aborts.
 User Action.  If you use a version of DOS that permits loadhigh put DOS
 and the drivers you use into high memory. The number of lines of code in
 the COBOL program is not a factor in running out of memory. One thing
 that is a factor is the number of data elements in a single record. If
 you have a record with 2500+ data elements SEO may have trouble
 getting enough memory to deal with the record.

DATA0032 (Data Message Number I%.4d) OUT OF MEMORY
 An attempt to allocate memory failed.
 SEO Action. SEO aborts.
 User Action.  If you use a version of DOS that permits loadhigh put DOS
 and the drivers you use into high memory. The number of lines of code in
 the COBOL program is not a factor in running out of memory. One thing
 that is a factor is the number of data elements in a single record. If
 you have a record with 2500+ data elements SEO may have trouble
 getting enough memory to deal with the record.

DATA0033 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has found two or more spaces between terms in buffer after
 the compress() function read the last COBOL source statement.
 SEO Action: SEO aborts.

DATA0033 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has found two or more spaces between terms in buffer after
 the compress() function read the last COBOL source statement.
 SEO Action: SEO aborts.

DATA0034 (Data Message Number T%.4d) INTERNAL ERROR
 SEO processed a COPY ... REPLACING operand BY operand .... statement
 and now cannot find the end of the current PROCEDURE DIVISION statement.
 SEO Action: The statement is ignored.
 User Action: Make sure the COPY ... REPLACING .... is valid before calling
 Technical Support.

DATA0035 (Data Message Number I%.4d) REACHED EOF LOOKING FOR QUALIFIER

DATA0036 (Data Message Number T%.4d) DATA ELEMENT NAME IS RESERVED FOR VERB
 SEO checks all data element names for possible conflict with
 verbs and other key PROCEDURE DIVISION words.
 SEO Action: SEO aborts.
 User Action: Rename the element.

DATA0036 (Data Message Number T%.4d) DATA ELEMENT NAME IS RESERVED FOR VERB
 SEO checks all data element names for possible conflict with
 verbs and other key PROCEDURE DIVISION words.
 SEO Action: SEO aborts.

DATA0037 (Data Message Number I%.4d) RECURSIVE CALL.
 SEO is processing a subprogram that appears to have invoked itself
 or is in a path where the same subprogram was found at a higher level in
 the path.
 SEO Action: The subprogram source file is bypassed and SEO
 continues with the statement following the CALL.

DATA0038 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has not found a space+NULL byte at the end of buffer after
 the compress() read the last source record.
 SEO Action: SEO aborts.
 User Action: Call Technical Support.

DATA0038 (Data Message Number T%.4d) BUFFER CONTENT ERROR
 SEO has not found a space+NULL byte at the end of buffer after
 the compress() read the last source record.
 SEO Action: SEO aborts.

DATA0039 (Data Message Number I%.4d) UNSUPPORTED DIRECTIVES
 SEO has found one of the following: -INC, ++INCLUDE, REPLACE
 These directives are not supported
 SEO Action: SEO aborts.

DATA0039 (Data Message Number I%.4d) UNSUPPORTED DIRECTIVES
 SEO has found one of the following: -INC, ++INCLUDE, REPLACE
 These directives are not supported
 SEO Action: SEO aborts.

DATA0040 (Data Message Number I%.4d) CONFLICT BETWEEN RECORD LENGTH AND
 FIELD OFFSET

DATA0041 (Data Message Number I%.4d) THE SORT KEYS ARE GREATER THAN THE
 MAXIMUM

DATA0042 (Data Message Number I%.4d) select_nearest_key() HAS RETURNED
 AN INVALID ORDINAL NR

DATA0043 (Data Message Number T%.4d) INTERNAL ERROR, alnum_lit NOT PRESENT
 SEO expected to find an alphanumeric literal in the alnum_lit
 structure. The literal is part of a COPY ... REPLACING statement; but, the
 next structure pointer in alnum_lit was NULL.
 SEO Action: SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0043 (Data Message Number T%.4d) INTERNAL ERROR, alnum_lit NOT PRESENT
 SEO expected to find an alphanumeric literal in the alnum_lit
 structure. The literal is part of a COPY ... REPLACING statement; but, the
 next structure pointer in alnum_lit was NULL.
 SEO Action: SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0044 (Data Message Number I%.4d) THE SORTIN RECORDS ARE GREATER
 THAN THE MAXIMUM

DATA0045 (Data Message Number I%.4d) THE SORTIN FILE IS NOT
 COMPATIBLE WITH THE SPECIFIED RECORD LENGTH.

DATA0046 (Data Message Number I%.4d) PROCEDURE NAME IS RESERVED FOR VERB
 SEO could not find a procedure name following a GO TO verb.
 The most likely cause is a procedure name that is the same as a verb
 (e.g., END-SEARCH) or other reserved PROCEDURE DIVISION name.
 The same applies to the THROUGH clause of the PERFORM verb and the
 INPUT and OUTPUT PROCEDURE's in a SORT or MERGE. A PERFORM
 without a procedure name following the keyword PERFORM is considered
 to be an in-line PERFORM.
 SEO Action: The statement is ignored.

DATA0047 (Data Message Number I%.4d) BUFFER OVERFLOW
 SEO has detected that the primary buffer is full. SEO uses
 a buffer of 6000 bytes to hold a single COBOL data definition or a single
 verb statement - after the alphanumeric literals are removed and all
 unnecessary blanks are removed.
 SEO Action. SEO aborts.
 User Action. Make sure the input file to SEO is a COBOL source file.

DATA0047 (Data Message Number I%.4d) BUFFER OVERFLOW
 SEO has detected that the primary buffer is full. SEO uses
 a buffer of 6000 bytes to hold a single COBOL data definition or a single
 verb statement - after the alphanumeric literals are removed and all
 unnecessary blanks are removed.
 SEO Action. SEO aborts.
 User Action. Make sure the input file to SEO is a COBOL source file.

DATA0048 (Data Message Number I%.4d) INVALID EXECPRGM.PRG RECORD
 SEO edited the execprgm.prg record created by the preprocessor
 (prepro.bat). The format should be: 8-byte (or less) program ID and
 8-byte (or less) DDNAME, separated by at least one space. The program
 ID must start in column one and the DDNAME must start in column nine.
 SEO Action. Theparser aborts.
 User Action. Make sure the preprocessor has been run successfully.

DATA0048 (Data Message Number I%.4d) INVALID EXECPRGM.PRG RECORD
 SEO edited the execprgm.prg record created by the preprocessor
 (prepro.bat). The format should be: 8-byte (or less) program ID and
 8-byte (or less) DDNAME, separated by at least one space. The program
 ID must start in column one and the DDNAME must start in column ten.
 SEO Action. SEO aborts.
 User Action. Make sure the preprocessor has been run successfully.

DATA0049 (Data Message Number I%.4d) GROUP MOVE LIMIT EXCEEDED
 SEO limit is 2730 elements in a group move.
 SEO Action: The remaining elements are ignored.

DATA0050 (Data Message Number I%.4d) NESTED REDEFINES ARE TOO DEEP
 SEO limit is 49 levels.
 SEO Action: The remaining redefines are ignored.

DATA0051 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while handling sub programs.
 SEO Action. SEO aborts.
 User Action: Notify Technical Support.

DATA0051 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while handling sub programs.
 SEO Action. SEO aborts.
 User Action: Notify Technical Support.

DATA0052 (Data Message Number T%.4d) INTERNAL ERROR, ERROR SORTING FILE
 SEO received a bad status from the create_inx() function.
 SEO Action. SEO aborts.
 User Action. Notify Technical support.

DATA0052 (Data Message Number T%.4d) INTERNAL ERROR, ERROR SORTING FILE
 SEO received a bad status from the create_inx() function.
 SEO Action. SEO aborts.
 User Action. Notify Technical support.

DATA0053 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while searching for REDEFINES
 information.
 SEO Action: SEO aborts.
 User Action: Notify Technical Support.

DATA0053 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while searching for REDEFINES
 information.
 SEO Action: SEO aborts.

DATA0054 (Data Message Number I%.4d) NESTED SUBPROGRAMS.
 SEO was processing the PROCEDURE DIVISION when it found one of the
 following: [IDENTIFICATION] [ID] DIVISION or END PROGRAM .... Nested
 programs in the same COBOL source file is not supported by this version of
 SEO.
 SEO Action: The end-of-file condition is set equal to TRUE.

DATA0055 (Data Message Number I%.4d) UNEXPECTED E-O-F IN COBOL SOURCE
 SEO was looking for the next verb or a period separator when
 E-O-F was encountered.
 SEO Action: The current statement is ignored.

DATA0056 (Data Message Number I%.4d) OVERFLOW ERROR
 SEO attempted to relate all the file's 01 level record names to
 the file name; but, the number of 01 level record names is greater than
 SEO's capacity, app. 200.
 SEO Action. SEO aborts.

DATA0056 (Data Message Number I%.4d) OVERFLOW ERROR
 SEO attempted to relate all the file's 01 level record names to
 the file name; but, the number of 01 level record names is greater than
 SEO's capacity, app. 200.
 SEO Action. SEO aborts.

DATA0057 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while handling records belonging
 to a file definition. SEO was unable to find the records belonging
 to a file definition (FD).
 SEO Action. SEO aborts.
 User Action: Notify Technical Support.

DATA0057 (Data Message Number T%.4d) INTERNAL ERROR
 SEO has incurred an internal error while handling records belonging
 to a file definition. SEO was unable to find the records belonging
 to a file definition (FD).
 SEO Action. SEO aborts.
 User Action: Notify Technical Support.

DATA0058 (Data Message Number I%.4d) REACHED EOF LOOKING FOR USING ....
 SEO attempted to find the end of a PROCEDURE DIVISION USING ...
 statement and encountered EOF.
 SEO Action. SEO aborts.

DATA0058 (Data Message Number I%.4d) REACHED EOF LOOKING FOR USING ....
 SEO attempted to find the end of a PROCEDURE DIVISION USING ...
 statement and encountered EOF.
 SEO Action. SEO aborts.

DATA0059 (Data Message Number T%.4d) INTERNAL ERROR, INVALID POINTER
 SEO has detected an invalid pointer value.
 SEO Action. SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0059 (Data Message Number T%.4d) INTERNAL ERROR, INVALID POINTER
 SEO has detected an invalid pointer value.
 SEO Action. SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0060 (Data Message Number I%.4d) DATA ELEMENT NAME TRUNCATED
 SEO limit is 30 bytes for a data element name. The name was
 truncated.

DATA0061 (Data Message Number I%.4d) ENTRY POINT TRUNCATED
 SEO limit is 8 bytes for an entry point name. The name was
 truncated.

DATA0062 (Data Message Number I%.4d) UNKNOWN LITERAL IN SELECT STATEMENT
 SEO encountered an alphnumeric literal that is too long to fit in
 the buffer for a ddname.
 SEO Action: SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0062 (Data Message Number I%.4d) UNKNOWN LITERAL IN SELECT STATEMENT
 SEO encountered an alphnumeric literal that is too long to fit in
 the buffer for a ddname.
 SEO Action: SEO aborts.
 User Acton. Send the progid.seo file via CompuServe or mail to Technical
 Support; where, progid in the name of the COBOL program. The file will be
 in the EXS sub directory of the application ID.

DATA0063 (Data Message Number I%.4d) ELEMENTARY ITEM WITHOUT 01-LEVEL
 SEO encountered an elementary item (level > 1 and < 50) but there was no
 prior 01-level group item.
 SEO Action. SEO bypasses the item.
 User Action. Make sure the elementary item has an 01-level; if the group
 item is defined in a copy book, make sure the copy book is present.

FILE0001 (File Message Number I%.4d) ERROR OPENING INPUT FILE
 SEO attempted to open a source file for a called program or a
 copy book and the attempt failed. SEO continues with the statement
 following the CALL verb or COPY directive. A missing copy book will result
 in many DATA0002 messages, "UNKNOWN COBOL ELEMENT NAME", if there are
 references to the missing elements. PC COBOL call by number (CALL X'1A')
 and call by name (CALL CBL_GET_VIDEO_CONFIG) are converted to
 "CALL callBYnr" and "CALL callBYnm" respectively and result in this message
 (FILE0001). Nested calls to program names greater than eight characters are
 converted to "CALL callnest" that also result in this message. This
 condition does not abort SEO.
 This message is also produced when SEO attempts to open, for the
 first time, the following files: .ifi, .f2s, .f1s, .inx, or .mst. This
 means SEO is aware there are times when a program is coded with
 no data elements or procedures; e.g., a common abort sub program which
 simply moves 16 to the COBOL register, RETURN-CODE, and does a STOP RUN.
 A failed attempt to open one of these files a second time, after
 processing a CALL verb, results in a FILE0005 message.
 SEO Action: SEO continues.
FILE0002 (File Message Number I%.4d) ERROR OPENING OUTPUT FILE
 SEO attempted to open a required output file. The attempt
 failed. See the DOS error message. The most likely cause is too
 many files open. Make sure the config.sys file specifies a large
 number of files (FILES=nn); e.g., FILES=50.
 SEO Action: SEO aborts
FILE0002 (File Message Number I%.4d) ERROR OPENING OUTPUT FILE
 SEO attempted to open a required output file. The attempt
 failed. See the DOS error message. The most likely cause is too
 many files open. Make sure the config.sys file specifies a large
 number of files (FILES=nn); e.g., FILES=50.
 SEO Action: SEO aborts
FILE0003 (File Message Number I%.4d) ERROR WRITING RECORD
 SEO attempted to write a record. The attempt failed. See the
 DOS error message. The most likely cause is no space left on the
 device. Another possibility, if a RAM drive is being used, is the
 parser exceeded the 64 file allocation tables (FAT) limit of the
 root directory. Either define the RAM drive with a larger limit
 or create a sub directory, which as no limit.
 SEO Action: SEO aborts
FILE0003 (File Message Number I%.4d) ERROR WRITING RECORD
 SEO attempted to write a record. The attempt failed. See the
 DOS error message. The most likely cause is no space left on the
 device. Another possibility, if a RAM drive is being used, is the
 parser exceeded the 64 file allocation tables (FAT) limit of the
 root directory. Either define the RAM drive with a larger limit
 or create a sub directory, which as no limit.
 SEO Action: SEO aborts
FILE0005 (File Message Number I%.4d) ERROR REOPENING INPUT FILE
 SEO attempted to reopen a file in a program that called another
 program after the call verb was processed. The attempt failed. This
 could mean the file never existed in the first place. That would mean
 there were no DATA DIVISION elements and/or procedures. This could
 happen if copy books were used to define the elements, and the copy
 books are missing. PROCEDURE DIVISION references to elements when the
 parser is not aware that any elements exist will abort SEO
 SEO Action: SEO aborts
FILE0005 (File Message Number I%.4d) ERROR REOPENING INPUT FILE
 SEO attempted to reopen a file in a program that called another
 program after the call verb was processed. The attempt failed. This
 could mean the file never existed in the first place. That would mean
 there were no DATA DIVISION elements and/or procedures. This could
 happen if copy books were used to define the elements, and the copy
 books are missing. PROCEDURE DIVISION references to elements when the
 parser is not aware that any elements exist will abort SEO
 SEO Action: SEO aborts
FILE0006 (File Message Number I%.4d) ERROR READING FILE
 SEO Action: SEO aborts
FILE0006 (File Message Number I%.4d) ERROR READING FILE
 SEO Action: SEO aborts
FILE0007 (File Message Number I%.4d) ERROR SEEKING RECORD
 SEO attempted to seek a byte address using a relative byte address
 returned from qualified_names(). The attempt failed.
 SEO Action: SEO aborts
FILE0007 (File Message Number I%.4d) ERROR SEEKING RECORD
 SEO attempted to seek a byte address using a relative byte address
 returned from qualified_names(). The attempt failed.
 SEO Action: SEO aborts
FILE0009 (File Message Number I%.4d) UNABLE TO OPEN SORT FILE
 The sort attempted to open the sortin or a sortwork file for input. The
 attempt failed.
 SEO Action: SEO aborts.
FILE0009 (File Message Number I%.4d) UNABLE TO OPEN SORT FILE
 The sort attempted to open the sortin or a sortwork file for input. The
 attempt failed.
 SEO Action: SEO aborts.
FILE0010 (File Message Number I%.4d) UNABLE TO DELETE FILE
 Mostly, these are files not created in the first place, perhaps because a
 called subprogram was not found, for example. But a failed attempt to
 delete a file is noted.
 SEO Action: None.
 User Action: You can check the FILE0001 message. The name of the program
 matching the program name here should be found there also.
FILE0011 (File Message Number I%.4d) ERROR RESETTING FILE POSITION
 SEO attempted to reset the file position on the COBOL source file
 of a program that called another program. This occurs after the sub
 program's source code is processed. The attempt failed.
 SEO Action. SEO aborts.
FILE0011 (File Message Number I%.4d) ERROR RESETTING FILE POSITION
 SEO attempted to reset the file position on the COBOL source file
 of a program that called another program. This occurs after the sub
 program's source code is processed. The attempt failed.
 SEO Action. SEO aborts.
FILE0012 (File Message Number I%.4d) ERROR GETTING CURRENT WORKING DIRECTORY
 The sort did not have a working directory specified by an environment
 variable and failed to get the current working directory.
 SEO Action: SEO aborts.
FILE0012 (File Message Number I%.4d) ERROR GETTING CURRENT WORKING DIRECTORY
 The sort did not have a working directory specified by an environment
 variable and failed to get the current working directory.
 SEO Action: SEO aborts.
FILE0013 (File Message Number I%.4d) THE COBOL SOURCE DIRECTORY IS EMPTY
 SEO attempted to get a COBOL source file from the specified (or default)
 directory. The attempt failed.
 SEO Action. SEO aborts.
 User Action: Make sure of the path to the COBOL programs. Make sure all
 COBOL program have .cbl extensions.
FILE0013 (File Message Number I%.4d) THE COBOL SOURCE DIRECTORY IS EMPTY
 SEO attempted to get a COBOL source file from the specified (or default)
 directory. The attempt failed.
 SEO Action. SEO aborts.
 User Action: Make sure of the path to the COBOL programs. Make sure all
 COBOL program have .cbl extensions.
FILE0014 (File Message Number I%.4d) ERROR OPENING NEXT COBOL SOURCE FILE
 SEO attempted to open the next COBOL source file in the directory. The
 attempt failed for a unknown reason.
 SEO Action. SEO aborts.
FILE0014 (File Message Number I%.4d) ERROR OPENING NEXT COBOL SOURCE FILE
 SEO attempted to open the next COBOL source file in the directory. The
 attempt failed for a unknown reason.
 SEO Action. SEO aborts.
FILE0015 (File Message Number I%.4d) ERROR GETTING FILE POSITION
 SEO attempted to get the file position on a work file. The attempt failed.
 SEO Action. SEO aborts.
FILE0015 (File Message Number I%.4d) ERROR GETTING FILE POSITION
 SEO attempted to get the file position on a work file. The attempt failed.
 SEO Action. SEO aborts.
FILE0016 (File Message Number I%.4d) ERROR OPENING REQUIRED OUTPUT FILE
 SEO attempted to open the file but the attempt failed.
 SEO Action. SEO aborts.
 User Action. Make sure the application ID on the command line matches an
 existing sub directory of the SEO working directory, MACHY.
FILE0016 (File Message Number I%.4d) ERROR OPENING WORK FILE AS INPUT
 SEO attempted to open the file but the attempt failed.
 SEO Action. SEO aborts.
 User Action. Make sure the application ID on the command line matches an
 existing sub directory of the SEO working directory, MACHY.
FILE0017 (File Message Number I%.4d) ERROR OPENING WORK FILE AS INPUT
 SEO attempted to open a file just created. The attempt failed.
 SEO Action. SEO aborts.
 User Action. Check the DOS error message before calling Technical Support.
FILE0017 (File Message Number I%.4d) ERROR OPENING WORK FILE AS INPUT
 SEO attempted to open a file just created. The attempt failed.
 SEO Action. SEO aborts.
 User Action. Check the DOS error message before calling Technical Support.
FILE0018 (File Message Number I%.4d) ERROR OPENING WORK FILE AS OUTPUT
 SEO Action. SEO aborts.
 User Action. Check the DOS error message. The most likely cause is no space
 left on the device. Another possibility, if a RAM drive is being used, is
 SEO exceeded the 64 file allocation tables (FAT) limit of the root
 directory. Either define the RAM drive with a larger limit or create a sub
 directory, which as no limit.
FILE0018 (File Message Number I%.4d) ERROR OPENING WORK FILE AS OUTPUT
 SEO Action. SEO aborts.
 User Action. Check the DOS error message. The most likely cause is no space
 left on the device. Another possibility, if a RAM drive is being used, is
 SEO exceeded the 64 file allocation tables (FAT) limit of the root
 directory. Either define the RAM drive with a larger limit or create a sub
 directory, which as no limit.

MEMO0001 (Memory Message Number I%.4d) ERROR ALLOCATING MEMORY
 SEO attempted to allocate memory and was unsuccessful.
 SEO Action: SEO aborts.
 User Action. Check the amount of DOS conventional memory available for an
 application program. If the amount is less than 600,000 bytes and you are
 using a version of DOS that permits LOADHIGH, put DOS in high memory; also,
 put all drivers and TSR's in high memory. This should make 620,000 bytes
 available for application programs like the parser. If the problem persists
 the problem is mostly a record in the COBOL program that contains a large
 amount of elements (in excess of 3,000 elements). If such a record exists
 the parser will not be able to get enough memory to parse the program.

MEMO0001 (Memory Message Number I%.4d) ERROR ALLOCATING MEMORY
 SEO attempted to allocate memory and was unsuccessful.
 SEO Action: SEO aborts.
 User Action. Check the COBOL program's .seo file in the EXS sub directory
 of application Id.