WAAE: Visual Basic Script Job issue after Windows upgrade
Article ID: 103587
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
CA Workload Automation Agent
Issue/Introduction
Workload Automation AE (AutoSys Edition)
We have a command job to run a Visual Basic Script (VBS) macro.
The job ran and completed successfully on Windows 2003.
But since the Agent node upgrade from Windows 2003 to Windows 2012 R2,
when we launch our VBS macro by WAAE AutoSys, it goes in the background.
We have a command job to run a Visual Basic Script (VBS) macro.
The job ran and completed successfully on Windows 2003.
But since the Agent node upgrade from Windows 2003 to Windows 2012 R2,
when we launch our VBS macro by WAAE AutoSys, it goes in the background.
Environment
WAAE 11.3.6 SP4 on Linux
WA Agent 11.3 SP4 on Windows
WA Agent 11.3 SP4 on Windows
Resolution
The encountered problem is related to changes between Win 2003 and Win 20012 R2.
The recommended solution is to add the following attribute to the job definition:
interactive: y
Example:
insert_job: jobname
job_type: CMD
command: D:/app12/batch.vbs
machine: machine-name
interactive: y < =======
Problem resolved by applying the solution.
The recommended solution is to add the following attribute to the job definition:
interactive: y
Example:
insert_job: jobname
job_type: CMD
command: D:/app12/batch.vbs
machine: machine-name
interactive: y < =======
Problem resolved by applying the solution.
Feedback
Powered by
