AEH Message logs-EH
- AEH Message logs
A work-around was successful at the Merck - Ballydine site. The key is to force the AEH software to recalculate the UTC -> LocalTime offset value. This can be done by forcing an AEH utility to execute:From an HPTerm: ps -ef | grep hsModInterface-- to get the PID of the hsModInterface process kill -SIGUSR2 hsModInterface pid-- send the SIGUSR2 signal to the hsModInterface processThis action causes a utility to run and dump information to the file /usr/tmp/mod1.stats. This action also forces the recalculation of the offset, and in the MSD case it cleared up the problem.
- AEH Message Logs - Time is off by 1 hour after time shift (EDT --> EST)
AEH Message logs are indicating the wrong time for PDL Messages. The actual messages are time stamped correctly, which indicates that the time in the Controller is accurate. However, the AEH Log time in the Message Log presentation is off by 1 hour.I received an example of this from Merck - Ballydine. The problem was specific to the AEH 2.0, because they still have an IMS 1.3 which did not exhibit the problem.Scott Bundonis explained in more detail than I need to go into here the problem (at least part of it). An 'offset' is calculated to convert UTC time to Local time. This 'offset' is calculated initially and whenever a message from a different 'time season' is received, and used for all subsequent conversions. There appears to be a bug which allows the 'offset' to be calculated incorrectly under certain conditions (this is not completely understood at this point).