Actually I found an answer.
It is "Start". If you prefix the statements with start, it will initate all the statements. Therefore, the script does not have to wait for statement one to finish to begin statement #2.
Simplified Example:
start copy log.txt log.bak
start db2 -tvf create.sql
The goal as stated is to "run all the statements at once" where command 2 does not have to wait for command 1 to start. I was hopeing it was obvious from my initial post.
I am not looking for a delayed variable expansion. Not looking for anything "delayed". In fact, not sure what a delayed variable expansion is.
Let me try to explain the benefit of "running all commands at once". Assume for a second that you drive a car, and you want the ability to play the radio and open the window at the same time. That is what I am looking for

In a typical batch file situation, I would have to wait until I was done listening to the radio and then I could open the radio. OK this last paragraph may have confused things. I guess to me the benefit seems obvious. Assume you wanted to copy a large log file and at the same time run a sql statement and run a "windows command". In a typical batch mode, you would have to wait for the copy to finish and then start the sql statement and when that was done - start the windows command.