Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 5.0.0 and later
Information in this document applies to any platform.
When the Provisioning Interface's (PI) localTZ parameter is configured then the PI will use this timezone (TZ) value to convert stored dates when sending and receiving dates used in commands. Example of setting the localTZ parameter:
This shows how the activation date send and the generated error response activiation date timestamps are different. In the examples above the time shift is 5 hours, which means that the generated error date is being displayed in the local machine time of GMT (or UTC). The expected result is that the activation date values for sent command and generated error responses be the same.
Note that the timestamp sent in the PI command is correct and that it is only the error response date that is displayed incorrectly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms