There are references to DPA at the end of the first paragraph and again in
the second to last paragraph. Are these really needed? Can't this document
stand on its own without DPA?
Under "User" it says "No attempt is made to actually predict the length of
time that jobs will take." Then, under "Operator" it says "Provide some
idea of how long each job will take." Aren't these contradictory?
Bob Pentecost
HP
----------
From: Ron Bergman[SMTP:rbergma@dpc.com]
Sent: Saturday, February 15, 1997 6:14 AM
To: jmp@pwg.org
Subject: JMP> Major Revision to MIB Introduction
I have completed a major rewrite of the Introduction/Goals sections
of the Job Monitoring MIB. Sorry for the uglyness of the IS: part.
I will save of copy of this on the ftp server if anyone requests.
IS:
-----------------------------------------------------------------------
<deleted>
-----------------------------------------------------------------------
CHANGE TO:
-----------------------------------------------------------------------
Introduction
The Job Monitoring MIB is intended for use by an agent within a printer
or the first server closest to the printer, where the printer is either
directly connected to the server only or the printer does not contain
the job monitoring MIB agent. It is recommended that implementations
place the SNMP agent as close as possible to the processing of the print
job. This MIB applies to printers with and withoutspooling
capabilities. This MIB is designed to be compatible with most current
comonly used job submission protocols. In most environments that
support high function job submission/job control protocols, like ISO
DPA, those protocols would be used to monitor and manage print jobs
rather than using the Job Monitoring MIB.
The job MIB is intended to provide the following information for the
indicated Role Models (Refer to RFC 2XXX, Appendix D - Roles of Users).
User:
Provide the ability to identify the least busy printer. The user
will be able to determine the number and size of jobs waiting for
each printer. No attempt is made to actually predict the length of
time that jobs will take.
Provide the ability to identify the current status of the job (user
queries).
Provide a timely notification that the job has completed and where
it can be found.
Provide error and diagnostic information for jobs that did not
successfully complete.
Operator
Provide a presentation of the state of all the jobs in the print
system.
Provide the ability to identify the user that submitted the print
job.
Provide the ability to identify the resources required by each job.
Provide the ability to define which physical printers are candidates
for the print job.
Provide some idea of how long each job will take. However, exact
estimates of time to process a job is not being attempted. Instead,
objects are included that allow the operator to be able to make
gross estimates.
Capacity Planner:
Provide the ability to determine printer utilization as a function
of time.
Provide the ability to determine how long jobs wait before starting
to print.
Accountant:
Provide information to allow the creation of a record of resources
used and printer usage data for charging users or groups for
resources used.
The MIB will support printers that can contain more than one job at a
time, but still be usable for low end printers that only contain a
single job at a time. In particular, the MIB shall support the needs of
Windows and other PC environments for managing low-end networked devices
without unnecessary overhead or complexity, while also providing for
higher end systems and devices.
The MIB will provide job resource accounting information after the
printer has finished printing the job. This resource accounting
information is intended to be used by:
- A management station that is co-located with the printer to provide
an enhanced console capability.
- End user job monitoring programs that provide status on progress and
completion of jobs during the complete life cycle of the job, ncluding
a defined period after the job completes.
- System accounting programs that copy the completed job statistics to
an accounting system. It is recognized that depending on accounting
programs to copy MIB data during the job-retention period is somewhat
unreliable, since the accounting program may not be running (or
may have crashed).
The MIB provides a set of objects that represent a compatible subset of
job and document attributes of the ISO DPA standard, so that coherence
is maintained between the two protocols and information presented to
end users and system operators. However, the job monitoring MIB is
intended to be used with printers that implement other job submitting
and management protocols, such as IEEE 1284.1 (TIPSI), as well as with
ones that do implement ISO DPA. So nothing in the job monitoring MIB
shall require implementation of the ISO DPA protocol.
The MIB is designed so that an additional MIB(s) can be specified in the
future for monitoring multi-function (scan, FAX, copy) jobs as an
augmentation to this MIB.
----------------------------------------------------------------------
Ron Bergman
Dataproducts Corp
rbergma@dpc.com
(805)578-4421