Owner`s manual

Page 5-9System Administration
6.Now you can use the ATTACH statement to link the terminal defined in the
TRMDEF statement with the job defined in the JOBALC statement. (Or, you can
use the SETJOB statement instead of ATTACH; see the
System Operator’s Guide
to System Initialization
for information on SETJOB). Add the ATTACH statement
anywhere after the last SYSTEM command in the file.
ATTACH TERM2,JOB4
Immediately after the ATTACH statement you need to include several statements
to initialize the job.
7.The KILL statement forces a Control-C to the job and makes it ready to receive
and process commands.
KILL JOB4
8.The FORCE statement forces the new job to perform other commands, such as
the MEMORY command. To allocate 256K of memory to the new job, type:
FORCE JOB4 MEMORY 256K
9.If you have a specific disk account you want the new job to log into each time the
computer boots, you can do that too. To log the job into DSK1:[100,1], type:
FORCE JOB4 LOG DSK1:[100,1]
10.To unlock the terminal’s keyboard, type:
FORCE JOB4 VER
11.And finally, add a WAIT command to give the computer time for the new job to
process the above commands before proceeding with the rest of the instructions
in this TEST.INI file.
WAIT JOB4
12.When you have added the statements described above for each job you’re adding
to the computer, you’re ready to perform a test reboot. Warn everyone using the
computer that you’re going to reboot, and when they’re ready, press the
ESC
key
to move to AlphaVUE command level, type G
RETURN
. The computer then uses your
TEST.INI file to reboot.
If everything goes all right, and the new terminals and jobs work to your
satisfaction, you can rename the TEST.INI file to the proper name for your system
initialization file:
COPY AMOS32.INI=TEST.INI
RETURN
Eagle Series Computer Owner’s Manual, Rev. 03