Difference between revisions of "Where is my report?"
From MidrangeWiki
m |
(→Understand Queues) |
||
| Line 5: | Line 5: | ||
One of the biggest issues for new users coming from an environment of stand-alone PCs, is a failure to recognize the implications of network queues. | One of the biggest issues for new users coming from an environment of stand-alone PCs, is a failure to recognize the implications of network queues. | ||
| + | |||
| + | A new user, unaccustomed to a multi-user system, is accustomed to doing SOMETHING, then IMMEDIATELY expecting to find the results on the printer. But | ||
| + | * Their task might still be in JOBQ. | ||
| + | * Their report might not print until someone else's report has finished printing. | ||
| + | * Their reports might be going to an OUTQ that does not have an attached printer writer. | ||
| + | * If they slow to get to printer, relative to when report prints, someone else may have torn it off and set it aside, or accidentally when tear off reports, a user goes off with THEIR report(s) with someone else's attached. | ||
== Where 400 places report == | == Where 400 places report == | ||
Revision as of 01:49, 9 June 2005
When we have lots of users with lots of reports for lots of printers, this can be a problem.
Understand Queues
One of the biggest issues for new users coming from an environment of stand-alone PCs, is a failure to recognize the implications of network queues.
A new user, unaccustomed to a multi-user system, is accustomed to doing SOMETHING, then IMMEDIATELY expecting to find the results on the printer. But
- Their task might still be in JOBQ.
- Their report might not print until someone else's report has finished printing.
- Their reports might be going to an OUTQ that does not have an attached printer writer.
- If they slow to get to printer, relative to when report prints, someone else may have torn it off and set it aside, or accidentally when tear off reports, a user goes off with THEIR report(s) with someone else's attached.
