You should take the following steps before you begin to install your system: (NUMBERED) Decide on automatic or manual installation. Survey the general installation procedures. Study the contents of your software kit. Select the components you need in your working system. Plan the arrangement of components. Choose the software customizations you need to make. (Deciding on Automatic or Manual Installation\ins_ins_autman_sec)

If you are uncertain as to whether your hardware configuration supports automatic installation, see the (aut_book) for information. In general, if your hardware configuration supports automatic installation, you should install your software distribution using that method and return to (ins_ins_cuspat_sec) of this chapter.

If your hardware configuration supports automatic installation, install your distribution using that method. The remainder of this chapter provides information you might find useful however you install your software. You can, however, safely ignore the information in this manual that follows this chapter. (Surveying Installation Procedures)

Although the specific steps you must perform to install RT--11 depend on your configuration, all users must perform some general procedures.

First, you must bootstrap the distribution volume and preserve the volume (or volumes) by making backup copies. You then automatically or manually create the working system from chosen components (eliminating components you do not need) and install the bootstrap on the working system volume(s). At this point, you can make software customizations which do not require performing the system generation process. When you have customized the system, you should compress the working system volume or volumes and preserve them on backup volumes. Once you are satisfied with the working system you have created, you should test it to make sure that it works properly. (Studying Software Kit Contents\ins_ins_sofkit_sec)

Study (ins_ins_comp_tab) for a summary of the RT--11 components distributed in the kits, and refer to the (sum_book) for a thorough description of each utility. RT--11 is distributed on an RL02 disk, on RX01, RX02, and RX50 diskettes, and on reel and cartridge magtape. The organization of files on volumes depends on the distribution medium. (RT--11 Software Components\ins_ins_comp_tab) (2\20) (Type of Software\Description) ((Monitors\bold)\) (RT11AI.SYS\Automatic installation monitor) (RT11MT.SYS\Magtape monitor used only to build MDUP.xx for user-supplied (not distributed) device handler) (RT11SB.SYS\Unmapped single-job monitor) (RT11FB.SYS\Unmapped foreground/background monitor) (RT11XB.SYS\Mapped extended memory single-job monitor; not distributed -- must be built by SYSGEN from distributed answer file) (RT11XM.SYS\Mapped extended memory monitor) (RT11ZB.SYS\Fully-mapped extended memory single-job monitor;not distributed -- must be built by SYSGEN from distributed answer file) (RT11ZM.SYS\Fully-mapped extended memory monitor) ((Device Handlers\bold)\) (DL.SYS\RL11/RL01/RL02 handler for unmapped monitors) (DLX.SYS\RL11/RL01/RL02 handler for mapped monitors) (DM.SYS\RK611/RK06/RK07 handler for unmapped monitors) (DMX.SYS\RK611/RK06/RK07 handler for mapped monitors) (DU.SYS\MSCP device handler for unmapped monitors) (DUX.SYS\MSCP device handler for mapped monitors) (DW.SYS\Professional 300 series processor disk handler for unmapped monitors) (DWX.SYS\Professional 300 series processor disk handler for mapped monitors) (DX.SYS\RX11/RX01 single-density diskette handler for unmapped monitors) (DXX.SYS\RX11/RX01 single-density diskette handler for mapped monitors) (DY.SYS\RX211/RX02 handler for unmapped monitors) (DYX.SYS\RX211/RX02 handler for mapped monitors) (DZ.SYS\Professional 300 series diskette handler for unmapped monitors) (DZX.SYS\Professional 300 series diskette handler for mapped monitors) (LD.SYS\Logical disk subsetting handler for unmapped monitors) (LDX.SYS\Logical disk subsetting handler for mapped monitors) (LP.SYS\Parallel interface printer handler for unmapped monitors) (LPX.SYS\Parallel interface printer handler for mapped monitors) (LS.SYS\Serial interface printer handler for unmapped monitors) (LSX.SYS\Serial interface printer handler for mapped monitors) (MM.SYS\File-structured TJU16 handler for unmapped monitors) (MMX.SYS\File-structured TJU16 handler for mapped monitors) (MS.SYS\File-structured TS11 handler for unmapped monitors) (MSX.SYS\File-structured TS11 handler for mapped monitors) (MT.SYS\File-structured TM11 handler for unmapped monitors) (MTX.SYS\File-structured TM11 handler for mapped monitors) (MU.SYS\File-structured TMSCP handler for unmapped monitors) (MUX.SYS\File-structured TMSCP handler for mapped monitors) (NCX.SYS\Ethernet handler for Professional 300 series processors) (NL.SYS\Null handler for unmapped monitors) (NLX.SYS\Null handler for mapped monitors) (NQX.SYS\Ethernet handler for Q-Bus processors) (NUX.SYS\Ethernet handler for UNIBUS processors) (PI.SYS\Professional 300 series processor interface system support handler for unmapped monitors) (PIX.SYS\Professional 300 series processor interface system support handler for mapped monitors) (RK.SYS\RK11/RK05 handler for unmapped monitors) (RKX.SYS\RK11/RK05 handler for mapped monitors) (SP.SYS\Transparent print spooler handler for unmapped monitors) (SPX.SYS\Transparent print spooler handler for mapped monitors) (UBX.SYS\UNIBUS mapping register system support handler for mapped monitors) (VM.SYS\Virtual disk handler for unmapped monitors) (VMX.SYS\Virtual disk handler for mapped monitors) (XC.SYS\Professional 300 series processor communication port modem handler for unmapped monitors) (XCX.SYS\Professional 300 series processor communication port modem handler for mapped monitors) (XL.SYS\DL--11 communication port modem handler for unmapped monitors) (XLX.SYS\DL--11 communication port modem handler for mapped monitors) ((Other System Files\bold)\) (SL.SYS\Single-line editor pseudohandler for unmapped monitors) (SLMIN.SYS\Minimal single-line editor pseudohandler) (SLX.SYS\Single-line editor pseudohandler for mapped monitors) (SWAP.SYS\External monitor swap blocks) ((Utility Programs\bold)\) (BINCOM.SAV\Binary compare utility) (BUP.SAV\Backup utility) (CREF.SAV\Cross-reference utility) (DIR.SAV\Directory utility) (DUMP.SAV\File dump utility) (DUP.SAV\Disk utility) (EDIT.SAV\Text editor) (FILEX.SAV\Foreign file exchange utility) (FORMAT.SAV\Disk formatting utility) (GIDIS.SAV\Graphics utility for Professional 300 series processors) (HELP.SAV\Help utility) (IND.SAV\Indirect control file processor) (INDEX.SAV\On-line index utility) (INDEXX.SAV\Virtual memory on-line index utility) (KED.SAV\Keypad editor) (KEX.SAV\Virtual memory keypad editor) (LIBR.SAV\Librarian) (LINK.SAV\Linker) (MACRO.SAV\MACRO assembler) (MDUP.AI\Magtape bootstrap utility for TMSCP auto installation) (MDUP.MM\Magtape bootstrap utility for TJU16) (MDUP.MS\Magtape bootstrap utility for TS11) (MDUP.MT\Magtape bootstrap utility for TM11) (MDUP.MU\Magtape bootstrap utility for TMSCP) (MDUP.SAV\Magtape utility) (MONMRG.SAV\System generation monitor linking program) (MSCPCK.SAV\Q-bus revision level checking program for MSCP and TMSCP devices) (PAT.SAV\Patching utility for program object modules) (PIP.SAV\File transfer utility) (QUEMAN.SAV\User interface with QUEUE utility) (QUEUE.REL\Device queue utility) (RESORC.SAV\System resource display utility) (SETUP.SAV\VT100 and Professional 300 series processor terminal setup utility) (SIPP.SAV\Save image patch utility) (SLP.SAV\Source language patch utility) (SPOOL.REL\Transparent print spooler utility) (SPOOL.SAV\Virtual memory tranparent print spooler utility) (SRCCOM.SAV\Source compare utility) (TRANSF.SAV\RT--11 host file transfer program for VTCOM) (UCL.SAV\User command linkage executable image) (VTCOM.REL\Virtual terminal communication and file transfer utility) (VTCOM.SAV\Virtual version of VTCOM communication utility, for running under mapped monitors) ((Miscellaneous\bold)\) (BATCH.SAV\BATCH processor) (ERROUT.SAV\Error log display program) (INDEX.IDX\Index pointer file for INDEX utility) (INDEXA.IMG\First half of INDEX utility index file) (INDEXB.IMG\Second half of INDEX utility index file) (MSB.COM\MS type magtape distribution build file) (MTB.COM\MM/MT type magtape distribution build file) (MUB.COM\MU type magtape distribution build file) (RTFB.MAP\Distributed FB monitor link map) (RTSB.MAP\Distributed SB monitor link map) (RTXB.MAP\Distributed XB monitor link map) (RTXM.MAP\Distributed XM monitor link map) (RTZB.MAP\Distributed ZB monitor link map) (RTZM.MAP\Distributed ZM monitor link map) (STRTFB.COM\FB start-up command file) (STRTSB.COM\SB start-up command file) (STRTXB.COM\XB start-up command file) (STRTXM.COM\XM start-up command file) (STRTZB.COM\ZB start-up command file) (STRTZM.COM\ZM start-up command file) (V5USER.TXT\Distribution kit message text file) ((System Generation Files\bold)\) (SYSGEN.COM\SYSGEN command file) (SBFB.ANS\Answer file to build distributed unmapped monitors) (XB.ANS\Answer file to build distributed XB monitor) (XM.ANS\Answer file to build distributed XM monitor) (XMEL.ANS\Answer file to build distributed XM monitor with MSCP error logging support) (ZB.ANS\Answer file to build distributed ZB monitor) (ZM.ANS\Answer file to build distributed ZM monitor) ((Automatic Installation Files\bold)\) (IVP.MAC\Automatic installation verification source file) (STRTAI.COM\Start-up file for automatic installation) (TERMID.SAV\Console terminal identification program) (VERIFY.COM\Automatic installation verification command file) ((Debuggers\bold)\) (DBGSYM.SAV\DBG--11 symbol table utility) (ODT.OBJ\Debugging aid) (SDH.SYS\DBG--11 unmapped hardware I/O pseudohandler) (SDHX.SYS\DBG--11 mapped hardware I/O pseudohandler) (SDS.SYS\DBG--11 unmapped software I/O pseudohandler) (SDSX.SYS\DBG--11 mapped software I/O pseudohandler) (VDT.OBJ\Debugging aid for virtual and multiterminal jobs) ((Graphics Software\bold)\) (ALPH00.FNT\PRO GIDIS font table) ((Libraries and Subroutines\bold)\) (EDTL.MLB\Common monitor definitions) (SYSLIB.OBJ\System-callable subroutines) (SYSMAC.SML\System macro library) (SYSTEM.MLB\System-callable data structure macros) ((Bootstraps\bold)\) (MBOOT.BOT\Magtape primary bootstrap for TMSCP and 800 bits/in tape) (MBOT16.BOT\Magtape primary bootstrap for 1600 bits/in tape) (MSBOOT.BOT\Magtape secondary bootstrap) ((Demonstration Programs\bold)\) (DEMOB1.BAS\Demonstration source -- BASIC--PLUS program) (DEMOBG.MAC\Demonstration source -- SB/FB macro program) (DEMOFG.MAC\Demonstration source -- FB macro program) (DEMOF1.FOR\Demonstration source -- FORTRAN program) (DEMOF2.FOR\Demonstration source -- FORTRAN program) (DEMOF3.FOR\Demonstration source -- FORTRAN program) (DEMOKD.TXT\Keypad editor demonstration source) (DEMOM1.MAC\Debugging demonstration source) (\) ((Source Files\bold)\) (BA.MAC\BATCH handler source file for system generation) (BSTRAP.MAC\Bootstrap source file for system generation) (DL.MAC\RL01/02 handler source file for system generation) (DM.MAC\RK06/07 handler source file for system generation) (DU.MAC\MSCP device handler source file for system generation) (DW.MAC\Professional 300 series processor disk handler source file for system generation) (DX.MAC\RX01 handler source file for system generation) (DY.MAC\RX02 handler source file for system generation) (DZ.MAC\Professional 300 series processor diskette handler source file for system generation) (EDTG.MAC\Monitor edit log and global definition file for system generation) (EL.MAC\Error logger handler source file for system generation) (ELCOPY.MAC\Error log job source file for system generation) (ELINIT.MAC\Error log job source file for system generation) (ELTASK.MAC\Error log job source file for system generation) (ERROUT.OBJ\Error log job file for system generation) (ERRTXT.MAC\Error log job source file for system generation) (FB.MAC\FB conditional source file for system generation) (FSM.MAC\Magtape file support source file for system generation) (KMON.MAC\Keyboard monitor source file for system generation) (KMOVLY.MAC\Keyboard monitor overlay source file for system generation) (LD.MAC\Logical disk subsetting handler source file for system generation) (LP.MAC\Parallel interface printer handler source file for system generation) (LS.MAC\Serial interface printer handler source file for system generation) (MTTEMT.MAC\Multiterminal programmed request source file for system generation) (MTTINT.MAC\Multiterminal interrupt service source file for system generation) (NC.MAC\Ethernet port handler source file for system generation for Professional 300 series processors (DECNA controller)) (NI.MAC\Ethernet class handler source file for system generation) (NL.MAC\Null handler source file for system generation) (NQ.MAC\Ethernet port handler source code file for system generation for Q-bus processors (DEQNA and DELQA controllers)) (NU.MAC\Ethernet port handler source code file for system generation for UNIBUS processors (DEUNA and DELUA controllers)) (RK.MAC\RK05 handler source file for system generation) (RMON.MAC\Resident monitor source file for system generation) (SP.MAC\Transparent print spooler handler source file for system generation) (TJ.MAC\TJU16 handler source file for system generation) (TM.MAC\TM11 handler source file for system generation) (TRMTBL.MAC\Multiterminal table source file for system generation) (TS.MAC\TS11 handler source file for system generation) (TT.MAC\TT.SYS source file for system generation) (TU.MAC\TMSCP handler source file for system generation) (UM.MAC\MSCP (and TMSCP) handler source file for system generation) (USR.MAC\USR source file for system generation) (VM.MAC\VM.SYS source file for system generation) (XB.MAC\XB conditional file for system generation) (XC.MAC\Professional 300 series processor communication port modem handler source file for system generation) (XL.MAC\DL--11 communication port modem handler source file for system generation) (XM.MAC\XM conditional source file for system generation) (XMSUBS.MAC\Mapped monitor subroutines for system generation) (ZB.MAC\ZB conditional file for system generation) (ZM.MAC\ZM conditional file for system generation) ((Unsupported Software\bold)\) (CONFIG.SAV\Automatic system software configuration services program) (CONFIG.COM\Automatic system software configuration command file) (CONSOL.MAC\Change boot-time console terminal) (CUSTOM.TXT\Customization symbol location file) (DATIME.MAC\Date and time source file for system generation) (DATIME.SAV\Date and time utility) (NITEST.MAC\Ethernet test source file) (RTMON.REL\System activity monitor) (SPLIT.SAV\File split utility) (TRANSF.EXE\VAX/VMS host file transfer program for VTCOM) (TRANSF.TSK\RSX host file transfer program for VTCOM) (V5NOTE.TXT\RT--11 release notes addenda) (VBGEXE.SAV\Virtual RUN utility) (Selecting Components for Your Working System\ins_ins_selcom_sec)

