Dropped rows on SQL INSERT

I've got an issue I don't understand. First...we are at 7.2. I can't find anything like this in the 'net.

We have loaded 7.2 on our development LPAR and we immediately began to have an issue with this scenario.

We've a CTE that normally generates...say 8 rows...when writing to a table in QTEMP. Now this results in 6 rows.

During debugging...the CTE (without the insert) will generate the expected 8 rows. But wrap the CTE in an insert (that's all) and two rows are dropped. Interestingly(coincidently?), the missing rows are also the rows that are impacted by a GROUP BY in the 2nd expression that eliminated the duplicates. Remove this GROUP BY and the missing rows are in the final result set.

I'll try to sanitize the SQL somewhat and post it here soon. Anyone even heard of such a thing?

Steve Needles

________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

TRVDiscDefault::1201