com.ibm.ejs.ns.jndi.CNInitialContextFactory
com.ibm.websphere.naming.WsnInitialContextFactory
An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.
The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.
Look up the MVS code, if there is one, in the relevant MVS codes manual.
Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.
If module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.
If you cannot continue without the full use of module modname you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHEJ**
XMEOUT Parameters:
applid,
aaa/bbbb,
X'
offset',
modname
An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.
An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.
CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.
If the message recurs or if you cannot continue without the full use of module modname, you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHEJ**
XMEOUT Parameters:
applid,
X'
code',
modname
A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Notify the system programmer. If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.
Since some CICS functions can use a lot of processor time, this message may have been caused by a long-running function, so there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that module modname in the message is terminated and CICS continues.
But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.
If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently, but you can change the ICVR time interval temporarily online, using the CEMT transaction.
If raising the ICVR time does not solve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHEJ**
XMEOUT Parameters:
applid,
X'offset',
modname
The Enterprise Java (EJ) domain initialization has started. Java is a trademark of Sun Microsystems, Inc.
Initialization continues.
None.
Console
DFHEJDM
XMEOUT Parameter:
applid
The Enterprise Java (EJ) domain initialized correctly. CICS will accept CorbaServer, DJar and Bean operations.
Initialization continues.
None.
Console
DFHEJDM
XMEOUT Parameter:
applid
The Enterprise Java (EJ) domain did not correctly initialize.
An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.
Message DFHME0116 is normally produced containing the symptom string for this problem.
This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.
CICS may not have been terminated. If the message occurs once and the domain is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.
If the message recurs or if you cannot continue without the full use of Enterprise Java domain, you should bring CICS down in a controlled shutdown.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHEJDM
XMEOUT Parameter:
applid
A request has been made to open file DFHEJDIR. The request has failed because the RDO file definition for this file does not specify RECOVERY(BACKOUTONLY).
File DFHEJDIR remains closed.
Change the RDO file definition for DFHEJDIR to RECOVERY(BACKOUTONLY). Reinstall the file and the CorbaServer.
Console
DFHEJDI
XMEOUT Parameter:
applid
An informational message has been issued by a Java class running in a CICS JVM that has not been recognized as a CICS message. The insert JRAS_informational_message contains the message that was issued.
Processing continues.
An exception trace giving the name of the class and method issuing the message along with the message text will be made.
If the message is issued by an IBM supplied class then you may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CJRM
com.ibm.cics.ras.CICSMessageService
XMEOUT Parameters:
date,
time,
applid,
JRAS_informational_message
A warning message has been issued by a Java class running in a CICS JVM that has not been recognized as a CICS message. The insert JRAS_warning_message contains the message that was issued.
Processing continues.
An exception trace giving the name of the class and method issuing the message along with the message text will be made.
If the message is issued by an IBM supplied class then you may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CJRM
com.ibm.cics.ras.CICSMessageService
XMEOUT Parameters:
date,
time,
applid,
JRAS_warning_message
An error message has been issued by a Java class running in a CICS JVM that has not been recognized as a CICS message. The insert JRAS_error_message contains the message that was issued.
Processing continues.
An exception trace giving the name of the class and method issuing the message along with the message text will be made.
If the message is issued by an IBM supplied class then you may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CJRM
com.ibm.cics.ras.CICSMessageService
XMEOUT Parameters:
date,
time,
applid,
JRAS_error_message
The CorbaServer has been added to the Enterprise Java domain by placing it in the chain of CorbaServer Control Blocks. However, until the CorbaServer is resolved, it is not available for use.
Processing continues. The CorbaServer will be resolved at a later stage.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer CorbaServer_name was not added to the Enterprise Java domain. This error is most likely caused by an attempt to add a duplicate CorbaServer.
Processing continues.
Examine the exception trace entry that shows the cause of the error.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
After the CorbaServer has been created, it undergoes the Resolution process in a separate transaction. However, this transaction was not successfully attached. Another attachment of the Resolution Transaction will occur (if this failure does not re-occur) when the next CorbaServer is created, and hence this failure may be thereby corrected.
Processing continues.
Examine the exception trace entry that shows the cause of the attachment error.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
transaction_name
A CorbaServer Control Block has been deleted and removed from the chain of CorbaServers held within the EJ domain. Consequently, the CorbaServer is no longer available for use.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
Resolution for CorbaServer CorbaServer_name has failed. The Resolution process was attempting to create the Shelf for this CorbaServer.
The CorbaServer is placed into the DISABLED state and cannot be used.
Check that the CorbaServer's shelf directory does exist and that the CICS region id has permission to read and write to that directory. If the problem persists you may need to use the trace facility to determine the cause of the problem.
CorbaServer CorbaServer_name must be reenabled before processing can continue.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
A failure occurred updating the Global Catalog for CorbaServer CorbaServer_name.
The state is not updated in the Global Catalog for the CorbaServer.
Discard and reinstall the CorbaServer. If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
An update to the Global Catalog for CorbaServer CorbaServer_name, to record that Resolution has occurred failed when the read for update operation returned invalid data.
The state is not updated in the Global Catalog for the CorbaServer.
The CorbaServer resource should be discarded and reinstalled. If the problem persists you may have to use the trace facility to determine the cause of the problem.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
An update of the Global Catalog for CORBASERVER CorbaServer_name, to record that Resolution has occurred, failed when the read for update operation returned an invalid CORBASERVER.
The state is not updated in the Global Catalog for the CorbaServer.
The CORBASERVER resource should be discarded and reinstalled.
If the problem persists you may have to use the trace facility to determine the cause of the problem.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
An update to the state of CorbaServer CorbaServer_name to record the status of the Resolution process has failed. The Resolution process was attempting to create the Shelf for this CorbaServer.
Processing continues with CorbaServer CorbaServer in an incorrect state.
Ensure that the region id under which CICS is running has write permission to the area of the HFS directory structure in which the shelf directory should be created. Also check that there is sufficient free space for the directory to be created.
The CorbaServer should be discarded and reinstalled.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The Resolution of CorbaServer CorbaServer_name involved with the Object Store file file_name has failed.
The CorbaServer is put into the DISABLED state.
The most likely problem is that the file definition for VSAM file file_name has not been installed or is incorrectly defined. Verify that the both the file and the file definition have been created with appropriate attributes. Check that the resource definition for the file has been installed. Sample definitions for files DFHEJDIR and DFHEJOS are available in groups DFHEJVS, DFHEJCF and DFHEJVR.
Discard and reinstall the resource. If the problem persists you may need to use the trace service to find the failing object store operation.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name,
file_name,
store_name
An update of CorbaServer CorbaServer_name's state to record the status of the Resolution process has failed. The Resolution process failed opening an Object Store file.
Processing continues with the CorbaServer in an incorrect state.
The CorbaServer should be discarded and reinstalled.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
CORBASERVER CorbaServer_name was being installed but the TCPIPSERVICE tcpipservice named is not installed.
The CORBASERVER is not installed. Processing continues.
Examine the CORBASERVER definition to check that the correct TCPIPSERVICE has been named and then delete the CORBASERVER, install the TCPIPSERVICE first and then retry the install of the CORBASERVER.
The TCPIPSERVICE needs to be installed in the listener region AND where the CORBASERVER is installed (AOR) if they are separate regions. If the CORBASERVER is in a separate region, the listener needs to have IIOPLISTENER=(YES) specified in the System Initialization Table (SIT) and the AOR needs to have IIOPLISTENER=(NO) specified.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name,
tcpipservice
CorbaServer CorbaServer_name was being installed but the TCPIPSERVICE TCPIPSERVICE named does not have the same authenticate value as the TCPIPSERVICE.
The CorbaServer is installed but becomes unusable. Processing continues.
Examine the CORBASERVER definition to check that the correct TCPIPSERVICE has been named and then correct the authenticate parameter in the TCPIPSERVICE. Delete the CorbaServer then reinstall the TCPIPSERVICE and the CorbaServer.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name,
tcpipservice
CorbaServer CorbaServer_name was being installed but the TCPIPSERVICE TCPIPSERVICE named for SSLUNAUTH has an SSL setting of NO. The TCPIPSERVICE named must have an SSL value of YES or CLIENTAUTH.
The CorbaServer becomes unusable. Processing continues.
Examine the CORBASERVER definition to check that the correct TCPIPSERVICE has been named and then change the SSL parameter in the TCPIPSERVICE to YES or CLIENTAUTH. Delete the CorbaServer then reinstall the TCPIPSERVICE and the CorbaServer.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name,
tcpipservice
CorbaServer CorbaServer_name was being installed but the TCPIPSERVICE TCPIPSERVICE named for UNAUTH has an SSL setting of YES or CLIENTAUTH. The TCPIPSERVICE named must have an SSL value of NO.
The CorbaServer becomes unusable. Processing continues.
Examine the CORBASERVER definition to check that the correct TCPIPSERVICE has been named and then change the SSL parameter in the TCPIPSERVICE to NO. Delete the CorbaServer then reinstall the TCPIPSERVICE and the CorbaServer.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name,
tcpipservice
A function needs to ensure that a CorbaServer is available for use, so it is going to wait until the CorbaServer becomes available (it enters the INSERVICE State).
This message will usually appear while Resolution is proceeding (or pending) for the CorbaServer. However, it can also occur after this time during consistency processing for the items associated with the CorbaServer.
The transaction enters a Wait state until the CorbaServer becomes INSERVICE.
If the Wait is associated with consistency processing, it is likely that this delay will be short.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer was not found during the availability wait. The CorbaServer has probably been deleted via CEMT while another transaction was waiting for the CorbaServer to be available.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer is now available and so the availability wait has successfully ended.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer entered the UNUSABLE state and so will never become available for use. Consequently, the availability wait has ended with this error condition.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer entered the DISABLED state and so will never become available for use. Consequently, the availability wait has ended with this error condition.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer availability wait ended in error. This is probably due to the transaction being cancelled via CEMT.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer has been set to be enabled. This operation may not complete immediately.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer has been set to be disabled. This operation may not complete immediately.
Processing continues.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
A DJar has been created and added to the chain of DJars. However, it is not available for use until it has been resolved.
Processing continues. The DJar will be resolved at a later stage.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
DJar DJar_name was not created. This error is usually caused by an attempt to create a DJar with the same name as an already existing DJar.
Processing continues.
Rename the jar file and DJar resource and retry the operation.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
After the DJar has been created, it undergoes the Resolution process in a separate transaction. However, this transaction was not successfully attached. Another attachment of the Resolution Transaction will occur (if this failure does not re-occur) when the next DJar is created, and hence this failure may be thereby corrected.
Processing continues.
Examine the exception trace entry that shows the cause of the attachment error.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
transaction_name
The DJar was successfully deleted from the chain of DJars. The Beans contained in DJar DJar_name have also been deleted.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
The Resolution for DJar DJar_name, involving copying the DJar to the Shelf, has failed.
The DJar is put into the UNUSABLE state and cannot be used.
Check that the CICS region id has permission to write to the HFS shelf directory and that there is sufficient free space available.
DJar DJar_name should be discarded and reinstalled.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
The updating of the Global Catalog entry for the DJar DJar_name failed when the read for update operation, to record the fact that Resolution has occurred, was executed. The state is not updated in the Global Catalog for the DJar; so, upon the next warm restart processing will not be as expected.
The DJar is put into the UNUSABLE state and cannot be used.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The updating of the Global Catalog entry for DJar DJar_name, to record the fact that Resolution has occurred, failed when the read for update operation returned invalid data. The state is not updated in the Global Catalog for the DJar; so, upon the next warm restart processing will not be as expected.
The DJar is put into the UNUSABLE state and cannot be used.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The updating of the Global Catalog entry for DJar DJar_name, to record the fact that Resolution has occurred, failed when the read for update operation returned an invalid DJar. The state is not updated in the Global Catalog for the DJar; so, upon the next warm restart processing will not be as expected.
The DJar is put into the UNUSABLE state and cannot be used.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The updating of the state, to record the status of Resolution processing, for DJar DJar_name has failed. The Resolution process was attempting to copy the Djar to the Shelf.
Processing continues with the DJar in an incorrect state.
Check that the CICS region id has write permission to the HFS shelf directory and that there is sufficient space available for the write operation to succeed.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
All Beans within DJar DJar_name were correctly loaded. However, an error occurred while making the Beans within this DJar available for use during Resolution.
A System error has occurred which probably does not have anything to do with the DJar or the Beans themselves.
The DJar is put into the UNRESOLVED state and is not available for use. An attempt is made to delete any Beans associated with the DJar.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
An error occurred while installing the Beans from DJar DJar_name during the Bean copying phase of Resolution.
The most probable reason is that an attempt was made to install a duplicate Bean twice within the scope of the CorbaServer. In other words the duplicate Bean occurs in more than one DJar.
The partially processed Beans within the DJar are deleted and the DJar is put into the UNRESOLVED state.
Investigate why the Beans within the DJar within the scope of the CorbaServer caused this error to occur. In the most likely case, check that the contents of the DJar are not already present within the scope of the CorbaServer (for example, copying a Bean and then using both copies).
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
Beans are being deleted due to an error in the Resolution process which was loading Beans from DJar DJar_name. This deletion has succeeded.
Processing continues.
A previous message should explain why the Bean failed to install.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
Beans are being deleted due to an error in the Bean Resolution process for DJar DJar_name. However, this deletion of Beans has failed.
Processing continues.
A previous message should explain why the Bean failed to install.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name,
CorbaServer_name
The updating of the state, to record the status of Bean Resolution processing, for DJar DJar_name has failed. The Bean Resolution process consists of loading Beans from the DJar.
Processing continues with the DJar in an incorrect state.
Discard and reinstall the DJar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
A function needs to ensure that a DJar is available for use, so it is going to wait until this DJar becomes available by entering the INSERVICE state).
This message will usually be generated while the DJar is awaiting or undergoing Resolution Processing. However, it can also occur during consistency processing of items associated with the DJar.
The transaction enters a Wait state until the DJar is INSERVICE.
If the Wait is due to consistency processing, the delay is likely to be small.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar was not found during the availability wait. The DJar has probably been deleted via CEMT while another transaction was waiting for the DJar to be available.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar is now available and so the availability wait has successfully ended.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar entered the UNUSABLE state and so will never become available for use. Consequently, the availability wait has ended with this error condition.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar entered the UNRESOLVED state and so will never become available for use. Consequently, the availability wait has ended with this error condition.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar availability wait ended in error. This is probably due to the transaction being cancelled via CEMT.
Processing continues.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
A function needs to ensure that all the Beans contained within DJars associated with a CorbaServer are present. Thus, it is going to wait until all DJars associated with the CorbaServer have been resolved (they all enter the INSERVICE state).
The transaction enters a Wait state until the all the DJars associated with the CorbaServer enter the INSERVICE state.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
All Beans contained within the DJars associated with this CorbaServer are present. This means that the CorbaServer and all associated DJars are in the INSERVICE state.
None.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The waiting has ended without all Beans contained within the DJars associated with this CorbaServer being present. This will probably be a side effect of a previous error in DJar or CorbaServer processing.
This could be a side effect of the CorbaServer being deleted or in the UNUSABLE state, or a DJar being in the UNUSABLE or UNRESOLVED state, or the wait being cancelled via CEMT.
None.
Examine the exception trace entry showing the failure of the operation which caused the wait to end in error.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The Bean contained in DJar DJar_name and associated with the named CorbaServer has not been created because the CorbaServer CorbaServer_name was not found. The CorbaServer was probably deleted via CEMT while the Bean loading phase of the DJar Resolution was in progress.
Processing continues.
The owning DJar should be deleted and reinstalled when CorbaServer CorbaServer_name is present.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean, contained in the named DJar and associated with the named CorbaServer, has not been created because the CorbaServer was not in the INSERVICE state.
Processing continues.
The DJar should be deleted.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean contained in the DJar DJar_name and associated with the named CorbaServer has not been created because the DJar was not found. The DJar was probably deleted via CEMT while the Bean copying phase of the DJar Resolution was in progress.
Processing continues.
None.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean, contained in the named DJar and associated with the named CorbaServer, has not been created because the DJar was not in the RESOLVING state.
Processing continues.
This indicates some sort of internal race condition and should not occur.
You may need to contact your IBM service representative.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean, contained in the named DJar and associated with the named CorbaServer, has not been created because the Bean was already defined. This probably means that an attempt was being made to process a copy of an already defined DJar.
Processing continues.
The DJar should be deleted.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean, contained in the named DJar and associated with the named CorbaServer, has not been created because the Bean was already known within the namespace of the CorbaServer.
This probably means that an attempt was being made to process a copy of an already defined DJar.
Another possibility is that a Bean with the same name is present within two different DJars. Within the scope of a CorbaServer, all the Beans within all the DJars associated with the CorbaServer must be unique.
Processing continues.
The DJar should be deleted.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The Bean, contained in the named DJar and associated with the named CorbaServer, has not been created.
Processing continues.
A prior message will usually indicate the cause of the error. The DJar should be deleted.
CEJL
DFHEJBG
XMEOUT Parameters:
date,
time,
applid,
userid,
Bean_name,
DJar_name,
CorbaServer_name
The portion of the Enterprise Java (EJ) Domain which deals with CorbaServers, DJars and Beans has not correctly initialized. This EJ function is not available.
This message indicates a system error while creating the Elements part of the EJ Domain. This processing manipulates CorbaServers, DJars and Beans. This implies that an EJ Gate was not created or a GETMAIN for required areas failed. A failure to recover a CorbaServer or a DJar upon a warm restart is also a possibility.
All EJ elements function is unavailable. However, other components of the EJ domain (such as Object Store) may be available.
This is a system-related failure and an exception trace entry will indicate why the EJ domain has failed to install.
Console
DFHEJGE
XMEOUT Parameter:
applid
A prior Resolution transaction (CEJR) failed and left a CorbaServer in the INITING state.
The CorbaServer is put into the DISABLED state in order to prevent its use.
A prior message should indicate the cause of the previous error.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
A prior Resolution transaction (CEJR) failed and left a CorbaServer in an intermediate state.
The CorbaServer will be put into the DISABLED state in order to prevent its use.
Examine the message log to determine why the CorbaServer Resolution failed. The CorbaServer should either be discarded or reenabled.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer CorbaServer_name failed to complete the part of the Resolution process which involves creation of the shelf onto which components associated with the CorbaServer are placed.
The CorbaServer is put into the DISABLED state.
Check that the CICS region id has write permission to the shelf HFS directory structure.
The CorbaServer should be discarded and reinstalled.
If the problem persists you may have to use the trace facility to determine the cause of the problem.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer CorbaServer_name has successfully completed the part of the Resolution process which involves opening CorbaServer related Object Store files. The CorbaServer CorbaServer_name is now accessible.
Processing continues.
None.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
The CorbaServer CorbaServer_name failed to complete the part of the Resolution process which involves opening the CorbaServer related Object Store files.
The CorbaServer is put into the DISABLED state.
Discard and reinstall the CorbaServer.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer_name
A prior Resolution transaction (CEJR) failed and left a DJar in the INITING state.
The DJar will be put into the UNUSABLE state to prevent its use.
A prior message will usually indicate the cause of the previous error. Discard and reinstall the Djar.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
A prior Resolution transaction (CEJR) failed and left a DJar in the RESOLVING state.
The DJar will be put into the UNRESOLVED state to prevent its use.
A prior message will usually indicate the cause of the previous error. Discard and reinstall the CorbaServer.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
DJar DJar_name failed to Resolve. The Resolution process failed while attempting to copy this DJar to the Shelf.
The DJar has been put into the UNUSABLE state.
Check that the CICS region id has permission to write to the HFS shelf directory structure. Discard and reinstall the CorbaServer.
If the problem persists you may need to use the trace facility to determine the cause of the problem.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The DJar DJar_name has correctly Resolved. This means that the Resolution process successfully loaded all the Beans from this DJar. DJar DJar_name and all the Beans which are contained in the DJar are now accessible and ready for use. This message does not imply that the Beans have been published. If the DJar has been published then CICS is now ready to accept requests for the Beans.
Processing continues.
None.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
DJar DJar_name failed to Resolve. The Resolution process failed while attempting to load the Beans from this DJar because the Beans contained within the DJar were invalid.
The Djar is put into the UNRESOLVED state.
A prior message should describe the error in the DJar. Fix this error and then reinstall the DJar.
CEJL
DFHEJIO
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
The EJ domain attempted to invoke the Enterprise Java event URM module but failed with a code supplied as reason.
Exception trace point 6000 is issued. Enterprise resource processing continues.
Possible causes of the problem and an indication of how to solve them are given in the following list of reason code meanings:
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
module,
X'reason
'
Installation of a DJar has failed because either the HFS file referred to by the DJar definition could not be found or the security permissions on HFS prevented CICS from opening it.
Processing continues, but this particular DJar is not installed.
Check that the HFS filename defined in the DJar definition is correct and that the file exists on HFS. Also check the permissions on the jar file and the permissions on the directory hierarchy in which it can be found.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_name,
DJar_name
There was an HFS problem when attempting to remove a .jar file from the Shelf directory.
Processing continues and the DJar object is discarded, but CICS was unable to tidy up HFS.
Check the permissions on the Shelf directory and .jar file described in the message to ensure CICS has access. The file can then either be removed manually or install of a subsequent DJar definition with the same name overwrites the file.
CEJL
com.ibm.cics.ejs.csi.commands.DiscardDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_file_name,
shelf_partition
Whilst installing a DJar, CICS was unable to open a file on the shelf for writing.
Processing continues, but this DJar will not be installed.
Check the permissions for the shelf directory specified for the related CORBASERVER into which this DJar is being installed. CICS should be able to read and write to all files and directories within that shelf directory.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_file_name,
djar_name
The container was attempting to process a .jar file, looking for enterprise beans. The container was working with the copy of the .jar file that is held on the Shelf, not the original HFS .jar file described in the DJar definition.
Processing continues, but this particular DJar is not installed.
Check the validity of the .jar file referred to in the DJar definition. Check it has a valid deployment descriptor and the generated code contained within the jar file is correct. The CICS deployment tooling can be used to check the deployment descriptor and perform the code generation step if it is suspected that the generated code within the jar is incorrect.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar_name
To publish a home IOR for a bean to JNDI, it is necessary to obtain a remote reference for that bean from the container. This message indicates there was a problem retrieving the reference from the container.
Processing continues, but this particular bean does not have its home published to JNDI.
Check the validity of the .jar file referred to in the DJar definition. Check it is fully deployed with an ASCII manifest file.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name
Before publishing a home for a bean in JNDI, the subcontext hierarchy described in the CorbaServer definition must exist. This informational message indicates that part of that hierarchy does not exist and is being created.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
jndi_subcontext
After a home for a bean has been unbound from JNDI, it is possible that the namespace can be tidied up. CICS attempts to remove the hierarchy of subcontexts described in the CorbaServer definition. It only deletes a subcontext if it is empty.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
jndi_subcontext
The home IOR for a bean may be written to the HFS Shelf. This message indicates that CICS had a problem in attempting to write to the Shelf.
Processing continues, but this particular bean does not have its home published to the Shelf.
Check the permissions of the Shelf directory. If there already exists an IOR for the bean in the Shelf directory, check its permissions. CICS must have write access to the directory and to overwrite any files that might exist.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
shelf_partition
CICS has successfully published the home for the bean in JNDI. The location where the home is bound, and hence where the home can be looked up, is also supplied in the message.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_server,
jndi_location
CICS is publishing the home for the bean on the Shelf. The location where the home is being written is supplied in the message as a directory and filename.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
shelf_partition,
file_name
CICS has successfully retracted the home for a bean from JNDI. The JNDI location that is being unbound is supplied in the message. Once this message has appeared, clients are no longer able to look up the bean home at this location.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_server,
jndi_location
CICS is retracting the home for the bean from the Shelf. When retracting bean homes from the Shelf, retraction means deletion of the IOR file object created at publish.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
shelf_partition,
file_name
CICS is attempting to retract the home of a bean from JNDI. However, the home has not been found at the expected location in JNDI. This is usually due to a previous retraction having removed the home already.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_location
Installation of a DJar has failed because although the HFS file referred to by the DJar definition exists, it cannot be opened for reading by CICS.
Processing continues, but this particular DJar is not installed.
Check the permissions on the HFS file referred to by the DJar definition. Change the permissions if necessary to enable reading by CICS.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_name,
DJar_name
Whilst installing a DJar, CICS found a file on the shelf of the same name that it wanted to use when copying the users source deployed jar. CICS was unable to delete that file.
Processing continues, but this particular DJar is not installed.
Check the permissions of the shelf directory for the CORBASERVER and the permissions of the HFS file that the CICS message describes as already existing on the shelf. CICS should normally have the ability to read and write to all directories and files that exist under the directory defined as the CORBASERVERs shelf.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_file_name,
djar_name
During install of a DJar, CICS encountered an exception reading the HFS file described in the DJar definition.
Processing continues, but this particular DJar is not installed.
This is a very unusual situation. The file was found to exist and CICS had read permission, but a problem occurred whilst reading it. Retry the install operation.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_file_name,
djar_name
During install of a DJar, CICS encountered an exception writing the HFS file described in the DJar definition.
Processing continues, but this particular DJar is not installed.
This is usually due to running out of space in the filesystem. Check the size of the filesystem where the shelf is defined to exist for the CORBASERVER into which the DJar is being installed.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
hfs_file_name,
djar_name
The Java classloader responsible for loading Enterprise Beans was asked to load a class and was unable to locate it.
Processing stops. The request processor reporting the error shuts down, returning an exception to the client.
If the class is part of an Enterprise Bean, check the class exists in the deployed jar file you have named on the DJar definition. If it is a utility class used by an Enterprise Bean, check the utility class is on the user application classpath.
CEJL
com.ibm.cics.ejs.csi.DJarClassLoader
XMEOUT Parameters:
date,
time,
applid,
userid,
class_name
CICS is only able to process beans whose names are composed of characters from a specific set. This set being a subset of those allowable in the deployment descriptor.
Processing continues, but none of the beans from this DJar are installed.
Check the names of your beans against the allowable character set.
CEJL
com.ibm.cics.ejs.csi.CICSBeanMetaDataStore
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name
This message indicates that a bean installed in CICS contains generated code at the incorrect level. This can happen if, for example, Visualage for Java has been used to fully deploy a bean for use in CICS, the generated code produced by Visualage is not of the correct level (it is EJB 1.0 level code).
Processing against this bean stops and the initiating method request fails.
Use the CICS deployment tool to generate code at the correct EJB level for all the beans installed in the named corbaserver.
CEJL
com.ibm.cics.ejs.csi.DJarClassLoader
XMEOUT Parameters:
date,
time,
applid,
userid,
corbaserver
CICS has failed to publish the home of the bean in JNDI. The location where the home was being bound, and the server which was being used are included in the message.
None.
Check that the JNDI server named in the message is working.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_server,
jndi_location
The HFS file named in the DJar definition contains a deployed Enterprise Bean whose name conflicts with a bean already installed in the CorbaServer.
The DJar named in the message is not installed. None.
Change the name of the bean in the named DJar so that it does not conflict, or install the DJar in an alternative CorbaServer.
CEJL
com.ibm.cics.ejs.csi.MethodInfoStore
XMEOUT Parameters:
date,
time,
applid,
userid,
DJar,
bean_name,
CorbaServer
A CorbaServer scan failed because the djardir attribute on the CorbaServer definition is invalid. The djardir is invalid either because it is not an HFS directory or CICS does not have read access to it.
The scan fails. There is no change to the currently installed set of DJar resources.
Check the HFS directory exists and is accessible by CICS.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
djardir
A CorbaServer scan has been requested against the specified CorbaServer. This message also indicates the HFS directory that is scanned for new or updated deployed jars. When the scan has completed a summary message is produced indicating how many new DJar resources have been created and how many have been updated.
None.
None.
CEJL
DFHEJCG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
djardir
A CorbaServer scan has completed against the specified CorbaServer. The message indicates how many new DJar resources have been created based on the contents of the scanned djardir. It also indicates how many DJar resources have been upgraded due to new versions of jar files being discovered in the djardir.
None.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
newdjarcount,
upddjarcount
During a scan operation against the specified CorbaServer, CICS discovered a subdirectory in the djardir. The subdirectory is ignored. Scan does not recurse into subdirectories when looking for deployed jars to install.
The scan continues, simply ignoring the subdirectory.
The subdirectory does not harm the scan operation, but it may be advisable to remove it from the djardir as the scan operation always has to look at every object (directory or file) that exists in the djardir when performing a scan.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
subdir,
djardir
During a scan operation against the specified CorbaServer, CICS discovered a file that has an incorrect suffix. The scan code is looking for candidate deployed jar files and these files are expected to have .jar as their file suffix.
The scan continues, simply ignoring the incorrectly named file.
If the file was meant to be installed as a DJar resource in CICS, it should be renamed such that it ends .jar. If the file is not a deployed jar file, it should be deleted since CICS will examine it every time a scan is executed against this CorbaServer.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
file,
djardir
During a scan operation against the specified CorbaServer, CICS discovered a file whose name was too long for it to be installed into CICS as a DJar resource. The maximum length for deployed jar file names on HFS is 36 characters. That is a 32 character base name plus four characters for the .jar suffix. The DJar resource installed in CICS uses the basename for the deployed jar file as its resource name.
The scan continues, simply ignoring the file whose name is too long.
If the file was meant to be installed as a DJar resource in CICS, it should be renamed such that its basename is less than 33 characters. If it is not a deployed jar file, it should be deleted since CICS examines it every time a scan is executed against this CorbaServer.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
file,
djardir
During a scan operation against the specified CorbaServer, CICS discovered a file whose name contained characters that cannot be used when constructing a DJar resource. The name used for the DJar resource created in the CICS region is based on the 32 character basename of the deployed jar file discovered in the djardir.
The scan continues, simply ignoring the file whose name contains unacceptable characters.
If the file was meant to be installed as a DJar resource in CICS, it should be renamed such that its basename contains only valid characters. For the list of suitable characters to use in the name, see the character set restrictions for normal CEDA defined DJar resources. If it is not a deployed jar file, it should be deleted since CICS will examine it every time a scan is executed against this CorbaServer.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
file,
djardir
A new deployed jar file has been discovered on HFS during a scan. A corresponding CICS DJar resource is being automatically created to represent it. The DJar resource then goes through the normal stages of DJar resolution before it is ready for use.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
Djar,
CorbaServer
An update has been detected for a DJar resource. CICS compares the last modification time of the deployed jar file on HFS with the last modification time stored in the DJar resource definition. If the deployed jar file on HFS is newer than the currently installed resource, the DJar resource goes through the resolution process again, this causes the new version of the deployed jar file on HFS to be picked up.
None.
None.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
Djar,
CorbaServer
When a DJar completes resolution and becomes inservice, CICS checks the autopublish setting for the related CorbaServer. If autopublish is set to YES, the DJar is automatically published to the namespace.
None.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
Djar
A CorbaServer scan has completed against the specified CorbaServer. The message indicates how many new DJar resources have been created based on the contents of the scanned djardir. It also indicates how many DJar resources have been upgraded due to new versions of jar files being discovered in the djardir.
None.
None.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer
A CorbaServer scan has discovered that the pickup directory could not be read. This may be because the region does not have read access to the HFS directory.
The scan ends and no djar resources are installed.
Check that the directory exists and that the read access permissions are set.
CEJL
DFHEJDG
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer
During a scan operation against the specified CorbaServer, CICS discovered a file whose name had a .jar suffix but could not be installed in CICS because it had no file basename. Everything prior to the .jar suffix is the file basename and the basename is used as the name of the DJar resource that represents this jar file in the CICS system. CICS cannot install a DJar resource with an empty name.
The scan continues, simply ignoring the file with an invalid basename.
If the file was meant to be installed as a DJar resource in CICS, it should be renamed such that it has a suitable basename. A suitable basename is between 1 and 32 characters in length inclusive. If it is not a deployed jar file, it should be deleted since CICS examines it every time a scan is executed against this CorbaServer.
CEJL
com.ibm.cics.ejs.csi.commands.ScanCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
CorbaServer,
djardir
During an attempt to process the deployment descriptor for the specified jar file an exception was generated. The message indicates the source location of the exception in the deployment descriptor.
The djar fails to resolve and will have its state set to UNRESOLVED.
The jar file should be opened with appropriate tools and the deployment descriptor corrected.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
jarFileName,
line,
col
CICS has processed the supplied system properties and jndi properties, and it has determined the location upon the LDAP server where it attempts to place the InitialContext. The context described in the message is made up of several properties, containerdn and noderootrdn amongst them.
CICS continues processing. Any subsequent namespace processing against LDAP occurs relative to the named context.
No action is necessary unless the context is not as expected. If there is a problem with it, check the settings of the noderootrdn and containerdn LDAP properties, the CICS LDAP documentation and your LDAP administrator can help ensure they are set appropriately.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
ldap_context,
ldap_server
CICS has failed to publish the home for the bean in the JNDI namespace. This is because at the location CICS tried to publish the bean a JNDI context was found. CICS is unable to overwrite a context with a bean reference. The location where CICS attempted to publish the bean is included in the message.
The bean is not published. CICS continues to publish any further beans from the CorbaServer or DJar against which the publish operation was issued.
It is likely that another CorbaServer is sharing the same JNDI namespace and has a JNDI prefix that clashes with the JNDI prefix of the CorbaServer whose contents are currently being published. This may be a CorbaServer in a different CICS region. In order to avoid such clashes it is advisable to have an organized structure for JNDI prefixes used by CorbaServers sharing a namespace. This could include the machine name, region name and CorbaServer name in the JNDI prefix. Clashes usually occur because the name of a bean conflicts with a component of the JNDI prefix defined for the other CorbaServer. One of the CorbaServers must have its JNDI prefix altered to avoid this clash.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_server,
jndi_location
CICS has failed to retract the home for the bean from the JNDI namespace. This is because at the location CICS tried to retract the bean reference a JNDI context was found. CICS does not attempt to unbind the context because it is likely to be an area of the JNDI namespace in use by another CorbaServer. The location where CICS found the context is included in the message.
The bean is not retracted. CICS attempts to retract any further beans from the CorbaServer or DJar against which the retract operation was issued.
It is likely that another CorbaServer is sharing the same JNDI namespace and has a JNDI prefix that clashes with the JNDI prefix of the CorbaServer whose contents are currently being retracted. This may be a CorbaServer in another CICS region. In order to avoid such clashes, it is advisable to have an organized structure for JNDI prefixes used by CorbaServers sharing a namespace. This could include the machine name, region name and CorbaServer name in the JNDI prefix. Clashes usually occur because the name of a bean conflicts with a component of the JNDI prefix defined for the other CorbaServer. One of the CorbaServers must have its JNDI prefix altered to avoid this clash.
CEJL
com.ibm.cics.ejs.csi.commands.AdminCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
jndi_server,
jndi_location
The container was attempting to install a bean which has been deployed to use container managed transactions. The container was unable to find a suitable transaction attribute for a bean method whilst processing the DJar's deployment descriptor. According to the EJB Specification, the deployment descriptor must contain valid transaction attributes for all methods defined on the remote interface (excluding ejbCreate and ejbRemove methods which always run as NotSupported). This does not imply that each individual method must have an entry in the deployment descriptor as it is valid to use a wildcard to give all methods on the bean the same transactional characteristics. The message describes which jar file, bean and method it encountered problems with.
The bean and its containing DJar fail to install.
Modify the deployment descriptor in a suitable deployment tool to ensure that all the methods on the remote interface have a valid transaction attribute set.
CEJL
com.ibm.cics.ejs.csi.commands.InstallDJarCommand
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
bean_name,
method_name
CICS has failed to install a DJAR. This is probably due to a problem in the EJB-Jar file. This may be due to an invalid deployment descriptor, unresolved classpath requirement or the EJB-Jar file not having been 'deployed'. A Java exception was generated during the processing of the DJAR. The message string associated with the exception is included in this message.
The DJAR is put in the UNRESOLVED state.
Read the message from the Java exception and fix the problem. You will probably need to use the Application Assembly Tool (AAT) to verify or change the contents of the deployment descriptor for this DJAR. Ensure that any classes needed by the enterprise beans in this DJAR are available either in the DJAR or on the shared application class path. Ensure that you 'deployed' the EJB-Jar file using the "Generate code for deployment" option within AAT.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
file_name,
exception_message
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Further information is not available.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, an element of type element_type has been found which duplicates a similar element with the same name. The duplicated name is element_name.
According to the EJB 1.1 specification this element name cannot be duplicated within the same deployment descriptor.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type,
element_name
CICS has failed to install a DJAR. This is because a problem was discovered while trying to access or interpret the jar file.
The DJAR is put in the UNRESOLVED state.
Ensure that the HFS file specified on the DJAR resource definition exists. Also check that CICS has read permission for this file, that the file has been transferred in binary mode and that the file conforms to the jar file format.
The HFS file attribute of the DJAR resource definition is case sensitive. Please ensure that it has been entered correctly.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, a cross reference has been found which cannot be resolved. The reference was found in a element_type element of the deployment descriptor. The value in this element is element_value.
For example, a role-link element may have been found where the textual content of the role-link does not represent a valid security-role element from this same deployment descriptor.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type,
element_value
CICS has failed to install a DJAR. This is because a class specified in the deployment descriptor as a home, remote or bean implementation class for bean bean_name does not extend the appropriate ejb marker interface for that class. The interface that should be extended is interface_name.
According to the EJB 1.1 specification:
The home interface class must inherit from the javax.ejb.EJBHome interface.
The remote interface class must inherit from the javax.ejb.EJBObject interface.
The session bean implementation class must implement the javax.ejb.SessionBean interface.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor and/or classes in the jar file. To do this you may need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
class_name,
bean_name,
interface_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, bean bean_name implements the javax.ejb.SessionSynchronization interface but the deployment descriptor has conflicting values specified.
According to the EJB 1.1 specification, if a session bean implements session synchronization, it must be stateful, use container managed transactions and limit itself to TxRequired, TxRequiresNew or TxMandatory transactions.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
bean_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, an XML element has been found with an invalid value.
Many elements of the deployment descriptor are only permitted to have one of a small number of possible values. For example, the transaction-type element may only contain the values 'Bean' or 'Container'. These values are case sensitive.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type,
element_value,
bean_name
CICS has failed to install a DJAR. This is because the jar file has not been fully deployed. The process of 'deploying' an ejb-jar file causes some infrastructure code to be generated. This code is required by CICS but is absent from the jar file. The class that CICS was looking for but could not find is indicated in class_name.
The DJAR is put in the UNRESOLVED state.
Use the WebSphere Application Assembly Tool (AAT) or equivalent to produce the deployed jar file required by CICS.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
class_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, an XML element of type missing_element should have been found beneath any element of type parent_element. The missing element is required.
For example, the 'assembly-descriptor' subelement of the 'ejb-jar' element may be missing.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
parent_element,
missing_element
CICS has failed to install a DJAR. This is because a class or other resource required by the DJAR cannot be found. The missing resource may be the XML deployment descriptor, the XMI bindings file or a Java class. The name of the missing resource is given in resource_name.
If the missing resource is a Java class, this class is required by either the bean's home interface or the bean's remote interface and should be present in the jar file.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor and/or classes in the jar file. To do this you may need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
resource_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, an XML element has been found with an invalid value.
The bean-name and role-name elements of the deployment descriptor are defined in the EJB specification as having to conform to the lexical rules for an NMTOKEN. One of these elements was found which contained an illegal NMTOKEN character.
The full definition of an NMTOKEN can be found here: http://www.w3.org/TR/1998/REC-xml-19980210#NT-Nmtoken .
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type,
element_value
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. The deployment descriptor is valid but does not contain any Session beans.
A EJB-jar file must contain at least one Session bean before CICS is able to install it.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name
CICS has failed to install a DJAR. This is because an element in the EJB-Jar file's deployment descriptor has not been bound to a JNDI lookup string.
All 'resource-ref' elements and many 'ejb-ref' elements have to be associated with a JNDI string. This is done using the WebSphere Application Assembly Tool. The JNDI bindings are stored in a separate XMI bindings file in the EJB-Jar file.
The DJAR is put in the UNRESOLVED state.
Add the JNDI bindings. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the XMI bindings file for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type,
element_name
CICS has failed to install a DJAR. This is because an unexpected element has been found in the EJB-Jar file's deployment descriptor.
Some combinations of XML elements in the deployment descriptor are invalid. For example, if a session bean is defined to use bean managed transactions, it must not have any container-transaction elements associated with it.
The DJAR is put in the UNRESOLVED state.
Correct the deployment descriptor. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to verify or change the contents of the deployment descriptor for this DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
element_type
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. The XML parser was unable to validate the deployment descriptor or the XMI bindings file as the deployment descriptor is invalid.
The XML parser issued a message which is available in XML_message.
The DJAR is put in the UNRESOLVED state.
Use the XML_message to find and fix the problem in the deployment descriptor.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
line_number,
column_number,
XML_message
The deployment descriptor for DJAR djar_name contained references to enterprise beans which cannot be installed in CICS as they are not Session beans. CICS does not support non-Session enterprise beans such as Entity beans or Message-Driven beans.
The non-Session beans are ignored. Processing continues.
Either remove these beans from the deployment descriptor or ignore this warning.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's manifest file. The manifest file contains an invalid entry. The entry which contained the problem is called attribute.
The most common cause for this problem is a Class-Path entry in the manifest file that includes absolute file locations. For more information about manifest files visit this URL: http://java.sun.com/j2se/1.4.1/docs/guide/extensions /spec.html
The DJAR is put in the UNRESOLVED state.
Either fix the manifest file or remove the manifest file from the jar file.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
attribute
CICS has failed to install a DJAR. This is due to a problem in the name of one of the beans from the DJAR. CICS can only install enterprise beans with names whose characters fall in the following range: A-Z a-z 0-9 _ .
The DJAR is put in the UNRESOLVED state.
Either fix the bean name or remove the bean from the DJAR.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
bean_name
CICS has failed to install a DJAR. This is due to a problem in the EJB-Jar file's deployment descriptor. Specifically, bean bean_name has EJB 2.0 local interfaces defined.
CICS does not tolerate the presence of EJB 2.0 local interfaces.
The DJAR is put in the UNRESOLVED state.
Remove the local interfaces. To do this you need to use the WebSphere Application Assembly Tool (AAT) or equivalent to remove the interfaces and to regenerate the EJB Jar file's deployed code.
CEJL
com.ibm.cics.ejs.csi.ContainerUtil
XMEOUT Parameters:
date,
time,
applid,
userid,
djar_name,
bean_name
The EJB Container is unable to activate a bean. The bean being activated is named in the bean insert of the message. The class trying to activate the bean is named in class and the specific exception which caused the failure is given in exception.
Processing of the EJB Container continues but it is unlikely that any subsequent operations on the specified bean will be possible.
The exception insert is likely to be one of two values. If the exception contains the text 'ClassNotFoundexception', then check that the jar file containing the bean has been included in the classpath. Also, check that the bean does exist in the jar file. If the exception contains the text 'IOexception', then this may indicate a problem with reading the serialized bean from the bean store.
CEJL
com.ibm.ejs.container.passivator.StatefulPassivator
XMEOUT Parameters:
date,
time,
applid,
userid,
bean,
class,
exception
The EJB Container is unable to passivate a bean. The bean being passivated is named in the bean insert of the message. The class trying to passivate the bean is named in class and the specific exception which caused the failure is given in exception.
Processing of the EJB Container continues but it is unlikely that any subsequent operations on the specified bean will be possible.
If the exception contains the text 'IOexception', then this may indicate a problem with writing the serialized bean to the bean store.
CEJL
com.ibm.ejs.container.passivator.StatefulPassivator
XMEOUT Parameters:
date,
time,
applid,
userid,
bean,
class,
exception
The EJB Container is unable to passivate a bean. The bean being passivated is named in the bean insert of the message. The class trying to passivate the bean is named in class and the specific exception which caused the failure is given in exception.
Processing of the EJB Container continues but it is unlikely that any subsequent operations on the specified bean will be possible.
If the exception contains the text 'IOexception', then this may indicate a problem with writing the serialized bean to the bean store.
CEJL
com.ibm.ejs.container.activator.ActivationStrategy
XMEOUT Parameters:
date,
time,
applid,
userid,
bean,
class,
exception
The EJB Container is unable to evict an element from its cache. The element being evicted is named in the element insert of the message. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues. As the element was being removed from the cache, then no further operations on it would be expected.
None.
CEJL
com.ibm.ejs.util.cache.Cache
XMEOUT Parameters:
date,
time,
applid,
userid,
element,
exception
The EJB Container has encountered a problem while firing an alarm. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues.
None.
CEJL
com.ibm.ejs.util.am.AlarmManager
XMEOUT Parameters:
date,
time,
applid,
userid,
exception
The EJB Container is unable to locate the home wrapper for a bean object. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues.
None.
CEJL
com.ibm.ejs.container.BeanO
XMEOUT Parameters:
date,
time,
applid,
userid,
exception
The thread within the EJB Container, which monitors elements in the cache which are potential candidates for removal, has been interrupted. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues.
None.
CEJL
com.ibm.ejs.util.cache.BackgroundLruEvictionStrategy
XMEOUT Parameters:
date,
time,
applid,
userid,
exception
An unexpected exception occurred in the thread, within the EJB Container, which monitors elements in the cache which are potential candidates for removal. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues.
None.
CEJL
com.ibm.ejs.util.cache.BackgroundLruEvictionStrategy
XMEOUT Parameters:
date,
time,
applid,
userid,
class,
exception
An unexpected exception occurred when the Container tried to get the transaction coordinator. The specific exception which caused the failure is given in exception.
Processing of the EJB Container continues.
None.
CEJL
com.ibm.websphere.csi.TransactionControlImpl
XMEOUT Parameters:
date,
time,
applid,
userid,
exception
Whilst processing the deployment descriptor for a bean, the container found an EJB reference was not fully specified. An EJB reference must have either a valid ejb-link to another EJB within the same Jar file or it must have a valid binding specified.
The bean and its containing DJar fail to install.
Modify the EJB reference in a suitable deployment tool and add either a valid ejb-link or binding.
CEJL
com.ibm.ejs.container.BeanMetaData
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
reference
Whilst processing the deployment descriptor for a bean, the container found an EJB resource reference that did not have a binding specified. A valid resource reference must have a binding specified.
The bean and its containing DJar fail to install.
Modify the resource reference in a suitable deployment tool and enter a suitable binding value.
CEJL
com.ibm.ejs.container.BeanMetaData
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
reference
Whilst processing the deployment descriptor for a bean, the container found an EJB environment entry whose value was null. Environment entries must have a value specified in order to be valid.
The bean and its containing DJar fail to install.
Modify the environment entry in a suitable deployment tool and set a value appropriate to the type of the entry.
CEJL
com.ibm.ejs.container.BeanMetaData
XMEOUT Parameters:
date,
time,
applid,
userid,
bean_name,
env_entry
An unexpected message was produced by the CICS/WebSphere JNDI code. The full text of this message should explain the problem.
The behaviour of the system depends on the kind of naming problem. Naming problems could occur during bean publish, bean retract or bean lookup, any of these three operations may fail depending on the severity of the error.
If unable to determine an appropriate action from the full CICS message, lookup the WebSphere naming message code (NMSVnnnn) in your WebSphere documentation.
CEJL
com.ibm.ejs.ns.* com.ibm.ws.naming.*
XMEOUT Parameters:
date,
time,
applid,
userid,
message
The JNDI initial context factory which is specified as property java.naming.factory.initial has been set to com.ibm.ejs.nd.jndi.CNInitialContextFactory. This value specifies a deprecated class and has been replaced by com.ibm.websphere.naming.WsnInitialContextFactory.
Depending on the kind of naming operation attempted, it may succeed or fail.
Begin using the new initial context factory as soon as possible. This can be achieved by ensuring the java.naming.factory.initial property is set to the correct value, or by ensuring it is not set anywhere, so CICS can default appropriately. If unsure where it is being set, check the system properties file and any jndi.properties that exist on the classpath for the CICS system.
CEJL
com.ibm.ejs.ns.jndi.CNInitialContextFactory
XMEOUT Parameters:
date,
time,
applid,
userid
The CICS EJB container attempted to instantiate the requested plugin classplugin but the container could not find this class on the current classpath.
The plugin is not loaded.
Examine the value set for the classpath in the JVM profile being used from the XDFHENV dataset. The pathname for the requested plugin must be present in the classpath.
CEJL
com.ibm.cics.ejs.csi.CICSContainerConfig
XMEOUT Parameters:
date,
time,
applid,
userid,
plugin
The CICS EJB container caught an exception thrown from plugin plugin.
The EJB container attempts to continue processing the user application.
Either contact the plugin vendor for further assistance or catch the exception in the body of your plugin.
CEJL
com.ibm.cics.ejs.csi.CICSContainerConfig
XMEOUT Parameters:
date,
time,
applid,
userid,
plugin,
exception