Owner`s manual

Page 3-2 Chapter 3
If you did modify the file directly, and made a mistake, before you could again use the disabled
disk as a System Disk, you would need to bring the computer up off of another System Disk or
warm boot tape, and transfer over a copy of a good system initialization command file.
If we seem overly cautious in handling the system initialization command file, just
remember—When you press the RESET button, the computer will not boot if your system
disk does not contain a good system initialization command file!
Remember, too, the system initiailization command file must have the proper name and
extension (for example, AMOSL.INI or AMOS32.INI).
This section discusses the procedures you should follow when modifying a system initialization
command file.
Before you begin, it is a good idea to make a bootable backup copy of your System Disk.
The first step is to make a copy of your system initialization command file. In this example,
we’ll call it TEST.INI:
COPY TEST.INI=AMOS32.INI
RETURN
Now, edit the TEST.INI file using the AlphaVUE text editor:
VUE TEST.INI
RETURN
When making a number of changes to the TEST.INI file, it is wise to test your changes
in steps. For example, if you are going to add two new terminals, add a disk device,
and change job memory allocations, do just one set of changes at a time. For example,
add the new terminals and then test the TEST.INI file. If everything works well, then
add the disk device. After successfully testing the TEST.INI file again, make your
memory allocation changes. In other words, keep the number of changes to a
minimum. Then if you make an error, you won’t have to wonder which of the many
changes you just made caused the problem.
The next chapters will take you through the editing process, explaining how to change each
area of the system initialization command file.
System Operator’s Guide to the System Initialization Command File, Rev. 03