RE: WRKSBMJOB taking a long time.

DSPSYSSTS.  How many jobs are on the system?  We're running a pretty
sturdy 570.  Even at off-peak times it can take 10-15 seconds to pull up
WRKSBMJOB.  We have over 60,000 jobs on the system.  I would venture a
guess that the OS is digging through the job tables, and it isn't using
an efficient retrieval method.

Q:      How do you delete a spool file?

A:      Print it and throw it away.


-Jim


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick baird
Sent: Thursday, April 27, 2006 12:01 PM
To: Midrange Systems Technical Discussion
Subject: WRKSBMJOB taking a long time.

Would any of you have an idea why a simple WRKSBMJOB command (no
parms) would take 15-20 seconds to load?

When I run it, it only displays 2 entries and it doesn't seem to make
a difference who runs it, it takes forever.

refresh takes as long as well.

I've been on busier systems than this, so it doesn't seem to make any
sense to me.

Thanks,

Rick