This is one of those IIRC posts. I think this behavior goes back decades. The reason is as Kolusu states. Moreover--IIRC--the very appearance of the 'progress bar' was in response to what could be a long delay. Delay to the point that the user might suspect that the process was hung outright. I remember when the bar was introduced with that very explanation. Everything in those distant days was slower than today.
As for the difference in processing, I could imagine an RFE asking for a 'quick sort' based only on the data previously collected and displayed. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Sri h Kolusu Sent: Tuesday, October 13, 2020 9:47 AM To: [email protected] Subject: (External):Re: ISPF dsn sort CAUTION EXTERNAL EMAIL > I can use ISPF 3.4 to display a set of data sets. > Given that the DSORG was already displayed, why does ISPF go and > collect the same information again? 3.4 listing shows the list of datasets sorted on the Dataset name by default. Now when you issue SORT DSORG command , ISPF needs to read in the list once again and make DSORG as the primary key and then present you the list sorted on that order. You will Thanks, Kolusu ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
