Populating the Security File › Populate the Security File

Populate the Security File

To populate the Security File from the CP source directory

1. (Optional) Determine which z/VM minidisks are to be available to all users.
2. Create a file named CAKVDIR ALL that lists each minidisk and its access level (if applicable). For instructions, see the section Specify Common Resources in this chapter.

   CA supplies a user exit named CAKVDIRE used to determine department and name assignments. You can use it as supplied or you can modify it to make assignments based on requirements at your site. For information, see the section CAKVDIRE Command in this chapter.

3. Obtain the CP source directory file, ensuring that it is located on any accessed minidisk or SFS directory.
4. Execute the CAKVDIR command. Inputs to the command are the CP source directory file and the CAKVDIR ALL file (if used); the output is a TSS command file. This file is named direct_fn TSS A.

   For information, see the section CAKVDIR Command in this chapter.

5. Examine the TSS command file, and if necessary, edit it to meet your installation requirements.
6. Activate CA Top Secret, and log on using the MCSA ACID.
7. (Optional) If the TSS command file is in TSSCRIPT format:
   1. Edit the TSS command file to add to the top of the file:

      	//TSSJOB ACID=msca_acid,PASSWORD=msca_pswd
      	//EXEC PGM=TSSCRIPT
      

   2. Save the file as direct_fn SCRIPT fm.
   3. Use the SUBTSS command to submit the SCRIPT file to the TSSVM service machine or punch it directly:

      	CP SPOOL PUNCH tssvm_service_machine_id CLASS B
      	PUNCH direct_fn SCRIPT fm (NOHEADER
      

8. (Optional) If the TSS command file is in REXX EXEC format:
   1. Rename or copy the TSS command field to have a file name of EXEC.
   2. Run the command file by entering the following:

      	EXEC direct_fn
      

   The Security File is populated with security records based on the information in the CP source directory.