When editing a large element the software will use browse even when view has been defined
If the data set is too large, ISPF browses it instead of viewing it as browse takes less resources.
In the case when BROWSE is being substituted for VIEW, it is ISPF objecting to the size of the file.
One hint is to check the User Defaults and make sure that the list dataset Record length is NOT allowed to default to 0.
Instead use a record size like 133 or 200 as in the screen shot below. This will stop Endevor using full track blocking, which
in turn causes VIEW to estimate the maximum memory size required to VIEW a listing as just 200xNum_of_records (rather than 32KxNum_of_records).
Remember if they change the defaults they may need to exit Endevor and re-start if the list dataset is already allocated.