The following UIC's are part of the KMSKIT RSX11M V4.0 Enhancements
Package.
[344,1] Documentation files. All FCSRES features supported in
previous releases are now supported by DEC with the
PLAS ANSI FCSRES. KMS no longer supports the command
and ODL files for the 4K non-ANSI, non-PLAS FCSRES.
[344,2] HELP files specific to using this kit.
[344,3] Command files (.COM) and what not which has been useful to
us in migrating from RSX to VMS. Note, that we have command
files which do identical things on both our systems.
Note, also the super-dooper SPR generator for VMS, and
the MEMO and word processing files.
[344,5] Useful command files. MEMO is used for automatic memo
generation and filing. WP converts a VT100 to a menue
driven word processing terminal. BUILD is an indirect
command file which is used in dynamically creating
procedure files for PIN. These files use BLD.CMD and
OPT.CMD when they run to do the taskbuilding.
COMPILE and LINK are also supplied as examples of
using indirect command files to provide a CCL command.
SPR.CMD - The RSX group likes this one. It will produce
legible, machine generated SPR addendums. SPR
administration will now accept these if you send
in a preprinted form with your name attached and
6 or so copies of the addendum. In addition it will keep
a file of all SPR's sent which you can use to keep track
of where they are in the system.
[344,40] Terminal and disk accounting, privlege allocation,
modifications to HELLO, HELP and BYE, account utilities
and report programs. Mark Johnson's MAIL Utility
for V4.0. 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. An enhanced version of RMC which uses
the RPOI$ (Chain) directive if available so RMC
can exit at once before command completes and still
have exit status passed on. This version of RMC was
written to use the new F77 compiler.
[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 only on a RSX11M V4.0 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:
Also included is a Procedure Interpreter (PIN) for use with
BATCH. PIN is used as a replacement for ...AT. by PDQ
When built with FCSRES, PIN is 4 times smaller than ...AT.
The previously released version of BATCH can be obtained from
previous SIG tapes. It still should work but is not now
in active use on our system. We use PDQ. However, include
is an updated VTDRV. The update only is for its data bas
so it can work on a multi-CLI system.
[344,61] CCL V8.0. Alternate CLI support. Uses the RPOI$ directive.
Need I say more? 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.
[344,66] This UIC contains programs and command files to aid in
measuring system performance. LOAD.CMD will measure system
performance for from 1 to 'n' concurrent program development
sessions. To fully utilize its features it is best to have
implemented KMS accounting, but some rough benchmarks can be
done with a vanilla flavor RSX11M V4.0 system.
For systems with KMS Accounting, program SNPSHT will
produce a snapshot of the system performance statistics
which are collected by SYSLOG. SNPSHT produces a command file
for setting global parameters(.SETN $PARM val) so that a
controling command file can use the values. Also a program
(DSKMON) is provided to measure the load on one's system disk
(how much time it spends busy).
To create the kit documentation, SET /UIC=[344,1] and type
@CREATEDOC.CMD.
A version of RNO is on [344,1] which will be used if you do not have
RNO installed on your system. 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.
To use this kit, transfer the files to their respective UIC's. The
user with an RK05 system (like I used to) is going to have a bit (a lot) of
trouble since there are a lot of files. If the HELP and documentation files
are all transfered to a seperate disk, then a RK05 can be constructed
containing just the kit sources, command files, SLP files, and DEC virgin
distribution source files and .OLB files. (with room left over for
taskbuilding). However it will be tight. 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.
It is very important that any user implementing these enhancements
to register its use with me. If any bugs are found that are of consequence
I am prone to mail out bug fixes to the current distribution list. Also
direct feedback to me is important for deciding if features/programs are
to be enhanced, maintained and supported from one RSX11M release to the
next.
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.
Other options/configurations of this KIT are possible, but until I start
getting feeback from other users who have configured their option selection
option selection differently, I will not know if I got all the conditional
code correct.
Good Luck,
James G. Downward
KMS Fusion, Inc.
3941 Research Park Dr.
Ann Arbor, Mich. 48104
(313)-769-8500
05-May-1982