The AUTORUN Variable Is Set in an 11.3 Job Environment

Document ID : KB000008351
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

In pre-11.3 versions of WAAE, the AUTORUN variable was set within a job's environment. The value was set to the job's current run number and could be referenced in output files. This is not getting set in 11.3.x job environments.

Resolution:
On the agent machine where the job runs, go to the agent installation directory and open the agentparm.txt file. Make sure these parameters are set in there. If not, add them anywhere in the file and restart the agent...

filemon.firstscan.skip=true
oscomponent.cmdprefix.force=true
oscomponent.initialworkingdirectory=USER_CONT_NOT_AVAIL
oscomponent.noexitcode=256
oscomponent.noforceprofile=true
oscomponent.profiles.src.delay=true
oscomponent.profiles.src.order.global.first=true
oscomponent.profiles.src.verify=true

The specific parameter that allows the AUTORUN variable to be available is 'oscomponent.cmdprefix.force=true'. However, it is recommended that all of these parameters be set for optimal compatibility with WAAE.