In a recent note unmask]> said: > Date: Mon, 29 Aug 2005 17:52:03 -0500 > > 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. > (Thanks for correctly surmising my intent when I neglected to mention MIM.)
Understood. I was merely stating an analogy: the preponderance of our users find the problems associated with concurent update of profile from different systems less onerous than the prohibition of concurrent sessions. I conjecture they would likewise find the hazards from concurrent sessions on a single system no less bearable. I frequently run concurrent ISPF sessions on different systems with a shared PROFILE. I have never experienced a significant corruption of the profile data set (no ABENDs in OPEN, BLDL failures or the like). I am irritated by the occasional loss of profile updates (last session wins), but that's hardly worse than similar contention over saving the pattern from DSLIST or the owner from SDSF. What does ISPF do if I split the screen and enter 0.x in each split, and make conflicting profile updates in the two splits? I expect the same when I run concurrent ISPF sessions. Generally, last guy wins. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
