Your first step in using RT--11 is to install it on your system. You can install RT--11 automatically or manually, depending on your configuration. (Manual and Automatic Installation)

You can install RT--11 automatically or manually. See the (aut_book) to determine if you can automatically install RT--11. If your hardware does not support automatic installation, you must install RT--11 manually. Manual installation requires: (unnumbered) Bootstrapping and preserving the distribution volumes. Creating the working system from selected components. Optionally customizing the working system. Preserving and testing the working system.

Usually, your system is ready to run once you have installed and tested it. However, if you need certain special features, such as multiterminal support, you must perform the system generation process. In this case, run the SYSGEN program, answer its questions, and assemble your own generated monitor(s) and device handlers. See the (syg_book) for information about generating specialized monitors.

The following sections help decide which course of action to take. Once you have established which steps you must complete, identify the chapters you need to read. You need not read this entire manual. (Identifying Your Needs)

To select the procedures you must perform and the reading path to follow, use the information in this chapter to answer the following questions: (UNNUMBERED) Can you automatically install your system? What is your hardware configuration? Which monitor(s) do you need? Which features do you need? (Can You Automatically Install Your System?)

Look at the (aut_book) to determine if you can install RT--11 automatically. If possible, you should install RT--11 automatically unless you have a good reason for doing a manual installation. The automatic installation procedure is simple and it configures and tests your system automatically.

If, according to the (aut_book), your system is supported for automatic installation, go now to that manual for directions. After automatically installing and configuring your system, return to this chapter for more installation information.

If, according to the (aut_book), your system is not supported for automatic installation, continue reading this chapter and follow the appropriate reading path as defined in (ins_readpath_tab). (What Is Your Hardware Configuration?)

Your hardware configuration is an important consideration for three reasons: (unNUMBERED) Installation procedures vary according to the hardware configuration. System generation cannot be performed on all hardware configurations. System generation procedures vary according to the hardware configuration.

Chapters (ins_rx01_chap\value) through (ins_pro_chap\value) contain detailed procedures for manually installing RT--11 systems on certain common hardware configurations. Unless you have an unusual configuration, read only the chapter intended for your configuration. See (ins_readpath_tab) to identify your reading path. (Which Monitor(s) Do You Need?)

You have to decide which monitor or monitors you need to know what steps to follow in getting started. Your distribution kit includes the unmapped SB and FB monitors and the mapped XB, XM, ZB, and ZM monitors.

Sections (ins_int_unmap_sec\value) and (ins_int_map_sec\value) describe the RT--11 monitors. More monitor information is located in the (int_book). (Unmapped (SB and FB) Monitors\ins_int_unmap_sec)

The unmapped monitors (SB and FB) are appropriate for processors that contain only kernel (64K bytes) memory. The SB monitor supports one job while the FB monitor supports a foreground and a background job.

The SB monitor is the smallest RT--11 monitor. Use the SB monitor if your processor contains only 64K bytes of memory and your application is too large to run under the FB monitor.

Use the FB monitor if your processor contains only 64K bytes of memory and your application will run in the available address space. The FB monitor allows you to execute an independent foreground job at a higher software priority level than the background, while you use the remaining system facilities to support the background. The RT--11 foreground job is not intended for a two-user time-sharing system. Rather, it best supports a stable, event-driven real-time or I/O application that can execute with a minimum of user interaction while the bulk of the system's business is conducted in the background.

The background in the foreground/background environment appears just like the SB monitor; all the facilities available to you as an SB user are available to you as an FB user in the background. (Mapped (XB, XM, ZB, ZM) Monitors\ins_int_map_sec)

The mapped monitors are for processors that contain extended or mapped memory. (MMD) lists the basic characteristics. For more information on mapped monitors, see the Software Product Description (SPD) and the (int_book). (Mapped Monitor Description\MMD) (2\8) (Monitor\Characteristics) (XB\Single job. Does not support I & D (instruction and data) address space separation or Supervisor Mode) (XM\Multiple jobs. Supports up to 8 concurrent jobs. Does not support I & D address space separation or Supervisor Mode) (ZB\Single job. Supports I & D address space separation and Supervisor Mode) (ZM\Multiple jobs. Supports up to 8 concurrent jobs, I & D address space separation and Supervisor Mode) (Which Features Do You Need?)

