I'm creating an XML file in \TMP on the IFS.
I have DAZzle running on a PC to print endicia postage from the XML files.
DAZzle (runnin in Win7) is monitoring the \TMP file once every 30 seconds.
DAZzle is now able to read and delete the files the way it should.
The AS/400 creates a job called QZLSFILE which handles NetServer file transfers.
(that I learned from Simon) every time DAZzle looks to see if there is an XML file to
be processed once every 30 seconds. At this moment the DAZzle software has been
running 10 min and there are 20 jobs called QZLSFILE. An example of a job log is here:
http://pastebin.com/MtMJTE4H
What would be the best way to tune QZLSFILE prestart jobs?
Currently I have:
Start Jobs *Yes
Initial number of jobs 1
Threshold 1
Additional number of jobs 5
Maximum number of jobs *NOMAX
Maximum number of uses 200
Wait for job *Yes
I ended the DAZzle program.
The DSPACTPJ shows:
Prestart jobs:
Current number 3
Average number 3.3
Peak number 32
Prestart jobs in use:
Current number 1
Average number 1.1
Peak number 31
Program start requests:
Current number waiting 0
Average number waiting .0
Peak number waiting 0
Average wait time 0
Number accepted 31
Number rejected 0
These jobs most of the time will have nothing to do. It will be DAZzle just looking for a
file and not finding anything. I'm guessing that maybe four times a day it will read a
small file. Once a month there will be about 800 files to read. They don't need to
process very quickly because when each XML file is read off the 400 the PC will print an
envelope at the rate of about 12 per min.
I realize I have to change the Maximum number of jobs from *nomax to something
reasonable. I realize I will have to adjust the figures when I start running the monthly
job.
Does anyone have any guesses as to where I should start in adjusting the numbers?
Thanks,
Gary
It's running v4r4
Win7 ultimate
Thank you,
Gary
As an Amazon Associate we earn from qualifying purchases.