Chapter 8
About Command Files

What is a Command File?

A Command File is a short instruction that functions much like a macro to automate repetitive tasks such as importing a large number of documents, searching, adding nodes to your index tree, and generating reports.

You can SAVE command files, MODIFY and reuse them - or in NUD.IST terminology, RUN them again.

What Can Command Files Do?

You don't NEED to learn how to use command files but sometimes they come in handy. The simplest Command File allows you to import all your documents into NUD.IST at one time - a 'must' if you have more than about 20 files to import.

More complex Command Files allow you to build your Index Tree or add nodes to the tree, perform repetitive searches, and automate the coding of your data.

About the Command File Syntax

Command Files use a specific syntax or structure - and they are very finicky about it -- get one character out of sequence or make one typo and your file won't run. Unfortunately the typical error message is often less than helpful and after a few false starts it becomes quite annoying.

COMMANDS:build tree checking command Problem> Command does not make sense at all.

Do I Have to Use Command Files?

No. Learning to use the proper syntax can be a challenge for first-time users and if you're having trouble mastering this you're not alone. It's just not that easy!! So don't be too hard on yourself.

If you don't want to take time to learn how to write complex command files you can use the 'manual' approach: every command file can be executed manually using index searches.

The Command File Nightmare

Command Files can have unintended consequences! An incorrectly structured command file can rewrite your Index Tree in unintended ways and effectively destroy your project. To avoid this you should:

1. make a backup copy of your project on which you practice using the command files you've written; or
2. make a test project and test your command files there first.

To be safe you should ALWAYS make a backup copy of your project before running complex command files.

You can never have too many backup copies of your project. What would you do if the next time you sat down to work on your project you found the files had become corrupted beyond recognition? Think how smart you'd feel - and how confident - if you knew you had a backup copy - and how you'd feel if you didn't....!!!!

Copyright Bobbi A. Kerlin, Ph.D.
http://kerlins.net/bobbi/research/nudist/
Last updated March 7, 2002