Re: bad indicators, bad! (was: RE: MOVEA -> EVAL)

Joe wrote:
>>Program to system fields are cool for this.  However I have not found a
way
>>to avoid using the indicators for things like SFLCLR, SFLDSP and such.
>>Anyone else found a replacement method for the subfile keywords?

Though indicators are unavoidable for Display and Printer files, I find the
following use of Logical Variables and Based Data Structures makes the
program easier to read.

FSfileDsp  CF   E             Workstn Sfile(Control:Rrn)

D DspInd          DS                  Based(IndPtr)
D   Exit                          N   Overlay(DspInd:3)
D   SflEnd                        N   Overlay(DspInd:40)
D   SflClr                        N   Overlay(DspInd:75)
D   SflDspCtl                     N   Overlay(DspInd:85)
D   SflDsp                        N   Overlay(DspInd:95)
D Rrn             S              5P 0
D IndPtr          S               *   Inz(%Addr(*In))
 ** Logic fragment (not complete)
C                   Dow       NOT Exit
 ** etc, etc, then Display Subfile
C                   Eval      SflDspCtl = *ON
C                   Eval      SflDsp    = *ON
C                   Exfmt     Control

I confess I do NOT like the use of INDARA (in DDS) and INDDS (in RPG).  Just a 
personal opinion.  They can cause more
more confusion/maintenance problems than they appear to solve.

Brian Parkins

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---