SECURITY

Use the SECURITY parameter to specify how security is implemented in your installation and to assign the CA‑GSS default user ID.

Use this format for the SECURITY parameter:

SECURITY {NONE|SAF} [DEFAULT userid]

The SECURITY parameter takes these arguments.

Argument	Description
NONE	No attempt will be made to limit processing by user ID. All IMOD tasks and subtasks will execute under the authority of the CA‑GSS address space. CA‑GSS will still attempt to obtain a user ID for each requestor and that user ID will be passed to IMODs and ADDRESS environments that request the information.
SAF	This option should be coded if a SAF-compatible security system is installed. CA‑GSS' CALLs to SAF and its use of ACEEs are compatible with operating-system requirements. All security software should support the needed functions.
Userid	There are times when a user ID cannot be assigned to a request. For example, some started tasks do not have user IDs. When no user ID can be determined, this default value will be used. Note: This default must be recognized as a valid user ID by your security system.

Whenever a request for executing an IMOD is received, an attempt is made to determine the user ID responsible for the request.
If the user ID cannot be determined, execution is performed under the default user ID, if one has been specified and it is valid. Otherwise, processing occurs under the authority of the CA‑GSS address space.
SECURITY is syntax checked and then ignored by SRVBATCH, SRVMAINT, and the IMOD Packaging Facility. These programs always execute under the security assigned by the system at job initiation.
If you do not specify the SECURITY parameter, no attempts will be made to access your site's security system.