BNDS - Display Bounds Line
Syntax
BNDS | BND |
Operands
|
None |
Description
The BNDS line command provides an alternative to setting the boundaries with the BOUNDS primary command; the effect on the data is the same. However, if you use both the BOUNDS primary command and the BNDS line command in the same interaction, the Primary command overrides the Line command.
The BNDS definitions remain in effect, even if they are not displayed, until you change them. BNDS definitions are retained as part of the file type PROFILE, and are automatically used the next time you edit the same kind of data (based on the EFT specification).
To display the boundary definition (=BNDS>) line:
- Type BNDS in the line command area of any unflagged line.
- Press Enter
- The boundary definition line is inserted.
To change the BOUNDS settings:
Note: You can use the COLS line command with the BNDS line command to help check and reposition the BOUNDS settings. The COLS line command displays the column identification line.
- Delete a < or > or + marker. The < marker shows the left BOUNDS setting and the > marker shows the right BOUNDS setting. If no > marker is specified, it is taken to mean MAX for the right boundary.
- Move the cursor to a different location on the =BNDS> line.
- Retype the deleted marker or markers. Note: The < character must be typed to the left of the > character.
- Press Enter.
- The new BOUNDS settings are now in effect.
To revert to the default settings:
- Display the boundary definition line. Blank out its contents with the Erase EOF key, the cursor, or the Del (delete) key.
- Press Enter.
- The default boundary settings will take effect.
To remove the boundary definition line from the display:
Note: If you delete the =BNDS> line, it merely gets rid of the display of the bounds information on that line. The bounds specification defined by that =BNDS> line is still in effect. If you want to get rid of the specification, apply the steps to "revert the default settings.
A word about the use of BOUNDS
The BOUNDS feature of ISPF is one that IBM did not extensively document, and in practice, mainframe ISPF users do not tend to use this feature very often. Every effort was made to implement BOUNDS in SPFLite in an ISPF compliant manner. However, it may produce surprising and unexpected results if you are not familiar with the actions taken by various commands when operating under restricted column BOUNDS. The "surprising and unexpected" aspect is even more of a factor for SPFLite users without a prior mainframe ISPF background.
For many users, you will likely get the most benefit from SPFLite by operating in unbounded mode most or all of the time, and not worry about using BOUNDS unless you have very particular editing requirements.
Note: When the BOUNDS setting is anything other than MAX, the status line display will show the BOUNDS setting in white letters on a red background, like Bnds: 1 to 40 so that it can't be ignored. This will help users to avoid the unexpected and nonstandard handling of data that occurs when non-default bounds are in effect, if that was not their intent.