Hi,
being a DB2-DBA and fairly new to perl, I'm trying to figure out to put a
lot of stress to my Database.
Actually I have lot's of sql-statements in a huge lot of file's which I can
e.g.
either read with perl and send them via dbi and dbd::db2 to the database
====================================================
But I see no way how to influence how many statements get processed
simultanously in the database. As well the programming perl-DBI-Book says
it is possible with dbd::db2. Sure I can have many databasehandles and send
different statements in a circle over different $dbh's. But how to be sure
they don't get processed one after the other. Does anybody out there know
where to find some examples or has done it themselves already and is so
kind to share it with me ?
or read myself into posix-thread-management and start every sql-file
through a separate child-process
=========================================================================
This appears to be the longer way for me with greater efforts to solve.
Main question here is to test out how to have independent child processes
with batch-procedures. Actually I think the recipe 16.3 of the perl
cookbook may be right for my task, but i don't really get the difference
between <with shell> == < exec ("db2f.bat *.sql") > and < without shell>
== < exec ( "db2f.bat" , "statements.sql" )> Sure when I don't have a
shell, I will have to run the db2cmd.exe in this above mentioned case to
have a db2-commandshell! But what difference it means in thread-programming
and what therefore is to be done in perl, I just don't know!
As well as I like and ask for any detail-comments on anyone of the two ways
described above, I like any ideas, comments and so on about which how-to (
not only the above mentioned ways ) is preferable or possible at all.
Mit freundlichen Gruessen / Best regards
Manfred Beilfuss
Deutsche Verm�gensberatung AG
IT_Systemmanagement , DBA
M�nchenerstr. 1
60329 Frankfurt
Tel.: +49 (69) 2384 - 639
Fax: +49 (69) 2384 - 329
Mailto:[EMAIL PROTECTED]
