VIEW should have the same support as BROWSE for working with OPEN data sets

We are using ISPF VIEW to filter events in an open LDAP LOG data set (in use by LDAP) for example.
After a certain runtime from LDAP, and using ISPF VIEW to filter messages, VIEW terminates with I/O error during opening the LOG.
ISPF BROWSE is getting also I/O errors, but is able to handle this and we can see all messages in LOG.
Since ISPF VIEW has the capability to filter, we are very interested to integrate the same functionality as ISPF BROWSE has today into VIEW.

We have created PMR 33749,077,724 to analyze the I/O error in detail.
ISPF level2 came to the statement: The termination of VIEW is expected in case of I/O error (see 1). BROWSE has a different behaviour (see 2).

Here the details ISPF found:
1) ISPF VIEW calls ISPCDG to read the data:
- Both EDIT and VIEW read the entire file into storage.
- In case of I/O error ISPCDG SYNAD routine gets control.
ISPCDG SYNAD does: Close/Open and return to caller (VIEW).
- VIEW recognize I/O error and closes the DS per DESIGN.
This means: VIEW terminates after I/O error, this is the current logic in VIEW code.
2) ISPF BROWSE on the other hand only reads the data and itt uses the same interface:
BROWSE calls also ISPCDG to read the data.
- In case of I/O error ISPCDG SYNAD does exactly the same:
It Close/Open and return to caller (BROWSE).
- But BROWSE doesn't close the DS, instead it continues.
This means: BROWSE shows I/O error but can be used to read the data.