echo the commands you want to run into a batch file and nexec that.
Is that the only way ? I created an nexec script that takes arguments etc. to make things simpler / generic (copy package etc) compared to deploy jobs which work, and then i have to create a batch install ? and run that ?
I might as well have a nsh script that just calls a cmd file, with 1 argument, the path and name of it, copy it and have all the detail in the cmd file. Kind of makes nsh redundant ?
I’ve been able to get the path to work out right so I’m not sure what issue you are having.
Also – it looks like you are trying to do an install, so why aren’t you using a blpackage or depot software for this?
The issue I am having is that this in a nsh shell;
nexec -e cmd /c "echo .| C:\TEMP\\$PKG_NAME $PKG_POST_ARGS"
Where POST ARGS = dir="C:\\Program Files\\myapp
removes everything after C:\Program
so what syntax have you used to prevent the space being considered the end of the string, despite being in quotes ?
Why aren’t you using a blpackage or depot software for this?
I think something like:
myapp\”” should work.
Tried this, didn't work for me.
I've tried all sorts inc.
Because the GUI is so irritatingly slow to do anything in and I can't do things like edit reg files, so every small change I have to go through the process of uploading a new file, setting all the options in the BL job (with tiny windows for long commands" and it's generally more down to poor usability of the GUI as much as anything
I hope v 8.0 improes on it in a big way - we should be upgrading this year.
So you are not creating a depot object because the GUI is slow?
What version of bsa are you running?
What database backend?
Is the gui across a wan from the appserver?