>>> >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.
Then your setup was quite clearly different. The idea of using one userid for all systems in the same plex never really held appeal to the TSO users here. Ours were used to having a different userid on every system (convolutedly derived from the clone id of that system). >They all complained prior to allowing it. Ours didn't. They started complaining when the same userid was allowed. > The only annoyance is the brodcast issue you mentioned. In this shop, it was enough of an issue, that I finally undid all customization (yes, I had used your instructions!). So I am apparently the only one inconvenienced by not being able to use the same userid. :-( >Can you clarify this? Are you saying that if I am logged on to TSO in LPAR1 >then I cannot log on (with the same user ID) to TSO in LPAR2? Not unless there was customization done to explicitly allow this. Also, 'same userid' in this context means defined in the same RACF database and using the same identical datasets (like ISPPROF). >If this is not what you mean, can you elaborate a bit on what you do mean? Check out Marks page on what needs to be done to allow this. As I explained above, the broadcast issue *and* shared EMCS consoles via SDSF finally made me uncustomize the use of the same userid. 'shared EMCS consoles via SDSF': Whenever SDSF.LOG (the syslog/operlog) or ULOG is called, an EMCS console is established. Unless explicitly customized to use a different name on every system for that EMCS console (that was the part I could not get the TSO users to grasp, not even some sysprogs), the default name for that console is TSO userid. Inevitably they were in u/LOG on one system and did not get responses to commands on the system they were currently working. (Yes, I know there is a route command, yes, I know, SDSF can customize the name of the EMCS console, no, I was unable to get *that* concept across.) At this point I regret that I even mentioned duplicate TSO userids in my previous post. Barbara Nitz ---------------------------------------------------------------------- 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
