Given the age of your post you likely found a way around the lack of timeouts for NSH commands and related tools (agentinfo, etc.)... However for those who have not, here is a shell solution I've recently used at Putnam as part of a test to alert us when the RSCD agent on our App server(s) drops into a "reachable by unresponsive" state which would result in "agentinfo" test hanging forever.
The shell logic to deal with a command which may never return could easily be modified for your case and any other case where a network shell command is potentially applied against a broken RSCD which may result in the command hanging forever.
- Jim Collins
rscd-agent-check.nsh 1.8 K