(Messages) (Informative messagesSee Messages) (PromptsSee Messages) (Error messagesSee Messages) (Command level messagesSee Messages) (HELP messagesSee Messages) (Fatal error messagesSee Messages) (Warning messagesSee Messages) This appendix describes the KED messages you can encounter during a work session. (unnumbered) (messtypes_sec) describes the different types of messages. (nonrecover_sec) tells you what to do if you ever encounter a nonrecoverable condition. (filefull_sec) is for RT--11 users. It tells you what to do when an output file is full. (strange_sec) explains how you can accidentally create a lot of extraneous characters on your terminal screen. (mess_sec) lists, explains, and gives corrective actions for all the messages that KED can display. (Message Types\messtypes_sec)

KED displays three types of messages: (simple) Command level messages HELP function messages Prompts and informative messages (Command Level Messages)

Command level messages appear when your response to a system or KED prompt contains or causes an error. Such messages have the following general form. ?KED-Severity code-Text

or ?KEX-Severity code-Text

You will see only two severity codes, F or W: (2\8) (Severity Code\Meaning and KED Operation) (F\A fatal error. KED returns to your system prompt or to the KED utility prompt.) (W\A warning. KED continues executing unless you stop it.)

KEX is a virtual KED program; the severity code and text for KEX and KED messages are the same. If you see a (?KEX-Severity code-text) message, look it up in (mess_sec) under (?KED-Severity code-text). (HELP Function Messages)

When KED is displaying a file and cannot complete your function or command, it signals you by sounding a beeper or reversing the text and background on your terminal.

If that happens: (numbered) Try to determine the cause of the signal by inspecting the cursor's position or the changes that are displayed on your screen. If you need more information, press (HELP) to display a 1-line message (centered on the bottom of your screen) that will explain the signal.

You can return to your file by pressing (ENTER) or (CTRL/W). (Prompts and Informative Messages)

When KED is displaying a file, as the need arises, it also displays prompts and informative messages on the top line of your screen.

KED restores your screen when it completes an operation that is related to the prompt or informative message. For example, when you move the cursor from the beginning to the end of a very long file, KED displays (WORKING...) on the top screen line. When the cursor reaches the end of that file, KED removes the message and restores your screen. (Nonrecoverable Conditions\nonrecover_sec)

Some of the messages displayed by KED identify nonrecoverable conditions. Digital uses those messages to diagnose KED malfunctions.

If you encounter a nonrecoverable condition: (numbered) As accurately as possible, write down the message, the functions, and the commands you used before the message appeared. Save all the files you were editing (input and output files). Obtain a new copy of the appropriate version of KED from your distribution kit. (iasrsx) (simple) If you are running RT--11, copy KED.SAV or KEX.SAV. If you are running RSX--11M, copy ??? If you are running RSX--11M--PLUS, copy ??? If you are running IAS, copy ??? Using the new copy of KED, try to duplicate the functions and commands that caused the message. If the message appears again, make sure your hardware is connected and functioning properly. If your hardware is connected and functioning properly and you qualify to receive a written reply under Digital's Software Performance Report (SPR) service, follow the instructions on the SPR form. (When an RT--11 Output File Is Full\filefull_sec)

Under RT--11, KED displays a message when the file you are editing or creating becomes too large to allow more insertions during your work session.

When that happens, try one or more of the following procedures. (unnumbered) Exit and begin another work session.

KED opens a new output file when you begin another work session. In most cases, the new output file will be large enough to hold the additions you want to make.

That procedure may not be effective if your output volume is almost full or if free space on it is not consolidated. (unnumbered\-) If free space on your output volume is not consolidated, use the SQUEEZE command. If your output volume is almost full, use the next procedure or use a new output volume.

The principal disadvantage of the procedure is that the EXIT command: (simple) Closes all open files Discards the contents of the paste, line, word, and character buffers Restores KED's default settings Delete and make room for insertions.

When your output file is full and valuable text is in the paste buffer or the other buffers, you can make room for the text by deleting part of your file. Each character you delete makes room for one additional character during your work session. Use an auxiliary output file.

When your output file is full, you can split it into two files. (numbered) Use the OPEN OUTPUT command to open an auxiliary output file and the WRITE command to store as much of your output file as necessary. Use the CLOSE command to save the auxiliary output file and then delete the section of your output file that you stored in the auxiliary output file.

In most cases, you can recombine the parts of your original file in another work session. If free space is still not sufficient, use a new output volume. (When KED Seems to Insert Extraneous Characters\strange_sec)

