draft-ietf-printmib-job-monitor-04.txt   draft-ietf-printmib-job-monitor-05.txt 
Job Monitoring MIB, V0.85 Aug 8, 1997
INTERNET-DRAFT Ron Bergman INTERNET-DRAFT Ron Bergman
Dataproducts Corp. Dataproducts Corp.
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
Scott Isaacson Scott Isaacson
Novell, Inc. Novell, Inc.
Harry Lewis Harry Lewis
IBM Corp. IBM Corp.
August 8, 1997
Job Monitoring MIB - V0.84 Job Monitoring MIB - V0.85
<draft-ietf-printmib-job-monitor-04.txt> <draft-ietf-printmib-job-monitor-05.txt>
Expires Jan 21, 1997 Expires Feb 8, 1997
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 2, line 4 skipping to change at page 1, line 49
Abstract Abstract
This Internet-Draft specifies a small set of read-only SNMP MIB This Internet-Draft specifies a small set of read-only SNMP MIB
objects for (1) monitoring the status and progress of print jobs objects for (1) monitoring the status and progress of print jobs
(2) obtaining resource requirements before a job is processed, (3) (2) obtaining resource requirements before a job is processed, (3)
monitoring resource consumption while a job is being processed and monitoring resource consumption while a job is being processed and
(4) collecting resource accounting data after the completion of a (4) collecting resource accounting data after the completion of a
job. This MIB is intended to be implemented (1) in a printer or 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 (2) in a server that supports one or more printers. Use of the
Job Monitoring MIB, V0.84 July 21, 1997
object set is not limited to printing. However, support for object set is not limited to printing. However, support for
services other than printing is outside the scope of this Job services other than printing is outside the scope of this Job
Job Monitoring MIB, V0.85 Aug 8, 1997
Monitoring MIB. Future extensions to this MIB may include, but are Monitoring MIB. Future extensions to this MIB may include, but are
not limited to, fax machines and scanners. not limited to, fax machines and scanners.
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
TABLE OF CONTENTS TABLE OF CONTENTS
1. INTRODUCTION 11 1. INTRODUCTION 8
1.1 Types of Information in the MIB 11
1.2 Types of Job Monitoring Applications 13
2. TERMINOLOGY AND JOB MODEL 14
2.1 System Configurations for the Job Monitoring MIB 16 1.1 Types of Information in the MIB 8
2.1.1 Configuration 1 - client-printer 17 1.2 Types of Job Monitoring Applications 10
2.1.2 Configuration 2 - client-server-printer - agent in the server17 2. TERMINOLOGY AND JOB MODEL 11
2.1 System Configurations for the Job Monitoring MIB 13
2.1.1 Configuration 1 - client-printer 14
2.1.2 Configuration 2 - client-server-printer - agent in the server14
2.1.3 Configuration 3 - client-server-printer - client monitors 2.1.3 Configuration 3 - client-server-printer - client monitors
printer agent and server 19 printer agent and server 16
3. MANAGED OBJECT USAGE 21
3.1 Conformance Considerations 21
3.1.1 Conformance Terminology 21
3.1.2 Agent Conformance Requirements 21
3.1.2.1 MIB II System Group objects 22
3.1.2.2 MIB II Interface Group objects 22
3.1.2.3 Printer MIB objects 22
3.1.3 Job Monitoring Application Conformance Requirements 22
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 23 3. MANAGED OBJECT USAGE 17
3.3 The Attribute Mechanism 24 3.1 Conformance Considerations 17
3.1.1 Conformance Terminology 18
3.1.2 Agent Conformance Requirements 18
3.1.2.1 MIB II System Group objects 18
3.1.2.2 MIB II Interface Group objects 19
3.1.2.3 Printer MIB objects 19
3.1.3 Job Monitoring Application Conformance Requirements 19
3.3.1 Conformance of Attribute Implementation 25 3.2 The Job Tables and the Oldest Active and Newest Active Indexes 19
3.3 The Attribute Mechanism 21
3.3.1 Conformance of Attribute Implementation 22
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and
Attributes 25 Attributes 23
3.3.3 Data Sub-types and Attribute Naming Conventions 23
Job Monitoring MIB, V0.84 July 21, 1997 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 24
3.3.5 Requested Attributes 24
3.3.3 Data Sub-types and Attribute Naming Conventions 26 3.3.6 Consumption Attributes 26
3.3.7 Index Value Attributes 26
3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 27
3.3.5 Requested Attributes 27
3.3.6 Consumption Attributes 28
3.3.7 Index Value Attributes 28
3.4 Job Identification 28
3.5 Internationalization Considerations 29
3.6 IANA Considerations 29
3.6.1 IANA Registration of enums 29
3.6.1.1 Type 1 enumerations 30
3.6.1.2 Type 2 enumerations 30
3.6.1.3 Type 3 enumeration 31
3.6.2 IANA Registration of type 2 bit values 31
3.6.3 IANA Registration of Job Submission Id Formats 31
3.6.4 IANA Registration of MIME types/sub-types for document-formats31
3.7 Security Considerations 32
3.7.1 Read-Write objects 32
3.7.2 Read-Only Objects In Other User's Jobs 32
3.8 Notifications 32
4. MIB SPECIFICATION 32
Textual conventions for this MIB module 34
JmTimeStampTC - simple time in seconds 34
JmJobSourcePlatformTypeTC - operating system platform definitions 34
JmFinishingTC - device finishing definitions 35
Job Monitoring MIB, V0.84 July 21, 1997
JmPrintQualityTC - print quality 37
JmPrinterResolutionTC - printer resolution 37
JmTonerEconomyTC - toner economy setting 38
JmBooleanTC - Boolean value 38
JmMediumTypeTC - medium type definitions 39
JmJobSubmissionIDTypeTC - job submission ID type definitions 40
JmJobStateTC - job state definitions 42
JmAttributeTypeTC - attribute type definitions 45
other (Int32(-2..) and/or Octets63) 46
Job State attributes 46
jobStateReasons2 (JmJobStateReasons2TC) 46 3.4 Job Identification .............................................26
jobStateReasons3 (JmJobStateReasons3TC) 46 3.5 Internationalization Considerations 26
3.5.1 'JmUTF8StringTC' for text generated by the server or device 25
3.5.2 'JmJobStringTC' for text generated by the job submitter 25
Job Monitoring MIB, V0.85 Aug 8, 1997
jobStateReasons4 (JmJobStateReasons4TC) 47 3.5.3 'DateAndTime' for representing the date and time 25
processingMessage (Octets63) 47 3.6 IANA Considerations 27
3.6.1 IANA Registration of enums 28
3.6.1.1 Type 1 enumerations 28
3.6.1.2 Type 2 enumerations 28
3.6.1.3 Type 3 enumeration 29
3.6.2 IANA Registration of type 2 bit values 29
3.6.3 IANA Registration of Job Submission Id Formats 29
3.6.4 IANA Registration of MIME types/sub-types for document-formats29
Job Identification attributes 47 3.7 Security Considerations 30
3.7.1 Read-Write objects 30
3.7.2 Read-Only Objects In Other User's Jobs 30
jobAccountName (Octets63) 47 3.8 Values for Objects 23
serverAssignedJobName (Octets63) 47 3.9 Notifications 30
jobName (Octets63) 48 4. MIB SPECIFICATION 30
Textual conventions for this MIB module 32
JmUTF8StringTC 33
JmJobStringTC 33
JmTimeStampTC 33
JmJobSourcePlatformTypeTC 33
JmFinishingTC 34
JmPrintQualityTC 36
JmPrinterResolutionTC 36
JmTonerEconomyTC 37
JmBooleanTC 37
JmMediumTypeTC 38
JmJobSubmissionIDTypeTC 39
JmJobStateTC 41
JmAttributeTypeTC 44
other (Int32(-2..) and/or Octets63) 45
Job State attributes 45
jobStateReasons2 (JmJobStateReasons2TC) 45
jobStateReasons3 (JmJobStateReasons3TC) 45
jobStateReasons4 (JmJobStateReasons4TC) 45
processingMessage (UTF8String63) 45
jobCodedCharSet (CodedCharSet) 45
Job Identification attributes 46
jobAccountName (JobString63) 46
serverAssignedJobName (JobString63) 47
jobName (JobString63) 47
jobServiceTypes (JmJobServiceTypesTC) 48 jobServiceTypes (JmJobServiceTypesTC) 48
Job Monitoring MIB, V0.85 Aug 8, 1997
jobSourceChannelIndex (Int32(0..)) 49 jobSourceChannelIndex (Int32(0..)) 48
jobSourcePlatformType (JmJobSourcePlatformTypeTC) 48
jobSourcePlatformType (JmJobSourcePlatformTypeTC) 49 submittingServerName (JobString63) 48
submittingApplicationName (JobString63) 49
submittingServerName (Octets63) 49 jobOriginatingHost (JobString63) 49
deviceNameRequested (JobString63) 49
submittingApplicationName (Octets63) 49 queueNameRequested (JobString63) 49
physicalDevice (hrDeviceIndex and/or UTF8String63) 49
jobOriginatingHost (Octets63) 50 numberOfDocuments (Int32(-2..)) 49
fileName (JobString63) 50
Job Monitoring MIB, V0.84 July 21, 1997 documentName (JobString63) 50
jobComment (JobString63) 50
deviceNameRequested (Octets63) 50 documentFormatIndex (Int32(0..)) 50
documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 50
queueNameRequested (Octets63) 50 Job Parameter attributes 51
jobPriority (Int32(1..100)) 51
physicalDevice (hrDeviceIndex and/or Octets63) 50 jobProcessAfterDateAndTime (DateAndTime) 51
jobHold (JmBooleanTC) 51
numberOfDocuments (Int32(-2..)) 50 jobHoldUntil (JobString63) 52
outputBin (Int32(0..) and/or JobString63) 52
fileName (Octets63) 51 sides (Int32(-2..2)) 52
finishing (JmFinishingTC) 52
documentName (Octets63) 51 Image Quality attributes (requested and used) 52
printQualityRequested (JmPrintQualityTC) 52
jobComment (Octets63) 51 printQualityUsed (JmPrintQualityTC) 53
printerResolutionRequested (JmPrinterResolutionTC) 53
documentFormatIndex (Int32(0..)) 51 printerResolutionUsed (JmPrinterResolutionTC) 53
tonerEcomonyRequested (JmTonerEconomyTC) 53
documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 52 tonerEcomonyUsed (JmTonerEconomyTC) 53
tonerDensityRequested (Int32(-2..100)) 53
Job Parameter attributes 52 tonerDensityUsed (Int32(-2..100)) 53
Job Progress attributes (requested and consumed) 53
jobPriority (Int32(1..100)) 52 jobCopiesRequested (Int32(-2..)) 54
jobCopiesCompleted (Int32(-2..)) 54
jobProcessAfterDateAndTime (DateAndTime) 52 documentCopiesRequested (Int32(-2..)) 54
documentCopiesCompleted (Int32(-2..)) 54
jobHold (JmBooleanTC) 53 jobKOctetsTransferred (Int32(-2..)) 54
Impression attributes (requested and consumed) 55
jobHoldUntil (Octets63) 53 impressionsSpooled (Int32(-2..)) 55
impressionsSentToDevice (Int32(-2..)) 55
outputBin (Int32(0..) and/or Octets63) 53 impressionsInterpreted (Int32(-2..)) 55
impressionsCompletedCurrentCopy (Int32(-2..)) 55
sides (Int32(-2..2)) 53 fullColorImpressionsCompleted (Int32(-2..)) 55
highlightColorImpressionsCompleted (Int32(-2..)) 55
finishing (JmFinishingTC) 53 Page attributes (requested and consumed) 56
pagesRequested (Int32(-2..)) 56
Image Quality attributes (requested and used) 54 pagesCompleted (Int32(-2..)) 56
pagesCompletedCurrentCopy (Int32(-2..)) 56
printQualityRequested (JmPrintQualityTC) 54 Job Monitoring MIB, V0.85 Aug 8, 1997
printQualityUsed (JmPrintQualityTC) 54
printerResolutionRequested (JmPrinterResolutionTC) 54
printerResolutionUsed (JmPrinterResolutionTC) 54
tonerEcomonyRequested (JmTonerEconomyTC) 54
tonerEcomonyUsed (JmTonerEconomyTC) 54
Job Monitoring MIB, V0.84 July 21, 1997
tonerDensityRequested (Int32(-2..100)) 55
tonerDensityUsed (Int32(-2..100)) 55
Job Progress attributes (requested and consumed) 55
jobCopiesRequested (Int32(-2..)) 55
jobCopiesCompleted (Int32(-2..)) 55
documentCopiesRequested (Int32(-2..)) 55
documentCopiesCompleted (Int32(-2..)) 56
jobKOctetsTransferred (Int32(-2..)) 56
Impression attributes (requested and consumed) 56
impressionsSpooled (Int32(-2..)) 57
impressionsSentToDevice (Int32(-2..)) 57
impressionsInterpreted (Int32(-2..)) 57
impressionsCompletedCurrentCopy (Int32(-2..)) 57
fullColorImpressionsCompleted (Int32(-2..)) 57
highlightColorImpressionsCompleted (Int32(-2..)) 57
Page attributes (requested and consumed) 58
pagesRequested (Int32(-2..)) 58
pagesCompleted (Int32(-2..)) 58
pagesCompletedCurrentCopy (Int32(-2..)) 58
Sheet attributes (requested and consumed) 58
sheetsRequested (Int32(-2..)) 58
sheetsCompleted (Int32(-2..)) 59
sheetsCompletedCurrentCopy (Int32(-2..)) 59
Resource attributes (requested and consumed) 59
Job Monitoring MIB, V0.84 July 21, 1997
mediumRequested (JmMediumTypeTC and/or Octets63) 59
mediumConsumed (Int32(-2..) and/or Octets63) 59
colorantRequested (Int32(-2..) and/or Octets63) 60
colorantConsumed (Int32(-2..) and/or Octets63) 60
Time attributes (set by server or device) 60
jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 61
jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 61
jobStartedBeingHeldTime (JmTimeStampTC) 61
jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 61
jobCompletedTime (JmTimeStampTC and/or DateAndTime) 61
jobProcessingCPUTime (Int32(-2..)) 62
JmJobServiceTypesTC - bit encoded job service type definitions 64
JmJobStateReasons1TC - additional information about job states 65
JmJobStateReasons2TC - More additional information about job states69
JmJobStateReasons3TC - More additional information about job states73
JmJobStateReasons4TC - More additional information about job states74
The General Group (MANDATORY) 75
jmGeneralJobSetIndex (Int32(1..32767)) 75
jmGeneralNumberOfActiveJobs (Int32(0..)) 76
jmGeneralOldestActiveJobIndex (Int32(0..)) 76
jmGeneralNewestActiveJobIndex (Int32(0..)) 77
jmGeneralJobPersistence (Int32(15..)) 77
jmGeneralAttributePersistence (Int32(15..)) 78
jmGeneralJobSetName (Octets63) 78
Job Monitoring MIB, V0.84 July 21, 1997
The Job ID Group (MANDATORY) 78
jmJobSubmissionID (OCTET STRING(SIZE(48))) 79
jmJobIDJobSetIndex (Int32(1..32767)) 80
jmJobIDJobIndex (Int32(1..)) 81
The Job Group (MANDATORY) 81
jmJobIndex (Int32(1..)) 82
jmJobState (JmJobStateTC) 82
jmJobStateReasons1 (JmJobStateReasons1TC) 83
jmNumberOfInterveningJobs (Int32(-2..)) 83
jmJobKOctetsRequested (Int32(-2..)) 84
jmJobKOctetsProcessed (Int32(-2..)) 84
jmJobImpressionsRequested (Int32(-2..)) 85
jmJobImpressionsCompleted (Int32(-2..)) 85
jmJobOwner (Octets63) 85 Sheet attributes (requested and consumed) 57
sheetsRequested (Int32(-2..)) 57
sheetsCompleted (Int32(-2..)) 57
sheetsCompletedCurrentCopy (Int32(-2..)) 57
Resource attributes (requested and consumed) 57
mediumRequested (JmMediumTypeTC and/or JobString63) 57
mediumConsumed (JobString63) 57
colorantRequested (Int32(-2..) and/or JobString63) 58
colorantConsumed (Int32(-2..) and/or JobString63) 58
Time attributes (set by server or device) 58
jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 59
jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 59
jobStartedBeingHeldTime (JmTimeStampTC and/or DateAndTime) 59
jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 59
jobCompletedTime (JmTimeStampTC and/or DateAndTime) 59
jobProcessingCPUTime (Int32(-2..)) 59
JmJobServiceTypesTC 61
JmJobStateReasons1TC 63
JmJobStateReasons2TC 67
JmJobStateReasons3TC 71
JmJobStateReasons4TC 72
The Attribute Group (MANDATORY) 86 The General Group (MANDATORY) 73
jmGeneralJobSetIndex (Int32(1..32767)) 73
jmGeneralNumberOfActiveJobs (Int32(0..)) 74
jmGeneralOldestActiveJobIndex (Int32(0..)) 74
jmGeneralNewestActiveJobIndex (Int32(0..)) 75
jmGeneralJobPersistence (Int32(15..)) 75
jmGeneralAttributePersistence (Int32(15..)) 75
jmGeneralJobSetName (UTF8String63) 76
jmAttributeTypeIndex (JmAttributeTypeTC) 87 The Job ID Group (MANDATORY) 76
jmJobSubmissionID (OCTET STRING(SIZE(48))) 77
jmJobIDJobSetIndex (Int32(1..32767)) 78
jmJobIDJobIndex (Int32(1..)) 78
jmAttributeInstanceIndex (Int32(1..32767)) 88 The Job Group (MANDATORY) 79
jmJobIndex (Int32(1..)) 80
jmJobState (JmJobStateTC) 80
jmJobStateReasons1 (JmJobStateReasons1TC) 81
jmNumberOfInterveningJobs (Int32(-2..)) 81
jmJobKOctetsRequested (Int32(-2..)) 81
jmJobKOctetsProcessed (Int32(-2..)) 82
jmJobImpressionsRequested (Int32(-2..)) 83
jmJobImpressionsCompleted (Int32(-2..)) 83
jmJobOwner (JobString63) 83
jmAttributeValueAsInteger (Int32(-2..)) 88 The Attribute Group (MANDATORY) 84
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeValueAsOctets (Octets63) 89 jmAttributeTypeIndex (JmAttributeTypeTC) 86
jmAttributeInstanceIndex (Int32(1..32767)) 86
jmAttributeValueAsInteger (Int32(-2..)) 87
jmAttributeValueAsOctets (Octets63) 88
5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 93 5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 91
6. APPENDIX B - SUPPORT OF THE JOB SUBMISSION ID IN JOB SUBMISSION 6. APPENDIX B - SUPPORT OF THE JOB SUBMISSION ID IN JOB SUBMISSION
PROTOCOLS 94 PROTOCOLS 92
6.1 Hewlett-Packard's Printer Job Language (PJL) 94
6.2 ISO DPA 94
Job Monitoring MIB, V0.84 July 21, 1997 6.1 Hewlett-Packard's Printer Job Language (PJL) 92
7. REFERENCES 94 6.2 ISO DPA 92
8. AUTHOR'S ADDRESSES 95 7. REFERENCES 93
9. INDEX 98 8. AUTHOR'S ADDRESSES 94
Job Monitoring MIB, V0.84 July 21, 1997 9. INDEX 97
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB Job Monitoring MIB
1. Introduction 1. Introduction
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 within
a printer or the first server closest to the printer, where the printer a printer or the first server closest to the printer, where the printer
is either directly connected to the server only or the printer does not is either directly connected to the server only or the printer does not
contain the job monitoring MIB agent. It is recommended that contain the job monitoring MIB agent. It is recommended that
implementations place the SNMP agent as close as possible to the implementations place the SNMP agent as close as possible to the
skipping to change at page 11, line 33 skipping to change at page 8, line 32
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 ID
Group, a Job Group, and an Attribute Group. Each group is a table. All Group, a Job Group, and an Attribute Group. Each group is a table. All
accessible objects are read-only. The General Group contains general accessible objects are read-only. The General Group contains general
information that applies to all jobs in a job set. The Job Submission information that applies to all jobs in a job set. The Job Submission
ID table maps the job submission ID that the client uses to identify a ID table maps the job submission ID that the client uses to identify a
job to the jmJobIndex that the Job Monitoring Agent uses to identify job to the jmJobIndex that the Job Monitoring Agent uses to identify
jobs in the Job and Attribute tables. The Job table contains the jobs in the Job and Attribute tables. The Job table contains the
MANDATORY integer job state and status objects. The Attribute table MANDATORY integer job state and status objects. The Attribute table
consists of multiple entries per job that specify (1) job and document consists of multiple entries per job that specify (1) job and document
identification and parameters, (2) requested resources, and (3) identification and parameters, (2) requested resources, and (3)
consumed resources during and after job processing/printing. Sixty five consumed resources during and after job processing/printing. A larger
job attributes are defined as textual conventions that an agent SHALL number of job attributes are defined as textual conventions that an
return if the server or device implements the functionality so agent SHALL return if the server or device implements the functionality
represented and the agent has access to the information. so represented and the 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 - Roles
of Users). 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 user
will be able to determine the number and size of jobs waiting for will be able to determine the number and size of jobs waiting for
each printer. No attempt is made to actually predict the length each printer. No attempt is made to actually predict the length
of time that jobs will take. of time that jobs will take.
Provide the ability to identify the current status of the user's Provide the ability to identify the current status of the user's
job (user queries). job (user queries).
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
Provide a timely indication that the job has completed and where Provide a timely indication that the job has completed and where
it can be found. it can be found.
Provide error and diagnostic information for jobs that did not Provide error and diagnostic information for jobs that did not
successfully complete. successfully complete.
Operator: Operator:
Provide a presentation of the state of all the jobs in the print Provide a presentation of the state of all the jobs in the print
skipping to change at page 12, line 52 skipping to change at page 9, line 52
Provide information to allow the creation of a record of resources Provide information to allow the creation of a record of resources
consumed and printer usage data for charging users or groups for consumed and printer usage data for charging users or groups for
resources consumed. 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 time,
but still be usable for low end printers that only contain a single job but still be usable for low end printers that only contain a single job
at a time. In particular, the MIB supports the needs of Windows and at a time. In particular, the MIB supports the needs of Windows and
other PC environments for managing low-end networked devices without other PC environments for managing low-end direct-connect (serial or
unnecessary overhead or complexity, while also providing for higher end parallel) and networked devices without unnecessary overhead or
systems and devices. complexity, while also providing for higher end systems and devices.
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
1.2 Types of Job Monitoring Applications 1.2 Types of Job Monitoring Applications
The Job Monitoring MIB is designed for the following types of monitoring The Job Monitoring MIB is designed for the following types of monitoring
applications: applications:
1.Monitor a single job starting when the job is submitted and ending 1.Monitor a single job starting when the job is submitted and ending
a defined period after the job completes. The Job Submission ID a defined period after the job completes. The Job Submission ID
table provides the map to find the specific job to be monitored. table provides the map to find the specific job to be monitored.
2.Monitor all 'active' jobs in a queue, which this specification 2.Monitor all 'active' jobs in a queue, which this specification
generalizes to a "job set". End users may use such a program when generalizes to a "job set". End users may use such a program when
selecting a least busy printer, so the MIB is designed for such a selecting a least busy printer, so the MIB is designed for such a
program to start up quickly and find the information needed quickly program to start up quickly and find the information needed
without having to read all (completed) jobs in order to find the quickly without having to read all (completed) jobs in order to
active jobs. System operators may also use such a program, in find the active jobs. System operators may also use such a
which case it would be running for a long period of time and may program, in which case it would be running for a long period of
also be interested in the jobs that have completed. Finally such a time and may also be interested in the jobs that have completed.
program may be used to provide an enhanced console and logging Finally such a program may be used to provide an enhanced console
capability. and logging capability.
3.Collect resource usage for accounting or system utilization 3.Collect resource usage for accounting or system utilization
purposes that copy the completed job statistics to an accounting purposes that copy the completed job statistics to an accounting
system. It is recognized that depending on accounting programs to system. It is recognized that depending on accounting programs to
copy MIB data during the job-retention period is somewhat copy MIB data during the job-retention period is somewhat
unreliable, since the accounting program may not be running (or may unreliable, since the accounting program may not be running (or
have crashed). Such a program is also expected to keep a shadow may have crashed). Such a program is also expected to keep a
copy of the entire Job Attribute table including completed, shadow copy of the entire Job Attribute table including completed,
canceled, and aborted jobs which the program updates on each canceled, and aborted jobs which the program updates on each
polling cycle. Such a program polls at the rate of the persistence polling cycle. Such a program polls at the rate of the
of the Attribute table. The design is not optimized to help such persistence of the Attribute table. The design is not optimized
an application determine which jobs are completed, canceled, or to help such an application determine which jobs are completed,
aborted. Instead, the application SHALL query each job that the canceled, or aborted. Instead, the application SHALL query each
application's shadow copy shows was not complete, canceled, or job that the application's shadow copy shows was not complete,
aborted at the previous poll cycle to see if it is now complete or canceled, or aborted at the previous poll cycle to see if it is
canceled, plus any new jobs that have been submitted. 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 The MIB provides a set of objects that represent a compatible subset of
job and document attributes of the ISO DPA standard[iso-dpa] and the job and document attributes of the ISO DPA standard[iso-dpa] and the
Internet Printing Protocol (IPP)[ipp-model], so that coherence is Internet Printing Protocol (IPP)[ipp-model], so that coherence is
maintained between these two protocols and the information presented to maintained between these two protocols and the information presented to
end users and system operators by monitoring applications. However, the end users and system operators by monitoring applications. However, the
job monitoring MIB is intended to be used with printers that implement job monitoring MIB is intended to be used with printers that implement
other job submitting and management protocols, such as IEEE 1284.1 other job submitting and management protocols, such as IEEE 1284.1
(TIPSI)[tipsi], as well as with ones that do implement ISO DPA. Thus (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 the job monitoring MIB does not require implementation of either the ISO
DPA or IPP protocols. DPA or IPP protocols.
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
The MIB is designed so that an additional MIB(s) can be specified in the The MIB is designed so that an additional MIB(s) can be specified in the
future for monitoring multi-function (scan, FAX, copy) jobs as an future for monitoring multi-function (scan, FAX, copy) jobs as an
augmentation to this MIB. augmentation to this MIB.
2. Terminology and Job Model 2. Terminology and Job Model
This section defines the terms that are used in this specification and This section defines the terms that are used in this specification and
the general model for jobs. the general model for jobs.
skipping to change at page 14, line 46 skipping to change at page 11, line 46
devices, each MIB job set represents a job queue for (1) a specific devices, each MIB job set represents a job queue for (1) a specific
device or (2) set of devices, if the server uses a single queue to load device or (2) set of devices, if the server uses a single queue to load
balance between several devices. Each job set is disjoint; no job SHALL balance between several devices. Each job set is disjoint; no job SHALL
be represented in more than one MIB job set. be represented in more than one MIB job set.
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.
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. configuration, using any job submission protocol over a serial or
parallel port to a directly-connected device or over the network to a
networked-connected device.
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. A server MAY be a submits the jobs to printers and other devices that may be directly
printer supervisor control program, or a print spooler. connected to the server via a serial or parallel port or may be on the
network. A server MAY be a printer supervisor control program, or a
print spooler.
Job Monitoring MIB, V0.85 Aug 8, 1997
Device: a hardware entity that (1) interfaces to humans in human Device: a hardware entity that (1) interfaces to humans in human
perceptible means, such as produces marks on paper, scans marks on paper perceptible means, such as produces marks on paper, scans marks on paper
to produce an electronic representations, or writes CD-ROMs or (2) to produce an electronic representations, or writes CD-ROMs or (2)
Job Monitoring MIB, V0.84 July 21, 1997
interfaces electronically to another device, such as sends FAX data to interfaces electronically to another device, such as sends FAX data to
another FAX device. another FAX device.
Printer: a device that puts marks on media. Printer: a device that puts marks on media.
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.
Spooler: a server that accepts jobs, spools the data, and decides when Spooler: a server that accepts jobs, spools the data, and decides when
skipping to change at page 15, line 51 skipping to change at page 13, line 5
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 other
agents, forwarding them on to those other agents, gathering responses agents, forwarding them on to those other agents, gathering responses
from those other agents and returning them to the original requesting from those other agents and returning them to the original requesting
monitor. monitor.
User: a person that uses a client or a monitor. User: a person that uses a client or a monitor.
End User: a user that uses a client to submit a print job. End User: a user that uses a client to submit a print job.
Job Monitoring MIB, V0.85 Aug 8, 1997
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 and
carries out tasks to keep the system running. 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.
Job Monitoring MIB, V0.84 July 21, 1997
Job Instruction: an instruction specifying how, when, or where the job Job Instruction: an instruction specifying how, when, or where the job
is to be processed. Job instructions MAY be passed in the job is to be processed. Job instructions MAY be passed in the job
submission protocol or MAY be embedded in the document data or a submission protocol or MAY be embedded in the document data or a
combination depending on the job submission protocol and implementation. combination depending on the job submission protocol and implementation.
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 in
the document data or a combination, depending on the job submission the document data or a combination, depending on the job submission
protocol and implementation. protocol and implementation.
skipping to change at page 16, line 47 skipping to change at page 13, line 52
information to the user about the processing of the job. information to the user about the processing of the job.
Job Accounting: the activity of a management application of accessing Job Accounting: the activity of a management application of accessing
the MIB and recording what happens to the job during and after the the MIB and recording what happens to the job during and after the
processing of the job. processing of the job.
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 Goals section. devices are shown as printers. See section 1.1 entitled "Types of
Information in the MIB".
Job Monitoring MIB, V0.85 Aug 8, 1997
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 View
of the Network" is assumed for this MIB as well. Please refer to that of the Network" is assumed for this MIB as well. Please refer to that
diagram to aid in understanding the following system configurations. diagram to aid in understanding the following system configurations.
Job Monitoring MIB, V0.84 July 21, 1997
2.1.1 Configuration 1 - client-printer 2.1.1 Configuration 1 - client-printer
In the client-printer configuration, the client(s) submit jobs directly In the client-printer configuration 1, the client(s) submit jobs
to the printer, either by some direct connect, or by network connection. directly to the printer, either by some direct connect, or by network
connection.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs by
communicating directly with an agent that is part of the printer. The communicating directly with an agent that is part of the printer. The
agent in the Printer SHALL keep the job in the Job Monitoring MIB as agent in the printer SHALL keep the job in the Job Monitoring MIB as
long as the job is in the Printer, plus a defined time period after the long as the job is in the printer, plus a defined time period after the
job enters the completed state in which accounting programs can copy out job enters the completed state in which accounting programs can copy out
the accounting data from the Job Monitoring MIB. 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 |
+---#---+ +--#--+--+ +---#---+ +--#--+--+
# # | # # |
# ############ | # ############ |
# # | # # |
skipping to change at page 17, line 38 skipping to change at page 14, line 43
| +-------+ | | | +-------+ | |
| 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 jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
the printer. While configuration 2 is included, the design center for the printer. While configuration 2 is included, the design center for
this MIB is configurations 1 and 3, this MIB is configurations 1 and 3.
The job submitting client and/or monitoring application monitor job by The job submitting client and/or monitoring application monitor jobs by
communicating directly with: 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 this configuration 2, at least that the client or monitor are aware. In this
configuration, the agent SHALL return the current values of the objects configuration, the agent SHALL return the current values of the objects
in the Job Monitoring MIB both for jobs the server keeps and jobs that in the Job Monitoring MIB both for jobs the server keeps and jobs that
the server has submitted to the printer. The Job Monitoring MIB agent the server has submitted to the printer. The Job Monitoring MIB agent
SHALL obtain the required information from the printer by a method that SHALL obtain the required information from the printer by a method that
is beyond the scope of this document. The agent in the server SHALL is beyond the scope of this document. The agent in the server SHALL
keep the job in the Job Monitoring MIB in the server as long as the job keep the job in the Job Monitoring MIB in the server as long as the job
is in the Printer, plus a defined time period after the job enters the is in the printer, plus a defined time period after the job enters the
completed state in which accounting programs can copy out the accounting completed state in which accounting programs can copy out the accounting
data from the Job Monitoring MIB. data from the Job Monitoring MIB.
all end-user all end-user
+-------+ +----------+ +-------+ +----------+
|monitor| | client | ######## SNMP query |monitor| | client | ######## SNMP query
+---+---# +---#----+-+ **** non-SNMP cntrl +---+---# +---#----+-+ **** non-SNMP cntrl
# # | ---- job submission # # | ---- job submission
# # | # # |
# # | # # |
skipping to change at page 19, line 4 skipping to change at page 16, line 4
+========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
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
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 jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
the printer. That server does not contain a Job Monitoring MIB and the printer. That server does not contain a Job Monitoring MIB agent.
agent.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs by
communicating directly with: communicating directly with:
1.The server using some undefined protocol to monitor jobs in the 1.The server using some undefined protocol to monitor jobs in the
server (that does not contain the Job Monitoring MIB) AND 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
monitor jobs after the server passes the jobs to the printer. jobs after the server passes the jobs to the printer. In such
In such configurations, the server deletes its copy of the job configurations, the server deletes its copy of the job from the
from the server after submitting the job to the printer usually server after submitting the job to the printer usually almost
almost immediately (before the job does much processing, if immediately (before the job does much processing, if any).
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 of
the objects in the Job Monitoring MIB that the agent implements updated the objects in the Job Monitoring MIB that the agent implements updated
for a job that the server has submitted to the printer. The agent SHALL for a job that the server has submitted to the printer. The agent SHALL
obtain information about the jobs submitted to the printer from the obtain information about the jobs submitted to the printer from the
server (either in the job submission protocol, in the document data, or server (either in the job submission protocol, in the document data, or
by direct query of the server), in order to populate some of the objects by direct query of the server), in order to populate some of the objects
the Job Monitoring MIB in the printer. The agent in the printer SHALL the Job Monitoring MIB in the printer. The agent in the printer SHALL
keep the job in the Job Monitoring MIB as long as the job is in the keep the job in the Job Monitoring MIB as long as the job is in the
Printer, and longer in order to implement the completed state in which Printer, and longer in order to implement the completed state in which
Job Monitoring MIB, V0.84 July 21, 1997
monitoring programs can copy out the accounting data from the Job monitoring programs can copy out the accounting data from the Job
Monitoring MIB. Monitoring MIB.
Job Monitoring MIB, V0.85 Aug 8, 1997
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 |
skipping to change at page 20, line 38 skipping to change at page 17, line 35
| 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 monitors
printer agent and server printer agent and server
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 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.
Job Monitoring MIB, V0.84 July 21, 1997
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 applications In order to achieve interoperability between job monitoring applications
and job monitoring agents, this specification includes the conformance and job monitoring agents, this specification includes the conformance
requirements for both monitoring applications and agents. requirements for both monitoring applications and agents.
Job Monitoring MIB, V0.85 Aug 8, 1997
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 "NEED
NOT" to specify conformance requirements according to RFC 2119 [req- NOT" to specify conformance requirements according to RFC 2119 [req-
words] as follows: words] as follows:
. "SHALL": indicates an action that the subject of the sentence must . "SHALL": indicates an action that the subject of the sentence must
implement in order to claim conformance to this specification implement in order to claim conformance to this specification
. "MAY": indicates an action that the subject of the sentence does . "MAY": indicates an action that the subject of the sentence does
skipping to change at page 21, line 46 skipping to change at page 18, line 36
. "SHOULD": indicates an action that is recommended for the subject . "SHOULD": indicates an action that is recommended for the subject
of the sentence to implement, but is not required, in order to of the sentence to implement, but is not required, in order to
claim conformance to this specification. claim conformance to this specification.
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 supports 2. SHALL implement any attributes if (1) the server or device
the functionality represented by the attribute and (2) the supports the functionality represented by the attribute and (2)
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 forms, attribute that permits a choice of INTEGER and OCTET STRING forms,
since implementing both forms may help management applications by since implementing both forms may help management applications by
giving them a choice of representations, since the representation are giving them a choice of representations, since the representation
equivalent. See the JmAttributeTypeTC textual-convention. are equivalent. See the JmAttributeTypeTC textual-convention.
Job Monitoring MIB, V0.84 July 21, 1997
NOTE - This MIB, like the Printer MIB, is written following the 4. NOTE - This MIB, like the Printer MIB, is written following the
subset of SMIv2 that can be supported by SMIv1 and SNMPv1 subset of SMIv2 that can be supported by SMIv1 and SNMPv1
implementations. implementations.
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 System
Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is
implemented or not. implemented or not.
Job Monitoring MIB, V0.85 Aug 8, 1997
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-mib]
is implemented or not. 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[print-mib] and all the objects in other MIBs that conformance to the MIB[print-mib] and all the objects in other MIBs that conformance to the
Printer MIB requires, such as the Host Resources MIB[hr-mib]. If the 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 agent is providing access to a server that controls one or more direct-
networked printers, the agent NEED NOT implement the Printer MIB and connect or networked printers, the agent NEED NOT implement the Printer
NEED NOT implement the Host Resources MIB. 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 to be MANDATORY groups and all MANDATORY attributes that are required to
implemented by an agent according to Section 3.1.2 and SHALL either be implemented by an agent according to Section 3.1.2 and SHALL
present them to the user or ignore them. either present them to the user or ignore them.
2.SHALL accept the full syntactic range for all attributes, including
enum and bit values specified in this specification and additional
ones that may be registered with IANA and SHALL either present them
to the user or ignore them. In particular, a conforming job
monitoring application SHALL not malfunction when receiving any
standard or registered enum or bit values. See Section 3.6 entitled
"IANA Considerations".
3.SHALL NOT fail when operating with agents that materialize attributes 2. SHALL accept the full syntactic range for all attributes,
after the job has been submitted, as opposed to when the job is including enum and bit values specified in this specification and
submitted. additional ones that may be registered with IANA and SHALL either
present them to the user or ignore them. In particular, a
conforming job monitoring application SHALL not malfunction when
receiving any standard or registered enum or bit values. See
Section 3.6 entitled "IANA Considerations".
Job Monitoring MIB, V0.84 July 21, 1997 3. SHALL NOT fail when operating with agents that materialize
attributes after the job has been submitted, as opposed to when
the job is submitted.
4.SHALL, if it supports a time attribute, accept either form of the 4.SHALL, if it supports a time attribute, accept either form of the
time attribute, since agents are free to implement either time form. time attribute, since agents are free to implement either 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 are:
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
Job Monitoring MIB, V0.85 Aug 8, 1997
In order for a monitoring application to quickly find that active jobs In order for a monitoring application to quickly find that active jobs
(jobs in the pending, processing, or processingStopped states), the MIB (jobs in the pending, processing, or processingStopped states), the MIB
contains two indexes: contains two indexes:
1.jmGeneralOldestActiveJobIndex - the index of the active job that 1.jmGeneralOldestActiveJobIndex - the index of the active job that
has been in the tables the longest. has been in the tables the longest.
2.jmGeneralNewestActiveJobIndex - the index of the active job that 2.jmGeneralNewestActiveJobIndex - the index of the active job that
has been most recently added to the tables. has been most recently added to the tables.
skipping to change at page 23, line 39 skipping to change at page 20, line 26
The agent SHALL assign the next incremental value of jmJobIndex to the The agent SHALL assign the next incremental value of jmJobIndex to the
job, when a new job is accepted by the server or device to which the job, when a new job is accepted by the server or device to which the
agent is providing access. If the incremented value of jmJobIndex would agent is providing access. If the incremented value of jmJobIndex would
exceed the implementation-defined maximum value for jmJobIndex, the exceed the implementation-defined maximum value for jmJobIndex, the
agent SHALL 'wrap' back to 1. An agent uses the resulting value of agent SHALL 'wrap' back to 1. An agent uses the resulting value of
jmJobIndex for storing information in the jmJobTable and the jmJobIndex for storing information in the jmJobTable and the
jmAttributeTable about the job. 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 larger
than the maximum number of jobs that the implementation can contain at a than the maximum number of jobs that the implementation can contain at a
single time, so as to minimize the pre-mature re-use of jmJobIndex value single time, so as to minimize the premature re-use of a jmJobIndex
for a newer job while clients retain the same 'stale' value for an older value for a newer job while clients retain the same 'stale' value for an
job. older job.
It is recommended that agents that are providing access to
servers/devices that already allocate job-identifiers for jobs as
integers use the same integer value for the jmJobIndex. Then the jobs
will have the same job identifier value as the jmJobIndex value, so that
users viewing jobs by management applications using this MIB and
applications using other protocols will see the same job identifiers for
the same jobs. Agents providing access to systems that contain jobs
with a job identifier of 0 SHALL map the job identifier value 0 to a
jmJobIndex value that is one higher than the highest job identifier
value that any job can have on that system. Then only job 0 will have a
different job-identifier value than the job's jmJobIndex value.
NOTE - If a server or device accepts jobs using multiple job submission
protocols, it may be difficult for the agent to meet the recommendation
to use the job-identifier values that the server or device assigns as
the jmJobIndex value, unless the server/device assigns job-identifiers
for each of its job submission protocols from 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 agent
is providing access to AND that job is to be 'active' (pending, 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 SHALL
copy the value of the job's jmJobIndex to the 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
Job Monitoring MIB, V0.85 Aug 8, 1997
'inactive' (pendingHeld state), the agent SHALL not change the value of 'inactive' (pendingHeld state), the agent SHALL not change the value of
jmGeneralNewestActiveJobIndex object. jmGeneralNewestActiveJobIndex object (though the agent SHALL 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 value
that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL
Job Monitoring MIB, V0.84 July 21, 1997
advance (or wrap) the value to the next oldest 'active' job, if any. advance (or wrap) the value to the next oldest 'active' job, if any.
See the JmJobStateTC textual-convention for a definition of the job See the JmJobStateTC textual-convention for a definition of the job
states. 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 one
of the 'active' job states (from pendingHeld to pending or processing), of the 'active' job states (from pendingHeld to pending or processing),
the agent SHALL update the value of either the 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 jmGeneralNewestActiveJobIndex. between jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex.
skipping to change at page 24, line 35 skipping to change at page 21, line 42
oldest active job and continue until they reach the index value equal to oldest active job and continue until they reach the index value equal to
jmGeneralNewestActiveJobIndex, skipping over any pendingHeld, completed, jmGeneralNewestActiveJobIndex, skipping over any pendingHeld, completed,
canceled, or aborted jobs that might intervene. 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 wrapped.
In this case, the application SHALL reset the index to 1 when the end of In this case, the application SHALL reset the index to 1 when the end of
the table is reached and continue the GetNext operations to find the the table is reached and continue the GetNext operations to find the
rest of the active jobs. rest of the active jobs.
NOTE - Application detect the end of the table when the OID returned by NOTE - Application detect the end of the jmAttributeTable table when the
the GetNext operation is an OID in a different MIB. There is no object OID returned by the GetNext operation is an OID in a different MIB.
in this MIB that specifies the maximum value for the jmJobIndex There is no object in this MIB that specifies the maximum value for the
supported by the implementation. 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 the
next jmJobIndex value to be assigned, so that new jobs are not assigned next jmJobIndex value to be assigned, so that new jobs are not assigned
the same jmJobIndex as recent jobs before the power cycle. the same jmJobIndex as recent jobs before the power cycle.
Job Monitoring MIB, V0.85 Aug 8, 1997
3.3 The Attribute Mechanism 3.3 The Attribute Mechanism
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 be
registered without requiring a new MIB. Also an implementation that registered without requiring a new MIB. Also an implementation that
does not have the functionality represented by the attribute can omit does not have the functionality represented by the attribute can omit
the attribute entirely, rather than having to return a distinguished the attribute entirely, rather than having to return a distinguished
value. The agent is free to materialize an attribute in the value. The agent is free to materialize an attribute in the
jmAttributeTable as soon as the agent is aware of the value of the jmAttributeTable as soon as the agent is aware of the value of the
attribute. attribute.
Job Monitoring MIB, V0.84 July 21, 1997
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
skipping to change at page 25, line 45 skipping to change at page 23, line 5
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 available
or MAY create the row earlier with the designated 'unknown' value or MAY create the row earlier with the designated 'unknown' value
appropriate for that attribute. See next section. appropriate for that attribute. See next section.
Job Monitoring MIB, V0.85 Aug 8, 1997
If the server or device does not implement or does not provide access to 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 the information about an attribute, the agent SHOULD NOT create the
corresponding row in the jmAttributeTable. 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.
Job Monitoring MIB, V0.84 July 21, 1997
SNMP requires that if an object cannot be implemented because its values SNMP requires that if an object cannot be implemented because its values
cannot be accessed, then a compliant agent SHALL return an SNMP error in cannot be accessed, then a compliant agent SHALL return an SNMP error in
SNMPv1 or an exception value in SNMPv2. However, this MIB has been SNMPv1 or an exception value in SNMPv2. However, this MIB has been
designed so that 'all' objects can and SHALL be implemented by an agent, designed so that 'all' objects can and SHALL be implemented by an agent,
so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be
generated by the agent. This MIB has also been designed so that when an generated by the agent. This MIB has also been designed so that when an
agent materializes an attribute, the agent SHALL materialize a row agent materializes an attribute, the agent SHALL materialize a row
consisting of both the jmAttributeValueAsInteger and consisting of both the jmAttributeValueAsInteger and
jmAttributeValueAsOctets objects. jmAttributeValueAsOctets objects.
skipping to change at page 26, line 44 skipping to change at page 24, line 4
object. object.
3.3.3 Data Sub-types and Attribute Naming Conventions 3.3.3 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 have indicated on the first line(s) of the description. Some attributes have
several different data sub-type representations. When an attribute has several different data sub-type representations. When an attribute has
both an Integer32 data sub-type and an OCTET STRING data sub-type, the both an Integer32 data sub-type and an OCTET STRING data sub-type, the
attribute can be represented in a single row in the jmAttributeTable. attribute can be represented in a single row in the jmAttributeTable.
Job Monitoring MIB, V0.85 Aug 8, 1997
In this case, the data sub-type name is not included as the last part of In this case, the data sub-type name is not included as the last part of
the name of the attribute, e.g., documentFormat(38) which is both an the name of the attribute, e.g., documentFormat(38) which is both an
enum and/or a name. When the data sub-types cannot be represented by a enum and/or a name. When the data sub-types cannot be represented by a
single row in the jmAttributeTable, each such representation is single row in the jmAttributeTable, each such representation is
considered a separate attribute and is assigned a separate name and enum considered a separate attribute and is assigned a separate name and enum
value. For these attributes, the name of the data sub-type is the last value. For these attributes, the name of the data sub-type is the last
part of the name of the attribute: Name, Index, DateAndTime, TimeStamp, part of the name of the attribute: Name, Index, DateAndTime, TimeStamp,
etc. For example, documentFormatIndex(37) is an index. etc. For 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 such sub-types of each attribute, using the textual-convention name when such
Job Monitoring MIB, V0.84 July 21, 1997
is defined. The following abbreviations are used in the Table of is defined. The following abbreviations are used in the Table of
Contents as shown: 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))
'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.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes
Most attributes SHALL have only one row per job. However, a few Most attributes SHALL have only one row per job. However, a few
attributes can have multiple values per job or even per document, where attributes can have multiple values per job or even per document, where
each value is a separate row in the jmAttributeTable. Unless indicated each value is a separate row in the jmAttributeTable. Unless indicated
with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL
ensure that each attribute occurs only once in the jmAttributeTable for ensure that each attribute occurs only once in the jmAttributeTable for
skipping to change at page 27, line 38 skipping to change at page 24, line 45
attributes can have multiple values per job or even per document, where attributes can have multiple values per job or even per document, where
each value is a separate row in the jmAttributeTable. Unless indicated each value is a separate row in the jmAttributeTable. Unless indicated
with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL
ensure that each attribute occurs only once in the jmAttributeTable for ensure that each attribute occurs only once in the jmAttributeTable for
a job. Most of the 'MULTI-ROW' attributes do not allow duplicate a job. Most of the 'MULTI-ROW' attributes do not allow duplicate
values, i.e., the agent SHALL ensure that each value occurs only once values, i.e., the agent SHALL ensure that each value occurs only once
for a job. Only if the specification of the 'MULTI-ROW' attribute also for a job. Only if the specification of the 'MULTI-ROW' attribute also
says "the values NEED NOT be unique" can the agent allow duplicate says "the values NEED NOT be unique" can the agent allow duplicate
values to occur for the job. values to occur for the job.
NOTE - Duplicate are allowed for 'extensive' 'MULTI-ROW' attributes, NOTE - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes,
such as fileName(34) or documentName(35), but are not allowed for such as fileName(34) or documentName(35) which are specified to be 'per-
'intensive' 'MULTI-ROW' attributes, such as mediumConsumed(171) and document' attributes, but are not allowed for 'intensive' 'MULTI-ROW'
documentFormat(38). attributes, such as mediumConsumed(171) and documentFormat(38) which are
specified to be 'per-job' attributes.
3.3.5 Requested Attributes 3.3.5 Requested Attributes
A number of attributes record requirements for the job. Such attribute A number of attributes record requirements for the job. Such attribute
names end with the word 'Requested'. In the interests of brevity, the names end with the word 'Requested'. In the interests of brevity, the
Job Monitoring MIB, V0.85 Aug 8, 1997
phrase 'requested' SHALL mean: (1) requested by the client (or phrase 'requested' SHALL mean: (1) requested by the client (or
intervening server) in the job submission protocol and MAY also mean (2) intervening server) in the job submission protocol and MAY also mean (2)
embedded in the submitted document data, and/or (3) defaulted by the embedded in the submitted document data, and/or (3) defaulted by the
recipient device or server with the same semantics as if the requester recipient device or server with the same semantics as if the requester
had supplied, depending on implementation. had supplied, depending on implementation.
Job Monitoring MIB, V0.84 July 21, 1997
3.3.6 Consumption Attributes 3.3.6 Consumption Attributes
A number of attributes record consumption. Such attribute names end A number of attributes record consumption. Such attribute names end
with the word 'Completed' or 'Consumed'. If the job has not yet with the word 'Completed' or 'Consumed'. If the job has not yet
consumed what that resource is metering, the agent either: (1) SHALL consumed what that resource is metering, the agent either: (1) SHALL
return the value 0 or (2) SHALL not add this attribute to the return the value 0 or (2) SHALL not add this attribute to the
jmAttributeTable until the consumption begins. In the interests of jmAttributeTable until the consumption begins. In the interests of
brevity, the semantics for 0 is specified once here and is not repeated brevity, the semantics for 0 is specified once here and is not repeated
for each consumptive attribute specification. for each consumptive attribute specification.
skipping to change at page 28, line 31 skipping to change at page 25, line 36
index value for a particular index attribute for a job, the agent SHALL 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 the either: (1) return the value 0 or (2) not add this attribute to the
jmAttributeTable until the index value is assigned. In the interests of jmAttributeTable until the index value is assigned. In the interests of
brevity, the semantics for 0 is specified once here and is not repeated brevity, the semantics for 0 is specified once here and is not repeated
for each index attribute specification. for each index attribute specification.
3.4 Job Identification 3.4 Job Identification
There are a number of attributes that permit a user, operator or system There are a number of attributes that permit a user, operator or system
administrator to identify jobs of interest, such as jobName, administrator to identify jobs of interest, such as jobName,
jobOriginatingHost, etc. In addition, there is a Job Submission ID jobOriginatingHost, etc. In addition, there is a jmJobSubmissionID
object that allows a monitoring application to quickly locate and object that is a text string table index. Being a table index allows a
identify a particular job of interest that was submitted from a monitoring application to quickly locate and identify a particular job
particular client by the user invoking the monitoring application. The of interest that was submitted from a particular client by the user
Job Monitoring MIB needs to provide for identification of the job at invoking the monitoring application. The Job Monitoring MIB needs to
both sides of the job submission process. The primary identification provide for identification of the job at both sides of the job
point is the client side. The Job Submission ID allows the monitoring submission process. The primary identification point is the client
application to identify the job of interest from all the jobs currently side. The jmJobSubmissionID allows the monitoring application to
"known" by the server or device. The Job Submission ID can be assigned identify the job of interest from all the jobs currently "known" by the
by either the client's local system or a downstream server or device. server or device. The value of jmJobSubmissionID can be assigned by
The point of assignment depends on the job submission protocol in use. either the client's local system or a downstream server 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, SHALL
be assigned by the SNMP Job Monitoring MIB agent when the server or be assigned by the SNMP Job Monitoring MIB agent when the server or
device accepts the jobs from submitting clients. The jmJobIndex object device accepts the jobs from submitting clients. The jmJobIndex object
allows the interested party to obtain all objects desired that relate to allows the interested party to obtain all objects desired that relate to
this job. The MIB provides a mapping table that maps each Job a particular job. See Section 3.2, entitled 'The Job Tables and the
Submission ID (generated by the client) to the corresponding jmJobIndex Job Monitoring MIB, V0.85 Aug 8, 1997
value generated by the agent, so that an application can determine the
correct value for the jmJobIndex value for the job of interest in a
single Get operation, given the Job Submission ID. See the
jmJobIDGroup.
Job Monitoring MIB, V0.84 July 21, 1997 Oldest Active and Newest Active Indexes' for the specification of how
the agent shall assign the jmJobIndex values.
NOTE - For a number of job submission protocols the server/device
assigns an integer job identifier when accepting a job so that the
submitting client can reference the job in subsequent protocol
operations (For example, see IPP [ipp]). For such implementations, it
is recommended that the value of the job identifier and the value of
jmJobIndex be the same, so that
The MIB provides a mapping table that maps each jmJobSubmissionID value
to the corresponding jmJobIndex value generated by the agent, so that an
application can determine the correct value for the jmJobIndex value for
the job of interest in a single Get operation, given the Job Submission
ID. See the jmJobIDGroup.
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 Internationalization Considerations 3.5 Internationalization Considerations
There are a number of objects in this MIB that are represented as coded This section describes the internationalization considerations included
character sets with a data type of OCTET STRING. Most of the objects in this MIB.
are supplied as job attributes by the client that submits the job to the
server or device and so are represented in the coded character set
specified by that client.
For simplicity, this specification assumes that the clients, job 3.5.1 'JmUTF8StringTC' for text generated by the server or device
monitoring applications, servers, and devices are all running in the
same locale, including locales that use two-octet coded character sets, There are a few objects and attributes that are represented using the
such as ISO 10646 (Unicode). Job monitoring applications are expected Universal Multiple-Octet Coded Character Set (UCS) [ISO-10646] encoded
to understand the coded character set of the client (and job), server, as an octet string using the UTF-8 [UTF-8] character encoding scheme.
or device. No special means is provided for the monitor to discover the The 'JmUTF8StringTC' textual convention is used to indicate UTF-8 text
coded character set used by jobs or by the server or device. This strings. These objects and attributes are always supplied (if
specification does not contain an object that indicates what locale the implemented) by the agent, not by the job submitting client:
server or device is running in, let alone contain an object to control 1. jmGeneralJobSetName object
what locale the agent is to use to represent coded character set 2. processingMessage(6) attribute
objects. 3. physicalDevice(32) (name value) attribute
The coded character set for representing these objects and attributes
SHALL be UTF-8 as recommended by RFC 2130 [RFC 2130] and the "IETF
Policy on Character Sets and Language" [char-set policy].
NOTE - For strings in 7-bit US-ASCII, there is no impact since the UTF-8
representation is identical to the US-ASCII [US-ASCII] encoding.
3.5.2 'JmJobStringTC' for text generated by the job submitter
All of the objects and attributes represented by the 'JmJobStringTC'
textual-convention are either (1) supplied in the job submission
Job Monitoring MIB, V0.85 Aug 8, 1997
protocol by the client that submits the job to the server or device or
(2) are defaulted by the server or device if the job submitting client
does not supply values. 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. In any case, the resulting coded
character set representation SHOULD be UTF-8 [UTF-8], but SHALL be one
in which the code positions from 0 to 31 SHALL not be used, 32 to 127
SHALL be US-ASCII [US-ASCII], 127 SHALL be unused, and the remaining
code positions 128 to 255 SHALL represent single-byte or multi-byte
graphic characters structured according to ISO 2022 [ISO 2022] or SHALL
be unused.
The coded character set SHALL be one of the ones registered with IANA
[IANA] and SHALL be identified by the jobCodedCharSet attribute in the
jmJobAttributeTable for the job. If the agent does not know what coded
character set was used by the job submitting client, the agent SHALL
return the 'unknown(2)' value for the jobCodedCharSet attribute for the
job.
Examples of coded character sets which meet this criteria for use as 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, 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 Chinese
[GB2312]. See the IANA registry of coded character sets [IANA
charsets].
Examples of coded character sets which do not meet this criteria are:
national 7-bit sets conforming to ISO 646 (except US-ASCII), EBCDIC, and
ISO 10646 (Unicode) [ISO-10646]. In order to represent Unicode
characters, the UTF-8 [UTF-8] encoding scheme SHALL be used which has
been assigned the MIBenum value of '106' by IANA.
The jobCodedCharSet attribute uses the imported 'CodedCharSet' textual-
convention from the Printer MIB [printmib].
3.5.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 the
user running the monitoring application. user running the monitoring application.
3.6 IANA Considerations 3.6 IANA Considerations
During the development of this standard, the Printer Working Group (PWG) During the development of this standard, the Printer Working Group (PWG)
working with IANA [iana] will register additional enums while the working with IANA [iana] will register additional enums while the
Job Monitoring MIB, V0.85 Aug 8, 1997
standard is in the proposed and draft states according to the procedures standard is in the proposed and draft states according to the procedures
described in this section. IANA will handle registration of additional described in this section. IANA will handle registration of additional
enums after this standard is approved in cooperation with an IANA- enums after this standard is approved in cooperation with an IANA-
appointed registration editor from the PWG according to the procedures appointed registration editor from the PWG according to the procedures
described in this section: described in this section:
3.6.1 IANA Registration of enums 3.6.1 IANA Registration of enums
This specification uses textual conventions to define enumerated values This specification uses textual conventions to define enumerated values
(enums) and bit values. Enumerations (enums) and bit values are sets of (enums) and bit values. Enumerations (enums) and bit values are sets of
symbolic values defined for use with one or more objects or attributes. symbolic values defined for use with one or more objects or attributes.
All enumeration sets and bit value sets are assigned a symbolic data All enumeration sets and bit value sets are assigned a symbolic data
type name (textual convention). As a convention the symbolic name ends type name (textual convention). As a convention the symbolic name ends
in "TC" for textual convention. These enumerations are defined at the in "TC" for textual convention. These enumerations are defined at the
beginning of the MIB module specification. beginning of the MIB module specification.
Job Monitoring MIB, V0.84 July 21, 1997
This working group has defined several type of enumerations for use in This working group has defined several type of enumerations for use in
the Job Monitoring MIB and the Printer MIB[print-mib]. These types the Job Monitoring MIB and the Printer MIB[print-mib]. These types
differ in the method employed to control the addition of new differ in the method employed to control the addition of new
enumerations. Throughout this document, references to "type n enum", enumerations. Throughout this document, references to "type n enum",
where n can be 1, 2 or 3 can be found in the various tables. The where n can be 1, 2 or 3 can be found in the various tables. The
definitions of these types of enumerations are: definitions of these types of enumerations are:
3.6.1.1 Type 1 enumerations 3.6.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
skipping to change at page 30, line 30 skipping to change at page 28, line 45
There are no type 1 enums in the current draft. There are no type 1 enums in the current draft.
3.6.1.2 Type 2 enumerations 3.6.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 after review by this working group or an editor appointed by registered after review by this working group or an editor appointed by
IANA after this working group is no longer active. IANA after this working group is no longer active.
The following type 2 enums are contained in the current draft : The following type 2 enums are contained in the current draft :
1. JmUTF8StringTC
1.JmTimeStampTC 2. JmJobStringTC
3. JmTimeStampTC
2.JmFinishingTC [same enum values as IPP "finishing" attribute] 4. JmFinishingTC [same enum values as IPP "finishing" attribute]
5. JmPrintQualityTC [same enum values as IPP "print-quality"
3.JmPrintQualityTC [same enum values as IPP "print-quality"
attribute] attribute]
6. JmTonerEconomyTC
7. JmMediumTypeTC
8. JmJobSubmissionTypeTC
Job Monitoring MIB, V0.85 Aug 8, 1997
4.JmTonerEconomyTC 9. JmJobStateTC [same enum values as IPP "job-state" attribute]
10.JmAttributeTypeTC
5.JmMediumTypeTC
6.JmJobSubmissionTypeTC
7.JmJobStateTC [same enum values as IPP "job-state" attribute]
8.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 SHALL be simultaneously registered by IANA indicated IPP Job attribute SHALL be simultaneously registered by IANA
for use with IPP [ipp-model] and the Job Monitoring MIB. for use with IPP [ipp-model] and the Job Monitoring MIB.
Job Monitoring MIB, V0.84 July 21, 1997
3.6.1.3 Type 3 enumeration 3.6.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 IANA without working group review. registered through IANA without working group review.
There are no type 3 enums in the current draft. There are no type 3 enums in the current draft.
3.6.2 IANA Registration of type 2 bit values 3.6.2 IANA Registration of type 2 bit values
skipping to change at page 32, line 5 skipping to change at page 30, line 5
procedures for a type 2 enum as specified in Section 3.6.1.2. procedures for a type 2 enum as specified in Section 3.6.1.2.
3.6.4 IANA Registration of MIME types/sub-types for document-formats 3.6.4 IANA 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" names.
The values of the documentFormat(38) attribute are the same as the The values of the documentFormat(38) attribute are the same as the
corresponding Internet Printing Protocol (IPP) "document-format" Job corresponding Internet Printing Protocol (IPP) "document-format" Job
attribute values [ipp-model]. attribute values [ipp-model].
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
3.7 Security Considerations 3.7 Security Considerations
3.7.1 Read-Write objects 3.7.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 accept considerations. If another MIB augments this MIB, that MIB might accept
SNMP Write operations to objects in that MIB whose effect is to modify SNMP Write operations to objects in that MIB whose effect is to modify
the values of read-only objects in this MIB. However, that MIB SHALL the values of read-only objects in this MIB. However, that MIB SHALL
have to support the required access control in order to achieve have to support the required access control in order to achieve
security, not this MIB. security, not this MIB.
3.7.2 Read-Only Objects In Other User's Jobs 3.7.2 Read-Only Objects In Other User's Jobs
The security policy of some sites MAY be that unprivileged users can The security policy of some sites MAY be that unprivileged users can
only get the objects from jobs that they submitted, plus a few minimal only get the objects from jobs that they submitted, plus a few minimal
objects from other jobs, such as the jmJobKOctetsRequested and objects from other jobs, such as the jmJobKOctetsRequested and
jmJobKOctetsCompleted objects, so that a user can tell how busy a jmJobKOctetsProcessed objects, so that a user can tell how busy a
printer is. Other sites MAY allow all unprivileged users to see all printer is. Other sites MAY allow all unprivileged users to see all
objects of all jobs. This MIB does not require, nor does it specify objects of all jobs. This MIB does not require, nor does it specify
how, such restrictions would be implemented. A monitoring application how, such restrictions would be implemented. A monitoring application
SHOULD enforce the site security policy with respect to returning SHOULD enforce the site security policy with respect to returning
information to an unprivileged end user that is using the monitoring information to an unprivileged end user that is using the monitoring
application to monitor jobs that do not belong to that user, i.e., the application to monitor jobs that do not belong to that user, i.e., the
jmJobOwner object in the jmJobTable does not match the user's user name. jmJobOwner 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 objects
of all jobs, independent of the policy for unprivileged users. of all jobs, independent of the policy for unprivileged users.
skipping to change at page 33, line 5 skipping to change at page 31, line 5
This MIB does not specify any notifications. For simplicity, management This MIB does not specify any notifications. For simplicity, management
applications are expected to poll for status. The applications are expected to poll for status. The
jmGeneralJobPersistence and jmGeneralAttributePersistence objects assist jmGeneralJobPersistence and jmGeneralAttributePersistence objects assist
an application to determine the polling rate. The resulting network an application to determine the polling rate. The resulting network
traffic is not expected to be significant. 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, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
Job-Monitoring-MIB DEFINITIONS ::= BEGIN Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed -- The following textual-conventions are needed
-- to implement certain attributes, but are not -- to implement certain attributes, but are not
-- needed to compile this MIB. They are -- needed to compile this MIB. They are
-- provided here for convenience: -- provided here for convenience:
-- hrDeviceIndex FROM HOST-RESOURCES-MIB -- hrDeviceIndex FROM HOST-RESOURCES-MIB
-- DateAndTime FROM SNMPv2-TC -- DateAndTime FROM SNMPv2-TC
-- PrtInterpreterLangFamilyTC FROM Printer-MIB -- PrtInterpreterLangFamilyTC,
-- CodedCharSet FROM Printer-MIB
- -- Use the experimental (54) OID assigned to the Printer MIB[print-mib] -- Use the experimental (54) OID assigned to the Printer MIB[print-mib]
- -- before it was published as RFC 1759. -- before it was published as RFC 1759.
- -- Upon publication of the Job Monitoring MIB as an RFC, delete this -- Upon publication of the Job Monitoring MIB as an RFC, delete this
- -- comment and the line following this comment and change the -- comment and the line following this comment and change the
- -- reference of { temp 105 } (below) to { mib-2 X }. -- reference of { temp 105 } (below) to { mib-2 X }.
- -- This will result in changing: -- This will result in changing:
- -- 1 3 6 1 3 54 jobmonMIB(105) to: -- 1 3 6 1 3 54 jobmonMIB(105) to:
- -- 1 3 6 1 2 1 jobmonMIB(X) -- 1 3 6 1 2 1 jobmonMIB(X)
- -- This will make it easier to translate prototypes to -- This will make it easier to translate prototypes to
- -- the standard namespace because the lengths of the OIDs won't -- the standard namespace because the lengths of the OIDs won't
- -- change. -- change.
temp OBJECT IDENTIFIER ::= { experimental 54 } temp OBJECT IDENTIFIER ::= { experimental 54 }
- change.
jobmonMIB MODULE-IDENTITY jobmonMIB MODULE-IDENTITY
LAST-UPDATED "9707210000Z" LAST-UPDATED "9708080000Z"
ORGANIZATION "IETF Printer MIB Working Group" ORGANIZATION "IETF Printer MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Tom Hastings "Tom Hastings
Postal: Xerox Corp. Postal: Xerox Corp.
Mail stop ESAE-231 Mail stop ESAE-231
701 S. Aviation Blvd. 701 S. Aviation Blvd.
El Segundo, CA 90245 El Segundo, CA 90245
Tel: (301)333-6413 Tel: (301)333-6413
Fax: (301)333-5514 Fax: (301)333-5514
E-mail: hastings@cp10.es.xerox.com E-mail: hastings@cp10.es.xerox.com
Send comments to the printmib WG using the Job Monitoring Send comments to the printmib WG using the Job Monitoring
Project (JMP) Mailing List: jmp@pwg.org Project (JMP) Mailing List: jmp@pwg.org
To learn how to subscribe to the JMP mailing list, To learn how to subscribe to the JMP mailing list,
send email to: jmp-request@pwg.org send email to: jmp-request@pwg.org
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
For further information, access the PWG web page under 'JMP': For further information, access the PWG web page under 'JMP':
http://www.pwg.org/" http://www.pwg.org/"
DESCRIPTION DESCRIPTION
"The MIB module for monitoring job in servers, printers, and "The MIB module for monitoring job in servers, printers, and
other devices. other devices.
File: draft-ietf-printmib-job-monitor-04.txt File: draft-ietf-printmib-job-monitor-05.txt
Version: 0.84" Version: 0.85"
::= { temp 105 } ::= { temp 105 }
- -- Textual conventions for this MIB module -- Textual conventions for this MIB module
JmUTF8StringTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information taken from the ISO/IEC IS 10646-1 character set,
encoded as an octet string using the UTF-8 character encoding
scheme.
NOTE - The values of objects and attributes using this textual
convention are generated by the server or the device, not by the
job submitter."
REFERENCE
"See section 3.5.1, ''JmUTF8StringTC' for text generated by the
server or device'."
SYNTAX OCTET STRING (SIZE (0..63))
JmJobStringTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information using any coded character set registered by IANA
that has the following properties: (1) code positions from 0 to
31 SHALL not be used, (2) 32 to 127 SHALL be US-ASCII [US-
ASCII], (3) 127 SHALL be unused, and (4) the remaining code
Job Monitoring MIB, V0.85 Aug 8, 1997
positions 128 to 255 SHALL represent single-byte or multi-byte
graphic characters structured according to ISO 2022 [ISO 2022]
or SHALL be unused. While it is recommended that the coded
character set be UTF-8 [UTF-8], the actual coded character set
SHALL be indicated by the value of the jobCodedCharSet(7)
attribute for the job.
NOTE - The values of objects and attributes using this textual
convention are either generated by the job submitter or
defaulted by the server or device when the job submitter does
not supply values."
REFERENCE
"See section 3.5.2, ''JmJobStringTC' for text generated by the
job submitter'."
SYNTAX OCTET STRING (SIZE (0..63))
JmTimeStampTC ::= TEXTUAL-CONVENTION JmTimeStampTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The simple time at which an event took place. The units SHALL "The simple time at which an event took place. The units SHALL
be in seconds since the system was booted. be in seconds since the system was booted.
NOTE - JmTimeStampTC is defined in units of seconds, rather than NOTE - JmTimeStampTC is defined in units of seconds, rather than
100ths of seconds, so as to be simpler for agents to implement 100ths of seconds, so as to be simpler for agents to implement
(even if they have to implement the 100ths of a second to comply (even if they have to implement the 100ths of a second to comply
skipping to change at page 34, line 43 skipping to change at page 34, line 4
convention defined in SMNPv2-TC is defined as an APPLICATION 3 convention defined in SMNPv2-TC is defined as an APPLICATION 3
IMPLICIT INTEGER tag, not an Integer32, so cannot be used in IMPLICIT INTEGER tag, not an Integer32, so cannot be used in
this MIB as one of the values of jmAttributeValueAsInteger." this MIB as one of the values of jmAttributeValueAsInteger."
SYNTAX INTEGER(0..2147483647) SYNTAX INTEGER(0..2147483647)
JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source platform type that can submit jobs to servers or "The source platform type that can submit jobs to servers or
devices in any of the 3 configurations." devices in any of the 3 configurations."
Job Monitoring MIB, V0.85 Aug 8, 1997
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
Job Monitoring MIB, V0.84 July 21, 1997
unknown(2), unknown(2),
sptUNIX(3), -- UNIX(tm) sptUNIX(3), -- UNIX(tm)
sptOS2(4), -- OS/2 sptOS2(4), -- OS/2
sptPCDOS(5), -- DOS sptPCDOS(5), -- DOS
sptNT(6), -- NT sptNT(6), -- NT
sptMVS(7), -- MVS sptMVS(7), -- MVS
sptVM(8), -- VM sptVM(8), -- VM
sptOS400(9), -- OS/400 sptOS400(9), -- OS/400
sptVMS(10), -- VMS sptVMS(10), -- VMS
sptWindows95(11), -- Windows95 sptWindows95(11), -- Windows95
skipping to change at page 35, line 46 skipping to change at page 35, line 5
Perform no finishing. Perform no finishing.
staple(4), staple(4),
Bind the document(s) with one or more staples. The exact Bind the document(s) with one or more staples. The exact
number and placement of the staples is site-defined. number and placement of the staples is site-defined.
stapleTopLeft(5), stapleTopLeft(5),
Place one or more staples on the top left corner of the Place one or more staples on the top left corner of the
document(s). document(s).
Job Monitoring MIB, V0.85 Aug 8, 1997
stapleBottomLeft(6), stapleBottomLeft(6),
Place one or more staples on the bottom left corner of the Place one or more staples on the bottom left corner of the
document(s). document(s).
Job Monitoring MIB, V0.84 July 21, 1997
stapleTopRight(7), stapleTopRight(7),
Place one or more staples on the top right corner of the Place one or more staples on the top right corner of the
document(s). document(s).
stapleBottomRight(8), stapleBottomRight(8),
Place one or more staples on the bottom right corner of the Place one or more staples on the bottom right corner of the
document(s). document(s).
saddleStitch(9), saddleStitch(9),
Bind the document(s) with one or more staples (wire Bind the document(s) with one or more staples (wire
skipping to change at page 36, line 51 skipping to change at page 36, line 4
specific." specific."
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
none(3), none(3),
staple(4), staple(4),
stapleTopLeft(5), stapleTopLeft(5),
stapleBottomLeft(6), stapleBottomLeft(6),
Job Monitoring MIB, V0.85 Aug 8, 1997
stapleTopRight(7), stapleTopRight(7),
stapleBottomRight(8), stapleBottomRight(8),
saddleStitch(9), saddleStitch(9),
edgeStitch(10), edgeStitch(10),
Job Monitoring MIB, V0.84 July 21, 1997
punch(11), punch(11),
cover(12), cover(12),
bind(13) bind(13)
} }
JmPrintQualityTC ::= TEXTUAL-CONVENTION JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Print quality settings. "Print quality settings.
skipping to change at page 37, line 41 skipping to change at page 37, line 4
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 in by a SIGNED-BYTE. The values are the same as those specified in
the Printer MIB [printmib]. The first SIGNED-INTEGER contains the Printer MIB [printmib]. The first SIGNED-INTEGER contains
the value of prtMarkerAddressabilityXFeedDir. The second the value of prtMarkerAddressabilityXFeedDir. The second
SIGNED-INTEGER contains the value of SIGNED-INTEGER contains the value of
Job Monitoring MIB, V0.85 Aug 8, 1997
prtMarkerAddressabilityFeedDir. The SIGNED-BYTE contains the prtMarkerAddressabilityFeedDir. The SIGNED-BYTE contains the
value of prtMarkerAddressabilityUnit. value of prtMarkerAddressabilityUnit.
Note: the latter value is either 3 (tenThousandsOfInches) or 4 Note: the latter value is either 3 (tenThousandsOfInches) or 4
(micrometers) and the addressability is in 10,000 units of (micrometers) and the addressability is in 10,000 units of
Job Monitoring MIB, V0.84 July 21, 1997
measure. Thus the SIGNED-INTEGERs represent integral values in measure. Thus the SIGNED-INTEGERs represent integral values in
either dots-per-inch or dots-per-centimeter. either dots-per-inch or dots-per-centimeter.
The syntax is the same as the IPP 'printer-resolution' The syntax is the same as the IPP 'printer-resolution'
attribute. See Section 3.6.1.2." attribute. See Section 3.6.1.2."
SYNTAX OCTET STRING (SIZE(9)) SYNTAX OCTET STRING (SIZE(9))
JmTonerEconomyTC ::= TEXTUAL-CONVENTION JmTonerEconomyTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 38, line 37 skipping to change at page 38, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Boolean true or false value." "Boolean true or false value."
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(2), -- unknown. unknown(2), -- unknown.
false(3), -- FALSE. false(3), -- FALSE.
true(4) -- TRUE. true(4) -- TRUE.
} }
Job Monitoring MIB, V0.85 Aug 8, 1997
JmMediumTypeTC ::= TEXTUAL-CONVENTION JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"Identifies the type of medium. "Identifies the type of medium.
other(1), other(1),
The type is neither one of the values listed in this The type is neither one of the values listed in this
specification nor a registered value. specification nor a registered value.
unknown(2), unknown(2),
The type is not known. The type is not known.
skipping to change at page 39, line 49 skipping to change at page 39, line 5
connected along the short edge. connected along the short edge.
tabStock(10), tabStock(10),
Media with tabs. Media with tabs.
multiPartForm(11), multiPartForm(11),
Form medium composed of multiple layers not pre-attached to Form medium composed of multiple layers not pre-attached to
one another; each sheet MAY be drawn separately from an one another; each sheet MAY be drawn separately from an
input source. input source.
Job Monitoring MIB, V0.85 Aug 8, 1997
labels(12), labels(12),
Label-stock. Label-stock.
multiLayer(13) multiLayer(13)
Form medium composed of multiple layers which are pre- Form medium composed of multiple layers which are pre-
attached to one another, e.g. for use with impact printers." attached to one another, e.g. for use with impact printers."
Job Monitoring MIB, V0.84 July 21, 1997
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
stationery(3), stationery(3),
transparency(4), transparency(4),
envelope(5), envelope(5),
envelopePlain(6), envelopePlain(6),
envelopeWindow(7), envelopeWindow(7),
skipping to change at page 40, line 44 skipping to change at page 40, line 5
ASCII coded character string, consisting of the following ASCII coded character string, consisting of the following
fields: fields:
octet 1 The format letter. octet 1 The format letter.
octets 2-40 A 39-character, ASCII trailing SPACE filled octets 2-40 A 39-character, ASCII trailing SPACE filled
field specified by the format letter, if the field specified by the format letter, if the
data is less than 39 ASCII characters. data is less than 39 ASCII characters.
octets 41-48 A sequential or random number to make the ID octets 41-48 A sequential or random number to make the ID
quasi-unique. quasi-unique.
Job Monitoring MIB, V0.85 Aug 8, 1997
If the client does not supply a job submission ID in the job If the client does not supply a job submission ID in the job
submission protocol, then the server SHALL assign a job submission protocol, then the server SHALL assign a job
submission ID using any of the standard formats that are submission ID using any of the standard formats that are
reserved to the agent. Clients SHALL not use formats that are reserved to the agent. Clients SHALL not use formats that are
reserved to agents. reserved to agents.
Job Monitoring MIB, V0.84 July 21, 1997
The format values defined at the time of completion of the The format values defined at the time of completion of the
specification are: specification are:
Format Format
Letter Description Letter Description
------ ------------ ------ ------------
'0' octets 2-40: last 39 bytes of the jmJobOwner '0' octets 2-40: last 39 bytes of the jmJobOwner
object. object.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
This format is reserved to agents for use when This format is reserved to agents for use when
the client does not supply a job submission ID. the client does not supply a job submission ID.
Clients wishing to use a job submission ID that Clients wishing to use a job submission ID that
incorporates the job owner, SHALL use format '8'. incorporates the job owner, SHALL use format '8',
not format '0', in order to reduce the chances of
one client assigning the same ID as the agent when
receiving a job from another client that does not
supply a job submission id.
NOTE - other formats may be registered that are NOTE - other formats may be registered that are
reserved to the agent for use when the client does reserved to the agent for use when the client does
not supply a job submission ID. not supply a job submission ID.
'1' octets 2-40: last 39 bytes of the jobName attribute. '1' octets 2-40: last 39 bytes of the jobName attribute.
octets 41-48: 8-decimal-digit random number octets 41-48: 8-decimal-digit random number
'2' octets 2-40: Client MAC address: in hexadecimal '2' octets 2-40: Client MAC address: in hexadecimal
with each nibble of the 6 octet address being with each nibble of the 6 octet address being
skipping to change at page 41, line 45 skipping to change at page 41, line 4
[URI-spec]. [URI-spec].
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'4' octets 2-40: last 39 bytes of the URI [URI-spec] '4' octets 2-40: last 39 bytes of the URI [URI-spec]
assigned by the server or device to the job when assigned by the server or device to the job when
the job was submitted for processing. the job was submitted for processing.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'5' octets 2-40: last 39 bytes of a user number, such '5' octets 2-40: last 39 bytes of a user number, such
as POSIX user number. as POSIX user number.
Job Monitoring MIB, V0.85 Aug 8, 1997
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'6' octets 2-40: last 39 bytes of the user account '6' octets 2-40: last 39 bytes of the user account
number. number.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'7' octets 2-40: last 39 bytes of the DTMF incoming '7' octets 2-40: last 39 bytes of the DTMF incoming
FAX routing number. FAX routing number.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
Job Monitoring MIB, V0.84 July 21, 1997
'8' octets 2-40: last 39 bytes of the job owner name '8' octets 2-40: last 39 bytes of the job owner name
(that the agent returns in the jmJobOwner object). (that the agent returns in the jmJobOwner object).
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
NOTE - the job submission id is only intended to be unique NOTE - the job submission id is only intended to be unique
between a limited set of clients for a limited duration of time, between a limited set of clients for a limited duration of time,
namely, for the life time of the job in the context of the namely, for the life time of the job in the context of the
server or device that is processing the job. Some of the server or device that is processing the job. Some of the
formats include something that is unique per client and a random formats include something that is unique per client and a random
number so that the same job submitted by the same client will number so that the same job submitted by the same client will
skipping to change at page 42, line 40 skipping to change at page 42, line 5
SYNTAX OCTET STRING(SIZE(1)) -- ASCII '0'-'9', 'A'-'Z', 'a'-'z' SYNTAX OCTET STRING(SIZE(1)) -- ASCII '0'-'9', 'A'-'Z', 'a'-'z'
JmJobStateTC ::= TEXTUAL-CONVENTION JmJobStateTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the job (pending, processing, completed, "The current state of the job (pending, processing, completed,
etc.). etc.).
The following figure shows the normal job state transitions: The following figure shows the normal job state transitions:
Job Monitoring MIB, V0.85 Aug 8, 1997
+----> canceled(7) +----> canceled(7)
/ /
+---> pending(3) --------> processing(5) ------+------> completed(9) +---> pending(3) --------> processing(5) ------+------> completed(9)
| ^ ^ \ | ^ ^ \
- --->+ | | +----> aborted(8) --->+ | | +----> aborted(8)
| v v / | v v /
+---> pendingHeld(4) processingStopped(6) ---+ +---> pendingHeld(4) processingStopped(6) ---+
Figure 4 - Normal Job State Transitions Figure 4 - Normal Job State Transitions
Job Monitoring MIB, V0.84 July 21, 1997
Normally a job progresses from left to right. Other state Normally a job progresses from left to right. Other state
transitions are unlikely, but are not forbidden. Not shown are transitions are unlikely, but are not forbidden. Not shown are
the transitions to the canceled state from the pending, the transitions to the canceled state from the pending,
pendingHeld, processing, and processingStopped states. pendingHeld, processing, and processingStopped states.
Jobs in the pending, processing, and processingStopped states Jobs in the pending, processing, and processingStopped states
are called 'active', while jobs in the pendingHeld, canceled, are called 'active', while jobs in the pendingHeld, canceled,
aborted, and completed are called 'inactive'. aborted, and completed are called 'inactive'.
These values are the same as the enum values of the IPP 'job- These values are the same as the enum values of the IPP 'job-
state' job attribute. See Section 3.6.1.2. state' job attribute. See Section 3.6.1.2.
other(1),
The job state is not one of the defined states.
unknown(2), unknown(2),
The job state is not known, or its state is indeterminate. The job state is not known, or its state is indeterminate.
pending(3), pending(3),
The job is a candidate to start processing, but is not yet The job is a candidate to start processing, but is not yet
processing. processing.
pendingHeld(4), pendingHeld(4),
The job is not a candidate for processing for any number of The job is not a candidate for processing for any number of
reasons but will return to the pending state as soon as the reasons but will return to the pending state as soon as the
skipping to change at page 43, line 45 skipping to change at page 43, line 4
processing. The reasons are represented as bits in the processing. The reasons are represented as bits in the
jmJobStateReasons1 object and/or jobStateReasonsN (N=2..4) jmJobStateReasons1 object and/or jobStateReasonsN (N=2..4)
attributes. See the JmJobStateReasonsNTC (N=1..4) textual attributes. See the JmJobStateReasonsNTC (N=1..4) textual
convention for the specification of each reason. convention for the specification of each reason.
processing(5), processing(5),
Either: Either:
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 more
document transforms which include (1) purely software document transforms which include (1) purely software
Job Monitoring MIB, V0.85 Aug 8, 1997
processes that are interpreting a PDL, and (2) hardware processes that are interpreting a PDL, and (2) hardware
devices that are interpreting a PDL, making marks on a devices that are interpreting a PDL, making marks on a
medium, and/or performing finishing, such as stapling, etc. medium, and/or performing finishing, such as stapling, etc.
OR OR
2. (configuration 2) the server has made the job ready for 2. (configuration 2) the server has made the job ready for
printing, but the output device is not yet printing it, printing, but the output device is not yet printing it,
either because the job hasn't reached the output device or either because the job hasn't reached the output device or
Job Monitoring MIB, V0.84 July 21, 1997
because the job is queued in the output device or some other because the job is queued in the output device or some other
spooler, awaiting the output device to print it. 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 device state includes the detailed status represented in the device
MIB indicated by the hrDeviceIndex value of the job's MIB indicated by the hrDeviceIndex value of the job's
physicalDevice attribute, if the agent implements such a physicalDevice attribute, if the agent implements such a
device MIB. device MIB.
Implementations MAY, though they NEED NOT, include Implementations MAY, though they NEED NOT, include
skipping to change at page 44, line 47 skipping to change at page 44, line 5
MIB using the job's deviceIndex attribute(s), if the agent MIB using the job's deviceIndex attribute(s), if the agent
implements such a device MIB implements such a device MIB
canceled(7), canceled(7),
A client has canceled the job and the job is either: (1) in A client has canceled the job and the job is either: (1) in
the process of being terminated by the server or device or the process of being terminated by the server or device or
(2) has completed terminating. The job's jmJobStateReasons1 (2) has completed terminating. The job's jmJobStateReasons1
object SHOULD contain either the canceledByUser or object SHOULD contain either the canceledByUser or
canceledByOperator value. canceledByOperator value.
Job Monitoring MIB, V0.85 Aug 8, 1997
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. job was in the processing or processingStopped 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). The successfully stacked in the appropriate output bin(s). The
Job Monitoring MIB, V0.84 July 21, 1997
job's jmJobStateReasons1 object SHOULD contain one of: job's jmJobStateReasons1 object SHOULD contain one of:
completedSuccessfully, completedWithWarnings, or completedSuccessfully, completedWithWarnings, or
completedWithErrors values." completedWithErrors values."
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1),
unknown(2), unknown(2),
pending(3), pending(3),
pendingHeld(4), pendingHeld(4),
processing(5), processing(5),
processingStopped(6), processingStopped(6),
canceled(7), canceled(7),
aborted(8), aborted(8),
completed(9) completed(9)
} }
skipping to change at page 45, line 46 skipping to change at page 45, line 5
values of either an integer, an octets representation, or both, values of either an integer, an octets representation, or both,
depending on implementation. These attributes are indicated depending on implementation. These attributes are indicated
with 'INTEGER:' AND/OR 'OCTETS:' tags. with 'INTEGER:' AND/OR 'OCTETS:' tags.
A very few attributes require both objects at the same time to A very few attributes require both objects at the same time to
represent a pair of useful values (see mediumConsumed(171)). represent a pair of useful values (see mediumConsumed(171)).
These attributes are indicated with 'INTEGER:' AND 'OCTETS:' These attributes are indicated with 'INTEGER:' AND 'OCTETS:'
tags. See the jmAttributeGroup for the descriptions of these tags. See the jmAttributeGroup for the descriptions of these
two MANDATORY objects. two MANDATORY objects.
Job Monitoring MIB, V0.85 Aug 8, 1997
NOTE - The enum assignments are grouped logically with values NOTE - The enum assignments are grouped logically with values
assigned in groups of 20, so that additional values may be assigned in groups of 20, so that additional values may be
registered in the future and assigned a value that is part of registered in the future and assigned a value that is part of
their logical grouping. their logical grouping.
NOTE: No attribute name exceeds 31 characters. NOTE: No attribute name exceeds 31 characters.
Job Monitoring MIB, V0.84 July 21, 1997
The standard attribute types defined at the time of completion The standard attribute types defined at the time of completion
of the specification are: of the specification are:
jmAttributeTypeIndex Datatype jmAttributeTypeIndex Datatype
-------------------- -------- -------------------- --------
other(1), Integer32(-2..2147483647) other(1), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: and/or OCTETS: An attribute that is not in the INTEGER: and/or OCTETS: An attribute that is not in the
skipping to change at page 46, line 42 skipping to change at page 45, line 49
jobStateReasons3(4), JmJobStateReasons3TC jobStateReasons3(4), JmJobStateReasons3TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current
state that augments the jmJobState object. See the state that augments the jmJobState object. See the
description under JmJobStateReasons1TC textual-convention. description under JmJobStateReasons1TC textual-convention.
jobStateReasons4(5), JmJobStateReasons4TC jobStateReasons4(5), JmJobStateReasons4TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current
state that augments the jmJobState object. See the state that augments the jmJobState object. See the
description under JmJobStateReasons1TC textual-convention. description under JmJobStateReasons1TC textual-convention.
processingMessage(6), OCTET STRING(SIZE(0..63)) processingMessage(6), JmUTF8StringTC(SIZE(0..63))
OCTETS: MULTI-ROW: A coded character set message that is OCTETS: MULTI-ROW: A coded character set message that is
generated during the processing of the job as a simple form generated by the server or device during the processing of
of processing log to show progress and any problems. Job Monitoring MIB, V0.85 Aug 8, 1997
the job as a simple form of processing log to show progress
and any problems.
There is no restriction for the same message occurring in There is no restriction for the same message occurring in
multiple rows. multiple rows.
jobCodedCharSet(7), CodedCharSet
INTEGER: The MIBenum identifier of the coded character set
that the agent is using to represent coded character set
objects and attributes of type 'JmJobStringTC'. These 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 attribute.
These MIBenum values are assigned by IANA [IANA-charsets]
when the coded character sets are registered. The coded
character set SHALL be one of the ones registered with IANA
[IANA] and the enum value uses the CodedCharSet textual-
convention from the Printer MIB. See the JmJobStringTC
textual-convention.
If the agent does not know what coded character set was used
by the job submitting client, the agent SHALL return the
'unknown(2)' value for the jobCodedCharSet attribute for the
job. See Section 3.5.2, entitled ''JmJobStringTC' for text
generated by the job submitter'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Identification attributes + Job Identification attributes
+ +
Job Monitoring MIB, V0.84 July 21, 1997
+ The following attributes help an end user, a system + The following attributes help an end user, a system
+ operator, or an accounting program identify a job. + operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobAccountName(21), OCTET STRING(SIZE(0..63)) jobAccountName(21), JmJobStringTC(SIZE(0..63))
OCTETS: Arbitrary binary information which MAY be coded OCTETS: Arbitrary binary information which MAY be coded
character set data or encrypted data supplied by the character set data or encrypted data supplied by the
submitting user for use by accounting services to allocate submitting user for use by accounting services to allocate
Job Monitoring MIB, V0.85 Aug 8, 1997
or categorize charges for services provided, such as a or categorize charges for services provided, such as a
customer account name or number. customer account name or number.
NOTE: This attribute NEED NOT be printable characters. NOTE: This attribute NEED NOT be printable characters.
serverAssignedJobName(22), OCTET STRING(SIZE(0..63)) serverAssignedJobName(22), JmJobStringTC(SIZE(0..63))
OCTETS: Configuration 3 only: The human readable string OCTETS: Configuration 3 only: The human readable string
name, number, or ID of the job as assigned by the server name, number, or ID of the job as assigned by the server
that submitted the job to the device that the agent is that submitted the job to the device that the agent is
providing access to with this MIB. providing access to with this MIB.
NOTE - This attribute is intended for enabling a user to NOTE - This attribute is intended for enabling a user to
find his/her job that a server submitted to a device when find his/her job that a server submitted to a device when
either the client does not support the jmJobSubmissionID or either the client does not support the jmJobSubmissionID or
the server does not pass the jmJobSubmissionID through to the server does not pass the jmJobSubmissionID through to
the device. the device.
jobName(23), OCTET STRING(SIZE(0..63)) jobName(23), JmJobStringTC(SIZE(0..63))
OCTETS: The human readable string name of the job as OCTETS: The human readable string name of the job as
assigned by the submitting user to help the user distinguish assigned by the submitting user to help the user distinguish
between his/her various jobs. This name does not need to be between his/her various jobs. This name does not need to be
unique. unique.
This attribute is intended for enabling a user or the user's This attribute is intended for enabling a user or the user's
application to convey a job name that MAY be printed on a application to convey a job name that MAY be printed on a
start sheet, returned in a query result, or used in start sheet, returned in a query result, or used in
notification or logging messages. notification or logging messages.
In order to assist users to find their jobs for job In order to assist users to find their jobs for job
submission protocols that don't supply a jmJobSubmissionID, submission protocols that don't supply a jmJobSubmissionID,
the agent SHOULD maintain the jobName attribute for the time the agent SHOULD maintain the jobName attribute for the time
specified by the jmGeneralJobPersistence object, rather than specified by the jmGeneralJobPersistence object, rather than
the (shorter) jmGeneralAttributePersistence object. the (shorter) jmGeneralAttributePersistence object.
If this attribute is not specified when the job is If this attribute is not specified when the job is
submitted, no job name is assumed, but implementation submitted, no job name is assumed, but implementation
specific defaults are allowed, such as the value of the specific defaults are allowed, such as the value of the
Job Monitoring MIB, V0.84 July 21, 1997
documentName attribute of the first document in the job or documentName attribute of the first document in the job or
the fileName attribute of the first document in the job. the fileName attribute of the first document in the job.
The jobName attribute is distinguished from the jobComment The jobName attribute is distinguished from the jobComment
attribute, in that the jobName attribute is intended to attribute, in that the jobName attribute is intended to
permit the submitting user to distinguish between different permit the submitting user to distinguish between different
jobs that he/she has submitted. The jobComment attribute is jobs that he/she has submitted. The jobComment attribute is
intended to be free form additional information that a user intended to be free form additional information that a user
might wish to use to communicate with himself/herself, such might wish to use to communicate with himself/herself, such
as a reminder of what to do with the results or to indicate as a reminder of what to do with the results or to indicate
Job Monitoring MIB, V0.85 Aug 8, 1997
a different set of input parameters were tried in several a different set of input parameters were tried in several
different job submissions. different job submissions.
jobServiceTypes(24), JmJobServiceTypesTC jobServiceTypes(24), JmJobServiceTypesTC
INTEGER: Specifies the type(s) of service to which the job INTEGER: Specifies the type(s) of service to which the job
has been submitted (print, fax, scan, etc.). The service has been submitted (print, fax, scan, etc.). The service
type is bit encoded with each job service type so that more type is bit encoded with each job service type so that more
general and arbitrary services can be created, such as general and arbitrary services can be created, such as
services with more than one destination type, or ones with services with more than one destination type, or ones with
only a source or only a destination. For example, a job only a source or only a destination. For example, a job
skipping to change at page 49, line 4 skipping to change at page 48, line 44
INTEGER: The index of the row in the associated Printer INTEGER: The index of the row in the associated Printer
MIB[print-mib] of the channel which is the source of the MIB[print-mib] of the channel which is the source of the
print job. print job.
jobSourcePlatformType(26), JmJobSourcePlatformTypeTC jobSourcePlatformType(26), JmJobSourcePlatformTypeTC
INTEGER: The source platform type of the immediate upstream INTEGER: The source platform type of the immediate upstream
submitter that submitted the job to the server submitter that submitted the job to the server
(configuration 2) or device (configuration 1 and 3) to which (configuration 2) or device (configuration 1 and 3) to which
the agent is providing access. For configuration 1, this is the agent is providing access. For configuration 1, this is
the type of the client that submitted the job to the device; the type of the client that submitted the job to the device;
Job Monitoring MIB, V0.84 July 21, 1997
for configuration 2, this is the type of the client that for configuration 2, this is the type of the client that
submitted the job to the server; and for configuration 3, submitted the job to the server; and for configuration 3,
this is the type of the server that submitted the job to the this is the type of the server that submitted the job to the
device. device.
submittingServerName(27), OCTET STRING(SIZE(0..63)) submittingServerName(27), JmJobStringTC(SIZE(0..63))
OCTETS: For configuration 3 only: The administrative name OCTETS: For configuration 3 only: The administrative name
of the server that submitted the job to the device. of the server that submitted the job to the device.
submittingApplicationName(28), OCTET STRING(SIZE(0..63)) Job Monitoring MIB, V0.85 Aug 8, 1997
submittingApplicationName(28), JmJobStringTC(SIZE(0..63))
OCTETS: The name of the client application (not the server OCTETS: The name of the client application (not the server
in configuration 3) that submitted the job to the server or in configuration 3) that submitted the job to the server or
device. device.
jobOriginatingHost(29), OCTET STRING(SIZE(0..63)) jobOriginatingHost(29), JmJobStringTC(SIZE(0..63))
OCTETS: The name of the client host (not the server host OCTETS: The name of the client host (not the server host
name in configuration 3) that submitted the job to the name in configuration 3) that submitted the job to the
server or device. server or device.
deviceNameRequested(30), OCTET STRING(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 device requested by the submitting user. name of the target device requested by the submitting user.
For configuration 1, its value corresponds to the Printer For configuration 1, its value corresponds to the Printer
MIB[print-mib]: prtGeneralPrinterName object. For MIB[print-mib]: prtGeneralPrinterName object. For
configuration 2 and 3, its value is the name of the logical configuration 2 and 3, its value is the name of the logical
or physical device that the user supplied to indicate to the or physical device that the user supplied to indicate to the
server on which device(s) they wanted the job to be server on which device(s) they wanted the job to be
processed. processed.
queueNameRequested(31), OCTET STRING(SIZE(0..63)) queueNameRequested(31), 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 queue requested by the submitting user.
For configuration 1, its value corresponds to the queue in For configuration 1, its value corresponds to the queue in
the device for which the agent is providing access. For the device for which the agent is providing access. For
configuration 2 and 3, its value is the name of the queue configuration 2 and 3, its value is the name of the queue
that the user supplied to indicate to the server on which that the user supplied to indicate to the server on which
device(s) they wanted the job to be processed. device(s) they wanted the job to be processed.
NOTE - typically an implementation SHOULD support either the NOTE - typically an implementation SHOULD support either the
deviceNameRequested or queueNameRequested attribute, but not deviceNameRequested or queueNameRequested attribute, but not
both. both.
physicalDevice(32), hrDeviceIndex physicalDevice(32), hrDeviceIndex
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) JmUTF8StringTC(SIZE(0..63))
INTEGER: MULTI-ROW: The index of the physical device MIB INTEGER: MULTI-ROW: The index of the physical device MIB
instance requested/used, such as the Printer MIB[print-mib]. instance requested/used, such as the Printer MIB[print-mib].
Job Monitoring MIB, V0.84 July 21, 1997
This value is an hrDeviceIndex value. See the Host This value is an hrDeviceIndex value. See the Host
Resources MIB[hr-mib]. Resources MIB[hr-mib].
AND/OR AND/OR
OCTETS: MULTI-ROW: The name of the physical device to OCTETS: MULTI-ROW: The name of the physical device to
which the job is assigned. which the job is assigned.
numberOfDocuments(33), Integer32(-2..2147483647) numberOfDocuments(33), Integer32(-2..2147483647)
INTEGER: The number of documents in this job. INTEGER: The number of documents in this job.
fileName(34), OCTET STRING(SIZE(0..63)) Job Monitoring MIB, V0.85 Aug 8, 1997
fileName(34), JmJobStringTC(SIZE(0..63))
OCTETS: MULTI-ROW: The coded character set file name or OCTETS: MULTI-ROW: The coded character set file name or
URI[URI-spec] of the document. URI[URI-spec] of the document.
There is no restriction on the same file name occurring in There is no restriction on the same file name occurring in
multiple rows. multiple rows.
documentName(35), OCTET STRING(SIZE(0..63)) documentName(35), JmJobStringTC(SIZE(0..63))
OCTETS: MULTI-ROW: The coded character set name of the OCTETS: MULTI-ROW: The coded character set name of the
document. document.
There is no restriction on the same document name occurring There is no restriction on the same document name occurring
in multiple rows. in multiple rows.
jobComment(36), OCTET STRING(SIZE(0..63)) jobComment(36), JmJobStringTC(SIZE(0..63))
OCTETS: An arbitrary human-readable coded character text OCTETS: An arbitrary human-readable coded character text
string supplied by the submitting user or the job submitting string supplied by the submitting user or the job submitting
application program for any purpose. For example, a user application program for any purpose. For example, a user
might indicate what he/she is going to do with the printed might indicate what he/she is going to do with the printed
output or the job submitting application program might output or the job submitting application program might
indicate how the document was produced. indicate how the document was produced.
The jobComment attribute is not intended to be a name; see The jobComment attribute is not intended to be a name; see
the jobName attribute. the jobName attribute.
skipping to change at page 51, line 5 skipping to change at page 50, line 43
INTEGER: MULTI-ROW: The index in the prtInterpreterTable INTEGER: MULTI-ROW: The index in the prtInterpreterTable
in the Printer MIB[print-mib] of the page description in the Printer MIB[print-mib] of the page description
language (PDL) or control language interpreter that this job language (PDL) or control language interpreter that this job
requires/uses. A document or a job MAY use more than one requires/uses. A document or a job MAY use more than one
PDL or control language. PDL or control language.
NOTE - As with all intensive attributes where multiple rows NOTE - As with all intensive attributes where multiple rows
are allowed, there SHALL be only one distinct row for each are allowed, there SHALL be only one distinct row for each
distinct interpreter; there SHALL be no duplicates. distinct interpreter; there SHALL be no duplicates.
Job Monitoring MIB, V0.84 July 21, 1997
NOTE - This attribute type is intended to be used with an NOTE - This attribute type is intended to be used with an
agent that implements the Printer MIB and SHALL not be used agent that implements the Printer MIB and SHALL not be used
if the agent does not implement the Printer MIB. Such an if the agent does not implement the Printer MIB. Such an
agent SHALL use the documentFormat attribute instead. agent SHALL use the documentFormat attribute instead.
documentFormat(38), PrtInterpreterLangFamilyTC documentFormat(38), PrtInterpreterLangFamilyTC
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The interpreter language family INTEGER: MULTI-ROW: The interpreter language family
corresponding to the Printer MIB[print-mib] corresponding to the Printer MIB[print-mib]
prtInterpreterLangFamily object, that this job prtInterpreterLangFamily object, that this job
Job Monitoring MIB, V0.85 Aug 8, 1997
requires/uses. A document or a job MAY use more than one requires/uses. A document or a job MAY use more than one
PDL or control language. PDL or control language.
AND/OR AND/OR
OCTETS: MULTI-ROW: The document format registered as a OCTETS: MULTI-ROW: The document format registered as a
media type[iana-media-types], i.e., the name of the MIME media type[iana-media-types], i.e., the name of the MIME
content-type/subtype. Examples: 'application/postscript', content-type/subtype. Examples: 'application/postscript',
'application/vnd.hp-PCL', and 'application/pdf' 'application/vnd.hp-PCL', and 'application/pdf'
skipping to change at page 52, line 4 skipping to change at page 51, line 42
in favor of higher priority jobs). The value 100 is defined in favor of higher priority jobs). The value 100 is defined
to indicate the highest possible priority. Priority is to indicate the highest possible priority. Priority is
expected to be evenly or 'normally' distributed across this expected to be evenly or 'normally' distributed across this
range. The mapping of vendor-defined priority over this range. The mapping of vendor-defined priority over this
range is implementation-specific. range is implementation-specific.
jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC) jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC)
OCTETS: The calendar date and time of day after which the OCTETS: The calendar date and time of day after which the
job SHALL become a candidate to be scheduled for processing. job SHALL become a candidate to be scheduled for processing.
If the value of this attribute is in the future, the server If the value of this attribute is in the future, the server
Job Monitoring MIB, V0.84 July 21, 1997
SHALL set the value of the job's jmJobState object to SHALL set the value of the job's jmJobState object to
pendingHeld and add the jobProcessAfterSpecified bit value pendingHeld and add the jobProcessAfterSpecified bit value
to the job's jmJobStateReasons1 object. When the specified to the job's jmJobStateReasons1 object. When the specified
date and time arrives, the server SHALL remove the date and time arrives, the server SHALL remove the
jobProcessAfterSpecified bit value from the job's jobProcessAfterSpecified bit value from the job's
jmJobStateReasons1 object and, if no other reasons remain, jmJobStateReasons1 object and, if no other reasons remain,
SHALL change the job's jmJobState object to pending. SHALL change the job's jmJobState object to pending.
jobHold(52), JmBooleanTC jobHold(52), JmBooleanTC
INTEGER: If the value is 'true(4)', a client has explicitly INTEGER: If the value is 'true(4)', a client has explicitly
specified that the job is to be held until explicitly specified that the job is to be held until explicitly
Job Monitoring MIB, V0.85 Aug 8, 1997
released. Until the job is explicitly released by a client, released. Until the job is explicitly released by a client,
the job SHALL be in the pendingHeld state with the the job SHALL be in the pendingHeld state with the
jobHoldSpecified value in the jmJobStateReasons1 attribute. jobHoldSpecified value in the jmJobStateReasons1 attribute.
jobHoldUntil(53), OCTET STRING(SIZE(0..63)) jobHoldUntil(53), JmJobStringTC(SIZE(0..63))
OCTETS: The named time period during which the job SHALL OCTETS: The named time period during which the job SHALL
become a candidate for processing, such as 'evening', become a candidate for processing, such as 'evening',
'night', 'weekend', 'second-shift', 'third-shift', etc., as 'night', 'weekend', 'second-shift', 'third-shift', etc., as
defined by the system administrator. See IPP [ipp-model] defined by the system administrator. See IPP [ipp-model]
for the standard keyword values. Until that time period for the standard keyword values. Until that time period
arrives, the job SHALL be in the pendingHeld state with the arrives, the job SHALL be in the pendingHeld state with the
jobHoldUntilSpecified value in the jmJobStateReasons1 jobHoldUntilSpecified value in the jmJobStateReasons1
object. The value 'no-hold' SHALL indicate explicitly that object. The value 'no-hold' SHALL indicate explicitly that
no time period has been specified. 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) outputBin(54), Integer32(0..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) JmJobStringTC(SIZE(0..63))
INTEGER: MULTI-ROW: The output subunit index in the INTEGER: MULTI-ROW: The output subunit index in the
Printer MIB[print-mib] Printer MIB[print-mib]
AND/OR AND/OR
OCTETS: the name or number (represented as ASCII digits) of OCTETS: the name or number (represented as ASCII digits) of
the output bin to which all or part of the job is placed in. the output bin to which all or part of the job is placed in.
sides(55), Integer32(-2..2) sides(55), Integer32(-2..2)
INTEGER: MULTI-ROW: The number of sides, '1' or '2', that INTEGER: MULTI-ROW: The number of sides, '1' or '2', that
any document in this job requires/used. any document in this job requires/used.
finishing(56), JmFinishingTC finishing(56), JmFinishingTC
INTEGER: MULTI-ROW: Type of finishing that any document in INTEGER: MULTI-ROW: Type of finishing that any document in
this job requires/used. this job requires/used.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Image Quality attributes (requested and consumed) + Image Quality attributes (requested and consumed)
Job Monitoring MIB, V0.84 July 21, 1997
+ +
+ For devices that can vary the image quality. + For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityRequested(70), JmPrintQualityTC printQualityRequested(70), JmPrintQualityTC
INTEGER: MULTI-ROW: The print quality selection requested INTEGER: MULTI-ROW: The print quality selection requested
for a document in the job for printers that allow quality for a document in the job for printers that allow quality
differentiation. differentiation.
Job Monitoring MIB, V0.85 Aug 8, 1997
printQualityUsed(71), JmPrintQualityTC printQualityUsed(71), JmPrintQualityTC
INTEGER: MULTI-ROW: The print quality selection actually INTEGER: MULTI-ROW: The print quality selection actually
used by a document in the job for printers that allow used by a document in the job for printers that allow
quality differentiation. quality differentiation.
printerResolutionRequested(72), JmPrinterResolutionTC printerResolutionRequested(72), JmPrinterResolutionTC
OCTETS: MULTI-ROW: The printer resolution requested for a OCTETS: MULTI-ROW: The printer resolution requested for a
document in the job for printers that support resolution document in the job for printers that support resolution
selection. selection.
printerResolutionUsed(73), JmPrinterResolutionTC printerResolutionUsed(73), JmPrinterResolutionTC
OCTETS: MULTI-ROW: The printer resolution actually used by OCTETS: MULTI-ROW: The printer resolution actually used by
a document in the job for printers that support resolution a document in the job for printers that support resolution
selection. selection.
tonerEcomonyRequested(74), JmTonerEconomyTC tonerEcomonyRequested(74), JmTonerEconomyTC
INTEGER: MULTI-ROW: The print quality selection requested INTEGER: MULTI-ROW: The toner economy selection requested
for documents in the job for printers that allow toner for documents in the job for printers that allow toner
quality differentiation. economy differentiation.
tonerEcomonyUsed(75), JmTonerEconomyTC tonerEcomonyUsed(75), JmTonerEconomyTC
INTEGER: MULTI-ROW: The print quality selection actually INTEGER: MULTI-ROW: The toner economy selection actually
used by documents in the job for printers that allow toner used by documents in the job for printers that allow toner
quality differentiation. economy differentiation.
tonerDensityRequested(76), Integer32(-2..100) tonerDensityRequested(76), Integer32(-2..100)
INTEGER: MULTI-ROW: The toner density requested for a INTEGER: MULTI-ROW: The toner density requested for a
document in this job for devices that can vary toner density document in this job for devices that can vary toner density
levels. Level 1 is the lowest density and level 100 is the levels. Level 1 is the lowest density and level 100 is the
highest density level. Devices with a smaller range, SHALL highest density level. Devices with a smaller range, SHALL
map the 1-100 range evenly onto the implemented range. map the 1-100 range evenly onto the implemented range.
tonerDensityUsed(77), Integer32(-2..100) tonerDensityUsed(77), Integer32(-2..100)
INTEGER: MULTI-ROW: The toner density used by documents in INTEGER: MULTI-ROW: The toner density used by documents in
this job for devices that can vary toner density levels. 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.
Job Monitoring MIB, V0.84 July 21, 1997
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Progress attributes (requested and consumed) + Job Progress attributes (requested and consumed)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative progress + applications to show an indication of relative progress
+ to users. + to users.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.85 Aug 8, 1997
jobCopiesRequested(90), Integer32(-2..2147483647) jobCopiesRequested(90), Integer32(-2..2147483647)
INTEGER: The number of copies of the entire job that are to INTEGER: The number of copies of the entire job that are to
be produced. be produced.
jobCopiesCompleted(91), Integer32(-2..2147483647) jobCopiesCompleted(91), Integer32(-2..2147483647)
INTEGER: The number of copies of the entire job that have INTEGER: The number of copies of the entire job that have
been completed so far. been completed so far.
documentCopiesRequested(92), Integer32(-2..2147483647) documentCopiesRequested(92), Integer32(-2..2147483647)
INTEGER: The total count of the number of document copies INTEGER: The total count of the number of document copies
requested. If there are documents A, B, and C, and document requested for the job as a whole. If there are documents A,
B is specified to produce 4 copies, the number of document B, and C, and document B is specified to produce 4 copies,
copies requested is 6 for the job. the number of document copies requested is 6 for the job.
This attribute SHALL be used only when a job has multiple This attribute SHALL be used only when a job has multiple
documents. The jobCopiesRequested attribute SHALL be used documents. The jobCopiesRequested attribute SHALL be used
when the job has only one document. when the job has only one document.
documentCopiesCompleted(93), Integer32(-2..2147483647) documentCopiesCompleted(93), Integer32(-2..2147483647)
INTEGER: The total count of the number of document copies INTEGER: The total count of the number of document copies
completed so far for the job as a whole. If there are completed so far for the job as a whole. If there are
documents A, B, and C, and document B is specified to documents A, B, and C, and document B is specified to
produce 4 copies, the number of document copies starts a 0 produce 4 copies, the number of document copies starts a 0
skipping to change at page 55, line 4 skipping to change at page 54, line 45
jobKOctetsTransferred(94), Integer32(-2..2147483647) jobKOctetsTransferred(94), Integer32(-2..2147483647)
INTEGER: The number of K (1024) octets transferred to the INTEGER: The number of K (1024) octets transferred to the
server or device to which the agent is providing access. server or device to which the agent is providing access.
This count is independent of the number of copies of the job This count is independent of the number of copies of the job
or documents that will be produced, but it is only a measure or documents that will be produced, but it is only a measure
of the number of bytes transferred to the server or device. of the number of bytes transferred to the server or device.
The agent SHALL round the actual number of octets The agent SHALL round the actual number of octets
transferred up to the next higher K. Thus 0 octets SHALL be transferred up to the next higher K. Thus 0 octets SHALL be
represented as '0', 1-1024 octets SHALL BE represented as represented as '0', 1-1024 octets SHALL BE represented as
Job Monitoring MIB, V0.84 July 21, 1997
'1', 1025-2048 SHALL be '2', etc. When the job completes, '1', 1025-2048 SHALL be '2', etc. When the job completes,
the values of the jmJobKOctetsRequested object and the the values of the jmJobKOctetsRequested object and the
jobKOctetsTransferred attribute SHALL be equal. jobKOctetsTransferred attribute SHALL be equal.
NOTE - The jobKOctetsTransferred can be used with the NOTE - The jobKOctetsTransferred can be used with the
jmJobKOctetsRequested object in order to produce a relative jmJobKOctetsRequested object in order to produce a relative
indication of the progress of the job for agents that do not indication of the progress of the job for agents that do not
implement the jmJobKOctetsProcessed object. implement the jmJobKOctetsProcessed object.
Job Monitoring MIB, V0.85 Aug 8, 1997
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Impression attributes + Impression attributes
+ +
+ For a print job, an impression is the marking of the + For a print job, an impression is the marking of the
+ entire side of a sheet. Two-sided processing involves two + entire side of a sheet. Two-sided processing involves two
+ impressions per sheet. Two-up is the placement of two + impressions per sheet. Two-up is the placement of two
+ logical pages on one side of a sheet and so is still a + logical pages on one side of a sheet and so is still a
+ single impression. See also jmJobImpressionsRequested and + single impression. See also jmJobImpressionsRequested and
+ jmJobImpressionsCompleted objects in the jmJobTable. + jmJobImpressionsCompleted objects in the jmJobTable.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
skipping to change at page 56, line 4 skipping to change at page 55, line 45
services, the number of impressions completed includes the services, the number of impressions completed includes the
number of impressions processed. number of impressions processed.
This value SHALL be reset to 0 for each document in the job This value SHALL be reset to 0 for each document in the job
and for each document copy. and for each document copy.
fullColorImpressionsCompleted(114), Integer32(-2..2147483647) fullColorImpressionsCompleted(114), Integer32(-2..2147483647)
INTEGER: The number of full color impressions completed by INTEGER: The number of full color impressions completed by
the device for this job so far. For printing, the the device for this job so far. For printing, the
impressions completed includes interpreting, marking, and impressions completed includes interpreting, marking, and
Job Monitoring MIB, V0.84 July 21, 1997
stacking the output. For other types of job services, the stacking the output. For other types of job services, the
number of impressions completed includes the number of number of impressions completed includes the number of
impressions processed. Full color impressions are typically impressions processed. Full color impressions are typically
defined as those requiring 3 or more colorants, but this MAY defined as those requiring 3 or more colorants, but this MAY
vary by implementation. vary by implementation.
highlightColorImpressionsCompleted(115), Integer32(-2.. highlightColorImpressionsCompleted(115), Integer32(-2..
2147483647) 2147483647)
INTEGER: The number of highlight color impressions INTEGER: The number of highlight color impressions
Job Monitoring MIB, V0.85 Aug 8, 1997
completed by the device for this job so far. For printing, completed by the device for this job so far. For printing,
the impressions completed includes interpreting, marking, the impressions completed includes interpreting, marking,
and stacking the output. For other types of job services, and stacking the output. For other types of job services,
the number of impressions completed includes the number of the number of impressions completed includes the number of
impressions processed. Highlight color impressions are impressions processed. Highlight color impressions are
typically defined as those requiring black plus one other typically defined as those requiring black plus one other
colorant, but this MAY vary by implementation. colorant, but this MAY vary by implementation.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Page attributes + Page attributes
skipping to change at page 56, line 41 skipping to change at page 56, line 31
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
pagesRequested(130), Integer32(-2..2147483647) pagesRequested(130), Integer32(-2..2147483647)
INTEGER: The number of logical pages requested by the job INTEGER: The number of logical pages requested by the job
to be processed. to be processed.
pagesCompleted(131), Integer32(-2..2147483647) pagesCompleted(131), Integer32(-2..2147483647)
INTEGER: The number of logical pages completed for this job INTEGER: The number of logical pages completed for this job
so far. so far.
For implementations where multiple copies are produced by
the interpreter with only a single pass over the data, the
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 - See the impressionsCompletedCurrentCopy and
pagesCompletedCurrentCopy attributes for attributes that are
reset on each document copy.
NOTE - The pagesCompleted object can be used with the
pagesRequested object to provide an indication of the
relative progress of the job, provided that the
multiplicative factor is taken into account for some
implementations of multiple copies.
pagesCompletedCurrentCopy(132), Integer32(-2..2147483647) pagesCompletedCurrentCopy(132), Integer32(-2..2147483647)
INTEGER: The number of logical pages completed for the INTEGER: The number of logical pages completed for the
current copy of the document so far. This value SHALL be current copy of the document so far. This value SHALL be
Job Monitoring MIB, V0.85 Aug 8, 1997
reset to 0 for each document in the job and for each reset to 0 for each document in the job and for each
document copy. document copy.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Sheet attributes + Sheet attributes
+ +
+ The sheet is a single piece of a medium, whether printing + The sheet is a single piece of a medium, whether printing
+ on one or both sides. + on one or both sides.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.84 July 21, 1997
sheetsRequested(150), Integer32(-2..2147483647) sheetsRequested(150), Integer32(-2..2147483647)
INTEGER: The number of medium sheets requested to be INTEGER: The number of medium sheets requested to be
processed for this job. processed for this job.
sheetsCompleted(151), Integer32(-2..2147483647) sheetsCompleted(151), 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 entire job so far whether those marking and stacking for the entire job so far whether those
sheets have been processed on one side or on both. sheets have been processed on one side or on both.
sheetsCompletedCurrentCopy(152), Integer32(-2..2147483647) sheetsCompletedCurrentCopy(152), Integer32(-2..2147483647)
skipping to change at page 57, line 36 skipping to change at page 57, line 45
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) + Resources attributes (requested and consumed)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to + applications to show an indication of relative usage to
+ users. + users.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mediumRequested(170), JmMediumTypeTC mediumRequested(170), JmMediumTypeTC
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) JmJobStringTC(SIZE(0..63))
INTEGER: MULTI-ROW: The type INTEGER: MULTI-ROW: The type
AND/OR AND/OR
OCTETS: the name of the medium that is required by the job. OCTETS: the name of the medium that is required by the job.
mediumConsumed(171), Integer32(-2..2147483647) mediumConsumed(171), Integer32(-2..2147483647)
AND AND
OCTET STRING(SIZE(0..63)) Job Monitoring MIB, V0.85 Aug 8, 1997
JmJobStringTC(SIZE(0..63))
INTEGER: The number of sheets INTEGER: The number of sheets
AND AND
OCTETS: MULTI-ROW: the name of the medium that have 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
values. (represented as JmJobStringTC) values.
Job Monitoring MIB, V0.84 July 21, 1997
colorantRequested(172), Integer32(-2..2147483647) colorantRequested(172), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(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: the name of the colorant requested. OCTETS: the name of the colorant requested.
colorantConsumed(173), Integer32(-2..2147483647) colorantConsumed(173), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(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: the name of the colorant consumed. OCTETS: the name of the colorant consumed.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Time attributes (set by server or device) + Time attributes (set by server or device)
+ +
+ This section of attributes are ones that are set by the + This section of attributes are ones that are set by the
+ server or device that accepts jobs. Two forms of time are + server or device that accepts jobs. Two forms of time are
skipping to change at page 58, line 43 skipping to change at page 59, line 4
+ '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.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.85 Aug 8, 1997
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 the OCTETS: the date and time that the job was submitted to the
server (as distinguished from the device which uses server (as distinguished from the device which uses
jobSubmissionTime). jobSubmissionTime).
Job Monitoring MIB, V0.84 July 21, 1997
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 the OCTETS: the date and time that the job was submitted to the
server or device to which the agent is providing access. server or device to which the agent is providing access.
jobStartedBeingHeldTime(192), JmTimeStampTC jobStartedBeingHeldTime(192), JmTimeStampTC
AND/OR AND/OR
skipping to change at page 59, line 44 skipping to change at page 60, line 4
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 has INTEGER: The amount of CPU time in seconds that the job has
been in the processing state. If the job enters the been in the processing state. If the job enters the
Job Monitoring MIB, V0.85 Aug 8, 1997
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."
REFERENCE REFERENCE
"See Section 3.2 entitled 'The Attribute Mechanism' for a "See Section 3.2 entitled 'The Attribute Mechanism' for a
description of this textual-convention and its use in the description of this textual-convention and its use in the
jmAttributeTable. jmAttributeTable.
Job Monitoring MIB, V0.84 July 21, 1997
This is a type 2 enumeration. See Section 3.6.1.2." This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
jobStateReasons2(3), jobStateReasons2(3),
jobStateReasons3(4), jobStateReasons3(4),
jobStateReasons4(5), jobStateReasons4(5),
processingMessage(6), processingMessage(6),
jobCodedCharSet(7),
jobAccountName(21), jobAccountName(21),
serverAssignedJobName(22), serverAssignedJobName(22),
jobName(23), jobName(23),
jobServiceTypes(24), jobServiceTypes(24),
jobSourceChannelIndex(25), jobSourceChannelIndex(25),
jobSourcePlatformType(26), jobSourcePlatformType(26),
submittingServerName(27), submittingServerName(27),
submittingApplicationName(28), submittingApplicationName(28),
jobOriginatingHost(29), jobOriginatingHost(29),
skipping to change at page 60, line 44 skipping to change at page 61, line 4
jobPriority(50), jobPriority(50),
jobProcessAfterDateAndTime(51), jobProcessAfterDateAndTime(51),
jobHold(52), jobHold(52),
jobHoldUntil(53), jobHoldUntil(53),
outputBin(54), outputBin(54),
sides(55), sides(55),
finishing(56), finishing(56),
printQualityRequested(70), printQualityRequested(70),
Job Monitoring MIB, V0.85 Aug 8, 1997
printQualityUsed(71), printQualityUsed(71),
printerResolutionRequested(72), printerResolutionRequested(72),
printerResolutionUsed(73), printerResolutionUsed(73),
tonerEcomonyRequested(74), tonerEcomonyRequested(74),
tonerEcomonyUsed(75), tonerEcomonyUsed(75),
tonerDensityRequested(76), tonerDensityRequested(76),
tonerDensityUsed(77), tonerDensityUsed(77),
jobCopiesRequested(90), jobCopiesRequested(90),
jobCopiesCompleted(91), jobCopiesCompleted(91),
Job Monitoring MIB, V0.84 July 21, 1997
documentCopiesRequested(92), documentCopiesRequested(92),
documentCopiesCompleted(93), documentCopiesCompleted(93),
jobKOctetsTransferred(94), jobKOctetsTransferred(94),
impressionsSpooled(110), impressionsSpooled(110),
impressionsSentToDevice(111), impressionsSentToDevice(111),
impressionsInterpreted(112), impressionsInterpreted(112),
impressionsCompletedCurrentCopy(113), impressionsCompletedCurrentCopy(113),
fullColorImpressionsCompleted(114), fullColorImpressionsCompleted(114),
highlightColorImpressionsCompleted(115), highlightColorImpressionsCompleted(115),
skipping to change at page 61, line 41 skipping to change at page 62, line 4
jobSubmissionToServerTime(190), jobSubmissionToServerTime(190),
jobSubmissionTime(191), jobSubmissionTime(191),
jobStartedBeingHeldTime(192), jobStartedBeingHeldTime(192),
jobStartedProcessingTime(193), jobStartedProcessingTime(193),
jobCompletedTime(194), jobCompletedTime(194),
jobProcessingCPUTime(195) jobProcessingCPUTime(195)
} }
JmJobServiceTypesTC ::= TEXTUAL-CONVENTION JmJobServiceTypesTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Job Monitoring MIB, V0.85 Aug 8, 1997
DESCRIPTION DESCRIPTION
"Specifies the type(s) of service to which the job has been "Specifies the type(s) of service to which the job has been
submitted (print, fax, scan, etc.). The service type is submitted (print, fax, scan, etc.). The service type is
represented as an enum that is bit encoded with each job service represented as an enum that is bit encoded with each job service
type so that more general and arbitrary services can be created, type so that more general and arbitrary services can be created,
such as services with more than one destination type, or ones such as services with more than one destination type, or ones
with only a source or only a destination. For example, a job with only a source or only a destination. For example, a job
service might scan, faxOut, and print a single job. In this service might scan, faxOut, and print a single job. In this
case, three bits would be set in the jobServiceTypes attribute, case, three bits would be set in the jobServiceTypes attribute,
Job Monitoring MIB, V0.84 July 21, 1997
corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4,
respectively, yielding: 0x2C. respectively, yielding: 0x2C.
Whether this attribute is set from a job attribute supplied by Whether this attribute is set from a job attribute supplied by
the job submission client or is set by the recipient job the job submission client or is set by the recipient job
submission server or device depends on the job submission submission server or device depends on the job submission
protocol. With either implementation, the agent SHALL return a protocol. With either implementation, the agent SHALL return a
non-zero value for this attribute indicating the type of the non-zero value for this attribute indicating the type of the
job. job.
skipping to change at page 62, line 46 skipping to change at page 63, line 4
The job contains some instructions that specify printing The job contains some instructions that specify printing
scan 0x8 scan 0x8
The job contains some instructions that specify scanning The job contains some instructions that specify scanning
faxIn 0x10 faxIn 0x10
The job contains some instructions that specify receive fax The job contains some instructions that specify receive fax
faxOut 0x20 faxOut 0x20
The job contains some instructions that specify sending fax The job contains some instructions that specify sending fax
Job Monitoring MIB, V0.85 Aug 8, 1997
getFile 0x40 getFile 0x40
The job contains some instructions that specify accessing The job contains some instructions that specify accessing
files or documents files or documents
putFile 0x80 putFile 0x80
The job contains some instructions that specify storing The job contains some instructions that specify storing
files or documents files or documents
Job Monitoring MIB, V0.84 July 21, 1997
mailList 0x100 mailList 0x100
The job contains some instructions that specify distribution The job contains some instructions that specify distribution
of documents using an electronic mail system." of documents using an electronic mail system."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them MAY be used together. See except that combinations of them MAY be used together. See
section 3.6.1.2." section 3.6.1.2."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons1TC ::= TEXTUAL-CONVENTION JmJobStateReasons1TC ::= TEXTUAL-CONVENTION
skipping to change at page 63, line 39 skipping to change at page 64, line 4
JmJobStateReasonsNTC enums can be defined and registered without JmJobStateReasonsNTC enums can be defined and registered without
impacting such deployed clients. In other words, the impacting such deployed clients. In other words, the
jmJobStateReasons1 object and jobStateReasonsN attributes are jmJobStateReasons1 object and jobStateReasonsN attributes are
intended to be extensible. 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[ipp-model] for the IPP 'job-state-reasons' attribute, values[ipp-model] for the IPP 'job-state-reasons' attribute,
since the Job Monitoring MIB is intended to cover other job since the Job Monitoring MIB is intended to cover other job
submission protocols as well. Also some of the names of the submission protocols as well. Also some of the names of the
reasons have been changed from 'printer' to 'device', since the reasons have been changed from 'printer' to 'device', since the
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB is intended to cover additional types of Job Monitoring MIB is intended to cover additional types of
devices, including input devices, such as scanners. devices, including input devices, such as scanners.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values MAY be used at the same powers of two, since multiple values MAY be used at the same
time. For ease of understanding, the JmJobStateReasons1TC time. For ease of understanding, the JmJobStateReasons1TC
reasons are presented in the order in which the reasons are reasons are presented in the order in which the reasons are
likely to occur (if implemented), starting with the likely to occur (if implemented), starting with the
'jobIncoming' value and ending with the 'jobCompletedWithErrors'
Job Monitoring MIB, V0.84 July 21, 1997 value.
'jobIncoming' value and ending with 'jobCompletedWithErrors'
reasons.
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
skipping to change at page 64, line 47 skipping to change at page 65, line 5
NOT be a candidate for processing until this reason is NOT be a candidate for processing until this reason is
removed and there are no other reasons to hold the job. removed and there are no other reasons to hold the job.
jobProcessAfterSpecified 0x40 jobProcessAfterSpecified 0x40
The value of the job's jobProcessAfterDateAndTime(51) The value of the job's jobProcessAfterDateAndTime(51)
attribute specifies a time that is still in the future. The attribute specifies a time that is still in the future. The
job SHALL NOT be a candidate for processing until this job SHALL NOT be a candidate for processing until this
reason is removed and there are no other reasons to hold the reason is removed and there are no other reasons to hold the
job. job.
Job Monitoring MIB, V0.85 Aug 8, 1997
resourcesAreNotReady 0x80 resourcesAreNotReady 0x80
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, fonts, resource objects, etc., is not ready on any of media, fonts, resource objects, etc., is not ready on any of
the physical devices for which the job is a candidate. This the physical devices for which the job is a candidate. 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 on implementation. depending on implementation.
Job Monitoring MIB, V0.84 July 21, 1997
deviceStoppedPartly 0x100 deviceStoppedPartly 0x100
One or more, but not all, of the devices to which the job is One or more, but not all, of the devices to which the job is
assigned are stopped. If all of the devices are stopped (or assigned are stopped. If all of the devices are stopped (or
the only device is stopped), the deviceStopped reason SHALL the only device is stopped), the deviceStopped reason SHALL
be used. be used.
deviceStopped 0x200 deviceStopped 0x200
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.
skipping to change at page 65, line 46 skipping to change at page 66, line 5
abortedBySystem 0x2000 abortedBySystem 0x2000
The job was aborted by the system. The job was aborted by the system.
NOTE - When the system puts a job into the 'aborted' job NOTE - When the system puts a job into the 'aborted' job
state, this reason is not needed. This reason is needed state, this reason is not needed. This reason is needed
only when the system aborts a job, but, instead of placing only when the system aborts a job, but, instead of placing
the job in the aborted job state, places the job in the the job in the aborted job state, places the job in the
pendingHeld state, so that a user or operator can manually pendingHeld state, so that a user or operator can manually
try the job again. try the job again.
jobCompletedSuccessfully 0x4000 Job Monitoring MIB, V0.85 Aug 8, 1997
processingToStopPoint 0x4000
The requester has issued an operation to cancel or interrupt
the job or the server/device has aborted the job but the
server/device is still performing some actions on the job
until a specified stop point occurs or job
termination/cleanup is completed.
This reason is recommended to be used in conjunction with
the canceled or aborted job state to indicate that the
server/device is still performing some actions on the job
after the job leaves the processing state, so that some of
the jobs resources consumed counters may still be
incrementing while the job is in the canceled or aborted job
states.
jobCompletedSuccessfully 0x8000
The job completed successfully. The job completed successfully.
jobCompletedWithWarnings 0x8000 jobCompletedWithWarnings 0x10000
The job completed with warnings. The job completed with warnings.
jobCompletedWithErrors 0x10000 jobCompletedWithErrors 0x20000
The job completed with errors (and possibly warnings too). The job completed with errors (and possibly warnings too).
Job Monitoring MIB, V0.84 July 21, 1997 The following additional job state reasons have been added to
represent job states that are in ISO DPA[iso-dpa] and other job
The following additional job state reasons have been added submission protocols:
to represent job states that are in ISO DPA[iso-dpa] and
other job submission protocols:
jobPaused 0x20000 jobPaused 0x40000
The job has been indefinitely suspended by a client issuing The job has been indefinitely suspended by a client issuing
an operation to suspend the job so that other jobs may an operation to suspend the job so that other jobs may
proceed using the same devices. The client MAY issue an proceed using the same devices. The client MAY issue an
operation to resume the paused job at any time, in which operation to resume the paused job at any time, in which
case the agent SHALL remove the jobPaused values from the case the agent SHALL remove the jobPaused values from the
job's jmJobStateReasons1 object and the job is eventually job's jmJobStateReasons1 object and the job is eventually
resumed at or near the point where the job was paused. resumed at or near the point where the job was paused.
jobInterrupted 0x40000 jobInterrupted 0x80000
The job has been interrupted while processing by a client The job has been interrupted while processing by a client
issuing an operation that specifies another job to be run issuing an operation that specifies another job to be run
instead of the current job. The server or device will instead of the current job. The server or device will
automatically resume the interrupted job when the automatically resume the interrupted job when the
interrupting job completes. interrupting job completes.
jobRetained 0x80000 jobRetained 0x100000
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 the job's document data (and submitted resources, such as of the job's document data (and submitted resources, such as
Job Monitoring MIB, V0.85 Aug 8, 1997
fonts, logos, and forms, if any). Thus a client could issue fonts, logos, and forms, if any). Thus a client could issue
an operation to the server or device to either (1) re-do the an operation to the server or device to either (1) re-do the
job (or a copy of the job) on the same server or device or job (or a copy of the job) on the same server or device or
(2) resubmit the job to another server or device. When a (2) resubmit the job to another server or device. When a
client could no longer re-do/resubmit the job, such as after client could no longer re-do/resubmit the job, such as after
the document data has been discarded, the agent SHALL remove the document data has been discarded, the agent SHALL remove
the jobRetained value from the jmJobStateReasons1 object." the jobRetained value from the jmJobStateReasons1 object."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of bits may be used together. See except that combinations of bits may be used together. See
skipping to change at page 67, line 4 skipping to change at page 67, line 27
standardization and/or registration." standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons2TC ::= TEXTUAL-CONVENTION JmJobStateReasons2TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons2 "This textual-convention is used with the jobStateReasons2
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState object. See the description under jmJobState object. See the description under
Job Monitoring MIB, V0.84 July 21, 1997
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
cascaded 0x1 cascaded 0x1
An outbound gateway has transmitted all of the job's job and An outbound gateway has transmitted all of the job's job and
document attributes and data to another spooling system. document attributes and data to another spooling system.
skipping to change at page 67, line 30 skipping to change at page 68, line 4
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 by the job's job-discard-time attribute has specified 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 attributes for the job; therefore the job has accounting attributes for the job; therefore the job has
been placed into the completed state with the jobRetained been placed into the completed state with the jobRetained
Job Monitoring MIB, V0.85 Aug 8, 1997
jmJobStateReasons1 object value for a system-defined period jmJobStateReasons1 object value for a system-defined period
of time, so the administrator can examine it, resubmit it, of time, so the administrator can examine it, resubmit it,
etc. etc.
submissionInterrupted 0x10 submissionInterrupted 0x10
Indicates that the job was not completely submitted for some Indicates that the job was not completely submitted for some
unforeseen reason, such as: (1) the server has crashed unforeseen reason, such as: (1) the server has crashed
before the job was closed by the client, (2) the server or before the job was closed by the client, (2) the server or
the document transfer method has crashed in some non- the document transfer method has crashed in some non-
recoverable way before the document data was entirely recoverable way before the document data was entirely
skipping to change at page 68, line 4 skipping to change at page 68, line 31
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 the human intervention did not occur within the site- but the human intervention did not occur within the site-
settable time-out value. settable 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
Job Monitoring MIB, V0.84 July 21, 1997
using need a specially trained operator (who may need a key using need a specially trained operator (who may need a key
to unlock the device and gain access) in order for the job to unlock the device and gain access) in order for the job
to make progress, but the key operator intervention did not to make progress, but the key operator intervention did not
occur within the site-settable time-out value. occur within 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 cartridge or special non-standard media, but the job special cartridge or special non-standard media, but the job
was not resumed within the site-settable time-out value and was not resumed within the site-settable time-out value and
skipping to change at page 68, line 30 skipping to change at page 69, line 4
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 to await human action, such as removing a special processing to await human action, such as removing a special
cartridge or restoring standard media, but the job was not cartridge or restoring standard media, but the job was not
resumed within the site-settable time-out value and the resumed within the site-settable time-out value and the
server/device has transitioned the job to the completed server/device has 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
Job Monitoring MIB, V0.85 Aug 8, 1997
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 specified by the device's site-settable attribute. period specified by the device's site-settable attribute.
connectingToDeviceTimeOut 0x1000 connectingToDeviceTimeOut 0x1000
The server is attempting to connect to one or more devices The server is attempting to connect to one or more devices
skipping to change at page 69, line 5 skipping to change at page 69, line 32
The job is being transferred to a down stream server or The job is being transferred to a down stream server or
device. device.
queuedInDevice 0x4000 queuedInDevice 0x4000
The job has been queued in a down stream server or device. The job has been queued in a down stream server or device.
jobCleanup 0x8000 jobCleanup 0x8000
The server/device is performing cleanup activity as part of The server/device is performing cleanup activity as part of
ending normal processing. ending normal processing.
Job Monitoring MIB, V0.84 July 21, 1997
processingToStopPoint 0x10000
The requester has issued an operation to interrupt the job
and the server/device is processing up until the specified
stop point occurs.
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, but instead of assigning resources and starting the process, but instead of assigning resources and starting the
job processing, the server/device has transitioned the job job processing, the server/device has transitioned the job
to the pendingHeld state to await entry of a password (and to the pendingHeld state to await entry of a password (and
dispatched another job, if there is one). dispatched 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.
skipping to change at page 69, line 33 skipping to change at page 70, line 5
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 and document copy attributes that were originally job and document copy attributes that were originally
submitted. submitted.
Job Monitoring MIB, V0.85 Aug 8, 1997
heldForDiagnostics 0x200000 heldForDiagnostics 0x200000
The system is running intrusive diagnostics, so that all The system is running intrusive diagnostics, so that all
jobs are being held. jobs are being held.
serviceOffLine 0x400000 serviceOffLine 0x400000
The service/document transform is off-line and accepting no The service/document transform is off-line and accepting no
jobs. All pending jobs are put into the pendingHeld state. jobs. All pending jobs are put into the pendingHeld state.
This could be true if its input is impaired or broken. This could be true if its input is impaired or broken.
noSpaceOnServer 0x800000 noSpaceOnServer 0x800000
skipping to change at page 70, line 4 skipping to change at page 70, line 28
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. This condition SHOULD be detected before the job is limit. This condition SHOULD be detected before the job is
scheduled so that the user does not wait until his/her job scheduled so that the user does not wait until his/her job
Job Monitoring MIB, V0.84 July 21, 1997
is scheduled only to find that the account is overdrawn. is scheduled only to find that the account is overdrawn.
This condition MAY also occur while the job is processing This condition MAY also occur while the job is processing
either as processing begins or part way through processing. either as processing begins or part way through processing.
heldForRetry 0x4000000 heldForRetry 0x4000000
The job encountered some errors that the server/device could The job encountered some errors that the server/device could
not recover from with its normal retry procedures, but the not recover from with its normal retry procedures, but the
error might not be encountered if the job is processed again error might not be encountered if the job is processed again
in the future. Example cases are phone number busy or in the future. Example cases are phone number busy or
remote file system in-accessible. For such a situation, the remote file system in-accessible. For such a situation, the
skipping to change at page 70, line 33 skipping to change at page 71, line 4
The job was canceled because the server or device was The job was canceled because the server or device was
shutdown before completing the job. shutdown 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 to handle this particular job; the spooler SHOULD try unable to handle this particular job; the spooler SHOULD try
Job Monitoring MIB, V0.85 Aug 8, 1997
another device or the user should submit the job to another another device or the user should submit the job to another
device. 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 problem, such as an ill-formed PDL; the spooler SHOULD major problem, such as an ill-formed PDL; the spooler SHOULD
not even try another device. " not even try another device. "
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them may be used together. See except that combinations of them may be used together. See
section 3.6.1.2. See the description under JmJobStateReasons1TC section 3.6.1.2. See the description under JmJobStateReasons1TC
and the jobStateReasons2 attribute." and the jobStateReasons2 attribute."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons3TC ::= TEXTUAL-CONVENTION JmJobStateReasons3TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons3 "This textual-convention is used with the jobStateReasons3
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState object. See the description under jmJobState object. See the description under
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
skipping to change at page 71, line 30 skipping to change at page 72, line 4
has failed while the job was processing. The server or has failed while the job was processing. The server or
device is keeping the job in the pendingHeld state until an device is keeping the job in the pendingHeld state until an
operator can determine what to do with the job." operator can determine what to do with the job."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them may be used together. See except that combinations of them may be used together. See
section 3.6.1.2. The remaining bits are reserved for future section 3.6.1.2. The remaining bits are reserved for future
standardization and/or registration. See the description under standardization and/or registration. See the description under
JmJobStateReasons1TC and the jobStateReasons3 attribute." JmJobStateReasons1TC and the jobStateReasons3 attribute."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.85 Aug 8, 1997
JmJobStateReasons4TC ::= TEXTUAL-CONVENTION JmJobStateReasons4TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used in the jobStateReasons4 "This textual-convention is used in the jobStateReasons4
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState object. See the description under jmJobState object. See the description under
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
skipping to change at page 72, line 5 skipping to change at page 72, line 27
time: time:
none yet defined. These bits are reserved for future none yet defined. These bits are reserved for future
standardization and/or registration." standardization and/or registration."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them may be used together. See except that combinations of them may be used together. See
section 3.6.1.2. See the description under JmJobStateReasons1TC section 3.6.1.2. See the description under JmJobStateReasons1TC
and the jobStateReasons4 attribute." and the jobStateReasons4 attribute."
Job Monitoring MIB, V0.84 July 21, 1997
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 } jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 }
- -- The General Group (MANDATORY) -- The General Group (MANDATORY)
- -- The jmGeneralGroup consists entirely of the jmGeneralTable. -- The jmGeneralGroup consists entirely of the jmGeneralTable.
jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 } jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 }
jmGeneralTable OBJECT-TYPE jmGeneralTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmGeneralEntry SYNTAX SEQUENCE OF JmGeneralEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmGeneralTable consists of information of a general nature "The jmGeneralTable consists of information of a general nature
that are per-job-set, but are not per-job. See Section 2 that are per-job-set, but are not per-job. See Section 2
skipping to change at page 73, line 47 skipping to change at page 73, line 46
INDEX { jmGeneralJobSetIndex } INDEX { jmGeneralJobSetIndex }
::= { jmGeneralTable 1 } ::= { jmGeneralTable 1 }
JmGeneralEntry ::= SEQUENCE { JmGeneralEntry ::= SEQUENCE {
jmGeneralJobSetIndex Integer32(1..32767), jmGeneralJobSetIndex Integer32(1..32767),
jmGeneralNumberOfActiveJobs Integer32(0..2147483647), jmGeneralNumberOfActiveJobs Integer32(0..2147483647),
jmGeneralOldestActiveJobIndex Integer32(0..2147483647), jmGeneralOldestActiveJobIndex Integer32(0..2147483647),
jmGeneralNewestActiveJobIndex Integer32(0..2147483647), jmGeneralNewestActiveJobIndex Integer32(0..2147483647),
jmGeneralJobPersistence Integer32(15..2147483647), jmGeneralJobPersistence Integer32(15..2147483647),
jmGeneralAttributePersistence Integer32(15..2147483647), jmGeneralAttributePersistence Integer32(15..2147483647),
jmGeneralJobSetName OCTET STRING(SIZE(0..63)) jmGeneralJobSetName JmUTF8StringTC(SIZE(0..63))
} }
jmGeneralJobSetIndex OBJECT-TYPE jmGeneralJobSetIndex OBJECT-TYPE
SYNTAX Integer32(1..32767) SYNTAX Integer32(1..32767)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"A unique value for each job set in this MIB. The jmJobTable "A unique value for each job set in this MIB. The jmJobTable
and jmAttributeTable tables have this same index as their and jmAttributeTable tables have this same index as their
primary index. primary index.
The value(s) of the jmGeneralJobSetIndex SHALL be persistent The value(s) of the jmGeneralJobSetIndex SHALL be persistent
across power cycles, so that clients that have retained across power cycles, so that clients that have retained
jmGeneralJobSetIndex values will access the same job sets upon jmGeneralJobSetIndex values will access the same job sets upon
subsequent power-up. subsequent power-up.
skipping to change at page 75, line 4 skipping to change at page 75, line 4
'active' states (pending, processing, or processingStopped). In 'active' states (pending, processing, or processingStopped). In
other words, the index of the 'active' job that has been in the other words, the index of the 'active' job that has been in the
job tables the longest. job tables the longest.
If there are no active jobs, the agent SHALL set the value of If there are no active jobs, the agent SHALL set the value of
this object to 0." this object to 0."
REFERENCE REFERENCE
"See Section 3.2 entitled 'The Job Tables and the Oldest Active "See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes' for a description of the usage of and Newest Active Indexes' for a description of the usage of
this object." this object."
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
::= { jmGeneralEntry 3 } ::= { jmGeneralEntry 3 }
jmGeneralNewestActiveJobIndex OBJECT-TYPE jmGeneralNewestActiveJobIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIndex of the newest job that is in one of the 'active' "The jmJobIndex of the newest job that is in one of the 'active'
states (pending, processing, or processingStopped). In other states (pending, processing, or processingStopped). In other
skipping to change at page 76, line 4 skipping to change at page 76, line 4
jmGeneralAttributePersistence. This value SHOULD be at least 60 jmGeneralAttributePersistence. This value SHOULD be at least 60
which gives a monitoring application one minute in which to poll which gives a monitoring application one minute in which to poll
for job data." for job data."
DEFVAL { 60 } -- one minute DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 5 } ::= { jmGeneralEntry 5 }
jmGeneralAttributePersistence OBJECT-TYPE jmGeneralAttributePersistence OBJECT-TYPE
SYNTAX Integer32(15..2147483647) SYNTAX Integer32(15..2147483647)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum time in seconds for this instance of the Job Set "The minimum time in seconds for this instance of the Job Set
that an entry SHALL remain in the jmAttributeTable after that an entry SHALL remain in the jmAttributeTable after
processing has completed , i.e., the time in seconds starting processing has completed , i.e., the time in seconds starting
when the job enters the completed, canceled, or aborted state. when the job enters the completed, canceled, or aborted state.
Depending on implementation, the value of this object MAY be Depending on implementation, the value of this object MAY be
either (1) set by the system administrator by means outside this either (1) set by the system administrator by means outside this
specification or MAY be (2) fixed by the implementation. specification or MAY be (2) fixed by the implementation.
This value SHOULD be at least 60 which gives a monitoring This value SHOULD be at least 60 which gives a monitoring
application one minute in which to poll for job data." application one minute in which to poll for job data."
DEFVAL { 60 } -- one minute DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 6 } ::= { jmGeneralEntry 6 }
jmGeneralJobSetName OBJECT-TYPE jmGeneralJobSetName OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..63)) SYNTAX JmUTF8StringTC(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The human readable name of this job set assigned by the system "The human readable name of this job set assigned by the system
administrator (by means outside of this MIB). Typically, this administrator (by means outside of this MIB). Typically, this
name SHOULD be the name of the job queue. If a server or device name SHOULD be the name of the job queue. If a server or device
has only a single job set, this object can be the has only a single job set, this object can be the
administratively assigned name of the server or device itself. administratively assigned name of the server or device itself.
This name does not need to be unique, though each job set in a This name does not need to be unique, though each job set in a
single Job Monitoring MIB SHOULD have distinct names. single Job Monitoring MIB SHOULD have distinct names.
NOTE - The purpose of this object is to help the user of the job NOTE - The purpose of this object is to help the user of the job
monitoring application distinguish between several job sets in monitoring application distinguish between several job sets in
implementations that support more than one job set." implementations that support more than one job set."
REFERENCE REFERENCE
"See the OBJECT compliance macro for the minimum maximum length "See the OBJECT compliance macro for the minimum maximum length
required for conformance." required for conformance."
::= { jmGeneralEntry 7 } ::= { jmGeneralEntry 7 }
- -- The Job ID Group (MANDATORY) -- The Job ID Group (MANDATORY)
- -- The jmJobIDGroup consists entirely of the jmJobIDTable. -- The jmJobIDGroup consists entirely of the jmJobIDTable.
jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 } jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 }
jmJobIDTable OBJECT-TYPE jmJobIDTable OBJECT-TYPE
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
SYNTAX SEQUENCE OF JmJobIDEntry SYNTAX SEQUENCE OF JmJobIDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIDTable provides a correspondence map (1) between the "The jmJobIDTable provides a correspondence map (1) between the
job submission ID that a client uses to refer to a job and (2) job submission ID that a client uses to refer to a job and (2)
the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring
MIB agent assigned to the job and that are used to access the MIB agent assigned to the job and that are used to access the
job in all of the other tables in the MIB. If a monitoring job in all of the other tables in the MIB. If a monitoring
skipping to change at page 77, line 51 skipping to change at page 77, line 50
jmJobIDJobIndex Integer32(1..2147483647) jmJobIDJobIndex Integer32(1..2147483647)
} }
jmJobSubmissionID OBJECT-TYPE jmJobSubmissionID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(48)) SYNTAX OCTET STRING(SIZE(48))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A quasi-unique 48-octet fixed-length string ID which identifies "A quasi-unique 48-octet fixed-length string ID which identifies
the job within a particular client-server environment. There the job within a particular client-server environment. There
are multiple formats for the jmJobSubmissionID. See the are multiple formats for the jmJobSubmissionID. Each format
JmJobSubmissionIDTypeTC textual convention. Each format SHALL SHALL be uniquely identified. See the JmJobSubmissionIDTypeTC
be registered using the procedures of a type 2 enum. See textual convention. Each format SHALL be registered using the
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
section 3.6.3 entitled: 'IANA Registration of Job Submission Id procedures of a type 2 enum. See section 3.6.3 entitled: 'IANA
Formats'. Registration of Job Submission Id Formats'.
If the requester (client or server) does not supply a job If the requester (client or server) does not supply a job
submission ID in the job submission protocol, then the recipient submission ID in the job submission protocol, then the recipient
(server or device) SHALL assign a job submission ID using any of (server or device) SHALL assign a job submission ID using any of
the standard formats and adding the final 8 octets to the standard formats that have been reserved to agents and
distinguish the ID from others submitted from the same adding the final 8 octets to distinguish the ID from others
requester. submitted from the same requester.
The monitoring application, whether in the client or running The monitoring application, whether in the client or running
separately, MAY use the job submission ID to help identify which separately, MAY use the job submission ID to help identify which
jmJobIndex was assigned by the agent, i.e., in which row the job jmJobIndex was assigned by the agent, i.e., in which row the job
information is in the other tables. information is in the other tables.
NOTE - fixed-length is used so that a management application can NOTE - fixed-length is used so that a management application can
use a shortened GetNext varbind (in SNMPv1 and SNMPv2) in order use a shortened GetNext varbind (in SNMPv1 and SNMPv2) in order
to get the next submission ID, disregarding the remainder of the to get the next submission ID, disregarding the remainder of the
ID in order to access jobs independent of the trailing ID in order to access jobs independent of the trailing
identifier part, e.g., to get all jobs submitted by a particular identifier part, e.g., to get all jobs submitted by a particular
jmJobOwner or from a particular MAC address." jmJobOwner or submitted from a particular MAC address."
REFERENCE
"See the JmJobSubmissionIDTypeTC textual convention.
See APPENDIX B - Support of the Job Submission ID in Job
Submission Protocols."
::= { jmJobIDEntry 1 } ::= { jmJobIDEntry 1 }
jmJobIDJobSetIndex OBJECT-TYPE jmJobIDJobSetIndex OBJECT-TYPE
SYNTAX Integer32(1..32767) SYNTAX Integer32(1..32767)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the jmGeneralJobSetIndex for "This object contains the value of the jmGeneralJobSetIndex for
the job with the jmJobSubmissionID value, i.e., the job set the job with the jmJobSubmissionID value, i.e., the job set
index of the job set in which the job was placed when that index of the job set in which the job was placed when that
skipping to change at page 78, line 51 skipping to change at page 79, line 4
job-specific objects for this job." job-specific objects for this job."
REFERENCE REFERENCE
"See jmGeneralJobSetIndex in the jmGeneralTable." "See jmGeneralJobSetIndex in the jmGeneralTable."
::= { jmJobIDEntry 2 } ::= { jmJobIDEntry 2 }
jmJobIDJobIndex OBJECT-TYPE jmJobIDJobIndex OBJECT-TYPE
SYNTAX Integer32(1..2147483647) SYNTAX Integer32(1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.85 Aug 8, 1997
"This object contains the value of the jmJobIndex for the job "This object contains the value of the jmJobIndex for the job
with the jmJobSubmissionID value, i.e., the job index for the with the jmJobSubmissionID value, i.e., the job index for the
job when the server or device accepted the job. This value, in job when the server or device accepted the job. This value, in
combination with the jmJobIDJobSetIndex value, permits the combination with the jmJobIDJobSetIndex value, permits the
Job Monitoring MIB, V0.84 July 21, 1997
management application to access the other tables to obtain the management application to access the other tables to obtain the
job-specific objects for this job." job-specific objects for this job."
REFERENCE REFERENCE
"See jmJobIndex in the jmJobTable." "See jmJobIndex in the jmJobTable."
::= { jmJobIDEntry 3 } ::= { jmJobIDEntry 3 }
- -- The Job Group (MANDATORY) -- The Job Group (MANDATORY)
- -- The jmJobGroup consists entirely of the jmJobTable. -- The jmJobGroup consists entirely of the jmJobTable.
jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 } jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 }
jmJobTable OBJECT-TYPE jmJobTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmJobEntry SYNTAX SEQUENCE OF JmJobEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobTable consists of basic job state and status "The jmJobTable consists of basic job state and status
information for each job in a job set that (1) monitoring information for each job in a job set that (1) monitoring
skipping to change at page 79, line 48 skipping to change at page 80, line 4
DESCRIPTION DESCRIPTION
"Basic per-job state and status information. "Basic per-job state and status information.
An entry SHALL exist in this table for each job, no matter what An entry SHALL exist in this table for each job, no matter what
the state of the job is. Each job SHALL appear in one and only the state of the job is. Each job SHALL appear in one and only
one job set." one job set."
REFERENCE REFERENCE
"See Section 3.2 entitled 'The Job Tables'." "See Section 3.2 entitled 'The Job Tables'."
INDEX { jmGeneralJobSetIndex, jmJobIndex } INDEX { jmGeneralJobSetIndex, jmJobIndex }
::= { jmJobTable 1 } ::= { jmJobTable 1 }
Job Monitoring MIB, V0.85 Aug 8, 1997
JmJobEntry ::= SEQUENCE { JmJobEntry ::= SEQUENCE {
jmJobIndex Integer32(1..2147483647), jmJobIndex Integer32(1..2147483647),
jmJobState JmJobStateTC, jmJobState JmJobStateTC,
Job Monitoring MIB, V0.84 July 21, 1997
jmJobStateReasons1 JmJobStateReasons1TC, jmJobStateReasons1 JmJobStateReasons1TC,
jmNumberOfInterveningJobs Integer32(-2..2147483647), jmNumberOfInterveningJobs Integer32(-2..2147483647),
jmJobKOctetsRequested Integer32(-2..2147483647), jmJobKOctetsRequested Integer32(-2..2147483647),
jmJobKOctetsProcessed Integer32(-2..2147483647), jmJobKOctetsProcessed Integer32(-2..2147483647),
jmJobImpressionsRequested Integer32(-2..2147483647), jmJobImpressionsRequested Integer32(-2..2147483647),
jmJobImpressionsCompleted Integer32(-2..2147483647), jmJobImpressionsCompleted Integer32(-2..2147483647),
jmJobOwner OCTET STRING(SIZE(0..63)) jmJobOwner JmJobStringTC(SIZE(0..63))
} }
jmJobIndex OBJECT-TYPE jmJobIndex OBJECT-TYPE
SYNTAX Integer32(1..2147483647) SYNTAX Integer32(1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequential, monatonically increasing identifier index for "The sequential, monatonically increasing identifier index for
the job generated by the server or device when that server or the job generated by the server or device when that server or
device accepted the job. This index value permits the device accepted the job. This index value permits the
management application to access the other tables to obtain the management application to access the other tables to obtain the
job-specific row entries. job-specific row entries."
Agents providing access to systems that contain jobs with a job
identifier of 0 SHALL map the job identifier value 0 to a
jmJobIndex value that is one higher than the highest job
identifier value that any job can have on that system."
REFERENCE REFERENCE
"See Section 3.2 entitled 'The Job Tables'. "See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes'.
See Section 3.4 entitled 'Job Identification'.
See also jmGeneralNewestActiveJobIndex for the largest value of See also jmGeneralNewestActiveJobIndex for the largest value of
jmJobIndex. jmJobIndex.
See JmJobSubmissionTypeTC for a limit on the size of this index See JmJobSubmissionTypeTC for a limit on the size of this index
if the agent represents it as an 8-digit decimal number." if the agent represents it as an 8-digit decimal number."
::= { jmJobEntry 1 } ::= { jmJobEntry 1 }
jmJobState OBJECT-TYPE jmJobState OBJECT-TYPE
SYNTAX JmJobStateTC SYNTAX JmJobStateTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 81, line 4 skipping to change at page 81, line 4
"The current state of the job (pending, processing, completed, "The current state of the job (pending, processing, completed,
etc.). Agents SHALL implement only those states which are etc.). Agents SHALL implement only those states which are
appropriate for the particular implementation. However, appropriate for the particular implementation. However,
management applications SHALL be prepared to receive all the management applications SHALL be prepared to receive all the
standard job states. standard job states.
The final value for this object SHALL be one of: completed, The final value for this object SHALL be one of: completed,
canceled, or aborted. The minimum length of time that the agent canceled, or aborted. The minimum length of time that the agent
SHALL maintain MIB data for a job in the completed, canceled, or SHALL maintain MIB data for a job in the completed, canceled, or
aborted state before removing the job data from the jmJobIDTable aborted state before removing the job data from the jmJobIDTable
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
and jmJobTable is specified by the value of the and jmJobTable is specified by the value of the
jmGeneralJobPersistence object." jmGeneralJobPersistence object."
::= { jmJobEntry 2 } ::= { jmJobEntry 2 }
jmJobStateReasons1 OBJECT-TYPE jmJobStateReasons1 OBJECT-TYPE
SYNTAX JmJobStateReasons1TC SYNTAX JmJobStateReasons1TC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 81, line 40 skipping to change at page 81, line 39
REFERENCE REFERENCE
"The jobStateReasonsN (N=2..4) attributes provide further "The jobStateReasonsN (N=2..4) attributes provide further
additional information about the job's current state." additional information about the job's current state."
::= { jmJobEntry 3 } ::= { jmJobEntry 3 }
jmNumberOfInterveningJobs OBJECT-TYPE jmNumberOfInterveningJobs OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of jobs that are expected to be processed before "The number of jobs that are expected to complete being
this job is processed according to the implementation's queuing processed before this job has completed being processed
algorithm if no other jobs were to be submitted. In other according to the implementation's queuing algorithm if no other
words, this value is the job's queue position. The agent SHALL jobs were to be submitted. In other words, this value is the
return a value of 0 for this attribute while the job is job's queue position. The agent SHALL return a value of 0 for
processing." this attribute when the job is the next job to complete
processing (or has completed processing)."
::= { jmJobEntry 4 } ::= { jmJobEntry 4 }
jmJobKOctetsRequested OBJECT-TYPE jmJobKOctetsRequested OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.85 Aug 8, 1997
"The total size in K (1024) octets of the document(s) being "The total size in K (1024) octets of the document(s) being
requested to be processed in the job. The agent SHALL round the requested to be processed in the job. The agent SHALL round the
Job Monitoring MIB, V0.84 July 21, 1997
actual number of octets up to the next highest K. Thus 0 octets actual number of octets up to the next highest K. Thus 0 octets
SHALL be represented as '0', 1-1024 octets SHALL be represented SHALL be represented as '0', 1-1024 octets SHALL be represented
as '1', 1025-2048 SHALL be represented as '2', etc. as '1', 1025-2048 SHALL be represented as '2', etc.
In computing this value, the server/device SHALL not include the In computing this value, the server/device SHALL not include the
multiplicative factors contributed by (1) the number of document multiplicative factors contributed by (1) the number of document
copies, and (2) the number of job copies, independent of whether copies, and (2) the number of job copies, independent of whether
the device can process multiple copies of the job or document the device can process multiple copies of the job or document
without making multiple passes over the job or document data and without making multiple passes over the job or document data and
independent of whether the output is collated or not. Thus the independent of whether the output is collated or not. Thus the
skipping to change at page 82, line 52 skipping to change at page 83, line 4
NOTE - See the impressionsCompletedCurrentCopy and NOTE - See the impressionsCompletedCurrentCopy and
pagesCompletedCurrentCopy attributes for attributes that are pagesCompletedCurrentCopy attributes for attributes that are
reset on each document copy. reset on each document copy.
NOTE - The jmJobKOctetsProcessed object can be used with the NOTE - The jmJobKOctetsProcessed object can be used with the
jmJobKOctetsRequested object to provide an indication of the jmJobKOctetsRequested object to provide an indication of the
relative progress of the job, provided that the multiplicative relative progress of the job, provided that the multiplicative
factor is taken into account for some implementations of factor is taken into account for some implementations of
multiple copies." multiple copies."
::= { jmJobEntry 6 } ::= { jmJobEntry 6 }
Job Monitoring MIB, V0.85 Aug 8, 1997
jmJobImpressionsRequested OBJECT-TYPE jmJobImpressionsRequested OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
Job Monitoring MIB, V0.84 July 21, 1997
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of impressions requested by this job to produce." "The total size in number of impressions of the document(s)
being requested by this job to produce.
In computing this value, the server/device SHALL not include the
multiplicative factors contributed by (1) the number of document
copies, and (2) the number of job copies, independent of whether
the device can process multiple copies of the job or document
without making multiple passes over the job or document data and
independent of whether the output is collated or not. Thus the
server/device computation is independent of the implementation."
::= { jmJobEntry 7 } ::= { jmJobEntry 7 }
jmJobImpressionsCompleted OBJECT-TYPE jmJobImpressionsCompleted OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of impressions completed for this job so "The current number of impressions completed for this job so
far. For printing devices, the impressions completed includes far. For printing devices, the impressions completed includes
interpreting, marking, and stacking the output. For other types interpreting, marking, and stacking the output. For other types
of job services, the number of impressions completed includes of job services, the number of impressions completed includes
the number of impressions processed." the number of impressions processed.
For implementations where multiple copies are produced by the
interpreter with only a single pass over the data, the final
value SHALL be equal to the value of the
jmJobImpressionsRequested 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 jmJobImpressionsRequested object.
NOTE - See the impressionsCompletedCurrentCopy and
pagesCompletedCurrentCopy attributes for attributes that are
reset on each document copy.
NOTE - The jmJobImpressionsCompleted object can be used with the
jmJobImpressionsRequested object to provide an indication of the
relative progress of the job, provided that the multiplicative
factor is taken into account for some implementations of
multiple copies."
::= { jmJobEntry 8 } ::= { jmJobEntry 8 }
jmJobOwner OBJECT-TYPE jmJobOwner OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..63)) Job Monitoring MIB, V0.85 Aug 8, 1997
SYNTAX JmJobStringTC(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The coded character set name of the user that submitted the "The coded character set name of the user that submitted the
job. The method of assigning this user name will be system job. The method of assigning this user name will be system
and/or site specific but the method MUST insure that the name is and/or site specific but the method MUST insure that the name is
unique to the network that is visible to the client and target unique to the network that is visible to the client and target
device. device.
This value SHOULD be the authenticated name of the user This value SHOULD be the authenticated name of the user
submitting the job." submitting the job."
REFERENCE REFERENCE
"See the OBJECT compliance macro for the minimum maximum length "See the OBJECT compliance macro for the minimum maximum length
required for conformance." required for conformance."
::= { jmJobEntry 9 } ::= { jmJobEntry 9 }
- -- The Attribute Group (MANDATORY) -- The Attribute Group (MANDATORY)
- -- The jmAttributeGroup consists entirely of the jmAttributeTable.
- --
- -- Implementation of the two objects in this group is MANDATORY.
- -- See Section 3.1 entitled 'Conformance Considerations'.
- -- An agent SHALL implement any attribute if (1) the server or device
- -- supports the functionality represented by the attribute and (2) the
- -- information is available to the agent.
- The Attribute Group (MANDATORY) -- The jmAttributeGroup consists entirely of the jmAttributeTable.
Job Monitoring MIB, V0.84 July 21, 1997 --
-- Implementation of the two objects in this group is MANDATORY.
-- See Section 3.1 entitled 'Conformance Considerations'.
-- An agent SHALL implement any attribute if (1) the server or device
-- supports the functionality represented by the attribute and (2) the
-- information is available to the agent.
jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 } jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 }
jmAttributeTable OBJECT-TYPE jmAttributeTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmAttributeEntry SYNTAX SEQUENCE OF JmAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmAttributeTable SHALL contain attributes of the job and "The jmAttributeTable SHALL contain attributes of the job and
document(s) for each job in a job set. Instead of allocating document(s) for each job in a job set. Instead of allocating
distinct objects for each attribute, each attribute is distinct objects for each attribute, each attribute is
represented as a separate row in the jmAttributeTable." represented as a separate row in the jmAttributeTable."
REFERENCE REFERENCE
"The MANDATORY-GROUP macro specifies that this group is "The MANDATORY-GROUP macro specifies that this group is
MANDATORY. An agent SHALL implement any attribute if (1) the MANDATORY. An agent SHALL implement any attribute if (1) the
server or device supports the functionality represented by the server or device supports the functionality represented by the
attribute and (2) the information is available to the agent. " attribute and (2) the information is available to the agent. "
::= { jmAttribute 1 } ::= { jmAttribute 1 }
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeEntry OBJECT-TYPE jmAttributeEntry OBJECT-TYPE
SYNTAX JmAttributeEntry SYNTAX JmAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes representing information about the job and "Attributes representing information about the job and
document(s) or resources required and/or consumed. document(s) or resources required and/or consumed.
Each entry in the jmAttributeTable is a per-job entry with an Each entry in the jmAttributeTable is a per-job entry with an
skipping to change at page 85, line 4 skipping to change at page 85, line 34
convention. convention.
The agent SHALL create rows in the jmAttributeTable as the The agent SHALL create rows in the jmAttributeTable as the
server or device is able to discover the attributes either from server or device is able to discover the attributes either from
the job submission protocol itself or from the document PDL. As the job submission protocol itself or from the document PDL. As
the documents are interpreted, the interpreter MAY discover the documents are interpreted, the interpreter MAY discover
additional attributes and so the agent adds additional rows to additional attributes and so the agent adds additional rows to
this table. As the attributes that represent resources are this table. As the attributes that represent resources are
actually consumed, the usage counter contained in the actually consumed, the usage counter contained in the
jmAttributeValueAsInteger object is incremented according to the jmAttributeValueAsInteger object is incremented according to the
Job Monitoring MIB, V0.84 July 21, 1997
units indicated in the description of the JmAttributeTypeTC units indicated in the description of the JmAttributeTypeTC
enum. enum.
The agent SHALL maintain each row in the jmJobTable for at least The agent SHALL maintain each row in the jmJobTable for at least
the minimum time after a job completes as specified by the the minimum time after a job completes as specified by the
jmGeneralAttributePersistence object. jmGeneralAttributePersistence object.
Zero or more entries SHALL exist in this table for each job in a Zero or more entries SHALL exist in this table for each job in a
job set." job set."
REFERENCE REFERENCE
"See Section 3.3 entitled 'The Attribute Mechanism' for a "See Section 3.3 entitled 'The Attribute Mechanism' for a
description of the jmAttributeTable." description of the jmAttributeTable."
INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex, INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex,
jmAttributeInstanceIndex } jmAttributeInstanceIndex }
::= { jmAttributeTable 1 } ::= { jmAttributeTable 1 }
JmAttributeEntry ::= SEQUENCE { JmAttributeEntry ::= SEQUENCE {
jmAttributeTypeIndex JmAttributeTypeTC, jmAttributeTypeIndex JmAttributeTypeTC,
jmAttributeInstanceIndex Integer32(1..32767), jmAttributeInstanceIndex Integer32(1..32767),
jmAttributeValueAsInteger Integer32(-2..2147483647), jmAttributeValueAsInteger Integer32(-2..2147483647),
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeValueAsOctets OCTET STRING(SIZE(0..63)) jmAttributeValueAsOctets OCTET STRING(SIZE(0..63))
} }
jmAttributeTypeIndex OBJECT-TYPE jmAttributeTypeIndex OBJECT-TYPE
SYNTAX JmAttributeTypeTC SYNTAX JmAttributeTypeTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of attribute that this row entry represents. "The type of attribute that this row entry represents.
The type MAY identify information about the job or document(s) The type MAY identify information about the job or document(s)
or MAY identify a resource required to process the job before or MAY identify a resource required to process the job before
the job start processing and/or consumed by the job as the job the job start processing and/or consumed by the job as the job
is processed. is processed.
Examples of job and document attributes include: Examples of job attributes (i.e., apply to the job as a whole)
jobCopiesRequested, documentCopiesRequested, jobCopiesCompleted, that have only one instance per job include:
documentCopiesCompleted, fileName, and documentName. jobCopiesRequested(90), documentCopiesRequested(92),
jobCopiesCompleted(91), documentCopiesCompleted(93), while
examples of job attributes that may have more than one instance
per job include: documentFormatIndex(37), and
documentFormat(38).
Examples of document attributes (one instance per document)
include: fileName(34), and documentName(35).
Examples of required and consumed resource attributes include: Examples of required and consumed resource attributes include:
pagesRequested, pagesCompleted, mediumRequested, and pagesRequested(130), mediumRequested(170), pagesCompleted(131),
mediumConsumed, respectively." and mediumConsumed(171), respectively."
::= { jmAttributeEntry 1 } ::= { jmAttributeEntry 1 }
jmAttributeInstanceIndex OBJECT-TYPE jmAttributeInstanceIndex OBJECT-TYPE
SYNTAX Integer32(1..32767) SYNTAX Integer32(1..32767)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"A running 16-bit index of the attributes of the same type for "A running 16-bit index of the attributes of the same type for
each job. For those attributes with only a single instance per each job. For those attributes with only a single instance per
job, this index value SHALL be 1. For those attributes that are job, this index value SHALL be 1. For those attributes that are
a single value per document, the index value SHALL be the a single value per document, the index value SHALL be the
document number, starting with 1 for the first document in the document number, starting with 1 for the first document in the
job. Jobs with only a single document SHALL use the index value job. Jobs with only a single document SHALL use the index value
of 1. For those attributes that can have multiple values per of 1. For those attributes that can have multiple values per
job or per document, such as documentFormatIndex(37) or job or per document, such as documentFormatIndex(37) or
documentFormat(38), the index SHALL be a running index for the documentFormat(38), the index SHALL be a running index for the
job as a whole, starting at 1." job as a whole, starting at 1."
::= { jmAttributeEntry 2 } ::= { jmAttributeEntry 2 }
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeValueAsInteger OBJECT-TYPE jmAttributeValueAsInteger OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The integer value of the attribute. The value of the attribute "The integer value of the attribute. The value of the attribute
SHALL be represented as an integer if the enum description in SHALL be represented as an integer if the enum description in
the JmAttributeTypeTC textual-convention definition has the tag: the JmAttributeTypeTC textual-convention definition has the tag:
'INTEGER:'. 'INTEGER:'.
skipping to change at page 86, line 53 skipping to change at page 87, line 39
accounting system. accounting system.
Since the agent MAY add attributes representing resources to Since the agent MAY add attributes representing resources to
this table while the job is waiting to be processed or being this table while the job is waiting to be processed or being
processed, which can be a long time before any of the resources processed, which can be a long time before any of the resources
are actually used, the agent SHALL set the value of the are actually used, the agent SHALL set the value of the
jmAttributeValueAsInteger object to 0 for resources that the job jmAttributeValueAsInteger object to 0 for resources that the job
has not yet consumed. has not yet consumed.
Attributes for which the concept of an integer value is Attributes for which the concept of an integer value is
meaningless, such as fileName, interpreter, and physicalDevice, meaningless, such as fileName(34), jobName, and
do not have the 'INTEGER:' tag in the JmAttributeTypeTC processingMessage, do not have the 'INTEGER:' tag in the
JmAttributeTypeTC definition and so an agent SHALL always return
Job Monitoring MIB, V0.84 July 21, 1997 a value of '-1' to indicate 'other' for the value of the
jmAttributeValueAsInteger object for these attributes.
definition and so an agent SHALL always return a value of '-1'
to indicate 'other' for jmAttributeValueAsInteger.
For attributes which do have the 'INTEGER:' tag in the For attributes which do have the 'INTEGER:' tag in the
JmAttributeTypeTC definition, if the integer value is not (yet) JmAttributeTypeTC definition, if the integer value is not (yet)
known, the agent either SHALL not materialize the row in the known, the agent either (1) SHALL not materialize the row in the
jmAttributeTable until the value is known or SHALL return a '-2' jmAttributeTable until the value is known or (2) SHALL return a
to represent an 'unknown' counting integer value, a '0' to '-2' to represent an 'unknown' counting integer value, a '0' to
represent an 'unknown' index value, and a '2' to represent an represent an 'unknown' index value, and a '2' to represent an
'unknown(2)' enum value." 'unknown(2)' enum value."
::= { jmAttributeEntry 3 } ::= { jmAttributeEntry 3 }
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeValueAsOctets OBJECT-TYPE jmAttributeValueAsOctets OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(0..63)) SYNTAX OCTET STRING(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The octet string value of the attribute. The value of the "The octet string value of the attribute. The value of the
attribute SHALL be represented as an OCTET STRING if the enum attribute SHALL be represented as an OCTET STRING if the enum
description in the JmAttributeTypeTC textual-convention description in the JmAttributeTypeTC textual-convention
definition has the tag: 'OCTETS:'. definition has the tag: 'OCTETS:'.
Depending on the enum definition, this object value MAY be a Depending on the enum definition, this object value MAY be a
coded character set string (text) or a binary octet string, such coded character set string (text), such as 'JmUTF8StringTC', or
as DateAndTime. a binary octet string, such as 'DateAndTime'.
Attributes for which the concept of an octet string value is Attributes for which the concept of an octet string value is
meaningless, such as pagesCompleted, do not have the tag meaningless, such as pagesCompleted, do not have the tag
'OCTETS:' in the JmAttributeTypeTC definition and so the agent 'OCTETS:' in the JmAttributeTypeTC definition and so the agent
SHALL always return a zero length string for the value of the SHALL always return a zero length string for the value of the
jmAttributeValueAsOctets object. jmAttributeValueAsOctets object.
For attributes which do have the 'OCTETS:' tag in the For attributes which do have the 'OCTETS:' tag in the
JmAttributeTypeTC definition, if the OCTET STRING value is not JmAttributeTypeTC definition, if the OCTET STRING value is not
(yet) known, the agent either SHALL not materialize the row in (yet) known, the agent either SHALL not materialize the row in
the jmAttributeTable until the value is known or SHALL return a the jmAttributeTable until the value is known or SHALL return a
zero-length string." zero-length string."
::= { jmAttributeEntry 4 } ::= { jmAttributeEntry 4 }
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997 -- Notifications and Trapping
-- Reserved for the future
- -- Notifications and Trapping
- -- Reserved for the future
- Reserved for the future
jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2} jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2}
- -- Conformance Information -- Conformance Information
jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 } jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 }
- -- compliance statements -- compliance statements
jmMIBCompliance MODULE-COMPLIANCE jmMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for agents that implement the "The compliance statement for agents that implement the
job monitoring MIB." job monitoring MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup } jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup }
OBJECT jmGeneralJobSetName OBJECT jmGeneralJobSetName
SYNTAX OCTET STRING (SIZE(0..8)) SYNTAX JmUTF8StringTC (SIZE(0..8))
DESCRIPTION DESCRIPTION
"Only 8 octets maximum string length NEED be supported by the "Only 8 octets maximum string length NEED be supported by the
agent." agent."
OBJECT jmJobOwner OBJECT jmJobOwner
SYNTAX OCTET STRING (SIZE(0..16)) SYNTAX JmJobStringTC (SIZE(0..16))
DESCRIPTION DESCRIPTION
"Only 16 octets maximum string length NEED be supported by the "Only 16 octets maximum string length NEED be supported by the
agent." agent."
- -- There are no CONDITIONALLY MANDATORY or OPTIONAL groups. -- There are no CONDITIONALLY MANDATORY or OPTIONAL groups.
::= { jmMIBConformance 1 } ::= { jmMIBConformance 1 }
jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 } jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 }
jmGeneralGroup OBJECT-GROUP jmGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex, jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex,
jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence, jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence,
jmGeneralAttributePersistence, jmGeneralJobSetName} jmGeneralAttributePersistence, jmGeneralJobSetName}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The general group." "The general group."
::= { jmMIBGroups 1 } ::= { jmMIBGroups 1 }
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
jmJobIDGroup OBJECT-GROUP jmJobIDGroup OBJECT-GROUP
OBJECTS { OBJECTS {
jmJobIDJobSetIndex, jmJobIDJobIndex } jmJobIDJobSetIndex, jmJobIDJobIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job ID group." "The job ID group."
::= { jmMIBGroups 2 } ::= { jmMIBGroups 2 }
jmJobGroup OBJECT-GROUP jmJobGroup OBJECT-GROUP
skipping to change at page 90, line 4 skipping to change at page 91, line 4
jmAttributeGroup OBJECT-GROUP jmAttributeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
jmAttributeValueAsInteger, jmAttributeValueAsOctets } jmAttributeValueAsInteger, jmAttributeValueAsOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The attribute group." "The attribute group."
::= { jmMIBGroups 4 } ::= { jmMIBGroups 4 }
END END
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997
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 affect The job object has well-defined states and client operations that affect
the transition between the job states. Internal server and device the transition between the job states. Internal server and device
actions also affect the transitions of the job between the job states. actions also affect the transitions of the job between the job states.
These states and transitions are referred to as the job's life cycle. These states and transitions are referred to as the job's 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 is states of the job model specified here. The job model specified here is
skipping to change at page 91, line 5 skipping to change at page 92, line 5
settable or implementation-defined period of time. An accounting settable or implementation-defined period of time. An accounting
application MAY copy accounting information incrementally to an application MAY copy accounting information incrementally to an
accounting log as a job processes, or MAY be copied while the job is in accounting log as a job processes, or MAY be copied while the job is in
the canceled, aborted, or completed states, depending on implementation. the canceled, aborted, or completed states, depending on implementation.
The same is true for auditing logs. The same is true for auditing logs.
The jmJobState object specifies the standard job states. The normal job The jmJobState object specifies the standard job states. The normal job
state transitions are shown in the state transition diagram presented in state transitions are shown in the state transition diagram presented in
Table 1. Table 1.
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
6. APPENDIX B - Support of the Job Submission ID in Job Submission 6. APPENDIX B - Support of the Job Submission ID in Job Submission
Protocols Protocols
This appendix lists the job submission protocols that support the This appendix lists the job submission protocols that support the
concept of a job submission ID and indicates the attribute used in that concept of a job submission ID and indicates the attribute used in that
job submission protocol. job submission protocol.
6.1 Hewlett-Packard's Printer Job Language (PJL) 6.1 Hewlett-Packard's Printer Job Language (PJL)
skipping to change at page 91, line 37 skipping to change at page 92, line 37
The entire PJL JOB command with the optional parameter would be of the The entire PJL JOB command with the optional parameter would be of the
form: form:
@PJL JOB SUBMISSIONID = "id string" @PJL JOB SUBMISSIONID = "id string"
See "Printer Job Language Technical Reference Manual", part number 5021- See "Printer Job Language Technical Reference Manual", part number 5021-
0328, from Hewlett-Packard for complete information on the PJL JOB 0328, from Hewlett-Packard for complete information on the PJL JOB
command and the Printer Job Language. command and the Printer Job Language.
NOTE - Some PJL implementations wrap a banner page as a PJL job around a
job submitted by a client. In this case, there will be two job
submission ids. The outer one being the one with the banner page and
the inner one being the original user's job. The agent SHALL use the
last received job submission ID for the jmJobSubmissionID index, so that
the original user's job submission ID will be used, not the banner page
job ID.
6.2 ISO DPA 6.2 ISO DPA
The ISO 10175 Document Printing Application (DPA) protocol specifies the The ISO 10175 Document Printing Application (DPA) protocol specifies the
"job-client-id" attribute that allows the client to supply a text string "job-client-id" attribute that allows the client to supply a text string
ID for each job. ID for each job.
Job Monitoring MIB, V0.85 Aug 8, 1997
7. References 7. References
[char-set policy] Harald Avelstrand, "IETF Policy on Character Sets and
Language", June 1997. Latest draft: <draft-avelstrand-charset-policy-
00.txt>
[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, [hr-mib] P. Grillo, S. Waldbusser, "Host Resources MIB", RFC 1514,
September 1993 September 1993
[iana] J. Reynolds, and J. Postel, "Assigned Numbers", STD 2, RFC 1700, [iana] J. Reynolds, and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
ISI, October 1994. ISI, October 1994.
Job Monitoring MIB, V0.84 July 21, 1997 [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 [iana-media-types] IANA Registration of MIME media types (MIME content
types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/ types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/
[ISO 646] ISO/IEC 646:1991, "Information technology -- ISO 7-bit coded
character set for information interchange", JTC1/SC2.
[ISO 8859] ISO/IEC 8859-1:1987, "Information technology -- 8-bit single
byte coded graphic character sets - Part 1: Latin alphabet No. 1,
JTC1/SC2."
[ISO 2022] ISO/IEC 2022:1994 - "Information technology -- Character code
structure and extension techniques", 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 Document Printing Application (DPA). See [iso-dpa] ISO/IEC 10175 Document Printing Application (DPA). See
ftp://ftp.pwg.org/pub/pwg/dpa/ ftp://ftp.pwg.org/pub/pwg/dpa/
[ipp-model] Internet Printing Protocol (IPP), work in progress on the [ipp-model] Internet Printing Protocol (IPP), work in progress on the
IETF standards track. See draft-ietf-ipp-model-01.txt. See also IETF standards track. See draft-ietf-ipp-model-01.txt. See also
http://www.pwg.org/ipp/index.html http://www.pwg.org/ipp/index.html
[JIS X0208] JIS X0208-1990, "Japanese two byte coded character set."
[mib-II] MIB-II, RFC 1213. [mib-II] MIB-II, RFC 1213.
Job Monitoring MIB, V0.85 Aug 8, 1997
[print-mib] The Printer MIB - RFC 1759, proposed IETF standard. Also an [print-mib] The Printer MIB - RFC 1759, proposed IETF standard. Also an
Internet-Draft on the standards track as a draft standard: draft-ietf- Internet-Draft on the standards track as a draft standard: draft-ietf-
printmib-mib-info-02.txt printmib-mib-info-02.txt
[req-words] S. Bradner, "Keywords for use in RFCs to Indicate [req-words] S. Bradner, "Keywords for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[rfc 2130] C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R. [rfc 2130] C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R.
Atkinson, M. Crispin, and P. Svanberg, "The Report of the IAB Character Atkinson, M. Crispin, and P. Svanberg, "The Report of the IAB Character
Set Workshop held 29 Feb-1 March, 1997", April 1997, RFC 2130. Set Workshop held 29 Feb-1 March, 1997", April 1997, RFC 2130.
[SMIv2-TC] J. Case, et al. ``extual Conventions for Version 2 of the [SMIv2-TC] J. Case, et al. ``extual Conventions for Version 2 of the
Simple Network Managment Protocol (SNMPv2)'' RFC 1903, January 1996. Simple Network Management Protocol (SNMPv2)', RFC 1903, January 1996.
[tipsi] IEEE 1284.1, Transport-independent Printer System Interface [tipsi] IEEE 1284.1, Transport-independent Printer System Interface
(TIPSI). (TIPSI).
[URI-spec] Berners-Lee, T., Masinter, L., McCahill, M. , "Uniform [URI-spec] Berners-Lee, T., Masinter, L., McCahill, M. , "Uniform
Resource Locators (URL)", RFC 1738, December, 1994. Resource Locators (URL)", RFC 1738, December, 1994.
[US-ASCII] Coded Character Set - 7-bit American Standard Code for
Information Interchange, ANSI X3.4-1986.
[UTF-8] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO
10646", RFC 2044, October 1996.
8. Author's Addresses 8. Author's Addresses
Ron Bergman Ron Bergman
Dataproducts Corp. Dataproducts Corp.
1757 Tapo Canyon Road 1757 Tapo Canyon Road
Simi Valley, CA 93063-3394 Simi Valley, CA 93063-3394
Phone: 805-578-4421 Phone: 805-578-4421
Fax: 805-578-4001 Fax: 805-578-4001
Email: rbergman@dpc.com Email: rbergman@dpc.com
Tom Hastings Tom Hastings
Xerox Corporation, ESAE-231 Xerox Corporation, ESAE-231
701 S. Aviation Blvd. 701 S. Aviation Blvd.
El Segundo, CA 90245 El Segundo, CA 90245
Job Monitoring MIB, V0.84 July 21, 1997
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
EMail: hastings@cp10.es.xerox.com EMail: hastings@cp10.es.xerox.com
Scott A. Isaacson Scott A. Isaacson
Job Monitoring MIB, V0.85 Aug 8, 1997
Novell, Inc. Novell, Inc.
122 E 1700 S 122 E 1700 S
Provo, UT 84606 Provo, UT 84606
Phone: 801-861-7366 Phone: 801-861-7366
Fax: 801-861-4025 Fax: 801-861-4025
EMail: scott_isaacson@novell.com EMail: scott_isaacson@novell.com
Harry Lewis Harry Lewis
IBM Corporation IBM Corporation
skipping to change at page 94, line 4 skipping to change at page 95, line 44
Keith Carter, IBM Corporation Keith Carter, IBM Corporation
Jeff Copeland - QMS Jeff Copeland - QMS
Andy Davidson - Tektronix Andy Davidson - Tektronix
Roger deBry - IBM Roger deBry - IBM
Mabry Dozier - QMS Mabry Dozier - QMS
Lee Ferrel - Canon Lee Ferrel - Canon
Steve Gebert - IBM Steve Gebert - IBM
Robert Herriot - Sun Microsystems Inc. Robert Herriot - Sun Microsystems Inc.
Shige Kanemitsu - Kyocera Shige Kanemitsu - Kyocera
David Kellerman - Northlake Software David Kellerman - Northlake Software
Job Monitoring MIB, V0.84 July 21, 1997
Rick Landau - Digital Rick Landau - Digital
Harry Lewis - IBM Harry Lewis - IBM
Pete Loya - HP Pete Loya - HP
Ray Lutz - Cognisys Ray Lutz - Cognisys
Jay Martin - Underscore Jay Martin - Underscore
Mike MacKay, Novell, Inc. Mike MacKay, Novell, Inc.
Job Monitoring MIB, V0.85 Aug 8, 1997
Stan McConnell - Xerox Stan McConnell - Xerox
Carl-Uno Manros, Xerox, Corp. Carl-Uno Manros, Xerox, Corp.
Pat Nogay - IBM Pat Nogay - IBM
Bob Pentecost - HP Bob Pentecost - HP
Rob Rhoads - Intel Rob Rhoads - Intel
David Roach - Unisys David Roach - Unisys
Hiroyuki Sato - Canon Hiroyuki Sato - Canon
Bob Setterbo - Adobe Bob Setterbo - Adobe
Gail Songer, EFI Gail Songer, EFI
Mike Timperman - Lexmark Mike Timperman - Lexmark
Randy Turner - Sharp Randy Turner - Sharp
William Wagner - Digital Products William Wagner - Digital Products
Jim Walker - Dazel Jim Walker - Dazel
Chris Wellens - Interworking Labs Chris Wellens - Interworking Labs
Rob Whittle - Novell Rob Whittle - Novell
Don Wright - Lexmark Don Wright - Lexmark
Lloyd Young - Lexmark Lloyd Young - Lexmark
Atsushi Yuki - Kyocera Atsushi Yuki - Kyocera
Peter Zehler, Xerox, Corp. Peter Zehler, Xerox, Corp.
Job Monitoring MIB, V0.84 July 21, 1997 Job Monitoring MIB, V0.85 Aug 8, 1997
9. INDEX 9. INDEX
This index includes the textual conventions, the objects, and the This index includes the textual conventions, the objects, and the
attributes. Textual conventions all start with the prefix: "JM" and attributes. Textual conventions all start with the prefix: "JM" and
end with the suffix: "TC". Objects all starts with the prefix: "jm" end with the suffix: "TC". Objects all starts with the prefix: "jm"
followed by the group name. Attributes are identified with enums, and followed by the group name. Attributes are identified with enums, and
so start with any lower case letter and have no special prefix. so start with any lower case letter and have no special prefix.
------ ------
colorantConsumed, 58 colorantConsumed, 53
colorantRequested, 58 colorantRequested, 53
--D--- --D---
deviceNameRequested, 49 deviceNameRequested, 44
documentCopiesCompleted, 54 documentCopiesCompleted, 49
documentCopiesRequested, 54 documentCopiesRequested, 49
documentFormat, 51 documentFormat, 46
documentFormatIndex, 50 documentFormatIndex, 46
documentName, 50 documentName, 45
------ ------
fileName, 50 fileName, 45
finishing, 52 finishing, 48
fullColorImpressionsCompleted, 55 fullColorImpressionsCompleted, 51
--H--- --H---
highlightColorImpressionsCompleted, 56 highlightColorImpressionsCompleted, 51
------ ------
impressionsCompletedCurrentCopy, 55 impressionsCompletedCurrentCopy, 50
impressionsInterpreted, 55 impressionsInterpreted, 50
impressionsSentToDevice, 55 impressionsSentToDevice, 50
impressionsSpooled, 55 impressionsSpooled, 50
--J--- --J---
jmAttributeInstanceIndex, 85 jmAttributeInstanceIndex, 79
jmAttributeTypeIndex, 85 jmAttributeTypeIndex, 79
JmAttributeTypeTC, 45 JmAttributeTypeTC, 40
jmAttributeValueAsInteger, 86 jmAttributeValueAsInteger, 80
jmAttributeValueAsOctets, 87 jmAttributeValueAsOctets, 81
JmBooleanTC, 38 JmBooleanTC, 34
Job Monitoring MIB, V0.85 Aug 8, 1997
Job Monitoring MIB, V0.84 July 21, 1997 JmFinishingTC, 31
jmGeneralAttributePersistence, 69
jmGeneralJobPersistence, 69
jmGeneralJobSetIndex, 67
jmGeneralJobSetName, 70
jmGeneralNewestActiveJobIndex, 68
jmGeneralNumberOfActiveJobs, 68
jmGeneralOldestActiveJobIndex, 68
jmJobIDJobIndex, 72
jmJobIDJobSetIndex, 72
jmJobImpressionsCompleted, 76
jmJobImpressionsRequested, 76
jmJobIndex, 73
jmJobKOctetsProcessed, 75
jmJobKOctetsRequested, 75
jmJobOwner, 77
JmJobServiceTypesTC, 56
JmJobSourcePlatformTypeTC, 30
jmJobState, 74
jmJobStateReasons1, 74
JmJobStateReasons1TC, 58
JmJobStateReasons2TC, 62
JmJobStateReasons3TC, 65
JmJobStateReasons4TC, 66
JmJobStateTC, 38
JmJobStringTC, 29
jmJobSubmissionID, 71
JmJobSubmissionTypeTC, 36
JmMediumTypeTC, 34
jmNumberOfInterveningJobs, 75
JmPrinterResolutionTC, 33
JmPrintQualityTC, 32
JmTimeStampTC, 30
JmTonerEconomyTC, 33
JmUTF8StringTC, 29
jobAccountName, 42
jobCodedCharSet, 42
jobComment, 46
jobCompletedTime, 54
jobCopiesCompleted, 49
jobCopiesRequested, 49
jobHold, 47
jobHoldUntil, 47
jobKOctetsTransferred, 50
jobName, 43
jobOriginatingHost, 44
jobPriority, 47
jobProcessAfterDateAndTime, 47
Job Monitoring MIB, V0.85 Aug 8, 1997
JmFinishingTC, 35 jobProcessingCPUTime, 55
jmGeneralAttributePersistence, 75 jobServiceTypes, 43
jmGeneralJobPersistence, 75 jobSourceChannelIndex, 44
jmGeneralJobSetIndex, 73 jobSourcePlatformType, 44
jmGeneralJobSetName, 76 jobStartedBeingHeldTime, 54
jmGeneralNewestActiveJobIndex, 75 jobStartedProcessingTime, 54
jmGeneralNumberOfActiveJobs, 74 jobStateReasons2, 41
jmGeneralOldestActiveJobIndex, 74 jobStateReasons3, 41
jmJobIDJobIndex, 78 jobStateReasons4, 41
jmJobIDJobSetIndex, 78 jobSubmissionTime, 54
jmJobImpressionsCompleted, 83 jobSubmissionToServerTime, 54
jmJobImpressionsRequested, 82
jmJobIndex, 80
jmJobKOctetsProcessed, 82
jmJobKOctetsRequested, 81
jmJobOwner, 83
JmJobServiceTypesTC, 61
JmJobSourcePlatformTypeTC, 34
jmJobState, 80
jmJobStateReasons1, 81
JmJobStateReasons1TC, 63
JmJobStateReasons2TC, 66
JmJobStateReasons3TC, 70
JmJobStateReasons4TC, 71
JmJobStateTC, 42
jmJobSubmissionID, 77
JmJobSubmissionTypeTC, 40
JmMediumTypeTC, 38
jmNumberOfInterveningJobs, 81
JmPrinterResolutionTC, 37
JmPrintQualityTC, 37
JmTimeStampTC, 34
JmTonerEconomyTC, 38
jobAccountName, 47
jobComment, 50
jobCompletedTime, 59
jobCopiesCompleted, 54
jobCopiesRequested, 54
jobHold, 52
jobHoldUntil, 52
jobKOctetsTransferred, 54
jobName, 47
jobOriginatingHost, 49
jobPriority, 51
jobProcessAfterDateAndTime, 51
jobProcessingCPUTime, 59
jobServiceTypes, 48
jobSourceChannelIndex, 48
Job Monitoring MIB, V0.84 July 21, 1997 --M---
jobSourcePlatformType, 48 mediumConsumed, 53
jobStartedBeingHeldTime, 59 mediumRequested, 53
jobStartedProcessingTime, 59
jobStateReasons2, 46
jobStateReasons3, 46
jobStateReasons4, 46
jobSubmissionTime, 59
jobSubmissionToServerTime, 58
------ --N---
mediumConsumed, 57 numberOfDocuments, 45
mediumRequested, 57
------ --O---
numberOfDocuments, 50 other, 41
outputBin, 47
------ ------
other, 46 pagesCompleted, 51
outputBin, 52 pagesCompletedCurrentCopy, 52
pagesRequested, 51
--P--- physicalDevice, 45
printerResolutionRequested, 48
pagesCompleted, 56 printerResolutionUsed, 48
pagesCompletedCurrentCopy, 56 printQualityRequested, 48
pagesRequested, 56 printQualityUsed, 48
physicalDevice, 49 processingMessage, 41
printerResolutionRequested, 53
printerResolutionUsed, 53
printQualityRequested, 53
printQualityUsed, 53
processingMessage, 46
------ ------
queueNameRequested, 49 queueNameRequested, 45
--S--- ------
serverAssignedJobName, 47 serverAssignedJobName, 43
sheetsCompleted, 57 sheetsCompleted, 52
sheetsCompletedCurrentCopy, 57 sheetsCompletedCurrentCopy, 52
sheetsRequested, 57 sheetsRequested, 52
sides, 52 Job Monitoring MIB, V0.85 Aug 8, 1997
submittingApplicationName, 49
submittingServerName, 49
Job Monitoring MIB, V0.84 July 21, 1997 sides, 48
submittingApplicationName, 44
submittingServerName, 44
------ ------
tonerDensityRequested, 53 tonerDensityRequested, 49
tonerDensityUsed, 53 tonerDensityUsed, 49
tonerEcomonyRequested, 53 tonerEcomonyRequested, 48
tonerEcomonyUsed, 53 tonerEcomonyUsed, 48
 End of changes. 346 change blocks. 
914 lines changed or deleted 964 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/