From: Paul Gilmartin <[EMAIL PROTECTED]> In ISPF, why, oh why, can't I split the screen and bring up SMP/E query on one CSI in one split, and another SMP/E query on a different CSI (or even on the same CSI) in the other split.
I once worked at a place with an in-house application that prevented users from opening the same application in different split screen sessions. The reason was because the dialog would VPUT things into the PROFILE, and the PROFILE of course is shared across split screens. So, if the user opened the application on screen 1 and entered a value, then opened the same application on screen 2 and entered a different value, then swapped back to screen 1 and continued working, screen 1 would work with the value entered on screen 2, and not the value that was originally entered on screen 1. As you can imagine, the results of doing something like this could be very dangerous.
As the application was popular and many people wanted the ability to open it in split screen, I was asked to fix it. This was easy enough to do, as it just meant the application had to be made 'split screen' aware. For example, instead of calling a variable 'VALUE', it had to be changed to 'VALUEx' (where 'x' was a number represented by whichever split screen the user was in).
I don't know if this is the same reason why SMP/E is preventing split screen sessions, but I'm guessing it's probably something along these lines.
Dave Salt SimpList(tm) - The easiest, most powerful way to surf a mainframe! http://www.mackinney.com/products/SIM/simplist.htm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
