Why does REVIEW trap TSO attention interrupts?
(Added Oct 2004) A: When REVIEW detects an attention interrupt operations such as scrolling, searching, directory reading, directory sorting, and file offloading are terminated so that the user can have an opportunity to enter a new request more quickly. Because REVIEW does not terminate the whole session the user can often use this facility to gauge progress, and resume the operation if appropriate. Sometimes the user can initiate a new more efficient request. Suppose a request such as f varying is issued for a very large file. The user might realise that this will take “too long”. By interrupting the search, and issued the new request f c’VARYING’ the user will trigger a much more efficient search – one which searches for upper case text only.
