<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="../../resources/stylesheets/wasmsgxml.css"?>
<TMSSource name="TivoliMessages" tmsVersion="1.0" xml:lang="en">
<!-- CMVC MSG File Name = ws/code/pmi.rm/src/com/ibm/ws/pmi/reqmetrics/reqmetrics.nlsprops -->
<!-- DO NOT EDIT THIS FILE - This file was generated by the XML/Html & Property emitter -->
<!-- BEGIN MESSAGES -->
<Message ID="PMRM0113E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0113E" varFormat="Java">
    PMRM0113E=PMRM0113E: Invalid attempt to enable null filter type
  </MsgText>
  <Explanation>
    The enableFilter Java Management Extensions (JMX) was called with a null filter type.
  </Explanation>
  <UserResponse>
    Specify a valid filter type to the enableFilter method.
  </UserResponse>
</Message>
<Message ID="PMRM0215W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0215W" varFormat="Java">
    PMRM0215W=PMRM0215W: The parameter that is passed to method {0}: parameter name {1}, value {2} is not valid. Use one of the following values instead: {3}
  </MsgText>
  <Explanation>
    The parameter that is passed to the PmiRmJmxService managed bean (MBean) object is not valid.
  </Explanation>
  <UserResponse>
    Pass a valid parameter.
  </UserResponse>
</Message>
<Message ID="PMRM0030E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0030E" varFormat="Java">
    PMRM0030E=PMRM0030E: No correlator is found in the stack. Expect one.
  </MsgText>
  <Explanation>
    The correlator stack is empty when it should not.
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0109E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0109E" varFormat="Java">
    PMRM0109E=PMRM0109E: JMX cannot access filters or enabled flags with null filter type
  </MsgText>
  <Explanation>
    A Java Management Extensions (JMX) method attempted to get or set a filter or filter enabled flag using a null filter type.
  </Explanation>
  <UserResponse>
    Specify a valid filter type to the JMX method.
  </UserResponse>
</Message>
<Message ID="PMRM0026E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0026E" varFormat="Java">
    PMRM0026E=PMRM0026E: Cannot find the component or request for the request type {0}
  </MsgText>
  <Explanation>
    A missing component or request type definition or wrong request type is passed
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0112E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0112E" varFormat="Java">
    PMRM0112E=PMRM0112E: Filter configuration not initialized for filter type {0}
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0214W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0214W" varFormat="Java">
    PMRM0214W=PMRM0214W: {0}: Wrong ARM agent type: {0}
  </MsgText>
  <Explanation>
    The Application Response Measurement (ARM) agent type is not set correctly.
  </Explanation>
  <UserResponse>
    Set the ARM agent type correctly when using the PmiRmJmxService managed bean (MBean) object.
  </UserResponse>
</Message>
<Message ID="PMRM0108E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0108E" varFormat="Java">
    PMRM0108E=PMRM0108E: Exception thrown {0}
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0025E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0025E" varFormat="Java">
    PMRM0025E=PMRM0025E: This method cannot be called on the interface class
  </MsgText>
  <Explanation>
    This method cannot be called on the interface class
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0111E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0111E" varFormat="Java">
    PMRM0111E=PMRM0111E: JMX cannot set filters or enabled flags to null values
  </MsgText>
  <Explanation>
    A Java Management Extensions (JMX) method attempted to set request metrics filters or enabled flags to null values.
  </Explanation>
  <UserResponse>
    Specify non-null filters and enabled flags to the JMX method.
  </UserResponse>
</Message>
<Message ID="PMRM0213W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0213W" varFormat="Java">
    PMRM0213W=PMRM0213W: {0}: The ARM transaction start handle does not match the one on stack, so do not call stop on this transaction
  </MsgText>
  <Explanation>
    The Application Response Measurement (ARM) transaction start handle does not match the one on stack.
  </Explanation>
  <UserResponse>
    Do not call stop on the ARM transaction.
  </UserResponse>
