WebSphere Performance Monitoring Request MetricsPMRM0001I: ARM implementation is: {0}
Explanation
The name of the ARM implementation class
User Response:
No action required
PMRM0002E: Failed to instantiate: {0}
Explanation
Request Metrics was unable to instantiate the class
User Response:
Verify that the class name is correct and that all its dependencies are satisfied
Explanation
PMI Request Metrics timing information
User Response:
No action required
PMRM0004I: PmiRmInit servername={0}
Explanation
PMI Request Metrics has been initialized on server
User Response:
No action required
PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0102E: Method setData called with no incoming correlator.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0103E: Error registering PmiRmJmxService MBean
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0107E: Internal error: attempt to copy null filter
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0108E: Exception thrown {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0109E: JMX cannot access filters or enabled flags with null filter type
Explanation
JMX method attempted to get or set a filter or filter enabled flag using a null filter type
User Response:
Specify a valid filter type to JMX method
PMRM0110E: Internal error. Filter configuration not previously initialized
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0111E: JMX cannot set filters or enabled flags to null values
Explanation
A JMX method attempted to set Request Metrics filters or enabled flags to null values
User Response:
Specify non-null filters and enabled flags to JMX method
PMRM0112E: Filter configuration not initialized for filter type {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0113E: Invalid attempt to enable null filter type
Explanation
JMX method enableFilter was called with a null filter type
User Response:
Specify a valid filter type to the enabledFilter method
PMRM0114E: Unable to determine pid.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0115E: Internal error. Stack not empty at end of request
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0116E: Exception during startup configuration
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0200W: Failed to instantiate {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
PMRM0300I: {0} config change committed
Explanation
Config change committed
User Response:
No action required