Under rare circumstances, hardware conditions can cause extraneous characters (characters you did not type) such as [A, [B, [C, [D, or O, to appear in your text file. They appear because an overfilled buffer disrupts the stream of characters being sent to KED, and KED interprets some of them as insertions, not editing operations.

To prevent the problem, avoid unusually long bursts of automatic repeating.

To correct the problem, use keypad functions to delete the unwanted characters or use the QUIT command to end your work session without creating an output file. (Messages\mess_sec)

These messages are arranged alphabetically (according to the first letter and later characters in each message).

If you are looking for a ?KEX message, look it up as a ?KED message. (Advance char finds end of file) The CHAR or right-arrow function moved the cursor to the bottom of your file. (Your Response) Use any valid function or command. (Advance line finds end of file) The BLINE function moved the cursor to the end of your file. With line count definitions, the PAGE and SECTION functions can also cause that message. (Your Response) Use another valid function. (Advance word finds end of file) The WORD function moved the cursor to the bottom of your file or the DELWORD function deleted the last character in your file. (Your Response) Use any valid function or command. (All available learn macro buffers are active) There are no learn buffers left to use. (Your Response) Clear a learn buffer and use it. (Argument error to INCLUDE or SKIP) KED did not complete an INCLUDE or SKIP command because you specified a negative line or page count. (Your Response) Use any valid function or command. (Argument error to WRITE) KED did not complete a WRITE command because you specified a negative line or page count. (Your Response) Use any valid function or command. (Arrow command finds extremity of file) The up-arrow function moved the cursor to the top of your file, or the down-arrow function moved the cursor to the bottom of your file. (Your Response) Use any valid function or command. (Auxiliary input file not open) KED did not complete your INCLUDE command because the auxiliary input file is not open. KED closes an auxiliary input file when an INCLUDE or SKIP command processes the entire file. (Your Response) To open an auxiliary input file, use the OPEN INPUT command. Otherwise, use any valid function or command. (Auxiliary output error) KED was unable to write to the auxiliary output file, probably due to an I/O error. (Your Response) Be sure the device on which the auxiliary output file resides is available and on line. If KEX is being run as a system job, be sure the device handler for the device is loaded. (Auxiliary output file exists) You answered N to the following message. (Your Response) Use any valid function or command. (Auxiliary output file exists -- Replace (Y,N)?) The auxiliary output file you specified has the same name as an existing file on your output volume. (Your Response) To preserve the existing file, type (N) and press (RETURN).

To delete the existing file and create a new file with the same name, type (Y) and press (RETURN). (Auxiliary output file full) No more space remains in your auxiliary output file. (Your Response) Use the CLOSE command to close your auxiliary output file. Then, open another file for auxiliary output, and merge the files in another work session. Use the COPY command or the PIP utility to merge the files. (iasrsx) (simple) RT--11: Use the COPY command or the PIP utility to merge the files. RSX--11: Use the ??? command to merge the files. IAS: Use the PDS APPEND command to merge the files. (Auxiliary output file not open) KED did not complete your WRITE command because an auxiliary output file is not open. The CLOSE and EXIT commands close an auxiliary output file. The PURGE and QUIT commands discard an auxiliary output file if one is open. (Your Response) To open an auxiliary output file, use the OPEN OUTPUT command. Otherwise, use any valid function or command. (Backup char finds beginning of file) The CHAR or left-arrow function moved the cursor to the top of your file. (Your Response) Use any valid function or command. (Backup line finds beginning of file) The BLINE function moved the cursor to the top of your file. With line count definitions, the PAGE and SECTION functions can also cause that message. (Your Response) Use another valid function. (Backup word finds beginning of file) A WORD or line-feed function moved the cursor to the top of your file. (Your Response) Use any valid function or command. (Bounded search reached bound) You used a SET SEARCH BOUNDED command to limit searches to one page. Then, a FIND or FINDNEXT function moved the cursor to the top or bottom of a page without finding a character string that matches the model you specified. (Your Response) Use any valid function or command. (CHNGCASE finds end of file) In the ADVANCE mode, the CHNGCASE function changed the case of the last character in your file. (Your Response) Use another valid function or command. (Command:) You pressed (GOLD) and (COMMAND). (Your Response) Type the command you want KED to execute and then press (ENTER). (Command canceled) You pressed (CTRL/Z) or (CTRL/C) to cancel a command and the command prompt. (Your Response) Use any valid function or command. (CTRL/C entered to stop operation) You pressed (CTRL/C) to cancel a command or function. KED restores your screen and shows where the cursor moved. If you typed commands or functions while KED was displaying the (WORKING...) message, KED ignores all of them. (Your Response) Use any valid function or command. (CTRL/C or CTRL/Z ignored -- use QUIT) While you are working in a file (no prompts are displayed, no operation is being performed), KED ignores CTRL/C and CTRL/Z. (Your Response) To insert CTRL/C or CTRL/Z in your file, use the SPECINS function.

To end your work session without saving any open output files, use the QUIT command. (CTRL/U finds beginning of file) The CTRL/U function deleted the first character in your file. (Your Response) Use any valid function or command. (Cursor not at target) With no selected text, KED did not complete a CUT, APPEND, PASTE, or SUBSTITUTE function, because the cursor is not at a valid search target. (Your Response) Use any valid function or command. (DELCHAR finds end of file) The DELCHAR function deleted the last character in your file. (Your Response) Use any valid function or command. (DELEOL finds end of file) The DELEOL function deleted the last character in your file. (Your Response) Use any valid function or command. (DELETE finds beginning of file) The Delete function deleted the first character in your file. (Your Response) Use any valid function or command. (DELLINE finds end of file) The DELLINE function deleted the last character in your file. (Your Response) Use any valid function or command. (Empty select range specified to CHNGCASE) After using the SELECT function, you used the CHNGCASE function or pressed (CTRL/L) or (CTRL/U) before selecting text. (Your Response) Press (SELECT), move the cursor to select the letters you want to change, and then use the CHNGCASE, GOLD L, or GOLD U function. (End of file reached on auxiliary input file) A SKIP or INCLUDE command read to the bottom of your auxiliary input file, and KED closed that file. (Your Response) Use any valid function or command. (EOL finds beginning of file) The EOL function moved the cursor to the top of your file. (Your Response) Use any valid function or command. (EOL finds end of file) The EOL function moved the cursor to the bottom of your file. (Your Response) Use any valid function or command. (Error reading auxiliary input file) KED did not read the auxiliary input device. The problem is not due to reaching the end of the file on that device. (Your Response) If the file name was correct, check that the device is on line and contains the proper volume. Use another device if the device is faulty. (Error writing auxiliary output or journal file) KED may have detected a bad block or a faulty device. (Your Response) Check that your device is on line and write enabled. Check that your volume is properly formatted. Try using another auxiliary output device or volume. Use the DIRECTORY/BADBLOCKS command to check for bad blocks. (iasrsx)

RT--11: Use the DIRECTORY/BADBLOCKS command to check for bad blocks.

RSX--11: Use the ??? command to check for bad blocks.

IAS: Use the ??? command to check for bad blocks. (Error un/nesting input modes) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (EXIT stopped by CTRL/C) You pressed (CTRL/C) twice to cancel an EXIT command. The results are unpredictable because they depend on: (simple) Your output file size The speed of your hardware components When you pressed the last (CTRL/C) (Your Response) If KED displays its command prompt again, you were too late in canceling the EXIT process. In that case, your output files are saved. If you specified automatic backup of your input files, they are renamed.

If KED restores your screen with the part of your input file that contains the cursor, you were not too late in canceling the EXIT process. In that case, continue editing by using any valid function or command. (File full during FILL) KED did not complete your FILL command or function because the output file or temporary file is full. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ??? (File full during INCLUDE) KED did not complete your INCLUDE command because your output file is not large enough for the text you want to copy. The cursor is to the right of the last character KED copied from your auxiliary input file. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ???

You can also use the CLOSE or QUIT command and any functions or commands that delete text from your input and output files. (INCLUDE finds end of auxiliary input file) Your INCLUDE command copied the last character in the auxiliary input file to your document file. KED closed the auxiliary input file. (Your Response) Use another valid function or command. (Insert failure in LOCAL) You pressed (CTRL/C) to stop the processing of a LOCAL command, there is not enough space in the output file, or KED did not finish processing for some other reason. (Your Response) End your work session, begin it again and try another LOCAL command. Correct any erroneous local symbols in the current LSB. Delete any ^A and ^D markers left by the LOCAL process. (Insert finds file full) KED did not insert the character you typed because your output file is not large enough. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ???

You can also use the CLOSE or QUIT command or any functions or commands that delete text from the file. (Invalid command) You entered a command that KED could not accept. (Your Response) Use any valid function or command. (Invalid definition of PAGE or SECTION) KED did not process your SET PAGE or SET SECTION command for one of the following reasons. (simple) Your marker was not enclosed by single quotes or double quotes. Your marker was enclosed by invalid delimiters. In your line count definition, you did not specify a value greater than zero. (Your Response) Use any valid function or command. (Invalid file specification) The file specification you typed in an OPEN INPUT or OPEN OUTPUT command was not valid. (Your Response) Reenter the command, using a valid file specification. (Invalid frequency value) You entered an invalid number for the SET FREQUENCY command. Valid numbers are 0--511 (0 turns off frequency limit). Repeat the command and enter a valid frequency number. (Invalid function) KED did not recognize the function you used and did not insert the characters you typed. The most common cause is pressing (ESC) (escape) and then typing almost any other key(s) on your keyboard or keypad. (Your Response) To insert an escape character or another character you cannot insert directly, use the SPECINS function.

You can also use any valid function or command. (Invalid learn macro name) You attempted to assign a name of other than one alphabetic character to a learn macro. (Your Response) Assign only a single alphabetic character as a learn buffer name. (Invalid nesting of learn commands) You attempted to nest learn commands, which is not allowed. (Your Response) Terminate the first learn command before issuing another. (Invalid parameter to ADJUST) In your TABS ADJUST command, you specified an adjustment that is outside the range of -50 to +50. (Your Response) Reenter the command, using the correct adjustment, or use another valid command or function. (Invalid parameter to LOCAL) In your LOCAL command, you specified a starting value or increment that is 0 or greater than 32767. (Your Response) Reenter the command, using the correct starting value or increment, or use another valid command or function. (Invalid right column for wrap) You specified a right margin greater than 256 in your SET WRAP command. (Your Response) Reenter the command, using the correct right margin, or use another valid function or command. (Invalid tab indent value) You specified an indentation value of 0 or less in your SET TABS command. (Your Response) Reenter the command, using the correct indentation value, or use another valid function or command. (Invalid terminating key) KED did not complete your FIND function because: (simple) You included an invalid character in your model. or You did not press (ADVANCE) or (BACKUP) to enter your model. (Your Response) Use any valid function or command. (Invalid terminating key to command prompt) KED did not process your command because: (simple) You included an invalid character in your command. or You did not press (ENTER) after typing your command. (Your Response) Use any valid function or command. (Invalid to insert null) You typed (GOLD) 0 (GOLD) (SPECINS), hoping to insert a null character. (Your Response) Do not try to insert a null character. Use another valid function or command. (I/O error closing auxiliary output file) KED did not write to your auxiliary output file during a CLOSE operation. KED may have detected a bad block. (Your Response) Try using another auxiliary output volume. Use the DIRECTORY/BADBLOCKS command to check for bad blocks. (iasrsx)

RSX--11: Use the ??? command to check for bad blocks.

IAS: Use the ??? command to check for bad blocks. (Journal output file full. Journaling terminated.) No more room remains in the journal output file. (Your Response) Exit from the work session and start a new work session if you wish to continue journal file protection. You can continue with the current work session but will not have journal file protection. (Journal file output error -- Exist session (Y/N)?) KED encountered an I/O error while writing to the journal file. The error was not a file full error. (Your Response) Type (Y) and press (RETURN) to exit from the work session and guarantee preservation of your text file. Type (N) and press (RETURN) to continue the work session without the protection of a journal file.

In either case, examine the condition of the journal output device. For example, perform a DIRECTORY/BADBLOCKS operation to examine it for bad blocks. (Journal output file full -- Exit session (Y/N)?) The allocated space for the journal file is full. (Your Response) Type (Y) and press (RETURN) to exit from the work session and guarantee preservation of the text file. Type (N) and press (RETURN) to continue the work session without the protection of a journal file. (Journal preliminary buffer overflow -- Exit session (Y/N)?) The temporary journal file buffer is full. (Your Response) Type (Y) and press (RETURN) to exit from your work session and guarantee preservation of your text file. Type (N) and press (RETURN) to continue your work session without journal file protection. (?KED--F--Bad call to .VVV.V) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--File name conflict) You entered a command line in which the journal file and output file have the same file specification. (Your Response) Rename either the journal file or the output file (typically, the journal file). (iasrsx) (?KED--F--Illegal command line) ??? (Your Response) ??? (?KED--F--Illegal file specification) KED may have malfunctioned or ??? (Your Response) Refer to (nonrecover_sec) or ??? (?KED--F--Insufficient memory) KED:

KED cannot run, because too little memory is available (approximately 16K words are required) or KED may have malfunctioned.

KEX:

There is not enough available memory. Or you applied a customization (described in the (ins_book)) to limit the amount of memory KEX requests with a .SETTOP, but the amount of memory you specified was too small. (Your Response) KED:

Switch to a system that provides more memory or switch to a smaller RT--11 monitor. In the (msg_book), the section entitled Increasing Storage and Memory Resources offers other suggestions that may be useful. If the message continues to appear, refer to (nonrecover_sec).

KEX:

Reapply the KEX customization, specifying a larger value for the highest address KEX requests with a .SETTOP. (iasrsx)

RSX--11 and IAS: Make sure KED was properly built and installed and that there is a large enough task size increment. If the message continues to appear, refer to (nonrecover_sec). (?KED--F--Invalid device) Your input or output device is not random access. The message does not apply to auxiliary files, which can reside on sequential-access devices. (Your Response) Use a random-access device for your input and output files. (?KED--F--I/O or device error -- Continue (Y,N)?) One of the following situations can cause that message. (simple) Your device was switched off line. Your output device was write locked. Your volume has a bad block. (Your Response) Before responding, check that your device is on line. If it is an output device, check that it is write enabled.

To try the same function or command again, type (Y) and press (RETURN). If the function or command works, continue editing. If the function or command does not work or if you type (N) and press (RETURN), KED quits without saving your work and returns to the system prompt. (?KED--F--Journal not allowed with inspect mode) You have requested a journal file when opening a file for inspection, which is not allowed. (Your Response) Reenter the command without requesting a journal file. (?KED--F--Output file shorter than input file) The space available for your output file is smaller than your input file, or there may not be enough space on your volume. (Your Response) Use the SQUEEZE command to consolidate free space on your output volume or use a different volume. (iasrsx)

RSX--11 and IAS: Specify the output file size correctly or use the default. (?KED--F--RDBKW -- No space to read into) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--RDFWD -- No space to read) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--RDFWD -- Pointer corrupt) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--SETUP -- Allocation error) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--SPCFRE -- Logic error, character count wrong) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--Temporary file shorter than input file) The number of blocks you specified with a /BL option is less than the size of your input file. (Your Response) Reenter your command with a temporary file size that is greater than the input file size. (?KED--F--Too big to edit) Your input file is too large. KED cannot edit or inspect a file that is larger than 32767 blocks. That restriction does not apply to auxiliary files or devices. (Your Response) Split your file into two or more parts, using auxiliary output files, and edit each part separately. (?KED--F--TTY??? Logic error) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--Unable to access input device) KED did not access your auxiliary device for one of the following reasons. (simple) Your device is invalid, not ready, or not installed. The volume on your device has too many bad blocks. There is no room for the device handler. (Your Response) Check your device abbreviation. If it is correct, check that the device is on line (use the SHOW/DEVICES command). If necessary, use the INSTALL command to install the device. If the message appears again, use the DIRECTORY/BADBLOCKS command to check the volume for bad blocks. If there are too many bad blocks, use another volume. If you cannot install the handler for the device, try the suggestions listed for ?KED--F--Insufficient memory. (iasrsx)

