v5r2 to v5r4 upgrade issue with SQLRPGLE performance

All,

As an FYI for the archives and for my own education, I thought I'd
thow this out there and see if anybody else had issues with the
performance of SQLRPGLE programs after a v5r2 to v5r4 upgrade.

During testing of the upgrade on the Pre-Production box, we ran across
a single SQLRPGLE program that performed very poorly post-upgrade
(5-10 minutes) as opposed to pre-upgrade (5-10 seconds). Not just the
first run, but every run. (I'm aware of the embedded SQL object
conversion that happens at first run on v5r4)

The program had been compiled on our development box at v5r2 using
TGTRLS(V4R5M0).

We recompiled the program on v5r2 on our development box with
TGTRLS(V5R2M0) and sent it to the Pre-Production box running v5r4 and
all was well.

During the upgrade of the production box, we had an issue with a
_different_ SQLRPGLE program. It was also taking minutes instead of
seconds to run. Again, not just the first run but every run.

One of the other developers reported that the WRKACTJOB screen was
showing an index build taking place. But there should have been a
logical out there that should have been used. (see the post from me
with the subject "v5r4 upgrade first touch object conversions and
logical files")

We saved the object, deleted it, and restored it based upon my
recommendation. (My understanding is "something" happens behind the
scenes when an object with embedded SQL is restored, I thought it
might help :)

The user was no longer around to test the program, so we had to wait till today.

This morning all is well. Not sure if the the save/restore helped or
if the logical was now usable or what.

Anybody else seen anything like this?

Thanks!
Charles Wilt