Re: INDDS Data Structure

[PARKIB@xxxxxxxxxx]

By using INDARA and INDDS you are creating your own, Named Indicators
INSTEAD of the System Named Indicators.  So, SFLEND and *IN99 no longer map
to the same working storage area..  (*IN99 is just a 1-character variable).

Personally, I avoid using INDARA and INDDS.  This facility only allows you
to define your own names for Indicators specified in Display and Printer
Files.  No use for Indicators specified in other files types (or within the
program).

A much neater (and consistent) method is to make the Data Structure a Based
Variable, and resolve the Basing Pointer to the *IN array, something like:

DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++

D Indicators                   DS
Based(IndPtr)
D   SflEnd                                                      N
Overlay(Indicators:99)

CL0N01Factor1+++++++Opcode&ExtExtended-factor2+++++++++++++++++++++++++++++
  ** Following only executed once, at the very beginning of the program
C                                     Eval             IndPtr = %Addr(*IN)

Hope this helps.

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
+---