On Thu, 30 Jan 2014 01:21:19 -0600, Elardus Engelbrecht wrote: >Barbara Nitz wrote: > >>We only have one lpar (one system), and I am now logged in 11 times with the >>same TSO userid. We have made sure that each of those TSO sessions has their >>own ISPF profile data set. And each session can have up to 8 split screens. > >Having own ISPF profile makes sense. > That depends. If the user wants to operate in 11 different personae or roles, having distinct profiles makes sense. If the user wants profile changes made in one session to propagate to all subsequent logins, it's undesirable. Perhaps ISPF should be enhanced with a pair of commands, one to sync the DASD copy with the in-storage copy, the other to refresh the in-storage copy from the DASD copy just synched. Or keep the profile in a VSAM data set with shared access.
This doesn't bother me much in UNIX systems. If I want to change my ~/.profile, I edit and save it; otherwise it remains unchanged. >>If you go into SDSF and name all of those SDSF consoles the default (the TSO >>userid), then command responses won't necessarily come back to the console >>that issued the command. > >Indeed, my TSO users sometimes come crying back to me 'where are my >responses/messages', just because they're too lazy to have unique console >names. Oh well... ;-) > That's a bug. It should be fixed. It might be as simple as making SDSF enforce or generate unique console names. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
