> Shutting off propagation of the Enqueue for PROFILE would only > apply to logging on to multiple systems in the sysplex. It would > not help if you wanted to log on the same image agani. The ISPF > LOG might be a bigger issue if you wanted multiple concurrent > logons to the same system.
All such schemes tend to run aground on the problem that the reason the ENQ was there in the first place was to avoid corrupting the dataset(s) in question. If there was no need for such serialization the ENQ wouldn't be there in the first place. Tom Conley made a pretty good list of the gotchas in his six minutes of fame at the end of the bit bucket presentation last Friday. As things are now, it's hard to see any rational way to share profile or other "shared" state between userids and between systems. Separate datasets based on the active system name and userid -DO- work now, but that leaves plenty of room for messed up profile variables and utter astonishment with things like edit-recovery etc. ISPF would need to become sysplex aware. There's no reason it couldn't but that's not something it's shown any signs of thus far. And then we would run into the issue of people trying to share things outside of sysplex scope and it would all boil over again... it's a mess. CC ---------------------------------------------------------------------- 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
