[VAX87C.NSWC]AAAREADME.TXT
BATCH COMMAND
-------------
In order to make it as easy as possible for our users to use
batch jobs, we designed this command. It allows them to sub-
mit batch jobs without having to build a .COM file. They just
run:
$ BATCH any_vms_command
and the command gets run in batch mode, in the user's current
default directory. The log gets saved in a special place, and
the user gets notified when the job finishes. See BATCH.HLP
for more details. See BLD_BATCH.COM for building from sources
(you will need to do this, since BATCH.EXE needs to know what
directory BATCH.COM is in; this is hard-coded into BATCH.FOR).
You will need to edit BATCH.CLD.
MAILUAF PROCEDURE
-----------------
This is a procedure to maintain SYS$SYSTEM:VMSMAIL.DAT, which
controls the receiving and forwarding of VAX MAIL. Some system
managers are not aware that removing users from SYSUAF.DAT
does not remove all traces of them; they still have entries in
VMSMAIL.DAT until you manually remove them. DIGITAL provides
an 'example' procedure SYS$EXAMPLES:MAILUAF.COM, on which mine
is based. My version provides additional functions and can be
used in noninteractive situations. See notes in MAILUAF.COM
for details.
REMINDER UTILITY
----------------
This is my appointment-reminding utility. It reminds you when
you log in, and 'tickles' you at fixed intervals as the time
of an appointment approaches. The reminder message tells you
when the appointment is, and what it is. The message is for-
matted in reverse video for VTxxx terminals and the bell rings.
It is very easy to add, remove, and show appointments. For
further information, see REMINDER.HLP. See REMINDERS.DOC for
installation instructions. This utility uses a detached pro-
cess (which is usually hibernating) to send the 'tickler' mes-
sages. Use BLD_REMINDER.COM to build the package from sources.
The files are in subdirectory [.REMINDER] under this directory.
This product has appeared on previous SIG tapes. It has been
updated extensively to add new features (MAIL and BATCH remin-
ders, Recurring Appoinments, /DELETE/CONFIRM) and to fix a few
bugs.
IMPORTANT -- If you already use REMINDER, you must convert the
Event File to the new format. See REMINDERS.DOC for details.
OTHERNODE UTILITY
-----------------
This is a tool for system managers. If you have a cluster, or
any DECnet network, but don't have any nice terminal servers
that allow you to keep sessions active on all your nodes, then
it can be a pain to run commands on different nodes. You can
spend two minutes SETting HOST to node XXXX just to run a one-
second SHOW TIME. Using this utility, you could do:
$ OTHERNODE XXXX SHOW TIME
and get the result back instantly! No time is spent creating
a process on the remote node, because a server is kept running
(mostly hibernating) at all times, waiting to run commands for
OTHERNODE. You can even run multiple commands, and COMMANDS
WHICH REQUIRE INPUT (!!):
$ OTHERNODE XXXX
XXXX> SHOW TIME
30-OCT-1987 15:22:35
XXXX> RUN SYS$SYSTEM:SYSGEN
>> SHOW QUORUM
Parameter name . . .
-------------- . . .
QUORUM . . .
>> EXIT
XXXX> EXIT
$
You cannot run procedures which do INQUIREs, or commands which
expect to talk to terminals (the command is actually being run
on the remote node by a subprocess SPAWNed by a detached pro-
cess). The detached server process is NSWC_SERVER, described
more below. The files are in subdirectory [.OTHERNODE] under
this directory. See BLD_OTHERNODE.COM for building from sour-
ces. You will need to edit OTHERNODE.CLD. Neither OTHERNODE
nor NSWC_SERVER uses anything that has to be INSTALLed.
CHECK_SESSIONS PROGRAM
----------------------
This is a program which is run from SYLOGIN.COM on a cluster.
It displays a message to the user, telling them what node and
port they are using. It also checks to see if they have any
other interactive sessions going anywhere on the cluster. If
they do, messages tell them the count and node names of the
sessions. The NSWC_SERVER process (described below) must be
running for CHECK_SESSIONS to work. See BLD_CHECK_SESSIONS.COM
for building from sources. This program is just RUN (there is
no .CLD). The files are in directory [.OTHERNODE] under this
directory.
NSWC_SERVER PROGRAM
-------------------
This program runs as a detached process on each node in a VAX-
cluster or general DECnet network to support the OTHERNODE and
CHECK_SESSIONS programs. It spends most of its time hibernat-
ing, waiting for requests to serve. Since it is there anyway,
I gave it more things to do (which are optional). Every half-
hour, it prints the date and time on OPA0. Every five minutes
it SPAWNs a subprocess which you can have do anything that you
want done periodically. These times can be adjusted to suit
your needs. See BLD_NSWC_SERVER.COM for building from sources
and NSWC_SERVER.DOC for other implementation information. The
files are in subdirectory [.OTHERNODE] under this directory.
NSWC1LIB.OLB
------------
Object library, with sources, used in building the above prog-
rams. This library is built using BLD_NSWC1LIB.COM. Some of
the routines may be useful to you; they are documented by pro-
logues in the sources. Subdirectory [.NSWC1LIB] under this
directory contains the NSWC1LIB files. Those files have been
put in a save-set which was then compressed; see the AAAREADME
file for instructions.
I will probably in the future only put CHANGES to this library
on the SIG tapes, to save space.
BONNER LAB RUNOFF
-----------------
We use this program, and have modified it and extended it for
our own use. I have NOT included our version this time, but I
would like to hear from other sites using RNO, particularly
those modifying the program.
------------------------------------------------------------------
Submitted by: Alan L. Zirkle Naval Surface Warfare Center
Code K53
Fall 1987 Dahlgren, Virginia 22448
(703) 663-8023