Re: Keyboard States

Scott,


>
> I was asking where I would find the "little blinking numbers"

I've got a list from "IBM 3180 Model 2 Display Station User's Guide"
GA21-9469-2, Chapter 3. Error Codes And Recovery Procedures. AFAIK,
the book is not available in any but print form, I've found mine in
one of those boxes filled with dust in a conner of our computer room.
I could type the text as is from the book, but the following fragment
of code could be all you need for operator keying errors:

const

  { Operator keying error numbers }

  KErrHelpWithNoErrorCode                        = 0;
  KErrCannotKeepUpWithYou                        = 1;
  KErrInvalidKeyCode                             = 2;
  KErrNoInputAllowedIntoTheField                 = 4;
  KErrNoInputAllowedInProtectedArea              = 5;
  KErrInvalidKeyWhileInSysReq                    = 6;
  KErrMustFillInBeforeNextScreen                 = 7;
  KErrOnlyAlphaAllowed                           = 8; { A-Z, blank,
comma,
                                                        period,
hyphen }
  KErrOnlyNumericAllowed                         = 9; { 0-9, blank,
comma,
                                                        period, plus,
minus }
  KErrOnlySignedNumericAllowed                   = 10; { 0-9 }
  KErrNoDataInLastPositionOfSignedNumericAllowed = 11;
  KErrNoMoreRoomInThisField                      = 12;
  KErrCannotLeaveWithInsertOn                    = 13;
  KErrMandatoryFillField                         = 14;
  KErrSelfCheckField                             = 15;
  KErrFildMinusNotAllowedInThisField             = 16;
  KErrFieldExitBeforeMandatoryFillSatisfied      = 17;
  KErrUseFieldExitToLeaveTheField                = 18;
  KErrDupNotAllowedInThisField                   = 19;
  KErrTheKeyNotAllowedInThisField                = 20;
  KErrMandatoryEnterField                        = 21;
  KErrFieldStatusUnknown                         = 22;
  KErrInvalidHexKey                              = 23;
  KErrLastPositionMustBe0To9InThisField          = 26;
  KErrKeyNotUsedByThisStation                    = 27;
  KErrKeyNotUsedByThisStation2                   = 28;
  KErrInvalidSecondKeyForDiacriticKeyFunction    = 29;

You surely don't have to implement all of them. You just display the
number as Mark suggested on the error line and send that number while
processing KeyHelp in PreHelp error state. AS/400 will send you your
full error message while placing the terminal in PostHelp state. It's
a bit of a bugger to rap your head around it first, but when it's
done, it works flawlessly. Also if you implement it for operator key
errors listed above, you can just do 5250 stream parsing errors

see
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/co2e2001/13.4?DT=1
9950629163252#TBLSTR

from 5494 Remote Control Unit Functions Ref

the same way, thus making emulator error proof since it makes AS/400
responsibility to handle ALL errors.

> and
> how to tell which one to put in the corner, not how to send the help
> sequence.

As I've mentioned earlier, my const declarations should be descriptive
enough (I hope <g>) otherwise, I could probably type those couple
pages from the manual in for you.

> I decided to forego having those numbers blink in the corner, and
simply
> display the human-readable error message immediately.
>

You could do that too <g> ...


Alex