YYYYUUUUUKKK for sure! <g>
What dolt would design a Payroll that does all of it's thinking while
producing checks? I suppose more than one. :)
Our Payroll application does all of the calculations first and the print
job does just that, print. Posting happens afterwards. So I can see
where the design of the application would create additional
I was trying to point out that sometimes there are very simple solutions
that are often overlooked.
At the places I work at, they all have a dedicated printer for Payroll.
Not only do they not want others to see the paychecks, they also don't
want others to see any payroll reports. The same for financial
reports. In those cases, what you described is necessary to secure
John Earl wrote:
> Would a little less "learned response" suit you? Howz this?
> James W Kilgore wrote:
> > Don't spool checks. End of problem.
> YUKKKKKKKKKKKKKKKKKKKK!!! <g>
> You mean if that I have to tie up my printer for the length of the payroll
> print portion of the job that now takes 15 minutes will now take 1.5 hours
> system does all its calculation between each check print. Once the job
> one else can use the printer until that job is done, and the payroll clerk
> gaurd the printer for the next 1.5 hours? Yuk!
> What if the payroll job already runs for 5+ hours (seen it... infinium
>software in a
> 5000 person company)? YUKKKKKKK!
> What if the payroll job is scheduled to run after 5:00pm or overnight? Does
> payroll clerk have to stay until it's done (can't have the operators looking
> checks)? Ewwwwww!!
> What happens if there is a forms jam or an imbalance in the audit report?
> printed 150 (or 5000???) checks that you now have to void. Ouch!
> Naw, spooling is a definite improvement, use it. Spend X hours up front
> understanding OS/400 security and you won't burn (X * 4) manhours a month
> someone to be the Payroll Printer Police.
> > Too short? <g>
> Way! <g>
| 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: email@example.com
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