Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ISPF 3.4 SORT

26 views
Skip to first unread message

Martin Leist

unread,
Apr 12, 1999, 3:00:00 AM4/12/99
to
I too experience long response time when using the SORT within a
3.4. I always assumed that "that was the way it was", but maybe
there is a problem ?

At OS/390 1.3 for a 3390-3 with 353 datasets it takes less than
4secs to do 3.4 with VOLUME view or about 8 secs with TOTAL
view. Once the table is displayed it takes over 1minute 45 seconds
for the first SORT TRACKS in either of the two entry types.
Subsequent SORTs, even with multiple fields are sub-second. Surely
the SORT has all the infomation it needs to do the sort after using
the TOTAL view, so why should it take so long ?


On 12 Apr 99, at 11:21, g...@US.IBM.COM wrote:

> We use SYNCSORT to perform are batch sorts and I'd like to know
> >if ISPF would be using the sort provided by SYNCSORT or is it
> >using it's own sort(maybe DFSORT). If anyone has experienced
> >a similar problem or knows the answer please advise.....
>
> ISPF does not use *any* external sort product when sorting a list. It is
> all done internally.
>
> Are you sure it is the sort taking the time, or is it the accessing of the
> VTOC to get the full dataset data to sort? Greg
>
> Greg Dyck MVS BCP Kernel & CURE Support


--
Martin Leist
Technical Analyst
Itex, Norfolk County Council (UK) Email: Martin.l...@norfolk.gov.uk

Doug Nadel

unread,
Apr 12, 1999, 3:00:00 AM4/12/99
to
Actually, it only gets the info needed to display 1 screen. Then when
you do a SORT, it goes out and gets the rest.

-Doug

On 12 Apr 1999 08:57:48 -0700, martin.l...@norfolk.gov.uk

Thomas Conley

unread,
Apr 12, 1999, 3:00:00 AM4/12/99
to
Based on work I've done with ISPF Level 2, we have discovered degenerate
cases in ISPF 3.4 that will cause widely scattered response times for 3.4.
While the degenerate cases are very specific in nature, they can be common
to many sites. I'm sure Doug Nadel was unable to comment directly about
this, but it is being worked on. Unfortunately there are many requisites to
this maintenance before it can be released. Many modules and ISPF services
are involved, so there will be extensive integration testing. It may be a
while, but as soon as ISPF has published the APARs, I will post to the
group.

--
Regards,
Thomas Conley, President
Pinnacle Consulting Group, Inc.
To reply, remove 'consult' from my Email address

Martin Leist wrote in message
<1999041215...@imail.norfolk.gov.uk>...


I too experience long response time when using the SORT within a
3.4. I always assumed that "that was the way it was", but maybe
there is a problem ?

At OS/390 1.3 for a 3390-3 with 353 datasets it takes less than
4secs to do 3.4 with VOLUME view or about 8 secs with TOTAL
view. Once the table is displayed it takes over 1minute 45 seconds
for the first SORT TRACKS in either of the two entry types.

Subsequent SORTs, even with multiple fields are sub-second. Surely


the SORT has all the infomation it needs to do the sort after using
the TOTAL view, so why should it take so long ?

Bob Negron

unread,
Apr 19, 1999, 3:00:00 AM4/19/99
to
Bob Negron@ABIG
04/19/99 02:20 PM
We didn't make any changes to our hardware configuration when we went to
OS/390 so I don't believe it's our dasd. We have 2 IBM T82 RVA's and our
response time has been very good. I retried the sort and kept an eye on
response time of the particular volume I was sorting using TMON/MVS and it
was averaging 2 milisecond response time during the sort. I'm at a
loss....

Date: Mon, 12 Apr 1999 17:04:04 GMT
From: Doug Nadel <some...@MINDSPRING.COM>
Subject: Re: ISPF 3.4 SORT

Actually, it only gets the info needed to display 1 screen. Then when
you do a SORT, it goes out and gets the rest.

-Doug

On 12 Apr 1999 08:57:48 -0700, martin.l...@norfolk.gov.uk
(Martin Leist) wrote:

0 new messages