I believe that if a tray is out of paper, then something should be reported in
the host resources table. It has been my experience that is better to provide
as much information as possible and then let the management app decide. We
should however, try to clear up as much of the mib as possible.
What should be reported in the following situations: a priner has legal in a
200 sheet tray but the two thousand sheet tray that is supposed to have letter
in it is empty. If a job want letter paper then in all probablity the printer
is going to stall waiting for letter to be loaded. If the printer has stalled
then it is in an error state, no paper. But what about if it is not stalled
waiting on the tray(say it pick the last sheet as the last page of the previous
job)? If the three hr variables are supposed to reflect the state of the
printer, and a management app is looking to those variable to keep it informed,
then they must report somethng, but what is the right answer?
Gail
On Jan 23, 10:38am, Bill Wagner wrote:
> Subject: Re: PMP> Paper Out with Tray linking - Alerts
>
> Certainly, the most useful outcome of the MIB testing should be an
> understanding of common usage, details which are not/cannot be fully
> documented but which should be handled in a uniform manner.
>
> Harry's question appears to me to relate to the more general question
> of 'printer' versus 'subunit'. If a printer has paper that can be
> used, it makes no difference that a particular tray may be out. The
> status of a given tray should be reported under the input subunit
> status indexed to that tray.
>
> The criteria for low paper is not explicit, so that the user may or
> may not report printer low paper under this condition. This fuzziness
> is perhaps appropriate to a warning condition. Certainly, it would be
> hard to quantify what constitutes a paper low condition.
>
> Paper out is somewhat easier to define. But to flag a paper out
> warning for a *printer* when the printer still has paper would seem to
> be very confusing.
>
> Although the February test will have lots to do, I think the handling
> of subunit status is a fairly wide open area for checking consistency.
>
> Bill Wagner, DPI
--Gail Songer Electronics For Imaging gail.songer@eng.efi.com 2855 Campus Drive (415) 286-7235 San Mateo, CA 94403