RSX--11 and IAS: Correctly specify the input device. ??? (?KED--F--Unable to access output device) KED did not load the output device handler. (Your Response) If your device name is correct, check that your system volume contains the device handler. If the message appears again, try the suggestions listed for ?KED--F--Unable to access input device. (iasrsx) (?KED--F--Unable to attach terminal) KED cannot attach your terminal and therefore cannot proceed. (Your Response) Check with your system manager.

[What should the user of a standalone system do??? That person is also the "system manager".] (iasrsx) (?KED--F--Unable to copy temporary file) After you use the EXIT command, your system cannot properly convert KED's temporary file. Your system locks the temporary file and the output file. (Your Response) RSX--11: If you want to salvage the locked temporary file or locked output file, use the PIP UNLOCK command described in the (rsxum_book).

IAS: If you want to salvage the locked temporary file or locked output file, use the PIP UNLOCK command described in the (iasum_book) or use the PDS commands UNLOCK and SET END-OF-FILE described in the (iaspds_book). (?KED--F--Unable to create output file) RT--11:???

RSX--11: You specified an output file that was opened by another user, your input and output file specifications are the same, or your output volume does not have enough free space.

IAS: ??? (Your Response) RT--11: ???

RSX--11: ???

IAS: ??? (?KED--F--Unable to create temporary file) KED cannot create a temporary file on your output volume and in the directory you specified. That can be caused by one of the following. (simple) A protection violation Too little space on your output volume An I/O error (Your Response) Check that your output device is on line and write-enabled. Check that your output volume contains enough free space. Check that the current UIC has the correct file protection attributes. (?KED--F--Unable to edit input file) Your input file is too long. KED cannot edit a file that is larger than 16383 blocks. (Your Response) Split the file into two or more parts, using auxiliary output files, and edit each part separately. (?KED--F--Unable to open input file) KED did not open your input file for one of the following reasons. (simple) Your volume does not contain that file. Your volume was not initialized. Your input device is not on line. (Your Response) Check your file specification. If it is correct, check that the correct volume is installed and that the input device is on line. (?KED--F--Unable to open output file) KED did not open your output file for one of the following reasons. (simple) Your device is not ready or is write locked. Your volume was not initialized. Your volume does not have enough free space for the output file. Your output file is protected. (Your Response) Make sure your output volume is properly installed and initialized. If that volume is too full, use another volume. To edit a protected file, use a different output file specification. (?KED--F--Unable to rename recover file to JBK file type) You specified a journal file and a recover file of the same name. KED attempted to rename the recover file to type JBK, but failed, because a protected file of that name and type exists. (Your Response) Determine if the existing protected backup (JBK type) recover file is needed. If it is needed, unprotect it and rename it to a different file type (for example, OLD). Retry the operation. (?KED--F--Unable to trim output file) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (iasrsx) (?KED--F--Unable to truncate or close output file) ??? [See (rsx_ax).] (Your Response) ??? (?KED--F--WRBKW -- Bad block number) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--WRBKW -- Block overrun) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--WRBKW -- Plygnd not empty) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--WRFWD -- Bad block number) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--WRFWD -- Block overrun) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--WRFWD -- Not enough data) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (?KED--F--Wrong version of RT--11) You attempted to run a version (release) of KED that is not the same as the version (release) of RT--11 on your system. (Your Response) Replace the version of KED you are running with the version supplied on your current RT--11 software distribution. (?KED--W--Command file not found -- Continue (Y,N)?) KED did not find the command file on the volume you specified. (Your Response) Make sure you typed the input volume name and command file name correctly. To continue your work session, type (Y) and press (RETURN). (?KED--W--File not found -- Create it (Y,N)?) KED did not find your input file on the volume you specified. (Your Response) To continue your work session, type (Y) and press (RETURN). KED will create the file you specified on the volume you specified.

