RSX/IAS SIG Tape Distribution - Fall 1983 =========================================== This is the RSX/IAS SIG Symposium Tape from the 1983 Fall DECUS Symposium in Las Vegas. The tape contains material submitted by the user community for the tape at that meeting. The programs on this tape are from user submissions. The DECUS staff, the RSX & IAS SIG staffs, and DEC are all in complete ignorance of the contents of the tapes. No warranty of any kind is implied in the distribution of these tapes. The programs may or may not be well documented, they may or may not work, they may even crash your system. If you have a problem with the contents of the tape, contact the author of the program. Do not contact DECUS, DEC, or the RSX or IAS SIG's. The tape contains over 2000 files requiring 60,000 blocks of disk space. Since this will fit on a single 2400 foot tape only in BRU at 1600 bpi, it is being distributed as such. Because it is larger than an RK07 disk, it has been split into 2 BRU container files, with the 1st (/BAC:RSX83B) as an RK07 image (of 42,000 blocks), and the 2nd (/BAC:LBLTOOLS) as an RL02 image containing the new LBL Tools distribution in about 16,500 blocks. Directory [300,1] contains the files documenting the contents of the tape. The following files are present: RSX83BTPE.DOC contains an abstract of the contents of the tape by UIC. 83BREADME.ALL contains a concatenated list of all the README files on the tape. RSX83B.DIR contains a directory of all the files on the tape (BRU does not produce nice directories). SUBMIT.DOC contains guidelines for submissions to the RSX/IAS Sig Tape collection. This is MUST reading for everyone who desires to submit a program to the SIG tape. BEGIN83B.DOC has a copy of this text. UICSET83B.CMD contains the UFD commands to create all the needed UIC's on a device whose name is asked for in the command file. Edit it to match your needs before using BRU to extract the tape contents. A word of caution: under at least some circumstances, 11M V4.0 BRU's /UFD switch creates directories even when it doesn't put anything in them. Glenn C. Everhart RSX/IAS SIG Tape Copy Coordinator RCA GSD Engineering ms 206-1 Rt. 38 Cherry Hill, N.J. 08358 (609)-338-6022 RSX FALL 1983 README FILES Note: The LBL Tools were resubmitted in Fall 1983 also and their documentation appears in UIC [307,30] and following in the second backup set on the tape (LBLTOOLS). The following are the READMEs on the first backup set, which consists of all other submissions. ================================================================ ================================================================ ================================================================ [300,70]README.1ST Frank Penner System Programmer G. D. Searle & Co. 4901 Searle Parkway Skokie, IL 60077 (312) 982-8231 This submission includes a version of my FCB program that was on a previous DECUS tape, modified for RSX-11M-PLUS V2.0. FCP.TXT is a discussion of F11ACP tuning on same. ================================================================ ================================================================ ================================================================ [300,130]README.1ST RSX Systems Programming in C Anthony E. Scandora, Jr. Science Applications, Inc. 1701 E. Woodfield Road, Suite 819 Schaumburg, IL 60195 DRAFT February 9, 1984 This submission to the RSX/IAS SIGtape contains quite a few files that make it easy to use RSX's facilities from C. They have all been developed to serve real needs and are being used in production programs written entirely in C. That is not to say that they are all perfect. When I typed up all of the EMTs, for example, I did not try them all. I have used many of them, and so far, they have all worked. The documentation uses the latest Runoff from the RSX/IAS SIG's Runoff Working Group, which is on this tape in [307,50] (I think). Files are in the following directories: [300,130] Documentation [300,131] EMT header files: *.h defining structures *.emt defining xxx$S forms of all the EMTs *.dpb defining the DPBs as structures *.ast and *.sst defining all of the ASTs and SSTs [300,132] SYSLIB interface fcs.h defining FCS, CSI, GCML control blocks fcscal.mac interface routine to FCS, CSI, GCML $EDMSG interface routine [300,134] FMS-11 interface fdv.h defining arg block, req arg block as structures C-callable interface routines to all FDV functions I will submit a more complete version to the next SIG tape in June, including RMS-11 and Fortran interfaces. Until then, good luck using this stuff. I would appreciate hearing from anyone who is using it. If you have corrections or suggestions, let me know. If you make changes, please send them to me so I can incorporate them into future releases. ================================================================ ================================================================ ================================================================ [301,100]README.1ST ** CRTLIB -- VT100 Control routines ** Files: CRTLIB.DOC ;Documentation for CRTLIB CRTLIB.OLB ;Pre assembled library CRTLIB.ULB ;Sources, command files, and documentation. DEMO.FTN ;A test program which uses CRTLIB MAKLIB.CMD ;Command file for creating CRTLIB.OLB from CRTLIB.ULB Abstract: CRTLIB was created to enhance several of our screen oriented, interactive programs. The main objective was to eliminate, or reduce the jerkey fashion which the screen was updated. To do this, instead of having each routine do QIO's to the terminal, we send the output to a central buffer, and output that buffer when it fills. This library will give the user access to most of the features of a VT100 with AVO. Several routines are included which ease the use of the VT100 function keys. Building the library: MAKLIB.CMD will build the library, a copy is also included in CRTLIB.ULB. Simply issue the command "@MAKLIB". A prefix file (VTPRE.MAC) is also included in CRTLIB.ULB. VTPRE.MAC defines some hardware features that are used by CRTLIB. A test program (DEMO.FTN) is included to test the library. Documentation: CRTLIB.RNO is also included in CRTLIB.ULB. A copy (CRTLIB.DOC) is included for reference. Note: This library has only been tested under RSX-11m V4.0. It works for us, but this library is to be used at your own risk. Author: David A. Truesdell UCLA-Crump Institute for Medical Engineering 6417 Boelter Hall W. Los Angeles, CA 90024 ================================================================ ================================================================ ================================================================ [307,50]README.1ST [307,50] README.1ST RUNOFF (version S1.4) -- DECUS Fall '83 Symposium Distribution This submission is a further development of a version of RUNOFF which was submitted to the last three symposia under this UIC ([307,50]). (Earlier submissions were labeled as versions M3.0X and M3.0.) This version of RUNOFF is currently supported by a Working Group of the RSX Special Interest Group. The working group intends to continue adding features to this version of RUNOFF, including features available in other versions "out there" and features not known to be available in any version. Features added since the Spring '83 submission are described in the file CHANGES. as items 95-99. Several bugs have been fixed. The notable changes are: o Added the ability to suspend processing of the input file and get input from another file. When the secondary file is completed, processing of the original file resumes. o Added the ability to limit hyphenation to only those points spcified in the input. (This provides the ability to supress the algorithm RUNOFF normally uses for hyphenation.) o Added the ability to have pages numbered consecutively throughout a document even if the CHAPTER and APPENDIX commands are used. o Reworked the processing of blank lines automatically output by commands so that excessive blank lines are not output when such commands occur in succession. o Added the ability to turn off the significance of all the RUNOFF "special characters." o Fixed the processing of subpages so that subpage letters appear in the index and tables of contents. o The default tabs are now set if no argument at all is supplied to a TABS STOP command. o During processing of LITERAL sections, each page mark (formfeed character) in the input causes a new output page to be started. README.2ND contains an annotated list of all the files submitted and provides installation information. Submitted by: Chuck Spalding Adept Technology, Inc. 1202 Charleston Road Mountain View, CA 94043 (415) 965-0557 [307,50] README.1ST -- EOF ================================================================ ================================================================ ================================================================ [307,110]README.1ST Multi-trek (Multiplayer startrek) ---------------------------------- This account contains an enhanced M/M+ version of M-trek from the Miami RSX tape (Fall 81, I believe) which was written for IAS. This is a "must have" for those of you who haven't seen it yet. If you liked startrek, you'll love M-trek! No more fighting nameless Klingons & Romulans, now you can destroy your friends (if you're fast enough). M-trek is a real-time shoot'em up where your enemies are the other players. It's got lots of weapons & strategy, but you'd better learn to use them instinctively because the game goes on whether you do anything or not. Even if you've got the Miami (or later) version, this one is probably worth taking a look at. The enhancements make play significantly different (and faster). In addition to some general restructuring and bug fixes, this version: - runs on RSX 11-M or M+ (tested on M v3.2,4.0 & M+ v2.0,2.1) - allows named ships so you know who you're fighting - includes an "auto-default mode" which eases wear & tear on your finger - includes keypad navigation from the VT100 numeric pad - flashes the VT100 screen when you get hit - has a few new commands (including "plot torpedo intercept course") M-trek is written in RATFIV, a structured FORTRAN, but the FORTRAN source is also included in case you don't have the RATFIV preprocessor (which is available on several of the RSX tapes). Task images are also included so you may be able to run it as is. To compile & taskbuild it use MTREK.CMD; to start it up use MTREKUP.CMD. The taskbuild and command files have been tested on M+ v2.0, but as usual you may want to look at them to be sure they're right for your system. See MTREK.DOC for rules & commands. George Whittlesey Chevron Research Co. 576 Standard Ave Richmond, CA 94802 (415) 620-3126 ================================================================ ================================================================ ================================================================ [350,240]README.1ST ********************DR0:[350,240]README.1ST;1******************** ********************DR0:[350,240]README.1ST;1******************** Activity monitor for RSX-11M/M+ V3.2 The account contains an RSX-11M/M+ activity monitor. When running, it keeps track of time spent in each task as well as the exec. It counts directives and gathers I/O statistics. The MONITOR.HLP file explains this in greater detail. A sample run of the monitor program is contained in the MONITOR.RPT file. I originally got these programs from a friend of mine. We tried it and liked it so here it is for the rest of the DECUS community. Please note that it was written for V3.2 of RSX-11M. It usually works quite well there. I have tried it on V4.0 and V4.1 but have never had the time to update it for those execs (we do not have M+ so I can't speak for it). I am submitting it now because I simply don't have the time anymore to bring it up the the V4.1 rev level. I had planned to submit it when V4 came out. Seeing as that didn't make it, I thought for sure on V4.1. Well, we are now moving into the VAX world which means there is no way I'll ever have the time to work it. I am hoping that there are those of you who would have the time to bring it up to snuff. If any of you would like to work on it, I'd be happy to coordinate the efforts. In order to use the activity monitor, type @MONITOR. It will assemble and taskbuild the routines for you. To run it, type @STARTMON. To stop it, type STM. The MONITOR.HLP tells how to run it. There is also decent documentation within the code itself. Note that you might want to put the task images under [1,54] after you are sure that it isn't doing nasty things to your beautiful exec. And by the way, I can't be responsible for these programs possibly corrupting your system. They should be used with care and you should experiment with them a bit before you blindly go ahead and use them. Mike Drabicky Rockwell International 1200 N Alma Way MS 406-280 Richardson, TX 75081 (214) 996-7532 ================================================================ ================================================================ ================================================================ [312,315]README.1ST [ 312,* ] Collection A number of utilities are presented. Among them: [312,315] VMSCOMLIB - A version of the COMLIB module of BRU (V4) patch code to attempt to correct problems under VMS. The module has not been tried, but corrects a problem that prevented BRU from writing to mounted disks with the /NOINITIALIZE switch under VMS. May even allow writing to ODS-2 volumes, since the ACP does the actual allocation and only write-virtual-block is used to write the data (though sysprv may be needed). Don't turn loose on an ODS2 pack with LOG_IO privilege; shouldn't need it, and may cause mischief if the priv is set. ATT - file attributes read/write, from a very old RSX SIG tape and reissued because of its' great usefulness. Allows any file attributes to be listed or changed (including carriage control attributes, fixed record length max length, etc.). LISTRS - Reissue of multicolumn lister. A switch for controlling what continuation line indicator is generated was added. In addition, the program has been modified to clear the high bit of all characters passed through it. This allows it to filter out such characters, which can be introduced by moving files edited with programs such as Wordstar on micros onto PDP11 or VAX machines. LST will also filter out tabs, but programs such as LBL Tools Entab can put those back. DGT - TAR, DG, IBM, etc. etc. tape reader/writer (only reads TAR tape). Some small improvements over S83 version including better magic number recognition for TAR (Unix) tapes. Now recognizes and correctly identifies archives and object files as well as program code image files as not just regular ASCII. Also fixes some minor glitches with junk after the last real line of text from a tape file. ORC - ORC disassembler from DECUS with additions to allow you to tell it whether a PSECT should be handled as code or data. Handy for compilers that don't set this attribute right. However there are cases where symbols don't make it to the output file. Still, ORC will handle some object files that crash DOB from earlier SIG tapes, making it useful to have around. [312,360] IAS VDDRV and ASDEV - old IAS drivers for virtual disk that optionally encrypts data and performs LOTS of access checking with hooks for user customization. Also driver for terminal like device that can set input or output (or both) to come from/ go to any file via separate MCR ASSIGN command (MCR task source supplied). These are from F78 but work in current IAS versions too and are supplied due to the difficulty of locating the old tapes in some quarters, by consultation with the IAS SIG. [312,345] Latest PortaCalc spreadsheet for RSX or VMS, including a VMS version that uses memory instead of a scratch file. The version the default COMPILVM command builds is twice as large in capacity as DECALC, runs MUCH faster, and does more. Some tutorials are supplied also, and numerous bells & whistles & helpfile features. Matrix math, equation solving, iterative searching in up to 8 dimensions for solutions to systems of equations, and similar fancy things have been added. Also the VMS version now allows you to spawn DCL commands while staying in the spreadsheet. [312,366] PortaCalc-XL This is a version of PortaCalc for RSX which uses (finally!) virtual arrays to allow a large sheet. The default build file creates a sheet 60 by 65 lines max (rearrange the storage as you like) with a variable length workfile (if you don't need the full capacity). It is a full capability PortaCalc, but with enough storage to handle fairly large problems. It has been known to run in a 50K GEN partition on an 11/34, so should run on basically any mapped RSX11M or M+ configuration (and in numeric directories under P/OS it should be fine). Use with the FX driver (see below) to get the workfile into memory if you wish. [312,322] VE: Update to VE: multi-disk (or single) RSX M/M+ virtual disk. Supports current M/M+ releases, has security subsystem, and has ability to make single directory disks easily, so that one unit may be used as location for PortaCalc aux keypad files & help files. [312,346] FXDRV, finally updated so it works. This version has builds for M/M+ and checks the fork queue after copying each block, so it won't hang up your system's fork processing. The load commands supplied also show you how to set it up as a single directory device so you don't waste space with multiple UFDs on it. Handy for super-fast virtual disks if you have 22 bit machines with some memory that doesn't fill up very often. [312,365] DTC This is Desktop Calendar, a useful time management program from DECUS. It works on VT100 and needs F77 to compile it. While it is a bit inflexible in some command input formats, and needs better documentation, it works reliably and allows you to keep track of your schedule, schedule meetings, and/or display calendars and move around in them in a fairly simple way. A note to the wise: the Date command is ALWAYS of form D date hh:mm message where "date" can be in any of the usual formats, but hh:mm MUST have the colon, hh MUST have leading zeroes inserted, and both date AND time MUST be given when putting "message" into the calendar. Note however that the T command may be used, if DTC is installed, to permit an indirect file to fill in defaults and pass an edited command back to DTC to essentially free you from these restrictions. Glenn Everhart RCA G.S.D., Cherry Hill NJ ================================================================ ================================================================ ================================================================ [312,322]README.1ST VEDRV (Modified VDDRV) ABSTRACT: The VE: package is an RSX M/M+ Virtual Disk package permitting multiple files or devices (or mixtures) to be associated together as single virtual disks. Currently up to 8 such may be so associated, though more can be added easily by reassembly. The mnemonic was changed to VE: from VD: in order to permit the old virtual disks to coexist with it. They provide greater protection against inadvertent errors, but less capability for free association of devices. DESCRIPTION: This version of VEDRV is a mod from the VDDRV on [307,100] of F81RSX for M or M+. It incorporates changes which will allow it to link multiple files into a single virtual disk. It assumes that the virtual disk is 1 block longer than would be obtained from each file, with the extra block being a pseudo block that will always return an error on access. Thus, if you create a virtual disk and run BAD, those blocks will be marked bad, RSX will never attempt a QIO$ across file boundaries, and the driver is nearly as simple as the original. At present, AVE will allow up to 8 files to be assigned to a virtual disk (change VEPRE to increase). You must define M$VE$$ in VEPRE to enable this stuff. The driver's name was changed to VE: so that the 2 types of virtual disks can coexist in a system. Because there are NUMEROUS ways you can screw up with this driver (for instance, command errors in AVE will zero the disk size, or you can forget the order in which parts of a VE: are assigned), it was thought that you would be best off able to use the old VD: drivers where only single file assigns are needed. It also makes it easier to test VE: if all blocks are on a virtual disk.) Some minor kludges and caveats: 1. AVE will not lock the files any more and DVE won't unlock them. I thought that keeping multiple filename blocks in pool is too costly. Only the first is even kept and it is not really used. 2. Checking is rather minimal and if you don't run BAD first to add bad blocks to a badblock file, you'll screw up. 3. The driver will actually genrate a pair of bad blocks together at boundaries, plus one at the end of the disk. BAD will find these. Up to 8 files or devices may be associated with each VE: unit (as presently done; re-edit VEPRE to alter this if more are needed). If you try to assign more, the AVE program is supposed to tell you. The message is that the VE: unit is already assigned. (This was a 3 hour edit). Further additions include the AVEX program, which is also off an old DECUS tape but modified for this package. It allows you to use all or part of physical disks for virtual ones, by logical block number, so you can make several small disks look like one bigger one. Thus, you can make your 2 RL01's look like an RL02 or some such thing. It is a good idea to use the /INitialize switch on the first AVE to a virtual disk, just in case the old size was not zeroed in the UCB of the thing. DVE will zero the size, but if you ever bypass it, it'll be just too bad. This AVEX is also handy for preventing wild BRUs from clobbering your disk...as was the original. Since this version derives from one that is OK on M or M+, it should be so again. Note the UCB (I think) gets another 4 words in V4 of M or V2 of M+. It should be clear from the manuals where. Make that change before using on V4 or V2 or your system'll crash! Because of the ease with which one can forget the names of files or disks which are assigned, I recommend STRONGLY that you ALWAYS DRIVE AVE or AVEX from COMMAND FILES (i.e., using indirect MCR). This will give you a way to trace what you have. Glenn Everhart Further Note: This package can be built for various systems by the command file VEGEN. It allows VE: to be set up for single file use or the multifile use described above, and configured for the old versions of M or M+ (V3.2 or V1), or for M V4 or M+ V2. The thing is tested in M+ V2 but not in M V4 since I don't have an RSX11M V4 system handy. However, it looks like it'll be OK for M V4. There are some extra versions of AVE, DVE, and AVEX with longer filenames as well as the ones VEGEN uses. They attempt to support the new M+ V2 functionality of external headers by the DEC-suggested code changes. However they are NOT tested; try at your own risk. VEGEN will built the normal ones with no external header; they work but take a bit of pool for the headers. This may not be a problem however, if you use CCL to install-run-remove AVE and DVE rather than leaving them installed permanently. Glenn Everhart ================================================================ ================================================================ ================================================================ [312,345]README.1ST PortaCalc Brought to you courtesy of Glenn Everhart 409 High St. Mt. Holly, NJ. 08060 USA Version 7.0 and 7.0-VM, Fall 1983 This version of PortaCalc is smaller, faster (by a large factor) and more capable than the ones on Fall '82 SIG tapes. It is now fully 3 dimensional as well (by a reasonable definition of that.) Also, the keypad finally works on VAX as well as PDP11. See KEYPAD.DOC for info on the supplied default command files for implementing keypad functions. This spreadsheet finally can do matrix math and has (in the usrfct.src module which may be optionally included for VAX) some routines for iteratively searching up to 8 dimensional spaces for solutions to problems. It is the first spreadsheet able to do really significant math in addition to the simple routines needed for finance calculations. ABSTRACT: The PortaCalc spreadsheet is a FORTRAN written program able to perform the usual "what if" types of calculations for anyone with a compiler, 31KW of task space (more or less), and (in the present version) an ANSI 3.64 terminal (e.g. VT100). The program is easily recustomized for other terminals and designed for portability and functionality. A data management system interface is built in, permitting spreadsheets to access a potentially unlimited number of files and records or parts of records in those files for user defined functions, numbers, formulas, text, or whatnot. In fact it has many of the attributes of a language. Three versions are provided, with complete source code for all: a PDP11 version for I/D space machines that builds flat under RSX11M+, an overlaid version for other mapped PDP11's under regular RSX (11M or 11D/IAS), and a version for VAX that builds (flat of course) under VMS. I assume the F77 compiler but the program is in Fortran 66 (I use the /NOF77 switch). It is expected only minor changes would be needed for the DEC Fortran IV compiler however. A separate graphics output task is documented in PCG.DOC and provides histograms or scatterplots of any areas of the saved spread sheets with a simple command syntax. RESTRICTION: The overlaid version provides only a rather small spreadsheet, though it is large enough to be useful in many applications. There are some overlay tricks I haven't tried to increase the size, notably clustering. SPECIAL HARDWARE: The software must be built for the appropriate terminal. Versions of the UVT100 subroutine for VT100, VT52, Datamedia Elite, and several other types of terminals including VT100 with Advanced Video and Colorscan 10 are supplied, with command files for most combinations. The VT52 version will show what the minimum requirements are for control. Most any terminal can be easily interfaced to the package by editing one of the UVT100 routines to correspond to the terminal's control sequences, provided direct cursor addressing is supported. BUILD: There are 5 major build files. COMPIL.COM Build for Vax/vms...only compiles. Concatinate the objects and link. The next 2 files build 128 by 256 sheets by default. COMPILVM.COM Builds a VAX/VMS version of the sheet that does not use a random access workfile on disk (and may run a bit faster than the standard one for that reason) but with all other capabilities. COMPILVMX.COM Builds a version of PortaCalc for VMS that does not use a workfile, runs even faster than COMPILVM's does, and has extra features. The *U XQTCM function allows a command file inside any cell to execute commands to the sheet (except K, X, and H), and there is a function (see the manual) to extract parts (up to 8 characters at a time) of formulas in a sortable numeric form. Also, the formulas entered may have (this version only) the following constructs which will be edited into the formula as entered (so a command file can enter them): _@V1,V2 Means get the values stored in V1 and V2 and use them as column and row locations pointing at some cell in the sheet. Replace the construct with the name of that cell. _#V1 Means take the real number in cell V1 and unpack it as if it had been a packed value from a formula with 8 characters packed; then convert it back into ASCII and place in the formula in place of this construct. MAKE.CMD Non-overlay I/D space build for RSX11M+ V2 (uses F77 Compiler in non-F77 mode) SOMAKE.CMD Compact overlay structure, OK for any 11, RSX11M/M+. Note: THERE ARE COMPILER WARNINGS (ABOUT FUNCTION "INDEX") WHICH SHOULD BE IGNORED DURING THE BUILDS. I ASSUME FORTRAN 77 IS INSTALLED AS ...F4P. PRIOR TO BUILD: You must be sure the final VKLUGPRM.FTN is as you will need it. The PDP11 command files generally copy one of the template versions to this file, but the parameter file may be edited as may any template. The VAX versions of command files generally assume you know what you have is right. READ the appropriate template. Supplied templates include: VVKLUGPRM.FTN VAX "standard" version for VT100 with or without AVO BVKLUGPRM.FTN VAX "big" version for VT100 VVKLUGPR5.FTN VAX "standard" version for VT52 systems BVKLUGPRM.FTN VAX "big" version for VT52 terminal use MVKLUGPRM.FTN PDP11 version for RSX11M+ V2 I/D space, VT100 MVKLUGPR5.FTN PDP11 version for RSX11M+ V2 I/D space, VT52 SVKLUGPRM.FTN PDP11 version for RSX11M/M+ overlain, VT100 SVKLUGPR5.FTN PDP11 version for RSX11M/M+ overlain, VT52 HVKLUGPRM.FTN VAX really huge (128 by 256) version, VT100 HVKLUGPR5.FTN VAX really huge (128 by 256) version, VT52 or colorscan Note that several variants of UVT100 exist too. The ones presently included are: UVT100.FTN (.FOR for VAX) VT100 control, no Advanced Video Option (AVO) assumed. Many entries are not called by PortaCalc. The ones that are used are: CUP Cursor Position ED Erase Display SGR Set Graphics Rendition EL Erase Line ANSI set ANSI mode (may be nooped) UVTAVO.FTN VT100 control with AVO terminal support. Includes only entries needed. Also uses underline to underline alternate rows and will display display-sheet row numbers as well as physical ones. This version will also highlight negative values in intensified video. By editing to change how NUL is set in the CUP entry, this could be set to highlite entries over/under a fixed amount (put the amount in one of the letter accumulators). UVT52.FTN VT52 control. Since VT52 terminals have no reverse video, draws a ">" character in first col. of cell pointed at to indicate cursor location. UVTDM.FTN Datamedia Elite 1500 control. Similar to UVT52 but cursor controls for Datamedia. UVTCS.FTN Datamedia Colorscan-10 control. This terminal uses VT100 sequences, but UVTCS will use some of the color setup sequences to create a multicolor spread sheet. Colors are now used for showing negative numbers and work in a sensible screen design now. Negative numbers appear in red; positive ones in yellow. UVTTV925.FTN Televideo 925 experimental version. This version has not been well tested but is intended for Televideo 925 terminals. You may easily adapt the UVT100 subroutine from any of these to handle whatever terminal you have using these routines as examples. Note the parameter JVTINC in the VKLUGPRM.FTN which adjusts for the backspace generated by UVT100 on SGR calls needs to be set correctly. Adapting UVT100 to your terminal and setting up VKLUGPRM.FTN correctly are the necessary setup actions needed prior to compiling and building PortaCalc. You may of course get UVT100 to determine what terminal type is there itself, or use the VMS terminal independent cursor positioning logic, if you wish. On a VAX you may also want to inhibit scrolling. The normal PDP11 builds will make a version which attaches the terminal so no funny modes need be set. The RSX flavors of PortaCalc can use escape sequences and now recognize VT100 arrow keys (VT52 too) and also that PF2 means "help". On VMS, the ESCAPE parameter works differently so the arrow key support is somewhat flaky. Edit to use a QIO$ to read the commands to fix this if you wish, just before CMDMUN is called... Remember under VMS to copy the desired file to VKLUGPRM.FTN before compiling. Ignore compiler/linker errors in RSX or VMS. They are harmless warnings. It develops that a few compilers treat the INDEX errors as errors, not warnings. Inserting a statement like EXTERNAL *INDEX into offending programs will get them to compile however. F77 V4.0 is one that seems to mess this up. Note that in VMS you may want to run PortaCalc from a command file to set the terminal /NOESCAPE after PortaCalc exits. Otherwise EDT gets VERY unhappy (not to mention screwed up). On overlay builds, some functions (notably the F file readin function) are commented out of OXQTCMD.FTN. You may uncomment them to get the functions if things fit. They may. Journaling is commented out except for VAX versions due to number of open files needed. Uncomment for PDP11 if you wish. You should be able to build PortaCalc with regular old F4P but you may need minor changes to some OPEN statements. Note too the CMDMUN and TTYINI routines to set up the console. The supplied RSX versions implement case translation and enable the arrow keys. The VAX CMDMUN usually should be used but its' TTYINI is probably wrong and the dummy should be used. The idea is to effectively SET TERM /ESCAPE (and SET TERM /NOWRAP) on VMS to get the full escape sequences in. At least set the nowrap attribute. VMS does funny things to the escape sequences; I haven't deciphered them yet. You will find 4 user function routine areas too: USRFCT.FTN Version supporting return of system date USRFCT.FOR Supports also matrix equation solution USRFCT.ASC Supports matrix determinant, matrix value copy also USRFCT.SRC Supports matrix multiply/add/subtract also, and general functional vary for VAX. Note the USRFCT programs are designed to be points for you to plug in your favorite statistical subroutines. They'll need extra routines which you'll find sources for here (things like MTXEQU, MDET, GMSUBS) which may not be well included into command files. However, they may be linked together and used to support functionality far beyond that of conventional sheets. WHEN BUILDING PORTACALC, YOU MAY ENCOUNTER FORTRAN WARNINGS ABOUT THE INDEX FUNCTION BEING ASSUMED USER SUPPLIED. IGNORE THESE; THERE IS AN INDEX FUNCTION SUPPLIED HERE, AND THE WARNINGS ARE OF NO CONSEQUENCE, EITHER ON PDP11 OR VAX. ================================================================ ================================================================ ================================================================ [312,360]README.VDD VDDRV FOR IAS This set of programs (vddrv, vdkdrv, vdprv) is a virtual disk driver for IAS or RSX11D which was originally written about 1977. It provides virtual data disks only (must NOT run tasks from them), but allows encryption and MUCH access checking of access to the virtual disks, providing secure subsystems if this is desired. Replacing the ..BLXI or ..BLXO calls with functions that can run with no task context will allow this driver to load tasks too. Note vdkdrv is a version that does not ask passwords or provide encryption, just raw virtual disks. Glenn Everhart ASDEV and its companion program, ASSIGN, give IAS a virtual device that is terminal-like. However, input and/or output may be assigned to files, and optionally output may also go to a terminal as well as a file; the ASSIGN task controls this. It gives IAS users a means to arrange for programs that try to do I/O to terminals to have that I/O captured to a file. It was devised for use with a virtual RT11 V2C which did QIO$ directly to LP:, where the desired effect was to spool the output. However its applicability was much wider. All filename parsing is in the driver, allowing a VERY simple program interface to do file I/O (just issue a special QIO with the filename string; the driver does the rest). ================================================================ ================================================================ ================================================================ [312,371]README.1ST This area contains skeleton code for a PortaCalc version which will operate in very small environments by using bitmaps, etc., for storage. The WRKFIL and WRKSHT routines are called whenever the work file was accessed or VBLS, FVLD, or TYPE are called. Strategy: Use 3 bitmaps for FVLD to represent legal states of FVLD bytes. Make a 3 bit number up from the 3 bits and treat as signed in range -3 to +3. Use 1 bitmap for TYPE array for sheet; 0 means type 2 (real); 1 means type 4 (integer). For accumulators (1st 27 items), keep full integer array of types however. Keep 45 format entries resident, filling new areas in as needed and reusing the last if the area overflows (which will seldom happen in real life). Point to the format number with a byte in the formula. Values and formulas are kept in separate areas by a symbol-table type algorithm. This will treat memory areas for each as one "page" of a file whose size is given at runtime (and not opened if too small). Cells are 10 bytes long for values (ID plus 8 byte number), 16 bytes long for formulas (ID, format number, flag (for first/middle/last cell for a formula), and 12 bytes of formula per cell with continuations permitted.) On write to a cell, the page is calculated and a hashcode used to find start address in the page to look for space to put the cell. Linear search, in that memory page only, is used to find free space (initially all old refs are cleared). For formulas, cells are allocated until the entire formula is stored. Readback reads the cells starting at the hashcode and continuing by linear search if need be. Formula storage and retrieval is done by linear in-memory search using the hashcode only in computing the page to use. Unit 7 is formula file, and 9 is value file. This permits some flaky running out of room while the file still has empty space, but makes search speed at least bounded. A big enough file will always guarantee that a cell can have room found for it. Fixed cells for formulae are used to reduce compaction problems. Other algorithms can be put in WSHEET and WRKFIL to handle this differently, to tailor to random environments. This code is NOT known to be correct or work anywhere, so users are advised to treat it as material for experimentation where they need, for instance, a huge spreadsheet on a PDP11 which need not be completely filled. It IS however designed with ALL the capabilities of the VAX version except the execution of commands from inside cells of forms like CA, CR, etc. etc. and may be interesting for that reason. Please send any versions you bring up as working back to me in source, regardless of what machine they run on. In return I may get you my latest mods and bug fixes. Glenn Everhart 409 High St Mt. Holly, NJ 08060 This version works on VAX, and may be movable to RSX11M+ systems with full functions. However, note that some displays will appear to zero various displayed numbers. An extra V (View) command will draw the display correctly if this happens. The CR command is known to do this. The memory storage is small and backs up to disk files during operation. The sizes are asked for at startup, and if they overflow, (i.e., a PAGE fills), a message is given on screen. If the sizes (in K bytes) for the files are given NEGATIVE, then a different packing algorithm is used which requires more page swaps, but may allow less dense use of the page file and permit the same size disk files to handle more active cells. The trade-off is speed. The sizes of memory areas are compiler parameters. The file present is fairly conservative but may be made smaller still. LVBF should be at least 50, and LFM at least 32, for things to make sense. The files are NOT opened or used if the memory storage sizes on file are less than the in-memory storage provided. This is the first version of PortaCalc which plays the same dirty trick on you as commercial spread sheets. That is, you have a fairly huge matrix, but can't fill in all of it without overflow. However, by specifying a large enough file for variables and for formulae, you can always get things to fit. Variables are stored in 10-byte units (2 bytes for the ID, 8 for the value), and formulas in 16-byte chunks, of which 4 contain ID, format pointer, and flags, and 12 are formula characters. A long formula will have multiple formula nodes in the buffer. Most everything else is managed with bitmaps, rubber bands, and chewing gum. Note this version is intended so that HELP can be in a separate overlay from XQTCMD and CALC. Those must be together to handle the new syntax of cell-controllable commands. However, this may give enough room for any PDP11 to use the thing by using the rest of the portacalc overlay structure from the "standard" version. Be careful, however, to ensure the commons in WSHEET and WRKFIL are resident in the root. This will probably need some .PSECT statements or putting them in the root (not a bad idea, really). NOTE THAT THIS OVERLAY IS NOT FULLY DONE AND IS PROBABLY INCORRECT IN IMPORTANT WAYS. IT ALSO WILL ONLY BARELY FIT ON BARE RSX11M+. The overlay is just a start (though the result runs OK) but is complicated by the fact that CALC calls CMND which may call USRFCT which in turn can call XQTCMD. Thus at least the USRFCT main routine needs to be in the root so the call tree works for that. Or the call to XQTCMD can be snipped out and essentially the old tree structure used with WSHEET and WRKFIL also in root. Note however that this version of XQTCMD is not as broken up as the "standard" overlay version and the put and get routines may need to be broken off to get things to fit again. Try clustering or something if possible, on M. On M+ with 11/44 or 11/70 or J-11, using I/D space and super mode FCS should be a major win. Besides, you can overlay with I/D space and just moving the HELP into a separate leaf ought to buy a lot of space. HELP is only called from SPREDSHT (the main program) so that ought to be OK. The Best things in life are free! PORTACALC ================================================================ ================================================================ ================================================================ [312,365]README.1ST DTC - The Desk Top Calender Mitch Wyle December 1982 Version 1: REVISED BY GCE The idea here is to automate an appointment calender. Most appointment calenders give only one of Month-At-A-Glance, Week-At-A-Glance, or Day-At-A-Glance. DTC is an attempt to give all of these functions in a paperless, fast, menu-driven format. This release has had considerable work done to it to make it a more general tool. See the addendum for the extras. DTC is one of a number of Paperless Office programs I have been developing for two years. Other related programs are an on-line telephone directory, an electronic mail system, an automatic "While You Were Out" message taker which spawns mail directives, Memo and Form letter templates and programs, and software tools for writers in a business environment. Is there a DECUS sig for Office Automation? Please call me with your problems and suggestions. I am very new at programming in Fortran in the DEC world. I have already developed the paperless office package on a Honeywell Level 6 running Ultimate. Source code is in PROC and Data Basic. Hope to hear from someone, Mitchell F. Wyle Data Systems Supervisor, NUS Pittsburgh Radiological Laboratory 5350 Campbells Run Rd. Pittsburgh, PA 15205 (412) 788-1080 x405 Revision 1: Glenn C. Everhart I have added a few extras to the program to make it more usable and fix a few small bugs. The following has been done: * Date bugs in displaying weeks at the beginnings of months are fixed. * The E in Evening now is a pseudo time and gets displayed as 17:00 on the weekly summary. You can enter evening appointments using the D command with E for time. (EV works OK too.) * Most commands are accepted in lower case or upper case. * Commands T (Today), R (Reminder), and C (Calendar) correspond to Day, Week, and Month exactly but cause DTC to exit after they are executed. This permits them to be used from MCR with instant exit, thus to be placed into login.cmd files for an "auto reminder" service. * Time ranges may be input (so long as it is done with no format errors) in the form hh:mm>h2:m2 (e.g. 09:00>15:30) which will replicate the appointment part of the line into DTC.DAT over the indicated range. * Purge of old appointments (clear out appointments from before a given date, defaulting to today) * Reverse display of week/month times permitting FREE times to be found and displayed rather than occupied ones (potentially for a group of people) * A second level of data files, permitting an appointment file to contain pointers (1 level deep) to other files which can be searched as well as the first * Multiple appointment files, changeable on command (permitting "private" appointment calendars) * Scheduling of appointments in multiple files (useful for setting up meetings or maintaining multiple files) * Lookup for free times of length n * 30 minutes (where n is any number in the range 1 to 18) over a week period; display of times is made in Week format. Valid start times for meetings of given lengths are shown. You will have to extract the help file DTC.HLP from the universal library DTC.ULB, and put it in [1,2]. DTC needs [1,2]DTC.HLP to execute the H option from its menu. >LBR DTC.HLP=DTC.ULB/EX:HLP >PIP SY:[1,2]DTC.HLP=DTC.HLP The tape is an ANSI tape with the following contents: 1. All source and help files of the second revision of DTC 2. DTCOLD.BCK - an RMSBCK container file of the original DTC submission 3. DTCNEW.BCK - an RMSBCK container file of the new DTC submission (in case of bad files on tape...) New commands: P [mmddyy] - Removes all appointments from current calendar file whose date is BEFORE the date specified. If no date is specified, today's is assumed. N(command) (for example NW [mmddyy] ) - Displays FREE time instead of scheduled time in week or month formats. Not deemed useful for Day format, so left out there. F filename - Closes current calendar file (defaults to DTC.DAT initially) and opens filename instead S [mmddyy hh:mm[>hh:mm]] appointment/meeting - Schedules appointment /meeting at the given time. If current calendar file contains pointers to other files (see below; year=99 and appointment part has 'filename=' in it) then each of those gets a notice of the appointment or meeting added to it as well as the current calendar. Otherwise only the current calendar file is updated in the D format. L [mmddyy] nn - Locate a period of nn half-hours in the week containing mmddyy. Displays the free time in week format. Used to schedule meetings. nn must be 01 thru 18 and is clamped to this range POINTERS in CALENDAR FILES The calendar file format is sequential records of the format: YYMMDDTTTappointment text of 60 characters length in which every record has this form, and the time TTT is in the range (for correct files) of 080 through 170 (for 08:00 through 17:00). The third digit is always either 3 or 0 as well, since DTC only schedules half hour periods. Indirection is accomplished by editing your calendar file (with any editor) or just entering an "appointment" for year 99 (by which time somebody should have hacked some more on this to fix it up not to mess up real appointments). The text of the "appointment" should be just filespec=, with the = sign as the terminator of the file spec. This will lead to the file you specified being opened and treated as if it existed inside your own calendar file (except you need to use the S function rather than the D function to enter appointments in it as well as your own.) CAVEATS: DTC is a bit touchy about illegal inputs. Be sure you input the mmddyy in the format given (i.e. July 4, 1983 is entered as just "070483", NOT as "7483" or anything else except standard date formats (like mm/dd/yy or dd-mmm-yy). If DTC seems to generate weird displays, edit DTC.DAT (or whatever else is your calendar file) and remove or edit lines in which the date or time are in illegal format. Be aware: documentation of DTC is old and in poor shape but it can be figured out and is worth it. [312,365]README.2ND DTC Rev 2 The DTC program is now revised to provide the following new functionality: 1. Year at a glance (courtesy Mitch Wyle) 2. Default date and time remain as last set now, permitting switching among day/week/month displays 3. The new I command resets default date to today 4. Command D saves appointments in the current file only, not in any files indirected from the current file via the 99999999filename.typ= format. Command S (schedule) saves appointments entered that way in files indirected, but not in the current file (leaving a file of indirection pointers clean). Command G saves appointments in both. 5. Dates may be entered in format mmddyy (as before) mm/dd/yy (new, easier; mm and dd may be 1 digit long) dd-mmm-yy (dd may be 1 digit long. mmm text is parsed only enough to disambiguate months.) Also, the Week display does a better job now when showing appointments in a first week of a month where the month changes during the week. It appears completely correct now. Also the month display has been upgraded to not overflow the screen on long months with 6 lines for weeks. DTC Rev 3 DTC now contains the new function + nnU - nnU where U may be D,W,M, or Y for Day, Week, Month, or Year. This command changes the default date by the specified increment and leaves the display alone. The default for U is the last display mode, and the default for nn is 1 so that if just a + or - is seen, the default is to move 1 unit. Glenn Everhart 6/24/83 ================================================================ ================================================================ ================================================================ [312,366]README.1ST PortaCalc XL version for PDP11 This version of PortaCalc is a variant of the standard PortaCalc package for memory-mapping PDP11's. It differs from the standard VAX or PDP11 version in that its' data is kept in a virtual array, and hence the package can handle larger spreadsheets on a PDP11 with no special functions beyond memory mapping support. The current version supports a 60 by 64 sheet, but thesize can be modified by changing the SVKLUGPRM.FTN file's PARAMETER statements which define physical sheet sizes. The version supplied is something of a quick mod to the standard version and as such has the following restrictions: 1. Only VT100 support is provided (though other terminals can be added relatively easily using the standard version's routines) Actually, there is a modified copy of UVT52.FTN which may be used in place of UVT100.FTN and which will give VT52 support. It may work OK but is less well tested than the VT52 support on the normal PortaCalc because it cannot access the FVLD array, hence may insert a few extraneous > characters, though it probably won't. 2. Matrix algebra and solution finding for general equation systems is not included 3. No use is made of supervisor mode, I/D space, or other bells and whistles available through RSX11M+ on the larger PDP11's. This version should run on any RSX 11M or 11M+ (or 11D/IAS system) with a very reasonable spread sheet size. To get this product running on the PC 350, the standard method is to put a NUMERIC directory (e.g. [200,200] as 200200.dir) into your system and place the program there and always run it from that numeric account. The command files (ak*.cmd and KY*.cmd) should be placed there also and the DK: selection option not chosen. When you build this package, just use the SOMAKE.CMD procedure. It assumes the DEC F77 compiler, but uses only Fortran 66, so older versions like F4P should work with only tiny mods to OPEN statements. ================================================================ ================================================================ ================================================================ [312,367]AAAREADME.1ST This area contains 2 simple files implementing a crude but effective reminder system in DCL. The file CALEND.COM is used to insert text into a file in the user's login account (named CALTIK.DAT) which is then able to be shown. Start and end dates are prompted for, with RETURN defaulting to today for the start date, and to the start date for the end date. The TODAY.COM file displays messages if the current system date is between the dates entered by CALEND. If TODAY is run from one's login.com file, it will remind one of appointments, things-to-do, or similar notes, at login. The notes to oneself may be any length; a null line terminates them on entry. There is no special provision for cleaning the files up; edit the CALTIK.DAT file for this function. Note that this permits reminders to be left on the system which can come back to hit you months later if you so specify. Dates are entered as dd-mmm-yyyy OR as dd-mmm-yy. If the first 2 digits of the year are omitted, the 1900 is added in. This facilitates use by people used to RSX syntax. ================================================================ ================================================================ ================================================================ [312,370]AAAREADME.TXT Submitted by: Peter M. Hahn Building 206-1 RCA Government Systems Division Route 38 Cherry Hill, NJ 08358 (609) 338-5319 This submission contains two separate Datatrieve programs which run on either VAX-11 Datatrieve or Datatrieve-11. They are in the form of separate Datatrieve indirect command files which can easily be invoked by Datatrieve by simply preceding the file specification with an @ sign. Before being able to use the programs, however, the user must know the basics of Datatrieve and must create a data file for the specific Datatrieve domain defined in the program. This is done with a DEFINE FILE command using the file name specified in the domain definition found in the first few lines of the indirect command file. The first program is for creation, maintenance, finding contents and printing of a personal address and telephone directory. It contains programs for storing entries (STORE-ENTRY), finding phone numbers (FIND-NUMBER), printing the directory (PRINT-DIRECTORY), adding missing zip codes (CHECK-ZIP), and eliminating unwanted entries from the printing process (CHECK-LIST). The pertinent data on the first program is: Indirect command file: DIRECTOR.CMD Domain name: DIRECTORY Data file name: DIREC.DAT The second program is for maintaining, printing and testing oneself on the contents of a vocabulary list and its meanings. Creating the list is done via commonly known Data- trieve commands for preparing a domain for WRITEing (READY domain-name WRITE) and storing data (STORE domain-name). Programs are included for testing (TEST-ME), printing the list (PRINT- DICTIONARY) and reintroducing list entries temporarily bypassed as part of the testing process (TEST-WORD). The pertinent data on the second program is: Indirect command file: VOCABUL.CMD Domain name: VOCABULARY Data file name: NEWVOCAB.DAT ================================================================ ================================================================ ================================================================ [326,1]README.1ST North Texas Local Users Group Submissions The UIC=[326,*] comprise the NTLUG submission for this RSXIAS SUG tape. A simplified directory follows: [326,1] Universal library of past years NTLUG newsletters. [326,112] New Spelling Checker without the data base. Contains bug fixes and new features. Comes from Jeff Hamilton of E-Systems. [326,113] Misc collection of utilities and fun items. Comes from Jeff Hamilton of E-systems. [326,114] Submissions from Mike Drabicky of Rockwell. If you have any trouble getting in touch with any of the authors, please contact: Jeff Hamilton E-Systems, Inc. P. O. Box 1056 CBN 27 Greenville, Texas 75401 (214)457-4175 outside Texas (800)527-1000 ================================================================ ================================================================ ================================================================ [326,112]README.1ST ***************************************************************************** S P E L L The univeral library is part of the submission from E-Systems Greenville Division. The update to SPELL a spelling checker program (current version 4.4) fixes several bugs and adds several features and speeds execution (27%). To use extract the command file SPELLU.CMD from the universal library SPELL. THE SEQUENTIAL DICTIONARY IS NOT INCLUDED. To save space it was left out. If you need it, please see the Fall82 tape this UIC. It is the same one that would have been included here. ATTENTION SIG TAPE COPY PEOPLE: There are no task images or object files in the libraries. SPELL.ULB does not contain the sequential dictionary and thus is somewhat shorter than last time. All procedures are UIC independent but are submitted under the UIC assigned last tape ([326,112]). Jeff Hamilton E-Systems Inc. P. O. Box 1056 CBN 28 Greenville, Texas 75401 (214)454-4175 outside Texas (800)527-1000 ***************************************************************************** [326,113]README.1ST This UIC contains a collection of misc. I thought I would throw these on the distribution. Some things might be useful, some funny. Take you pick. FORTRAN programs TAPCPY copies from one drive to another with some control. HPTAPE copies ASCII files to tape using command lines (80 byte recrds) RFM enables reformating listing output (FF->FORTRAN)(remove tabs) DFX data file exchanger (see help for complete description) DFC data file converter (see help for complete description) TPT tape drive handler for unmounted tapes. (see source for doc) POET uses data files to create free form poetry. SPADES keeps a running score for spades and with standings UNO keeps a running score for UNO and with standings command files TPT builds TPT above SCCS a slightly changed RSXSIG tape program (enhanced for our use) F a FORTRAN compiler, linker, command file (use for above prgrms) subroutines TAPEIO connection to unmounted tapes easy to use routine DAOKWK function return of the day of the week for given date PLOT46 connection to the Tektronix 4662 interactive plotter NUMSTR convert a INTEGER*2 into a ASCII string FFT a FORTRAN FFT routine (uses IBITR) IBITR a macro bit reversal routine libraries PLOT.ULB a general purpose signal processing source library PLOT.OLB goes with the above PLOT.DOC documentation for above I hope someone can use some of this. It has come in handy for us. None of this sould crash your system. If there is any difficulty get in touch with me. I don't promise to fix it, but I may be in a generous mode and help you out. Jeff Hamilton E-Systems P. O. Box 1056 CBN 27 Greenville, Texas 75401 (214)457-4175 outside Texas (800)527-1000 [332,13]README.1ST FORTRAN HELP FILE The file contained in [332,13] id a .HLP file containing syntax for FORTRAN-77 as used under RSX/VMS systems. The help file contains only the commonly forgotten items as For- mats, Open/Close, Functions, and numerical accuracy. In ad- dition a compendium of all syntax without explanation is provided. ================================================================ ================================================================ ================================================================ [332,13]README.DOC BONNER LAB RUNOFF This distribution of BONNER LAB RUNOFF contains all the .MAC, .RNO, .TST, .CMD and .DOC files necessary to build and test RNO. The distribution .DOC file gives the necessary preceedures in the section on BUILDING RNO. The distri- buted .DOC file refers to the VMS version, but in the process of building RNO you may generate documentation suitable for the target operating system. If the .DOC file is trashed the file BUILDING.RNO is the how to manual for build- ing a working version. The following is documentation on the revisions to the BONNER LAB RUNOFF. This revision will be available on the Fall 83 DECUS tape.. The previous versions were available from the Fall 82 and Spring 83 DECUS tapes [332,12] and from the HOUSTON LUG. This version of RNO includes most of the features of DSR, and as a bonus escape sequence handling, a macro facility (substitution), and may other features documented in the RUNOFF.DOC manual. ENHANCEMENTS 1. .SEPARATED EQUATION command sets the mode so that the equation format- ting will automatically add extra lines to account for the levels of fractions. 2. Separate help files for VMS and RSX are included with the documenta- tion. These are part of the .RNO files and are conditionalized with the RSX or HLP key words. 3. Hyphenation improvements: o Hyphenation of 3 lines in a row is inhibited. If 2 consecutive lines are hyphenated the third line will not be hyphenated. o Options to control hyphenation have been added to the .AUTOHYPHEN- ATE command. These may improve the hyphenation, or at least make it more pleasing. The default settings follow recommended hyphe- nation rules. o Hyphen has been rewritten with copious comments and a number of changes: o Several words have been added to the suffix table. o Umlauts or dipthongs are prevented from being hyphenated. Unfor- tunately words like reinitialize will not be hyphenated after the re. No hyphenation is much superior to obviously wrong hyphena- tion. o A differential hyphenation test has been added to DIGRAM. o The hyphenation routine has been made faster. 4. The .AUTOBREAK command has been added to make hyphenation and tabula- tion more convenient. 5. FLAGS SPECIAL may specify multiple flags in 1 command. 6. Undefined escape sequences are tagged as errors when they are used. This is only done if the escape sequence is triggered by an escape flag or a special flag. 7. .KEEP has been added as a command the same as in DSR. 8. .FLAGS INDEX and .FLAGS SUBINDEX have been added. Both autoindexing and subindexing are available as options. 9. .UNDERLINE command has been added to declare any arbitrary character underlinable. .NO UNDERLINE declares characters not underlinable. 10. Error messages now list the input file name and line number for all currently open files in which the error occurrs. Essentially full traceback is now provided. 11. .LIST command may now specify a character to output rather than a number. 12. Two new define commands make this version completely printer indepen- dent. The half spacing and equations will work on any printer capable of sub/superscripting whatever the escape sequences necessary to do this. 13. The command table has been shortened and command parsing made faster. Page 2 14. The .VARIABLE SPACING and .DEFINE VARIABLE SPACE commands have been added to RNO to allow variable spacing between words. 15. .DEFINE COMMAND allows new commands to be defined. No parameters are passed. BUGS in the Spring 83 version now FIXED 1. Equations imbedded inside text were not handled properly if the line had to be split. They are now properly moved to the next line. 2. Lines did not properly justify if they included equations. .NJ was the only solution in previous versions. 3. If .FILL is enabled and a printable escape sequence is braketed by a pair of spaces the final space was removed. This no longer happens if the HSP attribute is defined for the escape sequence. 4. If an escape sequence changed the pitch of the printer, improper underlining may result. If the pitch change can be specified by the PSP and HSP attributes then the underlining will be correct, otherwise the user must use /UL:B instead of UL:L. 5. Module RNOIF was in the wrong overlay. It must be in the same overlay with OPEN,CLOSE or an overlay that calls OPEN,CLOSE. This has been fixed. RNO would bomb when a .IF statement was not folowed by the ap- propriate .ENDIF inside a "required file". 6. If hyphenation is enabled and escape sequences are used occasionally RNO will hyphenate the output in strange places. The workaround is to .DHY during escape sequences. 7. Strange hyphenation may occurr after tabs have been used. In general hyphenation only worked properly for normal text. Now it should work properly for all text. Authohyphenation has been restricted to normal text, but user specified hyphenation may be used in any text except equations. 8. Roman numerals were incorrectly converted for 9,90-99,900-999. . . 9. .NUMBER LIST n started numbering at n+1 rather than n. .NUMBER LEVEL also worked incorrectly. The defaults have been modified for the .NUMBER commands to correspond exactly to DSR. 10. .LITERAL or .NO FLAGS ALL would turn off SPECIAL FLAGS permanently never to turn on again. 11. The LCK attribute did not work unless the .FLAGS ESCAPE command was used. 12. Some versions of RNO may have difficulties when a footnote spills from one page to the next. Symptoms include multiple pages, and Can't jus- tify text messages. 13. The /WA switch would cause RNO to wait at the beginning of each page even when pages are suppressed by the /PA switch. BUGS NOT YET FIXED There are currently a few bugs which have not yet been fixed. Any help from other users in fixing them is gratefully appreciated. 1. Indirect command files do not work as input to RNO under IAS. They work for RSX-11M and VMS under compatibility mode! Since the documen- tation for RSX and IAS I/O routines and parsing is identical the problem is very maddening. This may actually be a bug in IAS! NOTE If you find any bugs I would appreciate getting a copy of both the .RNO and .DOC files containing these bugs. If you could isolate the bug and Page 3 demonstrate it in just a few lines of input I would appreciate the effort. I will try to fix bad bugs or at least create a workaround. John Clement Bonner Nuclear Lab Rice University Box 1892 Houston Tx, 77251 (713) 527-4018 ================================================================ ================================================================ ================================================================ [343,30]README.1ST INTERR In large networks of Digital Equipment Corporation computers using DEC's DECnet networking software, it is often desirable to have a method of automatically reconfiguring the network to adjust to changing conditions. In large DECnets, change is constant; new nodes enter the network, old nodes are removed, partitioned subnets are started, and node names are changed. This information is usually distributed to the various nodes by transferring a file containing node assignment information for all the nodes; but this is slow, error-prone, wasteful of expensive programmer time and effective only if the network is relatively small. When a network becomes much larger than 50 machines, the effort required to update network configuration information on all machines simultaneously becomes prohibitive. It is possible to avoid this problem by assigning a central node as a record-keeper for the entire network. If this is done, when a node enters the network all it needs to do is interrogate the record-keeping node about the current network configuration. This has the advantages of updating each node's configuration information whenever the node is restarted and of centralizing the network configuration information. INTERR is a program which interrogates the Network Management Listener / Network Information and Control Executor (NICE/NML) on a central node to obtain node numbers and node names for the current network configuration. When it has obtained this information, it spawns NCP SET commands to the local host to set this information locally. An additional advantage of INTERR is that, for networks which are partitioned into subnets, it is possible to interrogate a node in the local subnet for information rather than a globally known node which would not know about the subnetwork nodes. To build INTERR, invoke the build command file, INTGEN. INTGEN should normally build the task (on an M V4/M-Plus V2 or later system) without significant intervention. More documentation is available in INTERR.RNO. Direct all other inquiries, comments and suggestions - IN WRITING ONLY - to: Bruce R. Mitchell Machine Intelligence and Industrial Magic PO Box 601 Hudson, Wisconsin 54016 Attempted phone calls and in-person visits will be politely rejected. ================================================================ ================================================================ ================================================================ [343,36]README.1ST This distribution kit contains the RSX-11M/M-Plus user monitor files. Note that this version of the monitor was upgraded with the release of RSX-11M V4.1 and M-Plus V2.1. This distribution corrects bugs in the version distributed in the Multi-Tasker and corrects the deficiency which prevented the monitor from logging out its own TI: . The problem of the monitor logging out terminals remoted to other systems via DECnet RMT/RMTACP has also been corrected - but only works on the new versions of RSX, as it requires the GCII$ directive. Problems with the monitor refusing to log out the last logged-in terminal on the system have also been finally eliminated. This version introduces time limiting. This means that the monitor may be built to run only during time periods specified at generation time. This may be useful to sites which do not wish to log idle terminals out during normal working hours. To build the monitor, log in on a privileged account and copy the distribution files into a chosen UIC. Invoke the build command file, USERGEN. This command file is reasonably intelligent, UIC-independent, and is usually able to build a task without intervention. If this is not the case, it may be necessary to run the command file with the /-MC switch and build manually from the produced build command files. Users of RSX-11M V3.2 / M-Plus V1.0 systems or earlier, take note. The build command file uses some features released in the M V4.0 / M-Plus V2.0 Indirect which may not be available on older versions of RSX. This means there may be difficulties which require manual intervention. Please direct any inquiries, suggestions, etc. - IN WRITING ONLY - to the author at the following address. Phone calls and in-person visits will be politely rejected. Bruce R. Mitchell Machine Intelligence and Industrial Magic PO Box 601 Hudson, WI 54016 ================================================================ ================================================================ ================================================================ [343,37]README.1ST This distribution kit contains the RSX-11M/M-Plus network time coordination task source files. This update removes a previous restriction causing the time receiver task to run only under RSX-11M V4.0 or RSX-11M-Plus V2.0 (or later) systems. To build the tasks, copy the distribution files into a chosen UIC and invoke the build command file, TIMGEN. The command file is reasonably intelligent, UIC-independent, and should be able to build the tasks with no intervention. If this is not the case (as may be true under old versions of RSX), it may be necessary to run the command file with the /-MC switch and build the task manually from the produced build command files. Note the following: 1. To use TIMREC on a requesting node, you need only RUN TIMREC. It emits appropriate status if something goes wrong. 2. The master node name in TIMREC is defined as NETTIM. An alias for NETTIM must be defined to reflect your ____ network's master node. 3. TIMSND, the server, must be installed on the network ____ master node. 4. TIMSND must be made known to the network as a DECnet ____ object - see the source file for the command line. 5. This is SEMI-SUPPORTED, EXPERIMENTAL and PRIVILEGED software. If the TIMREC code is examined, a comment will be noted regarding self-rescheduling. This was not deemed desirable on the source system and hence was not included. Please do not contact the author regarding this. Suggestions and corrections are welcome - in writing only - __ _______ ____ at the address below. Phone calls and in-person visits will be politely refused. Bruce R. Mitchell Machine Intelligence and Industrial Magic PO Box 601 Hudson, Wisconsin 54016 ================================================================ ================================================================ ================================================================ [344,1]README.1ST K M S K I T R E A D M E . 1 S T V 4 . 1B *************************************************************************** ** Please note. Support for the KMS enhancements is dying fast. ** ** (DEC would refers to this as Catagory Z support on an SPD for ** ** KMSKIT.) However, things the RSX modifications still work and are ** ** still in active use at KMS (until we get a large enough PDP-11 to ** ** run M-Plus anyway). However, few attempts have been EVER made to ** ** install the whole thing as a package, as you, the user, might want ** ** to do. I tend to put changes in piece meal as I have time. The ** ** master command files are ant attempt to try and make the kit easily ** ** installable, and they actually have been tried a few times. That ** ** sadly, does not mean that they are guarantted to work for all users. ** ** ** ** Please be careful. The SLP files may not conform to the source ** ** files you have (though they should). BEWARE-----BEWARE. If the SLP ** ** files don't work, if the command files don't work, or if you need ** ** help, find a mirror (preferably larger than the pocket variety) and ** ** gaze at it intently. Note the face looking back at you. It is the ** ** kindly face of your Software Support Specialist. Good Luck!! ** *************************************************************************** The original V4.1 SLP files for the RSX Spring 83 tape were written to conform to the source files supplied as part of the RSX-11M V4.1 Field test. I should know better than to do that, but I honestly thought they might freeze the sources like they said. Well I got my BL35 kit from SDC, and guess what? Source file changes everywhere, particularly after applying a prototype Update "B" kit. Well, the SLP files I am supplying on this tape were designed to be applied AFTER applying the BL35 "B" update. But, they also should work with trivial modification on the BL35 sources. The command files EXESLP.CMD, MCRSLP.CMD and ICPSLP.CMD will display a comment indicating which sources assume Update "B". In going from V4.1 (field test version) to V4.2 Updata B version, all that I ever needed to change was the first ASCII locator string (which looks for that last audit trail record in the text preamble) to reflect the correct place for the SLP file audit trail to go. I have attempted to make the process fullproof, which is a sure indication that it is bound to fail for some. Three files (EXECSLP.CMD, MCRSLP.CMD, and ICPSLP.CMD) actually do all the SLPing. They assume most files are the unupdated distribution files with a NAME.EXT;1 file name. However, a few (known internally to the command files) are known to be updated (via Update B). These files assume that the DEC .COR files have been applied and that the distribution .EXT;1 files have been converted to .EXT;2 files. The .EXT;1 files should not exist for the updated files (I recommend renaming it to .VGN;1). Anyway, for these special files, a test is made for .EXT;2 files. If they are found they are renamed to .VGN;2 (or .VMD;2) and the SLP patches applied. Now, since Update "B" is at least a few months away from when I write this, I suppose DEC can always screw things up again by changing the SLP files on the kit. What can I say. If KMSKIT were a product, updates would only come out after the updates had come out and were installed, and I would have the motivation to test the installation procedure thouroughly. As it is, it's free and you are "on your own". Since users have not yet seriously proposed that KMS try generating a "product", my assumption is that users interested in KMSKIT are generally sophisticated and able to fix minor "bugs" that creep into the installation procedure. In practice, I do the following. 1. Distributions sources (.;1) are copied to .VGN;1 PIP *.VGN;1/pr/SY:R/OW:R/GR:R/WO:R 2. Apply DEC Autopatch/Update "xx" to produce .XYZ;2 files 3. Use EXECSLP.CMD, ICPSLP.CMD, MCRSLP.CMD 4. Read each and every SLPed source file to insure reasonablness I know of no way to set up a command procedure that can tell if the autopatch has been done and to set things up automatically. Perhaps if I gave it enough thought... But someone else should worry about this. As a note of MINOR encouragement, I have all of KMSKIT working on V4.1 of RSX11M and the enclosed files are the ones I used. This is NOT (nor was it intended to be) a rerelease of the entire KMSKIT. If you want the sources for ARC MAIL, some of the utilities, BATCH, etc look on earlier SIG tapes. These UIC's contain the new material relating to bringing up KMSKIT on V4.1 of RSX. The following UIC's are part of the KMSKIT RSX11M Enhancements Package Update for V4.1. [344,1] Documentation files. Command file to create the document files. You need RUNOFF to do this. Hope you have it. [344,40] Terminal and disk accounting, privlege allocation, modifications to HELLO, HELP and BYE, account utilities and report programs. Run privlege checking and searching both LIBUIC, NETUIC and SYSUIC on a RUN $ command. SET /LIBUIC for RSX11M (just like M-Plus). Enhancements to ...AT. to implement the /-LI switch. [344,43] Utilities. Updated versions of GREP and LIST [344,44] Here is a version of the old RMDEMO which runs on VT100's which are in ANSI mode. This version is almost half as small as the new version and supports reploting and easy exit. In addition, if KMS Accounting is present and active, it provides a dynamic display of the percent of total system utilization. This version (less my mods) was distributed with the field test kit of RSX11M V3.2 and is distributed here courtesy of the the RSX group. It runs on a RSX11M V4.1 system. [344,45] PDQ -- Program Development Queues. PDQ is a multi- queue command file despooler (using QMG...). Submit a command file for execution. When a program development queue becomes free, the command file executes at your TI: [344,61] CCL V9.0. Submitted by Paul Sorenson. Realy slick. I have fieldtested it and I think you will like it. Need I say more? CCL is almost too useful to be free. [344,65] A complete SYSTEM ACCOUNTING package for RSX11M. While oriented towards providing performance measurement, it provides the basis for implementing a versitile and reasonable charge-back accounting system. Some reports are provided which will do this. Please read SYSLOG.DOC. Please, create and read the documentation before leaping in and trying to use the kit! A discription of all the modifications and enhancements and most of the utilities is in KMSKIT.DOC. The command file [344,40]KMSGEN.CMD will provide all required information (or most of it)for building the KMS Enhancements and a number of the other programs. Read KMSKIT.DOC before trying to include the executive data base changes. Please note that it has not been updated since V4.0 and the file REQSB.SLP is no longer needed. Note also, this is an update kit. Hence all files refered to in KMSGEN may not bee on this kit. To use this kit, transfer the files to their respective UIC's. Read all the documentation over twice. Set /UIC=[344,40] and type @KMSGEN/-MC and run through a KMSGEN asking for a long dialog. Place the required DEC sources in the correct places, KMSGEN will try and do all the SLP patches both to MCR sources, the EXEC modules and the SYSGEN command files. If KMSGEN sucessfully SLPs the MCR, EXEC and SYSGEN command files, stop, place the OLB's and sources on your SYSGEN disks and do a SYSGEN if you are incorporating data structures (accounting) requiring a SYSGEN. Once the SYSGEN is done use KMSGEN again to create all needed files. This release kit of KMSKIT is not complete in and of itself. Hence, some programs if you desire to build them will require getting the programs from an earlier version of KMSKIT. Where useful programs have been updated, newer versions have been supplied. These programs have been extensively tested for the case where all KMS options are selected and where most DEC sysgen options are selected. KMSGEN and the command files to implement KMSKIT for the general user have had almost no testing since I do all patches one at a time checking results as I go. The first user to try KMSKIT found a bunch of bugs in the command files. These I tried to fix. But, as we all know, bugs are hard to completely stamp out. Be warned, be careful, and be alert. Since, I know the SLP patches once incorporated work, I am sure they can be incorporated with a bit of perseverence. I appologize in advance for any potential inconvenience, but current government regulations (let alone my family) preclude me spending in excess of 24 hours daily at work. I simply do not have time to do all that I have to do as well as all that I would like to do. Good Luck, James G. Downward KMS Fusion, Inc. 3941 Research Park Dr. Ann Arbor, Mich. 48104 (313)-769-8500 22-Oct-1983 ================================================================ ================================================================ ================================================================ [344,61]README.1ST CCL V8.0 This version of CCL is a composit of the work of Angle Li at the University of Miami, Paul Sorenson at Michigan State University, and Jim Downward at KMS Fusion. Angle Li edited the code to remove all the funny F4P lables and to comment the code. Paul Sorenson then provided a substanitial rewrite to CCL to provide significantly more flexible command string parsing. V8.0 of CCL will use the RPOI$ directive to chain command lines to tasks. In doing so the OCB's will be relinked and CCL will exit at once since it is not needed to hang around in core to pass back OCB information. This makes it possible to have CCL commands within a command file started by a CCL command. Also CCL was upgraded so that it can be an Alternate CLI for RSX11M V4.0. If it is used as an alternate CLI, it will receive the command line prior to MCR. This means that any MCR command (even for installed tasks) can be trapped and reparsed. Moreover, even with an unmodified MCR, illegal characters can be used as commands. The same CCL task image can be installed both as the catchall task (...CA.) and as an alternate CLI. If it is to work as a catchall task it must be installed with the name ...CA. User's desiring to use the Alternate CLI features should create a LB1:[1,5]SYSCLI.CCL file to avoid nasty error messages. Note that both the names for the system and the user CCL files are modified for if CCL is a CLI. The names are LB1:[1,5]SYSCLI.CCL and SY:[UIC]USERCLI.CCL. To simplify use of CCL for user's (like myself) who often assign a local LB:(to do a sysgen). The location of SYSCCL.CCL has been moved to LB1: (unless symbol $LB0 is defined in PRECCL.MAC). To use CCL, please do a global assign of LB1: to a physical disk either in VMR or in STARTUP.CMD. As was previously mentioned, this version of CCL has been extensively rewritten to provide a more flexible command format. The major changes that must be kept in mind for this newest version are, 1) All conditional assembly directives are now in PRECCL.MAC for easier access (see comments for their affects). They are $LB0,,$DCL, and $TABLE. 2) An internal table lookup has been added to offer a compromise between DCL and the .CCL files. (see comments in CCL.MAC) 3) Several new parameters have been defined -- %A%, %B%, %C% and %0% %A% is set the the entire character string past the command. %B% is set to character string up to first space %C% is defined as everything not in %B% (excluding delimiter) %0% is set to values of any leading switches (e.g. BRU/REW/VER, %0%=/REW/VER) 4) Two options have been added for command building. If a parameter is null, it may be replaced by a string starting with the key character "\" and extending to the % delimiter, also, a parameter may be tested by %2?S1\S2% which will insert string "S1" if parameter 2 is defined, otherwise string "S2" will be inserted (either S1 or S2 may be null). 5) A command line may extend to the next line by including the "+" character as the last character in the line. 6) USERCCL.CCL is opened on the user's logon UIC rather than the current default UIC. 7) If CCL can not find a command, it will try sending off its command to another catchall ...CA2. 8) %R is a special character signifying that CCL is to ring the terminal BELL when it exits. A previous version used %B for this. Sorry for the incompatability. 9) %D is added to aid in debugging CCL command lines. When it is encountered, the command up to that point is displayed in expanded format at the user's terminal rather than being sent to MCR. 9) %P is added to signify that an action line is to be printed out on TI:. This makes it very easy to create CCL commands which send escape sequences to control terminal characteristics. 10) %Q is added to signify that CCL should exit without sending on the command to MCR if a required input field is defaulted with a null (ie %1\%) and the input parameter is also a null. This prevents various PIP like commands from occuring with no files specified which often results in defaulting to the entire directory. 11) Two possible TABLE macro files are offered. TABLE.BIG has all kinds of CCL commands and results in a significantly larger CCL. TABLE.KMS includes those commands which used to be processed by the internal DCL code. The size of CCL using the internal table file is comprable to the previous versions using hard coded command. TABLEGEN.CMD allows the user to create an internal CCL file. 12) CCLGEN allows the user to select amoung a variety of options. If the user desires to use an internal table file, CCLGEN will allow the user to link to TABLEGEN.CMD to create an internal table from a standard CCL file. One can use either USERCCL.CCL or SYSCCL.CCL, for example, as a source file. 13) CCL now checks to see if the keyword typed in is longer than the maximum specified in the file (previously was ignored). This means that commands FOO and FOOY can be different and distinct. 14) Documentation and HELP files have been updated to reflect the many, many new features. 15) CCL now uses RPOI$ to chain the command to MCR if either a %$ is found, or if the action line is the last or only action line. The Command is chained off, and CCL immediately exits. This is only for the commands handled via the table file or the external file. The hardwired commands still use SPAWN. If RPOI$ fails CCL trys to use the SPAWN directive. Note that this makes it possible to have CCL commands within command files started by CCL commands. CCL is no mostly recursive although it is still not possible to have a CCL command itself be a CCL command. 16) Support for Dan Steinberg's patch for DRSPW (passing/relinking OCB's on special SPAWN directive) is withdrawn. RPOI$ can be used without patching the standard RSX11M system. 17) Support for CCL as an alternate CLI. KNOWN BUGS and RESTRICTIONS 1) If you specify the following in a command definition file $4411XSET *command_text CCL will come back and tell you that there is a read error on LB1:[1,5]SYSCCL.CCL. If you try $4411XSET ?0Switches *set %0%%1%P% you will also get a read error message on LB1:[1,5]SYSCCL.CCL if you type XSET /UIC=[xxx]. Values are stuffed into the %0 parameter until a space is found. Hence the whole line goes into %0. Now this screws up the checking for whether or not enough parameters were entered. %0 is not at this time counted as one of the characters, so CCL gets confused. The %0 parameter should be used with care until someone has a chance to come up with a versitile fix which doesn't screw up something else. II don't have time to fix this bug for this release, but I would welcome any help that any of you users would like to give. Active contributers to CCL now include Mr. Angel Li RSMAS/MPO University of Miami 4600 Rickenbacker Cswy. Miami, Fl. 33149 (305)-350-7491 Paul Sorenson Dept. of Physiology Mich. State Univ. E. Lansing, MI 48824 (517)-355-5125 And myself, James G. Downward KMS Fusion, Inc PO Box 1567 Ann Arbor, Mi 48106 (313)-769-8500 ================================================================ ================================================================ ================================================================ [346,103]README.1ST These are machine-readable versions of some of the handouts. The .RNO files have been edited, and were used in conjunction with a DSR setup file for the handout itself, so you would need to go into those and put the typical stuff about margins, etc in to the top of those files. Thanks should go to the session presenters who got the release forms in. AST.DOC;3 Gary Maxwell -- Hows and Whys of ASTs in RSX AST.RNO;126 MSCAN.MEM;8 Barry Miller -- MSCAN - An RSX Interprocessor MSCAN.RNO;10 Real time system README.1ST;2 This file RESLIB.MEM;2 Reid Madsen -- Cluster and Resident Libraries RESLIB.RNO;2 SYSGEN.DOC;4 Gary Maxwell -- RSX Sysgen session SYSGEN.RNO;16 ================================================================ ================================================================ ================================================================ [351,30]README.1ST This is a version of DOB (the object disassembler) with some mods to allow it to handle internal symbols from compilers like F77 V5.0. It does not fully support language specific features but is usable nevertheless. From Brian Nelson, U. of Toledo. 26-Jan-84 10:30:55 Brian Nelson ================================================================ ================================================================ ================================================================ [352,4]README.1ST SRD V6.4 Editor's note: This submission is a "Best Buy" of the tape. It merges most every SRD feature anyone has ever come up with into one program and provides a tool which anyone concerned with maintaining a set of files on an RSX volume should not be without. Users are encouraged to generate SRD and see how much easier maintaining or finding files is with it. Experienced RSX users generally swear by SRD and seldom if ever use the PIP /LI switch except under duress. [352,4]README.1ST - Las Vegas - Fall 1983 - Files submitted by: SRD Working Group Bob Turkelson NASA/Goddard Space Flight Center Mail Code 933 Greenbelt, MD 20771 (301) 344-5003 This UIC contains the files for building SRD V6.4. Many of the important items on the SRD Working Group wish-list were finished by the deadline for this release, although we realized that there was not enough time to complete all of them. At this time we know of no problems with the new features. Any important information we learn about this version will be promptly submitted for publication in the Multi-Tasker. The modifications made by the SRD Working Group since V6.3 are: o Fixed a problem which caused SRD to abort when listing large directories whose contents could not all fit into memory. (I also tried several other versions of SRD from recent SIG tapes and found that they all had the same problem.) When built on RSX-11M V4.0 with dynamic checkpoint allocation, SRD is able to read in a dense directory containing 3360 entries before having to list the directory in sections (2976 entries if built with FCSRES). o Fixed a problem which did not allow SRD to do any listings or selections based upon information contained in the file header if the entire directory did not all into memory (that is, when SRD needs to separate the directory contents into pieces). o Fixed a problem where instead of cancelling directory write- back for directories which could not all fit into memory, SRD wrote back only the last section of it, wiping out most of the directory! This problem probably only showed up when SRD was built without the dynamic checkpoint allocation option, for otherwise it would have aborted anyway due to the error described above in the first modification. Now SRD issues a fatal message informing you that write-back will not be done (and SRD means it). This message is issued before any directory sorting is attempted, so you don't have to wait for sorting the large segment of the directory which did fit into memory. o Fixed a memory protection violation problem than occurred only occasionally with some configurations when listing a dense directory which exactly fills the last block of the directory. o Improved the organization and contents of the documentation to reflect the current state of SRD, while converting to a true RUNOFF format. This work was done by Gerard Stackhouse, who is maintaining the documentation. Any suggestions for improvements may be sent to him at United Telecom Computer Group, United Information Services, Inc., 300 Second Avenue, Waltham, MA 02154 (617-890-6820). o Modified SRD so that it displays the original command line the user entered, before replacement of certain special symbols which may appear in the /SE, /SD, and date switches. o Added new capabilities in specifying the sorting to be done. Sorting by date may now be requested. SRD allows the major and minor sort keys (file name, type, version, date) to be specified in any order in the /SR:x:x:x switch, and also allows the sort to be either ascending or descending sort for any key independently. (To see an unusual looking directory listing, try using Version as the primary key. Or try your own combination.) The sorting by date feature was merged from Henry Tumblin's version of SRD (which is not on the SIG tapes). Allowing sorting to be done ascending or descending was a feature adapted from changes by Dave Sides (Sachs/Freeman Assoc., Inc., c/o JHU/Applied Physics Laboratory), and from the SRD in the U. S. Forest Service collection of programs submitted to the Spring 1982 SIG tape. Ideas for being able to specify the major and minor keys also came from the latter version, although the V6.4 implementation is quite a bit different. Coding changes were required in the sections of the selection/listing routine dealing with the highest and obsolete version selection switches (/SV, /NV, /OV, /PU) since files may be sorted with ascending version numbers. The former code compared each entry in the sorted directory with both the previous entry and the following entry. The current code looks only forward and remembers where it finds a different file name. o Added the /CM:xxx:fffff switch to enable the generation of command files. This feature was merged from the version submitted in the U. S. Forest Service program collection cited above (eliminating a problem that version had in handling null file names). The format and meaning of the switch values are taken from that version. For details see the documentation or help files; the information given there is also from the the earlier program. o Added the /PA switch to pack the files names (removing any blanks between the name and type and between the type and version number). o Added the /TB switch to include in the summary the number of blocks used/allocated even if it would not otherwise appear. For example, /OV/-LI shows only the number of obsolete files, not the total number of blocks. /OV/-LI/TB does show the block total. o Added the /GT:n switch to select files with allocated sizes of at least n. blocks. This is useful for finding large files on user disk packs, as well as easily determining large directory sizes. It may also be useful in obtaining some contiguous disk space. Use /GT and /BE (and perhaps /-SR) to search for large files which existed at the time of the last full disk copy. Rename one such file, then copy it to the original name using PIP /CD (assuming enough free space remains). Then delete the renamed file, which will usually free up contiguous blocks. o Added the /FI:n switch to select the file with File ID n (the sequence number should not be specified). This helps to find a file when a utility such as BRU issues a diagnostic containing the File ID without a file name, or reports the file name from the header, but the file has been renamed. Up to four File IDs may be specified: /FI:n1:n2:n3:n4. o Added the /FO:[g,m] switch to select files with file owner [g,m]. Either the group or member may be specified as a wildcard (* or zero). The UIC of the directory being listed will be the default switch value if /FO is specified without group and member. An alternate form of the switch, /FO:g:m, is supported (but a wildcard must be a zero, not *). The switch may be negated (/-FO:[g,m]) to select files not owned by [g,m]. SRD [*,*]/-FO would list all files not owned by the directory in which they reside. o Added the /ER switch to display files which produce errors when attempting to read their headers. o Added the /NV (new version) switch with the same meaning as /SV. Some other versions of SRD use /NV, and this seems to be a more appropriate name. o Changed the listing of a file's used and allocated blocks to reference the double word values stored in the header instead of single word values. In V6.3 the number of allocated blocks was calculated from the retrieval pointers if the file header showed a value of zero. Now this is also done if the file has multiple headers, which requires SRD to read each header. NOTE: There is a problem in RSX-11M V4.0 and RSX-11M-PLUS V2.0 which does not allow SRD to read an extension header unless your "login UIC" is a privileged UIC or the file owner's UIC (actually the file owner stored in the extension header). To get around this temporarily, SRD ignores such extension header read errors and treats the file as if it were not a multi-header one. DMP shows the same problem. The undocumented SRD switch /H2 inhibits this work around and causes the error message to be displayed - this is for testing purposes. We have learned that this does not show up in RSX-11M V3.2 or V4.1. For our next version we probably will obtain the number of allocated blocks from the statistics block. Until recently we felt there were reasons we could not use the statistics block. o Corrected handling the case when the date stored in the file header is corrupt, by issuing a non-fatal diagnostic message. Previously the same fatal message was issued for this situation as was given for when an invalid date was specified in a date switch in the command line. o Modified the program to use the three letters of the task name in the program prompt and in the error messages. o Modified SRD to make sure /SR (sort switch) is set if /SV, /NV, /OV, or /PU is specified, even if /-SR is specified. The directory needs to be sorted for these functions. o Changed the diagnostic processing so that the UIC and file name are included in the appropriate messages. o Changed the listing routine so that a file with a header read error will never be "selected" (as long as a switch which requires reading headers is specified, of course). In addition, if file selection by date is requested and a corrupt date is detected in the file header, that file will not be "selected." o Modified SRD to assure that the UIC heading line for the directory appears in the listing whenever issuing a diagnostic for a header read error or for a corrupt date in the header. o Correctly terminated each switch value table so that if too many values are specified for a particular switch, a syntax error message is given. With previous versions, extra values on certain switches would clobber fields for other switches. For example, SRD /SV/MI:80:3 would behave as if SRD /SV:3/MI:80 had be specified. o Made a few changes to enable this version of SRD to run on IAS systems. Recently I traced the failure to the method employed by SRD to reuse some of the memory taken by the largest overlay segment (SRDINI) once the routines in that segment have completed. IAS V3.0 is running on the system I was able to use. The current code seems to work OK (testing just a few switches) if SRD is built /-MU and the special dummy PSECTs $$$XX1, $$$XX2, and $$$XX3 are given the RO attribute for IAS systems, so these modifications are in this distribution. Of course this means that the resulting task is not multi-user. By the next SIG tape we plan to get it working as a multi-user task under IAS; there is no time left to make and test such changes before this submission. There were several modifications in the command file for IAS: eliminating certain SYSLIB routine references from the generated ODL file; and, jumping over any the references to the symbol (which is not defined in the version of Indirect on the IAS system I used). o Eliminated the extra 0 byte appearing at the end of the UIC line. o Eliminated the extra 0 byte appearing at the end of a diagnostic message. o Made a few other internal coding changes, documented in the source files. o Kept the help file up to date, added a HELP SRD NEW section to list new switches in V6.4, and changed the HELP SRD SWITCH DEFAULTS section so that it references a file created by the SRD generation command file. o Modified the command file to allow the user to select certain groups of default switches, to eliminate the need to ask as many questions. The *.C64 files are correction files which have already been applied to the V6.3 source files. They are provided here for reference purposes only. (Some sites obtained a pre-released version of the Spring tape - labelled as a pre-release. The SRD on that tape was different from the version on the final tape, even though they both were called V6.3. The date displayed in the V6.3 /ID switch was 01-June-83.) The *.MAC files are those for V6.4. SRD.TSK is a task built with the default switches shown in SRDDEF.HLP;1. It was built for RSX-11M V4.0/V4.1 with dynamic checkpoint allocation. SRDMOD.DOC describes the past changes to this version of SRD. SRDREF. is the text for a two-page SRD Reference Guide showing the available switches. Alan Frisbie sent us a typeset sheet for the version of SRD he was using. Alan plans to have this new version typeset for us to submit to the Multi-Tasker. Please send us any ideas you have for improving its organization and content. We will be updating it for each new version. Procedure: @SRD ! Asks configuration questions and ! builds SRD Copy SRD.HLP and SRDDEF.HLP to [1,2] and refer to SRD.HLP in [1,2]MCR.HLP. HELP SRD NEW will show users a list of the new switches. Note that under RSX-11M V4.0 or later and RSX-11M-PLUS V2.0 or later, the command string interpreter allows wildcards (* and %) anywhere in the file name or type. This eliminates the need for the /SE: switch in most circumstances. For example, SRD *AB%D*.%D* is valid. Specify /-SR whenever you are looking for certain files and do not care in what order they are listed. You will save the time required for sorting the directories. The /CM switch should be used with /NV (or /SV) unless V is specified in the second switch value and all versions are wanted. The value specified in the /GT:n switch is a four-byte integer value on RSX-11M V4.0/V4.1 and RSX-11M-PLUS V2.0/V2.1. It is considered a two-byte integer on V3.2. Its use on V3.2 has not been tested. The additions to the selection/listing overlay segment and the root segment total about 550. words (when built without FCSRES). This reduces the largest directory section that can be handled at one time by two or three blocks (out of about 110 blocks). Each block contains up to 32 file entries. The SRD Working Group plans to make additional modifications before the next SIG tape. Command and help file improvements are planned as well as program changes. We would appreciate hearing from those who have made changes or plan to make changes to this version, so we can continue to improve this useful utility. [352,4]README.1ST - END ================================================================ ================================================================ ================================================================ [352,20]README.1ST [352,20]README.1ST FRIENDLY - V1.0 This program may be installed as a catchall task for CCL (as ...CA2) or for MCR (as ...CA.). It is executed when the command entered by the user is understood by neither MCR nor CCL. The original idea was a give the user one of several "friendly" messages to say that the command was in error. But we couldn't resist adding other messages. No fair making more than a few intentional errors after first installing the program. They are more fun to get when you haven't seen them before. Eventually you will hear from most users! This code is a slightly modified version of the COOKIE program. B. T. [352,20]README.1ST - END ================================================================ ================================================================ ================================================================ [356,10]README.1ST October 1983 This SIG Tape submission accompanys the paper "Developing an RSX-11M ACP in a Higher Order Language" presented at the Fall 1983 DECUS Symposium in Las Vegas, Nevada. The submission contains a copy of the paper manuscript (without figures) and a number of program source files taken from the ACP software described in the paper. The program files are provided as examples of how an interactive program can be used to aid in the development of an RSX-11M ACP. A list of the program modules and a brief description of their purpose is provided below. The *.RAT files are FORTRAN source language files coded in the RATFOR preprocessor language. Filename Description SMMDEF.RAT These files define some program wide constants SMMDEF.MAC that are used in many of the individual program modules. CSMMDF.RAT These files define the structure of the FORTRAN ACPDAT.MAC common areas used by the program in its operation. CSMMOT.RAT The MACRO file contains an assembly language version of the principal common used by the program. This version of the common region is used by the ACP to fill in user parameters from a QIO request. SMMMAI.RAT These files are the main program module sources for SMMACP.MAC the interactive and ACP forms of the staging memory software. SMMPRC.RAT These files are the program module sources that ACPPRC.RAT control the process used to calculate the staging memory hardware control parameters. INPDES.RAT This module creates the initial FORTRAN common region used for stager parameter calculation. The data is supplied via user dialog or from an input data file. ACPINP.MAC This modules creates the same FORTRAN common as INPDES above. The required data is taken from an open function QIO data buffer. ACPOPN.MAC This module is the top-level subroutine for executing the ACP's I/O process creation or open functions. VIRTIO.RAT This module performs the data transfer QIO functions that use the I/O process data structures built by ACPOPN. ACPFST.MAC This module performs I/O process creation functions using pre-defined hardware control parameters supplied in an alternate "fast" open function QIO. ALLOST.RAT These modules provide stager memory buffer allocation DEALST.RAT and deallocation functions in support of ACP open BITMAP.MAC and close QIO's. SMMBLD.CMD These files drive the task build process and provide SMM.ODL definitions of the overlay structure of the staging SMMFCS.ODL memory software. SMMACP.ODL SMMACPFCS.ODL ACPAPER.DOC This file is the manuscript of the subject paper presented at the Fall 1983 DECUS Symposium. Carl T. Mickelson Goodyear Aerospace Corporation Akron, Ohio 44315 (216) 796-2388 ================================================================ ================================================================ ================================================================ [356,20]README.1ST ************************************************** * * * S U P E R - M A C * * * * PREPROCESSOR * * * * FORTRAN VERSION * * * * AUTHORS: Thomas J. Weslowski * * Computer Science Dept. * * SUNY at Oswego * * Oswego, NY 13126 * * * * and * * * * Richard R. DeMidio * * Instructional Comp. Ctr. * * Snygg Hall * * SUNY at Oswego * * Oswego, NY 13126 * * * * MAINTAINER: Edward F. Beadel, Jr. * * Manager * * Instructional Comp. Ctr. * * Snygg Hall * * SUNY at Oswego * * Oswego, NY 13126 * * * * PHONE: (315) 341-3305 * * * ************************************************** COPYRIGHT (c) 1981, 1982, 1983 BY Instructional Computing Center State University of New York at Oswego Oswego, NY 13126 contact: Edward F. Beadel, Jr., Manager phone: 315/341-3055 ************************************************** This account contains the sources for SUPMAC. SUPMAC is a preprocessor for the structured asem- bler language SUPER MAC which is written ti FOR- TRAN IV. The account also contains the command files SUPFOR.CMD to compile the sources, and SUPLNK to link the SUPER MAC compiler, togeather with SEG.OBJ and ESTUFF.OBJ which were compiled with an earlier SUPMAC compiler. Some test pro- grams are also included (The LIFE.SMA program will compile with-out errors but will not run due to a logic error, however it is a good test of the com- piler). The IOX.* files are needed to run the prepro- cessed, compiled, and linked SUPER MAC programs. The command file SUPDLK.CMD compiles SUPDIR and the command file SUPCOM.CMD linkes SUPDIR. See the documentation for how to use SUPDIR.SAV Please see the documentation in [83,155] on this tape for more complete information on the SUPER MAC language. What follows is an example of compilation and linkage of the SUPER MAC compiler. @SUPFOR.CMD Ready SWITCH RT11 .RUN $FORTRA *SUPMAC=SUPMAC/S SUPMAC *BEGIN=BEGIN/S BEGIN *CALL=CALL/S CALL *CASE=CASE/S CASE *CHECK=CHECK/S CHECK *ELSE=ELSE/S ELSE *ENDD=ENDD/S ENDD *ENDM=ENDM/S ENDM *ERROR=ERROR/S ERROR *EXTNAM=EXTNAM/S EXTNAM *FI=FI/S FI *FORGEN=FORGEN/S FORGEN *GOTO=GOTO/S GOTO *IFTHEN=IFTHEN/S IFTHEN *ILLCHR=ILLCHR/S ILLCHR *ILMATH=ILMATH/S ILMATH *INIMAC=INIMAC/S INIMAC *INIT=INIT/E/S INIT ?FORTRAN-I-[INIT ] Errors: 0, Warnings: 1 *INOP=INOP/S INOP *KEYWRD=KEYWRD/S KEYWRD *LABGEN=LABGEN/S LABGEN *LEAVE=LEAVE/S LEAVE *LENGTH=LENGTH/S LENGTH *LET=LET/S LET *LOOP=LOOP/S LOOP *LOOPS=LOOPS/S LOOPS *MACRO=MACRO/S MACRO *MULBLK=MULBLK/S MULBLK *NOERR=NOERR/S NOERR *ONERR=ONERR/S ONERR *OUTPUT=OUTPUT/S OUTPUT *PARSER=PARSER/S PARSER *POP=POP/S POP *PROBE=PROBE/S PROBE *PROCED=PROCED/S PROCED *PUSH=PUSH/S PUSH *REGFET=REGFET/S REGFET *REGSER=REGSER/S REGSER *REPEAT=REPEAT/S REPEAT *RETURN=RETURN/S RETURN *REVCOM=REVCOM/S REVCOM *REVLAB=REVLAB/S REVLAB *!SEG=SEG/S the modual SEG is now written in super-mac STR=STR/S STR *SUBCOT=SUBCOT/S SUBCOT *THROUT=THROUT/S THROUT *THRU=THRU/S THRU *UNTIL=UNTIL/E/S UNTIL *UTIL=UTIL/S UTIL *UTILTY=UTILTY/S UTILTY *VAL=VAL/S VAL *WHILE=WHILE/S WHILE *WRAPUP=WRAPUP/E/S WRAPUP *^Z . Ready @SUPLNK.CMD Ready LINK *SY:SUPMAC,SUPMAC=SUPMAC,SEG,LENGTH,STR,VAL/C *OUTPUT,UTILTY,EXTNAM,ESTUFF/C *SUBCOT,KEYWRD,INIMAC/O:1/C *REVCOM,ILLCHR,RETURN,CALL,CHECK/O:1/C *MACRO,ENDM,ERROR,FORGEN,REGSER/O:1/C *REGFET,INOP,INIT,LEAVE,MULBLK/O:1/C *POP,PUSH,BEGIN,GOTO,PROBE/O:1/C *ILMATH,PROCED/O:1/C *CASE,PARSER,LOOP,ONERR/O:2/C *NOERR,IFTHEN,FI,ELSE,WHILE/O:2/C *REPEAT,LOOPS,UNTIL,THRU,ENDD/O:2/C *UTIL,LABGEN,THROUT,WRAPUP/O:3/C *LET,REVLAB/O:3 *^C Ready We wish you good luck with this package. If you encounter any problems with the package please drop us a line c/o the maintainer. In that way we may be able to improve the product. Thanks! ================================================================ ================================================================ ================================================================ [356,30]README.1ST This account contains Datatrieve structures to produce reports of RSX-11M-Plus system accounding data. The file ACCOUNT.DOC is the text of a paper on this subject scheduled for the Fall 1983 Las Vegas symposium describing these reports, which I believe are more useful and more easily adaptable to individual sites than those distributed by DEC. A description of the files and how to set things up is in SETUP.DOC. This account also contains some commands for producing reports from the Console Log file, which work for both 11M and M-Plus, and are also described in the documents given above. ================================================================ ================================================================ ================================================================ [356,31]README.1ST This is an addition to the SFGL70 graphics package which has appeared on previous tapes, with an additional module by myself which simplifies plotting on the 4663 (and 4662) pen plotter. The additional functions allow turning the plotter on and off, selecting pens, unloading media, etc. Some functions which may also be of use with 4014 type terminals will select a line type (dots, dashes, etc.), the size of the characters printed, and will reset device characteristics. The module can be assembled and added to your copy of SFGL70.OLB: I have been using this library for some time, and find it quite satisfactory. I have also included a revised runoff source and document for SFGL70 where I have removed reference to the PDP-6 and added instructions for the plotter functions. Our configuration has the communications line running from the computer to the plotter, where it passes through to a CRT terminal: this works best as SFGL70 sends all graphics commands to your TI:, so you can run the program from the terminal connected to the plotter, and turn the plotter on and off as you wish. With this configuration, and the plotter set to use X-ON/X-OFF protocol, the functions BAUD and BLACK-BOX are not needed. SHADE.FTN is a subroutine to shade in rectangular spaces with a pattern of vertical, horizontal, or slanting lines, with various skip patterns. The source contains a description: this module calls SKIP.FTN, which also contains comments. SHATST.FTN simply prints out a set of shading patterns so you can see how they work. PIE.FTN is a sample program using the library and my additions: it takes up to 25 values and puts them in a pie chart, with the first value in a seperate wedge of it's own. I found that SFGL70 should be kept in a seperate object library and not SYSLIB, as there is a module called POINT which causes a conflict in names. B. Z. Lederman I.T.T. World Communications 67 Broad St. New York, N.Y. 10004 (212) 797-8080 ================================================================ ================================================================ ================================================================ [356,40]00README.TXT [Editor's note: A new KERMIT distribution arrived in mid january 1984, so this version of KERMIT is current as of about 1/15/1984 and corrects several bugs in the 10/21/83 distribution. See also the [356,41] and [356,42] directories for a DG AOS version in RATFOR and FORTRAN, and [356,43] for Brian Nelson's RSX and RSTS versions of Kermit. ] 00README.TXT (21 October 1983) COLUMBIA UNIVERSITY KERMIT DISTRIBUTION TAPE This tape includes all the versions of Kermit which were in our possession as of the time this distribution tape was made, plus some miscellanous files. The files on the tape have names of the form NAME.TYPE Where NAME is the name of file, and TYPE is its type (program source, documentation, executable core image, etc). No NAME is more than 9 characters long (the maximum accepted by VAX/VMS), and every NAME is unique in the first 6 characters (the maximum under TOPS-10). On TOPS-10 BACKUP/Interchange tapes, names longer than 6 will be truncated to 6. No type is longer than 3 characters. NAME and TYPE are separated by a period. * Prefixed Files: The file names for files associated with each implementation of KERMIT are prefixed by a few characters denoting the implementation. The following are presently used: Prefix Machine(s) Operating System Language 10 DECsystem-10 TOPS-10 MACRO-10 20 DECSYSTEM-20 TOPS-20 MACRO-20 CMS IBM 370 Series VM/CMS IBM Assembler VMS VAX VMS Bliss-32 VX VAX VMS C UX VAX, SUN, PDP-11, etc UNIX C RT PDP-11 RT-11 OMSI Pascal CPM 8080, 8085, or Z80 CP/M-80 ASM PC IBM PC or Zenith Z100 PC DOS, MS DOS PC Macro assembler APP Apple II 6502 Apple DOS DEC-10 CROSS RB DEC Rainbow-100 CP/M-86 ASM86 170 Cyber 170 NOS Fortran-77 (The Cyber 170 version just came in, hasn't made it into the User Guide yet) (The VAX/VMS C version is based on an old version of UNIX Kermit; the VMS support has yet to be merged with the current UNIX Kermit) In some cases, binaries (.REL, .EXE, .COM, etc) are not supplied. For instance, no binaries come with the UNIX sources, since these can be compiled to run on many different machines, under different versions of UNIX. No binaries come with the VAX/VMS source, since the VMS file attributes cannot be saved on the DEC-20 tape. Binaries are provided when it makes sense, however: DEC-10 and DEC-20 .EXE files are provided on DEC-10 and -20 distribution tapes, MODULE files for CMS KERMIT on the IBM VM/CMS tape. In any event, all necessary files for building each version of Kermit from program source are included on all tapes. When working with one of these implementations, you would normally copy them to a separate area and strip the prefix from the file names, and install the programs on the appropriate systems without the prefix. For instance, on the DEC-20 you would copy 20KERMIT.MAC to KERMIT.MAC, then assemble it, and store the result as KERMIT.EXE in SYS:. The VAX/VMS version is an exception; in this case REPLACE the "VMS" prefix with "KER". The following HEX files for specific CP/M implementations are included: CPMBASE.M80 The current, working source file for CP/M KERMIT. CPMBASE.DOC A list of recent changes to CP/M KERMIT (not in manual yet). CPMKERMIT.DOC An explanation of why there are three source files... CPMAPPLE.HEX Apple II with Z80 Softcard & DC Hayes Micromodem CPMAPPLE.SSC Notes for using above with Super Serial Card CPMBRAIN.HEX Intertec SuperBrain CPMDMII.HEX DECmate II with CP/M CPMGENERI.HEX "Generic" CP/M Kermit. CPMHEATH.HEX Heath/Zenith 89 CPMKAYPRO.HEX Kaypro-II CPMKERMIT.ASM Source file for all Kermit-80s but Generic Kermit CPMOSBORN.HEX Osborne 1 CPMOSI.HEX Ohio Scientific CPMPLUS.HEX For any system running CP/M-Plus (3.0) CPMRAINBO.HEX DEC Rainbow-100 CPMROBIN.HEX DEC VT180 "Robin" CPMTELCON.HEX Telcon Zorba CPMTRS80.HEX TRS-80 II with Lifeboat CP/M 2.25 CPMVECTOR.HEX Vector Graphics CPMZ100.HEX Heath/Zenith Z100 with CP/M-85 "Generic Kermit" can be used on micros not specifically supported, if the CP/M IOBYTE facility is implemented, and the fields of the IOBYTE point to the right devices. The CP/M-Plus version can run "generically" on any CP/M 3.0 system. See the User Guide for details. The Kermit Users Guide contains instructions for installing or bootstrapping the various versions of Kermit. * Manuals: There are two Kermit manuals: USER and PROTO, a user's guide and a protocol manual, respectively. Four versions of these files are provided: .MSS Scribe (UNILOGIC Ltd text formatter) source. .LPT Line Printer format (overstriking, underscore, etc). .DOC No special effects, suitable for reading on line. .FOR Like .LPT, but with Fortran-style carriage control. The Protocol manual was recently (this week) rewritten. If you have Scribe and the appropriate Scribe device drivers, you can run the .MSS files through it to produce output suitable for printing on any device supported at your site, including the Xerox-9700, Imagen Imprint-10, or other multifont laser printers or photocomposers. As of this writing, Scribe is not entirely bug-free; you may notice some problems with the footnotes in the .DOC and .LPT files. Note that some parts of the user manual rely on underlining to clarify examples; the underlines are missing from the .DOC files, but will be found in the .LPT and .FOR files. The user's guide is intended for users of Kermit (including those who want to install it), the protocol manual is for those who would like to write a new implementation (i.e. a Kermit program for a new machine or operating system). ASCII.MSS is the ASCII/EBCDIC character table, which is included as an appendix in both manuals. MANUAL.HYP is a hyphenation dictionary for building the manual with Scribe. * Other Files: 00README.TXT is this file, which should appear at the top of any alphabetical directory listing, and is the first file on the tape. FLYER.DOC is a short KERMIT "brochure", explaining the distribution policy. MAIL.TXT is the archive of the CCNET/BITNET/ARPANET KERMIT discussion group. The files MAC80.*, M80UNV, etc, are an 8080/8085 cross assembler for the DEC-10 or DEC-20; MAC80.DOC is a brief description. TORTUR.M80 is a "torture test" for MAC80, which illustrates its features. MAC80 is used to assemble CP/M KERMIT, and is mostly compatible with the standard CP/M 8080 assembler. There is also a new, "beta test" version of MAC80. This version assembles Z80 code as well as 8080 code, and it has a real manual. These files are stored as ZAC80, Z80UNV, etc (the same names as the MAC80 files, but starting with a Z instead of an M). HEXIFY.* is a program for converting a CP/M .COM file resident on the DEC-10 or DEC-20 to a CP/M .HEX file. This is handy when binary file transfers are failing to work for some reason. The .HEX file can be LOADed on the CP/M system in the normal way to reconstruct the original .COM file. HEXCOM.* is the inverse of HEXIFY, and provides .HEX-to-.COM file conversion. The files CROSS.* are a general purpose cross assembler for the DEC-10 and DEC-20; CROSS.DOC is the manual. CROSS is used to assemble Apple DOS KERMIT. TTLINK.* is a terminal linking program for the DEC-20, allowing you to log in to another system over a TTY line (e.g. using an autodialer). KERMIT-20 runs TTLINK to execute the CONNECT command. (NTTLINK is a new, experimental version that can send a BREAK). EZFIX.* is a utility for converting EasyWriter files sent to the DEC-20 from the IBM PC into ordinary text form. Strip is a programming for stripping away the 8th bit. KERMIT.WHO is a list of all the sites Columbia has sent KERMIT tapes to. VERSIONS.DOC is a list of all known versions of KERMIT, even those that aren't being distributed yet, showing their status, who's working on them, etc. * Finally... If you make any modifications to Kermit, fix any bugs, or write any new implementations or documentation, please send them back to us on magnetic tape so we can distribute them to other Kermit users: KERMIT Distribution Columbia University Center for Computing Activities 612 West 115th Street 7th Floor New York NY 10025 or via network mail notify CC.FDC@COLUMBIA-20.ARPA SY.FDC@CU20B.BITNET (or .CCNET) We'll return your tape to you with the latest Kermit distribution. ================================================================ ================================================================ ================================================================ [356,43]README.1ST See K11INS.DOC This area contains a version of Kermit for RSX-11. ================================================================ ================================================================ ================================================================ [356,50]README.TXT RSX11M version of Empire. Uses a PLAS region to handle its variables and is known to work under M 3.2, 4.0 and 4.1 with or without FPEM. Uses [7,13] to store maps generated when a "new game" is initiated. ================================================================ ================================================================ ================================================================ [356,51]README.TXT Adventure compiler and run-time system for RSX. Comes with a much expanded version of the original Adventure as an example of how to code one. ================================================================ ================================================================ ================================================================ [356,60]README.1ST Tape rewind program (REW) for RSX Submitted by: Gordon Ross Moore Business Forms, Inc. 300 Lang Boulevard Grand Island, NY 14072 716-773-0473 The contents of this submission are: REW.MAC The source code for rewind REW.CMD The command file to assemble and build REW REW.RNO The documentation for REW in RUNOFF format REW.DOC The documentation for REW README.1ST This file To create the rewind program, do the following: @REW and answer the questions. ================================================================ ================================================================ ================================================================ [356,70]README.1ST EDITOR'S NOTE: This tape came in from an RT-11 system and was not readable via standard utilities. These files have been extracted nevertheless, but beware of extra nulls in them. The LST utility may be of use to remove these (its' source is LISTRS.MAC) elsewhere on this tape. There were no other known transfer errors, but be warned. G. Everhart date: October 21, 1983 from: Dennis V. Jensen Ames Laboratory ISU/USDOE 310 Metallurgy Ames, Iowa 50011 515/294-4823 subject: Release information on HGRAPH and revised DECUS 11-431. HGRAPH is a plotting package which will generate two or three dimensional graphs on a Visual 550 graphics terminal (ektronix 4014 compatable) or on a Bausch and Lomb (Houston Instruments) DMPL plotter. The package is written in RT-11 Fortran using version 2.5 and is also being used on the VAX under VMS Fortran 77 without modifications to the source code. The package is composed of non-device specific code in the file HGRAPH.FOR and then two device specific files: HIPLOT.FOR and VIPLOT.FOR. The user code isidentical for driving the two devices. The plotting device is selected at link time. The files HGRAPH.DOC and HGRAPH.RNO describe how to use the package. The file HGRAPH.SAN is the same as HGRAPH.DOC but includes the graphics examples in a form which is printable on a Sanders printer with RCL. The graphics terminal support uses Tektronix 4014 compatability for graphics and also uss the extended character generator of the V550. The character size option is not supported as a standard part of TEK 4014 and therefore represents a limitataion if used on other "compatable" graphics terminals. (See the subroutine WRTSTR to adapt.) The graphics mode will require that the RT-11 commands "Set TT NOCRLF" and the "Set TT NOFF" commands be in effect to avoid RT inserting characters where the should not be. Under TSX-Plus, this is not a necessary. The Houston Instruments plotter supported can be any of the numerous intelligent models which use the DMPL plot language (ie, DMP-3, -4, -6, -7, -29). Except for the multipen option, none of the DMPL+ features are currently required. The plotter can be either attached to the printer port of a terminal (ala V550) or can be driven by an LS-stylehandler. The Fortran logical unit number controls which method will be used. Due to the number of subroutines that may nested at one time, the executable image will typically need to be linked with a larger stack than the default. (See files VIX.COM and HIX.COM as examples of link options which HGRAPH and modified DECUS 11-431 PAGE 2 may need to be used.) For people with HPLOT's which may desire CalComp or ComPlot compatability, the rest of the files have been included. They are a modification of the DECUS 11-431 distribution which supports the original DMP plotter. (See CCPLOT.DOC for information on what has been changed with respect the original 11-431.) These routines are useful for adapting existing programs to the DMPL plotters or for adapting high level device independent packages to this type of plotter. See file HICOMP.COM to compile the related programs and see file CCLIB.COM to build an object library. The files AXTEST, ALFTST, LGXTST, SYMTST, and LGXTST (all .FOR files) are routines which will test the operation of CCPLOT. ================================================================ ================================================================ ================================================================ [370,60]README.DOC INTRODUCTION There are a number of programs contained herein. CHEKIT : Checks record lengths, Version 1.05. The command file CHEKIT.CMD is the task builder file. TRUNCATE (TRC): Deletes trailing blanks from a file, same file characteristics on the output file as on the input file. The command file TRUNC.CMD is the task builder file. TR1: Same as TRC with the difference that in TRC zero length records (a record with nothing but blanks) are not kept, in this version a zero length record is written. The command file TR1.CMD is the task builder file. SOLO : SOL eliminates duplicate records either in length or content. The command file SOLO.CMD is the task builder file. CLEAR: CLR clears the screen on VT52/VT100 series terminals. The command file CLEAR.CMD is the task builder file. Several of the programs require the use of a object library called NOS. The neccesary source modules are also included and are ASCEBC.MAC, EBCASC.MAC, JDATE.MAC, CDATE.MAC, OPERR.MAC. The best of luck to you. ================================================================ ================================================================ ================================================================ [370,341]README.TXT RSX Fall 83 Sig tape Brian Nelson computer services university of toledo 2801 west bancroft toledo, ohio 43606 (419) 537-2841 TED, a full screen and line editor. See install.doc and mods.txt for more information. Please note the following files: TED.TSK for rsx11m 4.0 or 4.1 TED.EXE for VMS v3.2 TEDPDT.SAV for rt11 version 4 EDRT.RTS sharable image for RSTS v7.2 and 8.0 *.HLB help files The above listed files are binary files and if copied with FLX must be copied in image mode (ie, /IM) The following is the top level README.1ST from the LBLTOOLS backup set on the tape. ================================================================ ================================================================ ================================================================ [307,30]README.1ST Fall 1983 DECUS Distribution Software Tools VOS Joe Sventek Lawrence Berkeley Laboratory The UIC's and their contents for this distribution are: [307,30] TOOLGEN.CMD, the command file for building the LBL Software Tools Virtual Operating System. For more information on the features available in this release, consult the release notes contained in this UIC, RELEASE.DOC. [307,31] Everything you need to build this release of the VOS. [307,32] The source files for the RSX-specific tools and primitives. [307,33] The source files for the portable VOS utilities. [307,34] Source files for the variable-length send/receive driver. In addition, a document describing home directory management for RSX may be found here. Correction files for versions 3.2 and 4.0 of RSX-11M are also provided. [307,35] Archives containing the format input files for the manual entries in sections 2-4 of the manual. [307,36] The distribution of the Software Tools Mail System. [307,37] The TCS archives for the previously distributed Software Tools mail utilities, as well as the additional source files needed for building the tools on IAS. Statistics on this Distribution UIC Blocks Files ________ ______ _____ [307,31] 5353 198 [307,32] 742 15 [307,33] 4936 93 [307,34] 178 13 [307,35] 1717 9 [307,36] ???? ??? NOTE: before performing the toolgen, it is important that you peruse the section of release.doc entitled "Memory Limitations (and how to overcome them). IAS users will need to read both release.doc and [307,37]iasreadme.1st.