IV. Editing Functions Type I Commands
CANCEL
Type I Commands
EDGAR commands· are ·divided into three (3) categories. Type I and II com­
mands may either be entered on 'the Type I & -'n Command Area of the
screen (Fig. 2, Line 2), or passed to the Editing Command Processor via the
SVC interface. Type III commands generally pertain to individual Data
Display Areas and may be entered only in the Type III Command Areas.
Type I commands differ from Type II commands in that they require "edit level post-processing." this means that the immediate effect of a command is
to flag the requested action for execution at the appropriate time. Edit level
post-processing actually occurs after all logical displays on the screen have
been processed and all data has been analyzed. Post-processing involves edit
level disposition, edit level storage, and edit level re-formatting.
The Type I & II command line entry may be preceded by the character" & " causing EDGAR to leave the associated command(s) on the screen if no errors
are encountered during processing. This reduces the need for re-entering
commands which are used repeatedly. For example, if " & F" is entered on
the command line, the FORWARD co.mmand will remain on the screen, allow­
ing the user to "scroll" through the file without re-entering the FORWARD
command.
Multiple commands (both Type I and II) may be entered on the command line
if they are separated by a X'OI '. The commandS' will be processed, in order,
from left to right, with the exception of any post-processing activity, which
will occur only once, when all other command processing is complete.
Type I and II commands which are not recognized by the Editing Command
Processor are passed to the CMS subset.
Messages generated during edit level post processing, such as errors in writing
to disk or errors in re-formatting are not issued on the command line. In­
stead, these messages are produced on the standard VM or CMS screen,format
(with the command line and the "RUNNING" status at the bottom). After
displaying these messages, the screen will enter "MORE" status at which point
the user may depress PA 2 or CLEAR to return to EDGAR. If post-processing
errors occur, the necessary action must be taken (including re-issuing of
commands) to renew the post-processing request.
The Type I commands and their formats are described below. A Type I
command is entered on the Type I & II Command Area of the screen (Fig. 2,
Line 2). Each command described below is shown with its shortest form. Optional arguments are enclosed in brackets «» and the "OR" symbol ( I )
is used to designate operands of which one and only one must be selected
from the list.
CANCEL
This command causes immediate termination of the editor. It is functionally
equivalent to entering QUIT for each active edit level. (For information on
edit levels, see the TYPE I command, ENTER).
18
'ENTER E'<:Fn <ft <fm> > > ' < Lreel nn>
< Seq8 I NOSeq8 >
< Ctl xxxxxxxx I NOCtl> <Update I NOUpdate> < DEFault yyyyyyyy I NODEF> <CLEAR I NOCLEAR> The ENTER command provides the capability to edit on several different "edit
levels". Each edit level pertains to a different file and each is edited inde­
pendently. If .the ENTER command is issued with no arguments, another level
is entered. If no other level exists, no apparent change occurs. Optionally, a filename, filetype, and filemode may be specified in the ENTER
command. If the filename and/or file type is specified as "*", the correspond­
ing attribute of the current fileid will be substituted. (Note: the useof "*" for the filename or file type is not permitted when entering the first level, i.e.
from the eMS command level). The file mode must be specified as a one-or
two-character file mode or "*". If only the disk letter is specified, the mode
number defaults to "1". When a fileid is specified in this manner, the ENTER
command causes EDGAR to search all existing edit levels for a file name, type
and mode matching requested. If the mode is specified as "*", EDGAR
will scan for matching filename and filetype, only.
If no existing edit level can be found with a fileid matching that requested, a
new edit level is created using the requested fileid. In this case, the requested
disk is searched for a file with the same filename and file type as that speci­
fied. If the filemode is specified as "*", the standard order of disk search (A,
B, C, D, E, F, G, S, Y, Z) is used to locate the file. Once found, the file is
read from disk and editing initialized on the new level.
If no previous edit level exists with the specified filename and type, and no
file can be found on disk with a matching fileid, EDGAR assumes that a new
file is to be created. If the mode was specified as "*", the new level will be
created with a default mode of AI.
The remaining parameters on the ENTER command are used only when
creating a new edit level. These parameters will be ignored if an existing edit
level is found with a matching fileid. Each option permits specification of file
characteristics for the level being created. Only those characteristics which
cannot be altered after the level has been initialized are used in the ENTER
command.
LRECL -this option sets the maximum logical record length for the newly
created edit level. As with other options, LRECL may be speci­
fied explicitly on the command, or implicitly through the
EDGAR $PROFILE. If this option is not specified and the file
exists on disk, the maximum logical record length in the existing
file is used. If the option is specified and the file exists on disk,
the maximum record length for the newly-created edit level will
be equal to the specified length or the maximum record length
in the file, whichever is greater. If the file does not exist, the
specified LRECL is used. If none has been specified, LRECL will
default to 80. Type I Commands 19
Previous Page Next Page