                    RSX/IAS SIG Tape Distribution - Fall 1985

                   ===========================================





          This  is  the RSX/IAS SIG Symposium Tape from the Fall 1985 DECUS

     Symposium at Anaheim.  The tape contains  material  submitted  by  the

     user community for the tape at that meeting.  



          The  programs  on this tape are from user submissions.  The DECUS

     staff, the RSX & IAS SIG staffs, and DEC are all in complete ignorance

     of  the  contents of the tapes.  No warranty of any kind is implied in

     the distribution of these tapes.  The programs may or may not be  well

     documented, they may or may not work, they may even crash your system.

     If you have a problem with the  contents  of  the  tape,  contact  the

     author  of  the program.  Do not contact DECUS, DEC, or the RSX or IAS

     SIG's.  



          The  tape  contains  about  3510 files requiring 58,000 blocks of

     disk space.  Since this will fit on a single 2400 foot  tape  only  in

     BRU  at  1600  bpi,  it  is  being  distributed  as such.  To simplify

     distribution and production, the tape is a single BRU  container  file

     followed (for the LUG distribution only) by several extra files.  



          Directory  [300,1] contains the files documenting the contents of

     the tape.  The following files are present:  

     RSX85BTPE.DOC contains an abstract of the contents of the tape by UIC. 

     ALLREADME.85B  contains a concatenated list of all the README files on

        the tape.  

     RSX85BDIR.LIS  contains  a directory of all the files on the tape (BRU

        does not produce nice directories).  This is a brief  listing  with

        UICs and filenames only for space reasons.  

     SUBMIT.DOC contains guidelines for submissions to the RSX/IAS Sig Tape

        collection.  This is MUST  reading  for  everyone  who  desires  to

        submit a program to the SIG tape.  

     BEGIN85B.DOC has a copy of this text.  

     UICSET85B.CMD contains the UFD commands to create all the needed UIC's

        on a device whose name is asked for in the command file.   Edit  it

        to  match your needs before using BRU to extract the tape contents.

        A word of caution:  under at least  some  circumstances,  11M  V4.0

        BRU's  /UFD  switch  creates  directories  even when it doesn't put

        anything in them.  

     If  your  disk  is smaller than an RM03, you will want to exclude some

        files from the copy in order to have a backup set that  fits  on  a

        smaller  disk.  Copy these off in separate passes.  The directories

        [5,*] contain 20001 blocks in 26 directories  and  1613  files  and

        have  a  full  release  and  update  of DECUS C with some utilities

        needed  to   decompress   a   few   files   elsewhere   also   (See

        [4,14]lzpdp11.arc  for  these).   If these are omitted, the rest of

        tape will fit on an RK07.  A  second  pass  through  the  tape  can

        extract the [5,*] directories onto another device.  







                                        Glenn C. Everhart

                                        RSX/IAS SIG Tape Copy Coordinator

                                        RCA AD Engineering ms 206-1
                                             _

                                        Rt. 38

                                        Cherry Hill, N.J. 08358

                                        (609)-338-6022


	READ-ME Files for RSX Fall 1985 SIG Tape
	(Master directory entries mostly; where multiple directories
	exist, further document files generally appear in individual
	directories.)
