|
Thanks for all the replies - just after I wrote the question, I left town for a few days and forgot I even asked it until today, when I tried WRKSBMJOB again. I'll look into DSPJOBTBL. thanks, Rick On 4/28/06, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx> wrote:
No, don't increase..... OS400 will automatically allocate additional "permanent job structures" as it needs them. The problem comes when a command is run that searches through the job tables. If there are many table entries, the search is slow... The correct fix is to decrease the number of job table entries. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-297-2863 or ext. 1863 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Al Mac Sent: Friday, April 28, 2006 10:31 AM To: Midrange Systems Technical Discussion Subject: RE: WRKSBMJOB taking a long time. DSPJOBTBL ... you may need to increase how many are out there. >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 > > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.