Re: Contiguous memory and the *INKx indicators

["James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>]

Barbara,

AFAIK, the indicator 01-99 and Kx are in separate, but (group wise)
contiguous areas (also the Lx).

I believe that the keyboard scan codes would still map properly without
regard to the compiler omission of KO as a valid indicator.  There are
24 F keys, therefore 24 F key indicators.

So, it would seem, that the powers that be would write some simple code
to map 24 keys to 24 contiguous indicators, but then again, I've seen
plenty of stuff that defeats ANY attempt at simplicity or logic! ;-}

But your point is well taken, just make sure that the indicator overlay
omits the letter 'O'.

BTW, it has been this way since the S/34, maybe the S/32, anyone know
the reasoning behind this?  Is it just a compiler writer inside joke to
omit "KO"?

bmorris@ca.ibm.com wrote:

>
> Joe, I take it back a bit.  I'd forgotten about *INKO, which doesn't exist
> (O as in MNOP).  It's possible that some RPG compiler might have an
> internal
> array of 25 indicators, so the index would match the letter.  (Currently,
> we have *INKN at index 14 and *INKP at index 15, but it might be reasonable
> to have *INKP at index 16.)
>