The Micro Focus run time codes are listed here numerically, you may browse them, click on the link to go directly to the error code or you may use the search feature of your browser to search for the information.
The codes are broken up into numeric ranges to make the HTML documents smaller and thus load faster. They are basically divided into the groups by the hundreds digit, (ie 0-99, 100-199 and etc.). However each section has the index for all the run time codes.
001 002
003 004
005 006
007 008
009 010
012 013
014 015
016 017
018 019
020 021
022 023
024 025
026 027
028 029
030 031
032 033
034 035
036 037
038 039
040 041
042 043
044 045
046 047
048 055
065 066
067 068
069 070
071 072
073 074
075 076
077 078
079 081
082 086
100 101
102 103
104 105
106 107
108 109
110 114
115 116
117 118
119 120
121 122
123 124
125 126
129 135
137 138
139 141
142 143
144 146
147 148
149 151
152 153
154 155
156 157
158 159
160 161
162 163
164 165
166 167
168 169
170 171
172 173
174 175
176 177
178 179
180 181
182 183
184 185
186 187
188 189
190 191
192 193
194 195
196 197
198 199
201 202
203 206
207 208
209 210
211 213
214 215
216 217
218 219
220 221
222 223
224 225
226 227
228 229
230 235
236 237
254
Severity: Fatal
Explanation: You have tried a file operation which violates a general rule of COBOL in some way. The most likely cause of this error is that you have tried a rewrite on a sequential file opened I-O, or on a relative file with access mode sequential also opened I-O, without preceding it with a successful read NEXT.
Resolution: Recode your program to ensure that the REWRITE statement in error is preceded by a read NEXT.
Severity: Fatal
Explanation: This is the result of an internal system error.
Resolution: Contact Technical Support who will help you discover the cause of your error and how it can be rectified.
Severity: Fatal
Explanation: You have either specified an incorrect record length for a sequential file, or the sequential file you are trying to access is corrupt in some way, or the file which you have specified is not a sequential file.
Resolution: Recode your program so that it specifies the correct type of file, or if the error is the result of a corrupt file, try to run the program again using a backup copy of that file.
Severity: Fatal
Severity: Fatal
Explanation: You specified a data-name for a file-name instead of a literal, and the data item contained only spaces when you tried to open the file.
Resolution: Recode your program specifying the correct file-name.
Severity: Fatal
Explanation: The run-time system is unable to allocate sufficient memory space to successfully carry out the tried operation, probably because of insufficient memory space on your system.
Resolution: You should obtain more memory in which to run your program. Refer to your operating system documentation for details of how you can obtain more memory, if this is possible.
Severity: Fatal
Explanation: This could be the result of a read or write error to file or disk, but it is more likely to be the result of an internal system error.
Alternatively, your application might have called many programs without canceling them afterward, so that memory becomes exhausted during Animation.
Resolution: Contact Technical Support who will help you to discover the cause of your error and how it can be rectified.
Ensure that as much memory as possible is available during Animation by CANCELing any program you do not currently need to access.
Severity: Fatal
Explanation: You are trying to perform a file operation which your run-time system does not support.
Resolution: You should recode your program so that it does not try such operations, or you should acquire a version of your system that does support this facility.
Severity: Fatal
Explanation: The run-time system cannot load your program properly because the data needed to correctly initialize the Data Division has become corrupted.
Resolution: You should compile your program again to try to obtain good intermediate code.
Severity: Recoverable
Explanation: The internal information in the run-time system has been altered. The run-time system might have become corrupted, or you might have illegally tried to change the internal run-time system information.
Severity: Fatal
Resolution: Contact Technical Support who will help you to discover the cause of the error and how it can be rectified.
Severity: Fatal
Explanation: Memory access violation has been detected by your operating system.
Severity: Fatal
Explanation: A signal the run-time system was not expecting has been caught.
Severity: Fatal
Explanation: For some reason a part of your run-time system is unable to allocate you sufficient memory to enable you to execute your code.
Resolution: You should try to reduce memory usage by canceling programs that are not in use, then try the operation that caused this message again.
Severity: Fatal
Explanation: This is an internal system error.
Resolution: Please contact Technical Support who will help you to discover the cause of the error and how it can be rectified.
Severity: Fatal
Explanation: You are unable to load your object file. You have tried to call a program that has not been specified in the COBPATH environment variable.
Resolution: Check that your COBPATH has been set up correctly. If not, revise your COBPATH to include the program being called.
Severity: Fatal
Explanation: You are unable to load your object file because it has an entry point with the same name as a module already loaded.
Resolution: Once your program has terminated recode it to remove the naming duplication. Resubmit your program to your COBOL system.
Severity: Fatal
Explanation: You probably have a malformed object file.
Resolution: Once the program has terminated you must correct your object file. If this does not work, contact Technical Support who will help you to discover the specific cause of the error.
Severity: Fatal
Explanation: You have tried to call a subprogram that is not an executable program.
Alternatively, you have used the same name for a called program as for a previously defined data item.
Resolution: Check that the subprogram being called is an executable one. If required, correct the subprogram's name in the calling program and resubmit it to your COBOL system.
Once your program has terminated, recode it to remove the naming duplication. Resubmit your program to your COBOL system.
Severity: Fatal
Explanation: You might have returned control to a higher level in the CALL/PERFORM hierarchy than the level at which cobsetjmp was called. Coblongjmp must be called only from the same or from a lower level in the CALL/PERFORM hierarchy as cobsavenv was. See your COBOL System Reference for details of cobsavenv and coblongjmp.
Resolution: Check and correct the logic of your program, and then resubmit your program to your COBOL system.
Severity: Fatal
Explanation: You are using incompatible versions of the object file and the COBOL run-time library.
Resolution: Once the program has terminated, resubmit your object file to your COBOL system with the current version of your COBOL run-time library. If this does not work, contact Technical Support who will help you to discover the specific cause of the error.
Severity: Fatal
Severity: Recoverable
Explanation: The value specified in the RELATIVE KEY data item contains the value zero.
Resolution: You should ensure that the value in the RELATIVE KEY data item is greater than zero, then continue to run your program.
Severity: Recoverable
Explanation: The operating system has been unable to find a file which you have tried to access in your program.
Resolution: Ensure that you are in the correct directory or that a path to the file concerned exists. You can then try the file operation again. If the error is the result of a spelling mistake then ask for the correct file and try the file operation again.
Severity: Recoverable
Explanation: You are trying to open a file which you previously closed with lock, which violates one of the general rules of COBOL programming.
Resolution: You cannot open the relevant file. As this error implies that your program logic contains a mistake, you might want to close any remaining open files, execute a STOP RUN statement and recode.
Severity: Recoverable
Explanation: A discrepancy exists between the length of a record, or the keys which you have specified, in your current program and its definition in the program in which it was first opened.
Resolution: Your program has a fault, so you probably should edit your code, then resubmit it to your COBOL system before running it again.
Severity: Recoverable
Explanation: You have tried to open a file which is already open and so cannot be opened again.
Resolution: Cancel your second attempt to open the file and continue to run your program if the fact that the file is already open is acceptable to you. However as this error implies that your program logic contains a mistake, you might want to close any open files, execute a STOP RUN statement and then recode.
Severity: Recoverable
Explanation: You have tried to close a file which is not open which is impossible to achieve.
Resolution: You can abandon your attempt to close the relevant file and continue to run your program. However, as this error implies that your program logic contains a mistake, you might want to close any open files, execute a STOP RUN statement and then recode.
Severity: Recoverable
Explanation: You have failed to do a successful read on a sequentially accessed file trying a REWRITE or DELETE on some of the information contained in that file.
Resolution: If the previous read was successful then perform a read on the relevant file before you retry the unsuccessful REWRITE or DELETE operation. If the previous read was also unsuccessful close the file, execute a STOP RUN statement and then recode your program before you next run it.
Severity: Recoverable
Explanation: You have tried to write a record to a variable length record file, the length of which is not within the defined range for that file.
Resolution: Recode your program.
Severity: Recoverable
Explanation: The file position indicator in your file is undefined owing to a failed read/START or INVALID KEY condition. You have tried to read another record in the file but as the current record is undefined the system cannot find the start of the record for which you have asked.
Resolution: You should try a START operation, and continue to do so until the file position indicator is updated successfully.
Severity: Recoverable
Explanation: You have tried to carry out a read or START operation on a file which has not been opened for INPUT or I-O, or which is not open at all.
Resolution: Open the file for I-O or for INPUT and you should then be able to continue to run your program. However, as this error implies that your program logic contains a mistake, you might want to close any files which are open, execute a STOP RUN statement and then recode.
Severity: Recoverable
Explanation: You have tried to write to a file in sequential access mode that you have not opened for OUTPUT or EXTEND, or you have tried to write to a file in random or dynamic access mode that has not been opened INPUT or I-O, or which is not open at all.
Resolution: Close the file and reopen it with the correct open mode for the file type. However, as this error implies that your program logic contains a mistake, you might want to close any files that are open, execute a STOP RUN statement and then recode.
Severity: Recoverable
Explanation: You are trying to do a REWRITE or a DELETE on a file that you have not opened for I-O, or which is not open at all.
Resolution: Close the file and reopen for I-O. However, as this error implies that your program logic contains a mistake, you might want to close any open files, execute a STOP RUN statement and then recode.
Severity: Recoverable
Explanation: You are trying to do a random read on a file which has sequential organization.
Resolution: Read the file with the correct access mode. As this error implies that your program logic contains a mistake, you might like to close any files which are open, execute a STOP RUN statement and recode.
Severity: Recoverable
Explanation: You have tried a REWRITE on a file that is not open I-O.
Resolution: Close the relevant file and open it for I-O operations. You should then be able to carry out the REWRITE operation successfully. However, as this error implies that your program logic contains a mistake, you might want to close any open files, execute a STOP RUN statement and then recode.
Severity: Fatal
Explanation: A subscript which you have used in your program is out of the defined range, that is, it is either less than one or it is greater than the number of occurrences of the item.
Resolution: You should recode your program.
Severity: Fatal
Explanation: This error usually results if you have used GO TO to jump out of the range of a PERFORM rather than to jump to an EXIT statement at the end of its range.
Resolution: When your program has terminated you should to recode your program to ensure that the GO TO in question jumps to an EXIT statement at the end of the PERFORM's range.
Severity: Fatal
Explanation: The run-time system does not recognize as valid the command line format you have specified.
Alternatively, the generic command-line interpreter, which must be present if your program is to be run successfully, is not found on your system.
Alternatively, you have set an invalid COBSW value.
Resolution: Rerun your application with a valid command line.
Make sure that the interpreter is present to enable your system to pick up the commands correctly and then rerun your program.
Reset COBSW to a valid value.
Severity: Fatal
Explanation: You have coded a COMPUTE statement which is too complex for your system to handle successfully.
Resolution: You should recode your program. We strongly advise you to break the relevant COMPUTE statement into a number of simpler statements.
Severity: Recoverable
Explanation: Either your program is too large for the available memory space, or the stack is full.
Resolution: If you have specified the ON OVERFLOW/EXCEPTION clause in the relevant CALL statement, the error is recoverable. Any associated imperative statement is executed before the next instruction.
Severity: Recoverable
Explanation: You have used the REwrite statement in conjunction with a file whose organization is line sequential. The REWRITE statement cannot be used with line sequential files.
Resolution: Close the file in error before executing a STOP RUN statement to ensure that you do not lose any data from it. Recode your program to make the organization of the file to which you want to do a REWRITE either sequential, indexed sequential, or relative.
Severity: Recoverable
Explanation: A line-sequential file which you are trying to access is corrupt in some way.
Resolution: Rerun your program using the backup copy of that file.
Severity: Recoverable
Explanation: An error has occurred while trying to load the intermediate code for an independent segment. The segment is either missing or corrupted in some way.
Resolution: If the segment is missing, locate it. If you cannot find it, or if it is present and corrupt, resubmit your program to your COBOL system.
Severity: Fatal
Explanation: The intermediate code which is currently being processed is not valid code. You are probably trying to execute a corrupted file or one which has not been submitted to your COBOL system successfully.
Resolution: You should resubmit your source program to your COBOL system, to try to obtain uncorrupted intermediate code.
Severity: Fatal
Explanation: You are executing a program that is trying to perform a floating-point divide by zero.
Resolution: You should recode your program to avoid this illegal operation.
Severity: Fatal
Explanation: By default the value which you enter into a numeric or numeric edited field is checked to ensure that it is numeric. You have entered either nonnumeric characters or uninitialized numerics into numeric or numeric edited fields: these are automatically space filled and are thus classified as nonnumeric items.
Resolution: You must adjust your code so that no invalid data is used. You can locate the invalid numeric data in your code by setting the +F switch on, and animating your program until you receive this error. You might need to use one of the Compiler directives, BADSIGNS, HOST-NUMCOMPARE, SIGNCOMPARE or SPZERO, to resolve invalid data in numeric fields. See your COBOL System Reference for details of these directives.
Severity: Fatal
Explanation: You have tried to call a subroutine whose entry address has not been set up in your run-time system.
Resolution: Check to see that you used a valid call number in the unsuccessful subroutine call. If not, revise your code to contain a call number which your system recognizes. If you did use a valid call number but still received this error you should contact Technical Support.
Severity: Fatal
Explanation: One or more of the run-time support modules is incompatible with the run-time system you are using. The name of the incompatible support module is displayed.
Alternatively, the run-time system you are using is incompatible with the version of your COBOL system. Either "RTS" or the name of the run-time system file is displayed: coblib.dll (OS/2), coblib.dle (DOS) or coblib.dlw (Windows).
Resolution: Reinstall the support module, using your installation disks.
Reinstall the run-time system file, using your installation disks.
If no support module name is displayed, you have done one of the following:
Severity: Fatal
Explanation: You have tried to call a COBOL module that is already active.
Resolution: You should recode your program.
Severity: Fatal
Explanation: The list of items which you have supplied in a CALL....USING statement is longer than the run-time system can handle.
Resolution: Once your program has terminated recode it with group items rather than elementary items before rerunning it.
Severity: Fatal
Explanation: You have nested a PERFORM statement or a series of CALL statements too deeply.
Alternatively, if you have specified the CHECKSTACK directive when compiling your program, an incorrect number of parameters might have been used on a call, and as a result the stack has been corrupted.
Resolution: Edit your program to reduce the number of levels in the nested PERFORM or CALL statement.
If the CHECKSTACK directive has been used, determine which call is at fault and edit the source to provide the correct number and size of parameters.
Severity: Fatal
Explanation: You have tried an operation for which your machine is not configured; the most likely cause of this is that Adis is not configured correctly.
Resolution: Check that Adis is configured correctly. See your COBOL System Reference for details of how you can reconfigure Adis.
Severity: Fatal
Explanation: A system program, for example Adis or ExtFH, is not present on the current logged-in drive.
Resolution: Ensure that all the system programs are available on the logged-in drive and copy those which are not currently present using your backup system disk. Once all the necessary system programs are available you can run your program.
Severity: Fatal
Explanation: You are trying to perform Japanese operations with a non-Japanese run-time system, or you have used a Japanese version of your COBOL system to produce code which you are now trying to run using a non-Japanese run-time system.
Resolution: You should resubmit your program using a non-Japanese run-time system, or if you still want your program to perform Japanese operations, you should acquire a Japanese run-time system.
Severity: Fatal
Explanation: You have tried full recursion of a PERFORM statement in a program that was submitted to your COBOL system with the OSVS parameter of the PERFORM-TYPE directive specified. That is, you have tried to end two PERFORMs with the same return address.
Resolution: You should either resubmit your program to your COBOL system with a parameter other than OSVS specified for the PERFORM-TYPE directive, or recode your program so that each PERFORM has its own unique return address before you resubmit it to your COBOL system with the MF parameter of the PERFORM-TYPE directive specified.
Severity: Fatal
Explanation: You have tried to call a program which is not present on your current logged-in drive or directory, or in a directory pointed to by the COBDIR environment variable.
Resolution: Once your program has terminated you should copy the relevant file into your logged-in drive or directory. If insufficient space is available, you should set the COBDIR environment variable to search the directory or drive on which the file is present when your program calls it. Refer to your COBOL System Reference for details of the COBDIR environment variable. Once you have taken these steps, run your program again.
Severity: Fatal
Explanation: You have tried to load a .dll file which contains references to another .dll file which cannot be found by the operating system.
Resolution: Locate the missing file and ensure it is located on the default search path for your operating system.
Severity: Fatal
Explanation: You are trying to run a program that produced severe faults when you submitted it to your COBOL system with the run-time switch E turned off.
Alternatively, you could try to run the program with the E run-time switch set, though this might not give the desired results.
Resolution: You should edit your source code to correct all the severe faults, resubmit it to your COBOL system, then run the intermediate code that is produced.
When your program is being animated, Animator reports this error and enables you to continue to run the program.
See also:E RTS switch
Severity: Fatal
Explanation: You might have a corrupted file. Alternatively, your code contains a segment reference for the Forward Reference Table which is illegal.
Resolution: Resubmit your source code to your COBOL system. If you receive this error again, contact Technical Support who will help you to discover the specific cause of the error.
Severity: Fatal
Explanation: You have tried to remove a currently executing program or its parents or grandparents, from memory.
Alternatively, you have tried to cancel a DLL, either directly or indirectly as an imported DLL, that contains an entry point which has been registered as an EXIT LIST function via the OS/2 API call DosExitList.
Resolution: Once your program has terminated you need to recode your program to ensure that you do not try to cancel a program (or its parents or grandparents) while it is still being executed.
Locate the erroneous DLL and ensure that the EXIT LIST function is removed before you cancel the DLL. If you cannot recode the DLL, you can set the O RTS switch to force a logical cancel on the DLL.
See also:O RTS switch
Severity: Fatal
Explanation: You cannot save the information which your program has generated. This can be caused by several different reasons but one of the most common causes is that you have tried to Build a module that is too large for the available memory space.
Resolution: If the error is caused by a lack of space you can either delete some of the files which you no longer need on your current disk, or insert a new floppy disk to take the output from your program. You should then be able to rerun your program and save the information given by it.
Severity: Fatal
Explanation: You have tried to chain to another program which your system is unable to find.
Resolution: Once your program has terminated you should copy the relevant file into your logged-in drive or directory. If insufficient space is available, you should set the COBDIR environment variable to search the directory or drive on which the file is present when your program calls it. Refer to your COBOL System Reference for details of the COBDIR environment variable. Once you have taken these steps, run your program again.
Severity: Fatal
Explanation: A file-marker used to indicate that the end-of-file has been reached is missing from one of your files.
Resolution: You should resubmit your code to your COBOL system, or use a debugger to place the end-of-file marker at the end of the file. You can then rerun your program.
Severity: Fatal
Explanation: A parameter which you have used is not one which is recognized by your system. You have probably used a parameter for a run-time system subprogram which is not in the first 64K of the Data Division.
Resolution: Revise your code to contain a parameter which is known by your system. That is, ensure that the parameter is in the first 64K of the Data Division.
Severity: Fatal
Explanation: You are either trying to read input from the screen or write to the keyboard.
Resolution: You should recode your program.
Severity: Fatal
Explanation: You have tried to open a line-sequential file in the input-output open mode, but this mode is not supported for files with this organization.
Resolution: When your program has terminated you should recode your program to ensure that the file with organization line sequential is opened for input, output, or extend. You can then rerun your code.
Severity: Fatal
Explanation: You have either tried to read input from the screen or write to the keyboard, or the ADIS module has not been able to open your terminal's channels for I-O.
Resolution: Your program logic contains a mistake, so you must recode.
Severity: Recoverable
Severity: Recoverable
Explanation: You have tried to open either a standard input file with output mode, or some other file in an incorrect mode.
Severity: Fatal
Explanation: The run-time system cannot be found on the path you have set up in the COBDIR environment variable. Alternatively, you might not have installed your COBOL system correctly.
Resolution: Ensure that the run-time system is on the path you have set up in the COBDIR environment variable. Alternatively, ensure that your COBOL system has been installed correctly. If it has not, you must reinstall your COBOL system.
Severity: Fatal
Explanation: A file-name which you have used has more characters than the maximum number allowed by your operating system.
Resolution: You should recode your program to check the length of the file in error, and rename it with a shorter file-name. You can then run your program again.
Severity: Fatal
Explanation: You are unable to load your intermediate code. You might have tried to load intermediate code that either has not been successfully produced, or has been corrupted in some way.
Resolution: Try to obtain good intermediate code, for example, by resubmitting (or submitting) your source code to your COBOL system. You should then be able to load your code and run the program successfully.
Severity: Fatal
Explanation: A CALL statement in your program cannot be successfully executed because of the number of arguments which you have used with it.
Resolution: When your program has terminated you can recode it using group items rather than elementary ones. You should then be able to run your program successfully.
Severity: Fatal
Explanation: Your terminal is not defined.
Resolution: Your terminal type is undefined, so your operating system is unable to drive your terminal. Set up the necessary environment for your terminal.
Severity: Fatal
Explanation: A compulsory entry, for example cursor movement or clear screen, is missing from your terminal configuration database.
Resolution: Add the missing entry to your terminal configuration database.
Severity: Fatal
Explanation: The intermediate code which is currently being processed is not a valid operation. You are probably trying to execute a corrupt file or one which has not been produced.
Resolution: You should resubmit your source code to your COBOL system.
Severity: Fatal
Explanation: A file which your program is accessing is too large for successful execution to continue.
Resolution: When your program has terminated you should recode your program spreading the data over more than one file to ensure that no file becomes too large for your operating system to handle. Having recoded your program you can then rerun it.
Severity: Fatal
Explanation: Before a DELETE or a REwrite statement can be successfully executed in sequential access mode the last input-output statement executed for the associated file must have been a successful read. In your code no read statement precedes your tried DELETE or REwrite.
Resolution: When your program has terminated, recode your program, making sure that the last input-output statement to be executed before the DELETE or REwrite is a read statement.
Severity: Fatal
Explanation: The relative record key has exceeded the system limit, that is, the file is too large for the system to handle.
Alternatively, the record key which you have specified is too large for the system to deal with successfully, or the pointer to the record has been corrupted in some way so that it is either too large or it is not a multiple of the record length.
Severity: Fatal
Explanation: This error can be caused by one of the following:
Resolution: If you are using a DOS or OS/2 system, the monitor must be in alphanumeric display mode rather than graphics display mode. You can set the display mode to a valid alphanumeric mode by using the DOS MODE utility and then rerunning your program.
If you are using a UNIX-type system, you must check that your terminfo file contains the correct entry for your terminal. Refer to your COBOL System Reference for details. If your terminfo file is corrupt, or your screen handling interface has not been correctly initialized, you must advise your system administrator of the problem, and he will take steps to try to correct it. If your memory has been incorrectly allocated, you must rerun your program.
Severity: Fatal
Explanation: The system cannot load a program, usually because of insufficient memory.
Alternatively your program has run out of memory during the loading or reloading of a file. This occurs more frequently during Animation because of the extra memory required during Animation.
Resolution: Make more memory available and then rerun your program.
Ensure that as much memory as possible is available during Animation by CANCELing any program you do not currently need to access.
Severity: Fatal
Explanation: A system call has returned an unexpected error number which is not documented.
Resolution: Contact Technical Support who will help you to discover the specific cause of this error.