========> [VAX89A1.AEPSC]AAAREADME.TXT;1 <======== AMERICAN ELECTRIC POWER SERVICE CORPORATION Spring 1989 VAX SIG Tape Submission Paul R. Sorenson AEP/Engineering Computer Support Center 1 Riverside Plaza Columbus, OH 43215 This submission to the Spring 1989 VAX SIG tape contains: 1) VDDRIVER - yet another version of a virtual disk driver (VD:) !? There was confusion on my part as to whether previous versions handled segmented virtual I/O properly, so this version was born. 2) CDDRIVER - disk data caching driver. Hooks into a standard disk driver and caches the most recently accessed blocks in memory. Also provides a "recording" function to log all I/O performed on the disk. Consult the AAAREADME.TXT files in each subdirectory for more information on the features of each driver. Note that by creating a virtual disk and creating the same sized cache for the virtual disk, one can approach the I/O performance of a memory disk while always maintaining an up to date copy of the data on a physical disk. DISCLAIMER All programs, information, and copies are provided "As Is". American Electric Power Service Corporation and the contributor disclaim all warranties on the programs, including without limitation, all implied warranties of merchantibility and fitness. ========> [VAX89A1.ALLIED]AAAREADME.TXT;1 <======== Spring 1989 Submissions to the VAX SIG Tape from Allied Electronics Fort Worth, Texas Allied Electronics' submissions consist of a number of useful command procedures and programs. More complete descriptions of the submissions can be found in the AAAREADME.1ST file in each sub-directory, and within the programs and procedures. [.Allied.DCL] Command procedures to o Execute AUTOGEN and provide you with a complete list of changed SYSGEN params, with before and after values o Submit an executable to run in batch without having to make a command procedure for it. o Run VPA and send a MAIL message indicating if any `conclusions' were reached. o Do $INSTALL REPLACE commands on every node in a cluster using SYSMAN. o Optimize and rebuild indexed files. o Display a number of VPA graphs for the previous day. [.Allied.Login] A Macro program (mostly Hunter Goatley's code from the VAX Professional Magazine) with some mods I added. It should speed up logins considerably for anyone who is doing more than a few logical and symbol assignments via DCL in their current LOGIN.COM. [.Allied.Send_Mail] This directory includes a Fortran subroutine and a BASIC function which make use of DEC's undocumented (and as yet unsupported) Callable MAIL Interface to send a message. Jim Geier of General Instrument sent me the Fortran code in response to a message I posted on DECUServe. I wrote the BASIC code because we don't have a Fortran compiler. Object code from the BASIC function is included in this submission. Please direct any questions, comments, etc., to Alan Bruns Allied Electronics 401 East 8th Street Fort Worth, Texas 76102 (817) 336-5401 ========> [VAX89A1.APPLIEDRES]AAAREADME.TXT;1 <======== Applied Research Corporation Page 1 DECUS VAX SIG Tapecopy Submission 28 April 1989 Applied Research Corporation Suite 920 8201 Corporate Drive Landover, Md 20785 (301) 459-8442 Submitted By Don Stevens-Rayburn Director of Computer Services 1 Overview Of This Submission This area contains a variety of user-mode programs and programming utilities that have been written at Applied Research Corporation and that we have found useful. Included is the full source code for each of the programs and utilities along with both object code and, where appropriate, executables. In addition, more-or-less complete user manuals and programmer manuals are included. The major components of the submission are described in the following sections. 1.1 Address Database Management The address database managment system provides a powerful set of software for automating address/telephone lists. This system supports private address databases, group-wide databases and corporate-wide databases. This program is based on the A.R.C. Forms Management System and is completely menu-driven. It has the capability of searching a database on any field or combination of fields, including up to 6 key words that are part of each record in the database. For example, is is a simple matter to request the system to display all of the entries in the database that refer to people who (1) have names beginning with the characters ST and (2) live in the state of Maryland and (3) have the key words "FORTRAN", "MACRO" and "DCL" in their record. Finally, the program can print the selected records in a variety of ways: (1) the complete record; (2) only that part of the record that the U.S. Postal Service needs, formatted for direct printing on mailing label stock; and (3) as a telephone list containing just the name and up to 2 telephone numbers. As well as two standalone programs that implement the system, there are two separate callable interfaces to make it easy to incorporate address database management into larger menu driven systems. Page 2 1.2 Documentation Utilities Included are two routines which we use here to assist in maintaining programming documentation. CLEANMEM is a simple program that reads a ".MEM" file produced by Digital Standard Runoff and strips off the imbedded characters that DSR leaves in the file. This is useful when you wish to use multibuffer editing to proofread DSR output. You can put the original ".RNO" file in one buffer and the "cleaned" ".MEM" file in another. The ".MEM" file can be scrolled through and read easily without the distracting control characters at the end of each line and, when you find an error or an edit that you wish to make, you switch to the buffer containing the ".RNO" file and make the change directly. At our site, this routine saves a lot of paper and a lot of wear and tear on the laser printer. DOCUMENT is a routine that searches an entire directory and extracts the comment header blocks from all of the source code files in that directory, formatting them as a DSR input file. This routine assists in maintaining programming documentation. This requires that the programmer use a standardized comment block in each program module. Each source code module in this submission contains such a block and several templates are provided. 1.3 Forms And Menus The Applied Research Corporation Forms Management System is the major part of this submission. The ARC FMS consists of a suite of subroutines and a set of FORTRAN include files contained in a text library. It is designed to assist in the coding of programs that are menu driven and/or rely on forms manipulation for data entry and editing. This set of routines is the basis for all of the menu/forms based programs included in this submission as well as a variety of other systems in production here. The ARC FMS is based on the Digital Screen Management Facility but, for example, allows you to design and manipulate forms and menus with only a few subroutine calls. For example, one can present a form to the user and allow the user to edit any field on the form with a single call to one of the FMS subroutines. 1.4 The Form/Menu Demonstration Program The Form/ Menu Demonstration Program is an example of how the ARC FMS can be used to provide a completely menu-driven system to non-technical users of a VAX. The program presented here is, in fact, a copy of the program that our finance group uses daily. The only modifications that I have made to the program prior to submitting it are to remove any proprietary software that gets run from the system. While it is unlikely that this program will be of direct use at your site, it does provide a framework for a complete menu-driven system. Should you be required to write such a system, you will find this program worth reviewing and you may be able to re-use large chunks of it. Page 3 1.5 The Make Facility This is yet another implementation of a Unix-like MAKE facility. It is provided here mainly because we have used it to build all of the executables in this submission and is the easiest way for you to rebuild them if you wish to modify them. MAKE is provided in two forms: first as an executable, with source code and as a DCL command file. 1.6 Portwatch V2.0 Portwatch V2.0 is yet another idle terminal killer. This version is a total rewrite of an idle terminal killer that appeared on an earlier SIG tape submitted by J. B. Fischer. This version maintains a database of each terminal port on the system. For each port, you may specify whether processes running at that terminal are eligible for deletion and at which hours of the day. In addition, you may specify whether or not warning messages are broadcast to the terminal before process deletion. As an example, here we are not so much worried about people tying up terminal lines since (at least for the moment) every terminal has its own port. But we are concerned, for security sake, that everyone log off before leaving for the day. Therefore, most interactive sessions are protected from deletion during the hours 08:00 through 18:00. If you are logged on after 18:00 but inactive, it is assumed that you have gone home and your process becomes eligible for deletion. The major exception to the above is those ports which are connected to modems. Since we only have a few modems and since, if your process is connected to a modem line but has been inactive for more than 30 minutes, it is likely that you have lost the connection and away goes your process. Finally, while it is nice to warn people before killing their process, this is not always possible. For example, if you attempt to warn a process running on a port connected to a Hayes compatible modem (or most other modems) but for which the connection has been lost, all you will accomplish is to set up an interesting dialog of error messages flashing back and forth between the VAX and the modem. In addition, we have a bunch of Professional 350's that function mostly as standalone workstations but which occasionally connect to the VAX via async lines. If the operator of one of these work stations exits the terminal emulator without logging off the VAX, attempting to send a warning sets up a similar dialog. Therefore, Portwatch was written in such a way that you can specify on a port-by-port basis whether to broadcast a warning message prior to process deletion. 1.7 QMS Kiss Driver QMSPRINTV2 is both command-line and a menu-driven interface to one of our laser printers. Again, this routine will probably not be directly useful at your site unless you happen to be running a QMS Kiss laser printer in QUME emulation mode; however, it does provide an example of how to make the full power of a laser printer available to users who have access only to EDT and/or EVE on a dumb terminal. For example, we also have an LN03 driver that was Page 4 written in about a day simply by copying the QMSPRINT code to a new directory and modifying it. 1.8 Show Purge There are three small programs that make up this set. First, there is the SHOWPURGE program itself which has a command line interface and which takes most of the same parameters and qualifiers as does the DCL PURGE command. However, it does not actually delete anything; rather it informs you, by default, how many files would be deleted by a PURGE and, optionally, which files. The second and third programs work together as a gentle way of reminding users to purge old versions. The first merely creates an indexed file with room for a username and a quadword time; the second, which is run at login time via SYLOGIN.COM, determines the username of the person logging on. It then looks up that username and time in the ISAM file. If the time recorded for that username is less than a month ago, the program simply closes the database and exits, thus slowing login by only a fraction of a second. On the other hand, if either the username is not in the file or if the time recorded is more than a month ago, the program enters the user name and the current time in the file and closes it. It then searches the user's directory tree and displays a message of the form: Purging ddcn:[directory...]*.* would delete nn files occupying mm blocks. This serves as a gentle reminder about purging outdated files and has met with good success here. 1.9 Telephone TELEPHONE is a autodial routine that dials a modem without the user having to know anything about which port the modem is on or even about what kind of modem it is. It is implemented as a DCL command and does allow the user to specify all of the communications parameters, including baud rate, parity etc. In addition, it can use a variety of terminal emulations/file transfer protocols and even implements a "telephone" book by using DCL symbols. For example, if you were to include the line: $ ARC :== "1-301-nnn-nnnn" in your LOGIN.COM you could issue the command $ TELE[phone] ARC and TELEPHONE would call up our machine. Once a connection has been established, TELEPHONE spawns a subprocess running the terminal emulation system of your choice. When you exit that subprocess, TELEPHONE gets control again. It makes sure that the modem has hung up properly and that it is reset to power-up defaults. The current version of TELEPHONE supports Hayes compatible modems as well as DEC DF112 modems and works whether or not the port that the modem is on has even minimal modem control lines. Page 5 1.10 Time Management System TMSV41 is a time management system that allows you to keep track of what you should do and when you must do it. It also can keep track of what you have done and when you did it. The Time Management System is based on the ARC FMS and has both a command-line interface and a fully menu-driven interface. 1.11 Utilities Finally, there are a collection of utility routines. These include routines in several categories: o CLI routines for parsing the command line. These routines make it easy to determine what the user wants your program to do. o Lexical functions. Included are callable implementations of the following DCL lexicals: o F$EDIT o F$FILE_ATTRIBUTES o F$GETGPI o F$INTEGER o F$LENGTH o F$MODE o F$PARSE o F$PID o F$SEARCH o F$USER o Various functions. A small collection of functions that perform a variety of tasks such as declaring exit and AST handlers. Some of these routines have been modified from routines that others have put on previous SIG tapes. ========> [VAX89A1.ATG]AAAREADME.TXT;1 <======== Submission from: Nick de Smith Applied Telematics Group Ltd. Telematics House Vale Avenue Tunbridge Wells Kent TN1 1DJ England Voice: +44 892 511000 PSI MAIL: PSI%234213300154::NICK All programs and routines are (fully) tested, and believed working under V5.1. This includes the device drivers and all KERNEL mode code. I am always interested in (constructive) critisism and correspondance. Included here is all I could prepare in time. Languages used are generally C and MACRO. Object files are provided for all C modules. All programs are fully commented and complete. [.DRIVERS] A totally re-written version of the pseudo terminal drivers for V5. Many bug fixes and efficiency enhancements. Now includes DIRECT I/O support, and hooks for new features. See the AAAREADME file for a full description of what was done and why. [.H] Automatic way of generating all possible VAX C header files (eg. PCBDEF.H) from the VMS supplied MACRO libraries. Extremely useful - just re-run when a new release of VMS is issued to generate a new STARLET.TLB and LIB.TLB. [.LASER] Complete VMS symbiont and forms library for driving an HP LaserJet+ as an ordinary VMS print queue. [.MACRO] Lots of KERNEL and USER mode code for doing almost everything to someone else (or yourself). eg. create a process dump/traceback under program control, set process name, set DCL prompt, deallocate a device owned by someone else, change UIC, etc. The utilities for creating a process dump (or traceback) from another process (without effecting the running process) are VERY useful if you write detached servers etc. I believe there is no other tool for doing this. [.MAIL_PROTO] Complete MAIL alternate protocol routines as stubs for user Page 2 modification. Run it and see. Makes writing your own protocol module for VMS mail much more simple. Also includes a fully documented MAIL.COM (DCL implementation of MAIL-11 V3) and PHONE.COM that uses the PHONE protocol. [.NETOBJ] Example multi-threaded DECnet symbiont that demonstrates a full non-transparent task-to-task DECnet object. Runs as a detached process. User utility for talking to it also supplied. Generally, it can be used as a framework for building your own flavour of network server. This is now superceded by the DEC SYS$EXAMPLES:DB_xxx code. [.PDINIT] Utility to manipulate the VMS pseudo disk driver. Simple to use, comprehensive and effective. I know there are loads of these, but this is my offering! [.SHOW] Example programs that talk to NETACP directly to obtain a SHOW NET listing. Uses the undocumented QIO interface to NETACP, not NML. Oh, all right...I've included an example program that uses the NICE protocol via NMLSHR. This is the correct way to talk to DECnet for network management, but the documentation is really hard to come by. Note that under PhaseV DECnet, NICE will not be used. [.SP] Powerful utility for controlling privilege use for an individual user. Very flexible. We have used it for years (the coding style reflects that!). [.SYMBIONT] Example C VMS server symbiont that implements a simple REMIND utility. Quite fun and totally open to abuse! Complete with VMS HELP files and CLI utility. [.TOOLS] Some tools. Things of note are some command files to look at the UAF to see if it has been attacked by hackers; a routine to disable the CTRL/Y AST trap in DCL (see code for reasons); a PATCH file for MONITOR to enable concealed classes; and a command file that sorts your QUOTA.SYS file into alphabetical order (safely! - using DISKQUOTA) to aid disk maintenance. [.TPU] Complete V5.x version of the EDT initialiser, plus a few extras. Brings up EVE (quickly) looking just like good-ol' EDT, complete with Page 3 keypad. Many extra features, such as SPAWNing processes, including the output from DCL commands in buffers, a very nice way of selecting buffers, and all of EVE there too if you want it, including multiple windows and fully integrated help. Look at the start of ATG_EVE.TPU for a complete description. This module is constructed as a "Real EVE Product", and is layered on EVE and built with EVE$BUILD as per all VMS V5 requirements. It therefore should be compatable with all future versions of EVE/TPU. Fully commented and easy to extend. All our editing is done with this TPU section. [.UWD] Template User Written Debugger for VMS. From an idea in (I think) VAX Pro, but totally re-written to fix many bugs, ommissions and heavy duty over-coding. [.XE] MONITOR like utility that displays Ethernet Line Counters via an undocumented $QIO interface to the Ethernet 802 drivers. Very useful for looking at the results of flood testing or general analysis of Ethernet activity. Runs on any VAX with one or more (DEC) Ethernet interfaces. Why is there so little UIS/DECwindows software in the public domain? Coming soon... UIS tools for font generation/manipulation (conforming to DEC Common Font File Format), UIS and DECwindows terminal emulators, and any other tools for windows that I can prepare by the next tape. [end] ========> [VAX89A1.BRAMHALL]AAAREADME.TXT;1 <======== FAKE_VM - Special VM and EFN handling. FAKE_VM intercepts memory and event flag allocation routines and permits various debug and control options to help control or monitor the actions of these routines. FAKE_VM intercepts the following routines in LIBRTL: LIB$GET_VM The general get VM routine. [FAKE_VM does *not* handle zones!] LIB$FREE_VM The general free VM routine. [FAKE_VM does *not* handle zones!] LIB$SGET1_DD The get dynamic string routine. LIB$SFREE1_DD The free one dynamic string routine. LIB$SFREEN_DD The free n dynamic strings routine. LIB$GET_EF The general get EFN routine. LIB$FREE_EF The general free EFN routine. And, as of VMS V5.2, the following: LIB$VM_MALLOC The memory allocate routine. LIB$VM_CALLOC The cleared memory allocate routine. LIB$VM_REALLOC The memory reallocate routine. LIB$VM_FREE The memory free routine. FAKE_VM intercepts the following routines in VAXCRTL[G] provided that the VAXCRTL[G] shareable image was included when the image containing FAKE_VM was linked: MALLOC The memory allocate routine. CALLOC The cleared memory allocate routine. REALLOC The memory reallocate routine. FREE The memory free routine. CFREE The memory free routine. VAXC$MALLOC_OPT The optimized memory allocate routine. VAXC$CALLOC_OPT The optimized cleared memory allocate routine. VAXC$REALLOC_OPT The optimized memory reallocate routine. VAXC$FREE_OPT The optimized memory free routine. Page 2 VAXC$CFREE_OPT The optimized memory free routine. FAKE_VM intercepts the following routines in DECW$XLIBSHR provided that the DECW$XLIBSHR shareable image was included when the image containing FAKE_VM was linked: XMEMORY_MALLOC The memory allocate routine. XMEMORY_CALLOC The cleared memory allocate routine. XMEMORY_REALLOC The memory reallocate routine. XMEMORY_FREE The memory free routine. Submitted by Mark Barmhall, DEC. ========> [VAX89A1.CVLUG]AAAREADME.TXT;1 <======== [.CVLUG]AAAREADME.TXT @@@ @ @ @ @ @ @@@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @@@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @@@ @ @@@@@ @@@ @@@ DECUS Connecticut Valley Local Users Group P. O. Box 251, Glastonbury, CT 06033-0251 Each directory in this collection contains a AAAREADME.DOC file with specific information about the use of the programs there. [.BANNER.GOTH] A banner program with a Gothic character set 9 inch letters. [.BANNER.SERIF] A banner program with a Serifed character set 9 inch letters. [.CREDIRSYM] A foreign command which creates symbols and logicals for the primary sub-directories of the current default directory. (FORTRAN, MACRO) ** [.CAL] A native command which generates monthly or yearly calendar to the screen. (BASIC supports /OUTPUT). [.CALENDAR] A program which generate 12 month calendars 1 month per page with optional monthly pictures included from (JAN.DAT, FEB.DAT etc...) (BASIC) [.CALLBACK] These files provide auto AUTO CALLBACK via/ DEC DF03 autocall modem. [.CTS] Console Time Stamp, an image which runs detached, sending a one-line date-time stamp to the console device ever half hour. (FORTRAN,MACRO) [.DELTREE] A native command which performs a directory tree delete. (BASIC, MACRO) [.DTREE] A native command which generates graphical representation of a directory structure. (BASIC, /OUTPUT) ** [.ESCDEMO] A collection of similar programs coded in several languages (BASIC,COBOL,C,DCL,FORTRAN,PASCAL) which demonstrate terminal and disk i/o, and VT100 escape sequences. [.FUN.POSTERS] A few amusing images which are better appreciated on a printer. [.FUN.VT100] A couple of animated routines for you character cell terminal viewing pleasure. [.FUN.VT330] A little fun with monochrome ReGIS graphics. [.HELP] VMS Help files for VT100 escape sequences and RUNOFF commands. [.PEDIT] An EDT command file to redefine the default key configuration of the PROCOMM VT100 emulator, to a more conventional orientation. [.THOUGHTS] A foreign command to intended to provide a little moral boost at login by providing a thought for the day. Also included is BASIC utility which generates THOUGHTS.FOR from the THOUGHTS.TXT file. [.TOOLS] DCL procedure which defines numerous command abbreviations (symbols) for routine data processing, Runoff, LaTeX, BASIC, COBOL, RPG, MACRO, FORTRAN, Spell, TYCHO. This procedure is very popular among newer user who are not adept typists, and seasoned user who simply prefer Page 2 the convenience. [.USERCOUNT] A native command which counts the number of interactive users logged in with the same username as the executing process, useful in both login and logout procedures. [.UNQUE] A native command which deletes entries from batch or print queues by job name. (FORTRAN) [.UNTAB] A foreign command which will replace tab characters with the appropriate number of spaces to preserve the appearance of the file. ** When CREDIRSYM and DTREE are defined as keys they make navigation through directory systems (like SIG tapes) a most excellent adventure. Bob McDougall Hartford State Technical College Hartford, Connecticut May, 1989 ========> [VAX89A1.DOWN]AAAREADME.TXT;1 <======== DOWN Utility BRIEF DESCRIPTION OF THE UTILITY ================================ The DOWN utility provides an easy means to "move around" in your directory tree. This utility allows you to move deeper in your directory tree or up through your directory tree or even to change the directory tree you are in even if it exists on another device. You do not have to specify a path name as you would have to use with the SET DEFAULT command. All that is needed is the file name portion of the directory that you wish to make your default. This utility will find a directory that matches that specification regardless of where that directory is located in your directory tree. INTENDED USE ============ To be used as an aid to or a replacement for the DCL SET DEFAULT command. This program uses 100% VMS normal syntax but also allows for abbreviated syntax (including wildcards). This utility can be used like the set default command (i.e. specifying the desired directory on the command line). If you do not specify a directory it will list all of your directories and allow you to choose one by moving the cursor to it or by specifying it by its number as indicated on the screen. This utility IS device independant. Written in VAX BASIC V3 Comments are welcome: Send any questions, comments, enhancements, bug reports and wish lists to: Michael W. Wheeler ( Bitnet address: mww@tntech.bitnet ) Systems Programmer Tennessee Technological University Box 5071 Cookeville, TN 38505 (615) 372-3977 ========> [VAX89A1.DTRSIG]AAAREADME.TXT;1 <======== This is a combined effort by the DATATRIEVE / Fourth Generation Languages SIG to produce a library of items related to or using DATATRIEVE or RALLY. (** indicates new material for Spring 1989) [.ACCOUNTING] Programs to convert System Accounting and PSI Accounting data to a normalized form readable by Datatrieve (and other languages) with record definitions. Also has a procedure to measure terminal useage (an Erlang traffic study on terminal sessions). [.ALLIN1] Contains DTR definitions to work AI1 logging and data files. The document database also works with WPS-PLUS/VMS. (Note: this is ALL-IN-1 V2.0 through 2.2) [.CORPHONE] DTR replacement for the AI1 corporate phone directory, which also works quite well on it's own. [.FUNCTIONS] Many user defined functions including many string functions, Datatrieve procedures for cataloging, defining, and generating functions. ** I have "folded in" some functions from Don Stern which used to be in a separate file, including FN$DELETE_LOGICAL, FN$SET_LOGICAL, FN$SET_SYMBOL, FN$DELETE_FILE, FN$WAIT, and FN$EDT. I have also included FN$TRIM_FILESPEC and FN$SOUNDEX, String and Bitwise logical functions, VMS utilities CONVERT/RECLAIM and FDL$CREATE. [.MAGIC] Some procecdures from Wombat Magic sessions which didn't fit anywhere else. Build an FMS form from a record definition, and calculate mortgages. [.NEWSLETTERS] Past issues of the Wombat Examiner Newsletter. [.PLOTS] Additional PLOTS and articles on adding your own plots. A new family of compass and vector plots (and an analog clock face plot). [.RALLY] ** For the first time, some RALLY examples. [.DATE_FORMATTING] shows how to accommodate a wide variety of date formats as input to Rally. [.EXTERNAL_LINK] shows how to link to system Run Time Library routines LIB$GETJPI and LIB$SPAWN. [.RECALL] Use SMG to give you command line recall while using DTR. Plus DAB definitions in "C", Macro-32. ** The Macro-32 and "C" DAB definitions have been updated for DTR 4.2 [.RSX_ACCOUNTING] Process RSX-11M-Plus system accounting with DTR, also RSX console logs, and a routine for all 11s to convert the DTR (and VMS) DATE types to/from ASCII (without DTR). [.SESSIONS] Transcriptions of some Symposia sessions. Page 2 [.SYSMGR] Datatrieve definitions for Disk Quotas, SYSUAF, rightslist, network proxy logins, etc. Plus a method of processing an INSTALL/LIST/FULL listing to find out which are the most used images, shared images, etc. Procedures to record the login history of users on a system, and terminal/line usage. (Also a FORTRAN program to do this if you don't have DTR). B. Z. Lederman DTR/4GL SIG Library Representative ========> [VAX89A1.FLEMING]AAAREADME.TXT;1 <======== EVEplus+ Version 2.0.1/VMS version 5.1 -------------------------------------- EVEplus+ is a 4-tier multi-layer keypad editing interface,with the top two layers resembling EDT. The starting point for this editing interface under TPU 1.0/VMS version 4.X was the EVEplus procedures made available by DEC on the Spring 86 DECUS tapes. Many of these procedures were mapped to the bottom two layers, and enhanced. Principal Programmer: Glenn Fleming GE Microelectronics Center Mailstop 7T3-01 P.O. Box 13049 RTP, NC 27709 Phone : (919) 549-3743 Bitnet address: fleming@rtpark.rtp.ge.com Contributing Programmers: Bob Boyd, John Watters (Same address above). ========> [VAX89A1.GCE]AAAREADME.TXT;2 <======== Glenn Everhart / G.E. Aerospace The following subdirectories are present; the contents include materials as documented below. Browse other AAAREADME.* files too, please, for further information. The network material is unindexed but has VERY long filenames to make it easier to find things. [.ANALYBIG] AnalytiCalc spreadsheet (src, obj, exe). AnalytiCalc used to have lots of 16-bit integer variables inside to allow efficient work on PDP11 or IBMPC. This version has mostly 32 bit variables (good for Amiga and VAX) and will let you define as egregiously large spread- sheets as you want. It runs faster than the version with i*2 variables too! Also a couple new cell address modes are added to make it easier to write address calculations in your macros for it, and the binary save/load mode is speeded up over the old text mode (which is still available for compatibility and transportability.) [.TARRDWRT] Local TAR read/write mods. Allows ANY sequential file to be written to TAR tape and allows partial squashing of too-deep Unix directory trees. [.VMSVD] Virtual disks for VMS!!! The old VDDRIVER is fixed so it handles all split I/O correctly and is cleaner. This driver makes a contiguous file on a VAX system local disk appear to be a totally independent volume, with high performance. Also, a new driver FDDRV is introduced. It provides: * Remote virtual disks over DECnet or asynch, so you can back up a disk over a network from a machine without a tape, EXACTLY as if the remote disk were a local device. (Note: Be sure your RMS network buffers are set to 17 or more, or edit the source to the remote disk host/server routines, before using the DECnet remote disks. They expect to be able to send 8300 byte DECnet $QIO's.) * Memory disks, using a PROCESS' address space. Thus the VMS paging algorithm determines what memory is actually in physical memory. No more eating your nonpaged pool alive! * File disks. Data stored on a file, which does NOT have to be contiguous. (This can be used even on the most fragmented disks!) Files can be on other DECnet nodes also, if this is desired. * Crypto disks. Data is stored in a file, as in the file disk, but is encrypted on write and decrypted on read. This gives a trivial way to have storage automatically used by existing Page 2 software in encrypted form, and is the simplest way to solve problems like wanting to have one's payroll file online, but secure against perusal by the systems people after hours (or even, with a few caveats, during the time the disk is in use). In spite of the fairly high strength of the encryption, the routines run rather quickly and impose no noticeable burden even on a 750. * Bat Out of Hell Disk. This is a combination memory/file disk, whimsically named. The idea is that it is functionally a file disk shadowed by a (process based) memory disk, so that all reads are from the memory disk while writes go to memory AND the file disk, providing safety in case of crashes. As in the "standard" file disk, the file does not HAVE to be on a local node. Since a normal VMS process does all the physical I/O for FDDRV, you can create your own flavors of remote disks with it...WITHOUT even having to write any kernel mode code! That's been done for you. [.NETS89] Giant cornucopia of messages with source code, hints and tips on keeping your system healthy and happy, gleaned from Internet sources. Includes a very interactive disassembler. Also Sid Penstone's latest TAR read/write utilities. Sources only in most cases. [.ADASIMSCRIPT] SIMSCRIPT - similar package written in Ada [.BROWSER] Browser/Indexer. Allows full text retrieval of data by one or MORE keywords, in definable neighborhoods, from ANY text file. Fast, too! Somewhat crufty but not too obscure user interface. Worth using! [.NETS89.MISCUTL] Browser src; VMS MSDOS diskette reader; B-Tree source code; PD sources for ARC. [.NETMAP] Old DECnet mapper utility. Worked for DECnet phase III (one area). Source. [.TARDR] TAR reader/writer code for VMS, locally modified. Glenn Everhart Everhart%Arisia.decnet@crd.ge.com Everhart@Arisia.ge.com 215 354 7610 voice GE Aerospace Technology Bldg 100 Room U3040 POB 8555 Phila., Pa. 19101 Page 3 Mail/ship address: use my home address please: Glenn Everhart 25 Sleigh Ride Rd. Glen Mills, Pa 19342 215 358 3866 ========> [VAX89A2.GAMES.FCD]AAAREADME.TXT;1 <======== FCD These are bigfixes for the Five Card Draw poker video game from the Fall 1988 VAX Sig tapes. ========> [VAX89A2.GHC]AAAREADME.TXT;1 <======== I have modified the source modules PROTOCOL.FOR and XMODEM.FOR, along with the include file PARAMS.INC of Robin Miller's VAXNET program (ver 12.1) to support the XMODEM-CRC protocol. When sending, CRC usage is automatic when it is noted that the receiver requests CRC. When receiving, an additional prompt is presented to the user after the RECEIVE command is issued; depending on the users response, VAXNET will expect CRC. The modification was done in a conservative manner: Rather than create an additional protocol name, I have modified the low level functions GET_XMODEM and SEND_XMODEM. I have also added the subroutine XMODEM_CRC which I have blatently lifted from the XMODEM_AU program of David Swanger. The modification of PROTOCOL.FOR and PARAMS.INC is to send the required CRC initial character. Why did I do it? I have encountered several BBS systems that don't seem to want to hear of XMODEM(CHECKSUM) and don't have any form of KERMIT. I am seriously considering a modification which would increase the maximum buffer size to 1024 from 128. On a PC, such a size increase seems to make a big difference. On the VAX, I'm not sure, but I may try anyway. ========> [VAX89A2.GUNTHER]AAAREADME.TXT;1 <======== /* DISCLAIMER: USE AT YOUR OWN RISK !!! ------------------------------------ THESE PROGRAMS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING,WITHOUT LIMITATION, EXPRESSED FITNESS FOR A PARTICULAR PURPOSE BETZ DOES NOT WARRENT THAT THE FUNCTIONS CONTAINED IN THE PROGRAMS WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE PROGRAMS WILL BE UNINTERRUPTED OR ERROR FREE. IN NO EVENT WILL BETZ BE LIABLE FOR ANY DAMAGES, INCLUDING, WITHOUT LIMITATION, INCIDENTAL OR CONSEQUENCIAL DAMAGES, AND DAMAGES FOR LOST DATA OR PROFITS, ARISING OUT OF THE USE OF OR INABILITY TO USE THESE PROGRAMS, EVEN IF BETZ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WRITTEN BY JOHN C. GUNTHER, 4/89 COPYRIGHT 1989 BETZ LABORATORIES, INC. ALL RIGHTS RESERVED. */ This disk contains two RS/1 procedures for producing trilinear contourplots, contained in two subdirectories: o \TERNARY Contains a procedure to produce trilinear contourplots as RS/1 CONTOURPLOT objects. o \TRILIN Contains a procedure to produce trilinear contourplots as RS/1 GRAPH objects. The first of these is newer and better than the last. However, the older procedure in the \TRILIN directory has the advantage of not requiring the RS/1 CONTOURPLOT option to work (if your site does not have the CONTOURPLOT option, you will have to use the older procedure) as well as not requiring a graphics terminal or plotter (it can produce usable output on a line printer.) See the individual README.TXT files in each of the above subdirectories for more information. ========> [VAX89A2.INFOVAX]AAAREADME.TXT;1 <======== I N F O - V A X C O L L E C T I O N At the Fall 88 Symposium I volunteered to keep an archive of useful goodies posted on INFO-VAX (an internet mailing list.) I've built everything but the things that have `include-type' files missing so those without the needed compilers won't miss out on anything. I intentionally omitted material I KNEW would be submitted by their authors (Meadows, Everhart, et al...) The comments below come mostly from the postings themselves. Rand P. Hall Director, Academic Computing Merrimack College 300 Turnpike St. N. Andover, MA 01845 [.boss] BOSS is an interactive job controller. It lets you run several interactive jobs simultaneously. [.cvtime] A time conversion command procedure. [.exec_batch] Someone recently posted a BATCH.COM command procedure which inputs commands interactively and submits it to a batch queue. I have a utility called EXECUTE, written in C, which does this. It's advantage is, of course, being an executable, it runs faster than a command procedure. It also has the following added features: If there is only one command to be executed, that command can be entered on the EXECUTE command. The prompting for input lines is done using SMG$ routines, so that line recall is possible. Specifying /EDIT invokes an editor for inputting the commands, rather than prompting line by line. The qualifier /QUEUE can be used to specify the batch queue. Lastly, there is a /NOBATCH qualifier, so that the commands are executed immediately. I find this useful for executing a series of commands without having to create a command procedure (or alternatively typing the commands ahead and hoping that I've spelled them properly.) [.hayes_dte] Here's a modification of Jake VanNoy modification to the examples DF03 driver. I changed it for a MT224 (Multitech) modem which i think is functionally equivalent to a Hayes. [.KEPT_SUBPRC] An implementation of subprocess caching. [.mail_alias] Joel Snyder brought up an interesting point regarding LNM$FILE_DEV usage for mail aliases. So, i decided that i would write the program he is Page 2 afraid to show (because of it's DCL grossness) and here it is... It uses a /usr/lib/aliases style configuration file referenced by MAIL_ALIASES (default SYS$LOGIN:.DAT) and keeps track of the file to reload it if it changes (either by name or revision) The Logicals are stored in an alternate table that is connected in /user mode in LNM$FILE_DEV prior to invoking the mail command. This also supports the command line interface to MAIL ($ Mail [file] [to]) The format for MAIL_ALIASES.DAT is [alias : equivalence ] [! comments] E.G. ! Mail Aliases File People: Manny,Moe,Jack ! 3 people Everyone: People, @other_guys, ! all the people here Over_There: REMNOD::Hey_You ! remote node person [.mt_bot] I believe batch is the best way to deal with running backup and recieving "next volume" mount requests, however, there is a way we have used back in the olden days (pre-VHS tape drives) which you might find handy. Its a program that is SPAWN/NOWAIT'd from whatever terminal you are using and it wakes up every 30 seconds and checks the mag tape device status watching for the MT$_BOT bit to pop up (which usually means the tape has been rewound and dismounted) causing it to send a bell code to the terminal. I didn't write it, but here it is if you want it. [.password_swap] This module is a companion to POP_PASSWORD. Its purpose is to extract the hashed (encrypted) password of a specified VMS username, save it in a file in SYS$MANAGER:username.PUSHED, and insert a new, known hashed password using AUTHORIZE. POP_PASSWORD reverses the process. [.pgflquo_sizer] [Someone] had asked me about some method to help in determining what PGFLQUOTA would be needed to run programs being created on his system. He kept bumping into the quota problem as simple program(s) were 'enhanced' into complex programs then into HUGE programs. To this end, I have enclosed a command procedure which will examine the .EXE file for the amount of page file usage which MIGHT be used. The comment [.poke_boottime] Here is a SHELL archive containing a program to allow anyone with CMKRNL privilege to POKE the system BOOTTIME. This address in system, space (EXE$GQ_BOOTTIME) can sometimes be wrong. This causes programs that use the SYS$GETSYI item SYI$_BOOTTIME or the lexical function F$GETSYI item BOOTTIME) to be wrong. Page 3 The program will ask for a standard VMS time, convert it to binary time and call a kernal mode routine to poke the cell in system space. This program also serves as a nice template for writing other system space poking routines. [.profiler] A poorman's PCA. [.ptype] Command file to aid in typing files on remote printers (DEC compat. terms.) [.setportname] Here's a little [Ed. neat] toy I wrote yesterday which lets a suitably privileged (CMKRNL) user manipulate the Access Port Name (DVI$_TT_ACCPORNAM) field for terminal devices, e.g. [.setuser] This program allows a privileged user (CMKRNL, PSWAPM, privs plus read access to sysuaf) to change his username. It also changes the users Account name, UIC, Process name, and Default Directory to that of the specified user. [.showdef] Here is a program to find the default directory specification for any process (i.e., SHOW DEFAULT/ID=pid). [.showdev] ShowDev - A command file to show all information about a device. [.smp_photo] Photo with SMP support. For those of you who don't know about PHOTO, PHOTO copies all of the Input/Output (IO) that appears on the terminal to a file. It is useful for turning in homework assignments, which do most of their IO to the terminal. [.strip] options: -f remove embedded carriage returns and linefeeds like and when using EDT. (default option) -t remove trailing spaces -l remove leading spaces -a convert to 7 bit ascii Page 4 -u convert to uppercase -d convert to lowercase -e[#] expand tabs to # spaces (default is 7 spaces) -c[#] convert # contigious spaces to a tab (default is 7 spaces) -k[#] Insert a newline every # (def is 80) characters. -m[#] Truncate every line after # (80) characters. [.uaf_profile] PROFILE is a FORTRAN utility which adds new accounts or modifies existing accounts by using a screen-oriented interface that allows changes to be made by moving the cursor to the desired field and entering the changes. [.undel] Undelete a file on a FILES-11 disk Handles disks with any cluster size, and files with any number of extension headers. Use with caution only when you REALLY need it; a backup copy is always preferable if you have one. If the file is really vital, back the disk up before using UNDEL on it. [.vms_share] Packages a series of files into a format suitable for transmission over electronic mail networks which may mangle the text. [.what] A FAST Cluster and network-wide SHOW USERS (and Much more) type command. [.zoo] Zoo is used to create and maintain collections of files in compressed form. It uses a Lempel-Ziv compression algorithm that gives space savings in the range of 20% to 80% depending on the type of file data. Zoo can store and selectively extract multiple generations of the same file. ========> [VAX89A2.IVANOV]AAAREADME.TXT;1 <======== [.IVANOV] This is the base directory for the Grass Valley Group software contributions to the VAX SIG 1989 (spring) symposium. Included here is UN*X compatible MAKE for VMS, System V "termio" (partial implementation) for VMS (otherwise known as VAXCIO), Object lib- rary for BSD 4.2 Curses for VMS. Product: VAXCIO/CURSES (BSD4.2)/MAKE Descr: The VAXCIO package implements terminal I/O processing based on System 5 "termio". It includes raw(), cbreak(), echo(), etc. The curses package is a direct port of BSD 4.2 curses to VMS. MAKE (Unix style) is also included. Op Sys: VMS 4.x (maybe 5.x) Author: Tony Ivanov Grass Valley Group Keywords: VAXCIO,curses,termio,cbreak,make,unix,tools Files here: $$$DISCLAIMER. - Company disclaimer. READ IT! $$$README. - Description of what's in this directory. $$$README.ALL - Copy of all the $$$README. files from each of the sub- directories. CURSES.DIR - Directory of stuff dealing with BSD 4.2 Curses. LIBRARY.DIR - Copy of what is currently in *my* SYS$LIBRARY: directory. MAKE.DIR - Diretory of stuff dealing with PD MAKE. MISC.DIR - BIN2ASC, ASC2BIN and source of same, sample option file to link in shareable C RTL (don't use this with curses or vaxcio!). VAXCIO.DIR - Directory of stuff dealing with VAXCIO (System V "termio" for VMS). Source code is included here. ========> [VAX89A2.JSCLUG]AAAREADME.TXT;1 <======== THREE ENVIRONMENTS HAVE BEEN PROVIDED. ALL 3 ENVIRONMENTS ARE CURRENTLY RUNNING UNDER VMS 4.7, AND HAVE NOT BEEN TESTED AGAINST ANY VMS 5.X OPERATING SYSTEM. LABSTAR: AN ILLUSTRATION AND PRATICAL APPLICATION OF THE LABSTAR PROGRAMMING INTERFACE. AN ATTEMPT TO DO WHAT DEC SHOULD HAVE DONE IN PROVIDING A USER FRIENDLY CALLABLE ENVIRONMENT. AT LEAST IT IS A START. TELEMAIL: THIS WILL BE THE LAST UPDATE OF THIS SERIES OF ROUTINES. I HAVE NOT DONE ANY MAJOR MODIFICATIONS, HOWEVER I HAVE FIXED A FEW BUGS THAT HAVE CROPPED UP OVER THE LAST 1-1/2 YEARS SINCE I LAST PUBLISHED THIS SOFTWARE. I SHOULD NOTE THAT THERE IS STILL A KNOWN BUG IN THE TELEBULB ROUTINES (TELEMAIL BULLETIN BOARD READ PROGRAM). IT INVOLVLES THE FACT THAT IF A BULLETIN BOARD IS DELETED FROM THE TELEMAIL SYSTEM, THEN THE PROGRAM WILL THEN READ THE USERS MAIL INSTEAD OF ABORTING. I DON'T INTEND TO FIX THIS. ALSO, LONG BULLETINS TEND TO CAUSE PROBLEMS AND NOT ALL BULLETINS ARE READ WHEN THIS 2ND SITUATION ARISES. LIFENET: THIS IS A PROJECT WHICH I PROVIDED SOME PROGRAMS FROM LAST YEAR (MAY 88). THERE IS A MUCH IMPROVED MAIL PROGRAM INTERFACE. A SHARABLE EXECUTABLE WHICH PROVIDES A CALLABLE INTERFACE FOR VMS 4.X MAIL. (READ ONLY, BUT BETTER THAN DEC PROVIDED!) A CALENDAR OF EVENTS PROGRAM. AND A PROGRAM FOR ALLOWING USERS TO MOVE FILES BETWEEN THEMSELVES WITHOUT NEEDING WORLD WRITE PRIVILEGE IN THE DESTINATION DIRECTORY. I HOPE THAT THESE ROUTINES ARE OF USE TO SOMEONE OUT THERE. CERTAINLY THEY SHOULD AT LEAST PROVIDE IDEAS OF WHAT THE VMS SYSTEM IS CAPABLE OF PERFORMING, AND MAYBE VISIONS OF THE FUTURE POSSIBILITIES. AS A SYSTEM MANAGER, I AM FAIRLY IMPRESSED WITH THE SIMPLICITY OF THE MAIL CALLABLE INTERFACE PROVIDED, AND BEGIN TO WONDER WHY DEC NEVER PROVIDED SUCH AN ALGORITHM THEMSELVES. THINK OF THE POSSIBILITIES OF AUTOMATIC MANAGEMENT ROUTINES BASED UPON MAIL INTERFACES. BILL BAKER NASA/JSC NASA/SD BUILDING 37 HOUSTON, TEXAS 77058 Page 2 PHONE: 713-483-7273 ========> [VAX89A2.KUNZE]AAAREADME.TXT;1 <======== NOTES ON THE VAX READER PUNCH SYSTEM Included on the tape are three different programs for punching cards. RP_CARDPUNCH.COM reads a record from the input file and "writes" it to the reader/punch port. At the end of each record both a carriage return (CR) and a line feed (LF) are sent to the port. RP_CARDPUNCH_QUEUE.COM very simply treats the reader/punch as a printer and uses the system print command to "print" the input file at a queue (which must be previously initialized by the system manager) associated with the reader/punch port. Each record will have a CR and a LF at the end. It is possible that in some cases (depending on the input file type) additional LF's could be sent. These programs have the advantages of being simple, fast (especially the queue version), and easily modified since they are written in DCL. Also included is the executable image file, RP_PUNCH.EXE. This is a fairly simple program which sends records to the reader/punch port with only a CR at the end. It is almost certainly much faster than the punch, and will introduce much less overhead on the VAX. It is intended to do nothing more than pump the input records unmodified to the reader/punch. The VAX MACRO source code is included as sample code and in case some customizing is required. RP_MENU is based on a generic menu system which I intend to submit to the DECUS public domain library. The executable portion of this system is a "black box" which displays menu options defined in a menu definition file. RP_MENU.MDF is a text file which can be easily modified to change the appearance of the menu and the options it displays. The executable gets the user's choice and executes it based on the commands defined in the menu definition file. The simplest way to use the RP_ system is to execute the VMS command $ @RP_MENU This starts up the menu from which all functions can be performed. RP_CARDPUNCH will be executed to punch cards. More information on using and modifying RP_MENU is included in RP_MENU.DOC. Page 2 Following is a list of alternative commands and their functions: @RP_CARDREADER Reads cards from port @RP_SET_FILE_NAME Defines file name logical (gets user input) @RP_SET_DEFAULT_VALUES Defines logicals used in system (gets user input) @RP_CARDPUNCH.COM Reads records, punches cards (might require firmware change) @RP_CARDPUNCH_QUEUE.COM Efficient way to punch (might require firmware change) RUN RP_PUNCH Reads records, punches cards (executable image, MACRO source included) RUN RP_MENU Not recommended. Use @RP_MENU ========> [VAX89A2.KVC]AAAREADME.TXT;2 <======== [.PTY] These files make up a pseudo terminal driver for VAX/VMS. This driver was originally developed at Carnegie-Mellon University and has made the rounds before as the CMU PTY driver. I picked up the driver just after it had been migrated from V3 to V4, made a lot of improvements, and have been redistributing it ever since. This driver runs under VMS V4 and V5. It will not work under any VMS prior to V4. It has been minimally tested by me on V4.7 and V5.0. It should work on earlier V4 point releases as well, but I haven't tried it. Note that during assembly the driver will detect the version of VMS and build the proper variant. You do not need to modify the sources for V4 of V5. See PTY_DOC.TXT for documentation and NOTES.TXT for my additional comments and observations. Changes for version 05-011A (PYDRIVER) and 05-004A (TWDRIVER) include: o The bug causing the driver to sometimes hang on CTRL/S has been fixed. o A bug causing the driver to incorrectly check for XOFF has been fixed. o A bug causing writes of (32 * N) + 1 bytes to fail has been fixed. o Support has been added to immediately return echoed data on writes to the PY device. This can save substantial amounts of overhead in some situations by avoiding an extra output read. See the example program ECHO_TEST.C. o Support for VMS V5 including Symmetric Multiprocessing environments. Conditional assembly of the drivers will produce V4 or V5 compatible drivers. o The port control MULTISESSION bit is now set by the driver, causing terminal sessions on TW devices to NOT count against your license limit. This is good for programs like PHOTO, but not so good for network logins. This really should be made settable by the application controlling the PY device. o Writes to the PY device will now return SS$_DATAOVERUN if the TW signals XOFF. o There is now a SETMODE and SETCHAR function that allows you to enable three new ASTs. It does not take any function modifiers and only sets the specified ASTs. o The TW device now defaults to HOSTSYNC. o The PY device now accepts a SENSEMODE and SENSECHAR QIO function to read the device characteristics of the TW terminal device. o Modification to slave terminal device ownership to function correctly after "Security Upgrade V2" has been applied to a Page 2 VMS V4 system. The security upgrade is incorporated into V5. o The PY device now supports writes of buffers greater than 64K. Note that use of such large buffers probably requires that you monitor the flow control ASTs. o The terminal device name has been changed from TPAn: to TWAn: because the VAX PSI product now uses TP. PY and TW are the names of choice now since they have been registered within Digital by a development group. These drivers should be compatible with the DECwindows PY and TW drivers since they derive from the same code. There may, however, be differences that cause DECwindows to not function. I do not know. I would suggest using the DEC supplied DECwindows versions of the drivers if you have it installed. [.DECWINDOWS] Well, now that V5.1 and DECwindows is out lets get some VMS DECwindows related goodies onto this list! To start things rolling, here's a little hack to allow non workstation hosts, generally large, multiuser VAXen, to create a DECwindows (DW from now on, my fingers are tired of that!) LOGINOUT screen on a workstation running just the server. When DW starts up it determines if it is running on a workstation or not. If not, it simply does the things that need to be done on a client-only machine, not much, and exits. On a workstation it goes on to start the server and then create a DW LOGINOUT process which throws up the wonderful "|D|i|g|i|t|a|l|" logo and the "Username/Password" dialog box. /Kevin Carosso kvc@friday.a-t.com Innosoft International Inc. kvc@ymir.bitnet April 21, 1989 ========> [VAX89A2.LBGS89]AAAREADME.TXT;1 <======== This is the main directory for the Spring 1989 GE Lighting SIG tape submission. This "read me" file s a general description of what is in each directory. There are other "read me" files in each of the other directories. Comments and questions should be directed to: Eric Wentz GE Lighting Nela Park Noble Rd #1711.00 Cleveland, Ohio 44112 (216)266-2382 -------------------------------------------------------------------------------- BECOME.DIR;1 A revised version of BECOME with a few bug fixes and some new features. Updated for VMS V5. BLISSLIB.DIR;1 Contains some utilities for developing BLISS source code. If you don't write in BLISS, you probably couldn't care less about this directory. MISC.DIR;1 Here's a hodge podge of stuff that wouldn't fit elsewhere. Probable the best one in here is SHOQUOTA which will give you a real-time display of a process (similar to SHO PROC/CONT) but with all the process quotas and limits displayed as well. All the priv'd code has been updated for VMS V5. -------------------------------------------------------------------------------- ========> [VAX89A2.LILUG]AAAREADME.TXT;4 <======== [.LILUG] This subdirectory contains routines from the Long Island Local Users' Group. [.LILUG.ABT] This directory contains an assembler routine for RSX-11M/M+ that retrieves a radix-50 list of active tasks associated with the invoking terminal and a program that aborts them all. The list excludes cli's. Submitted by Mitch Nelson of Brookhaven National Laboratory. [.LILUG.CLOSEUP] Here are two command procedures for protecting a networked vax from attacks directed at the default decnet account. The procedures were written for easy readability and modification. Submitted by Mitch Nelson of Brookhaven National Laboratory. [.LILUG.HAHN] This directory contains two routines from Pierre Hahn of SUNY at Stony Brook. 28-DAY.COM analyzes the accounting for the past 28 days. TERM.COM collects the data from SHOW USER and stores a pictorial representation of it, indicating which lines are in use. ========> [VAX89A2.MCWMIS]AAAREADME.TXT;1 <======== Spring 1989 VAX SIG TAPE SUBMISSION [Update: formerly VAX-380] [see text at bottom of this file] Kent C. Brodie MIS Department Medical College of Wisconsin 8701 Watertown Plank Road Milwaukee, Wisconsin. 53226 Phone: (414) 257-8769 (414) 778-4561 BITNET: 7113BROD@MUCSD KEYWORDS for this submission: LASER, HP, LASERJET, PRINTER, FORM, QUEUE SYSTEM MANAGER UTILITIES This directory contains the command procedure and support files needed to easily support a Hewlett Packard HP-2000 laser printer on a VAX. You can use these files to support other laser printers as well, but some modules may have to be changed (Laserjet, Laserjet+ escape sequences are different in some areas). In any case, I hope this is a good example on how to manage a laser printer and its many available attributes. Additionally, this directory contains a few handy DCL utilities for system managers, including both a MANUAL and AUTOMATIC idle process killer. (what submission would be complete without them?) Please note that this submission contains the files necessary to use the "/FORM=xxxxx" qualifier when sending standard print files to the HP2000. This allows you to print regular "standard" files in a variety of fonts/styles, without having to use special text-formatting programs, such as RUNOFF, etc. The files are as follows: [.HP2000] HPFORMS.COM A command procedure that sets up some of the "stock" forms for a HP-2000 printer. Form names/numbers may have to be modified so they do no clash with definitions already present at your site. The procedure is fully commented. Sample form names are "PRESTIGE1" or "COURIER2". [.HP2000] REMOTEPRT.COM A sample command procedure that shows how we set up our print queue for the laser printer. Our site has a 2-node clustered system, with the printer port residing on a DECserver. This isn't really an official part of this submission - it is included only for completeness. [.HP2000] SYSDEVCTL.TLB A device-control text library of various tiny modules that control the HP-2000 printer. (Portrait vs. Landscape, 6 LPI vs. 8 LPI, etc). HPFORMS.COM uses various combinations Page 2 of the device modules to totally define the form of choice. If you are already heavily using SYSDEVCTL.TLB, you may wish to rename this file. This file should belong in the directory SYS$LIBRARY. [.HP2000] [.MODULES] This directory contains all of the text modules that comprise the file SYSDEVCTL.TLB. You may wish to keep these so that you can modify them (for another printer perhaps), or add to them and thus have the entire source in case SYSDEVCTL.TLB gets trashed. [.HP2000] BARCODE_EXAMPLE.TXT A sample text file that uses the "W" font cartridge that we happen to have installed on our printer. The example is right out of the book that came with the cartridge. If you would ever get that cartridge, this would be a nice sample to have. Notes: HPFORMS.COM does NOT contain all of the possible forms that you can define. For example, Prestige Elite Italic is not defined because we have no use for it. It is simple enough to use however, all you do is look at how HPFORMS.COM extracts the necessary modules to compile the form. In this example, you would use one of the forms set up for PRESTIGE, and substitute the STY_ITALIC module for the STY_UPRIGHT one. ==================================================================== Update: 5/1/89 Formerly VAX-380. This is all of the old stuff, plus: The newest "form" for the HP2000 that has been included is the "shaded" greenbar (form name: GREEN1). If you've modified a previous copy of HPFORMS.COM, all you gotta di is extract the bottom-most portion of the new file, and include it in yours. Nothing else has been changed. Also, I've included the following as a bonus (why not?): KILL.COM A **MANUAL** idle interactive process killer. (how's THAT for a switch?). This is an extremely handy and quick utility that shows you each user, and asks if you want to knock that process off of the system. (you also get to see GETJPI info, such as username, PID, and IMAGE). The nicest part of this deal is that all "kills" are logged into (appended to) a text file, so that you have a record of who has to be knocked off a lot.... JKILLER.COM Slightly modified JKILLER.COM (from "ARIS") that can run under a cluster environment that shares disks. DIALUP.COM Tiny dcl that shows you all of the interactive DIALUP users that are on the system. ("are all of my modems in use?"). Note: All three of these DCL files refer to a logical name called Page 3 "MCW$SYS", which is our common utilities directory. You can create your own assignment for MCW$SYS, or simply change it to your own site's naming conventions. ========> [VAX89A2.MINT]AAAREADME.TXT;3 <======== ELECTRONIC MAIL AT WESLEYAN An MM type mail interface which is somewhat similar to DEC20 mail but runs on VAX. 1. OVERVIEW MINT (Mail INTerface) is the new electronic mail program used on VAX systems at Wesleyan. MINT was written at Wesleyan and is still under development. (Please send suggestions and problem reports to Joseph Deck, Wesleyan Computing Center, or via MINT TO: JDECK@EAGLE.) A second mail program, MM remains in use on the administrative DEC-20, but will soon be replaced by MINT on VAX systems. Using MINT, members of the Wesleyan community with VAX computing accounts can send and receive messages between users at Wesleyan and hundreds of sites around the world. This guide, intended for both new and experienced VAX users, is organized into five sections: - A typical MINT session: This section will give you an idea of what your computing interaction will be when you use MINT to read and send messages. Browse through it quickly initially. You may wish to return to this section when you are ready to try the MINT program for the first time. - Basic Concepts: This section explains several concepts basic to using MINT. The structure of the MINT program, and addressing and referencing messages are among the topics covered. - Getting Started with MINT: This section explains the MINT commands needed by most users to use the MINT program. Topics include: getting help, listing, reading and sending messages. - Expanding your capabilities: This section includes topics that will facilitate your use of MINT. For example, it discusses how to create a mailing list that includes abbreviations for addresses you use frequently. It will be most useful to people who use the mail system frequently, or who send/receive many messages. - Command Dictionary: The dictionary includes a brief explanation of MINT commands, options, and concepts. It is intended primarily as a reference; however, if you browse through it you may discover just the option for which you've been looking. MINT MANAGERS MANUAL Manual last modified on 4 May 1989 at 15:57 Page 2 by JDECK Source is MGR-MANUAL.MSS, 03100/1 Comments to Joseph Deck (JDeck@Eagle.Wesleyan.Edu) Note: To install MINT you must have previously installed PMDF. Read the section titled "MINT and PMDF" for more information on PMDF. A mail system requires a delivery agent as well as a user in- terface. MINT interfaces with PMDF which may be acquired from: The Clearinghouse for Academic Software, Computation Center, 104 Computer Science Building, Iowa State University, Ames, Iowa 50011: (515) 294-0323. The last time I checked it cost between $80 and $105 depending upon the distribution media. 2.1.2. Spelling Checker Mint invokes the spelling checker written by Mark Resmer at Vassar. The Spelling checker made publically available via DECUS library is installed separately from Mint. If you have a dif- ferent spelling checker Mint will be able to use it if it can be invoked with the command line "spell filename". 2.1.3. New Mail Notification The program CNTNEW can be put in the user's startup LOGIN.COM file or the system wide login command file SYSLOGIN.COM. This program counts the new (unread) messages. Mail is delivered via PMDF-DELIVER.EXE. If mail is delivered to a user while he/she is logged on a message is sent to his/her terminal. 2.2.2. Mailing Lists There are two types of mailing lists available with MINT. One is maintained by the user as a personal list; the other is main- tained by the system postmaster. Mint uses an indexed form of the mailing lists. The program MLIST.EXE is used to create the indexed form. The system mailing list text and index files must be located in the directory pointed to by the logical name SYS$MINT. An example of a system mailing list is supplied in the distribution. Use that as a template for your MAILING-LIST.TXT file. ========> [VAX89A2.MONLATV]AAAREADME.TXT;1 <======== MONLATV.DIR This directory contains three programs submitted by DEC to monitor three different ethernet protocols: LAT, LAV, and HWA. Note: You cannot run MONLAT on system running LAT and you cannot run MONLAV on a machine in a LAVC. See the file MONLATV.DOC for instructions on how the programs work. ========> [VAX89A2.NIELAND]AAAREADME.TXT;1 <======== This following are the submissions for this time around: [.BULLETIN] Version 1.68 of Mark London's BULLETIN program. It has some nice new features and includes the material for a BULLETIN channel for the PMDF mail system. [.CHECKPASS] A program that will run a dictionary (supplied) through the accounts on your system to see if any of your users are using words from the dictionary as a password. The algorithm is based on the internet worm. A report on the internet worm is in WORM.MES. [.CRYPT] An encryption program that uses DES encryption, but outputs in HEX code, rather than binary, so the messages can be mailed. Messages can only be decrypted on like machines to implementation considerations (Floating POINT G/H, byte order). [.FINGER] A copy of FINGER for VMS for VMS 5.0 with the fix to TT_UCB.MAR (for single processor machines) to display the idle times and network locations. [.TAPES] A copy of a submission to the DECUS Library of Tape Utilties. [.TERMLOCK] A program that LOCKs a terminal and to unlock the terminal you need to type in the password(s) for the account logged in. You don't need to type in a password anymore. It also uses SMG to trap broaccast messages and display them in a set area. [.UUCODE] UUENCODE and UUDECODE for VMS. VMSINSTAL.HLP From the L&T SIG, A help file describing VMSINSTAL kits. ========> [VAX89A2.NSWC]AAAREADME.TXT;1 <======== This is the Spring 1989 DECUS VAX SIG Tape submission from Alan L. Zirkle Naval Surface Warfare Center Dahlgren, Virginia 22448 (703) 663-8023 The submission includes: -- NSWC RUNOFF, which is based on, and derived from, Bonner Lab Runoff (VAX version) from the VAX86C VAX SIG Tape. NSWC RUNOFF has been extensively updated since it was previously submitted in Spring 1988. The files for this are in subdirectory [.RNO]. See [.RNO]000README.1ST. NSWC RUNOFF (RNO) is an alternative to VMS RUNOFF (DSR). It has many capabilities not in DSR, including the ability to use macros and the means of easily using the features of whatever output devices are available (i.e. RNO understands escape sequences and uses them in a structured manner). -- MODIFY, yet another version of a program which goes through a wildcard list of files and changes one string to another. This one has more features than any I have seen; see the MODIFY.HLP file for a description of the features. -- REFORMAT, a utility to copy a file, changing its attributes in various ways. See the REFORMAT.HLP file to see what changes REFORMAT can make to a file. MODIFY and REFORMAT are FORTRAN programs. Each program has a .CLD file in which the "IMAGE" line must be edited with the path to the .EXE file. The .EXEs on this tape were compiled and linked under VMS 5.1. If you want to build MODIFY or REFORMAT from sources, you will need to link them with the library NSWC1LIB.OLB, which you must obtain from The Fall 1987 VAX SIG tape, in directory [VAX87C.NSWC.NSWC1LIB]. The sources to NSWC1LIB are also on that tape. I apologize for the inconvenience of this, but this will help keep this tape smaller. If you have any prob- lems, give me a call. ========> [VAX89A2.PAVLIN]AAAREADME.TXT;1 <======== Andy Pavlin's Collection DISM32 - A VERY powerful and complete disassembler for VAX executables. It knows most structures in VMS executables and will return them to you symbolically. It can disassemble drivers or system images as well as normal programs. ETHERMON - Monitor your ethernet, mostly symbolically. Even allows cuts, recording of selected traffic, etc. and knows ALL the protocols (almost) known to man on Ethernet! From Andy Pavlin, GE RSD ========> [VAX89A2.QMASTER]AAAREADME.TXT;1 <======== QMASTER Prerelease Version Rev. 04/28/89 QMASTER is an menu/SMG$ based application for manipulating jobs in print and batch queues. It is written in VAX BASIC and will currently run on the latter VMS 4.x systems as well as on V5 systems. The following operations can be performed on one or more entries at a time: 1. Release an entry. 2. Hold an entry. 3. Delete an entry. 4. Change the form type of an entry. 5. Change the queue priority of an entry. REQUIREMENTS and RECOMMENDATIONS: 20,000 block pagefile quota (to be fixed in a future release). VAX BASIC V3. DEC VT100 compatible terminal. DEC LK201 style keyboard recommended but not required. LIMITATIONS: 100 queues, 300 jobs per queue, 100 files per job. KNOWN BUGS: If there are more queue choices than will fit on the screen the menu will become confused and the program might terminate with an error status. Work around: specify the name of the queue on the command line. DISCLAIMER and COPYRIGHT NOTICE: Neither the author, Michael W. Wheeler, nor his employer, Tennessee Technological University, make any warrenty, either express or implied, with respect to this software. Copyright (c) 1988, 1989, Michael W. Wheeler. Permission is granted to make and distribute copies of this software, provided this disclaimer and copyright notice are preserved on all copies. The software may not, however, be sold or distributed for profit. AUTHOR: Michael W. Wheeler ( Bitnet address: mww@tntech ) Systems Support Specialist Tennessee Technological University Box 5071 Cookeville, TN 38505 (615) 372-3977 ========> [VAX89A2.RPI]AAAREADME.TXT;4 <======== DECUS VAX Systems SIG Tapecopy Submissions Rensselaer Polytechnic Institute Spring, 1989 submitted by: Matthew Madison Engineering Computing Services Rensselaer Polytechnic Institute Troy, New York 12180-3590 (518) 276-2606 madison@vms.ecs.rpi.edu (Internet) MADISON@RPIECS (BITNET) This submission contains eight subdirectories with items of possible interest to VMS system managers and users. All entries include source code, object code, executables, and documentation. Updates to previously submitted entries are noted. All entries, unless otherwise noted, are written BLISS-32 and include source in both BLISS and MACRO (as generated by the BLISS compiler). All include an AAAREADME.DOC file; some also include further documentation. Unless otherwise noted, programs were linked under VMS V5.x; most should run under VMS V4.x if re-linked. 1. [.CKALLOC] Contains two programs: CHECKALLOC compares disk quota allocations against space availble on disk and lists the users with the largest quotas. CHKUSE lists the usernames and disk quotas of users who have not logged in since a specific date. [new] 2. [.CLAIM] CLAIM is a program that allows a user to become the owner of files placed in his or her directories by other users. Linked under VMS V4.7. [update of Spring 1988 submission] 3. [.MDMLIB] MDMLIB is a set of utility routines called by some of the programs in this submission, and is required if rebuilding the programs from sources. [update of Spring 1988 submission] 4. [.MPMGR] MPMGR (MODPARAMS Manager) is a program that can build MODPARAMS.DAT files for an entire cluster from a central location. Linked under VMS V4.7. Written in PL/I. [same as Spring 1988 submission] 5. [.NSQUERY] NSQUERY is a utility that interrogates Internet domain name servers. Requires CMU-Tektronix TCP/IP V6.3 or later. [new] 6. [.SDFILTER] SDFILTER gives a system manager more control over the destination and page layout of VMS Workstation Software (VWS) screen dumps. Linked under VMS V4.7. [update of Spring 1988 submission] 7. [.SETUP] SETUP is a program through which a system manager can centralize the per-user, per-login setup of applications software on a system. Linked under VMS V4.7. [update of Spring 1988 submission] 8. [.WATCHER] WATCHER is an very flexible idle-job killer. The system manager specifies which terminals should be watched; and, on a per-terminal basis, which measurements should be used to determine that a process is idle and how long the job should remain idle before being logged out. One can also specify which jobs should not be monitored based on any combination of username, UIC, identifiers and privileges held, terminal, and day of week/hour of day. LAT terminals are identified by their server and port names. Written in PL/I. For VMS V5.0 or later only. [update of Spring 1988 submission] ========> [VAX89A2.SCHAFFRATH]AAAREADME.TXT;1 <======== [SCHAFFRATH]$README.TXT Greetings everyone! I have been using DECUS software for about three years now and finally decided it was time to squeeze my disk for various programs I have written and see what would fall out. The following section lists the various programs and .COM files that I have included. No executables have been provided due to the current 'computer virus' problems in the industry. If compiling is a problem, I will accept requests to provide the executables and/or object code on an individual basis. Most if not all of the programs use features of VMS V5.0 and up. Any questions or comments on this software may be directed to: Robert G. Schaffrath, System Manager General Foods Corporation 250 North Street / MS RA-5S White Plains, NY 10625-0001 (914) 335-9792 ************************ D I S C L A I M E R ******************** The following notice and disclaimer applies to all the software in my submission: Copyright © 1989 by Robert G. Schaffrath, Glen Head, New York All Rights Reserved This software has been furnished free of charge, and may be used and copied only with the inclusion of the above copyright notice. This software may be distributed or otherwise made available to any other person so long as there is no direct commercial profit derived from such distribution. No title to and ownership of this software is hereby transferred. The information in this software is subject to change without notice and should not be construed as a commitment by the copyright holder. This software is provided as-is and neither the author or his employers assume responsibilty for any damage or losses incurred through the use of this program. ***************************************************************** [SCHAFFRATH.COM] This directory contains a collection of various .COM files I have developed. Normally, I find DCL programming to be 'a hack' and would not consider including .COM files in a distribution. However, since others do it, why not me? So here are some (useless?) command procedures. BACKUPS.COM This procedure will display the backup status of all mounted disks. May or may Page 2 not require SYSPRV if the MFD is protected against read access. BATCH_CHECK.COM This procedure gives an example of checking for active batch jobs using the F$GETQUI lexical function. DEVCHAR.COM This procedure will display all known characteristics of a specified device. DSVBUILD.COM This procedure will reload the DECnet database with the load information for all DECservers that are defined in DSVCONFIG.DAT. PRINTER_CHECK.COM Similar to BATCH_CHECK.COM, this procedure will check for active print jobs. RCF.COM This procedure will perform an NCP CONNECT command after validating the specified server information stored in DSVCONFIG.DAT. STS.COM This procedure will display all known process status flags that are enabled for a specified PID. TIME.COM This procedure will produce a fancy date/time printout. A rather droll piece of DCL coding. ***************************************************************** [SCHAFFRATH.IDLE-MONITOR] This program would fall into the category of 'yet another idle terminal killer'! This program, written in BASIC, provides several features gleaned from other implementations. It also provides a feature allowing the system manager to query it's internal database about the status of all known processes, zero idle counters for specific processes and reload it's database of processes to ignore. Please read IDLE-MONITOR.DOC for more information. IDLE-MONITOR.BAS This is the source file. It was written for use under BASIC V3.3. IDLE-MONITOR.COM This is the startup procedure for running Idle-Monitor. Edit it to suit your site. IDLE-MONITOR.DOC This is the documentation for Idle- Monitor. IMC.BAS This is the Idle-Monitor Control program. Page 3 It is used to communicate with the running Idle-Monitor program. IMC.HLP This is the online help for IMC. It should be inserted into IMC.HLB and stored in SYS$HELP. IMC_COMMANDS.CLD This is the .CLD file to be linked with IMC. Perform a SET COMMAND/OBJECT to create the object code and link it with IMC. ***************************************************************** [SCHAFFRATH.INTERNALS] Several interesting internals programs. NOLOGINS.MAR This program will prevent the job controller from prompting for username and password. The behavior is identical to login attempts made when the system is booting up. To clear the setting, simply perform a SET LOGIN/INTERACTIVE=n. SECURE.MAR This program will set the bit TT2$M_SYSPASSWORD on a specified terminal port. It is intended for use with the template devices LTA0 and NVA0 although it will probably work with 'real' devices. This will allow system passwords for devices which would not normally have them. SECUREMSG.MSG Message file for SECURE.MAR. UNIT_SEED.MAR This program will reset the counter for a template device so that all new units start at 1. As an example, as a system is used, it is not uncommon to see unit numbers like LTA723: or VTA296:. After execution, new units will start out as LTA1: and VTA1:. UNSECURE.MAR A program to disable syspassword settings made by SECURE.MAR. USERNAME.MAR This program will allow the user to change his/her username. USERNAME.CLD .CLD for use with USERNAME.MAR. USERNAMEMSG.MSG Message file for use with USERNAME.MAR. Page 4 ***************************************************************** [SCHAFFRATH.LMF] Some interesting little tid-bits dealing with the License Management Facility. FORMAT_PAK.COM This procedure will take the output of a LICENSE ISSUE command and format it to look similar to a PAK provided by DEC. LICENSE_SERVICE.HLP Documentation on the use of the services SYS$GRANT_LICENSE and SYS$RELEASE_LICENSE. ***************************************************************** [SCHAFFRATH.MAILVIEW] MAILVIEW.BAS This program will allow a user to read his/her mail messages in a screen oriented environment. It allows for the selection of mail folders and messages via the arrow keys. In addition, it will allow a privileged user to read someone elses mail. This program, as yet, does not use the callable MAIL interface. (It will at some point in time) MAILVIEW.DOC This is the documentation for MAILVIEW. Unfortunately, it is one minor revision behind. Documentation is missing for the left and right arrow keys which scroll a long message. ***************************************************************** [SCHAFFRATH.MISC] Various programs that were too small to break into their own category. LATPORT.BAS This program will read the DECserver port information for a specified device via a call to SYS$QIOW. The functionality of this program was replaced by the new $GETDVI item DVI$M_TT_ACCPORNAM. However, it does return the LAT$LINK value which is not currently available via $GETDVI. But does anyone really care about that information? RDMODEM.BAS This program will read the modem control signals of a specified port and display them in a readable format (similar to a break-out box). Page 5 ***************************************************************** [SCHAFFRATH.PCBFLAGS] This code will allow a user with $CMKNRL to change various process flags in the Process Control Block. For example, you can make a BATCH job INTERACTIVE, enable full security auditing on a process, attempt to remove processes stuck in Resource Wait by setting the 'no resource wait' attribute. PCBFLAGS.BAS Source code. PCBFLAGS.CLD DCL Command definition. PCBFLAGS_KERNEL.MAR Kernel mode code to be linked with PCBFLAGS.BAS. ***************************************************************** [SCHAFFRATH.UAF] Several programs to do interesting things with the User Authorization file. UAFDEF.TXT User Authorization File Record format and definitions for use with the BASIC language. UAFLOGIN.BAS This program will allow the privileged user to scan the UAF for logins which occurred on or after a specified date. UAFSCAN.BAS This program will allow the privileged user scan the UAF for those usernames with a non-zero login failure count. UAFZAP.BAS This program will allow the privileged user to change parameters in the UAF which are not normally modifyable. These parameters are: login failure count, date/time of last interactive and non- interactive login, and the date/time of the last password changes. [End of $README.TXT] ========> [VAX89A2.SHAPIRO]AAAREADME.TXT;2 <======== Extensible VAX Editor - EDT Extension [ EVEDT ] (EVEDT Version V4.0-110188) (For use with VMS 5.x and TPU 2.x and above) AUTHOR Steven K. Shapiro SKS Associates POB 610637 Austin, TX 78761 14 December 1988 EVEDT is a very extended EDT superset and has some language specific features for several languages. See the .HLP file for full details. The EVEDT software package including all source code, section files, online help and documentation is subject to change without notice and should therefore not be construed as a commitment by its author. EVEDT Version 4.0 (and above) is designed to work with systems which are equipped with TPU V2.0 and above (available with systems which are VMS 5.0 and above). Since DIGITAL assumes no responsibility for its TPU product, I assume no responsibility for the use or reliability of EVEDT on any equipment or for any purpose and it is therefore offered as is. ========> [VAX89A2.SPC]AAAREADME.TXT;1 <======== (@)(@)(@) (@)(@)(@)(@)(@) SPC's Submission (@) %% ""-"" %% (@) (@) %%% (" ") %%% (@) Submitted by: (@) %%% ( O O ) %%% (@) Terry Kennedy (@) %%%% ( > ) %%%% (@) Saint Peter's College (@) %%%%% |-| %%%%% (@) Academic Computer Center (@) %% ((SPC)) %% (@) 2641 Kennedy Blvd (@)(@) | | (@)(@) Jersey City, NJ 07306 (@) | | (@) (201) 435-0252 -------|-|------- terry@spcvxa.bitnet Peter Peacock This software is made available to the public with no warranties, guarantees, or liability for its use or any consequences thereof. After all, it's free. But we think it works. If you have problems, please let us know. [.COOKIE] The biggest "monster fortune cookie" system you've ever seen. Full versions for VMS, RSTS/E, RT-11 and MS-DOS are included. [.FINGER] An update to the VMS FINGER utility. This is version V51_1_13 of FINGER. ========> [VAX89A2.SPCTELE]AAAREADME.TXT;1 <======== Space Telescope Science Institute ABSTRACTS F I L E L I S T I N G -------------------------------------------------------------------------------- ******************* * C O M F I L E S * ******************* MAILUAF.COM modified sys$examples:mailuaf.com to change users mail counters and personal name, view their mail directory and list all forwarding addresses and personal names. Regrettably, it's written for VMS V4.X -------------------------------------------------------------------------------- ***************************** * L O G G E R U P T I M E * ***************************** Makes a log of system uptime, reason for crash. At the end of the month, a report is produced showing number of crashes and shutdowns, average time to reboot on both and amount of business downtime. This is version 2.0 with bugfixes and enhancements -------------------------------------------------------------------------------- *********************** * M O N _ R E P O R T * *********************** Works off DEC software in sys$examples MONITOR.COM, MONSUM.COM and SUBMON.COM to create monitor stats for your machine. Data is then automatically plotted weekly using DISPLAA. (NB if you don't have DISPLAA, this will at least gather and massage the raw data into form.) -------------------------------------------------------------------------------- ******************* * S U B S C R I B * ******************* Creates listing of who has how many blocks on each disk to see if disk is over-subscribed and why. -------------------------------------------------------------------------------- *************************** * V W S _ G R A P H I C S * *************************** Page 2 Neat graphic tricks for Vax Workstations. ========> [VAX89A2.SWING_VMS5]AAAREADME.TXT;2 <======== Swing program from DECUS tape I had to modify SWING when I went to 5.0-2. I also, some time ago, added a 'list' option (get a directory listing while in swing). This area contains the result, with the Fortran sources in a ZOO file to conserve space. -------------------------------------------------------------------------------- John Howells | "Science does not | howells@pioneer.arc.nasa.gov Sterling Software | remove the terror | howells@krypton.arc.nasa.gov Palo Alto, Ca. | of the Gods" | howells%kry@ames-io.arpa ========> [VAX89A3.DBAG]AAAREADME.TXT;1 <======== DBAG This is DBAG, a full-function relational DBMS which is somewhat dBase III like, but runs on VMS. English language documentation has been added by Nick Nelson, Nick%evax2@rvax.ccit.arizona.edu. There is a very nice full screen feature and many enhancements over dBase III. The complete package is here (save for the large sample databases), and has been recompiled in /NODEBUG mode to save (a lot of) space. ========> [VAX89A3.NEWS58]AAAREADME.TXT;2 <======== NEWS 5.8 The main contents of this directory are ANU NEWS Version 5.8, from Geoff Huston, Australian National University. This gives a fairly complete Usenet News reader and NNTP package that allows a VMS site to receive or send Usenet news (provided he has a feed) and also use the News package as an electronic conferencing system along the lines of VAX NOTES, but allowing more layers in the topics trees. A somewhat NOTES style keypad interface exists. Documentation is extensive. This is from the University of Kansas Anonymous FTP directory. (Pulled by your VAX tape editor [GCE]). The following files are available: File Name Size in Bytes Description 000_readme.ascii;1 1526 This file autologout.bck_z 128579 AUTOLOGOUT Source and Executables lzdcmp.exe;1 69632 LZW decompression program ( new version ) lzw.bck_z;1 137635 LZW source ( new version ) news_v58_dist.bck_z; 587525 NEWS executables and minimum documentation news_v58_doc.bck_z;1 464853 NEWS detailed documentation news_v58_obj.bck_z;1 1689071 NEWS object files news_v58_src.bck_z;1 516001 NEWS source Most of the files here have been compressed to save file space and transmission time. Each of these files is an LZW compressed Backup Save set. To get a file you must use a binary transfer. First, get the LZDCMP.EXE file, so that you can decompress the save set after you get it, and then get the xxx.BCK_Z file. For example, LZW.BCK_Z is a compressed backup save set of the LZW compression/decompression routines. Using Wollongong TCP/IP on a VMS system you would do the following: $ ftp kuhub.cc.ukans.edu ! (129.237.1.10) ... (you already know how to do this, or you wouldn't be reading this :-) *binary *get lzdcmp.exe *get lzw.bck_z *quit $ LZDCMP:==$disk:[dir]LZDCMP $ LZDCMP lzw.bck_z lzw.bck $ BACKUP lzw.bck/save/sel=[*...]*.* []*.* These commands would copy the LZDCMP program into the current directory, copy the compressed save set to the current directory, define the LZDCMP command, decompress the backup save set, and finally, extract the source files from the backup save set. There are two different versions of the LZW compression version. The new version works fine for decompressing the files found on this directory, but will not correctly decompress UNIX compressed files. The old version will handle UNIX files correctly, but will not decompress some of the files made with the newer version. I did not realize there was a problem with the new Page 2 version until after I had deleted the source files for the old version, and I didn't want to distribute the program without source, hence the two versions. If all you want to do is decompress the files you get here or compress and decompress files using only the LZW package, the new version works fine. If you have a file from a UNIX system, you will need to get the old version. [Tape editor's note: The new version of LZDCMP can indeed read Unix compressed files. However it is necessary to give a command of the form $lzdcmp -b -x 1 inputfile.type_z outputfile.type since the -x 1 switch is REQUIRED for handling Unix files. A spurious error message is usually generated at end of file claiming that some error occurred. However, this has only to do with end of file boundary conditions. The data comes out OK. The unknown VMS error number 0 is just unix-ese for "success". Glenn Everhart ] Direct any questions to: +-------------------+-------------------------------------+------------------+ | Bob Sloane \Internet: SLOANE@KUHUB.CC.UKANS.EDU/Anything I said is | | Computer Center \ BITNET: SLOANE@UKANVAX.BITNET / my opinion, not my | | University of Kansas\ AT&T: (913) 864-0444 / employer's. | +-----------------------+-----------------------------+----------------------+ ========> [VAX89A3.TREADWAY]AAAREADME.TXT;1 <======== State Transition Simulator --| Summary This package body contains all packages necessary --| for the State Transition Executor to operate --| Description --| This package body contains the following software hierarchy --| Build_Transition_Actions_Package Procedure --| Build_Transition_Events_Package Procedure --| Build_State_Transition_Executor Procedure --| Get_Threads Procedure --| Requirements --| Use Ward-Mellor Methodology --| Keywords --| Real-Time, Recursion --| Developed_By --| P.L. Treadway --| GTE Government Systems Corporation --| 1 Research Drive --| Mail Stop #54 --| Westborough, Massachusetts 01581 --| (508) 870-4482 --| As_Part_Of --| Structured Development for Real Time Systems --| Under_Contract --| 5-9 (After Hours) ---------------------------------------------------------------------- -- -- -- B u i l d _ T r a n s i t i o n _ A c t i o n s -- -- -- -- This procedure builds the Ada package Transition_Actions. -- -- The package Transaction_Actions consists of two Ada files, -- -- one for the specification and the other for the body. The -- -- files are named as follows: -- -- -- -- Package Specification: Transaction_Actions_Spec.Ada -- -- Package Body: Transaction_Actions_Body.Ada -- -- -- -- With Mealy State Transition Diagrams, an event at some state -- -- may cause the system to transition to another state and -- -- optionally cause some action to occur. The State Transition -- -- Executor simulates the events which in turn, will cause -- -- "Action" procedures in the Transaction_Action package during -- -- run-time. The action that occurs is displayed on the screen -- -- and optionally written to a file as well. -- -- -- ---------------------------------------------------------------------- ========> [VAX89A3.UALR]AAAREADME.TXT;1 <======== ******** ******** ***** ****** *********** * * * * * * * * * * * * * * * * * * * * **** * * * * * * * * * * * * * * * * * * * * * * * * * * **** * * * * * * * * * * * * * * * * * * * * * * * * * ** * * * * * ***** * * * * * * * * * * * * * * * * * * * * * * * * ******* * * * * * * * * * ******* * * * * * * ************ * * * * * * * * * * * * * * * * ************ ****** ****** **************** ****** **** Submissions by: Dale Miller University of Arkansas at Little Rock Data Center 2801 S. University Little Rock, AR 72204-1099 DOMILLER@UALR.BITNET To further your computing experiences, the following directories are enclosed for your inspection and use: [.ALOCWAIT] - ALLOCATE/WAIT - The qualifier that VMS left out! Useful for anyone who has to wait on a peripheral to become free (particularly in a batch job). This revision fixes a major bug in the previous version. [.ETAPE] - The latest version of an old favorite. This ETAPE has a few fixes in since the last one on DECUS. Converts to/from EBCDIC, non-standard ASCII and Honeywell GCOS BCD tapes. This revision now allows writing of standard-labelled IBM tapes and supports both command-driven and screen-driven modes of operation. The documentation has also been (slightly) expanded. [.BBS] - A full-function bulletin board system for the VAX. It has messaging, conferencing, uploads, downloads, etc. Rev. 7.3. This version provides user definable text, naming, etc. so that it may be installed and used by most sites as is. [.CB] - A CB simulator for the VAX. So good you'll think it's the real thing! Identical to previous submission, but included for completeness of UBBS. [.READBACK] - A BACKUP save-set extraction utility. Allows you to extract a list of files from a backup save set. Not particularly general purpose, but useful. Permission is given to all DECUS members to copy, distribute, and use all files Page 2 contained in this submission. Not to be sold! ========> [VAX89A3.UUCP]AAAREADME.TXT;1 <======== The VMSnet Working Group (VAX Systems SIG) Submissions coordinated by: Jamie Hanrahan, Simpact Associates 9210 Sky Park Court, San Diego, CA 92123 +1 619-565-1865 X116 jeh@crash.cts.com This directory tree contains Version 1.1 of DECUS uucp (formerly "VMSnet software"), a package which allows VMS systems to exchange mail and network news with other systems (including Unix systems, and VMS systems running this software) using the uucp "g" protocol. This version completely replaces Version 0.2, found in the [.VMSNET...] tree on the Fall 1988 VAX SIG tapes. It runs under both VMS V4.7 and V5. Geoff Huston's ANU News, Version 5.7, with several minor modifications (for uucp integration) and fixes, is included. Full documentation is in [.UUCP.DOC]URGD11.MEM, and in other files described therein. The total space required for these files is about 36,000 blocks. If you have no plans to work on this software, you can save about 17,000 blocks by not restoring the source files, object files, and development tools. A BACKUP command such as the following (edited to reflect the actual saveset and root directory name on the SIG tape, device names, etc.), should work. (This command obviously hasn't been tested, since this was written before the tape was assembled; you may have to experiment a bit.) $ backup tape_dvc:vax89xn/select=[vax89xn.uucp...] - /exclude=([vax89xn.uucp.devel...], [vax89xn.uucp.fromthenet], - [vax89xn.uucp.news57.bld_v4], [vax89xn.uucp.news57.bld_v5], - [vax89xn.uucp.news57.src], [vax89xn.uucp.orig_code...], - [vax89xn.uucp.tools...]) disk_dvc:[*...] Other contacts, in case Jamie can't be reached: Tom Allebrandi II Mark Pizzolato ACCI 1558 Fernside Street 700 Harris Street, Suite 101 Redwood City CA 94061 Charlottesville, VA 22901 +1 415-369-9366 +1 804-977-4272 mark@infopiz.uucp ta2@esther.acci.com ...!uunet!lupine!infopiz!mark ========> [VAX89A3.WATCHDOG]AAAREADME.TXT;1 <======== W A T C H D O G This directory contains the WATCHDOG program. The original was taken from a DECUS tape (unknown authors) and was rewritten. The purpose of this program is to monitor interactive processes and log processes off that have been inactive for a specified period of time. A interactive process is a process that is attached to a terminal. The process can be network process, a spawned process, or an interactive process. WATCHDOG does not care as long as it is connected to a terminal. There are several logical names needed to run to WATCHDOG which are explained below. WATCHDOG_OPER_FLAG - Specifics which operator terminal types are to receive WATCHDOG operator messages. WATCHDOG_INTERVAL - Defines the Interval that WATCHDOG should wake up and look for idle processes. WATCHDOG_START_MSG - Defines the system wide default at which time WATCHDOG will start taking idle action and at every interval after that until the process it no long idle or the process is stopped. WATCHDOG_STOP_PROC - Defines the system wide default at which time WATCHDOG should perform the stop action on idle processes. WATCHDOG_FLAGS - Defines the system wide default option flags for users. Specifics which options will be on by default when WATCHDOG is running. WATCHDOG_FORCEX - Defines the system wide decimal value to be issued by $FORCEX system service before the users to be logged off. WATCHDOG_TIMESTAMP - Defines the frequency timestamp messages (Optional) should be send to the operator. If the flag USER_M_NO_OPER_TIMESTAMP is set in system default options then no logical name need be defined. WATCHDOG_EXCEPTION_FILE (Must be Comment Out If Not Used) - Defines file containing the exceptions to override the default start message, stop process, and option values. George H. Walrod III 8150 Lakecrest Drive #402 Greenbelt, MD 20770 (301)474-2971 ========> [VAX89A3.ZMODEM]AAAREADME.TXT;1 <======== [Editor's notes: This is an update of Chuck Forzberg's X/Y/ZMODEM programs RZ and SZ The program was compiled using the GCC 1.34 C compiler.] May 1989: Corrections for undefined variable and multiply defined rdchk() on some systems. New for April 1989: ZMODEM compression and other compatible extensions have been added to the rz and sz programs. Please read the comments in the rz.c and sz.c source code for licensing information for commercial use. Previous versions of rz and sz (April 1988) remain Public Domain. New for April 1988: VMS C flavors of rz and sz especially for tired frog stompers. The following performance log entries give the story! 2400 Z splat.arc 3968 220 18 0 0 0 512 30 (rz) 0 ccvax off 2400 K splat.arc 3968 110 36 0 0 0 89 -1 get -1 ccvax off The contents of RZSZ.ARC can be uploaded to a VAX/XMS system by ZCOMM or Professional-YAM using the supplied vupl.t script. Connect to your VMS system, select an empty directory, and then give the YAM/ZCOMM command: "source vupl.t". This will attempt to start a Kermit server ans upload the files to it. If the script can't fire up a Kermit server, the script will use the VMS DCL "create" command to upload the files directly. In the latter case, use a clean line for best results. Compile/Link directions for VMS C are in the comments at the beginning of the rz.c and sz.c files. The contents of RZSZ.ARC can be uploaded to a Unix or Xenix system by ZCOMM or Professional-YAM using the supplied zupl.t script. Connect to your Unix/Xenix system, select an empty directory, and then give the YAM/ZCOMM command: "source zupl.t". This will upload minirb.c, compile it, and then use minirb to upload the rz/sz files. Once these files are on your Unix system, you can type "make". The Makefile will list the various systems it knows how to compile the programs for, and the command to do so (e.g., "make bsd"). The Makefile is self explanatory; just say "make". Naturally, rz and sz work best with comm programs that seamlessly support ZMODEM command and file AutoDownload (Pro-YAM and ZCOMM). The "DSZ" shareware program allows ZMODEM file transfers with traditional DOS comm programs, but it must be called manually. (The computer should do that for you!) DSZ provides a "mini Page 2 term function" that supports ZMODEM AutoDownload. DSZ (part of DSZ.ARC) and the ZMODEM protocol description (YZMODEM.ARC) are on TeleGodzilla and other fine bulletin boards. Chuck Forsberg WA7KGX ...!tektronix!reed!omen!caf Author of YMODEM, ZMODEM, Professional-YAM, ZCOMM, and DSZ Omen Technology Inc "The High Reliability Software" 17505-V NW Sauvie IS RD Portland OR 97231 503-621-3406 TeleGodzilla:621-3746 FAX:621-3735 CIS:70007,2304 Genie:CAF ========> [LT89A.AVEN_MAKE]AAAREADME.TXT;1 <======== The contents of this directory constitute MAKE/VMS version 3.4 by Todd Aven/the Software Sweatshop. This is a UNIX make look-alike optimized for the VMS environment. Much effort has been expended to keep makefiles as closely compatible with UNIX makefiles as possible, but some differences naturally arise. Please refer to MAKE.DOC or MAKE.HLP for online information about MAKE. The most recent modifications are documented in RELEASE.V33. Two example makefiles are provided, MAKEFILE. and PMDF.MAKE. Simply running MAKE.EXE *should* rebuild MAKE (if necessary). Comments, suggestions, and bug reports should be directed to one of the addresses at the end of MAKE.DOC. Todd Aven 6/1/89 ========> [LT89A.BAUER]AAAREADME.TXT;1 <======== --------------------------------------------------------------------------- Space Telescope Science Institute Tools Group DECUS Atlanta '89 Submissions --------------------------------------------------------------------------- This saveset contains all source, objects, and executables for a series of tools developed in the OSB Tool Group at the Space Telescope Science Institue in Baltimore Md. The source languages include VAX C, FORTRAN, SCAN, MACRo, and MESSAGE. If you do not have one of these compilers, yuo can still link with the objects. There are LaTeX documents for most of the tools also included. The LaTeX include files have also been included should you want to try to LaTeX these. Some of the tools have logical names associated with them that you will need to define before running/building the tool. Tool descriptions follow: =========================================================================== Tool: Check Map (CKMAP) Tool Description: The CKMAP tool scans a VMS link map for PSECT mismatches and undefined symbols and reports these accordingly. =========================================================================== Tool: Disk Report Tool Description: The Disk Report tool scans one or more directory log files creating a series of reports summarizing disk space utilization. =========================================================================== Tool: Show Merged CMS Classes Description: The Show Merged CMS Classes tool compares all of the elements in a CMS library class (typically an SPR class) to see if they are also inserted, or ``merged'' into another class (typically a PENDING class) in that same CMS library. =========================================================================== Tool: Image Definition Tool (IMGDEF) Description: An image definition file contains the information on how to build an executable image. It is the primary input to IMGDEF, which is used to produce an options file, an MMS file to describe the LINK process, and an MMS file for building the image and its components. Page 2 =========================================================================== Tool: Remote CMS Server Description: The Remote CMS tool provides an interface to CMS libraries on a different DECnet node. This lets the user issue CMS commands that access a CMS library on a different VAX without having to log onto that node. =========================================================================== Tool: DCOPY Tool (Delete/Copy Tool) Description: The DCOPY is a modified version of the VMS COPY command that deletes a file in the destination directory before it copies into it. Before it copies the file to the destination directory, it checks for the existence of the file, and if it exists already AND the revision date of the existing file is older than the revision date on the file to be copied, DCOPY deletes the file. This is useful when disk space is tight on the destination device. Stretched logicals are also supported such that only the first version of a file is copied over a stretched directory list. =========================================================================== Tool: MMS Generator For Source (MMSGEN) Description: The MMSGEN tool is used to generate a compile MMS for files with the following extensions: .FOR, .EQF, .EQE, .FBL, .C, .SCN, .MSG, .MAR, .MBL, .X. It scans one or more input files creating one or more MMS files with the correct dependency list and action lines to build or compile to target object file. =========================================================================== Tool: Link Check Tool (LNKCHK) Description: The Link Check tool verifies the existence of all input files on a link command, passing the command onto the Linker if all inputs exist. Link Check is a workaround for a bug in the Linker that causes it to go into an endless loop when processing many objects with logical searchlists when one of the objects is missing (either from the command line or an options file). =========================================================================== ========> [LT89A.GNUSOFTWARE]AAAREADME.TXT;1 <======== GNU Software This area contains several programs from the Free Software Foundation, a group working on a complete replacement for Un*x which will solve performance and reliability problems with the Un*x OS and add new functionality. Included are BISON (a YACC superset), an AWK, Gnu Emacs, Gnu C, Gnu C++, and several more. The VMS binaries for a bootstrap Gnu C for VMS are included also. Also included are VMS ports of GAWK, BISON, and GNU Grep. Please note that these utilities are primarily for GNU with VMS variants in some cases. Also, Gnu C is a BETA version. It is fairly usable nonetheless, and version 1.34 here is quite recent. The diffs to go to 1.35 GCC are present, but GCC 1.35 does not compile itself under VMS (yet) so is not included. GCC 1.34 for VMS is here. When Gnu C finishes compiling all of Berkeley Un*x, it will be called a "real" C. (This effort is reportedly going very well.) Gnu C has been reported to generate much better code than VAX11 C and to emulate Un*x C better also. Complete sources to all files are present, but are presented in compressed TAR saveset form. Tools able to pull these distributions apart under VMS are furnished in the [vax000.tools] directory on these tapes. Various messages from the GNU Mailing lists can be found in the ZOO archive CHANGES_CORRECTIONS.ZOO. Use the ZOO executable found in [VAXLT_89A.TOOLS] to read the ZOO file. Thanks to Richard Stallman et. al. for this software. ========> [LT89A.LOMASKY]AAAREADME.TXT;3 <======== AAAREADME.TXT V1.0 5/3/89 This directory contains the actual BASIC Source files that were referenced at the DECUS 1989 Spring Symposium held at Atlanta, GA. during the "LT029 - VAX BASIC Toolkit of Useful Callable Functions" session. These routines form the beginning of a "Toolkit" of useful and frequently-used functions that VAX BASIC programmers may need. These functions can be compiled and linked into any VAX BASIC program (or any other VAX language, as long as you take into account the subtleties and differences between the languages). See AAAREADME.ABSTRACT for a description of all of the contained functions. ========> [LT89A.MDRAW]AAAREADME.TXT;2 <======== This contains the initial release of MDRAW code and assorted utilities. Included are source files and executable for mdraw itself along with the converter for mdraw files into sixel files. Also included are files describing how to set up and how to use mdraw. These come in TeX format and in plain text. The user guide is in `help.txt' and the setup stuff is in `start.txt'. There is a command file start.com which sets up the directories needed and the symbols and logicals that need to be set up. (Hows that for repetitive redundancy?) Just change the directory path and anything else you like. There is a directory `[.samples]' that has, guess what, samples in it. There is a read.me in there describing how to look at them and print them out, once mdraw and company is set up. If problems arise, or major bugs strike, feel free to contact me at: S. Mike Dierken (206) 885 8408 Sundstrand Data Control P.O 97001 M/S 25 Redmond, WA 98073-9701 Note: The two fortran programs are slight modifications of the originals from a previous DECUS tape. The previous author (Strickland) is in no way responsible for anything that might go wrong. Nothing should go wrong, but if it does, complain to me. Thank you. ========> [LT89A.MEMOREX_TELEX]AAAREADME.TXT;1 <======== DECUS Submissions from Memorex Telex 3270 Networks 3301 Terminal Drive Raleigh, North Carolina 27604 The Spring '89 submission consists of two directories: [.ethernet] Contains a couple of programs for monitoring network traffic on an Ethernet. [.sde] The latest version of the Software Development Environment we use at Memorex Telex. SDE is a general model software development methodology that incorporates DEC/CMS and DEC/MMS. Further documentation is included in the AAAREADME files found in each of these subdirectories. ========> [LT89A.REMTAB]AAAREADME.TXT;1 <======== R E M T A B REMOTE TABLE HANDLING ROUTINES Version 2.0 September, 1988 INTRODUCTION WHAT IS REMTAB? REMTAB is a collection of routines written in VAX COBOL and MACRO that were designed to ease the task of dealing with static and semi-static data definitions that are used by multiple programs. These routines were developed by TERADYNE, Inc. in conjunction with a VAX DBMS application which is now used by Teradyne's Customer Service Organization. Early on in the development cycle of the system we determined that there would be certain types of data that we would need to maintain that would not require any or would require very little in the way modifications. We quickly learned that a DBMS database was not the kind of place to be storing these small data sets. We experimented with the idea of having separate RMS files for each table and decided that this too was not going to suffice. In both cases the overhead involved in loading the tables was too costly. In certain programs up to ten different tables would need to be loaded and in the case of the RMS file idea the amount of time invloved in simply opening each of the separate table files was sufficient enough that we decided to look at other alternatives. The Remote Table concept soon started to evolve. Our first attempts were much better than the RMS file concept but it was still taking too long to load all of the tables required by certain programs. The subroutine that loaded the tables was written in COBOL and we determined that this was likely part of the problem. After scrapping the table loader module and rewritting it in VAX MACRO we noticed a considerable improvement over the prior version. Finally we has something we could use. ========> [LT89A.TEX]AAAREADME.TXT;1 <======== Here are some TeXware items that didn't make it on to the February 1989 DECUS TeX Collection. The files ending in .TAR_LZW are compressed Tar files from UNIX. SPIDERWEB is a utility to generate versions of WEB for different languages. TEXPS-R1 is a TeX DVI to postscript system that will use the built in postscript fonts. TEXX_2_8_6 is a X11 Windows previewer for TeX DVI files. MAKEINDEX is a LaTeX utility for creating indexes ported to VMS. PROFILE is a program to profile PASCAL programs. XDVI is a port of the DVI viewer for X windows to DEC Windows. ========> [LT89A.TPUVI_V5]AAAREADME.TXT;1 <======== This is a clone of the Vi editor written in TPU; this version runs under VMS V5 and its' flavor of TPU. Complete sources, documents, and executable are present. ------------------------ Gregg Wonderly Department of Mathematics Oklahoma State University INTERNET: gregg@nemo.math.okstate.edu UUCP: {ihnp4, rutgers, isucs1}!okstate!nemo.math.okstate.edu!gregg US MAIL: 401 Mathematical Sciences Oklahoma State University Stillwater, OK 74078 ========> [LT89A.XEVE5]AAAREADME.TXT;3 <======== submitted by: Tom Wolfe Jet Propulsion Laboratory Mail Stop 510/202 4800 Oak Grove Drive Pasadena, CA 91109 (818) 397-9280 My Extended EVE Editor. This is the VAX/VMS 5.x version of the the XEVE spelling checker. Some of the other edit functin in the 4.x version of XEVE have not been conver to 5.x and are not included in this distribution. The XEVE spelling checker includes the following: Three dictionaries are used to test the spelling of words. A common dictionary (standard english words), a project dictionary (acronyms, etc). and a user defined dictionary. The user defined dictionary can be created/updated while in an EVE edit session. Utilities are provided to build all three dictionaries from text files containing one word per line. The source word file for the common dictionary must be in ascending (lexical) sort order. The project and user source word files do not. The EVE spelling checker also has special commands that understands a little about C, DCL, FORTRAN, DCL and MACRO source code files and only checks appropriate things. For example, The "SPELL FORTRAN" command checks only comments and character constants. The special command are currently very primitive. A separate (standalone) spelling checker patterned after the LBL software tools SPELL utility is also available. The common dictionary currently contains 91,000+ words. The project dictionary can contain 1,000 word (or 10,000 bytes). The user dictionary can contain 200 words (or 2,000 bytes). The maximum word size is currently 31 bytes. Documentation can be found in the file XEVE.MEM. Editor's note: In the interests of gaining a bit of (badly needed) space, the file COMMON.DICT was put into a VMS BACKUP saveset with the command $ BACKUP/BLOCK=4096 COMMON.DICT COMMONDICT.BCK/SAVE and was compressed with the LZCOMP tool. It may be decompressed with the command $ LZDCMP COMMONDICT.BCK_LZW COMMONDICT.BCK and the original file restored. This has brought the storage from over 6000 blocks to about 1300.