Explanation | A replication instance has launched successfully for the specified application server component. |
Action | No action is required. |
Explanation | A replication instance has been able to establish communication with a partner replication instance. |
Action | No action is required. |
Explanation | A replication instance is unable to communicate with a partner replication instance. |
Action | No action is required. |
Explanation | The messaging transport used by a replication instance is congested and is temporarily unable to send or receive messages. |
Action | No action is required. |
Explanation | The messaging transport used by a replication instance is no longer congested and is able to send and receive messages. |
Action | No action is required. |
Explanation | A replication instance has been terminated by the specified application server component. |
Action | No action is required. |
Explanation | The application server has changed the replication instance group to which it belongs. |
Action | No action is required. |
Explanation | A runtime exception has occurred. |
Action | No action is required. |
Explanation | An exception was caught while initializing message transport. |
Action | No action is required. |
Explanation | An exception was caught while attempting to send or receive a message. |
Action | No action is required. |
Explanation | An exception was caught while creating a reference in the specified method. |
Action | No action is required. |
Explanation | An exception was caught in the specified method. |
Action | No action is required. |
Explanation | An exception was caught in the specified method. |
Action | No action is required. |
Explanation | The specified method can only be used in a controller environment. |
Action | No action is required. |
Explanation | An exception was caught while creating a callback in the specified method. |
Action | No action is required. |
Explanation | A factory could not be located for the specified data replication service (DRS) user. |
Action | No action is required. |
Explanation | The specified method could not determine the factory type. |
Action | No action is required. |
Explanation | The specified method was invoked with a null token. |
Action | No action is required. |
Explanation | The specified method was invoked to add an already existing token. |
Action | No action is required. |
Explanation | The specified method was invoked to delete a token that does not exist. |
Action | No action is required. |
Explanation | An exception was caught while creating a DRSControllerProxy reference in the specified method. See the error log for more information. |
Action | No action is required. |
Explanation | A remote exception was caught while creating a reference in the specified method. See the error log for more information. |
Action | No action is required. |
Explanation | The servant is registered, but the key for the servant token appears in the unregistered table. |
Action | No action is required. |
Explanation | The servant is registered, but the key for the servant token does not appear in the registered table. |
Action | No action is required. |
Explanation | The servant is unregistered, but the key for the servant token appears in the registered table. |
Action | No action is required. |
Explanation | The wrapper for the servant token is null for the given data replication service (DRS) instance. |
Action | No action is required. |
Explanation | The unregistered table contains the key for the servant token, but the entry could not be retrieved from the table. |
Action | No action is required. |
Explanation | The drsInstanceToken does not match tmp2. |
Action | No action is required. |
Explanation | The data replication service (DRS) was unable to convert a byte array to an object in the specified method. |
Action | No action is required. |
Explanation | The returned byte array is null in the specified method. |
Action | No action is required. |
Explanation | The proxy could not be created for the specified servant token. |
Action | No action is required. |
Explanation | The servant token could not be located in the registeredServantTokens table. |
Action | No action is required. |
Explanation | The specified method was invoked in an incorrect environment. |
Action | No action is required. |
Explanation | The call to registerServant returned null. |
Action | No action is required. |
Explanation | The value specified for stoken does not match the value specified for stokenTest. |
Action | No action is required. |
Explanation | The registration token is null. |
Action | No action is required. |
Explanation | The the value specified for servantInitStoken does not match the value specified for initStoken. |
Action | No action is required. |
Explanation | The confirmation token is not marked confirmed. |
Action | No action is required. |
Explanation | The specified token is not in the token table. |
Action | No action is required. |
Explanation | The specified method encountered an instanceOffset error while processing the token. |
Action | No action is required. |
Explanation | An Error occurred while the data replication service (DRS) was accessing the native data store. |
Action | No action is required. |
Explanation | The designated servant has completed data replication service (DRS) initialization. |
Action | No action is required. |
Explanation | The designated servant has shutdown. |
Action | No action is required. |
Explanation | The designated servant has terminated. |
Action | No action is required. |
Explanation | The data replication service (DRS) was unable to communicate with the high availability manager. |
Action | No action is required. |
Explanation | The data replication service (DRS) ONLY starts on a federated application server node or the zOS Control & Servant region. |
Action | No action required. |
Explanation | The data replication service (DRS) ONLY starts when a replication domain has been configured in the multibroker.xml |
Action | If the intent is to enable cache replication, please create replication domain/s via the wsadmin scripting interface or the admin console. |
Explanation | Encryption of replication data can be accomplished by using the DCS-Secure channel transport for the core group. |
Action | Set the Transport type to Channel framework and the Transport chain to DCS-Secure if replication data needs to be encrypted. |