========> [VAX91A.4GL_SIG]AAAREADME.TXT;1 <======== Revision VS0059 Fourth Generation Languages SIG Library Collection Version: Spring 1991 Author: Members of the 4GL SIG Submitted by: Bart Z. Lederman, System Resources Corp., c/o DOT Transportation Systems Center 55 Broadway DTS-66 Cambridge, MA 02142-1093 Abstract: This is a combined effort by the Fourth Generation Languages SIG to produce a library of items related to or using DATATRIEVE, RALLY, or ACCENT-R. To save space on the VAX / L&T SIG Tapes at the request of their tape coordinators, only (mostly) new material for Spring 1991 is included here. [.GENERAL] Below this are sections which are of general interest: [.4GL_COMPARISON] Below this are directories containing some of the 4GL Comparison Panel / Problem session entries for Fall 1990 [.NEWSLETTERS] machine-readable copies of past newsletters Some additional newsletters from 1990 have been added, plus two newsletters in Interleaf format from Steve Cordiviola. ========> [VAX91A.ANTIVIRUS]AAAREADME.TXT;1 <======== This tree contains antiviral programs which have appeared for IBM PC (or similar MSDOS engines), for Amiga, and for Macintosh computers. In addition the top level contains a list of sites archiving this software. (These programs obtained from antiviral sites by Glenn Everhart). ========> [VAX91A.AUSDECUS]AAAREADME.TXT;1 <======== DECUS South Pacific Chapter Symposium Tape 1990. This tape was compiled from submissions gathered at the DECUS South Pacific Chapter Symposium, Canberra, August 19-24, 1990. Each submission is gathered in a separate directory labelled according to the contributor. A brief description of the contents follows this notice. ******************************************************************************* WARNING: The production of this tape involves only the collection and assembly into the current format. NO testing has been done so the risks of using code submitted to this tape are YOURS. You should test programs yourself to determine what risks they may pose. None of this code contains any known problems within the above mentioned limits. If you notice anything unusual about any DECUS program we ask that you attempt to help by reporting the problem to the DECUS office immediately in as much detail as possible. In using this code, please be aware that privileged code may contain operating system version dependencies whose effects should be assessed before use. Please exercise due caution. ******************************************************************************* [ACTEW] Wayne Myles, ACT Electricity & Water, Canberra, ACT. [ACTEW] Cookie v3.5, a fortune cookie program, with database. [ACTEW.PC] PC version of Cookie v3.5 [ACTEW.VAX] VAX version of Cookie v3.5 [AZTECH] John Wolnisty, A-Z Tech P/L, Brisbane, QLD. [AZTECH] Broadcast of running batch job information to console. [CSIROCR] Christopher Nutt, CSIRO Cotton Research, Narrabri, NSW. [CSIROCR] Diskspace scanning program, working but incomplete. [JDUFF] Jim Duff [JDUFF] A bug-fixed version of V00429 Encryption Routine [NOTES] NOTES.BCK, a saveset containing the NOTES files from the Symposium. [PCS] Craig McGill, Pagefile Computing Services, Woden, ACT. [PCS] Example programs from Craig's paper, showing how to set up a privileged Page 2 shareable image. [PRAXA] Trevor Taylor, Praxa [PRAXA.PBMPLUS] Extended Portable Bitmap Toolkit [PRAXA.PBMPLUS.PBM] Tools for manipulating bitmaps [PRAXA.PBMPLUS.PGM] Tools for greyscale images [PRAXA.PBMPLUS.PPM] Tools for full-colour images [PRAXA.PBMPLUS.PNM] Tools for content-idependent manipulations on any of the three formats [PRAXA.XAQ] Turn your workstation into an aquarium (DO NOT fill with water ;-) [PRAXA.XCHOMP] X Window Pacman [PRAXA.XGIF] Display GIF images on 8-plane X11 display. Allows image rescaling. [PRAXA.XGIF.PIC] A few GIF images [PRAXA.XINVAD] X Window Space Invaders [PRAXA.XLOAD] X11 Image Loading Utility Will view several image formats or load images onto the root window. Supported image formats are: Faces Project GIF Portable Bitmap (PBM) Sun Rasterfile X11 Bitmap X Pixmap [PRAXA.XSWARM] A swarm of little line segments chase a bigger one - cute. [PRAXA.XTERM] X Window terminal emulation [SPES] Paul Hogwood, Siemens Plessey Electronic Systems, Belconnen, ACT. {SPES] A collection of VAX goodies [SPES.ABBA] - Abbrevation/acronym store [SPES.BITS] - Miscellaneous goodies for VAX user [SPES.JPI] - Shows info about VAX processes {SPES.LTMONITOR] - Yet another Idle-Terminal-Killer [SPES.REMINDER] - Manages reminders for VAX users [SPES.X] - VAX users inter-communication ========> [VAX91A.BARNES]AAAREADME.TXT;1 <======== TETROIDS - A game which is similiar to the arcade game Tetris. This directory includes the source code, object file and an executable. You must have a X-Window terminal to use this program. The code should be compatible with all X-Window environments. The program will ask you 2 questions at the beginning, the screen sized desired and a skill level. For a 19 inch screen you should choose 1000. Otherwise just use trial and error. A good beginners skill level is 100. The skill level dictates how fast the objects will fall at the beginning of the game. The object of TETROIDS is to rotate the different objects in a way to complete lines. To rotate an object hit you left mouse button, to move object left hit you middle button, to move object right hit your right mouse button. To begin the game click you mouse on the begin window. To quit click on quit. Good luck and don't become addicted !!! Software: VMS Version 5.4 DECWINDOWS Author: Jym Barnes CONTEL 15 Declaration Trail Dr O'Fallon MO, 63366 (314) 926-8672 Compile: $CC TETROIDS $LINK TETROIDS,SYS$INPUT/OPT SYS$LIBRARY:DECW$DWTLIBSHR/SHARE Note: To execute this program on one node and view it on another type the following command if using DECNET. $SET DISPLAY/CREATE/NODE= If you are using TCP/IP then $SET DISPLAY/CREATE/NODE=/TRANSPORT=TCPIP * Make sure you use customize and modify security to allow the connection. This needs to be done even if you use you own account. There is two different version of Tetroids. The only difference is in the random number generate. You decide which one is more random. Page 2 ========> [VAX91A.BRIAN-JIM]AAAREADME.TXT;1 <======== This directory contains a fixed up copy of symtab from the Fall 1990 tape. A number of copies of the fall 1990 tape went out with this file corrupted; this one is fixed. The CDRom (#8) was fixed up. This utility lists symbols in object files. ========> [VAX91A.BULLETIN]AAAREADME.TXT;2 <======== The following are instructions for creating and installing the BULLETIN utility. None of the command procedures included here are sophisticated, so it is likely that several modifications will have to be made by the installer. The installer should enable all privileges before installation. Once installation is complete, it is suggested that the installer enter BULLETIN and read HELP FOLDERS to see the options available when creating or modifying folders. One of the main uses of BULLETIN, besides storage of messages that are manually entered by users, is storage of messages from network mailing lists. This is done by using the BBOARD feature, which is enabled using the SET BBOARD command inside BULLETIN. The alternative method is for mail messages to be written directly by a mailing program by calling internal BULLETIN routines. Such a a program has been written for the popular mail utility PMDF. If you wish to do so for another utility, read the text file WRITEMSG.TXT. I would be glad to include any such programs with my distribution if you think such a program would be of use to other users. Responding to mail which is either added via the BBOARD feature is done using VMS MAIL. If for some reason this is inappropriate, you can define BULL_MAILER to point to a command procedure, and which will be run instead of VMS MAIL. The parameters passed to this procedure are P1 = username and P2 = subject. 1) CREATE.COM This will compile and link the BULLETIN sources. Also, there are several INCLUDE files for the fortran sources (.INC files). BULLETIN will create it's data files in the directory pointed to by the logical name BULL_DIR. If you elect not to use this definition, BULLFILES.INC should be modified. Note that after this procedure compiles the sources, it puts the objects into an object library, and then deletes all the OBJ files in the directory. NOTE 1: If you plan on using the USENET NEWS reader capability of BULLETIN, read NEWS.TXT for installation instructions before compiling. NOTE 2: The maximum number of folders for this distribution is 96 folders. If you wish to increase this, modify BULLUSER.INC and recompile the sources. When the new executable is run, it will create a new BULLUSER.DAT data file and rename the old one to BULLUSER.OLD. You cannot reduce the number of folders. 2) INSTALL.COM The following procedure copies the executable image to SYS$SYSTEM and installs it with certain privileges. It also installs the necessary help files in SYS$HELP. (BULLETIN help file is installed into the system help library HELPLIB.HLB. If you don't wish this done, delete or modify the appropriate line in the procedure. Also, the help library for the BULLETIN program, BULL.HLB, can be moved to a different directory other than SYS$HELP. If this is done, the system logical name BULL_HELP should be defined to be the directory where the library is to be found.) 3) LOGIN.COM This contains the commands that should be executed at login time by SYS$MANAGER:SYLOGIN.COM. It defines the BULLETIN commands. Page 2 It also executes the command BULLETIN/LOGIN in order to notify the user of new messages. NOTE: If you wish the utility to be a different name than BULLETIN, you should modify this procedure. The prompt which the utility uses is named after image executable. If you want messages displayed upon logging in starting from oldest to newest (rather than newest to oldest), add /REVERSE to the BULLETIN/LOGIN command. Note that users with the DISMAIL flag setting in the authorization file will not be notified of new messages. See help on the SET LOGIN command within the BULLETIN utility for more information on this. Also, please note that when a brand new user to the system logins, to avoid overwhelming the new user with lots of messages, only PERMANENT SYSTEM messages are displayed. If you want SYSTEM messages, i.e. messages which are displayed in full when logging in, to be continually displayed for a period of time rather than just once, you should add the /SYSTEM= qualifier. This is documented in BULLETIN.HLP, although there it is referred to only with respect to a user wanting to review system messages. It can be added with /LOGIN. 4) BULLSTART.COM This procedure contains the commands that should be executed after a system startup. It should be executed by SYS$MANAGER:SYSTARTUP.COM. It installs the BULLETIN utility with correct privileges. It also includes the command BULLETIN/STARTUP. This starts up a detached process with the name BULLCP. It periodically check for expire messages, cleanup empty space in files, and converts BBOARD mail to messages. It also allows other DECNET nodes to share it's folders. If you don't want this feature and don't plan on having multiple folders or make use of BBOARD, you could eliminate this command if you like. However, it is highly recommended that you create this process to avoid extra overhead when users login. NOTE: BULLCP normally is created so it is owned by the DECNET account. If that account does not exist, BULLCP will be owned by the account that issues the BULLETIN/START command. In that case, access via other DECNET nodes will not be available. If you are installing BULLETIN on a cluster and plan to have the bulletin files be shared between all of the cluster nodes, you only need to have this process running on one node. On all other nodes, the system logical name BULL_BULLCP should be defined (to anything you want) so as to notify BULLETIN that BULLCP is running. (On the local node where BULLCP is running, this logical name is automatically defined.) The use of the MARK command to mark messages require that a file be created for each user which saves the marked info. That file file is stored in the directory pointed to by the logical name BULL_MARK. You can either let users who want to use this command define it themselves, or you can define it for them, i.e. DEFINE/SYSTEM BULL_MARK SYS$LOGIN. 5) INSTRUCT.COM This procedure adds 2 permanent messages which give a very brief description about the BULLETIN utility, and how to turn off optional prompting of non-system messages (via SET NOREADNEW). 6) BOARD_SPECIAL.COM This command procedure describes and illustrates how to use the Page 3 SET BBOARD/SPECIAL feature. This feature allows the use of BBOARD where the input does not come from VMS MAIL. For example, this could be used in the case where mail from a non-DEC network is not stored in the VMS MAIL. Another example is BOARD_DIGEST.COM. This file takes mail messages from "digest" type mailing lists and splits them into separate BULLETIN messages for easier reading. To use this feature, place the special command procedure into the bulletin file directory using the name BOARD_SPECIAL.COM. If you want to have several different special procedure, you should name the command procedure after the username specified by the SET BBOARD command. 7) INSTALL_REMOTE.COM This procedure, in conjunction with REMOTE.COM and DCLREMOTE.COM allows a user to install new versions of BULLETIN on several DECNET nodes from a single node, rather than having to login to each node. This is especially useful when a new version modifies the format of one of the data file. Older versions of BULLETIN will not run with newer formats and will either issue error statements when run, or may cause major problems by attempting to change the files back to the old format. (NOTE: Don't attempt to use this if different nodes are running different versions of VMS, i.e. V4 and V5, as they require different linked executables.) 8) MASTER.COM If you are using PMDF, and want to use the BBOARD option, a set of routines are included which will allow PMDF to write message directly into folders, which is a much more effecient way of doing it than the normal BBOARD method of using VMS MAIL. Read PMDF.TXT for how to do this. 9) OPTIMIZE_RMS.COM This routine optimizes index files. To run, type @OPTIMIZE_RMS.COM followed by the filename. If you omit the filename, it will prompt you to allow you to turn off or on several different types of RMS compression. The default is to turn on all types of compression. The optimization will cause the file to be compressed. If you use the NEWS feature, it is suggest that you run this procedure on BULLNEWS.DAT after it is created. Compression that file greatly speeds up the NEWS update process. If you are tight on space, and have been running BULLETIN for a long time, it might also be useful to compress BULLINF.DAT if that file is very large. However, compressing that (or the other BULLETIN data files) don't appear to save any execution time, unlike BULLNEWS.DAT. 10) BULLETIN.COM If one wants BULLETIN to be able to send messages to other DECNET node's GENERAL folder, but wants to avoid running the process created by BULLETIN/STARTUP on this node, another method exists. This is the "older" (and slower) method. BULLETIN.COM must be put in each node's DECNET default user's directory (usually [DECNET]). Once this is done, the /NODE qualifier for the ADD & DELETE commands can be used. The object BULLETIN pointing to BULLETIN.COM must be added to the NCP database, i.e. the command Page 4 MCR NCP SET OBJ BULLETIN FILE directory:BULLETIN.COM number 0 must be executed at startup time on the remote node. NOTE: Privileged functions such as /SYSTEM will work on other nodes if you have an account on the other node with appropriate privileges. ========> [VAX91A.BULLETIN]AAAREADME.TXT;1 <======== Bulletin is a messaging and conferencing system very similar in use to VAX MAIL. This directory has a new version of BULLETIN adding NEWS reading capability. Messages on BULLETIN can live in a number of folders each with many messages; these can receive mail lists also, can reply or post, extract, print, etc. Message folders can be auto expired after a period of time if desired, and each user's current position in the folder is recorded. As of V2.0, BULLETIN is able to read USENET NEWS via TCP/IP using either CMU, MULTINET, UCX, or via DECNET. It can also serve as a NEWS gateway for DECNET nodes without direct access to the NEWS server, i.e. a DECNET node without Internet access will be able to read NEWS. This version includes all necessary modifications to work under VMS V5.0. However, it will still be necessary to reassemble the ALLMACS.MAR source under V5 and relink. The V4 version will not be installable under V5 due to a change in a shared library which BULLETIN uses. However, relinking by itself will not be enough. You MUST also reassemble ALLMACS.MAR. If you only relink, BULLETIN can cause your system to crash (the BULLCP process will do this because it uses the routines in ALLMACS.MAR). ========> [VAX91A.CKERMIT]AAAREADME.TXT;2 <======== This area contains C Kermit from Terry Kennedy, obtained from watsun.c.columbia.edu, per the following note from Terry: Yup - the version on watsun is 5A(171), and that's the latest. I have newer development stuff, but it's not stable. You should note in the AAAREADME that this is supplied because a lot of people have expressed interest in it, and an older and less-functional C-Kermit was on an earlier tape. Users should still consider this a pre-beta release and be aware that it has known problems in handling the serial line. ========> [VAX91A.CKERMIT]AAAREADME.TXT;1 <======== From: ADVAX::"mcnc!pucc.PRINCETON.EDU!TERRY%SPCVXA.BITNET" "Terry Kennedy, Operations Mgr" 14-JUN-1991 14:26:34.12 To: ARISIA::EVERHART CC: Subj: Re: S91 tapes Received: by ADVAX.DECnet (utk-mail11 v1.5) ; Fri, 14 Jun 91 14:23:28 EDT Received: from mcnc by ge-dab.GE.COM (5.61/GE-DAB 1.15) with UUCP id AA15691 for ; Fri, 14 Jun 91 13:24:53 -0400 Received: from pucc.PRINCETON.EDU by mcnc.mcnc.org (5.59/MCNC/3-21-91) id AA12045; Tue, 11 Jun 91 17:35:19 -0400 for ARISIA.dnet.ge.com!EVERHART Received: from SPCVXA.BITNET by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 2766; Tue, 11 Jun 91 17:36:19 EDT Date: Tue, 11 Jun 1991 17:34 EDT From: "Terry Kennedy, Operations Mgr" Subject: Re: S91 tapes To: ARISIA::EVERHART Message-Id: <9B0928E780201BB0@SPCVXA.BITNET> X-Organization: St. Peter's College, US X-Envelope-To: EVERHART@ARISIA.dnet.ge.com X-Vms-To: IN%"EVERHART@ARISIA.dnet.ge.com" X-Vms-Cc: TERRY > the S91 tape is nearing completion; I'd like to get whatever c kermit > you have for it soon as you can. I can FTP it from watsun if that > is the Latest&Greatest (I got a version a week or so ago that had your > work in it), or will await media... Yup - the version on watsun is 5A(171), and that's the latest. I have newer development stuff, but it's not stable. You should note in the AAAREADME that this is supplied because a lot of people have expressed interest in it, and an older and less-functional C-Kermit was on an earlier tape. Users should still consider this a pre-beta release and be aware that it has known problems in handling the serial line. > I'd also like the pc-blue stuff after #679 at your convenience. > I will of course return the prelim S91 stuff your way...two reels' > worth, or one 4mm or 8mm. I'll send that out, but it might not be for a week or so - our computer venter was hit by lightning a week ago and we're still getting back to- gether. Yup, I'd appreciate a tape. 6250BPI 9-track is best (I don't have 8 or 4 mm). Thanks, Terry ========> [VAX91A.DBAG]AAAREADME.TXT;2 <======== 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. This version is unchanged in source from the one which appeared on the Fall '89 VAX tapes, but has been recompiled in VMS V5 so that it will run under VMS V5. Much of the distribution is compressed in LHARC or ZOO files to prevent it from taking excessive space. ========> [VAX91A.DECUSERVE_1991A]AAAREADME.TXT;2 <======== Submission Title: FORCEX -- A DCL interface to SYS$FORCEX Submitter/Author: M. Erik Husby Access Technology, Inc. 2 Natick Executive Park Natick, MA. 01760 (508)655-9191 Abstract: FORCEX provides a DCL interface to the SYS$FORCEX system service. This command is similar to the STOP "process" command except it simply tries to force the image in the specified process to exit. Computer and O/S Version Information: Any version of VMS with a C compiler. Other Documentation / Installation Instructions: Installation instructions are in FORCEX.TXT DCL help is in FORCEX.HLP Submission Title: WATCH - Program to monitor terminal data Submitter/Author: John Briggs (301)231-3061 Vitro Corporation 14000 Georgia Avenue Silver Spring, MD 20906 Based on WATCH5 from the 1989 Fall symposium tape Abstract: WATCH allows a privileged user to perform live monitoring of a terminal session. It also can supply keyboard input for the terminal being monitored. WATCH can be useful in system support, allowing support personnel to see actual error messages and assist remote users interactively. It can also be used as a debugging tool for modems, printers and other devices attached through serial interfaces. Computer and O/S Version Information: VAX, VMS 5.2 or greater. Other Documentation / Installation Instructions: WATCH5_BUILD.COM will create WATCH5.EXE in your current directory and Page 2 a user-written system service dispatcher, WATCH5_USS.EXE in SYS$COMMON:[SYSLIB]. More complete documentation may be found in the prologue of WATCH5.FOR ========> [VAX91A.DEMAX]AAAREADME.TXT;1 <======== There are two directories in this submission: [.KNOWN_FILES] This directory contains the notes and sample code for my talk titled "Known Files: The Internals of INSTALL" at the Spring 1991 DECUS Symposium. The contents of this directory differ only slightly from the same files distributed on the SIG tape for the Fall 1990 Symposium. [.LOGICALS] This directory contains the notes and sample code for my talk titled "The Internals of Logical Names" at the Spring 1991 DECUS Symposium. ========> [VAX91A.DF]AAAREADME.TXT;1 <======== DF Utility Author: Esther Lumsdon Date of this file: 3-MAY-1991 DF is like the unix (tm) df command. It gives a more informative display than $ sho dev d. It was written in FORTRAN while the author was employed by David Taylor Research Center, Annapolis, MD. DTRC cleared this item for public release on 9-NOV-1990. INSTALLATION There is source, object, and executable on the tape. Just backup the tape into an appropriate location, set the file permissions, and define a command. $ cre/dire mydisk:[df_utility] ! this does not have to be a top-level dir. $ set def mydisk:[df_utility] $ backup/log tape:df.bck/select=[esther.df...] [...] $ df :== $mydisk:[df_utility]df The current release of DF spawns to get a list of disks; a future version will use the new scan$device feature of VMS and eliminate the spawn. Another future version will be written in Verdix Ada. The author is currently employed by Verdix Corporation, and can be reached at esther@verdix.com or Esther Lumsdon 703-378-7600 Department VPSO Verdix Corporation 14130-A Sullyfield Circle Chantilly, VA 22021 Note: Verdix is moving to a new address sometime in August - September 1991. ========> [VAX91A.DIBOL]AAAREADME.TXT;1 <======== DECUS 1990 Fall Symposium - Las Vegas Session # LT196 DECUS 1991 Spring Symposium - Atlanta Session # LT046 VAX DIBOL - A User's Experiences Using System Services Abstract: This session will cover some of the uses for System Services and other Run Time Library Routines. Some knowledge of these routines and VAX DIBOL is assumed. This code carries no implied warranties nor will the author be held responsible for any problems stemming from its use. In other words: USE AT YOUR OWN RISK ! Submitted by: Mike Durkin Intracorp 1205 Westlakes Drive Berwyn, Pa 19312 (215) 889-2883 Please call if you have any questions. This directory contains Command Procedures, DIBOL & Message File Source. FILES DESCRIPTION ----- ----------- AAAREADME.1ST This file CALLMAIL.COM Command procedure to compile all modules used with CALLMAIL.DBL CALLMAIL.DBL Example of Callable Mail from DIBOL. CALLMAIL.OLB Object Module Library containing subroutines and functions used in CALLMAIL.DBL FIND_RIGHTS.COM Command procedure to compile FIND_RIGHTS.COM FIND_RIGHTS.DBL Example of how to use SYS$FIND_HELD to find the rights indentifiers held by the current process. FOCRE.SBL Example of simple folder action routine. GETST.SBL Example of subroutine to obtain process stats through LIB$xxxx_TIMER services. MAILDEF.DIB Include module which defines all Callable Mail Page 2 Item Codes for VAX DIBOL. MAILMSGDEF.DIB Include module which defines all Callable Mail Return Status Codes. SMAIL.SBL Example of subroutine to send a mail message. SNDMA.SBL Modifed SMAIL.SBL to be a function. STOPRO.COM Command procedure to compile STOPRO.DBL and STOPROMSG.MSG files. STOPRO.DBL Example of Force Exit - SYS$FORCEX service. STOPROMSG.MSG Message file for STOPRO.DBL TSTHLP.COM Command Procedure to compile TSTHLP.DBL TSTHLP.DBL Example of how to access Help (.HLB) files from VAX DIBOL. ========> [VAX91A.ETHERNET]AAAREADME.TXT;3 <======== From: ADVAX::"""l_leahy""@star.enet.dec.com" "Lee Leahy DTN 381-0570 14-May-1991 1051" 16-MAY-1991 22:04:36.68 To: arisia::everhart CC: Subj: AAAREADME.TXT - Contents file for DECUS Spring '91 VAXSIG tape Received: by ADVAX.DECnet (utk-mail11 v1.5) ; Thu, 16 May 91 22:03:23 EDT Received: from mcnc by ge-dab.GE.COM (5.61/GE-DAB 1.15) with UUCP id AA20298 for ; Thu, 16 May 91 21:46:00 -0400 Received: from enet-gw.pa.dec.com by mcnc.mcnc.org (5.59/MCNC/3-21-91) id AA06353; Thu, 16 May 91 19:45:43 -0400 for ARISIA.DNET.ge.com!Everhart Received: by enet-gw.pa.dec.com; id AA18531; Thu, 16 May 91 16:45:23 -0700 Message-Id: <9105162345.AA18531@enet-gw.pa.dec.com> Received: from star.enet; by decwrl.enet; Thu, 16 May 91 16:45:34 PDT Date: Thu, 16 May 91 16:45:34 PDT From: Lee Leahy DTN 381-0570 14-May-1991 1051 <"l_leahy"@star.enet.dec.com> To: arisia::everhart Subject: AAAREADME.TXT - Contents file for DECUS Spring '91 VAXSIG tape The MONHWA, MONLAT, and MONLAV programs are updates to the programs submitted by David Gagne. These programs can be used monitor the Ethernet or FDDI to determine what systems are using the LAN. These programs have been updated to include support for new Digital hardware. The MONHWA program is used to monitor the LAN and collect data on the LAN adapters in use. The MONLAT program is used to monitor the LAN and collect data on the systems and servers using the LAT protocol. This programs has been modified to better display the group numbers in use. The MONLAV program is used to monitor the LAN and collect data on the Local Area and Mixed Interconnect VAXclusters that are using the LAN segment. This program has been updated for multi-adapter LAVc support and thus sorts the displays in a different order. This program also displays additional information about each of the nodes in the cluster. ========> [VAX91A.EURO91]AAAREADME.TXT;1 <======== These are contributions from the DECUS Munich area for the S91 US VAX/L&T SIG tapes, thanks to Norbert Wiehl, European VAX SIG tapecopy coordinator. [.break] BREAK: A Terminal-Blocker ************************* Version 1.1 Irlet Thomas, Dr. Gruppe für Rüstungsdienste Stauffacherstrasse 65 CH-3000 Bern 22 Switzerland Abstract: When you run this program on a appropriate terminal, then the screen is erased and a prompt ask you for your login-password. You can't do anything on this terminal until you gave the correct password. The SYSGEN-parameters LGI_BRK_LIM and LGI_HID_TIM are considered for granting access to the teminalsession. Failures are logged on OPCOM. This Version is only for VMS Versions 5.4 and higher! [.koerber] Facility to run compilers for Fortran and Pascal on machines where the compilers are licensed where one has a cluster and wishes to make the compilers appear available everywhere. beide : KOERBER AG Hauni-Werke Rechenzentrum Digital / 646 Kampchaussee 8-32 2050 Hamburg 80 Tel: 040 / 7250-2918 [.license_1] [.license_2] Enhancements to LMF to allow the license database to be cleaned up, licenses moved, SUPs and so forth deleted, and more. [.load_function_keys] Short procedure to load function keys on a terminal. [.weck] The VTEDIT Editing Interface for VAXTPU The Video Terminal Editor VTEDIT is an editing interface for the VAX Text Processing Utility VAXTPU available under VAX/VMS. The VTEDIT interface is an efficient, keypad driven editor allowing multi window editing and providing semi automatic, context dependent text formatting. VTEDIT implements, among others, the following features: - support for multi file and multi buffer editing with optional selection of files and buffers via wildcards; - support for split screen editing using an optional second window into the same or another text buffer; - selection of insert and overstrike mode of editing; - selection of free and bound cursor movement; Page 2 - many additional editor functions, like: + (search and) replace operations, + global search and replace on all buffers, + rectangular cut, paste, and delete operations, + pattern-directed replacement operations, + operations to remember and retrieve buffer positions, + insertion of date, time, file and buffer names, + case and position control for searches, + case conversion and capitalization of words, + center line and fill paragraph operations, + control of tabulator setting and margins via a ruler, + operations to replace Tabs with spaces and vice versa, + deletion of trailing blanks, + sorting of buffers and ranges, + wildcard filename search and selection with semi-automatic loading of the next file(s) or all remaining files, + selection of user and system buffers from a list; - support for pattern-directed search based on: + TECO match control constructs, + VAXTPU pattern built-in procedures, + EVE-like VMS search patterns ("wildcards"), + ULTRIX-like regular expressions; - journaling the editing session in order to protect against loss of work in case of a crash: + as keystroke journaling, + as journaling of changes to the individual buffers; - access to the VMS operating system via DCL, Spawn and Attach commands; - access to VAXTPU with possiblities to extend the VTEDIT editing interface; - an extensible interface to the VMS programming facilities; - optional semi automatic, context dependent text formatting providing the following functions: + case conversion / automatic case control, + automatic indentation, + manual correction of indentation, + automatic word wrap (possibly context-dependent), + automatic line justification, + optional automatic insertion of closing parentheses and string delimiters, + optional highlighting of the matching opening parenthesis and string delimiter; - no (practical) restrictions as to the maximum size of texts to be edited; Page 3 - command driven line mode editing, available also on non-ANSI terminals and from batch files; - menu selection of editor commands; - optional EDT keypad emulation; - use of the mouse as positioning and command input device; - extensive online help; - optional access to the features of the Language-Sensitive Editor VAX LSE, providing operations to: + fill and align program comments, + specify a directory search list, + retrieve sources from a CMS library, + protect buffers against modification, + control the LSE code elision features, + move to and/or delete placeholders, + expand tokens, routines, placeholders, and aliases, + define aliases for use in later expansions, + insert and use pseudocode and overviews, + compile sources and review errors, + locate errors and retrieve the corresponding source text, + load language definitions and environments at run time, + access the LSE command interpreter directly; - optional access to the features of the Source Code Analyzer VAX SCA, providing operations to: + find declarations of symbols, + list positions of variable declarations and/or references, + retrieve corresponding sources, + access the SCA command interpreter directly. Dr. G. Weck Infodas GmbH Rhonestr. 2 D-5000 Köln 71 West Germany ========> [VAX91A.FLOWERS]AAAREADME.TXT;1 <======== ___ ___ _____ ___ ___ | \/ | / ____\ | | | | | \ / | \____ \ | |_| | SPRING 1991 VAX SIG TAPE SUBMISSION |_|\/|_| \_____/ \_____/ Memphis State University Harry Flowers Internet: FLOWERS@MSUVX1.MEMST.EDU 112 Admin Bldg Bitnet: FLOWERS@MEMSTVX1 Memphis, TN 38152 Phone: (901) 678-2663 +-------------------------------------------------------------------------+ | Disclaimer: The author, Memphis State University, and DECUS assume no | | responsibility for the use or reliability of this software. | +-------------------------------------------------------------------------+ SUBMISSION DIRECTORY ==================== AAAREADME.TXT - This text file. Most of these submissions require VMS V5.4 to run; in fact, many were modified to take advantage of new features. As I use most of these programs regularly, I would be interested in any problems of a general nature you may have with them, or enhancements which would prove generally useful. Enjoy! Corrections and enhancements to previous submissions: ----------------------------------------------------- DISK_WATCHER.COM - Monitors free disk space. Changed to use the F$DEVICE lexical instead of the old SHOW DEVICE /OUTPUT kludge. Since disk order is not important to DISK_WATCHER, this is not a problem. See command file for setup. RMSGLOBUF.COM - Shows files using RMS global buffers. Changed to use the F$DEVICE lexical; one less kludge in a kludgy but handy (if you take advantage of global buffering) program. The show device was used to take a name like DUA1: and translate it to HSC000$DUA1: or $1$DUA1: or something similar that DUMP would accept. F$DEVICE works very well for this. MENU.COM - DCL Menu System V2.1. Improvements over V2.0: now can space entries with blank lines between to group them; allows balancing columns any way you wish. See command file for full details. I don't know of any image activation off hand that the menu does, so it's pretty efficient. More efficient that SPAWNing commands (even if you have a "kept" subprocess to execute them), and more versatile. MEM.COM - Monitor free memory (esp. the last 10%) showing SYSGEN parameters. Made minor terminal-handling modifications. Good on memory-poor systems to see what's happening to your free and modified page lists. ASKOPER.BAS - Defines a symbol with an operator reply. What you wish REQUEST/REPLY could do. Works with any operator classes. Page 2 This version will ignore slashes "/" within quotes for the request, the /LOG qualifier is now the default, and operator replies are uppercased. ASKOPER.DOC - Documentation for the above program. ASKOPER.OBJ - Object file for those without a BASIC compiler. New submissions: ---------------- ADD_CHECKSUM.COM - Adds an internal checksum check to a command file. Just rather interesting, I prefer to use VMS_SHARE for distributing files through the mail. Uses the undocumented CHECKSUM DCL command. The next two are very helpful if you subscribe to mailing lists and have a heavy volume of mail. MAIL_EDIT.COM - This command file allows: o Spell checking of outgoing mail before you send it; uses the Vassar spelling package (not included) or any other which is invoked with the SPELL command. o Quoting of messages you reply to or forward. You may choose the quote character(s). The default is "> ". Unlike most of these on the net, this one will work with EDT or TPU because it achieves this with DCL. It also filters out the internal mail header on messages received through the foreign mail interface (keys off the "%"). o Appending a signature file to the end of your mail message. Directions for set-up and customization are included in the command file. MAILMAINT.COM - Program to create mail subdirectories and file mail from existing folders to the subdirectories. Assumes you already use a subdirectory for your mail. What this program does is create a subdirectory of your mail subdirectory for each folder you have in your mail file. It gives the subdirectory the folder name, and creates a folder.MAI file with a folder inside of the same name. It files all mail over 90 days old in these files. This can speed up MAIL access as there are fewer files in your mail subdirectory. It also does a compress on the subdirectory mail files. It does a convert of the main mail file, but *not* a compress. You will get better performance if you do a compress after you run it the first time, then do no more compresses unless you get an unusual volume of mail between runs. Once a week would be a good frequency. SYSTAT.BAS - System status program. I finally wrote the one I was looking for; it shows the things I want to see as well as some things that are important at our site. I named it after a similar DEC program on RSTS/E (for nostalgia and because I couldn't come up with any better one). It keeps to 80 columns unless you ask for process rights information. It shows the PID, Username, elapsed time, CPU time, mode, state, global and total memory, and image for any or all nodes in a cluster. It optionally shows the process name (replaces elapsed and CPU time), the IO counts (replaces the global and total memory), and process rights. The documentation contains all the details. Requires VMS V5.4 or later. The BASIC$STARLET.TLB include modules must have been rebuilt after VMS V5.4 to compile. Page 3 The executable may be installed with WORLD privilege. SYSTAT.OBJ - Object code for those with out a VAX BASIC compiler or a current version of the SYS$LIBRARY:BASIC$STARLET.TLB library. Just $ LINK/NOTRACE SYSTAT $ INSTALL CREATE dev:[dir]SYSTAT.EXE/PRIV=WORLD ! optional and add the SYSTAT symbol to your login. SYSTAT.TEX - LaTeX source for documentation. SYSTAT.PS - Postscript documentation for those without LaTeX. MASTER.BAS - Allows a nonprivileged holder of a nnn_MASTER identifier to grant/revoke any existing nnn_* identifier to any user. The program must be installed with CMKRNL, SYSPRV, and WORLD. This is intended to allow project managers to control access to their projects without having elevated privileges. (This is the primary reason for the SYSTAT program above showing process rights). Using ACLs with these identifiers allow very fine control over files and types of access. This program also requires VMS V5.4 and a current starlet to compile. MASTER.OBJ - Object file; see comments and directions for SYSTAT.OBJ above, except that this image must be installed or run with privileges: $ INSTALL CREATE dev:[dir]MASTER.EXE/PRIV=(CMKRNL,SYSPRV,WORLD) MASTER.TEX - LaTeX source for documentation. MASTER.PS - Postscript documentation for those without LaTeX. PMP.COM - Phone Message Pad. This mails a user a phone message. I find it very handy when I pick up for someone else. This way, I don't forget to give them the message. It's pretty simple. Just try it by sending a message to yourself. Some code to try another node is commented out; you may adapt for your site if not everyone is in the same SYSUAF. CSWING.EXE - Version of SWING written in C by S.J. Brown & modified by M. Akerberg. SWING is an extremely handy directory management tool. I have made several minor bug fixes to version 3.3 from Mats Akerberg. I'm calling this V3.4, but my version maintains the V3.2 key bindings that Mats changed in V3.2.x and V3.3. I think that the original V3.2 keys are much more intuitive to a VMS user than the V3.3 ones, so both of us will probably be maintaining slightly different versions. Mine also includes changes others have made from Mats' V3.2.2 which I got via FTP archives of vmsnet.sources. I'd like to thank the many hands which have maintained this code, and S.J. Brown, who did much more than just port this version from the original written in FORTRAN. CSWING.HLB - Help library for CSWING. Just put it in the same directory as CSWING.EXE or in SYS$HELP. CSWING.PS - Postscript documentation. See [.CSWING.DOC] for a runoff version. [.CSWING] - Contains sources for CSWING and has the following sub-directories: [.DOC] - Contains sources for help and documentation. [.OBJ] - Contains object files; the original is linked under VMS V5.4, so you'll need to go to the [.CSWING] directory and @LINK_V5 if you're running a previous version of VMS. If your site doesn't use CSWING, you're missing something. Even a "techie" such as myself finds it useful for browsing and cleaning up directories; it is even more valuable to a general user. Here are some of the bugs I fixed: Page 4 o Did not handle disks in bound volume sets. o Couldn't exit from "@ - change file protection". o Disk quota ("&") option did not stay on screen until key pressed. o Quit option did not work on copy or move files or directory options. o More ("Y") option failed after invoking it a fixed number of times. o More ("Y") option ^W did not reset internally to normal from wide. o More ("Y") option searching did not work in case-insensitive mode unless a lower-case string was used for the search pattern. o More ("Y") option spacing problem with form feeds; now treated just like a non-printable character (replaces it with a "^" character). o More ("Y") option caused the file manager to display the file in lower case after it had been viewed. Please note: If your site makes heavy use of CSWING and you find any bugs, I'd like to hear about them (but I don't promise fixes :-). It appears that I'll be supporting it (at least locally) for some time. +-------------------------------------------------------------------------+ ========> [VAX91A.GCE91A]AAAREADME.TXT;2 <======== Glenn Everhart's tree... [.ANALY...] AnalytiCalc spreadsheet for VMS etc. with changed version from Chris Dorn that uses SMG$ for screen access. I added my later mods to the spreadsheet to his SMG$ version so that it is functionally complete, though I have not tested the thing for functions that may have been broken by the SMG$ porting (notably the *@file.typ command within a spreadsheet cell). Also present is the initial release of AnalytiCalc for Unix, with a prelim Sun executable. This is the first release of this code. ASNVDM6.mar and VDDRIVER4ae.mar - my contiguous-file virtual disk images, just to be sure current versions are available somewhere well defined. Also present is VQDRIVERe.Mar. These have an important fix for SMP processors. [.BBOARD] Bulletin board program from Ben Cohen. This program links mail and VAX notes so that only one user need be subscribed to BITNET list server groups. [.DKBRAYTRACE] Raytracer for several systems; will produce images by ray tracing object definitions. PBM can display some output formats. See the AAAREADME.1ST file for more. [.NET91A] The usual collection of useful things seen on the Internet since Fall 1990. Includes updates to VMS RCS, a MORE replacement, updates to XV (image view in X), DECwindows and X examples, generic RZ/SZ (zmodem), VMS TAR updates, force workset trim, head/tail, MIRROR to let multiple terminals connect to a single session, much more. [.NETXV] XV update from Eric Wentz. XV is a program to view images in X windows. [.RTG] Caveats for RCS in VMS. The fixes for these are noted also though the RCS code itself is in the [.net91a...] tree here. (from Rich Gregory) [.SWING] C Swing vms directory examine frontend, obtained from the Swedish maintainer's FTP site. TECOC.tar_z Pete Siemsen's latest TECOC, now with full screen support; can run on VMS, MSDOS, AmigaDos, and Unix. ========> [VAX91A.GOATLEY]AAAREADME.TXT;2 <======== I've submitted BAT, which queues multiple commands to a batch queue. It works pretty much like SUBMIT, except you give the DCL commands and it creates a temporary file and executes them. Also submitted is FLIST, a TPU/MACRO-based directory and file manager. Hunter Goatley, WKU, goathunter@wkuvx1.bitnet, 502-745-5251 ========> [VAX91A.GOATLEY.FLIST]AAAREADME.TXT;1 <======== ======================================================================== Copyright 1990--1991 by Hunter Goatley. This code may be freely distributed and modified for non-commercial purposes as long as this copyright notice is retained. ======================================================================== FLIST v2.0 is a file and directory manager written in VAX TPU and MACRO. The program was originally written in 1987 by Hunter Goatley. FLIST v2.0 includes many new features, added by Hunter Goatley and Peter Galbraith. (Generic EVE and DCL code by Peter Galbraith is provided to support a "kept" EVE subprocess. This code is compatible with the code used by EVEplus.) Please forgive me for the bad code---I wrote it quickly and have never had the time to go back and really do much with it. It isn't as pretty as I'd like, but it works. To build, simply execute BUILD_FLIST.COM. This version of FLIST has been tested on VMS V5.3-1 through v5.4-1. Earlier versions will report errors during startup because FLIST uses new (since 5.2) TPU features to change default directories and provide support for DECwindows. To use, you must define a logical and a symbol: $ define FLIST_TPU_SECTION device:[dir]FLIST.TPU$SECTION $ flist :== $device:[dir]flist.exe You can then type $ FLIST [file-spec] The optional file-spec can contain wildcards. Once inside of FLIST, you can type H for a one-line description of some of the commands. Pressing PF2 will show you a list of all key definitions. All of the FLIST commands consist of either single-key presses or GOLD-key combinations; be careful which characters you type once inside FLIST. (If you use a DECwindows mouse for cut and paste between DECterms, be careful that you don't paste into a DECterm running FLIST, because each pasted character will be treated as an FLIST command.) If you don't want to define the logical, simply change the following line in FLIST.MAR to point to the section file FLIST.TPU$SECTION: SECTION: .ASCII /FLIST_TPU_SECTION/ Simply replace FLIST_TPU_SECTION with the full file specification. If you find bugs, drop me a line and I'll see what I can do. If you fix it, send me the fix and I'll incorporate it in my version. Known limitations: o Long file names get truncated and can't be viewed; it's one of those little bugs I just haven't gotten to yet. Page 2 Enjoy. I welcome any comments. Hunter =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer E-mail: GOATHUNTER@WKUVX1.bitnet ACRS, Western Kentucky University Voice: 502-745-5251 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- FLIST v2.0 Description Authors: Hunter Goatley, goathunter@wkuvx1.bitnet Peter Galbraith, galbrth@ac.dal.ca FLIST v2.0 contains an almost-completely-new interface. There are now two windows created when FLIST is started: a window of subdirectories and a window of all non-.DIR files in the specified directory. In addition, a "graphical" directory tree interface has been added, as well as support for a DECwindows mouse. Numerous bugs have been fixed, ranging from errors trying to copy files to purely-visual enhancements. Some of the new features include: o Separate subdirectory and file windows (can be resized) o Graphical tree interface (GOLD/T) o CD directory changer which uses abbreviations o Ability to connect to a "kept" editor in a subprocess o Separate key map lists for the various buffers, including user key maps o Support for DECwindows mouse ("M" and GOLD/S) o Support for an initialization file containing user customizations (see the file FLIST.INIT) o Option to repaint screens instead of scroll o Ability to copy, rename, and purge tagged files o Ability to view a full-screen MESSAGES buffer o Ability to shift the windows left and right o Ability to show all key definitions for a given buffer (PF2) The number of keys defined are too numerous to list here. The documentation for FLIST is sparse, but the product is (hopefully) intuitive enough that you should be able to understand what it does by simply playing with it. In addition to the documentation below, the sample initialization file FLIST.INIT contains extensive documentation about user-settable parameters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kept Editor: (see also KEPT_EDIT.README) ~~~~~~~~~~~~ FLIST allows the use of a kept editor (spawned in a sub-process) although none is provided. It should work with EVEPLUS without modification. Page 3 Your kept editor should: o Have defined the logical name KEPT_EDIT in the JOB table to hold the the process name of the editor. FLIST will translate it and attach to this process. This is usually defined by the COM file which you call to spawn and create the editor. o When you attach to the kept editor process, it should translate the logical name EDIT_NEW_FILE to get the filename of the new file to edit. FLIST will define this logical in the JOB table. Note that a simple TPU `file_parse' or `file_search' statement can translate the logical for you. o Optionally, it may translate the logical name EDIT_NEW_DEFAULT which FLIST sets as the current default directory. Note that a TPU `file_parse' statement can translate the logical. The following keys are defined in FLIST for the kept editor: K - Attaches to kept editor. GOLD\K - Attaches to Kept editor to edit the file under cursor. M3 - (mouse button 3 when mouse is activated using "M") Pressing M3 down highlights the file under the mouse. Move the mouse off of the selected line and release to cancel or release with the mouse still on the selected line to attach to the kept editor with the selected file. Tree ~~~~ A directory tree is displayed by pressing GOLD\T while in the directory/file list. Pressing GOLD\T will display the Tree and position the cursor on the current default directory. The movement keys are then defined to let you move around as well as: exits back to the directory/file list V or M2 select directory under cursor and redo directory/file list (The mouse works again as describe above, move and release to cancel the selection) L position cursor on current default directory GOLD\T redo the TREE (if newer directories were created) The Tree is only built the first time you invoke it. Pressing GOLD\T in the directory/file list afterwards simply put you back into the existing Tree with the cursor on the current default directory. Pressing GOLD\T again once in the Tree re-builds it. CD ~~ CD replaces the DCL "SET DEFAULT" command with a shorthand that permits the use of abbreviations for each directory name. It also allows the use of UNIX style directory separators (/). It automatically pops-up the directory tree if it cannot not find the search list below the current default (see examples). Normal_Use CD F.SE ==> SET DEF [F*.SE*] where F and SE are abbreviations Page 4 to directory names. If the directory is not found below, then the search starts above. All directories are validated. CD F/SE ==> UNIX style directory separators can be used. Features - supported prefixed tokens: CD \ ==> Goes to SYS$LOGIN. CD ~ ==> Goes to SYS$LOGIN (UNIX style) CD \SUBDIR ==> Goes to SYS$LOGIN and then searches for SUBDIR*.DIR CD .. ==> Pops-up one level (equivalent to SET DEF [-]). CD $DISK: ==> Forces "SET DEF DISK:" without validation. The use of logical names can be made preceded by "$". Examples o You may put any number of prefix token before the abbreviated search list: CD .... will pop twice. CD \.. will go to SYS$LOGIN and then pop. CD \..A.B will go to SYS$LOGIN, pop and search for [.A*.B*] o SYS$LOGIN Asuming the default directory is \ [.FORTRAN.PROJECT] FORTRAN / \ $ CD T will go to TEST below. CODE PROJECT $ CD C will go to CODE because \ nothing that starts with TEST C is found below PROJECT so that it will move up to FORTRAN and look again and find CODE. $ CD \F.C will again go to CODE o Current default is: DISK4:[GALBRTH.UTILITY.COM_FILES.EVE.BETA.POSITION] CD T.K.C will search for: (*) DISK4:[GALBRTH.UTILITY.COM_FILES.EVE.BETA.POSITION.T*.K*.C*] will not find a directory, will search for: DISK4:[GALBRTH.UTILITY.COM_FILES.EVE.BETA.T*.K*.C*] will not find a directory, will search for: DISK4:[GALBRTH.UTILITY.COM_FILES.EVE.T*.K*.C*] will not find a directory, will search for: DISK4:[GALBRTH.UTILITY.COM_FILES.T*.K*.C*] will not find a directory, will search for: DISK4:[GALBRTH.UTILITY.T*.K*.C*] and will find: DISK4:[GALBRTH.UTILITY.TEX.KATIA.CV] (*) Note that CD will actually skip this level and pop because it knows the directory can only be 8 levels deep. ========> [VAX91A.IUPOP3]AAAREADME.TXT;1 <======== The IUPOP3 server is a VMS implementation of the Post Office Protocol Version 3, based on RFC 1081 and somewhat on Berkeley's popper. There are many differences between IUPOP3 and the popper, partly due to the differences between VMS and UNIX as operating systems. Probably the most notable difference is that IUPOP3 is a static multithreaded server. The server always listens on the network port for new connections, and can handle up to 31 simultaneous POP3 client connections. In this way, expensive VMS process creation overhead can be avoided. Note that this does not mean that IUPOP3 can serve only 31 clients; indeed, at IU it serves dozens. The limitation is 31 concurrent connections from POP3 clients at any given moment in time. IUPOP3 was developed and tested on VMS 5.3 and 5.4 systems, using the VMS callable mail (MAIL$) interface. The current release is compatible with the following TCP/IP network implementations: Wollongong WIN/TCP for VMS, DEC's UCX, and TGV's Multinet. ========> [VAX91A.JBAKER]AAAREADME.TXT;1 <======== The following are a list of subdirectories and a short description of what is contained in each. Some changes may be required due to the location of files and related routines. Hopefully any of these can be done with the least amount of effort. All higher level programs are documented internally to help any user that may want to modify any of the code. If a user does modify any code so that it works better I would appreciate a copy. The use of any of these programs is free to any user and is not to be sold as is or under any other form. [.CONFIRM] - A login message to display to users that is to be confirmed as to have been read. Keeps those users that are known to say "WELL NOBODY EVER TOLD ME" very quiet. Some security patches have been added. [.DISKINFO] - Short program that displays used and free disk space along with percentages. [.LAST] - Utility that tells when and how long ago a user logged in. If the user has never logged in, the program will provide the creation date to the users default login directory assuming that this was created at the same time as the account itself. [.LIST] - The new version of LIST is version 2.0, a total rewrite. A phone book type utility using indexed files. Users are capable to changing their own information. [.VERSION] - A utility that displays the current version of software whether it be personal files, layered products or the version of the operating system (NOT THE FILE NAME VERSION). This does not require the SYSTEM MANAGER to update any files. There have been a few changes to the previous version of VERSION. I think you will really like this one. Things coming: [.TERMINALS] - A terminal statistic package that handles virtual terminals, multiple terminal server sessions and much, much more. I was hoping to have this done, however, other projects were deemed mission critical due to DESERT STORM. The package will dislpay a statistical table of logins (i.e. total logins, total time in minutes, longest login, shortest login, average login, and an optional location field). The other display will be a map of times in 15 minute increments indicating what times in the day a particual terminal was in use. There have been many unexpected results from the current status of the project, so before this one goes out, I hope to address every possible problem that could taint the accuracy of the statistics. I do not expect this project to be completed until the next DECUS. Page 2 If there are any questions or problems contact: JONATHAN C. BAKER NAVAL SURFACE WARFARE CENTER CODE N23 DAHLGREN, VA 22448 (703)663-8705 ========> [VAX91A.JSCMSD]AAAREADME.TXT;1 <======== Programs Developed for the NASA JSC Medical Sciences Division. Developed by Loral Space Information Systems Division, Loral Aerospace Corp. ADDASYS.DIR A/D, D/A VSL Control Programs (for AXV11, KWV11) JESCOM.DIR Setup environment for creating distribution list, and defines eligibility for access to remote Message Router Gateways (X.400 & SoftSwitch). UTILS.DIR SetUser Program, Fast Symbol Definition MAILUTIL.DIR Program to show NEW Mail Count for local or remote users. Update includes trusted node verification procedure. Uses VMS Mail Calls. REMMAIL.DIR VMS Mail Callable Interface Programs (Read, Send, & Gateway Functions) Posted as an example of how to use Callable Interface. Also provides a sharable image which provides simpler interface to the VMS Mail Calls. USERDB.DIR User Database Interface Programs, example of how to build and code a simple database. DEVELOP.DIR Support Files for REMMAIL & USERDB programs. ========> [VAX91A.MCMAHON]AAAREADME.TXT;1 <======== [.cant_open_display] This directory tree contains various pieces of code described in session GR032 "Can't Open Display: Debugging X Transport Problems" at the DECUS 1991 Spring Symposium. Subdirectory [.CHECK_SERVER] This contains the CHECK_SERVER test program. This program simulates an X windows connection (TCP/IP) between a client and server. This simulation can locate many X transport errors. Subdirectory [.DGHBN] This contains a DCL interface to the GETHOSTBYNAME() Berkeley Socket Routine. Subdirectory [.DOCS] SYMBOL_DOC.TXT - Information on the undocumented SHOW DISPLAY/SYMBOL command. WS_DOC.TXT - Information on using the $QIO interface to WSDRIVER. Subdirectory [.LIST_HOSTS] This contains a simple utility to dump an X windows server security database. Subdirectory [.SEARCH_BG] The utility in here scans all the BG and WS devices on the system. It is good for locating who is currently using X windows, and if your server has established a connection to the TCP/IP network. Subdirectory [.SYNTAX_CHECKER] The utility in here performs simple syntax checking on a SET DISPLAY command. John McMahon TGV, Incorporated 603 Mission Street Santa Cruz, CA 95060 Work: (408) 427-4366 E-Mail: MCMAHON@TGV.COM DCS: MCMAHON (MCMAHON@TOPAZ.DECUS.ORG) [.whois_client] This directory contains the C source code for an Internet WHOIS Client. The program is part of session NE060 "WHOIS: A Warehouse of Internet Knowledge" at the DECUS 1991 Spring Symposium. The code is written to support wither SunOS, ULTRIX or VMS running MultiNet. it should be pretty easy to modify to other TCP/IP systems. See the code for building and linking instructions. John McMahon TGV, Incorporated Page 2 603 Mission Street Santa Cruz, CA 95060 Work: (408) 427-4366 E-Mail: MCMAHON@TGV.COM DCS: MCMAHON (MCMAHON@TOPAZ.DECUS.ORG) ========> [VAX91A.NEWS60]AAAREADME.TXT;2 <======== This area contains the latest versions of ANU NEWS (currently V6.0-3) with other files containing important patches to these. It is suggested that the patches be applied before installation if a C compiler is available. The complete distributions are supplied as obtained from Geoff Huston, author. To facilitate patching, I have included the file NEWS603PATCHED.LZH, an LHARC archive of the sources already patched with the Bill Glass patches etc. as of about 5/10/1991. The news.exe file in the lharc file is of that vintage also, as is news.hlb. After extracting news.exe and news.hlb you will want to use FILE to reset them as follows: $file/attr=noimpliedcc/type=fixed/record=512 news.hlb $file/attr=noimpliedcc/type=fixed/record=512 news.exe The sources are OK as is, but should be moved into the [.news_Src] area to rebuild NEWS. The original Geoff Huston distribution is untouched and exactly as I received it. Glenn Everhart VAX SIG tape librarian ========> [VAX91A.NSWC]AAAREADME.TXT;1 <======== SPRING 1991 DECUS VAX SIG TAPE SUBMISSIONS FROM DAHLGREN VAX LUG Naval Surface Warfare Center Dahlgren, Virginia 22448 For each submission, all of the sources are present. The sources, and other files necessary to build the products from their sources, are compressed. See SOURCES.0README for more information. Most of the programs are written in Fortran, and require object library NXXXLIB (whose sources are also present) to link. Each product has a command procedure (named product.BUILD) to build the product from sources. Several of the programs require some site-specific configuring, often edit- ing a .CLD file. I believe everything should work without tinkering if you set your default directory to this directory, and define logical name HERE to be this directory. I. Submissions from Alan Zirkle, NSWC Code K55 (703) 663-8023 Dahlgren, VA 22448 SD -- SET/SHOW DEFAULT -- This version of SD is related to Dale Coy's excellent version, in that they both descend from a common ancestor. This incorporates his features, plus several new ones. Read SD.0README and SD.HLP for further information. LET -- Related to SD. A shorthand DEFINE command for defining logical names. Read LET.HLP for more information. To use, first execute the command $ LET == "$dev:[dir]LET". SDDRAW -- Related to SD. Creates a file containing the structure diagram of a directory tree, like SD * displays on the screen. Has options for different printers (the /X9700 option, for Xerox 9700, will not be useful to anybody except as a guide for how to add support for your own unique printer). MODIFY -- Performs string replacement in a wild-card group of files. Has many features not found in the version in the DECUS VMS Startup Set. Read MODIFY.HLP for more information. To use, first execute the command $ SET COMMAND MODIFY. REFORMAT -- Copies a file, optionally performing many types of conver- sions in the process. Read REFORMAT.HLP for more info. To use, first execute the command $ SET COMMAND REFORMAT. SPCOPY -- Copies or prints a file, performing either or both of the following conversions: transforms all non-printable char- acters to printable mnemonics (ESC -> ""), and divides the file into pages with page headings. Read SPCOPY.HLP for more information. To use, first execute the command $ SET COMMAND SPCOPY. Page 2 TP_LOGIN -- Two-person login; a program to go in SYLOGIN.COM to enforce a "two-man rule"; login cannot complete until a second user enters a valid username/password. More general than the SYSUAF Secondary Password feature, and site-tailorable. See TP_LOGIN.TXT. XDCL -- Saves/restores the DCL Command Recall buffer. Read XDCL.HLP for more information. To use, first execute the command $ SET COMMAND XDCL. FDIFF -- Generates a report showing the differences, over time, of the contents of a directory structure. FDIFF shows the names of files which have been deleted, added, or modified since the last time FDIFF was run on the directory structure. Has an exclusion list. Includes example for monitoring a System Disk. See FDIFF.HLP and FDIFF.CLD for more information. To use, first execute $ SET COMMAND FDIFF. The example is FDIFF_SYSTEM_DISK.*. SYSMSG -- Utility called from SYLOGIN.COM for interactive users to dis- play system messages. Allows scrolling if the messages are longer than one screen. Requires user response to continue; nobody can use the excuse that the message scrolled by too fast. User can supress already-read messages. SYSMSG.HLP has more info. To use, first execute $ SET COMMAND SYSMSG. VGRAPH -- A very, very simple viewgraph producer for PrintServer 20 and 40 printers. Uses PostScript. Read VGRAPH.HLP for more information. To use, first execute $ SET COMMAND VGRAPH. Two sample input files *.VIEW are included. Program may require tailoring to conform to your print queues. NXXXLIB -- Subroutine library needed to link the above programs. Many of the routines may be useful to you in other applications. The library and its sources are in the compressed sources file; see SOURCES.0README for more information. II. Submissions from Jay Jenkins, SYNETICS (703) 663-7634 24 Danube Drive King George, VA 22485 The sources are compressed; read SOURCES.0README. CPQ -- (Check Print Queues) Background process to check print queues for STOPPED, STALLED, or PAUSED status. We use for notification of serial printer problems. SYSDSK_MON - (System Disk Monitor) Monitors space on the system disk and sends message to console when free block percentage falls too low. UPTIME -- Command procedure to display the time since booting of nodes on a VAXcluster. Page 3 CHKUSR -- Checks a specified user to see if they are enabled or not. Useful for checking status of FIELD and other such accounts, and to quickly check when users complain that they can not log in. DDT -- (Display Disk Transactions) Gives an SMG generated display of disk transaction on the current node. SESSIONS -- Contains SESSIONS which displays the # of interactive and batch sessions a user has on a cluster. Privileged users may check status of other users. Also contains SSESSIONS, for enforcing single sessions for users having the restric- ted flag set; prevents multiple logins. These files are in subdirectory [.SESSIONS]; you must edit the .CLD file. SPACE -- Gives an SMG generated display of disk free space, total space, error count, plus much more. You can specify the disks to include on the command line, which is nice for sites without FORTRAN compiler. REGIS -- Contains three files that can be TYPEd on REGIS terminals. ENDFILE -- Useful for quick-checking logs where the only thing you are worried about is the last few lines where the final status is displayed. BELL -- Rings the terminal bell without destroying the screen. Used for letting you know when a lengthy process has completed. PIC -- Terminal pictures; TYPE them. Some require a REGIS terminal. ========> [VAX91A.PAVLIN]AAAREADME.TXT;1 <======== [.ethermon] ETHERMON is a software implementation of an Ethernet line activity monitor. It uses any VAX/VMS DEC-compatible Ethernet interface to collect the data, and reports statistics in a form similar to the VMS MONITOR utility. It also can collect Ethernet data for post-processing by a user-supplied offline program (sample programs are supplied). ETHERMON can determine symbolic identifications of remote nodes automatically, or have them defined manually; these symbolic identifications are used in ETHERMON's displays and reports. ETHERMON can also recognize equipment other than DEC's on the Ethernet. ETHERMON.COM is the build file; the documentation is stored in the files ETHERMON.PS (PostScript), ETHERMON.LN0 (DEC LN03), ETHERMON.LPT ("dumb" line printer or plain-text), and ETHERMON.MSS (Scribe manuscript source). The [.spell] directory is a variant of the Vassar Spelling Corrector. At our site, it was discovered a number of incorrect words had been placed in the dictionary. The code and dictionaries here have been corrected. The documentation is the same as older releases of the spelling corrector however and is not complete here. [.mtacc] MTACC is a simple replacement for the VMS V5.x SYS$MTACCESS system service. Its initial reason for creation was to get around the "feature" in HSC BACKUP where an unfriendly accessibility code was written in the VOL1 label on the tape, making the tape unmountable by VMS BACKUP. Sure, you could mount the first reel with /OVERRIDE=ACCESSIBILITY, but BACKUP won't do that when it mounts the 2nd through Nth reels. To get around this problem, this version of $MTACCESS allows dynamically ignoring any accessibility field constraints, using the SYSGEN dynamic parameter USERD1 to control whether or not the access control bypass is enabled or not (this allows the system managers to turn off the override after they are done with it, without having to reboot the system). Obviously, this could be extended to grant this override automatically to someone holding a certain identifier or privilege rather than permitting everyone in the world to bypass accessibility controls, but, since our shop doesn't use any sort of complicated tape control, it wasn't necessary to do anything complication to get the job done (hence the quick-and-dirty approach). Note that this program was built by using SYS$EXAMPLES:DOD_ERAPAT as a template and replacing the SYS$ERAPAT code with code analyzed from the original running $MTACCESS service. Feel free to extend this simple hack any way you like. Enjoy! Andrew Pavlin General Electric Co. Ocean & Radar Systems Department Syracuse, NY 13221 phone: (310 456-1875 email: pavlin@syr.ge.com [.SNMPsnop] SNMPSNOOP is a quick-and-dirty little program for dumping everything a remote Internet node knows in its SNMP database to your system in Page 2 (supposedly) human-readable format. It is written in C, and will theoretically run under DEC UCX and VAX C (has not been tested); it has been tested to work under TGV MultiNet after compilation with Gnu C. and with the standard Sun cc compiler under SunOS 4.1. Note that under MultiNet, it is possible to "hang" the program if a response packet gets lost in the Internet (the MultiNet socket library does not support the BSD select call, so a timed-out wait for the response message cannot be done). The program is invoked as a DCL foreign command. Once it is started, it reads one or two parameters from the command line; the first (required) is the target host to interrogate (either numeric or symbolic host address), the second (optional) is the SNMP community name to use for the query (defaults to "public"). The program then connects to the local Internet software (the linker options file needed for VAX/VMS only is set up for TGV MultiNet) for a UDP connection, then starts sending SNMP GetNextReq packets to the specified remote host and waiting for the replies. The replies are formatted and displayed on standard output. The program continues to query until a timeout occurs (except under MultiNet) or until an error is returned (generally indicating no more SNMP object ID's known to this agent). The utility is built in one of three ways: 1) with TGV MultiNet: $ [g]CC/DEFINE=MULTINET SNMPSNOOP.C $ LINK SNMPSNOOP/OPTIONS 2) with DEC UCX: $ [g]CC SNMPSNOOP.C $ LINK/EXE=SNMPSNOOP SYS$INPUT:/OPTIONS SNMPSNOOP,SYS$SHARE:VAXCRTL/SHAREABLE 3) under SunOS: % cc snmpsnoop.c % mv a.out snmpsnoop 4) presumably, under Ultrix (untested): % cc -Dsun snmpsnoop.c % mv a.out snmpsnoop After compiling and linking under VMS, a foreign command must be defined: $ SNMPSNOOP :== $disk:[dir]SNMPSNOOP Under any of the operating systems, the utility is then invoked as: $ SNMPSNOOP target [community-name] % snmpsnoop target {community-name} This little utility is nice for testing what SNMP capability you have in your hosts before spending oodles of money on an SNMP-based network management console, and just general debugging. Beware though: some hosts can be VERY verbose in the quantities of replies they send back! Page 3 Andrew Pavlin Ocean & Radar Systems Department General Electric Co. Syracuse, NY 13221 phone: (315) 456-1875 enail: pavlin@syr.ge.com ========> [VAX91A.PEDERSON]AAAREADME.TXT;1 <======== Thank you for obtaining KPYG-I Graphics Application. Please feel free to distribute this to friends and associates. KPYG-I is unique in its ability to provide true bitmap style graphics on VT-220s, VT-320s, VT-420s and compatibles. ReGIS compatible terminals are also supported. If you use this program please register to support its continued development and support. This software is distributed in a .TLB format with command procedures to extract the distribution and then as a VMSINSTAL compatible save set (KPYGI020.A). Use the following commands to install the software: LIB/EXTRACT=XTR^COM/OUT=XTR.COM KPYG1.TLB @XTR This will extract all of the files from the .TLB container file. Then to install type: @SYS$UPDATE:VMSINSTAL Eventually you will be asked to specify the location of the distribution, specify the device and directory where you unloaded the .TLB container file. For this installation to be successful you must be logged into a privileged account on VAX/VMS. If there are questions please contact: KPY Corporation 175 West Whittier Avenue Ben Lomond, CA 95005-9503 408/336/2708 ========> [VAX91A.PENNER]AAAREADME.TXT;1 <======== This submission is from G. D. Searle & Co. It includes: Header a program to list the number of free headers on a given disk. Show_spool a program to show which queue a terminal is spooled to Who_use_gblsec a program to show which processes are using a given global section Frank Penner G. D. Searle & Co. 4901 Searle Parkway Skokie, IL 60077 (708) 982-8231 ========> [VAX91A.PERLUNIX]AAAREADME.TXT;2 <======== This area contains a TAR file of the last known-stable release of PERL, a pattern matching utility used in unix. (note that a later release exists in the [.gnusoftware] area.) This version matches most of the books on PERL and is quite stable, while the V4 release is still somewhat less so. Submitted by Kurt Reisler, Hadron Corp. ========> [VAX91A.PROPRESS]AAAREADME.TXT;1 <======== This directory has code to programs that have been published in the VAX Professional Magazine over the past couple of years. It was furnished to the VAX/L&T Sig tapes by Professional Press as a courtesy. It also serves to a degree to show the sorts of information available in that magazine. Note: Before running privileged code found herein, it is up to you to make sure it can run correctly on the version of VMS you have; since the material is sometimes a couple years old, this should be kept in mind. TAPE CONTENTS: Targeting An AST To Another Process Filename: ASTPROC.DOC This files features code previously published in the August 1989 issue of VAX Professional magazine in an article written by Arthur R. Townsend titled, "Targeting An AST To Another Process." The article appears on page 7. The featured program demonstrates techniques required to queue an AST that issues the SET VERIFY commands for another interactive process. ARIS: "Protalk" column, August 1990 VAX Pro Filename: AUG_TALK.DOC "Protalk" column, August 1990 VAX Professional, Volume 12 #4. Page 4. ARIS Name: Aug_talk.doc TREE.COM, by Richard Whyte. A short DCL routine to allow a VMS user or manager to see the logical directory layout from a given directory. MRGATETEST.COM (The code for MAILX.COM; the text files MRGATE.TEST, MRGATE- FAIL.TXT, MRMANDOWN.TXT; and a sample ACL). Detects network trouble, message router failure or remote node crash. Print Barcodes On Your LN03 Filename: BARCODE.DOC This file contains a program written by Dennis Peipel that uses sixel graphics to allow your DEC printer to print barcodes. It was first published in the October 1989 issue of VAX Professional magazine, in an article titled "Print Barcodes On Your LN03." The article appears on page 11. Bit Flags In VAX BASIC Filename: BITFLAGS.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine. It was originally published as part of an article by Bradley R. Sheppard and Larry McCurdy titled, "Bit Flags In VAX BASIC." The article appears on page 34. The program is an example of how to use bit flags. Bucket Splitting In Indexed Files Filename: BUKTSPLIT.DOC This file contains a program previously published in the December 1989 issue of VAX Professional magazine. It was first published as part of Greg Dumbrell's article, "Bucket Splitting In Indexed Files" which appeared on page 19. The program gives a quantative guide to the amount of fragmentation in a file and indicates when the agony of a reorganization is required. It's for reorganizing RMS indexed files. Software Layering Filename: BLDIMAGE.DOC Page 2 This file features a program that was published in the June 1989 issue of VAX Professional magazine. It was originally published as part of Philip A. Naecker's article, "Software Layering" which appeared on page 23. The program BUILD_SHAREABLE_IMAGE.DOC compiles, links and installs the XYZ shareable image.. The macro routine defines the transfer vectors for the XYZ shareable image. The linker options file uses many features of the VMS LINKER. It's About Time Filename: CALENDAR.DOC This file features code previously published in the April 1990 issue of VAX Professional magazine. It was written as part of Donald W. Czerwinski's article "It's About Time," which appears on page 18. The program, "Julianday," converts an integer Julian Day into its Gregorian Calendar equivalent date, in the form: 01-jan-1989. The VAX clock assumes that the Smithsonian Astronomical Date, November 17, 1858, is Julian Day 1. Hierarchy: Procedure To Generate A Call Hierarchy Filename: CALLHIER.DOC This file features code previously published in the April 1989 issue of VAX Professional magazine. The program, originally titled CALLHIER.DOC, reads a list of object files and generates a call hierarchy for those files. It was originally published as part of Darren C. Abbott's article, "Hierarchy: A Procedure To Generate A Call Hierarchy" which appeared on page 27. Calling Routines In Other Languages From VAX C Filename: CALLVAXC.DOC This file features a program previously published in the June 1990 issue of VAX Professional magazine. The program was written by Rod Stephens as part of his article, "Calling Routines Written In Other Languages From VAX C." The article appeared on page 21. The program, "INCOME.C," shows a tricky solution to the pitfalls that can occur when you try to call a program written in another language from your C program. X Views: Plotting Capacity Data Filename: CAPACITY.DOC This file features code previously published in the December 1990 issue of VAX Professional magazine. It was originally published in David W. Bynon's article "X Views: Plotting Capacity Data," which appeared on page 31. The author takes the opportunity to show you how to plot a graph using system performance data collected through the MONITOR utility. Renumbering MACRO Local Labels Filename: CLEANUP.DOC This file features code previously published in the February 1990 issue of VAX Professional magazine. It was written by Hunter Goatley as part of his article, "Renumbering MACRO Local Labels" which appeared on page 31. The prgram segment presented here could become invaluable to VAX MACRO programmers. A Corner Clock For Your VT Terminal Filename: CLOCK.DOC Page 3 This file features a procedure previously published in the December 1989 issue of VAX Professional magazine. It was written by Al Beer and included in his article, "A Corner Clock For Your VT Terminal," which appeared on page 28. The procedure displays a clock in the upper right corner of your VT100 and, by subprocesses, updates the data/time every three seconds. But it scrolls down when you use the editor and contains other limitations. COM_ARGS Filename: COM_ARGS.DOC This file features code previously published in the June 1989 issue of VAX Professional magazine. The article, written by Richard Steinberger, appears on page 19. Titled "COM_ARGS," it details a simple way for FORTRAN programs to retrieve command line arguments. Easy Command Recall Filename: COMRECALL.DOC This file features a procedure written by Hunter Goatley which implements an easy-to-call interface to the SMG$ routines to provide command recall when reading from SYS$INPUT. Previously published in the February 1989 issue of VAX Professional magazine as part of his article titled, "Easy Command Recall," the procedure takes the same arguments as LIB$GET_INPUT and may be substituted directly in any call to LIB$GET_INPUT. Put The Power Of DCL Into Your Programs Filename: DCLPOWER.DOC This file features code previously published in the August 1989 issue of VAX Professional magazine, in an article by Charles A. Measday titled, "Put The Power Of DCL Into Your Programs." The code here presents an easy, effective way to issue a DCL command to the operating system within a program by spawning a CLI subprocess and connecting its SYS$INPUT and SYS$OUTPUT channels to mailboxes that you can read and write. Measday's article appears on page 21. View And Select With A TPU Directory Editor Filename: DIRED.DOC This file features a routine previously published in the October 1989 issue of VAX Professional magazine. The routine was initially part of Nicholas Aiuto's article, "View And Select With A TPU Directory Editor," which appeared on page 18. The routine allows you to view a list of files in a directory and select one for editing. This utility allows directory viewing, directory tree movement, and file selection, all from one buffer in any TPU-based editor. MODL, The Manager For Organized Distribution Lists Filename: DISLIST.DOC This file features code previously published in the February 1990 issue of VAX Professional magazine. The article, written by Paul G. Anagnostopoulos titled, "MODL, The Manager For Organized Distribution Lists," appears on page 11. MAIL distribution lists eliminate the need to type the same user names over and over, but can become cumbersome and redundant to update. This facility solves these problems by providing centralized distribution lists. Page 4 Dynamic Priority Adjustment Filename: DPA.DOC This file features code previously published in the December 1990 issue of VAX Professional magazine. It was taken from an article by Dennis Leiterman titled, "Dynamic Priority Adjustment," which appeared on page 21. The FORTRAN procedure here improves system performance by allocating system resources. It lowers the base priority of CPU-hogging interactive processes. When finished, the processes revert to normal priority. Dynamic System Monitor: VMS Priority Scheduling Filename: DSM.DOC This file features a program written by James G. Miserere, taken from his article "DYNAMIC SYSTEM MONITOR: Supplements VMS Priority Scheduling," which appeared in the February 1990 issue of VAX Professional magazine on page 21. The article represents the runner up in VAX Professional's Call For Papers on performance. The program tracks CPU use of user processes and adjusts their base priority to ensure that lower priority levels get CPU service. Dynamic Array Expansion Using VAX FORTRAN Filename: DYNARRAY.DOC This file contains code previously published in the December 1990 issue of VAX Professional magazine. It was originally part of Duane L. Violett's article, "Dynamic Array Expansion Using VAX FORTRAN," which appeared on page 17. The procedure here enables your FORTRAN memory allocation to expand or contract without requiring you to edit the source code each time the size of the allocation changes. Emulating EMACS With TPU Filename: EMACSTPU.DOC This file features a program previously published in the August 1990 issue of VAX Professional magazine. Written by Norman E. Smith, the program was published as part of the article, "Emulating EMACS With TPU," which appeared on page 22. The EMACS text editor provides mnemonic commands and split-screen editing. This home-grown editor, TEMACS, gives you most of the features of EMACS in TPU. Clear Device Error Counts Without Rebooting Filename: ERRCLEAR.DOC This file features code written by Jeff Jancula, taken from his October 1989 VAX Professional article "Clear Device Error Counts Without Rebooting." The article appeared on page 16. Under certain conditions, you might want to reset error counters to zero. RESET_ERRORS.MAR will reset errors on demand. This one carries a warning, however; use it with caution to avoid damage to your system. The Extended LOGIN Program Filename: EXTLOGIN.DOC This file contains code previously published in the April 1989 issue of VAX Professional magazine. It was originally part an of article written by Hunter Goatley titled, "The Extended LOGIN Program." The article can be found on page 10. This program was written to be called from a LOGIN.COM to define logicals, global symbols, and do other things at LOGIN. It is Page 5 substantially faster than a DCL command procedure that does the same things. Who's On The System And What's He Doing? Filename: FASU.DOC dThis file features a program that was published in the June 1990 issue of VAX Professional magazine. It was originally published as part of the article, "Who's On The System And What's He Doing?" which appeared on page 34. The article and code were written by Adri Koopman. Want to know what users are logged on and their activities? this FORTRAN procedure uses a DCL command to monitor user activity. It could be just what you need. F$USEFUL Redux Filename: FILATTRIB.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine. It was taken from the article, "F$USEFUL Redux," written by Donald R. Stevens-Rayburn. The article appears on page 13 and addresses calling DCL lexical functions from FORTRAN. The Hitchhiker's Guide To VMS: Part II (V5.1) Filename: HIKER.DOC This file features code previously published in the October 1989 issue of VAX Professional magazine. Written by Bruce Ellis and published in his series, "The Hitchhiker's Guide To VMS," the code appears in Part II which ran on page 39. In this episode, "The Guide explores the uses of ASTs to reclaim memory from an idle process." The Hitchhiker's Guide To VMS: Part III Filename: HIKERIII.DOC This file features code previously published in "The Hitchhiker's Guide To VMS: Part III," which ran in the February 1990 issue of VAX Professional magazine. Written by Bruce Ellis, Part III appears on page 39. In it, "The Guide uses the System Dump Analyzer (SDA) to locate and fix code broken by version 5.2 changes." The Hitchhiker's Guide To VMS: Part IV Filename: HIKER4.DOC This file features code published in the April 1990 issue of VAX Professional magazine. It was first run as part of Bruce Ellis' "The Hitchhiker's Guide To VMS: Part IV" article, which appeared on page 37. In Part IV of the series, "The Guide helps Billy solve problems with global sections and his love life." This program receives a section name and locates all sections named "name_" and displays the share counts for all pages mapped by the section. The Hitchhiker's Guide To VMS: Part V Filename: HIKER5.DOC This file features code previously published in the June 1990 issue of VAX Professional magazine, in Bruce Ellis' "The Hitchhiker's Guide To VMS: Part V," which ran on page 41. In part V, we learn: "Who's the white-haired man and what does he want? How many nights will it take Billy to adjust the quotas affecting the automatic working set adjustment?" The Hitchhiker's Guide To VMS: Episode 6.1 Page 6 Filename: HIKER6-1.DOC This file features code previously published in VAX Professional magazine. It was first run on page 39 of the August 1990 issue, as part of Bruce Ellis' "The Hitchhiker's Guide To VMS: Episode 6.1" In this episode we learn, "Is Dr. Albino for real? Does Billy Bitsenbites remain happy to operate under a legitimate set of priveleges? The code here sets bits in rab for proper locking on read with 10 second wait before error status is returned. The Hitchhiker's Guide To VMS: Episode 6.2 Filename: HIKER6-2.DOC This file features a program written by Bruce Ellis. It was previously published in the October 1990 issue of VAX Professional magazine in his series, "The Hitchhiker's Guide To VMS" in Episode 6.2, which appears on page 36. In episode 6.2, "Does Billy find the keys to unlock the mysteries of VMS? Does he figure out what to do when he's locked out of a process? Does he figure out what file to access when he's being blocked?" The Hitchhiker's Guide To VMS: Part II (V5.2) Filename: HIKERV52.DOC This file contains code previously published in the October 1989 issue of VAX Professional magazine, in Bruce Ellis' "The Hitchhiker's Guide To VMS: Part II," which appeared on page 39. In Part II, The Guide explores the use of ASTs to reclaim memory from an idle process. The program, WSBLASTER, takes a process id as input and adjusts the associated process working set down to 250 pages. LNMFILL: Logical Name Hash Table Statistics Filename: HASHTABLE.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine. It was first published as part of Lee K. Gleason's article "LNMFILL: Logical Name Hash Table Statistics," which appeared on page 4. This program will locate the systemwide shared, and the process-wide logical name hash tables. It will traverse the linked lists of their entries, and report the number of entries and the length of their lists. Shareable Image Libraries Filename: IMAGELIB.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine. The code, written by Alan MacArthur and published as part of his article, "Shareable Image Libraries: A Tool For Enhanced Structural Project Development At The User Level," which appears on page 27, represents a collection of subroutines and functions. FORTRAN Input Functions Filename: INPUT.DOC This file contains program segments perviously published in the December 1990 issue of VAX Professional magazine. Written by Kristopher Arenius for his article, "FORTRAN Input Functions," which appears on page 29, the four home - grown functions features here simplify VAX FORTRAN terminal input. Using LAT To Integrate Incompatible Systems Page 7 Filename: INTEGRATE.DOC This file features code previously published in the June 1990 issue of VAX Professional magazine. Written by David W. Bynon for his article, "Using LAT To Integrate Incompatible Systems," the code can be found on page 31. Users in a distributed VAX environment want to connect to a Unisys system from their office terminals, and they want documents to print on the printers in their office. Impossible without a network solution? Try this: VMS Kernels: $SNDJBC To Print Files Filename: KERNEL1.DOC This file features code published in the June 1990 issue of VAX Professional magazine. Originally run as part of Tracy E. Schreiber's article "VMS Kernels: $SNDJBC To Print Files," which appears on page 38, the routine is an example of how to use SYS$SNDJBC to print a single file. Rather than using LIB$SPAWN to print files from within a program, try using $SNDJBC. This article describes why using the system service is better than spawning a subprocess. X Views: Using the DECtoolkit to Create Widgets Filename: KITWINDOW.DOC This file features program segments previously published in the December 1989 issue of VAX Professional magazine. Written by David W. Bynon, the code here was first run as part of Bynon's article, "X Views: Using the DECtoolkit to Create Windows and Widgets," which appeared on page 43. From the article: Here's a complete explanation of widgets, what they are, how they work, and how to use them to create a modeless interface through the CALLBACK facility. VAX Knots: December 1989, Volume 11 # 6 Filename: KNOTS.DOC This file features VAX Knots excerpted from Bruce Ellis' VAX Knots column which ran in the December 1989 issue of VAX Professional magazine. Test your VAX/VMS skills. See how you measure up. No, you won't be graded, but you'll get the proverbial A for effort. The answer to this appears on page 42 of the December 1989 issue. VAX Knots appears on page 5. Three Utilities To Print PC-to-VAX Graphics Filename: LNO3GRAPH.DOC This file features code published in the April 1989 issue of VAX Professional. The code here was originally run as part of Gerardo Hugo Fisanotti's article, "Three Utilities To Print PC-to-VAX Graphics," which appeared on page 39. Program 1 converts AutoCAD's slide (.SLD) file to Tektronix 4010 mode files. Program 2 features procedures to draw vectors in Tektronix 4010/4014 mode. Program 3 converts HP Laser Jet mode files to sixel mode for LNO3+. A Whirlwind Tour Of VMS MAIL Filename: MAILTOUR.DOC This file features code previously published in the February 1990 issue of VAX Professional magazine. Originally run as part of Kevin Carosso and Fred Freed's article, "A Whirlwind Tour of VMS Mail," which appears on page 6, the article serves as an introduction to complex MAIL. On a higher level, VMS mail offers three hidden interfaces to add message management, routing Page 8 and delivery capabilities. Using Memory Management Routines Filename: MANAGEMEM.DOC This file features code written by Robert R. Horning that shows you how to use memory management routines for run-time allocation of I/O buffers, and to map a file of unknown size and share data in that file between processes. The code comes from Horning's article, "Using Memory Management Routines," which ran in the June 1990 issue of VAX Professional magazine on page 7. On VMS Kernel Mode Time Filename: MODETIME.DOC This file features code previously published in the August 1989 issue of VAX Professional magazine. Written by Bruce Ellis as part of his article, "On VMS Kernel Mode Time," which ran on page 15, this file gives you code for benchmarking the cost of soft faults on your machine when your bogged down with excessive kernel mode time. System Programming Without Priveleges Filename: NOPRIV.DOC This file features code previously published on page 14 of the December 1989 issue of VAX Professional magazine. Originally run as part of Bruce Ellis' article, "System Programming Without Priveleges," the code here features descriptions of four different routines that provide information accessed from user mode to help you get started with system programming. A VAX FORTRAN Command Dispatcher Filename: OPENVIRO.DOC This file contains code previously published on page 26 of the October 1990 issue of VAX Professional magazine. Originally run as part of Alan MacArthur's article, "A VAX FORTRAN Command Dispatcher," the code here is a command dispatching program used to list information from the user authorization file for one or all users on the local system. You must be able to set BYPASS privelege to use this routine. Using The VAX Pseudo Disk Device With Confidence Filename: PDAORECV.DOC This file features code written by Arthur R. Townsend that allow you to create PDAO:, and in the event of a system crash, permit you to recover the data. The code was originally run as part of Townsend's article, "Using The VAX Pseudo Disk Device With Confidence," which appeared on page 16. A note of warning: Some configurations are insufficient for rebuilding PDAO: and you should test the recovery before trusting valuable data to it. X Views: Program With Pizzazz Using Pixmaps Filename: PIXMAPS.DOC This file features code previously published in the August 1990 issue of VAX Professional magazine. Originally run as part of David W. Bynon's article, "X Views: Program With Pizzazz Using Pixmaps," which appeared on page 31, the program here demonstrates the use of pixmaps and bitmaps by changing a window's standard background, cursor and icon. Page 9 Performance Analysis w/o Code Modification Filename: PROFILER.DOC This file features a program written by Matthew Rabuzzi, which was first run as part of his article, "Program Performance Analysis Without Code Modification," which appeared in the April 1990 issue of VAX Professional magazine on page 29 and took third place in VAX Professional's Call For Papers On Performance contest. This code analyzes where a program is most active, i.e., what modules are most active. VMS Print Queues Filename: PRINTQUE.DOC This file features code written by Bill Van Vechten. Originally run as part of his article, "VMS Print Queues," which appeared on page 34 of the April 1989 VAX Professional magazine, the program creates and maintains Device Control Libraries, another defines forms for printing (an example), another initializes print queues, and the fourth changes stock on selected printer queues. The article addressed hints for successful setup of print queues. VMS Privelege Masks Filename: PRIVMASK.DOC This file contains code written by Hunter Goatley. Originally run as part of his article, "VMS Privelege Masks," which appeared in the June 1989 issue of VAX Professional magazine on page 15, the code is provided to demonstrate a method for ensuring that a subprocess does not gain priveleges that an installed user owns. The article addresses methods for controlling priveleged tasks. Consistent Error Reporting Filename: REPORTERR.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine, in an article written by Stephen Hicks titled, "Consistent Error Reporting," which ran on page 44. The article, and the program segments, address making programming easier by using the MESSAGE facility. Accessing RFAs From VAX COBOL Filename: RFAACCESS.DOC This file features code previously published in the February 1989 issue of VAX Professional magazine. Originally run as part of Robert W. Dilworth, Jr.'s article, "Accessing RFAs From VAX COBOL," which appeared on page 39, the code here consists of four example programs for setting up and using MACRO interface subroutines. KFH_GRANTID Filename: RIGHTS.DOC This file features code written by Kevin F. Homan. The code first appeared in Homan's article, "KFH_GRANTID," which was published in the June 1989 issue of VAX Professional magazine on page 5. The article addressed a user-written system service to temporarily grant a rights identifier. The five routines here are detailed in the VAX Professional article. SCRIPT: A Unique Banner Printing Program Filename: SCRIPT.DOC Page 10 This file contains code previously published in the April 1989 issue of VAX Professional magazine. Originally run as part of John F. McGlinchey's article, "SCRIPT," which appeared on page 32, the code here prints banners on your line printer. It does it with style, in cursive. Use SCRIPT.COM to run SCRIPT and make sure you modify the PRINT line for the correct form type for blank paper on your system. SDA: Part III - The Ultimate Management Tool Filename: SDA3.DOC This file features code written by Hunter Goatley. It was originally run as part of his article, "SDA: Part III - The Ultimate Management Tool," which appeared in the December 1989 issue of VAX Professional magazine on page 38. Parts I and II served as introductory overviews to SDA and were run in the August 1989 and October 1989 issues of VAX Professional. Here we examine how SDA can be used to examine VMS code. Who Watches The Watchers? Filename: SPYBEAM.DOC This file features a procedure written by Lee K. Gleason. Originally run as part of his article, "Who Watches The Watchers?," which appeared in the April 1990 issue of VAX Professional magazine on page 7 and represents the winning entry in VAX Professional's Call For Papers on software security, the code here will periodically check to see if anyone is using a terminal monitor program to spy on your terminal. SQUEEZER: A Memory Economizer Filename: SQUEEZER.DOC This file features code previously published in the December 1989 issue of VAX Professional magazine. It was first run as part of Frank Dolatshahi's article, "SQUEEZER: A Memory Economizer," which appeared on page 7 and was the winning entry in VAX Professional's first Call For Papers contest. This program forces the reduction of the working set size of idle processes, releasing memory to the free list without stopping the process. Alternate Between EVE And DCL Filename: SWITCH.DOC This file features code previously published as part of Dennis Broeckel's article, "Alternate Between EVE And DCL," which ran in the October 1990 issue of VAX Professional magazine on page 17. If you're using the non-DECwindows versions of EVE and VAXTPU on a standard, DEC-compatible terminal device, you you can use this procedure to hit the period key on the application keypad to spawn and attach the terminal to a DCL subprocess. Software Layering: Part IV - Error Messages Filename: SWLAYER4.DOC This file features code previously published in Philip A. Naecker's article, "Software Layering: Part IV - Error Messages," which ran in the August 1989 issue of VAX Professional magazine on page 27. Editor's note: In this fourth part of his series on software layering, Philip A. Naecker continues his description of how to build a priveleged shareable image. Software Layering: Part V - Error/Cond. Handling Page 11 Filename: SWLAYER5.DOC This file features code previously published in Philip A. Naecker and Tracy E. Schreiber's article, "Software Layering: Part V - Error And Condition Handling," which ran in the October 1989 issue of VAX Professional magazine on page 27. Here, Naecker and Schreiber explore how to use condition handlers to present consistent errors to the calling program and how to handle errors within the RTL. Here's how to use error messages in signaling mode. Software Layering: Part VI-Errors Inside Your RTL Filename: SWLAYER6.DOC This file Features code previously published in the December 1989 issue of VAX Professional magazine. Originally run as part of Philip A. Naecker and Tracy E. Schreiber's article, "Software Layering: Part VI - Handling Errors Inside Your RTL," which appeared on page 33, the code here represents the final installment in a series on on shareable images. TIMER Filename: TIMER.DOC This file contains code written by Richard D. Newman, originally published in the June 1989 issue of VAX Professional magazine in his article, "TIMER," which ran on page 21. TIMER is a routine to roughly help track the speed of any image or command executed at the DCL level. A DCL symbol EXPIRED or EXP is updated after each command at the DCL prompt while TIMER is active. TESTTIME Filename: TESTTIME.DOC This file features code written by Glenn Harris for his article, "TESTTIME," which ran on page 20 of the February 1989 VAX Professional magazine. The article addressed using VMS date formats for applications data. The code demonstrates a range of data/time routines. Indexed Sequential File Tuning Filename: TUNINGRMS.DOC This file contains a program written by Moses Sun. The code was originally published in the June 1989 issue of VAX Professional magazine in Sun's article, "Indexed Sequential File Tuning," which ran on page 30. The article addresses the concept, technique and tools of the file tuning process. X Views: Using UIL To Design An X User Interface Filename: UIL.DOC This file features code written by David W. Bynon. The user interface prototype for a telecommunications program, presented here, demonstrates the use of UIL and callback routines. The code was originally run as part of Bynon's article, "X Views: using UIL To Design An X User Interface," which appeared on page 14 of the April 1990 VAX Professional. Exploring Files-11 Filename: UNLOCKDSK.DOC This file features code originally run as part of Mark Draughn's article, "Exploring Files-11," which ran in the August 1990 issue of VAX Page 12 Professional magazine on page 14. The code here will unlock a disk volume or volume set that has been locked against allocation. Two other routines will issue an ACP control function to unlock the specified disk volume, and will do formatted dumps of a file header, given the disk name and the file number. The VAX Vector Processor Filename: VECTOR.DOC This file features program segments previously published as part of E. Loren Buhle, Jr., Ph.D.'s article, "The VAX Vector Processor," Which ran in the December 1990 issue of VAX Professional magazine on page 12. The article compares scalar versus vector processing, showing why vector processing can significantly increase processing speed. Amdahl's Law helps to examine the potential speedup because of vectorizing code. VMS Kernels: What's A Lock? Filename: VMSLOCK.DOC This file contains code written by Philip A. Naecker and Tracey E. Schreiber that maps a global section and takes a read lock out on the resource and waits for another process to update it. It shows how the lock manager can be used to synchronize use of non-recorded oriented resources. The code was first run as part of the article, "VMS Kernels: What's A Lock?" which appeared on page 34 in the August 1990 VAX Professional. The VMS Watchpoint Utility: Part I Filename: WATCHPT_1.DOC This file contains program segments previously published in the October 1990 issue of VAX Professional magazine. Originally run as part of Hunter Goatley's article, "The VMS Watchpoint Utility: Part I," which appeared on page 22, the code and the article examine the Watchpoint Utility, an internal-use-only debugging tool that can be used to check modifications of space addresses. It's useful when a data structure is getting trashed by unknown code. The VMS Watchpoint Utility: Part II Filename: WATCHPT_2.DOC This file features code previously published in Hunter Goatley's article, "The VMS Watchpoint Utility: Part II," which appeared on page 25 in the December 1990 issue of VAX Professional. The code here is a simple program to prompt for a system address and set it up as a watchpoint. It was written to demonstrate the $QIO interface to WP. The article provides a look at how the Watchpoint Utility actually works. X Views: Creating Windows And Processing X Events Filename: XEVENTS.DOC This file features code previously published in the August 1989 issue of VAX Professional magazine. Written by David W. Bynon as part of his article, "X Views: Creating Windows And Processing X Events," which ran on page 37, the example C program here demonstrates how to create a parent and subwindow, perform tasks and close the display. X Views: Using Graphics Primitives Filename: XVIEWS.DOC Page 13 This file features code previously published in the February 1990 issue of VAX Professional magazine. Originally run as part of David W. Bynon's article, X Views: Using Graphics Primitives," which appeared on page 34, the code here provides examples for creating graphics with the X Window system. Line drawing, creating arcs and circles, rectangles and points are exemplified in these program segments and sample routines. ORDERING INFO: VAX PROFESSIONAL - The Technical Journal for VMS Systems For over 11 years, VAX Professional has been the leading technical journal for VAX/VMS computing professionals. Published bimonthly, each issue of VAX Professional focuses on a specific topic, and contains articles on a range of other topics as well as regular columns and departments. VAX Professional publishes articles and code for VMS system programmers and managers. 1 year subscription $48, 2 years $86, 3 years $119 for US and Canada. Outside the US and Canada - $66 for one year, $112 for two year subscription. Payable using VISA, Mastercard and American Express. BACK ISSUES: United States and Canada: VAX PROFESSIONAL Set (approx. 25 issues) $175. $10/per issue $5/per article Foreign: Set (approx. 25 issues) $350. $16/per issue $8/per article All orders must be prepaid. VISA, Mastercard and American Express accepted. Be sure to include your expiration date. CONTACTS: MaryAlice Quimby (215) 957-4269 Georgiann Dunion (215) 957-4266 VAX Professional subscriptions Back issue information and orders ========> [VAX91A.QUEUECONTROL]AAAREADME.TXT;1 <======== QUEUE_CONTROL Written by Craig Salyers Aeroquip Corporation Automotive Products Group Mt. Clemens MI QUEUE_CONTROL is a program that allows you to stop and start print queues, change the form on a queue, hold, release, delete and requeue jobs, and send a job to a queue, WITHOUT NESSISSARILY HAVING OPER PRIVILEGE. QUEUE_CONTROL uses an X-Windows like interface that works on VT terminals by using VMS SMG based functions. The default queue for all operations is the one pointed to by the users SYS$PRINT. To use QUEUE_CONTROL, users must be granted the QUEUE_CONTROL Identifier. The program must be installed with the OPER privilege for non-privileged users to perform privileged operations. If you do not want to limit access to this program, simply comment out the IF statement at line 609 of the source code which checks for the identifier and install with OPER privilege. You can limit access to specific device queues using the queue ACL's feature of standard VMS version 5. See the VMS Guide to System Security Manual (M-3 pg. 4-18) for details. We prohibit access to queues which contain the word "BATCH", this has been commented out of the version sent to DECUS. To reinstate this feature remove the comment from line 1004. Detailed documentation on program functions is included in the file noted above. If you have any comments or suggestions for future versions please feel free to contact me at Aeroquip Corporation, Automotive Products Group, P.O. Box 2330 Mt. Clemens, MI. 48046-2330. ========> [VAX91A.RCS]AAAREADME.TXT;1 <======== This area contains RCS, Revision Control System. This is a tool along the lines of SCCS or DEC CMS which allows maintenance of numbers of source files, versioning, and control of shared development. (It is also the basis for CVS, the Concurrent Versioning System, elsewhere on these tapes.) Also included is Gnu DIFF, a differences tool needed for RCS. For a 4.35 minute install for vms without reading any instructions, look at setup.com in the [.install] subdirectory. Rich Gregory 12-jun-1991 /* Copyright (C) 1982, 1988, 1989 Walter Tichy Distributed under license by the Free Software Foundation, Inc. This file is part of RCS. RCS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version. RCS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with RCS; see the file "COPYRIGHT.NOTICE". If not, write to the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. Report problems and direct all questions to: rcs-bugs@cs.purdue.edu */ This directory contains complete sources for RCS version 4.3, Sat Nov 18 13:34:16 EST 1989 This directory contains complete sources for version 4 of RCS. Version 3 was included in the 4.3 BSD distribution. Features include: 1) Version 4 supports the "branch" keyword. 2) Numerous bug fixes. In addition, RCS now runs on many more machine architectures, including Suns (3.x and 4.0), VAXen (4.2 and 4.3 BSD), and IBM PC-ATs (Xenix). 3) Version 4 is backward compatible with version 3. Version 4 RCS will handle files checked in under version 3 (but not vice versa). Page 2 4) This distribution is not supported in anyway. However, bugs and (especially) bug fixes may be reported to rcs-bugs@cs.purdue.edu. 5) Older versions of diff do not support options used by RCS. It is known that 4.3 BSD, and SunOS 3.2 (and later releases) support the needed options. If your version of diff does not support these options, obtain the GNU diff from the FSF. If you use the GNU diff, it is necessary to change the setting of MERGE in the Makefile in the src directory. 6) RCS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License. The VMS port was done by Rich Gregory Commonwealth Clinical Systems 1650 State Farm BLVD. Charlottesville VA 22901 804-977-0000 If you find a bug, please send it to me and I will see if I recognize it. My work was done with the VMS C compiler, not the GNU VMS C compiler. The original unix code is available by ftp from purdue. I had no difficult technical problems with the port. All credit should go to purdue who did 99.99% of the work. rich gregory 7-dec-90 To install for vms: ------------------- Move the EXE and COM files mentioned in [.install]setup.com to an accessible directory and edit setup.com accordingly. Read AAAREADME.VMS. ========> [VAX91A.RPI]AAAREADME.TXT;1 <======== DECUS VAX Systems SIG Tapecopy Submissions Rensselaer Polytechnic Institute Spring, 1991 submitted by: Matthew Madison Engineering Computing Services Rensselaer Polytechnic Institute Troy, New York 12180-3590 USA +1 518 276 2606 madison@vms.ecs.rpi.edu (Internet) MADISON@RPIECSVX (BITNET) This submission contains five 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. All entries include the BLISS source code contained in a compressed BACKUP save set to save space. Use the LZDCMP program to decompress the save sets and BACKUP to unload them. Some of the entries also contain MACRO source code as generated by the BLISS compiler. All entries include an AAAREADME.DOC file; most also include further documentation. All entries require VMS V5.0 or later. 1. [.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 1990 submission] 2. [.MX] Mesage Exchange (MX) is an electronic mail routing and distribution facility, supporting local delivery via VMS MAIL; SMTP over CMU-Tek TCP/IP, TGV Multinet, or DEC VMS/ULTRIX Connection; BITNET mail over Jnet; and UUCP mail over DECUS UUCP. It also supports mailing lists and file distribution over E-mail. [update of the Spring 1990 submission] 3. [.NEWSRDR] NEWSRDR is an NNTP client program for reading Usenet news. Can use CMU-Tek TCP/IP or VMS/ULTRIX Connection as NNTP transport. [update of Spring 1990 submission] 4. [.PCX] PCX is a utility for reading and writing MSDOS-format floppies on VMS. Works with most RX23 and RX33 floppy disk drives. [new] 5. [.WATCHER] WATCHER is a flexible idle terminal monitor. 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, port information, and day of week/hour of day. This version also supports both VWS and DECwindows workstations. [update of Spring 1990 submission] ========> [VAX91A.RSX91A.BRUREAD]AAAREADME.TXT;1 <======== RSX 91A Submission: This directory contains an update to BRUREAD, a program to read RSX BRU backup sets under VMS. The modifications were applied to G. Kums' submission to the Fall 1990 RSX SIG tape (which in turn came from Adrian Weiler's submission to the U.S. Fall 1989 VAX SIG tape, part 1 (VAX89B1) that appeared in directory [.BRUREAD].) To use this program, simply: $ DEFINE BRUDIR $ SET COMMAND BRUDIR:BRU What documentation there is is in BRU.TXT, which is accessable via the command BRU/HELP (or, of course, your favorite editor). A working knowlege of "real" BRU may be helpful. The modifications in this update are mainly in the area of command interface: * The input spec now simply specifies the input file (I found the old device:backupset format awkward for TPC files). * There is a /BACKUP_SET qualifier, which takes multiple backup set names, with wildcards. * /ZERO qualifier to supress complaints about files whose maximum record length is zero. * /BRIEF qualifier to /LIST, which causes it to display only the backup set name and its size. * An output spec is also accepted, specifying the directory to restore the tape under. The old functionality (still supported) is equivalent to specifying [.]. The directory contains the following files: AAAREADME.1ST This file, for more info see AAAREADME.TXT BRU.CLD Set Command BRU BRU.TXT Short documentation BRUREAD.COM Recompile/relink BRUREAD. BRUREAD.PAS program source written in Pascal BRUREAD.OBJ Object file BRUREAD.EXE Executable build under VMS V5.1-1 BRUMSG.MSG Message/OBJ BRUMSG.OBJ Message object. T. R. Wyant E. I. DuPont de Nemours P. O. Box 27001 Richmond, VA 23261 USA ========> [VAX91A.RSX91A.TPC]AAAREADME.TXT;1 <======== TPC -- Fast Tape Copy 26-Jun-91 This is version 1.75 of TPC, the fast tape copy program. There are several enhancements over previous versions. These include: 1. Some unknown enhancer added magtape devices MU: and MA: to the device list. 2. Someone also added the /MI (Magtape In) and /MO (Magtape Out) switches to force a device to be treated as a tape (useful if new tape devices are ever defined). 3. I fixed a serious bug in the AST routines: none of them ever saved R0-R5!!! Since only one AST routine could ever execute at a time (and the mainline code was suspended), this bug has gone undetected for 14 years. It finally bit me when I tried to go disk-to-tape from a high-speed caching disk controller. The first QIO completed (and triggered the AST) before the second QIO was issued. The registers were then clobbered, causing the remainder of the setup code to execute incorrectly. There is still at least one more problem to be fixed when someone finds some time. On RSX-11M-Plus, if the tape is not mounted foreign, the program will simply hang. This condition needs to be checked for and reported. Alan E. Frisbie Flying Disk Systems 4759 Round Top Drive Los Angeles, CA 90065 (213) 256-2575 ========> [VAX91A.SCAN]AAAREADME.TXT;1 <======== V A X S C A N -- P R O G R A M S & I N C L U D E S The files in this directory are those used as examples or in the appendix of the DECUS VAX SCAN Seminar. It is hoped that they will be useful in using a templates for new applications or as examples of the utility of VAX SCAN. The logical name "comp_include" used on the INCLUDE FILE lines should be assigned to the directory where the .SCN_INC files are stored. For information on obtaining the Seminar Handouts, please contact: David K. Ream 9519 Greystone Parkway Brecksville, OH 44141 ========> [VAX91A.SIMON]AAAREADME.TXT;1 <======== Files found in subdirectories to this directory provided by: Christine Simon LTV Missiles and Electronics Group Missiles Division Mail Stop WT-25 P.O. Box 650003 Dallas, TX 75265-0003 (214) 266-7268 UUNET: engcon!simonc@uunet.uu.net DECUServe: SIMON_C Date of current submission: April 1991 This directory contains some ALL-IN-1 management tools. An asterisk denotes tools which are new or revised since the Fall 1990 submission. 1. [SIMON.BADDIR] - contains a command procedure which checks for several things which may be wrong with the users' ALL-IN-1 subdirectories so that problems may be fixed before running the various management procedures such as the Janitor and the Carpenter. ALL-IN-1 V2.3/V2.4 version includes major revisions through July 1990. *2. [SIMON.DTR] - includes all of the necessary DATATRIEVE definitions to run all of the submissions in this directory. Also includes some other domains, records, and procedures which may be useful. Some additional field names have been added to the V2.4 PROFILE record definition. 3. [SIMON.SHARED_REPORT] - contains a command procedure to produce a report of the ALL-IN-1 shared directories, including the number of files in each directory, the size of the .DIR files, and the total size of the files in each shared directory. Includes major revisions through July 1990. 4. [SIMON.PENDING] - contains a command procedure which will inform you of any nonexistent ALL-IN-1 users in the file PENDING.DAT. These represent users whose accounts were deleted when they still had unread mail. This is a bad thing because the OA$SHARE files pointed to by the user will never be deleted since they still have pointers to them. The solution is to find them and get them out of the PENDING.DAT file. Here is a tool to do just that. 5. [SIMON.ARCHIVING] - contains a command procedure which will check to see if an users have requested retrieval of archived files which are offline. If there are any requests, the procedure will send VMS mail to the people of your choice. This is a safeguard against everyone forgetting to check the MAR menu to see if there are retrieval requests. *6. [SIMON.DOC_STATS] - contains a Fortran program to produce a report of all ALL-IN-1 users, showing how many mail messages, archived documents, and word processing documents each user has. The program also shows total counts for the entire ALL-IN-1 system. This is a VERY new program, which works just fine, even though the Fortran is ugly and (so far) poorly Page 2 commented. The program contains Fortran structure definitions for the PROFILE and DOCDB files. ========> [VAX91A.SPX]AAAREADME.TXT;1 <======== SPX is a reference implementation of an open distributed authentication service architecture based on ISO Standard 9594\2558/CCITT X.509 Directory Public Key Certificates and hierarchically organized Certification Authorities. SPX manages the end system state and provides the run\255time environment enabling applications to mutually authenticate on the basis of a global principal identity. SPX scales well in that it does not require online trusted components, and permits management of global trust relationship policy in arbitrarily large distributed environments. Conceptual, component and protocol descriptions are provided. SPX is a portable, self contained implementation of a distributed authentication service intended for open (TCP/IP) network environments. SPX is specifically designed to deal with distributed management of trust relationships in arbitrarily large networks with multiple, mutually suspicious jurisdictional authorities, and to scale well without the need for on line, globally trusted authorities. SPX shares many concepts and data structures in common with ISO/CCITT X.509 Directory Authentication and Internet Privacy Enhanced mail including use of the same public key technology and certificate infrastructure, but operates independently of either of these applications. SPX represents an initial subset implementation of a larger security architecture that encompasses both authentication and a number of other security facilities. (This architecture has been partially described in Gasser et. al.) ========> [VAX91A.STITZINGER]AAAREADME.TXT;1 <======== SESSION NOTES TITLES, F90 and S91 The accompanying files contain the table of contents of the session notes from the Fall 1990 and Spring 1991 DECUS Symposium. Special thanks to Alice Wilson for her assistance in entering these. - - - - - - - - - - John F. Stitzinger Internet: JFS@ICF.HRB.COM HRB Systems, Inc. Bitnet: JFS%HRB@PSUECL.Bitnet PO Box 60, 300 Science Park Rd State College, PA 16804 (814)238-4311, Fax: (814)234-7720 ========> [VAX91A.TIHOR]AAAREADME.TXT;1 <======== The material here is parts of the VMSNET.SOURCES archives and also security and other information from VMSnet and Info-VAX submitted by Steve Tihor. ========> [VAX91A.UNZIP]AAAREADME.TXT;1 <======== Subject: Info-ZIP's free UNZIP v4.1 now available from SIMTEL20 (repost) Keywords: zip, unzip, compression Of most interest to y'all will be the unzip sources (unzip41.arc) and unzip ready-to-run executable (unzip41.exe, incredibly enough). If you just snarf the latter, please also grab the two text files unzip41.doc (a Unix-style [boo hiss] man page) and unzip41.notes (VMS-specific notes written by yours truly; much useless informa- tion therein, plus some very important stuff thrown in for bonus irritation value). The current version is much more compatible with various VMS file types, but it still can't do variable-length records without help (that's one of the important parts in unzip41.notes). Fixed-length 512 (ftp, Kermit "set file type fixed") and stream-LF (Zmodem, BSD uudecode) are fine, however. If there are some Real (tm) VMS C pro- grammers out there who'd like to work on this, feel free to join the Info-ZIP project (e-mail to info-zip-request@wsmr-simtel20.army.mil) --to the best of my knowledge, there's only one other VMSer involved, and he's swamped. I surpassed "swamped" a long time ago. Greg ========> [VAX91A.VMSKERMIT]AAAREADME.TXT;1 <======== This area contains a new test version of VMS Kermit which allows file attributes to be preserved across transfers. For this to work, both kermits (if both are VMS kermits) must be in SET FILE TYPE BLOCK mode. The vmsmit.exe was assembled from MACRO-32 source by Glenn Everhart under VMS 5.4-2. The complete sources are in the vmskersrc.lzh file in LHARC format; use lharc e vmskersrc to extract them if desired. ========> [VAX91A.VMSNET_ARCHIVES]AAAREADME.TXT;2 <======== This is a complete dump of the VMSnet sources archives as of May 1991. It was submitted by Bruce Tanner. Contents: [VLT91A.VMSNET_ARCHIVES] AAAREADME.TXT;1 MAILSERV.DIR;1 VMSNET.DIR;1 [VLT91A.VMSNET_ARCHIVES.MAILSERV] AUTODIAL.DIR;1 AWF-VMS.DIR;1 CALENDAR.DIR;1 CFORTRAN.DIR;1 CSWING.DIR;1 DATEBOOK59.DIR;1 DCL_MENU.DIR;1 DWPROFILE_V21.DIR;1 DWUTILS_V10.DIR;1 DXRN_614.DIR;1 GAWK.DIR;1 GEN_MODULE_DEFS.DIR;1 HELP.TXT;10 HORIZONTAL_MENU.DIR;1 IDLE_TIME.DIR;1 INDEX.TXT;179 JOBLOG_V12.DIR;1 LOAD_AVERAGE.DIR;1 MAILQ.DIR;1 MAILSHR_PATCH.DIR;1 MAIL_UUCP_HLP.DIR;1 MOST_V25.DIR;1 MXRN_DXRN.DIR;1 NBSTIME.DIR;1 ONEKO.DIR;1 PASSWORD_POLICY.DIR;1 PATCH_DIFF.DIR;1 PBMPLUS.DIR;1 PBM_TEX.DIR;1 PC_EXCHANGE.DIR;1 PLM$MAIL.DIR;1 POPEN_PCLOSE.DIR;1 POSTSCRIPT_SYMBIONT.DIR;1 PROFILE.DIR;1 PTD.DIR;1 RAMDRIVER.DIR;1 RATION_UTILITY.DIR;1 REPLY_USERS.DIR;1 SCHEDULAR.DIR;1 SHAPES.DIR;1 SKIM_NOW.DIR;1 STOP.DIR;1 SWIM.DIR;1 SWING.DIR;1 SYSTEM_WATCHER.DIR;1 TERM_LOCK.DIR;1 TGIF_V25.DIR;1 TIME_PROMPT.DIR;1 UNSHAR.DIR;1 UNZIP.DIR;1 USERS.DIR;1 UUENCODE.DIR;1 UUSTAT.DIR;1 VAXC_CRON.DIR;1 VAXNOTES_TO_NEWS_V11.DIR;1 VERTICAL_MENU.DIR;1 VMSTAR.DIR;1 VMS_SHARE.DIR;1 XLOADIMAGE_V203.DIR;1 XTEK.DIR;1 XTERM_V11.DIR;1 XV.DIR;1 YACC.DIR;1 [VLT91A.VMSNET_ARCHIVES.VMSNET] CSWING.BCK_Z;1 DATEBOOK59.BCK_Z;1 DWPROFILE21.BCK_Z;1 ETAPE.BCK_Z;1 LZW.BCK_Z;1 PATCH_DIFF.BCK_Z;1 PROFILE.BCK_Z;1 TGIF25.BCK_Z;1 XLOADIMAGE203.BCK_Z;1 XV.BCK_Z;1 See the [.mailserv] index.txt and help.txt for more information. ========> [VAX91A.WHO]AAAREADME.TXT;1 <======== Spring, 1991 VAX SIG Tape Submission Scott Bailey Xerox Computer Center Webster, New York WHO is a utility designed to output useful information about a user if a username or UIC is known. It was originally modelled on the Digital program of the same name which was eliminated during the summer of 1982, but it now provides much more information than the original program. ATTENTION: WHO accesses the authorization file directly via RMS rather than using the $GETUAI system service in order to support the wildcard and UIC searches it provides. Because the layout of the UAF is not guaranteed to remain stable, this program may break at VMS upgrades. It is known to work under all versions of VMS V5 through V5.4-2 (with CAPTIVE/RESTRICTED interpretation of VMS V5.4, as explained in the documentation) and should work with any version of VMS V4 without modifications. Generally changes are limited to adding support for an additional bit field, etc... but you've been warned... The program includes a variety of security features, most of which are peculiar to the Xerox sites where it is in active use. Restrictions on account visibility are documented at the top of WHO.PAS and are implemented in the module ACCESS.PAS. Fairly complete user documentation is contained in WHO.RNH. The program contains support for our use of the local data area present in each authorization record. In the event that the local area is not used, or contains different information, it will be ignored; the empty fields will not be very noticeable, except perhaps in the /FULL output listing. On the off chance that other sites are interested in utilizing the local data areas, FIXUAF is a program which allows this area to be initialized and updated. I don't have documentation for it, but it is fairly short and reasonably intuitive. If you have questions, fixes, or enhancements, drop me a line. I'm also willing to listen to bug reports, but don't expect fixes, sorry... You can reach me at the following: Scott Bailey (716) 422-0618 Xerox Corporation Mail Stop 300-11Q SBailey.Wbst300@Xerox.COM Webster, NY 14580 ========> [VAX91A.WRIGHTGR]AAAREADME.TXT;1 <======== Software from Gregory L. Wright [.set_default] - part of a .CLD file to allow simpler set default command than the normal VMS one. [.signal] - general purpose use of VMS message utility within DCL. [.signal.errcode] - help write message files to use with SIGNAL [.utils] - Lots of utilities for moving around in directories and so forth... ========> [VAX91A.ZACCA1]AAAREADME.TXT;1 <======== I've been meaning to submit some of these programs for years but I haven't gotten around to it until now. These are all All-in-1 utilities. Where feasible, I've included a sample of the output. I use these programs in an All-in-1 v2.3 environment. I don't believe that there are any differences in the files that are accessed in All-in-1 v2.4 but you should check this out. I've included fortran source, includes, objects and executables so you can do what you want. All of these programs operate in strictly read-only mode. They are to provide information to help you and you must use it as you want. At the bottom of this is a disclaimer that I'm required to include. PLEASE READ IT. Good luck and let me know how it goes. Russell C. Zaccari, Jr. Primerica MS: BSP03C 300 St Paul Place Baltimore, MD 21202 301-332-5945 DAF (DAF_MAIN and DAF_LOOKUP) This program takes a vms filename and gives you everything you could ever want to know about it. To use it, set up a foreign command like daf and type "daf OA$SHARE1:ZRPXBTCQM.WPL" and you will get something like the following: Subject : dec training Title : dec training Sender : PETRILAKM Senders Full Name : Marie Petrilak Senders Tel No : Type of document : MAIL Date Created : 18-Sep-1987 20:17 Date Modified : 19-Sep-1987 22:00 Date Sent : 19-Sep-1987 22:00 Read Receipt : NO Date Posted : 19-Sep-1987 22:00 Delivery Receipt : NO Date Deferred : Priority : FIRST_CLASS No of Attachments : 0 VMS fname : OA$SHARE1:ZRPXBTCQM.WPL Data type : WPSPLUS Language : References : 1 TO: Joanne Grelli ( GRELLIJ ) EMAIL This program takes a username (or username profile) and gives you stats about thier documents. To use, set up a foreign command like emc (email count) and type "emc username" and you will get output like this: NAME EMAIL WPS S2020 Dist Other Archv TOTAL Page 2 ALLIN1 28 0 0 0 2 0 30 If you want to use the other options, they are /FULL, /MATCH and /EXTRA. Full looks like this: NAME EMAIL WPS S2020 Dist Other Archv TOTAL ALLIN1 CREATED 0 0 0 0 0 0 0 READ 0 0 0 0 0 0 0 SENT 19 0 0 0 0 0 19 WASTEBASKET 2 0 0 0 0 0 2 FILED 7 0 0 0 2 0 9 TOTAL 28 0 0 0 2 0 30 MATCH will allow you to enter the beginning characters like "emc z" and you will get a brief listing for all people that begin with z. For all users type "emc *". EXTRA gives you all documents that each person has and information about each (name, number, folder, author and vms filename). PEND_CLEANUP This program tells you about any users that have pending mail and don't have a profile record. To use, just run it. Sample output is not included. PROFILE This program gives information from a users profile record without having to go into All-in-1. Here is an example: username: MANAGER fullname: ALL-IN-1 System Manager title: depart: location: intloc: phone: status: direct: DISK5:[ALLIN1.MGR] The program reads the whole record so you can take anything from the profile record. Due to our legal department's requirements I must include the following disclaimer. Because of this I must recommend that you examine the program's source code and compile and link each on your own. Therefore I have included everything that you will need for each of these utilities. These programs are provided AS IS. Primerica makes no statements or promises regarding the use or operations of these programs. There is no promised or intended warranty for any loss caused either directly or indirectly by any of these programs. Summary: If you use it and lose it, don't call us. Page 3 For you information, most of these utilities use read-only shared access to your files. Many ignore locks from other programs.