ERROR_TOO_MANY_SEMAPHORES Cannot create another system semaphore 101 Reported by CloseFile, Write, WriteIn, or Flush if the disk becomes full. 101 ERROR_EXCL_SEM_ALREADY_OWNED The exclusive semaphore is owned by another process. 102 Reported The server's password is out of date at the domain controller. 1398 There is a time and/or date difference between the client and server. 1399 This operation cannot be performed on Alternatively, you have tried to access an old format indexed file, created perhaps using CIS COBOL. 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
I doubt that is directly your problem, but might help in this timing problem you seem to be having during shutdown. System Error Codes (0-499) Note The information on this page is intended to be used by programmers so that the software they write can better deal with errors. Resolution: Check to see that you used a valid call number in the unsuccessful subroutine call. If required, correct the subprogram's name in the calling program and resubmit it to your COBOL system.
Resolution: Ensure that you are in the correct directory or that a path to the file concerned exists. Which is correct imho.">(GH-249
Resolution: Close some of the open files which you are not currently accessing, and then try to open the relevant file again. Try logging in later. 425 Cannot open data connection. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location. ERROR_PIPE_LOCAL 229 (0xE5) The pipe is local. ERROR_BAD_PIPE 230 (0xE6) Windows 10 Error Codes Some codes represent errors, most others simply communicate the status of the connection.
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 This documentation is archived and is not being maintained. Alternatively, you have used the same name for a called program as for a previously defined data item. 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
The internal communication capability cannot be removed from the network. 5067 One or more cluster resources depend on the network to provide service to clients. 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 Check the directory that you are backing the database to 4005 The name does not exist in the WINS database 4006 Replication with a non-configured partner is not allowed 6118 The Reload to refresh your session.
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 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 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 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
Whatever you do in your automated testing, chances are that you are not checking exception text (nor should you). 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 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. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package. 1636 This patch
Hopefully that will help find the issue. If you have additional suggestions regarding the System Error Codes documentation, given the constraints enumerated at the top of the page, please click the link labeled "Send comments about this topic Alternatively, the generic command-line interpreter, which must be present if your program is to be run successfully, is not found on your system.