How you select components for your working system is largely determined by whether you have a larger (disk) or a smaller (diskette) system device. (Components for Larger (Disk) System Devices)

If you have a disk system device, you can store all usable system files on one device and the single system device is your working system. Any of the disk devices contains enough storage capacity for all appropriate system files. RT--11 distributes a variety of system files and all are not needed on any one computer system. So, RT--11 provides a configuration program, CONFIG.COM, you can run to automatically delete all unneeded system files. Further, although certain system files could be used on your computer system, if you know you will not use them, you can manually delete them after running CONFIG. The CONFIG program is included in the automatic installation procedure. If you are installing your software distribution manually, after completing the installation, issue the following command and follow the prompts: (.)($@CONFIG (RET))

Then examine your directory: (.)(DIRECTORY/FULL SY: (RET))

If ample space remains unused on your system volume, you are done. You have created your working system.

If the remaining storage space on your system device is limited, use the information in (ins_ins_comp_tab) to determine which files can be deleted manually. Delete those files. You have then created your working system. (Components for Smaller (Diskette) System Devices)

If you have a diskette system device, you must be selective and perhaps only place system files for a particular application on each of several working systems; one for each application. To decide which components these should be, study the space limitations of your device, then consider the suggestions given for each software component (Sections (ins_ins_mon_sec\value) through (ins_ins_util_sec\value)).

Before selecting components, you should become familiar with your medium's space limitations. (See (ins_ins_siz_tab).) Establish how many blocks are occupied by the components residing on each volume and how much free space is available on the volume.

(Device Size\ins_ins_siz_tab) (3\20\12) (Device\Device Name\Size in Blocks) (RX01 Diskette\DX\486) (RX02 Diskette\DY\974) (RX50 Diskette\DU,DZ\786) (Virtual Memory\VM\Variable, depending on physical memory available)

Keep in mind the number of blocks components occupy when you select the components for your working system. Also, keep them in mind when you decide how to arrange these components on volumes. Remember that you may need space for data storage on your system volume and other volumes in the working system.

Although you will probably find it more efficient to select components for the working system before actually starting installation, you can also examine volume directories during the installation process to get the component size information. Once you have booted the system, begun the installation process, and backed up the distribution media, you can examine a backup volume's directory (or the directories of each backup volume if there are more than one). Use the DIRECTORY command to examine a directory. The following is a sample directory. 15-Mar-90 SWAP .SYS 28P 16-Jan-90 RT11XM.SYS 123P 16-Jan-90 VMX .SYS 3 14-Apr-89 PIX .SYS 68P 16-Jan-90 DWX .SYS 6P 16-Jan-90 DZX .SYS 4P 16-Jan-90 LSX .SYS 5P 16-Jan-90 SPX .SYS 11P 16-Jan-90 XCX .SYS 4P 16-Jan-90 LDX .SYS 11P 16-Jan-90 SLX .SYS 20P 16-Jan-90 DUP .SAV 52P 16-Jan-90 DIR .SAV 20P 16-Jan-90 PIP .SAV 30P 16-Jan-90 KEX .SAV 72P 16-Jan-90 VTCOM .SAV 24P 16-Jan-90 SPOOL .SAV 22P 16-Jan-90 DUMP .SAV 10P 16-Jan-90 SETUP .SAV 42P 16-Jan-90 RESORC.SAV 33P 16-Jan-90 UCL .SAV 16P 16-Jan-90 UCL .DAT 9 09-Jan-89 VBGEXE.SAV 16P 16-Jan-90 SRCCOM.SAV 26P 16-Jan-90 STARTX.COM 2 13-Feb-90 25 Files, 657 Blocks 634 Free blocks

You can also find the total free space on an initialized blank volume by obtaining a directory of the volume.

Once you have examined the software kit maps, read the following sections to help you make your selections. The following elements are described: (unNUMBERED) Monitor SWAP.SYS File System Device Handler Other Device Handlers Default System Library Help Package Printer Handlers MACRO--11 Assembler Queue Package Source Files Start-Up Command File Text Editors Utility Programs (Monitor\ins_ins_mon_sec)

In general, you need only one monitor on a working system. If you do need more than one monitor, build a different system volume for each monitor. When your system device is a large disk, you may have room for several monitors. (SWAP.SYS File)

You need the file SWAP.SYS on a system volume to serve as temporary storage for part of a program in memory when KMON, the USR, or both must swap over that program. When KMON or the USR are no longer needed, the system reads this external swap file back into main memory. The keyboard command, SET EXIT NOSWAP, precludes the necessity of using SWAP.SYS once you have bootstrapped the system. However, you must have the SWAP.SYS file on your distribution disk to bootstrap your system successfully. (System Device Handler)

You need a system device handler on each system volume. For example, if you build an FB system with RL02 as the system device, the file DL.SYS must be on the system disk. (Other Device Handlers)

In addition to the system device handler, you need the device handlers for the other peripheral devices in your configuration. You do not need handler files for any devices you do not have. (Default System Library)

To use the LINK utility program, you may need the file SYSLIB.OBJ, the default system library, which the RT--11 linker searches to resolve any undefined globals at the end of a linking operation.

Generally, SYSLIB for your application should contain the system subroutines (the file SYSLIB.OBJ found in the software kit), installation-specific libraries of application subroutines, and the FORTRAN OTS routines. If SYSLIB must contain application subroutines and language routines, you must customize it to include these routines. If you intend to link overlaid files, you need SYSLIB, because it contains the overlay handlers. See the (sum_book) for more information on LINK and overlays. (Help Package)

HELP.SAV consists of HELP.EXE and HELP.MLB (resulting file after the librarian, LIBR, processes HELP.TXT) merged into a ready-to-use utility. Unless you want to change the help text, HELP.SAV is the only file you need.

A customization patch describes how to tailor the help text to your specific needs. (Printer Handlers)

The software kit includes the printer handlers for a parallel interface, LP.SYS (or LPX.SYS), and a serial interface, LS.SYS (or LSX.SYS). If your hardware configuration includes a serial interface printer instead of a parallel interface printer, you should include only LS.SYS or LSX.SYS in your working system. Further, if you are going to use the serial interface printer, you should include the following command line in your start-up command file: ASSIGN LS LP

If your serial interface printer is installed at nonstandard vector and control status register (CSR) addresses, use the SET command to change the addresses. See the (SUG_BOOK) for all LS handler SET commands. (MACRO--11 Assembler)

To use the MACRO--11 assembler, you need the files MACRO.SAV and SYSMAC.SML (the system macro library) on the system volume. See the (INT_BOOK) and the (SUM_BOOK) for descriptions of the assembly process. If you are going to be assembling any system components, you should also have SYSTEM.MLB on your system device, as SYSTEM.MLB is a library of system data structures with the supported data structure names and elements. You should also have SYSTEM.MLB on your system device if you are going to call for any system data structures in your own programs. You will then be using the same label names as used by RT--11. (Printer Utilities)

RT--11 contains two utilities, QUEUE and SPOOL, that are used to send output to the printer. Both utilities can be used as foreground or system jobs.

QUEUE is perhaps more appropriate for use on a small system as it does not use a permanent intermediate file, but rather a small temporary work file. SPOOL is very useful on larger systems, as output can be directed in multiple streams. See the (SUM_BOOK) for a description of QUEUE and SPOOL. (Source Files)

Normally, you do not need any source files in your working system except demonstration sources. Otherwise, the source files (file type .MAC) are required only for the system generation process.

You need the DEMOBG.MAC and DEMOFG.MAC demonstration sources in the working system to perform the exercises in Chapters (ins_RX01_chap\value) through (ins_PRO_chap\value) of this manual and in the (INT_BOOK). Once you have finished those exercises, the demonstration source files are no longer useful and can be deleted from your working disk. (Start-Up Command File)

Each RT--11 monitor looks for a matching start-up command file (STRTxx.COM) whenever you bootstrap the system. If it finds one, the monitor executes the commands in the file (to print a message, assign devices, and so on). If a monitor does not find a start-up command file, it prints a message indicating that the start-up file has not been found. See the (INT_BOOK) for information on start-up command files. (Text Editors)

RT--11 gives you a choice of two text editors. The Keypad Editor (KED or KEX) is an easy-to-use, cursor-oriented editor that you can use only on a VT100-compatible video terminal. KEX is the virtual version of KED; they function identically. KED is the default editor for unmapped monitors, and KEX is the default editor for the mapped monitors. The EDIT command automatically calls the correct version of the keypad editor for the monitor you are using, assuming the editor resides on your system device.

The EDIT utility is a character-oriented text editor that you use with a hard-copy terminal.

Refer to the (INT_BOOK) for an introduction to the keypad editor and the (KED_book) for complete information. Refer to the (sug_book) for information on the EDIT utility. (Utility Programs\ins_ins_util_sec)

You do not need any system utility programs you do not intend to use, but remember that most of the keyboard monitor commands need certain system programs to work. For example, PIP, DUP, and DIR are necessary for most of the keyboard commands to function. Appendix A of the (SUG_BOOK) summarizes the keyboard monitor commands and lists the system utility programs that each command requires.

Refer to the (SUM_BOOK) for descriptions of the utility program functions. If your system device is a large disk, you will find it useful to have most of the utility programs on your working system device. On the other hand, if you have a small system device, you will not have room for all the utilities.

You must include PIP, DUP, and DIR, and you probably want at least the correct version of the keypad editor and the HELP utility on your system volume. The utilities you use less frequently can occupy a second volume, as described in (ins_ins_sep_util_sec). (Planning the Arrangement of Components for Smaller System Devices\ins_ins_small_sec)

If your system volume is one of the smaller devices, the following is especially important. Consider the following suggestions before you build a working system; they can help you create an efficient system: (unNUMBERED) Assign the default device to the data device. Create a separate utilities volume. Create several system volumes. Create volumes for use with (int_book).

More details on each of these suggestions follow. (Assigning the Default Device to the Data Device)

Once you have installed the system, you can assign the default device DK to the nonsystem device unit. Most temporary files, data files, and others default to the second unit, minimizing demand for system device capacity.

The command to assign the default device to a nonsystem device is as follows, where (dev) is the nonsystem device unit: (.)(ASSIGN dev: DK: (RET))

Include this command in your start-up command file to assign the default device to (dev) whenever you boot the system. The procedures in this manual assume DK has not been assigned and is also the system device unless indicated otherwise. (See the (int_book).) (Creating a Separate Utilities Volume\ins_ins_sep_util_sec)

Create a separate volume for the utility programs you expect to use infrequently. This technique provides you with a system volume containing all the components necessary to execute the majority of keyboard commands and perform common program preparation functions. When you need a seldom-used utility, you can insert the utilities volume in the nonsystem device unit and copy the utility temporarily to the system volume. The utility can be run from the system volume by using appropriate DCL commands. The DIR, PIP, and DUP utilities should always reside on the system volume.

If a utility contains no overlays, you can run the utility directly from the nonsystem device unit which reads the entire utility into memory. You can then reinsert the data volume in that device unit, keeping the utility in memory. An overlaid utility must be copied to the system volume before the data volume is reinserted. You can use the SIPP utility to determine if a utility (or any program) is overlaid. If SIPP asks for a segment number, the program is overlaid. For example, the following illustrates an overlaid (prog.SAV): (.)(RUN SIPP (RET)) (*)(prog.SAV (RET)) (Segment?)

To run a non-overlaid utility from the utilities volume, use the following commands, where (ddn) is the physical device name, and (aaaaaa) is the utility program's name. (.)(RUN ddn:aaaaaa (RET)) (*)

Then, issue the appropriate utility (not DCL) commands. When you are done with the utility, exit from the program: (*)( (CTRL/C)) (.)

It is easier to simply copy a utility to the system device unit and run it from there. Not only do you not need to be concerned if a utility is overlaid, but you can use the simpler DCL command language (assuming the utility supports DCL commands, and most do). Try to keep some unused space on the system volume for temporarily storing and running seldom-used utilities. (Creating Several System Volumes)

Create several system volumes, each devoted to a particular function. You can then change the system volume as normal job flow changes the functions you need. To change system volumes, wait for a logical stopping point in the job flow; do not arbitrarily remove the system volume in the middle of an operation. When you have reached a logical stopping point, exchange the system volumes and reboot the processor. The chapter in the (INT_BOOK) that describes using VM as the system device contains examples of several system volumes. (Creating Volumes for Use with (Introduction to RT--11))

To perform the exercises in (int_book), you need certain components on your working system. Because your system device is one of the small devices (RX01, RX02, or RX50), you need to build one working system for all exercises other than the programming part, and one working system for each programming chapter you intend to complete. (Working System for Nonprogramming Part)

For all exercises other than the programming part, place at least the following files on your working system: SWAP.SYS RT11FB.SYS xx.SYS (system device handler) LP.SYS or LS.SYS (if appropriate) PIP.SAV DUP.SAV DIR.SAV BUP.SAV KED.SAV SRCCOM.SAV RESORC.SAV DEMOF1.FOR DEMOF2.FOR (Working System for Programming Part)

The following files are required to build any working system: SWAP.SYS RT11FB.SYS (or a different monitor) xx.SYS (system device handler) DIR.SAV DUP.SAV PIP.SAV

The files required for each programming chapter are listed in the (Choosing a Programming Language) chapter. You will need the file, LIBR.SAV, to perform the exercises in (Constructing Library Files). Additionally, you should place on the system volume the appropriate printer handler (if you have a printer) and an editor (KED or KEX). The demonstration programs are placed on the nonsystem (DK) device volume. (Choosing Software Customizations\ins_ins_cuspat_sec)

In general, you use software customizations to modify an already supported feature. Also in general, you use the system generation procedure to add or remove support for a system feature.

Examine (ins_int_cuspat_tab) and read the following sections to determine what you need to do. Identify any non-system-generation customizations you need to make. You can perform the procedure for each selected customization during the installation process (Chapters (ins_rx01_chap\value) through (ins_pro_chap\value)). System generation is necessary only if you need a customization that cannot be achieved with one of the procedures described in the following sections. Refer to Appendix D in the (syg_book) for additional modifications that further customize specially generated monitors.

Use the SIPP utility to install software customizations. The (sum_book) contains information on the SIPP utility; however, each customization patch contains the complete procedure.

To customize your software: (NUMBERED) Determine which customization(s) you wish to make. Locate the symbol of the software component you wish to modify. The values of symbols for monitor customizations may be obtained from the link maps distributed with RT--11 as the files RTSB.MAP, RTFB.MAP, RTXB.MAP, RTXB.MAP, RTXM.MAP, RTZB.MAP, and RTZM.MAP. The values of symbols for utility customizations are in the file CUSTOM.TXT. Follow the instructions to modify the software component, substituting the actual address value of the symbol in place of the symbol in the update. In the software customizations reproduced in this manual, question marks (?) represent unknown characters. These characters vary according to the specific software component. All numeric input values are octal unless otherwise indicated. (Changing Characters That Indicate Insertion/Deletion)

You can modify SRCCOM to change the default characters that SRCCOM uses to indicate insertions and deletions on listings. Normally, when you use the DIFFERENCES/CHANGEBAR command or SRCCOM's /D option to compare two files, SRCCOM places vertical bars next to each line that has been added to the new file and bullets (lowercase alphabetic o) next to lines that have been deleted. You can modify SRCCOM to use characters other than the vertical bar and bullet characters,

In the following customization, (n) is the ASCII code for the character you want to use to indicate insertions, and (m) is the ASCII code for the character you want to use to indicate deletions. (.)(RUN SIPP (RET)) (*)(SRCCOM.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( 1000 (RET)) ( Base Offset Old New?) ( 000000 001000 ??????)( ;A (RET)) ( 000000 001000 (<)o>)( ;Am(RET)) ( 000000 001001 (<)>)( ;An (RET)) ( 000000 001002 (<)^C>)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing Default Output Device from Printer to Terminal)

If your configuration does not have a printer, you can cause monitor commands to default to the terminal (TT) instead of the line printer (LP). Since several monitor commands default the output device to LP, you should edit the start-up command file to cause all system references to the device LP: to use the terminal. To change the defaults of such commands (for example, DUMP and PRINT), you need to add an ASSIGN TT: LP: command to the start-up file. Then, every time you bootstrap the system, the reassignment of the default device takes place. (Changing the LD Handler Suffix Character)

Use the following customization patch to change the suffix character for the LD handler to anything other than X. (You can use the X suffix without performing a customization patch.) You must also use customization patch D.3, Changing the Handler File-Name Suffix, located in the (syg_book). The following customization makes known to the monitor bootstrap the suffix character you specified in that customization; you must specify the same suffix character in both.

In this customization, (monitor.SYS) is the name of the monitor file you want to modify, and ..BLDS is the value of that symbol from the monitor link map. The field (y) represents the suffix character you want to add to the LD handler name. (.)(RUN SIPP (RET)) (*)(monitor.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..BLDS (RET)) ( Base Offset Old New?) ( 000000 ..BLDS ??????)( ;Ay (RET)) ( 000000 ..BLDS+2 ??????)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing the Number of Directory Columns)

You can modify DIR to change the number of columns in the directory listing that prints when you use the DIRECTORY command. Normally, the directory contains two sets of three columns, with each set listing file names and types, file size in blocks, and date of creation. If you use the /FAST or /BRIEF option with DIRECTORY, DIR lists only file names and types in five columns. You can also use the /COLUMNS:n option to specify the number of columns in the directory listing. However, if you want to change the default number of columns in the directory listing, install the following change.

In the customization, (ffffff) is an octal number (in the range 1 to 11) for the number of directory columns to be displayed when you use the DIRECTORY/FAST command. The value (nnnnnn) is an octal number (in the range 1 to 11) for the number of columns to be displayed when you use the DIRECTORY command. (.)(RUN SIPP (RET)) (*)(DIR.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( 1000 (RET)) ( Base Offset Old New?) ( 000000 001000 ??????)( ffffff (RET)) ( 000000 001002 ??????)( nnnnnn (RET)) ( 000000 001004 ??????)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing the Default Order of Directory Listings)

You can change the default order in which entries are listed in a directory listing. The current default order is by position in the directory.

In the following customization, SWS is the value of that symbol from the CUSTOM.TXT file. The variable (nnnnnn) represents the address of SWS that SIPP returns in response to the search command. The variable (yyyyyy) represents the contents of nnnnnn+2. The variable (zzzzzz) requests the contents of SWS+2. The variable (xxx) represents one of the following default ordering options:

(single_spaced) (2\10) (DAT\Order by date (earliest to latest) ) (NAM\Alphabetical order by file name ) (POS\Order by position in directory (current default) ) (SIZ\Order by size (smallest to largest) ) (TYP\Alphabetical order by file type ) (.)(R SIPP (RET)) (*)(DIR.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( ;S (RET)) (Search for?)( SWS (RET)) (Start?)( (RET)) (End?)( (RET)) (Found at nnnnnn) (Offset?)( nnnnnn (RET)) ( Base Offset Old New?) ( 000000 nnnnnn SWS)( SWS+4 (RET)) ( 000000 nnnnnn+2 yyyyyy)( (CTRL/Z) (RET)) (Offset?)( SWS (RET)) ( Base Offset Old New?) ( 000000 SWS ??????)( ;Rxxx (RET)) ( 000000 SWS+2 zzzzzz)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Number of /Q Program Sections LINK Allows)

You can alter LINK to change the number of absolute base address p-sects (/Q p-sects) that LINK allows. Normally, the /Q option to LINK lets you specify the absolute base addresses of up to eight p-sects in your program. You need absolute base address p-sects to prepare programs in absolute loading format for use in read-only memory (ROM) storage. Refer to the (SUM_BOOK) for more information about absolute base address p-sects and about LINK in general.

The limit of eight such p-sects, however, is the default number, and you can change it by altering LINK. LINK uses the number of p-sects to set up the /Q buffer area and to establish how many times it should ask the question: Load section: address?

Note, however, that LINK allocates the buffer space even if you do not use the /Q option when you perform the link. LINK calculates the size of the buffer to be three times the contents of QSWNUM.