===========================================================================
===========================================================================
***************************
MD:[005,001]README.1ST
***********
      [5,1] Readme.1st
      DECUS C "scratch" update ([5,*] directories) master document.

	This area  contains  a  full  update  to  DECUS  C system for 
      enhanced  functionality  and   compatibility  with  evolving  C 
      language  standards.    TOTALLY  UNSUPPORTED  (DON'T  call  the 
      authors) but it is believed  the complete kit is here.  LOTS of 
      tools and support for all OSs.    To  obtain  a  working C, you 
      should look over the KIT.RNO file and  others  (redundant  .DOC 
      files have been deleted to make room for  the  whole  kit)  and 
      included  command  files.   Basically you need to assemble  the 
      compiler  and  assembler  and  then if the .OLB files here  are 
      inadequate  you  need to compile the runtime system.  The tools 
      here are  well  worth using even in VMS native mode VAX11C, for 
      which build files  also  exist.  This version has some enhanced 
      compatibility with U**x C  in  its  syntax and the preprocessor 
      has  been  enhanced  to  relieve  many  restrictions  of  older 
      versions.  Some work on floating math has supposedly been done, 
      but its degree of cleanliness is not  known.  Since none of the 
      authors has time to spend weeks putting the code in supportable 
      order,  this  submission  is  TOTALLY  unsupported  but is made 
      available to allow you to at least have something to  try.   It 
      is believed to work but testing has been quite spotty.   If you 
      find something that is broken and you can fix it, please do  so 
      and submit it to a later SIG tape.

	Original directory names follow with UICs on tape:
  [5,1]	Top level directory [decusc]
  [5,2] BIN directory (.H files, libraries, and VAX .EXE's)
  [5,3] COMMAND directory. Documents, more .H files, some other stuff.
  [5,4] COMP directory. Sources for AS and CC, compiler and assembler.
  [5,5] CPP directory. C preprocessor.
  [5,6] CROSS directory. A variety of cross assemblers.
  [5,7] CTEXLIB directory. Part of P/OS version of DECUS C. Access to
		menus, etc.
  [5,10] DECNETRSX directory. RSX DECnet support.
  [5,11] FONT directory. Part of P/OS C kit, fonts for bitmapped display.
  [5,12] LEX directory. A lexical scanner generator for DECUS C
  [5,13] LIBC directory. C library items.
  [5,14] MISC directory. Odds and ends, some quite useful, but not part of
		the compiler proper. Includes a speller, file compress
		utility, and more.
  [5,15] OTSCOM directory. Common OTS routines for C runtime.
  [5,16] OTSIO directory. I/O areas for C OTS.
  [5,17] PML directory. Portable Math Library (in C)
  [5,20] POS directory. Executable DECUS C for P/OS with libraries.
  [5,21] POSCTEX directory. Later version (?) of CTEXLIB for POS C.
  [5,22] RMSPCLIB directory. RMS I/O support items. Used for POS flavor
		of DECUS C.
  [5,23] RSTSLB directory. RSTS (and RT) I/O support items for runtime.
  [5,24] RSXLIB directory. RSX I/O support items for runtime.
  [5,25] SPRSX directory. file I/O-free support for tiny "standalone" C
		programs. Also support's R. Denny's special ACP.
  [5,26] TOOLS directory. LOTS and LOTS of tools no programmer should be
		without. Also buildable with VAX11C. Tom Shinal has
		contributed a super enhanced GREP also.
  [5,27] USEFUL directory. Odds and ends that may be handy compiling C code
		from other systems.
  [5,30] VAXLIB directory. VMS I/O components for runtime.
  [5,31] YACC directory. Compiler-compiler dialect (parser generator) that
		will work with LEX above. (IBM PC versions of these are on
		various bulletin boards also, but have added restrictions in
		space for tables. BBS mods are not here due to space limits.)
  [5,32] ZZDECUSC directory. H files needed (in a directory named ZZDECUSC)
		for P/OS DECUS C.

===========================================================================
===========================================================================
***************************
MD:[240,001]AAAREADME.TXT
***********
	This is VT Kermit from Tad Marshall, Bankers Trust.
It is a complete VT100 emulation in Kermit with the ability
also to handle script files. Look over the other .DOC and
.TXT files for complete documents.
	IBM PC version is supplied as an .EXE and the sources have
Rainbow and IBM PC versions.
===========================================================================
===========================================================================
***************************
MD:[307,020]README.1ST
***********
U.S. Geological Survey                   Fall 1985 DECUS Symposium
Menlo Park, California                   RSX SIG Tape Submissions

We are pleased to present two modest submissions to the Fall 1985
RSX SIG Tape:

------------------------------------------------------------------

Name:              VVC -- Volume Valid Control task
Operating System:  RSX-11M-Plus V2.1E
Author:            Gary L. Maxwell
Version:           V01
How to build:      @VVC.CMD

This task will bring a system disk "back to life" after losing
hardware or software volume valid (whatever the reason). VVC stalls
I/O to the system disk, while it waits for the disk to return to
operating condition. What was formerly a fatal condition under
M-Plus is now recoverable.

Please refer to the source file VVC.MAC for implementation details.

------------------------------------------------------------------

Name:              VINIT.PAT -- Patch file to Fortran-77 OTS
Operating System:  RSX-11M-Plus V2.1
Compiler Version:  Fortran-77 Version 5.0
Authors:           Gary L. Maxwell and Lawrence M. Baker
Version:           F7705Z
How to build:      See VINIT.DOC

This patch fixes a bug in the Fortran-77 OTS which causes Virtual
Arrays to fail in I/D Space tasks. 

Please read the accompanying Multi-Tasker article in VINIT.DOC for
test case and build instructions.

-----------------------------------------------------------------

Please report any problems or suggestions regarding this software
to:
       Gary Maxwell
       U.S.G.S. M/S 977
       345 Middlefield Road
       Menlo Park, California  94025
       (415) 323-8111 ext. 2318

Have fun!
===========================================================================
===========================================================================
***************************
MD:[310,001]README.1ST
***********
TARLUG (Toronto Area Rsx Local Users Group) FALL 1985 submission

Contains:

[310,1]	 This file.

[310,11] BUILD. This is the code for a BUILD command which enables most task
	 builder options to be put on a single line. It is capable of choos-
	 ing  defaults  and relieves most users of having to know  about the
	 task builder, since they will use the BUILD command instead.

	 AUTHOR	Dr. David Villeneuve
		Division of Physics M23A
		National Research Council
		Ottawa Ont. Canada

[310,15] A collection of GRAF subroutines to produce high quality x-y graphs
	 of tabulated functions.  The graphs are labelled, and the endpoints
	 of the axes are chosen to be nice numbers depending on the range of
	 data point values.

	 This is an updated version from the Fall 84 tape,  and contains the
	 following enhancements:
		No longer require privileged account for @MAKEGRAF.
		Support Hershey character set.
		Supply thick and dashed line support (GRDSHL).
		Supply spline fits support (GRSPLI).
		Can now plot curves which don't touch symbols (GRAF1A).

	 AUTHOR	Dr. David Villeneuve
		Division of Physics M23A
		National Research Council
		Ottawa Ont. Canada


TARLUG TAPE LIBRARIAN

Brad L. Tinney
Canadian Hydrographic Service
867 Lakeshore Road
Burlington, Ontario
Canada        L74 4A6

(416) 336-4728
===========================================================================
===========================================================================
***************************
MD:[311,100]README.TXT
***********
**********************************************************************
 
The modules in this UIC([311,100]) consist of the XQ: driver and associated
test codes used to verify its operation. They include all necessary source
codes and their associated command files required for building them. If
they are moved to another UIC some command files may have to be edited
to correct embedded UIC'S.
 
The command file required to build XQ: itself is fairly general
and supports 11M and 11S nodes. It assumes 11S system files to be in
UIC [330,64] and the 11S node tasks to be in [100,30x] where x is the
node address. The driver and .STB file are stored in the node task UIC
([100,30X]).The command file asks the appropriate questions(i hope)
to allow building the driver for various nodes.
 
Three modules are required to build the driver XQDRV.MAC,XQTAB.MAC
and NODEx.MAC where "x" is the node address entered in responce to
the node address question. It must be similar to the one supplied
"NODE2.MAC" i.e., a positive byte is assumed to be a physical address
a -1 is assumed to be the broadcast address and negative bytes are
assumed to be multicast address's. The file nodex.mac must be 14. bytes
long, as the deqna allows for 14. addresses's. These address's are written
into the DEQNA hardware at powerup(driver loading).
 
**********************************************************************
 
XQDRV	IS AN RSX11M DRIVER RESPONDING TO QIO'S FOR THE FOLLOWING FUNCTIONS
 
	SEND PACKETS
	RECEIVE PACKETS
	GET LINK INFORMATION(NODE ADDRESS AND ERROR COUNTERS)
	GET AND CLEAR LINK INFORMATION
	CANCEL I/O
 
XQLOOP 	TEST PROGRAM TO SEND PACKETS TO REMOTE NODES. IT ALLOWS
	SPECIFING THE REMOTE TASK NAME(DEFAULT=LWT...), REMOTE
	NODE ADDRESS, PACKET SIZE AND NUMBER OF PACKETS TO SEND.
 
XQECHO	TEST PROGRAM TO ECHO PACKETS AT A REMOTE NODE, IT MAY BE USED
	WITH XQLOOP TO COMPLETE THE CIRCUIT.
 
XQERR	TASK TO TYPE OUT REMOTE/LOCAL NETWORK ERROR STATISTICS, IT
	ALLOWS ENTRY OF A NODE ADDRESS STRING. IT WILL GET THE INFORMA-
	TION LOCALLY IF ITS OWN ADDRESS IS SPECIFIED AND WILL MAKE
	A REQUEST TO THE REQUESTED REMOTE NODE(TASK=LWT...) FOR ALL
	REMOTE NODES SPECIFIED. THE LOCAL AND REMOTE ERROR COUNTERS
	MAY BE CLEARED IF DESIRED.
 
XQDMP	DEBUG TASK TO PRINT OUT A PACKETS CONTENTS AT A REMOTE NODE.
	INSTALL THE TASK(XQDMP) WITH THE DESIRED NAME IN THE REMOTE NODE
	AND IF A PACKET ARRIVES FOR IT AT THAT NODE THE PACKET CONTENTS WILL
	BE TYPED OUT.
 
XQDGRM	IS A FORTRAN CALLABLE INTERFACE PACKAGE
 
XQMAC	IS A MACRO DEFINITION LIBRARY FOR VARIOUS XQ: PACKET PARAMETERS
===========================================================================
===========================================================================
***************************
MD:[311,101]README.TXT
***********
**********************************************************************
 
THIS UIC([100,3]) CONTAINS XQDRV UTILITY TASKS SOURCE CODE AND THE 
NECESSARY COMMAND FILES TO BUILD THEM. IF THEY ARE MOVED TO ANOTHER
UIC A FEW COMMAND FILES WILL HAVE TO BE EDITED TO CORRECT EMBEDDED
UIC'S.
 
**********************************************************************
 
THIS UIC CONTAINS FILE ACCESS AND DOWN LINE LOAD ROUTINES AS FOLLOWS;
 
LWT	LINE WATCHER TASK(RSX11M)
	PROCESSES CONNECT REQUESTS
		REMOTE FILE ACCESS
		DOWN LINE LOAD REQUESTS
	FLUSHES STALE PACKETS
	GET LOCAL SYSTEM TIME
	SET LOCAL SYSTEM TIME
	ECHO PACKETS FOR TESTING
	SEND/ACCEPT ID PACKETS
	GET ERROR STATISTICS
	GET AND CLEAR ERROR STATISTICS
	GET LINE STATUS
 
NWT	NODE LINE WATCHER TASK(RSX11S)
	FLUSHES STALE PACKETS
	GET LOCAL SYSTEM TIME
	SET LOCAL SYSTEM TIME
	ECHO PACKETS FOR TESTING
	SEND/ACCEPT ID PACKETS
	GET ERROR STATISTICS
	GET AND CLEAR ERROR STATISTICS
	GET LINE STATUS
 
NFC	NETWORK FILE COPY
	ALLOWS OPERATOR INTERACTIVE FILE TRANSFERS
	REMOTE FILE DELETE(NOT IMPLEMENTED YET)
	REMOTE DIRECTORY(NOT IMPLEMENTED YET)
 
RFA	REMOTE FILE ACCESS
	READS/WRITES FILES(BLOCK MODE)
	READS/WRITES FILE(SEQUENTIAL MODE NOT CHECHED OUT YET)
	DELETE FILE(NOT CHECKED OUT YET)
	DIRECTORY(NOT CHECKED OUT YET)
 
DLT	DOWN LINE LOAD TASK
	LOADS SPECIFIED NODE REQUESTED BY THE REMOTE NODE
 
BOOTQNA	PRIMARY LOADER RESIDES IN EPROM IN NODES TO BE DOWN
	LINE LOADED
 
FALODT	ODT/PRIMARY LOADER RESIDES IN EPROM ON FALCON BOARD
	ALLOWS NORMAL ODT FUNCTIONS PLUS ETHERNET DOWN LINE
	LOAD CAPIBILITY.
 
BOOEDT	DOWN LINE LOADER DATA BASE EDITOR TASK
 
PARSX	COMMAND LINE PARSER USED BY NFC
===========================================================================
===========================================================================
***************************
MD:[312,100]AAAREADME.1ST
***********
TRAMP
	This submission is the TRAMP package from the DECUS library.
It contains several programs including a complete forms driver package
and some forms-oriented data handling programs and can serve as a
controllable replacement for FMS in which all source code is available.
It was felt to be of enough general interest to include.
===========================================================================
===========================================================================
***************************
MD:[312,315]AAAREADME.TXT
***********
	RCA FALL 1985 Collection


This tree contains the AnalytiCalc spreadsheet current as of
Dec. 2, 1985 for both PDP11 and VAX. The .OLB files are present
to facilitate use on VAX sites without Fortran compilers.
	To build from objects look in [.PCCOBJ]*.BLD for
instructions.
	To build from source, I recommend using the procedure
[.PCCUNV]PCCMAKIVD.COM  if you have DTR-32, or
[.PCCUNV]PCCMAKIV.COM if you DON'T have DTR-32.

The documents and the older VAX version (with a FEW very minor
bug fixes) are in [.PCCVDOC].

	The [312,371] subdirectory contains both PDP11 and VAX
versions with all functionality. This release adds line fitting,
FFT, and weekday arithmetic, plus a project scheduler and a
set of utilities for accesssing DIF files and some other utility
odds and ends. The extras can be used for data management and
database access. Also supported is a bidirectional interface between
AnalytiCalc and DTR-32 and an address space of 32000 rows and 32000
columns. (!) A couple of major speed enhancements are added here too.
Also (for the VAX version) lots of new string functions and input and
output areas.
	In using, BE SURE to copy [.PCCUNV.AUXKPD]*.* somewhere and
assign it as DK: so that the auxiliary keypad keys will work as
specified!!! Also be sure to SET TERM /NOLINE in VMS V4.x before
using or the arrow keys won't work right.
	The [.DTCVAX] subdirectory has Charles Garman's version
of Desktop Calendar for the VAX. It has numerous useful and handy
features and deserves a look.
	The [312,345] directory has the manuals and the older VAX
version of AnalytiCalc. It works (even a bit better than the spring '85
one did) but is less capable and slightly slower than the new one,
so I discourage its use.
	The [312,375] directory is the .OLB files for AnalytiCalc.
Note that if you build the normal VMS AnalytiCalc and you DON'T
have DTR-32 you need to replace DTRIF.OBJ into PCCX.OLB and then
extract everything and link. Read the instructions in *.BLD in that
directory. Please. The RSX and P/OS task images are there too for those
without the F77 or F4P compilers. Just copy them contiguous and run.
	The [312,315] directory is short and has a couple DL11
comm drivers for RSX11S (one send, one receive) and an update to
Window (very minor). Only sources are supplied. A version of Window
to use the PTY driver is in the works but not far enough along to
supply this time around. It will support up to 10 VT100 type windows.
ALSO present is ASSDEV.MAC, an edit to the FCS module in VAX RSX V2
that does assign lun. This is a work-around of a VAX/RSX problem that
causes VAX/RSX to crash one's images if an assign LUN to LUN 0
occurs. It fakes out the assign to LUN 0 so the images work
correctly. A very slightly updated LST (multicol lister) is provided
also with an .EXE that will work on VMS V4.2 again. There is also a
minor mod to BIGTPC to get it to work on clustered VMS V4 systems again
(with funny device names) by allowing you to tell it that your device
mumble$crud777: is really a tape.

			Glenn Everhart
===========================================================================
===========================================================================
***************************
MD:[326,112]README.1ST
***********
*****************************************************************************
		S P E L L   
 
The SPELL files are part of the submission from E-Systems
Greenville Division.  The update to SPELL (a spelling checker program)
(current version 4.5) adds the overlay "feature" due to increase of the
size of the F77 OTS with v5.0.

ATTENTION SIG TAPE COPY PEOPLE:  There are no task images or object 
files in the libraries.  All procedures are UIC independent but are 
submitted under the UIC assigned last tape ([326,112]).

Jeff Hamilton
E-Systems Inc.
P. O. Box 1056  CBN 28
Greenville, Texas  75401
(214)454-4175 outside Texas  (800)527-1000
*****************************************************************************
===========================================================================
===========================================================================
***************************
MD:[332,012]AAAREADME.TXT
***********
     BONNER LAB RUNOFF                                                  Page 1
     

                                      AUTHOR:
                                      -------
                                   John Clement
                                Bonner Nuclear Lab
                                  Rice University
                                     Box 1892
                                 Houston Tx, 77251
                                  (713) 527-4018


                                     ABSTRACT

                              Bonner Lab Runoff (RNO)

     Bonner  Lab Runoff is a text formatter which when used with your favorite
     editor makes a complete word processor.  Its syntax is almost a  complete
     emulation of DSR (Digital Standard Runoff) and it is very compatible with
     previous versions of Runoff.  The document and help file for this version
     can  also be used for DSR.  The intent of this program is to support com-
     plete scientific word processing to produce publication  quality  output.
     It  has been used to produce thesis, progress reports, and scientific pa-
     pers here at Rice University.  

     This version allows complete control of any special printer available via
     user definable escape sequences.  In addition  a  macro  facility  allows
     text  or  sequences  of commands to be abbreviated to a single label.  If
     the printer has the correct features then variable  spacing,subscripting,
     superscripting, and equation formatting are possible.  By properly defin-
     ing escape sequences the user may support different printers in  a  tran-
     sparent  fashion.   In  other  words  the  same  input text will print in
     identical fashion on different printers with different control codes  and
     escape sequences.  

     Table  of  contents,  indexing  and  sub-indexing  are  all supported.  A
     variety of LAYOUT and STYLE commands may completely change  the  look  of
     the  pages.   Table layout is simplified by right justified and 'decimal'
     justified tabs.  Permanent margins which apply to the  page  headers  are
     available.  These simplify the setting of header and text margins.  

     All  special  characters  are  redefinable.  The user may define new com-
     mands, and text macros.  By defining commands you can  make  it  resemble
     other  text  formatters,  or  other  versions  of RUNOFF.  You may define
     numeric symbols to facilitate  constructing  lists  of  arbitrary  items.
     These  allow page and section references.  A 2 pass option allows forward
     references to symbols defined later in the text.  

     This  runs  under  VMS-native  mode, RSX, IAS, RT11, TSX, P/OS, and RSTS.
     RNO occupies a minimum of 30 to 37 kbytes depending on the operating sys-
     tem.   Complete  documentation,  help  files, and test files are supplied
     with the program for all operating systems.  

                                   Distribution

     This  distribution  contains all files necessary for building RNO for any
     supported operating systems.  Nearly All file names are 6  characters  or
     less  to  acommodate all operating systems.  Once you have built the exe-
     cutable image, you can use it to generate documentation  and  help  files
     for  your  operating system.  Several files are included to document this
     version.  

          1.  BUILD.DOC contains instructions for building the program and do-
              cumentation.  

          2.  RNOBUG.DOC lists bugs that have been fixed.  

          3.  CHANGE.DOC lists the latest enhancements.  

          4.  RUNOFF.DOC  is  the  full document for VMS.  This is not distri-
              buted on small (floppy) kits, but  is  included  with  mag  tape
              kits.  

          5.  INTERNALS.DOC is for wizards only.  

          6.  RNO.EXE is the VMS executable image.  All other users must build
              RNO.  

          7.  *.TST are test files for various RNO features.  

===========================================================================
===========================================================================
***************************
MD:[350,340]README.1ST
***********


	The following utilities are provided by:

	Eddy Fey 
	Utah Power and Light
	Room 125-51
	P.O. Box 899
	Salt Lake City, Utah 84110
	801-535-2795

	2591 E. Grand View Drive
	Sandy, Utah 84092
	801-942-3185

	1.0	Task-to-task Communications and Flying Install Subsystem.

		1.1 RUNNER and INSREM
		    Set of programs used to send parameters to a task,
		    install the task, activate it and remove it upon exit.
		    This is a complete 'flying install' subsystem and will
		    work for permanently installed tasks as well (see RUNNER.DOC).

		1.2 SNDPRM and RCVPRM
		    Interface to RUNNER and INSREM for sending and receiving
		    parameters.

		1.3 VXDRV and VXUTIL
		    This is yet another re-write of the VSDRV by Osudar.
		    It provides mulitple units each capable of having 16kb 
		    of pool space. This will only work on RSX11M+ with I/D.

		1.4 PIPE
		    Interface to VXDRV QIO's for sending, receiving, creating
		    queues.

		1.5 SNDTST and RCVTST
		    Test programs for demonstration.

	2.0	CMB
		Compare binary. Compares two fixed length binary files for
		equality. Can be used for task images, data files, etc.

	3.0	WATCHER
		Nifty patch for finding executive space memory clobbers.

	4.0	IODUMP
		Dumps buffers in hex-ascii byte or word format.

	5.0	BUGMSG
		Prints debug messages only if lun 4 is not assigned to the NL:
		device (i.e. TT: or HT:).

	6.0	SYSMSG
		Prints messages on the system terminal device (ST0:).

	7.0	CDUMP
		Searches a binary CDA file for a given pattern.

===========================================================================
===========================================================================
***************************
MD:[351,040]AAAREADME.TXT
***********

		Cornell University Submissions
		[351,40] to [351,43]
		Coordinated by: Dennis P. Costello
				National Submicron Facility
				G02 Knight Lab
				Cornell University
				Ithaca, NY 14853

				607-256-2329
CADNET - Author: Dennis P. Costello (in [351,43])

	CADNET is a terminal-to-terminal file transfer program which moves
files between VMS and/or RSX systems. It is not as good as Kermit, in the 
following ways:

- no error checking (other than checking the number of characters that come
	over the cable)
- no virtual terminal support (no remote login)
- sending is only by executing a command for every file, receiving is only by
	a receive server (which must be started up from a terminal connected 
	locally to the remote system)
- limitations on file type and record length (variable length records only up 
	to 132 bytes, fixed length up to 512). CADnet does support transfer of 
	source, object, task, and library files.

	CADnet's only claim to fame is that it works on systems where Kermit 
won't; in particular, it will work on RSX Baseline 22 (Version 3.2) systems, 
with the half-duplex terminal driver. It does require the Read with Prompt 
(IO.RPR) support in the driver. Note that this means it will work on Applicon 
860 systems (in fact, it was written for that purpose).

	These tasks have also been run on VMS V3.5 and RSX V4.0 systems. They 
have not been tested on VMS V4.0, and I have no idea whether they will work in 
that environment or not.

	They refer to device MD0:, which is the terminal line over which they
should communicate. I had an ASSIGN/GLOBAL in my SYSVMR.CMD for this line. The
following is the list of terminal characteristics I use. 

(RSX)	Slave, 9600 Baud, Lower, Buf=132., Echo, Norpa, Nohht, Nocrt

(VMS) Terminal: _TTA2:          Device_Type: Unknown       Owner: No Owner

   Input:   9600      LFfill:  0      Width:  80      Parity: None
   Output:  9600      CRfill:  0      Page:   24

Terminal Characteristics:
   Passall           No Echo           Type_ahead        No Escape
   No Hostsync       TTsync            Lowercase         No Tab
   Wrap              Scope             No Remote         No Holdscreen
   Eightbit          No Broadcast      No Readsync       No Form
   Fulldup           No Modem          No Local_echo     Autobaud
   No Hangup         No Brdcstmbx      No DMA            No Altypeahd
   Set_speed         No ANSI_CRT       No Regis          No Block_mode
   No Advanced_video No Edit_mode      No DEC_CRT

	CADnet seems to prefer to work on idle systems. If either end is
loaded, they have a tendency to hang, though they have not yet hung the system
itself. 

	The command syntax is:

	ins $recrem
	ins $xmtrem
	run receiv		{on the receiving system}
	xmt name=name		{ASCII files on RSX}
	xmt name=name/im:512.	{image files on RSX, eg, Tasks, .olb}
	abo receiv		{on the receiving system, to kill RECEIV}

Accounting - Author:	Steve Thompson	(in [351,41])
			Dept of Chemical Engineering
			254 Olin Hall
			Cornell University
			Ithaca, NY 14853

	This package provides month-end billing reportsfor RSX11-M. It will 
almost certainly not work for M+, in addition to being silly in that 
environment, since there is already some accounting available there. 
Charges are levied for many different resources such as CPU time, connect
time, disk space, QIO's issued, lines printed, etc. See the README.1ST for
more information. 

Accounting - Author:	Steve Thompson
			Dept of Chemical Engineering
			254 Olin Hall
			Cornell University
			Ithaca, NY 14853

	The batch system is in [351,42].

	This package provides a complete batch system for RSX11-M. There is a 
Virtual Terminal driver, a multi-stream job scheduler, a means for supplying 
input to a user program from the batch command file, etc. See the README.1ST
for more information. 
===========================================================================
===========================================================================
***************************
MD:[351,070]AAAREADME.1ST
***********

       			       Free software BY
			     Northern Telecom Inc.

	Northern Telecom Inc.
	Network Support Systems Division
	54 Regional Drive
	Concord, New Hampshire 03301
	(603) 224-6511 X2529

	Program:	VTL
	Author:		Robin Miller
	Date:		Fall 1985

     Description:

	This program is used to list file(s) on a VT100 family  terminal.
     The  file(s)  are  displayed  one screen at a time for easy viewing.
     Various commands can be entered to change listing parameters  or  to
     position  to a particular portion of the file.  Many of the commands
     are the same as the Digital editor EDT.   Commands  can  be  entered
     either by using keys on the VT100 keypad, or by entering commands to
     the prompt at the bottom of the screen.  Some of the major  features
     of the program are outlined below:

       o  CTRL/C detection for aborting searches, etc.
       o  Delete the file being displayed.
       o  Display a ruler along the top of the file.
       o  Display the next file or next the directory.
       o  Display record numbers along the left margin.
       o  Display the file header of file being displayed.
       o  Print the file being displayed.
       o  Search (forward only) for a specified string.
       o  Shift the display window left or right.
       o  Split screen mode to display two files.
       o  Teco compatible see-all mode.
       o  Write portions of the file being displayed.

     The maximum record size that can be  displayed  is  512  characters.
     All  commands  have a repetition count of one.  Relative and indexed
     files are not supported.

     The  special  wildcard  characters "* and %" can be used with VTL on
     RSX-11M using FCS for I/O instead of RMS. Previously these were only
     valid  on VMS since a native image was being called to lookup files.
     The  Digital  files  ASCR50.MAC and PARSFN.MAC were modifed to allow
     this  type of wildcard lookup.  Unfortunatly, since they are Digital
     source  files I can't submit them to the SIG Tape.  I hope to submit
     an article on this to the RSX News Letter in the near future.  These
     modified  modules  are  in  the  object library (VTL.OLB) and can be
     extracted  an  used with other programs.  Refer to module VTLOPE for
     further information on using these (must save the file name block).

     [ File "VTL.DOC" contains full documentation for this program. ]

------------------------------------------------------------------------------

     Fall 1985 DECUS Submission.

     This version of VTL has several bug fixes and will now sense the AVO
     setting of the terminal characteristics. Previously, either the /AVO
     qualifier had to be specified, or a taskbuild option changed to let
     VTL know the terminal was equiped with the Advanced Video Option.
===========================================================================
===========================================================================
***************************
MD:[351,071]AAAREADME.1ST
***********

	Northern Telecom Inc.
	Network Support Systems Division
	54 Regional Drive
	Concord, New Hampshire 03301
	(603) 224-6511 X2529

	Program:	CAT
	Author:		Robin Miller
	Date:		Fall 1985

     Description:

	This  is a catchall utility I've used successfully for many years.
     It  allows some capabilities not available in other catchalls and has
     been received very well on the systems I've used it on.  This version
     is much the same as the Digital version except for the following:

	o  It's a privileged task which allows non-privileged users to
	   execute certain privileged commands.

	o  Many of the commands such as DELETE, DIRECTORY, TYPE, etc.,
	   are spawned to DCL for a friendlier interface (allows prompting
	   and switches such as /TODAY).

	o  Allows multiple command lines to be spawned.

	o  Allows commands to be added much easier than the Digital
	   version.  See module CATTBL for more details.

	o  Does not require the definition of the logical names ZZ1: and
	   ZZ2: to use the flying run/install of tasks or global command
	   files in the library account.

	o  Allows both flying run/installs or command file execution.
	   The Digital version allows one or the other but not both.

	o  On RSX-11M, commands can be shortened to a single character.
	   On RSX-11M+, modification of the MCR dispatcher is neccessary
	   to pass single character commands to catchall.

	o  A short command summary is displayed by the "CAT" command
	   along with the current version and last modification date.

------------------------------------------------------------------------------

     CAT for Fall 1985 DECUS.

	This  version of catchall has had several commands added which are
     used to program the Hayes autodial modem connected to another port on
     the  system.  The commands are generic and can be used to program any
     type  of  autodial modem from an indirect command file.  The commands
     used are:

	CHECK	This command checks for the terminal being busy or logged
		on by another user.  The exit status will be:

			success = 1 = the terminal is available.
			warning = 0 = no device or not a terminal.
			error   = 2 = the terminal is logged on.
			severe	= 4 = the terminal is busy.

	SEND	This command is used send the specified string via a
		write-breakthru to the specified terminal.

		Format:	SEND TTnn: Text_to_send [+]

		A logical name can also be used in place of TTnn:
		If the plus sign (+) is specified then overprint carriage
		control is used, otherwise single spacing is used.

	WAIT	Waits for a string from a terminal.

		Format:	WAIT[/D:n] TTnn: match_string [+]

		The  /D:n is the number of seconds to delay before issuing
		the read.  If not specified, we wait 1 second.  The number
		of  characters  in the typehead buffer is then read and if
		non-zero,  the  read  is  issued.  If  a  match  string is
		specified,  then  the  buffer  read  is  searched for that
		substring.  The  plus  sign (+) causes the characters read
		to be displayed at the terminal.  The exit status is:

			success = 1 = read and match of substring.
			warning = 0 = no characters in typehead to read.
			error   = 2 = read with no match of substring.
			fatal   = 4 = directive or syntax error.

     An example of using the above commands can be found in CALLBACK.CMD.
     This command file is used to give a user a callback on a Hayes modem
     pointed to by the logical name RM0:. Also a Runoff file CALLBACK.RNO
     explains how this procedure is supposed to work.
===========================================================================
===========================================================================
***************************
MD:[351,072]AAAREADME.1ST
***********
	Northern Telecom Inc.
	Network Support Systems Division
	54 Regional Drive
	Concord, New Hampshire 03301
	(603) 224-6511 X2529

	Program:	DIRectory
	Author:		Robin Miller
	Date:		Fall 1985

Description:

   The  DIRECTORY command lists the files contained in a directory.  When
   you use certain qualifiers with the command, additional information is
   displayed,  along  with  the  names  of  the files.  The output of the
   DIRECTORY  command  depends on certain formatting qualifiers and their
   defaults.  These  qualifiers  are:  /COLUMNS,  /DATE,  /FULL,  /OWNER,
   /PROTECTION, and /SIZE.

   In  studying the qualifiers and the capabilities they offer, watch for
   qualifiers that override other qualifiers. For example, if you specify
   the  /FULL  format,  the  system cannot display all the information in
   more  than  one column.  Thus, if you specify both /COLUMNS and /FULL,
   the number of columns you requested is ignored.

   Format:	DIRECTORY [file-spec[,...]]

   Additional information available:

   ALL         BEFORE      BRIEF       COLUMN      CONTROL     CREATED
   DATE        DETACH      EXPIRED     FID         FILEID      FORMAT
   FORMFEED    FULL        GRANDTOTAL  HEADING     HELP        MODIFIED
   OUTPUT      OWNER       PARAMETERS  PRINTER     PROTECTION  REWIND
   REVISED     QUALIFIERS  SINCE       SIZE        SPOOL       STARTUP
   TODAY       TOTAL       TRAILING    VERSION

	*****************************************************
	* Refer to the help file (DIR.HLP) for descriptions *
	* and examples of the above qualifiers.             *
	*****************************************************

------------------------------------------------------------------------------

Fall 1985 DECUS Submission.

   This  version  of  DIRectory  has  several  bug fixes and now supports
   directorys of ANSI magtapes.
===========================================================================
===========================================================================
***************************
MD:[351,073]AAAREADME.1ST
***********

	Program:	AUX
	Author:		Robin Miller
	Date:		Fall 1985

Description:

   The  AUX  program  allows  VT100 auxillary key definitions and command
   line editing ala VAX/VMS V4.x systems. The program also saves the last
   twenty  commands  which can then be recalled.  In this release of AUX,
   the  auxillary  keys are statically defined.  A "DEFINE KEY" interface
   may be added for the next version of AUX if it becomes widely used.

   The main AUX documentation is contained in file AUXKEY.PAD.  This file
   is  used  by  AUX to display help from the program when the PF2 (help)
   key  or  the  PF1  (GOLD)  PF2 key is pressed.  This help file must be
   placed in LB:[1,2] for system wide access.

   To start AUX, simply type "AUX" if it is installed, or "RUN AUX".  The
   program is not currently setup as a Command Line Interface (CLI).  AUX
   will  accept input and spawn the command line to your default CLI when
   you press the return key.  To exit AUX, type CTRL/Z.

   The following is the control key definitions:

   Control Keys:

	CTRL/A		Toggle between overprint and insert mode.
	CTRL/B		Skip backward to next character input.
	CTRL/C		Delete the entire command line.
	CTRL/D		Delete to end of command line.
	CTRL/E		Position to end of command line.
	CTRL/F		Skip forward to next character input.
	CTRL/H (BS)	Position to beginning of command line.
	CTRL/J (LF)	Delete the previous word.
	CTRL/M (CR)	Terminate the current command line.
	CTRL/R		Recall all previous command lines.
	CTRL/T		Display one line status report.
	CTRL/U		Delete to beginning of command line.
	CTRL/V		Display the current version number.
	CTRL/W		Refresh the current command line.
	CTRL/Z		Exit from the AUX program.
	DELETE		Delete the previous character.

	!n		Recall command line number 'n'.
===========================================================================
===========================================================================
***************************
MD:[356,040] document
***********
Brian Nelson 21-MAY-1985 11:34
This area contains Kermit-11 updated for all PDP11 DEC OS's. Task images
are also present. See various *.DOC and *.RNO files for info on installing
and using Kermit-11. This is generally the most complete and powerful
implementation of the Kermit protocol on any machine and is a must for
getting your PDP11 to talk to the world.
===========================================================================
===========================================================================
***************************
MD:[356,041]AAAREADME.TXT
***********
Brian Nelson 21-MAY-1985 11:34
	     29-JAN-1986 15:25

This is yet another text editor which was first written a few years  ago
in  Macro-11  and  used on RT, RSTS/E and RSX. The Macro-11 version (not
included here) predates EDT change mode, which is  one  of  the  reasons
why  it  was  written  to  start  with.  This is a complete redesign and
rewrite in C with some Macro-32. It functions as both a line editor  and
full  screen  editor.  The  main  reason  it  was rewritten in C was for
portability and to be able to run in native mode.  Documentation  is  in
the  *.MEM  files  and  also in online help. Note that it is copyrighted
and can not be ported to any other system and sold. 
It does allow multiple paste buffers and multiple file windows, see HELP
and notes at the end of this document.
The PDP11 task image  dynamically determines  actions at run  time based
on the underlying operating system,  thus the same task image  run under
P/OS, RSX11M+ and RSTS/E. On the PDP11, it takes 38KW user + 4KW shared.


[installation info in the document in [356,41], not here.]

For edit history, see EDMAIN.C

===========================================================================
===========================================================================
***************************
MD:[356,044]README.DOC
***********

			Harry Herman
                        Corpane Industries Inc.
			250 Production Court
			Louisville, Ky 40220
			(502)491-4433
			06-Dec-85

This account contains modifications to the DOB program originally released on
the Fall '83 RSX DECUS tape on account [351,30].  The original version was
written by Tom Getzinger of Hughes Aircraft.  This version has been extended
to recognize RT11 object libraries (at least on RSTS), allow global symbols
to be specified, dynamically increase its size as needed, use I&D space (if
your processor supports it), new error messages, print numbers larger than
170000(8) as negative numbers, print comment lines decoding some of the 
Internal Symbol Directory (ISD) entries documented in the TKB manual,
correctly print "TRAP global" and "EMT global" (instead of printing ".BYTEs"),
handle library symbol tables that now specify offsets to start of a library
.PSECT, and a couple of minor bug fixes.

To build DOB, the file "DOB.COM" should be editted to assign "IN:" to whatever
account you decide to put the sources onto, and then invoked.  Note that I do
not have access to a RSX machine, so I do not know if it will work as is on RSX.
The .CMD files invoked by DOB.COM should work as is on either system.  No
DOB.TSK has been provided, so edit DOBTKB.CMD to include the "/ID" task
qualifier if the I&D version of DOB is wanted (M+ and RSTS V9.0 or later), or
remove "/ID" if the I&D version of DOB is not wanted (M or RSTS prior to 9.0
or machines not supporting I&D space).

Once the task has been built, you can install it as a CCL (RSTS) or a known
task (RSX) so that it can take a command line of the form:

	DOB output[/switches[,tmpfile]]=input[/switches].

Or the program can be run with a "RUN [account]DOB" and DOB will prompt for
input of a similar format.

The following switches are recognized on output files:

	/ID	Show version number of DOB.
	/RA	Print comments showing the RAD50 equivalent of whatever is
		disassembled.
	/AS	Print comments showing the ASCII equivalent of whatever is
		disassembled.

A temp file specification is not needed unless you want to put the temporary
file on another disk.

The following switches recognized on input files:

	/ID	Show version nyumber of DOB.
	/LB:modnam	Input file is an object library, and modnam is the
			name of the module to look for inside the library.
	/RT[:modnam]	Input file is an RT11 object library, and modnam is
			the name of the module to look for inside the
			library.  NOTE: this may not work on RSX because RT11
			uses different internal record formats that are
			recognized by the RSTS version of GET$, but may not
			be recognized by the RSX version of GET$.  The module
			name may be specified either here or on the /LB switch.
			The /LB switch is optional with the /RT switch.
	/EP		Modifies /LB and /RT to have DOB search the entry point
			table for modnam if it is not in the module name table.
			In other words, it looks for a global symbol named
			modnam.  This can be used to look for the module that
			defines a symbol ($DSW, for example) if you do not
			know the name of the module the symbol is defined in.
	/[-]EI		Extended Instruction Set (EIS) instructions are valid
			(the default is /EI).
	/[-]FI		Floating Instruction Set (FIS) instructions are valid
			(the default is /FI).
	/[-]FP		Floating Point Processor (FPP) instructions are valid
			(the default is /FP).
Examples are:
	TI:=LB:SYSLIB/LB:ALERR		(Find module ALERR in SYSLIB.OLB)
	TI:=LB:SYSLIB/LB:xxxxx/RT	(Find module xxxxx in RT11 SYSLIB.OBJ)
	TI:=LB:SYSLIB/RT:xxxxx		(Same as above)
	TI:=LB:SYSLIB/LB:$DSW/EP	(Find the module that defines $DSW)


===========================================================================
===========================================================================
***************************
MD:[356,045]AAAREADME.TXT
***********

	CAM	'MAC backwards'

	A sophisticated utility to reduce PDP-11 object code to source
	macro. CAM labels where possible using the original global or
	local symbol names. Many (many) formatting options are available
	including pretty features such as converting 'mov x,-(sp)' into
	'push x' etc.

	It is possible to produce 'listings' or code that can be fed
	directly back into MACRO without editing.

	Currently CAM can handle object modules produced under
	RSX-11M/M+, RSTS/E RSX and RT-11 emulation, RT-11 native
	mode, VMS compatability mode and IAS. CAM has only been
	tested actually running on RSX native mode, VMS RSX
	compatability mode and RSTS/E RSX emulation with native RSX-11,
	VMS compatability mode and RSTS/E RSX/RT-11 emulation input files.

	CAM is written in C and will compile and run under DECUS C.

	A number of support programs are supplied in the CAM package to
	assist in MACRO development and debugging. These include a
	object module analyser on the lines of VMS's "ANALYSE/OBJECT".

	Nick de Smith. Jan '84
===========================================================================
===========================================================================
***************************
MD:[370,020]README.1ST
***********
README.1ST
	This submission consists of three files in addition to this
README.1ST file. The first file, RX037.DOC, is RUNOFF output of
information as submitted to the RSX Session Notes for Session RX037:
Menu Front-End for RSX.  The second file is the indirect command
procedure, MENU.CMD. The third file, named PROJECT.CMD, is a short
command procedure which may be useful for displaying contents of a
short file onto the screen of a VT241, in a manner suited for making
slides or transparancies for a presentation.
	MENU.CMD is a procedure which allows inexperienced users easy
access to various DEC and DECUS utilities and applications.  Some changes
must be made to the MENU.CMD as supplied here to customize it for your
particular installation.  These necessary changes are noted in comments
within the procedure.  DECUS software that this procedure uses is also
noted in the comments.
	This procedure has been very popular with most of our users, and
perhaps, it may be useful for others.  If you have any questions or
suggestions, let me know.

				Submitted by: James I. Shultz
					      U.S. Dept. of Agriculture
					      Nutrient Composition Laboratory
					      Room 216, Bldg. 161, BARC-E
					      Beltsville, MD  20705
===========================================================================
===========================================================================
***************************
MD:[370,021]README.1ST
***********
Documentation for CPU Monitor for RSX11-M/M+

	Don Rubin
	S.E.T. Inc.
	9703 Forest Glen Court
	Silver Spring, MD 20910

 The enclosed program is a graphic CPU monitor for RSX11M/M+. It requires no
modification to the operating system and adds little overhead to the system.
It was created because there is no way to measure CPU availability in RSX
(the stuff on the RMD system page is garbage, ask the DEC developers).

 See CPU.DOC for further info.
===========================================================================
===========================================================================
***************************
MD:[370,037]README.1ST
***********
							06-Dec-1985

			PDP-11 SEARCH UTILITIES
			-----------------------

	This consists of three modules, SEA.CMD, SRP.CMD and TEC.TSK,
	which will allow you to accomplish the following functions on
	A PDP-11:

		1) Search file spec for an occurance of an ascii
		   string.

		2) Search and replace a specified file spec for
		   occurances of a set string and replacing that
		   string with a new one.


	To Search the following is required:

		@SEA a b c

		Where:
			a = is the file spec to search, no disk spec allowed
			    the disk to search thru is SY: (this is due to
			    our version of TECO screwing up the disk spec for
			    disk unit #'s greater than 17 octal).	
			b = is the search string, and no blanks are allowed.
			    this can be overcome by not putting in this
			    parameter (and the following parameter also), thus
			    causing the command file to promt for the rest of
			    the parameters.  That promt will allow any string
			    to be inputed.
			c = is the optional output file spec to put the results
			    of the search.  If not provided, then TI: is the
			    assumed destination.

	To Search and Replace the following is required:

		@SRP a b c d

		Where:
			a = is the file spec to search, no disk spec allowed
			    the disk to search thru is SY: (this is due to
			    our version of TECO screwing up the disk spec for
			    disk unit #'s greater than 17 octal).	
			b = is the search string, and no blanks are allowed.
			    this can be overcome by not putting in this
			    parameter (and the following parameters also), thus
			    causing the command file to promt for the rest of
			    the parameters.  That promt will allow any string
			    to be inputed.
			c = is the replace string, and no blanks are allowed.
			    this can be overcome by not putting in this
			    parameter (and the following parameter also), thus
			    causing the command file to promt for the rest of
			    the parameters.  That promt will allow any string
			    to be inputed.
			d = is the optional output file spec to put the results
			    of the search.  If not provided, then TI: is the
			    assumed destination.

	Also provided is our copy of catchall.cmd that we used to help in our
	development environment.
===========================================================================
===========================================================================
***************************
MD:[370,112]README.1ST
***********
	Programs in this directory submitted thru 
	LILUG, the Long Island Local Users' Group.


XXTAB.CMD	This command file will create a driver database for you, if
		you're lucky enough to be running RSX-11M-PLUS (NOT 11M!).  It's
		a bit more useful than the skeleton databases that abound, since
		you can choose options such as contiguous or non-contiguous 
		KRB/SCBs, whether or not to create a UCB table with the KRB, and
		it even letters your KRBs correctly (they're NOT a-z!).

		BE WARNED that this hasn't been tested to all extremes.  It has
		worked for us, and we've modified it as bugs have arisen.  The
		usual DECUS caveats about "use at your own risk" apply...

		Please forward bug reports/comments to:
			Gus Altobello
			Reuters Ltd, 90 Davids Dr, Hauppauge, NY 11788
			Office: 516/435-7036	Home: 516/367-4211
