Thanks for all of the clues. I am going to hack on this and see what I can figure out.
Charles On Fri, 26 Sep 2025 14:01:11 +0000, Schmitt, Michael <[email protected]> wrote: >I did have this part of the question wrong. > >The *KEYS table is the source of the keylist, but not where it is used at >runtime. The keys in the keylist are stored in the application profile -- look >for KEYnDEF, KEYnLAB, KEYnATR. > >But there's something odd. Normally you can only have one of each variable >name, but there are multiple KEY1DEF, etc. > >An ISPF profile is actually an ISPF table, composed solely of extension >variables. But ISPF is known to cheat. For example, it stores more than the >limit of extension variables. > >So, either... > >1. The keylist keys are data stored in one extension variable, i.e. it is a >structure in a variable. > >2. ISPF is cheating and the data is some entirely different binary form, not >accessible by ISPF table commands. > > >To see what it isw would need to open a profile as a table, iterate through >the rows, and dump out all the extension variables. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
