RSX/IAS SIG Tape Distribution - Spring 1983 =========================================== This is the RSX/IAS SIG Symposium Tape from the 1983 Spring DECUS Symposium in St. Louis. 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:RSX83A) as an RK07 image (of 38,000 blocks), and the 2nd (/BAC:PRNTRPICS) as a 2nd RK07 image containing a collection of printer pictures (22,000 blocks). Directory [300,1] contains the files documenting the contents of the tape. The following files are present: RSX83ATPE.DOC contains an abstract of the contents of the tape by UIC. 83AREADME.ALL contains a concatenated list of all the README files on the tape. RSX83A.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. BEGIN83A.DOC has a copy of this text. UICSET83A.CMD contains the UFD commands to create all the needed UIC's on device XX:. 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. Jim Neeland RSX/IAS SIG Tape Copy Coordinator Hughes Research Labs MS RL63 3011 Malibu Canyon Rd. Malibu, California 90265 (213) 456-6411 ext. 333 ********************DM0:[307,20]README.1ST;2******************** ********************DM0:[307,20]README.1ST;2******************** ******************************************************************************* [307,20]README.1ST U. S. Geological Survey RSX/IAS SIG Tape 345 Middlefield Rd. Mailstop 77 Spring 1983 Submissions Menlo Park, CA 94025 This UIC contains the USGS submissions for the Spring 1983 SIG tape. Included are the following programs/files: BACBRU Utilities A Pascal program and indirect command file for M-Plus systems to implement incremental disk backups using Virtual Terminals. Provides neatly formatted output from BRU, and may be executed from Batch to provide daily backup with a log of all backed-up files. See [307,20]BACBRU.DOC for futher details. BUGSF82.TXT A list of known problems with the U.S.G.S Fall '82 submissions. AST.RNO Handout accompanying the Spring '83 DECUS session AST.DOC "Hows and Whys of ASTs," originally published in the RSX/IAS Spring '83 DECUS Handout. If you want to know anything about ASTs in RSX, this handout should cover it. NEWFIXER Replacement for FXR... task distributed with M-Plus systems, which recovers from hard memory parity errors. DEC's version has problems; you may want to try using this one. See NEWFIXER.DOC For questions or problems regarding these submissions, please contact Gary L. Maxwell at the address listed above. ********************DM0:[307,50]README.1ST;1******************** ********************DM0:[307,50]README.1ST;1******************** [307,50] README.1ST RUNOFF (version M3.0) -- DECUS Spring '83 Symposium Distribution This submission is a further development of a version of RUNOFF which was submitted to the last two symposia under this UIC ([307,50]). 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 Fall '82 submission are described in the file CHANGES. as items 81-94. The notable changes are: o Added the ability to have up to three tables of contents output. These are intended for contents, figures and tables. Entries can be made in all three tables with an explicit command, or can be automatically made in the "contents" based on the text accompanying CHAPTER, APPENDIX, and HEADER LEVEL commands. The number of header levels which cause entries can be set by the user. User control of outputting of the tables is provided. o Added exit status value set by any warning or error which occurs. The exit value represents the "worst" condition that occurred. The possible values are: 0 (warning), 1 (success), 2 (error) and 4 (severe error [RUNOFF aborted]). o A command error now causes only the remainder of the current command to be ignored, rather than the remainder of the current command _l_i_n_e. o Added LEVEL STYLE command to set (1) level at which section headers change to the run-in style, (2) the number of blank lines output before section headers, and (3) the value to be used for the automatic test page before outputting headers. o Added a limit on the number of consecutive lines which will be hyphenated (limit can be set during task build). Added control of the minimum word fragment which will be left at the end of a line (length can be set during task build). Several bugs present in the last submission have been fixed (apologies hereby offered). README.2ND contains an annotated list of all the files submitted and provides installation information. Submitted by: Chuck Spalding 1202 Charleston Road Mountain View, CA 94043 (415) 965-0557 [307,50] README.1ST -- EOF ********************DM0:[307,50]README.2ND;1******************** ********************DM0:[307,50]README.2ND;1******************** RUNOFF (Version M3.0) This version of DECUS RUNOFF is basically compatible with the previous text processing SIG's version M02 and the current DECUS library version (M02.4). Scores of enhancements and fixes have been made, as summarized in SUMMARY. and described in CHANGES. The RUNOFF manual has been extensively modified, including documentation of all the new features. This release of RUNOFF is a further development of the versions submitted to the Spring and Fall 1982 DECUS Symposia. (The current release includes 94 listed changes. The Spring '82 submission covered up to change 62 and Fall '82 included up to change 80 [unfortunately, change 78 was bug ridden in that submission].) The most notable change made since Fall '82 is the implementation of the ability to have up to three tables of contents in the output document, one of which can be created automatically from chapter and header-level titles. 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. Users are encouraged to report any problems encountered and to provide feedback on the features present and those desired. When reporting a problem, please save copies of the input and output which demonstrate the problem. NOTE This version of RUNOFF cannot be used under RT-11 (version M02.4 can). Submitted by: Chuck Spalding 1202 Charleston Road Mountain View, CA 94043 (415) 965-0557 FILES SUBMITTED README.1ST Introductory comments README.2ND This file RUNOFF.DOC Printer-ready RUNOFF manual (uses backspace underlining) RUNOFF.RNO RUNOFF input file for manual SUMMARY. Summary of new/changed features of version M3.0 (comparison with versions M02 and M02.4) CHANGES. Complete list of all changes incorporated in version M3.0 FILES. List of all changes indicating source files affected RNPRE.MAC Source prefix file which defines all assembly switches DATA.MAC Source for all global data CMTAB.MAC Source for command tables START.MAC Source for task initiation code COMND.MAC Source for command parser ERMSG.MAC Source for initialization and error processing RNCMD.MAC Source for commands FMTCM.MAC Source for commands SETUP.MAC Source for infrequent commands QUEUE.MAC Source for commands for deferring output RUNOFF.MAC Source for main text processing RNFIO.MAC Source for input and output RNORSX.MAC Source for RSX data structures INDEX.MAC Source for index accumulation PINDX.MAC Source for index outputting PRTOC.MAC Source for outputting tables of contents HYPHEN.MAC Source for hyphenation MAKRNO.CMD Do-it-all command file for generating a RUNOFF task file. This file asks the user for selections for all the task build options. RNOIAS.CMD Commands for IAS task builder (NOT TESTED) RNOIAS.ODL Overlay description for IAS (NOT TESTED) RSTASM.CMD Command file for assembling under RSTS (NOT TESTED) RSTBLD.CMD Command file for RSTS task builder (NOT TESTED) RSTBLD.ODL Overlay description for RSTS (NOT TESTED) BUILDING RUNOFF (M3.0) RSX-11M and RSX-11M-PLUS Procedure: 1. You do NOT need to be a privileged user, although the last two steps below may require privileged status. 2. Transfer all files to the UFD you want to work in. 3. Type @MAKRNO and respond to the questions asked. You can press the ESCAPE key in response to any question to get information which will help you decide how to answer. 4. Copy RNO.TSK to the system UFD. 5. If desired, install RNO. It is built to run in GEN partition. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NOTE * * * * The following instructions are adapted from those provided with * * version M02.4. THESE INSTRUCTIONS HAVE NOT BEEN CHECKED. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * RSX-11M UNMAPPED SYSTEMS Users of unmapped systems should follow the procedure outlined for mapped systems. Before beginning the building process, edit the file MAKRNO.CMD to delete the /MM switch and to change the PAR directive to match your system requirements (other changes may be required). RSX-11D/IAS Users of RSX-11D/IAS should follow the procedure outlined for users of RSX-11M Mapped systems. Since the conventions for source and object files are installation dependent, MAKRNO.CMD should be edited as required. For example, RSX-11D/IAS users should change the /MM switch to /MU and change the PAR directive as needed. Building RUNOFF Page 2 Alternatively, IAS users may use command file RNOIAS.CMD to build RUNOFF. The command file contains definitions for the default parameter values and switch settings. The file RNOIAS.ODL contains an overlay description for use with IAS. (THESE FILES HAVE NOT BEEN TRIED!) RSTS/E Before assembling the source files, you must edit the file RNPRE.MAC and change the definitions of symbols RSTS and RSX to "1" and "0", respectively. (Note that some of the features claimed for version M3.0 will no longer be present then--e.g., automatic task extension and exit with status.) The command file RSTASM.CMD can be used to assemble all the source files. (THIS FILE HAS NOT BEEN TRIED!) The files RSTBLD.CMD and RSTBLD.ODL are provided for building RUNOFF for use under RSTS. (THESE FILES HAVE NOT BEEN TRIED!) RNO.TSK is not a privileged program. It should, however, be installed with an <104> protection code if it is desirable for all users on the system to access it. To get a RSTS version of the manual, edit page one of RUNOFF.RNO changing "INCLUDE 1" to "EXCLUDE 1", and "EXCLUDE 2" to "INCLUDE 2". RT-11 This version of RUNOFF does not support use under RT-11. ********************DM0:[312,315]README.DGT;1******************** ********************DM0:[312,315]README.DGT;1******************** DGT DGT is one of the more powerful "foreign tape" utilities that are around. It was written initially for tape positioning, but has been growing for some time and now can handle numerous tape data formats. Among its major supported formats are: ASCII or EBCDIC input in fixed length records of any length blocked up to 100 (with some minor restrictions on total record length). ASCII or EBCDIC output in 80 byte records blocked up to 100 [note: it'd be fairly easy to make record length variable but I never needed to] per tape block Data General RDOS tape input UNIX TAR tape input (creates a separate file with the UNIX pathnames and makes RSX-compatible names out of the last part of the pathnames. Also flags binary files. BCD tapes from old IBM equipment (easy to change char set) DGT can also position tape in either direction by any number of files or records, write endfiles, rewind tape, and set tape characteristics (e.g. parity or density) to anything the driver allows. It has a HELP command (just say DGT HELP if installed) to give key letters and meanings. DGT commands are of the format ,, where information past the blockfactor is often not needed and is optional if not required. is an ASCII command name which I usually abbreviate to a single letter. Only the first letter is examined of the string in any case. A space or comma after the string is required. The unit number is then given as a decimal number for the tape. DGT is customized for MT:, MM:, MS:, or whatever by editing the ALUN.MAC file. ALUN gets the number in and assigns MAGLUN (defined in the TKB file with a GBLDEF) to the appropriate device and unit. DGT works on unmounted or foreign-mounted tape, in M, M+, or IAS (or VAX VMS compatibility mode). The block factor is the number of fixed length records that fit onto one physical record on the tape. DGT is not too smart about this; if it is set up for 80 character record length (with the B command [e.g., B 0,80]) or by default and you tell it that the blocking factor is 100 [e.g. INPUT 0,100] it will write 100 records on the PDP11 even if it reads only 80 bytes on tape. To build DGT, assemble or compile the files that you find referred to in the TKB file, link, and use. When DGT needs a filename (as when reading a file from tape to PDP11, or when writing tape from a file), it prompts for it on a separate line and uses GETCML to allow this to happen from a command file. Be aware that while all commands use GETCML, the format is not normal MCR. When DGT reads 80 byte records, it will remove trailing whitespace on the read. For other record lengths, it leaves the whitespace in. On output to 80 byte records, DGT will re-insert spaces to the end of record. It has a mode to write DG RDOS tapes which is imperfect. Use the DGWRIT program instead for that purpose. It has been tested and works correctly. DGT can however read RDOS tapes fine. No special software need be written on the DG side. A minor customization is occasionally needed in DGT to go through and clear all 200 bits in characters on readin, where ASCII comes in from foreign tapes with the 200 bit set. Such data reads in and generally lists but is almost impossible to edit because of this difference in the ASCII codes used. PDP11 and VAX always clear the 200 bit. You may want to use MTQIO or ASCEBC as utilities; they provide easy and complete tape control or ASCII <==> EBCDIC translation respectively. Glenn Everhart ********************DM0:[312,315]README.1ST;4******************** ********************DM0:[312,315]README.1ST;4******************** [312,*] COLLECTION - SPRING 1983 This collection is being submitted for RSX and VAX users who will find different parts useful. Highlights: [312,315] 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. New enhancement is the ability to read or list Unix TAR format tapes of blocking factors up to the Unix standard of 20. Can selectively extract files from these tapes too. Also still positions tapes, writes EOF, rewinds, reads/writes cardimages (or other length fixed factor files), reads DG RDOS tapes, etc. etc. etc. as before. An EXE is supplied for use with VMS. TPC - Also present is my latest/greatest TPC with a switch to let it attempt to copy past the end-tape foil to get the double EOF on multireel backup sets. Jim Neeland's mod to support TU78's is merged in also, and a fix so it works right when installed. FPEM - A copy of FPEM is included too though it needs work to run on M+ V2 still. Hopefully we can get it debugged sometime by F83. 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. 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,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,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. It also has greater capabilities including full 3D sheet support. Also on RSX the arrow keys now work and commands may be entered lowercase if desired. (Area [312,352] has object libraries for building under VMS and an RSX task image for those who don't have Fortran. [312,346] FXDRV - Memory disk driver mods for multiple systems (M/M+ v3.2,v4, v1,v2), 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,347] A spreadsheet from the Unix world. This sheet is less capable than PortaCalc, uses the Unix termcap routines (not included) for screen I/O. To get it running you'll need something like the termcap screen routines (maybe start with the old TECO screen routine). A bit of documentation of these is present but no code. If anyone wants this badly enough maybe they'll fix it up to compile under DECUS C (the new one in the DECUS library has floats, longs) and submit it for F83. Of course, your friends running Unix might like a copy as is ... [312,350] A CP/M disk utility from the Unix world. Needs some mods to get it running for RSX and of unknown quality. Nevertheless, maybe some kind soul will get time to fix it up for F83. Claims to read, write, list CP/M 1.4 disks on RX drives. Low level I/O needs to be replaced with some form of QIO$ access or some other low level access kluge. Maybe copy to files on other disks, set attributes to 128 byte records, then just read/write the records. This gives 2 utils, one to copy to/from real RX01 or single density RX02, the other this modification utility. Be aware Unix uses bare linefeeds as line terminators; you'll need to TECO lf to crlf to read source files, or the i/o lib will have to. [312,351] My mods to DUPLEX for delayed transmission of text to half duplex systems. Designed to save continual typing of control chars. Useful only for source code transmission. [312,352] OLBs of PortaCalc for VMS and .TSK of PortaCalc for RSX. The task image has F4PEIS linked in so that it MAY work with the emulator. [312,353] Another bit of intercomputer communications software for VAX-RSX communications. [312,357] 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. [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,361] 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. ********************DM0:[312,315]README.TPC;2******************** ********************DM0:[312,315]README.TPC;2******************** TPC -- Fast Tape Copy This is version 1.50 of TPC, the fast tape copy program. There are several enhancements over previous versions. These include: 1. TPC is now serially re-usable when switching copy directions. Previous versions would fail with an Output file Open error. 2. /VE (Verify) and /CM (Compare) switches have been added to ensure accurate copies. "Verify" makes a copy in the indicated direction and then compares the two. "Compare" compares an existing disk file with the tape. 3. Error messages and Help text are now in lower case to avoid the feeling that TPC is yelling at you. Thanks should go to Jim Neeland and Glenn Everhart for bugging me until I finally put the /VE and /CM switches in. Alan E. Frisbie Flying Disk Systems 3786 E. Mountain View Ave. Pasadena, CA 91107 (213) 577-2579 12-May-83 ********************DM0:[312,322]README.1ST;1******************** ********************DM0:[312,322]README.1ST;1******************** 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 ********************DM0:[312,345]README.VAX;1******************** ********************DM0:[312,345]README.VAX;1******************** PortaCalc This file is VAX build notes: To build PortaCalc from supplied object libraries, you need just to extract all objects from a library and link: $LIBR/EXTRACT=*/OUT=PCCAVO.OBJ PCCAVO.OLB $LINK/NOMAP PCCAVO or replace PCCAVO (VT100 version with advanced video) by PCC100 (for VT100 without advanced video) or PCGRAF (for the graphics utility). These should run even if you don't have Fortran. For those with Fortran, the COMPIL.COM file builds these files from source. You can edit the VVKLUGPRM.FTN file first (compil.com copies it to vklugprm.ftn for inclusion in the compiles) to set your max sheet sizes if the ones supplied are too small. The maxima possible then are large enough you are very unlikely to need to go into sources to edit them. The file PortaCalc.rno can become a VAX help library and be integrated with your system help if desired. The graphics utility is described separately in PCG.DOC and there is a file called KEYPAD.DOC in the distribution which describes various files of PortaCalc commands which implement auxiliary keypad functions. It should be edited to reflect any system default changes if these features are to be generally used. Note that if CMDMUN.FOR is compiled with the /debug qualifier, these files reside on device DK:, which may be ASSIGN/USER'd to a particular system area prior to running the local PortaCalc version. The PortaCalc.rno file must be passed through Runoff (possibly DECUS runoff as opposed to DSR) to convert it to a VAX help file format. It is designed to fit on 2 columns (using the LISTRS program to reformat it, available in various places in the DECUS library including 11-SP-6), but can fit on other sizes output with a little editing. Column size of less than 60 characters may fail in some places. Apology: To those who have come to know and love the name ViziKluge which used to appear as this program's alternate title: I have withdrawn the name ViziKluge from the title page since it can be interpreted to mean the program is not really a useful tool. In fact, you will find PortaCalc a spreadsheet equal or greater in power to most any commercial product on the market, of speeds comparable with any of them, and more easily tailored to particular needs than most. I am also mindful of the difficulty of convincing people to use a tool named "vizikluge", since its' command set is not closely related to anyone else's and learning it is another educational chore people may have. This is the reason for the alternate keypad commands (which I may expand and which you will see can be expanded yourself by editing cmdmun.for or perhaps xqtcmd.for) and the alternate keypad diagram. I expect eventually to offer a supported and enhanced version of this program commercially (for a price similar to those of Z80-based sheets, however; I am opposed to super high priced software just because it runs on VAXen or PDP11's and encourage users to revolt against it as I have done). For the present, however, enhancements to this version of PortaCalc are expected at most to include spawning subprocesses and perhaps a Datatrieve interface for the VAX versions only. I'm considering an interface to the public domain RIM DBMS instead, since that DBMS is pretty good and available from Boeing for a copy fee. However, the difficulty of providing a general purpose DBMS interface is considerable where values need to be returned. Therefore, a usable general purpose database interface may wait on a commercialized version which will integrate various other tools as well (including hopefully editing, more complex graphics, and timekeeping). I recommend all who use this product for office automation look into the DTC program from DECUS also (#11-597, code MC $70). It's a highly useful desktop calendar program for doing time based scheduling, meetings, etc. Glenn Everhart 6/14/1983 Additional note: 8/18/83 This version of PortaCalc has 2 VAX versions of interest. The older one uses a random access workfile to hold formulas, and may be used where the workfile provides insurance against crashes or other faults. Since this is a burden on some sites with tight disk quotas, a second version, here called PortaCalc-VM, is provided for VAX only. It is built by running the COMPILVM.COM procedure (possibly after edits to VVKLUGPRM.FTN) and it uses a memory array to hold formulas. The WRKFIL.F4 source of the routine that handles this array is pretty crude and could easily be adapted to keep better track of which array elements are in use, but it works reliably. In this version, the S command allows resetting title and default format specification, but does not modify the data. The ZA command clears data out of the array (virtually; actually, it only zeroes the bitmap), and the X and XD commands are identical. The VM version of PortaCalc does not ask any questions about workfile names (since there are none). Since VMS will treat the big array as demand-zero pages, it normally will hit only those you use, so a large sheet is not a major liability. The PDP11 versions of PortaCalc still use workfiles, since they need the storage and haven't room for it in memory. The XL version of PortaCalc-11, which has virtual arrays available, could conceivably be modified to use this approach, but it is costly in memory and seems of questionable usefulness on any but the very largest PDP11 configurations. If you need it, it only takes about an hour to do the mods, maybe less with my model. The one complication with virtual arrays is that their names must be in subroutine call sequences; hence the WRKFIL subroutine cannot hide the array representation in a modified PortaCalc-XL as it does in the-VM version on VAX. I do not propose to make this mod for PDP11; the workfile approach is usable there, and the FX: driver allows the workfile to reside on a memory disk with NO program mods if this approach is needed. I will not be offering a commercial PortaCalc as such, but am asking for small donations (see README.NOT) to support the effort of maintenance. However, it appears that the RIM database manager is submittable to DECUS (with a US use only restriction), so once that is done, a RIM interface to PortaCalc is more likely. In the interim, the ability to spawn DCL commands from PortaCalc will serve. ********************DM0:[312,345]README.NOT;1******************** ********************DM0:[312,345]README.NOT;1******************** - * F R E E W A R E * - This software is being distributed using the FREEWARE concept. To those unfamiliar with this approach, it works like this: The product is distributed with totally machine readable sources and documents free of charge (except possibly a copy fee). If you find the product doesn't meet your needs, please pay nothing. If however you can use it and it meets your needs, please send a contribution (suggest $50.00) to help defray the cost of maintaining this product and of developing it. This contribution should go to the author. Contributions are completely voluntary and much encouraged. Even if you do not contribute, you are encouraged to copy and distribute the product freely subject to the following restrictions: 1. Do not distribute altered copies without at least a. distributing the unaltered copies as well, and b. sending the author a copy of the modified version in machine readable form 2. Commercial sale of this product is prohibited without the author's expressed written opinion. 3. This notice and all files of the distribution should be distributed; partial distribution is prohibited. User groups, club, etc., are encouraged to continue the distribution subject to the same restrictions above. The same holds for bulletin boards. Exception: Those who purchase this package directly from the DECUS program library are exempted from the request to contribute; the DECUS copy fee is considered to be your contribution (and is mine to the DECUS library). Glenn Everhart 409 High St. Mt. Holly, NJ 08060 ********************DM0:[312,345]README.1ST;1******************** ********************DM0:[312,345]README.1ST;1******************** PortaCalc Brought to you courtesy of Glenn Everhart 409 High St. Mt. Holly, NJ. 08060 USA 609-261-3709 Version 5.4 and 5.4-VM, Summer 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 4 major build files. COMPIL.COM Build for Vax/vms...only compiles. Concatinate the objects and link. 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. 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 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 not used for showing negative numbers but could be adapted to (compare UVTAVO). 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. To get PortaCalc to control the PDP11 more efficiently you may also want to SET /SERIAL=TI: under RSX (which will inhibit MCR from grabbing input you want to send to PortaCalc). 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. 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. WRITEUP: This is a spreadsheet written in Fortran (the only universal assembler) for portability. Its functions are described in the separate document file; it assumes VT100, but the UVT100 routines are the only places the VT100 is actually handled in screen mode, and may be altered for other machines. The spreadsheet sizes may be defined by editing the parameter file Vklugprm.ftn (caveats and restrictions are listed there). There are 2 sheets -- a big physical sheet and a small display sheet which is what's really shown on screen. Sheets may be saved/merged/restored/ linked (via saved files)/printed or hardcopy made onto files. Numerous other functions exist. The sheet's physical size can be tailored to any desired size (subject to memory constraints) by editing VKLUGPRM.FTN and recompiling. 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. There are 2 ODL files, either of which can build a reduced version when the fortran files are compiled with OVKLUGPRM.FTN renamed to VKLUGPRM.FTN, included. There is a bit of extra space so the parameters in that file can be enlarged somewhat. They use a very overlain FCS and F4P OTS. You may be able to do similar things clustering an FCSRES and a F4PRES together too. However, the overlay versions (made with the OMAKE.CMD file) do work, though more slowly than the I/D space one. This at least gets you something on a machine with only normal 11/34 type resources. I assume the F4P or F77 compiler here for the OTS part. You will need to tailor to other Fortran compilers on PDP11's yourself. NOTE: If you get this program working on a non-PDP11, non- VAX, the author would appreciate a (machine readable) copy of the modified version. BUGS: The functions here are mostly tested, but some bugs may remain. Fortran formats are used and any format entered will be used. If you put something in that Fortran can't understand, you lose. Portacalc will try your format once before writing to disk, however, to (hopefully) prevent you from generating an un-reusable work file. Conversely, you can use things like O or Z formats for octal/hex or whatever you like. Formats A and L by themselves mean "display the formula itself"; anything else means "display the number". On entering numbers, any formula containing the characters ".","[","+", "(", or "-" is treated as a numeric; anything else is treated as a formula, unless the string contains the double quote (") character, which forces it to be treated as a literal rather than a number regardless of what else it has. The DF command can fix up this if it's not what you want. Note too that the multi-argument functions: SUM[args] Sum MAX[args] Maximum MIN[args] Minimum AVG[args] Average STD[args] Standard Deviation and the statement IF [v1.RL.v2]true-statement|false-statement must appear at the start of a formula or formula substatement (substate- ments are delimited by \ characters) and the value goes into the current variable cell (which is universally named P## if you want something location independent). It's a good idea to include an else statement in IFs since something gets put in otherwise. Glenn Everhart FURTHER NOTE: In response to some user queries, I have added some comments in the XQTCMD.FTN and OXQTCMD.FTN code about journaling. They are a section of code (look for it just before the string "'*'" (minus the " chars)) which will implement journaling. The syntax of the journaling command would be +J filename which will cause Portacalc to record all commands issued to it in a file of the given name. The command +N will close the journal file and stop recording.. If you want to implement the functions, just take out the initial C's in column 1 and use. It uses unit 10, and I didn't want to overload task size on PDP11's. On VAX it should be fine. Glenn Everhart The journaling commands are implemented by default for VAX; not for PDP11 for size reasons. Try them if you want however; they work well. ********************DM0:[312,345]README.2ND;1******************** ********************DM0:[312,345]README.2ND;1******************** KEYS ON VT100 FOR PORTACALC The files KYP.CMD, KYR.CMD and KYSAUX.CMD implement auxiliary keypad commands when used with PortaCalc for PF1, PF3, and PF4 keys. They need to be inside the login account as presently set up but can come off DK: device if CMDMUN.FOR is compiled /DEBUG. Functions: PF1 (KYP.CMD) WIDE - Sets screen into wide mode and sets up display of 10 columns. (The DB command can vary this) PF2 (no file) HELP (gets to top help page. A reply of Hn instead of just return will get help page n. PF3 (KYR.CMD) NARROW - Sets screen into 80 column mode and sets display back to 7 columns (DB command may vary this) PF4 (KYSAUX.CMD) ENTER - Turns off aux keypad mode and goes into a mode of reading input for expressions to enter, entering them at current cursor position. The Mn command should have previously been used to set automatic motion. Any control character or space as 1st entered character, or \ as first entered character, gets out of enter mode and back to normal command mode. Note if aux keypad mode isn't turned off, various AKl.CMD files (l varies from A to N; see cmdmun.for) may be used for user defined commands. To implement this scheme rename KYSAUX.CMD to KYS.CMD; otherwise you use KYS.CMD which means "recalculate" and the keypad is all a lot of functions. ********************DM0:[312,345]README.OL;1******************** ********************DM0:[312,345]README.OL;1******************** VMS OLB FILES The .OLB files on this tape are VMS native mode objects for various PortaCalc utilities and versions (VT100 normal, VT100 with Advanced Video) (pcgraf is the graphics utility.) To build, extract ALL modules in a library into a big concatinated object file. Then just link it. Ignore errors; it'll work OK. ********************DM0:[312,346]README.1ST;1******************** ********************DM0:[312,346]README.1ST;1******************** The files in this area are edits of the FX driver from the Fall '82 SIG tape. They are not wholly debugged but attempt to do 2 things: 1. Get FXDRV to work under all flavors of RSX11M or M+ 2. Check the fork list frequently so the driver won't hang your system from fork processing too long at a time. The FX driver implements a memory disk. This version still has problems with M+ V2, though it at least doesn't crash systems. It looks like the search logic for finding partitions works wrong in M+ V2 somehow. These files are placed here for some kind soul to fix. I'll try to if I can get time to... ********************DM0:[312,347]README.1ST;1******************** ********************DM0:[312,347]README.1ST;1******************** This area contains a spreadsheet of limited capacity written at CMU for Unix. It will need some work to convert for RSX; in particular some replacement for terminal screen I/O must be built. Hopefully there is enough documentation to do it. ********************DM0:[312,350]README.1ST;1******************** ********************DM0:[312,350]README.1ST;1******************** This area has a Unix program to read/write/list directories etc. on CP/M disks using DEC drives. By some minor editing it ought to be able to work under RSX using DECUS C. The low-level I/O needs to be done. I haven't had time, but am placing this here so some kind soul might do so by the next time. ********************DM0:[312,351]README.1ST;1******************** ********************DM0:[312,351]README.1ST;1******************** This is the famous "duplex" program from DECUS modified to provide the ability to delay between characters or lines sent to remote systems as needed. Kind of a kluge, but useful. Note that Duplex doesn't generate any kind of parity ASCII. For that get XMIT off old RSX SIG tapes; it can. ********************DM0:[312,352]README.1ST;1******************** ********************DM0:[312,352]README.1ST;1******************** These files are VMS object libraries for the default VT100 (AVO and non-AVO) versions of PortaCalc. The .TSK image is however a version of PortaCalc built for straight RSX11M with no special system conditions. ********************DM0:[312,353]README.VAX;1******************** ********************DM0:[312,353]README.VAX;1******************** This directory contains the source for VTH. The files dummy2 and dummy3 are not used at all. To get the system going, edit vth.for, find the places where it references specific files, and change them for your system (or remove them). $ fortran vth,setterm,setpar,getjpi,wait $ link vth,setterm,setpar,getjpi,wait Put a modem onto one of your terminal ports. Assign the logical name dial_out_modem so that vth knows which port to use. Run vth. Issue the RESTART command. (The START command attempts to initialize a specific type of modem which we use here, made by BIZCOMP). At that point all characters you type will be sent to the modem, and all characters sent into the modem will appear on your screen. Type a ^A to return to command mode. At that point the LOGFILE= command can be used to create a log file. Please see the help file for details. ********************DM0:[312,353]README.1ST;1******************** ********************DM0:[312,353]README.1ST;1******************** This is a terminal I/O program for VAX that supplements VAXNET and handles parity. ********************DM0:[312,354]README.BKO;1******************** ********************DM0:[312,354]README.BKO;1******************** This UIC contains the source, object modules, and task images for a game similar to the (once) popular arcade game, BRKOUT. To play you need: 1 PDP-11 (or VAX-see below) computer running RSX-11M or RSX-11M+ 1 VT100 terminal at 9600 baud (Advanced Video Option NOT required) A brief set of playing instructions are present in the file BRKOUT.DOC Two versions of the task are provided, BKOFSL.TSK for those of you who have a supervisor mode FCS library, and BKO.TSK for everybody else. The supervisor mode library version runs in about 10K words of memory, and the regular version in about 13K words. Task build command files are provided for both versions: (BKOFSL.TKB and BKO.TKB) The source code is written mostly in RATFOR, with some assembly language. A command file to assemble and compile the source is provided (BRKOUT.BLD) Enjoy!! Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,354]README.CEN;1******************** ********************DM0:[312,354]README.CEN;1******************** This UIC contains the source, object modules, and task images for a game similar to the popular arcade game, CENTIPEDE. To play you need: 1 PDP-11 (or VAX-see below) computer running RSX-11M or RSX-11M+ 1 VT100 terminal at 9600 baud (Advanced Video Option NOT required) A brief set of playing instructions are present in the file CNTPED.DOC Two versions of the task are provided, CENFSL.TSK for those of you who have a supervisor mode FCS library, and CEN.TSK for everybody else. The supervisor mode library version runs in about 12K words of memory, and the regular version in about 15K words. Task build command files are provided for both versions: (CENFSL.TKB and CEN.TKB) The source code is written mostly in RATFOR, with some assembly language. A command file to assemble and compile the source is provided (CNTPED.BLD) Enjoy!! Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,354]README.MSL;1******************** ********************DM0:[312,354]README.MSL;1******************** This UIC contains the source, object modules, and task images for a game similar to the popular arcade game, MISSILE COMMANDER. To play you need: 1 PDP-11 (or VAX-see below) computer running RSX-11M or RSX-11M+ 1 VT100 terminal at 9600 baud (Advanced Video Option NOT required) A brief set of playing instructions are present in the file MISSIL.DOC. Two versions of the task are provided, MSLFSL.TSK for those of you who have a supervisor mode FCS library, and MSL.TSK for everybody else. The supervisor mode library version runs in about 13K words of memory, and the regular version in about 16K words. Task build command files are provided for both versions: (MSLFSL.TKB and MSL.TKB) The source code is written mostly in RATFOR, with some assembly language. A command file to assemble and compile the source is provided (MISSIL.BLD) Enjoy!! Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,354]README.PAC;1******************** ********************DM0:[312,354]README.PAC;1******************** This UIC contains the source, object modules, and task images for a game similar to the popular arcade game, PACMAN. To play you need: 1 PDP-11 (or VAX-see below) computer running RSX-11M or RSX-11M+ 1 VT100 terminal at 9600 baud (Advanced Video Option NOT required) A brief set of playing instructions are present in the file PACMAN.DOC. Two versions of the task are provided, PACFSL.TSK for those of you who have a supervisor mode FCS library, and PAC.TSK for everybody else. The supervisor mode library version runs in about 13K words of memory, and the regular version in about 16K words. This program has been run in both a PDP 11/44 and a PDP 11/23 successfully, although it is a bit too slow in the 11/23. (The PAC.TSK version has also been run successfully in compatibility mode on a VAX 11/750, although brief inspection indicates that the control-C AST and the mark time directive in the main program loop do not seem to work. Neither of these problems seriously affects the useability of the program.) Task build command files are provided for both versions: (PACFSL.TKB and PAC.TKB) The source code is written mostly in RATFOR, with some assembly language. A command file to assemble and compile the source is provided (PACMAN.BLD) The attempt has been made to give this game as much of the "feel" of PACMAN as possible. Your comments, suggestions, complaints, praise, etc. would be appreciated, in particular whether the game is too hard or easy. Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,354]README.1ST;1******************** ********************DM0:[312,354]README.1ST;1******************** April 20, 1983 This UIC contains improved versions of the games PACMAN, CENTIPEDE, MISSILE COMMAND, and BREAKOUT first submitted on the Spring '82 SIG tape. The changes are as follows: 1) All games have been modified to perform many fewer QIOs in writing to the VT100. As a result, the games play more efficiently and no longer bring a PDP-11 to its knees when they are running. This means other people can use the system for useful(?) work while you are playing games! 2) All games have been built with a call to subroutine TIMCHK, which allows them to run only during the hours 11:30 AM to 12:30 PM, or before 8:00 AM or after 5:00 PM. If you would like to change these hours, modify TIMCHK.RAT or write your own version. If you want no restrictions, I have provided a TIMCHKALT.OBJ, which enforces none. To use it, re-task build the tasks after either a) renaming TIMCHKALT.OBJ to TIMCHK.OBJ, or b) modifying the task build (.TKB) files to link to TIMCHKALT. 3) PACMAN has been modified with a new maze that is more in line with the arcade version dimensions, and that is much more exciting to play with. 4) Disk files for the games have been renamed so that the source for all four games can coexist in one UIC. All files pertaining to PACMAN start with PAC, all CENTIPEDE files start with CEN or CNT, all MISSIL COMMAND files start with MIS or MSL, and all BREAKOUT files start with BRK or BKO. See the other README files in this UIC for directions on using the games, and contact me if you have any questions/problems. Glen Hoffing 609-338-2441 RCA Gov't Communication Systems Mailstop 10-4-6 Camden, NJ 08102 ********************DM0:[312,355]README.1ST;1******************** ********************DM0:[312,355]README.1ST;1******************** This UIC contains some subroutines mostly involved in helping the FORTRAN programmer with Files-11 operations. The contents are as follows: UACTIV - subroutine indicates whether a specified task is active or not. UCREAT - subroutine returns the creation date of a file. UEFBLK - subroutines sets or retrieves the end-of-file block number of a file. UFILNO - subroutine returns the file number of a file (called by UCREAT) UFIND - subroutine indicates whether a specified file exists. UVERS - subroutine returns the file version number of a specified file. UNLOCK,(UNLOCKRMS) - UNLOCK is a FORTRAN USEROPEN routine that prevents a file from being locked in the event of an abnormal task failure. To use it, a FORTRAN programmer must include the statement "EXTERNAL UNLOCK" in his definitions, and perform a file open as he normally would: i.e., "OPEN (UNIT=nn,NAME=xxx,...,USEROPEN=UNLOCK)". (UNLOCK is the FCS version, and UNLOCKRMS the RMS version) UERINI,UERQIO,(UERINIRMS) - UERINI and UERQIO are subroutines used to provide a standard hardcopy error message interface for QIO operations done in FORTRAN. UERINI is called once at the beginning of a task, and UERQIO is called after the completion of each QIO operation. If the I/O status is anything other than "1 - successful" or "0 - pending", UERQIO will print a message on the issuing terminal in a standard format indicating the task name, LUN, time of day, I/O device, and I/O status. (UERINI is the FCS version and UERINIRMS is the RMS version) (UERQIO is the same for both FCS and RMS) EDP.TSK - This is a modified version of DEC's DMP utility, whose only difference is that when you specify the /AS switch, the data is converted from EBCDIC to ASCII before being dumped. It is thus useful for dumping files encoded in EBCDIC. It is based on the old version of DMP, so it does not support the newer DMP switches such as /LC and /SB. Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,356]README.1ST;1******************** ********************DM0:[312,356]README.1ST;1******************** This UIC contains a complete set of RSX HELP files. They are oriented towards our 11MPlus Version 2.0 system, but should be of general use to anyone. These files contain the following enhancements over the DEC supplied ones: 1. The top level HELP commands, HELP and HELP LIST, give a more structured picture of what help is available. 2. The DEC supplied help files have been edited to correct errors in both spelling and substance. It is, for example, extremely frustrating to request help on a Fortran error code, and be given a description of the wrong error code. I believe the help file for Fortran error codes is now entirely correct. I do not claim the other DEC supplied files are now perfect, but they are better than they were. 3. HELP is now available for all MCR commands. (DEC for some reason left out a few.) 4. HELP ERRORS now provides a top level description of what help is available for Fortran, FCS, RMS, and executive directive errors. Access to help for these errors is much improved, for instance, help can be obtained on a specific FCS error in decimal, octal, or symbolic. Thus, HELP FCS ERROR -16, HELP FCS ERROR 360, and HELP FCS ERROR PRI all provide the same information. 5. Help is available for a multitude of DECUS utilities, including: ATT AVD CCL CVL DOB DVD FRC GREP LST RATFOR RUNOFF SORTS SPEED SRD SUPMAC TECO TPP TRN TTY T2T UNDELETE UVT100 VIRTUAL_DISKS WHO XRF 6. HELP ASCII and HELP EBCDIC will print out ASCII and EBCDIC character values in octal, decimal, or hexadecimal. I will try to maintain and improve these help files. If you find any errors in them, please drop me a note. Glen Hoffing RCA Gov't Communications Systems Front and Cooper Sts. 10-4-6 Camden, NJ 08102 ********************DM0:[312,357]README.1ST;1******************** ********************DM0:[312,357]README.1ST;1******************** 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. Among the features I would like to see added: - Year-At-A-Glance in 132 column mode with two rows of six months each - Menu option(s) to print out appointments, in day, week, month format - Support for non VT-100 terminals (general cursor positioning calls) 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. This distribution kit includes the following files: DTC.ULB - Universal library with Fortran source code - and DTC.HLP which DTC needs to be in [1,2] DTC.OLB - Object library containing DTC object code DTCF.TSK - Task image of DTC for PDP-11's with floating point processor DTCN.TSK - Task image of DTC for machines without floating point processor DTC.DAT - Empty text file for appointments README.1ST - This file 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 "7/4/83" or "7483" or anything else. 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. To use DTC, you need to create an empty DTC.DAT file first (and also any other calendar files you expect to need.) The simplest way to do this in RSX is to use the command PIP DTC.DAT=NL: and in VMS MCR PIP DTC.DAT=NL: but any method will do, including using an editor to set it up. Don't be alarmed about occasional open file errors; most have been fixed but just re-run DTC if any still show up; they don't corrupt your calendar file. I haven't seen any for awhile, so don't think many (if any) remain, but I could have missed a spot where a redundant close is needed. You may fix if need be. ********************DM0:[312,357]README.2ND;1******************** ********************DM0:[312,357]README.2ND;1******************** 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 ********************DM0:[312,360]README.VDD;1******************** ********************DM0:[312,360]README.VDD;1******************** 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 ********************DM0:[312,361]README.NOT;1******************** ********************DM0:[312,361]README.NOT;1******************** - * F R E E W A R E * - This software is being distributed using the FREEWARE concept. To those unfamiliar with this approach, it works like this: The product is distributed with totally machine readable sources and documents free of charge (except possibly a copy fee). If you find the product doesn't meet your needs, please pay nothing. If however you can use it and it meets your needs, please send a contribution (suggest $25.00) to help defray the cost of maintaining this product and of developing it. This contribution should go to the author. Contributions are completely voluntary and much encouraged. Even if you do not contribute, you are encouraged to copy and distribute the product freely subject to the following restrictions: 1. Do not distribute altered copies without at least a. distributing the unaltered copies as well, and b. sending the author a copy of the modified version in machine readable form 2. Commercial sale of this product is prohibited without the author's expressed written opinion. 3. This notice and all files of the distribution should be distributed; partial distribution is prohibited. User groups, club, etc., are encouraged to continue the distribution subject to the same restrictions above. The same holds for bulletin boards. Exception: Those who purchase this package directly from the DECUS program library are exempted from the request to contribute; the DECUS copy fee is considered to be your contribution (and is mine to the DECUS library). Glenn Everhart 409 High St. Mt. Holly, NJ 08060 ********************DM0:[312,361]README.1ST;1******************** ********************DM0:[312,361]README.1ST;1******************** 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. ********************DM0:[326,1]README.1ST;2******************** ********************DM0:[326,1]README.1ST;2******************** The North Texas Local Users Group The files contained in [326,*] were submitted to the North Texas Local Users Group Library. The submissions: [326,001] - README.1ST - This file. [326,002] - FILMS - Video fun from Mike Drabicky of Rockwell International. [326,003] - Pretty Pictures - Computer Printer Pictures collected by John Jenkinson of MOSTEK [326,117] - MISC - Various routines from Jeff Hamilton of E-Systems Greenville. If you need help in reaching the authors, please contact: John Jenkinson MOSTEK Corporation 1215 West Crosby Road MS 32 Carrollton, Texas 75006 ********************DM0:[326,2]README.1ST;1******************** ********************DM0:[326,2]README.1ST;1******************** FILMS FOR RSX-11M This account includes films I have managed to "borrow" from a variety of sources. They have been adapted for RSX-11M/M+ for use thru the HELP command. The account includes the FILM.HLP file along with a variety of films called *.FLM. In order to make the films available to your users, you must do two things. First, copy these files into [1,2] on your system disk. And second, edit [1,2]MCR.HLP and include the following two lines: 2 FILMS @FILMS Your users with then be able to type in HELP FILMS to tell them what films are available for viewing. They can then type HELP FILM filmname to see a particular film. You might also want to add the FILM keyword to the list of available helps so that others will know that help is available. Submitted by: Mike Drabicky Rockwell International 1200 N Alma Way MS 406-280 Richardson, TX 75081 ********************DM0:[326,3]README.1ST;1******************** ********************DM0:[326,3]README.1ST;1******************** These are some computer printout pictures that almost everyone has seen, but may not have a copy of. Now you do. The FILEnn.LST are generally overprinted. The *.PI0 AND *.PI1 aren't. Some may be found offensive. I didn't make any of them, I only collected them (I like to see how other people waste their time). See FILEnn.IDX for titles of the FILEnn.LST's. ********************DM0:[326,3]README.2ND;3******************** ********************DM0:[326,3]README.2ND;3******************** SIG TAPE EDITOR'S NOTE: All the files referenced in this directory are in the 2nd BRU backup_set on the RSX83A tape, backup_set name PRNTRPICS. The backup set is an RK07 image, with 21905. blocks used. Note that this is just a bit too big for an RL02; if you /EXCLUDE FILE8.LST, all the rest will fit. ********************DM0:[326,117]README.1ST;2******************** ********************DM0:[326,117]README.1ST;2******************** These submissions are from Jeff Hamilton E-Systems Inc. P. O. Box 1056 CBN 28 Greenville, Texas 75401 The Files: FFT.FTN - FFT routine IBITR.MAC - FORTRAN Callable bit reversal routine IBITR.FTN INTL2ETEK.FTN - Intel formatted object records to extended Tektronix Hex records ISISRD.FTN - ISIS floppy program. ********************DM0:[332,12]README.1ST;1******************** ********************DM0:[332,12]README.1ST;1******************** BONNER LAB RUNOFF The following is documentation on the revisions to the BONNER LAB RUNOFF. This revision will be available on the Spring 83 DECUS tape. The various revisions are made available to the Houston LUG as they are generated. The previous ver- sions were available from the Fall 82 DECUS tape [332,12] and from the HOUSTON LUG. The table of contents features were available on the HOUSTON LUG version but not on the Fall 82 tape. This version of RNO includes most of the features of DSR, and as a bonus escape sequence handling, a macro facility (substitu- tion), and may other features documented in the RUNOFF.DOC manual. The manual has been rearranged to logically group the commands, and a whole new section INTRODUCTION TO THE COMMANDS has been added. In addition several paragraphs of explanation have been added to most sections. This revision adds a few fea- tures and fixes several bugs. ENHANCEMENTS 1. TABLE of CONTENTS - This was omitted from the Fall 82 tape but made available to the Houston LUG. This includes the following commands 1. .TOC 2. .END TOC 3. .STYLE CHAPTERS 4. .ENABLE TOC 5. .DISABLE TOC 6. .SEND TOC 2. No form feed is issued at the beginning of the first page, but one is present at the end of the last page. This makes it easy for the user to concatonate .DOC files to produce composite files. DSR produces form feeds neither at the start or end, and the old RUNOFF put them at both places. The user must be careful to make sure forms are correct- ly positioned before starting. 3. The maximum input buffer size has been expanded to 512 without any extra growth in the program size, or loss of dynamic memory. This en- hancement was available to the Houston LUG. 4. .INDENT LEVELS will produce both left and right indentation of header levels 5. .ENABLE LEVELS allows control over which header levels are used, and which go to the .RNT (table of contents) file. 6. .AUTOSUBTITLE command same as in DSR. 7. .AUTOTITLE command to control automatic titles. 8. .PAGE SIZE has been extended to set permenant spacing also. 9. .HEADER LEVEL command has been changed to work differently if no title is included. This change gives the user complete flexibility in for- matting header levels. 10. .NUMBER LEVEL command has been added 11. .NUMBER LIST command has been added. 12. Some restrictions on the .DEFINE statements have now been removed. The .DEFINE SUBSTITUTE statements will now work in any order. They will also detect duplicate label definitions and reject them. 13. .DISPLAY CHAPTER and .DISPLAY APPENDIX have been extended in a manner similar to .DISPLAY ELEMENTS. When used in conjuntion with .STYLE CHAPTER they allow you to reformat chapter headers into a large varie- ty of styles. 14. Similarly .DISPLAY NUMBER has been extended to allow the user more styles for the page number. 15. The range of possible list entry numbers has been increased to 4000. 16. .PERMANENT FOOTNOTE command has been added to automatically have a header between the text, and the footnotes on a page. For example this can automatically draw a line between the text and the footnotes. 17. .IMMEDIATE TEST PAGE has been added. This is a .TEST PAGE without a break. This is very useful for filled text. 18. In addition .TEST TEXT and .IMMEDIATE TEST TEXT have been added to test if enough room for n lines of text remain on a page. Unlike test Page 2 page these depend on the current spacing. 19. .TEXT command and .END TEXT commands guarantee that text braketed by these commands will be printed on same page if possible. 20. .LEFT has been added for DSR compatibility. 21. .ENABLE BAR has 2 indentation parameters added. 22. Some changes were made to speed up processing when the /PA/CH/AP switches are used. 23. FIGURE DEFERRED was added similar to the same command in DSR. 24. .CHAPTER LAYOUT was added to allow changing the layout of the first page of each chapter. In other words the main text can have a differ- ent layout from the title page of each chapter. 25. The .LAYOUT command was slightly modifed to change only the layout of the next and subsequent pages, but not the current page. Without this modifacation a change in layout can give undesirable results. For users who set the layout once at the beginning this change will behave the same as previous versions. 26. Several permanent substitutions are defined when Runoff starts. These are: $$DATE $$TIME $$DAY $$MONTH $$YEAR $$HOURS $$MINUTES $$SECONDS. As the names imply they are used to output the current date and time. 27. .FLAGS SPECIAL is a command to simplify the escape sequence handling. It allows the user to define a single character as a flag to trigger a series of escape sequences. By doing this RUNOFF can be made compati- ble with other programs such as TEDI. For example TEDI used [ to shift up for superscripting, and RUNOFF can now do the same. 28. Escape sequence attributes have been added to .DEFINE ESCAPE. These refine escape sequence handling to simplify document preparation. 29. Substitution labels ignore the letter case for all but the first char- acter of the label. This change was made to make the substitution syntax more flexible and easier to use. 30. Underlining and overstriking are now allowed in .TITLE, .SUBTITLE, and .CHAPTER/.APPENDIX commands. 31. .ENABLE/DISABLE TABS commands have been added. These allow you to se- lect normal tabulation or have tabs interpreted as spaces only. 32. More error messages have been added and in general the error messages are more informative and helpful. 33. Equation formatting has been added. This formats multiple nested fractions using the braces and slash {A}/{B} as the necessary flags. 34. The .NO SPACE command has been added from DSR. 35. The command .HALF SPACING enables half line spacing for standard word processing printers. 36. Several commands were changed to be more DSR compatible. This in- volved performing a SKIP rather than a BLANK, or a TEST TEXT rather than TEST PAGE. 37. .IF,.IFNOT, and .ENDIF were added. .ELSE was omitted, and the syntax is DSR compatible. .VARIANT serves the same purpose as the /VARIANT switch. 38. In addition to the .DOC file a .HLP file has been generated. BUGS now FIXED 1. .STYLE CHAPTER did not work correctly. This is only important to those who recieved the Houston LUG distribution. 2. Header levels caused the next line to have incorrect justification, and filling. Issuing any command which caused a break, or skipping a line fixed this problem. 3. Footnotes would not correctly justify and fill. This could have been worked around by using .NO FILL inside footnotes. 4. Footnotes would sometimes cause the first line of the next page to have incorrect fill and justification. Page 3 5. STYLE HEADERS wouldn't work in conjuction with NO HEADER, and TOP MAR- GIN 0. 6. .ELLIPSES would sometimes cause mistabulation. 7. .SUBPAGE command at the beginning of the first page causes RUNOFF to bomb. This is a nonsensical command sequence so nobody should have had problems with this one. 8. SUBSTITUTION failed unpredictably if a large number of substitutes were defined. 9. /RI switch did not work at all properly. This could be worked around with a permanent left margin. 10. RNO failed to underline the last word of a section terminated by \& if the last word occurred on the first word of an output line. 11. In .HEADER LEVEL command if capitalized first character is desired and the first char. was already in caps, the second char would be capi- talized. The workaround was to not capitalize any section headers or use .STYLE HEADERS to disable automatic capitalization. 12. .LITERAL or .END LITERAL commands may bomb RNO with odd address trap. Also .LITERAL didn't turn off the flags properly if it worked. The use of .FLAGS ALL and .NO FLAGS ALL provided a partial workaround. 13. If overstriking preceeds underlining on the same line, underlining by /UL:S or /UL:L will fail to underline correctly. /UL:B worked however. 14. If both .NUMBER PAGE and .NUMBER SUBPAGE are used before a .SUBPAGE command the page number will be wrong. 15. Runoff can mess up the number of spaces in a line if the following conditions were met. .FILL .PERIOD are enabled and the end of the input line is terminated by a punctuation followed by a space. Since there is no need to have a space after a punctuation at the end of the line the workaround was to remove the final space. 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 prob- lem is very maddening. 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 demonstrate it in just a few lines of input I would appreci- ate the effort. I will try to fix bad bugs or at least create a wor- karound. John Clement ********************DM0:[335,1]README.1ST;5******************** ********************DM0:[335,1]README.1ST;5******************** ******************************************************************* [335,1]README.1ST Spring 1983 RSXSIG Tape St. Louis DECUS Symposium ******************************************************************* The contributions in [335,*] are from the Greater Lansing Local Users Group (GLLUG). This LUG encompasses the southern central Michigan area and includes members from Michigan State University, Lansing Community College, Olivet College, Alma College, Lansing State Journal, Oldsmobile, Buick, and other local businesses and state agencies. The file [335,1]ROADMAP.DOC contains a brief description of the contents of this submission. The submissions for the Spring 1983 RSXSIG tape are from the following three members of GLLUG. Hugh Gregg (517-355-5125) Department of Physiology T. V. Atkinson (517-353-4511) Department of Chemistry Phil Hoffman (517-353-5215) Department of Chemistry Michigan State University East Lansing, MI 48824 ******************************************************************* ********************DM0:[335,10]README.1ST;3******************** ********************DM0:[335,10]README.1ST;3******************** [335,10] VECTOR sources for May 1983 RSX DECUS tape. Submitted by the Greater Landing Local Users Group. VECTOR is a device independant graphics 'switch', allowing the FORTRAN programmer identical access to all known graphics devices. VECTOR is basically a pen-up/down and move subroutine; for additional capabilities, see MSULIB routines such as SYMPLT, a symbol plotting routine. If the user writes to VECTOR's device number 0, a file of the vector commands is made, which is then used by RASTER to allow access to raster oriented devices. With both VECTOR and RASTER, the user can access virtually all graphics devices. To build VECTOR for use with MULPLT and RASTER, select the devices that you want supported. Support is currently implemented for the following devices: TEK 4010 terminal VTEK4010.PGM RETROGRAPHICS enhanced VT100 VRETROG.PGM MATROX enhanced VT100 VMATROX.PGM HP 7470A graphics plotter VHP7470.PGM DEC GIGI terminal VGIGI.PGM GRINNELL GMR-37 VGRIN.PGM The following line will build a copy of VECTOR for use with MULPLT: PIP VECTOR.FTN=VECTOR.TLE,Vxxxx.PGM,Vxxxx.PGM,...,VECEND.PGM You may include as many vector devices as you wish, to the limit of memory. Usually, 2-4 devices may be included when resident libraries are used. Then compile and insert into MSULIB in [335,21]. ********************DM0:[335,11]README.1ST;3******************** ********************DM0:[335,11]README.1ST;3******************** [335,11] MSULIB sources for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. MSULIB is a collection of subroutines used at Michigan State University as a base for higher level graphics processing. Most of the routines have general and specific documentation in the subroutine itself. One of the most commonly used routines is SYMPLT, a symbol plotting subroutine which uses libraries of characters adapted from the Hershey Library of Occidental Fonts. For more information, see SYMPLT documentation (in the MULPLT documentation accounts). Copies of MSULIB.OLB are in account [335,21]. To rebuild the libraries, use the indirect command file MSULIB.CMD. ********************DM0:[335,12]README.1ST;3******************** ********************DM0:[335,12]README.1ST;3******************** [335,12] RASTER source for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. RASTER is a general purpose rasterizing program that converts vector oriented data to raster data for dot matrix printers. RASTER currently supports two printers (Printronix P-300 and Integral Data Systems 132 column printers). Code for support of Versatek printers is still under development, and should be available for the next DECUS tape. RASTER can easily be converted to other printer types. See the comments in RASTER.TLE. To build the libraries, use the command file RASTER.CMD. The command file RASTERTKB.CMD should produce task images. For more information on use, see RASTER.DOC. ********************DM0:[335,13]README.1ST;3******************** ********************DM0:[335,13]README.1ST;3******************** [335,13] RASTER libraries and task images for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. The two task images in this account are built without libraries, and should work on any RSX V3.2 or better system. RASTERFOR.TSK has been built with FORTRAN IV, and linked with an EIS only library, and should run on any machine. RASTERF77.TSK requires the floating point unit of the newer PDP11's. For more information, see account [335,12]. ********************DM0:[335,14]README.1ST;4******************** ********************DM0:[335,14]README.1ST;4******************** [335,14] Symbol library source files for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. This is the source files for the symbol libraries used by SYMPLT. These libraries are derived from Hershey Library of Occidental Fonts. To build for inclusion in a program (internal library) (MULPLT): MAC ROMSIM.OBJ=ROMSIM.MAC To build as an external library file: MAC ROMSIM.SYM/EN:ABS=ROMSIM.MAC For more information, see SYMPLT documentation. ********************DM0:[335,15]README.1ST;2******************** ********************DM0:[335,15]README.1ST;2******************** [335,15] Built SYMPLT libraries for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. This account contains the complete set of external symbol libraries used by MULPLT. The source to these files are in account [335,14]. For more information, see SYMPLT documentation. ********************DM0:[335,20]README.1ST;2******************** ********************DM0:[335,20]README.1ST;2******************** [335,20] MULPLT sources for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. MULPLT - The MULtiple file PLoTting program developed at Michigan State University produces graphs of publication quality (when the output device has the needed resolution) on a wide variety of graphics devices. Multiple data sets can be plotted as well as a wide variety of special features. Entire posters for poster sessions have been done with MULPLT and its special features. For more information, see the MULPLT documentation. The WIZARD's menu for MULPLT gives descriptions of each of the known commands, as well as the special features. Try it, you may find it useful. Account [335,21] contains task images that should work on any RSX11M V3.2 or better system. It should also work on RSX11M+ systems, but this has not been tested. ********************DM0:[335,21]README.1ST;3******************** ********************DM0:[335,21]README.1ST;3******************** [335,21] MULPLT objects and tasks - May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. This account contains a couple of task images and the object libraries that built them. Each task has been built with with support for two vector oriented devices (RETROGRAPHICS enhanced VT100's, and the HP7470A plotter). If the tasks are rebuilt with resident libraries, there will be more room in the task image for more graphic device handlers. Both versions provided here can write vector lists to be used as input to RASTER, providing hardcopy output. MULPLTFOR - FORTRAN-IV compiled, linked for EIS. MULPLTF77 - FORTRAN-77 compiled, linked for FPU. Brief descriptions of the commands are given in [335,22]WIZARD.DOC, the Wizard's menu of commands and their defaults. Note that this file is set up for 15 pitch printing. To get on the air with MULPLT, get a copy of the Wizard's menu. Make a file that looks like this: RD 1,1 RD 2,2 RD 3,3 RD 4,5 RD 5,4 RD 6,6 Run MULPLT, and type the following: AG 1=TTn: where TTn: is the TEK 4010 emulator FN filename filename is the name of the data file GO 1 produces the plot A graph should appear. The only way to really learn MULPLT is to play with it. It can be fun. Good luck. You may also want to try "NP DINK" and then "GO 1". DINK.PDL and DINK.SPF are "Plot Descriptor" and "SPecial Feature" files for MULPLT. ********************DM0:[335,22]README.1ST;2******************** ********************DM0:[335,22]README.1ST;2******************** [335,22] MULPLT Documentation for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. This account contains .RNO and .DOC files for the MULPLT documentation. All the figures for the documents are in [335,23]. As we all know, documentation is hard to keep current. As a result, only the Wizard's menu has been updated for the current version of MULPLT. The SYMPLT and AXIS documents describe the corresponding subroutines in MSULIB and are used by MULPLT. The advanced user will need only the Wizard's menu to make plots. This menu is formatted such that if it was printed at 15 pitch, it would fit on an 8 1/2 by 11 inch paper. ********************DM0:[335,23]README.1ST;2******************** ********************DM0:[335,23]README.1ST;2******************** [335,23] MULPLT documentation - figures, etc. for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. This account contains the MULPLT commands (.PDL files) and the associated special features files (.SPF) to make all the figures for the MULPLT documentation. These files assume that the symbol libraries are on logical disk SB: in account [10,10], and were designed to be output on the Versatek electrostatic plotter. Some of the commands will be site specific, so some work may be necessary to output documentation at your site. ********************DM0:[335,24]README.1ST;3******************** ********************DM0:[335,24]README.1ST;3******************** [335,24] MULPLT on-line help files. Submitted by the Greater Lansing Local Users Group. This account contains help files for MULPLT. To use, place a redirection marker in your main help file, as follows: 1 MULPLT @ddn:[335,24]MULPLT.HLP ********************DM0:[335,30]README.1ST;3******************** ********************DM0:[335,30]README.1ST;3******************** ******************************************************************* [335,30]README.1ST Spring 1983 RSXSIG Tape St. Louis DECUS Symposium T. V. Atkinson Department of Chemistry Michigan State University East Lansing, MI 48824 517-353-4511 ******************************************************************* This account contains tutorial units on RSX that we have used for several years in our graduate course in electronic instrumentation for scientists. RSX-1 - A tutorial unit on RSX-11M. Introduces the student to various concepts of using a modern well endowed operating system. Included are such topics as on-line-HELP, system facilities, private device maintainence, program development, file manipulations, and editing. The idea is to expose a student with no assumed computer background, well actually, FORTRAN might be helpful, to the facilities needed for program development and file maintainence. The unit assumes MCR, DIR (Paul Sorenson's), and CCL and is compatible with Version 3.2 and 4.0. The unit uses a group of write protected files in a write protected directory. The student must also have access to a private device and a write enabled public device. This version is written to use DP0: for the write protected files, DP1: as the write enabled public device, and DX: for the private device. Other configurations can be easily utilized. The file RSX1BLD.CMD can be used to set up the write protected files. ******************************************************************* ********************DM0:[335,40]README.1ST;3******************** ********************DM0:[335,40]README.1ST;3******************** [335,40] MPRNO - simple RNO for MULPLT; May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. MPRNO is a quick hack to take a paragraph of text and convert it into a special features file for MULPLT. This allows the user to make right and left justified, proportionally spaced text of any size characters. Very useful when creating posters. ********************DM0:[335,41]README.1ST;2******************** ********************DM0:[335,41]README.1ST;2******************** [335,41] KILL: ABO * (at TI:) for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. KILL is a utility that aborts all running tasks at the issuing terminal. It is very handy when using CCL - ie. a TYPE command spawns PIP, but most users don't care to know this. KILL doesn't care either - it just aborts whatever is running, however many things are running. It does check for not aborting things like MCR... and the like. To build, use the provided indirect command file. ********************DM0:[335,42]README.1ST;2******************** ********************DM0:[335,42]README.1ST;2******************** [335,42] MIDNIGHT - pseudo batch processor for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. MIDNIGHT is a program that looks on specified disks, all accounts for files MIDNIGHT.CMD. Each file found is executed, creating log file output. This task is expected to be scheduled to run at midnight to run CPU intensive jobs in a batch type manner. More info in the program itself. To build, use the supplied indirect command file. ********************DM0:[335,43]README.1ST;2******************** ********************DM0:[335,43]README.1ST;2******************** [335,43] BYECHK - disk quota checking for May 1983 RSX DECUS tape. Submitted by the Greater Lansing Local Users Group. BYECHK is a utility, installed as ...BYE that checks the disk usage of the current user. If a predefined quota has not been exceded, the user is logged off. If the quota has been exceded, the user is requested to clean up his/her account and then BYE again. To build, use the supplied indirect command file. ********************DM0:[335,44]README.1ST;3******************** ********************DM0:[335,44]README.1ST;3******************** [335,44] HPFIX - a utility to cancel suspend/supression at a terminal. Submitted by the Greater Lansing Local Users Group. This program checks a terminal line to see if it is suspended and/or supressed (^O or ^S). If either or both is set, they are reset. To build, use supplied indirect command file. ********************DM0:[344,1]README.1ST;33******************** ********************DM0:[344,1]README.1ST;33******************** K M S K I T R E A D M E . 1 S T V 4 . 1 *************************************************************************** ** Please note. Support for the KMS enhancements is dying fast. ** ** (DEC would refers to this as Catagory Z on the SPD for KMSKIT.) ** ** No attempt has EVER been made to implement the V4.1 kit as a package.** ** The SLP files were written to conform to the source files supplied as** ** part of the RSX-11M V4.1 Field test. They may not conform to the ** ** source files in the released software. 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!! ** *************************************************************************** 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. Paul Sorenson says he is submitting CCL for inclusion on this UIC. 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 18-May-1983 ********************DM0:[344,61]README.1ST;1******************** ********************DM0:[344,61]README.1ST;1******************** CCL VERSION 9.0 CCL V9.0 addresses several limitations/restrictions in CCL V8.0, while attempting to retain CCL's best virtues; non-privileged, SMALL and flexible command interpreter. The most important feature in V9.0 is a new parameter parsing scheme which allows the user to redefine command line parameter delimiters. Command delimiters may be altered using a new CCL command file line, the PARAMETER DELIMITERS LINE, described under CCL COMMAND FILE FORMAT. This facility is coupled with the redefinition of the command parameter designators to make parsing of more complicated command syntaxes possible. Revised and updated CCL.RNO and CCL.HLP files give a more complete description of these changes. V9.0 still attempts to retain full V8.0 compatibility. CCL command files may switch back and forth between the enhanced V9.0 parsing and the V8.0 compatible parsing. A new CCL command file has been added: a group wide command file under LBn:[ggg,5]GRPCCL.CCL. Additionally, the order CCL command files and which command files will be opened is controlled by the conditional assembly file PRECCLASM.MAC. CCL V9.0 no longer considers the FCS "FILE NOT FOUND" error to be fatal for any CCL command files. When CCL fails to identify a user command, CCL CHAIN's to its catchall based on its installed taskname; if this is ...CA., chain to ...CA1; if we're ...CA6, chain to ...CA7, etc. Of lesser significance, the catchall task for CCL when it's installed as an alternate CLI maybe reconfigured (using TASK BUILDER options or the ZAP utility) to bypass MCR completely. In general, most of CCL's important data structures are alterable by TASK BUILDER or ZAP; consult "CCL TASK OPTIONS" in CCL.RNO. Support for the "HEY" command has been added to the standard command file "WAIT FOR TASK" action line by including the "%P%$" special parameters to signify a "prompt" (with exit status) and "exit when done" sequence. Also, task names specified in "WAIT FOR TASK" lines default to "TTn", and will automatically attempt to connect to "XYZTn" before trying to connect to task "...XYZ". The DCL "DLY" command cannot be implemented from a standard CCL command file, requiring the inclusion of the DCL.MAC module if the delay command must be supported. SPECIAL NOTE: With support for redefining the command delimiters, the definition of the "KEYWORD" is no longer fixed. This means support for automatically sending a "HELP" command line when the keyword terminates in a "?" has been dropped. In its place, the installer may select that all command lines ending with a "?" be considered a HELP request (this requires one of CCL's command files to recognize the "?" keyword !!!). Also, when CCL is operating under V9.0 parsing rules, all user input in response to a CCL QUERY LINE is parsed just as if it had been entered on the original command line !!! To get started with CCL V9.0, execute the CCLGEN indirect command file, @CCLGEN. As with V8.0, heavily used command sequences may be supported by an internal table to improve system response. Installers are urged to debug all CCL command line sequences from standard *.CCL files prior to embedding them in the CCL.TSK image. The TABLEGEN.CMD command file will take any valid *.CCL command file and generate the MACRO-11 code required by CCL. A debugged (??) internal table, TABLE.KMS, is again supplied, and utilizes many new V9.0 features in implementing many convenient commands. The MACRO code in TABLE.KMS was generated by submitting KMSTABLE.CCL to the TABLEGEN command file, and then editing in the code in TTTABLE.MAC which includes the special control/escape character sequences to erase VT52 screens, etc. Support for the "BIG" table distributed with V8.0 has been dropped. In its place, UTILTABLE.CCL is a standard CCL command file which will issue "FLYING-INSTALLS" for most DEC RSX-11M utilities. Any bugs or aberrant behavior should be directed to CCL's supporters: James G. Downward KMS Fusion, Inc PO Box 1567 Ann Arbor, Mi 48106 (313)-769-8500 and myself, Paul Sorenson Pulmonary Research, S-3 Mayo Clinic Rochester, MN 55905 (507)-284-8395 ********************DM0:[350,300]README.1ST;2******************** ********************DM0:[350,300]README.1ST;2******************** [ 3 5 0 , 3 0 0 ] The major submission from the Southeastern Minnesota Local User's Group for Spring 1983 is yet another revision to CCL, the console command language. CCL V9.0 has been submitted under the auspices of Jim Downward and appears under the [344,61] KMSkit UFD. This account contains two SLP correction files to the executive and INStall task respectively: 1) INITL.SLP implements pre-allocation of QIO packets during a virgin system boot under 11M V4.0 in the same manner as a RSX-11M V3.2 correction file submitted to the RSXSIG by Dan Steinberg in 1980. 2) INSPS.SLP is a corrected and slightly enhanced version of the same file submitted by our group last year. INSPS.SLP defines a new switch to INStall, "/RTC", which consolidates the functions of the /RUN, /TASK and /CMD switches. CCL is used for the large majority of all our task dispatching, but is confined to the 79. character command line limit set by 11M. The "/RTC" switch syntax is identical to the /CMD switch and uses the first 3-6 RAD-50 characters in the command line as arguments to an implied /TASK=xxxxxx switch saving 12 bytes in the MCR command line (/CMD already implies /RUN=REM). Any problems encountered, and suggestions for enhancements should be directed to Paul Sorenson Pulmonary Research, S-3 Rochester, MN 55905 (507)-284-8395 ********************DM0:[352,4]README.1ST;1******************** ********************DM0:[352,4]README.1ST;1******************** [352,4]README.1ST - ST. LOUIS SPRING 83 - FILES SUBMITTED BY: SRD Working Group Bob Turkelson NASA/Goddard Space Flight Center Code 933 Greenbelt, MD 20771 (301) 344-5003 This UIC contains the files for building SRD V6.3. The modifications made by the SRD Working Group since V6.2 are: o Merged in /SM, /HD, and /BK switches from Glen Everhart's Fall 1982 version ([312,332]). o Added a requirement that a file specification appear on the command line (with or without /SE:) whenever /DE is specified. Command SRD /DE using the previous version deleted every file in the directory, which would surprise you if you had meant to type SRD /BE instead. Note that as a result of this change, purging the entire directory requires SRD */PU rather than SRD /PU. o Changed SRD so that the command NAME/DE will now delete all NAME.;* files, rather than all NAME.*;* files; that is, when no period is specified in the file specification, SRD will no longer delete all files of any type with that name field. o Corrected bug which caused version number selection to fail to list the proper files in many cases. Sometimes files were listed which should not have been, and sometimes files which satisfied the selection criteria were not listed. o Added Psects to every module in order to facilitate /MU on RSX-11M-PLUS. o Revised SRD.CMD to process RSX-11M-PLUS/SUPLIB and flattened out M-PLUS version. The *.C63 files are cumulative correction files which have already been applied to the V6.0 source files. They are provided here for reference purposes only. The *.MAC files are those for V6.3. Procedure: @SRD ! Asks configuration questions and ! builds SRD Modify SRD.HLP to show the defaults you have selected for your system, and refer to it in [1,2]MCR.HLP. 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. The SRD Working Group plans to make additional modifications before the next SIG tape. 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 ********************DM0:[364,2]README.1ST;2******************** ********************DM0:[364,2]README.1ST;2******************** THE FOLLOWING PROGRAM IS SUBMITTED BY: HARRY ATHERTON UNIVERSITY OF CINCINNATI MEDICAL CENTER DEPARTMENT OF PEDIATRICS, ML 541 231 BETHESDA AVE. CINCINNATI, OHIO 45267 PHONE (513) 872-5341 THIS SUBMISSSION CONTAINS SEMAPHORE DIRECTIVES FOR THE RSX-11M AND RSX-11M-PLUS EXECUTIVE. THE MATERIAL FOR RSX-11M-PLUS V2.0 IS IN [364,22]; THE MATERIAL FOR RSX-11M V4.0 IS IN [364,24]. THESE DIRECTIVES ARE USEFUL FOR SOLVING PROBLEMS OF CONCURRENT ACCESS OF MULTIPLE TASKS TO DATA STRUCTURES (OR ANYTHING ELSE). A DESCRIPTION OF THE DIRECTIVES AND INFORMATION FOR ADDING THEM DURING A SYSGEN ARE GIVEN IN SEMINFO.RNO. INFORMATION ON SEMAPHORES IS GIVEN IN THE PAPER "IMPLEMENTATION AND APPLICATION OF SEMAPHORES IN RSX-11M" PRESENTED AT THE FALL 1979 DECUS. REPRINTS ARE AVAILABLE FROM THE ABOVE ADDRESS. ********************DM0:[364,2]README.2ND;1******************** ********************DM0:[364,2]README.2ND;1******************** SINCE MAKING THE INITIAL SUBMISSION TO THE SPRING DECUS TAPE, RSX-11M-PLUS-V2.1 ARRIVED. THERE ARE SEVERAL CHANGES TO THE EXECUTIVE DIRECTIVE COMMONS WHICH AFFECT THE SEMAPHORES. TO REDUCE CONFUSION I HAVE ALSO SUBMITTED THE MATERIAL IN [364,26] WHICH HAS INSTRUCTIONS (IN SEMINFO.DOC) AND FILES FOR IMPLEMENTING SEMAPHORES IN RSX-11M-PLUS-V2.1. I HAVE NOT RECEIVED RSX-11M-V4.1 AS OF THIS DATE SO I DON'T KNOW WHAT CHANGES MAY BE REQUIRED TO ADD THE SEMAPHORES TO IT. HARRY ATHERTON 7/20/83 ********************DM0:[370,1]README.TXT;1******************** ********************DM0:[370,1]README.TXT;1******************** 1983 Spring DECUS Symposium TAPE COPY FACILITY (SIG TAPE) submission From: City of Gainesville Information Systems Division P.O. Box 490 200 East University Ave Gainesville, Florida 32602 (904) 374-2020 Mark C. Weston PDP-11/70, 512KW, RM05, RM80, TU16, 64 ports under RSX-11M-PLUS V2.0 Our submission: CONVERT - a program for converting EBCDIC coded files containing embedded binary data (i.e. it only converts EBCDIC coded characters via a table describing the record layout). CALL - an attempt at having the PDP control a DF03-AC to do the calling. It worked under M+ V1.0 with a jumper on DTR (or was it DSR?), but the autobaud detect screws it up now, and I cannot seem to control this from the task. Anyone have ideas. TIMER - a nice little task for printing the time on the console on the hour. DAILY - a program that is a part of our Computer Assisted Dispatch system (which is going into the DECUS library soon) that will spawn a batch job at midnight that spawns additional batch jobs. Example batch jobs are included. LA100 - a nifty program for controlling the features of a LA100-YA/RA (without keyboard) just like the SETUP key on the LA120 (it is configured to control a specific port and therefore just one printer). CPU - a crude way to determine the CPU busy percentage time (well you just run this task at priority 0 and it endless loops and you count how many time it looped in a second and the you you subtract that from the max and ...). DOW - a program to return the day of the week in for ICP (a.k.a. Indirect Command File Processor, "@", "AT."). ********************DM0:[370,21]README.1ST;5******************** ********************DM0:[370,21]README.1ST;5******************** This file describes the submission to the Spring 1983 RSX tape from the Washington DC LUG. The contents of this UIC are as follows: NOTBAD.* A F77 program (along with TKB file and task image) to write a fake bad block descriptor block on a newly created virtual disk so that INI or BRU won't complain. Also included is a command file that can be used to create a virtual disk and run NOTBAD on it. VD*.*,AVD,DVD A release of the original virtual disk software modified for RSX11M Plus 2.0 EDT.CMD A command file that remembers the last filename edited EXE.CMD A command file that compiles and taskbuilds C or F77 programs We hope you enjoy these programs. They are supplied without any warranty. Don Rubin S.E.T. Inc. LUG Librarian ********************DM0:[370,200]README.1ST;1******************** ********************DM0:[370,200]README.1ST;1******************** THIS IS THE README.1ST FILE FOR THE CONTRIBUTIONS TO THE SPRING 1983 DECUS SYMPOSIUM PROGRAM EXCHANGE THROUGH THE RSX SIG FROM USAFETAC, SCOTT AFB, ILLINOIS. IN THIS DIRECTORY ARE THE FOLLOWING FILES: DSPLOG.FTN - THE SOURCE FOR THE 'DISPLAY LOGIC' PROGRAM PRESENTED IN A SHORT PAPER AT THE SPRING 1982 (ATLANTA) DECUS SYMPOSIUM UNDER THE TOPIC "EMBEDDED PDL AIDS FORTRAN PROGRAM DESIGN AND MAINTENANCE". THIS SOURCE PROGRAM IS ITSELF A COMPLETE ILLUSTRATION OF THE PRINCIPLES OF EMBEDDING PROGRAM DESIGN LANGUAGE, OR PSEUDO-CODE, IN A STRUCTURED FORTRAN PROGRAM, WHERE THE STRUCTURE IS GRAPHICALLY ILLUSTRATED BY THE LEVEL OF INDENTATION OF BOTH THE FORTRAN STATEMENTS AND THE PDL STATEMENTS (WHICH ARE WRITTEN ON SPECIALLY-FLAGGED FORTRAN COMMENTS). THE DSPLOG PROGRAM, WHEN EXECUTED, WILL EXTRACT THE EMBEDDED PDL FROM A FORTRAN SOURCE AND DISPLAY IT ALONE, SO THAT THE STRUCTURE AND LOGIC OF THE PROGRAM CAN BE STUDIED INDEPENDENTLY OF THE CODE. NATURALLY, TO USE THIS TECHNIQUE SATISFACTORILY ONE MUST HAVE A CERTAIN AMOUNT OF SELF-DISCIPLINE IN ORDER TO MAKE THE SOURCE AND COMMENTS CORRESPOND TO EACH OTHER APPROPRIATELY. DSPLOG.PDL - A PRINT FILE OUTPUT FROM THE DSPLOG PROGRAM OPERATING ON ITS OWN SOURCE TEXT, ILLUSTRATING THE PRINCIPLES STATED ABOVE. PRNDOC.PGM - AN INDIRECT COMMAND FILE CONTAINING THE SOURCE TEXT (FORTRAN 4-PLUS) FOR THE "PRINT DOCUMENTATION" PROGRAM USED AT USAFETAC TO PRINT EMBEDDED USER MANUALS (SUCH AS CAN BE FOUND WITHIN BOTH PRNDOC AND DSPLOG). THE COMMAND FILE SETS UP THE COMPILATION AND TASK-BUILD OF THE PROGRAM. PLOTSM.SUB - AN INDIRECT COMMAND FILE CONTAINING THE SOURCE TEXT (FORTRAN 4-PLUS) FOR THE "VIRTUAL" HALF OF THE VIRTUAL PLOTTER PACKAGE. PLOTTR.FTN - THE FORTRAN 4-PLUS SOURCE TEST FOR THE "REAL" HALF OF THE VIRTUAL PLOTTER PACKAGE. THE VIRTUAL PLOTTER PACKAGE WAS PRESENTED IN A POSTER PAPER AT THE SPRING 1982 (ATLANTA) DECUS SYMPOSIUM. IT PROVIDES A VERY SIMPLY WAY TO PUT A VIRTUAL PLOTTER ON A COMPUTER SYSTEM WHICH DOES NOT HAVE A REAL PLOTTER; THE VIRTUAL PLOTTER SUBROUTINE SIMULATES THE PRESENCE OF AN ACTUAL PLOTTER SOFTWARE PACKAGE, ACCEPTING THE ARGUMENTS PASSED TO IT AND WRITING A TRANSFER FILE WHICH CAN BE MOVED (E.G. VIA TAPE) TO A SYSTEM HAVING A REAL PLOTTER. ON THE SECOND SYSTEM, THE PLOT TRANSFER PROGRAM "PLOTTR" READS THE TRANSFER FILE AND CALLS THE ACTUAL PLOTTER SOFTWARE. THE PACKAGE AS PRESENTED HERE USES CALCOMP-STYLE CALLS, WITH SOME ADDITIONAL SUPPORT FOR A VERSATEC RASTER PLOTTER. IT CAN READILY BE TAILORED TO THE PARTICULARS OF ANY SIMILAR PLOTTER SOFTWARE SYSTEM. ALSO INCLUDED ARE A FEW SUBROUTINES USED BY SOME OF THE ABOVE PROGRAMS. THESE ARE ALL IN THE FORM OF INDIRECT COMMAND FILES CONTAINING THE FORTRAN 4-PLUS OR MACRO-11 SOURCE TEXT PLUS THE COMMANDS NEEDED TO COMPILE OR ASSEMBLE THEM. THEY ARE AS FOLLOWS: BEGIN.SUB - USED TO TYPE STARTING MESSAGE AND DTG QUIT.SUB - USED TO TYPE FINISHED MESSAGE AND DTG (DOCUMENTATION ONLY; ENTRY POINT IS IN "BEGIN".) TRMSG.SUB - USED FOR SOME TERMINAL I/O. CHAR7.SUB - USED TO BUILD LARGE (7X7) CHARACTERS MESSG.SUB - USED FOR TERMINAL OUTPUT OF SIMPLE MESSAGES. (OBSOLETE--SHOULD BE REPLACED WITH TRMSG.) TABIT.SUB - USED TO CHANGE TABS TO CORRECT NUMBER OF SPACES. PLEASE NOTE THAT ALL OF THE ABOVE SOURCES ARE EXACTLY AS THEY APPEAR ON OUR CURRENT SYSTEM, EXCEPT FOR THE ADDITION OF THE CAVEAT REPEATED BELOW. NO EFFORT HAS BEEN MADE TO CLEAN UP THE CODE PURELY FOR THIS DECUS DISTRIBUTION. IF YOUR PROFESSIONAL SENSIBILITIES ARE OFFENDED BY SOME OF THE THINGS YOU SEE IN THESE FILES, PLEASE ACCEPT OUR APOLOGIES. THE CURRENT STATE OF OUR ART IS MUCH BETTER, BUT OUR RESOURCES DO NOT PERMIT RETROFITTING SOFTWARE FOR STYLE UNTIL MAINTENANCE IS REQUIRED FOR OTHER PURPOSES AS WELL. GOOD LUCK! C.S.Z. C C C C************************************************************************ C* * C* THIS SOFTWARE IS RELEASED FOR PUBLIC USE UNDER THE PROVISIONS * C* OF AIR FORCE REGULATION 300-6, MAC SUPPLEMENT 1, PARA.11-7, * C* BY USAFETAC/ADW, SCOTT AFB, IL 62225. THIS SOFTWARE IS * C* RELEASED "AS-IS"; THE U. S. AIR FORCE HAS NO WARRANTY * C* RESPONSIBILITY OR LIABILITY FOR THE OPERATION OR USE OF * C* SOFTWARE RELEASED UNDER THIS POLICY. * C* * C* RELEASE OF THIS SOFTWARE IS BEING DONE THROUGH DECUS, SO * C* ALL USUAL DECUS DISCLAIMERS APPLY AS WELL. * C* * C* UNDER THE PROVISIONS OF THE REGULATION CITED ABOVE, NO * C* CONTRACTOR MAY CHARGE THE GOVERNMENT FOR THE USE OF THIS * C* SOFTWARE DURING THE PERFORMANCE OF ANY CONTRACT WITH THE * C* GOVERNMENT. * C* * C* USERS WHO OBTAIN THIS SOFTWARE THROUGH DECUS DISTRIBUTION * C* ARE WELCOME TO SEND COMMENTS TO THE AUTHOR, AS FOLLOWS: * C* USAFETAC/ADW * C* ATTN: MAJOR CARL S. ZIMMERMAN * C* SCOTT AFB, IL 62225 * C* GIVEN THE EXIGENCIES OF MILITARY SERVICE, A REPLY TO YOUR * C* COMMENTS CANNOT BE GUARANTEED. * C* * C************************************************************************ C ********************DM0:[370,210]README.1ST;1******************** ********************DM0:[370,210]README.1ST;1******************** Submitted by: Rick Webster Caterpillar Tractor Co. Mail stop: AD235 600 West Washington St. East Peoria, Il. 61630 This UFD contains the 1983 Spring DECUS Symposium Tape submission from Caterpillar Tractor Co. It contains mostly fixes or re-writes of software submitted by others on previous RSX SIG tapes as well as some original stuff. The following software is provided on an "as is" basis only. Caterpillar Tractor Co., disclaims all warranties on the programs, including without limitation, all implied warranties of merchantablity and fitness. Note: FILES.DOC lists the files in this distribution and identifies which of the following catagories they fall in. Documentation - RNO and HELP files created at Caterpillar have been included and HELP for all the utilities in this distribution. In addition, files there is a RNO help file and VT100 and LA120 help files (operator's reference cards). Also included is RNO.TSK in case your version of RUNOFF isn't the same as ours. Build command - Individual build command files are supplied for each utility. files Also included is a master command file, BUILDALL.CMD which will allow you to selectively build all utilities. Before building any utilities, you will have to copy several files to this UFD from an RSX11M V4.0 distribution kit. For WHO we need a patched or unpatched MLTUSR.OLB and MCR.OLB For COR we need an unpatched SHUFL.MAC which has been renamed to SHUFL.VGN For CONFIG we need an unpatched SGNPER.CMD CONFIG.CMD - This command file is used in conjunction with the command files CONFIG1.CMD and CONFIG2.CMD. It is used to give a sysgen-like listing of a saved answer file. The output looks similar to the SYSGEN printout when the saved answer file was originally created. The command files must be on the current default device and UIC to function properly but the input saved answer file can be anywhere. To use CONFIG, do the following: >@CONFIG saved-answer-file output-file where: saved-answer-file is the name of your save answer file output-file is the name of the file to contain the sysgen listing (Default is TI:) If either are un-specified on the command line, you will be prompted for them. If output is directed to a file, it will also be printed on TI: The output will contain the appropriate SYSGEN question with the response that is in the saved answer file along with the appropriate symbol name used in the saved answer file. Note: You will need a copy of SGNPER.CMD from an unpatched RSX11M V4.0 distribution kit. CONFIG2.CMD must be created prior to running CONFIG. This is done with a SLP correction file to SGNPER.CMD as follows: SLP @CONFIG2.COR MERGE.CMD - Command file to create concatenated RSX11M V4.0 listings with a cross-reference. This was inspired by the command files submitted by Ralph Stamerjohn on the Fall '80 tape for RSX11M V3.2 but this one uses EDT instead of TECO. In addition, it will also give concatenated listings of EXCOM1, EXCOM2 and LDR if your system uses them. To use it: 1) Enter @MERGE 2) You will be prompted for the device that contains the Executive and Driver sources and the device that contains you system. 3) MERGE will ASN to you system disk and set the UIC to [1,34] 4) Note that an EDTINI.EDT file is created there and later deleted, so if you have any EDTINI.EDT files in [1,34] they will also be deleted. 5) MERGE will read your RSXBLD.CMD to determine how to merge the sources and whether you have executive commons or not. Then PIP will be used to merge the sources, EDT will then run to massage the initial merged sources and finally MAC and CRF will run to create the listings. EDTINICLS.CMD - This is a Computer Managed Instruction course (CMI) on the advanced usage of EDT initializer files. It uses the EDTINI file described by David Spencer of Infinity Software Corp., in the Nov. 1982 issue of the DEC Professional Magazine, as an example of an initializer file and goes through a detailed description of how that file works. Part of the tutorial is driven by indirect and part is driven by EDT itself so that the new commands can be tried as they are described. In addition, this command file provides an excellent example of how the new features in V4.0 Indirect have really made Indirect an interpretive programming language that allows you to edit and test code with no intervening assembly, compilation or task build. This command file can be executed from anywhere as long as there is a UFD there to create temporary files. We put it on a training disk and have a CCL command (EDTINI) which translates to "@VD1:[200,206]EDTINICLS" Note: This will only run on a VT100 or VT100 look alike. Also the command file EDTINISAM.CMD must be run prior to running the tutorial, to create the sample initializer file EDTINICLS.SAM. This was necessary since the initializer has imbedded carriage control and FLX screws up the file. By creating the file with Indirect, I could hide the carriage control from FLX. TCF - Utility to send any octal string to any terminal. This is a re-write of a program that was submitted on a previous SIG tape. It still works the same as the original version but has a number of additional capabilities. These include the following: Indirect command file input, directing sequences to another device, passing ASCII strings in command line, upper and lower case support on command line, large letter output similar to the print spooler's flag pages. See TCF.RNO for details. Virtual Disk - This software was obtained from Ralph Stamerjohn's submission on the New Orleans, Spring '79 DECUS symposium tape, UIC [346,100]. The virtual disk package has been extensivly modified and enhanced. AVD and DVD have been modified to provide new functionality and two new utilities were added, VDA and VDC. In addition, enhancements were provided to allow the virtual disk driver to keep track of the number of qio's occurring on each unit since the last system boot. Three utilities are provided to allow a user to display this information. These are: VDQIO, VDQ and VDRPT. Virtual disks are in wide use here at Caterpillar and have been a real life saver. Thank you very much, Ralph. See VD.RNO for details. WHO - Task to display logged on users. This software was originally obtained from the New Orleans, Spring '79 DECUS symposium tape, UIC [301,25]. It has been modified to use the user subroutine option of HELLO and BYE rather than SLP corrections, to make it easier to implement on new releases of RSX11M. To build it, you will have to put a copy of MLTUSR.OLB and MCR.OLB in this UFD. The new versions of HEL and BYE will have file names of HELLOTCM.TSK and BYETCM.TSK. To use WHO, install the TERCOM common, install TLOGGR and WHO, remove ...HEL and ...BYE and install HELLOTCM and BYETCM. See WHO.RNO for details. COR and SPC - allow creation of partitions on the fly from the GEN. SPC is a modified DEC shuffler SHF... which is used by COR to unconditionally shuffle the GEN partition. You will need a copy of SHUFL.MAC from an unpatched RSX11M V4.0 distribution kit, in this UFD with a file name of SHUFL.VGN in order to build SPC. See COR.RNO for details. OPA - Online system POOL Analyzer. Obtained from the San Diego, Fall '80 DECUS symposium tape, UIC [301,31]. It contains a number of fixes over the original. See the release notes in OPA.RNO for details. This has been a very useful program to us at Caterpillar and I would like to thank Jim Neeland for the original submission. UND - Utility to un-delete all deleted files in a particular UIC. Obtained from the Atlanta, Spring '82 DECUS Symposium tape. UFD [312,14]. This version has some minor bug fixes and the error messages have been enhanced. See UND.RNO for description REI - Reincarnate specific deleted or undeleted files who have corrupted file headers. Obtained from the Los Angeles, Fall '81 DECUS symposium tape, UFD [307,22]. This version has minor bug fixes and enhanced error messages. See REI.RNO for description HOL - Utility to display a map of the free areas on a FILES-11 disk. Originally obtained from the Miami, Spring '81 DECUS symposium tape, UIC [373,20]. It has been modified to display logical block numbers in decimal (instead of octal) but with the option to display in octal. We use this program a lot when trying to place Virtual disks on our large disks that have bad blocks. The Virtual disk package in this UFD allows placement control through the /PL switch, allowing us to put VD:'s on a disk in the most efficient manner. See HOL.RNO for details. TTIO - Routines and macros to do terminal I/O. Used by VDA routine in the Virtual Disk package. See TTIO.RNO for details. ********************DM0:[370,220]README.1ST;1******************** ********************DM0:[370,220]README.1ST;1******************** This UIC contains a traffic analysis program, and assorted articles. The largest contribution is ERLANG, a fortran program which solves the Erlang B blocking formulas for traffic analysis. This is very useful in wide variety of aplications where many users compete for a limited resource, or wait on a single queue for one or more servers. The subject is explained in a paper at the Fall 1982 symposium under the somewhat misleading title of "Avoiding Congestion", and will be given at the Spring 1983 symposium under the title "Sizing Communications Requirements". The text is in this UIC as SIZCOM.DOC, and in the proceedings and should be read before ERLANG.DOC, which explains the program. DOCPRP.DOC is a few notes on how to get your documentation in a form which will be correctly transmitted on FLX tapes, such as symposia collections, using TECO (even if you have never used TECO). There is also a suggested procedure for recovering files which have already been garbled, which also works for RT-11 tapes read on RSX. UT1.DOC is an article from the Multi-tasker on adding a user translation table to MTAACP. SORT.DOC is yet another comparison of sort timings: this one done by actually running various Fortran sort routines on an RSX system. If you are still using the Bubble sort, you are wasting your time. See also "Internal sorting using Cobol-11 and Watbol-11" in the Spring 1981 proceedings. M8085.MAC is a version of the macro prefix file M8008.MAC in the DECUS library. It allows assembly of 8080, 8085 and most Z80 programs with the regular PDP-11 Macro assembler by using M8085 as a prefix. M8085.EXT is a version with user added routines (like subroutine calls, push, pop, etc.) PROM takes the output of the Macro Assembler (such as is produced by M8085 above) and changes it to Intel MDS format for transmission to a PROM programmer. OTSMOD is a tool for making Fortran OTS module overlays. If a Fortran-IV-Plus or Fortran-77 program is taskbuilt with the /MA switch on the map, OTSMOD will extract the names of the OTS modules, eliminate duplicates, and sort them alphabetically. This can then be used with the ODL file distributed with fortran to overlay the OTS. MULTI is a simple program to calculate throughput for one or more processors sharing one or more memory banks. QUERY.CMD creates an empty Datatrieve dictionary using RMSDEF. For those without a fortran compiler, task images which have been built NOT using any resident libraries, and checkpointable, are included, but you MUST have a floating point processor. Object modules are not included as you must have the OTS modules to build the task, and that is a DEC product. Although written in Fortran-77 (Fortran-IV-Plus), few extensions are used, and they should run or be easily convertable to Fortran-IV. Comments on any of the above are welcome. B. Z. Lederman I.T.T. World Communications 67 Broad St. N.Y., N.Y. 10004 ********************DM0:[370,230]README.1ST;1******************** ********************DM0:[370,230]README.1ST;1******************** This directory contains several tasks and command files that I have found useful. These come with the standard DECUS grarantee (ie - if it doesn't work or crashes your system, tough). The phrase "Will run under" means I have tried it under these operating systems, and had no problems. The phrase "Should run under" means I have not tried it, but know of no reason why it needs to be modified to work under these operating systems. T. R. Wyant Central Virginia LUG E. I. DuPont de Nemours & co TFD - P.O. Box 27001 Richmond, Virginia 23261 TIZ - Task Image Zapper Source Language - Fortran-77 Will run under - RSX-11M V3.2, RSX-11M+ V1.0 and V2.0 Should run under - RSX-11M, at least back to V3.0 and forward to V4.0 Function - Provide formatted dump of task image label blocks, showing name, partition, priority, creation date, LUN assign- ments, and so on. Most of the items dumped can be modified. This grew out of a task written to deal with the M+ V2.0 task builder's incorrect common area access assignment (since patched). CALC - Calculator and radix converter. Source Language - "@" processor. Will run under - RSX-11M+ V2.0 Should run under - RSX-11M V4.0 Function - Do integer calculations in octal or decimal, and radix conversion to or from ASCII (word), RAD-50, or any radix from 2 thru 16. User can create numeric symbols on the fly to store results for later use. Note that the calculations string is interpreted in "@" fashion (left to right), rather than in algebraic fashion (* and / before + and -). Also, trapping errors in the calculation string requires servicing Type 2 errors with an ONERR directive, ignoring the manual's contention that you can't continue after a Type 2 error. Wierd things may happen in this case, though it has worked okay, so far. BRU - BRU command line builder. Source Language - "@" processor. Will run under - RSX-11M V3.2, RSX-11M+ V1.0 and V2.0 Should run under - RSX-11M V4.0 Function - Construct the required mount commands and BRU command line to do most of our BRU runs. Can be invoked interactively (@BRU), or with parameter passing (@BRU IN: OU: or @BRU OU:=IN:). Validates input and output devices, mounts all unmounted media foreign (under M+ only), and selects BRU switches depending on whether the input and output media are disk or tape, and whether mounted FILES-11 or foreign. All media mounted by this command file will be dismounted when it exits. Under and RSX-11M+ V1.0 only, media should be either mounted FILES-11 or unmounted; unmounted devices should not be set public. Under the other 3 operating systems, this doesn't matter. This command file will apply the /DEN switch for MF:, MM:, MS:, and MT: out- put, using the highest density avail- able. No density is assumed for input. This should be readily modifiable to meet individual site needs. This command file will also (under M+ V2.0 and M V4.0) compute initial and maximum index file sizes for disk-to- disk transfers between different-sized disks. In all tested cases, these ap- proximate the INI defaults. ********************DM0:[370,340]README.RSX;1******************** ********************DM0:[370,340]README.RSX;1******************** brian nelson computer services university of toledo 2801 west bancroft toledo, ohio 43606 (419) 537-2841 RSX Sig tape Spring 1983 TED is a text editor that has appeared on other SIG tapes in the past. This version is current and contains a number of improvements related to thruput and partial screen scrolling that are not in previous versions. An edit history can be found in the file MODS.TXT. It has in it both a line editor and a fast and useful full screen editor. The RSTS version is a sharable run time system called EDRT.RTS. The file TED.TSK is a RSX11 v4.0 version that is not linked to fcsres. The file TED.EXE is a version that I run on my VAX in compatibility mode. The file TEDPDT.SAV is a subset version for RT11 version 4 Please note that the files EDRT.RTS, TEDPDT.SAV and *.HLB are all binary files and if copied with FLX the /IM switch MUST be used for these files. Please note that the program is copyrighted and can not be sold or included in any package intended for sale or resale. ********************DM0:[370,340]README.1ST;1******************** ********************DM0:[370,340]README.1ST;1******************** please see MODS.TXT and WHYTED.RNO brian nelson computer services university of toledo 2801 west bancroft toledo, ohio 43606 (419) 537-2841 office number (419) 537-2902 computer room (419) 537-2511 main office ********************DM0:[370,350]README.1ST;1******************** ********************DM0:[370,350]README.1ST;1******************** **> README.1ST Additional SEMLUG submissions by George Cornelius Mayo Clinic 200 First Street SW Rochester, MN 55901 (507) 284-2109 This submission consist of a collection of TECO and CCL macros. The CCL macros run under CCL v6.0 or 7.0, but some may require slight changes for the most recent CCL version. Also included are some friendly routines for access to spawn, chain operations from Fortran. See MAYOECG.DOC for more information.