.COMMENT EDITED 3-OCT-71 /LPW .COMMENT EDIT # 0045 3 Dec 1981 15:26:38 VD0:[305,100]RNO.RNO;60 .COMMENT PREVIOUS EDIT 30 Nov 1981 11:20:26 DB0:[305,100]RNO.RNO;57 .EBB .COMMENT EDITED 26-DEC-73 TO REFLECT RSX OPERATION -- E. POLLACK .COMMENT EDITED 3-JUL-74 FOR FORMAT AND CLARIFICATION -- M. F. LEWIS .COMMENT EDITED 23-DEC-75 FOR VERSION M01 -- M. F. LEWIS .COMMENT EDITED 24-FEB-77 FOR RSTS/E -- MARTIN MINOW .COMMENT EDITED 15-NOV-77 FOR RSTS/E V06C -- SIMON SZETO .COMMENT EDITED 04-Jan-79 FOR ACCURACY AND ADDITIONS -- GARY B. STEBBINS .COMMENT EDITED 8-AUG-79 FOR VERSION M02 -- M. F. LEWIS .COMMENT EDITED 15-SEP-79 FOR LIBRARY RELEASE -- M. F. LEWIS .COMMENT EDITED 5-APR-80 FOR CARTS LUG MODIFICATIONS -- D. B. CURTIS .; RAY VAN TASSLE ADDED TABLE OF CONTENTS, DARK, ETC .; AND SOME UPDATES AND CORRECTIONS .comment 20 Nov 81 RVT /BT & /SC switches. TOC margin explanation .PAPER SIZE 60,80 .LEFT MARGIN 8 .RIGHT MARGIN 72 .FLAGS CAPITALIZE .FIGURE 5 .spacing 1 .center RUNOFF .skip 1 .center Revision Date: Dec 1981 .center Program Version: M02.2 .period .skip 1 .center Document Revision .center Nov 1981 .skip 5 NOTICE: THis document describes a program which the Digital Equipment Corporation has no committment to offer or support at this time. This document is, however, believed to be an accurate description of RUNOFF. .skip 1 This version of RUNOFF is supported by a working group within the Text Processing Special Interest Group. If you experience any difficulties, send a description of the problem, together with the .RNO input file and the .DOC output file, to: Text Processing Special Interest Group, c/o DECUS, One Iron Way, MR2-3/E55, Marlboro, MA 01752. Present plans call for support of RUNOFF in source form only. It is recommended that you keep a reference copy of the distributed sources so that corrections and modifications may be distributed with SLP command files. .chapter INTRODUCTION .title ########INTRODUCTION .left margin 8 .right margin 72 .skip RUNOFF#(RNO) is a PDP-11 program to facilitate the preparation of typed or printed manuscripts, such as memos, manuals, etc. The user prepares his material on any regular PDP-11 terminal, and writes it onto a file using an appropriate editor. The user includes not only textual material, but also case and formatting information. RUNOFF then takes the file and reproduces it onto the line printer, terminal or other file to produce a final copy or final file image. It performs the formatting and case shifting as directed, and will also perform line justification, page numbering and titling, etc., as desired. .skip The principal benefit of such a program is that files prepared for use with it may be easily edited and corrected. Small or large amounts of material may be added or deleted, and unchanged material need not be retyped. After a set of changes, the program may be operated to produce a new copy which is properly paged and formatted. Documentation may thus be updated as necessary without requiring extensive retyping. .chapter RSX/IAS OPERATING PROCEDURES .title ########RSX/IAS OPERATING PROCEDURES .index Operation .left margin 8 .right margin 72 .hl 1 ^initiating ^runoff RUNOFF can be initiated in several ways. The general formats for RSX-11 users are: .nofill .skip .indent +24 MCR>RNO _ .INDENT +24 MCR>RNO#Filespec .s .fill .hl 1 ^rno ^command ^string .index Command string System programs usually require a command string to specify such things as input files and various options. A standard command string has one of the following forms: .skip .nofill .indent +16 output-file=input-file .skip .indent +24 or .skip .indent +16 @command-file .skip .fill Both output-file and input-file are strings comprising a file specification. .skip The second form of command string (@command-file) is used to specify an indirect command file. In this case each record of the file is used as a command string before any commands following the indirect command are accepted. .skip The command string syntax is described more completely in the User's Guide for the relevant operating system. .hl 2 ^file ^specifications .index File Specifications An RSX-11 file specification has the following form: .nofill .skip .indent +16 Dev:[UIC]Filename.Typ;Ver .skip .fill In this specification Dev must be a legal device code. The default value is SY:, the system disk. UIC must be a valid User Identification Code. Filename is any 1- to 9-character alphanumeric string which specifies a file name. Typ is a 1- to 3-character alphanumeric file type. System programs default to an appropriate standard type so the typical user will not have to explicitly specify it. Finally, Ver is a number which is the version number of the file. This field also normally can be omitted since it defaults on input to the highest existing version number for the file and on output to the highest existing version number plus one. .skip Default file specifications (any part of which may be overridden): .skip .nofill .indent +16 Input:###SY:RUNOFF.RNO .skip .indent +16 Output:##SY:RUNOFF.DOC .skip .i +10 RNO File###means###RNO TI:=File .i +10 RNO =file##means###RNO File=file .fill .note Editing RUNOFF Output RUNOFF output files may not be edited normally with the standard RSX/IAS file editors. To edit RUNOFF output, the output file must first be processed by TECO with a command of the format: .b.nofill.i +8 *ERFilespec_$EWFilespec/-CR_$EX_$_$ or just TEC Filespec followed by EX$$ .en .page .hl 2 RNO Switches .index Switches A file specification may have one or more switches associated with it. A switch is an indicator, consisting of a slash and a two-character ASCII name, used to select program options. .bb Several switches control the .eb RNO program. These switches, described below, may be specified on either the input or output file specification. The defaults may be set by the system manager at Task Build time. .skip .left margin 16 .nofill /SP#####-- Spool the output file .index Spooling .s /UC#####-- Force ALL uppercase output .index Case .s /FF#####-- Force Form-feeds (instead of multi-LFS) /-