Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
performance of a batch job ran and no current threads available
- Thread starter krishrad
- Start date
fredericofonseca
IS-IT--Management
Please do not post duplicated thread. I'll reply to your original post thread178-1448283.
Regards
Frederico Fonseca
SysSoft Integrated Ltd
Regards
Frederico Fonseca
SysSoft Integrated Ltd
Krishrad,
Sorry, in your previous post you said that you were a DBA, I'm guessing from your comments in this post that you accidently left out the word 'not'.
It depends on the tools you have available at your site, how much information you are going to be able to gather after the job has run.
You need to speak to somebody, possibly your DBAs or you mainframe support to discover whether you have any DB2 tools. BMC are a company (amongst others) that market a tool that stores thread history. Ask at your site if you have any tools like this.
Other than that, you are looking at whether the program(s) that ran had been compiled to generate entries to a plan table. This will give you an breakdown of every SQL statement within a plan, and by examining this, you should be able to determine if any of the SQL is inefficient (doing table space scans for instance). You can also look at the cost analysis table for the plan and this will give you an estimate at the cost of SQL.
These last two suggestions are generic to your plan rather than specific to the actual job that ran. Without the threads you cannot really analyse the run. The plan table though should be able to point you in the right direction if there is a problem.
Hope this is of help.
Marc
Sorry, in your previous post you said that you were a DBA, I'm guessing from your comments in this post that you accidently left out the word 'not'.
It depends on the tools you have available at your site, how much information you are going to be able to gather after the job has run.
You need to speak to somebody, possibly your DBAs or you mainframe support to discover whether you have any DB2 tools. BMC are a company (amongst others) that market a tool that stores thread history. Ask at your site if you have any tools like this.
Other than that, you are looking at whether the program(s) that ran had been compiled to generate entries to a plan table. This will give you an breakdown of every SQL statement within a plan, and by examining this, you should be able to determine if any of the SQL is inefficient (doing table space scans for instance). You can also look at the cost analysis table for the plan and this will give you an estimate at the cost of SQL.
These last two suggestions are generic to your plan rather than specific to the actual job that ran. Without the threads you cannot really analyse the run. The plan table though should be able to point you in the right direction if there is a problem.
Hope this is of help.
Marc
- Status