Step 7: Define security server profiles for ADNR

Create a USERID profile for ADNR as follows:

ADDUSER  ADNR     DFLTGRP(OMVSGRP) NOPASSWORD OMVS(UID(nn) -
         HOME('/RDWR_working_directory') PROGRAM('/bin/sh'))

ADNR must have read and write access to the directory specified on the HOME keyword. This directory becomes ADNR's working directory. ADNR creates and deletes temporary files in this directory during its operation. The UID value, nn, can be zero or nonzero.

ADNR is a multi-threaded application. If you define an unusually large number of name servers or zones to ADNR, you should check to determine whether the maximum number of threads allowed per process, represented by the THREADSMAX value in BPXPRMxx, is going to be exceeded. The number of threads required for ADNR is determined in the following way: (number of dns statements) + (number of zone keywords within all dns statements) + 3. You can customize the maximum number of threads allowed for ADNR by specifying the THREADSMAX keyword on the ADDUSER command.

The program specified on the user ID assigned to run ADNR must be /bin/sh. For more information about specifying a user program and the ADDUSER command, see z/OS Security Server RACF Command Language Reference.

Add ADNR to the STARTED class profile:

RDEFINE  STARTED  ADNR.*            STDATA(USER(ADNR))