You did not say what you upgraded from? Was it from V5R4 or V6R1? (or
You did not say what hardware this is running on? What model of IIBM
iSeries / System i? How much real main storage? etc.
Can you quantify "a significant drop in performance"? Does this affect
batch jobs? Interactive jobs? Both?
Are your applications mostly "in house" or do you have any vendor packages?
An upgrade to V6R1 or above (V7R1) requires "re-encapsulation" of all
objects on your system -- this can slow everything down, until all of
the objects are converted. Did your shop take steps during this
"upgrade" to ensure this conversion was done? (e.g. run STROBJCVN for
all of the applications libraries immediately after the upgrade was
completed.) There is a Redbook that tells you all you should know about
If you upgraded from V5R4 to V7R1, you should have studied both the
"V6R1 Memo to Users" and the "V7R1 Memo to Users" to be aware of the
changes to the system that might impact your applications.
Do your COBOL applications make use of embedded SQL?
I notice you mentioned "OPM COBOL" -- why not ILE COBOL?
You might get more and better responses from the MIDRANGE-L list ...
Recent enhancements to the SQL query optimizer (part of SQE (SQL Query
Engine) can have an adverse effect, if some of your uses of SQL were
previously using the "Classic Query Engine" (CQE). You might need to
make a few small tuning adjustments in some cases to bring performance
back up to expected levels -- there was a thread about this topic
recently on MIDRANGE-L ... the start of that thread is here:
I hope this helps somewhat ...
All the best,
Mark S. Waterbury
> On 3/24/2014 2:39 PM, geir.kildal@xxxxxxxxxx wrote:
Maybe this is not the proper site to discuss this, but:
We upgraded to V7R1 and experienced a significant drop in performance. We run most cobol opm-pgms on db2, and some queries in addition.
Anyone who have experienced the same - and what solutions are there?
Please direct me to some answers.
As an Amazon Associate we earn from qualifying purchases.