How to Enable Concurrent Action Processing › How to Enable and Secure Concurrent Action Processing › Setting Up Security for CAP › How to Configure CA ACF2 for CAP

How to Configure CA ACF2 for CAP

For the CA, Inc. Event Notification Facility (CAIENF) to spawn the SPAWNPROC defined to the C1DEFLTS table, the task must be defined to your security software package with a corresponding default user ID. Using these definitions, CAIENF will start the spawned task. The task will start under the security context of the default user ID, but then switch security context to that of the user submitting the CA Endevor SCM job.

Important: In the following description ENDEVOR is used as both the SPAWNPROC started task name and its corresponding user ID. If your site already has user ID ENDEVOR defined as the alternate user ID, do not use ENDEVOR for your task name or task user ID. Instead, select a different value. The alternate ID (ALTID) is defined in the C1DEFLTS table as RACFUID=ENDEVOR.

To configure CA ACF2 for CAP, complete the following steps:

1. Create an STC logon ID named ENDEVOR for the Concurrent Action Processing Started task by entering the following commands:

   ACF
   INSERT ENDEVOR NAME(ENDEVOR) STC
   

2. Verify that the ENDEVOR logon ID is defined with site-specific logon ID fields such as those fields used to create the UID string.
3. Verify that the ENDEVOR logon ID has access to all the data sets in the ENDEVOR task by writing CA ACF2 security ACCESS rules for the logon ID.

Note: For more information about configuring CA ACF2, see the ACF2 Security Administration Guide or contact CA ACF2 Technical Support.