RASD

RASD0001W: Parsing error in Registration xml {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

RASD0002W: No rule parameter names

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0003I: No AlertConfig object for AlertKey {0}

Explanation

This message is for informational purpose only.

Action

RASD0004W: Method called with a null parameter. This is invalid.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0005W: Method called with an invalid paramter of: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0006W: JMX Error Info: ObjectName: {0} Other1: {1} Other2: {2} Other3: {3}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0007W: Diagnostic Provider Registry Propagation failed because {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0008W: Regular Expression String is invalid {0}

Explanation

Regular expression compilation of the string failed

Action

If part of setStateCollectionSpec, then re-specify string to be a valid entry

RASD0009W: ApplicationException in evaluteTriggerConditions {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0010W: Runtime Throwable Exception in evaluteTriggerConditions

Explanation

The evaluateTriggerConditions created a lower level exception.

Action

Review the exception for further details.

RASD0011W: Invalid object type of {0} in DiagnosticEvent HashMap

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0012I: Updating State Collection Spec from {0} to {1}

Explanation

The State Collection Specification was updated, this is an informational message

Action

No user action required

RASD0013W: Attempting to update State Collection spec, but new spec is null

Explanation

The State Collection Spec passed in to the method was null

Action

If this is a result of invalid data due to driving an MBean method, review your procedures

RASD0014W: Attempting to update State Collection spec, but new spec is invalid {0}

Explanation

The State Collection Spec passed in to the method was invalid

Action

If this is a result of invalid data due to driving an MBean method, review your procedures

RASD0015W: Retrieve of DiagnosticConfig object for DPName, DPName passed in was null

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0016W: CBE Completion Exception Populating CBE

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0017W: CBE Completion Exception Populating CBE, type {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0018W: Exception retrieving the DTD for parsing DiagnosticProvider.xml

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0019W: Exception resulted from z/OS Servant MBean JMX call

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0020W: JMX Query to create an ObjectName threw exception

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0021W: JMX Call threw exception

Explanation

An exception occurred in a JMX invocation

Action

See prior exception for further details

RASD0022W: Registry result: {0} could not be parsed

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0023W: No DPName associated with that DPID: {0}

Explanation

Diagnostic Provider ID is not registered and, thus has no Diagnostic Provider Name associated with it

Action

Verify that the Diagnostic Provider ID was entered accurately

RASD0024W: Failed to activateMBean w/exception: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0025W: Aggregator called with an invalid method of: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0026I: Null MessageDataElement on CBE, could not get ResourceBundleName

Explanation

CBE was created with a ResourceBundle, so no localization will be taking place

Action

No User Action Required

RASD0027W: CommonBaseEventDiagnosticEventImpl constructed with null CBE

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0028W: No Extended Data Element found for this CBE

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0029W: InstanceId of {0} not fully parseable to WebSphere topology elements

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0030W: Failed to find property {0} in Hash/Property Lookup

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0031W: No Bean or hashMap data held

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0032W: Admin Service null, should exists, cannot register with DiagnosticService MBean

Explanation

This is a sample message, don""t sweat it

Action

This is a sample message, don""t sweat it at all

RASD0033W: Multiple DiagnosticService MBeans found: {0}. Should be just 1.

Explanation

This is a sample message, don""t sweat it

Action

This is a sample message, don""t sweat it

RASD0034W: No rule/configuration data found for AlertKey: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0035I: No configuration registry data found of type {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0038I: Failed to send alert, DiagnosticEvent getContent did not return a CBE

Explanation

This exception is unexpected. The cause is not immediately known.

Action

RASD0039W: Because the WsLogRecord log record did not contain information for the CommonBaseEvent class, the WsLogRecord log record could not be processed to generate a diagnostic alert: {0}

Explanation

An error occurred when attempting to generate a diagnostic alert.

Action

See the problem determination information on the WebSphere Application Server Support web page: https://ibm.biz/BdztgV.

RASD0041W: Error processing DiagnosticProvider XML: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action