idnits 2.17.1 draft-ietf-printmib-job-monitor-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 97 longer pages, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 98 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 435: '...extual conventions that an agent SHALL...' RFC 2119 keyword, line 539: '... the application SHALL query each job ...' RFC 2119 keyword, line 588: '...Each job set is disjoint; no job SHALL...' RFC 2119 keyword, line 599: '... and other devices. A server MAY be a...' RFC 2119 keyword, line 629: '...monitor MAY be either a separate appli...' (234 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 558 has weird spacing: '...ure for monit...' == Line 1436 has weird spacing: '...and the objec...' == Line 1437 has weird spacing: '...tion of jmJob...' == Line 3833 has weird spacing: '...dent of wheth...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: 2.SHALL accept the full syntactic range for all attributes, including enum and bit values specified in this specification and additional ones that may be registered with IANA and SHALL either present them to the user or ignore them. In particular, a conforming job monitoring application SHALL not malfunction when receiving any standard or registered enum or bit values. See Section 3.6 entitled "IANA Considerations". == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: 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, processing, or processingStopped, but not pendingHeld), the agent SHALL copy the value of the job's jmJobIndex to the jmGeneralNewestActiveJobIndex object. If the new job is to be 'inactive' (pendingHeld state), the agent SHALL not change the value of jmGeneralNewestActiveJobIndex object. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: A number of attributes record consumption. Such attribute names end with the word 'Completed' or 'Consumed'. If the job has not yet consumed what that resource is metering, the agent either: (1) SHALL return the value 0 or (2) SHALL not add this attribute to the jmAttributeTable until the consumption begins. In the interests of brevity, the semantics for 0 is specified once here and is not repeated for each consumptive attribute specification. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: If the client does not supply a job submission ID in the job submission protocol, then the server SHALL assign a job submission ID using any of the standard formats that are reserved to the agent. Clients SHALL not use formats that are reserved to agents. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: NOTE - This attribute type is intended to be used with an agent that implements the Printer MIB and SHALL not be used if the agent does not implement the Printer MIB. Such an agent SHALL use the documentFormat attribute instead. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: jobStartedBeingHeldTime(192), JmTimeStampTC AND/OR DateAndTime INTEGER: The time AND/OR OCTETS: the date and time that the job last entered the pendingHeld state. If the job has never entered the pendingHeld state, then the value SHALL be '0' or the attribute SHALL not be present in the table. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: jobProcessingCPUTime(195) Integer32(-2..2147483647) UNITS 'seconds' INTEGER: The amount of CPU time in seconds that the job has been in the processing state. If the job enters the processingStopped state, that elapsed time SHALL not be included. In other words, the jobProcessingCPUTime value SHOULD be relatively repeatable when the same job is processed again on the same device." == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: badJob 0x40000000 This job was aborted by the system because this job has a major problem, such as an ill-formed PDL; the spooler SHOULD not even try another device. " REFERENCE "These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.6.1.2. See the description under JmJobStateReasons1TC and the jobStateReasons2 attribute." == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: In computing this value, the server/device SHALL not include the multiplicative factors contributed by (1) the number of document copies, and (2) the number of job copies, independent of whether the device can process multiple copies of the job or document without making multiple passes over the job or document data and independent of whether the output is collated or not. Thus the server/device computation is independent of the implementation." ::= { jmJobEntry 5 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: For attributes which do have the 'INTEGER:' tag in the JmAttributeTypeTC definition, if the integer value is not (yet) known, the agent either SHALL not materialize the row in the jmAttributeTable until the value is known or SHALL return a '-2' to represent an 'unknown' counting integer value, a '0' to represent an 'unknown' index value, and a '2' to represent an 'unknown(2)' enum value." ::= { jmAttributeEntry 3 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHALL not' in this paragraph: For attributes which do have the 'OCTETS:' tag in the JmAttributeTypeTC definition, if the OCTET STRING value is not (yet) known, the agent either SHALL not materialize the row in the jmAttributeTable until the value is known or SHALL return a zero-length string." ::= { jmAttributeEntry 4 } -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 1997) is 9781 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1903 (ref. 'SMIv2-TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1738 (ref. 'URI-spec') (Obsoleted by RFC 4248, RFC 4266) Summary: 11 errors (**), 0 flaws (~~), 19 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Ron Bergman 2 Dataproducts Corp. 3 Tom Hastings 4 Xerox Corporation 5 Scott Isaacson 6 Novell, Inc. 7 Harry Lewis 8 IBM Corp. 9 July 1997 11 Job Monitoring MIB - V0.84 13 15 Expires Jan 21, 1997 17 Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, 21 and its working groups. Note that other groups may also distribute 22 working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet-Drafts 27 as reference material or to cite them other than as "work in 28 progress." 30 To learn the current status of any Internet-Draft, please check the 31 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 32 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 33 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 34 ftp.isi.edu (US West Coast). 36 Abstract 38 This Internet-Draft specifies a small set of read-only SNMP MIB 39 objects for (1) monitoring the status and progress of print jobs 40 (2) obtaining resource requirements before a job is processed, (3) 41 monitoring resource consumption while a job is being processed and 42 (4) collecting resource accounting data after the completion of a 43 job. This MIB is intended to be implemented (1) in a printer or 44 (2) in a server that supports one or more printers. Use of the 46 Job Monitoring MIB, V0.84 July 21, 1997 48 object set is not limited to printing. However, support for 49 services other than printing is outside the scope of this Job 50 Monitoring MIB. Future extensions to this MIB may include, but are 51 not limited to, fax machines and scanners. 53 Job Monitoring MIB, V0.84 July 21, 1997 55 TABLE OF CONTENTS 57 1. INTRODUCTION 11 59 1.1 Types of Information in the MIB 11 61 1.2 Types of Job Monitoring Applications 13 63 2. TERMINOLOGY AND JOB MODEL 14 65 2.1 System Configurations for the Job Monitoring MIB 16 67 2.1.1 Configuration 1 - client-printer 17 69 2.1.2 Configuration 2 - client-server-printer - agent in the server17 71 2.1.3 Configuration 3 - client-server-printer - client monitors 72 printer agent and server 19 74 3. MANAGED OBJECT USAGE 21 76 3.1 Conformance Considerations 21 78 3.1.1 Conformance Terminology 21 80 3.1.2 Agent Conformance Requirements 21 82 3.1.2.1 MIB II System Group objects 22 84 3.1.2.2 MIB II Interface Group objects 22 86 3.1.2.3 Printer MIB objects 22 88 3.1.3 Job Monitoring Application Conformance Requirements 22 90 3.2 The Job Tables and the Oldest Active and Newest Active Indexes 23 92 3.3 The Attribute Mechanism 24 94 3.3.1 Conformance of Attribute Implementation 25 96 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and 97 Attributes 25 99 Job Monitoring MIB, V0.84 July 21, 1997 101 3.3.3 Data Sub-types and Attribute Naming Conventions 26 103 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 27 105 3.3.5 Requested Attributes 27 107 3.3.6 Consumption Attributes 28 109 3.3.7 Index Value Attributes 28 111 3.4 Job Identification 28 113 3.5 Internationalization Considerations 29 115 3.6 IANA Considerations 29 117 3.6.1 IANA Registration of enums 29 119 3.6.1.1 Type 1 enumerations 30 121 3.6.1.2 Type 2 enumerations 30 123 3.6.1.3 Type 3 enumeration 31 125 3.6.2 IANA Registration of type 2 bit values 31 127 3.6.3 IANA Registration of Job Submission Id Formats 31 129 3.6.4 IANA Registration of MIME types/sub-types for document-formats31 131 3.7 Security Considerations 32 133 3.7.1 Read-Write objects 32 135 3.7.2 Read-Only Objects In Other User's Jobs 32 137 3.8 Notifications 32 139 4. MIB SPECIFICATION 32 141 Textual conventions for this MIB module 34 143 JmTimeStampTC - simple time in seconds 34 145 JmJobSourcePlatformTypeTC - operating system platform definitions 34 147 JmFinishingTC - device finishing definitions 35 149 Job Monitoring MIB, V0.84 July 21, 1997 151 JmPrintQualityTC - print quality 37 153 JmPrinterResolutionTC - printer resolution 37 155 JmTonerEconomyTC - toner economy setting 38 157 JmBooleanTC - Boolean value 38 159 JmMediumTypeTC - medium type definitions 39 161 JmJobSubmissionIDTypeTC - job submission ID type definitions 40 163 JmJobStateTC - job state definitions 42 165 JmAttributeTypeTC - attribute type definitions 45 167 other (Int32(-2..) and/or Octets63) 46 169 Job State attributes 46 171 jobStateReasons2 (JmJobStateReasons2TC) 46 173 jobStateReasons3 (JmJobStateReasons3TC) 46 175 jobStateReasons4 (JmJobStateReasons4TC) 47 177 processingMessage (Octets63) 47 179 Job Identification attributes 47 181 jobAccountName (Octets63) 47 183 serverAssignedJobName (Octets63) 47 185 jobName (Octets63) 48 187 jobServiceTypes (JmJobServiceTypesTC) 48 189 jobSourceChannelIndex (Int32(0..)) 49 191 jobSourcePlatformType (JmJobSourcePlatformTypeTC) 49 193 submittingServerName (Octets63) 49 195 submittingApplicationName (Octets63) 49 197 jobOriginatingHost (Octets63) 50 199 Job Monitoring MIB, V0.84 July 21, 1997 201 deviceNameRequested (Octets63) 50 203 queueNameRequested (Octets63) 50 205 physicalDevice (hrDeviceIndex and/or Octets63) 50 207 numberOfDocuments (Int32(-2..)) 50 209 fileName (Octets63) 51 211 documentName (Octets63) 51 213 jobComment (Octets63) 51 215 documentFormatIndex (Int32(0..)) 51 217 documentFormat (PrtInterpreterLangFamilyTC and/or Octets63) 52 219 Job Parameter attributes 52 221 jobPriority (Int32(1..100)) 52 223 jobProcessAfterDateAndTime (DateAndTime) 52 225 jobHold (JmBooleanTC) 53 227 jobHoldUntil (Octets63) 53 229 outputBin (Int32(0..) and/or Octets63) 53 231 sides (Int32(-2..2)) 53 233 finishing (JmFinishingTC) 53 235 Image Quality attributes (requested and used) 54 237 printQualityRequested (JmPrintQualityTC) 54 239 printQualityUsed (JmPrintQualityTC) 54 241 printerResolutionRequested (JmPrinterResolutionTC) 54 243 printerResolutionUsed (JmPrinterResolutionTC) 54 245 tonerEcomonyRequested (JmTonerEconomyTC) 54 247 tonerEcomonyUsed (JmTonerEconomyTC) 54 249 Job Monitoring MIB, V0.84 July 21, 1997 251 tonerDensityRequested (Int32(-2..100)) 55 253 tonerDensityUsed (Int32(-2..100)) 55 255 Job Progress attributes (requested and consumed) 55 257 jobCopiesRequested (Int32(-2..)) 55 259 jobCopiesCompleted (Int32(-2..)) 55 261 documentCopiesRequested (Int32(-2..)) 55 263 documentCopiesCompleted (Int32(-2..)) 56 265 jobKOctetsTransferred (Int32(-2..)) 56 267 Impression attributes (requested and consumed) 56 269 impressionsSpooled (Int32(-2..)) 57 271 impressionsSentToDevice (Int32(-2..)) 57 273 impressionsInterpreted (Int32(-2..)) 57 275 impressionsCompletedCurrentCopy (Int32(-2..)) 57 277 fullColorImpressionsCompleted (Int32(-2..)) 57 279 highlightColorImpressionsCompleted (Int32(-2..)) 57 281 Page attributes (requested and consumed) 58 283 pagesRequested (Int32(-2..)) 58 285 pagesCompleted (Int32(-2..)) 58 287 pagesCompletedCurrentCopy (Int32(-2..)) 58 289 Sheet attributes (requested and consumed) 58 291 sheetsRequested (Int32(-2..)) 58 293 sheetsCompleted (Int32(-2..)) 59 295 sheetsCompletedCurrentCopy (Int32(-2..)) 59 297 Resource attributes (requested and consumed) 59 299 Job Monitoring MIB, V0.84 July 21, 1997 301 mediumRequested (JmMediumTypeTC and/or Octets63) 59 303 mediumConsumed (Int32(-2..) and/or Octets63) 59 305 colorantRequested (Int32(-2..) and/or Octets63) 60 307 colorantConsumed (Int32(-2..) and/or Octets63) 60 309 Time attributes (set by server or device) 60 311 jobSubmissionToServerTime (JmTimeStampTC and/or DateAndTime) 61 313 jobSubmissionTime (JmTimeStampTC and/or DateAndTime) 61 315 jobStartedBeingHeldTime (JmTimeStampTC) 61 317 jobStartedProcessingTime (JmTimeStampTC and/or DateAndTime) 61 319 jobCompletedTime (JmTimeStampTC and/or DateAndTime) 61 321 jobProcessingCPUTime (Int32(-2..)) 62 323 JmJobServiceTypesTC - bit encoded job service type definitions 64 325 JmJobStateReasons1TC - additional information about job states 65 327 JmJobStateReasons2TC - More additional information about job states69 329 JmJobStateReasons3TC - More additional information about job states73 331 JmJobStateReasons4TC - More additional information about job states74 333 The General Group (MANDATORY) 75 335 jmGeneralJobSetIndex (Int32(1..32767)) 75 337 jmGeneralNumberOfActiveJobs (Int32(0..)) 76 339 jmGeneralOldestActiveJobIndex (Int32(0..)) 76 341 jmGeneralNewestActiveJobIndex (Int32(0..)) 77 343 jmGeneralJobPersistence (Int32(15..)) 77 345 jmGeneralAttributePersistence (Int32(15..)) 78 347 jmGeneralJobSetName (Octets63) 78 349 Job Monitoring MIB, V0.84 July 21, 1997 351 The Job ID Group (MANDATORY) 78 353 jmJobSubmissionID (OCTET STRING(SIZE(48))) 79 355 jmJobIDJobSetIndex (Int32(1..32767)) 80 357 jmJobIDJobIndex (Int32(1..)) 81 359 The Job Group (MANDATORY) 81 361 jmJobIndex (Int32(1..)) 82 363 jmJobState (JmJobStateTC) 82 365 jmJobStateReasons1 (JmJobStateReasons1TC) 83 367 jmNumberOfInterveningJobs (Int32(-2..)) 83 369 jmJobKOctetsRequested (Int32(-2..)) 84 371 jmJobKOctetsProcessed (Int32(-2..)) 84 373 jmJobImpressionsRequested (Int32(-2..)) 85 375 jmJobImpressionsCompleted (Int32(-2..)) 85 377 jmJobOwner (Octets63) 85 379 The Attribute Group (MANDATORY) 86 381 jmAttributeTypeIndex (JmAttributeTypeTC) 87 383 jmAttributeInstanceIndex (Int32(1..32767)) 88 385 jmAttributeValueAsInteger (Int32(-2..)) 88 387 jmAttributeValueAsOctets (Octets63) 89 389 5. APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 93 391 6. APPENDIX B - SUPPORT OF THE JOB SUBMISSION ID IN JOB SUBMISSION 392 PROTOCOLS 94 394 6.1 Hewlett-Packard's Printer Job Language (PJL) 94 396 6.2 ISO DPA 94 398 Job Monitoring MIB, V0.84 July 21, 1997 400 7. REFERENCES 94 402 8. AUTHOR'S ADDRESSES 95 404 9. INDEX 98 406 Job Monitoring MIB, V0.84 July 21, 1997 408 Job Monitoring MIB 410 1. Introduction 412 The Job Monitoring MIB is intended to be implemented by an agent within 413 a printer or the first server closest to the printer, where the printer 414 is either directly connected to the server only or the printer does not 415 contain the job monitoring MIB agent. It is recommended that 416 implementations place the SNMP agent as close as possible to the 417 processing of the print job. This MIB applies to printers with and 418 without spooling capabilities. This MIB is designed to be compatible 419 with most current commonly-used job submission protocols. In most 420 environments that support high function job submission/job control 421 protocols, like ISO DPA[iso-dpa], those protocols would be used to 422 monitor and manage print jobs rather than using the Job Monitoring MIB. 424 The Job Monitoring MIB consists of a General Group, a Job Submission ID 425 Group, a Job Group, and an Attribute Group. Each group is a table. All 426 accessible objects are read-only. The General Group contains general 427 information that applies to all jobs in a job set. The Job Submission 428 ID table maps the job submission ID that the client uses to identify a 429 job to the jmJobIndex that the Job Monitoring Agent uses to identify 430 jobs in the Job and Attribute tables. The Job table contains the 431 MANDATORY integer job state and status objects. The Attribute table 432 consists of multiple entries per job that specify (1) job and document 433 identification and parameters, (2) requested resources, and (3) 434 consumed resources during and after job processing/printing. Sixty five 435 job attributes are defined as textual conventions that an agent SHALL 436 return if the server or device implements the functionality so 437 represented and the agent has access to the information. 439 1.1 Types of Information in the MIB 441 The job MIB is intended to provide the following information for the 442 indicated Role Models in the Printer MIB[print-mib] (Appendix D - Roles 443 of Users). 445 User: 447 Provide the ability to identify the least busy printer. The user 448 will be able to determine the number and size of jobs waiting for 449 each printer. No attempt is made to actually predict the length 450 of time that jobs will take. 452 Provide the ability to identify the current status of the user's 453 job (user queries). 455 Job Monitoring MIB, V0.84 July 21, 1997 457 Provide a timely indication that the job has completed and where 458 it can be found. 460 Provide error and diagnostic information for jobs that did not 461 successfully complete. 463 Operator: 465 Provide a presentation of the state of all the jobs in the print 466 system. 468 Provide the ability to identify the user that submitted the print 469 job. 471 Provide the ability to identify the resources required by each 472 job. 474 Provide the ability to define which physical printers are 475 candidates for the print job. 477 Provide some idea of how long each job will take. However, exact 478 estimates of time to process a job is not being attempted. 479 Instead, objects are included that allow the operator to be able 480 to make gross estimates. 482 Capacity Planner: 484 Provide the ability to determine printer utilization as a function 485 of time. 487 Provide the ability to determine how long jobs wait before 488 starting to print. 490 Accountant: 492 Provide information to allow the creation of a record of resources 493 consumed and printer usage data for charging users or groups for 494 resources consumed. 496 Provide information to allow the prediction of consumable usage 497 and resource need. 499 The MIB supports printers that can contain more than one job at a time, 500 but still be usable for low end printers that only contain a single job 501 at a time. In particular, the MIB supports the needs of Windows and 502 other PC environments for managing low-end networked devices without 503 unnecessary overhead or complexity, while also providing for higher end 504 systems and devices. 506 Job Monitoring MIB, V0.84 July 21, 1997 508 1.2 Types of Job Monitoring Applications 510 The Job Monitoring MIB is designed for the following types of monitoring 511 applications: 513 1.Monitor a single job starting when the job is submitted and ending 514 a defined period after the job completes. The Job Submission ID 515 table provides the map to find the specific job to be monitored. 517 2.Monitor all 'active' jobs in a queue, which this specification 518 generalizes to a "job set". End users may use such a program when 519 selecting a least busy printer, so the MIB is designed for such a 520 program to start up quickly and find the information needed quickly 521 without having to read all (completed) jobs in order to find the 522 active jobs. System operators may also use such a program, in 523 which case it would be running for a long period of time and may 524 also be interested in the jobs that have completed. Finally such a 525 program may be used to provide an enhanced console and logging 526 capability. 528 3.Collect resource usage for accounting or system utilization 529 purposes that copy the completed job statistics to an accounting 530 system. It is recognized that depending on accounting programs to 531 copy MIB data during the job-retention period is somewhat 532 unreliable, since the accounting program may not be running (or may 533 have crashed). Such a program is also expected to keep a shadow 534 copy of the entire Job Attribute table including completed, 535 canceled, and aborted jobs which the program updates on each 536 polling cycle. Such a program polls at the rate of the persistence 537 of the Attribute table. The design is not optimized to help such 538 an application determine which jobs are completed, canceled, or 539 aborted. Instead, the application SHALL query each job that the 540 application's shadow copy shows was not complete, canceled, or 541 aborted at the previous poll cycle to see if it is now complete or 542 canceled, plus any new jobs that have been submitted. 544 The MIB provides a set of objects that represent a compatible subset of 545 job and document attributes of the ISO DPA standard[iso-dpa] and the 546 Internet Printing Protocol (IPP)[ipp-model], so that coherence is 547 maintained between these two protocols and the information presented to 548 end users and system operators by monitoring applications. However, the 549 job monitoring MIB is intended to be used with printers that implement 550 other job submitting and management protocols, such as IEEE 1284.1 551 (TIPSI)[tipsi], as well as with ones that do implement ISO DPA. Thus 552 the job monitoring MIB does not require implementation of either the ISO 553 DPA or IPP protocols. 555 Job Monitoring MIB, V0.84 July 21, 1997 557 The MIB is designed so that an additional MIB(s) can be specified in the 558 future for monitoring multi-function (scan, FAX, copy) jobs as an 559 augmentation to this MIB. 561 2. Terminology and Job Model 563 This section defines the terms that are used in this specification and 564 the general model for jobs. 566 NOTE - Existing systems use conflicting terms, so these terms are 567 drawn from the ISO 10175 Document Printing Application (DPA) 568 standard[iso-dpa]. For example, PostScript systems use the term 569 session for what is called a job in this specification and the term 570 job to mean what is called a document in this specification. PJL 571 systems use the term job to mean what is called a job in this 572 specification. PJL also supports multiple documents per job, but does 573 not support specifying per-document attributes independently for each 574 document. 576 Job: a unit of work whose results are expected together without 577 interjection of unrelated results. A job contains one or more 578 documents. 580 Job Set: a group of jobs that are queued and scheduled together 581 according to a specified scheduling algorithm for a specified device or 582 set of devices. For implementations that embed the SNMP agent in the 583 device, the MIB job set normally represents all the jobs known to the 584 device, so that the implementation only implements a single job set. If 585 the SNMP agent is implemented in a server that controls one or more 586 devices, each MIB job set represents a job queue for (1) a specific 587 device or (2) set of devices, if the server uses a single queue to load 588 balance between several devices. Each job set is disjoint; no job SHALL 589 be represented in more than one MIB job set. 591 Document: a sub-section within a job that contains print data and 592 document instructions that apply to just the document. 594 Client: the network entity that end users use to submit jobs to 595 spoolers, servers, or printers and other devices, depending on the 596 configuration, using any job submission protocol. 598 Server: a network entity that accepts jobs from clients and in turn 599 submits the jobs to printers and other devices. A server MAY be a 600 printer supervisor control program, or a print spooler. 602 Device: a hardware entity that (1) interfaces to humans in human 603 perceptible means, such as produces marks on paper, scans marks on paper 604 to produce an electronic representations, or writes CD-ROMs or (2) 606 Job Monitoring MIB, V0.84 July 21, 1997 608 interfaces electronically to another device, such as sends FAX data to 609 another FAX device. 611 Printer: a device that puts marks on media. 613 Supervisor: a server that contains a control program that controls a 614 printer or other device. A supervisor is a client to the printer or 615 other device. 617 Spooler: a server that accepts jobs, spools the data, and decides when 618 and on which printer to print the job. A spooler is a client to a 619 printer or a printer supervisor, depending on implementation. 621 Spooling: the act of a device or server of (1) accepting jobs and (2) 622 writing the job's attributes and document data on to secondary storage. 624 Queuing: the act of a device or server of ordering (queuing) the jobs 625 for the purposes of scheduling the jobs to be processed. 627 Monitor or Job Monitoring Application: the SNMP management application 628 that End Users, and System Operators use to monitor jobs using SNMP. A 629 monitor MAY be either a separate application or MAY be part of the 630 client that also submits jobs. 632 Accounting Application: the SNMP management application that copies job 633 information to some more permanent medium so that another application 634 can perform accounting on the data for Accountants, Asset Managers, and 635 Capacity Planners use. 637 Agent: the network entity that accepts SNMP requests from a monitor or 638 accounting application and provides access to the instrumentation for 639 managing jobs modeled by the management objects defined in the Job 640 Monitoring MIB module for a server or a device. 642 Proxy: an agent that acts as a concentrator for one or more other 643 agents by accepting SNMP operations on the behalf of one or more other 644 agents, forwarding them on to those other agents, gathering responses 645 from those other agents and returning them to the original requesting 646 monitor. 648 User: a person that uses a client or a monitor. 650 End User: a user that uses a client to submit a print job. 652 System Operator: a user that uses a monitor to monitor the system and 653 carries out tasks to keep the system running. 655 System Administrator: a user that specifies policy for the system. 657 Job Monitoring MIB, V0.84 July 21, 1997 659 Job Instruction: an instruction specifying how, when, or where the job 660 is to be processed. Job instructions MAY be passed in the job 661 submission protocol or MAY be embedded in the document data or a 662 combination depending on the job submission protocol and implementation. 664 Document Instruction: an instruction specifying how to process the 665 document. Document instructions MAY be passed in the job submission 666 protocol separate from the actual document data, or MAY be embedded in 667 the document data or a combination, depending on the job submission 668 protocol and implementation. 670 SNMP Information Object: a name, value-pair that specifies an action, a 671 status, or a condition in an SNMP MIB. Objects are identified in SNMP 672 by an OBJECT IDENTIFIER. 674 Attribute: a name, value-pair that specifies a job or document 675 instruction, a status, or a condition of a job or a document that has 676 been submitted to a server or device. A particular attribute NEED NOT 677 be present in each job instance. In other words, attributes are present 678 in a job instance only when there is a need to express the value, either 679 because (1) the client supplied a value in the job submission protocol, 680 (2) the document data contained an embedded attribute, or (3) the server 681 or device supplied a default value. An agent SHALL represent an 682 attribute as an entry (row) in the Attribute table in this MIB in which 683 entries are present only when necessary. Attributes are identified in 684 this MIB by an enum. 686 Job Monitoring (using SNMP): the activity of a management application 687 of accessing the MIB and (1) identifying jobs in the job tables being 688 processed by the server, printer or other devices, and (2) displaying 689 information to the user about the processing of the job. 691 Job Accounting: the activity of a management application of accessing 692 the MIB and recording what happens to the job during and after the 693 processing of the job. 695 2.1 System Configurations for the Job Monitoring MIB 697 This section enumerates the three configurations in which the Job 698 Monitoring MIB is intended to be used. To simplify the pictures, the 699 devices are shown as printers. See Goals section. 701 The diagram in the Printer MIB[print-mib] entitled: "One Printer's View 702 of the Network" is assumed for this MIB as well. Please refer to that 703 diagram to aid in understanding the following system configurations. 705 Job Monitoring MIB, V0.84 July 21, 1997 707 2.1.1 Configuration 1 - client-printer 709 In the client-printer configuration, the client(s) submit jobs directly 710 to the printer, either by some direct connect, or by network connection. 712 The job submitting client and/or monitoring application monitor jobs by 713 communicating directly with an agent that is part of the printer. The 714 agent in the Printer SHALL keep the job in the Job Monitoring MIB as 715 long as the job is in the Printer, plus a defined time period after the 716 job enters the completed state in which accounting programs can copy out 717 the accounting data from the Job Monitoring MIB. 719 all end-user ######## SNMP query 720 +-------+ +--------+ ---- job submission 721 |monitor| | client | 722 +---#---+ +--#--+--+ 723 # # | 724 # ############ | 725 # # | 726 +==+===#=#=+==+ | 727 | | agent | | | 728 | +-------+ | | 729 | PRINTER <--------+ 730 | | Print Job Delivery Channel 731 | | 732 +=============+ 734 Figure 2-1 - Configuration 1 - client-printer - agent in the printer 736 The Job Monitoring MIB is designed to support the following 737 relationships (not shown in Figure 2-1): 739 1.Multiple clients MAY submit jobs to a printer. 741 2.Multiple clients MAY monitor a printer. 743 3.Multiple monitors MAY monitor a printer. 745 4.A client MAY submit jobs to multiple printers. 747 5.A monitor MAY monitor multiple printers. 749 2.1.2 Configuration 2 - client-server-printer - agent in the server 751 In the client-server-printer configuration 2, the client(s) submit jobs 752 to an intermediate server by some network connection, not directly to 754 Job Monitoring MIB, V0.84 July 21, 1997 756 the printer. While configuration 2 is included, the design center for 757 this MIB is configurations 1 and 3, 759 The job submitting client and/or monitoring application monitor job by 760 communicating directly with: 762 A Job Monitoring MIB agent that is part of the server (or a front 763 for the server) 765 There is no SNMP Job Monitoring MIB agent in the printer in 766 configuration 2, at least that the client or monitor are aware. In this 767 configuration, the agent SHALL return the current values of the objects 768 in the Job Monitoring MIB both for jobs the server keeps and jobs that 769 the server has submitted to the printer. The Job Monitoring MIB agent 770 SHALL obtain the required information from the printer by a method that 771 is beyond the scope of this document. The agent in the server SHALL 772 keep the job in the Job Monitoring MIB in the server as long as the job 773 is in the Printer, plus a defined time period after the job enters the 774 completed state in which accounting programs can copy out the accounting 775 data from the Job Monitoring MIB. 777 all end-user 778 +-------+ +----------+ 779 |monitor| | client | ######## SNMP query 780 +---+---# +---#----+-+ **** non-SNMP cntrl 781 # # | ---- job submission 782 # # | 783 # # | 784 #=====#=+==v==+ 785 | agent | | 786 +-------+ | 787 | server | 788 +----+-----+--+ 789 control * | 790 ********** | 791 * | 792 +========v====+ | 793 | | | 794 | | | 795 | PRINTER <---------+ 796 | | Print Job Delivery Channel 797 | | 798 +=============+ 800 Figure 2-2 - Configuration 2 - client-server-printer - agent in the 801 server 803 Job Monitoring MIB, V0.84 July 21, 1997 805 The Job Monitoring MIB is designed to support the following 806 relationships (not shown in Figure 2-2): 808 1.Multiple clients MAY submit jobs to a server. 810 2.Multiple clients MAY monitor a server. 812 3.Multiple monitors MAY monitor a server. 814 4.A client MAY submit jobs to multiple servers. 816 5.A monitor MAY monitor multiple servers. 818 6.Multiple servers MAY submit jobs to a printer. 820 7.Multiple servers MAY control a printer. 822 2.1.3 Configuration 3 - client-server-printer - client monitors printer 823 agent and server 825 In the client-server-printer configuration 3, the client(s) submit jobs 826 to an intermediate server by some network connection, not directly to 827 the printer. That server does not contain a Job Monitoring MIB and 828 agent. 830 The job submitting client and/or monitoring application monitor jobs by 831 communicating directly with: 833 1.The server using some undefined protocol to monitor jobs in the 834 server (that does not contain the Job Monitoring MIB) AND 836 2.A Job Monitoring MIB agent that is part of the printer to 837 monitor jobs after the server passes the jobs to the printer. 838 In such configurations, the server deletes its copy of the job 839 from the server after submitting the job to the printer usually 840 almost immediately (before the job does much processing, if 841 any). 843 In configuration 3, the agent (in the printer) SHALL keep the values of 844 the objects in the Job Monitoring MIB that the agent implements updated 845 for a job that the server has submitted to the printer. The agent SHALL 846 obtain information about the jobs submitted to the printer from the 847 server (either in the job submission protocol, in the document data, or 848 by direct query of the server), in order to populate some of the objects 849 the Job Monitoring MIB in the printer. The agent in the printer SHALL 850 keep the job in the Job Monitoring MIB as long as the job is in the 851 Printer, and longer in order to implement the completed state in which 853 Job Monitoring MIB, V0.84 July 21, 1997 855 monitoring programs can copy out the accounting data from the Job 856 Monitoring MIB. 858 all end-user 859 +-------+ +----------+ 860 |monitor| | client | ######## SNMP query 861 +---+---* +---*----+-+ **** non-SNMP query 862 # * * | ---- job submission 863 # * * | 864 # * * | 865 # *=====v====v==+ 866 # | | 867 # | server | 868 # | | 869 # +----#-----+--+ 870 # optional# | 871 # ########## | 872 # # | 873 +==+=v===v=+==+ | 874 | | agent | | | 875 | +-------+ | | 876 | PRINTER <---------+ 877 | | Print Job Delivery Channel 878 | | 879 +=============+ 881 Figure 2-3 - Configuration 3 - client-server-printer - client monitors 882 printer agent and server 884 The Job Monitoring MIB is designed to support the following 885 relationships (not shown in Figure 2-3): 887 1.Multiple clients MAY submit jobs to a server. 889 2.Multiple clients MAY monitor a server. 891 3.Multiple monitors MAY monitor a server. 893 4.A client MAY submit jobs to multiple servers. 895 5.A monitor MAY monitor multiple servers. 897 6.Multiple servers MAY submit jobs to a printer. 899 7.Multiple servers MAY control a printer. 901 Job Monitoring MIB, V0.84 July 21, 1997 903 3. Managed Object Usage 905 This section describes the usage of the objects in the MIB. 907 3.1 Conformance Considerations 909 In order to achieve interoperability between job monitoring applications 910 and job monitoring agents, this specification includes the conformance 911 requirements for both monitoring applications and agents. 913 3.1.1 Conformance Terminology 915 This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED 916 NOT" to specify conformance requirements according to RFC 2119 [req- 917 words] as follows: 919 . "SHALL": indicates an action that the subject of the sentence must 920 implement in order to claim conformance to this specification 922 . "MAY": indicates an action that the subject of the sentence does 923 not have to implement in order to claim conformance to this 924 specification, in other words that action is an implementation 925 option 927 . "NEED NOT": indicates an action that the subject of the sentence 928 does not have to implement in order to claim conformance to this 929 specification. The verb "NEED NOT" is used instead of "may not", 930 since "may not" sounds like a prohibition. 932 . "SHOULD": indicates an action that is recommended for the subject 933 of the sentence to implement, but is not required, in order to 934 claim conformance to this specification. 936 3.1.2 Agent Conformance Requirements 938 A conforming agent: 940 1.SHALL implement all MANDATORY groups in this specification. 942 2.SHALL implement any attributes if (1) the server or device supports 943 the functionality represented by the attribute and (2) the 944 information is available to the agent. 946 3.SHOULD implement both forms of an attribute if it implements an 947 attribute that permits a choice of INTEGER and OCTET STRING forms, 948 since implementing both forms may help management applications by 949 giving them a choice of representations, since the representation are 950 equivalent. See the JmAttributeTypeTC textual-convention. 952 Job Monitoring MIB, V0.84 July 21, 1997 954 NOTE - This MIB, like the Printer MIB, is written following the 955 subset of SMIv2 that can be supported by SMIv1 and SNMPv1 956 implementations. 958 3.1.2.1 MIB II System Group objects 960 The Job Monitoring MIB agent SHALL implement all objects in the System 961 Group of MIB-II[mib-II], whether the Printer MIB[print-mib] is 962 implemented or not. 964 3.1.2.2 MIB II Interface Group objects 966 The Job Monitoring MIB agent SHALL implement all objects in the 967 Interfaces Group of MIB-II[mib-II], whether the Printer MIB[print-mib] 968 is implemented or not. 970 3.1.2.3 Printer MIB objects 972 If the agent is providing access to a device that is a printer, the 973 agent SHALL implement all of the MANDATORY objects in the Printer 974 MIB[print-mib] and all the objects in other MIBs that conformance to the 975 Printer MIB requires, such as the Host Resources MIB[hr-mib]. If the 976 agent is providing access to a server that controls one or more 977 networked printers, the agent NEED NOT implement the Printer MIB and 978 NEED NOT implement the Host Resources MIB. 980 3.1.3 Job Monitoring Application Conformance Requirements 982 A conforming job monitoring application: 984 1.SHALL accept the full syntactic range for all objects in all 985 MANDATORY groups and all MANDATORY attributes that are required to be 986 implemented by an agent according to Section 3.1.2 and SHALL either 987 present them to the user or ignore them. 989 2.SHALL accept the full syntactic range for all attributes, including 990 enum and bit values specified in this specification and additional 991 ones that may be registered with IANA and SHALL either present them 992 to the user or ignore them. In particular, a conforming job 993 monitoring application SHALL not malfunction when receiving any 994 standard or registered enum or bit values. See Section 3.6 entitled 995 "IANA Considerations". 997 3.SHALL NOT fail when operating with agents that materialize attributes 998 after the job has been submitted, as opposed to when the job is 999 submitted. 1001 Job Monitoring MIB, V0.84 July 21, 1997 1003 4.SHALL, if it supports a time attribute, accept either form of the 1004 time attribute, since agents are free to implement either time form. 1006 3.2 The Job Tables and the Oldest Active and Newest Active Indexes 1008 The jmJobTable and jmAttributeTable contain objects and attributes, 1009 respectively, for each job in a job set. These first two indexes are: 1011 1.jmGeneralJobSetIndex - which job set 1013 2.jmJobIndex - which job in the job set 1015 In order for a monitoring application to quickly find that active jobs 1016 (jobs in the pending, processing, or processingStopped states), the MIB 1017 contains two indexes: 1019 1.jmGeneralOldestActiveJobIndex - the index of the active job that 1020 has been in the tables the longest. 1022 2.jmGeneralNewestActiveJobIndex - the index of the active job that 1023 has been most recently added to the tables. 1025 The agent SHALL assign the next incremental value of jmJobIndex to the 1026 job, when a new job is accepted by the server or device to which the 1027 agent is providing access. If the incremented value of jmJobIndex would 1028 exceed the implementation-defined maximum value for jmJobIndex, the 1029 agent SHALL 'wrap' back to 1. An agent uses the resulting value of 1030 jmJobIndex for storing information in the jmJobTable and the 1031 jmAttributeTable about the job. 1033 It is recommended that the largest value for jmJobIndex be much larger 1034 than the maximum number of jobs that the implementation can contain at a 1035 single time, so as to minimize the pre-mature re-use of jmJobIndex value 1036 for a newer job while clients retain the same 'stale' value for an older 1037 job. 1039 Each time a new job is accepted by the server or device that the agent 1040 is providing access to AND that job is to be 'active' (pending, 1041 processing, or processingStopped, but not pendingHeld), the agent SHALL 1042 copy the value of the job's jmJobIndex to the 1043 jmGeneralNewestActiveJobIndex object. If the new job is to be 1044 'inactive' (pendingHeld state), the agent SHALL not change the value of 1045 jmGeneralNewestActiveJobIndex object. 1047 When a job transitions from one of the 'active' job states (pending, 1048 processing, processingStopped) to one of the 'inactive' job states 1049 (pendingHeld, completed, canceled, or aborted), with a jmJobIndex value 1050 that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL 1052 Job Monitoring MIB, V0.84 July 21, 1997 1054 advance (or wrap) the value to the next oldest 'active' job, if any. 1055 See the JmJobStateTC textual-convention for a definition of the job 1056 states. 1058 Whenever a job transitions from one of the 'inactive' job states to one 1059 of the 'active' job states (from pendingHeld to pending or processing), 1060 the agent SHALL update the value of either the 1061 jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex 1062 objects, or both, if the job's jmJobIndex value is outside the range 1063 between jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex. 1065 When all jobs become 'inactive', i.e., enter the pendingHeld, completed, 1066 canceled, or aborted states, the agent SHALL set the value of both the 1067 jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex objects 1068 to 0. 1070 NOTE - Applications that wish to efficiently access all of the active 1071 jobs MAY use jmGeneralOldestActiveJobIndex value to start with the 1072 oldest active job and continue until they reach the index value equal to 1073 jmGeneralNewestActiveJobIndex, skipping over any pendingHeld, completed, 1074 canceled, or aborted jobs that might intervene. 1076 If an application detects that the jmGeneralNewestActiveJobIndex is 1077 smaller than jmGeneralOldestActiveJobIndex, the job index has wrapped. 1078 In this case, the application SHALL reset the index to 1 when the end of 1079 the table is reached and continue the GetNext operations to find the 1080 rest of the active jobs. 1082 NOTE - Application detect the end of the table when the OID returned by 1083 the GetNext operation is an OID in a different MIB. There is no object 1084 in this MIB that specifies the maximum value for the jmJobIndex 1085 supported by the implementation. 1087 When the server or device is power-cycled, the agent SHALL remember the 1088 next jmJobIndex value to be assigned, so that new jobs are not assigned 1089 the same jmJobIndex as recent jobs before the power cycle. 1091 3.3 The Attribute Mechanism 1093 Attributes are similar to information objects, except that attributes 1094 are identified by an enum, instead of an OID, so that attributes may be 1095 registered without requiring a new MIB. Also an implementation that 1096 does not have the functionality represented by the attribute can omit 1097 the attribute entirely, rather than having to return a distinguished 1098 value. The agent is free to materialize an attribute in the 1099 jmAttributeTable as soon as the agent is aware of the value of the 1100 attribute. 1102 Job Monitoring MIB, V0.84 July 21, 1997 1104 The agent materializes job attributes in a four-indexed 1105 jmAttributeTable: 1107 1.jmGeneralJobSetIndex - which job set 1109 2.jmJobIndex - which job in the job set 1111 3.jmAttributeTypeIndex - which attribute 1113 4.jmAttributeInstanceIndex - which attribute instance for those 1114 attributes that can have multiple values per job. 1116 Some attributes represent information about a job, such as a file-name, 1117 a document-name, a submission-time or a completion time. Other 1118 attributes represent resources required, e.g., a medium or a colorant, 1119 etc. to process the job before the job starts processing OR to indicate 1120 the amount of the resource consumed during and after processing, e.g., 1121 pages completed or impressions completed. If both a required and a 1122 consumed value of a resource is needed, this specification assigns two 1123 separate attribute enums in the textual convention. 1125 NOTE - The table of contents lists all the attributes in order. This 1126 order is the order of enum assignments which is the order that the SNMP 1127 GetNext operation returns attributes. Most attributes apply to all 1128 three configurations covered by this MIB specification (see section 2.1 1129 entitled "System Configurations for the Job Monitoring MIB"). Those 1130 attributes that apply to a particular configuration are indicated as 1131 'Configuration n:' and SHALL NOT be used with other configurations. 1133 3.3.1 Conformance of Attribute Implementation 1135 An agent SHALL implement any attribute if (1) the server or device 1136 supports the functionality represented by the attribute and (2) the 1137 information is available to the agent. The agent MAY create the 1138 attribute row in the jmAttributeTable when the information is available 1139 or MAY create the row earlier with the designated 'unknown' value 1140 appropriate for that attribute. See next section. 1142 If the server or device does not implement or does not provide access to 1143 the information about an attribute, the agent SHOULD NOT create the 1144 corresponding row in the jmAttributeTable. 1146 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes 1148 Some attributes have a 'useful' Integer32 value, some have a 'useful' 1149 OCTET STRING value, some MAY have either or both depending on 1150 implementation, and some MUST have both. See the JmAttributeTypeTC 1151 textual convention for the specification of each attribute. 1153 Job Monitoring MIB, V0.84 July 21, 1997 1155 SNMP requires that if an object cannot be implemented because its values 1156 cannot be accessed, then a compliant agent SHALL return an SNMP error in 1157 SNMPv1 or an exception value in SNMPv2. However, this MIB has been 1158 designed so that 'all' objects can and SHALL be implemented by an agent, 1159 so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be 1160 generated by the agent. This MIB has also been designed so that when an 1161 agent materializes an attribute, the agent SHALL materialize a row 1162 consisting of both the jmAttributeValueAsInteger and 1163 jmAttributeValueAsOctets objects. 1165 In general, values for objects and attributes have been chosen so that a 1166 management application will be able to determine whether a 'useful', 1167 'unknown', or 'other' value is available. When a useful value is not 1168 available for an object that agent SHALL return a zero-length string for 1169 octet strings, the value 'unknown(2)' for enums, a '0' value for an 1170 object that represents an index in another table, and a value '-2' for 1171 counting integers. 1173 Since each attribute is represented by a row consisting of both the 1174 jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY 1175 objects, SNMP requires that the agent SHALL always create an attribute 1176 row with both objects specified. However, for most attributes the agent 1177 SHALL return a "useful" value for one of the objects and SHALL return 1178 the 'other' value for the other object. For integer only attributes, 1179 the agent SHALL always return a zero-length string value for the 1180 jmAttributeValueAsOctets object. For octet string only attributes, the 1181 agent SHALL always return a '-1' value for the jmAttributeValueAsInteger 1182 object. 1184 3.3.3 Data Sub-types and Attribute Naming Conventions 1186 Many attributes are sub-typed to give a more specific data type than 1187 Integer32 or OCTET STRING. The data sub-type of each attribute is 1188 indicated on the first line(s) of the description. Some attributes have 1189 several different data sub-type representations. When an attribute has 1190 both an Integer32 data sub-type and an OCTET STRING data sub-type, the 1191 attribute can be represented in a single row in the jmAttributeTable. 1192 In this case, the data sub-type name is not included as the last part of 1193 the name of the attribute, e.g., documentFormat(38) which is both an 1194 enum and/or a name. When the data sub-types cannot be represented by a 1195 single row in the jmAttributeTable, each such representation is 1196 considered a separate attribute and is assigned a separate name and enum 1197 value. For these attributes, the name of the data sub-type is the last 1198 part of the name of the attribute: Name, Index, DateAndTime, TimeStamp, 1199 etc. For example, documentFormatIndex(37) is an index. 1201 NOTE: The Table of Contents also lists the data sub-type and/or data 1202 sub-types of each attribute, using the textual-convention name when such 1204 Job Monitoring MIB, V0.84 July 21, 1997 1206 is defined. The following abbreviations are used in the Table of 1207 Contents as shown: 1209 'Int32(-2..)' Integer32(-2..2147483647) 1211 'Int32(0..)' Integer32(0..2147483647) 1213 'Int32(1..)' Integer32(1..2147483647) 1215 'Int32(m..n)' For all other Integer ranges, the lower 1216 and upper bound of the range is 1217 indicated. 1219 'Octets63' OCTET STRING(SIZE(0..63)) 1221 'Octets(m..n)' For all other OCTET STRING ranges, the 1222 exact range is indicated. 1224 3.3.4 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 1226 Most attributes SHALL have only one row per job. However, a few 1227 attributes can have multiple values per job or even per document, where 1228 each value is a separate row in the jmAttributeTable. Unless indicated 1229 with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL 1230 ensure that each attribute occurs only once in the jmAttributeTable for 1231 a job. Most of the 'MULTI-ROW' attributes do not allow duplicate 1232 values, i.e., the agent SHALL ensure that each value occurs only once 1233 for a job. Only if the specification of the 'MULTI-ROW' attribute also 1234 says "the values NEED NOT be unique" can the agent allow duplicate 1235 values to occur for the job. 1237 NOTE - Duplicate are allowed for 'extensive' 'MULTI-ROW' attributes, 1238 such as fileName(34) or documentName(35), but are not allowed for 1239 'intensive' 'MULTI-ROW' attributes, such as mediumConsumed(171) and 1240 documentFormat(38). 1242 3.3.5 Requested Attributes 1244 A number of attributes record requirements for the job. Such attribute 1245 names end with the word 'Requested'. In the interests of brevity, the 1246 phrase 'requested' SHALL mean: (1) requested by the client (or 1247 intervening server) in the job submission protocol and MAY also mean (2) 1248 embedded in the submitted document data, and/or (3) defaulted by the 1249 recipient device or server with the same semantics as if the requester 1250 had supplied, depending on implementation. 1252 Job Monitoring MIB, V0.84 July 21, 1997 1254 3.3.6 Consumption Attributes 1256 A number of attributes record consumption. Such attribute names end 1257 with the word 'Completed' or 'Consumed'. If the job has not yet 1258 consumed what that resource is metering, the agent either: (1) SHALL 1259 return the value 0 or (2) SHALL not add this attribute to the 1260 jmAttributeTable until the consumption begins. In the interests of 1261 brevity, the semantics for 0 is specified once here and is not repeated 1262 for each consumptive attribute specification. 1264 3.3.7 Index Value Attributes 1266 A number of attributes are indexes in other tables. Such attribute 1267 names end with the word 'Index'. If the agent has not (yet) assigned an 1268 index value for a particular index attribute for a job, the agent SHALL 1269 either: (1) return the value 0 or (2) not add this attribute to the 1270 jmAttributeTable until the index value is assigned. In the interests of 1271 brevity, the semantics for 0 is specified once here and is not repeated 1272 for each index attribute specification. 1274 3.4 Job Identification 1276 There are a number of attributes that permit a user, operator or system 1277 administrator to identify jobs of interest, such as jobName, 1278 jobOriginatingHost, etc. In addition, there is a Job Submission ID 1279 object that allows a monitoring application to quickly locate and 1280 identify a particular job of interest that was submitted from a 1281 particular client by the user invoking the monitoring application. The 1282 Job Monitoring MIB needs to provide for identification of the job at 1283 both sides of the job submission process. The primary identification 1284 point is the client side. The Job Submission ID allows the monitoring 1285 application to identify the job of interest from all the jobs currently 1286 "known" by the server or device. The Job Submission ID can be assigned 1287 by either the client's local system or a downstream server or device. 1288 The point of assignment depends on the job submission protocol in use. 1290 The server/device-side identifier, called the jmJobIndex object, SHALL 1291 be assigned by the SNMP Job Monitoring MIB agent when the server or 1292 device accepts the jobs from submitting clients. The jmJobIndex object 1293 allows the interested party to obtain all objects desired that relate to 1294 this job. The MIB provides a mapping table that maps each Job 1295 Submission ID (generated by the client) to the corresponding jmJobIndex 1296 value generated by the agent, so that an application can determine the 1297 correct value for the jmJobIndex value for the job of interest in a 1298 single Get operation, given the Job Submission ID. See the 1299 jmJobIDGroup. 1301 Job Monitoring MIB, V0.84 July 21, 1997 1303 The jobName attribute provides a name that the user supplies as a job 1304 attribute with the job. The jobName attribute is not necessarily 1305 unique, even for one user, let alone across users. 1307 3.5 Internationalization Considerations 1309 There are a number of objects in this MIB that are represented as coded 1310 character sets with a data type of OCTET STRING. Most of the objects 1311 are supplied as job attributes by the client that submits the job to the 1312 server or device and so are represented in the coded character set 1313 specified by that client. 1315 For simplicity, this specification assumes that the clients, job 1316 monitoring applications, servers, and devices are all running in the 1317 same locale, including locales that use two-octet coded character sets, 1318 such as ISO 10646 (Unicode). Job monitoring applications are expected 1319 to understand the coded character set of the client (and job), server, 1320 or device. No special means is provided for the monitor to discover the 1321 coded character set used by jobs or by the server or device. This 1322 specification does not contain an object that indicates what locale the 1323 server or device is running in, let alone contain an object to control 1324 what locale the agent is to use to represent coded character set 1325 objects. 1327 This MIB also contains objects that are represented using the 1328 DateAndTime textual convention from SMIv2 [SMIv2-TC]. The job 1329 management application SHALL display such objects in the locale of the 1330 user running the monitoring application. 1332 3.6 IANA Considerations 1334 During the development of this standard, the Printer Working Group (PWG) 1335 working with IANA [iana] will register additional enums while the 1336 standard is in the proposed and draft states according to the procedures 1337 described in this section. IANA will handle registration of additional 1338 enums after this standard is approved in cooperation with an IANA- 1339 appointed registration editor from the PWG according to the procedures 1340 described in this section: 1342 3.6.1 IANA Registration of enums 1344 This specification uses textual conventions to define enumerated values 1345 (enums) and bit values. Enumerations (enums) and bit values are sets of 1346 symbolic values defined for use with one or more objects or attributes. 1347 All enumeration sets and bit value sets are assigned a symbolic data 1348 type name (textual convention). As a convention the symbolic name ends 1349 in "TC" for textual convention. These enumerations are defined at the 1350 beginning of the MIB module specification. 1352 Job Monitoring MIB, V0.84 July 21, 1997 1354 This working group has defined several type of enumerations for use in 1355 the Job Monitoring MIB and the Printer MIB[print-mib]. These types 1356 differ in the method employed to control the addition of new 1357 enumerations. Throughout this document, references to "type n enum", 1358 where n can be 1, 2 or 3 can be found in the various tables. The 1359 definitions of these types of enumerations are: 1361 3.6.1.1 Type 1 enumerations 1363 Type 1 enumeration: All the values are defined in the Job Monitoring 1364 MIB specification (RFC for the Job Monitoring MIB). Additional 1365 enumerated values require a new RFC. 1367 There are no type 1 enums in the current draft. 1369 3.6.1.2 Type 2 enumerations 1371 Type 2 enumeration: An initial set of values are defined in the Job 1372 Monitoring MIB specification. Additional enumerated values are 1373 registered after review by this working group or an editor appointed by 1374 IANA after this working group is no longer active. 1376 The following type 2 enums are contained in the current draft : 1378 1.JmTimeStampTC 1380 2.JmFinishingTC [same enum values as IPP "finishing" attribute] 1382 3.JmPrintQualityTC [same enum values as IPP "print-quality" 1383 attribute] 1385 4.JmTonerEconomyTC 1387 5.JmMediumTypeTC 1389 6.JmJobSubmissionTypeTC 1391 7.JmJobStateTC [same enum values as IPP "job-state" attribute] 1393 8.JmAttributeTypeTC 1395 For those textual conventions that have the same enum values as the 1396 indicated IPP Job attribute SHALL be simultaneously registered by IANA 1397 for use with IPP [ipp-model] and the Job Monitoring MIB. 1399 Job Monitoring MIB, V0.84 July 21, 1997 1401 3.6.1.3 Type 3 enumeration 1403 Type 3 enumeration: An initial set of values are defined in the Job 1404 Monitoring MIB specification. Additional enumerated values are 1405 registered through IANA without working group review. 1407 There are no type 3 enums in the current draft. 1409 3.6.2 IANA Registration of type 2 bit values 1411 This draft contains the following type 2 bit value textual-conventions: 1413 1.JmJobServiceTypesTC 1415 2.JmJobStateReasons1TC 1417 3.JmJobStateReasons2TC 1419 4.JmJobStateReasons3TC 1421 5.JmJobStateReasons4TC 1423 These textual-conventions are defined as bits in an Integer so that they 1424 can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4) attributes 1425 are defined as bit values using the corresponding JmJobStateReasonsNTC 1426 textual-conventions. 1428 The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit 1429 values SHALL follow the procedures for a type 2 enum as specified in 1430 Section 3.6.1.2. 1432 3.6.3 IANA Registration of Job Submission Id Formats 1434 In addition to enums and bit values, this specification assigns a single 1435 ASCII digit or letter to various job submission ID formats. See the 1436 JmJobSubmissionIDTypeTC textual-convention and the object. The 1437 registration of jmJobSubmissionID format numbers SHALL follow the 1438 procedures for a type 2 enum as specified in Section 3.6.1.2. 1440 3.6.4 IANA Registration of MIME types/sub-types for document-formats 1442 The documentFormat(38) attribute has MIME type/sub-type values for 1443 indicating document formats which IANA registers as "media type" names. 1444 The values of the documentFormat(38) attribute are the same as the 1445 corresponding Internet Printing Protocol (IPP) "document-format" Job 1446 attribute values [ipp-model]. 1448 Job Monitoring MIB, V0.84 July 21, 1997 1450 3.7 Security Considerations 1452 3.7.1 Read-Write objects 1454 All objects are read-only, greatly simplifying the security 1455 considerations. If another MIB augments this MIB, that MIB might accept 1456 SNMP Write operations to objects in that MIB whose effect is to modify 1457 the values of read-only objects in this MIB. However, that MIB SHALL 1458 have to support the required access control in order to achieve 1459 security, not this MIB. 1461 3.7.2 Read-Only Objects In Other User's Jobs 1463 The security policy of some sites MAY be that unprivileged users can 1464 only get the objects from jobs that they submitted, plus a few minimal 1465 objects from other jobs, such as the jmJobKOctetsRequested and 1466 jmJobKOctetsCompleted objects, so that a user can tell how busy a 1467 printer is. Other sites MAY allow all unprivileged users to see all 1468 objects of all jobs. This MIB does not require, nor does it specify 1469 how, such restrictions would be implemented. A monitoring application 1470 SHOULD enforce the site security policy with respect to returning 1471 information to an unprivileged end user that is using the monitoring 1472 application to monitor jobs that do not belong to that user, i.e., the 1473 jmJobOwner object in the jmJobTable does not match the user's user name. 1475 An operator is a privileged user that would be able to see all objects 1476 of all jobs, independent of the policy for unprivileged users. 1478 3.8 Notifications 1480 This MIB does not specify any notifications. For simplicity, management 1481 applications are expected to poll for status. The 1482 jmGeneralJobPersistence and jmGeneralAttributePersistence objects assist 1483 an application to determine the polling rate. The resulting network 1484 traffic is not expected to be significant. 1486 4. MIB specification 1488 The following pages constitute the actual Job Monitoring MIB. 1490 Job Monitoring MIB, V0.84 July 21, 1997 1492 Job-Monitoring-MIB DEFINITIONS ::= BEGIN 1494 IMPORTS 1495 MODULE-IDENTITY, OBJECT-TYPE, experimental, 1496 Integer32 FROM SNMPv2-SMI 1497 TEXTUAL-CONVENTION FROM SNMPv2-TC 1498 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 1499 -- The following textual-conventions are needed 1500 -- to implement certain attributes, but are not 1501 -- needed to compile this MIB. They are 1502 -- provided here for convenience: 1503 -- hrDeviceIndex FROM HOST-RESOURCES-MIB 1504 -- DateAndTime FROM SNMPv2-TC 1505 -- PrtInterpreterLangFamilyTC FROM Printer-MIB 1507 - -- Use the experimental (54) OID assigned to the Printer MIB[print-mib] 1508 - -- before it was published as RFC 1759. 1509 - -- Upon publication of the Job Monitoring MIB as an RFC, delete this 1510 - -- comment and the line following this comment and change the 1511 - -- reference of { temp 105 } (below) to { mib-2 X }. 1512 - -- This will result in changing: 1513 - -- 1 3 6 1 3 54 jobmonMIB(105) to: 1514 - -- 1 3 6 1 2 1 jobmonMIB(X) 1515 - -- This will make it easier to translate prototypes to 1516 - -- the standard namespace because the lengths of the OIDs won't 1517 - -- change. 1518 temp OBJECT IDENTIFIER ::= { experimental 54 } 1520 jobmonMIB MODULE-IDENTITY 1521 LAST-UPDATED "9707210000Z" 1522 ORGANIZATION "IETF Printer MIB Working Group" 1523 CONTACT-INFO 1524 "Tom Hastings 1525 Postal: Xerox Corp. 1526 Mail stop ESAE-231 1527 701 S. Aviation Blvd. 1528 El Segundo, CA 90245 1530 Tel: (301)333-6413 1531 Fax: (301)333-5514 1532 E-mail: hastings@cp10.es.xerox.com 1534 Send comments to the printmib WG using the Job Monitoring 1535 Project (JMP) Mailing List: jmp@pwg.org 1537 To learn how to subscribe to the JMP mailing list, 1538 send email to: jmp-request@pwg.org 1540 Job Monitoring MIB, V0.84 July 21, 1997 1542 For further information, access the PWG web page under 'JMP': 1543 http://www.pwg.org/" 1544 DESCRIPTION 1545 "The MIB module for monitoring job in servers, printers, and 1546 other devices. 1548 File: draft-ietf-printmib-job-monitor-04.txt 1549 Version: 0.84" 1550 ::= { temp 105 } 1552 - -- Textual conventions for this MIB module 1554 JmTimeStampTC ::= TEXTUAL-CONVENTION 1555 STATUS current 1556 DESCRIPTION 1557 "The simple time at which an event took place. The units SHALL 1558 be in seconds since the system was booted. 1560 NOTE - JmTimeStampTC is defined in units of seconds, rather than 1561 100ths of seconds, so as to be simpler for agents to implement 1562 (even if they have to implement the 100ths of a second to comply 1563 with implementing sysUpTime in MIB-II[mib-II].) 1565 NOTE - JmTimeStampTC is defined as an Integer32 so that it can 1566 be used as a value of an attribute, i.e., as a value of the 1567 jmAttributeValueAsInteger object. The TimeStamp textual- 1568 convention defined in SMNPv2-TC is defined as an APPLICATION 3 1569 IMPLICIT INTEGER tag, not an Integer32, so cannot be used in 1570 this MIB as one of the values of jmAttributeValueAsInteger." 1571 SYNTAX INTEGER(0..2147483647) 1573 JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION 1574 STATUS current 1575 DESCRIPTION 1576 "The source platform type that can submit jobs to servers or 1577 devices in any of the 3 configurations." 1578 REFERENCE 1579 "This is a type 2 enumeration. See Section 3.6.1.2." 1580 SYNTAX INTEGER { 1581 other(1), 1583 Job Monitoring MIB, V0.84 July 21, 1997 1585 unknown(2), 1586 sptUNIX(3), -- UNIX(tm) 1587 sptOS2(4), -- OS/2 1588 sptPCDOS(5), -- DOS 1589 sptNT(6), -- NT 1590 sptMVS(7), -- MVS 1591 sptVM(8), -- VM 1592 sptOS400(9), -- OS/400 1593 sptVMS(10), -- VMS 1594 sptWindows95(11), -- Windows95 1595 sptNetWare(33) -- NetWare 1596 } 1598 JmFinishingTC ::= TEXTUAL-CONVENTION 1599 STATUS current 1600 DESCRIPTION 1601 "The type of finishing operation. 1603 These values are the same as the enum values of the IPP 1604 'finishings' attribute. See Section 3.6.1.2. 1606 other(1), 1607 Some other finishing operation besides one of the specified 1608 or registered values. 1610 unknown(2), 1611 The finishing is unknown. 1613 none(3), 1614 Perform no finishing. 1616 staple(4), 1617 Bind the document(s) with one or more staples. The exact 1618 number and placement of the staples is site-defined. 1620 stapleTopLeft(5), 1621 Place one or more staples on the top left corner of the 1622 document(s). 1624 stapleBottomLeft(6), 1625 Place one or more staples on the bottom left corner of the 1626 document(s). 1628 Job Monitoring MIB, V0.84 July 21, 1997 1630 stapleTopRight(7), 1631 Place one or more staples on the top right corner of the 1632 document(s). 1634 stapleBottomRight(8), 1635 Place one or more staples on the bottom right corner of the 1636 document(s). 1638 saddleStitch(9), 1639 Bind the document(s) with one or more staples (wire 1640 stitches) along the middle fold. The exact number and 1641 placement of the stitches is site-defined. 1643 edgeStitch(10), 1644 Bind the document(s) with one or more staples (wire 1645 stitches) along one edge. The exact number and placement of 1646 the staples is site-defined. 1648 punch(11), 1649 This value indicates that holes are required in the finished 1650 document. The exact number and placement of the holes is 1651 site-defined The punch specification MAY be satisfied (in a 1652 site- and implementation-specific manner) either by 1653 drilling/punching, or by substituting pre-drilled media. 1655 cover(12), 1656 This value is specified when it is desired to select a non- 1657 printed (or pre-printed) cover for the document. This does 1658 not supplant the specification of a printed cover (on cover 1659 stock medium) by the document itself. 1661 bind(13) 1662 This value indicates that a binding is to be applied to the 1663 document; the type and placement of the binding is product- 1664 specific." 1665 REFERENCE 1666 "This is a type 2 enumeration. See Section 3.6.1.2." 1667 SYNTAX INTEGER { 1668 other(1), 1669 unknown(2), 1670 none(3), 1671 staple(4), 1672 stapleTopLeft(5), 1673 stapleBottomLeft(6), 1674 stapleTopRight(7), 1675 stapleBottomRight(8), 1676 saddleStitch(9), 1677 edgeStitch(10), 1679 Job Monitoring MIB, V0.84 July 21, 1997 1681 punch(11), 1682 cover(12), 1683 bind(13) 1684 } 1686 JmPrintQualityTC ::= TEXTUAL-CONVENTION 1687 STATUS current 1688 DESCRIPTION 1689 "Print quality settings. 1691 These values are the same as the enum values of the IPP 'print- 1692 quality' attribute. See Section 3.6.1.2." 1693 REFERENCE 1694 "This is a type 2 enumeration. See Section 3.6.1.2." 1695 SYNTAX INTEGER { 1696 other(1), -- Not one of the specified or registered 1697 -- values. 1698 unknown(2), -- The actual value is unknown. 1699 draft(3), -- Lowest quality available on the printer. 1700 normal(4), -- Normal or intermediate quality on the 1701 -- printer. 1702 high(5) -- Highest quality available on the printer. 1703 } 1705 JmPrinterResolutionTC ::= TEXTUAL-CONVENTION 1706 STATUS current 1707 DESCRIPTION 1708 "Printer resolutions. 1710 Nine octets consisting of two 4-octet SIGNED-INTEGERs followed 1711 by a SIGNED-BYTE. The values are the same as those specified in 1712 the Printer MIB [printmib]. The first SIGNED-INTEGER contains 1713 the value of prtMarkerAddressabilityXFeedDir. The second 1714 SIGNED-INTEGER contains the value of 1715 prtMarkerAddressabilityFeedDir. The SIGNED-BYTE contains the 1716 value of prtMarkerAddressabilityUnit. 1718 Note: the latter value is either 3 (tenThousandsOfInches) or 4 1719 (micrometers) and the addressability is in 10,000 units of 1721 Job Monitoring MIB, V0.84 July 21, 1997 1723 measure. Thus the SIGNED-INTEGERs represent integral values in 1724 either dots-per-inch or dots-per-centimeter. 1726 The syntax is the same as the IPP 'printer-resolution' 1727 attribute. See Section 3.6.1.2." 1728 SYNTAX OCTET STRING (SIZE(9)) 1730 JmTonerEconomyTC ::= TEXTUAL-CONVENTION 1731 STATUS current 1732 DESCRIPTION 1733 "Toner economy settings." 1734 REFERENCE 1735 "This is a type 2 enumeration. See Section 3.6.1.2." 1736 SYNTAX INTEGER { 1737 unknown(2), -- unknown. 1738 off(3), -- Off. Normal. Use full toner. 1739 on(4) -- On. Use less toner than normal. 1740 } 1742 JmBooleanTC ::= TEXTUAL-CONVENTION 1743 STATUS current 1744 DESCRIPTION 1745 "Boolean true or false value." 1746 REFERENCE 1747 "This is a type 2 enumeration. See Section 3.6.1.2." 1748 SYNTAX INTEGER { 1749 unknown(2), -- unknown. 1750 false(3), -- FALSE. 1751 true(4) -- TRUE. 1752 } 1754 JmMediumTypeTC ::= TEXTUAL-CONVENTION 1755 STATUS current 1757 Job Monitoring MIB, V0.84 July 21, 1997 1759 DESCRIPTION 1760 "Identifies the type of medium. 1762 other(1), 1763 The type is neither one of the values listed in this 1764 specification nor a registered value. 1766 unknown(2), 1767 The type is not known. 1769 stationery(3), 1770 Separately cut sheets of an opaque material. 1772 transparency(4), 1773 Separately cut sheets of a transparent material. 1775 envelope(5), 1776 Envelopes that can be used for conventional mailing 1777 purposes. 1779 envelopePlain(6), 1780 Envelopes that are not preprinted and have no windows. 1782 envelopeWindow(7), 1783 Envelopes that have windows for addressing purposes. 1785 continuousLong(8), 1786 Continuously connected sheets of an opaque material 1787 connected along the long edge. 1789 continuousShort(9), 1790 Continuously connected sheets of an opaque material 1791 connected along the short edge. 1793 tabStock(10), 1794 Media with tabs. 1796 multiPartForm(11), 1797 Form medium composed of multiple layers not pre-attached to 1798 one another; each sheet MAY be drawn separately from an 1799 input source. 1801 labels(12), 1802 Label-stock. 1804 multiLayer(13) 1805 Form medium composed of multiple layers which are pre- 1806 attached to one another, e.g. for use with impact printers." 1808 Job Monitoring MIB, V0.84 July 21, 1997 1810 REFERENCE 1811 "This is a type 2 enumeration. See Section 3.6.1.2." 1812 SYNTAX INTEGER { 1813 other(1), 1814 unknown(2), 1815 stationery(3), 1816 transparency(4), 1817 envelope(5), 1818 envelopePlain(6), 1819 envelopeWindow(7), 1820 continuousLong(8), 1821 continuousShort(9), 1822 tabStock(10), 1823 multiPartForm(11), 1824 labels(12), 1825 multiLayer(13) 1826 } 1828 JmJobSubmissionTypeTC ::= TEXTUAL-CONVENTION 1829 STATUS current 1830 DESCRIPTION 1831 "Identifies the format type of a job submission ID. 1833 The ASCII characters '0-9', 'A-Z', and 'a-z' are assigned in 1834 order giving 62 possible formats. 1836 Each job submission ID is a fixed-length, 48-octet printable 1837 ASCII coded character string, consisting of the following 1838 fields: 1840 octet 1 The format letter. 1841 octets 2-40 A 39-character, ASCII trailing SPACE filled 1842 field specified by the format letter, if the 1843 data is less than 39 ASCII characters. 1844 octets 41-48 A sequential or random number to make the ID 1845 quasi-unique. 1847 If the client does not supply a job submission ID in the job 1848 submission protocol, then the server SHALL assign a job 1849 submission ID using any of the standard formats that are 1850 reserved to the agent. Clients SHALL not use formats that are 1851 reserved to agents. 1853 Job Monitoring MIB, V0.84 July 21, 1997 1855 The format values defined at the time of completion of the 1856 specification are: 1858 Format 1859 Letter Description 1860 ------ ------------ 1861 '0' octets 2-40: last 39 bytes of the jmJobOwner 1862 object. 1863 octets 41-48: 8-decimal-digit sequential number 1864 This format is reserved to agents for use when 1865 the client does not supply a job submission ID. 1866 Clients wishing to use a job submission ID that 1867 incorporates the job owner, SHALL use format '8'. 1869 NOTE - other formats may be registered that are 1870 reserved to the agent for use when the client does 1871 not supply a job submission ID. 1873 '1' octets 2-40: last 39 bytes of the jobName attribute. 1874 octets 41-48: 8-decimal-digit random number 1876 '2' octets 2-40: Client MAC address: in hexadecimal 1877 with each nibble of the 6 octet address being 1878 '0'-'9' or 'A' - 'F' (uppercase only). 1879 Most significant octet first. 1880 octets 41-48: 8-decimal-digit sequential number 1882 '3' octets 2-40: last 39 bytes of the client URL 1883 [URI-spec]. 1884 octets 41-48: 8-decimal-digit sequential number 1886 '4' octets 2-40: last 39 bytes of the URI [URI-spec] 1887 assigned by the server or device to the job when 1888 the job was submitted for processing. 1889 octets 41-48: 8-decimal-digit sequential number 1891 '5' octets 2-40: last 39 bytes of a user number, such 1892 as POSIX user number. 1893 octets 41-48: 8-decimal-digit sequential number 1895 '6' octets 2-40: last 39 bytes of the user account 1896 number. 1897 octets 41-48: 8-decimal-digit sequential number 1899 '7' octets 2-40: last 39 bytes of the DTMF incoming 1900 FAX routing number. 1901 octets 41-48: 8-decimal-digit sequential number 1903 Job Monitoring MIB, V0.84 July 21, 1997 1905 '8' octets 2-40: last 39 bytes of the job owner name 1906 (that the agent returns in the jmJobOwner object). 1907 octets 41-48: 8-decimal-digit sequential number 1909 NOTE - the job submission id is only intended to be unique 1910 between a limited set of clients for a limited duration of time, 1911 namely, for the life time of the job in the context of the 1912 server or device that is processing the job. Some of the 1913 formats include something that is unique per client and a random 1914 number so that the same job submitted by the same client will 1915 have a different job submission id. For other formats, where 1916 part of the id is guaranteed to be unique for each client, such 1917 as the MAC address or URL, a sequential number SHOULD suffice 1918 for each client (and may be easier for each client to manage). 1919 Therefore, the length of the job submission id has been selected 1920 to reduce the probability of collision to an extremely low 1921 number, but is not intended to be an absolute guarantee of 1922 uniqueness. None-the-less, collisions are remotely possible, 1923 but without bad consequences, since this MIB is intended to be 1924 used only for monitoring jobs, not for controlling and managing 1925 them." 1926 REFERENCE 1927 "This is like a type 2 enumeration. See section 3.6.3." 1928 SYNTAX OCTET STRING(SIZE(1)) -- ASCII '0'-'9', 'A'-'Z', 'a'-'z' 1930 JmJobStateTC ::= TEXTUAL-CONVENTION 1931 STATUS current 1932 DESCRIPTION 1933 "The current state of the job (pending, processing, completed, 1934 etc.). 1936 The following figure shows the normal job state transitions: 1938 +----> canceled(7) 1939 / 1940 +---> pending(3) --------> processing(5) ------+------> completed(9) 1941 | ^ ^ \ 1942 - --->+ | | +----> aborted(8) 1943 | v v / 1944 +---> pendingHeld(4) processingStopped(6) ---+ 1946 Figure 4 - Normal Job State Transitions 1948 Job Monitoring MIB, V0.84 July 21, 1997 1950 Normally a job progresses from left to right. Other state 1951 transitions are unlikely, but are not forbidden. Not shown are 1952 the transitions to the canceled state from the pending, 1953 pendingHeld, processing, and processingStopped states. 1955 Jobs in the pending, processing, and processingStopped states 1956 are called 'active', while jobs in the pendingHeld, canceled, 1957 aborted, and completed are called 'inactive'. 1959 These values are the same as the enum values of the IPP 'job- 1960 state' job attribute. See Section 3.6.1.2. 1962 other(1), 1963 The job state is not one of the defined states. 1965 unknown(2), 1966 The job state is not known, or its state is indeterminate. 1968 pending(3), 1969 The job is a candidate to start processing, but is not yet 1970 processing. 1972 pendingHeld(4), 1973 The job is not a candidate for processing for any number of 1974 reasons but will return to the pending state as soon as the 1975 reasons are no longer present. The job's jmJobStateReasons1 1976 object and/or jobStateReasonsN (N=2..4) attributes SHALL 1977 indicate why the job is no longer a candidate for 1978 processing. The reasons are represented as bits in the 1979 jmJobStateReasons1 object and/or jobStateReasonsN (N=2..4) 1980 attributes. See the JmJobStateReasonsNTC (N=1..4) textual 1981 convention for the specification of each reason. 1983 processing(5), 1984 Either: 1986 1. The job is using, or is attempting to use, one or more 1987 document transforms which include (1) purely software 1988 processes that are interpreting a PDL, and (2) hardware 1989 devices that are interpreting a PDL, making marks on a 1990 medium, and/or performing finishing, such as stapling, etc. 1992 OR 1994 2. (configuration 2) the server has made the job ready for 1995 printing, but the output device is not yet printing it, 1996 either because the job hasn't reached the output device or 1998 Job Monitoring MIB, V0.84 July 21, 1997 2000 because the job is queued in the output device or some other 2001 spooler, awaiting the output device to print it. 2003 When the job is in the processing state, the entire job 2004 state includes the detailed status represented in the device 2005 MIB indicated by the hrDeviceIndex value of the job's 2006 physicalDevice attribute, if the agent implements such a 2007 device MIB. 2009 Implementations MAY, though they NEED NOT, include 2010 additional values in the job's jmJobStateReasons1 object to 2011 indicate the progress of the job, such as adding the 2012 jobPrinting value to indicate when the device is actually 2013 making marks on a medium. 2015 processingStopped(6), 2016 The job has stopped while processing for any number of 2017 reasons and will return to the processing state as soon as 2018 the reasons are no longer present. 2020 The job's jmJobStateReasons1 object and/or the job's 2021 jobStateReasonsN (N=2..4) attributes MAY indicate why the 2022 job has stopped processing. For example, if the output 2023 device is stopped, the deviceStopped value MAY be included 2024 in the job's jmJobStateReasons1 object. 2026 NOTE - When an output device is stopped, the device usually 2027 indicates its condition in human readable form at the 2028 device. The management application can obtain more complete 2029 device status remotely by querying the appropriate device 2030 MIB using the job's deviceIndex attribute(s), if the agent 2031 implements such a device MIB 2033 canceled(7), 2034 A client has canceled the job and the job is either: (1) in 2035 the process of being terminated by the server or device or 2036 (2) has completed terminating. The job's jmJobStateReasons1 2037 object SHOULD contain either the canceledByUser or 2038 canceledByOperator value. 2040 aborted(8), 2041 The job has been aborted by the system, usually while the 2042 job was in the processing or processingStopped state. 2044 completed(9) 2045 The job has completed successfully or with warnings or 2046 errors after processing and all of the media have been 2047 successfully stacked in the appropriate output bin(s). The 2049 Job Monitoring MIB, V0.84 July 21, 1997 2051 job's jmJobStateReasons1 object SHOULD contain one of: 2052 completedSuccessfully, completedWithWarnings, or 2053 completedWithErrors values." 2054 REFERENCE 2055 "This is a type 2 enumeration. See Section 3.6.1.2." 2056 SYNTAX INTEGER { 2057 other(1), 2058 unknown(2), 2059 pending(3), 2060 pendingHeld(4), 2061 processing(5), 2062 processingStopped(6), 2063 canceled(7), 2064 aborted(8), 2065 completed(9) 2066 } 2068 JmAttributeTypeTC ::= TEXTUAL-CONVENTION 2069 STATUS current 2070 DESCRIPTION 2071 "The type of the attribute which identifies the attribute. 2073 In the following definitions of the enums, each description 2074 indicates whether the useful value of the attribute SHALL be 2075 represented using the jmAttributeValueAsInteger or the 2076 jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' 2077 or 'OCTETS:', respectively. 2079 Some attributes allow the agent implementer a choice of useful 2080 values of either an integer, an octets representation, or both, 2081 depending on implementation. These attributes are indicated 2082 with 'INTEGER:' AND/OR 'OCTETS:' tags. 2084 A very few attributes require both objects at the same time to 2085 represent a pair of useful values (see mediumConsumed(171)). 2086 These attributes are indicated with 'INTEGER:' AND 'OCTETS:' 2087 tags. See the jmAttributeGroup for the descriptions of these 2088 two MANDATORY objects. 2090 NOTE - The enum assignments are grouped logically with values 2091 assigned in groups of 20, so that additional values may be 2092 registered in the future and assigned a value that is part of 2093 their logical grouping. 2095 NOTE: No attribute name exceeds 31 characters. 2097 Job Monitoring MIB, V0.84 July 21, 1997 2099 The standard attribute types defined at the time of completion 2100 of the specification are: 2102 jmAttributeTypeIndex Datatype 2103 -------------------- -------- 2105 other(1), Integer32(-2..2147483647) 2106 AND/OR 2107 OCTET STRING(SIZE(0..63)) 2108 INTEGER: and/or OCTETS: An attribute that is not in the 2109 list and/or that has not been approved and registered with 2110 IANA. 2112 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2113 + Job State attributes 2114 + 2115 + The following attributes specify the state of a job. 2116 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2118 jobStateReasons2(3), JmJobStateReasons2TC 2119 INTEGER: Additional information about the job's current 2120 state that augments the jmJobState object. See the 2121 description under the JmJobStateReasons1TC textual- 2122 convention. 2124 jobStateReasons3(4), JmJobStateReasons3TC 2125 INTEGER: Additional information about the job's current 2126 state that augments the jmJobState object. See the 2127 description under JmJobStateReasons1TC textual-convention. 2129 jobStateReasons4(5), JmJobStateReasons4TC 2130 INTEGER: Additional information about the job's current 2131 state that augments the jmJobState object. See the 2132 description under JmJobStateReasons1TC textual-convention. 2134 processingMessage(6), OCTET STRING(SIZE(0..63)) 2135 OCTETS: MULTI-ROW: A coded character set message that is 2136 generated during the processing of the job as a simple form 2137 of processing log to show progress and any problems. 2139 There is no restriction for the same message occurring in 2140 multiple rows. 2142 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2143 + Job Identification attributes 2144 + 2146 Job Monitoring MIB, V0.84 July 21, 1997 2148 + The following attributes help an end user, a system 2149 + operator, or an accounting program identify a job. 2150 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2152 jobAccountName(21), OCTET STRING(SIZE(0..63)) 2153 OCTETS: Arbitrary binary information which MAY be coded 2154 character set data or encrypted data supplied by the 2155 submitting user for use by accounting services to allocate 2156 or categorize charges for services provided, such as a 2157 customer account name or number. 2159 NOTE: This attribute NEED NOT be printable characters. 2161 serverAssignedJobName(22), OCTET STRING(SIZE(0..63)) 2162 OCTETS: Configuration 3 only: The human readable string 2163 name, number, or ID of the job as assigned by the server 2164 that submitted the job to the device that the agent is 2165 providing access to with this MIB. 2167 NOTE - This attribute is intended for enabling a user to 2168 find his/her job that a server submitted to a device when 2169 either the client does not support the jmJobSubmissionID or 2170 the server does not pass the jmJobSubmissionID through to 2171 the device. 2173 jobName(23), OCTET STRING(SIZE(0..63)) 2174 OCTETS: The human readable string name of the job as 2175 assigned by the submitting user to help the user distinguish 2176 between his/her various jobs. This name does not need to be 2177 unique. 2179 This attribute is intended for enabling a user or the user's 2180 application to convey a job name that MAY be printed on a 2181 start sheet, returned in a query result, or used in 2182 notification or logging messages. 2184 In order to assist users to find their jobs for job 2185 submission protocols that don't supply a jmJobSubmissionID, 2186 the agent SHOULD maintain the jobName attribute for the time 2187 specified by the jmGeneralJobPersistence object, rather than 2188 the (shorter) jmGeneralAttributePersistence object. 2190 If this attribute is not specified when the job is 2191 submitted, no job name is assumed, but implementation 2192 specific defaults are allowed, such as the value of the 2194 Job Monitoring MIB, V0.84 July 21, 1997 2196 documentName attribute of the first document in the job or 2197 the fileName attribute of the first document in the job. 2199 The jobName attribute is distinguished from the jobComment 2200 attribute, in that the jobName attribute is intended to 2201 permit the submitting user to distinguish between different 2202 jobs that he/she has submitted. The jobComment attribute is 2203 intended to be free form additional information that a user 2204 might wish to use to communicate with himself/herself, such 2205 as a reminder of what to do with the results or to indicate 2206 a different set of input parameters were tried in several 2207 different job submissions. 2209 jobServiceTypes(24), JmJobServiceTypesTC 2210 INTEGER: Specifies the type(s) of service to which the job 2211 has been submitted (print, fax, scan, etc.). The service 2212 type is bit encoded with each job service type so that more 2213 general and arbitrary services can be created, such as 2214 services with more than one destination type, or ones with 2215 only a source or only a destination. For example, a job 2216 service might scan, faxOut, and print a single job. In this 2217 case, three bits would be set in the jobServiceTypes 2218 attribute, corresponding to the hexadecimal values: 0x8 + 2219 0x20 + 0x4, respectively, yielding: 0x2C. 2221 Whether this attribute is set from a job attribute supplied 2222 by the job submission client or is set by the recipient job 2223 submission server or device depends on the job submission 2224 protocol. This attribute SHALL be implemented if the server 2225 or device has other types in addition to or instead of 2226 printing. 2228 One of the purposes of this attribute is to permit a 2229 requester to filter out jobs that are not of interest. For 2230 example, a printer operator may only be interested in jobs 2231 that include printing. 2233 jobSourceChannelIndex(25), Integer32(0..2147483647) 2234 INTEGER: The index of the row in the associated Printer 2235 MIB[print-mib] of the channel which is the source of the 2236 print job. 2238 jobSourcePlatformType(26), JmJobSourcePlatformTypeTC 2239 INTEGER: The source platform type of the immediate upstream 2240 submitter that submitted the job to the server 2241 (configuration 2) or device (configuration 1 and 3) to which 2242 the agent is providing access. For configuration 1, this is 2243 the type of the client that submitted the job to the device; 2245 Job Monitoring MIB, V0.84 July 21, 1997 2247 for configuration 2, this is the type of the client that 2248 submitted the job to the server; and for configuration 3, 2249 this is the type of the server that submitted the job to the 2250 device. 2252 submittingServerName(27), OCTET STRING(SIZE(0..63)) 2253 OCTETS: For configuration 3 only: The administrative name 2254 of the server that submitted the job to the device. 2256 submittingApplicationName(28), OCTET STRING(SIZE(0..63)) 2257 OCTETS: The name of the client application (not the server 2258 in configuration 3) that submitted the job to the server or 2259 device. 2261 jobOriginatingHost(29), OCTET STRING(SIZE(0..63)) 2262 OCTETS: The name of the client host (not the server host 2263 name in configuration 3) that submitted the job to the 2264 server or device. 2266 deviceNameRequested(30), OCTET STRING(SIZE(0..63)) 2267 OCTETS: The administratively defined coded character set 2268 name of the target device requested by the submitting user. 2269 For configuration 1, its value corresponds to the Printer 2270 MIB[print-mib]: prtGeneralPrinterName object. For 2271 configuration 2 and 3, its value is the name of the logical 2272 or physical device that the user supplied to indicate to the 2273 server on which device(s) they wanted the job to be 2274 processed. 2276 queueNameRequested(31), OCTET STRING(SIZE(0..63)) 2277 OCTETS: The administratively defined coded character set 2278 name of the target queue requested by the submitting user. 2279 For configuration 1, its value corresponds to the queue in 2280 the device for which the agent is providing access. For 2281 configuration 2 and 3, its value is the name of the queue 2282 that the user supplied to indicate to the server on which 2283 device(s) they wanted the job to be processed. 2285 NOTE - typically an implementation SHOULD support either the 2286 deviceNameRequested or queueNameRequested attribute, but not 2287 both. 2289 physicalDevice(32), hrDeviceIndex 2290 AND/OR 2291 OCTET STRING(SIZE(0..63)) 2292 INTEGER: MULTI-ROW: The index of the physical device MIB 2293 instance requested/used, such as the Printer MIB[print-mib]. 2295 Job Monitoring MIB, V0.84 July 21, 1997 2297 This value is an hrDeviceIndex value. See the Host 2298 Resources MIB[hr-mib]. 2300 AND/OR 2302 OCTETS: MULTI-ROW: The name of the physical device to 2303 which the job is assigned. 2305 numberOfDocuments(33), Integer32(-2..2147483647) 2306 INTEGER: The number of documents in this job. 2308 fileName(34), OCTET STRING(SIZE(0..63)) 2309 OCTETS: MULTI-ROW: The coded character set file name or 2310 URI[URI-spec] of the document. 2312 There is no restriction on the same file name occurring in 2313 multiple rows. 2315 documentName(35), OCTET STRING(SIZE(0..63)) 2316 OCTETS: MULTI-ROW: The coded character set name of the 2317 document. 2319 There is no restriction on the same document name occurring 2320 in multiple rows. 2322 jobComment(36), OCTET STRING(SIZE(0..63)) 2323 OCTETS: An arbitrary human-readable coded character text 2324 string supplied by the submitting user or the job submitting 2325 application program for any purpose. For example, a user 2326 might indicate what he/she is going to do with the printed 2327 output or the job submitting application program might 2328 indicate how the document was produced. 2330 The jobComment attribute is not intended to be a name; see 2331 the jobName attribute. 2333 documentFormatIndex(37), Integer32(0..2147483647) 2334 INTEGER: MULTI-ROW: The index in the prtInterpreterTable 2335 in the Printer MIB[print-mib] of the page description 2336 language (PDL) or control language interpreter that this job 2337 requires/uses. A document or a job MAY use more than one 2338 PDL or control language. 2340 NOTE - As with all intensive attributes where multiple rows 2341 are allowed, there SHALL be only one distinct row for each 2342 distinct interpreter; there SHALL be no duplicates. 2344 Job Monitoring MIB, V0.84 July 21, 1997 2346 NOTE - This attribute type is intended to be used with an 2347 agent that implements the Printer MIB and SHALL not be used 2348 if the agent does not implement the Printer MIB. Such an 2349 agent SHALL use the documentFormat attribute instead. 2351 documentFormat(38), PrtInterpreterLangFamilyTC 2352 AND/OR 2353 OCTET STRING(SIZE(0..63)) 2354 INTEGER: MULTI-ROW: The interpreter language family 2355 corresponding to the Printer MIB[print-mib] 2356 prtInterpreterLangFamily object, that this job 2357 requires/uses. A document or a job MAY use more than one 2358 PDL or control language. 2360 AND/OR 2362 OCTETS: MULTI-ROW: The document format registered as a 2363 media type[iana-media-types], i.e., the name of the MIME 2364 content-type/subtype. Examples: 'application/postscript', 2365 'application/vnd.hp-PCL', and 'application/pdf' 2367 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2368 + Job Parameter attributes 2369 + 2370 + The following attributes represent input parameters 2371 + supplied by the submitting client in the job submission 2372 + protocol. 2373 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2375 jobPriority(50), Integer32(1..100) 2376 INTEGER: The priority for scheduling the job. It is used by 2377 servers and devices that employ a priority-based scheduling 2378 algorithm. 2380 A higher value specifies a higher priority. The value 1 is 2381 defined to indicate the lowest possible priority (a job 2382 which a priority-based scheduling algorithm SHALL pass over 2383 in favor of higher priority jobs). The value 100 is defined 2384 to indicate the highest possible priority. Priority is 2385 expected to be evenly or 'normally' distributed across this 2386 range. The mapping of vendor-defined priority over this 2387 range is implementation-specific. 2389 jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC) 2390 OCTETS: The calendar date and time of day after which the 2391 job SHALL become a candidate to be scheduled for processing. 2392 If the value of this attribute is in the future, the server 2394 Job Monitoring MIB, V0.84 July 21, 1997 2396 SHALL set the value of the job's jmJobState object to 2397 pendingHeld and add the jobProcessAfterSpecified bit value 2398 to the job's jmJobStateReasons1 object. When the specified 2399 date and time arrives, the server SHALL remove the 2400 jobProcessAfterSpecified bit value from the job's 2401 jmJobStateReasons1 object and, if no other reasons remain, 2402 SHALL change the job's jmJobState object to pending. 2404 jobHold(52), JmBooleanTC 2405 INTEGER: If the value is 'true(4)', a client has explicitly 2406 specified that the job is to be held until explicitly 2407 released. Until the job is explicitly released by a client, 2408 the job SHALL be in the pendingHeld state with the 2409 jobHoldSpecified value in the jmJobStateReasons1 attribute. 2411 jobHoldUntil(53), OCTET STRING(SIZE(0..63)) 2412 OCTETS: The named time period during which the job SHALL 2413 become a candidate for processing, such as 'evening', 2414 'night', 'weekend', 'second-shift', 'third-shift', etc., as 2415 defined by the system administrator. See IPP [ipp-model] 2416 for the standard keyword values. Until that time period 2417 arrives, the job SHALL be in the pendingHeld state with the 2418 jobHoldUntilSpecified value in the jmJobStateReasons1 2419 object. The value 'no-hold' SHALL indicate explicitly that 2420 no time period has been specified. 2422 outputBin(54), Integer32(0..2147483647) 2423 AND/OR 2424 OCTET STRING(SIZE(0..63)) 2425 INTEGER: MULTI-ROW: The output subunit index in the 2426 Printer MIB[print-mib] 2428 AND/OR 2430 OCTETS: the name or number (represented as ASCII digits) of 2431 the output bin to which all or part of the job is placed in. 2433 sides(55), Integer32(-2..2) 2434 INTEGER: MULTI-ROW: The number of sides, '1' or '2', that 2435 any document in this job requires/used. 2437 finishing(56), JmFinishingTC 2438 INTEGER: MULTI-ROW: Type of finishing that any document in 2439 this job requires/used. 2441 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2442 + Image Quality attributes (requested and consumed) 2444 Job Monitoring MIB, V0.84 July 21, 1997 2446 + 2447 + For devices that can vary the image quality. 2448 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2450 printQualityRequested(70), JmPrintQualityTC 2451 INTEGER: MULTI-ROW: The print quality selection requested 2452 for a document in the job for printers that allow quality 2453 differentiation. 2455 printQualityUsed(71), JmPrintQualityTC 2456 INTEGER: MULTI-ROW: The print quality selection actually 2457 used by a document in the job for printers that allow 2458 quality differentiation. 2460 printerResolutionRequested(72), JmPrinterResolutionTC 2461 OCTETS: MULTI-ROW: The printer resolution requested for a 2462 document in the job for printers that support resolution 2463 selection. 2465 printerResolutionUsed(73), JmPrinterResolutionTC 2466 OCTETS: MULTI-ROW: The printer resolution actually used by 2467 a document in the job for printers that support resolution 2468 selection. 2470 tonerEcomonyRequested(74), JmTonerEconomyTC 2471 INTEGER: MULTI-ROW: The print quality selection requested 2472 for documents in the job for printers that allow toner 2473 quality differentiation. 2475 tonerEcomonyUsed(75), JmTonerEconomyTC 2476 INTEGER: MULTI-ROW: The print quality selection actually 2477 used by documents in the job for printers that allow toner 2478 quality differentiation. 2480 tonerDensityRequested(76), Integer32(-2..100) 2481 INTEGER: MULTI-ROW: The toner density requested for a 2482 document in this job for devices that can vary toner density 2483 levels. Level 1 is the lowest density and level 100 is the 2484 highest density level. Devices with a smaller range, SHALL 2485 map the 1-100 range evenly onto the implemented range. 2487 tonerDensityUsed(77), Integer32(-2..100) 2488 INTEGER: MULTI-ROW: The toner density used by documents in 2489 this job for devices that can vary toner density levels. 2490 Level 1 is the lowest density and level 100 is the highest 2491 density level. Devices with a smaller range, SHALL map the 2492 1-100 range evenly onto the implemented range. 2494 Job Monitoring MIB, V0.84 July 21, 1997 2496 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2497 + Job Progress attributes (requested and consumed) 2498 + 2499 + Pairs of these attributes can be used by monitoring 2500 + applications to show an indication of relative progress 2501 + to users. 2502 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2504 jobCopiesRequested(90), Integer32(-2..2147483647) 2505 INTEGER: The number of copies of the entire job that are to 2506 be produced. 2508 jobCopiesCompleted(91), Integer32(-2..2147483647) 2509 INTEGER: The number of copies of the entire job that have 2510 been completed so far. 2512 documentCopiesRequested(92), Integer32(-2..2147483647) 2513 INTEGER: The total count of the number of document copies 2514 requested. If there are documents A, B, and C, and document 2515 B is specified to produce 4 copies, the number of document 2516 copies requested is 6 for the job. 2518 This attribute SHALL be used only when a job has multiple 2519 documents. The jobCopiesRequested attribute SHALL be used 2520 when the job has only one document. 2522 documentCopiesCompleted(93), Integer32(-2..2147483647) 2523 INTEGER: The total count of the number of document copies 2524 completed so far for the job as a whole. If there are 2525 documents A, B, and C, and document B is specified to 2526 produce 4 copies, the number of document copies starts a 0 2527 and runs up to 6 for the job as the job processes. 2529 This attribute SHALL be used only when a job has multiple 2530 documents. The jobCopiesCompleted attribute SHALL be used 2531 when the job has only one document. 2533 jobKOctetsTransferred(94), Integer32(-2..2147483647) 2534 INTEGER: The number of K (1024) octets transferred to the 2535 server or device to which the agent is providing access. 2536 This count is independent of the number of copies of the job 2537 or documents that will be produced, but it is only a measure 2538 of the number of bytes transferred to the server or device. 2540 The agent SHALL round the actual number of octets 2541 transferred up to the next higher K. Thus 0 octets SHALL be 2542 represented as '0', 1-1024 octets SHALL BE represented as 2544 Job Monitoring MIB, V0.84 July 21, 1997 2546 '1', 1025-2048 SHALL be '2', etc. When the job completes, 2547 the values of the jmJobKOctetsRequested object and the 2548 jobKOctetsTransferred attribute SHALL be equal. 2550 NOTE - The jobKOctetsTransferred can be used with the 2551 jmJobKOctetsRequested object in order to produce a relative 2552 indication of the progress of the job for agents that do not 2553 implement the jmJobKOctetsProcessed object. 2555 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2556 + Impression attributes 2557 + 2558 + For a print job, an impression is the marking of the 2559 + entire side of a sheet. Two-sided processing involves two 2560 + impressions per sheet. Two-up is the placement of two 2561 + logical pages on one side of a sheet and so is still a 2562 + single impression. See also jmJobImpressionsRequested and 2563 + jmJobImpressionsCompleted objects in the jmJobTable. 2564 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2566 impressionsSpooled(110), Integer32(-2..2147483647) 2567 INTEGER: The number of impressions spooled to the server or 2568 device for the job so far. 2570 impressionsSentToDevice(111), Integer32(-2..2147483647) 2571 INTEGER: The number of impressions sent to the device for 2572 the job so far. 2574 impressionsInterpreted(112), Integer32(-2..2147483647) 2575 INTEGER: The number of impressions interpreted for the job 2576 so far. 2578 impressionsCompletedCurrentCopy(113), Integer32(-2..2147483647) 2579 INTEGER: The number of impressions completed by the device 2580 for the current copy of the current document so far. For 2581 printing, the impressions completed includes interpreting, 2582 marking, and stacking the output. For other types of job 2583 services, the number of impressions completed includes the 2584 number of impressions processed. 2586 This value SHALL be reset to 0 for each document in the job 2587 and for each document copy. 2589 fullColorImpressionsCompleted(114), Integer32(-2..2147483647) 2590 INTEGER: The number of full color impressions completed by 2591 the device for this job so far. For printing, the 2592 impressions completed includes interpreting, marking, and 2594 Job Monitoring MIB, V0.84 July 21, 1997 2596 stacking the output. For other types of job services, the 2597 number of impressions completed includes the number of 2598 impressions processed. Full color impressions are typically 2599 defined as those requiring 3 or more colorants, but this MAY 2600 vary by implementation. 2602 highlightColorImpressionsCompleted(115), Integer32(-2.. 2603 2147483647) 2604 INTEGER: The number of highlight color impressions 2605 completed by the device for this job so far. For printing, 2606 the impressions completed includes interpreting, marking, 2607 and stacking the output. For other types of job services, 2608 the number of impressions completed includes the number of 2609 impressions processed. Highlight color impressions are 2610 typically defined as those requiring black plus one other 2611 colorant, but this MAY vary by implementation. 2613 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2614 + Page attributes 2615 + 2616 + A page is a logical page. Number up can impose more than 2617 + one page on a single side of a sheet. Two-up is the 2618 + placement of two logical pages on one side of a sheet so 2619 + that each side counts as two pages. 2620 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2622 pagesRequested(130), Integer32(-2..2147483647) 2623 INTEGER: The number of logical pages requested by the job 2624 to be processed. 2626 pagesCompleted(131), Integer32(-2..2147483647) 2627 INTEGER: The number of logical pages completed for this job 2628 so far. 2630 pagesCompletedCurrentCopy(132), Integer32(-2..2147483647) 2631 INTEGER: The number of logical pages completed for the 2632 current copy of the document so far. This value SHALL be 2633 reset to 0 for each document in the job and for each 2634 document copy. 2636 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2637 + Sheet attributes 2638 + 2639 + The sheet is a single piece of a medium, whether printing 2640 + on one or both sides. 2641 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2643 Job Monitoring MIB, V0.84 July 21, 1997 2645 sheetsRequested(150), Integer32(-2..2147483647) 2646 INTEGER: The number of medium sheets requested to be 2647 processed for this job. 2649 sheetsCompleted(151), Integer32(-2..2147483647) 2650 INTEGER: The number of medium sheets that have completed 2651 marking and stacking for the entire job so far whether those 2652 sheets have been processed on one side or on both. 2654 sheetsCompletedCurrentCopy(152), Integer32(-2..2147483647) 2655 INTEGER: The number of medium sheets that have completed 2656 marking and stacking for the current copy of a document in 2657 the job so far whether those sheets have been processed on 2658 one side or on both. 2660 The value of this attribute SHALL be reset to 0 as each 2661 document in the job starts being processed and for each 2662 document copy as it starts being processed. 2664 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2665 + Resources attributes (requested and consumed) 2666 + 2667 + Pairs of these attributes can be used by monitoring 2668 + applications to show an indication of relative usage to 2669 + users. 2670 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2672 mediumRequested(170), JmMediumTypeTC 2673 AND/OR 2674 OCTET STRING(SIZE(0..63)) 2675 INTEGER: MULTI-ROW: The type 2676 AND/OR 2677 OCTETS: the name of the medium that is required by the job. 2679 mediumConsumed(171), Integer32(-2..2147483647) 2680 AND 2681 OCTET STRING(SIZE(0..63)) 2682 INTEGER: The number of sheets 2683 AND 2684 OCTETS: MULTI-ROW: the name of the medium that have been 2685 consumed so far whether those sheets have been processed on 2686 one side or on both. 2688 This attribute SHALL have both Integer32 and OCTET STRING 2689 values. 2691 Job Monitoring MIB, V0.84 July 21, 1997 2693 colorantRequested(172), Integer32(-2..2147483647) 2694 AND/OR 2695 OCTET STRING(SIZE(0..63)) 2696 INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in 2697 the Printer MIB[print-mib] 2698 AND/OR 2699 OCTETS: the name of the colorant requested. 2701 colorantConsumed(173), Integer32(-2..2147483647) 2702 AND/OR 2703 OCTET STRING(SIZE(0..63)) 2704 INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in 2705 the Printer MIB[print-mib] 2706 AND/OR 2707 OCTETS: the name of the colorant consumed. 2709 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2710 + Time attributes (set by server or device) 2711 + 2712 + This section of attributes are ones that are set by the 2713 + server or device that accepts jobs. Two forms of time are 2714 + provided. Each form is represented in a separate attribute. 2715 + See section 3.1.2 and section 3.1.3 for the 2716 + conformance requirements for time attribute for agents and 2717 + monitoring applications, respectively. The two forms are: 2718 + 2719 + 'DateAndTime' is an 8 or 11 octet binary encoded year, 2720 + month, day, hour, minute, second, deci-second with 2721 + optional offset from UTC. See SNMPv2-TC [SMIv2-TC]. 2722 + 2723 + NOTE: 'DateAndTime' is not printable characters; it is 2724 + binary. 2725 + 2726 + 'JmTimeStampTC' is the time of day measured in the number of 2727 + seconds since the system was booted. 2728 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2730 jobSubmissionToServerTime(190), JmTimeStampTC 2731 AND/OR 2732 DateAndTime 2733 INTEGER: Configuration 3 only: The time 2734 AND/OR 2735 OCTETS: the date and time that the job was submitted to the 2736 server (as distinguished from the device which uses 2737 jobSubmissionTime). 2739 Job Monitoring MIB, V0.84 July 21, 1997 2741 jobSubmissionTime(191), JmTimeStampTC 2742 AND/OR 2743 DateAndTime 2744 INTEGER: Configurations 1, 2, and 3: The time 2745 AND/OR 2746 OCTETS: the date and time that the job was submitted to the 2747 server or device to which the agent is providing access. 2749 jobStartedBeingHeldTime(192), JmTimeStampTC 2750 AND/OR 2751 DateAndTime 2752 INTEGER: The time 2753 AND/OR 2754 OCTETS: the date and time that the job last entered the 2755 pendingHeld state. If the job has never entered the 2756 pendingHeld state, then the value SHALL be '0' or the 2757 attribute SHALL not be present in the table. 2759 jobStartedProcessingTime(193), JmTimeStampTC 2760 AND/OR 2761 DateAndTime 2762 INTEGER: The time 2763 AND/OR 2764 OCTETS: the date and time that the job started processing. 2766 jobCompletedTime(194), JmTimeStampTC 2767 AND/OR 2768 DateAndTime 2769 INTEGER: The time 2770 AND/OR 2771 OCTETS: the date and time that the job entered the 2772 completed, canceled, or aborted state. 2774 jobProcessingCPUTime(195) Integer32(-2..2147483647) 2775 UNITS 'seconds' 2776 INTEGER: The amount of CPU time in seconds that the job has 2777 been in the processing state. If the job enters the 2778 processingStopped state, that elapsed time SHALL not be 2779 included. In other words, the jobProcessingCPUTime value 2780 SHOULD be relatively repeatable when the same job is 2781 processed again on the same device." 2783 REFERENCE 2784 "See Section 3.2 entitled 'The Attribute Mechanism' for a 2785 description of this textual-convention and its use in the 2786 jmAttributeTable. 2788 Job Monitoring MIB, V0.84 July 21, 1997 2790 This is a type 2 enumeration. See Section 3.6.1.2." 2791 SYNTAX INTEGER { 2792 other(1), 2793 unknown(2), 2794 jobStateReasons2(3), 2795 jobStateReasons3(4), 2796 jobStateReasons4(5), 2797 processingMessage(6), 2799 jobAccountName(21), 2800 serverAssignedJobName(22), 2801 jobName(23), 2802 jobServiceTypes(24), 2803 jobSourceChannelIndex(25), 2804 jobSourcePlatformType(26), 2805 submittingServerName(27), 2806 submittingApplicationName(28), 2807 jobOriginatingHost(29), 2808 deviceNameRequested(30), 2809 queueNameRequested(31), 2810 physicalDevice(32), 2811 numberOfDocuments(33), 2812 fileName(34), 2813 documentName(35), 2814 jobComment(36), 2815 documentFormatIndex(37), 2816 documentFormat(38), 2818 jobPriority(50), 2819 jobProcessAfterDateAndTime(51), 2820 jobHold(52), 2821 jobHoldUntil(53), 2822 outputBin(54), 2823 sides(55), 2824 finishing(56), 2826 printQualityRequested(70), 2827 printQualityUsed(71), 2828 printerResolutionRequested(72), 2829 printerResolutionUsed(73), 2830 tonerEcomonyRequested(74), 2831 tonerEcomonyUsed(75), 2832 tonerDensityRequested(76), 2833 tonerDensityUsed(77), 2835 jobCopiesRequested(90), 2836 jobCopiesCompleted(91), 2838 Job Monitoring MIB, V0.84 July 21, 1997 2840 documentCopiesRequested(92), 2841 documentCopiesCompleted(93), 2842 jobKOctetsTransferred(94), 2844 impressionsSpooled(110), 2845 impressionsSentToDevice(111), 2846 impressionsInterpreted(112), 2847 impressionsCompletedCurrentCopy(113), 2848 fullColorImpressionsCompleted(114), 2849 highlightColorImpressionsCompleted(115), 2851 pagesRequested(130), 2852 pagesCompleted(131), 2853 pagesCompletedCurrentCopy(132), 2855 sheetsRequested(150), 2856 sheetsCompleted(151), 2857 sheetsCompletedCurrentCopy(152), 2859 mediumRequested(170), 2860 mediumConsumed(171), 2861 colorantRequested(172), 2862 colorantConsumed(173), 2864 jobSubmissionToServerTime(190), 2865 jobSubmissionTime(191), 2866 jobStartedBeingHeldTime(192), 2867 jobStartedProcessingTime(193), 2868 jobCompletedTime(194), 2869 jobProcessingCPUTime(195) 2870 } 2872 JmJobServiceTypesTC ::= TEXTUAL-CONVENTION 2873 STATUS current 2874 DESCRIPTION 2875 "Specifies the type(s) of service to which the job has been 2876 submitted (print, fax, scan, etc.). The service type is 2877 represented as an enum that is bit encoded with each job service 2878 type so that more general and arbitrary services can be created, 2879 such as services with more than one destination type, or ones 2880 with only a source or only a destination. For example, a job 2881 service might scan, faxOut, and print a single job. In this 2882 case, three bits would be set in the jobServiceTypes attribute, 2884 Job Monitoring MIB, V0.84 July 21, 1997 2886 corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, 2887 respectively, yielding: 0x2C. 2889 Whether this attribute is set from a job attribute supplied by 2890 the job submission client or is set by the recipient job 2891 submission server or device depends on the job submission 2892 protocol. With either implementation, the agent SHALL return a 2893 non-zero value for this attribute indicating the type of the 2894 job. 2896 One of the purposes of this attribute is to permit a requester 2897 to filter out jobs that are not of interest. For example, a 2898 printer operator MAY only be interested in jobs that include 2899 printing. That is why the attribute is in the job 2900 identification category. 2902 The following service component types are defined (in 2903 hexadecimal) and are assigned a separate bit value for use with 2904 the jobServiceTypes attribute: 2906 other 0x1 2907 The job contains some instructions that are not one of the 2908 identified types. 2910 unknown 0x2 2911 The job contains some instructions whose type is unknown to 2912 the agent. 2914 print 0x4 2915 The job contains some instructions that specify printing 2917 scan 0x8 2918 The job contains some instructions that specify scanning 2920 faxIn 0x10 2921 The job contains some instructions that specify receive fax 2923 faxOut 0x20 2924 The job contains some instructions that specify sending fax 2926 getFile 0x40 2927 The job contains some instructions that specify accessing 2928 files or documents 2930 putFile 0x80 2931 The job contains some instructions that specify storing 2932 files or documents 2934 Job Monitoring MIB, V0.84 July 21, 1997 2936 mailList 0x100 2937 The job contains some instructions that specify distribution 2938 of documents using an electronic mail system." 2939 REFERENCE 2940 "These bit definitions are the equivalent of a type 2 enum 2941 except that combinations of them MAY be used together. See 2942 section 3.6.1.2." 2943 SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit 2945 JmJobStateReasons1TC ::= TEXTUAL-CONVENTION 2946 STATUS current 2947 DESCRIPTION 2948 "The JmJobStateReasonsNTC (N=1..4) textual-conventions are used 2949 with the jmJobStateReasons1 object and jobStateReasonsN 2950 (N=2..4), respectively, to provide additional information 2951 regarding the current jmJobState object value. These values MAY 2952 be used with any job state or states for which the reason makes 2953 sense. 2955 NOTE - While values cannot be added to the jmJobState object 2956 without impacting deployed clients that take actions upon 2957 receiving jmJobState values, it is the intent that additional 2958 JmJobStateReasonsNTC enums can be defined and registered without 2959 impacting such deployed clients. In other words, the 2960 jmJobStateReasons1 object and jobStateReasonsN attributes are 2961 intended to be extensible. 2963 NOTE - The Job Monitoring MIB contains a superset of the IPP 2964 values[ipp-model] for the IPP 'job-state-reasons' attribute, 2965 since the Job Monitoring MIB is intended to cover other job 2966 submission protocols as well. Also some of the names of the 2967 reasons have been changed from 'printer' to 'device', since the 2968 Job Monitoring MIB is intended to cover additional types of 2969 devices, including input devices, such as scanners. 2971 The following standard values are defined (in hexadecimal) as 2972 powers of two, since multiple values MAY be used at the same 2973 time. For ease of understanding, the JmJobStateReasons1TC 2974 reasons are presented in the order in which the reasons are 2975 likely to occur (if implemented), starting with the 2977 Job Monitoring MIB, V0.84 July 21, 1997 2979 'jobIncoming' value and ending with 'jobCompletedWithErrors' 2980 reasons. 2982 other 0x1 2983 The job state reason is not one of the standardized or 2984 registered reasons. 2986 unknown 0x2 2987 The job state reason is not known to the agent or is 2988 indeterminent. 2990 jobIncoming 0x4 2991 The job has been accepted by the server or device, but the 2992 server or device is expecting (1) additional operations from 2993 the client to finish creating the job and/or (2) is 2994 accessing/accepting document data. 2996 jobOutgoing 0x8 2997 Configuration 2 only: The server is transmitting the job to 2998 the device. 3000 jobHoldSpecified 0x10 3001 The value of the job's jobHold(52) attribute is TRUE. The 3002 job SHALL NOT be a candidate for processing until this 3003 reason is removed and there are no other reasons to hold the 3004 job. 3006 jobHoldUntilSpecified 0x20 3007 The value of the job's jobHoldUntil(53) attribute specifies 3008 a time period that is still in the future. The job SHALL 3009 NOT be a candidate for processing until this reason is 3010 removed and there are no other reasons to hold the job. 3012 jobProcessAfterSpecified 0x40 3013 The value of the job's jobProcessAfterDateAndTime(51) 3014 attribute specifies a time that is still in the future. The 3015 job SHALL NOT be a candidate for processing until this 3016 reason is removed and there are no other reasons to hold the 3017 job. 3019 resourcesAreNotReady 0x80 3020 At least one of the resources needed by the job, such as 3021 media, fonts, resource objects, etc., is not ready on any of 3022 the physical devices for which the job is a candidate. This 3023 condition MAY be detected when the job is accepted, or 3024 subsequently while the job is pending or processing, 3025 depending on implementation. 3027 Job Monitoring MIB, V0.84 July 21, 1997 3029 deviceStoppedPartly 0x100 3030 One or more, but not all, of the devices to which the job is 3031 assigned are stopped. If all of the devices are stopped (or 3032 the only device is stopped), the deviceStopped reason SHALL 3033 be used. 3035 deviceStopped 0x200 3036 The device(s) to which the job is assigned is (are all) 3037 stopped. 3039 jobPrinting 0x400 3040 The output device is marking media. This attribute is useful 3041 for servers and output devices which spend a great deal of 3042 time processing when no marking is happening and then want 3043 to show that marking is now happening or when the job is in 3044 the canceled or aborted state, but the marking has not yet 3045 stopped so that impression or sheet counts are still 3046 increasing for the job. 3048 jobCanceledByUser 0x800 3049 The job was canceled by the user, i.e., by an unknown user 3050 or by a user whose name is the same as the value of the 3051 job's jmJobOwner object. 3053 jobCanceledByOperator 0x1000 3054 The job was canceled by the operator, i.e., by a user whose 3055 name is different than the value of the job's jmJobOwner 3056 object. 3058 abortedBySystem 0x2000 3059 The job was aborted by the system. 3061 NOTE - When the system puts a job into the 'aborted' job 3062 state, this reason is not needed. This reason is needed 3063 only when the system aborts a job, but, instead of placing 3064 the job in the aborted job state, places the job in the 3065 pendingHeld state, so that a user or operator can manually 3066 try the job again. 3068 jobCompletedSuccessfully 0x4000 3069 The job completed successfully. 3071 jobCompletedWithWarnings 0x8000 3072 The job completed with warnings. 3074 jobCompletedWithErrors 0x10000 3075 The job completed with errors (and possibly warnings too). 3077 Job Monitoring MIB, V0.84 July 21, 1997 3079 The following additional job state reasons have been added 3080 to represent job states that are in ISO DPA[iso-dpa] and 3081 other job submission protocols: 3083 jobPaused 0x20000 3084 The job has been indefinitely suspended by a client issuing 3085 an operation to suspend the job so that other jobs may 3086 proceed using the same devices. The client MAY issue an 3087 operation to resume the paused job at any time, in which 3088 case the agent SHALL remove the jobPaused values from the 3089 job's jmJobStateReasons1 object and the job is eventually 3090 resumed at or near the point where the job was paused. 3092 jobInterrupted 0x40000 3093 The job has been interrupted while processing by a client 3094 issuing an operation that specifies another job to be run 3095 instead of the current job. The server or device will 3096 automatically resume the interrupted job when the 3097 interrupting job completes. 3099 jobRetained 0x80000 3100 The job is being retained by the server or device with all 3101 of the job's document data (and submitted resources, such as 3102 fonts, logos, and forms, if any). Thus a client could issue 3103 an operation to the server or device to either (1) re-do the 3104 job (or a copy of the job) on the same server or device or 3105 (2) resubmit the job to another server or device. When a 3106 client could no longer re-do/resubmit the job, such as after 3107 the document data has been discarded, the agent SHALL remove 3108 the jobRetained value from the jmJobStateReasons1 object." 3109 REFERENCE 3110 "These bit definitions are the equivalent of a type 2 enum 3111 except that combinations of bits may be used together. See 3112 section 3.6.1.2. The remaining bits are reserved for future 3113 standardization and/or registration." 3115 SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit 3117 JmJobStateReasons2TC ::= TEXTUAL-CONVENTION 3118 STATUS current 3119 DESCRIPTION 3120 "This textual-convention is used with the jobStateReasons2 3121 attribute to provides additional information regarding the 3122 jmJobState object. See the description under 3124 Job Monitoring MIB, V0.84 July 21, 1997 3126 JmJobStateReasons1TC for additional information that applies to 3127 all reasons. 3129 The following standard values are defined (in hexadecimal) as 3130 powers of two, since multiple values may be used at the same 3131 time: 3133 cascaded 0x1 3134 An outbound gateway has transmitted all of the job's job and 3135 document attributes and data to another spooling system. 3137 deletedByAdministrator 0x2 3138 The administrator has deleted the job. 3140 discardTimeArrived 0x4 3141 The job has been deleted due to the fact that the time 3142 specified by the job's job-discard-time attribute has 3143 arrived. 3145 postProcessingFailed 0x8 3146 The post-processing agent failed while trying to log 3147 accounting attributes for the job; therefore the job has 3148 been placed into the completed state with the jobRetained 3149 jmJobStateReasons1 object value for a system-defined period 3150 of time, so the administrator can examine it, resubmit it, 3151 etc. 3153 submissionInterrupted 0x10 3154 Indicates that the job was not completely submitted for some 3155 unforeseen reason, such as: (1) the server has crashed 3156 before the job was closed by the client, (2) the server or 3157 the document transfer method has crashed in some non- 3158 recoverable way before the document data was entirely 3159 transferred to the server, (3) the client crashed or failed 3160 to close the job before the time-out period. 3162 maxJobFaultCountExceeded 0x20 3163 The job has faulted several times and has exceeded the 3164 administratively defined fault count limit. 3166 devicesNeedAttentionTimeOut 0x40 3167 One or more document transforms that the job is using needs 3168 human intervention in order for the job to make progress, 3169 but the human intervention did not occur within the site- 3170 settable time-out value. 3172 needsKeyOperatorTimeOut 0x80 3173 One or more devices or document transforms that the job is 3175 Job Monitoring MIB, V0.84 July 21, 1997 3177 using need a specially trained operator (who may need a key 3178 to unlock the device and gain access) in order for the job 3179 to make progress, but the key operator intervention did not 3180 occur within the site-settable time-out value. 3182 jobStartWaitTimeOut 0x100 3183 The server/device has stopped the job at the beginning of 3184 processing to await human action, such as installing a 3185 special cartridge or special non-standard media, but the job 3186 was not resumed within the site-settable time-out value and 3187 the server/device has transitioned the job to the 3188 pendingHeld state. 3190 jobEndWaitTimeOut 0x200 3191 The server/device has stopped the job at the end of 3192 processing to await human action, such as removing a special 3193 cartridge or restoring standard media, but the job was not 3194 resumed within the site-settable time-out value and the 3195 server/device has transitioned the job to the completed 3196 state. 3198 jobPasswordWaitTimeOut 0x400 3199 The server/device has stopped the job at the beginning of 3200 processing to await input of the job's password, but the 3201 password was not received within the site-settable time-out 3202 value. 3204 deviceTimedOut 0x800 3205 A device that the job was using has not responded in a 3206 period specified by the device's site-settable attribute. 3208 connectingToDeviceTimeOut 0x1000 3209 The server is attempting to connect to one or more devices 3210 which may be dial-up, polled, or queued, and so may be busy 3211 with traffic from other systems, but server was unable to 3212 connect to the device within the site-settable time-out 3213 value. 3215 transferring 0x2000 3216 The job is being transferred to a down stream server or 3217 device. 3219 queuedInDevice 0x4000 3220 The job has been queued in a down stream server or device. 3222 jobCleanup 0x8000 3223 The server/device is performing cleanup activity as part of 3224 ending normal processing. 3226 Job Monitoring MIB, V0.84 July 21, 1997 3228 processingToStopPoint 0x10000 3229 The requester has issued an operation to interrupt the job 3230 and the server/device is processing up until the specified 3231 stop point occurs. 3233 jobPasswordWait 0x20000 3234 The server/device has selected the job to be next to 3235 process, but instead of assigning resources and starting the 3236 job processing, the server/device has transitioned the job 3237 to the pendingHeld state to await entry of a password (and 3238 dispatched another job, if there is one). 3240 validating 0x40000 3241 The server/device is validating the job after accepting the 3242 job. 3244 queueHeld 0x80000 3245 The operator has held the entire job set or queue. 3247 jobProofWait 0x100000 3248 The job has produced a single proof copy and is in the 3249 pendingHeld state waiting for the requester to issue an 3250 operation to release the job to print normally, obeying any 3251 job and document copy attributes that were originally 3252 submitted. 3254 heldForDiagnostics 0x200000 3255 The system is running intrusive diagnostics, so that all 3256 jobs are being held. 3258 serviceOffLine 0x400000 3259 The service/document transform is off-line and accepting no 3260 jobs. All pending jobs are put into the pendingHeld state. 3261 This could be true if its input is impaired or broken. 3263 noSpaceOnServer 0x800000 3264 There is no room on the server to store all of the job. 3266 pinRequired 0x1000000 3267 The System Administrator settable device policy is (1) to 3268 require PINs, and (2) to hold jobs that do not have a pin 3269 supplied as an input parameter when the job was created. 3271 exceededAccountLimit 0x2000000 3272 The account for which this job is drawn has exceeded its 3273 limit. This condition SHOULD be detected before the job is 3274 scheduled so that the user does not wait until his/her job 3276 Job Monitoring MIB, V0.84 July 21, 1997 3278 is scheduled only to find that the account is overdrawn. 3279 This condition MAY also occur while the job is processing 3280 either as processing begins or part way through processing. 3282 heldForRetry 0x4000000 3283 The job encountered some errors that the server/device could 3284 not recover from with its normal retry procedures, but the 3285 error might not be encountered if the job is processed again 3286 in the future. Example cases are phone number busy or 3287 remote file system in-accessible. For such a situation, the 3288 server/device SHALL transition the job from the processing 3289 to the pendingHeld, rather than to the aborted state. 3291 The following values are from the X/Open PSIS draft standard: 3293 canceledByShutdown 0x8000000 3294 The job was canceled because the server or device was 3295 shutdown before completing the job. 3297 deviceUnavailable 0x10000000 3298 This job was aborted by the system because the device is 3299 currently unable to accept jobs. 3301 wrongDevice 0x20000000 3302 This job was aborted by the system because the device is 3303 unable to handle this particular job; the spooler SHOULD try 3304 another device or the user should submit the job to another 3305 device. 3307 badJob 0x40000000 3308 This job was aborted by the system because this job has a 3309 major problem, such as an ill-formed PDL; the spooler SHOULD 3310 not even try another device. " 3311 REFERENCE 3312 "These bit definitions are the equivalent of a type 2 enum 3313 except that combinations of them may be used together. See 3314 section 3.6.1.2. See the description under JmJobStateReasons1TC 3315 and the jobStateReasons2 attribute." 3317 SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit 3319 JmJobStateReasons3TC ::= TEXTUAL-CONVENTION 3320 STATUS current 3322 Job Monitoring MIB, V0.84 July 21, 1997 3324 DESCRIPTION 3325 "This textual-convention is used with the jobStateReasons3 3326 attribute to provides additional information regarding the 3327 jmJobState object. See the description under 3328 JmJobStateReasons1TC for additional information that applies to 3329 all reasons. 3331 The following standard values are defined (in hexadecimal) as 3332 powers of two, since multiple values may be used at the same 3333 time: 3335 jobInterruptedByDeviceFailure 0x1 3336 A device or the print system software that the job was using 3337 has failed while the job was processing. The server or 3338 device is keeping the job in the pendingHeld state until an 3339 operator can determine what to do with the job." 3340 REFERENCE 3341 "These bit definitions are the equivalent of a type 2 enum 3342 except that combinations of them may be used together. See 3343 section 3.6.1.2. The remaining bits are reserved for future 3344 standardization and/or registration. See the description under 3345 JmJobStateReasons1TC and the jobStateReasons3 attribute." 3346 SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit 3348 JmJobStateReasons4TC ::= TEXTUAL-CONVENTION 3349 STATUS current 3350 DESCRIPTION 3351 "This textual-convention is used in the jobStateReasons4 3352 attribute to provides additional information regarding the 3353 jmJobState object. See the description under 3354 JmJobStateReasons1TC for additional information that applies to 3355 all reasons. 3357 The following standard values are defined (in hexadecimal) as 3358 powers of two, since multiple values may be used at the same 3359 time: 3361 none yet defined. These bits are reserved for future 3362 standardization and/or registration." 3363 REFERENCE 3364 "These bit definitions are the equivalent of a type 2 enum 3365 except that combinations of them may be used together. See 3366 section 3.6.1.2. See the description under JmJobStateReasons1TC 3367 and the jobStateReasons4 attribute." 3369 Job Monitoring MIB, V0.84 July 21, 1997 3371 SYNTAX INTEGER(0..2147483647) -- 31 bits, all but sign bit 3373 Job Monitoring MIB, V0.84 July 21, 1997 3375 jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 } 3377 - -- The General Group (MANDATORY) 3379 - -- The jmGeneralGroup consists entirely of the jmGeneralTable. 3381 jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 } 3383 jmGeneralTable OBJECT-TYPE 3384 SYNTAX SEQUENCE OF JmGeneralEntry 3385 MAX-ACCESS not-accessible 3386 STATUS current 3387 DESCRIPTION 3388 "The jmGeneralTable consists of information of a general nature 3389 that are per-job-set, but are not per-job. See Section 2 3390 entitled 'Terminology and Job Model' for the definition of a job 3391 set." 3392 REFERENCE 3393 "The MANDATORY-GROUP macro specifies that this group is 3394 MANDATORY." 3395 ::= { jmGeneral 1 } 3397 jmGeneralEntry OBJECT-TYPE 3398 SYNTAX JmGeneralEntry 3399 MAX-ACCESS not-accessible 3400 STATUS current 3401 DESCRIPTION 3402 "Information about a job set (queue). 3404 An entry SHALL exist in this table for each job set." 3405 INDEX { jmGeneralJobSetIndex } 3406 ::= { jmGeneralTable 1 } 3408 JmGeneralEntry ::= SEQUENCE { 3409 jmGeneralJobSetIndex Integer32(1..32767), 3410 jmGeneralNumberOfActiveJobs Integer32(0..2147483647), 3411 jmGeneralOldestActiveJobIndex Integer32(0..2147483647), 3412 jmGeneralNewestActiveJobIndex Integer32(0..2147483647), 3413 jmGeneralJobPersistence Integer32(15..2147483647), 3414 jmGeneralAttributePersistence Integer32(15..2147483647), 3415 jmGeneralJobSetName OCTET STRING(SIZE(0..63)) 3416 } 3418 jmGeneralJobSetIndex OBJECT-TYPE 3419 SYNTAX Integer32(1..32767) 3420 MAX-ACCESS not-accessible 3421 STATUS current 3423 Job Monitoring MIB, V0.84 July 21, 1997 3425 DESCRIPTION 3426 "A unique value for each job set in this MIB. The jmJobTable 3427 and jmAttributeTable tables have this same index as their 3428 primary index. 3430 The value(s) of the jmGeneralJobSetIndex SHALL be persistent 3431 across power cycles, so that clients that have retained 3432 jmGeneralJobSetIndex values will access the same job sets upon 3433 subsequent power-up. 3435 An implementation that has only one job set, such as a printer 3436 with a single queue, SHALL hard code this object with the value 3437 1." 3438 REFERENCE 3439 "See Section 2 entitled 'Terminology and Job Model' for the 3440 definition of a job set. 3441 Corresponds to the first index in jmJobTable and 3442 jmAttributeTable." 3443 ::= { jmGeneralEntry 1 } 3445 jmGeneralNumberOfActiveJobs OBJECT-TYPE 3446 SYNTAX Integer32(0..2147483647) 3447 MAX-ACCESS read-only 3448 STATUS current 3449 DESCRIPTION 3450 "The current number of 'active' jobs in the jmJobIDTable, 3451 jmJobTable, and jmAttributeTable, i.e., the total number of jobs 3452 that are in the pending, processing, or processingStopped 3453 states. See the JmJobStateTC textual-convention for the exact 3454 specification of the semantics of the job states." 3455 ::= { jmGeneralEntry 2 } 3457 jmGeneralOldestActiveJobIndex OBJECT-TYPE 3458 SYNTAX Integer32 (0..2147483647) 3459 MAX-ACCESS read-only 3460 STATUS current 3461 DESCRIPTION 3462 "The jmJobIndex of the oldest job that is still in one of the 3463 'active' states (pending, processing, or processingStopped). In 3464 other words, the index of the 'active' job that has been in the 3465 job tables the longest. 3467 If there are no active jobs, the agent SHALL set the value of 3468 this object to 0." 3469 REFERENCE 3470 "See Section 3.2 entitled 'The Job Tables and the Oldest Active 3471 and Newest Active Indexes' for a description of the usage of 3472 this object." 3474 Job Monitoring MIB, V0.84 July 21, 1997 3476 ::= { jmGeneralEntry 3 } 3478 jmGeneralNewestActiveJobIndex OBJECT-TYPE 3479 SYNTAX Integer32 (0..2147483647) 3480 MAX-ACCESS read-only 3481 STATUS current 3482 DESCRIPTION 3483 "The jmJobIndex of the newest job that is in one of the 'active' 3484 states (pending, processing, or processingStopped). In other 3485 words, the index of the 'active' job that has been most recently 3486 added to the job tables. 3488 When all jobs become 'inactive', i.e., enter the pendingHeld, 3489 completed, canceled, or aborted states, the agent SHALL set the 3490 value of this object to 0." 3491 REFERENCE 3492 "See Section 3.2 entitled 'The Job Tables and the Oldest Active 3493 and Newest Active Indexes' for a description of the usage of 3494 this object." 3495 ::= { jmGeneralEntry 4 } 3497 jmGeneralJobPersistence OBJECT-TYPE 3498 SYNTAX Integer32(15..2147483647) 3499 UNITS "seconds" 3500 MAX-ACCESS read-only 3501 STATUS current 3502 DESCRIPTION 3503 "The minimum time in seconds for this instance of the Job Set 3504 that an entry SHALL remain in the jmJobIDTable and jmJobTable 3505 after processing has completed, i.e., the minimum time in 3506 seconds starting when the job enters the completed, canceled, or 3507 aborted state. 3509 Depending on implementation, the value of this object MAY be 3510 either: (1) set by the system administrator by means outside 3511 this specification or (2) fixed by the implementation. 3513 This value SHALL be equal to or greater than the value of 3514 jmGeneralAttributePersistence. This value SHOULD be at least 60 3515 which gives a monitoring application one minute in which to poll 3516 for job data." 3517 DEFVAL { 60 } -- one minute 3518 ::= { jmGeneralEntry 5 } 3520 jmGeneralAttributePersistence OBJECT-TYPE 3521 SYNTAX Integer32(15..2147483647) 3522 UNITS "seconds" 3523 MAX-ACCESS read-only 3525 Job Monitoring MIB, V0.84 July 21, 1997 3527 STATUS current 3528 DESCRIPTION 3529 "The minimum time in seconds for this instance of the Job Set 3530 that an entry SHALL remain in the jmAttributeTable after 3531 processing has completed , i.e., the time in seconds starting 3532 when the job enters the completed, canceled, or aborted state. 3534 Depending on implementation, the value of this object MAY be 3535 either (1) set by the system administrator by means outside this 3536 specification or MAY be (2) fixed by the implementation. 3538 This value SHOULD be at least 60 which gives a monitoring 3539 application one minute in which to poll for job data." 3540 DEFVAL { 60 } -- one minute 3541 ::= { jmGeneralEntry 6 } 3543 jmGeneralJobSetName OBJECT-TYPE 3544 SYNTAX OCTET STRING(SIZE(0..63)) 3545 MAX-ACCESS read-only 3546 STATUS current 3547 DESCRIPTION 3548 "The human readable name of this job set assigned by the system 3549 administrator (by means outside of this MIB). Typically, this 3550 name SHOULD be the name of the job queue. If a server or device 3551 has only a single job set, this object can be the 3552 administratively assigned name of the server or device itself. 3553 This name does not need to be unique, though each job set in a 3554 single Job Monitoring MIB SHOULD have distinct names. 3556 NOTE - The purpose of this object is to help the user of the job 3557 monitoring application distinguish between several job sets in 3558 implementations that support more than one job set." 3559 REFERENCE 3560 "See the OBJECT compliance macro for the minimum maximum length 3561 required for conformance." 3562 ::= { jmGeneralEntry 7 } 3564 - -- The Job ID Group (MANDATORY) 3566 - -- The jmJobIDGroup consists entirely of the jmJobIDTable. 3568 jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 } 3570 jmJobIDTable OBJECT-TYPE 3572 Job Monitoring MIB, V0.84 July 21, 1997 3574 SYNTAX SEQUENCE OF JmJobIDEntry 3575 MAX-ACCESS not-accessible 3576 STATUS current 3577 DESCRIPTION 3578 "The jmJobIDTable provides a correspondence map (1) between the 3579 job submission ID that a client uses to refer to a job and (2) 3580 the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring 3581 MIB agent assigned to the job and that are used to access the 3582 job in all of the other tables in the MIB. If a monitoring 3583 application already knows the jmGeneralJobSetIndex and the 3584 jmJobIndex of the job it is querying, that application NEED NOT 3585 use the jmJobIDTable." 3586 REFERENCE 3587 "The MANDATORY-GROUP macro specifies that this group is 3588 MANDATORY." 3589 ::= { jmJobID 1 } 3591 jmJobIDEntry OBJECT-TYPE 3592 SYNTAX JmJobIDEntry 3593 MAX-ACCESS not-accessible 3594 STATUS current 3595 DESCRIPTION 3596 "The map from (1) the jmJobSubmissionID to (2) the 3597 jmGeneralJobSetIndex and jmJobIndex. 3599 An entry SHALL exist in this table for each job currently known 3600 to the agent for all job sets and job states. Each job SHALL 3601 appear in one and only one job set." 3602 INDEX { jmJobSubmissionID } 3603 ::= { jmJobIDTable 1 } 3605 JmJobIDEntry ::= SEQUENCE { 3606 jmJobSubmissionID OCTET STRING(SIZE(48)), 3607 jmJobIDJobSetIndex Integer32(1..32767), 3608 jmJobIDJobIndex Integer32(1..2147483647) 3609 } 3611 jmJobSubmissionID OBJECT-TYPE 3612 SYNTAX OCTET STRING(SIZE(48)) 3613 MAX-ACCESS not-accessible 3614 STATUS current 3615 DESCRIPTION 3616 "A quasi-unique 48-octet fixed-length string ID which identifies 3617 the job within a particular client-server environment. There 3618 are multiple formats for the jmJobSubmissionID. See the 3619 JmJobSubmissionIDTypeTC textual convention. Each format SHALL 3620 be registered using the procedures of a type 2 enum. See 3622 Job Monitoring MIB, V0.84 July 21, 1997 3624 section 3.6.3 entitled: 'IANA Registration of Job Submission Id 3625 Formats'. 3627 If the requester (client or server) does not supply a job 3628 submission ID in the job submission protocol, then the recipient 3629 (server or device) SHALL assign a job submission ID using any of 3630 the standard formats and adding the final 8 octets to 3631 distinguish the ID from others submitted from the same 3632 requester. 3634 The monitoring application, whether in the client or running 3635 separately, MAY use the job submission ID to help identify which 3636 jmJobIndex was assigned by the agent, i.e., in which row the job 3637 information is in the other tables. 3639 NOTE - fixed-length is used so that a management application can 3640 use a shortened GetNext varbind (in SNMPv1 and SNMPv2) in order 3641 to get the next submission ID, disregarding the remainder of the 3642 ID in order to access jobs independent of the trailing 3643 identifier part, e.g., to get all jobs submitted by a particular 3644 jmJobOwner or from a particular MAC address." 3645 ::= { jmJobIDEntry 1 } 3647 jmJobIDJobSetIndex OBJECT-TYPE 3648 SYNTAX Integer32(1..32767) 3649 MAX-ACCESS read-only 3650 STATUS current 3651 DESCRIPTION 3652 "This object contains the value of the jmGeneralJobSetIndex for 3653 the job with the jmJobSubmissionID value, i.e., the job set 3654 index of the job set in which the job was placed when that 3655 server or device accepted the job. This 16-bit value in 3656 combination with the jmJobIDJobIndex value permits the 3657 management application to access the other tables to obtain the 3658 job-specific objects for this job." 3659 REFERENCE 3660 "See jmGeneralJobSetIndex in the jmGeneralTable." 3661 ::= { jmJobIDEntry 2 } 3663 jmJobIDJobIndex OBJECT-TYPE 3664 SYNTAX Integer32(1..2147483647) 3665 MAX-ACCESS read-only 3666 STATUS current 3667 DESCRIPTION 3668 "This object contains the value of the jmJobIndex for the job 3669 with the jmJobSubmissionID value, i.e., the job index for the 3670 job when the server or device accepted the job. This value, in 3671 combination with the jmJobIDJobSetIndex value, permits the 3673 Job Monitoring MIB, V0.84 July 21, 1997 3675 management application to access the other tables to obtain the 3676 job-specific objects for this job." 3677 REFERENCE 3678 "See jmJobIndex in the jmJobTable." 3679 ::= { jmJobIDEntry 3 } 3681 - -- The Job Group (MANDATORY) 3683 - -- The jmJobGroup consists entirely of the jmJobTable. 3685 jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 } 3687 jmJobTable OBJECT-TYPE 3688 SYNTAX SEQUENCE OF JmJobEntry 3689 MAX-ACCESS not-accessible 3690 STATUS current 3691 DESCRIPTION 3692 "The jmJobTable consists of basic job state and status 3693 information for each job in a job set that (1) monitoring 3694 applications need to be able to access in a single SNMP Get 3695 operation, (2) that have a single value per job, and (3) that 3696 SHALL always be implemented." 3697 REFERENCE 3698 "The MANDATORY-GROUP macro specifies that this group is 3699 MANDATORY." 3700 ::= { jmJob 1 } 3702 jmJobEntry OBJECT-TYPE 3703 SYNTAX JmJobEntry 3704 MAX-ACCESS not-accessible 3705 STATUS current 3706 DESCRIPTION 3707 "Basic per-job state and status information. 3709 An entry SHALL exist in this table for each job, no matter what 3710 the state of the job is. Each job SHALL appear in one and only 3711 one job set." 3712 REFERENCE 3713 "See Section 3.2 entitled 'The Job Tables'." 3714 INDEX { jmGeneralJobSetIndex, jmJobIndex } 3715 ::= { jmJobTable 1 } 3717 JmJobEntry ::= SEQUENCE { 3718 jmJobIndex Integer32(1..2147483647), 3719 jmJobState JmJobStateTC, 3721 Job Monitoring MIB, V0.84 July 21, 1997 3723 jmJobStateReasons1 JmJobStateReasons1TC, 3724 jmNumberOfInterveningJobs Integer32(-2..2147483647), 3725 jmJobKOctetsRequested Integer32(-2..2147483647), 3726 jmJobKOctetsProcessed Integer32(-2..2147483647), 3727 jmJobImpressionsRequested Integer32(-2..2147483647), 3728 jmJobImpressionsCompleted Integer32(-2..2147483647), 3729 jmJobOwner OCTET STRING(SIZE(0..63)) 3730 } 3732 jmJobIndex OBJECT-TYPE 3733 SYNTAX Integer32(1..2147483647) 3734 MAX-ACCESS not-accessible 3735 STATUS current 3736 DESCRIPTION 3737 "The sequential, monatonically increasing identifier index for 3738 the job generated by the server or device when that server or 3739 device accepted the job. This index value permits the 3740 management application to access the other tables to obtain the 3741 job-specific row entries. 3743 Agents providing access to systems that contain jobs with a job 3744 identifier of 0 SHALL map the job identifier value 0 to a 3745 jmJobIndex value that is one higher than the highest job 3746 identifier value that any job can have on that system." 3747 REFERENCE 3748 "See Section 3.2 entitled 'The Job Tables'. 3749 See also jmGeneralNewestActiveJobIndex for the largest value of 3750 jmJobIndex. 3751 See JmJobSubmissionTypeTC for a limit on the size of this index 3752 if the agent represents it as an 8-digit decimal number." 3753 ::= { jmJobEntry 1 } 3755 jmJobState OBJECT-TYPE 3756 SYNTAX JmJobStateTC 3757 MAX-ACCESS read-only 3758 STATUS current 3759 DESCRIPTION 3760 "The current state of the job (pending, processing, completed, 3761 etc.). Agents SHALL implement only those states which are 3762 appropriate for the particular implementation. However, 3763 management applications SHALL be prepared to receive all the 3764 standard job states. 3766 The final value for this object SHALL be one of: completed, 3767 canceled, or aborted. The minimum length of time that the agent 3768 SHALL maintain MIB data for a job in the completed, canceled, or 3769 aborted state before removing the job data from the jmJobIDTable 3771 Job Monitoring MIB, V0.84 July 21, 1997 3773 and jmJobTable is specified by the value of the 3774 jmGeneralJobPersistence object." 3775 ::= { jmJobEntry 2 } 3777 jmJobStateReasons1 OBJECT-TYPE 3778 SYNTAX JmJobStateReasons1TC 3779 MAX-ACCESS read-only 3780 STATUS current 3781 DESCRIPTION 3782 "Additional information about the job's current state, i.e., 3783 information that augments the value of the job's jmJobState 3784 object. 3786 Implementation of any reason values is OPTIONAL, but an agent 3787 SHOULD return any reason information available These values MAY 3788 be used with any job state or states for which the reason makes 3789 sense. Furthermore, when implemented as with any MIB data, the 3790 agent SHALL return these values when the reason applies and 3791 SHALL NOT return them when the reason no longer applies whether 3792 the value of the job's jmJobState object changed or not. When 3793 the agent cannot provide a reason for the current state of the 3794 job, the agent SHALL set the value of the jmJobStateReasons1 3795 object and jobStateReasonsN attributes to 0." 3796 REFERENCE 3797 "The jobStateReasonsN (N=2..4) attributes provide further 3798 additional information about the job's current state." 3799 ::= { jmJobEntry 3 } 3801 jmNumberOfInterveningJobs OBJECT-TYPE 3802 SYNTAX Integer32(-2..2147483647) 3803 MAX-ACCESS read-only 3804 STATUS current 3805 DESCRIPTION 3806 "The number of jobs that are expected to be processed before 3807 this job is processed according to the implementation's queuing 3808 algorithm if no other jobs were to be submitted. In other 3809 words, this value is the job's queue position. The agent SHALL 3810 return a value of 0 for this attribute while the job is 3811 processing." 3812 ::= { jmJobEntry 4 } 3814 jmJobKOctetsRequested OBJECT-TYPE 3815 SYNTAX Integer32(-2..2147483647) 3816 MAX-ACCESS read-only 3817 STATUS current 3818 DESCRIPTION 3819 "The total size in K (1024) octets of the document(s) being 3820 requested to be processed in the job. The agent SHALL round the 3822 Job Monitoring MIB, V0.84 July 21, 1997 3824 actual number of octets up to the next highest K. Thus 0 octets 3825 SHALL be represented as '0', 1-1024 octets SHALL be represented 3826 as '1', 1025-2048 SHALL be represented as '2', etc. 3828 In computing this value, the server/device SHALL not include the 3829 multiplicative factors contributed by (1) the number of document 3830 copies, and (2) the number of job copies, independent of whether 3831 the device can process multiple copies of the job or document 3832 without making multiple passes over the job or document data and 3833 independent of whether the output is collated or not. Thus the 3834 server/device computation is independent of the implementation." 3835 ::= { jmJobEntry 5 } 3837 jmJobKOctetsProcessed OBJECT-TYPE 3838 SYNTAX Integer32(-2..2147483647) 3839 MAX-ACCESS read-only 3840 STATUS current 3841 DESCRIPTION 3842 "The current number of octets processed by the server or device 3843 measured in units of K (1024) octets. The agent SHALL round the 3844 actual number of octets processed up to the next higher K. Thus 3845 0 octets SHALL be represented as '0', 1-1024 octets SHALL be 3846 represented as '1', 1025-2048 octets SHALL be '2', etc. For 3847 printing devices, this value is the number interpreted by the 3848 page description language interpreter rather than what has been 3849 marked on media. 3851 For implementations where multiple copies are produced by the 3852 interpreter with only a single pass over the data, the final 3853 value SHALL be equal to the value of the jmJobKOctetsRequested 3854 object. For implementations where multiple copies are produced 3855 by the interpreter by processing the data for each copy, the 3856 final value SHALL be a multiple of the value of the 3857 jmJobKOctetsRequested object. 3859 NOTE - See the impressionsCompletedCurrentCopy and 3860 pagesCompletedCurrentCopy attributes for attributes that are 3861 reset on each document copy. 3863 NOTE - The jmJobKOctetsProcessed object can be used with the 3864 jmJobKOctetsRequested object to provide an indication of the 3865 relative progress of the job, provided that the multiplicative 3866 factor is taken into account for some implementations of 3867 multiple copies." 3868 ::= { jmJobEntry 6 } 3870 jmJobImpressionsRequested OBJECT-TYPE 3871 SYNTAX Integer32(-2..2147483647) 3873 Job Monitoring MIB, V0.84 July 21, 1997 3875 MAX-ACCESS read-only 3876 STATUS current 3877 DESCRIPTION 3878 "The number of impressions requested by this job to produce." 3879 ::= { jmJobEntry 7 } 3881 jmJobImpressionsCompleted OBJECT-TYPE 3882 SYNTAX Integer32(-2..2147483647) 3883 MAX-ACCESS read-only 3884 STATUS current 3885 DESCRIPTION 3886 "The current number of impressions completed for this job so 3887 far. For printing devices, the impressions completed includes 3888 interpreting, marking, and stacking the output. For other types 3889 of job services, the number of impressions completed includes 3890 the number of impressions processed." 3891 ::= { jmJobEntry 8 } 3893 jmJobOwner OBJECT-TYPE 3894 SYNTAX OCTET STRING(SIZE(0..63)) 3895 MAX-ACCESS read-only 3896 STATUS current 3897 DESCRIPTION 3898 "The coded character set name of the user that submitted the 3899 job. The method of assigning this user name will be system 3900 and/or site specific but the method MUST insure that the name is 3901 unique to the network that is visible to the client and target 3902 device. 3904 This value SHOULD be the authenticated name of the user 3905 submitting the job." 3906 REFERENCE 3907 "See the OBJECT compliance macro for the minimum maximum length 3908 required for conformance." 3909 ::= { jmJobEntry 9 } 3911 - -- The Attribute Group (MANDATORY) 3913 - -- The jmAttributeGroup consists entirely of the jmAttributeTable. 3914 - -- 3915 - -- Implementation of the two objects in this group is MANDATORY. 3916 - -- See Section 3.1 entitled 'Conformance Considerations'. 3917 - -- An agent SHALL implement any attribute if (1) the server or device 3918 - -- supports the functionality represented by the attribute and (2) the 3919 - -- information is available to the agent. 3921 Job Monitoring MIB, V0.84 July 21, 1997 3923 jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 } 3925 jmAttributeTable OBJECT-TYPE 3926 SYNTAX SEQUENCE OF JmAttributeEntry 3927 MAX-ACCESS not-accessible 3928 STATUS current 3929 DESCRIPTION 3930 "The jmAttributeTable SHALL contain attributes of the job and 3931 document(s) for each job in a job set. Instead of allocating 3932 distinct objects for each attribute, each attribute is 3933 represented as a separate row in the jmAttributeTable." 3934 REFERENCE 3935 "The MANDATORY-GROUP macro specifies that this group is 3936 MANDATORY. An agent SHALL implement any attribute if (1) the 3937 server or device supports the functionality represented by the 3938 attribute and (2) the information is available to the agent. " 3939 ::= { jmAttribute 1 } 3941 jmAttributeEntry OBJECT-TYPE 3942 SYNTAX JmAttributeEntry 3943 MAX-ACCESS not-accessible 3944 STATUS current 3945 DESCRIPTION 3946 "Attributes representing information about the job and 3947 document(s) or resources required and/or consumed. 3949 Each entry in the jmAttributeTable is a per-job entry with an 3950 extra index for each type of attribute (jmAttributeTypeIndex) 3951 that a job can have and an additional index 3952 (jmAttributeInstanceIndex) for those attributes that can have 3953 multiple instances per job. The jmAttributeTypeIndex object 3954 SHALL contain an enum type that indicates the type of attribute 3955 (see the JmAttributeTypeTC textual-convention). The value of 3956 the attribute SHALL be represented in either the 3957 jmAttributeValueAsInteger or jmAttributeValueAsOctets objects, 3958 and/or both, as specified in the JmAttributeTypeTC textual- 3959 convention. 3961 The agent SHALL create rows in the jmAttributeTable as the 3962 server or device is able to discover the attributes either from 3963 the job submission protocol itself or from the document PDL. As 3964 the documents are interpreted, the interpreter MAY discover 3965 additional attributes and so the agent adds additional rows to 3966 this table. As the attributes that represent resources are 3967 actually consumed, the usage counter contained in the 3968 jmAttributeValueAsInteger object is incremented according to the 3970 Job Monitoring MIB, V0.84 July 21, 1997 3972 units indicated in the description of the JmAttributeTypeTC 3973 enum. 3975 The agent SHALL maintain each row in the jmJobTable for at least 3976 the minimum time after a job completes as specified by the 3977 jmGeneralAttributePersistence object. 3979 Zero or more entries SHALL exist in this table for each job in a 3980 job set." 3981 REFERENCE 3982 "See Section 3.3 entitled 'The Attribute Mechanism' for a 3983 description of the jmAttributeTable." 3984 INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex, 3985 jmAttributeInstanceIndex } 3986 ::= { jmAttributeTable 1 } 3988 JmAttributeEntry ::= SEQUENCE { 3989 jmAttributeTypeIndex JmAttributeTypeTC, 3990 jmAttributeInstanceIndex Integer32(1..32767), 3991 jmAttributeValueAsInteger Integer32(-2..2147483647), 3992 jmAttributeValueAsOctets OCTET STRING(SIZE(0..63)) 3993 } 3995 jmAttributeTypeIndex OBJECT-TYPE 3996 SYNTAX JmAttributeTypeTC 3997 MAX-ACCESS not-accessible 3998 STATUS current 3999 DESCRIPTION 4000 "The type of attribute that this row entry represents. 4002 The type MAY identify information about the job or document(s) 4003 or MAY identify a resource required to process the job before 4004 the job start processing and/or consumed by the job as the job 4005 is processed. 4007 Examples of job and document attributes include: 4008 jobCopiesRequested, documentCopiesRequested, jobCopiesCompleted, 4009 documentCopiesCompleted, fileName, and documentName. 4011 Examples of required and consumed resource attributes include: 4012 pagesRequested, pagesCompleted, mediumRequested, and 4013 mediumConsumed, respectively." 4014 ::= { jmAttributeEntry 1 } 4016 jmAttributeInstanceIndex OBJECT-TYPE 4017 SYNTAX Integer32(1..32767) 4018 MAX-ACCESS not-accessible 4019 STATUS current 4021 Job Monitoring MIB, V0.84 July 21, 1997 4023 DESCRIPTION 4024 "A running 16-bit index of the attributes of the same type for 4025 each job. For those attributes with only a single instance per 4026 job, this index value SHALL be 1. For those attributes that are 4027 a single value per document, the index value SHALL be the 4028 document number, starting with 1 for the first document in the 4029 job. Jobs with only a single document SHALL use the index value 4030 of 1. For those attributes that can have multiple values per 4031 job or per document, such as documentFormatIndex(37) or 4032 documentFormat(38), the index SHALL be a running index for the 4033 job as a whole, starting at 1." 4034 ::= { jmAttributeEntry 2 } 4036 jmAttributeValueAsInteger OBJECT-TYPE 4037 SYNTAX Integer32(-2..2147483647) 4038 MAX-ACCESS read-only 4039 STATUS current 4040 DESCRIPTION 4041 "The integer value of the attribute. The value of the attribute 4042 SHALL be represented as an integer if the enum description in 4043 the JmAttributeTypeTC textual-convention definition has the tag: 4044 'INTEGER:'. 4046 Depending on the enum definition, this object value MAY be an 4047 integer, a counter, an index, or an enum, depending on the 4048 jmAttributeTypeIndex value. The units of this value are 4049 specified in the enum description. 4051 For those attributes that are accumulating job consumption as 4052 the job is processed as specified in the JmAttributeTypeTC 4053 textual-convention, SHALL contain the final value after the job 4054 completes processing, i.e., this value SHALL indicate the total 4055 usage of this resource made by the job. 4057 A monitoring application is able to copy this value to a 4058 suitable longer term storage for later processing as part of an 4059 accounting system. 4061 Since the agent MAY add attributes representing resources to 4062 this table while the job is waiting to be processed or being 4063 processed, which can be a long time before any of the resources 4064 are actually used, the agent SHALL set the value of the 4065 jmAttributeValueAsInteger object to 0 for resources that the job 4066 has not yet consumed. 4068 Attributes for which the concept of an integer value is 4069 meaningless, such as fileName, interpreter, and physicalDevice, 4070 do not have the 'INTEGER:' tag in the JmAttributeTypeTC 4072 Job Monitoring MIB, V0.84 July 21, 1997 4074 definition and so an agent SHALL always return a value of '-1' 4075 to indicate 'other' for jmAttributeValueAsInteger. 4077 For attributes which do have the 'INTEGER:' tag in the 4078 JmAttributeTypeTC definition, if the integer value is not (yet) 4079 known, the agent either SHALL not materialize the row in the 4080 jmAttributeTable until the value is known or SHALL return a '-2' 4081 to represent an 'unknown' counting integer value, a '0' to 4082 represent an 'unknown' index value, and a '2' to represent an 4083 'unknown(2)' enum value." 4084 ::= { jmAttributeEntry 3 } 4086 jmAttributeValueAsOctets OBJECT-TYPE 4087 SYNTAX OCTET STRING(SIZE(0..63)) 4088 MAX-ACCESS read-only 4089 STATUS current 4090 DESCRIPTION 4091 "The octet string value of the attribute. The value of the 4092 attribute SHALL be represented as an OCTET STRING if the enum 4093 description in the JmAttributeTypeTC textual-convention 4094 definition has the tag: 'OCTETS:'. 4096 Depending on the enum definition, this object value MAY be a 4097 coded character set string (text) or a binary octet string, such 4098 as DateAndTime. 4100 Attributes for which the concept of an octet string value is 4101 meaningless, such as pagesCompleted, do not have the tag 4102 'OCTETS:' in the JmAttributeTypeTC definition and so the agent 4103 SHALL always return a zero length string for the value of the 4104 jmAttributeValueAsOctets object. 4106 For attributes which do have the 'OCTETS:' tag in the 4107 JmAttributeTypeTC definition, if the OCTET STRING value is not 4108 (yet) known, the agent either SHALL not materialize the row in 4109 the jmAttributeTable until the value is known or SHALL return a 4110 zero-length string." 4111 ::= { jmAttributeEntry 4 } 4113 Job Monitoring MIB, V0.84 July 21, 1997 4115 - -- Notifications and Trapping 4116 - -- Reserved for the future 4118 jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2} 4120 - -- Conformance Information 4122 jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 } 4124 - -- compliance statements 4125 jmMIBCompliance MODULE-COMPLIANCE 4126 STATUS current 4127 DESCRIPTION 4128 "The compliance statement for agents that implement the 4129 job monitoring MIB." 4130 MODULE -- this module 4131 MANDATORY-GROUPS { 4132 jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup } 4134 OBJECT jmGeneralJobSetName 4135 SYNTAX OCTET STRING (SIZE(0..8)) 4136 DESCRIPTION 4137 "Only 8 octets maximum string length NEED be supported by the 4138 agent." 4140 OBJECT jmJobOwner 4141 SYNTAX OCTET STRING (SIZE(0..16)) 4142 DESCRIPTION 4143 "Only 16 octets maximum string length NEED be supported by the 4144 agent." 4146 - -- There are no CONDITIONALLY MANDATORY or OPTIONAL groups. 4148 ::= { jmMIBConformance 1 } 4150 jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 } 4152 jmGeneralGroup OBJECT-GROUP 4153 OBJECTS { 4154 jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex, 4155 jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence, 4156 jmGeneralAttributePersistence, jmGeneralJobSetName} 4157 STATUS current 4158 DESCRIPTION 4159 "The general group." 4160 ::= { jmMIBGroups 1 } 4162 Job Monitoring MIB, V0.84 July 21, 1997 4164 jmJobIDGroup OBJECT-GROUP 4165 OBJECTS { 4166 jmJobIDJobSetIndex, jmJobIDJobIndex } 4167 STATUS current 4168 DESCRIPTION 4169 "The job ID group." 4170 ::= { jmMIBGroups 2 } 4172 jmJobGroup OBJECT-GROUP 4173 OBJECTS { 4174 jmJobState, jmJobStateReasons1, jmNumberOfInterveningJobs, 4175 jmJobKOctetsRequested, jmJobKOctetsProcessed, 4176 jmJobImpressionsRequested, jmJobImpressionsCompleted, jmJobOwner 4177 } 4178 STATUS current 4179 DESCRIPTION 4180 "The job group." 4181 ::= { jmMIBGroups 3 } 4183 jmAttributeGroup OBJECT-GROUP 4184 OBJECTS { 4185 jmAttributeValueAsInteger, jmAttributeValueAsOctets } 4186 STATUS current 4187 DESCRIPTION 4188 "The attribute group." 4189 ::= { jmMIBGroups 4 } 4191 END 4193 Job Monitoring MIB, V0.84 July 21, 1997 4195 5. Appendix A - Implementing the Job Life Cycle 4197 The job object has well-defined states and client operations that affect 4198 the transition between the job states. Internal server and device 4199 actions also affect the transitions of the job between the job states. 4200 These states and transitions are referred to as the job's life cycle. 4202 Not all implementations of job submission protocols have all of the 4203 states of the job model specified here. The job model specified here is 4204 intended to be a superset of most implementations. It is the purpose of 4205 the agent to map the particular implementation's job life cycle onto the 4206 one specified here. The agent MAY omit any states not implemented. 4207 Only the processing and completed states are required to be implemented 4208 by an agent. However, a conforming management application SHALL be 4209 prepared to accept any of the states in the job life cycle specified 4210 here, so that the management application can interoperate with any 4211 conforming agent. 4213 The job states are intended to be user visible. The agent SHALL make 4214 these states visible in the MIB, but only for the subset of job states 4215 that the implementation has. Some implementations MAY need to have sub- 4216 states of these user-visible states. The jmJobStateReasons1 object and 4217 the jobStateReasonsN (N=2..4) attributes can be used to represent the 4218 sub-states of the jobs. 4220 Job states are intended to last a user-visible length of time in most 4221 implementations. However, some jobs may pass through some states in 4222 zero time in some situations and/or in some implementations. 4224 The job model does not specify how accounting and auditing is 4225 implemented, except to assume that accounting and auditing logs are 4226 separate from the job life cycle and last longer than job entries in the 4227 MIB. Jobs in the completed, aborted, or canceled states are not logs, 4228 since jobs in these states are accessible via SNMP protocol operations 4229 and SHALL be removed from the Job Monitoring MIB tables after a site- 4230 settable or implementation-defined period of time. An accounting 4231 application MAY copy accounting information incrementally to an 4232 accounting log as a job processes, or MAY be copied while the job is in 4233 the canceled, aborted, or completed states, depending on implementation. 4234 The same is true for auditing logs. 4236 The jmJobState object specifies the standard job states. The normal job 4237 state transitions are shown in the state transition diagram presented in 4238 Table 1. 4240 Job Monitoring MIB, V0.84 July 21, 1997 4242 6. APPENDIX B - Support of the Job Submission ID in Job Submission 4243 Protocols 4245 This appendix lists the job submission protocols that support the 4246 concept of a job submission ID and indicates the attribute used in that 4247 job submission protocol. 4249 6.1 Hewlett-Packard's Printer Job Language (PJL) 4251 Hewlett-Packard's Printer Job Language provides job-level printer 4252 control and printer status information to applications. The PJL JOB 4253 command is used at the beginning of a print job and can include options 4254 applying only to that job. A PJL JOB command option has been defined to 4255 facilitate passing the JobSubmissionID with the print job, as required 4256 by the Job Monitoring MIB. The option is of the form: 4258 SUBMISSIONID = "id string" 4260 Where the "id string" is a string and SHALL be enclosed in double 4261 quotes. The format is as described for the jmJobSubmissionID object. 4263 The entire PJL JOB command with the optional parameter would be of the 4264 form: 4266 @PJL JOB SUBMISSIONID = "id string" 4268 See "Printer Job Language Technical Reference Manual", part number 5021- 4269 0328, from Hewlett-Packard for complete information on the PJL JOB 4270 command and the Printer Job Language. 4272 6.2 ISO DPA 4274 The ISO 10175 Document Printing Application (DPA) protocol specifies the 4275 "job-client-id" attribute that allows the client to supply a text string 4276 ID for each job. 4278 7. References 4280 [hr-mib] P. Grillo, S. Waldbusser, "Host Resources MIB", RFC 1514, 4281 September 1993 4283 [iana] J. Reynolds, and J. Postel, "Assigned Numbers", STD 2, RFC 1700, 4284 ISI, October 1994. 4286 Job Monitoring MIB, V0.84 July 21, 1997 4288 [iana-media-types] IANA Registration of MIME media types (MIME content 4289 types/subtypes). See ftp://ftp.isi.edu/in-notes/iana/assignments/ 4291 [iso-dpa] ISO/IEC 10175 Document Printing Application (DPA). See 4292 ftp://ftp.pwg.org/pub/pwg/dpa/ 4294 [ipp-model] Internet Printing Protocol (IPP), work in progress on the 4295 IETF standards track. See draft-ietf-ipp-model-01.txt. See also 4296 http://www.pwg.org/ipp/index.html 4298 [mib-II] MIB-II, RFC 1213. 4300 [print-mib] The Printer MIB - RFC 1759, proposed IETF standard. Also an 4301 Internet-Draft on the standards track as a draft standard: draft-ietf- 4302 printmib-mib-info-02.txt 4304 [req-words] S. Bradner, "Keywords for use in RFCs to Indicate 4305 Requirement Levels", RFC 2119, March 1997. 4307 [rfc 2130] C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R. 4308 Atkinson, M. Crispin, and P. Svanberg, "The Report of the IAB Character 4309 Set Workshop held 29 Feb-1 March, 1997", April 1997, RFC 2130. 4311 [SMIv2-TC] J. Case, et al. ``extual Conventions for Version 2 of the 4312 Simple Network Managment Protocol (SNMPv2)'' RFC 1903, January 1996. 4314 [tipsi] IEEE 1284.1, Transport-independent Printer System Interface 4315 (TIPSI). 4317 [URI-spec] Berners-Lee, T., Masinter, L., McCahill, M. , "Uniform 4318 Resource Locators (URL)", RFC 1738, December, 1994. 4320 8. Author's Addresses 4321 Ron Bergman 4322 Dataproducts Corp. 4323 1757 Tapo Canyon Road 4324 Simi Valley, CA 93063-3394 4326 Phone: 805-578-4421 4327 Fax: 805-578-4001 4328 Email: rbergman@dpc.com 4330 Tom Hastings 4331 Xerox Corporation, ESAE-231 4332 701 S. Aviation Blvd. 4333 El Segundo, CA 90245 4335 Job Monitoring MIB, V0.84 July 21, 1997 4337 Phone: 310-333-6413 4338 Fax: 310-333-5514 4339 EMail: hastings@cp10.es.xerox.com 4341 Scott A. Isaacson 4342 Novell, Inc. 4343 122 E 1700 S 4344 Provo, UT 84606 4346 Phone: 801-861-7366 4347 Fax: 801-861-4025 4348 EMail: scott_isaacson@novell.com 4350 Harry Lewis 4351 IBM Corporation 4352 6300 Diagonal Hwy 4353 Boulder, CO 80301 4355 Phone: (303) 924-5337 4356 Fax: 4357 Email: harryl@us.ibm.com 4359 Send comments to the printmib WG using the Job Monitoring Project 4360 (JMP) Mailing List: jmp@pwg.org 4362 To learn how to subscribe, send email to: jmp-request@pwg.org 4364 For further information, access the PWG web page under "JMP": 4365 http://www.pwg.org/ 4367 Other Participants: 4368 Chuck Adams - Tektronix 4369 Jeff Barnett - IBM 4370 Keith Carter, IBM Corporation 4371 Jeff Copeland - QMS 4372 Andy Davidson - Tektronix 4373 Roger deBry - IBM 4374 Mabry Dozier - QMS 4375 Lee Ferrel - Canon 4376 Steve Gebert - IBM 4377 Robert Herriot - Sun Microsystems Inc. 4378 Shige Kanemitsu - Kyocera 4379 David Kellerman - Northlake Software 4381 Job Monitoring MIB, V0.84 July 21, 1997 4383 Rick Landau - Digital 4384 Harry Lewis - IBM 4385 Pete Loya - HP 4386 Ray Lutz - Cognisys 4387 Jay Martin - Underscore 4388 Mike MacKay, Novell, Inc. 4389 Stan McConnell - Xerox 4390 Carl-Uno Manros, Xerox, Corp. 4391 Pat Nogay - IBM 4392 Bob Pentecost - HP 4393 Rob Rhoads - Intel 4394 David Roach - Unisys 4395 Hiroyuki Sato - Canon 4396 Bob Setterbo - Adobe 4397 Gail Songer, EFI 4398 Mike Timperman - Lexmark 4399 Randy Turner - Sharp 4400 William Wagner - Digital Products 4401 Jim Walker - Dazel 4402 Chris Wellens - Interworking Labs 4403 Rob Whittle - Novell 4404 Don Wright - Lexmark 4405 Lloyd Young - Lexmark 4406 Atsushi Yuki - Kyocera 4407 Peter Zehler, Xerox, Corp. 4409 Job Monitoring MIB, V0.84 July 21, 1997 4411 9. INDEX 4413 This index includes the textual conventions, the objects, and the 4414 attributes. Textual conventions all start with the prefix: "JM" and 4415 end with the suffix: "TC". Objects all starts with the prefix: "jm" 4416 followed by the group name. Attributes are identified with enums, and 4417 so start with any lower case letter and have no special prefix. 4419 ------ 4421 colorantConsumed, 58 4422 colorantRequested, 58 4424 --D--- 4426 deviceNameRequested, 49 4427 documentCopiesCompleted, 54 4428 documentCopiesRequested, 54 4429 documentFormat, 51 4430 documentFormatIndex, 50 4431 documentName, 50 4433 ------ 4435 fileName, 50 4436 finishing, 52 4437 fullColorImpressionsCompleted, 55 4439 --H--- 4441 highlightColorImpressionsCompleted, 56 4443 ------ 4445 impressionsCompletedCurrentCopy, 55 4446 impressionsInterpreted, 55 4447 impressionsSentToDevice, 55 4448 impressionsSpooled, 55 4450 --J--- 4452 jmAttributeInstanceIndex, 85 4453 jmAttributeTypeIndex, 85 4454 JmAttributeTypeTC, 45 4455 jmAttributeValueAsInteger, 86 4456 jmAttributeValueAsOctets, 87 4457 JmBooleanTC, 38 4459 Job Monitoring MIB, V0.84 July 21, 1997 4461 JmFinishingTC, 35 4462 jmGeneralAttributePersistence, 75 4463 jmGeneralJobPersistence, 75 4464 jmGeneralJobSetIndex, 73 4465 jmGeneralJobSetName, 76 4466 jmGeneralNewestActiveJobIndex, 75 4467 jmGeneralNumberOfActiveJobs, 74 4468 jmGeneralOldestActiveJobIndex, 74 4469 jmJobIDJobIndex, 78 4470 jmJobIDJobSetIndex, 78 4471 jmJobImpressionsCompleted, 83 4472 jmJobImpressionsRequested, 82 4473 jmJobIndex, 80 4474 jmJobKOctetsProcessed, 82 4475 jmJobKOctetsRequested, 81 4476 jmJobOwner, 83 4477 JmJobServiceTypesTC, 61 4478 JmJobSourcePlatformTypeTC, 34 4479 jmJobState, 80 4480 jmJobStateReasons1, 81 4481 JmJobStateReasons1TC, 63 4482 JmJobStateReasons2TC, 66 4483 JmJobStateReasons3TC, 70 4484 JmJobStateReasons4TC, 71 4485 JmJobStateTC, 42 4486 jmJobSubmissionID, 77 4487 JmJobSubmissionTypeTC, 40 4488 JmMediumTypeTC, 38 4489 jmNumberOfInterveningJobs, 81 4490 JmPrinterResolutionTC, 37 4491 JmPrintQualityTC, 37 4492 JmTimeStampTC, 34 4493 JmTonerEconomyTC, 38 4494 jobAccountName, 47 4495 jobComment, 50 4496 jobCompletedTime, 59 4497 jobCopiesCompleted, 54 4498 jobCopiesRequested, 54 4499 jobHold, 52 4500 jobHoldUntil, 52 4501 jobKOctetsTransferred, 54 4502 jobName, 47 4503 jobOriginatingHost, 49 4504 jobPriority, 51 4505 jobProcessAfterDateAndTime, 51 4506 jobProcessingCPUTime, 59 4507 jobServiceTypes, 48 4508 jobSourceChannelIndex, 48 4510 Job Monitoring MIB, V0.84 July 21, 1997 4512 jobSourcePlatformType, 48 4513 jobStartedBeingHeldTime, 59 4514 jobStartedProcessingTime, 59 4515 jobStateReasons2, 46 4516 jobStateReasons3, 46 4517 jobStateReasons4, 46 4518 jobSubmissionTime, 59 4519 jobSubmissionToServerTime, 58 4521 ------ 4523 mediumConsumed, 57 4524 mediumRequested, 57 4526 ------ 4528 numberOfDocuments, 50 4530 ------ 4532 other, 46 4533 outputBin, 52 4535 --P--- 4537 pagesCompleted, 56 4538 pagesCompletedCurrentCopy, 56 4539 pagesRequested, 56 4540 physicalDevice, 49 4541 printerResolutionRequested, 53 4542 printerResolutionUsed, 53 4543 printQualityRequested, 53 4544 printQualityUsed, 53 4545 processingMessage, 46 4547 ------ 4549 queueNameRequested, 49 4551 --S--- 4553 serverAssignedJobName, 47 4554 sheetsCompleted, 57 4555 sheetsCompletedCurrentCopy, 57 4556 sheetsRequested, 57 4557 sides, 52 4558 submittingApplicationName, 49 4559 submittingServerName, 49 4561 Job Monitoring MIB, V0.84 July 21, 1997 4563 ------ 4565 tonerDensityRequested, 53 4566 tonerDensityUsed, 53 4567 tonerEcomonyRequested, 53 4568 tonerEcomonyUsed, 53