* PFxx TABCHR System Overview 6 , For,:exarriple, if ,the FILE statement read, . :l :; " " , 'I.', \ 'f',',': _' , . ' FILE ASSEMBLE (& LRECL80 DEFAULT ASMDEF U '. o'..t .' ; ,.. , , .... and the user entered " '" EDGAR TEST ASSEMBLE the following statement would be generated EDGAR TEST ASSEMBLE * LRECL 80 DEFAULT ASMDEF UPDATE
The presence of the SYNONYM keyword establishes a syno­
nym filetype, yyyyyyy, by which a file may be called. In
addition, the filetype may be abbreviated to the minimum
number of characters indicated by 'm'. For example, if the
FILE statement read FILE ASSEMBLE 0:: LRECL 80 SYN TEST 1
and the user entered
EDGAR SOME T
the following statement would be generated
EDGAR SOME ASSEMBLE (& LRECL 80 A file type of asterisk (*) not starting in position one (1) of
the statement establishes the default ENTER settings for all
filetypes for which there is no FILE control statement.
An asterisk in column one indicates a comment card and has
no effect on the editing system environment.
The PF control statement allows the user to establish the meaning of the depression of a PF Key. The data which
appears on the rest of the PF control statement becomes
associated with the key and is placed, LIFO, in the CMS con­
sole stack when the PF key is depressed during an editing
session. The data is then available to the sos facility and
may, as a result, cause a simulated screen operation or be­
come part of the data file. (See Section v, Advanced Editing
Facilities for a discussion of SOS and its use of the CMS con­
sole stack).
The T ABCHR control statement defines a logical tab charac­
ter. When this character is encountered in the data as the I/O virtual screen is being updated (see Section III, System Flow), a tab operation is performed based on the current "tab settings" as defined by the editing command TAB. Use
of the T ABCHR is functionally equivalent to use of the "FIELD MARK" key. (See Section III, Keyboard Functions).
TABDEF " CMDSYN The TABDEF,controi statement defines the "tab fill" 'charac­ ter string. This character string is inserted on the I/O virtual , screen from the point where the logical tab character was'
. 'depre'ssed to the start of the data at the next "tab stop" For:-' , example, if the T ABDEF and T ABCHR read: .
TABDEF' TABCHR @ " and the data appearing on the screen reads as follows:
abc def ghi
with the 'A', the 'D' and the 'G' appearing in the "tab stop"
columns, and one entered:
x@klm@y
the result would be:
x kIm yhi
Setting the TABDEF to nothing means "don't fill" and will
leave existing data on the I/O virtual screen. (The function
of the IIDUP" key is useful when using logical tabs. See Sec­
tion III, Keyboard Functions.)
The CMDSYN control statement allows the user to create
command synonyms. Through the use of this control state­
ment, the user may provide a synonym for any EDGAR, CMS, or CP command enterable from the EDGAR command line.
The synonym definition may include the re-ordering andlor
reformatting of command operands.
The CMDSYN control word identifies a synonym definition
statement describing the synonym name, minimum abbrevia­
tion, and the order and format of its operands. This control
statement must be immediately followed by a synonym mod­
el as shown below. CMDSYN xxx xx < n > < & & / &. > ABC & 1 & 2 & 3
The synonym definition statement contains the name of the
synonym, xxxxx, the minimum abbreviation count, "n", and
a set of descriptive codes identifying the position and attri­
butes of each of the possible operands. An' & ' signifies a
blank delimited operand. An' & I' signifies a string delimit­
ed operand such as I abel. An' & .' indicates a dual string
delimited operand. This form is used when two operands
utilize a common string delimiter as in I abcl xyz/ such that
the embedded delimiter, 'I', can be reused for the second
operand. In this case, the format of the first string would be
signified by an '& .' and the format of the second by an
System Overview 7
Previous Page Next Page