Job fails if the path to a CL_EXT contains a node variable
book
Article ID: 101372
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
If a job of type "External script" (CL_EXT) contains a node variable in the path that refers to its external script, the job fails with error in the History Trace: CL non executable by this user or not found
An additional symptom is that U_ANTE_UPROC is not executed.
So this occurs, for instance, with the following node variable: PATH_TO_EXT_SCRIPT=/path/DUAS/scripts
... and inside the CL_EXT the following path to the external script: $PATH_TO_EXT_SCRIPT/external_script
Environment
Release: ADUASU99000-6.8-Automic Dollar Universe-AS - UNIX Component:
Resolution
Workaround: Define the path variable in unienv_specific.ksh
Solution:
Update to a fix version listed below or a newer version if available.