Operating system error code 64

operating system error code 64

Description. Windows error code 64 means: ERROR_NETNAME_DELETED. 64 (0x40). The specified network name is no longer available. perror 13 64 OS error code 13: Permission denied OS error code 64: Machine is not on the network. To obtain the error message for a MySQL Cluster error code. This error appears because the operating system (OS) is outdated. Newer versions of the driver require newer Windows 10 OS builds. Follow these steps.

Operating system error code 64 - useful

perror(1) — Linux manual page


PERROR(1) MariaDB Database System PERROR(1)

NAME         top

perror - explain error codes

SYNOPSIS         top

perror [options] errorcode...

DESCRIPTION         top

For most system errors, MariaDB displays, in addition to an internal text message, the system error code in one of the following styles: message ... (errno: #) message ... (Errcode: #) You can find out what the error code means by examining the documentation for your system or by using the perror utility. perror prints a description for a system error code or for a storage engine (table handler) error code. Invoke perror like this: shell> perror [options] errorcode... Example: shell> perror 13 64 OS error code 13: Permission denied OS error code 64: Machine is not on the network Note that the meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems. perror supports the following options. • --help, --info, -I, -? Display a help message and exit. • --silent, -s Silent mode. Print only the error message. • --verbose, -v Verbose mode. Print error code and message. This is the default behavior. • --version, -V Display version information and exit.

COPYRIGHT         top

Copyright 2007-2008 MySQL AB, 2008-2010 Sun Microsystems, Inc., 2010-2020 MariaDB Foundation This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA or see http://www.gnu.org/licenses/.

SEE ALSO         top

For more information, please refer to the MariaDB Knowledge Base, available online at https://mariadb.com/kb/

AUTHOR         top

MariaDB Foundation (http://www.mariadb.org/).

COLOPHON         top

This page is part of the MariaDB (MariaDB database server) project. Information about the project can be found at ⟨http://mariadb.org/⟩. If you have a bug report for this manual page, see ⟨https://mariadb.com/kb/en/mariadb/reporting-bugs/⟩. This page was obtained from the project's upstream Git repository ⟨https://github.com/MariaDB/server⟩ on 2021-08-27. (At that time, the date of the most recent commit that was found in the repository was 2021-08-26.) If you discover any rendering problems in this HTML version of the page, or you believe there is a better or more up-to-date source for the page, or you have corrections or improvements to the information in this COLOPHON (which is not part of the original manual page), send a mail to [email protected]

Chapter 4: Run-time System Error Messages

PreviousCode Generation Error MessagesFile Status CodesNext

These messages are output by the run-time system (RTS), and so can be produced while you are compiling, debugging, or running your program. For each error message, the error message number, and its text and severity, is listed, along with an explanation of the error or problem that caused the message, and advice on how to prevent the error.

4.1 Format of Messages

Run-time system messages are displayed in the format:

action error: file 'file-name' error code:yyy, pc=xxxxxxxx, call=0, seg=ssnnnmessage-text

where the variables are:

What the run-time system was doing at the time of the error. For example, execution, I/O, load or write.
The name of the file on which the run-time system was operating
Either the run-time system error number or, if the error is caused by an I/O operation, the file status value. If the latter, the file status mappings currently on force are also displayed.
The position of the program counter, in hexadecimal; this can be related back to the source program using the REF Compiler directive.
The number of the segment being executed (0 for ROOT)
The error number
The error message
One of:


4.2 Types of Error

There are two types of run-time error; exceptions and I/O errors. I/O errors are either fatal or recoverable. Recoverable errors are reported by the operating system; this enables you to trap them and take steps to recover from them if at all possible. Exceptions are fatal errors which are not reported and so cannot be trapped.

4.2.1 Exceptions

These are fatal errors covering conditions such as arithmetic overflow, too many levels of PERFORM nesting, and subscript out of range.

4.2.2 I/O Errors

These are either fatal or recoverable errors, that cause one of the following to take place:

  • If you did not specify a FILE STATUS clause for the file on which the error occurred then the error is treated as fatal. That is, the program terminates immediately with the RTS displaying its own message on the console in the format given above. See the chapter File Status Codes in your File Handling book for details of how to define the file status.

  • If you specified a FILE STATUS clause for the relevant file then the value "9" (which indicates that an operating system error message has been received) is placed into status-key-1 and the operating system or RTS error number is placed into status key 2.

You must examine status key 1 after each file operation to ensure that the operation has been carried out successfully. 0 in status key 1 indicates the successful completion of a file operation; any other value indicates an error condition of some type.

If an error condition is reported, the action which your program then takes is entirely your responsibility. If your program does not terminate when an error is reported, its subsequent behavior might not be as you would expect.

4.2.3 Fatal Errors

Fatal errors cause a message to be output to the console, and once this error message has been displayed your program terminates immediately.

Although you cannot recover from such an error during the run of your program, once it has terminated you might be able to take steps to rectify the conditions which caused the error to occur. The list of run-time system error messages gives hints on how this might be achieved for individual errors.

4.2.4 Recoverable Errors

You can trap recoverable errors in your program, but the action you take when one of these errors is received is your responsibility.

4.2.5 Error Handling

Having received a file error you can deal with it in one of many ways. You might want your program to display its own general error message, close any open files (if this is possible) and terminate. This should enable you to save any data which you have already written to the files. This data could be lost if you do not trap the error.

Should you want to recover from an error and to continue to run your program, code your program in such a way as to take action should a particular error be reported. For example, if you receive a "file not found" error then your program could prompt you to insert a disk containing the required file into a specified drive, if your operating system supports this.

Hints on how to recover from specific errors are given later in this chapter but you will be able to follow these hints only if you have coded your program in such a way as to be able to take advantage of them.

You might want to code your program to handle recoverable errors as follows:

  • Use AT END (which checks for a value of 1 in status key 1), or INVALID KEY (which checks for a value of 2 in status key 1) clauses where appropriate. You do not need to declare FILE STATUS items in this case.

  • Use Declaratives which check that status key 1 is not equal to 0 (that is the operation was not completed successfully) for all file-operations that have no AT END or INVALID KEY clauses. You should declare FILE STATUS items in this case.

  • Declare FILE STATUS items and check for a value in status key 1 of either 9 which indicates an RTS error, or nonzero which shows that the file operation has not been successfully completed. You should explicitly check the status byte after each file operation.

  • Do not use the FILE STATUS clause or AT END or INVALID KEY, in which case the RTS terminates immediately should any file error be received. In this situation all error messages are treated as though they were fatal with the relevant RTS error message being output to the console.

4.2.6 Return-code Values

The run-time system always returns a value to the operating system when a COBOL program terminates. If the program terminates normally, the value is taken from the program's special register RETURN-CODE If the run-time system terminates the program because an unrecoverable error has occurred or because it has received a message from the operating system to quit immediately, the value returned depends on the operating system as described below.

Windows::
The value returned is 32 for a run-time system error and 16 for a quit interrupt when running under Windows. A keyboard quit interrupt is generated when the user presses Ctrl + Break. Use the command with the parameter to test the returned value, as shown in the following batch file fragment:

run myprog if errorlevel 32 goto rts_error if errorlevel 16 goto rts_interrupt

UNIX:
The run-time system returns a value of -1 for a run-time system error and -2 for an abnormal termination when the keyboard interrupt key (for example, Ctrl-C) is pressed or the SIGTERM or SIGHUP signals are received. Typically, many UNIX implementations translate the value of -1 to the unsigned value 255, and the value -2 to the unsigned value 254. You can configure the run-time system to ignore ignore keyboard interrupts by using the run-time switch i (see the chapter Descriptions of Run-time Switches in your Server Express User's Guide for further details). Use the Bourne shell special parameter $ to obtain the value returned to the operating system, as shown in the following shell script fragment:

cobrun prog if test $? -eq 255 then echo "Abnormal termination" fi

See your operating system documentation for further details of how interrupts can be generated and how to handle values returned by a program.

4.3 Key to RTS Error Messages

These messages are output by the run-time system (RTS), and so can be produced while you are compiling, debugging, or running your program. When you select an error message number, its text and severity is listed, along with an explanation of the error or problem that caused the message, and advice on how to prevent the error.

There are two types of run-time error:

FatalA message is sent to the screen and the program terminates immediately.
RecoverableThe error is reported to the program. You can trap these errors in your program, but often they are the result of an error in your program's logic. If the program does not trap the error a message is sent to the screen and the program terminates immediately.

4.4 List of RTS Error Messages


001 Insufficient buffer space (Recoverable)

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.


002 File not open when access attempted (Recoverable)

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.


003 Serial mode error (Recoverable)

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.


004 Illegal file name (Recoverable)

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.


005 Illegal device specification (Recoverable)

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.


006 Attempt to write to a file opened for INPUT (Recoverable)

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.


007 Disk space exhausted (Fatal)

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.


008 Attempt to input from a file opened for OUTPUT (Recoverable)

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.


009 No room in directory (Recoverable)

The system cannot write to the specified directory for one of the following reasons:

  • The directory does not exist

  • The directory is full

  • Your program cannot find the directory

Resolution:
Create the directory if it doesn't exist. If the directory is full, 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 it. Alternatively, specify a different drive or directory for your file operations.


010 File name not supplied (Recoverable)

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.


011 Process limit reached (Fatal)

One of the following has occurred:

  • The run-time system cannot create a new process as the operating system limit on the total number of processes per user or system-wide would be exceeded.

  • Insufficient memory is available to complete the operation.

Resolution:
Terminate any processes that you are no longer using, or make more memory available.

Your operating system might enable you to increase the maximum number of processes allowed. Refer to your operating system documentation for further information.


012 Attempt to open a file which is already open (Recoverable)

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.


013 File not found (Recoverable)

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.


014 Too many files open simultaneously (Recoverable)

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.


015 Too many indexed files open (Recoverable)

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.)


016 Too many device files open (Recoverable)

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.


017 Record error: probably zero length (Recoverable)

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.


018 Read part record error: EOF before EOR or file open in wrong mode (Recoverable)

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.


019 Rewrite error: open mode or access mode wrong (Recoverable)

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.


020 Device or resource busy (Recoverable)

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.


021 File is a directory (Fatal)

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.


022 Illegal or impossible access mode for OPEN (Recoverable)

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.


023 Illegal or impossible access mode for CLOSE (Recoverable)

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.


024 Disk input-output error (Recoverable)

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.


025 Operating system data error (Fatal)

You are trying to set up terminal characteristics for a device which is not a terminal.

Resolution:
Recode your program.


026 Block I-O error (Fatal)

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.


027 Device not available (Recoverable)

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.


028 No space on device (Fatal)

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.


029 Attempt to delete open file (Recoverable)

You have tried to perform a DELETE FD operation on an open file.

Resolution:
Close the file before performing the DELETE FD operation.


030 File system is read-only (Recoverable)

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.


031 Not owner of file (Recoverable)

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.


032 Too many indexed files, or no such process (Recoverable)

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.


033 Physical I-O error (Fatal)

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.


034 Incorrect mode or file descriptor (Recoverable)

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.


035 Attempt to access a file with incorrect permission (Recoverable)

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.


036 File already exists (Recoverable)

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.


037 File access denied (Fatal)

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.


038 Disk not compatible (Fatal)

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.


039 File not compatible (Fatal)

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.


040 National Language initialization not set up correctly (Fatal)

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.


041 Corrupt index file (Recoverable)

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.


042 Attempt to write on broken pipe (Recoverable)

One of the following has occurred:

  • Your program has created a process as a result of a DD_ logical file-name mapping assignment (for example, the process might be a line printer spooler). The process was not created properly, or has ended prematurely. This error occurs when your program tries to write to the process.

  • Your application has terminated abnormally or prematurely, thus breaking the pipe.

Resolution:
You can trap the error status returned by the write operation, then open the file again.


043 File information missing for indexed file (Fatal)

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.


044 Attempt to OPEN an NLS file in a non-NLS program (Fatal)

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.


045 Attempt to OPEN an NLS file using incompatible language definition (Fatal)

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.


047 Indexed structure overflow (Fatal)

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. This may be because you have reached the maximum number of duplicate keys.

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 either reorganize your file or convert it to IDXFORMAT"4" using Rebuild, to allow a greater number of duplicate keys.

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.


048 Attempt to divide by zero (Fatal)

You are executing a program that is trying to perform a fixed-point divide by zero.

Resolution:
Recode your program so that you can trap the error with an ON SIZE ERROR clause


055 Routine table overflow (Fatal)

You have tried to load too many programs simultaneously.

Resolution:
Cancel any programs that you are no longer using, or use fewer separate programs.


065 File locked (Recoverable)

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.


066 Attempt to add duplicate record key to indexed file (Fatal)

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.


067 Indexed file not open (Recoverable)

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.


068 Record locked (Recoverable)

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.


069 Illegal argument to isam module (Fatal)

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.


070 Too many indexed files open (Recoverable)

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.


071 Bad indexed file format (Fatal)

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.


072 End of indexed file (Fatal)

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.


073 No record found in indexed file (Fatal)

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.


074 No current record in indexed file (Fatal)

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.


075 Indexed data file name too long (Fatal)

When creating indexed files, the extension .idx is added to the user-defined file-name, so your file-name must not exceed x-4 characters in length, where x is the maximum length of file-name.

Resolution:
Rename the file with a shorter file-name, that is, one that is less than 10 characters in length.


076 Can't create lock file in /isam directory (Fatal)

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.


077 Internal ISAM module error (Fatal)

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.


078 Illegal key description in indexed file (Fatal)

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.


079 COBCONFIG syntax error (Fatal)

An error exists in the run-time configuration sidefile accessed via the environment variable COBCONFIG.

Resolution:
Check the syntax of the entries in the configuration file. You might have used incorrect syntax, or syntax that is not compatible with the type of run-time tuneable you are configuring (this could include assigning an illegal value to the tuneable).

See Also:
The chapter Run-time Configuration in your Server Express User's Guide.


081 Key already exists in indexed file (Fatal)

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.


082 CALL convention not supported (Fatal)

The CALL convention you have specified is not supported.

Resolution:
Change the convention defined in the special-names paragraph to one of the supported CALL conventions.


086 Remote file system failure (Fatal)

099 Illegal operation in SORT/MERGE module (Fatal)

A SORT or MERGE module has received a RELEASE operation outside the Input procedure, or a RETURN operation either outside the Output procedure, or before the Input procedure has terminated correctly.

Resolution:
Recode your program so that RELEASE and RETURN operations are issued by the appropriate procedures.


100 Invalid file operation (Fatal)

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.


101 Illegal operation on an indexed file (Fatal)

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.


102 Sequential file with non-integral number of records (Fatal)

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.


103 Parameter cannot be passed BY VALUE (Fatal)

104 Null file name used in a file operation (Fatal)

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.


105 Memory allocation error (Fatal)

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.


106 Dictionary error (Fatal)

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.


107 Operation not implemented in this run-time system (Fatal)

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.


108 Failure to initialize data division (Fatal)

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.


109 Invalid checksum in run-time system (Recoverable)

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.


110 Generated code not supported by this RTS (Fatal)

Resolution:
Contact Technical Support who will help you to discover the cause of the error and how it can be rectified.


111 Incompatible Class Library and Run-Time Environment versions (Fatal)

The version numbers for these components do not match.

Resolution:
Check that you have fully installed both the Class Library and the Run-Time Environment from the same version of Object COBOL. If you have more than one version installed, check that your PATH, LIBPATH, and COBDIR environment variables specify an appropriate path for the version you are using.


112 Unable to locate/access the required security key (Recoverable)

The run-time system cannot locate or cannot access the coded security key (dongle) that is required to execute this application.

Resolution:
Connect the security key that was supplied with your COBOL system to the parallel port of your computer, then re-run the application.


114 Attempt to access item beyond bounds of memory (Fatal)

Memory access violation has been detected by your operating system.

See Also:
The chapter Handling Protection Violation Errors in your Programmer's Guide to Writing Programs.


115 Unexpected signal (Fatal)

A signal the run-time system was not expecting has been caught.


116 Cannot allocate memory (Fatal)

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.


117 Bad collating sequence (Fatal)

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.


118 Symbol not found (Fatal)

You have attempted to reference a name that has not been defined.


119 Name is not unique (Fatal)

The run-time system has detected a name (for example, data item, entry point or module name) which is already defined.

OO programs can also cause this error for either of the following reasons:

  • You have defined the same method-name twice in a single object

  • You have defined the same class name with different filenames in different programs, in the Class-Control paragraph. Filename matching is case-sensitive; class filenames should always be coded in lower-case.

Resolution:
You can recode your application to remove the naming duplication.

See Also:
The description of the E run-time switch in the chapter Descriptions of Run-time Switches in your Server Express User's Guide.


120 Symbol string table of zero size (Fatal)

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.


121 Symbol is not in TEXT section (Fatal)

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.


122 coblongjmp() called from below level of cobsetjmp() (Fatal)

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 the corresponding cobsetjmp() or cobsavenv().

Resolution:
Check and correct the logic of your program, and then resubmit it to your COBOL system.


123 Unknown relocation type (Fatal)

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.


124 Communications failure during I/O request to the Fileshare Server (Fatal)

See Also:
Your Fileshare User's Guide.


125 All locks/ current transactions canceled due to exceeding time limit

See Also:
Your Fileshare User's Guide.


126 Record size exceeds system limit (Fatal)

127 coblongjmp() called from a different thread to cobsetjmp() (Fatal)

You have called coblongjmp() in a different thread from the corresponding call to cobsetjmp(). coblongjmp() must be called from the same thread as the corresponding call to cobsetjmp().

Resolution:
Check and correct the logic of your program, then resubmit it to your COBOL system.


129 Attempt to access record zero of relative file (Recoverable)

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.


135 File not found (Recoverable)

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.


136 Corrupt or invalid executable file (Fatal)

An attempt was made to execute a .gnt file or a library file that is not valid. The file might be corrupted or truncated.

Resolution:
Recompile the source code or recreate the library file, ensuring that it is processed without errors.


137 Illegal device specification - not mass storage

138 File closed with lock - cannot be opened (Recoverable)

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.


139 Record length or key data inconsistency (Recoverable)

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.


141 File already open - cannot be opened (Recoverable)

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.


142 File not open - cannot be closed (Recoverable)

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.


143 Rewrite/delete in sequential mode not preceded by successful read (Recoverable)

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.


144 Boundary violation (Recoverable)

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.


146 No current record defined for sequential read (Recoverable)

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.


147 Wrong open mode or access mode for read/start (Recoverable)

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.


148 Wrong open mode or access mode for write (Recoverable)

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.


149 Wrong open mode or access mode for rewrite/delete (Recoverable)

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.


151 Random read on sequential file (Recoverable)

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.


152 REWRITE on file not opened I-O (Recoverable)

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.


153 Subscript out of range (Fatal)

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.


154 PERFORM nested too deeply (Fatal)

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 recode your program to ensure that the GO TO in question jumps to an EXIT statement at the end of the PERFORM's range.


155 Illegal command line (Fatal)

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.


156 Too many parentheses in compute statement (Fatal)

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.


157 Not enough program memory: object file too large to load (Recoverable)

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.


158 Attempt to REWRITE to a line-sequential file (Recoverable)

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.


159 Malformed line-sequential file (Recoverable)

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.


160 Overlay loading error (Recoverable)

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.


161 Illegal intermediate code (Fatal)

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.


162 Arithmetic overflow or underflow (Fatal)

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.


163 Illegal character in numeric field (Fatal)

The contents of a numeric or numeric edited field are inconsistent with the picture definition of that field.

Resolution:
You must adjust your code so that no invalid data is used.


164 Run-Time subprogram not found (Fatal)

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.


165 Version number incompatibility (Fatal)

You have tried to:

  • Run a program that has intermediate code which has been produced on a version of your COBOL system that is incompatible with the run-time system you are using. Your run-time system, therefore, cannot execute correctly any generated code you are producing or have already produced from this intermediate code.

  • Execute a file which is not in your COBOL system's intermediate or generated code.

  • Load a module whose format is not valid for the Win32 platform.

166 Recursive COBOL CALL is illegal (Fatal)

You have tried to call a COBOL module that is already active.

Resolution:
You should recode your program.


167 Too many USING items (Fatal)

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.


168 Stack overflow (Fatal)

You have nested a PERFORM statement or a series of CALL statements too deeply.

Resolution:
Edit your program to reduce the number of levels in the nested PERFORM or CALL statement.


169 Illegal configuration information (Fatal)

You have tried an operation for which your machine is not configured; the most likely cause of this is incorrect configuration of Adis or the file handler.

Resolution:
Check the configuration of Adis or the file handler.


170 System program not found (Fatal)

A system program, for example Adis or Mffh, is not present.

Resolution:
Ensure that all the system programs are available and copy those which are not currently present using. Once all the necessary system programs are available you can run your program.


171 Japanese operations illegal with this RTS (Fatal)

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.


173 Called program file not found in drive/directory (Fatal)

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, or to send a message to a class which cannot be loaded.

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.

If the error was caused by a class which could not be loaded, find out whether or not the filename for the class (listed in the Class-Control paragraph) is a separate executable file, or contained in a .dll or .lbr file. If it is a separate executable file, the resolution is as above. If it is part of a .dll or .lbr file, ensure that the containing file has been loaded with a CALL statement before sending messages to any of the classes. If the program not found is P2emgr, you need to load the GUI Class Library, with a CALL "APIGUI" statement.

See Also:
The chapter Micro Focus Environment Variables in your Server Express User's Guide.


174 Imported file not found (Fatal)

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.


175 Attempt to run intermediate code program which had severe errors in it (Fatal)

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, the debugger reports this error and enables you to continue to run the program.

See Also:
The description of the E run-time switch in the chapter Descriptions of Run-time Switches in your Server Express User's Guide.


176 Illegal intersegment reference (Fatal)

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.


177 Attempt to cancel program failed (Fatal)

You have tried to remove a currently executing program or its parents or grandparents, from memory.

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.


179 Error during chain (program not found) (Fatal)

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 include the directory or drive on which the file is present when your program calls it.


180 End-of-file marker error (Fatal)

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.


181 Invalid parameter error (Fatal)

A parameter which you have used is not one which is recognized by your system.

Resolution:
Revise your code to contain a parameter which is known by your system.


182 Console input or console output open in wrong direction (Fatal)

You are either trying to read input from the screen or write to the keyboard.

Resolution:
You should recode your program.


183 Attempt to open line sequential file for I-O (Fatal)

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.


184 ACCEPT/DISPLAY I-O error (Fatal)

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.


185 File malformed (Recoverable)

186 Attempt to open stdin, stdout or stderr with incorrect mode (Recoverable)

You have tried to open either a standard input file with output mode, or some other file in an incorrect mode.


188 Filename too large (Fatal)

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.


189 Intermediate code load error (Fatal)

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.


190 Too many arguments to CALL (Fatal)

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.


191 Terminal type not defined (Fatal)

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.


192 Required terminal capability description missing (Fatal)

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.


193 Error in variable length count (Fatal)

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.


194 File size too large (Fatal)

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.


195 DELETE/REWRITE not preceded by a read (Fatal)

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.


196 Record number too large in relative or indexed file (Fatal)

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.


197 Screen handling system initialization error (Fatal)

This error can be caused by one of the following:

  • Your display adapter is in the wrong mode.

  • Your screen handling interface has not been correctly initialized because your terminal does not have the required capabilities.

  • Memory has been incorrectly allocated.

Resolution:
The monitor must be in alphanumeric display mode rather than graphics display mode.


198 Load failure (Fatal)

The system cannot load a program module or, in a multi-threading program, start a new thread.

A CALL statement has failed because:

  • In the case of a DLL, the specified entry point does not exist in the file

  • In the case of an .int or .gnt file, the file has been corrupted

  • In the case of a call of the form $PROG, name mapping has failed

  • In the case of a call-by-number library routine (CALL data-name, where data-name is a pic x with value greater than x'80'), the routine does not exist

Any call or attempt to start a thread can fail where internal structures have been corrupted; for example, by a protection violation.

A statement of the form SET PROCEDURE POINTER TO ENTRY entry-point has failed because the entry point cannot be found on disk or in the current run-unit.

Rarely, this error can be caused by a CALL statement failing because of insufficient available memory or because the run-time system version is too old.

Resolution:
Check that the target of your call exists and has not been corrupted.

Test that a procedure pointer is valid before using it by including code of the form:

set bad-pointer to entry 'just-not-there-ever' ... set procedure-pointer to entry 'myentrypoint' if procedure-pointer = bad-pointer display error end-if
199 Operating System error code lies outside expected range (Fatal)

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.


200 Run-time system internal logic error (Fatal)

The amount of memory available on your machine is so low that not even the run-time system can be fully loaded.

Alternatively, your run-time system has stopped as a result of an internal logic error from which you cannot recover.

Resolution:
Free some memory and then you should be able to run your program successfully.

Contact Technical Support who will help you to discover the cause of the error.


201 I-O error in paging system (Fatal)

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.


203 CALL parameter not supplied (Fatal)

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.


206 Reading unwritten data from memory (Fatal)

You are trying to read data which has not been written, from the core file.


207 Machine does not exist (Recoverable)

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.


208 Error in multi-user system (Fatal)

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.


209 Network communication error (Recoverable)

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.


210 File is closed with lock (Fatal)

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.


211 Program not executable by Run-Time System (Fatal)

An attempt was made to run a program that is incompatible with the currently-specified run-time system. For example, system executable, shared library, and callable shared object files that have been linked using older COBOL systems could be incompatible.

On dual 32-bit/64-bit COBOL systems, all code must be compiled and linked using the same word length. A 64-bit run-time system does not run programs compiled and/or linked on 32-bit platforms or in 32-bit mode. Similarly, a 32-bit run-time system does not run programs compiled and/or linked on 64-bit platforms in 64-bit mode.

Resolution:
Recompile and/or relink your program so that it is compatible with the current run-time system.


213 Too many locks (Recoverable)

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.


214 GO TO has not been ALTERed (Fatal)

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.


215 Cannot ANIMATE a program running COMMUNICATIONS (Fatal)

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.


216 Cannot initialize the named communications device (Fatal)

A device driver is probably missing.

Resolution:
Ensure that all communications drivers are loaded before you try to run Communications.


217 Incompatible host for native code file (Fatal)

The .gnt file is not valid for the host processor.

Resolution:
You must resubmit your program to your COBOL system.


218 Malformed MULTIPLE REEL/UNIT file (Fatal)

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.


219 Operating system shared file limit exceeded (Recoverable)

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.


220 Attempt to execute more than one SORT or MERGE simultaneously (Fatal)

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.


221 SORT/MERGE error: see status keys (Fatal)

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.


222 SORT/MERGE error: see status keys (Fatal)

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.


223 SORT/MERGE error: see status keys (Fatal)

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.


224 External Language Initialization failure

225 Dynamic load error - program component missing (Fatal)

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 or restructure your application so that it uses less memory.

Increase your operating system file handles limit.


226 EXTERNAL file definition inconsistent

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.


227 EXTERNAL data definition inconsistent (Fatal)

Two or more programs are defining the same external data item, but the first loaded program has defined the size differently from 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.


228 Could not allocate memory for EXTERNAL item (Fatal)

229 SORT/MERGE module does not support EXTERNAL using/giving files (Recoverable)

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).


235 Error in animator communications channel (Fatal)

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.


236 Animated program has terminated unexpectedly (Fatal)

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.


237 Unable to initialize animated process (Fatal)

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.


238 STOP RUN encountered during GNT animation (Informational)

Animator has encountered a STOP RUN statement while animating your .gnt code program.

Resolution:
Step or Zoom the animated program, and Animator will terminate the program and its current session.


239 Shared run-time system initialization failure (Informational)

You are calling a COBOL module from a non-COBOL program, and have not initialized the shared run-time system.

Resolution:
Ensure that your application calls the cobinit() function before executing any COBOL modules. See the chapter Mixed-language Programming in your Programmer's Guide to Writing Programs for more information about the cobinit() function.


240 Object reference not valid (Fatal)

You have tried to use an object reference that contains an incorrect or non-existent object handle.

Resolution:
Ensure that the object reference uses the correct object handle, and that your program has not previously destroyed the object by sending it a Finalize message.


241 Cannot instantiate an abstract class (Fatal)

You have tried to create an instance of a class that has been declared ABSTRACT. Such classes cannot be instantiated.

Resolution:
Ensure that you have specified the correct class name. Check to see if there is a subclass that you should use instead.


242 Could not resolve DoesNotUnderstand message (Fatal)

The run-time system could not resolve the DoesNotUnderstand message. This is usually because you have defined a class in such a way that this method cannot be found.

Resolution:
Check the logic in your program to ensure that it invokes only methods that are supported by the object, or ensure that the object supports the DoesNotUnderstand method.


243 Class could not be loaded (Fatal)

An attempt to load an object class has failed because the class does not contain a valid Class-Control section, or because the class is not defined correctly.

Resolution:
Check the definition of the class.


254 Keyboard interrupt to ANIMATOR during ACCEPT (Fatal)

While using Animator you have terminated your program with a keyboard interrupt.

PreviousCode Generation Error MessagesFile Status CodesNext

Backup Failure: Operating system error 64

Hello,

I am having a problem creating backups for a database.  I am using the Backup Task in SSIS and executing the SSIS package against a SQL Server 2000 database.  Sometimes the backup is successful, but recently the failure rate has increased with the following messages listed in the log:

[Execute SQL Task] Error: Executing the query "BACKUP DATABASE [Galaxy]

TO  DISK = N'\\mindata02\Data_D\DEVSQL6\Galaxy\Galaxy_backup_200706070927.bak'

WITH NOFORMAT, NOINIT,  NAME = N'Galaxy_backup_20070607092724', SKIP, REWIND, NOUNLOAD, 

STATS = 10 " failed with the following error: "BACKUP DATABASE is terminating abnormally. 10 percent backed up.

20 percent backed up. 30 percent backed up. 40 percent backed up. 50 percent backed up. 60 percent backed up.

70 percent backed up. 80 percent backed up. 90 percent backed up. Processed 4503024 pages for database

'Galaxy', file 'Galaxy_Data' on file 1. Processed 9360 pages for database 'Galaxy', file 'Galaxy_IDX' on file 1.

100 percent backed up. Processed 59228 pages for database 'Galaxy', file 'Galaxy_Log' on file 1.".

Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly,

or connection not established correctly.

Message

BackupDiskFile::RequestDurableMedia:  failure on backup device

'\\mindata02\Data_D\DEVSQL6\Galaxy\Galaxy_backup_200706070927.bak'.

Operating system error 64(The specified network name is no longer available.).

If anyone has encountered the Operating System Error 64(The specified network name is no longer available) or Operating System Error 59(An unexpected network error arrived) and has some recommendations it would be greatly appreciated.  Thanks in advance for the help.

 

How to Fix Error 64 “The specified network name is no longer available”

In this article we show possible fixes for Windows error 64 “The specified network name is no longer available”,

which may pop up when large network I/O is performed and appears to affect only certain kinds of devices, for example, Linux-based NAS devices during lengthy backups.

In the network adapter settings of the sending machine (or both machines), disable all of the following options, if they exist:

Large Receive Offload Large Send Offload IPv4 Checksum Offload TCP Checksum Offload

In addition, you could locate the following key in the registry and set it to 1

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters\DisableTaskOffload

The above key disables the TCP Chimney (TCP Offload). Setting it to 0 enables it again.

BackupChain Features

As a Windows Server backup software, BackupChain offers several network backup and NAS backup features that automate backups over the network. You can also set up a cloud backup system or use a server for remote backup purposes at your choice.
Another great application of BackupChain is live virtual machine backup. You can backup a VDHX while running and take an online backup using file versioning even over FTP. You will find that whether you backup over FTP, the network, or to a local disk, the unified user interface offers the same features for all targets.
Free Download

See also

  • Hyper-V Backup Software for Microsoft Hyper-V: BackupChain
  • FTP Backup Software with Incremental: Upload Only Changes
  • BackupChain Backup Software Rewards for MSPs and Users

  • Backup Software Without Compression Option: As-Is File Backup

  • Version Backup Software with File Versioning

  • Hyper-V Backup to NAS: Synology, Qnap, Netgear, Drobo, Buffalo

  • BackupChain v2.4.531 Released!

  • NAS Backup Software for QNAP, Buffalo, Drobo, and Synology

  • List of 12 Virtual Backup Software Vendors

  • Backup Software with Deduplication for Data, VM, Database Backup

  • Incremental Backup

  • Differential Backup

  • RAID Backup Software for RAID Array Backup (0, 1, 5, 10)

  • How to Fix Hyper-V Backup Errors

Operating System Error Codes

NumberError CodeDescription1EPERMOperation not permitted2ENOENTNo such file or directory3ESRCHNo such process4EINTRInterrupted system call5EIOI/O error6ENXIONo such device or address7E2BIGArgument list too long8ENOEXECExec format error9EBADFBad file number10ECHILDNo child processes11EAGAINTry again12ENOMEMOut of memory13EACCESPermission denied14EFAULTBad address15ENOTBLKBlock device required16EBUSYDevice or resource busy17EEXISTFile exists18EXDEVCross-device link19ENODEVNo such device20ENOTDIRNot a directory21EISDIRIs a directory22EINVALInvalid argument23ENFILEFile table overflow24EMFILEToo many open files25ENOTTYNot a typewriter26ETXTBSYText file busy27EFBIGFile too large28ENOSPCNo space left on device29ESPIPEIllegal seek30EROFSRead-only file system31EMLINKToo many links32EPIPEBroken pipe33EDOMMath argument out of domain of func34ERANGEMath result not representable35EDEADLKResource deadlock would occur36ENAMETOOLONGFile name too long37ENOLCKNo record locks available38ENOSYSFunction not implemented39ENOTEMPTYDirectory not empty40ELOOPToo many symbolic links encountered42ENOMSGNo message of desired type43EIDRMIdentifier removed44ECHRNGChannel number out of range45EL2NSYNCLevel 2 not synchronized46EL3HLTLevel 3 halted47EL3RSTLevel 3 reset48ELNRNGLink number out of range49EUNATCHProtocol driver not attached50ENOCSINo CSI structure available51EL2HLTLevel 2 halted52EBADEInvalid exchange53EBADRInvalid request descriptor54EXFULLExchange full55ENOANONo anode56EBADRQCInvalid request code57EBADSLTInvalid slot59EBFONTBad font file format60ENOSTRDevice not a stream61ENODATANo data available62ETIMETimer expired63ENOSROut of streams resources64ENONETMachine is not on the network65ENOPKGPackage not installed66EREMOTEObject is remote67ENOLINKLink has been severed68EADVAdvertise error69ESRMNTSrmount error70ECOMMCommunication error on send71EPROTOProtocol error72EMULTIHOPMultihop attempted73EDOTDOTRFS specific error74EBADMSGNot a data message75EOVERFLOWValue too large for defined data type76ENOTUNIQName not unique on network77EBADFDFile descriptor in bad state78EREMCHGRemote address changed79ELIBACCCan not access a needed shared library80ELIBBADAccessing a corrupted shared library81ELIBSCN.lib section in a.out corrupted82ELIBMAXAttempting to link in too many shared libraries83ELIBEXECCannot exec a shared library directly84EILSEQIllegal byte sequence85ERESTARTInterrupted system call should be restarted86ESTRPIPEStreams pipe error87EUSERSToo many users88ENOTSOCKSocket operation on non-socket89EDESTADDRREQDestination address required90EMSGSIZEMessage too long91EPROTOTYPEProtocol wrong type for socket92ENOPROTOOPTProtocol not available93EPROTONOSUPPORTProtocol not supported94ESOCKTNOSUPPORTSocket type not supported95EOPNOTSUPPOperation not supported on transport endpoint96EPFNOSUPPORTProtocol family not supported97EAFNOSUPPORTAddress family not supported by protocol98EADDRINUSEAddress already in use99EADDRNOTAVAILCannot assign requested address100ENETDOWNNetwork is down101ENETUNREACHNetwork is unreachable102ENETRESETNetwork dropped connection because of reset103ECONNABORTEDSoftware caused connection abort104ECONNRESETConnection reset by peer105ENOBUFSNo buffer space available106EISCONNTransport endpoint is already connected107ENOTCONNTransport endpoint is not connected108ESHUTDOWNCannot send after transport endpoint shutdown109ETOOMANYREFSToo many references: cannot splice110ETIMEDOUTConnection timed out111ECONNREFUSEDConnection refused112EHOSTDOWNHost is down113EHOSTUNREACHNo route to host114EALREADYOperation already in progress115EINPROGRESSOperation now in progress116ESTALEStale NFS file handle117EUCLEANStructure needs cleaning118ENOTNAMNot a XENIX named type file119ENAVAILNo XENIX semaphores available120EISNAMIs a named type file121EREMOTEIORemote I/O error122EDQUOTQuota exceeded123ENOMEDIUMNo medium found124EMEDIUMTYPEWrong medium type125ECANCELEDOperation Canceled126ENOKEYRequired key not available127EKEYEXPIREDKey has expired128EKEYREVOKEDKey has been revoked129EKEYREJECTEDKey was rejected by service130EOWNERDEADOwner died131ENOTRECOVERABLEState not recoverable

4.8.1. perror — Explain Error Codes

For most system errors, MySQL displays, in addition to an internal text message, the system error code in one of the following styles:

message ... (errno: #) message ... (Errcode: #)

You can find out what the error code means by examining the documentation for your system or by using the perror utility.

perror prints a description for a system error code or for a storage engine (table handler) error code.

Invoke perror like this:

shell>

Example:

shell> OS error code 13: Permission denied OS error code 64: Machine is not on the network

To obtain the error message for a MySQL Cluster error code, invoke perror with the option:

shell>

Note that the meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems.

perror supports the following options.

  • , , ,

    Display a help message and exit.

  • Print the error message for a MySQL Cluster error code.

  • ,

    Silent mode. Print only the error message.

  • ,

    Verbose mode. Print error code and message. This is the default behavior.

  • ,

    Display version information and exit.

Having a Windows Network Error Code 64 pop up does happen.

"The specified network name is no longer available. (code 64)"

Fortunately it is a known issue and there are some easy tips to helping you solve the Network problem. Read our article on Windows Error Code 64 and take care of it today.


What happens

When accessing a network resource, like a file server that is no longer responding or online, you will get the Windows error code 64. This error can indicate that a network resource is not connected to the network or is having hardware or software problems and is not responsive.

The following will help you if Windows code 64 comes up

The logical place to start with Windows error code 64 is with network connectivity. Verify whether or not you are able to connect to other network resources. You should also check with other users or computers that are on the same network to see if they can reach the resource that you are trying to connect to.

If your computer is the only one that is unable to connect to the network resource and you cannot connect to other resources on the network, you will need to make sure that your computer is plugged into the network. Check the network cable to verify that it is plugged securely into your computer and to the wall jack.

If other computers are having a problem connecting to the network resource, the problem is a little more serious. Verify whether the other computers/users are able to connect to any network resources. If they are not, there is probably a serious network problem that will require a network technician to resolve.

If there is only one specific computer or server that you and others on the network cannot connect to, try the following steps:

  • Click on Start and then click on Run
  • Type cmd into the box and hit the Enter key.
  • The Command Prompt window will come up.
  • In the Command Prompt window type in ping “server name” (server name will be the actual computer name or IP address of the server)
  • If the results come back with time out message, the issue will need to be escalated to a network administrator or technician. They will need to check the network connectivity to the resource and the resource itself to verify whether or not it is up and running and online.


TipFor more information, please see: How to fix Network error #64



Other Network error messages


Related Videos

Fix windows 7 update error 80072efe - Error Code 80072EFE Problem Fixed

Operating system error code 64 - are not

How to fix the Runtime Code 64 Access Error 64 Bit

Recommended Repair Tool:


This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.


STEP 1:
Click Here to Downloadand install the Windows repair tool.

STEP 2:
Click on Start Scanand let it analyze your device.

STEP 3:
Click on Repair Allto fix all of the issues it detected.

DOWNLOAD NOW

Compatibility

Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.

Article ID: ACX01759EN


Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000



Speed Up Tip #66

Use Keyboard Shortcuts:

Navigate through your computer quickly by learning how to use keyboard shortcuts. Windows programs such as Microsoft Excel and Outlook have a specific set of keyboard shortcuts for you to use efficiently. You can also create your own set of shortcuts for an even more personalized use.

Click Here for another way to speed up your Windows PC

4.8.2 perror — Display MySQL Error Message Information

For most system errors, MySQL displays, in addition to an internal text message, the system error code in one of the following styles:

You can find out what the error code means by examining the documentation for your system or by using the perror utility.

perror prints a description for a system error code or for a storage engine (table handler) error code.

Invoke perror like this:

Examples:

To obtain the error message for a MySQL Cluster error code, use the ndb_perror utility.

The meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems.

perror supports the following options.

  • , , ,

    Display a help message and exit.

  • Print the error message for an NDB Cluster error code.

    This option is deprecated in NDB 7.6.4 and later, where perror prints a warning if it is used, and is removed in NDB Cluster 8.0. Use the ndb_perror utility instead.

  • ,

    Silent mode. Print only the error message.

  • ,

    Verbose mode. Print error code and message. This is the default behavior.

  • ,

    Display version information and exit.


Having a Windows Network Error Code 64 pop up does happen.

"The specified network name is no longer available. (code 64)"

Fortunately it is a known issue and there are some easy tips to helping you solve the Network problem. Read our article on Windows Error Code 64 and take care of it today.


What happens

When accessing a network resource, like a file server that is no longer responding or online, you will get the Windows error code 64. This error can indicate that a network resource is not connected to the network or is having hardware or software problems and is not responsive.

The following will help you if Windows code 64 comes up

The logical place to start with Windows error code 64 is with network connectivity. Verify whether or not you are able to connect to other network resources. You should also check with other users or computers that are on the same network to see if they can reach the resource that you are trying to connect to.

If your computer is the only one that is unable to connect to the network resource and you cannot connect to other resources on the network, you will need to make sure that your computer is plugged into the network. Check the network cable to verify that it is plugged securely into your computer and to the wall jack.

If other computers are having a problem connecting to the network resource, the problem is a little more serious. Verify whether the other computers/users are able to connect to any network resources. If they are not, there is probably a serious network problem that will require a network technician to resolve.

If there is only one specific computer or server that you and others on the network cannot connect to, try the following steps:

  • Click on Start and then click on Run
  • Type cmd into the box and hit the Enter key.
  • The Command Prompt window will come up.
  • In the Command Prompt window type in ping “server name” (server name will be the actual computer name or IP address of the server)
  • If the results come back with time out message, the issue will need to be escalated to a network administrator or technician. They will need to check the network connectivity to the resource and the resource itself to verify whether or not it is up and running and online.


TipFor more information, please see: How to fix Network error #64



Other Network error messages


Error: "This Installation Package Is Not Supported by this Processor Type" When Installing an Intel® Graphics Driver

Summary

Update your operating systems to fix the installation error message.

Description

An error message is displayed saying This installation package is not supported by this processor type when installing Intel® Graphics drivers on Windows® 10.

Resolution

This error appears because the operating system (OS) is outdated. Newer versions of the driver require newer Windows 10 OS builds.

Follow these steps:

  1. Update Windows
  2. Select Check for Windows Updates to update the Windows 10 or 11 OS to the latest version.
  3. Install the latest Intel Graphics driver for Windows 10 from the Intel Download Center for your processor. For more information, see How to Install an Intel® Graphics Driver in Windows® 10 & Windows 11*.

If the issue persists: 

  1. Open the Device Manager by right-clicking the Windows Start button. Select Device Manager.
  2. Expand the Display adapterssection.
  3. Identify the Intel Graphics device among the options listed.
  4. Download the latest Intel Graphics driver for Windows 10 and save the .exe file on your system.
  5. Disconnect from the internet to make sure the driver will not be automatically updated by Windows.
  6. Go back to the Intel Graphics entry in the Device Manager.
  7. Right-click on Intel Graphics and click Uninstall.
  8. In the device removal dialog box, check Delete the driver software for this deviceand click OK.
  9. Restart the computer after the uninstallation is complete.
  10. Open the Device Manager.
  11. Expand theDisplay adapters section again.
  12. If no older drivers are stored in the system, the graphics controller in Device Manager should now be listed as Microsoft Basic Display Adapter, Standard VGA Graphics Adapter or similar. If not, repeat steps 7 through 10.
  13. Reboot the computer when prompted.

Additional troubleshooting:

  1. Check if integrated Graphics is enabled in the system BIOS. 
  2. Install the Intel Graphics Driver again after removing the external graphics card that has already been installed.

Backup Failure: Operating system error 64

Hello,

I am having a problem creating backups for a database.  I am using the Backup Task in SSIS and executing the SSIS package against a SQL Server 2000 database.  Sometimes the backup is successful, but recently the failure rate has increased with the following messages listed in the log:

[Execute SQL Task] Error: Executing the query "BACKUP DATABASE [Galaxy]

TO  DISK = N'\\mindata02\Data_D\DEVSQL6\Galaxy\Galaxy_backup_200706070927.bak'

WITH NOFORMAT, NOINIT,  NAME = N'Galaxy_backup_20070607092724', SKIP, REWIND, NOUNLOAD, 

STATS = 10 " failed with the following error: "BACKUP DATABASE is terminating abnormally. 10 percent backed up.

20 percent backed up. 30 percent backed up. 40 percent backed up. 50 percent backed up. 60 percent backed up.

70 percent backed up. 80 percent backed up. 90 percent backed up. Processed 4503024 pages for database

'Galaxy', file 'Galaxy_Data' on file 1. Processed 9360 pages for database 'Galaxy', file 'Galaxy_IDX' on file 1.

100 percent backed up. Processed 59228 pages for database 'Galaxy', file 'Galaxy_Log' on file 1.".

Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly,

or connection not established correctly.

Message

BackupDiskFile::RequestDurableMedia:  failure on backup device

'\\mindata02\Data_D\DEVSQL6\Galaxy\Galaxy_backup_200706070927.bak'.

Operating system error 64(The specified network name is no longer available.).

If anyone has encountered the Operating System Error 64(The specified network name is no longer available) or Operating System Error 59(An unexpected network error arrived) and has some recommendations it would be greatly appreciated.  Thanks in advance for the help.

 

operating system error code 64

4.8.2 perror — Display MySQL Error Message Information

For most system errors, MySQL displays, in addition to an internal text message, the system error code in one of the following styles:

You can find out what the error code means by examining the documentation for your system or by using the perror utility.

perror prints a description for a system error code or for a storage engine (table handler) error code.

Invoke perror like this:

Examples:

To obtain the error message for a MySQL Cluster error code, use the ndb_perror utility.

The meaning of system error messages may be dependent on your error 017 undefined symbol money operating system. A error parsing xaml file root element error code may mean different things critical error 84 on different operating systems.

perror supports the following options.

  • ,

    Display a help message and exit.

  • Print the error message for an NDB Cluster error code.

    This option is deprecated in NDB 7.6.4 and later, where perror prints a warning if it is used, and is removed in NDB Cluster 8.0. Use the 49 service error printer ndb_perror utility instead.

  • ,

    Silent mode. Print only the error message.

  • ,

    Verbose mode. Print error code and message. Operating system error code 64 is the default behavior.

  • ,

    Display version information and exit.


perror(1) — Linux manual page


PERROR(1) MariaDB Database System PERROR(1)

NAME         top

perror - explain error codes

SYNOPSIS         top

perror [options] errorcode.

DESCRIPTION         top

For most system errors, MariaDB displays, in addition to an internal text message, the system error code in one of the following styles: message . (errno: #) message . (Errcode: #) You can find out what the error code means by examining the documentation for your system or by using the perror utility. perror prints a description for a system error system error 32007 or for a storage engine (table handler) error code. Invoke perror like this: shell> perror [options] errorcode. Example: shell> perror 13 64 OS error code 13: Permission denied OS error code 64: Machine is not on the network Note that the meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems. perror supports the following options. • --help, --info, -I, -? Display a help message and exit. • --silent, -s Silent mode. Print only the error message. • --verbose, -v Verbose mode. Print error code and message, operating system error code 64. This is the default behavior. • --version, -V Display version information and exit.

COPYRIGHT         top

operating system error code 64 Copyright 2007-2008 MySQL AB, 2008-2010 Sun Microsystems, Inc., 2010-2020 MariaDB Foundation This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied operating system error code 64 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA read error 0x20 02110-1335 USA or see http://www.gnu.org/licenses/.

SEE ALSO         top

For more information, please refer to the MariaDB Knowledge Base, available online at https://mariadb.com/kb/

AUTHOR         top

MariaDB Foundation (http://www.mariadb.org/).

COLOPHON         top

This page is part of the MariaDB (MariaDB database server) project. Information about the project can be found at ⟨http://mariadb.org/⟩. If you have a bug report for this manual page, see ⟨https://mariadb.com/kb/en/mariadb/reporting-bugs/⟩. This page was obtained from the project's upstream Git repository ⟨https://github.com/MariaDB/server⟩ on 2021-08-27. (At that time, the date of the most recent commit that was found in the repository was 2021-08-26.) If you discover any rendering problems in this HTML version of the page, or you believe there is a better or more up-to-date source for the page, or you have corrections or improvements to the information in this COLOPHON (which is not part of the original manual page), send a mail to [email protected]

Error: "This Installation Package Is Not Supported by this Processor Type" When Installing an Intel® Graphics Driver

Summary

Update your operating systems to fix the installation error message.

Description

An error message is displayed saying operating system error code 64 installation package is not supported by this processor type when installing Intel® Graphics drivers on Windows® 10.

Resolution

This error appears because the operating system (OS) is outdated. Newer versions of the driver require newer Windows 10 OS builds.

Follow these steps:

  1. Update Windows
  2. Select Check for Windows Updates to update the Windows 10 or 11 OS to the latest version.
  3. Install the latest Intel Graphics driver for Windows 10 from the Intel Download Center for your processor. For more information, see How to Install an Intel® Graphics Driver in Windows® 10 & Windows 11*.

If the issue persists: 

  1. Open the Device Manager by right-clicking the Windows Start button. Select Device Manager.
  2. Expand the Display adapterssection.
  3. Identify the Intel Graphics device among the options listed.
  4. Download the latest Intel Graphics driver for Windows 10 and save the .exe file on your system.
  5. Disconnect from the internet to make sure the driver will not be automatically updated by Windows.
  6. Go back to the Intel Graphics entry in the Device Manager.
  7. Right-click on Intel Graphics and click Uninstall.
  8. In the device removal dialog box, check Delete the driver software for this deviceand click OK.
  9. Restart the computer after the uninstallation is complete.
  10. Open the Device Manager.
  11. Expand theDisplay adapters section again.
  12. If no older drivers are stored in the system, the graphics controller in Device Manager should now be listed as Microsoft Basic Display Adapter, Standard VGA Graphics Adapter or similar. If not, repeat steps 7 through 10.
  13. Reboot the computer when prompted.

Additional troubleshooting:

  1. Check if integrated Graphics is enabled in the system BIOS. 
  2. Install the Intel Graphics Driver again after removing the external graphics card that has already been installed.

Operating System Error Codes

NumberError CodeDescription1EPERMOperation not permitted2ENOENTNo such file or directory3ESRCHNo such process4EINTRInterrupted system call5EIOI/O error6ENXIONo such device or address7E2BIGArgument list too long8ENOEXECExec format error9EBADFBad file number10ECHILDNo child processes11EAGAINTry again12ENOMEMOut of memory13EACCESPermission denied14EFAULTBad address15ENOTBLKBlock device required16EBUSYDevice or resource busy17EEXISTFile exists18EXDEVCross-device link19ENODEVNo such device20ENOTDIRNot a directory21EISDIRIs a directory22EINVALInvalid argument23ENFILEFile table overflow24EMFILEToo many open files25ENOTTYNot a typewriter26ETXTBSYText file busy27EFBIGFile too large28ENOSPCNo space left on device29ESPIPEIllegal seek30EROFSRead-only file system31EMLINKToo many links32EPIPEBroken pipe33EDOMMath argument out of domain of func34ERANGEMath result not representable35EDEADLKResource deadlock would occur36ENAMETOOLONGFile name too long37ENOLCKNo record locks available38ENOSYSFunction not implemented39ENOTEMPTYDirectory not empty40ELOOPToo many symbolic links encountered42ENOMSGNo message of desired type43EIDRMIdentifier removed44ECHRNGChannel number out of range45EL2NSYNCLevel 2 not synchronized46EL3HLTLevel 3 halted47EL3RSTLevel 3 reset48ELNRNGLink number out of range49EUNATCHProtocol driver not attached50ENOCSINo CSI structure available51EL2HLTLevel 2 halted52EBADEInvalid exchange53EBADRInvalid request descriptor54EXFULLExchange full55ENOANONo anode56EBADRQCInvalid request code57EBADSLTInvalid slot59EBFONTBad font file format60ENOSTRDevice not a stream61ENODATANo data available62ETIMETimer expired63ENOSROut of streams resources64ENONETMachine is not on the network65ENOPKGPackage not installed66EREMOTEObject is remote67ENOLINKLink has been severed68EADVAdvertise error69ESRMNTSrmount error70ECOMMCommunication error on send71EPROTOProtocol error72EMULTIHOPMultihop attempted73EDOTDOTRFS specific error74EBADMSGNot a data message75EOVERFLOWValue too large for defined data type76ENOTUNIQName not unique on network77EBADFDFile descriptor in bad state78EREMCHGRemote address changed79ELIBACCCan not access a needed shared library80ELIBBADAccessing a corrupted shared library81ELIBSCN.lib section in a.out corrupted82ELIBMAXAttempting to link in too many shared libraries83ELIBEXECCannot exec a shared library directly84EILSEQIllegal byte sequence85ERESTARTInterrupted system call should be restarted86ESTRPIPEStreams pipe error87EUSERSToo many users88ENOTSOCKSocket operation on non-socket89EDESTADDRREQDestination address required90EMSGSIZEMessage too long91EPROTOTYPEProtocol wrong type for socket92ENOPROTOOPTProtocol not available93EPROTONOSUPPORTProtocol not supported94ESOCKTNOSUPPORTSocket type not supported95EOPNOTSUPPOperation not supported on transport endpoint96EPFNOSUPPORTProtocol family not supported97EAFNOSUPPORTAddress family not supported by protocol98EADDRINUSEAddress already in use99EADDRNOTAVAILCannot assign requested address100ENETDOWNNetwork is down101ENETUNREACHNetwork is unreachable102ENETRESETNetwork dropped connection because of reset103ECONNABORTEDSoftware caused connection abort104ECONNRESETConnection reset by peer105ENOBUFSNo buffer space available106EISCONNTransport endpoint is already connected107ENOTCONNTransport endpoint is not connected108ESHUTDOWNCannot send after transport endpoint shutdown109ETOOMANYREFSToo many references: cannot splice110ETIMEDOUTConnection timed out111ECONNREFUSEDConnection refused112EHOSTDOWNHost is down113EHOSTUNREACHNo route to host114EALREADYOperation already in progress115EINPROGRESSOperation now in progress116ESTALEStale NFS file handle117EUCLEANStructure needs cleaning118ENOTNAMNot a XENIX named type file119ENAVAILNo XENIX semaphores available120EISNAMIs a named type file121EREMOTEIORemote I/O error122EDQUOTQuota exceeded123ENOMEDIUMNo medium found124EMEDIUMTYPEWrong medium type125ECANCELEDOperation Canceled126ENOKEYRequired key not available127EKEYEXPIREDKey has expired128EKEYREVOKEDKey has been revoked129EKEYREJECTEDKey was rejected by service130EOWNERDEADOwner died131ENOTRECOVERABLEState not recoverable

Chapter 4: Run-time System Error Messages

PreviousCode Generation Error MessagesFile Status CodesNext

These messages are output by the run-time system (RTS), and so can be produced while you are compiling, debugging, or running your program. For each error message, the error message number, and its text and severity, is listed, along with an explanation of the error or problem that caused the message, and advice on how to prevent the error.

4.1 Format of Messages

Run-time system messages are displayed in the format:

action error: file 'file-name' error code:yyy, pc=xxxxxxxx, call=0, seg=ssnnnmessage-text

where the variables are:

What the run-time system was doing at the time of the error. For example, execution, I/O, load or write.
The name of the file on which the run-time system was operating
Either the run-time system error number or, if the error is caused by an I/O operation, the file status value. If the latter, the file status mappings currently on force are also displayed.
The position of the program counter, in hexadecimal; this can be related back to the source program using the REF Compiler directive.
The number of the segment being executed (0 for ROOT)
The error number
The error message
One of:


4.2 Types mhdd write error Error

There are two types of run-time error; exceptions and I/O errors. I/O errors are either fatal or recoverable. Recoverable errors are reported by the operating system; this enables you to trap them and take steps to recover from them if at all possible. Exceptions are fatal errors which are not reported and so cannot be trapped.

4.2.1 Exceptions

These are fatal errors covering conditions such as arithmetic overflow, too many levels of PERFORM nesting, operating system error code 64, and subscript out of range.

4.2.2 I/O Errors

These are either fatal or recoverable errors, that cause one of the following to take place:

  • If you did not specify a FILE STATUS clause for the file on which the error occurred then the error is treated as fatal. That is, the program terminates immediately with the RTS displaying its own message on the console in the format given above, operating system error code 64. See the chapter File Status Codes in your File Handling book for gta 4 terrorist mod details of how to define the file status.

  • If you specified a FILE STATUS clause for the relevant file then the value "9" (which indicates that an operating system error message has been received) is placed into status-key-1 and the operating system or RTS error number is placed into status key 2.

You must examine status key 1 after each file operation to ensure that the operation has been carried out successfully. 0 in status key 1 indicates the successful completion of a file operation; any other value indicates an error condition of some type.

If an error condition operating system error code 64 reported, the action which your program then takes is entirely your responsibility. If your program does not terminate when an error is reported, operating system error code 64, its subsequent behavior might not be as you would expect.

4.2.3 Fatal Errors

Fatal errors cause a message to be output to the console, and error c2548 for string this error message has been displayed your program terminates immediately.

Although you cannot recover from such an error during the run of your program, once it has terminated you operating system error code 64 be able to take steps to rectify the conditions which caused the error to occur. The list of run-time system error messages gives hints on how this might be achieved for individual errors.

4.2.4 Recoverable Errors

You can trap recoverable errors in your program, but the action you take when one of these errors is received is your responsibility.

4.2.5 Error Handling

Having received a file error you can deal with it in one of many ways. You might want your program operating system error code 64 display its own general error message, close any open files (if this is possible) and terminate. This should enable you to save any data which you have already written to the files. This data could be lost if you do not trap the error.

Should you want to recover from an error and to continue to run your program, code your program in such a way as to take action should a particular error be reported. For example, if you receive a "file not found" error then your program could prompt you to insert a disk containing the required file into a specified drive, if your operating system supports this.

Hints on how to recover from specific errors are given later in this chapter but you will be able to follow these hints only if you have coded your program in such a way as to be able to take advantage of them.

You might want to code your program to handle recoverable errors as follows:

  • Use AT END (which checks for a value of 1 in status key 1), or ahci smart error INVALID KEY (which checks for a value of 2 in status key 1) clauses where appropriate. You do not need to declare FILE STATUS items in this case.

  • Use Declaratives which check that status key 1 is not equal to 0 (that is the operation was not completed successfully) for all file-operations that have no AT END or INVALID KEY usb_bulk_write no error n900. You should declare FILE STATUS items in this case.

  • Declare FILE STATUS items and check for a value in status key 1 of either 9 which indicates an RTS error, operating system error code 64, or nonzero which shows that the file operation has not been successfully completed. You should explicitly check the operating system error code 64 byte after each file operation.

  • Do not use the FILE STATUS clause or AT END or INVALID KEY, in which bios error 75 case the RTS terminates immediately should any file error be received. In this situation all error messages are treated as though operating system error code 64 were fatal with the relevant RTS error message being output to the console.

4.2.6 Return-code Values

The run-time system always returns a value to the operating system when a COBOL program terminates. If the program terminates normally, the value is taken from the program's special register RETURN-CODE If the run-time system terminates the program because an operating system error code 64 error has occurred or because it has received a message from the operating system to quit immediately, the value returned depends on the operating system as described below.

Windows::
The value returned is 32 for a run-time system error and 16 for a quit interrupt when running under Windows, operating system error code 64. A keyboard quit interrupt is generated when the user presses Ctrl + Break. Use the command with the parameter to test the returned value, as shown in the following batch file fragment:

run myprog if errorlevel 32 goto rts_error if errorlevel 16 goto rts_interrupt

UNIX:
The run-time system returns a value of -1 for a run-time system error and -2 for an abnormal termination when the keyboard interrupt key (for example, Ctrl-C) is pressed error reading smart or the SIGTERM or SIGHUP signals are received. Typically, many UNIX implementations translate the value of -1 to the unsigned value 255, and the value -2 to the unsigned value 254. You can configure the run-time system to ignore ignore keyboard interrupts by using the run-time switch i (see the chapter Descriptions kazaki aplication error of Run-time Switches in your Server Express User's Guide for further details). Use the Bourne shell special parameter $ to obtain the value returned to the operating system, as shown in the following shell script fragment:

cobrun prog if test $? -eq 255 then echo "Abnormal termination" fi

See your operating system documentation for further details of how interrupts can be generated and how to handle values returned by a program.

4.3 Key to RTS Error Messages

These messages are output by the run-time system (RTS), and so can be produced while you are compiling, debugging, or running your program. When you select an error message number, its text and severity is listed, along with an explanation of the error or problem that caused the message, and advice on how to prevent the error.

There are two types of run-time error:

FatalA message is sent to the screen and the program terminates immediately.
RecoverableThe error is reported to the program, operating system error code 64. You can trap these errors in your program, but often they are the result of an error in your program's logic. If the program does not trap the error a message is sent to the screen and the program terminates immediately.

4.4 List of RTS Error Messages


001 Insufficient buffer space (Recoverable)

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 operating system error code 64 unable to allocate enough memory space for this operation, operating system error code 64.

Resolution:
Although you can trap this error you must do STOP RUN as soon as it is reported.


002 File not open when access attempted (Recoverable)

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.


003 Serial mode error (Recoverable)

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.


004 Illegal file name (Recoverable)

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.


005 Illegal device specification (Recoverable)

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.


006 Attempt to write to a file opened for INPUT (Recoverable)

You have tried to WRITE to a file that is open for input only, operating system error code 64.

Resolution:
Close the file and open it with a mode such as I-O, which allows you to write operating system error code 64 the file. As this error implies that your program logic contains a mistake, you might want to terminate the run and recode your program.


007 Disk space exhausted (Fatal)

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 operating system error code 64 this, put a new disk in a floppy disk drive and redirect your program's file operations to this.


008 Attempt to input from a file opened for OUTPUT (Recoverable)

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.


009 No room in directory (Recoverable)

The system cannot write to the specified directory for one of the following reasons:

  • The directory does not exist

  • The directory is full

  • Your program cannot find the directory

Resolution:
Create the directory if it doesn't exist. If the directory is full, 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 it. Alternatively, specify a different drive or directory for your file operations.


010 File name not supplied (Recoverable)

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.


011 Process limit reached (Fatal)

One of the following has occurred:

  • The run-time system cannot create a new process operating system error code 64 the operating system limit on the total number of processes per user or system-wide would be exceeded.

  • Insufficient memory is available to complete the operation.

Resolution:
Terminate any processes that you are no longer using, or make more memory available.

Your operating system might enable you to increase the maximum number of processes allowed. Refer to your operating system documentation for further information, operating system error code 64.


012 Attempt to open a parse error syntax error, unexpected t_variable, expecting which is already open (Recoverable)

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.


013 File not found (Recoverable)

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.


014 Too many files open simultaneously (Recoverable)

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.


015 Too many indexed files open (Recoverable)

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.)


016 Too many device files open (Recoverable)

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, operating system error code 64.

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.


017 Record error: probably zero length (Recoverable)

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.


018 Read part record error: EOF before EOR or file open in operating system error code 64 wrong mode (Recoverable)

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 canon 160 mp160 error 23 record, reports this error.

Resolution:
mercedes start error Ensure that the record size you give when you read from or WRITE to a file is consistent.


019 Rewrite error: open mode or access mode wrong (Recoverable)

You are trying to do a REWRITE american megatrends bios error 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.


020 Device or resource busy (Recoverable)

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.


021 File is a directory (Fatal)

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 operating system error code 64 either change your file access attributes or recode your program so that it does not violate the existing attributes.


022 Illegal or impossible access mode for OPEN (Recoverable)

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.


023 Illegal or impossible access mode for CLOSE (Recoverable)

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.


024 Disk input-output error (Recoverable)

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.


025 Operating system data ora-00905 oracle error (Fatal)

You are trying to set up terminal characteristics for a device which is not a terminal.

Resolution:
Recode your program.


026 Block I-O error (Fatal)

An error has occurred while you are trying to access a disk. This could be the result of a corrupt disk.

Resolution:
hasp runtime error operating system error code 64 If you have a corrupt disk try to run your program again using your backup copy.


027 Device not available (Recoverable)

You are trying to sql error 10054 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.


028 No space on device (Fatal)

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.


029 Attempt to delete open file (Recoverable)

You have tried to perform a DELETE FD operation on an open file.

Resolution:
Close the file before performing the DELETE FD operation.


030 File system is read-only (Recoverable)

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 operating system error code 64 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.


031 Not owner of file (Recoverable)

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.


032 Too many indexed files, or no such process (Recoverable)

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:
operating system error code 64 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.


033 Physical I-O error (Fatal)

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, operating system error code 64.

Resolution:
You should try to correct the fault in your hardware; for example put a disk in the necessary drive.


034 Incorrect mode or file descriptor (Recoverable)

You are either trying to write to a file which is open for read purposes only, or read a file which is alone wake error code 5 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 operating system error code 64 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.


035 Attempt to access a file with incorrect permission (Recoverable)

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 operating system error code 64 of the file you cannot to carry out that operation successfully unless you copy the file and make bad image error the changes to the copy only. You cannot alter the source file.


036 File already exists (Recoverable)

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 operating system error code 64 to eliminate this mistake.


037 File access denied (Fatal)

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 operating system error code 64 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. chevronwp7 error 81030120 Disk not compatible (Fatal)

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.


039 File not compatible (Fatal)

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.


040 National Language initialization not set up correctly (Fatal)

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 operating system error code 64, 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, operating system error code 64.

Resolution:
Set up the required environment or side file before you operating system error code 64 to run the program again.


041 Corrupt index file (Recoverable)

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. Canon mp270 e08 error 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.


042 Attempt to write on broken pipe (Recoverable)

One of the following has occurred:

  • Your program has created a process as a result of a DD_ logical file-name mapping assignment (for example, the process might be a line printer spooler). The process was not created properly, or has ended prematurely. This error occurs when your program tries to write to the process.

  • Your application has terminated abnormally or prematurely, thus breaking the pipe.

Resolution:
You can trap the error status returned by the write operation, then open the file again.


043 File information missing for indexed file (Fatal)

The system has crashed on your program's previous run, while the file was open. Information was probably added operating system error code 64 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 operating system error code 64 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.


044 Attempt to OPEN an NLS file in a non-NLS program (Fatal)

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.


045 Attempt to OPEN an NLS file using incompatible language definition (Fatal)

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:
operating system error code 64 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.


047 Indexed structure overflow (Fatal)

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. This may be because you have reached the maximum number of duplicate keys.

Alternatively, you have tried to access an old format indexed file, created perhaps using CIS COBOL.

Resolution:
If your index has no room operating system error code 64 further operating system error code 64 you should either reorganize your file or convert it to IDXFORMAT"4" using Rebuild, to allow a greater number of duplicate keys.

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.


048 Attempt to divide by zero (Fatal)

You are executing a program that is trying to perform a fixed-point divide by zero.

Resolution:
Recode your program so that you can trap the error with an ON SIZE ERROR clause


055 Routine table overflow (Fatal)

You have tried to load too many programs simultaneously.

Resolution:
Cancel any programs that you are no longer using, or use fewer separate programs.


065 File locked (Recoverable)

You have tried to open a file which has already been locked, or opened for output by another operating system error code 64. Alternatively, service call 069 error 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 script fs_mode error. You should then be able to continue to run your program.


066 Attempt to add duplicate record key to indexed file (Fatal)

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.


067 Indexed file not open (Recoverable)

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, operating system error code 64.


068 Record locked (Recoverable)

You have tried to access a record which is currently locked by another user, operating system error code 64.

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.


069 Illegal argument to isam module (Fatal)

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.


070 Too many indexed files open (Recoverable)

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.


071 Bad indexed file format (Fatal)

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.


072 End of indexed file (Fatal)

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.


073 No record found in indexed file (Fatal)

This is the operating system error code 64 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.


074 No current record in indexed file (Fatal)

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, operating system error code 64.


075 Indexed data file name too long (Fatal)

When creating indexed files, the extension .idx is added to the user-defined file-name, so your file-name must not exceed x-4 characters in length, where x is the maximum length of file-name.

Resolution:
Rename the file with a shorter file-name, that is, one that is less than 10 characters in length.


076 Can't create lock file in /isam directory (Fatal)

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.


077 Internal ISAM module error (Fatal)

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.


078 Illegal key description in indexed file (Fatal)

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.


079 COBCONFIG syntax error (Fatal)

An error exists in the run-time configuration sidefile accessed via the environment variable COBCONFIG.

Resolution:
Check the syntax of the entries in the configuration file. You might have used incorrect syntax, or syntax that is not compatible with the type of run-time tuneable you are configuring (this could include assigning an illegal value to the tuneable).

See Also:
The chapter Run-time Configuration in your Server Express User's Guide.


081 Key already exists in indexed file (Fatal)

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.


082 CALL convention not supported (Fatal)

The CALL convention you have specified is not supported.

Resolution:
Change the convention defined in the special-names paragraph to one of the supported CALL conventions.


086 Remote file system failure (Fatal)

099 Illegal operation in SORT/MERGE module (Fatal)

A SORT or MERGE module has received a RELEASE operation outside the Input procedure, or a RETURN operation either outside the Output procedure, or before the Input procedure has terminated correctly.

Resolution:
Recode your program so that RELEASE and RETURN operations are issued by the appropriate procedures.


100 Invalid file operation (Fatal)

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:
operating system error code 64 Recode your program to ensure that the REWRITE statement in error is preceded by a read NEXT.


101 Illegal operation on an indexed file (Fatal)

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.


102 Sequential file with non-integral number of records (Fatal)

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.


103 Parameter operating system error code 64 be passed BY VALUE (Fatal)

104 Null file name used in a file operation (Fatal)

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:
Connection error socketexception connection reset your program specifying the correct file-name.


105 Memory allocation error (Fatal)

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.


106 Dictionary error (Fatal)

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.


107 Operation not implemented in this run-time system (Fatal)

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.


108 Failure to initialize data division (Fatal)

The run-time system cannot load your program properly because the data the roots of terrorism needed to correctly initialize the Data Division has become corrupted.

Resolution:
You should compile your program again to try to obtain good intermediate code.


109 Invalid checksum in run-time system (Recoverable)

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, operating system error code 64.


110 Generated adsl ber test error ratio not supported by this RTS (Fatal)

Resolution:
Contact Technical Support who will help you to discover the cause of the error and how it can be rectified.


111 Incompatible Class Library and Run-Time Environment versions (Fatal)

The version numbers for these components do not match.

Resolution:
Check that you have fully installed both the Class Library and the Run-Time Environment from the same version of Object COBOL. If you have more than one version installed, check that your PATH, LIBPATH, and COBDIR environment variables specify an appropriate path for the version you are using.


112 Unable to locate/access the required security key (Recoverable)

The run-time system cannot locate or cannot access the coded security key (dongle) that is required to execute this application.

Resolution:
Connect the security key that was supplied with your COBOL system to the parallel port of your computer, then re-run the application.


114 Attempt to access item beyond bounds of memory (Fatal)

Memory access violation has been detected by your operating system.

See Also:
The chapter Handling Protection Violation Errors in your Programmer's Guide to Writing Programs.


115 Unexpected signal (Fatal)

A signal the run-time system was not expecting has been caught.


116 Cannot allocate memory (Fatal)

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.


117 Bad collating sequence (Fatal)

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.


118 Symbol not found (Fatal)

You have attempted to reference a name that has not been defined.


119 Name is not unique (Fatal)

The run-time system has detected a name (for example, data item, entry remote shutdown 53 error or module name) which is already defined.

OO programs can also cause this error for either of the following reasons:

  • You have defined the same method-name twice in a single object

  • You have defined the same class name with different filenames in different programs, operating system error code 64, in the Class-Control paragraph. Filename matching is case-sensitive; class filenames should always be coded in lower-case.

Resolution:
You can recode your application to remove the naming duplication.

See Also:
The description of the E run-time switch in the chapter Descriptions of Run-time Switches in your Server Express User's Guide.


120 Symbol string table of zero size (Fatal)

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.


121 Operating system error code 64 is not in TEXT section (Fatal)

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.


122 coblongjmp() called from below level of cobsetjmp() (Fatal)

You might have returned control to a higher level in operating system error code 64 CALL/PERFORM hierarchy than the level at which cobsetjmp() was called, operating system error code 64. coblongjmp() must be called only from the same or from a lower level in the CALL/PERFORM hierarchy as the corresponding cobsetjmp() or cobsavenv().

Resolution:
Check and correct the logic of your program, and then resubmit it to your COBOL system.


123 Unknown relocation type (Fatal)

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.


124 Communications failure during I/O request to the Fileshare Server (Fatal)

See Also:
Your Fileshare User's Guide.


125 All locks/ current transactions canceled due to exceeding time limit

See Also:
Your Fileshare User's Guide.


126 Record size exceeds system limit (Fatal)

127 coblongjmp() called from a different thread to cobsetjmp() (Fatal)

You have called coblongjmp() in a different thread from the corresponding call to cobsetjmp(). coblongjmp() must be called from the same thread as the corresponding call to cobsetjmp().

Resolution:
Check and correct the logic of your program, then resubmit it to your COBOL system.


129 Attempt to access record zero of relative file (Recoverable)

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 error sd down to run your program.


135 File not found (Recoverable)

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.


136 Corrupt or invalid executable file (Fatal)

An attempt was made to execute a .gnt file or a library file that is not valid. The file might be corrupted or truncated.

Resolution:
Recompile the source code or recreate the operating system error code 64 file, operating system error code 64, ensuring that it is processed without errors.


137 Illegal device specification - not mass storage

138 File closed with lock - cannot be opened (Recoverable)

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.


139 Record length or key data inconsistency (Recoverable)

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.


141 File already open - cannot be opened (Recoverable)

You have tried to open a file which is already open and so cannot be opened again, operating system error code 64.

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, operating system error code 64, you might want to close any open files, execute a STOP RUN statement and then recode.


142 File not open - cannot be closed (Recoverable)

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.


143 Rewrite/delete in sequential mode not preceded by successful read (Recoverable)

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.


144 Boundary violation (Recoverable)

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.


146 No current record defined for sequential read (Recoverable)

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.


147 Wrong open mode or access mode for read/start (Recoverable)

You have tried to carry out a read or START operation on a file which has not been opened for INPUT or I-O, operating system error code 64, 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, operating system error code 64, you might want to close any files which are open, execute a STOP RUN statement and then recode.


148 Wrong open mode or access mode for write (Recoverable)

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 operating system error code 64 which is not open at all.

Resolution:
Close the file and reopen it with the correct open mode for the file type. However, operating system error code 64, 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 operating system error code 64 then recode.


149 Wrong open mode or access mode for rewrite/delete (Recoverable)

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.


151 Random read on sequential file (Recoverable)

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.


152 REWRITE on file not opened I-O (Recoverable)

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 Sql error 17058 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. chernobyl terrorist attack 2


153 Subscript out of range (Fatal)

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.


154 PERFORM nested too deeply (Fatal)

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 recode your program to ensure that the GO TO in question jumps to an EXIT statement at the end of the PERFORM's range.


155 Illegal command line (Fatal)

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.


156 Too many parentheses in compute statement (Fatal)

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.


157 Not enough program memory: object file too large to load (Recoverable)

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 sentura builder sql error CALL statement, the error is recoverable. Any associated imperative statement is executed before the next instruction.


158 Attempt to REWRITE to a line-sequential file (Recoverable)

You have used the REWRITE statement in conjunction with a file whose organization is line sequential. The Operating system error code 64 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 interface error press f1 file to which you want to do a REWRITE either sequential, indexed sequential, or relative.


159 Malformed line-sequential file (Recoverable)

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, operating system error code 64.


160 Overlay loading error (Recoverable)

An error has occurred while trying to load the intermediate code for an operating system error code 64 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.


161 Illegal intermediate code (Fatal)

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, operating system error code 64, to try to obtain uncorrupted intermediate code.


162 Arithmetic overflow or underflow (Fatal)

You are executing a program that is trying to perform a operating system error code 64 divide by zero.

Resolution:
You should recode your program to avoid this illegal operation.


163 Illegal character in numeric field (Fatal)

The contents of a numeric or numeric edited field are inconsistent with 800a03ec excel error picture definition of that field.

Resolution:
operating system error code 64 You must adjust your code so that no invalid data is used.


164 Run-Time subprogram not found (Fatal)

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 operating system error code 64 still received this error you should contact Technical Support.


165 Version number incompatibility (Fatal)

You have tried to:

  • Run a program that has intermediate code which operating system error code 64 been produced on a version of your COBOL system that is incompatible with the run-time system you are using. Your run-time system, therefore, cannot execute correctly any generated code you are producing or have already produced from this intermediate code.

  • Execute a file which is not in your COBOL system's intermediate or generated code.

  • Load a module whose format is not valid for the Win32 platform.

166 Recursive COBOL CALL is illegal (Fatal)

You have tried to call a COBOL module that is already active.

Resolution:
You should recode your program.


167 Too many USING items (Fatal)

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.


168 Stack overflow (Fatal)

You have nested a PERFORM statement or a series of CALL statements too deeply.

Resolution:
Edit your program to reduce the number of levels in the nested PERFORM or CALL statement.


169 Illegal configuration information (Fatal)

You have tried an operation for which your machine is not configured; the most likely cause of this is incorrect configuration of Adis or the file handler.

Resolution:
Check the configuration of Adis or the file handler.


170 System program not found (Fatal)

A system program, for example Adis or Mffh, is not present.

Resolution:
Ensure that all the system programs are available and copy those which are not currently present using. Once all the necessary system programs are available you can run your program.


171 Japanese operations illegal with this RTS (Fatal)

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.


173 Called program file not found in drive/directory (Fatal)

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, or to send a message to a class which cannot be loaded.

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.

If the error was caused by a class which could not be loaded, find out whether or not the filename for the class (listed in the Class-Control paragraph) is a separate executable file, or contained in a .dll or .lbr file. If it is a separate executable file, operating system error code 64, the resolution is as above. If it is part of a .dll or .lbr file, ensure that the containing file has been loaded with a CALL statement before sending messages to any of the ifacechangeaddr error, closing ipcp. If the program not found is P2emgr, operating system error code 64, you need to load the GUI Class Library, with a CALL "APIGUI" statement.

See Also:
The chapter Micro Focus Environment Variables in your Server Express User's Guide.


174 Imported file not found (Fatal)

You have tried to load a .dll file which contains references to another canon printer mp250 error e02 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.


175 Attempt to run intermediate code program which had severe errors in it (Fatal)

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, the debugger reports this error and enables you to continue to run the program.

See Also:
The description of the E run-time switch in the chapter Descriptions of Run-time Switches in your Server Express User's Guide.


176 Illegal intersegment reference (Fatal)

You might have a corrupted file, operating system error code 64. 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.


177 Attempt to cancel program failed (Fatal)

You have tried to remove a currently executing program or its parents or grandparents, from memory.

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.


179 Error during chain (program not found) (Fatal)

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 include the directory or drive on which the file is present when your program calls it.


180 End-of-file marker error (Fatal)

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 operating system error code 64 your program.


181 Invalid parameter error (Fatal)

A parameter which you have used is not operating system error code 64 which is recognized by your operating system error code 64 system.

Resolution:
Revise your code to contain a parameter which is known by your system.


182 Console input or console output open in wrong direction (Fatal)

You are either trying to read input from the screen or write to the keyboard.

Resolution:
You should recode your program.


183 Attempt to open line sequential file for I-O (Fatal)

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.


184 ACCEPT/DISPLAY I-O error (Fatal)

You have either tried to read input from the screen or write to the keyboard, or the ADIS module has not been able to ms sql server error 15023 your terminal's channels for I-O.

Resolution:
Your program logic contains a mistake, so you must recode.


185 File malformed (Recoverable)

186 Attempt to open stdin, stdout or stderr with incorrect mode (Recoverable)

You have tried to open either a standard input file with output mode, or some other file in an incorrect mode.


188 Filename too large (Fatal)

A file-name which you have used has more characters than the maximum number allowed by your operating system.

Resolution:
Operating system error code 64 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.


189 Intermediate code load error (Fatal)

You are unable to load your intermediate code, operating system error code 64. 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, operating system error code 64. You should then be able to load your code and run the program successfully.


190 Too many arguments to CALL (Fatal)

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 operating system error code 64 ones. You should then be able to operating system error code 64 your program successfully, operating system error code 64.


191 Terminal type not defined (Fatal)

Your terminal is not defined. operating system error code 64
Your terminal type is undefined, so your operating system is unable to drive your terminal. Set up the necessary environment for your terminal.


192 Required terminal capability description missing (Fatal)

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.


193 Error in variable length count (Fatal)

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.


194 File size too large (Fatal)

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 operating system error code 64 for your operating system to handle. Having recoded your program you can then rerun it.


195 Operating system error code 64 not preceded by a read (Fatal)

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.


196 Record number too large in relative or indexed file (Fatal)

The relative record key has exceeded the system limit, that is, operating system error code 64, 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 operating system error code 64 record length.


197 Screen handling system initialization error (Fatal)

This error can be caused by one of the following:

  • Your display adapter is in the wrong mode.

  • Your screen handling interface has not been correctly initialized because your terminal does not have the required capabilities.

  • Memory has been incorrectly allocated.

Resolution:
The monitor must be in alphanumeric display mode rather than graphics display mode.


198 Load failure (Fatal)

The system cannot load a program module or, in a operating system error code 64 program, start a new thread, operating system error code 64.

A CALL statement has failed because:

  • In the case of a DLL, the specified entry point does not exist in the file

  • In the case of an .int or .gnt file, the file has been corrupted

  • In the case of a call of the form $PROG, name mapping has failed

  • In the case of a call-by-number library routine (CALL data-name, where data-name is a pic x with value greater than x'80'), the routine does not exist

Any call or attempt to start a thread can fail where internal structures have been corrupted; for example, by a protection violation.

A statement of the form SET PROCEDURE POINTER TO ENTRY entry-point has failed because the entry point cannot be found on disk or in the operating system error code 64 current run-unit, operating system error code 64.

Rarely, this error can be caused by a CALL statement failing because of insufficient available memory or because the run-time system version is too old.

Resolution:
Check that the target of your call exists and has not been corrupted.

Test that a procedure pointer is valid before using it by including code of the form:

set bad-pointer to entry 'just-not-there-ever' . set procedure-pointer to entry 'myentrypoint' if procedure-pointer = bad-pointer display error end-if
199 Operating System error code lies outside expected range (Fatal)

A system call has returned an unexpected error number which is not documented.

Resolution:
Contact Technical Support who will help you to discover the operating system error code 64 cause of this error.


200 Run-time system internal logic error (Fatal)

The amount of memory available on your machine is so low that not even the run-time system can be fully loaded.

Alternatively, your run-time system has stopped as a result of an internal logic error from which you cannot recover.

Resolution:
Free some memory and then you should be able to run your program successfully.

Contact Technical Support who will help you to discover the cause of the error.


201 I-O error in paging system (Fatal)

No room is available in your current directory or on the floppy disk which you are using, for the paging file.

Resolution:
Operating system error code 64 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.


203 CALL parameter not supplied (Fatal)

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, operating system error code 64, or check that it is a valid caller.


206 Reading unwritten data from memory (Fatal)

You are trying to read data which has not been written, from the core file.


207 Machine does not exist (Recoverable)

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.


208 Error in multi-user system (Fatal)

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.


209 Network communication error (Recoverable)

This is normally given if an incorrect checksum has been received in a communications operating system error code 64.

Resolution:
Your program should continue to execute after you have received this error but database import error might be undefined.


210 File is closed with lock (Fatal)

You stop c0000221 unknown hard error xtreme 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.


211 Program not executable by Run-Time System (Fatal)

An attempt was made to run a program that is incompatible with the currently-specified run-time system. For example, system executable, shared library, and callable shared object files that have been linked using older COBOL systems could be incompatible.

On brink error appcrash 32-bit/64-bit COBOL systems, all code must be compiled and linked using the same word length. A 64-bit run-time system does not run programs compiled and/or linked on 32-bit platforms or in 32-bit mode. Similarly, a 32-bit run-time system does not run programs compiled and/or linked on 64-bit platforms in 64-bit mode.

Resolution:
Recompile and/or relink your program so that it is compatible with the current run-time system.


213 Too many locks (Recoverable)

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 essbase error 1040004 to continue to run your program. You should try not to operating system error code 64 a record lock for longer than is necessary.


214 GO TO has not been ALTERed (Fatal)

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.


215 Cannot ANIMATE a program running COMMUNICATIONS (Fatal)

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.


216 Cannot initialize the named communications device (Fatal)

A device driver is probably missing.

Resolution:
Ensure that all communications drivers are loaded before you try to run Communications.


217 Incompatible host for native code file (Fatal)

The .gnt file is not valid operating system error code 64 the host processor.

Resolution:
You must resubmit your program to your COBOL system.


218 Malformed MULTIPLE REEL/UNIT file (Fatal)

Either your file header is not correctly formatted, operating system error code 64 you are not using a MULTIPLE REEL/UNIT file, operating system error code 64.

Resolution:
You should try to run your program again using a backup copy of the relevant file.


219 Operating system shared file limit exceeded (Recoverable)

You have tried to exceed your operating system's limit on the number of shared files that you can have open simultaneously, operating system error code 64. 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.


220 Attempt to execute more than one SORT or MERGE simultaneously (Fatal)

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, operating system error code 64.

Resolution:
You should recode your program to ensure that it does not execute more than one SORT or MERGE at any one time.


221 SORT/MERGE error: see status keys (Fatal)

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, operating system error code 64.

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, operating system error code 64.


222 SORT/MERGE error: see status keys (Fatal)

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.


223 SORT/MERGE error: see status keys (Fatal)

You have tried a SORT/MERGE operation which has been unsuccessful for some reason, operating system error code 64. 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. image i/o error 3ds max set TMP to point to a directory that does exist, or unset TMP.


224 External Language Initialization failure

225 Dynamic load error - program component missing (Fatal)

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 no dns records squid error, 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 or restructure your application so that it uses less memory.

Increase your operating system file handles limit.


226 EXTERNAL file definition inconsistent

Two or more programs define the same external file but with different formats. For example, maximum and minimum record lengths might operating system error code 64 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 operating system error code 64 have the file definition in a COPY file.


227 EXTERNAL data definition inconsistent (Fatal)

Two or more programs are defining the same external data item, but as3 error 1023 first loaded program has defined the size differently from the second or server connection error bizhub 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.


228 Could not allocate memory for EXTERNAL item (Fatal)

229 SORT/MERGE module does not support EXTERNAL using/giving files (Recoverable)

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).


235 Error in animator communications channel (Fatal)

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:
operating system error code 64 Copy the animated program file to a different directory and try animation, operating system error code 64.


236 Animated program has terminated unexpectedly (Fatal)

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:
operating system error code 64 Run your program without animation to determine if it runs successfully; if so, animate the program without cross-session or intrasession animation.


237 Unable to initialize animated process (Fatal)

Animator has encountered system limits in starting your program. The animated program cannot start because of either insufficient memory or too operating system error code 64 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, operating system error code 64.


238 STOP RUN encountered during GNT animation (Informational)

Animator has encountered a STOP RUN statement while animating your .gnt code program.

Resolution:
Step or Zoom the animated program, operating system error code 64, and Animator will terminate the program and its current session.


239 Iar error e27 run-time system initialization failure (Informational)

You are calling a COBOL module from a non-COBOL program, and have not initialized the shared run-time system.

Resolution:
Ensure that your application calls the cobinit() function before executing any COBOL modules. See the chapter Mixed-language Programming in your Programmer's Guide to Writing xerox workcentre 3119 lsu error Programs for more information about the cobinit() function.


240 Object reference not valid (Fatal)

You have tried to use an object reference that contains an incorrect or non-existent object handle.

Resolution:
Ensure that the object reference uses the correct object handle, and that your program has not previously destroyed the object by sending it a Finalize message.


241 Cannot instantiate an abstract class (Fatal)

You have tried to create an instance of a class that has been declared stop in /usr/ports/misc/mc error code 1 ABSTRACT. Such classes cannot be instantiated.

Resolution:
Ensure that you have specified the correct class name. Check to see if there is a subclass that you should use instead.


242 Could not resolve DoesNotUnderstand message (Fatal)

The run-time system could not resolve the DoesNotUnderstand message. This is usually because you have defined a class in such a way that this method cannot be found.

Resolution:
Check the logic in your program to ensure that it invokes only methods that are supported by the object, or ensure that the object supports the DoesNotUnderstand method.


243 Class could not be loaded (Fatal)

An attempt to load an object class has failed because the class does not contain a valid Class-Control section, or because the class is not defined correctly.

Resolution:
Check the definition of the class.


254 Keyboard interrupt to ANIMATOR during ACCEPT (Fatal)

While using Animator you have terminated your program with a keyboard interrupt.

PreviousCode Generation Operating system error code 64 MessagesFile Status CodesNext

How to fix the Runtime Code 64 Access Error 64 Bit

Recommended Repair Tool:


This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, operating system error code 64, as well as repair malware/virus damage and more by replacing damaged and missing system files.


STEP 1:
Click Here to Downloadand install the Windows repair tool.

STEP 2:
Click on Start Scanand let it analyze your device.

STEP 3:
Click on Repair Allto fix all of the issues it detected.

DOWNLOAD NOW

Compatibility

Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free, operating system error code 64. Full system repairs start at $19.95.

Article ID: ACX01759EN


Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000



Speed Up Tip #66

Use Keyboard Shortcuts:

Navigate through your computer quickly by learning how to use keyboard shortcuts. Windows programs such as Microsoft Excel and Outlook have a specific set of keyboard shortcuts for you to use efficiently. You can also create your own set of shortcuts for an even more personalized use.

Click Here for another way to speed up your Windows PC

0 Comments

Leave a Comment