On Wed, 29 Jan 2014 08:31:07 -0600, John McKown wrote: >Oh, my. Given the fact that many of our users cannot remember a single RACF >logon id, assigning them multiple would cause chaos. And is against company > Yup. We can't even get a group ID for some tech support purposes. If the employee having the ID terminates, the function vanishes.
>policy. We really need to implement EIM and an SSO solution (zero cost with >no overhead, of course) so that Windows people can access z/OS (TSO, ftp, >and CICS) without needing to do another logon. Of course, this won't solve > But would they want to? IBM needs to wake up and recognize it's no longer the biggest kid in every block, and accept enterprise-wide identity management, not necessarily mainframe based, notwithstanding the advertised security advantages of the mainframe. >all the id problems because we have literally had people forget their name >(Oh? I said kathy.mulligan? It should be cathy.mulligan! But everybody >calls me "cat".) >> At 1/28/2014 09:15 PM, Govind Chettiar wrote: >> >>> A contractor who joined our team said that in his previous place of >>> employment he could have multiple TSO sessions each of which used the same >>> userid and password, so he used to have multiple instances of his TN3270 >>> emulator running and a different TSO session in each. >>> IBM is the only vendor I know of that enforces such an archaic restriction, at least with CMS and TSO. But it's getting better with Unix System Services. (I suspect not with VM/CMS Open Extensions.) It's time IBM woke up. In the bad old days when carbon was cheaper tnan siilcon, we couldn't even afford one terminal per programmer; we had to share. Things should be different now. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