To change the number of /Q p-sects LINK allows, use SIPP to change LINK.SAV as follows. QSWNUM is the value of that symbol from the CUSTOM.TXT file. The number (nnn) must be in the range 1 to 177(8); it represents the number of p-sects you want. (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( QSWNUM (RET)) (Segment Base Offset Old New?) (000000 000000 QSWNUM ??????)( nnn (RET)) (000000 000000 QSWNUM+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Size of LINK's Library Module List)

You can modify LINK to change the default size of LINK's list of library modules. LINK creates a list of 252(8) modules to be included from libraries during the link operation. Because the size of each entry in this list is larger in RT--11 Version 5 than in previous versions, the list may not be large enough for your application. You can use the LINK /P option at link time to increase the size of this list. If you want to change the default size of the list (and avoid using the /P option), you can modify the linker. You can still override the new default at link time by using /P.

Note that if you increase the default size of the list, the maximum number of global symbols allowed in the link will be reduced. You must install this change if you use DIBOL. Make the default number of modules LINK holds 400(8) or greater.

In the following customization, LMLSIZ is the value of that symbol from the CUSTOM.TXT file, and (nnnnnn) is the number of modules the list should hold. (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( LMLSIZ (RET)) (Segment Base Offset Old New?) (000000 000000 LMLSIZ ??????)( nnnnnn (RET)) (000000 000000 LMLSIZ+2 ??????)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing the Size of the QUEUE Work File)

QUEUE, the device queue foreground program (or system job), uses a work file five blocks long. This work file allows you to queue approximately 127(10) files at once. If your application requires larger queues, you can modify QUEUE.REL to change the default size of the work file.

In the following customization, QSIZE and QCBLK are the value of those symbols from the CUSTOM.TXT file, and (nnn) is the default size of the work file in octal blocks. To compute the approximate size of the work file that would be required for the number of files you need queued at once, use the formula:

nnn = (max no. of file specs in queue at one time + 1)/32 + 1 (.)(RUN SIPP (RET)) (*)(QUEUE.REL/A (RET)) (Base?)( 0 (RET)) (Offset?)( QSIZE (RET)) ( Base Offset Old New?) ( 000000 QSIZE ??????)( nnn (RET)) ( 000000 QSIZE+2 ??????)( (CTRL/Z) (RET)) (Offset?)( QCBLK (RET)) ( Base Offset Old New?) ( 000000 QCBLK ??????)( (nnn-1) (RET)) ( 000000 QCBLK+2 ??????)( (nnn-1)*32 (RET)) ( 000000 QCBLK+4 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying EDIT for Terminals with Nonstandard ESCAPE Codes)

You can modify the editor to allow it to operate correctly on terminals with nonstandard ESCAPE codes. Certain older terminals generate 175(8) or 176(8), rather than the standard 33(8), when you type the ESCAPE or ALTMODE key. Because codes 175 and 176 represent legitimate characters on more modern terminals, EDIT does not recognize ESCAPE code as the command terminator in the older terminals.

If you have an older terminal, you can correct the problem by making the following change, so that you can use the ESCAPE code as documented in the EDIT chapter of the (sug_book). In the change, ALTMDE is the value of that symbol from the CUSTOM.TXT file, and (nnn) represents the octal code that your terminal generates when you type the ESCAPE key on it. (.)(RUN SIPP (RET)) (*)(EDIT.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( ALTMDE (RET)) ( Base Offset Old New?) ( 000000 ALTMDE ??????)( (RET)) ( Base Offset Old New?) ( 000000 ALTMDE ???)( nnn (RET)) ( 000000 ALTMDE+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

The character $ echoes on the terminal, regardless of the octal value used for the ESCAPE code. However, EDIT recognizes only the ESCAPE code you specify, not both. (Installing Other Devices)

You may need to install device handlers that are available but are not installed in the standard monitors. Installing a device handler adds information to the monitor device tables, so that you can use the device. Many devices are available in the standard monitors. (Refer to the (sug_book) for a list of available devices.) You can perform the system generation process to create monitors and handlers that support nonstandard devices. The (DEV_book) describes how to write your own device handler.

When you bootstrap RT--11: (unnumbered) The bootstrap routine locates the system device handler and installs it. Then the bootstrap looks at the rest of the device handler files on the system device and tries to install the device handler for each device it finds in the configuration. It does not try to install any handlers for which there is no hardware. If there are more handlers than device slots, the bootstrap uses a certain priority scheme to establish which handlers to install.

Refer to the (sim_book) for a description of these priorities.

The SHOW command lists all installed device handlers and specifies when any empty device slots are available. (.)(SHOW (RET)) DU (Resident) DU0 = SY , DK LD DX SL UB LS NL 14 free slots

If the bootstrap did not install a device when you booted the system, it did not have enough device slots when it encountered the handler, the hardware was not present, or the device handler was not present. To install a device, ensure that the correct handler is on the system device and that the hardware is present. If there are no free slots, use the REMOVE command to remove an unneeded device and the INSTALL command to install the device you need. (.)(REMOVE LS: (RET)) (.)(INSTALL LP: (RET))

The standard (distributed) monitors provide a total of 16(10) device slots. If your application requires more than 16 device slots simultaneously, you must perform a system generation to create your own monitor and device handlers.

To control which handlers the bootstrap installs, place on the system device for your working system only the handlers for the devices you will be using. Do not include the handler for a device you will not be using.

You can keep a handler from being installed at boot time by giving it a name that does not correspond to the naming conventions for the monitor being booted. A device handler is named (yy.SYS) for unmapped monitors and (yyX.SYS) for mapped monitors (where (yy) is the device name). Use the RENAME command to rename a handler.

The bootstrap cannot install support for some devices. Thus, different procedures are required. The following sections describe how you can change the control status register (CSR) and vector addresses for the parallel and serial interface printers, RX01 and RX02 diskettes, and MSCP disks, and how you can install hardware magtape support, and set magtape parity and density. (CSR and Vector Addresses for Printers, RX01/02 Diskettes and MSCP Disks)

With the SET command, you can change the CSR and vector addresses of five devices: parallel and serial interface printers, RX01 and RX02 diskettes, and MSCP disks. You need to change the addresses if the controller is installed at nonstandard addresses. When using the SET command, enter the following commands, where (dd) is the device mnemonic (LP, LS, DX, DY, or DU), (aaaaaa) is the CSR address, and (bbb) is the vector address. (.)(SET dd: CSR2=aaaaaa (RET)) (.)(SET dd: VEC2=bbb (RET)) (.)(SET dd: CSR=aaaaaa (RET)) (.)(SET dd: VECTOR=bbb (RET))

In addition, the following commands are valid for MSCP disks: (.)(SET DU: CSR3=aaaaaa (RET)) (.)(SET DU: VEC3=bbb (RET)) (.)(SET DU: CSR4=aaaaaa (RET)) (.)(SET DU: VEC4=bbb (RET))

Use the following command to assign RT--11 unit numbers to MSCP disks, where (n) is the RT--11 unit number and (x) is the MSCP unit number: (.)(SET DUn: UNIT=x (RET))

To partition MSCP disks, use the following command, where (n) is the RT--11 unit number and (x) is the partition number: (.)(SET DUn: PART=x (RET))

You can also assign unit numbers to the MSCP ports. To generate support for the following command, you must perform a system generation and respond to question 108 (How many ports are to be supported (1) ?) with 2, 3, or 4. The distributed monitors do not support this command. In the command, (n) is the RT--11 unit number and (x) is the port number: (.)(SET DUn: PORT=x (RET))

See the description of the SET command in the (sug_BOOK) and the (DEV_BOOK) for more information on partitioning MSCP disks and assigning ports.

These commands permanently alter the handler .SYS file. That is, the CSR and vector addresses you specify remain in effect even if the system is rebooted. If you want to change the addresses again, you can use the SET command again. (Hardware Magtape Support)

You can choose to install hardware magtape support, rather than use file-structured magtape support. File-structured handlers include hardware magtape handler features; however, hardware magtape handlers are smaller.

File-structured magtape handlers are distributed as part of the RT--11 operating system; hardware magtape handlers are not. If you want to use hardware magtape handlers, you must perform a system generation. System generation produces either file-structured or hardware magtape handlers, but not both at the same time.

The files MT.SYS, MTX.SYS, MM.SYS, MMX.SYS, MS.SYS, MSX.SYS, MU.SYS, and MUX.SYS are distributed file-structured handlers for TM11, TJU16, TS11, and TMSCP magtape devices. The files MTHD.SYS, MTHDX.SYS, MMHD.SYS, MMHDX.SYS, MSHD.SYS, MSHDX.SYS, MUHD.SYS, and MUHDX.SYS are the system-generated hardware magtape handlers for the same devices. There are two sets of handlers: one for unmapped monitors, the other for mapped monitors. The file-name suffix X indicates device support for mapped monitors. (page_break)

The two ways to install a hardware magtape handler in place of the file-structured handler are: (NUMBERED) Rename the distributed file-structured handler to save it, rename the corresponding hardware magtape handler to the original name of the file-structured handler, and reboot the system to let the bootstrap install the handler. Use the INSTALL and REMOVE commands: (UNNUMBERED) Make sure the hardware magtape handler for your monitor and device is on the system disk. Rename the distributed file-structured handler to save it. Remove the file-structured handler from the system volume. Rename the corresponding hardware magtape handler to the name of the distributed file-structured handler. Install the renamed hardware magtape handler.

For example, to install TS11 hardware support in place of TS11 file-structured support, first make sure that the correct (unmapped or mapped) version of the hardware magtape handler (MSHD.SYS or MSHDX.SYS) is on the system volume, and then do the following. In the example, the mapped version of the handler is used: (NUMBERED) Rename and remove the file-structured handler. (You must remove the old handler before you can install the new one.) (.)(RENAME MS.SYS MS.FIL (RET)) (.)(REMOVE MS: (RET)) (.) Rename and install the hardware magtape handler. (.)(RENAME MSHD.SYS MS.SYS (RET)) (.)(INSTALL MS: (RET)) (.)

The handler you have named MS.SYS will be installed in the device table when the system is bootstrapped.

(ins_magunmapp_har_tab) identifies hardware handlers that you must rename, if you are using an unmapped monitor. Make sure you save the distributed (file-structured) handler.

(File-Structured and Hardware Magtape Handlers for Unmapped Monitors\ins_magunmapp_har_tab) (Device\File-StructuredHandler\HardwareHandler\Renamed HardwareHandler Name) (4\6\14\10) (TM11\MT.SYS\MTHD.SYS\MT.SYS) (TJU16\MM.SYS\MMHD.SYS\MM.SYS) (TS11\MS.SYS\MSHD.SYS\MS.SYS) (TMSCP\MU.SYS\MUHD.SYS\MU.SYS) (page_break)

(ins_magmapp_har_tab) identifies hardware handlers that you must rename, if you are using a mapped monitor. Make sure you save the distributed (file-structured) handler.

(File-Structured and Hardware Magtape Handlers for Mapped Monitors\ins_magmapp_har_tab) (Device\File-StructuredHandler\HardwareHandler \Renamed HardwareHandler Name) (4\6\14\10) (TM11\MTX.SYS\MTHDX.SYS\MTX.SYS) (TJU16\MMX.SYS\MMHDX.SYS\MMX.SYS) (TS11\MSX.SYS\MSHDX.SYS\MSX.SYS) (TMSCP\MUX.SYS\MUHDX.SYS\MUX.SYS) (Magtape Parity and Density)

To operate TM11 or TJU16 magtape at parity or density settings different from standard support, you can use the monitor SET command as described in the (SUG_BOOK). The distributed monitors support seven- and nine-track TM11 and TJU16 magtape at 800 bits/in and odd parity. You cannot set the density of TS11 magtape, since it is 1600 bits/in odd parity only. (Modifying BATCH to Save Space)

BATCH support requires system generation. Once you have generated BATCH support, to minimize space demands on your system device, you can modify BATCH to access certain system programs on DK rather than on SY. These customizations allow you to store certain system programs on DK rather than on SY and let BATCH access them there.

You can make any or all of the customizations. Modify BATCH for the system programs you need to remove from the system device. Copy the programs for which you install changes to the device on which you want them to reside; then, delete them from the system device (SY). Finally, use the ASSIGN command to assign the logical name DK to the device to which you copied the system programs. Then, run BATCH as usual.

The following change to BATCH makes DK the default storage volume for one of the specified programs. In the patch, (nnnnnn) is the octal value for the symbol that corresponds to the program you want to affect. The values for the symbols can be found in the file CUSTOM.TXT on your distribution kit.

(single_spaced) (2\10) (Program\Symbol) (DIR\..RDIR) (MACRO\..RMAC) (FORTRAN\..RFOR) (LINK\..RLIN) (PIP\..RPIP) (BASIC\..RBAS) (.)(RUN SIPP (RET)) (*)(BATCH.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( nnnnnn (RET)) ( Base Offset Old New?) ( BASE nnnnnn ??????)( (\)(RET)) ( Base Offset Old New?) ( BASE nnnnnn ???)( 125 (RET)) ( BASE nnnnnn+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

Once you assign DK to a device other than SY, the new device becomes the default input and output storage device for most system programs. You may need to modify BATCH jobs to reference certain files on SY explicitly, since that is no longer the same device as DK. You can keep .BAT and .CTL files on SY by invoking BATCH as follows: (.)(RUN BATCH (RET)) (*)(SY:myjob=SY:myjob (RET)) (Modifying LINK to Change the Default SYSLIB Device)

You can modify the linker to make it look for the default system library (SYSLIB.OBJ) on the device you choose instead of on the system device (SY). This change may be useful if you have space problems on your system device, because you can then place SYSLIB on the device you have specified to LINK.

To change the device on which SYSLIB.OBJ resides, make the following change to LINK.SAV. In the customization, (dev) is the name of the device on which you want to place SYSLIB. (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( SYSLIB (RET)) (Segment Base Offset Old New?) (000000 000000 SYSLIB ?)( ;Rdev (RET)) (000000 000000 SYSLIB+2 ?)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying the Help Text)

To change the help text that prints when you use the HELP command, you must create your own help text file, process that file with LIBR, and copy the resulting library and the file HELP.EXE to the same volume.

The files HELP.TXT and HELP.EXE, which together make up the program HELP.SAV, are not provided on the distribution kit. Therefore, to change your HELP text, you must first recreate HELP.TXT and HELP.EXE from HELP.SAV using the unsupported utility SPLIT.

To recreate these files, type this command: (.)(SPLIT ddn:HELP.EXE,,ddn:HELP.TXT=ddn:HELP.SAV/B:..HLP1:..HLP2 (RET))

In the command, (ddn:) represents the device on which to create the files HELP.TXT and HELP.EXE, or the device on which HELP.SAV exists. The variables ..HLP1 and ..HLP2 represent the boundaries along which to split HELP.SAV. Refer to the file CUSTOM.TXT on your distribution kit for the values to substitute in the command line for ..HLP1 and ..HLP2.

HELP.SAV is the only file you need if you do not want to change the help text. However, if you do want to change the text that prints when you use the HELP command, you must perform the following procedure.

First, edit the file HELP.TXT in your working system. Make sure that this file (as well as the rest of the distribution) is safely backed up and the actual distribution media are stored away. Add any explanations your application requires and delete any explanations that do not apply to your application.

When you edit HELP.TXT, you must use a specific format, as follows: (NUMBERED) Give each topic in the file an alphabetic name. The name you give must be unique within the first six characters. Place each topic on a page, delimited by form feeds. (See the following example.) Place topics in alphabetical order in the file. Leave the dummy topic 999999 at the end of the file.

The following illustrates the format of a topic, properly formatted, on a page. ((FF)) (.)(MACRO(TAB)TOPICNAME (RET)(LF)) (TOPICNAME(TAB)ONE LINE DESCRIPTION OF THE TOPIC (RET)(LF)) ((RET)(LF)) ((SP)(SP)SUBTOPICNAME (RET)(LF)) (TEXT ABOUT THE SUBTOPIC (RET)(LF)) (MORE TEXT (ANY NUMBER OF LINES) (RET)(LF)) ((SP)(SP)(SP)SUBTOPICITEMNAME (RET)(LF)) (DESCRIPTION OF SUBTOPIC ITEM [USUALLY ONLY FOR (RET)(LF)) (THE SUBTOPIC 'OPTION'], ANY NUMBER OF LINES (RET)(LF)) ([ANOTHER SUBTOPIC, STARTING FROM THE BLANK LINE ABOVE]) (.)(ENDM (RET)(LF)) ((FF))

Now, create the help text library file by processing HELP.TXT with the librarian. Use the following command: (.)(LIBR/MACRO HELP.MLB HELP.TXT (RET)) (.)

You can leave HELP.MLB as a separate file or merge it with HELP.EXE.

To run HELP with a separate program and text library file or files, copy HELP.EXE to the system volume. When you copy HELP.EXE, name it HELP.SAV. (.)(COPY/CONCATENATE HELP.EXE,HELP.MLB HELP.SAV (RET)) (.)

Make sure that the file HELP.MLB that you create is also on the system volume. You can back up HELP.EXE and HELP.TXT on another volume and delete them from the system volume. Then, to invoke HELP, type: (.)(HELP (RET))

If you leave HELP.MLB separate, you can alter it more easily in the future. However, if HELP.MLB is a separate file, the program runs more slowly. This problem is significant on systems that use a small device (for example, diskette) as the system device.

Digital recommends that you merge the two files, since the program runs faster that way. Use the following command to merge the program and text library file or files. (.)(COPY/CONCATENATE HELP.EXE,HELP.MLB HELP.SAV (RET)) (.)

In this case too, you can back up HELP.EXE and HELP.TXT on another volume and delete them from the system volume. You can also delete the file HELP.MLB, since you can recreate it from the file HELP.TXT. (Preventing Fatal System Errors from Causing a Reset)

Normally, the monitor performs a hard reset when a fatal system error occurs. The reset stops I/O transfers, minimizing the possibility that the error will corrupt media. In some cases, the cause of software errors might still be in memory, and the reset preserves the data, making it possible to analyze the error.

However, in rare cases, the reset may prevent diagnosis of hardware errors. If you prefer to suppress the reset, you can install the following change in the monitor, although doing so increases the risk of corrupting media. Digital does not recommend using a monitor with this customization installed except for diagnostic purposes. Do not use such a monitor for normal operations.

In the customization, (monitr.SYS) is the name of the monitor file you want to modify, and FATAL is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( FATAL (RET)) ( Base Offset Old New?) ( 000000 FATAL ??????)( 240 (RET)) ( 000000 FATAL+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Running RT--11 in Less Memory Than Is Available)

If your application requires that RT--11 run in less memory than is available, you can make a customization that allows you to bootstrap the system to run in the lower 12K words or 8K words of a 16K word machine. The SB and FB monitors have bootstraps that allow the system to run in less memory than is available. (This cannot be done for mapped monitors, because the mapped monitors require 32K memory.) The distributed monitors automatically make use of all available memory, since most applications require that RT--11 do so. However, if your configuration includes a hardware switch register and your application requires less memory, you can make the following customization. In the customization, (monitr.SYS) is the name of the unmapped monitor file that you want to modify, and BHALT is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( BHALT (RET)) ( Base Offset Old New?) ( 000000 BHALT ??????)( 0 (RET)) ( 000000 BHALT+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If this is the hardware bootable monitor, you must write a new system bootstrap with the COPY/BOOT command after you install this change.

Once you make the change to your monitor, a halt occurs whenever you boot that monitor file. While the system is halted, set the switch register to one of the values from the following table and press the CONTINUE switch; the bootstrap operation then completes for the memory size you specify.

(single_spaced) (2\10) (Value\Size in Words) ( 40000\8K) ( 44000\9K) ( 50000\10K) ( 54000\11K) ( 60000\12K) ( 64000\13K) ( 70000\14K) ( 74000\15K) (100000\16K) (104000\17K) (110000\18K) (114000\19K) (120000\20K) (124000\21K) (130000\22K) (134000\23K) (140000\24K) (144000\25K) (150000\26K) (154000\27K)

If your configuration does not include a hardware switch register or if you always want the system to boot in a specified amount of memory without halting, you can make the following customization. In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, and (nnnnnn) is a value from the preceding table. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( BHALT (RET)) ( Base Offset Old New?) ( 000000 BHALT ??????)( 240 (RET)) ( 000000 BHALT ??????)( 12704 (RET)) ( 000000 BHALT ??????)( nnnnnn (RET)) ( 000000 BHALT ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If this is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. Once you change your monitor, the system will boot in the memory you specify whenever you boot the customized monitor file.

To run RT--11 in exactly 28K words, use the customization in Section 2.6.20. (Setting VTCOM Default Dial String)

Apply one of the following customizations to VTCOM.REL or VTCOM.SAV to set a default dial string for the DIAL command.

In the customization, the symbol ..DIAL represents the address of the first character in the dial string. You can find the correct value for the symbol ..DIAL in the file CUSTOM.TXT on your distribution kit. Replace the symbols (a, b,) and so on, with the ASCII characters that make up your dial string. Add a mandatory null byte (a zero) following the last character of your dial string. The dial string cannot be longer than 39 characters. The fortieth byte must be a null. (To modify VTCOM.REL:) (.)(R SIPP (RET)) (*)(VTCOM.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..DIAL (RET)) ( Base Offset Old New?) ( 000000 ..DIAL ??????)( ;Aa (RET)) ( 000000 ..DIAL+1 ???)( ;Ab (RET)) ( 000000 ..DIAL+2 ???)( ;Ac (RET)) ( . . . .) ( . . . .) ( . . . .) ( 000000 ..DIAL+47 ???)( 0 (RET)) ( 000000 ..DIAL+50 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (To modify VTCOM.SAV:) (.)(R SIPP (RET)) (*)(VTCOM.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..DIAL (RET)) (Segment Base Offset Old New?) (000001 000000 ..DIAL ??????)( ;Aa (RET)) (000001 000000 ..DIAL+1 ???)( ;Ab (RET)) ( . . . . .) ( . . . . .) ( . . . . .) (000001 000000 ..DIAL+47 ???)( 0 (RET)) (000001 000000 ..DIAL+50 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Setting Upper Limit on a File Size)

If your application requires an upper limit on the size of a file, you can install a customization that changes the maximum size RT--11 allocates in a general .ENTER request. On distributed monitors, the .ENTER programmed request allocates space in such a way that the maximum size of a file is either half the largest space available or the entire second largest space available, whichever is larger. For most applications, this scheme is satisfactory and should be left unchanged. However, if yours is an application that requires an upper limit, you should make the following change.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, $RMON is the value of that symbol from the monitor link map, and (nnnnnn) is the octal number of blocks that is to be the maximum file size for a general .ENTER. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( $RMON (RET)) (Offset?)( 314 (RET)) ( Base Offset Old New?) ( $RMON 000314 ??????)( nnnnnn (RET)) ( $RMON 000316 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Number of Bad Blocks That BUP Accepts)

By default, BUP successfully handles up to 25 bad blocks on the input device when backing up a disk to a tape or when restoring from a tape to a disk (copy back). If any bad blocks are encountered on the output device, BUP issues a fatal error message and stops the backup operation.

BUP issues a warning message each time it encounters a bad block on the input device, then continues to back up or restore. If BUP encounters more than 25 bad blocks on the input device, BUP issues a fatal error message and the operation is stopped.

Use the following customization to set your own value for the number of bad blocks on the input device that BUP will accept.

In the customization, ..MBAD is the symbol for the value found in the file CUSTOM.TXT, and (nnnnn) is the new value that you enter. The maximum value you can enter is 77777(8); that is, you can customize BUP to read 77777(8) bad blocks on the input device before the next bad block encountered causes a fatal error. The value you enter is also the number of verification mismatches that BUP reads on the input device before the subsequent mismatch causes a fatal error. (.)(RUN SIPP (RET)) (*)(BUP.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MBAD (RET)) ( Base Offset Old New?) ( 000000 ..MBAD ??)( nnnnn (RET)) ( 000000 ..MBAD+2 ????)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing the Default File Type Extension of IND Control Files)

As distributed, the file type extension for IND control files is .COM. You can change that extension to distinguish IND control files from KMON command files (which also use the extension .COM).

In the customization, ..INDF is the symbol for a value located in the file CUSTOM.TXT, and (nnn) is the new default RAD50 3-character file type extension. (.)(RUN SIPP (RET)) (*)(IND.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..INDF (RET)) (Segment Base Offset Old New?) (000000 000000 ..INDF ??????)( ;R (RET)) (000000 000000 ..INDF ??????)( ;Rnnn (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Setting Upper Limit on Memory Size)

If your PDP--11 does not generate a bus timeout trap when the running program accesses location 160000, the RT--11 bootstrap may assume that you have an LSI--11 with the MSV11--DD memory option. The bootstrap assumes that there are 30K words available for the operating system. If this is not the case, RT--11 will not load into memory properly. However, if you install the following customization in your monitor, the bootstrap will never look for more than 28K words of memory. You cannot install this customization in a mapped monitor.

In the customization, (monitr.SYS) is the name of the monitor file you want to modify (SB or FB), and ..28KW is the symbol for the value found in the monitor link map on your software distribution kit. (.)(RUN SIPP (RET)) (*)(monitr.SYS/A (RET)) (Base?)( (RET)) (Offset?)( ..28KW (RET)) ( Base Offset Old New?) ( 000000 ..28KW ??????)( 160000 (RET)) ( 000000 ..28KW+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If the monitor you modify is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. (Suppressing the Bootstrap Message)

You can modify a monitor to prevent the monitor identification message from printing when you bootstrap that monitor. In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, and ..SLNT is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..SLNT (RET)) ( Base Offset Old New?) ( 000000 ..SLNT ??????)( 1 (RET)) ( 000000 ..SLNT+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If the monitor you modify is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. (Suppressing the Start-Up Indirect Command File)

You can suppress the monitor from calling a start-up command file when you bootstrap that monitor. The standard monitors include start-up command file support although you need not select it if you perform the system generation process to create special monitors. In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, and ..NIND is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..NIND (RET)) ( Base Offset Old New?) ( 000000 ..NIND ??????)( 0 (RET)) ( 000000 ..NIND+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If the monitor you modify is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. (Suppressing the Start-Up Indirect Command File Echo)

You can modify a monitor to execute the start-up indirect command file when you bootstrap a monitor but not echo (display) the command lines in the file. This customization causes the monitor to use the SET TT QUIET mode of operation. In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, and ..TTQU is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..TTQU (RET)) ( Base Offset Old New?) ( 000000 ..TTQU ??????)( 1 (RET)) ( 000000 ..TTQU+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If the monitor you modify is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. (Changing the Bootstrap Message)

You can modify a monitor to change the monitor identification message that appears when you bootstrap that monitor. Place the string (the message) in the monitor image starting at location BSTRNG. End the string with a null byte. The string must not be more than 20(10) bytes long, including the null byte. If the monitor you modify is the hardware bootable monitor, write a new system bootstrap with the COPY/BOOT command. (Changing the Default Device for Indirect Command Files)

You can change the default device for indirect command files. Normally, when you invoke an indirect command file (by typing $@filnam), the default device where the monitor looks for the command file is DK. If you have a special application, you can change this default to any three-character device name.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..ATDK is the value of that symbol from the monitor link map, and (nnn) is the new default device name. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..ATDK (RET)) ( Base Offset Old New?) ( 000000 ..ATDK ??????)( ;R (RET)) ( 000000 ..ATDK )( ;Rnnn (RET)) ( 000000 ..ATDK+2 ?????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default File Type for Indirect Command Files)

You can change the default file type for indirect command files. Normally, indirect command files have the default file type .COM. When you invoke an indirect command file (by typing $@filnam), the monitor looks for the file (filnam).COM. If you have a special application, you can change this default to any three-character file type.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..ATFX is the value of that symbol from the monitor link map, and (nnn) is the new default file type. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..ATFX (RET)) ( Base Offset Old New?) ( 000000 ..ATFX ??????)( ;R (RET)) ( 000000 ..ATFX (<)COM>)( ;Rnnn (RET)) ( 000000 ..ATFX+2 )( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default Device for the FRUN Command)

You can change the default device for the FRUN command. Normally, when you start a foreground program (by typing FRUN filnam), the default device where the monitor looks for the program file is DK:. If you have a special application, you can change this default device to any three-character device name.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..FRDK is the value of that symbol from the monitor link map, and (nnn) is the new default device name. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..FRDK (RET)) ( Base Offset Old New?) ( 000000 ..FRDK ??????)( ;R (RET)) ( 000000 ..FRDK (<)DK >)( ;Rnnn (RET)) ( 000000 ..FRDK+2 (<)???>)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default File Type for the FRUN Command)

You can change the default file type for foreground programs from .REL (the default) to any three-character file type.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..FRUX is the value of that symbol from the monitor link map, and (nnn) is the new default file type. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..FRUX (RET)) ( Base Offset Old New?) ( 000000 ..FRUX ??????)( R (RET)) ( 000000 ..FRUX (<)REL>)( ;Rnnn (RET)) ( 000000 ..FRUX+2 ?????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default Device for the EDIT Utility Command)

The customization changes the default device for the EDIT hard-copy editor only; it does not change the default device for the KED or KEX keypad editors. Further, as EDIT.SAV is not the default editor under any monitor, you must include the command SET EDIT EDIT in your start-up command file or perform the customization patch in Section 2.6.30 before this patch has effect.

Assuming you have made EDIT the default editor, if you then want to change the default device for the EDIT command, you can modify the monitor. Normally, when you invoke an editor by typing the EDIT command, the default device where the monitor looks for EDIT.SAV is SY. If you have a special application, you can change this default device to any three-character device name.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..EDDV is the value of that symbol from the monitor link map, and (nnn) is the new default device name. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..EDDV (RET)) ( Base Offset Old New?) ( 000000 ..EDDV ??????)( ;R (RET)) ( 000000 ..EDDV (<)SY >)( ;Rnnn (RET)) ( 000000 ..EDDV+2 ?????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default File Name for the EDIT Command)

You can change the default editor that is run when you type the EDIT command.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, PROGDF is the value of that symbol from the monitor link map, and EEE is 200(8) plus the new byte value of one of the following symbols from the monitor link map:

(single_spaced) (2\10) ($$EDIT\Command value for default editor EDIT) ($$KED\Command value for default editor KED) ($$KEX\Command value for default editor KEX) (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( PROGDF (RET)) ( Base Offset Old New?) ( 000000 PROGDF ??????)( (\) (RET)) ( Base Offset Old New?) ( 000000 PROGDF ???)( EEE (RET)) ( 000000 PROGDF+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Using Examine and Deposit Above the Background Job)

If you want to be able to examine and modify the monitor and the I/O page, you can modify the monitor to remove a restriction on the use of the E (Examine) and the D (Deposit) keyboard commands. Normally, the monitor allows you to examine and modify only locations inside the background job's area. You can remove this restriction, but you must be extremely careful when modifying the monitor or I/O page, since you may inadvertently destroy the resident monitor or corrupt a device.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, and ..EMON is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..EMON (RET)) ( Base Offset Old New?) ( 000000 ..EMON ??????)( 240 (RET)) ( 000000 ..EMON+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default Device for QUEMAN)

You can change the default device for the queue manager (QUEMAN). Normally, when you use the PRINT or DELETE/ENTRY command (in an FB or XM system with QUEUE running as a foreground or system job), QUEMAN sends the file to the device LP or deletes the entry from the LP queue. If you frequently queue to another device (such as the serial interface printer, LS), you can change the default device for these commands.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..QULP is the value of that symbol from the monitor link map, and (dv) is the two-character device name that you want as the default. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..QULP (RET)) ( Base Offset Old New?) ( 000000 ..QULP ??????)( ;A (RET)) ( 000000 ..QULP (<)L>)( ;Ad (RET)) ( 000000 ..QULP+1 (

))( ;Av (RET)) ( 000000 ..QULP+2 (<):>)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Indirect Command File Nesting Depth)

You can increase the indirect command file nesting depth. Normally, RT--11 allows you to nest indirect files to a depth of three. A nesting depth of three allows your indirect file to invoke another indirect file, which invokes still another indirect file. If you have a special application that requires more nesting, you can change the maximum nesting depth by modifying the monitor. Note that if you increase the nesting depth, any use of the indirect file feature will use more memory than is usual.

In the customization, (monitr.SYS) is the name of the monitor file that you want to modify, $RMON is the value of that symbol from the monitor link map, and (nnn) is the maximum indirect file nesting depth that you want; (nnn) should be a small integer, and must not be zero. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( $RMON (RET)) (Offset?)( 377 (RET)) ( Base Offset Old New?) ( $RMON 000377 ???)( nnn (RET)) ( $RMON 000400 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Threshold for Resuming Output-Stalled Jobs)

You can improve system throughput by changing the threshold for resuming output-stalled jobs. In an RT--11 system, a job is placed in a stalled state whenever it has terminal output to print but there is no room in its terminal output ring buffer. The system restarts the job when room becomes available in that ring buffer. The system's default mode of operation is to restart the job as soon as a single character of space is available. If more than one job is running, this mode of operation can cause the system to spend much time swapping in the context of a job, simply to have it output a single character and then stall again.

You can patch the monitor so that a job that is stalled while waiting for room in the terminal output buffer does not resume execution until several characters are available in the ring buffer. If you have a foreground or system job that produces a large amount of terminal output, installing this change can greatly improve system throughput.

In the following customization, (monitr.SYS) is the name of the monitor file that you want to modify, ..TTON is the value of that symbol from the monitor link map, and (nnn) is the threshold value for resuming a terminal output-stalled job.

The monitor will resume such a job when there are nnn-1 characters left to print in the output ring. The default value, 50(8), is the size of the ring; consequently, the monitor resumes a job when 47(8) characters are left to print (that is, when only one character position is available in the output ring). You can specify any value from 1 to the size of the output ring buffer (which is normally octal 50). Note that a value of 1 will cause the job to stay stalled until its ring buffer is empty. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..TTON (RET)) ( Base Offset Old New?) ( 000000 ..TTON ??????)( nnn (RET)) ( 000000 ..TTON+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default Number of Directory Segments)

You can change the number of directory segments DUP creates when you initialize a volume. Normally, DUP uses the default number of directory segments, which depends on the size of the volume. (Refer to the (sum_book).) In other words, when you use the INITIALIZE command to initialize a volume, DUP ascertains the size of the volume and checks a table (within DUP) to establish the number of directory segments to use. This table consists of two-word entries that give a size and the number of segments. DUP searches the table until it finds a size larger than or equal to the size of the volume being initialized and uses the value in the following word as the number of directory segments.

If the default number of directory segments for a volume is unacceptable for your application, you can use the /SEGMENTS:n option with INITIALIZE to initialize a volume with n directory segments. (Refer to the (sug_book).) However, if you want DUP to use a specific number, you can modify DUP to change DUP's directory segment table (duplicated in the following). .WORD 1000 ;Volumes with (<)= 512. blocks .WORD 1 ;get 1 segment directories .WORD 4000 ;Volumes with (<)= 2048. blocks .WORD 4 ;get 4 segment directories .WORD 30000 ;Volumes with (<)= 12288. blocks .WORD 20 ;get 16. segments .WORD 177777 ;Volumes with (<)= 65535. blocks .WORD 37 ;get 31. segments .BLKW 10. ;Expansion space for finer variations .WORD 0 ;Must be 0.

In the customization, (nnnnnn) is an octal offset value from the table below. The value (mmmmmm) is an octal number (in the range 1 to 37) for the number of directory segments you want as the default. Find the size of the volume for which you are changing the default number of directory segments in the table. Enter the corresponding offset value in (nnnnnn). Then, enter the number of default directory segments you want in (mmmm).

(2\24) (Size of Volume in Blocks (decimal)\Offset Value (octal)) ((<)=512\000002) ((<)=2048\000006) ((<)=12288\000012) ((<)=65535\000016) (.)(R SIPP (RET)) (*)(DUP.SAV (RET)) (Segment?)( 10 (RET)) (Base?)( SEGTBL (RET)) (Offset?)( nnnnnn (RET)) (Segment Base Offset Old New?) (000010 SEGTBL nnnnnn )( mmmmmm (RET)) (000010 SEGTBL nnnnnn+2 )( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Banner Page Width)

You can modify QUEUE to change the width of the banner page on printer output from 132 positions to 80 positions.

In the customization, ..NB1, ..NB2, and ..NB3 are the values of those symbols from the link map. (.)(RUN SIPP (RET)) (*)(QUEUE.REL/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..NB1 (RET)) ( Base Offset Old New?) ( 000000 ..NB1 ???)( (\) (RET)) ( Base Offset Old New?) ( 000000 ..NB1 ???)( 15 (RET)) ( 000000 ..NB1+1 ???)( 12 (RET)) ( 000000 ..NB1+2 ???)( 0 (RET)) ( 000000 ..NB1+3 ???)( (CTRL/Z) (RET)) (Offset?)( ..NB2 (RET)) ( Base Offset Old New?) ( 000000 ..NB2 ???)( (\) (RET)) ( Base Offset Old New?) ( 000000 ..NB2 ???)( 15 (RET)) ( 000000 ..NB2+1 ???)( 12 (RET)) ( 000000 ..NB2+2 ???)( (CTRL/Z) (RET)) (Offset?)( ..NB3 (RET)) ( Base Offset Old New?) ( 000000 ..NB3 ??????)( 240 (RET)) ( 000000 ..NB2+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying Listing Page Length in LINK)

If you do not use printer paper of a standard size (10.5 inches long) or if your configuration does not include a printer, you can modify the listing page length in LINK. RT--11 LINK sets the number of lines printed on each listing page at 60. This line count is generally satisfactory only for applications with printers that use paper 10.5 inches long. You may require a listing of a different length. In the customization, LINPPG is the value of that symbol in the link map, and (nnn) is the desired listing page length (in lines). (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( LINPPG (RET)) (Segment Base Offset Old New?) (000000 000000 LINPPG ?)( nnn (RET)) (000000 000000 LINPPG+2 ?)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Assigning the HELP File)

You can assign your HELP file to a file and/or device other than SY:HELP.SAV.

In the customization, (monitr.SYS) is the name of the monitor file that you wish to modify, and ..HELF is the value of that symbol from the monitor link map. The RAD50 file specification starts at ..HELF. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..HELF (RET)) ( Base Offset Old New?) ( 000000 ..HELF ??????)( ;R (RET)) ( 000000 ..HELF (<)SY >)( ;Rdev (RET)) ( 000000 ..HELF+2 (<)HEL>)( ;Rfil (RET)) ( 000000 ..HELF+4 (<)P >)( ;Rnam (RET)) ( 000000 ..HELF+6 (<)SAV>)( ;Rext (RET)) ( 000000 ..HELF+10 (<)???>)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Device from Which IND.SAV Is Run)