</Message>
<Message ID="PMRM0300I" severity="I" prefix="yes">
  <MsgText pgmKey="PMRM0300I" varFormat="Java">
    PMRM0300I=PMRM0300I: {0} config change committed
  </MsgText>
  <Explanation>
    This information is for informational purpose only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="PMRM0107E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0107E" varFormat="Java">
    PMRM0107E=PMRM0107E: Internal error: attempt to copy null filter
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0209W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0209W" varFormat="Java">
    PMRM0209W=PMRM0209W: Request metrics cannot make the call for {0} because there is no parent correlator in the stack
  </MsgText>
  <Explanation>
    Request metrics cannot make the call because there is no parent correlator in the stack.
  </Explanation>
  <UserResponse>
    The edge transaction must be traced.
  </UserResponse>
</Message>
<Message ID="PMRM0024E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0024E" varFormat="Java">
    PMRM0024E=PMRM0024E: This method cannot be called for Tivoli Agents
  </MsgText>
  <Explanation>
    This method cannot be called for Tivoli agents.
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0004I" severity="I" prefix="yes">
  <MsgText pgmKey="PMRM0004I" varFormat="Java">
    PMRM0004I=PMRM0004I: PmiRmInit servername={0}
  </MsgText>
  <Explanation>
    Performance Monitoring Infrastructure (PMI) request metrics has been initialized on the server. This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="PMRM0110E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0110E" varFormat="Java">
    PMRM0110E=PMRM0110E: Internal error. Filter configuration not previously initialized
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0212W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0212W" varFormat="Java">
    PMRM0212W=PMRM0212W: Request metrics finds an obsolete system property {0}. Its value is {1}, different from the relevant configuration data, whose value is {2}. The configuration data will be used and the property will be ignored.
  </MsgText>
  <Explanation>
    The obsolete system property has different value than the configuration data and can be ignored.
  </Explanation>
  <UserResponse>
    Decide what value should be used and set the correct configuration data on the administrative console for request metrics. Remove the obsolete system property.
  </UserResponse>
</Message>
<Message ID="PMRM0106E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0106E" varFormat="Java">
    PMRM0106E=PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0208W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0208W" varFormat="Java">
    PMRM0208W=PMRM0208W: Request metrics expects a PmiRmCallContext but gets a user PmiRmArmTx {0}
  </MsgText>
  <Explanation>
    Request metrics expects a PmiRmCallContext object but gets a user PmiRmArmTx object.
  </Explanation>
  <UserResponse>
    Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (ARM) stop call.
  </UserResponse>
</Message>
<Message ID="PMRM0023E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0023E" varFormat="Java">
    PMRM0023E=PMRM0023E: Underlying ArmTransaction is null
  </MsgText>
  <Explanation>
    The underlying ArmTransaction object is null.
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0003I" severity="I" prefix="yes">
  <MsgText pgmKey="PMRM0003I" varFormat="Java">
    PMRM0003I=PMRM0003I: {0}
  </MsgText>
  <Explanation>
    This is Performance Monitoring Infrastructure (PMI) request metrics timing information. This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="PMRM0019E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0019E" varFormat="Java">
    PMRM0019E=PMRM0019E: CallContext contains a null ArmTransaction
  </MsgText>
  <Explanation>
    The CallContext parameter contains a null ArmTransaction object.
  </Explanation>
  <UserResponse>
    The parameter must contain a non-null ArmTransaction object before calling the function.
  </UserResponse>
</Message>
<Message ID="PMRM0211W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0211W" varFormat="Java">
    PMRM0211W=PMRM0211W: Request metrics finds an obsolete system property {0}. Its value is {1}, same as the relevant configuration data. The configuration data will be used and the property will be ignored.
  </MsgText>
  <Explanation>
    The obsolete system property has the same value as the configuration data and can be ignored.
  </Explanation>
  <UserResponse>
    Remove the obsolete system property to avoid confusion.
  </UserResponse>
