JAMS VBScript integration
VBScript Job Scheduling and Automation
JAMS Scheduler runs your VB scripts on any Windows server with the Vbs execution method, with schedules, dependencies, stored credentials, and alerts. Keep them running on time while you decide what replaces them.
Execution method
Vbs, built in
Runs on
The JAMS Scheduler or any JAMS Agent for Windows
Completion rules
Exit codes and log patterns decide success or failure
What JAMS Scheduler Runs in VBScript
Paste the script into the job, or call an existing .vbs file from a Command job, then set the credential it runs as. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Runs VBScript
VBScript jobs run on the JAMS Scheduler or on a JAMS Agent for Windows on the server where the script needs to run. The job runs as a JAMS credential, so the script gets that account’s rights.
Every run’s log stays in the job history.
Requirements
Runs on
JAMS Scheduler or JAMS Agent for Windows
Credential
A Windows account with rights to run the script
VBScript Jobs in a Cross-Platform Workflow
A VB script can wait for a file transfer or a SQL Server job, then start the next step. When you rewrite a script in PowerShell, the new job can take over the same schedule and dependencies.
Visual Basic FAQ
Can JAMS Scheduler run my existing VB scripts?
Yes. The Vbs execution method runs a VB script on Windows as a JAMS job, on the scheduler or any Windows agent.
How does JAMS know if a VB script failed?
From its exit code, by default. You can also set exit codes that count as warnings, or match patterns in the log output that mean success or failure.
Can I move a VBScript job to PowerShell later?
Yes. PowerShell jobs use the same schedules, dependencies, and alerts, so you can rewrite the script and keep the workflow around it.
