A fews years ago, when working with ISPF, I created new screens with F2 (split) and switch between the screens with F9 (swap). But then IBM changed something and split and swap did not work like before. I had to use "split new" and "swap next". And after changing the keys, I realised that every window got its own key settings (keylists). So before changing the keys, I had to turn off keylists, then change swap to "swap next" and split to "split new". But still not all windows had the changed keys.
I never understood what was the intention of these changes. Who can explain this?
Joined: 01 Sep 2006 Posts: 2372 Location: Silicon Valley
I will take some of the credit (and none of the blame :-) ). As an IBMer, around 1992* (?) I questioned the use of some PF keys: FIND and CHANGE did not make sense in 99% of the panels. And with the advent of popups, that sometimes there was not enough room to display all key settings. I argued for an enhancement and the development team created keylists. Yeah!
At the time, you could only have two screens. After seeing a 'ring' capability on CMS, I also argued for more that two screens in ISPF. The development team added support for up to 32 screens, though only two could share the screen at one time for compatability issues. When you use SWAP, it applies only to the two active screens.
Regarding your post:
1. "I created new screens with F2 (split) and switch between the screens with F9 (swap)"
That is the way I expect it to work with the first screen. After the second screen is created, SPLIT will partition the screen, but a new screen is not created. That is the way it has worked since the mid 1990's.
Like you, I got accustomed to setting F9 to SWAP NEXT, though I kept F2 as SPLIT. When I needed a new screen, I typed NEW and then pressed F2.
I retired 5 years ago. If something changed since then, I do not know.
2. "every window got its own key settings"
Not every panel has it's own keys. Relying on my not-so-good memory, I recall that there were about 40 different keylists in ISPF, though, in practice, you might actually only have to use about 10 of them. Once you customize it, your customization should be there for any panel that uses the same keylist. (maybe more than 10 if there are other products involved). Yeah, I know it is more cumbersome that it should be.
3. "turn off keylists, then change swap"
There are actually two different objects:
a. Each applid has its own keys definition. You use the KEYS command to enter the panel to change the definition. This is one set of keys and it is good for any non-keylist panel in the application.
b. Any panel might refer to a keylist. In order to change the keys here, use the KEYLIST command while displaying the panel and then edit the keylist marked as active (my memory is vague here).
If you turn off keylists for this applid, it should revert to the application wide KEYS definition (see 'a' above). But the scope is still only for the applid, not everywhere.
4. "But still not all windows had the changed keys"
Each applid has its own set of keys. You need to customize each applid. Yeah, I know it is more cumbersome that it should be.
My recommendation is to keep keylists on and use the KEYLIST command to customize F2 and F9 as needed.
* In 1992, I was an MVS systems programmer at IBM Santa Teresa Lab. The developers of ISPF were in North Carolina. They treated me as one of their customers. I feel honored that they listened to me on these ideas (as well a bunch of other ideas). The attachment is of me wearing my 1990's era ISPF shirt, which I still have.