|
Type of IMOD |
How CA‑GSS Determines the User ID |
|---|---|
|
IMODs that support operator commands |
If you have defined a user ID through the COMMAND parameter in the PARMLIB data set, CA‑GSS uses it. Otherwise, CA‑GSS uses its default user ID. |
|
IMODs triggered by WTOs |
If you have defined a user ID through the WTO parameter in the PARMLIB data set, CA‑GSS uses it. If not, CA‑GSS tries to determine and use the user ID of the WTO issuer. As a last resort, CA‑GSS uses its default user ID. Note: During execution, an IMOD task may switch user IDs by supplying a new user ID and its associated password to the SECURITY() function. |
|
WTO‑triggered IMODs with ASID numbers matching those on the MONITOR command |
CA‑GSS tries to determine and use the user ID of the WTO issuer. Otherwise, CA‑GSS uses its default user ID. |
|
IMODs supporting the Logon Facility |
If a user ID and password are provided, CA‑GSS uses them. Otherwise, CA‑GSS uses its default user ID. |
|
Server IMOD |
CA‑GSS uses the user ID of the IMOD that started it. |
|
ADDRESS environments and subtasks |
CA‑GSS uses the user ID of the IMOD that invokes them. Note: If a subtask is reassigned to another IMOD, the user ID changes. |
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|