C7$ ?BOOT-U-No boot on volume ߋtvSBA-KN41A-BC RX2 7/7 DECRT11A `Ԁt:#v t:#O:t:#89g& RT-11 V5.4B RELEASE NOTES ========================= | This file contains release notes for RT-11 V5.4B, release notes for | RT-11 V5.4A, and the release notes addenda for RT-11 V5.4. | Information for RT-11 V5.4B is indicated by change bars and pertains | only to that release. The information in this file is included in the | new on-line index program INDEX. | This file is structured in the following manner: 1.0 FEATURES OF RT-11 FOR V5.4 AND UPDATES TO V5.4 2 1.1 FEATURES OF RT-11 V5.4B 2 1.2 FEATURES OF RT-11 V5.4A 3 1.3 FEATURES OF RT-11 V5.4 3 2.0 NEW FILES ON THE DISTRIBUTION KIT 4 2.1 ON-LINE INDEX PACKAGE 4 2.2 MSCPCK.SAV 5 3.0 NEW DEVICES AND FEATURES, SOFTWARE AND DOCUMENTATION CORRECTIONS 6 3.1 DEVICES 6 3.2 MONITORS 6 3.3 UTILITIES and PROCEDURES 7 3.4 DEVICE HANDLERS 32 3.5 PROCESSORS AND PERIPHERAL DEVICES 38 3.6 SYSMAC.SML (System Macro library) 40 3.7 SYSLIB (System Subroutine Library) 42 3.8 DOCUMENTATION CORRECTIONS 47 3.8.1 RT-11 System Release Notes 47 3.8.2 RT-11 System User's Guide 48 3.8.3 RT-11 Installation Guide 48 3.8.4 Introduction to RT-11 49 3.8.5 RT-11 Software Support Manual 49 3.8.6 RT-11 Programmer's Reference Manual 50 4.0 RESTRICTIONS 56 Page 2 | 1.0 FEATURES OF RT-11 FOR V5.4 AND UPDATES TO V5.4 | 1.1 FEATURES OF RT-11 V5.4B | Version 5.4B provides support for the following new features: | o A new on-line index package, INDEX | o Enhancements and changes to the single-line editor, SL | - Increased storage of previous commands, using a 512-byte | command stack | - Keypad editing of command lines | - Support for storing a command line offset into the | command stack (SET CYCLE) for repeated recalling of | successive commands (CYCLE). | o Changes and enhancements to the backup utility BUP | - Support for storing several file or volume backups on one | or several magtapes | - Support for running BUP from a KMON command or IND | control file, using the new /NOQUERY option | - Support for inhibiting the bad block scan on output | volumes | - Enhancements to the magtape volume directory display | o Support for customizing IND to: | - Change the default file type extension of IND control | files | - Eliminate or change the IND control file terminating | message | o Addition of DATE, IDATE, RAN, and RANDU functions and | subroutines to the RT-11 system subroutine library, SYSLIB | o Support for LG01 and LG02 dot-matrix printers Page 3 1.2 FEATURES OF RT-11 V5.4A Version 5.4A provides support for the following new features and devices: o Support for verifying DU devices, using the FORMAT/VERIFY:ONLY command. (DU devices larger than one partition must be verified one partition at a time) o Full formatting and verifying support (20M byte) for the RD31 hard disk under DW handler o Support for the RD32, RD54, and a second RX33 diskette drive on PDP-11 processors o FORMAT utility support for formatting RX33 diskettes o Support for automatic installation on RX33 diskette drives (using RX50 diskettes as automatic installation media) o New features and improvements to the BUP utility - Ability to transport BUP-written magtapes to VAX/VMS systems - New format for magtape backup media - Improved verification for multivolume magtape operations - Improved error message clarity o New cache-bypass for global regions under XM monitor 1.3 FEATURES OF RT-11 V5.4 Version 5.4 provides support for the following new features and devices: o Support for the TK50 magtape drive and the TK50 magtape as a distribution medium for automatic and manual installation o Support for the PDP-11/53 processor o Support for the RX33 diskette drive as a system and data device o Support for the RD31 disk drive under DU (limited support under DW) o Support for the new LA75 printer in the same manner as LA50 printer support Page 4 o Support for fetching magtape handlers under the XM monitor o New DBG-11 Symbolic Debugger Package (unsupported) o New Ethernet hardware handler NU for UNIBUS Ethernet controllers (DEUNA, DELUA) o New device handler macros: .DRTAB and .DRUSE o New system subroutines: JREADF and JWRITF o New TMSCP (MU) device controller checking program: MSCPCK.SAV (unsupported) o New procedures to back up the distribution to magtape o New procedures to create bootable magtapes o New uniform automatic installation procedure for all input and output media that are supported for automatic installation, with additional supported media 2.0 NEW FILES ON THE DISTRIBUTION KIT The following files are included with the RT-11 V5.4B distribution kit and are not documented in the RT-11 System Release Notes for V5.4. | 2.1 ON-LINE INDEX PACKAGE | RT-11 V5.4B includes a new on-line index program, INDEX, that displays | on your terminal screen most of the entries contained in the RT-11 | Master Index. INDEX entries are taken directly from the index files | used to create the RT-11 Master Index. INDEX also contains entries | for the RT-11 System Release Notes and the on-line release notes file, | V5NOTE.TXT, that are not included in the RT-11 Master Index. The | entries for INDEX are updated for each release of RT-11. Therefore, | INDEX is your best source for the latest information in the RT-11 | documentation. | The INDEX package consists of three files: | INDEX.IDX is an index-pointer (an index of the index) | INDEX.IMG is the index file | INDEX.SAV is the INDEX program device | You can run INDEX as the background job, the foreground job, or as a | system job. The files in the INDEX package can be on your system (SY) | and/or data (DK) device. Page 5 | When you run INDEX, it displays an introductory frame on your screen. | That frame displays the mnemonics for the manuals in the RT-11 | documentation set that are contained in the index. Manuals not listed | in the introductory frame are not included in the index. | Of those manuals listed, only the device-specific installation | information (Chapters 3 through 11) of the RT-11 Installation Guide | (INST), and the actual commands and options in the RT-11 System User's | Guide (SUG) are not included in the index. (It is assumed that you | have installed your system before you require the on-line index, and | the commands and options in the SUG are alphabetically listed.) | Installation and command information appearing elsewhere in the RT-11 | documentation is indexed. | Press RETURN to enter the index. Type as short an unambiguous search | string as possible and press RETURN. INDEX displays any entries | matching the string. Continue to press RETURN to scroll through the | index or type another search string and press RETURN. | Type CTRL/C to exit from INDEX. 2.2 MSCPCK.SAV The file, MSCPCK.SAV, is included with the RT-11 distribution kit and is not documented in the RT-11 System Release Notes for V5.4. MSCPCK.SAV checks your TMSCP (MU) device controller (if present) and reports its revision level by displaying the following message: ?MSCPCK-I-MUx-FW Rev Level is nnn/HW Rev Level is nnn where x is the MU unit number and nnn is a 3-digit firmware or hardware revision level. A command to run MSCPCK is included and enabled in the start-up command files for all monitors (except STARTA.COM). If your configuration includes a TMSCP device, be sure that MSCPCK.SAV resides on your system volume. If your configuration does not include a TMSCP device, you can disable the command to run MSCPCK in your start-up command file by editing that file and placing an exclamation point (!) before the command (!R MSCPCK). Reliable TK50 operation on Q-bus processors requires a controller of at least a particular revision level. See Section 3.5 (TK50 magtape) of this file for information specific to MSCPCK.SAV and the TK50. Page 6 3.0 NEW DEVICES AND FEATURES, SOFTWARE AND DOCUMENTATION CORRECTIONS The following sections list new RT-11 devices, features, general information, software corrections, documentation changes and additions, and restrictions for RT-11 V5.4B, V5.4A. Also included is additional information for V5.4 finalized after the printing of the RT-11 System Release Notes, AA-5286I-TC. 3.1 DEVICES RT-11 contains support for the following new devices: | o LG01 and LG02 printers | RT-11 V5.4B supports the new LG01 and LG02 dot-matrix | printers. The SETUP utility does not support the uniform | printer modes [NO]BOLD, LANG, and [NO]TABS. SETUP supports | no nonuniform printer modes for the LG01 and LG02. (Uniform | and nonuniform SETUP modes are listed in Section 1.6.1 of the | RT-11 System Release Notes and described in Chapter 7 of the | RT-11 System User's Guide.) | DIGITAL recommends you set at least the following | conditionals when using the LP or LS handler with the LG01 | and LG02: | SET LP/LS CR,LC,CTRL,FORM,NOFORM0 3.2 MONITORS BSTRAP o For RT-11 V5.3, any RT-11 monitor that was generated with memory parity support would not boot on machines immediately following a power-up. For RT-11 V5.4, monitors that are generated with memory parity support boot correctly on power-up. | KMON | o Job names specified using the /NAME:name option can be | numeric. For example, the following commands run VTCOM as a | system job and assign it the name 6. All further references | to VTCOM must use the name 6, and that name assignment | remains in effect until you reboot your system. | .SRUN SY:VTCOM.SAV/NAME:6/PAUSE | LOAD XC=6 | RESUME 6 | You would then specify 6 in response to the system job prompt Page 7 | (JOB>) to call VTCOM. The SHOW JOBS command would display | the job 6. | o Previously, when running under the SJ monitor, you could not | use the .CHAIN request to chain to a program when the handler | for the device containing that program was not loaded. Doing | that returned the error message, ?MON-F-Trap to 4 nnnnnn, | rather than running the program. For RT-11 V5.4B, the .CHAIN | programmed request works under the SJ monitor as documented. | o Previously, issuing a CLOSE command could hang or crash your | system under the following circumstances: a channel was | still open to the device containing the file you were closing | and that device was not loaded. Those circumstances could | corrupt the fetched handler for that device. For RT-11 | V5.4B, the CLOSE command correctly fetches and releases the | device handler and the problem does not occur. | o Previously, the ABORT command did not correctly stop a job | under the XM monitor when that job had called and enabled the | .SCCA request. ABORT set bit 15 in a random word and not the | .SCCA terminal status word. For RT-11 V5.4B, ABORT correctly | sets bit 15 in the .SCCA terminal status word, and correctly | stops a job under those circumstances. | SJ (Single-Job Monitor) | o If you are using the SJ monitor, read the restriction | concerning I/O programmed requests within completion routines | and device handlers located at the beginning of Section 4.0 | of this file. USR o For RT-11 V5.4, all monitors support the .DRPTR macro. 3.3 UTILITIES and PROCEDURES Automatic Installation o RT-11 V5.4A supports the RX33 diskette drive for the automatic installation procedure. The automatic installation media is RX50 diskettes. Use the following procedure to perform automatic installation on the RX33 diskette drive: 1. If your processor is on, turn it off. Remove any diskette from the RX33 diskette drive. If you have more than one RX33 diskette drive on your system, remove any diskettes from those drives. 2. Select from your RX50 software distribution the diskette labeled AUTO. Insert that diskette in the Page 8 RX33 diskette drive. If you have more than one RX33 diskette drive on your system, you can insert the AUTO diskette in either drive. 3. Turn on your processor. Your processor boots the diskette in the RX33 diskette drive. 4. Follow the instructions displayed on your terminal screen to perform the automatic installation. o For RT-11 V5.4, if automatic installation is not valid for your hardware configuration and your distribution is multivolume, you are prompted to mount diskette 1; diskette 1 boots the FB monitor on RX01/RX02 distributions or the XM monitor on the RX50 distribution. If your hardware configuration is not valid and your distribution is a single volume (disk), the automatic installation procedure boots the FB monitor on that volume and refers you to the RT-11 Installation Guide. If your distribution is TK50, the automatic installation procedure boots the AI monitor on device VM; see Section 4.4 of the RT-11 System Release Notes for information on manually installing RT-11 from a TK50 magtape. BATCH | o Previously, BATCH could not run virtual jobs under the XM | monitor. For RT-11 V5.4B, BATCH can now run virtual jobs | under the XM monitor; the restriction concerning this in the | RT-11 System Release Notes no longer applies. o Previously, BATCH did not work. Attempting to run BATCH returned the error messages, ?MON-F-No device, or ?BATCH-F-Invalid LOG device. For RT-11 V5.4, BATCH works as documented. BUP | o BUP for RT-11 V5.4B will restore backed-up files and volumes | written by previous versions of BUP. However, files and | volumes backed-up using V5.4B BUP require the V5.4B BUP to | restore them. Page 9 | o For RT-11 V5.4B, BUP supports the following new or changed | options: | KMON Option CSI Option* Explanation | ----------- ---------- ----------------------------- | /INITIALIZE /Z Must be specified to initialize | a magtape; is automatically | included with disk operations. | /[NO]LOG /W /NOLOG (/W) suppresses various | informational messages BUP | prints as backup operations are | performed. The default | operation is to display the | messages (/LOG). | /[NO]QUERY /Y /NOQUERY (/Y) inhibits various | responses otherwise required | from the terminal. Allows | using BUP from KMON command and | IND control files to write a | single disk or magtape output | volume (MOUNT prompts require | terminal response). /QUERY is | the default. | /OUTPUT[:filespec] Writes the results of a | DIRECTORY/BACKUP operation to | the specified file | specification. The input | device can be magtape or disk. | The default operation (no | option or option without file | specification) displays the | directory on your terminal. | /PRINTER Directs the results of a | DIRECTORY/BACKUP operation to | your printer. | /[NO]REWIND /M /NOREWIND (/M) inhibits | rewinding magtape before | appending next saveset to that | magtape. Increases the speed | of backup operations but also | stops saveset name verification | (the magtape must rewind to | check for unique saveset | names). The default operation | is to rewind the magtape before | appending the next saveset to | that magtape (/REWIND). Page 10 | /[NO]SCAN /G /NOSCAN (/G) inhibits the bad | block scan on disk output | volumes. Use /NOSCAN only on | disk output volumes you know | contain no bad blocks. The | default operation is to scan | each disk output volume for bad | blocks (/SCAN). | /SAVESET /S Valid only with | /RESTORE/DEVICE/FILES options | combination and only from | magtape volumes. Use to | indicate the saveset containing | a file you want to restore. | /VERIFY:ONLY /V:ONL Valid only when used with | /RESTORE (/X) option. Causes a | comparison between named | saveset and restored file or | volume. | * All CSI options are position dependent; they must be | coupled with the input file. Coupling any CSI option with | the output file returns an error message. Page 11 | BUP operations involve either initialization, making the | backup, obtaining a directory, or restoring what was backed | up. The following table lists valid BUP option (CSI and | KMON) combinations for those categories of BUP operations: | Valid Valid | CSI KMON | Operation Options Options | --------- ------- ----------- | Initialize /Z /INITIALIZE | /Y /NOQUERY | Backup /I /DEVICE | /Z /INITIALIZE | /W /NOLOG | /Y /NOQUERY | /M /NOREWIND | /G /NOSCAN | /V /VERIFY | Directory /L DIRECTORY/BACKUP | DIRECTORY/BACKUP/OUTPUT[:filespec] | DIRECTORY/BACKUP/PRINTER | Restore /X /RESTORE | /F /FILE | /I /DEVICE | /W /NOLOG | /Y /NOQUERY | /M /NOREWIND | /S /SAVESET | /V[:ONL] /VERIFY[:ONLY] | The following text explains how to use the RT-11 V5.4B BUP | options: | o For RT-11 V5.4B, you can perform multiple backup operations | to the same magtape or series of magtapes. The result of | each file or volume backup operation is called a 'saveset'. | You can only create savesets on magtapes; you cannot create | savesets on disks. Use the following information to create | savesets: | - For RT-11 V5.4B, you must initialize all magtapes you use | as BUP output volumes. The following example command | initializes magtape device MS0: | .INITIALIZE/BACKUP MS0: | You can also initialize the magtape by including the | /INITIALIZE option in the backup command line for the Page 12 | first backup operation as shown below. When you back up | files or volumes to a series of magtapes, BUP implicitly | initializes all subsequent magtapes in the series. | The initialization process rewinds the magtape and writes | a volume and header label at the beginning of the | magtape. | - You can name each saveset as shown in the following | example. Each saveset name must be unique, or BUP | returns a fatal level error message. The following | example illustrates backing up the volume located on | device DL1. In the command, DL1 is the input device, MS0 | is the backup magtape volume, and FOO is the optional | saveset name with the default file type of .BUP: | .BACKUP/DEVICE DL1: MS0:FOO | If you do not supply a saveset name, BUP uses the device | name with file type .BUP as that saveset name (DL1.BUP). | You can couple the initialization process with the first | backup operation by including the /INITIALIZE option in | the command line: | .BACKUP/INITIALIZE/DEVICE DL1: MS0:FOO | - BUP normally rewinds magtapes before each backup | operation. If you intend to back up a number of savesets | to a magtape, you can inhibit the magtape rewinding by | including the /NOREWIND option in the backup command | line. However, BUP cannot check that the saveset name | you use is unique unless the tape rewinds before each | backup operation. DIGITAL recommends you explicitly | assign unique saveset names when you use the /NOREWIND | option. | - You can back up a file on a volume to a saveset on | magtape by including the filename in the command line. | For example, the following command backs up the file | MYFILE.TXT located on device DL1 to magtape MS0. Because | no explicit saveset name is specified, this saveset will | have the name MYFILE.BUP. It is assumed that saveset | FOO.BUP is already written on magtape MS0; saveset | MYFILE.BUP is being added to magtape MS0. | .BACKUP DL1:MYFILE.TXT MS0: | BUP notifies you this saveset is being added to another | saveset on magtape MS0 by displaying the following | informational message: | ?BUP-I-Appending to volume Page 13 | - You can display a directory of the savesets of a | specified magtape, using the DIRECTORY/BACKUP command. | The following example displays the directory of savesets | for magtape MS0: | .DIRECTORY/BACKUP MS0: | You can send the directory of the savesets on a magtape | to the device and file you specify, using the | /OUTPUT[:filespec] option. The default file type is | .LST. For example, the following command stores the | directory of magtape MS0 on device DL1 with the file name | MAG1.LST: | .DIRECTORY/BACKUP/OUTPUT:DL1:MAG1.LST MS0: | You can send the directory of the savesets on a magtape | to your printer using the /PRINTER option. The following | example sends a directory of the savesets on magtape MS0 | to your printer: | .DIRECTORY/BACKUP/PRINTER MS0: | For RT-11 V5.4B, the format for BUP magtape directories | has been changed to include the following new | information: | The saveset name. | The section of that saveset residing on this magtape | volume. If a saveset is spread across more than one | magtape volume, the magtape volume containing the | first section of the saveset is identified as | section 1, that containing the second section as | section 2, and so on. | The size of that saveset in blocks on this magtape | volume followed by the total size of the saveset. | If the two numbers are the same, the entire saveset | is on this magtape volume. | The date on which that saveset was backed up to this | magtape volume. | The following is an example display of the V5.4B BUP | magtape directory. The example magtape volume contains | the second section (2348 blocks) of a 5400 block saveset | named BIGDSK.BUP, the complete savesets FIRST.TXT and | SECOND.BUP, and the first (408 block) section of a 988 | block saveset THIRD.BUP. You would proceed to the next | magtape volume of this series to restore the second | section of THIRD.BUP. Page 14 | SAVESET SECTION BLOCKS DATE | BIGDSK.BUP 2 2348/5400 20-MAR-87 | FIRST .TXT 1 800/800 20-MAR-87 | SECOND.BUP 1 5400/5400 21-MAR-87 | THIRD .BUP 1 408/988 26-MAR-87 | DIGITAL recommends you maintain a directory of each | magtape backup series. You can restore a saveset or a | file located on a saveset from the backup magtape | containing that saveset by mounting only that magtape. A | directory of the savesets on a series of backup magtapes | can point you to the correct magtape to mount. | Because of the new saveset functionality, BUP must read | to the end of magtape volumes before returning a | directory. For certain magtape devices, this process can | take some time. | - You restore a device image saveset from a magtape or | series of magtapes, using the following command. In the | command, FOO is the named saveset contained on magtape | MS0. You are restoring FOO to disk device DL1: | .BACKUP/RESTORE/DEVICE MS0:FOO DL1: | You restore a file image saveset from a magtape or series | of magtapes by excluding the /DEVICE option. The | following command restores the file image FIRST.TXT from | magtape MS0 to device DL1: | .BACKUP/RESTORE MS0:FIRST.TXT DL1: | - You restore a file located on a particular saveset, using | the /SAVESET option with the RESTORE/DEVICE/FILES option | combination. In the command line, you couple the | /SAVESET option with the saveset name and supply the file | name. The following example restores the file, FILE.TXT, | located on saveset FOO.BUP contained on magtape MS0. | This example assumes that magtape MS0 contains the entire | file; if not, you would be prompted to mount the next | magtape input volume. | .BACKUP/RESTORE/DEVICE/FILE MS0:FOO/SAVESET,FILE.TXT DL1: | Mount input volume 1 in MS0: Continue? Y | ?BUP-I-Restore operation started on volume 1 | . | o For RT-11 V5.4B, you can inhibit the bad block scan on backup | operations from disk to disk, using the new BUP option | /NOSCAN. | o For RT-11 V5.4B, you can verify that the restored file or | volume is the same as the named saveset, using the Page 15 | /VERIFY:ONLY option with the /RESTORE option. As | appropriate, the /VERIFY:ONLY option causes BUP to return the | following informational messages: | ?BUP-I-Verify operation started on volume n | ?BUP-I-Verify operation complete | o For RT-11 V5.4B, BUP displays the following informational | message when you request a verify pass (/VERIFY) during a | backup operation: | ?BUP-I-Verify pass started | o For RT-11 V5.4B, you can inhibit the logging of informational | messages, using the /NOLOG option. | o For RT-11 V5.4B, BUP responses can be entered from command | files. Use the new /NOQUERY option to eliminate the need for | terminal intervention when you are writing a single output | volume (MOUNT prompts continue to require terminal | responses). The BUP restriction in the RT-11 System Release | Notes prohibiting running BUP from command files is removed. | o For RT-11 V5.4B, you can back up a smaller disk volume to a | larger disk volume or to a disk volume of the same size. BUP | no longer returns the error message, ?BUP-F-Enough space on | one volume - use PIP. However, if you back up a smaller disk | to a larger disk, the remainder of that larger disk is | unusable. | o Previously, RT-11 did not print any warning message if you | restored a device image to your system device. Doing that | can cause an uncoupling of RMON and the system files and | could corrupt your system device. For RT-11 V5.4B, BUP | displays the following warning requiring an affirmative | answer when you issue the command BACKUP/RESTORE/DEVICE and | your system device is the output volume: | Restoring over SYSTEM volume! | SY:/Restore; Are you sure? | o Previously, BUP attempted to back up files containing zero | blocks. For RT-11 V5.4B, BUP refuses to back up files | containing zero blocks and returns the following error | message: | ?BUP-F-No blocks to backup o For RT-11 V5.4A, you can transport BUP-written magtapes to a VAX/VMS system and manipulate those magtapes. Use the VAX/VMS EXCHANGE utility or RTEM. Magtapes you transport should contain directory-structured logical or physical disk images. Use the following procedure: Page 16 1. BUP magtapes can be mounted on a VAX/VMS system, using the following command, where mdnn is the magtape drive and RTBUP is the backup magtape label: $ MOUNT mdnn: RTBUP 2. Copy the BUP backup image to disk, using the following command, where ddn is the RT-11 device you backed up. This command produces a virtual disk image file: $ COPY mdnn:ddn.BUP * 3. Use the VAX/VMS EXCHANGE utility or RTEM to manipulate files on that virtual disk file. See the VAX/VMS EXCHANGE utility documentation for information on using EXCHANGE. The following command is shown as an example. In the example, vdn is a virtual disk name: $ EXCHANGE EXCHANGE>MOUNT/VIRTUAL vdn: ddn.BUP o The format that BUP uses to store data on magtape volumes has been changed to increase the reliability of multivolume magtape data retrieval and to make those volumes abide by certain industry conventions. BUP detects whether a magtape is organized in the new or old format, using information stored in the header records. Although the new format more closely resembles ANSI standard, certain data in the VOL1, HDR, and EOF records are not in conformance with that standard. o BUP for RT-11 V5.4A corrects several problems with the /VERIFY option, when that option is used to verify multivolume magtape backups. BUP for RT-11 V5.2 fails in the verify pass at the end of the last volume of a multivolume set. BUP for RT-11 V5.3 and V5.4 fails in the verify pass at the end of the first volume if another volume is to follow. BUP for RT-11 V5.4A correctly verifies multivolume magtape volumes. o BUP for RT-11 V5.4A records a starting block number in the header of each magtape volume. The value for that starting block number is the value for any previous magtape starting block number plus the number of blocks on the previous magtape. During a multivolume /RESTORE operation, Page 17 each starting block number is checked for consistency against the expected starting block number. If the two numbers disagree, the following error and warning messages are displayed: ?BUP-E-Tape volume position error ?BUP-W-Expected block nnn; Tape volume begins with mmm When the starting block number disagrees by 16 or less, the /RESTORE operation resumes with the current magtape starting block number. BUP displays the following warning message: ?BUP-W-Continuing RESTORE with mounted volume BUP aborts when the starting block number disagrees by more than 16. o BUP for RT-11 V5.4A performs a new consistency check at the end of each /DEVICE or file /RESTORE operation (but not /DEVICE/FILES). BUP reads the record following the last data record to verify that it is the final tape mark. If the final tape mark is not found, it indicates the RESTORE operation probably did not store blocks in their correct locations. BUP then displays the following error message: ?BUP-E-Tape volume position error o Previously, BUP wrote one extra magtape block when the number of disk blocks being read was divisible by eight but not divisible by eight times the number of memory buffers. For RT-11 V5.4A, BUP no longer writes an extra block under those circumstances. o Previously, BUP displayed the following error message when you attempted to back up to a magtape drive that was write protected, not ready, or off line: ?BUP-F-Directory input error on ddn:, where ddn: was the input disk drive. For RT-11 V5.4A, BUP returns the following error message under those circumstances: ?BUP-F-Output error Mxn:, where Mxn: is the magtape drive. o Previously, BUP incorrectly reported an input error on the output disk drive when an error was encountered reading back a magtape block during a BACKUP/RESTORE/VERIFY operation. For RT-11 V5.4A, BUP correctly returns the error message, ?BUP-F-Input error mxn:ddn.BUP, where mxn: is the magtape drive and ddn.BUP is the backup set name. o Previously, BUP did not append the device and backup set number to the error message it returned (?BUP-F-Output error) if an error occurred while writing a magtape. For RT-11 V5.4A, BUP correctly appends the device and backup set name and returns the error message, ?BUP-F-Output error Mxn:ddn.BUP, under those circumstances. Page 18 o Previously, BUP could fail to correctly initialize, back up, and restore data when the output volume was an RL01/RL02 (DL) or RK06/RK07 (DM) that was initialized with a non-RT-11 format. Results of a backup and restore operation using such a volume were unpredictable and often incorrect. For RT-11 V5.4, BUP correctly performs backup and restore operations for those volumes when they were previously initialized as non-RT-11 volumes. o Previously, BUP could fail to restore a single file from a magtape backup volume when file directory segments on the backed-up volume were not forward linked. BUP could not correctly search the directory of a volume on a magtape backup if that directory contained one or more segments that were not forward linked to the other segments. For RT-11 V5.4, BUP correctly follows the links of the directory segments and successfully restores single files under those circumstances. o Previously, BUP could incorrectly determine the size of an RK05 disk. When backing up a file that was larger than a single RK05 disk, BUP would incorrectly inform you to use PIP to copy the file to a single RK05. For RT-11 V5.4, BUP correctly sizes RK05 disks and no longer informs you to use PIP under those circumstances. o Previously, when you attempted to use VBGEXE to run BUP, BUP returned the error message ?BUP-F-Channel in use. For RT-11 V5.4, you can successfully use VBGEXE to run BUP. DIR o Previously, when you performed a directory (DIR command) on a magtape, you received the directory listing, the magtape rewound, and you then received the trailer information (number of files and free blocks). For RT-11 V5.4, you receive the directory listing with the trailer information while the tape is rewinding. You receive the monitor prompt after the magtape has rewound. | For RT-11 V5.4B, the above also applies when the directory | information is directed to your printer (DIRECTORY/PRINTER | command). DUMP o Previously, if you assigned the DUMP default output device (LP) to a file-structured device (for example, ASSIGN DU1 LP), DUMP did not recognize the assigned device as the default output device and returned the error message, ?DUMP-F-No LP, when you attempted to run DUMP. For RT-11 V5.4, DUMP recognizes the assigned device as the default output device and does not return the error message under those circumstances. Page 19 o Previously, if you used the CSI form to run DUMP and specified an output device (other than TT:) without a file name, the command failed and returned the error message, ?CSI-F-Invalid command. For RT-11 V5.4, the command works as documented and places the output on the device you specify with the default file name DUMP.DMP. | DUP | o Previously, DUP incorrectly initialized magtapes by writing | random characters to the ANSI VOL1 label record. For RT-11 | V5.4B, DUP correctly initializes magtapes by writing blanks | (ASCII space characters) in character positions 52 through 79 | of the ANSI VOL1 label record. That conforms to ANSI | standard X3.27. ERROR LOGGER o The following information is not included in Section 16.4.1 of the RT-11 System Utilities Manual, Using ELINIT: When you RUN ELINIT (or R ELINIT) followed by a carriage return and you receive the prompt requesting the device to which you want the statistics file ERRLOG.DAT written, you can press RETURN to select your system device (SY) or you can specify a device. If you specify a device, you must include a colon (:) following that device; for example, DL:. Also, do not specify a file name in response to that prompt; only the file name ERRLOG.DAT is valid. For RT-11 V5.4, if you do not specify a valid device in response to the ELINIT prompt requesting the device to which you want the statistics file ERRLOG.DAT written, ELINIT checks the default data device (DK) for ERRLOG.DAT. If ERRLOG.DAT is not on DK, ELINIT returns the warning message, ?ELINIT-W-File not found DK:ERRLOG.DAT. ELINIT then writes ERRLOG.DAT on DK. If you specify a valid device that does not contain the file ERRLOG.DAT, ELINIT returns the warning message, ?ELINIT-W-File not found , where ddn: is the device you specified. ELINIT then writes the file ERRLOG.DAT on that device. o For RT-11 V5.4, the block number returned in the device error report is in decimal radix. Previously, the block number was in octal radix. FORMAT o For RT-11 V5.4A, FORMAT supports formatting the RX33 diskette. Formatting RX33 diskettes requires an RX33 diskette drive and an RQDX3 controller of at least microcode revision 2. If you attempt to format an RX33 diskette and your controller Page 20 is below microcode revision 2, FORMAT returns the error message, ?FORMAT-F-Operation unsupported on old micro-code revision. Contact your local DIGITAL field service representative to update your RQDX3 controller. If you attempt to format an RX50 diskette in an RX33 diskette drive, FORMAT returns the query, ddn: is an RX50 volume/FORMAT-Are you sure? Do not format single-sided quad-density RX50 diskettes in the RX33 diskette drive. You can format double-sided high-density diskettes previously formatted as RX50s in the RX33 diskette drive. If you attempt to format an RX33 diskette and your DU controller is not an RQDX3, FORMAT returns the error message, ?FORMAT-F-Device invalid or not supported by FORMAT. o The error message, ?FORMAT-U-Channel in use, indicates an internal FORMAT error. If you receive that message, reboot your system and try the operation again. If the error occurs again, get a new copy of FORMAT.SAV and retry the operation. If the error persists, submit an SPR to DIGITAL. See Appendix B of the RT-11 System Release Notes for information. o Attempting to format a disk that is not mounted returns the error message, ?FORMAT-F-Device not ready. If you receive that message and your disk is not mounted, mount your disk and be sure it is up to speed. IND | o Previously, the .READ directive incorrectly enforced the | obsolete 80-characters-per-line restriction; that | restriction was removed for RT-11 V5.4. For RT-11 V5.4B, the | .READ directive correctly allows 132 characters per line. | o Previously, the .TEST directive failed to detect | nonalphanumeric characters appearing in a string symbol after | the first occurrence of a lowercase alphabetic character. | For example, performing a .TEST SYMBOL where SYMBOL contained | the string v/ would incorrectly set the special symbol | to true. For RT-11 V5.4B, the .TEST directive | recognizes nonalphanumeric characters appearing in a string | symbol after a lowercase alphabetic character, and | would be correctly set to false for this example. | o 2.7.66 Changing the Default File Type Extension of IND | Control Files | For RT-11 V5.4B, you can change 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). Page 21 | 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 | *IND.SAV | Segment? 0 | Base? 0 | Offset? ..INDF | Segment Base Offset Old New? | 000000 000000 ..INDF ?????? ;R | 000000 000000 ..INDF ?????? ;nnn | * | . | o 2.7.67 Eliminating or Changing the IND Control File | Terminating Message | For RT-11 V5.4B, 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 '@ '. | 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 | a 0. | .RUN SIPP | *IND.SAV | Segment? 0 | Base? 0 | Offset? ..INEO | Segment Base Offset Old New? | 000000 000000 ..INEO ?????? ;A | 000000 000000 ..INEO <@> ;n | 000000 000000 ..INEO+1 < > ;n | 000000 000000 ..INEO+2 <<> ;n | 000000 000000 ..INEO+3 ;n | 000000 000000 ..INEO+4 ;n | 000000 000000 ..INEO+5 ;n | 000000 000000 ..INEO+6 <>> ;n | 000000 000000 ..INEO+7 ?????? ;0 | * | . Page 22 | o Previously, the .TESTDEVICE directive incorrectly returned | off-line (OFL) status for a DM device that was logically | possible but physically nonexistent. By default, the DM | handler contains valid table entries for eight devices. If a | configuration contained less than eight DM devices, a | .TESTDEVICE directive to a nonexistent DM device incorrectly | returned OFL status rather than the correct NSD (no such | device). For RT-11 V5.4B, the .TESTDEVICE directive | correctly returns the NSD status for logically possible but | physically nonexistent DM devices. o For RT-11 V5.3, the .TESTDEVICE directive sometimes returned incorrect mounted (MTD) and unmounted (NMT) status information for logical disks. IND did not correctly track the new data table information in the LD(X).SYS file. For RT-11 V5.4, IND correctly tracks the LD(X).SYS file data tables, and the logical disk mount information returned by the .TESTDEVICE directive is correct. o Previously, the .TESTDEVICE directive incorrectly returned off-line (OFL) status for a DL device that was logically possible but physically nonexistent. By default, the DL handler contains valid table entries for two DL devices. If a configuration using the distributed DL handler included only one DL device (DL0), a .TESTDEVICE to the nonexistent DL1 device incorrectly returned OFL status, rather than the correct NSD (no such device). For RT-11 V5.4, the .TESTDEVICE directive correctly returns the NSD status for logically possible but nonexistent DL devices. o Previously, the .TESTDEVICE directive incorrectly returned the LOD (loaded) status for magtape handlers that were in fact not loaded. Other status information returned on unloaded magtape handlers was also randomly incorrect. For RT-11 V5.4, the .TESTDEVICE returns correct status information on unloaded magtape handlers. o Previously, the .TESTDEVICE directive could incorrectly return size and status information for some DU devices. That problem is corrected for RT-11 V5.4. o Previously, IND did not interpret some errors returned by PIP and DUP. Therefore, IND did not correctly process all PIP and DUP errors. For RT-11 V5.4, that error information is now mapped to IND's internal error table, and IND processes PIP and DUP errors correctly. KED/KEX o If you are simultaneously using two KED/KEX editors and you enter (and keep open) command mode on the first editor and then exit or quit the second, you cannot at that point reenter the first editor because it is still in command mode and will not accept input from the keyboard. If you attempt Page 23 to reenter the first editor, you cannot return to the background or the foreground. To free the editor and the keyboard, you must return to the editor, using the appropriate special function key (CTRL/B, CTRL/F, or CTRL/X and the editor name) and press the ESCAPE key twice. You can then press CTRL/W to repaint the screen, enter command mode to exit or quit editing that file, or use a special function key to perform other functions. LD (logical disk utility) | o LD initially loads any unloaded device containing a file you | associate with a logical disk using the MOUNT command or the | LD /L option. That association remains in effect until you | change it. However, if the device becomes unloaded, you must | load it again to access that logical disk. o For RT-11 V5.3, the LD handlers LD.SYS (appropriate for the SJ and FB monitors) and LDM.SYS (for RTEM-11) would crash the system if a MOUNT command was issued after the LD handler was loaded. The LD handler for the XM monitor (LDX.SYS) did not exhibit this problem. For RT-11 V5.4, the LD handler no longer crashes the system if mounted after being loaded. o You may need to issue the command SET LD CLEAN more than once to verify and correct nested logical disk assignments. Use the SHOW command to determine logical disk subsetting assignments and repeat the SET LD CLEAN command as necessary. o For RT-11 V5.4, attempting to nest a logical disk within the same logical disk (MOUNT LD3: LD3:foo.dsk) returns the error message, ?LD-F-Invalid nesting. o For RT-11 V5.4, nesting a logical disk within a higher-numbered logical disk (MOUNT LD2: LD3:foo.dsk) is not recommended, and for RT-11 V5.4 returns the warning message, ?LD-W-Invalid nesting. LINK o Previously, LINK did not give the correct value of zero to undefined symbols specified by the .WEAK directive in overlaid files. For RT-11 V5.4A, LINK correctly gives a value of zero to undefined symbols under those circumstances. o Previously, if you directed the binary output file to the NL device in a LINK command line, LINK failed and returned the error message, ?LINK-F-Storing text beyond high limit. LINK did not recognize that you were directing the output to the null (NL) device and failed, producing that message indicating a bad read/write error. For RT-11 V5.4, LINK does not fail when you direct binary file output to the NL device in a LINK command line. Page 24 o Previously, when link maps contained more than one page of undefined global symbols, the header information was incomplete on the second and following pages. For RT-11 V5.4, the link maps contain complete header information on all pages. | MACRO-11 | o Previously, MACRO-11 parsed arguments on .IF statements that | were within unsatisfied conditional code blocks. MACRO-11 | could return assembly errors (error code A) on lines of code | that should not have been parsed. For MACRO-11 Version 5.4, | MACRO-11 correctly keeps only a conditional nesting count and | does not parse arguments of conditional statements within | unsatisfied blocks of code. | o Previously, invalid nonprintable characters in MACRO-11 | source code were not detected and flagged as errors. For | MACRO-11 Version 5.4, invalid nonprintable characters are | detected and flagged with an 'I' error. | o Previously, the utility CREF.SAV did not produce a correct | cross-reference of a MACRO-11 program that contained more | than 999 lines of code. For MACRO-11 Version 5.4, CREF.SAV | produces correct cross-references under those circumstances. MDUP o For RT-11 V5.4, the MDUP programs no longer support the following devices: RP02/RP03, RS03/RS04, and RF11. However, the MDUP programs now support VM and devices controlled by the DU handler. If you need to create MDUP support for a device not supported in the distributed MDUPs, see Appendix A of the RT-11 Installation Guide. The text in Appendix A indicates the customization is for user-written devices. However, the customization also applies to device handlers distributed with RT-11 but not supported by the distributed MDUPs. The customization patch shows a value of 60000 for offset 1122; that produces the documented 12K words of memory when you boot the modified SJ monitor. DIGITAL recommends you use a value of 70000 at offset 1122; that produces 14K words of memory and lets you support more and/or larger devices. That value is the maximum size you can use - do not exceed the value 70000. o You cannot use the distributed MDUP programs with LSI-11 processors. Perform the following procedure to build an MDUP program that you can use with your LSI-11 processor: 1. Use the SYSGEN procedure to build an SJ monitor on your LSI-11 processor. You can use the distributed answer file SJFB.ANS to build a copy of the distributed SJ monitor. Respond Y to the second Page 25 SYSGEN dialog question and specify SJFB.ANS in response to the third question. Respond to the rest of the SYSGEN prompts. You only need to build the SJ monitor; you do not need to build device handlers for this procedure. 2. Modify that SJ monitor you built, using the procedure described in Appendix A of the RT-11 Installation Guide. Also see the information included in this section of this file, located above. Follow the rest of the procedure described in Appendix A for customizing all handlers you want to support and then build an MDUP.?? as described. 3. Use the monitor you built and modified, and the MDUP.?? file you created, with your LSI-11 processor. Use that SJ monitor only to build your MDUP.?? file, using that MDUP.SAV program; that monitor is useless for all other applications. PIP | o Previously, using any wildcard in the input file name with | the COPY/PROTECT command caused the monitor to trap to 4. | For RT-11 V5.4B, the COPY/PROTECT command works as | documented. | o Previously, the FB monitor failed to perform copy operations | from one nonfile-structured device to another | nonfile-structured device. The specific case of copy | operations from TT to TT also failed under the SJ and XM | monitors. For RT-11 V5.4B, copy operations from one | nonfile-structured device to another work as documented. o Previously, characters copied from your terminal (TT:) to an output device (such as LP:) were always copied in uppercase. For RT-11 V5.4, characters are copied from your terminal with no change in case. o Previously, if the command DELETE/QUERY filenam.SYS was included in an indirect command file, responding N (no) to the prompt returned by that command incorrectly returned the message ?PIP-W-Reboot. However, the specified file was correctly not deleted. For RT-11 V5.4, PIP does not return that message under those circumstances. | PRO/GIDIS | o Previously, when you exited from PRO/GIDIS you did not regain | the cursor. You needed to reboot your system to regain the | cursor. For RT-11 V5.4B, you regain the cursor when you exit | from PRO/GIDIS. Page 26 RESORC o For RT-11 V5.4, the SHOW CONFIGURATION command no longer displays 'Global .SCCA flag is disabled' when .SCCA support was not requested during SYSGEN. SETUP o For RT-11 V5.3, the SETUP SMOOTH command did not work on PDP-11 processors as documented. For RT-11 V5.4, SETUP SMOOTH does work as documented on PDP-11 processors. SETUP SMOOTH is not supported on Professional 300 series processors. o Previously, the SETUP GENERIC command returned an error message if you were using a PDP-11 processor with a VT200 series terminal. For RT-11 V5.4, the SETUP GENERIC command works as documented with VT200 series terminals. SIPP o When a program you specify for a SIPP session is overlaid, SIPP reads in 259(decimal) words of that program at a time. That is three words more than a single block - SIPP reads in the first three words of the next block too. If either block is a bad block, SIPP returns the error message, ?SIPP-F-Input error . If you receive that error message, issue the command DIRECTORY/BAD for that device to find the bad block. For RT-11 V5.4, SIPP reads in one block at a time when the program is overlaid and you use the /A option, or if the program is not overlaid. o Previously, if you used the /L option and the device was write locked, SIPP incorrectly returned the error message, ?MON-F-Dir IO error
. For RT-11 V5.4, SIPP works as documented and does not return that error message under those circumstances. o Previously, if you used CCL command mode to run SIPP and included the checksum option (/C), the checksum prompt was not returned and SIPP saved none of the modifications. For RT-11 V5.4, when you use CCL to run SIPP and include the checksum option, the command works as documented. | SL (Single-Line Editor) | o Previously, SL stored up to two previous commands on its | stack (list) of commands. For RT-11 V5.4B, SL can store up | to one block (512 bytes) of previous commands on its stack of | commands. That stack can be thought of as a vertical list of | commands, with the most recent command placed at the bottom. | You use the up-arrow key to recall previous commands by | scrolling up through the stack. You use the down-arrow key | to scroll back down through the stack of commands. You press Page 27 | RETURN to enter any command displayed. Entering a command | returns you to the bottom of the command stack. | o Previously, you saved a command by pressing the | key sequence, and recalled that saved | command by pressing the key. That functionality | is called SAVE and GET SAVE. For the V5.4B version of SL, | you use the key sequence to save a command. Use the | key sequence to recall that saved command. The | characters S and X are located on your main keyboard and are | not case sensitive. | o For RT-11 V5.4B, you can use SL to store a command line | offset into the command stack and then repeatedly recall the | successive commmands. That functionality is called SET CYCLE | and CYCLE and is especially useful when you are repeating a | sequence of commands. | For example, in debugging a MACRO-11 program, you might | continually issue the commands EDIT filename, MACRO filename, | LINK filename, and RUN filename. Once you had issued those | commands, RUN filename would be the first command on your | stack and EDIT filename would be fourth. Rather than | continually look for those commands, you could use SET CYCLE | and CYCLE to recall and reenter them in the following manner: | 1. Press the key until you return to the | command EDIT filename. Press the | key sequence to store that offset into your command | stack. Press RETURN to EDIT that file. | 2. When done editing, press to recall | the next command in the cycle, MACRO filename. Press | RETURN to assemble that file. | 3. Continue that sequence to LINK and RUN that file. | 4. Pressing again recalls the first | command in the cycle, EDIT filename. You can | continue to use this command cycle until you alter | the cycle by entering another command. | o For RT-11 V5.4B, you can use the keypad to edit KMON commands | when you have set the SL editor by issuing the following | command: | .SET SL KED | Issue that command before you turn on SL by issuing the SET | SL KMON command. A display showing keypad key functions for | SL keypad mode Page 28 | is located in the RT-11 V5.4B HELP utility. You can display | that information by typing in response to the monitor prompt | (.): | .HELP SL | The key continues to display general SL help | information. | The following paragraphs describe using the SL editor's | keypad mode: | In keypad mode, you use the keypad to edit KMON commands | as you would from within the KED editor. Use the KED | keypad functions appropriate for editing text within a | single line. | There is a direct correlation between the KED editor and | keypad mode under SL in the concept of single character | (<3>) functions and line (<0> and <2>) functions. | However, the SL editor in keypad mode uses an enhanced | concept of the word (<1>) function. To SL, a word can | be thought of as an element in the command syntax. The | elements in command syntax are the file name, the file | type or extension, any options you specify, and any | arguments to those options. You use the word function | key to move forward or backward through the elements of | a KMON command. | You use the forward (<4>) and reverse (<5>) function | keys to establish a direction of motion when moving the | cursor through single characters (<3>), command elements | (<1>), or complete command lines (<0>). For example, | pressing the sequence <5><0> moves the cursor to the | beginning of the command line. Pressing again the | beginning-of-line (<0>) function key moves the cursor to | the beginning of the previous command on the stack. You | can use forward and reverse functions and the | beginning-of-line (<0>) or end-of-line (<2>) function | key to scroll through the commands on the stack. | You can use the <,> key to delete a single character, | use the <-> key to delete a single command element, or | use the key to delete the complete command line - | just as you would with the KED editor. You can also use | and the appropriate key to undelete - again, just | as with KED. (You can use the delete line function | () and the undelete line function () to | save and recall a command. You save the command by | 'deleting' it and later recall the command by | 'undeleting' it.) | The keypad keys marked 6, 7, 8, and 9 are not | implemented. Page 29 | o For RT-11 V5.4B, 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 typing CTRL/A. | SL returns to INSERT mode at each command line. | SLMIN (Minimum functionality Single-Line Editor, SJ and FB only) | o SLMIN for V5.4B supports only those functions contained in | previous versions of SLMIN. However, changes have been made | to SLMIN to make its limited functionality consistent with SL | for V5.4B. For example, the SAVE and GET SAVE functions use | the V5.4B key sequences and . Also, you no | longer press to recall the | command-before-last, but rather press twice. SPLIT o When you use the SPLIT /2 option, the block allocation on the output volumes is determined by the standard RT-11 file size allocation algorithm; one-half of the largest free area. That could cause SPLIT to fail because of insufficient size. Therefore, when you use the /2 option, you should include the [-1] optional size specification after each output file specification. That lets SPLIT use the maximum blocks available on the output volumes. For example, the following command splits the file TEST.TXT, located on device DK, into two files: TESTA.TXT located on device DZ0 and TESTB.TXT located on device DZ1: .SPLIT DZ0:TESTA.TXT[-1],DZ1:TESTB.TXT[-1]=TEST.TXT/2 SPOOL | o Previously, the time-of-day string was not printed on | flagpages when the SP handler was not loaded and you were | running under the XM monitor. For RT-11 V5.4B, SPOOL | supports time-of-day functionality under XM without requiring | that the SP handler be loaded. o If you wish to use VM as the work device for SPOOL, you should attach VM to SPOOL. However, that makes VM unavailable for other use. The following series of commands lets you attach VM as the work device for SPOOL, but still makes VM available for other use. These commands can Page 30 be included in your start-up command file, but if you include them, be sure to remove or disable any current commands you use to start SPOOL. ASSIGN LS: SO0: ASSIGN VM7: SFD: FRUN SPOOL/PAUSE LOAD LS:=SPOOL LOAD VM7:=SPOOL ASSIGN SP: LP: ASSIGN SP0: LP0: RESUME SPOOL | (VM does not recognize unit numbers. However, specifying a | unit number for VM in the commands above lets the RT-11 | monitor assign more than one function to VM.) SRCCOM o Previously, the DIFFERENCES command with the /OUTPUT:filespec option could produce a corrupted output file when wildcards were used for input file names. For RT-11 V5.4A, a corrupted output file is not produced under those circumstances. SYSGEN | o Previously, SYSGEN generated incorrect symbol names (system | conditionals) for the second, third, and fourth CSR and | VECTORs for TMSCP magtape units. For RT-11 V5.4B, SYSGEN | generates correct symbol names as documented in the RT-11 | System Release Notes, Section 2.34.3. o The LINK command line for the DW handler in the indirect command file that SYSGEN creates to build devices has been modified for RT-11 V5.4 to the following: LINK/NOBITMAP/EXE:BIN:DWX.SYG/BOUNDARY:512. OBJ:DWX SETOVR o Previously, if SYSGEN needed to load a device handler, that device handler was not unloaded at the end of the SYSGEN procedure. For RT-11 V5.4, SYSGEN unloads any device handlers that it loaded. UCL | o It is a documented restriction that you cannot call indirect | files (@filename) in a command definition. The keyboard | monitor (KMON) preprocesses characters following an @ sign | for expansion as part of its command processing. However, | you can edit the UCL data file to place the @ (or $@) sign | ahead of an indirect file name and thereby bypass the KMON | preprocessing. Page 31 | For the purpose of this example, assume you want to create a | command named DO that will run the start-up command file | STARTX.COM. Because STARTX.COM is an indirect command file, | you want to include the prefix $@. Use the following | procedure to enable UCL to run STARTX.COM when you type the | command DO: | 1. Place the following command syntax in your UCL data | file: | DO :== $$STARTX.COM | 2. You must now edit your UCL data file to replace the | $$ prefix on STARTX.COM with the $@ prefix. Assuming | KED (or KEX) is your default editor and UCL.DAT is | your UCL data file, issue the command: | .EDIT UCL.DAT | 3. Use the KED advance-one-word keypad sequence (<4><1>) | to advance through your UCL data file until the | cursor rests at the beginning of the word | $$STARTX.COM. | 4. Advance the cursor two characters, delete the $ sign | and replace it with an @ sign. The word should now | appear as $@STARTX.COM. | 5. Exit from KED. Now, when you type the command DO in | response to the monitor prompt, you run the indirect | command file STARTX.COM. | If the indirect file you want to run is an IND indirect | control file, for example, FOO.COM, you would enter the UCL | command as: | DO :== $FOO.COM | Using the procedure described above, you would edit your UCL | data file to change the $ sign to an @ sign. The command DO | would then run the IND control file named FOO.COM. o For RT-11 V5.4, you can create and issue UCL commands in upper-, lower-, or mixed case. The case you use to create the UCL command is stored (as entered) in the UCL data file, and the command's case is passed to KMON in the chain area as stored. o Previously, UCL did not consider a command containing an asterisk (minimum abbreviation character) as a valid replacement for the same command that did not contain the asterisk. UCL did not clear the replaced command. For RT-11 V5.4, UCL clears the replaced command under those circumstances. Page 32 VTCOM o To run VTCOM.REL under XM is inefficient; you should run VTCOM.SAV. For RT-11 V5.4, if you run VTCOM.REL under the XM monitor, VTCOM returns the message, ?VTCOM-W-Use XM version, VTCOM.SAV. o If you attempt a VTCOM operation that uses a volume that is invalid (not initialized, for example), VTCOM returns the error message, ?VTCOM-F-Invalid directory. Make the volume a valid RT-11 volume and retry the VTCOM operation. o Previously, the modem's Clear To Send signal controlled whether VTCOM reported a connection as established or lost. For RT-11 V5.4, the Carrier Detect signal controls the status of the connection report. The connection report is the same and remains valid for all supported modems. 3.4 DEVICE HANDLERS CT o Previously, the CT handler would install on all processors under all monitors whether or not a TU60 cassette device was in fact in the configuration. For RT-11 V5.4, the CT handler will only install if the required hardware is present at the correct CSR. DD, DL, DM, DU, DW, DX, DY, DZ, MM, MS, MT, MU, RK o Previously, valid values for the SET dd: RETRY=n command for the device handlers above were varied. For RT-11 V5.4A, valid RETRY values for all the device handlers above are 1 through 127(decimal). The default number of retries for the device handlers above is 8. DD o Previously, when running under the XM monitor, attempting to access files on an unloaded TU58 DECtape II could crash the system. For RT-11 V5.4, accessing files on an unloaded TU58 returns the error message, ?MON-F-Unloaded driver
, and does not crash the system. DL, DM o Previously, the DL and DM handlers did not check .READx/.WRITx requests from a non-file-structured .LOOKUP to determine if they correctly accessed replaced blocks only through the bad-block replacement table. For RT-11 V5.4, the DL and DM handlers reject any attempt to access replaced blocks other than through the bad-block replacement table and return the carry bit set. Note that special function Page 33 (.SPFUN) reads and writes continue to directly access any block on the device. o Previously, when you issued the COPY/DEVICE/RETAIN command to the DL and DM handlers, those handlers incorrectly read two blocks beyond the data area on the input volume. DL and DM then wrote those two blocks to the first two replaced blocks on the output volume, thereby corrupting those first two blocks. For RT-11 V5.4, the DL and DM handlers only read from and write to the data area when you use the COPY/DEVICE/RETAIN command. o Previously, some invalid SPFUN codes directed to DL and DM could cause a default action to occur. For RT-11 V5.4, all invalid SPFUN codes directed to DL and DM are correctly ignored. DU o If the system crashes while the DU handler (DUX.SYS) is performing bad-block replacement on a disk, restarting the system and accessing that disk should cause the DU handler to recover bad-block replacement information and complete the bad-block replacement. Previously, that process did not work correctly. For RT-11 V5.4A, that process works correctly. o Previously, if a bad block occurred during a special MSCP BYPASS recovery operation (.SPFUN 360 with blk argument set to 1) and the DU handler was responsible for bad-block replacement, bad-block replacement did not occur. DU attempted to replace a different block that might or might not be bad. That attempt was not always successful and could crash the system. For RT-11 V5.4A, DU correctly replaces bad blocks during a special MSCP BYPASS function. o For RT-11 V5.4A, DU displays the following error message if bad-block replacement on a device is performed by the DU handler and DU is unable to replace a block on that device: ?DU-E-Replace command failure. ?DU-E-Software write protecting volume. If you receive that message, you should immediately close any open files and back up that volume. Then check any file you had open for lost data. You cannot write to that volume again without first taking it off line and then placing it on line. o For RT-11 V5.4, the command SET DU SUCCES works as documented. o For RT-11 V5.4, you can issue the command SET DUx PORT=0 when you have a single port DU configuration. That command no Page 34 longer returns an error message in a single port configuration. | DZ | o Previously, the DZ handler wrapped unit numbers such that an | operation directed to DZ4 would wrap to DZ0, DZ5 would wrap | to DZ1, and so on. For RT-11 V5.4B, the DZ handler no longer | wraps unit numbers. LP/LS o For RT-11 V5.4, the LS handler is distributed with support for both PRO and PDP-11 processors. The SYSGEN conditionals that enable that support are LS$PC=1 for the PRO and LS$PDP=1 for the PDP-11 processors. You can build an LS handler for only the PRO by requesting PC300 printer port support and also including the conditional LS$PDP=0 after replying Y to the SYSGEN prompt - Do you want to define or redefine any system conditionals (N)?. You can also build an LS handler for only PDP-11 processors by requesting no PC300 printer port support in the SYSGEN dialog. o For RT-11 V5.3, the SET LS CSR=nnnnnn command required the default system generation PC300 printer port support. That support was included in all distributed monitors. For RT-11 V5.4, the SET LS CSR=nnnnnn command works as documented with all LS handlers except those generated for only PC300 printer port support during system generation. The CSR and vector addresses for the Professional 300 series processors are fixed by the hardware and cannot be set. Magtape Handlers (MM,MS,MT,MU) The following information applies to all magtape handlers. Information about specific magtape handlers is listed under the particular handler name. o Magtape devices require that you close channels rather than just deactivate them when you terminate your program. DIGITAL recommends you use the .CLOSE request before you terminate a program that performs I/O operations to any RT-11 magtape device. Some RT-11 utilities (such as BUP) use the .PURGE request to deactivate a channel at program termination; that is appropriate for I/O operations to a disk device. You should LOAD some magtape handlers before they are used with utilities such as BUP. If you LOAD your magtape handler and you use a utility that performs a .PURGE, that utility can return an error message at the next attempted magtape access because the channel has not been closed. You can clear that Page 35 error condition by UNLOADing and then again LOADing the magtape handler. If a program does not require you to LOAD the magtape handler, then let the program .FETCH the handler. A .FETCH always loads a new copy of the handler into memory and therefore corrects any channel problem caused by a .PURGE request at program termination. | MM | o Previously, the MM handler could occasionally cause a system | crash or a monitor trap to 4 condition when a hard error | occurred during a write (.WRITE or .SPFUN 371) operation. | For RT-11 V5.4B, the MM handler responds correctly by | performing recovery or returning a hard error code under | those circumstances. MQ o Previously, the MQ handler used only the .READx wcnt parameter value to determine the size of a data transfer. A mismatch between the wcnt parameter value for a .WRITx and a .READx request could cause data or code corruption. For RT-11 V5.4, the MQ handler uses the smaller of the .READx and .WRITx wcnt parameter values to determine the data transfer size, and memory corruption can no longer occur under those circumstances. MS o RT-11 V5.3 corrected a problem in which a double CTRL/C issued to a program using the MS magtape while it was in motion could cause the system to hang. That problem was caused by MS attempting to dismiss queue elements already dismissed by the monitor. | MT | o Previously, the MT handler could occasionally cause a system | crash or a monitor trap to 4 condition when a hard error | occurred during a write (.WRITE or SPFUN 371) operation. For | RT-11 V5.4B, the MT handler responds correctly by performing | recovery or returning a hard error code under those | circumstances. Page 36 MU | o For RT-11 V5.4B, the MU handler recognizes the following SET | commands: | MUn: DEFALT Returns magtape unit n to default | density of 6250 bits/in. Valid only | with 9-track TMSCP magtapes and sets | only the specified magtape unit. | DENSE=1600 Sets density for only 9-track TMSCP | =6250 magtapes and for only the specified | magtape unit. Setting DENSE=1600 | specifies 1600 bits/in (phase | encoded). Setting DENSE=6250 | specifies 6250 bits/in (group code | recording). | PORT=x Defines which port to access when | magtape unit n is specified. The | variable x is an integer in the | range 0-3 and corresponds to the | variable x used with the SET MU | CSRx=n and SET MU VECx=n commands. | By default, the port variable x is | the same as the magtape unit n. | Valid only if the handler is | assembled for multiple ports | (units). | UNIT=x Defines which TMSCP unit number to | access when magtape unit n is | specified. The variable x is an | integer in the range 0-255. The | default value for x is 0. Since | each TMSCP unit requires a | controller, this modification is | optional and is used only if you | have multiple TMSCP devices and you | have modified the unit number on the | device front panel. | o The MU handler initializes the port interface between the | processor and the TMSCP magtape controller when you use the | drive for the first time, or when a new magtape is mounted. | Previously, aborting magtape operations by typing double | CTRL/C during that port initialization procedure could hang | your system. For RT-11 V5.4B, aborting the port | initialization does not hang your system. You can, however, | experience a delay of up to 90 seconds before receiving the | monitor prompt after aborting port initialization. | o Previously, aborting magtape operations by typing double | CTRL/C while the system was .FETCHing or LOADing the MU Page 37 | handler could halt your system. For RT-11 V5.4B, you can | successfully abort operations under those circumstances. o Previously, the MU handler did not report EOT (end-of-tape) until the physical end-of-tape was reached with Write, Write Tape Mark, and Space Forward operations. For RT-11 V5.4A, the MU handler correctly reports EOT when it encounters the end-of-tape mark. o Previously, you could crash the system if you issued the BACKUP command to MU under XM when MU was not loaded and you then typed CTRL/C in response to the initial BUP console prompt. For RT-11 V5.4A, typing CTRL/C under those circumstances correctly exits BUP and does not crash the system. o Previously, you could hang the MU handler if it was loaded in memory and an error caused the unit status to change to 'off-line'. For RT-11 V5.4A, the MU handler does not hang under those circumstances. o Through the SYSGEN process, you can generate an MU hardware handler that does not contain the file-structure module (FSM). Also, through SYSGEN, you can generate support for up to four device units. Previously, the hardware handler incorrectly marked as valid those device units not requested during SYSGEN. Attempts to access invalid device units could halt or hang the handler and crash the system. The MU handler controller revision checking program, MSCPCK.SAV, attempted to check all units not marked as invalid and therefore could halt or hang the hardware MU handler. For RT-11 V5.4A, the MU hardware handler correctly marks as valid only device units for which support is requested during SYSGEN. XC/XL | o For RT-11 V5.4B, the XC and XL handlers refuse to be unloaded | until you pause or exit from VTCOM. o For RT-11 V5.4, additional functionality has been added to SPFUN 204 so that it now returns the following modem control information in bits 3 and 4 of the low byte of the user buffer: Bit Meaning 3 Set indicates Carrier Detect is high (on); clear indicates Carrier Detect is low (off) 4 Set indicates Ring Indicator is high (on); clear indicates Ring Indicator is low (off) Page 38 Because of changes made to SPFUN 204, the driver support level value returned in the high byte of the user buffer is now 18(decimal) rather than 17(decimal). 3.5 PROCESSORS AND PERIPHERAL DEVICES CACHE-BYPASS o RT-11 V5.4A includes new cache-bypass functionality for processors that share memory over the Q-bus. Use the cache-bypass functionality to ensure that data read from shared memory is read from that shared memory and not the processor's hardware memory cache. Using the cache-bypass functionality does not eliminate use of the processor hardware memory cache for other purposes such as nonshared memory references. Use the following information to enable the new cache-bypass functionality: - Only global regions can possess the cache-bypass attribute. Therefore, you must assign all or a portion of your shared memory to a global region. Any local region attached to a global region shares the cache-bypass attribute of that global region. Any local region not attached to a global region has cache-bypass set off. - The following bit definitions are new and control the cache-bypass attributes of a global region: Symbol Value Location and Meaning When Set ------ ----- ----------------------------- RS.CAC 100 Bit 6 of R.GSTS (byte offset 4 of region definition block). Enable cache-bypass. RS.BAS 40 Bit 5 of R.GSTS (byte offset 4 of region definition block). Explicitly assign base address for this global region. RS.NSM 20 Bit 4 of R.GSTS (byte offset 4 of region definition block). Explicitly assign base address for this global region above system memory. GR.CAC 20 Bit 4 of GR.STA (byte offset 4 of global region control block). Cache-bypass is enabled for global region. Page 39 R.CACH 10 Bit 3 of R.BSTA (byte offset 4 of region control block). Local region is attached to a global region with cache-bypass set. - The following information describes the use of those bits to enable cache-bypass: Use the new base=n parameter in the .RDBBK macro to assign the shared memory global region base address at each processor to the same value. Using the base=n parameter (with n nonzero) also sets RS.BAS in the region status word (R.GSTS). If that shared memory region resides above system memory, you must also specify RS.NSM in the rgsta parameter of .RDBBK. (You can use RMON fixed offset 420, $MEMSZ, to find the top of system. See Section 3.6 of this file for more information on using the .RDBBK macro base=n parameter. Specify RS.CAC in the rgsta parameter of .RDBBK. Specifying RS.CAC causes GR.CAC in the global region control block to be set when the global region is created using the .CRRG request; otherwise, GR.CAC is cleared. When .CRRG is processed, R.CACH is initially cleared. If .CRRG is for attachment to or creation of a global region, GR.CAC is copied to R.CACH. Mapping operations (.MAP request or the .CRAW request with WS.MAP specified) set bit 15 in all PDRs used to map the region that has cache-bypass enabled. See Chapter 4 of the RT-11 Software Support Manual for information on global regions. - The following program fragment illustrates the code necessary to use cache-bypass. It attaches a local region to a global region named SHARED with a size of 20000 bytes and a base address of 1000000. The size and base in the fragment are expressed in 32-word blocks. The rgsta parameter RS.CGR creates the global region SHARED if it is not already resident in memory. The rgsta parameter RS.CAC causes caching to be bypassed for all mapped windows using this region. You should perform a similar operation, using the same values and symbols for any processor using this shared memory: AREA: .BLKW 2 RDB: .RDBBK RGSIZ=200,RGSTA=, NAME=SHARED,BASE=10000 . . .CRRG #AREA,#RDB Page 40 LA75 Printer o For RT-11 V5.4, the LA75 printer is supported in the same manner as current LA50 printer support. That is, the LA75 responds to the same (and only) SET conditions and SETUP modes as an LA50. TK50 Magtape o The RT-11 V5.4 program, MSCPCK.SAV, checks the TQK50 Q-bus controller for its rev level. If the TQK50 controller is below rev level, the MU handler installs and MSCPCK.SAV returns the error message, ?MSCPCK-W-TQK50 controller below FW Rev 4/HW Rev 6. If you receive that message, contact your local DIGITAL field service representative. Reliable TK50 operation on Q-bus processors requires a controller of at least firmware revision 4 and hardware revision 6. 3.6 SYSMAC.SML (System Macro library) .RDBBK o A new optional fourth parameter, BASE=n, is added to the .RDBBK macro for RT-11 V5.4A. Use the BASE=n parameter to explicitly assign a base address to a global region. Because the BASE=n parameter is optional, you do not need to modify existing programs unless you want this new functionality. The .RDBBK macro now has the following syntax: Macro Call: .RDBBK rgsiz,rgsta,name[,base=n] where: base is the starting address of the region expressed in 32-word units. A value of 0 or omitted means any available base address is acceptable You cannot assign a base address value for a local region. Use the .CRRG request to assign the base address for a global region before you create that global region. If you assign a base address value for a global region that already exists at another base address, .CRRG returns error code 16 in ERRBYT and sets the carry bit: 16 Global region already exists at a different base address The base=n parameter sets a new bit 5 (RS.BAS) in the region status word only when you specify a nonzero value for n. You can use the base=n parameter to assign the starting Page 41 address of a global region above system memory. (You can use RMON fixed offset 420, $MEMSZ, to find the top of system memory.) You must specify a new symbol, RS.NSM, in the .RDBBK macro's rgsta parameter. Specifying RS.NSM sets bit 4 (value 20) in R.GSTS of the region definition block and also causes bit 5 (GR.NRF) in the global region control block status byte (GR.STA) to be set. GR.NRF stops return of the global region's allocated memory to the system free memory list when that global region is eliminated. No error checking is performed when the base=n parameter is used in this manner. o For RT-11 V5.4A, a sixth word (R.GBAS) has been added to the region definition block set up by the .RDBBK macro. R.GBAS resides at offset 12(octal), immediately following R.NAME. R.GBAS contains the base address for the global region described by that region definition block. The structure of a region definition block is now: +---------------+ | R.GID | 0 +---------------+ | R.GSIZ | 2 +---------------+ | R.GSTS | 4 +---------------+ | R.NAME | 6 + + | | 10 +---------------+ | R.GBAS | 12 +---------------+ R.GBAS is referenced by the monitor only when the RS.BAS bit is set. RS.BAS is set only when you specify a nonzero value for n in the new BASE=n parameter. Therefore, you do not need to modify existing programs because of this new word. | .READ/.READC/.READW | o If you are using the .READ, .READC, or .READW programmed | requests under the SJ monitor, read the restricion at the | beginning of Section 4.0 of this file. | .SPFUN | o If you are using the .SPFUN programmed request under the SJ | monitor, read the restriction at the beginning of Section 4.0 | of this file. | o Previously, directing a .SPFUN 373 to a logically possible | but physically nonexistent DM device did not return an error. | Instead, it returned an incorrect size. For RT-11 V5.4B, | directing a .SPFUN 373 to a logically possible but physically | nonexistent DM device correctly returns and error. Page 42 .SAVESTATUS o For RT-11 V5.4, you can use the .SAVESTATUS request for a device channel that is opened with the .ENTER request, so long as that device is both special directory structured and write only. The .ENTER request remains an invalid way to open a channel for which you intend to use .SAVESTATUS for all other types of devices. You can also use the .LOOKUP request and .SAVESTATUS for special directory-structured devices, so long as the device is write only. A device is recognized as special directory structured and write only when the SPECL$ and WONLY$ bits are set in the $STAT entry table in the resident monitor (RMON). For RT-11 V5.4, the only devices that are special directory structured and write only are LP, LS, and SP. | .WRITE/.WRITC/.WRITW | o If you are using the .WRITE, .WRITC, or .WRITW programmed | requests under the SJ monitor, read the restriction at the | beginning of Section 4.0 of this file. 3.7 SYSLIB (System Subroutine Library) | REMOVED FUNCTIONS AND SUBROUTINES | The following functions and subroutines have been removed from | the distributed RT-11 system subroutine library, SYSLIB. They | were specific to FORTRAN programming and did not work without | a resident FORTRAN OTS. They have been added to the FORTRAN | IV distributed FORLIB and the FORTRAN-77 distributed F77OTS. | GETSTR IFREEC INTSET | IASIGN IGETC IQSET | ICDFN IGETSP PUTSTR | IFETCH ILUN SECNDS | DATE | o RT-11 V5.4B adds the DATE subroutine to SYSLIB. Previously, | the DATE subroutine was located in the distributed FORTRAN | subroutine libraries, FORLIB and F77OTS. Page 43 | The DATE subroutine obtains the current (system) date. The | current date is stored as a nine-byte string in the form: | dd-mmm-yy | where: | dd is the two-digit day of the month (with | leading zero if necessary) | mmm is the three-digit month (all capital letters) | yy is the last two-digits of the year | - is the separating character | Form: CALL DATE (array[(i)]) | Where: | array is a predefined array that contains at least | nine bytes. The nine-byte string is set to | blanks if system date has not been set | i specifies which element of that array contains | the first element of the string | IDATE | o RT-11 V5.4B adds the IDATE function to SYSLIB. Previously, | the IDATE function was located in the distributed FORTRAN | subroutine libraries, FORLIB and F77OTS. | IDATE returns three INTEGER*2 values representing the current | (system) month, day, and year. | Form: CALL IDATE(i,j,k) | Where: | i is an INTEGER*2 variable containing an integer | representation of the month. January is | represented as 1. December is represented as | 12. Returned as zero if the system date has | not been set | j is an INTEGER*2 variable containing the | integer day of the month | k is an INTEGER*2 variable containing the last | two integer numbers of the year Page 44 ICHCPY o Previously, ICHCPY incorrectly interpreted the optional jobblk parameter. A value specified for the first word of jobblk was incorrectly used as the location of the string rather than correctly as the first word of the string itself. For RT-11 V5.4, the ICHCPY subroutine works as documented. IGETR o Previously, IGETR could not be called from a FORTRAN program. Also, numerous problems occurred in the code with information mapping, sizing, and channel operations. For RT-11 V5.4, IGETR works as documented. See Section 3.8.6 of this file for more information and an example program using IGETR. JREADF o RT-11 V5.4 provides the JREADF variant of the JREAD function. The JREADF function transfers into memory a specified number of words from the indicated channel. The monitor returns control to the user program immediately after the JREADF function is initiated. When the operation is complete, the monitor enters the specified FORTRAN subprogram (crtn) as an asynchronous completion routine. (See Section 1.2.1.2 of the RT-11 Programmer's Reference Manual for information on completion routines.) Form: i = JREADF (wcnt,buff,jblock,chan,[area],lblk,crtn) where: wcnt, buff, jblock, chan, and area are the same as the JREAD function lblk is a 4-word area to be set aside for link information; this area must not be modified by the FORTRAN program or swapped over by the USR. This area can be reclaimed by other FORTRAN completion functions when crtn has been activated crtn is the FORTRAN routine to be activated on completion of the transfer. This name must be specified in an EXTERNAL statement in the routine that issues the JREADF call Errors: The return codes are the same as for JREAD, except 0 (and not n) is the normal return. Page 45 JWRITF o RT-11 V5.4 provides the JWRITF variant of the JWRITE function The JWRITF function transfers a specified number of words from memory to the specified channel. The monitor returns control to the user program immediately after queuing the request. When the transfer is complete, the monitor enters the specified FORTRAN subprogram (crtn) as an asynchronous completion routine. (See Section 1.2.1.2 of the RT-11 Programmer's Reference Manual for information on completion routines.) Form: i = JWRITF (wcnt,buff,jblock,chan,[area],lblk,crtn) where: wcnt, buff, jblock, chan, and area are the same as the JWRITE function. lblk is a 4-word area to be set aside for link information; this area must not be modified by the FORTRAN program or swapped over by the USR. This area can be reclaimed by other FORTRAN completion functions when crtn has been activated crtn is the FORTRAN routine to be activated on completion of the transfer. This name must be specified in an EXTERNAL statement in the routine that issues the JWRITF call. Errors: The return codes are the same as for JWRITE, except 0 (and not n) is the normal return. MRKT o Previously, MRKT incorrectly interpreted the id parameter. The value specified for the id parameter was incorrectly interpreted as the address of the id parameter rather than correctly as the id parameter itself. Now, the MRKT subroutine works as documented. | RAN/RANDU | o RT-11 V5.4B adds the RAN function and RANDU subroutine | uniform pseudorandom number generators to SYSLIB. | Previously, RAN and RANDU were located in the FORTRAN IV and | FORTRAN-77 object time system libraries. | RAN and RANDU generate a floating-point number that is evenly | distributed in the range between 0.0 inclusive and 1.0 Page 46 | exclusive (1.0 is never generated). | You supply a 32-bit seed number, and that seed number is | automatically updated according to the following: | SEED = 69069 * SEED +1 (MOD 2**32) | The value of SEED is a 32-bit number. The high-order 24 bits | of SEED are converted to floating point and returned as the | result (f). | Form: f = RAN (jseed) | or: | f = RAN (iseed1,iseed2) | or: | CALL RANDU(iseed1,iseed2,f) | Where: | f is a 24-bit real, floating-point, random | number | jseed is an INTEGER*4 seed number | iseed1 is the low-order seed word | iseed2 is the high-order seed word | RAN and RANDU are multiplicative congruential general random | number generators. They are fast, but prone to nonrandom | sequences if you construct and analyze triples of generated | numbers. | Note that RAN and RANDU are different from the routines | previously supplied with FORTRAN IV. They are the same as | the default routines previously supplied with FORTRAN-77. | There are no restrictions on the seed. The seed should be | initialized to different values on separate runs to obtain | different random sequences. | Example: | This example illustrates a simple way to get a uniform | random integer selector. Multiply the value returned by Page 47 | the RAN function by the number of cases - in this | example five. | GO TO (1,2,3,4,5), (1 + IFIX(5.*RAN(JSEED))) | The explicit IFIX is necessary before adding 1 to avoid | possible rounding during the normalization after the | addition of floating-point numbers. 3.8 DOCUMENTATION CORRECTIONS 3.8.1 RT-11 System Release Notes - o Section 1.5.3.6, .DREST The release notes incorrectly state on page 1-19 that the replace argument information is stored in word 22 of block 0 in the handler. In fact, the replace information is stored in word 32 of block 0. o Section 1.5.4.10, JREAD/JREADC/JREADW, contains inaccurate information about the error codes returned for JREAD and JREADC. The normal return for JREAD and JREADC is 0 and not n. JREAD and JREADC cannot return the value for n because the monitor returns control to the user program immediately after they are initiated. JREADW does return n as the normal return because the monitor returns control to the user program at completion of the subroutine. The rest of the section is correct. o Section 1.5.4.11, JWRITE/JWRITC/JWRITW, contains inaccurate information about the error codes returned for JWRITE and JWRITC. The normal return for JWRITE and JWRITC is 0, and not n. JWRITE and JWRITC cannot return the value for n because the monitor returns control to the user program immediately after they are initiated. JWRITW does return n as the normal return because the monitor returns control to the user program at completion of the subroutine. The rest of the section is correct. o Section 3.1.6, Utility Restrictions The LD restriction on page 3-6 incorrectly illustrates the recursive logical disk rule. The example, MOUNT LD2: LD3:FOO.DSK, is incorrect. In fact, the following example obeys the recursive logical disk rule: MOUNT LD3: LD2:FOO.DSK Page 48 o Section 3.4.4, RT-11 Software Support Manual changes and additions, contains inaccurate information in the addition to Section 10.15.1, (MU) Use of Special Functions. The buf parameter is inaccurately indicated as 0 (unused). In fact, the buf parameter is the address of the 52(decimal) word TMSCP area. o Appendix C, Section C.3.2, A Working System for Performing a SYSGEN, contains an inaccurate value setting for VM. The second command line in the file VMGEN.COM you create should read: SET VM BASE = 4000 Setting that value (instead of 5000 as documented), provides enough MACRO work file space to successfully run the SYSGEN build files. 3.8.2 RT-11 System User's Guide - | o Section 5.2.1.3, Suppress Console Display Option (/Q) | This section inaccurately states that the /Q option | suppresses the display of keyboard commands and their results | as IND executes the keyboard commands. In fact, the /Q | option only suppresses keyboard commands; the /Q option does | not suppress the results of keyboard commands. 3.8.3 RT-11 Installation Guide - | o Modifying the Help Text (Section 2.7.14) | The command to merge the HELP program (.EXE) and library | (.MLB) located above the last paragraph of this section | should read: | .COPY/CONCATENATE HELP.EXE,HELP.MLB HELP.SAV | o Preserving the Working System (Section 8.9) | The command to initialize an MU magtape is incorrect. The | file MUBOOT.BOT does not exist. The following is the correct | procedure to initialize an MU magtape: | .INITIALIZE/FILE:MSBOOT.BOT MU0: | MU0:/INITIALIZE; Are you sure? Y | . Page 49 3.8.4 Introduction to RT-11 - o Chapter 5, Creating and Editing Text Files, demonstrates the EDIT hard-copy editor. That editor is no longer the default RT-11 editor. Therefore, to start the EDIT editor, you must either SET EDIT EDIT and then issue the EDIT command or issue the command RUN EDIT (or R EDIT). 3.8.5 RT-11 Software Support Manual - o Section 3.5.7, Message Handling, should contain the following information about FB monitor support for message transfers: The distributed FB monitor only supports using the .SDAT/.RCVD/.MWAIT requests to transfer messages. You must build (SYSGEN) an FB monitor and request system job support (or use XM) to transfer messages, using the system job lookup macro (.LOOKUP) and the standard I/O requests. (You can also continue to use the .SDAT/.RCVD/.MWAIT requests to transfer messages between the foreground and background programs when you run any FB or XM monitor.) | o Section 5.14, Multi-Terminal Example Program, contains code | in two places that can cause the program to fail. | The code between symbol 6$: and symbol LOGLUN: should be | changed to the following: | 6$: BIS #,@R3 | MOV #ENDTBL,R4 | MOV #32,LOTIM ;Inserted line | CALL TERMID | CALL RSET | BR 3$ | The line at symbol UNKTT: on the last page of the example | program should be coded for 5 spaces before the text: | UNKTT: .ASCII / unidentifiable terminal/<200> | The rest of the program is correct. o Section 7.8.2, How to Support Special Functions in a Device Handler, incorrectly states in the fourth paragraph that you should return a hard error for invalid special function codes. In fact, device handlers should simply ignore invalid special function codes. o Section 11.2.3, Device Attributes (DA), incorrectly states the form of SETUP VT100 DA response and the secondary DA response for FB and XM monitors. Page 50 If the terminal is SETUP VT100, the correct DA responses are: When running under the FB monitor: [?1;1c When running under the XM monitor: [?1;3c The following are the correct forms for the secondary DA response: For the FB monitor, the response is of the form: [>7;VVNNc where VV is the version and NN is the edit level. For the XM monitor, the response is of the form: [>8;VVNNc where VV is the version and NN is the edit level. The rest of the information in Section 11.2.3 is correct. 3.8.6 RT-11 Programmer's Reference Manual - Completion Routines (Section 1.2.1.2) o The following information concerns possible stack overflow under the FB and SJ monitors when you use a subroutine that calls a completion routine. If your program is using a subroutine that calls a completion routine and you receive the message, ?MON-F-Trap to 4 (under the FB monitor) or ?MON-F-Stack overflow (under the SJ monitor), you should relink your program and increase its stack size. You increase the stack size of your program by raising the program base address, using the LINK /BOTTOM:value option. By default, LINK places the program base address at 1000(octal). Raise the base address and thereby increase the stack size by specifying a /BOTTOM:value address in the range of 1010 to 1200(octal). o The following restriction is not mentioned for the ISLEEP function: Do not call ISLEEP from within a completion routine when running under the SJ monitor. Doing that can hang the program containing the completion routine. Page 51 | .CSIGEN and .CSISPC - Passing Option Information (Section 2.13.1) | o This section does not explicitly state that .CSIGEN and | .CSISPC parse options and their associated values in reverse | order from that specified on the command line. That is, the | last option (and associated value if present) is placed last | on the stack and therefore is the first option retrieved. | That information is given implicitly in the examples, which | are correct. | .LOOKUP Standard Lookup (Section 2.46.1) | o The description for value 0 for the optional seqnum parameter | is incorrect. In fact, specifying a value 0 means rewind to | the beginning of the tape and do a file-structured lookup. | The rest of the section is correct. | Multiterminal Example Program MTXAMP.MAC (Section 2.50) | o Three areas in this program have a coding error or omission | that can cause the program to fail. | The code following the first occurrence of the symbol 30$ | should read: | 30$: ADD #2,R2 | INC R1 | CMP R1,R4 | BLOS 10$ ;Was BLO | LOOP: | CLR R1 | MOV #AST,R2 | 10$: TSTB TAI(R1) | BEQ 20$ | BIT #AS.INP,(R2) | BEQ 20$ | .MTIN #MTA,#MTCHAR,R1,#1 | BCS ERR | CMPB MTCHAR,#CTRLC ;Inserted line | BEQ DONE ;Inserted line | .MTOUT #MTA,#MTCHAR,R1,#1 | BCS ERR | 20$: ADD #2,R2 | INC R1 | CMP R1,R4 | BLOS 10$ ;Was BLO | The rest of the example is correct. | .READC (Section 2.73) | o The last sentence in the paragraph following the .READC | request syntax states that the completion routine will never Page 52 | be entered if the .READC request returns an error. That is | correct when .READC is used with any DIGITAL hardware. | However, that might not always be correct when .READC is used | with non-DIGITAL hardware. | Under rare circumstances, a completion routine could be | entered even when .READC returns an error. For that to | occur, a very high-speed non-DIGITAL device would have to | return a hard error during a short window that exists between | two sections of hardware error processing code in .READC. | The first section checks for hard errors reported by the | previous request - the second for hard errors for this .READC | request. The completion routine is entered before .READC | returns for the second hardware error check. CONCAT (Section 3.4) o The err argument is a logical error flag of data type LOGICAL*1; not simply LOGICAL. It is especially important to use the LOGICAL*1 form when you use the FORTRAN-77 compiler. GTJB/IGTJB (Section 3.11) o You must include a valid ASCII job name in the jobblk parameter to obtain a 12-word block; simply including a comma after the addr parameter obtains an 8-word block. Also, the example program is incorrect; you cannot use a job number for the jobblk parameter - you must use a valid ASCII job name. | ICSI (Section 3.21) | o The option parameter description does not include the | following information: | ICSI parses options in reverse order from that specified | on the command line. Therefore, ICSI places options in | the INTEGER*2 array in reverse order from that specified | on the command line. That is, the last option on the | command line is placed first in the array. That is only | significant if you have multiple occurrences of the same | option in the command line. IFREEC (Section 3.29) o Error code 1, Specified channel is not currently allocated, is incorrect. The error code is actually -1. IGETR (Section 3.32) o The argument parameters, offset and msize, are in reverse order in the documented IGETR subroutine syntax and the Page 53 parameter list. In fact, the correct syntax is [,msize[,offset]]. o The description of the IGETR system subroutine does not indicate the method you should employ to use IGETR from within a FORTRAN program. There is no example indicating how to force the addr parameter to begin on a PAR boundary. The following information and example show how to do that. As documented, the addr parameter is a variable. The base address of that variable is used for the global region. That variable must reside on a PAR boundary. Therefore, the variable's address must be a 4K-word multiple from 000000. Use the following procedure to place the variable on such an address (the example program below uses the variable names mentioned in the procedure): 1. Create an INTEGER*2 array of one element. (That array is X in the example.) 2. Create an INTEGER*2 index for that array. That index (called INDX in the example) contains the desired octal PAR boundary value minus the assembled address of the array X, divided by two, plus one. Those contents produce the offset into the array that falls on the PAR boundary. 3. Use the array at the calculated index as the address (addr parameter) in IGETR, forcing the addr parameter to a PAR boundary. 4. The following restrictions apply when using IGETR with FORTRAN IV and FORTRAN-77: o If you are using FORTRAN IV, do not generate your OTS with the V2S array subscript bounds checking module - use the V2SN module instead. o If you are using FORTRAN-77, do not enable array subscript bounds checking (do not use the /I compiler option). The following example program illustrates the procedure discussed above. The program tests the 4 methods of calling IGETR: Page 54 C TO DEMONSTRATE INITIALIZING A GLOBAL REGION FROM A FILE, COPY C ANY ASCII TEXT (.TXT) FILE OF AT LEAST ONE BLOCK TO A FILE YOU C CREATE NAMED TEST.DAT. THE FIRST 256 BYTES OF TEST.DAT IS C USED AS THE INITIAL INPUT DATA FOR A GLOBAL REGION YOU CREATE C USING THE FOLLOWING PROGRAM. INTEGER*2 RES, I, J, IPAR, CSIZ, MSIZ, OFS INTEGER*2 WRKA(7), INDX, OFFSET, X(1) INTEGER*4 RNAME REAL*8 SPEC EXTERNAL SETREY DATA IPAR / "40000 / DATA CSIZ / 128 /, MSIZ / 0 /, OFS / 0 / C INDX = (IPAR - IADDR(X)) / 2 + 1 !CALCULATE INDEX OFFSET = INDX - 1 ! AND SUBSCRIPT OFFSET CALL IRAD50( 6, 'REYJUN', RNAME ) ! MAKE RAD50 REGION NAME CALL IRAD50( 12, 'DK TEST DAT', SPEC ) ! RAD50 TEST DATA FILE C--------------------------TEST METHOD 1------------------------------ RES = IGETR( WRKA, 'P', RNAME, X(INDX), CSIZ, MSIZ, OFS ) WRITE( 5, *) 'TEST 1 RETURNED', RES DO 10 I = 1, 128 X(OFFSET+I) = I 10 CONTINUE DO 20 I = 1, 10 WRITE( 5, 1001) I, IPEEK( IPAR+((I-1)*2)) 1001 FORMAT( ' EXPECTED/FOUND: ',I6,' / ',I6) 20 CONTINUE RES = IFREER( WRKA, 'E' ) C--------------------------TEST METHOD 2------------------------------ ICHAN = IGETC() IF (ICHAN .LT. 0) STOP '- NO CHANNELS AVAILABLE' RES = LOOKUP( ICHAN, SPEC) RES = IGETR( WRKA, 'A',RNAME,X(INDX),CSIZ,MSIZ,OFS,ICHAN,0) WRITE( 5, *) 'TEST 2 RETURNED', RES CALL CLOSEC( ICHAN ) CALL IFREEC( ICHAN ) RES = IFREER( WRKA, 'E' ) Page 55 C--------------------------TEST METHOD 3------------------------------ RES = IGETR( WRKA,'A',RNAME,X(INDX),CSIZ,MSIZ,OFS,SPEC,0 ) WRITE( 5, *) 'TEST 3 RETURNED', RES WRITE( 5, 1002) (IPEEK( IPAR+((I-1)*2)),I=1,10) 1002 FORMAT( ' STRING IN FILE: "',10A2, '"') RES = IFREER( WRKA, 'E' ) C--------------------------TEST METHOD 4------------------------------ RES = IGETR(WRKA,'A',RNAME,X(INDX),CSIZ,MSIZ,OFS,SETREY,-1) WRITE( 5, *) 'TEST 4 RETURNED', RES DO 40 I = 1, 10 WRITE( 5, 1001) I, IPEEK( IPAR+((I-1)*2)) 40 CONTINUE RES = IFREER( WRKA, 'E' ) END C--------------------------------------------------------------------- SUBROUTINE SETREY( ADDR, LN ) ! CALLED BY IGETR INTEGER*2 I, ADDR, LN DO 10 I = 1, LN CALL IPOKE( ADDR+((I-1)*2), I) 10 CONTINUE RETURN END IREAD/IREADC/IREADF/IREADW (Section 3.48) o Section 3.48, IREAD/IREADC/IREADF/IREADW, contains inaccurate information about the error codes returned for IREAD, IREADC, and IREADF. The normal return for IREAD, IREADC, and IREADF is 0, and not n. IREAD, IREADC, and IREADF cannot return the value for n because the monitor returns control to the user program immediately after they are initiated. IREADW does return n as the normal return because the monitor returns control to the user program at completion of the subroutine. The rest of the section is correct. IRENAM (Section 3.49) o Section 3.49, IRENAM, contains inaccurate information about the error codes it returns. Code 3 is incorrect and code 4 is omitted. The following are the correct descriptions of those codes: i = 3 Device is currently in use. = 4 A file by that name already exists and is protected Page 56 IWRITE/IWRITC/IWRITF/IWRITW (Section 3.68) o Section 3.68, IWRITE/IWRITC/IWRITF/IWRITW, contains inaccurate information about the error codes returned for IWRITE, IWRITC, and IWRITF. The normal return for IWRITE, IWRITC, and IWRITF is 0, and not n. IWRITE, IWRITC, and IWRITF cannot return the value for n because the monitor returns control to the user program immediately after they are initiated. IWRITW does return n as the normal return because the monitor returns control to the user program at completion of the subroutine. The rest of the section is correct. | LOOKUP (Section 3.82) | o The description for value 0 for the optional seqnum parameter | is incorrect. In fact, specifying a value 0 means rewind to | the beginning of the tape and do a file-structured lookup. | The rest of the section is correct. REPEAT, SCOPY, STRPAD (Sections 3.101, 3.105, 3.108) o The err argument is a logical error flag of data type LOGICAL*1; not simply LOGICAL. It is especially important to use the LOGICAL*1 form when you use the FORTRAN-77 compiler. 4.0 RESTRICTIONS | o You should not use I/O programmed requests (for example, | .READ/.READC/.READW, .WRITE/.WRITC/.WRITW, and .SPFUN) within | completion routines under the SJ (single-job) monitor. You | should also not use those I/O programmed requests within | device handlers under the SJ monitor, even when such requests | follow a .SYNCH request. Doing that induces a race condition | that under certain circumstances can hang the system. | That race condition is not a result of RT-11 V5.4B | development; however, it was only recently discovered. The | system hang is most probable when using I/O programmed | requests in completion routines with the VM device. Although | less probable, using I/O programmed requests in completion | routines under SJ can hang the system with any device. | Therefore, any critical application running under SJ should | not use I/O programmed requests in completion routines with | any device. | o You can hang or crash your system if you unload a device | handler that has outstanding I/O requests from a job. You Page 57 | must stop the job that is using that handler before you | unload the handler. | o All BUP CSI options are position dependent; they must be | coupled with the input file. Coupling any CSI option with | the output file returns an error message. | o Do not use ODT or the hard I/O versions of the DBG-11 | pseudohandlers (SDH.SYS or SDHX.SYS) while running RT-11 | under a multiterminal monitor that was generated with | multiterminal timeout support. If you use them under such a | multiterminal monitor, characters may be echoed twice on your | console terminal screen. Characters can be echoed by both | the debugging utilities and the monitor. | Also, using ODT, SDH.SYS, or SDHX.SYS under that monitor | causes characters you type as debugging commands to be placed | in the KMON command buffer. When you exit from them, KMON | attempts to execute those characters as a command, and KMON | can return an 'invalid command' error message. | Use instead VDT or the DBG-11 soft I/O pseudohandlers | (SDS.SYS or SDSX.SYS) when running under a multiterminal | monitor. (Also, you can run VDT, SDS.SYS, or SDSX.SYS from | any terminal in a multiterminal configuration.) | o If you use VDT or the DBG-11 soft I/O version pseudohandlers | (SDS.SYS or SDSX.SYS) with a multiterminal monitor, you must | set your terminal to NOWRAP (SET TT NOWRAP). | o The SET MM/MT NOODDPAR command is provided only for media | compatibility with other operating systems; use it only to | exchange magtapes with another system that requires even | parity. Do not set even parity (SET MM/MT NOODDPAR) on MM or | MT 9-track magtapes for use with DIGITAL controllers. | Magtapes written for DIGITAL controllers require at least one | nonzero bit per byte. Setting odd parity ensures that at | least the parity bit is set for a null byte. Setting parity | to even (NOODPAR) violates that requirement. DIGITAL | controllers can then either lose (fail to distinguish) that | null byte or set bit 4, which stores an octal value of 020 | with bad parity. The MM and MT handlers cannot distinguish | bytes with created parity errors from those with true parity | errors. That makes magtapes created by BUP, DUP, and PIP | unreadable. | o Multiterminal monitors for Professional 300 series processors | must be generated for multiterminal timeout support, and can | support only one terminal. o Do not use BUP to back up DL or DM non-RT-11 file-structured volumes. DL and DM volumes contain bad-block replacement tables in their home block. Do not use BUP to back up any Page 58 other volumes that contain bad-block replacement tables in their home block. (Only DL and DM among DIGITAL volumes are affected by this restriction.) o DIGITAL recommends you LOAD the MU handler when performing BUP or COPY operations with TMSCP magtape devices. o All DEQNA controllers used with RT-11 should be at revision E1/E2 or higher. o When you run under the XM monitor and you use any of the following handlers, you must explicitly load them using the LOAD command: BA, CT, DD, NC, NQ, NU, SD, and ST. You cannot fetch those handlers. o Use the .CLOSE request rather than the .PURGE request when you terminate a program that performs I/O operations to any RT-11 magtape device. See Section 3.4, Magtape Handlers, of this file for information. o The transparent spooler (SPOOL) supports only a single device: SP0 or SP. Attempts to SET conditions for SPn, where n is other than 0 or omitted, can cause SPOOL to hang. o All terminals used with DBG-11 must have hardware tabs. o You cannot run IND or RESORC from VBGEXE. o You cannot use SL to edit the continuation line of a DCL KMON command. o All DEQNA Ethernet controllers used with RT-11 must have the sanity timer disabled. The DEQNA sanity timer reboots the RT-11 system after a period of time under certain circumstances. If you suspect your DEQNA sanity timer is enabled, consult your DEQNA user documentation for information about disabling it. o The LIBR /X option for creating multiple definition libraries is included in RT-11 only for compatibility with the RSTS operating system. DIGITAL recommends you do not use the LIBR /X option under the RT-11 operating system. o When you perform a SYSGEN and request no SPOOL banner page support, various SET conditions appropriate for SPOOL banner page support are made invalid. Also, you cannot change the default SET conditions FORM0 and ENDPAG=0. If you want the SET condition NOFORM0 or ENDPAG=n, where n is other than 0, use the distributed SP handler. o When you use the PRINT SCREEN function on Professional series processors and the text displayed on your screen contains certain character sets or character and/or line attributes Page 59 (bolding and so forth), your printer might not print the entire screen line. You can avoid (or minimize) this problem by setting the LS handler condition GRAPH, using the SET LS GRAPH command. You must unload and reload the LS handler before any LS condition will change. You can do that by soft-booting your system device after you issue that command. o A directory listing of a file larger than 42767(decimal) blocks on any magtape shows a file size of 0. All magtape handlers incorrectly translate numbers greater than 42767(decimal) block file size to ASCII 0. (The number 42767 is a correct number; it is not a typo.) o On a multiterminal system, do not abort a job on a private console with two CTRL/Cs. Issuing two CTRL/Cs to a job on a private console can crash the system. You must abort a job on a private console from the hardware console. From the hardware console, first use the SUSPEND command to suspend the job on the private console and then use the ABORT command to abort that job. o You cannot use the distributed MDUP programs with LSI-11 processors. Use the procedure described in the MDUP section of this file to build an SJ monitor and an MDUP program that you can use with your LSI-11 processor. o If you use SIPP to patch or examine an overlaid program without using the /A option and SIPP reads to the end of a disk, SIPP returns the error message, ?SIPP-F-Input error , and does not read the last block on the disk. ----- End of V5NOTE.TXT b?INDEX-X-6 J_t$4FScx3DRInvalid input stringEnd of index reachedSearch string not foundMismatched book identifier lengths, incompatible data fileUnknown error codeWEFU *ABDNOPRSTUZ/*jr.T>J4Unknown error code Channel in use Channel not open Device full Directory full Directory I/O error Fetch error File created; protected file already exists File not found Invalid device Input error Insufficient memory Output error Output file full Protected file already exists Record too long System error Unexpected EOF   E@$ % * v   < \'     ȕ0  X   ȕ0  : w"    z  ȕF  0  0 $   z ևe07/ 6  E C˥ ʥ  ȕF0  j ҋʋAaɥ %w.% / 6 e  H  8 & & 8 ȋw  ȕ0   8   ȕ0  )AZA 8 $[ .\A\Ae  fE  p0    ȕF E77$  0 և $  8  & ΥaΥz B8 ¥A܂¥Zه  Bҋ╀ы@  ыɥn   Ý ɵ Bŀ `& j  ^ ɥ@ɋ Bɵ@ f( 8 . ( BBы5@ L4  ɥɥы8 > 鈇鈇E@ Y 2- (&       Еi ЕiЕv Еi Еxe Еx2Еl R'#1   6   1 1 1 1  %F&7 @ : .0 ߋ* ȕF$   , t:#8t:#O:#6RT-11 ON-LINE INDEX X.00Search string:Enter new search string or just press RETURN to scrollNo match foundThe on-line index data file includes indexes from several manuals in the RT-11 documentation set. The on-line index display identifies index entries from each manual with a mnemonic: The on-line index does not include the entire RT-11 documentation set. In general, obvious references (for example, the KED manual to find out about KED, and the commands section of the System User's Guide) are omitted. Type to continue: DEV Device HandlersGUI Guide to DocumentationINS Installation GuideINT Introduction to RT-11MRM Mini-Reference ManualV5N Online Release Notes (V5NOTE.TXT)PRM Programmer's ReferenceSIM System InternalsRLN System Release NotesSSM Software Support ManualSUG System User's GuideSUM System Utilities ManualSYG System Generation GuideVFF Volume and File FormatsBEG RT-11 For BeginnersDBG DBG-11 User's GuideKED Keypad Editor User's GuideMAC MACRO-11 Language Manual[A15][A33][A133]50C[S][A40][A40] [S]-[U3]-[U] to ,  P   2  `E@@鈀5  ѕeȋР+ z f&feD&][ y ȋ e@h Bӕ ӕ ӕ @A @ B  ~C   &:ԋ@   & m  . "   F&A m   C Se  * E0B & W c `ԋ@䋇&f& v  Е- w   Е- w @A f    e0(@w  % b % e%e ee e w :D   ѕ:   ѕ.  D &f f A N  %$F/A DIR option Error Logger option FILEX option LD option  LIBR option  LINK option + PIP option  QUEMAN option RESORC option SIPP option SLP option ABORT$ bit in I.STATE= Aborting program executionABORT keyboard command ABORT operating mode (IND), effect on CTRL/C, ABPND$ bit in I.STATE=ABS p-sect attribute Absolute base address p-sects changing number ofAbsolute binary file format See .LDA filesAbsolute binary loader and .LDA files'Absolute block parameters (table) Absolute load module creating Absolute program section  attributes (table)  contents of .ABS program section declared in .OBJ fileABTIO$ bit in device status word defined by .DRDEF$ .ABTIO programmed request  corrected problems summary  with outstanding I/O Access code p-sect attributes ACTIV$ ACTIVE Active page field use in memory mappingActive page register definition of  discussion format  relationship to PSW Addresses assignment by LINK ) converting 16-bit To 18- or 22-bit Addressing 18- and 22-bitAddressing modes description Address regions discussion.ADDR macro  summary Advance (A) command (EDIT)   arguments(AGE (Automatic Global Elimination)EAJFLT system subroutine summaryC using:/ALLOCATE option Alloc-code function of  p-sect attributes ALPH00.FNT  IND special symbol  IND special symbol(American Standard Code for Information Interchange See ASCII ANSI codes setting terminal for ANSWERBACK:/message/ SETUP mode Answer file creation required with SPR use of previously createdAPF See Active page fieldApplication packages APR See Active page registerArrays in extended memory# AS.CAR bit in AST word AS.CTC bit in AST word AS.HNG bit in AST word AS.INP bit in AST word AS.OUT bit in AST word /ASCII[:n] TRANSFER mode qualifierASCII character setASCII files copying  described"ASCII formatASECT See Absolute program section.ASK directive (IND)1 maximum number of characters allowed in prompt for question display& responses to prompts printed by.ASKN directive (IND)1 maximum number of characters allowed in prompt for question display! radix  responses!.ASKS directive (IND)" determining the radix#1 maximum number of characters allowed in prompt for question display$ responses$Assembler  function ofAssembler errors Assembling diskette files,Assembling monitor and device handlersAssembly language See Machine-level languageAssembly listing ASSIGN keyboard command% assigning logical device names $ changing the output device .ASSUME macro  summary Asterisk (*) used with UCLAsterisk (*) sign wildcard See Wildcards. AST Word( See Asynchronous terminal status word%Asynchronous terminal status'Asynchronous terminal status word defined description At (@) sign restriction with UCL Audit trail SLP disabling enabling specifying specifying size ofAuto installation file list of (table)Automatic installation changes to% corrected problems  DL devices&% invalid hardware configuration IVP on the PRO&! media file structure check& media installation check& memory check for TK50& RD52 QUANTUM disk& requirements for RL02 support for RX02 support for RX33 support for RX50 support for TK50 support for valid input media% valid output media%Automatic system build AVAIL& list of free I/O queue elements  /B BINCOM option DIR option DUP option LINK option + PIP option  SLP option BA.MAC  Background job communicating with See CTRL/B creating debugging with ODT description& differences from foreground job directing input to editing executing privileged* running terminating virtual-Background program runningBACKSPACE key with single-line editor Backup copy files system volumeBBACKUP keyboard command /INITIALIZE option  /NOLOG option  /NOQUERY option  /NOREWIND option  /NOSCAN option  /SAVESET option  /VERIFY:ONLY option Backup utility program See BUPBackup volumes (BUP) initializing Bad block replacement*  BUP and DL with9 BUP and DM with9 DU requires XM monitor /H option with MSCP (DU)* in user-written handlers9# non-RT-11 file-structured DL9# non-RT-11 file-structured DM9 on RK06/RK07 (DM) $ table in handler table in home block " /VERIFY:only with MSCP (DU)*!Bad block replacement table Bad blocks covering replacingBad block scans. including name of files with bad blocks  performing .BAD files copying  deleting  PIP treatment of  BA handler must LOAD:Banner pages changing default width of7# printing specified number of setting default number of suppressing printing ofBanner page support#Base address in VM handler 0Base-line monitor See BL monitor$BASIC BATCH commandA BASIC-11 commands   command summary edit  execution  file maintenance  demonstration program  errors  running  exiting  immediate mode  interpreter  language processor  programming language  returning to command mode BASIC-11 program creating   editing  maintaining files  replacing  running  saving using &BASIC-11 programming language BASIC-PLUS BATCHAA4 * assembling MACRO source files usingA) calling another BATCH control fileA calling BASIC withA $ calling FORTRAN compiler withA$ can run virtual jobs under XM character setA character set (table)A  command field optionsA$ command field options (table)A* command fields in control statementA command line syntaxA command namesA commandsA A! commands (table)A  commentsA" communication with RT-11A A$ compilerA creating files withA- creating programs for on punched cardsA* data transfersA with FORTRAN programsA, deassigning logical device names withA description of  directory operationA executing a program withA  file deletionA3 file specifications in control statements toA file typesA function ofA general rulesA  hardware requirementsA image mode copyA& indicating beginning of job forA" indicating end of a job forA! indicating end-of-data forA jobs* assigning identification number toA! communicating withA0 link operationsA loadingA+' nesting control files with BATCHA preparing to useA+ printing files withA restrictions for RT-11 differences from RSX-11DA3 RT-11 modeA A# RT-11 mode (examples)A) RT-11 mode programs comments inA) creatingA% runningA- run-time handlerA software requirementsA" specification field optionsA* specification field options (table)A specification fieldsA2 specifying devices in control statement forA stream running SIPP from stream (example)A! temporary filesA terminal I/O control withA( terminatingA3 wildcards using withA$ works as documented with V5.4 BATCH$BATCH.SAV# modifying to save disk space&Batch support BATRN$ bit in I.STATE=Baud rates*BCD SETUP mode.BEGIN directive (IND)%Begin-end blocks (IND)%3 exiting4 "Beginning (B) command (EDIT) Belgium language keyboard BIN: /BINARY[:n] TRANSFER mode qualifierBinary coded decimal see BCDBinary Comparison Program See BINCOMBinary files comparing copying Binary formatBinary output device - BINCOMb  byte-by-byte comparison calling changes to& command syntax corrected problems description of device comparison differences file forcing creation of format suppressing end block for comparison examples function of halting help option options0 and keyboard command equivalents (table)B options (table) output processing of files* SIPP command file as output from forcing creation of$ starting block for comparison wildcards withBINCOM.SAVBit definition of 18-bit addressing discussion22-bit addressing discussion Bitmap  for low memory protection5 in .SAV file  suppressing creation of 8Bit-map graphics setting terminal for B keyboard command BL.ANSBlank arguments description .BLANK graphics macroA BLKEY RMON fixed offset 2560 used by USR $BLKMV4 BL monitor advantages of description of features of features of (table) vs SJ monitor (table)BLOCK SETUP modeBlocking conditions defined discussion# how the monitor blocks a job% how the monitor unblocks a job" list of bits in I.BLOK!Block-replaceable device See also DevicesBOLD SETUP mode BOOT keyboard command operation8:/BOOT option& COPY keyboard command operation9 Bootstrap copying to a volume  discussion4 error routine7! handler loading and .DRPTR loading softwareB magtape list of (table) manual operationsA part of primary driver6 procedure$ prompts and responses (table) pushbutton consoleAA read routine6* relationship with computer (figure) role of DUP program8$ suggestions for bootstrappingB! switch register consoleAA terminal keyboardA typingA use to install handlers=Bootstrap loader MSCP address and contents RK05 address and contentsB RK06 address and contentsB RK07 address and contentsB RL01 address and contentsB RL02 address and contentsB RX11 address and contentsB! RX211 address and contentsB TC11 address and contentsB! TJU16 address and contentsB TM11 address and contentsB! TMSCP address and contents ! TSV05 address and contentsBBootstrap message changing0 suppressing/Bootstrapping foreign volumes Bootstrapping the system in less than 16K words*,Bootstrap routine's automatic installation capabilityBPT instruction under XMIBREAK VTCOM command Breakpoints clearing  clearing all  setting using with ODT /BRIEF option! DIRECTORY keyboard command.BR macro  summary BSTRAP.MAC  Buffers in extended memory#Building device handlers."Building handlers separatelyBuilding monitors. Bullets$ in SRCCOM differences listing# changing character used for BUPc  bad blocks on input media' calling can run under VBGEXE changes to'/ changing acceptable number of bad blocks' command string syntax corrected problems 3 correction for non-RT-11 formatted DL and DM4 correctly follows links of directory segments! correctly sizes RK05 disks% CSI options position dependent9 default operation description of) DIRECTORY/BACKUP/OUTPUT[:filespec]  directory listing changes to magtape  sample for magtape' sample for random-access volume directory operation changes to , disk input volume containing FILE.BAD file backup error in V5.2 function of /G option  image mode backup changes for magtapes  command syntax example for files for volumes inhibiting bad block scan # inhibiting magtape rewind . initializing volumes for use with  magtape magtape format changes, magtape multivolume consistency check magtapes with( magtape volume header information /M option " multiple backups to magtape ' multiple output volumes under XM must initialize magtapes  options 0 and keyboard command equivalents (table)B options (table)! restoring a single file" restoring file from saveset* restoring files and volumes with  restoring savesets restrictions for 9/ running from command or control files ' smaller to larger volume allowed /S option " Storing magtape directories . suppressing initialization confirmation terminating" using savesets with magtape  /V:ONL option valid option combinations ( VAX/VMS magtape transport support verification! verifying restored saveset! /VERIFY option corrections wildcards with /W option  /Y option changes BUP.SAV BUS$ BYE command BASIC-11 Byte definition of  /C DIR option DUP option LD option  LIBR option  LINK option , MACRO option  arguments for (table)  PAT option PIP option  QUEMAN option RESORC option SIPP option SLP option  SRCCOM option C.COMP ' offset in timer queue element @  C.CSW returned by .SAVESTATUSt C.DEVQ" offset in I/O channel block@ returned by .SAVESTATUSt C.HOT ' offset in timer queue element @  C.JNUM ' offset in timer queue element @  C.LENG" offset in I/O channel block@ returned by .SAVESTATUSt C.LINK ' offset in timer queue element @  C.LOT ' offset in timer queue element @  C.SBLK" offset in I/O channel block@ returned by .SAVESTATUSt C.SEQ ' offset in timer queue element @  C.SYS ' offset in timer queue element @  C.UNIT returned by .SAVESTATUSt C.USED" offset in I/O channel block@ returned by .SAVESTATUSt CACHE$Cache-bypass using global regions&$CALL BATCH commandACALL$F system subroutine saves general registers)Canadian (French) language keyboardCAPS SETUP mode CAPS-11 using to load files. Card reader See also CR handler Cassette file header format  file structure  handler See CT handler CC$GBL CC$INDCCL adding new commands' function of getting unaltered command) syntax using in control files.CDFN programmed request  effect of .EXIT1 effect on .GTJB: relationship to .CHAIN relationship to .SRESET restricted in PAR1H restrictions summary usingCF: assigning to VM deviceC% LINK cross-reference work file $CHAIN BATCH commandA CHAIN$ Chain area$ passing unaltered CCL command) with R command  with RUN command  with virtual jobs .CHAIN directive (IND)% Chain Exit See .EXIT.CHAIN programmed request  description restrictions in XM summary using works under SJ monitorCHAIN system subroutine summaryBChange (C) command (EDIT) arguments Change bars$ in SRCCOM differences listing# changing character used for Changes/ marking in SRCCOM differences listingChanging dialog responses*Channel allocation using .CDFNChannel numbers description system subroutine library'Channel status word See also CSW ACTIV$ DBLK$M DWRIT$ EOF$ HDERR$ INDX$M RENAM$Character case handling by KMON*Character insertion immediate modeCharacter search (EDIT) Character setsCharacter strings allocating in FORTRAN= parsing in control files= passing to subprograms> quoted literals? support in SYSLIB< .CHCOPY programmed request  applicable to system jobs' summary% using Version 4 Checksum PAT SIPP SLP CHKEY RMON fixed offset 2600 used by USR CHNIF$ CHNWT$  bit in I.BLOK>Circumflex (^) used with UCL CIS$CK.Rn check macro created by .CKXX.CKXX macroCLEAR SETUP mode  VTCOM command.CLEAR graphics macroACLICK SETUP mode CLIFLG9 CLITYP9 CLK50$Clock support for CLOCK$ Clock modes See SETUP Clock rate specifying 50-cycle- CLOCK SHOW SETUP modeCLOSEC system subroutine relationship to ICSI relationship to IENTER summary? USR requirements+.CLOSE directive (IND)&CLOSE keyboard command after .EXIT& closing a file opened with EDIT relationship to .EXIT0 CLOSELOG VTCOM command.CLOSE programmed request   CT handler  hardware magtape handler  not done by .CSISPC on a protected file6! on file-structured magtape recommended with magtapes" relationship to .CHCOPY relationship to .ENTER. relationship to .LOOKUPF relationship to .PURGE_ relationship to .SERR? requires device handler2 summary! using!.CMKT programmed request   See also .MRKT relationship to .MRKTL summary! using CMPLT$ bit in I.STATE= .CNTXSW programmed request   restrictions summary% using CNTXT$ RMON fixed offset 320 (FB/XM)2COLOR SETUP modeColor monitors changing color onCOLOR on COLOR SETUP mode 132COLUMNS SETUP mode 80COLUMNS SETUP mode COMMAN IND local string symbol Command arguments (EDIT) table ofCommand Line Processors selectively inhibitingFCommand lines( abbreviating commands and options6 abbreviating using file specification factoring" continuing to the next line deleting See Single-line editor. deleting characters in editing See Single-line editor reproducing See Single-line editor Commands BASIC See BASIC-11 control format of correcting typing errors EDIT See EDIT getting CCL parameters) getting unaltered CCL) keyboard See also Keyboard commands format of multiline using in a control file ODT See ODTCommand String Interpreter See CSI Comments( ignoring during SRCCOM comparison in BATCH filesA in control files external internalCOMMON attributes (table) COMMON statement (FORTRAN) creating p-sects with  Comparison of binary files See BINCOM of source files See SRCCOMCOMPILE keyboard commandCompiler Completion queueCompletion queue element  format? Q.BUFF  Q.COMP  Q.LINK  Q.WCNT Completion routines correcting stack overflow2- implications of a blocked main program# introduction not serialized in SJ restrictions)  system subroutine library( Components" arranging on working system COMPOSE SETUP controlCOMPOSE CHARACTER keyComposing charactersCON p-sect attribute Concatenating files CONCAT system subroutine corrected problems err argument information4 len argument clarified& summary<DConcise command language See CCLConditional files) retaining source files after build.Condition codes used in .DRVTB macro CONFG2' See also System configuration word 2 RMON fixed offset 3703 bit definitions7 CONFIG C% See also System configuration word changes to( /D option( /F option( introduction4 RMON fixed offset 3001 bit definitions4 /T option(CONFIG.COM CONFIG.SAV Configuration hardware displaying software displayingConfiguration word See CONFIGConfirmation prompts FORMAT suppressing PIP requesting  QUEMAN& requesting when printing files CONSOLCCONSOL.MAC Console See also Terminals background or command boot-time definition of hardware private shared special characteristics switchingContext switching defined discussion information saved" virtual and privileged jobs" CONTINUE VTCOM commandControl files! See also IND, IND command line" See also Indirect control files arithmetic operators in begin-end blocks in%3 exiting4 branching to a command line4 to subroutines4 when errors occur; CCL commands in chaining between% closing open files& command line in (example) commenting See Comments contents of creating general rules for debugging with /T default file type delaying processing of'* deleting after processing completes0 displaying processing of command lines in2 ESCAPE recognition in. executing# from keyboard monitor level exiting4 formatting" global symbol definition in/ global symbols in IND directives in keyboard commands in! suppressing display of1 suppressing execution of labels in See also Labels local symbols in logical symbols in See also Logical symbols lowercase characters in/ multiline commands in nesting numeric expressions in numeric symbols in See Numeric symbols opening data files from<" parsing strings from within>( passing parameters when executing  querying file structureD( returning from subroutines within? sample line from string symbols in See String symbols symbols in# terminating processing ofD% testing device characteristicsG" testing existence of a fileI, testing the starting position of an ASCII stringF uses for Controller second$CONTROL-Z operating mode (IND)-$COPY BATCH commandA Copying$ between RT-11 and RSX-11 host% between RT-11 and VAX/VMS host using TRANSFER and VTCOMCOPY keyboard command Copy operations reducing errors during  verifying Core control block used by RUN command CPEND$ bit in I.STATE= CR.MAC  CR.SYS!.CRAW programmed request  See also .ELAW description of operationB relationship to .GMCX7 relationship to .WDBBK summary%# uses window definition block9 using with cache-bypass' $CREATE BATCH commandACREATE keyboard command/CREATE option EDIT keyboard command" LIBRARY keyboard command  Creation date of files CREF* See also Cross-reference (CREF) listing chain interface$ file format$CREF.SAV# changing page listing length< CR handler described $Cross-reference (CREF) listing  assigning device for  contents of  designating device for 2 example  generating 2   in load map (! in load map (illustration) 'Cross-reference (CREF) table% See Cross-reference (CREF) listing/CROSSREFERENCE option MACRO keyboard command !.CRRG programmed request  See also .ELRG# attaching to a global regionA creating a global regionA creating a local region@ summary% usingCSECT named  unnamed CSECT attributes (table) .CSECT directive CSI See also .CSIGEN See also .CSISPC Command string syntaxa command string syntax default devices in" radix of numeric arguments function of implicit .UNLOCKD implicit UNLOCKp introduction options using .CSIGEN programmed request  See also .CSISPC" channel purging information% compared to .GTLIN; implicit .UNLOCKD& parses options in reverse order3 performs a purge;! relationship to .LOOKUPFH summary! usingCSI Options CSIRN$ bit in I.STATE= .CSISPC programmed request  See also .CSIGEN compared to .GTLIN; implicit .UNLOCKD modifies no channels& parses options in reverse order3& relationship to .SETTOP and USR} summary! usingCSI special mode See .CSISPCCSR addresses DL11 lines( DZ multiplexer,first* local DL11 interfaces) parallel printer$ printer, nonstandard$ remote DL11 interfaces) RX02 diskette! serial line printer% VT11/VT60& XL handler%CSRs interrupt.CSTAT programmed request  summary! using Version 5 $CSW RMON fixed offset 40CSW See also Channel status word bits defined by .DRDEF% contentsA CT.MAC  CT.SYS CT handler .CLOSE programmed request  corrected problems ! .DELETE programmed request  described  detecting EOF  .ENTER programmed request ! .LOOKUP programmed request  must LOAD:! .READx programmed requests  .SPFUN requests  last block  last file  next block  next file  rewind  write file gap ! .WRITx programmed requests .CTIMIO macro  See also .TIMIO described expansion relationship to .DRDEF$ summary! using CTRL/A CTRL/B  discussion CTRL/C  disablingv discussion" including in text with EDIT sets bit in AST word with EDIT!CTRL/C ESCAPE ESCAPE (EDIT) CTRL/D CTRL/E  CTRL/F   discussion CTRL/G CTRL/L CTRL/N CTRL/O    discussion reset by .RCTRLOd with EDITCTRL/P VTCOM command CTRL/Q  discussionCTRL/R  CTRL/S  discussion CTRL/U   with EDITCTRL/U (EDIT) CTRL/VCTRL/W  CTRL/X   discussion use of) with EDITCTRL/Y with SIPP CTRL/Z  with SIPP CTRL keys CURSOR SETUP modeCUSTOM.TXT " customization symbol valuesCustomizations# for distributed monitorsG software! getting symbol values forCVTTIM system subroutine instead of .GTIM9 summaryA using:CYCLE single-line editor50-cycle clock rate-. restriction for Professional 300 series- /D BINCOM option DIR option DUP option FILEX options  IND option LIBR option  LINK option - MACRO option  PIP option  QUEMAN option RESORC option SIPP option SLP option SRCCOM optionD p-sect attribute  D.EXTR D.HIGH D.NEXT D.STRT D.TOTADA See Device attributesDanish language keyboardDAPRES (RSX-11) libraryDARK SETUP terminal mode$DATA BATCH commandADATA SETUP controlData blocks in .OBJ module contents ENDGSD ENDMOD GSD ISD librarian end librarian header RLD TXT types.DATA directive (IND)&0 creating an indirect command file with& Data format ASCII binaryDATA operating mode (IND)- $DATE RMON fixed offset 2620Date See also Time displaying  entering' .GTIM required for date rollover9 internal format  month and year rollover set by .SDTTM{ IND special symbolDATE[:dd:mm:yy] SETUP modeDATE keyboard command .DATE programmed request  summary! usingDATE subroutine (in FORLIB) using:DATE system subroutine support for* DATIME  CDATIME.MAC DATIME.SAV Daylight saving time see DSTDBG-11! handler suffix restriction handlers used for SDH.SYS* SDHX.SYS* SDS.SYS* SDSX.SYS* restrictions for support for & terminals require hardware tabs: utility used for DBGSYM.SAV " with multiterminal monitors9DBGSYM.SAV DBLK$MDCL operating mode.DCL status word IFABRT IFACTV IFBEXT IFCHAI IFCTLC IFDAT IFDOL IFEKO$ IFEOF$ IFGTCC IFIND IFINP IFLEOF IFLIF IFRVTT DD.MAC  DD.SYS DD handler, accessing unloaded TU58 no longer crashes system ) adding bad blocks to avoid rewinds ) changes to data storage ( described ( RETRY=n values for  write-protect feature ( DDX.SYSDead diacritical keysDEASSIGN keyboard command Debuggers list of (table)Debugging a program  See also ODT techniquesDebugging programs See ODT and VDT See also DBG-11 /DEBUG option LINK keyboard command.DEC directive (IND)'DECFKM See Function key mode%Decimal/octal/binary conversion DECsystem-10 volumes copying to RT-11 volumes DECtape II block locations on changing CSR addresses in# changing vectors in# handler See DD handler! improving response time on restrictions for DECTCEM See Text cursor mode  IND special symbol and .ASK directive and .ASKN! DEFAULT SETUP controlDefault device assigning changing for EDIT command2 changing for FRUN command1* changing for indirect command files0 changing for QUEMAN4Default mapping.DELAY directive (IND)' $DELETE BATCH commandADelete (D) command (EDIT)  arguments (table)DELETE (DEL) command BASIC-11 DELETE key  correcting typing errors editing for Single-line editor function immediate mode ODT with EDITDELETE keyboard command !DELETE operating mode (IND). .DELETE programmed request  CT handler  on a protected file6! on file-structured magtape  requires device handler2 summary! usingDeleting .OBJ files Deleting files  .BAD  .SYS  with BATCHA with FILEX DEMOBG.MACDEMOED.TXTDEMOF1.FORDEMOFG.MACDemonstration programs BASIC-11  creating creating volumes for FORTRAN library files  list of (table) load maps  MACRODEMOX1.MACDENSE SETUP mode Density changing for magtape&DEQNA controller disable sanity timer: revision restriction:Device assigning default to dataDevice assignments changing  displayingDevice attributes. FB and XM secondary response correction2 primary responses  requesting primary  requesting secondary  secondary responses  set as GENERIC100  set as VT100  VT100 response correction2Device attributes reply setting like VT100  setting to GENERIC100Device blocks description % with system subroutine library*Device codes" MU NC/NQ/NU SD STDevice comparison binary See BINCOMDevice driver See Device handlerDevice failure( using the Error Logger to predictDevice handler definition#Device handler block number table discussionB"Device handler entry point table discussionBDevice handler macros .CTIMIO  .DRAST ! .DRBEG # .DRBOT # .DRDEF .DREND % .DREST .DRFIN & .DRINS & .DRPTR .DRSET ' .DRSPF .DRTAB .DRUSE .DRVTB ( .FORK 4 .INTEN B .QELDF .SYNCH  .TIMIO %Device handler permanent name table discussionADevice handlers % accessing user buffer directly1& adding to queue of I/O requests advantages of using" as dynamic system component assembling; assembling and linking( associated with specific monitorsD bad block replacement* block 0 information use of .DREST use of .DRPTR use of .DRSPF use of .DRTAB use of .DRUSE building. changing file name suffixD& choosing for peripheral devices " choosing for working system 2 controller installed at nonstandard address#$ converting old handlers to V5B& defining special function codes description device classification variations of device I/O timeout applications " DIGITAL-defined data tables .DRINS used withB editing SYSTBL.MAC@ for pseudo-devices for system devices4 creating5 I/O completion section if error if successful) installation verification routinesA techniquesA installing=& bypassing hardware requirementD precedence= requires device hardware@ with INSTALL command? with the bootstrap=$ installing generated handlersD+ instead of in-line interrupt service internal queuing interrupt service section guidelines for coding in XM systems+ addressing user buffer, linking< list of (table) lowering priority naming conventions+ performing I/O retries planning queue element offsets registers available abort entry point I/O initiation section  interrupt entry point relationship to RMON renaming" require PIC code service routines in SET commands examples information in registers R4 and R5 not available size limits SET table format size of+ special directory devices* special functions( specific card reader (CR)  cassette (CT)  DECtape II (DD) ( diskette (DX, DY)  file-structured magtape  hardware magtape  logical disk (LD) 2 MM, MS, MT  MSCP (DU) * null handler (NL) ( paper tape (PC) # RK06/RK07 (DM) $ RL01/RL02 (DL) & terminal (TT) # virtual memory (VM) / status of displaying structure abort entry point block 0 information  # handler termination section header section I/O completion section I/O initiation section ! interrupt service section  preamble section skeleton outline # supporting special functions) SYSGEN conditionals testing and debuggingD! uniform RETRY=n values for  unloading restriction8! use of $GETBYT and $PUTBYT. use of $MPPHY routine. use of $PUTBYT routine/ use of $PUTWRD routine0 use of .CTIMIO use of .DRAST use of .DRBEG  use of .DRDEF in writing use of .DREND use of .DREST use of .DRFIN use of .DRPTR use of .DRSET use of .DRSPF use of .DRTAB use of .DRUSE use of .DRVTB  use of .SPFUN( use of .TIMIO use of error logger$ user-defined data tables user-written! bad block replacement for9$ bad block replacement tables defining data tables for magtapes: variable-size volumes)% when bootstrap doesn't install# writing steps to follow$ writing code for SET commandsDevice handler size table discussionCDevice handler status table discussionBDevice I/O timeoutDevice identification codes list of values)Device identifier bytes listDevice names  " for peripheral devices%Device names, permanent (table)Device options ! addresses of magtape units# banner page support# changing+ CSR addresses!& disk platters on RF11 subsystem" extra device slots&& file-structured magtape handler# magtape units supported# MSCP port support## parallel printer CSR address$, Professional 300 printer port support%& RJS03 rather than RJS04 support" RL01/RL02 units supported"+ RPR02 rather than RPR02/RP03 support"' RX02 double-density only support! second device controller!$ user-supplied device handlers% vector addresses"Device ownership table discussionC .DEVICE programmed request  summary%* use in an interrupt service routine using Devices also see Device options" adding support for a device, asterisk in list! binary output  block-replaceable  File-structured. installing nonstandard! list of valid! map output nonfile-structured peripheral random access discussion  home block  random-access  random-access (figure) removing support for+! RT-11 directory-structured sequential cassette  magtape  sequential-access   sizes of (table)  source input  structures of (table) system 5 testing characteristics of, from control filesG0 testing in control files to see if loaded8Device selection,Device size table discussionCDevice size word describedDevice slots extra&Device status word contents) defined by .DRDEF$ described symbol SPECL$ correction"DEVICE system subroutine relationship to INTSET( summaryBDevice tables adding a new deviceD discussionADevice timeout applications  disk handlers! line printer" multiterminal service! discussion! timer queue element format use of .CTIMIO use of .TIMIODevice timeout supportDevice unit Device utility program See DUP DEV macro described@DEVTBL.MAC% DF03 modem operating using with VTCOM, DFLG RMON fixed offset 2641$DHALT display halt instructionADIAL VTCOM commandDIAL command using with VTCOM,&Dial-up line as console terminalD DIBOL  LINK change requirementDIBOL keyboard command# /BUFFERING option eliminated#DIFFERENCES/CHANGEBAR command"DIFFERENCES keyboard command ) /OUTPUT:filespec option correction /SLP option correction!Differences listing SRCCOM See SRCCOM DIRd   See also Directory listings calling changes to)' change to magtape operation with command string syntax corrected problems  description of halting% large magtape file restriction; options 0 and keyboard command equivalents (table)B options (table)# reading listings produced by DIR.SAV, changing default number of columns in) changing default order of listings Direct access labels (IND) $DIRECTORY BATCH commandADIRECTORY command Directory entry E.CHAN E.DATE E.JNUM E.LENG E.NAME E.USED empty  format  permanent  status word format  status word values  tentative !Directory entry status word EMPTY ENDBLK PERM PROT TENTDirectory header D.EXTR D.HIGH D.NEXT D.STRT D.TOTA format  DIRECTORY keyboard command  ) /BEGIN option position independentDirectory listing program See DIRDirectory listings , changing default number of columns in default format# excluding certain files from FILEX generating! including deleted files in 5 including files created before certain date in4 including files created since certain date in, including file starting block numbers+ including files with certain date in. including only files names and types in# including protected files in % including unprotected files in # including unused areas in, including volume ID and owner name in  reading   sorting  by creation date  by file name  by file type  by position on volume  by size  changing default of in alphabetical order in reverse order ' specifying number of columns for% starting with file you specify summary format) with octal sizes and block numbers)Directory recovery after corruption Directory segments! changing default number of6  default number of (table)' determining number of entries in sample  splitting what happens why Directory structure described  format  interchange diskette ' maximum number of possible files  special directories*"Directory-structured volumesBDIRECTORY utility program See DIR.DISABLE directive (IND)( .DISABLE OCTAL directive (IND) effect on .ASKN directive effect on .ASKS directive# .DISABLE QUIET directive (IND)% corrected relationship with /Q0DISCSR defined by .DRINSB Diskette RX01/RX02 RX33 RX50  ! working system Diskettes identifying (volume ID) initializing sizes of (table) %Disk platters on RF11 subsystem"Disks sizes of (table) $DISMOUNT BATCH commandADISMOUNT keyboard commandDISMT1.COM% replacing magtape bootstrap in;DISMT2.COMDisplacement field use in memory mappingDisplay file handler# assembling graphics programsA assembly instructionsA descriptionA exampleA linkingA linking graphics programsA subroutine summaryA usingADisplay file structureA! BASIC-11 graphics softwareA subroutine callsA!Display processor mnemonicsADistribution kit files on (table) source kit informationDJFLT system subroutine summaryC using:&DJSR subroutine call instructionA D keyboard command" use of above background job3 DL.MAC  DL.SYSDL11 interface discussion!DL11 lines, CSR address for($DL11 lines, vector address for( DL11-W( DL handler changes to5 COPY/DEVICE/RETAIN only reads/writes data area! corrected problems described &# improved hard error recovery0 invalid .SPFUN requests correctly ignored!' .READx/.WRITx request correction  RETRY=n values for  .SPFUN requests & DLX.SYS DM.MAC  DM.SYS DM handler bad block replacement $ changes to6 COPY/DEVICE/RETAIN only reads/writes data areas! described $0 invalid .SPFUN requests correctly ignored!' .READx/.WRITx request correction  RETRY=n values for  .SPFUN requests % DMX.SYS*DNAME load name register instructionADocumentation  hardware manuals  software manuals  source listings DOS/BATCH volumes copying files to and fromDouble-density diskettes( formatting in single-density modeDouble-density only RX02!Double-density only support!DOWN SETUP mode DP.MAC  DP.SYSDRAFT SETUP mode .DRAST macro ! described relationship to .DRDEF$ relationship to .FORK4 summary! using.DRBEG macro #! additional word to block 0: described  relationship to .DRDEF$ relationship to .DRPTR: relationship to .DRVTB( relationship to .FORK4 summary! using.DRBOT macro # relationship to .DRDEF$ summary! to set up primary driver7 using.DRDEF macro $ calls .QELDF! for a variable-size device) format stat argument correction" summary! use before .DRBEG# used with .TIMIO/.CTIMIO using using in a device handler.DREND macro % called by .DRBOT# described force argument; psect argument; relationship to .DRDEF$ relationship to .DRVTB( relationship to .FORK4 summary! using.DREST macro" bad block replacement table" creates block 0 information device classification relationship to .DRTAB! relationship to .SPFUN 372* replace argument storage correction/% updatable internal data tables used by RT-11 utilities(DRET subroutine return instructionA .DRFIN macro & canceling .TIMIO requests! described relationship to .DRDEF$ relationship to .FORK4 summary! using.DRINS macro & relationship to .DRDEF$ summary!1 use with installation verification routineB usingDrive See Device unit.DRPTR macro" creates block 0 information relationship to .DRBEG:# supported under all monitors with .FETCH and .RELEAS with bootstap operations with job abort with LOAD and UNLOAD.DRSET macro ' described relationship to .DRDEF$ summary! using.DRSPF macro" creates block 0 information% defines special function codes.DRTAB macro" creates block 0 information" DIGITAL-defined data tables relationship to .DREST.DRUSE macro" creates block 0 information user-defined data tables$DRVEC$ device handler block number table discussionB.DRVTB macro ( described  relationship to .DRDEF$ summary! using DS.MAC  DS.SYSDST SETUP mode&DSTAT display status instructionA .DSTATUS Information Block!.DSTATUS programmed request )! for a variable-size device)& relationship to .SETTOP and USR} summary! using DT.MAC  DT.SYS DU.ENT DU.ID DU.MAC  DU.NUM DU.PAR DU.POR DU.SYS DU.UNI DU handler See also MSCP handler (DU) addressing an MSCP disk *) asterisk as invalid port indicator bad block replacement after system crash!" during special MSCP BYPASS! failure of! .SPFUN 360 information!$ bad block replacement support from controller from handler changes to controller port numbers + corrected problems described * device status word STATU$ disk partition numbers ,, getting information about device unit MSCP unit numbers +" multiport booting procedure$ multiport booting restriction nonfile-structured reads! , nonfile-structured writes% -* port validity check at installation restrictions for RETRY=n values for + returning information on device unit( SET DU SUCCES works as documented!3 SET DUx PORT=0 supported with single port DU!$ SHOW DEVICE on SBC-11/21 PLUS SJ monitor restriction+ .SPFUN 360 and 371 with virtual jobs4 .SPFUN 372 writes and reads translation table .SPFUN requests . support for)' support for .SPFUN/ISPFN 376,377 support for .SPFUN 360 translation table labels DU.ENT DU.ID DU.NUM DU.PAR DU.POR DU.UNI translation tables changed labels for changed size of changed structure of use of IGTDUS! use of JREAD/JREADC/JREADW! use of JREADF function," use of JWRITE/JWRITC/JWRITW% use of JWRITF function- DUMP  e / assigned device as default output device calling command syntax corrected problems  description of examples halting operations with magtape options0 and keyboard command equivalents (table)B options (table)DUMP.SAV.DUMP directive (IND))DUMP keyboard commandDump utility program See DUMP DUPf  bad block scans with bootstrapping volumes  foreign  calling changes to)) changing volumes during operations command string syntax copying bootstrap * copying to or from magtapes with ' corrected magtape initialization corrected problems creating files with deleted files recovering with description of extending files  function of halting! image copying volumes with command syntax options 0 and keyboard command equivalents (table)B% valid combinations of (table) options (table)& performing bad block scans with 1 preserving output volume bad block replacement table* printing or changing volume ID with  query messages suppressing restrictions for' support for /DEVICE/FILE/WAIT option combination V5.4 error messages)! V5.4 informational prompts) with MSCP (DU) devices* DUP.SAVDutch language keyboard DUX.SYS DVC.CT DVC.DE DVC.DK DVC.DL DVC.DP DVC.LP DVC.MT DVC.NI DVC.NL DVC.PS DVC.TP DVC.TT DVC.UK DVC.VT DVM.DM DVM.DX DVM.NFDVREC$ monitor P-sect$DVSIZ device size table discussionC DW.MAC  DW.SYS DW handler! changed disk configuration changes to corrected problems1 incorrect mapping of block numbers in V5.2 relationship to .DRPTR RETRY=n values for  special function codes? .SPFUN requests support for)DWRIT$ DWX.SYS DX.MAC  DX.SYS DX handler annotated listingA changes to described  RETRY=n values for  .SPFUN requests  DXX.SYS DY.MAC  DY.SYS DY handler changes to corrected problems described  RETRY=n values for  .SPFUN requests Dynamic regionsDynamic windows DYX.SYS DZ.MAC  DZ.SYS$DZ11/DZV11 multiplexer support)DZ11 interface discussion line polling routineDZ11 up to 9600 baud DZ handler changes to corrected problems" RETRY=n values for  special function codes? .SPFUN requests support for)DZ lines supported baud rates* local lines) remote lines)DZ multiplexer support) DZX.SYS /E BINCOM option DIR option LIBR option  LINK option / MACRO option  PIP option E.CHAN E.DATE E.JNUM E.LENG E.NAME E.USED E16LST RMON fixed offset 3162EDIT+ buffers  calling changes to* character deletion" character-oriented commands command arguments (table)  command mode command repetition  commands  advance by lines change characters change lines of text  delete characters delete lines of text# display EDIT version number$' effects on output files (table)& effects on text buffer (table)* enable uppercase or lowercase mode%. execute command stored in Macro buffer$ for closing files" for creating a backup file for opening files  for reading files for writing files immediate mode) insert text, insert text saved in external buffer"! list lines of text buffer0 move location pointer a number of spaces( move location pointer to text buffer beginning# read files into text buffer, save text in external (macro) buffer#+ save text in external (save) buffer! search* search entire file for text string. search for text string and write buffer to output file* search text buffer for text string summary of ! terminate editing session terminating text listing text modification using arguments in utility! verify current line+ write text buffer to output file commands (table) command strings command syntax( current location pointer (cursor)# determining the location of1 deleting of all characters on current line display editor& format&% using with graphics terminals' error conditions+ example) exiting function of+ ignoring current command string with, immediate mode for graphics terminals( key commands (table) line-oriented commands  memory usage  no longer default editor* 1 processing terminating text buffer  filling  text mode EDIT$EDIT.SAV' changing size of text window for customizations for$ with nonstandard ESCAPE codes%Edit Backup (EB) command (EDIT)EDIT commands &Edit Console (EC) command (EDIT)'&Edit Display (ED) command (EDIT)'Editing command modeEditing commands ESCAPE) returning to editing command modeEditing commands, multiple entering erasingEDIT keyboard command% changing default file name for3 creating a file editing a file file type changing default2$Edit Lower (EL) command (EDIT)  % Editors See Text editors#Edit Read (ER) command (EDIT)$Edit Upper (EU) command (EDIT)  %&Edit Version (EV) command (EDIT)$$Edit Write (EW) command (EDIT)EDTGBL required for assembliesEDTGBL.MAC  EIS$E keyboard command" use of above background job3 EL.MAC  EL.SYS' changing size of internal buffer function of.ELAW programmed request + description of operationF relationship to .CRAW summary%# uses window definition block9 usingELBLDR macro described'ELCOPY.MAC  ELINIT function ofELINIT.MAC  $ELPTR defined by .DREND%& pointer to error logger routine&.ELRG programmed request ," clears region control block7% detaching from a global regionB" eliminating a global regionE$ eliminating a physical regionD relationship to .CRRG summary% usingELTASK.MAC  ELTIME RMON fixed offset 4224 EMPTY Empty file defined  EMT codes See also Programmed requests EMT 374 EMT 375" meaning of different valuesEMT instructions See Programmed requests EMTRTN RMON fixed offset 4003EMT Values EMT 340 .TTINR .TTYIN EMT 341 .TTOUTR .TTYOUT EMT 342 .DSTATUS EMT 343 .FETCH .RELEAS EMT 344 .CSIGEN EMT 345 .CSISPC .GTLIN EMT 346 .LOCK EMT 347 .UNLOCK EMT 350 .EXIT EMT 351 .PRINT EMT 353 .QSET EMT 354 .SETTOP EMT 355 .RCTRLO EMT 357 .HRESET EMT 374 .ABTIO .CHAIN .CLOSE .DATE .HERR .MWAIT .PURGE .RSUM .SPND .SRESET .TLOCK .WAIT EMT 375 .CDFN .CHAIN .CMKT .CNTXSW .CRAW .CRRG .CSTAT .DELETE .DEVICE .ELAW .ELRG .ENTER .FPROT .GMCX .GTIM .GTJB .GVAL .LOOKUP .MAP .MRKT .MTATCH .MTDTCH .MTGET .MTIN .MTOUT .MTPRNT .MTPS .MTRCTO .MTSET .MTSTAT .PEEK .POKE .PROTECT .PVAL .RCVD .RCVDC .RCVDW .READ .READC .READW .REOPEN .SAVESTATUS .SCCA .SDAT .SDATC .SDATW .SDTTM .SERR .SFDAT .SFPA .SPCPS .SPFUN .TRPSET .TWAIT .UNMAP .UNPROTECT .WRITC .WRITE .WRITW.ENABLE DATA directive (IND)/ using to create an indirect command file.ENABLE directive (IND)+ .ENABLE GLOBAL directive (IND)# defining global symbols with.ENABLE OCTAL directive (IND) effect on .ASKN directive effect on .ASKS directive#*.ENABLE SUBSTITUTION directive (IND) ENDBLK.END directive (IND)3"End File (EF) command (EDIT)ENDGSD block end of GSD block  .OBJ data blockENDMOD block .OBJ data block part of .OBJ module describedEnd of module block See ENDMOD block$ENSYS monitor routine discussion.ENTER programmed request - CT handler  done by .CSIGEN not done by .CSISPC on a protected file6$ on a special directory device+! on file-structured magtape  relationship to .CHCOPY  relationship to .CLOSE  relationship to .CSTAT relationship to .READxj" relationship to .SAVESTATUSs * relationship to .SERR? relationship to .SRESET relationship to .WRITx requires device handler2 summary! using$ENTRY# device handler entry point table discussionBENTRY monitor P-sect Entry point definition of $EOD BATCH commandA EOF$ defined by .DRDEF% IND special symbol$EOJ BATCH commandA.ERASE directive (IND)3Erasing a line See CTRL/UERL$G defined by .DRDEF$+ SYSGEN conditional for error logging$ERL$S+ SYSGEN conditional for error logging$ERL$U+ SYSGEN conditional for error logging$ ERLG$ $ERLOG$ERLOG pointer# in handler termination table% ERRBYT in SYSCOM area ERRCNT RMON fixed offset 3562 ERRLEV RMON fixed offset 3763 ERRLOG.DAT format& function of initializing specifying device for specifying size for ERRLOG.REL function of ERROR  ERROR$ definition  IND special symbol Error byte See ERRBYT Error codes MACRO Error Logger adding a device'% analyzing reports generated by buffers& cache memory error report  calling& with FB and XM monitors with SJ monitor described& description of devices that support! disabling under SJ monitor discussion#. file environment and error count report  file format& function of generating reports% halting under FB or XM monitor hard errors% internal buffer under SJ changing size of clearing' logging successful I/O transfers%! memory parity error report % options for generating reports& processing under the SJ monitor register usage%) running under the FB or XM monitor soft errors% statistics files, statistics-gathering under SJ monitor" storage device error report 1 summary error report for memory statistics 0 summary error report of device statistics / suspending and resuming under SJ monitor use of ELBLDR macro' uses forError logger' changed ELINIT messages for V5.4 changes to+ corrected problems 3 device error report block number now decimal( ELINIT only recognizes ERRLOG.DAT# valid devices for ERRLOG.DATError logging units supportedError logging program See Error LoggerError logging subsystem description of"Error messages for SYSGEN!Error messages new for V5.3A!Error messages new for V5.4AError processing monitor errorsErrors avoiding programming' difference between hard and soft& during copy operations ignoring  fatal preventing reset from)" intercepting monitor errors programmed requests  severity levels error fatal severe success warning system build types of assembler  clerical compiler  logical syntax ERROUTg function of options0 and keyboard command equivalents (table)BERROUT.OBJERROUT.SAVERRTXT.MAC  ESC See ESCAPE key  IND special symbol and .ASK directive and .ASKN! and .ASKS$ESCAPE command! entering multiple commands( returning to editing command modeESCAPE ESCAPE command activating immediate mode! executing editing commands* executing multiple editing commandsESCAPE key, See also ESCAPE command and ESCAPE ESCAPE command with EDIT!ESCAPE operating mode (IND).#Ethernet handlers (NC and NQ) 4 Examples re-creating EXCHANGE' VAX/VMS utility and BUP magtapes!Exchange (X) command (EDIT)  arguments (table)!Executable files creating at link time !EXECUTE keyboard command  # /BUFFERING option eliminated'Execute Macro (EM) command (EDIT)$Executing sequential commands See Indirect command filesEXIT VTCOM command EXIT$  bit in I.BLOK=Exit (EX) command (EDIT) .EXIT directive (IND)4.EXIT programmed request 0 relationship to .DEVICE summary! using Exit status of control filesEXPANDER BOX support for  IND special symbol  IND special symbolExtended memory See also Mapping See also Memory management3 addressing user buffer from a device handler, applications" arrays# buffers# data structures2 region control block26 region definition block2 window control block> window definition block9 debugging applicationsK definition device handlers+! .FETCH support limitations+ hardware concepts! interrupt service routines introduction memory management faultsJ multi-user application# overlays" pages  program exampleK programmed requests2! programmed request summaryF software concepts summary! TRAPS,BPT,IOT instructionsI use as work space$ VM device inC' which programmed requests to use2Extended memory .SETTOP%Extended memory monitor See XM monitor!Extended memory subroutines4 $BLKMV4 FINDGR4 $USRPH4 XALLOC4 XDEALC. EXTIND RMON fixed offset 4164Extra device slots& /F BUP option DIR option DUP option LINK option / PIP option F.BADR , must be cleared by handler abort code offset in fork block# offset in fork queue element? F.BLNK  offset in fork block# offset in fork queue element? F.BR4  offset in fork block# offset in fork queue element? F.BR5  offset in fork block# offset in fork queue element?F-11 processor chip support for  IND special symbolFAST VTCOM command FATAL$Fatal errors preventing reset from)FB FB.MAC  FBMON$FB monitor  advantages of description of duplicating standardA features of features of (table) introduction minimum requirements processing priorities".FETCH programmed request 2 ) always loads fresh magtape handler# disabling done by .CSIGEN fills in $FKPTR4" handler service routine for in XM monitor limitations+ not done by .CSISPC relationship to $INPTR! relationship to .DRPTR relationship to .ENTER.& relationship to .SETTOP and USR} relationship to .SRESET0 relationship to handler termination table& summary! Version 5 with magtapes# File block for QUEUE format,File exchange program See FILEXFile formats ASCII or source" CREF$ error logger& .LDA library .OBJ .REL .SAVFile maintenance BASIC-11  programs & See also File maintenance commandsFile maintenance commands summary !File maintenance operationsFile names  changingFile operations introduction  IND special symbol( supported by .TESTDEVICE and .VOL,Files ASCII See ASCII files backing up with BUP backup copy  binary See Binary format* changing volumes while manipulating  closing  comparing concatenating  copying+ between RT-11 and DOS/BATCH or RSTS. between RT-11 and interchange diskette" from DECsystem-10 to RT-11 in image mode with BATCHA& many to several output volumes  on a double-drive system on a single-drive system  one block at a time + those created before specified date 0 those created on or after specified date  those with certain date  creating  with BATCHA! creating several copies of  deleting  after printing .BAD  before copy .SYS  with BATCHA distributed list of (table) editing editing (figure) empty directory entry " excluding from an operation  extending with DUP  with SIPP ) ignoring input errors when copying indirect See Indirect command files listing! See DIRECTORY utility program loading with CAPS-11. naming object See Object Files paging permanent directory entry  preventing replacement of printing multiple copies of+ those created before specified date* those created since specified date! those with specified date with banner pages with BATCHA without banner pages protecting  ' recovering ones that are deleted removing protection from renaming  setting creation date for  size of setting upper limit on- storing storing with BUP tentative directory entry  transferring unprotecting Files created by SYSGEN Filespec See File specificationsFile specifications factoring restrictions syntax of File storage number of files  on a random-access device discussion  size of files File-structured devices See also DevicesFile types $ and interchange format changing default! changing for FRUN command2+ changing for indirect command files1 modifying default standardFile types (table) FILEXh   ASCII transfer calling changes to+) changing volumes during operations  description of" device supported by (table) function of halting image mode transfer options 0 and keyboard command equivalents (table)B options (table)! packed image mode transfer* printing or changing volume ID with  volume initialization / suppressing confirmation message during FILEX.SAVFill character in SYSCOM area Fill count in SYSCOM area  IND special symbolFILST$ bit in device status word defined by .DRDEF$ Find (F) command (EDIT) FINDGR4Finnish language keyboardFixed offsets See RMON fixed offsets FJOB$ $FKPTR defined by .DREND% setting up its value setup by user program4FLG.CP# flag bit in QUEUE file block," flag bit in QUEUE job block,FLG.DE" flag bit in QUEUE job block,FLG.HD# flag bit in QUEUE file block," flag bit in QUEUE job block,FLG.IR6 flag bit in QUEUE request acknowledgement block.FLG.JR" flag bit in QUEUE job block,& flag bit in QUEUE request block-FLG.NG6 flag bit in QUEUE request acknowledgement block.FLG.QF6 flag bit in QUEUE request acknowledgement block.FLG.RA6 flag bit in QUEUE request acknowledgement block.Floating point supportFMPUR size of impure area9Foreground/background  communications context switch with FORTRAN programs6'Foreground/background environmentForeground/background monitor See FB monitorForeground/background program communicationForeground impure area definitionForeground job" as dynamic system component communicating with  creating debugging with ODT description& differences from background job directing input to displaying status of executing linking loading device handlers privileged+ starting terminating unloading virtual-./FOREGROUND option/LINK keyboard commandForeground program runningForeground stack description $FORK FORK RMON fixed offset 4023 Fork block contents.FORK macro 4 applications registers available relationship to .DRDEF$ setting up $FKPTR simulated in SJ. special procedure in handler abort code summary"  use for I/O retries* use in an interrupt service routine with VBGEXE (restriction)$FORK pointer# in handler termination table%Fork processing& in SJ if timer support included Fork queue element  F.BADR  F.BLNK  F.BR4  F.BR5  summary?FORLIB.OBJ   including in a link / linking9% when combining with SYSLIB.OBJ FORMATi  calling changes to, 6 changing volumes during formatting or verifying command string syntax confirmation prompts default format description of DW disks on the PRO function of halting options0 and keyboard command equivalents (table)B options (table) pattern verification# pattern verification (table)! RD50/RD51 disk restriction RX33 diskette support for' suppressing confirmation prompts- using while a foreground job is loadedFORMAT.SAVFORMAT keyboard command$Formatted binary blocks in .OBJ module contentsFormatting utility program See FORMAT $FORTRAN BATCH commandA FORTRAN compiler  demonstration program running  library modules  object time system (OTS)  programming language  P-sect ordering! restrictions for  servicing interrupts! virtual arrays restriction#FORTRAN/BASIC language volumeBFORTRAN-77  restrictions for /FORTRAN[:n] TRANSFER mode qualifierFORTRAN demonstration program errors FORTRAN IV  restrictions for FORTRAN keyboard command  & FORTRAN language processor FORTRAN logical units relationship to .CHAIN FORTRAN OTS processing by LINK "FORTRAN programming language FORTRAN programs calculating workspace6 compiling  execution commands summary  linking   producing a load map  producing a load module  running  sectioning .FPROT programmed request 6 relationship to .RENAMEq requires device handler2 summary" using FPU11$Free memory list described for XM?"Free space, consolidatingFrench language keyboardFRUN restrictions forFRUN keyboard command )" changing default device for1 description file type changing default2 relating to system jobs( FSM.MAC  Function key mode (DECFKM) control sequences  to enter/exit Function keys /G BUP option  DIR option LIBR option  LINK option 0 PIP option GBL p-sect attribute General mode See .CSIGEN GENERIC100 SETUP modeGerman language keyboardGet (G) command (EDIT)   $GETBY$GETBYT pointer# in handler termination table%$GETBYT routine described/GET keyboard command)GETSTR.FORGETSTR system subroutine removed from SYSLIB* restrictions/ summary<D USR requirements+GICLOS system subroutine summaryE used by PRO/GIDISC#GIDCAL system subroutines  error codes  sample programC  used by PRO/GIDISC GIDIS.SAV graphics utilityGIDIS graphics utility See PRO/GIDISGIOPEN system subroutine summaryE used by PRO/GIDISCGIREAD system subroutine  summaryE used by PRO/GIDISCGIWRIT system subroutine  summaryE used by PRO/GIDISCGlobal .SCCA support displaying status of !GLOBAL operating mode (IND)/ !Global region control block 7 GR.ADD GR.NAM GR.SHC GR.SIZ GR.STA-Global region control block status byte8Global regions above system memory($ assigning base address for'( creating and mappingN support in SYSLIB; using shared memory&GLobal region status byte GR.AGE GR.NRF GR.PRMGlobal SCCA supportGlobal sections Global symbol directory block See GSD blockGlobal symbols  creating  definition of ' forcing inclusion of during link 1 function of  in control files$ listing in alphabetical order + processing of by LINK  referencing  resolution of .GMCX programmed request 7 description of operationD summary%# uses window definition block9 using GOLD key% use of with Single-Line Editor .GOSUB directive (IND)4.GOTO directive (IND)5 GR.ADD, offset in global region control block8 GR.AGE5 bit in global region control block status byte9 GR.CAC& GR.NAM GR.NRF5 bit in global region control block status byte9 GR.PRM5 bit in global region control block status byte9 GR.SHC, offset in global region control block8 GR.SIZ, offset in global region control block8 GR.STA. global region control block status byte8 GR.CAC bit in', offset in global region control block8 GRAPHIC SETUP mode Graphics list of files for (table)Graphics display paging See CTRL/AGraphics display terminal See VT11 display hardwareGraphics macro calls summaryAGraphics options& CSR address for VT11/VT60&# vector address for VT11/VT60' VT11/VT60 support& VT60 support&Graphics terminal display with console terminal display See CTRL/EGraphics utility GSCCA$ GSD block ENDGSD end of GSD block entry type 0, module name) entry type 1, control section name) entry type 2, internal symbol name% entry type 3, transfer address ' entry type 4, global symbol name entry type 5, P-sect name 3 entry type 6, program version identification - entry type 7, mapped array declaration  .OBJ data block part of .OBJ module described types of entries list $GTBYT defined by .DREND%! pointer to $GETBYT routine/.GTIM programmed request 8 summary" usingGTIM system subroutine  summaryA.GTJB programmed request 9 applicable to system jobs' summary" using Version 4GTJB system subroutine # jobblk parameter information4 summaryBGT keyboard command * GTLIN$.GTLIN programmed request ; implicit .UNLOCKD& relationship to .SETTOP and USR} summary" using Version 5GTLIN system subroutine getting unaltered command) summary@ USR requirements+ GTLNK$ GT OFF keyboard command AGT ON keyboard command A and EDIT' GTVECT RMON fixed offset 3542!.GVAL programmed request = compared with .PEEK[ summary" with VBGEXE /H BINCOM option LINK option 0 PIP option  QUEMAN option RESORC option H.BLEN H.BPTR H.DSTS H.DVSZ H.GEN H.READ H.SIZ+Handler file name,changing the suffixDHandler files magtape (table)%Handler global regionsHandler prefix area H.BLEN H.BPTR H.DSTS H.DVSZ H.GEN H.READ H.SIZ Handlers See Device handlersHANGUP VTCOM commandHardware components (table) computer storage medium terminal%Hardware, minimum configuration"Hardware characteristics program see SETUPHardware configuration computer displaying   languages minimum optional devices storage volume system volume terminal. when invalid for automatic installationHardware magtape handlersHardware magtapes installing support for$Hardware manuals HDERR$ defined by .DRDEF%/HELP! TRANSFER control qualifierHELP changes to, corrected problems SETUP control VTCOM command HELP.EXE creating from HELP.SAV'HELP.SAV HELP.TXT creating from HELP.SAV'HELP file" changing default device for8% changing default file name for8 Help key Single-line editor HELP keyboard command +HELP package Help text modifying'.HERR programmed request ? summary" usingHigh-level languages  See also BASIC-11 and FORTRAN High limit definition of  in SYSCOM area. program, virtual, and next free address'High-speed ring buffer description HLTERHNDLR$ bit in device status word defined by .DRDEF$ Home block( block 1 of a random access device  format  HORIZONTAL SETUP mode 12HOUR SETUP mode24HOUR SETUP mode#.HRESET programmed request A relationship to .CDFN relationship to .LOOKUPF relationship to .PURGE_ relationship to .QSETb summary" using$HSIZE device handler size table discussionCHSR$B4 SYSGEN conditional for high-speed ring buffer HWDSP$ HWFPU$50 Hz clock /I BUP option DUP option FILEX option LINK option 1 PIP option  QUEMAN optionI p-sect attribute  I.BITM" impure area relative offset;I.BLOK& checked for blocking conditions impure area offset 36: job blocking word contents=! See also Job blocking bits  I.CHWT impure area offset 10: I.CLUN" impure area relative offset; I.CMPE impure area offset 4:) pointer to end of completion queue I.CMPL impure area offset 6:3 pointer to list of completion queue elements I.CNSL impure area offset 16: I.CNUM impure area offset 26: I.CSW impure area offset 30: I.DEVL" impure area relative offset< I.FPP" impure area relative offset; I.FPSA" impure area relative offset< I.FSAV" impure area relative offset< I.IBLOK I.ICTR" impure area relative offset; I.IGET" impure area relative offset; I.IOCT impure area offset 32: I.IPUT" impure area relative offset; I.IRNG" impure area relative offset; I.ITOP" impure area relative offset; I.JID" impure area relative offset; terminal identity string* I.JNUM impure area offset 24: I.LNAM" impure area relative offset; I.MSG" impure area relative offset< I.NAME" impure area relative offset; I.OCTR" impure area relative offset; I.OGET" impure area relative offset; I.OPUT" impure area relative offset; I.OTOP" impure area relative offset; I.PCHW impure area offset 12: I.PERR impure area offset 14: I.PTTI impure area offset 20: I.QHDR impure area offset 2: I.QUE" impure area relative offset< I.RGN" impure area relative offset< I.RSAV" impure area relative offset< I.SCCA" impure area relative offset< I.SCCI" impure area relative offset< I.SCHP" impure area relative offset< I.SCOM" impure area relative offset< I.SCTR impure area offset 34:I.SERR" impure area relative offset<! RMON fixed offset 252 (SJ)0 I.SP" impure area relative offset;I.SPLS" impure area relative offset;! RMON fixed offset 254 (SJ)0 I.SPSV" impure area relative offset; I.STATE checked by context switch impure area offset 0: job state word contents= See also Job state word I.SWAP" impure area relative offset; I.SYCH" impure area relative offset< I.TERM" impure area relative offset< I.TID impure area offset 22: I.TRAP" impure area relative offset; I.TRM2" impure area relative offset<I.TTLC impure area offset 16:" impure area relative offset; I.VHII.WHI" impure area relative offset< I.WNUM" impure area relative offset< I.WPTR" impure area relative offset<I/O device timeout applications  use of .CTIMIO use of .TIMIO discussion of queued I/O  SJ monitor restriction8 system error message using interrupts without using interrupts writing a routineI/O channel block C.CSW C.DEVQ C.LENG C.SBLK C.UNIT C.USED format@I/O operations asynchronous event driven introduction synchronous I/O page depositing in3 description  examining3I/O processing in FB and XM in SJ sequence of events I/O queue operation  summary>I/O queue element  described for XM? format  in XM systems discussion, Q.BLKN  Q.BUFF  Q.COMP  Q.CSW  Q.FREE  Q.FUNC  Q.JNUM  Q.LINK  Q.PAR  Q.UNIT  Q.WCNT  I/O timeout deviceI/O transfers completing performingIABTIO system subroutine summaryAIADDR system subroutine summaryBIAJFLT system subroutine summaryC using:IASIGN system subroutine# carriage control corrections corrected problems removed from SYSLIB* summaryAICDFN system subroutine removed from SYSLIB* summaryA USR requirements+ICHCPY system subroutine" jobblk parameter correction, summaryAICLOSE system subroutine relationship to IENTER summary? USR requirements+ICMKT system subroutine" canceling an ITIMER requestE canceling ISCHED requests8 summaryAICSI system subroutine& parses options in reverse order4 summaryA! using argument from IFETCH using with IASIGN USR requirements+ICSTAT system subroutine summaryAIDATE subroutine (in FORLIB) using:IDATE system subroutine support for+IDELET system subroutine summary? USR requirements+IDJFLT system subroutine summaryC using:IDSTAT system subroutine summaryB USR requirements+IENTER system subroutine relationship to CLOSE relationship to ICSI summary? USR requirements+ IFABRT IFACTV IFBEXT IFCHAI IFCTLC IFDAT.IFDF directive (IND)7.IF directive (IND)6!.IFDISABLED directive (IND)7 IFDOL IFEKO$ .IFENABLED directive (IND)7 IFEOF$IFETCH system subroutine relationship to ICSI relationship to IDELET removed from SYSLIB* summaryB USR requirements+.IFF directive (IND)9 IFGTCC IFIND IFINP IFLEOF IFLIF.IFLOA directive (IND)8 IFMXNS RMON fixed offset 3773.IFNDF directive (IND)7.IFNLOA directive (IND)8IFPROT system subroutine summary?IFREEC system subroutine error code 1 correction4 summaryAIFREER system subroutine calling from MACRO-11 summaryB IFRVTT.IFT directive (IND)9IGETC system subroutine  removed from SYSLIB* summaryAIGETR system subroutine  calling from MACRO-11"* calling from within FORTRAN program5 can call from FORTRAN, corrections to4 dependencies on IFREER! example program for5+ offset and msize parameters reversed4# restrictions with FORTRAN-775# restrictions with FORTRAN IV5 summaryBIGETSP system subroutine# removed from SYSLIB* summaryEIGTDUS function' relationship to JREAD and JWRITE relationship to JWRITE%, returns information on DU device unit, returns information on MU device unitIGTJB system subroutine # jobblk parameter information4 summaryBIJCVT system subroutine$ summaryC using:ILUN system subroutine% corrected problems removed from SYSLIB* summaryA with $FCHNL routine /IMAGE[:n] TRANSFER mode qualifierImage mode copy   for volumesImmediate mode BASIC-11 Immediate mode (EDIT)( character insertion commands )% VT11 display hardware (table) VT11 display hardwareIMPLOC fixed offset$IMPUR pointer to impure area9 Impure area contents: defined discussion9 IN$IND IN$RUNINC directive (IND): INDI See also Control files# arithmetic operators (table) cannot run from VBGEXE: changes to,/ changing control files default file type& characters with special meaning command string syntax# control file terminating message changing eliminating corrected problems 0 corrected status report for logical disks. correctly interprets PIP and DUP errors logical operators (table) logical tests6 operating modes! testing to see if enabled7 options options (table) parameter passing " processing of command lines+ processing single command lines with /Q definition correction0# relational operators (table) restrictions for running from the console (TT:)1 .STRUCTURE returns UNKNOWN when read error4 support for blanks and tabs between operators5 suppressing dynamic allocation of a region forB symbols global local symbol tables displaying* terminating timeout count "2 IND.SAV " changing default device for8 changing default to=IND.SAV, runningIND command lines See also Control file CCL commands in comments in example IND directives in keyboard commands in labels in. maximum number of characters allowed in sampleIND control status byte CC$GBL CC$IND IN$IND IN$RUN LN$INDIND directivesj I functions of in control files separating from arguments IND directives (table)  $INDDV RMON fixed offset 4264 INDEXINDEX.IDXINDEX.IMGINDEX.SAVINDEX system subroutine& summary<DIndirect command files   accepting keyboard input building device handlers building diskette system building monitor building system" changing default device for0 commenting# compared to BATCH processing creating  within a control file default file type definition of editing entering monitor commands executing " from within a control file # executing a MACRO program in, executing with SET KMON IND in effect file type changing default1 including CTRL/C in keyboard commands in nesting changing depth4 nesting depth displaying allowed& placing responses to prompts in relationship to .CSIGEN retaining after build. running BUP from  running from UCL running SIPP from" running utility programs in* specifying an overlays structure in Start-up start-up# choosing for working system suppressing/ suppressing echo0% suppressing execution printout SYSGEN.BLD using# using commands that query in using IND with=" using INITIALIZE command in using LINK commands in! using the editor to create!Indirect Control File Processor See INDIndirect control files See also Control file& CSI and DCL command restriction  definition of( indirect command file restriction lengthy partitioning prompts using .GTLIN restrictions for running BUP from  running from UCL, setting severity of error that terminates execution% special chain exit restriction  terminating under XM monitor  using CTRL/Cs inIndirect files" See also Indirect command files!IND operating modes (table) INDSTA RMON fixed offset 4174' See also IND control status byte IND symbols deleting definitions of3 displaying definitions of*' enabling symbol substitution for1 logical See Logical symbols numeric See Numeric symbols special logical numeric string special (table) string See String symbols substituting values for( substituting values for (example) testing to see if defined7 testing type ofFINDX$M!INITIALIZE keyboard command ,/INITIALIZE option BACKUP keyboard command Initializing volumes  with FILEX $INPTR defined by .DREND% referenced by .DRAST!Input/output devices See Peripheral devicesInput/output operations See I/O operationsInput ring buffer operationInput ring buffer sizeINSCSR defined by .DRINSBINSDAT defined by .DRINSBInsert (I) command (EDIT)  INSERT mode single-line editor/INSERT option LIBRARY keyboard command INSERT system subroutine& summary<D.INSRT graphics macroAInstallation customization" features available through on RX33 diskette drive on VM deviceC preparation for procedure reading path for survey of procedures$Installation verification routines% bypassing hardware requirementD describedA techniquesAInstallation worksheetG+Installing additional device handlersInstalling handlers" See Device handlers, installingINSTALL keyboard command-% bypassing hardware requirementD discussion? relationship to .DRINS& requires device hardware@ restrictionBINTACT% used by $RQTSW monitor routine#INTEGER*4 support in SYSLIB: $INTEN INTEN .INTEN macro B discussion must precede .FORK4 registers available" relationship to .SPND/.RSUM summary" * use in an interrupt service routine using with VBGEXE (restriction)$INTEN monitor routine discussion referenced by .DRAST!$INTEN pointer# in handler termination table%Interchange diskettes# copying files to and from directory format 480INTERLACE SETUP mode INTERLACE SETUP modeInternal queuing described!Internal symbol directory block See ISD blockInternal symbols "International character sets Interpreter description of Interrupt CSRsInterrupt level counter See INTLVLInterrupt priority discussion lowering with .INTEN Interrupts described in FORTRANInterrupt service for terminals Interrupt service routines  advantages of in-line exiting) in-line instead of device handlers in XM systems registers available restricted in PAR1 restrictions in PAR2 skeleton outline structure  use of .DEVICE  use of .FORK setting up $FKPTR use of .INTEN  use of .PROTECT  use of .SYNCH  with VBGEXE (restriction) writing a routineInterrupt vectors%  list setting up the values INTLVL interrupt level counter valuesIntroduction to RT-11 creating volumes for files required forINTSET system subroutine' corrected problems& processor and device priorities removed from SYSLIB* summaryE' to service interrupts in FORTRAN-Invoking system generation command fileIOT instruction under XMIIPEEKB system subroutine) restrictions. summaryBIPEEK system subroutine) restrictions. summaryB using with IGETSP$IPOKEB system subroutine* restrictions. summaryBIPOKE system subroutine* restrictions. summaryB using with IGETSP$IPUT system subroutine+ summaryBIQSET system subroutine+* relationship to JREAD/JREADC/JREADW!+ relationship to JWRITE/JWRITC/JWRITW% removed from SYSLIB* summaryC using. USR requirements+IRAD50 system subroutine, summaryD using;!IRCVDC system subroutine-. requires queue element. summary@!IRCVDF system subroutine-. requires queue element. summary@IRCVD system subroutine- requires queue element. summary@!IRCVDW system subroutine-/ requires queue element. summary@!IREADC system subroutine01 error codes correction7 requires queue element. summary@!IREADF system subroutine02 error codes correction7 requires queue element. summary@IREAD system subroutine0 error codes correction7 requires queue element. summary@!IREADW system subroutine04 requires queue element. summary@IRENAM system subroutine4 error codes correction7 summary? USR requirements+IREOPN system subroutine5 summaryAISAVES system subroutine6 relationship to IREOPN5 summaryAISCHED system subroutine7 canceled by ICMKT requires queue element. summaryAISCOMP system subroutineg summaryD!ISDATC system subroutine89 requires queue element. summary@!ISDATF system subroutine8: requires queue element. summary@ ISDAT system subroutine89 requires queue element. summary@!ISDATW system subroutine8: requires queue element. summary@ ISD block .OBJ data block part of .OBJ module describedISDTTM system subroutine; summaryAISFDAT system subroutine; summary?ISLEEP system subroutine<. completion routine under SJ restriction2 requires queue element. summaryA using:!ISPFNC system subroutine=@! ISPFNC 376 and 377 with DU:! ISPFNC 376 and 377 with DW: requires queue element. summary@!ISPFNF system subroutine=A! ISPFNF 376 and 377 with DU:! ISPFNF 376 and 377 with DW: requires queue element. summary@ISPFN system subroutine=# example using with PRO/GIDISC ISPFN 376 and 377 with DU: ISPFN 376 and 377 with DW: requires queue element. summary@ used by PRO/GIDISC!ISPFNW system subroutine=B! ISPFNW 376 and 377 with DU:! ISPFNW 376 and 377 with DW: requires queue element. summary@ISPY system subroutineD restrictions. summaryCISR! See Interrupt service routinesItalian language keyboardITIMER system subroutineD canceled by ICMKT requires queue element.' rescheduling FORTRAN subroutines8 summaryBITLOCK system subroutineF summaryC using- USR requirements+ITTINR system subroutineF multiterminal equivalent] summary@ITTOUR system subroutineH multiterminal equivalent] summary@ITWAIT system subroutineH$ relationship to SUSPND/RESUMEl requires queue element. summaryB using:IUNTIL system subroutineI requires queue element. summaryB using:IVERIF system subroutine$ See also VERIFY system subroutine summaryD IVP.MAPIWAIT system subroutineJ relationship to JREAD" summaryA use with ISPFN=!IWRITC system subroutineJK error codes correction8 requires queue element. summary@IWRITE system subroutineJ error codes correction8 requires queue element. summary@!IWRITF system subroutineJL error codes correction8 requires queue element. summary@!IWRITW system subroutineJM requires queue element. summary@ /J DIR option PIP option  QUEMAN option RESORC optionJ-11 processor chip support forJADD system subroutineM summaryCJAFIX system subroutineN summaryC using:JCMP system subroutineN summaryCJDFIX system subroutineO summaryC using:JDIV system subroutineP summaryCJICVT system subroutineP summaryC using:JJCVT system subroutineQ summaryDJMOV system subroutineQ summaryDJMUL system subroutineR summaryD$JOB BATCH commandA Job block for QUEUE format+Job blocking bits CHNWT$  EXIT$  KSPND$  NORUN$  SPND$  TTIWT$  TTOEM$  TTOWT$  USRWT$  JOBNUM$ RMON fixed offset 322 (FB/XM)2Job numbers%Job priority%Jobs background" displaying status of loaded foregroundJob state word ABORT$ ABPND$ BATRN$ CMPLT$ CPEND$ CSIRN$ USRRN$ WINDW$ Job status displayingJob status word See also JSW CHAIN$ CHNIF$ EDIT$ GTLIN$ HLTER OVLY$ RSTRT$ SPXIT$ TCBIT$ TTLC$ TTSPC$ USWAP$ VIRT$JREADC function description of# error codes correction/ introduction to! reads entire DU device! relationship to IGTDUSJREADF function support for,JREAD function description of" error codes correction/ introduction to! reads entire DU device! relationship to IGTDUS relationship to IWAIT"JREADW function description of$ introduction to! reads entire DU device! relationship to IGTDUSJSUB system subroutineR summaryD JSW  See also Job status word bit 110 bit 12 effect on terminal input relationship to ITTINRF bit 14< effect on terminal input relationship to ITTINRG bit 3; bit 4 bit 50 bit 6" compared with M.TSTS bit 6T relationship to .TTINR relationship to .TTOUTR relationship to ITTINRF relationship to ITTOURH bit 8 in SYSCOM area. issue .MTRCTO or .RCTRLO after changingd  use of bit 10JTIME system subroutineS summaryB using:JUMP SETUP mode Jump (J) command (EDIT)  argumentsJWRITC function description of' error codes correction/ introduction to% relationship to IGTDUS% relationship to IQSET% writes entire DU device%JWRITE function description of& error codes correction/ introduction to% relationship to IGTDUS% relationship to IQSET% writes entire DU device%JWRITF function support for-JWRITW function description of( introduction to% relationship to IGTDUS% relationship to IQSET% writes entire DU device% /K DIR option DUP option LINK option 1 PIP option  QUEMAN option K52.SAVKDA50 controller support for KDJ11-A support for KDJ11-DA support for KEDo changes to- corrected problems default editor-, FIND supports most control characters/ LOCAL supports form-feeds within a range+ multiple editors reentry information uses USERRB- KED.SAV" modifying default file type?KED text editor compared to KEX virtual See KEX Kernel mode applies to .SYNCH definitionKEX as system job  compared to KED + multiple editors reentry information running from VM deviceC support for KEX.SAV# limiting memory requested by=KEX text editor See KEX Keyboard Belgium language! Canadian (French) language Danish language Dutch language Finnish language French language German language Italian language North American Norwegian language Spanish language Swedish language Swiss (French) language Swiss (German) language  United KingdomKeyboard click enabling and disablingKeyboard command options mutually exclusiveKeyboard commands abbreviating changes to error messages for expanded by KMON& function of in control files suppressing display of suppressing execution of monitor restrictions prompts radix of arguments* suppressing control file display of1 syntax# syntax illustration (sample)& syntax illustration conventions/ that should not be used in control files unrecognizedKeyboard layouts (figure)Keyboard monitor See KMONKeyboard monitor commands See Keyboard commands&Keyboard monitor command subsetsKeyboard symbols (table)Keypad editor See K52.SAV See KED.SAV Keypad mode single-line editorKeyword macro arguments description KILL Kill (K) command (EDIT)   arguments KMON &" as dynamic system component corrected problems ) default passing unaltered commands definition of) inhibiting command line processors% lower to upper case conversion relationship to .GTLIN size of+ UCF preprocessorKMON.MAC  KMON/UCF interface8KMON commands See Keyboard commandsKMONIN fixed offsetKMON overlaysKMOVLY.MAC   KSPND$  bit in I.BLOK=KT-11 discussion KT11$ KW11P$KW11-P programmable clockK-Word equivalents' /L BUP option changes to  DIR option FILEX option LD option  LINK option 1 MACRO option  QUEMAN option RESORC option SIPP option SLP option SRCCOM optionLA120 recommended setup optionsLA75 printer support for(Labels in control files defining direct access processing of .label: directive (IND) LANDSCAPE SETUP mode LANG:code SETUP mode "Language comparisons (table)Language processors  BASIC-11  FORTRAN  MACRO  Languages! See also Programming languages supported by RT-11 Language volume FORTRAN/BASICBLCL p-sect attribute  LD   calling  command string syntax  corrected problems  creating logical disks  description of! file device must be loaded# handler suffix customization options   0 and keyboard command equivalents (table)B options (table)  recursive disks messages" recursive disks restriction- recursive disks restriction correction/ restrictions for .SPFUN 372 changes for terminating  translation table labels LD.FLG LD.ID LD.NAM LD.NUM LD.OFS LD.SIZ translation tables changes to LD.FLG LD.ID LD.MAC  LD.NAM LD.NUM LD.OFS LD.SIZ LD.SYS p also see Logical disk files used with magtape; .LDA files See also Load image files described generating  1 LD handler changing suffix character described 2 special /$ option 4 translation table 3 LDREL$ used by LD handler 3 LDX.SYS!Left/Right byte equivalentsLEN system subroutineT summary<D LETCLETTER SETUP mode LG01 printer support forLG02 printer support for LIBRq   calling  changes to. command string syntax  continuing command lines  corrected problems default file types  description of function of  halting  options   0 and keyboard command equivalents (table)B combining  for macro libraries # for macro libraries (table)  options (table)  /X option not for RT-11:LIBR.SAVLibrarian  See also Library files function ofLibrarian end block .OBJ data blockLibrarian header block .OBJ data blockLibrarian utility See LIBRLibrarian utility program See LIBR Libraries list of (table) $LIBRARY BATCH commandALIBRARY command Library directory format of a .OBJ libraryLibrary end block formatLibrary files& accessing object modules within  as input to LINK  copying  creating  definition of   demonstration programs  directory of$ including all global symbols  wide  format of directories header of a .MAC library header of a .OBJ library/ including in link operations using BATCHA- including module names in directory of - including p-sect names in directory of macro  creating $ designating in MACRO command  maintaining  maintenance commands for summary  multiple definition  object creating 5 deleting global symbols from the directory of  deleting modules from  extracting modules from  inserting modules into  merging ' obtaining directory listings of  replacing modules in  updating  object libraries  processing by LINK 0 with multiply defined global entry points !LIBRARY keyboard command   .' /MACRO[:n] is names in directory"Library modules $ calling other library modules  definition of & duplicating in overlay segments -$ increasing number of for LINK processing by LINK Library references resolving Library routine list- changing amount of space allocated for 4LIGHT SETUP mode LIGHT$.LIMIT special features enabling 7LINE FEED key ODTLine printer characteristics see SETUPLine printer handlers changing CSR addresses in# changing vectors in#" choosing for working system' restrictions and workarounds forLine printers" recommended SET options for$LINK BATCH commandA LINKr  9! address space restrictions calling  changes to/ command line continuing , command string syntax  corrected problems  CREF.TMP and CF device " default file specifications  description of function of   input library modules for  input object modules for  object module processing  options  ! + 80 and keyboard command equivalents (table)B options (table)  output load module  processing  description of  prompts 9 sequence of 9 restrictions for symbol table* allowing largest possible area for 5 terminating . /V option supports all available memory! .WEAK directive correction% /XM option restriction removed/LINK.SAV, changing default output to 132-column@+ changing size of library module list. changing size of library module list of$ modifying listing page length70 modifying to change default SYSLIB device'Linker function ofLinker utility See LINKLinking a program * See also LINK keyboard command and Link operation&Linking files in diskette system )Linking monitor and device handlersLINK keyboard command  0# linking a foreground program linking a MACRO program  Linking ODTLink maps  on output device required with SPR  saved on disk suppression suppression ofLink operations  address assignment  overlay feature  producing a load map  producing a load module  program relocation  program sections # resolving library references $ resolving symbolic references  summary of commands  using BATCHALink volumeBList (L) command (EDIT)  argumentsLIST command BASIC-11  LISTING SETUP mode LISTNH command BASIC-11 /LIST option FORTRAN keyboard command  LIBRARY keyboard command  MACRO keyboard command  LKCS$ LN$IND.LNKRT graphics macroALoad image fileLOAD keyboard command 3 fills in $FKPTR4 relating to system jobs( relationship to .DRPTR relationship to .SRESET0 relationship to handler termination table& relationship to IDELET Load maps' changing default page length for7 contents of  demonstration programs  description of  producing  sample * with unmapped and virtual overlays & wide creating 7Load modules arrangement of  as LINK output  creation of  definition of  producing  relocatable code/ specifying lowest address to be used by +5 specifying a value to fill unused locations in 8 Local DL11 lines supported(Local regionsLocal sections Local symbols in control files LOCK key setting function of$.LOCK programmed request C compared to .TLOCK effect of .EXIT1 relationship to .CSIGEN summary" usingLOCK system subroutineT summaryC USR requirements+/LOG! TRANSFER control qualifierLOG VTCOM commandLogical assignments Logical deviceLogical device names assigning  to logical disks  with BATCHA deassigning with BATCHA displaying assignments of% limit on number of assignmentsC special (table)  using with BATCHALogical disk files! changing default file type;Logical disks  See also LD assigning to files ! file device must be loaded# freeing from file assignment  uses for + verifying and correcting assignments  write-enabling  write-locking Logical disk subsetting$ displaying assignments for !Logical disk subsetting handler See LDLogical job names assigningLogical name table discussionCLogical symbols (IND) defining@C# defining with .ASK directive in control files& testing to see if true or false9Logical unit number defined of a terminalLog of files$ requesting when copying files % requesting when printing files .LOOKUP programmed request E CT handler  done by .CSIGEN hardware magtape handler  not done by .CSISPC on a protected file6$ on a special directory device+! on file-structured magtape  relationship to .CLOSE  relationship to .CSTAT relationship to .ENTER. relationship to .READxj relationship to .REOPENr% relationship to .SAVESTATUSst * relationship to .SERR? relationship to .WRITx requires device handler2" seqnum paramater correction3 summary" system jobH using Version 4LOOKUP system subroutineV relationship to CLOSE relationship to ICSI" seqnum parameter correction8 summary? USR requirements+Lowercase characters EDIT $LOWERCASE operating mode (IND)/ LOWMAP RMON fixed offset 3262 Low memory definition Low memory bitmap See Bitmap LP.MAC  LP.SYS choosing renaming.LPEN graphics macroA LP handler changes to  corrected problems% file-structured device handler " relationship to .SAVESTATUS* restrictions for2 special directory structured and write only* with off-line printers LPX.SYS LS.MAC  LS.SYS choosing renaming LS handler and SHOW DEVICE command  changes to  corrected problems! CSR and VECTOR information  CTS-300 SYSGEN for PRO do not rename to LP!% file-structured device handler!0 PRO and PDP-11 SYSGEN support information"" relationship to .SAVESTATUS* restrictions for0 SET LS CSR=nnnnnn changes and information"2 special directory structured and write only* with LVP-16 printer  with off-line printers! LSI11$LSI-11 processors( not supported by distributed MDUP LSX.SYSLUN See Logical unit number /M BUP option  DIR option LIBR option  LINK option 2 MACRO option  PIP option  QUEMAN option RESORC option M.FCNT contentsR M.TFIL contentsR M.TST2 contentsS$ in multiterminal status blockR M.TSTS bit 12 relationship to .MTINT bit 6 relationship to .MTINT relationship to .MTOUTU contentsR M.TSTW contentsS$ in multiterminal status blockR M.TWID contentsRMachine language code Machine-level language  See also MACRO$MACRO BATCH commandA MACROt   assembly listing  changes to/ corrected problems demonstration program errors  running  options0 and keyboard command equivalents (table)B programming language  restrictions forMacro (M) command (EDIT)# arguments (table)#MACRO.SAV0 changing default .ENABLE/.DISABLE options>, changing default .LIST/.NLIST options># changing page listing length< MACRO-11+ increasing default work file size ofAMACRO assembler    calling  calling using BATCHA command string syntax * default file specifications (table)  error codes  files required for function control options  arguments for (table)  listing control options  arguments for (table)  options   options (table)  output from  restrictions for running  temporary work file assigning  terminating MACRO keyboard command  3MACRO language processor Macro library files  creating /MACRO option LIBRARY keyboard command MACRO programs assembling  developing  linking   producing a load map  producing a load module  sectioning $ summary of execution commands  Macros MACRO work fileMagtape handlers hardware Magtapes$ See also specific magtape devices! backing up distribution to1 bootable creating using MSB.COM3 creating using MTB.COM3 creating using MUB.COM4 how to create3 BUP changes for inhibiting rewind  multiple backups to % multivolume consistency check multivolume information must initialize  using savesets with  VAX/VMS compatibility! volume header information% changing parity and density of&! .CLOSE request recommended" copying from " copying to or from with DUP * directory of large file restriction; dumping even parity restricted9! .FETCH request recommended" FETCH under XM! file structure ! file-structured handler   #! .CLOSE programmed request " .DELETE programmed request ! .ENTER programmed request  hardware calls " .LOOKUP programmed request " .READx programmed requests " .RENAME programmed request " .SPFUN programmed requests " .WRITx programmed requests  handler files (table)% hardware installing support for$ hardware handler ! .CLOSE programmed request  exception reporting " .LOOKUP programmed request  reading and writing " .READx programmed requests  rewinding $ rewinding and going off-line $ spacing forward and backward  writing a tape mark ! writing with extended gap " .WRITx programmed requests ! 100 in/s streaming on TS05  in BUP operations' initializing for use with BUP label format 2 LOAD command and .PURGE request information"' reading tapes from other systems , replacing bootstrap for in DISMT1.COM; searching by file name # searching by sequence number  seven-track tape  Storing BUP directories TK25 TK50 automatic installation+ initialization procedure correction0 manual installation4 MSCPCK.SAV Q-bus controller checking program( TSV05. using at 100in/s during BUP operations unit addresses# units supported# user-written handlers for: using with PIP $ VAX/VMS and BUP compatibility writing tapes for RSTS/E ( writing tapes for RSX-11D and IAS  writing tapes for RSX-11M  writing to Manual system build MAP: /MAP option LINK keyboard command Map output device-   IND special symbol Mapping See also Extended memory See also Memory management control by programs default definition% for interrupt service routines privileged using $P1EXT routine1 virtual .MAP programmed request I description of operationC summary%# uses window definition block9 using with cache-bypass' MARGINBELL SETUP modeMass storage optimizing Mass storage control protocol See DU handler/MATCH option# DIFFERENCES keyboard command MAXBLK RMON fixed offset 3142MAXJOB in timer blockMBOOT.BOTMBOT16.BOT.MCALL directive useMCR operating mode (IND)0MDUP& changes in devices supported by changes to/# creating support for devices2 must build for support on LSI-11 processors$ support for DU and VM devices MDUP.AI MDUP.MM device supportA MDUP.MS device supportA MDUP.MT device supportA MDUP.MUMDUP.SAV/ nonstandard device support,modifying forAMedia calculating sufficientMEMO SETUP mode Memory  amount on system displaying+ limiting amount allocated by .SETTOP 1 minimum required organization of displaying % running in less than available* size of setting upper limit on. use of extended memoryMemory allocation swapping USR with .SETTOPMemory image files See also .SAV filesMemory image load module Memory locations modifying with LINK Memory management See also Extended memory See also Mapping relocation Memory management faults discussionJMemory management unit discussion status registersMemory parityMemory parity errors discussionJMemory parity support corrections toMemory usage bitmap See also Bitmap MEMPTR RMON fixed offset 4304 $MEMSZ RMON fixed offset 4204 $MESSAGE BATCH commandAMessage handler See MQ handlerMessage handling* FB only supports .SDAT/.RCVD/.MWAIT1/ must build FB for system .LOOKUP support1 Messages( sending to the console with BATCHA $MFPS RMON fixed offset 3622!.MFPS programmed request J summary" using with VBGEXE (restriction)MicroPDP-11/53 support forMicroPDP-11/73 support forMicroPDP-11/83 support forMini-Exchange support for use with VTCOM MM.SYSMMG$T defined by .DRDEF$ effect on .QELDF-5 SYSGEN conditional for extended memory support+ MMGT$ MM handler changes to! corrected problems# described  even parity restriction9 RETRY=n values for  SET MM CSR=n support! SET MM RETRY=n support! SET MM VECTOR=n support! support for .FETCH!* using ISPFN/.SPFUN 375 and 376 with&'MMHD.SYS hardware magtape handler$(MMHDX.SYS hardware magtape handler$ $MMPTR pointer to $MPPHY routine.MMSR3 status register% used by memory management unit MMX.SYS MONAME RMON fixed offset 4063 Monitor definition keeping smallMonitor command formatMonitor command language See Keyboard commandsMonitor commands keyboard subsets relating to system jobs(Monitor fixed offset area introductionMonitor map files" customization symbol valuesMonitor options# asynchronous terminal status batch support changing+ device timeout support error logging units supported) error message on system I/O errors .FETCH programmed request floating point support global SCCA support% high-speed ring buffer support 50 Hz clock input ring buffer size keyboard monitor commands language subset minimal subset utility subset memory parity support# month and year date rollover multiterminal support$ multiterminal timeout support output ring buffer size power failure message) programmable clock as system clock! save/set main-line PC & PS SJ timer support .SPCPS request% start-up indirect command file system job support UCLMonitor program Monitors/ See also BL monitor, FB monitor, SJ monitor, and XM monitor assembling and linking1 associating handlers with specific monitorD bootstrapping with DUP  building. customizationsD customizations available for descriptions ofG+ customizations available for (table) depositing in3 description of distributed choice of% features available in (table) list of (table) duplicating standardA examining3& identifying specially generated / identifying specially generated monitors& selection of for working system 6 system generation options available for (table)Monitor services introductionMonitor typeMonitor type and version displaying  IND special symbolMONO SETUP mode%Month and year date rollover$MOUNT BATCH commandAMOUNT keyboard command6 $MPPHY$MPPHY pointer# in handler termination table%$MPPHY routine described.$MPPTR defined by .DREND%MPTY$MQH$P2 may restrict .FETCH in XM++ restricts interrupt service routines0 SYSGEN conditional for special MQ handler( MQ handler" communicating with QUEUE*- corrected problems# for inter-job messages' may restrict .FETCH in XM+ MQH$P2 conditional() relationship to system job .LOOKUPH% restricted in PAR2 under XMH using .MRKT programmed request L relationship to .CMKT  requires queue elementb summary" usingMRKT system subroutineX canceled by ICMKT id parameter correction- requires queue element. summaryB MS.SYSMSB.COM1MSBOOT.BOT MSCPCK.SAV" TMSCP (MU) checking program# hardware handler correction% MSCP disks assigning unit numbers to# changing CRS addresses in# changing vectors in# partitioning#MSCP handler See DU handlerMSCP handler (DU) See also DU handler bootstrap loading address and contents  using MICRO-ODT ! using the switch register MSCP port support# MS handler changes to! corrected problems# described  RETRY=n values for  streaming support for! support for .FETCH!* using ISPFN/.SPFUN 375 and 376 with&'MSHD.SYS hardware magtape handler$(MSHDX.SYS hardware magtape handler$ MSX.SYS MT.SYS .MTATCH programmed request N description of operation relationship to .MTGETR summary" usingMTATCH system subroutineY summaryE MTB.COM1 .MTDTCH programmed request P description of operation summary" usingMTDTCH system subroutine[ summaryEMTEMT$ monitor P-sect.MTGET programmed request Q description of operation relationship to .MTATCHN required before .MTSET summary" usingMTGET system subroutine\ summaryE MT handler change to" corrected problems# described  even parity restriction9 RETRY=n values for  support for .FETCH"* using ISPFN/.SPFUN 375 and 376 with&'MTHD.SYS hardware magtape handler$(MTHDX.SYS hardware magtape handler$.MTIN programmed request T description of operation summary" usingMTIN system subroutine] corrected problems ocnt argument correction summaryEMTINT$ monitor P-sect.MTOUT programmed request U description of operation summary" usingMTOUT system subroutine] corrected problems ocnt argument correction summaryE .MTPRNT programmed request V description of operation summary" usingMTPRNT system subroutine^ summaryE $MTPS RMON fixed offset 3602 !.MTPS programmed request J summary# using with VBGEXE (restriction) .MTRCTO programmed request W description of operation issue after changing JSW summary#MTRCTO system subroutine^ summaryE.MTSET programmed request X description of operation requires previous .MTGET summary# usingMTSET system subroutine_ summaryE .MTSTAT programmed request Y description of operation summary# usingMTSTAT system subroutine_ summaryEMTTEMT.MAC   discussionMTTINT corrected problemsMTTINT.MAC   discussion MTTY$ monitor P-sect MTX.SYS MU.SYS MUB.COM3MU handler = See also TMSCP handler (MU) changes to" corrected problems$ corrections for00 correct unit support, CSR and vectors for% EOT correction%, getting information about device unit" hardware handler correction%* initialization procedure correction0 port initialization delay$ RETRY=n values for + returning information on device unit should load* :* .SPFUN 360 buf parameter correction0 support for) support for .FETCH"$ unit support, CSR and vectors > use of IGTDUS use of special functions = using .SPFUN 360 with$* using ISPFN/.SPFUN 375 and 376 with&Multiple definition libraries creating , enlarging LINK's directory buffer for 0 processing by LINK  Multiplexer applying to DZ11Multiplexer support)Multiport booting (DU) procedure for requires SYSGEN7 version restriction XM monitor onlyMultiterminal feature# corrected example program13 data structures  terminal control block . DBG-11 restriction with timeout support9% debugging application programs) description of programmed requests DZ11 line polling routine example program interrupt service introduction* ODT restricted with timeout support9( private console abort restriction;' programmed request error summary" programmed requests summary # PRO requires timeout support9 restrictions restrictions for  time-out polling routine use soft I/O DBG-119 use VDT9 with multiple users $ without multiterminal supportMultiterminal requests introductionMultiterminal status block contentsR contents after .MTSETXMultiterminal support  hardware# suppressing polling routinesD TRMTBL.MAC required Multiterminal system answers to createB&Multiterminal timeout support required by PRO9Multi-user application use of extended memory# MUX.SYS.MWAIT programmed request Z relationship to .RCVDxe) relationship to system job .LOOKUPH summary% usingMWAIT system subroutine` requires queue element. summaryA /N DIR option DUP option IND option LIBR option  LINK option 2 MACRO option  PIP option  QUEMAN option SLP option.NAME graphics macroANative transfer utility See TRANSFER NC.MACNC and NQ handlers restrictions 4 use of special functions 5NC handler 4 changes to# code example for# corrected problems must LOAD: restrictions for support for* NCX.SYSNesting depth indirect command files changing4 NEW command BASIC-11 NEWLINE SETUP mode NEXT Next (N) command (EDIT)   NI.MAC  NITESTCNITEST.MAC  NL.MAC  NL.SYS NL handler described ( NLX.SYSNOBCD SETUP modeNOBOLD SETUP mode NOCLICK SETUP mode NOCOMPOSE SETUP control NOCURSOR SETUP modeNODST SETUP mode NOINTERLACE SETUP modeNOLOG VTCOM command/NOLOG option BACKUP keyboard command NOMARGINBELL SETUP mode%Nondirectory-structured volumesB NONEWLINE SETUP modeNonfile-structured devices See Devices/NOQUERY option BACKUP keyboard command NOREPEAT SETUP mode/NOREWIND option BACKUP keyboard command North American keyboard NORUN$  bit in I.BLOK=!Norwegian language keyboard/NOSCAN option BACKUP keyboard command .NOSYN graphics macroA NOTABS SETUP mode NOUNDERLINE SETUP mode NOWRAP SETUP mode NQ.MACNQ handler 4 changes to# code example for# corrected problems must LOAD: restrictions for support for* NQX.SYS NU.MAC NU handler changes to# code example for# must LOAD: restrictions for support for *Null handler See NL handlerNumeric expressions& evaluation of, in control files forming, in control filesNumeric symbols (IND) decrementing' defining@A in control files incrementing: radix of  testingG NUX.SYS /O BINCOM option DIR option DUP option  LINK option  3 PIP option  RESORC optionObject files  on binary output device Object libraries  building  creating input files  header format correction# listing  updating Object module patch program See PAT'Object module relocation (figure) Object modules  adding subroutines to" combine to make a .OBJ file creating  definition of  linking FORTRAN  MACRO  linking (figure)  LINK processing of  replacing lines in updating with PAT See also PAT+Object modules, retaining system OBJs-Object programs linking Object time system (OTS)  .OBJ files format of.OBJ module format data blocks ENDGSD blocks ENDMOD blocks formatted binary blocks) general arrangement of data blocks GSD blocks ISD blocks librarian end blocks librarian header blocks RLD blocks TXT blocks  IND special symbol OCTAL operating mode (IND)0 ODT v " accessing general registers   - accessing program's internal registers ASCII terminators (table) automatic relocation back-arrow command breakpoints  removing using calculating offsets with changes to0 changing ASCII text with* changing contents of locations with clearing breakpoints  closing locations with2 closing the currently open location address commands   summary  constant register continuing execution % debugging background jobs with% debugging foreground jobs with description of  effective address search error detection executing MACRO programs format of output function of halting& initializing memory blocks with internal organization( internal registers to access with  line feed key command linking low in memory Linking with a program linking with a program" linking with overlaid files location addresses' monitor-independent variation of0" opening addressed locations  opening byte locations  ! opening location addresses  1 opening location at relative branch offset + opening locations indexed by the program counter opening locations with! opening next location with% opening previous location with, opening sequential location addresses# priority level register ($P) r # Radix-50 terminators (table) - relationship to multiterminal monitors9' relocation calculators n! and nR# relocation register commands relocation registers removing a breakpoint  removing all breakpoints  running running a program with   searching for bit patterns setting breakpoints# setting relocation registers single-instruction mode/ single-instruction mode commands (table)" start and restart addresses$ terminal interrupt processing up-arrow command! use VDT in extended memoryK2 use VDT to debug multiterminal applications% using in XM, with restrictionsG using Radix-50  using to debug a handlerD" using with display hardware word search X command ODT.OBJ OFF OHANDL overlay handler OLD command BASIC-11 ON .ONERR directive (IND):On-line debugging technique See ODTOn-line index package See INDEX.OPENA directive (IND)<.OPEN directive (IND)< OPENLOG VTCOM command.OPENR directive (IND)=Operating modes (IND)+ default settings, disabling( enabling+ global+ local+ testing to see if enabled7Operating system applications packages  description of device handlers installing generated  language processors  monitor program utility programsOperating system (figure) Optional devices hardware configuration/OUTPUT[:filespec] option with DIRECTORY/BACKUP Output device changing # changing default to terminalOutput ring buffer4 increasing space requirement in to resume job5 operationOutput ring buffer sizeOverlaid utilities list ofOverlay feature See Overlay segmentsOverlay handler extended memory ) low memory Overlay regions calculating the size of  definition of  virtual  number of  Overlays See Overlay segmentsOverlay segments  definition of calling  calling (example) 0 combining low memory with extended memory $ definition of  extended memory ! converting program to use  creating ! 7 definition of  extending with SIPP  in extended memory" low memory creating 3 definition of  description of * preserving return path when calling Overlay structure creating    extended memory % of a FORTRAN program (example)  OVLY$OVLYnn monitor P-sectOVR p-sect attribute $OWNER device ownership table discussionCOWNER$ monitor P-sect /P DIR option FILEX option FORMAT option LIBR option  LINK option 4 PIP option  QUEMAN option SLP option P1EXT RMON fixed offset 4324 pointer to $P1EXT2$P1EXT routine described1# example of use in DX handlerA* restrictions2P1 through P9 IND local string symbols Page address register discussion format Page descriptor register discussion formatPAGELENGTH:n SETUP mode Pages, correspondence between pages and APRs  in memory management unit definition Paper tape handler See PC handlerPAR See Page address registerPAR1, borrowed by $P1EXT to map user buffer10 restricted for interrupt service routines restrictions on useG+ value passed in XM I/O queue element,PAR22 restrictions for interrupt service routines restrictions on useHParameter blocks PRO/GIDIS use ofCParity changing for magtape& memory.PARSE directive (IND)= PATx + adding a subroutine to a module with calling changes to1 checksum command string syntax correction file format of description of  function of halting0 processing of duplicate PSECTs and CSECTs' processing of new global symbols" replacing module lines with% updating an object module with. updating an object module with (figure) PAT.SAVPATCH$ monitor P-sectPatch programs See PAT, SIPP, and SLPPAUSE VTCOM command PC.MAC  PC.SYS PC handler annotated listingA0 described # PD.MAC   PD.SYS PDP-11/84 support for PDP60$ PDP70$PDR See Page descriptor register!.PEEK programmed request [ summary# with VBGEXEPercent (%) sign wildcard See Wildcards.Peripheral devices  specifying See Physical device names!Peripheral devices (figure) Peripheral interchange program See PIP PERMPermanent device names See Physical device namesPermanent file defined  PF1 key% use of with Single-Line Editor Physical address definition discussionPhysical address region discussionPhysical address space with low memory overlays #Physical device names (table) Physical device name table discussionCPhysical unit number of a terminal PI.SYS PI handler changes to# corrected problems .SPFUN requestsC support for* used by PRO/GIDISC PIPy   ASCII mode copy  binary mode copy  calling  changes to1 command string syntax  corrected problems  description of function of  image mode copy   options   0 and keyboard command equivalents (table)B options (table) - terminal to output with no case change terminating  treatment of .BAD files  treatment of .SYS files  wildcards with  PIP.SAV PIX.SYSPLAS maximum size of& program's logical address space relationship to .SETTOP$PNAME& device handler permanent name table discussionA referenced by bootstrap=PNAME$ monitor P-sect PNPTR RMON fixed offset 4043!.POKE programmed request [ summary# with VBGEXE!Polling routine suppressionD PORTRAIT SETUP mode!Position (P) command (EDIT)Power failure message!PREFIX operating mode (IND)0Primary driver discussion5 entry routine6 software bootstrap6 use of .DRBOT7$PRINT BATCH commandA Printer enabling nonstandard addresses$ parallel$ CSR address$ vector address$ serial CSR address% vector address%Printer modes See SETUP/PRINTER option! DIRECTORY keyboard commandPRINT keyboard command 7% /FLAGPAGE:n option information % /NAME option specific to QUEUE ' /PROMPT option specific to QUEUE ( when running both SPOOL and QUEUE .PRINT programmed request \ multiterminal equivalentV summary# usingPRINT system subroutinea summary@ Priority device and processor discussion" lowering after an interrupt lowering with .INTEN  of jobs%Privileged and virtual jobs context switching" differences!Privileged jobs" address space available for ! background* discussion foreground+ foreground restriction XM .SETTOP*PRO/GIDISCC   corrected problems data path illustrationC GIDCAL interfaceC instruction syntaxC MACRO-11 sample programC parameter blocksC requirements to runC restrictions for restrictions when runningC $ supported software interfacesC use of PI handlerC Processor increasing speed ofC stopping theBProcessor status word See PSWProfessional 300 series clock description0 creating VM device forC printer port support% PRINT SCREEN restriction: restrictions for  support for&Professional 300 series keyboard  special function keys Professional 325 creating VM device forCProfessional 350/380 creating VM device forC formatting the diskPROGDF fixed offsetProgram counter +Programmable clock as system clockProgrammed request .SPCPSProgrammed requests   See also EMT codes addressing modes  blank arguments  channel numbers  conversion to Version 5 device blocks errors  execution extended memory 2 summaryF format for multiterminal support introduction keyword macro arguments  multiterminal summary ! on file-structured magtape  registers available  restrictions for summary using USR requirements  Version 1 Version 2 Version 3 Version 4 Version 5Programming languages BASIC-11  choosing comparing (table) DIBOL FORTRAN  hardware configuration MACRO Program relocation  Programs2 See also FORTRAN program, BASIC-11 program, and MACRO programs debugging developing developing (figure)Program sections See also P-sects absolute  blank  instruction  named relocatable Program virtual address space See PVAS/PROGRESS[:n]! TRANSFER control qualifier /PROMPT! TRANSFER control qualifier/PROMPT option LINK keyboard command  Prompts bootstrap EDIT monitor system (table) PROS$ PROT$Protecting files from deletion  PROTECT keyboard command 9$.PROTECT programmed request ] summary%* use in an interrupt service routine  use of bitmap5 usingPS See PSWPSCLKH pseudo-clock PSCLOK pseudo-clock .PSECT directive  P-sects absolute base address changing number of specifying 4 allocation of memory for  attributes  attributes (table)  contents of  creating a  definition of  description of  extending in the root / ordering in memory ! ordering in memory (table) 1 specifying starting address of in the root 8Pseudo-devices MQ, NL writing handlers forPSW description# referenced by .MFPS/.MTPSJK, relationship to active page registers $PTBYT defined by .DREND%! pointer to $PUTBYT routine/ $PTWRD defined by .DREND%! pointer to $PUTWRD routine0.PURGE directive (IND)?.PURGE programmed request _ relationship to .CHCOPY+ relationship to .FETCH with magtapes"! relationship to .LOOKUPFH relationship to .SERR?) relationship to LOAD with magtapes" summary# using with magtapes"PURGE system subroutinea in place of CLOSE summaryAPushbutton console using to bootstrapA!Pushbutton console (figure)A $PUTBY$PUTBYT pointer# in handler termination table%$PUTBYT routine described/ PUTSCR PUTSTR.FORPUTSTR system subroutineb removed from SYSLIB* restrictions/ summary<D USR requirements+ $PUTWR$PUTWRD pointer# in handler termination table%$PUTWRD routine described0!.PVAL programmed request = compared with .POKE[ summary#$ to change default .ENTER size- with VBGEXEPVAS definition of  illustration of  structure of  /Q BINCOM option DIR option  DUP option  IND option LINK option 4 PIP option  QUEMAN option RESORC option Q$BLKN defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$BUFF defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$COMP defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$CSW defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$FUNC defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$JNUM defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$LINK defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$PAR defined by .QELDFa% offset in XM I/O queue element- Q$UNIT defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element- Q$WCNT defined by .QELDFa" offset in I/O queue element% offset in XM I/O queue element-Q.BLKN  defined by .QELDFa offset in .SYNCH block% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element- referenced by $GETBYT/ referenced by $PUTBYT0 referenced by $PUTWRD0Q.BUFF   defined by .QELDFa- meaning for a special directory device* offset in .SYNCH block, offset in completion queue element?% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element- referenced by $MPPHY. updated by $GETBYT/ updated by $PUTBYT0Q.COMP   defined by .QELDFa offset in .SYNCH block, offset in completion queue element?% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element- relationship to .SYNCHQ.CSW   defined by .QELDFa offset in .SYNCH block% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element- Q.ELGH defined by .QELDFa" length of I/O queue element% length of XM I/O queue element- Q.FREE Q.FUNC  check if .SPFUN request) defined by .QELDFa offset in .SYNCH block% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element-Q.JNUM  defined by .QELDFa% offset in I/O queue element % offset in XM I/O queue element-Q.JUM" offset in I/O queue element>Q.LINK   defined by .QELDFa offset in .SYNCH block, offset in completion queue element?% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element-Q.PAR  defined by .QELDFa% offset in I/O queue element >% offset in XM I/O queue element- used by $P1EXT2Q.UNIT  defined by .QELDFa% offset in I/O queue element > % offset in XM I/O queue element-Q.WCNT   defined by .QELDFa- meaning for a special directory device+ offset in .SYNCH block, offset in completion queue element?% offset in I/O queue element > ' offset in synch queue element?% offset in XM I/O queue element- QCOMP RMON fixed offset 2701.QELDF macro a called by .DRDEF effect of $MMG$T- relationship to .DRDEF$ relationship to .FORK4 summary#.QSET programmed request b corrected problems effect of .EXIT1 relationship to .RCVDxe relationship to .READxi relationship to .SRESET relationship to .TWAIT relationship to .WRITx restricted in PAR1H restrictions summary# using QUEMAN{   calling command string syntax# continuing on several lines  options  0 and keyboard command equivalents (table)B options (table)QUEMAN.SAV" changing default device for4" choosing for working system/QUERY option DELETE keyboard commandQUEUE  calling changes to2 corrected problems displaying status of example program. file block format, how to queue files*- job block format+$ request acknowledgement block. request block format- restrictions for) resuming or restarting output from  suspending output from terminating% used with SPOOL (restrictions) when also running SPOOL ' wildcard symbols on banner pagesQueue listing contents of removing a job from the QUEUE$QUEUE.REL! changing size of work file" choosing for working system QUEUE.SAV allowing first form feed; Queued I/O discussion Queue element formats>Queue element offsets defined by .QELDFQueue package description of function ofQueues& completion queue element format? fork queue element format? I/O queue element format>' summary of queue element formats>! synch queue element format?! timer queue element format@QUEUE work file changing size of QUFILE.WRK Queue package work file& setting default for deletion of QUIET operating mode (IND)1/R DIR option  DUP option LD option  LIBR option  LINK option 5 PIP option  QUEMAN option R.BADD% offset in region control block7 R.BNWD* byte offset in region control block7 R.BSIZ% offset in region control block7 R.BSTA* byte offset in region control block7 R.CACH bit in' R.CACH' relationship to .CRRG' relationship to GR.CAC' R.EXITR.GBAS with RS.BAS)- word offset in region definition block)R.GID defined by .RDBDFi 6( offset in region definition block4 used by IFREER used by IGETR! R.GLGH defined by .RDBDFi 6R.GNAM defined by .RDBDFiR.GSIZ defined by .RDBDFi 6( offset in region definition block4 used by IFREER used by IGETR!R.GSTS defined by .RDBDFi 6( offset in region definition block4 RS.BAS bit in' RS.CAC bit in' RS.NSM bit in' R.NAME used by IFREER used by IGETR! R.SHAR R.STOPR50ASC system subroutineb summaryD using; RA80 disk device name  size of  support for RA81 disk support for  IND special symbolRAD50 system subroutinec summaryD using;Radix conversion table . setting octal default, in control files0Radix-50 character set!Radix-50 support in SYSLIB;Random-access devices See also Devices discussion  home block Random number generators-RANDU system subroutine support for-RAN system subroutine support for- RC25 disk device name  restriction size of  support forRCHAIN system subroutined relationship to CHAIN summaryC .RCTRLO programmed request d multiterminal equivalentW summary# usingRCTRLO system subroutined multiterminal equivalent^ summaryC.RCVDC programmed request e relationship to .SDATxw requires queue elementb summary% using.RCVD programmed request e relationship to .SDATxw) relationship to system job .LOOKUPH requires queue elementb summary% use with .MWAITZ using.RCVDW programmed request e relationship to .SDATxw requires queue elementb summary% RD31 disk support for RD50 disk device name  size of  support for RD51 disk device name  size of  support for RD52 disk support for RD53 disk support for.RDBBK macro h base=n parameter'( described6 summary% using.RDBDF macro i described6 relationship to .RDBBKh summary% usingRead (R) command (EDIT) .READC programmed request i% completion routine information3 requires device handler2 requires queue elementb SJ monitor restriction8 summary# used with XC/XL+ using.READ directive (IND)? corrected problemsReading path for installation.READ programmed request i for messages between jobsH relationship to .CHCOPY" relationship to .SAVESTATUSt relationship to .SPFUN requires device handler2 requires queue elementb SJ monitor restriction8 summary# used with XC/XL+ use with .WAIT using.READW programmed request i requires device handler2 requires queue elementb SJ monitor restriction8 summary# used with XC/XL+ using.READx programmed requests CT handler  hardware magtape handler ! on file-structured magtape REENTER keyboard command; after .EXIT relationship to .EXIT0 with EDITRegion control block cleared by .ELRG7 described6 discussion R.BADD R.BNWD R.BSIZ R.BSTARegion definition block defined by .RDBDF6 described4 discussion R.GID R.GSIZ R.GSTS R.NAME reserved by .RDBBK6 Regions dynamic global local staticRegion status Byte R.BSTARegion status word R.GSTS described5 RS.AGE RS.CGR RS.CRR RS.EGR RS.EXI RS.GBL RS.NAL RS.NEW RS.UNM Registers saving using CALL$F verifying contents ofRegisters available after .FORK after .INTEN after .SYNCH after interrupt# at handler abort entry point' at handler interrupt entry point error logger&( in handler I/O initiation section  in SET codeREL p-sect attribute #.RELEAS programmed request 2 after .FETCH3" handler service routine for relationship to .DRPTR sometimes ignored3 summary# .REL file# See also Relocatable image files) calculating absolute addresses for  creating " creating for foreground job 5 described  without overlays  with overlays" $RELOCRelocatable code% highest address in load module 0Relocatable expressionsRelocatable file See .REL fileRelocatable file format See .REL fileRelocatable image fileRelocatable load module creating "Relocatable program sections  Relocation by memory management unit definition (Relocation bias for object modulesRelocation directory block See RLD blockRelocation registers ODT Reloc-code p-sect attributes $RELOC pointer# in handler termination table% /REMOTE! TRANSFER control qualifier !Remote DL11 lines supported(REMOVE keyboard command< to free a device slot?/REMOVE option LIBRARY keyboard command .REMOV graphics macroA Removing device support+RENAM$ RENAME keyboard command = .RENAME programmed request q on a protected file6! on file-structured magtape  requires device handler2 summary# usingRenaming files cassette usersB magtape usersB#.REOPEN programmed request r summary# usingREPEAT SETUP modeREPEAT system subroutinee err argument information8 summary<DREPLACE command BASIC-11 REPLACE mode single-line editorRequest acknowledgment block for QUEUE format.Request block for QUEUE format-RESET SETUP control VTCOM commandRESET keyboard command>Resident monitor See RMON RESORC|   calling cannot run from VBGEXE: changes to3 corrected problems  description of DU:/D option display3 function of options  0 and keyboard command equivalents (table)B options (table) relationship to .DRINS& restrictions for terminatingRESORC.SAVResource program See RESORCResource utility program See RESORC Responses changing dialog inappropriate SYSGEN%Restoring BUP volumes and files.RESTR graphics macroA Restrictions FORTRAN  general handler monitor$ multiterminal special feature  peripheral devices processor Professional 300 series  programmed request specific handler utilitiesRESUME keyboard command? relating to system jobs)RESUME system subroutinee relationship to SUSPNDk summaryCRETAIN SETUP controlRetaining work files..RETURN directive (IND)? RETURN key executing commands function ODT RF.MAC   RF.SYS RGWDSZ Ring buffer high-speed output5 increasing space requirement in to resume job5 sizeRing buffers for terminal service high-speed operation%RJS03 rather than RJS04 support" RK.MAC   RK.SYSRK05 loading bootstrapB RK05 disk device name  size of RK06 loading bootstrapBRK06/RK07 disk device name  size of RK06/RK07 Handler See DM handlerRK07 loading bootstrapBRK11 DECpack See RK05R keyboard command; compared with RUN  description RK handler annotated listingA changes to$ corrected problems RETRY=n values for RKX.SYSRL01 loading bootstrapB RL01/RL02, units supported"RL01/RL02 disk device name  size of RL01/RL02 handler See DL handlerRL02 installation information loading bootstrapB RLD block( entry type 1, internal relocation3 entry type 10, location counter modification$ entry type 11, program limits' entry type 12, P-sect relocation! entry type 13, not defined1 entry type 14, P-sect displaced relocation0 entry type 15, P-sect additive relocation/ entry type 16, P-sect additive displaced( entry type 17, complex relocation& entry type 2, global relocation2 entry type 3, internal displaced relocation0 entry type 4, global displaced relocation/ entry type 5, global additive relocation. entry type 6, global additive displaced0 entry type 7, location counter definition .OBJ data block part of .OBJ module described  types of entries list $RLPTR defined by .DREND%RMNUSR monitor P-sect $RMON RMON fixed offset 00 RMON ( abort code to handler entry point corrected problems definition of description  monitor P-sect& relationship to device handlers size of+RMON base address in SYSCOM areaRMONFB.MAC   RMON fixed offsets 0 BLKEY CHKEY CNTXT CONFG2 CONFIG $CSW $DATE DFLG discussion0 E16LST ELTIME EMTRTN ERRCNT ERRLEV EXTIND FORK GTVECT I.SERR I.SPLS IFMXNS $INDDV INDSTA JOBNUM LOWMAP MAXBLK MEMPTR $MEMSZ $MFPS MONAME $MTPS P1EXT PNPTR QCOMP $RMON SCROLL SPSTAT SPUSR STATWD SUFFIX SYINDX SYNCH $SYSCH SYSGEN SYSUPD SYSVER SYUNIT $TCFIG $TIME TTKB TTKS TTPB TTPS USRARE $USRLC USRLOC values0RMON impure area I.BITM I.CHWT I.CLUN I.CMPE I.CMPL I.CNSL I.CNUM I.CSW I.DEVL I.FPP I.FPSA I.FSAV I.IBLOK I.ICTR I.IGET I.IOCT I.IPUT I.IRNG I.ITOP I.JID I.JNUM I.LNAM I.MSG I.NAME I.OCTR I.OGET I.OPUT I.OTOP I.PCHW I.PERR I.PTTI I.QHDR I.QUE I.RGN I.RSAV I.SCCA I.SCCI I.SCHP I.SCOM I.SCTR I.SERR I.SP I.SPLS I.SPSV I.STATE I.SWAP I.SYCH I.TERM I.TID I.TRAP I.TRM2 I.TTLC I.VHI I.WNUM I.WPTR RGWDSZ TTYIN TTYOUT WNWDSZRMONSJ.MAC   RMONxx.MAC RMSRES (RSX-11) libraryRO p-sect attribute  Rollover month and year dateRONLY$ bit in device status word defined by .DRDEF$ Root See Root segmentRoot segment definition of  rounding up the size of 7RP03 magtape support&*RPR02 rather than RPR02/RP03 support"RQDX3 disk controller (DU) restriction$RQTSW monitor routine discussion## to request a scheduling pass" RS.AGE bit in region status word5 defined by .RDBDFi RS.BAS& set by .RDBBK' RS.CAC& set in .RDBBK' RS.CGR bit in region status word5 defined by .RDBDFiRS.CRR bit in region status word5 defined by .RDBDFi 6 RS.EGR bit in region status word5 defined by .RDBDFi RS.EXI bit in region status word5 defined by .RDBDFi RS.GBL bit in region status word5 defined by .RDBDFiRS.NAL bit in region status word5 defined by .RDBDFi 6 RS.NEW bit in region status word5 defined by .RDBDFi RS.NSM& set in .RDBBK'RS.UNM bit in region status word5 defined by .RDBDFi 6 RSTRT$RSTS volumes copying files to and from RSUM.RSUM programmed request  effect of .TWAIT relationship to .SRESET summary&$RT11 BATCH commandA RT11 monitor P-sectRT11AI.SYS monitorRT11BL.SYS monitorRT-11 computer system description of$RT-11 computer system (figure)RT-11 conditionalsC$RT-11 directory-structured devices See DevicesRT-11 Emulator use with TRANSF RT-11 operating system See Operating systemRT11PI.SYS monitorRT11SJ.SYS monitorRTBL.MAPRTDATA monitor P-sect RTEM$ RTMONCRTMON.REL RTSJ.MAPRTXM.MAPRubout key $RUN BATCH commandA RUN command BASIC-11  ODT.RUN IND.SAV SYSGEN.COMRUN keyboard command? background job compared with R  description MUBASIC restriction RUNNH command BASIC-11 Running SYSGEN.COMRW p-sect attribute RX01/RX02 disketteRX01 diskette device name  size of RX01 distribution kit installation information PDT-11/150 bootableRX02 diskette device name  installation information size of &RX02 double-density only support!RX11 loading bootstrapBRX211 loading bootstrapB RX33 diskette compared to RX50" format diskette BL-FM5AA-MC" format diskette BL-FM5AB-MC formatting procedure! FORMAT utility support for$ manual installation procedure support forRX50 diskette compared to RX33 device name  installation information size of  support for /S BINCOM option BUP option  DIR option  DUP option  FILEX option FORMAT option LINK option 5 PIP option  QUEMAN option RESORC option  SLP option SRCCOM option TRANSF option SAV p-sect attribute SAVE SETUP controlSave (S) command (EDIT)! Save/set main-line PC & PSSAVE command BASIC-11 Save image files See .SAV files examining and modifying See SIPPSave image patch program See SIPPSAVE keyboard command@/SAVESET option BACKUP keyboard command '.SAVESTATUS programmed request s changes to*& conditionally valid with .ENTER* relationship to .ENTER. relationship to .LOOKUPF relationship to .PURGE_ relationship to .REOPENr summary# using .SAV files See also Memory image files creating  described.SAV image file formatSCCA global.SCCA programmed request v for FB and XM only% summary#SCCA system subroutinef for FB and XM only& summaryC Scheduler discussion" how it works# Scheduling definedSCOMP system subroutineg summary<D Scope-code function of  p-sect attributes SCOPY system subroutineh corrected problems err argument correction err argument information8 len argument clarified' summary<DSCRATCH (SCR) command BASIC-11 Screen cursor setting type of turning on and offScreen scrolling JUMP or SMOOTH .SCROL graphics macroA SCROLL RMON fixed offset 3021.SDATC programmed request wy relationship to .RCVDxe requires queue elementb summary& using.SDAT programmed request w relationship to .RCVDxe) relationship to system job .LOOKUPH requires queue elementb summary& use with .MWAITZ using.SDATW programmed request wy relationship to .RCVDxe requires queue elementb summary&SDH.SYS * SD handler must LOAD: support for*SDHX.SYS *SDS.SYS *SDSX.SYS *.SDTTM programmed request { summary$ usingSearch commands (EDIT)SECNDS system subroutineh instead of .GTIM9 removed from SYSLIB* summaryBSecond controller&Second device controller support!SELECT VTCOM commandSEND VTCOM changing default speedC VTCOM command $SEQUENCE BATCH commandA!Sequential-access devices  See also Devices cassette  magtape #Serial printer vector address%!.SERR programmed request ? error codes@ relationship to .DELETE relationship to .ENTER. summary$ usingSETCMD system subroutinei summaryC SETCOLOR SETUP mode SET CYCLE single-line editor.SETD directive (IND)@SET DU CSR0=nSET DU CSR1=nSET DU CSR2=nSET DU CSR3=nSET DU RETRY=n error logger not required"SET DU VEC0=nSET DU VEC1=nSET DU VEC2=nSET DU VEC3=n.SETF directive (IND)BSET keyboard command@SET keyboard commandsO% conditions individually parsed CRO DDP DLP DMP DUQ DUxQ DWR DXxR DYxS DZxS EDITS ELT ERRORT examples EXITU how they work& information passed in registers KMONU LDxU LPU LSW MMY MTZ MUZ NCZ NQZ PDx[ R4 and R5 not available relationship to .DRSET' RK[ SET ERROR effect SET EXIT NOSWAP relationship to .EXIT0' relationship to .SETTOP and USR} SET EXIT SWAP relationship to .EXIT0 SET TT: NOFB relating to system jobs) SET TT options# status word bit definitions SET TT QUIET relationship to .GTLIN< SET USR NOSWAP relationship to .SETTOP|# relationship to LOCK/UNLOCKU size limits SL[ SP\ table format in handler TERM] TT] use of .DRSET USR_ VM_ WILD_ XC_ XL`SET LD CLEAN with nested logical disks.SETL directive (IND)@SET LS GRAPH* corrects some PRINT SCREEN problems:SET LS NOGRAPHSET LS WIDTH=n maximum width is 32767"SET MS CSR2=nSET MS CSR3=nSET MS CSR4=nSET MS CSR5=nSET MS CSR6=nSET MS CSR7=nSET MS CSR8=nSET MS CSR=nSET MS VEC2=nSET MS VEC3=nSET MS VEC4=nSET MS VEC5=nSET MS VEC6=nSET MS VEC7=nSET MS VEC8=nSET MS VECTOR=nSET MU [NO]SUCCESSET MU CSR0=nSET MU CSR1=nSET MU CSR2=nSET MU CSR3=nSET MUn: DEFALT$SET MUn: DENSE=1600$SET MUn: DENSE=6250$SET MUn: PORT=x$SET MUn: UNIT=x$SET MU RETRY=nSET MU VEC0=nSET MU VEC1=nSET MU VEC2=nSET MU VEC3=n.SETN directive (IND)ASET NQ CSR=nSET NQ VECTOR=nSET NU CSR=nSET NU SHOWSET NU VECTOR=n.SETO directive (IND)@SET OptionsSET options in effect displaying SET option table defined by .DRSET'.SETS directive (IND)ASET SL KEDSET SP FLAG=n) relationship to /FLAGPAGE=n option .SETT directive (IND)B"Setting hardware characteristics see SETUP .SETTOP programmed request |& for privileged jobs, XM .SETTOP*# for virtual jobs, XM .SETTOP, in extended memory% in XM monitor~- limiting amount of memory allocated by 1 restrictions special features for enabling 7 summary$ summary of effects. used with KEX= using& with XM monitor, non-XM .SETTOP(" with XM monitor, XM .SETTOP)SET TT QUIETSET TT SCOPE default for all monitors SETUP" changes to4 clock modes  BCD CLOCK SHOW DATE[:dd:mm:yy] DST 12HOUR 24HOUR NOBCD NODST TIME[:hh:mm:ss] controls" COMPOSE DATA DEFAULT HELP NOCOMPOSE RESET RETAIN SAVE SHOW TYPE corrected problems description of device restrictions! GENERIC supported on VT200 indicated defaults introduction to1 nonuniform line printer modes and controls restrictions for , SMOOTH supported on PDP-11 processors$ summary of modes and controls!% terminal and printer modes  BOLD CLEAR DENSE DOWN DRAFT  GRAPHIC  HORIZONTAL  LANG:code  LETTER  LISTING MEMO  NOBOLD  NOTABS  NOUNDERLINE  NOWRAP  PAGELENGTH:n  TABS:n TEXT  UNDERLINE UP  VERTICAL WRAP  terminal modes  ANSWERBACK:/message/ BLOCK CAPS CLICK COLOR COLOR on COLOR 132COLUMNS  80COLUMNS  CURSOR$ CURSOR supported under VT200 DARK GENERIC100 INTERLACE JUMP  LANDSCAPE LIGHT MARGINBELL MONO NEWLINE NOCLICK NOCURSOR& NOCURSOR supported under VT200  NOINTERLACE NOMARGINBELL NONEWLINE NOREPEAT PORTRAIT REPEAT SETCOLOR SHIFT SMOOTH  UNDERSCORE VT100 VT52 terminals valid terminals for. uniform line printer modes and controls valid abbreviations forSETUP.SAVSETUP commands description of valid destinations forSETUP control commands example of syntaxSETUP keyboard commandASETUP mode commands command syntax example of syntaxSET VM BASE=nnnnnn$ relationship to SET VM SIZE=0 with VM deviceCSET VM SIZE=0) relationship to SET VM BASE=nnnnnn with VM deviceCSET VM SIZE=nnnnnnSEVER$ definition  IND special symbol.SFDAT programmed request  relationship to .RENAMEq requires device handler2 summary$ using.SFPA programmed request   relationship to .CNTXSW  summary$ usingSHIFT SETUP modeSHIFT key SHOW  SETUP control VTCOM commandSHOW keyboard commandD3 includes logical disk subsetting information  with SET LD CLEANSHOW keyboard commands  SHOW DEVICE:DU! new DU status information SHOW JOBS relating to system jobs) SHOW MEMORY$ to get size and base of RMON+& to get size of loaded handlers+ to get size of USR+!SHOW QUEUE keyboard commandSingle-density format* writing on double-density diskettesSingle-job monitor See SJ monitorSingle-line editor changes to6 changes to command saving$ continuation line restriction:% control characters restriction cycling through commands deleting characters with deleting lines with+ executing a command line edited with function keys (table)  function of  GOLD key  help key  HELP utility support for INSERT mode moving cursor with  PF1 key % redisplaying current line with! redisplay line before last relationship to .TTYIN relationship to ITTINRG REPLACE mode) reproducing last command line with ( restoring deleted characters with% restoring deleted command line restrictions for saving a command SET SL KMON recommended stores multiple commands switching characters with turning off  turning on # using the keypad for editing virtual jobs restriction SIPP} ' advancing through files by bytes ASCII mode- backing up by bytes through files with- backing up by words through files with Base? prompt calling changes to5+ changing from word mode to byte mode checksum commands (table) command string syntax$ /C option with CCL correction corrected problems# creating a command file with2 creating only a command file as output with description of dialog display+ extending files and overlay segments % extending non-overlaid program 2 extending program with extended memory overlays only 1 extending program with low and extended memory overlays6 extending program with low memory overlays only  file searches ASCII  Radix-50  function of halting input command file creating with BINCOM inserting ASCII values$ inserting Radix-50 characters4 /L option with write-locked device correction% making modifications permanent + modifying only locations you specify octal mode Offset? prompt+ opening and modifying locations with options (table)! overlaid files information+ overlaid file without /A restriction;% prompting for an overlaid file Radix-50 mode' recalling previous dialog prompt " running from a BATCH stream, running from an indirect command file Segment? prompt- suppressing modification of input file verifying changes made by SIPP.SAV- installing customization symbol values SJ.MAC   SJFB.ANSSJ monitor advantages of& completion routines restriction8 description of duplicating standardA features of features of (table) introductionSJ timer supportSL See Single-line editor SL.SYS SLEDI$ SLKMO$SLMIN changes to SLMIN.SYS smaller SL handler $SLOT defined in SYSTBL.MACA0 limits number of logical name assignmentsCSLOW VTCOM command SLP  ) adding lines to a source file with audit trail disabling disabling generation of enabling specifying size of# specifying start column for backup file suppressing calling changes to6 checksum  command file creating with SRCCOM command string syntax, creating a double-spaced listing with' creating a numbered listing with- deleting lines from a source file with  description of ! formatting output file for function of halting input command file$ creating using a text editor creating with SRCCOM options options (table), replacing lines in a source file with  size of source line to update commands (table) update line format update text ending starting SLP.SAV SLX.SYSSMOOTH SETUP mode SOB macro  summary$ SOFT RESET performing a Software defined operating systemSoftware (figure)!Software customizationsG choosing getting symbol values forSoftware kit distributed components ofSoftware manuals Software Performance Report See SPRSoftware updates installingSoftware vectors%Source comparison program  See also Source comparison See SRCCOM Source file comparison program See SRCCOMSource files See also ASCII files adding lines to changing device" choosing for working system comparing See also SRCCOM deleting deleting lines from  list of (table) modifying See SLP replacing lines in required for system build Source input device ,Source language patch program See SLPSource listings SP# see Spool Package pseudo-handler SP.BRK, SP.CLR, SP.DTR- SP.MAC   SP.OFF- SP.SRD, SP.STS- SP.SYS  IND special symbolSpanish language keyboard.SPCPS programmed request   summary& using2Special (single-character) mode for terminalSpecial Chain Exit See .EXITSpecial chain exit" from indirect control files  restrictionSpecial function codes>? defining using .DRSPF DW handler? DZ handler?( invalid codes ignored by handlers1 NC handler? NQ handler? PI handler?Special functions See .SPFUN programmed requestSPECL$ bit in device status word defined by .DRDEF$  SPEEDC SP FLAG=n SPOOL set command SP FORM0 SPOOL set commandSPFUN$ bit in device status word defined by .DRDEF$ .SPFUN programmed request  bit in device status word* check Q.FUNC) CT handler  described( DM handler .SPFUN 373 correction) DU handler . blk argument .SPFUN 360 information! .SPFUN 360 support& .SPFUN 376 and 377 information< wcnt argument DW handler& .SPFUN 376 and 377 information< DX handler  DY handler  DZ handler! for a variable-size device* for DL handler & for DM handler % function codes hardware magtape handler MU handler .SPFUN 360 information$ .SPFUN 374 information<! on file-structured magtape  requires device handler2 SJ monitor restriction8 summary$ used by PRO/GIDISCCC used with XC/XL+ use of .WAIT using SP handler changes to$" relationship to .SAVESTATUS*2 special directory structured and write only* support for+ SP KILL SPOOL set command SPLITC /2 option informationSPLIT.SAV Splitting a directory segment what happens why  SPND$  bit in I.BLOK=!.SPND programmed request  effect of .TWAIT relationship to .SRESET summary& using SP NEXT SPOOL set command SP NOFORM0 SPOOL set command SP NOWAIT SPOOL set command SP NOWIDE SPOOL set command/SPOOL! TRANSFER control qualifier SPOOL changes to6 corrected problems  description of displaying status of flag page support   output device assignment running requirements for restrictions for set commands list of1 SET conditions require banner page support:* starting from indirect command file" supports only single device:$ using VM as SPOOL work device when also running QUEUE SPOOL.REL changing output device@ changing work file size@" choosing for working system SPOOL.SYS# see also Spool Package work file created by SPOOL.REL@Spool Package$ comparison with Queue package function ofSpool Package pseudo-handler device assignmentSpool Package work file device assignment size allocationSPOOL status byte  ACTIVE  DATIME  ERROR  INTEN  KILL  NEXT  OFF  ON  PUTSCR  SHOW  SPR  & for specially generated monitor guidelines for submittingB SPSTAT RMON fixed offset 4144 bit definitions8! See also SPOOL status byte  SPUSR RMON fixed offset 2721) used by special directory devices* SP WAIT SPOOL set command SP WIDE SPOOL set command SPX.SYS SPXIT$SQUEEZE keyboard commandGSqueeze operation" squeezing the system device  squeezing volumes SRC: SRCCOM  calling changes to7 command string syntax corrected problems% creating SLP command file with description of differences listing format of including form feeds in interpreting halting* ignoring comments during comparison1 ignoring spaces and tabs during comparison* including blank lines in comparison' including change bars and bullets in differences listing, including trailing blanks and tabs during comparison options0 and keyboard command equivalents (table)B options (table) processing of files+ setting number of lines for matching2 specifying audit trail for SLP command file. specifying number of lines to match for wildcards with1 wildcards with /OUTPUT:filespec correctionSRCCOM.SAV5 changing insertion/deletion characters used by /D option#.SRESET programmed request  performed by .HRESETA relationship to .CDFN relationship to .LOOKUPF relationship to .PURGE_ relationship to .QSETb summary$ usingSRUN restrictions forSRUN keyboard commandH changing default deviceD! changing default file typeD description' /NAME:name option can be numeric relating to system jobs(SST See Synchronous system trapsStack definition of  increasing size of2 modifying address of the 2( overflow from completion routines2STACK$ monitor P-sectStack pointer caution with .CHAIN during .EXIT1 in SYSCOM areaSTARTA.COMSTARTF.COM  corrected problems with SPOOL.START graphics macroA Starting address in SYSCOM areaStarting RT-11$ See Bootstrapping the system.START keyboard commandI after .EXIT relationship to .EXIT0STARTS.COM %Start-up indirect command files " See also Indirect command filesStart-up messagesSTARTX.COM  STASK$$STAT device handler status table discussionBSTAT$ monitor P-sect.STAT graphics macroA Static regions( not applicable to privileged jobsStatic window for a virtual job( not applicable to privileged jobs /STATISTICS! TRANSFER control qualifier STATU$Status registers in memory management unit STATWD See also DCL status word RMON fixed offset 3663 .STB file as input to LINK  third linker output file ST handler must LOAD:.STOP directive (IND)D.STOP graphics macroA Storage medium definition of random-access See DevicesStorage volumes hardware configuration initializing loading protecting files usingStorage volumes (figure)String symbols (IND) breaking into substrings concatenating definingA( testing for alphanumeric or RAD50F  IND special symbolSTRPAD system subroutinej err argument information8 summary<D .STRUCTURE directive (IND)D Subroutines$ calling within a control file4 list of (table)' returning from, in control files?SUBSTITUTE (SUB) command BASIC-11 'SUBSTITUTION operating mode (IND)1SUBSTR system subroutinek summary<D  IND special symbol SUCCS$ definition SUFFIX RMON fixed offset 4124SUFFIX mode (IND)1Suppressing link mapsSUSPEND keyboard commandI! interaction with scheduler# relating to system jobs)Suspension of a programSUSPND system subroutinek relationship to RESUMEe summaryCSWAP.SYS need for Swedish language keyboard&Swiss (French) language keyboard&Swiss (German) language keyboard Switch register console using to bootstrapA&Switch register console (figure)A SWREG$  IND special symbol.SYG file type renaming.SYG master files SYINDX RMON fixed offset 3643Symbolic references resolving  Symbols global  in control files internal Symbol substitution (IND) enabling1Symbol table  Symbol table definition file See .STB fileSymbol table overflow correcting with LINK /P 4Symbol tables (IND) deleting definitions from3 displaying contents of*  IND special symbol.SYNC graphics macroA SYNCH RMON fixed offset 3242.SYNCH block contents.SYNCH macro ( does not use an I/O queue element# executes with kernel mapping registers available" relationship to .SPND/.RSUM special error return summary$ * use in an interrupt service routine uses completion queue usingSYNCH queue element formatSynch queue element  Q.BUFF  Q.COMP  Q.CSW  Q.LINK  Q.WCNT  summary?Synchronous system traps discussion and listI $SYSCH RMON fixed offset 2440SYSCOM area% See also System communication area and LINK  introduction .SYS files PIP treatment of   SYSGEN See also SYSGEN features word RMON fixed offset 3723 bit definitions8 referenced by bootstrapBSYSGEN.ANSSYSGEN.BLD.  SYSGEN.BLD to build systemSYSGEN.CND   required for assembliesSYSGEN.COM SYSGEN.DEV SYSGEN.MON /SYSGEN.MON and SYSGEN.DEV to build systemSYSGEN.TBL  SYSGEN conditionals in a device handlerSYSGEN features word ERLG$ FPU11$ MMGT$ MPTY$ MTTY$ RTEM$ STASK$ TIMER$ TIMIT$SYSGEN responses changing default inappropriateSYSLIB AJFLT CALL$F CHAIN CLOSEC CONCAT CVTTIM DEVICE DJFLT GETSTR GICLOS GIOPEN GIREAD GIWRIT GTIM GTJB GTLIN IABTIO IADDR IAJFLT IASIGN ICDFN ICHCPY ICLOSE ICMKT ICSI ICSTAT IDELET IDJFLT IDSTAT IENTER IFETCH IFPROT IFREEC IFREER IGETC IGETR IGETSP IGTDUS IGTJB IJCVT ILUN INDEX INSERT INTSET IPEEK IPEEKB IPOKE IPOKEB IPUT IQSET IRAD50 IRCVD IRCVDC IRCVDF IRCVDW IREAD IREADC IREADF IREADW IRENAM IREOPN ISAVES ISCHED ISDAT ISDATC ISDATF ISDATW ISDTTM ISFDAT ISLEEP ISPFN ISPFNC ISPFNF ISPFNW ISPY ITIMER ITLOCK ITTINR ITTOUR ITWAIT IUNTIL IWAIT IWRITC IWRITE IWRITF IWRITW JADD JAFIX JCMP JDFIX JDIV JICVT JJCVT JMOV JMUL JREAD! JREADC! JREADF, JREADW! JSUB JTIME JWRITC% JWRITE% JWRITF- JWRITW% LEN LOCK LOOKUP MRKT MTATCH MTDTCH MTGET MTIN MTOUT MTPRNT MTRCTO MTSET MTSTAT MWAIT PRINT PURGE PUTSTR R50ASC RAD50 RCHAIN RCTRLO REPEAT RESUME SCCA SCOMP SCOPY SECNDS SETCMD STRPAD SUBSTR SUSPND TIMASC TIME TRANSL TRIM UNLOCK VERIFYSYSLIB.OBJ   additional services9 changes to9! changing default device of'' extracting overlay handlers from  introduction need for  processing by LINK SYSLIB functions  channelA character string<D data transfer@ date and time: device and fileA file-oriented? GIDCALE global regions; INTEGER*4*: C miscellaneousE program suspension: Radix-50; radix-50D RT-11 servicesB summary? timerA SYSLOW SYSMAC.MAC from SYSMAC.SML listingBSYSMAC.SML changes to: description introduction! macros for device handlers, macros for interrupt service routines% modifying system macro libraryC" splitting to get SYSMAC.MAC SYSPTR SYSTBL.MAC edit to add a new handler@& module containing device tablesA  IND special symbolSystem build automatic  binary output device  creating diskette system" default device requirements diskette assembling and linking assembling files COPY commands errors  linking files  diskette contents fourth diskette second diskette system diskette third diskette diskette working system errors files to retain free storage requirements indirect command files   manual map output device procedure $ procedure for diskette system required free blocks  required source files  source input device  SYSGEN.BLD to perform SYSGEN dialog- binary output device- building entire system. building monitors. device and unit number- map output device- retaining system OBJs- retaining work files.& using SYSGEN.MON and SYSGEN.DEVSystem communication area See also SYSCOM area ERRBYT JSW SYSPTR TTFILL TTNFIL UFLOAT USERPC USERRB USERSP USERTOSystem conditionalsC changing, defining,+ individual keyboard monitor commandsC in SYSGEN dialog  user defined System configuration word See also CONFIG BATCH$ CLK50$ CLOCK$ FBMON$ FJOB$ GTLNK$ HWDSP$ HWFPU$ KT11$ KW11P$ LKCS$ LSI11$ QUEUE$ SLEDI$ SLKMO$ USR$!System configuration word 2 See also CONFG2 BUS$ CACHE$ CIS$ EIS$ GSCCA$ LDREL$ LIGHT$ MPTY$ PDP60$ PDP70$ PROS$ SWREG$ VS6$0 XITSW$System device  building diskette system building disk system displaying VM asCSystem device handlers creating5 description  discussion4System disketteSystem generation altering command files! bad block replacement (DU)7% building one monitor at a time changes to7! changes to DW device build# changing responses to dialog* cleanup, corrected problems/ correct generation of TMSCP conditionals CTS-300 with answer files default answers dialog device options  monitor options monitor questions dialog questions (new)8! features available (table) from VM deviceC correction to0 introduction to list of files for (table) multiport booting (DU)7 need for on disk system# on RX01/RX02 diskette system on small system& PROCTS.ANS for Professional/CTS! question numbers (changed)8 questions, summary ofA, system conditionals (new and changed)9 terminating! unloads handlers it loadedSystem generation options$ displaying those in effect  System I/O error messageSystem jobs$% applicable programmed requests' characteristics$ communicating with ) See CTRL/X design& effect on memory space&# equivalent to foreground job KEX editor as ! LOAD handlers restrictions logical names% .LOOKUPH' /NAME:name option can be numeric privileged scheduling& starting virtualSystem job support introductionSystem Library See SYSLIB.OBJSystem macro library  introduction listingB modifying SYSMAC.SMLCSystem source files System state conditions requiring in I/O processing switching asynchronously switching synchronouslySystem status how to getSystem subroutine library calling conventions/ capabilities& channel numbers' completion routines( restrictions) conventions' device blocks* FORTRAN/MACRO interface0 introduction subroutine argument block0 subroutine register usage1 system restrictions. using&System utilities minimum on system volumeSystem volume backing upB creating example of hardware configuration# including overlaid utilities limiting components on loadingSystem volume (table) SYSUPD RMON fixed offset 2771 SYSVER RMON fixed offset 2761$SYSWT monitor routine( run after all completion routines$ to check job blocking SYUNIT RMON fixed offset 2741  IND special symbol /T DIR option  FILEX option IND option LINK option 6 PIP option  RESORC option  SLP option SRCCOM option TRANSF option T.AST* two words in terminal control block T.CNF2' offset in terminal control block % second terminal configuration word descriptionT.CNFG' offset in terminal control block  terminal configuration word descriptionT.CNT' offset in terminal control block T.CSR' offset in terminal control block T.FCNT, byte offset in terminal control block T.ICTR' offset in terminal control block T.IGET' offset in terminal control block T.IPUT' offset in terminal control block T.IRNG' offset in terminal control block T.ITOP' offset in terminal control block T.JOB, byte offset in terminal control block T.LPOS, byte offset in terminal control block T.NFIL, byte offset in terminal control block T.OCHR, byte offset in terminal control block T.OCTR, byte offset in terminal control block T.OGET' offset in terminal control block T.OPUT' offset in terminal control block T.OTOP' offset in terminal control block T.OWNR' offset in terminal control block T.PRI' offset in terminal control block T.PTTI, byte offset in terminal control block T.PUN, byte offset in terminal control block T.RTRY' offset in terminal control block T.STAT' offset in terminal control block  terminal status word descriptionT.TBLK, seven words in terminal control block T.TCTF, byte offset in terminal control block T.TFIL, byte offset in terminal control block T.TID' offset in terminal control block T.TNFL, byte offset in terminal control block T.TTLC' offset in terminal control block T.VEC' offset in terminal control block T.WID' offset in terminal control block T.XBUF, three words in terminal control block T.XCNT, byte offset in terminal control block T.XFLG, byte offset in terminal control block T.XPRE' offset in terminal control block T-11 processor chip support for/T:n DUP option TAB key with EDITTABS:n SETUP mode TC11 loading bootstrapBTCB See Terminal control block TCBIT$ $TCFIG RMON fixed offset 4244 TENTTentative file defined TERMID.SAV /TERMINAL! TRANSFER control qualifier Terminal (figure)Terminal configuration word T.CNF2 description T.CNFG descriptionTerminal control block defined description format  patchingTerminal devices (figure)Terminal handler See TT handlerTerminal I/O control characters introduction limitations0 sets bit in AST word when input available4 sets bit in AST word when output buffer empty special modeTerminal interface options baud rates of DZ lines* CSR addresses DZ multiplexer,first*! CSR address for DL11 lines(% DZ11/DZV11 multiplexer support) DZ11 multiplexer support) DZ multiplexers supported) introduction'! local DL11 lines supported( local DZ lines supported)" Remote DL11 lines supported( remote DZ lines supported) vector addresses DZ multiplexer,first*$ vector address for DL11 lines(Terminal modes See SETUPTerminal output resuming See CTRL/Q suppressing See CTRL/O suspending See CTRL/STerminals See also Console! changing default output to console different types defined displaying status of hardware configuration interrupt service local remote" recommended SET options for$ recommended setup options for restrictions setting width of  switching the console using more than one* using without multiterminal supportTerminal service input ring buffer in RMON output ring buffer, remote terminal sets bits in AST word ring buffersTerminal status asynchronous displaying Terminal status word T.STAT descriptionTerminating program execution See CTRL/CTerminating SYSGENTermination of a program!.TESTDEVICE directive (IND)G corrected problems support for ,.TEST directive (IND)F corrected problems.TESTFILE directive (IND)ITEXT SETUP mode Text buffer pointerText cursor mode (DECTCEM) introduction  to enter/exit Text editors" choosing for working system for hard copy terminals for video terminals multiple using KEX RT-11 running under XM Text file format See ASCII filesText information block See TXT blockTIM$IT defined by .DRDEF$TIMASC system subroutinel instead of .GTIM9 summaryB using: $TIME! RMON fixed offset 320 (SJ)2 system time Time See also Date displaying  entering internal format{) maintained by system clock support  set by .SDTTM{