[AWA] EARLIEST_STARTTIME (in MODIFY_UC_OBJECT) returns error when used with non-default format

Article Id: 128846
Status: Published
Updated On: 05-03-2019 21:37
Products:
CA Automic Workload Automation - Automation Engine , AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction:

EARLIEST_STARTTIME (in MODIFY_UC_OBJECT) returns error when used with non-default format 

Reproduction steps:

  • Create a work flow with child tasks 
  • Set a script with MODIFY_UC_OBJECT(<JOBP's runID>,EARLIEST_STARTTIME, <child task's name>, "HHMM;&TIME#") with &TIME# and format (HHMM) freely defined 
Example:
:SET &hnd# = MODIFY_UC_OBJECT(&runid#, EARLIEST_STARTTIME, "&taskname#","HHMM;&time#")

<where &time# was set as 1655 to match with for mat HHMM for example>
Error message: 
"U00020437 Runtime error in object 'SCRI.MODIFY.1', line '00001': Time '165' does not correspond to time format 'HHMM'."

 

Cause:

Looks like the length of that attribute is capped at 8 chars (including the ";"), this is identified as a bug.

Environment:

Release:
Component: AAUTEN

Resolution:

An error has been fixed where MODIFY_UC_OBJECT did not work for opcode EARLIEST_STARTTIME if a different time format was used.

Fixed versions:

  • Automation Engine 12.1.5 (Planned release on 20-May-2019) 
  • Automation Engine 12.2.3 (Planned release on 04-Jun-2019) 
  • Automation Engine 12.3.0 (Planned release on 28-Jun-2019)