Launch via "uxadd fla" does not inherit Task Variables

book

Article ID: 210395

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Launches created via "uxadd fla" without the argument TSK=Taskname do not inherit the Task variables

Example of the used command:

uxadd fla exp ses=session upr=uproc mu=mu pdate="01/01/2021" user=username lend="(16/03/2021,2200)" queue=SYS_BATCH  vartsk

 

Cause

Wrong usage of "uxadd fla" :

by default, if tsk parameter is empty, the launch will not be associated to a Task (where variables are defined).

Environment

Release : 6.x

Component : Dollar Universe

 

Resolution

As explained in the documentation, if the "uxadd fla" command has the TSK argument transmitted, the launch will be associated to that Task and will use the Task variables instead of Uproc variables.

TSK=
(Optional) Enter a task code or * (wildcard accepted except for uxadd). Incompatible with UPR, SES and USER. 
 
VARTSK | NOVARTSK
(Optional) Variables:
VARTSK (or Y on OS/400): (default) The launch is created using the values of variables of the corresponding task (if it exists).
NOVARTSK (or N on OS/400): The launch is created using the values of the variables of the Uproc defining the launch.
 
 
 

Additional Information

An example of the minimum necessary syntax to launch the task called IU_UMNT via "uxadd fla":

uxadd fla tsk=IU_UMNT  mu=muname pdate="01/01/2021"