K M S K I T
R E A D M E . 1 S T
V 4 . 1B

***************************************************************************
** Please note. Support for the KMS enhancements is dying fast. **
** (DEC would refers to this as Catagory Z support on an SPD for **
** KMSKIT.) However, things the RSX modifications still work and are **
** still in active use at KMS (until we get a large enough PDP-11 to **
** run M-Plus anyway). However, few attempts have been EVER made to **
** install the whole thing as a package, as you, the user, might want **
** to do. I tend to put changes in piece meal as I have time. The **
** master command files are ant attempt to try and make the kit easily **
** installable, and they actually have been tried a few times. That **
** sadly, does not mean that they are guarantted to work for all users. **
** **
** Please be careful. The SLP files may not conform to the source **
** files you have (though they should). BEWARE-----BEWARE. If the SLP **
** files don't work, if the command files don't work, or if you need **
** help, find a mirror (preferably larger than the pocket variety) and **
** gaze at it intently. Note the face looking back at you. It is the **
** kindly face of your Software Support Specialist. Good Luck!! **
***************************************************************************

The original V4.1 SLP files for the RSX Spring 83 tape were
written to conform to the source files supplied as part of the RSX-11M
V4.1 Field test. I should know better than to do that, but I
honestly thought they might freeze the sources like they said. Well I
got my BL35 kit from SDC, and guess what? Source file changes
everywhere, particularly after applying a prototype Update "B" kit.
Well, the SLP files I am supplying on this tape were designed to be
applied AFTER applying the BL35 "B" update. But, they also should work
with trivial modification on the BL35 sources. The command files
EXESLP.CMD, MCRSLP.CMD and ICPSLP.CMD will display a comment indicating
which sources assume Update "B".

In going from V4.1 (field test version) to V4.2 Updata B version,
all that I ever needed to change was the first ASCII locator string
(which looks for that last audit trail record in the text preamble) to
reflect the correct place for the SLP file audit trail to go. I have
attempted to make the process fullproof, which is a sure indication that
it is bound to fail for some. Three files (EXECSLP.CMD, MCRSLP.CMD, and
ICPSLP.CMD) actually do all the SLPing. They assume most files are the
unupdated distribution files with a NAME.EXT;1 file name. However, a
few (known internally to the command files) are known to be updated (via
Update B). These files assume that the DEC .COR files have been applied
and that the distribution .EXT;1 files have been converted to .EXT;2
files. The .EXT;1 files should not exist for the updated files (I
recommend renaming it to .VGN;1). Anyway, for these special files, a
test is made for .EXT;2 files. If they are found they are renamed to
.VGN;2 (or .VMD;2) and the SLP patches applied.

Now, since Update "B" is at least a few months away from when I
write this, I suppose DEC can always screw things up again by changing
the SLP files on the kit. What can I say. If KMSKIT were a product,
updates would only come out after the updates had come out and were
installed, and I would have the motivation to test the installation
procedure thouroughly. As it is, it's free and you are "on your own".
Since users have not yet seriously proposed that KMS try generating a
"product", my assumption is that users interested in KMSKIT are
generally sophisticated and able to fix minor "bugs" that creep into the
installation procedure.

In practice, I do the following.

1. Distributions sources (.;1) are copied to .VGN;1
PIP *.VGN;1/pr/SY:R/OW:R/GR:R/WO:R
2. Apply DEC Autopatch/Update "xx" to produce .XYZ;2 files
3. Use EXECSLP.CMD, ICPSLP.CMD, MCRSLP.CMD
4. Read each and every SLPed source file to insure reasonablness

I know of no way to set up a command procedure that can tell if the
autopatch has been done and to set things up automatically. Perhaps if
I gave it enough thought... But someone else should worry about this.


As a note of MINOR encouragement, I have all of KMSKIT working on
V4.1 of RSX11M and the enclosed files are the ones I used. This is
NOT (nor was it intended to be) a rerelease of the entire KMSKIT. If
you want the sources for ARC MAIL, some of the utilities, BATCH, etc
look on earlier SIG tapes. These UIC's contain the new material relating
to bringing up KMSKIT on V4.1 of RSX.

