Abend codes AJxx

Start of change
AJAA
Explanation:

The CREA/CREC transaction could not allocate the shared memory it required. The transaction will free all allocated memory and issue this abend.

System action:

The transaction is terminated.

User response:

Examine the trace to determine why the GETMAIN failed. If the CICS region was short on storage then take the necessary steps to correct this. If your region was not short on storage you may need help from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHADDRM

End of change
Start of change
AJAB
Explanation:

The CREA/CREC transaction could not free the shared memory it allocated.

System action:

The transaction is terminated.

User response:

Examine the trace to determine why the FREEMAIN failed. You may need help from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHADDRM

End of change
Start of change
AJAC
Explanation:

The CREA/CREC transaction browses the installed REQUESTMODELs. An attempt to start or continue the browse of the REQUESTMODELs failed with an unexpected return code.

System action:

The transaction is terminated.

User response:

Examine the trace to determine why the INQUIRE REQUESTMODEL call failed. You may need help from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHADDRM

End of change
Start of change
AJAD
Explanation:

The CREA/CREC transaction received an unexpected return code from an EXEC CICS call and could not continue.

System action:

The transaction is terminated.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHADDRM

End of change
Start of change
AJAE
Explanation:

The CREA/CREC transaction used the EXEC CICS SEND MAP call to display a BMS map. This call returned an expected return code.

System action:

The transaction is terminated.

User response:

Examine the trace to determine why the SEND MAP call. You may need help from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed. failed.

Modules:

DFHADDRM

End of change
Start of change
AJAF
Explanation:

The CREA/CREC transaction used the EXEC CICS RECEIVE MAP call to receive data from a BMS map. This call returned an expected return code.

System action:

The transaction is terminated.

User response:

Examine the trace to determine why the RECEIVE MAP call failed. You may need help from IBM to resolve this problem. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHADDRM

End of change
Start of change
AJAG
Explanation:

The CREA/CREC transaction must be invoked using the transaction ID of 'CREA' or 'CREC'. You are not able to use another transaction ID to invoke DFHADDRM (the program invoked for the CREA/CREC transaction).

System action:

The transaction is terminated.

User response:

Use CREA or CREC to invoke the CREA/CREC transaction.

Modules:

DFHADDRM

End of change
Start of change
AJA0
Explanation:

The native method SetAbendForCondition has been passed an invalid Resp value by the Wrapper class.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
AJCD
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHJCP

AJCE
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHJCP

AJCS
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the log manager (LM) domain. The domain that detected the original error provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHJCP

AJCT
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The domain that detected the original error provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHJCP

AJCU
Explanation:

A purge response has been received from either the log manager or or the recovery manager. The domain that detected the original purge condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHJCP

AJMB
Explanation:

The CICS-JVM interface has rejected an attempt to invoke a Java program to run under control of a JVM because a previous JVM for the same CICS task terminated abnormally. The CICS-JVM interface is unable to create a JVM to run the Java program.

This error occurs when the previous JVM was terminated because of a Java program invoking the Java system.exit method and because errors occurred during the subsequent JVM termination. A system.exit invocation causes a forced termination of the JVM and the LE/370 runtime environment.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine why the previous JVM termination failed. Wherever possible avoid the use of system.exit to return from Java programs.

Modules:

DFHAPLJ

Start of change
AJ01
Explanation:

The main method of the Java environment setup class, Wrapper, has been invoked without an an argument. Wrapper main expects the class name of the user's main to be passed as the first argument.

The callUserClass method of Wrapper detects this, sets return code INVALID_ARGUMENTS and invokes native method SetAbend to abend the task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
Start of change
AJ02
Explanation:

A CICS AbendError has been caught by the Java environment setup class, Wrapper.

The callUserClass method of Wrapper detects this, sets return code ABEND_RECEIVED and invokes native method SetAbend to abend the task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See related messages to determine the reason for the original abend.

Modules:

DFJCICS

End of change
Start of change
AJ03
Explanation:

A CicsConditionException has been caught by the Java environment setup class, Wrapper.

The callUserClass method of Wrapper detects this, sets return code CONDITION_RECEIVED and invokes native method SetAbendForCondition to abend the task. The appropriate default abend code for the condition should be issued but, if for some reason this is not possible, an AJ03 abend may be issued.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See related messages to determine the reason for the original CicsConditionException.

Modules:

DFJCICS

End of change
Start of change
AJ04
Explanation:

An unexpected error has been caught by the Java environment setup class, Wrapper, attempting to invoke the user class.

The callUserClass method of Wrapper detects this, sets return code UNEXPECTED_EXCEPTION and invokes native method SetAbend to abend the task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
Start of change
AJ05
Explanation:

An unhandled exception has been caught by the Java environment setup class, Wrapper, as an InvocationTargetException from the user class.

The callUserClass method of Wrapper detects this, sets return code INVOCATION_TARGET_EXCEPTION and invokes native method setAbend to abend the task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See related messages to determine the reason for the original Exception.

Modules:

DFJCICS

End of change
Start of change
AJ07
Explanation:

The Java environment setup class, Wrapper, has been unable to invoke the user's main method. The class whose name was passed as an input parameter to its CallUserClass method was not found.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

If your Java program has been bound using ET/390, check that the -main option correctly specifies, or defaults to, the name of the class containing your main method.

Check that CICS has been granted read permission to the target class and the entire HFS directory structure in which the class or Jar file is located.

Modules:

DFJCICS

End of change
Start of change
AJ09
Explanation:

The Java environment setup class, Wrapper, has been unable to invoke the user's main method. A public static method, taking either a CommAreaHolder or a String array as input, was not found in the class whose name was passed as an input parameter to the CallUserClass method of Wrapper.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that you have provided a main method, with an appropriate method signature, in the specified class. Also check that the target class explicitly uses the 'public' class modifier. If your Java program has been bound using ET/390, check that the -main option correctly specifies, or defaults to, the name of the class containing your main method.

Modules:

DFJCICS

End of change
Start of change
AJ10
Explanation:

The Java environment setup class, Wrapper, has detected that the user's class has used JDBC or SQLJ. It however has been unable to load the DB2 JDBC classes necessary to call back the JDBC/SQL driver for cleanup processing following completion of the user class.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
Start of change
AJ11
Explanation:

The Java environment setup class, Wrapper, has detected that the user's class has used JDBC or SQLJ. It however has been unable to find the DB2 JDBC static method to call back the JDBC/SQL driver for cleanup processing following completion of the user class.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
Start of change
AJ12
Explanation:

The Java environment setup class, Wrapper, has detected that the user's class has used JDBC or SQLJ. It however has been unable to invoke the DB2 JDBC static method to call back the JDBC/SQL driver for cleanup processing following completion of the user class.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFJCICS

End of change
Start of change
AJ99
Explanation:

The Java environment setup class, Wrapper, has detected an AbendException and issued setAbend. The abend code extracted from the AbendException is too long.

System action:

Task abnormal termination continues with the abend code set to AJ99

User response:

Correct the abend code String used to create the AbendException.

Modules:

DFJCICS

End of change [[ Contents Previous Page | Next Page Index ]]