draft-ietf-printmib-job-monitor-03.txt   draft-ietf-printmib-job-monitor-04.txt 
Job Monitoring MIB, V0.83 July 14, 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.
Job Monitoring MIB - V0.83 Job Monitoring MIB - V0.84
<draft-ietf-printmib-job-monitor-03.txt> <draft-ietf-printmib-job-monitor-04.txt>
Expires Jan 14, 1997 Expires Jan 21, 1997
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 41 skipping to change at page 1, line 39
progress." progress."
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet-Draft specifies a set of 18 SNMP MIB objects for (1) This Internet-Draft specifies a small set of read-only SNMP MIB
monitoring the status and progress of print jobs (2) obtaining objects for (1) monitoring the status and progress of print jobs
resource requirements before a job is processed, (3) monitoring (2) obtaining resource requirements before a job is processed, (3)
resource consumption while a job is being processed and (4) monitoring resource consumption while a job is being processed and
collecting resource accounting data after the completion of a job. (4) collecting resource accounting data after the completion of a
This MIB is intended to be implemented (1) in a printer or (2) in a job. This MIB is intended to be implemented (1) in a printer or
server that supports one or more printers. Use of the object set (2) in a server that supports one or more printers. Use of the
is not limited to printing. However, support for services other
than printing is outside the scope of this Job Monitoring MIB.
Job Monitoring MIB, V0.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
Future extensions to this MIB may include, but are not limited to, object set is not limited to printing. However, support for
fax machines and scanners. services other than printing is outside the scope of this Job
Monitoring MIB. Future extensions to this MIB may include, but are
not limited to, fax machines and scanners.
Job Monitoring MIB, V0.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
TABLE OF CONTENTS TABLE OF CONTENTS
1. INTRODUCTION............................................8 1. INTRODUCTION 11
1.1 Types of Information in the MIB ......................8 1.1 Types of Information in the MIB 11
1.2 Types of Job Monitoring Applications ................10 1.2 Types of Job Monitoring Applications 13
2. TERMINOLOGY AND JOB MODEL..............................11 2. TERMINOLOGY AND JOB MODEL 14
2.1 System Configurations for the Job Monitoring MIB 16
2.1.1 Configuration 1 - client-printer 17
2.1.2 Configuration 2 - client-server-printer - agent in the server17
2.1 System Configurations for the Job Monitoring MIB ....13
2.1.1 Configuration 1 - client-printer ................13
2.1.2 Configuration 2 - client-server-printer - agent in the server
......................................................14
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 19
3. MANAGED OBJECT USAGE...................................17 3. MANAGED OBJECT USAGE 21
3.1 Conformance Considerations ..........................17 3.1 Conformance Considerations 21
3.1.1 Conformance Terminology .........................18
3.1.2 Agent Conformance Requirements ..................18
3.1.2.1 MIB II System Group objects..................18
3.1.2.2 MIB II Interface Group objects...............19
3.1.2.3 Printer MIB objects..........................19
3.1.3 Job Monitoring Application Conformance Requirements 19
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 19 3.1.1 Conformance Terminology 21
3.1.2 Agent Conformance Requirements 21
3.1.2.1 MIB II System Group objects 22
3.1.2.2 MIB II Interface Group objects 22
3.1.2.3 Printer MIB objects 22
3.1.3 Job Monitoring Application Conformance Requirements 22
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 23
3.3 The Attribute Mechanism 24
3.3.1 Conformance of Attribute Implementation 25
3.3 The Attribute Mechanism .............................21
3.3.1 Conformance of Attribute Implementation .........22
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and
Attributes ............................................23 Attributes 25
3.3.3 Data Sub-types and Attribute Naming Conventions .23
3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 23
3.3.5 Requested Attributes ............................24
3.3.6 Consumption Attributes ..........................24
3.3.7 Index Value Attributes ..........................24
3.4 Job Identification ..................................25 Job Monitoring MIB, V0.84 July 21, 1997
3.5 Internationalization Considerations .................25 3.3.3 Data Sub-types and Attribute Naming Conventions 26
Job Monitoring MIB, V0.83 July 14, 1997
3.6 IANA Considerations .................................26 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 27
3.6.1 IANA Registration of enums ......................26
3.6.1.1 Type 1 enumerations..........................26
3.6.1.2 Type 2 enumerations..........................27
3.6.1.3 Type 3 enumeration...........................27
3.6.2 IANA Registration of type 2 bit values ..........27
3.6.3 IANA Registration of Job Submission Id Formats ..28
3.6.4 IANA Registration of MIME types/sub-types for document-formats
......................................................28
3.7 Security Considerations .............................28 3.3.5 Requested Attributes 27
3.7.1 Read-Write objects ..............................28
3.7.2 Read-Only Objects In Other User's Jobs ..........28
3.8 Values for Objects ..................................22 3.3.6 Consumption Attributes 28
3.9 Notification-s ......................................29 3.3.7 Index Value Attributes 28
4. MIB SPECIFICATION......................................29 3.4 Job Identification 28
Textual conventions for this MIB module .................31 3.5 Internationalization Considerations 29
JmTimeStampTC - simple time in seconds ................31
JmJobSourcePlatformTypeTC - operating system platform definitions 31
JmFinishingTC - device finishing definitions ..........32
JmPrintQualityTC - print quality ......................34
JmPrinterResolutionTC - printer resolution ............34
JmTonerEconomyTC - toner economy setting ..............36
JmBooleanTC - Boolean value ...........................36
JmMediumTypeTC - medium type definitions ..............36
JmJobSubmissionIDTypeTC - job submission ID type definitions 38
JmJobStateTC - job state definitions ..................40
JmAttributeTypeTC - attribute type definitions ........43
other (Int32(-2..) and/or Octets63) ..............43
Job State attributes.................................44
jobStateReasons2 (JmJobStateReasons2TC) ..........44
jobStateReasons3 (JmJobStateReasons3TC) ..........44
jobStateReasons4 (JmJobStateReasons4TC) ..........44
processingMessage (Octets63) .....................44
Job Identification attributes........................44
jobAccountName (Octets63) ........................45
serverAssignedJobName (Octets63) .................45
jobName (Octets63) ...............................45
jobServiceTypes (JmJobServiceTypesTC) ............46
jobSourceChannelIndex (Int32(0..)) ...............46
jobSourcePlatformType (JmJobSourcePlatformTypeTC) 46
submittingServerName (Octets63) ..................47
submittingApplicationName (Octets63) .............47
Job Monitoring MIB, V0.83 July 14, 1997
jobOriginatingHost (Octets63) ....................47 3.6 IANA Considerations 29
deviceNameRequested (Octets63) ...................47
queueNameRequested (Octets63) ....................47
physicalDevice (hrDeviceIndex and/or Octets63) ...48
numberOfDocuments (Int32(-2..)) ..................48
fileName (Octets63) ..............................48
documentName (Octets63) ..........................48
jobComment (Octets63) ............................48
documentFormatIndex (Int32(0..)) .................49
documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 49
Job Parameter attributes.............................49
jobPriority (Int32(1..100)) ......................50
jobProcessAfterDateAndTime (DateAndTime) .........50
jobHold (JmBooleanTC) ............................50
jobHoldUntil (Octets63) ..........................50
outputBin (Int32(0..) and/or Octets63) ...........51
sides (Int32(-2..2)) .............................51
finishing (JmFinishingTC) ........................51
Image Quality attributes (requested and used)........51
printQualityRequested (JmPrintQualityTC) .........51
printQualityUsed (JmPrintQualityTC) ..............51
printerResolutionRequested (JmPrinterResolutionTC)51
printerResolutionUsed (JmPrinterResolutionTC) ....52
tonerEcomonyRequested (JmTonerEconomyTC) .........52
tonerEcomonyUsed (JmTonerEconomyTC) ..............52
tonerDensityRequested (Int32(-2..100)) ...........52
tonerDensityUsed (Int32(-2..100)) ................52
Job Progress attributes (requested and consumed).....52
jobCopiesRequested (Int32(-2..)) .................53
jobCopiesCompleted (Int32(-2..)) .................53
documentCopiesRequested (Int32(-2..)) ............53
documentCopiesCompleted (Int32(-2..)) ............53
jobKOctetsTransferred (Int32(-2..)) ..............53
Impression attributes (requested and consumed).......54
impressionsSpooled (Int32(-2..)) .................54
impressionsSentToDevice (Int32(-2..)) ............54
impressionsInterpreted (Int32(-2..)) .............54
impressionsCompletedCurrentCopy (Int32(-2..)) ....54
fullColorImpressionsCompleted (Int32(-2..)) ......55
highlightColorImpressionsCompleted (Int32(-2..)) .55
Page attributes (requested and consumed).............55
pagesRequested (Int32(-2..)) .....................55
pagesCompleted (Int32(-2..)) .....................55
pagesCompletedCurrentCopy (Int32(-2..)) ..........56
Sheet attributes (requested and consumed)............56
sheetsRequested (Int32(-2..)) ....................56
sheetsCompleted (Int32(-2..)) ....................56
sheetsCompletedCurrentCopy (Int32(-2..)) .........56
Job Monitoring MIB, V0.83 July 14, 1997
Resource attributes (requested and consumed).........56 3.6.1 IANA Registration of enums 29
mediumRequested (JmMediumTypeTC and/or Octets63) .57
mediumConsumed (Octets63) ........................57
colorantRequested (Int32(-2..) and/or Octets63) ..57
colorantConsumed (Int32(-2..) and/or Octets63) ...57
Time attributes (set by server or device)............57
jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 58
jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 58
jobStartedBeingHeldTime (JmTimeStampTC and/or DateAndTime) 58
jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 59
jobCompletedTime (JmTimeStampTC and/or DateAndTime)59
jobProcessingCPUTime (Int32(-2..)) ...............59
JmJobServiceTypesTC - bit encoded job service type definitions 61
JmJobStateReasons1TC - additional information about job states 63
JmJobStateReasons2TC - More additional information about job states
......................................................66
JmJobStateReasons3TC - More additional information about job states
......................................................70
JmJobStateReasons4TC - More additional information about job states
......................................................71
The General Group (MANDATORY) ...........................73 3.6.1.1 Type 1 enumerations 30
jmGeneralJobSetIndex (Int32(1..32767)) ..............73
jmGeneralNumberOfActiveJobs (Int32(0..)) ............74
jmGeneralOldestActiveJobIndex (Int32(0..)) ..........74
jmGeneralNewestActiveJobIndex (Int32(0..)) ..........75
jmGeneralJobPersistence (Int32(15..)) ...............75
jmGeneralAttributePersistence (Int32(15..)) .........76
jmGeneralJobSetName (Octets63) ......................76
The Job ID Group (MANDATORY) ............................76 3.6.1.2 Type 2 enumerations 30
jmJobSubmissionID (OCTET STRING(SIZE(48))) ..........77
jmJobIDJobSetIndex (Int32(1..32767)) ................78
jmJobIDJobIndex (Int32(1..)) ........................79
The Job Group (MANDATORY) ...............................79 3.6.1.3 Type 3 enumeration 31
jmJobIndex (Int32(1..)) .............................80
jmJobState (JmJobStateTC) ...........................80
jmJobStateReasons1 (JmJobStateReasons1TC) ...........81
jmNumberOfInterveningJobs (Int32(-2..)) .............81
jmJobKOctetsRequested (Int32(-2..)) .................82
jmJobKOctetsProcessed (Int32(-2..)) .................82
jmJobImpressionsRequested (Int32(-2..)) .............83
jmJobImpressionsCompleted (Int32(-2..)) .............83
jmJobOwner (Octets63) ...............................83
The Attribute Group (MANDATORY) .........................84 3.6.2 IANA Registration of type 2 bit values 31
jmAttributeTypeIndex (JmAttributeTypeTC) ............85
Job Monitoring MIB, V0.83 July 14, 1997
jmAttributeInstanceIndex (Int32(1..32767)) ..........86 3.6.3 IANA Registration of Job Submission Id Formats 31
jmAttributeValueAsInteger (Int32(-2..)) .............86
jmAttributeValueAsOctets (Octets63) .................87
5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE...........91 3.6.4 IANA Registration of MIME types/sub-types for document-formats31
3.7 Security Considerations 32
3.7.1 Read-Write objects 32
3.7.2 Read-Only Objects In Other User's Jobs 32
3.8 Notifications 32
4. MIB SPECIFICATION 32
Textual conventions for this MIB module 34
JmTimeStampTC - simple time in seconds 34
JmJobSourcePlatformTypeTC - operating system platform definitions 34
JmFinishingTC - device finishing definitions 35
Job Monitoring MIB, V0.84 July 21, 1997
JmPrintQualityTC - print quality 37
JmPrinterResolutionTC - printer resolution 37
JmTonerEconomyTC - toner economy setting 38
JmBooleanTC - Boolean value 38
JmMediumTypeTC - medium type definitions 39
JmJobSubmissionIDTypeTC - job submission ID type definitions 40
JmJobStateTC - job state definitions 42
JmAttributeTypeTC - attribute type definitions 45
other (Int32(-2..) and/or Octets63) 46
Job State attributes 46
jobStateReasons2 (JmJobStateReasons2TC) 46
jobStateReasons3 (JmJobStateReasons3TC) 46
jobStateReasons4 (JmJobStateReasons4TC) 47
processingMessage (Octets63) 47
Job Identification attributes 47
jobAccountName (Octets63) 47
serverAssignedJobName (Octets63) 47
jobName (Octets63) 48
jobServiceTypes (JmJobServiceTypesTC) 48
jobSourceChannelIndex (Int32(0..)) 49
jobSourcePlatformType (JmJobSourcePlatformTypeTC) 49
submittingServerName (Octets63) 49
submittingApplicationName (Octets63) 49
jobOriginatingHost (Octets63) 50
Job Monitoring MIB, V0.84 July 21, 1997
deviceNameRequested (Octets63) 50
queueNameRequested (Octets63) 50
physicalDevice (hrDeviceIndex and/or Octets63) 50
numberOfDocuments (Int32(-2..)) 50
fileName (Octets63) 51
documentName (Octets63) 51
jobComment (Octets63) 51
documentFormatIndex (Int32(0..)) 51
documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 52
Job Parameter attributes 52
jobPriority (Int32(1..100)) 52
jobProcessAfterDateAndTime (DateAndTime) 52
jobHold (JmBooleanTC) 53
jobHoldUntil (Octets63) 53
outputBin (Int32(0..) and/or Octets63) 53
sides (Int32(-2..2)) 53
finishing (JmFinishingTC) 53
Image Quality attributes (requested and used) 54
printQualityRequested (JmPrintQualityTC) 54
printQualityUsed (JmPrintQualityTC) 54
printerResolutionRequested (JmPrinterResolutionTC) 54
printerResolutionUsed (JmPrinterResolutionTC) 54
tonerEcomonyRequested (JmTonerEconomyTC) 54
tonerEcomonyUsed (JmTonerEconomyTC) 54
Job Monitoring MIB, V0.84 July 21, 1997
tonerDensityRequested (Int32(-2..100)) 55
tonerDensityUsed (Int32(-2..100)) 55
Job Progress attributes (requested and consumed) 55
jobCopiesRequested (Int32(-2..)) 55
jobCopiesCompleted (Int32(-2..)) 55
documentCopiesRequested (Int32(-2..)) 55
documentCopiesCompleted (Int32(-2..)) 56
jobKOctetsTransferred (Int32(-2..)) 56
Impression attributes (requested and consumed) 56
impressionsSpooled (Int32(-2..)) 57
impressionsSentToDevice (Int32(-2..)) 57
impressionsInterpreted (Int32(-2..)) 57
impressionsCompletedCurrentCopy (Int32(-2..)) 57
fullColorImpressionsCompleted (Int32(-2..)) 57
highlightColorImpressionsCompleted (Int32(-2..)) 57
Page attributes (requested and consumed) 58
pagesRequested (Int32(-2..)) 58
pagesCompleted (Int32(-2..)) 58
pagesCompletedCurrentCopy (Int32(-2..)) 58
Sheet attributes (requested and consumed) 58
sheetsRequested (Int32(-2..)) 58
sheetsCompleted (Int32(-2..)) 59
sheetsCompletedCurrentCopy (Int32(-2..)) 59
Resource attributes (requested and consumed) 59
Job Monitoring MIB, V0.84 July 21, 1997
mediumRequested (JmMediumTypeTC and/or Octets63) 59
mediumConsumed (Int32(-2..) and/or Octets63) 59
colorantRequested (Int32(-2..) and/or Octets63) 60
colorantConsumed (Int32(-2..) and/or Octets63) 60
Time attributes (set by server or device) 60
jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 61
jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 61
jobStartedBeingHeldTime (JmTimeStampTC) 61
jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 61
jobCompletedTime (JmTimeStampTC and/or DateAndTime) 61
jobProcessingCPUTime (Int32(-2..)) 62
JmJobServiceTypesTC - bit encoded job service type definitions 64
JmJobStateReasons1TC - additional information about job states 65
JmJobStateReasons2TC - More additional information about job states69
JmJobStateReasons3TC - More additional information about job states73
JmJobStateReasons4TC - More additional information about job states74
The General Group (MANDATORY) 75
jmGeneralJobSetIndex (Int32(1..32767)) 75
jmGeneralNumberOfActiveJobs (Int32(0..)) 76
jmGeneralOldestActiveJobIndex (Int32(0..)) 76
jmGeneralNewestActiveJobIndex (Int32(0..)) 77
jmGeneralJobPersistence (Int32(15..)) 77
jmGeneralAttributePersistence (Int32(15..)) 78
jmGeneralJobSetName (Octets63) 78
Job Monitoring MIB, V0.84 July 21, 1997
The Job ID Group (MANDATORY) 78
jmJobSubmissionID (OCTET STRING(SIZE(48))) 79
jmJobIDJobSetIndex (Int32(1..32767)) 80
jmJobIDJobIndex (Int32(1..)) 81
The Job Group (MANDATORY) 81
jmJobIndex (Int32(1..)) 82
jmJobState (JmJobStateTC) 82
jmJobStateReasons1 (JmJobStateReasons1TC) 83
jmNumberOfInterveningJobs (Int32(-2..)) 83
jmJobKOctetsRequested (Int32(-2..)) 84
jmJobKOctetsProcessed (Int32(-2..)) 84
jmJobImpressionsRequested (Int32(-2..)) 85
jmJobImpressionsCompleted (Int32(-2..)) 85
jmJobOwner (Octets63) 85
The Attribute Group (MANDATORY) 86
jmAttributeTypeIndex (JmAttributeTypeTC) 87
jmAttributeInstanceIndex (Int32(1..32767)) 88
jmAttributeValueAsInteger (Int32(-2..)) 88
jmAttributeValueAsOctets (Octets63) 89
5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 93
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 94
6.1 Hewlett-Packard's Printer Job Language (PJL) ........92 6.1 Hewlett-Packard's Printer Job Language (PJL) 94
6.2 ISO DPA .............................................92 6.2 ISO DPA 94
7. REFERENCES.............................................92 Job Monitoring MIB, V0.84 July 21, 1997
8. AUTHOR'S ADDRESSES.....................................93 7. REFERENCES 94
9. INDEX..................................................96 8. AUTHOR'S ADDRESSES 95
Job Monitoring MIB, V0.83 July 14, 1997
9. INDEX 98
Job Monitoring MIB, V0.84 July 21, 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
processing of the print job. This MIB applies to printers with and processing of the print job. This MIB applies to printers with and
without spooling capabilities. This MIB is designed to be compatible without spooling capabilities. This MIB is designed to be compatible
with most current commonly-used job submission protocols. In most with most current commonly-used job submission protocols. In most
environments that support high function job submission/job control environments that support high function job submission/job control
protocols, like ISO DPA[iso-dpa], those protocols would be used to protocols, like ISO DPA[iso-dpa], those protocols would be used to
monitor and manage print jobs rather than using the Job Monitoring MIB. monitor and manage print jobs rather than using the Job Monitoring MIB.
The Job Monitoring MIB consists of a 7-object General Group, a 2-object The Job Monitoring MIB consists of a General Group, a Job Submission ID
Job Submission ID Group, a 7-object Job Group, and a 2-object Attribute Group, a Job Group, and an Attribute Group. Each group is a table. All
Group. Each group is a table. The General Group contains general accessible objects are read-only. The General Group contains general
information that applies to all jobs in a job set. The Job Submission information that applies to all jobs in a job set. The Job Submission
ID table maps the job submission ID that the client uses to identify a ID table maps the job submission ID that the client uses to identify a
job to the jmJobIndex that the Job Monitoring Agent uses to identify job to the jmJobIndex that the Job Monitoring Agent uses to identify
jobs in the Job and Attribute tables. The Job table contains the jobs in the Job and Attribute tables. The Job table contains the
MANDATORY integer job state and status objects. The Attribute table MANDATORY integer job state and status objects. The Attribute table
consists of multiple entries per job that specify (1) job and document consists of multiple entries per job that specify (1) job and document
identification and parameters, (2) requested resources, and (3) identification and parameters, (2) requested resources, and (3)
consumed resources during and after job processing/printing. Sixty five consumed resources during and after job processing/printing. Sixty five
job attributes are defined as textual conventions that an agent SHALL job attributes are defined as textual conventions that an agent SHALL
return if the server or device implements the functionality so return if the server or device implements the functionality so
skipping to change at page 9, line 5 skipping to change at page 12, 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.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 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 13, line 5
Provide information to allow the prediction of consumable usage Provide information to allow the prediction of consumable usage
and resource need. and resource need.
The MIB supports printers that can contain more than one job at a time, The MIB supports printers that can contain more than one job at a time,
but still be usable for low end printers that only contain a single job but still be usable for low end printers that only contain a single job
at a time. In particular, the MIB supports the needs of Windows and at a time. In particular, the MIB supports the needs of Windows and
other PC environments for managing low-end networked devices without other PC environments for managing low-end networked devices without
unnecessary overhead or complexity, while also providing for higher end unnecessary overhead or complexity, while also providing for higher end
systems and devices. systems and devices.
Job Monitoring MIB, V0.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
1.2 Types of Job Monitoring Applications 1.2 Types of Job Monitoring Applications
The Job Monitoring MIB is designed for the following types of monitoring The Job Monitoring MIB is designed for the following types of monitoring
applications: applications:
1.Monitor a single job starting when the job is submitted and 1.Monitor a single job starting when the job is submitted and ending
finishing a defined period after the job completes. The Job a defined period after the job completes. The Job Submission ID
Submission ID table provides the map to find the specific job to be table provides the map to find the specific job to be monitored.
monitored.
2.Monitor all 'active' jobs in a queue, which this specification 2.Monitor all 'active' jobs in a queue, which this specification
generalizes to a "job set". End users may use such a program when generalizes to a "job set". End users may use such a program when
selecting a least busy printer, so the MIB is designed for such a selecting a least busy printer, so the MIB is designed for such a
program to start up quickly and find the information needed quickly program to start up quickly and find the information needed quickly
without having to read all (completed) jobs in order to find the without having to read all (completed) jobs in order to find the
active jobs. System operators may also use such a program, in active jobs. System operators may also use such a program, in
which case it would be running for a long period of time and may which case it would be running for a long period of time and may
also be interested in the jobs that have completed. Finally such a also be interested in the jobs that have completed. Finally such a
program may be used to provide an enhanced console and logging program may be used to provide an enhanced console and logging
skipping to change at page 11, line 5 skipping to change at page 14, line 5
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.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 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 we call a job in this specification and the term job session for what is called a job in this specification and the term
to mean what we call a document in this specification. PJL systems job to mean what is called a document in this specification. PJL
use the term job to mean what we call a job in this specification. systems use the term job to mean what is called a job in this
PJL also supports multiple documents per job, but does not support specification. PJL also supports multiple documents per job, but does
specifying per-document attributes independently for each document. 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.
skipping to change at page 11, line 54 skipping to change at page 15, line 4
spoolers, servers, or printers and other devices, depending on the spoolers, servers, or printers and other devices, depending on the
configuration, using any job submission protocol. configuration, using any job submission protocol.
Server: a network entity that accepts jobs from clients and in turn Server: a network entity that accepts jobs from clients and in turn
submits the jobs to printers and other devices. A server MAY be a submits the jobs to printers and other devices. A server MAY be a
printer supervisor control program, or a print spooler. printer supervisor control program, or a print spooler.
Device: a hardware entity that (1) interfaces to humans in human Device: a hardware entity that (1) interfaces to humans in human
perceptible means, such as produces marks on paper, scans marks on paper perceptible means, such as produces marks on paper, scans marks on paper
to produce an electronic representations, or writes CD-ROMs or (2) to produce an electronic representations, or writes CD-ROMs or (2)
interfaces to a network, such as sends FAX data to another FAX device.
Job Monitoring MIB, V0.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
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.
skipping to change at page 12, line 44 skipping to change at page 15, line 47
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: is a person that uses a client or a monitor. User: a person that uses a client or a monitor.
End User: is a user that uses a client to submit a print job. End User: a user that uses a client to submit a print job.
System Operator: is a user that uses a monitor to monitor the system System Operator: a user that uses a monitor to monitor the system and
and carries out tasks to keep the system running. carries out tasks to keep the system running.
System Administrator: is a user that specifies policy for the system. System Administrator: a user that specifies policy for the system.
Job Instruction: is an instruction specifying how, when, or where the Job Monitoring MIB, V0.84 July 21, 1997
job is to be processed. Job instructions MAY be passed in the job
Job Monitoring MIB, V0.83 July 14, 1997
Job Instruction: an instruction specifying how, when, or where 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: is 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: is a name, value-pair that specifies an SNMP Information Object: a name, value-pair that specifies an action, a
action, a status, or a condition in an SNMP MIB. Objects are identified status, or a condition in an SNMP MIB. Objects are identified in SNMP
in SNMP by an OBJECT IDENTIFIER. by an OBJECT IDENTIFIER.
Attribute: is 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): is (1) identifying jobs within the serial Job Monitoring (using SNMP): the activity of a management application
streams of data being processed by the server, printer or other devices, of accessing the MIB and (1) identifying jobs in the job tables being
(2) creating "rows" in the job table for each job, and (3) recording processed by the server, printer or other devices, and (2) displaying
information, known by the agent, about the processing of the job in that information to the user about the processing of the job.
"row".
Job Accounting: is recording what happens to the job during the Job Accounting: the activity of a management application of accessing
processing and printing of the job. the MIB and recording what happens to the job during and after the
processing of the job.
2.1 System Configurations for the Job Monitoring MIB 2.1 System Configurations for the Job Monitoring MIB
This section enumerates the three configurations in which the Job This section enumerates the three configurations in which the Job
Monitoring MIB is intended to be used. To simplify the pictures, the Monitoring MIB is intended to be used. To simplify the pictures, the
devices are shown as printers. See Goals section. devices are shown as printers. See Goals section.
The diagram in the Printer MIB[print-mib] entitled: "One Printer's View The diagram in the Printer MIB[print-mib] entitled: "One Printer's View
of the Network" is assumed for this MIB as well. Please refer to that of the Network" is assumed for this MIB as well. Please refer to that
diagram to aid in understanding the following system configurations. diagram to aid in understanding the following system configurations.
Job Monitoring MIB, V0.84 July 21, 1997
2.1.1 Configuration 1 - client-printer 2.1.1 Configuration 1 - client-printer
In the client-printer configuration, the client(s) submit jobs directly In the client-printer configuration, the client(s) submit jobs directly
to the printer, either by some direct connect, or by network connection. to the printer, either by some direct connect, or by network connection.
Job Monitoring MIB, V0.83 July 14, 1997
The client-printer configuration can accommodate multiple job submitting
clients in either of two ways:
1.if each client relinquishes control of the Print Job Delivery
Channel after each job (or after a number of jobs)
2.if the printer supports more than one Print Job Delivery Channel
The job submitting client and/or monitoring application monitor jobs by The job submitting client and/or monitoring application monitor jobs by
communicating directly with an agent that is part of the printer. The communicating directly with an agent that is part of the printer. The
agent in the Printer SHALL keep the job in the Job Monitoring MIB as agent in the Printer SHALL keep the job in the Job Monitoring MIB as
long as the job is in the Printer, plus a defined time period after the long as the job is in the Printer, plus a defined time period after the
job enters the completed state in which accounting programs can copy out job enters the completed state in which accounting programs can copy out
the accounting data from the Job Monitoring MIB. the accounting data from the Job Monitoring MIB.
all end-user ######## SNMP query all end-user ######## SNMP query
+-------+ +--------+ ---- job submission +-------+ +--------+ ---- job submission
|monitor| | client | |monitor| | client |
skipping to change at page 14, line 41 skipping to change at page 17, line 38
| +-------+ | | | +-------+ | |
| PRINTER <--------+ | PRINTER <--------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 2-1 - Configuration 1 - client-printer - agent in the printer Figure 2-1 - Configuration 1 - client-printer - agent in the printer
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 2-1): relationships (not shown in Figure 2-1):
1.Multiple clients MAY submit jobs to a printer. 1.Multiple clients MAY submit jobs to a printer.
2.Multiple clients MAY monitor a printer. 2.Multiple clients MAY monitor a printer.
3.Multiple monitors MAY monitor a printer. 3.Multiple monitors MAY monitor a printer.
4.A client MAY submit jobs to multiple printers. 4.A client MAY submit jobs to multiple printers.
5.A monitor MAY monitor multiple printers. 5.A monitor MAY monitor multiple printers.
2.1.2 Configuration 2 - client-server-printer - agent in the server 2.1.2 Configuration 2 - client-server-printer - agent in the server
In the client-server-printer configuration 2, the client(s) submit jobs In the client-server-printer configuration 2, the client(s) submit jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
Job Monitoring MIB, V0.84 July 21, 1997
the printer. While configuration 2 is included, the design center for the printer. While configuration 2 is included, the design center for
this MIB is configurations 1 and 3, this MIB is configurations 1 and 3,
Job Monitoring MIB, V0.83 July 14, 1997
The job submitting client and/or monitoring application monitor job by The job submitting client and/or monitoring application monitor job by
communicating directly with: communicating directly with:
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
skipping to change at page 15, line 50 skipping to change at page 19, line 5
| | | | | |
| | | | | |
| 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.84 July 21, 1997
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 2-2): relationships (not shown in Figure 2-2):
1.Multiple clients MAY submit jobs to a server.
Job Monitoring MIB, V0.83 July 14, 1997 1.Multiple clients MAY submit jobs to a server.
2.Multiple clients MAY monitor a server. 2.Multiple clients MAY monitor a server.
3.Multiple monitors MAY monitor a server. 3.Multiple monitors MAY monitor a server.
4.A client MAY submit jobs to multiple servers. 4.A client MAY submit jobs to multiple servers.
5.A monitor MAY monitor multiple servers. 5.A monitor MAY monitor multiple servers.
6.Multiple servers MAY submit jobs to a printer. 6.Multiple servers MAY submit jobs to a printer.
7.Multiple servers MAY control a printer. 7.Multiple servers MAY control a printer.
2.1.3 Configuration 3 - client-server-printer - client monitors printer 2.1.3 Configuration 3 - client-server-printer - client monitors printer
agent and server agent and server
In the client-server-printer configuration 3, the client(s) submit jobs In the client-server-printer configuration 3, the client(s) submit jobs
to an intermediate server by some network connection, not directly to to an intermediate server by some network connection, not directly to
the printer. That server does not contain a Job Monitoring MIB and the printer. That server does not contain a Job Monitoring MIB and
agent. agent.
skipping to change at page 16, line 44 skipping to change at page 20, line 4
In configuration 3, the agent (in the printer) SHALL keep the values of In configuration 3, the agent (in the printer) SHALL keep the values of
the objects in the Job Monitoring MIB that the agent implements updated the objects in the Job Monitoring MIB that the agent implements updated
for a job that the server has submitted to the printer. The agent SHALL for a job that the server has submitted to the printer. The agent SHALL
obtain information about the jobs submitted to the printer from the obtain information about the jobs submitted to the printer from the
server (either in the job submission protocol, in the document data, or server (either in the job submission protocol, in the document data, or
by direct query of the server), in order to populate some of the objects by direct query of the server), in order to populate some of the objects
the Job Monitoring MIB in the printer. The agent in the printer SHALL the Job Monitoring MIB in the printer. The agent in the printer SHALL
keep the job in the Job Monitoring MIB as long as the job is in the keep the job in the Job Monitoring MIB as long as the job is in the
Printer, and longer in order to implement the completed state in which Printer, and longer in order to implement the completed state in which
Job Monitoring MIB, V0.84 July 21, 1997
monitoring programs can copy out the accounting data from the Job monitoring programs can copy out the accounting data from the Job
Monitoring MIB. Monitoring MIB.
Job Monitoring MIB, V0.83 July 14, 1997
all end-user all end-user
+-------+ +----------+ +-------+ +----------+
|monitor| | client | ######## SNMP query |monitor| | client | ######## SNMP query
+---+---* +---*----+-+ **** non-SNMP query +---+---* +---*----+-+ **** non-SNMP query
# * * | ---- job submission # * * | ---- job submission
# * * | # * * |
# * * | # * * |
# *=====v====v==+ # *=====v====v==+
# | | # | |
# | server | # | server |
skipping to change at page 17, line 35 skipping to change at page 20, line 38
| PRINTER <---------+ | PRINTER <---------+
| | Print Job Delivery Channel | | Print Job Delivery Channel
| | | |
+=============+ +=============+
Figure 2-3 - Configuration 3 - client-server-printer - client monitors Figure 2-3 - Configuration 3 - client-server-printer - client monitors
printer agent and server printer agent and server
The Job Monitoring MIB is designed to support the following The Job Monitoring MIB is designed to support the following
relationships (not shown in Figure 2-3): relationships (not shown in Figure 2-3):
1.Multiple clients MAY submit jobs to a server. 1.Multiple clients MAY submit jobs to a server.
2.Multiple clients MAY monitor a server. 2.Multiple clients MAY monitor a server.
3.Multiple monitors MAY monitor a server. 3.Multiple monitors MAY monitor a server.
4.A client MAY submit jobs to multiple servers. 4.A client MAY submit jobs to multiple servers.
5.A monitor MAY monitor multiple servers. 5.A monitor MAY monitor multiple servers.
6.Multiple servers MAY submit jobs to a printer. 6.Multiple servers MAY submit jobs to a printer.
7.Multiple servers MAY control a printer. 7.Multiple servers MAY control a printer.
Job Monitoring MIB, V0.84 July 21, 1997
3. Managed Object Usage 3. Managed Object Usage
This section describes the usage of the objects in the MIB. This section describes the usage of the objects in the MIB.
3.1 Conformance Considerations 3.1 Conformance Considerations
In order to achieve interoperability between job monitoring applications In order to achieve interoperability between job monitoring applications
and job monitoring agents, this specification includes the conformance and job monitoring agents, this specification includes the conformance
requirements for both monitoring applications and agents. requirements for both monitoring applications and agents.
Job Monitoring MIB, V0.83 July 14, 1997
3.1.1 Conformance Terminology 3.1.1 Conformance Terminology
This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED
NOT" to specify conformance requirements according to RFC 2119 [req- NOT" to specify conformance requirements according to RFC 2119 [req-
words] as follows: words] as follows:
. "SHALL": indicates an action that the subject of the sentence must . "SHALL": indicates an action that the subject of the sentence must
implement in order to claim conformance to this specification implement in order to claim conformance to this specification
. "MAY": indicates an action that the subject of the sentence does . "MAY": indicates an action that the subject of the sentence does
skipping to change at page 18, line 46 skipping to change at page 22, line 5
2.SHALL implement any attributes if (1) the server or device supports 2.SHALL implement any attributes if (1) the server or device supports
the functionality represented by the attribute and (2) the the functionality represented by the attribute and (2) the
information is available to the agent. information is available to the agent.
3.SHOULD implement both forms of an attribute if it implements an 3.SHOULD implement both forms of an attribute if it implements an
attribute that permits a choice of INTEGER and OCTET STRING forms, attribute that permits a choice of INTEGER and OCTET STRING forms,
since implementing both forms may help management applications by since implementing both forms may help management applications by
giving them a choice of representations, since the representation are giving them a choice of representations, since the representation are
equivalent. See the JmAttributeTypeTC textual-convention. equivalent. See the JmAttributeTypeTC textual-convention.
Job Monitoring MIB, V0.84 July 21, 1997
NOTE - This MIB, like the Printer MIB, is written following the NOTE - This MIB, like the Printer MIB, is written following the
subset of SMIv2 that can be supported by SMIv1 and SNMPv1 subset of SMIv2 that can be supported by SMIv1 and SNMPv1
implementations. implementations.
3.1.2.1 MIB II System Group objects 3.1.2.1 MIB II System Group objects
The Job Monitoring MIB agent SHALL implement all objects in the System The Job Monitoring MIB agent SHALL implement all objects in the System
Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is
implemented or not. implemented or not.
Job Monitoring MIB, V0.83 July 14, 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 44 skipping to change at page 23, line 5
ones that may be registered with IANA and SHALL either present them ones that may be registered with IANA and SHALL either present them
to the user or ignore them. In particular, a conforming job to the user or ignore them. In particular, a conforming job
monitoring application SHALL not malfunction when receiving any monitoring application SHALL not malfunction when receiving any
standard or registered enum or bit values. See Section 3.6 entitled standard or registered enum or bit values. See Section 3.6 entitled
"IANA Considerations". "IANA Considerations".
3.SHALL NOT fail when operating with agents that materialize attributes 3.SHALL NOT fail when operating with agents that materialize attributes
after the job has been submitted, as opposed to when the job is after the job has been submitted, as opposed to when the job is
submitted. submitted.
Job Monitoring MIB, V0.84 July 21, 1997
4.SHALL, if it supports a time attribute, accept either form of the 4.SHALL, if it supports a time attribute, accept either form of the
time attribute, since agents are free to implement either time form. time attribute, since agents are free to implement either time form.
3.2 The Job Tables and the Oldest Active and Newest Active Indexes 3.2 The Job Tables and the Oldest Active and Newest Active Indexes
The jmJobTable and jmAttributeTable contain objects and attributes, The jmJobTable and jmAttributeTable contain objects and attributes,
respectively, for each job in a job set. These first two indexes are: respectively, for each job in a job set. These first two indexes are:
1.jmGeneralJobSetIndex - which job set 1.jmGeneralJobSetIndex - which job set
2.jmJobIndex - which job in the job set 2.jmJobIndex - which job in the job set
Job Monitoring MIB, V0.83 July 14, 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.
When a new job is accepted by the server or device that the agent is The agent SHALL assign the next incremental value of jmJobIndex to the
providing access to , the agent SHALL assign the next available value to job, when a new job is accepted by the server or device to which the
the job's jmJobIndex that is used for storing job information in the agent is providing access. If the incremented value of jmJobIndex would
jmJobTable and the jmAttributeTable. If the value would exceed the exceed the implementation-defined maximum value for jmJobIndex, the
implementation-defined maximum value for jmJobIndex, the agent SHALL set agent SHALL 'wrap' back to 1. An agent uses the resulting value of
the value back to 1, i.e., 'wrap' around to the beginning of the job jmJobIndex for storing information in the jmJobTable and the
tables. jmAttributeTable about the job.
It is recommended that the largest value for jmJobIndex be much larger It is recommended that the largest value for jmJobIndex be much larger
than the maximum number of jobs that the implementation can contain at a than the maximum number of jobs that the implementation can contain at a
single time, so as to minimize the pre-mature re-use of jmJobIndex value single time, so as to minimize the pre-mature re-use of jmJobIndex value
for a newer job while clients retain the same 'stale' value for an older for a newer job while clients retain the same 'stale' value for an older
job. job.
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
'inactive' (pendingHeld state), the agent SHALL not change the value of 'inactive' (pendingHeld state), the agent SHALL not change the value of
jmGeneralNewestActiveJobIndex object. jmGeneralNewestActiveJobIndex object.
When a job transitions from one of the 'active' states (pending, When a job transitions from one of the 'active' job states (pending,
processing, processingStopped) to one of the 'inactive' states processing, processingStopped) to one of the 'inactive' job states
(pendingHeld, completed, canceled, or aborted), with a jmJobIndex value (pendingHeld, completed, canceled, or aborted), with a jmJobIndex value
that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL
Job Monitoring MIB, V0.84 July 21, 1997
advance (or wrap) the value to the next oldest 'active' job, if any. advance (or wrap) the value to the next oldest 'active' job, if any.
See the JmJobStateTC textual-convention for a definition of the job
states.
Whenever a job changes from 'inactive' to 'active' (from pendingHeld to Whenever a job transitions from one of the 'inactive' job states to one
pending or processing), the agent SHALL update the value of either the of the 'active' job states (from pendingHeld to pending or processing),
the agent SHALL update the value of either the
jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex
objects, or both, if the job's jmJobIndex value is outside the range objects, or both, if the job's jmJobIndex value is outside the range
between jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex. between jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex.
When all jobs become 'inactive', i.e., enter the pendingHeld, completed, When all jobs become 'inactive', i.e., enter the pendingHeld, completed,
canceled, or aborted states, the agent SHALL set the value of both the canceled, or aborted states, the agent SHALL set the value of both the
jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex objects jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex objects
to 0. to 0.
Job Monitoring MIB, V0.83 July 14, 1997
NOTE - Applications that wish to efficiently access all of the active NOTE - Applications that wish to efficiently access all of the active
jobs MAY use jmGeneralOldestActiveJobIndex value to start with the jobs MAY use jmGeneralOldestActiveJobIndex value to start with the
oldest active job and continue until they reach the index value equal 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, when the application detects that the returned OID is in a In this case, the application SHALL reset the index to 1 when the end of
different MIB (Get Next has moved to the next MIB in the agent), the the table is reached and continue the GetNext operations to find the
application SHALL start over at 1 and continue the GetNext operations to rest of the active jobs.
find the rest of the active jobs.
NOTE - Application detect the end of the table when 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 jmJobIndex
supported by the implementation.
When the server or device is power-cycled, the agent SHALL remember the When the server or device is power-cycled, the agent SHALL remember the
next jmJobIndex value to be assigned, so that new jobs are not assigned next jmJobIndex value to be assigned, so that new jobs are not assigned
the same jmJobIndex as recent jobs before the power cycle. the same jmJobIndex as recent jobs before the power cycle.
3.3 The Attribute Mechanism 3.3 The Attribute Mechanism
Attributes are similar to information objects, except that attributes Attributes are similar to information objects, except that attributes
are identified by an enum, instead of an OID, so that attributes may be are identified by an enum, instead of an OID, so that attributes may be
registered without requiring a new MIB. Also an implementation that registered without requiring a new MIB. Also an implementation that
does not have the functionality represented by the attribute can omit does not have the functionality represented by the attribute can omit
the attribute entirely, rather than having to return a distinguished the attribute entirely, rather than having to return a distinguished
value. The agent is free to materialize an attribute in the value. The agent is free to materialize an attribute in the
jmAttributeTable as soon as the agent is aware of the value of the jmAttributeTable as soon as the agent is aware of the value of the
attribute. attribute.
Job Monitoring MIB, V0.84 July 21, 1997
The agent materializes job attributes in a four-indexed The agent materializes job attributes in a four-indexed
jmAttributeTable: jmAttributeTable:
1.jmGeneralJobSetIndex - which job set 1.jmGeneralJobSetIndex - which job set
2.jmJobIndex - which job in the job set 2.jmJobIndex - which job in the job set
3.jmAttributeTypeIndex - which attribute 3.jmAttributeTypeIndex - which attribute
4.jmAttributeInstanceIndex - which attribute instance for those 4.jmAttributeInstanceIndex - which attribute instance for those
skipping to change at page 22, line 5 skipping to change at page 25, line 28
Some attributes represent information about a job, such as a file-name, Some attributes represent information about a job, such as a file-name,
a document-name, a submission-time or a completion time. Other a document-name, a submission-time or a completion time. Other
attributes represent resources required, e.g., a medium or a colorant, attributes represent resources required, e.g., a medium or a colorant,
etc. to process the job before the job starts processing OR to indicate etc. to process the job before the job starts processing OR to indicate
the amount of the resource consumed during and after processing, e.g., the amount of the resource consumed during and after processing, e.g.,
pages completed or impressions completed. If both a required and a pages completed or impressions completed. If both a required and a
consumed value of a resource is needed, this specification assigns two consumed value of a resource is needed, this specification assigns two
separate attribute enums in the textual convention. separate attribute enums in the textual convention.
Job Monitoring MIB, V0.83 July 14, 1997
NOTE - The table of contents lists all the attributes in order. This NOTE - The table of contents lists all the attributes in order. This
order is the order of enum assignments which is the order that the SNMP order is the order of enum assignments which is the order that the SNMP
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
attribute 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
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.
If the server or device does not implement or does not provide access to If the server or device does not implement or does not provide access to
the information about an attribute, the agent SHOULD NOT create the the information about an attribute, the agent SHOULD NOT create the
corresponding row in the jmAttributeTable. corresponding row in the jmAttributeTable.
3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes
Some attributes have a 'useful' INTEGER32 value, some have a 'useful' Some attributes have a 'useful' Integer32 value, some have a 'useful'
OCTET STRING value, some MAY have either or both depending on OCTET STRING value, some MAY have either or both depending on
implementation, and some MUST have both. See the JmAttributeTypeTC implementation, and some MUST have both. See the JmAttributeTypeTC
textual convention for the specification of each attribute. textual convention for the specification of each attribute.
Job Monitoring MIB, V0.84 July 21, 1997
SNMP requires that if an object cannot be implemented because its values SNMP requires that if an object cannot be implemented because its values
cannot be accessed, then a compliant agent SHALL return an SNMP error in cannot be accessed, then a compliant agent SHALL return an SNMP error in
SNMPv1 or an exception value in SNMPv2. However, this MIB has been SNMPv1 or an exception value in SNMPv2. However, this MIB has been
designed so that 'all' objects can and SHALL be implemented by an agent, designed so that 'all' objects can and SHALL be implemented by an agent,
so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be
generated by the agent. This MIB has also been designed so that when an generated by the agent. This MIB has also been designed so that when an
agent materializes an attribute, the agent SHALL materialize a row agent materializes an attribute, the agent SHALL materialize a row
consisting of both the jmAttributeValueAsInteger and consisting of both the jmAttributeValueAsInteger and
jmAttributeValueAsOctets objects. jmAttributeValueAsOctets objects.
In general, values for objects and attributes have been chosen so that a In general, values for objects and attributes have been chosen so that a
management application will be able to determine whether a 'useful', management application will be able to determine whether a 'useful',
'unknown', or 'other' value is available. When a useful value is not 'unknown', or 'other' value is available. When a useful value is not
available for an object that agent SHALL return a zero-length string for available for an object that agent SHALL return a zero-length string for
octet strings, the value 'unknown(2)' for enums, a '0' value for an octet strings, the value 'unknown(2)' for enums, a '0' value for an
object that represents an index in another table, and a value '-2' for object that represents an index in another table, and a value '-2' for
counting integers. counting integers.
Since each attribute is represented by a row consisting of both the Since each attribute is represented by a row consisting of both the
jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY
Job Monitoring MIB, V0.83 July 14, 1997
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.
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 sub-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.
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) in an index. etc. For example, documentFormatIndex(37) is an index.
NOTE: The Table of Contents also lists the data sub-type and/or data NOTE: The Table of Contents also lists the data sub-type and/or data
sub-types of each attribute, using the textual-convention name when such sub-types of each attribute, using the textual-convention name when such
Job Monitoring MIB, V0.84 July 21, 1997
is defined. The following abbreviations are used in the Table of is defined. The following abbreviations are used in the Table of
Contents as shown: Contents as shown:
'Int32(-2..)' Integer32(-2..2147483647) 'Int32(-2..)' Integer32(-2..2147483647)
'Int32(0..)' Integer32(0..2147483647) 'Int32(0..)' Integer32(0..2147483647)
'Int32(1..)' Integer32(1..2147483647) 'Int32(1..)' Integer32(1..2147483647)
'Int32(m..n)' For all other Integer ranges, the lower 'Int32(m..n)' For all other Integer ranges, the lower
and upper bound of the range is and upper bound of the range is
indicated. indicated.
'Octets63' OCTET STRING(SIZE(0..63)) 'Octets63' OCTET STRING(SIZE(0..63))
'Octets(m..n)' For all other OCTET STRING ranges, the 'Octets(m..n)' For all other OCTET STRING ranges, the
exact range is indicated. exact range is indicated.
3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes
Most attributes SHALL have only one row per job. However, a few Most attributes SHALL have only one row per job. However, a few
attributes can have multiple values per job or even per document, where attributes can have multiple values per job or even per document, where
each value is a separate row in the jmAttributeTable. Unless indicated each value is a separate row in the jmAttributeTable. Unless indicated
with 'MULTI-ROW:' in JmAttributeTypeTC, an agent SHALL ensure that each with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL
attribute occurs only once in the jmAttributeTable for a job. ensure that each attribute occurs only once in the jmAttributeTable for
Attributes that are permitted to appear multiple times in the a job. Most of the 'MULTI-ROW' attributes do not allow duplicate
Job Monitoring MIB, V0.83 July 14, 1997 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
jmAttributeTable for a job are indicated with 'MULTI-ROW:' in their says "the values NEED NOT be unique" can the agent allow duplicate
specification in the JmAttributeTypeTC. However, such 'MULTI-ROW' values to occur for the job.
attributes SHALL not contain duplicates for 'intensive' (as opposed to
'extensive') attributes.
For example, a job or document(s) may use multiple PDLs. However, each
distinct documentFormat attribute value SHALL appear in the
jmAttributeTable only once for a job since the interpreter language is
an intensive attribute, even though the job has a number of documents
that all use the same PDL.
As another example of an intensive attribute that can have multiple
entries, if a document or job uses multiple types of media, there SHALL
be only one row in the jmAttributeTable for each media type, not one row
for each document that uses that medium type.
On the other hand, if a job contains two documents of the same name, NOTE - Duplicate are allowed for 'extensive' 'MULTI-ROW' attributes,
there can be separate rows for the documentName attribute with the same such as fileName(34) or documentName(35), but are not allowed for
name, since a document name is an extensive attribute. The 'intensive' 'MULTI-ROW' attributes, such as mediumConsumed(171) and
specification indicates that the values NEED NOT be unique for such documentFormat(38).
'MULTI-ROW: 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
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 that submitted the intervening server) in the job submission protocol and MAY also mean (2)
job and MAY also mean (2) embedded in the submitted document data, embedded in the submitted document data, and/or (3) defaulted by the
and/or (3) defaulted by the recipient device or server with the same recipient device or server with the same semantics as if the requester
semantics as if the requester had supplied, depending on implementation. had supplied, depending on implementation.
Job Monitoring MIB, V0.84 July 21, 1997
3.3.6 Consumption Attributes 3.3.6 Consumption Attributes
A number of attributes record consumption. Such attribute names end A number of attributes record consumption. Such attribute names end
with the word 'Completed' or 'Consumed'. If the job has not yet with the word 'Completed' or 'Consumed'. If the job has not yet
consumed what that resource is metering, the agent either: (1) SHALL consumed what that resource is metering, the agent either: (1) SHALL
return the value 0 or (2) SHALL not add this attribute to the return the value 0 or (2) SHALL not add this attribute to the
jmAttributeTable until the consumption begins. In the interests of jmAttributeTable until the consumption begins. In the interests of
brevity, the semantics for 0 is specified once here and is not repeated brevity, the semantics for 0 is specified once here and is not repeated
for each consumptive attribute specification. for each consumptive attribute specification.
3.3.7 Index Value Attributes 3.3.7 Index Value Attributes
A number of attributes are indexes in other tables. Such attribute A number of attributes are indexes in other tables. Such attribute
names end with the word 'Index'. If the agent has not (yet) assigned 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
Job Monitoring MIB, V0.83 July 14, 1997
jmAttributeTable until the index value is assigned. In the interests of jmAttributeTable until the index value is assigned. In the interests of
brevity, the semantics for 0 is specified once here and is not repeated brevity, the semantics for 0 is specified once here and is not repeated
for each index attribute specification. for each index attribute specification.
3.4 Job Identification 3.4 Job Identification
There are a number of attributes that permit a user, operator or system There are a number of attributes that permit a user, operator or system
administrator to identify jobs of interest, such as jobName, administrator to identify jobs of interest, such as jobName,
jobOriginatingHost, etc. In addition, there is a Job Submission ID jobOriginatingHost, etc. In addition, there is a Job Submission ID
object that allows a monitoring application to quickly locate and object that allows a monitoring application to quickly locate and
skipping to change at page 25, line 37 skipping to change at page 29, line 5
be assigned by the SNMP Job Monitoring MIB agent when the server or be assigned by the SNMP Job Monitoring MIB agent when the server or
device accepts the jobs from submitting clients. The jmJobIndex object device accepts the jobs from submitting clients. The jmJobIndex object
allows the interested party to obtain all objects desired that relate to allows the interested party to obtain all objects desired that relate to
this job. The MIB provides a mapping table that maps each Job this job. The MIB provides a mapping table that maps each Job
Submission ID (generated by the client) to the corresponding jmJobIndex Submission ID (generated by the client) to the corresponding jmJobIndex
value generated by the agent, so that an application can determine the value generated by the agent, so that an application can determine the
correct value for the jmJobIndex value for the job of interest in a correct value for the jmJobIndex value for the job of interest in a
single Get operation, given the Job Submission ID. See the single Get operation, given the Job Submission ID. See the
jmJobIDGroup. jmJobIDGroup.
Job Monitoring MIB, V0.84 July 21, 1997
The jobName attribute provides a name that the user supplies as a job The jobName attribute provides a name that the user supplies as a job
attribute with the job. The jobName attribute is not necessarily attribute with the job. The jobName attribute is not necessarily
unique, even for one user, let alone across users. unique, even for one user, let alone across users.
3.5 Internationalization Considerations 3.5 Internationalization Considerations
There are a number of objects in this MIB that are represented as coded There are a number of objects in this MIB that are represented as coded
character sets with a data type of OCTET STRING. Most of the objects character sets with a data type of OCTET STRING. Most of the objects
are supplied as job attributes by the client that submits the job to the are supplied as job attributes by the client that submits the job to the
server or device and so are represented in the coded character set server or device and so are represented in the coded character set
specified by that client. specified by that client.
For simplicity, this specification assumes that the clients, job For simplicity, this specification assumes that the clients, job
monitoring applications, servers, and devices are all running in the monitoring applications, servers, and devices are all running in the
same locale, including locales that use two-octet coded character sets, same locale, including locales that use two-octet coded character sets,
such as ISO 10646 (Unicode). Job monitoring applications are expected such as ISO 10646 (Unicode). Job monitoring applications are expected
to understand the coded character set of the client (and job), server, to understand the coded character set of the client (and job), server,
Job Monitoring MIB, V0.83 July 14, 1997
or device. No special means is provided for the monitor to discover the or device. No special means is provided for the monitor to discover the
coded character set used by jobs or by the server or device. This coded character set used by jobs or by the server or device. This
specification does not contain an object that indicates what locale the specification does not contain an object that indicates what locale the
server or device is running in, let alone contain an object to control server or device is running in, let alone contain an object to control
what locale the agent is to use to represent coded character set what locale the agent is to use to represent coded character set
objects. objects.
This MIB also contains objects that are represented using the This MIB also contains objects that are represented using the
DateAndTime textual convention from SMIv2 [SMIv2]. The job management DateAndTime textual convention from SMIv2 [SMIv2-TC]. The job
application SHALL display such objects in the locale of the user running management application SHALL display such objects in the locale of the
the monitoring application. user running the monitoring application.
3.6 IANA Considerations 3.6 IANA Considerations
During the development of this standard, the Printer Working Group (PWG) During the development of this standard, the Printer Working Group (PWG)
working with IANA will register additional enums while the standard is working with IANA [iana] will register additional enums while the
in the proposed and draft states according to the procedures described standard is in the proposed and draft states according to the procedures
in this section. IANA will handle registration of additional enums described in this section. IANA will handle registration of additional
after this standard is approved in cooperation with an IANA-appointed enums after this standard is approved in cooperation with an IANA-
registration editor from the PWG according to the procedures described appointed registration editor from the PWG according to the procedures
in this section: described in this section:
3.6.1 IANA Registration of enums 3.6.1 IANA Registration of enums
This specification uses textual conventions to define enumerated values This specification uses textual conventions to define enumerated values
(enums) and bit values. Enumerations (enums) and bit values are sets of (enums) and bit values. Enumerations (enums) and bit values are sets of
symbolic values defined for use with one or more objects or attributes. symbolic values defined for use with one or more objects or attributes.
All enumeration sets and bit value sets are assigned a symbolic data All enumeration sets and bit value sets are assigned a symbolic data
type name (textual convention). As a convention the symbolic name ends type name (textual convention). As a convention the symbolic name ends
in "TC" for textual convention. These enumerations are defined at the in "TC" for textual convention. These enumerations are defined at the
beginning of the MIB module specification. beginning of the MIB module specification.
Job Monitoring MIB, V0.84 July 21, 1997
This working group has defined several type of enumerations for use in This working group has defined several type of enumerations for use in
the Job Monitoring MIB and the Printer MIB[print-mib]. These types the Job Monitoring MIB and the Printer MIB[print-mib]. These types
differ in the method employed to control the addition of new differ in the method employed to control the addition of new
enumerations. Throughout this document, references to "type n enum", enumerations. Throughout this document, references to "type n enum",
where n can be 1, 2 or 3 can be found in the various tables. The where n can be 1, 2 or 3 can be found in the various tables. The
definitions of these types of enumerations are: definitions of these types of enumerations are:
3.6.1.1 Type 1 enumerations 3.6.1.1 Type 1 enumerations
Type 1 enumeration: All the values are defined in the Job Monitoring Type 1 enumeration: All the values are defined in the Job Monitoring
MIB specification (RFC for the Job Monitoring MIB). Additional MIB specification (RFC for the Job Monitoring MIB). Additional
enumerated values require a new RFC. enumerated values require a new RFC.
There are no type 1 enums in the current draft. There are no type 1 enums in the current draft.
Job Monitoring MIB, V0.83 July 14, 1997
3.6.1.2 Type 2 enumerations 3.6.1.2 Type 2 enumerations
Type 2 enumeration: An initial set of values are defined in the Job Type 2 enumeration: An initial set of values are defined in the Job
Monitoring MIB specification. Additional enumerated values are Monitoring MIB specification. Additional enumerated values are
registered after review by this working group. The initial versions of registered after review by this working group or an editor appointed by
the MIB will contain the values registered so far. After the MIB is IANA after this working group is no longer active.
approved, additional values will be registered through IANA after
approval by this working group.
The following type 2 enums are contained in the current draft : The following type 2 enums are contained in the current draft :
1.JmTimeStampTC 1.JmTimeStampTC
2.JmFinishingTC [same enum values as IPP "finishing" attribute] 2.JmFinishingTC [same enum values as IPP "finishing" attribute]
3.JmPrintQualityTC [same enum values as IPP "print-quality" 3.JmPrintQualityTC [same enum values as IPP "print-quality"
attribute] attribute]
4.JmTonerEconomyTC 4.JmTonerEconomyTC
5.JmPrinterResolutionTC [same enum values as IPP "printer-resolution"
attribute]
6.JmMediumTypeTC
7.JmJobSubmissionTypeTC
8.JmJobStateTC [same enum values as IPP "job-state" attribute]
9.JmAttributeTypeTC
Those textual conventions that are labeled "[same enum values as IPP]" 5.JmMediumTypeTC
have the same enum values as the indicated IPP Job attribute. When IPP
registers additional values, those values shall be simultaneously 6.JmJobSubmissionTypeTC
registered by IANA for use with the Job Monitoring MIB textual-
convention, so that the enum values stay in lock step between the IPP 7.JmJobStateTC [same enum values as IPP "job-state" attribute]
protocol and the Job Monitoring MIB.
8.JmAttributeTypeTC
For those textual conventions that have the same enum values as the
indicated IPP Job attribute SHALL be simultaneously registered by IANA
for use with IPP [ipp-model] and the Job Monitoring MIB.
Job Monitoring MIB, V0.84 July 21, 1997
3.6.1.3 Type 3 enumeration 3.6.1.3 Type 3 enumeration
Type 3 enumeration: An initial set of values are defined in the Job Type 3 enumeration: An initial set of values are defined in the Job
Monitoring MIB specification. Additional enumerated values are Monitoring MIB specification. Additional enumerated values are
registered without working group review. The initial versions of the registered through IANA without working group review.
MIB will contain the values registered so far. After the MIB is
approved, additional values will be registered through IANA without
approval by this working group.
There are no type 3 enums in the current draft. There are no type 3 enums in the current draft.
3.6.2 IANA Registration of type 2 bit values 3.6.2 IANA Registration of type 2 bit values
This draft contains the following type 2 bit value textual-conventions: This draft contains the following type 2 bit value textual-conventions:
1.JmJobServiceTypesTC 1.JmJobServiceTypesTC
2.JmJobStateReasons1TC 2.JmJobStateReasons1TC
3.JmJobStateReasons2TC 3.JmJobStateReasons2TC
4.JmJobStateReasons3TC 4.JmJobStateReasons3TC
5.JmJobStateReasons4TC 5.JmJobStateReasons4TC
Job Monitoring MIB, V0.83 July 14, 1997
These textual-conventions are defined as bits in an Integer so that they These textual-conventions are defined as bits in an Integer so that they
can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4) attributes can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4) attributes
are defined as bit values using the corresponding JmJobStateReasonsNTC are defined as bit values using the corresponding JmJobStateReasonsNTC
textual-conventions. textual-conventions.
The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit
values SHALL follow the procedures for a type 2 enum as specified in values SHALL follow the procedures for a type 2 enum as specified in
Section 3.6.1.2. Section 3.6.1.2.
skipping to change at page 28, line 31 skipping to change at page 32, line 5
procedures for a type 2 enum as specified in Section 3.6.1.2. procedures for a type 2 enum as specified in Section 3.6.1.2.
3.6.4 IANA Registration of MIME types/sub-types for document-formats 3.6.4 IANA Registration of MIME types/sub-types for document-formats
The documentFormat(38) attribute has MIME type/sub-type values for The documentFormat(38) attribute has MIME type/sub-type values for
indicating document formats which IANA registers as "media type" names. indicating document formats which IANA registers as "media type" names.
The values of the documentFormat(38) attribute are the same as the The values of the documentFormat(38) attribute are the same as the
corresponding Internet Printing Protocol (IPP) "document-format" Job corresponding Internet Printing Protocol (IPP) "document-format" Job
attribute values [ipp-model]. attribute values [ipp-model].
Job Monitoring MIB, V0.84 July 21, 1997
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 29, line 4 skipping to change at page 32, line 29
The security policy of some sites MAY be that unprivileged users can The security policy of some sites MAY be that unprivileged users can
only get the objects from jobs that they submitted, plus a few minimal only get the objects from jobs that they submitted, plus a few minimal
objects from other jobs, such as the jmJobKOctetsRequested and objects from other jobs, such as the jmJobKOctetsRequested and
jmJobKOctetsCompleted objects, so that a user can tell how busy a jmJobKOctetsCompleted objects, so that a user can tell how busy a
printer is. Other sites MAY allow all unprivileged users to see all printer is. Other sites MAY allow all unprivileged users to see all
objects of all jobs. This MIB does not require, nor does it specify objects of all jobs. This MIB does not require, nor does it specify
how, such restrictions would be implemented. A monitoring application how, such restrictions would be implemented. A monitoring application
SHOULD enforce the site security policy with respect to returning SHOULD enforce the site security policy with respect to returning
information to an unprivileged end user that is using the monitoring information to an unprivileged end user that is using the monitoring
Job Monitoring MIB, V0.83 July 14, 1997
application to monitor jobs that do not belong to that user, i.e., the application to monitor jobs that do not belong to that user, i.e., the
jmJobOwner object in the jmJobTable does not match the user's user name. jmJobOwner object in the jmJobTable does not match the user's user name.
An operator is a privileged user that would be able to see all objects An operator is a privileged user that would be able to see all objects
of all jobs, independent of the policy for unprivileged users. of all jobs, independent of the policy for unprivileged users.
3.8 Notifications 3.8 Notifications
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.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
Job-Monitoring-MIB DEFINITIONS ::= BEGIN Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed -- The following textual-conventions are needed
-- to implement certain attributes, but are not -- to implement certain attributes, but are not
-- needed to compile this MIB. They are -- needed to compile this MIB. They are
-- provided here for convenience: -- provided here for convenience:
-- hrDeviceIndex FROM HOST-RESOURCES-MIB
-- DateAndTime FROM SNMPv2-TC -- DateAndTime FROM SNMPv2-TC
-- PrtInterpreterLangFamilyTC FROM Printer-MIB -- PrtInterpreterLangFamilyTC FROM Printer-MIB
- -- Use the experimental (54) OID assigned to the Printer MIB[print-mib]
- -- before it was published as RFC 1759.
- -- Upon publication of the Job Monitoring MIB as an RFC, delete this
- -- comment and the line following this comment and change the
- -- reference of { temp 105 } (below) to { mib-2 X }.
- -- This will result in changing:
- -- 1 3 6 1 3 54 jobmonMIB(105) to:
- -- 1 3 6 1 2 1 jobmonMIB(X)
- -- This will make it easier to translate prototypes to
- -- the standard namespace because the lengths of the OIDs won't
- -- change.
temp OBJECT IDENTIFIER ::= { experimental 54 } temp OBJECT IDENTIFIER ::= { experimental 54 }
jobmonMIB MODULE-IDENTITY jobmonMIB MODULE-IDENTITY
LAST-UPDATED "9707140000Z" LAST-UPDATED "9707210000Z"
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
For further information, access the PWG web page under 'JMP': Job Monitoring MIB, V0.84 July 21, 1997
Job Monitoring MIB, V0.83 July 14, 1997
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-02.txt File: draft-ietf-printmib-job-monitor-04.txt
Version: 0.83" Version: 0.84"
::= { temp 105 } ::= { temp 105 }
- -- Textual conventions for this MIB module
JmTimeStampTC ::= TEXTUAL-CONVENTION JmTimeStampTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The simple time at which an event took place. The units SHALL "The simple time at which an event took place. The units SHALL
be in seconds since the system was booted. be in seconds since the system was booted.
NOTE - JmTimeStampTC is defined in units of seconds, rather than NOTE - JmTimeStampTC is defined in units of seconds, rather than
100ths of seconds, so as to be simpler for agents to implement 100ths of seconds, so as to be simpler for agents to implement
(even if they have to implement the 100ths of a second to comply (even if they have to implement the 100ths of a second to comply
skipping to change at page 31, line 46 skipping to change at page 35, line 4
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."
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),
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
unknown(2),
sptUNIX(3), -- UNIX(tm) sptUNIX(3), -- UNIX(tm)
sptOS2(4), -- OS/2 sptOS2(4), -- OS/2
sptPCDOS(5), -- DOS sptPCDOS(5), -- DOS
sptNT(6), -- NT sptNT(6), -- NT
sptMVS(7), -- MVS sptMVS(7), -- MVS
sptVM(8), -- VM sptVM(8), -- VM
sptOS400(9), -- OS/400 sptOS400(9), -- OS/400
sptVMS(10), -- VMS sptVMS(10), -- VMS
sptWindows95(11), -- Windows95 sptWindows95(11), -- Windows95
sptNetWare(33) -- NetWare sptNetWare(33) -- NetWare
skipping to change at page 33, line 5 skipping to change at page 36, line 5
number and placement of the staples is site-defined. number and placement of the staples is site-defined.
stapleTopLeft(5), stapleTopLeft(5),
Place one or more staples on the top left corner of the Place one or more staples on the top left corner of the
document(s). document(s).
stapleBottomLeft(6), stapleBottomLeft(6),
Place one or more staples on the bottom left corner of the Place one or more staples on the bottom left corner of the
document(s). document(s).
Job Monitoring MIB, V0.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 1997
stapleTopRight(7), stapleTopRight(7),
Place one or more staples on the top right corner of the Place one or more staples on the top right corner of the
document(s). document(s).
stapleBottomRight(8), stapleBottomRight(8),
Place one or more staples on the bottom right corner of the Place one or more staples on the bottom right corner of the
document(s). document(s).
saddleStitch(9), saddleStitch(9),
skipping to change at page 34, line 4 skipping to change at page 37, line 4
other(1), other(1),
unknown(2), unknown(2),
none(3), none(3),
staple(4), staple(4),
stapleTopLeft(5), stapleTopLeft(5),
stapleBottomLeft(6), stapleBottomLeft(6),
stapleTopRight(7), stapleTopRight(7),
stapleBottomRight(8), stapleBottomRight(8),
saddleStitch(9), saddleStitch(9),
edgeStitch(10), edgeStitch(10),
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
punch(11), punch(11),
cover(12), cover(12),
bind(13) bind(13)
} }
JmPrintQualityTC ::= TEXTUAL-CONVENTION JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Print quality settings. "Print quality settings.
skipping to change at page 34, line 35 skipping to change at page 37, line 36
normal(4), -- Normal or intermediate quality on the normal(4), -- Normal or intermediate quality on the
-- printer. -- printer.
high(5) -- Highest quality available on the printer. high(5) -- Highest quality available on the printer.
} }
JmPrinterResolutionTC ::= TEXTUAL-CONVENTION JmPrinterResolutionTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Printer resolutions. "Printer resolutions.
The values represent single integer resolutions or pairs of Nine octets consisting of two 4-octet SIGNED-INTEGERs followed
integer resolutions. The latter are to specify the resolution by a SIGNED-BYTE. The values are the same as those specified in
when the x and y dimensions differ. When two integers are the Printer MIB [printmib]. The first SIGNED-INTEGER contains
specified, the first is in the x direction, i.e., in the the value of prtMarkerAddressabilityXFeedDir. The second
direction of the shortest dimension of the medium, so that the SIGNED-INTEGER contains the value of
value is independent of whether the printer feeds long edge or prtMarkerAddressabilityFeedDir. The SIGNED-BYTE contains the
short edge first. value of prtMarkerAddressabilityUnit.
These values are the same as the enum values of the IPP
'printer-resolution' attribute. See Section 3.6.1.2."
Job Monitoring MIB, V0.83 July 14, 1997
REFERENCE Note: the latter value is either 3 (tenThousandsOfInches) or 4
"This is a type 2 enumeration. See Section 3.6.1.2." (micrometers) and the addressability is in 10,000 units of
SYNTAX INTEGER {
other(1), -- Not one of the specified or registered
-- values.
unknown(2), -- The actual value is unknown.
normal(3), -- Normal resolution.
res100(4), -- 100 x 100 dpi
res200(5), -- 200 x 200 dpi
res240(6), -- 240 x 240 dpi
res300(7), -- 300 x 300 dpi
res360(8), -- 360 x 360 dpi
res400(9), -- 400 x 400 dpi
res600(10), -- 600 x 600 dpi
res720(11), -- 720 x 720 dpi
res800(12), -- 800 x 800 dpi
res1200(13), -- 1200 x 1200 dpi
res1440(14), -- 1440 x 1440 dpi
res1600(15), -- 1600 x 1600 dpi
res1800(16), -- 1800 x 1800 dpi
-- future equal resolutions will be added Job Monitoring MIB, V0.84 July 21, 1997
-- here, the enum values will not be re-
-- sorted or re-assigned:
res100x200(100), -- 100 x 200 dpi measure. Thus the SIGNED-INTEGERs represent integral values in
res200x100(101), -- 200 x 100 dpi either dots-per-inch or dots-per-centimeter.
res300x600(102), -- 300 x 600 dpi
res600x300(103), -- 600 x 300 dpi
res360x720(104), -- 360 x 720 dpi
res720x360(105), -- 720 x 360 dpi
res400x800(106), -- 400 x 800 dpi
res800x400(107), -- 800 x 400 dpi
res600x1200(108), -- 600 x 1200 dpi
res1200x600(109), -- 1200 x 600 dpi
res720x1440(110), -- 720 x 1440 dpi
res1440x720(111), -- 1440 x 720 dpi
res1800x600(112) -- 1800 x 600 dpi
-- future unequal resolutions will be The syntax is the same as the IPP 'printer-resolution'
-- added here, the enum values will not attribute. See Section 3.6.1.2."
-- be re-sorted or re-assigned: SYNTAX OCTET STRING (SIZE(9))
}
Job Monitoring MIB, V0.83 July 14, 1997
JmTonerEconomyTC ::= TEXTUAL-CONVENTION JmTonerEconomyTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Toner economy settings." "Toner economy settings."
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.
off(3), -- Off. Normal. Use full toner. off(3), -- Off. Normal. Use full toner.
skipping to change at page 36, line 32 skipping to change at page 39, line 4
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.
} }
JmMediumTypeTC ::= TEXTUAL-CONVENTION JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"Identifies the type of medium. "Identifies the type of medium.
other(1), other(1),
The type is neither one of the values listed in this The type is neither one of the values listed in this
specification nor a registered value. specification nor a registered value.
unknown(2), unknown(2),
The type is not known. The type is not known.
Job Monitoring MIB, V0.83 July 14, 1997
stationery(3), stationery(3),
Separately cut sheets of an opaque material. Separately cut sheets of an opaque material.
transparency(4), transparency(4),
Separately cut sheets of a transparent material. Separately cut sheets of a transparent material.
envelope(5), envelope(5),
Envelopes that can be used for conventional mailing Envelopes that can be used for conventional mailing
purposes. purposes.
skipping to change at page 37, line 45 skipping to change at page 40, line 4
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.
labels(12), labels(12),
Label-stock. Label-stock.
multiLayer(13) multiLayer(13)
Form medium composed of multiple layers which are pre- Form medium composed of multiple layers which are pre-
attached to one another, e.g. for use with impact printers." attached to one another, e.g. for use with impact printers."
Job Monitoring MIB, V0.84 July 21, 1997
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
stationery(3), stationery(3),
transparency(4), transparency(4),
envelope(5), envelope(5),
envelopePlain(6), envelopePlain(6),
envelopeWindow(7), envelopeWindow(7),
Job Monitoring MIB, V0.83 July 14, 1997
continuousLong(8), continuousLong(8),
continuousShort(9), continuousShort(9),
tabStock(10), tabStock(10),
multiPartForm(11), multiPartForm(11),
labels(12), labels(12),
multiLayer(13) multiLayer(13)
} }
JmJobSubmissionTypeTC ::= TEXTUAL-CONVENTION JmJobSubmissionTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 38, line 25 skipping to change at page 40, line 36
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 The ASCII characters '0-9', 'A-Z', and 'a-z' are assigned in
order giving 62 possible formats. order giving 62 possible formats.
Each job submission ID is a fixed-length, 48-octet printable Each job submission ID is a fixed-length, 48-octet printable
ASCII coded character string, consisting of the following ASCII coded character string, consisting of the following
fields: fields:
octet 1 The format letter. octet 1 The format letter.
octets 2-40 A 39-character, ASCII trailing SPACE filled octets 2-40 A 39-character, ASCII trailing SPACE filled
field specified by the format letter, if the field specified by the format letter, if the
data is less than 39 ASCII characters. data is less than 39 ASCII characters.
octets 41-48 A sequential or random number to make the ID octets 41-48 A sequential or random number to make the ID
quasi-unique. quasi-unique.
If the client does not supply a job submission ID in the job If the client does not supply a job submission ID in the job
submission protocol, then the server SHALL assign a job submission protocol, then the server SHALL assign a job
submission ID using any of the standard formats and adding the submission ID using any of the standard formats that are
final 8 octets to distinguish the ID from others submitted from reserved to the agent. Clients SHALL not use formats that are
the same client. reserved to agents.
The format values registered so far are: Job Monitoring MIB, V0.84 July 21, 1997
The format values defined at the time of completion of the
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
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'.
NOTE - other formats may be registered that are
reserved to the agent for use when the client does
not supply a job submission ID.
'1' octets 2-40: last 39 bytes of the jobName attribute. '1' octets 2-40: last 39 bytes of the jobName attribute.
octets 41-48: 8-decimal-digit random number octets 41-48: 8-decimal-digit random number
Job Monitoring MIB, V0.83 July 14, 1997
'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
'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
skipping to change at page 39, line 33 skipping to change at page 42, line 5
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'6' octets 2-40: last 39 bytes of the user account '6' octets 2-40: last 39 bytes of the user account
number. number.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
'7' octets 2-40: last 39 bytes of the DTMF incoming '7' octets 2-40: last 39 bytes of the DTMF incoming
FAX routing number. FAX routing number.
octets 41-48: 8-decimal-digit sequential number octets 41-48: 8-decimal-digit sequential number
Job Monitoring MIB, V0.84 July 21, 1997
'8' octets 2-40: last 39 bytes of the job owner name
(that the agent returns in the jmJobOwner object).
octets 41-48: 8-decimal-digit sequential number
NOTE - the job submission id is only intended to be unique NOTE - the job submission id is only intended to be unique
between a limited set of clients for a limited duration of time, between a limited set of clients for a limited duration of time,
namely, for the life time of the job in the context of the namely, for the life time of the job in the context of the
server or device that is processing the job. Some of the server or device that is processing the job. Some of the
formats include something that is unique per client and a random formats include something that is unique per client and a random
number so that the same job submitted by the same client will number so that the same job submitted by the same client will
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
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'
Job Monitoring MIB, V0.83 July 14, 1997
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:
+----> canceled(7) +----> canceled(7)
/ /
+---> pending(3) --------> processing(5) ------+------> completed(9) +---> pending(3) --------> processing(5) ------+------> completed(9)
| ^ ^ \ | ^ ^ \
- --->+ | | +----> aborted(8)
| v v / | v v /
+---> pendingHeld(4) processingStopped(6) ---+ +---> pendingHeld(4) processingStopped(6) ---+
Figure 4 - Normal Job State Transitions Figure 4 - Normal Job State Transitions
Job Monitoring MIB, V0.84 July 21, 1997
Normally a job progresses from left to right. Other state Normally a job progresses from left to right. Other state
transitions are unlikely, but are not forbidden. Not shown are transitions are unlikely, but are not forbidden. Not shown are
the transitions to the canceled state from the pending, the transitions to the canceled state from the pending,
pendingHeld, processing, and processingStopped states. pendingHeld, processing, and processingStopped states.
Jobs in the pending, processing, and processingStopped states Jobs in the pending, processing, and processingStopped states
are called 'active', while jobs in the pendingHeld, canceled, are called 'active', while jobs in the pendingHeld, canceled,
aborted, and completed are called 'inactive'. aborted, and completed are called 'inactive'.
These values are the same as the enum values of the IPP 'job- These values are the same as the enum values of the IPP 'job-
skipping to change at page 41, line 5 skipping to change at page 43, line 29
other(1), other(1),
The job state is not one of the defined states. The job state is not one of the defined states.
unknown(2), unknown(2),
The job state is not known, or 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.
Job Monitoring MIB, V0.83 July 14, 1997
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.
skipping to change at page 41, line 32 skipping to change at page 44, line 4
document transforms which include (1) purely software document transforms which include (1) purely software
processes that are interpreting a PDL, and (2) hardware processes that are interpreting a PDL, and (2) hardware
devices that are interpreting a PDL, making marks on a devices that are interpreting a PDL, making marks on a
medium, and/or performing finishing, such as stapling, etc. medium, and/or performing finishing, such as stapling, etc.
OR OR
2. (configuration 2) the server has made the job ready for 2. (configuration 2) the server has made the job ready for
printing, but the output device is not yet printing it, printing, but the output device is not yet printing it,
either because the job hasn't reached the output device or either because the job hasn't reached the output device or
Job Monitoring MIB, V0.84 July 21, 1997
because the job is queued in the output device or some other because the job is queued in the output device or some other
spooler, awaiting the output device to print it. spooler, awaiting the output device to print it.
When the job is in the processing state, the entire job When the job is in the processing state, the entire job
state includes the detailed status represented in the device state includes the detailed status represented in the device
MIB indicated by the hrDeviceIndex value of the job's MIB indicated by the hrDeviceIndex value of the job's
physicalDevice attribute, if the agent implements such a physicalDevice attribute, if the agent implements such a
device MIB. device MIB.
Implementations MAY, though they NEED NOT, include Implementations MAY, though they NEED NOT, include
skipping to change at page 42, line 4 skipping to change at page 44, line 30
making marks on a medium. making marks on a medium.
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
Job Monitoring MIB, V0.83 July 14, 1997
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
skipping to change at page 42, line 31 skipping to change at page 45, line 4
canceledByOperator value. canceledByOperator value.
aborted(8), aborted(8),
The job has been aborted by the system, usually while the The job has been aborted by the system, usually while the
job was in the processing or processingStopped state. job was in the processing or processingStopped state.
completed(9) completed(9)
The job has completed successfully or with warnings or The job has completed successfully or with warnings or
errors after processing and all of the media have been errors after processing and all of the media have been
successfully stacked in the appropriate output bin(s). The successfully stacked in the appropriate output bin(s). The
Job Monitoring MIB, V0.84 July 21, 1997
job's jmJobStateReasons1 object SHOULD contain one of: job's jmJobStateReasons1 object SHOULD contain one of:
completedSuccessfully, completedWithWarnings, or completedSuccessfully, completedWithWarnings, or
completedWithErrors values." completedWithErrors values."
REFERENCE REFERENCE
"This is a type 2 enumeration. See Section 3.6.1.2." "This is a type 2 enumeration. See Section 3.6.1.2."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
pending(3), pending(3),
pendingHeld(4), pendingHeld(4),
skipping to change at page 43, line 5 skipping to change at page 45, line 29
canceled(7), canceled(7),
aborted(8), aborted(8),
completed(9) completed(9)
} }
JmAttributeTypeTC ::= TEXTUAL-CONVENTION JmAttributeTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the attribute which identifies the attribute. "The type of the attribute which identifies the attribute.
Job Monitoring MIB, V0.83 July 14, 1997
In the following definitions of the enums, each description In the following definitions of the enums, each description
indicates whether the useful value of the attribute SHALL be indicates whether the useful value of the attribute SHALL be
represented using the jmAttributeValueAsInteger or the represented using the jmAttributeValueAsInteger or the
jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:'
or 'OCTETS:', respectively. or 'OCTETS:', respectively.
Some attributes allow the agent implementer a choice of useful Some attributes allow the agent implementer a choice of useful
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.
skipping to change at page 43, line 31 skipping to change at page 46, line 5
tags. See the jmAttributeGroup for the descriptions of these tags. See the jmAttributeGroup for the descriptions of these
two MANDATORY objects. two MANDATORY objects.
NOTE - The enum assignments are grouped logically with values NOTE - The enum assignments are grouped logically with values
assigned in groups of 20, so that additional values may be assigned in groups of 20, so that additional values may be
registered in the future and assigned a value that is part of registered in the future and assigned a value that is part of
their logical grouping. their logical grouping.
NOTE: No attribute name exceeds 31 characters. NOTE: No attribute name exceeds 31 characters.
In the following descriptions of each attribute, the tags: Job Monitoring MIB, V0.84 July 21, 1997
'INTEGER:' or 'OCTETS:' specify whether the value SHALL be
represented in the jmAttributeValueAsInteger or the
jmAttributeValueAsOctets object, or both, respectively.
The standard attribute types defined so far are: The standard attribute types defined at the time of completion
of the specification are:
jmAttributeTypeIndex Datatype jmAttributeTypeIndex Datatype
-------------------- -------- -------------------- --------
other(1), Integer32(-2..2147483647) other(1), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: and/or OCTETS: An attribute that is not in the INTEGER: and/or OCTETS: An attribute that is not in the
list and/or that has not been approved and registered with list and/or that has not been approved and registered with
IANA. IANA.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job State attributes + Job State attributes
+ +
+ The following attributes specify the state of a job. + The following attributes specify the state of a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.83 July 14, 1997
jobStateReasons2(3), JmJobStateReasons2TC jobStateReasons2(3), JmJobStateReasons2TC
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 the JmJobStateReasons1TC textual- description under the JmJobStateReasons1TC textual-
convention. convention.
jobStateReasons3(4), JmJobStateReasons3TC jobStateReasons3(4), JmJobStateReasons3TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current
state that augments the jmJobState object. See the state that augments the jmJobState object. See the
skipping to change at page 44, line 27 skipping to change at page 46, line 47
jobStateReasons4(5), JmJobStateReasons4TC jobStateReasons4(5), JmJobStateReasons4TC
INTEGER: Additional information about the job's current INTEGER: Additional information about the job's current
state that augments the jmJobState object. See the state that augments the jmJobState object. See the
description under JmJobStateReasons1TC textual-convention. description under JmJobStateReasons1TC textual-convention.
processingMessage(6), OCTET STRING(SIZE(0..63)) processingMessage(6), OCTET STRING(SIZE(0..63))
OCTETS: MULTI-ROW: A coded character set message that is OCTETS: MULTI-ROW: A coded character set message that is
generated during the processing of the job as a simple form generated during the processing of the job as a simple form
of processing log to show progress and any problems. of processing log to show progress and any problems.
There is no restriction for the same message to occur in There is no restriction for the same message occurring in
multiple rows. multiple rows.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Identification attributes + Job Identification attributes
+ +
Job Monitoring MIB, V0.84 July 21, 1997
+ The following attributes help an end user, a system + The following attributes help an end user, a system
+ operator, or an accounting program identify a job. + operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobAccountName(21), OCTET STRING(SIZE(0..63)) jobAccountName(21), 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
or categorize charges for services provided, such as a or categorize charges for services provided, such as a
customer account name or number. customer account name or number.
NOTE: This attribute NEED NOT be printable characters. NOTE: This attribute NEED NOT be printable characters.
serverAssignedJobName(22), OCTET STRING(SIZE(0..63)) serverAssignedJobName(22), OCTET STRING(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
Job Monitoring MIB, V0.83 July 14, 1997
that submitted the job to the device that the agent is that submitted the job to the device that the agent is
providing access to with this MIB. providing access to with this MIB.
NOTE - This attribute is intended for enabling a user to NOTE - This attribute is intended for enabling a user to
find his/her job that a server submitted to a device when find his/her job that a server submitted to a device when
either the client does not support the jmJobSubmissionID or either the client does not support the jmJobSubmissionID or
the server does not pass the jmJobSubmissionID through to the server does not pass the jmJobSubmissionID through to
the device. the device.
jobName(23), OCTET STRING(SIZE(0..63)) jobName(23), OCTET STRING(SIZE(0..63))
skipping to change at page 45, line 35 skipping to change at page 48, line 4
In order to assist users to find their jobs for job In order to assist users to find their jobs for job
submission protocols that don't supply a jmJobSubmissionID, submission protocols that don't supply a jmJobSubmissionID,
the agent SHOULD maintain the jobName attribute for the time the agent SHOULD maintain the jobName attribute for the time
specified by the jmGeneralJobPersistence object, rather than specified by the jmGeneralJobPersistence object, rather than
the (shorter) jmGeneralAttributePersistence object. the (shorter) jmGeneralAttributePersistence object.
If this attribute is not specified when the job is If this attribute is not specified when the job is
submitted, no job name is assumed, but implementation submitted, no job name is assumed, but implementation
specific defaults are allowed, such as the value of the specific defaults are allowed, such as the value of the
Job Monitoring MIB, V0.84 July 21, 1997
documentName attribute of the first document in the job or documentName attribute of the first document in the job or
the fileName attribute of the first document in the job. the fileName attribute of the first document in the job.
The jobName attribute is distinguished from the jobComment The jobName attribute is distinguished from the jobComment
attribute, in that the jobName attribute is intended to attribute, in that the jobName attribute is intended to
permit the submitting user to distinguish between different permit the submitting user to distinguish between different
jobs that he/she has submitted. The jobComment attribute is jobs that he/she has submitted. The jobComment attribute is
intended to be free form additional information that a user intended to be free form additional information that a user
might wish to use to communicate with himself/herself, such might wish to use to communicate with himself/herself, such
as a reminder of what to do with the results or to indicate as a reminder of what to do with the results or to indicate
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
Job Monitoring MIB, V0.83 July 14, 1997
only a source or only a destination. For example, a job 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 case, three bits would be set in the jobServiceTypes
attribute, corresponding to the hexadecimal values: 0x8 + attribute, corresponding to the hexadecimal values: 0x8 +
0x20 + 0x4, respectively, yielding: 0x2C. 0x20 + 0x4, respectively, yielding: 0x2C.
Whether this attribute is set from a job attribute supplied Whether this attribute is set from a job attribute supplied
by the job submission client or is set by the recipient job by the job submission client or is set by the recipient job
submission server or device depends on the job submission submission server or device depends on the job submission
protocol. This attribute SHALL be implemented if the server protocol. This attribute SHALL be implemented if the server
skipping to change at page 46, line 35 skipping to change at page 49, line 4
INTEGER: The index of the row in the associated Printer INTEGER: The index of the row in the associated Printer
MIB[print-mib] of the channel which is the source of the MIB[print-mib] of the channel which is the source of the
print job. print job.
jobSourcePlatformType(26), JmJobSourcePlatformTypeTC jobSourcePlatformType(26), JmJobSourcePlatformTypeTC
INTEGER: The source platform type of the immediate upstream INTEGER: The source platform type of the immediate upstream
submitter that submitted the job to the server submitter that submitted the job to the server
(configuration 2) or device (configuration 1 and 3) to which (configuration 2) or device (configuration 1 and 3) to which
the agent is providing access. For configuration 1, this is the agent is providing access. For configuration 1, this is
the type of the client that submitted the job to the device; the type of the client that submitted the job to the device;
Job Monitoring MIB, V0.84 July 21, 1997
for configuration 2, this is the type of the client that for configuration 2, this is the type of the client that
submitted the job to the server; and for configuration 3, submitted the job to the server; and for configuration 3,
this is the type of the server that submitted the job to the this is the type of the server that submitted the job to the
device. device.
submittingServerName(27), OCTET STRING(SIZE(0..63)) submittingServerName(27), OCTET STRING(SIZE(0..63))
OCTETS: For configuration 3 only: The administrative name OCTETS: For configuration 3 only: The administrative name
of the server that submitted the job to the device. of the server that submitted the job to the device.
submittingApplicationName(28), OCTET STRING(SIZE(0..63)) submittingApplicationName(28), OCTET STRING(SIZE(0..63))
OCTETS: The name of the client application (not the server OCTETS: The name of the client application (not the server
in configuration 3) that submitted the job to the server or in configuration 3) that submitted the job to the server or
device. device.
jobOriginatingHost(29), OCTET STRING(SIZE(0..63)) jobOriginatingHost(29), OCTET STRING(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.
Job Monitoring MIB, V0.83 July 14, 1997
deviceNameRequested(30), OCTET STRING(SIZE(0..63)) deviceNameRequested(30), OCTET STRING(SIZE(0..63))
OCTETS: The administratively defined coded character set OCTETS: The administratively defined coded character set
name of the target device requested by the submitting user. name of the target device requested by the submitting user.
For configuration 1, its value corresponds to the Printer For configuration 1, its value corresponds to the Printer
MIB[print-mib]: prtGeneralPrinterName object. For MIB[print-mib]: prtGeneralPrinterName object. For
configuration 2 and 3, its value is the name of the logical configuration 2 and 3, its value is the name of the logical
or physical device that the user supplied to indicate to the or physical device that the user supplied to indicate to the
server on which device(s) they wanted the job to be server on which device(s) they wanted the job to be
processed. processed.
skipping to change at page 47, line 30 skipping to change at page 49, line 49
For configuration 1, its value corresponds to the queue in For configuration 1, its value corresponds to the queue in
the device for which the agent is providing access. For the device for which the agent is providing access. For
configuration 2 and 3, its value is the name of the queue configuration 2 and 3, its value is the name of the queue
that the user supplied to indicate to the server on which that the user supplied to indicate to the server on which
device(s) they wanted the job to be processed. device(s) they wanted the job to be processed.
NOTE - typically an implementation SHOULD support either the NOTE - typically an implementation SHOULD support either the
deviceNameRequested or queueNameRequested attribute, but not deviceNameRequested or queueNameRequested attribute, but not
both. both.
physicalDevice(32), hrDeviceIndex (see HR MIB) physicalDevice(32), hrDeviceIndex
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The index of the physical device MIB INTEGER: MULTI-ROW: The index of the physical device MIB
instance requested/used, such as the Printer MIB[print-mib]. instance requested/used, such as the Printer MIB[print-mib].
Job Monitoring MIB, V0.84 July 21, 1997
This value is an hrDeviceIndex value. See the Host This value is an hrDeviceIndex value. See the Host
Resources MIB[hr-mib]. Resources MIB[hr-mib].
AND/OR AND/OR
OCTETS: MULTI-ROW: The name of the physical device to OCTETS: MULTI-ROW: The name of the physical device to
which the job is assigned. which the job is assigned.
numberOfDocuments(33), Integer32(-2..2147483647) numberOfDocuments(33), Integer32(-2..2147483647)
INTEGER: The number of documents in this job. INTEGER: The number of documents in this job.
fileName(34), OCTET STRING(SIZE(0..63)) fileName(34), OCTET STRING(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 in multiple There is no restriction on the same file name occurring in
rows. multiple rows.
Job Monitoring MIB, V0.83 July 14, 1997
documentName(35), OCTET STRING(SIZE(0..63)) documentName(35), OCTET STRING(SIZE(0..63))
OCTETS: MULTI-ROW: The coded character set name of the OCTETS: MULTI-ROW: The coded character set name of the
document. document.
There is no restriction on the same document name in There is no restriction on the same document name occurring
multiple rows. in multiple rows.
jobComment(36), OCTET STRING(SIZE(0..63)) jobComment(36), OCTET STRING(SIZE(0..63))
OCTETS: An arbitrary human-readable coded character text OCTETS: An arbitrary human-readable coded character text
string supplied by the submitting user or the job submitting string supplied by the submitting user or the job submitting
application program for any purpose. For example, a user application program for any purpose. For example, a user
might indicate what he/she is going to do with the printed might indicate what he/she is going to do with the printed
output or the job submitting application program might output or the job submitting application program might
indicate how the document was produced. indicate how the document was produced.
The jobComment attribute is not intended to be a name; see The jobComment attribute is not intended to be a name; see
skipping to change at page 48, line 36 skipping to change at page 51, line 5
INTEGER: MULTI-ROW: The index in the prtInterpreterTable INTEGER: MULTI-ROW: The index in the prtInterpreterTable
in the Printer MIB[print-mib] of the page description in the Printer MIB[print-mib] of the page description
language (PDL) or control language interpreter that this job language (PDL) or control language interpreter that this job
requires/uses. A document or a job MAY use more than one requires/uses. A document or a job MAY use more than one
PDL or control language. PDL or control language.
NOTE - As with all intensive attributes where multiple rows NOTE - As with all intensive attributes where multiple rows
are allowed, there SHALL be only one distinct row for each are allowed, there SHALL be only one distinct row for each
distinct interpreter; there SHALL be no duplicates. distinct interpreter; there SHALL be no duplicates.
Job Monitoring MIB, V0.84 July 21, 1997
NOTE - This attribute type is intended to be used with an NOTE - This attribute type is intended to be used with an
agent that implements the Printer MIB and SHALL not be used agent that implements the Printer MIB and SHALL not be used
if the agent does not implement the Printer MIB. Such an if the agent does not implement the Printer MIB. Such an
agent SHALL use the documentFormat attribute instead. agent SHALL use the documentFormat attribute instead.
documentFormat(38), PrtInterpreterLangFamilyTC documentFormat(38), PrtInterpreterLangFamilyTC
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The interpreter language family INTEGER: MULTI-ROW: The interpreter language family
corresponding to the Printer MIB[print-mib] corresponding to the Printer MIB[print-mib]
prtInterpreterLangFamily object, that this job prtInterpreterLangFamily object, that this job
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
Job Monitoring MIB, V0.83 July 14, 1997
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.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
skipping to change at page 49, line 35 skipping to change at page 52, line 4
in favor of higher priority jobs). The value 100 is defined in favor of higher priority jobs). The value 100 is defined
to indicate the highest possible priority. Priority is to indicate the highest possible priority. Priority is
expected to be evenly or 'normally' distributed across this expected to be evenly or 'normally' distributed across this
range. The mapping of vendor-defined priority over this range. The mapping of vendor-defined priority over this
range is implementation-specific. range is implementation-specific.
jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC) jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC)
OCTETS: The calendar date and time of day after which the OCTETS: The calendar date and time of day after which the
job SHALL become a candidate to be scheduled for processing. job SHALL become a candidate to be scheduled for processing.
If the value of this attribute is in the future, the server If the value of this attribute is in the future, the server
Job Monitoring MIB, V0.84 July 21, 1997
SHALL set the value of the job's jmJobState object to SHALL set the value of the job's jmJobState object to
pendingHeld and add the jobProcessAfterSpecified bit value pendingHeld and add the jobProcessAfterSpecified bit value
to the job's jmJobStateReasons1 object. When the specified to the job's jmJobStateReasons1 object. When the specified
date and time arrives, the server SHALL remove the date and time arrives, the server SHALL remove the
jobProcessAfterSpecified bit value from the job's jobProcessAfterSpecified bit value from the job's
jmJobStateReasons1 object and, if no other reasons remain, jmJobStateReasons1 object and, if no other reasons remain,
SHALL change the job's jmJobState object to pending. SHALL change the job's jmJobState object to pending.
jobHold(52), JmBooleanTC jobHold(52), JmBooleanTC
INTEGER: If the value is 'true(4)', a client has explicitly INTEGER: If the value is 'true(4)', a client has explicitly
specified that the job is to be held until explicitly specified that the job is to be held until explicitly
released. Until the job is explicitly released by a client, released. Until the job is explicitly released by a client,
the job SHALL be in the pendingHeld state with the the job SHALL be in the pendingHeld state with the
jobHoldSpecified value in the jmJobStateReasons1 attribute. jobHoldSpecified value in the jmJobStateReasons1 attribute.
jobHoldUntil(53), OCTET STRING(SIZE(0..63)) jobHoldUntil(53), OCTET STRING(SIZE(0..63))
OCTETS: The named time period during which the job SHALL OCTETS: The named time period during which the job SHALL
become a candidate for processing, such as 'no-hold', become a candidate for processing, such as 'evening',
Job Monitoring MIB, V0.83 July 14, 1997 'night', 'weekend', 'second-shift', 'third-shift', etc., as
defined by the system administrator. See IPP [ipp-model]
'evening', 'night', 'weekend', 'second-shift', 'third- for the standard keyword values. Until that time period
shift', etc., as defined by the system administrator. Until arrives, the job SHALL be in the pendingHeld state with the
that time period arrives, the job SHALL be in the jobHoldUntilSpecified value in the jmJobStateReasons1
pendingHeld state with the jobHoldUntilSpecified value in object. The value 'no-hold' SHALL indicate explicitly that
the jmJobStateReasons1 object. no time period has been specified.
outputBin(54), Integer32(0..2147483647) outputBin(54), Integer32(0..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The output subunit index in the INTEGER: MULTI-ROW: The output subunit index in the
Printer MIB[print-mib] Printer MIB[print-mib]
AND/OR AND/OR
OCTETS: the name or number (represented as ASCII digits) of OCTETS: the name or number (represented as ASCII digits) of
skipping to change at page 50, line 33 skipping to change at page 53, 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.84 July 21, 1997
+ +
+ For devices that can vary the image quality. + For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityRequested(70), JmPrintQualityTC printQualityRequested(70), JmPrintQualityTC
INTEGER: MULTI-ROW: The print quality selection requested INTEGER: MULTI-ROW: The print quality selection requested
for a document in the job for printers that allow quality for a document in the job for printers that allow quality
differentiation. differentiation.
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
INTEGER: 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.
Job Monitoring MIB, V0.83 July 14, 1997
printerResolutionUsed(73), JmPrinterResolutionTC printerResolutionUsed(73), JmPrinterResolutionTC
INTEGER: MULTI-ROW: The printer resolution actually used OCTETS: MULTI-ROW: The printer resolution actually used by
by a document in the job for printers that support a document in the job for printers that support resolution
resolution selection. selection.
tonerEcomonyRequested(74), JmTonerEconomyTC tonerEcomonyRequested(74), JmTonerEconomyTC
INTEGER: MULTI-ROW: The print quality selection requested INTEGER: MULTI-ROW: The print quality selection requested
for documents in the job for printers that allow toner for documents in the job for printers that allow toner
quality differentiation. quality differentiation.
tonerEcomonyUsed(75), JmTonerEconomyTC tonerEcomonyUsed(75), JmTonerEconomyTC
INTEGER: MULTI-ROW: The print quality selection actually INTEGER: MULTI-ROW: The print quality selection actually
used by documents in the job for printers that allow toner used by documents in the job for printers that allow toner
quality differentiation. quality differentiation.
skipping to change at page 51, line 36 skipping to change at page 54, 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.84 July 21, 1997
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Progress attributes (requested and consumed) + Job Progress attributes (requested and consumed)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative progress + applications to show an indication of relative progress
+ to users. + to users.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobCopiesRequested(90), Integer32(-2..2147483647) jobCopiesRequested(90), Integer32(-2..2147483647)
INTEGER: The number of copies of the entire job that are to INTEGER: The number of copies of the entire job that are to
be produced. be produced.
jobCopiesCompleted(91), Integer32(-2..2147483647) jobCopiesCompleted(91), Integer32(-2..2147483647)
INTEGER: The number of copies of the entire job that have INTEGER: The number of copies of the entire job that have
been completed so far. been completed so far.
documentCopiesRequested(92), Integer32(-2..2147483647) documentCopiesRequested(92), Integer32(-2..2147483647)
INTEGER: The total count of the number of document copies INTEGER: The total count of the number of document copies
Job Monitoring MIB, V0.83 July 14, 1997
requested. If there are documents A, B, and C, and document requested. If there are documents A, B, and C, and document
B is specified to produce 4 copies, the number of document B is specified to produce 4 copies, the number of document
copies requested is 6 for the job. copies requested is 6 for the job.
This attribute SHALL be used only when a job has multiple This attribute SHALL be used only when a job has multiple
documents. The jobCopiesRequested attribute SHALL be used documents. The jobCopiesRequested attribute SHALL be used
when the job has only one document. when the job has only one document.
documentCopiesCompleted(93), Integer32(-2..2147483647) documentCopiesCompleted(93), Integer32(-2..2147483647)
INTEGER: The total count of the number of document copies INTEGER: The total count of the number of document copies
skipping to change at page 52, line 35 skipping to change at page 55, 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.84 July 21, 1997
'1', 1025-2048 SHALL be '2', etc. When the job completes, '1', 1025-2048 SHALL be '2', etc. When the job completes,
the values of the jmJobKOctetsRequested object and the the values of the jmJobKOctetsRequested object and the
jobKOctetsTransferred attribute SHALL be equal. jobKOctetsTransferred attribute SHALL be equal.
NOTE - The jobKOctetsTransferred can be used with the NOTE - The jobKOctetsTransferred can be used with the
jmJobKOctetsRequested object in order to produce a relative jmJobKOctetsRequested object in order to produce a relative
indication of the progress of the job for agents that do not indication of the progress of the job for agents that do not
implement the jmJobKOctetsProcessed object. implement the jmJobKOctetsProcessed object.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ 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.
Job Monitoring MIB, V0.83 July 14, 1997
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
impressionsSpooled(110), Integer32(-2..2147483647) impressionsSpooled(110), Integer32(-2..2147483647)
INTEGER: The number of impressions spooled to the server or INTEGER: The number of impressions spooled to the server or
device for the job so far. device for the job so far.
impressionsSentToDevice(111), Integer32(-2..2147483647) impressionsSentToDevice(111), Integer32(-2..2147483647)
INTEGER: The number of impressions sent to the device for INTEGER: The number of impressions sent to the device for
the job so far. the job so far.
skipping to change at page 53, line 36 skipping to change at page 56, 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.84 July 21, 1997
stacking the output. For other types of job services, the stacking the output. For other types of job services, the
number of impressions completed includes the number of number of impressions completed includes the number of
impressions processed. Full color impressions are typically impressions processed. Full color impressions are typically
defined as those requiring 3 or more colorants, but this MAY defined as those requiring 3 or more colorants, but this MAY
vary by implementation. vary by implementation.
highlightColorImpressionsCompleted(115), Integer32(-2.. highlightColorImpressionsCompleted(115), Integer32(-2..
2147483647) 2147483647)
INTEGER: The number of highlight color impressions INTEGER: The number of highlight color impressions
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.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.83 July 14, 1997
+ Page attributes + Page attributes
+ +
+ A page is a logical page. Number up can impose more than + A page is a logical page. Number up can impose more than
+ one page on a single side of a sheet. Two-up is the + one page on a single side of a sheet. Two-up is the
+ placement of two logical pages on one side of a sheet so + placement of two logical pages on one side of a sheet so
+ that each side counts as two pages. + that each side counts as two pages.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
pagesRequested(130), Integer32(-2..2147483647) pagesRequested(130), Integer32(-2..2147483647)
INTEGER: The number of logical pages requested by the job INTEGER: The number of logical pages requested by the job
skipping to change at page 54, line 35 skipping to change at page 57, line 5
reset to 0 for each document in the job and for each reset to 0 for each document in the job and for each
document copy. document copy.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Sheet attributes + Sheet attributes
+ +
+ The sheet is a single piece of a medium, whether printing + The sheet is a single piece of a medium, whether printing
+ on one or both sides. + on one or both sides.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Job Monitoring MIB, V0.84 July 21, 1997
sheetsRequested(150), Integer32(-2..2147483647) sheetsRequested(150), Integer32(-2..2147483647)
INTEGER: The number of medium sheets requested to be INTEGER: The number of medium sheets requested to be
processed for this job. processed for this job.
sheetsCompleted(151), Integer32(-2..2147483647) sheetsCompleted(151), Integer32(-2..2147483647)
INTEGER: The number of medium sheets that have completed INTEGER: The number of medium sheets that have completed
marking and stacking for the entire job so far whether those marking and stacking for the entire job so far whether those
sheets have been processed on one side or on both. sheets have been processed on one side or on both.
sheetsCompletedCurrentCopy(152), Integer32(-2..2147483647) sheetsCompletedCurrentCopy(152), Integer32(-2..2147483647)
INTEGER: The number of medium sheets that have completed INTEGER: The number of medium sheets that have completed
marking and stacking for the current copy of a document in marking and stacking for the current copy of a document in
the job so far whether those sheets have been processed on the job so far whether those sheets have been processed on
one side or on both. one side or on both.
The value of this attribute SHALL be reset to 0 as each The value of this attribute SHALL be reset to 0 as each
document in the job starts being processed and for each document in the job starts being processed and for each
document copy as it starts being processed. document copy as it starts being processed.
Job Monitoring MIB, V0.83 July 14, 1997
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) + Resources attributes (requested and consumed)
+ +
+ Pairs of these attributes can be used by monitoring + Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to + applications to show an indication of relative usage to
+ users. + users.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mediumRequested(170), JmMediumTypeTC mediumRequested(170), JmMediumTypeTC
AND/OR AND/OR
skipping to change at page 55, line 34 skipping to change at page 58, line 5
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: The number of sheets INTEGER: The number of sheets
AND AND
OCTETS: MULTI-ROW: the name of the medium that have been OCTETS: MULTI-ROW: the name of the medium that have been
consumed so far whether those sheets have been processed on consumed so far whether those sheets have been processed on
one side or on both. one side or on both.
This attribute SHALL have both Integer32 and OCTET STRING This attribute SHALL have both Integer32 and OCTET STRING
values. values.
Job Monitoring MIB, V0.84 July 21, 1997
colorantRequested(172), Integer32(-2..2147483647) colorantRequested(172), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in
the Printer MIB[print-mib] the Printer MIB[print-mib]
AND/OR AND/OR
OCTETS: the name of the colorant requested. OCTETS: the name of the colorant requested.
colorantConsumed(173), Integer32(-2..2147483647) colorantConsumed(173), Integer32(-2..2147483647)
AND/OR AND/OR
OCTET STRING(SIZE(0..63)) OCTET STRING(SIZE(0..63))
INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in
the Printer MIB[print-mib] the Printer MIB[print-mib]
AND/OR AND/OR
OCTETS: the name of the colorant consumed. OCTETS: the name of the colorant consumed.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Time attributes (set by server or device) + Time attributes (set by server or device)
Job Monitoring MIB, V0.83 July 14, 1997
+ +
+ This section of attributes are ones that are set by the + This section of attributes are ones that are set by the
+ server or device that accepts jobs. Two forms of time are + server or device that accepts jobs. Two forms of time are
+ provided. Each form is represented in a separate attribute. + provided. Each form is represented in a separate attribute.
+ See section 3.1.2 and section 3.1.3 for the + See section 3.1.2 and section 3.1.3 for the
+ conformance requirements for time attribute for agents and + conformance requirements for time attribute for agents and
+ monitoring applications, respectively. The two forms are: + monitoring applications, respectively. The two forms are:
+ +
+ 'DateAndTime' is an 8 or 11 octet binary encoded year, + 'DateAndTime' is an 8 or 11 octet binary encoded year,
+ month, day, hour, minute, second, deci-second with + month, day, hour, minute, second, deci-second with
+ optional offset from UTC. See SNMPv2-TC. + optional offset from UTC. See SNMPv2-TC [SMIv2-TC].
+ +
+ NOTE: 'DateAndTime' is not printable characters; it is + NOTE: 'DateAndTime' is not printable characters; it is
+ binary. + binary.
+ +
+ 'JmTimeStampTC' is the time of day measured in the number of + 'JmTimeStampTC' is the time of day measured in the number of
+ seconds since the system was booted. + seconds since the system was booted.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobSubmissionToServerTime(190), JmTimeStampTC jobSubmissionToServerTime(190), JmTimeStampTC
AND/OR AND/OR
DateAndTime (SNMPv2-TC) DateAndTime
INTEGER: Configuration 3 only: The time INTEGER: Configuration 3 only: The time
AND/OR AND/OR
OCTETS: the date and time that the job was submitted to the OCTETS: the date and time that the job was submitted to the
server (as distinguished from the device which uses server (as distinguished from the device which uses
jobSubmissionTime). jobSubmissionTime).
Job Monitoring MIB, V0.84 July 21, 1997
jobSubmissionTime(191), JmTimeStampTC jobSubmissionTime(191), JmTimeStampTC
AND/OR AND/OR
DateAndTime (SNMPv2-TC) DateAndTime
INTEGER: Configurations 1, 2, and 3: The time INTEGER: Configurations 1, 2, and 3: The time
AND/OR AND/OR
OCTETS: the date and time that the job was submitted to the OCTETS: the date and time that the job was submitted to the
server or device to which the agent is providing access. server or device to which the agent is providing access.
jobStartedBeingHeldTime(192), JmTimeStampTC jobStartedBeingHeldTime(192), JmTimeStampTC
AND/OR AND/OR
DateAndTime (SNMPv2-TC) DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job last entered the OCTETS: the date and time that the job last entered the
pendingHeld state. If the job has never entered the pendingHeld state. If the job has never entered the
pendingHeld state, then the value SHALL be '0' or the pendingHeld state, then the value SHALL be '0' or the
attribute SHALL not be present in the table. attribute SHALL not be present in the table.
Job Monitoring MIB, V0.83 July 14, 1997
jobStartedProcessingTime(193), JmTimeStampTC jobStartedProcessingTime(193), JmTimeStampTC
AND/OR AND/OR
DateAndTime (SNMPv2-TC) 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 jobCompletedTime(194), JmTimeStampTC
AND/OR AND/OR
DateAndTime (SNMPv2-TC) DateAndTime
INTEGER: The time INTEGER: The time
AND/OR AND/OR
OCTETS: the date and time that the job entered the OCTETS: the date and time that the job entered the
completed, canceled, or aborted state. completed, canceled, or aborted state.
jobProcessingCPUTime(195) Integer32(-2..2147483647) jobProcessingCPUTime(195) Integer32(-2..2147483647)
UNITS 'seconds' UNITS 'seconds'
INTEGER: The amount of CPU time in seconds that the job has INTEGER: The amount of CPU time in seconds that the job has
been in the processing state. If the job enters the been in the processing state. If the job enters the
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 'When the server or device is power- "See Section 3.2 entitled 'The Attribute Mechanism' for a
cycled, the agent SHALL remember the next jmJobIndex value to be description of this textual-convention and its use in the
assigned, so that new jobs are not assigned the same jmJobIndex jmAttributeTable.
as recent jobs before the power cycle.
The Attribute Mechanism' for a description of this textual- Job Monitoring MIB, V0.84 July 21, 1997
convention and its use in the 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),
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),
Job Monitoring MIB, V0.83 July 14, 1997
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),
skipping to change at page 58, line 37 skipping to change at page 61, line 4
printQualityUsed(71), printQualityUsed(71),
printerResolutionRequested(72), printerResolutionRequested(72),
printerResolutionUsed(73), printerResolutionUsed(73),
tonerEcomonyRequested(74), tonerEcomonyRequested(74),
tonerEcomonyUsed(75), tonerEcomonyUsed(75),
tonerDensityRequested(76), tonerDensityRequested(76),
tonerDensityUsed(77), tonerDensityUsed(77),
jobCopiesRequested(90), jobCopiesRequested(90),
jobCopiesCompleted(91), jobCopiesCompleted(91),
Job Monitoring MIB, V0.84 July 21, 1997
documentCopiesRequested(92), documentCopiesRequested(92),
documentCopiesCompleted(93), documentCopiesCompleted(93),
jobKOctetsTransferred(94), jobKOctetsTransferred(94),
impressionsSpooled(110), impressionsSpooled(110),
impressionsSentToDevice(111), impressionsSentToDevice(111),
impressionsInterpreted(112), impressionsInterpreted(112),
impressionsCompletedCurrentCopy(113), impressionsCompletedCurrentCopy(113),
fullColorImpressionsCompleted(114), fullColorImpressionsCompleted(114),
highlightColorImpressionsCompleted(115), highlightColorImpressionsCompleted(115),
pagesRequested(130), pagesRequested(130),
pagesCompleted(131), pagesCompleted(131),
pagesCompletedCurrentCopy(132), pagesCompletedCurrentCopy(132),
sheetsRequested(150), sheetsRequested(150),
sheetsCompleted(151), sheetsCompleted(151),
Job Monitoring MIB, V0.83 July 14, 1997
sheetsCompletedCurrentCopy(152), sheetsCompletedCurrentCopy(152),
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),
skipping to change at page 59, line 32 skipping to change at page 62, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the type(s) of service to which the job has been "Specifies the type(s) of service to which the job has been
submitted (print, fax, scan, etc.). The service type is submitted (print, fax, scan, etc.). The service type is
represented as an enum that is bit encoded with each job service represented as an enum that is bit encoded with each job service
type so that more general and arbitrary services can be created, type so that more general and arbitrary services can be created,
such as services with more than one destination type, or ones such as services with more than one destination type, or ones
with only a source or only a destination. For example, a job with only a source or only a destination. For example, a job
service might scan, faxOut, and print a single job. In this service might scan, faxOut, and print a single job. In this
case, three bits would be set in the jobServiceTypes attribute, case, three bits would be set in the jobServiceTypes attribute,
Job Monitoring MIB, V0.84 July 21, 1997
corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4,
respectively, yielding: 0x2C. respectively, yielding: 0x2C.
Whether this attribute is set from a job attribute supplied by Whether this attribute is set from a job attribute supplied by
the job submission client or is set by the recipient job the job submission client or is set by the recipient job
submission server or device depends on the job submission submission server or device depends on the job submission
protocol. With either implementation, the agent SHALL return a protocol. With either implementation, the agent SHALL return a
non-zero value for this attribute indicating the type of the non-zero value for this attribute indicating the type of the
job. job.
One of the purposes of this attribute is to permit a requester One of the purposes of this attribute is to permit a requester
to filter out jobs that are not of interest. For example, a to filter out jobs that are not of interest. For example, a
printer operator MAY only be interested in jobs that include printer operator MAY only be interested in jobs that include
printing. That is why the attribute is in the job printing. That is why the attribute is in the job
identification category. identification category.
Job Monitoring MIB, V0.83 July 14, 1997
The following service component types are defined (in The following service component types are defined (in
hexadecimal) and are assigned a separate bit value for use with hexadecimal) and are assigned a separate bit value for use with
the jobServiceTypes attribute: the jobServiceTypes attribute:
other 0x1 other 0x1
The job contains some 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
skipping to change at page 60, line 39 skipping to change at page 63, line 5
The job contains some instructions that specify sending fax The job contains some instructions that specify sending fax
getFile 0x40 getFile 0x40
The job contains some instructions that specify accessing The job contains some instructions that specify accessing
files or documents files or documents
putFile 0x80 putFile 0x80
The job contains some instructions that specify storing The job contains some instructions that specify storing
files or documents files or documents
Job Monitoring MIB, V0.84 July 21, 1997
mailList 0x100 mailList 0x100
The job contains some instructions that specify distribution The job contains some instructions that specify distribution
of documents using an electronic mail system." of documents using an electronic mail system."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them MAY be used together. See except that combinations of them MAY be used together. See
section 3.6.1.2." section 3.6.1.2."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.83 July 14, 1997
JmJobStateReasons1TC ::= TEXTUAL-CONVENTION JmJobStateReasons1TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 provides 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
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
skipping to change at page 61, line 35 skipping to change at page 63, line 45
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 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 reason is most reasons are presented in the order in which the reasons are
likely to occur, not counting the 'other' and 'unknown' reasons. likely to occur (if implemented), starting with the
Job Monitoring MIB, V0.84 July 21, 1997
'jobIncoming' value and ending with 'jobCompletedWithErrors'
reasons.
other 0x1 other 0x1
The job state reason is not one of the standardized or The job state reason is not one of the standardized or
registered reasons. registered reasons.
unknown 0x2 unknown 0x2
The job state reason is not known to the agent or is The job state reason is not known to the agent or is
indeterminent. indeterminent.
jobIncoming 0x4 jobIncoming 0x4
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.
Job Monitoring MIB, V0.83 July 14, 1997
jobOutgoing 0x8 jobOutgoing 0x8
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 jobHoldSpecified 0x10
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 0x20
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 0x40
The value of the job's jobProcessAfterDateAndTime(51) The value of the job's jobProcessAfterDateAndTime(51)
attribute specifies a time that is still in the future, attribute specifies a time that is still in the future. The
either set when the job was created or subsequently by an job SHALL NOT be a candidate for processing until this
explicit modify job operation. The job SHALL NOT be a reason is removed and there are no other reasons to hold the
candidate for processing until this reason is removed and job.
there are no other reasons to hold the job.
resourcesAreNotReady 0x80 resourcesAreNotReady 0x80
At least one of the resources needed by the job, such as At least one of the resources needed by the job, such as
media, fonts, resource objects, etc., is not ready on any of media, fonts, resource objects, etc., is not ready on any of
the physical devices for which the job is a candidate. This the physical devices for which the job is a candidate. This
condition MAY be detected when the job is accepted, or condition MAY be detected when the job is accepted, or
subsequently while the job is pending or processing, subsequently while the job is pending or processing,
depending on implementation. depending on implementation.
Job Monitoring MIB, V0.84 July 21, 1997
deviceStoppedPartly 0x100 deviceStoppedPartly 0x100
One or more, but not all, of the devices to which the job is One or more, but not all, of the devices to which the job is
assigned are stopped. If all of the devices are stopped (or assigned are stopped. If all of the devices are stopped (or
the only device is stopped), the deviceStopped reason SHALL the only device is stopped), the deviceStopped reason SHALL
be used. be used.
deviceStopped 0x200 deviceStopped 0x200
The device(s) to which the job is assigned is (are all) The device(s) to which the job is assigned is (are all)
stopped. stopped.
jobPrinting 0x400 jobPrinting 0x400
The output device is marking media. This attribute is useful The output device is marking media. This attribute is useful
for servers and output devices which spend a great deal of for servers and output devices which spend a great deal of
time processing when no marking is happening and then want time processing when no marking is happening and then want
to show that marking is now happening or when the job is in to show that marking is now happening or when the job is in
the canceled or aborted state, but the marking has not yet the canceled or aborted state, but the marking has not yet
Job Monitoring MIB, V0.83 July 14, 1997
stopped so that impression or sheet counts are still stopped so that impression or sheet counts are still
increasing for the job. increasing for the job.
jobCanceledByUser 0x800 jobCanceledByUser 0x800
The job was canceled by the user, i.e., by an unknown user The job was canceled by the user, i.e., by an unknown user
or by a user whose name is the same as the value of the or by a user whose name is the same as the value of the
job's jmJobOwner object. job's jmJobOwner object.
jobCanceledByOperator 0x1000 jobCanceledByOperator 0x1000
The job was canceled by the operator, i.e., by a user whose The job was canceled by the operator, i.e., by a user whose
name is different than the value of the job's jmJobOwner name is different than the value of the job's jmJobOwner
object. object.
abortedBySystem 0x2000 abortedBySystem 0x2000
The job was aborted by the system. The job was aborted by the system.
NOTE - this reason is needed only when the system aborts a NOTE - When the system puts a job into the 'aborted' job
job, but does not put the job in the aborted job state. For state, this reason is not needed. This reason is needed
example, if the system aborts the job, but places the job in only when the system aborts a job, but, instead of placing
the pendingHeld state, so that a user or operator can try the job in the aborted job state, places the job in the
the job again. pendingHeld state, so that a user or operator can manually
try the job again.
jobCompletedSuccessfully 0x4000 jobCompletedSuccessfully 0x4000
The job completed successfully. The job completed successfully.
jobCompletedWithWarnings 0x8000 jobCompletedWithWarnings 0x8000
The job completed with warnings. The job completed with warnings.
jobCompletedWithErrors 0x10000 jobCompletedWithErrors 0x10000
The job completed with errors (and possibly warnings too). The job completed with errors (and possibly warnings too).
Job Monitoring MIB, V0.84 July 21, 1997
The following additional job state reasons have been added The following additional job state reasons have been added
to represent job states that are in ISO DPA[iso-dpa] and to represent job states that are in ISO DPA[iso-dpa] and
other job submission protocols: other job submission protocols:
jobPaused 0x20000 jobPaused 0x20000
The job has been indefinitely suspended by a client issuing The job has been indefinitely suspended by a client issuing
an operation to suspend the job so that other jobs may an operation to suspend the job so that other jobs may
proceed using the same devices. The client MAY issue an proceed using the same devices. The client MAY issue an
operation to resume the paused job at any time, in which operation to resume the paused job at any time, in which
case the agent SHALL remove the jobPaused values from the case the agent SHALL remove the jobPaused values from the
job's jmJobStateReasons1 object and the job is eventually job's jmJobStateReasons1 object and the job is eventually
resumed at or near the point where the job was paused. resumed at or near the point where the job was paused.
jobInterrupted 0x40000 jobInterrupted 0x40000
The job has been interrupted while processing by a client The job has been interrupted while processing by a client
issuing an operation that specifies another job to be run issuing an operation that specifies another job to be run
instead of the current job. The server or device will instead of the current job. The server or device will
Job Monitoring MIB, V0.83 July 14, 1997
automatically resume the interrupted job when the automatically resume the interrupted job when the
interrupting job completes. interrupting job completes.
jobRetained 0x80000 jobRetained 0x80000
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
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
skipping to change at page 64, line 33 skipping to change at page 67, line 4
standardization and/or registration." standardization and/or registration."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons2TC ::= TEXTUAL-CONVENTION JmJobStateReasons2TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons2 "This textual-convention is used with the jobStateReasons2
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState object. See the description under jmJobState object. See the description under
Job Monitoring MIB, V0.84 July 21, 1997
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
cascaded 0x1 cascaded 0x1
An outbound gateway has transmitted all of the job's job and An outbound gateway has transmitted all of the job's job and
document attributes and data to another spooling system. document attributes and data to another spooling system.
deletedByAdministrator 0x2 deletedByAdministrator 0x2
The administrator has deleted the job. The administrator has deleted the job.
discardTimeArrived 0x4 discardTimeArrived 0x4
The job has been deleted due to the fact that the time The job has been deleted due to the fact that the time
Job Monitoring MIB, V0.83 July 14, 1997
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
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.
skipping to change at page 65, line 38 skipping to change at page 68, line 4
administratively defined fault count limit. administratively defined fault count limit.
devicesNeedAttentionTimeOut 0x40 devicesNeedAttentionTimeOut 0x40
One or more document transforms that the job is using needs One or more document transforms that the job is using needs
human intervention in order for the job to make progress, human intervention in order for the job to make progress,
but the human intervention did not occur within the site- but the human intervention did not occur within the site-
settable time-out value. settable time-out value.
needsKeyOperatorTimeOut 0x80 needsKeyOperatorTimeOut 0x80
One or more devices or document transforms that the job is One or more devices or document transforms that the job is
Job Monitoring MIB, V0.84 July 21, 1997
using need a specially trained operator (who may need a key using need a specially trained operator (who may need a key
to unlock the device and gain access) in order for the job to unlock the device and gain access) in order for the job
to make progress, but the key operator intervention did not to make progress, but the key operator intervention did not
occur within the site-settable time-out value. occur within the site-settable time-out value.
jobStartWaitTimeOut 0x100 jobStartWaitTimeOut 0x100
The server/device has stopped the job at the beginning of The server/device has stopped the job at the beginning of
processing to await human action, such as installing a processing to await human action, such as installing a
special cartridge or special non-standard media, but the job special cartridge or special non-standard media, but the job
was not resumed within the site-settable time-out value and was not resumed within the site-settable time-out value and
the server/device has transitioned the job to the the server/device has transitioned the job to the
pendingHeld state. pendingHeld state.
jobEndWaitTimeOut 0x200 jobEndWaitTimeOut 0x200
The server/device has stopped the job at the end of The server/device has stopped the job at the end of
processing to await human action, such as removing a special processing to await human action, such as removing a special
Job Monitoring MIB, V0.83 July 14, 1997
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
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.
skipping to change at page 66, line 39 skipping to change at page 69, line 5
The job is being transferred to a down stream server or The job is being transferred to a down stream server or
device. device.
queuedInDevice 0x4000 queuedInDevice 0x4000
The job has been queued in a down stream server or device. The job has been queued in a down stream server or device.
jobCleanup 0x8000 jobCleanup 0x8000
The server/device is performing cleanup activity as part of The server/device is performing cleanup activity as part of
ending normal processing. ending normal processing.
Job Monitoring MIB, V0.84 July 21, 1997
processingToStopPoint 0x10000 processingToStopPoint 0x10000
The requester has issued an operation to interrupt the job The requester has issued an operation to interrupt the job
and the server/device is processing up until the specified and the server/device is processing up until the specified
stop point occurs. stop point occurs.
jobPasswordWait 0x20000 jobPasswordWait 0x20000
The server/device has selected the job to be next to The server/device has selected the job to be next to
process, but instead of assigning resources and starting the process, but instead of assigning resources and starting the
job processing, the server/device has transitioned the job job processing, the server/device has transitioned the job
to the pendingHeld state to await entry of a password (and to the pendingHeld state to await entry of a password (and
dispatched another job, if there is one). dispatched another job, if there is one).
validating 0x40000 validating 0x40000
The server/device is validating the job after accepting the The server/device is validating the job after accepting the
job. job.
Job Monitoring MIB, V0.83 July 14, 1997
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.
skipping to change at page 67, line 38 skipping to change at page 70, line 4
pinRequired 0x1000000 pinRequired 0x1000000
The System Administrator settable device policy is (1) to The System Administrator settable device policy is (1) to
require PINs, and (2) to hold jobs that do not have a pin require PINs, and (2) to hold jobs that do not have a pin
supplied as an input parameter when the job was created. supplied as an input parameter when the job was created.
exceededAccountLimit 0x2000000 exceededAccountLimit 0x2000000
The account for which this job is drawn has exceeded its The account for which this job is drawn has exceeded its
limit. This condition SHOULD be detected before the job is limit. This condition SHOULD be detected before the job is
scheduled so that the user does not wait until his/her job scheduled so that the user does not wait until his/her job
Job Monitoring MIB, V0.84 July 21, 1997
is scheduled only to find that the account is overdrawn. is scheduled only to find that the account is overdrawn.
This condition MAY also occur while the job is processing This condition MAY also occur while the job is processing
either as processing begins or part way through processing. either as processing begins or part way through processing.
heldForRetry 0x4000000 heldForRetry 0x4000000
The job encountered some errors that the server/device could The job encountered some errors that the server/device could
not recover from with its normal retry procedures, but the not recover from with its normal retry procedures, but the
error might not be encountered if the job is re-tried in the error might not be encountered if the job is processed again
future, such as phone number busy or remote file system in- in the future. Example cases are phone number busy or
accessible. For such a situation, the server/device SHALL remote file system in-accessible. For such a situation, the
transition the job from the processing to the pendingHeld, server/device SHALL transition the job from the processing
rather than to the aborted state. to the pendingHeld, rather than to the aborted state.
The following values are from the X/Open PSIS draft standard: The following values are from the X/Open PSIS draft standard:
Job Monitoring MIB, V0.83 July 14, 1997
canceledByShutdown 0x8000000 canceledByShutdown 0x8000000
The job was canceled because the server or device was The job was canceled because the server or device was
shutdown 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
skipping to change at page 68, line 35 skipping to change at page 71, line 4
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them may be used together. See except that combinations of them may be used together. See
section 3.6.1.2. See the description under JmJobStateReasons1TC section 3.6.1.2. See the description under JmJobStateReasons1TC
and the jobStateReasons2 attribute." and the jobStateReasons2 attribute."
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
JmJobStateReasons3TC ::= TEXTUAL-CONVENTION JmJobStateReasons3TC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"This textual-convention is used with the jobStateReasons3 "This textual-convention is used with the jobStateReasons3
attribute to provides additional information regarding the attribute to provides additional information regarding the
jmJobState object. See the description under jmJobState object. See the description under
JmJobStateReasons1TC for additional information that applies to JmJobStateReasons1TC for additional information that applies to
all reasons. all reasons.
The following standard values are defined (in hexadecimal) as The following standard values are defined (in hexadecimal) as
powers of two, since multiple values may be used at the same powers of two, since multiple values may be used at the same
time: time:
jobInterruptedByDeviceFailure 0x1 jobInterruptedByDeviceFailure 0x1
A device or the print system software that the job was using A device or the print system software that the job was using
has failed while the job was processing. The server or has failed while the job was processing. The server or
Job Monitoring MIB, V0.83 July 14, 1997
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
skipping to change at page 69, line 37 skipping to change at page 72, line 5
time: time:
none yet defined. These bits are reserved for future none yet defined. These bits are reserved for future
standardization and/or registration." standardization and/or registration."
REFERENCE REFERENCE
"These bit definitions are the equivalent of a type 2 enum "These bit definitions are the equivalent of a type 2 enum
except that combinations of them may be used together. See except that combinations of them may be used together. See
section 3.6.1.2. See the description under JmJobStateReasons1TC section 3.6.1.2. See the description under JmJobStateReasons1TC
and the jobStateReasons4 attribute." and the jobStateReasons4 attribute."
Job Monitoring MIB, V0.84 July 21, 1997
SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 } jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 }
- -- The General Group (MANDATORY)
- -- The jmGeneralGroup consists entirely of the jmGeneralTable.
jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 } jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 }
jmGeneralTable OBJECT-TYPE jmGeneralTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmGeneralEntry SYNTAX SEQUENCE OF JmGeneralEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmGeneralTable consists of information of a general nature "The jmGeneralTable consists of information of a general nature
that are per-job-set, but are not per-job. See Section 2 that are per-job-set, but are not per-job. See Section 2
skipping to change at page 71, 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 OCTET STRING(SIZE(0..63)) jmGeneralJobSetName OCTET STRING(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.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"A unique value for each job set in this MIB. The jmJobTable "A unique value for each job set in this MIB. The jmJobTable
and jmAttributeTable tables have this same index as their and jmAttributeTable tables have this same index as their
primary index. primary index.
The value(s) of the jmGeneralJobSetIndex SHALL be persistent The value(s) of the jmGeneralJobSetIndex SHALL be persistent
across power cycles, so that clients that have retained across power cycles, so that clients that have retained
jmGeneralJobSetIndex values will access the same job sets upon jmGeneralJobSetIndex values will access the same job sets upon
subsequent power-up. subsequent power-up.
An implementation that has only one job set, such as a printer An implementation that has only one job set, such as a printer
with a single queue, SHALL hard code this object with the value with a single queue, SHALL hard code this object with the value
1." 1."
REFERENCE REFERENCE
"See Section 2 entitled 'Terminology and Job Model' for the "See Section 2 entitled 'Terminology and Job Model' for the
definition of a job set. Corresponds to the first index in definition of a job set.
jmJobTable and jmAttributeTable." Corresponds to the first index in jmJobTable and
jmAttributeTable."
::= { jmGeneralEntry 1 } ::= { jmGeneralEntry 1 }
jmGeneralNumberOfActiveJobs OBJECT-TYPE jmGeneralNumberOfActiveJobs OBJECT-TYPE
SYNTAX Integer32(0..2147483647) SYNTAX Integer32(0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of 'active' jobs in the jmJobIDTable, "The current number of 'active' jobs in the jmJobIDTable,
jmJobTable, and jmAttributeTable, i.e., the total number of jobs jmJobTable, and jmAttributeTable, i.e., the total number of jobs
that are in the pending, processing, or processingStopped that are in the pending, processing, or processingStopped
skipping to change at page 71, line 53 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.84 July 21, 1997
::= { jmGeneralEntry 3 } ::= { jmGeneralEntry 3 }
Job Monitoring MIB, V0.83 July 14, 1997
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
words, the index of the 'active' job that has been most recently words, the index of the 'active' job that has been most recently
added to the job tables. added to the job tables.
skipping to change at page 72, line 52 skipping to change at page 76, line 4
jmGeneralAttributePersistence. This value SHOULD be at least 60 jmGeneralAttributePersistence. This value SHOULD be at least 60
which gives a monitoring application one minute in which to poll which gives a monitoring application one minute in which to poll
for job data." for job data."
DEFVAL { 60 } -- one minute DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 5 } ::= { jmGeneralEntry 5 }
jmGeneralAttributePersistence OBJECT-TYPE jmGeneralAttributePersistence OBJECT-TYPE
SYNTAX Integer32(15..2147483647) SYNTAX Integer32(15..2147483647)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
STATUS current
DESCRIPTION DESCRIPTION
"The minimum time in seconds for this instance of the Job Set "The minimum time in seconds for this instance of the Job Set
that an entry SHALL remain in the jmAttributeTable after that an entry SHALL remain in the jmAttributeTable after
processing has completed , i.e., the time in seconds starting processing has completed , i.e., the time in seconds starting
when the job enters the completed, canceled, or aborted state. when the job enters the completed, canceled, or aborted state.
Depending on implementation, the value of this object MAY be Depending on implementation, the value of this object MAY be
either (1) set by the system administrator by means outside this either (1) set by the system administrator by means outside this
specification or MAY be (2) fixed by the implementation. specification or MAY be (2) fixed by the implementation.
skipping to change at page 73, line 42 skipping to change at page 76, line 44
single Job Monitoring MIB SHOULD have distinct names. single Job Monitoring MIB SHOULD have distinct names.
NOTE - The purpose of this object is to help the user of the job NOTE - The purpose of this object is to help the user of the job
monitoring application distinguish between several job sets in monitoring application distinguish between several job sets in
implementations that support more than one job set." implementations that support more than one job set."
REFERENCE REFERENCE
"See the OBJECT compliance macro for the minimum maximum length "See the OBJECT compliance macro for the minimum maximum length
required for conformance." required for conformance."
::= { jmGeneralEntry 7 } ::= { jmGeneralEntry 7 }
- -- The Job ID Group (MANDATORY)
- -- The jmJobIDGroup consists entirely of the jmJobIDTable.
jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 } jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 }
jmJobIDTable OBJECT-TYPE jmJobIDTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmJobIDEntry
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
SYNTAX SEQUENCE OF JmJobIDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobIDTable provides a correspondence map (1) between the "The jmJobIDTable provides a correspondence map (1) between the
job submission ID that a client uses to refer to a job and (2) job submission ID that a client uses to refer to a job and (2)
the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring
MIB agent assigned to the job and that are used to access the MIB agent assigned to the job and that are used to access the
job in all of the other tables in the MIB. If a monitoring job in all of the other tables in the MIB. If a monitoring
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
skipping to change at page 74, line 52 skipping to change at page 78, line 4
jmJobSubmissionID OBJECT-TYPE jmJobSubmissionID OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(48)) SYNTAX OCTET STRING(SIZE(48))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A quasi-unique 48-octet fixed-length string ID which identifies "A quasi-unique 48-octet fixed-length string ID which identifies
the job within a particular client-server environment. There the job within a particular client-server environment. There
are multiple formats for the jmJobSubmissionID. See the are multiple formats for the jmJobSubmissionID. See the
JmJobSubmissionIDTypeTC textual convention. Each format SHALL JmJobSubmissionIDTypeTC textual convention. Each format SHALL
be registered using the procedures of a type 2 enum. See be registered using the procedures of a type 2 enum. See
Job Monitoring MIB, V0.84 July 21, 1997
section 3.6.3 entitled: 'IANA Registration of Job Submission Id section 3.6.3 entitled: 'IANA Registration of Job Submission Id
Formats'. Formats'.
Job Monitoring MIB, V0.83 July 14, 1997
If the requester (client or server) does not supply a job If the requester (client or server) does not supply a job
submission ID in the job submission protocol, then the recipient submission ID in the job submission protocol, then the recipient
(server or device) SHALL assign a job submission ID using any of (server or device) SHALL assign a job submission ID using any of
the standard formats and adding the final 8 octets to the standard formats and adding the final 8 octets to
distinguish the ID from others submitted from the same distinguish the ID from others submitted from the same
requester. 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
skipping to change at page 75, line 52 skipping to change at page 79, line 4
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
"This object contains the value of the jmJobIndex for the job "This object contains the value of the jmJobIndex for the job
with the jmJobSubmissionID value, i.e., the job index for the with the jmJobSubmissionID value, i.e., the job index for the
job when the server or device accepted the job. This value, in job when the server or device accepted the job. This value, in
combination with the jmJobIDJobSetIndex value, permits the combination with the jmJobIDJobSetIndex value, permits the
Job Monitoring MIB, V0.84 July 21, 1997
management application to access the other tables to obtain the management application to access the other tables to obtain the
job-specific objects for this job." job-specific objects for this job."
Job Monitoring MIB, V0.83 July 14, 1997
REFERENCE REFERENCE
"See jmJobIndex in the jmJobTable." "See jmJobIndex in the jmJobTable."
::= { jmJobIDEntry 3 } ::= { jmJobIDEntry 3 }
- -- The Job Group (MANDATORY)
- -- The jmJobGroup consists entirely of the jmJobTable.
jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 } jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 }
jmJobTable OBJECT-TYPE jmJobTable OBJECT-TYPE
SYNTAX SEQUENCE OF JmJobEntry SYNTAX SEQUENCE OF JmJobEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmJobTable consists of basic job state and status "The jmJobTable consists of basic job state and status
information for each job in a job set that (1) monitoring information for each job in a job set that (1) monitoring
skipping to change at page 76, line 49 skipping to change at page 80, line 4
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 }
JmJobEntry ::= SEQUENCE { JmJobEntry ::= SEQUENCE {
jmJobIndex Integer32(1..2147483647), jmJobIndex Integer32(1..2147483647),
jmJobState JmJobStateTC, jmJobState JmJobStateTC,
Job Monitoring MIB, V0.84 July 21, 1997
jmJobStateReasons1 JmJobStateReasons1TC, jmJobStateReasons1 JmJobStateReasons1TC,
jmNumberOfInterveningJobs Integer32(-2..2147483647), jmNumberOfInterveningJobs Integer32(-2..2147483647),
Job Monitoring MIB, V0.83 July 14, 1997
jmJobKOctetsRequested Integer32(-2..2147483647), jmJobKOctetsRequested Integer32(-2..2147483647),
jmJobKOctetsProcessed Integer32(-2..2147483647), jmJobKOctetsProcessed Integer32(-2..2147483647),
jmJobImpressionsRequested Integer32(-2..2147483647), jmJobImpressionsRequested Integer32(-2..2147483647),
jmJobImpressionsCompleted Integer32(-2..2147483647), jmJobImpressionsCompleted Integer32(-2..2147483647),
jmJobOwner OCTET STRING(SIZE(0..63)) jmJobOwner OCTET STRING(SIZE(0..63))
} }
jmJobIndex OBJECT-TYPE jmJobIndex OBJECT-TYPE
SYNTAX Integer32(1..2147483647) SYNTAX Integer32(1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 77, line 29 skipping to change at page 80, line 32
the job generated by the server or device when that server or the job generated by the server or device when that server or
device accepted the job. This index value permits the device accepted the job. This index value permits the
management application to access the other tables to obtain the management application to access the other tables to obtain the
job-specific row entries. job-specific row entries.
Agents providing access to systems that contain jobs with a job Agents providing access to systems that contain jobs with a job
identifier of 0 SHALL map the job identifier value 0 to a identifier of 0 SHALL map the job identifier value 0 to a
jmJobIndex value that is one higher than the highest job jmJobIndex value that is one higher than the highest job
identifier value that any job can have on that system." identifier value that any job can have on that system."
REFERENCE REFERENCE
"See Section 3.2 entitled 'The Job Tables'. See also "See Section 3.2 entitled 'The Job Tables'.
jmGeneralNewestActiveJobIndex for the largest value of See also jmGeneralNewestActiveJobIndex for the largest value of
jmJobIndex." jmJobIndex.
See JmJobSubmissionTypeTC for a limit on the size of this index
if the agent represents it as an 8-digit decimal number."
::= { jmJobEntry 1 } ::= { jmJobEntry 1 }
jmJobState OBJECT-TYPE jmJobState OBJECT-TYPE
SYNTAX JmJobStateTC SYNTAX JmJobStateTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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.84 July 21, 1997
and jmJobTable is specified by the value of the and jmJobTable is specified by the value of the
jmGeneralJobPersistence object." jmGeneralJobPersistence object."
::= { jmJobEntry 2 } ::= { jmJobEntry 2 }
jmJobStateReasons1 OBJECT-TYPE jmJobStateReasons1 OBJECT-TYPE
Job Monitoring MIB, V0.83 July 14, 1997
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. Furthermore, when implemented as with any MIB data, the
agent SHALL return these values when the reason applies and agent SHALL return these values when the reason applies and
SHALL NOT return them when the reason no longer applies whether SHALL NOT return them when the reason no longer applies whether
the value of the job's jmJobState object changed or not. When the value of the job's jmJobState object changed or not. When
the job does not have any reasons for being in its current the agent cannot provide a reason for the current state of the
state, the agent SHALL set the value of the jmJobStateReasons1 job, the agent SHALL set the value of the jmJobStateReasons1
object and jobStateReasonsN attributes to 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
skipping to change at page 78, line 49 skipping to change at page 82, line 4
processing." 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
"The total size in K (1024) octets of the document(s) being "The total size in K (1024) octets of the document(s) being
requested to be processed in the job. The agent SHALL round the requested to be processed in the job. The agent SHALL round the
Job Monitoring MIB, V0.84 July 21, 1997
actual number of octets up to the next highest K. Thus 0 octets actual number of octets up to the next highest K. Thus 0 octets
SHALL be represented as '0', 1-1024 octets SHALL be represented SHALL be represented as '0', 1-1024 octets SHALL be represented
as '1', 1025-2048 SHALL be represented as '2', etc. as '1', 1025-2048 SHALL be represented as '2', etc.
Job Monitoring MIB, V0.83 July 14, 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 79, line 51 skipping to change at page 83, line 4
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 }
jmJobImpressionsRequested OBJECT-TYPE jmJobImpressionsRequested OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
Job Monitoring MIB, V0.84 July 21, 1997
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of impressions requested by this job to produce." "The number of impressions requested by this job to produce."
Job Monitoring MIB, V0.83 July 14, 1997
::= { jmJobEntry 7 } ::= { jmJobEntry 7 }
jmJobImpressionsCompleted OBJECT-TYPE jmJobImpressionsCompleted OBJECT-TYPE
SYNTAX Integer32(-2..2147483647) SYNTAX Integer32(-2..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of impressions completed for this job so "The current number of impressions completed for this job so
far. For printing devices, the impressions completed includes far. For printing devices, the impressions completed includes
interpreting, marking, and stacking the output. For other types interpreting, marking, and stacking the output. For other types
skipping to change at page 80, line 38 skipping to change at page 83, line 43
unique to the network that is visible to the client and target unique to the network that is visible to the client and target
device. device.
This value SHOULD be the authenticated name of the user This value SHOULD be the authenticated name of the user
submitting the job." submitting the job."
REFERENCE REFERENCE
"See the OBJECT compliance macro for the minimum maximum length "See the OBJECT compliance macro for the minimum maximum length
required for conformance." required for conformance."
::= { jmJobEntry 9 } ::= { jmJobEntry 9 }
- -- The Attribute Group (MANDATORY)
- -- The jmAttributeGroup consists entirely of the jmAttributeTable.
- --
- -- Implementation of the two objects in this group is MANDATORY.
- -- See Section 3.1 entitled 'Conformance Considerations'.
- -- An agent SHALL implement any attribute if (1) the server or device
- -- supports the functionality represented by the attribute and (2) the
- -- information is available to the agent.
Job Monitoring MIB, V0.84 July 21, 1997
jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 } jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 }
jmAttributeTable OBJECT-TYPE jmAttributeTable OBJECT-TYPE
Job Monitoring MIB, V0.83 July 14, 1997
SYNTAX SEQUENCE OF JmAttributeEntry SYNTAX SEQUENCE OF JmAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jmAttributeTable SHALL contain attributes of the job and "The jmAttributeTable SHALL contain attributes of the job and
document(s) for each job in a job set. Instead of allocating document(s) for each job in a job set. Instead of allocating
distinct objects for each attribute, each attribute is distinct objects for each attribute, each attribute is
represented as a separate row in the jmAttributeTable." represented as a separate row in the jmAttributeTable."
REFERENCE REFERENCE
"The MANDATORY-GROUP macro specifies that this group is "The MANDATORY-GROUP macro specifies that this group is
skipping to change at page 81, line 49 skipping to change at page 85, line 4
convention. convention.
The agent SHALL create rows in the jmAttributeTable as the The agent SHALL create rows in the jmAttributeTable as the
server or device is able to discover the attributes either from server or device is able to discover the attributes either from
the job submission protocol itself or from the document PDL. As the job submission protocol itself or from the document PDL. As
the documents are interpreted, the interpreter MAY discover the documents are interpreted, the interpreter MAY discover
additional attributes and so the agent adds additional rows to additional attributes and so the agent adds additional rows to
this table. As the attributes that represent resources are this table. As the attributes that represent resources are
actually consumed, the usage counter contained in the actually consumed, the usage counter contained in the
jmAttributeValueAsInteger object is incremented according to the jmAttributeValueAsInteger object is incremented according to the
Job Monitoring MIB, V0.84 July 21, 1997
units indicated in the description of the JmAttributeTypeTC units indicated in the description of the JmAttributeTypeTC
enum. enum.
Job Monitoring MIB, V0.83 July 14, 1997
The agent SHALL maintain each row in the jmJobTable for at least The agent SHALL maintain each row in the jmJobTable for at least
the minimum time after a job completes as specified by the the minimum time after a job completes as specified by the
jmGeneralAttributePersistence object. jmGeneralAttributePersistence object.
Zero or more entries SHALL exist in this table for each job in a Zero or more entries SHALL exist in this table for each job in a
job set." job set."
REFERENCE REFERENCE
"See Section 3.3 entitled 'The Attribute Mechanism' for a "See Section 3.3 entitled 'The Attribute Mechanism' for a
description of the jmAttributeTable." description of the jmAttributeTable."
INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex, INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex,
skipping to change at page 82, line 52 skipping to change at page 86, line 4
Examples of required and consumed resource attributes include: Examples of required and consumed resource attributes include:
pagesRequested, pagesCompleted, mediumRequested, and pagesRequested, pagesCompleted, mediumRequested, and
mediumConsumed, respectively." mediumConsumed, respectively."
::= { jmAttributeEntry 1 } ::= { jmAttributeEntry 1 }
jmAttributeInstanceIndex OBJECT-TYPE jmAttributeInstanceIndex OBJECT-TYPE
SYNTAX Integer32(1..32767) SYNTAX Integer32(1..32767)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
Job Monitoring MIB, V0.84 July 21, 1997
DESCRIPTION DESCRIPTION
"A running 16-bit index of the attributes of the same type for "A running 16-bit index of the attributes of the same type for
each job. For those attributes with only a single instance per each job. For those attributes with only a single instance per
Job Monitoring MIB, V0.83 July 14, 1997
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 }
skipping to change at page 83, line 51 skipping to change at page 87, line 4
Since the agent MAY add attributes representing resources to Since the agent MAY add attributes representing resources to
this table while the job is waiting to be processed or being this table while the job is waiting to be processed or being
processed, which can be a long time before any of the resources processed, which can be a long time before any of the resources
are actually used, the agent SHALL set the value of the are actually used, the agent SHALL set the value of the
jmAttributeValueAsInteger object to 0 for resources that the job jmAttributeValueAsInteger object to 0 for resources that the job
has not yet consumed. has not yet consumed.
Attributes for which the concept of an integer value is Attributes for which the concept of an integer value is
meaningless, such as fileName, interpreter, and physicalDevice, meaningless, such as fileName, interpreter, and physicalDevice,
do not have the 'INTEGER:' tag in the JmAttributeTypeTC do not have the 'INTEGER:' tag in the JmAttributeTypeTC
Job Monitoring MIB, V0.84 July 21, 1997
definition and so an agent SHALL always return a value of '-1' definition and so an agent SHALL always return a value of '-1'
to indicate 'other' for jmAttributeValueAsInteger. to indicate 'other' for jmAttributeValueAsInteger.
Job Monitoring MIB, V0.83 July 14, 1997
For attributes which do have the 'INTEGER:' tag in the For attributes which do have the 'INTEGER:' tag in the
JmAttributeTypeTC definition, if the integer value is not (yet) JmAttributeTypeTC definition, if the integer value is not (yet)
known, the agent either SHALL not materialize the row in the known, the agent either SHALL not materialize the row in the
jmAttributeTable until the value is known or SHALL return a '-2' jmAttributeTable until the value is known or SHALL return a '-2'
to represent an 'unknown' counting integer value, a '0' to 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 }
jmAttributeValueAsOctets OBJECT-TYPE jmAttributeValueAsOctets OBJECT-TYPE
skipping to change at page 85, line 4 skipping to change at page 88, 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.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
- -- Notifications and Trapping
- -- Reserved for the future
jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2} jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2}
- -- Conformance Information
jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 } jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 }
- -- compliance statements
jmMIBCompliance MODULE-COMPLIANCE jmMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for agents that implement the "The compliance statement for agents that implement the
job monitoring MIB." job monitoring MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup } jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup }
OBJECT jmGeneralJobSetName OBJECT jmGeneralJobSetName
skipping to change at page 85, line 37 skipping to change at page 88, line 38
DESCRIPTION DESCRIPTION
"Only 8 octets maximum string length NEED be supported by the "Only 8 octets maximum string length NEED be supported by the
agent." agent."
OBJECT jmJobOwner OBJECT jmJobOwner
SYNTAX OCTET STRING (SIZE(0..16)) SYNTAX OCTET STRING (SIZE(0..16))
DESCRIPTION DESCRIPTION
"Only 16 octets maximum string length NEED be supported by the "Only 16 octets maximum string length NEED be supported by the
agent." agent."
- -- There are no CONDITIONALLY MANDATORY or OPTIONAL groups.
::= { jmMIBConformance 1 } ::= { jmMIBConformance 1 }
jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 } jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 }
jmGeneralGroup OBJECT-GROUP jmGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex, jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex,
jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence, jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence,
jmGeneralAttributePersistence, jmGeneralJobSetName} jmGeneralAttributePersistence, jmGeneralJobSetName}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The general group." "The general group."
Job Monitoring MIB, V0.83 July 14, 1997
::= { jmMIBGroups 1 } ::= { jmMIBGroups 1 }
Job Monitoring MIB, V0.84 July 21, 1997
jmJobIDGroup OBJECT-GROUP jmJobIDGroup OBJECT-GROUP
OBJECTS { OBJECTS {
jmJobIDJobSetIndex, jmJobIDJobIndex } jmJobIDJobSetIndex, jmJobIDJobIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The job ID group." "The job ID group."
::= { jmMIBGroups 2 } ::= { jmMIBGroups 2 }
jmJobGroup OBJECT-GROUP jmJobGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 87, line 4 skipping to change at page 90, 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.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
5. Appendix A - Implementing the Job Life Cycle 5. Appendix A - Implementing the Job Life Cycle
The job object has well-defined states and client operations that affect The job object has well-defined states and client operations that affect
the transition between the job states. Internal server and device the transition between the job states. Internal server and device
actions also affect the transitions of the job between the job states. actions also affect the transitions of the job between the job states.
These states and transitions are referred to as the job's life cycle. These states and transitions are referred to as the job's life cycle.
Not all implementations of job submission protocols have all of the Not all implementations of job submission protocols have all of the
states of the job model specified here. The job model specified here is states of the job model specified here. The job model specified here is
skipping to change at page 88, line 5 skipping to change at page 91, 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.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 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 88, line 45 skipping to change at page 91, line 45
command and the Printer Job Language. command and the Printer Job Language.
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.
7. References 7. References
[print-mib] The Printer MIB - RFC 1759, proposed IETF standard. Also an [hr-mib] P. Grillo, S. Waldbusser, "Host Resources MIB", RFC 1514,
Internet-Draft on the standards track as a draft standard: draft-ietf- September 1993
printmib-mib-info-01.txt
[iana] J. Reynolds, and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
ISI, October 1994.
Job Monitoring MIB, V0.84 July 21, 1997
[iana-media-types] IANA Registration of MIME media types (MIME content
types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/
[iso-dpa] ISO/IEC 10175 Document Printing Application (DPA). See [iso-dpa] ISO/IEC 10175 Document Printing Application (DPA). See
ftp://ftp.pwg.org/pub/pwg/dpa/ ftp://ftp.pwg.org/pub/pwg/dpa/
Job Monitoring MIB, V0.83 July 14, 1997
[ipp-model] Internet Printing Protocol (IPP), in progress on the IETF [ipp-model] Internet Printing Protocol (IPP), work in progress on the
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
[tipsi] IEEE 1284.1, Transport-independent Printer System Interface
(TIPSI).
[mib-II] MIB-II, RFC 1213. [mib-II] MIB-II, RFC 1213.
[hr-mib] P. Grillo, S. Waldbusser, "Host Resources MIB", RFC 1514, [print-mib] The Printer MIB - RFC 1759, proposed IETF standard. Also an
September 1993 Internet-Draft on the standards track as a draft standard: draft-ietf-
printmib-mib-info-02.txt
[SMIv2] SNMPv2-TC, RFC 1903,
[req-words] S. Bradner, "Keywords for use in RFCs to Indicate [req-words] S. Bradner, "Keywords for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[rfc 2130] C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R.
Atkinson, M. Crispin, and P. Svanberg, "The Report of the IAB Character
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
Simple Network Managment Protocol (SNMPv2)'' RFC 1903, January 1996.
[tipsi] IEEE 1284.1, Transport-independent Printer System Interface
(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.
[iana-media-types] IANA Registration of MIME media types (MIME content
types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/
8. Author's Addresses 8. Author's Addresses
Ron Bergman Ron Bergman
Dataproducts Corp. Dataproducts Corp.
1757 Tapo Canyon Road 1757 Tapo Canyon Road
Simi Valley, CA 93063-3394 Simi Valley, CA 93063-3394
Phone: 805-578-4421 Phone: 805-578-4421
Fax: 805-578-4001 Fax: 805-578-4001
Email: rbergman@dpc.com Email: rbergman@dpc.com
Tom Hastings Tom Hastings
Xerox Corporation, ESAE-231 Xerox Corporation, ESAE-231
701 S. Aviation Blvd. 701 S. Aviation Blvd.
El Segundo, CA 90245 El Segundo, CA 90245
Job Monitoring MIB, V0.84 July 21, 1997
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
EMail: hastings@cp10.es.xerox.com EMail: hastings@cp10.es.xerox.com
Scott A. Isaacson Scott A. Isaacson
Novell, Inc. Novell, Inc.
122 E 1700 S 122 E 1700 S
Provo, UT 84606 Provo, UT 84606
Job Monitoring MIB, V0.83 July 14, 1997
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
6300 Diagonal Hwy 6300 Diagonal Hwy
Boulder, CO 80301 Boulder, CO 80301
skipping to change at page 90, line 40 skipping to change at page 94, line 4
Keith Carter, IBM Corporation Keith Carter, IBM Corporation
Jeff Copeland - QMS Jeff Copeland - QMS
Andy Davidson - Tektronix Andy Davidson - Tektronix
Roger deBry - IBM Roger deBry - IBM
Mabry Dozier - QMS Mabry Dozier - QMS
Lee Ferrel - Canon Lee Ferrel - Canon
Steve Gebert - IBM Steve Gebert - IBM
Robert Herriot - Sun Microsystems Inc. Robert Herriot - Sun Microsystems Inc.
Shige Kanemitsu - Kyocera Shige Kanemitsu - Kyocera
David Kellerman - Northlake Software David Kellerman - Northlake Software
Job Monitoring MIB, V0.84 July 21, 1997
Rick Landau - Digital Rick Landau - Digital
Harry Lewis - IBM Harry Lewis - IBM
Pete Loya - HP Pete Loya - HP
Ray Lutz - Cognisys Ray Lutz - Cognisys
Jay Martin - Underscore Jay Martin - Underscore
Mike MacKay, Novell, Inc. Mike MacKay, Novell, Inc.
Stan McConnell - Xerox Stan McConnell - Xerox
Carl-Uno Manros, Xerox, Corp. Carl-Uno Manros, Xerox, Corp.
Pat Nogay - IBM Pat Nogay - IBM
Job Monitoring MIB, V0.83 July 14, 1997
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.83 July 14, 1997 Job Monitoring MIB, V0.84 July 21, 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, 51 colorantConsumed, 58
colorantRequested, 50 colorantRequested, 58
--D--- --D---
deviceNameRequested, 42 deviceNameRequested, 49
documentCopiesCompleted, 47 documentCopiesCompleted, 54
documentCopiesRequested, 47 documentCopiesRequested, 54
documentFormat, 44 documentFormat, 51
documentFormatIndex, 44 documentFormatIndex, 50
documentName, 43 documentName, 50
--F--- ------
fileName, 43 fileName, 50
finishing, 46 finishing, 52
fullColorImpressionsCompleted, 49 fullColorImpressionsCompleted, 55
--H--- --H---
highlightColorImpressionsCompleted, 49 highlightColorImpressionsCompleted, 56
--I--- ------
impressionsCompletedCurrentCopy, 48 impressionsCompletedCurrentCopy, 55
impressionsInterpreted, 48 impressionsInterpreted, 55
impressionsSentToDevice, 48 impressionsSentToDevice, 55
impressionsSpooled, 48 impressionsSpooled, 55
--J--- --J---
jmAttributeInstanceIndex, 77 jmAttributeInstanceIndex, 85
jmAttributeTypeIndex, 76 jmAttributeTypeIndex, 85
JmAttributeTypeTC, 39 JmAttributeTypeTC, 45
jmAttributeValueAsInteger, 77 jmAttributeValueAsInteger, 86
jmAttributeValueAsOctets, 78 jmAttributeValueAsOctets, 87
JmBooleanTC, 32 JmBooleanTC, 38
Job Monitoring MIB, V0.83 July 14, 1997
JmFinishingTC, 29 Job Monitoring MIB, V0.84 July 21, 1997
jmGeneralAttributePersistence, 67
jmGeneralJobPersistence, 67
jmGeneralJobSetIndex, 65
jmGeneralJobSetName, 68
jmGeneralNewestActiveJobIndex, 66
jmGeneralNumberOfActiveJobs, 66
jmGeneralOldestActiveJobIndex, 66
jmJobIDJobIndex, 70
jmJobIDJobSetIndex, 70
jmJobImpressionsCompleted, 74
jmJobImpressionsRequested, 74
jmJobIndex, 71
jmJobKOctetsProcessed, 73
jmJobKOctetsRequested, 73
jmJobOwner, 74
JmJobServiceTypesTC, 54
JmJobSourcePlatformTypeTC, 28
jmJobState, 72
jmJobStateReasons1, 72
JmJobStateReasons1TC, 55
JmJobStateReasons2TC, 59
JmJobStateReasons3TC, 63
JmJobStateReasons4TC, 63
JmJobStateTC, 36
jmJobSubmissionID, 69
JmJobSubmissionTypeTC, 34
JmMediumTypeTC, 33
jmNumberOfInterveningJobs, 73
JmPrinterResolutionTC, 31
JmPrintQualityTC, 30
JmTimeStampTC, 28
JmTonerEconomyTC, 32
jobAccountName, 40
jobComment, 43
jobCompletedTime, 52
jobCopiesCompleted, 47
jobCopiesRequested, 47
jobHold, 45
jobHoldUntil, 45
jobKOctetsTransferred, 47
jobName, 41
jobOriginatingHost, 42
jobPriority, 44
jobProcessAfterDateAndTime, 45
jobProcessingCPUTime, 52
jobServiceTypes, 41
jobSourceChannelIndex, 42
Job Monitoring MIB, V0.83 July 14, 1997
jobSourcePlatformType, 42 JmFinishingTC, 35
jobStartedBeingHeldTime, 52 jmGeneralAttributePersistence, 75
jobStartedProcessingTime, 52 jmGeneralJobPersistence, 75
jobStateReasons2, 40 jmGeneralJobSetIndex, 73
jobStateReasons3, 40 jmGeneralJobSetName, 76
jobStateReasons4, 40 jmGeneralNewestActiveJobIndex, 75
jobSubmissionTime, 51 jmGeneralNumberOfActiveJobs, 74
jobSubmissionToServerTime, 51 jmGeneralOldestActiveJobIndex, 74
jmJobIDJobIndex, 78
jmJobIDJobSetIndex, 78
jmJobImpressionsCompleted, 83
jmJobImpressionsRequested, 82
jmJobIndex, 80
jmJobKOctetsProcessed, 82
jmJobKOctetsRequested, 81
jmJobOwner, 83
JmJobServiceTypesTC, 61
JmJobSourcePlatformTypeTC, 34
jmJobState, 80
jmJobStateReasons1, 81
JmJobStateReasons1TC, 63
JmJobStateReasons2TC, 66
JmJobStateReasons3TC, 70
JmJobStateReasons4TC, 71
JmJobStateTC, 42
jmJobSubmissionID, 77
JmJobSubmissionTypeTC, 40
JmMediumTypeTC, 38
jmNumberOfInterveningJobs, 81
JmPrinterResolutionTC, 37
JmPrintQualityTC, 37
JmTimeStampTC, 34
JmTonerEconomyTC, 38
jobAccountName, 47
jobComment, 50
jobCompletedTime, 59
jobCopiesCompleted, 54
jobCopiesRequested, 54
jobHold, 52
jobHoldUntil, 52
jobKOctetsTransferred, 54
jobName, 47
jobOriginatingHost, 49
jobPriority, 51
jobProcessAfterDateAndTime, 51
jobProcessingCPUTime, 59
jobServiceTypes, 48
jobSourceChannelIndex, 48
--M--- Job Monitoring MIB, V0.84 July 21, 1997
mediumConsumed, 50 jobSourcePlatformType, 48
mediumRequested, 50 jobStartedBeingHeldTime, 59
jobStartedProcessingTime, 59
jobStateReasons2, 46
jobStateReasons3, 46
jobStateReasons4, 46
jobSubmissionTime, 59
jobSubmissionToServerTime, 58
--N--- ------
numberOfDocuments, 43 mediumConsumed, 57
mediumRequested, 57
--O--- ------
other, 39 numberOfDocuments, 50
outputBin, 45
------
other, 46
outputBin, 52
--P--- --P---
pagesCompleted, 49 pagesCompleted, 56
pagesCompletedCurrentCopy, 49 pagesCompletedCurrentCopy, 56
pagesRequested, 49 pagesRequested, 56
physicalDevice, 43 physicalDevice, 49
printerResolutionRequested, 46 printerResolutionRequested, 53
printerResolutionUsed, 46 printerResolutionUsed, 53
printQualityRequested, 46 printQualityRequested, 53
printQualityUsed, 46 printQualityUsed, 53
processingMessage, 40 processingMessage, 46
--Q--- ------
queueNameRequested, 43 queueNameRequested, 49
--S--- --S---
serverAssignedJobName, 40 serverAssignedJobName, 47
sheetsCompleted, 50 sheetsCompleted, 57
sheetsCompletedCurrentCopy, 50 sheetsCompletedCurrentCopy, 57
sheetsRequested, 50 sheetsRequested, 57
sides, 46 sides, 52
submittingApplicationName, 42 submittingApplicationName, 49
submittingServerName, 42 submittingServerName, 49
Job Monitoring MIB, V0.83 July 14, 1997
Job Monitoring MIB, V0.84 July 21, 1997
------ ------
tonerDensityRequested, 46 tonerDensityRequested, 53
tonerDensityUsed, 47 tonerDensityUsed, 53
tonerEcomonyRequested, 46 tonerEcomonyRequested, 53
tonerEcomonyUsed, 46 tonerEcomonyUsed, 53
 End of changes. 325 change blocks. 
695 lines changed or deleted 922 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/