(IAS operating system procedures) (Operating system proceduresIAS) (ProceduresIAS operating system) This appendix describes procedures that are specific to the IAS operating system. (Installing KED)

The system prompt for IAS is: (simple) The characters PDS followed by a right-angle bracket ((PDS>)) or The characters MCR followed by a right-angle bracket ((MCR>))

Your system manager may be responsible for the settings described in this section. If you are not sure about the settings for your system, check your local operating procedures or ask your system manager. (System Requirements)

You must identify your terminal as a VT100.

DCL: (PDS> )(SET TERMINAL VT100(Return))

MCR: (MCR> )(TER /VT100(Return)) (Terminal Requirements)

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)

Refer to the ???. (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) Make sure your system contains KED files for use with the DCL or MCR command language interface. If your installation uses DCL, read Chapters 1 through 6 in the (iaspds_book) and read Chapter 14 for details of the PDS commands.

If your installation uses MCR, read Chapters 1, 2, 3 and 6 in the (iasmcr_book). (Running KED)

You can run KED in two ways: (numbered) By using the monitor console routine (MCR). You call KED directly with the task name KED. By using the DIGITAL command language (DCL) implemented by the IAS program development system (PDS). You use the PDS command EDIT/KED.

With MCR: (unnumbered) If you include a file specification string in your direct 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 do not include a file specification string in your direct call, any special settings you made and the contents of KED's buffers are preserved for your next work session. When the prompt (KED>) appears, you can begin another work session by completing a 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) or when you exit KED in any way.

For a full description of MCR, see the (iasmcr_book).

With DCL, KED returns you to the PDS level when you end your work session. Any special settings you made and anything you stored in KED's buffers are lost.

