Re: How about in INC opcode

>>The VA/RPG syntax would be fine
>>
>> C              Eval        %setatr('format':'field':'ReverseImage')=*On
>>
>>But, like too many have already stated - don't hold your breath waiting
for
>>5250 to change.
>
>A capability similiar to this already exists.  I don't know at what version
>it started, but DSPATR can accept a field name for some of the display
>attributes.

I've used this technique in the past. It's not difficult, just time
consuming.

Let's say that the DDS compiler actually created these system fields for
each "object" in the display file. By "object", I mean all fields, text, sfl
control
fields, etc. Then by using the %getatr and %setatr, we would be able to
retrieve and set these system fields. In other words, we would have the
capability to control the DSPF inside our RPG without coding the DSPF
side. Maybe even use a parm setting on the CRTDSPF command to
control if the system fields are created or not. I think the %getatr and
%setatr
add a nice level of clarity as it names the format, field and attribute
being
used, rather than another field name that is not necessarily as obvious.

Joe Teff

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---