</Message>
<Message ID="PMRM0105E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0105E" varFormat="Java">
    PMRM0105E=PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0022E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0022E" varFormat="Java">
    PMRM0022E=PMRM0022E: PmiReqMetricsImpl is null
  </MsgText>
  <Explanation>
    The Prepare servers for request metrics collection check box is not selected, which causes Performance Monitoring Infrastructure (PMI) request metrics not be instantiated.
  </Explanation>
  <UserResponse>
    Select the Prepare servers for request metrics collection check box in the administrative console, save the change, and restart the application server.
  </UserResponse>
</Message>
<Message ID="PMRM0207W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0207W" varFormat="Java">
    PMRM0207W=PMRM0207W: Request metrics has to pop user PmiRmArmTx from the correlator stack {0}
  </MsgText>
  <Explanation>
    Request metrics expects a request metrics context but gets a user PmiRmArmTx object.
  </Explanation>
  <UserResponse>
    Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (ARM) stop call or forget to pop.
  </UserResponse>
</Message>
<Message ID="PMRM0002E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0002E" varFormat="Java">
    PMRM0002E=PMRM0002E: Failed to instantiate: {0}
  </MsgText>
  <Explanation>
    Request metrics was unable to instantiate the class.
  </Explanation>
  <UserResponse>
    Verify that the class name is correct and that all its dependencies are satisfied.
  </UserResponse>
</Message>
<Message ID="PMRM0018E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0018E" varFormat="Java">
    PMRM0018E=PMRM0018E: CallContext contains a null correlator
  </MsgText>
  <Explanation>
    The CallContext parameter contains a null correlator.
  </Explanation>
  <UserResponse>
    The parameter must contain a non-null correlator before calling the function.
  </UserResponse>
</Message>
<Message ID="PMRM0210W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0210W" varFormat="Java">
    PMRM0210W=PMRM0210W: {0}: Request metrics expects a correlator in the stack but cannot find one.
  </MsgText>
  <Explanation>
    Request metrics did not pass the context information when Web services was disabled.
  </Explanation>
  <UserResponse>
    Pass the context data no matter if Web services is enabled or not so that at Web services outbound, the correlator can be accessed and passed along in the SOAP (formerly known as Simple Object Access Protocol) header.
  </UserResponse>
</Message>
<Message ID="PMRM0104E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0104E" varFormat="Java">
    PMRM0104E=PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0206W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0206W" varFormat="Java">
    PMRM0206W=PMRM0206W: Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction
  </MsgText>
  <Explanation>
    Request metrics users cannot reset the PmiRmArmStack class because request metrics starts the edge transaction.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="PMRM0021E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0021E" varFormat="Java">
    PMRM0021E=PMRM0021E: Parameter passed is null
  </MsgText>
  <Explanation>
    A null parameter was passed.
  </Explanation>
  <UserResponse>
    The parameter must be non-null before calling the function.
  </UserResponse>
</Message>
<Message ID="PMRM0001I" severity="I" prefix="yes">
  <MsgText pgmKey="PMRM0001I" varFormat="Java">
    PMRM0001I=PMRM0001I: ARM implementation is: {0}
  </MsgText>
  <Explanation>
    The name of the Application Response Measurement (ARM) implementation class. This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="PMRM0017E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0017E" varFormat="Java">
    PMRM0017E=PMRM0017E: CallContext passed is null
  </MsgText>
  <Explanation>
    The PmiRmCallContext parameter passed was null.
  </Explanation>
  <UserResponse>
    Verify that the parameter is non-null before calling the function
  </UserResponse>
</Message>
<Message ID="PMRM0103E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0103E" varFormat="Java">
    PMRM0103E=PMRM0103E: Error registering PmiRmJmxService MBean
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0020E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0020E" varFormat="Java">
    PMRM0020E=PMRM0020E: External Component attempted to peek Request Metrics correlator. This operation is not allowed.
  </MsgText>
  <Explanation>
    An external component attempted to peek request metrics correlator which is not allowed.
  </Explanation>
  <UserResponse>
    Verify that the parameter contains a non-null correlator before calling the function.
  </UserResponse>