The following UIC's are part of the KMSKIT RSX11M Enhancements
Package Update for V4.1.

[344,1] Documentation files. Command file to create the document
files. You need RUNOFF to do this. Hope you have it.


[344,40] Terminal and disk accounting, privlege allocation,
modifications to HELLO, HELP and BYE, account utilities
and report programs.
Run privlege checking and searching both
LIBUIC, NETUIC and SYSUIC on a RUN $ command.
SET /LIBUIC for RSX11M (just like M-Plus).
Enhancements to ...AT. to implement the /-LI switch.

[344,43] Utilities. Updated versions of GREP and LIST

[344,44] Here is a version of the old RMDEMO which runs on VT100's
which are in ANSI mode. This version is almost half as
small as the new version and supports reploting and
easy exit. In addition, if KMS Accounting is present
and active, it provides a dynamic display of the percent
of total system utilization. This version (less
my mods) was distributed with the field test kit of
RSX11M V3.2 and is distributed here courtesy of the the
RSX group. It runs on a RSX11M V4.1 system.

[344,45] PDQ -- Program Development Queues. PDQ is a multi-
queue command file despooler (using QMG...). Submit
a command file for execution. When a program development
queue becomes free, the command file executes at your TI:

[344,61] CCL V9.0. Submitted by Paul Sorenson. Realy slick.
I have fieldtested it and I think you will like
it. Need I say more? CCL is almost too useful to be free.

[344,65] A complete SYSTEM ACCOUNTING package for RSX11M.
While oriented towards providing performance measurement,
it provides the basis for implementing a versitile and
reasonable charge-back accounting system. Some reports
are provided which will do this. Please read SYSLOG.DOC.


Please, create and read the documentation before leaping in and trying to use
the kit!

A discription of all the modifications and enhancements and most of
the utilities is in KMSKIT.DOC. The command file [344,40]KMSGEN.CMD will
provide all required information (or most of it)for building the KMS
Enhancements and a number of the other programs. Read KMSKIT.DOC before
trying to include the executive data base changes. Please note that
it has not been updated since V4.0 and the file REQSB.SLP is no longer
needed. Note also, this is an update kit. Hence all files refered to
in KMSGEN may not bee on this kit.

To use this kit, transfer the files to their respective UIC's. Read all
the documentation over twice. Set /UIC=[344,40] and type @KMSGEN/-MC and run
through a KMSGEN asking for a long dialog. Place the required DEC sources in
the correct places, KMSGEN will try and do all the SLP patches both to MCR
sources, the EXEC modules and the SYSGEN command files. If KMSGEN sucessfully
SLPs the MCR, EXEC and SYSGEN command files, stop, place the OLB's and sources
on your SYSGEN disks and do a SYSGEN if you are incorporating data structures
(accounting) requiring a SYSGEN. Once the SYSGEN is done use KMSGEN again to
create all needed files.

This release kit of KMSKIT is not complete in and of itself. Hence,
some programs if you desire to build them will require getting the
programs from an earlier version of KMSKIT. Where useful programs have
been updated, newer versions have been supplied.

These programs have been extensively tested for the case where all KMS
options are selected and where most DEC sysgen options are selected.
KMSGEN and the command files to implement KMSKIT for the general user have
had almost no testing since I do all patches one at a time checking results
as I go. The first user to try KMSKIT found a bunch of bugs in the command
files. These I tried to fix. But, as we all know, bugs are hard to
completely stamp out. Be warned, be careful, and be alert. Since, I know
the SLP patches once incorporated work, I am sure they can be incorporated
with a bit of perseverence. I appologize in advance for any potential
inconvenience, but current government regulations (let alone my family)
preclude me spending in excess of 24 hours daily at work. I simply do not
have time to do all that I have to do as well as all that I would like to
do.
Good Luck,


James G. Downward
KMS Fusion, Inc.
3941 Research Park Dr.
Ann Arbor, Mich. 48104
(313)-769-8500
22-Oct-1983