By default, the system runs IND.SAV from SY when KMON is set to IND and you type @filnam. To change the device from which the IND.SAV file is run, change the contents of ..INDN to the RAD50 device name of the device from which IND will be run. For example, to run IND from the virtual device (VM), open the ..INDN location in the link map and change its contents to VM.

In the customization, (monitr.SYS) is the name of the monitor file that you wish to modify, and ..INDN is the value of that symbol from the monitor link map. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( ..INDN (RET)) ( Base Offset Old New?) ( 000000 ..INDN ??????)( ;R (RET)) ( 000000 ..INDN (<)SY >)( ;Rdev (RET)) ( 000000 ..INDN+2 (<)IND>)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Supporting Bad Block Replacement in User-Written Handlers)

If a user-written handler supports bad block replacement, you must apply one of the following customizations. If all bad blocks are replaceable (such as the RL01/02), apply customization A. If only bad sector errors are replaceable (such as the RK06/07), apply customization B. (Customization A) (.)(R SIPP (RET)) (*)(DUP.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ARDPS (RET)) (Segment Base Offset Old New?) (000001 000030 ARDPS ???)( 377 (RET)) (000001 000030 ARDPS+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Customization B) (.)(R SIPP (RET)) (*)(DUP.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( SRDPS (RET)) (Segment Base Offset Old New?) (000001 000000 SRDPS ??????)( (\) (RET)) (Segment Base Offset Old New?) (000001 000000 SRDPS ???)( 377 (RET)) (000001 000000 SRDPS+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Supporting User-Written Magtape Handlers)

If a user-written magtape handler is used, you must apply the following three customizations. All three customizations assume that the device code for the device is 377(8). (Customization 1) (.)(R SIPP (RET)) (*)(DUP.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( MTDPS (RET)) (Segment Base Offset Old New?) (000001 000000 MTDPS ??????)( (\) (RET)) (Segment Base Offset Old New?) (000001 000000 MTDPS ???)( 377 (RET)) (000001 000000 MTDPS+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Customization 2) (.)(R SIPP (RET)) (*)(PIP.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( PIPMT (RET)) (Segment Base Offset Old New?) (000001 000000 PIPMT ???)( (\) (RET)) (Segment Base Offset Old New?) (000001 000000 PIPMT ???)( 377 (RET)) (000001 000000 PIPMT+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Customization 3) (.)(R SIPP (RET)) (*)(MDUP.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( MDUPMT (RET)) ( Base Offset Old New?) ( 000000 MDUPMT ???)( (\) (RET)) ( Base Offset Old New?) ( 000000 MDUPMT ???)( 377 (RET)) ( 000000 MDUPMT+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Eliminating or Changing the IND Control File Terminating Message)

You can eliminate or change the terminating message of IND control files, using the following customization patch.

The terminating message in the distributed IND is '@ (<)EOF>'. That message appears whenever IND exits and returns control. You can eliminate that message by specifying only a null character or change that message by specifying up to 7 characters plus the null character.

In the customization, ..INEO is the symbol for a value located in the file CUSTOM.TXT, and each (n) is an ASCII character in the new message. The required null character is an octal 0. (.)(RUN SIPP (RET)) (*)(IND.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..INEO (RET)) (Segment Base Offset Old New?) (000000 000000 ..INEO ??????)( ;A (RET)) (000000 000000 ..INEO <@>)( ;An (RET)) (000000 000000 ..INEO+1 < >)( ;An (RET)) (000000 000000 ..INEO+2 <<>)( ;An (RET)) (000000 000000 ..INEO+3 (<)E>)( ;An (RET)) (000000 000000 ..INEO+4 (<)O>)( ;An (RET)) (000000 000000 ..INEO+5 (<)F>)( ;An (RET)) (000000 000000 ..INEO+6 <>>)( ;An (RET)) (000000 000000 ..INEO+7 ???)( ;O (RET)) (Segment Base Offset Old New?) (000000 000000 ..INEO+6 ??????)( (\) (RET)) (Segment Base Offset Old New?) (000000 000000 ..INEO+6 ???)( (RET)) (000000 000000 ..INEO+7 ???)( 0 (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Changing Default File Type of Logical Disk Files)

By default, the file type of logical disk files is .DSK. You can alter the default file type in one of two ways. (Note that the same procedures also apply to LDX.SYS for the XM monitor.) (Customization 1)

Edit the conditional file SYSGEN.CND and add the following line where (typ) is the desired default file type: DEF$LD = ^Rtyp ; define default for LD filetype

Then, reassemble and relink LD.SYS by using the conditional file SYSGEN.CND. (Customization 2)

Do the following customization patch: (.)(UNPROTECT SY:LD.SYS (RET)) (.)(R SIPP (RET)) (*)(SY:LD.SYS/A (RET)) (Base?)( ..LDEX (RET)) (Offset?)( 0 (RET)) ( Base Offset Old New?) ( 000000 ..LDEX ??????)( ;R (RET)) ( 000000 ..LDEX (<)DSK>)( ;Rtyp (RET)) ( 000000 ..LDEX+2 (<)DSK>)( ;Rtyp (RET)) ( 000000 ..LDEX+4 (<)DSK>)( ;Rtyp (RET)) ( 000000 ..LDEX+6 (<)DSK>)( ;Rtyp (RET)) ( 000000 ..LDEX+10 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing QUEUE to Allow First Form Feed)

QUEUE suppresses the first form feed in a file, because QUEUE assumes that the LP or LS handler is set to FORM0, which generates a form feed. If the printer handler is set to NOFORM0, no form feed is generated.

You can apply the following customization so that QUEUE will never suppress the initial form feed in a file. If you apply this customization and set your printer handler to FORM0, an extra blank page will be produced.

In the customization, ..DOFF is the value of that symbol from the file CUSTOM.TXT on your distribution kit. (.)(RUN SIPP (RET)) (*)(QUEUE.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..DOFF (RET)) ( Base Offset Old New?) ( 000000 ..DOFF ??????)( 240 (RET)) ( 000000 ..DOFF+2 ??????)( 240 (RET)) ( 000000 ..DOFF+4 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Listing Page Length in MACRO and CREF)

The default listing page size for MACRO and CREF, 60 lines long, is suitable for printers that use standard size printer paper (10.5 inches long). If you use printer paper that is not standard size, or if your configuration does not include a printer, you may need to modify the listing page length in MACRO and CREF. In the customizations, (nnn) represents the desired listing page length (octal). Substitute for the symbol PGSIZE the value of that symbol given in the file CUSTOM.TXT on your distribution kit. (To modify MACRO:) (.)(RUN SIPP (RET)) (*)(MACRO.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( PGSIZE (RET)) (Segment Base Offset Old New?) (000000 000000 PGSIZE ??????)( nnn (RET)) (000000 000000 PGSIZE+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (To modify CREF:) (.)(RUN SIPP (RET)) (*)(CREF.SAV (RET)) (Base?)( 0 (RET)) (Offset?)( PGSIZE (RET)) ( Base Offset Old New?) ( 000000 PGSIZE ??????)( nnn (RET)) ( 000000 PGSIZE+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Default Command File Processor to IND)

In the distributed monitors, the default command file processor is KMON. Apply the following customization to change the default command file processor to IND. After you have applied this customization, you may use an IND control file as your start-up command file, providing the file IND.SAV resides on your system volume.

In the customization, (monitr.SYS) is the monitor file you want to modify, and ..INDR is the value of that symbol from the appropriate monitor link map. If the monitor you customize is hardware bootable, write a new system bootstrap with the COPY/BOOT command. (.)(RUN SIPP (RET)) (*)(monitr.sys (RET)) (Base?)( 0 (RET)) (Offset?)( ..INDR (RET)) ( Base Offset Old New?) ( 000000 ..INDR ??????)( 1 (RET)) ( 000000 ..INDR+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If you do not wish to apply this customization, you can set the default command file processor to IND by setting the conditional IND$ON to 1 in the conditional file. (Limiting Amount of Memory KEX Requests)

KEX, by default, requests all available 16-bit memory up to 32K words. This customization allows you to limit the amount of memory KEX requests with a .SETTOP programmed request.

In the customization, the symbol ..MAXM represents the highest address KEX will request. (In the distributed monitors, this value is set to 177776, the highest address possible.) If you set this value too low, KEX will fail and print the error message (?KEX-F-Insufficient memory). You can find the correct value for the symbol ..MAXM in the file CUSTOM.TXT on your distribution kit. Replace the symbol (nnnnnn) with the new maximum address value you want KEX to request. (.)(R SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( (RET)) (Base?)( (RET)) (Offset?)( ..MAXM (RET)) ( Base Offset Old New?) ( 000000 ..MAXM ??????)( ;nnnnnn (RET)) ( 000000 ..MAXM+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing MACRO's Default .LIST/.NLIST Options)

MACRO--11 is distributed with the following .NLIST defaults:

.NLIST LD,ME,MEB,TTM

You may change the .NLIST defaults to any of the following, where the following bit significance applies (bit asserted implies ".NLIST"):

(single_spaced) (2\6) (BEX =\ 2) (BIN =\ 4) (CND =\ 10) (COM =\ 20) (HEX =\ 40) (LOC =\ 100) (MC =\ 200) (MD =\ 400) (ME =\ 1000) (MEB =\ 2000) (SEQ =\ 4000) (SRC =\ 10000) (SYM =\ 20000) (TOC =\ 40000) (TTM =\ 100000) (.)(RUN SIPP (RET)) (*)(MACRO.SAV (RET)) (Segment?)( (RET)) (Base?)( 0 (RET)) (Offset?)( LCBITS (RET)) ( Base Offset Old New?) ( 000000 LCBITS ??????)( nnnnnn (RET)) ( 000000 LCBITS+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing MACRO's Default .ENABLE/.DISABLE Options)

MACRO--11 is distributed with the following .DSABL defaults:

.DSABL ABS,AMA,CDR,DBG,FPT,LCM,LSB,MCL

You may change the .DSABL defaults to any of the following, where the following bit significance applies (bit asserted implies ".DSABL"):

(single_spaced) (2\6) (ABS =\ 1) (AMA =\ 2) (CDR =\ 10) (CRF =\ 20) (DBG =\ 40) (FPT =\ 100) (GBL =\ 200) (LC =\ 400) (LCM =\ 1000) (LSB =\ 2000) (MCL =\ 4000) (PNC =\ 10000) (REG =\ 20000) (.)(RUN SIPP (RET)) (*)(MACRO.SAV (RET)) (Segment?)( (RET)) (Base?)( 0 (RET)) (Offset?)( EDBITS (RET)) ( Base Offset Old New?) ( 000000 EDBITS ??????)( nnnnnn (RET)) ( 000000 EDBITS+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying KED Default File Type)

KED supports default file types. When editing a file, the default input file type is .MAC; the default output file type is the same as the input file type. When inspecting a file, the default input file type is .LST. There is no default input file type when creating a file.

To specify a file with no file type, type only the file name and the period separating the file name and type (FILNAM.).

You can modify the default file types with the following software customization. In the customization, substitute KED or KEX for (aaa). Substitute the value for the symbol ..EEXT (for the editing-file default) or ..IEXT (for the inspecting-file default) for (bbbbbb). These values can be found in CUSTOM.TXT on your distribution kit (be sure to use the proper KED variant). Substitute the three-character file type default you want for (ccc). (.)(R SIPP (RET)) (*)(aaa.SAV/A (RET)) (Base?)( 0 (RET)) (Offset?)( bbbbbb (RET)) ( Base Offset Old New?) ( 000000 bbbbbb ??????)( ;R (RET)) ( 000000 bbbbbb (<)???>)( ;Rccc (RET)) ( 000000 bbbbbb (<)???>)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing SPOOL's Work File Size)

SPOOL allocates by default 1024(10) blocks on logical device SFD or SY for its work file SPOOL.SYS. You can change the default size of SPOOL.SYS by applying the following software customization. In the customization, ..SPSZ is the offset for the current number of blocks SPOOL allocates for its work file. Substitute for ..SPSZ the value provided in the file CUSTOM.TXT. (nnnnnn) is the number (octal) of blocks you want SPOOL to allocate for its work file. (.)(RUN SIPP (RET)) (*)(SPOOL.REL/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..SPSZ (RET)) ( Base Offset Old New?) ( 000000 ..SPSZ ??????)( nnnnnn (RET)) ( 000000 ..SPSZ+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

If there is not enough room on the volume for a work file of the default size, SPOOL.SYS occupies the largest empty area on the volume. (Changing SPOOL's Output Device)

You can change SPOOL's default output device to any RT--11 non-file-structured device by installing the following software customization. In the customization, substitute for ..SPSO the value provided in the file CUSTOM.TXT. (nnn) is the new output device's mnemonic. (.)(RUN SIPP (RET)) (*)(SPOOL.REL/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..SPSO (RET)) ( Base Offset Old New?) ( 000000 ..SPSO ??????)( ;R (RET)) ( 000000 ..SPSO (<)LP>)( ;Rnnn (RET)) ( 000000 ..SPSO+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing LINK for Default 132-Column Link Map and Global Cross-Reference Table)

You can change the link map and global cross-reference table to default to 132 columns, rather than 80 columns. The value of ..WDSZ can be found in CUSTOM.TXT on your distribution kit. (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..WDSZ (RET)) (Segment Base Offset Old New?) (000001 000000 ..WDSZ ??????)( 000006 (RET)) (000001 000000 ..WDSZ+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Default Size of MACRO--11 Work File)

You can tailor the size of the MACRO--11 work file. If the work file is too small, a program that uses a great many symbols or macros can cause the work file to overflow and return the error message (?MACRO-F-Storage limit exceeded). A work file that is too large may not fit on a small device such as VM.

In the customization, (nnn) represents the size of the work file and can be a value between 128 and 256(10). WRKSIZ is the symbol for the value given in the file CUSTOM.TXT on your distribution kit. (.)(R SIPP (RET)) (*)(MACRO.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( WRKSIZ (RET)) (Segment Base Offset Old New?) (000000 000000 WRKSIZ ??????)( nnn (RET)) (000000 000000 WRKSIZ+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Name and Default Device for UCL.DAT)

You can change the name of the UCL data file. With this patch, you can also change the default device on which the UCL data file resides.

The file specification for the UCL data file is stored in four RAD50 words. The first word is the device name without the colon (:). You must leave a trailing space if you use a 2-letter device name. The second word is the first three letters of the file name. The third word is the second three letters of the file name (if required). The fourth word is the file type. Do not include the period (.) between the file name and file type.

In the customization patch, ..UCLD is the symbol for the first RAD50 word. Substitute for ..UCLD the value for that word found in the file CUSTOM.TXT on your distribution kit. Substitute for (nnn) each part of the file specification that you changed when you created a new UCL data file. (.)(R SIPP (RET)) (*)(UCL.SAV/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..UCLD (RET)) ( Base Offset Old New?) ( 0000 ..UCLD ??????)( ;R (RET)) ( 0000 ..UCLD ??????)( ;Rnnn (RET)) ( 0000 ..UCLD+2 ??????)( ;Rnnn (RET)) ( 0000 ..UCLD+4 ??????)( ;Rnnn (RET)) ( 0000 ..UCLD+6 ??????)( ;Rnnn (RET)) ( 0000 ..UCLD+10 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Suppressing Dynamic Allocation of a Region for IND)

IND dynamically allocates a region in extended memory for its symbol table when running RT--11 under a mapped monitor. You can suppress the dynamic allocation by using the following customization.

In the customization, ..ALRG is the symbol for the value given in the file CUSTOM.TXT on your distribution kit. Enter the value 0 (zero) for symbol (n) to suppress the dynamic allocation. Enter the value 1 for (n) to dynamically allocate a region. (.)(R SIPP (RET)) (*)(IND.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..ALRG (RET)) (Segment Base Offset Old New?) (000000 000000 ..ALRG ??????)( n (RET)) (000000 000000 ..ALRG+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Size of UCL.DAT)

You can change (increase or decrease) the maximum number of user-defined UCL commands in the UCL data file from 31(10) to a maximum you specify. Perform the following customization patch to change the size of UCL.DAT. (Refer to the (int_book) for more information on UCL.)

In the customization patch, replace the symbol ..CMDS with the value given in the file CUSTOM.TXT on your distribution kit. Replace (nnnnn) with an octal value for the maximum number of defined (UCL) commands you want. (.)(R SIPP (RET)) (*)(UCL.SAV/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..CMDS (RET)) ( Base Offset Old New?) ( 000000 ..CMDS ??)( nnnnn (RET)) ( 000000 ..CMDS+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing Default VTCOM Send Speed)

The VTCOM SEND command sends ASCII files at two speeds: SLOW or FAST. Use SLOW if the host terminal service does not support XON/XOFF and use FAST if it supports XON/XOFF. The default speed is SLOW.

The following customization patch lets you set the default speed at which VTCOM sends ASCII files. In the customization, ..FAST is the symbol for the value given in the file CUSTOM.TXT on your distribution kit. Set the value for (n) to 1 to specify FAST. (For VTCOM.REL:) (.)(R SIPP (RET)) (*)(VTCOM.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..FAST (RET)) ( Base Offset Old New?) ( 000000 ..FAST ??????)( n (RET)) ( 000000 ..FAST+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For VTCOM.SAV:) (.)(R SIPP (RET)) (*)(VTCOM.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..FAST (RET)) (Segment Base Offset Old New?) (000001 000000 ..FAST ??????)( n (RET)) (000001 000000 ..FAST+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying System Macro Library SYSMAC.SML)

To modify the system macro library, recreate the file SYSMAC.MAC from the distributed file SYSMAC.SML by using the SPLIT utility.

The following command creates the file SYSMAC.MAC on your default device. The symbol ..SYSM represents the boundary along which to split SYSMAC.SML. Refer to the file CUSTOM.TXT on your distribution kit for the value to substitute for ..SYSM in the command line. (.)(SPLIT ,SYSMAC.MAC=SYSMAC.SML/B:..SYSM (RET))

Refer to the (sum_book) for more information on using the SPLIT utility. (Modifying VTCOM Default Dial String Prefix)

The default VTCOM dial string prefix is ^A^B. Perform the following customization patch if your modem requires a different dial string prefix. Consult your modem user guide for the correct prefix.

VTCOM first sends the dial string prefix and then sends the dial string. This patch does not affect the dial string.

In the customization, ..DPFX is the symbol for the value given in the file CUSTOM.TXT on your distribution kit, and nnn is the octal value for each ASCII character in the dial string prefix. Insert a null (000) in the location immediately following the last character in the dial string prefix. The prefix cannot be longer than 15 characters. The sixteenth byte must be a null. (For VTCOM.REL:) (.)(R SIPP (RET)) (*)(VTCOM.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..DPFX (RET)) ( Base Offset Old New?) ( 000000 ..DPFX ???)( nnn (RET)) ( 000000 ..DPFX+1 ???)( nnn (RET)) ( . . .)( .) ( . . .)( .) ( . . .)( .) ( 000000 ..DPFX+16 ???)( nnn (RET)) ( 000000 ..DPFX+17 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For VTCOM.SAV:) (.)(R SIPP (RET)) (*)(VTCOM.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..DPFX (RET)) (Segment Base Offset Old New?) (000001 000000 ..DPFX ???)( nnn (RET)) (000001 000000 ..DPFX+1 ???)( nnn (RET)) ( . . . .)( .) ( . . . .)( .) ( . . . .)( .) (000001 000000 ..DPFX+16 ???)( nnn (RET)) (000001 000000 ..DPFX+17 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying VTCOM Default Dial String Suffix)

The default dial string suffix is an exclamation (!) mark (041). Some modems require a different dial string suffix following the digits of the number to be dialed. Refer to your modem user guide for any required dial string suffix. Perform the following customization patch if your modem requires a different dial string suffix.

In the customization, ..DSFX is the symbol for the value given in the file CUSTOM.TXT on your distribution kit, and (nnn) is the octal value for each ASCII character in the dial string suffix. Insert a null (000) in the location immediately following the last character in the dial string suffix. The suffix cannot be longer than 15 characters. The sixteenth byte must be a null. (For VTCOM.REL:) (.)(R SIPP (RET)) (*)(VTCOM.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..DSFX (RET)) ( Base Offset Old New?) ( 000000 ..DSFX ???)( nnn (RET)) ( 000000 ..DSFX+1 ???)( nnn (RET)) ( . . .)( .) ( . . .)( .) ( . . .)( .) ( 000000 ..DSFX+16 ???)( nnn (RET)) ( 000000 ..DSFX+17 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For VTCOM.SAV:) (.)(R SIPP (RET)) (*)(VTCOM.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..DSFX (RET)) (Segment Base Offset Old New?) (000001 000000 ..DSFX ???)( nnn (RET)) (000001 000000 ..DSFX+1 ???)( nnn (RET)) ( . . . .)( .) ( . . . .)( .) ( . . . .)( .) (000001 000000 ..DSFX+16 ???)( nnn (RET)) (000001 000000 ..DSFX+17 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Automatically Creating KED/KEX Journal Files)

The following customization patch automatically creates a journal file on the default data (DK) device for every work session.

In the customization, ..JOU is the symbol for a value located in the file CUSTOM.TXT. (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 6 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JOU (RET)) (Segment Base Offset Old New?) (000006 000000 ..JOU ??????)( 1 (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JOU (RET)) (Segment Base Offset Old New?) (000001 000000 ..JOU ??????)( 1 (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Adjusting Default KED/KEX Journal File Size Allocation)

By default, KED/KEX allocates 50(10) blocks on the default or specified device for journal files. You can adjust the default number of allocated blocks, using the following customization patch.

In the customization, ..JSIZ is the symbol for a value located in the file CUSTOM.TXT. The symbol (nnn) represents the number of octal blocks you want to allocate as the default journal file size (62 octal blocks equal 50 decimal blocks). (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JSIZ (RET)) (Segment Base Offset Old New?) (000000 000000 ..JSIZ ??????)( nnn (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JSIZ (RET)) (Segment Base Offset Old New?) (000001 000000 ..JSIZ ??????)( nnn (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Creating a Monitor-Independent ODT Debugger)

The following procedure lets you create a monitor-independent ODT debugger; that is, an ODT that does not require that the operating system be loaded in memory.

The distributed debugger ODT.OBJ needs the operating system loaded in memory. You can modify ODT so it does not need the operating system loaded in memory, which could be useful, for example, in debugging the bootstrap.

Use the following procedure to create a debugger called ODTHWD.OBJ that functions independently of the operating system: (numbered) Use KED to create the following patch program. Name it ODTPAT.MAC. In the program, substitute for the symbol ..GVAL the value for that symbol located in the file CUSTOM.TXT. .TITLE ODT .PSECT $ODT$ BASE=..GVAL-1000 .=.+BASE BR .+34 .END Assemble the created patch program: (.)(R MACRO (RET)) (*)(ODTPAT=ODTPAT (RET)) (*)((CTRL/C)) Create the monitor-independent debugger ODTHWD.OBJ by modifying ODT.OBJ, which does not destroy the distributed ODT.OBJ but modifies a copy of it. Use the utility PAT.SAV in the following manner: (.)(R PAT (RET)) (*)(ODTHWD=ODT,ODTPAT (RET)) (*)((CTRL/C)) Explicitly specify ODTHWD in the LINK/DEBUG command. If you do not specify ODTHWD, RT--11 by default links the distributed ODT. (.)(LINK/DEBUG:ODTHWD program (RET)) (Forcing an Explicit KED/KEX Journal File Device)

By default, KED/KEX creates a requested journal file on the DK device or a device you specify on the command line. You can force KED/KEX to create any requested journal file on a specified device, using the following customization patch. Note that if the customization is performed, KED/KEX creates a journal file on only the device specified in the customization; any device specified in the command line is ignored. Further, if the specified device cannot be found, a journal file is not created and KED/KEX returns an error message.

In the customization, ..JDEV is the symbol for a value located in the file CUSTOM.TXT. The symbol (rrr) represents the RAD50 value for the journal file device. (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JDEV (RET)) (Segment Base Offset Old New?) (000000 000000 ..JDEV ??????)( ;R (RET)) (000000 000000 ..JDEV ??????)( ;rrr (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..JDEV (RET)) (Segment Base Offset Old New?) (000001 000000 ..JDEV ??????)( ;R (RET)) (000001 000000 ..JDEV ??????)( ;rrr (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Modifying the Storage Capacity for LEARN Macros)

By default KED/KEX allocates 512(10) locations for storing LEARN macros. That storage area is shared by up to 8 macro definitions. You can modify that storage capacity by performing the following customization. Increasing the storage capacity decreases the amount of memory available for paste buffer space and general file editing. Therefore, ask only the amount of storage capacity you require.

In the customization, ..MACS is the symbol for a value located in the file CUSTOM.TXT. The symbol (nnnnnnn) is the octal number of storage locations you want to support. (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MACS (RET)) (Segment Base Offset Old New?) (000000 000000 ..MACS ??????)( nnnnnnn (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MACS (RET)) .b (Segment Base Offset Old New?) (000001 000000 ..MACS ??????)( nnnnnnn (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Modifying the Maximum Number of LEARN Macros)

By default KED/KEX allows 8(10) LEARN macros to be defined at any one time. You can modify that limit by performing the following customization.

In the customization, ..MACN is the symbol for a value located in the file CUSTOM.TXT. The symbol (nn) is the octal number of macros you want to define. The maximum is support for 27(10) macro definitions, for which you would specify 33(8). (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MACN (RET)) (Segment Base Offset Old New?) (000000 000000 ..MACN ??????)( nnn (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MACN (RET)) (Segment Base Offset Old New?) (000001 000000 ..MACN ??????)( nnn (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Restoring LOCAL Form Feed Processing)

The LOCAL command ignores the presence of form feeds in files that are being processed. If for some reason you wish to restore the previous way the LOCAL command treated form feeds in files, you can perform the following customization.

In the customization, ..LCFF is the symbol for a value located in the file CUSTOM.TXT. (For KED.SAV:) (.)(RUN SIPP (RET)) (*)(KED.SAV (RET)) (Segment?)( 0 (RET)) (Base?)( 0 (RET)) (Offset?)( ..LCFF (RET)) (Segment Base Offset Old New?) (000000 000000 ..LCCF ??????)( 000014 (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For KEX.SAV:) (.)(RUN SIPP (RET)) (*)(KEX.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..LCFF (RET)) (Segment Base Offset Old New?) (000000 000000 ..LCCF ??????)( 000014 (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Removing the JSW Bit 6 Check for SL)

Previously, SL checked only the state of bits 4 (EDIT$) and 12 (TTSPC$) in the JSW (job status word). SL refused to edit a command line if either was set. SL did not check if a program had set bit 6 (TCBIT$), the inhibit terminal wait bit. SL could hang in the rare event that a program had set bit 6 and not set bit 12 and was using the .TTINR request in a loop to clear the input buffer. (KED is such a program.)

SL checks the status of bits 4, 6, and 12 of the JSW. If a program sets any of those bits, SL does not edit command lines.

Possible incompatibilities remain with SL editing of command lines written and retrieved using requests other than .GTLIN. Digital continues to recommend you use .GTLIN to display prompts and retrieve terminal input.

If for some reason you require that SL ignore the status of bit 6 of the JSW, RT--11 provides the following customization patches to remove that functionality. Three patches are provided, one for each version of the SL command line editor. In the customization patches, _..SLCN, ..SLCX, and ..SLCM are the values for those symbols located in the file CUSTOM.TXT. (For SL.SYS:) (.)(RUN SIPP (RET)) (*)(SL.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..SLCN (RET)) ( Base Offset Old New?) ( 000000 ..SLCN ??????)( 010020 (RET)) ( 000000 ..SLCN+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For SLX.SYS:) (.)(RUN SIPP (RET)) (*)(SLX.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..SLCX (RET)) ( Base Offset Old New?) ( 000000 ..SLCX ??????)( 010020 (RET)) ( 000000 ..SLCX+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For SLMIN.SYS:) (.)(RUN SIPP (RET)) (*)(SLMIN.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..SLCM (RET)) ( Base Offset Old New?) ( 000000 ..SLCM ??????)( 010020 (RET)) ( 000000 ..SLCM+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing SL Character Edit Mode to REPLACE)

SL can edit single characters in two modes: INSERT mode and REPLACE mode. INSERT mode lets you place a character in the command line by shifting to the right all characters beyond that character. REPLACE mode lets you place a character in the command line without shifting any characters. SL is distributed in INSERT mode. You can alternate between INSERT and REPLACE mode by pressing CTRL/A. SL returns to INSERT mode at each command line.

Apply the following customization to change the default mode for single-character editing from INSERT to REPLACE. You can still continue to alternate between REPLACE and INSERT mode by pressing CTRL/A. SL returns to REPLACE mode at each command line.

Three patches are provided, one for each version of the SL command line editor. In the customization patches, _..IRDF, ..IRDX, and ..IRDM are the values for those symbols located in the file CUSTOM.TXT. (For SL.SYS:) (.)(RUN SIPP (RET)) (*)(SL.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..IRDF (RET)) ( Base Offset Old New?) ( 000000 ..IRDF ??????)( 000000 (RET)) ( 000000 ..IRDF+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For SLX.SYS:) (.)(RUN SIPP (RET)) (*)(SLX.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..IRDX (RET)) ( Base Offset Old New?) ( 000000 ..IRDX ??????)( 000000 (RET)) ( 000000 ..IRDX+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For SLMIN.SYS:) (.)(RUN SIPP (RET)) (*)(SLMIN.SYS/A (RET)) (Base?)( 0 (RET)) (Offset?)( ..IRDM (RET)) ( Base Offset Old New?) ( 000000 ..IRDM ??????)( 000000 (RET)) ( 000000 ..IRDM+2 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the VTCOM Command Mode Character)

You can change the character you type to VTCOM to enter command mode. The default command mode character for VTCOM is (CTRL/P). You can change the character CTRL/P to any you choose by using the following customization patch.

In the customization, ..LCCH is the symbol for a value located in the file CUSTOM.TXT, (nnn) is the octal value for the new default command mode character. That new character cannot be printable and cannot be a character that RT--11 intercepts and processes, such as (CTRL/F), (CTRL/B), (CTRL/X), (CTRL/O), and so on. (For VTCOM.REL:) (.)(R SIPP (RET)) (*)(VTCOM.REL (RET)) (Base?)( 0 (RET)) (Offset?)( ..LCCH (RET)) ( Base Offset Old New?) ( 000000 ..LCCH ??????)( (\) (RET)) ( Base Offset Old New?) ( 000000 ..LCCH ???)( nnn (RET)) ( 000000 ..LCCH+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (For VTCOM.SAV:) (.)(R SIPP (RET)) (*)(VTCOM.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..LCCH (RET)) (Segment Base Offset Old New?) (000001 000000 ..LCCH ??????)( (\) (RET)) (Segment Base Offset Old New?) (000001 000000 ..LCCH ???)( nnn (RET)) (000001 000000 ..LCCH+1 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Forcing Obsolete SJ Monitor Value in CONFIG Bit $FBMON)

Previously, a handler or program could check the state of the $FBMON bit in the CONFIG word (bit 0 in RMON fixed offset 300) to determine under which monitor it was running. In particular, $FBMON being clear indicated the SJ monitor. Further, some programs may have used the state of $FBMON to determine other monitor characteristics. The removal of the SJ monitor and the advent of new monitors have decoupled those characteristics with any particular distributed monitor, and $FBMON is set with all distributed monitors. All distributed RT--11 software is also decoupled from $FBMON.

This customization patch is provided because a user-written device handler or program might require $FBMON be clear as a condition for installation. In that case, the following procedure is recommended: (numbered) Perform the customization patch, which clears $FBMON in the file image, allowing the device handler to install once the customized monitor is booted. Reset $FBMON early in your start-up command file, using the command SET MODE NOSJ.

The SET command conditions SET MODE SJ and SET MODE NOSJ clear or set bit zero (the $FBMON bit) in CONFIG. Those SET commands affect only the memory resident monitor image. Therefore, $FBMON is clear at installation time but correctly set before the system is used.

Digital recommends you do not run RT--11 with $FBMON clear as that setting does not accurately describe any monitor distributed with the operating system.

In the customization, (monitr.sys) is the monitor you are running, and (CONFIG) is the address of that symbol in the monitor link map.

To clear $FBMON and thereby simulate the obsolete SJ monitor setting, clear the low bit in CONFIG. To set $FBMON (the distributed condition), set the low bit in CONFIG. (.)(RUN SIPP (RET)) (*)(monitr.SYS (RET)) (Base?)( 0 (RET)) (Offset?)( CONFIG (RET)) (Base Offset Old New?) (000000 CONFIG ??????)( (\) (RET)) (Base Offset Old New?) (000000 CONFIG ??? value with bit zero set or clear) ((RET)) (000000 CONFIG+1 ???)( (CTRL/Y) (RET)) (*)((CTRL/C)) (.) (Making LINK /G Option a Default)

The LINK /G option (increasing the directory buffer size) is available only from CSI command syntax; it is not available as a DCL option. The following customization patch enables the /G option whenever LINK is run by any command syntax. You should read the LINK /G option section in the (SUM_BOOK) before performing this patch as there are possible negative effects.

In the customization, ..GON is the symbol for a value located in the file CUSTOM.TXT. (.)(RUN SIPP (RET)) (*)(LINK.SAV (RET)) (Segment?)( 1 (RET)) (Base?)( 0 (RET)) (Offset?)( ..GON (RET)) (Segment Base Offset Old New?) (000001 000000 ..GON ??????)( 240 (RET)) (000001 000000 ..GON+2 ??????)( 240 (RET)) (000000 000000 ..GON+4 ??????)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.) (Changing the Default Magtape Label Size)

You can change the default magtape label size from 40(10) words to any value between 40(10) and 512(10). (The value is entered in the customization in octal radix.)

In the following customization, ..MTLS is the symbol for the value located in CUSTOM.TXT, and (nnnn) is the octal value for the default magtape label size you want. (.)(R SIPP (RET)) (*)(DUP.SAV (RET)) (Segment?)( 7 (RET)) (Base?)( 0 (RET)) (Offset?)( ..MTLS (RET)) (Segment Base Offset Old New?) (000007 000000 ..MTLS ???)( nnnn (RET)) (000001 000000 ..MTLS+2 ???)( (CTRL/Y) (RET)) (*)( (CTRL/C)) (.)

(Installation Worksheet\F2P2) (KEEP) (1)

(2\5) ()

(SELECTED COMPONENTS SIZE IN BLOCKS\BOLD) (Monitors\BOLD)

RT11MT.SYS RT11SB.SYS RT11FB.SYS RT11XB.SYS RT11XM.SYS RT11ZB.SYS RT11ZM.SYS

(System Device Handler\BOLD)

(Other Device Handlers\BOLD)

(KEEP) (5)

SWAP.SYS

(Utility Programs\BOLD)

BATCH.SAV BINCOM.SAV BUP.SAV CREF.SAV DIR.SAV DUMP.SAV DUP.SAV EDIT.SAV ERROUT.SAV FILEX.SAV FORMAT.SAV GIDIS.SAV and ALPH00.FNT HELP.SAV IND.SAV KED.SAV KEX.SAV K52.SAV LIBR.SAV LINK.SAV MDUP.MU MDUP.SAV PAT.SAV PIP.SAV QUEMAN.SAV QUEUE.REL RESORC.SAV SETUP.SAV SIPP.SAV SLP.SAV SPOOL.REL SRCCOM.SAV UCL.SAV VTCOM.REL VTCOM.SAV

(Help Files\BOLD)

HELP.SAV

(Libraries\BOLD)

SYSLIB.OBJ SYSMAC.SML

(Assemblers\BOLD)

MACRO

(Source Files\BOLD)

(KEEP) (5) (Other Files\BOLD)

(ARRANGEMENT\BOLD)

(System Volume\BOLD)

(KEEP) (7) (Volume 2\BOLD)

(KEEP) (5) (Volume 3\BOLD)

(KEEP) (5) (Volume 4\BOLD)

(KEEP) (5) (Volume 5\BOLD)

(KEEP) (6) (Customizations\BOLD)

(PAGE\BOLD) (PAGE\BOLD) (PAGE\BOLD) (PAGE\BOLD) (PAGE\BOLD)