Scheduled Jobs do not Run in Data Process Control

There is an intermittent issue in certain environments where scheduled jobs will not run on their scheduled data and time.  Upon further inspection of the supporting SQL Server Agent job, the following pattern will be exhibited:

• The job shows success
• The duration of the job shows that it ran in zero (0) seconds successfully
• The job even though it has run in the Agent, will not show in the Data Process Control history list

This problem is due to a rogue value in the  IU_SEC table in BPM Connect.  To solve this issue, apply the following scripts to the BPM Connect database in SQL Server.

• p_UI_SCHEDULE_BROKER_v2.6.sql
• p_UI_SCHEDULE_AGTBLD_v2.3.sql 

This is a related issue to the container issue, they are manifestations of the same issue:
http://bpmconnect.blogspot.com/2011/06/124-pack-hot-fix-for-container-process.html

This change is included in the 125 pack or greater.