TRAS

TRAS0004E: Unable to create or open the service log file {0}. The following exception was encountered {1}
TRAS0005E: Unable to write to the service log. The following exception was encountered {0}
TRAS0006E: Unable to change the size of the service log. The following exception was encountered {0}
TRAS0007I: Logging to the service log is disabled
TRAS0008E: Failed to open trace log file {0} {1}
TRAS0009I: Defaulting trace output to SystemOut.log
TRAS0010I: The size of the service log indicates that some corruption has occurred. This could be due to not transferring the file in binary mode
TRAS0011I: {0} messages could not be read from the service log
TRAS0012W: {0} was specified in the configuration information as the name of the file to use for the {1} stream. This is not a legal name. {2} will be used instead
TRAS0013E: An attempt to redirect the {0} stream failed. The following exception was encountered. {1}
TRAS0014I: The following exception was logged {0}.
TRAS0015E: Unable to schedule time-based rollover for log file {0}. Size-based rollover will be used instead {1}.
TRAS0016E: An unexpected exception while trying to archive log file {0} Exception is {1}.
TRAS0017I: The startup trace state is {0}.
TRAS0018I: The trace state has changed. The new trace state is {0}.
TRAS0019I: Defaulting trace output to the circular memory buffer.
TRAS0020W: Trace might not be enabled properly due to syntax errors found in the trace string, {0}.
TRAS0021W: An invalid level name {0} was used as the filter level for the logging agent handler configuration.
TRAS0022I: The logging agent handler is disabled.
TRAS0023I: The logging agent handler is enabled. Filter level is set to {0}.
TRAS0024I: Log entry is of size {0} bytes which is too large to be added to log stream which is configured for {1} byte records. Log entry will not be logged to the log stream.
TRAS0025E: Unable to load source file {0}.
TRAS0026E: Unable to open destination file {0}.
TRAS0027E: Insufficient memory to process source file {0}.
TRAS0028I: The trace output is stored in the circular memory buffer, holding {0} message objects.
TRAS0029I: Could not dump ring buffer to specified directory, {0}. Dumped to default file, {1}.
TRAS0030W: Failed to dump ring buffer to specified file, {0}, or the default dump file location, {1}. Exceptions: {2} {3}
TRAS0031W: Unable to rename file {0} to {1} during log file rollover. Attempting to copy file contents.
TRAS0100E: Empty string is not part of trace string grammar
TRAS0101E: Empty string encountered - remove extra colon
TRAS0102E: No type=state value pair(s) found at ''{0}''
TRAS0103E: No component name found at ''{0}''
TRAS0104E: Missing type=state value pair at ''{0}''
TRAS0105E: Invalid type=state value pair - ''{0}'' at ''{1}''
TRAS0106E: Missing state value at ''{0}''
TRAS0107E: Missing type value at ''{0}''
TRAS0108E: Invalid type value - ''{0}'' at ''{1}''
TRAS0109E: Invalid state value - ''{0}'' at ''{1}''
TRAS0110E: The extension name ''{0}'' is reserved
TRAS0111I: The message IDs that are in use are deprecated
TRAS0112E: Null value returned on call to InetAddress.getLocalHost().getHostName().
TRAS0113I: This MBean Operation should not be used when High Performance Logging is enabled. Function will be forwarded to proper MBean
TRAS0115W: Exception resulted from z/OS Servant MBean JMX call
TRAS0116W: JMX Error Info: ObjectName: {0} Other1: {1} Other2: {2} Other3: {3}
TRAS0117W: Method called with a null parameter. This is invalid {0}.
TRAS0118W: Diagnostic Provider Registry Propagation failed because {0}
TRAS0150W: Invalid Logger Regular Expression {0}, no Logger Checking Enabled
TRAS0210I: The JNI call could not go thru.
TRAS0220I: The number of dropped messages: {0}
TRAS0230I: The message time stamp exceeded end time.
TRAS0240I: Logstream {0} does not contain any records beyond start time {1}.
TRAS0250W: The {0} on logstream {1} returned a warning - return code {2}, reason code {3}
TRAS0260I: The {0} on logstream {1} returned more than 500 messages in the buffer. Excess messages were discarded.
TRAS0270E: Failed to connect to logstream {1} - return code {2}, reason code {3}
TRAS0280E: Failed to open logstream {1} with return code {2}, reason code {3}


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ejs.resources.RasMessages.dita
File name: com.ibm.ejs.resources.RasMessages.html