× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



have you verified ssw85 is defined for update in the F specs (and since
i have not coded /free i pray thats not a stupid statement.)?
jim
----- Original Message ----- From: "Holden Tommy" <Tommy.Holden@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, June 02, 2006 12:10 PM
Subject: RE: Update Operation Failure Help Please


Not true...

You can lock the record in a file update hundreds of files & still be
able to do the update.  I believe the issue is that he updates the SSW85
file 2 times using SQL prior to executing the rpg update.

Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Friday, June 02, 2006 11:04 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Update Operation Failure Help Please


With a cursory glance at your code, I think the following is your
problem.
The update to SSW85 has to take place DIRECTLY AFTER reading/chaining of
SSW85. In your loop you read SSW85, then read and update other files
before
the update of SSW85. The way around this is to save the keys for the
record
you are reading and then chain that same record, change the fields where
necessary, and the update SSW85, with NO OTHER reads/updates of any
description to ANY OTHER files.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.