System Overview 8 Immediately following the synonym' definition 'statement is
the synonym model. This statement is a model of the com- ' mand which is to be generated from the command synonym.
The model statement includes all literal data to be generated.
The variable data (operands supplied in the source com­
mand) are indicated by & 1, & 2, etc. In this case, , & l'
refers to the first operand encountered under control of the
synonym model. For example, if the synonym HEXC were
defined as follows: CMDSYN HEXC 1 &. & I &::: C IX' & l' IX' & 2' I & 3
and the following command was entered:
h Ild/efl * * ver
the command generated (and processed by the Editing
Command Processor) would be: , C IX'ID' IX'EF' I ::: ::: VER
Note that the "string-delimited" operands (X' & l' and
X' & 2') include only the data within the delimiters; i.e., the
delimiters in the source command are removed prior to sub­
stitution. Thus the user may provide alternate delimiters if
desired.
The synonym command table is always examined before
analysis of the command thereby permitting synonyms for
any EDGAR, CMS, or CP command enterable from the com­
mand line.
A synonym definition cannot contain a logical command
separator. Since the synonym is processed by the Editing
Command Processor, facilities which are provided by the I/O and Display Processors are not available to data generated
through use of the synonyms. For example, the resultant
command is not translated before processing nor can you
define a synonym to execute an SOS command.
After the processing of EDGAR $PROFILE, the file to be edited is read into
virtual storage and closed. The file is written from storage-to-disk when a
FILE or SAVE command is issued or via the AUTOSAVE facility (see Section IV). The method used in each of these cases is to write the file to a utility file
('EDIT CMSUTl') on the specified disk. When the entire file has been success­
fully written, the original file is erased and the utility file is 'RENAMED' to the
original file-id. Should any errors occur while writing the utility file, the
original is always maintained. Furthermore, any AUTOSA VE files for the
given level are not erased until the utility file has been successfully written
and renamed. If the file 'EDIT CMSUTl' exists, EDGAR cannot be initialized.
This reduces inadvertent deletion of important data. If this condition exists,
the user should verify the information in the utility file and 'ERASE' it if not
needed or 'RENAME' the file to the desired fileid if required.

1 FN
Figure 2 below describes the basic screen layout and 'names of the various
screen'fields.' The user should attempt to become familiar with these names
because they will be used throughout this manual and will be referenced in
error messages generated by EDGAR.
AL TERATION COUNTER UPDATE OPTION'INDICATOR I I J
LRECL I , AUTOSAVE I FlLEID, AREA RECFM I D RECORD COUNTER , , J I I , I , I I I I I I I I I I I I I Xt Xt -.!t -.!t Xt FT FM -UPD 80 (1) ALT"'14 RECDS 21 LINE
LINE 2 ..:=> TYPE I & II COMMAND AREA
LINE I - - - -> /===/
LINE 1 *.==*
LINE 1 LINE 1 * ...... *
LINE 7<-------DATA DISPLAY AREA---------------> *===*
LINE
LINE
LINE 10 LINE 11
LINE 12
LINE 13
LINE 14
LINE 15
LINE 16 LINE 17
LINE 18
LINE 19
LINE 20 LINE 21
LINE 22
LINE 23
24
Figure 2. Basic screen layout and definition
*===* *=z::=* *===*
*===*
*===*
*===*
TYPE *===*
THREE *===* *===* AREAS *===*
*===*
*===*
*===*
*===*
*===*
- - - -> *EOF* System Overview 9