A logical file does not contain any data. It simply provides services such as indexing, data mapping, etc so that the data stored in the physical file can be access and worked with in a different manner. In general when the physical file data is updated, the logical file immediated reflects this change.
If you want a static view of the underlying data, perhaps for query purposes, the typical approach is to periodically duplicate/copy the physical file and then run queries against logical files built over the static copy.
Logical files do provide some limited capabilities in terms of the underlying data that is seen. If in your update of the physical you set a field to a particular value, then the logical file could have select/omit definitions based on that field that could make the new record not accessible through the logical file. In this case you wouldn’t see the change, but you also wouldn’t see the original data (as it’s no longer there).
Commitment control can be used to restrict access to a change in the physical file until the transaction is committed but again, once the change is committed, the logical file will reflect that change.
What is it you are trying to do? Logical files are intended to provide flexibility over real time data. In your case it sounds like you want a static view of the data, suggesting the need to make a copy of the underlying data.