On Dec 27, 2007, at 2:49 AM, Jason To wrote:
We have been constantly improving our batch window by implementing
the following available technologies:
1. SMS SMB and data compression on some of our VSAM files
2. System determined blocksizes on sequential files
3. BUFNO on some input files
4. Constantly improving our access to DB2
4.1 Add indices
4.2 Compress of big DB2 tables
4.3 Reorg of DB2 databases
5. Increase parallelism
6. Improve DFSORT performance
7. Improve application efficiencies
We have basically improved the batch window after implementing all
these, however, after some time, the batch starts to become longer
again. My question is aside from these, any other thing we can do
to implement to improve our batch further? TIA.
Regards,
Jason
Jason,
You just gave a extremely brief list. So its hard to come up with any
generalization(s)., The first I would do is look at sort and see if
you can give in more storage. Sort LOVES storage and lots of it. I do
not have much experience with DB2 you might want ask the DB2 list for
ideas.
If you have VSAM files and its heavily used look at increasing
cisizes and make sure you don't have to many splits (CA or CI) as to
the applications, I would suggest hiring a COBOL consultant (assuming
that is what they are written in) .
Don't be cheap with any resource is another well known tuning call
but know when they are being wasted as well. Be generous but don't be
overkill.
Ws
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
