CA-L-Serv Configuration Tasks › Update External Security for CA-L-Serv › How the Update Tasks are Accomplished › Usage Notes

Usage Notes

Notes:

• Do not alter security definitions that are previously implemented for CA Endevor Software Change Manager or other products. The security checks made by these products still function in the same manner.
• If you do not discriminate between CA‑L‑Serv data sets, define a resource, 'ALL', in class $LSRVDSN and give users or groups CONTROL access to this resource provides a convenient means to control access to CA‑L‑Serv data sets without having to make extensive new security definitions.
• Allowing the users to use the $LSRVDSN class gives them access to the data sets only through CA‑L‑Serv. It does not provide any access to the data sets through any other program (such as IDCAMS REPRO).
• The privileged users who already have CONTROL access to the data sets managed by CA‑L‑Serv are able to access data sets using CA‑L‑Serv in the same manner as outside CA‑L‑Serv. No additional definitions are necessary for these privileged users.
• The CA‑L‑Serv utility program, LDMAMS, can be executed only under a user ID that has CONTROL access to the data sets.

Important! CA Endevor Software Change Manager users must grant access to the new resource class to the 'true' user ID, not the 'alternate' user ID. When CA Endevor Software Change Manager invokes CA‑L‑Serv, the 'true' user ID is in control, not the 'alternate' user ID.

The following sections describe implementation of external security for CA‑L‑Serv in three different environments.