This chapter describes the error (minor) codes.
The transaction timed out before it was fully initialized. Consequently, the transaction services cleaned up the infrastructure create for the transaction.
None.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series attempted to retry the error from the signal handler but the current thread did not allow retry.The thread was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series terminated the process due to catching a non-retryable signal. The process was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series terminated the thread due to catching a non-retryable signal. The thread was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series detected a bad assertion.A CORBA::INTERNAL exception is thrown.
Report the problem and accompanying information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series detected a bad parameter passed on open of a file.
Report the problem and accompanying information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fseek of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fseek of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fputs of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Too many specific trace points were specified. None of the trace points are set.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
Since a group of specific traces can lead to another group of specific traces, it is possible to create an infinite loop of definitions. To avoid this, there is a limit on the number of levels of nested definitions that are allowed The additional trace points are not set.
Check the trace group definitions for a circular reference or reduce the number of layers of definitions.
An open parenthesis was found in the definition of specific trace points indicating a list follows, but no closing parenthesis was found. None of the trace points are set.
Add a closing parenthesis.
Trace group names are delimited by single quotes and a quote was found starting the name of a group, but no closing single quote was found to end it. None of the trace points are set.
Add a closing quote to the end of the group name and try the command again.
Trace group names are delimited by single quotes and a quote was found starting the name of a group, but no closing single quote was found to end it. None of the trace points are set.
Add a closing quote to the end of the group name and try the command again.
Following the closing quote of a trace specific group there is additional text. The next character after the quote must be a comma, but something else was found. None of the trace points are set.
Correct the syntax and try the command again
An environment variable name was specified as containing a list of specific trace points to set, however the specified environment variable has no value set. No trace points are set.
Either remove the group from the command or use an environment variable that has a value.
An environment variable name was specified as containing a list of specific trace points to set, however the specified environment variable has no value set. No trace points are set.
Either remove the group from the command or use an environment variable that has a value.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that contained non hexadecimal values. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that contained non hexadecimal values. No trace points are set.
Specify a valid value and try the command again.
Too many exclude specific trace points were specified. The additional trace points are ignored.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
Too many specific trace points with special processing were specified. The additional trace points are ignored.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Caller invoked ArmRegister() with a bad cell name.
Ensure that the daemon_group_name configuration variable is set
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS could not load the specified DLL.
Ensure that the specified DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS could not obtain a message skeleton due to a previous failure.
Ensure that the message DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
MsgRetrieve function could not be obtained from the message DLL.
Ensure that the message DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code was invoked while in an invalid state.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected GIOP message type was received by the server. If a server is terminated, it is possible that other servers in session with the terminating server may get this minor code.
"None"
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This error results when you are trying to flow a locate request and are unable to establish a connection to the server (identified in the IOR for your particular situation) after iterating through the information for the communications protocols in the current IOR.
One of three things could be responsible: a network error (if the thing you were trying to reach was remote), a setup error (a local server that isn't up), or your IOR is not valid. A non-valid IOR (which is not as likely to be the case as the other two) could result if, for example, you got the IOR from naming and tucked it away somewhere (like a file), then tried to use it weeks later. It could also come from network changes or something that made specific IOR information obsolete.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A control region attempted to register with the daemon during the control region initialization process. However, the daemon is not available for new control regions to register, probably due to a STOP command having been issued for the Daemon or because the Daemon was terminating when the register request was issued. The control region ends.
Retry starting the control region after the Daemon has finished coming down and is back up again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client has remained up while the WebSphere Application Server for z/OS installation bootstraps were re-run (i.e. ORBCBI specified). A reference the client has to an object on the server contains information rendered obsolete by the re-bootstraping.
Restart the client.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client has remained up while the WebSphere Application Server for z/OS installation bootstraps were re-run (i.e. ORBCBI specified). A reference the client has to an object on the server contains information rendered obsolete by the re-bootstraping.
Check the host file for the system IP address that matches the DAEMON IP_NAME of the system that is trying to connect with the EUI.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to the next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS controller execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
If thrown by the application code, change your application code to catch and process it or add a user exception to the IDL and throw it instead so that the bindings will catch the user exception and return it to the client. If thrown by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::BOA::change_implementation was invoked but is not supported.
Do not invoke CORBA::BOA::change_implementation.
CORBA::BOA::obj_is_ready was invoked but is not supported.
Do not invoke CORBA::BOA::obj_is_ready.
CORBA::BOA::deactivate_obj was invoked but is not supported.
Do not invoke CORBA::BOA::deactivate_obj.
CORBA::BOA::_get_implementation was invoked but is not supported.
Do not invoke CORBA::BOA::_get_implementation.
CORBA::BOA::_get_interface was invoked but is not supported.
Do not invoke CORBA::BOA::_get_interface.
CORBA::BOA::_create_request was invoked but is not supported.
Do not invoke CORBA::BOA::_create_request.
CORBA::BOA::_request was invoked but is not supported.
Do not invoke CORBA::BOA::_request.
CORBA::BOA::_is_a was invoked but is not supported.
Do not invoke CORBA::BOA::_is_a.
CORBA::BOA::_non_existent was invoked but is not supported.
Do not invoke CORBA::BOA::_non_existent.
CORBA::BOA::_is_equivalent was invoked but is not supported.
Do not invoke CORBA::BOA::_is_equivalent.
CORBA::BOA::_hash was invoked but is not supported.
Do not invoke CORBA::BOA::_hash.
CORBA::BOA::_has_ancestor was invoked but is not supported.
Do not invoke CORBA::BOA::_has_ancestor.
Controller thread is terminating because a non-retryable signal was encountered.
Provide the controller dump and look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servant thread is terminating because a non-retryable signal was encountered.
Look at the Servant dump and log to determine whether this is an application or WebSphere Application Server for z/OS problem. If termination occurred due to an application error, correct the problem. If it is a WebSphere Application Server for z/OS error then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue work to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue work from the pending queue to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A locate request returned an unknown object.
There are several reasons why you might get this message: :ol.:li.What you are looking for may be corrupted. :li.Your configuration may have changed so that what you are trying to locate is no longer in the configuration.:li. Your request could get forwarded to another server that is more appropriate to handle your request.:li.If it gets forwarded too many times, it may give up.:li. The locate message send could have failed due to a TCP/IP timeout or other reason. If the locate message send failed, COMM should have logged the error.:eol.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This exception is accompanied by message BBOO0053E with the name of the DLL.
Locate message BBOO0053E in the error log to determine the name of the DLL which could not be loaded. Place missing DLL in the STEPLIB concatenation so that it can be found
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servant tried to register with the control region but the server is being stopped.
None, if the server was being stopped. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The dispatch method returned an indication that the operation was not executed.
Ensure that the server is running with a DLL for the class that has a version of the xxxxxxxs.cpp file that supports the requested operation.
Validation of the object key failed.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Unable to get a list of initial services.
Check the error log for other messages. Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a proxy object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Input object is not a CORBA::Object.
Verify that the object inherits from CORBA::Object.
Something is not correct with the object key. Possibly a UUID of the server or controller is not consistent with the type of communication indicated in the object key.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The build_IOR method failed to create an IOR.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
get_SCO() was called and initialization was not done.
Insure that the BOA_init method was called prior to invoking the get_SCO method.
The object_to_IOR method failed to make an IOR.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
When marshalling an object reference into an encapsulation, the object reference was NULL.
Report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
When marshalling an IOR into an encapsulation buffer, a little endian byte order was detected. S/390 should be big endian byte order.
Report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but never progressed. A ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the client.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but never progressed. A ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the client.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM and received by a Servant. This request did not complete within the time period specified by the ORB dispatch time out value. The ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the Client.
Check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Transaction Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Transaction Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::BOA::get_principal was invoked but is not supported.
Do not invoke CORBA::BOA::get_principal
A DII method was used on a CORBA::Request object that has not been created for use with DII.
Do not use this method or change the way the CORBA::Request object is created.
One of the DSI methods params(), ctx(), result() or exception of class ServerRequest has been called out of order.
Call the methods in the right order as specified in CORBA 2.0 and never call the same method twice.
Unable to dispatch method due to MO bindings generated as localonly objects.
Regenerate MO bindings as remotable objects.
CORBA::BOA::create was invoked but is not supported.
Do not invoke CORBA::BOA::create
CORBA::BOA::dispose was invoked but is not supported.
Do not invoke CORBA::BOA::dispose
CORBA::BOA::get_id was invoked but is not supported.
Do not invoke CORBA::BOA::get_id
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::Object_ORBProxy::_get_implementation was invoked from client which is not supported.
Do not invoke CORBA::Object_ORBProxy::_get_implementation from a client.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB::resolve_initial_references could not complete because it was unable to determine from where to get the initial references.
The RESOLVE_IPNAME environment variable must specify a TCP/IP name of a system where the initial references can be resolved (i.e. a S/390 system where a WebSphere Application Server for z/OS Systems Management server is running) or else a WebSphere Application Server for z/OS Daemon and Systems Management server must be running on the same system where the resolve_initial_references was issued
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::Object_ORBProxy::_decref() was invoked to decrement the reference count of the object but the reference count was 0.
Check application to make sure that CORBA::release is not being issued too many times. If it is an internal object then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
COMM failed when trying to drive a locate request to the daemon.
Check the error log for a COMM failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Naming IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
Since the Naming IOR is generated in Phase 1 of the Systems Management bootstrap , this situation indicates the Systems Management bootstrap needs to be run.
The IR IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
Since the IR IOR is generated in Phase 1 of the Systems Management bootstrap , this situation indicates the Systems Management bootstrap needs to be run.
The Systems Management SMO IOR has not been stored in the Systems Management server object, so it cannot be stored in the BGVT.
Since the SM SMO IOR is generated in Phase 1 of the Systems Management bootstrap, this situation indicates the Systems Management bootstrap needs to be run.
An attempt to start TCP/IP listening has failed.
Check the error log for messages relating to the error
BBOOSCO:readMasterRecord was called but the Master Record is not present. The Systems Management bootstrap is not being driven.
Restart the daemon with the -ORBCBI parameter so that the Systems Management bootstrap will be driven.
BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Possible causes are an update attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
BBOOSCO:initialize_SCOI_Server encountered an error while attempting to read server configuation information from DB2 tables.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered Possible causes are the address space is not authorized to use DB2, a read attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
BBOOSCO:initialize_SCOI_Server did not find the server defined in the Systems Management Tables.
Turn on exception tracing retry if it isn't already on. Additional information on which server record was not found will be traced. This error can only happen on the Systems Management server or the daemon. The probable cause is the Systems Management bootstrap failed or has not been run.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The index of the request sequence is equal or bigger than the length of the sequence.
Use only access to valid sequence elements.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:getSCO did not find the server defined in the Systems Management tables for this sysplex at the currently active level.
Turn on exception tracing retry and if it isn't already on. Additional information on which server was not found will be traced. Possible causes are the server wasn't defined using the Systems Management End User Interface (EUI) or if the server was defined using the Systems Management EUI, the conversation containing that server has not yet been activated using the Systems Management EUI.
BBOOSCO:getSCO could not obtain this server's configuration data from the Systems Management Control Region.
Turn on exception tracing and retry if it isn't already on. Additional information on which server is in error will be traced. Additional trace information may also be found in the Systems Management controller exception trace output. Possible causes are the server wasn't defined using the Systems Management End User Interface (EUI) or if the server was defined using the Systems Management EUI, the conversation containing that server has not yet been activated using the Systems Management EUI. Another possible cause is the server could not call back to the Systems Management controller. If the EUI indicates the server is defined and the conversation that contains it is the activated conversation, report the problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Class Manager failed to find the specified class in the list of classes supported by the server. The application that contains this class may not be properly defined or installed on the server.
Look in the error log to determine which class is in error. Additional information can be found in the trace when exception tracing is turned on. Possible causes are the class wasn't installed using the Systems Management End User Interface (EUI) or if the class was installed using the Systems Management EUI, the conversation containing that class has not yet been activated using the Systems Management EUI. If the EUI indicates the class is supported, report the problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::ImplRepository::find_impldef_by_alias was invoked by client.
Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef_by_alias
CORBA::ImplRepository::find_impldef was invoked by client.
Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying to narrow to a CORBA::ImplementationDef object.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying create an object.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trynig to build a IOR.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef was invoked but an error ocurred trynig find the implementationDef for the input implid.
Ensure that the server for the input implid is started. When exception tracing is on, the input implid is traced.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
While a WebSphere Application Server for z/OS Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS Series servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An attempt was made to start a WebSphere Application Server for z/OS Series Control Region while another Controller with the same specific server name was active. Only one WebSphere Application Server for z/OS Series Control Region with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Controllers with the same specific server name.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Before a Servant can start, the control region which it is associated with must be initialized. This Servant was unable to find its owning controller and thus terminates.
Ensure this Servant's owning control region is active before starting the Servant.
An attempt was made to start a WebSphere Application Server for z/OS Series Control Region while another Controller with the same specific server name was active. Only one WebSphere Application Server for z/OS Series Control Region with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Controllers with the same specific server name.
Timeout occurred waiting for the naming server to start. We are unable to continue without it, so an exception is thrown.
Determine why the naming server failed to start before the timeout occurred, correct the problem, and try again.
Timeout occurred waiting for the IR server to start. We are unable to continue without it, so an exception is thrown.
Determine why the IR server failed to start before the timeout occurred, correct the problem, and try again.
Timeout occurred waiting for the Systems Management Server to start. We are unable to continue without it, so an exception is thrown.
Determine why the SM server failed to start before the timeout occurred, correct the problem, and try again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB_Request::setSystemException was invoked with an unrecognized System Exception. The unrecognized System Exception was traced and a CORBA::UNKNOWN System Exception with this minor code was placed into the ORB_Request to be returned to the client.
Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
ORB_Request::getSystemExceptionId encountered an unrecognized System Exception. The unrecognized System Exception was traced and a CORBA::UNKNOWN System Exception with this minor code was placed into the ORB_Request to be returned to the client.
Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
The WebSphere Application Server for z/OS Servant execution thread caught a ... This is an incorrect throw. A system exception with this error code is created and returned.
If application code is throwing something other than a system or user exception, change the application code to throw a system exception or a user exception that the method indicates it raises. If it is not application code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The DAEMON_IPNAME environment variable is set to an IP address. It must be set to an IP name, host n name.
Correct the DAEMON_IPNAME environment variable and run the Systems Management Bootstrap again.
Cannot open converter
Code set may not be compatible
Cannot open converter
Code set may not be compatible
Conversion Error
Code set may not be compatible
Conversion Error
Code set may not be compatible
Incorrect data length
Make sure the input data length is correct
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
COMM failed when trying to drive a locate request to the daemon.
Check the error log for a COMM failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Cannot open converter
Code set may not be compatible
Cannot open converter
Code set may not be compatible
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a proxy object in rebuild_proxy.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Possible causes are an update attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
CORBA::Context::delete_values was invoked but the input property name was not found in the context object.
If encountered by application code, check for application error. If encountered by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Processing in a Controller was halted because it was detected that the WebSphere Application Server for z/OS Daemon was not active.
The WebSphere Application Server for z/OS Daemon is required for WebSphere Application Server for z/OS servers to be active. All WebSphere Application Server for z/OS servers should terminate if the Daemon ends. This abend may occur if the servers are processing work when the Daemon terminates. Restart the Daemon when ready.
Processing in a Controller was halted because it was detected that the WebSphere Application Server for z/OS Daemon was not active.
The WebSphere Application Server for z/OS Daemon is required for WebSphere Application Server for z/OS servers to be active. All WebSphere Application Server for z/OS servers should terminate if the Daemon ends. This abend may occur if the servers are processing work when the Daemon terminates. Restart the Daemon when ready.
resolve_initial_references was called before doing ORB_init and BOA_init.
Make sure both the ORB and the BOA are initialized, either by a call to CBSeriesGlobal::Initialize() or by some other method, before resolve_initial_references is called.
resolve_initial_references_remote was called before doing ORB_init and BOA_init.
Make sure both the ORB and the BOA are initialized, either by a call to CBSeriesGlobal::Initialize() or by some other method, before resolve_initial_references_remote is called.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In encode_objref, pfactory is NULL after lookup of pfactory in ptable.
pfactory looks up the table entry for a certain classname in ptable. Look at the system error message to determine what classname was "looked up" in ptable.
In encode_objref, attempted to marshal a local_only object during a request. Here local_only means a local object residing in a pure client-only process.
Don't marshal a local_only object while a request is in progress.
BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Probable cause is the address space is not authorized to use DB2.
BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS information that will indicate what errors were encountered. Series error log for Probable cause is the address space is not authorized to use DB2.
ORBid keyword to ORB_init must specify a value of BOSS
Provide a value of BOSS as the value of the ORBid keyword.
ORBid keyword must be specified on ORB_init with a value
Specify ORBid BOSS.
ORBsrvname keyword to ORB_init must have a value
Specify ORBsrvname with a valid server name
The ORBType keyword to ORB_init must have a valid value
Specify ORBType with a valid value.
Initialization of a WebSphere Application Server for z/OS Server failed loading a required product load module. Look for the accompanying message for the name of the module which could not be found.
Determine which module could not be found and why and correct the problem and restart the server.
RRS is required for WebSphere Application Server for z/OS Series to function. During initialization of a WebSphere Application Server for z/OS Server, RRS could not be found. The server terminates.
Make sure RRS is up and initialized.
The value specified for the ORBCBI keyword to ORB_init was not one of COLD, WARM, or HOT.
Specify a valid value.
The ORBCBI keyword to ORB_init requires a valid value
Specify COLD, WARM, or HOT as a value. Example: START BBODMN,BOOT='-ORBCBI COLD' (where BBODMN is the Daemon proc name).
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This exception is accompanied by message BBOO0053E with the name of the DLL.
Locate message BBOO0053E in the error log to determine the name of the DLL which could not be loaded. Place missing DLL in the STEPLIB concatenation so that it can be found
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CBSeriesGlobal::hostName was called from a WebSphere Application Server for z/OS server space. In this environment the hostName returned would be the DAEMON_IPNAME environment variable specified for the Daemon on this system. However, it appears the daemon is not active (perhaps it is terminating) on this system.
If the Daemon was terminating or down at the time this error occurred, then no action is necessary as it is expected.
Systems management server created requested data space for SMF data gathering but the ALESERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Systems management server tried to create requested dataspace but the DSPSERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the DSPSERV return and reason codes. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Systems management server created the requested data space for SMF data gathering but when this server tried the ALESERV the ALESERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The MVS STOP console command or the System Managment EUI STOP command has already been issued for this server. Subsequent commands are ignored.
Wait for the current stop processing to complete or escalate to an EUI Cancel or MVS console Modify Cancel command.
The MVS Modify Cancel console command or the System Managment EUI CANCEL command has already been issued for this server. Subsequent commands are ignored.
Wait for the current cancel processing to complete
No server name was specified for the Controller
Examine the Controller procedure or the parameters which were used to start the Controller and correct to specify the appropriate server name.
A user exception was caught by the main Controller routine
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
No server name was specified for the Servant
Examine the Servant procedure or the parameters which were used to start the Servant and correct to specify the appropriate server name.
A user exception was caught by the main Servant routine
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
The Servant is terminating due to an internal error.
Check the WebSphere Application Server for z/OS error log for information about errors preceeding this one which could have caused the Servant to terminate.
WebSphere Application Server for z/OS Daemon and Controllers must run authorized. However, the space has detected that it is not. The space ends in error.
The most probable cause of this is a dataset in the Steplib for the proc that is not in the APF list or the PPT settings for the load module(bboctl) should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:readSysplex was called but the Sysplex does not exist in the Systems Management database. The Systems Management bootstrap has not been run.
Restart the daemon with the -ORBCBI parameter to run the Systems Management bootstrap.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The server instance is terminating due to a MODIFY server-instance,CANCEL
Restart the server instance when the reason that required you to cancel it has been resolved.
The server instance is terminating due to a MODIFY server-instance,CANCEL,ARMRESTART
None.
An outbound request could not be sent because length of message exceeded maximum.
Try sending a smaller message.
A send oneway or send deferred request could not be sent because length of message exceeded maximum.
Try sending a smaller message.
An outbound request (callback) could not be sent because length of message exceeded maximum.
Try sending a smaller message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series terminated the thread due to error when attempting to pause for more work.
See previous messages for why the thread was unable to pause for more work.
WebSphere Application Server for z/OS Series terminated the SSL Handshake thread due to error when attempting to pause for more work.
See previous messages for why the thread was unable to pause for more work.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An outbound request could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
A send oneway or send deferred request could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
An outbound request (callback) could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
An outbound response could not be sent by the SR because its size exceeded the maximum allowed for local IIOP messages.
Try sending a smaller response.
The server could not send the response to client because its size exceeded the maximum allowed for local IIOP messages.
Try sending a smaller message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue HTTP request to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to the next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS Controller execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
If thrown by the application code, change your application code to catch and process it or add a user exception to the IDL and throw it instead so that the bindings will catch the user exception and return it to the client. If thrown by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The destroyJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The detachThreadFromJVM external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ACRW request not queued because the server is being stopped. Control is returned to the requestor with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Controller's attempt to dynamically define application environment failed. Most likely the application environment definition already exists and is running under the same subsystem name and node name.
Verify the application environment definition does not already exist, and if it does, verify the existing application environment and the new application environment are not being defined with the same subsystem name and node name.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In order for the WebSphere Application Server for z/OS Servant to start, the DAEMON GROUP NAME environment variable must be set. If it is not set, this exception results and the server region will not initialize.
Set the DAEMON GROUP NAME environment variable.
In order for the WebSphere Application Server for z/OS server to start, the daemon needs to be active.
Ensure daemon is active before starting the server.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Initialization of a WebSphere Application Server for z/OS Server loaded the wrong version of a required product load module. Look for the accompanying message for the name of the module.
Determine which module had the problem. Fix STEPLIB, LPA or Linklist so that the correct version of the module will be loaded and restart the server.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The attempt to create a dataspace via DSPSERV failed. No SMF data gathering will be done.
Locate message BBOO0038E in the error log to get the DSPSERV return and reason codes. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unknown user exception was thrown while processing a synchronous ACRW in the Controller.
Examine the Controller logs for the cause of the initial user exception.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to create a WLM enclave for an inbound MDB Request failed.
Examine the job log from the controller region for a related BBOO0037E message. This message will contain the return and reason code from the WLM create enclave service (IWMECREA).
Attempt to queue an MDB Request to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB_Request::mergeMessageReplyBody detected that the servant was not able to obtain a cell in the comm dataspace to hold the large HTTP response.
Retry the request.
The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL
Restart the Daemon instance when the reason that required you to cancel it has been resolved.
The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL,ARMRESTART
none
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive an outbound request.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive an outbound request.
Check the error log for a communication failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The redrive count for invoking an outbound request was exceeded.
Check the error log for a communication failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No class implementation exists for the method
Verify coding to the intended method is correct and supported. Do not invoke unsupported methods. For supported methods, instance manager detailed tracing may be enabled to capture method flow.
WebSphere read an interest back from the RRS recovery logs that was an unknown or invalid type. WebSphere cannot process this interest.
If you recently upgraded your service level, confirm that a cold start of WebSphere or RRS was not required. Ensure that your RRS logstreams are not corrupted.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failed to get terminator pointer from control.
Rewrite application logic.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tried to decrement thread association count below zero in decrement_association.
Transaction rolled back. Follow these procedures before calling IBM: <;ol>;<;li>;.Run initial diagnostics to determine if the rollback was due to a timeout. Ensure that the transaction timeout value did not expire.<;/li>; <;li>;If the timeout value did not expire, check the application to ensure the transaction's logic didn't cause the rollback.<;/li>; <;li>;Ensure you did not timeout DB2 or the Resource Manager.<;/li>; <;li>;If your application, DB2, or the Resource Manager did not cause the rollback then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ <;/li>;<;/ol>;
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
register_resource detected transaction is marked rollback.
See C9C21809.
register_synchronization detected transaction is marked rollback.
See C9C21809.
register_synchronization with superior coordinator raised unknown exception.
No action possible. Raise CORBA::UNKNOWN exception.
Resource registration with superior failed in genericCreate.
See C9C2181F
Null PropagationContext in extract_gitd.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during root prepare.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Detected that transaction is pending rollback.
See C9C21809.
Detected that transaction is pending rollback.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempted to access transactional objects that no longer exist. The method that threw the exception detected that the transactional object no longer existed and had either been committed or rolled back by some other asynchronous operation.
If the exception was thrown by your application, there may be a problem synchronizing the application execution and the attempt to query, modify, rollback, or commit the transaction.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
There was not enough storage preallocated to accomodate OTS structures.
Set TRACEDETAIL=(3,4,6) in your environment dataset (BBOENV).
Transaction Service does not support inbound transactional one-way requests.
Do not issue transactional one-way request.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Control Region is shutting down. Transaction creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Transaction creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resource commit came in on restart resource but resolver owns syncpoint.
This exception is normal processing for restart but indicates that attempts to contact the recovery coordinator have been unsuccessful. If this condition persists, ensure the recovery coordinator is up and functioning. It is possible that the application (or application environment) acting as recovery coordinator is down.
Resource rollback came in on restart resource but resolver owns syncpoint.
This exception is normal processing for restart but indicates that attempts to contact the recovery coordinator have been unsuccessful. If this condition persists, ensure the recovery coordinator is up and functioning. It is possible that the application (or application environment) acting as recovery coordinator is down.
Detected that transaction is pending rollback.
See C9C21809.
Rollback request was rejected because requested was not the initiator of the transaction. Obsolete.
Check for a possible application coding error.
Commit request was rejected because requested was not the initiator of the transaction. Obsolete.
Check for a possible application coding error.
Unable to register resource due to underlying recovery service logging limit.
Rewrite application to include fewer resources.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Unable to register local resource object due to implementation restriction.
Check for an application error. Refer to application documentation for restrictions on local resource.
Unable to register local synchronization object due to implementation restriction.
Check for an application error. Refer to application documentation for restrictions on synchronization onjects.
Encountered a user exception while trying to mark transaction on thread as rollback_only.
Check for an application error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRAPRP service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRAPRP service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRACMT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRACMT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRABAK service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRABAK service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRAFGT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRAFGT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRPDUE service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRPDUE service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code indicating that RRS is not currently active was returned from an invocation of an RRS Callable Service.
Make sure RRS is currently active. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRWID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRDINT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSPID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSWID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRURD service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRRI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSUSI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRUSI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSSPC service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIERS service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRLN service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRISLN service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code indicating that RRS is not currently active was returned from an invocation of an RRS Callable Service.
Make sure RRS is currently active. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Registration Services CRGSEIF service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery.For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIBRS service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRNI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATREINT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during delegate prepare.
See C9C21809.
Inbound transaction is a nested transaction. WebSphere Application Server for z/OS does not support nested transactions.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resource one_phase_commit came in on a resource but a syncpoint was already in progress.
If the transaction was rolled back, see C9C21809.
Transaction rolled back with a heuristic mixed condition during delegate prepare.
RRS will write a record to LOGREC to indicate which resource manager(s) had a heuristic condition during the commit process. Follow the identified resource manager's procedures to resolve the heuristic condition. Also see C9C21809.
Invalid or NULL CosTransactions::Coordinator object extracted from an inbound. CosTransactions::PropagationContext structure.
Verify that sending ORB interoperates with WebSphere Application Server for z/OS.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Server region sending reply checks detected a mismatch between the original transaction associated with the method and the one currently associated with the thread.
Check the application for a logic error.
Transaction service is unable to locate transaction factory.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction service is unable to locate transaction factory.
Check systems management configuration for a definition of transaction factories.
Transactional request rejected because transaction is no longer active.
Check the application for a logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction server in server region detected a thread termination while the transaction was active on thread. This resulted in termination of the server region address space.
Check the application for a logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction server detected invalid state for rollback_only request.
WebSphere Application Server for z/OS internal processing. No error has occurred.
Transaction server detected transaction service containing deferred begin request.
WebSphere Application Server for z/OS internal processing. No error has occurred.
Non-existent transaction detected for rollback_only request.
Check the application for a logic error.
Invalid CosTransaction::PropagationContext returned from a 'deferred begin' outbound request.
Check the documentation on interoperability between ORBs.
An attempt was made to mark a transaction 'rollback_only' which was previously marked 'rolledback_only' or is in the process of being rolled back.
The transaction has or will be rolled back asynchronously from this processing. The initial rollback may have been initiated by the application itself, asynchronous from this call, or initiated by one of the resource managers participating in the transaction. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atrdint issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atrspid issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atreint issued but UR log data limit exceeded.
A system limit has been exceeded and is no longer capable of storing transactional information. The application must reduce the number of different resource managers participating, possibly by narrowing the scope of the transactions or by redefining the composite objects so they are comprised of fewer components.
atreint issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere Application Server for z/OS syncpoint coordinator.)
Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere Application Server for z/OS syncpoint coordinator.) The detection of failure was prior to a system exception being raised for this transaction.
Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
An inbound request to a control region was detected to be contained within a transaction that had previously timed out.
Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
Commit request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
Check for a possible application coding error.
Rollback request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
Check for a possible application coding error.
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
OTS has determined that the method inbound to this server has timed out, because one of its transactional objects does not exist. Most probable cause is the transaction timedout.
Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
Transaction rolled back due to an unexpected return code from agent prepare.
Scan the traces subsequent to this one. TBD
Transaction rolled back because a protected resource is not in the proper state for a commit.
TBD
The control region was brought down after a CANCEL reply to MSGINDEX_BBOUENUS_OTS_HARDENED_DATA_LOSS.
None
Unknown transaction policy specified for continer.
Check the transaction policy specified for this container in the SM EUI.
Transaction that was started during a method dispatch was not completed before returning. The transaction was marked for rollback.
Check the application logic for a possible coding error.
A different transaction was present at container exit than at container entry. The transaction at exit was marked for rollback and the transaction at entry was resumed.
Check the application logic for a possible coding error.
Container initiated transaction caught unknown exception from commit.
None.
Container caught exception while attempting to resume the transaction that was present on entry.
None.
An error occurred while attempting to retrieve data about the current unit of recovery. RRS detected that the server had an invalid environment. The server will terminate itself and take a dump.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred while attempting to retrieve data about the current unit of recovery. RRS has become unavailable and/or the server cannot communicate with RRS.
Restart RRS and/or the application server that failed.
An error occurred while trying to commit the procedural global transaction on behalf of the container. The procedural global transaction was rolledback. Containers can start procedural global transactions in server regions, on behalf of business logic for certain transaction policies.
The resource that was being modified by the object was rolledback for some reason that is not known to the server. Consult rollback debug documentation for the resource manager which initiated the rollback. See RRS problem determination documentation for assistence in determining the rollback initiating resource manager.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Hybrid Global transaction could not be committed by the server because the resource managers involved in transaction were in the wrong state. The server region is terminated.
Check for an application logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resume not allowed because the application has uncommitted local resources.
Local resources must be committed or rolled back before resuming another transaction. Check for an application coding error.
An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
A Heuristic Mixed exception was raised while attempting to commit container initiated transaction.
Check the traces and messages prior to this to determine what protected resource caused the heuristic outcome.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRBEG service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRBEG service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSENV service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRADCT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRADCT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during root commit.
See C9C2181F.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An inbound transaction context did not contain a reference to the coordinator object for the global transaction.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRS is unavailable on this system.
Ensure RRS has been started on this system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRS is unavailable on this system.
Ensure RRS has been started on this system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The client attempted to invoke an component, e.g. EJB, in a global transaction, however the the the component was deployed with a transaction policy that indicates it must not be invoked within a global transaction.
Correct the client application or redploy the component in error.
The client attempted to invoke an component, e.g. EJB, in a global transaction, however the the the component was deployed with a transaction policy that indicates it must not be invoked within a global transaction.
Correct the client application or redploy the component in error.
Transaction rolled back during root commit.
See C9C2181F.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During the RRS log name exchange process, RRS indicated that no previous log name was set. This condition occurred while the server was running in restart and recovery mode. This implies that the recovery system is not in the same RRS log group or that the server was never started on its configured system.
If you are attempting to start the server in restart and recovery mode on an alternate system, verify that RRS is in the same log group as the server's configured system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction manager attempted to contact an XA resource with an attempt to resume a previously suspended transaction. The resource responded with a return code indicating an error and processing cannot continue.
Check the message log for a message displaying the XAException thrown by the resource and the error code. Contact your resource vendor to determine why this error occurred.
The transaction manager attempted to contact an XA resource with an attempt to suspend a transaction. The resource responded with a return code indicating an error and processing cannot continue.
Check the message log for a message displaying the XAException thrown by the resource and the error code. Contact your resource vendor to determine why this error occurred.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An exception was raised while driving preInvoke on the transaction strategy for this method. A subsequent attempt to resume the local transaction that was on the thread before the transaction strategy was driven failed.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during prepare.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during prepare.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
Transaction rolled back during prepare.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An inbound request contained a transaction service context for a transaction that has already been added to the path sensitive branch registry but can't be found in the GTID map.
None. This condition can occur during or after an asynchronous transaction rollback. Common causes of asynchronous rollbacks include timeouts and abends.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere transaction service cannot support more than 254 inbound branches of a transaction in one server.
Check for a probable application coding error. A possible cause of this error is a recursive call between components in different servers that are participating in the same transaction.
RRS was cancelled or failed while WebSphere Application Server for z/OS was active. WebSphere is unable to process work when RRS is unavailable.
Restart RRS and WebSphere.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A resolver which was about to enter a blocking call to RRS could not re-register himself as a transaction alarm.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A subordinate OTS resource recieved a commit outcome from his superior node. The resource attempted to drive commit on any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
A subordinate OTS resource recieved a commit outcome from his superior node. The resource attempted to drive commit on any XAResources taking part in this transaction branch, but an unexpected exception was thrown.
The operation will retry periodically. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A subordinate OTS resource is attempting to drive the XAResources associated with his branch of the transaction. The resources cannot be driven yet because there is no server region capable of taking such a request at this time.
The operation will retry periodically. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21899.
See C9C21899
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21908.
See C9C21908.
See C9C21909.
See C9C21909.
See C9C21907.
See C9C21907.
See C9C21907.
See C9C21907.
See C9C218FF.
See C9C218FF.
See C9C21905.
See C9C21905.
See C9C2190A.
See C9C2190A.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for commit request.
See C9C21884.
Non-existent transaction detected for get_control request.
See C9C21884.
Non-existent transaction detected for suspend request.
See C9C21884.
Non-existent transaction detected for rollback request.
See C9C21884.
Non-existent transaction detected for Prepare request.
See C9C21884.
Non-existent transaction detected for Commit request.
See C9C21884.
See C9C21076.
See C9C21076.
See C9C2107B.
See C9C2107B.
See C9C2107C.
See C9C2107C.
The XaRecoveryTableManager class could not be loaded by the JNI.
The XaRecoveryTableManager class may not be on the classpath. Ensure that the CR classpath specified is correct. If it is correct then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The "instance" method on the XaRecoveryTableManager class could not be found by the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The one or more methods on the XaRecoveryTableManager class could not be found by the JNI.
Ensure that your classpath is set correctly. Failing that, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21928.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An array could not be allocated in the JVM through the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2192D.
See C9C2192D.
WebSphere is performing a warm start with RRS. A counter is maintained in the RRS logstream that must match a counter in the XA partner log in order for recovery to complete successfully. The counters do not match.
If the RRS logstream was restored from a backup copy, the XA partner log must also be restored from the same backup. Also, it is possible that the XA partner log was deleted. It will need to be restored from a backed up copy. If neither of these actions are possible, a cold start with RRS will be necessary to restore the logs to a usable state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction sequence number wrapped and needs to be logged in the XA partner log, but the log write failed.
Ensure that the XA partner log file exists and is not full. Ensure that there is free space on the device that the partner log resides on. Look for message WTRN0076 for a detailed stack trace which may provide more information.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
A server region thread associated with a transaction received a piece of work for a different tranaction.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JTA transaction manager raised an unexpected exception while processing an inbound request.
Examine the error log for information about the original java exception that was raised.
The JTA transaction manager raised an unexpected exception while processing an outbound reply.
Examine the error log for information about the original java exception that was raised.
An unexpected java exception was encountered while obtaining a reference to the JTA transaction manager.
Examine the error log for information about the original java exception that was raised.
An unexpected OTS UserException was encountered while processing transaction manager request.
Examine the error log for information about the original CORBA exception that was raised.
The JVM raised an exeption while attempting to enter the monitor associated with the JTA transaction object from native code.
Examine the error log for information about the original java exception that was raised.
The JVM raised an exeption while attempting to exit the monitor associated with the JTA transaction object from native code.
Examine the error log for information about the original java exception that was raised.
The transaction manager could not find a reference to a recently created transaction in the active GTID map. This can happen when a server region initiated transaction completes during asynchronous processing.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
The transaction identifer generated in the server region did not match the identifier generated in the control region from the primary key.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A request to enlist XA resources in a transaction could not be completed as the control region does not yet have an interest in the RRS unit of recovery.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
A request to enlist XA resources in a transaction could not be completed as the control region no longer has an interest in the RRS unit of recovery.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
The JTA transaction manager raised an unexpected exception while attempting to determine the transaction attribute of the target object and operation.
Examine the error log for information about the original java exception that was raised.
The RRS service ATREINT1 returned the value ATR_CONTEXT_TOKEN_INV. The Transaction will be marked rollback-only.
None.
A request was received for a transaction that has already gone through a syncpoint.
None.
Non-existent transaction detected in the received_request method.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2192D.
See C9C2192D.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The "instance" method on the ControllerRequestProcessor class could not be found by the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A call to RegisterNatives failed. The method could not be registered with the JNI.
Ensure the classpath has not been modified and that your service level is not corrupted. For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21928.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A method on the TranAttributeMap class could not be found by the JNI. There is likely a mismatch between the native and Java WebSphere libraries.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction manager could not find a reference to a recently created transaction in the active GTID map. This can happen when a server region initiated transaction completes during asynchronous processing.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
See C9C21076.
See C9C21076.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for Forget request.
See C9C21884.
No outcome received while heuristically rolling back a restarted transaction.
Examine the error log for information about the cause of the failure. The transaction may have completed already. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected while heuristically rolling back a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No outcome received while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. The transaction may have completed already. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction in wrong state for commit while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21908.
See C9C21908.
See C9C21909.
See C9C21909.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An XA resource recieved an outcome. The resource attempted to resolve any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
An XA resource recieved an outcome. The resource attempted to resolve any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
An XA resource recieved an outcome. However the XARecoveryAgent was not found to resolve any XAResources taking part in this transaction branch.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
RRS macro ATRQUERY was issued to query the RRS logs. This service returned a bad return code indicating that the issued action failed to complete.
Check the message and error logs for the return and reason codes. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. If the problem persists, please contact the IBM support center.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for Register request.
See C9C21884.
The JVM could not be found by the native method.
Look for error messages in the server output which may explain why the JVM did not start. If the problem persists, contact the IBM Support Center.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Invalid object reference detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Shasta marshaling error detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Shasta internal error detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
_narrow method caught non-CORBA exception
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CORBA::UNKNOWN error has been unmarshalled in the bindings from javaspace.
Look prior to this message to see if any java error messages have been recorded
A CORBA::UNKNOWN error has occured in the SOMRef process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function _CallMethod in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _CallMethod in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _StrongRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _StrongRef in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _WeakRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/SOMBase.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
Function _WeakRef in bbolrt.cpp could not find the "_weakref" method in Java class /com/ibm/som/corba/rt/SOMBase.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
Function _WeakRef in bbolrt.cpp did not get a weak object reference for a Java object.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function _isInstanceOf in bbolss.cpp is not implemented.
Do not use this function.
Function SOMCPP_SOMObjectDecoder in bbolsreq.cpp detected that the length in the encapsulation does not match the length of a pointer on the OS/390 platform.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function take_buffer in bbolsreq.cpp detected that the length of the CDR buffer is zero.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function decode_SOMRef in bbolsreq.cpp detected that the length in the encapsulation does not match the length of a pointer on the OS/390 platform.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In bbolpoi.cpp, some CORBA DII object is nil after creation.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In bbolpoi.cpp, some Context methods not supported
Change application program accordingly
Tried to find a proxy factory for a class and it was not available to the server. The proxy factory was going to be used to cast a void pointer to a CORBA::Object_ptr so that an object reference could be marshaled back into the Java environment.
Insure that the class name that is indicated in the associated message is installed on the server.
Function checkJavaException was called An Exception was thrown in a JNI thread.
Look prior to this message to find what JNI Exceptions were thrown.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RuntimeUtil failed to initialise because it failed to complete a FindClass
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RuntimeUtil failed to complete initilization
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS and OS/390 ORB is not initialized. An IOR can not be created from an object if an ORB is not available.
Check error logs for failure of the ORB to initialize. If there are not any ORB initialization failures then the initialization will need to be added to the client code.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JVM System.exit or Runtime.exit routine was called and the JVM has terminaated. As part of this processing, WebSphere has terminated the current process.
If the exit request was issued by an application, please examine the application to determine why exit was called. If Java 2 Security is enabled, the application was explcitly given permission to call this API. If this behavior is not desired, do not grant the application the RuntimePermission "exitVM". If the exit was not initiated by the application then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JVM has unexpectedly aborted. As part of this processing, WebSphere has terminated the current process.
Check the error logs for a possible cause. If the problem cannot be resolved then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Environment variables value field is empty or not set (which is a mandatory one)
Assign a valid (non-null) value for the environment variable indicated by message (this minor code is for mandatory environment variables not mentioned in current.env files)
This server was started after a Stop command was was issued for the WebSphere Application Server for z/OS Daemon. Daemon stop processing stops all active servers and no new servers are allowed to start. Any servers starting after the stop command is issued will receive this failure.
None
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In order for the WebSphere Application Server for z/OS Daemon to start properly, the protocol_iiop_daemon_listenIPAddress environment variable must be set. If it is not set, this exception results and the Daemon will not initialize.
Set the protocol_iiop_daemon_listenIPAddress environment variable appropriately (probably to the TCP/IP host name of the system where you are trying to start the Daemon).
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application Servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In PPT::PPT(char*), BBO3PPT1 Macro is unable to call IEFPPSCN because APF Not Authorized to perform such action.
Make Sure Load Module is APF Authorized.
PPT Entry Specification Error
Correct PPT Entry - BBOSCHED
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was active. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was active. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A bad return code received from service CRGRRMD.
See message BBOO0056E in the error log for additional information.
A bad return code received from service CTXSDTA.
See message BBOO0056E in the error log for additional information.
A bad return code received from service CTXBEGC.
See message BBOO0056E in the error log for additional information.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A Servant was started and was unable to find the Controller it goes with.
If the Servant started as the Controller was ending then this is normal. If a Servant was manually started (instead of allowing WLM to start it) then possibly the parameters were incorrect or it was started on the wrong system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 IDENTIFY processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 SIGNON processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service.For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 CREATE THREAD processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 Terminate Thread processing failed for the DB2 active server respository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 Terminate Identity processing failed for the DB2 active server respository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unsupported daue work queue element type was detected. Processing of the daue work queue will be terminated.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Initialization of a WebSphere Application Server for z/OS Server failed loading a required product load module. Look for the accompanying message for the name of the module which could not be found.
Determine which module could not be found and why and correct the problem and restart the server.
No server name was specified for the Daemon.
Examine the Daemon procedure or the parameters which were used to start the Daemon and correct to specify the appropriate server name.
A user exception was caught by the main Daemon routine.
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates. This should never happen :-)
WebSphere Application Server for z/OS Daemon and Controller must run authorized. However, the space has detected that it is not. The space ends in error.
The most probable cause of this is a dataset in the Steplib for the proc that is not in the APF list or the PPT settings for the load module(bbodaemn)should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
The DSNLOAD which is done to setup DB2 from the DAUT thread initialization failed. An exception trace is cut with the return code.
The Daemon's call to DSNLOAD setting up DB2 failed. An exception trace is cut with the return code from DSNLOAD.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SQL error besides 'not found' occurred while trying to delete all entries from the DB2 ASR table. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error besides 'not found' occurred while trying to delete all entries from the DB2 ASR for a given system name. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to add an entry to the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to delete an entry from the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to update an entry in the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to read all entries in the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to read all entries in the DB2 ASR for one system. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to open a cursor to read all the DB2 ASR entries. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to open a cursor to read DB2 ASR entries for 1 system. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to delete a DB2 ASR entry at the current cursor location. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A Daemon is configured to run on a particular system. This Daemon was started on a system in the sysplex other than where it was configured to start. In the event of a system failure, automation or ARM may restart the Daemon, Systems Management, and Controllers on another system in order to allow transactions to rollback and locks to be released. As the Daemon has no cleanup work to do, it fails with this minor code. A Daemon/SM configured to run on the restart system is required to be active before SM and Control regions will be allowed to start on a system where they are not configured to run.
If started as part of a cross system recovery no action is required. If the Daemon was started as part of an attempt to bring up the WebSphere Application Server servers, either start these servers on the system where they are configured to run, or configure new servers to run on this system.
In order for the WebSphere Application Server for z/OS Daemon to start properly, the DAEMON GROUP NAME environment variable must be set. If it is not set, this exception results and the Daemon will not initialize.
Set the DAEMON GROUP NAME environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Externalization StreamIO method in which this exception occurred was issued out of order. This exception will occur if a get_buffer_ref() method was previuosly issued to obtain the current StreamIO buffer and then a StreamIO method is invoked before a set_buffer_ref() is issued to re-establish a StreamIO buffer.
Correct your code to ensure that when a get_buffer_ref() is issued to get the StreamIO buffer, a set_buffer_ref() is done to re-establish a StreamIO buffer before any other StreamIO methods can be issued.
An attempt was made to invoke the Externalization StreamIO method, write_object(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the write_object method from your code.
An attempt was made to invoke the Externalization StreamIO method, write_graph(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the write_graph method from your code.
An attempt was made to invoke the Externalization StreamIO method, read_object(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the read_object method from your code.
An attempt was made to invoke the Externalization StreamIO method, read_graph(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the read_graph method from your code.
An attempt was made to invoke the 390 StreamIO destructor. This destructor should never be called. IExtended390 streamIO objects are returned to a stack and never destructed.
Locate the code that called the invalid operation and correct its usage.
An attempt was made to invoke the Externalization StreamIO method, read_wchar() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the read_wchar method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, read_wstring() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the read_wstring method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, write_wchar() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the write_wchar method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, write_wstring() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the write_wstring method from your code or switch to an IBM format 2 externalization.
An attempt was made to allocate an encapsulation buffer for an EncapIIOP object that is being used by the Externalization StreamIO support.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This method is not implemented.
Call another method to perform the intended operation.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Wide character data was detected within an encapsulation but a wide character transmission code set was not negotiated when the associated session was established (this prevents CB/390 from transmitting wide character data within this session)
Verify that wide character support is configured correctly.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An invalid multi-byte character value was detected within an encapsulation or in data to be encapsulated. (This is most likely caused by the presence of an invalid multi-byte character within the request or reply parameters associated with a method invocation on a CORBA object.)
Inspect the values of wide character parameters associated with the method invocation that caused the error.
The native code page used for wide characters is non-byte-oriented with a character length other than 2.
Switch to a native code page for wide characters that is either byte-oriented or is non-byte-oriented with a character length of 2.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The length of a character or character array changed as a result of doing a codepage conversion on the character data while marshaling or unmarshaling the data.
If a multi-byte code page is being used, change the IDL type used to represent the multi-byte data to either a string or wchar.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Default identities are allowed but a default identity has not been defined for this server. Authorization is denied.
Configure system management to define a default identity for this server.
A userid with an invalid length was provided in the security context. Authorization was denied.
The ORB Request for the client must supply an eight character string, padded with blanks for userids less than eight characters.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Client ID does not have RACF authorization to BIND to this server.
Obtain the needed RACF authorization and resubmit the request (CB.BIND.servername).
This is a single client session and the client ID in the request does not match the ID from a previous request. Only one client is authorized for a single client session.
Either change the RACF authorization to make this a multi client session or submit all requests from the same client for a single client session.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AccountingId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType NonRepudiationId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType GroupId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Role is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AttributeSet is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Clearance is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Capability is NOT IMPLEMENTED as a SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Session owner does not have RACF authorization to pass multiple clients to this server.
Obtain the needed RACF authorization (CONTROL) and resubmit the request (CB.BIND.servername).
Client id does not have RACF authorization to execute this <serverName.homeName>.
Obtain the needed RACF authorization and resubmit the request.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Client ID does not have RACF authorization to execute on this server.
Obtain the needed RACF authorization and resubmit the request.Note: For DCE, authentication map the DCE principal to a valid. MVS userid Clients from a foreign DCE cell can never be permitted
There was no password provided in a security context thought to contain a userid and password.
If running with the default userid, see if a default password was set.
SecurityAttributeType Public is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
The copy method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the set_security_features method in SecurityLevel2::Credentials is not implemented.
Do not ask for this method in this class.
the get_security_features method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the is_valid method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the refresh method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
The SCO information indicated that this server was to use DCE security but DCE security services were not available when the server was started.
Look in the server logs for messages to see why this server was unable to access DCE security services. Based on these messages, perform the appropriate corrective actions and try the operation again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
DCE PRINCIPAL is not mapped to MVS userid.
"Set up principal UUID to MVS ID map in RACF"
Version of Native security does not match expected version #.
Check security version of client and server
Raw Client executing protected code
Fix client code
Server attempting to execute non server code
Fix server code
A native security context was sent remotely
Possible external hack attempted
A native security context was sent remotely
Possible external hack attempted
Get Transportable Identity returned a null
IBM internal problem
Get Transportable Identity returned a null
IBM internal problem
The non-repudiation credentials type is not implemented.
Do not ask for this credentials type.
ALthough the request orignated in the Server region, no Native Security Context exists. Originated in get_userid() method.
ORB should have copied the Native Security CTX from the ORBR in the Server back to the ORBR in the CTL on the outbound flow from the server. See if the Servant abended before doing the copy.
ALthough the request originated in the Server region, no Native Security Context exists. Originated in get_userid_build_ctx() method.
ORB should have copied the Native Security CTX from the ORBR in the server back to the ORBR in the CTL on the outbound flow from the server. See if the Servant abended before doing the copy.
Client id does not have RACF authorization to USE this server.
Obtain the needed RACF authorization and resubmit the request (CB.servername).
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Mutual authentication failed when client tried to verify the server.
investigate the server.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
There is no authentication for this client
Failure trying to authenticate client
A client is attempting to initiate a DCE protected conversation with a server with a DCE quality of protection level that is less than that which has been set for this server by the system administrator. The server returns a no permission exception to the client.
The client can increase the quality of protection that it uses to initiate the DCE protected conversation, or the server can have its setting lowered to match the client's requested protection level. Servers will respect a client's requested DCE quality of protection level if it is equal to or greater than its quality of protection setting. The servers quality of protection level is controled through the System Management User Interface. The client's quality of protection level is set through the System Management User Interface, or on OS/390 the environment variable CLIENT_DCE_QOP.
A client process failed in the attempt to initiate a a request to a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in a request to a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security over SSL.
The request probably failed because the specified DCE principal and/or DCE password are invalid. Please respecify REM_DCEPRINCIPAL and/or REM_DCEPASSWORD and try again.
An SSL Client Certificate was received by a server during SSL handshake processing. This certificated cannot be resolved to an identity.
The SSL client certificate is probably not in the servers keyring, and cannot be transformed into an S/390 identity. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in a request to a server using an unknown security method.
This is an internal error! Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RACF - Parameter list error occurred
RACF - An internal error occurred during RACF processing
RACF - Recovery environment could not be established
RACF - User ID is not defined to RACF
RACF - Password or PassTicket is not valid
RACF - Password is expired
RACF - User ID is revoked
RACF - User is not authorized
RACF - Certificate is not valid
RACF - Either no user ID is defined for this certificate or the certificate status is NOTRUST
Null sessionid in NatSecCtx_Auth
MethAuthCheck was issued in an address space without a BACB
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The client has a DCE quality of protection setting of confidential and the target server does not support DCE security. In the work station version of WebSphere Application Server for z/OS, servers advertise that they support DCE security whether they do or not. If it is determined that the target server advertised DCE security, but really does not support it, the OS/390 client checks to see what DCE quality of protection the client has asked for. If it is confidentiality the request is terminated with this exception. If the client has any other DCE quality of protection setting the request proceeds with no security.
If the client requires DCE security with the quality of protection setting of confidentiality, the administrator of the targeted server must enable DCE security for the server. If the client does not require DCE security with a quality of protection setting of confidentiality the environment variable CLIENT_DCE_QOP can be set to any value other than CONFIDENTIALITY. If the quality of protection is lowered in this manner the request will continue but no security is enabled for it.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servers reply to the Client's initial message does not contain a session ID. This indicates that the server did not agree to a session with this client. Check for a server exception returned to the client.
Check that the needed RACF authorization has been established on the server. If not, obtain the necessary RACF authorization and resubmit the request (CB.servername).
Servers reply to the Client's initial message has already been processed by this client.
The handshake between the client and the server is out of sequence. Resubmit the request
As part of the DCE mutual authentication process the server was unable to verify the identity of the client. This exception is initially raised by a server as a response to a failed gss_accept_sec_context() GSS_API call. A message should appear in the server's message log with the GSS_API major and minor status codes returned from this call.
Refer to the OS/390 DCE Messages and Codes book for a description of the status codes returned. Based on the status codes found take the appropriate actions and have the client retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ Ref: OS/390 V2R7.0 DCE Messages and Codes Document Number: SC28-1591-06
The return value for the current RACO pointer in the OPI for the original inbound client is NULL when getTransportableIdentity() is called while building a security context an outbound request.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error in the DEC mutual authentication process occurred during the creation of an Authentication object or there is a problem in the DCE first time message handshake
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The authentication class was not found during the DCE mutual authentication process after the DCE first time message was handled.
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Mutual authentication failed when client tried to verify the server.
investigate the server.
Mutual authentication failed when client tried to verify the server.
investigate the server.
Mutual authentication failed when client tried to verify the server.
investigate the server.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
An error occurred during the new of the saved RACO pointer in security method convertToSessionID. Possibly memory could not be allocated for the pointer.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No client security context (and therefore no identity) has been supplied in the ORB Request and default identities are not allowed for this server. Authorization is denied.
Either the client ORB Request must contain a security identity in the security context, or the system administrator should configure system management to allow undefined users.
Only a client userid has been supplied in the ORB Request sent to this server. The client must supply more than just a user id (i.e., password, etc) to gain access to a server. Authorization is denied.
The client ORB Request must contain a complete security context.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SSL Type 1 Association Complete service context encountered by the server but there was no corresponding authentication segment.
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SSL Type 1 service context was received by a server with a msgtype of something other than ASSOC_COMPLETE or MUTUAL AUTH.
You may be using an incompatible client and server configuration. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The SSL Session identity was not given update authority and is not authorized to propagate asserted identities.
Check to ensure that the session identity should be authorized to propagate asserted identities, and if so give the identity update authority. If the SSL session identity already has update authority, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
SSL session received asserted identity service and this was not accepted. Either the identity was unknown on the target host, or this server is not authorized by the target server to assert identities.
Verify the CB.BIND on the target server and consider disabling asserted identity for this client or server.
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a SupportedSecurities structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A process failed to find the SSL kerberos security context associated with the request.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the allocation of a sting for a Kerberos session identifier in the security method KRBAuth. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server using Kerberos GSS_API security over SSL.
Review the message logs from the contacted server for the reason that the request failed. Based on the information found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a sting for a Kerberos name in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Kerberos GSS_API service context in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a sting for a Kerberos name in the security method initKRB. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the allocation of a sting for a Kerberos security context in the security method KRBAuth. Memory could not be allocated on the server.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error in the DCE api gss_init_sec_context.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error when processing a SSL Kerberos GSS_API context. The session identifier contained in the context is in use by the server and the context contains a GSS_API token.
Review the context sent by the client process. Based on the context take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The requester does not have the authorization to make this request.
Contact your security administrator and request authorization for this service and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The requester failed the Kerberos authentication test the server ran out of memory.
Check the server logs for the reason that the Kerberos authentication failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to accept the client context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to extract the principal name from the security context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name extracted from the security context is too long.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name does not contain an "at" sign (@). The principal name should be in the form principal@realm.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During Kerberos authentication, CB was unable to obtain the SAF user associated with the Kerberos principal because there is no mapping between the Kerberos principal and a RACF userid.
Contact your security administrator and have the principal mapped to a RACF userid. The SAF and RACF codes are documented in the OS/390 Security Server Callable services book. Once the principal is mapped, retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure trying to authenticate role name
Correct any problems with the definitions of users or EJBROLE profiles. Ensure the EJBROLE class is active.
push Identity failed, because on OS thread function disabled
Cannot synch OS thread to Userid, enableSyncOSThread = false. Check settings in SM GUI
Caller ID does not have permission to execute method
Make sure that the caller ID has permission to access that particular method.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included authorization token. This level of z/OS WebSphere does not support authorization tokens.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send authorization tokens to servers that do not support them.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context contained an asserted identity of the Principal Name type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of principal names.
The CSIv2 security attribute service context contained an asserted identity of the Certificate Chain type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of Certificate Chains.
The CSIv2 security attribute service context contained an asserted identity of the Distinguished Name type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of Distinguished Names.
The CSIv2 security attribute service context contained an asserted identity of the Identity Extension type and, the target server is not configured to support this type of asserted identity.
Have the client process change its request to use a different asserted identity type that is supported by the target server.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the length of the authentication token.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the mechanism object identifier (OID) of the security mechanism.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the mechanism object identifier (OID) of the security mechanism.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP target name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request contained a invalid userid.
This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid userid.
The CSIv2 security attribute service context included in a GIOP request contained a invalid password.
This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include a valid userid.
The CSIv2 security attribute service context included in a GIOP request indicates that the anonymous user is to be used for authorization checks, and the target server does not support this.
This is most likely a problem caused by the process that formed the request and context. The most likely solution is to have the client. include authentication information when contacting this server.
Get Transportable Identity returned a null
IBM internal problem
The CSIv2 security attribute service context included in a GIOP request is not valid.
We have not done Kerberos yet.
The CSIv2 security attribute service message context contains a context identifier that in not valid at the target server.
The most likely cause of this problem is that the target server has invalidated the client's context identifier. A server may do this so that a client is forced to re-authenticate itself. No action is required, this exception should be handled by a CSIv2 client.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The creation of a CSIV2 GSSUP context failed.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The creation of a CSIV2 Idenity Assertion context failed.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The user identitfier that is to be used for the asserted identity is not a valid z/OS user.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The principal name mechanism is not supported on z/OS.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the SSL/TLS session identity does not have SAF 'control' access to the profile CB.BIND.servername. This identity is found by mapping the client X509 certificate that was passed during SSL/TLS initialization, to a RACF id. This is the identity that requires control access to the profile CB.BIND.servername.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the z/OS user that was authenticated in the CSIv2 supplemental client authentication layer does not have 'control' access to the profile CB.BIND.servername. Contact your security administrator and request that this user be granted access to the asserted identity service.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the server default identity does not have 'control' access to the profile CB.BIND.servername and there was no SSL session owner (no client certificate) on the session. Contact your security administrator and request that this user be granted access to the asserted identity service.
The CSIv2 server was not able to use an establish context because it indicated that it contained a asserted principal but no principal was found.
The most likely reason for this is that the context generator is sending a bad context.
The CSIv2 server was not able to use an establish context because it indicated that it contained a asserted principal but no principal was found.
The most likely reason for this is that the context generator is sending a bad context.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The server was not able to produce a token value based on the authorization token sent in a CSIv2 context.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included a Kerberos authentication token that could not be processes because the server could not load the Kerberos DLL.
An error occurred when the server attempted to accept the client Kerberos gssapi context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to extract the principal name from the security context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name extracted from the security context is too long.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name does not contain an "at" sign ( The principal name should be in the form principallm.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During Kerberos authentication, CB was unable to obtain the SAF user associated with the Kerberos principal.
The most likely reasom is that there is no mapping between the Kerberos principal and a RACF userid. Contact your security administrator and have the principal mapped to a RACF userid. The SAF and RACF codes are documented in the z/OS Server Callable services book. Once the principal is mapped, retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included a X509 certificate identity token that could not be processed because the token was malformed. The token contained a certificate length that was too large or not valid.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included an X501 Distinguished Name token. There was an internal error processing the token. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context was received that the same key as an exisiting context. However, the credentials were not the same. All credentials with the same key must have the same credentials.
The CSIv2 security attribute service context included in a GIOP request that is not valid .
The CSIv2 security attribute service context included a realmname that zOS attempted to convert to the UTF1047 code page. The convert failed. This is an internal error. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CSIv2 service context contained an LTPA token that could not be mapped to a zOS userid.
A CSIv2 security attribute service context was received that contained an LTPA token. The token could not be validated and was not mapped to a zOS userid. Either the token has expired or is not known to the system. Make sure that the LTPA configuration between the sender system and receiver system is correct.
During a CBIND access check a CSIv2 service context contained an LTPA token that could not be mapped to a z/OS userid. No client bind authorization could be done.
A CSIv2 security attribute service context was received that contained an LTPA token. The token could not be validated and was not mapped to a z/OS userid. Either the token has expired or the user it represents is not known to the system. Make sure that the LTPA configuration between the sender system and receiver system is correct.
During a CBIND access check a CSIv2 service context contained an z/OS user id that could not be found on the system. No client bind authorization could be done.
A CSIv2 security attribute service context was received that contained a z/OS userid that could not be found on the target system. The most likely reason for this is that the requested user is not in the z/OS registry. Insure that the user that is being requested is a member of the z/OS registry.
During a CBIND access check the initACEE callable security service failed to convert an SSL Certificate into a z/OS native security context. No client bind authorization could be done. The SAF return and reason codes can be found in the server log file.
See return codes for initACEE (IRRSIA00) in the Security Server (RACF) Callable Services or equivalent reference for other security products. Security Server reference documentation for initACEE include: Security Server (RACF) Security Administrator's Guide and Security Server (RACF) Callable Services for initACEE service call return and reason codes.
During a CBIND access check a CSIv2 asserted distinguished name failed to be mapped to a z/OS userid. No client bind authorization could be done. The SAF return and reason codes can be found in the server log log file.
See return codes for initACEE (IRRSIA00) in the Security Server (RACF) Callable Services or equivalent reference for other security products. Security Server reference documentation for initACEE include: Security Server (RACF) Security Administrator's Guide and Security Server (RACF) Callable Services for initACEE service call return and reason codes.
During a CBIND access check a CSIv2 asserted distinguished name failed to be mapped to a z/OS userid. No client bind authorization could be done.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During a CBIND access check an ACEE could not be obtained so client bind authentication cannot be done.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CSIv2 service context contained an ltpa token that was not valid.
The token has most likely expired. The client initiating the connection should resend the request with new credentials. No user action is required.
A CSIv2 service context contained a userid and password. The server attempted to login using the userid and password but the login failed.
The userid and password was not valid for the current registry. Check the registry to make sure they are still valid. If the configured registry is not SAF, there may be a problem connecting to the registry. Check the server output log for problems communicating with the registry.
The server received a CSIv2 establish security attribute service context that contained two IBM Security Attribute Propagation authorization tokens. This is not supported. A context may only have one such token.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send duplicate authorization tokens.
The server received a CSIv2 establish security attribute service context that contained a type of authorization token that is not supported.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send authorization tokens that are not supported.
The server received a CSIv2 establish security attribute service context that contained an IBM Security Attribute Propagation authorization token. This server was not configured to support this tokens.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send this tokens when a server does not support them.
An attempt was made to clone a security object but the pointer to the object no longer points to the correct storage. The storage was probably freed.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
The authentication information provided for the request could not be validated during login.
Ensure that the appropriate credentials have been presented to the server and retry the request.
There was a problem validating the LTPA token during login processing. It is likely that the token has expired. This exception may also be raised if the token could not be decrypted with the configured keys.
Ensure that the token has not expired and that the appropriate keys were used to encrypt and decrypt the token at the client and server. In most cases this error is transient as the client side service will generate a new token and retry the request. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
A problem was encountered while attempting to login with an asserted ID. The most likely cause of this error is that the presented identity is not found in the active user registry or that the server does not trust the client side service to assert identities.
Ensure that the server is configured to trust the client service to assert identities and that the user ID that is being asserted can be found in the active user registry. For further information, please consult the product documentation.
Adapter code encountered an unexpected system failure.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The adapter is unable to narrow to the adapter resource manager.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an unknown unexpected interrupt.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code using APPC failed to allocate the conversation
Check APPC configuration to make sure APPC is up and running and that APPC connectivity exists between the two LUs. If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC Allocate failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC send service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC send failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC receive service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC receive failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC confirmed service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC confirm failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC deallocate service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC deallocate failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code failed while using one of the CICSEXCI services.
Check the CB error log for the string "CICSEXCI" for further diagnostic information.
Specified TPName (also known as transaction program name in IMS or as Function Program name in the J2EE Connector Architecture) exceeds maximum length.
Specify a shorter name. Consult IMS and APPC documentation for specific parameter requirements.
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
Servant Object could not be created for the invoke request. This is likely due to a class type conflict or a protection domain conflict.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
An object request was received with a method name that the target object does not support. The client's RMI/IIOP Stub is out of synch with the server's RMI/IIOP Tie.
Correct the application.
The CORBA Container container returned a null remote implementation when trying to execute a J2EE request.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
getServiceContextList is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
getRequestId is not implemented in this implementation of ClientResponse
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
getForwardedIOR is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
peekUserExceptionId is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The object given to the ORB had an incorrect delegate while trying to load a IDLJ stub.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An invalid ClientDelegate was used to drive a request.
IBM Internal Only.
The com.ibm.ws390.orb.WS390ServerDelegate class could not be found by Java.
Ensure that the WebSphere/390 EE runtime jar files are on the failing process's CLASSPATH.
The com.ibm.ws390.orb.WS390ExtendedServerDelegate class could not be found by Java.
Ensure that the WebSphere/390 EE runtime jar files are on the failing process's CLASSPATH.
Attempted to register an object as an INS NamingService that is not an org.omg.CosNaming.NamingContext or an org.omg.CosNaming.NamingContextExt .
Verify the object specified.
The URL supplied to ORBDefaultInitRef should be a corbaname or corbaloc URL.
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
The URL supplied to ORBDefaultInitRef should not contain a '/'.
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
Badly formed ORBInitRef parameter. ObjectURL was missing. Parameter should be of the form:
<ObjectID>
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
Badly formed ORBInitRef parameter. ObjectURL was missing. Parameter should be of the form:
<ObjectID>
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
A java.rmi.RemoteException is being returned as the result of a J2EE request. The actual RemoteException is imbedded within the Unknown Exception service context in the GIOP response. It is the embedded exception that will be received by the client.
This is not an error.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
A request to an object that was colocated within the server could not be completed because the object no longer exists.
Look for a Java stack trace in the server's SYSOUT to determine the object that was requested. Check whether the application that owns the object was stopped or uninstalled.
Unexpected IO Exception when creating ClientResponse.
IBM Internal Only
Unexpected IO Exception when creating ClientResponse.
IBM Internal Only
The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request.
IBM Internal Only
The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request.
IBM Internal Only
An error occured while trying to create an IOR for an RMI/IIOP Stub. The remote mode Stub does not already hold a reference to the IOR that created it.
IBM Internal Only
A user exception was received by the client side non_existent() method, but there are no exceptions defined on that method.
IBM Internal Only
A user exception was received by the client side is_a() method, but there are no exceptions defined on that method.
IBM Internal Only
A user exception was received by the client side get_interface_def() method, but there are no exceptions defined on that method.
IBM Internal Only
An erroneous IIOP response type was received in the client.
IBM Internal Only
An HTTP request was received but the target Tie could not be found.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
A request to dispatch a callback object failed because the target callback object is not registered with the client ORB.
For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A request to dispatch a callback object was received with a method name that the target object does not support.
For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occured while trying to load an RMI/IIOP Tie.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occured while trying to load an RMI/IIOP Stub.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A J2EE request was received with a method name that the target object does not support. The client's RMI/IIOP Stub is out of synch with the server's RMI/IIOP Tie.
Correct the application.
The get_interface() method has been deprecated and is not supported for J2EE components.
Correct the application.
The J2EE container returned a null remote implementation when trying to execute a J2EE request.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
The getTransportManager() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The process() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The locate() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The ORB received an exception from the J2EE container while trying to load an IDLJ stub.
Correct the application.
The string_to_object method was passed a zero length string.
Correct the application.
The string_to_object method was passed a string that is not a stringified IOR.
Correct the application.
The string_to_object method was passed a NULL string.
Correct the application.
The resolve_initial_references() method was driven on a singleton Java ORB, which singleton ORBs do not implement.
None.
The ORB received an exception from the J2EE container while trying to load a local mode RMI/IIOP stub.
None.
The ORB received a NULL remote implementationn from the J2EE container while trying to load a local mode RMI/IIOP stub.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An error occured while trying to load an RMI/IIOP Stub.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2107B.
See C9C2107B.
See C9C2107C.
See C9C2107C.
See C9C21076.
See C9C21076.
See C9C21076.
See C9C21076.
An array could not be allocated in the JVM through the JNI.
An out of memory condition could exist. Try the operation again.
The JVM could not be found by the native method.
Look for error messages in the server output which may explain why the JVM did not start. For further assistance, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB service such as string_to_IOR received null or bad parameters.
report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Null synchronizer pointer in register_sync.
No action possible , raise CORBA::BAD_PARAM exception.
Null TransactionService Context in extract_gitd.
No action possible, raise CORBA::BAD_PARAM exception.
Null synchronizer pointer in register_sync.
No action possible, raise CORBA::BAD_PARAM exception.
Unable to register resource due to invalid resource parameter.
Check for an application error.
Unable to register synchronization object due to invalid resource parameter.
Check for an application error.
Invalid coordinator reference passed on is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
Check for an application error.
Invalid propagation context accessed in is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
Check for an application error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
Check to make sure you are running with enough memory for the address space issuing the failing code. Verify that for the controller/Servant the REGION=0M. Refer to the "WebSphere Application Server for z/OS and OS/390:Installation and Customization Guide" for additional WebSphere storage requirements. If that is not the problem, collect the following information and look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ : Run with exception tracing, i.e. TRACEALL=1 in the current.env file associated with the server. If TRACEBUFFLOC=SYSPRINT, send all the job output for that region to IBM as well as the contents of the error log. If TRACEBUFFLOC=BUFFER and you have the CTRACE writer operating, send the CTRACE data set, as well as the job output and error log to IBM.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series attempted to retry the error from the signal handler but the current thread did not allow retry.The thread was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series terminated the process due to catching a non-retryable signal. The process was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series terminated the thread due to catching a non-retryable signal. The thread was terminated.
See previous messages for why the thread entered the signal handler.
WebSphere Application Server for z/OS Series detected a bad assertion.A CORBA::INTERNAL exception is thrown.
Report the problem and accompanying information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series detected a bad parameter passed on open of a file.
Report the problem and accompanying information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fseek of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fseek of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure during fputs of the header record (first record) of a log file. The header record is bad.
Run the error log utility program to initialize the error log data set and correct the problem. If the problem persists, report the problem and related information to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Too many specific trace points were specified. None of the trace points are set.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
Since a group of specific traces can lead to another group of specific traces, it is possible to create an infinite loop of definitions. To avoid this, there is a limit on the number of levels of nested definitions that are allowed The additional trace points are not set.
Check the trace group definitions for a circular reference or reduce the number of layers of definitions.
An open parenthesis was found in the definition of specific trace points indicating a list follows, but no closing parenthesis was found. None of the trace points are set.
Add a closing parenthesis.
Trace group names are delimited by single quotes and a quote was found starting the name of a group, but no closing single quote was found to end it. None of the trace points are set.
Add a closing quote to the end of the group name and try the command again.
Trace group names are delimited by single quotes and a quote was found starting the name of a group, but no closing single quote was found to end it. None of the trace points are set.
Add a closing quote to the end of the group name and try the command again.
Following the closing quote of a trace specific group there is additional text. The next character after the quote must be a comma, but something else was found. None of the trace points are set.
Correct the syntax and try the command again
An environment variable name was specified as containing a list of specific trace points to set, however the specified environment variable has no value set. No trace points are set.
Either remove the group from the command or use an environment variable that has a value.
An environment variable name was specified as containing a list of specific trace points to set, however the specified environment variable has no value set. No trace points are set.
Either remove the group from the command or use an environment variable that has a value.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that contained non hexadecimal values. No trace points are set.
Specify a valid value and try the command again.
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that contained non hexadecimal values. No trace points are set.
Specify a valid value and try the command again.
Too many exclude specific trace points were specified. The additional trace points are ignored.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
Too many specific trace points with special processing were specified. The additional trace points are ignored.
Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Caller invoked ArmRegister() with a bad cell name.
Ensure that the daemon_group_name configuration variable is set
Trace points specified for TRACESPECIFIC must be eight hex digits long. A value was found that was not the correct length. No trace points are set.
Specify a valid value and try the command again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS could not load the specified DLL.
Ensure that the specified DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS could not obtain a message skeleton due to a previous failure.
Ensure that the message DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
MsgRetrieve function could not be obtained from the message DLL.
Ensure that the message DLL is part of the execution path (or STEPLIB) for this process. If it is not, add it to the execution path or specify a different language in the BBOLANG environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code was invoked while in an invalid state.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected GIOP message type was received by the server. If a server is terminated, it is possible that other servers in session with the terminating server may get this minor code.
"None"
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This error results when you are trying to flow a locate request and are unable to establish a connection to the server (identified in the IOR for your particular situation) after iterating through the information for the communications protocols in the current IOR.
One of three things could be responsible: a network error (if the thing you were trying to reach was remote), a setup error (a local server that isn't up), or your IOR is not valid. A non-valid IOR (which is not as likely to be the case as the other two) could result if, for example, you got the IOR from naming and tucked it away somewhere (like a file), then tried to use it weeks later. It could also come from network changes or something that made specific IOR information obsolete.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A control region attempted to register with the daemon during the control region initialization process. However, the daemon is not available for new control regions to register, probably due to a STOP command having been issued for the Daemon or because the Daemon was terminating when the register request was issued. The control region ends.
Retry starting the control region after the Daemon has finished coming down and is back up again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client has remained up while the WebSphere Application Server for z/OS installation bootstraps were re-run (i.e. ORBCBI specified). A reference the client has to an object on the server contains information rendered obsolete by the re-bootstraping.
Restart the client.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client has remained up while the WebSphere Application Server for z/OS installation bootstraps were re-run (i.e. ORBCBI specified). A reference the client has to an object on the server contains information rendered obsolete by the re-bootstraping.
Check the host file for the system IP address that matches the DAEMON IP_NAME of the system that is trying to connect with the EUI.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to the next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS controller execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
If thrown by the application code, change your application code to catch and process it or add a user exception to the IDL and throw it instead so that the bindings will catch the user exception and return it to the client. If thrown by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::BOA::change_implementation was invoked but is not supported.
Do not invoke CORBA::BOA::change_implementation.
CORBA::BOA::obj_is_ready was invoked but is not supported.
Do not invoke CORBA::BOA::obj_is_ready.
CORBA::BOA::deactivate_obj was invoked but is not supported.
Do not invoke CORBA::BOA::deactivate_obj.
CORBA::BOA::_get_implementation was invoked but is not supported.
Do not invoke CORBA::BOA::_get_implementation.
CORBA::BOA::_get_interface was invoked but is not supported.
Do not invoke CORBA::BOA::_get_interface.
CORBA::BOA::_create_request was invoked but is not supported.
Do not invoke CORBA::BOA::_create_request.
CORBA::BOA::_request was invoked but is not supported.
Do not invoke CORBA::BOA::_request.
CORBA::BOA::_is_a was invoked but is not supported.
Do not invoke CORBA::BOA::_is_a.
CORBA::BOA::_non_existent was invoked but is not supported.
Do not invoke CORBA::BOA::_non_existent.
CORBA::BOA::_is_equivalent was invoked but is not supported.
Do not invoke CORBA::BOA::_is_equivalent.
CORBA::BOA::_hash was invoked but is not supported.
Do not invoke CORBA::BOA::_hash.
CORBA::BOA::_has_ancestor was invoked but is not supported.
Do not invoke CORBA::BOA::_has_ancestor.
Controller thread is terminating because a non-retryable signal was encountered.
Provide the controller dump and look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servant thread is terminating because a non-retryable signal was encountered.
Look at the Servant dump and log to determine whether this is an application or WebSphere Application Server for z/OS problem. If termination occurred due to an application error, correct the problem. If it is a WebSphere Application Server for z/OS error then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue work to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue work from the pending queue to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A locate request returned an unknown object.
There are several reasons why you might get this message: :ol.:li.What you are looking for may be corrupted. :li.Your configuration may have changed so that what you are trying to locate is no longer in the configuration.:li. Your request could get forwarded to another server that is more appropriate to handle your request.:li.If it gets forwarded too many times, it may give up.:li. The locate message send could have failed due to a TCP/IP timeout or other reason. If the locate message send failed, COMM should have logged the error.:eol.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This exception is accompanied by message BBOO0053E with the name of the DLL.
Locate message BBOO0053E in the error log to determine the name of the DLL which could not be loaded. Place missing DLL in the STEPLIB concatenation so that it can be found
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servant tried to register with the control region but the server is being stopped.
None, if the server was being stopped. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The dispatch method returned an indication that the operation was not executed.
Ensure that the server is running with a DLL for the class that has a version of the xxxxxxxs.cpp file that supports the requested operation.
Validation of the object key failed.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Unable to get a list of initial services.
Check the error log for other messages. Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a proxy object for the object reference.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Input object is not a CORBA::Object.
Verify that the object inherits from CORBA::Object.
Something is not correct with the object key. Possibly a UUID of the server or controller is not consistent with the type of communication indicated in the object key.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The build_IOR method failed to create an IOR.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
get_SCO() was called and initialization was not done.
Insure that the BOA_init method was called prior to invoking the get_SCO method.
The object_to_IOR method failed to make an IOR.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
When marshalling an object reference into an encapsulation, the object reference was NULL.
Report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
When marshalling an IOR into an encapsulation buffer, a little endian byte order was detected. S/390 should be big endian byte order.
Report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but never progressed. A ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the client.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but never progressed. A ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the client.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM and received by a Servant. This request did not complete within the time period specified by the ORB dispatch time out value. The ORB_Request Registry cleanup routine, WLM Queue Snoozer, will drive the exception back to the Client.
Check that the ORB dispatch time out value is of sufficient length. See the instructions for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Transaction Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request is under a transaction that has timed out. A ORB_Request Registry cleanup routine, Transaction Timed Out, will drive the exception back to the client.
Ensure that the transaction time out value is of sufficient length. See the instructions for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing Servant.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
An unknown error occurred while processing a request in the Servant. This error code is returned to the client to indicate that processing of the request has failed.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::BOA::get_principal was invoked but is not supported.
Do not invoke CORBA::BOA::get_principal
A DII method was used on a CORBA::Request object that has not been created for use with DII.
Do not use this method or change the way the CORBA::Request object is created.
One of the DSI methods params(), ctx(), result() or exception of class ServerRequest has been called out of order.
Call the methods in the right order as specified in CORBA 2.0 and never call the same method twice.
Unable to dispatch method due to MO bindings generated as localonly objects.
Regenerate MO bindings as remotable objects.
CORBA::BOA::create was invoked but is not supported.
Do not invoke CORBA::BOA::create
CORBA::BOA::dispose was invoked but is not supported.
Do not invoke CORBA::BOA::dispose
CORBA::BOA::get_id was invoked but is not supported.
Do not invoke CORBA::BOA::get_id
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::Object_ORBProxy::_get_implementation was invoked from client which is not supported.
Do not invoke CORBA::Object_ORBProxy::_get_implementation from a client.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB::resolve_initial_references could not complete because it was unable to determine from where to get the initial references.
The RESOLVE_IPNAME environment variable must specify a TCP/IP name of a system where the initial references can be resolved (i.e. a S/390 system where a WebSphere Application Server for z/OS Systems Management server is running) or else a WebSphere Application Server for z/OS Daemon and Systems Management server must be running on the same system where the resolve_initial_references was issued
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::Object_ORBProxy::_decref() was invoked to decrement the reference count of the object but the reference count was 0.
Check application to make sure that CORBA::release is not being issued too many times. If it is an internal object then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
COMM failed when trying to drive a locate request to the daemon.
Check the error log for a COMM failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Naming IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
Since the Naming IOR is generated in Phase 1 of the Systems Management bootstrap , this situation indicates the Systems Management bootstrap needs to be run.
The IR IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
Since the IR IOR is generated in Phase 1 of the Systems Management bootstrap , this situation indicates the Systems Management bootstrap needs to be run.
The Systems Management SMO IOR has not been stored in the Systems Management server object, so it cannot be stored in the BGVT.
Since the SM SMO IOR is generated in Phase 1 of the Systems Management bootstrap, this situation indicates the Systems Management bootstrap needs to be run.
An attempt to start TCP/IP listening has failed.
Check the error log for messages relating to the error
BBOOSCO:readMasterRecord was called but the Master Record is not present. The Systems Management bootstrap is not being driven.
Restart the daemon with the -ORBCBI parameter so that the Systems Management bootstrap will be driven.
BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Possible causes are an update attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
BBOOSCO:initialize_SCOI_Server encountered an error while attempting to read server configuation information from DB2 tables.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered Possible causes are the address space is not authorized to use DB2, a read attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
BBOOSCO:initialize_SCOI_Server did not find the server defined in the Systems Management Tables.
Turn on exception tracing retry if it isn't already on. Additional information on which server record was not found will be traced. This error can only happen on the Systems Management server or the daemon. The probable cause is the Systems Management bootstrap failed or has not been run.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The index of the request sequence is equal or bigger than the length of the sequence.
Use only access to valid sequence elements.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:getSCO did not find the server defined in the Systems Management tables for this sysplex at the currently active level.
Turn on exception tracing retry and if it isn't already on. Additional information on which server was not found will be traced. Possible causes are the server wasn't defined using the Systems Management End User Interface (EUI) or if the server was defined using the Systems Management EUI, the conversation containing that server has not yet been activated using the Systems Management EUI.
BBOOSCO:getSCO could not obtain this server's configuration data from the Systems Management Control Region.
Turn on exception tracing and retry if it isn't already on. Additional information on which server is in error will be traced. Additional trace information may also be found in the Systems Management controller exception trace output. Possible causes are the server wasn't defined using the Systems Management End User Interface (EUI) or if the server was defined using the Systems Management EUI, the conversation containing that server has not yet been activated using the Systems Management EUI. Another possible cause is the server could not call back to the Systems Management controller. If the EUI indicates the server is defined and the conversation that contains it is the activated conversation, report the problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Class Manager failed to find the specified class in the list of classes supported by the server. The application that contains this class may not be properly defined or installed on the server.
Look in the error log to determine which class is in error. Additional information can be found in the trace when exception tracing is turned on. Possible causes are the class wasn't installed using the Systems Management End User Interface (EUI) or if the class was installed using the Systems Management EUI, the conversation containing that class has not yet been activated using the Systems Management EUI. If the EUI indicates the class is supported, report the problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CORBA::ImplRepository::find_impldef_by_alias was invoked by client.
Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef_by_alias
CORBA::ImplRepository::find_impldef was invoked by client.
Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying to narrow to a CORBA::ImplementationDef object.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying create an object.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trynig to build a IOR.
Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
CORBA::ImplRepository::find_impldef was invoked but an error ocurred trynig find the implementationDef for the input implid.
Ensure that the server for the input implid is started. When exception tracing is on, the input implid is traced.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
While a WebSphere Application Server for z/OS Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS Series servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An attempt was made to start a WebSphere Application Server for z/OS Series Control Region while another Controller with the same specific server name was active. Only one WebSphere Application Server for z/OS Series Control Region with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Controllers with the same specific server name.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Before a Servant can start, the control region which it is associated with must be initialized. This Servant was unable to find its owning controller and thus terminates.
Ensure this Servant's owning control region is active before starting the Servant.
An attempt was made to start a WebSphere Application Server for z/OS Series Control Region while another Controller with the same specific server name was active. Only one WebSphere Application Server for z/OS Series Control Region with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Controllers with the same specific server name.
Timeout occurred waiting for the naming server to start. We are unable to continue without it, so an exception is thrown.
Determine why the naming server failed to start before the timeout occurred, correct the problem, and try again.
Timeout occurred waiting for the IR server to start. We are unable to continue without it, so an exception is thrown.
Determine why the IR server failed to start before the timeout occurred, correct the problem, and try again.
Timeout occurred waiting for the Systems Management Server to start. We are unable to continue without it, so an exception is thrown.
Determine why the SM server failed to start before the timeout occurred, correct the problem, and try again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB_Request::setSystemException was invoked with an unrecognized System Exception. The unrecognized System Exception was traced and a CORBA::UNKNOWN System Exception with this minor code was placed into the ORB_Request to be returned to the client.
Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
ORB_Request::getSystemExceptionId encountered an unrecognized System Exception. The unrecognized System Exception was traced and a CORBA::UNKNOWN System Exception with this minor code was placed into the ORB_Request to be returned to the client.
Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
The WebSphere Application Server for z/OS Servant execution thread caught a ... This is an incorrect throw. A system exception with this error code is created and returned.
If application code is throwing something other than a system or user exception, change the application code to throw a system exception or a user exception that the method indicates it raises. If it is not application code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The DAEMON_IPNAME environment variable is set to an IP address. It must be set to an IP name, host n name.
Correct the DAEMON_IPNAME environment variable and run the Systems Management Bootstrap again.
Cannot open converter
Code set may not be compatible
Cannot open converter
Code set may not be compatible
Conversion Error
Code set may not be compatible
Conversion Error
Code set may not be compatible
Incorrect data length
Make sure the input data length is correct
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
The input codeset is not found in registry
check if codeset is supported
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
COMM failed when trying to drive a locate request to the daemon.
Check the error log for a COMM failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Cannot open converter
Code set may not be compatible
Cannot open converter
Code set may not be compatible
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Couldn't create a proxy object in rebuild_proxy.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Possible causes are an update attempt was made to tables that were not there, or the bind jobs were not run for WebSphere Application Server for z/OS.
CORBA::Context::delete_values was invoked but the input property name was not found in the context object.
If encountered by application code, check for application error. If encountered by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Processing in a Controller was halted because it was detected that the WebSphere Application Server for z/OS Daemon was not active.
The WebSphere Application Server for z/OS Daemon is required for WebSphere Application Server for z/OS servers to be active. All WebSphere Application Server for z/OS servers should terminate if the Daemon ends. This abend may occur if the servers are processing work when the Daemon terminates. Restart the Daemon when ready.
Processing in a Controller was halted because it was detected that the WebSphere Application Server for z/OS Daemon was not active.
The WebSphere Application Server for z/OS Daemon is required for WebSphere Application Server for z/OS servers to be active. All WebSphere Application Server for z/OS servers should terminate if the Daemon ends. This abend may occur if the servers are processing work when the Daemon terminates. Restart the Daemon when ready.
resolve_initial_references was called before doing ORB_init and BOA_init.
Make sure both the ORB and the BOA are initialized, either by a call to CBSeriesGlobal::Initialize() or by some other method, before resolve_initial_references is called.
resolve_initial_references_remote was called before doing ORB_init and BOA_init.
Make sure both the ORB and the BOA are initialized, either by a call to CBSeriesGlobal::Initialize() or by some other method, before resolve_initial_references_remote is called.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In encode_objref, pfactory is NULL after lookup of pfactory in ptable.
pfactory looks up the table entry for a certain classname in ptable. Look at the system error message to determine what classname was "looked up" in ptable.
In encode_objref, attempted to marshal a local_only object during a request. Here local_only means a local object residing in a pure client-only process.
Don't marshal a local_only object while a request is in progress.
BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS Series error log for information that will indicate what errors were encountered. Probable cause is the address space is not authorized to use DB2.
BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere Application Server for z/OS Systems Management Master Record.
Check the WebSphere Application Server for z/OS information that will indicate what errors were encountered. Series error log for Probable cause is the address space is not authorized to use DB2.
ORBid keyword to ORB_init must specify a value of BOSS
Provide a value of BOSS as the value of the ORBid keyword.
ORBid keyword must be specified on ORB_init with a value
Specify ORBid BOSS.
ORBsrvname keyword to ORB_init must have a value
Specify ORBsrvname with a valid server name
The ORBType keyword to ORB_init must have a valid value
Specify ORBType with a valid value.
Initialization of a WebSphere Application Server for z/OS Server failed loading a required product load module. Look for the accompanying message for the name of the module which could not be found.
Determine which module could not be found and why and correct the problem and restart the server.
RRS is required for WebSphere Application Server for z/OS Series to function. During initialization of a WebSphere Application Server for z/OS Server, RRS could not be found. The server terminates.
Make sure RRS is up and initialized.
The value specified for the ORBCBI keyword to ORB_init was not one of COLD, WARM, or HOT.
Specify a valid value.
The ORBCBI keyword to ORB_init requires a valid value
Specify COLD, WARM, or HOT as a value. Example: START BBODMN,BOOT='-ORBCBI COLD' (where BBODMN is the Daemon proc name).
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This exception is accompanied by message BBOO0053E with the name of the DLL.
Locate message BBOO0053E in the error log to determine the name of the DLL which could not be loaded. Place missing DLL in the STEPLIB concatenation so that it can be found
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
CBSeriesGlobal::hostName was called from a WebSphere Application Server for z/OS server space. In this environment the hostName returned would be the DAEMON_IPNAME environment variable specified for the Daemon on this system. However, it appears the daemon is not active (perhaps it is terminating) on this system.
If the Daemon was terminating or down at the time this error occurred, then no action is necessary as it is expected.
Systems management server created requested data space for SMF data gathering but the ALESERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Systems management server tried to create requested dataspace but the DSPSERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the DSPSERV return and reason codes. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Systems management server created the requested data space for SMF data gathering but when this server tried the ALESERV the ALESERV failed. No data gathering will be done.
Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The MVS STOP console command or the System Managment EUI STOP command has already been issued for this server. Subsequent commands are ignored.
Wait for the current stop processing to complete or escalate to an EUI Cancel or MVS console Modify Cancel command.
The MVS Modify Cancel console command or the System Managment EUI CANCEL command has already been issued for this server. Subsequent commands are ignored.
Wait for the current cancel processing to complete
No server name was specified for the Controller
Examine the Controller procedure or the parameters which were used to start the Controller and correct to specify the appropriate server name.
A user exception was caught by the main Controller routine
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
No server name was specified for the Servant
Examine the Servant procedure or the parameters which were used to start the Servant and correct to specify the appropriate server name.
A user exception was caught by the main Servant routine
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
The Servant is terminating due to an internal error.
Check the WebSphere Application Server for z/OS error log for information about errors preceeding this one which could have caused the Servant to terminate.
WebSphere Application Server for z/OS Daemon and Controllers must run authorized. However, the space has detected that it is not. The space ends in error.
The most probable cause of this is a dataset in the Steplib for the proc that is not in the APF list or the PPT settings for the load module(bboctl) should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
BBOOSCO:readSysplex was called but the Sysplex does not exist in the Systems Management database. The Systems Management bootstrap has not been run.
Restart the daemon with the -ORBCBI parameter to run the Systems Management bootstrap.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The server instance is terminating due to a MODIFY server-instance,CANCEL
Restart the server instance when the reason that required you to cancel it has been resolved.
The server instance is terminating due to a MODIFY server-instance,CANCEL,ARMRESTART
None.
An outbound request could not be sent because length of message exceeded maximum.
Try sending a smaller message.
A send oneway or send deferred request could not be sent because length of message exceeded maximum.
Try sending a smaller message.
An outbound request (callback) could not be sent because length of message exceeded maximum.
Try sending a smaller message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An application thread in an SR failed. A RAS_ASSERT brings down the Servant.
The SR will be restarted by WLM as necessary. The space is terminated because we don't know what damage the failing thread might have caused.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
WebSphere Application Server for z/OS Series terminated the thread due to error when attempting to pause for more work.
See previous messages for why the thread was unable to pause for more work.
WebSphere Application Server for z/OS Series terminated the SSL Handshake thread due to error when attempting to pause for more work.
See previous messages for why the thread was unable to pause for more work.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An outbound request could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
A send oneway or send deferred request could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
An outbound request (callback) could not be sent due to lack of available buffer space.
Try re-sending, or sending a smaller message.
An outbound response could not be sent by the SR because its size exceeded the maximum allowed for local IIOP messages.
Try sending a smaller response.
The server could not send the response to client because its size exceeded the maximum allowed for local IIOP messages.
Try sending a smaller message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to queue HTTP request to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS execution thread caught a user exception. This is an incorrect throw. The user exception will be represented by a system exception with this error code.
If this exception was thrown by application code, add the user exception to the IDL so that the bindings will catch the user exception and return it to the client. If this exception was thrown by system code, check the error log to see if the user exception was recorded when it was thrown. If it was not recorded, report this error to the next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS Controller execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
If thrown by the application code, change your application code to catch and process it or add a user exception to the IDL and throw it instead so that the bindings will catch the user exception and return it to the client. If thrown by system code, report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The destroyJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The detachThreadFromJVM external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ACRW request not queued because the server is being stopped. Control is returned to the requestor with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed.
None, if the error occurred in Servant that was initializing when the Controller was stopping. Otherwise report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, HTTP(S) Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or protocol_https_timeout_output) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Controller's attempt to dynamically define application environment failed. Most likely the application environment definition already exists and is running under the same subsystem name and node name.
Verify the application environment definition does not already exist, and if it does, verify the existing application environment and the new application environment are not being defined with the same subsystem name and node name.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In order for the WebSphere Application Server for z/OS Servant to start, the DAEMON GROUP NAME environment variable must be set. If it is not set, this exception results and the server region will not initialize.
Set the DAEMON GROUP NAME environment variable.
In order for the WebSphere Application Server for z/OS server to start, the daemon needs to be active.
Ensure daemon is active before starting the server.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Initialization of a WebSphere Application Server for z/OS Server loaded the wrong version of a required product load module. Look for the accompanying message for the name of the module.
Determine which module had the problem. Fix STEPLIB, LPA or Linklist so that the correct version of the module will be loaded and restart the server.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The attempt to create a dataspace via DSPSERV failed. No SMF data gathering will be done.
Locate message BBOO0038E in the error log to get the DSPSERV return and reason codes. If the problem persists, contact your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unknown user exception was thrown while processing a synchronous ACRW in the Controller.
Examine the Controller logs for the cause of the initial user exception.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempt to create a WLM enclave for an inbound MDB Request failed.
Examine the job log from the controller region for a related BBOO0037E message. This message will contain the return and reason code from the WLM create enclave service (IWMECREA).
Attempt to queue an MDB Request to WLM failed.
Issue D WLM,APPLENV=xxxxxx and make sure that it is not in the STOPPED state. If it is in the STOPPED state issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that caused it to get in the STOPPED state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
An ORB_Request was Queued to WLM, but its response was not received in a reasonable amount of time. An ORB_Request Registry cleanup routine, MDB Request Timed out, will cleanup the request.
Make sure that WLM can start the target server region (it may be in a quiesced state). Additionally, check that the time out value is of sufficient length. See the instructions for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout) in the WebSphere Application Server Information Center, which can be found at http:publib.boulder.ibm.com/infocenter/wasinfo/.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
ORB_Request::mergeMessageReplyBody detected that the servant was not able to obtain a cell in the comm dataspace to hold the large HTTP response.
Retry the request.
The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL
Restart the Daemon instance when the reason that required you to cancel it has been resolved.
The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL,ARMRESTART
none
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB, LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive a locate request to the daemon.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive an outbound request.
Check the error log for a communication failure error message.
A communication failure was detected while attempting to drive an outbound request.
Check the error log for a communication failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The redrive count for invoking an outbound request was exceeded.
Check the error log for a communication failure error message.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No class implementation exists for the method
Verify coding to the intended method is correct and supported. Do not invoke unsupported methods. For supported methods, instance manager detailed tracing may be enabled to capture method flow.
WebSphere read an interest back from the RRS recovery logs that was an unknown or invalid type. WebSphere cannot process this interest.
If you recently upgraded your service level, confirm that a cold start of WebSphere or RRS was not required. Ensure that your RRS logstreams are not corrupted.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failed to get terminator pointer from control.
Rewrite application logic.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tried to decrement thread association count below zero in decrement_association.
Transaction rolled back. Follow these procedures before calling IBM: <;ol>;<;li>;.Run initial diagnostics to determine if the rollback was due to a timeout. Ensure that the transaction timeout value did not expire.<;/li>; <;li>;If the timeout value did not expire, check the application to ensure the transaction's logic didn't cause the rollback.<;/li>; <;li>;Ensure you did not timeout DB2 or the Resource Manager.<;/li>; <;li>;If your application, DB2, or the Resource Manager did not cause the rollback then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ <;/li>;<;/ol>;
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
register_resource detected transaction is marked rollback.
See C9C21809.
register_synchronization detected transaction is marked rollback.
See C9C21809.
register_synchronization with superior coordinator raised unknown exception.
No action possible. Raise CORBA::UNKNOWN exception.
Resource registration with superior failed in genericCreate.
See C9C2181F
Null PropagationContext in extract_gitd.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during root prepare.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Detected that transaction is pending rollback.
See C9C21809.
Detected that transaction is pending rollback.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Attempted to access transactional objects that no longer exist. The method that threw the exception detected that the transactional object no longer existed and had either been committed or rolled back by some other asynchronous operation.
If the exception was thrown by your application, there may be a problem synchronizing the application execution and the attempt to query, modify, rollback, or commit the transaction.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
There was not enough storage preallocated to accomodate OTS structures.
Set TRACEDETAIL=(3,4,6) in your environment dataset (BBOENV).
Transaction Service does not support inbound transactional one-way requests.
Do not issue transactional one-way request.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
Control Region is shutting down. Transaction creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Transaction creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Control Region is shutting down. Creation is not possible.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resource commit came in on restart resource but resolver owns syncpoint.
This exception is normal processing for restart but indicates that attempts to contact the recovery coordinator have been unsuccessful. If this condition persists, ensure the recovery coordinator is up and functioning. It is possible that the application (or application environment) acting as recovery coordinator is down.
Resource rollback came in on restart resource but resolver owns syncpoint.
This exception is normal processing for restart but indicates that attempts to contact the recovery coordinator have been unsuccessful. If this condition persists, ensure the recovery coordinator is up and functioning. It is possible that the application (or application environment) acting as recovery coordinator is down.
Detected that transaction is pending rollback.
See C9C21809.
Rollback request was rejected because requested was not the initiator of the transaction. Obsolete.
Check for a possible application coding error.
Commit request was rejected because requested was not the initiator of the transaction. Obsolete.
Check for a possible application coding error.
Unable to register resource due to underlying recovery service logging limit.
Rewrite application to include fewer resources.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Unable to register local resource object due to implementation restriction.
Check for an application error. Refer to application documentation for restrictions on local resource.
Unable to register local synchronization object due to implementation restriction.
Check for an application error. Refer to application documentation for restrictions on synchronization onjects.
Encountered a user exception while trying to mark transaction on thread as rollback_only.
Check for an application error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRAPRP service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRAPRP service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRACMT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRACMT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRABAK service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRABAK service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRAFGT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRAFGT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRPDUE service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRPDUE service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code indicating that RRS is not currently active was returned from an invocation of an RRS Callable Service.
Make sure RRS is currently active. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRWID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRDINT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSPID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSWID service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRURD service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRRI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSUSI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRRUSI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSSPC service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIERS service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRLN service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRISLN service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code indicating that RRS is not currently active was returned from an invocation of an RRS Callable Service.
Make sure RRS is currently active. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Registration Services CRGSEIF service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery.For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIBRS service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRIRNI service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATREINT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during delegate prepare.
See C9C21809.
Inbound transaction is a nested transaction. WebSphere Application Server for z/OS does not support nested transactions.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resource one_phase_commit came in on a resource but a syncpoint was already in progress.
If the transaction was rolled back, see C9C21809.
Transaction rolled back with a heuristic mixed condition during delegate prepare.
RRS will write a record to LOGREC to indicate which resource manager(s) had a heuristic condition during the commit process. Follow the identified resource manager's procedures to resolve the heuristic condition. Also see C9C21809.
Invalid or NULL CosTransactions::Coordinator object extracted from an inbound. CosTransactions::PropagationContext structure.
Verify that sending ORB interoperates with WebSphere Application Server for z/OS.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Server region sending reply checks detected a mismatch between the original transaction associated with the method and the one currently associated with the thread.
Check the application for a logic error.
Transaction service is unable to locate transaction factory.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction service is unable to locate transaction factory.
Check systems management configuration for a definition of transaction factories.
Transactional request rejected because transaction is no longer active.
Check the application for a logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction server in server region detected a thread termination while the transaction was active on thread. This resulted in termination of the server region address space.
Check the application for a logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction server detected invalid state for rollback_only request.
WebSphere Application Server for z/OS internal processing. No error has occurred.
Transaction server detected transaction service containing deferred begin request.
WebSphere Application Server for z/OS internal processing. No error has occurred.
Non-existent transaction detected for rollback_only request.
Check the application for a logic error.
Invalid CosTransaction::PropagationContext returned from a 'deferred begin' outbound request.
Check the documentation on interoperability between ORBs.
An attempt was made to mark a transaction 'rollback_only' which was previously marked 'rolledback_only' or is in the process of being rolled back.
The transaction has or will be rolled back asynchronously from this processing. The initial rollback may have been initiated by the application itself, asynchronous from this call, or initiated by one of the resource managers participating in the transaction. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atrdint issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atrspid issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
atreint issued but UR log data limit exceeded.
A system limit has been exceeded and is no longer capable of storing transactional information. The application must reduce the number of different resource managers participating, possibly by narrowing the scope of the transactions or by redefining the composite objects so they are comprised of fewer components.
atreint issued against rolled back transaction.
The transaction has been rolled back asynchronously from this call. Either the rollback was initiated by the application asynchronous from this one, or one of the resource managers participating in the transactions initiated it. It is possible that the application has violated one of the resource manager protocols. Scan the traces previous to this one that would indicate when the rollback occurred and see C9C21809 for the rollback procedures.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere Application Server for z/OS syncpoint coordinator.)
Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere Application Server for z/OS syncpoint coordinator.) The detection of failure was prior to a system exception being raised for this transaction.
Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
An inbound request to a control region was detected to be contained within a transaction that had previously timed out.
Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
Commit request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
Check for a possible application coding error.
Rollback request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
Check for a possible application coding error.
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Persistant data that contains up level version numbers was retrieved during the OTS restart process. The server is brought down. This condition can occur when a new level of code was used to start an application server, run for a time, creating entries for transactions in RRS' hardened data logs, and then the application server is brought down. When the application server was restarted, an older level of WebSphere Application Server for z/OS code was used, and this is not supported.
Operator: Ensure the correct PROC was used to start this application server. System Programmer: Ensure the PROC used to start this application server has specified the intended level of WebSphere Application Server for z/OS code. If so, and you have knowingly regressed the level of WebSphere Application Server for z/OS code, you must follow the WebSphere Application Server for z/OS cold start procedures to undo any changes that were made to the WebSphere Application Server for z/OS environment while the application server was at the higher level. If you are not attempting to change code levels, and the PROC has specified the correct WebSphere Application Server for z/OS code, then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
OTS has determined that the method inbound to this server has timed out, because one of its transactional objects does not exist. Most probable cause is the transaction timedout.
Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
Transaction rolled back due to an unexpected return code from agent prepare.
Scan the traces subsequent to this one. TBD
Transaction rolled back because a protected resource is not in the proper state for a commit.
TBD
The control region was brought down after a CANCEL reply to MSGINDEX_BBOUENUS_OTS_HARDENED_DATA_LOSS.
None
Unknown transaction policy specified for continer.
Check the transaction policy specified for this container in the SM EUI.
Transaction that was started during a method dispatch was not completed before returning. The transaction was marked for rollback.
Check the application logic for a possible coding error.
A different transaction was present at container exit than at container entry. The transaction at exit was marked for rollback and the transaction at entry was resumed.
Check the application logic for a possible coding error.
Container initiated transaction caught unknown exception from commit.
None.
Container caught exception while attempting to resume the transaction that was present on entry.
None.
An error occurred while attempting to retrieve data about the current unit of recovery. RRS detected that the server had an invalid environment. The server will terminate itself and take a dump.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred while attempting to retrieve data about the current unit of recovery. RRS has become unavailable and/or the server cannot communicate with RRS.
Restart RRS and/or the application server that failed.
An error occurred while trying to commit the procedural global transaction on behalf of the container. The procedural global transaction was rolledback. Containers can start procedural global transactions in server regions, on behalf of business logic for certain transaction policies.
The resource that was being modified by the object was rolledback for some reason that is not known to the server. Consult rollback debug documentation for the resource manager which initiated the rollback. See RRS problem determination documentation for assistence in determining the rollback initiating resource manager.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Hybrid Global transaction could not be committed by the server because the resource managers involved in transaction were in the wrong state. The server region is terminated.
Check for an application logic error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Resume not allowed because the application has uncommitted local resources.
Local resources must be committed or rolled back before resuming another transaction. Check for an application coding error.
An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
A Heuristic Mixed exception was raised while attempting to commit container initiated transaction.
Check the traces and messages prior to this to determine what protected resource caused the heuristic outcome.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Tid length is zero, or less than or equal to bqual length.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
gtrid length exceeds MAX_GTRID length in extract_gtid.
Check the workstation logs to see if there are any previous corresponding exceptions. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRBEG service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRBEG service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRSENV service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A return code was issued from an invocation of the Resource Recovery Services ATRADCT service, indicating restart processing required.
Restart address space.
An unexpected return code was issued from an invocation of the Resource Recovery Services ATRADCT service.
Check the error log for message BBOT0004E. If present, this message will indicate the unexpected return code issued from the service. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during root commit.
See C9C2181F.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An inbound transaction context did not contain a reference to the coordinator object for the global transaction.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRS is unavailable on this system.
Ensure RRS has been started on this system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRS is unavailable on this system.
Ensure RRS has been started on this system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The client attempted to invoke an component, e.g. EJB, in a global transaction, however the the the component was deployed with a transaction policy that indicates it must not be invoked within a global transaction.
Correct the client application or redploy the component in error.
The client attempted to invoke an component, e.g. EJB, in a global transaction, however the the the component was deployed with a transaction policy that indicates it must not be invoked within a global transaction.
Correct the client application or redploy the component in error.
Transaction rolled back during root commit.
See C9C2181F.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During the RRS log name exchange process, RRS indicated that no previous log name was set. This condition occurred while the server was running in restart and recovery mode. This implies that the recovery system is not in the same RRS log group or that the server was never started on its configured system.
If you are attempting to start the server in restart and recovery mode on an alternate system, verify that RRS is in the same log group as the server's configured system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction manager attempted to contact an XA resource with an attempt to resume a previously suspended transaction. The resource responded with a return code indicating an error and processing cannot continue.
Check the message log for a message displaying the XAException thrown by the resource and the error code. Contact your resource vendor to determine why this error occurred.
The transaction manager attempted to contact an XA resource with an attempt to suspend a transaction. The resource responded with a return code indicating an error and processing cannot continue.
Check the message log for a message displaying the XAException thrown by the resource and the error code. Contact your resource vendor to determine why this error occurred.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An exception was raised while driving preInvoke on the transaction strategy for this method. A subsequent attempt to resume the local transaction that was on the thread before the transaction strategy was driven failed.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during prepare.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction rolled back during prepare.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
Transaction rolled back during prepare.
See C9C21809.
Transaction rolled back during commit.
See C9C21809.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An inbound request contained a transaction service context for a transaction that has already been added to the path sensitive branch registry but can't be found in the GTID map.
None. This condition can occur during or after an asynchronous transaction rollback. Common causes of asynchronous rollbacks include timeouts and abends.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere transaction service cannot support more than 254 inbound branches of a transaction in one server.
Check for a probable application coding error. A possible cause of this error is a recursive call between components in different servers that are participating in the same transaction.
RRS was cancelled or failed while WebSphere Application Server for z/OS was active. WebSphere is unable to process work when RRS is unavailable.
Restart RRS and WebSphere.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A resolver which was about to enter a blocking call to RRS could not re-register himself as a transaction alarm.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A subordinate OTS resource recieved a commit outcome from his superior node. The resource attempted to drive commit on any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
A subordinate OTS resource recieved a commit outcome from his superior node. The resource attempted to drive commit on any XAResources taking part in this transaction branch, but an unexpected exception was thrown.
The operation will retry periodically. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A subordinate OTS resource is attempting to drive the XAResources associated with his branch of the transaction. The resources cannot be driven yet because there is no server region capable of taking such a request at this time.
The operation will retry periodically. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21899.
See C9C21899
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21908.
See C9C21908.
See C9C21909.
See C9C21909.
See C9C21907.
See C9C21907.
See C9C21907.
See C9C21907.
See C9C218FF.
See C9C218FF.
See C9C21905.
See C9C21905.
See C9C2190A.
See C9C2190A.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for commit request.
See C9C21884.
Non-existent transaction detected for get_control request.
See C9C21884.
Non-existent transaction detected for suspend request.
See C9C21884.
Non-existent transaction detected for rollback request.
See C9C21884.
Non-existent transaction detected for Prepare request.
See C9C21884.
Non-existent transaction detected for Commit request.
See C9C21884.
See C9C21076.
See C9C21076.
See C9C2107B.
See C9C2107B.
See C9C2107C.
See C9C2107C.
The XaRecoveryTableManager class could not be loaded by the JNI.
The XaRecoveryTableManager class may not be on the classpath. Ensure that the CR classpath specified is correct. If it is correct then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The "instance" method on the XaRecoveryTableManager class could not be found by the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The one or more methods on the XaRecoveryTableManager class could not be found by the JNI.
Ensure that your classpath is set correctly. Failing that, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21928.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An array could not be allocated in the JVM through the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2192D.
See C9C2192D.
WebSphere is performing a warm start with RRS. A counter is maintained in the RRS logstream that must match a counter in the XA partner log in order for recovery to complete successfully. The counters do not match.
If the RRS logstream was restored from a backup copy, the XA partner log must also be restored from the same backup. Also, it is possible that the XA partner log was deleted. It will need to be restored from a backed up copy. If neither of these actions are possible, a cold start with RRS will be necessary to restore the logs to a usable state.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction sequence number wrapped and needs to be logged in the XA partner log, but the log write failed.
Ensure that the XA partner log file exists and is not full. Ensure that there is free space on the device that the partner log resides on. Look for message WTRN0076 for a detailed stack trace which may provide more information.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
See C9C21931.
A server region thread associated with a transaction received a piece of work for a different tranaction.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JTA transaction manager raised an unexpected exception while processing an inbound request.
Examine the error log for information about the original java exception that was raised.
The JTA transaction manager raised an unexpected exception while processing an outbound reply.
Examine the error log for information about the original java exception that was raised.
An unexpected java exception was encountered while obtaining a reference to the JTA transaction manager.
Examine the error log for information about the original java exception that was raised.
An unexpected OTS UserException was encountered while processing transaction manager request.
Examine the error log for information about the original CORBA exception that was raised.
The JVM raised an exeption while attempting to enter the monitor associated with the JTA transaction object from native code.
Examine the error log for information about the original java exception that was raised.
The JVM raised an exeption while attempting to exit the monitor associated with the JTA transaction object from native code.
Examine the error log for information about the original java exception that was raised.
The transaction manager could not find a reference to a recently created transaction in the active GTID map. This can happen when a server region initiated transaction completes during asynchronous processing.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
The transaction identifer generated in the server region did not match the identifier generated in the control region from the primary key.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A request to enlist XA resources in a transaction could not be completed as the control region does not yet have an interest in the RRS unit of recovery.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
A request to enlist XA resources in a transaction could not be completed as the control region no longer has an interest in the RRS unit of recovery.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
The JTA transaction manager raised an unexpected exception while attempting to determine the transaction attribute of the target object and operation.
Examine the error log for information about the original java exception that was raised.
The RRS service ATREINT1 returned the value ATR_CONTEXT_TOKEN_INV. The Transaction will be marked rollback-only.
None.
A request was received for a transaction that has already gone through a syncpoint.
None.
Non-existent transaction detected in the received_request method.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2192D.
See C9C2192D.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The "instance" method on the ControllerRequestProcessor class could not be found by the JNI.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A call to RegisterNatives failed. The method could not be registered with the JNI.
Ensure the classpath has not been modified and that your service level is not corrupted. For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21928.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A method on the TranAttributeMap class could not be found by the JNI. There is likely a mismatch between the native and Java WebSphere libraries.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The transaction manager could not find a reference to a recently created transaction in the active GTID map. This can happen when a server region initiated transaction completes during asynchronous processing.
Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
See C9C21076.
See C9C21076.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for Forget request.
See C9C21884.
No outcome received while heuristically rolling back a restarted transaction.
Examine the error log for information about the cause of the failure. The transaction may have completed already. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected while heuristically rolling back a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No outcome received while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. The transaction may have completed already. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Transaction in wrong state for commit while heuristically committing a restarted transaction.
Examine the error log for information about the cause of the failure. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C21908.
See C9C21908.
See C9C21909.
See C9C21909.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An XA resource recieved an outcome. The resource attempted to resolve any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
An XA resource recieved an outcome. The resource attempted to resolve any XAResources taking part in this transaction branch, but one or more of the resources threw an exception.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
An XA resource recieved an outcome. However the XARecoveryAgent was not found to resolve any XAResources taking part in this transaction branch.
The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
RRS macro ATRQUERY was issued to query the RRS logs. This service returned a bad return code indicating that the issued action failed to complete.
Check the message and error logs for the return and reason codes. For further information on the service and return code, please see publication SA22-7616 entitled MVS Programming: Resource Recovery. If the problem persists, please contact the IBM support center.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Non-existent transaction detected for Register request.
See C9C21884.
The JVM could not be found by the native method.
Look for error messages in the server output which may explain why the JVM did not start. If the problem persists, contact the IBM Support Center.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Invalid object reference detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Shasta marshaling error detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Shasta internal error detected.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
_narrow method caught non-CORBA exception
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CORBA::UNKNOWN error has been unmarshalled in the bindings from javaspace.
Look prior to this message to see if any java error messages have been recorded
A CORBA::UNKNOWN error has occured in the SOMRef process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function _CallMethod in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _CallMethod in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _StrongRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _StrongRef in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
Function _WeakRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/SOMBase.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
Function _WeakRef in bbolrt.cpp could not find the "_weakref" method in Java class /com/ibm/som/corba/rt/SOMBase.class
Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
Function _WeakRef in bbolrt.cpp did not get a weak object reference for a Java object.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function _isInstanceOf in bbolss.cpp is not implemented.
Do not use this function.
Function SOMCPP_SOMObjectDecoder in bbolsreq.cpp detected that the length in the encapsulation does not match the length of a pointer on the OS/390 platform.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function take_buffer in bbolsreq.cpp detected that the length of the CDR buffer is zero.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Function decode_SOMRef in bbolsreq.cpp detected that the length in the encapsulation does not match the length of a pointer on the OS/390 platform.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In bbolpoi.cpp, some CORBA DII object is nil after creation.
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In bbolpoi.cpp, some Context methods not supported
Change application program accordingly
Tried to find a proxy factory for a class and it was not available to the server. The proxy factory was going to be used to cast a void pointer to a CORBA::Object_ptr so that an object reference could be marshaled back into the Java environment.
Insure that the class name that is indicated in the associated message is installed on the server.
Function checkJavaException was called An Exception was thrown in a JNI thread.
Look prior to this message to find what JNI Exceptions were thrown.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RuntimeUtil failed to initialise because it failed to complete a FindClass
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RuntimeUtil failed to complete initilization
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
For assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The WebSphere Application Server for z/OS and OS/390 ORB is not initialized. An IOR can not be created from an object if an ORB is not available.
Check error logs for failure of the ORB to initialize. If there are not any ORB initialization failures then the initialization will need to be added to the client code.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JVM System.exit or Runtime.exit routine was called and the JVM has terminaated. As part of this processing, WebSphere has terminated the current process.
If the exit request was issued by an application, please examine the application to determine why exit was called. If Java 2 Security is enabled, the application was explcitly given permission to call this API. If this behavior is not desired, do not grant the application the RuntimePermission "exitVM". If the exit was not initiated by the application then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The JVM has unexpectedly aborted. As part of this processing, WebSphere has terminated the current process.
Check the error logs for a possible cause. If the problem cannot be resolved then look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Environment variables value field is empty or not set (which is a mandatory one)
Assign a valid (non-null) value for the environment variable indicated by message (this minor code is for mandatory environment variables not mentioned in current.env files)
This server was started after a Stop command was was issued for the WebSphere Application Server for z/OS Daemon. Daemon stop processing stops all active servers and no new servers are allowed to start. Any servers starting after the stop command is issued will receive this failure.
None
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In order for the WebSphere Application Server for z/OS Daemon to start properly, the protocol_iiop_daemon_listenIPAddress environment variable must be set. If it is not set, this exception results and the Daemon will not initialize.
Set the protocol_iiop_daemon_listenIPAddress environment variable appropriately (probably to the TCP/IP host name of the system where you are trying to start the Daemon).
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application Servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
WebSphere Application Server for z/OS server address spaces can not start without an active WebSphere Application Server for z/OS Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
Start the WebSphere Application Server for z/OS Daemon on this system prior to starting other WebSphere Application servers.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
All WebSphere Application Server for z/OS servers must have a specific server name specified as an input parameter following the keyword '-ORBsrvname'. This name must be no longer than 8 characters. The specified name was greater than this length.
Specify the correct specific server name when starting the server. This name was specified when the server was defined to WebSphere Application Server for z/OS Systems Management Adminstration.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
In PPT::PPT(char*), BBO3PPT1 Macro is unable to call IEFPPSCN because APF Not Authorized to perform such action.
Make Sure Load Module is APF Authorized.
PPT Entry Specification Error
Correct PPT Entry - BBOSCHED
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was active. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was active. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A bad return code received from service CRGRRMD.
See message BBOO0056E in the error log for additional information.
A bad return code received from service CTXSDTA.
See message BBOO0056E in the error log for additional information.
A bad return code received from service CTXBEGC.
See message BBOO0056E in the error log for additional information.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Controller while another Controller with the same specific server name was also starting. Only one WebSphere Application Server for z/OS Controller with a given specific server name can be active at one time. This Controller terminates in error.
Do not attempt to start two Controllers with the same specific server name.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
An attempt was made to start a WebSphere Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon was also starting. Only one WebSphere Application Server for z/OS Daemon can be active on a system at one time. This Daemon terminates in error.
Do not attempt to start two WebSphere Application Server for z/OS Daemons on the same system at the same time.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
While a WebSphere Application Server for z/OS Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere Application Server for z/OS servers can exist without a Daemon present on the system, this server must end.
Determine why the Daemon failed and restart the daemon and other servers as necessary.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A Servant was started and was unable to find the Controller it goes with.
If the Servant started as the Controller was ending then this is normal. If a Servant was manually started (instead of allowing WLM to start it) then possibly the parameters were incorrect or it was started on the wrong system.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 IDENTIFY processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 SIGNON processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service.For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 CREATE THREAD processing failed for the DB2 active server repository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 Terminate Thread processing failed for the DB2 active server respository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RRSAF DB2 Terminate Identity processing failed for the DB2 active server respository thread.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An unsupported daue work queue element type was detected. Processing of the daue work queue will be terminated.
Report the problem and accompanying information to your next level of service. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Initialization of a WebSphere Application Server for z/OS Server failed loading a required product load module. Look for the accompanying message for the name of the module which could not be found.
Determine which module could not be found and why and correct the problem and restart the server.
No server name was specified for the Daemon.
Examine the Daemon procedure or the parameters which were used to start the Daemon and correct to specify the appropriate server name.
A user exception was caught by the main Daemon routine.
Examine the error log for information regarding the thrown exception and take whatever action the exception indicates. This should never happen :-)
WebSphere Application Server for z/OS Daemon and Controller must run authorized. However, the space has detected that it is not. The space ends in error.
The most probable cause of this is a dataset in the Steplib for the proc that is not in the APF list or the PPT settings for the load module(bbodaemn)should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
The DSNLOAD which is done to setup DB2 from the DAUT thread initialization failed. An exception trace is cut with the return code.
The Daemon's call to DSNLOAD setting up DB2 failed. An exception trace is cut with the return code from DSNLOAD.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SQL error besides 'not found' occurred while trying to delete all entries from the DB2 ASR table. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error besides 'not found' occurred while trying to delete all entries from the DB2 ASR for a given system name. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to add an entry to the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to delete an entry from the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to update an entry in the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to read all entries in the DB2 ASR. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to read all entries in the DB2 ASR for one system. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to open a cursor to read all the DB2 ASR entries. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to open a cursor to read DB2 ASR entries for 1 system. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
An SQL error occurred while trying to delete a DB2 ASR entry at the current cursor location. An error log entry is made with the DB2 error text. Depending on the SQLCODE, we may ASSERT to bring down the space.
Look at the error log for further information about the error. If the SQLCODE is -812 or -805 you have a Bind vs. Code timestamp problem and may need to re-bind.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A Daemon is configured to run on a particular system. This Daemon was started on a system in the sysplex other than where it was configured to start. In the event of a system failure, automation or ARM may restart the Daemon, Systems Management, and Controllers on another system in order to allow transactions to rollback and locks to be released. As the Daemon has no cleanup work to do, it fails with this minor code. A Daemon/SM configured to run on the restart system is required to be active before SM and Control regions will be allowed to start on a system where they are not configured to run.
If started as part of a cross system recovery no action is required. If the Daemon was started as part of an attempt to bring up the WebSphere Application Server servers, either start these servers on the system where they are configured to run, or configure new servers to run on this system.
In order for the WebSphere Application Server for z/OS Daemon to start properly, the DAEMON GROUP NAME environment variable must be set. If it is not set, this exception results and the Daemon will not initialize.
Set the DAEMON GROUP NAME environment variable.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Externalization StreamIO method in which this exception occurred was issued out of order. This exception will occur if a get_buffer_ref() method was previuosly issued to obtain the current StreamIO buffer and then a StreamIO method is invoked before a set_buffer_ref() is issued to re-establish a StreamIO buffer.
Correct your code to ensure that when a get_buffer_ref() is issued to get the StreamIO buffer, a set_buffer_ref() is done to re-establish a StreamIO buffer before any other StreamIO methods can be issued.
An attempt was made to invoke the Externalization StreamIO method, write_object(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the write_object method from your code.
An attempt was made to invoke the Externalization StreamIO method, write_graph(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the write_graph method from your code.
An attempt was made to invoke the Externalization StreamIO method, read_object(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the read_object method from your code.
An attempt was made to invoke the Externalization StreamIO method, read_graph(). This method is not implemented by the Externalization StreamIO support.
Remove any usage of the read_graph method from your code.
An attempt was made to invoke the 390 StreamIO destructor. This destructor should never be called. IExtended390 streamIO objects are returned to a stack and never destructed.
Locate the code that called the invalid operation and correct its usage.
An attempt was made to invoke the Externalization StreamIO method, read_wchar() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the read_wchar method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, read_wstring() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the read_wstring method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, write_wchar() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the write_wchar method from your code or switch to an IBM format 2 externalization.
An attempt was made to invoke the Externalization StreamIO method, write_wstring() on an IBM format 1 externalization. This method is not supported by the Externalization StreamIO support for format 1 externalizations.
Remove any usage of the write_wstring method from your code or switch to an IBM format 2 externalization.
An attempt was made to allocate an encapsulation buffer for an EncapIIOP object that is being used by the Externalization StreamIO support.
Report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
This method is not implemented.
Call another method to perform the intended operation.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Wide character data was detected within an encapsulation but a wide character transmission code set was not negotiated when the associated session was established (this prevents CB/390 from transmitting wide character data within this session)
Verify that wide character support is configured correctly.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An invalid multi-byte character value was detected within an encapsulation or in data to be encapsulated. (This is most likely caused by the presence of an invalid multi-byte character within the request or reply parameters associated with a method invocation on a CORBA object.)
Inspect the values of wide character parameters associated with the method invocation that caused the error.
The native code page used for wide characters is non-byte-oriented with a character length other than 2.
Switch to a native code page for wide characters that is either byte-oriented or is non-byte-oriented with a character length of 2.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The length of a character or character array changed as a result of doing a codepage conversion on the character data while marshaling or unmarshaling the data.
If a multi-byte code page is being used, change the IDL type used to represent the multi-byte data to either a string or wchar.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Default identities are allowed but a default identity has not been defined for this server. Authorization is denied.
Configure system management to define a default identity for this server.
A userid with an invalid length was provided in the security context. Authorization was denied.
The ORB Request for the client must supply an eight character string, padded with blanks for userids less than eight characters.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Client ID does not have RACF authorization to BIND to this server.
Obtain the needed RACF authorization and resubmit the request (CB.BIND.servername).
This is a single client session and the client ID in the request does not match the ID from a previous request. Only one client is authorized for a single client session.
Either change the RACF authorization to make this a multi client session or submit all requests from the same client for a single client session.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AccountingId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType NonRepudiationId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType GroupId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Role is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AttributeSet is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Clearance is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType Capability is NOT IMPLEMENTED as a SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Session owner does not have RACF authorization to pass multiple clients to this server.
Obtain the needed RACF authorization (CONTROL) and resubmit the request (CB.BIND.servername).
Client id does not have RACF authorization to execute this <serverName.homeName>.
Obtain the needed RACF authorization and resubmit the request.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Client ID does not have RACF authorization to execute on this server.
Obtain the needed RACF authorization and resubmit the request.Note: For DCE, authentication map the DCE principal to a valid. MVS userid Clients from a foreign DCE cell can never be permitted
There was no password provided in a security context thought to contain a userid and password.
If running with the default userid, see if a default password was set.
SecurityAttributeType Public is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
The copy method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the set_security_features method in SecurityLevel2::Credentials is not implemented.
Do not ask for this method in this class.
the get_security_features method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the is_valid method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
the refresh method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
Do not ask for this method in this class.
The SCO information indicated that this server was to use DCE security but DCE security services were not available when the server was started.
Look in the server logs for messages to see why this server was unable to access DCE security services. Based on these messages, perform the appropriate corrective actions and try the operation again.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
DCE PRINCIPAL is not mapped to MVS userid.
"Set up principal UUID to MVS ID map in RACF"
Version of Native security does not match expected version #.
Check security version of client and server
Raw Client executing protected code
Fix client code
Server attempting to execute non server code
Fix server code
A native security context was sent remotely
Possible external hack attempted
A native security context was sent remotely
Possible external hack attempted
Get Transportable Identity returned a null
IBM internal problem
Get Transportable Identity returned a null
IBM internal problem
The non-repudiation credentials type is not implemented.
Do not ask for this credentials type.
ALthough the request orignated in the Server region, no Native Security Context exists. Originated in get_userid() method.
ORB should have copied the Native Security CTX from the ORBR in the Server back to the ORBR in the CTL on the outbound flow from the server. See if the Servant abended before doing the copy.
ALthough the request originated in the Server region, no Native Security Context exists. Originated in get_userid_build_ctx() method.
ORB should have copied the Native Security CTX from the ORBR in the server back to the ORBR in the CTL on the outbound flow from the server. See if the Servant abended before doing the copy.
Client id does not have RACF authorization to USE this server.
Obtain the needed RACF authorization and resubmit the request (CB.servername).
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Mutual authentication failed when client tried to verify the server.
investigate the server.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
There is no authentication for this client
Failure trying to authenticate client
A client is attempting to initiate a DCE protected conversation with a server with a DCE quality of protection level that is less than that which has been set for this server by the system administrator. The server returns a no permission exception to the client.
The client can increase the quality of protection that it uses to initiate the DCE protected conversation, or the server can have its setting lowered to match the client's requested protection level. Servers will respect a client's requested DCE quality of protection level if it is equal to or greater than its quality of protection setting. The servers quality of protection level is controled through the System Management User Interface. The client's quality of protection level is set through the System Management User Interface, or on OS/390 the environment variable CLIENT_DCE_QOP.
A client process failed in the attempt to initiate a a request to a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in a request to a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security over SSL.
The request probably failed because the specified DCE principal and/or DCE password are invalid. Please respecify REM_DCEPRINCIPAL and/or REM_DCEPASSWORD and try again.
An SSL Client Certificate was received by a server during SSL handshake processing. This certificated cannot be resolved to an identity.
The SSL client certificate is probably not in the servers keyring, and cannot be transformed into an S/390 identity. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in a request to a server using an unknown security method.
This is an internal error! Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
RACF - Parameter list error occurred
RACF - An internal error occurred during RACF processing
RACF - Recovery environment could not be established
RACF - User ID is not defined to RACF
RACF - Password or PassTicket is not valid
RACF - Password is expired
RACF - User ID is revoked
RACF - User is not authorized
RACF - Certificate is not valid
RACF - Either no user ID is defined for this certificate or the certificate status is NOTRUST
Null sessionid in NatSecCtx_Auth
MethAuthCheck was issued in an address space without a BACB
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The client has a DCE quality of protection setting of confidential and the target server does not support DCE security. In the work station version of WebSphere Application Server for z/OS, servers advertise that they support DCE security whether they do or not. If it is determined that the target server advertised DCE security, but really does not support it, the OS/390 client checks to see what DCE quality of protection the client has asked for. If it is confidentiality the request is terminated with this exception. If the client has any other DCE quality of protection setting the request proceeds with no security.
If the client requires DCE security with the quality of protection setting of confidentiality, the administrator of the targeted server must enable DCE security for the server. If the client does not require DCE security with a quality of protection setting of confidentiality the environment variable CLIENT_DCE_QOP can be set to any value other than CONFIDENTIALITY. If the quality of protection is lowered in this manner the request will continue but no security is enabled for it.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to mutually authenticate with a server using DCE security.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Servers reply to the Client's initial message does not contain a session ID. This indicates that the server did not agree to a session with this client. Check for a server exception returned to the client.
Check that the needed RACF authorization has been established on the server. If not, obtain the necessary RACF authorization and resubmit the request (CB.servername).
Servers reply to the Client's initial message has already been processed by this client.
The handshake between the client and the server is out of sequence. Resubmit the request
As part of the DCE mutual authentication process the server was unable to verify the identity of the client. This exception is initially raised by a server as a response to a failed gss_accept_sec_context() GSS_API call. A message should appear in the server's message log with the GSS_API major and minor status codes returned from this call.
Refer to the OS/390 DCE Messages and Codes book for a description of the status codes returned. Based on the status codes found take the appropriate actions and have the client retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ Ref: OS/390 V2R7.0 DCE Messages and Codes Document Number: SC28-1591-06
The return value for the current RACO pointer in the OPI for the original inbound client is NULL when getTransportableIdentity() is called while building a security context an outbound request.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error in the DEC mutual authentication process occurred during the creation of an Authentication object or there is a problem in the DCE first time message handshake
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The authentication class was not found during the DCE mutual authentication process after the DCE first time message was handled.
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
Server attempting to execute non server code
Fix server code
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Mutual authentication failed when client tried to verify the server.
investigate the server.
Mutual authentication failed when client tried to verify the server.
investigate the server.
Mutual authentication failed when client tried to verify the server.
investigate the server.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
Do not ask for this SecurityAttribute type in this class.
An error occurred during the new of the saved RACO pointer in security method convertToSessionID. Possibly memory could not be allocated for the pointer.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
No client security context (and therefore no identity) has been supplied in the ORB Request and default identities are not allowed for this server. Authorization is denied.
Either the client ORB Request must contain a security identity in the security context, or the system administrator should configure system management to allow undefined users.
Only a client userid has been supplied in the ORB Request sent to this server. The client must supply more than just a user id (i.e., password, etc) to gain access to a server. Authorization is denied.
The client ORB Request must contain a complete security context.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SSL Type 1 Association Complete service context encountered by the server but there was no corresponding authentication segment.
Review the message logs for the reason that the request failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An SSL Type 1 service context was received by a server with a msgtype of something other than ASSOC_COMPLETE or MUTUAL AUTH.
You may be using an incompatible client and server configuration. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The SSL Session identity was not given update authority and is not authorized to propagate asserted identities.
Check to ensure that the session identity should be authorized to propagate asserted identities, and if so give the identity update authority. If the SSL session identity already has update authority, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
SSL session received asserted identity service and this was not accepted. Either the identity was unknown on the target host, or this server is not authorized by the target server to assert identities.
Verify the CB.BIND on the target server and consider disabling asserted identity for this client or server.
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a SupportedSecurities structure in the security method createOutbound. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A process failed to find the SSL kerberos security context associated with the request.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the allocation of a sting for a Kerberos session identifier in the security method KRBAuth. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server using Kerberos GSS_API security over SSL.
Review the message logs from the contacted server for the reason that the request failed. Based on the information found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a sting for a Kerberos name in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a Kerberos GSS_API service context in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the new of a sting for a Kerberos name in the security method initKRB. Memory could not be allocated.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred during the allocation of a sting for a Kerberos security context in the security method KRBAuth. Memory could not be allocated on the server.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error in the DCE api gss_init_sec_context.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error when processing a SSL Kerberos GSS_API context. The session identifier contained in the context is in use by the server and the context contains a GSS_API token.
Review the context sent by the client process. Based on the context take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The requester does not have the authorization to make this request.
Contact your security administrator and request authorization for this service and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The requester failed the Kerberos authentication test the server ran out of memory.
Check the server logs for the reason that the Kerberos authentication failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A client process failed in an attempt to authenticate with a server.
Review the message logs for the reason that the request failed. Based on the error messages found take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to accept the client context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to extract the principal name from the security context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name extracted from the security context is too long.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name does not contain an "at" sign (@). The principal name should be in the form principal@realm.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During Kerberos authentication, CB was unable to obtain the SAF user associated with the Kerberos principal because there is no mapping between the Kerberos principal and a RACF userid.
Contact your security administrator and have the principal mapped to a RACF userid. The SAF and RACF codes are documented in the OS/390 Security Server Callable services book. Once the principal is mapped, retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Failure trying to authenticate role name
Correct any problems with the definitions of users or EJBROLE profiles. Ensure the EJBROLE class is active.
push Identity failed, because on OS thread function disabled
Cannot synch OS thread to Userid, enableSyncOSThread = false. Check settings in SM GUI
Caller ID does not have permission to execute method
Make sure that the caller ID has permission to access that particular method.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included authorization token. This level of z/OS WebSphere does not support authorization tokens.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send authorization tokens to servers that do not support them.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context contained an asserted identity of the Principal Name type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of principal names.
The CSIv2 security attribute service context contained an asserted identity of the Certificate Chain type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of Certificate Chains.
The CSIv2 security attribute service context contained an asserted identity of the Distinguished Name type and, the target server is not configured to support this type of asserted identity.
There are two actions that can be taken to eliminate this exception. One is to have the client process change its request to use a different asserted identity type that is supported by the target server. The second is to have your J2EE security administrator configure the server to support the assertion of Distinguished Names.
The CSIv2 security attribute service context contained an asserted identity of the Identity Extension type and, the target server is not configured to support this type of asserted identity.
Have the client process change its request to use a different asserted identity type that is supported by the target server.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the length of the authentication token.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the mechanism object identifier (OID) of the security mechanism.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the mechanism object identifier (OID) of the security mechanism.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP exported user name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP target name.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
The CSIv2 security attribute service context included in a GIOP request contained a invalid userid.
This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid userid.
The CSIv2 security attribute service context included in a GIOP request contained a invalid password.
This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid password.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The context does not include a valid userid.
The CSIv2 security attribute service context included in a GIOP request indicates that the anonymous user is to be used for authorization checks, and the target server does not support this.
This is most likely a problem caused by the process that formed the request and context. The most likely solution is to have the client. include authentication information when contacting this server.
Get Transportable Identity returned a null
IBM internal problem
The CSIv2 security attribute service context included in a GIOP request is not valid.
We have not done Kerberos yet.
The CSIv2 security attribute service message context contains a context identifier that in not valid at the target server.
The most likely cause of this problem is that the target server has invalidated the client's context identifier. A server may do this so that a client is forced to re-authenticate itself. No action is required, this exception should be handled by a CSIv2 client.
The getJavaEnv external function was not found in the BBOLRT dll.
Check to be sure that the correct version of BBOLRT is accessible to the failing address space either through STEPLIB,LNKLST or via loading the runtime into LPA.
The BBOLRT dll was not able to be loaded.
Check to be sure that the failing address space has access to the WAS/390 EE runtime DLLs either through STEPLIB,LNKLST or via loading the runtime into LPA.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The creation of a CSIV2 GSSUP context failed.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The creation of a CSIV2 Idenity Assertion context failed.
Review the message logs for the reason that the new failed. Based on the error messages found take the the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The user identitfier that is to be used for the asserted identity is not a valid z/OS user.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. The principal name mechanism is not supported on z/OS.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the SSL/TLS session identity does not have SAF 'control' access to the profile CB.BIND.servername. This identity is found by mapping the client X509 certificate that was passed during SSL/TLS initialization, to a RACF id. This is the identity that requires control access to the profile CB.BIND.servername.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the z/OS user that was authenticated in the CSIv2 supplemental client authentication layer does not have 'control' access to the profile CB.BIND.servername. Contact your security administrator and request that this user be granted access to the asserted identity service.
The CSIv2 server was not able to use the asserted identity requested because the CSIv2 authenticated identity was not authorized to the asserted identity service.
The most likely reason for this is that the server default identity does not have 'control' access to the profile CB.BIND.servername and there was no SSL session owner (no client certificate) on the session. Contact your security administrator and request that this user be granted access to the asserted identity service.
The CSIv2 server was not able to use an establish context because it indicated that it contained a asserted principal but no principal was found.
The most likely reason for this is that the context generator is sending a bad context.
The CSIv2 server was not able to use an establish context because it indicated that it contained a asserted principal but no principal was found.
The most likely reason for this is that the context generator is sending a bad context.
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The server was not able to produce a token value based on the authorization token sent in a CSIv2 context.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it forms contexts compliant with the OMG CSIv2 specifications.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included a Kerberos authentication token that could not be processes because the server could not load the Kerberos DLL.
An error occurred when the server attempted to accept the client Kerberos gssapi context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occurred when the server attempted to extract the principal name from the security context.
Review the message logs for the reason that the request failed. Based on the error messages found, take the appropriate actions and retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name extracted from the security context is too long.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The Kerberos principal name does not contain an "at" sign ( The principal name should be in the form principallm.
Correct the principal name and try the request again. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During Kerberos authentication, CB was unable to obtain the SAF user associated with the Kerberos principal.
The most likely reasom is that there is no mapping between the Kerberos principal and a RACF userid. Contact your security administrator and have the principal mapped to a RACF userid. The SAF and RACF codes are documented in the z/OS Server Callable services book. Once the principal is mapped, retry the request. If the problem persists, report it to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included a X509 certificate identity token that could not be processed because the token was malformed. The token contained a certificate length that was too large or not valid.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context included an X501 Distinguished Name token. There was an internal error processing the token. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
The CSIv2 security attribute service context included in a GIOP request is not valid.
The CSIv2 security attribute service context was received that the same key as an exisiting context. However, the credentials were not the same. All credentials with the same key must have the same credentials.
The CSIv2 security attribute service context included in a GIOP request that is not valid .
The CSIv2 security attribute service context included a realmname that zOS attempted to convert to the UTF1047 code page. The convert failed. This is an internal error. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CSIv2 service context contained an LTPA token that could not be mapped to a zOS userid.
A CSIv2 security attribute service context was received that contained an LTPA token. The token could not be validated and was not mapped to a zOS userid. Either the token has expired or is not known to the system. Make sure that the LTPA configuration between the sender system and receiver system is correct.
During a CBIND access check a CSIv2 service context contained an LTPA token that could not be mapped to a z/OS userid. No client bind authorization could be done.
A CSIv2 security attribute service context was received that contained an LTPA token. The token could not be validated and was not mapped to a z/OS userid. Either the token has expired or the user it represents is not known to the system. Make sure that the LTPA configuration between the sender system and receiver system is correct.
During a CBIND access check a CSIv2 service context contained an z/OS user id that could not be found on the system. No client bind authorization could be done.
A CSIv2 security attribute service context was received that contained a z/OS userid that could not be found on the target system. The most likely reason for this is that the requested user is not in the z/OS registry. Insure that the user that is being requested is a member of the z/OS registry.
During a CBIND access check the initACEE callable security service failed to convert an SSL Certificate into a z/OS native security context. No client bind authorization could be done. The SAF return and reason codes can be found in the server log file.
See return codes for initACEE (IRRSIA00) in the Security Server (RACF) Callable Services or equivalent reference for other security products. Security Server reference documentation for initACEE include: Security Server (RACF) Security Administrator's Guide and Security Server (RACF) Callable Services for initACEE service call return and reason codes.
During a CBIND access check a CSIv2 asserted distinguished name failed to be mapped to a z/OS userid. No client bind authorization could be done. The SAF return and reason codes can be found in the server log log file.
See return codes for initACEE (IRRSIA00) in the Security Server (RACF) Callable Services or equivalent reference for other security products. Security Server reference documentation for initACEE include: Security Server (RACF) Security Administrator's Guide and Security Server (RACF) Callable Services for initACEE service call return and reason codes.
During a CBIND access check a CSIv2 asserted distinguished name failed to be mapped to a z/OS userid. No client bind authorization could be done.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
During a CBIND access check an ACEE could not be obtained so client bind authentication cannot be done.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A CSIv2 service context contained an ltpa token that was not valid.
The token has most likely expired. The client initiating the connection should resend the request with new credentials. No user action is required.
A CSIv2 service context contained a userid and password. The server attempted to login using the userid and password but the login failed.
The userid and password was not valid for the current registry. Check the registry to make sure they are still valid. If the configured registry is not SAF, there may be a problem connecting to the registry. Check the server output log for problems communicating with the registry.
The server received a CSIv2 establish security attribute service context that contained two IBM Security Attribute Propagation authorization tokens. This is not supported. A context may only have one such token.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send duplicate authorization tokens.
The server received a CSIv2 establish security attribute service context that contained a type of authorization token that is not supported.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send authorization tokens that are not supported.
The server received a CSIv2 establish security attribute service context that contained an IBM Security Attribute Propagation authorization token. This server was not configured to support this tokens.
This is most likely a problem caused by the process that formed the request and context. This process should be investigated, to insure that it does not send this tokens when a server does not support them.
An attempt was made to clone a security object but the pointer to the object no longer points to the correct storage. The storage was probably freed.
This is an internal error. Please report this problem to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
The authentication information provided for the request could not be validated during login.
Ensure that the appropriate credentials have been presented to the server and retry the request.
There was a problem validating the LTPA token during login processing. It is likely that the token has expired. This exception may also be raised if the token could not be decrypted with the configured keys.
Ensure that the token has not expired and that the appropriate keys were used to encrypt and decrypt the token at the client and server. In most cases this error is transient as the client side service will generate a new token and retry the request. For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/.
A problem was encountered while attempting to login with an asserted ID. The most likely cause of this error is that the presented identity is not found in the active user registry or that the server does not trust the client side service to assert identities.
Ensure that the server is configured to trust the client service to assert identities and that the user ID that is being asserted can be found in the active user registry. For further information, please consult the product documentation.
Adapter code encountered an unexpected system failure.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an invalid input parameter.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The adapter is unable to narrow to the adapter resource manager.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code received an unknown unexpected interrupt.
For further assistance look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Adapter code using APPC failed to allocate the conversation
Check APPC configuration to make sure APPC is up and running and that APPC connectivity exists between the two LUs. If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC Allocate failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC send service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC send failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC receive service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC receive failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC confirmed service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC confirm failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code using APPC failed while invoking the APPC deallocate service.
If trace level 1 (exception tracing) was active for the Adapter component, search the trace for the string "Error issuing APPC service". This trace entry will contain APPC error message text that describes the reason for the APPC deallocate failure. Lookup the APPC message explanation in the MVS publication " Writing TPs for APPC/MVS" and perform the action indicated for the APPC error message. If no tracing was active, rerun the application with trace level 1 or higher for the Adapter component and then locate the APPC error message text in the trace as indicated above.
Adapter code failed while using one of the CICSEXCI services.
Check the CB error log for the string "CICSEXCI" for further diagnostic information.
Specified TPName (also known as transaction program name in IMS or as Function Program name in the J2EE Connector Architecture) exceeds maximum length.
Specify a shorter name. Consult IMS and APPC documentation for specific parameter requirements.
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
Servant Object could not be created for the invoke request. This is likely due to a class type conflict or a protection domain conflict.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
An object request was received with a method name that the target object does not support. The client's RMI/IIOP Stub is out of synch with the server's RMI/IIOP Tie.
Correct the application.
The CORBA Container container returned a null remote implementation when trying to execute a J2EE request.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
A bridge method that is only implemented in one of Control Region or Server Region was called in the space where it isn't implemented.
IBM Internal Only
getServiceContextList is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
getRequestId is not implemented in this implementation of ClientResponse
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
getForwardedIOR is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
peekUserExceptionId is not implemented in this implementation of ClientResponse.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The object given to the ORB had an incorrect delegate while trying to load a IDLJ stub.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An invalid ClientDelegate was used to drive a request.
IBM Internal Only.
The com.ibm.ws390.orb.WS390ServerDelegate class could not be found by Java.
Ensure that the WebSphere/390 EE runtime jar files are on the failing process's CLASSPATH.
The com.ibm.ws390.orb.WS390ExtendedServerDelegate class could not be found by Java.
Ensure that the WebSphere/390 EE runtime jar files are on the failing process's CLASSPATH.
Attempted to register an object as an INS NamingService that is not an org.omg.CosNaming.NamingContext or an org.omg.CosNaming.NamingContextExt .
Verify the object specified.
The URL supplied to ORBDefaultInitRef should be a corbaname or corbaloc URL.
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
The URL supplied to ORBDefaultInitRef should not contain a '/'.
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
Badly formed ORBInitRef parameter. ObjectURL was missing. Parameter should be of the form:
<ObjectID>
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
Badly formed ORBInitRef parameter. ObjectURL was missing. Parameter should be of the form:
<ObjectID>
Ensure the specified ORBDefaultInitRef parameter obeys the syntax specified by the OMG INS Specification.
A java.rmi.RemoteException is being returned as the result of a J2EE request. The actual RemoteException is imbedded within the Unknown Exception service context in the GIOP response. It is the embedded exception that will be received by the client.
This is not an error.
An unexpected error has occurred in a J2EE server during execution of a J2EE request.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
A request to an object that was colocated within the server could not be completed because the object no longer exists.
Look for a Java stack trace in the server's SYSOUT to determine the object that was requested. Check whether the application that owns the object was stopped or uninstalled.
Unexpected IO Exception when creating ClientResponse.
IBM Internal Only
Unexpected IO Exception when creating ClientResponse.
IBM Internal Only
The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request.
IBM Internal Only
The stream passed to the delegate as a parameter to invoke does not contain information required to process the request. This path is particular to IDLJ method invocations, which require the request to be pre-constructed to force codeset negotiation. The stream passed to invoke does not contain a reference to the negotiated codeset, or to the previously constructed request.
IBM Internal Only
An error occured while trying to create an IOR for an RMI/IIOP Stub. The remote mode Stub does not already hold a reference to the IOR that created it.
IBM Internal Only
A user exception was received by the client side non_existent() method, but there are no exceptions defined on that method.
IBM Internal Only
A user exception was received by the client side is_a() method, but there are no exceptions defined on that method.
IBM Internal Only
A user exception was received by the client side get_interface_def() method, but there are no exceptions defined on that method.
IBM Internal Only
An erroneous IIOP response type was received in the client.
IBM Internal Only
An HTTP request was received but the target Tie could not be found.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
A request to dispatch a callback object failed because the target callback object is not registered with the client ORB.
For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A request to dispatch a callback object was received with a method name that the target object does not support.
For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occured while trying to load an RMI/IIOP Tie.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An error occured while trying to load an RMI/IIOP Stub.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
A J2EE request was received with a method name that the target object does not support. The client's RMI/IIOP Stub is out of synch with the server's RMI/IIOP Tie.
Correct the application.
The get_interface() method has been deprecated and is not supported for J2EE components.
Correct the application.
The J2EE container returned a null remote implementation when trying to execute a J2EE request.
Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
The getTransportManager() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The process() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The locate() method was driven on the ws390 ORB. The ws390 ORB does not support this method.
IBM Internal Only
The ORB received an exception from the J2EE container while trying to load an IDLJ stub.
Correct the application.
The string_to_object method was passed a zero length string.
Correct the application.
The string_to_object method was passed a string that is not a stringified IOR.
Correct the application.
The string_to_object method was passed a NULL string.
Correct the application.
The resolve_initial_references() method was driven on a singleton Java ORB, which singleton ORBs do not implement.
None.
The ORB received an exception from the J2EE container while trying to load a local mode RMI/IIOP stub.
None.
The ORB received a NULL remote implementationn from the J2EE container while trying to load a local mode RMI/IIOP stub.
Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
An error occured while trying to load an RMI/IIOP Stub.
Look for a Java stack trace in the server's SYSOUT. For further assistance, look up problem determination information on the WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
See C9C2107B.
See C9C2107B.
See C9C2107C.
See C9C2107C.
See C9C21076.
See C9C21076.
See C9C21076.
See C9C21076.
An array could not be allocated in the JVM through the JNI.
An out of memory condition could exist. Try the operation again.
The JVM could not be found by the native method.
Look for error messages in the server output which may explain why the JVM did not start. For further assistance, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
An ORB service such as string_to_IOR received null or bad parameters.
report this error to your next level of support or look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
Null synchronizer pointer in register_sync.
No action possible , raise CORBA::BAD_PARAM exception.
Null TransactionService Context in extract_gitd.
No action possible, raise CORBA::BAD_PARAM exception.
Null synchronizer pointer in register_sync.
No action possible, raise CORBA::BAD_PARAM exception.
Unable to register resource due to invalid resource parameter.
Check for an application error.
Unable to register synchronization object due to invalid resource parameter.
Check for an application error.
Invalid coordinator reference passed on is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
Check for an application error.
Invalid propagation context accessed in is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
Check for an application error.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
Check to make sure you are running with enough memory for the address space issuing the failing code. Verify that for the controller/Servant the REGION=0M. Refer to the "WebSphere Application Server for z/OS and OS/390:Installation and Customization Guide" for additional WebSphere storage requirements. If that is not the problem, collect the following information and look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ : Run with exception tracing, i.e. TRACEALL=1 in the current.env file associated with the server. If TRACEBUFFLOC=SYSPRINT, send all the job output for that region to IBM as well as the contents of the error log. If TRACEBUFFLOC=BUFFER and you have the CTRACE writer operating, send the CTRACE data set, as well as the job output and error log to IBM.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
IBM Internal Only
For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.
The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
See minor code C9C2E001.