|
The code I have is... (The program is unfortunately written in RPGIII)
* IINFDS DS I 369 369 #KEY * I X'3F' C #AUTO I X'F1' C #ENTER
C *IN93 IFEQ *ON * C SELEC C @COL WHEQ 9 C EXSR COLCHK * C @COL WHGE 20 C @COL ANDLE24 C #KEY IFEQ #AUTO C #KEY OREQ #ENTER C EXSR COLCHK C END * C @COL WHGE 39 C @COL ANDLE43 C #KEY IFEQ #AUTO C #KEY OREQ #ENTER C EXSR COLCHK C END C ENDSL C END
From: "Bob O." <otis_the_cat@xxxxxxxxxxx> Reply-To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To: rpg400-l@xxxxxxxxxxxx Subject: Hex Code for Field+ key Date: Fri, 01 Apr 2005 06:44:22 -0600
I have a program I am working on where a field has CHECK(ER) assigned. The users want to use the Enter key to page through the screens. When the user(s) press the Field Exit (+ key on the numeric keypad) on the keyboard, the program checks for a valid ticket number. If it is a valid number, the program then positions the cursor to the next field via the CSRLOC keyword. When the Field Exit key is pressed however, the program is moving on to the next screen instead of positioning to the next field.
I think what would solve the problem is checking for the hex code for the field exit key. I cannot find the hex value of the key in any of the books I have. They all only show X'3F' for Auto Enter and X'F1' for Enter. Is there a value for the field exit(+) key?
We are using Client Access and run V5R3 on the iSeries.
Thanks for any help!
-- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.