The following sections describe the different methods of running KED. (Startup Default Values) (2\15) (Item\Default) (Device name\Your system device when you log in. You can change your default device on a timesharing system by using the PDS SET DEFAULT command. On a multiuser system you cannot specify a default device.) (UFD\Equivalent to your UIC when you log in. Use the PDS SET DEFAULT command to specify a different UFD or the MCR SET UIC command to specify a different UIC.) (Input file name and type\No default. You must specify the file name and type.) (Output file name and type\When you create a new version of a file, KED uses your input file name and type. When you create a new file from an existing file, you must specify the output file name and type.) (Input file version\The latest version of your input file.) (Output file version\When you create a new file, KED assigns version 1. Otherwise, KED assigns a version number that is 1 greater than the version number of the latest version.) (Output file protection\When you create a new file, your system gives that file the default protection of your volume. When you edit a file, KED sets the output file protection to match the input file protection. To change file protection, use the PDS SET PROTECTION command described in the (iaspds_book) or the PIP utility with the /PR switch described in the (iasum_book).) (Output file carriage control attribute\When you create a new file, KED assigns the implied carriage control attribute. Otherwise, KED assigns the input file's attribute.) (Size of 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 temporary file size is 50 blocks. Otherwise, the default size is 50 blocks larger than your input file.) (Calling KED with the Task Name KED)

If you have a real-time system or a multiuser system with MCR as the user interface, you can call KED directly by typing the task name.

The two forms of the call, which are the same for RSX--11 systems, are described in (rsx_ax).

[Should I copy the applicable sections here???] (Using the PDS EDIT/KED Command\pdsedit_sec)

The PDS command EDIT lets you use DIGITAL's text editors. The (iaspds_book) describes that command in full. The following paragraphs tell you how to specify the EDIT command so you can use KED.

Use EDIT/KED if you are running KED on a terminal that is compatible with the VT100 series. The command format is: (EDIT/KED[/qualifiers] input-filespec(Return))

(qualifiers) is one or more of the following.

(2\25) ((/BLOCK_SIZE:n)\Specifies the decimal number of blocks (n) that KED will use for a temporary file. Do not type a decimal point.

KED's use of the temporary file is explained in (iasouttemp_sec). Since the default temporary file size is usually adequate, use this qualifier only in special cases, for example, when you want to combine several files.) ((/EMBEDDED_CARRIAGE_CONTROL)\Creates an output file with the embedded carriage control attribute.) ((/FORTRAN_CARRIAGE_CONTROL)\Creates an output file with the FORTRAN carriage control attribute. KED does not check that the first character in each record is a valid FORTRAN carriage control character.) ((/IMPLIED_CARRIAGE_CONTROL)\Creates an output file with the carriage control attribute. This is the default when you create a new file.) ((/INSPECT)\Lets you inspect your input file. When you use /INSPECT, you cannot specify any other qualifiers.) ((/OUTPUT:output-filespec)\Specifies your output file.)

The qualifiers you specify for the EDIT/KED command start one of the four KED editing processes: (numbered) 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 forms of the EDIT/KED command you specify to begin each editing process are described in Sections (iasstoreorig_sec\value) through (iasstorenew_sec\value).

By default, your system uses the input file with the highest version number and stores the output file with the next highest version number.

Although your system and KED accept an explicit output file version number, if you use such a number 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\iasstoreorig_sec)

To store a new version of a file and use the original file name, use the following format. (EDIT/KED[/qualifiers] input-filespec(Return))

(qualifiers) is one or more of the following. (simple) (/BLOCKS_SIZE:n) (/EMBEDDED_CARRIAGE_CONTROL) (/FORTRAN_CARRIAGE_CONTROL) (/IMPLIED_CARRIAGE_CONTROL)

Those qualifiers are described in (pdsedit_sec). Use any valid file specification for (input-filespec).

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 JEN.LST. That new version includes all the changes you made to the latest version of JEN.LST under your UFD on your default device. (PDS> )(EDIT/KED JEN.LST(Return))

KED displays the first 24 lines of the latest version of JEN.LST. (Inspecting a File)

To inspect a file, use the following format. (EDIT/KED/INSPECT input-filespec(Return))

The /INSPECT qualifier is described in (pdsedit_sec).

For example, if you begin a work session with the following command, KED displays the first 24 lines of the most recent version of the file named INSPEX.FTN. You cannot make any changes to that file, because the /INSPECT qualifier disables all KED functions and commands that insert or delete text. (PDS> )(EDIT/KED/INSPECT INSPEX.FTN(Return)) (Creating a New File)

To create a new file, use the following format. (EDIT/KED/OUTPUT:output-filespec[/qualifiers](Return))

(qualifiers) is one or more of the following. (simple) (/BLOCK_SIZE:n) (/EMBEDDED_CARRIAGE_CONTROL) (/FORTRAN_CARRIAGE_CONTROL) (/IMPLIED_CARRIAGE_CONTROL)

Those qualifiers are described in (pdsedit_sec). Use any valid file specification for (output-filespec).

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 JW123.CBL under your UFD on your default device. (PDS> )(EDIT/KED/OUTPUT:JW123.CBL(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\iasstorenew_sec)

To store a new version of a file and use a new output file name, use the following format. (EDIT/KED/OUTPUT:output-filespec[/qualifiers] input-filespec(Return))

(qualifiers) is one or more of the following. (simple) (/BLOCK_SIZE:n) (/EMBEDDED_CARRIAGE_CONTROL) (/FORTRAN_CARRIAGE_CONTROL) (/IMPLIED_CARRIAGE_CONTROL)

Those qualifiers are described in (pdsedit_sec). Use any valid file specifications for (output-filespec) and (input-filespec).

For example, your default device does not contain a file named EXAMP.FTN. At the end of a work session that you begin with the following command, KED stores version 1 of a new file named EXAMP.FTN under your UFD on your default device. That file includes all the changes you made to the latest version of the file OLDEX.FTN that KED finds under your UFD on your default device. (PDS> )(EDIT/KED/OUTPUT:EXAMP.FTN OLDEX.FTN(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. (File and Volume Protection)

KED supports standard system conventions, such as read, write and update access to files. The (iaspds_book) and (iasmcr_book) describe file and volume protection in detail.

KED also warns you in the following cases. (unnumbered) If you specify an output file name and version number that are stored on the device you specify, 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 your new file under the old name by responding with Y (for yes). If you specify an output file that is open for 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

After KED displays that message, no files are created or changed. Following the message, your system displays its prompt or the KED prompt, depending on how you invoked KED.

In the following example, KED warns that disk DM1 contains the file MAYQUE.BAS;17. It will be deleted because you respond Y to the warning. (MCR>)(KED DM1:MAYQUE.BAS;17=MAYQUE.BAS(Return)) (?KED-W-Output file exists - Continue (Y,N)? )(Y(Return))

or (PDS> )(EDIT/KED/OUTPUT:DM1:MAYQUE.BAS;17 MAYQUE.BAS(Return)) (?KED-W-Output file exists - Continue (Y,N)? )(Y(Return)) (Output File and Temporary File Size\iasouttemp_sec)

KED allocates free space, on the device you specify to contain your output file, for two purposes: (numbered) For a temporary file that KED uses until you end your work session For your final output file when you end your work session

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

The most common problem occurs when the device you specify to contain your output file does not contain enough free space for the file that KED creates. If you need more free space on that device, you can: (unnumbered) Specify another device with more free space on it to contain your output file. Free some space on the device you specified by deleting some of the files stored there. Specify a smaller temporary file size by using the: (simple) /BL option (MCR) or /BLOCK_SIZE:n qualifier for EDIT/KED (PDS)

KED lets you move the cursor backward in the file you are editing, inspecting or creating, and that feature requires a temporary file. When KED starts, it allocates free space for the temporary file. (unnumbered) 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 move the cursor backward through your file, KED uses the copy until you finish editing.

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 the temporary file (named KEDXXX.TMP) and displays the following message. ?KED-F-Unable to copy temporary file

When KED finishes copying, it truncates your output file after the last record and deletes the temporary file. If KED cannot close your output file correctly, your system locks the output file and the 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 part of a locked file, use the PIP UNLOCK command described in the (iasum_book) or the PDS commands UNLOCK and SET END-OF-FILE described in the (iaspds_book).

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

That 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 your output file. If you add the /BL option to your file specification string (MCR) or the BLOCK_SIZE:n file qualifier to your EDIT/KED command (PDS), KED allocates the amount of space you specify for the temporary file and 10% more for your output file. Both spaces are allocated on the device you specify to contain your output file. When that device does not contain enough free space, KED displays the following message or the message shown 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 (MCR) or the BLOCK_SIZE:n file qualifier to your EDIT/KED command (PDS), KED allocates the amount of space you specify for the temporary file. With and without the /BL option or the BLOCK_SIZE:n qualifier, KED allocates for your output file 10% more than the size of the temporary file. Both spaces are allocated on the device you specify to contain your output file. When that device does not contain enough free space, KED displays one of the messages shown 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 XXXXXX 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 free 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 your 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.

When KED copies the temporary file to your output file, the maximum output file record length that 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 your 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.

KED does not warn you when it processes long records as described above. (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)?

If that message appears, you can cancel your work session by responding with N (for no). Responding with Y (for yes) continues the session. 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 the input buffer 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 or PDS command RUN, adding the /INC option or /INCREASE qualifier to your command line, and specifying the size you need. The form of the RUN command is: (MCR>)(RUN [11,1]KED/INC=size(Return))

or (PDS> )(RUN/INCREASE:size [11,1]KED(Return))

(size) is a decimal value.

The following table shows the values you should specify with the /INC option or /INCREASE qualifier 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 or /INCREASE qualifier) (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 or /INCREASE qualifier, 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).$$$$