To end your work session, type (N) and press (RETURN). Then correctly type the input volume name and file name. (iasrsx) (?KED--W--Input file not properly closed -- Continue (Y,N)?) KED found conflicting information ??? about your input file. (Your Response) To continue your work session, type (Y) and press (RETURN). KED will try to read your file, but it may contain invalid text that you will have to delete. If text at the end of your file appears to have been deleted because the end-of-file symbol appears earlier than expected, your file may contain a record that is too long for one of KED's buffers.

To end your work session and avoid confusion, type (N) and press (RETURN). (?KED--W--Journal file exists -- Replace (Y/N)?) On the command line, you have requested the opening of a journal file that already exists. (Your Response) Type (N) and press (RETURN) to quit the work session; no output file or journal file is created, thereby preserving the existing journal file. Type (Y) and press (RETURN) to create a new journal file by replacing the existing file of the same name. (?KED--W--Journal file size below minimum -- Continue (Y/N)?) Because of a lack of free space on the journal file output volume, the journal file is smaller than the default (50(10) blocks) or set size. (Your Response) Type (Y) and press (RETURN) to continue the work session with a smaller journal file size; the journal file may fill quickly. Type (N) and press (RETURN) to stop the work session. Perform a SQUEEZE operation on the journal file output volume or assign the journal file to a larger output volume and restart the work session. (?KED--W--Only MMMMMM blocks available for insertions -- Continue (Y,N)?) Free space on your output volume is less than 10 blocks larger than your input file. The message reports the number of blocks available. (Your Response) To continue your work session, type (Y) and press (RETURN). KED will signal you when your input file becomes as large as possible. To cancel your work session and return to the system prompt, type (N) and press (RETURN). Then use the SQUEEZE command to consolidate free space on your output volume, or specify an output volume that has more free space. (iasrsx)

