oscomponent.environment.variable causing our jobs to fail

Products

• CA Workload Automation AE - System Agent (AutoSys)
• Workload Automation Agent
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

We are doing an autosys agent install and testing and just noticed that jobs are failing when forcestarting due to this parameter.

oscomponent.environment.variable=/opt/CTCOautosysR12/SystemAgent/WA_AGENT/profiles/WAAE.txt

Tried to comment this parameter and job went SU:

#

# Agent-wide environment variables

#

oscomponent.environment.variable=C:/Program Files/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/Profiles/WAAE.txt

 

Is this an issue on R12 version?

What are the pros and cons of having it set?

Is it safe to not include in the install? 

 

From the agentparm list:

oscomponent.environment.variable
Specifies the path to the file that defines agent-wide variables.
Example: C:\MyVars\agent_vars.txt

 

Environment

Release : 12.x

Component : CA Workload Automation System Agent

Resolution

/etc/auto.profile did not exist yet WAAE.txt file referenced it and the agent had oscomponent.environment.variable set in the agentparm.txt file, as a result the wrapper script failed.  

The two solutions are:

1 - comment out the 
oscomponent.environment.variable
setting in the agentparm.txt file and restart the agent
so it will not try to source the /etc/auto.profile

2 - create the /etc/auto.profile so the command does not fail.

As these were agent only machines, there was no other autosys software on the host.

The directories like AUTOSYS=/opt/CA/WorkloadAutomationAE/autosys did not exist.