draft-ietf-printmib-job-monitor-08.txt   rfc2707.txt 
INTERNET-DRAFT R. Bergman Network Working Group R. Bergman
Dataproducts Corp. Request for Comments: 2707 Dataproducts Corp.
T. Hastings (editor) Category: Informational T. Hastings, Ed.
Xerox Corporation Xerox Corporation
S. Isaacson S. Isaacson
Novell, Inc. Novell, Inc.
H. Lewis H. Lewis
IBM Corp. IBM Corp.
February 19, 1999 November 1999
Job Monitoring MIB - V1.0 Job Monitoring MIB - V1.0
<draft-ietf-printmib-job-monitor-08.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This memo provides information for the Internet community. It does
all provisions of Section 10 of [RFC2026]. Internet-Drafts are not specify an Internet standard of any kind. Distribution of this
working documents of the Internet Engineering Task Force (IETF), memo is unlimited.
its areas, and its working groups. Note that other groups may
also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html.
This Internet-Draft expires on August 19, 1999.
Copyright Notice Copyright Notice
@
Copyright (C) The Internet Society (1998). All Rights Reserved.
@
Abstract
This document has been developed and approved by the Printer
Working Group (PWG) as a PWG standard. It is intended to be
distributed as an Informational RFC. This document provides a
printer industry standard SNMP MIB for (1) monitoring the status
and progress of print jobs (2) obtaining resource requirements
before a job is processed, (3) monitoring resource consumption
while a job is being processed and (4) 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 server
that supports one or more printers. Use of the object set is not
limited to printing. However, support for services other than
printing is outside the scope of this Job Monitoring MIB. Future
extensions to this MIB may include, but are not limited to, fax
machines and scanners.
TABLE OF CONTENTS
1 INTRODUCTION 6
1.1 Types of Information in the MIB 6
1.2 Types of Job Monitoring Applications 8
2 TERMINOLOGY AND JOB MODEL 9
2.1 System Configurations for the Job Monitoring MIB 12
2.1.1 Configuration 1 - client-printer 12
2.1.2 Configuration 2 - client-server-printer - agent in the
server 13
2.1.3 Configuration 3 - client-server-printer - client monitors
printer agent and server 14
3 MANAGED OBJECT USAGE 16
3.1 Conformance Considerations 16
3.1.1 Conformance Terminology 16
3.1.2 Agent Conformance Requirements 16
3.1.2.1 MIB II System Group objects 17
3.1.2.2 MIB II Interface Group objects 17
3.1.2.3 Printer MIB objects 17
3.1.3 Job Monitoring Application Conformance Requirements 17
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 18
3.3 The Attribute Mechanism and the Attribute Table(s) 20
3.3.1 Conformance of Attribute Implementation 20
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and
Attributes 21
3.3.3 Index Value Attributes 21
3.3.4 Data Sub-types and Attribute Naming Conventions 22
3.3.5 Single-Value (Row) Versus Multi-Value (MULTI-ROW)
Attributes 23
3.3.6 Requested Objects and Attributes 23
3.3.7 Consumption Attributes 23
3.3.8 Attribute Specifications 24
3.3.9 Job State Reason bit definitions 44
3.3.9.1 JmJobStateReasons1TC specification 45
3.3.9.2 JmJobStateReasons2TC specification 49
3.3.9.3 JmJobStateReasons3TC specification 52
3.3.9.4 JmJobStateReasons4TC specification 53
3.4 Monitoring Job Progress 53
3.5 Job Identification 57
3.5.1 The Job Submission ID specifications 58
3.6 Internationalization Considerations 63
3.6.1 Text generated by the server or device 63
3.6.2 Text supplied by the job submitter 64
3.6.3 'DateAndTime' for representing the date and time 65
3.7 IANA and PWG Registration Considerations 65
3.7.1 PWG Registration of enums 65
3.7.1.1 Type 1 enumerations 66
3.7.1.2 Type 2 enumerations 66
3.7.1.3 Type 3 enumeration 66
3.7.2 PWG Registration of type 2 bit values 67
3.7.3 PWG Registration of Job Submission Id Formats 67
3.7.4 PWG Registration of MIME types/sub-types for document-
formats 67
3.8 Security Considerations 67
3.8.1 Read-Write objects 67
3.8.2 Read-Only Objects In Other User's Jobs 68
3.9 Notifications 68
4 MIB SPECIFICATION 68
Textual conventions for this MIB module 70
JmUTF8StringTC 70
JmJobStringTC 70
JmNaturalLanguageTagTC 70
JmTimeStampTC 71
JmJobSourcePlatformTypeTC 71
JmFinishingTC 72
JmPrintQualityTC 73
JmPrinterResolutionTC 73
JmTonerEconomyTC 74
JmBooleanTC 74
JmMediumTypeTC 74
JmJobCollationTypeTC 76
JmJobSubmissionIDTypeTC 76
JmJobStateTC 77
JmAttributeTypeTC 80
JmJobServiceTypesTC 84
JmJobStateReasons1TC 85
JmJobStateReasons2TC 85
JmJobStateReasons3TC 86
JmJobStateReasons4TC 86
The General Group (MANDATORY) 87
jmGeneralJobSetIndex (Int32(1..32767)) 88
jmGeneralNumberOfActiveJobs (Int32(0..)) 88
jmGeneralOldestActiveJobIndex (Int32(0..)) 89
jmGeneralNewestActiveJobIndex (Int32(0..)) 89
jmGeneralJobPersistence (Int32(15..)) 90
jmGeneralAttributePersistence (Int32(15..)) 90
jmGeneralJobSetName (UTF8String63) 91
The Job ID Group (MANDATORY) 92 Copyright (C) The Internet Society (1999). All Rights Reserved.
jmJobSubmissionID (OCTET STRING(SIZE(48))) 93
jmJobIDJobSetIndex (Int32(0..32767)) 94
jmJobIDJobIndex (Int32(0..)) 94
The Job Group (MANDATORY) 95
jmJobIndex (Int32(1..)) 96
jmJobState (JmJobStateTC) 96
jmJobStateReasons1 (JmJobStateReasons1TC) 97
jmNumberOfInterveningJobs (Int32(-2..)) 97
jmJobKOctetsPerCopyRequested (Int32(-2..)) 98
jmJobKOctetsProcessed (Int32(-2..)) 98
jmJobImpressionsPerCopyRequested (Int32(-2..)) 99
jmJobImpressionsCompleted (Int32(-2..)) 99
jmJobOwner (JobString63) 100
The Attribute Group (MANDATORY) 101
jmAttributeTypeIndex (JmAttributeTypeTC) 103
jmAttributeInstanceIndex (Int32(1..32767)) 103
jmAttributeValueAsInteger (Int32(-2..)) 104
jmAttributeValueAsOctets (Octets63) 105
5 APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 108
6 APPENDIX B - SUPPORT OF JOB SUBMISSION PROTOCOLS 109 IESG Note
7 REFERENCES 109 This MIB module uses an unconventional scheme for modeling management
information (on top of the SNMP model) which is unique to this MIB.
The IESG recommends against using this document as an example for the
design of future MIBs.
8 AUTHOR'S ADDRESSES 111 The "Printer Working Group" industry consortium is not an IETF
working group, and the IETF does not recognize the Printer Working
Group as a standards-setting body. This document is being published
solely to provide information to the Internet community regarding a
MIB that might be deployed in the marketplace. Publication of this
document as an RFC is not an endorsement of this MIB.
9 CHANGE HISTORY 114 Abstract
9.1 Changes to produce version 1.0, dated February 19, 1999 114 This document provides a printer industry standard SNMP MIB for (1)
monitoring the status and progress of print jobs (2) obtaining
resource requirements before a job is processed, (3) monitoring
resource consumption while a job is being processed and (4)
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
server that supports one or more printers. Use of the object set is
not limited to printing. However, support for services other than
printing is outside the scope of this Job Monitoring MIB. Future
extensions to this MIB may include, but are not limited to, fax
machines and scanners.
9.2 Changes to produce version 1.2, dated October 2, 1998 114 Table of Contents
9.3 Changes to produce version 1.1, dated October 1, 1998 115 1 INTRODUCTION 4
1.1 Types of Information in the MIB 5
1.2 Types of Job Monitoring Applications 6
2 TERMINOLOGY AND JOB MODEL 7
2.1 System Configurations for the Job Monitoring MIB 11
2.1.1 Configuration 1 - client-printer 11
2.1.2 Configuration 2 - client-server-printer - agent in the
server 12
2.1.3 Configuration 3 - client-server-printer - client
monitors printer agent and server 14
3 MANAGED OBJECT USAGE 15
3.1 Conformance Considerations 15
3.1.1 Conformance Terminology 16
3.1.2 Agent Conformance Requirements 16
3.1.2.1 MIB II System Group objects 17
3.1.2.2 MIB II Interface Group objects 17
3.1.2.3 Printer MIB objects 17
3.1.3 Job Monitoring Application Conformance Requirements 17
3.2 The Job Tables and the Oldest Active and Newest Active
Indexes 18
3.3 The Attribute Mechanism and the Attribute Table(s) 20
3.3.1 Conformance of Attribute Implementation 21
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and
Attributes 21
3.3.3 Index Value Attributes 22
3.3.4 Data Sub-types and Attribute Naming Conventions 22
3.3.5 Single-Value (Row) Versus Multi-Value (MULTI-ROW)
Attributes 23
3.3.6 Requested Objects and Attributes 23
3.3.7 Consumption Attributes 24
3.3.8 Attribute Specifications 24
3.3.9 Job State Reason bit definitions 43
3.3.9.1 JmJobStateReasons1TC specification 44
3.3.9.2 JmJobStateReasons2TC specification 47
3.3.9.3 JmJobStateReasons3TC specification 51
3.3.9.4 JmJobStateReasons4TC specification 51
3.4 Monitoring Job Progress 51
3.5 Job Identification 55
3.5.1 The Job Submission ID specifications 56
3.6 Internationalization Considerations 60
3.6.1 Text generated by the server or device 61
3.6.2 Text supplied by the job submitter 61
3.6.3 'DateAndTime' for representing the date and time 63
10 INDEX 116 3.7 IANA and PWG Registration Considerations 63
Job Monitoring MIB 3.7.1 PWG Registration of enums 63
3.7.1.1 Type 1 enumerations 64
3.7.1.2 Type 2 enumerations 64
3.7.1.3 Type 3 enumeration 64
3.7.2 PWG Registration of type 2 bit values 65
3.7.3 PWG Registration of Job Submission Id Formats 65
3.7.4 PWG Registration of MIME types/sub-types for document-
formats 65
3.8 Security Considerations 65
3.8.1 Read-Write objects 65
3.8.2 Read-Only Objects In Other User's Jobs 66
3.9 Notifications 66
4 MIB SPECIFICATION 67
Textual conventions for this MIB module 68
JmUTF8StringTC 68
JmJobStringTC 68
JmNaturalLanguageTagTC 68
JmTimeStampTC 69
JmJobSourcePlatformTypeTC 69
JmFinishingTC 70
JmPrintQualityTC 71
JmPrinterResolutionTC 71
JmTonerEconomyTC 72
JmBooleanTC 72
JmMediumTypeTC 72
JmJobCollationTypeTC 74
JmJobSubmissionIDTypeTC 74
JmJobStateTC 75
JmAttributeTypeTC 78
JmJobServiceTypesTC 81
JmJobStateReasons1TC 83
JmJobStateReasons2TC 83
JmJobStateReasons3TC 83
JmJobStateReasons4TC 84
The General Group (MANDATORY) 84
jmGeneralJobSetIndex (Int32(1..32767)) 85
jmGeneralNumberOfActiveJobs (Int32(0..)) 86
jmGeneralOldestActiveJobIndex (Int32(0..)) 86
jmGeneralNewestActiveJobIndex (Int32(0..)) 86
jmGeneralJobPersistence (Int32(15..)) 87
jmGeneralAttributePersistence (Int32(15..)) 87
jmGeneralJobSetName (UTF8String63) 88
The Job ID Group (MANDATORY) 88
jmJobSubmissionID (OCTET STRING(SIZE(48))) 89
jmJobIDJobSetIndex (Int32(0..32767)) 90
jmJobIDJobIndex (Int32(0..)) 91
The Job Group (MANDATORY) 91
jmJobIndex (Int32(1..)) 92
jmJobState (JmJobStateTC) 92
jmJobStateReasons1 (JmJobStateReasons1TC) 93
jmNumberOfInterveningJobs (Int32(-2..)) 93
jmJobKOctetsPerCopyRequested (Int32(-2..)) 94
jmJobKOctetsProcessed (Int32(-2..)) 94
jmJobImpressionsPerCopyRequested (Int32(-2..)) 95
jmJobImpressionsCompleted (Int32(-2..)) 96
jmJobOwner (JobString63) 96
The Attribute Group (MANDATORY) 97
jmAttributeTypeIndex (JmAttributeTypeTC) 98
jmAttributeInstanceIndex (Int32(1..32767)) 99
jmAttributeValueAsInteger (Int32(-2..)) 99
jmAttributeValueAsOctets (Octets63) 100
5 APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 104
6 APPENDIX B - SUPPORT OF JOB SUBMISSION PROTOCOLS 105
7 REFERENCES 105
8 NOTICES 108
9 AUTHORS' ADDRESSES 109
10 INDEX 111
11 Full Copyright Statement 114
1 Introduction 1 Introduction
This specification defines an official Printer Working Group (PWG) This specification defines an official Printer Working Group (PWG)
[PWG] standard SNMP MIB for the monitoring of jobs on network printers. [PWG] standard SNMP MIB for the monitoring of jobs on network
This specification is being published as an IETF Information Document printers. This specification is being published as an IETF
for the convenience of the Internet community. In consultation with Information Document for the convenience of the Internet community.
the IETF Application Area Directors, it was concluded that this MIB In consultation with the IETF Application Area Directors, it was
specification properly belongs as an Information document, because this concluded that this MIB specification properly belongs as an
MIB monitors a service node on the network, rather than a network node Information document, because this MIB monitors a service node on the
proper. network, rather than a network node proper.
The Job Monitoring MIB is intended to be implemented by an agent within The Job Monitoring MIB is intended to be implemented by an agent
a printer or the first server closest to the printer, where the printer within a printer or the first server closest to the printer, where
is either directly connected to the server only or the printer does not the printer is either directly connected to the server only or the
contain the job monitoring MIB agent. It is recommended that printer does not contain the job monitoring MIB agent. It is
implementations place the SNMP agent as close as possible to the recommended that implementations place the SNMP agent as close as
processing of the print job. This MIB applies to printers with and possible to the processing of the print job. This MIB applies to
without spooling capabilities. This MIB is designed to be compatible printers with and without spooling capabilities. This MIB is
with most current commonly-used job submission protocols. In most designed to be compatible with most current commonly-used job
environments that support high function job submission/job control submission protocols. In most environments that support high
protocols, like ISO DPA[iso-dpa], those protocols would be used to function job submission/job control protocols, like ISO DPA [iso-
monitor and manage print jobs rather than using the Job Monitoring MIB. dpa], those protocols would be used to monitor and manage print jobs
rather than using the Job Monitoring MIB.
The Job Monitoring MIB consists of a General Group, a Job Submission ID The Job Monitoring MIB consists of a General Group, a Job Submission
Group, a Job Group, and an Attribute Group. Each group is a table. ID Group, a Job Group, and an Attribute Group. Each group is a
All accessible objects are read-only. The General Group contains table. All accessible objects are read-only. The General Group
general information that applies to all jobs in a job set. The Job contains general information that applies to all jobs in a job set.
Submission ID table maps the job submission ID that the client uses to The Job Submission ID table maps the job submission ID that the
identify a job to the jmJobIndex that the Job Monitoring Agent uses to client uses to identify a job to the jmJobIndex that the Job
identify jobs in the Job and Attribute tables. The Job table contains Monitoring Agent uses to identify jobs in the Job and Attribute
the MANDATORY integer job state and status objects. The Attribute tables. The Job table contains the MANDATORY integer job state and
table consists of multiple entries per job that specify (1) job and status objects. The Attribute table consists of multiple entries per
document identification and parameters, (2) requested resources, and job that specify (1) job and document identification and parameters,
(3) consumed resources during and after job processing/printing. A (2) requested resources, and (3) consumed resources during and after
larger number of job attributes are defined as textual conventions that job processing/printing. A larger number of job attributes are
an agent SHALL return if the server or device implements the defined as textual conventions that an agent SHALL return if the
functionality so represented and the agent has access to the server or device implements the functionality so represented and the
information. agent has access to the information.
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[print-mib] (Appendix D - Roles indicated Role Models in the Printer MIB [print-mib] (Appendix D -
of Users). Roles of Users).
User: User:
Provide the ability to identify the least busy printer. The user Provide the ability to identify the least busy printer. The
will be able to determine the number and size of jobs waiting for user will be able to determine the number and size of jobs
each printer. No attempt is made to actually predict the length waiting for each printer. No attempt is made to actually
of time that jobs will take. predict the length of time that jobs will take.
Provide the ability to identify the current status of the user's Provide the ability to identify the current status of the
job (user queries). user's job (user queries).
Provide a timely indication that the job has completed and where Provide a timely indication that the job has completed and
it can be found. where 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
system. print system.
Provide the ability to identify the user that submitted the print Provide the ability to identify the user that submitted the
job. print 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,
estimates of time to process a job is not being attempted. exact estimates of time to process a job is not being
Instead, objects are included that allow the operator to be able attempted. Instead, objects are included that allow the
to make gross estimates. operator to be able to make gross estimates.
Capacity Planner: Capacity Planner:
Provide the ability to determine printer utilization as a Provide the ability to determine printer utilization as a
function of time. function of time.
Provide the ability to determine how long jobs wait before Provide the ability to determine how long jobs wait before
starting to print. starting to print.
Accountant: Accountant:
Provide information to allow the creation of a record of Provide information to allow the creation of a record of
resources consumed and printer usage data for charging users or resources consumed and printer usage data for charging users or
groups for resources consumed. groups for resources consumed.
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
but still be usable for low end printers that only contain a single job time, but still be usable for low end printers that only contain a
at a time. In particular, the MIB supports the needs of Windows and single job at a time. In particular, the MIB supports the needs of
other PC environments for managing low-end direct-connect (serial or Windows and other PC environments for managing low-end direct-connect
parallel) and networked devices without unnecessary overhead or (serial or parallel) and networked devices without unnecessary
complexity, while also providing for higher end systems and devices. overhead or complexity, while also providing for higher end systems
and devices.
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 The Job Monitoring MIB is designed for the following types of
monitoring applications: monitoring applications:
1. Monitor a single job starting when the job is submitted and
ending a defined period after the job completes. The Job
Submission ID table provides the map to find the specific job
to be monitored.
2. Monitor all 'active' jobs in a queue, which this specification 1. Monitor a single job starting when the job is submitted and
generalizes to a "job set". End users may use such a program ending a defined period after the job completes. The Job
when selecting a least busy printer, so the MIB is designed for Submission ID table provides the map to find the specific job
such a program to start up quickly and find the information to be monitored.
needed quickly without having to read all (completed) jobs in
order to find the active jobs. System operators may also use
such a program, in which case it would be running for a long
period of time and may also be interested in the jobs that have
completed. Finally such a program may be used to provide an
enhanced console and logging capability.
3. Collect resource usage for accounting or system utilization 2. Monitor all 'active' jobs in a queue, which this
purposes that copy the completed job statistics to an specification generalizes to a "job set". End users may use
accounting system. It is recognized that depending on such a program when selecting a least busy printer, so the
accounting programs to copy MIB data during the job-retention MIB is designed for such a program to start up quickly and
period is somewhat unreliable, since the accounting program may find the information needed quickly without having to read
not be running (or may have crashed). Such a program is also all (completed) jobs in order to find the active jobs.
expected to keep a shadow copy of the entire Job Attribute System operators may also use such a program, in which case
table including completed, canceled, and aborted jobs which the it would be running for a long period of time and may also be
program updates on each polling cycle. Such a program polls at interested in the jobs that have completed. Finally such a
the rate of the persistence of the Attribute table. The design program may be used to provide an enhanced console and
is not optimized to help such an application determine which logging capability.
jobs are completed, canceled, or aborted. Instead, the
application SHOULD query each job that the application's shadow
copy shows was not complete, canceled, or aborted at the
previous poll cycle to see if it is now complete or canceled,
plus any new jobs that have been submitted.
The MIB provides a set of objects that represent a compatible subset of 3. Collect resource usage for accounting or system utilization
job and document attributes of the ISO DPA standard[iso-dpa] and the purposes that copy the completed job statistics to an
Internet Printing Protocol (IPP)[ipp-model], so that coherence is accounting system. It is recognized that depending on
maintained between these two protocols and the information presented to accounting programs to copy MIB data during the job-retention
end users and system operators by monitoring applications. However, period is somewhat unreliable, since the accounting program
the job monitoring MIB is intended to be used with printers that may not be running (or may have crashed). Such a program is
implement other job submitting and management protocols, such as IEEE also expected to keep a shadow copy of the entire Job
1284.1 (TIPSI)[tipsi], as well as with ones that do implement ISO DPA. Attribute table including completed, canceled, and aborted
jobs which the program updates on each polling cycle. Such a
program polls at the rate of the persistence of the Attribute
table. The design is not optimized to help such an
application determine which jobs are completed, canceled, or
aborted. Instead, the application SHOULD query each job that
the application's shadow copy shows was not complete,
canceled, or aborted at the previous poll cycle to see if it
is now complete or canceled, plus any new jobs that have been
submitted.
Thus the job monitoring MIB does not require implementation of either The MIB provides a set of objects that represent a compatible subset
the ISO DPA or IPP protocols. of job and document attributes of the ISO DPA standard [iso-dpa] and
the Internet Printing Protocol (IPP) [ipp-model], so that coherence
is maintained between 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 job submitting and management
protocols, such as IEEE 1284.1 (TIPSI) [tipsi], as well as with ones
that do implement ISO DPA. Thus the job monitoring MIB does not
require implementation of either the ISO DPA or IPP protocols.
The MIB is designed so that an additional MIB(s) can be specified in 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 the 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
the general model for jobs in alphabetical order. and the general model for jobs in alphabetical order.
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[iso-dpa]. For example, PostScript systems use the term standard [iso-dpa]. For example, PostScript systems use the term
session for what is called a job in this specification and the term session for what is called a job in this specification and the
job to mean what is called a document in this specification. term job to mean what is called a document in this specification.
Accounting Application: The SNMP management application that copies Accounting Application: The SNMP management application that copies
job information to some more permanent medium so that another job information to some more permanent medium so that another
application can perform accounting on the data for Accountants, Asset application can perform accounting on the data for Accountants, Asset
Managers, and Capacity Planners use. Managers, and Capacity Planners use.
Agent: The network entity that accepts SNMP requests from a monitor or Agent: The network entity that accepts SNMP requests from a monitor
accounting application and provides access to the instrumentation for or accounting application and provides access to the instrumentation
managing jobs modeled by the management objects defined in the Job for managing jobs modeled by the management objects defined in the
Monitoring MIB module for a server or a device. Job Monitoring MIB module for a server or a device.
Attribute: A name, value-pair that specifies a job or document Attribute: A name, value-pair that specifies a job or document
instruction, a status, or a condition of a job or a document that has instruction, a status, or a condition of a job or a document that has
been submitted to a server or device. A particular attribute NEED NOT been submitted to a server or device. A particular attribute NEED
be present in each job instance. In other words, attributes are NOT be present in each job instance. In other words, attributes are
present in a job instance only when there is a need to express the present in a job instance only when there is a need to express the
value, either because (1) the client supplied a value in the job value, either because (1) the client supplied a value in the job
submission protocol, (2) the document data contained an embedded submission protocol, (2) the document data contained an embedded
attribute, or (3) the server or device supplied a default value. An attribute, or (3) the server or device supplied a default value. An
agent MAY represent an attribute as an entry (row) in the Attribute agent MAY represent an attribute as an entry (row) in the Attribute
table in this MIB in which entries are present only when necessary. table in this MIB in which entries are present only when necessary.
Attributes are identified in this MIB by an enum. Attributes are identified in this MIB by an enum.
Client: The network entity that end users use to submit jobs to Client: 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 over a serial or configuration, using any job submission protocol over a serial or
parallel port to a directly-connected device or over the network to a parallel port to a directly-connected device or over the network to a
networked-connected device. networked-connected device.
Device: A hardware entity that (1) interfaces to humans, such as a Device: A hardware entity that (1) interfaces to humans, such as a
device that produces marks on paper or scans marks on paper to produce device that produces marks on paper or scans marks on paper to
an electronic representation, (2) accesses digital media, such as CD- produce an electronic representation, (2) accesses digital media,
ROMs, or (3) interfaces electronically to another device, such as sends such as CD-ROMs, or (3) interfaces electronically to another device,
FAX data to another FAX device. such as sends FAX data to another FAX device.
Document: A sub-section within a job that contains print data and Document: A sub-section within a job that contains print data and
document instructions that apply to just the document. document instructions that apply to just the document.
Document Instruction: An instruction specifying how to process the Document Instruction: 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
the document data or a combination, depending on the job submission in the document data or a combination, depending on the job
protocol and implementation. submission protocol and implementation.
End User: A user that uses a client to submit a print job. See End User: A user that uses a client to submit a print job. See
"user". "user".
Impression: For a print job, an impression is the passage of the Impression: For a print job, an impression is the passage of the
entire side of a sheet by the marker, whether or not any marks are made entire side of a sheet by the marker, whether or not any marks are
and independent of the number of passes that the side makes past the made and independent of the number of passes that the side makes past
marker. Thus a four pass color process counts as a single impression, the marker. Thus a four pass color process counts as a single
as does highlight color. Impression counters count all kinds: impression, as does highlight color. Impression counters count all
monochrome, highlight color, and full process color, while full color kinds: monochrome, highlight color, and full process color, while
counters only count full color impressions, and high light color full color counters only count full color impressions, and high light
counters only count high light color impressions. color counters only count high light color impressions.
One-sided processing involves one impression per sheet. Two-sided One-sided processing involves one impression per sheet. Two-sided
processing involves two impressions per sheet. If a two-sided document processing involves two impressions per sheet. If a two-sided
has an odd number of pages, the last sheet still counts as two document has an odd number of pages, the last sheet still counts as
impressions, if that sheet makes two passes through the marker or the two impressions, if that sheet makes two passes through the marker or
marker marks on both sides of a sheet in a single pass. Two-up the marker marks on both sides of a sheet in a single pass. Two-up
printing is the placement of two logical pages on one side of a sheet printing is the placement of two logical pages on one side of a sheet
and so is still a single impression. See "page" and "sheet". and so is still a single impression. See "page" and "sheet".
NOTE - Since impressions include blank sides, it is suggested that NOTE - Since impressions include blank sides, it is suggested that
accounting application implementers consider charging for sheets, accounting application implementers consider charging for sheets,
rather than impressions, possibly using the value of the sides rather than impressions, possibly using the value of the sides
attribute to select different charges for one-sided versus two-sided attribute to select different charges for one-sided versus two-sided
printing, since some users may think that impressions don't include printing, since some users may think that impressions don't include
blank sides. blank sides.
Internal Collation: The production of the sheets for each document copy Internal Collation: The production of the sheets for each document
performed within the printing device by making multiple passes over copy performed within the printing device by making multiple passes
either the source or an intermediate representation of the document. over either the source or an intermediate representation of the
document.
Job: A unit of work whose results are expected together without Job: A unit of work whose results are expected together without
interjection of unrelated results. A job contains one or more interjection of unrelated results. A job contains one or more
documents. documents.
Job Accounting: The activity of a management application of accessing Job Accounting: The activity of a management application of
the MIB and recording what happens to the job during and after the accessing the MIB and recording what happens to the job during and
processing of the job. after the processing of the job.
Job Instruction: An instruction specifying how, when, or where the job Job Instruction: An instruction specifying how, when, or where the
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 combination depending on the job submission protocol and
implementation. implementation.
Job Monitoring (using SNMP): The activity of a management application Job Monitoring (using SNMP): The activity of a management
of accessing the MIB and (1) identifying jobs in the job tables being application of accessing the MIB and (1) identifying jobs in the job
processed by the server, printer or other devices, and (2) displaying tables being processed by the server, printer or other devices, and
information to the user about the processing of the job. (2) displaying information to the user about the processing of the
job.
Job Monitoring Application: The SNMP management application that End Job Monitoring Application: The SNMP management application that End
Users, and System Operators use to monitor jobs using SNMP. A monitor Users, and System Operators use to monitor jobs using SNMP. A
MAY be either a separate application or MAY be part of the client that monitor MAY be either a separate application or MAY be part of the
also submits jobs. See "monitor". client that also submits jobs. See "monitor".
Job Set: A group of jobs that are queued and scheduled together Job Set: A group 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
set of devices. For implementations that embed the SNMP agent in the or set of devices. For implementations that embed the SNMP agent in
device, the MIB job set normally represents all the jobs known to the the device, the MIB job set normally represents all the jobs known to
device, so that the implementation only implements a single job set. the device, so that the implementation only implements a single job
If the SNMP agent is implemented in a server that controls one or more set. If the SNMP agent is implemented in a server that controls one
devices, each MIB job set represents a job queue for (1) a specific or more devices, each MIB job set represents a job queue for (1) a
device or (2) set of devices, if the server uses a single queue to load specific device or (2) set of devices, if the server uses a single
balance between several devices. Each job set is disjoint; no job queue to load balance between several devices. Each job set is
SHALL be represented in more than one MIB job set. disjoint; no job SHALL be represented in more than one MIB job set.
Monitor: Short for Job Monitoring Application. Monitor: Short for Job Monitoring Application.
Page: A page is a logical division of the original source document. Page: A page is a logical division of the original source document.
Number up is the imposition of more than one page on a single side of a Number up is the imposition of more than one page on a single side of
sheet. See "impression" and "sheet" and "two-up". a sheet. See "impression" and "sheet" and "two-up".
Proxy: An agent that acts as a concentrator for one or more other Proxy: 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
agents, forwarding them on to those other agents, gathering responses other agents, forwarding them on to those other agents, gathering
from those other agents and returning them to the original requesting responses from those other agents and returning them to the original
monitor. requesting monitor.
Queuing: The act of a device or server of ordering (queuing) the jobs Queuing: The act of a device or server of ordering (queuing) the
for the purposes of scheduling the jobs to be processed. jobs for the purposes of scheduling the jobs to be processed.
Printer: A device that puts marks on media. Printer: A device that puts marks on media.
Server: A network entity that accepts jobs from clients and in turn Server: A network entity that accepts jobs from clients and in turn
submits the jobs to printers and other devices that may be directly submits the jobs to printers and other devices that may be directly
connected to the server via a serial or parallel port or may be on the connected to the server via a serial or parallel port or may be on
network. A server MAY be a printer supervisor control program, or a the network. A server MAY be a printer supervisor control program,
print spooler. or a print spooler.
Sheet: A sheet is a single instance of a medium, whether printing on Sheet: A sheet is a single instance of a medium, whether printing on
one or both sides of the medium. See "impression" and "page". one or both sides of the medium. See "impression" and "page".
SNMP Information Object: A name, value-pair that specifies an action, SNMP Information Object: A name, value-pair that specifies an
a status, or a condition in an SNMP MIB. Objects are identified in action, a status, or a condition in an SNMP MIB. Objects are
SNMP by an OBJECT IDENTIFIER. identified in SNMP by an OBJECT IDENTIFIER.
Spooler: A server that accepts jobs, spools the data, and decides when Spooler: A server that accepts jobs, spools the data, and decides
and on which printer to print the job. A spooler is a client to a when and on which printer to print the job. A spooler is a client to
printer or a printer supervisor, depending on implementation. a printer or a printer supervisor, depending on implementation.
Spooling: The act of a device or server of (1) accepting jobs and (2) Spooling: The act of a device or server of (1) accepting jobs and
writing the job's attributes and document data on to secondary storage. (2) writing the job's attributes and document data on to secondary
storage.
Stacked: When a media sheet is placed in an output bin of a device. Stacked: When a media sheet is placed in an output bin of a device.
Supervisor: A server that contains a control program that controls a Supervisor: A server that contains a control program that controls a
printer or other device. A supervisor is a client to the printer or printer or other device. A supervisor is a client to the printer or
other device. other device.
System Operator: A user that uses a monitor to monitor the system and System Operator: A user that uses a monitor to monitor the system
carries out tasks to keep the system running. and carries out tasks to keep the system running.
System Administrator: A user that specifies policy for the system. System Administrator: A user that specifies policy for the system.
Two-up: The placement of two pages on one side of a sheet so that each Two-up: The placement of two pages on one side of a sheet so that
side or impressions counts as two pages. See "page" and "sheet". each side or impressions counts as two pages. See "page" and
"sheet".
User: A person that uses a client or a monitor. See "end user". User: A person that uses a client or a monitor. See "end user".
2.1 System Configurations for the Job Monitoring MIB 2.1 System Configurations for the Job Monitoring MIB
This section enumerates the three configurations in 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 section 1.1 entitled "Types of devices are shown as printers. See section 1.1 entitled "Types of
Information in the MIB". Information in the MIB".
The diagram in the Printer MIB[print-mib] entitled: "One Printer's View The diagram in the Printer MIB [print-mib] entitled: "One Printer's
of the Network" is assumed for this MIB as well. Please refer to that View of the Network" is assumed for this MIB as well. Please refer
diagram to aid in understanding the following system configurations. to that diagram to aid in understanding the following system
configurations.
2.1.1 Configuration 1 - client-printer 2.1.1 Configuration 1 - client-printer
In the client-printer configuration 1, the client(s) submit jobs In the client-printer configuration 1, the client(s) submit jobs
directly to the printer, either by some direct connect, or by network directly to the printer, either by some direct connect, or by network
connection. connection.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs
communicating directly with an agent that is part of the printer. The by communicating directly with an agent that is part of the printer.
agent in the printer SHALL keep the job in the Job Monitoring MIB as The agent in the printer SHALL keep the job in the Job Monitoring MIB
long as the job is in the printer, plus a defined time period after the as long as the job is in the printer, plus a defined time period
job enters the completed state in which accounting programs can copy after the job enters the completed state in which accounting programs
out the accounting data from the Job Monitoring MIB. can copy out the accounting 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 2-1 - Configuration 1 - client-printer - agent in the printer Figure 2-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 2-1): relationships (not shown in Figure 2-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.
2.1.2 Configuration 2 - client-server-printer - agent in the server 2.1.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
to an intermediate server by some network connection, not directly to jobs to an intermediate server by some network connection, not
the printer. While configuration 2 is included, the design center for directly to the printer. While configuration 2 is included, the
this MIB is configurations 1 and 3. design center for this MIB is configurations 1 and 3.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs
communicating directly with: by communicating directly with:
A Job Monitoring MIB agent that is part of the server (or a front A Job Monitoring MIB agent that is part of the server (or a front
for the server) 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 configuration 2, at least that the client or monitor are aware. In
this configuration, the agent SHALL return the current values of the this configuration, the agent SHALL return the current values of the
objects in the Job Monitoring MIB both for jobs the server keeps and objects in the Job Monitoring MIB both for jobs the server keeps and
jobs that the server has submitted to the printer. The Job Monitoring jobs that the server has submitted to the printer. The Job
MIB agent obtains the required information from the printer by a method Monitoring MIB agent obtains the required information from the
that is beyond the scope of this document. The agent in the server printer by a method that is beyond the scope of this document. The
SHALL keep the job in the Job Monitoring MIB in the server as long as agent in the server SHALL keep the job in the Job Monitoring MIB in
the job is in the printer, plus a defined time period after the job the server as long as the job is in the printer, plus a defined time
enters the completed state in which accounting programs can copy out period after the job enters the completed state in which accounting
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
# # | # # |
# # | # # |
#=====#=+==v==+ #=====#=+==v==+
| agent | | | agent | |
+-------+ | +-------+ |
| server | | server |
+----+-----+--+ +----+-----+--+
control * | control * |
********** | ********** |
* | * |
+========v====+ | +========v====+ |
| | | | | |
| | | | | |
| PRINTER <---------+ | PRINTER <---------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 2-2 - Configuration 2 - client-server-printer - agent in the Figure 2-2 - Configuration 2 - client-server-printer - agent in the
server 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-2): relationships (not shown in Figure 2-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. 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.
2.1.3 Configuration 3 - client-server-printer - client monitors printer 2.1.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
to an intermediate server by some network connection, not directly to jobs to an intermediate server by some network connection, not
the printer. That server does not contain a Job Monitoring MIB agent. directly to the printer. That server does not contain a Job
Monitoring MIB agent.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs
communicating directly with: by communicating directly with:
1. The server using some undefined protocol to monitor jobs in the 1. The server using some undefined protocol to monitor jobs in
server (that does not contain the Job Monitoring MIB) AND the server (that does not contain the Job Monitoring MIB) AND
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
from the server after submitting the job to the printer usually job from the server after submitting the job to the printer
almost immediately (before the job does much processing, if usually almost immediately (before the job does much
any). processing, if any).
In configuration 3, the agent (in the printer) SHALL keep the values of In configuration 3, the agent (in the printer) SHALL keep the values
the objects in the Job Monitoring MIB that the agent implements updated of the objects in the Job Monitoring MIB that the agent implements
for a job that the server has submitted to the printer. The agent updated for a job that the server has submitted to the printer. The
SHALL obtain information about the jobs submitted to the printer from agent SHALL obtain information about the jobs submitted to the
the server (either in the job submission protocol, in the document printer from the server (either in the job submission protocol, in
data, or by direct query of the server), in order to populate some of the document data, or by direct query of the server), in order to
the objects the Job Monitoring MIB in the printer. The agent in the populate some of the objects the Job Monitoring MIB in the printer.
printer SHALL keep the job in the Job Monitoring MIB as long as the job The agent in the printer SHALL keep the job in the Job Monitoring MIB
is in the Printer, and longer in order to implement the completed state as long as the job is in the Printer, and longer in order to
in which monitoring programs can copy out the accounting data from the implement the completed state in which monitoring programs can copy
Job Monitoring MIB. 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 query +---+---* +---*----+-+ **** non-SNMP query
# * * | ---- job submission # * * | ---- job submission
# * * | # * * |
# * * | # * * |
# *=====v====v==+ # *=====v====v==+
# | | # | |
# | server | # | server |
# | | # | |
# +----#-----+--+ # +----#-----+--+
# optional# | # optional# |
# ########## | # ########## |
# # | # # |
+==+=v===v=+==+ | +==+=v===v=+==+ |
| | agent | | | | | agent | | |
| +-------+ | | | +-------+ | |
| PRINTER <---------+ | PRINTER <---------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 2-3 - Configuration 3 - client-server-printer - client monitors Figure 2-3 - Configuration 3 - client-server-printer - client
printer agent and server monitors 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 2-3): relationships (not shown in Figure 2-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.
3 Managed Object Usage 3 Managed Object Usage
This section describes the usage of the objects in the MIB. This section describes the usage of the objects in the MIB.
3.1 Conformance Considerations 3.1 Conformance Considerations
In order to achieve interoperability between job monitoring In order to achieve interoperability between job monitoring
applications and job monitoring agents, this specification includes the applications and job monitoring agents, this specification includes
conformance requirements for both monitoring applications and agents. the conformance requirements for both monitoring applications and
agents.
3.1.1 Conformance Terminology 3.1.1 Conformance Terminology
This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED This specification uses the verbs: "SHALL", "SHOULD", "MAY", and
NOT" to specify conformance requirements according to RFC 2119 "NEED NOT" to specify conformance requirements according to RFC 2119
[RFC2119] as follows: [RFC2119] as follows:
"SHALL": indicates an action that the subject of the sentence must "SHALL": indicates an action that the subject of the sentence
implement in order to claim conformance to this specification must implement in order to claim conformance to this specification
"MAY": indicates an action that the subject of the sentence does not "MAY": indicates an action that the subject of the sentence does
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 option specification, in other words that action is an implementation
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 of "SHOULD": indicates an action that is recommended for the subject
the sentence to implement, but is not required, in order to claim of the sentence to implement, but is not required, in order to
conformance to this specification. claim conformance to this specification.
3.1.2 Agent Conformance Requirements 3.1.2 Agent Conformance Requirements
A conforming agent: A conforming agent:
1. SHALL implement all MANDATORY groups in this specification. 1. SHALL implement all MANDATORY groups in this specification.
2. SHALL implement any attributes if (1) the server or device 2. SHALL implement any attributes if (1) the server or device
supports the functionality represented by the attribute and (2) supports the functionality represented by the attribute and (2)
the information is available to the agent. the information is available to the agent.
3. SHOULD implement both forms of an attribute if it implements an 3. SHOULD implement both forms of an attribute if it implements an
attribute that permits a choice of INTEGER and OCTET STRING attribute that permits a choice of INTEGER and OCTET STRING
forms, since implementing both forms may help management forms, since implementing both forms may help management
applications by giving them a choice of representations, since applications by giving them a choice of representations, since
the representation are equivalent. See the JmAttributeTypeTC the representation are equivalent. See the JmAttributeTypeTC
textual-convention. textual-convention.
NOTE - This MIB, like the Printer MIB, is written following the subset NOTE - This MIB, like the Printer MIB, is written following the
of SMIv2 that can be supported by SMIv1 and SNMPv1 implementations. subset of SMIv2 that can be supported by SMIv1 and SNMPv1
implementations.
3.1.2.1 MIB II System Group objects 3.1.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
Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is System Group of MIB-II [mib-II], whether the Printer MIB [print-mib]
implemented or not. is implemented or not.
3.1.2.2 MIB II Interface Group objects 3.1.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[mib-II], whether the Printer MIB[print-mib] Interfaces Group of MIB-II [mib-II], whether the Printer MIB [print-
is implemented or not. mib] is implemented or not.
3.1.2.3 Printer MIB objects 3.1.2.3 Printer MIB objects
If the agent is providing access to a device that is a printer, the If the agent is providing access to a device that is a printer, the
agent SHALL implement all of the MANDATORY objects in the Printer agent SHALL implement all of the MANDATORY objects in the Printer MIB
MIB[print-mib] and all the objects in other MIBs that conformance to [print-mib] and all the objects in other MIBs that conformance to the
the Printer MIB requires, such as the Host Resources MIB[hr-mib]. If Printer MIB requires, such as the Host Resources MIB [hr-mib]. If
the agent is providing access to a server that controls one or more the agent is providing access to a server that controls one or more
direct-connect or networked printers, the agent NEED NOT implement the direct-connect or networked printers, the agent NEED NOT implement
Printer MIB and NEED NOT implement the Host Resources MIB. the Printer MIB and NEED NOT implement the Host Resources MIB.
3.1.3 Job Monitoring Application Conformance Requirements 3.1.3 Job Monitoring Application Conformance Requirements
A conforming job monitoring application: A conforming job monitoring application:
1. SHALL accept the full syntactic range for all objects in all 1. SHALL accept the full syntactic range for all objects in all
MANDATORY groups and all MANDATORY attributes that are required MANDATORY groups and all MANDATORY attributes that are
to be implemented by an agent according to Section 3.1.2 and required to be implemented by an agent according to Section
SHALL either present them to the user or ignore them. 3.1.2 and SHALL either present them to the user or ignore
them.
2. SHALL accept the full syntactic range for all attributes, 2. SHALL accept the full syntactic range for all attributes,
including enum and bit values specified in this specification including enum and bit values specified in this specification
and additional ones that may be registered with the PWG and and additional ones that may be registered with the PWG and
SHALL either present them to the user or ignore them. In SHALL either present them to the user or ignore them. In
particular, a conforming job monitoring application SHALL not particular, a conforming job monitoring application SHALL not
malfunction when receiving any standard or registered enum or malfunction when receiving any standard or registered enum or
bit values. See Section 3.7 entitled "IANA and PWG bit values. See Section 3.7 entitled "IANA and PWG
Registration Considerations". Registration Considerations".
3. SHALL NOT fail when operating with agents that materialize 3. SHALL NOT fail when operating with agents that materialize
attributes after the job has been submitted, as opposed to when attributes after the job has been submitted, as opposed to
the job is submitted. when the job is submitted.
4. SHALL, if it supports a time attribute, accept either form of 4. SHALL, if it supports a time attribute, accept either form of
the time attribute, since agents are free to implement either the time attribute, since agents are free to implement either
time form. time form.
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 3.2 The Job Tables and the Oldest Active and Newest Active Indexes
The jmJobTable and jmAttributeTable contain objects and attributes, The jmJobTable and jmAttributeTable contain objects and attributes,
respectively, for each job in a job set. These first two indexes are: respectively, for each job in a job set. These first two indexes
1. jmGeneralJobSetIndex - which job set are:
2. jmJobIndex - which job in the job set 1. jmGeneralJobSetIndex - which job set
2. jmJobIndex - which job in the job set
In order for a monitoring application to quickly find that active jobs In order for a monitoring application to quickly find that active
(jobs in the pending, processing, or processingStopped states), the MIB jobs (jobs in the pending, processing, or processingStopped states),
contains two indexes: the MIB contains two indexes:
1. jmGeneralOldestActiveJobIndex - the index of the active job 1. jmGeneralOldestActiveJobIndex - the index of the active job
that has been in the tables the longest. that has been in the tables the longest.
2. jmGeneralNewestActiveJobIndex - the index of the active job 2. jmGeneralNewestActiveJobIndex - the index of the active job
that has been most recently added to the tables. that has been most recently added to the tables.
The agent SHALL assign the next incremental value of jmJobIndex to the The agent SHALL assign the next incremental value of jmJobIndex to
job, when a new job is accepted by the server or device to which the the job, when a new job is accepted by the server or device to which
agent is providing access. If the incremented value of jmJobIndex the agent is providing access. If the incremented value of
would exceed the implementation-defined maximum value for jmJobIndex, jmJobIndex would exceed the implementation-defined maximum value for
the agent SHALL 'wrap' back to 1. An agent uses the resulting value of jmJobIndex, the agent SHALL 'wrap' back to 1. An agent uses the
jmJobIndex for storing information in the jmJobTable and the resulting value of jmJobIndex for storing information in the
jmAttributeTable about the job. jmJobTable and the jmAttributeTable about the job.
It is recommended that the largest value for jmJobIndex be much larger It is recommended that the largest value for jmJobIndex be much
than the maximum number of jobs that the implementation can contain at larger than the maximum number of jobs that the implementation can
a single time, so as to minimize the premature re-use of a jmJobIndex contain at a single time, so as to minimize the premature re-use of a
value for a newer job while clients retain the same 'stale' value for jmJobIndex value for a newer job while clients retain the same '
an older job. stale' value for an older job.
It is recommended that agents that are providing access to It is recommended that agents that are providing access to
servers/devices that already allocate job-identifiers for jobs as servers/devices that already allocate job-identifiers for jobs as
integers use the same integer value for the jmJobIndex. Then integers use the same integer value for the jmJobIndex. Then
management applications using this MIB and applications using other management applications using this MIB and applications using other
protocols will see the same job identifiers for the same jobs. Agents protocols will see the same job identifiers for the same jobs.
providing access to systems that contain jobs with a job identifier of Agents providing access to systems that contain jobs with a job
0 SHALL map the job identifier value 0 to a jmJobIndex value that is identifier of 0 SHALL map the job identifier value 0 to a jmJobIndex
one higher than the highest job identifier value that any job can have value that is one higher than the highest job identifier value that
on that system. Then only job 0 will have a different job-identifier any job can have on that system. Then only job 0 will have a
value than the job's jmJobIndex value. different job-identifier value than the job's jmJobIndex value.
NOTE - If a server or device accepts jobs using multiple job submission NOTE - If a server or device accepts jobs using multiple job
protocols, it may be difficult for the agent to meet the recommendation submission protocols, it may be difficult for the agent to meet the
to use the job-identifier values that the server or device assigns as recommendation to use the job-identifier values that the server or
the jmJobIndex value, unless the server/device assigns job-identifiers device assigns as the jmJobIndex value, unless the server/device
for each of its job submission protocols from the same job-identifier assigns job-identifiers for each of its job submission protocols from
number space. the same job-identifier number space.
Each time a new job is accepted by the server or device that the agent Each time a new job is accepted by the server or device that the
is providing access to AND that job is to be 'active' (pending, agent is providing access to AND that job is to be 'active' (pending,
processing, or processingStopped, but not pendingHeld), the agent SHALL processing, or processingStopped, but not pendingHeld), the agent
copy the value of the job's jmJobIndex to the SHALL copy the value of the job's jmJobIndex to the
jmGeneralNewestActiveJobIndex object. If the new job is to be jmGeneralNewestActiveJobIndex object. If the new job is to be '
'inactive' (pendingHeld state), the agent SHALL not change the value of inactive' (pendingHeld state), the agent SHALL not change the value
jmGeneralNewestActiveJobIndex object (though the agent SHALL assign the of jmGeneralNewestActiveJobIndex object (though the agent SHALL
next incremental jmJobIndex value to the job). assign the next incremental jmJobIndex value to the job).
When a job transitions from one of the 'active' job states (pending, When a job transitions from one of the 'active' job states (pending,
processing, processingStopped) to one of the 'inactive' job states processing, processingStopped) to one of the 'inactive' job states
(pendingHeld, completed, canceled, or aborted), with a jmJobIndex value (pendingHeld, completed, canceled, or aborted), with a jmJobIndex
that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL value that matches the jmGeneralOldestActiveJobIndex object, the
advance (or wrap) the value to the next oldest 'active' job, if any. agent SHALL advance (or wrap) the value to the next oldest 'active'
See the JmJobStateTC textual-convention for a definition of the job job, if any. See the JmJobStateTC textual-convention for a
states. definition of the job states.
Whenever a job transitions from one of the 'inactive' job states to one Whenever a job transitions from one of the 'inactive' job states to
of the 'active' job states (from pendingHeld to pending or processing), one of the 'active' job states (from pendingHeld to pending or
the agent SHALL update the value of either the processing), the agent SHALL update the value of either the
jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex
objects, or both, if the job's jmJobIndex value is outside the range objects, or both, if the job's jmJobIndex value is outside the range
between jmGeneralOldestActiveJobIndex and between jmGeneralOldestActiveJobIndex and
jmGeneralNewestActiveJobIndex. jmGeneralNewestActiveJobIndex.
When all jobs become 'inactive', i.e., enter the pendingHeld, When all jobs become 'inactive', i.e., enter the pendingHeld,
completed, canceled, or aborted states, the agent SHALL set the value completed, canceled, or aborted states, the agent SHALL set the value
of both the jmGeneralOldestActiveJobIndex and of both the jmGeneralOldestActiveJobIndex and
jmGeneralNewestActiveJobIndex objects to 0. jmGeneralNewestActiveJobIndex objects to 0.
NOTE - Applications that wish to efficiently access all of the active NOTE - Applications that wish to efficiently access all of the active
jobs MAY use jmGeneralOldestActiveJobIndex value to start with the jobs MAY use jmGeneralOldestActiveJobIndex value to start with the
oldest active job and continue until they reach the index value equal oldest active job and continue until they reach the index value equal
to jmGeneralNewestActiveJobIndex, skipping over any pendingHeld, to jmGeneralNewestActiveJobIndex, skipping over any pendingHeld,
completed, canceled, or aborted jobs that might intervene. completed, canceled, or aborted jobs that might intervene.
If an application detects that the jmGeneralNewestActiveJobIndex is If an application detects that the jmGeneralNewestActiveJobIndex is
smaller than jmGeneralOldestActiveJobIndex, the job index has wrapped. smaller than jmGeneralOldestActiveJobIndex, the job index has
In this case, the application SHALL reset the index to 1 when the end wrapped. In this case, the application SHALL reset the index to 1
of the table is reached and continue the GetNext operations to find the when the end of the table is reached and continue the GetNext
rest of the active jobs. operations to find the rest of the active jobs.
NOTE - Applications detect the end of the jmAttributeTable table when NOTE - Applications detect the end of the jmAttributeTable table when
the OID returned by the GetNext operation is an OID in a different MIB. the OID returned by the GetNext operation is an OID in a different
There is no object in this MIB that specifies the maximum value for the MIB. There is no object in this MIB that specifies the maximum value
jmJobIndex supported by the implementation. for the jmJobIndex supported by the implementation.
When the server or device is power-cycled, the agent SHALL remember the When the server or device is power-cycled, the agent SHALL remember
next jmJobIndex value to be assigned, so that new jobs are not assigned the next jmJobIndex value to be assigned, so that new jobs are not
the same jmJobIndex as recent jobs before the power cycle. assigned the same jmJobIndex as recent jobs before the power cycle.
3.3 The Attribute Mechanism and the Attribute Table(s) 3.3 The Attribute Mechanism and the Attribute Table(s)
Attributes are similar to information objects, except that attributes Attributes are similar to information objects, except that attributes
are identified by an enum, instead of an OID, so that attributes may be are identified by an enum, instead of an OID, so that attributes may
registered without requiring a new MIB. Also an implementation that be registered without requiring a new MIB. Also an implementation
does not have the functionality represented by the attribute can omit that does not have the functionality represented by the attribute can
the attribute entirely, rather than having to return a distinguished omit the attribute entirely, rather than having to return a
value. The agent is free to materialize an attribute in the distinguished value. The agent is free to materialize an attribute
jmAttributeTable as soon as the agent is aware of the value of the in the jmAttributeTable as soon as the agent is aware of the value of
attribute. the attribute.
The agent materializes job attributes in a four-indexed The agent materializes job attributes in a four-indexed
jmAttributeTable: jmAttributeTable:
1. jmGeneralJobSetIndex - which job set 1. jmGeneralJobSetIndex - which job set
2. jmJobIndex - which job in the job set 2. jmJobIndex - which job in the job set
3. jmAttributeTypeIndex - which attribute 3. jmAttributeTypeIndex - which attribute
4. jmAttributeInstanceIndex - which attribute instance for those 4. jmAttributeInstanceIndex - which attribute instance for those
attributes that can have multiple values per job. attributes that can have multiple values per job.
Some attributes represent information about a job, such as a file-name, Some attributes represent information about a job, such as a file-
a document-name, a submission-time or a completion time. Other name, a document-name, a submission-time or a completion time. Other
attributes represent resources required, e.g., a medium or a colorant, attributes represent resources required, e.g., a medium or a
etc. to process the job before the job starts processing OR to indicate colorant, etc. to process the job before the job starts processing OR
the amount of the resource consumed during and after processing, e.g., to indicate the amount of the resource consumed during and after
pages completed or impressions completed. If both a required and a processing, e.g., pages completed or impressions completed. If both
consumed value of a resource is needed, this specification assigns two a required and a consumed value of a resource is needed, this
separate attribute enums in the textual convention. specification assigns two separate attribute enums in the textual
convention.
NOTE - The table of contents lists all the attributes in order. This NOTE - The table of contents lists all the attributes in order. This
order is the order of enum assignments which is the order that the SNMP order is the order of enum assignments which is the order that the
GetNext operation returns attributes. Most attributes apply to all SNMP GetNext operation returns attributes. Most attributes apply to
three configurations covered by this MIB specification (see section 2.1 all three configurations covered by this MIB specification (see
entitled "System Configurations for the Job Monitoring MIB"). Those section 2.1 entitled "System Configurations for the Job Monitoring
attributes that apply to a particular configuration are indicated as MIB"). Those attributes that apply to a particular configuration are
'Configuration n:' and SHALL NOT be used with other configurations. indicated as 'Configuration n:' and SHALL NOT be used with other
configurations.
3.3.1 Conformance of Attribute Implementation 3.3.1 Conformance of Attribute Implementation
An agent SHALL implement any attribute if (1) the server or device An agent SHALL implement any attribute if (1) the server or device
supports the functionality represented by the attribute and (2) the supports the functionality represented by the attribute and (2) the
information is available to the agent. The agent MAY create the information is available to the agent. The agent MAY create the
attribute row in the jmAttributeTable when the information is available attribute row in the jmAttributeTable when the information is
or MAY create the row earlier with the designated 'unknown' value available or MAY create the row earlier with the designated 'unknown'
appropriate for that attribute. See next section. value appropriate for that attribute. See next section.
If the server or device does not implement or does not provide access If the server or device does not implement or does not provide access
to the information about an attribute, the agent SHOULD NOT create the to the information about an attribute, the agent SHOULD NOT create
corresponding row in the jmAttributeTable. the corresponding row in the jmAttributeTable.
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes
Some attributes have a 'useful' Integer32 value, some have a 'useful' Some attributes have a 'useful' Integer32 value, some have a 'useful'
OCTET STRING value, some MAY have either or both depending on OCTET STRING value, some MAY have either or both depending on
implementation, and some MUST have both. See the JmAttributeTypeTC implementation, and some MUST have both. See the JmAttributeTypeTC
textual convention for the specification of each attribute. textual convention for the specification of each attribute.
SNMP requires that if an object cannot be implemented because its SNMP requires that if an object cannot be implemented because its
values cannot be accessed, then a compliant agent SHALL return an SNMP values cannot be accessed, then a compliant agent SHALL return an
error in SNMPv1 or an exception value in SNMPv2. However, this MIB has SNMP error in SNMPv1 or an exception value in SNMPv2. However, this
been designed so that 'all' objects can and SHALL be implemented by an MIB has been designed so that 'all' objects can and SHALL be
agent, so that neither the SNMPv1 error nor the SNMPv2 exception value implemented by an agent, so that neither the SNMPv1 error nor the
SHALL be generated by the agent. This MIB has also been designed so SNMPv2 exception value SHALL be generated by the agent. This MIB has
that when an agent materializes an attribute, the agent SHALL also been designed so that when an agent materializes an attribute,
materialize a row consisting of both the jmAttributeValueAsInteger and the agent SHALL materialize a row consisting of both the
jmAttributeValueAsOctets objects. jmAttributeValueAsInteger and jmAttributeValueAsOctets objects.
In general, values for objects and attributes have been chosen so that In general, values for objects and attributes have been chosen so
a management application will be able to determine whether a 'useful', that a management application will be able to determine whether a '
'unknown', or 'other' value is available. When a useful value is not useful', 'unknown', or 'other' value is available. When a useful
available for an object, that agent SHALL return a zero-length string value is not available for an object, that agent SHALL return a
for octet strings, the value 'unknown(2)' for enums, a '0' value for an zero-length string for octet strings, the value 'unknown(2)' for
object that represents an index in another table, and a value '-2' for enums, a '0' value for an object that represents an index in another
counting integers. table, and a value '-2' for counting integers.
Since each attribute is represented by a row consisting of both the Since each attribute is represented by a row consisting of both the
jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY
objects, SNMP requires that the agent SHALL always create an attribute objects, SNMP requires that the agent SHALL always create an
row with both objects specified. However, for most attributes the attribute row with both objects specified. However, for most
agent SHALL return a "useful" value for one of the objects and SHALL attributes the agent SHALL return a "useful" value for one of the
return the 'other' value for the other object. For integer only objects and SHALL return the 'other' value for the other object. For
attributes, the agent SHALL always return a zero-length string value integer only attributes, the agent SHALL always return a zero-length
for the jmAttributeValueAsOctets object. For octet string only string value for the jmAttributeValueAsOctets object. For octet
attributes, the agent SHALL always return a '-1' value for the string only attributes, the agent SHALL always return a '-1' value
jmAttributeValueAsInteger object. for the jmAttributeValueAsInteger object.
3.3.3 Index Value Attributes 3.3.3 Index Value Attributes
A number of attributes are indexes in other tables. Such attribute A number of attributes are indexes in other tables. Such attribute
names end with the word 'Index'. If the agent has not (yet) assigned names end with the word 'Index'. If the agent has not (yet) assigned
an index value for a particular index attribute for a job, the agent an index value for a particular index attribute for a job, the agent
SHALL either: (1) return the value 0 or (2) not add this attribute to SHALL either: (1) return the value 0 or (2) not add this attribute to
the jmAttributeTable until the index value is assigned. In the the jmAttributeTable until the index value is assigned. In the
interests of brevity, the semantics for 0 is specified once here and is interests of brevity, the semantics for 0 is specified once here and
not repeated for each index attribute specification and a DEFVAL of 0 is not repeated for each index attribute specification and a DEFVAL
is implied, even though the DEFVAL for jmAttributeValueAsInteger is -2. of 0 is implied, even though the DEFVAL for jmAttributeValueAsInteger
is -2.
3.3.4 Data Sub-types and Attribute Naming Conventions 3.3.4 Data Sub-types and Attribute Naming Conventions
Many attributes are sub-typed to give a more specific data type than Many attributes are sub-typed to give a more specific data type than
Integer32 or OCTET STRING. The data sub-type of each attribute is Integer32 or OCTET STRING. The data sub-type of each attribute is
indicated on the first line(s) of the description. Some attributes indicated on the first line(s) of the description. Some attributes
have several different data sub-type representations. When an have several different data sub-type representations. When an
attribute has both an Integer32 data sub-type and an OCTET STRING data attribute has both an Integer32 data sub-type and an OCTET STRING
sub-type, the attribute can be represented in a single row in the data sub-type, the attribute can be represented in a single row in
jmAttributeTable. In this case, the data sub-type name is not included the jmAttributeTable. In this case, the data sub-type name is not
as the last part of the name of the attribute, e.g., documentFormat(38) included as the last part of the name of the attribute, e.g.,
which is both an enum and/or a name. When the data sub-types cannot be documentFormat(38) which is both an enum and/or a name. When the
represented by a single row in the jmAttributeTable, each such data sub-types cannot be represented by a single row in the
representation is considered a separate attribute and is assigned a jmAttributeTable, each such representation is considered a separate
separate name and enum value. For these attributes, the name of the attribute and is assigned a separate name and enum value. For these
data sub-type is the last part of the name of the attribute: Name, attributes, the name of the data sub-type is the last part of the
Index, DateAndTime, TimeStamp, etc. For example, name of the attribute: Name, Index, DateAndTime, TimeStamp, etc. For
documentFormatIndex(37) is an index. example, documentFormatIndex(37) is an index.
NOTE: The Table of Contents also lists the data sub-type and/or data NOTE: The Table of Contents also lists the data sub-type and/or data
sub-types of each attribute, using the textual-convention name when sub-types of each attribute, using the textual-convention name when
such is defined. The following abbreviations are used in the Table of such is defined. The following abbreviations are used in the Table
Contents as shown: of Contents as shown:
'Int32(-2..)' Integer32 (-2..2147483647) 'Int32(-2..)' Integer32 (-2..2147483647)
'Int32(0..)' Integer32 (0..2147483647) 'Int32(0..)' Integer32 (0..2147483647)
'Int32(1..)' Integer32 (1..2147483647) 'Int32(1..)' Integer32 (1..2147483647)
'Int32(m..n)' For all other Integer ranges, the lower 'Int32(m..n)' For all other Integer ranges, the lower
and upper bound of the range is and upper bound of the range is
indicated. indicated.
'UTF8String63' JmUTF8StringTC (SIZE(0..63)) 'UTF8String63' JmUTF8StringTC (SIZE(0..63))
'JobString63' JmJobStringTC (SIZE(0..63)) 'JobString63' JmJobStringTC (SIZE(0..63))
'Octets63' OCTET STRING (SIZE(0..63)) 'Octets63' OCTET STRING (SIZE(0..63))
'Octets(m..n)' For all other OCTET STRING ranges, the 'Octets(m..n)' For all other OCTET STRING ranges, the
exact range is indicated. exact range is indicated.
3.3.5 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 3.3.5 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes
Most attributes have only one row per job. However, a few attributes Most attributes have only one row per job. However, a few attributes
can have multiple values per job or even per document, where each value can have multiple values per job or even per document, where each
is a separate row in the jmAttributeTable. Unless indicated with value is a separate row in the jmAttributeTable. Unless indicated
'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent
ensure that each attribute occurs only once in the jmAttributeTable for SHALL ensure that each attribute occurs only once in the
a job. Most of the 'MULTI-ROW' attributes do not allow duplicate jmAttributeTable for a job. Most of the 'MULTI-ROW' attributes do
values, i.e., the agent SHALL ensure that each value occurs only once not allow duplicate values, i.e., the agent SHALL ensure that each
for a job. Only if the specification of the 'MULTI-ROW' attribute also value occurs only once for a job. Only if the specification of the '
says "There is no restriction on the same xxx occurring in multiple MULTI-ROW' attribute also says "There is no restriction on the same
rows" can the agent allow duplicate values to occur for the job. xxx occurring in multiple rows" can the agent allow duplicate values
to occur for the job.
NOTE - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes, NOTE - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes,
such as fileName(34) or documentName(35) which are specified to be such as fileName(34) or documentName(35) which are specified to be '
'per-document' attributes, but are not allowed for 'intensive' 'MULTI- per-document' attributes, but are not allowed for 'intensive' '
ROW' attributes, such as mediumConsumed(171) and documentFormat(38) MULTI-ROW' attributes, such as mediumConsumed(171) and
which are specified to be 'per-job' attributes. documentFormat(38) which are specified to be 'per-job' attributes.
3.3.6 Requested Objects and Attributes 3.3.6 Requested Objects and Attributes
A number of objects and attributes record requirements for the job. A number of objects and attributes record requirements for the job.
Such object and attribute names end with the word 'Requested'. In the Such object and attribute names end with the word 'Requested'. In
interests of brevity, the phrase 'requested' means: (1) requested by the interests of brevity, the phrase 'requested' means: (1) requested
the client (or intervening server) in the job submission protocol and by the client (or intervening server) in the job submission protocol
may also mean (2) embedded in the submitted document data, and/or (3) and may also mean (2) embedded in the submitted document data, and/or
defaulted by the recipient device or server with the same semantics as (3) defaulted by the recipient device or server with the same
if the requester had supplied, depending on implementation. Also if a semantics as if the requester had supplied, depending on
value is supplied by the job submission client, and the server/device implementation. Also if a value is supplied by the job submission
determines a better value, through processing or other means, the agent client, and the server/device determines a better value, through
MAY return that better value for such object and attribute. processing or other means, the agent MAY return that better value for
such object and attribute.
3.3.7 Consumption Attributes 3.3.7 Consumption Attributes
A number of objects and attributes record consumption. Such attribute A number of objects and attributes record consumption. Such
names end with the word 'Completed' or 'Consumed'. If the job has not attribute names end with the word 'Completed' or 'Consumed'. If the
yet consumed what that resource is metering, the agent either: (1) job has not yet consumed what that resource is metering, the agent
SHALL return the value 0 or (2) SHALL not add this attribute to the either: (1) SHALL return the value 0 or (2) SHALL not add this
jmAttributeTable until the consumption begins. In the interests of attribute to the jmAttributeTable until the consumption begins. In
brevity, the semantics for 0 is specified once here and is not repeated the interests of brevity, the semantics for 0 is specified once here
for each consumption attribute specification and a DEFVAL of 0 is and is not repeated for each consumption attribute specification and
implied, even though the DEFVAL for jmAttributeValueAsInteger is -2. a DEFVAL of 0 is implied, even though the DEFVAL for
jmAttributeValueAsInteger is -2.
3.3.8 Attribute Specifications 3.3.8 Attribute Specifications
This section specifies the job attributes. This section specifies the job attributes.
In the following definitions of the attributes, each description
indicates whether the useful value of the attribute SHALL be
represented using the jmAttributeValueAsInteger or the
jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' or
'OCTETS:', respectively.
Some attributes allow the agent implementer a choice of useful values In the following definitions of the attributes, each description
of either an integer, an octet string representation, or both, indicates whether the useful value of the attribute SHALL be
depending on implementation. These attributes are indicated with represented using the jmAttributeValueAsInteger or the
'INTEGER:' AND/OR 'OCTETS:' tags. jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' or '
OCTETS:', respectively.
A very few attributes require both objects at the same time to Some attributes allow the agent implementer a choice of useful values
represent a pair of useful values (see mediumConsumed(171)). These of either an integer, an octet string representation, or both,
attributes are indicated with 'INTEGER:' AND 'OCTETS:' tags. See the depending on implementation. These attributes are indicated with '
jmAttributeGroup for the descriptions of these two MANDATORY objects. INTEGER:' AND/OR 'OCTETS:' tags.
NOTE - The enum assignments are grouped logically with values assigned A very few attributes require both objects at the same time to
in groups of 20, so that additional values may be registered in the represent a pair of useful values (see mediumConsumed(171)). These
future and assigned a value that is part of their logical grouping. attributes are indicated with 'INTEGER:' AND 'OCTETS:' tags. See the
jmAttributeGroup for the descriptions of these two MANDATORY objects.
Values in the range 2**30 to 2**31-1 are reserved for private or NOTE - The enum assignments are grouped logically with values
experimental usage. This range corresponds to the same range reserved assigned in groups of 20, so that additional values may be registered
in IPP. Implementers are warned that use of such values may conflict in the future and assigned a value that is part of their logical
with other implementations. Implementers are encouraged to request grouping.
registration of enum values following the procedures in Section 3.7.1.
NOTE: No attribute name exceeds 31 characters. Values in the range 2**30 to 2**31-1 are reserved for private or
experimental usage. This range corresponds to the same range
reserved in IPP. Implementers are warned that use of such values may
conflict with other implementations. Implementers are encouraged to
request registration of enum values following the procedures in
Section 3.7.1.
The standard attribute types are: NOTE: No attribute name exceeds 31 characters.
jmAttributeTypeIndex Datatype The standard attribute types are:
-------------------- --------
other(1), Integer32 (-2..2147483647) jmAttributeTypeIndex Datatype
AND/OR -------------------- --------
OCTET STRING(SIZE(0..63))
INTEGER: and/or OCTETS: An attribute that is not in the
list and/or that has not been approved and registered with
the PWG.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ other(1), Integer32 (-2..2147483647)
+ Job State attributes (3 - 19 decimal) AND/OR
+ OCTET STRING(SIZE(0..63))
+ The following attributes specify the state of a job. INTEGER: and/or OCTETS: An attribute that is not in the
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ list and/or that has not been approved and registered with
the PWG.
jobStateReasons2(3), JmJobStateReasons2TC +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: Additional information about the job's current + Job State attributes (3 - 19 decimal)
state that augments the jmJobState object. See the +
description under the JmJobStateReasons1TC textual- + The following attributes specify the state of a job.
convention. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobStateReasons3(4), JmJobStateReasons3TC jobStateReasons2(3), JmJobStateReasons2TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current state
state that augments the jmJobState object. See the that augments the jmJobState object. See the description under
description under JmJobStateReasons1TC textual-convention. the JmJobStateReasons1TC textual-convention.
jobStateReasons4(5), JmJobStateReasons4TC jobStateReasons3(4), JmJobStateReasons3TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current state
state that augments the jmJobState object. See the that augments the jmJobState object. See the description under
description under JmJobStateReasons1TC textual-convention. JmJobStateReasons1TC textual-convention.
processingMessage(6), JmUTF8StringTC (SIZE(0..63)) jobStateReasons4(5), JmJobStateReasons4TC
OCTETS: MULTI-ROW: A coded character set message that is INTEGER: Additional information about the job's current state
generated by the server or device during the processing of that augments the jmJobState object. See the description under
the job as a simple form of processing log to show progress JmJobStateReasons1TC textual-convention.
and any problems. The natural language of each value is
specified by the corresponding
processingMessageNaturalLangTag(7) value.
NOTE - This attribute is intended for such conditions as processingMessage(6), JmUTF8StringTC (SIZE(0..63))
interpreter messages, rather than being the printable form OCTETS: MULTI-ROW: A coded character set message that is
of the jmJobState and jmJobStateReasons1 objects and generated by the server or device during the processing of the
jobStateReasons2, jobStateReasons3, and jobStateReasons4 job as a simple form of processing log to show progress and any
attributes. In order to produce a localized printable form problems. The natural language of each value is specified by
of these job state objects/attribute, a management the corresponding processingMessageNaturalLangTag(7) value.
application SHOULD produce a message from their enum and
bit values.
NOTE - There is no job description attribute in IPP/1.0 NOTE - This attribute is intended for such conditions as
that corresponds to this attribute and this attribute does interpreter messages, rather than being the printable form of
not correspond to the IPP/1.0 'job-state-message' job the jmJobState and jmJobStateReasons1 objects and
description attribute, which is just a printable form of jobStateReasons2, jobStateReasons3, and jobStateReasons4
the IPP 'job-state' and 'job-state-reasons' job attributes. attributes. In order to produce a localized printable form of
these job state objects/attribute, a management application
SHOULD produce a message from their enum and bit values.
There is no restriction for the same message occurring in NOTE - There is no job description attribute in IPP/1.0 that
multiple rows. corresponds to this attribute and this attribute does not
correspond to the IPP/1.0 'job-state-message' job description
attribute, which is just a printable form of the IPP 'job-state'
and 'job-state-reasons' job attributes.
processingMessageNaturalLangTag(7), OCTET STRING(SIZE(0..63)) There is no restriction for the same message occurring in
OCTETS: MULTI-ROW: The natural language of the multiple rows.
corresponding processingMessage(6) attribute value. See
section 3.6.1, entitled 'Text generated by the server or
device'.
If the agent does not know the natural language of the job processingMessageNaturalLangTag(7), OCTET STRING(SIZE(0..63))
processing message, the agent SHALL either (1) return a OCTETS: MULTI-ROW: The natural language of the corresponding
zero length string value for the processingMessage(6) attribute value. See section 3.6.1,
processingMessageNaturalLangTag(7) attribute or (2) not entitled 'Text generated by the server or device'.
return the processingMessageNaturalLangTag(7) attribute for
the job.
There is no restriction for the same tag occurring in If the agent does not know the natural language of the job
multiple rows, since when this attribute is implemented, it processing message, the agent SHALL either (1) return a zero
SHOULD have a value row for each corresponding length string value for the processingMessageNaturalLangTag(7)
processingMessage(6) attribute value row. attribute or (2) not return the
processingMessageNaturalLangTag(7) attribute for the job.
jobCodedCharSet(8), CodedCharSet There is no restriction for the same tag occurring in multiple
INTEGER: The MIBenum identifier of the coded character set rows, since when this attribute is implemented, it SHOULD have a
that the agent is using to represent coded character set value row for each corresponding processingMessage(6) attribute
objects and attributes of type 'JmJobStringTC'. These value row.
coded character set objects and attributes are either: (1)
supplied by the job submitting client or (2) defaulted by
the server or device when omitted by the job submitting
client. The agent SHALL represent these objects and
attributes in the MIB either (1) in the coded character set
as they were submitted or (2) MAY convert the coded
character set to another coded character set or encoding
scheme as identified by the jobCodedCharSet(8) attribute.
See section 3.6.2, entitled 'Text supplied by the job
submitter'.
These MIBenum values are assigned by IANA [IANA-charsets] jobCodedCharSet(8), CodedCharSet
when the coded character sets are registered. The coded INTEGER: The MIBenum identifier of the coded character set that
character set SHALL be one of the ones registered with IANA the agent is using to represent coded character set objects and
[IANA] and the enum value uses the CodedCharSet textual- attributes of type 'JmJobStringTC'. These coded character set
convention from the Printer MIB. See the JmJobStringTC objects and attributes are either: (1) supplied by the job
textual-convention. submitting client or (2) defaulted by the server or device when
omitted by the job submitting client. The agent SHALL represent
these objects and attributes in the MIB either (1) in the coded
character set as they were submitted or (2) MAY convert the
coded character set to another coded character set or encoding
scheme as identified by the jobCodedCharSet(8) attribute. See
section 3.6.2, entitled 'Text supplied by the job submitter'.
If the agent does not know what coded character set was These MIBenum values are assigned by IANA [IANA-charsets] when
used by the job submitting client, the agent SHALL either the coded character sets are registered. The coded character
(1) return the 'unknown(2)' value for the set SHALL be one of the ones registered with IANA [IANA] and the
jobCodedCharSet(8) attribute or (2) not return the enum value uses the CodedCharSet textual-convention from the
jobCodedCharSet(8) attribute for the job. Printer MIB. See the JmJobStringTC textual-convention.
jobNaturalLanguageTag(9), OCTET STRING(SIZE(0..63)) If the agent does not know what coded character set was used by
OCTETS: The natural language of the job attributes supplied the job submitting client, the agent SHALL either (1) return the
by the job submitter or defaulted by the server or device 'unknown(2)' value for the jobCodedCharSet(8) attribute or (2)
for the job, i.e., all objects and attributes represented not return the jobCodedCharSet(8) attribute for the job.
by the 'JmJobStringTC' textual-convention, such as jobName,
mediumRequested, etc. See Section 3.6.2, entitled 'Text
supplied by the job submitter'.
If the agent does not know what natural language was used jobNaturalLanguageTag(9), OCTET STRING(SIZE(0..63))
by the job submitting client, the agent SHALL either (1) OCTETS: The natural language of the job attributes supplied by
return a zero length string value for the the job submitter or defaulted by the server or device for the
jobNaturalLanguageTag(9) attribute or (2) not return job, i.e., all objects and attributes represented by the '
jobNaturalLanguageTag(9) attribute for the job. JmJobStringTC' textual-convention, such as jobName,
mediumRequested, etc. See Section 3.6.2, entitled 'Text
supplied by the job submitter'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ If the agent does not know what natural language was used by the
+ Job Identification attributes (20 - 49 decimal) job submitting client, the agent SHALL either (1) return a zero
+ length string value for the jobNaturalLanguageTag(9) attribute
+ The following attributes help an end user, a system or (2) not return jobNaturalLanguageTag(9) attribute for the
+ operator, or an accounting program identify a job. job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobURI(20), OCTET STRING(SIZE(0..63)) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
OCTETS: MULTI-ROW: The job's Universal Resource + Job Identification attributes (20 - 49 decimal)
Identifier (URI) [RFC1738]. See IPP [ipp-model] for +
example usage. + The following attributes help an end user, a system
+ operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTE - The agent may be able to generate this value on each jobURI(20), OCTET STRING(SIZE(0..63))
SNMP Get operation from smaller values, rather than having OCTETS: MULTI-ROW: The job's Universal Resource
to store the entire URI. Identifier (URI) [RFC1738]. See IPP [ipp-model] for
example usage.
If the URI exceeds 63 octets, the agent SHALL use multiple NOTE - The agent may be able to generate this value on each
values, with the next 63 octets coming in the second value, SNMP Get operation from smaller values, rather than having
etc. to store the entire URI.
NOTE - IPP [ipp-model] has a 1023-octet maximum length for If the URI exceeds 63 octets, the agent SHALL use multiple
a URI, though the URI standard itself and HTTP/1.1 specify values, with the next 63 octets coming in the second value,
no maximum length. etc.
jobAccountName(21), OCTET STRING(SIZE(0..63)) NOTE - IPP [ipp-model] has a 1023-octet maximum length for
OCTETS: Arbitrary binary information which MAY be coded a URI, though the URI standard itself and HTTP/1.1 specify
character set data or encrypted data supplied by the no maximum length.
submitting user for use by accounting services to allocate
or categorize charges for services provided, such as a
customer account name or number.
NOTE: This attribute NEED NOT be printable characters. 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 or number.
serverAssignedJobName(22), JmJobStringTC (SIZE(0..63)) NOTE: This attribute NEED NOT be printable characters.
OCTETS: Configuration 3 only: The human readable string
name, number, or ID of the job as assigned by the server
that submitted the job to the device that the agent is
providing access to with this MIB.
NOTE - This attribute is intended for enabling a user to serverAssignedJobName(22), JmJobStringTC (SIZE(0..63))
find his/her job that a server submitted to a device when OCTETS: Configuration 3 only: The human readable string
either the client does not support the jmJobSubmissionID or name, number, or ID of the job as assigned by the server
the server does not pass the jmJobSubmissionID through to that submitted the job to the device that the agent is
the device. providing access to with this MIB.
jobName(23), JmJobStringTC (SIZE(0..63)) NOTE - This attribute is intended for enabling a user to
OCTETS: The human readable string name of the job as find his/her job that a server submitted to a device when
assigned by the submitting user to help the user either the client does not support the jmJobSubmissionID or
distinguish between his/her various jobs. This name does the server does not pass the jmJobSubmissionID through to
not need to be unique. the device.
This attribute is intended for enabling a user or the jobName(23), JmJobStringTC (SIZE(0..63))
user's application to convey a job name that MAY be printed OCTETS: The human readable string name of the job as
on a start sheet, returned in a query result, or used in assigned by the submitting user to help the user
notification or logging messages. distinguish between his/her various jobs. This name does
not need to be unique.
In order to assist users to find their jobs for job This attribute is intended for enabling a user or the
submission protocols that don't supply a jmJobSubmissionID, user's application to convey a job name that MAY be printed
the agent SHOULD maintain the jobName attribute for the on a start sheet, returned in a query result, or used in
time specified by the jmGeneralJobPersistence object, notification or logging messages.
rather than the (shorter) jmGeneralAttributePersistence
object.
If this attribute is not specified when the job is In order to assist users to find their jobs for job
submitted, no job name is assumed, but implementation submission protocols that don't supply a jmJobSubmissionID,
specific defaults are allowed, such as the value of the the agent SHOULD maintain the jobName attribute for the
documentName attribute of the first document in the job or time specified by the jmGeneralJobPersistence object,
the fileName attribute of the first document in the job. rather than the (shorter) jmGeneralAttributePersistence
object.
The jobName attribute is distinguished from the jobComment If this attribute is not specified when the job is
attribute, in that the jobName attribute is intended to submitted, no job name is assumed, but implementation
permit the submitting user to distinguish between different specific defaults are allowed, such as the value of the
jobs that he/she has submitted. The jobComment attribute documentName attribute of the first document in the job or
is intended to be free form additional information that a the fileName attribute of the first document in the job.
user might wish to use to communicate with himself/herself,
such as a reminder of what to do with the results or to
indicate a different set of input parameters were tried in
several different job submissions.
jobServiceTypes(24), JmJobServiceTypesTC The jobName attribute is distinguished from the jobComment
INTEGER: Specifies the type(s) of service to which the job attribute, in that the jobName attribute is intended to
has been submitted (print, fax, scan, etc.). The service permit the submitting user to distinguish between different
type is bit encoded with each job service type so that more jobs that he/she has submitted. The jobComment attribute
general and arbitrary services can be created, such as is intended to be free form additional information that a
services with more than one destination type, or ones with user might wish to use to communicate with himself/herself,
only a source or only a destination. For example, a job such as a reminder of what to do with the results or to
service might scan, faxOut, and print a single job. In indicate a different set of input parameters were tried in
this case, three bits would be set in the jobServiceTypes several different job submissions.
attribute, corresponding to the hexadecimal values: 0x8 +
0x20 + 0x4, respectively, yielding: 0x2C.
Whether this attribute is set from a job attribute supplied jobServiceTypes(24), JmJobServiceTypesTC
by the job submission client or is set by the recipient job INTEGER: Specifies the type(s) of service to which the job
submission server or device depends on the job submission has been submitted (print, fax, scan, etc.). The service
protocol. This attribute SHALL be implemented if the type is bit encoded with each job service type so that more
server or device has other types in addition to or instead general and arbitrary services can be created, such as
of printing. services with more than one destination type, or ones with
only a source or only a destination. For example, a job
service might scan, faxOut, and print a single job. In
this case, three bits would be set in the jobServiceTypes
attribute, corresponding to the hexadecimal values: 0x8 +
0x20 + 0x4, respectively, yielding: 0x2C.
One of the purposes of this attribute is to permit a Whether this attribute is set from a job attribute supplied
requester to filter out jobs that are not of interest. For by the job submission client or is set by the recipient job
example, a printer operator may only be interested in jobs submission server or device depends on the job submission
that include printing. protocol. This attribute SHALL be implemented if the
server or device has other types in addition to or instead
of printing.
jobSourceChannelIndex(25), Integer32 (0..2147483647) One of the purposes of this attribute is to permit a
INTEGER: The index of the row in the associated Printer requester to filter out jobs that are not of interest. For
MIB[print-mib] of the channel which is the source of the example, a printer operator may only be interested in jobs
print job. that include printing.
jobSourcePlatformType(26), JmJobSourcePlatformTypeTC jobSourceChannelIndex(25), Integer32 (0..2147483647)
INTEGER: The source platform type of the immediate INTEGER: The index of the row in the associated Printer
upstream submitter that submitted the job to the server MIB [print-mib] of the channel which is the source of the
(configuration 2) or device (configuration 1 and 3) to print job.
which the agent is providing access. For configuration 1,
this is the type of the client that submitted the job to
the device; for configuration 2, this is the type of the
client that submitted the job to the server; and for
configuration 3, this is the type of the server that
submitted the job to the device.
submittingServerName(27), JmJobStringTC (SIZE(0..63)) jobSourcePlatformType(26), JmJobSourcePlatformTypeTC
OCTETS: For configuration 3 only: The administrative name INTEGER: The source platform type of the immediate
of the server that submitted the job to the device. upstream submitter that submitted the job to the server
(configuration 2) or device (configuration 1 and 3) to
which the agent is providing access. For configuration 1,
this is the type of the client that submitted the job to
the device; for configuration 2, this is the type of the
client that submitted the job to the server; and for
configuration 3, this is the type of the server that
submitted the job to the device.
submittingApplicationName(28), JmJobStringTC (SIZE(0..63)) submittingServerName(27), JmJobStringTC (SIZE(0..63))
OCTETS: The name of the client application (not the server OCTETS: For configuration 3 only: The administrative name
in configuration 3) that submitted the job to the server or of the server that submitted the job to the device.
device.
jobOriginatingHost(29), JmJobStringTC (SIZE(0..63)) submittingApplicationName(28), JmJobStringTC (SIZE(0..63))
OCTETS: The name of the client host (not the server host OCTETS: The name of the client application (not the server
name in configuration 3) that submitted the job to the in configuration 3) that submitted the job to the server or
server or device. device.
deviceNameRequested(30), JmJobStringTC (SIZE(0..63)) jobOriginatingHost(29), JmJobStringTC (SIZE(0..63))
OCTETS: The administratively defined coded character set OCTETS: The name of the client host (not the server host
name of the target device requested by the submitting user. name in configuration 3) that submitted the job to the
For configuration 1, its value corresponds to the Printer server or device.
MIB[print-mib]: prtGeneralPrinterName object. For
configuration 2 and 3, its value is the name of the logical
or physical device that the user supplied to indicate to
the server on which device(s) they wanted the job to be
processed.
queueNameRequested(31), JmJobStringTC (SIZE(0..63)) deviceNameRequested(30), JmJobStringTC (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 user. name of the target device requested by the submitting user.
For configuration 1, its value corresponds to the queue in For configuration 1, its value corresponds to the Printer
the device for which the agent is providing access. For MIB [print-mib]: prtGeneralPrinterName object. For
configuration 2 and 3, its value is the name of the queue configuration 2 and 3, its value is the name of the logical
that the user supplied to indicate to the server on which or physical device that the user supplied to indicate to
device(s) they wanted the job to be processed. the server on which device(s) they wanted the job to be
processed.
NOTE - typically an implementation SHOULD support either queueNameRequested(31), JmJobStringTC (SIZE(0..63))
the deviceNameRequested or queueNameRequested attribute, OCTETS: The administratively defined coded character set
but not both. name of the target queue requested by the submitting user.
For configuration 1, its value corresponds to the queue in
the device for which the agent is providing access. For
configuration 2 and 3, its value is the name of the queue
that the user supplied to indicate to the server on which
device(s) they wanted the job to be processed.
physicalDevice(32), hrDeviceIndex NOTE - typically an implementation SHOULD support either
AND/OR the deviceNameRequested or queueNameRequested attribute,
JmUTF8StringTC (SIZE(0..63)) but not both.
INTEGER: MULTI-ROW: The index of the physical device MIB
instance requested/used, such as the Printer MIB[print-
mib]. This value is an hrDeviceIndex value. See the Host
Resources MIB[hr-mib].
AND/OR physicalDevice(32), hrDeviceIndex
AND/OR
JmUTF8StringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The index of the physical device MIB
instance requested/used, such as the Printer MIB [print-mib].
This value is an hrDeviceIndex value. See the Host
Resources MIB [hr-mib].
OCTETS: MULTI-ROW: The name of the physical device to AND/OR
which the job is assigned.
numberOfDocuments(33), Integer32 (-2..2147483647) OCTETS: MULTI-ROW: The name of the physical device to
INTEGER: The number of documents in this job. which the job is assigned.
The agent SHOULD return this attribute if the job has more numberOfDocuments(33), Integer32 (-2..2147483647)
than one document. INTEGER: The number of documents in this job.
fileName(34), JmJobStringTC (SIZE(0..63)) The agent SHOULD return this attribute if the job has more
OCTETS: MULTI-ROW: The coded character set file name or than one document.
URI[URI-spec] of the document.
There is no restriction on the same file name occurring in fileName(34), JmJobStringTC (SIZE(0..63))
multiple rows. OCTETS: MULTI-ROW: The coded character set file name or
URI [URI-spec] of the document.
documentName(35), JmJobStringTC (SIZE(0..63)) There is no restriction on the same file name occurring in
OCTETS: MULTI-ROW: The coded character set name of the multiple rows.
document.
There is no restriction on the same document name occurring documentName(35), JmJobStringTC (SIZE(0..63))
in multiple rows. OCTETS: MULTI-ROW: The coded character set name of the
document.
jobComment(36), JmJobStringTC (SIZE(0..63)) There is no restriction on the same document name occurring
OCTETS: An arbitrary human-readable coded character text in multiple rows.
string supplied by the submitting user or the job
submitting application program for any purpose. For
example, a user might indicate what he/she is going to do
with the printed output or the job submitting application
program might indicate how the document was produced.
The jobComment attribute is not intended to be a name; see jobComment(36), JmJobStringTC (SIZE(0..63))
the jobName attribute. OCTETS: An arbitrary human-readable coded character text
string supplied by the submitting user or the job
submitting application program for any purpose. For
example, a user might indicate what he/she is going to do
with the printed output or the job submitting application
program might indicate how the document was produced.
documentFormatIndex(37), Integer32 (0..2147483647) The jobComment attribute is not intended to be a name; see
INTEGER: MULTI-ROW: The index in the prtInterpreterTable the jobName attribute.
in the Printer MIB[print-mib] of the page description
language (PDL) or control language interpreter that this
job requires/uses. A document or a job MAY use more than
one PDL or control language.
NOTE - As with all intensive attributes where multiple rows documentFormatIndex(37), Integer32 (0..2147483647)
are allowed, there SHALL be only one distinct row for each INTEGER: MULTI-ROW: The index in the prtInterpreterTable
distinct interpreter; there SHALL be no duplicates. in the Printer MIB [print-mib] of the page description
language (PDL) or control language interpreter that this
job requires/uses. A document or a job MAY use more than
one PDL or control language.
NOTE - This attribute type is intended to be used with an NOTE - As with all intensive attributes where multiple rows
agent that implements the Printer MIB and SHALL not be used are allowed, there SHALL be only one distinct row for each
if the agent does not implement the Printer MIB. Such an distinct interpreter; there SHALL be no duplicates.
agent SHALL use the documentFormat attribute instead.
documentFormat(38), PrtInterpreterLangFamilyTC NOTE - This attribute type is intended to be used with an
AND/OR agent that implements the Printer MIB and SHALL not be used
OCTET STRING(SIZE(0..63)) if the agent does not implement the Printer MIB. Such an
INTEGER: MULTI-ROW: The interpreter language family agent SHALL use the documentFormat attribute instead.
corresponding to the Printer MIB[print-mib]
prtInterpreterLangFamily object, that this job
requires/uses. A document or a job MAY use more than one
PDL or control language.
AND/OR documentFormat(38), PrtInterpreterLangFamilyTC
AND/OR
OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The interpreter language family
corresponding to the Printer MIB [print-mib]
prtInterpreterLangFamily object, that this job
requires/uses. A document or a job MAY use more than one
PDL or control language.
OCTETS: MULTI-ROW: The document format registered as a AND/OR
media type[iana-media-types], i.e., the name of the MIME
content-type/subtype. Examples: 'application/postscript',
'application/vnd.hp-PCL', 'application/pdf', 'text/plain'
(US-ASCII SHALL be assumed), 'text/plain; charset=iso-8859-
1', and 'application/octet-stream'. The IPP 'document-
format' job attribute uses these same values with the same
semantics. See the IPP [ipp-model] 'mimeMediaType'
attribute syntax and the document-format attribute for
further examples and explanation.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ OCTETS: MULTI-ROW: The document format registered as a
+ Job Parameter attributes (50 - 67 decimal) media type [iana-media-types], i.e., the name of the MIME
+ content-type/subtype. Examples: 'application/postscript',
+ The following attributes represent input parameters 'application/vnd.hp-PCL', 'application/pdf', 'text/plain'
+ supplied by the submitting client in the job submission (US-ASCII SHALL be assumed), 'text/plain; charset=iso-8859-1',
+ protocol. and 'application/octet-stream'. The IPP 'document-format'
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ job attribute uses these same values with the same semantics.
See the IPP [ipp-model] 'mimeMediaType' attribute syntax and
the document-format attribute for further examples and
explanation.
jobPriority(50), Integer32 (-2..100) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: The priority for scheduling the job. It is used + Job Parameter attributes (50 - 67 decimal)
by servers and devices that employ a priority-based +
scheduling algorithm. + The following attributes represent input parameters
+ supplied by the submitting client in the job submission
+ protocol.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A higher value specifies a higher priority. The value 1 is jobPriority(50), Integer32 (-2..100)
defined to indicate the lowest possible priority (a job INTEGER: The priority for scheduling the job. It is used by
which a priority-based scheduling algorithm SHALL pass over servers and devices that employ a priority-based scheduling
in favor of higher priority jobs). The value 100 is algorithm.
defined to indicate the highest possible priority.
Priority is expected to be evenly or 'normally' distributed
across this range. The mapping of vendor-defined priority
over this range is implementation-specific. -2 indicates
unknown.
jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC) A higher value specifies a higher priority. The value 1 is
OCTETS: The calendar date and time of day after which the defined to indicate the lowest possible priority (a job which a
job SHALL become a candidate to be scheduled for priority-based scheduling algorithm SHALL pass over in favor of
processing. If the value of this attribute is in the higher priority jobs). The value 100 is defined to indicate the
future, the server SHALL set the value of the job's highest possible priority. Priority is expected to be evenly or
jmJobState object to pendingHeld and add the 'normally' distributed across this range. The mapping of
jobProcessAfterSpecified bit value to the job's vendor-defined priority over this range is implementation-
jmJobStateReasons1 object. When the specified date and specific. -2 indicates unknown.
time arrives, the server SHALL remove the
jobProcessAfterSpecified bit value from the job's
jmJobStateReasons1 object and, if no other reasons remain,
SHALL change the job's jmJobState object to pending.
jobHold(52), JmBooleanTC jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC)
INTEGER: If the value is 'true(4)', a client has OCTETS: The calendar date and time of day after which the job
explicitly specified that the job is to be held until SHALL become a candidate to be scheduled for processing. If the
explicitly released. Until the job is explicitly released value of this attribute is in the future, the server SHALL set
by a client, the job SHALL be in the pendingHeld state with the value of the job's jmJobState object to pendingHeld and add
the jobHoldSpecified value in the jmJobStateReasons1 the jobProcessAfterSpecified bit value to the job's
attribute. jmJobStateReasons1 object. When the specified date and time
arrives, the server SHALL remove the jobProcessAfterSpecified
bit value from the job's jmJobStateReasons1 object and, if no
other reasons remain, SHALL change the job's jmJobState object
to pending.
jobHoldUntil(53), JmJobStringTC (SIZE(0..63)) jobHold(52), JmBooleanTC
OCTETS: The named time period during which the job SHALL INTEGER: If the value is 'true(4)', a client has explicitly
become a candidate for processing, such as 'evening', specified that the job is to be held until explicitly released.
'night', 'weekend', 'second-shift', 'third-shift', etc., Until the job is explicitly released by a client, the job SHALL
(supported values configured by the system administrator). be in the pendingHeld state with the jobHoldSpecified value in
See IPP [ipp-model] for the standard keyword values. Until the jmJobStateReasons1 attribute.
that time period arrives, the job SHALL be in the
pendingHeld state with the jobHoldUntilSpecified value in
the jmJobStateReasons1 object. The value 'no-hold' SHALL
indicate explicitly that no time period has been specified;
the absence of this attribute SHALL indicate implicitly
that no time period has been specified.
outputBin(54), Integer32 (0..2147483647) jobHoldUntil(53), JmJobStringTC (SIZE(0..63))
AND/OR OCTETS: The named time period during which the job SHALL become
JmJobStringTC (SIZE(0..63)) a candidate for processing, such as 'evening', 'night', '
INTEGER: MULTI-ROW: The output subunit index in the weekend', 'second-shift', 'third-shift', etc., (supported values
Printer MIB[print-mib] configured by the system administrator). See IPP [ipp-model]
for the standard keyword values. Until that time period
arrives, the job SHALL be in the pendingHeld state with the
jobHoldUntilSpecified value in the jmJobStateReasons1 object.
The value 'no-hold' SHALL indicate explicitly that no time
period has been specified; the absence of this attribute SHALL
indicate implicitly that no time period has been specified.
AND/OR outputBin(54), Integer32 (0..2147483647)
AND/OR
JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The output subunit index in the Printer
MIB [print-mib]
OCTETS: MULTI-ROW: the name or number (represented as AND/OR
ASCII digits) of the output bin to which all or part of the
job is placed in.
sides(55), Integer32 (-2..2) OCTETS: MULTI-ROW: the name or number (represented as ASCII
INTEGER: MULTI-ROW: The number of sides, '1' or '2', that digits) of the output bin to which all or part of the job is
any document in this job requires/used. placed in.
finishing(56), JmFinishingTC sides(55), Integer32 (-2..2)
INTEGER: MULTI-ROW: Type of finishing that any document INTEGER: MULTI-ROW: The number of sides, '1' or '2', that any
in this job requires/used. document in this job requires/used.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ finishing(56), JmFinishingTC
+ Image Quality attributes (requested and consumed) (70 - 87) INTEGER: MULTI-ROW: Type of finishing that any document in
+ this job requires/used.
+ For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityRequested(70), JmPrintQualityTC +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: MULTI-ROW: The print quality selection requested + Image Quality attributes (requested and consumed) (70 - 87)
for a document in the job for printers that allow quality +
differentiation. + For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityUsed(71), JmPrintQualityTC printQualityRequested(70), JmPrintQualityTC
INTEGER: MULTI-ROW: The print quality selection actually INTEGER: MULTI-ROW: The print quality selection requested for
used by a document in the job for printers that allow a document in the job for printers that allow quality
quality differentiation. differentiation.
printerResolutionRequested(72), JmPrinterResolutionTC printQualityUsed(71), JmPrintQualityTC
OCTETS: MULTI-ROW: The printer resolution requested for a INTEGER: MULTI-ROW: The print quality selection actually used
document in the job for printers that support resolution by a document in the job for printers that allow quality
selection. differentiation.
printerResolutionUsed(73), JmPrinterResolutionTC printerResolutionRequested(72), JmPrinterResolutionTC
OCTETS: MULTI-ROW: The printer resolution actually used OCTETS: MULTI-ROW: The printer resolution requested for a
by a document in the job for printers that support document in the job for printers that support resolution
resolution selection. selection.
tonerEcomonyRequested(74), JmTonerEconomyTC printerResolutionUsed(73), JmPrinterResolutionTC
INTEGER: MULTI-ROW: The toner economy selection requested OCTETS: MULTI-ROW: The printer resolution actually used by a
for documents in the job for printers that allow toner document in the job for printers that support resolution
economy differentiation. selection.
tonerEcomonyUsed(75), JmTonerEconomyTC tonerEcomonyRequested(74), JmTonerEconomyTC
INTEGER: MULTI-ROW: The toner economy selection actually INTEGER: MULTI-ROW: The toner economy selection requested for
used by documents in the job for printers that allow toner documents in the job for printers that allow toner economy
economy differentiation. differentiation.
tonerDensityRequested(76) Integer32 (-2..100) tonerEcomonyUsed(75), JmTonerEconomyTC
INTEGER: MULTI-ROW: The toner density requested for a INTEGER: MULTI-ROW: The toner economy selection actually used
document in this job for devices that can vary toner by documents in the job for printers that allow toner economy
density levels. Level 1 is the lowest density and level differentiation.
100 is the highest density level. Devices with a smaller
range, SHALL map the 1-100 range evenly onto the
implemented range.
tonerDensityUsed(77), Integer32 (-2..100) tonerDensityRequested(76) Integer32 (-2..100)
INTEGER: MULTI-ROW: The toner density used by documents INTEGER: MULTI-ROW: The toner density requested for a document
in this job for devices that can vary toner density levels. in this job for devices that can vary toner density levels.
Level 1 is the lowest density and level 100 is the highest Level 1 is the lowest density and level 100 is the highest
density level. Devices with a smaller range, SHALL map the density level. Devices with a smaller range, SHALL map the
1-100 range evenly onto the implemented range. 1-100 range evenly onto the implemented range.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ tonerDensityUsed(77), Integer32 (-2..100)
+ Job Progress attributes (requested and consumed) (90-109) INTEGER: MULTI-ROW: The toner density used by documents in
+ this job for devices that can vary toner density levels. Level
+ Pairs of these attributes can be used by monitoring 1 is the lowest density and level 100 is the highest density
+ applications to show an indication of relative progress level. Devices with a smaller range, SHALL map the 1-100 range
+ to users. See section 3.4, entitled: evenly onto the implemented range.
+ 'Monitoring Job Progress'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobCopiesRequested(90), Integer32 (-2..2147483647) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: The number of copies of the entire job that are + Job Progress attributes (requested and consumed) (90-109)
to be produced. +
+ Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative progress
+ to users. See section 3.4, entitled:
+ 'Monitoring Job Progress'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobCopiesCompleted(91), Integer32 (-2..2147483647) jobCopiesRequested(90), Integer32 (-2..2147483647)
INTEGER: The number of copies of the entire job that have INTEGER: The number of copies of the entire job that are to be
been completed so far. produced.
documentCopiesRequested(92), Integer32 (-2..2147483647) jobCopiesCompleted(91), Integer32 (-2..2147483647)
INTEGER: The total count of the number of document copies INTEGER: The number of copies of the entire job that have been
requested for the job as a whole. If there are documents completed so far.
A, B, and C, and document B is specified to produce 4
copies, the number of document copies requested is 6 for
the job.
This attribute SHALL be used only when a job has multiple documentCopiesRequested(92), Integer32 (-2..2147483647)
documents. The jobCopiesRequested attribute SHALL be used INTEGER: The total count of the number of document copies
when the job has only one document. requested for the job as a whole. If there are documents A, B,
and C, and document B is specified to produce 4 copies, the
number of document copies requested is 6 for the job.
documentCopiesCompleted(93), Integer32 (-2..2147483647) This attribute SHALL be used only when a job has multiple
INTEGER: The total count of the number of document copies documents. The jobCopiesRequested attribute SHALL be used when
completed so far for the job as a whole. If there are the job has only one document.
documents A, B, and C, and document B is specified to
produce 4 copies, the number of document copies starts a 0
and runs up to 6 for the job as the job processes.
This attribute SHALL be used only when a job has multiple documentCopiesCompleted(93), Integer32 (-2..2147483647)
documents. The jobCopiesCompleted attribute SHALL be used INTEGER: The total count of the number of document copies
when the job has only one document. completed so far for the job as a whole. If there are documents
A, B, and C, and document B is specified to produce 4 copies,
the number of document copies starts a 0 and runs up to 6 for
the job as the job processes.
jobKOctetsTransferred(94), Integer32 (-2..2147483647) This attribute SHALL be used only when a job has multiple
INTEGER: The number of K (1024) octets transferred to the documents. The jobCopiesCompleted attribute SHALL be used when
server or device to which the agent is providing access. the job has only one document.
This count is independent of the number of copies of the
job or documents that will be produced, but it is only a
measure of the number of bytes transferred to the server or
device.
The agent SHALL round the actual number of octets jobKOctetsTransferred(94), Integer32 (-2..2147483647)
transferred up to the next higher K. Thus 0 octets SHALL INTEGER: The number of K (1024) octets transferred to the
be represented as '0', 1-1024 octets SHALL BE represented server or device to which the agent is providing access. This
as '1', 1025-2048 SHALL be '2', etc. When the job count is independent of the number of copies of the job or
completes, the values of the jmJobKOctetsPerCopyRequested documents that will be produced, but it is only a measure of the
object and the jobKOctetsTransferred attribute SHALL be number of bytes transferred to the server or device.
equal.
NOTE - The jobKOctetsTransferred can be used with the The agent SHALL round the actual number of octets transferred up
jmJobKOctetsPerCopyRequested object in order to produce a to the next higher K. Thus 0 octets SHALL be represented as '
relative indication of the progress of the job for agents 0', 1-1024 octets SHALL BE represented as '1', 1025-2048 SHALL
that do not implement the jmJobKOctetsProcessed object. be '2', etc. When the job completes, the values of the
jmJobKOctetsPerCopyRequested object and the
jobKOctetsTransferred attribute SHALL be equal.
sheetCompletedCopyNumber(95), Integer32 (-2..2147483647) NOTE - The jobKOctetsTransferred can be used with the
INTEGER: The number of the copy being stacked for the jmJobKOctetsPerCopyRequested object in order to produce a
current document. This number starts at 0, is set to 1 relative indication of the progress of the job for agents that
when the first sheet of the first copy for each document is do not implement the jmJobKOctetsProcessed object.
being stacked and is equal to n where n is the nth sheet
stacked in the current document copy. See section 3.4 ,
entitled 'Monitoring Job Progress'.
sheetCompletedDocumentNumber(96), Integer32 (-2..2147483647) sheetCompletedCopyNumber(95), Integer32 (-2..2147483647)
INTEGER: The ordinal number of the document in the job INTEGER: The number of the copy being stacked for the current
that is currently being stacked. This number starts at 0, document. This number starts at 0, is set to 1 when the first
increments to 1 when the first sheet of the first document sheet of the first copy for each document is being stacked and
in the job is being stacked, and is equal to n where n is is equal to n where n is the nth sheet stacked in the current
the nth document in the job, starting with 1. document copy. See section 3.4 , entitled 'Monitoring Job
Progress'.
Implementations that only support one document jobs SHOULD sheetCompletedDocumentNumber(96), Integer32 (-2..2147483647)
NOT implement this attribute. INTEGER: The ordinal number of the document in the job that is
currently being stacked. This number starts at 0, increments to
1 when the first sheet of the first document in the job is being
stacked, and is equal to n where n is the nth document in the
job, starting with 1.
jobCollationType(97), JmJobCollationTypeTC Implementations that only support one document jobs SHOULD NOT
INTEGER: The type of job collation. See also Section 3.4, implement this attribute.
entitled 'Monitoring Job Progress'.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ jobCollationType(97), JmJobCollationTypeTC
+ Impression attributes (110 - 129 decimal) INTEGER: The type of job collation. See also Section 3.4,
+ entitled 'Monitoring Job Progress'.
+ See the definition of the terms 'impression', 'sheet',
+ and 'page' in Section 2.
+
+ See also jmJobImpressionsPerCopyRequested and
+ jmJobImpressionsCompleted objects in the jmJobTable.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
impressionsSpooled(110), Integer32 (-2..2147483647) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: The number of impressions spooled to the server + Impression attributes (110 - 129 decimal)
or device for the job so far. +
+ See the definition of the terms 'impression', 'sheet',
+ and 'page' in Section 2.
+
+ See also jmJobImpressionsPerCopyRequested and
+ jmJobImpressionsCompleted objects in the jmJobTable.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
impressionsSentToDevice(111), Integer32 (-2..2147483647) impressionsSpooled(110), Integer32 (-2..2147483647)
INTEGER: The number of impressions sent to the device for INTEGER: The number of impressions spooled to the server or
the job so far. device for the job so far.
impressionsInterpreted(112), Integer32 (-2..2147483647) impressionsSentToDevice(111), Integer32 (-2..2147483647)
INTEGER: The number of impressions interpreted for the job INTEGER: The number of impressions sent to the device for the
so far. job so far.
impressionsCompletedCurrentCopy(113), impressionsInterpreted(112), Integer32 (-2..2147483647)
Integer32 (-2..2147483647) INTEGER: The number of impressions interpreted for the job so
INTEGER: The number of impressions completed by the device far.
for the current copy of the current document 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.
This value SHALL be reset to 0 for each document in the job impressionsCompletedCurrentCopy(113),
and for each document copy. Integer32 (-2..2147483647)
INTEGER: The number of impressions completed by the device for
the current copy of the current document 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.
fullColorImpressionsCompleted(114), Integer32 (-2..2147483647) This value SHALL be reset to 0 for each document in the job and
INTEGER: The number of full color impressions completed by for each document copy.
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. In any case, the value of this
attribute counts by 1 for each side that has full color,
not by the number of colors per side (and the other
impression counters are incremented, except
highlightColorImpressionsCompleted(115)).
highlightColorImpressionsCompleted(115), fullColorImpressionsCompleted(114), Integer32 (-2..2147483647)
Integer32 (-2..2147483647) INTEGER: The number of full color impressions completed by the
INTEGER: The number of highlight color impressions device for this job so far. For printing, the impressions
completed by the device for this job so far. For printing, completed includes interpreting, marking, and stacking the
the impressions completed includes interpreting, marking, output. For other types of job services, the number of
and stacking the output. For other types of job services, impressions completed includes the number of impressions
the number of impressions completed includes the number of processed. Full color impressions are typically defined as those
impressions processed. Highlight color impressions are requiring 3 or more colorants, but this MAY vary by
typically defined as those requiring black plus one other implementation. In any case, the value of this attribute counts
colorant, but this MAY vary by implementation. In any by 1 for each side that has full color, not by the number of
case, the value of this attribute counts by 1 for each side colors per side (and the other impression counters are
that has highlight color (and the other impression counters incremented, except highlightColorImpressionsCompleted(115)).
are incremented, except
fullColorImpressionsCompleted(114)).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ highlightColorImpressionsCompleted(115),
+ Page attributes (130 - 149 decimal) Integer32 (-2..2147483647)
+ INTEGER: The number of highlight color impressions
+ See the definition of 'impression', 'sheet', and 'page' completed by the device for this job so far. For printing,
+ in Section 2. 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. In any
case, the value of this attribute counts by 1 for each side
that has highlight color (and the other impression counters
are incremented, except
fullColorImpressionsCompleted(114)).
pagesRequested(130), Integer32 (-2..2147483647) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: The number of logical pages requested by the job + Page attributes (130 - 149 decimal)
to be processed. +
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
pagesCompleted(131), Integer32 (-2..2147483647) pagesRequested(130), Integer32 (-2..2147483647)
INTEGER: The number of logical pages completed for this INTEGER: The number of logical pages requested by the job
job so far. to be processed.
For implementations where multiple copies are produced by pagesCompleted(131), Integer32 (-2..2147483647)
the interpreter with only a single pass over the data, the INTEGER: The number of logical pages completed for this
final value SHALL be equal to the value of the job so far.
pagesRequested object. For implementations where multiple
copies are produced by the interpreter by processing the
data for each copy, the final value SHALL be a multiple of
the value of the pagesRequested object.
NOTE - See the impressionsCompletedCurrentCopy and For implementations where multiple copies are produced by
pagesCompletedCurrentCopy attributes for attributes that the interpreter with only a single pass over the data, the
are reset on each document copy. final value SHALL be equal to the value of the
pagesRequested object. For implementations where multiple
copies are produced by the interpreter by processing the
data for each copy, the final value SHALL be a multiple of
the value of the pagesRequested object.
NOTE - The pagesCompleted object can be used with the NOTE - See the impressionsCompletedCurrentCopy and
pagesRequested object to provide an indication of the pagesCompletedCurrentCopy attributes for attributes that
relative progress of the job, provided that the are reset on each document copy.
multiplicative factor is taken into account for some
implementations of multiple copies.
pagesCompletedCurrentCopy(132), Integer32 (-2..2147483647) NOTE - The pagesCompleted object can be used with the
INTEGER: The number of logical pages completed for the pagesRequested object to provide an indication of the
current copy of the document so far. This value SHALL be relative progress of the job, provided that the
reset to 0 for each document in the job and for each multiplicative factor is taken into account for some
document copy. implementations of multiple copies.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ pagesCompletedCurrentCopy(132), Integer32 (-2..2147483647)
+ Sheet attributes (150 - 169 decimal) INTEGER: The number of logical pages completed for the
+ current copy of the document so far. This value SHALL be
+ See the definition of 'impression', 'sheet', and 'page' reset to 0 for each document in the job and for each
+ in Section 2. document copy.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sheetsRequested(150), Integer32 (-2..2147483647) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INTEGER: The total number of medium sheets requested to be + Sheet attributes (150 - 169 decimal)
produced for this job. +
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sheetsRequested(150), Integer32 (-2..2147483647)
INTEGER: The total number of medium sheets requested to be
produced for this job.
Unlike the jmJobKOctetsPerCopyRequested and Unlike the jmJobKOctetsPerCopyRequested and
jmJobImpressionsPerCopyRequested attributes, the jmJobImpressionsPerCopyRequested attributes, the
sheetsRequested(150) attribute SHALL include the sheetsRequested(150) attribute SHALL include the
multiplicative factor contributed by the number of copies multiplicative factor contributed by the number of copies
and so is the total number of sheets to be produced by the and so is the total number of sheets to be produced by the
job, as opposed to the size of the document(s) submitted. job, as opposed to the size of the document(s) submitted.
sheetsCompleted(151), Integer32 (-2..2147483647) sheetsCompleted(151), Integer32 (-2..2147483647)
INTEGER: The total number of medium sheets that have INTEGER: The total number of medium sheets that have
completed marking and stacking for the entire job so far completed marking and stacking for the entire job so far
whether those sheets have been processed on one side or on whether those sheets have been processed on one side or on
both. both.
sheetsCompletedCurrentCopy(152), Integer32 (-2..2147483647) 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 in marking and stacking for the current copy of a document in
the job so far whether those sheets have been processed on the job so far whether those sheets have been processed on
one side or on both. one side or on both.
The value of this attribute SHALL be 0 before the job The value of this attribute SHALL be 0 before the job
starts processing and SHALL be reset to 1 after the first starts processing and SHALL be reset to 1 after the first
sheet of each document and document copy in the job is sheet of each document and document copy in the job is
processed and stacked. processed and stacked.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) (170 - 189) + Resources attributes (requested and consumed) (170 - 189)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to + applications to show an indication of relative usage to
+ users, i.e., a 'thermometer'. + users, i.e., a 'thermometer'.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mediumRequested(170), JmMediumTypeTC mediumRequested(170), JmMediumTypeTC
AND/OR AND/OR
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The type INTEGER: MULTI-ROW: The type
AND/OR AND/OR
OCTETS: MULTI-ROW: the name of the medium that is OCTETS: MULTI-ROW: the name of the medium that is
required by the job. required by the job.
NOTE - The name (JmJobStringTC) values correspond to the NOTE - The name (JmJobStringTC) values correspond to the
name values of the prtInputMediaName object in the Printer name values of the prtInputMediaName object in the Printer
MIB [print-mib] and the name, size, and input tray values MIB [print-mib] and the name, size, and input tray values
of the IPP 'media' attribute [ipp-model]. of the IPP 'media' attribute [ipp-model].
mediumConsumed(171), Integer32 (-2..2147483647) mediumConsumed(171), Integer32 (-2..2147483647)
AND AND
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The number of sheets INTEGER: MULTI-ROW: The number of sheets
AND AND
OCTETS: MULTI-ROW: the name of the medium that has been OCTETS: MULTI-ROW: the name of the medium that has been
consumed so far whether those sheets have been processed on consumed so far whether those sheets have been processed on
one side or on both. one side or on both.
This attribute SHALL have both Integer32 and OCTET STRING This attribute SHALL have both Integer32 and OCTET STRING
(represented as JmJobStringTC) values. (represented as JmJobStringTC) values.
NOTE - The name (JmJobStringTC) values correspond to the NOTE - The name (JmJobStringTC) values correspond to the
name values of the prtInputMediaName object in the Printer name values of the prtInputMediaName object in the Printer
MIB [print-mib] and the name, size, and input tray values MIB [print-mib] and the name, size, and input tray values
of the IPP 'media' attribute [ipp-model]. of the IPP 'media' attribute [ipp-model].
colorantRequested(172), Integer32 (-2..2147483647) colorantRequested(172), Integer32 (-2..2147483647)
AND/OR AND/OR
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in
the Printer MIB[print-mib] the Printer MIB [print-mib]
AND/OR AND/OR
OCTETS: MULTI-ROW: the name of the colorant requested. OCTETS: MULTI-ROW: the name of the colorant requested.
NOTE - The name (JmJobStringTC) values correspond to the NOTE - The name (JmJobStringTC) values correspond to the
name values of the prtMarkerColorantValue object in the name values of the prtMarkerColorantValue object in the
Printer MIB. Examples are: red, blue. Printer MIB. Examples are: red, blue.
colorantConsumed(173), Integer32 (-2..2147483647) colorantConsumed(173), Integer32 (-2..2147483647)
AND/OR AND/OR
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in
the Printer MIB[print-mib] the Printer MIB [print-mib]
AND/OR AND/OR
OCTETS: MULTI-ROW: the name of the colorant consumed. OCTETS: MULTI-ROW: the name of the colorant consumed.
NOTE - The name (JmJobStringTC) values correspond to the NOTE - The name (JmJobStringTC) values correspond to the
name values of the prtMarkerColorantValue object in the name values of the prtMarkerColorantValue object in the
Printer MIB. Examples are: red, blue Printer MIB. Examples are: red, blue
mediumTypeConsumed(174), Integer32 (-2..2147483647) mediumTypeConsumed(174), Integer32 (-2..2147483647)
AND AND
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The number of sheets of the indicated INTEGER: MULTI-ROW: The number of sheets of the indicated
medium type that has been consumed so far whether those medium type that has been consumed so far whether those
sheets have been processed on one side or on both sheets have been processed on one side or on both
AND AND
OCTETS: MULTI-ROW: the name of that medium type. OCTETS: MULTI-ROW: the name of that medium type.
This attribute SHALL have both Integer32 and OCTET STRING This attribute SHALL have both Integer32 and OCTET STRING
(represented as JmJobStringTC) values. (represented as JmJobStringTC) values.
NOTE - The type name (JmJobStringTC) values correspond to NOTE - The type name (JmJobStringTC) values correspond to
the type name values of the prtInputMediaType object in the the type name values of the prtInputMediaType object in the
Printer MIB [print-mib]. Values are: 'stationery', Printer MIB [print-mib]. Values are: 'stationery',
'transparency', 'envelope', etc. These medium type names 'transparency', 'envelope', etc. These medium type names
correspond to the enum values of JmMediumTypeTC used in the correspond to the enum values of JmMediumTypeTC used in the
mediumRequested attribute. mediumRequested attribute.
mediumSizeConsumed(175), Integer32 (-2..2147483647) mediumSizeConsumed(175), Integer32 (-2..2147483647)
AND AND
JmJobStringTC (SIZE(0..63)) JmJobStringTC (SIZE(0..63))
INTEGER: MULTI-ROW: The number of sheets of the indicated INTEGER: MULTI-ROW: The number of sheets of the indicated
medium size that has been consumed so far whether those medium size that has been consumed so far whether those
sheets have been processed on one side or on both sheets have been processed on one side or on both
AND AND
OCTETS: MULTI-ROW: the name of that medium size. OCTETS: MULTI-ROW: the name of that medium size.
This attribute SHALL have both Integer32 and OCTET STRING This attribute SHALL have both Integer32 and OCTET STRING
(represented as JmJobStringTC) values. (represented as JmJobStringTC) values.
NOTE - The size name (JmJobStringTC) values correspond to NOTE - The size name (JmJobStringTC) values correspond to
the size name values in the Printer MIB [print-mib] the size name values in the Printer MIB [print-mib]
Appendix B. These size name values are also a subset of Appendix B. These size name values are also a subset of
the keyword values defined by [ipp-model] for the 'media' the keyword values defined by [ipp-model] for the 'media'
Job Template attribute. Values are: 'letter', 'a', 'iso- Job Template attribute. Values are: 'letter', 'a', 'iso-
a4', 'jis-b4', etc. a4', 'jis-b4', etc.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Time attributes (set by server or device) (190 - 209 decimal) + Time attributes (set by server or device) (190 - 209 decimal)
+ +
+ 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 3.1.2 and section 3.1.3 for the + See section 3.1.2 and section 3.1.3 for the
+ conformance requirements for time attribute for agents and + conformance requirements for time attribute for agents and
+ monitoring applications, respectively. The two forms are: + monitoring 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 [SMIv2-TC]. + optional offset from UTC. See SNMPv2-TC [SMIv2-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. + seconds since the system was booted.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobSubmissionToServerTime(190), JmTimeStampTC jobSubmissionToServerTime(190), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: Configuration 3 only: The time INTEGER: Configuration 3 only: The time
AND/OR AND/OR
OCTETS: the date and time that the job was submitted to OCTETS: the date and time that the job was submitted to
the server (as distinguished from the device which uses the server (as distinguished from the device which uses
jobSubmissionTime). jobSubmissionTime).
jobSubmissionTime(191), JmTimeStampTC jobSubmissionTime(191), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: Configurations 1, 2, and 3: The time INTEGER: Configurations 1, 2, and 3: The time
AND/OR AND/OR
OCTETS: the date and time that the job was submitted to OCTETS: the date and time that the job was submitted to
the server or device to which the agent is providing the server or device to which the agent is providing
access. access.
jobStartedBeingHeldTime(192), JmTimeStampTC jobStartedBeingHeldTime(192), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job last entered the OCTETS: the date and time that the job last entered the
pendingHeld state. If the job has never entered the pendingHeld state. If the job has never entered the
pendingHeld state, then the value SHALL be '0' or the pendingHeld state, then the value SHALL be '0' or the
attribute SHALL not be present in the table. attribute SHALL not be present in the table.
jobStartedProcessingTime(193), JmTimeStampTC jobStartedProcessingTime(193), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job started processing. OCTETS: the date and time that the job started processing.
jobCompletionTime(194), JmTimeStampTC jobCompletionTime(194), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job entered the OCTETS: the date and time that the job entered the
completed, canceled, or aborted state. completed, canceled, or aborted state.
jobProcessingCPUTime(195) Integer32 (-2..2147483647) jobProcessingCPUTime(195) Integer32 (-2..2147483647)
UNITS 'seconds' UNITS 'seconds'
INTEGER: The amount of CPU time in seconds that the job INTEGER: The amount of CPU time in seconds that the job
has been in the processing state. If the job enters the has been in the processing state. If the job enters the
processingStopped state, that elapsed time SHALL not be processingStopped state, that elapsed time SHALL not be
included. In other words, the jobProcessingCPUTime value included. In other words, the jobProcessingCPUTime value
SHOULD be relatively repeatable when the same job is SHOULD be relatively repeatable when the same job is
processed again on the same device. processed again on the same device.
3.3.9 Job State Reason bit definitions 3.3.9 Job State Reason bit definitions
The JmJobStateReasonsNTC (N=1..4) textual-conventions are used with the The JmJobStateReasonsNTC (N=1..4) textual-conventions are used with
jmJobStateReasons1 object and jobStateReasonsN (N=2..4), respectively, the jmJobStateReasons1 object and jobStateReasonsN (N=2..4),
to provide additional information regarding the current jmJobState respectively, to provide additional information regarding the current
object value. These values MAY be used with any job state or states jmJobState object value. These values MAY be used with any job state
for which the reason makes sense. or states for which the reason makes sense.
NOTE - While values cannot be added to the jmJobState object without NOTE - While values cannot be added to the jmJobState object without
impacting deployed clients that take actions upon receiving jmJobState impacting deployed clients that take actions upon receiving
values, it is the intent that additional JmJobStateReasonsNTC enums can jmJobState values, it is the intent that additional
be defined and registered without impacting such deployed clients. In JmJobStateReasonsNTC enums can be defined and registered without
other words, the jmJobStateReasons1 object and jobStateReasonsN impacting such deployed clients. In other words, the
attributes are intended to be extensible. jmJobStateReasons1 object and jobStateReasonsN attributes are
intended to be extensible.
NOTE - The Job Monitoring MIB contains a superset of the IPP NOTE - The Job Monitoring MIB contains a superset of the IPP values
values[ipp-model] for the IPP 'job-state-reasons' attribute, since the [ipp-model] for the IPP 'job-state-reasons' attribute, since the Job
Job Monitoring MIB is intended to cover other job submission protocols Monitoring MIB is intended to cover other job submission protocols as
as well. Also some of the names of the reasons have been changed from well. Also some of the names of the reasons have been changed from '
'printer' to 'device', since the Job Monitoring MIB is intended to printer' to 'device', since the Job Monitoring MIB is intended to
cover additional types of devices, including input devices, such as cover additional types of devices, including input devices, such as
scanners. scanners.
3.3.9.1 JmJobStateReasons1TC specification 3.3.9.1 JmJobStateReasons1TC specification
The following standard values are defined (in hexadecimal) as powers of The following standard values are defined (in hexadecimal) as powers
two, since multiple values MAY be used at the same time. For ease of of two, since multiple values MAY be used at the same time. For ease
understanding, the JmJobStateReasons1TC reasons are presented in the of understanding, the JmJobStateReasons1TC reasons are presented in
order in which the reasons are likely to occur (if implemented), the order in which the reasons are likely to occur (if implemented),
starting with the 'jobIncoming' value and ending with the starting with the 'jobIncoming' value and ending with the '
'jobCompletedWithErrors' value. jobCompletedWithErrors' value.
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 or is The job state reason is not known to the agent or is
indeterminent. indeterminent.
jobIncoming 0x4 jobIncoming 0x4
The job has been accepted by the server or device, but the The job has been accepted by the server or device, but the
server or device is expecting (1) additional operations server or device is expecting (1) additional operations from the
from the client to finish creating the job and/or (2) is client to finish creating the job and/or (2) is
accessing/accepting document data. accessing/accepting document data.
submissionInterrupted 0x8 submissionInterrupted 0x8
The job was not completely submitted for some unforeseen The job was not completely submitted for some unforeseen reason,
reason, such as: (1) the server has crashed before the job such as: (1) the server has crashed before the job was closed by
was closed by the client, (2) the server or the document the client, (2) the server or the document transfer method has
transfer method has crashed in some non-recoverable way crashed in some non-recoverable way before the document data was
before the document data was entirely transferred to the entirely transferred to the server, (3) the client crashed or
server, (3) the client crashed or failed to close the job failed to close the job before the time-out period.
before the time-out period.
jobOutgoing 0x10 jobOutgoing 0x10
Configuration 2 only: The server is transmitting the job Configuration 2 only: The server is transmitting the job to the
to the device. device.
jobHoldSpecified 0x20 jobHoldSpecified 0x20
The value of the job's jobHold(52) attribute is TRUE. The The value of the job's jobHold(52) attribute is TRUE. The job
job SHALL NOT be a candidate for processing until this SHALL NOT be a candidate for processing until this reason is
reason is removed and there are no other reasons to hold removed and there are no other reasons to hold the job.
the job.
jobHoldUntilSpecified 0x40 jobHoldUntilSpecified 0x40
The value of the job's jobHoldUntil(53) attribute specifies The value of the job's jobHoldUntil(53) attribute specifies a
a time period that is still in the future. The job SHALL time period that is still in the future. The job SHALL NOT be a
NOT be a candidate for processing until this reason is candidate for processing until this reason is removed and there
removed and there are no other reasons to hold the job. are no other reasons to hold the job.
jobProcessAfterSpecified 0x80 jobProcessAfterSpecified 0x80
The value of the job's jobProcessAfterDateAndTime(51) The value of the job's jobProcessAfterDateAndTime(51) attribute
attribute specifies a time that is still in the future. specifies a time that is still in the future. The job SHALL NOT
The job SHALL NOT be a candidate for processing until this be a candidate for processing until this reason is removed and
reason is removed and there are no other reasons to hold there are no other reasons to hold the job.
the job.
resourcesAreNotReady 0x100 resourcesAreNotReady 0x100
At least one of the resources needed by the job, such as At least one of the resources needed by the job, such as media,
media, fonts, resource objects, etc., is not ready on any fonts, resource objects, etc., is not ready on any of the
of the physical devices for which the job is a candidate. physical devices for which the job is a candidate. This
This condition MAY be detected when the job is accepted, or condition MAY be detected when the job is accepted, or
subsequently while the job is pending or processing, subsequently while the job is pending or processing, depending
depending on implementation. on implementation.
deviceStoppedPartly 0x200 deviceStoppedPartly 0x200
One or more, but not all, of the devices to which the job One or more, but not all, of the devices to which the job is
is assigned are stopped. If all of the devices are stopped assigned are stopped. If all of the devices are stopped (or the
(or the only device is stopped), the deviceStopped reason only device is stopped), the deviceStopped reason SHALL be used.
SHALL be used.
deviceStopped 0x400 deviceStopped 0x400
The device(s) to which the job is assigned is (are all) The device(s) to which the job is assigned is (are all) stopped.
stopped.
jobInterpreting 0x800 jobInterpreting 0x800
The device to which the job is assigned is interpreting the The device to which the job is assigned is interpreting the
document data. document data.
jobPrinting 0x1000 jobPrinting 0x1000
The output device to which the job is assigned is marking The output device to which the job is assigned is marking media.
media. This value is useful for servers and output devices This value is useful for servers and output devices which spend
which spend a great deal of time processing (1) when no a great deal of time processing (1) when no marking is happening
marking is happening and then want to show that marking is and then want to show that marking is now happening or (2) when
now happening or (2) when the job is in the process of the job is in the process of being canceled or aborted while the
being canceled or aborted while the job remains in the job remains in the processing state, but the marking has not yet
processing state, but the marking has not yet stopped so stopped so that impression or sheet counts are still increasing
that impression or sheet counts are still increasing for for the job.
the job.
jobCanceledByUser 0x2000 jobCanceledByUser 0x2000
The job was canceled by the owner of the job, i.e., by a The job was canceled by the owner of the job, i.e., by a user
user whose name is the same as the value of the job's whose name is the same as the value of the job's jmJobOwner
jmJobOwner object, or by some other authorized end-user, object, or by some other authorized end-user, such as a member
such as a member of the job owner's security group. of the job owner's security group.
jobCanceledByOperator 0x4000 jobCanceledByOperator 0x4000
The job was canceled by the operator, i.e., by a user who The job was canceled by the operator, i.e., by a user who has
has been authenticated as having operator privileges been authenticated as having operator privileges (whether local
(whether local or remote). or remote).
jobCanceledAtDevice 0x8000 jobCanceledAtDevice 0x8000
The job was canceled by an unidentified local user, i.e., a The job was canceled by an unidentified local user, i.e., a user
user at a console at the device. at a console at the device.
abortedBySystem 0x10000 abortedBySystem 0x10000
The job (1) is in the process of being aborted, (2) has The job (1) is in the process of being aborted, (2) has been
been aborted by the system and placed in the 'aborted' aborted by the system and placed in the 'aborted' state, or (3)
state, or (3) has been aborted by the system and placed in has been aborted by the system and placed in the 'pendingHeld'
the 'pendingHeld' state, so that a user or operator can state, so that a user or operator can manually try the job
manually try the job again. again.
processingToStopPoint 0x20000 processingToStopPoint 0x20000
The requester has issued an operation to cancel or The requester has issued an operation to cancel or interrupt the
interrupt the job or the server/device has aborted the job, job or the server/device has aborted the job, but the
but the server/device is still performing some actions on server/device is still performing some actions on the job until
the job until a specified stop point occurs or job a specified stop point occurs or job termination/cleanup is
termination/cleanup is completed. completed.
This reason is recommended to be used in conjunction with This reason is recommended to be used in conjunction with the
the processing job state to indicate that the server/device processing job state to indicate that the server/device is still
is still performing some actions on the job while the job performing some actions on the job while the job remains in the
remains in the processing state. After all the job's processing state. After all the job's resources consumed
resources consumed counters have stopped incrementing, the counters have stopped incrementing, the server/device moves the
server/device moves the job from the processing state to job from the processing state to the canceled or aborted job
the canceled or aborted job states. states.
serviceOffLine 0x40000 serviceOffLine 0x40000
The service or document transform is off-line and accepting The service or document transform is off-line and accepting no
no jobs. All pending jobs are put into the pendingHeld jobs. All pending jobs are put into the pendingHeld state.
state. This situation could be true if the service's or This situation could be true if the service's or document
document transform's input is impaired or broken. transform's input is impaired or broken.
jobCompletedSuccessfully 0x80000 jobCompletedSuccessfully 0x80000
The job completed successfully. The job completed successfully.
jobCompletedWithWarnings 0x100000 jobCompletedWithWarnings 0x100000
The job completed with warnings. The job completed with warnings.
jobCompletedWithErrors 0x200000 jobCompletedWithErrors 0x200000
The job completed with errors (and possibly warnings too). The job completed with errors (and possibly warnings too).
The following additional job state reasons have been added to represent The following additional job state reasons have been added to
job states that are in ISO DPA[iso-dpa] and other job submission represent job states that are in ISO DPA [iso-dpa] and other job
protocols: submission protocols:
jobPaused 0x400000 jobPaused 0x400000
The job has been indefinitely suspended by a client issuing The job has been indefinitely suspended by a client issuing an
an operation to suspend the job so that other jobs may operation to suspend the job so that other jobs may proceed
proceed using the same devices. The client MAY issue an using the same devices. The client MAY issue an operation to
operation to resume the paused job at any time, in which resume the paused job at any time, in which case the agent SHALL
case the agent SHALL remove the jobPaused values from the remove the jobPaused values from the job's jmJobStateReasons1
job's jmJobStateReasons1 object and the job is eventually object and the job is eventually resumed at or near the point
resumed at or near the point where the job was paused. where the job was paused.
jobInterrupted 0x800000 jobInterrupted 0x800000 The job has been
The job has been interrupted while processing by a client 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 0x1000000 jobRetained 0x1000000
The job is being retained by the server or device with all The job is being retained by the server or device with all of
of the job's document data (and submitted resources, such the job's document data (and submitted resources, such as fonts,
as fonts, logos, and forms, if any). Thus a client could logos, and forms, if any). Thus a client could issue an
issue an operation to the server or device to either (1) operation to the server or device to either (1) re-do the job
re-do the job (or a copy of the job) on the same server or (or a copy of the job) on the same server or device or (2)
device or (2) resubmit the job to another server or device. resubmit the job to another server or device. When a client
When a client could no longer re-do/resubmit the job, such could no longer re-do/resubmit the job, such as after the
as after the document data has been discarded, the agent document data has been discarded, the agent SHALL remove the
SHALL remove the jobRetained value from the jobRetained value from the jmJobStateReasons1 object.
jmJobStateReasons1 object.
These bit definitions are the equivalent of a type 2 enum except that These bit definitions are the equivalent of a type 2 enum except
combinations of bits may be used together. See section 3.7.1.2. The that combinations of bits may be used together. See section
remaining bits are reserved for future standardization and/or 3.7.1.2. The remaining bits are reserved for future
registration. standardization and/or registration.
3.3.9.2 JmJobStateReasons2TC specification 3.3.9.2 JmJobStateReasons2TC specification
The following standard values are defined (in hexadecimal) as powers of The following standard values are defined (in hexadecimal) as powers
two, since multiple values MAY be used at the same time. of two, since multiple values MAY be used at the same time.
cascaded 0x1 cascaded 0x1
An outbound gateway has transmitted all of the job's job An outbound gateway has transmitted all of the job's job and
and document attributes and data to another spooling document attributes and data to another spooling system.
system.
deletedByAdministrator 0x2 deletedByAdministrator 0x2
The administrator has deleted the job. The administrator has deleted the job.
discardTimeArrived 0x4 discardTimeArrived 0x4
The job has been deleted due to the fact that the time The job has been deleted due to the fact that the time specified
specified by the job's job-discard-time attribute has by the job's job-discard-time attribute has arrived.
arrived.
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 the completed state with the jobRetained the completed state with the jobRetained jmJobStateReasons1
jmJobStateReasons1 object 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.
jobTransforming 0x10 jobTransforming 0x10
The server/device is interpreting document data and The server/device is interpreting document data and producing
producing another electronic representation. another electronic representation.
maxJobFaultCountExceeded 0x20 maxJobFaultCountExceeded 0x20
The job has faulted several times and has exceeded the The job has faulted several times and has exceeded the
administratively defined fault count limit. administratively defined fault count limit.
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. time-out value.
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. the site-settable time-out value.
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 cartridge or special non-standard media, but the job was not
job was not resumed within the site-settable time-out value resumed within the site-settable time-out value and the
and the server/device has transitioned the job to the server/device has transitioned the job to the pendingHeld state.
pendingHeld state.
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 to await human action, such as removing a to await human action, such as removing a special cartridge or
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.
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
password was not received within the site-settable time-out password was not received within the site-settable time-out
value. value.
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
period specified by the device's site-settable attribute. 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.
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
downstream device. downstream device.
queuedInDevice 0x4000 queuedInDevice 0x4000
The server/device has queued the job in a down stream The server/device has queued the job in a down stream server or
server or downstream device. downstream device.
jobQueued 0x8000 jobQueued 0x8000
The server/device has queued the document data. The server/device has queued the document data.
jobCleanup 0x10000 jobCleanup 0x10000
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.
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 starting but instead of assigning resources and starting the job
the job processing, the server/device has transitioned the processing, the server/device has transitioned the job to the
job to the pendingHeld state to await entry of a password pendingHeld state to await entry of a password (and dispatched
(and dispatched another job, if there is one). another job, if there is one).
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.
queueHeld 0x80000 queueHeld 0x80000
The operator has held the entire job set or queue. The operator has held the entire job set or queue.
jobProofWait 0x100000 jobProofWait 0x100000
The job has produced a single proof copy and is in the The job has produced a single proof copy and is in the
pendingHeld state waiting for the requester to issue an pendingHeld state waiting for the requester to issue an
operation to release the job to print normally, obeying any operation to release the job to print normally, obeying any job
job and document copy attributes that were originally and document copy attributes that were originally submitted.
submitted.
heldForDiagnostics 0x200000 heldForDiagnostics 0x200000
The system is running intrusive diagnostics, so that all The system is running intrusive diagnostics, so that all jobs
jobs are being held. are being held.
noSpaceOnServer 0x800000 noSpaceOnServer 0x800000
There is no room on the server to store all of the job. There is no room on the server to store all of the 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. supplied as an input parameter when the job was created.
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.
heldForRetry 0x4000000 heldForRetry 0x4000000
The job encountered some errors that the server/device The job encountered some errors that the server/device could not
could not recover from with its normal retry procedures, recover from with its normal retry procedures, but the error
but the error might not be encountered if the job is might not be encountered if the job is processed again in the
processed again in the future. Example cases are phone future. Example cases are phone number busy or remote file
number busy or remote file system in-accessible. For such system in-accessible. For such a situation, the server/device
a situation, the server/device SHALL transition the job SHALL transition the job from the processing to the pendingHeld,
from the processing to the pendingHeld, rather than to the rather than to the aborted state.
aborted 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. before completing the job.
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. currently unable to accept jobs.
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 to handle this particular job; the spooler SHOULD try another
try another device or the user should submit the job to device or the user should submit the job to another device.
another device.
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 problem, such as an ill-formed PDL; the spooler SHOULD not even
SHOULD not even try another device. try another device.
These bit definitions are the equivalent of a type 2 enum except that These bit definitions are the equivalent of a type 2 enum except that
combinations of them may be used together. See section 3.7.1.2. combinations of them may be used together. See section 3.7.1.2.
3.3.9.3 JmJobStateReasons3TC specification 3.3.9.3 JmJobStateReasons3TC specification
This textual-convention is used with the jobStateReasons3 attribute to This textual-convention is used with the jobStateReasons3 attribute
provides additional information regarding the jmJobState object. The to provides additional information regarding the jmJobState object.
following standard values are defined (in hexadecimal) as powers of The following standard values are defined (in hexadecimal) as powers
two, since multiple values may be used at the same time: of two, since multiple values may be used at the same time:
jobInterruptedByDeviceFailure 0x1 jobInterruptedByDeviceFailure 0x1
A device or the print system software that the job was A device or the print system software that the job was using has
using has failed while the job was processing. The server failed while the job was processing. The server or device is
or device is keeping the job in the pendingHeld state until keeping the job in the pendingHeld state until an operator can
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 that These bit definitions are the equivalent of a type 2 enum except that
combinations of them may be used together. See section 3.7.1.2. The combinations of them may be used together. See section 3.7.1.2. The
remaining bits are reserved for future standardization and/or remaining bits are reserved for future standardization and/or
registration. registration.
3.3.9.4 JmJobStateReasons4TC specification 3.3.9.4 JmJobStateReasons4TC specification
This textual-convention is used with the jobStateReasons4 attribute to This textual-convention is used with the jobStateReasons4 attribute
provides additional information regarding the jmJobState object. The to provides additional information regarding the jmJobState object.
following standard values are defined (in hexadecimal) as powers of The following standard values are defined (in hexadecimal) as powers
two, since multiple values MAY be used at the same time. of two, since multiple values MAY be used at the same time.
None defined at this time. None defined at this time.
These bit definitions are the equivalent of a type 2 enum except that These bit definitions are the equivalent of a type 2 enum except that
combinations of them may be used together. See section 3.7.1.2. The combinations of them may be used together. See section 3.7.1.2. The
remaining bits are reserved for future standardization and/or remaining bits are reserved for future standardization and/or
registration. registration.
3.4 Monitoring Job Progress 3.4 Monitoring Job Progress
There are a number of objects and attributes for monitoring the There are a number of objects and attributes for monitoring the
progress of a job. These objects and attributes count the number of K progress of a job. These objects and attributes count the number of
octets, impressions, sheets, and pages requested or completed. For K octets, impressions, sheets, and pages requested or completed. For
impressions and sheets, "completed" means stacked, unless the impressions and sheets, "completed" means stacked, unless the
implementation is unable to detect when each sheet is stacked, in which implementation is unable to detect when each sheet is stacked, in
case stacked is approximated when processing of each sheet completes. which case stacked is approximated when processing of each sheet
There are objects and attributes for the overall job and for the completes. There are objects and attributes for the overall job and
current copy of the document currently being stacked. For the latter, for the current copy of the document currently being stacked. For
the rate at which the various objects and attributes count depends on the latter, the rate at which the various objects and attributes
the sheet and document collation of the job. count depends on the sheet and document collation of the job.
Job Collation included sheet collation and document collation. Sheet Job Collation included sheet collation and document collation. Sheet
collation is defined to be the ordering of sheets within a document collation is defined to be the ordering of sheets within a document
copy. Document collation is defined to be ordering of document copies copy. Document collation is defined to be ordering of document
within a multi-document job. There are three types of job collation copies within a multi-document job. There are three types of job
(see terminology definitions in Section 2): collation (see terminology definitions in Section 2):
1.uncollatedSheets(3) - No collation of the sheets within each 1.uncollatedSheets(3) - No collation of the sheets within each
document copy, i.e., each sheet of a document that is to document copy, i.e., each sheet of a document that is to produce
produce multiple copies is replicated before the next sheet in multiple copies is replicated before the next sheet in the
the document is processed and stacked. If the device has an document is processed and stacked. If the device has an output
output bin collator, the uncollatedSheets(3) value may actually bin collator, the uncollatedSheets(3) value may actually produce
produce collated sheets as far as the user is concerned (in the collated sheets as far as the user is concerned (in the output
output bins). However, when the job collation is the bins). However, when the job collation is the to a monitoring
'uncollatedSheets(3)' value, job progress is indistinguishable application between a device that has an output bin collator and
to a monitoring application between a device that has an output one that does not.
bin collator and one that does not.
2.collatedDocuments(4) - Collation of the sheets within each 2.collatedDocuments(4) - Collation of the sheets within each
document copy is performed within the printing device by making document copy is performed within the printing device by making
multiple passes over either the source or an intermediate multiple passes over either the source or an intermediate
representation of the document. In addition, when there are representation of the document. In addition, when there are
multiple documents per job, the i'th copy of each document is multiple documents per job, the i'th copy of each document is
stacked before the j'th copy of each document, i.e., the stacked before the j'th copy of each document, i.e., the
documents are collated within each job copy. For example, if a documents are collated within each job copy. For example, if a
job is submitted with documents, A and B, the job is made job is submitted with documents, A and B, the job is made
available to the end user as: A, B, A, B, .... The available to the end user as: A, B, A, B, .... The '
'collatedDocuments(4)' value corresponds to the IPP [ipp-model] collatedDocuments(4)' value corresponds to the IPP [ipp-model] '
'separate-documents-collated-copies' value of the "multiple- separate-documents-collated-copies' value of the "multiple-
document-handling" attribute. document-handling" attribute.
If jobCopiesRequested or documentCopiesRequested = 1, then If jobCopiesRequested or documentCopiesRequested = 1, then
jobCollationType is defined as 4. jobCollationType is defined as 4.
3.uncollatedDocuments(5) - Collation of the sheets within each 3.uncollatedDocuments(5) - Collation of the sheets within each
document copy is performed within the printing device by making document copy is performed within the printing device by making
multiple passes over either the source or an intermediate multiple passes over either the source or an intermediate
representation of the document. In addition, when there are representation of the document. In addition, when there are
multiple documents per job, all copies of the first document in multiple documents per job, all copies of the first document in
the job are stacked before the any copied of the next document the job are stacked before the any copied of the next document in
in the job, i.e., the documents are uncollated within the job. the job, i.e., the documents are uncollated within the job. For
For example, if a job is submitted with documents, A and B, the example, if a job is submitted with documents, A and B, the job
job is mad available to the end user as: A, A, ..., B, B, .... is mad available to the end user as: A, A, ..., B, B, .... The
The 'uncollatedDocuments(5)' value corresponds to the IPP [ipp- 'uncollatedDocuments(5)' value corresponds to the IPP [ipp-model]
model] 'separate-documents-uncollated-copies' value of the 'separate-documents-uncollated-copies' value of the "multiple-
"multiple-document-handling" attribute. document-handling" attribute.
Consider the following four variables that are used to monitor the Consider the following four variables that are used to monitor the
progress of a job's impressions: progress of a job's impressions:
1.jmJobImpressionsCompleted - counts the total number of 1.jmJobImpressionsCompleted - counts the total number of
impressions stacked for the job impressions stacked for the job
2.impressionsCompletedCurrentCopy - counts the number of 2.impressionsCompletedCurrentCopy - counts the number of
impressions stacked for the current document copy impressions stacked for the current document copy
3.sheetCompletedCopyNumber - identifies the number of the copy 3.sheetCompletedCopyNumber - identifies the number of the copy for
for the current document being stacked where the first copy is the current document being stacked where the first copy is 1.
1.
4.sheetCompletedDocumentNumber - identifies the current document 4.sheetCompletedDocumentNumber - identifies the current document
within the job that is being stacked where the first document within the job that is being stacked where the first document in
in a job is 1. NOTE: this attribute SHOULD NOT be implemented a job is 1. NOTE: this attribute SHOULD NOT be implemented for
for implementations that only support one document per job. implementations that only support one document per job.
For each of the three types of job collation, a job with three copies For each of the three types of job collation, a job with three copies
of two documents (1, 2), where each document consists of 3 impressions, of two documents (1, 2), where each document consists of 3
the four variables have the following values as each sheet is stacked impressions, the four variables have the following values as each
for one-sided printing: sheet is stacked for one-sided printing:
Job Collation Type = uncollatedSheets(3) Job Collation Type = uncollatedSheets(3)
jmJobImpressions Impressions sheetCompleted sheetCompleted jmJobImpressions Impressions sheetCompleted sheetCompleted
Completed CompletedCurrent CopyNumber DocumentNumber Completed CompletedCurrent CopyNumber DocumentNumber
Copy Copy
0 0 0 0 0 0 0 0
1 1 1 1 1 1 1 1
2 1 2 1 2 1 2 1
3 1 3 1 3 1 3 1
4 2 1 1 4 2 1 1
5 2 2 1 5 2 2 1
6 2 3 1 6 2 3 1
7 3 1 1 7 3 1 1
8 3 2 1 8 3 2 1
9 3 3 1 9 3 3 1
10 1 1 2 10 1 1 2
11 1 2 2 11 1 2 2
12 1 3 2 12 1 3 2
13 2 1 2 13 2 1 2
14 2 2 2 14 2 2 2
15 2 3 2 15 2 3 2
16 3 1 2 16 3 1 2
17 3 2 2 17 3 2 2
18 3 3 2 18 3 3 2
Job Collation Type = collatedDocuments(4) Job Collation Type = collatedDocuments(4)
JmJobImpressions Impressions sheetCompleted sheetCompleted JmJobImpressions Impressions sheetCompleted sheetCompleted
Completed CompletedCurrent CopyNumber DocumentNumber Completed CompletedCurrent CopyNumber DocumentNumber
Copy Copy
0 0 0 0 0 0 0 0
1 1 1 1 1 1 1 1
2 2 1 1 2 2 1 1
3 3 1 1 3 3 1 1
4 1 1 2 4 1 1 2
5 2 1 2 5 2 1 2
6 3 1 2 6 3 1 2
7 1 2 1 7 1 2 1
8 2 2 1 8 2 2 1
9 3 2 1 9 3 2 1
10 1 2 2 10 1 2 2
11 2 2 2 11 2 2 2
12 3 2 2 12 3 2 2
13 1 3 1 13 1 3 1
14 2 3 1 14 2 3 1
15 3 3 1 15 3 3 1
16 1 3 2 16 1 3 2
17 2 3 2 17 2 3 2
18 3 3 2 18 3 3 2
Job Collation Type = uncollatedDocuments(5) Job Collation Type = uncollatedDocuments(5)
jmJobImpressions Impressions sheetCompleted sheetCompleted jmJobImpressions Impressions sheetCompleted sheetCompleted
Completed CompletedCurrent CopyNumber DocumentNumber Completed CompletedCurrent CopyNumber DocumentNumber
Copy Copy
0 0 0 0 0 0 0 0
1 1 1 1 1 1 1 1
2 2 1 1 2 2 1 1
3 3 1 1 3 3 1 1
4 1 2 1 4 1 2 1
5 2 2 1 5 2 2 1
6 3 2 1 6 3 2 1
7 1 3 1 7 1 3 1
8 2 3 1 8 2 3 1
9 3 3 1 9 3 3 1
10 1 1 2 10 1 1 2
11 2 1 2 11 2 1 2
12 3 1 2 12 3 1 2
13 1 2 2 13 1 2 2
14 2 2 2 14 2 2 2
15 3 2 2 15 3 2 2
16 1 3 2 16 1 3 2
17 2 3 2 17 2 3 2
18 3 3 2 18 3 3 2
3.5 Job Identification 3.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
administrator to identify jobs of interest, such as jobURI, jobName, system administrator to identify jobs of interest, such as jobURI,
jobOriginatingHost, etc. In addition, there is a jmJobSubmissionID jobName, jobOriginatingHost, etc. In addition, there is a
object that is a text string table index. Being a table index allows a jmJobSubmissionID object that is a text string table index. Being a
monitoring application to quickly locate and identify a particular job table index allows a monitoring application to quickly locate and
of interest that was submitted from a particular client by the user identify a particular job of interest that was submitted from a
invoking the monitoring application without having to scan the entire particular client by the user invoking the monitoring application
job table. The Job Monitoring MIB needs to provide for identification without having to scan the entire job table. The Job Monitoring MIB
of the job at both sides of the job submission process. The primary needs to provide for identification of the job at both sides of the
identification point is the client side. The jmJobSubmissionID allows job submission process. The primary identification point is the
the monitoring application to identify the job of interest from all the client side. The jmJobSubmissionID allows the monitoring application
jobs currently "known" by the server or device. The value of to identify the job of interest from all the jobs currently "known"
jmJobSubmissionID can be assigned by either the client's local system by the server or device. The value of jmJobSubmissionID can be
or a downstream server or device. The point of assignment depends on assigned by either the client's local system or a downstream server
the job submission protocol in use. or device. The point of assignment depends on the job submission
protocol in use.
The server/device-side identifier, called the jmJobIndex object, SHALL The server/device-side identifier, called the jmJobIndex object,
be assigned by the SNMP Job Monitoring MIB agent when the server or SHALL be assigned by the SNMP Job Monitoring MIB agent when the
device accepts the jobs from submitting clients. The jmJobIndex object server or device accepts the jobs from submitting clients. The
allows the interested party to obtain all objects desired that relate jmJobIndex object allows the interested party to obtain all objects
to a particular job. See Section 3.2, entitled 'The Job Tables and the desired that relate to a particular job. See Section 3.2, entitled '
Oldest Active and Newest Active Indexes' for the specification of how The Job Tables and the Oldest Active and Newest Active Indexes' for
the agent SHALL assign the jmJobIndex values. the specification of how the agent SHALL assign the jmJobIndex
values.
The MIB provides a mapping table that maps each jmJobSubmissionID value The MIB provides a mapping table that maps each jmJobSubmissionID
to a corresponding jmJobIndex value generated by the agent, so that an value to a corresponding jmJobIndex value generated by the agent, so
application can determine the correct value for the jmJobIndex value that an application can determine the correct value for the
for the job of interest in a single Get operation, given the Job jmJobIndex value for the job of interest in a single Get operation,
Submission ID. See the jmJobIDGroup. given the Job Submission ID. See the jmJobIDGroup.
In some configurations there may be more than one application program In some configurations there may be more than one application program
that monitors the same job when the job passes from one network entity that monitors the same job when the job passes from one network
to another when it is submitted. See configuration 3. When there are entity to another when it is submitted. See configuration 3. When
multiple job submission IDs, each entity MAY supply an appropriate there are multiple job submission IDs, each entity MAY supply an
jmJobSubmissionID value. In this case there would be a separate entry appropriate jmJobSubmissionID value. In this case there would be a
in the jmJobSubmissionID table, one for each jmJobSubmissionID. All separate entry in the jmJobSubmissionID table, one for each
entries would map to the same jmJobIndex that contains the job data. jmJobSubmissionID. All entries would map to the same jmJobIndex that
When the job is deleted, it is up to the agent to remove all entries contains the job data. When the job is deleted, it is up to the
that point to the job from the jmJobSubmissionID table as well. agent to remove all entries that point to the job from the
jmJobSubmissionID table as well.
The jobName attribute provides a name that the user supplies as 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.
3.5.1 The Job Submission ID specifications 3.5.1 The Job Submission ID specifications
This section specifies the formats for each of the registered Job This section specifies the formats for each of the registered Job
Submission Ids. This format is used by the JmJobSubmissionIDTypeTC. Submission Ids. This format is used by the JmJobSubmissionIDTypeTC.
Each job submission ID is a fixed-length, 48-octet printable US-ASCII Each job submission ID is a fixed-length, 48-octet printable US-ASCII
[US-ASCII] coded character string containing no control characters, [US-ASCII] coded character string containing no control characters,
consisting of the following fields: consisting of the following fields:
octet 1: The format letter identifying the format. The US- octet 1: The format letter identifying the format. The
ASCII characters '0-9', 'A-Z', and 'a-z' are assigned in US-ASCII characters '0-9', 'A-Z', and 'a-z' are assigned
order giving 62 possible formats. in order giving 62 possible formats.
octets 2-40: A 39-character, US-ASCII trailing SPACE filled octets 2-40: A 39-character, US-ASCII trailing SPACE
field specified by the format letter, if the data is less filled field specified by the format letter, if the data
than 39 ASCII characters. is less than 39 ASCII characters.
octets 41-48: A sequential or random US-ASCII number to make octets 41-48: A sequential or random US-ASCII number to
the ID quasi-unique. make the ID quasi-unique.
If the client does not supply a job submission ID in the job submission If the client does not supply a job submission ID in the job
protocol, then the agent SHALL assign a job submission ID using any of submission protocol, then the agent SHALL assign a job submission ID
the standard formats that are reserved for the agent. Clients SHALL using any of the standard formats that are reserved for the agent.
not use formats that are reserved for agents and agents SHALL NOT use Clients SHALL not use formats that are reserved for agents and agents
formats that are reserved for clients, in order to reduce conflicts in SHALL NOT use formats that are reserved for clients, in order to
ID generation. See the description for which formats are reserved for reduce conflicts in ID generation. See the description for which
clients or for agents. formats are reserved for clients or for agents.
Registration of additional formats may be done following the procedures Registration of additional formats may be done following the
described in Section 3.7.3. procedures described in Section 3.7.3.
The format values defined at the time of completion of this The format values defined at the time of completion of this
specification are: specification are:
Format Format
Letter Description Letter Description
------ ------------ ------ ------------
'0' Job Owner generated by the server/device '0' Job Owner generated by the server/device
octets 2-40: The last 39 bytes of the jmJobOwner object. octets 2-40: The last 39 bytes of the jmJobOwner object.
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the agent. assigned by the agent.
This format is reserved for agents. This format is reserved for agents.
skipping to change at page 59, line 31 skipping to change at page 57, line 39
incorporates the job owner, SHALL use format '8', not incorporates the job owner, SHALL use format '8', not
format '0'. format '0'.
'1' Job Name '1' Job Name
octets 2-40: The last 39 bytes of the jobName attribute. octets 2-40: The last 39 bytes of the jobName attribute.
octets 41-48: The US-ASCII 8-decimal-digit random number octets 41-48: The US-ASCII 8-decimal-digit random number
assigned by the client. assigned by the client.
This format is reserved for clients. This format is reserved for clients.
'2' Client MAC address '2' Client MAC address
octets 2-40: The client MAC address: in hexadecimal with each octets 2-40: The client MAC address: in hexadecimal with
nibble of the 6 octet address being '0'-'9' or 'A' - 'F' each nibble of the 6 octet address being '0'-'9' or
(uppercase only). Most significant octet first. 'A' - 'F' (uppercase only). Most significant octet first.
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the client. assigned by the client.
This format is reserved for clients. This format is reserved for clients.
'3' Client URL '3' Client URL
octets 2-40: The last 39 bytes of the client URL [URI-spec]. octets 2-40: The last 39 bytes of the client URL [URI-spec].
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the client. assigned by the client.
This format is reserved for clients. This format is reserved for clients.
'4' Job URI '4' Job URI
octets 2-40: The last 39 bytes of the URI [URI-spec] assigned octets 2-40: The last 39 bytes of the URI [URI-spec]
by the server or device to the job when the job was assigned by the server or device to the job when the job
submitted for processing. was submitted for processing.
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the agent. assigned by the agent.
This format is reserved for agents. This format is reserved for agents.
'5' POSIX User Number '5' POSIX User Number
octets 2-40: The last 39 bytes of a user number, such as POSIX octets 2-40: The last 39 bytes of a user number, such as
user number. POSIX user number.
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the client. assigned by the client.
This format is reserved for clients. This format is reserved for clients.
'6' User Account Number '6' User Account Number
octets 2-40: The last 39 bytes of the user account number. octets 2-40: The last 39 bytes of the user account number.
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the client. assigned by the client.
This format is reserved for clients. This format is reserved for clients.
'7' DTMF Incoming FAX routing number '7' DTMF Incoming FAX routing number
octets 2-40: The last 39 bytes of the DTMF incoming FAX octets 2-40: The last 39 bytes of the DTMF incoming FAX
skipping to change at page 60, line 30 skipping to change at page 58, line 43
'8' Job Owner supplied by the client '8' Job Owner supplied by the client
octets 2-40: The last 39 bytes of the job owner name (that the octets 2-40: The last 39 bytes of the job owner name (that the
agent returns in the jmJobOwner object). agent returns in the jmJobOwner object).
octets 41-48: The US-ASCII 8-decimal-digit sequential number octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the client. assigned by the client.
This format is reserved for clients. See format '0' which is This format is reserved for clients. See format '0' which is
reserved for agents. reserved for agents.
'9' Host Name '9' Host Name
octets 2-40: The last 39 bytes of the host name with trailing octets 2-40: The last 39 bytes of the host name with trailing
SPACES that submitted the job to this server/device using a SPACES that submitted the job to this server/device using
protocol, such as LPD [RFC1179] which includes the host a protocol, such as LPD [RFC1179] which includes the host
name in the job submission protocol. name in the job submission protocol.
octets 41-48: The US-ASCII 8-decimal-digit leading zero octets 41-48: The US-ASCII 8-decimal-digit leading zero
representation of the job id generated by the submitting representation of the job id generated by the submitting
server (configuration 3) or the client (configuration 1 and server (configuration 3) or the client (configuration 1
2), such as in the LPD protocol. and 2), such as in the LPD protocol.
This format is reserved for clients. This format is reserved for clients.
'A' AppleTalk Protocol 'A' AppleTalk Protocol
octets 2-40: Contains the AppleTalk printer name, with the octets 2-40: Contains the AppleTalk printer name, with the
first character of the name in octet 2. AppleTalk printer first character of the name in octet 2. AppleTalk printer
names are a maximum of 31 characters. Any unused portion names are a maximum of 31 characters. Any unused portion
of this field shall be filled with spaces. of this field shall be filled with spaces.
octets 41-48: '00000XXX', where 'XXX' is the 3-digit US-ASCII octets 41-48: '00000XXX', where 'XXX' is the 3-digit US-ASCII
decimal representation of the Connection Id. decimal representation of the Connection Id.
This format is reserved for agents. This format is reserved for agents.
skipping to change at page 61, line 40 skipping to change at page 59, line 49
'D' Transport Independent Printer/System Interface (TIP/SI) 'D' Transport Independent Printer/System Interface (TIP/SI)
octets 2-40: Contains the Job Name from the Job Control-Start octets 2-40: Contains the Job Name from the Job Control-Start
Job (JC-SJ) command. If the Job Name portion is less than Job (JC-SJ) command. If the Job Name portion is less than
40 octets, the left-most character in the string shall 40 octets, the left-most character in the string shall
appear in octet position 2. Any unused portion of this appear in octet position 2. Any unused portion of this
field shall be filled with spaces. Otherwise, only the field shall be filled with spaces. Otherwise, only the
last 39 bytes shall be included. last 39 bytes shall be included.
octets 41-48: The US-ASCII 8-decimal-digit leading zero octets 41-48: The US-ASCII 8-decimal-digit leading zero
representation of the jmJobIndex assigned by the agent. representation of the jmJobIndex assigned by the agent.
This format is reserved for agents, since the agent supplies This format is reserved for agents, since the agent supplies
octets 41-48, though the client supplies the job name. See octets 41-48, though the client supplies the job name.
format '1' reserved to clients to submit job name ids in See format '1' reserved to clients to submit job name ids
which they supply octets 41-48. in which they supply octets 41-48.
'E' IPDS on the MVS or VSE platform 'E' IPDS on the MVS or VSE platform
octets 2-40: Contains bytes 2-27 of the XOH Define Group octets 2-40: Contains bytes 2-27 of the XOH Define Group
Boundary Group ID triplet. Octet position 2 MUST carry the Boundary Group ID triplet. Octet position 2 MUST carry
value x'01'. Bytes 28-40 MUST be filled with spaces. the value x'01'. Bytes 28-40 MUST be filled with spaces.
octets 41-48: The US-ASCII 8-decimal-digit leading zero octets 41-48: The US-ASCII 8-decimal-digit leading zero
representation of the jmJobIndex assigned by the agent. representation of the jmJobIndex assigned by the agent.
This format is reserved for agents, since the agent supplies This format is reserved for agents, since the agent supplies
octets 41-48, though the client supplies the job name. octets 41-48, though the client supplies the job name.
'F' IPDS on the VM platform 'F' IPDS on the VM platform
octets 2-40: Contains bytes 2-31 of the XOH Define Group octets 2-40: Contains bytes 2-31 of the XOH Define Group
Boundary Group ID triplet. Octet position 2 MUST carry the Boundary Group ID triplet. Octet position 2 MUST carry
value x'02'. Bytes 32-40 MUST be filled with spaces. the value x'02'. Bytes 32-40 MUST be filled with spaces.
octets 41-48: The US-ASCII 8-decimal-digit leading zero octets 41-48: The US-ASCII 8-decimal-digit leading zero
representation of the jmJobIndex assigned by the agent. representation of the jmJobIndex assigned by the agent.
This format is reserved for agents, since the agent supplies This format is reserved for agents, since the agent supplies
octets 41-48, though the client supplies the file name. octets 41-48, though the client supplies the file name.
'G' IPDS on the OS/400 platform 'G' IPDS on the OS/400 platform
octets 2-40: Contains bytes 2-36 of the XOH Define Group octets 2-40: Contains bytes 2-36 of the XOH Define Group
Boundary Group ID triplet. Octet position 2 MUST carry the Boundary Group ID triplet. Octet position 2 MUST carry
value x'03'. Bytes 37-40 MUST be filled with spaces. the value x'03'. Bytes 37-40 MUST be filled with spaces.
octets 41-48: The US-ASCII 8-decimal-digit leading zero octets 41-48: The US-ASCII 8-decimal-digit leading zero
representation of the jmJobIndex assigned by the agent. representation of the jmJobIndex assigned by the agent.
This format is reserved for agents, since the agent supplies This format is reserved for agents, since the agent supplies
octets 41-48, though the client supplies the job name. octets 41-48, though the client supplies the job name.
NOTE - the job submission id is only intended to be unique between a NOTE - the job submission id is only intended to be unique between a
limited set of clients for a limited duration of time, namely, for the limited set of clients for a limited duration of time, namely, for
life time of the job in the context of the server or device that is the life time of the job in the context of the server or device that
processing the job. Some of the formats include something that is is processing the job. Some of the formats include something that is
unique per client and a random number so that the same job submitted by unique per client and a random number so that the same job submitted
the same client will have a different job submission id. For other by the same client will have a different job submission id. For
formats, where part of the id is guaranteed to be unique for each other formats, where part of the id is guaranteed to be unique for
client, such as the MAC address or URL, a sequential number SHOULD each client, such as the MAC address or URL, a sequential number
suffice for each client (and may be easier for each client to manage). SHOULD suffice for each client (and may be easier for each client to
Therefore, the length of the job submission id has been selected to manage). Therefore, the length of the job submission id has been
reduce the probability of collision to an extremely low number, but is selected to reduce the probability of collision to an extremely low
not intended to be an absolute guarantee of uniqueness. None-the-less, number, but is not intended to be an absolute guarantee of
collisions are remotely possible, but without bad consequences, since uniqueness. None-the-less, collisions are remotely possible, but
this MIB is intended to be used only for monitoring jobs, not for without bad consequences, since this MIB is intended to be used only
controlling and managing them. for monitoring jobs, not for controlling and managing them.
3.6 Internationalization Considerations 3.6 Internationalization Considerations
This section describes the internationalization considerations included This section describes the internationalization considerations
in this MIB. included in this MIB.
3.6.1 Text generated by the server or device 3.6.1 Text generated by the server or device
There are a few objects and attributes generated by the server or There are a few objects and attributes generated by the server or
device that SHALL be represented using the Universal Multiple-Octet device that SHALL be represented using the Universal Multiple-Octet
Coded Character Set (UCS) [ISO-10646]. These objects and attributes Coded Character Set (UCS) [ISO-10646]. These objects and attributes
are always supplied (if implemented) by the agent, not by the job are always supplied (if implemented) by the agent, not by the job
submitting client: submitting client:
1. jmGeneralJobSetName object 1. jmGeneralJobSetName object
2. processingMessage(6) attribute 2. processingMessage(6) attribute
3. physicalDevice(32) (name value) attribute 3. physicalDevice(32) (name value) attribute
The character encoding scheme for representing these objects and The character encoding scheme for representing these objects and
attributes SHALL be UTF-8 as REQUIRED by RFC 2277 [RFC2277]. The attributes SHALL be UTF-8 as REQUIRED by RFC 2277 [RFC2277]. The '
'JmUTF8StringTC' textual convention is used to indicate UTF-8 text JmUTF8StringTC' textual convention is used to indicate UTF-8 text
strings. strings.
NOTE - For strings in 7-bit US-ASCII, there is no impact since the UTF- NOTE - For strings in 7-bit US-ASCII, there is no impact since the
8 representation of 7-bit ASCII is identical to the US-ASCII [US-ASCII] UTF-8 representation of 7-bit ASCII is identical to the US-ASCII
encoding. [US-ASCII] encoding.
The text contained in the processingMessage(6) attribute is generated The text contained in the processingMessage(6) attribute is generated
by the server/device. The natural language for the by the server/device. The natural language for the
processingMessage(6) attribute is identified by the processingMessage(6) attribute is identified by the
processingMessageNaturalLangTag(7) attribute. The processingMessageNaturalLangTag(7) attribute. The
processingMessageNaturalLangTag(7) attribute uses the processingMessageNaturalLangTag(7) attribute uses the
JmNaturalLanguageTagTC textual convention which SHALL conform to the JmNaturalLanguageTagTC textual convention which SHALL conform to the
language tag mechanism specified in RFC 1766 [RFC1766]. The language tag mechanism specified in RFC 1766 [RFC1766]. The
JmNaturalLanguageTagTC value is the same as the IPP [IPP-model] JmNaturalLanguageTagTC value is the same as the IPP [ipp-model] '
'naturalLanguage' attribute syntax. RFC 1766 specifies that a US-ASCII naturalLanguage' attribute syntax. RFC 1766 specifies that a US-
string consisting of the natural language followed by an optional ASCII string consisting of the natural language followed by an
country field. Both fields use the same two-character codes from ISO optional country field. Both fields use the same two-character codes
639 [ISO-639] and ISO 3166 [ISO-3166], respectively, that are used in from ISO 639 [ISO-639] and ISO 3166 [ISO-3166], respectively, that
the Printer MIB for identifying language and country. are used in the Printer MIB for identifying language and country.
Examples of the values of the processingMessageNaturalLangTag(7) Examples of the values of the processingMessageNaturalLangTag(7)
attribute include: attribute include:
1. 'en' for English 1. 'en' for English
2. 'en-us' for US English 2. 'en-us' for US English
3. 'fr' for French 3. 'fr' for French
4. 'de' for German 4. 'de' for German
3.6.2 Text supplied by the job submitter 3.6.2 Text supplied by the job submitter
All of the objects and attributes represented by the 'JmJobStringTC' All of the objects and attributes represented by the 'JmJobStringTC'
textual-convention are either (1) supplied in the job submission textual-convention are either (1) supplied in the job submission
protocol by the client that submits the job to the server or device or protocol by the client that submits the job to the server or device
(2) are defaulted by the server or device if the job submitting client or (2) are defaulted by the server or device if the job submitting
does not supply values. The agent SHALL represent these objects and client does not supply values. The agent SHALL represent these
attributes in the MIB either (1) in the coded character set as they objects and attributes in the MIB either (1) in the coded character
were submitted or (2) MAY convert the coded character set to another set as they were submitted or (2) MAY convert the coded character set
coded character set or encoding scheme. In any case, the resulting to another coded character set or encoding scheme. In any case, the
coded character set representation SHOULD be UTF-8 [UTF-8], but SHALL resulting coded character set representation SHOULD be UTF-8 [UTF-8],
be one in which the code positions from 0 to 31 is not used, 32 to 127 but SHALL be one in which the code positions from 0 to 31 is not
is US-ASCII [US-ASCII], 127 is not unused, and the remaining code used, 32 to 127 is US-ASCII [US-ASCII], 127 is not unused, and the
positions 128 to 255 represent single-byte or multi-byte graphic remaining code positions 128 to 255 represent single-byte or multi-
characters structured according to ISO 2022 [ISO-2022] or are unused. byte graphic characters structured according to ISO 2022 [ISO-2022]
or are unused.
The coded character set SHALL be one of the ones registered with IANA The coded character set SHALL be one of the ones registered with IANA
[IANA] and SHALL be identified by the jobCodedCharSet attribute in the [IANA] and SHALL be identified by the jobCodedCharSet attribute in
jmJobAttributeTable for the job. If the agent does not know what coded the jmJobAttributeTable for the job. If the agent does not know what
character set was used by the job submitting client, the agent SHALL coded character set was used by the job submitting client, the agent
either (1) return the 'unknown(2)' value for the jobCodedCharSet SHALL either (1) return the 'unknown(2)' value for the
attribute or (2) not return the jobCodedCharSet attribute for the job. jobCodedCharSet attribute or (2) not return the jobCodedCharSet
attribute for the job.
Examples of coded character sets which meet this criteria for use as Examples of coded character sets which meet this criteria for use as
the value of the jobCodedCharSet job attribute are: US-ASCII [US- the value of the jobCodedCharSet job attribute are: US-ASCII [US-
ASCII], ISO 8859-1 (Latin-1) [ISO-8859-1], any ISO 8859-n, HP Roman8, ASCII], ISO 8859-1 (Latin-1) [ISO-8859-1], any ISO 8859-n, HP Roman8,
IBM Code Page 850, Windows Default 8-bit set, UTF-8 [UTF-8], US-ASCII IBM Code Page 850, Windows Default 8-bit set, UTF-8 [UTF-8], US-ASCII
plus JIS X0208-1990 Japanese [JIS X0208], US-ASCII plus GB2312-1980 PRC plus JIS X0208-1990 Japanese [JIS X0208], US-ASCII plus GB2312-1980
Chinese [GB2312]. See the IANA registry of coded character sets [IANA PRC Chinese [GB2312]. See the IANA registry of coded character sets
charsets]. [IANA charsets].
Examples of coded character sets which do not meet this criteria are: Examples of coded character sets which do not meet this criteria are:
national 7-bit sets conforming to ISO 646 (except US-ASCII), EBCDIC, national 7-bit sets conforming to ISO 646 (except US-ASCII), EBCDIC,
and ISO 10646 (Unicode) [ISO-10646]. In order to represent Unicode and ISO 10646 (Unicode) [ISO-10646]. In order to represent Unicode
characters, the UTF-8 [UTF-8] encoding scheme SHALL be used which has characters, the UTF-8 [UTF-8] encoding scheme SHALL be used which has
been assigned the MIBenum value of '106' by IANA. been assigned the MIBenum value of '106' by IANA.
The jobCodedCharSet attribute uses the imported 'CodedCharSet' textual- The jobCodedCharSet attribute uses the imported 'CodedCharSet'
convention from the Printer MIB [printmib]. textual-convention from the Printer MIB [printmib].
The natural language for attributes represented by the textual- The natural language for attributes represented by the textual-
convention JmJobStringTC is identified either (1) by the convention JmJobStringTC is identified either (1) by the
jobNaturalLanguageTag(9) attribute or is keywords in US-English (as in jobNaturalLanguageTag(9) attribute or is keywords in US-English (as
IPP). A monitoring application SHOULD attempt to localize keywords in IPP). A monitoring application SHOULD attempt to localize
into the language of the user by means of some lookup mechanism. If keywords into the language of the user by means of some lookup
the keyword value is not known to the monitoring application, the mechanism. If the keyword value is not known to the monitoring
monitoring application SHOULD assume that the value is in the natural application, the monitoring application SHOULD assume that the value
language specified by the job's jobNaturalLanguageTag(9) attribute and is in the natural language specified by the job's
SHOULD present the value to its user as is. The jobNaturalLanguageTag(9) attribute and SHOULD present the value to
jobNaturalLanguageTag(9) attribute value SHALL have the same syntax and its user as is. The jobNaturalLanguageTag(9) attribute value SHALL
semantics as the processingMessageNaturalLangTag(7) attribute, except have the same syntax and semantics as the
that the jobNaturalLanguageTag(9) attribute identifies the natural processingMessageNaturalLangTag(7) attribute, except that the
language of attributes supplied by the job submitter instead of the jobNaturalLanguageTag(9) attribute identifies the natural language of
natural language of the processingMessage(6) attribute. See Section attributes supplied by the job submitter instead of the natural
3.6.1. language of the processingMessage(6) attribute. See Section 3.6.1.
3.6.3 'DateAndTime' for representing the date and time 3.6.3 'DateAndTime' for representing the date and time
This MIB also contains objects that are represented using the This MIB also contains objects that are represented using the
DateAndTime textual convention from SMIv2 [SMIv2-TC]. The job DateAndTime textual convention from SMIv2 [SMIv2-TC]. The job
management application SHALL display such objects in the locale of the management application SHALL display such objects in the locale of
user running the monitoring application. the user running the monitoring application.
3.7 IANA and PWG Registration Considerations 3.7 IANA and PWG Registration Considerations
This MIB does not require any additional registration schemes for IANA, This MIB does not require any additional registration schemes for
but does depend on registration schemes that other Internet standards IANA, but does depend on registration schemes that other Internet
track specifications have set up. The names of these IANA registration standards track specifications have set up. The names of these IANA
assignments under the /in-notes/iana/assignments/ path: registration assignments under the /in-notes/iana/assignments/ path:
1.printer-language-numbers - used as enums in the documentFormat(38) 1.printer-language-numbers - used as enums in the documentFormat(38)
attribute attribute
2.media-types - uses as keywords in the documentFormat(38) attribute 2.media-types - uses as keywords in the documentFormat(38) attribute
3.character-sets - used as enums in the jobCodedCharSet(8) attribute 3.character-sets - used as enums in the jobCodedCharSet(8) attribute
The Printer Working Group (PWG) will handle registration of additional The Printer Working Group (PWG) will handle registration of
enums after approving this standard, according to the procedures additional enums after approving this standard, according to the
described in this section: procedures described in this section:
3.7.1 PWG Registration of enums 3.7.1 PWG Registration of enums
This specification uses textual conventions to define enumerated values This specification uses textual conventions to define enumerated
(enums) and bit values. Enumerations (enums) and bit values are sets values (enums) and bit values. Enumerations (enums) and bit values
of symbolic values defined for use with one or more objects or are sets of symbolic values defined for use with one or more objects
attributes. All enumeration sets and bit value sets are assigned a or attributes. All enumeration sets and bit value sets are assigned
symbolic data type name (textual convention). As a convention the a symbolic data type name (textual convention). As a convention the
symbolic name ends in "TC" for textual convention. These enumerations symbolic name ends in "TC" for textual convention. These
are defined at the beginning of the MIB module specification. enumerations are defined at the beginning of the MIB module
specification.
The PWG has defined several type of enumerations for use in the Job The PWG has defined several type of enumerations for use in the Job
Monitoring MIB and the Printer MIB[print-mib]. These types differ in Monitoring MIB and the Printer MIB [print-mib]. These types differ
the method employed to control the addition of new enumerations. in the method employed to control the addition of new enumerations.
Throughout this document, references to "type n enum", where n can be Throughout this document, references to "type n enum", where n can be
1, 2 or 3 can be found in the various tables. The definitions of these 1, 2 or 3 can be found in the various tables. The definitions of
types of enumerations are: these types of enumerations are:
3.7.1.1 Type 1 enumerations 3.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.
There are no type 1 enums in the current draft. There are no type 1 enums in the current document.
3.7.1.2 Type 2 enumerations 3.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
registered with the PWG. registered with the PWG.
The following type 2 enums are contained in the current draft : The following type 2 enums are contained in the current document:
1. JmUTF8StringTC 1. JmUTF8StringTC
2. JmJobStringTC 2. JmJobStringTC
3. JmNaturalLanguageTagTC 3. JmNaturalLanguageTagTC
4. JmTimeStampTC 4. JmTimeStampTC
5. JmFinishingTC [same enum values as IPP "finishing" attribute] 5. JmFinishingTC [same enum values as IPP "finishing" attribute]
6. JmPrintQualityTC [same enum values as IPP "print-quality" 6. JmPrintQualityTC [same enum values as IPP "print-quality"
attribute] attribute]
7. JmTonerEconomyTC 7. JmTonerEconomyTC
8. JmMediumTypeTC 8. JmMediumTypeTC
9. JmJobSubmissionIDTypeTC 9. JmJobSubmissionIDTypeTC
10.JmJobCollationTypeTC 10.JmJobCollationTypeTC
11.JmJobStateTC [same enum values as IPP "job-state" attribute] 11.JmJobStateTC [same enum values as IPP "job-state" attribute]
12.JmAttributeTypeTC 12.JmAttributeTypeTC
For those textual conventions that have the same enum values as the For those textual conventions that have the same enum values as the
indicated IPP Job attribute are simultaneously registered by the PWG indicated IPP Job attribute are simultaneously registered by the PWG
for use with IPP [ipp-model] and the Job Monitoring MIB. for use with IPP [ipp-model] and the Job Monitoring MIB.
3.7.1.3 Type 3 enumeration 3.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 through the PWG without PWG review. registered through the PWG without PWG review.
There are no type 3 enums in the current draft. There are no type 3 enums in the current document.
3.7.2 PWG Registration of type 2 bit values 3.7.2 PWG Registration of type 2 bit values
This draft contains the following type 2 bit value textual-conventions: This memo contains the following type 2 bit value textual-
1. JmJobServiceTypesTC conventions:
2. JmJobStateReasons1TC 1. JmJobServiceTypesTC
3. JmJobStateReasons2TC 2. JmJobStateReasons1TC
4. JmJobStateReasons3TC 3. JmJobStateReasons2TC
5. JmJobStateReasons4TC 4. JmJobStateReasons3TC
5. JmJobStateReasons4TC
These textual-conventions are defined as bits in an Integer so that These textual-conventions are defined as bits in an Integer so that
they can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4) they can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4)
attributes are defined as bit values using the corresponding attributes are defined as bit values using the corresponding
JmJobStateReasonsNTC textual-conventions. JmJobStateReasonsNTC textual-conventions.
The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit
values follow the procedures for a type 2 enum as specified in Section values follow the procedures for a type 2 enum as specified in
3.7.1.2. Section 3.7.1.2.
3.7.3 PWG Registration of Job Submission Id Formats 3.7.3 PWG Registration of Job Submission Id Formats
In addition to enums and bit values, this specification assigns a In addition to enums and bit values, this specification assigns a
single ASCII digit or letter to various job submission ID formats. See single ASCII digit or letter to various job submission ID formats.
the JmJobSubmissionIDTypeTC textual-convention and the object. The See the JmJobSubmissionIDTypeTC textual-convention and the object.
registration of JobSubmissionID format numbers follows the procedures The registration of JobSubmissionID format numbers follows the
for a type 2 enum as specified in Section 3.7.1.2. procedures for a type 2 enum as specified in Section 3.7.1.2.
3.7.4 PWG Registration of MIME types/sub-types for document-formats 3.7.4 PWG Registration of MIME types/sub-types for document-formats
The documentFormat(38) attribute has MIME type/sub-type values for The documentFormat(38) attribute has MIME type/sub-type values for
indicating document formats which IANA registers as "media type" names. indicating document formats which IANA registers as "media type"
The values of the documentFormat(38) attribute are the same as the names. The values of the documentFormat(38) attribute are the same
corresponding Internet Printing Protocol (IPP) "document-format" Job as the corresponding Internet Printing Protocol (IPP) "document-
attribute values [ipp-model]. format" Job attribute values [ipp-model].
3.8 Security Considerations 3.8 Security Considerations
3.8.1 Read-Write objects 3.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 considerations. If another MIB augments this MIB, that MIB might
accept SNMP Write operations to objects in that MIB whose effect is to accept SNMP Write operations to objects in that MIB whose effect is
modify the values of read-only objects in this MIB. However, that MIB to modify the values of read-only objects in this MIB. However, that
SHALL have to support the required access control in order to achieve MIB SHALL have to support the required access control in order to
security, not this MIB. achieve security, not this MIB.
3.8.2 Read-Only Objects In Other User's Jobs 3.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
objects from other jobs, such as the jmJobKOctetsPerCopyRequested and minimal objects from other jobs, such as the
jmJobKOctetsProcessed objects, so that a user can tell how busy a jmJobKOctetsPerCopyRequested and jmJobKOctetsProcessed objects, so
printer is. Other sites MAY allow all unprivileged users to see all that a user can tell how busy a printer is. Other sites MAY allow
objects of all jobs. This MIB does not require, nor does it specify all unprivileged users to see all objects of all jobs. This MIB does
how, such restrictions would be implemented. A monitoring application not require, nor does it specify how, such restrictions would be
SHOULD enforce the site security policy with respect to returning implemented. A monitoring application SHOULD enforce the site
information to an unprivileged end user that is using the monitoring security policy with respect to returning information to an
application to monitor jobs that do not belong to that user, i.e., the unprivileged end user that is using the monitoring application to
jmJobOwner object in the jmJobTable does not match the user's user monitor jobs that do not belong to that user, i.e., the jmJobOwner
name. object in the jmJobTable does not match the user's user name.
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
of all jobs, independent of the policy for unprivileged users. objects of all jobs, independent of the policy for unprivileged
users.
3.9 Notifications 3.9 Notifications
This MIB does not specify any notifications. For simplicity, This MIB does not specify any notifications. For simplicity,
management applications are expected to poll for status. The management applications are expected to poll for status. The
jmGeneralJobPersistence and jmGeneralAttributePersistence objects jmGeneralJobPersistence and jmGeneralAttributePersistence objects
assist an application to determine the polling rate. The resulting assist an application to determine the polling rate. The resulting
network traffic is not expected to be significant. network traffic is not expected to be significant.
4 MIB specification 4 MIB specification
The following pages constitute the actual Job Monitoring MIB. The following pages constitute the actual Job Monitoring MIB.
Job-Monitoring-MIB DEFINITIONS ::= BEGIN Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, enterprises, MODULE-IDENTITY, OBJECT-TYPE, enterprises,
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
skipping to change at page 69, line 55 skipping to change at page 68, line 10
Implementers of this specification are encouraged to join the Implementers of this specification are encouraged to join the
jmp mailing list in order to participate in discussions on any jmp mailing list in order to participate in discussions on any
clarifications needed and registration proposals being reviewed clarifications needed and registration proposals being reviewed
in order to achieve consensus." in order to achieve consensus."
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.
Version: 1.0" Version: 1.0"
-- revision history
REVISION "9902190000Z"
DESCRIPTION " This version published as RFC 2707"
::= { enterprises pwg(2699) mibs(1) jobmonMIB(1) } ::= { enterprises pwg(2699) mibs(1) jobmonMIB(1) }
-- Textual conventions for this MIB module -- Textual conventions for this MIB module
JmUTF8StringTC ::= TEXTUAL-CONVENTION JmUTF8StringTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a" DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To facilitate internationalization, this TC represents "To facilitate internationalization, this TC represents
information taken from the ISO/IEC IS 10646-1 character set, information taken from the ISO/IEC IS 10646-1 character set,
skipping to change at page 73, line 16 skipping to change at page 71, line 35
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Print quality settings. "Print quality settings.
These values are the same as the enum values of the IPP 'print- These values are the same as the enum values of the IPP 'print-
quality' attribute. See Section 3.7.1.2. quality' attribute. See Section 3.7.1.2.
This is a type 2 enumeration. See Section 3.7.1.2." This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- Not one of the specified or registered other(1), -- Not one of the specified or registered
-- values. -- 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 normal(4), -- Normal or intermediate quality on the
-- printer. -- printer.
high(5) -- Highest quality available on the printer. high(5) -- Highest quality available on the printer.
} }
JmPrinterResolutionTC ::= TEXTUAL-CONVENTION JmPrinterResolutionTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Printer resolutions. "Printer resolutions.
Nine octets consisting of two 4-octet SIGNED-INTEGERs followed Nine octets consisting of two 4-octet SIGNED-INTEGERs followed
by a SIGNED-BYTE. The values are the same as those specified by a SIGNED-BYTE. The values are the same as those specified
skipping to change at page 78, line 10 skipping to change at page 76, line 30
attributes SHALL indicate why the job is no longer a attributes SHALL indicate why the job is no longer a
candidate for processing. The reasons are represented as candidate for processing. The reasons are represented as
bits in the jmJobStateReasons1 object and/or bits in the jmJobStateReasons1 object and/or
jobStateReasonsN (N=2..4) attributes. See the jobStateReasonsN (N=2..4) attributes. See the
JmJobStateReasonsNTC (N=1..4) textual convention for the JmJobStateReasonsNTC (N=1..4) textual convention for the
specification of each reason. specification of each reason.
processing(5), processing(5),
One or more of: One or more of:
1. the job is using, or is attempting to use, one or more 1. the job is using, or is attempting to use, one or
purely software processes that are analyzing, creating, or more purely software processes that are analyzing,
interpreting a PDL, etc., creating, or interpreting a PDL, etc.,
2. the job is using, or is attempting to use, one or more 2. the job is using, or is attempting to use, one or
hardware devices that are interpreting a PDL, making marks more hardware devices that are interpreting a PDL,
on a medium, and/or performing finishing, such as stapling, making mark on a medium, and/or performing finishing,
etc., OR such as stapling, etc., OR
3. (configuration 2) the server has made the job ready for 3. (configuration 2) the server has made the job ready
printing, but the output device is not yet printing it, for printing, but the output device is not yet printing
either because the job hasn't reached the output device or it, either because the job hasn't reached the output
because the job is queued in the output device or some device or because the job is queued in the output
other spooler, awaiting the output device to print it. device or some other spooler, awaiting the output
device to print it.
When the job is in the processing state, the entire job When the job is in the processing state, the entire job
state includes the detailed status represented in the state includes the detailed status represented in the
device MIB indicated by the hrDeviceIndex value of the device MIB indicated by the hrDeviceIndex value of the
job's physicalDevice attribute, if the agent implements job's physicalDevice attribute, if the agent implements
such a device MIB. such a device MIB.
Implementations MAY, though they NEED NOT, include Implementations MAY, though they NEED NOT, include
additional values in the job's jmJobStateReasons1 object to additional values in the job's jmJobStateReasons1 object
indicate the progress of the job, such as adding the to indicate the progress of the job, such as adding the
jobPrinting value to indicate when the device is actually jobPrinting value to indicate when the device is actually
making marks on a medium and/or the processingToStopPoint making marks on a medium and/or the processingToStopPoint
value to indicate that the server or device is in the value to indicate that the server or device is in the
process of canceling or aborting the job. process of canceling or aborting the job.
processingStopped(6), processingStopped(6),
The job has stopped while processing for any number of The job has stopped while processing for any number of
reasons and will return to the processing state as soon as reasons and will return to the processing state as soon
the reasons are no longer present. as the reasons are no longer present.
The job's jmJobStateReasons1 object and/or the job's The job's jmJobStateReasons1 object and/or the job's
jobStateReasonsN (N=2..4) attributes MAY indicate why the jobStateReasonsN (N=2..4) attributes MAY indicate why the
job has stopped processing. For example, if the output job has stopped processing. For example, if the output
device is stopped, the deviceStopped value MAY be included device is stopped, the deviceStopped value MAY be
in the job's jmJobStateReasons1 object. included in the job's jmJobStateReasons1 object.
NOTE - When an output device is stopped, the device usually NOTE - When an output device is stopped, the device
indicates its condition in human readable form at the usually indicates its condition in human readable form
device. The management application can obtain more at the device. The management application can obtain
complete device status remotely by querying the appropriate more complete device status remotely by querying the
device MIB using the job's deviceIndex attribute(s), if the appropriate device MIB using the job's deviceIndex
agent implements such a device MIB attribute(s), if the agent implements such a device MIB
canceled(7), canceled(7),
A client has canceled the job and the server or device has A client has canceled the job and the server or device
completed canceling the job AND all MIB objects and has completed canceling the job AND all MIB objects and
attributes have reached their final values for the job. attributes have reached their final values for the job.
While the server or device is canceling the job, the job's While the server or device is canceling the job, the
jmJobStateReasons1 object SHOULD contain the job's jmJobStateReasons1 object SHOULD contain the
processingToStopPoint value and one of the canceledByUser, processingToStopPoint value and one of the
canceledByOperator, or canceledAtDevice values. The
canceledByUser, canceledByOperator, or canceledAtDevice canceledByUser, canceledByOperator, or canceledAtDevice
values remain while the job is in the canceled state. values. The canceledByUser, canceledByOperator, or
canceledAtDevice values remain while the job is in the
canceled state.
aborted(8), aborted(8),
The job has been aborted by the system, usually while the The job has been aborted by the system, usually while the
job was in the processing or processingStopped state and job was in the processing or processingStopped state and
the server or device has completed aborting the job AND all the server or device has completed aborting the job AND
MIB objects and attributes have reached their final values all MIB objects and attributes have reached their final
for the job. While the server or device is aborting the values for the job. While the server or device is
job, the job's jmJobStateReasons1 object MAY contain the aborting the job, the job's jmJobStateReasons1 object MAY
processingToStopPoint and abortedBySystem values. If contain the processingToStopPoint and abortedBySystem
implemented, the abortedBySystem value SHALL remain while values. If implemented, the abortedBySystem value SHALL
the job is in the aborted state. remain while the job is in the aborted state.
completed(9) completed(9)
The job has completed successfully or with warnings or The job has completed successfully or with warnings or
errors after processing and all of the media have been errors after processing and all of the media have been
successfully stacked in the appropriate output bin(s) AND successfully stacked in the appropriate output bin(s) AND
all MIB objects and attributes have reached their final all MIB objects and attributes have reached their final
values for the job. The job's jmJobStateReasons1 object values for the job. The job's jmJobStateReasons1 object
SHOULD contain one of: completedSuccessfully, SHOULD contain one of: completedSuccessfully,
completedWithWarnings, or completedWithErrors values. completedWithWarnings, or completedWithErrors values.
skipping to change at page 108, line 6 skipping to change at page 104, line 6
OBJECTS { OBJECTS {
jmAttributeValueAsInteger, jmAttributeValueAsOctets } jmAttributeValueAsInteger, jmAttributeValueAsOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The attribute group." "The attribute group."
::= { jmMIBGroups 4 } ::= { jmMIBGroups 4 }
END END
5 Appendix A - Implementing the Job Life Cycle 5 Appendix A - Implementing the Job Life Cycle
The job object has well-defined states and client operations that The job object has well-defined states and client operations that
affect the transition between the job states. Internal server and affect the transition between the job states. Internal server and
device actions also affect the transitions of the job between the job device actions also affect the transitions of the job between the job
states. These states and transitions are referred to as the job's life states. These states and transitions are referred to as the job's
cycle. life cycle.
Not all implementations of job submission protocols have all of the Not all implementations of job submission protocols have all of the
states of the job model specified here. The job model specified here states of the job model specified here. The job model specified here
is intended to be a superset of most implementations. It is the is intended to be a superset of most implementations. It is the
purpose of the agent to map the particular implementation's job life purpose of the agent to map the particular implementation's job life
cycle onto the one specified here. The agent MAY omit any states not cycle onto the one specified here. The agent MAY omit any states not
implemented. Only the processing and completed states are required to implemented. Only the processing and completed states are required
be implemented by an agent. However, a conforming management to be implemented by an agent. However, a conforming management
application SHALL be prepared to accept any of the states in the job application SHALL be prepared to accept any of the states in the job
life cycle specified here, so that the management application can life cycle specified here, so that the management application can
interoperate with any conforming agent. interoperate with any conforming agent.
The job states are intended to be user visible. The agent SHALL make The job states are intended to be user visible. The agent SHALL make
these states visible in the MIB, but only for the subset of job states these states visible in the MIB, but only for the subset of job
that the implementation has. Some implementations MAY need to have states that the implementation has. Some implementations MAY need to
sub-states of these user-visible states. The jmJobStateReasons1 object have sub-states of these user-visible states. The jmJobStateReasons1
and the jobStateReasonsN (N=2..4) attributes can be used to represent object and the jobStateReasonsN (N=2..4) attributes can be used to
the sub-states of the jobs. represent the sub-states of the jobs.
Job states are intended to last a user-visible length of time in most Job states are intended to last a user-visible length of time in most
implementations. However, some jobs may pass through some states in implementations. However, some jobs may pass through some states in
zero time in some situations and/or in some implementations. zero time in some situations and/or in some implementations.
The job model does not specify how accounting and auditing is The job model does not specify how accounting and auditing is
implemented, except to assume that accounting and auditing logs are implemented, except to assume that accounting and auditing logs are
separate from the job life cycle and last longer than job entries in separate from the job life cycle and last longer than job entries in
the MIB. Jobs in the completed, aborted, or canceled states are not the MIB. Jobs in the completed, aborted, or canceled states are not
logs, since jobs in these states are accessible via SNMP protocol logs, since jobs in these states are accessible via SNMP protocol
operations and SHALL be removed from the Job Monitoring MIB tables operations and SHALL be removed from the Job Monitoring MIB tables
after a site-settable or implementation-defined period of time. An after a site-settable or implementation-defined period of time. An
accounting application MAY copy accounting information incrementally to accounting application MAY copy accounting information incrementally
an accounting log as a job processes, or MAY be copied while the job is to an accounting log as a job processes, or MAY be copied while the
in the canceled, aborted, or completed states, depending on job is in the canceled, aborted, or completed states, depending on
implementation. The same is true for auditing logs. implementation. The same is true for auditing logs.
The jmJobState object specifies the standard job states. The normal The jmJobState object specifies the standard job states. The normal
job state transitions are shown in the state transition diagram job state transitions are shown in the state transition diagram
presented in Table 1. presented in Figure 4.
6 APPENDIX B - Support of Job Submission Protocols 6 APPENDIX B - Support of Job Submission Protocols
A companion PWG document, entitled "Job Submission Protocol Mapping A companion PWG document, entitled "Job Submission Protocol Mapping
Recommendations for the Job Monitoring MIB" [protomap] contains the Recommendations for the Job Monitoring MIB" [protomap] contains the
recommended usage of each of the objects and attributes in this MIB recommended usage of each of the objects and attributes in this MIB
with a number of job submission protocols. In particular, which job with a number of job submission protocols. In particular, which job
submission ID format should be used is indicated for each job submission ID format should be used is indicated for each job
submission protocol. submission protocol.
Some job submission protocols have support for the client to specify a Some job submission protocols have support for the client to specify
job submission ID. A second approach is to enhance the document format a job submission ID. A second approach is to enhance the document
to embed the job submission ID in the document data. This second format to embed the job submission ID in the document data. This
approach is independent of the job submission protocol. This appendix second approach is independent of the job submission protocol. This
lists some examples of these approaches. appendix lists some examples of these approaches.
Some PJL implementations wrap a banner page as a PJL job around a job Some PJL implementations wrap a banner page as a PJL job around a job
submitted by a client. If this results in multiple job submission IDs, submitted by a client. If this results in multiple job submission
the agent SHALL create multiple jmJobIDEntry rows in the jmJobIDTable IDs, the agent SHALL create multiple jmJobIDEntry rows in the
that each point to the same job entry in the job tables. See the jmJobIDTable that each point to the same job entry in the job tables.
specification of the jmJobIDEntry. See the specification of the jmJobIDEntry.
7 References 7 References
[BCP-11] Bradner S., Hovey R., "The Organizations Involved in the IETF [BCP-11] Bradner S. and R. Hovey, "The Organizations
Standards Process", 1996/10/29 (RFC 2028) Involved in the IETF Standards Process", BCP 11,
RFC 2028, October 1996.
[GB2312] GB 2312-1980, "Chinese People's Republic of China (PRC) mixed
one byte and two byte coded character set"
[hr-mib] P. Grillo, S. Waldbusser, "Host Resources MIB", RFC 1514,
September 1993
[iana] J. Reynolds, and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
ISI, October 1994.
[IANA-charsets] Coded Character Sets registered by IANA and assigned an
enum value for use in the CodedCharSet textual convention imported from
the Printer MIB. See ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets
[iana-media-types] IANA Registration of MIME media types (MIME content
types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/
[ipp-model] Internet Printing Protocol/1.0: Model and Semantics, work
in progress on the IETF standards track. See draft-ietf-ipp-model-
09.txt. See also http://www.pwg.org/ipp/index.html
[ISO-639] ISO 639:1988 (E/F) - Code for Representation of names of
languages - The International Organization for Standardization, 1st
edition, 1988.
[ISO-646] ISO/IEC 646:1991, "Information technology -- ISO 7-bit coded
character set for information interchange", JTC1/SC2.
[ISO-2022] ISO/IEC 2022:1994 - "Information technology -- Character
code structure and extension techniques", JTC1/SC2.
[ISO-3166] ISO 3166:1988 (E/F) - Codes for representation of names of
countries - The International Organization for Standardization, 3rd
edition, 1988-08-15."
[ISO-8859-1] ISO/IEC 8859-1:1987, "Information technology -- 8-bit
single byte coded graphic character sets - Part 1: Latin alphabet No.
1, JTC1/SC2."
[ISO-10646] ISO/IEC 10646-1:1993, "Information technology -- Universal
Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and
Basic Multilingual Plane, JTC1/SC2.
[iso-dpa] ISO/IEC 10175-1:1996 "Information technology -- Text and
Office Systems -- Document Printing Application (DPA) -- Part 1:
Abstract service definition and procedures. See
ftp://ftp.pwg.org/pub/pwg/dpa/
[JIS X0208] JIS X0208-1990, "Japanese two byte coded character set."
[mib-II] MIB-II, RFC 1213.
[print-mib] Smith, R., Wright, F., Hastings, T., Zilles, S. and
Gyllenskog, J., "Printer MIB", RFC 1759, proposed IETF standard, March
1995. See also [print-mib-draft].
[print-mib-draft] Turner, R., "Printer MIB", work in progress, on the [GB2312] GB 2312-1980, "Chinese People's Republic of China
standards track as a draft standard: <draft-ietf-printmib-mib-info- (PRC) mixed one byte and two byte coded character
04.txt>, January 22, 1999. set"
[protomap] Bergman, R., "Job Submission Protocol Mapping [hr-mib] Grillo, P. and S. Waldbusser, "Host Resources
Recommendations for the Job Monitoring MIB," work in progress as an MIB", RFC 1514, September 1993.
informational RFC. See <draft-bergman-printmib-job-protomap-03.txt>,
February 10, 1998.
[pwg] The Printer Working Group is a printer industry consortium open [iana] Reynolds, J. and J. Postel, "Assigned Numbers",
to any individuals. For more information, access the PWG web page: STD 2, RFC 1700, October 1994.
http://www.pwg.org
[RFC1179] McLaughlin, L., III, "Line Printer Daemon Protocol", RFC [IANA-charsets] Coded Character Sets registered by IANA and
1179, August 1990 assigned an enum value for use in the CodedCharSet
[RFC1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform textual convention imported from the Printer MIB.
Resource Locators (URL)", RFC 1738, December 1994. See ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets
[RFC1766] Avelstrand, H., "Tags for the Identification of Languages", [iana-media-types] IANA Registration of MIME media types (MIME
RFC 1766, March 1995. content types/subtypes). See
ftp://ftp.isi.edu/in-notes/iana/assignments/
[RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", [ipp-model] deBry, R., Hastings, T., Herriot, R., Issaacson,
RFC 2026, October 1996. S. and P. Powell, "The Internet Printing
Protocol/1.0: Model and Semantics", RFC 2566,
April 1999.
[RFC2119] S. Bradner, "Keywords for use in RFCs to Indicate Requirement [ISO-639] ISO 639:1988 (E/F) - Code for Representation of
Levels", RFC 2119, March 1997. names of languages - The International
Organization for Standardization, 1st edition,
1988.
[RFC2277] H. Alvestrand, "IETF Policy on Character Sets and [ISO-646] ISO/IEC 646:1991, "Information technology -- ISO
Languages" RFC 2277, January 1998. 7-bit coded character set for information
interchange", JTC1/SC2.
[RFC2278] N. Freed, J. Postel: "IANA CharSet Registration [ISO-2022] ISO/IEC 2022:1994 - "Information technology --
Procedures", RFC 2278, January 1998. Character code structure and extension
techniques", JTC1/SC2.
[SMIv2-SMI] J. Case, et al. "Structure of Management Information for [ISO-3166] ISO 3166:1988 (E/F) - Codes for representation of
Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC names of countries - The International
1902, January 1996. Organization for Standardization, 3rd edition,
1988-08-15."
[SMIv2-TC] J. Case, et al. "Textual Conventions for Version 2 of the [ISO-8859-1] ISO/IEC 8859-1:1987, "Information technology --
Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 8-bit single byte coded graphic character sets -
Part 1: Latin alphabet No. 1, JTC1/SC2."
[tipsi] IEEE 1284.1, Transport-independent Printer System Interface [ISO-10646] ISO/IEC 10646-1:1993, "Information technology --
(TIPSI). Universal Multiple-Octet Coded Character Set (UCS)
- Part 1: Architecture and Basic Multilingual
Plane, JTC1/SC2.
[URI-spec] Berners-Lee, T., Fielding, R., Masinter, L., "Uniform [iso-dpa] ISO/IEC 10175-1:1996 "Information technology --
Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. Text and Office Systems -- Document Printing
Application (DPA) -- Part 1: Abstract service
definition and procedures. See
ftp://ftp.pwg.org/pub/pwg/dpa/
[US-ASCII] Coded Character Set - 7-bit American Standard Code for [JIS X0208] JIS X0208-1990, "Japanese two byte coded character
Information Interchange, ANSI X3.4-1986. set."
[UTF-8] F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC [mib-II] McCloghrie, K. and M. Rose, "Management
2279, January 1998. Information Base for Network Management of
TCP/IP-based internets: MIB-II", STD 17, RFC 1213,
March 1991.
8 Notices [print-mib] Smith, R., Wright, F., Hastings, T., Zilles, S.
and J. Gyllenskog, "Printer MIB", RFC 1759, March
1995.
The IETF takes no position regarding the validity or scope of any [print-mib-draft] Turner, R., "Printer MIB", Work in Progress,
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11[BCP-11]. Copies of claims
of rights made available for publication and any assurances of licenses
to be made available, or the result of an attempt made to obtain a
general license or permission for the use of such proprietary rights by
implementers or users of this specification can be obtained from the
IETF Secretariat.
The IETF invites any interested party to bring to its attention any [protomap] Bergman, R., "Job Submission Protocol Mapping
copyrights, patents or patent applications, or other proprietary rights Recommendations for the Job Monitoring MIB", RFC
which may cover technology that may be required to practice this 2708, November 1999.
standard. Please address the information to the IETF Executive
Director.
Copyright (C) The Internet Society (1999). All Rights Reserved. [pwg] The Printer Working Group is a printer industry
consortium open to any individuals. For more
information, access the PWG web page:
http://www.pwg.org
This document and translations of it may be copied and furnished to [RFC1179] McLaughlin, L., III, "Line Printer Daemon
others, and derivative works that comment on or otherwise explain it or Protocol", RFC 1179, August 1990.
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of developing
Internet standards in which case the procedures for copyrights defined
in the Internet Standards process must be followed, or as required to
translate it into languages other than English.
The limited permissions granted above are perpetual and will not be [RFC1738] Berners-Lee, T., Masinter, L. and M., McCahill,
revoked by the Internet Society or its successors or assigns. "Uniform Resource Locators (URL)", RFC 1738,
December 1994.
This document and the information contained herein is provided on an [RFC1766] Avelstrand, H., "Tags for the Identification of
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING Languages", RFC 1766, March 1995.
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
9 Author's Addresses [RFC2026] Bradner, S., "The Internet Standards Process --
Ron Bergman Revision 3", BCP 9, RFC 2026, October 1996.
Dataproducts Corp.
1757 Tapo Canyon Road
Simi Valley, CA 93063-3394
Phone: 805-578-4421 [RFC2119] Bradner, S., "Keywords for use in RFCs to Indicate
Fax: 805-578-4001 Requirement Levels", BCP 14, RFC 2119, March 1997.
Email: rbergman@dpc.com
Tom Hastings [RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Xerox Corporation, ESAE-231 Languages", BCP 18, RFC 2277, January 1998.
737 Hawaii St.
El Segundo, CA 90245 [RFC2278] Freed, N. and J. Postel, "IANA CharSet
Registration Procedures", BCP 19, RFC 2278,
January 1998.
Phone: 310-333-6413 [SMIv2-SMI] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
Fax: 310-333-5514 "Structure of Management Information Version 2
EMail: hastings@cp10.es.xerox.com (SMIv2)", STD 58, RFC 2578, April 1999.
Scott A. Isaacson [SMIv2-TC] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
Novell, Inc. "Textual Conventions for SMIv2", STD 58, RFC 2579,
122 E 1700 S April 1999.
Provo, UT 84606
Phone: 801-861-7366 [tipsi] IEEE 1284.1, Transport-independent Printer System
Fax: 801-861-4025 Interface (TIPSI).
EMail: scott_isaacson@novell.com
Harry Lewis [URI-spec] Berners-Lee, T., Fielding, R. and L. Masinter,
IBM Corporation "Uniform Resource Identifiers (URI), Generic
6300 Diagonal Hwy Syntax", RFC 2396, August 1998.
Boulder, CO 80301
Phone: (303) 924-5337 [US-ASCII] Coded Character Set - 7-bit American Standard Code
Fax: for Information Interchange, ANSI X3.4-1986.
Email: harryl@us.ibm.com
Send questions and comments to the Printer Working Group (PWG) [UTF-8] Yergeau, F., "UTF-8, a transformation format of
using the Job Monitoring Project (JMP) Mailing List: jmp@pwg.org ISO 10646", RFC 2279, January 1998.
To learn how to subscribe, send email to: jmp-request@pwg.org 8 Notices
Implementers of this specification are encouraged to join the jmp The IETF takes no position regarding the validity or scope of any
mailing list in order to participate in discussions on any intellectual property or other rights that might be claimed to
clarifications needed and registration proposals for additional pertain to the implementation or use of the technology described in
attributes and values being reviewed in order to achieve consensus. this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [BCP-11].
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat.
For further information, access the PWG web page under "JMP": The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
http://www.pwg.org/ 9 Authors' Addresses
Other Participants: Ron Bergman
Chuck Adams - Tektronix Dataproducts Corp.
Jeff Barnett - IBM 1757 Tapo Canyon Road
Keith Carter, IBM Corporation Simi Valley, CA 93063-3394
Jeff Copeland - QMS
Andy Davidson - Tektronix
Roger deBry - IBM
Mabry Dozier - QMS
Lee Farrell - Canon
Steve Gebert - IBM
Robert Herriot - Sun Microsystems Inc.
Shige Kanemitsu - Kyocera
David Kellerman - Northlake Software
Rick Landau - Digital
Pete Loya - HP
Ray Lutz - Cognisys
Jay Martin - Underscore
Mike MacKay, Novell, Inc.
Stan McConnell - Xerox
Carl-Uno Manros, Xerox, Corp.
Pat Nogay - IBM
Bob Pentecost - HP
Rob Rhoads - Intel
David Roach - Unisys
Stuart Rowley - Kyocera
Hiroyuki Sato - Canon
Bob Setterbo - Adobe
Gail Songer, EFI
Mike Timperman - Lexmark
Randy Turner - Sharp
William Wagner - Digital Products
Jim Walker - Dazel
Chris Wellens - Interworking Labs
Rob Whittle - Novell
Don Wright - Lexmark
Lloyd Young - Lexmark
Atsushi Yuki - Kyocera
Peter Zehler, Xerox, Corp.
10 Change History Phone: 805-578-4421
Fax: 805-578-4001
EMail: rbergma@dpc.com
This section summarizes the changes in each version after version 1.0 Tom Hastings
in reverse chronological order. Xerox Corporation, ESAE-231
737 Hawaii St.
El Segundo, CA 90245
10.1Changes to produce version 1.0, dated February 19, 1999 Phone: 310-333-6413
Fax: 310-333-5514
EMail: hastings@cp10.es.xerox.com
The following changes were made to version 1.2, dated October 2, 1998 Scott A. Isaacson
to make version 1.0 [sic], dated January 28, 1999: Novell, Inc.
122 E 1700 S
Provo, UT 84606
1.Changed the version number back to 1.0 for this INTERNET-DRAFT in Phone: 801-861-7366
anticipation of its being published as an Information RFC. Fax: 801-861-4025
EMail: scott_isaacson@novell.com
10.2Changes to produce version 1.2, dated October 2, 1998 Harry Lewis
IBM Corporation
6300 Diagonal Hwy
Boulder, CO 80301
The following changes were made to version 1.1, dated October 1, 1998 Phone: (303) 924-5337
to make version 1.2, dated October 2, 1998: EMail: harryl@us.ibm.com
1.Removed all REFERENCE clauses since they referred to sections in the Send questions and comments to the Printer Working Group (PWG)
specification that were not in the MIB as requested by the IESG. using the Job Monitoring Project (JMP) Mailing List: jmp@pwg.org
2.Moved the definitions of the attributes from the TC to a new section To learn how to subscribe, send email to: jmp-request@pwg.org
3.3.8 as requested by the IESG. Implementers of this specification are encouraged to join the jmp
mailing list in order to participate in discussions on any
clarifications needed and registration proposals for additional
attributes and values being reviewed in order to achieve consensus.
3.Removed the attributes from the Table of Contents For further information, access the PWG web page under "JMP":
4.Added the data types as ASN.1 comments after each attribute enum. http://www.pwg.org/
5.Changed a number of occurrences of "SHALL" to "is" when they were Other Participants:
just definitions, rather than conformance requirements.
10.3Changes to produce version 1.1, dated October 1, 1998 Chuck Adams - Tektronix
Jeff Barnett - IBM
Keith Carter, IBM Corporation
Jeff Copeland - QMS
Andy Davidson - Tektronix
Roger deBry - IBM
Mabry Dozier - QMS
Lee Farrell - Canon
Steve Gebert - IBM
Robert Herriot - Sun Microsystems Inc.
Shige Kanemitsu - Kyocera
David Kellerman - Northlake Software
Rick Landau - Digital
Pete Loya - HP
Ray Lutz - Cognisys
Jay Martin - Underscore
Mike MacKay, Novell, Inc.
Stan McConnell - Xerox
Carl-Uno Manros, Xerox, Corp.
Pat Nogay - IBM
Bob Pentecost - HP
Rob Rhoads - Intel
David Roach - Unisys
Stuart Rowley - Kyocera
Hiroyuki Sato - Canon
Bob Setterbo - Adobe
Gail Songer, EFI
Mike Timperman - Lexmark
Randy Turner - Sharp
William Wagner - Digital Products
Jim Walker - Dazel
Chris Wellens - Interworking Labs
Rob Whittle - Novell
Don Wright - Lexmark
Lloyd Young - Lexmark
Atsushi Yuki - Kyocera
Peter Zehler, Xerox, Corp.
The following changes were made to version 1.0, dated February 3, 1998 10 INDEX
to make version 1.1, dated October 1, 1998:
1.Clarified sections 3.3.3 and 3.3.7 so that the DEFVAL of 0 for index This index includes the textual conventions, the objects, and the
attributes is different from the DEFVAL for attributes. Textual conventions all start with the prefix: "JM" and
jmAttributeValueAsInteger which is -2. end with the suffix: "TC". Objects all starts with the prefix:
"jm" followed by the group name. Attributes are identified with
enums, and so start with any lower case letter and have no special
prefix.
2.Clarified the relationships of the values of the colorantConsumed, 40
JmJobCollationTypeTC with the IPP "multiple-document-handling" colorantRequested, 40
attribute. deviceNameRequested, 30
documentCopiesCompleted, 35
documentCopiesRequested, 35
documentFormat, 31
documentFormatIndex, 31
documentName, 31
fileName, 31
finishing, 33
fullColorImpressionsCompleted, 37
highlightColorImpressionsCompleted, 37
impressionsCompletedCurrentCopy, 37
impressionsInterpreted, 37
impressionsSentToDevice, 37
impressionsSpooled, 36
jmAttributeInstanceIndex, 99
jmAttributeTypeIndex, 98
JmAttributeTypeTC, 78
jmAttributeValueAsInteger, 99
jmAttributeValueAsOctets, 100
JmBooleanTC, 72
JmFinishingTC, 70
jmGeneralAttributePersistence, 87
jmGeneralJobPersistence, 87
jmGeneralJobSetIndex, 85
jmGeneralJobSetName, 88
jmGeneralNewestActiveJobIndex, 86
jmGeneralNumberOfActiveJobs, 86
jmGeneralOldestActiveJobIndex, 86
JmJobCollationTypeTC, 74
jmJobIDJobIndex, 91
jmJobIDJobSetIndex, 90
jmJobImpressionsCompleted, 96
jmJobImpressionsPerCopyRequested, 95
jmJobIndex, 92
jmJobKOctetsPerCopyRequested, 94
jmJobKOctetsProcessed, 94
jmJobOwner, 96
JmJobServiceTypesTC, 81
JmJobSourcePlatformTypeTC, 69
jmJobState, 92
jmJobStateReasons1, 93
JmJobStateReasons1TC, 83
JmJobStateReasons2TC, 83
JmJobStateReasons3TC, 83
JmJobStateReasons4TC, 84
JmJobStateTC, 75
JmJobStringTC, 68
jmJobSubmissionID, 89
JmJobSubmissionIDTypeTC, 74
JmMediumTypeTC, 72
JmNaturalLanguageTagTC, 68
jmNumberOfInterveningJobs, 93
JmPrinterResolutionTC, 71
JmPrintQualityTC, 71
JmTimeStampTC, 69
JmTonerEconomyTC, 72
JmUTF8StringTC, 68
jobAccountName, 27
jobCodedCharSet, 26
jobCollationType, 36
jobComment, 31
jobCompletionTime, 43
jobCopiesCompleted, 35
jobCopiesRequested, 35
jobHold, 33
jobHoldUntil, 33
jobKOctetsTransferred, 35
jobName, 28
jobNaturalLanguageTag, 27
jobOriginatingHost, 30
jobPriority, 32
jobProcessAfterDateAndTime, 32
jobProcessingCPUTime, 43
jobServiceTypes, 29
jobSourceChannelIndex, 29
jobSourcePlatformType, 29
jobStartedBeingHeldTime, 42
jobStartedProcessingTime, 43
jobStateReasons2, 25
jobStateReasons3, 25
jobStateReasons4, 25
jobSubmissionTime, 42
jobSubmissionToServerTime, 42
jobURI, 27
mediumConsumed, 40
mediumRequested, 39
mediumSizeConsumed, 41
mediumTypeConsumed, 41
numberOfDocuments, 30
other, 25
outputBin, 33
pagesCompleted, 38
pagesCompletedCurrentCopy, 38
pagesRequested, 38
physicalDevice, 30
printerResolutionRequested, 34
printerResolutionUsed, 34
printQualityRequested, 34
printQualityUsed, 34
processingMessage, 25
processingMessageNaturalLangTag, 26
queueNameRequested, 30
serverAssignedJobName, 28
sheetCompletedCopyNumber, 36
sheetCompletedDocumentNumber, 36
sheetsCompleted, 39
sheetsCompletedCurrentCopy, 39
sheetsRequested, 39
sides, 33
submittingApplicationName, 29
submittingServerName, 29
tonerDensityRequested, 34
tonerDensityUsed, 34
tonerEcomonyRequested, 34
tonerEcomonyUsed, 34
3.Clarified that the values of the mediumRequested(170) and 11 Full Copyright Statement
mediumConsumed(171) attributes may be any of the IPP 'media' values
which are media names, media size names, and input tray names.
4.Added the two attributes approved by the PWG for registration in Copyright (C) The Internet Society (1999). All Rights Reserved.
April 1998: mediumTypeConsumed(174) and mediumSizeConsumed(175).
5.Changed "insure" to "ensure'. This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be