You are going to have to talk to the DBA responsible for DB2.
The timeout is caused by a default that prevents one task from "hogging" the database when other tasks need it. (From experience, the DBA will usually NOT change the timeout value for you). I also find the a production job has a higher timeout than a test job so you can see what you can do there.
Other things to consider: make your SQL more efficient by using index variables in your SELECT or WHERE clauses, or use PASSTHRU.