I am running a telnet script that connects to a database server and executes sql scripts. While the remote database is processing the commands within the sql scripts, my telnet script continues to send commands. Okay, that's fine. They get queued up in the remote server and executed sequentially. However, once the telnet script sends the last command, the script ends and the session closes. All of the commands that were queued up while the remote server was busy processing, never get run.

Here is the outline of my code:

Code:

TelnetDbServer()
{
(echo "servername"
sleep 20
echo "username"
sleep 5
echo "password"
sleep 5
echo "cd /dbscriptPath"
sleep 2
echo "..execute script1.sql" #pseudo
sleep 2 
echo "..execute script2.sql" #pseudo
....
sleep 2
echo "..execute scriptN.sql" #pseudo
sleep 2
echo "exit") | telnet
}

Sample Output
[remoteHost]$ ..execute script1.sql
script1.sql commands running running running
..execute script2.sql
..execute script3.sql
..execute script4.sql
..execute script5.sql
..execute script6.sql
exit
Connection closed by foreign host.
[localHost]#

This shows one command is being run while the others are being pushed into the stack, but the telnet script exits before they get run.

What doesn't work:
I cannot use expect because this script is to be used on many machines which do not have expect installed, I don't want to bother with installing expect on all of them.
I tried using read myVar, read -p myVar, echo "read myVar", echo "read -p myVar". These work on korn but don't work on bash in this situation. It just skips right through to exit.
I would prefer not to set a ridiculously high sleep value as a solution. The point of this script is to save time, not waste it in sleep.

Ideal Solution
Ideally I would like my telnet script to wait until the remote server has finished executing the sql scripts, then exit without user input.