OMNIbus server components and probes migration tips for date/time formatting and parsing functions
zhenniyan 06000209QP Visits (2036)
OMNIbus server components and probes started to use ICU for date/time formatting and parsing in V7.3.0. We have seen some date/time formatting and parsing related problem recently. There are some tips to help your migration.
1) Minor incompatibility to OMNIbus versions prior to V7.3.0. You might want to check this table when you are migrating from a version older than V7.3.0.
Table 1. Compatibility for POSIX format in date and time conversion in V7.3.0
2) Timezone environment variable "NFT-1DFT" on AIX is not a valid timezone format supported by ICU. The alternative is to use other conventional timezone setting, e.g. TZ=”CET-1CEST”.
3) The functions that parse a string into date/time V7.3.0 and onwards can process the timezone information in the string, while the ones in older versions ignore the timezone. Your date/time functions might work "properly" with some workarounds in older version of OMNIbus. During migration, you should review your date/time parsing functions that could take a date/time string containing the timezone information - replace the POSIX format ( e.g, with % ) with the new ICU format, add format for timezone if it didn't exist in old version, make sure the format you choose match exactly the timezone representation in the string.
4) In generally during migration you'd better replace the old POSIX style format ( e.g. with % ) with the new ICU format in your date/time functions. The POSIX format with % is supported for backwards compatibility only, customer is strongly recommended to move to the new ICU format during migration.