|
I use the same process here and it works fine (we have v3r1, v3r2, v3r7 and v4r1). I would suggest the folowing: Run your program in debug mode, check the value of RECNUM immediatly after the READ operation. It should be ok. After that check that value again immediatly before and after each CALL operation. If the value get changed after a CALL, it is because the parameters passed to the called program do not match the expected parameters. This can cause random and unpredictable result anywhere in the calling program! hard to beleive but thrue. Denis Robitaille Cascades Inc. >>> "Marc Zylka" <mzylka@netpath.net> 01/13 10:19 pm>>> I'm trying to get the record number which the cursor is on so that when I am done processing the option entered I can blank the option number which was used. (the program seems to lose the record number when I call another program and return). I set up SFLCSRRRN(&RECNUM), where RECNUM is 5S 0H but it gives me an incorrect number. For the first record, it gives 2. For the last, it gives 1. For all others, 1 more than it really is. We're on V3R2, is there a problem with this? Or is it just too late to be working on this? Thanks, Marc Zylka (mzylka@netpath.net) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- uucp +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@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.