Can you please paste your sample code and NSH Job output?
I've just use psexec. Here is idea, you invoke and NSH job that invoke the psexec with for command prompt so you don't the get the native behavior from NSH. Your thoughts?
you all seem to be confused - no where does john mention running a nsh job.
i've seen the same behaviour and i've just dealt w/ it - there's probably some problem in the shell that gets opened via nexec and the character encoding or keyboard mapping. i would open a rfe on this.
I'm surprised that you've seen this - we all thought that you were so good in NSH & BLCLI that you never needed the backspace key or Ctrl-C!
Thanks for the response - I'll open an RFE (and pray that Support don't ask me for an appserver.log file to support it!)
1 of 1 people found this helpful
I already reproduced this....
Don't worry, support will not ask unnecessary things..I believe, you know about 'IDEA' on communities as well which replaced the RFE process.
Check out BMC Ideas- A place to share and influence BMC product direction. Start here https://communities.bmc.com/welcome
I've had the same issue many times too, so I just don't use it because of this. The same interactive shell on Unix (i.e. nexec -i -e bash) doesn't give this problem... only seems to be happening with cmd on Windows.
You can give them some pretty easy STR ☺
I don’t use a lot of windows boxes – if I find one I just run a provisioning job and make it linux. That seems to solve most problems ☺
Was this ever resolved? Is there an environment setting or something that can be set to make the shell respond to the Backspace and Ctrl-C inputs?