I need to eliminate nexec waiting for a response.
you are running this script from the command line and not a job ?
what os is the nsh client ?
where are you doing the env var set ?
what is calling the nexec - your vb script ?
The OS is linux
I have not set the env var which is the part of the question.
Yes the vb script is making the call to the nexec
here is the line of VBscript
cmdString = "%COMSPEC% /c nexec " & serverName & " uname > " & outputFile & " 2>&1
Now that would work except that it waits for an answer on which role I want.
So if I can pass the variable into the command string or set it, it would work.
Uh.. the os of the nsh client is Linux, but you are running a vb script that calls nexec ?
You probably need to set the role variable in the vbscript.
I agree but how do I set and Pass it along to the nexec command?
Vb scripts can take arguments as input on the command line. so you could run the script like:
cscript /nologo script.vbs ROLENAME
and then code your vb script to use the 1st argument as the role name to set the env var before calling nexec.
Do you have an example the you could share?
I am missing the part where the variable is passed to the nexec command so that have the effect in the command.
How do i export it to nexec?
as long as the env that the vb script creates when it calls nexec has the BL_RBAC_ROLE variable set, then nexec will pick it up.