> What would cause > commands that work with jobs to perform _very_ slowly? WRKACTJOB isn't bad, > nor is WRKUSRJOB, but WRKSBMJOB and WRKSBSJOB can take five minutes to come > up. What's up with that? Most common reason for these commands to work slowly: - job tables are heavily fragmented and take up too many disk extents - job tables are located on a disk drive(a) with high contention Both of these can be remedied by forcing system to reallocate and compress job tables. Set system values QTOTJOB and QADLTOTJOB appropriately, use CHGIPLA to set system to compress job tables and reIPL (this applies to V4Rx.) Before doing this, it will be wise to get rid of old jobs, which have unneeded spool files lingering in output queues. Best regards Alexei Pytel +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.