[mailto:[EMAIL PROTECTED] On
Behalf Of Fred Schmidt
Sent: Wednesday, June 21, 2006 10:20 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SDSF poor performance when using SB or SE on a running job's
output
Have any of you noticed poor performance in SDSF when you use the SB or
SE
action characters to view
The way I've always understood this is that SDSF schedules an SRB into the
target address space to get spool data in buffers.
The difference between S (SDSF Browse) and the SB/SE (ISPF
Browse/Edit) line commands is that with the latter commands, all the data
is probably fetched up front. With
Brian Peterson wrote:
The way I've always understood this is that SDSF schedules an SRB into the
target address space to get spool data in buffers.
Not in any supported release. (Specifically, not since z/OS 1.2.)
The difference between S (SDSF Browse) and the SB/SE (ISPF
Browse/Edit)
Thanks for the feedback.
Unfortunately, none of it explains what we are seeing, as the address
space whose SDSF output was being browsed was a CICS region. The region
was active and consuming CPU. CICS is started as a started task here and
by virtue of ISC communication with other regions, is
Have any of you noticed poor performance in SDSF when you use the SB or SE
action characters to view a running job's output?
When I do a FIND in a job with only 666 lines, it takes at least 6 seconds
to respond. Compare that with subsecond response for the same FIND command
when using the S
5 matches
Mail list logo