</Message>
<Message ID="PMRM0102E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0102E" varFormat="Java">
    PMRM0102E=PMRM0102E: Method setData called with no incoming correlator.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0101E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0101E" varFormat="Java">
    PMRM0101E=PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0100E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0100E" varFormat="Java">
    PMRM0100E=PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0116E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0116E" varFormat="Java">
    PMRM0116E=PMRM0116E: Exception during startup configuration
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0033E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0033E" varFormat="Java">
    PMRM0033E=PMRM0033E: ARM API {0} returns error code {1}
  </MsgText>
  <Explanation>
    The call to the Application Response Measurement (ARM) application programming interface (API) failed.
  </Explanation>
  <UserResponse>
    The ARM agent must be started. Disable and enable ARM again from the administrative console.
  </UserResponse>
</Message>
<Message ID="PMRM0029E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0029E" varFormat="Java">
    PMRM0029E=PMRM0029E: Cannot perform {0} on correlation service when Request Metrics is disabled
  </MsgText>
  <Explanation>
    Cannot perform peek on correlation service when request metrics is disabled.
  </Explanation>
  <UserResponse>
    Enable request metrics first and then perform peek on correlation service.
  </UserResponse>
</Message>
<Message ID="PMRM0115E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0115E" varFormat="Java">
    PMRM0115E=PMRM0115E: Internal error.  Stack not empty at end of request
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0032E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0032E" varFormat="Java">
    PMRM0032E=PMRM0032E: An exception occurred when parsing the incoming correlator {0}.
  </MsgText>
  <Explanation>
    This problem results from an internal error. The incoming correlator might have an incorrect format.
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0028E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0028E" varFormat="Java">
    PMRM0028E=PMRM0028E: The PmiRmArmTx peeked off the stack is null
  </MsgText>
  <Explanation>
    The PmiRmArmTx object peeked off the stack is null.
  </Explanation>
  <UserResponse>
    The PmiRmArmTx object peeked off the stack must be non-null.
  </UserResponse>
</Message>
<Message ID="PMRM0114E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0114E" varFormat="Java">
    PMRM0114E=PMRM0114E: Unable to determine pid.
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0200W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0200W" varFormat="Java">
    PMRM0200W=PMRM0200W: Failed to instantiate {0}
  </MsgText>
  <Explanation>
    This exception is unexpected. The cause is not immediately known.
  </Explanation>
  <UserResponse>
    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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
  </UserResponse>
</Message>
<Message ID="PMRM0216W" severity="W" prefix="yes">
  <MsgText pgmKey="PMRM0216W" varFormat="Java">
    PMRM0216W=PMRM0216W: Duplicate registration with the existing registration id {0}: component name {1}, identity {2}.
  </MsgText>
  <Explanation>
    A component register with request metrics multiple times with the same identity parameter.
  </Explanation>
  <UserResponse>
    Do not register multiple times or pass a different identity parameter.
  </UserResponse>
</Message>
<Message ID="PMRM0031E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0031E" varFormat="Java">
    PMRM0031E=PMRM0031E: Got a null thread context.
  </MsgText>
  <Explanation>
    Cannot get thread context from request metrics.
  </Explanation>
  <UserResponse>
    This is an internal error. Restart the application server and try again.
  </UserResponse>
</Message>
<Message ID="PMRM0027E" severity="E" prefix="yes">
  <MsgText pgmKey="PMRM0027E" varFormat="Java">
    PMRM0027E=PMRM0027E: The PmiRmArmTx passed as a parameter is null
  </MsgText>
  <Explanation>
    The Correlation Service Arm wrapper (PmiRmArmTx object) passed as a parameter is null.
  </Explanation>
  <UserResponse>
    The PmiRmArmTx object must be non-null.
  </UserResponse>
</Message>
<!-- END MESSAGES -->
</TMSSource>
