Script Functions using attribute EARLIEST_STARTTIME fail with errors when correct format “HHMMSS” is used

Document ID : KB000085097
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U00020437 Runtime error in object '[OBJECTNAME]', line '[LINE-NR]': Time '' does not correspond to time format 'HHMMSS'.

Using Script Functions "MODIFY_UC_OBJECT" or "MODIFY_OBJECT" with the attribute "EARLIEST_STARTTIME" formatted correctly as 'HHMMSS' fail with the above error message.

This attribute works correctly in v9 and v10 but fails when using v11.2.2 or v11.2.3.

Investigation

The following script line is formatted correctly (using 'HHMMSS'):

 
:set &EARLIEST_STARTTIME# = sys_time('HHMMSS')
:set &EARLIEST_STARTTIME# = ADD_TIME(&EARLIEST_STARTTIME#,'001000')
:SET &MODOBJ# = MODIFY_UC_OBJECT(&$PROCESSOR_RUNID#, EARLIEST_STARTTIME, "MODIFY_UC_OBJECT.003", &EARLIEST_STARTTIME#)

Actual:  The script fails with the U00020437 error reference above and the attribute is not evaluated.

Expected:  The attribute should evaluate correctly and the script should complete successfully.

Reference

Automation Engine v11.2 Documentation:
 

 
 
Cause:
Cause type:
Defect
Root Cause: The Script Functions does not work with attribute EARLIEST_STARTTIME. Scripts cancelled with error: "U00020437 Runtime error in object 'TASK.1' line '00004': Time ;; does not correspond to time format 'HHMMSS'." because it was not recognizing 'HHMMSS'.
Resolution:
Update to a fix version listed below or a newer version if available.

Fix Status: Released

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

Automation Engine 11.2.4 - Available
Additional Information:
Workaround :
N/A