RSX--11 and IAS: ??? (?KED--W--Only nnnnnn blocks available for journal file -- Continue (Y,N)?) Free space on your output volume for creating the journal file is less than 10 blocks. (Your Response) Type (N) or (Y) and press (RETURN) to cancel journaling.

If you type (Y), you continue the work session without journal file protection.

If you type (N), you are then asked if you want to continue the work session. Then type (Y) and press (RETURN) if you wish to continue the work session without journal file protection. Type (N) and press (RETURN) if you wish to cancel the work session. Then use the SQUEEZE command to consolidate free space on your output volume, or specify an output volume that has more free space. (iasrsx)

RSX--11 and IAS: ??? (?KED--W--Output file exists -- Continue (Y,N)?) Your output file name is the same as the name for a file on your output volume. (Your Response) To preserve the existing file and return to the system or KED prompt, type (N) and press (RETURN).

To delete the existing file and create a new file with the same name, type (Y) and press (RETURN). (?KED--W--Output file or device protected -- Inspect (Y,N)?) KED discovered one of the following. (simple) The output file you specified for creating or editing exists as a protected file. The input file you specified for editing is protected. Your output device is write protected. (Your Response) To continue by inspecting the file you specified, on the device you specified, type (Y) and press (RETURN).

To end your work session, type (N) and press (RETURN). (?KED--W--Output files purged) You used the QUIT command. If an auxiliary output file was open, KED does not save it. If you were editing or creating a file, KED does not save any of your work. (Your Response) Use any valid command or function. (?KED--W--Recover file not found -- Continue (Y/N)?) You specified a journal recovery operation and KED did not find the recover file on the specified (or default) volume. (Your Response) Type (N) and press (RETURN) to return to the monitor or KED utility prompt. Determine where the required recover file resides and retry the operation. Type (Y) and press (RETURN) to continue the work session without performing the journal file recovery operation.

