draft-ietf-printmib-job-monitor-00.txt   draft-ietf-printmib-job-monitor-01.txt 
Job Monitoring MIB, V0.81 April 24, 1997
INTERNET-DRAFT Job Monitoring MIB, V0.82 June 9, 1997
Ron Bergman
INTERNET-DRAFT Ron Bergman
Dataproducts Corp. Dataproducts Corp.
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
Scott Isaacson Scott Isaacson
Novell, Inc. Novell, Inc.
Harry Lewis Harry Lewis
IBM Corp. IBM Corp.
Job Monitoring MIB - V0.81 Job Monitoring MIB - V0.82
<draft-ietf-printmib-job-monitor-00.txt>
Expires Oct 24, 1997 <draft-ietf-printmib-job-monitor-01.txt>
Expires Dec 10, 1997
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 36 skipping to change at page 1, line 38
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet-Draft specifies a set of 13 SNMP MIB objects for (1) This Internet-Draft specifies a set of 17 SNMP MIB objects for (1)
monitoring the status and progress of print jobs (2) obtaining monitoring the status and progress of print jobs (2) obtaining
resource requirements before a job is processed, (3) monitoring resource requirements before a job is processed, (3) monitoring
resource consumption while a job is being processed and (4) resource consumption while a job is being processed and (4)
collecting resource accounting data after the completion of a job. collecting resource accounting data after the completion of a job.
This MIB is intended to be implemented (1) in a printer or (2) in a This MIB is intended to be implemented (1) in a printer or (2) in a
server that supports one or more printers. Use of the object set server that supports one or more printers. Use of the object set
is not limited to printing. However, support for services other is not limited to printing. However, support for services other
than printing is outside the scope of this Job Monitoring MIB. than printing is outside the scope of this Job Monitoring MIB.
Job Monitoring MIB, V0.82 June 9, 1997
Future extensions to this MIB may include, but are not limited to, Future extensions to this MIB may include, but are not limited to,
fax machines and scanners. fax machines and scanners.
Job Monitoring MIB, V0.81 April 24, 1997 Job Monitoring MIB, V0.82 June 9, 1997
TABLE OF CONTENTS TABLE OF CONTENTS
1. INTRODUCTION 6 1. INTRODUCTION........................................................9
1.1 Types of Information in the MIB 6 1.1 Types of Information in the MIB ..................................9
1.2 Types of Job Monitoring Applications 7 1.2 Types of Job Monitoring Applications ............................11
2. TERMINOLOGY AND JOB MODEL 8 2. TERMINOLOGY AND JOB MODEL..........................................12
3. SYSTEM CONFIGURATIONS FOR THE JOB MONITORING MIB 10 3. SYSTEM CONFIGURATIONS FOR THE JOB MONITORING MIB...................14
3.1 Configuration 1 - client-printer 11 3.1 Configuration 1 - client-printer ................................15
3.2 Configuration 2 - client-server-printer - agent in the server 11 3.2 Configuration 2 - client-server-printer - agent in the server ...16
3.3 Configuration 3 - client-server-printer - client monitors printer 3.3 Configuration 3 - client-server-printer - client monitors printer
agent and server 13 agent and server ....................................................17
4. CONFORMANCE CONSIDERATIONS 14 4. CONFORMANCE CONSIDERATIONS.........................................18
4.1 Conformance Terminology 14 4.1 Conformance Terminology .........................................19
4.2 Agent Conformance Requirements 14 4.2 Agent Conformance Requirements ..................................19
4.2.1 MIB II System Group objects .................................19
4.2.2 MIB II Interface Group objects ..............................20
4.2.3 Printer MIB objects .........................................20
4.3 Job Monitoring Application Conformance Requirements 15 4.3 Job Monitoring Application Conformance Requirements .............20
5. JOB IDENTIFICATION 15 5. JOB IDENTIFICATION.................................................20
6. INTERNATIONALIZATION CONSIDERATIONS 16 6. INTERNATIONALIZATION CONSIDERATIONS................................21
7. IANA CONSIDERATIONS 17 7. IANA CONSIDERATIONS................................................22
7.1 IANA Registration of enums 17 7.1 IANA Registration of enums ......................................22
7.1.1 Type 1 enumerations .........................................22
7.1.2 Type 2 enumerations .........................................22
Job Monitoring MIB, V0.82 June 9, 1997
7.2 IANA Registration of type 2 bit values 18 7.1.3 Type 3 enumeration ..........................................23
7.3 IANA Registration of Job Submission Id Formats 18 7.2 IANA Registration of type 2 bit values ..........................23
8. SECURITY CONSIDERATIONS 18 7.3 IANA Registration of Job Submission Id Formats ..................23
8.1 Read-Write objects 18 8. SECURITY CONSIDERATIONS............................................24
8.2 Read-Only Objects In Other User's Jobs 19 8.1 Read-Write objects ..............................................24
9. RETURNING OBJECTS WITH NO VALUE IN MANDATORY GROUPS 19 8.2 Read-Only Objects In Other User's Jobs ..........................24
10. NOTIFICATION AND TRAPS 19 9. RETURNING OBJECTS WITH NO VALUE IN MANDATORY GROUPS................24
11. MIB SPECIFICATION 19 10. NOTIFICATION AND TRAPS............................................25
Textual conventions for this MIB module 20 11. MIB SPECIFICATION.................................................25
JmTimeStampTC - simple time in seconds 20
JmJobSourcePlatformTypeTC - operating system platform definitions21
Job Monitoring MIB, V0.81 April 24, 1997
JmFinishingTC - device finishing definitions 21 Textual conventions for this MIB module .............................27
JmPrintQualityTC - print quality 23 JmTimeStampTC - simple time in seconds ............................27
JmTonerEconomyTC - toner economy setting 23 JmJobSourcePlatformTypeTC - operating system platform definitions .27
JmMediumTypeTC - medium type definitions 23 JmFinishingTC - device finishing definitions ......................28
JmJobStateTC - job state definitions 24 JmPrintQualityTC - print quality ..................................29
JmAttributeTypeTC - attribute type definitions 27 JmPrinterResolutionTC - printer resolution ........................30
other 29 JmTonerEconomyTC - toner economy setting ..........................31
unknown 30 JmMediumTypeTC - medium type definitions ..........................31
Job State attributes 30 JmJobStateTC - job state definitions ..............................32
jobState (mandatory) 30 JmAttributeTypeTC - attribute type definitions ....................35
jobStateAssociatedValue 30 other ..........................................................38
jobStateReasons1 31 unknown ........................................................39
jobStateReasons2 31 Job State attributes.............................................39
jobStateReasons3 31 jobStateReasons2 ...............................................39
jobStateReasons4 31 jobStateReasons3 ...............................................39
numberOfInterveningJobs (mandatory) 32 jobStateReasons4 ...............................................39
deviceAlertCode (mandatory) 32 deviceAlertCode ................................................40
processingMessage 32 processingMessage ..............................................40
Job Identification attributes 32 Job Identification attributes....................................40
serverAssignedJobName 32 jobOwner (MANDATORY) ...........................................40
jobName 32 jobAccountName .................................................41
jobServiceTypes 33 serverAssignedJobName ..........................................41
jobOwner 33 jobName ........................................................41
jobAccountName 33 jobServiceTypes ................................................42
jobSourceChannelIndex 34 jobSourceChannelIndex ..........................................42
jobSourcePlatformType 34 jobSourcePlatformType ..........................................43
submittingServerName 34 Job Monitoring MIB, V0.82 June 9, 1997
submittingApplicationName 34
deviceNameRequested 34
queueNameRequested 34
physicalDeviceIndex 35
physicalDeviceName 35
numberOfDocuments 35
fileName 35
documentName 35
jobComment 35
documentFormatIndex 35
documentFormatType 36
Job Parameter attributes 36
jobPriority 36
jobProcessAfterDateAndTime 36
jobHoldUntil 37
outputBinIndex 37
outputBinName (mandatory) 37
sides 37
finishing 37
Image Quality attributes (requested and used) 37
printQualityRequested 37
printQualityUsed 37
tonerEcomonyRequested 38
tonerEcomonyUsed 38
tonerDensityRequested 38
tonerDensityUsed 38
Job Progress attributes (requested and consumed) 38
jobCopiesRequested 38
Job Monitoring MIB, V0.81 April 24, 1997
jobCopiesCompleted 38 submittingServerName ...........................................43
documentCopiesRequested 38 submittingApplicationName ......................................43
documentCopiesCompleted 38 jobOriginatingHost .............................................43
jobKOctetsRequested (mandatory) 39 deviceNameRequested ............................................43
jobKOctetsTransferred (mandatory) 39 queueNameRequested .............................................44
jobKOctetsCompleted (mandatory) 40 physicalDevice .................................................44
Impression attributes (requested and consumed) 40 numberOfDocuments ..............................................44
impressionsSpooled 40 fileName .......................................................44
impressionsSentToDevice 41 documentName ...................................................45
impressionsInterpreted 41 jobComment .....................................................45
impressionsRequested (mandatory) 41 documentFormatIndex ............................................45
impressionsCompleted (mandatory) 41 documentFormat .................................................45
impressionsCompletedCurrentCopy 41 Job Parameter attributes.........................................46
Page attributes (requested and consumed) 41 jobPriority ....................................................46
pagesRequested 41 jobProcessAfterDateAndTime .....................................46
pagesCompleted 41 jobHoldUntil ...................................................47
pagesCompletedCurrentCopy 41 jobHoldUntil ...................................................47
Sheet attributes (requested and consumed) 42 outputBin ......................................................47
sheetsRequested 42 sides ..........................................................48
sheetsCompleted 42 finishing ......................................................48
sheetsCompletedCurrentCopy 42 Image Quality attributes (requested and used)....................48
Resource attributes (requested and consumed) 42 printQualityRequested ..........................................48
mediumRequestedType 42 printQualityUsed ...............................................48
mediumRequestedName 42 printerResolutionRequested .....................................48
mediumConsumedName 42 printerResolutionUsed ..........................................48
colorantRequestedIndex 42 tonerEcomonyRequested ..........................................49
colorantRequestedName 43 tonerEcomonyUsed ...............................................49
colorantConsumedIndex 43 tonerDensityRequested ..........................................49
colorantConsumedName 43 tonerDensityUsed ...............................................49
Time attributes (set by server or device) 43 Job Progress attributes (requested and consumed).................49
jobSubmissionToServerDateAndTime 43 jobCopiesRequested .............................................49
jobSubmissionToDeviceDateAndTime 43 jobCopiesCompleted .............................................50
jobSubmissionToDeviceTimeStamp 43 documentCopiesRequested ........................................50
jobStartedBeingHeldTimeStamp 43 documentCopiesCompleted ........................................50
jobStartedProcessingDateAndTime 43 jobKOctetsTransferred ..........................................50
jobStartedProcessingTimeStamp 44 Impression attributes (requested and consumed)...................51
jobCompletedDateAndTime 44 impressionsSpooled .............................................51
jobCompletedTimeStamp 44 impressionsSentToDevice ........................................51
jobProcessingCPUTime 44 impressionsInterpreted .........................................51
JmJobServiceTypesTC - bit encoded job service type definitions 44 impressionsCompletedCurrentCopy ................................52
JmJobStateReasons1TC - additional information about job states 45 fullColorImpressionsCompleted ..................................52
JmJobStateReasons2TC - More additional information about job states highlightColorImpressionsCompleted .............................52
48 Page attributes (requested and consumed).........................52
JmJobStateReasons3TC - More additional information about job states pagesRequested .................................................53
53 pagesCompleted .................................................53
JmJobStateReasons4TC - More additional information about job states pagesCompletedCurrentCopy ......................................53
54 Sheet attributes (requested and consumed)........................53
sheetsRequested ................................................53
Job Monitoring MIB, V0.82 June 9, 1997
The General Group (Mandatory) 56 sheetsCompleted ................................................53
jmGeneralNumberOfActiveJobs 56 sheetsCompletedCurrentCopy .....................................54
jmGeneralOldestActiveJobIndex 57 Resource attributes (requested and consumed).....................54
jmGeneralNewestActiveJobIndex 57 mediumRequested ................................................54
jmGeneralJobPersistence 58 mediumConsumedName .............................................54
jmGeneralAttributePersistence 58 colorantRequested ..............................................54
jmGeneralJobSetName 58 colorantConsumed ...............................................55
Job Monitoring MIB, V0.81 April 24, 1997 Time attributes (set by server or device)........................55
jobSubmissionToServerTime ......................................55
jobSubmissionToDeviceTime ......................................55
timeSinceJobWasSubmittedToDevice ...............................56
jobStartedBeingHeldTimeStamp ...................................56
jobStartedProcessingTime .......................................56
timeSinceStartedProcessing .....................................56
jobCompletedTime ...............................................56
timeSinceCompleted .............................................57
jobProcessingCPUTime ...........................................57
JmJobServiceTypesTC - bit encoded job service type definitions...57
JmJobStateReasons1TC - additional information about job states .59
JmJobStateReasons2TC - More additional information about job
states .........................................................62
JmJobStateReasons3TC - More additional information about job
states .........................................................66
JmJobStateReasons4TC - More additional information about job
states .........................................................67
The General Group (Mandatory)....................................69
jmGeneralNumberOfActiveJobs ....................................69
jmGeneralOldestActiveJobIndex ..................................70
jmGeneralNewestActiveJobIndex ..................................70
jmGeneralJobPersistence ........................................72
jmGeneralAttributePersistence ..................................72
jmGeneralJobSetName ............................................72
The Job ID Group (Mandatory) 59 THE JOB ID GROUP (MANDATORY)..........................................73
jmJobSubmissionIDIndex 60
jmJobSetIndex 61
jmJobIndex 61
The Job State Group (Mandatory) 61 JMJOBSUBMISSIONID.....................................................74
jmJobState 62
jmJobStateKOctetsCompleted 63
jmJobStateImpressionsCompleted 63
jmJobStateAssociatedValue 63
The Attribute Group (Mandatory) 64 JMJOBSETINDEX.........................................................75
jmAttributeTypeIndex 65
jmAttributeInstanceIndex 66
jmAttributeValueAsInteger 66
jmAttributeValueAsOctets 67
12. JOB LIFE CYCLE 70 JMJOBINDEX............................................................76
13. BIBLIOGRAPHY 71 THE JOB GROUP (MANDATORY).............................................76
Job Monitoring MIB, V0.82 June 9, 1997
14. AUTHOR'S ADDRESSES 71 JMJOBSTATE............................................................77
15. INDEX 74 JMJOBSTATEREASONS1....................................................78
Job Monitoring MIB, V0.81 April 24, 1997
JMNUMBEROFINTERVENINGJOBS.............................................78
JMJOBKOCTETSREQUESTED.................................................79
JMJOBKOCTETSPROCESSED.................................................79
JMJOBIMPRESSIONSREQUESTED.............................................80
JMJOBIMPRESSIONSCOMPLETED.............................................80
THE ATTRIBUTE GROUP (MANDATORY).......................................81
JMATTRIBUTETYPEINDEX..................................................82
JMATTRIBUTEINSTANCEINDEX..............................................82
JMATTRIBUTEVALUEASINTEGER.............................................83
JMATTRIBUTEVALUEASOCTETS..............................................84
12. APPENDIX A - INSTRUMENTING THE JOB LIFE CYCLE.....................87
13. APPENDIX B - SUPPORT OF THE JOB SUBMISSION ID IN JOB SUBMISSION
PROTOCOLS.............................................................88
13.1 Hewlett-Packard's Printer Job Language (PJL) ...................88
14. BIBLIOGRAPHY......................................................88
Job Monitoring MIB, V0.82 June 9, 1997
15. AUTHOR'S ADDRESSES................................................89
16. INDEX.............................................................92
Job Monitoring MIB, V0.82 June 9, 1997
Job Monitoring MIB Job Monitoring MIB
1. Introduction 1. Introduction
The Job Monitoring MIB consists of a 5-object General Group, a 2-object The Job Monitoring MIB consists of a 6-object General Group, a 2-object
Job Submission ID Group, a 4-object Job State Group, and a 2-object Job Submission ID Group, a 7-object Job Group, and a 2-object Attribute
Attribute Group. Each group is a table. The General Group contains Group. Each group is a table. The General Group contains general
general information that applies to all jobs in a job set. The Job information that applies to all jobs in a job set. The Job Submission
Submission ID table maps the job submission ID that the client uses to ID table maps the job submission ID that the client uses to identify a
identify a job to the jmJobIndex that the Job Monitoring Agent uses to job to the jmJobIndex that the Job Monitoring Agent uses to identify
identify jobs in the Job State and Attribute tables. The Job State jobs in the Job and Attribute tables. The Job table contains the
table contains the job state and copies of three salient attributes for mandatory integer job state and status objects. The Attribute table
each job's current state. The Attribute table consists of multiple consists of multiple entries per job that specify (1) job and document
entries per job that specify (1) job and document identification and identification and parameters, (2) requested resources, and (3)
parameters, (2) requested resources, and (3) consumed resources during consumed resources during and after job processing/printing. One
and after job processing/printing. The Job Monitoring MIB is intended MANDATORY attribute and 70 OPTIONAL attributes are defined as textual
to be instrumented by an agent within a printer or the first server conventions.
closest to the printer, where the printer is either directly connected
to the server only or the printer does not contain the job monitoring The Job Monitoring MIB is intended to be instrumented by an agent within
MIB agent. It is recommended that implementations place the SNMP agent a printer or the first server closest to the printer, where the printer
as close as possible to the processing of the print job. This MIB is either directly connected to the server only or the printer does not
applies to printers with and without spooling capabilities. This MIB is contain the job monitoring MIB agent. It is recommended that
designed to be compatible with most current commonly-used job submission implementations place the SNMP agent as close as possible to the
protocols. In most environments that support high function job processing of the print job. This MIB applies to printers with and
submission/job control protocols, like ISO DPA[2], those protocols would without spooling capabilities. This MIB is designed to be compatible
be used to monitor and manage print jobs rather than using the Job with most current commonly-used job submission protocols. In most
Monitoring MIB. environments that support high function job submission/job control
protocols, like ISO DPA[2], those protocols would be used to monitor and
manage print jobs rather than using the Job Monitoring MIB.
1.1 Types of Information in the MIB 1.1 Types of Information in the MIB
The job MIB is intended to provide the following information for the The job MIB is intended to provide the following information for the
indicated Role Models in the Printer MIB[1] (Refer to RFC 1759, Appendix indicated Role Models in the Printer MIB[1] (Appendix D - Roles of
D - Roles of Users). Users).
User: User:
Provide the ability to identify the least busy printer. The 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 will be able to determine the number and size of jobs waiting for
each printer. No attempt is made to actually predict the length each printer. No attempt is made to actually predict the length
of time that jobs will take. of time that jobs will take.
Provide the ability to identify the current status of the job Provide the ability to identify the current status of the user's
(user queries). job (user queries).
Provide a timely notification that the job has completed and where Job Monitoring MIB, V0.82 June 9, 1997
Provide a timely indication that the job has completed and where
it can be found. it can be found.
Provide error and diagnostic information for jobs that did not Provide error and diagnostic information for jobs that did not
successfully complete. successfully complete.
Operator: Operator:
Provide a presentation of the state of all the jobs in the print Provide a presentation of the state of all the jobs in the print
system. system.
Job Monitoring MIB, V0.81 April 24, 1997
Provide the ability to identify the user that submitted the print Provide the ability to identify the user that submitted the print
job. job.
Provide the ability to identify the resources required by each Provide the ability to identify the resources required by each
job. job.
Provide the ability to define which physical printers are Provide the ability to define which physical printers are
candidates for the print job. candidates for the print job.
Provide some idea of how long each job will take. However, exact Provide some idea of how long each job will take. However, exact
skipping to change at page 7, line 45 skipping to change at page 11, line 5
Provide information to allow the prediction of consumable usage Provide information to allow the prediction of consumable usage
and resource need. and resource need.
The MIB supports printers that can contain more than one job at a time, The MIB supports 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 but still be usable for low end printers that only contain a single job
at a time. In particular, the MIB supports the needs of Windows and at a time. In particular, the MIB supports the needs of Windows and
other PC environments for managing low-end networked devices without other PC environments for managing low-end networked devices without
unnecessary overhead or complexity, while also providing for higher end unnecessary overhead or complexity, while also providing for higher end
systems and devices. systems and devices.
Job Monitoring MIB, V0.82 June 9, 1997
1.2 Types of Job Monitoring Applications 1.2 Types of Job Monitoring Applications
The Job Monitoring MIB is designed for the following types of monitoring The Job Monitoring MIB is designed for the following types of monitoring
applications: applications:
1.monitor a single job starting when the job is submitted and 1.monitor a single job starting when the job is submitted and
finishing a defined period after the job completes. The Job finishing a defined period after the job completes. The Job
Submission ID table provides the map to find the specific job to be Submission ID table provides the map to find the specific job to be
monitored. monitored.
2.monitor all active of the jobs in a queue, which is generalized to 2.monitor all 'active' jobs in a queue, which this specification
a job set. End users may use such a program when selecting a least generalizes to a "job set". End users may use such a program when
busy printer, so the MIB is designed for such a program to start up selecting a least busy printer, so the MIB is designed for such a
quickly and find the information needed quickly without having to program to start up quickly and find the information needed quickly
read all (completed) jobs in order to find the active jobs. System without having to read all (completed) jobs in order to find the
operators may also use such a program in which case it would be active jobs. System operators may also use such a program, in
running for a long period of time and may also be interested in the which case it would be running for a long period of time and may
Job Monitoring MIB, V0.81 April 24, 1997 also be interested in the jobs that have completed. Finally such a
program may be co-located with the printer to provide an enhanced
jobs that have completed. Finally such a program may be co-located console and logging capability.
with the printer to provide an enhanced console capability.
3.collect resource usage for accounting or system utilization 3.collect resource usage for accounting or system utilization
purposes that copy the completed job statistics to an accounting purposes that copy the completed job statistics to an accounting
system. It is recognized that depending on accounting programs to system. It is recognized that depending on accounting programs to
copy MIB data during the job-retention period is somewhat copy MIB data during the job-retention period is somewhat
unreliable, since the accounting program may not be running (or may unreliable, since the accounting program may not be running (or may
have crashed). Such a program is expected to keep a shadow copy of have crashed). Such a program is expected to keep a shadow copy of
the entire Job Attribute table including canceled and completed the entire Job Attribute table including completed, canceled, and
jobs which the program updates on each polling cycle. Such a aborted jobs which the program updates on each polling cycle. Such
program polls at the rate of the persistence of the Attribute a program polls at the rate of the persistence of the Attribute
table. The design is not optimized to help such an application table. The design is not optimized to help such an application
determine which jobs are completed or canceled. Instead, the determine which jobs are completed, canceled, or aborted. Instead,
application shall query each job that the application's shadow copy the application SHALL query each job that the application's shadow
shows was not complete or canceled at the previous poll cycle to copy shows was not complete, canceled, or aborted at the previous
see if it is now complete or canceled, plus any new jobs that have poll cycle to see if it is now complete or canceled, plus any new
been submitted. jobs that have been submitted.
The MIB provides a set of objects that represent a compatible subset of The MIB provides a set of objects that represent a compatible subset of
job and document attributes of the ISO DPA standard[2], so that job and document attributes of the ISO DPA standard[2] and the Internet
coherence is maintained between the two protocols and information Printing Protocol (IPP)[3], so that coherence is maintained between
presented to end users and system operators. However, the job these two protocols and the information presented to end users and
system operators by monitoring applications. However, the job
monitoring MIB is intended to be used with printers that implement other monitoring MIB is intended to be used with printers that implement other
job submitting and management protocols, such as IEEE 1284.1 (TIPSI)[4], job submitting and management protocols, such as IEEE 1284.1 (TIPSI)[4],
as well as with ones that do implement ISO DPA. So nothing in the job 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. monitoring MIB requires implementation of the ISO DPA or IPP protocols.
Job Monitoring MIB, V0.82 June 9, 1997
The MIB is designed so that an additional MIB(s) can be specified in the 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 future for monitoring multi-function (scan, FAX, copy) jobs as an
augmentation to this MIB. augmentation to this MIB.
2. Terminology and Job Model 2. Terminology and Job Model
This section defines the terms that are used in this specification and This section defines the terms that are used in this specification and
the general model for jobs. the general model for jobs.
NOTE - Existing systems use conflicting terms, so these terms are NOTE - Existing systems use conflicting terms, so these terms are
drawn from the ISO 10175 Document Printing Application (DPA) drawn from the ISO 10175 Document Printing Application (DPA)
standard[2]. For example, PostScript systems use the term session for standard[2]. For example, PostScript systems use the term session for
what we call a job in this specification and the term job to mean what what we call a job in this specification and the term job to mean what
we call a document in this paper. PJL systems use the term .. we call a document in this specification. PJL systems use the term
job to mean what we call a job in this specification. PJL also
supports multiple documents per job, but does not support specifying
per-document attributes independently for each document.
A job is a unit of work whose results are expected together without A job is a unit of work whose results are expected together without
interjection of unrelated results. A client is able to specify job interjection of unrelated results. A client is able to specify job
instructions that apply to the job as a whole. Proscriptive instructions that apply to the job as a whole. Proscriptive
instructions specify how, when, and where the job is to be printed. instructions specify how, when, and where the job is to be printed.
Descriptive instructions describe the job. A job contains one or more Descriptive instructions describe the job. A job contains one or more
documents. documents.
A job set is a set of jobs that are queued and scheduled together A job set is a set of jobs that are queued and scheduled together
according to a specified scheduling algorithm for a specified device or according to a specified scheduling algorithm for a specified device or
set of devices. For implementations that embed the SNMP agent in the set of devices. For implementations that embed the SNMP agent in the
device, the MIB job set normally represents all the jobs known to the device, the MIB job set normally represents all the jobs known to the
device, so that the implementation only implements a single job set device, so that the implementation only implements a single job set
Job Monitoring MIB, V0.81 April 24, 1997 which MAY be identified with a hard-coded value 1. If the SNMP agent is
which may be identified with a hard-coded value 1. If the SNMP agent is
implemented in a server that controls one or more devices, each MIB job implemented in a server that controls one or more devices, each MIB job
set represents a job queue for (1) a specific device or (2) set of set represents a job queue for (1) a specific device or (2) set of
devices, if the server uses a single queue to load balance between devices, if the server uses a single queue to load balance between
several devices. Each job set is disjoint; no job shall be represented several devices. Each job set is disjoint; no job SHALL be represented
in more than one MIB job set. in more than one MIB job set.
A document is a sub-section within a job. A document contains print A document is a sub-section within a job. A document contains print
data and document instructions that apply to just the document. The data and document instructions that apply to just the document. The
client is able to specify document instructions separately for each client is able to specify document instructions separately for each
document in a job. Proscriptive instructions specify how the document document in a job. Proscriptive instructions specify how the document
is to be processed and printed by the server. Descriptive instructions is to be processed and printed by the server. Descriptive instructions
describe the document. Server implementation of more than one document describe the document. Server implementation of more than one document
per job is optional. per job is optional.
A client is the network entity that end users use to submit jobs to A client is the network entity that end users use to submit jobs to
spoolers, servers, or printers and other devices, depending on the spoolers, servers, or printers and other devices, depending on the
configuration, using any job submission protocol. configuration, using any job submission protocol.
Job Monitoring MIB, V0.82 June 9, 1997
A server is a network entity that accepts jobs from clients and in turn A server is a network entity that accepts jobs from clients and in turn
submits the jobs to printers and other devices. A server may be a submits the jobs to printers and other devices. A server MAY be a
printer supervisor control program, or a print spooler. printer supervisor control program, or a print spooler.
A device is a hardware entity that (1) interfaces to humans in human A device is a hardware entity that (1) interfaces to humans in human
perceptible means, such as produces marks on paper, scans marks on paper perceptible means, such as produces marks on paper, scans marks on paper
to produce an electronic representations, or writes CD-ROMs or (2) to produce an electronic representations, or writes CD-ROMs or (2)
interfaces to a network, such as sends FAX data to another FAX device. interfaces to a network, such as sends FAX data to another FAX device.
A printer is a device that puts marks on media. A printer is a device that puts marks on media.
A supervisor is a server that contains a control program that controls a A supervisor is a server that contains a control program that controls a
skipping to change at page 9, line 52 skipping to change at page 13, line 34
printer or a printer supervisor, depending on implementation. printer or a printer supervisor, depending on implementation.
Spooling is the act of a device or server of (1) accepting jobs and (2) Spooling is the act of a device or server of (1) accepting jobs and (2)
writing the job's attributes and document data on to secondary storage. writing the job's attributes and document data on to secondary storage.
Queuing is the act of a device or server of ordering (queuing) the jobs Queuing is the act of a device or server of ordering (queuing) the jobs
for the purposes of scheduling the jobs to be processed. for the purposes of scheduling the jobs to be processed.
A monitor or job monitoring application is the network entity that End A monitor or job monitoring application is the network entity that End
Users, System Operators, Accountants, Asset Managers, and Capacity Users, System Operators, Accountants, Asset Managers, and Capacity
Planners use to monitor jobs using SNMP. A monitor may be either a Planners use to monitor jobs using SNMP. A monitor MAY be either a
separate application or may be part of the client that also submits separate application or MAY be part of the client that also submits
jobs. jobs.
An agent is the network entity that accepts SNMP requests from a monitor An agent is the network entity that accepts SNMP requests from a monitor
and implements the Job Monitoring MIB. and implements the Job Monitoring MIB by instrumenting a server or a
device.
A proxy is an agent that acts as a concentrator for one or more other A proxy is an agent that acts as a concentrator for one or more other
agents by accepting SNMP operations on the behalf of one or more other agents by accepting SNMP operations on the behalf of one or more other
Job Monitoring MIB, V0.81 April 24, 1997
agents, forwarding them on to those other agents, gathering responses agents, forwarding them on to those other agents, gathering responses
from those other agents and returning them to the original requesting from those other agents and returning them to the original requesting
monitor. monitor.
A user is a person that uses a client or a monitor. A user is a person that uses a client or a monitor.
An end user is a user that uses a client to submit a print job. An end user is a user that uses a client to submit a print job.
A system operator is a user that uses a monitor to monitor the system A system operator is a user that uses a monitor to monitor the system
and carries out tasks to keep the system running. and carries out tasks to keep the system running.
Job Monitoring MIB, V0.82 June 9, 1997
A system administrator is a user that specifies policy for the system. A system administrator is a user that specifies policy for the system.
A job instruction is an instruction specifying how, when, or where the A job instruction is an instruction specifying how, when, or where the
job is to be processed. Job instructions may be passed in the job job is to be processed. Job instructions MAY be passed in the job
submission protocol or may be embedded in the document data or a submission protocol or MAY be embedded in the document data or a
combination depending on the job submission protocol and implementation. combination depending on the job submission protocol and implementation.
A document instruction is an instruction specifying how to process the A document instruction is an instruction specifying how to process the
document. Document instructions may be passed in the job submission document. Document instructions MAY be passed in the job submission
protocol separate from the actual document data, or may be embedded in protocol separate from the actual document data, or MAY be embedded in
the document data or a combination, depending on the job submission the document data or a combination, depending on the job submission
protocol and implementation. protocol and implementation.
An SNMP information object is a name, value-pair that specifies an An SNMP information object is a name, value-pair that specifies an
action, a status, or a condition in an SNMP MIB. Objects are identified action, a status, or a condition in an SNMP MIB. Objects are identified
in SNMP by an OBJECT IDENTIFIER. in SNMP by an OBJECT IDENTIFIER.
An attribute is a name, value-pair that specifies an instruction, a An attribute is a name, value-pair that specifies an instruction, a
status, or a condition of a job or a document that has been submitted to status, or a condition of a job or a document that has been submitted to
a server or device. A particular attribute need not be present in each a server or device. A particular attribute NEED NOT be present in each
job instance. In other words, attributes are present in a job instance job instance. In other words, attributes are present in a job instance
only when there is a need to express the value, either because (1) the only when there is a need to express the value, either because (1) the
client supplied a value in the job submission protocol, (2) the document client supplied a value in the job submission protocol, (2) the document
data contained an embedded attribute, or (3) the server or device data contained an embedded attribute, or (3) the server or device
supplied a default value. An agent shall represent an attribute as an supplied a default value. An agent SHALL represent an attribute as an
entry (row) in the attribute table in this MIB in which entries are entry (row) in the Attribute table in this MIB in which entries are
present only when necessary. Attributes are identified in this MIB by present only when necessary. Attributes are identified in this MIB by
an enum.. an enum.
Job monitoring using SNMP is (1) identifying jobs within the serial Job monitoring using SNMP is (1) identifying jobs within the serial
streams of data being processed by the server, printer or other devices, streams of data being processed by the server, printer or other devices,
(2) creating "rows" in the job table for each job, and (3) recording (2) creating "rows" in the job table for each job, and (3) recording
information, known by the agent, about the processing of the job in that information, known by the agent, about the processing of the job in that
"row". "row".
Job accounting is recording what happens to the job during the Job accounting is recording what happens to the job during the
processing and printing of the job. processing and printing of the job.
3. System Configurations for the Job Monitoring MIB 3. System Configurations for the Job Monitoring MIB
This section enumerates the three configurations for which the Job This section enumerates the three configurations in which the Job
Monitoring MIB is intended to be used. To simplify the pictures, the Monitoring MIB is intended to be used. To simplify the pictures, the
devices are shown as printers. See Goals section. devices are shown as printers. See Goals section.
Job Monitoring MIB, V0.81 April 24, 1997
The diagram in the Printer MIB[1] entitled: "One Printer's View of the The diagram in the Printer MIB[1] entitled: "One Printer's View of the
Network" is assumed for this MIB as well. Please refer to that diagram Network" is assumed for this MIB as well. Please refer to that diagram
to aid in understand the following system configurations. to aid in understanding the following system configurations.
Job Monitoring MIB, V0.82 June 9, 1997
3.1 Configuration 1 - client-printer 3.1 Configuration 1 - client-printer
In the client-printer configuration, the client(s) submit jobs directly In the client-printer configuration, the client(s) submit jobs directly
to the printer, either by some direct connect, or by network connection. to the printer, either by some direct connect, or by network connection.
The client-printer configuration can accommodate multiple job submitting The client-printer configuration can accommodate multiple job submitting
clients in either of two ways: clients in either of two ways:
1.if each client relinquishes control of the Print Job Delivery 1.if each client relinquishes control of the Print Job Delivery
Channel after each job (or after a number of jobs) Channel after each job (or after a number of jobs)
2.if the printer supports more than one Print Job Delivery Channel 2.if the printer supports more than one Print Job Delivery Channel
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs by
communicating directly with an agent that is part of the printer. The communicating directly with an agent that is part of the printer. The
agent in the printer shall keep the job in the Job Monitoring MIB as agent in the printer SHALL keep the job in the Job Monitoring MIB as
long as the job is in the Printer, and longer in order to implement the long as the job is in the Printer, and longer in order to implement the
completed state in which monitoring programs can copy out the accounting completed state in which monitoring programs can copy out the accounting
data from the Job Monitoring MIB. data from the Job Monitoring MIB.
all end-user ######## SNMP query all end-user ######## SNMP query
+-------+ +--------+ ---- job submission +-------+ +--------+ ---- job submission
|monitor| | client | |monitor| | client |
+---#---+ +--#--+--+ +---#---+ +--#--+--+
# # | # # |
# ############ | # ############ |
# # | # # |
+==+===#=#=+==+ | +==+===#=#=+==+ |
| | agent | | | | | agent | | |
| +-------+ | | | +-------+ | |
| PRINTER <--------+ | PRINTER <--------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 1 - Configuration 1 - client-printer - agent in the printer Figure 3-1 - Configuration 1 - client-printer - agent in the printer
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 1): relationships (not shown in Figure 3-1):
1.Multiple clients may submit jobs to a printer. 1.Multiple clients MAY submit jobs to a printer.
2.Multiple clients may monitor a printer. 2.Multiple clients MAY monitor a printer.
3.Multiple monitors may monitor a printer. 3.Multiple monitors MAY monitor a printer.
4.A client may submit jobs to multiple printers. 4.A client MAY submit jobs to multiple printers.
5.A monitor may monitor multiple printers. 5.A monitor MAY monitor multiple printers.
Job Monitoring MIB, V0.82 June 9, 1997
3.2 Configuration 2 - client-server-printer - agent in the server 3.2 Configuration 2 - client-server-printer - agent in the server
In the client-server-printer configuration 2, the client(s) submit jobs In the client-server-printer configuration 2, the client(s) submit jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
Job Monitoring MIB, V0.81 April 24, 1997
the printer. While configuration 2 is included, the design center for the printer. While configuration 2 is included, the design center for
this MIB is configurations 1 and 3, this MIB is configurations 1 and 3,
The job submitting client and/or monitoring application monitor job by The job submitting client and/or monitoring application monitor job by
communicating directly with: communicating directly with:
1.a Job Monitoring MIB agent that is part of the server (or a 1.a Job Monitoring MIB agent that is part of the server (or a
front for the server) front for the server)
There is no SNMP Job Monitoring MIB agent in the printer in There is no SNMP Job Monitoring MIB agent in the printer in
configuration 2, at least that the client or monitor are aware. In this configuration 2, at least that the client or monitor are aware. In this
configuration, the agent shall return the current values of the objects configuration, the agent SHALL return the current values of the objects
in the Job Monitoring MIB both for jobs the server keeps and jobs that in the Job Monitoring MIB both for jobs the server keeps and jobs that
the server has submitted to the printer. In configuration 2, the server the server has submitted to the printer. In configuration 2, the server
keeps a copy of the job during the time that the server has submitted keeps a copy of the job during the time that the server has submitted
the job to the printer. Only some time after the printer completes the the job to the printer. Only some time after the printer completes the
job, shall the server remove the representation of the job from the Job job, SHALL the server remove the representation of the job from the Job
Monitoring MIB in the server. The agent need not access the printer, Monitoring MIB in the server. The agent NEED NOT access the printer,
except when a monitor queries the agent using an SNMP Get for an object except when a monitor queries the agent using an SNMP Get for an object
in the Job Monitoring MIB. Or the agent can subscribe to the in the Job Monitoring MIB. Or the agent can subscribe to the
notification events that the printer generates and keep the Job notification events that the printer generates and keep the Job
Monitoring MIB update to date. The agent in the server shall keep the Monitoring MIB update to date. The agent in the server SHALL keep the
job in the Job Monitoring MIB as long as the job is in the Printer, and job in the Job Monitoring MIB as long as the job is in the Printer, and
longer in order to implement the completed state in which monitoring longer in order to implement the completed state in which monitoring
programs can copy out the accounting data from the Job Monitoring MIB. programs can copy out the accounting data from the Job Monitoring MIB.
all end-user all end-user
+-------+ +----------+ +-------+ +----------+
|monitor| | client | ######## SNMP query |monitor| | client | ######## SNMP query
+---+---# +---#----+-+ **** non-SNMP cntrl +---+---# +---#----+-+ **** non-SNMP cntrl
# # | ---- job submission # # | ---- job submission
# # | # # |
skipping to change at page 12, line 50 skipping to change at page 17, line 4
| agent | | | agent | |
+-------+ | +-------+ |
| server | | server |
+----+-----+--+ +----+-----+--+
control * | control * |
********** | ********** |
* | * |
+========v====+ | +========v====+ |
| | | | | |
| | | | | |
Job Monitoring MIB, V0.82 June 9, 1997
| PRINTER <---------+ | PRINTER <---------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 2 - Configuration 2 - client-server-printer - agent in the server Figure 3-2 - Configuration 2 - client-server-printer - agent in the
server
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 2): relationships (not shown in Figure 3-2):
1.Multiple clients may submit jobs to a server. 1.Multiple clients MAY submit jobs to a server.
2.Multiple clients MAY monitor a server.
Job Monitoring MIB, V0.81 April 24, 1997 3.Multiple monitors MAY monitor a server.
4.A client MAY submit jobs to multiple servers.
2.Multiple clients may monitor a server. 5.A monitor MAY monitor multiple servers.
3.Multiple monitors may monitor a server. 6.Multiple servers MAY submit jobs to a printer.
4.A client may submit jobs to multiple servers. 7.Multiple servers MAY control a printer.
5.A monitor may monitor multiple servers.
6.Multiple servers may submit jobs to a printer.
7.Multiple servers may control a printer.
3.3 Configuration 3 - client-server-printer - client monitors printer 3.3 Configuration 3 - client-server-printer - client monitors printer
agent and server agent and server
In the client-server-printer configuration 3, the client(s) submit jobs In the client-server-printer configuration 3, the client(s) submit jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
the printer. the printer.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs by
communicating directly with: communicating directly with:
skipping to change at page 13, line 36 skipping to change at page 17, line 46
2.a Job Monitoring MIB agent that is part of the printer to 2.a Job Monitoring MIB agent that is part of the printer to
monitor jobs after the server passes the jobs to the printer. monitor jobs after the server passes the jobs to the printer.
In such configurations, the server deletes its copy of the job In such configurations, the server deletes its copy of the job
from the server after submitting the job to the printer usually from the server after submitting the job to the printer usually
almost immediately (before the job does much processing, if almost immediately (before the job does much processing, if
any). any).
There is no SNMP Job Monitoring MIB agent in the server in configuration There is no SNMP Job Monitoring MIB agent in the server in configuration
3, at least that the client or monitor are aware. In this 3, at least that the client or monitor are aware. In this
configuration, the agent (in the printer) shall keep the values of the configuration, the agent (in the printer) SHALL keep the values of the
objects in the Job Monitoring MIB that the agent implements updated for objects in the Job Monitoring MIB that the agent implements updated for
a job that the server has submitted to the printer. The agent shall a job that the server has submitted to the printer. The agent SHALL
obtain information about the jobs submitted to the printer from the obtain information about the jobs submitted to the printer from the
server (either in the job submission protocol, in the document data, or server (either in the job submission protocol, in the document data, or
by direct query of the server), in order to populate some of the objects by direct query of the server), in order to populate some of the objects
the Job Monitoring MIB in the printer. The agent in the printer shall the Job Monitoring MIB in the printer. The agent in the printer SHALL
Job Monitoring MIB, V0.82 June 9, 1997
keep the job in the Job Monitoring MIB as long as the job is in the keep the job in the Job Monitoring MIB as long as the job is in the
Printer, and longer in order to implement the completed state in which Printer, and longer in order to implement the completed state in which
monitoring programs can copy out the accounting data from the Job monitoring programs can copy out the accounting data from the Job
Monitoring MIB. Monitoring MIB.
all end-user all end-user
+-------+ +----------+ +-------+ +----------+
|monitor| | client | ######## SNMP query |monitor| | client | ######## SNMP query
+---+---* +---*----+-+ **** non-SNMP query +---+---* +---*----+-+ **** non-SNMP query
# * * | ---- job submission # * * | ---- job submission
# * * | # * * |
# * * | # * * |
# *=====v====v==+ # *=====v====v==+
# | | # | |
# | server | # | server |
# | | # | |
# +----#-----+--+ # +----#-----+--+
# optional# | # optional# |
# ########## | # ########## |
Job Monitoring MIB, V0.81 April 24, 1997
# # | # # |
+==+=v===v=+==+ | +==+=v===v=+==+ |
| | agent | | | | | agent | | |
| +-------+ | | | +-------+ | |
| PRINTER <---------+ | PRINTER <---------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 3 - Configuration 3 - client-server-printer - client monitors Figure 3-3 - Configuration 3 - client-server-printer - client monitors
printer agent and server printer agent and server
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 3): relationships (not shown in Figure 3-3):
1.Multiple clients may submit jobs to a server. 1.Multiple clients MAY submit jobs to a server.
2.Multiple clients may monitor a server. 2.Multiple clients MAY monitor a server.
3.Multiple monitors may monitor a server. 3.Multiple monitors MAY monitor a server.
4.A client may submit jobs to multiple servers. 4.A client MAY submit jobs to multiple servers.
5.A monitor may monitor multiple servers. 5.A monitor MAY monitor multiple servers.
6.Multiple servers may submit jobs to a printer. 6.Multiple servers MAY submit jobs to a printer.
7.Multiple servers may control a printer. 7.Multiple servers MAY control a printer.
4. Conformance Considerations 4. Conformance Considerations
In order to achieve interoperability between job monitoring applications In order to achieve interoperability between job monitoring applications
and job monitoring agents, this specification includes the conformance and job monitoring agents, this specification includes the conformance
requirements for both monitoring applications and agents. requirements for both monitoring applications and agents.
Job Monitoring MIB, V0.82 June 9, 1997
4.1 Conformance Terminology 4.1 Conformance Terminology
This specification uses the verbs: "shall", "should", "may", and "need This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED
not" to specify conformance requirements as follows: NOT" to specify conformance requirements according to RFC 2119 as
follows:
. "shall": indicates an action that the subject of the sentence must . "SHALL": indicates an action that the subject of the sentence must
implement in order to claim conformance to this specification implement in order to claim conformance to this specification
. "may": indicates an action that the subject of the sentence does . "MAY": indicates an action that the subject of the sentence does
not have to implement in order to claim conformance to this not have to implement in order to claim conformance to this
specification, in other words that action is an implementation specification, in other words that action is an implementation
option option
. "need not": indicates an action that the subject of the sentence . "NEED NOT": indicates an action that the subject of the sentence
does not have to implement in order to claim conformance to this does not have to implement in order to claim conformance to this
specification. The verb "need not" is used instead of "may not", specification. The verb "NEED NOT" is used instead of "may not",
since "may not" sounds like a prohibition. since "may not" sounds like a prohibition.
. "should": indicates an action that is recommended for the subject . "SHOULD": indicates an action that is recommended for the subject
of the sentence to implement, but is not required, in order to of the sentence to implement, but is not required, in order to
claim conformance to this specification. claim conformance to this specification.
4.2 Agent Conformance Requirements 4.2 Agent Conformance Requirements
A conforming agent: A conforming agent:
Job Monitoring MIB, V0.81 April 24, 1997 1.SHALL implement all MANDATORY groups and attributes in this
1.shall implement all mandatory groups and attributes in this
specification. specification.
2.shall implement each conditionally mandatory attributes, if the 2.NEED NOT implement any OPTIONAL attributes, whether the agent is able
server or device that the agent is instrumenting has the feature to obtain the information from the server or device.
represented by the conditionally mandatory attribute..
3.need not implement both forms of a time attribute if it implements a 3.NEED NOT implement both forms of an attribute if it implements an
time attribute and is recommended not to provide both forms for a attribute that permits a choice of Integer and Octets forms, though
particular time attribute. See page 43. implementing both forms may help management applications by giving
them a choice of representations, since the representation are
equivalent. See page 55.
NOTE - This MIB, like the Printer MIB, is written following the NOTE - This MIB, like the Printer MIB, is written following the
subset of SMIv2 that can be supported by SMIv1 and SNMPv1 subset of SMIv2 that can be supported by SMIv1 and SNMPv1
implementations. implementations.
4.2.1 MIB II System Group objects 4.2.1 MIB II System Group objects
The Job Monitoring MIB agent shall implement all objects in the system The Job Monitoring MIB agent SHALL implement all objects in the system
group of MIB-II (RFC 1213)[5], whether the Printer MIB[1] is implemented group of MIB-II (RFC 1213)[5], whether the Printer MIB[1] is implemented
or not. or not.
Job Monitoring MIB, V0.82 June 9, 1997
4.2.2 MIB II Interface Group objects 4.2.2 MIB II Interface Group objects
The Job Monitoring MIB agent shall implement all objects in the The Job Monitoring MIB agent SHALL implement all objects in the
Interfaces Group of MIB-II (RFC 1213)[5], whether the Printer MIB[1] is Interfaces Group of MIB-II (RFC 1213)[5], whether the Printer MIB[1] is
implemented or not. implemented or not.
4.2.3 Printer MIB objects 4.2.3 Printer MIB objects
If the agent is instrumenting a device that is a printer, the agent If the agent is instrumenting a device that is a printer, the agent
shall implement all of the mandatory objects in the Printer MIB[1] and SHALL implement all of the mandatory objects in the Printer MIB[1] and
all the objects in other MIBs that conformance to the Printer MIB all the objects in other MIBs that conformance to the Printer MIB
requires, such as the Host Resources MIB (RFC 1514)[6]. If the agent is requires, such as the Host Resources MIB (RFC 1514)[6]. If the agent is
instrumenting a server that controls one or more networked printers, the instrumenting a server that controls one or more networked printers, the
agent need not implement the Printer MIB and need not implement the Host agent NEED NOT implement the Printer MIB and NEED NOT implement the Host
Resources MIB. Resources MIB.
4.3 Job Monitoring Application Conformance Requirements 4.3 Job Monitoring Application Conformance Requirements
A conforming job monitoring application: A conforming job monitoring application:
1.shall accept all objects in all mandatory groups and all mandatory 1.SHALL accept all objects in all MANDATORY groups and all MANDATORY
and conditionally mandatory attributes that are required to be attributes that are required to be implemented by an agent according
implemented by an agent according to Section 4.2 and shall either to Section 4.2 and SHALL either present them to the user or ignore
present them to the user or ignore them. them.
2.shall accept all enum and bit values specified in this standard and
additional ones that may be registered with IANA and shall either
present them to the user or ignore them. In particular, a conforming
job monitoring application shall not malfunction when receiving any
standard or registered enum or bit values. See Section 7 entitled
"IANA Considerations" on page 17.
Job Monitoring MIB, V0.81 April 24, 1997 2.SHALL accept all OPTIONAL attributes, including enum and bit values
specified in this specification and additional ones that may be
registered with IANA and SHALL either present them to the user or
ignore them. In particular, a conforming job monitoring application
SHALL not malfunction when receiving any standard or registered enum
or bit values. See Section 7 entitled "IANA Considerations" on page
22.
3.shall accept either form of time attribute, if it supports a time 3.SHALL accept either form of time attribute, if it supports a time
attribute, since agents are free to implement either time form. See attribute, since agents are free to implement either time form. See
page 43. page 55.
5. Job Identification 5. Job Identification
There are a number of attributes that permit a user, operator or system There are a number of attributes that permit a user, operator or system
administrator to identify jobs of interest, such as jobOwner, jobName, administrator to identify jobs of interest, such as jobOwner, jobName,
etc. In addition, there is a Job Submission ID object that allows a etc. In addition, there is a Job Submission ID object that allows a
monitoring application to quickly locate and identify a particular job monitoring application to quickly locate and identify a particular job
of interest that was submitted from a particular client by the user of interest that was submitted from a particular client by the user
invoking the monitoring application. The Job Monitoring MIB needs to invoking the monitoring application. The Job Monitoring MIB needs to
provide for identification of the job at both sides of the job provide for identification of the job at both sides of the job
submission process. The primary identification point is the client submission process. The primary identification point is the client
side. The Job Submission ID allows the monitoring application to side. The Job Submission ID allows the monitoring application to
Job Monitoring MIB, V0.82 June 9, 1997
identify the job of interest from all the jobs currently "known" by the identify the job of interest from all the jobs currently "known" by the
server or device. The Job Submission ID can be assigned by either the server or device. The Job Submission ID can be assigned by either the
client's local system or a downstream server or device. The point of client's local system or a downstream server or device. The point of
assignment will be determined by the job submission protocol in use. assignment will be determined by the job submission protocol in use.
The server/device-side identifier, called the jmJobIndex object, will be The server/device-side identifier, called the jmJobIndex object, will be
assigned by the server or device that accepts the jobs from submitting assigned by the server or device that accepts the jobs from submitting
clients. The MIB agent shall use the job identifier assigned by the clients. The MIB agent SHALL use the job identifier assigned by the
server or device to the job as the value of the jmJobIndex object that server or device to the job as the value of the jmJobIndex object that
defines the table rows (there are multiple tables) that contain the defines the table rows (there are multiple tables) that contain the
information relating to the job. This object allows the interested information relating to the job. This object allows the interested
party to obtain all objects desired that relate to this job. The MIB party to obtain all objects desired that relate to this job. The MIB
provides a mapping table that maps each Job Submission ID to the provides a mapping table that maps each Job Submission ID to the
corresponding jmJobIndex value, so that an application can determine the corresponding jmJobIndex value, so that an application can determine the
correct value for the jmJobIndex value for the job of interest in a correct value for the jmJobIndex value for the job of interest in a
single Get operation. See the jmJobIDGroup on page 59. single Get operation. See the jmJobIDGroup on page 73.
The jobName attribute provides a name that the user supplies an a job The jobName attribute provides a name that the user supplies as a job
attribute with the job. The jobName attribute is not necessarily attribute with the job. The jobName attribute is not necessarily
unique, even for one user, let alone across users. unique, even for one user, let alone across users.
6. Internationalization Considerations 6. Internationalization Considerations
There are a number of objects in this MIB that are represented as coded There are a number of objects in this MIB that are represented as coded
character sets. The data type for such objects is OCTET STRING. Such character sets. The data type for such objects is OCTET STRING. Such
objects could be in different coded character sets and could be objects could be in different coded character sets and could be
localized in the language and country, i.e., could be localized. localized in the language and country, i.e., could be localized.
However, for the Job Monitoring MIB, most of the objects are supplied as However, for the Job Monitoring MIB, most of the objects are supplied as
job attributes by the client that submits the job to the server or job attributes by the client that submits the job to the server or
device and so are represented in the coded character set specified by device and so are represented in the coded character set specified by
that client. Therefore, the agent is not able to provide for different that client. Therefore, the agent is not able to provide for different
representations depending on the locale of the server, device, or user representations depending on the locale of the server, device, or user
of the job monitoring application. The only exception is job submission of the job monitoring application. The only exception is job submission
protocols that pass job or document attributes as OBJECT IDENTIFIERS or protocols that pass job or document attributes as OBJECT IDENTIFIERS or
enums. For those job and document attributes, the agent shall represent enums. For those job and document attributes, the agent SHALL represent
the corresponding objects in the Job Monitoring MIB as coded character the corresponding objects in the Job Monitoring MIB as coded character
sets in the current (default) locale of the server or printer as sets in the current (default) locale of the server or printer as
established by the system administrator or the implementation. established by the system administrator or the implementation.
Job Monitoring MIB, V0.81 April 24, 1997
For simplicity, this specification assumes that the clients, job For simplicity, this specification assumes that the clients, job
monitoring applications, servers, and devices are all running in the monitoring applications, servers, and devices are all running in the
same locale. However, this specification allows them to run in any same locale. However, this specification allows them to run in any
locale, including locales that use two-octet coded character sets, such locale, including locales that use two-octet coded character sets, such
as ISO 10646 (Unicode). Job monitors applications are expected to as ISO 10646 (Unicode). Job monitors applications are expected to
understand the coded character set of the client (and job), server, or understand the coded character set of the client (and job), server, or
device. No special means is provided for the monitor to discover the device. No special means is provided for the monitor to discover the
coded character set used by jobs or by the server or device. This coded character set used by jobs or by the server or device. This
specification does not contain an object that indicates what locale the specification does not contain an object that indicates what locale the
Job Monitoring MIB, V0.82 June 9, 1997
server or device is running in, let alone contain an object to control server or device is running in, let alone contain an object to control
what locale the agent is to use to represent coded character set what locale the agent is to use to represent coded character set
objects. objects.
This MIB also contains objects that are represented using the This MIB also contains objects that are represented using the
DateAndTime textual convention from SNMPv2-TC (RFC 1903). The job DateAndTime textual convention from SNMPv2-TC (RFC 1903). The job
management application shall display such objects in the locale of the management application SHALL display such objects in the locale of the
user running the monitoring application. user running the monitoring application.
7. IANA Considerations 7. IANA Considerations
During the development of this standard, the Printer Working Group (PWG) During the development of this standard, the Printer Working Group (PWG)
working with IANA will register additional enums while the standard is working with IANA will register additional enums while the standard is
in the proposed and draft states according to the procedures described in the proposed and draft states according to the procedures described
in this section. IANA will handle registration of additional enums in this section. IANA will handle registration of additional enums
after this standard is approved in cooperation with an IANA-appointed after this standard is approved in cooperation with an IANA-appointed
registration editor from the PWG according to the procedures described registration editor from the PWG according to the procedures described
skipping to change at page 18, line 5 skipping to change at page 22, line 50
types of enumerations are: types of enumerations are:
7.1.1 Type 1 enumerations 7.1.1 Type 1 enumerations
Type 1 enumeration: All the values are defined in the Job Monitoring Type 1 enumeration: All the values are defined in the Job Monitoring
MIB specification (RFC for the Job Monitoring MIB). Additional MIB specification (RFC for the Job Monitoring MIB). Additional
enumerated values require a new RFC. enumerated values require a new RFC.
NOTE - There are no type 1 enums in the current draft. NOTE - There are no type 1 enums in the current draft.
Job Monitoring MIB, V0.81 April 24, 1997
7.1.2 Type 2 enumerations 7.1.2 Type 2 enumerations
Type 2 enumeration: An initial set of values are defined in the Job Type 2 enumeration: An initial set of values are defined in the Job
Monitoring MIB specification. Additional enumerated values are Monitoring MIB specification. Additional enumerated values are
Job Monitoring MIB, V0.82 June 9, 1997
registered after review by this working group. The initial versions of registered after review by this working group. The initial versions of
the MIB will contain the values registered so far. After the MIB is the MIB will contain the values registered so far. After the MIB is
approved, additional values will be registered through IANA after approved, additional values will be registered through IANA after
approval by this working group. approval by this working group.
The following type 2 enums are contained in the current draft : The following type 2 enums are contained in the current draft :
1.JmTimeStampTC 1.JmTimeStampTC
2.JmFinishingTC 2.JmFinishingTC
3.JmPrintQualityTC 3.JmPrintQualityTC
4.JmTonerEconomyTC 4.JmTonerEconomyTC
5.JmTonerDensityTC 5.JmPrinterResolutionTC
6.JmMediumTypeTC 6.JmMediumTypeTC
7.JmJobStateTC 7.JmJobStateTC
8.JmAttributeTypeTC 8.JmAttributeTypeTC
7.1.3 Type 3 enumeration 7.1.3 Type 3 enumeration
Type 3 enumeration: An initial set of values are defined in the Job Type 3 enumeration: An initial set of values are defined in the Job
Monitoring MIB specification. Additional enumerated values are Monitoring MIB specification. Additional enumerated values are
registered without working group review. The initial versions of the registered without working group review. The initial versions of the
MIB will contain the values registered so far. After the MIB is MIB will contain the values registered so far. After the MIB is
skipping to change at page 18, line 47 skipping to change at page 23, line 42
7.2 IANA Registration of type 2 bit values 7.2 IANA Registration of type 2 bit values
This draft contains the following type 2 bit value textual-conventions: This draft contains the following type 2 bit value textual-conventions:
1.JmJobServiceTypesTC 1.JmJobServiceTypesTC
2.JmJobStateReasons1TC 2.JmJobStateReasons1TC
3.JmJobStateReasons2TC 3.JmJobStateReasons2TC
4.JmJobStateReasons3TC 4.JmJobStateReasons3TC
5.JmJobStateReasons4TC 5.JmJobStateReasons4TC
These textual-conventions are defined as bits in an Integer so that they These textual-conventions are defined as bits in an Integer so that they
may be used with SNMPv1 SMI.. The jobStateReasonsn (n=1..4) attributes can be used with SNMPv1 SMI. The jobStateReasonsn (n=1..4) attributes
are defined as bit values using the JmJobStateReasonsnTC textual- are defined as bit values using the corresponding JmJobStateReasonsnTC
convention. textual-conventions.
The registration of JmJobServiceTypesTC and JmJobStateReasonsnTC bit The registration of JmJobServiceTypesTC and JmJobStateReasonsnTC bit
values shall follow the procedures for a type 2 enum as specified in values SHALL follow the procedures for a type 2 enum as specified in
Section 7.1.2. Section 7.1.2.
7.3 IANA Registration of Job Submission Id Formats 7.3 IANA Registration of Job Submission Id Formats
In addition to enums and bit values, this specification assigns numbers In addition to enums and bit values, this specification assigns numbers
to various job submission ID formats. See jmJobSubmissionIDIndex on to various job submission ID formats. See jmJobSubmissionID on page 74.
page 60. The registration of jmJobSubmissionIDIndex format numbers
shall follow the procedures for a type 2 enum as specified in Section
7.1.2.
Job Monitoring MIB, V0.81 April 24, 1997 Job Monitoring MIB, V0.82 June 9, 1997
The registration of jmJobSubmissionID format numbers SHALL follow the
procedures for a type 2 enum as specified in Section 7.1.2.
8. Security Considerations 8. Security Considerations
8.1 Read-Write objects 8.1 Read-Write objects
All objects are read-only greatly simplifying the security All objects are read-only greatly simplifying the security
considerations. If another MIB augments this MIB, that MIB might allow considerations. If another MIB augments this MIB, that MIB might allow
objects in this MIB to be modified. However, that MIB shall have to objects in this MIB to be modified. However, that MIB SHALL have to
support the required access control in order to achieve security, not support the required access control in order to achieve security, not
this MIB. this MIB.
8.2 Read-Only Objects In Other User's Jobs 8.2 Read-Only Objects In Other User's Jobs
The security policy of some sites may be that unprivileged users can The security policy of some sites may be that unprivileged users can
only get the objects from jobs that they submitted, plus a few minimal only get the objects from jobs that they submitted, plus a few minimal
objects from other jobs, such as the jobKOctetsRequested and objects from other jobs, such as the jmJobKOctetsRequested and
jobKOctetsCompleted attributes, so that a user can tell how busy a jmJobKOctetsCompleted objects, so that a user can tell how busy a
printer is. Other sites might allow all unprivileged users to see all printer is. Other sites might allow all unprivileged users to see all
objects of all jobs. It is up to the agent to implement any such objects of all jobs. It is up to the agent to implement any such
restrictions based on the identification of the user making the SNMP restrictions based on the identification of the user making the SNMP
request. This MIB does not require, nor does it specify how, such request. This MIB does not require, nor does it specify how, such
restrictions would be implemented. A monitoring application should restrictions would be implemented. A monitoring application SHOULD
enforce the site security policy with respect to returning information enforce the site security policy with respect to returning information
to an unprivileged end user that is using the monitoring application to to an unprivileged end user that is using the monitoring application to
monitor jobs that do not belong to that user, i.e., the jobOwner monitor jobs that do not belong to that user, i.e., the jobOwner
attribute in the jmAttributeTable does not match the user's user name. attribute in the jmAttributeTable does not match the user's user name.
See the JmAttributeTypeTC textual convention on page 41 and the See the JmAttributeTypeTC textual convention on page Error! Bookmark not
jmAttributeTable. defined. and the jmAttributeTable on page 81.
An operator is a privileged user that would be able to see all objects An operator is a privileged user that would be able to see all objects
of all jobs, independent of the policy for unprivileged users. of all jobs, independent of the policy for unprivileged users.
9. Returning Objects With No Value In Mandatory Groups 9. Returning Objects With No Value In Mandatory Groups
If an object in a mandatory group does not have an instrumented value If an object in a mandatory group does not have an instrumented value
for a particular job submission protocol or the job submitting client for a particular job submission protocol or the job submitting client
did not supply a value (and the accepting server or device does not did not supply a value (and the accepting server or device does not
supply a default), this MIB requires that the agent shall follow the supply a default), this MIB requires that the agent SHALL follow the
normal SNMP practice of returning a distinguished value, such as a zero- normal SNMP practice of returning a distinguished value, such as a zero-
length string, an unknown(2) value for an enum, or a (-2) for an integer length string, an unknown(2) value for an enum, or a (-2) for an integer
value. value.
Job Monitoring MIB, V0.82 June 9, 1997
10. Notification and Traps 10. Notification and Traps
This MIB does not specify any traps. For simplicity, management This MIB does not specify any traps. For simplicity, management
applications are expected to poll for status. The resulting network applications are expected to poll for status. The resulting network
traffic is not expected to be significant. traffic is not expected to be significant.
11. MIB specification 11. MIB specification
The following pages constitute the actual Job Monitoring MIB. The following pages constitute the actual Job Monitoring MIB.
Job Monitoring MIB, V0.81 April 24, 1997 Job Monitoring MIB, V0.82 June 9, 1997
Job-Monitoring-MIB DEFINITIONS ::= BEGIN Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed -- The following textual-conventions are needed
-- to implement certain attributes, but are not -- to implement certain attributes, but are not
skipping to change at page 20, line 35 skipping to change at page 26, line 35
-- reference of { temp 104 } (below) to { mib-2 X }. -- reference of { temp 104 } (below) to { mib-2 X }.
-- This will result in changing: -- This will result in changing:
-- 1 3 6 1 3 54 jobmonMIB(105) to: -- 1 3 6 1 3 54 jobmonMIB(105) to:
-- 1 3 6 1 2 1 jobmonMIB(X) -- 1 3 6 1 2 1 jobmonMIB(X)
-- This will make it easier to translate prototypes to -- This will make it easier to translate prototypes to
-- the standard namespace because the lengths of the OIDs won't -- the standard namespace because the lengths of the OIDs won't
-- change. -- change.
temp OBJECT IDENTIFIER ::= { experimental 54 } temp OBJECT IDENTIFIER ::= { experimental 54 }
jobmonMIB MODULE-IDENTITY jobmonMIB MODULE-IDENTITY
LAST-UPDATED "9704240000Z" LAST-UPDATED "9705200000Z"
ORGANIZATION "IETF Printer MIB Working Group" ORGANIZATION "IETF Printer MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Tom Hastings "Tom Hastings
Postal: Xerox Corp. Postal: Xerox Corp.
Mail stop ESAE-231 Mail stop ESAE-231
701 S. Aviation Blvd. 701 S. Aviation Blvd.
El Segundo, CA 90245 El Segundo, CA 90245
Tel: (301)333-6413 Tel: (301)333-6413
Fax: (301)333-5514 Fax: (301)333-5514
E-mail: hastings@cp10.es.xerox.com" E-mail: hastings@cp10.es.xerox.com"
DESCRIPTION DESCRIPTION
"The MIB module for monitoring job in servers, printers, and "The MIB module for monitoring job in servers, printers, and
other devices. other devices.
File: jmp-mib.doc, .pdf, .txt, .mib File: jmp-mib.doc, .pdf, .txt, .mib
Version: 0.81" Version: 0.82"
::= { temp 105 } ::= { temp 105 }
Job Monitoring MIB, V0.82 June 9, 1997
-- Textual conventions for this MIB module -- Textual conventions for this MIB module
JmTimeStampTC ::= TEXTUAL-CONVENTION JmTimeStampTC ::= TEXTUAL-CONVENTION
Job Monitoring MIB, V0.81 April 24, 1997
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The simple time at which an event took place. The units shall "The simple time at which an event took place. The units SHALL
be in seconds since the system was booted. be in seconds since the system was booted.
NOTE - JmTimeStampTC is defined in units of seconds, rather than NOTE - JmTimeStampTC is defined in units of seconds, rather than
100ths of seconds, so as to be simpler for agents to implement 100ths of seconds, so as to be simpler for agents to implement
(even if they have to implement the 100ths of a second to comply (even if they have to implement the 100ths of a second to comply
with implementing sysUpTime in MIB-II[5].) with implementing sysUpTime in MIB-II[5].)
NOTE - JmTimeStampTC is defined as an Integer32 so that it can NOTE - JmTimeStampTC is defined as an Integer32 so that it can
be used as a value of an attribute, i.e., as a value of the be used as a value of an attribute, i.e., as a value of the
jmAttributeValueAsInteger object (see page 66). The TimeStamp jmAttributeValueAsInteger object (see page 83). The TimeStamp
textual-convention defined in SMNPv2-TC is defined as an textual-convention defined in SMNPv2-TC is defined as an
APPLICATION 3 IMPLICIT INTEGER tag, not an Integer32, so cannot APPLICATION 3 IMPLICIT INTEGER tag, not an Integer32, so cannot
be used in this MIB as one of the values of be used in this MIB as one of the values of
jmAttributeValueAsInteger." jmAttributeValueAsInteger."
SYNTAX INTEGER(0..2147483647) SYNTAX INTEGER(0..2147483647)
JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source platform type that can submit jobs to servers or "The source platform type that can submit jobs to servers or
devices in any of the 3 configurations." devices in any of the 3 configurations."
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
sptUNIX(3), -- UNIX(tm) sptUNIX(3), -- UNIX(tm)
sptOS2(4), -- OS/2 sptOS2(4), -- OS/2
sptPCDOS(5), -- DOS sptPCDOS(5), -- DOS
sptNT(6), -- NT sptNT(6), -- NT
sptMVS(7), -- MVS sptMVS(7), -- MVS
sptVM(8), -- VM sptVM(8), -- VM
sptOS400(9), -- OS/400 sptOS400(9), -- OS/400
sptVMS(10), -- VMS sptVMS(10), -- VMS
Job Monitoring MIB, V0.82 June 9, 1997
sptWindows95(11), -- Windows95 sptWindows95(11), -- Windows95
sptNetWare(33) -- NetWare sptNetWare(33) -- NetWare
} }
JmFinishingTC ::= TEXTUAL-CONVENTION JmFinishingTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of finishing." "The type of finishing."
Job Monitoring MIB, V0.81 April 24, 1997
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
-- Some other finishing besides one of the specified or -- Some other finishing besides one of the specified or
-- registered values. -- registered values.
unknown(2), unknown(2),
-- The finishing is unknown. -- The finishing is unknown.
none(3), none(3),
-- Perform no finishing. -- Perform no finishing.
staple(4), staple(4),
-- Bind the document(s) with one or more staples. The exact -- Bind the document(s) with one or more staples. The
-- number and placement of the staples is site-defined. -- exact number and placement of the staples is site-
-- defined.
stapleTopLeft(5), stapleTopLeft(5),
-- Place one or more staples on the top left corner of the -- Place one or more staples on the top left corner of
-- document(s). -- the document(s).
stapleBottomLeft(6), stapleBottomLeft(6),
-- Place one or more staples on the bottom left corner of -- Place one or more staples on the bottom left corner
-- the document(s). -- of the document(s).
stapleTopRight(7), stapleTopRight(7),
-- Place one or more staples on the top right corner of the -- Place one or more staples on the top right corner of
-- document(s). -- the document(s).
stapleBottomRight(8), stapleBottomRight(8),
-- Place one or more staples on the bottom right corner of -- Place one or more staples on the bottom right corner
-- the document(s). -- of the document(s).
saddleStitch(9), saddleStitch(9),
Job Monitoring MIB, V0.82 June 9, 1997
-- Bind the document(s) with one or more staples (wire -- Bind the document(s) with one or more staples (wire
-- stitches) along the middle fold. The exact number and -- stitches) along the middle fold. The exact number
-- placement of the stitches is site-defined. -- and placement of the stitches is site-defined.
edgeStitch(10), edgeStitch(10),
-- Bind the document(s) with one or more staples (wire -- Bind the document(s) with one or more staples (wire
-- stitches) along one edge. The exact number and -- stitches) along one edge. The exact number and
-- placement of the staples is site-defined. -- placement of the staples is site-defined.
punch(11), punch(11),
-- This value indicates that holes are required in the -- This value indicates that holes are required in the
-- finished document. The exact number and placement of the -- finished document. The exact number and placement of
-- holes is site-defined The punch specification may be -- the holes is site-defined The punch specification
-- satisfied (in a site- and implementation-specific -- MAY be satisfied (in a site- and implementation-
-- manner) either by drilling/punching, or by substituting -- specific manner) either by drilling/punching, or by
-- pre-drilled media. -- substituting pre-drilled media.
cover(12), cover(12),
-- This value is specified when it is desired to select a -- This value is specified when it is desired to select
-- non-printed (or pre-printed) cover for the document. -- a non-printed (or pre-printed) cover for the
-- This does not supplant the specification of a printed -- document. This does not supplant the specification of
-- cover (on cover stock medium) by the document itself. -- a printed cover (on cover stock medium) by the
-- document itself.
Job Monitoring MIB, V0.81 April 24, 1997
bind(13) bind(13)
-- This value indicates that a binding is to be applied to -- This value indicates that a binding is to be applied
-- the document; the type and placement of the binding is -- to the document; the type and placement of the
-- site-defined. -- binding is site-defined.
} }
JmPrintQualityTC ::= TEXTUAL-CONVENTION JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Print quality settings." "Print quality settings."
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- Not one of the specified or registered values. other(1), -- Not one of the specified or registered
-- values.
unknown(2), -- The actual value is unknown. unknown(2), -- The actual value is unknown.
draft(3), -- Lowest quality available on the printer. draft(3), -- Lowest quality available on the printer.
normal(4), -- Normal or intermediate quality on the printer. normal(4), -- Normal or intermediate quality on the
Job Monitoring MIB, V0.82 June 9, 1997
-- printer.
high(5) -- Highest quality available on the printer. high(5) -- Highest quality available on the printer.
} }
JmPrinterResolutionTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Printer resolutions.
The values are type2 enums that represent single integers or
pairs of integers. The latter are to specify the resolution
when the x and y dimensions differ. When two integers are
specified, the first is in the x direction, i.e., in the
direction of the shortest dimension of the medium, so that the
value is independent of whether the printer feeds long edge or
short edge first."
-- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER {
other(1), -- Not one of the specified or registered
-- values.
unknown(2), -- The actual value is unknown.
normal(3), -- Normal resolution.
res100(4), -- 100 x 100 dpi
res200(5), -- 200 x 200 dpi
res240(6), -- 240 x 240 dpi
res300(7), -- 300 x 300 dpi
res360(8), -- 360 x 360 dpi
res600(9), -- 600 x 600 dpi
res720(10), -- 720 x 720 dpi
res800(11), -- 800 x 800 dpi
res1200(12), -- 1200 x 1200 dpi
res1440(13), -- 1440 x 1440 dpi
res1800(14), -- 1800 x 1800 dpi
res100x200(15), -- 100 x 200 dpi
res300x600(16), -- 300 x 600 dpi
res600x300(17), -- 600 x 300 dpi
res360x720(18), -- 360 x 720 dpi
res720x360(19), -- 720 x 360 dpi
res400x800(20), -- 400 x 800 dpi
res800x400(21), -- 800 x 400 dpi
res600x1200(22), -- 600 x 1200 dpi
res1200x600(23), -- 1200 x 600 dpi
res720x1440(24), -- 720 x 1440 dpi
res1440x720(25), -- 1440 x 720 dpi
res1800x600(26) -- 1800 x 600 dpi
Job Monitoring MIB, V0.82 June 9, 1997
}
JmTonerEconomyTC ::= TEXTUAL-CONVENTION JmTonerEconomyTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Toner economy settings." "Toner economy settings."
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
off(0), -- Off. Normal. Use full toner. off(0), -- Off. Normal. Use full toner.
on(1) -- On. Use less toner than normal. on(1) -- On. Use less toner than normal.
} }
JmMediumTypeTC ::= TEXTUAL-CONVENTION JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the type of medium." "Identifies the type of medium."
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
Job Monitoring MIB, V0.81 April 24, 1997
other(1), other(1),
-- The type is neither one of the values listed in this -- The type is neither one of the values listed in this
-- specification nor a registered value. -- specification nor a registered value.
unknown(2), unknown(2),
-- The type is not known. -- The type is not known.
stationery(3), stationery(3),
-- Separately cut sheets of an opaque material. -- Separately cut sheets of an opaque material.
transparency(4), transparency(4),
-- Separately cut sheets of a transparent material. -- Separately cut sheets of a transparent material.
envelope(5), envelope(5),
-- Envelopes that can be used for conventional mailing -- Envelopes that can be used for conventional mailing
-- purposes. -- purposes.
envelopePlain(6), envelopePlain(6),
Job Monitoring MIB, V0.82 June 9, 1997
-- Envelopes that are not preprinted and have no windows. -- Envelopes that are not preprinted and have no windows.
envelopeWindow(7), envelopeWindow(7),
-- Envelopes that have windows for addressing purposes. -- Envelopes that have windows for addressing purposes.
continuousLong(8), continuousLong(8),
-- Continuously connected sheets of an opaque material -- Continuously connected sheets of an opaque material
-- connected along the long edge. -- connected along the long edge.
continuousShort(9), continuousShort(9),
-- Continuously connected sheets of an opaque material -- Continuously connected sheets of an opaque material
-- connected along the short edge. -- connected along the short edge.
tabStock(10), tabStock(10),
-- Media with tabs. -- Media with tabs.
multiPartForm(11), multiPartForm(11),
-- Form medium composed of multiple layers not pre-attached -- Form medium composed of multiple layers not pre-attached
-- to one another; each sheet may be drawn separately from -- to one another; each sheet MAY be drawn separately from
-- an input source. -- an input source.
labels(12), labels(12),
-- Label-stock. -- Label-stock.
multiLayer(13) multiLayer(13)
-- Form medium composed of multiple layers which are pre- -- Form medium composed of multiple layers which are pre-
-- attached to one another, e.g. for use with impact -- attached to one another, e.g. for use with impact
-- printers. -- printers.
} }
JmJobStateTC ::= TEXTUAL-CONVENTION JmJobStateTC ::= TEXTUAL-CONVENTION
Job Monitoring MIB, V0.81 April 24, 1997
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the job (pending, processing, held, etc.) "The current state of the job (pending, processing, completed,
etc.).
Management applications shall be prepared to receive all the The following figure shows the normal job state transitions:
standard job states. Agents instrumenting servers and devices
are not required to generate all job states, only those that are
indicated as 'mandatory' in the enum definitions below. The
remaining job states are 'conditionally mandatory', i.e., an
agent for a server or device shall implement each of the
remaining states if server or device jobs have states with the
same semantics. See Section 12 entitled 'Job Life Cycle' on
page 70 for additional job state semantics, legal job state
transitions, and implementation considerations.
Companion textual conventions (JmJobStateReasonsnTC, n=1..4) and +---->
corresponding attributes (jobStateReasonsn) provide additional canceled(7)
information about job states. While the job states cannot be /
added to without impacting deployed clients, it is the intent Job Monitoring MIB, V0.82 June 9, 1997
that additional JmJobStateReasonsnTC enums can be defined
without impacting deployed clients that take actions upon
receiving job state values. In other words, the
JmJobStateReasonsnTC TCs are intended to be extensible. See
page 45.
The following job state standard values are defined:" +----> pending(3) ---------> processing(5) -------+------>
completed(9)
| ^ ^ \
--->+ | | +---->
aborted(8)
| v v /
+----> pendingHeld(4) processingStopped(6) ----+
-- This is a type 2 enumeration. See Section 7.1 on page 17. Figure 4 - Normal Job State Transitions
Normally a job progresses from left to right. Other state
transitions are unlikely, but are not forbidden. Not shown are
the transitions to the canceled state from the pending,
pendingHeld, processing, and processingStopped states.
Jobs in the pending, processing, and processingStopped states
are called 'active', while jobs in the pendingHeld, canceled,
aborted, and completed are called 'in-active'."
-- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
-- The job state is not one of the defined states. -- The job state is not one of the defined states.
unknown(2), unknown(2),
-- The job state is not known, or is indeterminate. -- The job state is not known, or its state is
-- indeterminate.
held(3),
-- The job is not yet a candidate for processing for any
-- number of reasons. The reasons are represented as bits
-- in the jobStateReasons1 attribute. Some reasons are used
-- in other states to give added information about the job
-- state. See the JmJobStateReasons1TC textual convention
-- for the specification of each reason and in which states
-- the reasons may be used.
pending(4), pending(3),
-- The job is a candidate for processing, but is not yet -- The job is a candidate to start processing, but is
-- processing. -- not yet processing.
processing(5), -- mandatory pendingHeld(4),
-- The job is using one or more document transforms which -- The job is not a candidate for processing for any
-- include purely software processes, such as interpreting a -- number of reasons but will return to the pending
-- PDL, and hardware devices, but is not yet making marks on -- state as soon as the reasons are no longer
-- a medium. -- present. The job's jmJobStateReasons1 object
-- -- and/or jobStateReasonsn (n=2..4) attributes SHALL
-- If an implementation does not distinguish between -- indicate why the job is no longer a candidate for
Job Monitoring MIB, V0.81 April 24, 1997 -- processing. The reasons are represented as bits
-- in the jmJobStateReasons1 object and/or
-- jobStateReasonsn (n=2..4) attributes. See the
-- JmJobStateReasonsnTC (n=1..4) textual convention
-- on page (59) for the specification of each reason.
-- processing and printing, then the processing state shall processing(5),
-- be implemented. Job Monitoring MIB, V0.82 June 9, 1997
printing(6), -- Either:
-- The job is printing, i.e., making marks on a medium.
-- --
-- If an implementation does not distinguish between -- 1. The job is using, or is attempting to use, one
-- processing and printing, then the processing state shall -- or more document transforms which include (1)
-- be implemented. -- purely software processes that are interpreting a
-- PDL, and (2) hardware devices that are
needsAttention(7), -- mandatory -- interpreting a PDL, making marks on a medium,
-- The job is using one or more devices, but has encountered -- and/or performing finishing, such as stapling,
-- a problem with at least one device that requires human -- etc.
-- intervention before the job can continue using that
-- device. Examples include running out of paper or a paper
-- jam.
-- --
-- Usually devices indicate their condition in human -- OR
-- readable form locally at the device. The management --
-- application can obtain more complete device status -- 2. (configuration 2) the server has made the job
-- remotely by querying the appropriate device MIB using the -- ready for printing, but the output device is not
-- job's deviceIndex attribute. -- yet printing it, either because the job hasn't
-- reached the output device or because the job is
canceled(8), -- mandatory -- queued in the output device or some other spooler,
-- The job is in the process of being terminated by the -- awaiting the output device to print it.
-- server or device or has completed terminating the job, --
-- either because the client canceled the job or because a -- When the job is in the processing state, the
-- serious problem was encountered by a document transform -- entire job state includes the detailed status
-- while processing the job. The job's jobStateReasons1 -- represented in the device MIB indicated by the
-- attribute shall contain the reasons that the job was -- hrDeviceIndex value of the job's physicalDevice
-- canceled. The job shall remain in the canceled state for -- attribute, if the agent implements such a device
-- the same period of time as if the job had completed, -- MIB.
-- before transiting to the unknown state. See the --
-- completed state description. -- Implementations MAY, though they NEED NOT, include
-- additional values in the job's jmJobStateReasons1
-- object to indicate the progress of the job, such
-- as adding the jobPrinting value to indicate when
-- the device is actually making marks on a medium.
completed(9) -- mandatory processingStopped(6),
-- The job has (1) completed after processing/printing and -- The job has stopped while processing for any
-- all of the media have been successfully stacked in the -- number of reasons and will return to the
-- output bin(s). -- processing state as soon as the reasons are no
-- longer present.
-- --
-- The job has completed successfully or with warnings or -- The job's jmJobStateReasons1 object and/or the
-- errors. The job's jobStateReasons1 attribute shall -- job's jobStateReasonsn (n=2..4) attributes MAY
-- contain the reasons that the job has entered the -- indicate why the job has stopped processing. For
-- completed state. -- example, if the output device is stopped, the
-- deviceStopped value MAY be included in the job's
-- jmJobStateReasons1 object.
-- --
-- The length of time that a job may be in the completed -- NOTE - When an output device is stopped, the
-- state, before transitioning to unknown, is specified by Job Monitoring MIB, V0.82 June 9, 1997
-- the value of the jmGeneralJobPersistence object. In
-- addition, the agent shall maintain all of the attributes -- device usually indicate its condition in human
-- in the jmAttributeTable for at least the time specified -- readable form locally at the device. The
-- in the jmGeneralAttributePersistence object, so that a -- management application can obtain more complete
-- management application accounting program can copy all -- device status remotely by querying the appropriate
-- the attributes to an accounting log. -- device MIB using the job's deviceIndex
-- attribute(s), if the agent implements such a
-- device MIB
canceled(7),
-- A client has canceled the job and the job is
-- either: (1) in the process of being terminated by
-- the server or device or (2) has completed
-- terminating. The job's jmJobStateReasons1 object
-- SHOULD contain either the canceledByUser or
-- canceledByOperator value.
aborted(8),
-- The job has been aborted by the system, usually
-- while the job was in the processing or
-- processingStopped state.
completed(9)
-- The job has completed successfully or with
-- warnings or errors after processing and all of the
-- media have been successfully stacked in the
-- appropriate output bin(s). The job's
-- jmJobStateReasons1 object SHOULD contain one of:
-- completedSuccessfully, completedWithWarnings, or
-- completedWithErrors values.
} }
Job Monitoring MIB, V0.81 April 24, 1997
JmAttributeTypeTC ::= TEXTUAL-CONVENTION JmAttributeTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the attribute. "The type of the attribute which identifies the attribute.
Some attributes represent information about a job, such as a Some attributes represent information about a job, such as a
file-name, or a document-name, or submission-time or completion file-name, or a document-name, or submission-time or completion
time. Other attributes represent resources required, e.g., a time. Other attributes represent resources required, e.g., a
medium or a colorant, etc. to process the job before the job medium or a colorant, etc. to process the job before the job
start processing OR to indicate the amount of the resource that start processing OR to indicate the amount of the resource that
is being consumed while the job is processing, e.g., pages is being consumed while the job is processing, e.g., pages
completed or impressions completed. If both a required and a completed or impressions completed. If both a required and a
consumed value of a resource is needed, this specification consumed value of a resource is needed, this specification
assigns two separate attribute enums in the textual convention. assigns two separate attribute enums in the textual convention.
Datatypes Job Monitoring MIB, V0.82 June 9, 1997
The datatype of each attribute is indicated on the first line of Most attributes apply to all three configurations covered by
the description. Some attributes have several different data this MIB specification (see section 3 on page 14). Those
type representations. Each such representation is considered a attribute that apply to a particular configuration are indicated
as 'Configuration n:'.
Conformance of Attribute Implementation
A very few attributes are MANDATORY for conformance, and the
rest are OPTIONAL. An agent SHALL instrument any MANDATORY
attribute. If the server or device does not provide access to
the information about the MANDATORY attribute, the agent SHALL
return the 'unknown' value. For attributes represented by a
counting integer, the unknown value is (-2) and for attributes
represented by an enum, the unknown value is (2), as in the
Printer MIB[1]. For attributes represented by an OCTET STRING,
the unknown value is a zero-length string, unless specified
otherwise.
The MANDATORY attributes are:
jobOwner(20)
The attributes not labeled as MANDATORY are OPTIONAL. An agent
MAY, but NEED NOT, implement any OPTIONAL attributes.
NOTE - The table of contents lists all the attributes in order
to help see the order of enum assignments which is the order
that the GetNext operation can be used to get attributes. The
table of contents also indicates the MANDATORY attributes as:
(MANDATORY).
NOTE - The enum assignments are grouped logically with values
assigned in groups of 20, so that additional values may be
registered in the future and assigned a value that is part of
their logical grouping.
Datatypes and Attribute Naming Conventions
The datatype of each attribute is indicated on the first line(s)
of the description. Some attributes have several different data
type representations. When the data types can be represented in
a single row in the jmAttributeTable, the data type name is not
included as the last part of the name of the attribute. When
the data types cannot be represented by a single row in the
jmAttributeTable, each such representation is considered a
separate attribute and is assigned a separate name and enum separate attribute and is assigned a separate name and enum
value. For these attributes, the name of the datatype is the value. For these attributes, the name of the datatype is the
last part of the name of the attribute. Job Monitoring MIB, V0.82 June 9, 1997
last part of the name of the attribute: Name, Index,
DateAndTime, TimeStamp, etc.
NOTE: No attribute name exceeds 31 characters.
Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes
Most attributes shall have only one row per job. However, a few Most attributes SHALL have only one row per job. However, a few
attributes can have multiple values per job or even per attributes can have multiple values per job or even per
document, where each value is a separate row in the document, where each value is a separate row in the
jmAttributeTable. Unless indicated with 'MULTI-ROW:' in jmAttributeTable. Unless indicated with 'MULTI-ROW:' in
JmAttributeTypeTC, an agent shall ensure that each attribute JmAttributeTypeTC, an agent SHALL ensure that each attribute
item occurs only once in the jmAttributeTable for a job. item occurs only once in the jmAttributeTable for a job.
Attributes that may appear multiple times in the Attributes that are permitted to appear multiple times in the
jmAttributeTable for a job are indicated with 'MULTI-ROW:' in jmAttributeTable for a job are indicated with 'MULTI-ROW:' in
their specification in the JmAttributeTypeTC. However, such their specification in the JmAttributeTypeTC. However, such
attribute items shall not contain duplicates for 'intensive' (as 'MULTI-ROW' attribute items SHALL not contain duplicates for
opposed to 'extensive') attributes. 'intensive' (as opposed to 'extensive') attributes.
For example, each documentFormatType attribute entry For example, a job or document(s) may use multiple PDLs.
shall appear in the jmAttributeTable only once for a job However, each distinct documentFormat attribute value
SHALL appear in the jmAttributeTable only once for a job
since the interpreter language is an intensive attribute since the interpreter language is an intensive attribute
item, even though the job has a number of documents that item, even though the job has a number of documents that
all use the same PDL. all use the same PDL.
As another example of an intensive attribute that can As another example of an intensive attribute that can
have multiple entries, if a document or job uses have multiple entries, if a document or job uses
multiple types of media, there shall be only one row in multiple types of media, there SHALL be only one row in
the jmAttributeTable for each media type, not one row the jmAttributeTable for each media type, not one row
for each document that uses that medium type. for each document that uses that medium type.
On the other hand, if a job contains two documents of On the other hand, if a job contains two documents of
the same name, there can be separate rows for the the same name, there can be separate rows for the
Job Monitoring MIB, V0.81 April 24, 1997
documentName attribute item with the same name, since a documentName attribute item with the same name, since a
document name is an extensive attribute item. The document name is an extensive attribute item. The
specification indicates that the values need not be specification indicates that the values NEED NOT be
unique for such 'MULTI-ROW:' unique for such 'MULTI-ROW: attributes'
Value Represented As Integer Or Octets Value Represented As Integer Or Octets
In the following definitions of the enums, each description In the following definitions of the enums, each description
indicates whether the value of the attribute shall be indicates whether the value of the attribute SHALL be
represented using the jmAttributeValueAsInteger or the represented using the jmAttributeValueAsInteger or the
jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:'
or 'OCTETS:', respectively. A very few attributes use both or 'OCTETS:', respectively. Some attributes allow the agent a
objects at the same time to represent a pair of values choice of either an integer and/or an octets representation,
(mediumConsumed) and so have both tags. See the depending on implementation. These attributes are indicated
jmAttributeGroup on page 64 for the descriptions of these Job Monitoring MIB, V0.82 June 9, 1997
objects.
For the attributes that do not use the jmAttributeValueAsInteger
object (no 'INTEGER:' tag), the agent shall return the value (-
1) indicating other. For the attributes that do not use the
jmAttributeValueAsOctets object (no 'OCTETS:' tag), the agent
shall return a zero-length octet string.
Attribute Creation
An agent shall create a row in the jmAttributeTable for each with 'INTEGER:' and/or 'OCTETS:' tags. A very few attributes
attribute that is (1) supplied with a job when the job is require both objects at the same time to represent a pair of
accepted by a server or device or that (2) the server or device values (see mediumConsumed(171)). These attributes are
supplies as a default either when the job is accepted or later indicated with 'INTEGER:' and/or 'OCTETS:' tags. See the
during processing. jmAttributeGroup starting on page 81 for the descriptions of
these objects.
Consumption Attributes Consumption Attributes
A number of attributes record consumption. Such attribute names A number of attributes record consumption. Such attribute names
end with the word 'Completed'. If the job has not yet consumed end with the word 'Completed' or 'Consumed'. If the job has not
what that resource is metering, the agent either: (1) shall yet consumed what that resource is metering, the agent either:
return the value 0 or (2) shall not add this attribute to the (1) SHALL return the value 0 or (2) SHALL not add this attribute
jmAttributeTable until the consumption begins. In the interests to the jmAttributeTable until the consumption begins. In the
of brevity, the semantics for 0 is specified here and is not interests of brevity, the semantics for 0 is specified once here
repeated for each xxxxYyyyCompleted attribute specification. and is not repeated for each xxxxYyyyCompleted and
xxxxYyyyConsumed attribute specification.
Index Value Attributes Index Value Attributes
A number of attributes are indexes in other tables. Such A number of attributes are indexes in other tables. Such
attribute names end with the word 'Index'. If the agent does attribute names end with the word 'Index'. If the agent does
not (yet) know the index value for a particular index attribute not (yet) know the index value for a particular index attribute
for a job, the agent either: (1) shall return the value 0 or (2) for a job, the agent either: (1) SHALL return the value 0 or (2)
shall not add this attribute to the jmAttributeTable until the SHALL not add this attribute to the jmAttributeTable until the
index value is known. In the interests of brevity, the index value is known. In the interests of brevity, the
semantics for 0 is specified here and is not repeated for each semantics for 0 is specified once here and is not repeated for
index attribute specification. each index attribute specification.
Attribute Naming Conventions
Job Monitoring MIB, V0.81 April 24, 1997
Attribute names often end in the data type, especially when
there are more than one data type for the same information.
Thus the suffixes are used: Name, Index, DateAndTime, TimeStamp,
etc.
NOTE: No attribute name exceeds 31 characters.
Conformance of Attribute Implementation
Some attributes are mandatory for conformance, and the rest are
conditionally mandatory. An agent shall instrument any
mandatory attribute. If the server or device does not provide
access to the information about the mandatory attribute, the
agent shall return the 'unknown' value. For attributes
represented by a counting integer, the unknown value is (-2) and
for attributes represented by an enum, the unknown value is (2),
as in the Printer MIB[1]. An agent shall instrument any
conditionally mandatory attribute if the server or device
provides access to the information about the attribute to the
agent. If the server or device does not provide access to the
information about the conditionally mandatory attribute, the
agent need not create the row in the jmAttributeTable.
The mandatory attributes are the ones required to have copies in
the jmJobStateTable and to remain in the jmAttributeTable
longer. The mandatory attributes are:
jobState(3)
numberOfInterveningJobs(9)
deviceAlertCode(10)
jobKOctetsRequested(48)
jobKOctetsCompleted(50)
impressionsRequested(54)
impressionsCompleted(55)
outputBinName(35)
The table of contents lists the attributes in order to help see
the order of enum assignments which is the order that the
GetNext operation can be used to get attributes.
The standard attribute types defined so far are:" The standard attribute types defined so far are:"
-- This is a type 2 enumeration. See Section 7.1 on page 17. -- This is a type 2 enumeration. See Section 7.1 on page 22.
SYNTAX INTEGER { SYNTAX INTEGER {
-- jmAttributeTypeIndex Datatype -- jmAttributeTypeIndex Datatype
-- Description - including 'OCTETS:' or 'INTEGER:' to -- Description - including 'OCTETS:' or 'INTEGER:' to
-- specify whether the value shall be represented in the -- specify whether the value SHALL be represented in the
-- jmAttributeValueAsOctets or the jmAttributeValueAsInteger -- jmAttributeValueAsOctets or the jmAttributeValueAsInteger
-- object, or both, respectively. -- object, or both, respectively.
other(1), -- Integer32(-2..2147483647) other(1), -- Integer32(-2..2147483647)
-- OR -- AND/OR
-- OCTET STRING(SIZE(0..63)) -- OCTET STRING(SIZE(0..63))
-- INTEGER: or OCTETS: An attribute that is not in the -- INTEGER: and/or OCTETS: An attribute that is not in
-- list and/or that has not been approved and registered -- the list and/or that has not been approved and registered
Job Monitoring MIB, V0.81 April 24, 1997
-- with IANA. -- with IANA.
unknown(2), -- Integer32(-2..2147483647) unknown(2), -- Integer32(-2..2147483647)
Job Monitoring MIB, V0.82 June 9, 1997
-- OR -- OR
-- OCTET STRING(SIZE(0..63)) -- OCTET STRING(SIZE(0..63))
-- INTEGER: or OCTETS: An attribute whose semantics are -- INTEGER: or OCTETS: An attribute whose semantics are
-- not known to the agent. -- not known to the agent.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Job State attributes -- Job State attributes
-- --
-- The following attributes specify the state of a job. -- The following attributes specify the state of a job.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobState(3), -- JmJobStateTC (pg 24) jobStateReasons2(3), -- JmJobStateReasons2TC (pg 62)
-- INTEGER: The current state of the job (pending, -- INTEGER: Additional information about the job's current
-- processing, held, etc.). The final value for this -- state that augments the jmJobState object. See the
-- attribute shall be either completed or canceled, before -- description under the JmJobStateReasons1TC textual-
-- the agent removes the job from the table. -- convention on page 59.
--
-- Management applications shall be prepared to receive all
-- the standard job states. Servers and devices are not
-- required to generate all job states, only those which are
-- appropriate for the particular implementation.
--
-- NOTE - Companion textual conventions,
-- JmJobStateReasonsnTC (n=1..4 - see page 45) and
-- corresponding attributes (jobStateReasons1(5) - see page
-- 31) provides additional information about job states.
-- While the job states cannot be added to without impacting
-- deployed clients, it is the intent that additional
-- JmJobStateReasonsnTC enums can be defined without
-- impacting deployed clients.
jobStateAssociatedValue(4), -- Integer32(-2..2147483647)
-- INTEGER: The value of the most relevant attribute
-- associated with the job's current state.
--
-- Which attribute depends on the job's current state (as
-- specified by the value of the jmJobState/jobState
-- object/attribute) as follows:
--
-- jmJobState Associated Attribute Page
-- /jobState
--
-- held jobStartedBeingHeldTimeStamp(73) 43
-- pending numberOfInterveningJobs(9) 43
-- processing jobKOctetsRequested(48) 47
-- printing impressionsRequested(54) 49
-- needsAttention deviceAlertCode(10) 32
-- canceled impressionsCompleted(55) 41
-- completed outputBinName(35) 37
--
-- NOTE - The jobStateAssociatedValue attribute selects from
Job Monitoring MIB, V0.81 April 24, 1997
-- amongst seven mandatory attributes that attribute that is
-- most relevant to the job's current state. the
-- jobStateAssociatedValue attribute is provided as an
-- efficiency improvement, so that an application can obtain
-- the most relevant attribute for each job's current state
-- (1) without first having to determine the job's state or
-- (2) having to request all seven mandatory attributes in
-- the same GetNext operation that obtains the next job in
-- the next conceptual row in the jmAttributeTable.
jobStateReasons1(5), -- JmJobStateReasons1TC (pg 45)
-- OCTETS: Additional information about the job's current
-- state that augments the jmJobState/jobState
-- object/attribute. The jobStateReasons1 attribute
-- identifies the reason or reasons that the job is in the
-- held, pending, processing, needsAttention, canceled, or
-- completed state. The agent shall indicate the particular
-- reason(s) by setting the value of the jobStateReasons1
-- attribute. When the job does not have any reasons for
-- being in its current state, the agent shall set the value
-- of the jobStateReasons1 attribute to 0.
--
-- While the job states cannot be added to without impacting
-- deployed clients, it is the intent that additional
-- JmJobStateReasons1TC bit values can be defined without
-- impacting deployed clients. In other words, the
-- JmJobStateReasons1TC TC is intended to be extensible.
--
-- Companion job state reasons TCs: JmJobStateReasons2TC,
-- JmJobStateReasons3TC, JmJobStateReasons4TC, are
-- defined/reserved for additional 31*3 = 93 job state
-- reasons for use with the corresponding attributes:
-- jobStateReasons2, jobStateReasons3, and jobStateReasons4.
-- This is a type 2 bit definition. See section 7.1.2 on
-- page 17.
jobStateReasons2(6), -- JmJobStateReasons2TC (pg 45)
-- OCTETS: Additional information about the job's current
-- state that augments the jmJobState/jobState
-- object/attribute. See the description under
-- jobStateReasons1 attribute on page 31.
--
-- This is a type 2 bit definition. See section 7.1.2 on
-- page 17.
jobStateReasons3(7), -- JmJobStateReasons3TC (pg 45)
-- OCTETS: Additional information about the job's current
-- state that augments the jmJobState/jobState
-- object/attribute. See the description under
-- jobStateReasons1 attribute on page 31.
jobStateReasons4(8), -- JmJobStateReasons4TC (pg 45)
-- OCTETS: Additional information about the job's current
-- state that augments the jmJobState/jobState
-- object/attribute. See the description under
Job Monitoring MIB, V0.81 April 24, 1997
-- jobStateReasons1 attribute on page 31. jobStateReasons3(4), -- JmJobStateReasons3TC (pg 66)
-- INTEGER: Additional information about the job's current
-- state that augments the jmJobState object. See the
-- description under JmJobStateReasons1TC textual-convention
-- on page 59.
numberOfInterveningJobs(9), -- Integer32(-2..2147483647) jobStateReasons4(5), -- JmJobStateReasons4TC (pg 67)
-- INTEGER: The number of jobs that are expected to be -- INTEGER: Additional information about the job's current
-- processed before this job is processed according to the -- state that augments the jmJobState object. See the
-- implementation's queuing algorithm if no other jobs were -- description under JmJobStateReasons1TC textual-convention
-- to be submitted. In other words, this value is the job's -- on page 59.
-- queue position. The agent shall return a value of 0 for
-- this attribute when this job starts processing (since
-- there are no jobs in front of the job).
deviceAlertCode(10), -- PrtAlertCodeTC (Printer-MIB) deviceAlertCode(6), -- PrtAlertCodeTC (Printer-MIB)
-- INTEGER: The device alert code when the job is stopped -- INTEGER: The device alert code when the job is stopped
-- because the device needs attention, i.e., needs human -- because the device needs attention, i.e., needs human
-- intervention. When the device is a printer, this device -- intervention. When the device is a printer, this device
-- alert code shall be the printer alert code defined by the -- alert code SHALL be the printer alert code defined by the
-- Printer MIB[1] using the PrtAlertCodeTC textual -- Printer MIB[1] using the PrtAlertCodeTC textual
-- convention or equivalent. -- convention or equivalent.
processingMessage(11), -- OCTET STRING(SIZE(0..63)) processingMessage(7), -- OCTET STRING(SIZE(0..63))
-- OCTETS: MULTI-ROW: A coded character set message that -- OCTETS: MULTI-ROW: A coded character set message that
Job Monitoring MIB, V0.82 June 9, 1997
-- is generated during the processing of the job as a simple -- is generated during the processing of the job as a simple
-- form of processing log to show progress and any problems. -- form of processing log to show progress and any problems.
-- --
-- There is no restriction on the same message in multiple -- There is no restriction on the same message in multiple
-- rows. -- rows.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Job Identification attributes -- Job Identification attributes
-- --
-- The following attributes help an end user, a system -- The following attributes help an end user, a system
-- operator, or an accounting program identify a job. -- operator, or an accounting program identify a job.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
serverAssignedJobName(12), -- OCTET STRING(SIZE(0..63)) jobOwner(20), -- OCTET STRING(SIZE(0..63))
-- (MANDATORY)
-- OCTETS: The coded character set name of the user that
-- submitted the job. The method of assigning this user
-- name will be system and/or site specific but the method
-- must insure that the name is unique to the network that
-- is visible to the client and target device.
--
-- This value SHOULD be the authenticated name of the user
-- submitting the job.
--
-- In order to assist users to find their jobs for job
-- submission protocols that don't supply a
-- jmJobSubmissionID, the agent SHOULD maintain the jobOwner
-- attribute for the time specified by the
-- jmGeneralJobPersistence object, rather than the (shorter)
-- jmGeneralAttributePersistence object.
jobAccountName(21), -- OCTET STRING(SIZE(0..63))
-- OCTETS: Arbitrary binary information which MAY be coded
-- character set data or encrypted data supplied by the
-- submitting user for use by accounting services to
-- allocate or categorize charges for services provided,
-- such as a customer account name.
--
-- NOTE: This attribute NEED NOT be printable characters.
serverAssignedJobName(22), -- OCTET STRING(SIZE(0..63))
-- OCTETS: Configuration 3 only: The human readable string -- OCTETS: Configuration 3 only: The human readable string
-- name of the job as assigned by the server that submitted -- name of the job as assigned by the server that submitted
-- the job to the device that the agent in instrumenting -- the job to the device that the agent in instrumenting
-- with this MIB. -- with this MIB.
-- --
-- NOTE - This attribute is intended for enabling a user to -- NOTE - This attribute is intended for enabling a user to
Job Monitoring MIB, V0.82 June 9, 1997
-- find his/her job that a server submitted to a device -- find his/her job that a server submitted to a device
-- after the user submitted the job to the server when the -- after the user submitted the job to the server when the
-- jmJobIDGroup is not implemented. -- jmJobSubmissionID is not supported by the job submission
-- protocol.
jobName(13), -- OCTET STRING(SIZE(0..63)) jobName(23), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The human readable string name of the job as -- OCTETS: The human readable string name of the job as
-- assigned by the submitting user to help the user -- assigned by the submitting user to help the user
-- distinguish between his/her various jobs. This name does -- distinguish between his/her various jobs. This name does
-- not need to be unique. -- not need to be unique.
-- --
-- This attribute is intended for enabling a user or the -- This attribute is intended for enabling a user or the
-- user's application to convey a job name that may be -- user's application to convey a job name that MAY be
-- printed on a start sheet, returned in a query result, or -- printed on a start sheet, returned in a query result, or
Job Monitoring MIB, V0.81 April 24, 1997
-- used in notification or logging messages. -- used in notification or logging messages.
-- --
-- In order to assist users to find their jobs for job
-- submission protocols that don't supply a
-- jmJobSubmissionID, the agent SHOULD maintain the jobName
-- attribute for the time specified by the
-- jmGeneralJobPersistence object, rather than the (shorter)
-- jmGeneralAttributePersistence object.
--
-- If this attribute is not specified when the job is -- If this attribute is not specified when the job is
-- submitted, no job name is assumed, but implementation -- submitted, no job name is assumed, but implementation
-- specific defaults are allowed, such as the value of the -- specific defaults are allowed, such as the value of the
-- documentName resource item of the first document in the -- documentName attribute of the first document in the job
-- job or the fileName resource item of the first document -- or the fileName attribute of the first document in the
-- in the job. -- job.
-- --
-- The jobName attribute is distinguished from the -- The jobName attribute is distinguished from the
-- jobComment attribute, in that the jobName attribute is -- jobComment attribute, in that the jobName attribute is
-- intended to permit the submitting user to distinguish -- intended to permit the submitting user to distinguish
-- between different jobs that he/she has submitted. The -- between different jobs that he/she has submitted. The
-- jobComment attribute is intended to be free form -- jobComment attribute is intended to be free form
-- additional information that a user might wish to use to -- additional information that a user might wish to use to
-- communicate with himself/herself, such as a reminder of -- communicate with himself/herself, such as a reminder of
-- what to do with the results or to indicate a different -- what to do with the results or to indicate a different
-- set of input parameters were tried in several different -- set of input parameters were tried in several different
-- job submissions. -- job submissions.
jobServiceTypes(14), -- JmJobServiceTypesTC (pg 44) jobServiceTypes(24), -- JmJobServiceTypesTC (pg 57)
-- INTEGER: Specifies the type(s) of service to which the -- INTEGER: Specifies the type(s) of service to which the
-- job has been submitted (print, fax, scan, etc.). The -- job has been submitted (print, fax, scan, etc.). The
-- service type is bit encoded with each job service type so -- service type is bit encoded with each job service type so
-- that more general and arbitrary services can be created, -- that more general and arbitrary services can be created,
-- such as services with more than one destination type, or -- such as services with more than one destination type, or
-- ones with only a source or only a destination. For -- ones with only a source or only a destination. For
Job Monitoring MIB, V0.82 June 9, 1997
-- example, a job service might scan, faxOut, and print a -- example, a job service might scan, faxOut, and print a
-- single job. In this case, three bits would be set in the -- single job. In this case, three bits would be set in the
-- jobServiceTypes attribute, corresponding to the -- jobServiceTypes attribute, corresponding to the
-- hexadecimal values: 0x8 + 0x20 + 0x4, respectively, -- hexadecimal values: 0x8 + 0x20 + 0x4, respectively,
-- yielding: 0x2C. -- yielding: 0x2C.
-- --
-- Whether this attribute is set from a job attribute -- Whether this attribute is set from a job attribute
-- supplied by the job submission client or is set by the -- supplied by the job submission client or is set by the
-- recipient job submission server or device depends on the -- recipient job submission server or device depends on the
-- job submission protocol. This attribute shall be -- job submission protocol. This attribute SHALL be
-- implemented if the server or device has other types in -- implemented if the server or device has other types in
-- addition to or instead of printing. -- addition to or instead of printing.
-- --
-- One of the purposes of this attribute is to permit a -- One of the purposes of this attribute is to permit a
-- requester to filter out jobs that are not of interest. -- requester to filter out jobs that are not of interest.
-- For example, a printer operator may only be interested in -- For example, a printer operator may only be interested in
-- jobs that include printing. That is why this attribute -- jobs that include printing. That is why this attribute
-- is in the job identification category. -- is in the job identification category.
jobOwner(15), -- OCTET STRING(SIZE(0..63)) jobSourceChannelIndex(25), -- Integer32(0..2147483647)
-- OCTETS: The coded character set name of the user that
-- submitted the job. The method of assigning this user
-- name will be system and/or site specific but the method
-- must insure that the name is unique to the network that
-- is visible to the client and target device.
--
-- This value should be the authenticated name of the user
-- submitting the job.
Job Monitoring MIB, V0.81 April 24, 1997
jobAccountName(16), -- OCTET STRING(SIZE(0..63))
-- OCTETS: Arbitrary binary information which may be coded
-- character set data or encrypted data supplied by the
-- submitting user for use by accounting services to
-- allocate or categorize charges for services provided,
-- such as a customer account name.
--
-- NOTE: This attribute need not be printable characters.
jobSourceChannelIndex(17), -- Integer32(0..2147483647)
-- INTEGER: The index of the row in the associated Printer -- INTEGER: The index of the row in the associated Printer
-- MIB[1] of the channel which is the source of the print -- MIB[1] of the channel which is the source of the print
-- job. -- job.
-- --
-- NOTE - the Job Monitoring MIB points to the Channel row -- NOTE - the Job Monitoring MIB points to the Channel row
-- in the Printer MIB[1], so there is no need for a port -- in the Printer MIB[1], so there is no need for a port
-- attribute in the Job Monitoring MIB, since the PWG is -- attribute in the Job Monitoring MIB, since the PWG is
-- adding a prtChannelInformation object to the Channel -- adding a prtChannelInformation object to the Channel
-- table of the draft Printer MIB. -- table of the draft Printer MIB.
jobSourcePlatformType(18), -- JmJobSourcePlatformTypeTC jobSourcePlatformType(26), -- JmJobSourcePlatformTypeTC
-- (pg 21) -- (pg 27)
-- INTEGER: The source platform type of the immediate -- INTEGER: The source platform type of the immediate
-- upstream submitter that submitted the job to the server -- upstream submitter that submitted the job to the server
-- (configuration 2) or device (configuration 1 and 3) that -- (configuration 2) or device (configuration 1 and 3) that
-- the agent is instrumenting. For configuration 1, this is -- the agent is instrumenting. For configuration 1, this is
-- the type of the client that submitted the job to the -- the type of the client that submitted the job to the
-- device; for configuration 2, this is the type of the -- device; for configuration 2, this is the type of the
-- client that submitted the job to the server; and for -- client that submitted the job to the server; and for
-- configuration 3, this is the type of the server that -- configuration 3, this is the type of the server that
-- submitted the job to the device. -- submitted the job to the device.
submittingServerName(19), -- OCTET STRING(SIZE(0..63)) submittingServerName(27), -- OCTET STRING(SIZE(0..63))
-- OCTETS: For configuration 3 only: The administrative -- OCTETS: For configuration 3 only: The administrative
-- name of the server that submitted the job to the device. -- name of the server that submitted the job to the device.
submittingApplicationName(20), -- OCTET STRING(SIZE(0..63)) submittingApplicationName(28), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The name of the client application (not the -- OCTETS: The name of the client application (not the
Job Monitoring MIB, V0.82 June 9, 1997
-- server in configuration 3) that submitted the job to the -- server in configuration 3) that submitted the job to the
-- server or device. -- server or device.
deviceNameRequested(21), -- OCTET STRING(SIZE(0..63)) jobOriginatingHost(29), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The name of the client host (not the server host
-- name in configuration 3) that submitted the job to the
-- server or device.
deviceNameRequested(30), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The administratively defined coded character set -- OCTETS: The administratively defined coded character set
-- name of the target device requested by the submitting -- name of the target device requested by the submitting
-- user. For configuration 1, its value corresponds to the -- user. For configuration 1, its value corresponds to the
-- Printer MIB[1]: prtGeneralPrinterName object (added to -- Printer MIB[1]: prtGeneralPrinterName object (added to
-- the draft Printer MIB) for printers. For configuration 2 -- the draft Printer MIB) for printers. For configuration 2
-- and 3, its value is the name of the logical or physical -- and 3, its value is the name of the logical or physical
-- device that the user supplied to indicate to the server -- device that the user supplied to indicate to the server
-- on which device(s) they wanted the job to be processed. -- on which device(s) they wanted the job to be processed.
queueNameRequested(22), -- OCTET STRING(SIZE(0..63)) queueNameRequested(31), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The administratively defined coded character set -- OCTETS: The administratively defined coded character set
-- name of the target queue requested by the submitting -- name of the target queue requested by the submitting
Job Monitoring MIB, V0.81 April 24, 1997
-- user. For configuration 1, its value corresponds to the -- user. For configuration 1, its value corresponds to the
-- queue in the device that the agent is instrumenting. For -- queue in the device that the agent is instrumenting. For
-- configuration 2 and 3, its value is the name of the queue -- configuration 2 and 3, its value is the name of the queue
-- that the user supplied to indicate to the server on which -- that the user supplied to indicate to the server on which
-- device(s) they wanted the job to be processed. -- device(s) they wanted the job to be processed.
-- --
-- NOTE - typically an implementation should support either -- NOTE - typically an implementation SHOULD support either
-- the deviceNameRequested or queueNameRequested attribute, -- the deviceNameRequested or queueNameRequested attribute,
-- but not both. -- but not both.
physicalDeviceIndex(23), -- hrDeviceIndex (see HR MIB) physicalDevice(32), -- hrDeviceIndex (see HR MIB)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The index of the physical device -- INTEGER: MULTI-ROW: The index of the physical device
-- MIB instance requested/used, such as the Printer MIB[1]. -- MIB instance requested/used, such as the Printer MIB[1].
-- This value is an hrDeviceIndex value. See the Host -- This value is an hrDeviceIndex value. See the Host
-- Resources MIB[6]. -- Resources MIB[6].
-- AND/OR
physicalDeviceName(24), -- OCTET STRING(SIZE(0..63))
-- OCTETS: MULTI-ROW: The name of the physical device to -- OCTETS: MULTI-ROW: The name of the physical device to
-- which the job is assigned. -- which the job is assigned.
numberOfDocuments(25), -- Integer32(0..2147483647) numberOfDocuments(33), -- Integer32(0..2147483647)
-- INTEGER: The number of documents in this job. If this -- INTEGER: The number of documents in this job. If this
-- attribute is not present, the number of documents shall -- attribute is not present, the number of documents SHALL
-- be 1. -- be 1.
fileName(26), -- OCTET STRING(SIZE(0..63)) Job Monitoring MIB, V0.82 June 9, 1997
fileName(34), -- OCTET STRING(SIZE(0..63))
-- OCTETS: MULTI-ROW: The coded character set file name of -- OCTETS: MULTI-ROW: The coded character set file name of
-- the document. -- the document.
-- --
-- There is no restriction on the same file name in multiple -- There is no restriction on the same file name in multiple
-- rows. -- rows.
documentName(27), -- OCTET STRING(SIZE(0..63)) documentName(35), -- OCTET STRING(SIZE(0..63))
-- OCTETS: MULTI-ROW: The coded character set name of the -- OCTETS: MULTI-ROW: The coded character set name of the
-- document. -- document.
-- --
-- There is no restriction on the same document name in -- There is no restriction on the same document name in
-- multiple rows. -- multiple rows.
jobComment(28), -- OCTET STRING(SIZE(0..63)) jobComment(36), -- OCTET STRING(SIZE(0..63))
-- OCTETS: An arbitrary human-readable coded character text -- OCTETS: An arbitrary human-readable coded character text
-- string supplied by the submitting user or the job -- string supplied by the submitting user or the job
-- submitting application program for any purpose. For -- submitting application program for any purpose. For
-- example, a user might indicate what he/she is going to do -- example, a user might indicate what he/she is going to do
-- with the printed output or the job submitting application -- with the printed output or the job submitting application
-- program might indicate how the document was produced. -- program might indicate how the document was produced.
-- --
-- The jobComment attribute is not intended to be a name; -- The jobComment attribute is not intended to be a name;
-- see the jobName attribute. -- see the jobName attribute.
documentFormatIndex(29), -- Integer32(0..2147483647) documentFormatIndex(37), -- Integer32(0..2147483647)
-- INTEGER: MULTI-ROW: The interpreter language family -- INTEGER: MULTI-ROW: The index in the
-- index in the Printer MIB[1] of the -- prtInterpreterTable in the Printer MIB[1] of the page
-- prtInterpreterLangFamily object, that this job -- description language (PDL) or control language
-- requires/uses. A document or a job may use more than one -- interpreter that this job requires/uses. A document or a
Job Monitoring MIB, V0.81 April 24, 1997 -- job MAY use more than one PDL or control language.
-- PDL.
-- --
-- NOTE - As with all intensive attribute items where -- NOTE - As with all intensive attribute items where
-- multiple rows are allowed, there shall be only one -- multiple rows are allowed, there SHALL be only one
-- distinct row for each distinct PDL; there shall be no -- distinct row for each distinct interpreter; there SHALL
-- duplicates. -- be no duplicates.
-- --
-- NOTE - This attribute type is intended to be used with an -- NOTE - This attribute type is intended to be used with an
-- agent that implements the Printer MIB and shall not be -- agent that implements the Printer MIB and SHALL not be
-- used if the agent does not implement the Printer MIB. -- used if the agent does not implement the Printer MIB.
-- Such as agent shall use the documentFormatType attribute -- Such an agent SHALL use the documentFormat attribute
-- instead. -- instead.
documentFormatType(30), -- PrtInterpreterLangFamilyTC documentFormat(38), -- PrtInterpreterLangFamilyTC
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The interpreter language family -- INTEGER: MULTI-ROW: The interpreter language family
Job Monitoring MIB, V0.82 June 9, 1997
-- corresponding to the Printer MIB[1] -- corresponding to the Printer MIB[1]
-- prtInterpreterLangFamily object, that this job -- prtInterpreterLangFamily object, that this job
-- requires/uses. A document or a job may use more than one -- requires/uses. A document or a job MAY use more than one
-- PDL. -- PDL or control language.
-- --
-- NOTE - This attribute is represented by a type 2 enum -- NOTE - This attribute is represented by a type 2 enum
-- defined in the draft Printer MIB[1], but is not in RFC -- defined in the draft Printer MIB[1], but is not in RFC
-- 1759. -- 1759.
--
-- AND/OR
--
-- OCTETS: MULTI-ROW: The document format registered as a
-- MIME type, i.e., the name of the MIME type.
--
-- NOTE - IPP[3] uses MIME type keywords to identify
-- document formats.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Job Parameter attributes -- Job Parameter attributes
-- --
-- The following attributes represent input parameters -- The following attributes represent input parameters
-- supplied by the submitting client in the job submission -- supplied by the submitting client in the job submission
-- protocol. -- protocol.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobPriority(31), -- Integer32(1..100) jobPriority(50), -- Integer32(1..100)
-- INTEGER: The priority for scheduling the job. It is used -- INTEGER: The priority for scheduling the job. It is used
-- by servers and devices that employ a priority-based -- by servers and devices that employ a priority-based
-- scheduling algorithm. -- scheduling algorithm.
-- --
-- A higher value specifies a higher priority. The value 1 -- A higher value specifies a higher priority. The value 1
-- is defined to indicate the lowest possible priority (a -- is defined to indicate the lowest possible priority (a
-- job which a priority-based scheduling algorithm shall -- job which a priority-based scheduling algorithm SHALL
-- pass over in favor of higher priority jobs). The value -- pass over in favor of higher priority jobs). The value
-- 100 is defined to indicate the highest possible priority. -- 100 is defined to indicate the highest possible priority.
-- Priority is expected to be evenly or 'normally' -- Priority is expected to be evenly or 'normally'
-- distributed across this range. The mapping of vendor- -- distributed across this range. The mapping of vendor-
-- defined priority over this range is implementation- -- defined priority over this range is implementation-
-- specific. -- specific.
jobProcessAfterDateAndTime(32), -- DateAndTime (SNMPv2-TC) jobProcessAfterDateAndTime(51), -- DateAndTime (SNMPv2-TC)
-- INTEGER: The calendar date and time of day after which -- INTEGER: The calendar date and time of day after which
-- the job shall become a candidate to be scheduled for -- the job SHALL become a candidate to be scheduled for
-- processing. If the value of this attribute is in the -- processing. If the value of this attribute is in the
-- future, the server shall set the value of the job's -- future, the server SHALL set the value of the job's
-- jmJobState/jobState object/attribute to held and add the -- jmJobState object to pendingHeld and add the
-- jobProcessAfterSpecified bit value to the job's -- jobProcessAfterSpecified bit value to the job's
Job Monitoring MIB, V0.81 April 24, 1997 Job Monitoring MIB, V0.82 June 9, 1997
-- jobStateReasons1 attribute and shall not schedule the job -- jmJobStateReasons1 object and SHALL not schedule the job
-- for processing until the specified date and time has -- for processing until the specified date and time has
-- passed. When the specified date and time arrives, the -- passed. When the specified date and time arrives, the
-- server shall remove the jobProcessAfterSpecified bit -- server SHALL remove the jobProcessAfterSpecified bit
-- value from the job's jobStateReasons1 attribute and, if -- value from the job's jmJobStateReasons1 object and, if no
-- no other reasons remain, shall change the job's -- other reasons remain, SHALL change the job's jmJobState
-- jmJobState and the job's jobState attribute to pending so -- object to pending so that the job becomes a candidate for
-- that the job becomes a candidate for being scheduled on -- being scheduled on devices(s).
-- devices(s).
-- --
-- The agent shall assign an empty value to the -- The agent SHALL assign an empty value to the
-- jobProcessAfterDateAndTime attribute when no process -- jobProcessAfterDateAndTime attribute when no process
-- after time has been specified, so that the job shall be a -- after time has been specified, so that the job SHALL be a
-- candidate for processing immediately. -- candidate for processing immediately.
--
jobHold(52), -- Integer32(0..1)
-- INTEGER: If the value is 1, a client has explicitly
-- specified that the job is to be held until explicitly
-- released. Until the job is explicitly released by a
-- client, the job SHALL be in the pendingHeld state with
-- the jobHoldSpecified value in the jmJobStateReasons1
-- attribute.
jobHoldUntil(33), -- OCTET STRING(SIZE(0..63)) jobHoldUntil(53), -- OCTET STRING(SIZE(0..63))
-- OCTETS: The named time period during which the job shall -- OCTETS: The named time period during which the job SHALL
-- become a candidate for processing, such as 'no-hold', -- become a candidate for processing, such as 'no-hold',
-- 'evening', 'night', 'weekend', 'second-shift', 'third- -- 'evening', 'night', 'weekend', 'second-shift', 'third-
-- shift', etc., as defined by the system administrator. -- shift', etc., as defined by the system administrator.
-- Until that time period arrives, the job shall be in the -- Until that time period arrives, the job SHALL be in the
-- held state with the jobHoldUntilSpecified value in the -- pendingHeld state with the jobHoldUntilSpecified value in
-- jobStateReasons1 attribute. -- the jmJobStateReasons1 object.
outputBinIndex(34), -- Integer32(0..2147483647) outputBin(54), -- Integer32(0..2147483647)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The output subunit index in the -- INTEGER: MULTI-ROW: The output subunit index in the
-- Printer MIB[1] of the output bin to which all or part of -- Printer MIB[1]
-- the job is placed in. -- AND/OR
-- OCTETS: the name of the output bin to which all or part
outputBinName(35), -- OCTET STRING(SIZE(0..63)) -- of the job is placed in.
-- OCTETS: MULTI-ROW: The name of the output bin to which
-- all or part of the job is placed in.
sides(36), -- Integer32(-2..1) sides(55), -- Integer32(-2..1)
-- INTEGER: MULTI-ROW: The number of sides that any -- INTEGER: MULTI-ROW: The number of sides that any
-- document in this job requires/used. -- document in this job requires/used.
finishing(37), -- JmFinishingTC (pg 21) finishing(56), -- JmFinishingTC (pg 28)
-- INTEGER: MULTI-ROW: Type of finishing that any document -- INTEGER: MULTI-ROW: Type of finishing that any document
Job Monitoring MIB, V0.82 June 9, 1997
-- in this job requires/used. -- in this job requires/used.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Image Quality attributes (requested and consumed) -- Image Quality attributes (requested and consumed)
-- --
-- For devices that can vary the image quality. -- For devices that can vary the image quality.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityRequested(38), -- JmPrintQualityTC (pg 23) printQualityRequested(70), -- JmPrintQualityTC (pg 29)
-- INTEGER: MULTI-ROW: The print quality selection -- INTEGER: MULTI-ROW: The print quality selection
-- requested for document in the job for printers that allow -- requested for document in the job for printers that allow
-- quality differentiation. -- quality differentiation.
printQualityUsed(39), -- JmPrintQualityTC (pg 23) printQualityUsed(71), -- JmPrintQualityTC (pg 29)
-- INTEGER: MULTI-ROW: The print quality selection -- INTEGER: MULTI-ROW: The print quality selection
Job Monitoring MIB, V0.81 April 24, 1997 -- actually used by documents in the job for printers that
-- allow quality differentiation.
printerResolutionRequested(72), -- JmPrinterResolutionTC
-- (pg 30)
-- INTEGER: MULTI-ROW: The print quality selection
-- requested for document in the job for printers that allow
-- quality differentiation.
printerResolutionUsed(73), -- JmPrinterResolutionTC
-- (pg 30)
-- INTEGER: MULTI-ROW: The print quality selection
-- actually used by documents in the job for printers that -- actually used by documents in the job for printers that
-- allow quality differentiation. -- allow quality differentiation.
tonerEcomonyRequested(40), -- JmTonerEconomyTC (pg 23) tonerEcomonyRequested(74), -- JmTonerEconomyTC (pg 31)
-- INTEGER: MULTI-ROW: The print quality selection -- INTEGER: MULTI-ROW: The print quality selection
-- requested for documents in the job for printers that -- requested for documents in the job for printers that
-- allow toner quality differentiation. -- allow toner quality differentiation.
tonerEcomonyUsed(41), -- JmTonerEconomyTC (pg 23) tonerEcomonyUsed(75), -- JmTonerEconomyTC (pg 31)
-- INTEGER: MULTI-ROW: The print quality selection -- INTEGER: MULTI-ROW: The print quality selection
-- actually used by documents in the job for printers that -- actually used by documents in the job for printers that
-- allow toner quality differentiation. -- allow toner quality differentiation.
tonerDensityRequested(42), -- Integer32(1..20) tonerDensityRequested(76), -- Integer32(1..20)
-- INTEGER: MULTI-ROW: The toner density requested for -- INTEGER: MULTI-ROW: The toner density requested for
-- documents in this job for devices that can vary toner -- documents in this job for devices that can vary toner
-- density levels. Level 1 is the lowest density and level -- density levels. Level 1 is the lowest density and level
-- 20 is the highest density level. Devices with a smaller -- 20 is the highest density level. Devices with a smaller
-- range, shall map the 1-20 range evenly onto the -- range, SHALL map the 1-20 range evenly onto the
-- implemented range. -- implemented range.
tonerDensityUsed(43), -- Integer32(1..20) Job Monitoring MIB, V0.82 June 9, 1997
tonerDensityUsed(77), -- Integer32(1..20)
-- INTEGER: MULTI-ROW: The toner density used by documents -- INTEGER: MULTI-ROW: The toner density used by documents
-- in this job for devices that can vary toner density -- in this job for devices that can vary toner density
-- levels. Level 1 is the lowest density and level 20 is -- levels. Level 1 is the lowest density and level 20 is
-- the highest density level. Devices with a smaller range, -- the highest density level. Devices with a smaller range,
-- shall map the 1-20 range evenly onto the implemented -- SHALL map the 1-20 range evenly onto the implemented
-- range. -- range.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Job Progress attributes (requested and consumed) -- Job Progress attributes (requested and consumed)
-- --
-- Pairs of these attributes can be used by monitoring -- Pairs of these attributes can be used by monitoring
-- applications to show 'thermometers' of progress to users. -- applications to show 'thermometers' of progress to users.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobCopiesRequested(44), -- Integer32(-2..2147483647) jobCopiesRequested(90), -- Integer32(-2..2147483647)
-- INTEGER: The number of copies of the entire job that are -- INTEGER: The number of copies of the entire job that are
-- to be produced. -- to be produced.
jobCopiesCompleted(45), -- Integer32(-2..2147483647) jobCopiesCompleted(91), -- Integer32(-2..2147483647)
-- INTEGER: The number of copies of the entire job that -- INTEGER: The number of copies of the entire job that
-- have been completed so far. -- have been completed so far.
documentCopiesRequested(46), -- Integer32(-2..2147483647) documentCopiesRequested(92), -- Integer32(-2..2147483647)
-- INTEGER: The total count of the number of document -- INTEGER: The total count of the number of document
-- copies requested. If there are documents A, B, and C, -- copies requested. If there are documents A, B, and C,
-- and document B is specified to produce 4 copies, the -- and document B is specified to produce 4 copies, the
-- number of document copies requested is 6 for the job. -- number of document copies requested is 6 for the job.
--
-- This attribute SHALL be used only when a job has multiple
-- documents. The jobCopiesRequested attribute SHALL be
-- used when the job has only one document.
documentCopiesCompleted(47), -- Integer32(-2..2147483647) documentCopiesCompleted(93), -- Integer32(-2..2147483647)
-- INTEGER: The total count of the number of document -- INTEGER: The total count of the number of document
-- copies completed so far for the job as a whole. If there -- copies completed so far for the job as a whole. If there
-- are documents A, B, and C, and document B is specified to -- are documents A, B, and C, and document B is specified to
Job Monitoring MIB, V0.81 April 24, 1997
-- produce 4 copies, the number of document copies starts a -- produce 4 copies, the number of document copies starts a
-- 0 and runs up to 6 for the job as the job processes. -- 0 and runs up to 6 for the job as the job processes.
jobKOctetsRequested(48), -- Integer32(-2..2147483647)
-- INTEGER: The total number of K (1024) octets being
-- requested to be processed in the job, including document
-- and job copies. The agent shall round the actual number
-- of octets up to the next highest K. Thus 0 octets shall
-- be represented as 0, 1-1024 octets shall be represented
-- as 1, 1025-2048 shall be represented as 2, etc.
--
-- The server/device may update the value of this attribute
-- after each document has been transferred to the
-- server/device or the server/device may provide this value
-- after all documents have been transferred to the
-- server/device, depending on implementation. In other
-- words, while the job is in the held state with the
-- jobStateReasons1 attribute containing a documentsNeeded
-- or preProcessing value, the value of the
-- jobKOctetsRequested attribute depends on implementation
-- and may not correctly reflect the size of the job.
--
-- In computing this value, the server/device shall include
-- the multiplicative factors contributed by (1) the number
-- of document copies, and (2) the number of job copies,
-- independent of whether the device can process multiple
-- copies of the job or document without making multiple
-- passes over the job or document data and independent of
-- whether the output is collated or not. Thus the
-- server/device computation is independent of the
-- implementation and shall be:
--
-- (1) Document contribution: Multiply the size of each
-- document in octets by the number of document copies
-- of that document.
--
-- (2) Add each document contribution together.
-- --
-- (3) Job copy contribution: Multiply the job size by -- This attribute SHALL be used only when a job has multiple
-- the number of job copies. -- documents. The jobCopiesCompleted attribute SHALL be
-- -- used when the job has only one document.
-- (4) Round up the result to the next higher K (1024
-- multiple).
jobKOctetsTransferred(49), -- Integer32(-2..2147483647) Job Monitoring MIB, V0.82 June 9, 1997
jobKOctetsTransferred(94), -- Integer32(-2..2147483647)
-- INTEGER: The number of K (1024) octets transferred to -- INTEGER: The number of K (1024) octets transferred to
-- the server or device that the agent is instrumenting. -- the server or device that the agent is instrumenting.
-- This count is independent of the number of copies of the -- This count is independent of the number of copies of the
-- job or documents that will be produced, but is just a -- job or documents that will be produced, but is just a
-- measure of the number of bytes transferred to the server -- measure of the number of bytes transferred to the server
-- or device. -- or device.
-- --
-- The agent shall round the actual number of octets -- The agent SHALL round the actual number of octets
-- completed up to the next higher K. Thus 0 octets is -- transferred up to the next higher K. Thus 0 octets SHALL
-- represented as 0, 1-1023, is represented as 1, 1024-2047 -- be represented as 0, 1-1024 octets SHALL BE represented
Job Monitoring MIB, V0.81 April 24, 1997 -- as 1, 1025-2048 SHALL be 2, etc. When the job completes,
-- the values of the jmJobKOctetsRequested object and the
-- is 2, etc. When the job completes, the values of the -- jobKOctetsTransferred attribute SHALL be equal.
-- jobKOctetsRequested and the jobKOctetsTransferred
-- attributes shall be equal.
-- --
-- NOTE - The jobKOctetsTransferred can be used in the -- NOTE - The jobKOctetsTransferred can be used in the
-- numerator with the jobKOctetsRequested attribute in the -- numerator with the jmJobKOctetsRequested object in the
-- denominator in order to produce a "thermometer" that -- denominator in order to produce a "thermometer" that
-- indicates the progress of the job for agents that do not -- indicates the progress of the job for agents that do not
-- instrument the jobKOctetsCompleted attribute. -- implement the jmJobKOctetsProcessed object.
jobKOctetsCompleted(50), -- Integer32(-2..2147483647)
-- INTEGER: The number of K (1024) octets currently
-- processed by the server or device, including document and
-- job copies. For printing, the completed count only
-- includes processing (interpreting) if the implementation
-- distinguishes between the processing and printing states;
-- otherwise, the completed count includes both processing
-- (interpreting) and marking combined together. For
-- scanning, the completed count only includes scanning, if
-- the implementation distinguishes between the processing
-- and (to be registered) scanning states; otherwise the
-- completed count includes both scanning and processing
-- (formatting).
--
-- The agent shall round the actual number of octets
-- completed up to the next higher K. Thus 0 octets is
-- represented as 0, 1-1023, is represented as 1, 1024-2047
-- is 2, etc. When the job completes, the values of the
-- jobKOctetsRequested and the jobKOctetsCompleted
-- attributes shall be equal.
--
-- For multiple copies generated from a single data stream,
-- the value shall be incremented as if each copy was
-- printed from a new data stream without resetting the
-- count between copies. See the pagesCompletedCurrentCopy
-- attribute that is reset on each document copy.
--
-- NOTE - The jobKOctetsCompleted can be used in the
-- numerator with the jobKOctetsRequested attribute in the
-- denominator in order to produce a "thermometer" that
-- indicates the progress of the job.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Impression attributes -- Impression attributes
-- --
-- For a print job, an impression is the marking of the -- For a print job, an impression is the marking of the
-- entire side of a sheet. Two-sided processing involves two -- entire side of a sheet. Two-sided processing involves two
-- impressions per sheet. Two-up is the placement of two -- impressions per sheet. Two-up is the placement of two
-- logical pages on one side of a sheet and so is still a -- logical pages on one side of a sheet and so is still a
-- single impression. -- single impression. See also jmJobImpressionsRequested and
-- jmJobImpressionsCompleted objects in the jmJobTable on page
-- 80.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
impressionsSpooled(51), -- Integer32(-2..2147483647) impressionsSpooled(110), -- Integer32(-2..2147483647)
-- INTEGER: The number of impressions spooled to the server -- INTEGER: The number of impressions spooled to the server
Job Monitoring MIB, V0.81 April 24, 1997
-- or device for the job so far. -- or device for the job so far.
impressionsSentToDevice(52), -- Integer32(-2..2147483647) impressionsSentToDevice(111), -- Integer32(-2..2147483647)
-- INTEGER: The number of impressions sent to the device -- INTEGER: The number of impressions sent to the device
-- for the job so far. -- for the job so far.
impressionsInterpreted(53), -- Integer32(-2..2147483647) impressionsInterpreted(112), -- Integer32(-2..2147483647)
-- INTEGER: The number of impressions interpreted for the -- INTEGER: The number of impressions interpreted for the
-- job so far. -- job so far.
impressionsRequested(54), -- Integer32(-2..2147483647) Job Monitoring MIB, V0.82 June 9, 1997
-- INTEGER: The number of impressions requested by this job
-- to produce.
impressionsCompleted(55), -- Integer32(-2..2147483647)
-- INTEGER: The total number of impressions completed by
-- the device for this job so far. For printing, the
-- impressions completed includes interpreting, marking, and
-- stacking the output. For other types of job services,
-- the number of impressions completed includes the number
-- of impressions processed.
impressionsCompletedCurrentCopy(56), -- Integer32(-2.. impressionsCompletedCurrentCopy(113), -- Integer32(-2..
-- 2147483647) -- 2147483647)
-- INTEGER: The number of impressions completed by the -- INTEGER: The number of impressions completed by the
-- device for the current copy of the current document so -- device for the current copy of the current document so
-- far. For printing, the impressions completed includes -- far. For printing, the impressions completed includes
-- interpreting, marking, and stacking the output. For -- interpreting, marking, and stacking the output. For
-- other types of job services, the number of impressions -- other types of job services, the number of impressions
-- completed includes the number of impressions processed. -- completed includes the number of impressions processed.
-- --
-- This value shall be reset to 0 for each document in the -- This value SHALL be reset to 0 for each document in the
-- job and for each document copy. -- job and for each document copy.
fullColorImpressionsCompleted(114), -- Integer32(-2..
-- 2147483647)
-- INTEGER: The number of full color impressions completed
-- by the device for this job so far. For printing, the
-- impressions completed includes interpreting, marking, and
-- stacking the output. For other types of job services,
-- the number of impressions completed includes the number
-- of impressions processed. Full color impressions are
-- typically defined as those requiring 3 or more colorants,
-- but this MAY vary by implementation.
--
highlightColorImpressionsCompleted(115), -- Integer32(-2..
-- 2147483647)
-- INTEGER: The number of highlight color impressions
-- completed by the device for this job so far. For
-- printing, the impressions completed includes
-- interpreting, marking, and stacking the output. For
-- other types of job services, the number of impressions
-- completed includes the number of impressions processed.
-- Highlight color impressions are typically defined as
-- those requiring black plus one other colorant, but this
-- MAY vary by implementation.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Page attributes -- Page attributes
-- --
-- A page is a logical page. Number up can impose more than -- A page is a logical page. Number up can impose more than
-- one page on a single side of a sheet. Two-up is the -- one page on a single side of a sheet. Two-up is the
-- placement of two logical pages on one side of a sheet so -- placement of two logical pages on one side of a sheet so
-- that each side counts as two pages. -- that each side counts as two pages.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.82 June 9, 1997
pagesRequested(57), -- Integer32(-2..2147483647) pagesRequested(130), -- Integer32(-2..2147483647)
-- INTEGER: The number of logical pages requested by the -- INTEGER: The number of logical pages requested by the
-- job to be processed. -- job to be processed.
pagesCompleted(58), -- Integer32(-2..2147483647) pagesCompleted(131), -- Integer32(-2..2147483647)
-- INTEGER: The total number of logical pages completed for -- INTEGER: The number of logical pages completed for this
-- this job so far. -- job so far.
pagesCompletedCurrentCopy(59), -- Integer32(-2..2147483647) pagesCompletedCurrentCopy(132), -- Integer32(-2..2147483647)
-- INTEGER: The number of logical pages completed for the -- INTEGER: The number of logical pages completed for the
-- current copy of the document so far. This value shall be -- current copy of the document so far. This value SHALL be
Job Monitoring MIB, V0.81 April 24, 1997
-- reset to 0 for each document in the job and for each -- reset to 0 for each document in the job and for each
-- document copy. -- document copy.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Sheet attributes -- Sheet attributes
-- --
-- The sheet is a single piece of a medium, whether printing -- The sheet is a single piece of a medium, whether printing
-- on one or both sides. -- on one or both sides.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sheetsRequested(60), -- Integer32(-2..2147483647) sheetsRequested(150), -- Integer32(-2..2147483647)
-- INTEGER: The total number of medium sheets requested to -- INTEGER: The number of medium sheets requested to be
-- be processed for this job. -- processed for this job.
sheetsCompleted(61), -- Integer32(-2..2147483647)
-- INTEGER: The total number of medium sheets that have
-- completed marking and stacking for the entire job so far
-- whether those sheets have been processed on one side or
-- on both.
sheetsCompletedCurrentCopy(62), -- Integer32(-2..2147483647) sheetsCompleted(151), -- Integer32(-2..2147483647)
-- INTEGER: The number of medium sheets that have completed
-- marking and stacking for the entire job so far whether
-- those sheets have been processed on one side or on both.
--
sheetsCompletedCurrentCopy(152), -- Integer32(-2..2147483647)
-- INTEGER: The number of medium sheets that have completed -- INTEGER: The number of medium sheets that have completed
-- marking and stacking for the current copy of a document -- marking and stacking for the current copy of a document
-- in the job so far whether those sheets have been -- in the job so far whether those sheets have been
-- processed on one side or on both. -- processed on one side or on both.
-- --
-- The value of this attribute shall be reset to 0 as each -- The value of this attribute SHALL be reset to 0 as each
-- document in the job starts being processed and for each -- document in the job starts being processed and for each
-- document copy as it starts being processed. -- document copy as it starts being processed.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Resources attributes (requested and consumed) -- Resources attributes (requested and consumed)
-- --
-- Pairs of these attributes can be used by monitoring -- Pairs of these attributes can be used by monitoring
-- applications to show 'thermometers' of usage to users. -- applications to show 'thermometers' of usage to users.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mediumRequestedType(63), -- JmMediumTypeTC (pg 23) Job Monitoring MIB, V0.82 June 9, 1997
-- OCTETS: MULTI-ROW: The type of the medium that is
-- required by the job.
mediumRequestedName(64), -- OCTET STRING(SIZE(0..63)) -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- OCTETS: MULTI-ROW: The name of the medium that is
-- required by the job.
mediumConsumedName(65), -- OCTET STRING(SIZE(0..63)) mediumRequested(170), -- JmMediumTypeTC (pg 31)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The type
-- AND/OR
-- OCTETS: the name of the medium that is required by the
-- job.
mediumConsumed(171), -- OCTET STRING(SIZE(0..63))
-- AND -- AND
-- Integer32(-2..2147483647) -- Integer32(-2..2147483647)
-- OCTETS: MULTI-ROW: The name of the medium AND -- OCTETS: MULTI-ROW: The name of the medium
-- -- AND
-- INTEGER: the number of sheets that have been consumed so -- INTEGER: the number of sheets that have been consumed so
-- far whether those sheets have been processed on one side -- far whether those sheets have been processed on one side
-- or on both. This attribute shall have both values. -- or on both. This attribute SHALL have both values.
Job Monitoring MIB, V0.81 April 24, 1997
colorantRequestedIndex(66), -- Integer32(0..2147483647) colorantRequested(172), -- Integer32(0..2147483647)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) -- INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex)
-- in the Printer MIB[1] of the colorant requested. -- in the Printer MIB[1]
-- AND/OR
colorantRequestedName(67), -- OCTET STRING(SIZE(0..63)) -- OCTETS: the name of the colorant requested.
-- OCTETS: MULTI-ROW: The name of the colorant requested.
colorantConsumedIndex(68), -- Integer32(0..2147483647) colorantConsumed(173), -- Integer32(0..2147483647)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) -- INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex)
-- in the Printer MIB[1] of the colorant consumed. -- in the Printer MIB[1]
-- AND/OR
colorantConsumedName(69), -- OCTET STRING(SIZE(0..63)) -- OCTETS: the name of the colorant consumed.
-- OCTETS: MULTI-ROW: The name of the colorant consumed.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Time attributes (set by server or device) -- Time attributes (set by server or device)
-- --
-- This section of attributes are ones that are set by the -- This section of attributes are ones that are set by the
-- server or device that accepts jobs. Two forms of time are -- server or device that accepts jobs. Two forms of time are
-- provided. Each form is represented in a separate attribute. -- provided. Each form is represented in a separate attribute.
-- See section 4.2 on page 14 and section 4.3 on page 15 for the
Job Monitoring MIB, V0.82 June 9, 1997
-- See section 4.2 on page 19 and section 4.3 on page 20 for the
-- conformance requirements for agents and monitoring -- conformance requirements for agents and monitoring
-- applications, respectively. The two forms are: -- applications, respectively. The two forms are:
-- --
-- DateAndTime is an 8 or 11 octet binary encoded year, -- DateAndTime is an 8 or 11 octet binary encoded year,
-- month, day, hour, minute, second, deci-second with -- month, day, hour, minute, second, deci-second with
-- optional offset from UTC. See SNMPv2-TC. -- optional offset from UTC. See SNMPv2-TC.
-- --
-- NOTE: DateAndTime is not printable characters; it is -- NOTE: DateAndTime is not printable characters; it is
-- binary. -- binary.
-- --
-- JmTimeStampTC is the time of day measured in the number of -- JmTimeStampTC is the time of day measured in the number of
-- seconds since the system was booted. See page 20. -- seconds since the system was booted. See page 27.
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobSubmissionToServerDateAndTime(70), -- DateAndTime (SNMPv2-TC) jobSubmissionToServerTime(190), -- JmTimeStampTC (pg 27)
-- OCTETS: Configuration 2 and 3: The date and time that -- AND/OR
-- the job was submitted to the server. -- DateAndTime (SNMPv2-TC)
-- INTEGER: Configuration 2 and 3: The time
-- AND/OR
-- OCTETS: the date and time that the job was submitted to
-- the server.
jobSubmissionToDeviceDateAndTime(71), -- DateAndTime (SNMPv2-TC) jobSubmissionToDeviceTime(191), -- JmTimeStampTC (pg 27)
-- OCTETS: Configuration 1 and 3: The date and time that -- AND/OR
-- the job was submitted to the device. -- DateAndTime (SNMPv2-TC)
-- INTEGER: Configuration 1 and 3: The time
-- AND/OR
-- OCTETS: the date and time that the job was submitted to
-- the device.
jobSubmissionToDeviceTimeStamp(72), -- JmTimeStampTC (pg 20) timeSinceJobWasSubmittedToDevice(192), -- Integer32(0..
-- INTEGER: The time that the job was submitted. -- 2147483647)
-- INTEGER: The time in seconds since the job was submitted
-- to the device.
jobStartedBeingHeldTimeStamp(73), -- JmTimeStampTC (pg 20) jobStartedBeingHeldTimeStamp(193), -- JmTimeStampTC (pg 27)
-- INTEGER: The time that the job started being held, i.e., -- INTEGER: The time that the job started being held, i.e.,
-- the time that the job entered the held state most -- the time that the job entered the pendingHeld state most
-- recently. If the job has never entered the held state, -- recently. If the job has never entered the pendingHeld
-- then the value shall be 0 or the attribute shall not be -- state, then the value SHALL be 0 or the attribute SHALL
-- present in the table. -- not be present in the table.
Job Monitoring MIB, V0.81 April 24, 1997 jobStartedProcessingTime(194), -- JmTimeStampTC (pg 27)
-- AND/OR
-- DateAndTime (SNMPv2-TC)
Job Monitoring MIB, V0.82 June 9, 1997
jobStartedProcessingDateAndTime(74), -- DateAndTime (SNMPv2-TC) -- INTEGER: The time
-- OCTETS: The date and time that the job started -- AND/OR
-- OCTETS: the date and time that the job started
-- processing. -- processing.
jobStartedProcessingTimeStamp(75), -- JmTimeStampTC (pg 20) timeSinceStartedProcessing(195), -- Integer32(-2..2147483647)
-- INTEGER: The time that the job started processing. -- INTEGER: The time in milliseconds since the job started
-- processing.
jobCompletedDateAndTime(76), -- DateAndTime (SNMPv2-TC) jobCompletedTime(196), -- JmTimeStampTC (pg 27)
-- OCTETS: The date and time that the job completed -- AND/OR
-- DateAndTime (SNMPv2-TC)
-- INTEGER: The time
-- AND/OR
-- OCTETS: the date and time that the job completed
-- processing and the medium is completely stacked in the -- processing and the medium is completely stacked in the
-- output bin, i.e., when the job entered the completed -- output bin, i.e., when the job entered the completed,
-- state. -- canceled, or aborted state.
jobCompletedTimeStamp(77), -- JmTimeStampTC (pg 20) timeSinceCompleted(197), -- Integer32(-2..2147483647)
-- INTEGER: The time that the job completed processing and -- INTEGER: The time in milliseconds since the job
-- the medium is completely stacked in the output bin, i.e., -- completed processing and the medium was completely
-- when the job entered the completed state. -- stacked in the output bin, i.e., since the job entered
-- the completed, canceled, or aborted state.
jobProcessingCPUTime(78) -- Integer32(-2..2147483647) jobProcessingCPUTime(198) -- Integer32(-2..2147483647)
-- INTEGER: The amount of CPU time that the job has been -- INTEGER: The amount of CPU time that the job has been
-- processing in seconds. If the job needs attention, that -- processing in seconds, i.e., in the processing job state.
-- elapsed time shall not be included. In other words, the -- If the device stops and/or the job enters the
-- jobProcessingCPUTime value should be relatively -- processingStopped state, that elapsed time SHALL not be
-- repeatable when the same job is submitted again. -- included. In other words, the jobProcessingCPUTime value
-- SHOULD be relatively repeatable when the same job is
-- submitted again.
} }
JmJobServiceTypesTC ::= TEXTUAL-CONVENTION JmJobServiceTypesTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.82 June 9, 1997
"Specifies the type(s) of service to which the job has been "Specifies the type(s) of service to which the job has been
submitted (print, fax, scan, etc.). The service type is submitted (print, fax, scan, etc.). The service type is
represented as an enum that is bit encoded with each job service represented as an enum that is bit encoded with each job service
type so that more general and arbitrary services can be created, type so that more general and arbitrary services can be created,
such as services with more than one destination type, or ones such as services with more than one destination type, or ones
with only a source or only a destination. For example, a job with only a source or only a destination. For example, a job
service might scan, faxOut, and print a single job. In this service might scan, faxOut, and print a single job. In this
case, three bits would be set in the jobServiceTypes attribute, case, three bits would be set in the jobServiceTypes attribute,
corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4,
respectively, yielding: 0x2C. respectively, yielding: 0x2C.
Whether this attribute is set from a job attribute supplied by Whether this attribute is set from a job attribute supplied by
the job submission client or is set by the recipient job the job submission client or is set by the recipient job
submission server or device depends on the job submission submission server or device depends on the job submission
protocol. With either implementation, the agent shall return a protocol. With either implementation, the agent SHALL return a
non-zero value for this attribute indicating the type of the non-zero value for this attribute indicating the type of the
job. job.
One of the purposes of this attribute is to permit a requester One of the purposes of this attribute is to permit a requester
to filter out jobs that are not of interest. For example, a to filter out jobs that are not of interest. For example, a
printer operator may only be interested in jobs that include printer operator MAY only be interested in jobs that include
Job Monitoring MIB, V0.81 April 24, 1997
printing. That is why the attribute is in the job printing. That is why the attribute is in the job
identification category. identification category.
The following service component types are defined (in The following service component types are defined (in
hexadecimal) and are assigned a separate bit value for use with hexadecimal) and are assigned a separate bit value for use with
the jobServiceTypes attribute: the jobServiceTypes attribute:
other 0x1 other 0x1
The job contains some document production instructions that The job contains some document production instructions that are
are not one of the identified types. not one of the identified types.
unknown 0x2 unknown 0x2
The job contains some document production instructions The job contains some document production instructions whose
whose type is unknown to the agent. type is unknown to the agent.
print 0x4 print 0x4
The job contains some document production instructions that The job contains some document production instructions that
specify printing specify printing
scan 0x8 scan 0x8
The job contains some document production instructions that The job contains some document production instructions that
specify scanning specify scanning
faxIn 0x10 faxIn 0x10
The job contains some document production instructions that The job contains some document production instructions that
specify receive fax specify receive fax
Job Monitoring MIB, V0.82 June 9, 1997
faxOut 0x20 faxOut 0x20
The job contains some document production instructions that The job contains some document production instructions that
specify sending fax specify sending fax
getFile 0x40 getFile 0x40
The job contains some document production instructions that The job contains some document production instructions that
specify accessing files or documents specify accessing files or documents
putFile 0x80 putFile 0x80
The job contains some document production instructions that The job contains some document production instructions that
specify storing files or documents specify storing files or documents
mailList 0x100 mailList 0x100
The job contains some document production instructions that The job contains some document production instructions that
specify distribution of documents using an electronic mail specify distribution of documents using an electronic mail
system. system.
These bit definitions are the equivalent of a type 2 enum except These bit definitions are the equivalent of a type 2 enum except
that combinations of them may be used together. See section that combinations of them MAY be used together. See section 7.1.2
7.1.2 on page 17." on page 22."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.81 April 24, 1997
JmJobStateReasons1TC ::= TEXTUAL-CONVENTION JmJobStateReasons1TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons1 "This textual-convention is used with the jmJobStateReasons1
attribute to provides additional information regarding the object to provides additional information regarding the
jmJobState/jobState object/attribute. The jobStateReasons1 jmJobState object values.
attributes identifies the reason or reasons that the job is in
the held, pending, processing, printing, needsAttention,
canceled, or completed state. The server shall indicate the
particular reason(s) by setting the value of the
jobStateReasons1 attribute. While the job states cannot be
added to without impacting deployed clients, it is the intent
that additional JmJobStateReasons1TC enums can be defined
without impacting deployed clients. In other words, the
JmJobStateReasons1TC is intended to be extensible.
When the job does not have any reasons for being in its current The following standard values are defined (in hexadecimal) as
state, the server shall set the value of the jobStateReasons1 powers of two, since multiple values MAY be used at the same
attribute to zeros. time.
Companion job state reasons TCs: JmJobStateReasons2TC, NOTE - The Job Monitoring MIB contains a superset of the IPP
JmJobStateReasons3TC, JmJobStateReasons4TC, are defined/reserved values[3] for the IPP 'job-state-reasons' attribute, since the
for additional 31*3 = 93 job state reasons. This is a type 2 Job Monitoring MIB is intended to cover other job submission
bit definition. See section 7.1.2 on page 17. protocols as well. Also some of the names of the reasons have
been changed from 'printer' to 'device', since the Job
Job Monitoring MIB, V0.82 June 9, 1997
The following standard values are defined (in hexadecimal) as Monitoring MIB is intended to cover additional types of devices,
powers of two, since multiple values may be used at the same including input devices, such as scanners.
time:
NOTE - For easy of understanding the order of the reasons is
presented in the order in which the reason is most likely to
occur.
other 0x1 other 0x1
The job state reason is not one of the standardized or The job state reason is not one of the standardized or
registered reasons. registered reasons.
unknown 0x2 unknown 0x2
The job state reason is not known to the agent. The job state reason is not known to the agent or is
indeterminent.
documentsNeeded 0x4 jobIncoming 0x4
The job is in the held state because the server or device is The job has been accepted by the server or device, but the
waiting for the job's files to start and/or finish being server or device is expected (1) additional operations to finish
transferred before the job can be scheduled to be processed. creating the job and/or (2) is accessing/accepting document
data.
jobHoldSet 0x8 jobOutgoing 0x8
The job is in the held state because the client specified Configuration 2 only: The server is transmitting the job to the
that the job is to be held. device.
jobProcessAfterSpecified 0x10 jobHoldSpecified 0x10
The job is in the held state because the client specified a The value of the job's jobHold(52) attribute (see page 47) is
time specification reflected in the value of the job's TRUE, either set when the job was created or subsequently by an
jobProcessAfterDateAndTime attribute that has not yet explicit modify job operation. The job SHALL NOT be a candidate
occurred. for processing until this reason is removed and there are no
other reasons to hold the job.
requiredResourcesNotReady 0x20 jobHoldUntilSpecified 0x20
Job Monitoring MIB, V0.81 April 24, 1997 The value of the job's jobHoldUntil(53) (see page 47) attribute
specifies a time period that is still in the future, either set
when the job was created or subsequently by an explicit modify
job operation. The job SHALL NOT be a candidate for processing
until this reason is removed and there are no other reasons to
hold the job.
The job is in the held state because at least one of the jobProcessAfterSpecified 0x40
resources needed by the job, such as media, fonts, resource The value of the job's jobProcessAfterDateAndTime(51) (see page
objects, etc., is not ready on any of the physical devices 46) attribute specifies a time that is still in the future,
for which the job is a candidate. either set when the job was created or subsequently by an
explicit modify job operation. The job SHALL NOT be a candidate
for processing until this reason is removed and there are no
other reasons to hold the job.
successfulCompletion 0x40 Job Monitoring MIB, V0.82 June 9, 1997
The job is in the completed state having completed
successfully.
completedWithWarnings 0x80 resourcesAreNotReady 0x80
The job is in the canceled or completed states having At least one of the resources needed by the job, such as media,
completed with warnings. fonts, resource objects, etc., is not ready on any of the
physical devices for which the job is a candidate. This
condition MAY be detected when the job is accepted, or
subsequently while the job is pending or processing, depending
on implementation.
completedWithErrors 0x100 deviceStoppedPartly 0x100
The job is in the canceled or completed states having One or more, but not all, of the devices to which the job is
completed with errors (and possibly warnings too). assigned are stopped. If all of the devices are stopped (or the
only device is stopped), the deviceStopped reason SHALL be used.
canceledByUser 0x200 deviceStopped 0x200
The job is in the canceled, state having been canceled by The device(s) to which the job is assigned is (are all) stopped.
the user.
canceledByOperator 0x400 jobPrinting 0x400
The job is in the canceled state having been canceled by the The output device is marking media. This attribute is useful for
operator. servers and output devices which spend a great deal of time
processing when no marking is happening and then want to show
that marking is now happening.
abortedBySystem 0x800 jobCanceledByUser 0x800
The job is in the canceled, state having been aborted by the The job was canceled by the user, i.e., by a user whose name is
system. the same as the value of the job's jobOwner attribute.
logfilePending 0x1000 jobCanceledByOperator 0x1000
The job's logfile is pending file transfer. The job was canceled by the operator, i.e., by a user whose name
is different than the value of the job's jobOwner attribute.
logfileTransferring 0x2000 abortedBySystem 0x2000
The job is in the canceled or completed states and the job's The job was aborted by the system. NOTE - this reason is needed
logfile is being transferred. only when the job is not placed in the aborted job state.
jobCompletedSuccessfully 0x4000
The job completed successfully.
The following additional job state reasons have been added to jobCompletedWithWarnings 0x8000
specify sub-states of the held or completed states that may be The job completed with warnings.
used to represent states that are in ISO DPA[2]:
jobPreProcessing 0x4000 jobCompletedWithErrors 0x10000
The job has been created on the server or device but the The job completed with errors (and possibly warnings too).
submitting client is in the process of adding additional job
components and no documents have started processing. The
job maybe in the process of being checked by the
server/device for attributes, defaults being applied, a
device being selected, etc.
jobPaused 0x8000 The following additional job state reasons have been added to
The job has been indefinitely suspended by a client issuing represent job states that are in ISO DPA[2] and other job submission
an operation to suspend the job so that other jobs may protocols:
proceed using the same devices. The client may issue an
operation to resume the paused job at any time, in which
case the server or device places the job in the held or
Job Monitoring MIB, V0.81 April 24, 1997
pending states and the job is eventually resumed at the jobPaused 0x20000
point where the job was paused. The job has been indefinitely suspended by a client issuing an
Job Monitoring MIB, V0.82 June 9, 1997
jobInterrupted 0x10000 operation to suspend the job so that other jobs may proceed
using the same devices. The client MAY issue an operation to
resume the paused job at any time, in which case the agent SHALL
remove the jobPaused values from the job's jmJobStateReasons1
object and the job is eventually resumed at or near the point
where the job was paused.
jobInterrupted 0x40000
The job has been interrupted while processing by a client The job has been interrupted while processing by a client
issuing an operation that specifies another job to be run issuing an operation that specifies another job to be run
instead of the current job. The server or device will instead of the current job. The server or device will
automatically resume the interrupted job when the automatically resume the interrupted job when the interrupting
interrupting job completes. job completes.
jobRetained 0x20000
The job is being retained by the server or device after
processing and all of the media have been successfully
stacked in the output bin(s).
The job (1) has completed successfully or with warnings or
errors, (2) has been aborted while printing by the
server/device, or (3) has been canceled by the submitting
user or operator before or during processing. The job's
jobStateReasons1 attribute shall contain the reasons that
the job has entered the completed state.
While the jobRetained state reason is , all of the job's
document data (and submitted resources, such as fonts,
logos, and forms, if any) are retained by the server or
device; thus a client could issue an operation to resubmit
the job (or a copy of the job).
The following job state reasons have been added to align with
the Internet Printing Protocol (IPP):
jobHoldUntil 0x40000 jobRetained 0x80000
The jobHoldUntil(33) attribute was specified for a named The job is being retained by the server or device with all of
time period that is still in the future. The job remains in the job's document data (and submitted resources, such as fonts,
the held state until the time period arrives and there are logos, and forms, if any). Thus a client could issue an
no other reasons to hold the job. operation to resubmit the job (or a copy of the job). When a
client could no longer resubmit the job, such as after the
document data has been discarded, the agent SHALL remove the
jobRetained value from the jmJobStateReasons1 object.
These bit definitions are the equivalent of a type 2 enum except These bit definitions are the equivalent of a type 2 enum except
that combinations of them may be used together. See section that combinations of bits may be used together. See section 7.1.2
7.1.2 on page 17." on page 22. The remaining bits are reserved for future
standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons2TC ::= TEXTUAL-CONVENTION JmJobStateReasons2TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons2 "This textual-convention is used with the jobStateReasons2
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState/jobState object/attribute. See the description under jmJobState object. See the description under
JmJobStateReasons1TC on page 45. JmJobStateReasons1TC on page 59.
Job Monitoring MIB, V0.81 April 24, 1997
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
Job Monitoring MIB, V0.82 June 9, 1997
cascaded 0x1 cascaded 0x1
After the outbound gateway retrieves all job and document An outbound gateway has transmitted all of the job's job and
attributes and data, it stores the information into a spool document attributes and data to another spooling system.
directory. Once it has done this, it sends the supervisor a
job-processing event with this job-state-reason which tells
the supervisor to transition to a new job state.
deletedByAdministrator 0x2 deletedByAdministrator 0x2
The administrator has issued a Delete operation on the job The administrator has deleted the job.
or a Clean operation on the server or queue containing the
job; therefore the job may have been canceled before or
during processing, and will have no retention-period or
completion-period.
discardTimeArrived 0x4 discardTimeArrived 0x4
The job has been deleted (canceled with the job-retention- The job has been deleted due to the fact that the time specified
period set to 0) due to the fact that the time specified by by the job's job-discard-time has arrived.
the job's job-discard-time has arrived [if the job had
already completed, the only action that would have occurred
is that the job-retention-period would be set to 0 and the
job is deleted].
postProcessingFailed 0x8 postProcessingFailed 0x8
The post-processing agent failed while trying to log The post-processing agent failed while trying to log accounting
accounting attributes for the job; therefore the job has attributes for the job; therefore the job has been placed into
been placed into completed state with the retained the completed state with the jobRetained jmJobStateReasons1
jobStateReasons1 attribute value for a system-defined period object value for a system-defined period of time, so the
of time, so the administrator can examine it, resubmit it, administrator can examine it, resubmit it, etc.
etc. The post-processing agent is a plug-and-play mechanism
which the system and the customer uses to add functionality
that is executed after a job has finished processing.
submissionInterrupted 0x10 submissionInterrupted 0x10
Indicates that the job was not completely submitted for the Indicates that the job was not completely submitted for the
following reasons: (1) the server has crashed before the job following reasons: (1) the server has crashed before the job was
was closed by the client. The server shall put the job into closed by the client, (2) the server or the document transfer
the completed state (and shall not print the job). (2) the method has crashed in some non-recoverable way before the
server or the document transfer method has crashed in some document data was entirely transferred to the server, (3) the
non-recoverable way before the document data was entirely client crashed or failed to close the job before the time-out
transferred to the server. The server shall put the job period. Whether the server or device puts the job into the
into the completed state (and shall not print the job). (3) pendingHeld or aborted state depends on implementation.
the client crashed or failed to close the job before the
time-out period. The server shall close the job and put the
job into the held state with job-state-reasons of
submission-interrupted and job-hold-set and with the job's
job-hold attribute set to TRUE. The user may release the
job for scheduling by issuing a job submission or management
protocol operation.
maxJobFaultCountExceeded 0x20 maxJobFaultCountExceeded 0x20
The job has been faulted and returned by the server several The job has faulted several times and has exceeded the
Job Monitoring MIB, V0.81 April 24, 1997 administratively defined fault count limit.
times and that the job-fault-count exceeded the device's (or
server's, if not defined for the device) cfg-max-job-fault-
count. The job is automatically put into the held state
regardless of the hold-jobs-interrupted-by-device-failure
attribute. This job-state-reasons value is used in
conjunction with the job-interrupted-by-device-failure
value.
devicesNeedAttentionTimeOut 0x40 devicesNeedAttentionTimeOut 0x40
One or more document transforms that the job is using needs One or more document transforms that the job is using needs
human intervention in order for the job to make progress, human intervention in order for the job to make progress, but
but the human intervention did not occur within the site- the human intervention did not occur within the site-settable
settable time-out value and the server/device has time-out value.
transitioned the job to the held state.
needsKeyOperatorTimeOut 0x80 needsKeyOperatorTimeOut 0x80
One or more devices or document transforms that the job is One or more devices or document transforms that the job is using
using need a specially trained operator (who may need a key need a specially trained operator (who may need a key to unlock
to unlock the device and gain access) in order for the job the device and gain access) in order for the job to make
to make progress, but the key operator intervention did not progress, but the key operator intervention did not occur within
occur within the site-settable time-out value and the the site-settable time-out value.
server/device has transitioned the job to the held state.
jobStartWaitTimeOut 0x100 jobStartWaitTimeOut 0x100
The server/device has stopped the job at the beginning of The server/device has stopped the job at the beginning of
processing to await human action, such as installing a processing to await human action, such as installing a special
special cartridge or special non-standard media, but the job Job Monitoring MIB, V0.82 June 9, 1997
was not resumed within the site-settable time-out value and
the server/device has transitioned the job to the held cartridge or special non-standard media, but the job was not
state. Normally, the job is resumed by means outside the resumed within the site-settable time-out value and the
job submission protocol, such as some local function on the server/device has transitioned the job to the pendingHeld state.
device. Normally, the job is resumed by means outside the job submission
protocol, such as some local function on the device.
jobEndWaitTimeOut 0x200 jobEndWaitTimeOut 0x200
The server/device has stopped the job at the end of The server/device has stopped the job at the end of processing
processing/printing to await human action, such as removing to await human action, such as removing a special cartridge or
a special cartridge or restoring standard media, but the job restoring standard media, but the job was not resumed within the
was not resumed within the site-settable time-out value and site-settable time-out value and the server/device has
the server/device has transitioned the job to the completed transitioned the job to the completed state. Normally, the job
state. Normally, the job is resumed by means outside the is resumed by means outside the job submission protocol, such as
job submission protocol, such as some local function on the some local function on the device, whereupon the job SHALL
device, whereupon the job shall transition immediately to transition immediately to the completed state.
the canceled state.
jobPasswordWaitTimeOut 0x400 jobPasswordWaitTimeOut 0x400
The server/device has stopped the job at the beginning of The server/device has stopped the job at the beginning of
processing to await input of the job's password, but the processing to await input of the job's password, but the human
human intervention did not occur within the site-settable intervention did not occur within the site-settable time-out
time-out value and the server/device has transitioned the value.
job to the held state. Normally, the password is input and
the job is resumed by means outside the job submission
protocol, such as some local function on the device.
deviceTimedOut 0x800 deviceTimedOut 0x800
A device that the job was using has not responded in a A device that the job was using has not responded in a period
Job Monitoring MIB, V0.81 April 24, 1997 specified by the device's site-settable attribute.
period specified by the device's site-settable attribute.
connectingToDeviceTimeOut 0x1000 connectingToDeviceTimeOut 0x1000
The server is attempting to connect to one or more devices The server is attempting to connect to one or more devices which
which may be dial-up, polled, or queued, and so may be busy may be dial-up, polled, or queued, and so may be busy with
with traffic from other systems, but server was unable to traffic from other systems, but server was unable to connect to
connect to the device within the site-settable time-out the device within the site-settable time-out value.
value and the server has transitioned the job to the held
state.
transferring 0x2000 transferring 0x2000
The job is being transferred to a down stream server or The job is being transferred to a down stream server or device.
device.
queuedInDevice 0x4000 queuedInDevice 0x4000
The job has been queued in a down stream server or device. The job has been queued in a down stream server or device.
jobCleanup 0x8000 jobCleanup 0x8000
The server/device is performing cleanup activity as part of The server/device is performing cleanup activity as part of
ending normal processing. ending normal processing.
processingToStopPoint 0x10000 processingToStopPoint 0x10000
The requester has issued an operation to interrupt the job The requester has issued an operation to interrupt the job and
and the server/device is processing up until the specified the server/device is processing up until the specified stop
stop point occurs. point occurs.
Job Monitoring MIB, V0.82 June 9, 1997
jobPasswordWait 0x20000 jobPasswordWait 0x20000
The server/device has selected the job to be next to The server/device has selected the job to be next to process,
process, but instead of assigning resources and started the but instead of assigning resources and started the job
job processing, the server/device has transitioned the job processing, the server/device has transitioned the job to the
to the held state to await entry of a password (and pendingHeld state to await entry of a password (and dispatched
dispatched another job, if there is one). The user resumes another job, if there is one).
the job either locally or by issuing a remote operation and
supplying a job-password=secret-code input parameter that
must match the job's job-password attribute.
validating 0x40000 validating 0x40000
The server/device is validating the job after accepting the The server/device is validating the job after accepting the job.
job. The job state may be held, pending, or processing.
queueHeld 0x80000 queueHeld 0x80000
The operator has held the entire queue by means outside the The operator has held the entire job set or queue.
scope of the Job model.
jobProofWait 0x100000 jobProofWait 0x100000
The job has produced a single proof copy and is in the held The job has produced a single proof copy and is in the
state waiting for the requester to issue an operation to pendingHeld state waiting for the requester to issue an
release the job to print normally, obeying the job-copies operation to release the job to print normally, obeying any job
and copy-count job and document attributes that were and document copy attributes that were originally submitted.
originally submitted.
heldForDiagnostics 0x200000 heldForDiagnostics 0x200000
The system is running intrusive diagnostics, so the all jobs The system is running intrusive diagnostics, so that all jobs
are being held. are being held.
Job Monitoring MIB, V0.81 April 24, 1997
serviceOffLine 0x400000 serviceOffLine 0x400000
The service/document transform is off-line and accepting no The service/document transform is off-line and accepting no
jobs. All pending jobs are put into the held state. This jobs. All pending jobs are put into the pendingHeld state.
could be true if its input is impaired or broken. This could be true if its input is impaired or broken.
noSpaceOnServer 0x800000 noSpaceOnServer 0x800000
The job is held because there is no room on the server to There is no room on the server to store all of the job. For
store all of the job. For example, there is no room for the example, there is no room for the document data.
document data or a scan-to-file job.
pinRequired 0x1000000 pinRequired 0x1000000
The System Administrator settable device policy is (1) to The System Administrator settable device policy is (1) to
require PINs, and (2) to hold jobs that do not have a pin require PINs, and (2) to hold jobs that do not have a pin
supplied as an input parameter when the job was created. The supplied as an input parameter when the job was created. The
requester shall either (1) enter a pin locally at the device requester SHALL either (1) enter a pin locally at the device or
or issue a remote operation supplying the PIN in order for issue a remote operation supplying the PIN in order for the job
the job to be able to proceed. to be able to proceed.
exceededAccountLimit 0x2000000 exceededAccountLimit 0x2000000
The account for which this job is drawn has exceeded its The account for which this job is drawn has exceeded its limit.
limit. This condition should be detected before the job is This condition SHOULD be detected before the job is scheduled so
scheduled so that the user does not wait until his/her job that the user does not wait until his/her job is scheduled only
is scheduled only to find that the account is overdrawn. to find that the account is overdrawn. This condition MAY also
This condition may also occur while the job is processing occur while the job is processing either as processing begins or
either as processing begins or part way through processing. part way through processing.
An overdraft mechanism should be included to be user- Job Monitoring MIB, V0.82 June 9, 1997
friendly, so as to minimize the chances that the job cannot
finish or that media is wasted. For example, the An overdraft mechanism SHOULD be included to be user-friendly,
server/device should finish the current copy for a job with so as to minimize the chances that the job cannot finish or that
collated document copies, rather than stopping in the middle media is wasted. For example, the server/device SHOULD finish
of the current document copy. the current copy for a job with collated document copies, rather
than stopping in the middle of the current document copy.
heldForRetry 0x4000000 heldForRetry 0x4000000
The job encountered some errors that the server/device could The job encountered some errors that the server/device could not
not recover from with its normal retry procedures, but the recover from with its normal retry procedures, but the error is
error is worth trying the job later, such as phone number worth trying the job later, such as phone number busy or remote
busy or remote file system in-accessible. For such a file system in-accessible. For such a situation, the
situation, the server/device shall add the held-for-retry server/device SHALL transition the job from the processing to
value to the job's jobStateReasons2 attribute and transition the pendingHeld, rather than to the aborted state.
the job from the processing to the held, rather than to the
completed state.
The following values are from the X/Open PSIS draft standard: The following values are from the X/Open PSIS draft standard:
canceledByShutdown 0x8000000 canceledByShutdown 0x8000000
The job was canceled because the server or device was The job was canceled because the server or device was shutdown
shutdown before completing the job. The job shall be placed before completing the job. Whether the job is placed in the
in the pending state [if the job was not started, else the pendingHeld or aborted state, depends on implementation.
job shall be placed in the terminating state].
deviceUnavailable 0x10000000 deviceUnavailable 0x10000000
This job was aborted by the system because the device is This job was aborted by the system because the device is
currently unable to accept jobs. This reason [shall be] used currently unable to accept jobs. Whether the job is placed in
Job Monitoring MIB, V0.81 April 24, 1997 the pendingHeld or aborted state, depends on implementation.
in conjunction with the reason aborted-by-system. The job
shall be placed in the pending state.
wrongDevice 0x20000000 wrongDevice 0x20000000
This job was aborted by the system because the device is This job was aborted by the system because the device is unable
unable to handle this particular job; the spooler should try to handle this particular job; the spooler SHOULD try another
another device. This reason [shall be] used in conjunction device or the user should submit the job to another device.
with the reason aborted-by- system. The job shall be Whether the job is placed in the pendingHeld or aborted state,
pending if the queue contains other physical devices that depends on implementation.
the job could print on, and the spooler is capable of not
sending the job back to a physical device that has rejected
the job for this job-state-reasons value. Otherwise, [the
job] shall be placed in the completed state with the
retained value set in the jobStateReasons2 attribute.
badJob 0x40000000 badJob 0x40000000
This job was aborted by the system because this job has a This job was aborted by the system because this job has a major
major problem, such as an ill-formed PDL; the spooler should problem, such as an ill-formed PDL; the spooler SHOULD not even
not even try another device. This reason shall be used in try another device.
conjunction with the reason aborted-by-system. The job shall
be placed in the terminating state.
These bit definitions are the equivalent of a type 2 enum except These bit definitions are the equivalent of a type 2 enum except that
that combinations of them may be used together. See section combinations of them may be used together. See section 7.1.2 on page
7.1.2 on page 17." 22."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.82 June 9, 1997
JmJobStateReasons3TC ::= TEXTUAL-CONVENTION JmJobStateReasons3TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons3 "This textual-convention is used with the jobStateReasons3
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState/jobState object/attribute. See the description under jmJobState object. See the description under
JmJobStateReasons1TC on page 45. JmJobStateReasons1TC on page 59.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
jobInterruptedByDeviceFailure 0x1 jobInterruptedByDeviceFailure 0x1
A device or the print system software that the job was using A device or the print system software that the job was using has
has failed while the job was processing. The device is failed while the job was processing. The server or device is
keeping the job in the held state until an operator can keeping the job in the pendingHeld state until an operator can
determine what to do with the job. determine what to do with the job.
These bit definitions are the equivalent of a type 2 enum except These bit definitions are the equivalent of a type 2 enum except
that combinations of them may be used together. See section that combinations of them may be used together. See section 7.1.2
7.1.2 on page 17." on page 22. The remaining bits are reserved for future
Job Monitoring MIB, V0.81 April 24, 1997 standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons4TC ::= TEXTUAL-CONVENTION JmJobStateReasons4TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used in the jobStateReasons4 "This textual-convention is used in the jobStateReasons4
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState/jobState object/attribute. See the description under jmJobState object. See the description under
JmJobStateReasons1TC on page 45. JmJobStateReasons1TC on page 59.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
none yet defined. none yet defined.
These bit definitions are the equivalent of a type 2 enum except These bit definitions are the equivalent of a type 2 enum except
that combinations of them may be used together. See section that combinations of them may be used together. See section
7.1.2 on page 17." Job Monitoring MIB, V0.82 June 9, 1997
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.81 April 24, 1997
Job Monitoring MIB, V0.81 April 24, 1997
Job Monitoring MIB, V0.81 April 24, 1997
7.1.2 on page 22. These bits are reserved for future
standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.82 June 9, 1997
Job Monitoring MIB, V0.81 April 24, 1997 jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 }
-- The General Group (Mandatory) -- The General Group (Mandatory)
-- The jmGeneralGroup consists entirely of the jmGeneralTable. -- The jmGeneralGroup consists entirely of the jmGeneralTable.
-- Implementation of every object in this group is MANDATORY.
-- See Section 4 entitled 'Conformance Considerations' on page 18.
jmGeneral OBJECT IDENTIFIER ::= { jobmonMIB 5 } jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 }
jmGeneralTable OBJECT-TYPE jmGeneralTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmGeneralEntry SYNTAX SEQUENCE OF JmGeneralEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmGeneralTable consists of information of a general nature "The jmGeneralTable consists of information of a general nature
that are per-job-set, but are not per-job. See Terminology and that are per-job-set, but are not per-job. See Terminology and
Job Model on page 8 for the definition of a job set." Job Model on page 12 for the definition of a job set."
::= { jmGeneral 1 } ::= { jmGeneral 1 }
jmGeneralEntry OBJECT-TYPE jmGeneralEntry OBJECT-TYPE
SYNTAX JmGeneralEntry SYNTAX JmGeneralEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a job set (queue). "Information about a job set (queue).
An entry shall exist in this table for each job set." An entry SHALL exist in this table for each job set."
INDEX { jmJobSetIndex } INDEX { jmJobSetIndex }
::= { jmGeneralTable 1 } ::= { jmGeneralTable 1 }
JmGeneralEntry ::= SEQUENCE { JmGeneralEntry ::= SEQUENCE {
jmGeneralNumberOfActiveJobs Integer32(0..2147483647), jmGeneralNumberOfActiveJobs Integer32(0..2147483647),
jmGeneralOldestActiveJobIndex Integer32(0..2147483647), jmGeneralOldestActiveJobIndex Integer32(0..2147483647),
jmGeneralNewestActiveJobIndex Integer32(0..2147483647), jmGeneralNewestActiveJobIndex Integer32(0..2147483647),
jmGeneralJobPersistence Integer32(0..2147483647), jmGeneralJobPersistence Integer32(0..2147483647),
jmGeneralAttributePersistence Integer32(0..2147483647), jmGeneralAttributePersistence Integer32(0..2147483647),
jmGeneralJobSetName OCTET STRING(SIZE(0..63)) jmGeneralJobSetName OCTET STRING(SIZE(0..63))
} }
jmGeneralNumberOfActiveJobs OBJECT-TYPE jmGeneralNumberOfActiveJobs OBJECT-TYPE
SYNTAX Integer32(0..2147483647) SYNTAX Integer32(0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of active jobs in the jmJobIDTable, Job Monitoring MIB, V0.82 June 9, 1997
jmJobStateTable, and jmAttributeTable, i.e., the total number of
jobs that are in neither the completed nor the canceled states.
See JmJobStateTC on page 24 for the exact specification of the
semantics of the job states.
If there are no active jobs, the value of this object shall be "The current number of 'active' jobs in the jmJobIDTable,
jmJobTable, and jmAttributeTable, i.e., the total number of jobs
that are in the pending, processing, or processingStopped
states. See JmJobStateTC on page 32 for the exact specification
of the semantics of the job states.
If there are no active jobs, the value of this object SHALL be
0." 0."
::= { jmGeneralEntry 1 } ::= { jmGeneralEntry 1 }
Job Monitoring MIB, V0.81 April 24, 1997
jmGeneralOldestActiveJobIndex OBJECT-TYPE jmGeneralOldestActiveJobIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIndex of the oldest active job, i.e., the job in the "The jmJobIndex of the oldest job that is still in one of the
jmJobStateTable and jmAttributeTable that has been there the 'active' states (pending, processing, or processingStopped). In
longest and has neither completed nor been canceled. other words, the index of the 'active' job that has been in the
job tables the longest.
When a job completes or is canceled with a jmJobIndex value that When a job transitions from one of the 'active' states (pending,
matches this object, the agent shall advance the value to the processing, processingStopped) to one of the 'in-active' states
next oldest active job, if any. (pendingHeld, completed, canceled, or aborted), with a
jmJobIndex value that matches this object, the agent SHALL
advance (or wrap - see jmGeneralNewestActiveJobIndex) the value
to the next oldest 'active' job, if any.
If there are no active jobs, the agent shall the value of this On the other hand, when a job transitions from one of the 'in-
object to 0." active' states to one of the 'active' state, the agent SHALL
reduce (or wrap) the value of this object, if the job's
jmJobIndex is smaller than the current value.
If there are no active jobs, the agent SHALL set the value of
this object to 0."
::= { jmGeneralEntry 2 } ::= { jmGeneralEntry 2 }
jmGeneralNewestActiveJobIndex OBJECT-TYPE jmGeneralNewestActiveJobIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIndex of the newest active job, i.e., the job in the "The jmJobIndex of the newest job that is in one of the 'active'
jmJobStateTable and jmAttributeTable that has been added most states (pending, processing, or processingStopped). In other
recently and has neither completed nor been canceled. words, the index of the 'active' job that has been most recently
added to the job tables.
When a new job is accepted by the server or device that the When a new job is accepted by the server or device that the
agent is instrumenting, the agent shall increment this object by agent is instrumenting, the agent SHALL assign the next
1 and store the job attributes in the row specified by the Job Monitoring MIB, V0.82 June 9, 1997
incremented value. If the value would exceed the
implementation-defined maximum value for jmJobIndex, the agent available value to the job's jmJobIndex that is used for storing
shall set the value back to 1, i.e., wrap around to the job information in the jmJobIDTable, the jmJobTable, and the
beginning of the job tables. jmAttributeTable. If the value would exceed the implementation-
defined maximum value for jmJobIndex, the agent SHALL set the
value back to 1, i.e., wrap around to the beginning of the job
tables.
It is recommended that the largest value for jmJobIndex be much It is recommended that the largest value for jmJobIndex be much
larger than the maximum number of jobs that the implementation larger than the maximum number of jobs that the implementation
can contain at a single time, so as to minimize the pre-mature can contain at a single time, so as to minimize the pre-mature
re-use of jmJobIndex value for a newer job while clients retain re-use of jmJobIndex value for a newer job while clients retain
the same 'stale' value for an older job. the same 'stale' value for an older job.
When all jobs become inactive, i.e., enter the completed or Each time a new job is accepted by the server or device that the
canceled state, the agent shall leave the value of this object agent is instrumenting AND that job is to be 'active' (pending,
unchanged. processing, or processingStopped, but not pendingHeld), the
agent SHALL copy the value of the job's jmJobIndex to the
jmGeneralNewestActiveJobIndex object. If the new job is 'in-
active' (pendingHeld state), the agent SHALL not change the
value of jmGeneralNewestActiveJobIndex object.
When the server or device is power-cycled, the value of this When all jobs become 'inactive', i.e., enter the pendingHeld,
object shall be persistent, so that new jobs are not assigned completed, canceled, or aborted states, the agent SHALL set the
the same jmJobIndex as recent jobs before the power cycle. value of this object to 0. Whenever a job changes from 'in-
Therefore, the agent shall return the value 0 only on the first active' to 'active' (from pendingHeld to pending or processing),
power-up of the server or device. the agent SHALL update the value of either the
jmGeneralOldestActiveJobIndex or the
jmGeneralNewestActiveJobIndex objects, or both, if the job's
jmJobIndex value is outside the range between
jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex.
When the server or device is power-cycled, the agent SHALL
remember the next jmJobIndex value to be assigned, so that new
jobs are not assigned the same jmJobIndex as recent jobs before
the power cycle.
NOTE - Applications that wish to efficiently access all of the NOTE - Applications that wish to efficiently access all of the
active jobs may use jmGeneralOldestActiveJobIndex value to start active jobs MAY use jmGeneralOldestActiveJobIndex value to start
with the oldest active job and continue until they reach the with the oldest active job and continue until they reach the
index value equal to jmGeneralNewestActiveJobIndex, skipping index value equal to jmGeneralNewestActiveJobIndex, skipping
over any completed or canceled jobs that might intervene. If an over any pendingHeld, completed, canceled, or aborted jobs that
Job Monitoring MIB, V0.81 April 24, 1997 might intervene.
application detects that the jmGeneralNewestActiveJobIndex is If an application detects that the jmGeneralNewestActiveJobIndex
smaller than jmGeneralOldestActiveJobIndex, the job index has is smaller than jmGeneralOldestActiveJobIndex, the job index has
wrapped. In this case, when the application exceeds the maximum wrapped. In this case, when the application exceeds the maximum
job index (detected by a no such object status returned from a job index (detected by a no such object status returned from a
GetNext operation for the next conceptual row), the application GetNext operation for the next conceptual row), the application
shall start over at 1 and continue the GetNext operations to Job Monitoring MIB, V0.82 June 9, 1997
SHALL start over at 1 and continue the GetNext operations to
find the rest of the active jobs." find the rest of the active jobs."
::= { jmGeneralEntry 3 } ::= { jmGeneralEntry 3 }
jmGeneralJobPersistence OBJECT-TYPE jmGeneralJobPersistence OBJECT-TYPE
SYNTAX Integer32(0..2147483647) SYNTAX Integer32(0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum time in seconds that an entry will remain in the "The minimum time in seconds for this instance of the Job Set
jmJobIDTable and jmJobStateTable after processing/printing has that an entry will remain in the jmJobIDTable and jmJobTable
completed for this instance of the Job Set, i.e., the time in after processing has completed, i.e., the minimum time in
seconds starting when the job enters the completed or canceled seconds starting when the job enters the completed, canceled, or
state. Depending on implementation, the value of this object aborted state. Depending on implementation, the value of this
may be either: (1) set by the system administrator by means object MAY be either: (1) set by the system administrator by
outside this specification or (2)fixed by the implementation." means outside this specification or (2) fixed by the
implementation."
::= { jmGeneralEntry 4 } ::= { jmGeneralEntry 4 }
jmGeneralAttributePersistence OBJECT-TYPE jmGeneralAttributePersistence OBJECT-TYPE
SYNTAX Integer32(0..2147483647) SYNTAX Integer32(0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum time in seconds that an entry will remain in the "The minimum time in seconds for this instance of the Job Set
jmAttributeTable after processing/printing has completed for that an entry will remain in the jmAttributeTable after
this instance of the Job Set, i.e., the time in seconds starting processing has completed , i.e., the time in seconds starting
when the job enters the completed or canceled state. The value when the job enters the completed, canceled, or aborted state.
of this object may be either (1) set by the system administrator The value of this object MAY be either (1) set by the system
by means outside this specification or may be (2) fixed by the administrator by means outside this specification or MAY be (2)
implementation, depending on implementation. fixed by the implementation, depending on implementation.
This value shall be equal to or less than the value of This value SHALL be equal to or less than the value of
jmGeneralJobPersistence. Attributes that are shared between the jmGeneralJobPersistence."
jmJobIDTable/jmJobStateTable and the jmAttributeTable shall be
governed by the larger value in all tables."
::= { jmGeneralEntry 5 } ::= { jmGeneralEntry 5 }
jmGeneralJobSetName OBJECT-TYPE jmGeneralJobSetName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..63)) SYNTAX OCTET STRING(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The human readable administratively assigned name of this job "The human readable administratively assigned name of this job
set (by means outside of this MIB). Typically, this name will set (by means outside of this MIB). Typically, this name will
be the name of the job queue. If a server or device has only a be the name of the job queue. If a server or device has only a
single job set, this object can be the administratively assigned single job set, this object can be the administratively assigned
name of the server or device itself. This name does not need to name of the server or device itself. This name does not need to
be unique, though each job set in a single Job Monitoring MIB be unique, though each job set in a single Job Monitoring MIB
should have distinct names. SHOULD have distinct names.
Job Monitoring MIB, V0.81 April 24, 1997 Job Monitoring MIB, V0.82 June 9, 1997
NOTE - The purpose of this object is to help the user of the job NOTE - The purpose of this object is to help the user of the job
monitoring application distinguish between several job sets in monitoring application distinguish between several job sets in
implementations that support more than one job set." implementations that support more than one job set."
::= { jmGeneralEntry 6 } ::= { jmGeneralEntry 6 }
-- The Job ID Group (Mandatory) -- The Job ID Group (Mandatory)
-- The jmJobIDGroup consists entirely of the jmJobIDTable. -- The jmJobIDGroup consists entirely of the jmJobIDTable.
-- --
-- The two key indexes that are used in other tables to index jobs: -- The two key indexes that are used in other tables to index jobs:
-- jmJobSetIndex and jmJobIndex are materialized in this group. -- jmJobSetIndex and jmJobIndex are materialized in this group.
-- --
-- Implementation of every object in this group is MANDATORY.
-- See Section 4 entitled 'Conformance Considerations' on page 18.
jmJobID OBJECT IDENTIFIER ::= { jobmonMIB 6 } jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 }
jmJobIDTable OBJECT-TYPE jmJobIDTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmJobIDEntry SYNTAX SEQUENCE OF JmJobIDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIDTable provides a correspondence map (1) between the "The jmJobIDTable provides a correspondence map (1) between the
job submission ID that a client uses to refer to a job and (2) job submission ID that a client uses to refer to a job and (2)
the jmJobSetIndex and jmJobIndex that the Job Monitoring MIB the jmJobSetIndex and jmJobIndex that the Job Monitoring MIB
agent assigned to the job and that are used to access the job in agent assigned to the job and that are used to access the job in
all of the other tables in the MIB. If a monitoring application all of the other tables in the MIB. If a monitoring application
already knows the jmJobIndex of the job it is querying, that already knows the jmJobIndex of the job it is querying, that
application need not use the jmJobIDTable." application NEED NOT use the jmJobIDTable."
::= { jmJobID 1 } ::= { jmJobID 1 }
jmJobIDEntry OBJECT-TYPE jmJobIDEntry OBJECT-TYPE
SYNTAX JmJobIDEntry SYNTAX JmJobIDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The map from (1) the jmJobSubmissionIDIndex to (2) the "The map from (1) the jmJobSubmissionID to (2) the jmJobSetIndex
jmJobSetIndex and jmJobIndex. and jmJobIndex.
An entry shall exist in this table for each job, no matter what An entry SHALL exist in this table for each job, no matter what
the state of the job and no matter what job set the job is in. the state of the job and no matter what job set the job is in.
Each job shall appear in one and only one job set." Each job SHALL appear in one and only one job set.
INDEX { jmJobSubmissionIDIndex }
Job Monitoring MIB, V0.82 June 9, 1997
NOTE - an IMPLICIT statement is NOT provided in the following
INDEX clause, since it was not an SMIv1 feature. Therefore, the
extra ASN.1 tag SHALL be included in the varbind in the SNMP
request and the response."
INDEX { jmJobSubmissionID }
::= { jmJobIDTable 1 } ::= { jmJobIDTable 1 }
JmJobIDEntry ::= SEQUENCE { JmJobIDEntry ::= SEQUENCE {
jmJobSubmissionIDIndex OCTET STRING(SIZE(0..32)), jmJobSubmissionID OCTET STRING(SIZE(1..32)),
jmJobSetIndex Integer32(1..32767), jmJobSetIndex Integer32(1..32767),
jmJobIndex Integer32(1..2147483647) jmJobIndex Integer32(1..2147483647)
} }
Job Monitoring MIB, V0.81 April 24, 1997
jmJobSubmissionIDIndex OBJECT-TYPE jmJobSubmissionID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..32)) SYNTAX OCTET STRING(SIZE(1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A quasi-unique 32-octet string ID which identifies the job "A quasi-unique 32-octet string ID which identifies the job
uniquely within a particular client-server environment. Either uniquely within a particular client-server environment. Either
the client or the server assigns the job submission ID for each the client or the server assigns the job submission ID for each
job. The monitoring application whether in the client or job. The monitoring application whether in the client or
running separately, uses the job submission ID to help the user running separately, uses the job submission ID to help the user
identify which jmJobIndex was assigned by the agent. identify which jmJobIndex was assigned by the agent.
There are multiple formats for the jmJobSubmissionIDIndex. Each There are multiple formats for the jmJobSubmissionID. Each
format shall be registered using the procedures of a type 2 format SHALL be registered using the procedures of a type 2
enum. See section entitled: 'IANA Registration of enums' on enum. See section entitled: 'IANA Registration of enums' on
page 17. page 22.
The value of jmJobSubmissionIDIndex should be one of the The value of jmJobSubmissionID SHOULD be one of the registered
registered format types. The first two octets of the string format types. The first octet of the string SHALL indicate
shall indicate which registered format is being used. The agent which registered format is being used. The ASCII characters '0-
shall assign a string of registered format (00) for any job 9', 'A-Z', and 'a-z' will be assigned in order giving 62
without a Job Submission ID. The format values registered so possible formats. The agent SHALL assign a string of registered
far are: format (0) for any job without a Job Submission ID.
The format values registered so far are:
Format Format
Number Description Number Description
------ ------------ ------ ------------
00 Set by the agent when neither the client nor the 0 Set by the agent when neither the client nor the
server assigned a job submission ID. server assigned a job submission ID.
01 octets 3-10: 8-decimal-digit random number 1 octets 3-10: 8-decimal-digit random number
octets 11-32: last 22 bytes of the jobName attribute octets 11-32: last 22 bytes of the jobName attribute
Job Monitoring MIB, V0.82 June 9, 1997
02 octets 3-10: 8-decimal-digit sequential number 2 octets 3-10: 8-decimal-digit sequential number
octets 11-32: Client MAC address octets 11-32: Client MAC address
03 octets 3-10: 8-decimal-digit sequential number 3 octets 3-10: 8-decimal-digit sequential number
octets 11-32: last 22 bytes of the client URL octets 11-32: last 22 bytes of the client URL
.. to be registered according to procedures of a type 2 .. to be registered according to procedures of a type 2
enum. See section 7.3 on page 18. enum. See section 7.3 on page 23.
NOTE - the job submission id is only intended to be unique NOTE - the job submission id is only intended to be unique
between a limited set of clients for a limited duration of time, between a limited set of clients for a limited duration of time,
namely, for the life time of the job in the context of the namely, for the life time of the job in the context of the
server or device that is processing the job. Some of the server or device that is processing the job. Some of the
formats include something that is unique per client and a random formats include something that is unique per client and a random
number so that the same job submitted by the same client will number so that the same job submitted by the same client will
have a different job submission id. For other formats, where have a different job submission id. For other formats, where
part of the id is guaranteed to be unique for each client, such part of the id is guaranteed to be unique for each client, such
as the MAC address or URL, a sequential number should suffice as the MAC address or URL, a sequential number SHOULD suffice
for each client (and may be easier for each client to manage). for each client (and may be easier for each client to manage).
Therefore, the length of the job submission id has been selected Therefore, the length of the job submission id has been selected
to reduce the probability of collision to a very low number, but to reduce the probability of collision to a very low number, but
is not intended to be an absolute guarantee of uniqueness. is not intended to be an absolute guarantee of uniqueness.
Job Monitoring MIB, V0.81 April 24, 1997
None-the-less, collisions could occur, but without bad None-the-less, collisions could occur, but without bad
consequences, since this MIB is intended to be used only for consequences, since this MIB is intended to be used only for
monitoring jobs, not for controlling and managing them." monitoring jobs, not for controlling and managing them."
::= { jmJobIDEntry 1 } ::= { jmJobIDEntry 1 }
jmJobSetIndex OBJECT-TYPE jmJobSetIndex OBJECT-TYPE
SYNTAX Integer32(1..32767) SYNTAX Integer32(1..32767)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job set index of the job set in which the job was placed "The job set index of the job set in which the job was placed
when that server or device accepted the job. This 16-bit value when that server or device accepted the job. This 16-bit value
in combination with the jmJobIndex value permits the management in combination with the jmJobIndex value permits the management
application to access the other tables to obtain the job- application to access the other tables to obtain the job-
specific objects. This value shall be the same for a job in the specific objects. This value SHALL be the same for a job in the
jmJobIDTable as the corresponding jmJobSetIndex value in the jmJobIDTable as the corresponding jmJobSetIndex value in the
jmJobStateTable and jmAttributeTable for this job. jmJobTable and jmAttributeTable for this job.
The value(s) of the jmJobSetIndex shall be persistent across The value(s) of the jmJobSetIndex SHALL be persistent across
power cycles, so that clients that have retained jmJobSetIndex power cycles, so that clients that have retained jmJobSetIndex
values will access the same job sets upon subsequent power-up. values will access the same job sets upon subsequent power-up.
NOTE - an implementation that has only one job set, such as a An implementation that has only one job set, such as a printer
printer with a single queue, shall hard code this object with with a single queue, SHALL hard code this object with the value
the value 1. See Terminology and Job Model on page 8 for the 1. See Terminology and Job Model on page 12 for the definition
definition of a job set." of a job set."
Job Monitoring MIB, V0.82 June 9, 1997
::= { jmJobIDEntry 2 } ::= { jmJobIDEntry 2 }
jmJobIndex OBJECT-TYPE jmJobIndex OBJECT-TYPE
SYNTAX Integer32(1..2147483647) SYNTAX Integer32(1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequential, monatonically increasing identifier index for "The sequential, monatonically increasing identifier index for
the job generated by the server or device when that server or the job generated by the server or device when that server or
device accepted the job. This index value permits the device accepted the job. This index value permits the
management application to access the other tables to obtain the management application to access the other tables to obtain the
job-specific row entries. This value shall be the index used in job-specific row entries. This value SHALL be the index used in
the jmJobStateTable and jmAttributeTable for this job. the jmJobTable and jmAttributeTable for this job.
See jmGeneralNewestActiveJobIndex on page 57 for a discussion See jmGeneralNewestActiveJobIndex on page 70 for a discussion
about the largest value of jmJobIndex for an implementation. about the largest value of jmJobIndex for an implementation.
NOTE - Agents instrumenting systems that contain jobs with a job Agents instrumenting systems that contain jobs with a job
identifier of 0 shall map the job identifier value 0 to a identifier of 0 SHALL map the job identifier value 0 to a
jmJobIndex value that is one higher than the highest job jmJobIndex value that is one higher than the highest job
identifier value that any job can have on that system." identifier value that any job can have on that system."
::= { jmJobIDEntry 3 } ::= { jmJobIDEntry 3 }
-- The Job Group (Mandatory)
Job Monitoring MIB, V0.81 April 24, 1997
-- The jmJobGroup consists entirely of the jmJobTable.
-- --
-- Implementation of every object in this group is MANDATORY.
-- See Section 4 entitled 'Conformance Considerations' on page 18.
jmJobStateG OBJECT IDENTIFIER ::= { jobmonMIB 7 } jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 }
jmJobStateTable OBJECT-TYPE jmJobTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmJobStateEntry SYNTAX SEQUENCE OF JmJobEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobStateTable consists of basic job state and status "The jmJobTable consists of basic job state and status
information for each job in a job set that (1) monitoring information for each job in a job set that (1) monitoring
applications need to be able to access in a single SNMP Get applications need to be able to access in a single SNMP Get
operation, (2) that have a single value per job, and (3) that operation, (2) that have a single value per job, and (3) that
shall always be implemented. SHALL always be implemented."
::= { jmJob 1 }
NOTE - Every accessible object in this table shall have the same jmJobEntry OBJECT-TYPE
value as one of the attributes in the jmAttributeTable. Job Monitoring MIB, V0.82 June 9, 1997
Implementations may either keep a separate copy or may share
each value that is common between the jmJobStateTable and the
jmAttributeTable. The persistence of the two tables may be
different depending on implementation and/or system
administrator policy as specified by the jmGeneralJobPersistence
and jmGeneralAttributePersistence objects defined on page 58.
Thus an accounting application need only copy the entire
jmAttributeTable or selected job rows and will obtain all of the
information about those jobs and their states."
::= { jmJobStateG 1 }
jmJobStateEntry OBJECT-TYPE SYNTAX JmJobEntry
SYNTAX JmJobStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Basic per-job state and status information. "Basic per-job state and status information.
An entry shall exist in this table for each job, no matter what An entry SHALL exist in this table for each job, no matter what
the state of the job is. Each job shall appear in one and only the state of the job is. Each job SHALL appear in one and only
one job set." one job set."
INDEX { jmJobSetIndex, jmJobIndex } INDEX { jmJobSetIndex, jmJobIndex }
::= { jmJobStateTable 1 } ::= { jmJobTable 1 }
JmJobEntry ::= SEQUENCE {
jmJobState JmJobStateTC, -- pg 32
jmJobStateReasons1 JmJobStateReasons1TC, -- pg 59
jmNumberOfInterveningJobs Integer32(-2..2147483647),
jmJobKOctetsRequested Integer32(-2..2147483647),
jmJobKOctetsProcessed Integer32(-2..2147483647),
jmJobImpressionsRequested Integer32(-2..2147483647),
jmJobImpressionsCompleted Integer32(-2..2147483647)
JmJobStateEntry ::= SEQUENCE {
jmJobState JmJobStateTC, -- pg 24
jmJobStateKOctetsCompleted Integer32(-2..2147483647),
jmJobStateImpressionsCompleted Integer32(-2..2147483647),
jmJobStateAssociatedValue Integer32(-2..2147483647)
} }
jmJobState OBJECT-TYPE jmJobState OBJECT-TYPE
MAX-ACCESS read-only MAX-ACCESS read-only
Job Monitoring MIB, V0.81 April 24, 1997 STATUS current
DESCRIPTION
"The current state of the job (pending, processing, completed,
etc.). Even though the JmJobStateTC textual-convention defines
nine values for job states, agents SHALL only implement those
states which are appropriate for the particular implementation.
In other words, all possible enums for this object SHALL be
reported if implemented by the device and available to the
agent. However, management applications SHALL be prepared to
receive all the standard job states.
The final value for this object SHALL be one of: completed,
canceled, or aborted. The minimum length of time that the agent
SHALL keep a job in the completed, canceled, or aborted state
before removing the job from the jmJobIDTable and jmJobTable is
specified by the value of the jmGeneralJobPersistence object."
::= { jmJobEntry 1 }
jmJobStateReasons1 OBJECT-TYPE
Job Monitoring MIB, V0.82 June 9, 1997
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the job (pending, processing, held, etc.). "Additional information about the job's current state, i.e.,
information that augments the value of the job's jmJobState
object.
The value of this object shall always be the same as that of the NOTE - The jobStateReasonsn (n=2..4) attributes (see page 39)
jobState attribute, so that this information appears in both the provide further additional information about the job's current
jmJobStateTable and the jmAttributeTable simultaneously. See state.
the JmJobStateTC textual-convention on page 20 and the jobState
attribute on page 30 in the jmAttributeTable for the full
specification of this object/attribute."
::= { jmJobStateEntry 1 }
jmJobStateKOctetsCompleted OBJECT-TYPE Implementation of these values is OPTIONAL, i.e., an agent NEED
NOT implement them, even if (1) the device supports the
functionality represented by the reason and (2) is available to
the agent. These values MAY be used with any job state or
states for which the reason makes sense. Furthermore, when
implemented, the agent SHALL return these values when the reason
applies and SHALL NOT return them when the reason no longer
applies whether the value of the job's jmJobState object changed
or not. When the job does not have any reasons for being in its
current state, the agent SHALL set the value of the
jmJobStateReasons1 object and jobStateReasonsn attributes to 0.
NOTE - While values cannot be added to the jmJobState object
without impacting deployed clients that take actions upon
receiving jmJobState values, it is the intent that additional
JmJobStateReasonsnTC enums can be defined and registered without
impacting such deployed clients. In other words, the
jmJobStateReasons1 object and jobStateReasonsn attributes are
intended to be extensible."
::= { jmJobEntry 2 }
jmNumberOfInterveningJobs OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of octets completed processing by the server "The number of jobs that are expected to be processed before
or device measured in units of K (1024) octets. this job is processed according to the implementation's queuing
algorithm if no other jobs were to be submitted. In other
The value of this object shall always be the same as that of the words, this value is the job's queue position. The agent SHALL
jobKOctetsCompleted attribute, so that this information appears return a value of 0 for this attribute when this job starts
in both the jmJobStateTable and the jmAttributeTable processing (since there are no jobs in front of the job)."
simultaneously. See the jobKOctetsCompleted attribute on page ::= { jmJobEntry 3 }
40 in the jmAttributeTable for the full specification of this
object/attribute."
::= { jmJobStateEntry 2 }
jmJobStateImpressionsCompleted OBJECT-TYPE jmJobKOctetsRequested OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
Job Monitoring MIB, V0.82 June 9, 1997
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of impressions completed being marked and "The total size in K (1024) octets of the document(s) being
stacked by the device for this job so far. requested to be processed in the job. The agent SHALL round the
actual number of octets up to the next highest K. Thus 0 octets
SHALL be represented as 0, 1-1024 octets SHALL be represented as
1, 1025-2048 SHALL be represented as 2, etc.
The value of this object shall always be the same as that of the The server/device MAY update the value of this attribute after
impressionsCompleted attribute, so that this information appears each document has been transferred to the server/device or the
in both the jmJobStateTable and the jmAttributeTable server/device MAY provide this value after all documents have
simultaneously. See the impressionsCompleted attribute on page been transferred to the server/device, depending on
41 in the jmAttributeTable for the full specification of this implementation. In other words, while the job is in the
object/attribute." pendingHeld state with the jmJobStateReasons1 object containing
::= { jmJobStateEntry 3 } a jobIncoming value, the value of the jmJobKOctetsRequested
object depends on implementation and MAY not correctly reflect
the size of the job.
jmJobStateAssociatedValue OBJECT-TYPE In computing this value, the server/device SHALL not include the
multiplicative factors contributed by (1) the number of document
copies, and (2) the number of job copies, independent of whether
the device can process multiple copies of the job or document
without making multiple passes over the job or document data and
independent of whether the output is collated or not. Thus the
server/device computation is independent of the implementation."
::= { jmJobEntry 4 }
jmJobKOctetsProcessed OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the most relevant attribute associated with the "The current number of octets processed by the server or device
job's current state. measured in units of K (1024) octets. The agent SHALL round the
actual number of octets processed up to the next higher K. Thus
0 octets SHALL be represented as 0, 1-1024 octets SHALL be
represented as 1, 1025-2048 octets SHALL be 2, etc. For
printing devices, this value is the number interpreted by the
page description language interpreter rather than what has been
marked on media. For implementations where multiple copies are
produced by the interpreter makes only a single pass over the
document, the final value SHALL be equal to the value of the
jmJobKOctetsRequested object. For implementations where
multiple copies are produced by the interpreter making multiple
passes over the document, the final value SHALL be a multiple of
the value of the jmJobKOctetsRequested object.
The value of this object shall always be the same as that of the Job Monitoring MIB, V0.82 June 9, 1997
jobStateAssociatedValue attribute, so that this information
Job Monitoring MIB, V0.81 April 24, 1997
appears in both the jmJobStateTable and the jmAttributeTable NOTE - See the impressionsCompletedCurrentCopy and
simultaneously. See the jobStateAssociatedValue attribute on pagesCompletedCurrentCopy attributes for attributes that are
page 30 in the jmAttributeTable for the full specification of reset on each document copy.
this object/attribute."
::= { jmJobStateEntry 4 } NOTE - The jmJobKOctetsProcessed object can be used in the
numerator with the jmJobKOctetsRequested object in the
denominator in order to produce a 'thermometer' that indicates
the progress of the job, provided that the multiplicative factor
is taken into account for some implementations of multiple
copies."
::= { jmJobEntry 5 }
jmJobImpressionsRequested OBJECT-TYPE
SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of impressions requested by this job to produce."
::= { jmJobEntry 6 }
jmJobImpressionsCompleted OBJECT-TYPE
SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of impressions completed for this job so
far. For printing devices, the impressions completed includes
interpreting, marking, and stacking the output. For other types
of job services, the number of impressions completed includes
the number of impressions processed."
::= { jmJobEntry 7 }
-- The Attribute Group (Mandatory) -- The Attribute Group (Mandatory)
-- The jmAttributeGroup consists entirely of the jmAttributeTable. -- The jmAttributeGroup consists entirely of the jmAttributeTable.
-- --
-- Implementation of the two objects in this group is MANDATORY.
-- See Section 4 entitled 'Conformance Considerations' on page 18.
-- --
-- A few attributes are MANDATORY for agent conformance, and the rest
-- are OPTIONAL. See the specification of the JmAttributeTypeTC on
-- page 35 for which attributes are MANDATORY for agents to implement.
jmAttribute OBJECT IDENTIFIER ::= { jobmonMIB 8 } jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 }
Job Monitoring MIB, V0.82 June 9, 1997
jmAttributeTable OBJECT-TYPE jmAttributeTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmAttributeEntry SYNTAX SEQUENCE OF JmAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmAttributeTable shall contain attributes of the job and "The jmAttributeTable SHALL contain attributes of the job and
document(s) for each job in a job set. Instead of allocating document(s) for each job in a job set. Instead of allocating
distinct objects for each attribute, each attribute is distinct objects for each attribute, each attribute is
represented as a separate row in the jmAttributeTable. Some represented as a separate row in the jmAttributeTable."
attributes represent information about the job and document(s),
such as file-names, document-names, submission-time, completion-
time, size, etc. Other attributes represent requested and/or
consumed resources for each job for use by monitoring and
accounting applications.
The jmAttributeTable is a per-job table with an extra index for
each type of attribute (jmAttributeTypeIndex) that a job can
have and an additional index (jmAttributeInstanceIndex) for
those attributes that can have multiple instances per job. The
jmAttributeTypeIndex object shall contain an enum type that
indicates the type of attribute (see JmAttributeTypeTC on page
27). The value of the attribute shall be represented in either
the jmAttributeValueAsInteger or jmAttributeValueAsOctets
objects, or both, as specified in the JmAttributeTypeTC textual-
convention.
1)The agent shall create rows in the jmAttributeTable as the
server or device is able to discover the attributes either
from the job submission protocol itself or from the document
PDL. As the documents are interpreted, the interpreter may
discover additional attributes and so the agent adds
additional rows to this table. As the attributes that
Job Monitoring MIB, V0.81 April 24, 1997
represent resources are actually consumed, the usage counter
contained in the jmAttributeValueAsInteger object is
incremented according to the units indicated in the
description of the JmAttributeTypeTC enum."
::= { jmAttribute 1 } ::= { jmAttribute 1 }
jmAttributeEntry OBJECT-TYPE jmAttributeEntry OBJECT-TYPE
SYNTAX JmAttributeEntry SYNTAX JmAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes representing information about the job and "Attributes representing information about the job and
document(s) or resources required and/or consumed. document(s) or resources required and/or consumed.
Zero or more entries shall exist in this table for each job in a Each entry in the jmAttributeTable is a per-job entry with an
job set. Each job shall appear in one and only one job set." extra index for each type of attribute (jmAttributeTypeIndex)
that a job can have and an additional index
(jmAttributeInstanceIndex) for those attributes that can have
multiple instances per job. The jmAttributeTypeIndex object
SHALL contain an enum type that indicates the type of attribute
(see JmAttributeTypeTC on page 35). The value of the attribute
SHALL be represented in either the jmAttributeValueAsInteger or
jmAttributeValueAsOctets objects, and/or both, as specified in
the JmAttributeTypeTC textual-convention.
The agent SHALL create rows in the jmAttributeTable as the
server or device is able to discover the attributes either from
the job submission protocol itself or from the document PDL. As
the documents are interpreted, the interpreter MAY discover
additional attributes and so the agent adds additional rows to
this table. As the attributes that represent resources are
actually consumed, the usage counter contained in the
jmAttributeValueAsInteger object is incremented according to the
units indicated in the description of the JmAttributeTypeTC
enum.
The agent SHALL maintain each row in the jmJobTable for at least
the minimum time after a job completes as specified by the
jmGeneralAttributePersistence (see page 72).
Zero or more entries SHALL exist in this table for each job in a
job set. Each job SHALL appear in one and only one job set."
Job Monitoring MIB, V0.82 June 9, 1997
INDEX { jmJobSetIndex, jmJobIndex, jmAttributeTypeIndex, INDEX { jmJobSetIndex, jmJobIndex, jmAttributeTypeIndex,
jmAttributeInstanceIndex } jmAttributeInstanceIndex }
::= { jmAttributeTable 1 } ::= { jmAttributeTable 1 }
JmAttributeEntry ::= SEQUENCE { JmAttributeEntry ::= SEQUENCE {
jmAttributeTypeIndex JmAttributeTypeTC, -- pg 27 jmAttributeTypeIndex JmAttributeTypeTC, -- pg 35
jmAttributeInstanceIndex Integer32(1..32767), jmAttributeInstanceIndex Integer32(1..32767),
jmAttributeValueAsInteger Integer32(-2..2147483647), jmAttributeValueAsInteger Integer32(-2..2147483647),
jmAttributeValueAsOctets OCTET STRING(SIZE(0..63)) jmAttributeValueAsOctets OCTET STRING(SIZE(0..63))
} }
jmAttributeTypeIndex OBJECT-TYPE jmAttributeTypeIndex OBJECT-TYPE
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of attribute that this row entry represents. "The type of attribute that this row entry represents.
The type may identify information about the job or document(s) The type MAY identify information about the job or document(s)
or may identify a resource required to process the job before or MAY identify a resource required to process the job before
the job start processing and/or consumed by the job as the job the job start processing and/or consumed by the job as the job
is processed. is processed.
Examples of job and document information include: Examples of job and document attributes include:
jobCopiesRequested, documentCopiesRequested, jobCopiesCompleted, jobCopiesRequested, documentCopiesRequested, jobCopiesCompleted,
documentCopiesCompleted, fileName, and documentName. documentCopiesCompleted, fileName, and documentName.
Examples of resources required and consumed include: Examples of required and consumed resource attributes include: