Task hangs at 'Resolving variables' if PRPT defaults refer (indirectly) to a missing VARA object

book

Article ID: 87462

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

PromptSets that use a non-existing variable, generate a forced trace. Tasks using such a prompt will hang in a "Resolving Variables".status.

If, for example
  • Task A contains a promptset that uses a VARA.EXEC as a data reference
  • This VARA.EXEC executes task B that gets values from a non-existing VARA (with GET_VAR)
Then upon execution
  • Task B will fail.
  • Task A will remain in "Resolving variables" status.
  • A forced trace will be generated by the Automation Engine server.
Investigation

VARA.EXEC.ADDITION executes SCRI.ADDITION with &OPE1# and &VARA# as input values. &OPE1# is set with value '1' and &VARA# with 'VARA.STATIC.OPE', the name of a static variable. However this variable does not exist.

<Please see attached file for image>

0EMb0000000IX1K.png

SCRI.ADDITION uses GET_VAR to read a value from &VARA# (static variable 'VARA.STATIC.OPE'):

<Please see attached file for image>

0EMb0000000IX1Z.png

PRPT.ADDITION contains a combo box which uses VARA.EXEC.ADDITION as a data source:

<Please see attached file for image>

0EMb0000000IX4J.png

PRPT.ADDITION is nested in SCRI.PRINT.RESULT:

<Please see attached file for image>

0EMb0000000IX5R.png

Results

Expected:  Upon execution of SCRI.PRINT.RESULT, the Automation Engine should return an error message stating that the variable object is missing and cannot be resolved.

Actual: 
Previewing VARA.EXEC.ADDITION causes errors, which is the desired behavior:

<Please see attached file for image>

0EMb0000000IX5C.png

However, when running SCRI.PRINT.RESULT, it stays in 'Resolving variables' status and may not be canceled.

<Please see attached file for image>

0EMb0000000IX5g.png

A forced WP trace is written by the Automation Engine server.

Cause

Cause type:
Defect
Root Cause: A prompt, based on a non-existing variable results in a forced trace. The task, using the prompt, will hang in "Resolving Variables".

Environment

OS Version: N/A

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 12.1.0 - Available
Automation Engine 12.0.3 - Available
Automation Engine 11.2.6 - Available

Additional Information

Workaround :
N/A

Attachments

1558693239307000087462_sktwi1f5rjvs16m4a.png get_app
1558693237471000087462_sktwi1f5rjvs16m49.png get_app
1558693235516000087462_sktwi1f5rjvs16m48.png get_app
1558693233423000087462_sktwi1f5rjvs16m47.png get_app
1558693231531000087462_sktwi1f5rjvs16m46.png get_app
1558693229612000087462_sktwi1f5rjvs16m45.png get_app