Datasets:

testingllma

/

cicd

like 0

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

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.

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

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.

Malformed line-sequential file (Recoverable)

Rerun your program using the backup copy of that file.

Overlay loading error (Recoverable)

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.

Illegal intermediate code (Fatal)

You should resubmit your source program to your COBOL system, to try to obtain uncorrupted intermediate code.

Arithmetic overflow or underflow (Fatal)

You should recode your program to avoid this illegal operation.

Illegal character in numeric field (Fatal)

You must adjust your code so that no invalid data is used. You can locate the invalid numeric data in your code by setting the +F switch on, and animating your program until you receive this error. You might need to use one of the Compiler directives, BADSIGNS, HOST-NUMCOMPARE, SIGNCOMPARE or SPZERO

Run-Time subprogram not found (Fatal)

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.

Version number incompatibility (Fatal)

Tried to load a module whose format is invalid for this operating system.

Recursive COBOL CALL is illegal (Fatal)

You should recode your program.

Too many USING items (Fatal)

Once your program has terminated recode it with group items rather than elementary items before rerunning it.

Stack overflow (Fatal)

If the CHECKSTACK directive has been used, determine which call is at fault and edit the source to provide the correct number and size of parameters.

Illegal configuration information (Fatal)

Check that Adis or the External File Handler is is configured correctly. See your Programmer's Guide to Creating User Interfaces for details of how you can reconfigure Adis. See your Programmer's Guide to File Handling for details of how to configure the External File Handler.

System program not found (Fatal)

Ensure that all the system programs are available on the logged-in drive and copy those which are not currently present using your backup system disk. Once all the necessary system programs are available you can run your program.

Japanese operations illegal with this RTS (Fatal)

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.

Recursive non-MF PERFORM is illegal (Fatal)

You should either resubmit your program to your COBOL system with a parameter other than OSVS specified for the PERFORM-TYPE directive, or recode your program so that each PERFORM has its own unique return address before you resubmit it to your system with the MF parameter of the PERFORM-TYPE specified.

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

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. run your program again.

Imported file not found (Fatal)

Locate the missing file and ensure it is located on the default search path for your operating system.

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.

Attempt to cancel program failed (Fatal)

Locate the erroneous DLL and ensure that the EXIT LIST function is removed before you cancel the DLL. If you cannot recode the DLL, you can set the O RTS switch to force a logical cancel on the DLL.

Error during save (Fatal)

If the error is caused by a lack of space you can either delete some of the files which you no longer need on your current disk, or insert a new floppy disk to take the output from your program. You should then be able to rerun your program and save the information given by it.

End-of-file marker error (Fatal)

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.

Invalid parameter error (Fatal)

Revise your code to contain a parameter which is known by your system. That is, ensure that the parameter is in the first 64K of the Data Division.

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.

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

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.

ACCEPT/DISPLAY I-O error (Fatal)

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

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.

Run-time system not found on $COBDIR path (Fatal)

Ensure that the run-time system is on the path you have set up in the COBDIR environment variable. Alternatively, ensure that your COBOL system has been installed correctly. If it has not, you must reinstall your COBOL system.

Filename too large (Fatal)

You should recode your program to check the length of the file in error, and rename it with a shorter filename. You can then run your program again.

Terminal type not defined (Fatal)

Set up the necessary environment for your terminal.

Required terminal capability description missing (Fatal)

Add the missing entry to your terminal configuration database.

File size too large (Fatal)

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.

DELETE/REWRITE not preceded by a read (Fatal)

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.

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

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.

Screen handling system initialization error (Fatal)

If you are using a UNIX-type system, you must check that your terminfo file contains the correct entry for your terminal. If your terminfo file is corrupt, or your screen handling interface has not been correctly initialized, you must advise your system administrator of the problem, and he will take steps to try to correct it.

Operating System error code lies outside expected range (Fatal)

Contact Technical Support who will help you to find the specific cause of this error.

I-O error in paging system (Fatal)

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.

Exported functionality error (Fatal)

Ensure that all of your external assembler applications call and use run-time system functions correctly before you try to run your program again. If you are using a preprocessor as part of your COBOL system, you should use the software as a standalone preprocessor to isolate the problem areas.

CALL parameter not supplied (Fatal)

Recode your program to ensure that it contains all of the necessary parameters, or check that it is a valid caller.

Mainframe Pointer Manager (MFPM) module is required but not loaded (Recoverable)

Ensure that the file mfpm.dle (for DOS) or mfpm.dlw (for Windows) exists in a directory specified by the COBDIR environment variable

