Owner`s manual
Page 8-2 Chapter 8
8.3CREATING A MINIMAL FILE
There are times during addition of new hardware to the computer or when
troubleshooting an existing computer when it is handy to create a minimal system
initialization command file. This is a system initialization command file that contains the
minimum number of commands under which your computer will boot.
The advantage of a minimal initialization file is it lets you track down the problem you
are searching for or add a new device without worrying about interactions with
extraneous jobs and programs.
Once the computer comes up with under the minimal initialization file and works well,
you can then begin to add items from the original initialization file one by one, testing
between each addition, until you are sure the computer is operating correctly.
If you are not familiar with the elements of a system initialization command file, make
sure you have read the early parts of this manual before trying to build a minimal
initialization file.
To create a minimal initialization file, make a copy of your system initialization command
file. For example:
COPY MINI=AMOSL.INI
Now, edit the MINI.INI file with AlphaVUE, and reduce your computer to a one person,
one terminal system.
NEVER modify the file itself—modify a copy.
You may want to eliminate any device definitions for non-System Device devices.
Remember, the reason you are building the minimal initialization file will dictate exactly
what items to remove. For example, if you are troubleshooting the printer spooler, you
will probably want to leave the definitions for the printer and the spooler job.
Some items that MUST be in a minimal initialization file are:
A JOBS command.
At least one TRMDEF command (defining the Operator Terminal).
A PARITY command.
A JOBALC command.
At least one DEVTBL command (even if with no argument).
At least one BITMAP command.
System Operator’s Guide to the System Initialization Command File, Rev. 03