If you continue the work session and exit from the text file, creating a new output file, you cannot subsequently perform a journal file recovery operation on that file. (?KED--W--Unable to open journal file -- Continue (Y/N)?) KED was unable to open the journal file on the default or specified volume. (Your Response) Check that the journal file output volume is available and on line. If running KEX as a system job, check that the volume's device handler is loaded. Retry the operation. (?KED--W--Unable to rename input file to BAK file type) Your input file was not saved with the BAK file type, but KED attempted to save your output file. (Your Response) If you do not have another copy of your input file, you cannot recover it. You must use your output file if it exists. (?KED--W--Unable to set terminal characteristics -- Continue (Y,N)?) You are running KED on a multiterminal system, and your terminal was attached (.MTATCHed) by another job. KED now requires that you enter the command SET TERM NOCRLF. (Your Response) To continue your work session, type (Y) and press (RETURN). To end your work session, type (N) and press (RETURN). When KED returns to your system prompt, enter the command SET TERM NOCRLF. Then begin another work session. (iasrsx) (?KED--W--Unable to truncate or close output file) RT--11: ???

RSX--11: After you used the EXIT command, the system did not properly store your output file. The system locked that file because it may be faulty.

IAS: ??? (Your Response) RT--11: ???

RSX--11 and IAS: If you want to salvage the locked output file, use the PIP UNLOCK command, described in the (rsxum_book) or the (iasum_book). (LOAD command is invalid in LEARN mode) You attempted to define two macros at the same time. (Your Response) Finish the LEARN operation before loading another macro (Learn buffer full) The functions and commands you typed since you entered the LEARN command have too many bytes (characters) for the macro buffer. KED stops storing your macro in that buffer. (Your Response) Do not use unnecessary ADVANCE or BACKUP functions. Use abbreviations for commands, and use the shortest possible search strings. Other suggestions appear in (macro_chap). (func_ax) shows the minimum number of bytes (characters) required for each function and command. (Learn macro already exists) You attempted to assign an identifier to a learn buffer that is already assigned. (Your Response) Choose another identifier or clear the existing learn buffer and reuse it. (Local symbol definition too long) In processing your LOCAL command, KED detected a local symbol that is more than six digits long. (Your Response) Check that the local symbol is correct. (Logic error in ADJUST) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in CHNGCASE) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in CUT) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in FILL) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in PASTE) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in SUBSTITUTE) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in undelete) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in undelete setup) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Logic error in WRITE SELECT) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Model:) You pressed (GOLD) and (FIND). (Your Response) Type the character or character string you want KED to search for, and then press (ADVANCE) or (BACKUP). Your search string can be up to 60 characters long. (Model prompt canceled) You pressed (CTRL/Z) or (CTRL/C) to cancel a model (search target) and the model prompt. (Your Response) Use any valid function or command. (Move failure in LOCAL) You stopped the processing of your LOCAL command by pressing (CTRL/C), or KED did not finish processing that command for some other reason. (Your Response) If you stopped the LOCAL command processing, you can use any valid function or command. If KED did not finish the processing for some reason, end your work session, begin it again, and try another LOCAL command. Correct any erroneous local symbols in the current LSB. Delete any ^A and ^D markers left by the LOCAL process. (Move PAGE or SECTION finds extremity of file) A PAGE or SECTION function moved the cursor to the top or bottom of your file. (Your Response) Use any valid function or command. (Move to bottom when at bottom) The BOTTOM function is not valid when the cursor is at the bottom of your file. (Your Response) Use any valid function or command. (Move to top when at top) The TOP function is not valid when the cursor is at the top of your file. (Your Response) Use any valid function or command. (Nesting error) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (No journal file open) You entered a command that applies to journaling, such as SET FREQUENCY, and journaling is not being used with this work session. (Your Response) If you thought you were keeping a journal file, exit from your work session and restart the session with journaling. (No macro by that name to execute) You did not use a LEARN command to define the specified macro, or the specified macro failed while you were defining it. (Your Response) Use the LEARN command to define the specified macro. (No macro by that name to save) You did not use a LEARN command to define the specified macro, or the specified macro failed while you were defining it. In either case, the specified macro does not exist to be saved. (Your response) Use the LEARN command to define the specified macro and retry the save operation. (No macro to execute) The macro buffer is empty. You did not use a LEARN command to store your macro, or the last macro you tried to store failed while you were defining it. (Your Response) Use the LEARN command to store the macro you want to use. (No model defined) KED did not process a FINDNEXT, REPLACE, or SUBSTITUTE function, because you did not specify a search string. (Your Response) To search for a character string, press (GOLD) and (FIND), type the string, and then press (ADVANCE) or (BACKUP).

