I have to do a kind of migration of a specifi DB2 database.
The source environment is on one DB2 server and the destination on another one.
As there are many table structures changing and other goodies like that, I use : "export to ... select ... from ..." statements to export data from tables out of the source to external files.
Then I move these files to the new DB2 server, using : "import from ... insert into ..." statements to put back the data in the new database.
This works fine (test environment today).
The server's machines are multi-processor systems very powerful but the database tables contain a lot of data !
So instead of running or example all these "export" statement via one single script that I started with the famous DB2 command, I splitted the script in several shorter scripts and started then in different DOS sessions (DB2 is installed on a WIndows server 2003)
But what is very strange, is that I saw in fact these scripts not running in parallel.
Instead, the first script runs and only when it is completed does the second start etc...
I wonder why this behavior and how to correct it to have them run in "parallel"