Fred, I have noticed the same issue, and it appears that SDSF is executing code that runs with the same dispatching priority as the address space it is querying.
In a CPU-constrained environment, I can re-create this by browsing a low-priority running job's output, and the response is poor. I can then change the dispatching priority of the same job and the response is excellent. I can then reverse the priority and it reverts back. You have the source of SDSF and can investigate why if you need additional information. Tom -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Fred Schmidt Sent: Wednesday, June 21, 2006 10:20 PM To: [email protected] 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 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 action character to view the same output. If you are looking at a job with a significant number of lines of output, you may as well come back after lunch! The initial entry to view the job's output with SB or SE is also very slow. This poor performance only occurs when viewing the output from a job that is running. For jobs that have ended, performance is normal. We see this on both z/OS 1.4 and 1.7. It doesn't make any difference whether we look at job output from the DA panel or the ST panel. Regards, Fred Schmidt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