The characteristics of distributed software (monitors, utilities, and device handlers), are described in the Software Product Description (SPD), which is included with your documentation kit. You can change some characteristics of distributed software by using the customization patches listed in (ins_int_cuspat_tab) and described in (ins_ins_chap). If the distributed or customized software does not provide a feature you need, you must perform a system generation as described in the (syg_book). (Is Installation All You Need to Do?)

Decide whether installing the distributed software is all you need to do or whether you will also need to perform the system generation process. (ins_int_cuspat_tab) summarizes the features you can add to your system by performing simple customizations during or after installation. (ins_ins_chap) describes these software customizations in detail and provides instructions for implementing them. Many users will not need to make any of these customizations.

(Features Available Through Simple Software Customizations\ins_int_cuspat_tab) (\multipage) (3\25\8) (Feature\Section\Description) (Changing characters SRCCOM uses to indicate insertions and deletions\ 2.6.1\Normally, when you use the SRCCOM utility or DIFFERENCES/CHANGEBAR command to compare two files, SRCCOM uses the vertical bar character to indicate insertions and the bullet (alphabetic o) character to indicate deletions. You can modify SRCCOM to use different characters.) (Changing default output device from line printer to terminal \2.6.2\If your configuration does not include a printer, you can change the default output device (which certain monitor commands use) from printer to terminal. To make this change, you can edit the start-up command file.) (Changing the LD handler suffix character\2.6.3\ You can change the LD handler suffix character (LD(x)) to anything other than X.) (Changing number of directory columns\2.6.4\ When you use the DIRECTORY command, the directory prints in two columns. When you use the DIRECTORY/BRIEF command, the directory contains five columns with less information. You can modify DIR to change the default number of columns.) (Changing default order of directory listings\2.6.5\ By default, DIR lists a directory's contents by physical position. You can modify DIR to change the default to any one of five orders: creation date, file name, file size, file type, or position.) (Changing number of /Q p-sects LINK allows\2.6.6\ You can modify LINK to change the number of absolute base-address p-sects that LINK allows. Normally, LINK's /Q option lets you specify the absolute base addresses of up to eight p-sects in your program.) (Changing size of LINK's library module list\2.6.7\ To change the default size of LINK's list of library modules, you can modify LINK. LINK normally creates a list of 252(8) modules to be included from libraries during the link operation. If you are a DIBOL user, you must customize the software.) (Changing size of QUEUE work file\2.6.8\ You can modify QUEUE to change the size of the work file QUEUE uses to queue files to be sent to a device. If you increase the size of the work file, QUEUE can handle more files at one time.) (Modifying the EDIT utility\2.6.9\ If you have a terminal with nonstandard ESCAPE code (that is, the terminal generates 175(8) or 176(8) rather than 33(8)), you must modify EDIT.SAV so that it operates correctly.) (Installing other devices\2.6.10\ When you boot the system device, the bootstrap installs the devices in your hardware configuration if the appropriate device handler is on the system device and if there are enough slots. If you want to install a device that the bootstrap does not install, use the REMOVE and INSTALL commands. You can also:

(Change LP, LS, RK, DX, DY, DL, DM, or DU addresses): If any of these devices are installed at nonstandard CSR and vector addresses, you can use the monitor SET command to change the addresses.

(Install hardware magtape): If you need hardware magtape support, you must perform a system generation and then rename the hardware handler to MM.SYS, MT.SYS, MS.SYS, or MU.SYS (or the mapped versions with an X suffix).

(Set magtape parity and density): If you need to set magtape parity or density to other than the standard 800 bits/in, odd parity, you can use the monitor SET command for TM11 or TJU16 magtape (but not TS11).) (Modifying BATCH to save space\2.6.11\ If (after performing the system generation procedure and including BATCH support) you need to save disk space, you can store certain system programs on DK rather than on SY and cause BATCH to access them there. Modify BATCH so that it invokes system programs with the monitor RUN command (which assumes DK as the default) rather than with the R command (which always uses SY).) (Modifying LINK to change default SYSLIB device\2.6.12\ By customizing the linker, you can change the device on which the default system library, SYSLIB.OBJ, resides.) (Modifying help text\2.6.13\ To change the help text that prints when you use the HELP command, you must create your own help text file, process that text file with LIBR, and copy the resulting library and the file HELP.EXE to the same volume.) (Preventing fatal system errors from causing a reset\2.6.14\ You can customize the monitor to prevent it from performing a hard reset of errors when a fatal system error occurs. The normal reset stops I/O, protecting media from being corrupted. Some hardware errors may be more easily diagnosed without this reset.) (Running RT--11 in less memory than is available\2.6.15\ You can customize your software if your application requires that RT--11 run in less memory than is available.) (Setting VTCOM default dial string\2.6.16\ You can modify VTCOM to set a default string for the DIAL command.) (Setting upper limit on file size\2.6.17\ If your application requires an upper limit to the size of a file, you can change the monitor to set the limit you require.) (Changing the number of bad blocks that BUP accepts\2.6.18\ If you want BUP to handle more than 25 bad blocks on the input device, change BUP to accept and process as many as you specify.) (Changing the default file type extension of IND control files\2.6.19\ You can change the default IND file type extension from .COM to whatever you specify.) (Setting upper limit on memory size\2.6.20\ If your PDP--11 does not generate a bus timeout trap, RT--11 does not load into memory properly. You can alter the monitor to cause the bootstrap to never look for more than 28K words of memory.) (Suppressing bootstrap message\2.6.21\ If you want to prevent the monitor identification message from printing when you bootstrap a monitor, you can modify that monitor.) (Suppressing start-up indirect command file\2.6.22\ If you want to prevent the start-up command file from executing when you bootstrap a monitor, you can modify that monitor.) (Suppressing start-up indirect command file echo\2.6.23\ If you want the start-up indirect command file to execute when you bootstrap a monitor but you do not want the command lines in the file to echo (appear) on the terminal, you can modify the monitor.) (Changing bootstrap message\2.6.24\ If you want to change the monitor identification message that appears when you bootstrap a monitor, you can modify that monitor.) (Changing default device for indirect command files\2.6.25\ If you want to change the default device for indirect command files, you can modify the monitor. Normally, the monitor looks for the command file on DK:.) (Changing default file type for indirect command files\2.6.26\ If you want to change the default file type for indirect command files, you can modify the monitor. Normally, indirect command files have the default file type .COM.) (Changing default device for FRUN command\2.6.27\ If you want to change the default device for the FRUN command, you can modify the monitor. Normally, the monitor looks for the foreground program on device DK: when you type FRUN filnam.) (Changing default file type for FRUN command\2.6.28\ If you want to change the default file type for the FRUN command, you can modify the monitor. Normally, the default file type for foreground programs is .REL.) (Changing default device for EDIT utility command\2.6.29\ If you want to change the default device for the EDIT command with EDIT.SAV, you can modify the monitor. Normally, the monitor looks for the hard-copy editor file EDIT.SAV on device SY.) (Changing default file name for EDIT command\2.6.30\ If you want the monitor to run an editor other than the default editor when you type the EDIT command, you can modify the monitor to change the file name of the default editor.) (Using Examine and Deposit above background job\2.6.31\ If you want to be able to examine and modify the monitor and the I/O page, you can customize the monitor to remove a restriction on the use of the examine (E) and deposit (D) commands. Normally, the monitor allows you to examine and modify only locations inside the background job's area.) (Changing default device for QUEMAN\2.6.32\ If you want to send a file to a device other than LP when you use the PRINT command in an FB system (with QUEUE running as a foreground job), you can modify the monitor to change the default. This modification also changes the default for the DELETE/ENTRY command.) (Changing indirect command file nesting depth\2.6.33\ If you want to change the depth to which you can nest indirect command files, you can modify the monitor. Normally, RT--11 allows you to nest indirect command files three deep.) (Changing threshold for resuming output-stalled jobs\2.6.34\ If you have a foreground job that produces much terminal output and stalls frequently (waiting for room in the terminal output buffer), you can modify the monitor to improve throughput.) (Changing default number of directory segments\2.6.35\ If you want DUP to use a different default number of directory segments when you initialize volumes, you can modify DUP. DUP normally uses the number of directory segments specified in a table in DUP.) (Changing width of banner pages from 132 to 80 columns\2.6.36\ If you want to change the width of banner page printouts from 132 to 80 columns, you can modify QUEUE.) (Modifying listing page length in LINK\2.6.37\ If your line printer uses paper that is not 10.5 inches long, or if you do not have a line printer, you can modify LINK to change the listing page length from the standard 60 lines.) (Assigning HELP file\2.6.38\ You can modify the monitor to assign your HELP file to a file or device other than SY:HELP.SAV.) (Changing device from which IND is run\2.6.39\ You can modify the monitor to change the device from which IND is run.) (Replacing bad blocks\2.6.40\ You must customize DUP if your user-written device handler supports bad block replacement. One change is required to replace all bad blocks, another to replace only bad sectors.) (Including user-written magtape handler\2.6.41\ You must customize DUP, PIP, and MDUP if you use a user-written magtape handler.) (Eliminating or changing the IND control file terminating message\2.6.42\ You can eliminate or change the terminating message of IND control files.) (Changing default file type of logical disk files\2.6.43\ You can change the default file type of logical disk files from .DSK by modifying either the LD.SYS file or the conditional file SYSGEN.CND.) (Changing QUEUE to allow first form feed\2.6.44\ You can modify QUEUE to never suppress the initial form feed in a file.) (Changing listing page length in MACRO and CREF\2.6.45\ You can change the default (60 lines) page listing length for MACRO and CREF.) (Changing default command file processor to IND\2.6.46\ You can change the monitor command file processor from KMON to IND.) (Limiting amount of memory KEX requests\2.6.47\ You can reduce memory requested by KEX from the default 32KW to your requirements by using the .SETTOP programmed request.) (Changing MACRO's default .LIST/.NLIST options\2.6.48\ You can change the default options for the .LIST/.NLIST macros.) (Changing MACRO's default .ENABLE/.DISABLE options\2.6.49\ You can change the default options for the .ENABLE/.DISABLE macros.) (Modifying KED default file type\2.6.50\ You can change the KED default file type.) (Changing SPOOL's work file size\2.6.51\ You can change the size of SPOOL's work file.) (Changing SPOOL's output device\2.6.52\ You can change SPOOL's default output device.) (Changing LINK's default map and table output to 132 columns\ 2.6.53\You can change LINK's default link map and global cross-reference table output to 132 columns.) (Changing default size of MACRO--11 work file\2.6.54\ You can change the default size of MACRO--11's work file to a value from 128(10) to a maximum of 256(10) blocks.) (Changing name and default device for UCL.DAT\2.6.55\ You can change the name and default device for UCL.DAT.) (Suppressing dynamic allocation of a region for IND\2.6.56\ You can suppress IND's dynamic allocation of a region in extended memory for its symbol table.) (Changing size of UCL.DAT\2.6.57\ You can change the maximum number of user-defined UCL commands from 31(10) to a maximum you specify.) (Changing default VTCOM send speed\2.6.58\ You can change the default VTCOM send speed to FAST if the host terminal service supports XON/XOFF.) (Modifying system macro library SYSMAC.SML\2.6.59\ You can modify the system macro library by running the SPLIT utility.) (Modifying VTCOM default dial string prefix\2.6.60\ You can modify the VTCOM default dial string prefix.) (Modifying VTCOM default dial string suffix\2.6.61\ You can modify the VTCOM default dial string suffix.) (Automatically creating KED/KEX journal files\2.6.62\ You can cause the keypad editor to automatically open and write a journal file at each editing session.) (Adjusting default KED/KEX journal file size allocation\2.6.63\ You can change the number of blocks allocated by the keypad editor on the default journal file device.) (Creating a monitor-independent ODT debugger\2.6.64\ You can create an ODT variant that does not require that the operating system be loaded in memory.) (Forcing an explicit KED/KEX journal file device\2.6.65\ You can force the default journal file device to be other than DK.) (Modifying the storage capacity for LEARN macros\2.6.66\ You can modify the amount of storage capacity (in memory) that the keypad editor allocates for LEARN macro storage.) (Modifying the maximum number of LEARN macros\2.6.67\ By default, the keypad editor allows the definition of 8(10) LEARN macros at one time. You can modify that limit.) (Restoring LOCAL form feed processing\2.6.68\ You can restore the recognition of form feeds in files being processed by the LOCAL keypad editor feature.) (Removing the JSW bit 6 check for SL\2.6.69\ The single-line editor (SL) checks bit 6 of the Job Status Word before editing a command line. You can remove that bit check.) (Changing SL character edit mode to REPLACE\2.6.70\ SL can edit single characters in two modes: REPLACE and INSERT. You can change the default edit mode from INSERT to REPLACE.) (Changing the VTCOM command mode character\2.6.71\ You can change the character you type to VTCOM to enter command mode from CTRL/P to one you specify.) (Forcing obsolete SJ monitor value in CONFIG bit $FBMON\ 2.6.72\You can change the default value of the $FBMON bit in the CONFIG word from set to clear, if required, to load handlers that require a clear $FBMON bit.) (Making LINK /G option a default\2.6.73\You can make the /G option a default whenever LINK is run. The /G option is not available under DCL; you can use this customization to include that option when issuing LINK commands under DCL.) (Changing the default magtape label size\2.6.74\The current magtape label size is 80(10) bytes. If you need to change that size to some other value, use this customization. (80 byte labels are required for any magtape that will be subsequently read by the VMS operating system.)) (Do You Need to Perform the System Generation Procedures?)

You must perform the system generation procedures if you want to add to your system any features that are not included in the distributed software or listed in (ins_int_cuspat_tab). You may also need to perform the system generation procedures if you want to remove features to reduce the size of the monitor and improve response time. Refer to the system generation dialog and the descriptive text in the (syg_book) further information about these features. (Choosing a Reading Path)

You only need to read the chapters that pertain to your configuration. (ins_readpath_tab) gives you the information you need to select these chapters. ()If you are unfamiliar with RT--11 software, you should probably use the distributed monitors uncustomized for a while. Once you have gained familiarity with the system, you will be better equipped to perform customizations or system generation procedures. Be aware, however, that some customizations may be essential for your particular application, and, consequently, you may experience problems when you use software without needed support. If you are an inexperienced user, be sure to study (ins_int_cuspat_tab), but you may want to delay making any customizations until you have gained more experience with RT--11. Further, be sure to read the (int_book) before using RT--11 for any critical applications.

(Chapters You Should Read\ins_readpath_tab) (\multipage) (3\20\20) (If Your DistributionMedium is:\ And if Your System Device on Target System is:\Then Read Chapters:) (Single-Density DisketteRX01\Single-Density DisketteHard Disk (SIMPLE) RL01 RL02 RK05 RK06 RK07 \ 1, 2, 3 1, 2, 4) (Hard Disk (SIMPLE) RL02 \Hard Disk (SIMPLE) RL01 RL02 RK05 RK06 RK07 RC25 \1, 2, 5) (\Single-Density or Double-Density Diskette\1, 2, 6) (Double-Density Diskette (SIMPLE) RX02 \Double-Density Diskette (SIMPLE) RX02 \1, 2, 7) (Magtape (SIMPLE) 9-track, 1600 bpi TMSCP \Hard Disk (SIMPLE) RL01 RL02 RK05 RK06 RK07 \1, 2, 8) (Diskette RX50\ (simple) Professional 350/380 MSCP disk \ (simple) 1, 2, 9 Use Automatic Installation Procedure )