Datasets:

testingllma

/

cicd

like 0

Compilation complete with n errors

Cause could be found few lines above as an COBCH0149S and inference from OpenText could be suggested to user

Folder1’ is an NON TRUSTED FOLDER

Inform to IT-OPS before deployment, so potential error could be corrected beforehand

Bind Failure: SQLSTATE=80001 Error:dd/mm/yyyy hh:mm :D:/pathtobindfile failed in bind

Intimate IT-OPS when such embedded errors occurs in IT-OPS. Solution. Kill the running Api's and redeploy

Code E401 npm ERR!

Suggest user to change the token. Solution – Logon to artifactory – setup npm – download token

CASKC0027E Error executing service ‘program’

Intimate Dev to provision access to respective folders for mf_users

Communications component error (8) or 00008

check the ssl_client connections using ssl_connect?

0 0 0 LOG TRANSMISSION RESUMED 0 0 0 0

Intimate infrastructure team about the repeated instances

Authorization ID: XXXX Operation: Replace View SQLCODE: -551

Logon to DB2LUW and check grants for tables and inform stakeholders

Insufficient buffer space (Recoverable)

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

File not open when access attempted (Recoverable)

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.

Serial mode error (Recoverable)

The name of your program is recognized by the operating system as a valid device. Rename your program.

Illegal file name (Recoverable)

A filename 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.

Illegal device specification (Recoverable)

Try the operation again using a device name that your system recognizes.

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

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.

Disk space exhausted (Fatal)

This error can be trapped, once it has been reported you must do a STOP RUN immediately to terminate your program's run. When your program has terminated, delete file that no longer need. Alternatively, if your operating system supports this, put new disk in a floppy disk drive and redirect your program's file operations.

No room in directory (Recoverable)

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.

File name not supplied (Recoverable)

Specify the external filename.

Process limit reached (Fatal)

You should 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.

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

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.

File not found (Recoverable)

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.

Too many files open simultaneously (Recoverable)

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.

Too many indexed files open (Recoverable)

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

Record error: probably zero length (Recoverable)

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.

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

Ensure that the record size you give when you read from or WRITE to a file is consistent.

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

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.

Device or resource busy (Recoverable)

You can trap the error status returned by open and retry the open at regular intervals until it succeeds.

File is a directory (Fatal)

You need to either change your file access attributes or recode your program so that it does not violate the existing attributes.

Illegal or impossible access mode for OPEN (Recoverable)

Open the file with a mode that is compatible with that type of file.

Illegal or impossible access mode for CLOSE (Recoverable)

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.

Disk input-output error (Recoverable)

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.

Operating system data error (Fatal)

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

Block I-O error (Fatal)

If you have a corrupt disk try to run your program again using your backup copy.

Device not available (Recoverable)

Attach the device to your machine and ensure that it is on-line. Repeat the file operation.

No space on device (Fatal)

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.

Attempt to delete open file (Recoverable)

Close the file before performing the DELETE FD operation.

File system is read-only (Recoverable)

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.

Not owner of file (Recoverable)

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.

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

In this case you must rewrite your code so that it uses a process id which your system recognizes.

Physical I-O error (Fatal)

You should try to correct the fault in your hardware

for example put a disk in the necessary drive.

Incorrect mode or file descriptor (Recoverable)

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.

Attempt to access a file with incorrect permission (Recoverable)

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.

File already exists (Recoverable)

As this error implies that your program logic contains a mistake, you might like to recode your program to eliminate this mistake.

File access denied (Fatal)

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.

Disk not compatible (Fatal)

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.

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.

National Language initialization not set up correctly (Fatal)

On DOS, Windows and OS/2, use the COBLANG environment variable to set the locale information for the COBOL system. See the chapter NLS Support in your Programmer's Guide to Writing Programs.

Corrupt index file (Recoverable)

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.

Attempt to write on broken pipe (Recoverable)

Your program has created a process as a result of a DD_ logical filename 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.

File information missing for indexed file (Fatal)

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.

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

The logical filename is preceded by "%NLS%", but the program which OPENS the file has been compiled without the NLS directive set: the OPEN fails.

NLS support module not found (Fatal)

Ensure that cobnls.dle is present in utils.lbr, or that cobnls.dlw is present in a directory specified in COBDIR, or that cobnls.dll is present on the LIBPATH.

Indexed structure overflow (Fatal)