or (for OS/2 only) that mfpm.dll exists in a directory that is on your LIBPATH.

Invalid mainframe pointer value (Fatal)

Check your program's logic and recode the appropriate statements.

Reading unwritten data from memory (Fatal)

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

Machine does not exist (Recoverable)

Make sure the machine is connected to the network and is on-line, then try to access it again.

Error in multi-user system (Fatal)

Retry the unsuccessful operation. If the error persists, contact Technical Support who will help you to find the specific cause of this error.

Network communication error (Recoverable)

Your program should continue to execute after you have received this error but results might be undefined.

File is closed with lock (Fatal)

Recode your program to avoid opening a file which has previously been closed with lock.

Program not executable by run-time system (Fatal)

If your object file is incompatible with the current version of either your COBOL run-time library or your run-time system, you should relink with the current version of your COBOL run-time library.

Too many locks (Recoverable)

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.

GO TO has not been ALTERed (Fatal)

Close any files which might be open, execute a STOP RUN statement and then edit your program to avoid such illegal operations.

Cannot ANIMATE a program running COMMUNICATIONS (Fatal)

You should run your program without the aid of Animator.

Cannot initialize the named communications device (Fatal)

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

Incompatible host for native code file (Fatal)

You must resubmit your program to your COBOL system.

Malformed MULTIPLE REEL/UNIT file (Fatal)

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

Operating system shared file limit exceeded (Recoverable)

Close some of the open shared files you are no longer accessing and retry the file operation.

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

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

SORT/MERGE error: see status keys (Fatal)

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.

SORT/MERGE error: see status keys (Fatal)

Either set TMP to point to a directory that does exist, or unset TMP.

Dynamic load error - program component missing (Fatal)

Increase your operating system file handles limit.

EXTERNAL file definition inconsistent

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.

EXTERNAL data definition inconsistent (Fatal)

Make sure that both or all of your programs define the size of the external data item as being the same.

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

Recompile your program to use the callable SORT module (EXTSM).

Error in animator communications channel (Fatal)

Copy the animated program file to a different directory and try animation.

Animated program has terminated unexpectedly (Fatal)

Run your program without animation to determine if it runs successfully; if so, animate the program without cross-session or intrasession animation.

STOP RUN encountered during GNT animation (Informational)

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

Shared run-time system initialization failure (Informational)

Ensure that your application calls the cobinit() function before executing any COBOL modules.

Object reference not valid (Fatal)

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.

Cannot instantiate an abstract class (Fatal)

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

Could not resolve DoesNotUnderstand message (Fatal)

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.

Class could not be loaded (Fatal)

Check the definition of the class.

Keyboard interrupt to ANIMATOR during ACCEPT (Fatal)

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

BeanCreationException: Error creating bean with name 'exampleBean'

The bean creation process failed due to misconfiguration or dependency issues.

Check the bean configuration and ensure all dependencies are properly set up.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: BeanCreationException: Error creating bean with name 'exampleBean' ### Input The bean creation process failed due to misconfiguration or dependency issues. ###Response Check the bean configuration and ensure all dependencies are properly set up.

NoSuchBeanDefinitionException: No qualifying bean of type 'ExampleService' available

Spring couldn't find a bean of the specified type.

Ensure that the bean is defined and registered with the correct type in the Spring container.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: NoSuchBeanDefinitionException: No qualifying bean of type 'ExampleService' available ### Input Spring couldn't find a bean of the specified type. ###Response Ensure that the bean is defined and registered with the correct type in the Spring container.

NullPointerException: null

Trying to access a null reference.

Check the code where the null pointer is being accessed and handle null values appropriately.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: NullPointerException: null ### Input Trying to access a null reference. ###Response Check the code where the null pointer is being accessed and handle null values appropriately.

MappingException: Unknown entity: com.example.EntityClass

Hibernate couldn't find the specified entity class.

Make sure the entity class is properly annotated with @Entity and is included in the component scan.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: MappingException: Unknown entity: com.example.EntityClass ### Input Hibernate couldn't find the specified entity class. ###Response Make sure the entity class is properly annotated with @Entity and is included in the component scan.

CannotGetJdbcConnectionException: Could not get JDBC Connection

Unable to establish a database connection.

Check the database configuration and ensure the database server is running.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: CannotGetJdbcConnectionException: Could not get JDBC Connection ### Input Unable to establish a database connection. ###Response Check the database configuration and ensure the database server is running.

