On 02/05/2018 10:49 AM, Peter Hunkeler wrote: >>> VIEW/EDIT should really learn to work in a window mode, so larger data sets >>> can be viewed/edited. > > >> Or use storage above the bar. > > > I'm not a fan of this. How much would you allow it to use? Loading a huge > data set into the editor would allocate a huge number frames, just to drop > them shortly (whatever that means) thereafter. > > > -- > Peter Hunkeler And on heavily loaded systems, even if getting enough real frames to back a huge temporary spike in the session's virtual memory working set weren't an issue, the CPU usage and I/Os to read an entire huge multi-volume data set into virtual memory could make the TSO session appear to die from the users standpoint for a very long time. In my experience, for most users, having the editor fail from insufficient space below the 2G bar was actually a better outcome than an apparently-dead session trying to read the entire data set when the user attempted to edit a huge data set either accidentally or without realizing the resources they were requesting. If they really needed to edit a small piece of a huge data set, there were generally better approaches than trying to use the ISPF Editor directly.
A windowed-edit capability for large files would be a nice alternative, but it would also be useful that it warn the user when requesting operations that could potentially require reading through a large part of a large file just to be sure that a potentially time-intensive, resource-intensive operation is what the user really intended and requires before proceeding -- and there may still be more-efficient, alternative ways to achieve the desired result using other utilities. Joel C Ewing -- Joel C. Ewing, Bentonville, AR [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
