Troubleshooting
Problem
A RUN TASK using CMD() to call a VBS file name never completes.
Symptom
Windows prevented the VBS script from running. Instead Windows opened a GUI and prompted the user for manual interaction. Since the RUN TASK is non-interactive, the GUI will never be visible to the user and thus keeps sitting in the background forever. This is the root cause for RUN TASK "hanging".
The issue only occurred when calling a VBS file name using the CMD() parameter, like
RUN TASK SNODE (PGM=Windows)
SYSOPTS="cmd(C:\test.vbs)"
[{"Product":{"code":"SSRRVY","label":"IBM Sterling Connect:Direct for Microsoft Windows"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.6;4.5;4.4","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
24 July 2020
UID
swg21625254