|
midrange.com
I know from upgrading to 5.3 that we did run into alot of issues with the
change to cqe engine for the queries (sql). I'm not sure how your app is
running but we did find that with the change to cqe if you are running sql
statements over logicals with include or omits in it, the queries will tank
unless you tell the optomizer to use the old query engine (sqe). The other
issue that we hit it large files with access paths that were "old", you cant
telll that they are but if you do a chglf and just take the option to force the
access path rebuild that helped alot.
Not sure if it helps you, but thought I'd mention it
-----Original Message-----
From: ChadB@xxxxxxxxxxxxxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, 7 Apr 2006 11:20:30 -0400
Subject: Re: V5R3M0 Performance Issues
You're screaming bloody murder to IBM, right? ;)
"Jon Allen"
<jallen@xxxxxxxxx
> To
Sent by: <midrange-l@xxxxxxxxxxxx>
midrange-l-bounce cc
s@xxxxxxxxxxxx
Subject
V5R3M0 Performance Issues
04/07/2006 10:49
AM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
V5R3M0 job performance has tanked.
After upgrading to V5R3M0 our system performance with jobs running in
PASE have tanked. Jobs that once took 20 minutes now take 5-6 hours to
complete. Has anyone had this happen? Jobs running in native mode do
not seem to be affected. However, when displaying wrksyssts we notice
that our CPU% is running around 20-40% during our daily work load where
it used to run in the upper 80%'s during that same time back on V5R2M0.
We feel this is very strange.
Our PASE jobs are killing our business. Has anyone else have trouble
with PASE and V5R3M0?
Any help much appreciated, thanks!
Important Confidentiality Notice: This email message, including all
attachments is for the exclusive use by the person(s)
to whom it is addressed, and may contain information that is confidential
or privileged. Any unauthorized review, use,
disclosure or distribution is prohibited under applicable law. If you have
received this email in error, please notify me
immediately by reply email and delete this message and any attachments.
Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT000428D2=
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
