<?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 = XD/ws/code/visualization.cacheservice/src/com/ibm/ws/xd/visualizationengine/cacheservice/util/RASCacheUtil.nlsprops -->
<!-- DO NOT EDIT THIS FILE - This file was generated by the XML/Html & Property emitter -->
<!-- BEGIN MESSAGES -->
<Message ID="WVCS0024I" severity="I" prefix="yes">
  <MsgText pgmKey="DISABLENONXD" varFormat="Java">
    DISABLENONXD=WVCS0024I: Custom property {0} located with a value of {1}.  Will not monitor any metrics in the {2} cache pertaining to non-XD nodes or their hosted servers.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0022W" severity="W" prefix="yes">
  <MsgText pgmKey="ALPHA_INT_ODC_READ_ERROR" varFormat="Java">
    ALPHA_INT_ODC_READ_ERROR=WVCS0022W: An exception, {0}, occured when trying to read the work profiler interval from the odc with message {1}.  Will use default the default interval of {2}.
  </MsgText>
  <Explanation>
    The odc tree could be malformed.
  </Explanation>
  <UserResponse>
    Please enable trace on the dmgr com.ibm.ws.odc.*=all.
  </UserResponse>
</Message>
<Message ID="WVCS0008W" severity="W" prefix="yes">
  <MsgText pgmKey="CP_REMOVED_TIME_FORMAT" varFormat="Java">
    CP_REMOVED_TIME_FORMAT=WVCS0008W: The cell level custom property xd.visengine.timestampformat was either removed or had is value cleared, timestamp formating will be removed for the visualization data logs.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS1000E" severity="E" prefix="yes">
  <MsgText pgmKey="WVCS_UNKNOWN_ERROR" varFormat="Java">
    WVCS_UNKNOWN_ERROR=WVCS1000E: Exception occurred in the visualization engine.  Exception was {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="WVCS0006I" severity="I" prefix="yes">
  <MsgText pgmKey="CP_NEW_TIME_FORMAT" varFormat="Java">
    CP_NEW_TIME_FORMAT=WVCS0006I: Custom cell property was either changed or added, changing the timestamp format for the visualization data logs to {0}
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0009W" severity="W" prefix="yes">
  <MsgText pgmKey="REMOVED_TIME_FORMAT" varFormat="Java">
    REMOVED_TIME_FORMAT=WVCS0009W: The timestamp configuration for the visualization data logs was cleared, timestamp formating will be removed for the visualization data logs.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0004W" severity="W" prefix="yes">
  <MsgText pgmKey="CP_INVALID_TIME_FORMAT" varFormat="Java">
    CP_INVALID_TIME_FORMAT=WVCS0004W: A cell custom property was found for specifying a format for the timestamps for the data logs, however the format provided, &quot;{0}&quot;, is invalid and can not be used.
  </MsgText>
  <Explanation>
    Please see the javadoc for SimpleDateFormat for valid patterns.
  </Explanation>
  <UserResponse>
    Please correct the pattern and save, the new format will dynamically be used once saved to the master repository.
  </UserResponse>
</Message>
<Message ID="WVCS0005W" severity="W" prefix="yes">
  <MsgText pgmKey="INVALID_TIME_FORMAT" varFormat="Java">
    INVALID_TIME_FORMAT=WVCS0005W: Specified timestamp for the data logs is invalid, &quot;{0}&quot;.  Unformatted timestamp will be used.
  </MsgText>
  <Explanation>
    Please see the javadoc for SimpleDateFormat for valid patterns.
  </Explanation>
  <UserResponse>
    Please correct the pattern and save, the new format will dynamically be used once saved to the master repository.
  </UserResponse>
</Message>
<Message ID="WVCS0010I" severity="I" prefix="yes">
  <MsgText pgmKey="APPLY_CONFIG_FORMAT" varFormat="Java">
    APPLY_CONFIG_FORMAT=WVCS0010I: Timestamp configuration for the visualization data logs was located, {0}, and will be applied to the visualization data logs.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0003I" severity="I" prefix="yes">
  <MsgText pgmKey="CP_FOUND_TIME_FORMAT" varFormat="Java">
    CP_FOUND_TIME_FORMAT=WVCS0003I: A cell custom property was found for specifying a format for the timestamps for the data logs, &quot;{0}&quot;.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0023W" severity="W" prefix="yes">
  <MsgText pgmKey="OLD_BG" varFormat="Java">
    OLD_BG=WVCS0023W: Background work statistic for node {0} in cell {1} is stale.  The background work value was last received at {2}, its submission interval is {3} seconds, and is being queried for use at {4}.
  </MsgText>
  <Explanation>
    This could be caused by communication problems between the XD work profiler and the Deployment Manager.
  </Explanation>
  <UserResponse>
    Please monitor the situation and call support if problem persists.
  </UserResponse>
</Message>
<Message ID="WVCS0013I" severity="I" prefix="yes">
  <MsgText pgmKey="UPDATING_WRITER_PROP_DT" varFormat="Java">
    UPDATING_WRITER_PROP_DT=WVCS0013I: Configuration for visualization data service has been modified and a new data transformer has been specified, updating data transformer for the data writer writing log {0}.  Please note that the transformation for the first data logged to the file after this change may not be accurate if data logging is already enabled.
  </MsgText>
  <Explanation>
    When a new data transformer is specified while data is actively being logged, the transformer could miss data some data from when the last data was logged and its instantiation.
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0007I" severity="I" prefix="yes">
  <MsgText pgmKey="NEW_TIME_FORMAT" varFormat="Java">
    NEW_TIME_FORMAT=WVCS0007I: A new timestamp format for the visualization data logs was specified, changing the timestamp format to {0}
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS0002W" severity="W" prefix="yes">
  <MsgText pgmKey="OLD_WASBG" varFormat="Java">
    OLD_WASBG=WVCS0002W: WebSphere background work statistic for node {0} in cell {1} is stale.  The WebSphere background work value was last received at {2}, its submission interval is {3} seconds, and is being queried for use at {4}.
  </MsgText>
  <Explanation>
    This could be caused by communication problems between the XD work profiler and the Deployment Manager.
  </Explanation>
  <UserResponse>
    Please monitor the situation and call support if problem persists.
  </UserResponse>
</Message>
<Message ID="WVCS0011I" severity="I" prefix="yes">
  <MsgText pgmKey="CP_FORMAT_PRECEDENCE" varFormat="Java">
    CP_FORMAT_PRECEDENCE=WVCS0011I: Timestamp configuration for the visualization data logs was located, {0}, however a cell level custom property, xd.visengine.timestampformat was also present and will take precedence unless its value was empty.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="WVCS1001E" severity="E" prefix="yes">
  <MsgText pgmKey="ERROR_CACHE_ACCESS" varFormat="Java">
    ERROR_CACHE_ACCESS=WVCS1001E: Exception occurred while trying to access the cache service.  Exception was {0}.
  </MsgText>
  <Explanation>
    The cache service may not have fully initialized.
  </Explanation>
  <UserResponse>
    Please try accessing the cache service again.
  </UserResponse>
</Message>
<Message ID="WVCS0012I" severity="I" prefix="yes">
  <MsgText pgmKey="UPDATING_WRITER_PROPS" varFormat="Java">
    UPDATING_WRITER_PROPS=WVCS0012I: Configuration for visualization data service has been modified, updating properties for the data writer writing log {0}.
  </MsgText>
  <Explanation>
    None
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<!-- END MESSAGES -->
</TMSSource>
