I agree to that, One TSO userid per user in the same LPAR at a time to perform his or her task. I don't understand the the logic of having multiple logon's of the same userid in the *same LPAR* at the same time.
What I experienced is that if a TSO userid is logged on with a LPAR, loggin on the same id with another LPAR will display that particular id is already logged on and used by another user. Also if a logged on id is used to log again on a different CEC in the MONOPLEX, system will be rejected and dropped off (the second log on). We are operating two sites of primary and backup with two CEC's connected with GRS. We do not have SYSPLEX/Parallel sysplex. I read from the discussions that we can have multiple logins, In this case with the above config of a MONOPLEX with multiprocessors at two sites connected with GRS using TN3270/AVIVA, TSO/VTAM, kindly share what profile updates we have to make to have multiple TSO logins with the same id in the different LPARS or accross the processor LPARS. (Example:- TSO userid multiple log on in LPA1 and LPA2 in CEC1 and LPA3 and LPA4 in CEC2). Thank you, Suresh On Wed, Jan 29, 2014 at 8:35 PM, Ted MacNEIL <tedmacn...@bell.blackberry.net > wrote: > I truly believe that one ID per person with the ability to sign on once > per LPAR (and share the same ISPPROF) is simpler to implement. > > I don't believe that the "typical" user needs multiple userids to do their > job. > - > -teD > > 300,000 Kilometres per Second > Not only is it a good idea! > It's the LAW!!! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- *SureshNc* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
