ADMINISTERING
You can use indirect files to run the same maintenance task multiple times, resulting in significant time savings. The fixup, compact, updall, design, convert, and replicate tasks support using indirect files. You can also create batch files or scripts that run several maintenance tasks serially against different indirect files to help complete them quickly. If you have multiple CPUs, you can run the same maintenance tasks against multiple indirect files so they run concurrently. It is recommended you only run as many concurrent maintenance tasks as you have CPUs, otherwise they will start competing for CPU resources and can take longer to complete.
About this task
This procedure includes steps for running indirect files with or without multiple CPUs. Steps that involve multiple CPUs are identified as such in the instructions.
Procedure
1. Create a text file with the .ind file name extension. For example, mailfiles1.ind.
2. Add the list of databases and or directories to the text file. For example, in the mailfiles1.ind file, you would add these files:
load compact -c mailfiles1.ind
load updall mailfiles1.ind
load design -i mailfiles1.ind
load convert -u -f mailfiles1.ind * mail85.ntf
d:\notefile> c:\notes\nfixup.exe -j mailfiles1.ind
d:\notefile> c:\notes\ncompact.exe -c mailfiles1.ind
d:\notefile> c:\notes\nupdall.exe mailfiles1.ind
d:\notefile> c:\notes\ndesign.exe -i mailfiles1.ind
d:\notefile> c:\notes\nconvert.exe -u -f mailfiles1.ind * mail85.ntf
Note: The design task requires the -i parameter prior to the indirect file name, and the convert task requires the -f parameter prior to the indirect file.
load updall mailfiles2.ind
load updall mailfiles3.ind
d:\notefile> c:\notes\nupdall.exe mailfiles2.ind
d:\notefile> c:\notes\nupdall.exe mailfiles3.ind
For example, if you have 100 mailfiles that you want to run updall against and the computer has four CPUs, create four indirect files: