For example, you can create CONFIGAA as your specifics settings and then DIRMAINT loads it after load CONFIG DATADVH. The CONFIG DATADVH  file is self-documented. For more information, see Directory Maintenance Facility Tailoring and Administration Guide , SC24-6283. Example 6-5 on page 166 

## CONFIGSM DATADVH 

Note:  The CONFIGSM DATADVH  file must be on the 11F disk when it is created. It is updated by using the dirm send  and dirm file  commands to get and replace this file. After changes are made, the DirMaint administrator must run the dirm rldata  command. This command is used to instruct the DIRMAINT VM to reload all DATADVH  files into memory. 

The statements that are shown in Example 6-1 are considered as a good starting point for your CONFIGSM DATADVH  file. DirMaint accepts nn  as AA, BB, and so on. This example uses SM to refer to SMAPI configuration. 

ALLOW_ASUSER_NOPASS_FROM= VSMGUARD * ALLOW_ASUSER_NOPASS_FROM= VSMWORK1 * ALLOW_ASUSER_NOPASS_FROM= VSMWORK2 * ALLOW_ASUSER_NOPASS_FROM= VSMWORK3 * ALLOW_ASUSER_NOPASS_FROM= WAVEWRKS * ALLOW_ASUSER_NOPASS_FROM= WAVEWRKC * ALLOW_ASUSER_NOPASS_FROM= WAVEWRKL * ALLOW_ASUSER_NOPASS_FROM= EDI * ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.TCP= DVHXNE EXEC ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.UDP= DVHXNE EXEC 

This file must  be on the same disk as the CONFIG DATADVH  file. 

Note:  Consider the following points: 

GLYPH<SM590000> The ALLOW_ASUSER_NOPASS_FROM  lines allow SMAPI users to issue commands to the Directory Manager by using the ASUSER  modifier and the password of that user. 

GLYPH<SM590000> The ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT  lines activate an exit that notifies SMAPI of changes that are made to the user directory. 

GLYPH<SM590000> If privacy of residual data is a concern on your system, use DISK_CLEANUP=YES . 

GLYPH<SM590000> The ONLINE= IMMED  line sets your changes to be made immediately. 

GLYPH<SM590000> The RUNMODE= OPERATIONAL  line sets directory changes to be committed. This line can be set to TESTING and the changes are not performed. 

## AUTHFOR control file 

This file defines authorized administrators for your system in DirMaint. Several administrators can be defined in the AUTHFOR CONTROL  file. The file is not included with the product and must be created manually. The file must  be on the DIRMAINT 1DF disk. This file is also case-sensitive and must  be in uppercase. 

As shown in Figure 6-1 on page 161, a set of service VMs are granted full DirMaint authority through DirMaint specific privilege classes (ADGHOPS). These privilege classes represent distinct types of DirMaint roles and correspond to particular DirMaint commands and operations. When updating the AUTHFOR  file, carefully consider the requirements of the VMs that are added and the scope of their authority. 

