(RSX--11 operating system procedures) (Operating system proceduresRSX--11) (ProceduresRSX--11 operating system) This appendix describes procedures that are specific to RSX--11M and RSX--11M--PLUS operating systems. (RSX--11M Systems)

??? (Installing KED)

The system prompt for RSX--11M is: (simple) A right-angle bracket ((>)) or The characters MCR followed by a right-angle bracket ((MCR>)) (System Requirements)

You will need approximately 620 blocks of free space on your system volume.

Your system must be generated with the full-duplex terminal driver, and that driver must include support for Get Multiple Characteristics and Set Multiple Characteristics.

If you are uncertain about how your system was built, ask your system manager. If you are responsible for building your system, refer to the installation instructions in the (rsxmsg_book).

Your terminal must be identified by the following command. (SET /VT100=TI:(Return)) (Terminal Requirements)

Your terminal must be set for type-ahead.

To set VT100 terminal characteristics, use the SETUP A and SETUP B modes. Refer to your (vtug_book) for detailed instructions about the SETUP modes.

To set VT??? terminal characteristics, ???

For some terminals, you can choose the block cursor or the underline cursor. Examples in this document show the underline cursor.

You can run KED with your terminal set for the ANSI mode. When you exit KED, your terminal will be set for the ANSI mode. (Installation Procedures)

Each of the following procedures consists of two steps. (numbered) Copying files from your distribution volume to your system volume. Executing an indirect command file supplied by DIGITAL to task build KED.

In each procedure, (dev) is the device abbreviation and unit number for your distribution volume. (Procedure for Disks) (MCR>)(MOU dev:KEDRSX(Return)) (MCR>)(PIP SY:/NV=dev:[30,15]*.*(Return)) (MCR>)(DMO dev:(Return)) (MCR>)(@KEDBLD(Return)) (Procedure for Magtape)

For 1600 bits/inch magtape, add the /DNS:1600 option to the second command line. (MCR>)(ALL dev:(Return)) (MCR>)(FLX SY:/RS=dev:[30,15]*.*/DO(Return)) (MCR>)(DEA dev:(Return)) (MCR>)(@KEDBLD(Return)) (Verifying Your Installation)

To verify that KED operates correctly, you can work through the example provided in (session_ax). That example tells you how to edit SAMPLE.KED, a file included in your distribution kit. (Before Using KED) (numbered) Check that KED was installed. Complete the (rsxmbg_book). Complete the sections of (rsxmin_book) that cover file specifications and default storage volumes. (Running KED)

This section tells you how to run KED on all RSX--11M systems, as well as on RSX--11M--PLUS systems when you are using the MCR command line interpreter (CLI). On RSX--11M--PLUS systems you can also use the DIGITAL command language (DCL) EDIT command as described in (runplus_sec).

You can run KED on RSX--11M and RSX--11M--PLUS systems in two ways: (numbered) By calling KED directly with the task name KED, if KED was installed as an RSX--11 utility By using the RSX--11 MCR command RUN and specifying KED

If you call KED directly with the task name KED and include a file specification string in your call, KED returns you to the MCR level when you end your work session. Any special settings you made and anything you stored in KED's buffers are lost.

If you use the MCR RUN command, KED returns you to its file specification string level and displays (KED>) when you end your work session. Any special settings you made and the contents of KED's buffers are preserved for your next work session. You can begin another work session session by completing another file specification string, or you can return to the MCR level by pressing (Ctrl/Z). Your settings and the buffer contents are lost only when you respond to (KED>) by pressing (Ctrl/Z).

With KED installed in your system, you can also call KED directly with the task name KED without including a file specification string. That case is the same for the RUN command.

The following sections describe the two most common methods of running KED. The descriptions assume that your system library device LB contains KED or that KED is one of your installed utilities. Refer to the (rsxpmcr_book) for full descriptions of the RUN command and MCR procedures. That document also tells you how to use the MCR INS command to install KED. (Startup Default Values) (2\20) (Item\Default) (Input and output UIC\The LOGON UIC. Use the SET /UIC command or the /UIC option for the RUN command to specify a different default.) (Input and output volume\The volume in default device SY. Use the ASN command to assign logical name SY to different devices.) (Input file name and type\No default; must be specified.) (Output file name and type\When creating a new file from an existing file, must be specified. When creating a new version of a file, KED uses the input file name and type.) (Input file version\The latest version of the input file on the input volume) (Output file version\When creating a new file, KED assigns version 1. Otherwise, KED assigns a version number that is 1 plus the version number of the latest version on the output volume.) (Output file protection\When creating a new file, the default file protection. When editing a file, KED sets the output file protection to match the input file protection. The (rsxum_book) tells you how to change your file protection.) (Output file carriage control attribute\When creating a new file, KED assigns the implied carriage control attribute. Otherwise, KED assigns the input file attribute.) (Size of temporary file\The size of the temporary file limits the amount by which you can increase the size of your input file in one work session. When you create a new file, the default size of the temporary file is 50 blocks. Otherwise, the default size is 50 blocks larger than the input file.) (Calling KED with the Task Name KED)

