A fix is available
APAR status
Closed as program error.
Error description
If you design a UCA for repeated execution, you might experience the case that the first execution happens on the defined time, while all subsequent executions are moved by one or more hours. This situation can happen, if the Process Server and the Database are running on different time zones. This fix solves this situation so that the UCA execution takes place always on the scheduled Process Server time.
Local fix
N/A
Problem summary
Time-elapsed UCA are rescheduled incorrectly if Process Server and Database are in different time zones. If you design a UCA for repeated execution, you might experience the case that the first execution happens on the defined time, while all subsequent executions are moved by one or more hours. This situation can happen, if the Process Server and the Database are running on different time zones. This fix solves this situation so that the UCA execution takes place always on the scheduled Process Server time. Hint: if the Process Server runs on Linux, the UCA's schedules are meant without daylight savings time. Additional Information: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.j sp?topic=%2Fcom.ibm.wbpm.wle.editor.doc%2Fmodeling%2Ftopic%2Fusi ng_undercover_agents_B.html describes how to define an UnderCover Agent for a scheduled event. In bullet 10, the sample shows how to define the schedule to fire at midnight. The time specification "midnight" is interpreted as the point in time, where the process server machine's clock reaches 24:00 local time. This means, that the local timezone setting of the process server machine is used. In case of clustered process servers, the process servers must be set to the same time zone, and their clocks should be synchronized. For scheduled Undercover Agents, the clocks' times must not differ for more than 2.5 minutes. The process server's databases may reside on a remote machine, and this machine may have different timezone and time setting. Changes to timezone or time setting on process server or database machines may cause already scheduled Undercover Agents to run at an unexpected time. However, all subsequent executions of the Undercover Agents are performed according to the specification, interpreted as usual: according to the current time zone and time setting of the systems.
Problem conclusion
Problem fixed iFix available on top of V751 GA
Temporary fix
Comments
APAR Information
APAR number
JR43099
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-14
Closed date
2012-08-28
Last modified date
2012-08-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
R751 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1"}]
Document Information
Modified date:
06 October 2021