• Subject: RE: WRKJOB commands
  • From: Terry Richardson <RichardsonT@xxxxxxxxx>
  • Date: Wed, 24 Mar 1999 07:38:41 -0500

Thank you very much for this information.  I have been trying to get an
answer to this dilemma for some time, and this is the first time someone
has taken the time to fully explain what is going on and how to remedy
it.  Again, my sincere thanks.

Terry Richardson

> -----Original Message-----
> From: pytel@us.ibm.com [SMTP:pytel@us.ibm.com]
> Sent: Tuesday, March 23, 1999 4:38 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: WRKJOB commands
> 
> WRKxxJOB commands work by sequentially scanning WCBT (Work Control
> Block
> Table - job control structures on AS/400). If it takes a lot of time,
> it
> indicates that WCBT is heavily fragmented.
> Two things can be done: compress WCBT or force WCBT recreation.
> To compress WCBT:
>  -   create data area:
>           CRTDTAARA DTAARA(QSYS/QWCBTCMPTB) TYPE(*CHAR) LEN(1)
> 
>      The following command will then turn on the compression of the
> WCBT
> during the IPL:
> 
>           CHGDTAARA DTAARA(QSYS/QWCBTCMPTB) VALUE('1')
> 
>      The following command will then turn off the compression of the
> WCBT
> during the IPL:
> 
>           CHGDTAARA DTAARA(QSYS/QWCBTCMPTB) VALUE('0')
> 
> To force WCBT recreation, perform manual IPL from system console, and
> on
> one of the menus you can request WCBT recreation.
>  It will remove all jobs from system, including all spool files.
> Two system values, which control WCBT allocation are QTOTJOB (initial
> allocation) and QADLTOTJOB (increment).
> 
> Best regards
>     Alexey Pytel
> 
> 
> 
> Terry Richardson <RichardsonT@ORVIS.com> on 03/23/99 01:41:38 PM
> 
> Please respond to MIDRANGE-L@midrange.com
> 
> To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
> cc:    (bcc: Alexei Pytel/Rochester/IBM)
> Subject:  WRKJOB commands
> 
> 
> 
> 
> 
> Our shop has 3 AS/400's, a 170, a 530 and an older F45. The F45 is
> running V3R2. When any job related command is issued (WRKUSRJOB,
> WRKJOB,
> WRKSBMJOB, etc.) they take seemingly FOREVER to respond. Generally,
> the
> response time is 35 to 45 seconds. This only started happening when
> V3R2
> was loaded. The machine is strictly for development and never has more
> than 2 or 3 users logged on. Is there any remedy for this situation? I
> don't think it is a tuning issue, since all other commands respond
> well.
> I seem to remember someone saying once that certain job information
> may
> be stored in a compressed format and the 'decompression' may be
> responsible for the slow response, but haven't been able to confirm
> this. Any feedback on this would be MUCH appreciated.
> 
> +---
> | 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:
> david@midrange.com
> +---
> 
> 
> 
> +---
> | 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:
> david@midrange.com
> +---
+---
| 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: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].