[  [ left-col ] { right-col | MAX }  ]



If the left column boundary is omitted, it is assumed to be 1.

right-col |



The right column boundary to be set or the Keyword 'MAX' or + to indicate the maximum record length.

You cannot specify the same column for both boundaries. .

If you specify BOUNDS MAX or BOUNDS 1 MAX, you will see a bounds display on the status line of Bnds: MAX. When this is in effect, you can describe this as "edit columns are unbounded" or "the editor is in unbounded mode".

If you specify BOUNDS n MAX, where n is any value higher than 1, you will see a bounds display on the status line of Bnds: n to MAX

Abbreviations and Aliases

BOUNDS can also be spelled as BOUND, BNDS, BND or BOU



The BOUNDS primary command provides an alternative to setting the boundaries with the BNDS line 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 left column boundary number is optional, and if omitted, it is assumed to be 1.

To reset the boundaries to the default column (1 and Max Record Length):

    1. On the command line, type:  BOUNDS or BOUNDS MAX

    1. Press Enter

    1. The boundaries are reset to the defaults.

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.

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.

Created with the Personal Edition of HelpNDoc: Full-featured Help generator