NumberFormatException: For input string: "abc"

Trying to parse a non-numeric string into a numeric type.

Ensure the input string is valid before attempting to parse it into a numeric type.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: NumberFormatException: For input string: "abc" ### Input Trying to parse a non-numeric string into a numeric type. ###Response Ensure the input string is valid before attempting to parse it into a numeric type.

NoHandlerFoundException: No handler found for GET /example

Spring couldn't find a suitable handler for the requested URL.

Check the request mapping and controller method to ensure it matches the URL pattern.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: NoHandlerFoundException: No handler found for GET /example ### Input Spring couldn't find a suitable handler for the requested URL. ###Response Check the request mapping and controller method to ensure it matches the URL pattern.

DataAccessException: SQL [SELECT * FROM example_table]

The database table does not exist

The SQL query is referencing a non-existent table.

Verify the database schema and table name to ensure they match with the query.

InvalidDataAccessApiUsageException: The given id must not be null

Trying to perform an operation with a null ID.

Ensure the ID is set before performing any database operations.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: InvalidDataAccessApiUsageException: The given id must not be null ### Input Trying to perform an operation with a null ID. ###Response Ensure the ID is set before performing any database operations.

MethodArgumentTypeMismatchException: Failed to convert value of type 'java.lang.String' to required type 'int'

Data type mismatch while binding request parameters.

Check the data types of request parameters and the corresponding method parameters in the controller.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: MethodArgumentTypeMismatchException: Failed to convert value of type 'java.lang.String' to required type 'int' ### Input Data type mismatch while binding request parameters. ###Response Check the data types of request parameters and the corresponding method parameters in the controller.

HttpMessageNotReadableException: Required request body is missing

The request body is empty or not well-formed.

Ensure the request contains the required data in the request body.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: HttpMessageNotReadableException: Required request body is missing ### Input The request body is empty or not well-formed. ###Response Ensure the request contains the required data in the request body.

ConstraintViolationException: could not execute statement

SQL [n/a]

constraint [null]

HttpMediaTypeNotSupportedException: Content type 'application/xml' not supported

The server doesn't support the requested media type in the request headers.

Use a supported content type or update the server to handle the requested media type.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: HttpMediaTypeNotSupportedException: Content type 'application/xml' not supported ### Input The server doesn't support the requested media type in the request headers. ###Response Use a supported content type or update the server to handle the requested media type.

TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'java.util.Date'

Data type mismatch while binding form data.

Ensure the data types of form fields match the corresponding model attributes.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: TypeMismatchException: Failed to convert property value of type 'java.lang.String' to required type 'java.util.Date' ### Input Data type mismatch while binding form data. ###Response Ensure the data types of form fields match the corresponding model attributes.

ClassNotFoundException: com.example.missing.Class

The specified class is missing from the classpath.

Check the classpath configuration and ensure the required class is available.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: ClassNotFoundException: com.example.missing.Class ### Input The specified class is missing from the classpath. ###Response Check the classpath configuration and ensure the required class is available.

IOException: Stream closed

Trying to read from a closed input stream or write to a closed output stream.

Ensure the stream is open before attempting to read or write data.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: IOException: Stream closed ### Input Trying to read from a closed input stream or write to a closed output stream. ###Response Ensure the stream is open before attempting to read or write data.

BeanInstantiationException: Failed to instantiate [com.example.BeanClass]: No default constructor found

The bean class doesn't have a default constructor.

Add a public default constructor to the bean class or use constructor-based dependency injection.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: BeanInstantiationException: Failed to instantiate [com.example.BeanClass]: No default constructor found ### Input The bean class doesn't have a default constructor. ###Response Add a public default constructor to the bean class or use constructor-based dependency injection.

TransactionSystemException: Could not commit JPA transaction

An error occurred while committing the JPA transaction.

Check the logs for more specific error messages and resolve the underlying issue.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: TransactionSystemException: Could not commit JPA transaction ### Input An error occurred while committing the JPA transaction. ###Response Check the logs for more specific error messages and resolve the underlying issue.

IllegalStateException: Cannot forward after response has been committed

Attempting to forward the request after sending a response to the client.

Ensure that the forward or redirect is performed before sending any response to the client.

Below is an instruction that describe a task, paired with an input that provides further context. Write a response that appropriately completes the request. ### Instruction: IllegalStateException: Cannot forward after response has been committed ### Input Attempting to forward the request after sending a response to the client. ###Response Ensure that the forward or redirect is performed before sending any response to the client.