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
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: Recoverable
Explanation: You have tried to open a file directly or indirectly and, although you have not exceeded your system's file limit, something in your system is unable to allocate enough memory space for this operation.
Resolution: Although you can trap this error you must do STOP RUN as soon as it is reported.
Severity: Recoverable
Explanation: You have tried to access a file without opening it first.
Resolution: Open the file with the open mode that you need and try the operation again. As this error implies that your program logic contains a mistake, you might want to terminate the run and recode your program.
Severity: Recoverable
Explanation: You have tried to open a device as a relative or indexed file.
You are trying to execute a device, not a program.
Resolution: Open the device in the correct mode or close any open files, do STOP RUN and recode your program.
The name of your program is recognized by the operating system as a valid device. Rename your program.
Severity: Recoverable
Explanation: A file-name contains an illegal character. This could be any character that is not part of the permitted character set or it could be the system-dependent delimiter, which on most systems is the space.
Resolution: Try the file operation again using the correct file-name.
Severity: Recoverable
Explanation: Devices to which your COBOL program can write are defined by the operating system. You have tried to write to a device that is not defined by your system.
Resolution: Try the operation again using a device name that your system recognizes.
Severity: Recoverable
Explanation: You have tried to WRITE to a file that is open for input only.
Resolution: Close the file and open it with a mode such as I-O, which allows you to write to the file. As this error implies that your program logic contains a mistake, you might want to terminate the run and recode your program.
Severity: Fatal
Explanation: The disk is full.
Resolution: This error can be trapped, but once it has been reported you must do a STOP RUN immediately to terminate your program's run. When your program has terminated, delete any files that you no longer need. Alternatively, if your operating system supports this, put a new disk in a floppy disk drive and redirect your program's file operations to this.
Severity: Recoverable
Explanation: You have tried to read from a file that is open for output only.
Resolution: Close the file and open it with a mode such as I-O, which allows you to read from the file. As this error implies that your program logic contains a mistake, you might want to terminate the run and recode your program.
Severity: Recoverable
Explanation: Either the directory is full, or your program cannot find it.
Resolution: Either delete any files that you no longer need, or if your operating system supports this, put a new disk in a floppy disk drive and redirect your program's file operations to this. Alternatively, specify a different drive or directory for your file operations.
Severity: Recoverable
Explanation: You have tried to open a file that you have declared as an external file, but have not named.
Resolution: Specify the external file-name.
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. If the fact that the file is already open is acceptable to you, 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 have tried to exceed the maximum number of files which you can have open at any one time. This can be a software or an operating system constraint, but you must not violate it.
Resolution: Close some of the open files which you are not currently accessing, and then try to open the relevant file again. You should then be able to continue to run your program.
Depending on your operating system, you might be able to increase the
maximum number of files you are allowed to have open. For example, on DOS,
add the line
to your config.sys file. On Novell, add
the lines
to your
shell.cfg file.
Severity: Recoverable
Explanation: You have tried to exceed the maximum number of indexed files which you can have open at any one time. This can be a software or an operating system restraint, but you must not violate it.
Resolution: Close some of the open indexed files which you are not currently accessing, and then try to open the relevant file again. You should then be able to continue to run your program. (Indexed files count as two files, one for data and one for the index.)
Severity: Recoverable
Explanation: You have tried to exceed the maximum number of device files which you can have open at any one time. This can be a software or an operating system constraint, but you must not violate it.
Resolution: Close some of the open device files which you are not currently accessing, and then try to open the relevant file again. You should then be able to continue to run your program.
Severity: Recoverable
Explanation: You have probably tried to access a record that has had no value moved into it.
Resolution: Although this error is recoverable in the sense that it can be trapped, once it has been reported you must execute a STOP RUN statement immediately and then recode your program to ensure that the COBOL record length is not zero
EOF before EOR or file open in wrong mode
Severity: Recoverable
Explanation: A part record has been found at the end of a file. Consequently your run-time system treats the data file as a record, and not finding a full record, reports this error.
Resolution: Ensure that the record size you give when you read from or WRITE to a file is consistent.
Severity: Recoverable
Explanation: You are trying to do a REWRITE to a file that has not been opened with the correct access mode for this operation.
Resolution: Close the file and reopen it in a mode such as I-O, which allows you to do REWRITE operations on that file. As this error implies that your program logic contains a mistake, you might want to close any open files and then execute a STOP RUN. You can then recode your program to eliminate the logic error.
Severity: Recoverable
Explanation: You have tried to open a file that is assigned to a device or resource (for example, a line printer) that is not available at this time.
Resolution: You can trap the error status returned by open and retry the open at regular intervals until it succeeds.
Severity: Fatal
Explanation: You have tried to WRITE to a directory instead of to a file.
Alternatively, the attributes are not set up correctly to allow you to access a file. That is, it is marked as read-only or you don't have sufficient rights to open it.
Resolution: Recode your program so that it writes to a file and not to a directory.
You need to either change your file access attributes or recode your program so that it does not violate the existing attributes.
Severity: Recoverable
Explanation: The mode in which you are trying to open a file violates the General Rule of COBOL for that type of file; for example you might have opened a line sequential file in the I-O mode.
Resolution: Open the file with a mode that is compatible with that type of file.
Severity: Recoverable
Explanation: The mode in which you are trying to close a file is not possible for that type of file.
Resolution: Close the file with a new access mode which is compatible with that type of file, or execute a STOP RUN statement and recode your program.
Severity: Recoverable
Explanation: You might have performed a read after a WRITE, or there might be either a verification failure or a parity error.
Resolution: In some circumstances this error is fatal, but if it occurs during a read you can trap it and then do a close on the file before executing a STOP RUN statement.
Severity: Fatal
Explanation: You are trying to set up terminal characteristics for a device which is not a terminal.
Resolution: Recode your program.
Severity: Fatal
Explanation: An error has occurred while you are trying to access a disk. This could be the result of a corrupt disk.
Resolution: If you have a corrupt disk try to run your program again using your backup copy.
Severity: Recoverable
Explanation: You are trying to access a device which either is not attached to your machine or if attached is not on-line.
Resolution: Attach the device to your machine and ensure that it is on-line. Repeat the file operation.
Severity: Fatal
Explanation: You have tried a file operation such as WRITE for which insufficient space is available on your disk.
Resolution: When your program has terminated you should delete some of the files or directories on your current logged in disk. Ensure that you delete sufficient files on your disk so that you have enough room to carry out successful file operations.
Severity: Recoverable
Explanation: You have tried to perform a DELETE FD operation on an open file.
Resolution: Close the file before performing the DELETE FD operation.
Severity: Recoverable
Explanation: The file system which you are using is read-only, which effectively means that it is write-protected. You have tried to change a file in some way, for example you might have tried to WRITE to a file or to DELETE information in it.
Resolution: You should abandon your attempt to alter the file unless you can make your own personal copy of it. You should then be able to alter the contents of your copy, but not of the original source.
Severity: Recoverable
Explanation: You are trying an operation on a file but the file's owner has not given you the necessary permission for that operation. You could for example be trying to alter the access modes for a file, which only the file's owner can do.
Resolution: You should abandon your tried file operation unless the file's owner gives you the permission necessary to do the operation you want to carry out.
Severity: Recoverable
Explanation: You have tried to open an indexed file but the number of files that you currently have open is the system limit.
Alternatively, you could be trying to use a process id which does not exist, or which your operating system no longer recognizes.
Resolution: You should close some of the indexed files which you are no longer accessing, and you should then be able to open the file you require.
In this case you must rewrite your code so that it uses a process id which your system recognizes.
Severity: Fatal
Explanation: You have a hardware error of some type. Perhaps you have not put a disk in the relevant drive or you might have tried to WRITE to a disk but the processor detected hardware interface has failed.
Resolution: You should try to correct the fault in your hardware; for example put a disk in the necessary drive.
Severity: Recoverable
Explanation: You are either trying to write to a file which is open for read purposes only, or read a file which is open for write purposes only.
Resolution: You should close the file and reopen using the correct access mode. 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 your program to eliminate the logic error.
Shareable files opened INPUT (read-only) by the COBOL system still require write-permission (from the operating system) to enable temporary locking to take place.
Severity: Recoverable
Explanation: You are trying a file operation which you do not have sufficient permission to achieve. For example you could be trying to write data to a file which has been set up with the read attribute only.
Resolution: If you are the owner of the file you can alter the attributes of the file so that you have the permission needed to effect the particular file operation you were trying. If you are not the owner of the file you cannot to carry out that operation successfully unless you copy the file and make the changes to the copy only. You cannot alter the source file.
Severity: Recoverable
Explanation: You are trying an inappropriate operation on an already existing file.
Resolution: As this error implies that your program logic contains a mistake, you might like to recode your program to eliminate this mistake.
Severity: Fatal
Explanation: Your attempt to access a file has been denied by the operating system. You might have tried to write to a write-protected file or you could have tried to read from an output device.
Resolution: Alter the access permission on the relevant file. Access can be read-only, if you just want to read the contents of the file without making any changes, or it can be read and write in which case you can alter its contents.
Severity: Fatal
Explanation: You have tried to access a disk that is incompatible with the current version of your operating system. This could be because it was created under a previous version of the system or it could have been created under a completely different operating system. You would also receive this error if you tried to load a disk with a name that clashed with a disk that was already loaded.
Resolution: If the error is a result of a clash of names you can rename one of the disks and then you can load both disks together if this is what you want.
Severity: Fatal
Explanation: You have tried to access a file that is not compatible with the structure of files under the current release of your software. This could be because the file was created either under a different operating system or under a previous version of your current system.
Resolution: You should create a new copy of the file which has the correct structure.
Severity: Fatal
Explanation: You have tried to use the additional language variants, but the environment or side file that is required to set up the language either has not been set up correctly, or does not exist, or is invalid.
This might be because you have the LANG environment variable set for use by another system in a format not recognized by this COBOL system.
Resolution: Set up the required environment or side file before you try to run the program again.
Use the COBLANG environment variable to set the locale information for the COBOL system. See the chapter NLS Support in your COBOL System Reference.
Severity: Recoverable
Explanation: Your run-time system does not recognize the control information for an indexed file and as the index has been corrupted in some way the data in the file is no longer accessible by your system. This error is recoverable in the sense that it can be trapped but should you receive it, you can do little except to close any open files and stop your program's run.
Resolution: You should rerun your program using the backup copy of that file. If you have added a great deal of information to the file since you last took a backup you might like to rebuild the file using the Rebuild utility, which reads the data (if this has not been corrupted) and builds a new index for it.
Severity: Recoverable
Explanation:One of the following has occurred:
Resolution: You can trap the error status returned by the write operation, then open the file again.
Severity: Fatal
Explanation: The system has crashed on your program's previous run, while the file was open. Information was probably added to the end of the file, but the directory information was not updated and so that data cannot be accessed by your system. Alternatively, you have copied the indexed file from one disk to another but have copied either only the data part of the file or only the index.
Resolution: If the error is the result of a crash then whether you can access the necessary data or not is entirely system dependent. If, however, it is the result of a faulty copy you should be able to restore the missing part of the file from the .dat or .idx file.
Severity: Fatal
Explanation: The logical file-name is preceded by "%NLS%", but the program which OPENS the file has been compiled without the NLS directive set: the OPEN fails.
Severity: Fatal
Explanation: The NLS control information for a file in your program does not match the same NLS control information in the header of your index file. Alternatively, your index file has become corrupted.
Resolution: Rebuild your index file, or rerun your program using the backup copy of that file. If you have added a great deal of information since you last took a backup, you might want to rebuild the file using a utility that is able to read the data, if it is not corrupt, and build a new index for it.
Severity: Fatal
Explanation: Your system could not find the National Language Support module COBNLSMG.
Alternatively, your system cannot find cobnls.dll (OS/2), cobnls.dle (DOS), or cobnls.dlw (Windows).
Resolution: Ensure that cobnlsmg.gnt is present in either utils.lbr or in a directory on COBDIR, or, if your program is linked, ensure that cobnlsmg.obj is linked in to it.
Ensure that cobnls.dle is present in utils.lbr, or that cobnls.dlw is present in a directory specified in COBDIR, or that cobnls.dll is present on the LIBPATH.
Severity: Fatal
Explanation: The structure of your indexed file contains a fault. You have probably tried to put another entry in the index when there is no room for it.
Alternatively, you have tried to access an old format indexed file, created perhaps using CIS COBOL.
Resolution: If your index has no room for further entries you should reorganize your file.
If you have tried to access an old format indexed file, you can run the Rebuild utility to check the consistency of this indexed file, and to construct a new indexed file if the old one was found to be corrupt. See your COBOL System Reference for details of the Rebuild utility.
Severity: Fatal
Explanation: You are executing a program that is trying to perform a fixed-point divide by zero.
Alternatively, if you have COBFSTAT environment variable set to HOSTSTAT, this could be mainframe file status code "90".
Resolution: Either recode your program so that you can trap the error with an ON SIZE ERROR clause, or run your program without the RTS O switch set, or recompile your program without the CHECKDIV"OSVS" directive set.
Severity: Fatal
Explanation: You have tried to load too many programs simultaneously.
Alternatively, if you have COBFSTAT environment variable set to HOSTSTAT, this could be mainframe file status code "97".
Resolution: Cancel any programs that you are no longer using, or use fewer separate programs.
Severity: Recoverable
Explanation: You have tried to open a file which has already been locked, or opened for output by another user. Alternatively, you have tried to lock or open for output a file which another user already has open.
Resolution: Your program can inform the system operator (if there is one) that it is unable to access this file and should wait until the other user has finished using the file and closes it. You should then be able to continue to run your program.
Severity: Fatal
Explanation: You have tried to add a duplicate key for a key which you have not defined as being able to have duplicates.
Resolution: As this error implies that your program logic contains a mistake, you probably should recode.
Severity: Recoverable
Explanation: You are trying to access an indexed file which you have not opened.
Resolution: Open the file in the relevant access mode and then retry the unsuccessful file operation.
Severity: Recoverable
Explanation: You have tried to access a record which is currently locked by another user.
Resolution: Your program can inform the system operator (if there is one) that the record is currently locked, and you should then wait until the other user has released the lock on that record. You should then be able to access the relevant record. You should not continually retry to gain access to the record without operator intervention, as this could result in your application hanging.
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: Recoverable
Explanation: You are trying to open an indexed file but you have already exhausted the system limit which specifies how many of these files can be opened at any one time.
Resolution: Close some of the open indexed files which you are not currently accessing. You should then be able to open the indexed file which you require and to continue the program run.
Severity: Fatal
Explanation: You are either using a file which has been corrupted, or there is an internal system error.
Resolution: If the disk you are using is corrupt, rerun your program using your backup copy of the disk. If this is not the cause of the error then you should contact Technical Support who will help you discover the cause of your error and how it can be rectified.
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: This is the result of an internal system error.
Resolution: Contact Technical Support who will help you discover the cause of the error and how it can be rectified.
Severity: Fatal
Explanation: This is the result of an internal system error.
Resolution: Contact Technical Support who will help you discover the cause of the error and how it can be rectified.
Severity: Fatal
Explanation: When creating indexed files, the extension .idx is added to the user-defined file-name, and so your file-name must not exceed x-4 characters in length, where x is the maximum length of file-name. See your COBOL System Reference for details.
Resolution: Rename the file with a shorter file-name, that is, one that is less than 10 characters in length.
Severity: Fatal
Explanation: For some reason your system is unable to create a lock file in the /isam directory. One reason for this could be that in its previous run your program terminated abnormally (perhaps due to a power failure) leaving some files locked.
Resolution: You should manually remove all of the files that are still locked from the /isam directory before you can successfully run your program.
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: 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: An error exists in the run-time configuration sidefile accessed via the environment variable COBCONFIG.
Resolution: Check your syntax against your COBOL System Reference. You might have used incorrect syntax, or syntax that is not compatible with the type of RTS tuneable you are configuring (this could include assigning an illegal value to the RTS tuneable).
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: The CALL convention you have specified is not supported.
Resolution: See your COBOL User Guide for a list of supported CALL conventions.
Severity: Fatal