Converting WAF to v5r1

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxxx>]

Help!

We upgraded to the v5r1 O/S on our production server with no problems on
11/23.  After two weeks of running this with no problems we converted the
WAF feature of Content Manager (5722VI1) from v4r3 to v5r1 on 12/7.  Since
then we have had severe performance issues with two small API's in the WAF
application.  IBM has been no help as they consider this to be our code even
though it calls their API's and was written the way they told us to (many
years ago) in order to maintain release compatability.

Though it's only a small part of the code that we have problems with, the
impact is severe as nearly all of the users use this code regularly.  My
interactive CPU usage is up about 30% and my (already poor) response time is
down about 50%.

I suspect that this is a DB issue, but am not sure how to approach this as
the files involved are IBM supplied.  The WAF API's involved are FINDOBJ and
QUERYDOC.

Has anyone seen or heard of anything like this?  Any help would be greatly
appreciated.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group