OPDESC support for numeric parameters

Would like to see operational descriptor support extended to include numeric parameters, i.e. be able to determine type (packed, zoned, int, uns etc), length, and decimal positions for a numeric parameter passed to a sub-procedure when 'const' or 'value' keywords are specified.

Before the addition of the OVERLOAD keyword, a general purpose procedure that needed to handle a variety of data types usually required the numerics to be cast to char before passing.

Using OVERLOAD means that procedures can now be written to handle each data type without the need to cast, making the use of these procedures 'cleaner'.

However, given the huge number of variations in length and decimal positions that are possible for a numeric variable, it is not practical to write a unique interface for every combination (e.g. one for a packed(3:0), one for a packed(5:2) etc, etc) so numeric variables still need to be cast to a suitably sized receiver (e.g. packed(63:32)).

If the received numeric variable then needs to be included as a part of a text string for example, the lack of OPDESC support means that it is not possible to correctly format the received argument to the same specifications (length, dec.pos if applicable) as the parameter used on the call.

OPDESC support would allow the original length and dec.pos. to be determined making formatting operations easier.

User overloaded procedures to handle a variety of data types as inputs.

Allow the details of the received argument to be determined to facilitate formatting operations, check for possible overflows etc