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: No room is available in your current directory or on the floppy disk which you are using, for the paging file.
Resolution: When your program has terminated, delete any files which you no longer need from your directory to make room for the paging file, or insert a new floppy disk.
Severity: Fatal
Explanation: You have either caused an internal run-time system error by invalid use of an exported function, or the code produced by a preprocessor in your COBOL system contains errors.
Resolution: Ensure that all of your external assembler applications call and use run-time system functions correctly before you try to run your program again. If you are using a preprocessor as part of your COBOL system, you should use the software as a standalone preprocessor to isolate the problem areas.
Severity: Fatal
Explanation: The item you are trying to access in the Linkage Section of the currently executing program has not been initialized.
Resolution: Recode your program to ensure that it contains all of the necessary parameters, or check that it is a valid caller.
Severity: Fatal
Explanation: You are trying to read data which has not been written, from the core file.
Severity: Recoverable
Explanation: You have tried to access a machine that is not connected to your network, or which is not on-line.
Resolution: Make sure the machine is connected to the network and is on-line, then try to access it again.
Severity: Fatal
Explanation: This is normally caused by an unexpected error occurring in the network or file-sharing facilities. A corrupted network message also causes this error to be returned.
Resolution: Retry the unsuccessful operation. If the error persists, contact Technical Support who will help you to discover the specific cause of this error.
Severity: Recoverable
Explanation: This is normally given if an incorrect checksum has been received in a communications packet.
Resolution: Your program should continue to execute after you have received this error but results might be undefined.
Severity: Fatal
Explanation: You have tried to open a file which you have previously closed with lock.
Resolution: Recode your program to avoid opening a file which has previously been closed with lock.
Severity: Fatal
Explanation: You have tried to run a program that is incompatible with the current version of either your run-time system, your object file or your COBOL run-time library. For example, your run-time system does not run a program linked using a different object file format or COBOL run-time library.
Resolution: If your object file is incompatible with the current version of either your COBOL run-time library or your run-time system, you should relink with the current version of your COBOL run-time library.
Severity: Recoverable
Explanation: You have either tried to exceed the maximum number of simultaneous record locks per file you can have, or you have exhausted an operating system or network resource, for example dynamic memory.
Resolution: Execute a COMMIT or an UNLOCK operation on the relevant file and you should then be able to continue to run your program. You should try not to retain a record lock for longer than is necessary.
Severity: Fatal
Explanation: You have violated one of the general rules of COBOL programming.
Resolution: Close any files which might be open, execute a STOP RUN statement and then edit your program to avoid such illegal operations.
Severity: Fatal
Explanation: You have tried to animate a program which makes use of the communications module. This cannot be done as both Animator and the communications module need full use of the CRT.
Resolution: You should run your program without the aid of Animator.
Severity: Fatal
Explanation: A device driver is probably missing.
Resolution: Ensure that all communications drivers are loaded before you try to run Communications.
Severity: Fatal
Explanation: The .gnt file is not valid for the host processor.
Resolution: You must resubmit your program to your COBOL system.
Severity: Fatal
Explanation: Either your file header is not correctly formatted, or you are not using a MULTIPLE REEL/UNIT file.
Resolution: You should try to run your program again using a backup copy of the relevant file.
Severity: Recoverable
Explanation: You have tried to exceed your operating system's limit on the number of shared files that you can have open simultaneously. As this figure is operating system dependent, you should consult your Release Notes for details of how many shared files your system permits to be open at any one time.
Resolution: Close some of the open shared files you are no longer accessing and retry the file operation.
Severity: Fatal
Explanation: You have coded your program in such a way that it is trying to execute more than one SORT or MERGE operation at the same time. For example, you might have coded a SORT statement in the input or output procedure of another SORT statement, an operation that is specifically prohibited under the rules of ANSI COBOL.
Resolution: You should recode your program to ensure that it does not execute more than one SORT or MERGE at any one time.
Severity: Fatal
Explanation: You have tried a SORT/MERGE operation which has been unsuccessful for some reason. You might have had too many files open when you tried a SORT/MERGE operation, or the file which you are trying to access might be locked.
Resolution: The action you should take depends on the situation in which it occurs. Check the status of each file (USING/ GIVING) defined in the SORT statement.
Severity: Fatal
Explanation: You have tried a SORT/MERGE operation which has been unsuccessful for some reason. You might have had too many files open when you tried a SORT/MERGE operation, or the file which you are trying to access might be locked.
Resolution: The action you should take depends on the situation in which it occurs. Check the status of each file (USING/ GIVING) defined in the SORT statement.
Severity: Fatal
Explanation: You have tried a SORT/MERGE operation which has been unsuccessful for some reason. You might have had too many files open when you tried a SORT/MERGE operation, or the file which you are trying to access might be locked.
Alternatively, you have set the TMP environment variable to point to a directory that does not exist.
Resolution: The action you should take depends on the situation in which it occurs.
Either set TMP to point to a directory that does exist, or unset TMP.
Severity: Fatal
Explanation: The run-time system cannot locate the root or overlay of a program that is currently loaded in memory.
Alternatively, you have insufficient memory to load your program.
Alternatively, the run-time system could not find enough file handles to open and, therefore, load the code.
Resolution: Either the library that contained the program has been canceled, or the program is no longer available on the program search path. Ensure that the program is available either on disk or on an open library.
Either free some memory, use XM or restructure your application so that it uses less memory.
Increase your operating system file handles limit.
Explanation: Two or more programs define the same external file but with different formats. For example, maximum and minimum record lengths might be different.
Resolution: Make sure that all of your programs define the external file with the same format so that they are consistent. It is useful to have the file definition in a COPY file.
Severity: Fatal
Explanation: Two or more programs are defining the same external data item, but the first loaded program has defined the size smaller than has the second or subsequent loaded program.
Resolution: Make sure that both or all of your programs define the size of the external data item as being the same.
Severity: Fatal
Severity: Recoverable
Explanation: You have tried a SORT or MERGE operation which has USING/ GIVING files which are defined as EXTERNAL. The SORT/ MERGE module does not support USING/ GIVING files defined as EXTERNAL.
Resolution: Recompile your program to use the callable SORT module (EXTSM).
Severity: Fatal
Severity: Fatal
Explanation: Animator has encountered system limits or conflicts resulting in communications errors. Perhaps two logins on the same UNIX system are trying to cross-session animate the same program file.
Resolution: Copy the animated program file to a different directory and try animation.
Severity: Fatal
Explanation: A program you are animating has terminated without following the standard run-time system shut-down process. The termination was probably either initiated by the user or caused by a severe run-time error.
Resolution: Run your program without animation to determine if it runs successfully; if so, animate the program without cross-session or intrasession animation.
Severity: Fatal
Explanation: Animator has encountered system limits in starting your program. The animated program cannot start because of either insufficient memory or too many processes running on the UNIX system.
Resolution: Animate your program when the load on the system has reduced. Run the program without animation to determine if it runs successfully; if so, animate the program without cross-session or intrasession animation. Ask your system administrator to expand the number of process slots and virtual memory page maps.
Severity: Fatal
Explanation: While using Animator you have terminated your program with a keyboard interrupt.