SE-logs should become more transparent

Starting with z15 HMCs and SEs users such as SooSysprog are no longer used on the SE for Single Object Operation sessions. Starting with z15 HMC/SE all user management for HMC and SE can be performed from the HMC. This complete set of information is then used for Single Object Operation sessions. For example, default HMC user SYSPROG will have the HMC permissions that it typically had, but it will also have the appropriate permissions for the tasks and objects available to the default SYSPROG on the SE. This means that when user SYSPROG from HMC1 Single Object Operations into a z15 SE the user will have a name, such as SYSPROG(HMC1), and have the appropriate permissions for this user from HMC1. The permissions and roles for the SYSPROG user on HMC1 and these will be used when this user Single Operations into a z15 SE. So, the HMC now is the single point of control for both HMC and SE user management and when this is coupled with data replication on the HMC users and roles changes can be made on a single HMC and then shared with other HMCs as well as the SEs being managed by the HMC.

Note that the HMC user information is shared with the SE when ever it changes and is cached on the SE. this means you could in fact walk up to an SE and log in directly on the SE rather than through Single Object Operations using the HMC user information.