This chapter describes the WebSphere for z/OS error (minor) codes.
C9C20001 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20002 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20003 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20004 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20005 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20006 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20007 |
Explanation: WebSphere 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.
User Response: See previous messages for why the thread entered the signal handler.
C9C20008 |
Explanation: WebSphere for z/OS Series terminated the process due to catching a non-retryable signal. The process was terminated.
User Response: See previous messages for why the thread entered the signal handler.
C9C20009 |
Explanation: WebSphere for z/OS Series terminated the thread due to catching a non-retryable signal. The thread was terminated.
User Response: See previous messages for why the thread entered the signal handler.
C9C2000A |
Explanation: WebSphere for z/OS Series detected a bad assertion. A CORBA::INTERNAL exception is thrown.
User Response: Report the problem and accompanying information to your next level of support or the IBM Support Center.
C9C2000B |
Explanation: WebSphere for z/OS Series detected a bad parameter passed on open of a file.
User Response: Report the problem and accompanying information to your next level of support or the IBM Support Center.
C9C2000C |
Explanation: Failure during fseek of the header record (first record) of a log file. The header record is bad.
User Response: 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 the IBM Support Center.
C9C2000D |
Explanation: Failure during fgets of the header record (first record) of a log file. The header record is bad.
User Response: 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 the IBM Support Center.
C9C2000E |
Explanation: Failure during sscan of the header record (first record) of a log file. The header record is bad.
User Response: 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 the IBM Support Center.
C9C2000F |
Explanation: Failure during fseek of the header record (first record) of a log file. The header record is bad.
User Response: 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 the IBM Support Center.
C9C20010 |
Explanation: Failure during fputs of the header record (first record) of a log file. The header record is bad.
User Response: 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 the IBM Support Center.
C9C20011 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20012 |
Explanation: Failure during fflush/fputs of the header record (first record) of a log file. The header record is bad.
User Response: Report the problem and accompanying information to your next level of support or the IBM Support Center.
C9C20014 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20015 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20016 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20017 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20018 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20019 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2001A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2001B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2001C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2001D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2001F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20020 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20021 |
Explanation: Too many specific trace points were specified. None of the trace points are set.
User Response: Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
C9C20022 |
Explanation: 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.
User Response: Check the trace group definitions for a circular reference or reduce the number of layers of definitions.
C9C20023 |
Explanation: 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.
User Response: Add a closing parenthesis.
C9C20024 |
Explanation: 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.
User Response: Add a closing quote to the end of the group name and try the command again.
C9C20025 |
Explanation: 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.
User Response: Add a closing quote to the end of the group name and try the command again.
C9C20026 |
Explanation: 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.
User Response: Correct the syntax and try the command again
C9C20027 |
Explanation: 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.
User Response: Either remove the group from the command or use an environment variable that has a value.
C9C20028 |
Explanation: 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.
User Response: Either remove the group from the command or use an environment variable that has a value.
C9C20029 |
Explanation: 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.
User Response: Specify a valid value and try the command again.
C9C2002A |
Explanation: 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.
User Response: Specify a valid value and try the command again.
C9C2002B |
Explanation: 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.
User Response: Specify a valid value and try the command again.
C9C2002C |
Explanation: 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.
User Response: Specify a valid value and try the command again.
C9C2002D |
Explanation: 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.
User Response: Specify a valid value and try the command again.
C9C2002F |
Explanation: Too many exclude specific trace points were specified. The additional trace points are ignored.
User Response: Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
C9C20030 |
Explanation: Too many specific trace points with special processing were specified. The additional trace points are ignored.
User Response: Use the TraceNone modify command to turn off all tracing and start over with fewer trace points or use more generic tracing.
C9C20031 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20032 |
Explanation: Caller invoked ArmRegister() with a bad cell name.
User Response: Ensure that the daemon_group_name configuration variable is set
C9C20401 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20402 |
Explanation: CBSeries could not load the specified dll.
User Response: 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.
C9C20403 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20404 |
Explanation: CBSeries could not obtain a message skeleton due to a previous failure.
User Response: 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.
C9C20405 |
Explanation: MsgRetrieve function could not be obtained from the message DLL.
User Response: 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.
C9C20406 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20407 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20408 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20409 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2040A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2040B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2040C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2040D |
Explanation: Adapter code was invoked while in an invalid state.
User Response: Contact the IBM Support Center.
C9C2040E |
Explanation: Adapter code received an invalid input parameter.
User Response: Contact the IBM Support Center.
C9C2040F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20410 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C0A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C0D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C1C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C1D |
Explanation: 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.
User Response: "None"
C9C20C1E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C20 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C24 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C30 |
Explanation: 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.
User Response: 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.
C9C20C35 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C41 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C42 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C44 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C4E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C52 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C54 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C55 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C56 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C57 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C5D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C5E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C5F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C60 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C61 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C63 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C64 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C68 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C6C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C6D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C6F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C70 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C71 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C72 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C7C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C7D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C85 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C8E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C8F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20C99 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CAD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CAE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CAF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CB9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CBA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CBB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CBC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CC2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CD9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CDA |
Explanation: 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.
User Response: Retry starting the control region after the Daemon has finished coming down and is back up again.
C9C20CDF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CE9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CEA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CEB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CEC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CED |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CEE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CEF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CF9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20CFF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D00 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D01 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D02 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D03 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D04 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D05 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D06 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D07 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D08 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D09 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D0F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D10 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D11 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D12 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D13 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D14 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D15 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D16 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D17 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D18 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D19 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D1F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D20 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D21 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D22 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D23 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D24 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D25 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D26 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D27 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D28 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D29 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D2F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D30 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D31 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D34 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D35 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D36 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D37 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D38 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D39 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D3F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D40 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D41 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D42 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D43 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D44 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D45 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D46 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D47 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D48 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D49 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C20D4A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21001 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21002 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21003 |
Explanation: A client has remained up while the WebSphere 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.
User Response: Restart the client.
C9C21004 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21005 |
Explanation: A client has remained up while the WebSphere 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.
User Response: 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.
C9C21006 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21007 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21008 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21009 |
Explanation: The WebSphere 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.
User Response: 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 to the IBM Support Center.
C9C2100D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2100E |
Explanation: The WebSphere for z/OS control region execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
User Response: 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 to the IBM Support Center.
C9C2100F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21010 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21011 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21012 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21013 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21014 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21015 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21016 |
Explanation: CORBA::BOA::change_implementation was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::change_implementation.
C9C21017 |
Explanation: CORBA::BOA::obj_is_ready was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::obj_is_ready.
C9C21018 |
Explanation: CORBA::BOA::deactivate_obj was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::deactivate_obj.
C9C21019 |
Explanation: CORBA::BOA::_get_implementation was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_get_implementation.
C9C2101A |
Explanation: CORBA::BOA::_get_interface was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_get_interface.
C9C2101B |
Explanation: CORBA::BOA::_create_request was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_create_request.
C9C2101C |
Explanation: CORBA::BOA::_request was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_request.
C9C2101D |
Explanation: CORBA::BOA::_is_a was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_is_a.
C9C2101E |
Explanation: CORBA::BOA::_non_existent was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_non_existent.
C9C2101F |
Explanation: CORBA::BOA::_is_equivalent was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_is_equivalent.
C9C21020 |
Explanation: CORBA::BOA::_hash was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_hash.
C9C21021 |
Explanation: CORBA::BOA::_has_ancestor was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::_has_ancestor.
C9C21022 |
Explanation: Control region thread is terminating because a non-retryable signal was encountered.
User Response: Provide the control region dump and log to the IBM Support Center.
C9C21023 |
Explanation: Server region thread is terminating because a non-retryable signal was encountered.
User Response: Look at the server region dump and log to determine whether this is an application or WebSphere for z/OS problem. If termination occurred due to an application error, correct the problem. If it is a WebSphere for z/OS error, contact the IBM Support Center.
C9C21024 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21025 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21026 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21027 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21028 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21029 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2102A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2102B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2102C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2102E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2102F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21030 |
Explanation: Attempt to queue work to WLM failed.
User Response: 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.
C9C21031 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21032 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21033 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21034 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21035 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21036 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21037 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21039 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2103A |
Explanation: Attempt to queue work from the pending queue to WLM failed.
User Response: 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.
C9C2103B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2103C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2103D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2103E |
Explanation: The WebSphere 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.
User Response: 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 to the IBM Support Center.
C9C2103F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21040 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21042 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21044 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21045 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21047 |
Explanation: A locate request returned an unknown object.
User Response: There are several reasons why you might get this message:
C9C21048 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21049 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2104A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2104B |
Explanation: This exception is accompanied by message BBOO0053E with the name of the DLL.
User Response: 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
C9C2104C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2104D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2104E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2104F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21050 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21051 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21052 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21054 |
Explanation: Couldn't create a object for the object reference.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C21055 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21056 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21057 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21058 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21059 |
Explanation: Couldn't create a object for the object reference.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C2105D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21064 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21065 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21066 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21067 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21068 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2106B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2106C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21071 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21072 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21073 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21074 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21075 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21076 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21077 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21078 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21079 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2107A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2107B |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C2107C |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C21080 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21081 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21082 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21083 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21087 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21089 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2108F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21090 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21091 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21092 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21093 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21094 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21095 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21096 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21097 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21098 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21099 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2109A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2109B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2109C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2109D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2109E |
Explanation: Server region tried to register with the control region but the server is being stopped.
User Response: None, if the server was being stopped. Otherwise report this error to your next level of support or to the IBM Support Center.
C9C2109F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210A6 |
Explanation: The dispatch method returned an indication that the operation was not executed.
User Response: 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.
C9C210AA |
Explanation: Validation of the object key failed.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C210AB |
Explanation: Unable to get a list of initial services.
User Response: Check the error log for other messages. Report this problem to your next level of support or to the IBM Support Center.
C9C210AC |
Explanation: Couldn't create a proxy object for the object reference.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C210AD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210AE |
Explanation: Input object is not a CORBA::Object.
User Response: Verify that the object inherits from CORBA::Object.
C9C210AF |
Explanation: Something is not correct with the object key. Possibly a UUID of the server or control region is not consistent with the type of communication indicated in the object key.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C210B0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B2 |
Explanation: The build_IOR method failed to create an IOR.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C210B3 |
Explanation: get_SCO() was called and initialization was not done.
User Response: Insure that the BOA_init method was called prior to invoking the get_SCO method.
C9C210B4 |
Explanation: The object_to_IOR method failed to make an IOR.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C210B5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210B9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210BF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210C9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210CF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D1 |
Explanation: When marshalling an object reference into an encapsulation, the object reference was NULL.
User Response: Report this error to your next level of support or to the IBM Support Center.
C9C210D2 |
Explanation: When marshalling an IOR into an encapsulation buffer, a little endian byte order was detected. S/390 should be big endian byte order.
User Response: Report this error to your next level of support or to the IBM Support Center.
C9C210D3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210D9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210DF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210E9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210EA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210EB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210ED |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210EF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210F9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210FA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210FB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210FC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C210FD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21100 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21101 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21102 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21103 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21104 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21105 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21106 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21107 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21108 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21109 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2110F |
Explanation: 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.
User Response: 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 in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout).
C9C21110 |
Explanation: 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.
User Response: 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 in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout).
C9C21111 |
Explanation: An ORB_Request was Queued to WLM and received by a server region. 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.
User Response: Check that the ORB dispatch time out value is of sufficient length. See the instructions in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting the ORB dispatch time out default via an environment variable (control_region_wlm_dispatch_timeout).
C9C21112 |
Explanation: 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.
User Response: Ensure that the transaction time out value is of sufficient length. See the instructions in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout).
C9C21113 |
Explanation: 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.
User Response: Ensure that the transaction time out value is of sufficient length. See the instructions in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout).
C9C21114 |
Explanation: 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.
User Response: Ensure that the transaction time out value is of sufficient length. See the instructions in the OS/390 WebSphere for z/OS Planning and Installation Guide for setting transaction time out defaults via environment variables (transaction_defaultTimeout and transaction_maximumTimeout).
C9C21115 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21116 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21117 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21118 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21119 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21120 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21121 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21122 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21123 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21124 |
Explanation: An unknown error occurred while processing a request in the server region. This error code is returned to the client to indicate that processing of the request has failed.
User Response: Check the WebSphere for z/OS Series error log for information that will indicate what errors were encountered in the failing server region.
C9C21125 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21126 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21127 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21128 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21129 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2112A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2112C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2112D |
Explanation: CORBA::BOA::get_principal was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::get_principal
C9C2112E |
Explanation: A DII method was used on a CORBA::Request object that has not been created for use with DII.
User Response: Do not use this method or change the way the CORBA::Request object is created.
C9C2112F |
Explanation: One of the DSI methods params(), ctx(), result() or exception of class ServerRequest has been called out of order.
User Response: Call the methods in the right order as specified in CORBA 2.0 and never call the same method twice.
C9C21130 |
Explanation: CORBA::CBSeriesGlobal::hostName was invoked but is not supported.
User Response: Do not invoke CORBA::CBSeriesGlobal::hostName.
C9C21131 |
Explanation: Unable to dispatch method due to MO bindings generated as localonly objects.
User Response: Regenerate MO bindings as remotable objects.
C9C21132 |
Explanation: CORBA::BOA::create was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::create
C9C21133 |
Explanation: CORBA::BOA::dispose was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::dispose
C9C21134 |
Explanation: CORBA::BOA::get_id was invoked but is not supported.
User Response: Do not invoke CORBA::BOA::get_id
C9C21135 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21136 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21137 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21138 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21139 |
Explanation: CORBA::Object_ORBProxy::_get_implementation was invoked from client which is not supported.
User Response: Do not invoke CORBA::Object_ORBProxy::_get_implementation from a client.
C9C2113A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2113B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2113C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2113D |
Explanation: ORB::resolve_initial_references could not complete because it was unable to determine from where to get the initial references.
User Response: 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 for z/OS Systems Management server is running) or else a WebSphere for z/OS Daemon and Systems Management server must be running on the same system where the resolve_initial_references was issued
C9C2113E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2113F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21140 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21141 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21142 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21143 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21145 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21146 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21147 |
Explanation: CORBA::Object_ORBProxy::_decref() was invoked to decrement the reference count of the object but the reference count was 0.
User Response: Check application to make sure that CORBA::release is not being issued too many times. If it is an internal object, report this error to the IBM Support Center.
C9C21148 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21149 |
Explanation: COMM failed when trying to drive a locate request to the daemon.
User Response: Check the error log for a COMM failure error message.
C9C2114A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2114B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2114C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2114D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2114E |
Explanation: The Naming IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
User Response: 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.
C9C2114F |
Explanation: The IR IOR has not been stored in the Systems Management Sysplex object, so it cannot be stored in the BGVT.
User Response: 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.
C9C21150 |
Explanation: The Systems Management SMO IOR has not been stored in the Systems Management server object, so it cannot be stored in the BGVT.
User Response: 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.
C9C21151 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21152 |
Explanation: An attempt to start TCP/IP listening has failed.
User Response: Check the error log for more information that will indicate what errors were encountered.
C9C21153 |
Explanation: BBOOSCO:readMasterRecord was called but the Master Record is not present. The Systems Management bootstrap is not being driven.
User Response: Restart the daemon with the -ORBCBI parameter so that the Systems Management bootstrap will be driven.
C9C21154 |
Explanation: BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere for z/OS Systems Management Master Record.
User Response: Check the WebSphere 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 for z/OS.
C9C21155 |
Explanation: BBOOSCO:initialize_SCOI_Server encountered an error while attempting to read server configuation information from DB2 tables.
User Response: Check the WebSphere 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 for z/OS.
C9C21156 |
Explanation: BBOOSCO:initialize_SCOI_Server did not find the server defined in the Systems Management Tables.
User Response: 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.
C9C21157 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21158 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21159 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2115F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21160 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21161 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21162 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21163 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21164 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21165 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21166 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21167 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21168 |
Explanation: The index of the request sequence is equal or bigger than the length of the sequence.
User Response: Use only access to valid sequence elements.
C9C21169 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2116A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2116B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2116C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2116D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2116E |
Explanation: BBOOSCO:getSCO did not find the server defined in the Systems Management tables for this sysplex at the currently active level.
User Response: 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.
C9C2116F |
Explanation: BBOOSCO:getSCO could not obtain this server's configuration data from the Systems Management Control Region.
User Response: 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 control region 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 control region. 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 the IBM Support Center.
C9C21170 |
Explanation: 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.
User Response: 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 the IBM Support Center.
C9C21171 |
Explanation: CORBA::ImplRepository::find_impldef_by_alias was invoked by client.
User Response: Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef_by_alias
C9C21172 |
Explanation: CORBA::ImplRepository::find_impldef was invoked by client.
User Response: Change the client program so that it does not invoke CORBA::ImplRepository::find_impldef
C9C21173 |
Explanation: CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying to narrow to a CORBA::ImplementationDef object.
User Response: Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
C9C21174 |
Explanation: CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trying create an object.
User Response: Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
C9C21175 |
Explanation: CORBA::ImplRepository::find_impldef_by_alias was invoked but an error ocurred trynig to build a IOR.
User Response: Ensure that the server for the input alias is started. When exception tracing is on, the input alias is traced.
C9C21176 |
Explanation: CORBA::ImplRepository::find_impldef was invoked but an error ocurred trynig find the implementationDef for the input implid.
User Response: Ensure that the server for the input implid is started. When exception tracing is on, the input implid is traced.
C9C2117B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2117E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21180 |
Explanation: While a WebSphere for z/OS Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no WebSphere for z/OS Series servers can exist without a Daemon present on the system, this server must end.
User Response: Determine why the Daemon failed and restart the daemon and other servers as necessary.
C9C21181 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21182 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21183 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21184 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21186 |
Explanation: An attempt was made to start a WebSphere for z/OS Series Control Region while another Control Region with the same specific server name was active. Only one WebSphere for z/OS Series Control Region with a given specific server name can be active at one time. This Control Region terminates in error.
User Response: Do not attempt to start two WebSphere for z/OS Control Regions with the same specific server name.
C9C2118C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2118D |
Explanation: Before a server region can start, the control region which it is associated with must be initialized. This server region was unable to find its owning control region and thus terminates.
User Response: Ensure this server region's owning control region is active before starting the server region.
C9C2118E |
Explanation: An attempt was made to start a WebSphere for z/OS Series Control Region while another Control Region with the same specific server name was active. Only one WebSphere for z/OS Series Control Region with a given specific server name can be active at one time. This Control Region terminates in error.
User Response: Do not attempt to start two WebSphere for z/OS Control Regions with the same specific server name.
C9C21190 |
Explanation: Timeout occurred waiting for the naming server to start. We are unable to continue without it, so an exception is thrown.
User Response: Determine why the naming server failed to start before the timeout occurred, correct the problem, and try again.
C9C21191 |
Explanation: Timeout occurred waiting for the IR server to start. We are unable to continue without it, so an exception is thrown.
User Response: Determine why the IR server failed to start before the timeout occurred, correct the problem, and try again.
C9C21192 |
Explanation: Timeout occurred waiting for the Systems Management Server to start. We are unable to continue without it, so an exception is thrown.
User Response: Determine why the SM server failed to start before the timeout occurred, correct the problem, and try again.
C9C21193 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21194 |
Explanation: 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.
User Response: Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
C9C21195 |
Explanation: 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.
User Response: Determine the origin of the unrecognized System Exception. Use this information to determine the reason for the failure.
C9C21196 |
Explanation: The WebSphere for z/OS server region execution thread caught a ... This is an incorrect throw. A system exception with this error code is created and returned.
User Response: 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 to the IBM Support Center.
C9C21197 |
Explanation: The DAEMON_IPNAME environment variable is set to an IP address. It must be set to an IP name, host n name.
User Response: Correct the DAEMON_IPNAME environment variable and run the Systems Management Bootstrap again.
C9C21198 |
Explanation: Cannot open converter
User Response: Code set may not be compatible
C9C21199 |
Explanation: Cannot open converter
User Response: Code set may not be compatible
C9C2119A |
Explanation: Conversion Error
User Response: Code set may not be compatible
C9C2119B |
Explanation: Conversion Error
User Response: Code set may not be compatible
C9C2119C |
Explanation: Incorrect data length
User Response: Make sure the input data length is correct
C9C2119D |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C2119E |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C2119F |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C211A0 |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C211A1 |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C211A2 |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C211A3 |
Explanation: The input codeset is not found in registry
User Response: check if codeset is supported
C9C211A4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211A5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211A6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211A7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211A8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211A9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211AF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211B9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211BF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C7 |
Explanation: COMM failed when trying to drive a locate request to the daemon.
User Response: Check the error log for a COMM failure error message.
C9C211C8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211C9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211CA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211CB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211CC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211CE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211CF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211D0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211D1 |
Explanation: Cannot open converter
User Response: Code set may not be compatible
C9C211D2 |
Explanation: Cannot open converter
User Response: Code set may not be compatible
C9C211D3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211D4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211D5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211D6 |
Explanation: Couldn't create a proxy object in rebuild_proxy.
User Response: Report this problem to your next level of support or to the IBM Support Center.
C9C211D7 |
Explanation: BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere for z/OS Systems Management Master Record.
User Response: Check the WebSphere 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 for z/OS.
C9C211D8 |
Explanation: CORBA::Context::delete_values was invoked but the input property name was not found in the context object.
User Response: If encountered by application code, check for application error. If encountered by system code, report this error to your next level of support or to the IBM Support Center.
C9C211D9 |
Explanation: Processing in a control region was halted because it was detected that the WebSphere for z/OS Daemon was not active.
User Response: The WebSphere for z/OS Daemon is required for WebSphere for z/OS servers to be active. All WebSphere 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.
C9C211DA |
Explanation: Processing in a control region was halted because it was detected that the WebSphere for z/OS Daemon was not active.
User Response: The WebSphere for z/OS Daemon is required for WebSphere for z/OS servers to be active. All WebSphere 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.
C9C211DB |
Explanation: resolve_initial_references was called before doing ORB_init and BOA_init.
User Response: 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.
C9C211DC |
Explanation: resolve_initial_references_remote was called before doing ORB_init and BOA_init.
User Response: 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.
C9C211DD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211DE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211DF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211E0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211E1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211E2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211E3 |
Explanation: In encode_objref, pfactory is NULL after lookup of pfactory in ptable.
User Response: 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.
C9C211E4 |
Explanation: 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.
User Response: Don't marshal a local_only object while a request is in progress.
C9C211E5 |
Explanation: BBOOSCO:readMasterRecord encountered an error while attempting to update the WebSphere for z/OS Systems Management Master Record.
User Response: Check the WebSphere 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.
C9C211E6 |
Explanation: BBOOSCO:readMasterRecord encountered an error while attempting to read the WebSphere for z/OS Systems Management Master Record.
User Response: Check the WebSphere 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.
C9C211E7 |
Explanation: ORBid keyword to ORB_init must specify a value of BOSS
User Response: Provide a value of BOSS as the value of the ORBid keyword.
C9C211E8 |
Explanation: ORBid keyword must be specified on ORB_init with a value
User Response: Specify ORBid BOSS.
C9C211E9 |
Explanation: ORBsrvname keyword to ORB_init must have a value
User Response: Specify ORBsrvname with a valid server name
C9C211EA |
Explanation: The ORBType keyword to ORB_init must have a valid value
User Response: Specify ORBType with a valid value.
C9C211EB |
Explanation: Initialization of a WebSphere 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.
User Response: Determine which module could not be found and why and correct the problem and restart the server.
C9C211EC |
Explanation: RRS is required for WebSphere for z/OS Series to function. During initialization of a WebSphere for z/OS Server, RRS could not be found. The server terminates.
User Response: Make sure RRS is up and initialized.
C9C211ED |
Explanation: The value specified for the ORBCBI keyword to ORB_init was not one of COLD, WARM, or HOT.
User Response: Specify a valid value.
C9C211EE |
Explanation: The ORBCBI keyword to ORB_init requires a valid value
User Response: Specify COLD, WARM, or HOT as a value. Example: START BBODMN,BOOT='-ORBCBI COLD' (where BBODMN is the Daemon proc name).
C9C211F0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211F9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C211FF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21200 |
Explanation: This exception is accompanied by message BBOO0053E with the name of the DLL.
User Response: 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
C9C21201 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21202 |
Explanation: CBSeriesGlobal::hostName was called from a WebSphere 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.
User Response: If the Daemon was terminating or down at the time this error occurred, then no action is necessary as it is expected.
C9C21203 |
Explanation: Systems management server created requested data space for SMF data gathering but the ALESERV failed. No data gathering will be done.
User Response: Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or the IBM Support Center.
C9C21204 |
Explanation: Systems management server tried to create requested dataspace but the DSPSERV failed. No data gathering will be done.
User Response: 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 the IBM Support Center.
C9C21205 |
Explanation: 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.
User Response: Locate message BBOO0038E in the error log to get the ALESERV return code. If the problem persists, contact your next level of support or the IBM Support Center.
C9C21206 |
Explanation: The MVS STOP console command or the System Managment EUI STOP command has already been issued for this server. Subsequent commands are ignored.
User Response: Wait for the current stop processing to complete or escalate to an EUI Cancel or MVS console Modify Cancel command.
C9C21207 |
Explanation: The MVS Modify Cancel console command or the System Managment EUI CANCEL command has already been issued for this server. Subsequent commands are ignored.
User Response: Wait for the current cancel processing to complete
C9C21208 |
Explanation: No server name was specified for the Control Region
User Response: Examine the Control Region procedure or the parameters which were used to start the Control Region and correct to specify the appropriate server name.
C9C21209 |
Explanation: A user exception was caught by the main Control Region routine
User Response: Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
C9C2120A |
Explanation: No server name was specified for the Server Region
User Response: Examine the Server Region procedure or the parameters which were used to start the Server Region and correct to specify the appropriate server name.
C9C2120B |
Explanation: A user exception was caught by the main Server Region routine
User Response: Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
C9C2120C |
Explanation: The server region is terminating due to an internal error.
User Response: Check the WebSphere for z/OS error log for information about errors preceeding this one which could have caused the server region to terminate.
C9C2120D |
Explanation: CBSeries Daemon and Control Regions must run authorized. However, the space has detected that it is not. The space ends in error.
User Response: 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
C9C2120E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2120F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21210 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21211 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21212 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21213 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21214 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21215 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21216 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21217 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21218 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21219 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2121F |
Explanation: BBOOSCO:readSysplex was called but the Sysplex does not exist in the Systems Management database. The Systems Management bootstrap has not been run.
User Response: Restart the daemon with the -ORBCBI parameter to run the Systems Management bootstrap.
C9C21220 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21221 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21222 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21223 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21224 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21225 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21226 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21227 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21228 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21229 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2122F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21230 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21231 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21232 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21233 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21234 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21235 |
Explanation: The server instance is terminating due to a MODIFY server-instance,CANCEL
User Response: Restart the server instance when the reason that required you to cancel it has been resolved.
C9C21236 |
Explanation: The server instance is terminating due to a MODIFY server-instance,CANCEL,ARMRESTART
User Response: None.
C9C21237 |
Explanation: An outbound request could not be sent because length of message exceeded maximum.
User Response: Try sending a smaller message.
C9C21238 |
Explanation: A send oneway or send deferred request could not be sent because length of message exceeded maximum.
User Response: Try sending a smaller message.
C9C21239 |
Explanation: An outbound request (callback) could not be sent because length of message exceeded maximum.
User Response: Try sending a smaller message.
C9C2123A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2123B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2123C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2123E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2123F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21240 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21241 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21242 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21243 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21244 |
Explanation: IBM Internal Only
User Response: For support, look up problem determination information on WebSphere Application Server eSupport page at: http://www.ibm.com/software/webservers/appserv/zos_os390/support/
C9C21245 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21246 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21247 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21248 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21249 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2124A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2124B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2124C |
Explanation: WebSphere for z/OS Series terminated the thread due to error when attempting to pause for more work.
User Response: See previous messages for why the thread was unable to pause for more work.
C9C2124D |
Explanation: WebSphere for z/OS Series terminated the SSL Handshake thread due to error when attempting to pause for more work.
User Response: See previous messages for why the thread was unable to pause for more work.
C9C2124E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2124F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21250 |
Explanation: A failure occurred in attempting to get received credentials.
User Response:
C9C21251 |
Explanation: An outbound request could not be sent due to lack of available buffer space.
User Response: Try re-sending, or sending a smaller message.
C9C21252 |
Explanation: A send oneway or send deferred request could not be sent due to lack of available buffer space.
User Response: Try re-sending, or sending a smaller message.
C9C21253 |
Explanation: An outbound request (callback) could not be sent due to lack of available buffer space.
User Response: Try re-sending, or sending a smaller message.
C9C21254 |
Explanation: An outbound response could not be sent by the SR because its size exceeded the maximum allowed for local IIOP messages.
User Response: Try sending a smaller response.
C9C21255 |
Explanation: The server could not send the response to client because its size exceeded the maximum allowed for local IIOP messages.
User Response: Try sending a smaller message.
C9C21256 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21257 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21258 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21259 |
Explanation: Attempt to queue HTTP request to WLM failed.
User Response: 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.
C9C2125A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2125B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2125C |
Explanation: The WebSphere 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.
User Response: 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 to the IBM Support Center.
C9C2125D |
Explanation: The WebSphere for z/OS control region execution thread caught an exception of an unknown type. This is an incorrect throw. A system exception with this error code is created.
User Response: 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 to the IBM Support Center.
C9C2125E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2125F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21260 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21261 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21262 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21263 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21264 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21265 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21266 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21267 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21268 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21269 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2126A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2126B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2126C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2126D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2126E |
Explanation: The destroyJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C2126F |
Explanation: The detachThreadFromJVM external function was not found in the BBOLRT dll.
User Response: 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.
C9C21270 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C21272 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C21273 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C21274 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21275 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21276 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21277 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21278 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21279 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2127A |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C2127B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2127C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2127D |
Explanation: BoaSnoozeAlarm::TimedEventExit() failed (rc=-1) startDeferredListeners. Look for a communication error to aid in determining the cause of the failure.
User Response: Check the WebSphere for z/OS Series error log and Job log of the Controller for information that may indicate what errors were encountered during the initialization of a communication protocol.
C9C2127E |
Explanation: 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.
User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center.
C9C2127F |
Explanation: 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.
User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center.
C9C21280 |
Explanation: 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.
User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center.
C9C21281 |
Explanation: 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.
User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center.
C9C21282 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21283 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21284 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21285 |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or 4792C protocol_https_timeout_output). 4792C
C9C21286 |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or 4792C protocol_https_timeout_output). 4792C
C9C21287 |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting HTTP OUTPUT time out value via an environment variable (protocol_http_timeout_output or 4792C protocol_https_timeout_output). 4792C
C9C21289 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2128A |
Explanation: Control region'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.
User Response: 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.
C9C2128B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2128C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2128D |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C2128E |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C2128F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21290 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21291 |
Explanation: In order for the WebSphere for z/OS server region 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.
User Response: Set the DAEMON GROUP NAME environment variable.
C9C21292 |
Explanation: In order for the WebSphere for z/OS server to start, the daemon needs to be active.
User Response: Ensure daemon is active before starting the server.
C9C21293 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C21294 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C21295 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21296 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21297 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21298 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21299 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2129A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2129B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2129C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2129D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2129E |
Explanation: Initialization of a WebSphere 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.
User Response: 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.
C9C2129F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212A0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212A1 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C212A2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212A3 |
Explanation: The attempt to create a dataspace via DSPSERV failed. No SMF data gathering will be done.
User Response: 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 the IBM Support Center.
C9C212A5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212A6 |
Explanation: An unknown user exception was thrown while processing a synchronous ACRW in the control region.
User Response: Examine the control region logs for the cause of the initial user exception.
C9C212A7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212A8 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C212A9 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C212AA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212AB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212AC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212AD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212AE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212AF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B0 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C212B1 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C212B2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B3 |
Explanation: Attempt to create a WLM enclave for an inbound MDB Request failed.
User Response: 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).
C9C212B4 |
Explanation: Attempt to queue an MDB Request to WLM failed.
User Response: 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.
C9C212B5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212B9 |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout)
C9C212BA |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout)
C9C212BB |
Explanation: 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.
User Response: 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 in the WebSphere for z/OS Planning and Installation Guide for setting the MDB Request time out value via an environment variable (control_region_mdb_request_timeout)
C9C212BC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212BD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212BE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212BF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212C0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212C1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212C2 |
Explanation: ORB_Request::mergeMessageReplyBody detected that the servant was not able to obtain a cell in the comm dataspace to hold the large HTTP response.
User Response: Retry the request.
C9C212C3 |
Explanation: The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL
User Response: Restart the Daemon instance when the reason that required you to cancel it has been resolved.
C9C212C4 |
Explanation: The Daemon instance is terminating due to a MODIFY Daemon-instance,CANCEL,ARMRESTART
User Response: none
C9C212F7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212F8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212F9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212FA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C212FB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21411 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21412 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C216A4 |
Explanation: No class implementation exists for the method
User Response: 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.
C9C21800 |
Explanation: WebSphere read an interest back from the RRS recovery logs that was an unknown or invalid type. WebSphere cannot process this interest.
User Response: 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.
C9C21801 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21802 |
Explanation: Failed to get terminator pointer from control.
User Response: Rewrite application logic.
C9C21803 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21804 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21805 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21806 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21807 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21808 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21809 |
Explanation: Tried to decrement thread association count below zero in decrement_association.
User Response: Transaction rolled back. Follow these procedures before calling IBM:
C9C2180A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2180B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2180C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2180D |
Explanation: register_resource detected transaction is marked rollback.
User Response: See C9C21809.
C9C2180E |
Explanation: register_synchronization detected transaction is marked rollback.
User Response: See C9C21809.
C9C2180F |
Explanation: register_synchronization with superior coordinator raised unknown exception.
User Response: No action possible. Raise CORBA::UNKNOWN exception.
C9C21810 |
Explanation: Resource registration with superior failed in genericCreate.
User Response: See C9C2181F
C9C21811 |
Explanation: Null PropagationContext in extract_gitd.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the the IBM Support Center.
C9C21812 |
Explanation: Tid length is zero, or less than or equal to bqual length.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the the IBM Support Center.
C9C21813 |
Explanation: gtrid length exceeds MAX_GTRID length in extract_gtid.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the the IBM Support Center.
C9C21814 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21815 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21816 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21817 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21818 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21819 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2181A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2181B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2181C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2181E |
Explanation: Transaction rolled back during root prepare.
User Response: See C9C21809.
C9C2181F |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21820 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21821 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21822 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21823 |
Explanation: Detected that transaction is pending rollback.
User Response: See C9C21809.
C9C21824 |
Explanation: Detected that transaction is pending rollback.
User Response: See C9C21809.
C9C21825 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21826 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21827 |
Explanation: 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.
User Response: 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.
C9C21828 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21829 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2182A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2182B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2182C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2182D |
Explanation: There was not enough storage preallocated to accomodate OTS structures.
User Response: Set TRACEDETAIL=(3,4,6) in your environment dataset (BBOENV).
C9C2182E |
Explanation: Transaction Service does not support inbound transactional one-way requests.
User Response: Do not issue transactional one-way request.
C9C2182F |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21830 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21831 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21832 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21833 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21834 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21835 |
Explanation: Control Region is shutting down. Transaction creation is not possible.
User Response: Contact the IBM Support Center.
C9C21836 |
Explanation: Control Region is shutting down. Transaction creation is not possible.
User Response: Contact the IBM Support Center.
C9C21837 |
Explanation: Control Region is shutting down. Creation is not possible.
User Response: Contact the IBM Support Center.
C9C21838 |
Explanation: Control Region is shutting down. Creation is not possible.
User Response: Contact the IBM Support Center.
C9C21839 |
Explanation: Control Region is shutting down. Creation is not possible.
User Response: Contact the IBM Support Center.
C9C2183A |
Explanation: Control Region is shutting down. Creation is not possible.
User Response: Contact the IBM Support Center.
C9C2183C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2183D |
Explanation: Resource commit came in on restart resource but resolver owns syncpoint.
User Response: 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.
C9C2183E |
Explanation: Resource rollback came in on restart resource but resolver owns syncpoint.
User Response: 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.
C9C2183F |
Explanation: Detected that transaction is pending rollback.
User Response: See C9C21809.
C9C21840 |
Explanation: Rollback request was rejected because requested was not the initiator of the transaction. Obsolete.
User Response: Check for a possible application coding error.
C9C21841 |
Explanation: Commit request was rejected because requested was not the initiator of the transaction. Obsolete.
User Response: Check for a possible application coding error.
C9C21842 |
Explanation: Unable to register resource due to underlying recovery service logging limit.
User Response: Rewrite application to include fewer resources.
C9C21843 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21844 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21845 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21846 |
Explanation: Unable to register local resource object due to implementation restriction.
User Response: Check for an application error. Refer to application documentation for restrictions on local resource.
C9C21847 |
Explanation: Unable to register local synchronization object due to implementation restriction.
User Response: Check for an application error. Refer to application documentation for restrictions on synchronization onjects.
C9C21848 |
Explanation: Encountered a user exception while trying to mark transaction on thread as rollback_only.
User Response: Check for an application error.
C9C21849 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2184F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21850 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21851 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21852 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21853 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21854 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21855 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21856 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21857 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21858 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21859 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2185F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21860 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21861 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21862 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21863 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21864 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21865 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21866 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21867 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21868 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21869 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2186A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2186B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2186C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2186D |
Explanation: Transaction rolled back during delegate prepare.
User Response: See C9C21809.
C9C2186E |
Explanation: Inbound transaction is a nested transaction. WebSphere for z/OS does not support nested transactions.
User Response: Contact the IBM Support Center.
C9C2186F |
Explanation: Resource one_phase_commit came in on a resource but a syncpoint was already in progress.
User Response: If the transaction was rolled back, see C9C21809.
C9C21870 |
Explanation: Transaction rolled back with a heuristic mixed condition during delegate prepare.
User Response: 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.
C9C21871 |
Explanation: Invalid or NULL CosTransactions::Coordinator object extracted from an inbound. CosTransactions::PropagationContext structure.
User Response: Verify that sending ORB interoperates with WebSphere for z/OS.
C9C21872 |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C21873 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21874 |
Explanation: Server region sending reply checks detected a mismatch between the original transaction associated with the method and the one currently associated with the thread.
User Response: Check the application for a logic error.
C9C21875 |
Explanation: Transaction service is unable to locate transaction factory.
User Response: Contact the IBM Support Center.
C9C21876 |
Explanation: Transaction service is unable to locate transaction factory.
User Response: Check systems management configuration for a definition of transaction factories.
C9C21877 |
Explanation: Transactional request rejected because transaction is no longer active.
User Response: Check the application for a logic error.
C9C21878 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21879 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2187A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2187B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2187C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2187D |
Explanation: 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.
User Response: Check the application for a logic error.
C9C2187E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2187F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21880 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21881 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21882 |
Explanation: Transaction server detected invalid state for rollback_only request.
User Response: WebSphere for z/OS internal processing. No error has occurred.
C9C21883 |
Explanation: Transaction server detected transaction service containing deferred begin request.
User Response: WebSphere for z/OS internal processing. No error has occurred.
C9C21884 |
Explanation: Non-existent transaction detected for rollback_only request.
User Response: Check the application for a logic error.
C9C21885 |
Explanation: Invalid CosTransaction::PropagationContext returned from a 'deferred begin' outbound request.
User Response: Check the documentation on interoperability between ORBs.
C9C21886 |
Explanation: 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.
User Response: 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.
C9C21887 |
Explanation: atrdint issued against rolled back transaction.
User Response: 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.
C9C21888 |
Explanation: atrspid issued against rolled back transaction.
User Response: 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.
C9C21889 |
Explanation: atreint issued but UR log data limit exceeded.
User Response: 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.
C9C2188A |
Explanation: atreint issued against rolled back transaction.
User Response: 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.
C9C2188B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2188C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2188D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2188E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2188F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21890 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21891 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21892 |
Explanation: A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere for z/OS syncpoint coordinator.)
User Response: Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
C9C21893 |
Explanation: A transaction was rolled back because the containing transaction exceeded the specified timeout value. (This timeout was detected by the WebSphere for z/OS syncpoint coordinator.) The detection of failure was prior to a system exception being raised for this transaction.
User Response: Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
C9C21894 |
Explanation: An inbound request to a control region was detected to be contained within a transaction that had previously timed out.
User Response: Scan the traces previous to this one that would indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
C9C21895 |
Explanation: Commit request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
User Response: Check for a possible application coding error.
C9C21896 |
Explanation: Rollback request was rejected because the request was not made by the initiator of the transaction. Transaction has been marked rollback only.
User Response: Check for a possible application coding error.
C9C21897 |
Explanation: 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 for z/OS code was used, and this is not supported.
User Response: 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 for z/OS code. If so, and you have knowingly regressed the level of WebSphere for z/OS code, you must follow the WebSphere for z/OS cold start procedures to undo any changes that were made to the WebSphere 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 for z/OS code, then contact the IBM Support Center.
C9C21898 |
Explanation: 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 for z/OS code was used, and this is not supported.
User Response: 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 for z/OS code. If so, and you have knowingly regressed the level of WebSphere for z/OS code, you must follow the WebSphere for z/OS cold start procedures to undo any changes that were made to the WebSphere 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 for z/OS code, then contact the IBM Support Center.
C9C21899 |
Explanation: 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 for z/OS code was used, and this is not supported.
User Response: 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 for z/OS code. If so, and you have knowingly regressed the level of WebSphere for z/OS code, you must follow the WebSphere for z/OS cold start procedures to undo any changes that were made to the WebSphere 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 for z/OS code, then contact the IBM Support Center.
C9C2189A |
Explanation: 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 for z/OS code was used, and this is not supported.
User Response: 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 for z/OS code. If so, and you have knowingly regressed the level of WebSphere for z/OS code, you must follow the WebSphere for z/OS cold start procedures to undo any changes that were made to the WebSphere 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 for z/OS code, then contact the IBM Support Center.
C9C2189B |
Explanation: 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.
User Response: Scan the traces subsequent to this one that indicate when the rollback initially occurred and see C9C21809 for the rollback procedures.
C9C2189C |
Explanation: Transaction rolled back due to an unexpected return code from agent prepare.
User Response: Scan the traces subsequent to this one. TBD
C9C2189D |
Explanation: Transaction rolled back because a protected resource is not in the proper state for a commit.
User Response: TBD
C9C2189E |
Explanation: The control region was brought down after a CANCEL reply to MSGINDEX_BBOUENUS_OTS_HARDENED_DATA_LOSS.
User Response: None
C9C2189F |
Explanation: Unknown transaction policy specified for continer.
User Response: Check the transaction policy specified for this container in the SM EUI.
C9C218A0 |
Explanation: Transaction that was started during a method dispatch was not completed before returning. The transaction was marked for rollback.
User Response: Check the application logic for a possible coding error.
C9C218A1 |
Explanation: 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.
User Response: Check the application logic for a possible coding error.
C9C218A2 |
Explanation: Container initiated transaction caught unknown exception from commit.
User Response: None.
C9C218A3 |
Explanation: Container caught exception while attempting to resume the transaction that was present on entry.
User Response: None.
C9C218A4 |
Explanation: 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.
User Response: Contact the IBM Support Center.
C9C218A5 |
Explanation: 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.
User Response: Restart RRS and/or the application server that failed.
C9C218A6 |
Explanation: 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.
User Response: 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.
C9C218A7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218A8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218A9 |
Explanation: 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.
User Response: Check for an application logic error.
C9C218AA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218AB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218AC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218AD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218AE |
Explanation: Resume not allowed because the application has uncommitted local resources.
User Response: Local resources must be committed or rolled back before resuming another transaction. Check for an application coding error.
C9C218AF |
Explanation: An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
User Response: Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
C9C218B0 |
Explanation: A Heuristic Mixed exception was raised while attempting to commit container initiated transaction.
User Response: Check the traces and messages prior to this to determine what protected resource caused the heuristic outcome.
C9C218B1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218B9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218BA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218BB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218BC |
Explanation: Tid length is zero, or less than or equal to bqual length.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the IBM Support Center.
C9C218BD |
Explanation: gtrid length exceeds MAX_GTRID length in extract_gtid.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the IBM Support Center.
C9C218BE |
Explanation: Tid length is zero, or less than or equal to bqual length.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the IBM Support Center.
C9C218BF |
Explanation: gtrid length exceeds MAX_GTRID length in extract_gtid.
User Response: Check the workstation logs to see if there are any previous corresponding exceptions. Report this information to the IBM Support Center.
C9C218C0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C5 |
Explanation: Transaction rolled back during root commit.
User Response: See :spotref refid=rollbac..
C9C218C6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218C8 |
Explanation: An inbound transaction context did not contain a reference to the coordinator object for the global transaction.
User Response: Contact the IBM Support Center.
C9C218C9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218CA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218CB |
Explanation: RRS is unavailable on this system.
User Response: Ensure RRS has been started on this system.
C9C218CC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218CD |
Explanation: RRS is unavailable on this system.
User Response: Ensure RRS has been started on this system.
C9C218CE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218CF |
Explanation: 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.
User Response: Correct the client application or redploy the component in error.
C9C218D0 |
Explanation: 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.
User Response: Correct the client application or redploy the component in error.
C9C218D1 |
Explanation: Transaction rolled back during root commit.
User Response: See :spotref refid=rollbac..
C9C218D2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D5 |
Explanation: 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.
User Response: 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.
C9C218D6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218D9 |
Explanation: 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.
User Response: 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.
C9C218DA |
Explanation: 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.
User Response: 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.
C9C218DB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218DC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218DD |
Explanation: 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.
User Response: Contact the IBM Support Center.
C9C218DE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218DF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E3 |
Explanation: Transaction rolled back during prepare.
User Response: See C9C21809.
C9C218E4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218E8 |
Explanation: Transaction rolled back during prepare.
User Response: See C9C21809.
C9C218E9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218EA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218EB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218EC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218ED |
Explanation: An exception was thrown while driving the before_completion against a synchronization object. The transaction was rolled back.
User Response: Check the traces and messages prior to this failure to determine what exception was thrown from the sync object.
C9C218EE |
Explanation: Transaction rolled back during prepare.
User Response: See C9C21809.
C9C218EF |
Explanation: Transaction rolled back during commit.
User Response: See C9C21809.
C9C218F0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F4 |
Explanation: 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.
User Response: None. This condition can occur during or after an asynchronous transaction rollback. Common causes of asynchronous rollbacks include timeouts and abends.
C9C218F5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F6 |
Explanation: The WebSphere transaction service cannot support more than 254 inbound branches of a transaction in one server.
User Response: 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.
C9C218F7 |
Explanation: RRS was cancelled or failed while WebSphere for z/OS was active. WebSphere is unable to process work when RRS is unavailable.
User Response: Restart RRS and WebSphere.
C9C218F8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218F9 |
Explanation: A resolver which was about to enter a blocking call to RRS could not re-register himself as a transaction alarm.
User Response: Contact the IBM Support Center.
C9C218FA |
Explanation: 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.
User Response: The operation will retry periodically. If the problem persists, contact your resource vendor for assistance.
C9C218FB |
Explanation: 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.
User Response: The operation will retry periodically. If the problem persists, contact the IBM Support Center.
C9C218FC |
Explanation: 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.
User Response: The operation will retry periodically. If the problem persists, contact the IBM Support Center.
C9C218FD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C218FF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21900 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21901 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21902 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21903 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21904 |
Explanation: See C9C21899.
User Response: See C9C21899
C9C21905 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21906 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21907 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21908 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21909 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2190A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2190B |
Explanation: See C9C21908.
User Response: See C9C21908.
C9C2190C |
Explanation: See C9C21909.
User Response: See C9C21909.
C9C2190D |
Explanation: See C9C21907.
User Response: See C9C21907.
C9C2190E |
Explanation: See C9C21907.
User Response: See C9C21907.
C9C2190F |
Explanation: See C9C218FF.
User Response: See C9C218FF.
C9C21910 |
Explanation: See C9C21905.
User Response: See C9C21905.
C9C21911 |
Explanation: See C9C2190A.
User Response: See C9C2190A.
C9C21913 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21914 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21915 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21916 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21917 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21918 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21919 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2191A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2191B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2191C |
Explanation: Non-existent transaction detected for commit request.
User Response: See C9C21884.
C9C2191D |
Explanation: Non-existent transaction detected for get_control request.
User Response: See C9C21884.
C9C2191E |
Explanation: Non-existent transaction detected for suspend request.
User Response: See C9C21884.
C9C2191F |
Explanation: Non-existent transaction detected for rollback request.
User Response: See C9C21884.
C9C21920 |
Explanation: Non-existent transaction detected for Prepare request.
User Response: See C9C21884.
C9C21921 |
Explanation: Non-existent transaction detected for Commit request.
User Response: See C9C21884.
C9C21922 |
Explanation: See C9C21076.
User Response: See C9C21076.
C9C21923 |
Explanation: See C9C2107B.
User Response: See C9C2107B.
C9C21924 |
Explanation: See C9C2107C.
User Response: See C9C2107C.
C9C21925 |
Explanation: The XaRecoveryTableManager class could not be loaded by the JNI.
User Response: The XaRecoveryTableManager class may not be on the classpath. Ensure that the CR classpath specified is correct. If it is correct, contact the IBM Support Center.
C9C21926 |
Explanation: The "instance" method on the XaRecoveryTableManager class could not be found by the JNI.
User Response: Contact the IBM Support Center.
C9C21927 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21928 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21929 |
Explanation: The one or more methods on the XaRecoveryTableManager class could not be found by the JNI.
User Response: Ensure that your classpath is set correctly. Failing that, Contact the IBM Support Center.
C9C2192A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2192B |
Explanation: See C9C21928.
User Response: Contact the IBM Support Center.
C9C2192C |
Explanation: An array could not be allocated in the JVM through the JNI.
User Response: Contact the IBM Support Center.
C9C2192D |
Explanation: See C9C2192D.
User Response: See C9C2192D.
C9C2192E |
Explanation: 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.
User Response: 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.
C9C2192F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21930 |
Explanation: The transaction sequence number wrapped and needs to be logged in the XA partner log, but the log write failed.
User Response: 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.
C9C21931 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21932 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21933 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21934 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21935 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21936 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21937 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21938 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C21939 |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C2193A |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C2193B |
Explanation: See C9C21931.
User Response: See C9C21931.
C9C2193C |
Explanation: A server region thread associated with a transaction received a piece of work for a different tranaction.
User Response: Contact the IBM Support Center.
C9C2193D |
Explanation: The JTA transaction manager raised an unexpected exception while processing an inbound request.
User Response: Examine the error log for information about the original java exception that was raised.
C9C2193E |
Explanation: The JTA transaction manager raised an unexpected exception while processing an outbound reply.
User Response: Examine the error log for information about the original java exception that was raised.
C9C2193F |
Explanation: An unexpected java exception was encountered while obtaining a reference to the JTA transaction manager.
User Response: Examine the error log for information about the original java exception that was raised.
C9C21940 |
Explanation: An unexpected OTS UserException was encountered while processing transaction manager request.
User Response: Examine the error log for information about the original CORBA exception that was raised.
C9C21941 |
Explanation: The JVM raised an exeption while attempting to enter the monitor associated with the JTA transaction object from native code.
User Response: Examine the error log for information about the original java exception that was raised.
C9C21942 |
Explanation: The JVM raised an exeption while attempting to exit the monitor associated with the JTA transaction object from native code.
User Response: Examine the error log for information about the original java exception that was raised.
C9C21943 |
Explanation: 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.
User Response: Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
C9C21944 |
Explanation: The transaction identifer generated in the server region did not match the identifier generated in the control region from the primary key.
User Response: Contact the IBM Support Center.
C9C21945 |
Explanation: 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.
User Response: Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
C9C21946 |
Explanation: 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.
User Response: Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error.
C9C21947 |
Explanation: The JTA transaction manager raised an unexpected exception while attempting to determine the transaction attribute of the target object and operation.
User Response: Examine the error log for information about the original java exception that was raised.
C9C21948 |
Explanation: The RRS service ATREINT1 returned the value ATR_CONTEXT_TOKEN_INV. The Transaction will be marked rollback-only.
User Response: None.
C9C21949 |
Explanation: A request was received for a transaction that has already gone through a syncpoint.
User Response: None.
C9C21C01 |
Explanation: Invalid object reference detected.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C02 |
Explanation: Shasta marshaling error detected.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C03 |
Explanation: Shasta internal error detected.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C04 |
Explanation: _narrow method caught non-CORBA exception
User Response: Gather documentation and contact the IBM Support Center.
C9C21C05 |
Explanation: A CORBA::UNKNOWN error has been unmarshalled in the bindings from javaspace.
User Response: Look prior to this message to see if any java error messages have been recorded
C9C21C06 |
Explanation: A CORBA::UNKNOWN error has occured in the SOMRef process
User Response: Gather documentation and contact the IBM Support Center.
C9C21C30 |
Explanation: Function _CallMethod in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
C9C21C31 |
Explanation: Function _CallMethod in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
C9C21C32 |
Explanation: Function _StrongRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/WeakRef.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
C9C21C33 |
Explanation: Function _StrongRef in bbolrt.cpp could not find the "get" method in Java class /com/ibm/som/corba/rt/WeakRef.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains WeakRef.class
C9C21C34 |
Explanation: Function _WeakRef in bbolrt.cpp could not find Java class /com/ibm/som/corba/rt/SOMBase.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
C9C21C35 |
Explanation: Function _WeakRef in bbolrt.cpp could not find the "_weakref" method in Java class /com/ibm/som/corba/rt/SOMBase.class
User Response: Verify that the CLASSPATH environment variable specifies a JAR (Java ARchive) file that contains SOMBase.class
C9C21C36 |
Explanation: Function _WeakRef in bbolrt.cpp did not get a weak object reference for a Java object.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C37 |
Explanation: Function _isInstanceOf in bbolss.cpp is not implemented.
User Response: Do not use this function.
C9C21C38 |
Explanation: 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.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C39 |
Explanation: Function take_buffer in bbolsreq.cpp detected that the length of the CDR buffer is zero.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C3A |
Explanation: 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.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C3B |
Explanation: In bbolpoi.cpp, some CORBA DII object is nil after creation.
User Response: Gather documentation and contact the IBM Support Center.
C9C21C3C |
Explanation: In bbolpoi.cpp, some Context methods not supported
User Response: Change application program accordingly
C9C21C3D |
Explanation: 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.
User Response: Insure that the class name that is indicated in the associated message is installed on the server.
C9C21C3E |
Explanation: Function checkJavaException was called An Exception was thrown in a JNI thread.
User Response: Look prior to this message to find what JNI Exceptions were thrown.
C9C21C3F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C40 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C41 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C42 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C43 |
Explanation: RuntimeUtil failed to initialise because it failed to complete a FindClass
User Response: Gather documentation and contact the IBM support center.
C9C21C44 |
Explanation: RuntimeUtil failed to complete initilization
User Response: Gather documentation and contact the IBM support center.
C9C21C45 |
Explanation: in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
User Response: Gather documentation and contact the IBM support center
C9C21C46 |
Explanation: in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
User Response: Gather documentation and contact the IBM support center
C9C21C47 |
Explanation: in bbolUtil.cpp iconv_open failed during ASCII to EBCDIC process
User Response: Gather documentation and contact the IBM support center
C9C21C48 |
Explanation: in bbolUtil.cpp iconv failed during ASCII to EBCDIC process
User Response: Gather documentation and contact the IBM support center
C9C21C49 |
Explanation: 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.
User Response: 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.
C9C21C4A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C4B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C4C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C4D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C21C4E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22001 |
Explanation: An attempt is being made to set the specific server name to a value longer than 8 characters.
User Response: Correct the name and rerun the process.
C9C22002 |
Explanation: An _narrow or _narrow_in_trans on an object failed.
User Response: Contact the IBM Support Center.
C9C22009 |
Explanation: A call to a DB2 assembler service failed.
User Response: Use the return code, reason code, and DB2 service name reported in the error log and refer to the DB2 Messages and Codes book to determine the reason for the failure.
C9C2200E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2200F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22010 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22012 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22013 |
Explanation: A timeout occurred attempting to start a CB server. This could be due to a JCL error in the started procedure or other environmental problems.
User Response: Determine which server CB attempted to start and why it failed. Correct the problem and try again.
C9C22014 |
Explanation: This server was started after a Stop command was was issued for the CB 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.
User Response: None
C9C22015 |
Explanation: a backlevel server has been started. As all replicated servers already operate at a higher function level, the server must be abended.
User Response: Upgrade server to new function level.
C9C22016 |
Explanation: During the SM boostrap an unrecoverable error occured.
User Response: Analyze accompanying messages
C9C22017 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22018 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22019 |
Explanation: The internal CB environment could not be initialized.
User Response: Analyze accompanying messages
C9C22020 |
Explanation: The configuration file required for bootstrap could not be opened. See accompanying message for the exact filename.
User Response: Make sure that the environment variable CBCONFIG is set properly and that the path in HFS where it points to is actually there. If working in a sysplex environment make sure that this path is shared among all systems via NFS mounted HFS or shared HFS (OS/390 R9+).
C9C22021 |
Explanation: The (XML) configuration file which was used during during bootstrap or importServer is missing the configuration root node or contains invalid XML elements.
User Response: Bootstrap: make sure the environment variable CBCONFIG points to the correct configuration directory and a proper current.xml is available in this path: CONFIG)/configuration/current.xml. ImportServer: make sure the path you specified points to the correct server-configuration directory and a proper SERVERNAME.xml is available in the specified path. In case current.xml is damaged or missing, backup configurations can be found in the CONFIG)/configuration/backup directory. In case SERVERNAME.xml is damaged or missing, create a new SERVERNAME.xml file by exporting the server again using the EUI. See accompanying message for the name of the configuration that's actually being used.
C9C22022 |
Explanation: During bootstrap a new conversation is being created that needs to be bound to the default CB administrator that is specified using environment variable SM_DEFAULT_ADMIN. Now the object that represents the default administrator could not be found.
User Response: As the default administrator is also created during bootstrap processing, this is an internal error. Please contact IBM. See accompanying message for the ID of the administrator that's actually being used.
C9C22023 |
Explanation: The initialization of the XML parser or ICU class library failed. XML parser and the ICU lib are being used for importing configuration data or servers .
User Response: Make sure the environment variable ICU_DATA points to the correct location of the ICU converter files which are located in CONFIG)/configuration/icudata directory. See accompanying messages for more details about the cause for the problem.
C9C22024 |
Explanation: Errors occurred during the parsing of the XML file. The XML used for the import contains invalid XML elements.
User Response: See accompanying messages for more details.
C9C22025 |
Explanation: The import of configuration data failed because one of the objects to be imported already exists.
User Response: See accompanying messages for more details.
C9C22026 |
Explanation: The import of configuration data failed because one of the objects to be imported could not be created in the MOFW.
User Response: See accompanying messages for more details.
C9C22027 |
Explanation: The import of configuration data failed because of one if the objects to be imported references another object that could not be found.
User Response: See accompanying messages for more details.
C9C22028 |
Explanation: The import of configuration data failed due to an unclassified error.
User Response: See accompanying messages for more details about the cause for the problem.
C9C22029 |
Explanation: the daemon has been started on a backlevel database.
User Response: Upgrade database to new schema version via patch utility shipped with the driver, or start daemon with -ORBCBI COLD option.
C9C2202A |
Explanation: No server name was specified for Systems Management
User Response: Examine the BBOSMS procedure or the parameters which were used to start BBOSMS and correct to specify the appropriate server name.
C9C2202B |
Explanation: A user exception was caught by the main Systems Management routine.
User Response: Examine the error log for information regarding the thrown exception and take whatever action the exception indicates.
C9C2202C |
Explanation: CBSeries Daemon and Control Regions must run authorized. However, the space has detected that it is not. The space ends in error.
User Response: Check that all datasets referenced by the steplib statement are APF authorized.
C9C2202D |
Explanation: SM bootstrap has been applied to a completely bootstrapped database.
User Response: Apply BBOMCRDB first.
C9C2202E |
Explanation: Naming registration during server startup issued an unrecoverable error.
User Response: Analyze accompanying messages
C9C2202F |
Explanation: Context data manager issued an unrecoverable error when OTS tried to access component or method metadata.
User Response: Analyze accompanying messages
C9C22030 |
Explanation: SM EUI has been dynamically rerouted to a different SM Server that is currently running under a different function level or has an incompatible scripting version. The SM EUI disconnects.
User Response: Reconnect with your EUI and repeat the last step that has been performed.
C9C22031 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22032 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22033 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22034 |
Explanation: Environment variables value field is empty or not set (which is a mandatory one)
User Response: 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)
C9C22035 |
Explanation: Environment variables value field is empty or not set (which is a mandatory one)
User Response: Assign a valid (non-null) value for the environment variable indicated by message (this minor code is for mandatory environment variables but not in curent.env )
C9C221EF |
Explanation: This server was started after a Stop command was was issued for the WebSphere 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.
User Response: None
C9C22401 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22402 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22403 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22404 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22405 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22406 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22407 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22408 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22409 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2240A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2240B |
Explanation: In order for the Component Broker Daemon to start properly, the DAEMON_IPNAME environment variable must be set. If it is not set, this exception results and the Daemon will not initialize.
User Response: Set the DAEMON_IPNAME environment variable appropriately (probably to the TCP/IP host name of the system where you are trying to start the Daemon).
C9C2240C |
Explanation: CB Series server address spaces can not start without an active CB Series 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.
User Response: Start the CB Series Daemon on this system prior to starting other CB Series servers.
C9C2240D |
Explanation: CB Series server address spaces can not start without an active CB Series 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.
User Response: Start the CB Series Daemon on this system prior to starting other CB Series servers.
C9C2240E |
Explanation: CB Series server address spaces can not start without an active CB Series 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.
User Response: Start the CB Series Daemon on this system prior to starting other CB Series servers.
C9C2240F |
Explanation: CB Series server address spaces can not start without an active CB Series 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.
User Response: Start the CB Series Daemon on this system prior to starting other CB Series servers.
C9C22410 |
Explanation: All CB Series 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.
User Response: Specify the correct specific server name when starting the server. This name was specified when the server was defined to CB Series Systems Management Adminstration.
C9C22411 |
Explanation: All CB Series 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.
User Response: Specify the correct specific server name when starting the server. This name was specified when the server was defined to CB Series Systems Management Adminstration.
C9C22412 |
Explanation: All CB Series 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.
User Response: Specify the correct specific server name when starting the server. This name was specified when the server was defined to CB Series Systems Management Adminstration.
C9C22413 |
Explanation: All CB Series 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.
User Response: Specify the correct specific server name when starting the server. This name was specified when the server was defined to CB Series Systems Management Adminstration.
C9C22414 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22415 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22416 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22417 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22418 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22419 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2241A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2241B |
Explanation: In PPT::PPT(char*), BBO3PPT1 Macro is unable to call IEFPPSCN because APF Not Authorized to perform such action.
User Response: Make Sure Load Module is APF Authorized.
C9C2241C |
Explanation: PPT Entry Specification Error
User Response: Correct PPT Entry - BBOSCHED
C9C2241E |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was active. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C2241F |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was active. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C22420 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22421 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22422 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22423 |
Explanation: A bad return code received from service CRGRRMD.
User Response: See message BBOO0056E in the error log for additional information.
C9C22425 |
Explanation: A bad return code received from service CTXSDTA.
User Response: See message BBOO0056E in the error log for additional information.
C9C22427 |
Explanation: A bad return code received from service CTXBEGC.
User Response: See message BBOO0056E in the error log for additional information.
C9C22428 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22429 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2242F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22430 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22431 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22432 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22433 |
Explanation: An attempt was made to start a CB Series Control Region while another Control Region with the same specific server name was also starting. Only one CB Series Control Region with a given specific server name can be active at one time. This Control Region terminates in error.
User Response: Do not attempt to start two CB Control Regions with the same specific server name.
C9C22434 |
Explanation: An attempt was made to start a CB Series Control Region while another Control Region with the same specific server name was also starting. Only one CB Series Control Region with a given specific server name can be active at one time. This Control Region terminates in error.
User Response: Do not attempt to start two CB Control Regions with the same specific server name.
C9C22435 |
Explanation: An attempt was made to start a CB Series Control Region while another Control Region with the same specific server name was also starting. Only one CB Series Control Region with a given specific server name can be active at one time. This Control Region terminates in error.
User Response: Do not attempt to start two CB Control Regions with the same specific server name.
C9C22436 |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was also starting. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C22437 |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was also starting. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C22438 |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was also starting. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C22439 |
Explanation: An attempt was made to start a CB Series Daemon while another CB Series Daemon was also starting. Only one CB Series Daemon can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two CB Series Daemons on the same system at the same time.
C9C2243A |
Explanation: While a CB Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no CB Series servers can exist without a Daemon present on the system, this server must end.
User Response: Determine why the Daemon failed and restart the daemon and other servers as necessary.
C9C2243B |
Explanation: While a CB Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no CB Series servers can exist without a Daemon present on the system, this server must end.
User Response: Determine why the Daemon failed and restart the daemon and other servers as necessary.
C9C2243C |
Explanation: While a CB Series Daemon was active when this server starting initializing, it was no longer present when initialization completed. Since no CB Series servers can exist without a Daemon present on the system, this server must end.
User Response: Determine why the Daemon failed and restart the daemon and other servers as necessary.
C9C2243D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2243E |
Explanation: A server region was started and was unable to find the control region it goes with.
User Response: If the server region started as the control region was ending then this is normal. If a server region was manually started (instead of allowing WLM to start it) then possibly the parameters were incorrect or it was started on the wrong system.
C9C2243F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22440 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22441 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22442 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22443 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22444 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22445 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22446 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22447 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22448 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22449 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2244A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2244B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22804 |
Explanation: RRSAF DB2 IDENTIFY processing failed for the DB2 active server repository thread.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C22805 |
Explanation: RRSAF DB2 SIGNON processing failed for the DB2 active server repository thread.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C22806 |
Explanation: RRSAF DB2 CREATE THREAD processing failed for the DB2 active server repository thread.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C22808 |
Explanation: RRSAF DB2 Terminate Thread processing failed for the DB2 active server respository thread.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C22809 |
Explanation: RRSAF DB2 Terminate Identity processing failed for the DB2 active server respository thread.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C2280A |
Explanation: An unsupported daue work queue element type was detected. Processing of the daue work queue will be terminated.
User Response: Report the problem and accompanying information to your next level of service or the IBM Support Center.
C9C22810 |
Explanation: Initialization of a CB Server failed loading a required product load module. Look for the accompanying message for the name of the module which could not be found.
User Response: Determine which module could not be found and why and correct the problem and restart the server.
C9C2281A |
Explanation: No server name was specified for the Daemon.
User Response: Examine the Daemon procedure or the parameters which were used to start the Daemon and correct to specify the appropriate server name.
C9C2281B |
Explanation: A user exception was caught by the main Daemon routine.
User Response: Examine the error log for information regarding the thrown exception and take whatever action the exception indicates. This should never happen :-)
C9C2281C |
Explanation: CBSeries Daemon and Control Regions must run authorized. However, the space has detected that it is not. The space ends in error.
User Response: 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
C9C2281E |
Explanation: The DSNLOAD which is done to setup DB2 from the DAUT thread initialization failed. An exception trace is cut with the return code.
User Response: The Daemon's call to DSNLOAD setting up DB2 failed. An exception trace is cut with the return code from DSNLOAD.
C9C2281F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22820 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22821 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22822 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22823 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C22824 |
Explanation: Attempting to add a new entry we found a duplicate exists, so we try to delete it. That delete failed. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22825 |
Explanation: Attempting to add a new entry to the DB2 ASR table we failed. The failure was not 'duplicate entry'. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22826 |
Explanation: Attempting to delete a DB2 ASR entry we failed BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22827 |
Explanation: Attempting to update a DB2 ASR entry we failed BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22828 |
Explanation: During reprime processing we try to read all the ASR entries from DB2 for a particular system. That read failed. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22829 |
Explanation: Deleting all entries for a specified system we encountered an error from DB2. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C2282A |
Explanation: 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.
User Response: 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.
C9C2282B |
Explanation: 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.
User Response: 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.
C9C2282C |
Explanation: 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.
User Response: 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.
C9C2282D |
Explanation: 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.
User Response: 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.
C9C2282E |
Explanation: 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.
User Response: 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.
C9C2282F |
Explanation: 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.
User Response: 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.
C9C22830 |
Explanation: 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.
User Response: 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.
C9C22831 |
Explanation: 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.
User Response: 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.
C9C22832 |
Explanation: 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.
User Response: 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.
C9C22833 |
Explanation: 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.
User Response: 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.
C9C22834 |
Explanation: Opening a cursor to do the initial read of all DB2 ASR entries we encountered an error. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22835 |
Explanation: Opening a cursor to do a reprime read by sysname we encountered an error. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22836 |
Explanation: Opening a cursor to do a dmn down read by sysname we encountered an error. BBODADT logged information about the failure.
User Response: "IBM Interal Only"
C9C22837 |
Explanation: 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 Control Regions 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.
User Response: 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.
C9C22838 |
Explanation: In order for the WebSphere 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.
User Response: Set the DAEMON GROUP NAME environment variable.
C9C22839 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23001 |
Explanation: 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.
User Response: 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.
C9C23002 |
Explanation: An attempt was made to invoke the Externalization StreamIO method, write_object(). This method is not implemented by the Externalization StreamIO support.
User Response: Remove any usage of the write_object method from your code.
C9C23003 |
Explanation: An attempt was made to invoke the Externalization StreamIO method, write_graph(). This method is not implemented by the Externalization StreamIO support.
User Response: Remove any usage of the write_graph method from your code.
C9C23004 |
Explanation: An attempt was made to invoke the Externalization StreamIO method, read_object(). This method is not implemented by the Externalization StreamIO support.
User Response: Remove any usage of the read_object method from your code.
C9C23005 |
Explanation: An attempt was made to invoke the Externalization StreamIO method, read_graph(). This method is not implemented by the Externalization StreamIO support.
User Response: Remove any usage of the read_graph method from your code.
C9C23007 |
Explanation: 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.
User Response: Remove any usage of the read_wchar method from your code or switch to an IBM format 2 externalization.
C9C23008 |
Explanation: 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.
User Response: Remove any usage of the read_wstring method from your code or switch to an IBM format 2 externalization.
C9C23009 |
Explanation: 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.
User Response: Remove any usage of the write_wchar method from your code or switch to an IBM format 2 externalization.
C9C2300A |
Explanation: 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.
User Response: Remove any usage of the write_wstring method from your code or switch to an IBM format 2 externalization.
C9C2300B |
Explanation: An attempt was made to allocate an encapsulation buffer for an EncapIIOP object that is being used by the Externalization StreamIO support.
User Response: Report this problem to your next level of support or the IBM Support Center.
C9C23101 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23102 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23103 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23104 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23105 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23106 |
Explanation: This method is not implemented.
User Response: Call another method to perform the intended operation.
C9C23107 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23108 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23109 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2310A |
Explanation: 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)
User Response: Verify that wide character support is configured correctly.
C9C2310B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2310C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2310D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2310E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2310F |
Explanation: 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.)
User Response: Inspect the values of wide character parameters associated with the method invocation that caused the error.
C9C23110 |
Explanation: The native code page used for wide characters is non-byte-oriented with a character length other than 2.
User Response: 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.
C9C23111 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23112 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23113 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23114 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23115 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23116 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23117 |
Explanation: 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.
User Response: 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.
C9C23118 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C23119 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2311A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24002 |
Explanation: Default identities are allowed but a default identity has not been defined for this server. Authorization is denied.
User Response: Configure system management to define a default identity for this server.
C9C24003 |
Explanation: A userid with an invalid length was provided in the security context. Authorization was denied.
User Response: The ORB Request for the client must supply an eight character string, padded with blanks for userids less than eight characters.
C9C24004 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24005 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24006 |
Explanation: Client ID does not have RACF authorization to BIND to this server.
User Response: Obtain the needed RACF authorization and resubmit the request (CB.BIND.servername).
C9C24007 |
Explanation: 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.
User Response: 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.
C9C24008 |
Explanation: SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C24009 |
Explanation: SecurityAttributeType AccountingId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400A |
Explanation: SecurityAttributeType NonRepudiationId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400B |
Explanation: SecurityAttributeType GroupId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400C |
Explanation: SecurityAttributeType Role is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400D |
Explanation: SecurityAttributeType AttributeSet is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400E |
Explanation: SecurityAttributeType Clearance is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C2400F |
Explanation: SecurityAttributeType Capability is NOT IMPLEMENTED as a SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C24010 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24011 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24012 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24013 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24014 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24015 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24016 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24017 |
Explanation: Session owner does not have RACF authorization to pass multiple clients to this server.
User Response: Obtain the needed RACF authorization (CONTROL) and resubmit the request (CB.BIND.servername).
C9C24018 |
Explanation: Client id does not have RACF authorization to execute this <serverName.homeName>.
User Response: Obtain the needed RACF authorization and resubmit the request.
C9C24019 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2401A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2401B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2401C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2401D |
Explanation: Client ID does not have RACF authorization to execute on this server.
User Response: 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
C9C2401E |
Explanation: There was no password provided in a security context thought to contain a userid and password.
User Response: If running with the default userid, see if a default password was set.
C9C2401F |
Explanation: SecurityAttributeType Public is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C24020 |
Explanation: The copy method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
User Response: Do not ask for this method in this class.
C9C24021 |
Explanation: the set_security_features method in SecurityLevel2::Credentials is not implemented.
User Response: Do not ask for this method in this class.
C9C24022 |
Explanation: the get_security_features method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
User Response: Do not ask for this method in this class.
C9C24023 |
Explanation: the is_valid method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
User Response: Do not ask for this method in this class.
C9C24024 |
Explanation: the refresh method in SecurityLevel2::Credentials is NOT IMPLEMENTED.
User Response: Do not ask for this method in this class.
C9C24025 |
Explanation: The SCO information indicated that this server was to use DCE security but DCE security services were not available when the server was started.
User Response: 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.
C9C24026 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24027 |
Explanation: DCE PRINCIPAL is not mapped to MVS userid.
User Response: "Set up principal UUID to MVS ID map in RACF"
C9C24028 |
Explanation: Version of Native security does not match expected version #.
User Response: Check security version of client and server
C9C24029 |
Explanation: Raw Client executing protected code
User Response: Fix client code
C9C2402A |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C2402B |
Explanation: A native security context was sent remotely
User Response: Possible external hack attempted
C9C2402C |
Explanation: A native security context was sent remotely
User Response: Possible external hack attempted
C9C2402D |
Explanation: Get Transportable Identity returned a null
User Response: IBM internal problem
C9C2402E |
Explanation: Get Transportable Identity returned a null
User Response: IBM internal problem
C9C2402F |
Explanation: The non-repudiation credentials type is not implemented.
User Response: Do not ask for this credentials type.
C9C24030 |
Explanation: ALthough the request orignated in the Server region, no Native Security Context exists. Originated in get_userid() method.
User Response: 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 server region abended before doing the copy.
C9C24031 |
Explanation: ALthough the request originated in the Server region, no Native Security Context exists. Originated in get_userid_build_ctx() method.
User Response: 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 server region abended before doing the copy.
C9C24032 |
Explanation: Client id does not have RACF authorization to USE this server.
User Response: Obtain the needed RACF authorization and resubmit the request (CB.servername).
C9C24033 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24035 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24036 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24037 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24038 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24039 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2403F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24040 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24041 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24043 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24044 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24045 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24046 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24048 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24049 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2404A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2404B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2404C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2404E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2404F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24050 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24051 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24052 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24054 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24055 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24056 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24057 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24058 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2405A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2405B |
Explanation: Mutual authentication failed when client tried to verify the server.
User Response: investigate the server.
C9C2405D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2405E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2405F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24060 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24061 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24062 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24063 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24064 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2406A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24070 |
Explanation: There is no authentication for this client
User Response:
C9C24071 |
Explanation: Failure trying to authenticate client
User Response:
C9C24073 |
Explanation: 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.
User Response: 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.
C9C24074 |
Explanation: A client process failed in the attempt to initiate a a request to a server using DCE security.
User Response: 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 the IBM Support Center.
C9C24075 |
Explanation: A client process failed in a request to a server using DCE security.
User Response: 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 the IBM Support Center.
C9C24076 |
Explanation: A client process failed in an attempt to mutually authenticate with a server using DCE security over SSL.
User Response: 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.
C9C24077 |
Explanation: An SSL Client Certificate was received by a server during SSL handshake processing. This certificated cannot be resolved to an identity.
User Response: The SSL client certificate is probably not in the servers keyring, and cannot be transformed into an S/390 identity. If the problem persists, contact your IBM Support Center.
C9C24080 |
Explanation: A client process failed in a request to a server using an unknown security method.
User Response: This is an internal error! Please report this problem to your next level of support or the IBM Support Center.
C9C24081 |
Explanation: A client process failed in an attempt to mutually authenticate with a server using DCE security.
User Response: 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 the IBM Support Center.
C9C24082 |
Explanation: RACF - Parameter list error occurred
User Response:
C9C24083 |
Explanation: RACF - An internal error occurred during RACF processing
User Response:
C9C24084 |
Explanation: RACF - Recovery environment could not be established
User Response:
C9C24085 |
Explanation: RACF - User ID is not defined to RACF
User Response:
C9C24086 |
Explanation: RACF - Password or PassTicket is not valid
User Response:
C9C24087 |
Explanation: RACF - Password is expired
User Response:
C9C24088 |
Explanation: RACF - User ID is revoked
User Response:
C9C24089 |
Explanation: RACF - User is not authorized
User Response:
C9C2408A |
Explanation: RACF - Certificate is not valid
User Response:
C9C2408B |
Explanation: RACF - Either no user ID is defined for this certificate or the certificate status is NOTRUST
User Response:
C9C2408C |
Explanation: Null sessionid in NatSecCtx_Auth
User Response:
C9C2408D |
Explanation: MethAuthCheck was issued in an address space without a BACB
User Response:
C9C2408E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2408F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24090 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24091 |
Explanation: 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 Component Broker, 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.
User Response: 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.
C9C24092 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24093 |
Explanation: A client process failed in an attempt to mutually authenticate with a server using DCE security.
User Response: 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 the IBM Support Center.
C9C24094 |
Explanation: A client process failed in an attempt to mutually authenticate with a server using DCE security.
User Response: 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 the IBM Support Center.
C9C24096 |
Explanation: 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.
User Response: 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).
C9C24097 |
Explanation: Servers reply to the Client's initial message has already been processed by this client.
User Response: The handshake between the client and the server is out of sequence. Resubmit the request
C9C24098 |
Explanation: 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.
User Response: 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 the IBM Support Center. Ref: OS/390 V2R7.0 DCE Messages and Codes Document Number: SC28-1591-06
C9C24099 |
Explanation: 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.
User Response: 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 the IBM Support Center.
C9C2409A |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2409B |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2409C |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2409D |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2409E |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C2409F |
Explanation: 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
User Response: 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 the IBM Support Center.
C9C240A0 |
Explanation: The authentication class was not found during the DCE mutual authentication process after the DCE first time message was handled.
User Response: 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 the IBM Support Center.
C9C240A1 |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C240A2 |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C240A3 |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C240A4 |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C240A5 |
Explanation: Server attempting to execute non server code
User Response: Fix server code
C9C240A6 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240A7 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240A8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240A9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240AA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240AB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240AC |
Explanation: Mutual authentication failed when client tried to verify the server.
User Response: investigate the server.
C9C240AD |
Explanation: Mutual authentication failed when client tried to verify the server.
User Response: investigate the server.
C9C240AE |
Explanation: Mutual authentication failed when client tried to verify the server.
User Response: investigate the server.
C9C240AF |
Explanation: SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C240B0 |
Explanation: SecurityAttributeType AuditId is NOT IMPLEMENTED as a valid SecurityAttributeType in the SecurityLevel1::get_attributes() class.
User Response: Do not ask for this SecurityAttribute type in this class.
C9C240B1 |
Explanation: An error occurred during the new of the saved RACO pointer in security method convertToSessionID. Possibly memory could not be allocated for the pointer.
User Response: 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 the IBM Support Center.
C9C240B2 |
Explanation: 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.
User Response: 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.
C9C240B3 |
Explanation: 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.
User Response: The client ORB Request must contain a complete security context.
C9C240B4 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240B5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240B6 |
Explanation: An SSL Type 1 Association Complete service context encountered by the server but there was no corresponding authentication segment.
User Response: 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 the IBM Support Center.
C9C240B7 |
Explanation: An SSL Type 1 service context was received by a server with a msgtype of something other than ASSOC_COMPLETE or MUTUAL AUTH.
User Response: You may be using an incompatible client and server configuration. If the problem persists, contact your the IBM Support Center.
C9C240B8 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240B9 |
Explanation: The SSL Session identity was not given update authority and is not authorized to propagate asserted identities.
User Response: 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 the IBM Support Center.
C9C240BA |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240BB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240BC |
Explanation: 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.
User Response: Verify the CB.BIND on the target server and consider disabling asserted identity for this client or server.
C9C240C0 |
Explanation: A client process failed in an attempt to authenticate with a server.
User Response: 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 the IBM Support Center.
C9C240C1 |
Explanation: A client process failed in an attempt to authenticate with a server.
User Response: 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 the IBM Support Center.
C9C240C2 |
Explanation: A client process failed in an attempt to authenticate with a server.
User Response: 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 the IBM Support Center.
C9C240C3 |
Explanation: An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240C4 |
Explanation: An error occurred during the new of a Outbound_UseridInfo structure in the security method createOutbound. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240C5 |
Explanation: An error occurred during the new of a SupportedSecurities structure in the security method createOutbound. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240C6 |
Explanation: A process failed to find the SSL kerberos security context associated with the request.
User Response: 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 the IBM Support Center.
C9C240C7 |
Explanation: An error occurred during the allocation of a sting for a Kerberos session identifier in the security method KRBAuth. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240C8 |
Explanation: A client process failed in an attempt to authenticate with a server using Kerberos GSS_API security over SSL.
User Response: 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 the IBM Support Center.
C9C240C9 |
Explanation: An error occurred during the new of a sting for a Kerberos name in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240CA |
Explanation: An error occurred during the new of a Kerberos GSS_API service context in the security method createSSLKRBGSSAPIAuthenticationContext. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240CB |
Explanation: An error occurred during the new of a sting for a Kerberos name in the security method initKRB. Memory could not be allocated.
User Response: 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 the IBM Support Center.
C9C240CC |
Explanation: 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.
User Response: 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 the IBM Support Center.
C9C240CD |
Explanation: An error in the DCE api gss_init_sec_context.
User Response: 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 the IBM Support Center.
C9C240CE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240CF |
Explanation: 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.
User Response: 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 the IBM Support Center.
C9C240D0 |
Explanation: The requester does not have the authorization to make this request.
User Response: 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 the IBM Support Center.
C9C240D2 |
Explanation: The requester failed the Kerberos authentication test the server ran out of memory.
User Response: 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 the IBM Support Center.
C9C240D3 |
Explanation: A client process failed in an attempt to authenticate with a server.
User Response: 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 the IBM Support Center.
C9C240D4 |
Explanation: A client process failed in an attempt to authenticate with a server.
User Response: 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 the IBM Support Center.
C9C240D5 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240D6 |
Explanation: An error occurred when the server attempted to accept the client context.
User Response: 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 contact the IBM support center.
C9C240D7 |
Explanation: An error occurred when the server attempted to extract the principal name from the security context.
User Response: 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 contact the IBM support center.
C9C240D8 |
Explanation: The Kerberos principal name extracted from the security context is too long.
User Response: Correct the principal name and try the request again. If the problem persists, report it to your next level of support or contact the IBM support center.
C9C240D9 |
Explanation: The Kerberos principal name does not contain an "at" sign (The principal name should be in the form principallm.
User Response: Correct the principal name and try the request again. If the problem persists, report it to your next level of support or contact the IBM support center.
C9C240DA |
Explanation: 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.
User Response: 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 contact the IBM support center.
C9C240DB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240DC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240DD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240DE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240DF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240E0 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240E1 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240E2 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240E3 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C240E4 |
Explanation: Failure trying to authenticate role name
User Response: Correct any problems with the definitions of users or EJBROLE profiles. Ensure the EJBROLE class is active.
C9C240E5 |
Explanation: push Identity failed, because on OS thread function disabled
User Response: Cannot synch OS thread to Userid, enableSyncOSThread = false. Check settings in SM GUI
C9C240E6 |
Explanation: Caller ID does not have permission to execute method
User Response: Make sure that the caller ID has permission to access that particular method.
C9C240E7 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240E8 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240E9 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240EA |
Explanation: The CSIv2 security attribute service context included authorization token. This level of z/OS WebSphere does not support authorization tokems.
User Response: 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.
C9C240EB |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240EC |
Explanation: 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.
User Response: 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.
C9C240ED |
Explanation: 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.
User Response: 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.
C9C240EE |
Explanation: The CSIv2 security attribute service context contained an asserted identity of the Distingushed Name type and, the target server is not configured to support this type of asserted identity.
User Response: 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 Distingushed Names.
C9C240EF |
Explanation: 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.
User Response: Have the client process change its request to use a different asserted identity type that is supported by the target server.
C9C240F0 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F1 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F2 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F3 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F4 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F5 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F6 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
C9C240F7 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C240F8 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
C9C240F9 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not include the GSSUP password.
C9C240FA |
Explanation: The CSIv2 security attribute service context included in a GIOP request contained a invalid userid.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid userid.
C9C240FB |
Explanation: The CSIv2 security attribute service context included in a GIOP request contained a invalid password.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not contain a valid password.
C9C240FC |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: This is most likely a problem caused by the process that formed the request and context. The context does not include a valid userid.
C9C240FD |
Explanation: 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.
User Response: 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.
C9C240FE |
Explanation: Get Transportable Identity returned a null
User Response: IBM internal problem
C9C24100 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: We have not done Kerberos yet.
C9C24101 |
Explanation: The CSIv2 security attribute service message context contains a context identifier that in not valid at the target server.
User Response: 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.
C9C24102 |
Explanation: The getJavaEnv external function was not found in the BBOLRT dll.
User Response: 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.
C9C24103 |
Explanation: The BBOLRT dll was not able to be loaded.
User Response: 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.
C9C24104 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C24105 |
Explanation: The creation of a CSIV2 GSSUP context failed.
User Response: 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 the IBM Support Center.
C9C24106 |
Explanation: The creation of a CSIV2 Idenity Assertion context failed.
User Response: 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 the IBM Support Center.
C9C24107 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24108 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24109 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410A |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410B |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410C |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410D |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410E |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2410F |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24110 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24111 |
Explanation: 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.
User Response: 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.
C9C24112 |
Explanation: 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.
User Response: 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.
C9C24113 |
Explanation: 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.
User Response: 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.
C9C24114 |
Explanation: 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.
User Response: The most likely reason for this is that the context generator is sending a bad context.
C9C24115 |
Explanation: 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.
User Response: The most likely reason for this is that the context generator is sending a bad context.
C9C24116 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24117 |
Explanation: The server was not able to produce a token value based on the authorization token sent in a CSIv2 context.
User Response: This is an internal error. Please report this problem to your next level of support or the IBM Support Center.
C9C24118 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24119 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C2411A |
Explanation: An error occurred when the server attempted to accept the client Kerberos gssapi context.
User Response: 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 contact the IBM support center.
C9C2411B |
Explanation: An error occurred when the server attempted to extract the principal name from the security context.
User Response: 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 contact the IBM support center.
C9C2411C |
Explanation: The Kerberos principal name extracted from the security context is too long.
User Response: Correct the principal name and try the request again. If the problem persists, report it to your next level of support or contact the IBM support center.
C9C2411D |
Explanation: The Kerberos principal name does not contain an "at" sign (The principal name should be in the form principallm.
User Response: Correct the principal name and try the request again. If the problem persists, report it to your next level of support or contact the IBM support center.
C9C2411E |
Explanation: During Kerberos authentication, CB was unable to obtain the SAF user associated with the Kerberos principal.
User Response: 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 contact the IBM support center.
C9C2411F |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24120 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: The CSIv2 security attribute service context included an X501 Distinguished Name token. There was an internal error processing the token. Contact the IBM support center.
C9C24121 |
Explanation: The CSIv2 security attribute service context included in a GIOP request is not valid.
User Response: 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.
C9C24C01 |
Explanation: Adapter code encountered an unexpected system failure.
User Response: Contact the IBM Support Center.
C9C24C02 |
Explanation: Adapter code received an invalid input parameter.
User Response: Contact the IBM Support Center.
C9C24C03 |
Explanation: The adapter is unable to narrow to the adapter resource manager.
User Response: Contact the IBM Support Center.
C9C24C04 |
Explanation: Adapter code received an unknown unexpected interrupt.
User Response: Contact the IBM Support Center.
C9C24C05 |
Explanation: Adapter code using APPC failed to allocate the conversation
User Response: 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.
C9C24C06 |
Explanation: Adapter code using APPC failed while invoking the APPC send service.
User Response: 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.
C9C24C07 |
Explanation: Adapter code using APPC failed while invoking the APPC receive service.
User Response: 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.
C9C24C08 |
Explanation: Adapter code using APPC failed while invoking the APPC confirmed service.
User Response: 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.
C9C24C09 |
Explanation: Adapter code using APPC failed while invoking the APPC deallocate service.
User Response: 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.
C9C24C0A |
Explanation: Adapter code failed while using one of the CICSEXCI services.
User Response: Check the CB error log for the string "CICSEXCI" for further diagnostic information.
C9C24C0B |
Explanation: Specified TPName (also known as transaction program name in IMS or as Function Program name in the J2EE Connector Architecture) exceeds maximum length.
User Response: Specify a shorter name. Consult IMS and APPC documentation for specific parameter requirements.
C9C2576C |
Explanation: getServiceContextList is not implemented in this implementation of ClientResponse.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support.
C9C2576D |
Explanation: getRequestId is not implemented in this implementation of ClientResponse.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support.
C9C2576E |
Explanation: getForwardedIOR is not implemented in this implementation of ClientResponse.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support.
C9C2576F |
Explanation: peekUserExceptionId is not implemented in this implementation of ClientResponse.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obivous, contact IBM support.
C9C2577C |
Explanation: The object given to the ORB had an incorrect delegate while trying to load a IDLJ stub.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C2577D |
Explanation: An unexpected error has occurred in a J2EE server during execution of a J2EE request.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C2577E |
Explanation: An unexpected error has occurred in a J2EE server during execution of a J2EE request.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C2577F |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C25780 |
Explanation: The com.ibm.ws390.rmi.corba.ClientDelegate class could not be found by Java.
User Response: Ensure that the WebSphere/390 EE runtime jar files are on the failing process's CLASSPATH.
C9C25790 |
Explanation: 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.
User Response: None. This is not an error.
C9C2579F |
Explanation: An unexpected error has occurred in a J2EE server during execution of a J2EE request.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C257A9 |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257AB |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257AC |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257AD |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257AE |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257AF |
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center.
C9C257C8 |
Explanation: A request to dispatch a callback object failed because the target callback object is not registered with the client ORB.
User Response: Contact IBM support.
C9C257C9 |
Explanation: A request to dispatch a callback object was received with a method name that the target object does not support.
User Response: Contact IBM support.
C9C257CA |
Explanation: An error occurred while trying to load an RMI/IIOP Tie.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obvious, contact IBM support.
C9C257CB |
Explanation: An error occurred while trying to load an RMI/IIOP Stub.
User Response: Look for a Java stack trace in the server's SYSOUT. If the problem is not obvious, contact IBM support.
C9C257CC |
Explanation: 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.
User Response: Correct the application.
C9C257CD |
Explanation: The get_interface() method has been deprecated and is not supported for J2EE components.
User Response: Correct the application.
C9C257CE |
Explanation: The J2EE container returned a null remote implementation when trying to execute a J2EE request.
User Response: Look for a Java stack trace in the server's SYSOUT and report the exception to IBM.
C9C257EE |
Explanation: The ORB received an exception from the J2EE container while trying to load an IDLJ stub.
User Response: Correct the application.
C9C257EF |
Explanation: The string_to_object method was passed a zero length string.
User Response: Correct the application.
C9C257F0 |
Explanation: The string_to_object method was passed a string that is not a stringified IOR.
User Response: Correct the application.
C9C257F0 |
Explanation: The string_to_object method was passed a string that is not a stringified IOR.
User Response: Correct the application.
C9C257F1 |
Explanation: The string_to_object method was passed a NULL string.
User Response: Correct the application.
C9C257F2 |
Explanation: The resolve_initial_references() method was driven on a singleton Java ORB, which singleton ORBs do not implement.
User Response: None
C9C257F3 |
Explanation: The ORB received an exception from the J2EE container while trying to load a local mode RMI/IIOP stub.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C257F4 |
Explanation: The ORB received a NULL remote implementation from the J2EE container while trying to load a local mode RMI/IIOP stub.
User Response: Find the Java stack trace in the server's SYSOUT to determine the actual exception that occurred.
C9C25801 |
Explanation: The user id to bind to the LDAP Server was not supplied to the Systems Management Server. This userid is required because the Systems Management Server requires write authority to the LDAP Server for the purpose of registering the EJB object homes/factories.
User Response: Add the following to the current.env for the Systems Management Server: java.naming.security.principal=[userid] Where userid equals the value in the ldif file used to initialize LDAP for WebSphere. The value to use is the entryowner value associated with the "WAS Naming over LDAP Name Tree Root"
C9C25802 |
Explanation: The password used to bind to the LDAP Server was not supplied to the Systems Management Server. The password is required because the Systems Management Server requires write authority to the LDAP Server for the purpose of registering the EJB object homes/factories.
User Response: Add the following to the current.env for the Systems Management Server: java.naming.security.credentials=[password] Where password equals the value in the ldif file used to initialize LDAP for WebSphere. The value to use is the userPassword value associated with the "WAS Naming over LDAP Name Tree Root"
C9C25803 |
Explanation: Systems Management Server was unable to setup the required java System Properties for the purpose of connecting to the LDAP Server.
User Response: Check and make sure the Naming Server is active. Check for any exceptions in Systems Management. Check for a Java stack trace in the Systems Management job log. This will give an indication of any possible error that may have caused the failure.
C9C25804 |
Explanation: Create of the upper tree structure in the LDAP Server failed.
User Response: Check the Systems Management Server job log for Java stack trace. This will give possible indications of the problem. Some of the problems may be, the LDAP Server is not running, user id and/or password may be incorrect, the host name and/or port may be incorrect. Userid and password should be in the current.env of the Systems Systems Management Server. The environment variable names are java.naming.security.principal,java.naming.security.credentials. If com.ibm.ws.naming.ldap.masterurl was not specified in the current.env of the Naming Server then the default host and port were used. The default host is the the system the Naming Server is running on. The default port is 1389.
C9C25805 |
Explanation: Bean method raised an EJBException that did not contain an internal exception.
User Response: Bean methods should utilize EJBExceptions to encapsulate runtime errors. EJBExceptions are instances of RuntimeException and therefore will not be surfaced back to a client. Only Application Exceptions, exceptions specified on the beans remote interface and RemoteExceptions are to be surfaced back to the client as per the EJB1.1 specification. EJBExceptions are not coded on the remote interface. Re-Code the bean method to utilize EJBExceptions in this manner or anticipate that the client will see this UNKNOWN/minor code combination as a RemoteException.
C9C2C409 |
Explanation: An ORB service such as string_to_IOR received null or bad parameters.
User Response: report this error to your next level of support or to the IBM Support Center.
C9C2C601 |
Explanation: Null synchronizer pointer in register_sync.
User Response: No action possible , raise CORBA::BAD_PARAM exception.
C9C2C602 |
Explanation: Null TransactionService Context in extract_gitd.
User Response: No action possible, raise CORBA::BAD_PARAM exception.
C9C2C603 |
Explanation: Null synchronizer pointer in register_sync.
User Response: No action possible, raise CORBA::BAD_PARAM exception.
C9C2C604 |
Explanation: Unable to register resource due to invalid resource parameter.
User Response: Check for an application error.
C9C2C605 |
Explanation: Unable to register synchronization object due to invalid resource parameter.
User Response: Check for an application error.
C9C2C606 |
Explanation: Invalid coordinator reference passed on is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
User Response: Check for an application error.
C9C2C607 |
Explanation: Invalid propagation context accessed in is_same_transaction, is_ancestor_transaction, is_descendant_transacation, or is_related_transaction method.
User Response: Check for an application error.
C9C2DE01 |
Explanation:
User Response:
C9C2DE02 |
Explanation:
User Response:
C9C2DE03 |
Explanation:
User Response:
C9C2DE04 |
Explanation:
User Response:
C9C2E001 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: Check to make sure you are running with enough memory for the address space issuing the failing code. Verify that for the control/server region the REGION=0M. Refer to the "WebSphere 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 contact the IBM Support Center: 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.
C9C2E002 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E003 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E004 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E101 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E202 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E203 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E204 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E301 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E303 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E304 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E305 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E306 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E307 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E308 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E309 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E30F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E310 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E311 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E312 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E313 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E314 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E315 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E316 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E317 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E318 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E401 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E402 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E403 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E404 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E405 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E406 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E407 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E408 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E409 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E40F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E410 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E411 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E412 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E413 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E414 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E415 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E416 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E417 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E418 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E419 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E41F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E420 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E421 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E422 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E423 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E424 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E425 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E426 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E427 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001. Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage. Suggested Action: See minor code C9C2E001.
C9C2E429 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E42F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E430 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E431 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E432 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E433 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E434 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E435 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E436 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E437 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E438 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E439 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E43A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E43B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E43C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E43D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E601 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E602 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E603 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E604 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E605 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E606 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E607 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E608 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E609 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E60F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E610 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E611 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E612 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E613 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E614 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E615 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E616 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E617 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E618 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E619 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61D |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61E |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E61F |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E620 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E621 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E622 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E623 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E701 |
Explanation:
User Response:
C9C2E703 |
Explanation:
User Response:
C9C2E745 |
Explanation: This was created so that a CORBA::NO_MEMORY exception could be thrown in bbolpoi.cpp This exception is thrown because there is not enough memory to allocate a buffer of the specified size. Some of the reasons might me, The value being passed in defining the size of the buffer may not have been initialized.
User Response:
C9C2E746 |
Explanation: This was created so that a CORBA::NO_MEMORY exception could be thrown in bbolpoi.cpp This exception is thrown because there is not enough memory to allocate a buffer of the specified size. Some of the reasons might me, The value being passed in defining the size of the buffer may not have been initialized.
User Response:
C9C2E801 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E802 |
Explanation: Unable to acquire storage for the start command parameters when starting a server instance.
User Response: Ensure adequate storage exists in the system management address space.
C9C2E901 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E902 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E903 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E904 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E905 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E906 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2E907 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2EA01 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2EA02 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2F201 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE01 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE02 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE03 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE04 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE05 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE06 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE07 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE08 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE09 |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE0A |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE0B |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.
C9C2FE0C |
Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage.
User Response: See minor code C9C2E001.