With KED installed in your system, you can call KED directly by typing the task name. The two forms of the call are: (KED file-specification-string[/options](Return))

or (KED(Return))

When you use the first form, the file specification string you type specifies one of the following editing processes and KED starts immediately. (unnumbered) Storing a new version of a file and using the original file name Inspecting a file Creating a new file Storing a new version of a file and using a new output file name

The different file specification strings and options are described in the following sections.

When you use the second form, KED displays (KED>). Respond to that prompt by typing one of the file specification strings and options described in the following sections.

RSX--11 systems use the input file with the highest version number and store the output file with the next higher version number.

Although your system and KED accept an explicit output file version number, by using one you may accidentally reduce the security of your files. For example, if you specify an output file version number that is lower than the version number of your input file, the highest version number no longer applies to your latest file. (Storing a New Version of a File and Using the Original File Name)

The general form of the file specification string to use when you want to store a new version of a file and use the original file name is: input-filespec[/CA][/BL:temporary-file-size](Return) [/-CA] [/FO]

For the file specifications, use any of the forms that are valid for RSX--11. The options are described in (rsxcomopt_sec).

For example, at the end of a work session that you begin with the following command, KED stores a new version of the file named EXAMP.FTN. That version will include all the changes you make to the latest version of EXAMP.FTN under your default UIC that KED finds on your default system device. (MCR>)(KED EXAMP.FTN(Return))

KED displays the first 24 lines of the latest version of SY:EXAMP.FTN under your default UIC. (Inspecting a File)

The general form of the file specification string to use when you want to inspect a file is: input-filespec/IN

Use any valid RSX--11 file specification. The /IN option (for INSPECT) is required.

For example, when you begin a work session with the following command, KED displays the first 24 lines of version 4 of the file SY:INSPEX.PRG. You cannot change the file, because the /IN option disables all KED functions and commands that insert or delete text. (MCR>)(KED INSPEX.PRG;4/IN(Return)) (Creating a New File)

The general form of the file specification string to use when you want to create a new file is: output-filespec/CR[/CA][/BL:temporary-file-size](Return) [/-CA] [/FO]

Use any valid RSX--11 file specification. The /CR option (for CREATE) is required. The other options are described in (rsxcomopt_sec).

For example, at the end of a work session that you begin with the following command, KED stores version 1 of a new file named EXAMP.BAS on default device SY. (MCR>)(KED EXAMP.BAS/CR(Return))

KED displays its cursor in the upper left corner of an empty screen. (Storing a New Version of a File and Using a New Output File Name)

The general form of the file specification string to use when you want to store a new version of a file and use a new output file name is: output-filespec[/CA][/BL:temporary-file-size]=input-filespec(Return) [/-CA] [/FO]

Use any valid RSX--11 file specifications. The options are described in (rsxcomopt_sec).

For example, your default system device does not contain a file named SPCOUT.FTN. At the end of a work session that you begin with the following command, KED stores version 1 of a new file named SPCOUT.FTN on your default system device. The file SPCOUT.FTN;1 will include all the changes you make to the latest version of GENIN.FTN that KED finds on your default system device. (MCR>)(KED SPCOUT.FTN=GENIN.FTN(Return)) (KED Command Line Options\rsxcomopt_sec)

