ACTIVATE_UC_OBJECT ignores exceeded start time when object with period container was started earlier

Article Id: 84930
Status: Published
Updated On: 15-04-2018 08:06
Legacy Id: 000009751
Products:
CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction:

Error Message :
N/A

A Task is:

  1. started by an ACTIVATE_UC_OBJECT task
  2. started with an exceeded earliest start time
  3. AFTER a Task with a started period container
Result: The earliest start time of the started Task is ignored.

Example:
 
:set &runid# = activate_uc_object('CCALL.SCRI.WAIT', , , 'TZ.CET', "2017-03-30 01:30:00")
:set &runid# = activate_uc_object('CCALL.SCRI.WAIT', , , 'TZ.CET', "CCALL.PERIOD.WAIT")
:set &runid# = activate_uc_object('CCALL.SCRI.WAIT', , , 'TZ.CET', "2017-03-30 02:30:00")

Expected:  The third activated task’s earliest start time is ignored, as well as the second’s. 
The third task should maintain its start time and get an ENDED_TIMEOUT status, since the start time is exceeded.
 
Actual:  The third activated task’s earliest start time is ignored, as well as the second’s.
The third task’s earliest start time is ignored and so the status does not change to ENDED_TIMEOUT even though the start time was actually exceeded.
 

Cause:

Cause type:
Defect
Root Cause: ACTIVATE_UC_OBJECT with a specific start time does not work after being invoked with a period object.

Environment:

OS Version: N/A

Resolution:

Update to a fix version listed below or a newer version if available.

Fix Status: In Progress

Fix Version(s):
Component(s): AE Server and Initialdata

Automation Engine 12.1.0 - Available
Automation Engine 12.0.2 - Available
Automation Engine 11.2.5 - Available

Additional Information:

Workaround :
Change the sequence of the tasks so that the Tasks inside the period container are activated at the end of the list.