Enable options(*exact) for indicators.

I am the developer of RPGUNIT and recently I added procedure assertEqual() to it. This procedure handles all data types, because it uses the OVERLOAD keyword for delegating the call to the procedure that is in charge for the data type.

dcl-pr assertEqual overload(assertEqual_string
                          : assertEqual_numeric
                          : assertEqual_float
                          : assertEqual_date
                          : assertEqual_time
                          : assertEqual_timestamp);
//                           : assertEqual_ind);

Too my surprise I had to notice, that the parameter fields (defined as: len(32565) varying(4)) were completely filled with '1' or '0', if I pass one of the figurative constants *ON or *OFF to assertEqual().

My first idea was to add an assertEqual_ind() procedure with options(*exact) to force the compiler to call that procedure if *ON or *OFF is passed.

But that did not work, because the compiler did not like it:

RNF3246 Prototypes ASSERTEQUAL_STRING and ASSERTEQUAL_IND both match the call; first match assumed.

The idea is to enhance the compiler so that data type 'ind' is handled like a real data type and not just like a label for data type 'char'. If 'ind' was a real data type, the compiler could distinguish between 'char' and 'ind' and hence allow assertEqual_string() next to assertEqual_ind().

In addition *ON and *OFF should be changed, so that only one character is assigned to a field regardless of its length. These figurative constants are BOOLEAN constants and hence should be handled with a fixed length (1 char) in contrast to the other figurative constants such as *ZERO, *ZEROS, *BLANK and *BLANKS.