(2\17) (Option\Meaning) (/BL:temporary-file-size\Use the /BL (BLOCKS) option and specify the number of blocks you want KED to use for a temporary file. To specify a decimal size, add a decimal point to the number; to specify an octal size, omit the decimal point. KED's use of temporary files is explained in (outtempsize_sec). Since the default size is usually adequate, use this option only in special cases, such as when you want to combine several files.) (/CA\Create an output file with the implied carriage control attribute. This is the default when you create a new file.) (/-CA\Create an output file with the embedded carriage control attribute.) (/FO\Create an output file with the FORTRAN carriage control attribute. KED does not check that the first character in each record is a FORTRAN carriage control character.) (/ID\Use the /ID (IDENTIFY) option to have KED display its version number. Do not add the option to any file specification string. The option is valid only by itself in response to the (KED>) prompt and in the following form of a direct call with the task name. (KED/ID(Return)) ) (Anticipating a System Crash or Similar Malfunction)

??? (Beginning Your Work Session)

??? (Recovering the Work You Performed)

??? (Using Initialization Files)

??? (Restrictions)

This section describes restrictions for running KED on RSX--11 systems. (File, Account and Volume Protection)

KED supports standard system conventions such as: (simple) Read, write and update access to files The characteristics of privileged and nonprivileged accounts Public and private devices

The (rsxpmcr_book) describes those conventions in detail.

KED also warns you in the following cases. (unnumbered) When you specify an output file name and version number that are stored on the output volume, KED displays the following message. ?KED-W-Output file exists - Continue (Y,N)?

If that message appears, you can cancel your work session by responding with N (for no). Or you can continue the session, delete the existing file, and store the new file you create under the old name by responding with Y (for yes). When you specify an output file that was opened by another user or if the input and output file specifications are the same, KED displays the following message. ?KED-F-Unable to create output file

If that message appears, no files are created or changed. Following the message, your system displays the (KED>) prompt.

In the following example, KED warns that disk DM1 contains the file MAYQUE.BAS;17. It is deleted because the user responds with Y. (MCR>)(KED DM1:MAYQUE.BAS;17=MAYQUE.BAS(Return)) (?KED-W-Output file exists - Continue (Y,N)? )(Y(Return)) (Output File and Temporary File Size\outtempsize_sec)

KED allocates free space on your output volume for two purposes: (simple) For a temporary file that KED uses until you end your work session For the final output file when you end your work session

The following paragraphs describe restrictions and requirements that apply to the temporary file and final output file.

The most common problem occurs when your output volume contains too little free space for the file that KED creates. If you need more free space, you can: (unnumbered) Specify an output volume that has more free space than SY. Create more free space on SY by purging some of the files stored there. Specify a smaller temporary file size by using the /BL option.

KED lets you move the cursor backward in the file you are editing, inspecting or creating. But that feature requires a temporary file, and when KED starts it allocates free space on your output volume for the temporary file. When you create a new file, initially the temporary file is empty. When you edit or inspect a file, KED copies your input file into the temporary file as you move the cursor down through your input file. As you back the cursor up through the file, KED uses the copy until you end your work session.

When you end your work session, KED copies the temporary file to the output file you specified. If KED cannot complete the copying process, your system locks the output file and temporary file and displays the following message. ?KED-F-Unable to copy temporary file

When KED finishes copying, it truncates the output file after the last record and deletes the temporary file. If KED cannot close the output file properly, your system locks the output file and temporary file and displays the following message. ?KED-F-Unable to truncate or close output file

If either message appears, the locked files contain questionable data. If you want to salvage parts of those files, use the PIP UNLOCK command described in the (rsxum_book).

KED allocates free space on your output volume for the temporary file and output file in one of the following ways. (unnumbered) When you inspect a file, KED allocates space for the temporary file in the default UIC and on the default device SY but does not allocate space for an output file. The free space KED requires is the same as for your input file. If the space available for the temporary file is too small for your input file, KED displays one of the following messages and your system displays the (KED>) prompt. ?KED-F-Temporary file shorter than input file ?KED-F-Unable to create temporary file

Those and the following messages are explained in (mes_ax). When you create a new file, KED allocates 50 blocks for the temporary file and 55 blocks for the output file. If you add the /BL option to your file specification string, KED allocates the amount of space you specify for the temporary file and 10% more for the output file. Both spaces are allocated on your output volume. If your output volume does not have enough free space, KED displays the following message or one of the messages listed above and your system displays the (KED>) prompt. ?KED-F-Unable to create output file When you edit a file, KED allocates for the temporary file 50 blocks more than the size of your input file. If you add the /BL option to your file specification string, KED allocates the amount of space you specify for the temporary file. With and without the /BL option, KED allocates for the output file 10% more than the size of the temporary file. Both spaces are allocated on your output volume. If your output volume does not have enough free space, KED displays one of the messages listed above.

When you start KED, if the temporary file is not at least 10 blocks larger than your input file, KED displays the following message. ?KED-W-Only MMMMMM blocks available for insertions - Continue (Y,N)?

If you plan to delete text from your input file or add a small amount of new text, you can continue your work session by responding with Y (for yes). Otherwise, you can stop the session by responding with N (for no).

When you add text to a file you are creating or editing and the file becomes as large as the space allocated for it, KED refuses to accept more text and signals you by ringing the bell, sounding the beeper, or reversing the screen background on your terminal. If you then use the HELP function, KED displays the following message. Insert finds file full (Output File Record Length)

In the output file, KED creates a record for each text line in the temporary file. You can create a text line of any length by typing or using other methods of inserting text. But when KED copies the temporary file to the output file, the maximum output file record length KED creates is 256 bytes, not counting the record's line terminator.

If the temporary file includes a text line that is longer than 256 bytes, KED writes more than one record to the output file. In that case, KED writes 256-byte output records, adding the carriage-return/line-feed terminator, until 256 bytes or fewer remain in the temporary file record. The last output file record that KED writes has the terminator that KED displays. (Input File Record Length)

When you edit or inspect a file, the size of KED's input buffer determines the maximum length of input file records that KED can read.

If your input file contains a record that is too long, KED displays the following message. ?KED-W-Input file contains records that will be truncated - Continue (Y,N)?

When that message appears, you can cancel your work session by responding with N (for no). Or you can continue the session by responding with Y (for yes). If you continue, KED truncates each input file record that is too long but does not warn you in any way.

The following section tells you how to increase the size of the input buffer when you start KED. (Running KED with Larger Paste and Input Buffers)

The size of KED's input buffer and paste buffer is determined when KED is task built. The minimum size for each is 512 bytes, but you can install KED with a larger task increment.

You can increase the size of the input buffer and paste buffer for a single work session by starting KED with the MCR command RUN, adding the /INC (INCREASE) option, and specifying the increase you need. The general form of the command is: RUN $KED/INC=size.(Return)

(size) is a decimal value followed by a period ((.)).

The following table lists the values you should specify with the /INC option to increase the input buffer and paste buffer by increments of 512 bytes.

(2\20) (Desired increase in input and paste buffer size\Value to specify with /INC option) (512 bytes\3988.) (1024 bytes\4756.) (Each additional 512 bytes\Add 768.)

Intermediate increases for the paste buffer are also possible. For example, if you specify 4400. with the /INC option, the input buffer is increased by 512 bytes as shown in the table and the paste buffer is increased by 924 bytes (4400 $()\; 3988$ ()\; 412$ ()\; 512$ ()\; 924).(RSX--11M--PLUS\; Systems)$$$$

??? (Installing KED)

The system prompt for RSX--11M--PLUS is: (simple) A dollar sign (($)) or If the monitor console routine (MCR) is running, the RSX--11M prompts. (simple) A right-angle bracket ((>)) or The characters MCR followed by a right-angle bracket ((MCR>)) (System Requirements)

You will need approximately 620 blocks of free space on your system volume.

There are no special system generation requirements.

Your terminal must be identified by the following command. (SET /VT100=TI:(Return)) (Terminal Requirements)

Your terminal must be set for type-ahead.

To set VT100 terminal characteristics, use the SETUP A and SETUP B modes. Refer to your (vtug_book) for detailed instructions about the SETUP modes.

To set VT??? terminal characteristics, ???

For some terminals, you can choose the block cursor or the underline cursor. Examples in this document show the underline cursor.

You can run KED with your terminal set for the ANSI mode. When you exit KED, your terminal will be set for the ANSI mode. (Installation Procedures)

Each of the following procedures consists of two steps. (numbered) Copying files from your distribution volume to your system volume. Executing an indirect command file supplied by DIGITAL to task build KED.

In each procedure, (dev) is the device abbreviation and unit number for your distribution volume. (Procedure for Disks) (MCR>)(MOU dev:KEDRSX(Return)) (MCR>)(PIP SY:/NV=dev:[30,15]*.*(Return)) (MCR>)(DMO dev:(Return)) (MCR>)(@KEDBLD(Return)) (Procedure for Magtape)

For 1600 bits/inch magtape, add the /DNS:1600 option to the second command line. (MCR>)(MOU dev:/FOR(Return)) (MCR>)(FLX SY:/RS=dev:[30,15]*.*/DO(Return)) (MCR>)(DMO dev:(Return)) (MCR>)(@KEDBLD(Return)) (Verifying Your Installation)

To verify that KED operates correctly, you can work through the example provided in (session_ax). That example tells you how to edit SAMPLE.KED, a file included in your distribution kit. (Before Using KED) (numbered) Check that KED was installed. Complete the (rsxpin_book). Study the (rsxpmcr_book), and learn to start and stop the monitor console routine (MCR). (Running KED\runplus_sec)

Use the same procedures as for RSX--11M systems. KED accepts all RSX--11M--PLUS file specifications. (Using the EDIT Command)

In addition to the RUN command and direct calls with the task name KED, you can run KED with the EDIT command.

Complete the EDIT command with the /USING qualifier and add the task name KED.

For example, to inspect a file named STUDY.TST on your default system device: (>)(EDIT/USING:KED STUDY.TST/IN(Return)) (Restrictions)

???