DATE: 15 AUGUST 1991 Incorporating chgs from Linda Banche, Don Bridgewater (Using the RT--11 System Message Manual\USM_SEC) Eventually (maybe) sections 1 thorugh 6 should become Part 1, "Error Conditions and Recovery Procedures". and sections 7, 8, and 9 should become "Messages".

This manual lists RT--11 operating system diagnostic messages, the single-line (SL) editor (command-line) diagnostic messages, hardware error conditions, types of RT--11 system failures, and suggested recovery procedures for each situation.

Consult other documentation for explanations of messages from programs that are not a part of the RT--11 operating system and use the INDEX utility if you need help in finding information related to RT--11. Error messages from the KED/KEX editor programs and from the BASIC--11, FORTRAN IV, and MACRO--11 languages, previously documented in this manual, are now documented in their respective program or language manuals. (Finding System Error Messages and Recovering from Errors)

(lSm_sec) lists all the system diagnostic messages of RT--11, Version 5.6. These messages are listed alphabetically, first by the program that displayed them, then by the error code, and finally by the message text. Under each message is an explanation of it and a possible way or ways to correct the situation.

You may use either DCL commands or system utility commands to recover from error conditions. Both are described. The (Sug_book) contains a list of DCL commands; the (sum_book) describes associated utility program commands.

Some error messages, however, describe error conditions that you cannot resolve. When you receive a message of this type, you should submit a Software Performance Report (SPR) to Digital. An SPR is a form that customers who are in-warranty or have purchased support services can use to report faults in the software and to suggest product improvements. (System Error Message Format\emf_sec)

RT--11 system error messages begin with a question mark. For example: ?KMON-F-Invalid option

or: ?PIP-E-Protected file already exists ()

These messages are in the format:

(?ProgramName--ErrorLevel--MessageText\bold)

where: (3\1\14\) (\(Program Name\bold)\ is the name of the program that found the error. The program may be the command interpreter (KMON or CSI) or any one of the utilities to which KMON forwards the command. For example, PIP (in the preceding example) is one of the utilities that the COPY command uses.) (\(Error Level\bold)\ is a single letter indicating the severity of the error. The Error Level can be one of the following.

(3\6\12) (Error Level\ Meaning \ Effect) (I\ Information\Command execution continues. The program detected a condition of which you should be informed. The message appears at the terminal or in the listing file. The condition may affect execution at a later time and may require future action. ) (W\ Warning\Command execution continues. The program detected a condition that may cause errors in execution. Corrective action may be necessary. The message appears at the terminal or in the listing file. ) (E\ Error\Command execution may terminate. The program detected an error that causes other errors during execution. Corrective action is necessary. The message appears at the terminal or in the listing file. ) (F\ Fatal\Execution terminates. The program detected a serious error. You must enter another command to continue processing. The message appears at the terminal or in the listing file. ) (U\ Unconditional Abort\Execution terminates. A serious error occurred that prevents further processing.) ) (\\ You can use the monitor SET command to change the effect of the severity level on the system's response. In particular, these settings affect the execution of indirect command files. See the (sug_book) for a description of the SET ERROR command. ) (\ (Message Text\bold)\ is the error description.
Since error messages are in alphabetical order, the first digit or letter of the error message text has been used for alphabetizing and other characters have been ignored. For example, the following error message is alphabetized using the letter e; the characters ("<>") are ignored: ?EDIT-F-"<>" error; no command(s) executed ) (System Error Message References\sem_sec)
Some symbols appear in messages in this manual. These symbols are (general) references to (specific) names or values, which are copied into the message from the work you are doing. They are:

(multipage) (2\20) (Symbol\Meaning) (()\ A label, name, or other text that RT--11 copies into a message from the program you are using. In some message descriptions, aaaaaa may be replaced by a descriptive word, such as () or ().) (first) (()\ A device specification that RT--11 copies from one of your commands.) (\ A file specification that RT--11 copies from one of your commands.) (()\A numeric value that RT--11 reports as partof a message---usually an address, offset, or count total---giving its value at the time of the message. In some message descriptions, nnnnnn may be replaced by a descriptive word such as (
) or ().) (a\ A single character that RT--11 fills in---usually the single-letter abbreviation for a file or command option.) (last) (n\ A single digit that RT--11 fills in---usually the unit number in a device specification. ) (nnn\ A 3-digit number, such as a firmware or hardware revision number or a block number.) (x\ A command option that is copied into messages from commands you have typed.) (IND and CTI Bus-Based Processor Bootstrap Message Format\isp_sec)
The RT--11 Indirect Control File Processor (IND) uses the preceding error message format but also adds the line in the control file that caused the error. The format for control-file error messages is: ?IND-ErrorLevel-MessageText Line In Control File
In addition, if a control-file error occurs during a data input/output transfer, IND prints both a primary and a secondary message (further defining the error condition) plus the line in the control file that caused the error. IND error messages dealing with input/output transfers have the format: ?IND-ErrorLevel-Primary Message Secondary Message Line In Control File
CTI Bus-based processor bootstrap software error messages are also not in the format described in the preceding paragraphs. See (p3s_sec) for the description of these messages. ****** HERE ADD (INCREASING STORAGE AND MEMORY RESOURCES) (DIAGNOSING SYSTEM FAILURES) ****** (Increasing Storage and Memory Resources\ism_sec)
Some RT--11 system errors result from insufficient free memory space or insufficient space on a storage volume. Using one or more of the procedures listed below may eliminate the problem. If, by using the methods listed below, you still cannot provide adequate storage or memory resources for your application, move the application to a system with larger capacities, if possible. (Enlarging Storage Space\ess_sec)
During an output operation, an error message may indicate that your output volume has insufficient space or, if the volume is directory structured, that there is no room for a new entry in its directory. Try one or more of the following corrective actions: (unnumbered) Delete unnecessary files from the output volume, perhaps transferring them to a backup volume. Use another volume with more space. Specify an explicit output file size by using the /ALLOCATE option or the size option on the output file specification. Compress the volume by using the monitor SQUEEZE command or the DUP /S option. This creates the largest possible empty space on the volume by consolidating all the free blocks into one area. It also maximizes efficient use of the directory space. If directory overflow persists, you can allocate more directory segments on another volume by using the monitor INITIALIZE/SEGMENTS command or the DUP /N option and then transferring the files to this volume. Alternatively, you can create several logical devices on the physical device by using the MOUNT and DISMOUNT commands. If device overflow persists, use a larger volume---for example, from RX02 diskette to RK05 disk or from RK05 disk to RL02 disk.
If these methods do not provide sufficient space, see the (VFF_BOOK) for more details about the directory structure of devices and the allocation of files. (Increasing Memory Resources\imr_sec)
Many error messages indicate insufficient room in main memory. The following sections present some guidelines to help you use memory efficiently. (Increasing Memory Availability\ima_sec)
The following methods make more memory available without requiring you to redesign the program: (unnumbered) Use the SHOW command to find out which device handlers are loaded; then use the UNLOAD command to take unnecessary device handlers out of memory. Do not unload handlers that are needed to run a foreground or system job. Terminate and unload the foreground program or one or more system jobs. Use the single background (SB) monitor, which requires approximately three-quarters the amount of space needed by the foreground/background monitor. Use the SET USR SWAP command (see the (sug_book)) to allow USR swapping. If you create a monitor through system generation, do not add any features to the monitor that you do not need. Each feature you select adds to the size of the monitor in memory. In a multiterminal system, for example, support for each additional terminal you select adds approximately 200 (decimal) words to the resident monitor. Use the completely virtual environment provided by any of the mapped monitors. Most RT--11 utility programs use the completely virtual environment automatically when SET RUN VBGEXE is in effect. (Decreasing Program Size\dps_sec)
In general, each of the following methods reduces the maximum amount of memory a program requires at one time: (unnumbered) Use single buffering instead of double buffering. Use smaller I/O buffers. Decrease the maximum number of channels open simultaneously. Overlay the program or break the code into smaller modules for more efficient overlaying. Remove any testing code no longer needed. Use algorithms that need less main memory. Transfer more data storage to mass storage devices. Break the program into several programs to permit chaining between them. Use the extended memory overlay feature with one of the mapped monitors so only your program's root needs to be resident in low memory. See the (sum_book) for a description of extended memory overlays. Use the SET RUN VBGEXE command with one of the mapped monitors. Most RT--11 utilities can run in the completely virtual environment and will run in that environment whenever SET RUN VBGEXE is in effect. See the (SUG_BOOK). (Diagnosing System Failures\sf_sec)
An RT--11 system failure occurs whenever the currently running program stops unexpectedly or suspends execution, leaving the system in what appears to be a nonfunctioning state. Most system failures fall into one of three categories: (unnumbered) Those that cause a return to the keyboard monitor Those that cause a monitor halt Those that result in an indefinite program loop
Each failure is explained in detail below. While attempting to analyze a system failure, keep in mind any new or unusual system features, such as user-written device handlers, a complex application program, or a special-purpose device.
When the system fails, follow this general procedure. Examine the programmer's console immediately after the failure. Then use the programmer's console to examine the program counter (PC), the stack pointer (SP), the general-purpose registers (0 through 5), and certain memory locations. However, if your processor is an LSI--11, 11/03, 11/23, 11/23 Plus, 11/24, 11/44, 11/55, 11/73, 11/83, or 11/84, 11/93, 11/94, use the on-board ROM ODT to determine the cause of the halt. See the processor handbook for your PDP--11 for instructions on using ODT, the programmer's console, or the ROM ODT.
The first five of the following questions are useful for finding the cause of a failure. Later questions are useful in special situations. This section should help you to determine the cause of the system failure and also to distinguish between user errors and system errors. In this section, text preceded by asterisks (**) is meant primarily for experienced system programmers who have access to monitor source listings, but all users should read this text for general knowledge. (numbered) Did any message appear on the terminal? Is the processor halted or looping? What is the value of the program counter in either case? If the processor is looping, do characters typed on the keyboard echo on the console? Does CTRL/C have any effect? Is the halt or loop in a device handler? Are the devices ready to run? (Check the line printer, if present.) Has code in the handlers been corrupted? What are the contents of location 54, which points to the base of RMON, and location 46, which is the USR load address? The location of the halt or the loop may be determined by comparing the value of the program counter with the numbers in the preceding locations. If the program counter is higher than the base of RMON or is within 2K words (010000 bytes, octal) of the start of the USR, the halt or loop occurred in the monitor, and the difference between the numbers gives the offset into the monitor code. What is the value of the stack pointer and the first several elements in the stack? Has the stack overflowed; is the stack pointer less than 400? **What are the contents of the registers? **Has monitor code been corrupted? Determine from a source listing, if available, the integrity of significant areas in RMON, especially the area immediately below the monitor stack. **Can you determine from a source listing, if available, what code is indicated by the halt or loop? **What are the contents of the monitor data base---for example, the address of the running job or the addresses of the loaded handlers? **Can the problem be localized to a single job? If so, what are the contents of the job impure area---the job status word, channel status words, the queue elements? **Can the problem be localized to a single device? If so, what are the contents of the handler data, handler queue, and device status registers? **Has the job impure area in the FB and the XM monitors been corrupted? Has the stack for the foreground or system job overflowed? (Failures That Cause a Return to Keyboard Monitor\ftcr_sec)
Whenever you see the prompting character---a dot---on the left margin of the console terminal, control has returned to the keyboard monitor. If you also receive a monitor message, one beginning with (?MON--), you can find its meaning and corrective action in (sm_sec).
**If only the monitor dot---without a message---appears, an interrupt through an empty vector to code at location 0 or another unexpected jump to location 0 is indicated. The following example shows the code stored at locations 0 and 2: LOCATION OCTAL VALUE CODE COMMENT 0 040000 BIC R0,R0 ;To ensure a hard exit 2 104350 .EXIT ;Back to KMON
**Possible causes of this type of error include the following: (unnumbered) A spurious interrupt request appeared A vector was never filled A filled vector was not protected under the FB monitor An .ASECT was attempted into a protected vector An application program was run with an incorrect vector address The program has a JMP or a JSR instruction with an undefined label The program has an RTS instruction with no valid return address on the stack (Failures That Cause Monitor Halts\ftcm_sec)
Monitor halts occur in high memory above the address in location 54, the RMON base address pointer. The most common symptoms are the absence of the monitor prompt and the lack of an echo when you type characters.
When a monitor halt occurs, do not attempt to restart the system by pressing the continue key ((CONT)) on the processor or by using the micro-ODT P command. You must reboot the system. The following sections describe the kinds of halts that occur under the different monitors and the problems involved in USR swapping and stack overflow. Each description of a halt or loop in the following sections includes a symbol name. Use the symbol name to find the sections of code in the monitor source listings that reveal offsets from location 54. If you are working with the distributed version of RT--11, see the link maps on the distribution kit for accurate offsets. If you created the monitor you are working with through system generation, the symbol names described here are accurate, but you must refer to the link map created by system generation to determine the offsets. Therefore, for any monitors you generate through system generation, such as a version of FB with multiterminal support, use the symbols in your link map to identify the appropriate code. (Monitor Halts\fbe_sec)
All monitors have halts, but those that can occur for a specific version of particular monitor depend on features you choose or exclude during system generation.
The extended memory monitor has the same halts as the foreground/background monitor, but the offsets into RMON differ for the two monitors. Make sure that you refer to the appropriate link map to determine the symbol value (see Note in (ftcm_sec)).
Any other halts that occur may indicate that the monitor code is corrupted. So, check for logic errors in the user program and reboot the system. (numbered) Absolute location 26 (octal)
See (?MON--F--Power fail halt).
If the message (?MON--F--Power fail halt) is disabled during system generation, this halt is executed on power up and power down. If the message is enabled, the monitor issues the message and halts. Absolute location 116 (octal)
See (?MON--F--Memory error (
)).
If memory parity support is disabled---the default for the distributed versions of the monitors---the monitor executes this halt when it detects a memory parity error. The last item in this list of foreground/background and extended memory monitor halts describes the monitor action when the message is enabled. Absolute location 244 (octal)
The monitor executes this halt if a floating-point interrupt occurs under a monitor that does not have floating-point support. Programs that use floating-point instructions must be run under monitors with floating-point support. Floating-point support is included in the distributed foreground/background monitor and is also available for the extended memory monitor through system generation. **Check the symbol SYHALT. The monitor executes this halt in two general situations. The message (?MON--F--System halt) may precede the halt. (alphabetic) If the message (?MON--F--Power fail halt) is enabled---the default for the distributed version of the monitors---the monitor issues the message and executes this halt on power up. On power down, the monitor executes this halt, but without supporting the overhead of the message. The monitor executes this halt when it traps to 4 or 10 or when it encounters a memory error, but only when it is executing critical monitor or interrupt code---in interrupt service routines, device handlers, or selected portions of the monitor. (When the monitor is not executing critical code, it issues a message---(?MON--F--Memory error (
)), (?MON--F--Trap to 4 (
)), or (?MON--F--Trap to 10 (
))---aborts the program, and returns to KMON.)
Check the contents of the stack pointer (register 6). If the contents are less than 400 (octal), stack overflow has caused the trap. (STo_sec) has further information about stack overflow.
The address where the trap occurred is at the top of the stack. If this address is within user code, check for an error in an interrupt service routine or a device handler. Verify that handlers are not fetched into areas that will be destroyed by data buffers or overlaid when the USR swaps. (uss_sec) has further information about USR swapping.
Check for a reference to a nonexistent device. The reference causes the handler to trap to 4 when it attempts to access the device registers. You can reduce the possibility of this error by deleting from the system volume all handlers for devices that are not part of your system.
If the address where the trap occurred is in the monitor, calculate the corresponding monitor offset by subtracting the contents of location 54. Consult a source listing of the monitor and compare the monitor you are running to the sources. The monitor or data in the monitor or user region, such as queue elements and channel status tables, may be corrupted.
Hardware problems that cause bus timeout cause this halt because they trap to 4. This type of hardware problems is extremely rare, however; consider it only as a last resort. (USR Swapping\uss_sec)
Many system failures occur when the USR swaps over important memory areas, such as device handlers, queue elements, and completion routines; the latter may occur when you are running FORTRAN programs that use SYSLIB calls. One way to detect this type of failure is to use the SET USR NOSWAP command and to rerun the program---if enough free memory exists. If the failure does not occur again, USR swapping is probably causing the problem. The USR may be linked with overlays or with a different bottom address. Make sure that the USR does not swap over any important areas within the program. See the (SSL_book) and the (sim_book) for details concerning the swapping. (Stack Overflow\sto_sec)
Stack overflow occurs when the stack is pushed through its low limit. Whether it may be detected depends on the location of the stack. The normal location for the user background stack is 1000, with a low limit of 400. Most PDP--11 processors detect stack overflow at 400 and generate a trap to 4. (Some processors---for example, the PDP--11/03---do not provide this feature.) If the stack is located elsewhere, overflow detection is not supported by the RT--11 system.
Stack overflow is usually a fatal condition. RT--11 treats all detected user stack overflows as fatal and aborts the offending program. The monitor aborts the program with the (?MON--F--Trap to 4 (
)) message.
The (FORTRAN Object Time System) (OTS) may cause user stack overflow because it uses large amounts of stack space. Extra stack space can be allocated for background jobs by using LINK/BOTTOM to raise the program base. Extra stack space can be allocated for foreground jobs at link time by using the (stacksize\ITALIC) argument with the LINK/FOREGROUND command.
Monitor stack overflow will generally not occur, since enough stack space is allocated to handle (worst-case) situations. To determine if the stack overflowed, inspect the contents of the address in the stack pointer minus 2. If the stack did not overflow, the contents will be 52525 (octal), which is the empty stack pattern. If the stack overflowed, the contents will be something other than 52525. If it overflowed, you can allocate more stack space by increasing the value of the conditional STAC$K in your system generated conditional file and by assembling and linking the monitors again.
If you are using a user-written device handler that requires a large amount of stack space, allocate stack space within the handler. A register other than SP should be used to reference the stack. (Failures That Cause Program Looping\ftcpl_sec)
When your system repeats a set of instructions continuously, it is in a loop. Programmed loops cause the system to wait until a device responds appropriately before resuming operation. However, looping can continue indefinitely if hard errors occur. This section describes causes of indefinite looping.
Handler loops are the most common. See (hal_sec) for further information about them.
The general method for diagnosing a program loop condition is to disable any device that generates frequent interrupts (the KW11L clock, for example) and then to single-step through the set of looping instructions to find the location in memory where the loop occurs. (See the processor handbook for the PDP--11 you are using for instructions on single-stepping.) A frequent cause of looping is the loss of an interrupt or interrupt enable bit in a device or terminal interface. If you are familiar with the devices your program is using, you can examine the device registers to determine if this is the case. (Monitor Looping\bsm_sec)
Loops are located at different offsets in specific monitors. Refer to the appropriate link map to determine the symbol value. (numbered) **Check the symbol QRESET.
This loop waits for all I/O to complete before executing an exit or chain. When the system is in this loop, check the queue elements and channel status word for outstanding I/O requests and then examine the appropriate devices to determine why requests are not satisfied. **Check the symbol CHWAIT.
This loop waits for I/O completion on a given channel and is entered when a .WAIT request is issued. The device that is causing the loop can be identified by checking register 3, which points to the channel status table. **Check the symbol QGTELT.
This loop waits for a queue element. If an active program waits in this loop for long periods of time, it is bound by queue elements and should have its number of queue elements increased with the .QSET program request. If a program hangs in this loop indefinitely, a device is not satisfying an I/O request. The device can be identified by checking the queue elements and channel status tables. Note that a mark time request (.MRKT) ties up a queue element until it is complete. **Check the symbol CDFN.
This loop is reached by a .CDFN programmed request and delays execution until all I/O is finished. A bad device can cause programs to hang in this loop. Examine the queues, channel tables, and device queues to identify a device that is not satisfying an I/O request and then examine the device registers. **Check the symbol QUIESCE.
This loop is reached by a .SRESET programmed request and delays execution until all I/O is finished. Use the same procedure as for item 5, above. **Check the symbol EXRDKM.
When the system encounters a hard error while reading the KMON or USR, it issues the (?MON--F--System read error) message. It may then continuously retry the read operation. If this loop should occur, the controller is malfunctioning. Halt the processor and try to reboot the system. If the system does not boot, check the system device for bad blocks. **Check the symbol SCHDLR.
This is the scheduler and null job (idle) loop, which the system enters when no job is runnable. Check the impure areas of all jobs to locate the cause.
Check the symbol BCNTXT to determine the location of the pointer to the background impure area. Check the symbol FCNTXT to determine the location of the pointer to the foreground impure area. Using these pointers, examine the I.BLOK words (see the (SIM_book) for details), the channel tables, and the queues to determine why neither job is runnable.
Note that a job can be blocked by a lack of available queue elements despite the fact that I.BLOK is zero, because on every significant event, the job will be run to check for an available queue element. Note also that the EXIT$ bit in I.BLOK can be set in several ways---with the .EXIT, .CDFN, or .SRESET programmed requests, for example. (Handler Looping\hal_sec)
By default, the line printer handler will loop on hardware errors until the error condition has been removed. The system will loop through the monitor service code and the handler detection code. This condition can be changed by using the monitor SET command (see the (sug_book)). The other supplied handlers use counts to prevent indefinite retries on a device. (Hard Error Conditions\hec_sec)
Hard error conditions are detected by the hardware rather than by the system software. RT--11 interprets hard errors by printing a short message on the console terminal. The corrective action that you take depends on the type of hard error condition and the device in use.
Often a hard error condition is simple to correct. The message will indicate an off-line or write-locked device, for example, and the system may wait until you correct the problem.
Other hard errors indicate more serious problems such as bad blocks on the system volume or a malfunction in the hardware itself. You may have to reinitiate the operation or use another device; in extreme cases, you may need the advice of a hardware specialist.
The following sections list: (unnumbered) Devices that can be used with RT--11 Hard error conditions that can occur for each of these devices Corrective actions for the errors
If an error persists after all possible corrective actions have been tried and all appropriate diagnostics have been run, call a Digital field service representative. (Video Terminals\vt_sec)

(multipage) (2\2) ((2\left) (Error Conditions)) (\ Video terminals do not report any hard error conditions.) ((2\left) (Corrective Action)) (\ Before using the system, make sure that the terminal is turned on and is on line. Adjust the scope on a video terminal so that it is bright enough to be easily read. Be sure that XOFF (CTRL/S) or the (HOLD SCREEN) key is disabled. Press (CTRL/Q) to set XON or press (HOLD SCREEN) to switch the HOLD SCREEN state.) (Hard-Copy Terminals\hct_sec)

(multipage) (2\2) ((2\left) (Error Conditions)) (\ Hard-copy terminals do not report any hard error conditions.) ((2\left) (Corrective Actions)) (\ Before using the system, make sure that the terminal is turned on, is on line, and has enough paper and a ribbon in good condition. Be sure that XOFF (CTRL/S) is disabled; press (CTRL/Q) to set XON.
If a DECwriter III is out of paper, replace paper. Turn the terminal off line and then on line. (Turning the terminal off and on will also work.) You can then enter keyboard input.) (Line Printers\lp_sec)

(multipage) (2\2) ((2\left) (Error Conditions)) (\ No power, no paper, printer drum gate open, off line, over temperature alarm, or no printer connected to control unit (LP11).) ((2\left) (Corrective Actions)) (\ Make sure that the printer is turned on and is set on line. See that the paper is loaded properly. Make sure that a line printer is connected properly to the controller (LP11).
The system waits while you take corrective action. (You can use the monitor commands SET LP HANG/NOHANG to control the wait feature; see the (SUG_book).)) (Magtapes\mag_sec)

(multipage) (2\2) ((2\left) (Error Conditions)) (\ Cyclical redundancy or parity (checksum) error, record length error, nonexistent memory, write-locked, off line, unit select, or power off.) ((2\left) (Corrective Actions)) (\ Make sure that all magtape units are powered on---regardless of which one is in use---set on line, and, if appropriate, write-enabled---insert a write-ring on the back of a magtape to write enable it. See that the tape is correctly mounted on the proper unit and that all units are assigned different select numbers. Make sure that 7-track tapes are on 7-track drives; 9-track tapes, on 9-track drives.
For checksum and bad tape errors, retry the operation, using another magtape or drive, if possible, or use the monitor COPY/IGNORE command or the PIP /G option to ignore input errors while copying.) (Disks\dis_sec)

(multipage) (2\2) ((2\left) (Error Conditions)) (\ Off line, write-locked, unit select, parity error, bad blocks, drive not ready, or volume not formatted.) ((2\left) (Corrective Actions)) (\ Make sure that the disk drive is set on line and is write enabled, if appropriate. Make sure that the disk is correctly loaded in the proper unit and that all units are assigned different select numbers. Note the locations of drive 0 and drive 1. Make sure that a new disk is properly formatted before you use it. ) (\ For parity errors, retry the operation, using another disk or drive, if possible, or use the monitor COPY/IGNORE command or the PIP /G option to ignore input errors while copying. ) (\ Use the monitor INITIALIZE/BADBLOCKS command or the DUP /B option to detect and identify bad blocks on the new devices just received from the manufacturer. This procedure initializes the device directory, leaving only FILE BAD entries in it. This ensures that the system will not try to access these bad blocks during routine operations.) (\ Sometimes disks develop bad blocks as a result of use and age. Use the monitor DIRECTORY/BADBLOCKS command or the DUP /K option to detect bad blocks on devices that contain data. If the bad blocks fall in a small area, use the monitor CREATE command or the DUP /C option to assign a file name with a .BAD file type to the area (see the (sug_book)). If hard errors are frequent, you can copy the device to a second device, using the monitor COPY/DEVICE command or the DUP /I option, and then copy the second device back to the first. This procedure rewrites the headers and eliminates hard errors. However, if hard errors persist, request that a hardware maintenance specialist check the head alignment of your device. ) (\ You can also use the FORMAT utility program to reformat devices that generate hard errors. This procedure destroys the data on the device, which is then suitable for use with RT--11. Use of FORMAT varies depending on the type of device, however. See the (sum_book) for information about FORMAT. ) (RT--11 System Messages\sm_sec)
This chapter alphabetically lists diagnostic messages from the RT--11 monitor and system programs and suggests corrective actions for each message. If you need further information concerning a message, consult the INDEX regarding the subject of the message and the (sug_book) or the (sum_book) for a description of the system program or utility that displayed the message. Error messages for (FORTRAN IV, BASIC--11,\ITALIC) and (MACRO--11\ITALIC) are no longer listed in this chapter, but are located in their respective manuals. Also, editor messages unique to specific editors are now listed in the error section of documentation for that editor. (SL and EDIT are listed with the other system utility messages.) (Special Information About RT--11 System Messages\sia_sec)
See (emf_sec) for an explanation of the organization and format of RT--11 system messages and the references found in the messages. (CTI Bus-Based Software Bootstrap Error Messages\p3s_sec)
If a software bootstrap error occurs when you power up your system, the octal number 051124 will appear on your screen. Below this will be a second octal number, which is the error code. The following table gives the error message assigned to each error code. Reference the error message, not the error code number.