If you have tried to access an old format indexed file, you can run the Rebuild utility to check the consistency of this indexed file, and to construct a new indexed file if the old one was found to be corrupt. See your Programmer's Guide to File Handling for details of the Rebuild utility.

Attempt to divide by zero (Fatal)

Either recode your program so that you can trap the error with an ON SIZE ERROR clause, or run your program without the RTS O switch set, or recompile your program without the CHECKDIV"OSVS" directive set.

57  Host file status, not an RTS message

If you have COBFSTAT environment variable set to HOSTSTAT, this is a mainframe file status code "9x", where x is given by subtracting 48 from the error number.

Routine table overflow (Fatal)

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

File locked (Recoverable)

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.

Indexed file not open (Recoverable)

Open the file in the relevant access mode and then retry the unsuccessful file operation.

Record locked (Recoverable)

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 retry to gain access to the record without operator intervention.

Illegal argument to isam module (Fatal)

Contact Technical Support who will help you find the cause of your error and how it can be rectified.

Bad indexed file format (Fatal)

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 find the cause of your error and how it can be rectified.

No record found in indexed file (Fatal)

Contact Technical Support who will help you find the cause of the error and how it can be rectified.

Indexed data file name too long (Fatal)

Rename the file with a shorter filename, that is, one that is less than 10 characters in length.

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

You should manually remove all of the files that are still locked from the /isam directory before you can successfully run your program.

COBCONFIG syntax error (Fatal)

Check your syntax against your Object COBOL User Guide. You might have used incorrect syntax, or syntax that is not compatible with the type of RTS tuneable you are configuring (this could include assigning an illegal value to the RTS tuneable).

CALL convention not supported (Fatal)

See your Object COBOL User Guide for a list of supported CALL conventions.

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.

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.

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

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.

Null file name used in a file operation (Fatal)

You specified a data-name for a filename instead of a literal, and the data item contained only spaces when you tried to open the file.

Memory allocation error (Fatal)

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.

Dictionary error (Fatal)

Ensure that as much memory as possible is available during Animation by canceling any program you do not currently need to access.

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

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.

Failure to initialize data division (Fatal)

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

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.

Generated code not supported by this RTS (Fatal)

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

Incompatible Class Library and Run-time Environment versions (Fatal)

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.

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

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

Attempt to access item beyond bounds of memory (Fatal)

Memory access violation has been detected by your operating system.

Unexpected signal (Fatal)

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

Cannot allocate memory (Fatal)

You should try to reduce memory usage by canceling programs that are not in use, then try the operation that caused this message again.

Bad collating sequence (Fatal)

Please contact Technical Support who will help you to find the cause of the error and how it can be rectified.

Symbol not found (Fatal)

Check that your COBPATH has been set up correctly. If not, revise your COBPATH to include the program being called.

Symbol redefined (Fatal)

You can recode your application to remove the naming duplication. If you are not linking with a non-COBOL function, you can use the -e RTS switch (32-bit RTS only).

Symbol string table of zero size (Fatal)

Once the program has terminated you must correct your object file. If this does not work, contact Technical Support who will help you to find the specific cause of the error.

Symbol is not in TEXT section (Fatal)

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.

Coblongjmp() called below level of cobsavenv() (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 cobsavenv was. See your Object COBOL User Guide for details of cobsavenv and coblongjmp.

Unknown relocation type (Fatal)

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 find the specific cause of the error.

Attempt to access record zero of relative file (Recoverable)

You should ensure that the value in the RELATIVE KEY data item is greater than zero, then continue to run your program.

File closed with lock - cannot be opened (Recoverable)

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.

Record length or key data inconsistency (Recoverable)

Your program has a fault, so you probably should edit your code, then resubmit it to your COBOL system before running it again.

File not open - cannot be closed (Recoverable)

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.

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

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.

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.

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.

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

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.

Random read on sequential file (Recoverable)

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.

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.

PERFORM nested too deeply (Fatal)

When your program has terminated you should to recode your program to ensure that the GO TO in question jumps to an EXIT statement at the end of the PERFORM's range.

Illegal command line (Fatal)

Make sure that the interpreter is present to enable your system to pick up the commands correctly and then rerun your program.

Too many parentheses in compute statement (Fatal)

You should recode your program. We strongly advise you to break the relevant COMPUTE statement into a number of simpler statements.