You can also use any other valid function or command. (No room for this level of nesting) You have attempted to nest more than three macros and KED allows a macro nesting depth of three. (Your Response) Do not nest macros beyond the third level. (No select range defined) You used a REPLACE, APPEND, or CUT function without selecting text, and the cursor was not located at a search target. (Your Response) Use any valid function or command. (No select range defined for FILL) You did not select text or you were not selecting text before you used the FILL function or command. (Your Response) Select the text you want to reformat before using the FILL command or function. (No select range for ADJUST) You did not select text, or there are no characters in the part you selected before using the TABS ADJUST command. (Your Response) Select the text you want to adjust before using the TABS ADJUST command. (No select range for WRITE SELECT) You used the SELECT function and then entered the WRITE SELECT command, but there are no characters in the part you selected. (Your Response) Select all the text you want to copy to your auxiliary output file, and then enter the WRITE SELECT command. (Not enough file space to do PASTE) KED did not complete a PASTE function, because your output file is not large enough for the text in the paste buffer. The cursor is to the right of the last character KED copied from that buffer. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ???

You can also use the EXIT or QUIT command or any functions or commands that delete text from your file. (Not enough space to undelete) KED did not complete an UNDELLINE, UNDELWORD, or UNDELCHAR function, because your output file is not large enough for the additional text. The cursor is to the right of the last character KED copied. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ??? (Nothing to undelete) KED did not process an UNDELLINE, UNDELWORD, or UNDELCHAR function, because the line, word or character buffer is empty. (Your Response) Use any valid function or command. (OPENLINE finds file full) KED did not process an OPENLINE function, because your output file is not large enough for a carriage return and line feed. (Your Response) See (filefull_sec). (iasrsx)