(multipage) (2\14\) (Code Number\ Error Message) ( 000001\?BOOT--F--No boot on volume) ( 000002\?BOOT--F--Conflicting SYSGEN options) ( 000003\?BOOT--U--Handler file not found) ( 000004\?BOOT--U--Insufficient memory) ( 000005\?BOOT--U--I/O error) ( 000006\?BOOT--U--Monitor file not found) ( 000007\?BOOT--U--No KT--11) ( 000010\?BOOT--U--Swap file too small) ( 000011\?BOOT--U--SWAP.SYS not found) ( 000012\?BOOT--W--Error reading handler) ( 000013\?BOOT--U--Failure to load system handler)
If a problem occurs when you boot your system but the octal number 051124 does not appear on your screen, you have a hardware problem and should consult your hardware manual. (List of System Messages\lsm_sec) (part System Messages\damn_sdml) (new error message manual) (noident) (#) (?BA--E--Must 'R BATCH',type '/U') An UNLOAD BA command was entered before the handler was unlinked. (User Action) Run BATCH and specify the /U option to unlink the handler. BATCH automatically performs the UNLOAD BA command. (?BA--U--BC) The BATCH handler found bad code in the control file. This can happen when a .CTL file is corrupted or if someone made an editing mistake when altering or creating the file with a text editor. (User Action) Make sure that no editing errors have been introduced into the file. Recompile the .BAT file. (?BA--U--FE) (numbered) An invalid F followed by a Return was used in the .CTL file, causing a forced end to BATCH processing. BATCH was terminated from the console by a F followed by a Return. (User Action) (numbered) Insert another BATCH control directive after the F to prevent forced termination. Do not type F followed by a Return at the console unless you intend to terminate BATCH processing. (?BA--U--IO) (numbered) An input or an output error occurred---probably because of a log file overflow---when the BATCH handler tried to read the .CTL file or to write to the log file. This message may also appear if the BATCH control file (.CTL) is not in the correct format. Common format errors occur when you run an uncompiled BATCH input file or use a BATCH run-time system directive that is preceded by one backslash instead of two. (User Action) (numbered) Rerun the BATCH stream, specifying a larger log file with the square bracket construction; the default log size is 64 decimal blocks. Make sure that the .CTL file is a valid control file output by the BATCH compiler and that the directives to the BATCH run-time system are in the correct format. (?BA--U--LU) The BATCH handler could not find a free channel. This can happen if all 16 channels are opened for magtape operations within the BATCH stream. (User Action) Check the program and make sure that one channel is left open and is not specified for use by magtape. (BASIC--11 messages) The BASIC--11 messages have been removed from this manual. Look in the separate BASIC--11 documentation for explanations of all BASIC--11 error messages. (?BATCH--F--Abort job) An error occurred in compiling a BATCH program, or a diagnostic compile was requested with /N.
The compiler forces the job to abort. (User Action) Check the log file for all error messages. (?BATCH--F--Ambiguous command) The command abbreviation entered is not unique. (User Action) Make sure that the command includes enough characters to make it unique. (?BATCH--F--Ambiguous option) The option abbreviation specified is not unique. (User Action) Make sure that the option contains enough characters to make it unique. (?BATCH--F--Batch fatal error) An unrecoverable error occurred. This may indicate a problem in the software. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). The system may have to be bootstrapped again. If the problem continues, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?BATCH--F--Batch handler not resident) The BATCH run-time handler was not loaded with the RT--11 LOAD command. (User Action) Load the BATCH handler, using the LOAD command to run BATCH. (?BATCH--F--Batch stack overflow) The BATCH stream has too many nested $CALL commands. (User Action) Make sure that the BATCH stream includes no more than 31 nested $CALL commands. (?BATCH--F--Cannot run with SL ON.) The SL handler is on. (User Action) SET SL OFF. (?BATCH--F--Channel in use) A channel that should have been free for BATCH was busy as a result of an internal BATCH error. (User Action) Try the program again. (?BATCH--F--Dismount error) The logical device name specified does not exist. (User Action) Make sure that the device was assigned with a $MOUNT command. (?BATCH--F--Duplicate option) An option was specified more than once in a command line. (User Action) Correct the command line. (?BATCH--F--EOF with no $EOJ) A file was not terminated with a $EOJ command. (User Action) Insert a $EOJ command as the last statement in the BATCH job. (?BATCH--F--File created: protected file already exists) A protected file exists, along with a newly created unprotected file of the same name. The protected file is either a BATCH control file or a log file. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?BATCH--F--File not found) A file specified as input to BATCH was not found, or the /X option was specified but the input to BATCH was not a precompiled (.CTL) file. (User Action) Check the file specifications and correct the program to reflect any changes made. (?BATCH--F--Input error) A hardware error occurred while BATCH was attempting to read the compiler input file (.BAT). (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?BATCH--F--Input file) An input file descriptor was not specified in the BATCH compiler command line. (User Action) Check for a typing error in the command line. Specify an input file in the command line. (?BATCH--F--Insufficient memory) The BATCH compiler does not have enough memory to fetch the device handler it needs. The handler is needed as an I/O device for the BATCH compiler or to satisfy a $MOUNT or $DISMOUNT command in the BATCH job. (User Action) Check for a typing error in the command line to the BATCH compiler or in the $MOUNT or $DISMOUNT command in the BATCH input file. See (ism_sec) for information on how to increase storage space. (?BATCH--F--Invalid '+') (numbered) The plus sign (+) construction was used when not allowed---for example, in a $RUN or a $BASIC input file descriptor. A plus sign (+) is in an output file descriptor or terminates a file descriptor. (User Action) Verify that the plus sign (+) is used only to indicate a positive value in an option or to separate multiple file descriptors. (?BATCH--F--Invalid character) The character specified was not used in the proper context. (User Action) Check the log file to determine the character in error. (?BATCH--F--Invalid command ) The command line to the BATCH compiler is incorrect. (User Action) Check for a typing error in the command line. Check the format for the command and enter the command again. (?BATCH--F--Invalid construction) In RT--11 mode, an IF statement was not in the correct form, or an invalid 'text' directive occurred in a command. (User Action) Verify that the format of the IF statement is correct and that the 'text' directive is valid as entered. (?BATCH--F--Invalid copy of handler) The copy of BA.SYS in memory is invalid. (User Action) Unlink the batch handler if necessary, unload the copy of BA.SYS in memory, reload BA.SYS, and run BATCH. (?BATCH--F--Invalid device) An invalid or nonexistent device was specified in the command line. (User Action) Check for a typing error in the command line. Verify that the device exists as entered in the command line or use another device. Enter the command again. (?BATCH--F--Invalid LOG device) A magtape or read-only device was specified as the log device. (User Action) Check for a typing error in the command line. Assign the log device to a suitable device. (?BATCH--F--Invalid option) (numbered) An invalid option was used in the command line to the BATCH handler. The option name specified is not a valid RT--11 BATCH option or is not valid for this field. (User Action) (numbered) Check for a typing error in the command line. Make sure that the option indicated is valid. Make sure that the option name specified is a valid RT--11 BATCH option or option abbreviation and that it is valid for the field to which it applies. See the (sum_book) or the (sug_book) for a list of valid options and option abbreviations. (?BATCH--F--Invalid option combination) More than one option of the same type was specified on one command line. (User Action) Make sure that only one option from the following combinations is used: /MACRO, /INPUT, /SOURCE, and /FORTRAN, /INPUT, /SOURCE, and /BASIC, /INPUT, /SOURCE. (?BATCH--F--Invalid sequence argument) A nonnumeric identification number was specified in a $SEQUENCE command. (User Action) Enter the command again, specifying the identification number as an unsigned decimal number. (?BATCH--F--Invalid variable) The variable specified is not one of the characters A to Z. (User Action) Enter the variable as an alphabetic character. (?BATCH--F--Invalid VID) An incorrect form was used when specifying the volume identification in a $MOUNT command. (User Action) Make sure that the equal sign (=) and the name of the volume are included in the command. (?BATCH--F--Line too long) The input line entered contains more than 80 characters. (User Action) Correct the input line. (?BATCH--F--LOG device error) A hardware error occurred during a transfer operation to the log device. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?BATCH--F--'$' missing) A dollar sign ($) is not present in the first position of the command line or card column 1. (User Action) Make sure that a dollar sign ($) begins the command line. (?BATCH--F--No control file) The program tried to send .CTL file to a nonfile-structured device---for example, LP:. (User Action) Check for a typing error in the command line. Use a file-structured device for the .CTL file or use the /N option to inhibit execution. (?BATCH--F--No $EOJ) A $JOB or $SEQUENCE command was issued without a preceding $EOJ command to end the previous job. (User Action) Correct the BATCH stream by inserting a $EOJ command. (?BATCH--F--No file) No file descriptor appeared where expected in the BATCH stream, or no file name was entered in the $CREATE command. (User Action) Enter a file descriptor where expected in the BATCH stream or enter a file name in the $CREATE command. (?BATCH--F--No file name before ".") A file type was specified, but no file name preceded it. (User Action) Correct the format of the file descriptor. (?BATCH--F--No ',' in $LIB) Libraries in a $LIBRARY command were separated by a comma (,) instead of by a plus sign (+). (User Action) Edit the $LIBRARY command in the BATCH input file, using a plus sign (+) instead of a comma (,). (?BATCH--F--No logical device) No logical device was specified in a $MOUNT command. (User Action) Correct the command format. (?BATCH--F--No physical device) No physical device was specified in a $MOUNT command. (User Action) Correct the command format. (?BATCH--F--Output device full) The temporary file (.CTL) created by BATCH is too large for the specified device. (User Action) See (ism_sec) for information on how to increase storage space. (?BATCH--F--Output error) (numbered) Magtape was specified as the .CTL output device. A hard error was reported while BATCH was attempting to write the compiler output file (.CTL). (User Action) (numbered) Check for a typing error in the command line. Verify that the output device specified is not a magtape. Check the procedures for recovery from hard error conditions listed in (hec_sec). (?BATCH--F--Output file not open) The .CTL file output channel was not opened, probably because of an error in the BATCH compiler. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?BATCH--F--Please assign LOG,LST) The log device (LOG:) or the listing device (LST:) was not assigned. (User Action) Use the ASSIGN command to assign LOG: and LST: devices. LOG: must be assigned, and LST: is recommended unless the BATCH stream will definitely not reference LST:. (?BATCH--F--Please load LOG handler) The log device handler is not resident. (User Action) Check for a typing error in the LOAD command. Load the appropriate device handler. (?BATCH--F--Protected file already exists) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?BATCH--F--Return from call error) BATCH could not read the control file that called a subprogram. Execution could not be resumed on return from the call. (User Action) Verify that the .CTL file has not been destroyed; recompile, if necessary. Try the operation again. Use another drive or unit if possible. (?BATCH--F--Separator missing) A file descriptor was not terminated by a space, a plus sign (+), a comma (,) or a Return. (User Action) Correct the format of the file descriptor. (?BATCH--F--Too many file descriptors) More than six file descriptors were specified in a BATCH command line beginning with a dollar sign ($). (User Action) Check for a typing error in the command line. Limit the number of file descriptors to six. Check the format of the command in question. (?BATCH--F--Too many output files) More than two output files were specified. (User Action) Check for a typing error in the command line. Limit the number of output file specifications to two. (For BATCH, output files represent the compiler output device and file and the log file.) (?BATCH--F--Unknown command) The command specified with a dollar sign ($) in character position 1 is not a valid BATCH command. (User Action) Check the command line for typing errors. (BE (
)) BE = bad entry. An entry to ODT was caused by a breakpoint trap that ODT did not expect. Location (
) represents the location after the trap instruction that ODT did not expect. Setting the T bit in the status register, jumping to the middle of ODT, or executing data, using an invalid trace trap instruction, can cause this error. (User Action) Correct the contents of the location before (
). (?BINCOM--E--Device full ()) Not enough room is available in the directory of the output device to create the specified output file. (User Action) Use SQUEEZE to compress the volume or use a different volume for this operation. See (ism_sec) for information on how to increase memory resources. (?BINCOM--E--Device not active ()) Input or output was requested for a device that is not on line, not write enabled, or not in the system's device tables. Wildcards may have been used in the command string. (User Action) Make sure that the device is on line and is write enabled. Use the INSTALL command to enter the device into the system's device tables. (?BINCOM--E--Error reading directory ()) A hardware error occurred while the directory of the indicated input device was being read. Wildcards were used in the command string. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?BINCOM--E--File created; protected file already exists ()) A protected file exists along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?BINCOM--E--Input error ()) (numbered) A hardware error occurred while the specified input file was being read. During an attempt to access an input device specified with wildcards, a hardware error occurred. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BINCOM--E--Input file not found ()) (numbered) The specified input file was not found on the specified device. Wildcards were used in the command line, and a match was not found. (User Action) Make sure that the command line contains no errors and that the specified file exists on the specified device. If the correct device is not mounted, mount it and enter the command again. (?BINCOM--E--Insufficient memory) BINCOM does not have the minimum amount of memory it requires to use as buffer space when it compares files. (User Action) See (ism_sec) for information on how to increase memory resources. (?BINCOM--E--Invalid command) (numbered) An incorrect command was issued to BINCOM. A file specification was given in the command string of the device/device comparison. A patch file was specified with wildcards. (User Action) (numbered) Check for a typing error in the command line and make sure that the format of the command line is correct. Enter the command again. Retype the command line without any file specifications. Remove the patch file from the command line and retry the operation. (?BINCOM--E--Invalid directory ()) Wildcards were used in the command line to read a directory, and the volume was not in RT--11 format. (User Action) Copy the files onto an RT--11 directory device. (?BINCOM--E--Invalid option /x) The option specified in the command line is invalid. (User Action) Check for a typing error in the command line. See the (SUM_book) or the (SUg_book) for a list of valid options. (?BINCOM--E--Invalid option /x:val) An option that requires a value was not given one, or an option that does not take a value was given one. (User Action) Check for a typing error, and type the command line again. (?BINCOM--E--Output error ()) A hardware error occurred while the specified output file was being written. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BINCOM--E--Output file full ()) Not enough room was allocated to the specified output file when it was created. (User Action) Delete the existing output file, or use a different volume for the output file. See (ism_sec) for information on how to increase memory resources. (?BINCOM--F--Invalid device.) Trying to produce a patch (SIPP) on a device that is not in the system tables. (User Action) Specify an existing device. (?BINCOM--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (BINCOM) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?BINCOM--I--Comparing/()---()) (numbered) The two input files compared are different. A comparison resulted from wildcards. BINCOM prints this message to show which two files are being compared. (User Action) This message is informational. (?BINCOM--I--No differences found) The files compared are identical. BINCOM does not create an output file unless you used the DIFFERENCES/ALWAYS command or specified the /O option in the command string. (User Action) This message is informational. (?BINCOM--I--Number of files compared =) Used in wildcarding. (User Action) This message is informational. (?BINCOM--W--Device is longer ()) Whether or not there are differences in the binary data on the two devices compared, the devices differ in length. (User Action) This message is informational. (?BINCOM--W--Devices are different) The devices compared are different. (User Action) This message is informational. (?BINCOM--W--File is longer ()) Whether or not there are differences in the binary data in the two files compared, the files differ in length. (User Action) This message is informational. (?BINCOM--W--Files are different) The files compared are different. (User Action) This message is informational. (?BINCOM--W--Files with differences =) Used in wildcarding. (User Action) This message is informational. (?BOOT--F--No V5 boot on volume) No bootstrap was written on the volume. (User Action) Use the DUP /U option or the COPY/BOOT command to write the bootstrap. (?BOOT--U--Conflicting SYSGEN options) Support for the error logger, extended memory, and device timeout differs in the system handler and the monitor. Execution terminates. (User Action) Make sure that the monitor and handler file versions are correct. If these files are lost, assemble the monitor and handlers with the same system generation conditional file. See the (SYG_book) for details about SYSGEN options. (?BOOT--U--Failure to load system handler) The bootstrap program displays this message and aborts the boot. The message means there is an error in the system handler load routine causing the system to halt. (User Action) You must fix the handler load routine. (?BOOT--U--Handler file not found) The handler for the system device was not found during the bootstrap operation. Execution terminates. (User Action) Copy the handler file (DD[X].SYS) for the system device onto the volume you are trying to boot. Reboot. (?BOOT--U--Insufficient memory) (numbered) The bootstrap blocks designate a monitor that is too large for the system's memory. Execution terminates. Since RT--11 sizes memory, hardware failure of a memory module may result in the monitor's booting into less memory than is installed on the system. (User Action) (numbered) Select a monitor that is small enough for the system and use the DUP /U option or the COPY/BOOT command to copy the bootstrap blocks for that monitor. Make sure that the hardware device has enough memory for the monitor. (?BOOT--U--I/O error) (numbered) An I/O error occurred during system bootstrap. Using a monitor before copying that monitor's bootstrap to the volume bootstrap blocks causes this error. Execution terminates. An error occurred in the interface between the ROM primitive I/O subroutines and the RT--11 software bootstrap. Execution terminates. MBOOT or MSBOOT selected the incorrect I/O instructions for the specified magtape (MM, MT, MS or MU) because another peripheral is located at the standard address for that magtape. (User Action) (numbered) Make sure that the proper monitor and system handler are on the system disk. Use the backup volume and the DUP /U option or the COPY/BOOT:xx command to make sure that the bootstrap for the monitor is on the corresponding system volume. See the (sug_book) for more information about copying the bootstrap. If the error persists, check the procedures for recovery from hard error conditions in (hec_sec). Retry the bootstrap operation. If the error persists, turn the power off and then on. Then recopy the monitor file onto your system volume from the distribution kit and reinstall the bootstrap with the DUP /U option or the monitor COPY/BOOT command. If the error persists, the problem may be in the hardware. Make sure that the magtape controller is located at the correct standard address and that the standard addresses for the other magtape devices are not used. (?BOOT--U--Monitor file not found) The system volume's bootstrap blocks designate a monitor file that is not on the volume. Execution terminates. (User Action) Make sure that the proper file is on the system disk. Use the backup volume and the DUP /U option or the monitor COPY/BOOT command to make sure that the bootstrap for the monitor is on the corresponding system volume. (?BOOT--U--No KT--11) An attempt was made to boot a mapped monitor on a system that does not have a KT--11 memory-management unit. Execution terminates. (User Action) Reboot and select the unmapped monitor or use a system that has KT11 memory-management hardware. (?BOOT--U--Swap file too small) The file SWAP.SYS is on the system volume but is less than 28 (decimal) blocks long. Execution terminates. (User Action) Copy the SWAP.SYS file from another working system volume to the system volume or use the DUP /C option or the CREATE command to create the file with the correct length. The DUP /T option or the CREATE/EXTENSION command can also be used to extend the file to the correct length. (?BOOT--U--SWAP.SYS not found) The system SWAP file was not found on the system volume during the bootstrap operation. Execution terminates. (User Action) Copy SWAP.SYS to the system volume. Reboot the monitor. (?BOOT--W--Error reading handler) A hardware error occurred while a handler file was being read.
A nonsystem handler file resides on a bad block. Entries for this handler are removed from the running system's device handler tables. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BOOT--W--Invalid or missing TT.SYS) Terminal handler TT.SYS was not on the system volume when RT11MT monitor was bootstrapped. (User Action) Copy the file TT.SYS to the bootable magtape. Reboot the system, using the new magtape. (?BUP--E--Directory input error ()) BUP detected a hardware problem with the input device. For example, you inserted a floppy diskette incorrectly or your magtape device is off line. (User Action) Correct your hardware problem and respond (YES) to the BUP prompt. (?BUP--E--Incompatible output volume size) The output volumes used during the BACKUP operation are a different size than the first backup volume used. For example, this message will appear if single-density and double-density diskettes are used for output volumes during the operation. (User Action) Try the operation again, using volumes that are the same size. (?BUP--E--Input error ()) The specified data block on the input device could not be read without error. The backup volume may contain wrong data for this block. The () (device specification) is given when errors are found while making a device backup. (User Action) Be aware that the output volume may contain data that does not match that in the input volume. Retry operation. (?BUP--E--Input error at block () [of ()]) The specified data block on the input device could not be read without error. The backup volume may contain wrong data for this block. The () (file specification) is given when errors are found while making a file backup. (User Action) Be aware that the output volume may contain data that does not match that in the input volume. Retry operation. (?BUP--E--Input error at block () of ()) The specified data block on the input device could not be read without error. The backup volume may contain wrong data for this block. The () (device specification) is given when errors are found while making a device backup. (User Action) Be aware that the output volume may contain data that does not match that in the input volume. Retry operation. (?BUP--E--Insufficient space on output volume ()) Not enough room is available on the output device for BUP to complete the RESTORE operation. (User Action) Try the operation again, using an output device that has a larger number of contiguous free blocks. (?BUP--E--Not a BACKUP saveset ()) BACKUP/DIRECTORY of a magtape has found a file that is not a BACKUP saveset. (User Action) Note that you cannot use BACKUP to RESTORE such files. (?BUP--E--Not a BACKUP saveset section) The saveset section specified for a RESTORE operation does not conform to BUP's saveset format. (User Action) Treat the saveset as a file. Try using the COPY command to transfer it to an RT--11 volume. (?BUP--E--Not a BACKUP volume) The volume specified in the command line for a BACKUP or a RESTORE operation has not been initialized as a BACKUP volume. (User Action) If you are performing a BACKUP operation and you want to proceed to initialize the output volume, type (YES) in response to the initialization query. If performing a RESTORE operation, you should determine whether you mounted the wrong volume, or whether the volume has since been used for another purpose. (?BUP--E--Output error ) On a BACKUP operation to magtape, BUP could not successfully write the volume header or volume ID label to the magtape. (User Action) Check to make sure that the tape volume is on line and write enabled. Retry the operation. If no success, mount another magtape and retry the operation. ( ?BUP--E--Protected file already exists ()) The named destination file cannot be created because a file of the same name already exists, and that file is protected. (User Action) Specify a different output file name or unprotect the existing file so that it can be replaced. (?BUP--E--Tape volume position error) While performing a RESTORE operation from a magtape, there were unexpected extra tape records at the end of the saveset file. (User Action) Make sure that the correct backup volume has been mounted. Try performing the RESTORE operation again. (?BUP--E--Verification error ()) The BUP /VERIFY option found differences between the original data and the new transferred copy. (User Action) Retry the operation to be certain you are verifying the correct file or device. If the operation fails again, see the procedures for recovering from hard error conditions described in (hec_sec). (?BUP--E--Volume does not belong to this set) During a RESTORE operation, the mounted BACKUP volume is from a different BACKUP session than previously mounted volumes. (User Action) Find the correct volume and mount it. (?BUP--E--Wrong volume number) During a RESTORE operation, the correct set of volumes was being used, but the wrong volume was mounted. (User Action) Mount the correct volume. Try the operation again. (?BUP--F--Bad block detected ()) A read error has occurred on disk during a /RESTORE/VERIFY operation. (User Action) Restart the operation, using a different destination disk. (?BUP--F--Cannot append to old BUP tape) A request has been made to append a saveset to a mounted BUP magtape. However, the magtape was made using an old version of BUP (before V5.46). (User Action) You cannot append savesets to tapes made with BUP versions before V5.46, because these tapes are not ANSI compatible. (?BUP--F--Channel in use ()) A magtape handler was aborted and left in a "busy" state. (User Action) UNLOAD the magtape handler and then RELOAD it before trying the command again. (?BUP--F--Device in use) Another job was using the specified device. (User Action) Try the operation again after the job is finished or aborted. (?BUP--F--Device not available ()) A magtape device is not available. (User Action) Check to make sure that the specified tape drive is powered up, a tape volume is mounted, and the unit is on line. (?BUP--F--Device write-locked ()) During a BACKUP operation, a magtape device is write locked. (User Action) Write enable the volume and try the operation again. (?BUP--F--Directory input error ()) A hardware error occurred while the directory was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BUP--F--Directory I/O error ()) An error occurred while reading or writing device directory blocks or tape labels. (User Action) Check to be sure that the device is on line. If you intend to modify the output device, check to make sure that it is write enabled. Also, see the procedures for recovery from hard error conditions listed in (hec_sec). (?BUP--F--Directory I/O error ():BUPTMP.TMP) BUP was unable to create a workfile. (User Action) The BUP workfile requires at least 68 contiguous blocks of space. By default, it is created on your system device, SY:. If you have assigned WF as a workfile device, make sure that it is initialized and has adequate space for the workfile. (?BUP--F--Duplicate option) The same option was specified more than once in a single command line. (User Action) Correct the command line. (?BUP--F--Duplicate saveset name ()) A saveset with the output saveset name already exists. (User Action) If you do not specify a saveset name, BUP uses the name BACKUP.BUP. You must either initialize the tape with the /INITIALIZE (/Z) option or supply a unique name if a saveset by that name already exists. (?BUP--F--Fetch error ()) A device handler could not be fetched, probably because not enough memory was available. (User Action) Be sure the specified device handler is installed and that there is adequate memory available to fetch the device handler. (?BUP--F--File not found ()) The backup volume does not contain the input file specified in the command line. Control returns to the monitor. (User Action) Check for a typing error in the command line. Make sure that the specified file resides on the backup volume. Try the operation again. (?BUP--F--Incompatible output volume size) The size of a mounted output disk is different than that of previously used volumes in the same BACKUP operation. For example, a mounted RX02 floppy disk is formatted with the wrong density. (User Action) When performing multivolume disk-to-disk backups, use output disks of uniform size. (?BUP--F--Input error ()) A read error has occurred on disk during a /RESTORE/VERIFY operation. (User Action) Restart the operation, using a different destination disk. (?BUP--F--Input error ()) (numbered) A hardware error occurred during a read operation. An input error on the output disk drive was encountered reading back a magtape block during a BACKUP/RESTORE/VERIFY operation. is the file specification for the restored file image on the output drive. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BUP--F--Insufficient memory) Not enough memory is available to complete the requested operation. (User Action) See (ism_sec) for information on how to increase memory space. (?BUP--F--Invalid command) The command entered is invalid, because the command line specified contains a syntax error, too many files were specified, no device was specified, or an attempt was made to use wildcards. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?BUP--F--Invalid device ()) An invalid or nonexistent device was specified in the command line. (User Action) Check for a typing error in the command line. Verify that the device indicated is valid. (?BUP--F--Invalid device combination) The same device and unit was specified for both input and output. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for valid device combinations. (?BUP--F--Invalid device for operation) Your command has been rejected because the operation is not possible with one or more of the devices specified. (User Action) Use a different device or a different kind of BACKUP operation to perform your task. (?BUP--F--Invalid directory) The volume in the specified device does not contain a valid RT--11 directory structure. (User Action) Initialize the volume before using it for the first time. (?BUP--F--Invalid option) An invalid option was used in the command line. (User Action) Check for a typing error in the command line. See the (SUM_book) or the (sug_book) for a list of valid options. (?BUP--F--Invalid option combination) The specified options request conflicting functions to be performed. (User Action) Examine the logic of the command line and correct it, if necessary. See the (sum_book) or the (sug_book) for valid option combinations. Try the operation again. (?BUP--F--Invalid option for device) An option has been specified that is invalid when used in combination with the specified device. For example, /NOREWIND has been specified for a disk backup. (User Action) Check the command line and reenter it with either an appropriate device name or without the invalid option. (?BUP--F--Invalid use of wildcards) A wildcard character has been specified as part of a saveset name or output file name. (User Action) Specify an exact saveset name or output file name. (?BUP--F--No blocks to back up ()) A request has been made to back up a file whose length is zero blocks. (User Action) A file with no blocks cannot be backed up. (?BUP--F--Not a backup volume ()) The volume specified in the BACKUP/DIRECTORY command is not a backup volume. Control returns to the monitor. (User Action) Use a backup volume for the directory operation or use the DIRECTORY command. (?BUP--F--Operation not completed) The operation was aborted before it was completed because a (NO) response was given to the mount query. (User Action) None. (?BUP--F--Output error ()) A hardware error occurred during a write operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?BUP--F--Output error ()) A hardware error occurred during a write operation. (User Action) See the procedures for recovery from hard error conditions in (hec_sec). ( ?BUP--F--Protected file already exists (<)dev:filenam.typ>) A saveset of the same name as that specified in the BACKUP command already exists on the backup volume. BUP does not allow you to backup two or more savesets of the same name on the same volume so that you do not accidentally delete information.
After the fatal error message, BUP also displays the following prompt: Mount output volume in (<)dev>; Continue?
This is done to enable you to continue with the same backup operation by placing a new backup volume in the specified device. (User Action) (unnumbered) If you want to keep the same saveset file name but on a different volume, at the (Continue?) prompt, mount a new volume in the specified drive. If you want to use the same volume with the same saveset file name, abort the backup operation with (CTRL/C) and reissue the BACKUP commmand with the /INITIALIZE option, but be aware that this action deletes all files on the backup volume. If you want to use the same volume with a different saveset file name, abort the backup operation with (CTRL/C) and reissue the BACKUP command with a new saveset file name. (?BUP--F--Size does not match ()) A /RESTORE/VERIFY:ONLY operation has been requested for two files or devices with different sizes. (User Action) Check for a typing error in the command line. Two files or devices with different sizes will not be compared. (?BUP--F--Too many bad blocks ()) More than 25 bad blocks were detected during a disk-to-disk BACKUP, RESTORE, or bad-block scan operation. (User Action) Verify that your disks are loaded correctly. If that is not the problem, use another disk. (?BUP--F--Too many mismatches during verify operation) The BUP verification procedure encountered an unacceptably high number of mismatches between the input and output data. (User Action) Check the input device for bad blocks. By default, BUP returns this error if it finds more than 25 mismatches. To change this number, perform the customization patch procedure described in the (ins_book), Section 2.7.64. ( ?BUP--F--Too many mismatches during verify operation ()) The backup does not match the original data. A /VERIFY operation has encountered more than 25 blocks with different contents. (User Action) If you are checking a BACKUP or RESTORE operation that was just performed, do that operation again with a fresh destination disk or tape. (?BUP--F--Unexpected end of saveset) On restoring a file or device image, the tape's saveset file ended prematurely. (User Action) The file or device image cannot be fully restored, since the tape's saveset is incomplete. Check to make sure the correct backup volume is mounted. (?BUP--F--Unexpected error on .SPFUN) An attempt was made to stream a nonstreaming magtape, and the handler did not ignore the inappropriate .SPFUN request.
All distributed RT--11 magtape handlers ignore inappropriate .SPFUN requests and should not cause this error. (User Action) Magtape handlers should be written to ignore .SPFUN requests that are inappropriate for the hardware involved and not return hard errors. In this case, the magtape handler should ignore the .SPFUN request to enable streaming. (?BUP--F--Volume does not belong to this set) During the RESTORE operation, the specified input file and the number of the mounted volume match the file name and the volume number of the backup volume. However, the number of blocks that were backed up to the mounted volume does not match the number of blocks for the set of volumes being restored. (User Action) Try the operation again, using volumes that are part of the set being restored. (?BUP--F--Wrong version of RT--11) An attempt was made to run RT--11 Version 5 BUP on a previous version of the RT--11 system. (User Action) Do not run RT--11 Version 5 BUP under any earlier RT--11 versions. (?BUP--I--Appending to volume) A BACKUP operation has begun on an output tape saveset, preserving one or more savesets that were previously stored on the tape. (User Action) This message is informational. (?BUP--I--Backup operation is complete) BUP has finished backing up a file or volume. (User Action) This message is informational. (?BUP--I--Backup/Verify operation is complete) BUP has finished backing up and verifying a file or volume. (User Action) This message is informational. (?BUP--I--Bad block scan started) BUP has started to scan a volume for bad blocks. (User Action) This message is informational. (?BUP--I--Bad blocks detected; use another volume) BUP detected bad blocks on the specified volume. (User Action) Use another volume and try the operation again. (?BUP--I--Creating volume n) BUP is backing up information to the specified volume. (User Action) This message is informational. (?BUP--I--No bad blocks detected) BUP did not detect any bad blocks on the specified volume during the bad block scan. (User Action) This message is informational. (?BUP--I--No files restored) No files matching the input specification were found in the saveset, or those that were found could not be restored because of size or protection constraints. (User Action) This message is informational. (?BUP--I--No files verified) No files matching the input specification were found in the saveset. Check to see that adequate space exists on the output volume, and that protected files with names matching the input wildcard specification do not already exist. (?BUP--I--Restore operation is complete) BUP has finished restoring a file or volume. (User Action) This message is informational. (?BUP--I--Restore operation started from volume n) The RESTORE operation has started from the specified volume. (User Action) This message is informational. (?BUP--I--Restore/Verify operation is complete) BUP has finished restoring and verifying a file or volume. (User Action) This message is informational. (?BUP--I--Verify operation is complete) The specified /VERIFY:ONLY operation is finished. (User Action) This message is informational. ( ?BUP--I--Verify operation started from volume ()) The named saveset has been found and a /RESTORE /VERIFY:ONLY operation has begun. (User Action) This message is informational. (?BUP--I--Verify pass started) BACKUP operation is finished. BUP prepares for and performs a VERIFY operation. (User Action) This message is informational. (?BUP--W--Bad block read at ()) A bad block was detected at block number () during a BACKUP or RESTORE operation. The bad block was not copied. (User Action) Corresponding blocks on the output volume may contain wrong data. (?BUP--W--Continuing RESTORE with mounted volume) This message follows an (Expected block...) message. It indicates that there was a difference between the expected block number and the block number found, and the RESTORE operation will resume with the new volume information. (User Action) Data may be missing or incorrectly placed on the destination disk. (?BUP--W--Expected block (); Tape volume begins with ()) While performing a RESTORE operation from a multi-volume magtape saveset, a check of resuming tape block numbers has revealed an inconsistency across a tape boundary. (User Action) Make sure that the correct tape volume has been mounted. If tape
read-errors have been observed, try the RESTORE operation again, starting with the first volume. (BUP--W--File not found ()) During the RESTORE operation, the input file specified in the command line was not found on the volume mounted. The wrong set of volumes may have been used. (User Action) Check for a typing error in the command line. Make sure that the volume that is mounted contains the specified file. (?BUP--W--Not a BACKUP saveset) A request has been made to append a saveset to a magtape, but the magtape was not initialized with BUP. (User Action) Use a different tape or use BACKUP/INITIALIZE on the one that is mounted. (?BUP--W--Not a backup volume ()) The volume specified in the command line for a backup or a RESTORE operation has not been initialized as a backup volume. BUP repeats the initialization query. (User Action) If you want to proceed to initialize the disk, type (YES) in response to the initialization query. (?BUP--W--Output file exists and is protected ()) An attempt was made to restore a file to a device that contained a protected file of the same name. (User Action) Make sure you want to replace the existing protected file. Then use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file. (?BUP--W--Output volume not initialized; Are you sure?) During a RESTORE operation to an RK06/7 or RL01/2 disk unit, no RT--11 identification was found in block 1 of the destination disk. (User Action) Digital recommends that you stop and initialize the disk volume(s) with the INITIALIZE/BADBLOCKS/REPLACE command before performing the RESTORE operation. This ensures that a valid bad-block-replacement table exists in the volume's home block. You can then reissue the BACKUP/RESTORE command. (?BUP--W--Output volume not resized. SQUEEZE before using.) Directory is fragmented. (User Action)Squeeze to consolidate directory. (?BUP--W--Output volume will be truncated; are you sure?) Insufficient output space to perform entire operation. Output will truncate. (User Action) Ensure that there is adequate output space. (?BUP--W--Tape unit not ready; Continue?) A tape operation cannot complete, because the unit is not ready or off line. (User Action) Make the unit on line and answer (YES) in response to the prompt. (?BUP--W--Verification error at block () [of ()]) The BUP verification procedure encountered a mismatch between the input and output data at block (nnn) of the input device. The () is supplied when errors are found during a verify pass after making a file backup. (User Action) This error is usually caused by a bad block located near block (nnn). Check the output data. It may not be what you expect. (?BUP--W--Verification error at block () [of ()]) The specified data block on the output device does not match that in the input volume. Different situations can cause this: (numbered) You are comparing a backup tape with the wrong disk. You are verifying a system disk, and the contents of the file SWAP.SYS or some other file have changed. Read errors during the original backup made data differences on corresponding blocks. (User Action) (numbered) Mount the correct backup disk and perform the verification procedure. By using the block number and the DIR/BLOCK command, check which files are changed. You must decide if the change warrants making a new backup volume. If you have read errors, try backing up the volume again on another output medium. (?BUP--U--Reboot) Given if the RESTORE operation corrupted the system device. (User Action)Reboot, using a different volume. (?CREF--F--Chain-only CUSP (Vnn.nn)) An attempt was made to use R CREF or the START command to run a copy of CREF that is in memory. (CUSP stands for (Commonly Used System Program).) (User Action) Use a language processor to invoke CREF. (?CREF--F--CRF file error) An input error occurred while DK:CREF.TMP, the temporary input file passed to CREF, was being read. (User Action) Run the language processor again to create a new CREF input file. (?CREF--F--Device not found) (numbered) A listing was written to magtape before the magtape was manually loaded. The input file to CREF (CREF.TMP) is not on a random-access device. The language processor chaining to CREF specified an invalid device. This may be a system error. (User Action) (numbered) Before writing a listing to magtape use the LOAD command to manually load the appropriate device handler. Verify that CREF.TMP is on a random-access device and that CF: is assigned to it. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?CREF--F--File created: protected file already exists) A protected listing file exists along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?CREF--F--LST file error) An output error occurred while the cross-reference table to the listing file was being written to. The output volume may not have enough free space for the listing file. (User Action) See (ism_sec) for information on how to increase storage space. If the error persists when space is adequate, check the procedures for recovery from hard error conditions listed in (hec_sec). (?CSI--F--Device full) The output file created by a user program using .CSIGEN with terminal input did not fit on the device specified. (User Action) See (ism_sec) for information on how to increase storage space. Use the /ALLOCATE option or the CSI square bracket ([]) construction to specify the size of the output file. (?CSI--F--File not found) The input file called by a user program using .CSIGEN with terminal input was not found. (User Action) Check for a typing error in the command line. Verify that all file names exist as entered in the command line and try the operation again. (?CSI--F--Invalid command) The command line in a user program using .CSIGEN or .CSISPC with terminal input contains a syntax error. (numbered) An RT--11 directory-structured device was specified for output without a file name---for example, *RK1:= RK1:RT11FB.SYS/U. A command line contains more than 80 printing characters before a RETURN or the line contains invalid characters, such as blanks. Too many files and devices were specified in a keyboard monitor command. Input to a .GTLIN request contains more than 80 characters. (User Action) Check for a typing error in the command line. Check the format of the monitor command and reenter it. Try to simplify the command and retype it.
Make sure that input to a .GTLIN request does not exceed 80 characters. (?CSI--F--Invalid device) The device specified in a user program using .CSIGEN with terminal input does not exist.
A device, such as BA, was referenced, probably in a TYPE command. But that device handler does not exist on the system device, even though a SHOW command lists the device as valid. (User Action) Check for a typing error in the command line. Make sure that the device indicated is a valid device. (?CSI--F--Prot file) One or more files specified in a user program using .CSIGEN with terminal input already exist and are protected. (User Action) Choose a different name for the new output file or delete, rename, or change the protection code of the existing file with the UNPROTECT command or the PIP /Z option. (?DIR--F--Device not active) Input or output was requested for a device that was not on line, not write enabled, or not in the system's device tables. (User Action) Make sure that the device is on line and is write enabled. Use the INSTALL command to enter the device into the system's device tables. (?DIR--F--Error reading directory) A hardware error occurred while the directory was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?DIR--F--File created; protected file already exists ()) A protected directory file exists along with a newly created unprotected file of the same name. (User Action) List the directory unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?DIR--F--Input error ()) A hardware error occurred when DIR tried to open the input file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?DIR--F--Insufficient memory) Not enough memory is available to perform the directory sort specified. (User Action) Use fewer file names in the sort. Specify only the necessary files or exclude files that do not need to be sorted. Use the DIR /P or the DCL /EXCLUDE option; for example, use /EXCLUDE *.SYS to exclude all system files. (?DIR--F--Invalid command) An incorrect command format was used with the DIRECTORY command. (User Action) Check the format of the DIRECTORY command; correct any typing errors and enter the command again. (?DIR--F--Invalid device ()) The desired operation cannot be performed on the device specified, because the device is not directory and file structured, such as or LP. (User Action) Use a valid device name in the command. (?DIR--F--Invalid directory) An attempt was made to read a directory not in RT--11 format. (User Action) If the volume is from another system, use the corresponding option for that format; for example, use /DOS to read a RSTS directory. (?DIR--F--Invalid option: /x) An invalid option was used in the command line. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for a list of valid options. (?DIR--F--Output error ()) A hardware error occurred while the output file was being written. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?DIR--F--Output file full) The output file is full. (User Action) Send the output from the DIRECTORY command to a printing device or use the /ALLOCATE option to specify the size of the output file. See (ism_sec) for information on how to increase memory and storage resources. (?DIR--F--Protected file already exists ()) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?DIR--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (DIR on a previous version of RT--11.) (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?DIR--I--Backup volume---Use BACKUP/DIRECTORY command) The file specified with the DIRECTORY command was created by the BUP utility. (User Action) Enter the command line again, using the BACKUP/DIRECTORY command. (?DU--E--Replacement control table invalid\ ?DU--E--Software write protecting the volume) The DU handler is in the process of replacing bad block(s) on a device and is unable to replace a block on that device. (User Action) Immediately close any open files and back up the volume you are using. Then check for lost data in any file you had open. You cannot write to that volume again without first taking it off line and then placing it again on line. (?DUMP--F--Attempted access beyond end of device caused by: /x) The /x represents the option /E or /O. The block number you specified with the indicated option is larger than the device size. (User Action) Check the device or block size and reenter the block number. (?DUMP--F--Device full ()) The device does not have enough room for the DUMP output file. (User Action) See (ism_sec) for information on how to increase storage space. (?DUMP--F--File or input device not found) The input file was not on the volume specified, or the device was not known to the system. This error occurs if the device was not installed or if its handler was not on the system disk. (User Action) Use the DIRECTORY command to check the file names in the SY directory. Verify that the input file's device handler is on SY. Use the SHOW command to list installed devices and install the appropriate device, if necessary, with the INSTALL command. Type the command again. (?DUMP--F--Input error ()) A hardware error occurred while the input file was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). The /IGNORE or the /G option may be used to disregard input errors. (?DUMP--F--Insufficient memory) Fewer than the minimal 256 words of memory are free for DUMP to use as a buffer. The command is not executed. (User Action) See (ism_sec) for information on how to increase the amount of available memory. (?DUMP--F--Invalid command) The DUMP command line has an error, such as more than one input or output file specification. The command is not executed. (User Action) Correct the command line. (?DUMP--F--Invalid option: /x) An option in the command line is invalid, has an invalid value, or has no value where a block number (octal) is required. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for a list of valid options. (?DUMP--F--No LP) A line printer handler was not available on the system. (User Action) Check for a typing error in the command line. Indicate a specific valid output device and file name. (?DUMP--F--Output error ()) The output device is full, or a hardware error occurred in writing the output file. (User Action) See (ism_sec) for information on how to increase storage space. See the procedures for recovery from hard error conditions listed in (hec_sec). (?DUMP--F--Protected file already exists ()) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?DUMP--F--Unexpected EOF ()) DUMP found the end of the file before the last block specified by an /END:block, /ONLY:block, or /START:block option. (User Action) Retype the command, using the block values (octal) of the file to be dumped. Use the DIRECTORY/BLOCKS/ORDER: POSITION command or the DIR /B/S option to show the position on the volume and the starting block for each file. (?DUMP--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (DUMP) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?DUMP--W--File created; protected file already exists ()) A protected file exists along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?DUP--E--Operation not completed) The /WAIT operation was aborted, because the response to the mount message began with an (N) or was a CTRL/C. (User Action) This message informs you that the operation has been aborted. The response to the mount message must begin with a (Y) for the /WAIT operation to continue. (?DUP--E--Output device is smaller than input device\?DUP--E--Output device is truncated ) You issued a COPY/DEVICE/NOQUERY command, and the output device is smaller than the input device. The operation completes, but input data is truncated (lost) on the output device. (User Action) Mount an output device large enough to receive all the data from the input device. (?DUP--E--Output device is smaller than input file\?DUP--E--Output device is truncated ) You issued the command COPY/DEVICE/FILES/NOQUERY, and the output device is smaller than the input file. The operation completes, but input data is truncated (lost) on the output device. (User Action) Mount an output device large enough to receive all the data from the input file. (?DUP--E--Output file is smaller than input device\?DUP--E--Output file is truncated) You issued the command COPY/DEVICE/FILES/NOQUERY, and the output file is not large enough to receive the entire input device. The operation completes, but input data is truncated (lost) on the output file. (User Action) Perform a SQUEEZE operation to consolidate all available free space on the output volume. If the SQUEEZE operation does not produce enough free space, mount another output volume with enough free space to contain the entire input device. (?DUP--F--Bad block in system area ()) DUP found a bad block in a critical area of the disk, making the volume unusable. (User Action) Reformat the volume, if possible; try the operation again. If the error persists, the volume must be replaced. (?DUP--F--Can't squeeze SY: while foreground loaded) A foreground or a system job was loaded when a SQUEEZE command was issued for the system device. (User Action) Stop any foreground or system jobs or wait until they are complete and then unload them. Issue the command again. (?DUP--F--Channel in use ()) An internal DUP error occurred. (User Action) Reboot the system and retry the operation. If the error occurs again, get a new copy of DUP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--F--Channel not open ()) An internal DUP error occurred. (User Action) Reboot the system and retry the operation. If the error occurs again, get a new copy of DUP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--F--Conflicting SYSGEN options) The system device handler and the monitor file have different SYSGEN options enabled. (User Action) Make sure that the correct monitor file was specified in the command. Make sure that the correct device handler is on the volume. (?DUP--F--Device full ()) (numbered) The output volume does not have enough room to receive the specified files or data. No unused area is large enough to create the file.
The specified file and successive files on the input volume are not copied. (User Action) If the CREATE command was used, specify a smaller file size with the /ALLOCATE option or consolidate free space on the output volume with the SQUEEZE command. If the SQUEEZE/OUTPUT command was used, initialize the output volume with fewer directory segments. If the COPY/DEVICE/FILE command was used, copy to a different output volume, or use the SQUEEZE command to create a large enough contiguous unused area on the current volume. (?DUP--F--Directory full ()) The output volume directory does not have enough space to create the output file. (User Action) Use the SQUEEZE command to consolidate free space on the output volume, or copy the output volume to a volume with more directory segments. Enter the command again. (?DUP--F--Directory input error ()) An error occurred while the directory of the specified device was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). Try the operation again. If the error persists, copy as many files as possible to another volume, then reformat the original volume. If the error still occurs, replace the volume. (?DUP--F--Directory output error ()) An error occurred while the directory of the specified device was being written. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). Try the operation again. If the error persists, copy as many files as possible to another volume, then reformat the original volume. If the error still occurs, replace the volume. (?DUP--F--Error reading bad block replacement table ()) An input error occurred while the bad-block replacement table was being read from the specified volume. This table is contained in block 1, the home block of the volume. (User Action) Check for bad blocks on the volume. If the home block is bad, the volume is unusable and must be replaced. See the procedures for recovery from hard error conditions listed in (hec_sec). (?DUP--F--Fetch error ()) (numbered) A serious DUP or internal system error occurred. The copy of DUP.SAV, the monitor file, or the specified device handler may be corrupted on disk. The in-memory copy of DUP or the monitor may be corrupted. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of DUP.SAV and the specified device handler. Retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--F--File not found ()) The specified file was not found. (User Action) Check for a typing error in the command line. Try the operation again. (?DUP--F--Input error () at relative block ()) A hard error occurred during a read operation. (User Action) See the procedures for recovery from hard error conditions in (hec_sec). (?DUP--F--Insufficient memory) Not enough memory is available to complete the requested operation. (User Action) See (ism_sec) for information on how to increase memory space. (?DUP--F--Invalid command) (numbered) The command entered is invalid. The format specification is incorrect. The combination of options specified is invalid. A device is not valid for the requested operation. (User Action) (numbered) Check for a typing error in the command line. Check the format of the command line. See the (sum_book) or the (sug_book) for a list of valid option combinations. Make sure that the specified device is valid for the requested operation and try the command again. (?DUP--F--Invalid device ()) The specified device is not installed in the monitor device tables. (User Action) Check for a typing error in the command line. Use the INSTALL command to add the device to the monitor device tables. (?DUP--F--Invalid directory ()) The volume in the specified device does not contain a valid RT--11 directory structure. (User Action) Initialize the volume before using it for the first time. (?DUP--F--Invalid option: /x) The option specified in the command line is invalid. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for a list of valid options. (?DUP--F--Invalid restore data ()) DUP was unable to execute the INITIALIZE/RESTORE command or the DUP /D option because data stored in the home block of the volume is invalid. (User Action) The volume cannot be restored; files and directory entries present before the volume was initialized are lost. See the (sug_book) for more information about the INITIALIZE/RESTORE command. (?DUP--F--Invalid value specified with option: /x) A value specified is outside the acceptable range. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for a list of valid options and the range of valid values for each option. (?DUP--F--Non-bootable device ()) (numbered) A BOOT or COPY/BOOT command or a DUP /U option was given for a device whose device handler did not contain a primary bootstrap. The colon (:) that must follow the device handler mnemonic is missing. dev: represents the physical device name. (User Action) (numbered) The device cannot be booted. Use another device for the operation. Retype the command, typing a colon after the device driver mnemonic. (?DUP--F--Non-bootable file ()) (numbered) A BOOT or COPY/BOOT command or a DUP /U option was given for a device whose device handler did not contain a primary bootstrap. The colon (:) that must follow the device handler mnemonic is missing. dev: represents the physical device name. (User Action) (numbered) The device cannot be booted. Use another device for the operation. Retype the command, typing a colon after the device driver mnemonic. (?DUP--F--No room for file ()) Not enough room is available on the device to create the file. The unused area is not as large as the value specified with the /ALLOCATE or the DUP[n] option, or a file already occupies the area specified. (User Action) Delete a file or files from the affected area of the volume. (?DUP--F--No space for extension ()) The unused area following the file is not large enough to accommodate the required size specified by the CREATE/EXTENSION command or DUP /T option. (User Action) Specify a smaller value on the CREATE/EXTENSION command or the DUP /T option or delete a file or files from the affected area of the volume. (?DUP--F--No V5 boot on volume) (numbered) An attempt was made to boot a volume that does not contain a bootstrap. An attempt was made to boot a volume containing a bootstrap that is not compatible with RT--11 Version 5. (User Action) (numbered) Use the COPY/BOOT command to copy a bootstrap to the volume. Retry the operation, using the BOOT/FOREIGN command. (?DUP--F--Output error () at relative block ()) A hard error occurred during a write operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?DUP--F--Output file exists ()) A CREATE command specified a file name that already exists on the output volume. No operation is performed. (User Action) Delete the file that exists on the volume or enter the command again, using a different file name. (?DUP--F--Size function failed) An error occurred while DUP was determining the size of the volume mounted in a device. The monitor, the device handler, or DUP may be corrupted. This message also occurs if the unit number specified is not supported by the monitor created through system generation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). Reboot the system and try the operation again. (DUP--F--Too many bad blocks ()) More than 128 bad blocks were encountered during a bad-block scan. (User Action) The volume cannot be used and must be reformatted or replaced. (?DUP--F--Unexpected EOF ()) An internal DUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of DUP.SAV from your distribution volume and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--F--Uninitialized volume ()) The directory of the specified volume is not initialized properly for the command. (User Action) Initialize the directory, using the INITIALIZE command. (?DUP--F--Volume not RT--11 format ()) The specified volume is not in RT--11 directory-structured format. (User Action) Format the volume, using the FORMAT command, or use another volume for the operation. (?DUP--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (DUP) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?DUP--I--No bad blocks detected ()) No bad blocks were detected during the bad-block scan initiated by the (#) #DIRECTORY/BADBLOCKS, the #INITIALIZE/REPLACE, or the INITIALIZE/BADBLOCKS command, or by the DUP /K, /R, or /B option. (User Action) The volume is ready to use. (?DUP--U--Channel not open ()) An internal DUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of DUP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--U--System error) An internal DUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of DUP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?DUP--U--Wrong version of RT--11) An attempt was made to run RT--11 Version 5 DUP on a previous version of the RT--11 system. (User Action) Do not attempt to run RT--11 Version 5 DUP under any RT--11 version preceding Version 5. (?DUP--W--Bad blocks detected ()) A total of () bad blocks were detected during the bad-block scan initiated by the DIRECTORY/BADBLOCKS, INITIALIZE/REPLACE, or INITIALIZE/BADBLOCKS command, or by the DUP /K, /R, or /B option. (User Action) The volume is ready to use. (?DUP--W--Device full ()) The output volume does not have enough room to receive the data specified in a COPY/DEVICE command or a DUP /I operation. (User Action) Use an output volume that is larger than or equal to the input volume. See (ism_sec) for information on how to increase storage space. (?DUP--W--File created; protected file already exists ()) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?DUP--W--Output device is larger than input device) You issued a COPY/DEVICE/NOQUERY command, and the output device is larger than the input device. The operation completed. (User Action) The number of blocks you can address on the output device is reduced, because the /DEVICE option copies the home and directory blocks from the input device to the output device. (?DUP--W--Output device is larger than input file) You issued the command COPY/DEVICE/FILES/NOQUERY, and the device containing the output file is larger than the input file. The operation completed. (User Action) The number of blocks you can address on the output device is reduced, because the /DEVICE option copies the home and directory blocks from the input device to the output device containing the output file. (?DUP--W--Output error ()) An output error occurred during a SQUEEZE operation. (User Action) DUP places a .BAD file over the bad block and continues with the operation. (?DUP--W--Owner name truncated at ten characters) DUP truncated the owner name for a magtape because more than 10 characters were entered as the name. (User Action) If truncation is not acceptable, initialize the magtape again, entering 10 or fewer characters. (?DUP--W--Owner name truncated at twelve characters) DUP truncated the owner name for a disk because more than 12 characters were entered as the name. (User Action) If truncation is not acceptable, use the INITIALIZE/VOLUMEID :ONLY command or the DUP /V option to change the owner name. Remember to enter 12 or fewer characters. (?DUP--W--Replacement table overflow ()) The specified device contains more than the maximum replaceable bad blocks. (User Action) DUP prompts you to determine which blocks should be replaced and which should be made .BAD files. The (sum_book) and the (sug_book) describe how to create files over bad blocks. (?DUP--W--Verification error at relative block ()) During a COPY/DEVICE/VERIFY command, the input data did not match the output data at the specified relative block. (User Action) Check the output volume for bad blocks. See the procedures for recovery from hard error conditions listed in (hec_sec). Try the operation again. (?DUP--W--Volume ID truncated at six characters) DUP truncated the volume ID for a magtape because more than six characters were entered as the ID. (User Action) If truncation is not acceptable, INITIALIZE the magtape again. Remember to enter six or fewer characters. (?DUP--W--Volume ID truncated at twelve characters) DUP truncated the volume ID for a disk because more than 12 characters were entered as the ID. (User Action) If truncation is not acceptable, use the INITIALIZE/VOLUME :ONLY command or the DUP /V option to change the volume ID. Remember to enter 12 or fewer characters. (?EDIT--F--Command aborted) A command was prematurely terminated because (CTRL/C) was pressed twice. (User Action) Examine the effect of the termination for any undesirable conditions and correct, if necessary. (?EDIT--F--Command buffer full; no command(s) executed) The command exceeded the space allowed for a command string in the command buffer. (User Action) Empty the save or the macro buffers, if possible, or write part of the text buffer to the output file. Retype the command and any subsequent lengthy commands as a series of smaller commands or shorter sequences. (?EDIT--F--Device full) Not enough disk space is available to accommodate a file of the size requested in the EW or the EB command or in the /ALLOCATE specification to the EDIT command. (User Action) Use the SQUEEZE command to compress the disk, if possible, or request a file of smaller size. See (ism_sec) for information on how to increase storage and memory resources. (?EDIT--F--Directory full) No room exists in the volume directory for the output file name. This message occurs following an EB or an EW command or the input specification to the EDIT command. (User Action) See (ism_sec) for information on how to increase storage space. (?EDIT--F--End of input file) A READ, NEXT, or file search command was not executed, because the end of the input file was reached. (User Action) Close the file by using EX or EF; reopen it if more editing remains to be done. (?EDIT--F--("<>") error; no command(s) executed) Iteration brackets are nested too deeply, used incorrectly, or not matched. (User Action) Make sure that all brackets are properly matched and that the number of nested brackets does not exceed 20 levels. (?EDIT--F--File not found) An attempt was made to open a nonexistent file for editing. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?EDIT--F--Input error) A hardware error occurred during a read operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?EDIT--F--Insufficient memory) An attempt was made to use the I, S, U, R, N, C, or E command with insufficient room for the appropriate buffer. (User Action) Delete unwanted buffers to create more room by using the 0U or 0M command (see the (sug_book)) or write text to the output file. (?EDIT--F--Invalid argument; no command(s) executed) (numbered) The argument specified is invalid for the command used. A negative argument is specified where a positive one is expected. The argument is outside the range +16,383 to --16,383. (User Action) Check the command format for proper argument usage and reenter the command correctly. (?EDIT--F--Invalid command; no command(s) executed) (numbered) The editor does not recognize the command line specified. ED was not the first command used to activate the display hardware. (User Action) (numbered) Check for a typing error in the command line. Check the format of any editing command that produces this error and enter the command correctly. Recall the editor and type ED before entering any other editing commands. Remember to type the insert command (I) before inserting text. (?EDIT--F--Invalid device) An attempt was made to open a file on an invalid device or to use display hardware when none is available. (User Action) Check for a typing error in the command line. Verify that the device indicated is valid and that display hardware exists and is not already in use by another job. (?EDIT--F--Invalid file name) An invalid file name was specified in an EB, EW, or ER command, or as input to the EDIT command. (User Action) Check for a typing error in the command line. Make sure that the dev:filnam.typ[size] specification does not exceed 19 characters and is in the proper format. Verify that an input file name exists as entered. (?EDIT--F--Invalid macro; no command(s) executed) (numbered) Delimiters in an M command are used improperly. An attempt was made to enter an M or an EM command during execution of a macro. (User Action) (numbered) Check for a typing error in the command line. Make sure that the character used for the delimiters does not appear in the macro. Try the command again and wait until the current macro has finished executing before entering the M or EM command. (?EDIT--F--No file open for input) An R, N, F, or P command was issued, but no file had been opened for input. (User Action) Check for a typing error in the command line. Use the ER command to open a file for input and then reenter the command. (?EDIT--F--No file open for output) An EX, EF, F, or W command was issued, but no file had been opened for output. (User Action) Check for a typing error in the command line. Use the EW command to open a file for output and then reenter the command. (?EDIT--F--Output error) A hardware error occurred during a write operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?EDIT--F--Output file full) No free space is left in the output file. (User Action) Close the file by using an EF command or close the file and open a new file for output by using the EW command. (?EDIT--F--Protected file already exists) An attempt was made to edit a protected file or to create a protected file with the same name as an existing file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?EDIT--F--Protected .BAK file exists) A protected .BAK file having the same name as the specified file has already been created in an edit BACKUP operation. (User Action) Exit from EDIT, then use the UNPROTECT command or the PIP /Z option to change the protection level of the backup file. Perform the edit BACKUP operation again. (?EDIT--F--Search failed) The text string specified in a G, F, or P command was not found. (User Action) Check for a typing error in the command line. Make sure that the text string exists in the file as specified in the command line. If this error occurs following a Get command, the pointer is positioned at the end of the current text buffer and the command can be reentered. If the error follows a Find or a Position command, the end-of-file is detected and the pointer is positioned at the beginning of an empty text buffer; close the file, reopen it, and then reenter the command. (?EDIT--F--System I/O error) A system operation, such as opening a file, failed because of an I/O error, most probably one involving a write protected volume. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?EDIT--W--Command buffer almost full) The command entered is within 10 characters of exceeding the space available in the command buffer. (User Action) Complete the command, using fewer than 10 characters, if possible. Otherwise, press the (ESCAPE) key twice to execute that portion of the command line already completed and then enter the remainder as a second command. (?EDIT--W--Superseding existing file) An EW or an EB command was issued for an already existing file name. If the new file is closed, the old one will be deleted. (User Action) To avoid replacing the file, terminate the edit with CTRL/C, followed by two ESCAPEs. Then use the REENTER command. (?EL--W--Device statistics table is full) The error logger is maintaining statistics for the number of devices selected during system generation. Error reports from any device will be logged, but statistics will be maintained only for those devices already having statistics entries. This state does not affect the operation of the system. (User Action) Perform another system generation and select support for more devices. (?EL--W--Special function table is full) The error logger's table of special functions, which the error logger uses to look up the type of an .SPFUN, is full. Any device handler's .SPFUNs that are not in the table will be logged as type "Unknown". (User Action) To free up space in the error logger's .SPFUN tables, use the REMOVE command to remove some device handlers. Then restart the error logger. This action makes space available in the error logger's .SPFUN table, which had been used by .SPFUNs from the removed handlers. (?ELINIT--F--Channel error) An internal error occurred. (User Action) Retry the operations that produced the error. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ELINIT--F--Device full) Not enough room is available on the specified device to create or expand the ERRLOG.DAT file. (User Action) Use the SQUEEZE command or the DUP /S option to compress the volume, or use a different disk for the operation. See (ism_sec) for information on how to increase memory and off-line storage resources. (?ELINIT--F--Device not available) The device requested by the operator is not loaded. (User Action) Load the device handler and run ELINIT again. (?ELINIT--F--ERRLOG.DAT file I/O error) An error was encountered while reading or writing the ERRLOG.DAT file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?ELINIT--F--ERRLOG task not active ) An attempt was made to initiate error logging before running the error logging job. (User Action) Run ERRLOG, using the FRUN or the SRUN command, before running ELINIT. (?ELINIT--F--Internal error) An internal error occurred while the error logger was recovering from a previous system or user error. (User Action) Retry the operations that produced the error. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ELINIT--F--Protected file already exists ERRLOG.DAT) The ERRLOG.DAT file is protected. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. Then run ELINIT again. (?ELINIT--W--File not found DK:ERRLOG.DAT) You want the statistics file ERRLOG.DAT written, and ELINIT checks the default data device (DK) for ERRLOG.DAT. But ERRLOG.DAT is not on DK, so ELINIT then writes ERRLOG.DAT on DK. (User Action) This message is informational. (?ELINIT--W--File not found ()) You specified a valid device that does not contain the file ERRLOG.DAT, but ELINIT then writes the file ERRLOG.DAT on that device. (User Action) This message is informational. (?ELINIT--W--Invalid command) An invalid answer was given to an operator command initialization question. The question is asked again. (User Action) Correct the response to the question. (END BATCH) A BATCH job was terminated. Control returns to the monitor. (User Action) This message is informational. (?ERRLOG--F--Channel error) An internal error occurred. (User Action) Retry the operations that produced the error. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ERRLOG--F--Internal error) An internal system error occurred. (User Action) Retry the operations that produced the error. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ERRLOG--F--Invalid message received) ELINIT sent invalid information to ERRLOG. This can happen if you attempt to examine the contents of the error log before running ELINIT. (User Action) Build the error logger over again and run ELINIT before examining the error log. (?ERRLOG--F--Log file I/O error) An error was encountered while reading or writing the ERRLOG.DAT file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?ERRLOG--I--REMINDER: To initiate error logging, RUN ELINIT) ERRLOG prints this message as a reminder that you must run the ELINIT program to initiate error logging. (User Action) This message is informational. (?ERRLOG--I--To initiate error logging, RUN ELINIT) To initiate error logging, run the ELINIT program. (User Action) This message is informational. (?ERRLOG--W--Device statistics table is full) Insufficient space was allocated for the number of errors detected. (User Action) Table size is controlled by the SYSGEN conditional ERL$U. Perform SYSGEN and increase the value of ERL$U to increase the size of the statistics table. (?ERRLOG--W--Invalid message received) A task or a background job other than ERROUT tried to communicate with the ERRLOG task, but ERRLOG ignored this. One way this can happen is to run ELINIT more than once. (User Action) This message is informational. (?ERRLOG--W--Log Buffer Full---an error record counted but discarded) The internal logging buffer is full. Logging of new reports has been suspended, but statistics will continue to be maintained along with a count of the reports not logged. This state does not affect the operation of the system. (User Action) The current contents of the internal logging buffer may be discarded by using the SET EL PURGE command. Statistics are not affected. (?ERRLOG--W--Log File Full---an error record counted but discarded) The ERRLOG.DAT file is full. The header block continues to be updated, but error records are not recorded. (User Action) To save the contents of ERRLOG.DAT, copy it to another file name. To save more error records, terminate ERRLOG and reinitialize to enable error logging again. (?ERRLOG--W--Special Function table is full) The error logger's table of special functions, which the error logger uses to look up the type of an .SPFUN, is full. Any device handler's .SPFUNS that are not in the table will be logged as type "Unknown". (User Action) To free up space in the error logger's .SPFUN tables, use the REMOVE command to remove some device handlers. Then restart the error logger. This action makes space available in the error logger's .SPFUN table, which had been used by .SPFUNS from the removed handlers. (ERROR: FORTRAN IV messages) (The FORTRAN IV error messages have been removed from this manual. See the separate FORTRAN documentation for explanations of all FORTRAN error messages.) (?ERROUT--F--Channel error) An error occurred within the ERROUT program. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ERROUT--F--Device not found) The device specified in the command string was not found. (User Action) Make sure that the specified device is installed. Reenter the command. (?ERROUT--F--File not found) The input file containing the error log statistics was not found. (User Action) Make sure that the specified file resides on the specified device. Reenter the command. (?ERROUT--F--Input error) A hardware error occurred. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?ERROUT--F--Insufficient memory) Not enough memory is available to process the statistics file. (User Action) See (ism_sec) for information on how to increase memory resources. (?ERROUT--F--Internal error) An error occurred within the ERROUT program. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?ERROUT--F--Invalid command) The ERROUT command is not in the correct format. (User Action) Make sure that the command is typed in the correct format. Enter the command again. (?ERROUT--F--Output error) A hardware error occurred. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?ERROUT--F--Output file full) The output file does not have enough room to continue writing. (User Action) See (ism_sec) for information on how to increase storage space. (?ERROUT--F--Protected file already exists) An attempt was made to create a report file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?ERROUT--W--Device full) Not enough room is available on the specified device to create the output file. (User Action) Use another device for this operation or use the SQUEEZE command on the device to create more room. (?FILEX--E--Operation not completed) The /WAIT operation was aborted, because the response to the mount message began with an N or was a CTRL/C. (User Action) This message informs you that the operation has been aborted. The response to the mount message must begin with a Y for the /WAIT operation to continue. (?FILEX--F--Channel not open) An I/O channel that FILEX required for the command is not open. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?FILEX--F--Device full) The output directory does not have room for the file name, or the output volume does not have room for the file. (User Action) See (ism_sec) for information on how to increase storage space. (?FILEX--F--Directory input error) An error occurred while the directory of the input device was being read or looked up, or the input device does not have the proper file structure. (User Action) Check for a typing error in the command line. Verify that the input device has the correct structure. If it does, a hard error condition exists. Check the procedures for recovery from hard error conditions listed in (hec_sec). (?FILEX--F--File already exists ()) An attempt was made to create the named file on a DOS DECtape when a file already existed under the name specified. (User Action) Use the /D option to delete the file and try the transfer again or use a new name to create the file. (?FILEX--F--File created; protected file already exists) A protected file exists, along with a newly created unprotected output file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?FILEX--F--File not found) The input file was not found, or the wildcard construction matched none of the existing files. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?FILEX--F--Foreground loaded) An attempt was made to use the /T or /TOPS option when a foreground job was active. (User Action) Terminate the foreground job and unload it, using the UNLOAD FG command. (?FILEX--F--Input error) A hardware error occurred during an input operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?FILEX--F--Insufficient memory) Not enough room is available in memory for buffers and input list expansion. (User Action) See (ism_sec) for information on how to increase memory space. Try copying the files one at a time without using the wildcard construction on input. (?FILEX--F--Invalid command) (numbered) The length of the command line exceeds 72 characters. The command line is not in the proper CSI format. The UIC exceeds the allowed number of characters, or square brackets ([]) are unbalanced. A wildcard construction was used on a sequential-access device. No output or no input file was specified for a copy operation. More than one file name construction (dev:filnam.typ) was specified on either side of the equal sign (=). An operation that FILEX cannot perform was attempted---for example, initializing an RT--11 device. (User Action) Check for a typing error in the command line. Verify that the format of the command line is correct and that the UIC is in the proper format. Verify that FILEX can perform all specified operations. Then retry the operation. (?FILEX--F--Invalid device) (numbered) The device handler was not found. An invalid device name was used. One of the following was attempted: (unnumbered) RK or DT was not used for DOS/BATCH (RSTS) in a copy operation. DT was not used for DOS/BATCH (RSTS) output in an initialize or a delete operation. DT was not used for DOS/BATCH (RSTS) output in a copy operation. DT was not used for DECsystem--10 input in any operation. (User Action) Check for a typing error in the command line. Make sure that necessary device handlers are present on the system and that the device indicated is a valid device name and is valid for the operation indicated. (?FILEX--F--Invalid option) An invalid option was used in a command line. (User Action) Check for a typing error in the command line. See the (sum_book) or the (sug_book) for a list of valid commands. (?FILEX--F--Invalid option combination) (numbered) An attempt was made to use more than one device option (/S, /T, /U), transfer option (/I, /P, /A), or operation option (/D, /L, /F, /Z) in a FILEX command line. Only one option can be used per combination. An attempt was made to combine /DOS and /TOPS in a COPY or a DELETE command, to use /IMAGE and /ASCII together on a copy operation, or to use one of these with /INTERCHANGE on a DELETE operation. (User Action) Check the command line for invalid combinations. Issue the command again. (?FILEX--F--Invalid output filename) The output file name is invalid or null. (User Action) Check for a typing error in the command line. Verify that an output file name was specified in the correct format and that it contains no invalid characters. (?FILEX--F--Invalid PPN format) The DOS/BATCH user identification code was not in the form [nnn,nnn], where each nnn is an octal number less than or equal to 377. (User Action) Check the format of the user identification code. (?FILEX--F--Invalid value specified with option : /V) You typed something other than the FILEX /V[:ONL] option when attempting to initialize an interchange diskette. (User Action) Check for a typing error in the command line and retype the command. (?FILEX--F--Not interchange format) The /P option or the /INTERCHANGE command was used, and a diskette did not have a directory in universal interchange format. (User Action) Check for a typing error in the command line. Verify that the diskette has a directory in universal interchange format. (?FILEX--F--Output error) An unrecoverable error occurred while an output file was being processed. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?FILEX--F--Protected file already exists ()) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?FILEX--F--UFD not found) The specified UFD was not found on the DOS input disk. (User Action) Verify that no typing error has been made and that the input disk is the correct one. (?FILEX--F--Unexpected EOF) During a transfer between a volume in RT--11 format and a volume in universal interchange format, the system detected the end of the file on the interchange volume before completing the transfer. Attempts to read a faulty diskette or to read or write with a faulty device can cause this error. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). If the error occurs on input hardware that is operating properly, check the hardware that wrote the input volume, if possible. (?FILEX--F--Unsupported operation) You used the FILEX /V option without the /U interchange option. Or you specified an input device identical to the output device. (User Action) Retype the command specifying the FILEX /V option with the /U option or using different devices. (?FILEX--W--Volume ID truncated at six characters) FILEX truncated the volume ID for a magtape because more than six characters were entered as the ID. (User Action) If truncation is not acceptable, initialize the magtape again. Remember to enter six or fewer characters. (?FORMAT--E--Operation not completed) The /WAIT operation was aborted because the response to the mount message began with an N or was a CTRL/C. (User Action) This message informs you that the operation has been aborted. The response to the mount message must begin with a Y for the /WAIT operation to continue. (?FORMAT--F--Bad sector (RK06/07)) A sector was marked as bad but no header check error occurred. The sector cannot be replaced by the DM handler. (User Action) Initialize the device, using the INITIALIZE/BADBLOCKS /REPLACE command so that FILE.BADs can be created for the bad sectors to prevent them from being used. (?FORMAT--F--Device error) An error occurred while FORMAT was attempting to format the device, or the unit number specified does not exist. (User Action) Make sure that the unit number specified is valid. If the problem appears to be a hardware error, see the procedures for recovery from hard error conditions listed in (hec_sec). (?FORMAT--F--Device invalid or not supported by FORMAT) The FORMAT program did not recognize the device specified. (User Action) Retype the command line, using a valid device specification. You may have to install the device handler for the specified device. (?FORMAT--F--Device not ready) The device specified is not ready to be formatted or verified because the device is off line, write protected, or not up to speed. (User Action) Check the device unit. Make sure that it is powered up, that the volume is write enabled, and that the device---if it is a disk---is up to speed. (?FORMAT--F--Error reading manufacturer's bad sector file (RK06/07)) Sectors on the last file of the last track contain a manufacturer's bad sector on an RK06 or an RK07; the file could not be read. Execution terminates. (User Action) Use another disk. (?FORMAT--F--Error writing headers (RK06/07)) The FORMAT program encountered errors while writing headers to a track on an RK06 or RK07. Execution terminates. (User Action) Use another disk. (?FORMAT--F--Error writing software bad block file) Formatting was successful, but no software bad-block table was written. (User Action) FORMAT prompts for another command. No corrective action is necessary for this condition. (?FORMAT--F--File not found) FORMAT received an error when attempting a .LOOKUP on the device handler file. This error can occur if the device handler was renamed. (User Action) Use a device handler that has not been renamed. (?FORMAT--F--Input error) A hardware error occurred during a read operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?FORMAT--F--Insufficient memory) Not enough memory is available to perform the specified function. (User Action) See (ism_sec) for information on how to increase memory resources. (?FORMAT--F--Invalid command line) The command line typed is incorrect, possibly because an output as well as an input device was specified; more than one input device was specified; or a file name was given with the device specification. (User Action) Reenter the command line in the format input-device[/options]. (?FORMAT--F--Invalid device for FORMAT) You attempted to format an RX50 diskette. RX50 diskettes are preformatted in the factory, and FORMAT does not support formatting them. (User Action) Use the FORMAT/VERIFY:ONLY command to verify the format on an RX50 diskette. (?FORMAT--F--Invalid device for /VERIFY, or not formatted) An attempt was made to verify an unformatted disk. (User Action) Format the unformatted disk, install and load its device handler, and then verify the disk. (?FORMAT--F--Invalid option: /x) The option specified (/x) is not a valid option for the device specified. (User Action) Reenter the command line and use only valid options. See the (sum_book) or the (sug_book) for a summary of valid options. (?FORMAT--F--Invalid option /x:val) The specified option (/x) does not accept an argument. FORMAT prompts for another command. (User Action) Reenter the command line and use only valid syntax. See the (sum_book) or the (sug_book) for a summary of valid options. (?FORMAT--F--Invalid value specified with option: /x) An invalid value was specified with option /x. (User Action) Reenter the command line and use only valid syntax. See the (sum_book) or the (sug_book) for valid option values. (?FORMAT--F--LOOKUP ERROR) An internal logic error occurred when you attempted to open a volume. (User Action) Try the operation again. If the problem persists, submit an SPR to Digital. (?FORMAT--F--Manufacturer's bad sector file corrupt (RK06/07)) The manufacturer's bad sector file is not in a valid format on an RK06 or an RK07. Execution terminates. (User Action) Use another disk. (?FORMAT--F--Operation unsupported on old micro-code revision) You attempted to format an RX33 diskette, and your RQDX3 controller is below microcode revision 2. (User Action) Contact your local Digital field service representative to update your RQDX3 controller. (?FORMAT--F--Unit number too large for RT--11 configuration) The unit number specified exceeds the number of units on the configuration. (User Action) Check the number of the required unit. Issue the command again. (?FORMAT--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (FORMAT) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?FORMAT--I--Formatting aborted) A device error occurred. Formatting is aborted. (User Action) The device must be formatted successfully before it can be used. Run the FORMAT program again. (?FORMAT--I--Formatting complete) The device is now formatted. (User Action) The device is ready for use. (?FORMAT--I--Install DW) After the processor hard disk has been formatted, its associated device handler DW must be installed. (User Action) This is an informational message; issue the INSTALL DW command to install the DW device handler. (?FORMAT--I--PATTERN #nn) FORMAT displays the format pattern on a disk when it does a verification of that pattern on the disk. (User Action) This message is informational. (?FORMAT--I--Verification aborted) A device error or a user abort caused the pattern verification to terminate. (User Action) Rerun the pattern verification to verify the volume, if necessary. See the procedures for recovery from hard error conditions listed in (hec_sec). (?FORMAT--I--Verification complete) The FORMAT program verification sequence is complete. (User Action) This message is informational. (?FORMAT--U--Channel in use) There is an internal FORMAT error. (User Action) Reboot your system and try the operation again. If the error still occurs, get a new copy of FORMAT.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?FORMAT--U--Device handler fetch error) The handler could not be fetched, probably because the device handler was not present to perform device verification. (User Action) Make sure that the device handler for the disk being verified resides on the system volume. Run the FORMAT program again. (?FORMAT--U--Disk is an alignment cartridge) The RK06/07 disk selected for formatting is an alignment disk. Execution terminates. (User Action) Use another disk. (?FORMAT--U--Formatting/Verifying the system volume is not allowed) An attempt was made to format or to verify the volume on which the running RT--11 system currently resides. (User Action) Specify a different device unit number and format the device. You can also use the /WAIT or the /W option, which permits a pause before formatting begins, so a second volume can be substituted for the system device. See the (sum_book) or the (sug_book) for information on how to do this. (?FORMAT--U--Too many bad blocks ()) The software bad-block limit was exceeded. (User Action) Use another disk for the operation. (?FORMAT--W--Duplicate option: specified /x) The option (/x) was already specified in the command line. (User Action) Check the command line for duplicate options and enter the command again. (?FORMAT--W--Foreground loaded () /FORMAT--Are you sure?) You ran FORMAT with the foreground loaded. (User Action) If this causes no problem, type Y (RET) to continue. Otherwise, type N (RET) to abort formatting the disk. (FORTRAN messages) The FORTRAN messages have been removed from this manual. Look in the separate FORTRAN documentation for explanations of all FORTRAN error messages. (?GIDIS--F--Error attaching to global region VM:filnam.typ) GIDIS was unable to attach to the specified global region. (User Action) Issue the SHOW MEMORY command and verify that the specified global region exists in extended memory. If not, be sure that the version of the monitor you are using is RT--11 V5.2 or later.
If the global region is shown in extended memory and the error persists, submit an SPR to Digital. Include with your SPR a program listing and a machine-readable source of the program, if possible. (?GIDIS--F--Extended memory monitor required for GIDIS.SAV) An attempt was made to run GIDIS.SAV, using the unmapped monitor. (User Action) Use only the mapped monitor when running GIDIS. (?GIDIS--F--File not found ALPH00.FNT) An attempt was made to run GIDIS without having the file ALPH00.FNT on DK. ALPH00.FNT must be on DK to run GIDIS. (User Action) Copy ALPH00.FNT to DK, then run GIDIS. (?GIDIS--F--Floating point unit required) An attempt was made to run GIDIS on a processor that does not have the FP--11 floating point chip. (User Action) Install the FP--11 floating point chip, then run GIDIS. (?GIDIS--F--GIDIS must be run as a foreground job) An attempt was made to run GIDIS as other than the foreground job. (User Action) Use the command FRUN GIDIS.SAV to run GIDIS as the foreground job. (?GIDIS--F--GIDIS must be run on a PROFESSIONAL series processor) An attempt was made to run GIDIS on a processor other than a CTI Bus-based processor. (User Action) Use a CTI Bus-based processor to run GIDIS. (?GIDIS--F--Input error ()) GIDIS detected a hard error when reading the file (). (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec) of this manual. (?GIDIS--F--Insufficient memory) An attempt was made to run GIDIS on a system with less than the required amount of extended memory. (User Action) GIDIS requires a minimum of 26K bytes of extended memory. Issue the SHOW MEMORY command and look at the allocation of extended memory. Unload any unneeded jobs that use extended memory until the required minimum is available for GIDIS. (?HELP--F--File not a valid library HELP.MLB) The file HELP.MLB is not in proper library format. (User Action) Create the file HELP.MLB by processing HELP.TXT with the librarian after editing HELP.TXT. See the procedures for customizing the HELP text in the (ins_book). (?HELP--F--File not found HELP.MLB) The file HELP.MLB was not found on either SY or DK, and HELP was built to run without an integral text file. (User Action) Copy HELP.TXT from the system backup volume onto SY, if SY has room for it, and use LIBR to create HELP.MLB. Copy the file to DK if SY does not have room. Alternatively, copy HELP.SAV from the distribution volume. (?HELP--F--HELP not available for ?) HELP text is not available for the command HELP ?. (User Action) Issue the HELP command by itself for an explanation of how to use that command. (?HELP--F--Help not available for topic ()) The information requested is not available. (User Action) Consult the (sug_book), the (sum_book), or an experienced user. (?HELP--F--HELP.MLB has invalid format) The file HELP.MLB is in library format but contains a line that is not in valid format. (User Action) See the procedures for customizing the HELP text in the (ins_book). Make sure that you do not corrupt the format of lines in the file HELP.MLB after it has been created by processing HELP.TXT with the librarian. (?HELP--F--Insufficient memory) An internal error occurred. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?HELP--F--Invalid option, type 'HELP ()') An invalid HELP option was specified. (User Action) Check the command line for a typing error. Type HELP (RETURN) or see the (sug_book) for a list of valid HELP options. Retry the operation. (?HELP--F--Read error on HELP.MLB) A hard error occurred while the file HELP.MLB was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?HELP--F--Syntax error in command, type 'HELP ()') The HELP command was improperly formatted. (User Action) Type HELP (RETURN) for a listing of the HELP command text and an explanation of how to use the HELP command. (?HELP--F--Write error on LP:) A hard error occurred during a write operation to the printer. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?HELP--W--Help not available for subtopic ()) The information requested is not available. (User Action) Consult the (sug_book), the (sum_book), or an experienced user. (?HELP--W--Help not available for subtopic item ()) The information requested is not available. (User Action) Consult the (sug_book), the (sum_book), or an experienced user. (?HELP--W--Line printer not available---using terminal) An attempt was made to output information from the HELP text to a line printer not present in the system, or the handler is not installed. The output will be sent to the console terminal. (User Action) Verify that the printer specified is installed in the system. (Control File Messages) The format for control file messages is described in (isp_sec). (?IND--E--Invalid Answer or Terminator) (numbered) IND encountered an invalid response to an .ASK, .ASKN, or .ASKS directive prompt. For example, an alphabetic character response may have been given to an .ASKN prompt. Escape recognition is disabled, and an escape character was entered in response to a prompt. The prompt is repeated. (User Action) Make sure that the response to the .ASK, .ASKN, or .ASKS prompt is valid. (?IND--E--String length not in range) The response entered to an .ASKS directive prompt fell outside the range designated by the prompt. The prompt is repeated. (User Action) Make sure that the response entered is within the specified range. (?IND--E--Value not in range) The numeric value entered in response to an .ASKN directive prompt fell outside the range designated by the prompt. The prompt is repeated. (User Action) Make sure that the response entered is within the specified range. (?IND--F--Bad range or default specification) (numbered) The default response fell outside the range specified with an .ASKN or an .ASKS prompt; the range used an invalid radix; or the range was specified in an invalid sequence. The optional default value assigned to the symbol in the .ASKS directive is not a string literal or another string symbol. (User Action) (numbered) Make sure that a valid radix is used in the range specification and that the range is specified from low to high. Make sure that the default value assigned to the symbol in the .ASKS directive is a string literal or another string symbol. (?IND--F--Data file error) A hard error was encountered while IND was processing an .OPEN, .OPENA, .CLOSE, or .DATA directive or a data mode access to the output file.
This message sometimes includes a secondary error message. For a listing of the secondary message and its explanation, see the (IND Secondary Input/Output Error Messages) at the end of the IND message listings. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?IND--F--Data file open) IND attempted to execute a keyboard command before closing open files. (User Action) Close open files before the control file exits from IND. (?IND--F--Deleting special symbol) An attempt was made to delete an IND special symbol. (User Action) Check for a typing error. Do not try to delete an IND special symbol. (?IND--F--Error reading from terminal) IND encountered an error while trying to receive data from the console.
This message sometimes includes a secondary error message. For a listing of the secondary message and its explanation, see the (IND Secondary Input/Output Error Messages) at the end of the IND message listings. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?IND--F--File already open) An attempt was made to open a file with the .OPEN, .OPENA, or .OPENR directive and the file is already open. (User Action) Make sure that the file is closed before trying to open it. (?IND--F--File not found) The control file IND tried to process does not exist in the directory of the specified volume. (User Action) Check the control file specifications to make sure that they are correct and that the specified control file exists. Also, make sure that the specified volume is mounted. (?IND--F--File not open) An attempt was made to access a file that is not open. (User Action) Make sure that the file is open before trying to access it. (?IND--F--File read error) A hard error occurred when IND tried to read a file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?IND--F--Invalid attempt to erase symbol) An attempt was made to delete a symbol outside a Begin/End block. (User Action) Try the operation again. Delete symbols only within the current Begin/End block. (?IND--F--Invalid command) IND encountered an error in a command line used to execute another control file. (User Action) Make sure that nested control file specifications and options are correct. See the (sug_book) for information on nested control file specifications and options. (?IND--F--Invalid device or unit) The device specification for a file IND tried to access is invalid, or the device specification is for a nonexistent device. (User Action) Make sure that all device specifications are valid. (?IND--F--Invalid device or unit, device is attached) The .VOL directive was issued for a device assigned to the foreground or a system job using the LOAD ddn:=F or LOAD ddn:=job commands. (User Action) You can intercept that error by using the .ONERR directive. Use the .TESTDEVICE directive to determine if the device is attached and to what job. (?IND--F--Invalid file number) The file number specified is outside the valid range 0 to 3. (User Action) Make sure that the file number falls within the valid range. (?IND--F--Invalid keyword) An unrecognized keyword, preceded by a period, was specified in the command. (User Action) Make sure that all directives are spelled correctly and that the directives are in the correct syntax. (?IND--F--Invalid nesting) IND found .END without .BEGIN or .BEGIN without .END directives in the control file. (User Action) Make sure that each .BEGIN and .END directive has a corresponding .END and .BEGIN directive. (?IND--F--Invalid operator for operation) You attempted to use an arithmetic operator (+, --, *, or /) in a logical expression with the .SETL directive. (User Action) Do not use arithmetic operators in .SETL logical expressions. Use only the logical operators & (AND), ! (OR), and ^ (NOT). (?IND--F--Invalid option) IND encountered an unrecognized option. (User Action) Enter the command again. Use only the valid options listed in the (sug_book). (?IND--F--Label not at beginning of line) A label does not appear as the first character(s) on a line, except for spaces or tabs. (User Action) Make sure that the labels have no embedded spaces and that the labels do not appear in the middle of the command line. (?IND--F--Maximum indirect files exceeded) An attempt was made to access a control file at a depth greater than three levels. (User Action) Make sure that the nesting limit of three is not exceeded. This limit does not include the initial level. (?IND--F--Null control string) No delimiters were defined in a .PARSE directive control string. A control string cannot be null. (User Action) Make sure that the correct syntax is used for a control string. (?IND--F--Numeric under- or overflow) A value assigned as a numeric symbol falls outside the valid range 0 to 177777 (octal) or 65535 (decimal). (User Action) Make sure that all numeric symbols have values within the valid range. Make sure that no arithmetic expression that IND tries to assign to a numeric symbol yields a result outside the valid range. (?IND--F--Prompt string too large) The prompt issued with the .ASK, .ASKN, or .ASKS directive has too many characters. (User Action) Specify a prompt that has a valid number of characters. (?IND--F--Redefining special symbol) An attempt was made to change the value of a special symbol. (User Action) Do not try to change the value of an IND special symbol. (?IND--F--Redefining symbol to different type ()) (numbered) An .ASK, .ASKN, .ASKS, .READ, .SETT, .SETF, .SETL, .SETN, or SETS directive was used in an attempt to set the specified defined symbol to a different type. The first definition of a symbol determines its type, and subsequent redefinitions must conform to the original type. The numeric symbol specified with the .SETT, .SETF, or .SETL directive has not been previously defined. The numeric symbol specified with the .IFT or .IFF directive has been defined as a logical or string symbol. (User Action) (numbered) Do not try to change the type of a defined symbol. If you redefine a symbol, make sure that the new definition has the same type as the original symbol. Define the numeric symbol being used before you specify it with the .SETT, .SETF, or .SETL directive. Define a new symbol as a numeric type. Specify the numeric symbol with the .IFT or .IFF directive. (?IND--F--.RETURN without .GOSUB) A .RETURN statement does not have a corresponding .GOSUB statement. (User Action) Make sure that there are no extraneous .RETURN statements and that all .GOSUB statements are used correctly. Make sure that all .RETURN statements are located correctly in the program logic. (?IND--F--String expression exceeded limit) The limit of 132 characters in a string expression was exceeded; a string concatenation operation yielded a string that exceeds the 132-character limit; or quotes do not appear at the end of a string expression. (User Action) Make sure that string expressions do not exceed the 132-character limit. Make sure that all string expressions are properly enclosed by quotes. (?IND--F--String substitution error) IND encountered an error while substituting a symbol. (User Action) Make sure that all substituted symbols have been defined and that each substituted symbol is enclosed with apostrophes. (?IND--F--Subroutine nesting too deep) The maximum subroutine nesting level of eight is exceeded. (User Action) Make sure that the maximum nesting level is not exceeded. (?IND--F--Symbol table overflow ()) The IND symbol table is full; there is no space for the symbol represented by (). (User Action) Use the .ERASE directive to delete symbol definitions from the symbol table. (?IND--F--Symbol type error ()) The symbol () was not used in the context for its type; for example, a numeric expression referenced a logical symbol. (User Action) Compare only symbols of the same type. (?IND--F--Swap error) IND encountered an error while writing to itself.
This message sometimes includes a secondary error message. For a listing of the secondary message and its explanation, see the (IND Secondary Input/Output Error Messages) at the end of the IND message listings. (User Action) Make sure that the system device is not write-locked. (?IND--F--Syntax error) IND encountered an unrecognizable element. Common examples of syntax errors are misspelled commands, unmatched parentheses, embedded or missing spaces, and other typographical errors. (User Action) Check for typing errors and enter the command again. (?IND--W--Timeout support not available) IND tried to process a .ENABLE timeout directive on a system that does not have a clock, or while a monitor without timeout support was running.
This message sometimes includes a secondary error message. For a listing of the secondary message and its explanation, see the (IND Secondary Input/Output Error Messages) at the end of the IND message listings. (User Action) Remove the .ENABLE timeout directive from the program, use a monitor that has timeout support, or run the program on a system that has a clock. (?IND--F--Undefined label (<.label>)) IND did not find the label, represented by (<.label>), specified in a .GOTO, .GOSUB, or .ONERR directive. (User Action) Check for a typing error. Check the program logic and insert the label, represented by (<.label>), where appropriate. (?IND--F--Undefined symbol ()) A symbol in the command line is not defined. (User Action) Make sure that all symbols being used or substituted are defined. (?IND--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (IND) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions.
(IND Secondary Input/Output Error Messages) (Bad file name) The file specification in the command line is invalid. (User Action) Make sure that the format of the file specifications is correct. (Bad record type---not ASCII data) The file specified as input to IND does not contain valid ASCII characters. (User Action) Make sure that there are no typing errors in the specified file. (Data overrun) More than 80 characters were entered at the terminal, or an attempt was made to read a record that contains more than the maximum of 80 characters. (User Action) Make sure that input entered at the terminal does not exceed 80 characters. (Device full) Not enough room is available in the directory of the output device to create the specified output file. This error generally occurs when IND attempts to execute a .OPEN or a .CLOSE directive. (User Action) Make sure that the output device has enough room for all the files to be stored there. See (ism_sec) for information on how to increase storage space. (Device read error) IND encountered a bad block or another type of hard error when trying to access a file. (User Action) Make sure that each device accessed is mounted. See the procedures for recovery from hard error conditions listed in (hec_sec). (Device write error) IND encountered a bad block or another type of hard error when trying to send output to a file. (User Action) Make sure that the device to which data is being sent is mounted and is write enabled. See the procedures for recovery from hard error conditions listed in (hec_sec). (End of file) Notifies you that end of file has been reached. (User Action)This message is informational. (File accessed for read) An attempt was made to write to a currently open file with the .OPENR directive. (User Action) Close or purge the file, then open it for output. (File accessed for write) An attempt was made to read a currently open file with the .OPEN or .OPENA directives. (User Action) Close or purge the file, then open it for input. (File already open) An attempt was made to open a file with a file number already in use. (User Action) Use an available file number or close a file that is already open. (File exceeds space allocated) The volume receiving data is full. (User Action) Use the SQUEEZE command or the DUP /S option to compress the volume. See (ism_sec) for information on how to increase storage space. (File protection error) An attempt was made to delete a protected file or to create a file with the same name as a protected file that already exists. (User Action) Use the keyboard UNPROTECT command to disable a file's protected status or use a different name for the new file. (Invalid device or unit) The device or unit specified with the .OPEN, .OPENA, or .OPENR directives is invalid. (User Action) Check for syntax errors in the device specification. (No file accessed on channel) An internal error occurred in IND. (User Action) Try the operation again. If the error persists, send an SPR to Digital; include with the SPR an output listing or log file and a machine-readable copy of the control file(s). (No room to FETCH handler) Requires more room to accomplish FETCH. (User Action)This message is informational. (No such file) The file specified in the OPEN or DELETE command was not found. (User Action) Make sure that the file specification has the correct syntax and spelling. (Undefined error code) IND has detected an error it cannot classify. (User Action) Submit an SPR to Digital; include with the SPR an output listing or log file and a machine-readable copy of the control file(s). (?KMON--F--Address) An address is out of range in an E or a D command. (User Action) The allowable range is between 0 and the base of RMON (contents of location 54 octal); the locations in the E or the D commands cannot exceed this range. If device handlers are loaded, the high limit is the beginning address of these loaded handlers. Check for a typing error in a prior B command. (?KMON--F--Ambiguous command) The command abbreviation entered is not unique---for example, CO could stand for COPY or COMPILE. (User Action) Use enough characters in a command abbreviation to make that command unique. Four characters are usually enough. See the (sug_book) for the minimum abbreviations. (?KMON--F--Ambiguous option) The option abbreviation entered is not unique. (User Action) Use enough characters in an option abbreviation to make that option unique. Four characters are usually sufficient; six characters are sufficient in an option prefixed by NO. (?KMON--F--Attempt to access unmapped memory) With the EXAMINE command, you were attempted to access a non-existent location. (User Action) Reenter correct location. (?KMON--F--Bad fetch ()) An error occurred while KMON was reading a device handler from SY. This error can occur during the execution of a keyboard LOAD, RUN, SRUN, or FRUN command or from using indirect files that do not reside on the system device. The keyboard monitor loads device handlers for these commands. This error can also occur if the system diskette was exchanged without rebooting. (User Action) Make sure that the device handlers referenced are installed and are not in an area that contains bad blocks. If you exchange the system diskette, reboot the system. (?KMON--F--Command file nesting too deep) A reference was made to a fourth level of nested indirect command files. (User Action) Limit indirect command file nesting to three levels. (?KMON--F--Command string too complicated) The command is too complicated to parse, probably because too many options are in the command line. (User Action) Simplify the command and reenter it. (?KMON--F--Conflicting options) Incompatible options were specified in the command line. (User Action) See the (sug_book) for valid option combinations. (?KMON--F--Conflicting SYSGEN options ) The SYSGEN options of the device handler disagree with those of RMON. (User Action) Select a compatible RMON/handler combination or perform a new SYSGEN to create a monitor and set of handlers that are compatible. (?KMON--F--Console must be local) A SET TT CONSOL=n command specified a logical unit of a terminal that is supported as a remote terminal. (User Action) Specify a local terminal as the console terminal and issue the command again. (?KMON--F--Device full (<)dev:filnam.typ(>)) Not enough room is available in the directory of the output device to create the specified output file. (User Action) Make room on the device by removing files or use another device for this operation. See (ism_sec) for information on how to increase memory on off-line storage resources. (?KMON--F--Device loaded or not removable ()) (numbered) A REMOVE command specified an invalid device handler---for example, the BA or system device handler. A REMOVE command specified a handler that is loaded. (User Action) (numbered) Make sure the device handler specified in the REMOVE command can be removed. Use the SHOW command to determine which handlers are resident; unload resident handlers before removing them. (?KMON--F--Device not installed ()) An attempt was made to remove a device that is not installed in the system table. (User Action) Verify that the device name was typed correctly. Use the SHOW command to determine which handlers are installed. (?KMON--F--Error in file spec) An error exists in the format of a file specification; for example, the file name is longer than six characters. Or a file specification does not appear in the command line where one is expected. (User Action) Verify that the dev:filnam.typ format is used and enter the command again. (?KMON--F--Extended memory monitor required for ()) (numbered) A program was running under an unmapped monitor, but extended memory overlays were requested. The virtual bit of the job status word is set. (User Action) Make sure that the system includes memory-management hardware and that the program is run under a mapped monitor. (?KMON--F--File not found ()) (numbered) The file specified in an EXECUTE R, RUN, FRUN, SRUN, GET, SET, INSTALL, or indirect file command was not found. The file needed to process the command was not found on the indicated devices. (User Action) Check for a typing error in the command line. Verify that the file name is in the correct format and that it contains no invalid characters. Verify that the named file resides on the named device and that all files necessary to process the command, such as utility programs and handler files, also reside on the named device. Type the command line again. This message can occur during system bootstrap if the startup indirect command file (STRTSB, STRTFB, STRTXM, STRTXB, STRTZM or STRTZB.COM) is not found. The startup file may have been accidentally deleted or renamed. This message does not mean the system has not been bootstrapped properly. So this message will not display whenever the system is bootstrapped, replace the startup file for the monitor in use or create a new startup file and give it the proper name for the monitor being used (STRTSB.COM for SB, STRTFB.COM for FB, STRTXM.COM for XM, STRTXB.COM for XB, STRTZM.COM for ZM, and STRTZB.COM for ZB. (?KMON--F--Foreground active) An attempt was made to execute an FRUN or an UNLOAD F command when an active foreground job already existed. (User Action) Wait for the foreground job to finish, unload it, and then start a new foreground job. (?KMON--F--Fully mapped monitor required for ()) The program is either in I-D space file format or specifies that it requires either Supervisor mode support or I-D space support. Supervisor mode support is required whenever bit value 4 (REQSM$) is set and I-D space support is required whenever bit value 1 (REQID$) is set in location 4 (JSX$) in block 0 of the save image. (User Action) Make sure that the system includes I-D space memory- management hardware and that () is run under a fully mapped monitor. (?KMON--F--Handler must be loaded ()) You issued the EXECUTE command but the device was not resident. (User Action) Load the device handler needed for your operation. (?KMON--F--Input error ()) (numbered) An input error occurred while the file specified in an R, RUN, GET, FRUN, or SRUN command was being read. An error occurred while block 0 of the handler file was being read during the INSTALL command. An error occurred during the execution of a SET command for a handler. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?KMON--F--Insufficient memory) (numbered) The GET, R, or RUN command was used on a file that is big enough to overlay the monitor if loaded into memory. An indirect file is too large to be executed. The USR would have moved down into the area of memory mapped by the KT11 PAR1 mapping register. Not enough memory was detected by I/O to or from the system scratch area during command processing---for example, on a SAVE operation. (page_break) (User Action) (numbered) See (ism_sec) for information on how to increase storage space. Insert a CTRL/C in the middle of the indirect file to break it into two sections. Reduce the size of the foreground program. Use the UNLOAD command to remove some resident device handlers, if there are too many. If you are using the a mapped monitor, try running your program using the unsupported utility program VBGEXE, described in the (sum_book). (?KMON--F--Insufficient memory for region) Not enough memory is available to create the virtual overlay region when running the program in extended memory. (User Action) See (ism_sec) for information on how to increase memory resources. (?KMON--F--Invalid command) (numbered) The KMON command used is invalid; for example, you used digits rather than characters in a command that contains only alphabetic characters. An indirect file is not the last item, excluding comments, on a keyboard monitor command line---for example: COMPILE FILE @A. The command file name contains invalid characters---for example, @A*B. The command used is not available through the DCL commands, and no .SAV file type of the command name used exists. (User Action) (numbered) Check for a typing error in the command line. Try the operation again. Make sure that the indirect file is the last item on a keyboard monitor command line. Make sure that the command file name contains only valid characters. See the system manager about whether the DCL command was removed from the system during system generation. Make sure that a .SAV file type of the command being used exists on the system volume. (?KMON--F--Invalid command file nesting) Same explanation as for preceding message, except that it refers to indirect command files. (User Action)Same as for preceding message. (?KMON--F--Invalid continuation) An attempt was made to continue a line from a nonnested indirect file to the console terminal. (User Action) When continuing a line from an indirect command file, make sure that the indirect file is nested. (?KMON--F--Invalid control file nesting) You are running an ind control file that calls an indirect command file, which in turn calls another ind control file. (User Action) You cannot include, in ind control files, an indirect command file that calls another ind control file. (?KMON--F--Invalid date) The DATE command argument is invalid. (User Action) Check for a typing error in the command line. Enter the date, using the correct format---DATE dd--mmm--yy. (?KMON--F--Invalid device ()) (numbered) The device specified is invalid, the operation is invalid for the specified device, or a device handler for use with a foreground job (dev=F) was loaded when a single-job monitor was running. An attempt was made to install BA. Under the FB and XM, or ZM monitors, an attempt was made to unload a device the foreground owns while a foreground job was active. In this case, () is the job name. The command LOAD BA (in any monitor) was used when the appropriate file (BA.SYS or BAX.SYS) was not present on the system device. In this situation, BA still appears in a SHOW listing, because RT--11 reserves device slots for them. (User Action) (numbered) Check for a typing error in the command line. Verify that the device indicated is valid. Note that devices for R, RUN, GET, SAV, SRUN, and FRUN must be random-access devices. The dev=F (and dev=B) construction is valid only under the FB monitor. Enter the command again. Copy the BA handler file to the system volume, then reboot the system so that BA can be installed. Unload the device after the foreground job has finished. Copy the BA handler file to the system volume and reboot the system. (?KMON--F--Invalid device for command file) An indirect file was invoked from a non-block-replaceable device (MT). (User Action) Copy the indirect file to a block-replaceable device, such as RK: or DX:, and enter the command line again. (?KMON--F--Invalid device installation ()) You have an installation error with the specified device. Three possible causes of this error are: (numbered) There is a bad block on the volume you want to install. The CSR specified in the handler is not valid in the current configuration, or the device setup failed. You installed VM but you SET the BASE beyond the end of available memory. (User Action) (numbered) To find out if you have a bad block, scan the specified volume for bad blocks. Then take the appropriate action. Verify that the device specified by the CSR is installed. To install VM, SET the BASE within the available memory. (?KMON--F--Invalid file format ()) (numbered) In XM, ZM or FB, a .REL file produced by a version of RT--11 previous to Version 3 was specified in the foreground. In XM or ZM, the .SAV image specified for the foreground is not a virtual job. In FB, the file is not a .REL file. (User Action) (numbered) Because the .REL format of RT--11 Version 3 and later versions differs from the .REL format of Version 2C and earlier versions, foreground jobs must be relinked to run under Version 3 and later monitors. Use the LINK/FOREGROUND command or the LINK /R option to relink the file and reenter the command. Verify that the .SAV image specified for the foreground is a virtual job in XM or ZM. Also, check the file to make sure that the virtual bit is set. Verify that the file is a .REL file when running in FB. (?KMON--F--Invalid logical job name) An attempt was made to execute an SRUN or an FRUN command with a job name already associated with an active job or with an invalid job name. (User Action) Make sure that the job name contains from one to six characters and that neither F nor B is used for a logical job name. Verify that the line contains no errors. Use the SHOW JOBS command or the RESORC /J option to obtain a list of current job names. Reenter the SRUN or the FRUN command with a name not already associated with an active job. (?KMON--F--Invalid NO on option) A NO prefix was specified with an option that does not allow it---for example, COPY/NOBOOT. (User Action) Check the (sug_book) for a list of options that are valid when prefixed by NO. Omit the option. This may produce the desired effect by default. Check and enter the command line again. (?KMON--F--Invalid option) An invalid option was used in the command line. (User Action) Check for a typing error in the command line. Use only those options for DCL commands listed in the (sug_book). (?KMON--F--Invalid option for program) The option used belongs to another program---not the one implied by the command line. (User Action) Examine the command line, select an appropriate option, and try the operation again. (?KMON--F--Invalid priority level) The priority level specified by the SRUN/LEVEL option is an invalid priority level, or the same value as another active job. (User Action) Use a value from one to six to specify the priority level. Use the SHOW JOBS command or the RESORC /J option to list the current job levels. (?KMON--F--Invalid set parameter) (numbered) An invalid parameter was used in the SET command. The parameter specified in the command line does not exist. A NO or a value was used on a parameter not requiring one. (User Action) Check for a typing error in the command line. Make sure that valid arguments are used for the parameters. (?KMON--F--Invalid terminal) The terminal number specified in the SET TT CONSOLE=n command or FRUN or SRUN/TERMINAL option is not a valid unit number.
A unit number may be invalid for the following reasons: (unnumbered) The unit number specified is larger than the maximum number of units supported on the system as configured. The unit number is assigned to a terminal that does not exist on the hardware configuration. The terminal specified is being used by another job. The terminal specified is the system console terminal. (User Action) Check for a typing error in the command line. Use the SHOW command to list the currently installed devices. Correct the unit number. (?KMON--F--Invalid time) The TIME command argument is invalid. (User Action) Check for a typing error in the command line. Reenter the TIME command in the correct format---TIME hh:mm:ss. (?KMON--F--Invalid value specified with option) (numbered) An option was modified by an invalid value. You omitted an argument from an option that required one. (User Action) (numbered) Correct the value and issue the command again. Include all required option arguments and issue the command again. (?KMON--F--Job active---cannot unload ()) An attempt was made to execute an UNLOAD command for the existing active job (). (User Action) Wait for the job to finish or abort it before unloading and starting a new job. Use the SHOW JOBS command or the RESORC /J option to obtain a listing of current jobs. (?KMON--F--Line too long) A command line or a line in an indirect file is too long. This condition usually results from too many continuation lines. (User Action) Divide the command line into more than one command and retype the operation. Make sure that each command line or indirect file line contains 200 (decimal) or fewer bytes. (?KMON--F--No file) No file was named where one was expected---for example, RUN followed by RETURN. (User Action) Check for a typing error in the command line; check the format of the monitor command and try the operation again, inserting the proper file name. (?KMON--F--Fully mapped monitor required for ()) Use the ZM or ZB monitor to run job () (User Action) Select appropriate monitor. (?KMON--F--No foreground job) A SUSPEND, RESUME, or UNLOAD F command was given, but no foreground job was in memory. (User Action) Check for a typing error in the command line. Enter a command that does not require a foreground job. (?KMON--F--No room) An attempt to install a new device revealed no free device slots in the monitor table, or an attempt to assign a user logical name revealed no free slots in the monitor user name table. (User Action) Remove a device from the system and install the new device or deassign a user logical name before assigning the new logical name. Use the SHOW command to display the status of the devices on the system. (?KMON--F--No such job---()) An attempt was made to execute an UNLOAD, SUSPEND, or RESUME command for the job (), which does not exist. (User Action) Check for a typing error in the job name. Use the SHOW JOBS command to list the current jobs with their status. (?KMON--F--No such job or device---()) An attempt was made to unload a job () or device () that does not exist. This message appears only on systems with system job support. (User Action) Verify that you typed the job name or device name correctly. Use the SHOW JOBS or SHOW DEVICES command to obtain a list of current jobs or devices for your system. (?KMON--F--Output error ()) An output error occurred while a .REL file was being written during FRUN or SRUN command processing, or while a SAVE command was executing. (User Action) Verify that the system device is write enabled. See the procedures for recovery from hard error conditions listed in (hec_sec). (?KMON--F--Parameters) Bad parameters were typed to the SAVE command. (User Action) Check for a typing error in the command line. Check the format of the SAVE command and enter it again. (?KMON--F--Protected file already exists ()) A protected file with the same name as the file name specified with a SAVE command already exists. (User Action) Use a different name to create a new file. (?KMON--F--Region does not exist ()) An attempt was made to eliminate a global region that does not exist. (User Action) Check for a typing error in the command line. Use the SHOW MEMORY command to determine which global regions exist. (?KMON--F--Region is permanent or active ()) An attempt was made to eliminate a global region while another job was attached to that region. (User Action) A global region can be eliminated only when no other jobs are attached to it. (?KMON--F--Six system tasks already running---cannot SRUN job) An attempt was made to execute an SRUN command when the maximum number of jobs---six---was already running. (User Action) Wait for a job to finish before running the new job with SRUN. (?KMON--F--SY: Write-locked ()) A SET command failed because the system volume is write protected. (User Action) Make sure the system device and volume are write enabled and reissue the SET command. (?KMON--F--Too many files) Too many files were specified for I/O in the command line. (User Action) See the (sug_book) for restrictions on file specifications. (?KMON--F--Unable to unload handler) The handler service routine called by the UNLOAD command returned an error. (User Action) See the handler source code or the handler documentation. (?KMON--U--Command file I/O error) An I/O error occurred while an indirect file was being read. This is probably a hardware malfunction. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?KMON--U--Overlay read error) A hardware error occurred while a KMON overlay, used to process the current command, was being read. This indicates that a bad block is in the system file in question, or that the system volume has been removed. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). Try bootstrapping a different monitor file with the BOOT command. Replace the system volume. (?KMON--U--System input error) A hard input error condition occurred on the system device while the system swap area was being read, or while the scroller code was being read from the monitor file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?KMON--U--System output error) A hard output error condition occurred on the system device while the system swap area was being written. (User Action) Verify that the system device is write enabled. See the procedures for recovery from hard error conditions listed in (hec_sec). (?KMON--U--System output error ()) A hard error condition occurred as a result of a SET command while the indicated system file was being output. (User Action) Verify that the system device is write enabled. See the procedures for recovery from hard error conditions listed in (hec_sec). (?KMON--W--Already installed/assigned ()) The device specified already exists in the system tables. (User Action) Remove the device or deassign the device name. Then install the new handler. (?KMON--W--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?KMON--W--Logical name not found ()) The logical device name in the DEASSIGN command is unknown to the system. (User Action) Check for a typing error in the command line. Use the SHOW command to list the physical and logical device names currently known to the system. (?KMON--W--No clock) No KW11 clock is available for the TIME command. (User Action) The TIME command cannot be used on the system. (?KMON--W--No date) The date was requested but it had not yet been set. (User Action) Enter the date, using the format DATE dd-mmm-yy. (?KMON--W--No ownership assigned; monitor does not support ownership) You attempted to assign a device to an owner in a monitor that does not support ownership. (User Action) Select appropriate monitor that supports ownership. (?LD--F--/A requires exactly 1 /L) An attempt was made to specify and mount more than one logical disk with a logical name assignment. LD exits and does not prompt for a new command. (User Action) Specify only one /L option with each /A option. Try the command again. (?LD--F--/C not specified alone) The /C option was specified with another option in the command line. This option cannot be specified with any other option. (User Action) Make sure that the /C option is not specified with any other options. Enter the command again. (?LD--F--/E not specified alone) The /E option was specified with another option in the command line. This option cannot be specified with any other option. (User Action) Make sure that the /E option is not specified with any other options. Enter the command again. (?LD--F--Device not installed ()) You attempted to access a logical disk mounted on a device that is not installed. (User Action) Install the device on which the logical disk is mounted and reenter the command. (?LD--F--Fetch error) (numbered) A serious LD or system internal error occurred. The copy of LD, the monitor file, or the specified device handler may be corrupted on disk. The in-memory copy of LD or the monitor may be corrupted. (User Action) Reboot the system and retry the operation. If the error occurs again, get a new copy of LD and the specified device handler. Try the operation again. If the error persists, submit an SPR to Digital. (?LD--F--File not found ()) The input file specified was not found. (User Action) Check for a typing error in the command line. Make sure that the specified file resides on the specified device. Enter the command again. (?LD--F--Insufficient memory) Not enough memory is available to complete the requested operation. (User Action) See (ism_sec) for information on how to increase memory space. (?LD--F--Invalid command) The command line typed is not valid. (User Action) Check for a typing error in the command line and make sure that the command is in the correct format. Enter the command again. (?LD--F--Invalid device ()) The device specified in the command line is invalid. Only RT--11 directory-structured devices can be specified in LD commands. (User Action) Check for a typing error in the command line. Verify that the device indicated is a valid RT--11 directory-structured device. (?LD--F--Invalid nesting) You attempted to nest a logical disk within the same logical disk, which is an invalid operation. For example: the command MOUNT LD3: LD3:FOO.DSK is invalid. (User Action) Mount a logical disk on a disk different from itself. (?LD--F--Lookup for LD failed) An internal logic error occurred, or LD.SYS (LDX.SYS) under XM monitor is not on the system volume. (User Action) Verify that LD.SYS (or LDX.SYS) is on the system volume. If it is not, copy LD.SYS or LDX.SYS from the distribution volume to your working system volume. If the error occurs and LD.SYS is on your system volume, submit an SPR to Digital. (?LD--F--No file specified) The command line specified a device without a file name. (User Action) Make sure that a file name is specified in the command line and try the operation again. (?LD--F--Only 1 option per SET allowed) More than one option was specified in the same SET LDn command. (User Action) Reenter the command, using one option for each SET LDn command. (?LD--F--Option value out of range (0--7) /val) A value outside the range 0 to 7 was specified for an option operation. (User Action) Check for a typing error. Retype the command, using an option value in the range 0 to 7. (?LD--F--Option without required value /L) A unit number (n) was not specified in a SET LDn command. (User Action) Specify a unit number (n) for the logical disk when executing a SET LDn command. Try the operation again. (?LD--F--.SpFun to LD failed) An internal logic error occurred. (User Action) Submit an SPR to Digital. (?LD--F--Too many /W and/or /R options) Too many /W and/or /R options were specified on the same command line. (User Action) Reenter the command line with fewer /W and/or /R options. Also, submit an SPR to Digital; include with the SPR an example of a command that produces the error. (?LD--F--Unable to update LD handler) An attempt was made to issue a MOUNT or a SET LD command when the system device was write locked and there was no copy of LD in memory. (User Action) Remove write-lock protection from the system device and reissue the command. (?LD--F--Unknown option (/C, /L, /R, or /W only) /x) An option (/x) other than /C, /L, /R, or /W was specified. (User Action) Enter the command again, using a valid option. (?LD--W--Invalid nesting) Nesting a logical disk within a higher-numbered logical disk (for example: MOUNT LD2: LD3:FOO.DSK) is not recommended. (User Action) If you nest a logical disk, mount it on a lower-numbered logical disk. (?LD--W--Unable to protect file ()) An attempt was made to protect a file, and the operation failed because the output device is write locked. (User Action) Make sure that the output device is write enabled and try the operation again. (?LD--W--Unable to update disk copy of LD handler) (numbered) The system was booted from a write-locked system device. The system will boot, but SY:LD.SYS will not be updated. You issued a MOUNT or a SET LD command with LD loaded and the system device write locked. The in-memory copy of LD will be updated, but LD.SYS (or LDX.SYS) will be unchanged. Whatever SET LD or MOUNT commands you issue will be in effect as long as the system is running, but they will revert to their old settings as soon as you reboot. (User Action) Remove write-lock protection from the system device and reboot or remove write-lock protection and reissue the SET LD or MOUNT command. (?LD--W--/W and /R specified for same unit, /W ignored) /W:n and /R:n were specified in the command line with the same unit n. (User Action) Reenter the command line specifying different units with the /W and the /R options. (?LD--W--/W and/or /R specified for unmounted unit ignored) /W:n and/or /R:n was specified for a unit n that is not already mounted and is not mounted by the current command line. (User Action) Reenter the command line, specifying a unit number of a mounted unit with the /W or /R options. (?LIBR--F--EOF during extract) The end of the input file was reached before the end of the module being extracted was reached. (User Action) The object module format is probably incorrect. Rebuild the library file. If the error persists, reassemble the object module(s) belonging to that file. (?LIBR--F--File not found ()) One of the input files specified in the command line was not found. The CSI program prints an asterisk. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?LIBR--F--Input error in ()) An unrecoverable error occurred during the processing of an input file. The CSI prints an asterisk and waits for another command to be entered. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LIBR--F--Insufficient memory) Available memory is used up. The current command is aborted. (User Action) See (ism_sec) for information on how to increase memory space. (?LIBR--F--Internal error) An internal error occurred while the librarian was recovering from a previous system or user error. (User Action) Retry the operations that produced this error; if the error persists, submit an SPR to Digital; include a program listing and a machine-readable source program, if possible. (?LIBR--F--Invalid device ()) The device specified is not available. (User Action) Verify that the device is valid for the system in use. (?LIBR--F--Invalid GSD in ()) The global symbol directory (GSD) contains an error. The file specified is probably not a valid object module. (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Reassemble or recompile the source to get a good object module and try the operation again. (?LIBR--F--Invalid input file ()) A file other than a form library file or a form descriptor file was given as input when a form (/F) library was being created. (User Action) Make sure that the input file name is entered correctly and that the file is a valid one. (?LIBR--F--Invalid library for listing or extract) The input file specified either for extraction or to produce a directory listing is not a valid object library file. (User Action) Verify the file name in the command line and check for a typing error. It may be necessary to rebuild the input file. (?LIBR--F--Invalid option: /x) The librarian did not recognize the given option---/x represents the unrecognized option. The librarian restarts and prompts with an asterisk. (User Action) Check for a typing error in the command line. Verify that the option is valid for the librarian and try the operation again. (?LIBR--F--Invalid option combination) The options specified request conflicting functions to be performed. For example, if /E or /EXTRACT is specified, no other option may be used. If /M or /MACRO is specified, only continuation options -- /C, //, or /PROMPT may follow. (User Action) Correct the logic of the command line, if necessary. Check for a typing error and retry the operation. (?LIBR--F--Invalid record type in ()) A formatted binary record had a type not in the range 1 to 10 (octal). (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Reassemble or recompile the source to obtain a good object module and retry the operation. (?LIBR--F--Macro name table full, use /M:n) The number of macros to be placed in the macro name table is greater than the number allowed. (User Action) Increase the size of the macro name table by supplying a value (n) to the option /M:n. The default is 128 names. (?LIBR--F--No value allowed: /x) The specified option (/x) does not take a value. The librarian restarts and prompts with an asterisk. (User Action) Check for typing errors; verify that the correct option has been specified in the command line and try the operation again. (?LIBR--F--Output and Input filenames the same) The same file name was specified for both input and output files in the command string to build the macro library. (User Action) Use different file names for the input and output files specified to build a macro library. The input and output file type is .MAC. (?LIBR--F--Output device full ()) The device is full; LIBR was unable to create or to update the indicated library file. (User Action) See (ism_sec) for information on how to increase storage space. (?LIBR--F--Output error ()) The LIBR program detected an unrecoverable error while processing an output file. This may indicate that not enough space is left on a device to create a file, although enough directory entries may be left. (User Action) See (ism_sec) for information on how to increase storage space. (?LIBR--F--Output file full) The output file is not large enough to hold the library file or the list file. (User Action) Increase the output file size with the /ALLOCATE command or the output-filespec[:n] construction; otherwise, increase the free space on the output device. (?LIBR--F--Protected file already exists ()) An attempt was made to open an output file, using ENTER with a name already assigned to a protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to open a new file. (?LIBR--F--/R or /U given on library file ()) A /R or /REPLACE or a /U or /UPDATE option incorrectly followed the specified library file in the command string. (User Action) Use the /R or /REPLACE options or /U or /UPDATE options only after input file names containing modules for replacement or updating. Correct and reenter the command string. (?LIBR--F--Too many .ENDM or .ENDR statements) The input .MAC file to the LIBR/MAC command is missing one or more .MACRO-type statements, resulting in the macro library not being built. (User Action) Add the missing .MACRO-type statement in the input .MAC file or edit the file appropriately. (?LIBR--F--Too many .MACRO, .IRP, .IRPC, or .REPT statements) The input .MAC file to the LIBR/MAC command is missing one or more .ENDM-type statements, resulting in the macro library not being built. (User Action) Add the missing .ENDM-type statement in the input .MAC file or edit the file appropriately. (?LIBR--F--/U given on library file ()) The /U option or the LIBRARY/UPDATE command has incorrectly modified a forms library file. (User Action) Use the LIBRARY/UPDATE command or the /U option only after input file names containing modules for replacement or updating. (?LIBR--W--Duplicate form name of () ) Two forms having the same name were specified as input, and the /U option or the LIBRARY/UPDATE command was not given on the second form. The first form encountered was put in the output file; all duplicates are ignored. (User Action) Use the LIBRARY/UPDATE command or the /U option to update a form of the same name as a previously specified file. (?LIBR--W--Duplicate macro name of () ) Two macros of the same name were specified as input. The first macro encountered is put in the output file; all duplicates are ignored. (User Action) Make all macro names unique. (?LIBR--W--Duplicate module name of () ) A new module inserted in a library has the same name as a module that is already in the library. The librarian does not reenter the name in the directory. The old module is not updated or replaced. (User Action) For the librarian program, insertion is the default operation and no command option is needed; the option for update is /U, and the option for replacement is /R.
For the keyboard LIBRARY command, /INSERT puts the duplicate name in the module; /UPDATE and /REPLACE are not possible operations in this case. (?LIBR--W--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?LIBR--W--Invalid character ) The symbol name entered contains an invalid character. (User Action) Retype the command line, using Radix-50 characters only and try the operation again. (?LIBR--W--Invalid delete of () ) An attempt was made to delete a module or a nonexistent entry point from the library's directory; () represents the module or entry point name. The entry point name or module name is ignored, and processing continues. (User Action) Check for a typing error in the command line. (?LIBR--W--Invalid extract of ()) An extraction of the identified global symbol was attempted, but the symbol was not found in the library. (User Action) Check the command string and the contents of the library file for the correct library file and global symbol specifications. (?LIBR--W--Invalid insert of () ) An attempt was made to insert into a library a module that contains the same entry point as an existing module. () represents the entry point name. The entry point is ignored, but the module is still inserted into the library. (User Action) No user action is necessary. (?LIBR--W--Invalid replacement of () ) An attempt was made to replace in the library file a nonexistent module. () represents the module name. The module is ignored, and the library is built without it. (User Action) Review the module names in the library file. Make sure that the correct module was specified. (?LIBR--W--Null library) An attempt was made to build a library file containing no directory entries. (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Verify that the input to the library has at least one directory entry. (?LIBR--W--Only continuation allowed) A command string was entered beyond the end of the current line without the use of a continuation character. (User Action) Enter a /C option or // (/PROMPT) at the end of the current line. (?LINK--F--Address space exceeded) The high limit of all program sections exceeded 32K words when all sections were concatenated. (User Action) Reduce the size of the program by using overlays, by reducing the size of the root segment, and/or by reducing the size of the largest segment within each overlay region. See (ism_sec) for information on how to increase memory resources. (?LINK--F--ASECT too big) An absolute section overlaps an occupied area of memory or an overlay region. (User Action) Locate a segment of available memory large enough to contain the absolute section and substitute the appropriate starting address. (?LINK--F--/B no value) No argument was specified with the /B or the /BOTTOM option. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument to the /B or the /BOTTOM option. (?LINK--F--/B odd value) The argument specified with the /B or the /BOTTOM option is not an unsigned even octal number. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /B or the /BOTTOM option. (?LINK--F--Cross reference device full ()) The directory does not have enough room for the file name, or the output device does not have enough room for the cross reference temporary file. (User Action) See (ism_sec) for information on how to increase storage space. (?LINK--F--/E no value) No argument was specified with the /E or the /EXTEND option. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /E or the /EXTEND option. (?LINK--F--/E odd value) The argument specified with the /E or the /EXTEND option is not an unsigned even octal number. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /E or the /EXTEND option. (?LINK--F--/H no value) No argument was specified with the /H or the /TOP option. (User Action) Reenter the command string specifying an unsigned even octal number as the argument with the /H or the /TOP option. (?LINK--F--/H odd value) The argument specified with the /H or the /TOP option is not an unsigned even octal number. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /H or the /TOP option. (?LINK--F--/H value too low) The value specified as the high address for linking is too small to accommodate the code. (User Action) Obtain map output without using the /H or the /TOP option to determine the space required and try the operation again. (?LINK--F--/M symbol not in D-space) Symbolic input to /M (/STACK) option must be a D-space symbol. (?LINK--F--/T symbol not in I-space) Symbolic input to /T (/TRANSFER) option must be an I-space symbol. (?LINK--F--Input error in ()) A hardware error occurred while the indicated input file was being read. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--F--Insufficient memory) Not enough memory is available to accommodate the command, the symbol table, or the resultant load module. (User Action) See (ism_sec) for information on how to increase memory space. (?LINK--F--Internal error) An internal error occurred while the linker was recovering from a previous system or user error. (User Action) Retry the operations that produced this error; if it occurs again, submit an SPR to Digital; include a program listing and a machine-readable source program, if possible. (?LINK--F--Invalid character) The character specified was not used in the proper context. (User Action) Examine the command string for errors in syntax, making sure that the characters for symbols are valid Radix-50 characters. Correct and retype the command. (?LINK--F--Invalid complex relocation in ()) During pass 2 of the linker, a complex relocation string in the input file was found to be invalid. (User Action) Check for a typing error in the command line; verify that the correct file names were specified as input. Reassemble or recompile to obtain a good object module and retry the operation. If the error persists, verify that the source code is correct. (?LINK--F--Invalid device ()) The volume indicated is not available. (User Action) Verify that the device is valid for the system in use. (?LINK--F--Invalid GSD in ()) The global symbol directory (GSD) contains an error. The file is probably not a valid object module. (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Reassemble or recompile the source code to obtain a good object module, then try the operation again. (?LINK--F--Invalid record type in ()) A formatted binary record has a type not in the range 1 to 10 (octal). (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Reassemble or recompile the source code to obtain a good object module and try the operation again. (?LINK--F--Invalid RLD in ()) The input file contains an invalid relocation directory (RLD) command. The file is probably not a valid input module. (User Action) Verify that the correct file names were specified as input; check for a typing error in the command line. Reassemble or recompile to obtain a good object module and try the operation again. If the error persists, check the source code to make sure that all modules contributing to a data p-sect are word aligned. (?LINK--F--Invalid RLD symbol in ()) A global symbol named in a relocatable record was not defined in the global symbol definition record, resulting in an error in the language processor. (User Action) Reassemble the indicated file. If the condition persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?LINK--F--/K invalid value) The argument specified with the /K or the /LIMIT option is not in the range 2 to 28 (decimal). (User Action) Reenter the command string, specifying a valid unsigned even octal number as the argument with the /K or the /LIMIT option. (?LINK--F--/K no value) No argument was specified with the /K or the /LIMIT option. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /K or the /LIMIT option. (?LINK--F--Library EPT too big, increase buffer with /G) The /G option was not specified and a /X library with too large an Entry Point Table was encountered. (User Action) Relink and issue the /G option on the first input line. (?LINK--F--Library list overflow, increase size with /P) The maximum number of library routines for the linker was exceeded. (User Action) Relink the program that uses the library routines. The /P:n option default is 170 (decimal). Increase the size of the list by specifying a size greater than the default. (?LINK--F--/M odd value) An odd value was specified for the stack address. (User Action) Check for a typing error in the command line. Reenter the command, specifying an even value with the /M or the /STACK option. (?LINK--F--MAP device full ()) The directory does not have enough room for the file name, or the output device does not have enough room for the map file. (User Action) See (ism_sec) for information on how to increase storage space. (?LINK--F--Old library format in ()) The format of the library file is outdated (previous to Version 3B). (User Action) Rebuild the library file, using the current librarian and the command format LIBRARY/CREATE newlib oldlib for an object library. (?LINK--F--Protected file already exists ()) An attempt was made to open a file with a name already assigned to an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to open a new file. (?LINK--F--/R odd value) The argument specified with the /R or the /FOREGROUND option is not an unsigned even octal number. (User Action) Reenter the command string, specifying an unsigned even octal number as the argument with the /R or the /FOREGROUND option. (?LINK--F--REL write beyond EOF) The relocation information section of an REL file overflowed when an entire load module required relocation. (User Action) Use a square bracket construction or the /ALLOCATE option to enclose a number twice the size of the resulting .SAV file. (?LINK--F--SAV device full ()) The directory does not have room for the file name, or the output device does not have room for the image file (.SAV, .REL). (User Action) See (ism_sec) for information on how to increase storage space. (?LINK--F--SAV read error) A hardware error occurred while LINK was reading the image file (.SAV, .LDA, or .REL). (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--F--SAV write error) A hardware error occurred while LINK was writing the image file (.SAV, .LDA, or .REL). (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--F--Size overflow of section () ) The program section in question increased program size to more than 32K words. (User Action) Reduce the size of the program either in this section or elsewhere in the program. (?LINK--F--STB device full ()) The directory does not have room for the file name, or the output device does not have room for the symbol table (.STB) file. (User Action) See (ism_sec) for information on how to increase storage space. (?LINK--F--STB write error) A hardware error occurred while the symbol table (.STB) file was being written. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--F--Storing text beyond high limit) (numbered) An input object module may have caused the linker to store information in the image file beyond the high limit of the program. If so, the object module has an error condition. If an .LDA file was being produced, the output device did not have enough room for the output file. (User Action) (numbered) Reassemble or recompile the program. Specify a larger output file size or see (ism_sec) for information on how to increase storage space. (?LINK--F--Symbol table overflow) Too many global symbols were used in the program. (User Action) Try to link again, using the /S or the LINK /SLOWLY command. If the error recurs, reduce the size of the library list, using the /S and the /P:n options, with a value less than the default. If the error persists, the link cannot take place in the available memory. See (ism_sec) for information on how to increase memory space. (?LINK--F--/T odd value) An odd value was specified for the transfer address. (User Action) Check for a typing error in the command line. Reenter the command, specifying an even value to the /T or the /TRANSFER option. (?LINK--F--Too many program segments) More than 1777 (octal) program segments were specified. (User Action) Restructure the overlays to reduce the number of segments. (?LINK--F--Too many virtual overlay regions) More than eight extended memory overlay regions (windows), including the root, were in use for extended memory jobs. (User Action) Reorganize the extended memory overlay structure to use eight or fewer memory overlay regions, including the root. (?LINK--F--/U or /Y value not a power of 2) The value specified with the /U, the /ROUND, the /Y, or the /BOUNDARY option is not a power of 2. (User Action) Reenter the command with a value that is a positive power of 2. (?LINK--F--Virtual overlay logical address space exceeded) The virtual overlays in the program required more than 96K words of extended memory. (User Action) Reorganize the overlays to use less extended memory. See the LINK chapter in the (sum_book) for more information about the extended memory overlay option. (?LINK--F--Word relocation error in ()) During concatenation of data p-sects, a word reference was moved to an odd byte. (User Action) Place the .EVEN assembler directive at the end of data p-sects to make sure that all word references in data p-sects will be on a word boundary when relocated by LINK. (?LINK--F--/Y no value) No argument was specified with the /Y or the /BOUNDARY option. (User Action) Reenter the command string, specifying a positive power of 2 as the argument with the /Y or the /BOUNDARY option. (?LINK--F--/Y odd value) An odd value was specified as the argument with the /Y or the /BOUNDARY option. (User Action) Reenter the command string, specifying a value that is a positive power of 2 as the argument with the /Y or the /BOUNDARY option. (?LINK--W--Additive reference of (
) at segment # ()) A call or a branch to an overlay segment was not made directly to an entry point in the segment. (
) represents the entry point; () represents the segment number. (User Action) Make sure that calls or branches to overlay segments are made (page_break)
directly to entry points in the segment. See the (sum_book) for more information about using overlays. (?LINK--W--Boundary section not found) The program section name specified as a boundary section with the /Y or the option /BOUNDARY was not found in the modules that were linked, or the program section does not exist in the root segment. The linker continues after the warning without changing the program section. (User Action) Check the responses to the (Boundary section?) prompt and correct the section name the next time you link. (?LINK--W--Boundary section not in D-space) A PSECT specified to the "Data boundary section?" prompt exists as an I-space PSECT. LINK ignores the data space boundary operation and continues. (?LINK--W--Boundary section not in I-space) A PSECT specified to the "Instruction boundary section?" prompt exists as a D-space PSECT. LINK ignores the instruction space boundary operation and continues. (?LINK--W--Byte relocation error at (
)) The linker tried to relocate and link byte quantities, but failed because the high byte of the relocated value (or the linked value) was not all zeros. (
) represents the address at which the error occurred.
The relocated value is truncated to eight bits, and the linker continues processing for .SAV and .LDA files. For .REL files no truncation is performed, and processing continues. (User Action) Correct the source program so that no byte quantities are relocated. Reassemble and relink. (?LINK--W--Complex relocation divide by 0 in ()) An attempt was made to divide by 0 in a complex relocation string in the specified file. A result of 0 is returned, and linking continues. (User Action) Check the logic in the relocation string of the program. (?LINK--W--Complex relocation of ()) The complex relocation of global symbols was indicated for the linker in the foreground. (User Action) Examine the assembly listing. Edit the program to remove all complex expressions that contain relocatable symbols. The MACRO assembler tags such occurrences with a (C) in the binary contents column of the listing. (?LINK--W--Conflicting section attributes ()) The program section symbol is defined with different attributes. The attributes of the first definition are used, and the linking process continues. (User Action) Check the source program and use the desired section attributes for that program section. (?LINK--W--Cross reference input error) A hardware error occurred while the cross-reference temporary file was being read. The cross-reference portion of the map output is eliminated, and the linking process continues. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--W--Cross reference output error) A hardware error occurred while the cross-reference temporary file was being written. The cross-reference portion of the map output is eliminated, and the linking process continues. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--W--Default system library not found SYSLIB.OBJ) The linker did not find SYSLIB.OBJ on the system device when undefined globals existed or when overlays were being used. (User Action) Get a copy of SYSLIB.OBJ from the backup system volume and relink the program or correct the source files by removing the undefined globals listed on the terminal. The (ins_book) contains instructions for tailoring SYSLIB to meet various needs. The current version of SYSLIB contains the overlay handlers, which are required when overlays are specified. (?LINK--W--Duplicate symbol () is defined in non-library ()) An attempt was made to define a duplicate symbol with the /D option, using nonlibrary modules. The symbol is made nonduplicate, and the definition is allowed to stand. (User Action) Avoid duplicating the module that contains the symbol, represented by (), by not responding to the (Duplicate symbol?) query with that symbol. Alternatively, duplicate the module that contains () by placing the module in an object library and specifying it as a library to LINK. (?LINK--W--Duplicate symbol () is forced to the root) A module containing duplicate global symbols was forced to reside in the root, and the symbol is made nonduplicate. (User Action) Avoid duplicating the module that contains the symbol, represented by (), by not responding to the Duplicate symbol? query with that symbol. Alternatively, eliminate any references to () from the root. (?LINK--W--Extend section not found) The extend section name given with the /E or the LINK/EXTEND command was not found in the modules linked, or the extend section did not exist in the root segment. The linker continues after the warning without extending the section. (User Action) Check the response to the (Extend section?) query and correct the section name before linking again. (?LINK--W--Extend section not in D-space) A PSECT specified to the "Extend data section?" prompt exists as an I-space PSECT. LINK ignores the data space extend operation and continues. (?LINK--W--Extend section not in I-space) A PSECT specified to the "Extend instruction section?" prompt exists as a D-space PSECT. LINK ignores the instruction space extend operation and continues. (?LINK--W--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the RENAME/NOPROTECT command or the PIP /Z option. (?LINK--W--File not found ()) (numbered) The input file specified was not found. The LINK or the EXECUTE command was issued in response to the keyboard monitor prompt, and a file specified in the first line of the command was not found. LINK exits and the keyboard monitor prompt returns. A file specified on a continuation line of the LINK or the EXECUTE command was not found. LINK prompts for another file specification. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?LINK--W--Invalid option: /x) The linker did not recognize the option (/x) specified in the command line, or an invalid combination of options was used. (User Action) If the invalid option occurred in the first command line, control returns to the CSI; enter another command. If the invalid option occurred on a subsequent command line, the option is ignored and processing continues. In a continued command line, make sure that the only options used are /O, /V, /C, and //. Valid linker options are listed in the (sum_book). Examine the command line and check for a typing error. (?LINK--W--Load address odd) An odd load address was specified with the /Q option. (User Action) Reenter the line with an even address. (?LINK--W--Load address too low ()) The load address specified for the p-sect is too low. The p-sect was ignored to avoid overlaying code in a previous section.
LINK continues execution without loading the p-sect at the specified address. (User Action) Relink and specify a higher load address for the p-sect. (?LINK--W--Load section not found ()) The load section specified was not found in the root. LINK continues execution, ignoring the p-sect that was not found. (User Action) Reorder the modules to place the p-sect containing the load section in the root, then relink. (?LINK--W--Map write error) A hardware error occurred while the map output file was being written. The map output is terminated, and the linking process continues. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?LINK--W--Multiple definition of ()) The symbol indicated was defined more than once. Extra definitions are ignored. (User Action) Make sure that each symbol is defined only once. (?LINK--W--No load address) No address was specified with the /Q option. (User Action) Reenter the command line and specify a load address. (?LINK--W--/O or /V option error, re-enter line) An error was made in the use of the /O or the /V option. The four probable causes are: (numbered) A /O option appears after a /V option. No value was given with a /O or /V option. An incorrect value was given. A /O or a /V option was used with the /L option. (User Action) Check the context and reenter the line. (?LINK--W--Round section not found () ) The symbol representing the program section specified with the /U or the /ROUND option was not found in the symbol table. Linking continues with no round-up action. (User Action) Check the source to make sure that the symbol is globally defined. (?LINK--W--Round section not in D-space) A PSECT specified to the "Round data section?" prompt exists as an I-space PSECT. LINK ignores the data space round operation and continues. (?LINK--W--Round section not in I-space) A PSECT specified to the "Round instruction section?" prompt exists as a D-space PSECT. LINK ignores the instruction space round operation and continues. (?LINK--W--/S not allowed with STB or MAP files) The /S (/SLOWLY) option was used when requesting an .STB or .MAP file in the linking operation. The .STB or .MAP file is not produced, but the linking operation continues. (User Action) Do not use the /S (/SLOWLY) option of LINK when creating an .STB or .MAP file. (?LINK--W--Stack address undefined or in overlay) The stack address specified by the /M or the /STACK option was undefined or in an overlay. For .SAV files, the stack address is set to the default, 1000. For .REL files, the default is 0 and will be revised when the file is run in the foreground. (User Action) Check for a typing error in the command line. Verify that the stack address or the global symbol is not defined in an overlay segment. (?LINK--W--Transfer address undefined or in overlay) The transfer address is not defined or is in an overlay. (User Action) Check for a typing error in the command line. Respond to the /T or the LINK/TRANSFER command with a colon followed by an unsigned 6-digit octal number, or with a RETURN followed by the global symbol whose value is the transfer address of the load module. (?LINK--W--Undefined globals:) The globals listed are undefined, because SYSLIB is not present and overlays are used. (User Action) Check for a typing error in the command line. The undefined globals are listed on the terminal and also in the link map when requested. Correct the source program. Verify that all necessary object modules are indicated in the command line or are present in the libraries specified. See the (ins_book) for instructions on tailoring SYSLIB. (MACRO messages) The MACRO--11 error messages have been removed from this manual. See the separate MACRO--11 documentation for explanations of all MACRO--11 error messages. (?MDUP--F--Bad block in system area ()) A bad block was found in a critical area of the disk, making the volume unusable. (User Action) Reformat the volume, if possible. Try the operation again. If the error persists, the volume must be replaced. (?MDUP--F--Channel in use ()) An internal MDUP error occurred. (User Action) Reboot the system and try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?MDUP--F--Conflicting SYSGEN options) The system device handler and the monitor file have different SYSGEN options enabled. This conflict prevents further processing. (User Action) See the (ins_book) for details about the MDUP system program. (?MDUP--F--Directory I/O error ()) An error occurred while MDUP was reading the directory of the specified device. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). Try the operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume. (?MDUP--F--Directory input error ()) An error occurred while the directory of the specified device was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). Try the operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume. (?MDUP--F--Directory output error ()) An error occurred while the directory of the specified device was being written. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). Try the operation again. If the error persists, reformat the volume. If the error still occurs, replace the volume. (?MDUP--F--Error reading bad block replacement table ()) An input error occurred while MDUP was reading the bad-block replacement table in block 1, the home block of the specified volume. (User Action) Check for bad blocks on the volume. If the home block is bad, the volume is unusable and must be replaced. See the procedures for recovery from hard error conditions listed in (hec_sec). (?MDUP--F--File not found ()) The specified file was not found. (User Action) Check for a typing error in the command line. Try the operation again. (?MDUP--F--Input error ()) A hardware error occurred during a read operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?MDUP--F--Insufficient memory) Not enough memory is available to complete the requested operation. (User Action) Make sure that there are at least 12K words of memory for the requested operation. See the section on the MDUP.SAV program contained in the (ins_book). (?MDUP--F--Insufficient memory, bypassing automatic installation) You attempted to perform the automatic installation (AI) procedure on a processor that does not contain enough memory to support AI with this media. (User Action) The automatic installation procedure stopped, and the procedure to manually install your media has begun. The asterisk prompt (*) you see on your terminal screen is from MDUP.MU; that is, MDUP.MU is now loaded in memory. See Chapter 8 of the (ins_book) for complete information on manually installing your media. (?MDUP--F--Invalid command) (numbered) The command entered is invalid. The format of the command line is incorrect. An invalid combination of options was specified. A device may not be valid for the requested operation. (User Action) Check for a typing error in the command line. Check the format of the command line.
See the section on DUP in the (sum_book) or to the (sug_book) for a list of valid option combinations. Make sure that the device specified is valid for the requested operation. (?MDUP--F--Invalid device ()) The specified device is not supported for use with MDUP. (User Action) Check for a typing error in the command line. See the (ins_book) for the list of devices supported by MDUP. (?MDUP--F--Invalid directory ()) The volume in the specified device does not contain a valid RT--11 directory structure. (User Action) Initialize the volume before using it for the first time. Review the discussion about using the MDUP.SAV program in the (ins_book). (?MDUP--F--Invalid option: /x) An invalid option was specified in the command line. (User Action) Check for a typing error in the command line. Use only valid options. See the section on DUP in the (sum_book) or to the (sug_book) for a list of valid options. (?MDUP--F--Invalid value specified with option: /x) A value specified is outside the acceptable range. (User Action) Check for a typing error in the command line. See the section on DUP in the (sum_book) or to the (sug_book) for a list of valid options and the range of valid values for each option. (?MDUP--F--Non-bootable file ()) The specified device handler does not contain a valid primary bootstrap because the bootable magtape or MDUP.Mx was built incorrectly. (User Action) See the (ins_book) for details about the MDUP.SAV program. (?MDUP--F--No room for file ()) The output volume does not have room for the specified file. (User Action) Use the INITIALIZE command or the DUP /Z option to initialize the output device before copying the system to the output device. See the (ins_book) for more information. (?MDUP--F--Output error ()) A hardware error occurred during a write operation. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_SEC). (?MDUP--F--Size function failed) An error occurred while DUP was determining the size of the volume mounted in a device. The monitor, the device handler, or DUP may be corrupted. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). Reboot the system and try the operation again. (?MDUP--F--Trap to 4) An internal MDUP error occurred. (User Action) Reboot the system and try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?MDUP--F--Trap to 10) An internal MDUP error occurred. (User Action) Reboot the system and try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?MDUP--I--Bad blocks detected ().) The specified number of bad blocks was detected during the bad block scan initiated by the INITIALIZE/BADBLOCKS command or the DUP /Z/B option. (User Action) The volume is ready to use. (?MDUP--I--No bad blocks detected ()) No bad blocks were detected during the bad block scan initiated by the INITIALIZE/BADBLOCKS command or the DUP /Z/B option. (User Action) The volume is ready to use. (?MDUP--U--System error) An internal MDUP error occurred. (User Action) Reboot the system and try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?MDUP--W--Too many bad blocks ()) More than 128 bad blocks were encountered during a bad block scan. (User Action) The volume is unusable; reformat or replace. (?MON--F--Bad fetch) An error occurred while a device handler was being read from SY, the address at which the handler was to be loaded was invalid, or the handler to be fetched has SYSGEN options that do not match the SYSGEN options of the monitor. (User Action) Make sure that the address at which the handler is to be loaded is not outside the bounds of the program; also make sure that the handler is not so large that it will overflow the program bounds---in this case, allow more space for the handler. Examine location 60 of the device handler and the monitor fixed offset for SYSGEN features; they should agree. (?MON--F--Dir I/O err (
)) An error occurred during I/O in the directory of a device. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?MON--F--Dir ovflo (
)) No more directory segments are available for expansion; the error occurred during file creation through .ENTER. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) See (ism_sec) for information on how to increase storage space. (?MON--F--Directory unsafe) Along with the error message that appears immediately above it, this message indicates that an I/O error occurred while the USR was updating a device directory. The directory operation may have failed; one or more files may have been lost. The monitor attempts to complete the directory operation before aborting the job. (User Action) Examine the device directory carefully for lost files. See the procedures for recovery from hard error conditions listed in (hec_sec). (?MON--F--FPU trap (
)) A floating-point exception trap occurred, and the user program had no .SFPA exception routine active. The job is aborted. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Examine the data for floating-point overflow or underflow and adjust it accordingly. (?MON--F--Inv addr (
)) An address specified in a monitor call is odd or is not within the job's address space. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Correct the address in error in the source program. (?MON--F--Inv chan (
)) A channel number specified is too large. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Use a valid channel number---the default number is 16 channels---or define a larger channel number (225 maximum), using the .CDFN request. (?MON--F--Inv dir) Directory is incorrect format. (User Action) Reformat directory. (?MON--F--Inv EMT (
)) The function code of an EMT is out of bounds. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Check the EMT instruction to determine the correct code. (?MON--F--Inv SST (
)) This error message is generated only by the XM, ZM, and ZB monitor. (numbered) The program has not supplied a valid trap address for a synchronous system trap. The program has not properly initialized the trap vector before a trap instruction (BPT, IOT, or TRAP), and the monitor has intercepted the instruction. Zero and odd addresses in the vector locations cause this error. The value (
) is the address of the instruction following the instruction or EMT that caused the error. An internal mapping handler has not properly restored a kernel active page register or has issued a device timeout request without a .FORK. (User Action) (numbered) Verify that valid trap addresses are supplied for synchronous system traps. Initialize the trap vector properly for each trap instruction. If the program has no trap instructions, check for a logic error that is causing an inadvertent trap---for example, improper execution of data. See the (sim_book) for more information about synchronous system traps. Correct the handler logic. (?MON--F--Inv USR (
)) This error message is generated by only the FB monitor. A foreground job attempted to load the USR at an address outside the job's limits. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Make sure that jobs that issue programmed requests requiring the USR provide an area for the USR to swap into. This area must be at least 2K words, wholly within the job's upper and lower limits, and pointed to by location 46. (?MON--F--Invalid address (
)) An address specified in a monitor call is odd or is not within the job's address space. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Correct the erroneous address in the source program. (?MON--F--INV DIR ()) This error message is generated by a DIR hard error that is intercepted by the monitor. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?MON--F--MMU fault (
)) This error message is generated only by the XM, ZB, and ZM monitors. The program has a memory management error in the form of a program reference to an address that is outside the currently mapped bounds of the program. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Check the instruction that precedes address (
) and correct it. Run the program again. (?MON--F--No dev (
)) A READ/WRITE or a .LOOKUP operation was attempted, but no handler was in memory for the device. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Verify that no .RELEASE was done before the READ/WRITE operation. Make sure that the program uses the .FETCH command to fetch the handler or load the appropriate handler before running the program. ( ?MON--F--Ovly err (
)) An error occurred when an overlaid user program tried to read an overlay. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) Make sure that the program did not accidentally perform a .CLOSE or a .PURGE on channel 15 (decimal). Verify that the device is not off line and that the proper handler is loaded if the overlay program is running from other than the system device type. (?MON--F--Power fail halt) A power failure occurred. When power returns, the system prints the message---if display of this message was chosen during system generation---and halts. (User Action) Reboot the system. (?MON--F--Swap error) This error message is generated by only the FB and the XM monitors. A hard error occurred while the system was attempting to write a user program to the system swap blocks. This may indicate that the system device is write locked. (User Action) Verify that the system device is write enabled. See the procedures for recovery from hard error conditions listed in (hec_sec). (?MON--F--System halt) This error message is generated by only the FB and the XM monitors. An I/O error occurred while the monitor was reading the KMON or USR into memory. The system volume was dismounted, or the monitor file contained a bad block. The monitor continues to try to read the KMON after issuing this message. (User Action) Verify that the system volume is mounted and ready. Bootstrap a different monitor file on your system volume. If the monitor file is affected, obtain a new monitor file from your system backup device and label the corrupted file FILE.BAD to set aside the bad block. (?MON--F--System read error) A hardware error occurred when KMON/USR was being read back into low memory after a job exit. The monitor will continue to attempt to read in KMON, until the error condition is corrected or the system is halted and rebooted. (User Action) Check to see if the system disk is off line. If so, restore it to on line. Otherwise, the only recovery is to halt and reboot. If the error persists, See the procedures for recovery from hard error conditions listed in (hec_SEC). (?MON--F--Trap to 4 (
)) (?MON--F--Trap to 10 (
)) (numbered) A trap to location 10 occurs if the job referenced invalid memory or device registers or if an invalid instruction was used. A trap to location 4 occurs if stack overflow occurred, a word instruction was executed with an odd address, or a hardware problem caused bus timeout.
The value (
) is the address of the instruction following the instruction or EMT that caused the error. A special trap to location 4 occurs if the program counter (PC) is equal to 1, as in the following error message, indicating that the linker supplied a starting address of 1 for the program:
(?MON--F--Trap to 4 000001)
This can occur if the transfer address was omitted from the .END directive in a MACRO--11 program or if no transfer address was specified with the monitor LINK/TRANSFER command or the linker /T option. (User Action) (numbered) Determine the bounds of the user program from the link map or absolute locations 40, 46, 50, and 54. If the error occurred within the bounds of the user program, correct the programming logic. Verify that the program has not corrupted vital monitor data, such as the stack, the queue elements, or the monitor. Check USR swapping and program overlaying for possible error. Refer to (SF_SEC) for more information. Check for reference to a device that does not exist on the current system---for example, PRINT FILE.FOR on a system that does not have a line printer. Make sure that a transfer address is specified in the .END directive of a MACRO--11 program or with the monitor LINK/TRANSFER command or the linker /T option. If your program is using a subroutine that calls a completion routine, 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). If none of these errors can be identified, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?MON--F--Unloaded driver (
)) Under the FB monitor, the program attempted to use a device handler that is not in memory and could not be fetched. Under the XM, ZB, and ZM monitor, there may not be enough space for the device in the interrupt-forwarding table. The value (
) is the address of the instruction following the instruction or EMT that caused the error. (User Action) RT--11 requires device handlers to be loaded manually for foreground and system jobs under the FB, XM, ZB, and ZM monitors. Use the LOAD command to load the handler(s) before running the program.
Load the handler into an area of memory that is clear of the area mapped by kernel active page registers 1 and 3. Alternatively, perform another system generation and include additional device slots to increase the size of the interrupt forwarding table. (?MONMRG--F--Device full ()) The directory does not have room for the file name, or the output device does not have room for the output file. (User Action) See (ism_sec) for information on how to increase storage space. (?MONMRG--F--File not found ()) The input file specified was not found. (User Action) Check for a typing error in the command line. Make sure that the specified file resides on the specified device. Enter the command again. (?MONMRG--F--Incompatible input files () and ()) The input files indicated are not compatible linker map files generated by running a .MON or .BLD command file produced by SYSGEN. Or, possibly, one or both of the files have been corrupted. (User Action) Retry invoking the command file generated by SYSGEN. If the error occurs again, submit an SPR to Digital; include a listing of the SYSGEN answer file used to generate the command file which contains the invocation of the monitor merge utility (MONMRG) which produced this error message. (?MONMRG--F--Input error ()) A hardware error occurred while the indicated input file was being read. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?MONMRG--F--Insufficient memory) Not enough memory is available to accommodate the symbol table. (User Action) See (ism_sec) for information on how to increase memory space. (?MONMRG--F--Internal error) An internal error occurred while the monitor merge utility (MONMRG) was recovering from a previous system or user error. (User Action) Retry the operations that produced this error; if it occurs again, submit an SPR to Digital; include a listing of the SYSGEN answer file used to generate the command file which contains the invocation of the monitor merge utility (MONMRG) which produced this error message. (?MONMRG--F--Invalid command) The command line typed is invalid. (User Action) Check for a typing error in the command line and make sure that the command is in the correct format. Enter the command again. (?MONMRG--F--Invalid device ()) The volume indicated is not available. (User Action) Verify that the device is valid for the system in use. (?MONMRG--F--Invalid file format ()) The input file indicated is not a linker map file generated by running a .MON or .BLD command file produced by SYSGEN. Or, possibly, the file has been corrupted. (User Action) Retry invoking the command file generated by SYSGEN. If the error occurs again, submit an SPR to Digital; include a listing of the SYSGEN answer file used to generate the command file which contains the invocation of the monitor merge utility (MONMRG) which produced this error message. (?MONMRG--F--Output error ()) A hardware error occurred while the indicated output file was being written. (User Action) Check the procedures for recovery from hard error conditions listed in (hec_sec). (?MONMRG--F--Protected file already exists ()) An attempt was made to open a file with a name already assigned to an existing protected file. (User Action) Use the monitor UNPROTECT command or the PIP /Z option to change the protection level of the existing file, or use a different name to open a new file. (?MONMRG--W--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the monitor RENAME/NOPROTECT command or the PIP /Z option and delete it. (?MSBOOT--F--File not found) The specified file is not available for bootstrapping from the magtape. (User Action) Check for a typing error. (?MSBOOT--F--Invalid file name) An invalid file name was specified. (User Action) Check for a typing error in the command line. Verify that the file specification is in the proper format. (?MSBOOT--F--I/O error) A hardware error occurred during a magtape bootstrap operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?MSBOOT--F--Line too long) More than 80 characters were used in the MSBOOT command line. (User Action) Enter a valid MSBOOT command, limited to a file name and file type. (?MSCPCK--I--MUn-FW Rev Level is nnn/HW Rev Level is nnn) A command to run the TMSCP (Tape Mass Storage Communication Protocol) Controller Checking Program (MSCPCK.SAV) in your startup command file checks your TMSCP (MU) device controller (if present) and reports its revision level with this message. The n is the MU unit number and the nnn is a 3-digit firmware or hardware revision level.
Reliable TK50 operation on Q-bus processors requires a controller of at least firmware revision 4 and hardware revision 6. (User Action) If your configuration does not include a TMSCP device, you can disable the command to run MSCPCK in your startup command file by editing that file and placing an exclamation point (!) before the command (!R MSCPCK).
If the revision level is below firmware revision 4 and hardware revision 6, contact your local Digital field service representative to get a revised TMSCP controller. (?MSCPCK--W--TQK50 controller below FW Rev 4/HW Rev 6) The utility MSCPCK.SAV checked the TQK50 Q-bus controller for its revision level and found it below revision level. This means that, although the MU handler installs, you cannot use the MU device. (User Action) Contact your local Digital field service representative to get a new controller. Reliable TK50 operation on Q-bus processors requires a controller of at least firmware revision 4 and hardware revision 6. (?MSCPCK--W--TUK50 controller below FW Rev 4/HW Rev 2) The utility MSCPCK.SAV checked the TUK50 Unibus controller for its revision level and found it below revision level. This means that, although the MU handler installs, you cannot use the MU device. (User Action) Contact your local Digital field service representative to get a new controller. Reliable TK50 operation on Q-bus processors requires a controller of at least firmware revision 4 and hardware revision 6. (?NC-F-Handler may not be unloaded while in use) The user attempted to UNLOAD the handler while it was in use by a program. (?NQ-F-Handler may not be unloaded while in use) The user attempted to UNLOAD the handler while it was in use by a program. (?NU-F-Handler may not be unloaded while in use) The user attempted to UNLOAD the handler while it was in use by a program. (?PAT--F--Correction file has invalid record) The format of the correction file is not compatible with the object file format PAT requires. The standard language processors should produce the required format. (User Action) Verify that the correction file has the proper format and retype the command line. (?PAT--F--Correction file missing) The command line has no correction file specification. PAT requires both an input file and a correction input file in every command. (User Action) Enter a complete command to PAT. (?PAT--F--Correction file missing RLD record) The file is missing an RLD7 or p-sect definition command before the first TXT record. PAT cannot process the file. (User Action) Reassemble the correction file. (?PAT--F--Correction file read error) PAT detected an error while reading the correction file. Input hardware can cause this error. (User Action) Try the command again. If the error persists, see the procedures for recovery from hard error conditions listed in (hec_sec). (?PAT--F--Device full ()) The output volume does not have enough free space for the corrected object file. (User Action) If enough free space is on the output volume, use the form dev:filnam.typ[size] for the output file specification. Otherwise, see (ism_sec) for information on how to increase storage space. (?PAT--F--File not found ()) The file specified was not found. (User Action) Check for typing error in the command line, verify that the file name exists as entered in the command line, and try the operation again. (?PAT--F--Incompatible reference to global ()) The correction file contains a global symbol with improper attributes. () represents the name of the global symbol with improper attributes. (User Action) Modify the attributes of the global symbol. Choose DEFINITION or REFERENCE and choose RELOCATABLE or ABSOLUTE. Reassemble the correction file and type the command line again. (?PAT--F--Incompatible reference to section ()) The correction file contains a section name with improper attributes. () represents the name of the section with improper attributes. (User Action) Modify the section attributes or section type. Choose RELOCATABLE or ABSOLUTE and specify .PSECT or .CSECT. Reassemble the correction file and type the command line again. (?PAT--F--Input file has invalid record) The format of the input file is not compatible with the object file format PAT requires. The standard language processors should produce the required format. (User Action) Verify that the input file has the proper format and retype the command line. (?PAT--F--Insufficient memory) Not enough contiguous memory is available for the corrected output file. (User Action) See (ism_sec) for information on how to increase memory resources. (?PAT--F--Internal error) An internal software error condition occurred. (User Action) Try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PAT--F--Invalid command) The command line has a syntax error. (User Action) Check for typing errors and enter the command line again. (?PAT--F--Invalid device ()) An invalid or nonexistent device was specified in the command line. (User Action) (numbered) Check for a typing error in the command line. Using the SHOW DEVICES command, make sure the device handler is installed. If it is not, install it. (?PAT--F--Invalid GSD symbol in ()) The global symbol directory (GSD) contains an error. The file is probably not a valid object module. (User Action) Verify that the input file name is correct; check for a typing error in the command line. Reassemble or recompile the source code to obtain a good object module and try the operation again. (?PAT--F--Invalid RLD symbol in ()) An error occurred in the language processor, because a global symbol named in a relocatable record was not defined in the global symbol definition record. (User Action) Reassemble the indicated file. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PAT--F--No room for file ()) Volume does not have enough room to open output file. (User Action) Delete some nonessential files and squeeze the volume or copy some files to another volume, or get another volume with adequate space. (?PAT--F--Only /C allowed) The input module or correction file specifications contain an invalid option that is neither /C nor /C:n. (User Action) Enter a command line with appropriate options. (?PAT--F--Output error ()) PAT encountered an error while writing the output file. This error occurs when the output device is write locked or a hardware error condition exists. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?PAT--F--Protected file already exists ()) A protected file already existing on the output device has the same name as the file specified in the command. The operation involving the protected output file is not processed. (User Action) Use the UNPROTECT command to change the protection level of the existing file or use a different output file name. (?PAT--F--Unable to locate module ()) The correction file has a module name that does not exist in the input file. () represents the name of the nonexistent module. (User Action) Update the input file to include the missing module, or correct an improper module name in the correction file. Retype the command line. (?PAT--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (PAT) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?PAT--W--Correction file checksum error) PAT found a checksum value that is different from the value for the /C correction file option. Mistyping the /C option value or specifying an invalid version of the correction file causes this error. (User Action) Check for typing errors. Check both the checksum value and the correction file name used. Correct the command line. (?PAT--W--Correction file checksum is ()) PAT responds to the /C option on the correction file with this message. () is the octal value of the sum of all binary data composing the file. (User Action) This message is informational. (?PAT--W--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?PAT--W--Input file checksum error) PAT found a checksum value that is different from the value for the /C input file option. Mistyping the /C option value or specifying an invalid version of the input file causes this warning. (User Action) Check for a typing error. Check both the checksum value and the input file name used. Correct the command line. (?PAT--W--Input module checksum is ()) PAT responds to the /C option on the input module with this message. The octal value () is the sum of all binary data in the file. (User Action) This message is informational. (?PIP--E--Operation not completed) The /WAIT operation was aborted because the response to the mount message began with an N or was a CTRL/C. (User Action) This message informs you that the operation has been aborted. The response to the mount message must begin with a Y for the /WAIT operation to continue. (?PIP--E--Protected file already exists ()) A protected file already existing on the output device has the same name as the file specified in the command. The operation involving the protected output file is not processed. PIP processes any other operations specified in the same command line that do not involve protected output files. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file, or use a different output file name. (?PIP--F--Channel in use) An internal PIP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of PIP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--Channel not open ()) An internal PIP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of PIP.SAV and retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--Checksum error ()) A checksum error occurred during a formatted binary transfer. (User Action) Check for a typing error in the command line. Make sure that the correct file is being transferred. Data may have been lost from the input file. Try the operation again, using the /G or the /IGNORE option, and correct the file after input. (?PIP--F--Device full ()) The output device does not have enough room to contain the specified file, although preceding files were copied. (User Action) See (ism_sec) for information on how to increase storage space. (?PIP--F--Device in use) Another job was using the device (normally MT or MM). (User Action) Try the operation again after the other job is finished or aborted. (?PIP--F--Directory full ()) The output volume's directory does not have enough space to create the output file. (User Action)Use the SQUEEZE command to consolidate free space on the output volume or copy the output volume to a volume with a larger number of directory segments. Reenter the command. (?PIP--F--Directory input error ()) A hardware error occurred while the directory was being read. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?PIP--F--Directory I/O error () ) The PIP utility experienced an I/O error when accessing the directory for the indicated volume. (User Action) The I/O error is caused by a write-protected output volume or a corrupted directory structure on the input or output volume. Check if the output volume is write protected. If it is, remove the write protection. If the output volume is not write protected, attempt to recover data on the volume with the corrupted directory, using the methods described in the (vff_book). (?PIP--F--Fetch error ()) (numbered) An internal PIP or a system error occurred. The copy of PIP.SAV, the monitor file, or the specified device handler may be corrupted on disk. The in-memory copy of PIP or the monitor may be corrupted. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of PIP.SAV and the specified device handler. Retry the operation. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--File not found ()) The input file specified was not found or no input files with the expected name or type were found during a wildcard expansion. This message also occurs if /BEFORE, /SINCE, or /DATE was used and no files were found that corresponded to the specified date(s). (User Action) Check for a typing error in the command line, verify that the file name exists as entered in the command line, and try the operation again. (?PIP--F--File sequence number not found) The input magtape volume has fewer files than the sequence number in the /POSITION option. (User Action) Check for a mistyped file sequence number. Check the magtape directory by using the DIRECTORY/POSITION command or the DIR /B option. Reenter the command. (?PIP--F--Input error ()) You tried to use COPY on a magtape that was created by BUP, or PIP detected a hardware error while reading the file. (User Action) If the input device is a magtape, check to see if the magtape was written by BUP (BACKUP command). If so, use the appropriate BACKUP command to restore the files on the tape. Otherwise, see the procedures for recovery from hard error conditions listed in (hec_sec). Try the operation again, using the /G or the /IGNORE option. (?PIP--F--Insufficient memory) Memory overflow resulted from too many device and/or file specifications---usually in wildcard operations---and no room for buffers. (User Action) See (ism_sec) for information on how to increase memory space. Try copying the files one at a time, without using wildcards. (?PIP--F--Invalid command) The command line is invalid. An option incompatible with the command may have been typed. (User Action) Check for a typing error. Verify that the format and syntax are correct and retry the operation. (?PIP--F--Invalid delete ()) A magtape was used as the device in a DELETE command, a TYPE/DELETE command, a PRINT/DELETE command, or with the /D option in a PIP command line. No files are deleted from the magtape. (User Action) Delete the files from the magtape by copying files that should be saved to another volume with a COPY/QUERY command or a PIP /G option, then reinitialize the original magtape. Transfer the saved files back to the magtape, if necessary. (?PIP--F--Invalid device ()) An invalid or a nonexistent device was specified. (User Action) Check for a typing error in the command line. Verify that the device specified is valid. (?PIP--F--Invalid directory) The device did not contain a properly initialized directory structure---end-of-tape file on cassette; empty file directory on other devices. (User Action) Initialize the device with the INITIALIZE command or the DUP /Z option before using it the first time. (?PIP--F--Invalid option: /x) An invalid option was used in a command line. (User Action) Check for a typing error in the command line. Use only those options listed as valid for PIP in the (sum_book). (Also see the (sug_book) for the list of valid options for the COPY, DELETE, RENAME, PROTECT, and UNPROTECT commands.) (?PIP--F--Invalid output file) The specified file name is invalid for the command. (User Action) Type the command again. (?PIP--F--Invalid protect or unprotect ()) An error was detected within the PIP program. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--Invalid rename ()) An invalid rename operation was attempted. (User Action) Check for a typing error in the command line. Verify that the same device name appears in both the input and the output specifications. (?PIP--F--Invalid set date ()) An error was detected within the PIP program. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--Invalid use of wildcards ()) (numbered) The output file name or the file type does not match the input file specifications in the copy operation. The output file specification contained embedded wildcards (* or % ) as in A*B.MAC and A%B.MAC. (User Action) Check for errors and retype the command line. (?PIP--F--Invalid value specified with option: /x) During the copying of a magtape, the value of the file sequence number in a COPY/POSITION command or a PIP /M option is not in the range --2 to +999. No files were copied from the magtape. (User Action) Check for a typing error. Retype the command, using the appropriate file sequence number. (?PIP--F--Library file not copied ()) An object library (.OBJ) is an input file in a COPY/BINARY command or a PIP /B option. The file name is shown in this message. Copying stops. (User Action) Do not use the /BINARY or the /B option when copying object libraries. Use the /QUERY or the PIP /Q option to copy files selectively and type (NO) for each object library. (?PIP--F--Output error ()) (numbered) An unrecoverable error, perhaps caused by a hardware or a checksum error, occurred while PIP was writing a file. The device does not have enough room to create a file.
In a multiple file operation, the command was successfully executed on every file preceding the one interrupted by the error. (User Action) See (ism_sec) for information on how to increase storage space. Check the procedures for recovery from hard error conditions listed in (hec_sec). (?PIP--F--Output file full ()) (numbered) Physical end-of-tape was detected on an output magtape volume. The output file is not large enough for the input file.
For devices other than magtapes, fragmented storage space can cause this message. Copies from magtape or cassette and copies with the /CONCATENATE command or the PIP /U option also cause the error. (User Action) Use the /ALLOCATE command or the square bracket construction to specify large output files, if the output volume has sufficient free space. Check (ISM_SEC) for information on how to increase storage space. (?PIP--F--Protected file ()) An attempt was made to delete a protected file. (User Action) Remove the file's protection, using the UNPROTECT command or the PIP /Z option, and type the command again. (?PIP--F--Size function failed) PIP attempted to read the size of a device that is on a unit not supported by the monitor. (User Action) Mount the device on a unit number that the monitor supports. Otherwise, perform another system generation to add more units for the specified device. (?PIP--F--System error) (numbered) An attempt was made to use a device not on the system. An internal error has occurred. (User Action) (numbered) Make sure that the device specified is loaded. Check the directory of the relevant device to ensure that the necessary system programs are intact. Reboot the system, if necessary. Try the operation again. If the error persists, submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?PIP--F--Too many output files) More than one output file was specified in the command line. (User Action) Limit the number of output files on the command line to one. (?PIP--F--Verification error ()) The /VERIFY command or the PIP /V option was used after a copy operation and found differences between the new and the original copies of the file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?PIP--F--Wrong version of RT--11) An attempt was made to run RT--11 Version 5 PIP on an outdated version of RT--11. (User Action) Do not attempt to run RT--11 Version 5 PIP under any earlier RT--11 versions. (?PIP--I--Device full ()) The COPY/MULTIVOLUME command was used with a mounted output device that is full and does not have room for any of the input files. PIP continues and asks for another output device to be mounted. (User Action) Remove the full output volume and mount another output volume. (?PIP--I--File not found ()) The specified file was not found. (User Action) This message is informational because the /INFORMATION option was specified in the command line. (?PIP--W--File larger than output device ()) A file specified in the COPY/MULTIVOLUME command is larger than the output device. The file is not copied and the operation continues. (User Action) Use a larger device to back up the specified file that is too large. (?PIP--W--Input error ()) PIP detected a hardware error while reading the file. Execution continues because a /G or an /IGNORE option was used in the command line. (User Action) Examine the file for errors after the command finishes. (?PIP--W--No .SYS action) The /Y or the /SYSTEM option was not included with a command specified on a .SYS file. A wildcard transfer is most likely to cause this message. (User Action) Check for a typing error in the command line. The command is executed for all but .SYS files. Use the /Y or the /SYSTEM option if .SYS type files should also be included in the operation. (?PIP--W--Output file found, no operation performed ()) The command line included the /NOREPLACE or the PIP /N option, and a file on the output volume already has the name shown. That file is not changed, and the input file with the same name is not copied. (User Action) If output files having the same names as input files do not require protection, reissue the command without the /NOREPLACE or the /N option. Otherwise, change one of the names in each conflicting pair---the file already on the output volume, the file on the input volume, or the explicit output file name in the command line. (?PIP--W--Reboot) System (.SYS) files have been created, moved, renamed, or deleted from the system device. (User Action) If any of the .SYS files in use by the current system have been physically moved on the system device, reboot the system immediately. (The reboot operation must not be performed until PIP returns with the prompting asterisk for the next command or until a monitor command returns to the monitor prompt.) Otherwise, the message can be ignored. (?QUEMAN--E--File not found ()) The specified file was not found. (User Action) Check for a typing error in the command line. Make sure that the specified file resides on the specified device. Enter the command again. (?QUEMAN--E--Insufficient memory) Not enough memory is available to build the job request. (User Action) See (ism_sec) for information on how to increase memory resources. (?QUEMAN--E--Invalid command) The command line given to QUEMAN is not in the correct format. (User Action) Check for a typing error in the command line and make sure that the command is in the correct format. Enter the command again. (?QUEMAN--E--Invalid device ()) The specified device was not found in the system device tables. (User Action) Reenter the command, using a valid device. (?QUEMAN--E--Invalid option: /x) An invalid option was specified in the command line. (User Action) Check for a typing error in the command line and review the list of valid options. Reenter the command line. (?QUEMAN--E--QUEUE full) Not enough space is available in the work file for the number of input files specified. (User Action) Reduce the number of files requested or wait until some jobs have run to completion before making additional requests. (?QUEMAN--F--Handler not loaded ()) The handler for the device is not loaded. (User Action) Load the device handler and reenter the command. (?QUEMAN--F--Input error ()) An error occurred while a file or the directory was being read. This error may be caused by a hard error or an accidental deletion of the QUEUE work file. (User Action) Try reading the file or directory again. Use /L to list the current contents of the QUEUE. If the error persists, copy each file to another device. Reformat the disk, using the format program.
If the error persists, the disk is bad. Use a different disk for the operation. (?QUEMAN--F--Invalid date) An invalid value was specified for the day, month, or year in the /DATE, /BEFORE, or /SINCE option. (User Action) Check for a typing error in the command line. Reenter the command, using valid values for the option. (?QUEMAN--F--QUEUE is not running) The QUEUE program is not running as a foreground or system job. (User Action) Use FRUN to install QUEUE in the foreground or use SRUN to install QUEUE as a system job. (?QUEMAN--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (QUEMAN) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?QUEMAN--I--File not found ()) The specified file was not found. (User Action) This message is informational because the /INFORMATION option was specified in the command line. ( ?QUEUE--E--Cannot open input device ()) The specified input device could not be opened. (User Action) Make sure that the input device is on line. Reenter the job request. (?QUEUE--E--Cannot open output device ()) The specified output device could not be opened. (User Action) Make sure that the output device is on line. Reenter the job request. (?QUEUE--E--File not found ()) The file sent to the work file was deleted. (User Action) Make sure that the specified file resides on the specified device. Reenter the job request to print the file. (?QUEUE--E--Handler not loaded ()) The specified device handler is not loaded. (User Action) Load the handler and reenter the job request to print the file. (?QUEUE--E--Protected file exists ()) An attempt was made to create a protected file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?QUEUE--F--Cannot delete protected file ()) The referenced file is protected. QUEUE attempted to delete an input file in response to the /D option or the PRINT/DELETE command, to open an output file on a file-structured device, or to delete a work file that contained a protected file of the same name. (User Action) Use the UNPROTECT command or the PIP /Z option to remove the protection status of the file and reenter the request. (?QUEUE--F--Cannot open message channel) QUEUE was unable to open a message channel on which to receive job requests. This is an internal error. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?QUEUE--F--Input error ()) An input error occurred on the specified file. (User Action) See procedures for recovery from hard error conditions listed in (hec_sec). (?QUEUE--F--No room for QUEUE workfile on SY:) The system device does not have enough room for the QUEUE work file. (User Action) See (ism_sec) for instructions on how to increase storage space on volumes. (?QUEUE--F--Output error ()) A hard error occurred during an output transfer while the specified job was being processed. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?QUEUE--F--Output error SY:QUFILE.WRK) A hard error occurred while the QUEUE work file was being updated. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). ( ?QUEUE--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (QUEUE) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?QUEUE--W--Error sending message to ()) QUEUE was unable to send an acknowledgment to the requesting job, because the request message to QUEUE exited before receiving an acknowledgment message. (User Action) This message is informational. (?RESORC--F--Error reading directory) An input error occurred while RESORC was reading a directory segment from the system device. (User Action) Make sure that the system device is mounted and up to speed. Scan the system device for bad blocks, using the DIRECTORY/BADBLOCKS command or the DUP /K option. (?RESORC--F--Input error ()) An input error occurred while RESORC was reading the specified file. (User Action) Scan the system device for bad blocks. It may be necessary to obtain a fresh copy of the monitor from a backup copy of the system. (?RESORC--F--Insufficient memory) Not enough free memory is available for RESORC to allocate space to its input buffer. (User Action) Unload the foreground or the system job, if possible, and any unnecessary handlers. (?RESORC--F--Invalid UMR allocation table) An error was detected in the UMR allocation table. (User Action) Reboot the system and try the operation again. If the error persists, submit an SPR to Digital. (?RESORC--F--Invalid option) The option specified in the command line is invalid. (User Action) Check for a typing error in the command line. Use only valid options. See the (sum_book) or the (sug_book) for a list of valid options. (?RESORC--F--System error) A .DSTATUS or a .LOOKUP request to the system device failed. The system device is not mounted, or the image of the monitor currently in memory is corrupted. (User Action) Make sure that the system device is mounted and up to speed. It may be necessary to reboot the system. (?RESORC--F--Wrong version of RT--11) An attempt was made to run RT--11 Version 5 RESORC on an outdated version of RT--11. (User Action) Do not attempt to run RT--11 Version 5 RESORC under any earlier RT--11 versions. (?RESORC--I--No queues active) Neither QUEUE nor SPOOL were running when you issued a SHOW QUEUE or RESORC /Q command. (User Action) This message is informational. (?SETUP--F--Ambiguous command ()) The command abbreviation entered is not unique. (User Action) Retype the command, using enough characters to distinguish it from other commands. (?SETUP--F--Ambiguous value ()) The value you specified contains too few numbers to be unique. (User Action) Retype the command, using enough numbers to distinguish the value from others. (?SETUP--F--ANSWERBACK message too long) The message you specified for the answer-back feature has too many characters. (User Action) Retype the command, specifying an answer-back message with 20 (decimal) or fewer characters. (?SETUP--F--Channel in use) An internal SETUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of SETUP.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?SETUP--F--Channel not open ()) An internal SETUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of SETUP.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?SETUP--F--Fetch error ()) An internal SETUP or a system error occurred. The copy of SETUP.SAV, the monitor file, or the specified device handler may be corrupted on disk. The in-memory copy of SETUP or the monitor may be corrupted. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of SETUP.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?SETUP--F--File not found ()) The device handler file for the device you specified was not found on the system volume. (User Action) Copy the handler file for the device to the system volume and try the operation again. (?SETUP--F--Input error ()) SETUP detected a hardware error while reading the handler file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). Try the operation again. (?SETUP--F--Insufficient memory) Not enough memory is available to complete the requested operation. (User Action) See (ism_sec) for information on how to increase memory space. The command line is invalid. (User Action) Check for a typing error. Make sure the format and syntax of the command line are correct, and retype the command line. (?SETUP--F--Invalid command) The command you typed is invalid. (User Action) Check for typing error. Be sure format and syntax of command line are correct, then retype the line. (?SETUP--F--Invalid command for destination) The command you typed is invalid for the hardware you specified. (User Action) Retype the command, making sure the command option you choose is valid for the hardware (terminal, printer, or clock) you specify in the command line. (?SETUP--F--Invalid date) When attempting to set the date, you put in an invalid date. (User Action) Check for typing error. Retype the command. (?SETUP--F--Invalid device ()) The specified device is not installed in the monitor device tables. (User Action) Check for a typing error in the command line. Use the INSTALL command to add the device to the monitor device tables. (?SETUP--F--Invalid processor for command: ()) The command you typed is invalid for your processor. Some SETUP commands are valid for CTI Bus-based processors only; some commands are valid for PDP--11 hardware only. (User Action) Make sure the command you type is valid for your processor. (?SETUP--F--Invalid terminal for command) An attempt was made to execute the SETUP COLOR command on a monochrome monitor. (User Action) Issue the SETUP COLOR command only when using a color monitor. (?SETUP--F--Invalid terminator for command: ()) An attempt was made to execute a SETUP command terminated by an invalid character, such as a colon (:) or equal sign (=) with no parameter. (User Action) The only valid terminators for a command that does not take a parameter are space, comma (,), or RETURN ( (Return) ). (?SETUP--F--Invalid value ()) A value specified in the command line is invalid. (User Action) Check for a typing error in the command line. Make sure values you specify as arguments to SETUP commands are positive integers. (?SETUP--F--Printer is not available) You tried to issue a printer command and SETUP cannot find an LS printer on your system. (User Action) This message is informational. (?SETUP--F--Unexpected EOF ()) An internal SETUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of SETUP.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?SETUP--F--Wrong version of PI) You tried to run SETUP, but the version of PI(X).SYS on your system does not match the version of SETUP. (User Action) Use the version of PI(X).SYS distributed with the same version of RT--11 as the version of SETUP you are using. (?SETUP--U--System error) An internal SETUP error occurred. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of SETUP.SAV and retry the operation. If the error persists, submit an SPR to Digital. (?SIPP--E--Below segment boundary) An attempt was made to open a location below the low end of the segment. SIPP returns to the (OFFSET?) prompt. (User Action) Do not try to open a location below the low end of the segment. (?SIPP--E--Checksum error) An invalid checksum was typed. SIPP returns to the (SEGMENT?) or the (BASE?) prompt so that the error can be found and corrected. (User Action) If the checksum was mistyped, press (CTRL/Y), followed by a RETURN, to return to the checksum prompt, and type the checksum again. If the modifications were typed incorrectly, type (;V) to display the modifications in words, not bytes, made in the current session. Correct the modifications to reflect the distributed patch. Press (CTRL/Y), followed by a RETURN, and type the correct checksum. Note that SIPP does not install patches and does not create a log file if the checksum is incorrect. (?SIPP--E--End of file) An attempt was made to patch beyond the end of the file. This error will occur if you specify values for (Base) and (Offset) that lie outside the limits of the file. The error may also occur if you try to patch a file other than a .SAV file without specifying the /A option. (User Action) SIPP returns with the (OFFSET?) prompt. It does not discard any previous changes. Be sure that the values you specify for (Base) and (Offset) are within the limits of the file you are patching. If you are patching a file other than a .SAV file, include the /A option. (?SIPP--E--Exceeds program limit) The location being examined or modified is beyond the end of the program. (User Action) SIPP returns with the (OFFSET?) prompt and does not discard any previous changes. The current open location is not modified. (?SIPP--E--Exceeds segment boundary) An attempt was made to examine or to change a location beyond the segment's block boundary. (User Action) SIPP returns to the (OFFSET?) prompt without losing any previous changes. (?SIPP--E--Invalid address) An invalid value was specified in the segment, the base, or the offset. (User Action) Control returns to the (OFFSET?) prompt. (?SIPP--E--Invalid boundary size) The search range exceeded the size of the file. (User Action) Retype the search command and respond to the prompt with an accurate search range. (?SIPP--E--Invalid command) The command line typed is not valid. (User Action) Check for a typing error in the command string and try again. (?SIPP--E--Invalid extension of root segment) An attempt was made to modify the root beyond the root segment. SIPP returns to the (OFFSET?) prompt. (User Action) If the overlaid file contains /V overlays, the size of the root can be extended up to the block boundary. Do not try to extend the root segment if the overlaid file contains one or more /O overlays. (?SIPP--E--Invalid input) The input is invalid. SIPP prompts again. (User Action) Check for a typing error. Review the valid SIPP commands (see (sum_book)). Try the operation again. (?SIPP--E--Invalid option: /x) An option specified in the command string is not valid. (User Action) Check for a typing error in the command line. Use only valid options. See the (sum_book) for valid options. (?SIPP--E--Invalid option combination) Both the /C and /D options were used. (User Action) Enter the command line again, specifying only one of these options. (?SIPP--E--Invalid search command) The command or input to the search prompts is not valid. (User Action) Check for a typing error and try again. (?SIPP--E--Invalid segment number) The segment number specified does not exist. SIPP repeats the (SEGMENT?) prompt or the (START?) prompt if in search mode. (User Action) Check for a typing error. Check the program's link map to determine the true overlay structure. (?SIPP--E--Not V4 overlaid file) The file being patched is overlaid but was not produced by a Version 4 or later linker. SIPP repeats its prompt and waits for another command line. (User Action) Relink the program, using a Version 4 or later linker, or modify the file as explained in the (sum_book). (?SIPP--E--Odd base address) An odd base address was specified. SIPP repeats the (BASE?) prompt. (User Action) Type an even number. An odd base address may be specified in response to the (OFFSET?) prompt. (?SIPP--E--Patch buffer full) All memory available for storing modifications is in use. (User Action) Press (CTRL/Y) followed by a RETURN to insert the modifications typed so far. If this message occurs while you are extending a file, a segment, or a program, reopen the file and place a 0 one point beyond the location at which the message was produced. (?SIPP--E--Region size exceeds 96K) The modified program was extended beyond the maximum overlay address space. (User Action) Stop the current operation by pressing (CTRL/C) and reapply the modifications. Alternatively, continue the current operation by correcting the size of this segment to the size indicated in the overlay table and the two size words for this segment in the window definition block of the handler. (?SIPP--F--Device full ()) The output device does not have enough room for the SIPP modification. The log file is not created. (User Action) Use the SQUEEZE command to consolidate the disk or use another device for this operation. (?SIPP--F--Directory I/O error) The SIPP utility experienced an I/O error when accessing the directory for the indicated volume. (User Action) The I/O error is caused by a write-protected output volume or a corrupted directory structure on the input or output volume. Check if the output volume is write protected. If it is, remove the write protection. If the output volume is not write protected, attempt to recover data on the volume with the corrupted directory, using the methods described in the (vff_book). (User Action) (?SIPP--F--File not found ()) The input file is not on the specified device. (User Action) Check for a typing error in the command line, verify that the file name exists as it was typed, and try again. (?SIPP--F--Input error ()) A hardware error occurred when SIPP read the file to be modified. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SIPP--F--Insufficient memory) Not enough memory is available to run SIPP. (User Action) Increase the available memory by unloading device handlers, the foreground job, or one or more system jobs. (?SIPP--F--Invalid device ()) The specified device is not a random-access device. (User Action) Use a valid device. (?SIPP--F--Output error ()) A hardware error occurred when SIPP tried to patch the file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?SIPP--F--Patch aborted, no modifications made) A hardware error occurred. The patch is not installed. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?SIPP--F--Protected file already exists ()) An attempt was made to create a log file having the same name as an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection status of the file. (?SIPP--F--Size function failed) A hardware error occurred while SIPP was determining the size of the volume. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?SIPP--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (SIPP) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?SIPP--I--Approaching segment boundary) SIPP is within five words of exceeding the high limit, or block boundary, of an overlay segment. (User Action) This message is informational; the operation continues. (?SIPP--I--End of file) SIPP opened the next location beyond the end of the file during a patch operation. (User Action) SIPP returns to the (OFFSET?) prompt. (?SIPP--I--Extending high limit) An attempt was made to request a change to a location beyond the program's high limit. (User Action) When SIPP installs the patch, it calculates the new high limit and updates location 50 and the bit map of the program. This informational message is printed only once during a session. (?SIPP--I--Extending overlay segment) An attempt was made to request a change to a location beyond the segment's linked limit, but before its block boundary. (User Action) When SIPP installs the patch, it automatically updates the segment size in the overlay table. This message will occur the first time an overlay segment is extended during a session. (Each session begins with the (SEGMENT?) or (BASE?) prompt.) (?SIPP--I--No modifications made) The patch operation was terminated before modifications were made to the file; the file is not patched. (User Action) This message is informational; the operation continues. (?SIPP--W--Patch buffer approaching limit) SIPP is about to run out of memory for storage of modifications. (User Action) SIPP can accept five more modifications. To extend the file, press (CTRL/Y) and insert the remaining patches. (?SL--E--Invalid command) You tried an invalid RECALL option. (User Action) Reissue the command with a valid option. (?SL--E--ON/KMON/OFF must be last option in SET command) A SET SL () command included more than one option, and one of the options appeared after ON, OFF, or KMON. (User Action) Reenter the command, placing the ON, OFF, or KMON option last on the command line. (?SL--E--SET SL LEARN is not supported for VT52) You cannot use the SET SL LEARN capability if your terminal is one of the VT52-series devices. (?SL--F--Insufficient high memory) In an RT--11 XM environment, there was inadequate high memory for loading SL's private memory region. (User Action) Make more high memory available by unloading unnecessary modules or by making VM smaller. (?SL--F--No response to DA request) There was no terminal response to the command SET SL ASK. SL cannot determine your terminal type. (User Action) If you believe your terminal to be VT100 compatible, then SET SL OFF and SET SL VT100. Next, SET SL ON or SET SL KMON to restart SL. (?SL--F--SL cannot be unloaded while running) You attempted to UNLOAD the SL handler while SL was running. (User Action) Enter the command SET SL OFF. This automatically UNLOADS the SL handler. (?SL--F--Unknown DA response) The terminal's response to SET SL ASK was not recognized as a Digital device identifier. SL cannot determine your terminal type. (User Action) If you believe your terminal to be VT100 compatible, then SET SL OFF and SET SL VT100. Next, SET SL ON or SET SL KMON to restart SL. (?SL--F--Unsupported device) The terminal identified itself as one that is not supported by SL. (User Action) You may not be able to use SL with your terminal. If you believe that your terminal is VT100 compatible, then use SL cautiously after typing SET SL VT100. (?SL--I--At left margin now) You attempted to move or delete to the left when the cursor was at the left margin. (User Action) Enter a command that moves or deletes to the right. (?SL--I--At right margin now) You attempted to move or delete to the right when the cursor was at the right end of the command line. (User Action) Enter a command that moves or deletes to the left. (?SL--I--Following options ignored---()) The listed SET options were not recognized, executed, or set, because they were positioned beyond ON, OFF, or KMON options. (User Action) In order that all the options take effect, you should SET SL OFF and then reenter the original command, making sure to position the ON, OFF, or KMON option as the final one. (?SL--I--Nothing to undelete) You attempted to undelete text when there was no previously deleted text. (User Action) Use any valid function or command. (?SL--I--Supporting as a (), terminal is ()) These informational messages are produced after issuing the SET SL ASK command. They report the results of a device attributes (DA) request. (?SL--W--Invalid control character) The control character just typed is not among those recognized by the single-line editor. (User Action) Use only the control characters that are valid for the single-line editor. See the (sug_book) for a list of valid single-line editor control characters. (?SL--W--Invalid key) The key just typed is not among those recognized by the single-line editor. (User Action) Use only the keys that are valid for the single-line editor. See the (sug_book) for a list of valid keys. (?SL--W--No room to insert) There is not enough room to insert text on the current line. (User Action) Delete existing text from the current line, then insert new text, or advance to the next line. (?SL--W--Unsupported command) The single-line editor does not support the command just entered. (User Action) Use only supported commands. See the (sug_book) for a list of supported commands. (?SLP--F--Audit trail exceeds line limit) The /S or /L option values were used in invalid combinations. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Check the (sum_book) for valid combinations of option values. Retype the command. (?SLP--F--Audit trail overwrites line) Text on a source line went beyond the point where the audit trail was placed. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Use the /P option to reposition the audit trail. (?SLP--F--Backup file suppression unsuccessful) /N was specified to suppress the .BAK file. The operation was unsuccessful. (User Action) If the original source file is protected, use the UNPROTECT command or the PIP /Z option to remove the protection. (?SLP--F--/C Invalid option) The /C option was specified with an output file in the SLP command line. (User Action) Make sure that the /C option is specified in the SLP command line with an SLP input file and/or command file. (?SLP--F--Characters before the "-" in ()) SLP found characters before the hyphen symbol (-) in the update text file. Any data that precedes this symbol in the update text file is ignored. (User Action) Make sure that the hyphen symbol (-) is at the beginning of the update text file. (?SLP--F--Command syntax error) A line read from the command file is not a valid command. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Check the command line for a typing error. Make sure that the command is formatted correctly (see the (sum_book)). Try the operation again. (?SLP--F--Correction file checksum error) The computed checksum of the command file does not match the value specified in the /C:n option of the SLP command line. (User Action) Check for a typing error in the command line; verify that the correct checksum value and file name were specified. Retype the command line. (?SLP--F--Device full ()) During a write operation, an end-of-file was reached. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) See (ism_sec) for information on how to increase storage space or use another output volume. (?SLP--F--Extra file(s) specified) More than two output or input files were specified in the command line. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Retype the command line, using no more than two output files and two input files. (?SLP--F--File created; protected file already exists () ) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List an unsorted directory. If the unprotected file appears before the protected file in the directory listing, either delete or rename it. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?SLP--F--File not found ()) The specified file is not located on the specified device. (User Action) Check the command line for typing errors. Verify the location of the specified file and issue the command again. (?SLP--F--File protected) An attempt was made to modify a protected file. (User Action) Change the protection status of the file with the RENAME/NOPROTECT command or the PIP /Z option. (?SLIP--F--Hard error on device) A hardware error occurred during an I/O transfer. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SLP--F--Insufficient memory) Not enough memory is available for the combined requirements of the line buffer and block buffers for the files. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) See (ism_sec) for information on how to increase memory resources. (?SLP--F--Invalid option: /x) An invalid option was specified. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) See the (sum_book) for a list of valid options. (?SLP--F--Invalid rename) The SLP program tried to rename the output file that was sent to magtape. (User Action) Send the SLP output file to a volume other than magtape, which is not a valid output device for SLP operations. (?SLP--F--Invalid value specified with option: /x) An option value specified is not within the range of valid values. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) See the (sum_book) for a list of valid options and the range of valid values for each option. (?SLP--F--Line number error) A command line specified a numeric line locator that is not in the correct format. In an update line, locator2 pointed to a source file line that appears before the line pointed to by locator1. This message can also indicate that the update lines do not edit the source file in order from the beginning of the file to the end. (User Action) Check the command line for a typing error. Make sure that the command is formatted correctly, that the update lines reference source file lines in the correct order, and that locator1 and locator2 correctly define a range of lines in the source file. (?SLP--F--Line too long) A line was read that is longer than the line buffer. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Use the /L option to make the buffer larger. (?SLP--F--Protected file already exists ()) An attempt was made to create a protected file having the same name as an existing file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?SLP--F--Search failure in source file) A specified source line was not found in the source file. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Verify that the specified source line is in the source file. Add the missing source line, if necessary, or specify another source line. (?SLP--F--Source file checksum error) The computed checksum of the source file being updated does not match the value specified in the /C:n option of the SLP command line. (User Action) Check for a typing error in the command line; verify that the correct checksum value and file name were specified. Retype the command line. (?SLP--F--Source file not specified) The command did not specify a source file. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Try the operation again, specifying a source file in the command line. (?SLP--F--System error) This is an internal error. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Submit an SPR to Digital; include with the SPR a program listing and a machine-readable source program, if possible. (?SLP--F--Unexpected end of correction file) The correction file does not contain the end-of-file line (/). The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Change the correction file to include the end-of-file line (/). (?SLP--F--Value required: /x) An option specified requires a value, but none was given. The current editing session is terminated, and no output files are produced. Control returns to the CSI level. (User Action) Specify a value for the option and type the command again. (?SLP--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (SLP) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?SLP--I--() checksum is ()) The /C option was specified in the SLP command line to determine the checksum of an input file. (User Action) This message is informational. (?SLP--W--Audit trail overwrites existing audit trail) An attempt was made to write an audit trail at the end of a line that already ends with an audit trail. The new audit trail overwrites the old audit trail. (User Action) If the new audit trail is not acceptable, write the original or a new audit trail at the end of the line. (?SLP--W--No update text found) The update text file does not have the hyphen symbol (-). No changes were made, and control returns to the CSI prompt. (User Action) Check for a typing error. Make sure that the hyphen symbol (-) precedes the update text file. (?SPOOL--E--Device () already assigned to SPn: ) An attempt was made to assign the named printer device to more than one SPOOL output unit. (User Action) Assign only one printer device to a SPOOL output unit. (?SPOOL--E--Device handler not loaded for ()) A printer device handler is not loaded. (User Action) Load printer device handlers before starting the SPOOL program. (?SPOOL--E--SO device is file structured) A device with a logical name of the form "SOn" is a file-structured device, such as a disk. (User Action) Assign the "SO" names to physical printer device names only; for example, LP and LS. (?SPOOL--E--SO device is SP) A device with a logical name of the form "SOn" is assigned to an "SPn" device. (User Action) Assign the "SO" names to physical printer device names only; for example, LP and LS. (?SPOOL--F--Cannot attach SPX region) The SP handler is not installed. (User Action) Use the INSTALL command to install the SP handler. In XM monitors, there must be adequate extended memory for SP to install. (?SPOOL--F--Cannot create SPOOL region) The SPOOL program cannot create a SPOOL region since there is inadequate extended memory. (User Action) In XM monitors, there must be adequate extended memory for SP to install. (?SPOOL--F--Cannot create work file) The SPOOL program attempted to open a work file on the system disk or on a device whose logical name is SFD, if that logical device name is defined. The work file was not created due to one of several possible reasons: (numbered) The disk is write protected. There is inadequate space on SY or SFD. At least 10 blocks must be available. The file SPOOL.SYS exists and is protected. (User Action) Be certain that none of the conditions listed above is true, then try to restart the SPOOL program. (?SPOOL--F--Cannot get memory (use /BUFF:256.)) Under the FB monitor, SPOOL requires extra memory for data buffers, and this memory was not allotted. (User Action) Restart the SPOOL program by specifying /BUFF:256. with the FRUN command. (?SPOOL--F--Cannot map SPX window) On an XM monitor, the SPOOL program could not map to the SP handler's extended memory region. (User Action) Make sure that the SP handler is up to date and correctly installed. (?SPOOL--F--Input error on PI during PRINT SCREEN) The PRINT SCREEN function failed on a CTI Bus-based processor. The PI handler may be corrupt in memory. (User Action) Reboot the system, restart SPOOL, and try the PRINT SCREEN key. If this fails, obtain fresh copies of PIX.SYS, SPX.SYS, and SPOOL.SAV from your distribution media. (?SPOOL--F--Invalid work file size) A patched version of SPOOL.SAV specifies a work file larger than 8192 blocks. (User Action) The maximum work file size for SPOOL.SAV is 8192 blocks. Patch SPOOL.SAV accordingly. (?SPOOL--F--I/O error on work file) An I/O error occurred when SPOOL was either writing to or reading from the work file. (User Action) Check to make sure that the SY or SFD device is on line. Check that disk for bad blocks. (?SPOOL--F--No SO devices in system) The SPOOL program found no valid printer devices in the configuration in its initialization. (User Action) Check that there is at least one printer device on the system, that the printer device handler is loaded, and that it has a name of the form "LP", "LS", or "SOn". (?SPOOL--F--Output error ()) An I/O error occurred when the SPOOL program attempted to write data to a printer device. (User Action) Check to be sure that the spooled printer devices are on line. (?SPOOL--F--SET USR NOSWAP to start; it may swap once running) On an FB monitor, the USR was not resident when SPOOL was started. (User Action) Type SET USR NOSWAP to force the USR into memory. After SPOOL is initialized, you may allow the USR to swap by typing SET USR SWAP. (?SPOOL--F--Use virtual version SPOOL.SAV) On an XM monitor, an attempt was made to run SPOOL.REL. The .REL version of SPOOL is not compatible with the XM SPOOL handler, SPX. You must use SPOOL.SAV under XM. It is designed to occupy a much smaller amount of low memory. (User Action) FRUN or SRUN SPOOL.SAV on XM monitors. (?SPOOL--F--Work file device handler not loaded) The device handler associated with the SFD device is not loaded. (User Action) LOAD the SFD device before restarting SPOOL. (?SPOOL--F--Work file too small) Fewer than 10 blocks were available in the SPOOL program's work file. (User Action) Make more space available on the work file device, SY or SFD. (?SPOOL--I--Spooling started on xxn: through ()) The SPOOL program informs you that it has successfully established a spool connection on device (), and that you should direct output to that device through the name (). (User Action) This message is informational. (?SPOOL--W--Invalid SP unit) (numbered) A SET command has been issued to SP, which specifies an inactive SP unit. Output has been sent to an inactive SP unit. (User Action) Reenter the command, specifying a valid and active SP unit. (?SPOOL--W--Output to unrecognized channel) (numbered) An I/O request is associated with a channel that has not been properly opened. An internal error has occurred. (User Action) Type SHOW QUEUE to see whether there are spooled blocks pending. If so, and if no printer I/O is apparent, ABORT the SPOOL program, and restart it. (?SRCCOM--F--Device not active ()) The command string requested input or output for a device that is not on line, write enabled, or in the system's device tables. Wildcards may have been used. (User Action) Make sure that the device is on line and not write locked. Use the INSTALL command to enter the device into the system's device tables. (?SRCCOM--F--Error reading directory ()) A hardware error occurred while the directory of the indicated device was being read. Wildcards may have been used. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SRCCOM--F--File created; protected file already exists ()) A protected file exists, along with a newly created unprotected file of the same name. (User Action) List the directory, unsorted. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code with the UNPROTECT command or the PIP /Z option. (?SRCCOM--F--File not found ()) The specified input file was not found on the specified device. Wildcards may have been used. (User Action) Make sure that the command line contains no errors and that the specified file exists on the specified device. If the correct device is not mounted, mount it and reenter the command. (?SRCCOM--F--Input error ()) An attempt was made to access an input device for a comparison and a hardware error occurred. Wildcards may have been used. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (?SRCCOM--F--Insufficient memory) Not enough memory is available to hold a particular difference section. Wildcards may have been used. (User Action) See (ism_sec) for information on how to increase memory space. (?SRCCOM--F--Invalid command) An invalid command to SRCCOM was typed. (User Action) Check the valid commands for SRCCOM. Enter a valid command. (?SRCCOM--F--Invalid directory ()) An attempt was made to read a directory that is not in RT--11 format. Wildcards may have been used. (User Action) Copy the files onto an RT--11 directory device. (?SRCCOM--F--Invalid option: /x) An invalid option was found, or an option other than /MATCH was given a value. (User Action) Check for a typing error in the command line. Use only those options listed in the (sum_book) for SRCCOM. Also see the valid options for the DIFFERENCES command in the (sug_book), and specify values only for those options requiring values. (?SRCCOM--F--Invalid value specified with option: /x) An invalid value was specified in the command to SRCCOM. (User Action) Check the (sum_book) or the (sug_book) for a list of options and the range of valid values for each option. Enter the command again. (?SRCCOM--F--Protected file already exists ()) An attempt was made to create a protected file with a name already associated with an existing file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to create the new file. (?SRCCOM--F--Read error) A hardware error was reported during an input operation. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SRCCOM--F--Record too long (dev:filnam.typ)) The file contains a line which is greater than 250 characters, including the line terminator. You may be using SRCCOM to compare a binary file rather than an ASCII file. (User Action) Edit the input file to make all lines less than 250 characters. Use BINCOM to compare binary files. (?SRCCOM--F--Too many differences) More than 310 (octal) lines were found to be different when two files were compared. (User Action) Check for a typing error in the command line. A limit of 310 (octal) lines of difference is set for SRCCOM. (Note that the value specified to the /L [/MATCH] option must be <=310.) (?SRCCOM--F--Write error) The output device was full, or a hardware error occurred in writing the output file. (User Action) See (ism_sec) for information on how to increase storage space. Check the procedures for recovery from hard error conditions listed in (hec_sec). (?SRCCOM--F--Wrong version of RT--11) An attempt was made to run an RT--11 Version 5 utility (SRCCOM) on a previous version of RT--11. (User Action) Do not run RT--11 Version 5 utilities under earlier RT--11 versions. (?SRCCOM--I--No differences found) The specified files were compared and no differences were found. (User Action) This message is informational. (?SRCCOM--W--Audit trail truncated to eleven characters) The audit trail exceeded 11 characters and was truncated. (User Action) If the truncated audit trail is unacceptable, enter a new set of characters that contains 11 or fewer characters. (?SRCCOM--W--Files are different) The specified files were compared and differences were located. (User Action) This message is informational. (?SYSGEN--E--Ethernet handler support available for XM/XB, ZM/ZB only ) You requested support for an Ethernet handler (NC, NQ, or NU) while performing a SYSGEN for a monitor other than XM, XB, ZM or ZB. (User Action) You can request Ethernet handler support only when performing a SYSGEN to create an XM monitor. If you require Ethernet support, then SYSGEN for an XM monitor or use the distributed XM monitor. (?SYSGEN--E--File not found ()) The specified SYSGEN answer file was not found on the specified device. SYSGEN asks for a file name again. (User Action) Check for a typing error. Give the name of an existing SYSGEN answer file. Press the ESCAPE key for more information. (?SYSGEN--E--Invalid baud rate) The baud rate specified is invalid. (User Action) Check for a typing error. Be sure to specify one of the following bauds: 110, 150, 300, 1200, 2400, 4800, or 9600. (?SYSGEN--E--Invalid device ()) An invalid device was specified. (User Action) SYSGEN asks for another device specification. Type a question mark (?) for a list of valid device names. Respond to the SYSGEN dialog with a valid device specification. Press the ESCAPE key for more information. (?SYSGEN--E--Invalid filename: ()) An invalid file name was used to specify a SYSGEN answer file. (User Action) Try the operation again, using a valid file name. Press the ESCAPE key for more information. (?SYSGEN--E--Invalid multiplexer type) Used for DH questions. Selected an invalid DH-type multiplexer. (User Action) Select a valid DH-type multiplexer. (?SYSGEN--E--No monitor requested) A (NO) response was given to all possible monitor choices during a SYSGEN run. (User Action) SYSGEN asks again which monitors are to be built. Respond with (YES) to at least one of the monitor type queries of the SYSGEN dialog. Press the ESCAPE key for more information. (?SYSGEN--F--Error creating ()) An error occurred while the specified SYSGEN output file was being created. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SYSGEN--F--Input error ()) A hardware error occurred while SYSGEN was accessing the specified file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?SYSGEN--F--Next default CSR address out of range) SYSGEN calculated that the next default CSR address is out of range. (User Action) SYSGEN determines the default CSR address from the previous CSR address you entered. Because the next default is out of range, SYSGEN asks the questions again (restarts the query sequence) for that device. (?SYSGEN--F--Next default vector out of range) SYSGEN calculated that the next default vector address is out of range. (User Action) SYSGEN determines the default vector address from the previous vector address you entered. Because the next default is out of range, SYSGEN asks you the questions again (restarts the query sequence) for that device. (?SYSGEN--F--Protected file already exists ()) An attempt was made to open a file, using a name already associated with an existing protected file. (User Action) Use the UNPROTECT command or the PIP /Z option to change the protection level of the existing file or use a different name to open a new file. (?SYSGEN--I--Device time-out support set on) You selected multiterminal time-out support, but did not not select device time-out support. (User Action) When you receive this message device time-out support is set on. (?SYSGEN--I--Only 16. channels supported on ()) DH message -- requested too many terminals for the line. (User Action) This message is informational. (?SYSGEN--W--Address not even) SYSGEN encountered an odd number for a CSR or VECTOR address. (User Action) SYSGEN will ask for the CSR or VECTOR address again. Enter an even number. (?SYSGEN--W--Exceeded total number of valid DL11 lines) The number of local and remote lines is greater than eight. (User Action) SYSGEN asks again for the number of LOCAL and REMOTE lines. Respond to the SYSGEN dialog with a number of local and remote lines that is eight or less. Press the ESCAPE key for more information. (?SYSGEN--W--File already exists ()) The file name specified already exists. (User Action) SYSGEN asks if this file will be used or if another file name will be specified. Respond to the SYSGEN dialog. Press the ESCAPE key for more information. (?SYSGEN--W--Invalid physical device name ()) The physical device name is not one to three alphanumeric characters. (User Action) SYSGEN asks for another physical device name. Provide a valid physical device name in response to the SYSGEN prompt. Press the ESCAPE key for more information. (?SYSGEN--W--Limit of 17 terminals already reached) You attempted to select more than 17 terminals. (User Action) This message is informational. (?SYSGEN--W--Output error ()) A hardware error occurred while SYSGEN was accessing the specified file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_SEC). (System Macro Library (SYSMAC) Error Messages) Following each error message is one or more requests or macros that could produce the message and explanatory text if the message is not self-explanatory. (?SYSMAC--E--.DEBUG must be used before .DPRINT) .DPRINT (?SYSMAC--E--Expecting a single letter, found UNIT64) .DRDEF --- Letter to use for 64-unit version of the handler was incorrectly specified. (?SYSMAC--E--Invalid A D R, expecting #..., found ADR) .ADDR --- Address specified was not in the form of an immediate reference.
.CALLK --- Destination specified was not in the form of an immediate reference, and PIC was specified. (?SYSMAC--E--Invalid argument,(#0) in first argument position) .CSIGEN
.CSISPC --- First argument was specified as (#0); causes the request to be treated as a .GTLIN request. (?SYSMAC--E--Invalid C O N T R O L, found CONTROL) .DRBOT --- Expecting a possible combination of UBUS, QBUS, CBUS, UMSCP, QMSCP, or CMSCP. (?SYSMAC--E--Invalid D M A, expecting YES/NO, found DMA) .DRDEF (?SYSMAC--E--Invalid O P T I O N, expecting NO/NUM/OCT, found X) .DRSET (?SYSMAC--E--Invalid R E G, expecting Rx/@Rx/-SP, found REG) .ADDR (?SYSMAC--E--Invalid RETURN, expecting N,Z,V,C, found 'return') .CALLS (?SYSMAC--E--Invalid S I D E S, expecting 1/2, found SIDES) .DRBOT (#) (?SYSMAC--E--Invalid T Y P E, expecting GET/MOV/BIC/BIS/USER, found TYPE) .GFxxx
############.SFxxx (?SYSMAC--E--Invalid T Y P E, expecting MOV/BIC/BIS, found TYPE) .POKE
############.PVAL (?SYSMAC--E--Invalid TYPE, expecting OCT/DEC, found TYPE) .DPRINT (?SYSMAC--E--Invalid T Y P E, expecting O/R/W/M/T, found TYPE) .DRSPF (?SYSMAC--E--Invalid U N I T 6 4, expecting YES/NO, found UNIT 64) .DRDEF (?SYSMAC--E--Not at location TO) .BR (?SYSMAC--E--Odd or invalid vector specified) .DRBEG
############ .DRVTB (?SYSMAC--E--P E R M U M R value > 7) .DRDEF (?SYSMAC--E--Primary boot too large) .DREND (?SYSMAC--E--SPFUN values must be negative) .DRSPF (?SYSMAC--E--Too many different NN SPFUN codes) .DRSPF (?SYSMAC--E--U N I T 6 4 = N O and NAME'$N64 = 1) .DRDEF --- SYSGEN conditional for this handler is set for 64-unit support, but this handler does not support 64 units. (?SYSMAC--W--"A REL C" is not true) .ASSUME --- The relationship REL between A and C is not true. (?SYSMAC--W--D A T A table specified, but no T Y P E) .DREST --- Address of a data table is specified, but type of table is not specified. (?SYSMAC--W--Invalid argument, use #0, not 0) (#) Generally applicable to most system programmed requests.
.DELETE
.WAIT --- A value was specified as 0; should have been specified as (#0). (?SYSMAC--W--This operation may produce random results) .ADDR --- The user specified adding the PIC address calculated by .ADDR to the word ABOVE the stack. (?SYSMAC--W--Value specified for U C O D E, but T Y P E=TYPE) .SFINF
########### .SFSTA (?TRANSF--F--Channel in use) An internal TRANSF error occurred. (User Action) Reboot the host system and try the operation again. If the error occurs again, install a new copy of TRANSF.SAV on the host and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?TRANSF--F--Channel not open) An internal TRANSF error occurred. (User Action) Reboot the host system and try the operation again. If the error occurs again, install a new copy of TRANSF.SAV on the host and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?TRANSF--F--Conflicting option information) The /T option was specified with both the input and output file. (User Action) Use the /T option with only the input or output file specification, whichever is associated with your stand-alone system. (?TRANSF--F--Device full ()) The directory of the specified output device on the host system does not have enough room for the file name of the file being transferred. (User Action) Choose another output device for the operation or delete some files from the output device and retry the operation. (?TRANSF--F--Device in use) An attempt was made to use a nonshareable device. (User Action) Try the operation again, using another device. (?TRANSF--F--File created; protected file already exists ()) A protected file exists on the host output device, along with a newly created unprotected file of the same name. (User Action) List an unsorted directory. If the unprotected file appears before the protected file in the directory listing, either delete or rename the unprotected file. If the protected file appears first, rename it or change the protection code. (?TRANSF--F--File not found ()) The input file specified was not found on the host device specified. (User Action) Check for a typing error in the command line. Verify that the file name exists as entered in the command line and try the operation again. (?TRANSF--F--Input error ()) A hardware error occurred while TRANSF was reading from the host device. (User Action) See the procedures in (hec_sec) for recovery from hard error conditions. (?TRANSF--F--Invalid command) The command string entered is not a valid CSI or CCL command string. (User Action) Check the command line for typing errors. Reenter the command, using CSI or CCL command string syntax. (?TRANSF--F--Invalid device ()) The host device specified in a TRANSF command line is invalid. (User Action) Check for a typing error in the command line. Verify that the device specified is valid. (?TRANSF--F--Invalid file name) An invalid file name was specified in the TRANSF command line. (User Action) Check for typing error in command line. Verify that the file name specified is valid. (?TRANSF--F--Invalid option: /x) An invalid option was used in the TRANSF command line. (User Action) Check for a typing error in the command line. Use only the options listed as valid for TRANSF. (?TRANSF--F--Output error ()) A hardware error occurred while TRANSF was writing to the host device. (User Action) See the procedures in (hec_sec) for recovery from hard error conditions. (?TRANSF--F--Protected file already exists ()) A protected file already exists on the host output device with the same name as the file specified in the command. The file transfer is not processed. (User Action) Remove the protection from the existing file or use a different output file name. (?TRANSF--F--Read past end of file) An internal TRANSF error occurred. (User Action) Reboot the host system and try the operation again. If the error occurs again, install a new copy of TRANSF.SAV on the host and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?TRANSF--F--Transfer aborted) A file transfer was aborted. A (CTRL/C) was pressed, or an I/O error occurred on the host system. (User Action) If an I/O error occurred, try the operation again after hard-error recovery procedures have been performed on the host. (?TRANSF--F--Transfer aborted by remote) A file transfer was aborted due to an I/O error on the stand-alone system or through the RESET command. (User Action) See the procedures listed in (hec_sec) for recovery from hard error conditions. (?TRANSF--F--Unable to attach terminal) In a multiterminal environment, TRANSF was unable to attach the shared console because it was already attached by another job. (User Action) Remove the job that has attached the shared console and run TRANSF again. (?TRANSF--F--VTCOM not running on remote) VTCOM is not running on your stand-alone system, or the host system's response time is slow due to heavy usage and TRANSF timed out before receiving a response from VTCOM. (User Action) Run VTCOM and try the operation again. (?TRANSF--F--Wildcards not supported) An attempt was made to use a wildcard character (* or %) in a file specification for input or output. (User Action) Enter a valid RT--11 file specification for a single file. (?TRANSF--F--Write past end of file) An internal TRANSF error occurred. (User Action) Reboot the host system and try the operation again. If the error occurs again, install a new copy of TRANSF.SAV on the host and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?TRANSF--W--Transfer completed with n retries) The transfer completed, but n retries were performed. (User Action) Check the transfer output to make sure no errors were transmitted. (?UCL--F--Channel in use ()) An internal UCL error occurred while accessing the UCL data file. (User Action) Reboot your system and try the operation again. If the error occurs again, get a new copy of UCL.SAV from your distribution kit and retry the operation.
If the error persists, submit an SPR to Digital. Include with the SPR a program listing and a machine-readable source of the program, if possible. (?UCL--F--Command does not exist) An attempt was made to execute or delete a UCL command that is not in the UCL data file. (User Action) Check for correct spelling of the command. Issue the command SHOW COMMANDS and examine the contents of the data file. (?UCL--F--Command too long) The UCL command or the definition of the UCL command contains too many characters. (User Action) The UCL command cannot contain more than 16 (decimal) characters, including the asterisk. The UCL command definition cannot contain more than 128 (decimal) characters. Check the length of each. (?UCL--F--File not found ()) The UCL data file was not found. (User Action) The UCL data file is created automatically when the first UCL command is defined. Define a UCL command. (?UCL--F--Input error ()) A hardware read error occurred when UCL attempted to read the UCL data file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec). (?UCL--F--Insufficient memory available) Not enough free memory is available to run UCL. (User Action) Issue the SHOW MEMORY command. Look at the contents of memory and unload any unneeded jobs and device handlers, until enough memory is available to run UCL.SAV. (?UCL--F--Invalid command) Incorrect syntax was used when defining a UCL command. (User Action) Correct the command syntax and retry the command. The (SUG_BOOK) contains a description of UCL command syntax. (?UCL--F--Invalid format of ()) An attempt was made to access the UCL data file, and UCL found a first character other than the exclamation point (!). (User Action) The structure of the UCL data file was changed with RT--11 V5.2. Redefine your UCL commands, using the new version of UCL.SAV. (?UCL--F--Invalid number of commands) The characters following the first-character exclamation point (!) in the UCL data file do not form a valid octal number. The octal number must be in the range 1--77777. (User Action) Perform the appropriate customization patch described in Chapter 2 of the (SRN_BOOK). The customization patch will enter a valid octal number after the exclamation point in the UCL data file. (?UCL--F--No commands available in ()) The UCL data file exists but contains no UCL commands. (User Action) Define a UCL command, using the procedures described in the (sug_book). (?UCL--F--No more room in file ()) The UCL data file is full; no more UCL commands can be entered. (User Action) See Chapter 2 of the (SRN_BOOK) for information on increasing the size of the UCL data file or delete some UCL commands from the file. (?UCL--F--No room on disk for ()) The output volume does not have room for the UCL data file. (User Action) See (ism_sec) of this manual for information on increasing storage space. If you cannot use any of those techniques to increase the space available, you may be able to perform the customization patch described in Chapter 2 of the (SRN_BOOK) to reduce the size of the UCL data file. In that case, you will not be able to define as many commands. (?UCL--F--Output error ()) UCL detected a hardware error while writing to the UCL data file. (User Action) See the procedures for recovery from hard error conditions listed in (hec_sec) of this manual. (?VBGEXE--F--Cannot run in completely virtual environment ()) The program that VBGEXE attempted to load and run is not compatible with the completely virtual environment. This is signified when bit value 100 (NOVBG$) is set in location 4 (JSX$) in block 0 of the save image. (User Action) Do not try to run this program in the completely virtual environment. Use R, RUN, FRUN, or SRUN to run this program (?VBGEXE--F--Cannot run with separated I-D space ()) The program that VBGEXE attempted to load and run is prevented from running with separated I-D space because location 30 (SV.NID) in block 0 of the save file is non-zero. This is probably caused by the use of library routines that are incompatible with I-D space. (User Action) LINK your program as a non-I-D space program or do not use library routines that are not compatible with I-D space. (?VBGEXE--F--File not found ()) The file specified as the program for VBGEXE to load and run was not found. (User Action) Check for a typing error in the command line, make sure that the file exists, and retry the operation (?VBGEXE--F--Fully mapped monitor required for ()) The program that VBGEXE attempted to load and run is either in I-D space file format or specifies that it requires either supervisor mode support or I-D space support. Supervisor mode support is required whenever bit value 4 (REQSM$) is set and I-D space support is required whenever bit value 1 (REQID$) is set in location 4 (JSX$) in block 0 of the save image. (User Action) Make sure that the system includes I-D space memory-management hardware and that VBGEXE is run under a fully mapped monitor. (?VBGEXE--F--Handler not loaded ()) The handler for the user job is not loaded and VBGEXE cannot load it because VBGEXE is running as a foreground or system job. (User Action) Load the handler and retry the operation. (?VBGEXE--F--Input error ()) A hardware read error occurred while VBGEXE was loading the specified program into main memory. (User Action) Check that the device is readable and that ()) does not contain bad blocks. (?VBGEXE--F--Insufficient extended memory for virtual job region) VBGEXE was unable to allocate a virtual job region in which to load a piece of itself or in the user program. (User Action) Unload other jobs and handlers to provide more space for this job. (?VBGEXE--F--Insufficient memory for region) VBGEXE was unable to allocate a region in which to load a piece of itself or in the user program. (User Action) See Section 1.5 for information on how to increase memory resources. (?VBGEXE--F--Internal error) An internal error occurred while VBGEXE was trying to load a program. (User Action) Retry the operations that produced this error. If it occurs again, reboot your system and retry the operation once more. If the error still occurs, submit an SPR to Digital including as much information as possible about the problem. (?VBGEXE--F--Invalid I-D space file format ()) The program VBGEXE was trying to load and run appeared to be a save image in I-D space file format. However, it was inconsistent. (User Action) If you are trying to run an I-D space program, make sure that the program you are attempting to run is created without error by LINK using the /IDSPACE option. Otherwise, make sure that the program you are trying to run is an ordinary save file. (?VBGEXE--F--Mapped monitor required) VBGEXE was attempted to be run under an unmapped monitor. (User Action) Make sure that the system includes memory-management hardware and that VBGEXE is run under a mapped monitor. (?VBGEXE--F--Wrong version of RT-11) An attempt was made to run VBGEXE on an outdated version of RT-11. (User Action) Do not attempt to run VBGEXE on earlier versions of the RT-11 operating system. (?VBGEXE--W--File not found ()) The file specified as the program for VBGEXE to load and run was not found. (User Action) Check for a typing error in the command line, make sure that the file exists, and retry the operation (?VBGEXE--W--Invalid device ()) A file specification included a device () that is not present on your system because it is not installed and it is not assigned. (User Action) Verify that () is the device you want to use and either assign it to a valid device or install (). (?VBGEXE--W--Invalid file specification) The file specified as the program for VBGEXE to load and run was invalid. This is commonly caused by a typing error or a file name that is too long. (User Action) Check for a typing error in the command line, make sure that the file exists, and retry the operation. (?VHANDL--F--Window error) The file created with the linker /V option is using too many windows. (User Action) Relink, using fewer windows. (?VTCOM--E--Invalid port selection) An invalid value was entered in response to the port selection prompt. (User Action) Repeat the SELECT command and enter a valid port number in response to the port selection prompt. (?VTCOM--E--No dial string) You issued the DIAL command without specifying a dial string, and no default dial string has been set. (User Action) Retype the DIAL command. When the prompt appears, type a dial string. (?VTCOM--E--No port selected) (RETURN) was pressed in response to the port selection prompt. (User Action) Repeat the SELECT command and enter a valid port number in response to the port selection prompt. (?VTCOM--F--Clock not running ) You attempted to start VTCOM on a processor that does not have a running system clock. (User Action) Enable the system clock on your processor and restart VTCOM. (?VTCOM--F--Device full) In an OPENLOG operation or in a TRANSF file transfer from the host, the directory of the output device does not have enough room for the file name of the file being transferred. (User Action) Choose another output device for the operation or delete some files from the output device and retry the operation. (?VTCOM--F--Directory I/O error) A hardware error occurred while a directory was being read when a SEND, OPENLOG, or TRANSF operation was started. (User Action) See the procedures listed in (hec_sec) for recovery from hard error conditions. (?VTCOM--F--Fetch error ()) A serious VTCOM or internal system error occurred. The copy of VTCOM, the monitor file, or the specified device handler (XL or XC) may be corrupted on disk.
The in-memory copy of VTCOM or the monitor may have been corrupted. (User Action) Reboot the system and try the operation again. If the error occurs again, get a new copy of VTCOM and the specified device handler. Retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?VTCOM--F--File not found) The input file specified during a SEND operation or a TRANSF file transfer from your stand-alone system was not found on the volume you specified. (User Action) Check for a typing error in the command line, verify that the file name exists as typed in the command line, and try the operation again. (?VTCOM--F--Handler not loaded) The handler needed for a SEND, OPENLOG, or TRANSF operation is not loaded. (User Action) Load the handler by using the LOAD command and retry the operation. (?VTCOM--F--Handler not loaded ()) The VTCOM handler (XL or XC) is not loaded. (User Action) Load the proper handler (XL or XC) and retry the operation. (?VTCOM--F--Insufficient memory) Not enough memory is available for VTCOM to fetch the XC or XL handler. (User Action) If you are running under the XM, ZM or ZB monitor, run VTCOM.SAV rather than VTCOM.REL. Otherwise, see (ism_sec) for information on how to increase memory resources. (?VTCOM--F--Internal error) An internal error has occurred. (User Action) Run VTCOM again and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?VTCOM--F--Internal task stack overflow) An internal error has occurred. (User Action) Run VTCOM again and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?VTCOM--F--Invalid command) The command you typed is not a valid VTCOM command. (User Action) Check for a typing error in the command line. Check the list of valid VTCOM commands and command abbreviations by pressing (RETURN) in response to the (TT::VTCOM>) prompt. Try the operation again. (?VTCOM--F--Invalid device) The device specified in an OPENLOG or SEND operation, or the device on the stand-alone system in a TRANSF file transfer, is invalid. (User Action) Check for a typing error in the command line. Verify that the device specified is valid. (?VTCOM--F--Invalid device ()) The device (XC or XL) was not found in the system device tables. (User Action) Make sure XC or XL has been installed. Try the operation again. (?VTCOM--F--Invalid directory) You attempted a VTCOM operation that uses an invalid volume; for example, the volume might need to be initialized. (User Action) Make the volume a valid RT--11 volume and retry the VTCOM operation. (?VTCOM--F--Invalid file name) The file name specified for a SEND or OPENLOG operation, or the stand-alone system's file name during a TRANSF file transfer, is invalid. (User Action) Check for a typing error in the command line. Make sure the file name you specify includes only six characters in the file name and three in the file type. (?VTCOM--F--I/O error) A hardware error occurred during a SEND, OPENLOG, or TRANSF operation. (User Action) See the procedures in (hec_sec) for recovery from hard error conditions. (?VTCOM--F--Line too long) The line you typed in response to the VTCOM prompt (TT::VTCOM>) during a SEND or OPENLOG operation is too long. (User Action) Check for a typing error in the command line. Make sure the command you typed is a valid VTCOM command and make sure your response to the VTCOM prompt includes no more than 40 characters. Try the operation again. (?VTCOM--F--Lookup error ()) An error occurred when VTCOM attempted to open a channel to the XC or XL handler. (User Action) Run VTCOM again and retry the operation. If the error persists, submit an SPR to Digital. If possible, include a hard-copy listing or a summary of the console session from boot time until the error occurred. (?VTCOM--F--Protected file already exists) The file you specified for an OPENLOG or TRANSF operation already exists as a protected file on the stand-alone system volume you specified. (User Action) Use another file name or unprotect the file on the stand-alone system. Try the operation again. (?VTCOM--F--Protocol version mismatch) The versions of the VTCOM and TRANSF protocol you are using do not match. (User Action) Make sure the version of TRANSF installed on the host system was distributed with the same version of RT--11 as the version of VTCOM. VTCOM and TRANSF are distributed on the RT--11 distribution kit as matched versions. (?VTCOM--F--Timer support required) An attempt was made to run VTCOM under a single-job monitor that was built without specifying timer support during the system generation process. (User Action) VTCOM requires timer support. Perform a system generation and specify timer support. (?VTCOM--F--Unexpected EOF) The log file became full before you closed it with the CLOSE command. VTCOM closes the log file when this error occurs. (User Action) Squeeze the device on which the log file resides or use another device for the log file. (?VTCOM--F--Wrong version of ()) The version of XL or XC you are using is not the version required by VTCOM. (User Action) Make sure the version of XC or XL you are using was distributed with the same version of RT--11 as the version of VTCOM. VTCOM and its handlers are distributed on the RT--11 distribution kit as matched versions. (?VTCOM--I--Connection established) VTCOM has established a connection to a remote modem. (User Action) You can now log onto your host system. This message is informational. (?VTCOM--I--Connection lost) The connection to a remote modem has been lost. (User Action) Reestablish the connection or leave VTCOM terminal mode. This message is informational. (?VTCOM--W--File not sent, transfer in progress) A SEND command was issued while a SEND operation was already in progress. (User Action) The second SEND command is ignored. Wait until the operation in progress completes before issuing another SEND command. (?VTCOM--W--Log file closed due to I/O error) A hardware error has occurred during an OPENLOG operation. The log file has been closed. (User Action) See the procedures listed in (hec_sec) for recovery from hard error conditions. (?VTCOM--W--Log file not open) A log file was not open when a LOG or NOLOG command was issued. (User Action) Open a log file by using the OPENLOG command and reissue the command. (?VTCOM--W--Use XM version, VTCOM.SAV) You are running the FB version of VTCOM (VTCOM.REL) under XM or ZM. (User Action) Run VTCOM.SAV when you use the XM or ZM monitor. (?ZHANDL--F--Window error) The file created with the linker /V option is using too many windows. (User Action) Relink, using fewer windows. (MACRO--11 Messages\Mm_sec)
See the (mac_book) for the MACRO--11 error messages and information about MACRO--11 error conditions. (Editor and Command-Line Editing Messages\Edc_sec)
The KED/KEX error messages have been removed from this manual. Look in the separate KED/KEX documentation for explanations of all KED/KEX error messages.
For error messages displayed by the RT--11 system utility program, EDIT, see the EDIT section of the system error messages.
For command-line editing messages displayed by the RT--11 single-line (SL) editor, see the SL section of the system error messages. For some messages, SL displays the appropriate message on the current line if you press the (PF2) key (HELP) after SL sounds the terminal bell indicating an error condition. For more information, read the description of the single-line editor in the (sug_book).