A. Before loading the routines
Stub routines "%T", "XMB", and "ZU"
If you have no "%T" routine on your system, create one that
just QUITs. %T is not a DHCP routine, but some versions of
'XMYPOST' call it, erroneously.
Similarly, in the "production" namespace, if there is no 'XMB'
routine to start with, create a dummy one that just quits.
Also, make sure you start out with a 'ZU' routine. This is the
routine to which your user startups will be tied. It should contain an
ERR tag, for error trapping. To start with, a "stub routine" like the
following is good enough:
ZU G ^XUS
B. After loading the "MGR" ('%') routines
Make sure that there is a copy of the 'ZISX' routine in the production
account. If not, copy it over from 'MGR'.
C. After loading the 'KIDS' routines (XPD*)
An installation of the Kernel can get hung up thinking that it
is not entitled to update the 'XU' package. To kludge around this, add
a temporary line after tag
I X="XU" Q 7.1
Make sure tag MAIN+9^XUTMTR4 reads as follows:
'Setting $Y' within a parenthesized list causes an error in
D. After finishing the installation
Volume set ID
In order to help ensure that MailMan and TaskMan run
correctly, be sure that the 'Volume Set' named in
is matched by Files 14.7, 14.5, and 8989.3.
For example, if ^%ZOSF("VOL")="AAA", then there should be an
Entry named "AAA" in File 14.7 (the TASKMAN SITE PARAMETERS File), an
Entry named "AAA" in File 14.5, (the VOLUME SET File), and the entry in
File 8989.3 (the KERNEL SYSTEMS PARAMETER File) should have a "VOLUME
SET" multiple named "AAA", too.
That File 8989.3 is supposed to be set up by the routine named
XVIRPOST. If you do not have an entry in File 8989.3, you will have to
build it in order for Kernel Sign-on to run properly.
When you've created the first user in the NEW PERSON file,
you can 'give him programmer access' by entering the following code in
This is "the procedure" mentioned in the Kernel V8
Installation Guide on page 65 under the heading Finish Setting
Up First User Account.
Speaking of the NEW PERSON file, you'll probably want to use
FileMan to Modify Attributes of this File. For example, field 29,
"SERVICE/SECTION" should probably be made non-mandatory.
Re-cross-reference PACKAGE file
When you are done installing the Kernel, it's not a bad idea
to use FileMan's "RE-CROSS-REFERENCE" utility on File 9.4, the PACKAGE
File. This is especially advisable if you have installed the system
using a Global load of MUMPS globals.
Number of output lines -- XUPARAM routine
The Kernel is set up to restrict the number of lines of output
to a "Spool" or "HFS" (file) device. The appropriate parameter is found
in File 8989.3. Alternatively, since aborted output tends to make for
grumpy users, you may (optionally) override this restriction by
changing tag SPOOL^XUPARAM so that it reads
SPOOL QUIT 999999999
Maximum number of users -- XUS routine
Similarly, users are frustrated when they cannot sign on.
Change tag SET1+2^XUS so that "y^1" is replaced by "y^999". This will
"Maximum number of users already signed on"
message, at log-on.