RSX--11: ???

IAS: ??? (Operation is invalid during inspect) While you are inspecting a file, you attempted an operation or command that would modify the file. KED cannot complete functions or commands that modify the file. (Your Response) Use another function or command to move the cursor or end your inspection. (Repeat:) You pressed (GOLD) and typed a number on your keyboard. It indicates you are using the repeat function to repeat an editing operation or the special insertion function to insert a character you cannot insert directly. (Your Response) To complete the special insertion function, press (GOLD) and (SPECINS). To complete the repeat function, press one or more of the other keypad keys (including (GOLD), but not ()). (Saveset error) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Search canceled) You pressed (CTRL/C) or (CTRL/Z) to cancel the FIND function and (Model:) prompt. (Your Response) Use any valid function or command. (Select range too large to CUT) KED did not complete a CUT or APPEND function, because the paste buffer is not large enough for all the text you want to store. (Your Response) Select smaller sections of text, or use auxiliary output and input files for the same purpose as the CUT, APPEND, and PASTE functions.

You can also use any valid function or command. (TAB indent value wrong for align) You tried to use the A function, but the column number of the cursor's position is not evenly divisible by your indentation setting. (Your Response) Check that the cursor's position and your indentation setting are correct. Then, use the A function again. (Tabs not enabled for ADJUST) You used the TABS ADJUST command before using the SET TABS command. (Your Response) Enable structured tabs with the SET TABS command, and then use the TABS ADJUST command. (Target not found) A FIND or FINDNEXT function moved the cursor to the top or bottom of your file without finding a character string that matches the string you specified. (Your Response) Use any valid function or command. (Too many arguments for command) KED did not recognize your command, because you added extra characters after the last valid word or argument in the command. (Your Response) Use any valid function or command. (Unable to access auxiliary device) KED did not access your auxiliary device for one of the following reasons. (simple) Your device is invalid, not ready, or not installed. The volume on your device has too many bad blocks. There is no room for the device handler. (Your Response) Check your device abbreviation. If it is correct, check that the device is on line (use the SHOW/DEVICES command). If necessary, use the INSTALL command to install the device you need. If the message continues to appear, use the DIRECTORY/BADBLOCKS command to check the volume for bad blocks. If there are too many bad blocks, use another volume. If you cannot install the handler for the device, try the suggestions listed for ?KED--F--Insufficient memory. (iasrsx)

RSX--11 and IAS: Correctly specify your input device. ??? (Unable to close auxiliary file) KED did not close your auxiliary output file. Your output device may have caused the problem, or KED may have malfunctioned. (Your Response) Check that your output device is on line. You can also try the suggestions listed for Unable to access auxiliary device (above).

If the message continues to appear, see (nonrecover_sec). (Unable to delete mark) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Unable to delete target) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Unable to insert tab) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Unable to open auxiliary input file) KED did not open your auxiliary input file for one of the following reasons. (simple) Your volume does not contain that file. Your volume was not initialized. Your device is not ready. (Your Response) Check your file specification. If it is correct, check that the correct volume is installed and that your auxiliary input device is on line. (Unable to open auxiliary output file) KED did not open your auxiliary output file for one of the following reasons. (simple) Your volume was not initialized. Your device is not ready. Your device is write locked. (Your Response) Check that the auxiliary output volume is initialized. Also check that the auxiliary output device is on line and write-enabled. (Unable to replace symbol) KED may have malfunctioned. (Your Response) See (nonrecover_sec). (Undelete buffer full) KED did not complete a DELLINE or DELWORD function because: (simple) You tried to delete more than the capacity of the line buffer, 132 characters. or You tried to delete more than the capacity of the word buffer, 80 characters. (Your Response) Use repeated DELLINE or DELWORD functions (and ignore the error signals), or use the paste buffer or auxiliary files.

You can also use any valid function or command. (Use the SET HELP command to enable help screens) You pressed the help key (PF2) and the help screen is disabled from issuing the SET NOHELP command. (Your Response) If you wish to view the help screens, first issue the SET HELP command and then press (PF2). (Valid start of LSB not found) No global symbol or .ENABL LSB directive exists between the cursor's position and the preceding form-feed character or the top of your file. (Your Response) Make sure the cursor is in the first page of an LSB before you use the LOCAL command. (WORKING...) When an operation requires more than the usual amount of time, KED flashes that message at the top of your terminal screen until the operation is completed. The length of your file, the device you are using, and the function you are using determine when that message appears. (Your Response) Wait until the operation is completed, unless you want to stop it by pressing (CTRL/C) twice. (WRITE finds end of file) Your WRITE command copied the last character in your input file to the auxiliary output file. (Your Response) Use any valid command or function.