Barbara wrote: >> >If you use the same userid on all systems, your users are going to >complain as there can be only one userid with the same name in the >sysplex,
Huh? I've been using the same userid on multiple systems in a sysplex since sysplex was invented. >Mark Zeldens instructions in how-to-overcome that not >withstanding. >> They all complained prior to allowing it. I would say 99% prefer it (and I still get emails / calls all the time about this from people who want to implement it at other shops - even though I think my doc is pretty clear). The only annoyance is the brodcast issue you mentioned. We all live with that and as Ted wrote, I try to logon to the system where I usually submit my jobs first. That system in each plex is where we encourage TSO usage anyway and it gets better TSO response time since there aren't any production CICS/DB2/MQ regions. >> I've used the same ID on multiple systems for years. I even wrote a >REXX EXEC to help with the creation of separate ISPPROF datasets for >ISPF -- it's on the CBT tape somewhere. >> Yes, there is a tendency to drift; so what? >> Just allocate it in the logon clist with &SYSNAME. > >The downside of that is that the ISPPROF datasets will have different >contents. What you did on one system, will be unknown on the other >systems profile dataset. This is a change that can have unforseen and >not easily solvable consequences. I don't talk about my last dataset >edited and so, but about information saved by applications. > One time consideration (for each system). So 11 years ago when I implemented it at this shop (when I was consulting), people had to start with fresh profiles for each system. But what myself and all the other sysprogs did was copy the original ISPPROF data set to the new one(s). BTW, I also left it as an option to use the multiple system logons. The logon clist (even today) first checks for the existence of a ISPPROF without the sysname in it. If it exits, it uses that one. At the same time I did this, we were changing userid naming conventions, so I set up the new userids to always use the separate ISPPROFs. For anyone using their old userid, they could still switch by manually allocating the proper ISPPROF name. Also, as of z/OS 1.9, ISPPROF sharing is supported by ISPF. See the "Profile Sharing" section in the ISPF Planning and Customization manual. Here is a link to my doc: http://home.flash.net/~mzelden/mvsfiles/$sngltso.txt Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
