Windows Forum

Ask something
Discussion Locked

NT shell script quitting from inactivity

0 helpful
3 replies

by kimba1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have written an NT shell script (not using windows script host) that essentially calls another script and passes it some arguments. The called script does some things that can take some time to finish (like copying some large Oracle files). If theprocess that the called script takes more than 10 minutes the calling script abruptly quits. All scripts are either run from the commmand.exe or via the NT scheduler. I am seeing this behaviour on Windows2000 server on Compaq systems. I have not been able to reproduce the problem on other systems. I can consistently reproduce the problem on the compaq system. If I run the script from the command.exe shell the shell window dissapears with no error messages. I cannot find any idle time settings that might be causing this. I would appreciate any ideas.

Thank you.

3 replies

by beermonster

I'm guessing that your second script - the one thats being called - is using up the resources (probably memory) that the first cmd session requires to run. This may well happen if your copying large files, though this would not be machine specific. I suggest using START /WAIT to call the second script, which should spawn the second process outside of the calling scripts process area, rather than a call statement, which spawns the second script as a child process and shares resources.

by shanghai sam

This is a great suggestion. The second script actually executes an Oracle export process. I will try and call this script with a start /wait switch and see if this solves the problem. Thank you so much for your excellent suggestion.

This discussion is closed to new replies.