New autosys agent not recognizing environment variables

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• Autosys Workload Automation

Issue/Introduction

The new agent install that doesn't recognize the environment variables. 

This works:
/some/direcotry/work/scripts/user_script.sh INT-290 GET MSG

For our jobs to work though, needs to be able to run:

$SOMEVAR/work/scripts/user_script.sh INT-290 GET MSG

If I run an env command in a job the output looks the same as if I run it from the shell

This is the agent version:

./cybAgent -v

CA Workload Automation Agent

   for LINUX (Intel) 64-bit

   Version R11.3, Service Pack 4, Maintenance Level 0, Build 717

Environment

Release :  12.0 or above

Component : Workload Automation System Agent

Resolution

SOMEVAR is an environment variable that is set in the job profile.

When oscomponent.lookupcommand is set to false, the WA Agent cannot find the command before the job profile is sourced and fails the job with "File not found" error.
Setting oscomponent.lookupcommand=true will resolve the issue.

Additional Information

WA System Agent for UNIX, Linux, Windows, or i5/OS Agent Parameters

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-1/reference/ca-wa-agent-for-unix-linux-windows-or-iseries-agent-parameters.html