========> [VAX85A.AMBY]AAAREADME.TXT;1 <======== 24 May 1985 ==================================== Root Directory for Standard Toolkits ==================================== by Don Amby Delco Systems Operations General Motors Corporation Post Office Box 471, M/S 1A21 Milwaukee, Wisconsin 53201 (414)768-2682 GM Network: 8/521-2682 logical name: TOOLS_ROOT The logical name TOOLS_ROOT is assumed to point to this directory, and is set by the SETLOGS.COM file. This is the root directory for all of the Toolkits that have been set up by D. Amby, to aid in the development of tools, documents, and other Toolkits (Tools to develop tools, to develop tools, and so on). Be aware also, that this system of tools is presently a dynamic system, as I am presently doing work on coming up with new tools, and improving how they are managed. As such, I would appreciate any feedback regarding them (good or bad), if I am to improve them. Important Files --------------- The following is a list of some of the important files that are to be found in this directory. DESCRIP.MMS DEC/MMS descriptor file to build everything. BUILDKITS.COM Builds help libraries, and setup files, for all Toolkits below this directory. SETLOGS.COM Defines logical names for ALL Toolkits. SETSYMBS.COM Defines global symbols for ALL Toolkits. SETUP.SET Overall Toolkits startup file. Standard Toolkits ----------------- The following is a listing of the Standard Toolkits that are found below this directory (as subdirectories). Each will have a SETLOGS.COM and SETSYMBS.COM file, and will have a BUILDKIT.COM (to build the HELP.HLB, SETUP.SET, and SETSYMBS.HLP files) file. Directory Description of Contents ------------- ----------------------------- [.AMBY] Don Amby's Personal Toolkit. [.DOCTOOLS] Document Development Toolkit. Page 2 [.FILETOOLS] File Tools Toolkit. [.MGMT] Toolkit Management Toolkit. [.SWTOOLS] Software Development Toolkit. [.UNIX] Unix-Like Toolkit. Toolkit Standard Directories ---------------------------- For a toolkit directory (and this directory, in some cases) there are to be found some standard subdirectories. [.DOC] Documentation directory. [.RETIRED] Tools, etc, that have been retired. [.SRC] Source directory (Pascal or C programs, help, and document source). [.TEST] Test directory. [.UTILS] Utilities (*.EXE,*.COM, etc files) that implement\ the tools. Accessing Toolkit ----------------- There are three ways that you may access the tools and files that are in this Toolkit. The most important point to be kept in mind, is that the SETLOGS.COM procedure MUST BE RUN FROM THIS DIRECTORY ONLY! 1. Guaranteed Access Method The following method will always work, as the setup (SETLOGS.COM and SETSYMBS.COM) procedures are run from within this directory. $ SET DEF this-directory $ @SETLOGS $ @SETSYMBS $ SET DEF where-you-came-from 2. Access Using SETUP.SET File The second method is to use the SETUP.SET command procedure, for a Toolkit main directory. This can only be done after you are sure that the SETUP.SET file has the proper directory name within it. The SETUP.SET file must have been created with the BLDSETUP tool, that is part of the Toolkit Management Toolkit. This file will have the complete directory specification (including device) inside of it. 3. Access After Logical Names Defined The third, and best method, is to have the system manager use the SETLOGS.COM procedures to define the logical names in the system (or group) logical name tables. This can be accomplished easily as the SETLOGS.COM procedure allows a parameter of GROUP or SYSTEM to be passed, that will have it define system or group logical names. After the logical names are defined then all you need to do is the following. Page 3 $ @tool-kit-logical-name:SETSYMBS Building Files for First Time ----------------------------- If you are setting up these tools for the first time, then you can use the BUILDKITS.COM file, to create the help libraries, and other files. Prior to that, you must have all of the necessary logical names defined. This can be accomplished with the following. $ SET DEF this-directory $ $ @SETLOGS SUPPORT ! defines all logical names $ @SETSYMBS ! defines all global symbols $ $ @BUILDKITS ! builds HELP.HLB, etc. files Updating Toolkits with DEC/MMS ------------------------------ To update the toolkits, I have used DEC/MMS. While this may be a problem for those of you that do not have it, I apologize, but since we do (and I feel it is the best way to manage these tools) I use it. In fact, I highly recommend it, as I feel it is more than worth it's weight in GOLD. Every directory that has anything to be built with MMS will have a descriptor file (DESCRIP.MMS) in it, and will link (via CHECK.PNT files and the MMS .INCLUDE directive) to any descriptor files in subdirectories. Given that you have the logicals (using SETLOGS.COM) and the global symbols (via SETSYMBS.COM) defined, there will be a symbol (STMMS) that you may use to update everything. This will access some standard MACRO and RULES files (for MMS). All that you need to do, to update everything with MMS is the following. $ SET DEF this-directory $ STMMS Updating Toolkits without DEC/MMS --------------------------------- For those of you that do not have DEC/MMS (shame on you), the BUILDKIT procedures can be used (for help libraries), and you can modify them to do what the DESCRIP.MMS files specify. The other alternative is to convince someone (with the money) in your organization to aquire DEC/MMS for you. Toolkits Directory Structure ---------------------------- The directory hierarchy structure, below this directory (in the present environment) is shown in the following diagram. It also Page 4 exists as the file TOOLKITS.PIC, and was generated with the DIRGEN tool, found in the AMBY toolkit (and uses the DECUS supplied SD tool). directory structure of wizard::sys$user:[amby.toolkits] | +- amby ------+- doc | +- retired | +- src -----+- dm | | `- sd | `- utils +- doc +- doctools --+- retired | +- rno | +- src | +- test | `- utils +- exptools +- filetools -+- retired | +- src | +- test | `- utils +- lbl -------+- bin | +- lpr | +- man | +- msg | +- src | +- tmp | `- usr +- mail +- mgmt ------+- src | +- test | `- utils +- src +- swtools ---+- cprims | +- doc | +- pasprims -+- obj | | +- retired | | `- src | +- src | +- test | `- utils `- unix ------+- src `- utils ========> [VAX85A.ARIZONA]AAAREADME.TXT;1 <======== University of Arizona Submissions coordinated by: Joel M Snyder University of Arizona MIS Laboratories Department of Management Information Systems College of Business and Public Administration Tucson, Arizona 85721 (602) 621-2748 These are some preliminary programs that came out of our first six months with V4 of VAX/VMS. 1. BREAK Terminals which are set to be /DISCONNECTable can generate lots of spurious jobs if users lean on the BREAK key too much. Since our users were used to pounding on the BREAK key to talk to a IDX3000, V4 VAX systems often had 64 detached jobs running LOGINOUT. BREAK is a detached program (may be easily integrated into your existing DAEMON) which detects these monsters and cuts them off (before the normal disconnect process timeout) 2. ED1 When Digital gave us callable EDT, we implemented the long-requested EDT-which-remembers-the-last-file-you-edited. GOODBYE to all those awful EDT.COM files FOREVER! Also, for the fun of it, I implemented XLATE functionality, which allows you to go directly from EDT into PHONE, MAIL, or DCL and then back. It was easy. See our example EDTINI.SYS file for information on how to include this functionality. This particular program also implements file locking; that is, no two people can edit the same file at the same time. This was done for a particular customer; you may wish to comment out calls to ED1$ACQUIREMUTEX and ED1$RELEASEMUTEX if this feature is not needed at your site. In that case, you may also ignore ED1MUTEX.MAR. (I'm not sure, but since it uses $ENQ, it might even work on a cluster???) 3. ARRAYEDIT While writing ED1, I also thought that a subroutine which edits a FORTRAN character array might be handy, and here it is. Read ARRAYEDIT.FOR for documentation. ========> [VAX85A.BATTELLE]AAAREADME.TXT;2 <======== Submissions from Battelle Columbus Labs coordinated by: Gary L. Grebus Battelle Columbus Labs 505 King Avenue Columbus, OH 43201 (614)424-7156 This is the late-Friday-afternoon-before-DECUS submission from Battelle Columbus Labs. I have tried to include some of the more significant or useful things we have written or adapted under VMS V4.1. Of particular interest may be the three modified print symbionts. While they have been tailored very specifically to our site, they can hopefully serve as examples for anyone trying to contort the standard symbiont into doing unusual things. CAVEAT: THESE SYMBIONTS DO A FEW THINGS NOT SPECIFICALLY DOCUMENTED IN THE UTILITY ROUTINES MANUAL. THEY MAY NOT WORK WITH FUTURE RELEASES OF VMS, AND THERE MAY STILL BE SOME BUGS IN THEM AT THIS TIME. As this is a last minute effort, documentation is essentially nil. Everything is fairly well commented, but some of the details may be obscure. This is particularly true of the symbionts, which were extracted from our farily elaborate extended print facilities. Feel free to write or call if you need more information. The following items are submitted: 1. [.CLEANDISK] CLEANDISK is a utility to remove all files from a directory tree that are over a specified number of days old. It is currently set up to remove files with "scratch" file types (.LIS, .LOG, .TMP, .PLT,...). It's main advantage over DELETE is that it checks for all matching file types on one pass through the file system. (DELETE makes separate passes for each file type in the list). 2. [.HANDLESMB] HANDLESMB is a modified print symbiont which inserts special job burst pages based on values passed via the /PARAMETER qualifier of PRINT. We use it to flag print jobs which contain sensitive data or require special mailing or distribution. If no /PARAMETER is supplied, it generates a normal VMS burst page. 3. [.HASPSMB] HASPSMB is a modified print symbiont for transmitting files for printing on a remote mainframe. It "prints" the job into a file. The file is written as a mainframe batch job and is transmitted over a remote job entry link (in our case a modified copy of the Software Results Corporation COMBOARD/HASP). The file contains the mainframe job control statements, and a "card image" copy of the print lines. [.HASPSMB.FRMCARD] contains a program to unpack the card image files into print lines. Page 2 4. [.MONITORJOB] This is a command procedure which we run daily as an detached process. It collects MONITOR data during prime usage hours. The daily data is summarized, and the summary displays are archived to provide a historical picture of average system usage. 5. [.SETNODEID] SETNODEID is a program to add an entry to the system rights list containing the processor's node name. This identifier can then be used in ACL's to restrict access to software not licensed on all machines in a cluster. 6. [.SHAREINS] SHAREINS is a program to allow non-privileged users to install images with the /SHARED attribute. It must be installed with CMKRNL. When run, it performs a series of UIC and identifier based access checks and then spawns a subprocess to perform the INSTALL. 7. [.UAFDEF] UAFDEF.DTR is a Datatrieve record definition for the VMS V4 UAF record. We have found DTR to be a valuable tool for doing UAF related reports and maintenance. WARNING: no attempt has been made to actually write (or replace) UAF records using this definition. If it works, let me know. Being the cautious sort, I have always used DTR to generate AUTHORIZE commands to make any necessary changes. 8. [.VARY] VARY is a utility for marking a device as unavailable for allocation. It was developed to support dual-ported MASSBUS tape drives, but could be used for most any device. See [.VARY]VARY.DOC for more information. Note: cluster visible devices must be VARY'ed off on each node on which they are accessible. 9. [.XGPSMB] XGPSMB is a modified print symbiont for generating tapes for eventual printing on a Xerox 8700 Laser Printer. It generates the appropriate laser printer directives (for our laser printer configuration, at least) and formats the VMS print files into standard FORTRAN carriage control print lines. The symbiont also supports processing files containing binary data, such as SCRIBE output. ========> [VAX85A.CLEMENT]AAAREADME.TXT;8 <======== BONNER LAB RUNOFF Page 1 AUTHOR: ------- John Clement Bonner Nuclear Lab Rice University Box 1892 Houston Tx, 77251 (713) 527-4018 BONNER LAB RUNOFF Page 2 ABSTRACT Bonner Lab Runoff (RNO) Bonner Lab Runoff is a text formatter which when used with your favorite editor makes a complete word processor. Its syntax is almost a complete emulation of DSR (Digital Standard Runoff) and it is very compatible with previous versions of Runoff. The document and help file for this version can also be used for DSR. The intent of this program is to support com- plete scientific word processing to produce publication quality output. It has been used to produce thesis, progress reports, and scientific pa- pers here at Rice University. This version allows complete control of any special printer available via user definable escape sequences. In addition a macro facility allows text or sequences of commands to be abbreviated to a single label. If the printer has the correct features then variable spacing,subscripting, superscripting, and equation formatting are possible. By properly defin- ing escape sequences the user may support different printers in a tran- sparent fashion. In other words the same input text will print in identical fashion on different printers with different control codes and escape sequences. Table of contents, indexing and sub-indexing are all supported. Multiple table of contents or multiple indexing may be constructed from the avail- able commands. A variety of LAYOUT and STYLE commands may completely change the look of the pages. Table layout is simplified by right justi- fied and 'decimal' justified tabs. Permanent margins which apply to the page headers are available. These simplify the setting of header and text margins. All special characters are redefinable. The user may define new com- mands, and text macros. By defining commands you can make it resemble other text formatters, or other verstions of RUNOFF. You may define numeric symbols facilitate constructing lists of arbitrary items. These Page 2 allow page and section references. A 2 pass option allows forward refer- ences to symbols defined later in the text. This runs under VMS, RSX, IAS, RT11, TSX, and probably RSTS. It should run on a PRO with no modifacations. RNO occupies a minimum of 30 to 37 kbytes depending on the operating system. BONNER LAB RUNOFF Page 3 Distribution This distribution contains all files necessary for building RNO for any supported operating systems. Nearly All file names are 6 characters or less to acommodate all operating systems. Once you have built the exe- cutable image, you can use it to generate documentation and help files for your operating system. Several files are included to document this version. Instructions for building the program are in the BUILD.DOC file. Bugs that have been fixed are in RNOBUG.DOC. The latest enhance- ments are in CHANGE.DOC. The VMS distribution contains RNO.EXE, but all other users must build RNO. The full document (RUNOFF.DOC) is not dis- tributed on small (floppy) kits, but it is included with mag tape kits. ========> [VAX85A.DFWLUG]AAAREADME.TXT;3 <======== Dallas/Fort Worth Local Users Group The following are the contributions from the DFWLUG for spring of 1985. Located in [.DALSIMICO] subdirectory is a submission from Dallas Semiconductor which consists of a set of macros which support the VAX/VMS V4.x SMG$ RTL screen management routines from VAX-11 MACRO32 assembly language. Located in the [.SOHIO] subdirectory is a submission from Sohio Petroleum which will cross check the directories you have on your disks to the accounts which are defined within SYSUAF, recording differences. Located in the [.TECHDEVEL] subdirectory is a submission from Technology Development Corp. which will provide a output of the amount of disk space you have left on the disks mounted on your system. In the [.WESTELECT] area is a version of REMINDER with the expiration date set to 999 years from now, patched from the Fall '84 version which was set to expire on 8/1/85, submitted by the tape editor. ========> [VAX85A.DWIM]AAAREADME.TXT;1 <======== This directory contains my second try at building a smart commands for common VAX program development functions - The Do What I Mean or DWIM facility for VMS 4.0 or later. It is by no means complete, but can provide some very useful functions along with serving as a testbed for other similar functions. All you need to do to install it is to put it in an accesable directory. During or after login, if you wish to use DWIM functions all you have to do to initialize them is to use the command "@[directory]DWIM". Several areas of the package could use work such as the EDT initialize files but I haven't had the time. As with most things developed on a shoestring, documentation is somewhat of an afterthought. The help file was quickly put together just before Spring 85 DECUS and should be fairly accurate but not as comprehensive as I would like. After DWIM is initialized use "DWIM HELP" to access this help file. The remainder of the documentation, such as it is, is in the code. I would like feedback on usefullness, enhancements, features, bugs and comments if you try to use the package - but by mail only. My address is: Karl Johnson Interlink Computer Sciences Inc. 39055 Hastings St. Suite 203 Fremont, Ca. 94538 ========> [VAX85A.ERI]AAAREADME.TXT;4 <======== Eye Research Institute Submissions coordinated by: Bob Goldstein, Daniel P.B. Smith Bob Goldstein, Daniel P.B. Smith Eye Research Institute of Retina Foundation 20 Staniford Street Boston, MA 02114 (617) 742-3140 This our first VAX DECUS SIG tape submission. It consists of some system management utilities and a program for using Macintosh Computers with VAX/VMS. The system utilities consist of a command procedure to automatically queue nightly processes and a set of programs that logs interactive response time and reports the results. MACSNVAX is a program that allows VMS to emulate a Macintosh for the purpose of file transfer and storage. MACSNVAX has been used on several VMS systems, but the system manager utilities have not. These are all VMS version 3 programs and we do not know their behavior under version 4. 1. SYSMGR.DIR 1. Nightjob - Command procedure that automatically queues nightly, monthly, half-monthly processes. 2. UNITS - Program that replaces VAX logout, but eventually does chain to the VAX logout. Before logging out, the user is queried for his opinion of the response time during the session, and his response is logged. The program also generates accounting info for the user. 3. Resprept - Program that reads the response log generated by UNITS and reports on the results. 2. MACSNVAX.DIR MACSnVAX is a complete utility for uploading, downloading, and transferring Macintosh files via a VAX. o MACSnVAX is a VAX/VMS-hosted utility that serves Macintosh users running MacTerminal. It provides for transfers of any Macintosh file by emulating the modified version of XMODEM that MacTerminal use for "MacTerminal to MacTerminal" Page 2 transfers. o All Macintosh files, including applications, formatted MacWrite files, MacPaint files, fonts, etc. can be successfully transferred. o MACSnVAX is intended for end-users and is reasonably easy to use. It presents a standard VMS interface, with features like wildcarding supported where appropriate. o MACSnVAX can catalog the Macintosh files stored in a VMS subdirectory, presenting the full Macintosh name, type, creation date, etc. o In the case of Macintosh text files, MACSnVAX can present the information directly to the screen without downloading, and can convert between VMS and Macintosh text formats. Portions of MACSnVAX version 3.4 are copyright (c) 1985 by Eye Research Institute of Retina Foundation; all rights reserved. Eye Research Institute licenses MACSnVAX version 3.4 for use by DECUS members at no charge provided they register with us. 3.4 is a fully functional, useful utility. An improved version may be distributed on a "shareware" (donation requested) basis. ========> [VAX85A.EROS]AAAREADME.TXT;5 <======== EROS DATA CENTER ************************************BOUNCER************************************ BOUNCER is yet another idle terminal killer. The differences between BOUNCER and other idle terminal killers are that the killing is optional and the entire process tree is examined as one unit. On our system, we allow users to be idle unless we run out of lines (we have a port selector). The default mode only monitors and reports idle users to the operator, and the operator manually kills them when necessary. The exception to this rule is that privileged users are always killed, without warning, after exceeding the idle time limit. The console (OPA0:) and the user defined in exempt_user (OPS on our system) are never timed out. BOUNCER has a variable idle time limit (in minute increments), and any user exceeding that limit is logged in [SYSMGR]BOUNCER.LOG and optionally killed. BOUNCER also writes a file once a minute which is called [SYSMGR]DEADBEATS.LOG and contains an entry for each user which has been idle for more than a minute. The operator or system manager can type this file to see who has been idle how long (we have defined a symbol which types it). A process is idle if hasn't used any BIO (buffered I/O's), DIO (direct I/O's) and has used less than 10 milleseconds of cpu time. Because issuing GETJPI calls causes a kernel mode AST to run in the context of the target process, CPU time is occasionally incremented in the target process even though it is truly idle. Since GETJPI reports CPU time in 10 millesecond increments and the GETJPI call seems to increment their CPU time by less than a millesecond, we only occasionally see the change in CPU time. By allowing a process to use 10 milleseconds of CPU time and still be considered idle, we can eliminate the possibility of mis-reporting a process as being active. Some will argue that an active process could use 10 milleseconds (or less) of CPU in one minute and still be doing usefull work... but I won't beleive it unless I see it. If you disagree, you may change IDLE_CPU to 0, which will treat any increment in CPU time as "active" CPU time. BOUNCER properly handles sub-processes and will not consider a process idle if any subprocess is active. All subprocess BIO's, DIO's and CPU times are added to those of the root process. To use bouncer, do the following; BOUNCER :== $SYS$MANAGER:BOUNCER DEAD :== TYPE SYS$MANAGER:DEADBEATS.LOG BOUNCE 20 !Monitor users, write in log if idle 20 min or BOUNCE -20 !Monitor and bounce idle users after 20 min At our sight, we run BOUNCER detached. We have set up a command procedure which is invoked in systartup. Two command procedures are actually used, BOUNCE.COM which creates a detached process which invokes BOUNCE.CMD (these command procedures are included here). I have assumed that BOUNCER will reside in SYS$MANAGER. If not, you must change the command procedures and the above examples. The DEAD symbol will allow you to get an up to the minute report on Page 2 who is idle. All users wishing access to this info can define DEAD in their LOGIN.COM. DEAD is short for DEADBEATS! NOTE: Use of this program requires WORLD, OPER and write access to SYS$MANAGER. NOTE: BOUNCER has not been tested under VMS V4.0 but should run properly if recompiled and relinked. Compile and link thusly; @BUILD ******************************************************************************* EROS stands for Earth Resources Observation Systems and is not related in any way with the skin mag of the same name. We are a government agency which primarily stores, enhances and sells LANDSAT and other imagery. Written and submitted by: Thomas Bodoh U.S.G.S. / EROS data center Mundt Federal Building Sioux Falls, SD 57198 (605) 594-2271 ========> [VAX85A.FINGER]AAAREADME.TXT;1 <======== FINGER for VMS V4 This directory contains Rich Garland's latest Finger for VMS V4.0 documented in FINGER.DOC. Note the FINGERDIR.LIS file documents the original file names used; some long ones were renamed to get the sig tape distribution to be readable by V3 sites without errors. ========> [VAX85A.GDQSD]AAAREADME.TXT;1 <======== The programs INFORM, GQM and BECOME, which first appeared on the VAX SIG tape for the St. Louis symposium, will be updated for version 4 of VMS within the year. Ken Coar General Dynamics Quincy Shipbuilding Division ========> [VAX85A.GRAY]AAAREADME.TXT;1 <======== AAREADME.DOC Advanced Users Login Utility: LOGIN V2.0-01 VAX/VMS: V3.x (origonally edition) V4.1a (compatable distribution) VAX11-C: V1.4 (origonal edition) V1.5 (compatable distribution) Address comments, questions, large sums of cash and/or goods to one: - Thomas Charles Gray TDB Systems Development VOLT Delta Resources, Incorporated. 2323 West Lincon Avenue Anaheim, California 92801 This distribution contains a login-time utility, LOGIN, which was designed to expidite access to user accounts by defining (presumably) all logical and symbols from within a single image (as opposed to the DCL utility) and to allow easy modifications of these tables. Also provided is a brilliant login page describing all of the traditional garb on your newly created process --virtually everything you need to stimulate your ego into oblivion during those long login waits on your favorite VAX. LOGIN was origonally written in MACRO to run on a large (!) timesharing VAX-11/780 (where DCL is commonly refered to as Discusting Common-Language for its speed), and was rewritten in FORTRAN at a later point in time to improve source maintainability, user-friendliness, and author-sanity. This latest release is written entirely in C to take advantage of all of the benifits (datastructures!) of this (relatively) new and (subjectively) exciting language. Due to copyright problems, the MACRO and FORTRAN versions cannot be released. (You'll just have to bug management to buy "that C compiler everyone is talking about.") --BLISS32 users, forgive me, I am being held hostage at a site without the compiler! I have this up and running under V4.1a (8600 version of V4.1) right now . . . a version taking advantage of the new facilities of V4 (ie, $CRLNM) is underway. . . To setup LOGIN in a user account, do the following - $ SET DEFAULT SYS$LOGIN $ CREATE/DIRECTORY [.ACCOUNT] $ SET DEFAULT [.ACCOUNT] Page 2 ! !Setup your LOGICALS.CAT, SYMBOLS.CAT, CONSTANTS.CAT, ! DIRECTORY.CAT, and HARDWARE.CAT files ! by creating the files in an editor with the ! following format: ! ! [[defineetranslation],...] ! ! Example: ! LOGICALS.CAT ! MAINSYS$LOGIN ! DOCUMENTSMYDISK:[ME.DOCUMENTS] ! $ EDIT LOGIN.COM ! ! Add the following lines... ! $ ASSIGN mydisk:[me.ACCOUNT] ACNT $ LOGIN :== $ACNT:LOGIN.EXE $ LOGIN Usage - $ LOGIN [SUBPROCESS|NETWORK|BATCH] If no parameters are specified, LOGIN assumes a context of interactive process. If SUBPROCESS is specified, LOGIN performs only logical and symbol definitions (great for All-In-One's OAINI procedure). If BATCH or NETWORK are specified, no accounting or user display is performed, however logical and symbol definitions are made. One of these days I will add a $GETJPI item to find out how LOGIN is being invoked without requiring a parameter. Distribution - AAREADME.DOC ....... This file DECCRT.H ....... VT screen stuff LOGIN.C ....... VAX-11 C Source for LOGIN LOGIN.OBJ ....... VAX-11 C Object for FORTRAN low-lifes LOGIN.EXE ....... V4.1A (8600ized V4.1) image file LOGINMSG.MSG ....... VMS Message Utility Source File LOGINMSG.OBJ ....... VMS Message Utility Object File LOGICALS.CAT ....... Sample LOGICAL.CAT file SYMBOLS.CAT ....... " SYMBOLS.CAT " DIRECTORY.CAT ....... " DIRECTORY.CAT " HARDWARE.CAT ....... " HARDWARE.CAT " Rebuild - Page 3 To rebuild LOGIN from sources ... From a directory containing DECCRT.H . . . $ CC LOGIN $ MESSAGE LOGINMSG To rebuild LOGIN from objects ... $ LINK LOGIN,LOGINMSG ========> [VAX85A.HUGHESSCG]AAAREADME.TXT;1 <======== HUGHESSCG ----- random software from the dungeons of Hughes Aircraft Space and Communications Group, Computing Technology Center. Node: ENGVAX. Contributed by Kevin Carosso and Gordon Howell. (213) 647-8649 UUCP: ...{allegra | seismo | ihnp4}!scgvaxd!engvax!{kvc | gordon} All software runs under version 4.1 VMS. Source provided for all. Includes: PTYDRIVER -- Pseudo-terminal device driver for VMS. Implements all VMS terminal I/O functions. UUCP_MAIL -- a sample foreign mail protocol implementation for VAX/VMS MAIL. This one interfaces to the locally-developed VMS-UUCP. STRATEGO -- a re-submittal of the two-terminal STRATEGO game, originally published in the Spring '84 DECUS tape. Contains minor revisions for VMS 4.0. OPERATOR -- a captive-account command procedure, with associated utility procedures, to allow operators to do their job without hosing the system. ========> [VAX85A.LILUG]AAAREADME.TXT;7 <======== L O N G I S L A N D L O C A L U S E R' S G R O U P This directory contains the submissions from the LONG ISLAND USER GROUP. Questions concerning these submissions should be directed to one of the authors (shown in the sources) or one of the following contributors: John Hasstedt -or- AL(Fred) Scholldorf Physics Department Reuters Ltd. SUNY Stony Brook 90 Davids Dr. Stony Brook, NY 11974 Hauppauge, NY 11788 (516) 246-7110 (516) 435-7116 Subdirectories are: [.DQ650] Program to read the graphics screen of a Retrographics model DQ650 graphics enhancement board back in over the terminal line and dump it out to a file in QMS Laserprinter format. Handy (but slow) for graphics terminals without attached hardcopy printers. Easy to modify for other bitmap output formats. [.GREEK] Programs for manipulating bit maps for programming custom character set EPROMS for VT100's and other video controllers Also the bitmaps for our own greek/math character set. Also contains a program to download a greek character set to a VT220 or VT240. [.MTCOPY] RSX Compatibility Mode MAGTAPE-to-MAGTAPE copy program. Completely format independent, with options to skip over EOF markers and ignore parity errors (handy when trying to read marginal tapes or to recover files from a tape you mistakenly initialized). A hack program but it gets the job done. I use it all the time for making copies of DECUS symposium tapes. Also works on RSX. [.QMS] Command files and TeX sources for doing clever things with a QMS Lasergrafix 1200 printer. PRINT is a super command procedure to print files on a QMS Laserprinter with all the options (like /FONT, /TOP_MARGIN, /LOGO etc.) This also comes with a faster FORTRAN implementation. Subdirectory [.LOGO] contains procedures for generating letterheads and logos using TeX. PRINT.COM can download these to the QMS along with the file to be printed. [.TAPES] Command files and small FORTRAN programs for crunching on tapes: reading card image tapes, trailing blank suppression, EBCDIC conversion, etc. [.UTILS] Command files for an RSX sytle DELETE command; editor initialization files; command files to download fonts, Page 2 change print parameters, and print files on FX80 printers attached to a terminal printer port; minor rewrite of KEYDEF procedure for VT200 from an earlier tape, etc. See also [.UTILS]SUNY.HLP for more documentation on some of the command files and utilities described above. I didn't have time to burst all the documentation out into distinct files. ========> [VAX85A.LJK]AAAREADME.TXT;1 <======== Pageswapper Files These are the Pageswappers since the last symposium. Larry Kilgallen, editor. ========> [VAX85A.MACPRINT]AAAREADME.TXT;1 <======== MACPRINT here converts Macintosh print files into a format the VAX can handle. Switches are supplied for a variety of printers. ========> [VAX85A.MILLER]AAAREADME.TXT;1 <======== Free software BY Northern Telecom Inc. Program: VAXNET Author: Robin Miller Date: Spring 1985 Description: VAXNET is a program which allows communcations between two computers using an asynchronous terminal port. The systems can be connected either directly using a null modem cable or via a dialup modem. Communications with the remote system is accomplished using a second port on the local system. This version of VAXNET incorporates several new features. Free software BY Northern Telecom Inc. Program: VTL Author: Robin Miller Date: Spring 1985 Description: This program is used to list file(s) on a VT100 family terminal. The file(s) are displayed one screen at a time for easy viewing. Various commands can be entered to change listing parameters or to position to a particular portion of the file. Many of the commands are the same as the Digital editor EDT. Commands can be entered either by using keys on the VT100 keypad, or by entering commands to the prompt at the bottom of the screen. Some of the major features of the program are outlined below: o CTRL/C detection for aborting searches, etc. o Delete the file being displayed. o Display a ruler along the top of the file. o Display the next file or next the directory. o Display record numbers along the left margin. o Display the file header of file being displayed. o Print the file being displayed. o Search forward or backwards for a string. o Shift the display window left or right. o Split screen mode to display two files. o Teco compatible see-all mode. o Write portions of the file being displayed. The maximum record size that can be displayed is 512 characters. All commands have a repetition count of one. Relative and indexed files are not supported. This version of VTL runs on VMS version 4. Page 2 [ File "VTL.MEM" contains full documentation for this program. ] Northern Telecom Inc. Network Support Systems Division P.O. Box 649, Airport Road Concord, New Hampshire 03301 (603) 224-6511 X2024 ========> [VAX85A.MORSE]AAAREADME.TXT;4 <======== Kathleen D. Morse VAX/VMS Software Development Digital Equipment Corporation ZK01-1/D42 110 Spit Brook Road Nashua, NH 03061 603-884-8396 (Please don't call/write me.) These are the slides for some of the sessions given by the VAX/VMS developers at Spring DECUS in New Orleans. Listed below are the summaries of the sessions, and the name of the text file that contains the slides. All files are just text files and can be printed on any terminal or line-printer (*.TLK). PAGING, SWAPPING & WORKING SET ADJUSTMENT: MEMORY.TLK This talk details some of the internals of the VMS memory management subsystem. SYSGEN parameters are discussed for working set adjustments. VMS UPDATE: VMSUPDATE.TLK Update of new things happening in VMS. VMS V4 BATCH AND PRINT: BATCHPRNT.TLK This talk provides an overview of the batch and print capabilities of VAX/VMS. Topics include the job controller, and related DCL commands and system services with emphasis on new features for Version 4. The distribution and control of jobs in a VAXcluster is also described. VMS BATCH/PRINT SUBSYSTEMS INTERNALS: BATCH.TLK Talk on the internals of the batch and print subsystems. THE IMAGE ACTIVATOR (PAST, PRESENT, AND FUTURE): IMGACT.TLK This talk describes how the image activator works currently, and how it worked for each release of VMS. GUIDE TO WRITING A VMS UTILITY: DCLGUIDE.TLK This talk describes how to write a VMS utility. Page 2 MicroVMS FUTURES: UVMS4M.TLK This talk describes the VMS support for the new MicroVAX II product. GUIDE TO CREATING A VMS INSTALLABLE PRODUCT: INSPROD.TLK VMSINSTAL is a command procedure used by layered products to install their software products on VAX/VMS. This presentation will describe the internals of VMSINSTAL, the callbacks that are available, and how this VMS supported procedure can be used to install your own software products. DCL AND THE VMS UTILITIES: DCLUTIL.TLK There have been many enhancements to DCL and the utilities for Version 4.0 of VAX/VMS. This session will highlight many of the new features that are available at the command level interface to VMS and discuss the advantages they provide. Knowledge of the DCL interface is assumed. RMS ISAM INTERNALS: RMSISAM.TLK This talk will address the internal structure of RMS ISAM files, concentating on Prolog 3. Among the items discussed will be RRVs, RFAs, structure of primary and secondary indexes. Some attention will be given to the mechanism behind RMS operations (such as $GET, $PUT, and $UPDATE), and to what happens during bucket splits. ========> [VAX85A.NSWC]AAAREADME.TXT;1 <======== [VAX85A.NSWC]AAAREADME.TXT KILL AND BKILL COMMANDS ----------------------- The KILL command searches all output queues for jobs PRINTed by the calling user. For each job found, information on it is displayed, and the user is asked if he/she wants to kill it. If 'YES' is entered, the job is deleted. The BKILL command is identical, except it searches all BATCH queues. A job number or queue name can be specified to limit the queue searches. Privileged users (OPER, WORLD, or GROUP) can delete other users' jobs. For further information, see KILL.DOC and KILL.HLP. SD COMMAND ---------- Yes, yet still another Set/Show Directory command. This one uses the VT100 line-drawing set to draw a tree showing the subdirectory structure within the current default, and allows you to use EDT-like keypad commands to manipulate this dis- play. For a quick example, enter: $ SET DEFAULT [VAX85A] $ @[VAX85A.NSWC]SD * This version of SD is mostly implemented via a FORTRAN program instead of DCL commands, and runs faster (on our VAX, anyway). For further information, see SD.DOC. LET COMMAND ----------- LET is a shorthand way of doing DEFINEs or ASSIGNs in the same way that SD is a shorthand way of doing SET DEFAULTs. See the LET.HLP file for examples. Examine BLDLET.COM for information on the installation of the command. Also see SD.DOC for rel- ated information. LET and SD are closely related. Page 2 REMINDER UTILITY ---------------- This is yet another appointment-reminding utility. This one reminds you when you log in, and 'tickles' you at fixed inter- vals as the time of an appointment approaches. The reminder message tells you when the appointment is, and what it is. The message is formatted in reverse video for VT100+ terminals and the bell rings. It is very easy to add, remove, and show appointments. For further information, see REMINDER.HLP. See REMINDERS.DOC for installation instructions. This utility uses a detached process (which is usually hibernating) to send the 'tickler' messages. Use BLDREMIND.COM to rebuild the pack- age from its sources. NSWC1LIB.OLB ------------- Object library used in building the above programs. This lib- rary is built from LIB1.FOR and LIB*.MAR. Some of the routines may be useful to you; they are documented by prologues in the sources. SMG.DAT ------- This contains a twelve-page summary of the VAX/VMS Screen Man- agement (SMG$) Routines, condensed from the 207 pages in the VAX/VMS V4.0 Run-Time Library Routines Reference Manual. This to me is easier to use than the manual or HELP. You can print it and/or have the file handy to INCLUDE in your EDT session to use the editor's search commands to quickly find things. To save space, the 'SMG$' prefix was dropped from routine names. Page numbers reference the V4.0 RTL Reference Manual. ------------------------------------------------------------------ Submitted by: Alan L. Zirkle Naval Surface Weapons Center Code N41 Spring 1985 Dahlgren, Virginia 22448 ========> [VAX85A.NU]AAAREADME.TXT;1 <======== N O R T H E A S T E R N U N I V E R S I T Y [NU.MISC] - A FAST LOGIN.COM, TUNING STATISTICS GATHERER [NU.SACK] - UTILITY TO ALLOW NON-PRIVILEGED USERS DO A MULTITUDE OF THINGS IN A CONTROLLED MANNER This directory tree is from: Rand P. Hall Northeastern Univ. College of Engineering 268SN 360 Huntington Ave. Boston, Ma. 02115 ========> [VAX85A.OAKLEY]AAAREADME.TXT;2 <======== This directory contains the following submissions: FILES - program to quickly locate files based on ownership and size. This program ghas been revised to work under VMS V4, and replaces the submission found on the Spring, 1984 tape. GRANTID - software to grant (and revoke) system-wide rightslist id's. This is a new submission. This software is useful for controlling access to files to a subset of nodes in a cluster, when the disk is mounted cluster-wide. The author welcomes questions and comments. They may be addressed to: Mark Oakley DuPont Experimental Station Wilmington, Delaware 19898 302/772-3522 ========> [VAX85A.PANEL]AAAREADME.TXT;1 <======== The files is this directory comprise a utility called PANEL. PANEL was described in a session titled "Creating Menu Driven Systems Using VAX DCL and FMS" at the Spring, 1985 Decus in New Orleans. PANEL provides a way to display an FMS form from DCL. Upon existing, PANEL creates DCL symbols names of the form P$xxx where xxx is the name of each field on the form. Each of the P$xxx variables may then be used by the executing DCL command procedure. Note: The COM procedures on this directory are examples of using PANEL from DCL. In most cases, they will not work as they are because they use FOREIGN commands that your system probably does not have. The ASORT.COM file is the first one you should try after you have done a SET COMMAND PANEL. In PANEL.CLD you should modify the image line to point to the directory where PANEL.EXE lives on your system. PANEL is really very simple to use if you are familiar with FMS and DCL. You must have FMS in order to use PANEL. You must have VAX-11 C in order to make changes to PANEL. For additional information, consult the Procedings from 1985 Spring Decus. If you have FMS, and C and you still can't get it to work, call me at 614-548-4301. Brian Lockrey ========> [VAX85A.POTTER]AAAREADME.TXT;1 <======== All of these Utilities Have been modified so that they function properly on VMS V4.0 AWP (20 May 1985) these directories contains a bunch of simple (and somtimes useful) utilities. Questions concerning these submissions should be directed to: Andrew W. Potter Rochester Inst. of Techology ISC-Technical Support One Lomb Mem. Drive Rochester NY. 14623 Phone (716) 475-6994 programs are: NEWS A general news utility that runs when users login and gives them a brief listing of all unread news. When the user reads the news in full, the login message is removed for that user. A nice alternative to a lengthy SYS$WELCOME file. The program must be installed with SYSPRV and SYSLCK CD A fast unix(tm) like chdir written entirely in fortran (no dcl) GMAIL A general purpose public bulletin board facility. NETCOPY A preprocessor for copy which uses getjpi to get a username and inquires for the password separately(noecho)... (The username can still be specified explicitly) NETUSERS a graphic program which (on a GIGI or VT-125) will display in colered bar graph form the user and batch job counts on up to 5 decnet nodes. A version which works on VT100 or VT52 terminals called N100 is also supplied. NODESHOW a utility which will allow users to look at other DECNET nodes without actually logging on to them. (NEW) TRMPRINT A Utility to allow users to print files on their local Printers attached to their VT102 type terminals with a syntax similar to VMS PRINT. (NEW) EDTSPN A program that uses the VMS Callable EDT XLATE function to spawn a DCL session from Within EDT. (By hitting CTRL/F) It also has a File existance checking to confirm the creation of a new file. (NEW) USERSET A Program that allows a privileged user to Change his Username, UIC, Account Name, Process Name to that of another User. (NOTE: It does not change the Process JOB logical name table) ========> [VAX85A.PRC]AAAREADME.TXT;1 <======== This submission contains three items: [.PRC.BACKUP]*.* A captive command procedure for doing system backups in a consistent manner. The main features are: The backup command procedure implements the backup schedule suggested in the Guide to VAX/VMS System Management and Daily Operations manual. The suggested schedule is as follows: Daily incremental backups are performed Monday through Saturday. Weekly incremental backups are performed on all Sundays except the first Sunday of the month. Image backups are performed on the first Sunday of each month. All defaults are determined by the command procedure including type of backup and disks to be backed up. However, all defaults can be overridden. The backup command procedure can type a file on the system console to relay special instructions for the backup procedure. These special instructions could be to override either the type of backup to perform, the list of disks to be backed up, or the backup date for a Weekly backup. The default list of disks to be backed up can be either all disks on the system, a restricted group of disks or an explicit list of disks. The tape device to be used can be selected from any on the system, with preference given to certain types of tape drives or particular individual drives. The recording density used can be specified explicitly or the command procedure can select the highest density that the allocated tape drive supports. For Image backups, the backup command procedure will force users to logout, if necessary, to insure a complete backup of the disks. Before an image backup of the system disk the command procedure instructs the operator how to boot Stand-alone BACKUP, what command to use to backup the system disk, and how to re-boot VAX/VMS, before performing a system shutdown. The BACKUP commands issued by the command procedure create a BACKUP journal file which can be used to locate files to be restored. The command procedure also maintains a log of the backups that are performed. Log file entries record the type of backup performed, the date and time of the backup, the list of disks that were backed up, and the backup date for Weekly backups. For complete information RUNOFF the file BACKUP.RND. Page 2 [.PRC.KERMIT]*.* An copy of VMS Kermit (version '3.0.052') distribution with several bug fixes and updates. See the file CHANGES.DIF for complete descriptions of the changes. These changes include: Restricting the "SET RECEIVE PACKET_LENGTH " and "SET SEND PACKET_LENGTH " commands to specifying a maximum value for of 94 instead of 96. Correcting the descriptions of the "SET RECEIVE PACKET_LENGTH " and "SET SEND PACKET_LENGTH " commands to indicate that the maximum value for is 94 instead of 96, and to "quote" some characters that RUNOFF was interpreting as special flag characters. Increasing the size of the buffers used for packets sent and received. While the buffers were large enough for the maximum size of a Kermit packet, they did not include space for a line terminator character. Restoring the transmission terminal's parity settings and and fill counts. [.PRC]PARITY_FLAGS.DOC This file contains some documentation on the format of the Parity Flags field in the IOSB of the Terminal Driver's Set/Sense Mode/Characteristics I/O functions that is not contained in the I/O User's Reference Manual. In the process of fixing a problem in VMS Kermit that cropped up under VMS V4 I found that the format of the Parity Flags field was not documented. With the help of DEC's Customer Support Center and some microfiche reading I was able to determine the format of some of the information returned in the Parity Flags field. Jim Noble Mail Stop 5S3 Planning Research Corporation 1500 Planning Research Drive McLean, VA 22102 (703) 556-1394 ========> [VAX85A.QUEST]AAAREADME.TXT;3 <======== This area has the game QUEST for VAX, a dungeons-and-dragons type game. Owen Anthony, Ball State Univ. ========> [VAX85A.RCA]AAAREADME.TXT;4 <======== G. Everhart submissions for Spring 1985 The following are offered for your amusement or use: 1. In [.CPMRSX], is a package from the 1982 Astralian tape. It will allow one to read/write CP/M format 8" floppies on RSX (or VMS). You may be able to build a complete CP/M emulator with it. 2. In [.DTC...], several versions of DTC. These have been somewhat debugged and new features added. In particular the [.dtc.mvaxdtc] is an entirely new revision with many enhancements by C. Garman of RCA MSR. A few features were left out of his version however, so it does not replace all existing ones. A new version for 8088 has been supplied also. This is a really nifty desktop calendar that keeps getting nicer as more features are added. The new version is also MUCH faster than the original one, though it is designed for Vax only. The PDP11 and 8088 MSDOS versions are also present however. 3. In [.gcegen] are a few handy items from various places. These include a revision of the DDT symbolic (Pdp11) debugger with some features to permit back tracing where a program came from to get to an error. It is quite useful on VAX or RSX as a symbolic image examine/patch utility also. The ATT program (which reads or alters file attributes in place) and the BIGTPC fast tape to disk to tape copy utility are supplied. A version of DUMPER.C (to read TOPS-20 DUMPER tapes on VMS) is supplied. Also the LISTRS multicolumn lister, and CB.C, another BBS utility to "beautify" C code. A number of other additional utilities are present, so look around; a VT100 figure drawing package or two (also useful for flowcharts or org charts) can be found. Files of type ARC are in DECUS C Archive format and are pure source code. 4. In [.PCCOBJ] are object libraries (and DTRIF.OBJ for those who don't have Datatrieve) for the new PortaCalc spreadsheets for use by folks who lack Fortran (or equivalently are trying to use the new V4.0 release of the compiler) and want to link PortaCalc for their systems. The DTR-32 interface is supported for the PCCX.OLB library, so now your spreadsheets can directly access your DTR-32 databases. Note that the default PCCX.OLB build INCLUDES DTR32 calls and needs to be done with the .OPT file. use DTRIF.OBJ to OMIT the DTR32 calls from the PCCX version. 5. In [.PCCPDP] is the latest PDP11, PRO 350, and VAX version of AnalytiCalc with VAX support for DTR-32 (see DTRIF.DOC for further info on how it works). DTR-32 is NOT required, and a version can be built not using it if desired. Some code speedups and other random novelties have been added too, including ability to generate very wide output reports (up to 512 characters, probably wider than YOUR printer). 6. In [.PCCVAX] is the lastes VAX spreadsheet that does not use DTR (actually, on VMS you can pick the one here or the one in [.PCCPDP]. The one here is a bit faster but uses more Page 2 memory. The one in [.PCCPDP] uses less memory but is a bit slower. It can however access DTR-32. Try both and compare, then choose. All documents are here, plus income tax templates, a management system template for predicting manpower needs with several jobs, and a Business Expense Report template (to help you write up expenses for DECUS symposia and the like) with all the numbers at your fingertips. 7. In [.PCPGMS] are a number of IBM PC, Rainbow, Z80, 8088 etc. programs that may be of some interest. One notable item is a VT100/VT52/VT102 emulator for IBM PC so you needn't go and buy one of the expensive ones. 8. In [.SQUTL] is a new squeeze/unsqueeze system that is far superior to SQ/USQ, works on binary files (at least, on .EXE files) as well as text, and compiles in DECUS C or VAX11 C thanks to M. Minow. There are some sources for LAR (a utility to read CP/M or MSDOS LU libraries or write them) and a dialect of LOGO, both done for un*x originally and awaiting conversion to RSX or VMS. LAR is actually pretty close as it stands and will list directories of libraries now in VMS. 9. In [.TARFLP] is (compat mode) code that can read or write Unix TAR format floppies on RX01, RX02, or RX50 disks. Use now on your regular VAXen or use on your microVAXen later when VAX/RSX V2 comes out in fall '85 sometime. Very handy for communicating at high rates between Unix and real OSs like VMS or RSX. 10. In [.WINDOW] is a program (which works only on VMS version 4 or higher) which allows the user to simulate having windows a la the Appolo or MacIntosh. 11. In [.YASS] is Yet Another System Status program that will display information about the processes on the system. G. Everhart May, 1985 ========> [VAX85A.SASLAM]AAAREADME.TXT;2 <======== The two subdirectories included are MOD.DIR Contains the PIC stuff. PIC is plotting program that works as a picture editor. Written in Modula-2 SDCL.DIR A compiler for structured DCL. Allows one to write command procedure with if-then-els, while, for, do-while contructs (a-la C). Written in C. Please send comments and suggestions to Sohail Aslam CS Dept. University of Colorado at Colorado Springs PO Box 7150 Colorado Springs, CO 80933-7150 (303) 593-3332 ========> [VAX85A.SCREEN]AAAREADME.TXT;1 <======== DECUS submission from the Florida Solar Energy Center, May 1985. Contact: Jeff Burch, FSEC 300 State Road 401 Cape Canaveral, FL 32931 (305)-783-0300 Subject: A screen management library for FORTRAN programs is described that allow "EDT" like data entry from the user's terminal. Currently, this package works only on VT100 compatible terminals and makes extensive use of the keypad for fancy curser movement. For a quick preview, run the demo programs and hit the PF2 key to view the help functions. Background: At FSEC, many FORTRAN application programs are in use that require extensive data input and modification from the user via the terminal. For instance, a building thermal simulation program may have many parameters that the user can change before program execution, or a mailing labels programs requires significant terminal input for new additions, deletions, modifications, etc. This screen management library serves as a standard interface for programs requiring elaborate data entry. The screen is defined in a simple ascii file that can be produced with any text editor. The layout of titles, labels, prompts, etc are created directly where they should appear on the user's screen. Data fields are defined with a sequence of "_" characters. The applications program opens the screen definition file, loads three screen arrays for integer, real and character data and makes a single call to the master screen routine. The user modifies the data fields displayed on the screen and returns control to the application program by typing a control-Z. The keypad definitions parallel those of the standard VAX EDT editor (eg: keypad 2 is EOL and the sequence PF1 & keypad 2 is DEL EOL). Type PF2 for help. The keypad can be toggled between applications and numeric mode by the PF3 key. Entry into the data fields can be either in insert or exchange mode. The keypad "." key toggles this feature. Implementation: This screen library works only on VT100 compatible terminals. The program check the value of the DCL symbol "terminal_type" which must be equal to "V100" for the routine to continue. If the program is run in batch mode or from a command file without DEFINE/USER_MODE set, the program will read data from the command file and will not attempt to do fancy screen IO to TT:. This is my first submission to the DECUS library, more documentation will be coming in future releases. Study SCR_SCRIN, the demos, and the demo screen definition files for more information. The routine SCR_RDSECT gives more info on the screen definition files. The SCREEN.FOR is the include block and defines all global variables. Best of luck! ========> [VAX85A.SENDNET]AAAREADME.TXT;2 <======== This submission is from Institut Fran\ais du P{trole (I.F.P). IFP is a research institute involved in petroleum. Author is Dr. J.Dutertre Data Processing BP311 92506 RUEIL MALMAISON CEDEX FRANCE Tel : (1) 752 61 86 Telex: 20 30 50 F SENDNET is a utility to keep a VAX network, with or without clusters, under control as far as software is concerned. It is meant to help the system manager, programmers and sometimes the users. All necessary files are on the tape including a utility library. Look at SENDNET.RNO and SENDNET.HLP note that SENDNET.FOR is actually called SENDNETB.FOR. this was due to a conflicting name during a change of version. ========> [VAX85A.SKUNK]AAAREADME.TXT;2 <======== The directory [.SETDEF] contains a SET DEFAULT DIRECTORY utility program that runs under either VMS V3.x or V4.x. The directory [.EDT] contains a version of the EDT editor under VMS V4.x that allows the user to spawn subprocesses from within the editor. Dennis Jensen, Ames Laboratory ========> [VAX85A.STREAMCVT]AAAREADME.TXT;2 <======== This directory contains two programs which are useful for handling "foreign" data. The program STREAM and its subroutine FTLOCC were written to break apart stream-CR or stream-LF data files. The subroutine NEXT has been used to swap bytes on data tapes from IBM and HP machines and to convert IBM floating point into VAX floating point. NEXTTEST is an example program which shows the usage of NEXT in picking up the "next" bits in a word. As usual with DECUS SIG TAPE programs, I do not warrant the usefulness or accuracy of any of these programs. We do use them at the Oceanographic with good results and i expect that they will work for you as well. I will try to help anyone who needs help using them. You may contact me at Thomas W. Danforth Woods Hole Oceanographic Institution Woods Hole, MA 02574 617-548-1400 x2876 ========> [VAX85A.SZEP]AAAREADME.TXT;1 <======== ACMGR. ------ ACMGR is a home-brewed tool for management of user accounts in an academic environment. It can be accessed via the command $acmgr == "@ac$mgr:achdlr" . ACHDLR is a simple menu-handler for the program. The files included on this tape are: ACHDLR.COM menu CLASAC.COM add a new class DELSUB.COM delete a subdirectory DELTREE.COM delete a directory DQUOT.COM modify disk quota for user HANDIN.COM permit GROUP(:RE) access to a file HIDE.COM restrict GROUP(:RE) access LSTUSR.COM list the users in a class MORAC.COM add more users to a class README.1ST these notes REMAC.COM remove one user account RESETPW.COM reset a user's password V134.DOC session notes for DECUS Spring '85 Any questions concerning the workings of this program should be dirrected to: Steven Szep Pratt Institute Computing Resources 200 Willoughby Avenue Brooklyn, NJ 11205 (718) 636-3609 Caveat: Page 2 While we believe that this presentation describes user accounting facilities under VAX/VMS V3.5, neither I nor Pratt Institute can be held responsible for any inaccu- racies. ========> [VAX85A.VEVLE]AAAREADME.TXT;2 <======== _______ _______ __________________________________ | | | | / \ | | | | / \ | | | | / __ ____________ \ | | | | / / | | \ | | | | | / / | | | | | | | | / / | |____________/ / | | | | / / | / | | | |/ /______| ____________ \ | | | | \ \ | \__________/ | | | | __________ |____________/ | \ / | / \ / | / \____________________________/ |__________________________/ The University of Alabama at Birmingham Submissions for the Spring 1985 VAX SIG tape -------------------------------------------- [...UAB.RMDEMO] -- Update of RMDEMO, a dynamic user display program. Uses the terminal independent screen routines. Has been modified to allow multiple display pages, among other updates and bug fixes. [...UAB.GRADE] -- Update of GRADE, a class grading program. Uses the terminal independent screen procedures and the VTxxx line drawing character set. Should be used on a VTxxx terminal. Allows dropping of grades, selectable by the instructor. Calculates scores needed to make A, B, and C. Calculates class overall average as well as class average for each score. Has various types of printouts including some suitable for posting and some suitable for distribution to the student. GRADE will also build a sequential, ASCII file for easy storage and will load from a sequential, ASCII file for easy recall of student information. [...UAB.SMAUG] -- New submission. We run this program as a detached process to lower the priority of users using more than their share of the CPU. A user's share of the CPU is calculated as a function of the number of users on the system. SMAUG also allows the exclusion of some programs (we exclude FRODO if it is being run from terminal TXB2, which is our graphics station) and SMAUG will not tamper with Page 2 users who are already running at elevated priority (>4). SMAUG is written in VAX FORTRAN so modifications should be simple if not trivial. ========> [VAX85A.WATCHDOG]AAAREADME.TXT;8 <======== W A T C H D O G This directory contains a program, WATCHDOG, original was taken from a DECUS tape and the authors unknown, it was rewritten at American Satellite Company. This program monitors interactive processes and logs processes off that have been inactive for some time period. A interactive process is a process that is attached to a terminal. The process can be network process, a spawned process, or an interactive process WATCHDOG does not care as long as it is connected to a terminal and not HIBERATING. When a process is being logged off a message is sent to the central operators. Warning messages are sent to users terminals except under the condition when the process's main terminal is set for no broadcast or when a main process is suspended and the subprocess needs to be logged off. A command file is included to build the program called WATCHDOG.BLD. To start WATCHDOG you may use WATCHDOG.COM, this file may be put in your sys$manager:systartup.com. George H. Walrod III MS-34 American Satellite Company 1801 Research Boulevard Rockville, MD, 20850-3186 (301)251-8485 ========> [VAX85A.WATSON]AAAREADME.TXT;2 <======== SUBMISSION FROM THE BERGEN RECORD CORPORATION 150 RIVER STREET HACKENSACK, NJ 07602 ALLEN A. WATSON MANAGER, SYSTEMS TECHNOLOGY (201)-646-4111 This directory tree contains several submissions in three sub-directories: .COM -- Collection of many command procedures in use at The Record, some of which were included in the notes for my talks on DCL command procs at Anaheim and New Orleans (Fall 84, Spring 85). Most are documented in the help library COMFILES.HLB. See also the AAAREADME in this directory. .SYSMON -- A collection of system monitoring tools and command procedures, most of which are accessible through a menu interface. .TALKS -- the notes from several talks given at the DECUS symposia, including: Adjusting Working Set Parameters Nifty Things with DCL procedures Comparison of Two Versions of EMACS Introduction to TECO for programmers Browse through the other files I will throw in. .VAXDOC -- A coordinated set of command procedures to implement a word processing system using RUNOFF and EDT. Includes spelling check, screen review of documents, automatic indexing of documents, archiving, etc. Full use of this system requires some packages available on earlier DECUS VAX SIG tapes, but it can be used with only standard VMS software. User manual is also included. ========> [VAX85A.WENDY]AAAREADME.TXT;1 <======== This is a VMS version 4 comaptible version of SD, a popular set default program which has appeared on past VAX symposia tapes. Submitted by: Wendy Koenig Strategic Information 80 Blanchard St Burlington, MA 01803 (617) 273-5500 ========> [VAX85A.WENTZ]AAAREADME.TXT;1 <======== ============================================================================ F M S M E N U V2.1 ============================================================================ FMSMENU is an interface between DCL and FMS which allows command procedures to be menu driven. The bulk of the documentation for this program is in HELP.SLP All questions and/or comments should be directed to: Eric Wentz General Electric Co. Nela Park - Noble Road #1782.00 Cleveland, Ohio 44112 ---------------------------------------------------------------------------- Installation checklist: 1. Invoke BUILD.COM to compile and link FMSMENU.EXE 2. Apply the two SLP files to FMSDCL.CLD and FMS.HLP which are located in the FMS distribution kits by typing: $ EDIT/SUM FMSDCL/UPDATE=CLD.SLP $ EDIT/SUM FMS.HLP/UPDATE=HELP.SLP 3. Put FMSMENU.EXE in the SYS$SYSTEM directory. 4. Set FMSMENU.EXE for world read access. 5. Install the modified FMS.HLP in the system help library: $ LIBRARY/HELP SYS$HELP:HELPLIB FMS 6. Install the modified FMSDCL.CLD in the system DCL tables: $ SET COMMAND /OUTPUT=SYS$SHARE:DCLTABLES - /TABLES=SYS$SHARE:DCLTABLES FMS 7. Re-install the DCL tables $ RUN SYS$SYSTEM:INSTALL INSTALL>SYS$SHARE:DCLTABLES/REPLACE INSTALL>^Z 8. The next time you boot the system, you may purge the old copy of DCLTABLES if desired ---- End of AAAREADME.TXT ---- ========> [VAX85A.XLISP]AAAREADME.TXT;1 <======== XLISP V1.4 This account contains source, documents, and a VMS .EXE file of XLISP V1.4, an object-oriented dialect of LISP. This dialect runs on PDP11 (DECUS C), VAX (VAX11C), and 8088 and provides a fairly reasonable learning LISP. D. Betz.