How CA-GSS Uses User IDs

CA Global SubSystem › System Security › How CA-GSS Uses User IDs

How CA-GSS Uses User IDs

CA‑GSS executes under its own primary user ID during initialization and when performing some housekeeping functions.

When an IMOD task is created, CA‑GSS assigns it a valid user ID and obtains an ACEE for it. Generally, the user ID is taken from the task that triggered the IMOD task. For example, a request from a TSO user (IMOD editor or SRVCALL() function) is assigned the TSO user ID.

Sometimes, CA‑GSS cannot determine what user ID to use. For example, if a started task, which does not have a user ID, issues a WTO that triggers an IMOD. In these cases, CA‑GSS assigns the default user ID to the IMOD task.

Note: If no default user ID was defined at CA‑GSS initialization, the IMOD task executes under the scope of the primary user ID of the CA‑GSS address space.

Note: CA Technologies strongly suggests that you assign a specific user ID for CA-GSS.

The following table shows how CA‑GSS determines the user ID under which an IMOD executes.

Type of IMOD	How CA‑GSS Determines User ID
IMODs that support operator commands	If you have defined a user ID through the COMMAND initialization parameter in the CAW0OPTN(RUNPARM) data set member, CA‑GSS uses it. Otherwise, CA‑GSS uses its default user ID.
WTO-triggered IMODs	If you have defined a user ID through the WTO parameter in the CAW0OPTN(RUNPARM) data set member, 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 the execution, an IMOD task can switch user ID by supplying a new user ID and its associated password through the SECURITY() function.
WTO‑triggered IMODs with address space identifiers (ASIDs) matching those on the MONITOR CA‑GSS/ISERVE operator 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 subtask	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.