SET VERIFY
Purpose
- Control whether lines that subcommands change are to be displayed (in the message area, for a display terminal). If the current line pointer changes, the new current line is displayed.
- Define the columns to be displayed when a file appears on the screen. Optionally, data may be displayed in hexadecimal notation.
Operands
- ON
- specifies all lines changed by subcommands are to be displayed. (This is the initial setting for a typewriter terminal.)
- OFF
- specifies lines changed by subcommands are not to be displayed. (This is the initial setting for a display terminal.)
- Hex
- displays the data in hexadecimal notation.
- startcol endcol
- are a pair of column numbers that define an area to be displayed.
- *
- indicates LRECL will be used for endcol.
Initial Setting
Based on file type. See File Type Defaults.
Usage Notes
- You can specify up to 28 pairs of columns. For example:
displays columns 1 through 20 and 40 through 50.v 1 20 40 50 - You can display an area in both EBCDIC and hexadecimal. For example:
displays columns 1 through 20 in both EBCDIC and hexadecimal.v 1 20 H 1 20 - You can change the data in either the EBCDIC or the hexadecimal display. To change the hexadecimal
display, enter changes in hexadecimal. If you type an invalid hexadecimal code, the following
message is displayed on the first line of the screen (the file identification line):
Invalid hex-data on screen: - The SET IMAGE setting affects the way hexadecimal data is treated. For example, if IMAGE is ON and you enter a X'05', it expands into X'40's (or to whatever the FILLER character is in hexadecimal) to the next tab position.
- In multiple views of the same column, if changes are made on the screen the right-most change is the effective one.
- The columns specified in a SET VERIFY subcommand override any RIGHT or LEFT subcommand in effect.
- The editor displays a file line on as many screen lines as necessary. You can turn
off this automatic line wrapping feature by issuing the appropriate SET VERIFY subcommand.
For example, the default VERIFY setting for a SCRIPT file type is 1-132. To display only columns 1-72 of each line, thereby preventing lines longer than 72 characters from wrapping around to the next screen line, you could issue SET VERIFY 1 72. (You could then use a RIGHT subcommand to view the columns of data extending past column 72.)
The message lines or reserved lines may effect the number of wrapped lines that are displayed.
Automatic line wrapping is not available on vertical screens.
In a GUI environment, to improve performance choose a verify setting that prevents automatic line wrapping.
- For typewriter terminals, the maximum verify width is 132.
- Adding characters or blanks using the terminal's Insert key will result in lost data. Use XEDIT
subcommands, such as CINSERT to avoid lost information. For example, if you specify
v 1 20and the result is:|....+....1....+....2....+....3....+....4....+ 00001 This is an example oInserting the characters '1. ' using the terminal's Insert key and pressing the Enter key would result in:|....+....1....+....2....+....3....+....4....+ 00001 1. This is an examplThe characters 'e o' will no longer be contained in the line and will not be displayed even if the verify columns are expanded to display additional columns. For more information on the CINSERT subcommand, see CINSERT.
Messages and Return Codes
- 009E
- Column nn exceeds record length (nn) [RC=5]
- 520E
- Invalid operand: operand [RC=5]
- 545E
- Missing operand(s) [RC=5]
- 575E
- Invalid [argument or] {JOIN|SPLIT|TABS|VERIFY|ZONE} column(s) defined [RC=5]
- 576E
- {Total verify width exceeds screen size (nn)|Total offset exceeds LRECL (nn)} [RC=5]
- 581E
- Subcommand is not valid in extended mode [RC=3]
where return codes are:
- 0
- Normal
- 3
- Subcommand is not valid in extended mode
- 5
- Invalid or missing operand(s)
- 6
- Subcommand rejected in the profile due to LOAD error, or QUIT subcommand has been issued in a macro called from the last file in the ring
