If nsh is installed on the target system and you use the right shebang for the script I think runscript will run the right shell so a type 3 should work. /bin/nsh does not exist on a windows box though and windows doesn’t really understand that anyway.
So why don’t you make this a type 1 or type 2 script, have the script echo the bit you want to into a file and then nexec nsh and run it like:
Nexec SERVER nsh –c “yourscript.nsh args”
What we ended up doing is letting the script reside locally on our transfer server- then we setup a type 1 NSH script that simply ran the nexec hostname nsh -c "nsh /path/to/script/script.nsh arg1 arg 2 arg3 etc" command to excute the script.
Using this solution we were actually able to pass arguments to our NSH script and execute it locally on our Transfer server.
P.S. it didn't work correctly unless I put the nsh inside the double quotes. If I just ran nexec hostname nsh -c "script.nsh" it still tried to connect from the app server.