To create a db2.conf file for use with the user exit program

1. Before you create the db2.conf file, you need to create the policies to back up the archive logs and the configuration files.

2. Log on to a client computer.
3. Copy the sample db2.conf file from its location in the sample directory to its active location.

   Its location in the sample directory is as follows:

   Windows: install_path\NetBackup\dbext\db2\samples

   UNIX: /usr/openv/netbackup/ext/db_ext/db2/scripts

   The active location for the db2.conf file is as follows:

   Windows: install_path\NetBackup\dbext\db2\db2.conf

   UNIX: $DB2_Instance_Home/db2.conf

4. In the db2.conf file, create an object identifier for backing up the database.

   This object identifier starts with the following keyword lines:

   DATABASE SAMPLE
   OBJECTTYPE DATABASE
   ...

5. In the db2.conf file, create an object identifier for backing up the archive logs.

   The form depends on how the archive logs are backed up, as follows:

   • If you use ARCFUNC SAVE:

     DATABASE SAMPLE
     OBJECTTYPE ARCHIVE
     

     POLICY WIN_TYPE_POL_LOGPOL # an MS-Windows-NT type policy
     

     POLICY STD_TYPE_POL_LOGPOL # a standard UNIX type policy
     

     SCHEDULE USER_BACKUP_SCHED_LOGSCHED
     

     In the POLICY line, specify the name of the MS- Windows or Standard policy for backing up the archive logs.

     In the SCHEDULE line, specify the User Backup schedule that you created earlier for backing up the archive logs.

   • If you use ARCFUNC COPY:

     DATABASE SAMPLE
     OBJECTTYPE ARCHIVE

     Windows: ARCDIR C:\MyLogs\arcdir\
     RETDIR C:\MyLogs\arcdir\

     UNIX: ARCDIR /home/db2inst1/arcdir
     RETDIR /home/db2inst1/arcdir

     In the ARCDIR line, specify the full path to the location of the archive logs.

     In the RETDIR line, specify the full path to the location from which the archive logs are retrieved. Typically, the RETDIR location is the same as the ARCDIR location.

6. You may need to add other entries to the db2.conf file.

7. Save and close the db2.conf file.
8. Repeat this procedure on each client computer.