|
truthfully, you stated that the line number had those values, you--
didn't specify which field had those values. You left that open to
interpretation. Because of that I see svline (which you don't show
getting populated), I assume it's zero and you're attempting to set
orline to 00 for every record.
As mentioned in a previous email, you still have an issue with the read.
You are not checking for eof after your read.
On Wed, Mar 9, 2016 at 9:12 AM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:
I noted it changed from 00 to 20.it's
in this case, the first order line is 00 and they must have skipped
10 the second is 20.
I noted it changed to 20 but then at update time it went back to 00.
I am assuming the issue is that the key read is order only.
I beleive i need to make an update key that would comprise the
order and line.
On Wed, Mar 9, 2016 at 8:05 AM, Michael Schutte
<mschutte369@xxxxxxxxx>
wrote:
In debug, what value is in svline on both the first and second record?
You don't show where it's getting populated. We can only guess
that
partialvalue is 00 on both records, thus duplicate record error on the update.
On Tue, Mar 8, 2016 at 5:44 PM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:
I saw in the debug that it was reading the order lines. So the
inkey
is working.
But I want to update the order lines with the passed warehouse.
Here
(RPG400-L)tryingUpdate orppl the
first read is line number happens to be 00 but the second is 20
but at update it failed on duplicate record. So it seems that
its
tosaying?
update 00 line
since the pol key has only the order#. is this correct what I am
If(RPG400-L)
so, I need to update from another klist?
c pol setll srbpol
c if %equal
c dou %eof(srbpol)
c pol reade srbpol
c ohords iflt 30
c eval ohsrom = svsrom
c eval ohsrom = whs
c eval oloqty = svqty
c eval olline = svline
c update orppl
c*now take this line item and qty and update warehouse balances
c eval item = olprdc
c exsr step2
c endif
c enddo
c endif
c*
c endsr
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
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.
This is the RPG programming on the IBM i (AS/400 and iSeries)
--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.
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.
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.
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.