Installation guide

Installing the AlphaNET Software Page 3-13
AlphaNET Installation Guide, Revision 05
Once the computer has booted correctly, use SYSTAT to make sure the job running NETSER is in an
MS state, and the job running VTSER is in an SL state. If not, recheck your TEST.INI file to make sure
these jobs were properly initialized. If you are unsuccessful after several tries, you may wish to attach
either one of these background jobs to a real terminal during the boot process so you may see any error
messages they may be reporting.
When you have successfully completed the TEST.INI file and used MONTST to test it, rename it to
replace your previous initialization command file. On an AMOS/L computer, enter:
COPY AMOSL.OLD=AMOSL.INI
RETURN
RENAME/D AMOSL.INI=TEST.INI RETURN
On an AMOS/32 computer, enter:
COPY AMOS32.OLD=AMOS32.INI
RETURN
RENAME/D AMOS32.INI=TEST.INI
RETURN
You can now install the physical network connection and its related software. This installation is
described in the following sections.
DETERMINING YOUR CPU ID NUMBER
If you wish to find out what your cpuID number will be (which will save you time if you want to define
ersatz names), you can use the AlphaBASIC program listed below. It asks you for information from your
network initialization file, and returns the cpuID AlphaNET will give you.
MAP1 CPU'SOURCE,B,4
MAP1 CPU'NUM,@CPU'SOURCE
MAP2 NET'NODE,B,2
MAP2 NET'GROUP,B,1
MAP2 NET'NUM,B,1
MAP1 ANSWER,S,1
START:
INPUT LINE "Enter your Network number: ";NET'NUM : PRINT
INPUT LINE "Enter your Group number: ";NET'GROUP : PRINT
INPUT LINE "Enter your Node number: ";NET'NODE : PRINT
PRINT "Your CPU ID number is: ";
PRINT CPU'SOURCE USING "##########";"-" : PRINT
INPUT "Would you like to find another CPUID (Y/N)?
";ANSWER
IF UCS(ANSWER) = "Y" THEN GOTO START
END