Configuring CA VM:Secure for SFS › Before You Begin

Before You Begin

Before you begin the configuration tasks, be sure to address the following items:

• You must provide the CA VM:Secure service virtual machine with access to the MAINT 193 minidisk, or this minidisk’s equivalent. CA VM:Secure needs the SFS utility FILEPOOL EXEC, which normally resides on this minidisk. If you moved this utility to another minidisk, provide the CA VM:Secure service virtual machine with access to that minidisk.

  Important! If you removed this utility in the past (before you started using SFS), you must restore it before you can use CA VM:Secure for SFS administration.

  Note: During initialization, CA VM:Secure reports error 0021E if your site configured CA VM:Secure for SFS, and the access mode for MAINT 193, where the FILEPOOL EXEC is found, conflicts with a mode specified for the VMSECURE product minidisks. Help ensure that the access mode for MAINT 193 is different from any mode specified on an ACCESS record in the PRODUCT CONFIG file.

• User ID VMSECURE must have ADMIN authorization in the Filepool DMSPARMS file.
• CA VM:Secure must be using the Servant Facility to perform some commands on SFS file spaces, such as DELETE.
• If an ESM is being used for SFS authorization, CA VM:Secure servants must be able to access any SFS directory read and write

Important! Additionally, you may notice a file named SFS CONFIG on the CA VM:Secure service virtual machine 191 minidisk. CA VM:Secure alone maintains this file, based on the descriptions and enrollments you add to CA VM:Secure. If you edit this file directly you will invalidate the CA VM:Secure functions for SFS administration.