Tweet
A A1STS 1A P A R1STS R B 20 33REFFLD(STS LLREFDP) A TEXT('Status') A DSPATR(&A1STS) To archieve this I wrote two functions. For the first one I can pass the display attributes as I'd specify them in DDS, for example 'YLW': 'UL' and return the appropriate hex value. The valid hex values are x'20' to x'3F' for unprotected display attributes and x'A0' to x'BF' for protected display attributes. Instead of handling different situations with switching different indicators Off and On I simply determine the hex value in my program: Example: /Free Select When Action = Display and R1Sts = Active; A1Sts = SetDspAttr('WHT': 'PR'); When Action = Display and R1Sts = Inactive; A1Sts = SetDspAttr('RED': 'PR'); When Action <> Display and R1Sts = Active and R1Date <= %Date(); A1Sts = SetDspAttr('YLW': 'UL'); When Action <> Display and R1Sts = Active and R1Date > %Date(); A1Sts = SetDspAttr('TRQ': 'UL'); When Action <> Display and R1Sts = Inactive; A1Sts = SetDspAttr('RED': 'PR'); EndSl; /End-Free The other function I've written returns the reverse image for a given display attribute in hex. In this way I easily can change the display attribute without taking care about the conditions I set before. Example: /Free Monitor; ChkFkt(R1Sts); On-Error; A1Sts = SetDspAttrRI(A1Sts); SetCsrPos(R1Row: R1Col: 'DSPF': 'FORMAT': 'FIELD'); EndMon; /End-FreeA little more trickier is to position the cursor to a specified field without hardcoding column and row, because the API QDFRTVRD (Retrieve Display File Description) must be used. But a prodecure, written once and tested, will work forever. The only thing for what I have to use indicators, is for subfiles. There is no workaround to avoid indicators in DDS. Birgitta
Indicator Data Structure An indicator data structure is identified by the keyword INDDS on the file description specifications. It is used to store conditioning and response indicators passed to and from data management for a file. By default, the indicator data structure is initialized to all zeros ('0's). The rules for defining the data structure are:If your code compiles and works, then either I'm not understanding that part in italics above, or, the documentation is lying again. If the latter, maybe I can use a left-side %subdt.[*]It must not be externally described.[*]It can only have fields of indicator format.[*]It can be defined as a multiple occurrence data structure.[*]%SIZE for the data structure will return 99. For a multiple occurrence data structure, %SIZE(ds:*ALL) will return a multiple of 99. If a length is specified, it must be 99.[*]Subfields may contain arrays of indicators as long as the total length does not exceed 99.[/list]
Comment