Variable that we defined at Workflow level are not resolved in TASKS executed within this Workflow.
search cancel

Variable that we defined at Workflow level are not resolved in TASKS executed within this Workflow.

book

Article ID: 206260

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After an upgrade on a AE instance to 12.3.4 HF1 the variable resolution performed at Worflow level is not pushed to the underlying TASKS.

2020-12-09 09:37:29 - U00020206 Variable '&P_ENV#' was stored with value 'AWADS'.
2020-12-09 09:37:29 - U00020206 Variable '&P_VA_SETTING#' was stored with value 'VARA.AWA_REORG_UNLOAD_SETTINGS'.
2020-12-09 09:37:29 - U00020237 The object variable '&_HOST#' in object: 'JOBP.FOREACH.REORG.UNLOAD', line: '00003' (RunID: '0116540351') has been created with the value 'SRPLINUX.BROADCOM.COM' by  using the command :PSET.
2020-12-09 09:37:29 - U00020206 Variable '&_HOST#' was stored with value 'SRPLINUX.BROADCOM.COM'.
2020-12-09 09:37:29 - U00020408 *** SRPLINUX.BROADCOM.COM
2020-12-09 09:37:29 - U00011583 LOOP start with '4' iterations.
2020-12-09 09:37:29 - U00011584 Iteration '1' with value '0'.
2020-12-09 09:37:29 - U00007084 Error in object 'JOBS.UNIX.AWA.REORG': Login object '{&P_VA_SETTING#,&P_ENV#,3}' could not be resolved.

These sequence still worked perfectly in 12.3.1.

Environment

AE Release : 12.3.4 

 

Cause

This is bug that was introduced in version 12.3.4

A problem has been solved where values could not be resolved when dynamic variables contained script variables (for example, {&VAR#, &KEY#}) and when they were used in attributes (for example in the "Login" field).

Resolution

This bug has been fixed in version 12.3.5 (available mid of February of 2021).

Upgrade to this or the more recent AE version to have this problem fixed..