|
Or use the (E) extender and action any errors. The difference is that the Error should only happen occasionally as opposed to the preventative SETLL everytime. And yes, i think the (E) is more overhear - when it happens... At 11:03 AM 8/22/2001, you wrote: >As long as you do the SETLL just before writing out a record, we are talking >split second here. In most cases, it should not be a problem. > >Joe Giusto II >Programmer/Analyst >Ritz Camera >Beltsville, MD >301-419-3209 x347 >410-813-2812 x347 > > -----Original Message----- >From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com] On >Behalf Of Alan Addison >Sent: Monday, August 20, 2001 1:36 PM >To: rpg400-l@midrange.com >Subject: RE: CHAIN vs. SETLL > >Is there not the caveat to this that records added by other programs since >the file was opened may or may not show up in the resulting operation? I >seem to remember this bu am not sure about it. > >Alan > >-----Original Message----- >From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On >Behalf Of PatrickConner@parkdalemills.com >Sent: Monday, August 20, 2001 1:10 PM >To: rpg400-l@midrange.com >Subject: Re: CHAIN vs. SETLL > > > >If a chain fails it does the same thing as a setll. However, it will >retrieve info if it is successful. >It is more efficient to use setll when you are only interested if a record >exists in a file. > >Patrick Conner >www.ConnecTown.com >(828) 244-0822 > > > > "Reeve Fritchman" > <reeve@ltl400.com To: "RPG400-L@midrange. >com" <RPG400-L@midrange.com> > > cc: > Sent by: Subject: CHAIN vs. SETLL > rpg400-l-admin@mi > drange.com > > > 08/20/01 01:00 PM > Please respond to > rpg400-l > > > > > > >My understanding is that CHAIN grabs the record and fills the input buffer, >whilst (it's the British influence taking over) SETLL checks the access >path >only for the existence of the key. > >If I want to know if a record with an identical key is already in the file, >I SETLL. Yes, there are application reasons to do this! > >_______________________________________________ >This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list >To post a message email: RPG400-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l >or email: RPG400-L-request@midrange.com > > > > > >_______________________________________________ >This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list >To post a message email: RPG400-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l >or email: RPG400-L-request@midrange.com > >_______________________________________________ >This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list >To post a message email: RPG400-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l >or email: RPG400-L-request@midrange.com > >_______________________________________________ >This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list >To post a message email: RPG400-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l >or email: RPG400-L-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.