RE: A Mystery SQL Problem

Jose,

I have had an ORDER BY clause on the INSERT statement but it did not affect the outcome.

And I have run the statement in STRSQL and it ran properly. That is how I refine my SQL statements. First in STRSQL, and then in RPG/LE.

Thanks,

Marvin
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jose Perez
Sent: Tuesday, December 06, 2016 5:37 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: A Mystery SQL Problem

I know the order by has nothing to do but why no try to take the order by when doing the insert and see what you get and one more things is your code embedded? if so try running the sql statement outside of your program using strsql for example.



On Tue, Dec 6, 2016 at 6:07 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

One step I take in a situation like this is that I purposely do
something I know will compile-but-break the process. Quite often in
looking at the broken pieces the culprit spits in my face. For
instance I might copy both files to a sandbox. If its a big file,
take the last thousand records, or such. Then perhaps yse an existing
field to update with an incremental counter and then watch the counter for odd behavior.


On 12/6/2016 4:41 PM, Marvin Radding wrote:

This program is use to build records for the AHPOVRP file. When
exiting the program, the records, identified by the effective date,
are copied to the MMNYOVRP file. When they do this on a state by
state basis, the duplicates are always at the end and this will move
as more states are built. For example, when they build the first
state, it duplicated 40 records. When they built the second state the
duplicates for the first state disappeared and the second state had
duplicates. And when they built the third state there were no
duplicates on the first two states but then the third state had
duplicates. Each time, the program will extract from the AHPOVRP
file all the records built up to that time and will only crate duplicates for the last few records. I am very mystified.

Thanks,

Marvin
No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced

--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
Notice: This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. This message may also contain Protected Health Information (PHI) and must be treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately and delete this e-mail (and any accompanying attachments).