draft-ietf-printmib-job-monitor-05.txt   draft-ietf-printmib-job-monitor-06.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 September 19, 1997
Job Monitoring MIB - V0.85 Job Monitoring MIB - V0.86
<draft-ietf-printmib-job-monitor-05.txt> <draft-ietf-printmib-job-monitor-06.txt>
Expires Feb 8, 1997 Expires Mar 19, 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 48
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
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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 1997
TABLE OF CONTENTS TABLE OF CONTENTS
1. INTRODUCTION 8 1. INTRODUCTION............................................7
1.1 Types of Information in the MIB 8 1.1 Types of Information in the MIB ......................7
1.2 Types of Job Monitoring Applications 10 1.2 Types of Job Monitoring Applications .................9
2. TERMINOLOGY AND JOB MODEL 11 2. TERMINOLOGY AND JOB MODEL..............................10
2.1 System Configurations for the Job Monitoring MIB 13 2.1 System Configurations for the Job Monitoring MIB ....12
2.1.1 Configuration 1 - client-printer 14 2.1.1 Configuration 1 - client-printer ................13
2.1.2 Configuration 2 - client-server-printer - agent in the server14 2.1.2 Configuration 2 - client-server-printer - agent in the server
......................................................13
2.1.3 Configuration 3 - client-server-printer - client monitors 2.1.3 Configuration 3 - client-server-printer - client monitors
printer agent and server 16 printer agent and server ..............................15
3. MANAGED OBJECT USAGE 17 3. MANAGED OBJECT USAGE...................................16
3.1 Conformance Considerations 17 3.1 Conformance Considerations ..........................16
3.1.1 Conformance Terminology 18 3.1.1 Conformance Terminology .........................17
3.1.2 Agent Conformance Requirements 18 3.1.2 Agent Conformance Requirements ..................17
3.1.2.1 MIB II System Group objects 18 3.1.2.1 MIB II System Group objects..................18
3.1.2.2 MIB II Interface Group objects 19 3.1.2.2 MIB II Interface Group objects...............18
3.1.2.3 Printer MIB objects 19 3.1.2.3 Printer MIB objects..........................18
3.1.3 Job Monitoring Application Conformance Requirements 19 3.1.3 Job Monitoring Application Conformance Requirements 18
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 19 3.2 The Job Tables and the Oldest Active and Newest Active Indexes 19
3.3 The Attribute Mechanism 21 3.3 The Attribute Mechanism .............................21
3.3.1 Conformance of Attribute Implementation 22 3.3.1 Conformance of Attribute Implementation .........21
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and
Attributes 23 Attributes ............................................23
3.3.3 Data Sub-types and Attribute Naming Conventions 23 3.3.3 Data Sub-types and Attribute Naming Conventions .23
3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 24 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 23
3.3.5 Requested Attributes 24 3.3.5 Requested Attributes ............................24
3.3.6 Consumption Attributes 26 3.3.6 Consumption Attributes ..........................24
3.3.7 Index Value Attributes 26 3.3.7 Index Value Attributes ..........................24
3.4 Job Identification .............................................26 3.4 Job Identification ..................................24
3.5 Internationalization Considerations 26 3.5 Internationalization Considerations .................25
3.5.1 'JmUTF8StringTC' for text generated by the server or device 25 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.86 Sep 19, 1997
Job Monitoring MIB, V0.85 Aug 8, 1997
3.5.2 'JmJobStringTC' for text generated by the job submitter 25
3.5.3 'DateAndTime' for representing the date and time 25 3.5.3 'DateAndTime' for representing the date and time 25
3.6 IANA Considerations 27 3.6 IANA Considerations .................................27
3.6.1 IANA Registration of enums 28 3.6.1 IANA Registration of enums ......................27
3.6.1.1 Type 1 enumerations 28 3.6.1.1 Type 1 enumerations..........................27
3.6.1.2 Type 2 enumerations 28 3.6.1.2 Type 2 enumerations..........................27
3.6.1.3 Type 3 enumeration 29 3.6.1.3 Type 3 enumeration...........................28
3.6.2 IANA Registration of type 2 bit values 29 3.6.2 IANA Registration of type 2 bit values ..........28
3.6.3 IANA Registration of Job Submission Id Formats 29 3.6.3 IANA Registration of Job Submission Id Formats ..28
3.6.4 IANA Registration of MIME types/sub-types for document-formats29 3.6.4 IANA Registration of MIME types/sub-types for document-formats
......................................................29
3.7 Security Considerations 30 3.7 Security Considerations .............................29
3.7.1 Read-Write objects 30 3.7.1 Read-Write objects ..............................29
3.7.2 Read-Only Objects In Other User's Jobs 30 3.7.2 Read-Only Objects In Other User's Jobs ..........29
3.8 Values for Objects 23 3.8 Values for Objects ..................................22
3.9 Notifications 30 3.9 Notifications .......................................29
4. MIB SPECIFICATION 30 4. MIB SPECIFICATION......................................29
Textual conventions for this MIB module 32 Textual conventions for this MIB module .................31
JmUTF8StringTC 33 JmUTF8StringTC ........................................32
JmJobStringTC 33 JmJobStringTC .........................................32
JmTimeStampTC 33 JmTimeStampTC .........................................32
JmJobSourcePlatformTypeTC 33 JmJobSourcePlatformTypeTC .............................32
JmFinishingTC 34 JmFinishingTC .........................................33
JmPrintQualityTC 36 JmPrintQualityTC ......................................34
JmPrinterResolutionTC 36 JmPrinterResolutionTC .................................34
JmTonerEconomyTC 37 JmTonerEconomyTC ......................................35
JmBooleanTC 37 JmBooleanTC ...........................................35
JmMediumTypeTC 38 JmMediumTypeTC ........................................36
JmJobSubmissionIDTypeTC 39 JmJobSubmissionIDTypeTC ...............................37
JmJobStateTC 41 JmJobStateTC ..........................................40
JmAttributeTypeTC 44 JmAttributeTypeTC .....................................43
other (Int32(-2..) and/or Octets63) 45 other (Int32(-2..) and/or Octets63) ..............44
Job State attributes 45 Job State attributes.................................44
jobStateReasons2 (JmJobStateReasons2TC) 45 jobStateReasons2 (JmJobStateReasons2TC) ..........44
jobStateReasons3 (JmJobStateReasons3TC) 45 jobStateReasons3 (JmJobStateReasons3TC) ..........44
jobStateReasons4 (JmJobStateReasons4TC) 45 jobStateReasons4 (JmJobStateReasons4TC) ..........44
processingMessage (UTF8String63) 45 processingMessage (UTF8String63) .................44
jobCodedCharSet (CodedCharSet) 45 jobCodedCharSet (CodedCharSet) ...................44
Job Identification attributes 46 Job Identification attributes........................45
jobAccountName (JobString63) 46 jobURI (Octets(1..255)) ..........................46
serverAssignedJobName (JobString63) 47 jobAccountName (Octets63) ........................46
jobName (JobString63) 47 Job Monitoring MIB, V0.86 Sep 19, 1997
jobServiceTypes (JmJobServiceTypesTC) 48
Job Monitoring MIB, V0.85 Aug 8, 1997
jobSourceChannelIndex (Int32(0..)) 48 serverAssignedJobName (JobString63) ..............46
jobSourcePlatformType (JmJobSourcePlatformTypeTC) 48 jobName (JobString63) ............................46
submittingServerName (JobString63) 48 jobServiceTypes (JmJobServiceTypesTC) ............47
submittingApplicationName (JobString63) 49 jobSourceChannelIndex (Int32(0..)) ...............47
jobOriginatingHost (JobString63) 49 jobSourcePlatformType (JmJobSourcePlatformTypeTC) 47
deviceNameRequested (JobString63) 49 submittingServerName (JobString63) ...............48
queueNameRequested (JobString63) 49 submittingApplicationName (JobString63) ..........48
physicalDevice (hrDeviceIndex and/or UTF8String63) 49 jobOriginatingHost (JobString63) .................48
numberOfDocuments (Int32(-2..)) 49 deviceNameRequested (JobString63) ................48
fileName (JobString63) 50 queueNameRequested (JobString63) .................48
documentName (JobString63) 50 physicalDevice (hrDeviceIndex and/or UTF8String63)48
jobComment (JobString63) 50 numberOfDocuments (Int32(-2..)) ..................49
documentFormatIndex (Int32(0..)) 50 fileName (JobString63) ...........................49
documentName (JobString63) .......................49
jobComment (JobString63) .........................49
documentFormatIndex (Int32(0..)) .................49
documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 50 documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 50
Job Parameter attributes 51 Job Parameter attributes.............................50
jobPriority (Int32(1..100)) 51 jobPriority (Int32(1..100)) ......................50
jobProcessAfterDateAndTime (DateAndTime) 51 jobProcessAfterDateAndTime (DateAndTime) .........50
jobHold (JmBooleanTC) 51 jobHold (JmBooleanTC) ............................51
jobHoldUntil (JobString63) 52 jobHoldUntil (JobString63) .......................51
outputBin (Int32(0..) and/or JobString63) 52 outputBin (Int32(0..) and/or JobString63) ........51
sides (Int32(-2..2)) 52 sides (Int32(-2..2)) .............................51
finishing (JmFinishingTC) 52 finishing (JmFinishingTC) ........................51
Image Quality attributes (requested and used) 52 Image Quality attributes (requested and used)........51
printQualityRequested (JmPrintQualityTC) 52 printQualityRequested (JmPrintQualityTC) .........52
printQualityUsed (JmPrintQualityTC) 53 printQualityUsed (JmPrintQualityTC) ..............52
printerResolutionRequested (JmPrinterResolutionTC) 53 printerResolutionRequested (JmPrinterResolutionTC)52
printerResolutionUsed (JmPrinterResolutionTC) 53 printerResolutionUsed (JmPrinterResolutionTC) ....52
tonerEcomonyRequested (JmTonerEconomyTC) 53 tonerEcomonyRequested (JmTonerEconomyTC) .........52
tonerEcomonyUsed (JmTonerEconomyTC) 53 tonerEcomonyUsed (JmTonerEconomyTC) ..............52
tonerDensityRequested (Int32(-2..100)) 53 tonerDensityRequested (Int32(-2..100)) ...........52
tonerDensityUsed (Int32(-2..100)) 53 tonerDensityUsed (Int32(-2..100)) ................52
Job Progress attributes (requested and consumed) 53 Job Progress attributes (requested and consumed).....53
jobCopiesRequested (Int32(-2..)) 54 jobCopiesRequested (Int32(-2..)) .................53
jobCopiesCompleted (Int32(-2..)) 54 jobCopiesCompleted (Int32(-2..)) .................53
documentCopiesRequested (Int32(-2..)) 54 documentCopiesRequested (Int32(-2..)) ............53
documentCopiesCompleted (Int32(-2..)) 54 documentCopiesCompleted (Int32(-2..)) ............53
jobKOctetsTransferred (Int32(-2..)) 54 jobKOctetsTransferred (Int32(-2..)) ..............53
Impression attributes (requested and consumed) 55 Impression attributes (requested and consumed).......54
impressionsSpooled (Int32(-2..)) 55 impressionsSpooled (Int32(-2..)) .................54
impressionsSentToDevice (Int32(-2..)) 55 impressionsSentToDevice (Int32(-2..)) ............54
impressionsInterpreted (Int32(-2..)) 55 impressionsInterpreted (Int32(-2..)) .............54
impressionsCompletedCurrentCopy (Int32(-2..)) 55 impressionsCompletedCurrentCopy (Int32(-2..)) ....54
fullColorImpressionsCompleted (Int32(-2..)) 55 fullColorImpressionsCompleted (Int32(-2..)) ......54
highlightColorImpressionsCompleted (Int32(-2..)) 55 highlightColorImpressionsCompleted (Int32(-2..)) .55
Page attributes (requested and consumed) 56 Page attributes (requested and consumed).............55
pagesRequested (Int32(-2..)) 56 Job Monitoring MIB, V0.86 Sep 19, 1997
pagesCompleted (Int32(-2..)) 56
pagesCompletedCurrentCopy (Int32(-2..)) 56
Job Monitoring MIB, V0.85 Aug 8, 1997
Sheet attributes (requested and consumed) 57 pagesRequested (Int32(-2..)) .....................55
sheetsRequested (Int32(-2..)) 57 pagesCompleted (Int32(-2..)) .....................55
sheetsCompleted (Int32(-2..)) 57 pagesCompletedCurrentCopy (Int32(-2..)) ..........56
sheetsCompletedCurrentCopy (Int32(-2..)) 57 Sheet attributes (requested and consumed)............56
Resource attributes (requested and consumed) 57 sheetsRequested (Int32(-2..)) ....................56
sheetsCompleted (Int32(-2..)) ....................56
sheetsCompletedCurrentCopy (Int32(-2..)) .........56
Resource attributes (requested and consumed).........56
mediumRequested (JmMediumTypeTC and/or JobString63) 57 mediumRequested (JmMediumTypeTC and/or JobString63) 57
mediumConsumed (JobString63) 57 mediumConsumed (JobString63) .....................57
colorantRequested (Int32(-2..) and/or JobString63) 58 colorantRequested (Int32(-2..) and/or JobString63)57
colorantConsumed (Int32(-2..) and/or JobString63) 58 colorantConsumed (Int32(-2..) and/or JobString63) 57
Time attributes (set by server or device) 58 Time attributes (set by server or device)............57
jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 59 jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 58
jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 59 jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 58
jobStartedBeingHeldTime (JmTimeStampTC and/or DateAndTime) 59 jobStartedBeingHeldTime (JmTimeStampTC and/or DateAndTime) 58
jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 59 jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 58
jobCompletedTime (JmTimeStampTC and/or DateAndTime) 59 jobCompletionTime (JmTimeStampTC and/or DateAndTime) 58
jobProcessingCPUTime (Int32(-2..)) 59 jobProcessingCPUTime (Int32(-2..)) ...............59
JmJobServiceTypesTC 61 JmJobServiceTypesTC ...................................61
JmJobStateReasons1TC 63 JmJobStateReasons1TC ..................................62
JmJobStateReasons2TC 67 JmJobStateReasons2TC ..................................67
JmJobStateReasons3TC 71 JmJobStateReasons3TC ..................................70
JmJobStateReasons4TC 72 JmJobStateReasons4TC ..................................71
The General Group (MANDATORY) 73 The General Group (MANDATORY) ...........................73
jmGeneralJobSetIndex (Int32(1..32767)) 73 jmGeneralJobSetIndex (Int32(1..32767)) ..............73
jmGeneralNumberOfActiveJobs (Int32(0..)) 74 jmGeneralNumberOfActiveJobs (Int32(0..)) ............74
jmGeneralOldestActiveJobIndex (Int32(0..)) 74 jmGeneralOldestActiveJobIndex (Int32(0..)) ..........74
jmGeneralNewestActiveJobIndex (Int32(0..)) 75 jmGeneralNewestActiveJobIndex (Int32(0..)) ..........75
jmGeneralJobPersistence (Int32(15..)) 75 jmGeneralJobPersistence (Int32(15..)) ...............75
jmGeneralAttributePersistence (Int32(15..)) 75 jmGeneralAttributePersistence (Int32(15..)) .........75
jmGeneralJobSetName (UTF8String63) 76 jmGeneralJobSetName (UTF8String63) ..................76
The Job ID Group (MANDATORY) 76 The Job ID Group (MANDATORY) ............................76
jmJobSubmissionID (OCTET STRING(SIZE(48))) 77 jmJobSubmissionID (OCTET STRING(SIZE(48))) ..........77
jmJobIDJobSetIndex (Int32(1..32767)) 78 jmJobIDJobSetIndex (Int32(1..32767)) ................78
jmJobIDJobIndex (Int32(1..)) 78 jmJobIDJobIndex (Int32(1..)) ........................78
The Job Group (MANDATORY) 79 The Job Group (MANDATORY) ...............................79
jmJobIndex (Int32(1..)) 80 jmJobIndex (Int32(1..)) .............................80
jmJobState (JmJobStateTC) 80 jmJobState (JmJobStateTC) ...........................80
jmJobStateReasons1 (JmJobStateReasons1TC) 81 jmJobStateReasons1 (JmJobStateReasons1TC) ...........81
jmNumberOfInterveningJobs (Int32(-2..)) 81 jmNumberOfInterveningJobs (Int32(-2..)) .............81
jmJobKOctetsRequested (Int32(-2..)) 81 jmJobKOctetsRequested (Int32(-2..)) .................81
jmJobKOctetsProcessed (Int32(-2..)) 82 jmJobKOctetsProcessed (Int32(-2..)) .................82
jmJobImpressionsRequested (Int32(-2..)) 83 jmJobImpressionsRequested (Int32(-2..)) .............82
jmJobImpressionsCompleted (Int32(-2..)) 83 jmJobImpressionsCompleted (Int32(-2..)) .............83
jmJobOwner (JobString63) 83 Job Monitoring MIB, V0.86 Sep 19, 1997
The Attribute Group (MANDATORY) 84 jmJobOwner (JobString63) ............................83
Job Monitoring MIB, V0.85 Aug 8, 1997
jmAttributeTypeIndex (JmAttributeTypeTC) 86 The Attribute Group (MANDATORY) .........................84
jmAttributeInstanceIndex (Int32(1..32767)) 86 jmAttributeTypeIndex (JmAttributeTypeTC) ............85
jmAttributeValueAsInteger (Int32(-2..)) 87 jmAttributeInstanceIndex (Int32(1..32767)) ..........86
jmAttributeValueAsOctets (Octets63) 88 jmAttributeValueAsInteger (Int32(-2..)) .............86
jmAttributeValueAsOctets (Octets63) .................87
5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 91 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 92 PROTOCOLS.................................................92
6.1 Hewlett-Packard's Printer Job Language (PJL) 92 6.1 Hewlett-Packard's Printer Job Language (PJL) ........92
6.2 ISO DPA 92 6.2 ISO DPA .............................................92
7. REFERENCES 93 7. REFERENCES.............................................93
8. AUTHOR'S ADDRESSES 94 8. AUTHOR'S ADDRESSES.....................................94
9. INDEX 97 9. INDEX..................................................97
Job Monitoring MIB, V0.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 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 9, line 5 skipping to change at page 8, line 5
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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 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 10, line 5 skipping to change at page 9, line 5
Provide information to allow the prediction of consumable usage Provide information to allow the prediction of consumable usage
and resource need. and resource need.
The MIB supports printers that can contain more than one job at a time, The MIB supports printers that can contain more than one job at a time,
but still be usable for low end printers that only contain a single job but still be usable for low end printers that only contain a single job
at a time. In particular, the MIB supports the needs of Windows and at a time. In particular, the MIB supports the needs of Windows and
other PC environments for managing low-end direct-connect (serial or other PC environments for managing low-end direct-connect (serial or
parallel) and networked devices without unnecessary overhead or parallel) and networked devices without unnecessary overhead or
complexity, while also providing for higher end systems and devices. complexity, while also providing for higher end systems and devices.
Job Monitoring MIB, V0.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 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
a defined period after the job completes. The Job Submission ID ending a defined period after the job completes. The Job
table provides the map to find the specific job to be monitored. Submission ID table provides the map to find the specific job to
be monitored.
2. Monitor all 'active' jobs in a queue, which this specification 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
selecting a least busy printer, so the MIB is designed for such a when selecting a least busy printer, so the MIB is designed for
program to start up quickly and find the information needed such a program to start up quickly and find the information
quickly without having to read all (completed) jobs in order to needed quickly without having to read all (completed) jobs in
find the active jobs. System operators may also use such a order to find the active jobs. System operators may also use
program, in which case it would be running for a long period of such a program, in which case it would be running for a long
time and may also be interested in the jobs that have completed. period of time and may also be interested in the jobs that have
Finally such a program may be used to provide an enhanced console completed. Finally such a program may be used to provide an
and logging capability. enhanced console 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
copy MIB data during the job-retention period is somewhat to copy MIB data during the job-retention period is somewhat
unreliable, since the accounting program may not be running (or unreliable, since the accounting program may not be running (or
may have crashed). Such a program is also expected to keep a may have crashed). Such a program is also expected to keep a
shadow copy of the entire Job Attribute table including completed, shadow copy of the entire Job Attribute table including
canceled, and aborted jobs which the program updates on each completed, canceled, and aborted jobs which the program updates
polling cycle. Such a program polls at the rate of the on each polling cycle. Such a program polls at the rate of the
persistence of the Attribute table. The design is not optimized persistence of the Attribute table. The design is not optimized
to help such an application determine which jobs are completed, to help such an application determine which jobs are completed,
canceled, or aborted. Instead, the application SHALL query each canceled, or aborted. Instead, the application SHALL query each
job that the application's shadow copy shows was not complete, job that the application's shadow copy shows was not complete,
canceled, or aborted at the previous poll cycle to see if it is canceled, or aborted at the previous poll cycle to see if it is
now complete or canceled, plus any new jobs that have been now complete or canceled, plus any new jobs that have been
submitted. 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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 1997
The MIB is designed so that an additional MIB(s) can be specified in the The MIB is designed so that an additional MIB(s) can be specified in the
future for monitoring multi-function (scan, FAX, copy) jobs as an future for monitoring multi-function (scan, FAX, copy) jobs as an
augmentation to this MIB. augmentation to this MIB.
2. Terminology and Job Model 2. Terminology and Job Model
This section defines the terms that are used in this specification and This section defines the terms that are used in this specification and
the general model for jobs. the general model for jobs.
NOTE - Existing systems use conflicting terms, so these terms are NOTE - Existing systems use conflicting terms, so these terms are
drawn from the ISO 10175 Document Printing Application (DPA) drawn from the ISO 10175 Document Printing Application (DPA)
standard[iso-dpa]. For example, PostScript systems use the term standard[iso-dpa]. For example, PostScript systems use the term
session for what is called a job in this specification and the term session for what is called a job in this specification and the term
job to mean what is called a document in this specification. PJL job to mean what is called a document in this specification.
systems use the term job to mean what is called a job in this
specification. PJL also supports multiple documents per job, but does
not support specifying per-document attributes independently for each
document.
Job: a unit of work whose results are expected together without Job: A unit of work whose results are expected together without
interjection of unrelated results. A job contains one or more interjection of unrelated results. A job contains one or more
documents. documents.
Job Set: a group of jobs that are queued and scheduled together Job Set: A group of jobs that are queued and scheduled together
according to a specified scheduling algorithm for a specified device or according to a specified scheduling algorithm for a specified device or
set of devices. For implementations that embed the SNMP agent in the set of devices. For implementations that embed the SNMP agent in the
device, the MIB job set normally represents all the jobs known to the device, the MIB job set normally represents all the jobs known to the
device, so that the implementation only implements a single job set. If device, so that the implementation only implements a single job set. If
the SNMP agent is implemented in a server that controls one or more the SNMP agent is implemented in a server that controls one or more
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 over a serial or configuration, using any job submission protocol over a serial or
parallel port to a directly-connected device or over the network to a parallel port to a directly-connected device or over the network to a
networked-connected device. networked-connected device.
Server: a network entity that accepts jobs from clients and in turn Server: A network entity that accepts jobs from clients and in turn
submits the jobs to printers and other devices that may be directly submits the jobs to printers and other devices that may be directly
connected to the server via a serial or parallel port or may be on the connected to the server via a serial or parallel port or may be on the
network. A server MAY be a printer supervisor control program, or a network. A server MAY be a printer supervisor control program, or a
print spooler. print spooler.
Job Monitoring MIB, V0.85 Aug 8, 1997 Device: A hardware entity that (1) interfaces to humans, such as a
device that produces marks on paper or scans marks on paper to produce
an electronic representation, (2) accesses digital media, such as CD-
Job Monitoring MIB, V0.86 Sep 19, 1997
Device: a hardware entity that (1) interfaces to humans in human ROMs, or (3) interfaces electronically to another device, such as sends
perceptible means, such as produces marks on paper, scans marks on paper FAX data to another FAX device.
to produce an electronic representations, or writes CD-ROMs or (2)
interfaces electronically to another device, such as sends FAX data to
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
and on which printer to print the job. A spooler is a client to a and on which printer to print the job. A spooler is a client to a
printer or a printer supervisor, depending on implementation. printer or a printer supervisor, depending on implementation.
Spooling: the act of a device or server of (1) accepting jobs and (2) Spooling: The act of a device or server of (1) accepting jobs and (2)
writing the job's attributes and document data on to secondary storage. writing the job's attributes and document data on to secondary storage.
Queuing: the act of a device or server of ordering (queuing) the jobs Queuing: The act of a device or server of ordering (queuing) the jobs
for the purposes of scheduling the jobs to be processed. for the purposes of scheduling the jobs to be processed.
Monitor or Job Monitoring Application: the SNMP management application Monitor or Job Monitoring Application: The SNMP management application
that End Users, and System Operators use to monitor jobs using SNMP. A that End Users, and System Operators use to monitor jobs using SNMP. A
monitor MAY be either a separate application or MAY be part of the monitor MAY be either a separate application or MAY be part of the
client that also submits jobs. client that also submits jobs.
Accounting Application: the SNMP management application that copies job Accounting Application: The SNMP management application that copies job
information to some more permanent medium so that another application information to some more permanent medium so that another application
can perform accounting on the data for Accountants, Asset Managers, and can perform accounting on the data for Accountants, Asset Managers, and
Capacity Planners use. Capacity Planners use.
Agent: the network entity that accepts SNMP requests from a monitor or Agent: The network entity that accepts SNMP requests from a monitor or
accounting application and provides access to the instrumentation for accounting application and provides access to the instrumentation for
managing jobs modeled by the management objects defined in the Job managing jobs modeled by the management objects defined in the Job
Monitoring MIB module for a server or a device. Monitoring MIB module for a server or a device.
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.
Job Monitoring MIB, V0.85 Aug 8, 1997 End User: A user that uses a client to submit a print job.
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 Instruction: an instruction specifying how, when, or where the job Job Monitoring MIB, V0.86 Sep 19, 1997
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.
SNMP Information Object: a name, value-pair that specifies an action, a SNMP Information Object: A name, value-pair that specifies an action, a
status, or a condition in an SNMP MIB. Objects are identified in SNMP status, or a condition in an SNMP MIB. Objects are identified in SNMP
by an OBJECT IDENTIFIER. by an OBJECT IDENTIFIER.
Attribute: a name, value-pair that specifies a job or document Attribute: A name, value-pair that specifies a job or document
instruction, a status, or a condition of a job or a document that has instruction, a status, or a condition of a job or a document that has
been submitted to a server or device. A particular attribute NEED NOT been submitted to a server or device. A particular attribute NEED NOT
be present in each job instance. In other words, attributes are present be present in each job instance. In other words, attributes are present
in a job instance only when there is a need to express the value, either in a job instance only when there is a need to express the value, either
because (1) the client supplied a value in the job submission protocol, because (1) the client supplied a value in the job submission protocol,
(2) the document data contained an embedded attribute, or (3) the server (2) the document data contained an embedded attribute, or (3) the server
or device supplied a default value. An agent SHALL represent an or device supplied a default value. An agent SHALL represent an
attribute as an entry (row) in the Attribute table in this MIB in which attribute as an entry (row) in the Attribute table in this MIB in which
entries are present only when necessary. Attributes are identified in entries are present only when necessary. Attributes are identified in
this MIB by an enum. this MIB by an enum.
Job Monitoring (using SNMP): the activity of a management application Job Monitoring (using SNMP): The activity of a management application
of accessing the MIB and (1) identifying jobs in the job tables being of accessing the MIB and (1) identifying jobs in the job tables being
processed by the server, printer or other devices, and (2) displaying processed by the server, printer or other devices, and (2) displaying
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 section 1.1 entitled "Types of devices are shown as printers. See section 1.1 entitled "Types of
Information in the MIB". Information in the MIB".
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.86 Sep 19, 1997
2.1.1 Configuration 1 - client-printer 2.1.1 Configuration 1 - client-printer
In the client-printer configuration 1, the client(s) submit jobs In the client-printer configuration 1, the client(s) submit jobs
directly to the printer, either by some direct connect, or by network directly to the printer, either by some direct connect, or by network
connection. connection.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs 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
skipping to change at page 15, line 4 skipping to change at page 13, line 49
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
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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:
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
skipping to change at page 16, line 4 skipping to change at page 14, line 50
+========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
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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 agent. the printer. That server does not contain a Job Monitoring MIB agent.
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs 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 monitor 2. A Job Monitoring MIB agent that is part of the printer to
jobs after the server passes the jobs to the printer. In such monitor jobs after the server passes the jobs to the printer.
configurations, the server deletes its copy of the job from the In such configurations, the server deletes its copy of the job
server after submitting the job to the printer usually almost from the server after submitting the job to the printer usually
immediately (before the job does much processing, if any). almost immediately (before the job does much processing, if
any).
In configuration 3, the agent (in the printer) SHALL keep the values of In configuration 3, the agent (in the printer) SHALL keep the values 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
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 Job Monitoring MIB, V0.86 Sep 19, 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==+
# | | # | |
skipping to change at page 18, line 5 skipping to change at page 17, line 5
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 Job Monitoring MIB, V0.86 Sep 19, 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
skipping to change at page 18, line 41 skipping to change at page 17, line 41
A conforming agent: A conforming agent:
1. SHALL implement all MANDATORY groups in this specification. 1. SHALL implement all MANDATORY groups in this specification.
2. SHALL implement any attributes if (1) the server or device 2. SHALL implement any attributes if (1) the server or device
supports the functionality represented by the attribute and (2) supports the functionality represented by the attribute and (2)
the information is available to the agent. the information is available to the agent.
3. SHOULD implement both forms of an attribute if it implements an 3. SHOULD implement both forms of an attribute if it implements an
attribute that permits a choice of INTEGER and OCTET STRING forms, attribute that permits a choice of INTEGER and OCTET STRING
since implementing both forms may help management applications by forms, since implementing both forms may help management
giving them a choice of representations, since the representation applications by giving them a choice of representations, since
are equivalent. See the JmAttributeTypeTC textual-convention. the representation are equivalent. See the JmAttributeTypeTC
textual-convention.
4. NOTE - This MIB, like the Printer MIB, is written following the NOTE - This MIB, like the Printer MIB, is written following the
subset of SMIv2 that can be supported by SMIv1 and SNMPv1 subset of SMIv2 that can be supported by SMIv1 and SNMPv1
implementations. implementations.
Job Monitoring MIB, V0.86 Sep 19, 1997
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
skipping to change at page 19, line 28 skipping to change at page 18, line 34
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 direct- agent is providing access to a server that controls one or more direct-
connect or networked printers, the agent NEED NOT implement the Printer connect or networked printers, the agent NEED NOT implement the Printer
MIB and 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 MANDATORY groups and all MANDATORY attributes that are required
be implemented by an agent according to Section 3.1.2 and SHALL to be implemented by an agent according to Section 3.1.2 and
either present them to the user or ignore them. SHALL either present them to the user or ignore them.
2. SHALL accept the full syntactic range for all attributes, 2. SHALL accept the full syntactic range for all attributes,
including enum and bit values specified in this specification and including enum and bit values specified in this specification
additional ones that may be registered with IANA and SHALL either and additional ones that may be registered with IANA and SHALL
present them to the user or ignore them. In particular, a either present them to the user or ignore them. In particular,
conforming job monitoring application SHALL not malfunction when a conforming job monitoring application SHALL not malfunction
receiving any standard or registered enum or bit values. See when receiving any standard or registered enum or bit values.
Section 3.6 entitled "IANA Considerations". See Section 3.6 entitled "IANA Considerations".
3. SHALL NOT fail when operating with agents that materialize 3. SHALL NOT fail when operating with agents that materialize
attributes after the job has been submitted, as opposed to when attributes after the job has been submitted, as opposed to when
the job is submitted. 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
time attribute, since agents are free to implement either time the time attribute, since agents are free to implement either
form. time form.
Job Monitoring MIB, V0.86 Sep 19, 1997
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 20, line 32 skipping to change at page 19, line 40
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 premature re-use of a jmJobIndex single time, so as to minimize the premature re-use of a jmJobIndex
value for a newer job while clients retain the same 'stale' value for an value for a newer job while clients retain the same 'stale' value for an
older job. older job.
It is recommended that agents that are providing access to It is recommended that agents that are providing access to
servers/devices that already allocate job-identifiers for jobs as servers/devices that already allocate job-identifiers for jobs as
integers use the same integer value for the jmJobIndex. Then the jobs integers use the same integer value for the jmJobIndex. Then management
will have the same job identifier value as the jmJobIndex value, so that applications using this MIB and applications using other protocols will
users viewing jobs by management applications using this MIB and see the same job identifiers for the same jobs. Agents providing access
applications using other protocols will see the same job identifiers for to systems that contain jobs with a job identifier of 0 SHALL map the
the same jobs. Agents providing access to systems that contain jobs job identifier value 0 to a jmJobIndex value that is one higher than the
with a job identifier of 0 SHALL map the job identifier value 0 to a highest job identifier value that any job can have on that system. Then
jmJobIndex value that is one higher than the highest job identifier only job 0 will have a different job-identifier value than the job's
value that any job can have on that system. Then only job 0 will have a jmJobIndex value.
different job-identifier value than the job's jmJobIndex value.
NOTE - If a server or device accepts jobs using multiple job submission NOTE - If a server or device accepts jobs using multiple job submission
protocols, it may be difficult for the agent to meet the recommendation 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 to use the job-identifier values that the server or device assigns as
the jmJobIndex value, unless the server/device assigns job-identifiers the jmJobIndex value, unless the server/device assigns job-identifiers
for each of its job submission protocols from the same job-identifier for each of its job submission protocols from the same job-identifier
number space. number space.
Job Monitoring MIB, V0.86 Sep 19, 1997
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 (though the agent SHALL assign the jmGeneralNewestActiveJobIndex object (though the agent SHALL assign the
next incremental jmJobIndex value to the job). 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
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
skipping to change at page 21, line 42 skipping to change at page 20, line 48
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 jmAttributeTable table when the NOTE - Applications detect the end of the jmAttributeTable table when
OID returned by the GetNext operation is an OID in a different MIB. the OID returned by the GetNext operation is an OID in a different MIB.
There is no object in this MIB that specifies the maximum value for the There is no object in this MIB that specifies the maximum value for the
jmJobIndex supported by the implementation. jmJobIndex supported by the implementation.
Job Monitoring MIB, V0.86 Sep 19, 1997
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.
skipping to change at page 22, line 51 skipping to change at page 22, line 4
GetNext operation returns attributes. Most attributes apply to all GetNext operation returns attributes. Most attributes apply to all
three configurations covered by this MIB specification (see section 2.1 three configurations covered by this MIB specification (see section 2.1
entitled "System Configurations for the Job Monitoring MIB"). Those entitled "System Configurations for the Job Monitoring MIB"). Those
attributes that apply to a particular configuration are indicated as attributes that apply to a particular configuration are indicated as
'Configuration n:' and SHALL NOT be used with other configurations. 'Configuration n:' and SHALL NOT be used with other configurations.
3.3.1 Conformance of Attribute Implementation 3.3.1 Conformance of Attribute Implementation
An agent SHALL implement any attribute if (1) the server or device An agent SHALL implement any attribute if (1) the server or device
supports the functionality represented by the attribute and (2) the supports the functionality represented by the attribute and (2) the
Job Monitoring MIB, V0.86 Sep 19, 1997
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.
skipping to change at page 23, line 47 skipping to change at page 23, line 5
jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY
objects, SNMP requires that the agent SHALL always create an attribute objects, SNMP requires that the agent SHALL always create an attribute
row with both objects specified. However, for most attributes the agent row with both objects specified. However, for most attributes the agent
SHALL return a "useful" value for one of the objects and SHALL return SHALL return a "useful" value for one of the objects and SHALL return
the 'other' value for the other object. For integer only attributes, the 'other' value for the other object. For integer only attributes,
the agent SHALL always return a zero-length string value for the the agent SHALL always return a zero-length string value for the
jmAttributeValueAsOctets object. For octet string only attributes, the jmAttributeValueAsOctets object. For octet string only attributes, the
agent SHALL always return a '-1' value for the jmAttributeValueAsInteger agent SHALL always return a '-1' value for the jmAttributeValueAsInteger
object. object.
Job Monitoring MIB, V0.86 Sep 19, 1997
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
skipping to change at page 24, line 47 skipping to change at page 24, line 4
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 - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes, NOTE - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes,
such as fileName(34) or documentName(35) which are specified to be 'per- such as fileName(34) or documentName(35) which are specified to be 'per-
Job Monitoring MIB, V0.86 Sep 19, 1997
document' attributes, but are not allowed for 'intensive' 'MULTI-ROW' document' attributes, but are not allowed for 'intensive' 'MULTI-ROW'
attributes, such as mediumConsumed(171) and documentFormat(38) which are attributes, such as mediumConsumed(171) and documentFormat(38) which are
specified to be 'per-job' attributes. 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.
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
skipping to change at page 25, line 35 skipping to change at page 24, line 43
names end with the word 'Index'. If the agent has not (yet) assigned an names end with the word 'Index'. If the agent has not (yet) assigned an
index value for a particular index attribute for a job, the agent 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 jobURI, jobName,
jobOriginatingHost, etc. In addition, there is a jmJobSubmissionID jobOriginatingHost, etc. In addition, there is a jmJobSubmissionID
object that is a text string table index. Being a table index allows a object that is a text string table index. Being a table index allows a
monitoring application to quickly locate and identify a particular job monitoring application to quickly locate and identify a particular job
of interest that was submitted from a particular client by the user of interest that was submitted from a particular client by the user
invoking the monitoring application. The Job Monitoring MIB needs to invoking the monitoring application. The Job Monitoring MIB needs to
provide for identification of the job at both sides of the job provide for identification of the job at both sides of the job
submission process. The primary identification point is the client submission process. The primary identification point is the client
side. The jmJobSubmissionID allows the monitoring application to side. The jmJobSubmissionID allows the monitoring application to
identify the job of interest from all the jobs currently "known" by the identify the job of interest from all the jobs currently "known" by the
server or device. The value of jmJobSubmissionID can be assigned by server or device. The value of jmJobSubmissionID can be assigned by
Job Monitoring MIB, V0.86 Sep 19, 1997
either the client's local system or a downstream server or device. The either the client's local system or a downstream server or device. The
point of assignment depends on the job submission protocol in use. 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
a particular job. See Section 3.2, entitled 'The Job Tables and the a particular job. See Section 3.2, entitled 'The Job Tables and the
Job Monitoring MIB, V0.85 Aug 8, 1997
Oldest Active and Newest Active Indexes' for the specification of how Oldest Active and Newest Active Indexes' for the specification of how
the agent shall assign the jmJobIndex values. 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 The MIB provides a mapping table that maps each jmJobSubmissionID value
to the corresponding jmJobIndex value generated by the agent, so that an to the corresponding jmJobIndex value generated by the agent, so that an
application can determine the correct value for the jmJobIndex value for application can determine the correct value for the jmJobIndex value for
the job of interest in a single Get operation, given the Job Submission the job of interest in a single Get operation, given the Job Submission
ID. See the jmJobIDGroup. 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
This section describes the internationalization considerations included This section describes the internationalization considerations included
in this MIB. in this MIB.
3.5.1 'JmUTF8StringTC' for text generated by the server or device 3.5.1 Text generated by the server or device
There are a few objects and attributes that are represented using the There are a few objects and attributes generated by the server or device
Universal Multiple-Octet Coded Character Set (UCS) [ISO-10646] encoded that SHALL be represented using the Universal Multiple-Octet Coded
as an octet string using the UTF-8 [UTF-8] character encoding scheme. Character Set (UCS) [ISO-10646]. These objects and attributes are
The 'JmUTF8StringTC' textual convention is used to indicate UTF-8 text always supplied (if implemented) by the agent, not by the job submitting
strings. These objects and attributes are always supplied (if client:
implemented) by the agent, not by the job submitting client:
1. jmGeneralJobSetName object 1. jmGeneralJobSetName object
2. processingMessage(6) attribute 2. processingMessage(6) attribute
3. physicalDevice(32) (name value) attribute 3. physicalDevice(32) (name value) attribute
The coded character set for representing these objects and attributes The character encoding scheme for representing these objects and
SHALL be UTF-8 as recommended by RFC 2130 [RFC 2130] and the "IETF attributes SHALL be UTF-8 as recommended by RFC 2130 [RFC 2130] and the
Policy on Character Sets and Language" [char-set policy]. "IETF Policy on Character Sets and Language" [char-set policy]. The
'JmUTF8StringTC' textual convention is used to indicate UTF-8 text
strings.
NOTE - For strings in 7-bit US-ASCII, there is no impact since the UTF-8 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. representation of 7-bit ASCII is identical to the US-ASCII [US-ASCII]
encoding.
3.5.2 'JmJobStringTC' for text generated by the job submitter Job Monitoring MIB, V0.86 Sep 19, 1997
3.5.2 Text generated by the job submitter
All of the objects and attributes represented by the 'JmJobStringTC' All of the objects and attributes represented by the 'JmJobStringTC'
textual-convention are either (1) supplied in the job submission textual-convention are either (1) supplied in the job submission
Job Monitoring MIB, V0.85 Aug 8, 1997
protocol by the client that submits the job to the server or device or protocol by the client that submits the job to the server or device or
(2) are defaulted by the server or device if the job submitting client (2) are defaulted by the server or device if the job submitting client
does not supply values. The agent SHALL represent these objects and 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 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 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 or encoding scheme. In any case, the resulting coded
character set representation SHOULD be UTF-8 [UTF-8], but SHALL be one 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 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 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 code positions 128 to 255 SHALL represent single-byte or multi-byte
graphic characters structured according to ISO 2022 [ISO 2022] or SHALL graphic characters structured according to ISO 2022 [ISO 2022] or SHALL
be unused. be unused.
The coded character set SHALL be one of the ones registered with IANA The coded character set SHALL be one of the ones registered with IANA
[IANA] and SHALL be identified by the jobCodedCharSet attribute in the [IANA] and SHALL be identified by the jobCodedCharSet attribute in the
jmJobAttributeTable for the job. If the agent does not know what coded jmJobAttributeTable for the job. If the agent does not know what coded
character set was used by the job submitting client, the agent SHALL character set was used by the job submitting client, the agent SHALL
return the 'unknown(2)' value for the jobCodedCharSet attribute for the either (1) return the 'unknown(2)' value for the jobCodedCharSet
job. attribute or (2) not return the jobCodedCharSet attribute for the job.
Examples of coded character sets which meet this criteria for use as the 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 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 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- 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 1990 Japanese [JIS X0208], US-ASCII plus GB2312-1980 PRC Chinese
[GB2312]. See the IANA registry of coded character sets [IANA [GB2312]. See the IANA registry of coded character sets [IANA
charsets]. charsets].
Examples of coded character sets which do not meet this criteria are: Examples of coded character sets which do not meet this criteria are:
skipping to change at page 27, line 50 skipping to change at page 27, line 5
The jobCodedCharSet attribute uses the imported 'CodedCharSet' textual- The jobCodedCharSet attribute uses the imported 'CodedCharSet' textual-
convention from the Printer MIB [printmib]. convention from the Printer MIB [printmib].
3.5.3 'DateAndTime' for representing the date and time 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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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
skipping to change at page 28, line 49 skipping to change at page 28, line 4
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. JmUTF8StringTC
2. JmJobStringTC 2. JmJobStringTC
3. JmTimeStampTC 3. JmTimeStampTC
4. JmFinishingTC [same enum values as IPP "finishing" attribute] 4. JmFinishingTC [same enum values as IPP "finishing" attribute]
Job Monitoring MIB, V0.86 Sep 19, 1997
5. JmPrintQualityTC [same enum values as IPP "print-quality" 5. JmPrintQualityTC [same enum values as IPP "print-quality"
attribute] attribute]
6. JmTonerEconomyTC 6. JmTonerEconomyTC
7. JmMediumTypeTC 7. JmMediumTypeTC
8. JmJobSubmissionTypeTC 8. JmJobSubmissionTypeTC
Job Monitoring MIB, V0.85 Aug 8, 1997
9. JmJobStateTC [same enum values as IPP "job-state" attribute] 9. JmJobStateTC [same enum values as IPP "job-state" attribute]
10.JmAttributeTypeTC 10.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.
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
skipping to change at page 29, line 47 skipping to change at page 29, line 5
Section 3.6.1.2. Section 3.6.1.2.
3.6.3 IANA Registration of Job Submission Id Formats 3.6.3 IANA Registration of Job Submission Id Formats
In addition to enums and bit values, this specification assigns a single In addition to enums and bit values, this specification assigns a single
ASCII digit or letter to various job submission ID formats. See the ASCII digit or letter to various job submission ID formats. See the
JmJobSubmissionIDTypeTC textual-convention and the object. The JmJobSubmissionIDTypeTC textual-convention and the object. The
registration of jmJobSubmissionID format numbers SHALL follow the registration of jmJobSubmissionID format numbers SHALL follow the
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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.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.
skipping to change at page 31, line 5 skipping to change at page 30, 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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 1997
Job-Monitoring-MIB DEFINITIONS ::= BEGIN Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed -- The following textual-conventions are needed
-- to implement certain attributes, but are not -- to implement certain attributes, but are not
skipping to change at page 31, line 37 skipping to change at page 30, line 37
-- 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 }
jobmonMIB MODULE-IDENTITY jobmonMIB MODULE-IDENTITY
LAST-UPDATED "9708080000Z" LAST-UPDATED "9709190000Z"
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.86 Sep 19, 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-05.txt File: draft-ietf-printmib-job-monitor-06.txt
Version: 0.85" Version: 0.86"
::= { temp 105 } ::= { temp 105 }
-- Textual conventions for this MIB module -- Textual conventions for this MIB module
JmUTF8StringTC ::= TEXTUAL-CONVENTION JmUTF8StringTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a" DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To facilitate internationalization, this TC represents "To facilitate internationalization, this TC represents
information taken from the ISO/IEC IS 10646-1 character set, information taken from the ISO/IEC IS 10646-1 character set,
encoded as an octet string using the UTF-8 character encoding encoded as an octet string using the UTF-8 character encoding
scheme. 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 REFERENCE
"See section 3.5.1, ''JmUTF8StringTC' for text generated by the "See section 3.5.1, entitled: 'Text generated by the server or
server or device'." device'."
SYNTAX OCTET STRING (SIZE (0..63)) SYNTAX OCTET STRING (SIZE (0..63))
JmJobStringTC ::= TEXTUAL-CONVENTION JmJobStringTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To facilitate internationalization, this TC represents "To facilitate internationalization, this TC represents
information using any coded character set registered by IANA information using any coded character set registered by IANA as
that has the following properties: (1) code positions from 0 to specified in section 3.5.2. While it is recommended that the
31 SHALL not be used, (2) 32 to 127 SHALL be US-ASCII [US- coded character set be UTF-8 [UTF-8], the actual coded character
ASCII], (3) 127 SHALL be unused, and (4) the remaining code set SHALL be indicated by the value of the jobCodedCharSet(7)
Job Monitoring MIB, V0.85 Aug 8, 1997 attribute for the job."
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 REFERENCE
"See section 3.5.2, ''JmJobStringTC' for text generated by the "See section 3.5.2, entitled: 'Text generated by the job
job submitter'." submitter'."
Job Monitoring MIB, V0.86 Sep 19, 1997
SYNTAX OCTET STRING (SIZE (0..63)) 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
skipping to change at page 34, line 4 skipping to change at page 32, line 32
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),
unknown(2), unknown(2),
sptUNIX(3), -- UNIX(tm) sptUNIX(3), -- UNIX
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 sptWindows(11), -- Windows
sptNetWare(33) -- NetWare Job Monitoring MIB, V0.86 Sep 19, 1997
sptNetWare(12) -- NetWare
} }
JmFinishingTC ::= TEXTUAL-CONVENTION JmFinishingTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of finishing operation. "The type of finishing operation.
These values are the same as the enum values of the IPP These values are the same as the enum values of the IPP
'finishings' attribute. See Section 3.6.1.2. 'finishings' attribute. See Section 3.6.1.2.
skipping to change at page 34, line 45 skipping to change at page 33, line 31
unknown(2), unknown(2),
The finishing is unknown. The finishing is unknown.
none(3), none(3),
Perform no finishing. Perform no finishing.
staple(4), staple(4),
Bind the document(s) with one or more staples. The exact Bind the document(s) with one or more staples. The exact
number and placement of the staples is site-defined. number and placement of the staples is site-defined.
stapleTopLeft(5), punch(5),
Place one or more staples on the top left corner of the
document(s).
Job Monitoring MIB, V0.85 Aug 8, 1997
stapleBottomLeft(6),
Place one or more staples on the bottom left corner of the
document(s).
stapleTopRight(7),
Place one or more staples on the top right corner of the
document(s).
stapleBottomRight(8),
Place one or more staples on the bottom right corner of the
document(s).
saddleStitch(9),
Bind the document(s) with one or more staples (wire
stitches) along the middle fold. The exact number and
placement of the stitches is site-defined.
edgeStitch(10),
Bind the document(s) with one or more staples (wire
stitches) along one edge. The exact number and placement of
the staples is site-defined.
punch(11),
This value indicates that holes are required in the finished This value indicates that holes are required in the finished
document. The exact number and placement of the holes is document. The exact number and placement of the holes is
site-defined The punch specification MAY be satisfied (in a site-defined The punch specification MAY be satisfied (in a
site- and implementation-specific manner) either by site- and implementation-specific manner) either by
drilling/punching, or by substituting pre-drilled media. drilling/punching, or by substituting pre-drilled media.
cover(12), cover(6),
This value is specified when it is desired to select a non- This value is specified when it is desired to select a non-
printed (or pre-printed) cover for the document. This does printed (or pre-printed) cover for the document. This does
not supplant the specification of a printed cover (on cover not supplant the specification of a printed cover (on cover
stock medium) by the document itself. stock medium) by the document itself.
bind(13) bind(7)
This value indicates that a binding is to be applied to the This value indicates that a binding is to be applied to the
document; the type and placement of the binding is product- document; the type and placement of the binding is product-
specific." specific."
REFERENCE REFERENCE
Job Monitoring MIB, V0.86 Sep 19, 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),
none(3), none(3),
staple(4), staple(4),
stapleTopLeft(5), punch(5),
stapleBottomLeft(6), cover(6),
Job Monitoring MIB, V0.85 Aug 8, 1997 bind(7)
stapleTopRight(7),
stapleBottomRight(8),
saddleStitch(9),
edgeStitch(10),
punch(11),
cover(12),
bind(13)
} }
JmPrintQualityTC ::= TEXTUAL-CONVENTION JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Print quality settings. "Print quality settings.
These values are the same as the enum values of the IPP 'print- These values are the same as the enum values of the IPP 'print-
quality' attribute. See Section 3.6.1.2." quality' attribute. See Section 3.6.1.2."
REFERENCE REFERENCE
skipping to change at page 36, line 43 skipping to change at page 35, 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 Job Monitoring MIB, V0.86 Sep 19, 1997
Job Monitoring MIB, V0.85 Aug 8, 1997
SIGNED-INTEGER contains the value of
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
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."
skipping to change at page 38, line 4 skipping to change at page 36, 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 Job Monitoring MIB, V0.86 Sep 19, 1997
JmMediumTypeTC ::= TEXTUAL-CONVENTION JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
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.
skipping to change at page 39, line 5 skipping to change at page 37, 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 Job Monitoring MIB, V0.86 Sep 19, 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."
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 {
skipping to change at page 39, line 36 skipping to change at page 37, line 36
multiPartForm(11), multiPartForm(11),
labels(12), labels(12),
multiLayer(13) multiLayer(13)
} }
JmJobSubmissionTypeTC ::= TEXTUAL-CONVENTION JmJobSubmissionTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the format type of a job submission ID. "Identifies the format type of a job submission ID.
The ASCII characters '0-9', 'A-Z', and 'a-z' are assigned in Each job submission ID is a fixed-length, 48-octet printable US-
order giving 62 possible formats. ASCII [US-ASCII] coded character string containing no control
characters, consisting of the following fields:
Each job submission ID is a fixed-length, 48-octet printable
ASCII coded character string, consisting of the following
fields:
octet 1 The format letter. octet 1 The format letter identifying the format.
octets 2-40 A 39-character, ASCII trailing SPACE filled The US-ASCII characters '0-9', 'A-Z', and 'a-z'
are assigned in order giving 62 possible
formats.
octets 2-40 A 39-character, US-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 Job Monitoring MIB, V0.86 Sep 19, 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 agent 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 for the agent. Clients SHALL not use formats that are
reserved to agents. reserved for agents and agents SHALL NOT use formats that are
reserved for clients, in order to reduce conflicts in ID
generation. See the description for which formats are reserved
for clients or for agents.
The format values defined at the time of completion of the Registration of additional formats may be done following the
procedures described in Section 3.6.3.
The format values defined at the time of completion of this
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 for agents.
the client does not supply a job submission ID.
Clients wishing to use a job submission ID that
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 - Clients wishing to use a job submission ID
reserved to the agent for use when the client does that incorporates the job owner, SHALL use format
not supply a job submission ID. '8', not format '0'.
'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.
This format is reserved for clients.
'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
'0'-'9' or 'A' - 'F' (uppercase only). '0'-'9' or 'A' - 'F' (uppercase only).
Most significant octet first. Most significant octet first.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
This format is reserved for clients.
'3' octets 2-40: last 39 bytes of the client URL '3' octets 2-40: last 39 bytes of the client URL
[URI-spec]. [URI-spec].
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
This format is reserved for clients.
'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
This format is reserved for agents.
Job Monitoring MIB, V0.86 Sep 19, 1997
'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
This format is reserved for clients.
'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
This format is reserved for clients.
'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
This format is reserved for clients.
'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
This format is reserved for clients.
'9' octets 2-40: last 39 bytes of the host name with
trailing SPACES that submitted the job to this
server/device using a protocol, such as LPD
[RFC-1179] which includes the host name in the job
submission protocol.
octets 41-48: 8-decimal-digit leading zero
representation of the job id generated by the
by the submitting server (configuration 3)
or the client (configuration 1 and 2), such as in
the LPD protocol.
This format is reserved for clients.
NOTE - the job submission id is only intended to be unique NOTE - the job submission id is only intended to be unique
between a limited set of clients for a limited duration of time, between a limited set of clients for a limited duration of time,
namely, for the life time of the job in the context of the namely, for the life time of the job in the context of the
server or device that is processing the job. Some of the server or device that is processing the job. Some of the
formats include something that is unique per client and a random formats include something that is unique per client and a random
number so that the same job submitted by the same client will number so that the same job submitted by the same client will
have a different job submission id. For other formats, where have a different job submission id. For other formats, where
part of the id is guaranteed to be unique for each client, such part of the id is guaranteed to be unique for each client, such
as the MAC address or URL, a sequential number SHOULD suffice as the MAC address or URL, a sequential number SHOULD suffice
for each client (and may be easier for each client to manage). for each client (and may be easier for each client to manage).
Therefore, the length of the job submission id has been selected Therefore, the length of the job submission id has been selected
to reduce the probability of collision to an extremely low to reduce the probability of collision to an extremely low
number, but is not intended to be an absolute guarantee of number, but is not intended to be an absolute guarantee of
uniqueness. None-the-less, collisions are remotely possible, uniqueness. None-the-less, collisions are remotely possible,
but without bad consequences, since this MIB is intended to be but without bad consequences, since this MIB is intended to be
Job Monitoring MIB, V0.86 Sep 19, 1997
used only for monitoring jobs, not for controlling and managing used only for monitoring jobs, not for controlling and managing
them." them."
REFERENCE REFERENCE
"This is like a type 2 enumeration. See section 3.6.3." "This is like a type 2 enumeration. See section 3.6.3."
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
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, 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 states are called 'inactive'. Jobs reach
one of the three terminal states: completed, canceled, or
aborted, after the jobs have completed all activity, and all MIB
objects and attributes have reached their final values for the
job.
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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
reasons are no longer present. The job's jmJobStateReasons1 reasons are no longer present. The job's jmJobStateReasons1
object and/or jobStateReasonsN (N=2..4) attributes SHALL object and/or jobStateReasonsN (N=2..4) attributes SHALL
indicate why the job is no longer a candidate for indicate why the job is no longer a candidate for
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: One of:
1. The job is using, or is attempting to use, one or more 1. the job is using, or is attempting to use, one or more
document transforms which include (1) purely software purely software processes that are analyzing, creating, or
Job Monitoring MIB, V0.85 Aug 8, 1997 interpreting a PDL, etc.,
processes that are interpreting a PDL, and (2) hardware 2. the job is using, or is attempting to use, one or more
devices that are interpreting a PDL, making marks on a hardware devices that are interpreting a PDL, making marks
medium, and/or performing finishing, such as stapling, etc. on a medium, and/or performing finishing, such as stapling,
etc.,
OR OR
2. (configuration 2) the server has made the job ready for 3. (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
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
additional values in the job's jmJobStateReasons1 object to additional values in the job's jmJobStateReasons1 object to
indicate the progress of the job, such as adding the indicate the progress of the job, such as adding the
jobPrinting value to indicate when the device is actually jobPrinting value to indicate when the device is actually
making marks on a medium. Job Monitoring MIB, V0.86 Sep 19, 1997
making marks on a medium and/or the processingToStopPoint
value to indicate that the server or device is in the
process of canceling or aborting the job.
processingStopped(6), processingStopped(6),
The job has stopped while processing for any number of The job has stopped while processing for any number of
reasons and will return to the processing state as soon as reasons and will return to the processing state as soon as
the reasons are no longer present. the reasons are no longer present.
The job's jmJobStateReasons1 object and/or the job's The job's jmJobStateReasons1 object and/or the job's
jobStateReasonsN (N=2..4) attributes MAY indicate why the jobStateReasonsN (N=2..4) attributes MAY indicate why the
job has stopped processing. For example, if the output job has stopped processing. For example, if the output
device is stopped, the deviceStopped value MAY be included device is stopped, the deviceStopped value MAY be included
in the job's jmJobStateReasons1 object. in the job's jmJobStateReasons1 object.
NOTE - When an output device is stopped, the device usually NOTE - When an output device is stopped, the device usually
indicates its condition in human readable form at the indicates its condition in human readable form at the
device. The management application can obtain more complete device. The management application can obtain more complete
device status remotely by querying the appropriate device device status remotely by querying the appropriate device
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 server or device has
the process of being terminated by the server or device or completed canceling the job and all MIB objects and
(2) has completed terminating. The job's jmJobStateReasons1 attributes have reached their final values for the job.
object SHOULD contain either the canceledByUser or While the server or device is canceling the job, the job's
canceledByOperator value. jmJobStateReasons1 object SHOULD contain the
processingToStopPoint value and one of the canceledByUser,
Job Monitoring MIB, V0.85 Aug 8, 1997 canceledByOperator, or canceledAtDevice values. The
canceledByUser, canceledByOperator, or canceledAtDevice
values remain while the job is in the canceled state.
aborted(8), aborted(8),
The job has been aborted by the system, usually while the The job has been aborted by the system, usually while the
job was in the processing or processingStopped state. job was in the processing or processingStopped state and the
server or device has completed aborting the job and all MIB
objects and attributes have reached their final values for
the job. While the server or device is aborting the job,
the job's jmJobStateReasons1 object MAY contain the
processingToStopPoint and abortedBySystem values. If
implemented, the abortedBySystem value SHALL remain while
the job is in the aborted state.
completed(9) completed(9)
The job has completed successfully or with warnings or The job has completed successfully or with warnings or
errors after processing and all of the media have been errors after processing and all of the media have been
successfully stacked in the appropriate output bin(s). The successfully stacked in the appropriate output bin(s). The
Job Monitoring MIB, V0.86 Sep 19, 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 {
unknown(2), unknown(2),
pending(3), pending(3),
pendingHeld(4), pendingHeld(4),
processing(5), processing(5),
skipping to change at page 45, line 5 skipping to change at page 43, line 44
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.
Values in the range 2**30 to 2**31-1 are reserved for private or
experimental usage. This range corresponds to the same range
reserved in IPP. Implementers are warned that use of such
Job Monitoring MIB, V0.86 Sep 19, 1997
values may conflict with other implementations. Implementers
are encouraged to request registration of enum values following
the procedures in Section 3.6.1.
NOTE: No attribute name exceeds 31 characters. NOTE: No attribute name exceeds 31 characters.
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
skipping to change at page 46, line 4 skipping to change at page 44, line 50
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), JmUTF8StringTC(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 by the server or device during the processing of generated by the server or device during the processing of
Job Monitoring MIB, V0.85 Aug 8, 1997
the job as a simple form of processing log to show progress the job as a simple form of processing log to show progress
and any problems. and any problems.
Job Monitoring MIB, V0.86 Sep 19, 1997
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 jobCodedCharSet(7), CodedCharSet
INTEGER: The MIBenum identifier of the coded character set INTEGER: The MIBenum identifier of the coded character set
that the agent is using to represent coded character set that the agent is using to represent coded character set
objects and attributes of type 'JmJobStringTC'. These coded objects and attributes of type 'JmJobStringTC'. These coded
character set objects and attributes are either: (1) character set objects and attributes are either: (1)
supplied by the job submitting client or (2) defaulted by supplied by the job submitting client or (2) defaulted by
the server or device when omitted by the job submitting the server or device when omitted by the job submitting
skipping to change at page 46, line 33 skipping to change at page 45, line 31
scheme as identified by the jobCodedCharSet attribute. scheme as identified by the jobCodedCharSet attribute.
These MIBenum values are assigned by IANA [IANA-charsets] These MIBenum values are assigned by IANA [IANA-charsets]
when the coded character sets are registered. The coded when the coded character sets are registered. The coded
character set SHALL be one of the ones registered with IANA character set SHALL be one of the ones registered with IANA
[IANA] and the enum value uses the CodedCharSet textual- [IANA] and the enum value uses the CodedCharSet textual-
convention from the Printer MIB. See the JmJobStringTC convention from the Printer MIB. See the JmJobStringTC
textual-convention. textual-convention.
If the agent does not know what coded character set was used If the agent does not know what coded character set was used
by the job submitting client, the agent SHALL return the by the job submitting client, the agent SHALL either (1)
'unknown(2)' value for the jobCodedCharSet attribute for the return the 'unknown(2)' value for the jobCodedCharSet
job. See Section 3.5.2, entitled ''JmJobStringTC' for text attribute or (2) not return the jobCodedCharSet attribute
generated by the job submitter'. for the job. See Section 3.5.2, entitled 'Text generated by
the job submitter'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Identification attributes + Job Identification attributes
+ +
+ The following attributes help an end user, a system + The following attributes help an end user, a system
+ operator, or an accounting program identify a job. + operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobAccountName(21), JmJobStringTC(SIZE(0..63)) jobURI(20), OCTET STRING(SIZE(1..255))
OCTETS: The job's Universal Resource Identifier (URI) [RFC-
1738]. See IPP for example usage.
NOTE - The agent may be able to generate this value on each
SNMP Get operation from smaller values, rather than having
to store the entire URI.
Job Monitoring MIB, V0.86 Sep 19, 1997
If the URI exceeds 255 octets, the agent SHALL truncate from
the beginning (since the end tends to be more unique than
the beginning).
jobAccountName(21), OCTET STRING(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), JmJobStringTC(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.
skipping to change at page 47, line 46 skipping to change at page 47, line 5
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
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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 48, line 46 skipping to change at page 48, line 4
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;
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,
Job Monitoring MIB, V0.86 Sep 19, 1997
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), JmJobStringTC(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.
Job Monitoring MIB, V0.85 Aug 8, 1997
submittingApplicationName(28), JmJobStringTC(SIZE(0..63)) 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), JmJobStringTC(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.
skipping to change at page 49, line 48 skipping to change at page 49, line 5
both. both.
physicalDevice(32), hrDeviceIndex physicalDevice(32), hrDeviceIndex
AND/OR AND/OR
JmUTF8StringTC(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].
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].
Job Monitoring MIB, V0.86 Sep 19, 1997
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.
Job Monitoring MIB, V0.85 Aug 8, 1997
fileName(34), JmJobStringTC(SIZE(0..63)) 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), JmJobStringTC(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.
skipping to change at page 50, line 45 skipping to change at page 50, line 4
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.
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
Job Monitoring MIB, V0.86 Sep 19, 1997
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'
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Parameter attributes + Job Parameter attributes
+ +
+ The following attributes represent input parameters + The following attributes represent input parameters
+ supplied by the submitting client in the job submission + supplied by the submitting client in the job submission
+ protocol. + protocol.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobPriority(50), Integer32(1..100) jobPriority(50), Integer32(1..100)
INTEGER: The priority for scheduling the job. It is used by INTEGER: The priority for scheduling the job. It is used
servers and devices that employ a priority-based scheduling by servers and devices that employ a priority-based
algorithm. scheduling algorithm.
A higher value specifies a higher priority. The value 1 is A higher value specifies a higher priority. The value 1 is
defined to indicate the lowest possible priority (a job defined to indicate the lowest possible priority (a job
which a priority-based scheduling algorithm SHALL pass over which a priority-based scheduling algorithm SHALL pass over
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
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
Job Monitoring MIB, V0.86 Sep 19, 1997
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), JmJobStringTC(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
skipping to change at page 52, line 44 skipping to change at page 52, line 4
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.86 Sep 19, 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.
skipping to change at page 53, line 46 skipping to change at page 53, line 5
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.86 Sep 19, 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)
skipping to change at page 54, line 45 skipping to change at page 54, line 4
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.86 Sep 19, 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 55, line 45 skipping to change at page 55, line 4
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.86 Sep 19, 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 43 skipping to change at page 56, line 5
final value SHALL be equal to the value of the final value SHALL be equal to the value of the
pagesRequested object. For implementations where multiple pagesRequested object. For implementations where multiple
copies are produced by the interpreter by processing the copies are produced by the interpreter by processing the
data for each copy, the final value SHALL be a multiple of data for each copy, the final value SHALL be a multiple of
the value of the pagesRequested object. the value of the pagesRequested object.
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
NOTE - The pagesCompleted object can be used with the NOTE - The pagesCompleted object can be used with the
pagesRequested object to provide an indication of the pagesRequested object to provide an indication of the
relative progress of the job, provided that the relative progress of the job, provided that the
multiplicative factor is taken into account for some multiplicative factor is taken into account for some
implementations of multiple copies. 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.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
skipping to change at page 57, line 42 skipping to change at page 57, line 4
document in the job starts being processed and for each document in the job starts being processed and for each
document copy as it starts being processed. document copy as it starts being processed.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) + Resources attributes (requested and consumed)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to + applications to show an indication of relative usage to
+ users. + users.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.86 Sep 19, 1997
mediumRequested(170), JmMediumTypeTC mediumRequested(170), JmMediumTypeTC
AND/OR AND/OR
JmJobStringTC(SIZE(0..63)) JmJobStringTC(SIZE(0..63))
INTEGER: MULTI-ROW: The type INTEGER: MULTI-ROW: The type
AND/OR AND/OR
OCTETS: 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
Job Monitoring MIB, V0.85 Aug 8, 1997
JmJobStringTC(SIZE(0..63)) 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 has been OCTETS: MULTI-ROW: the name of the medium that has been
consumed so far whether those sheets have been processed on consumed so far whether those sheets have been processed on
one side or on both. one side or on both.
This attribute SHALL have both Integer32 and OCTET STRING This attribute SHALL have both Integer32 and OCTET STRING
(represented as JmJobStringTC) values. (represented as JmJobStringTC) values.
skipping to change at page 58, line 44 skipping to change at page 58, line 4
+ +
+ This section of attributes are ones that are set by the + This section of attributes are ones that are set by the
+ server or device that accepts jobs. Two forms of time are + server or device that accepts jobs. Two forms of time are
+ provided. Each form is represented in a separate attribute. + provided. Each form is represented in a separate attribute.
+ See section 3.1.2 and section 3.1.3 for the + See section 3.1.2 and section 3.1.3 for the
+ conformance requirements for time attribute for agents and + conformance requirements for time attribute for agents and
+ monitoring applications, respectively. The two forms are: + monitoring applications, respectively. The two forms are:
+ +
+ 'DateAndTime' is an 8 or 11 octet binary encoded year, + 'DateAndTime' is an 8 or 11 octet binary encoded year,
+ month, day, hour, minute, second, deci-second with + month, day, hour, minute, second, deci-second with
Job Monitoring MIB, V0.86 Sep 19, 1997
+ 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).
skipping to change at page 59, line 40 skipping to change at page 58, line 49
pendingHeld state, then the value SHALL be '0' or the pendingHeld state, then the value SHALL be '0' or the
attribute SHALL not be present in the table. attribute SHALL not be present in the table.
jobStartedProcessingTime(193), JmTimeStampTC jobStartedProcessingTime(193), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job started processing. OCTETS: the date and time that the job started processing.
jobCompletedTime(194), JmTimeStampTC jobCompletionTime(194), JmTimeStampTC
AND/OR AND/OR
DateAndTime DateAndTime
Job Monitoring MIB, V0.86 Sep 19, 1997
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.
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), jobCodedCharSet(7),
jobURI(20),
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),
deviceNameRequested(30), deviceNameRequested(30),
queueNameRequested(31), queueNameRequested(31),
physicalDevice(32), physicalDevice(32),
numberOfDocuments(33), numberOfDocuments(33),
fileName(34), fileName(34),
documentName(35), documentName(35),
jobComment(36), jobComment(36),
documentFormatIndex(37), documentFormatIndex(37),
documentFormat(38), documentFormat(38),
Job Monitoring MIB, V0.86 Sep 19, 1997
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),
skipping to change at page 61, line 44 skipping to change at page 61, line 4
mediumRequested(170), mediumRequested(170),
mediumConsumed(171), mediumConsumed(171),
colorantRequested(172), colorantRequested(172),
colorantConsumed(173), colorantConsumed(173),
jobSubmissionToServerTime(190), jobSubmissionToServerTime(190),
jobSubmissionTime(191), jobSubmissionTime(191),
jobStartedBeingHeldTime(192), jobStartedBeingHeldTime(192),
jobStartedProcessingTime(193), jobStartedProcessingTime(193),
jobCompletedTime(194), Job Monitoring MIB, V0.86 Sep 19, 1997
jobCompletionTime(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,
corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4,
skipping to change at page 62, line 44 skipping to change at page 62, line 4
other 0x1 other 0x1
The job contains some instructions that are not one of the The job contains some instructions that are not one of the
identified types. identified types.
unknown 0x2 unknown 0x2
The job contains some instructions whose type is unknown to The job contains some instructions whose type is unknown to
the agent. the agent.
print 0x4 print 0x4
Job Monitoring MIB, V0.86 Sep 19, 1997
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
mailList 0x100 mailList 0x100
skipping to change at page 63, line 36 skipping to change at page 63, line 4
"The JmJobStateReasonsNTC (N=1..4) textual-conventions are used "The JmJobStateReasonsNTC (N=1..4) textual-conventions are used
with the jmJobStateReasons1 object and jobStateReasonsN with the jmJobStateReasons1 object and jobStateReasonsN
(N=2..4), respectively, to provide additional information (N=2..4), respectively, to provide additional information
regarding the current jmJobState object value. These values MAY regarding the current jmJobState object value. These values MAY
be used with any job state or states for which the reason makes be used with any job state or states for which the reason makes
sense. sense.
NOTE - While values cannot be added to the jmJobState object NOTE - While values cannot be added to the jmJobState object
without impacting deployed clients that take actions upon without impacting deployed clients that take actions upon
receiving jmJobState values, it is the intent that additional receiving jmJobState values, it is the intent that additional
Job Monitoring MIB, V0.86 Sep 19, 1997
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' 'jobIncoming' value and ending with the 'jobCompletedWithErrors'
value. value.
skipping to change at page 64, line 31 skipping to change at page 63, line 41
unknown 0x2 unknown 0x2
The job state reason is not known to the agent or is The job state reason is not known to the agent or is
indeterminent. indeterminent.
jobIncoming 0x4 jobIncoming 0x4
The job has been accepted by the server or device, but the The job has been accepted by the server or device, but the
server or device is expecting (1) additional operations from server or device is expecting (1) additional operations from
the client to finish creating the job and/or (2) is the client to finish creating the job and/or (2) is
accessing/accepting document data. accessing/accepting document data.
jobOutgoing 0x8 submissionInterrupted 0x8
The job was not completely submitted for some unforeseen
reason, such as: (1) the server has crashed before the job
was closed by the client, (2) the server or the document
transfer method has crashed in some non-recoverable way
before the document data was entirely transferred to the
server, (3) the client crashed or failed to close the job
before the time-out period.
jobOutgoing 0x10
Configuration 2 only: The server is transmitting the job to Configuration 2 only: The server is transmitting the job to
the device. the device.
jobHoldSpecified 0x10 Job Monitoring MIB, V0.86 Sep 19, 1997
jobHoldSpecified 0x20
The value of the job's jobHold(52) attribute is TRUE. The The value of the job's jobHold(52) attribute is TRUE. The
job 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.
jobHoldUntilSpecified 0x20 jobHoldUntilSpecified 0x40
The value of the job's jobHoldUntil(53) attribute specifies The value of the job's jobHoldUntil(53) attribute specifies
a time period that is still in the future. The job SHALL a time period that is still in the future. The job SHALL
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 0x80
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 0x100
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.
deviceStoppedPartly 0x100 deviceStoppedPartly 0x200
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 0x400
The device(s) to which the job is assigned is (are all) The device(s) to which the job is assigned is (are all)
stopped. stopped.
jobPrinting 0x400 jobInterpreting 0x800
The output device is marking media. This attribute is useful The device to which the job is assigned is interpreting the
for servers and output devices which spend a great deal of document data.
time processing when no marking is happening and then want
to show that marking is now happening or when the job is in
the canceled or aborted state, but the marking has not yet
stopped so that impression or sheet counts are still
increasing for the job.
jobCanceledByUser 0x800 jobPrinting 0x1000
The job was canceled by the user, i.e., by an unknown user The output device to which the job is assigned is marking
or by a user whose name is the same as the value of the media. This attribute is useful for servers and output
job's jmJobOwner object. devices which spend a great deal of time processing (1) when
no marking is happening and then want to show that marking
is now happening or (2) when the job is in the process of
being canceled or aborted while the job remains in the
Job Monitoring MIB, V0.86 Sep 19, 1997
jobCanceledByOperator 0x1000 processing state, but the marking has not yet stopped so
The job was canceled by the operator, i.e., by a user whose that impression or sheet counts are still increasing for the
name is different than the value of the job's jmJobOwner job.
object.
abortedBySystem 0x2000 jobCanceledByUser 0x2000
The job was aborted by the system. The job was canceled by the owner of the job, i.e., by a
user whose name is the same as the value of the job's
jmJobOwner object, or by some other authorized end-user,
such as a member of the job owner's security group.
NOTE - When the system puts a job into the 'aborted' job jobCanceledByOperator 0x4000
state, this reason is not needed. This reason is needed The job was canceled by the operator, i.e., by a user who
only when the system aborts a job, but, instead of placing has been authenticated as having operator privileges
the job in the aborted job state, places the job in the (whether local or remote).
pendingHeld state, so that a user or operator can manually
try the job again.
Job Monitoring MIB, V0.85 Aug 8, 1997 jobCanceledAtDevice 0x8000
The job was canceled by an unidentified local user, i.e., a
user at a console at the device.
processingToStopPoint 0x4000 abortedBySystem 0x10000
The job (1) is in the process of being aborted, (2) has been
aborted by the system and placed in the 'aborted' state, or
(3) has been aborted by the system and placed in the
'pendingHeld' state, so that a user or operator can manually
try the job again.
processingToStopPoint 0x20000
The requester has issued an operation to cancel or interrupt The requester has issued an operation to cancel or interrupt
the job or the server/device has aborted the job but the the job or the server/device has aborted the job, but the
server/device is still performing some actions on the job server/device is still performing some actions on the job
until a specified stop point occurs or job until a specified stop point occurs or job
termination/cleanup is completed. termination/cleanup is completed.
This reason is recommended to be used in conjunction with This reason is recommended to be used in conjunction with
the canceled or aborted job state to indicate that the the processing job state to indicate that the server/device
server/device is still performing some actions on the job is still performing some actions on the job while the job
after the job leaves the processing state, so that some of remains in the processing state. After all the job's
the jobs resources consumed counters may still be resources consumed counters have stopped incrementing, the
incrementing while the job is in the canceled or aborted job server/device moves the job from the processing state to the
states. canceled or aborted job states.
jobCompletedSuccessfully 0x8000 serviceOffLine 0x40000
The service or document transform is off-line and accepting
no jobs. All pending jobs are put into the pendingHeld
state. This situation could be true if the service's or
document transform's input is impaired or broken.
Job Monitoring MIB, V0.86 Sep 19, 1997
jobCompletedSuccessfully 0x80000
The job completed successfully. The job completed successfully.
jobCompletedWithWarnings 0x10000 jobCompletedWithWarnings 0x100000
The job completed with warnings. The job completed with warnings.
jobCompletedWithErrors 0x20000 jobCompletedWithErrors 0x200000
The job completed with errors (and possibly warnings too). The job completed with errors (and possibly warnings too).
The following additional job state reasons have been added to The following additional job state reasons have been added to
represent job states that are in ISO DPA[iso-dpa] and other job represent job states that are in ISO DPA[iso-dpa] and other job
submission protocols: submission protocols:
jobPaused 0x40000 jobPaused 0x400000
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 0x80000 jobInterrupted 0x800000
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 0x100000 jobRetained 0x1000000
The job is being retained by the server or device with all The job is being retained by the server or device with all
of 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
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." standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.86 Sep 19, 1997
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
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
skipping to change at page 68, line 4 skipping to change at page 67, line 35
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 jobTransforming 0x10
Indicates that the job was not completely submitted for some The server/device is interpreting document data and
unforeseen reason, such as: (1) the server has crashed producing another electronic representation.
before the job was closed by the client, (2) the server or
the document transfer method has crashed in some non-
recoverable way before the document data was entirely
transferred to the server, (3) the client crashed or failed
to close the job before the time-out period.
maxJobFaultCountExceeded 0x20 maxJobFaultCountExceeded 0x20
The job has faulted several times and has exceeded the The job has faulted several times and has exceeded the
administratively defined fault count limit. administratively defined fault count limit.
devicesNeedAttentionTimeOut 0x40 devicesNeedAttentionTimeOut 0x40
One or more document transforms that the job is using needs One or more document transforms that the job is using needs
human intervention in order for the job to make progress, human intervention in order for the job to make progress,
Job Monitoring MIB, V0.86 Sep 19, 1997
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
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.
skipping to change at page 69, line 4 skipping to change at page 68, line 34
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
which may be dial-up, polled, or queued, and so may be busy which may be dial-up, polled, or queued, and so may be busy
with traffic from other systems, but server was unable to with traffic from other systems, but server was unable to
connect to the device within the site-settable time-out connect to the device within the site-settable time-out
value. value.
transferring 0x2000 transferring 0x2000
The job is being transferred to a down stream server or The job is being transferred to a down stream server or
device. downstream device.
Job Monitoring MIB, V0.86 Sep 19, 1997
queuedInDevice 0x4000 queuedInDevice 0x4000
The job has been queued in a down stream server or device. The server/device has queued the job in a down stream server
or downstream device.
jobCleanup 0x8000 jobQueued 0x8000
The server/device has queued the document data.
jobCleanup 0x10000
The server/device is performing cleanup activity as part of The server/device is performing cleanup activity as part of
ending normal processing. ending normal processing.
jobPasswordWait 0x20000 jobPasswordWait 0x20000
The server/device has selected the job to be next to The server/device has selected the job to be next to
process, 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).
skipping to change at page 70, line 5 skipping to change at page 69, line 39
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
The service/document transform is off-line and accepting no
jobs. All pending jobs are put into the pendingHeld state.
This could be true if its input is impaired or broken.
noSpaceOnServer 0x800000 noSpaceOnServer 0x800000
There is no room on the server to store all of the job. There is no room on the server to store all of the job.
pinRequired 0x1000000 pinRequired 0x1000000
The System Administrator settable device policy is (1) to The System Administrator settable device policy is (1) to
require PINs, and (2) to hold jobs that do not have a pin require PINs, and (2) to hold jobs that do not have a pin
supplied as an input parameter when the job was created. supplied as an input parameter when the job was created.
exceededAccountLimit 0x2000000 exceededAccountLimit 0x2000000
The account for which this job is drawn has exceeded its The account for which this job is drawn has exceeded its
limit. 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.86 Sep 19, 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 71, line 4 skipping to change at page 70, line 32
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.86 Sep 19, 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 72, line 4 skipping to change at page 71, line 29
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 26 skipping to change at page 72, line 4
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
none yet defined. 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.86 Sep 19, 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.86 Sep 19, 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
skipping to change at page 74, line 4 skipping to change at page 74, line 4
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 JmUTF8StringTC(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.86 Sep 19, 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.86 Sep 19, 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 75, line 39 skipping to change at page 75, line 39
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
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 jmJobIDTable and jmJobTable that an entry SHALL remain in the jmJobIDTable and jmJobTable
after processing has completed, i.e., the minimum time in after processing has completed, i.e., the minimum time in
seconds starting when the job enters the completed, canceled, or seconds starting when the job enters the completed, canceled, or
aborted state. aborted state.
Depending on implementation, the value of this object MAY be Configuring this object is implementation-dependent.
either: (1) set by the system administrator by means outside
this specification or (2) fixed by the implementation.
This value SHALL be equal to or greater than the value of This value SHALL be equal to or greater than the value of
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.86 Sep 19, 1997
"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 Configuring this object is implementation-dependent.
either (1) set by the system administrator by means outside this
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 JmUTF8StringTC(SIZE(0..63)) SYNTAX JmUTF8StringTC(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 77, line 4 skipping to change at page 76, line 46
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
SYNTAX SEQUENCE OF JmJobIDEntry SYNTAX SEQUENCE OF JmJobIDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.86 Sep 19, 1997
"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
application already knows the jmGeneralJobSetIndex and the application already knows the jmGeneralJobSetIndex and the
jmJobIndex of the job it is querying, that application NEED NOT jmJobIndex of the job it is querying, that application NEED NOT
use the jmJobIDTable." use the jmJobIDTable."
REFERENCE REFERENCE
"The MANDATORY-GROUP macro specifies that this group is "The MANDATORY-GROUP macro specifies that this group is
skipping to change at page 78, line 4 skipping to change at page 77, line 49
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. Each format are multiple formats for the jmJobSubmissionID. Each format
SHALL be uniquely identified. See the JmJobSubmissionIDTypeTC SHALL be uniquely identified. See the JmJobSubmissionIDTypeTC
textual convention. Each format SHALL be registered using the textual convention. Each format SHALL be registered using the
Job Monitoring MIB, V0.85 Aug 8, 1997
procedures of a type 2 enum. See section 3.6.3 entitled: 'IANA procedures of a type 2 enum. See section 3.6.3 entitled: 'IANA
Registration of Job Submission Id 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
Job Monitoring MIB, V0.86 Sep 19, 1997
(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 that have been reserved to agents and the standard formats that have been reserved for agents and
adding the final 8 octets to distinguish the ID from others adding the final 8 octets to distinguish the ID from others
submitted from the same 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
skipping to change at page 79, line 4 skipping to change at page 78, line 49
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.86 Sep 19, 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.
skipping to change at page 80, line 4 skipping to change at page 79, line 47
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.86 Sep 19, 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 JmJobStringTC(SIZE(0..63)) jmJobOwner JmJobStringTC(SIZE(0..63))
} }
jmJobIndex OBJECT-TYPE jmJobIndex OBJECT-TYPE
skipping to change at page 81, line 4 skipping to change at page 80, line 50
"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
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 }
Job Monitoring MIB, V0.86 Sep 19, 1997
jmJobStateReasons1 OBJECT-TYPE jmJobStateReasons1 OBJECT-TYPE
SYNTAX JmJobStateReasons1TC SYNTAX JmJobStateReasons1TC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Additional information about the job's current state, i.e., "Additional information about the job's current state, i.e.,
information that augments the value of the job's jmJobState information that augments the value of the job's jmJobState
object. object.
Implementation of any reason values is OPTIONAL, but an agent Implementation of any reason values is OPTIONAL, but an agent
SHOULD return any reason information available These values MAY SHOULD return any reason information available These values MAY
be used with any job state or states for which the reason makes be used with any job state or states for which the reason makes
sense. Furthermore, when implemented as with any MIB data, the sense. Since the Job State Reasons will be more dynamic than
agent SHALL return these values when the reason applies and the Job State, it is recommended that a job monitoring
SHALL NOT return them when the reason no longer applies whether application read this object every time jmJobState is read.
the value of the job's jmJobState object changed or not. When When the agent cannot provide a reason for the current state of
the agent cannot provide a reason for the current state of the the job, the the value of the jmJobStateReasons1 object and
job, the agent SHALL set the value of the jmJobStateReasons1 jobStateReasonsN attributes SHALL be 0."
object and jobStateReasonsN attributes to 0."
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 complete being "The number of jobs that are expected to complete processing
processed before this job has completed being processed before this job has completed processing according to the
according to the implementation's queuing algorithm if no other implementation's queuing algorithm, if no other jobs were to be
jobs were to be submitted. In other words, this value is the submitted. In other words, this value is the job's queue
job's queue position. The agent SHALL return a value of 0 for position. The agent SHALL return a value of 0 for this
this attribute when the job is the next job to complete attribute when the job is the next job to complete processing
processing (or has completed 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
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.
Job Monitoring MIB, V0.86 Sep 19, 1997
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
server/device computation is independent of the implementation." server/device computation is independent of the implementation."
::= { jmJobEntry 5 } ::= { jmJobEntry 5 }
jmJobKOctetsProcessed OBJECT-TYPE jmJobKOctetsProcessed OBJECT-TYPE
skipping to change at page 83, line 4 skipping to change at page 82, line 48
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)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.86 Sep 19, 1997
"The total size in number of impressions of the document(s) "The total size in number of impressions of the document(s)
being requested by this job to produce. being requested by this job to produce.
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
server/device computation is independent of the implementation." server/device computation is independent of the implementation."
skipping to change at page 84, line 4 skipping to change at page 83, line 49
reset on each document copy. reset on each document copy.
NOTE - The jmJobImpressionsCompleted object can be used with the NOTE - The jmJobImpressionsCompleted object can be used with the
jmJobImpressionsRequested object to provide an indication of the jmJobImpressionsRequested 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 8 } ::= { jmJobEntry 8 }
jmJobOwner OBJECT-TYPE jmJobOwner OBJECT-TYPE
Job Monitoring MIB, V0.85 Aug 8, 1997
SYNTAX JmJobStringTC(SIZE(0..63)) SYNTAX JmJobStringTC(SIZE(0..63))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Job Monitoring MIB, V0.86 Sep 19, 1997
"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
skipping to change at page 85, line 4 skipping to change at page 84, line 46
"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
Job Monitoring MIB, V0.86 Sep 19, 1997
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
extra index for each type of attribute (jmAttributeTypeIndex) extra index for each type of attribute (jmAttributeTypeIndex)
that a job can have and an additional index that a job can have and an additional index
(jmAttributeInstanceIndex) for those attributes that can have (jmAttributeInstanceIndex) for those attributes that can have
multiple instances per job. The jmAttributeTypeIndex object multiple instances per job. The jmAttributeTypeIndex object
SHALL contain an enum type that indicates the type of attribute SHALL contain an enum type that indicates the type of attribute
skipping to change at page 86, line 4 skipping to change at page 85, line 50
"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
Job Monitoring MIB, V0.86 Sep 19, 1997
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.
skipping to change at page 87, line 4 skipping to change at page 86, line 49
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
Job Monitoring MIB, V0.86 Sep 19, 1997
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:'.
Depending on the enum definition, this object value MAY be an Depending on the enum definition, this object value MAY be an
integer, a counter, an index, or an enum, depending on the integer, a counter, an index, or an enum, depending on the
jmAttributeTypeIndex value. The units of this value are jmAttributeTypeIndex value. The units of this value are
specified in the enum description. specified in the enum description.
skipping to change at page 88, line 4 skipping to change at page 87, line 49
jmAttributeValueAsInteger object for these attributes. jmAttributeValueAsInteger object for these attributes.
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 (1) 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 (2) SHALL return a jmAttributeTable until the value is known or (2) SHALL return a
'-2' 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
Job Monitoring MIB, V0.86 Sep 19, 1997
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), such as 'JmUTF8StringTC', or coded character set string (text), such as 'JmUTF8StringTC', or
a binary octet string, such as 'DateAndTime'. a binary octet string, such as 'DateAndTime'.
skipping to change at page 89, line 4 skipping to change at page 89, line 4
'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.86 Sep 19, 1997
-- Notifications and Trapping -- 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 }
skipping to change at page 90, line 4 skipping to change at page 90, line 4
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.86 Sep 19, 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 91, 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.86 Sep 19, 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 92, 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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 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 93, line 5 skipping to change at page 93, line 5
last received job submission ID for the jmJobSubmissionID index, so that 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 the original user's job submission ID will be used, not the banner page
job ID. 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 Job Monitoring MIB, V0.86 Sep 19, 1997
7. References 7. References
[char-set policy] Harald Avelstrand, "IETF Policy on Character Sets and [char-set policy] Harald Avelstrand, "IETF Policy on Character Sets and
Language", June 1997. Latest draft: <draft-avelstrand-charset-policy- Language", June 1997. Latest draft: <draft-avelstrand-charset-policy-
00.txt> 00.txt>
[GB2312] GB 2312-1980, "Chinese People's Republic of China (PRC) mixed [GB2312] GB 2312-1980, "Chinese People's Republic of China (PRC) mixed
one byte and two byte coded character set" one byte and two byte coded character set"
skipping to change at page 94, line 5 skipping to change at page 94, line 5
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." [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 Job Monitoring MIB, V0.86 Sep 19, 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 1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
Resource Locators (URL)", RFC 1738, December 1994.
[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. `Textual Conventions for Version 2 of the
Simple Network Management 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 [US-ASCII] Coded Character Set - 7-bit American Standard Code for
Information Interchange, ANSI X3.4-1986. Information Interchange, ANSI X3.4-1986.
skipping to change at page 94, line 51 skipping to change at page 95, line 4
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
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
Job Monitoring MIB, V0.86 Sep 19, 1997
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 95, line 47 skipping to change at page 96, line 4
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
Rick Landau - Digital Rick Landau - Digital
Harry Lewis - IBM Harry Lewis - IBM
Pete Loya - HP Pete Loya - HP
Job Monitoring MIB, V0.86 Sep 19, 1997
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.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 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, 53 colorantConsumed, 57
colorantRequested, 53 colorantRequested, 57
--D--- --D---
deviceNameRequested, 44 deviceNameRequested, 48
documentCopiesCompleted, 49 documentCopiesCompleted, 53
documentCopiesRequested, 49 documentCopiesRequested, 53
documentFormat, 46 documentFormat, 50
documentFormatIndex, 46 documentFormatIndex, 49
documentName, 45 documentName, 49
------ ------
fileName, 45 fileName, 49
finishing, 48 finishing, 51
fullColorImpressionsCompleted, 51 fullColorImpressionsCompleted, 54
--H--- --H---
highlightColorImpressionsCompleted, 51 highlightColorImpressionsCompleted, 55
------ ------
impressionsCompletedCurrentCopy, 50 impressionsCompletedCurrentCopy, 54
impressionsInterpreted, 50 impressionsInterpreted, 54
impressionsSentToDevice, 50 impressionsSentToDevice, 54
impressionsSpooled, 50 impressionsSpooled, 54
--J--- --J---
jmAttributeInstanceIndex, 79 jmAttributeInstanceIndex, 86
jmAttributeTypeIndex, 79 jmAttributeTypeIndex, 85
JmAttributeTypeTC, 40 JmAttributeTypeTC, 43
jmAttributeValueAsInteger, 80 jmAttributeValueAsInteger, 86
jmAttributeValueAsOctets, 81 jmAttributeValueAsOctets, 87
JmBooleanTC, 34 JmBooleanTC, 35
Job Monitoring MIB, V0.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 1997
JmFinishingTC, 31 JmFinishingTC, 33
jmGeneralAttributePersistence, 69 jmGeneralAttributePersistence, 75
jmGeneralJobPersistence, 69 jmGeneralJobPersistence, 75
jmGeneralJobSetIndex, 67 jmGeneralJobSetIndex, 73
jmGeneralJobSetName, 70 jmGeneralJobSetName, 76
jmGeneralNewestActiveJobIndex, 68 jmGeneralNewestActiveJobIndex, 75
jmGeneralNumberOfActiveJobs, 68 jmGeneralNumberOfActiveJobs, 74
jmGeneralOldestActiveJobIndex, 68 jmGeneralOldestActiveJobIndex, 74
jmJobIDJobIndex, 72 jmJobIDJobIndex, 78
jmJobIDJobSetIndex, 72 jmJobIDJobSetIndex, 78
jmJobImpressionsCompleted, 76 jmJobImpressionsCompleted, 83
jmJobImpressionsRequested, 76 jmJobImpressionsRequested, 82
jmJobIndex, 73 jmJobIndex, 80
jmJobKOctetsProcessed, 75 jmJobKOctetsProcessed, 82
jmJobKOctetsRequested, 75 jmJobKOctetsRequested, 81
jmJobOwner, 77 jmJobOwner, 83
JmJobServiceTypesTC, 56 JmJobServiceTypesTC, 61
JmJobSourcePlatformTypeTC, 30 JmJobSourcePlatformTypeTC, 32
jmJobState, 74 jmJobState, 80
jmJobStateReasons1, 74 jmJobStateReasons1, 81
JmJobStateReasons1TC, 58 JmJobStateReasons1TC, 62
JmJobStateReasons2TC, 62 JmJobStateReasons2TC, 67
JmJobStateReasons3TC, 65 JmJobStateReasons3TC, 70
JmJobStateReasons4TC, 66 JmJobStateReasons4TC, 71
JmJobStateTC, 38 JmJobStateTC, 40
JmJobStringTC, 29 JmJobStringTC, 31
jmJobSubmissionID, 71 jmJobSubmissionID, 77
JmJobSubmissionTypeTC, 36 JmJobSubmissionTypeTC, 37
JmMediumTypeTC, 34 JmMediumTypeTC, 36
jmNumberOfInterveningJobs, 75 jmNumberOfInterveningJobs, 81
JmPrinterResolutionTC, 33 JmPrinterResolutionTC, 34
JmPrintQualityTC, 32 JmPrintQualityTC, 34
JmTimeStampTC, 30 JmTimeStampTC, 32
JmTonerEconomyTC, 33 JmTonerEconomyTC, 35
JmUTF8StringTC, 29 JmUTF8StringTC, 31
jobAccountName, 42 jobAccountName, 46
jobCodedCharSet, 42 jobCodedCharSet, 45
jobComment, 46 jobComment, 49
jobCompletedTime, 54 jobCompletionTime, 58
jobCopiesCompleted, 49 jobCopiesCompleted, 53
jobCopiesRequested, 49 jobCopiesRequested, 53
jobHold, 47 jobHold, 51
jobHoldUntil, 47 jobHoldUntil, 51
jobKOctetsTransferred, 50 jobKOctetsTransferred, 53
jobName, 43 jobName, 46
jobOriginatingHost, 44 jobOriginatingHost, 48
jobPriority, 47 jobPriority, 50
jobProcessAfterDateAndTime, 47 jobProcessAfterDateAndTime, 50
Job Monitoring MIB, V0.85 Aug 8, 1997 Job Monitoring MIB, V0.86 Sep 19, 1997
jobProcessingCPUTime, 55 jobProcessingCPUTime, 59
jobServiceTypes, 43 jobServiceTypes, 47
jobSourceChannelIndex, 44 jobSourceChannelIndex, 47
jobSourcePlatformType, 44 jobSourcePlatformType, 47
jobStartedBeingHeldTime, 54 jobStartedBeingHeldTime, 58
jobStartedProcessingTime, 54 jobStartedProcessingTime, 58
jobStateReasons2, 41 jobStateReasons2, 44
jobStateReasons3, 41 jobStateReasons3, 44
jobStateReasons4, 41 jobStateReasons4, 44
jobSubmissionTime, 54 jobSubmissionTime, 58
jobSubmissionToServerTime, 54 jobSubmissionToServerTime, 58
jobURI, 45
--M--- --M---
mediumConsumed, 53 mediumConsumed, 57
mediumRequested, 53 mediumRequested, 57
--N--- ------
numberOfDocuments, 45 numberOfDocuments, 49
--O--- ------
other, 41 other, 44
outputBin, 47 outputBin, 51
------ --P---
pagesCompleted, 51 pagesCompleted, 55
pagesCompletedCurrentCopy, 52 pagesCompletedCurrentCopy, 56
pagesRequested, 51 pagesRequested, 55
physicalDevice, 45 physicalDevice, 48
printerResolutionRequested, 48 printerResolutionRequested, 52
printerResolutionUsed, 48 printerResolutionUsed, 52
printQualityRequested, 48 printQualityRequested, 52
printQualityUsed, 48 printQualityUsed, 52
processingMessage, 41 processingMessage, 44
------ --Q---
queueNameRequested, 45 queueNameRequested, 48
------ ------
serverAssignedJobName, 43 serverAssignedJobName, 46
sheetsCompleted, 52 sheetsCompleted, 56
sheetsCompletedCurrentCopy, 52 sheetsCompletedCurrentCopy, 56
sheetsRequested, 52 Job Monitoring MIB, V0.86 Sep 19, 1997
Job Monitoring MIB, V0.85 Aug 8, 1997
sides, 48 sheetsRequested, 56
submittingApplicationName, 44 sides, 51
submittingServerName, 44 submittingApplicationName, 48
submittingServerName, 48
------ --T---
tonerDensityRequested, 49 tonerDensityRequested, 52
tonerDensityUsed, 49 tonerDensityUsed, 52
tonerEcomonyRequested, 48 tonerEcomonyRequested, 52
tonerEcomonyUsed, 48 tonerEcomonyUsed, 52
 End of changes. 323 change blocks. 
750 lines changed or deleted 776 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/