E-ETC-102-036 Fail to parse date string: %0s using format: %1s. Error code: %2s

Explanation

The following example shows how this message is written to the log:
Error: E-ETC-102-036: Fail to parse date string:
 Tue DEC 19 18:33:11 JST 2010
 using format: %a %b %e %T %Y.
 Error code: U_PARSE_ERROR

This error messages indicates that a probe failed to parse a date string.

The example error message was written to a probe log file. In this example, the error occurs because the date and time pattern %a %b %e %T %Y does not match the date string, which includes time zone information (JST).

System action

Not applicable.

User response

Not applicable.

Administrator response

To address the problem indicated by the example error message, add the time zone information to the pattern. For example, use the pattern %a %b %e %T %Z %Y to define the time string Tue DEC 19 18:33:11 JST 2010.

However, because JST is not a standard time zone identifier supported by ICU, the time string Tue DEC 19 18:33:11 JST 2010 still causes a parse error. The solution is to use an unambiguous time zone identifier equal to JST, for example, Tue DEC 19 18:33:11 GMT+9 2010.

This error does not occur in versions of Tivoli Netcool/OMNIbus earlier than V7.3 because those versions ignore time zone information. In Tivoli Netcool/OMNIbus V7.3, POSIX date and time patterns were deprecated in favor of Locale Data Markup Language (LDML) date and time patterns that are provided by International Components for Unicode (ICU) libraries. Whenever possible, replace POSIX patterns in probe rules files with LDML patterns.