|
> Program defined attribute fields do not > support cursor positioning, which is > half of my requirement. > Any other suggestions? There's no magic wand for this yet. You can eliminate the 'not' condition issue by using the attribute field and still keep the indicator for DSPATR(PC) or you can create an elaborate routine to map the fields to row/column and use the DDS CSRLOC() keyword to position the cursor. There are a variety of ways to approach this but they personally seem like a lot of work to accomodate a convention (set all dspf indicators off) that seems... unhelpful. So my final thought is to change the (probably) MOVEA *OFF *IN to a subprocedure that sets the indicators the way you want them. The mainline goes from MOVEA *OFF *IN to callp setDspfInd so the code remains uncluttered. The subprocedure can be used via /copy in all of your programs (a new convention?) if you choose. I'm not being dogmatic about it; I'm just saying that when a programming convention makes it harder to get your work done, it may be time to re-visit that particular convention. --buck
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.