Re: I am short of Indicators

I once wrote a program for screen cotrol with 6 screens, each using 90
output fields, all fully conditioned, using only 1 indicator, and that was
a work indoicator for controlling reads and chains.

The trick is in the DSPATR definition to use a 'program to system' field.
This field is filled with a Hex value by the program, and is then used by
the Display file to control formatting.

The field needs to be defined in the format itself, with type A, length 2
and usage P.

The hex value used by the program is easy to setup.  The DDS manuals have
it.  You can either force a specific Hex value in as required (e.g.
Underscore, Blink, High Intensity is X'2E'), or use Biton/bitof (e.g.
Reverse Image is biton 7, Blink is biton 2).  For myself, I just did some
setups in *INZSR such as
MOVEL X'2E'    UNBLHI
then, when I had an error, used
MOVELUNBLHI   PE0001
 where PE0001 was the field name used in the DSPATR record.

Refer to the DDS manuals under DSPATR for all the details.





"Rajeev Asthana" <Rajeev_Asthana@paramount.com> on 19/05/99 10:26:32

Please respond to RPG400-L@midrange.com

To:   rpg400-l@midrange.com
cc:
Subject:  I am short of Indicators




Hi All,

It happens everytime.
My application uses almost every indicator from 01 to 99. These indiactors
are
basically used to condition various display attributes of the display
files'
fields.
Now when I go to add a new field or add some more display attribute to an
existing field, I find that I have already used up all the indicators,
nothing
is left.
Then I go and put lots of Or/And conditions for the indiactors.
But this is not a clean way.
Can anybody tell me if there is a better way to do this?

(Day dreaming : - AS/400 guys at IBM has increased Indiacator length from 2
to 3
thus increasing the indicators from 001 to 999)

Thanks,
Rajeev.


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *