EDIT Subcommands-VERIFY VERIFY Use the
setting.
r I I Verify 1
1 L- ON VERIFY subcommand to set or display the
The format of the VERIFY subcommand is:
current verification I r , rr , , I ION I 1 !startcoll endcoll I I OFF I I I 1 I * I ,L J LL .J .J specifies
displayed,
indicated.
that lines located, altered,
and changes between edit and ON is the initial setting.
or changed
input mode f. are are OFF specifies that lines that are located, altered, or changed are not displayed, and changes between edit ani input mode are not
indicated.
startcol indicates the column in which verification is to begin, when
verification is on. The default is column 1. startcol must
not be greater than the record length nor greater than endcol. endcol indicates the last column to be verified, when verification is
on. endcol must not be greater than the record length. If
endcol is specified as an asterisk (*), each record is
displayed to the end of the record.
1. If you issue the VERIFY subcommand with only one operand, that
operand is assumed to be the endcol operand. For example, if you
issue VERIFY 10, verification occurs in columns 1 through 10. 2. The editor assigns the following settings, by fi.!,giY:Qg§ AMSERV, ASSEMBLE, COBOL, DIRECT, FORTRAN, MaCRO, PLI, PLIOPT, UPDATE, UPDTxxxx others (Including FREEFORT) yeri.fi.£stiQll Column 72
Record Length
If you issue the VERIFY subcommand with no operands, the current
startcol and endcol settings are displayed, regardless of whether
verification is on or off.
Section 3. EDIT and 255
EDIT Subcommands-X, Y X or Y Use the X or Y subcommands to assign a given EDIT subcommand to be
executed whenever X or Y is entered, or to execute the previously
assigned subcommand a specified number of times. The format of the X and Y subcommands is:
subcommand indicates any EDIT subcommand line. The editor assumes that
you have specified a valid EDIT subco.mand, and no error
checking is done.
n indicates the number of times the previously assigned
subcommand is to be executed. If X or Y is entered with no
operands, 1 is assumed.
1. Advancement of the current line pointer depends upon the EDIT
subcommand that has been assigned to X or Y. If a number or a
subcommand is not specified, the previously assigned subcommand is
executed once.
2. X and Yare initially set to null strings. If you enter X or Y without having previously assigned a subcommanj to it, the editor
issues the ?EDIT error message.
3. You can use the X and Y subcommands in many instances where you
must repeat a subcommand line many times while editing a file, but
the situation does not lend itself to a global request. For
example, if you assign X to a LOCATE and Y to a CHANGE subcommand,
issue:
x
to execute the LOCATE request, and after examining the line, you
can change it and continue searching, by entering the Y subcommand
followed by the X subcommand: y#x or just continue searching:
x
Responses are issued for the EDIT subcommands that are assigned to X and Y, in a=cordance with the current verification setting.
256 VM/170 CMS Command and Macro Reference
Previous Page Next Page