|
Thank you all for great comments and info! -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Tuohy Sent: Wednesday, October 04, 2006 1:40 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: Subfile problem To do a double read of a subfile using READC. 1st read (RRN = field defined on SFILE keyword, SFLNxtChg = indicator controlling SFLNXTCHG keyword on subfile record in DDS) RRN = 0; // = SETLL on subfile SFLNxtChg = *On; ReadC SubRec; Dow Not %EOF(); // Process Record Update SubRec; // Updated with SFLNXTCHG on ReadC SubRec; EndDo; SFLNxtChg = *Off; 2nd Read RRN = 0; // = SETLL on subfile ReadC SubRec; Dow Not %EOF(); // Process Record ReadC SubRec; EndDo; HTH Regards Paul Tuohy ComCon www.comconadvisor.com -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Phil Kestenbaum Sent: 04 October 2006 16:37 To: RPG programming on the AS400 / iSeries Subject: RE: Subfile problem The problem I am having is to reset the subfile. IOW, I have a routine that checks each line via a READC, that is doing a dow not %eof But it is NOT going through and checking upon hitting enter, the indicators are controlling. Because, EOF has been hit. I am not sure how to reset the subfile. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael_Schutte@xxxxxxxxxxxx Sent: Wednesday, September 27, 2006 4:59 PM To: RPG programming on the AS400 / iSeries Subject: Re: Subfile problem If I am understanding you correctly, You should only have to reset the indicator for the line once the error has been corrected. On your "else", you need to update the subfile record there too because you are changing the value of *In60. Michael Schutte Dig in! Bob Evans New Knife & Fork Sandwiches - This much homestyle goodness demands a Knife & Fork! rpg400-l-bounces@xxxxxxxxxxxx wrote on 09/27/2006 04:50:50 PM:
HI, I have a subfile program that when there is an error, on say the third line, on the first pass, the cursor is being put on the third
line
correctly, but subsequently, the cursor will be placed on the first line. Let's say if I correct the third line but make an error on
first,
then correct the first and re-error on third, it then positions on FIRST. I appear to be missing code that would correctly align the
cursor
to the error line, or perhaps I need to clear the subfile on each
ENTER?
The code is: C prolin begsr C readc sfr1 * * C dow not %eof * C if s6sqty = 0 c C eval *in60 = *on C eval *in59 = *on C eval *in74 = *on C update sfr1 c else C eval *in60 = *off c endif C eval *in74 = *off c* c readc sfr1 C enddo C endsr Ind. 60 is to position the cursor: A 60 DSPATR(PC) This message contains information proprietary to our company. It is intended to be read only by the individual or entity named above or their designee. Any distribution of this message or the information contained herein without written permission from our company is strictly prohibited. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the RPG programming on the AS400 / 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.
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.