Difference in behavior of script processing the ":CASE" clause

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The following Script is executed on AAKE container in version 21.0.5 HF1 

:SET &GET_TOKEN_CLIENT_ID# = 5
:SET &GET_TOKEN_GRANT_TYPE# = "CREDENTIALS"
:SWITCH STR_UC(CLIENT_CREDENTIALS)
:  CASE "1"
:  IF &GET_TOKEN_CLIENT_ID# = ""
.....
:  ENDIF
:  CASE "2"
!  NOOP

:  OTHER
:  PSET &GET_TOKEN_MESSAGE#="Invalid GRANT_TYPE value: &GET_TOKEN_GRANT_TYPE#"
:  STOP MSG, 50, &GET_TOKEN_MESSAGE#
:ENDSWITCH

this task with ended with

"FAULT_OTHER - Start Impossible. Other Error "

Returned messages in the Report

15/03/2023 09:53:13        U00012112 Task 'SCRI.NEW.5' (RunID '0001005017') terminated with script error.
15/03/2023 09:53:13        U00020432 Runtime error in object 'SCRI.NEW.5', line '00010': script command :CASE must not followed directly by script command :OTHER.
15/03/2023 09:53:13        U00011000 'SCRI.NEW.5' (RunID: '0001005017') could not be started on 'XXXXX#WP0YY'. See next message.
15/03/2023 09:53:13        U00020432 Runtime error in object 'SCRI.NEW.5', line '00010': script command :CASE must not followed directly by script command :OTHER.

Remark if the line commented line "! NOOP" is deleted from the script, the SCRI is correctly executed. (workaround)

Environment

Automation Engine version 21.0.5 in AAKE

Cause

This is a defect of the Automation Engine 21

Description: A problem has been solved where an empty script line after a comment was skipped which resulted in a runtime error.

Resolution

Workaround:

Remark: if the line commented line "! NOOP" is deleted from the script above, the SCRI object is correctly executed. (workaround).

Resolution: This bug is fixed in 

Automation Engine 21.0.10

Automation Engine 24.0.0