This section provides an explanation of the minor codes used by the Component Broker, the definition of the minor codes in hexadecimal order, and the code ranges for system exceptions. Refer to the hints and tips section on Component Broker system exceptions for additional information on system exceptions.
Each minor code begins with 0x4942, which is the OMG-assigned identification code for the Component Broker ORB. The remaining digits identify the minor code. In some cases, minor error codes may be reported without the vendor ID. Minor error codes reported from Java are in decimal and lack the vendor ID.
Minor codes
Component Broker follows the CORBA model for exception handling. In this model, all
exceptions can be associated with minor error codes. The minor error codes provide greater
detail about the errors that can occur.
Error codes are used in several ways. They are returned in the minor code field of exception bodies (when appropriate), they are placed in the activity log as part of the PrimaryMessage, and they can be written in diagnostic messages on a computer screen. There is not a one-to-one mapping of exception names to minor error codes. Rather, a minor error code can be associated with several different exceptions. This means a minor error code message can mean different things depending on which exception was thrown. See Activity log for problem determination for more information on the activity log entries.
Minor code ranges
All minor error codes in Component Broker are defined to fall within a specific numeric
range. This range is defined by the Object Management Group. Within this range, Component
Broker defines further ranges. Each Component Broker range corresponds to a specific
Component Broker component. This makes it possible to identify which component threw an
exception by reading the minor error code. While it is not necessary for developers to
know which component threw an exception to identify an error, it can be helpful.
Minor codes are scope to System Exceptions in the range from 0 to 4095 (hexadecimal 000 to FFF). A minor code must be a unique number within the scope for each System Exception, but there is no restriction that minor codes be unique across all System Exceptions.
Minor code ranges by component
Code Range Component 0000-0031 Common error codes 0032-0063 Object Request Broker (ORB) 0064-0095 Java client 0096-00C7 Server run time 00C8-00F9 Server Groups 00FA-012B Caching 012C-015D IOM 015E-018F Concurrency service 0190-01C1 Events service 01C2-01F3 Externalization service 01F4-0225 LifeCycle service 0226-0257 Naming service 0258-0289 Object Identity service 028A-02BB Query service 02BC-02ED Security service 02EE-031F Transaction service 0320-03E7 Reserved 03E8-0419 Application Adaptor Framework 041A-044B Root Application Adaptor 044C-047D Business Object Application Adaptor 047E-04AF Relational DB Instance Manager 04B0-0545 Reserved 0546-0577 Oracle Application Adaptor 0578-05A9 DB2 Application Adaptor 05A0-05DB Reserved 05DC-060D MQSeries Application Adaptor 05AA-0FFF Reserved
Note on Common Error Codes: Usually, components raise exceptions using minor codes (from their assigned range). However, a set of common error codes are provided for use by all Component Broker components. These minor codes are defined identifiers that are used to set minor code fields when returning exceptions. These messages are also defined in the RAS message catalog. These messages are used when storing errors in the logs.
Minor Code Messages
The minor code messages in this section are organized in hexadecimal order, by minor code.
Some multiple minor codes have the same hexadecimal code.
The explanation of each minor error code includes:
0x49290000 CORBAMinorCommonUnspecified
Explanation: Minor code is unspecified. No special meaning. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420001 CORBAMinorActivityLog
Explanation: Detailed exception data was placed into the Activity Log. This is
one of the common error codes which are used by all Component Broker components. It is
used to set minor code fields when returning exceptions and writing errors in the logs.
The message is also defined in the RAS message catalog.
0x49420007 CORBAMinorCommonCannotLoadCatalog
Explanation: Unable to load message catalog %s, message %d. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420008 CORBAMinorCommonCannotFindMessage
Explanation: Unable to find message %d in message catalog %s. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420009 CORBAMinorCommonSevereError
Explanation: Severe Error, data was placed in the Error Log. This is one
of the common error codes which are used by all Component Broker components. It is used to
set minor code fields when returning exceptions and writing errors in the logs. The
message is also defined in the RAS message catalog.
0x4942000A CORBAMinorCommonOutOfMemory
Explanation: Out of memory. This is one of the common error codes which
are used by all Component Broker components. It is used to set minor code fields when
returning exceptions and writing errors in the logs. The message is also defined in the
RAS message catalog.
0x4942000B CORBAMinorCommonOSException
Explanation: Received Operation System Exception %s. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x4942000C CORBAMinorCommonOSReturnCode
Explanation: Operating System call %s returned %d. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x4942000D CORBAMinorCommonThreadCreateFail
Explanation: Failure occurred when creating a thread. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x4942000E CORBAMinorCommonThreadWaitTimeout
Explanation: Failure timeout occurred when waiting on a thread. This is
one of the common error codes which are used by all Component Broker components. It is
used to set minor code fields when returning exceptions and writing errors in the logs.
The message is also defined in the RAS message catalog.
0x4942000F CORBAMinorCommonSemaphoreCreateFail
Explanation: Failure occurred when creating a semaphore. This is one of
the common error codes which are used by all Component Broker components. It is used to
set minor code fields when returning exceptions and writing errors in the logs. The
message is also defined in the RAS message catalog.
0x49420010 CORBAMinorCommonSemaphoreRequestFail
Explanation: Failure occurred when requesting a semaphore. This is one of
the common error codes which are used by all Component Broker components. It is used to
set minor code fields when returning exceptions and writing errors in the logs. The
message is also defined in the RAS message catalog.
0x49420011 CORBAMinorCommonSemaphoreReleaseFail
Explanation: Failure occurred when releasing a semaphore. This is one of
the common error codes which are used by all Component Broker components. It is used to
set minor code fields when returning exceptions and writing errors in the logs. The
message is also defined in the RAS message catalog.
0x49420012 CORBAMinorCommonSemaphorSignalFail
Explanation: Failure occurred on semaphore signal. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420013 CORBAMinorCommonSemaphoreWaitTimeout
Explanation: Failure timeout occurred when waiting on a semaphore. This
is one of the common error codes which are used by all Component Broker components. It is
used to set minor code fields when returning exceptions and writing errors in the logs.
The message is also defined in the RAS message catalog.
0x49420014 CORBAMinorCommonProgramLoadFail
Explanation: Failure occurred when loading executable %s. This is one of
the common error codes which are used by all Component Broker components. It is used to
set minor code fields when returning exceptions and writing errors in the logs. The
message is also defined in the RAS message catalog.
0x49420015 CORBAMinorCommonDLLLoadFail
Explanation: Failure occurred when loading library %s. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420016 CORBAMinorCommonHeapCreateFail
Explanation: Failure occurred when creating a heap. This is one of the
common error codes which are used by all Component Broker components. It is used to set
minor code fields when returning exceptions and writing errors in the logs. The message is
also defined in the RAS message catalog.
0x49420031 SOMDERROR_OPSYS
Explanation: An operating system error has occurred.
User Response: Check the log for more information.
0x49420032 SOMDERROR_CouldNotLoadLibrary
Explanation: Client initialization failed to load either security or work
load management library or DLL.
User Response: Check the log for more information.
0x49420033 SOMDERROR_NoMemory
Explanation: A memory allocation failed.
User Response: Increase system resources. Check if process has a memory
leak.
0x49420034 SOMDERROR_NotImplemented
Explanation: The invoked operation is not supported in the product or is
not valid on the target object.
User Response: Check that the operation being invoked and the runtime
type of the target object are compatible. Reference the documentation for the operation to
find out about any restrictions.
0x49420035 SOMDERROR_InvalidProtocolInformation
Explanation: The configuration of the communications protocol(s) is
incorrect. Supported communications protocols are TCP/IP and IPC.
User Response: Insure that at least one valid communications protocol
image was configured using the Systems Management tool (for either TCP/IP or IPC). Insure
that a host image was configured using the correct hostname. Insure that for each
communications protocol configured, the csProfileTag and portNumber are set and that the
portNumber is not in use by another process on the system. (The portNumber is the port on
which the location-service daemon listens for requests.) The "profile tag" and
"port number" settings must be unique for each communications protocol. Insure
that for each server registered in the Implementation Repository, the set of supported
communications protocols for that server intersects with the set of communications
protocol images configured using the Systems Management tool.
0x49420036 SOMDERROR_InvalidConfigSetting
Explanation: A configuration setting or environment variable has not been
properly set.
User Response: An error log entry indicates which configuration setting
or environment variable is not properly set. If the reported variable is HOSTNAME, insure
that a host image was configured using the Systems Management tool. If the reported
variable is SOMCBASE, insure that the product was properly installed (SOMCBASE should be
set during product installation to be the directory into which the product was installed.)
If the reported variable is SOMCBENV, insure that SOMCBENV has one of the following forms:
D:<image-name> S:<image-name> C:<image-name> A:<image-name> where
"D:" is used when starting the location-service daemon, "S:" is used
when starting a server process, "C:" is used when starting a client process, and
"A:" is used when starting a systems-management agent process. The
<image-name> is the name of a systems-management image. (For servers, the image name
is the same as the server alias.) For non-managed clients, the SOMCBENV environment
variable should instead be set to the name of a configuration file that contains
configuration settings for the process. The default configuration file is installed in the
"etc" subdirectory of the directory in which the product was installed, and is
named "somcbenv.ini".
0x49420036 SOMDERROR_SOMDDAlreadyRunning
Explanation: The location-service daemon cannot begin listening because
another process is already using the port number on which the daemon was configured to
listen. The most likely cause of this error is attempting to start the location-service
daemon process when another instance of the process is already running.
User Response: Do not attempt to start the location-service daemon, or
terminate the other instance. If no other location-service daemon is running, try
reconfiguring the location-service daemon to listen on a different port number. (Each
communications protocol is configured with a separate port number using the Systems
Management tool.)
0x49420038 SOMDERROR_HostAddress
Explanation: A failure to map a hostname (of a different machine) to a
host address.
User Response: Ensure that the host with which this process is attempting
to communicate is known and can be reached via TCP/IP. For example, try to ping
the remote host by hostname.
0x49420039 SOMDERROR_CouldNotStartProcess
Explanation: The location daemon could not start a server process.
User Response: Check the log for more information.
0x4942003A SOMDERROR_CouldNotStartThread
Explanation: A thread could not be started.
User Response: Check the log for more information. Increase system
resources.
0x4942003B SOMDERROR_NoMessages
Explanation: No request messages are pending in a server process when the
server invoked CORBA::BOA::execute_next_request or CORBA::BOA::execute_request_loop with
the CORBA::BOA::SOMD_NO_WAIT flag.
User Response: Wait for a request to become available, or use the
CORBA::BOA::SOMD_WAIT flag when calling CORBA::BOA::execute_next_request or
CORBA::BOA::execute_request_loop.
0x4942003C SOMDERROR_MarshalingError
Explanation: An error has occurred when trying to marshall or demarshall
method parameters or return results as part of a remote invocation. This occurs, for
example, if the process attempts to pass a IOM proxy as a method parameter or return
result (only objects that inherit from CORBA::Object_ORBProxy can be passed on
cross-process invocations). This error can also occur when demarshalling an inout
sequence, if the length of the incoming sequence is greater than the original sequence
maximum. This error can also occur when using the Dynamic Skeleton Interface (DSI), if
methods are not invoked on the ServerRequest object in the correct order.
User Response: Ensure that IOM proxies are not passed as method
parameters or return results. Ensure that inout sequences do not grow beyond the maximum
of the sequence. If using the DSI, ensure that operations are invoked on the ServerRequest
object in the correct order.
0x4942003D SOMDERROR_CommTimeOut
Explanation: A process has timed out waiting for a response from another
process.
User Response: Ensure that the other process is still active. (Typically
a client receives this error when the server has terminated or hung due to an application
error.) To increase the timeout period, change the "request timeout" setting for
the process using Systems Management. (The default setting is 30 seconds.) Setting
"request timeout" to zero results in an infinite timeout.
0x4942003E SOMDERROR_CannotConnect
Explanation: A client process was unable to connect to a server process
when attempting to invoke a method on a proxy to an object residing in that server
process.
User Response: Ensure that the location-service daemon is running on the
machine on which the server resides. Ensure that the object reference is still valid.
Ensure that the two machines are connected (for instance, try to ping the remote
machine).
0x4942003F SOMDERROR_No_Server_Available
Explanation: A client has invoked a method on a proxy to an object
residing in a server group, but no server in the server group is currently available or
the server group cannot be reached.
Either a method call was made on a server group aware object, but the server group has no
servers configured in it or a method call was made on a server group aware object for
which there is at least one server configured, but none of the servers that are available
were selected by the configured bind policies.
User Response: Configure at least one server into the server group if the
server group has not servers configured in it. If the server group has at least one server
configured, then investigate the possibility that the configured bind policies are
deselecting all the available servers. This may be the correct behavior in this particular
situation or the bind policy may need to be modified.
Alternatively, there may be a problem communicating with one or of the servers so check
that the servers in the server group are running and that communication is possible
between the client or server that raised this error and the servers in the server group
and then shut down and restart the client or server that raised this error and/or
re-initialize the application that hit the error. Alternatively, catch the error and retry
the method call repeatedly until a server becomes available, but consider the possibility
of a permanent server failure or communications failure.
0x49420040 SOMDERROR_BadObjref
Explanation: An invalid object reference was used. For example, this
error is sent from a server to a client if the server receives a reference to an object
that no longer exists or cannot be located in that server. This error can occur in a
client process if an invalid string is passed to CORBA::ORB::string_to_object. This error
occurs in a server if CORBA::BOA::create is called with input ReferenceData that doesn't
map to any known exportable object residing in that server. The error also occurs if
CORBA::BOA::get_id is invoked on a nil object reference or on an object reference that has
no associated ReferenceData in that server. The error also occurs if a server attempts to
export an object reference that has no associated ReferenceData in that server, or if a
non-server attempts to pass a local object as a parameter on a remote method invocation.
(A "non-server" is any process that has not yet called
CORBA::BOA::impl_is_ready.)
User Response: In a client process, insure that the object to which the
object reference refers still exists. Insure that strings passed to
CORBA::ORB::string_to_object have not been corrupted or truncated. (There is no maximum
length for an object reference string; some are larger than others.) Insure that servers
don't attempt to export objects that aren't handled by the application adaptor of the
server. Also, IOM proxies cannot be exported from a server.
0x49420041 SOMDERROR_Unknown
Explanation: An unexpected error occurred during an operation.
User Response: Report the occurrence to technical support.
0x49420042 SOMDERROR_CommunicationsError
Explanation: A communications failure occurred. For example, a process
could have received an unknown or unexpected message type or message content, the process
could have encountered a low-level communications failure in attempting to send a message
or binding to a socket, or an unexpected broken connection could have occurred.
User Response: Ensure that communications resources are functioning
properly. For instance, when using TCP/IP, try to ping the remote host. Ensure
that the process with which this process is trying to communicate has not failed due to an
application error.
0x49420043 SOMDERROR_ImplRepIO
Explanation: The Implementation Repository database cannot be accessed.
User Response: Ensure that the Implementation Repository was correctly
created and configured using the Systems Management tool. Each host machine must have its
own Implementation Repository.
0x49420044 SOMDERROR_EntryNotFound
Explanation: An entry in the Implementation Repository was not found when
attempting to delete, update, or find it.
User Response: Insure that the specified server alias or UUID matches a
server that was previously registered in the Implementation Repository.
0x49420045 SOMDERROR_ClassNotFound
Explanation: Conversion of an IOR to an object failed because the class
name was unknown or it's proxy factory cannot be created.
User Response: Verify the class implementation and its bindings exist.
0x49420046 SOMDERROR_ServerAlreadyExists
Explanation: A server was unable to register with the location-service
daemon during CORBA::BOA::impl_is_ready. This is typically caused by another server
already being registered with the location-service daemon under the given server UUID.
(Only one instance of a particular server can be running on a given host at once.)
User Response: Terminate the duplicate server process. If no duplicate
server process is running, restart the location-service daemon.
0x49420047 SOMDERROR_CtxNoPropFound
Explanation: A specified CORBA::Context property was not found. For
example, if an invalid property name was passed to CORBA::Context::delete_values, this
error occurs.
User Response: Ensure that the specified property name exists in the
Context object.
0x49420048 SOMDERROR_BadParm
Explanation: An application supplied an invalid parameter to an
operation.
User Response: The error log should contain a message indicating which
operation was given the invalid parameter. Consult the documentation for that operation
and insure that the parameters passed to it are valid.
0x49420049 SOMDERROR_AuthnFail
Explanation: An application attempted to manipulate an entry in the
Implementation Repository for a server that is either being managed or disabled by the
Systems Management tool. (Such entries in the Implementation Repository cannot be deleted
or updated using the ImplRepository programmatic interface. Only entries registered using
the ImplRepository interface can be updated or deleted using the ImplRepository
interface.) This error is also raised if CORBA::ImplRepository::find_impldef is used to
find a server that was disabled by Systems Management.
User Response: Use the Systems Management tool to manipulate the server.
Insure that the server has not been disabled by the Systems Management tool. Insure that
all entries in the Implementation Repository to be updated or deleted programmatically
were originally added programmatically (rather than via the Systems Management tool).
0x4942004A SOMDERROR_DuplicateEntry
Explanation: The application attempted to add a duplicate entry to the
Implementation Repository, or attempted to update the server alias of an existing entry
using a name that is not unique.
User Response: Ensure that the server UUID and server alias of the
ImplementationDef to be added or updated in the Implementation Repository are unique. (The
server alias need not be unique throughout the network but must be unique in each
Implementation Repository.)
0x4942004B SOMDERROR_Internal
Explanation: Unknown.
User Response: Report the occurrence to technical support.
0x4942004D SOMDERROR_WrongRefType
Explanation: An object reference of the wrong type was used. The most
common reason for this error to occur is if a client invokes an operation on an object in
a server and the object does not support the invoked method. (To support a given
operation, a server must have been compiled and linked with the server-side C++ bindings
for the interface that introduces that IDL operation.) Another situation in which this
error can occur is if a server application invokes CORBA::BOA::get_id and passed in a
proxy object (rather than a local object).
User Response: Ensure that a server is compiled and linked with all the
server-side C++ bindings for the interfaces it exports. Ensure that a server does not pass
a proxy object to CORBA::BOA::get_id.
0x4942004E SOMDERROR_SOMDDNotRunning
Explanation: A server was unable to register with the location-service
daemon (in CORBA::BOA::impl_is_ready), because it was unable to contact the daemon. This
is usually a result of the daemon not running or the daemon running on a different port
number than the server expects.
User Response: Ensure that the location-service daemon is running on the
same host as the server. Ensure that the port number configuration setting for each
communications protocol is the same for the systems-management server image and daemon
image.
0x49420051 SOMDERROR_DataConversion
Explanation: Failure to perform code-set translation of character data
occurred. This could result from a failure of the XPG4 functions iconv() or nl_langinfo().
It can occur if the process is using a non-standard XPG4 code set that does not map to an
OSF code set. It can occur if the native code set for the process (as reported by the XPG4
function nl_langinfo) does not match the nativeCharSet configuration data of the process
(configured using the Systems Management tool). It can occur if a server does not have
XPG4 code set converters for the transmission code set chosen by the client process. It
can occur if the "char code sets" configuration setting for the server contains
one or more code sets for which the process cannot open (using iconv_open) XPG4
converters. It can occur in a client process when attempting to communicate with a server
if there is no common code set between the client and the server.
User Response: Ensure that, when using the translationEnabled
configuration setting, that the other NLS-related configuration settings have been set
correctly. Also ensure that the correct XPG4 code-set converters have been installed and
that all environment variables (such as LOCPATH) required by XPG4 have been set properly.
Ensure that both client and server are using standard code sets (recognized by both XPG4
and OSF) and that there is some code set supported by both the client and the server.
0x49420052 SOMDERROR_IRIncoherent
Explanation: An Interface Repository object references another named
Interface Repository object which no longer resides in the IR database.
User Response: Call your IBM customer support center and report the
problem.
0x49420053 SOMDERROR_IRInternal
Explanation: An internal programming or database error has occurred.
User Response: Call your IBM customer support center and report the
problem.
0x49420054 SOMDERROR_IRDuplicateEntry
Explanation: An attempt was made to create an Interface Repository object
and one already exists in the Interface Repository with either the same
CORBA::RepositoryId or the same name within that container.
User Response: Change the "id" (CORBA::RepositoryId) parameter
that is passed to the 'create_xxxx' operation, or change the "id"
(CORBA::RepositoryId) value of the object already in the IR which is causing the duplicate
entry error via the "id" write operation, or change the name of one of the two
conflicting objects within that container.
0x49420055 SOMDERROR_IREntryNotFound
Explanation: A "create_xxxx" operation determined that one of
the input parameters referenced an Interface Repository object which was not found in the
database.
User Response: Specify a named object that does exist in the Interface
Repository database.
0x49420056 SOMDERROR_IRCannotConnect
Explanation: The Interface Repository database could not be found or
accessed properly. If this error is thrown, it occurs during a call to
"resolve_initial_references" (with an input string of
"InterfaceRepository").
User Response: Ensure that the Interface Repository database exists and
is configured properly. Ensure that the directory/file permissions associated with the
Interface Repository database allow access by the user receiving the exception.
0x49420057 SOMDERROR_IRInUse
Explanation: Another thread or process is already updating that portion
of the Interface Repository database.
User Response: Retry the Interface Repository operation that generated
the exception at a later time.
0x4942009C SRThreadManagerUnknownError
Explanation: An unexpected exception has occurred during an operation
involving the thread manager.
User Response: Check the activity and error logs for more information and
report the occurrence to technical support.
0x4942009D SRContextCoordinator_IExpCControlError
Explanation: An IBM Class Library Exception, IException, was caught
during an operation.
User Response: Report the occurrence to technical support.
0x4942009E SRContextCoordinator_UnknownCControlError
Explanation: An unknown exception was caught during an operation.
User Response: Report the occurrence to technical support.
0x4942009F SRContextCoordinator_InternalError
Explanation: An internal error has occurred during an operation.
User Response: Report the occurrence to technical support.
0x494200A0 SRThreadManagerSafeExecuteError
Explanation: An uncaught exception was caught while processing user code.
This exception could be an Operating System exception. This can also occur if user code
throws an improperly defined CORBA user exception.
User Response: Check the activity log for more information. There will
usually be another log entry providing the object and method name associated with the
CORBA request which caused this error. Check the user code to see that any Operating
System exceptions are indeed caught. Also check the .idl file to see that any CORBA
exceptions thrown in the user code are defined.
0x494200A1 SRSaoMOInvalidStateException
Explanation: The Server Administration Object (SAO) Managed Object (MO)
encountered an invalid state.
User Response: Report the occurrence to technical support.
0x494200A2 SRSaoMO_UNKNOWN_PASSIVATE
Explanation: The Server Administration Object (SAO) Managed Object (MO)
encountered an unknown exception during the processing of its uninitForDestruction method.
User Response: Report the occurrence to technical support.
0x494200A3 SRSao_UNKNOWN_Exception
Explanation: The Server Administration Object (SAO) Managed Object (MO)
encountered an unknown exception during an operation.
User Response: Report the occurrence to technical support.
0x494200A4 SRSao_UNKNOWN_RegisteredObject
Explanation: The Object Registry received an IBM Class Library Exception,
IException, during an operation.
User Response: Report the occurrence to technical support.
0x494200A7 SRSao_ICDSDO_Exception
Explanation: An exception was caught during an operation which was
working with the CDS.
User Response: Report the occurrence to technical support.
0x494200A8 SRReqInterceptor_UnknownError
Explanation: An unknown exception was caught during the processing of the
server's request interceptor.
User Response: Report the occurrence to technical support.
0x494200C8 SOMSG::CorruptServiceContext
Explanation: A server groups service context was corrupted.
User Response: Check for other symptoms of a transmission error. Gather
information about the problem and follow your local procedures for reporting problems.
0x494200C8 SOMSG::MCIncompleteConfig
Explanation: The server groups code has failed to find some of its data
in the Common Data Store.
User Response: Delete and reinstate the configuration using the Systems
Management User Interface.
0x494200C8 SOMSG::MCNCRootNotFound
Explanation: The server groups code has failed to find the root naming
context of the name tree.
User Response: Check for other symptoms of a naming service error, then
gather information about the problem and report the occurrence to technical support.
0x494200C8 SOMSG::MCStateInvalid
Explanation: The server groups code has detected an invalid state in the
Common Data Store.
User Response: Delete and reinstate the configuration using the Systems
Management User Interface.
0x494200C8 SOMSG::NoServerDefined
Explanation: A method call was made on a server group aware object, but
the server group has no servers configured in it.
User Response: Configure at least one server into the server group.
0x494200C8 SOMSG::ObjrefAddFailure
Explanation: The server groups code has failed to add a server object
reference into an internal collection, possibly because of a shortage of memory.
User Response: Increase the amount of memory available and retry.
0x494200C8 SOMSG::RebindMinorCode
Explanation: A server that is a member of a server group has detected
that the client needs to refresh its copy of certain configuration information relating to
the server group.
User Response: No action is required as this minor code is used in normal
processing.
0x494200C9 SOMSG::MCNSNotAvailable
Explanation: The server groups code has detected an unexpected error when
using the naming service.
User Response: Check for other symptoms of a naming service error, then
gather information about the problem and report the occurrence to technical support.
0x494200C9 SOMSG::MCServerNotMember
Explanation: A server has attempted to register or deregister as a member
of a server group, but the server is not configured as a member of the server group.
User Response: Check the configuration to ensure that the server is not a
member of the server group. Try stopping the server and restarting it. If the error still
occurs, gather information about the problem and follow your local procedures for
reporting problems.
0x494200C9 SOMSG::NoServerAvailable
Explanation: A method call was made on a server group aware object for
which there is at least one server configured, but none of the servers that are available
were selected by the configured bind policies.
User Response: Investigate the possibility that the configured bind
policies are deselecting all the available servers. This may be the correct behavior in
this particular situation or the bind policy may need to be modified. Alternatively, there
may be a problem communicating with one or of the servers so check that the servers in the
server group are running and that communication is possible between the client or server
that raised this error and the servers in the server group and then shut down and restart
the client or server that raised this error and/or re-initialize the application that hit
the error. Alternatively, catch the error and retry the method call repeatedly until a
server becomes available, but consider the possibility of a permanent server failure or
communications failure.
0x494200CA SOMSG::MCCDSError
Explanation: The server groups code has detected an unexpected error
while accessing the Common Data Store.
User Response: Delete and reinstate the configuration using the Systems
Management User Interface.
0x494200CA SOMSG::UnknownServer
Explanation: The object request broker has attempted to send a request on
a server group aware object to a particular server but the request has failed and the
server groups code no longer recognizes the server as a member of the server group in
spite of the fact that it was the server groups code that selected the server from the
members of the server group.
User Response: Gather information about the problem and follow your local
procedures for reporting problems.
0x494200CB SOMSG::MCInvalidUse
Explanation: An unimplemented method in an internal server groups object
was called.
User Response: Check that you are not making calls to internal server
groups objects. If not, then gather information about the problem and follow your local
procedures for reporting problems.
0x494200F9 SOMGWDefs::GatewayNotImplemented
Explanation: A non-server group enabled client has attempted to make a
method call on a server group aware object. The method call was sent to the server group
gateway server and was rejected since the gateway server is not yet implemented to forward
requests to the server group.
User Response: A non-server group enabled client has attempted to make a
method call on a server group aware object. The method call was sent to the server group
gateway server and was rejected since the gateway server is not yet implemented to forward
requests to the server group.
0x494200FA ICACHE_BAD_INV_ORDER_KEYINIT
Explanation: Key not set prior to cache operation.
User Response: Check the DO implementation code and report problem to
technical support.
0x494200FA ICACHE_BAD_PARAM_INVATTR
Explanation: An invalid attribute name was passed on a DAO (Data Access
Object) call.
User Response: Make sure that the data object DLL and the system
management DDL are consistent.
0x494200FA ICACHE_INTERNAL_CACHNTRY
Explanation: A set to get attribute value was called from a cache entry
which is to be deleted.
User Response: Check the error log for more information.
0x494200FA ICACHE_NO_IMPLEMENT_DATATYPE
Explanation: A database attribute type not implemented by the cache
component was encountered in processing a DAO (Data Access Object) call.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x494200FA ICACHE_UNKNOWN_DATATYPE
Explanation: A database attribute type not implemented by the cache
component was encountered in processing a DAO (Data Access Object) call.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x494200FA NO_MEMORY_DAO
Explanation: The cache component is unable to acquire memory.
User Response: Increase the amount of virtual memory on the server system
or reduce the number of other tasks running on the server system.
0x494200FB ICACHE_BAD_INV_ORDER_CACHEMGRINIT
Explanation: Application server internal error.
User Response: Check the installation of Component Broker and report
problem to technical support.
0x494200FB ICACHE_BAD_PARAM_INCOMPTYPE
Explanation: The CORBA typecode used on a DAO call is inconsistent with
the database attribute type.
User Response: Make sure that the data object DLL and the system
management DDL are consistent with each other, and are also consistent with the table
definition in the relational database.
0x494200FB ICACHE_INTERNAL_CACHEMGR
Explanation: A program error occurred in the cache component.
User Response: Report the occurrence to technical support.
0x494200FC ICACHE_BAD_PARAM_KEYATTR
Explanation: The key attribute name was passed on a setValue DAO call.
User Response: Make sure that the data object DLL and the system
management DDL are consistent and correct.
0x494200FC ICACHE_BAD_INV_ORDER_NODBCOMM
Explanation: Cache internal error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x494200FC ICACHE_INTERNAL_AIXDAO
Explanation: A program error occurred in the cache component.
User Response: Report the occurrence to technical support.
0x494200FD ICACHE_BAD_INV_ORDER_NOMAP
Explanation: Map metadata not set prior to cache operation.
User Response: Check the DO implementation code and report problem to
technical support.
0x494200FD ICACHE_BAD_PARAM_INVMAP
Explanation: An invalid map name was passed on a DAO call.
User Response: Make sure that the data object DLL and the system
management DDL are consistent and correct.
0x494200FD ICACHE_INTERNAL_HASH
Explanation: A program error occurred in the cache component.
User Response: Report the occurrence to technical support.
0x494200FE ICACHE_BAD_PARAM_NONKEYATTR
Explanation: A non key attribute was passed on a set key operation.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x494200FE ICACHE_INTERNAL_CACHE
Explanation: A program error occurred in the cache component.
User Response: Report the occurrence to technical support.
0x494200FF ICACHE_BAD_PARAM_SMALLBUF
Explanation: An insufficient buffer size was provided in a getValue DAO
call to retrieve a database attribute of the DATE/TIME/TIMESTAMP type.
User Response: Make sure that the data object DLL and the system
management DDL are consistent and correct.
0x494200FF ICACHE_INTERNAL_GLOBAL_CACHE
Explanation: A program error occurred in the cache component.
User Response: Report the occurrence to technical support.
0x494200100 ICACHE_BAD_PARAM_UNEQUALBUF
Explanation: An incorrect size string was provided in a setValue DAO call
to modify a database attribute of the DATE/TIME/TIMESTAMP type.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x494200100 ICACHE_INTERNAL_SQLACCESS
Explanation: A program error occurred in the cache component.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420101 ICACHE_BAD_PARAM_NOTEXTRACT
Explanation: A string value from ::CORBA::Any that was passed in a
getValue DAO call failed to be extracted.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x49420101 ICACHE_INTERNAL_SQLERROR
Explanation: A system error occurred in the cache component when:
User Response: Check the error log for more information.
0x49420102 ICACHE_BAD_PARAM_INVDATATYPE
Explanation: Make sure that the data object implementation is correct and
consistent with the system management DDL.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x49420102 ICACHE_INTERNAL_SQLERROR_CONNECT
Explanation: The cache component failed to establish a database
connection.
User Response: Check the error log for more information.
0x49420103 ICACHE_BAD_PARAM_LARGEANYSTR
Explanation: The string buffer passed in the ::CORBA::Any on a setValue
DAO call was larger than the database attribute to be modified.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x49420103 ICACHE_INTERNAL_NOPREFEC
Explanation: A program error occurred in the cache component.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420104 ICACHE_BAD_PARAM_WRONGNUMKEYATTRS
Explanation: The wrong number of key attributes were passed on a DAO
setKeyAttributes or reactivateFromData call.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x49420104 ICACHE_INTERNAL_FKREL
Explanation: A program error occurred in the cache component.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420105 ICACHE_BAD_PARAM_LARGEANYBINARY
Explanation: The binary buffer passed in the ::CORBA::Any on a setValue
DAO call is larger than the database attribute to be modified.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl.
0x49420105 ICACHE_INTERNAL_BUILDDAOS
Explanation: Internal error. Cache unable to allocate a DAO object.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420106 ICACHE_BAD_PARAM_INVINTERFACE
Explanation: An invalid map name was passed on a DAO call.
User Response: Make sure that the data object implementation is correct
and consistent with the system management ddl. Verify that the metadata is consistent with
the database.
0x49420106 ICACHE_INTERNAL_PREFETCH
Explanation: A program error occurred in the cache component.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420107 ICACHE_BAD_PARAM_INVFKRELID
Explanation: Invalid relationship identifier.
User Response: Check the DO implementation code and report problem to
technical support.
0x49420108 ICACHE_BAD_PARAM_INVPARENTFKRELID
Explanation: Invalid relationship identifier.
User Response: Check the DO implementation code and report problem to
technical support.
0x49420109 ICACHE_BAD_PARAM_INVCHILDFKRELID
Explanation: Invalid relationship identifier.
User Response: Check the DO implementation code and report problem to
technical support.
0x4942010A ICACHE_BAD_PARAM_INVCHILDKEY
Explanation: Invalid key on cache operation.
User Response: Check the DO implementation code and report problem to
technical support.
0x4942010A ICACHE_BAD_PARAM_INVOVERFLOW
Explanation: An invalid data value was passed to cache service from Data
Object.
User Response: If the object attribute maps to a decimal datatype in the
database, either the value passed was invalid, or it overflowed the field in the database
record.
0x4942010B ICACHE_BAD_PARAM_INVCURSOR
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x4942010C ICACHE_BAD_PARAM_INVCURSOROP
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x4942010D ICACHE_BAD_PARAM_EMPTYCOLL
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x4942010E ICACHE_BAD_PARAM_BEGINCOLL
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x4942010F ICACHE_BAD_PARAM_ENDCOLL
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x49420120 ICACHE_BAD_PARAM_BETWEENELEM
Explanation: Internal cache error.
User Response: Check the error log for more information and report the
occurrence to technical support.
0x4942012C SOMERROR_NULL_CHARACTER_IN_STRING
Explanation: A CORBA string or wstring value contained a NULL character.
Used as a minor code for the DATA_CONVERSION exception.
User Response: Ensure that CORBA string and wstring values do not contain
NULL characters
0x4942012D SOMERROR_CHARACTER_OUT_OF_RANGE
Explanation: A CORBA string contained a non-ASCII character (a character
whose ordinal value was greater than 255). Used as a minor code for the DATA_CONVERSION
exception.
User Response:Ensure that CORBA string values do not contain non-ASCII
characters. This problem usually arises in Java, since Java strings can contain non-ASCII
characters.
0x4942012E SOMERROR_STRING_TOO_LONG
Explanation: A string containing too many characters was passed for a
CORBA string or wstring argument that was declared with a bounded length. Used as a minor
code for the MARSHAL exception.
User Response: Ensure that the length of strings passed does not exceed
the maximum length for the string declared in IDL.
0x4942012F SOMERROR_STRING_IS_NULL
Explanation: A null was passed where a CORBA string or wstring value was
expected. Used as a minor code for the DATA_CONVERSION exception.
User Response: Ensure that your program does not pass null for CORBA
string or wstring arguments. An empty string must be passed instead.
0x49420130 SOMERROR_CDS_ERROR
Explanation: Not currently used.
User Response: None.
0x49420131 SOMERROR_IMPL_NOT_IN_DLL
Explanation: Not currently used.
User Response: None.
0x49420132 SOMERROR_DLL_NOT_LOADED
Explanation: Not currently used.
User Response: None.
0x49420133 SOMERROR_JAVA_CLASS_NOT_LOADED
Explanation: A Java class could not be located or loaded. Used as a minor
code for OBJECT_NOT_EXIST.
User Response: Consult the activity log for a message containing the name
of the Java class that couldn't be loaded and ensure that it exists in CLASSPATH and can
be loaded.
0x49420134 SOMERROR_INTERFACE_NOT_FOUND
Explanation: A CORBA interface could not be located by IOM. Used as a
minor code for OBJECT_NOT_EXIST.
User Response: Consult the activity log the a message containing the name
of the interface that couldn't be found. Ensure that an implementation exists for the
requested interface.
0x49420135 SOMERROR_MESSAGE_NOT_UNDERSTOOD
Explanation: A CORBA operation could not be located by IOM. Used as a
minor code for OBJECT_NOT_EXIST.
User Response: Try rebuilding your object implementation (C++ DLL or Java
class). If the problem persists contact Component Broker support.
0x49420136 SOMERROR_CLASS_NOT_LOCALONLY
Explanation: An attempt was made to call _create on a C++ implementation
that had not been compiled as "localonly". Used as a minor code for
OBJECT_NOT_EXIST.
User Response: Ensure that the IDL file has a "#pragma meta X
localonly" statement for the interface or that idlc was run with the
"-mlocalonly" option.
0x49420137 SOMERROR_JAVAVM_DLL_NOT_FOUND
Explanation: IOM was unable to load the DLL containing the Java Virtual
Machine. Used as a minor code for OBJECT_NOT_EXIST.
User Response: Consult the activity log for a message containing the name
of the DLL containing the Java Virtual Machine (tagged with the text
"loadAndInitVM"). Ensure that the VM DLL name is correct (should be
"javai.dll"), that a directory containing that DLL ($JAVA_HOME\bin for NT,
$JAVA_HOME/lib/aix/native_threads for AIX) is in PATH (for NT) or LIBPATH (for AIX), and
that the DLL can be loaded. Also ensure that the JDK is at the level that Component Broker
requires.
0x49420138 SOMERROR_JAVAVM_NOT_JNI_ENABLED
Explanation: The Java Virtual Machine that IOM loaded does not support
the Java Native Interface. Used as a minor code with OBJECT_NOT_EXIST.
User Response: Ensure that the you have installed the Java JDK at the
level required by Component Broker and that the $JAVA_HOME\bin (for NT) or
$JAVA_HOME/lib/aix/native_threads (for AIX) directory appears in your PATH (for NT) or
LIBPATH (for AIX) before any other JDK.
0x49420139 SOMERROR_JAVA_REFLECTION_FAILED
Explanation: IOM was unable to use the Java Reflection API to obtain the
list of methods implemented by a Java class. Used as a minor code for OBJECT_NOT_EXIST.
User Response: Ensure that your JDK is correctly installed as described
above and that your Java implementation .class files will load without error. Contact
Component Broker support if the problem persists.
0x4942013A SOMERROR_JAVA_HELPER_NOT_LOADED
Explanation: IOM was unable to load the Helper class for a Java
implementation. Used as a minor code for OBJECT_NOT_EXIST.
User Response: Consult the activity log for a message containing the name
of the helper class that couldn't be found. Ensure that the Helper .class exists and is
reachable from CLASSPATH.
0x4942013B SOMERROR_JAVAVM_NOT_STARTED
Explanation: The JNI_CreateJavaVM call on the installed JDK did not
complete successfully. This means that IOM was unable to initialize the Java Virtual
Machine. Used as a minor code for OBJECT_NOT_EXIST.
User Response: Ensure that the you have installed the Java JDK at the
level required by Component Broker and that it initializes correctly (try running
"java java.lang.String". You should get an error for "main is not
defined". Any other result is incorrect).
0x4942013C SOMERROR_THREAD_ATTACH
Explanation: The JNI_AttachCurrentThread call on the installed JDK did
not complete successfully. This means that IOM was unable to bind to the Java Virtual
Machine. Used as a minor code for OBJECT_NOT_EXIST.
User Response: Ensure that the you have installed the Java JDK at the
level required by Component Broker and that it initializes correctly (try running
"java java.lang.String". You should get an error for "main is not
defined". Any other result is incorrect).
0x494201C3 EXERR_FLOATINGPOINTOVERFLOW
Explanation: The conversion from IEEE Double to MVS Double resulted in an
exponent outside the range of valid exponents.
User Response: Restrict usage of floating point values to those supported
by both IEEE Double and MVS Double.
0x494201C3 EXERR_INVALIDSTREAMIOBUFFERRESETPARM
Explanation: The StreamIO buffer reset param was invalid.
User Response: Internal error, contact IBM support.
0x494201C3 EXERR_UNSUPPORTEDCODEPAGE
Explanation: Either the source or destination code page, or both, as
given in the StreamIO header, is NULL. This minor code could also indicate that the
compiler's support for codeset id conversion has failed.
User Response: Ensure that the code page(s) are valid, non-NULL, and that
your compiler supports the codeset id conversion.
0x494201C4 EXERR_FLOATINGPOINTNOTCONFIGURED
Explanation: The conversion between MVS/IEEE Floats or Doubles was unable
to occur because the sourceFloatingPointFormatID and the destinationFloatingPointFormatID
did not match one of the supported formats.
User Response: Internal error, contact IBM support.
0x494201C4 EXERR_INVALIDSTREAMFORMAT
Explanation: The stioFormat of the
IStreamLocalObjectIBMImpl_StreamIO_Impl header was expected to be (Octet)
IExtendedStream::IBM, but was not.
User Response: Internal error, contact IBM support.
0x494201C5 EXERR_CODEPAGENOTCONFIGURED
Explanation: Either the source or destination code page, or both, as
given in the StreamIO header, is an Undefined code page.
User Response: Ensure that the code page(s) are defined and available on
the machine.
0x494201C5 EXERR_INVALIDENDIANFORMAT
Explanation: The StreamIO buffer header contained an invalid endianFormat
value.
User Response: Acceptable values are:
This is most likely caused by an internal error. Contact IBM support.
0x494201C6 EXERR_ENDIANNOTCONFIGURED
Explanation: The Endian format ID's of the StreamIO's were invalid.
User Response: Ensure that both source and destinationEndianFormatID's
are either BigEndian or LittleEndian. This is most likely caused by an IBM internal error.
Contact IBM support.
0x494201C6 EXERR_INVALIDFLOATINGPOINTFORMAT
Explanation: The Stream IO header indicated an invalid floating point
format.
User Response: Acceptable values are IEEE754 and MVS. This is most likely
caused by an IBM internal error. Contact IBM support.
0x494201C7 EXERR_FLOATINGPOINTUNDERFLOW
Explanation: The conversion from IEEE Double to MVS Double resulted in an
exponent outside the range of valid exponents.
User Response: Restrict usage of floating point values to those supported
by both IEEE Double and MVS Double.
0x494201C7 EXERR_STRINGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201C8 EXERR_CHARNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201C8 EXERR_ICONVCALLFAILED
Explanation: Code page conversion of aString failed.
User Response: Verify string contains valid characters for the target
code page.
0x494201C9 EXERR_OCTETNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CA EXERR_UNSIGNEDLONGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CB EXERR_UNSIGNEDSHORTNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CC EXERR_LONGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CD EXERR_SHORTNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CE EXERR_FLOATNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201CF EXERR_DOUBLENOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201D0 EXERR_BOOLEANNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201D1 EXERR_OBJECTNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201D2 EXERR_INVALIDBOOLEANVALUEFOUND
Explanation: The value of a boolean was neither recognized as
((CORBA::Boolean) 0), nor ((CORBA::Boolean) 1).
User Response: Check the object being read/written.
0x494201D9 EXERR_READPASSEDENDOFSTREAM
Explanation: The number of bytes requested to be read from the
stioBufferSeq exceeds the number of bytes left in the stioBufferSeq.
User Response: Check that the order and number of reads/writes in
internalize/externalize is correct.
0x494201E5 EXERR_WSTRINGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201E6 EXERR_WCHARNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201E7 EXERR_LONGLONGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201E8 EXERR_UNSIGNEDLONGLONGNOTFOUND
Explanation: The tag read from the stream did not match the expected data
type.
User Response: Check that the order of reads/writes in
internalize/externalize is correct.
0x494201F5 LCERR_UNKNOWN_SEE_EVENT_LOG
Explanation: LifeCycle made an invocation which resulted in an exception
being thrown by another component.
User Response: Examine activity log entries prior to this to see if
another exception was logged. Exception is CORBA::UNKNOWN.
0x494201F6 LCERR_SCOPE_MAN_ALREADY_INITIALIZED
Explanation: An undocumented internal method was invoked. Results will be
unpredictable.
User Response: Do not invoke any non-documented methods. Exception is
ILifeCycleLocalObjectImpl::AlreadyInitialized.
0x494201F7 LCERR_SCOPE_STRING_IS_NULL
Explanation: The Scope parameter, or the Scope constructed from the
ScopeString parameter,
contains a NULL element.
User Response: Reconstruct the scope parameter so that elements are
either specified or
left to the defaults. Note that in a ScopeString, any element not explicitly specified in
the string is given a default value as follows:
It is the user's responsibility to ensure that the combination of specified elements and supplied defaults is valid. Exception is CORBA::BAD_PARAM.
0x494201F8 LCERR_FAC_FIND_ALREADY_INITIALIZED
Explanation: An undocumented internal method was invoked. Results will be
unpredictable.
User Response: Do not invoke any non-documented methods. Exception is
ILifeCycleLocalObjectImpl::AlreadyInitialized.
0x494201F9 LCERR_FAC_FIND_LOCATION_IS_NULL
Explanation: An internal method was invoked illegally and with a null
parameter. Results will be unpredictable.
User Response: Do not invoke any non-documented methods. Exception is
CORBA::BAD_PARAM.
0x494201FA LCERR_SCOPE_ELEMENT_NOT_RECOGNIZED
Explanation: The ScopeString parameter contains an element other than
cell, workgroup, host, server, container, or home.
User Response: Remove the invalid element from the ScopeString. Exception
is IExtendeLifeCycle::UnrecognizedScopeElement.
0x494201FB LCERR_FAC_FIND_INVALID_KEY
Explanation: The key used to find the factory is invalid.
User Response: Check that the key used in the find factory operation is
correct. Exception is CosLifeCycle::NoFactory.
0x494201FC LCERR_FACTORY_NOT_FOUND
Explanation: The factory is not registered.
User Response: Check that the key used in the find factory operation is
correct. Try using a factory_finder with a less restrictive scope. Verify that the
registration of the expected factories did not result in any errors. Exception is
CosLifeCycle::NoFactory.
0x494201FD LCERR_SINGLE_LOC_ALREADY_INITIALIZED
Explanation: An undocumented internal method was invoked. Results will be
unpredictable.
User Response: Do not invoke any non-documented methods. Exception is
ILifeCycleLocalObjectImpl::AlreadyInitialized.
0x494201FE LCERR_MO_REGISTRATION_REQUEST_FAILED
Explanation: The FactoryRepository failed to complete all or some part of
the requested operation. Probable cause is a failure in the naming component.
User Response: Check the event log for additional information. Exception
is ILifeCycleRepositoryAdmin::RequestFailed.
0x494201FF LCERR_MO_UNREGISTRATION_REQUEST_FAILED
Explanation: The FactoryRepository failed to complete all or some part of
the requested operation. Probable cause is a failure in the naming component.
User Response: Check the event log for additional information. Exception
is ILifeCycleRepositoryAdmin::RequestFailed.
0x49420200 LCERR_SERVER_BRANCH_UNRETRIEVABLE
Explanation: The FactoryRepository failed to complete all or some part of
the requested operation. Probable cause is a failure in the naming component.
User Response: Check the event log for additional information. Exception
is ILifeCycleRepositoryAdmin::RequestFailed.
0x49420201 LCERR_UNABLE_TO_CLEAR_ELEMENT
Explanation: Most likely problem with naming code when attempting to
clear the repository.
User Response: Check the event log for additional information. Exception
is ILifeCycleRepositoryAdmin::RequestFailed.
0x49420202 LCERR_A_SCOPE_ELEMENT_IS_NULL
Explanation: An internal method was invoked illegally and with part of
the scope structure as null. Results will be unpredictable.
User Response: Do not invoke any non-documented methods. Exception is
CORBA::BAD_PARAM.
0x49420203 LCERR_INVALID_SCOPE
Explanation: The Scope parameter, or the Scope constructed from the
ScopeString parameter, did not obey the rules for valid scopes. The rules are:
User Response: Reconstruct the scope parameter so that it meets the specifications above. Note that in a ScopeString, any element not explicitly specified in the string is given a default value as follows:
It is the users responsibility to ensure that the combination of specified elements and supplied defaults is valid. Exception is IExtendedLifeCycle::InvalidScope.
0x49420204 LCERR_OUT_OF_MEMORY
Explanation: Machine has run out of virtual memory.
User Response: Cancel some of the applications currently running on the
system. Exception is CORBA::NO_MEMORY.
0x49420205 LCERR_MIXIN_PTR_IS_NULL
Explanation: Internal problem with a Life Cycle object.
User Response: Contact IBM Representative. Exception is CORBA::BAD_PARAM.
0x49420206 LCERR_INVALID_OBJECT
Explanation: Object is in an invalid state of absent.
User Response: Attempt to restart the server. Contact IBM Representative.
Exception is CORBA::INV_OBJREF.
0x49420207 LCERR_INVALID_LOCATION
Explanation: An invalid location object was passed in. The Location
object must inherit fromIManageble.
User Response: Ensure that the location object is properly created.
Exception is CORBA::BAD_PARAM.
0x49420208 LCERR_SYSTEMS_MANAGED
Explanation: An attempt was made to remove a systems managed lifecycle
object. These objects cannot be removed programmatically.
User Response: Remove the lifecycle object using the Component Broker
Graphical Interface. Exception is CosLifeCycle::NotRemovable.
0x49420209 LCERR_BAD_KEY_STRING
Explanation: An invalid key string was a member of the criteria passed to
the create_object method.
User Response: Correct the key string and retry the create_object
invocation. Exception is CosLifeCycle::InvalidCriteria.
0x4942020A LCERR_BAD_RELATIVENAME
Explanation: An invalid relative name was a member of the criteria passed
to the create_object method.
User Response: Correct the relative name and retry the create_object
invocation. The relative name must be a character string. Exception is
CosLifeCycle::InvalidCriteria.
0x4942020B LCERR_BAD_CELL_VISIBLE
Explanation: An invalid value was supplied for the "cell
visible" member of the criteria passed to the create_object method.
User Response: Correct the "cell visible" value and retry the
create_object invocation. Cell visible must be a CORBA::Boolean value. Exception is
CosLifeCycle::InvalidCriteria.
0x4942020C LCERR_BAD_HOST_VISIBLE
Explanation: An invalid value was supplied for the "host
visible" member of the criteria passed to the create_object method.
User Response: Correct the "host visible" value and retry the
create_object invocation. Host visible must be a CORBA::Boolean value. Exception is
CosLifeCycle::InvalidCriteria.
0x4942020D LCERR_BAD_WORKGROUP_VISIBLE
Explanation: An invalid value was supplied for the "workgroup
visible" member of the criteria passed to the create_object method.
User Response: Correct the "workgroup visible" value and retry
the create_object invocation. Workgroup visible must be a CORBA::Boolean value. Exception
is CosLifeCycle::InvalidCriteria.
0x4942020E LCERR_BAD_SCOPE
Explanation: An invalid scope was a member of the criteria passed to the
create_object method.
User Response: Correct the scope value and retry the create_object
invocation. The scope must be of type IExtendedLifeCycle::Scope. Exception is
CosLifeCycle::InvalidCriteria.
0x4942020F LCERR_BAD_SCOPE_STRING
Explanation: An invalid scope string was a member of the criteria passed
to the create_object method.
User Response: Correct the scope string value and retry the create_object
invocation. The scope string must be a character string. Exception is
CosLifeCycle::InvalidCriteria
0x49420210 LCERR_BAD_PROGRAMMATIC_BACKUP
Explanation: An invalid value was supplied for the "programmatic
backup" member of the criteria passed to the create_object method.
User Response: Correct the "programmatic backup" value and
retry the create_object invocation. Programmatic backup must be a CORBA::Boolean value.
Exception is CosLifeCycle::InvalidCriteria.
0x49420211 LCERR_PROGRAMMATIC_BACKUP_NOT_TRUE
Explanation: An invalid combination of values was supplied in the
criteria passed to the create_object method. If the criteria does not contain a primary
key string or a copy string, then the value of "programmatic backup" must be
true.
User Response: Correct the "programmatic backup" value and
retry the create_object invocation. Programmatic backup must be true if the criteria does
not contain a primary key string or copy string. Exception is
CosLifeCycle::InvalidCriteria.
0x49420212 LCERR_SEMANTICALLY_INVALID_METHOD_CALLED
Explanation: An internal error occurred which caused an invalid method to
be invoked.
User Response: Contact an IBM Representative. Exception is
CORBA::UNKNOWN.
0x49420213
LCERR_FAILURE_CREATING_DEFAULT_LIFECYCLE_OBJECTS
Explanation: An error occurred which caused a failure while trying to create the default
Lifecycle objects.
User Response: Examine activity log entries prior to this error to see if
another exception was logged. If so, see the user response for that error code. Otherwise,
attempt to reactivate the server. If this fails, contact an IBM Representative. Exception
is CORBA::UNKNOWN.
0x49420214
LCERR_FAILURE_DELETING_DEFAULT_LIFECYCLE_OBJECTS
Explanation: While attempting to remove a server, an error occurred which
caused failure to delete the default Lifecycle objects.
User Response: Examine activity log entries prior to this error to see if
another exception was logged. If so, see the user response to that error code. If this
error continues to occur, as a last resort, try a force delete of the server image, which
will remove the remaining default Lifecycle objects. To ensure that the name space
properly reflects the removal of these objects you will need to perform a Cleanup SMO
Namespace process for the Host Image of the host on which the server resided. Exception is
CORBA::UNKNOWN.
0x49420215 LCERR_INVALID_ATTRIBUTE_VALUE
Explanation: An internal error occurred while processing attribute
values.
User Response: Contact an IBM Representative. Exception is
CORBA::UNKNOWN.
0x49420227 CORBAMinorNamingAlreadyBound
Explanation: This indicate that an object is already bound to the name.
User Response: Re-binding operations unbind the name, then rebinds the
name without raising this exception.
0x49420227 CORBAMinorNamingCannotProceed
Explanation: This indicate that the implementation has given up for some
reason.
User Response: The client may be able to continue the operation using the
returned naming context.
0x49420227 CORBAMinorNamingContextObjectCreationFailed
Explanation: The creation of a NamingContext object or the narrowing to a
NamingContext implementation object failed.
User Response: Most likely system is running out of memory, or the remote
server of this object resided is not responding.
0x49420227 CORBAMinorNamingDCECDSError
Explanation: This indicate a DCE error has occurred.
User Response: User can look at fsLocStat and CDS entry information in
activity log to determine the problem.
0x49420227 CORBAMinorNamingHeapOutOfMemory
Explanation: Attempt to allocate memory on the heap has failed.
User Response: System is running out of memory.
0x49420227 CORBAMinorNamingInvalidCORBAName
Explanation: This indicate that the name is invalid. (This exception may
be raised upon further implementation restrictions.)
User Response: A name (of type CosNaming::Name) is valid if none of the
following is true:
Additional to above, for CDS-based implementation, a name n is invalid if:
0x49420227 CORBAMinorNamingListSizeExceedMaxValue
Explanation: The list size exceeds the allowed maximum value of 1000.
User Response: Make sure do not exceed the maximum value.
0x49420227 CORBAMinorNamingNoImplementation
Explanation: The invoked operation is not supported in the product or is
not valid on the target object.
User Response: Check that the operation being invoked and the runtime
type of the target object are compatible. Reference the documentation for the operation to
find out about any restrictions.
0x49420227 CORBAMinorNamingNotEmpty
Explanation: This indicate that the naming context contains any bindings.
User Response: User needs to issue a separate unbind or destroy for each
single binding in the sub-tree by traversing the name tree from bottom-up.
0x49420227 CORBAMinorNamingNotFound
Explanation: This indicate that the name does not identify a binding. If
a compound name is passed as an argument for the bind operation, it traverses multiple
contexts. A NotFound exception is raised if any of the intermediate contexts cannot be
resolved.
User Response: Make sure the name is correct and the binding exist in the
name space.
0x49420227 CORBAMinorNamingUnknownException
Explanation: An unknown exception was caught.
User Response: Look backward from activity log to find out the source of
the problem.
0x49420227 CORBAMinorPropertyInvalidPropertyName
Explanantion: This indicates that the supplied property_name is invalid.
User Response: For example, a property_name cannot be a NULL pointer or
cannot be of length 0.
0x49420227 CORBAMinorPropertyMultipleExceptions
Explanantion: This exception is used to return a sequence of exceptions
when dealing with the "batch" operations of define_properties. (See Property
Service or CosPropertyService.idl for detail information.)
User Response: Examine the reason and failing_property_name in
exceptions, which is returned by CosPropertyService::MultipleExceptions. exceptions is a
sequence of PropertyException, and a PropertyException is a two tuple of: <reason, and
failing_property_name>. reason is an enumeration reflecting one of the exceptions
defined in CosPropertyService.idl file. failing_property_name is a string, which names the
property.
0x49420227 CORBAMinorPropertyPropertyNotFound
Explanantion: This indicates that the supplied property_name is not in
the PropertySet.
User Response: See User Response in
CosPropertyService::UnsupportedProperty exception, minor code 0x49420227
CORBAMinorPropertyUnsupportedProperty for detail.
0x49420227 CORBAMinorPropertyReadOnlyProperty
Explanantion: This indicates that a user is trying to modify a property
that the PropertySet considers to be read only.
User Response: The current read only properties are:
0x49420227 CORBAMinorPropertyUnsupportedProperty
Explanantion: This indicates that a user is trying to define a property
not supported by this PropertySet.
User Response: Make sure there is no typo in the property_name and the
current fixed property set is:
0x49420227 CORBAMinorPropertyUnsupportedTypeCode
Explanantion: This indicates that a user is trying to define a property
having an any TypeCode that is not supported by this PropertySet.
User Response: The only supported TypeCode for every property in the
PropertySet is CORBA::tk_string.
0x49420228
CORBAMinorNamingBindingIteratorObjectCreationFailed
Explanation: The creation of a BindingIterator object or the narrowing to
a BindingIterator implementation object failed.
User Response: Most likely system is running out of memory, or the remote
server of this object resided is not responding.
0x49420228 CORBAMinorNamingBindingNotFound
Explanation: This indicate that the name does not identify a binding. If
a compound name is passed as an argument for the bind operation, it traverses multiple
contexts. A NotFound exception is raised if any of the intermediate contexts cannot be
resolved.
User Response: Make sure the name is correct and the binding exist
in the name space.
0x49420228 CORBAMinorNamingDCECDSCannotDeleteEntry
Explanation: CDS Naming implementation cannot delete the binding because
of the entry that client provided is not empty.
User Response: User needs to issue a separate unbind or destroy for each
single binding in the sub-tree by traversing the name tree from bottom-up.
0x49420228 CORBAMinorNamingInvalidCORBAObject
Explanation: The object supplied with the invoked method is not of type
CORBA::Object.
User Response: Make sure the object is of type CORBA::Object.
0x49420228 CORBAMinorNamingObjectDestructionFailed
Explanation: The destruction or removing of the object failed.
User Response: Look backward from activity log to find out the source of
the problem.
0x49420228 CORBAMinorNamingPropertyNameSyntaxError
Explanantion: The properties_s supplied with the invoked method has a
syntax error.
User Response: Provide a valid PropertiesStringConverter string. The
syntax uses equal ("=") to connect property name and property value and uses
comma (",") to separate property name/value pairs. For example:
BindingHost=challenger.austin.ibm.com,BindingServer=myappsrv1
Note: There is no space before or after the ("=") delimeter nor
the (",") separator.
0x49420228 CORBAMinorNamingStringNameSyntaxError
Explanation: The String name supplied with invoked method has a syntax
error.
User Response: Provide a valid NamingStringSyntax String name.
0x49420229
CORBAMinorNamingBindingStringIteratorObjectCreationFailed
Explanation: The creation of a BindingStringIterator object or the
narrowing to a BindingStringIterator implementation object failed.
User Response: Most likely system is running out of memory, or the remote
server of this object resided is not responding.
0x49420229 CORBAMinorNamingDCECDSHandleCreationFailed
Explanation: CDSPI cdsGetHandle() returned NULL pointer, handle creation
failed.
User Response: Most likely system is running out of memory or system
resources.
0x49420229 CORBAMinorNamingInvalidDCECDSName
Explanation: The DCE/CDS name converted from the CORBA name supplied with
the invoked method is invalid.
User Response: Provide a valid name for CDS-based implementation, a name
n is invalid if:
0x49420229 CORBAMinorNamingInvalidNamingContextObject
Explanation: The object supplied with the invoked method is not of type
CosNaming::NamingContext.
User Response: Make sure the object is of type CosNaming::NamingContext.
0x4942022A CORBAMinorNamingDCECDSWrongUsageUnbind
Explanation: Wrong method been called when remove a naming context (bound
using bind_new_context or bind_new_context_with_string).
User Response: User needs to use destroy rather than unbind to remove the
naming context.
0x4942022A
CORBAMinorNamingStandardSyntaxModelObjectCreationFailed
Explanation: The StandardSyntaxModel create method returned a NULL
object.
User Response: Most likely system is running out of memory or system
resources.
0x4942022A CORBAMinorNamingInvalidCosNamingName
Explanantion: This indicate that the name parameter is invalid. (In some
of the Naming functions, CosNaming::NamingContext::InvalidName exception is not in the
list for throwing. They throw CORBA::BAD_PARAM exception with this minor code instead.)
User Response: See User Response in
CosNaming::NamingContext::InvalidName exception, minor code 0x49420227
CORBAMinorNamingInvalidCORBAName for detail.
0x4942022B CORBAMinorNamingDCECDSNoPartialName
Explanantion: This indicates that the DCE/CDSPI cdsReadAttrValue() does
not return a valid partially resolved name to the Naming Service.
User Response: Report this problem to Component Broker customer support.
0x4942022B CORBAMinorNamingInvalidNameComponent
Explanantion: This indicates that the CosNaming::NameComponent in name
parameter is invalid.
User Response: See User Response in
CosNaming::NamingContext::InvalidName exception, minor code 0x49420227
CORBAMinorNamingInvalidCORBAName for detail.
0x4942022B CORBAMinorNamingUtilObjectCreationFailed
Explanation: The CosNameUtils Instance method returned a NULL object.
User Response: Most likely system is running out of memory or system
resources.
0x4942022C CORBAMinorNamingObjectCreationFailed
Explanation: Failed to create or initialize object.
User Response: Most likely system is running out of memory or system
resources, or look backward from activity log to find out the source of the problem.
0x4942022D
CORBAMinorNamingPropertiesStringConverterObjectCreationFailed
Explanantion: The creation of a PropertiesStringConverter object or the
narrowing to a PropertiesStringConverter implementation object failed. System exception is
CORBA::INV_OBJREF.
User Response: Most likely system is running out of memory, or the remote
server of this object resided is not responding.
0x4942024E CORBAMinorNamingStringHeapOutOfMemory
Explanation: Attempt to allocate memory on the heap has failed.
User Response: Most likely system is running out of memory or system
resources.
0x4942024E CORBAMinorNamingStringIllegalStringSyntax
Explanation: Found a syntax error in the string.
User Response: Make sure follow the syntax rule for string.
0x4942024E CORBAMinorNamingStringInvalidCORBAName
Explanation: The CORBA name supplied with the invoked method is invalid.
User Response: A name (of type CosNaming::Name) is valid if none of the
following is true:
0x4942024E
CORBAMinorNamingStringPropertiesToStringBadType
Explanantion: The properties_to_string method requires property values to
be of TypeCode CORBA::tk_string.
User Response: Make sure the supplied property values are of TypeCode
CORBA::tk_string.
0x4942024E CORBAMinorNamingStringUnMachedQuote
Explanation: Found an unmatched quote in the string.
User Response: Make sure a begin-quote is matched by an end-quote or vice
versa.
0x4942024E
CORBAMinorNamingStringValueFromStringNotFound
Explanantion: The supplied property_name was not found in the supplied
properties string, properties_s.
User Response: Make sure the supplied property_name is in the supplied
properties_s when calling
INamingPSCLocalObjectImpl::PropertiesStringConverter::value_from_string().
0x4942024F CORBAMinorNamingStringInvalidStringName
Explanation: The String name supplied with the invoked method is invalid.
User Response: Make sure the length of String name is not zero and the
String name pointer is not NULL.
0x494202EF OTSAPPCMINOR_SPACESFOUND
Explanation: Spaces have been found in a field/parameter supplied to the
component. This is not supported.
User Response: Correct the configuration/parameter and retry. Exception
is CORBA::BAD_PARAMS.
0x494202EF OTSAPPCMINOR_UNEXPECTEDEXCEPTION
Explanation: An unexpected exception has been caught by an object in the
transaction service and this object is unable to process it. The exception is not a CORBA
standard exception nor a CORBA user exception.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which objects were involved, were they calling an
operating system function? Make sure your application has access to the resources it
requires and is using any services from the operating // system or CBSeries correct. Look
in the NT event logs as there may be additional messages which indicate why the exception
was thrown. Exception is CORBA::UNKNOWN.
0x494202EF SOMTRRAS::Minor_unexpectedException
Explanation: An unexpected error occurred and was caught by an object in
the transaction service. The error is not a CORBA standard exception nor a CORBA user
exception.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which objects were involved. Where they calling
an operating system function? Make sure your application has access to the resources it
requires and is using any services from the operating system or Component Broker Connector
correctly. Look in the NT event logs for more information which might indicate why the
exception was thrown.
0x494202F0 OTSAPPCMINOR_LONGERTHANEIGHT
Explanation: A field/parameter supplied to the component is longer than
its maximum length of 8 characters. This is not supported.
User Response: Correct the configuration/parameter and retry. Exception
is CORBA::BAD_PARAMS.
0x494202F0 SOMTRRAS::Minor_unexpectedRetCode
Explanation: An unexpected response was received by an object in the
transaction service. This could be caused either by an application interacting incorrectly
with the transaction service or an internal error in one of the transaction service
objects.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. Check the error log for more
information that might describe what your application was doing when the error occurred
and report the occurrence to technical support.
0x494202F1 OTSAPPCMINOR_LONGERTHANSEVENTEEN
Explanation: A fully-qualified LUName field/parameter supplied to the
component is longer than its maximum length of 17 characters. This is not supported.
User Response: Correct the configuration/parameter and retry.Exception is
CORBA::BAD_PARAMS.
0x494202F1 SOMTRRAS::Minor_unknownState
Explanation: An object from the transaction service is unable to perform
the action requested by an application because all, or part, of its internal state is
unknown. This is a transient problem usually due to a configuration error.
User Response: Look for earlier messages in the activity log and follow
the instructions for these messages. Exception is CORBA::INITIALIZE.
0x494202F2 OTSAPPCMINOR_INVALIDSTATE
Explanation: An object from the transaction service has detected an
inconsistency in its internal state. This is caused either by an application making
incorrect use of the transaction service, or there is an internal error in the transaction
service.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the error occur. Make sure your
application is making correct use of the transaction
// service. If your application is correct, save the NT logs and the information
describing what your application was doing when the error occurred and contact your
support organization. Exception is CORBA::INTERNAL, CosTransactions::NotPrepared.
0x494202F2 OTSAPPCMINOR_LONGERTHANSIXTYFOUR
Explanation: A Transaction Program Name (TPN) field/parameter supplied to
the component is longer than its maximum length of 64 characters. This is not supported.
User Response: Correct the configuration/parameter and retry. Exception
is CORBA::BAD_PARAMS.
0x494202F2 SOMTRRAS::Minor_invalidState
Explanation: An object from the transaction service has detected an
inconsistency in its internal state. This is caused either by an application making
incorrect use of the transaction service, or there is an internal error in the transaction
service.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. Check the error log for more
information that might describe what your application was doing when the error occurred
and report the occurrence to technical support.
0x494202F3 OTSAPPCMINOR_ZEROLENGTH
Explanation: A field/parameter supplied to the component is either NULL
or zero length. This is not supported.
User Response:Correct the configuration/parameter and retry. Exception is
CORBA::BAD_PARAMS.
0x494202F3 SOMTRRAS::Minor_unfinishedTransaction
Explanation: The transaction service is unable to commit a top-level
transaction because there is still outstanding work occurring for the transaction either
locally or in a remote server. Alternatively, a non-user exception was generated in a
remote method.
User Response: Look in the NT event logs to see if an exception occurred
in a remote server. If a non-user exception is being thrown, correct your application so
that the exception does not occur, or ensure the exception is caught in the server where
it is first thrown. If no exception has occurred, there is a problem in the design of your
application. It should not request a commit until all remote methods and subtransactions
have completed for the transaction. Correct your application.
0x494202F4 OTSAPPCMINOR_TOOMANYDOTS
Explanation: A fully qualified LU name field/parameter supplied to the
component contains more then one ".". This is not supported.
User Response: Correct the configuration/parameter and retry. Exception
is CORBA::BAD_PARAMS.
0x494202F4 SOMTRRAS::Minor_unfinishedSubTransaction
Explanation: The transaction service is unable to commit a subtransaction
because there is either still outstanding work occurring for the transaction or a non-user
exception was thrown and not caught in a remote method.
User Response: Look in the NT event logs to see if an exception occurred
in a remote server involved in the transaction. If a non-user exception is being thrown,
correct your application so that the exception does not occur, or ensure the exception is
caught in the server where it is first thrown. If no exception has occurred, there is a
problem in the design of your application. It should not request a commit until all remote
methods and subtransactions have completed for the transaction. Correct your application.
0x494202F5 OTSAPPCMINOR_BUFFERTOOSMALL
Explanation: A buffer passed to an internal routine is too small.
User Response: Turn on transaction service trace in the Component Broker
server and rerun the failing request. Then contact IBM Service. Exception is
CORBA::INTERNAL.
0x494202F5 SOMTRRAS::Minor_noMemory
Explanation: An object from the transaction service is unable to acquire
the memory it needs to complete a request from an application.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and at what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. In particular look for
possible loops that may consume memory. If the application runs for some time before this
exception occurs, ensure that objects which are no longer required are being correctly
destroyed. If your application is correct, increase your NT virtual page size.
0x494202F6 OTSAPPCMINOR_BADLOGNAME
Explanation: A log name received from a partner system is not specified
in the correct SNA format.
User Response:Turn on link trace in the local SNA product and transaction
service trace in the Component Broker server and rerun the failing request. Then contact
IBM Service. Exception is CORBA::MARSHAL.
0x494202F6 OTSAPPCMINOR_LOGICERROR
Explanation: The transaction service has detected an internal logic
error. This should not occur if the transaction service is being called correctly.
User Response:Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the error occur. Make sure your
application is making correct use of the transaction
// service. If your application is correct, save the NT logs and the information
describing what your application was doing when the error occurred and contact your
support organization. Exception is CORBA::INTERNAL.
0x494202F6 SOMTRRAS::Minor_logicError
Explanation: The transaction service has detected an internal logic
error. This should not occur if the transaction service is being called correctly.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. Check the error log for more
information that might describe what your application was doing when the error occurred
and report the occurrence to technical support.
0x494202F7 OTSAPPCMINOR_BADPSHEADER
Explanation: A presentation services (PS) header received from a partner
system during commit processing is not specified in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x494202F7 OTSAPPCMINOR_USERERROR
Explanation: The transaction service has been incorrectly called by an
application.
User Response:Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the exception occur. Look for other
messages in the NT event logs that may give more details on the cause of the problem. When
you have identified which call or calls to the transaction service are in error, correct
your application. Exception is CORBA::INTERNAL.
0x494202F7 SOMTRRAS::Minor_userError
Explanation: The transaction service was incorrectly called by an
application.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the exception occur. Look for other
messages in the NT event logs that may give more details on the cause of the problem. When
you have identified which call or calls to the transaction service are in error, correct
your application.
0x494202F8 OTSAPPCMINOR_BADLUWID
Explanation: A Logical Unit of Work identifier (LUWId) received from a
partner system is not specified in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x494202F8 SOMTRRAS::Minor_mutexError
Explanation: The transaction service was unable to lock or unlock a
mutex. This should not occur if the transaction service is being called correctly.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the error occur. Make sure your
application is making correct use of the transaction service. Check the error log for more
information that might describe what your application was doing when the error occurred
and report the occurrence to technical support.
0x494202F9 OTSAPPCMINOR_BADLUNAME
Explanation: A Logical Unit (LU) name received from a partner system is
not specified in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x49202F9 SOMTRRAS::Minor_noTransaction
Explanation: A transactional request was issued outside the scope of the
transaction. This is an application error.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the exception occur. Ensure that your
application uses the CosTransactions::Current interface to ensure a transaction context is
associated with the current thread of execution when the transaction service is called.
0x494202FA OTSAPPCMINOR_BADSESSIONID
Explanation: A session identifier received from a partner system is not
specified in the correct SNA format.
User Response:Turn on link trace in the local SNA product and transaction
service trace in the Component Broker server and rerun the failing request. Then contact
IBM Service. Exception is CORBA::MARSHAL.
0x494202FA SOMTRRAS::Minor_wrongTransaction
Explanation: A transactional request was issued in the scope of one
transaction and returned in the scope of another transaction. This is an application
error.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and at what point in the lifetime of the transaction the exception occurred. In
particular, identify the objects that are located in different servers to where the
transaction was started and that either create one or more subtransactions or use the
CosTransactions::Current interface to suspend or resume the transaction context. It is
likely that these objects are not managing transactions correctly.
0x494202FB OTSAPPCMINOR_BADCONVCORRELATOR
Explanation: A conversation correlator received from a partner system is
not specified in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x49202FB SOMTRRAS::Minor_retryLimitExhausted
Explanation: There is a problem communicating with the objects involved
in a transaction. The transaction service made as many attempts to contact this object as
are permitted by the commitRetryLimit configured for the server and made a heuristic
decision.
User Response: Restart any servers that are currently unavailable. This
completes the transaction for any registered objects that are located in these servers.
Look at the action that was taken by each of these objects and correct any problems in the
data for your application caused by this heuristic decision.
0x494202FC OTSAPPCMINOR_BADLUWSTATE
Explanation: A transaction state indicator received from a partner system
is not a recognized SNA value.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x494202FC SOMTRRAS::Minor_wrongState
Explanation: The transaction service is unable to complete the requested
operation because it is not in the correct state to perform the work. This is an
application error.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and at what point in the lifetime of the transaction the exception occurred. It is likely
that these objects are not managing transactions correctly. Correct your application as
appropriate.
0x494202FD OTSAPPCMINOR_BADXLN
Explanation: An exchange log names (XLN) record received from a partner
system is not
// in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x494202FD SOMTRRAS::Minor_timedOut
Explanation: A transaction rolled back because it did not complete within
the specified time limit. This may indicate that the server is waiting for a resource that
is unavailable, or a deadlock has occurred in your application.
User Response: Check that all of the servers involved in the transaction
are operating correctly. In addition, check the use of locks in your application for
possible deadlock situations.
0x494202FE OTSAPPCMINOR_BADCOMPARESTATES
Explanation: An compare states record received from a partner system is
not in the correct SNA format.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exception is CORBA::MARSHAL.
0x494202FE SOMTRRAS::Minor_notInitialized
Explanation: An object from the transaction service was requested to
perform an operation before it was initialized.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and at what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. If your application is
correct, save the NT logs and the information describing what your application was doing
when the error occurred and report the occurrence to technical support.
0x494202FF OTSAPPCMINOR_NULLOBJECT
Explanation: A transaction service request has been made against an
object that does not exist.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which transaction service objects were involved and
what point in the lifetime of the transaction did the error occur. Make sure your
application is making correct use of the transaction service. If your application is
correct, save the NT logs and the information describing what your application was doing
when the error occurred and contact your support organization. Exceptions are
CORBA::PERSIST_STORE, CORBA::INTERNAL and CORBA::INVALID_TRANSACTION, CORBA::NO_MEMORY.
0x494202FF OTSAPPCMINOR_SENDRECEIVEFAILED
Explanation: A call to send data from a partner system and receive a
response has failed.
User Response: Turn on link trace in the local SNA product and
transaction service trace in the Component Broker server and rerun the failing request.
Then contact IBM Service. Exceptions are OTSAPPCConnection::TPNUnavailable,
OTSAPPCConnection::SecurityNotValid, OTSAPPCConnection::BadCommunications,
OTSAPPCConnection::PartnerNotRecoverable, and OTSAPPCConnection::RecoveryIncomplete.
0x494202FF SOMTRRAS::Minor_nullObject
Explanation: A transaction service request was made against an object
that does not exist.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which transaction service objects were involved
and at what point in the lifetime of the transaction the error occurred. Make sure your
application is making correct use of the transaction service. Check the error log for more
information that might describe what your application was doing when the error occurred
and report the occurrence to technical support.
0x49420300 OTSAPPCMINOR_COMMITCOMMFAILURE
Explanation: A commit call is unable to complete because a partner system
is unreachable.
User Response: Restart the partner system. Details of which system is
unavailable is given in a previous message. Exception is CORBA::COMM_FAILURE.
0x49420300 SOMTRRAS::Minor_recoveryFailed
Explanation: The transaction service has experienced problems during
recovery and, as a result, has prevented the application server from starting.
User Response: Determine the reason why recovery failed. Look for the
messages logged just prior to this exception being logged as these explain why recovery
failed. Having corrected the problem, restart the application server.
0x49420301 OTSAPPCMINOR_RBCOMMFAILURE
Explanation: A rollback call is unable to complete because a partner
system is unreachable.
User Response: Restart the partner system. Details of which system is
unavailable is given in a previous message. Exception is CORBA::COMM_FAILURE.
0x49420301 SOMTRRAS::Minor_terminationNotAllowed
Explanation: An application has attempted to end a transaction using the
commit method in a different server from the one where the transaction was started. This
is not supported by the transaction service.
User Response: Investigate what your application was doing when the
exception was thrown. For example, look at which application objects were involved and at
what point in their processing the commit method call was made. Correct your application
so that the commit is called in the same server as the begin method. The easiest way to
ensure this is to have a single object responsible for calling both the begin and the
commit method.
0x49420302 OTSAPPCMINOR_RESYNCOK
Explanation: A resync request confirms that the transaction has already
completed on both systems.
User Response: No action is required. This exception is thrown for
information only. Exception is CosTransactions::NoTransaction.
0x49420302 SOMTRRAS::Minor_rollbackOnlySet
Explanation: The transaction was marked "rollback only" and one
of the following types of requests was attempted.
These operations are not permitted when the transaction is marked as "rollback
only".
User Response: Examine the design of your application to understand how
the transaction service is used. Either alter the code so that these calls are not made
when the transaction is marked "rollback only", or ensure your application uses
a try/catch structure around these calls so it can handle the exception.
0x49420303 OTSAPPCMINOR_PREPAREHEURISTIC
Explanation: A heuristic decision was detected during a prepare
operation. This heuristic decision has been made by one of your application's
CosTransactions::Resource objects. The transaction service is reporting the heuristic
decision as it will affect the outcome of the transaction.
User Response: None. Exceptions are CosTransactions::HeuristicMixed,
CosTransactions::HeuristicHazard, CosTransactions::HeuristicCommit, and
CosTransactions::HeuristicRollback.
0x4920303 SOMTRRAS::Minor_prepareHeuristic
Explanation: A heuristic decision was detected during a prepare
operation. This heuristic decision was made by one of the CosTransactions::Resource
objects of your application. The transaction service is reporting the heuristic decision
as it affects the outcome of the transaction.
User Response: None.
0x49420304 OTSAPPCMINOR_COMMITHEURISTIC
Explanation: A heuristic decision was detected during a commit operation.
This heuristic decision has been made by one of your application's
CosTransactions::Resource objects. The transaction service is reporting the heuristic
decision as it will affect the outcome of the transaction.
User Response:None. Exceptions are CosTransactions::HeuristicMixed,
CosTransactions::HeuristicHazard, and CosTransactions::HeuristicRollback.
0x4920304 SOMTRRAS::Minor_commitHeuristic
Explanation: A heuristic decision was detected during a commit operation.
This heuristic decision was made by one of the CosTransactions::Resource objects of your
application. The transaction service is reporting the heuristic decision as it affects the
outcome of the transaction.
User Response: None.
0x49420305 OTSAPPCMINOR_ROLLBACKHEURISTIC
Explanation: A heuristic decision was detected during a rollback
operation. This heuristic decision has been made by one of your application's
CosTransactions::Resource objects. The transaction service is reporting the heuristic
decision as it will affect the outcome of the transaction.
User Response: None. Exceptions are CosTransactions::HeuristicMixed,
CosTransactions::HeuristicHazard, and CosTransactions::HeuristicCommit.
0x4920305 SOMTRRAS::Minor_rollbackHeuristic
Explanation: A heuristic decision was detected during a rollback
operation. This heuristic decision was made by one of the CosTransactions::Resource
objects of your application. The transaction service is reporting the heuristic decision
as it affects the outcome of the transaction.
User Response: None.
0x49420306 SOMTRRAS::Minor_subtransactionRolledBack
Explanation: A subtransaction rolled back during a commit_subtransaction
call to a CosTransactions::Resource object. This exception is part of the standard
transaction service interface.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to handle this exception appropriately.
0x49420307 OTSAPPCMINOR_COMMIT1PROLLEDBACK
Explanation: A transaction rolled back during the commit_one_phase call
to a CosTransactions::Resource object. This exception is part of the standard transaction
service interface.
User Response:Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to handle this exception appropriately. Exception is
CORBA::TRANSACTION_ROLLEDBACK.
0x49420307 SOMTRRAS::Minor_commitOnePhaseRolledBack
Explanation: A transaction rolled back during the commit_one_phase call
to a CosTransactions::Resource object. This exception is part of the standard transaction
service interface.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to handle this exception appropriately.
0x49420308 OTSAPPCMINOR_COMMIT1PHEURISTIC
Explanation: A heuristic decision was detected during a commit_one_phase
call to a CosTransactions::Resource object. This heuristic decision has been made by one
of your application's CosTransactions::Resource objects. The transaction service is
reporting the heuristic decision as it will affect the outcome of the transaction.
User Response: None. Exceptions are: CosTransactions::HeuristicMixed and
CosTransactions::HeuristicHazard.
0x4920308 SOMTRRAS::Minor_commitOnePhaseHeuristic
Explanation: A heuristic decision was detected during a commit_one_phase
call to a CosTransactions::Resource object. This heuristic decision was made by one of the
CosTransactions::Resource objects of your application. The transaction service is
reporting the heuristic decision as it affects the outcome of the transaction.
User Response: None.
0x49420309 SOMTRRAS::Minor_notSubtransaction
Explanation: A method that should only be used when working on behalf of
a subtransaction was issued during a top-level transaction. This is an application error.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to call this object appropriately.
0x4942030A SOMTRRAS::Minor_notTopLevelTransaction
Explanation: A method that should only be used when working on behalf of
a top-level transaction was issued during a subtransaction. This is an application error.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to call this object appropriately.
0x4942030B SOMTRRAS::Minor_commitRolledBack
Explanation: A transaction rolled back during the commit call. This
exception is part of the standard transaction service interface.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to handle this exception appropriately.
0x4942030C SOMTRRAS::Minor_noFactoryAvailable
Explanation: A transaction could not be started because a
CosTransactions::TransactionFactory is not available.
User Response: Ensure there is an application server available which
contains a transaction factory for the client.
0x4942030D SOMTRRAS::Minor_activeNested
Explanation: A transaction could not be completed because there are
active subtransactions. This is an application error.
User Response: Correct your application.
0x4942030E OTSAPPCMINOR_NOTSUPPORTED
Explanation: The request could not be completed because the function is
not supported.
User Response: Identify which call to the transaction service is throwing
this exception. Check the documentation for this call and alter your application to use
supported operations. Exceptions are CORBA::NO_IMPLEMENT.
0x492030E SOMTRRAS::Minor_notSupported
Explanation: The request could not be completed because the function is
not supported.
User Response: Identify which call to the transaction service is throwing
this exception. Check the documentation for this call and alter your application to use
supported operations.
0x4942030F SOMTRRAS::Minor_omgtidAlreadyUsed
Explanation: The transaction service can not create a new transaction
because it is unable to generate a new OMGtid as all possible values for the OMGtid are in
use. This could be caused by an application starting many transactions and never ending
them.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which objects were involved and what where they doing.
Look at the points in your application where transactions are started and ended and ensure
your application is making correct use of the transaction service. If your application is
correct, save the NT logs and the information describing what your application was doing
when the error occurred and contact your support organization. Exception is
CORBA::IMP_LIMIT.
0x49420310 SOMTRRAS::Minor_omgtidNull
Explanation: The CosTransactions::TransactionFactory recreate method was
called with a propagation context parameter containing a NULL OMGtid. This method is
provided for use by implementations of the transaction service when receiving
transactional requests from remote servers. It should not be used by applications.
User Response: Investigate what your application was doing when the
exception was thrown. Look at which objects were involved and what they were doing. Ensure
that no part of your application is calling the CosTransactions::TransactionFactory
recreate method. If the error occurs while your application is not using the recreate
method then the transaction service is using this method when receiving a request from a
remote server. Look for errors in this remote server. If you cannot solve the problem,
save the NT logs and the information describing what your application was doing when the
error occurred and report the occurrence to technical support.
0x49420311 SOMTRRAS::Minor_alreadyCurrent
Explanation: The transaction service cannot receive a transactional
request for a local object because the thread where the request is to run is already
associated with this transaction. This is an internal error in the transaction service.
User Response: Check the error log for more information that might
describe what your application was doing when the error occurred and report the occurrence
to technical support.
0x49420312 SOMTRRAS::Minor_noLog
Explanation: The transaction service can not initialize properly because
its log file is not available. This may be because the log directory set up for the server
does not exist, there is insufficient disk space for the log files, or the server does not
have permission to create the log files in the log directory.
User Response: Restart your server and look for the messages generated by
the transaction service. These explain what is wrong with the log configuration. Correct
the log configuration and restart the server.
0x49420313 OTSAPPCMINOR_RESYNCHEURISTIC
Explanation: A heuristic decision was taken when the transaction service
was resolving the outcome of an incomplete transaction during server startup. This
heuristic decision has been made by one of your application's CosTransactions::Resource
objects. The transaction service is reporting the heuristic decision as it will affect the
outcome of the transaction.
User Response: None. Exceptions are CosTransactions::HeuristicMixed,
CosTransactions::HeuristicHazard, CosTransactions::HeuristicCommit, and
CosTransactions::HeuristicRollback.
0x4920313 SOMTRRAS::Minor_resyncHeuristic
Explanation: A heuristic decision was taken when the transaction service
was resolving the outcome of an incomplete transaction during server startup. This
heuristic decision was made by one of the CosTransactions::Resource objects of your
application. The transaction service is reporting the heuristic decision as it affects the
outcome of the transaction.
User Response: None.
0x49420314 SOMTRRAS::Minor_asyncRolledBack
Explanation: A request can not be performed on a transaction because this
transaction has already rolled back. This exception is part of the standard transaction
service interface.
User Response: Identify which call to the transaction service resulted in
this exception. Check the documentation for this call and ensure your application is
programmed to handle this exception appropriately.
0x49420315 SOMTRRAS::Minor_thisServerEnding
Explanation: The transaction is being rolled back because the local
server is terminating.
User Response: Rerun the transaction when the server is restarted.
0x49420316 SOMTRRAS::Minor_remoteServerEnding
Explanation: The transaction is being rolled back because another server
which is processing part of the transaction is terminating.
User Response: Rerun the transaction when the remote server is restarted.
0x49420317 SOMTRRAS::Minor_superiorRegFailed
Explanation: The transaction is being rolled back because another server
which is processing part of the transaction can not be contacted.
User Response: Rerun the transaction when the remote server is restarted.
0x49420318 SOMTRRAS::Minor_noLogStorage
Explanation: The transaction service is unable to continue running
transactions because there is insufficient disk space for the transaction service log.
This log contains information about the transactions running in the server and is used
during recovery.
User Response: Free some disk space for the transaction service log.
0x49420320 OTSAPPCMINOR_ROLLBACKONLYSET
Explanation: The transaction has been marked "rollback only"
and one of the following types of requests has been attempted:
These operations are not permitted when the transaction is marked as "rollback
only".
User Response: Examine the design of your application to understand how
the transaction service is used. Either alter the code so that these calls are not made
when the transaction is marked "rollback only", or ensure your application uses
a try/catch structure around these calls so it can handle the
CORBA::TRANSACTION_ROLLEDBACK exception. Exception is CORBA::TRANSACTION_ROLLEDBACK.
0x494203EC SOMIM_INTERNAL
Explanation: Unknown.
User Response: Report the occurrence to technical support.
0x4942041A SOMROOTIM_ICONTAINERMINOR_HEAP_OUT_OF_MEMORY
Explanation: Memory could not be allocated from a heap.
User Response: A heap could not extend during an allocation. Review the
logs to determine the heap and take action to allow it to extend.
0x4942041A SOMROOTIM_ICONTAINERMINOR_NO_LOCALFRIENDQOS
Explanation: An object cannot register with a container.
User Response: The object lacks the interface needed to register with a
container. Refer to the programming documentation to determine the interface needed.
0x4942041A SOMROOTIM_ICONTAINERMINOR_NOIMPLEMENT
Explanation: The invoked operation is not supported in the product or is
not valid on the target object.
User Response: Check that the operation being invoked and the runtime
type of the target object are compatible. Reference the documentation for the operation to
find out about any restrictions.
0x4942041A SOMROOTIM_ICONTAINERMINOR_UNEXPECTED
Explanation: An unexpected error occurred during an operation.
User Response: This indicates a system type failure. Contact your service
provider for additional help.
0x4942041B SOMROOTIM_ICONTAINER_MC_FAILED_REGISTRATION
Explanation: The master container did not register into the master
container object cache.
User Response: The master container failed to register with itself.
Restart the server, if this fails again contact your service provider.
0x4942041B SOMROOTIM_ICONTAINERMINOR_BAD_KEY
Explanation: The key provided is invalid or corrupted.
User Response: Retry the operation, if the problem persists review the
objects key for valid character set and syntax. If this is not the problem contact your
service provider.
0x4942041B SOMROOTIM_ICONTAINERMINOR_UNKNOWN_HEAP
Explanation: An unexpected error occurred during the use of a heap.
User Response: Review the logs to determine the exact cause of this
failure and take the recommended action.
0x4942044C SOMBOIM_IHOMEMINOR_BADPARAM_CONFIG
Explanation: Configuration of the home failed.
User Response: Check the associated message. Most often this is the
result of an incorrect DULL or function name. Update the COS with the correct value, or
rebuild the particular DULL to have the function specified and try again.
0x4942044C SOMBOIM_IHOMEMINOR_DUPLICATE_KEY
Explanation: The key given for a createFromPrimaryKey has already been
used by an existing object.
User Response: Perform a findByPrimaryKeyString to find objects which
already exist.
0x4942044C SOMBOIM_IHOMEMINOR_INVALID_KEY
Explanation: The key given for a createFromPrimaryKeyString or
findByPrimaryKeyString can not be used to create or reactivate the object.
User Response: Check the contents of the key to make sure they are
correct. Check to make sure the type of key used is compatible with the keys used by the
home in question.
0x4942044C SOMBOIM_IHOMEMINOR_NO_IMPL
Explanation: The invoked operation is not supported in the product or is
not valid on the target object.
User Response: Check that the operation being invoked and the runtime
type of the target object are compatible. Reference the documentation for the operation to
find out about any restrictions.
0x4942044C SOMBOIM_IHOMEMINOR_NO_MEMORY_CONFIG
Explanation: A memory error occurred during configuration of a home.
Memory could not be extended in the heap.
User Response: Review the log and check to see why the heap could not be
used to create the object.
0x4942044C SOMBOIM_IHOMEMINOR_UNINIT_FAILED
Explanation: The uninitForPassivation or uninitForDestruction method
failed to complete.
User Response: In the case of uninitForDestruction, check to make sure
that the state of the home is "dead". If not, the home can not be destroyed.
Otherwise, check the error log for previous messages which may indicate why the the uninit
method failed.
0x4942044C SOMBOIM_IHOMEMINOR_UNKNOWN_CONFIG
Explanation: An error during the configuration has occurred.
User Response: This is a global configuration exception. Check previous
error log entries for previous configuration exceptions. If these problems are fixed, this
exception should cease to occur as well.
0x4942044C SOMBOIMHOME_IHOMEMINOR_SMOCOHOMENARROW
Explanation: The SMOCO Home could not be narrowed to a home of the
correct type.
User Response: Make sure your CDS default application was built
correctly.
0x4942044D SOMBOIM_IHOMEMINOR_BADPARAM_PO
Explanation: Contents of the key passed in invalid.
User Response: Check the contents of the key to determine if this is the
correct key for this particular object.
0x4942044D SOMBOIM_IHOMEMINOR_NO_MEMORY_CREATE_MO
Explanation: A memory error occurred during construction of a managed
object. Memory could not be extended in the heap.
User Response: Review the log and check to see why the heap could not be
used to create the object.
0x4942044D SOMBOIMHOME_IHOMEMINOR_SMOCONARROW
Explanation: The SMOCO could not be narrowed to the correct type.
User Response: Make sure your CDS default application was built
correctly.
0x4942044D SOMBOIM_IHOMEMINOR_UNKNOWN_CTOR
Explanation: An unexpected error occurred during the construction of a
home. This error means that the home caught an exception during its creation logic, and
has thrown this exception.
User Response: Check previous log entries to determine the nature of the
exception(s) prior to this exception.
0x4942044E SOMBOIM_IHOMEMINOR_BADPARAM_SYNCFROM
Explanation: The home could not retrieve all its data from the CDS or the
home could not configure itself from the data given.
User Response: Check the previous exception in the error log to see if a
configuration error occurred. If so, take action to correct the configuration value. If a
configuration error did not occur, check the previous entries in the log to see if the CDS
Data Object could not find a particular value in the CDS. If so, correct the CDS.
0x4942044E SOMBOIM_IHOMEMINOR_COMPLETEFAILED
Explanation: The SMOCO and its home could not be revived.
User Response: Make sure your CDS default application was built
correctly.
0x4942044E SOMBOIM_IHOMEMINOR_NO_MEMORY_CREATE_DO
Explanation: A memory error occurred during construction of a data
object. Memory could not be extended in the heap.
User Response: Review the log and check to see why the heap could not be
used to create the object.
0x4942044E SOMBOIM_IHOMEMINOR_UNKNOWN_DTOR
Explanation: An unexpected error occurred during the destruction of a
home. This error means that the home caught an exception during its destruction logic, and
has thrown this exception.
User Response: Check previous log entries to determine the nature of the
exception(s) prior to this exception.
0x4942044F SOMBOIM_IHOMEMINOR_BADPARAM_MIXIN
Explanation: The mixin type used can not be used by the home.
User Response: Check the type of the mixin.
0x4942044F SOMBOIM_IHOMEMINOR_NO_MEMORY_CREATE_PK
Explanation: A memory error occurred during construction of a primary
key. Memory could not be extended in the heap.
User Response: Review the log and check to see why the heap could not be
used to create the object.
0x4942044F SOMBOIM_IHOMEMINOR_UNKNOWN_CREATE_PK
Explanation: An unknown error occurred curing the creation of a primary
key
User Response: Check the logic of the keys constructor to see that is
behaving properly.
0x49420450 SOMBOIM_IHOMEMINOR_BAD_KEY
Explanation: Key component could not be created.
User Response: An internal error has occurred. Check for memory heap
overflows.
0x49420450 SOMBOIM_IHOMEMINOR_UNKNOWN_CREATE_FROM_PK
Explanation: During a creation, find, or reactivation, an unknown error
occurred.
User Response: This is a catcher exception. To find the cause of the
problem, examine the previous error log entries.
0x49420451 SOMBOIM_IHOMEMINOR_MCINIT
Explanation: The master container or bootstrap home failed to initialize.
User Response: Make sure your CDS default application was built
correctly.
0x49420451 SOMBOIM_IHOMEMINOR_NULL_DO_PARAM
Explanation: A null DO was passed into the home during an
initForReactivation call.
User Response: An internal error has occurred.
0x49420451 SOMBOIM_IHOMEMINOR_UNKNOWN_CREATE_DO
Explanation: An unknown error occurred curing the creation of a data
object.
User Response: Check the logic of the constructor for the data object to
see that is behaving properly.
0x49420452 SOMBOIM_IHOMEMINOR_PSTATE
Explanation: An error occurred as the result of the home processing its
state.
User Response: Check the associated message to see what has occurred.
Most often, this is the result of an object changing its state.
0x49420452 SOMBOIM_IHOMEMINOR_STATE
Explanation: An error occurred as the result of the home processing its
state.
User Response: Check to see that the home has a valid state attribute in
the CDS.
0x49420453 SOMBOIM_IHOMEMINOR_BAD_KC
Explanation: An error occurred processing the homeIdentification method
on the home.
User Response: Check the value of the managedObjectClass for the home and
make sure that it is valid.
0x49420453 SOMBOIM_IHOMEMINOR_UNKNOWN_CREATE_MO
Explanation: An unknown error occurred during the creation of a managed
object.
User Response: Check the logic of the constructor for the managed object
to see that is behaving properly.
0x49420454 SOMBOIM_IHOMEMINOR_UNKNOWN_DELETE_PK
Explanation: An unknown error occurred during the destruction of a
primary key.
User Response: Check the logic of the primary keys' destructor to see
that is behaving properly.
0x49420455 SOMBOIM_IHOMEMINOR_CREATE_DO
Explanation: An unknown error occurred during the creation of a data
object.
User Response: Check the logic of the constructor for the data object to
see that is behaving properly.
0x49420456 SOMBOIM_ICDSMINOR_IMKEYCOLLECTION_NOT_SET
Explanation: The key collection was not set in the CDS data object.
0x49420456 SOMBOIM_ICDSMINOR_INITDO_CDS
Explanation: A exception was thrown by the default data store.
User Response: See message log for more information.
0x49420456 SOMBOIM_ICDSMINOR_UNKNOWN
Explanation: An unexpected error occurred during an operation.
User Response: See message log for more details.
0x49420456 SOMBOIM_SMOCOMINOR_INTERNAL_FAILURE
Explanation: An internal failure occurred in the SMOCO. In most
situations this is caused by an incorrect CDS image.
User Response: Check the error log for more information.
0x49420457 SOMBOIM_ICDSMINOR_INITDO
Explanation: An unknown exception occurred while accessing the default
data store.
User Response: See message log for more information.
0x49420457 SOMBOIM_ICDSMINOR_REF_ELEMENT
Explanation: An error occurred while attempting to get a reference by
name.
User Response: See message log for more details.
0x49420458 SOMBOIM_ICDSMINOR_DELETE
Explanation: A delete of a CDS image did not complete, since the CDS
image was in the wrong state.
0x49420459 SOMBOIM_ICDSMINOR_GET_SET_ATTRIBUTE_FAILED
Explanation: An error occurred while using an attribute in the CDS.
User Response: See the message log for more details.
0x4942045A SOMBOIM_ICDSMINOR_INVALID_INDEX
Explanation: An invalid index was requested.
0x49420460 SOMBOIM_ICONTAINERMINOR_DEAD_STATE_CDS
Explanation: A container has reactivated in a terminating state.
User Response: The container is terminating and its image are deleted
from CDS. There is no action for this exception, it is informational only.
0x49420460 SOMBOIM_ICONTAINERMINOR_HEAP_OUT_OF_MEMORY
Explanation: Memory could not be allocated from a heap.
User Response: A heap could not extend during an allocation. Review the
logs to determine the heap and take action to allow it to extend.
0x49420460 SOMBOIM_ICONTAINERMINOR_NO_LOCALFRIENDQOS
Explanation: An object cannot register with a container.
User Response: The object lacks the interface needed to register with a
container. Refer to the programming documentation to determine the interface needed.
0x49420460 SOMBOIM_ICONTAINERMINOR_NOIMPLEMENT
Explanation: The invoked operation is not supported in the product or is
not valid on the target object.
User Response: Check that the operation being invoked and the runtime
type of the target object are compatible. Reference the documentation for the operation to
find out about any restrictions.
0x49420461 SOMBOIM_ICONTAINERMINOR_UNEXPECTED
Explanation: An unexpected error occurred during an operation.
User Response: This indicates a system type failure. Contact your service
provider for additional help.
0x49420461 SOMBOIM_ICONTAINERMINOR_UNKNOWN_HEAP
Explanation: An unexpected error occurred during the use of a heap.
User Response: Review the boimLog and the rootLog to determine the exact
cause of this failure and take the recommended action.
0x49420461 SOMBOIM_ICONTAINERMINOR_UNKNOWN_SETREFDATA
Explanation: The reference data received from the ORB is invalid.
User Response: Retry the operation, if the problem persists review the
objects key for valid character set and syntax. If this is not the problem contact your
service provider.
0x49420462 SOMBOIM_ICONTAINERMINOR_BAD_KEY
Explanation: The key provided is invalid or corrupted.
User Response: Retry the operation, if the problem persists review the
objects key for valid character set and syntax. If this is not the problem contact your
service provider.
0x49420463 SOMBOIM_ICONTAINERMINOR_NO_MORE_KEYS
Explanation: The provided key did not resolve an object.
User Response: The key has become corrupted. Resolve a new object
reference.
0x49420464 SOMBOIM_ICONTAINERMINOR_REACTIVATION_FAILED
Explanation: The object is not in memory and cannot be placed in memory.
User Response: This is an internal failure. Gather information from the
boimLog and rootLog and contact your service provider.
0x49420465 SOMBOIM_ICONTAINERMINOR_NO_ACTION_NECESSARY
Explanation: An internal exception has escaped to the user interface.
User Response: None, ignore this error.
0x49420466 SOMBOIM_ICONTAINERMINOR_CAN_NOT_HOLD_THIS_TRANSIENT
Explanation: A transient object is being resolved to an object that does
not exist in the container.
User Response: Create the object into the container before resolving it.
A transient object cannot be reactivated, it must be created before being referenced.
0x49420467 SOMBOIM_ICONTAINERMINOR_NO_HOMES_DEFINED
Explanation: A home cannot be found to create the requested object.
User Response: The container does not have a home capable of creating the
requested object. Review the containers backing store (CDS) to assure the objects home is
configured on this container. Review the logs (boimLog and rootLog) to assure the creation
of the home did not fail during container initialization.
0x4942047E RDBIM_XAConnMetaDataFailed
Explanation: A failure occurred when trying to access or use XA Connection
Metadata.
User Response: Look at the server's activity log for more information.
0x4942047F RDBIM_XAConnMgrFinderCreateFailed
Explanation: Internal Error: A failure occurred when trying to create the XA
Connection Manager Finder.
User Response: Report the problem to technical support.
0x49420480 RDBIM_XAConnMgrFindFailed
Explanation: Internal Error: A failure occurred when trying to find the requested
Connection Manager.
User Response: Report the problem to technical support.
0x49420481 RDBIM_XAConnectionFailed
Explanation: A failure occurred when trying to connect to the requested back end
database.
User Response: Look at the server's activity log for more information.
0x49420546 IOAABaseError
Explanation: Internal Error: The Oracle application adaptor has raised an
internal error.
User Response: Report the problem to technical support.
0x49420547 IOAConnMetaConver_CredentialMappingError
Explanation: The Oracle application adaptor failed while trying to do credential
mapping.
User Response: Look at the server's activity log for more information.
0x49420578
IDContextCoordinator_UnknownContextControlError
Explanation: Internal Error: The DB2 application adaptor has caught an unknown
error.
User Response: Report the problem to technical support.
0x49420579 IDContextControl_InternalError
Explanation: Internal Error: The DB2 application adaptor has raised an internal
error.
User Response: Report the problem to technical support.
0x4942058A DB2ConnMetaConverter_CredentialMappingError
Explanation: The DB2 application adaptor failed while trying to do credential
mapping.
User Response: Look at the server's activity log for more information.
0x494205DD IMQAAMinor_unexpectedException
Explanation: An unexpected exception has been caught by an object in the
MQSeries application adapter and this object is unable to process it. The exception is not
a CORBA standard exception nor a CORBA user exception. The CORBA::UNKNOWN exception is
thrown.
User Response: Investigate what your application was doing when the
exception was thrown. For example, which objects were involved, were they calling an
operating system function? Make sure your application has access to the resources it
requires and is using any services from the operating system or CBSeries correctly. Look
for other exceptions in the CBSeries activity.log and look at the Operating System
specific diagnostics, such the NT event log, as there may be additional messages which
indicate why the exception was thrown.
0x494205DE IMQAAMinor_duplicateKeyRaised
Explanation: A IDuplicateKey exception has been caught by the
MessageHome. This can be caused if the internal keys generated by the home wrap. This can
happen if a server is asked to put or get more than 4,294,967,296 messages before the
server is restarted. The IMessageHome::IMessagePutFailed exception is thrown.
User Response: Stop and restart the relevant server.
0x494205DF IMQAAMinor_noMessageOnQueue
Explanation: A INoObjectWKey exception has been caught by the
InboundMessageHome. This indicates that no message was available for the
InboundMessageHome. The IMessageHome::IMessageNotFound exception is thrown.
User Response: Wait for the message to arrive (e.g. by using message
triggering) and retry the operation
0x494205E0 IMQAAMinor_correlSerialVersionInvalid
Explanation: Attempt to construct ICBMQCorrelator from serialized form
failed as version numbers were not the same. The IBOIMException::IDataObjectFailed
exception is thrown.
User Response: This indicates an application error.
0x494205E1 IMQAAMinor_correlSerialMsgidInvalid
Explanation: Attempt to construct ICBMQCorrelator from serialized form
failed as msgIdOption was not valid. The IBOIMException::IDataObjectFailed exception is
thrown.
User Response: This indicates an application error.
0x494205E2 IMQAAMinor_correlSerialCorrelidInvalid
Explanation: Attempt to construct ICBMQCorrelator from serialized form
failed as correlIdOption was not valid. The IBOIMException::IDataObjectFailed
exception is thrown.
User Response: This indicates an application error.
0x494205E3 IMQAAMinor_correlMsgidInvalid
Explanation: Attempt to construct ICBMQCorrelator failed as msdIdOption
parameter was not valid. The IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205E4 IMQAAMinor_correlCorrelidInvalid
Explanation: Attempt to construct ICBMQCorrelator failed as
correlIdOption parameter was not valid. The IBOIMException::IDataObjectFailed exception is
thrown.
User Response: This indicates an application error.
0x494205E5 IMQAAMinor_putDispositionInvalid
Explanation: Attempt to set ICBMQPut disposition to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205E6 IMQAAMinor_putMsgtypeInvalid
Explanation: Attempt to set ICBMQPut msgType to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205E7 IMQAAMinor_putExpiryInvalid
Explanation: Attempt to set ICBMQPut expiry to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205E8 IMQAAMinor_putPriorityInvalid
Explanation: Attempt to set ICBMQPut priority to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205E9 IMQAAMinor_putPersistenceInvalid
Explanation: Attempt to set ICBMQPut persistence to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205EA IMQAAMinor_putAppltypeInvalid
Explanation: Attempt to set ICBMQPut putApplType to invalid value. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205EB IMQAAMinor_getIntervalInvalid
Explanation: Attempt to construct ICBMQGet failed as waitInterval not
>=0. The IBOIMException::IDataObjectFailed exception is thrown.
User Response: This indicates an application error.
0x494205EC IMQAAMinor_ConnectFailed
Explanation: A call to MQCONN failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205ED IMQAAMinor_OpenFailed
Explanation: A call to MQOPEN failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205EF IMQAAMinor_CloseFailed
Explanation: A call to MQCLOSE failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205F0 IMQAAMinor_DisconnectFailed
Explanation: A call to MQDISC failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205F1 IMQAAMinor_PutFailed
Explanation: A call to MQPUT failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205F2 IMQAAMinor_GetFailed
Explanation: A call to MQGET failed. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Examine the major and minor codes of the associated
IBOIMException::IDataObjectFailed. These correspond to the completion-code and reason-code
of the MQI call. Consult the appropriate MQSeries documentation to interpret these codes.
0x494205F3 IMQAAMinor_SecurityInternal
Explanation: An internal error occurred whilst calling the security
service. The IBOIMException::IDataObjectFailed exception is thrown.
User Response: Look for other exceptions in the CBSeries activity log
that might indicate errors in the CDS configuration.
0x494205F4 IMQAAMinor_NotAuthorized
Explanation: An MQOPEN failed with MQRC_NOT_AUTHORIZED. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: The AlternateUserId field of the ObjectDescriptor is set
to a user identifier that is mapped from either the delegated invocation credential of the
caller or the server's own credential. The type of credential is determined by the value
of the SecurityPolicy attribute on the RDBConnectionMetadata. The credential mapping is
performed for the security realm specified in the RDBConnectionMetadata for SecurityType
MQSecurity. Check that the security mapping for the specified realm returns a valid user
identifier for the target MQSeries queue.
0x494205F5 IMQAAMinor_NullQueueName
Explanation: A null queue name was passed to an ICBMQ constructor. The
IBOIMException::IDataObjectFailed exception is thrown.
User Response: Ensure that the constructor is passed a valid queue name
of type MQCHAR48.