Network Working Group R. Bergman
Request for Comments: 2707 Dataproducts Corp.
Category: Informational T. Hastings, Ed.
Xerox Corporation
S. Isaacson
Novell, Inc.
H. Lewis
IBM Corp.
November 1999
Network Working Group R. Bergman
Request for Comments: 2707 Dataproducts Corp.
Category: Informational T. Hastings, Ed.
Xerox Corporation
S. Isaacson
Novell, Inc.
H. Lewis
IBM Corp.
November 1999
Job Monitoring MIB - V1.0
作业监视MIB-V1.0
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
IESG Note
IESG注释
This MIB module uses an unconventional scheme for modeling management information (on top of the SNMP model) which is unique to this MIB. The IESG recommends against using this document as an example for the design of future MIBs.
此MIB模块使用非常规的方案来建模管理信息（在SNMP模型之上），这是此MIB独有的。IESG建议不要将本文档用作未来MIB设计的示例。
The "Printer Working Group" industry consortium is not an IETF working group, and the IETF does not recognize the Printer Working Group as a standards-setting body. This document is being published solely to provide information to the Internet community regarding a MIB that might be deployed in the marketplace. Publication of this document as an RFC is not an endorsement of this MIB.
“打印机工作组”行业联盟不是IETF工作组，IETF不承认打印机工作组是标准制定机构。本文档的发布仅为向互联网社区提供有关可能在市场上部署的MIB的信息。将本文件作为RFC发布并不是对本MIB的认可。
Abstract
摘要
This document provides a printer industry standard SNMP MIB for (1) monitoring the status and progress of print jobs (2) obtaining resource requirements before a job is processed, (3) monitoring resource consumption while a job is being processed and (4) collecting resource accounting data after the completion of a job. This MIB is intended to be implemented (1) in a printer or (2) in a server that supports one or more printers. Use of the object set is not limited to printing. However, support for services other than printing is outside the scope of this Job Monitoring MIB. Future
本文档提供了打印机行业标准SNMP MIB，用于（1）监控打印作业的状态和进度（2）在处理作业之前获取资源需求，（3）在处理作业时监控资源消耗，以及（4）在作业完成后收集资源记帐数据。此MIB旨在（1）在打印机中实现，或（2）在支持一台或多台打印机的服务器中实现。对象集的使用不限于打印。但是，对打印以外的服务的支持不在此作业监视MIB的范围内。将来
extensions to this MIB may include, but are not limited to, fax machines and scanners.
此MIB的扩展可能包括但不限于传真机和扫描仪。
Table of Contents
目录
1 INTRODUCTION 4 1.1 Types of Information in the MIB 5 1.2 Types of Job Monitoring Applications 6 2 TERMINOLOGY AND JOB MODEL 7 2.1 System Configurations for the Job Monitoring MIB 11 2.1.1 Configuration 1 - client-printer 11 2.1.2 Configuration 2 - client-server-printer - agent in the server 12 2.1.3 Configuration 3 - client-server-printer - client monitors printer agent and server 14 3 MANAGED OBJECT USAGE 15 3.1 Conformance Considerations 15 3.1.1 Conformance Terminology 16 3.1.2 Agent Conformance Requirements 16 3.1.2.1 MIB II System Group objects 17 3.1.2.2 MIB II Interface Group objects 17 3.1.2.3 Printer MIB objects 17 3.1.3 Job Monitoring Application Conformance Requirements 17 3.2 The Job Tables and the Oldest Active and Newest Active Indexes 18 3.3 The Attribute Mechanism and the Attribute Table(s) 20 3.3.1 Conformance of Attribute Implementation 21 3.3.2 Useful, 'Unknown', and 'Other' Values for Objects and Attributes 21 3.3.3 Index Value Attributes 22 3.3.4 Data Sub-types and Attribute Naming Conventions 22 3.3.5 Single-Value (Row) Versus Multi-Value (MULTI-ROW) Attributes 23 3.3.6 Requested Objects and Attributes 23 3.3.7 Consumption Attributes 24 3.3.8 Attribute Specifications 24 3.3.9 Job State Reason bit definitions 43 3.3.9.1 JmJobStateReasons1TC specification 44 3.3.9.2 JmJobStateReasons2TC specification 47 3.3.9.3 JmJobStateReasons3TC specification 51 3.3.9.4 JmJobStateReasons4TC specification 51 3.4 Monitoring Job Progress 51 3.5 Job Identification 55 3.5.1 The Job Submission ID specifications 56 3.6 Internationalization Considerations 60 3.6.1 Text generated by the server or device 61 3.6.2 Text supplied by the job submitter 61 3.6.3 'DateAndTime' for representing the date and time 63
1简介4 1.1 MIB中的信息类型5 1.2作业监控应用程序类型6 2术语和作业模型7 2.1作业监控MIB的系统配置11 2.1.1配置1-客户端打印机11 2.1.2配置2-客户端服务器打印机-服务器中的代理12 2.1.3配置3-客户端服务器打印机-客户端监视打印机代理和服务器14 3管理对象使用15 3.1一致性注意事项15 3.1.1一致性术语16 3.1.2代理一致性要求16 3.1.2.1 MIB II系统组对象17 3.1.2.2 MIB II接口组对象17 3.1.2.3打印机MIB对象17 3.1.3作业监视应用程序一致性要求173.2作业表和最旧的活动和最新的活动索引18 3.3属性机制和属性表20 3.3.1属性实现的一致性21 3.3.2有用，“未知”，对象和属性的“其他”值21 3.3.3索引值属性22 3.3.4数据子类型和属性命名约定22 3.3.5单值（行）与多值（多行）属性23 3.3.6请求的对象和属性23 3.3.7消耗属性24 3.3.8属性规范24 3.3.9作业状态原因位定义43 3.3.9.1 JmJobStateReasons1TC规范44 3.3.9.2 JmJobStateReasons2TC规范47 3.3.9.3 JmJobStateReasons3TC规范51 3.3.9.4 JmJobStateReasons4TC规范513.4监控作业进度51 3.5作业标识55 3.5.1作业提交ID规范56 3.6国际化注意事项60 3.6.1服务器或设备生成的文本61 3.6.2作业提交人提供的用于表示日期和时间的文本61 3.6.3“日期和时间”63
3.7 IANA and PWG Registration Considerations 63 3.7.1 PWG Registration of enums 63 3.7.1.1 Type 1 enumerations 64 3.7.1.2 Type 2 enumerations 64 3.7.1.3 Type 3 enumeration 64 3.7.2 PWG Registration of type 2 bit values 65 3.7.3 PWG Registration of Job Submission Id Formats 65 3.7.4 PWG Registration of MIME types/sub-types for document-formats 65 3.8 Security Considerations 65 3.8.1 Read-Write objects 65 3.8.2 Read-Only Objects In Other User's Jobs 66 3.9 Notifications 66 4 MIB SPECIFICATION 67 Textual conventions for this MIB module 68 JmUTF8StringTC 68 JmJobStringTC 68 JmNaturalLanguageTagTC 68 JmTimeStampTC 69 JmJobSourcePlatformTypeTC 69 JmFinishingTC 70 JmPrintQualityTC 71 JmPrinterResolutionTC 71 JmTonerEconomyTC 72 JmBooleanTC 72 JmMediumTypeTC 72 JmJobCollationTypeTC 74 JmJobSubmissionIDTypeTC 74 JmJobStateTC 75 JmAttributeTypeTC 78 JmJobServiceTypesTC 81 JmJobStateReasons1TC 83 JmJobStateReasons2TC 83 JmJobStateReasons3TC 83 JmJobStateReasons4TC 84 The General Group (MANDATORY) 84 jmGeneralJobSetIndex (Int32(1..32767)) 85 jmGeneralNumberOfActiveJobs (Int32(0..)) 86 jmGeneralOldestActiveJobIndex (Int32(0..)) 86 jmGeneralNewestActiveJobIndex (Int32(0..)) 86 jmGeneralJobPersistence (Int32(15..)) 87 jmGeneralAttributePersistence (Int32(15..)) 87 jmGeneralJobSetName (UTF8String63) 88 The Job ID Group (MANDATORY) 88 jmJobSubmissionID (OCTET STRING(SIZE(48))) 89 jmJobIDJobSetIndex (Int32(0..32767)) 90 jmJobIDJobIndex (Int32(0..)) 91 The Job Group (MANDATORY) 91
3.7 IANA和PWG注册注意事项63 3.7.1枚举的PWG注册63 3.7.1.1类型1枚举64 3.7.1.2类型2枚举64 3.7.1.3类型3枚举64 3.7.2类型2位值的PWG注册65 3.7.3作业提交Id格式的PWG注册65 3.7.4文件格式的MIME类型/子类型的PWG注册653.8安全注意事项65 3.8.1读写对象65 3.8.2其他用户作业中的只读对象66 3.9通知66 4 MIB规范67此MIB模块的文本约定68 JmUTF8StringTC 68 JmJobStringTC 68 JMNATURALLANGUETAGTC 68 JmTimeStampTC 69 JmJobSourcePlatformTypeTC 69 JmFinishingTC 70 JmPrintQualityTC 71JmPrinterResolutionTC 71 jmtoneeconomicytc 72 JmBooleanTC 72 JmMediumTypeTC 72 JmJobCollationTypeTC 74 JmJobSubmissionIDTypeTC 74 JmJobStateTC 75 JmAttributeTypeTC 78 JmJobServiceTypesTC 81 JmJobStateReasons1TC 83 jmJobStateReasons283 JmJobStateReasons4TC 84一般组（强制）84 jmGeneralJobSetIndex（Int32（1..32767）85 jmGeneralNumberOfActiveJobs（Int32（0..））86 JMGeneralOldStactiveJobIndex（Int32（0..））86 JMGeneralNewSetActiveJobIndex（Int32（0..））86 jmGeneralJobPersistence（Int32（15..）87 jmGeneralAttributePersistence（Int32（15..）87 jmGeneralJobSetName（UTStringF863）88作业ID组（必需）88作业提交ID（八位字符串（大小（48））)89 jmJobIDJobSetIndex（Int32（0..32767））90 jmJobIDJobSetIndex（Int32（0..））91作业组（必需）91
jmJobIndex (Int32(1..)) 92 jmJobState (JmJobStateTC) 92 jmJobStateReasons1 (JmJobStateReasons1TC) 93 jmNumberOfInterveningJobs (Int32(-2..)) 93 jmJobKOctetsPerCopyRequested (Int32(-2..)) 94 jmJobKOctetsProcessed (Int32(-2..)) 94 jmJobImpressionsPerCopyRequested (Int32(-2..)) 95 jmJobImpressionsCompleted (Int32(-2..)) 96 jmJobOwner (JobString63) 96 The Attribute Group (MANDATORY) 97 jmAttributeTypeIndex (JmAttributeTypeTC) 98 jmAttributeInstanceIndex (Int32(1..32767)) 99 jmAttributeValueAsInteger (Int32(-2..)) 99 jmAttributeValueAsOctets (Octets63) 100 5 APPENDIX A - IMPLEMENTING THE JOB LIFE CYCLE 104 6 APPENDIX B - SUPPORT OF JOB SUBMISSION PROTOCOLS 105 7 REFERENCES 105 8 NOTICES 108 9 AUTHORS' ADDRESSES 109 10 INDEX 111 11 Full Copyright Statement 114
jmJobIndex（Int32（1..））92 jmJobState（JmJobStateTC）92 jmJobStateReasons1（JmJobStateReasons1TC）93 jmJobStateReasons1（Int32（-2..））93 jmJobKoctetsPercOpyrRequested（Int32（-2..））94 jmJobKOctetsProcessed（Int32（-2..））94 jmJobImpressionsPercQuested（Int32（-2..））95 jmJobImpressionsCompleted（Int32（-2..））96 jmJobOwner（JobString63）96属性组（必需）97 jmAttributeTypeIndex（JmAttributeTypeTC）98 jmAttributeInstanceIndex（Int32（1..32767））99 jmAttributeValueAsInteger（Int32（-2..））99 jmAttributeValueAsOctets（Octets63）100 5附录A-实施工作生命周期104 6附录B-支持工作提交协议105 7参考文献105 8通知108 9作者地址109 10索引111 11完整版权声明114
1 Introduction
1导言
This specification defines an official Printer Working Group (PWG) [PWG] standard SNMP MIB for the monitoring of jobs on network printers. This specification is being published as an IETF Information Document for the convenience of the Internet community. In consultation with the IETF Application Area Directors, it was concluded that this MIB specification properly belongs as an Information document, because this MIB monitors a service node on the network, rather than a network node proper.
本规范定义了一个官方打印机工作组（PWG）[PWG]标准SNMP MIB，用于监控网络打印机上的作业。本规范作为IETF信息文件发布，以方便互联网社区。经与IETF应用区域主管协商，得出结论认为，该MIB规范应作为信息文档，因为该MIB监控网络上的服务节点，而不是网络节点本身。
The Job Monitoring MIB is intended to be implemented by an agent within a printer or the first server closest to the printer, where the printer is either directly connected to the server only or the printer does not contain the job monitoring MIB agent. It is recommended that implementations place the SNMP agent as close as possible to the processing of the print job. This MIB applies to printers with and without spooling capabilities. This MIB is designed to be compatible with most current commonly-used job submission protocols. In most environments that support high function job submission/job control protocols, like ISO DPA [iso-dpa], those protocols would be used to monitor and manage print jobs rather than using the Job Monitoring MIB.
作业监控MIB拟由打印机内的代理或距离打印机最近的第一台服务器实现，其中打印机仅直接连接到服务器，或者打印机不包含作业监控MIB代理。建议实施时将SNMP代理尽可能靠近打印作业的处理。此MIB适用于具有和不具有后台打印功能的打印机。此MIB旨在与当前最常用的作业提交协议兼容。在大多数支持高功能作业提交/作业控制协议的环境中，如ISO DPA[ISO DPA]，这些协议将用于监视和管理打印作业，而不是使用作业监视MIB。
The Job Monitoring MIB consists of a General Group, a Job Submission ID Group, a Job Group, and an Attribute Group. Each group is a table. All accessible objects are read-only. The General Group contains general information that applies to all jobs in a job set. The Job Submission ID table maps the job submission ID that the client uses to identify a job to the jmJobIndex that the Job Monitoring Agent uses to identify jobs in the Job and Attribute tables. The Job table contains the MANDATORY integer job state and status objects. The Attribute table consists of multiple entries per job that specify (1) job and document identification and parameters, (2) requested resources, and (3) consumed resources during and after job processing/printing. A larger number of job attributes are defined as textual conventions that an agent SHALL return if the server or device implements the functionality so represented and the agent has access to the information.
作业监视MIB由常规组、作业提交ID组、作业组和属性组组成。每组是一张桌子。所有可访问对象都是只读的。“常规”组包含适用于作业集中所有作业的常规信息。作业提交ID表将客户端用于标识作业的作业提交ID映射到作业监视代理用于标识作业和属性表中作业的jmJobIndex。作业表包含必需的整数作业状态和状态对象。属性表由每个作业的多个条目组成，这些条目指定（1）作业和文档标识和参数，（2）请求的资源，以及（3）作业处理/打印期间和之后消耗的资源。大量作业属性被定义为文本约定，如果服务器或设备实现了所表示的功能，并且代理可以访问信息，则代理应返回这些文本约定。
The job MIB is intended to provide the following information for the indicated Role Models in the Printer MIB [print-mib] (Appendix D - Roles of Users).
作业MIB旨在为打印机MIB[打印MIB]（附录D-用户角色）中指定的角色模型提供以下信息。
User:
用户：
Provide the ability to identify the least busy printer. The user will be able to determine the number and size of jobs waiting for each printer. No attempt is made to actually predict the length of time that jobs will take.
提供识别最忙打印机的功能。用户将能够确定等待每台打印机的作业数量和大小。没有人试图实际预测工作需要多长时间。
Provide the ability to identify the current status of the user's job (user queries).
提供识别用户作业当前状态的能力（用户查询）。
Provide a timely indication that the job has completed and where it can be found.
及时提供作业已完成以及可在何处找到的指示。
Provide error and diagnostic information for jobs that did not successfully complete.
为未成功完成的作业提供错误和诊断信息。
Operator:
接线员：
Provide a presentation of the state of all the jobs in the print system.
显示打印系统中所有作业的状态。
Provide the ability to identify the user that submitted the print job.
提供识别提交打印作业的用户的功能。
Provide the ability to identify the resources required by each job.
提供识别每项工作所需资源的能力。
Provide the ability to define which physical printers are candidates for the print job.
提供定义打印作业的候选物理打印机的功能。
Provide some idea of how long each job will take. However, exact estimates of time to process a job is not being attempted. Instead, objects are included that allow the operator to be able to make gross estimates.
提供一些关于每项工作需要多长时间的想法。但是，没有尝试准确估计处理作业的时间。相反，包含的对象允许操作员进行总体估计。
Capacity Planner:
容量规划师：
Provide the ability to determine printer utilization as a function of time.
提供根据时间确定打印机利用率的功能。
Provide the ability to determine how long jobs wait before starting to print.
提供确定作业在开始打印前等待多长时间的功能。
Accountant:
会计：
Provide information to allow the creation of a record of resources consumed and printer usage data for charging users or groups for resources consumed.
提供信息以允许创建已消耗资源的记录和打印机使用数据，以便向用户或组收取已消耗资源的费用。
Provide information to allow the prediction of consumable usage and resource need.
提供信息，以便预测消耗品使用和资源需求。
The MIB supports printers that can contain more than one job at a time, but still be usable for low end printers that only contain a single job at a time. In particular, the MIB supports the needs of Windows and other PC environments for managing low-end direct-connect (serial or parallel) and networked devices without unnecessary overhead or complexity, while also providing for higher end systems and devices.
MIB支持一次可包含多个作业的打印机，但仍可用于一次仅包含单个作业的低端打印机。特别是，MIB支持Windows和其他PC环境管理低端直接连接（串行或并行）和网络设备的需要，而不需要不必要的开销或复杂性，同时也为高端系统和设备提供支持。
The Job Monitoring MIB is designed for the following types of monitoring applications:
作业监视MIB设计用于以下类型的监视应用程序：
1. Monitor a single job starting when the job is submitted and ending a defined period after the job completes. The Job Submission ID table provides the map to find the specific job to be monitored.
1. 监视单个作业，从提交作业时开始，到作业完成后的定义时间段结束。作业提交ID表提供了查找要监视的特定作业的映射。
2. Monitor all 'active' jobs in a queue, which this specification generalizes to a "job set". End users may use such a program when selecting a least busy printer, so the MIB is designed for such a program to start up quickly and find the information needed quickly without having to read
2. 监视队列中的所有“活动”作业，本规范将其概括为“作业集”。最终用户在选择最不繁忙的打印机时可能会使用这样的程序，因此MIB是为这样一个程序设计的，可以快速启动并快速找到所需的信息，而无需阅读
all (completed) jobs in order to find the active jobs. System operators may also use such a program, in which case it would be running for a long period of time and may also be interested in the jobs that have completed. Finally such a program may be used to provide an enhanced console and logging capability.
查找活动工单所需的所有（已完成）工单。系统操作员也可以使用此类程序，在这种情况下，该程序将运行很长一段时间，并且可能对已完成的作业感兴趣。最后，这种程序可用于提供增强的控制台和日志记录功能。
3. Collect resource usage for accounting or system utilization purposes that copy the completed job statistics to an accounting system. It is recognized that depending on accounting programs to copy MIB data during the job-retention period is somewhat unreliable, since the accounting program may not be running (or may have crashed). Such a program is also expected to keep a shadow copy of the entire Job Attribute table including completed, canceled, and aborted jobs which the program updates on each polling cycle. Such a program polls at the rate of the persistence of the Attribute table. The design is not optimized to help such an application determine which jobs are completed, canceled, or aborted. Instead, the application SHOULD query each job that the application's shadow copy shows was not complete, canceled, or aborted at the previous poll cycle to see if it is now complete or canceled, plus any new jobs that have been submitted.
3. 收集资源使用情况，用于将已完成的作业统计信息复制到会计系统的会计或系统利用率目的。众所周知，在作业保留期间依靠记帐程序复制MIB数据有些不可靠，因为记帐程序可能未运行（或可能已崩溃）。这样的程序还应保留整个作业属性表的卷影副本，包括程序在每个轮询周期更新的已完成、取消和中止的作业。这样的程序以属性表的持久性速率进行轮询。该设计未优化以帮助此类应用程序确定哪些作业已完成、取消或中止。相反，应用程序应该查询应用程序的卷影副本显示的在上一个轮询周期未完成、已取消或已中止的每个作业，以查看它现在是否已完成或已取消，以及已提交的任何新作业。
The MIB provides a set of objects that represent a compatible subset of job and document attributes of the ISO DPA standard [iso-dpa] and the Internet Printing Protocol (IPP) [ipp-model], so that coherence is maintained between these two protocols and the information presented to end users and system operators by monitoring applications. However, the job monitoring MIB is intended to be used with printers that implement other job submitting and management protocols, such as IEEE 1284.1 (TIPSI) [tipsi], as well as with ones that do implement ISO DPA. Thus the job monitoring MIB does not require implementation of either the ISO DPA or IPP protocols.
MIB提供了一组对象，这些对象表示ISO DPA标准[ISO DPA]和Internet打印协议（IPP）[IPP模型]的作业和文档属性的兼容子集，以便在这两个协议以及通过监控应用程序向最终用户和系统操作员提供的信息之间保持一致性。然而，作业监控MIB旨在与实现其他作业提交和管理协议（如IEEE 1284.1（TIPSI）[TIPSI]）的打印机以及实现ISO DPA的打印机一起使用。因此，作业监控MIB不需要实现ISO DPA或IPP协议。
The MIB is designed so that an additional MIB(s) can be specified in the future for monitoring multi-function (scan, FAX, copy) jobs as an augmentation to this MIB.
MIB的设计使得将来可以指定额外的MIB来监视多功能（扫描、传真、复制）作业，作为对该MIB的扩充。
2 Terminology and Job Model
2术语和工作模式
This section defines the terms that are used in this specification and the general model for jobs in alphabetical order.
本节按字母顺序定义本规范中使用的术语和作业的通用模型。
NOTE - Existing systems use conflicting terms, so these terms are drawn from the ISO 10175 Document Printing Application (DPA) standard [iso-dpa]. For example, PostScript systems use the term session for what is called a job in this specification and the term job to mean what is called a document in this specification.
注-现有系统使用冲突术语，因此这些术语取自ISO 10175文档打印应用程序（DPA）标准[ISO DPA]。例如，PostScript系统使用术语session表示本规范中的作业，术语job表示本规范中的文档。
Accounting Application: The SNMP management application that copies job information to some more permanent medium so that another application can perform accounting on the data for Accountants, Asset Managers, and Capacity Planners use.
记帐应用程序：SNMP管理应用程序，它将作业信息复制到更永久的介质，以便另一个应用程序可以对会计、资产经理和容量计划人员使用的数据执行记帐。
Agent: The network entity that accepts SNMP requests from a monitor or accounting application and provides access to the instrumentation for managing jobs modeled by the management objects defined in the Job Monitoring MIB module for a server or a device.
代理：接受来自监视器或记帐应用程序的SNMP请求并提供对仪器的访问的网络实体，用于管理由服务器或设备的作业监视MIB模块中定义的管理对象建模的作业。
Attribute: A name, value-pair that specifies a job or document instruction, a status, or a condition of a job or a document that has been submitted to a server or device. A particular attribute NEED NOT be present in each job instance. In other words, attributes are present in a job instance only when there is a need to express the value, either because (1) the client supplied a value in the job submission protocol, (2) the document data contained an embedded attribute, or (3) the server or device supplied a default value. An agent MAY represent an attribute as an entry (row) in the Attribute table in this MIB in which entries are present only when necessary. Attributes are identified in this MIB by an enum.
属性：一个名称、值对，用于指定已提交到服务器或设备的作业或文档指令、状态或条件。每个作业实例中不需要存在特定属性。换句话说，只有当需要表示值时，属性才会出现在作业实例中，因为（1）客户端在作业提交协议中提供了值，（2）文档数据包含嵌入属性，或者（3）服务器或设备提供了默认值。代理可以将属性表示为此MIB中属性表中的条目（行），其中只有在必要时才存在条目。属性在此MIB中由枚举标识。
Client: The network entity that end users use to submit jobs to spoolers, servers, or printers and other devices, depending on the configuration, using any job submission protocol over a serial or parallel port to a directly-connected device or over the network to a networked-connected device.
客户端：最终用户使用的网络实体，根据配置，通过串行或并行端口将作业提交到直接连接的设备，或通过网络将作业提交到网络连接的设备，将作业提交到后台处理程序、服务器或打印机和其他设备。
Device: A hardware entity that (1) interfaces to humans, such as a device that produces marks on paper or scans marks on paper to produce an electronic representation, (2) accesses digital media, such as CD-ROMs, or (3) interfaces electronically to another device, such as sends FAX data to another FAX device.
设备：一种硬件实体，它（1）与人接口，如在纸上产生标记或扫描纸上标记以产生电子表示的设备，（2）访问数字媒体，如CD-ROM，或（3）以电子方式与另一设备接口，如向另一传真设备发送传真数据。
Document: A sub-section within a job that contains print data and document instructions that apply to just the document.
文档：作业中的一个子部分，包含仅适用于文档的打印数据和文档说明。
Document Instruction: An instruction specifying how to process the document. Document instructions MAY be passed in the job submission protocol separate from the actual document data, or MAY be embedded in the document data or a combination, depending on the job submission protocol and implementation.
文档说明：指定如何处理文档的说明。文档指令可以在作业提交协议中与实际文档数据分开传递，也可以嵌入到文档数据或其组合中，具体取决于作业提交协议和实现。
End User: A user that uses a client to submit a print job. See "user".
最终用户：使用客户端提交打印作业的用户。见“用户”。
Impression: For a print job, an impression is the passage of the entire side of a sheet by the marker, whether or not any marks are made and independent of the number of passes that the side makes past the marker. Thus a four pass color process counts as a single impression, as does highlight color. Impression counters count all kinds: monochrome, highlight color, and full process color, while full color counters only count full color impressions, and high light color counters only count high light color impressions.
印模：对于打印作业，印模是纸张的整个侧面通过标记的过程，无论是否有任何标记，并且与侧面通过标记的次数无关。因此，一个四遍的色彩处理可以算作一个单一的印象，就像突出显示颜色一样。印象计数器统计所有种类：单色、高光颜色和全过程颜色，而全色计数器仅统计全色印象，高光颜色计数器仅统计高光颜色印象。
One-sided processing involves one impression per sheet. Two-sided processing involves two impressions per sheet. If a two-sided document has an odd number of pages, the last sheet still counts as two impressions, if that sheet makes two passes through the marker or the marker marks on both sides of a sheet in a single pass. Two-up printing is the placement of two logical pages on one side of a sheet and so is still a single impression. See "page" and "sheet".
单面加工涉及每张纸的一个印模。双面处理涉及每张纸的两个印模。如果双面文档的页数为奇数，则最后一页仍将被视为两个印模，如果该页在一次印模中两次穿过标记或在一张纸的两面上进行标记。双面印刷是在一张纸的一侧放置两个逻辑页面，因此仍然是一个印模。参见“页面”和“页面”。
NOTE - Since impressions include blank sides, it is suggested that accounting application implementers consider charging for sheets, rather than impressions, possibly using the value of the sides attribute to select different charges for one-sided versus two-sided printing, since some users may think that impressions don't include blank sides.
注意-由于印象包括空白侧，建议会计应用实施者考虑收取单张，而不是印象，可能使用边属性的值来选择单侧和双面打印的不同收费，因为一些用户可能认为印象不包括空白侧。
Internal Collation: The production of the sheets for each document copy performed within the printing device by making multiple passes over either the source or an intermediate representation of the document.
内部校对：在打印设备内，通过多次传递文件的源或中间表示形式，为每个文件副本制作纸张。
Job: A unit of work whose results are expected together without interjection of unrelated results. A job contains one or more documents.
工作：一种工作单位，其结果是预期在一起的，没有不相关的结果感叹。作业包含一个或多个文档。
Job Accounting: The activity of a management application of accessing the MIB and recording what happens to the job during and after the processing of the job.
作业记帐：管理应用程序访问MIB并记录作业处理期间和之后发生的情况的活动。
Job Instruction: An instruction specifying how, when, or where the job is to be processed. Job instructions MAY be passed in the job submission protocol or MAY be embedded in the document data or a combination depending on the job submission protocol and implementation.
作业指令：指定如何、何时或在何处处理作业的指令。作业指令可以在作业提交协议中传递，也可以嵌入到文档数据中，或者根据作业提交协议和实现的组合。
Job Monitoring (using SNMP): The activity of a management application of accessing the MIB and (1) identifying jobs in the job tables being processed by the server, printer or other devices, and (2) displaying information to the user about the processing of the job.
作业监控（使用SNMP）：管理应用程序访问MIB和（1）识别服务器、打印机或其他设备正在处理的作业表中的作业，以及（2）向用户显示作业处理信息的活动。
Job Monitoring Application: The SNMP management application that End Users, and System Operators use to monitor jobs using SNMP. A monitor MAY be either a separate application or MAY be part of the client that also submits jobs. See "monitor".
作业监控应用程序：最终用户和系统操作员使用SNMP监控作业的SNMP管理应用程序。监视器可以是单独的应用程序，也可以是同时提交作业的客户端的一部分。见“监视器”。
Job Set: A group of jobs that are queued and scheduled together according to a specified scheduling algorithm for a specified device or set of devices. For implementations that embed the SNMP agent in the device, the MIB job set normally represents all the jobs known to the device, so that the implementation only implements a single job set. If the SNMP agent is implemented in a server that controls one or more devices, each MIB job set represents a job queue for (1) a specific device or (2) set of devices, if the server uses a single queue to load balance between several devices. Each job set is disjoint; no job SHALL be represented in more than one MIB job set.
作业集：根据指定设备或设备集的指定调度算法一起排队和调度的一组作业。对于在设备中嵌入SNMP代理的实现，MIB作业集通常表示设备已知的所有作业，因此实现仅实现单个作业集。如果SNMP代理在控制一个或多个设备的服务器中实现，则每个MIB作业集表示（1）特定设备或（2）设备集的作业队列（如果服务器使用单个队列在多个设备之间进行负载平衡）。每个作业集是不相交的；不得在多个MIB作业集中表示任何作业。
Monitor: Short for Job Monitoring Application.
监视器：作业监视应用程序的缩写。
Page: A page is a logical division of the original source document. Number up is the imposition of more than one page on a single side of a sheet. See "impression" and "sheet" and "two-up".
页面：页面是原始源文档的逻辑划分。数字向上是在一张纸的单面上强加一页以上的内容。请参阅“印象”和“工作表”以及“两个向上”。
Proxy: An agent that acts as a concentrator for one or more other agents by accepting SNMP operations on the behalf of one or more other agents, forwarding them on to those other agents, gathering responses from those other agents and returning them to the original requesting monitor.
代理：一种代理，作为一个或多个其他代理的集中器，代表一个或多个其他代理接受SNMP操作，将其转发到这些其他代理，收集这些其他代理的响应，并将其返回到原始请求监视器。
Queuing: The act of a device or server of ordering (queuing) the jobs for the purposes of scheduling the jobs to be processed.
排队：设备或服务器对作业进行排序（排队）的行为，目的是安排要处理的作业。
Printer: A device that puts marks on media.
打印机：在介质上作标记的设备。
Server: A network entity that accepts jobs from clients and in turn submits the jobs to printers and other devices that may be directly connected to the server via a serial or parallel port or may be on the network. A server MAY be a printer supervisor control program, or a print spooler.
服务器：一种网络实体，它接受来自客户端的作业，然后将作业提交给打印机和其他设备，这些设备可以通过串行或并行端口直接连接到服务器，也可以在网络上。服务器可以是打印机监控程序或后台打印程序。
Sheet: A sheet is a single instance of a medium, whether printing on one or both sides of the medium. See "impression" and "page".
纸张：纸张是介质的单个实例，无论是在介质的一面还是两面打印。请参阅“印象”和“页面”。
SNMP Information Object: A name, value-pair that specifies an action, a status, or a condition in an SNMP MIB. Objects are identified in SNMP by an OBJECT IDENTIFIER.
SNMP信息对象：指定SNMP MIB中的操作、状态或条件的名称、值对。对象在SNMP中由对象标识符标识。
Spooler: A server that accepts jobs, spools the data, and decides when and on which printer to print the job. A spooler is a client to a printer or a printer supervisor, depending on implementation.
后台打印程序：接受作业、后台打印数据并决定何时在哪台打印机上打印作业的服务器。后台打印程序是打印机的客户端或打印机管理员，具体取决于实现。
Spooling: The act of a device or server of (1) accepting jobs and (2) writing the job's attributes and document data on to secondary storage.
假脱机：设备或服务器（1）接受作业和（2）将作业属性和文档数据写入辅助存储器的行为。
Stacked: When a media sheet is placed in an output bin of a device.
堆叠：将介质纸放置在设备的输出箱中时。
Supervisor: A server that contains a control program that controls a printer or other device. A supervisor is a client to the printer or other device.
管理器：包含控制打印机或其他设备的控制程序的服务器。主管是打印机或其他设备的客户端。
System Operator: A user that uses a monitor to monitor the system and carries out tasks to keep the system running.
系统操作员：使用监视器监视系统并执行任务以保持系统运行的用户。
System Administrator: A user that specifies policy for the system.
系统管理员：为系统指定策略的用户。
Two-up: The placement of two pages on one side of a sheet so that each side or impressions counts as two pages. See "page" and "sheet".
二向上：把两页纸放在一张纸的一面上，使每一面或印痕计为两页。参见“页面”和“页面”。
User: A person that uses a client or a monitor. See "end user".
用户：使用客户端或监视器的人。见“最终用户”。
This section enumerates the three configurations in which the Job Monitoring MIB is intended to be used. To simplify the pictures, the devices are shown as printers. See section 1.1 entitled "Types of Information in the MIB".
本节列举了作业监视MIB打算使用的三种配置。为了简化图片，设备显示为打印机。参见第1.1节“MIB中的信息类型”。
The diagram in the Printer MIB [print-mib] entitled: "One Printer's View of the Network" is assumed for this MIB as well. Please refer to that diagram to aid in understanding the following system configurations.
打印机MIB[print MIB]中题为“一台打印机的网络视图”的图表也适用于此MIB。请参考该图以帮助理解以下系统配置。
In the client-printer configuration 1, the client(s) submit jobs directly to the printer, either by some direct connect, or by network connection.
在客户端打印机配置1中，客户端通过某种直接连接或网络连接直接向打印机提交作业。
The job submitting client and/or monitoring application monitor jobs by communicating directly with an agent that is part of the printer. The agent in the printer SHALL keep the job in the Job Monitoring MIB as long as the job is in the printer, plus a defined time period after the job enters the completed state in which accounting programs can copy out the accounting data from the Job Monitoring MIB.
作业提交客户端和/或监控应用程序通过直接与作为打印机一部分的代理通信来监控作业。打印机中的代理应将作业保留在作业监控MIB中，只要作业在打印机中，加上作业进入完成状态后的定义时间段，在该状态下，会计程序可以从作业监控MIB中复制会计数据。
all end-user ######## SNMP query
+-------+ +--------+ ---- job submission
|monitor| | client |
+---#---+ +--#--+--+
# # |
# ############ |
# # |
+==+===#=#=+==+ |
| | agent | | |
| +-------+ | |
| PRINTER <--------+
| | Print Job Delivery Channel
| |
+=============+
all end-user ######## SNMP query
+-------+ +--------+ ---- job submission
|monitor| | client |
+---#---+ +--#--+--+
# # |
# ############ |
# # |
+==+===#=#=+==+ |
| | agent | | |
| +-------+ | |
| PRINTER <--------+
| | Print Job Delivery Channel
| |
+=============+
Figure 2-1 - Configuration 1 - client-printer - agent in the printer
Figure 2-1 - Configuration 1 - client-printer - agent in the printer
The Job Monitoring MIB is designed to support the following relationships (not shown in Figure 2-1): 1. Multiple clients MAY submit jobs to a printer. 2. Multiple clients MAY monitor a printer. 3. Multiple monitors MAY monitor a printer. 4. A client MAY submit jobs to multiple printers. 5. A monitor MAY monitor multiple printers.
作业监控MIB旨在支持以下关系（图2-1中未显示）：1。多个客户端可以向打印机提交作业。2.多个客户端可以监视一台打印机。3.多个监视器可以监视一台打印机。4.客户端可以向多个打印机提交作业。5.监视器可以监视多台打印机。
In the client-server-printer configuration 2, the client(s) submit jobs to an intermediate server by some network connection, not directly to the printer. While configuration 2 is included, the design center for this MIB is configurations 1 and 3.
在客户机-服务器-打印机配置2中，客户机通过某种网络连接将作业提交到中间服务器，而不是直接提交到打印机。虽然包含配置2，但此MIB的设计中心是配置1和3。
The job submitting client and/or monitoring application monitor jobs by communicating directly with:
作业提交客户端和/或监控应用程序通过直接与以下对象通信来监控作业：
A Job Monitoring MIB agent that is part of the server (or a front for the server)
作为服务器（或服务器前端）一部分的作业监视MIB代理
There is no SNMP Job Monitoring MIB agent in the printer in configuration 2, at least that the client or monitor are aware. In this configuration, the agent SHALL return the current values of the objects in the Job Monitoring MIB both for jobs the server keeps and jobs that the server has submitted to the printer. The Job Monitoring MIB agent obtains the required information from the printer by a method that is beyond the scope of this document. The agent in the server SHALL keep the job in the Job Monitoring MIB in the server as long as the job is in the printer, plus a defined time period after the job enters the completed state in which accounting programs can copy out the accounting data from the Job Monitoring MIB.
配置2中的打印机中没有SNMP作业监视MIB代理，至少客户端或监视器知道。在此配置中，对于服务器保留的作业和服务器提交给打印机的作业，代理应返回作业监视MIB中对象的当前值。作业监视MIB代理通过超出本文档范围的方法从打印机获取所需信息。只要作业在打印机中，服务器中的代理就应将作业保留在服务器中的作业监控MIB中，加上作业进入完成状态后的定义时间段，在此期间，会计程序可以从作业监控MIB中复制会计数据。
all end-user
+-------+ +----------+
|monitor| | client | ######## SNMP query
+---+---# +---#----+-+ **** non-SNMP cntrl
# # | ---- job submission
# # |
# # |
#=====#=+==v==+
| agent | |
+-------+ |
| server |
+----+-----+--+
control * |
********** |
* |
+========v====+ |
| | |
| | |
| PRINTER <---------+
| | Print Job Delivery Channel
| |
+=============+
all end-user
+-------+ +----------+
|monitor| | client | ######## SNMP query
+---+---# +---#----+-+ **** non-SNMP cntrl
# # | ---- job submission
# # |
# # |
#=====#=+==v==+
| agent | |
+-------+ |
| server |
+----+-----+--+
control * |
********** |
* |
+========v====+ |
| | |
| | |
| PRINTER <---------+
| | Print Job Delivery Channel
| |
+=============+
Figure 2-2 - Configuration 2 - client-server-printer - agent in the server
图2-2-配置2-客户端-服务器打印机-服务器中的代理
The Job Monitoring MIB is designed to support the following relationships (not shown in Figure 2-2): 1. Multiple clients MAY submit jobs to a server. 2. Multiple clients MAY monitor a server. 3. Multiple monitors MAY monitor a server. 4. A client MAY submit jobs to multiple servers. 5. A monitor MAY monitor multiple servers. 6. Multiple servers MAY submit jobs to a printer. 7. Multiple servers MAY control a printer.
作业监控MIB旨在支持以下关系（图2-2中未显示）：1。多个客户端可以向服务器提交作业。2.多个客户端可以监视一台服务器。3.多个监视器可以监视一台服务器。4.客户端可以向多个服务器提交作业。5.一个监视器可以监视多个服务器。6.多个服务器可以向打印机提交作业。7.多台服务器可以控制一台打印机。
2.1.3 Configuration 3 - client-server-printer - client monitors printer agent and server
2.1.3 配置3-客户端服务器打印机-客户端监视打印机代理和服务器
In the client-server-printer configuration 3, the client(s) submit jobs to an intermediate server by some network connection, not directly to the printer. That server does not contain a Job Monitoring MIB agent.
在客户机-服务器-打印机配置3中，客户机通过某种网络连接将作业提交到中间服务器，而不是直接提交到打印机。该服务器不包含作业监视MIB代理。
The job submitting client and/or monitoring application monitor jobs by communicating directly with:
作业提交客户端和/或监控应用程序通过直接与以下对象通信来监控作业：
1. The server using some undefined protocol to monitor jobs in the server (that does not contain the Job Monitoring MIB) AND
1. 服务器使用一些未定义的协议来监视服务器中的作业（不包含作业监视MIB）和
2. A Job Monitoring MIB agent that is part of the printer to monitor jobs after the server passes the jobs to the printer.
2. 作业监视MIB代理，是打印机的一部分，用于在服务器将作业传递给打印机后监视作业。
In such configurations, the server deletes its copy of the job from the server after submitting the job to the printer usually almost immediately (before the job does much processing, if any).
在这种配置中，服务器在将作业提交到打印机后（通常在作业进行大量处理（如果有的话）之前）从服务器上删除其作业副本。
In configuration 3, the agent (in the printer) SHALL keep the values of the objects in the Job Monitoring MIB that the agent implements updated for a job that the server has submitted to the printer. The agent SHALL obtain information about the jobs submitted to the printer from the server (either in the job submission protocol, in the document data, or by direct query of the server), in order to populate some of the objects the Job Monitoring MIB in the printer. The agent in the printer SHALL keep the job in the Job Monitoring MIB as long as the job is in the Printer, and longer in order to implement the completed state in which monitoring programs can copy out the accounting data from the Job Monitoring MIB.
在配置3中，代理（打印机中）应保持代理为服务器提交给打印机的作业实现的作业监控MIB中对象的值更新。代理应从服务器（作业提交协议、文档数据或通过服务器直接查询）获取提交给打印机的作业信息，以便在打印机中填充作业监控MIB中的某些对象。打印机中的代理应将作业保留在作业监控MIB中，只要作业在打印机中，时间更长，以便实现监控程序可以从作业监控MIB中复制记帐数据的完成状态。
all end-user
+-------+ +----------+
|monitor| | client | ######## SNMP query
+---+---* +---*----+-+ **** non-SNMP query
# * * | ---- job submission
# * * |
# * * |
# *=====v====v==+
# | |
# | server |
# | |
# +----#-----+--+
# optional# |
# ########## |
# # |
+==+=v===v=+==+ |
| | agent | | |
| +-------+ | |
| PRINTER <---------+
| | Print Job Delivery Channel
| |
+=============+
all end-user
+-------+ +----------+
|monitor| | client | ######## SNMP query
+---+---* +---*----+-+ **** non-SNMP query
# * * | ---- job submission
# * * |
# * * |
# *=====v====v==+
# | |
# | server |
# | |
# +----#-----+--+
# optional# |
# ########## |
# # |
+==+=v===v=+==+ |
| | agent | | |
| +-------+ | |
| PRINTER <---------+
| | Print Job Delivery Channel
| |
+=============+
Figure 2-3 - Configuration 3 - client-server-printer - client monitors printer agent and server
图2-3-配置3-客户端服务器打印机-客户端监视器打印机代理和服务器
The Job Monitoring MIB is designed to support the following relationships (not shown in Figure 2-3): 1. Multiple clients MAY submit jobs to a server. 2. Multiple clients MAY monitor a server. 3. Multiple monitors MAY monitor a server. 4. A client MAY submit jobs to multiple servers. 5. A monitor MAY monitor multiple servers. 6. Multiple servers MAY submit jobs to a printer. 7. Multiple servers MAY control a printer.
作业监控MIB旨在支持以下关系（图2-3中未显示）：1。多个客户端可以向服务器提交作业。2.多个客户端可以监视一台服务器。3.多个监视器可以监视一台服务器。4.客户端可以向多个服务器提交作业。5.一个监视器可以监视多个服务器。6.多个服务器可以向打印机提交作业。7.多台服务器可以控制一台打印机。
3 Managed Object Usage
3托管对象的使用
This section describes the usage of the objects in the MIB.
本节介绍MIB中对象的用法。
In order to achieve interoperability between job monitoring applications and job monitoring agents, this specification includes the conformance requirements for both monitoring applications and agents.
为了实现作业监控应用程序和作业监控代理之间的互操作性，本规范包括监控应用程序和代理的一致性要求。
This specification uses the verbs: "SHALL", "SHOULD", "MAY", and "NEED NOT" to specify conformance requirements according to RFC 2119 [RFC2119] as follows:
根据RFC 2119[RFC2119]，本规范使用动词“应”、“应”、“可”和“无需”规定符合性要求，如下所示：
"SHALL": indicates an action that the subject of the sentence must implement in order to claim conformance to this specification
“应”：表示句子主体必须实施的行动，以声明符合本规范
"MAY": indicates an action that the subject of the sentence does not have to implement in order to claim conformance to this specification, in other words that action is an implementation option
“可能”：表示句子主体不必实施的行动，以声明符合本规范，换句话说，行动是一种实施选项
"NEED NOT": indicates an action that the subject of the sentence does not have to implement in order to claim conformance to this specification. The verb "NEED NOT" is used instead of "may not", since "may not" sounds like a prohibition.
“无需”：表示句子主体不必执行的动作，以声明符合本规范。动词“NEED NOT”代替“may NOT”，因为“may NOT”听起来像是禁止。
"SHOULD": indicates an action that is recommended for the subject of the sentence to implement, but is not required, in order to claim conformance to this specification.
“应”：表示建议句子主体实施的行动，但并非要求，以声明符合本规范。
A conforming agent:
合格代理人：
1. SHALL implement all MANDATORY groups in this specification.
1. 应实施本规范中的所有强制性分组。
2. SHALL implement any attributes if (1) the server or device supports the functionality represented by the attribute and (2) the information is available to the agent.
2. 如果（1）服务器或设备支持属性表示的功能，并且（2）代理可以使用信息，则应实现任何属性。
3. SHOULD implement both forms of an attribute if it implements an attribute that permits a choice of INTEGER and OCTET STRING forms, since implementing both forms may help management applications by giving them a choice of representations, since the representation are equivalent. See the JmAttributeTypeTC textual-convention.
3. 如果实现了允许选择整数和八位字符串形式的属性，则应实现属性的两种形式，因为实现这两种形式可能有助于管理应用程序，因为它们可以选择表示形式，因为表示形式是等效的。请参见JmAttributeTypeTC文本约定。
NOTE - This MIB, like the Printer MIB, is written following the subset of SMIv2 that can be supported by SMIv1 and SNMPv1 implementations.
注意-此MIB与打印机MIB一样，是按照SMIv1和SNMPv1实现支持的SMIv2子集编写的。
The Job Monitoring MIB agent SHALL implement all objects in the System Group of MIB-II [mib-II], whether the Printer MIB [print-mib] is implemented or not.
作业监控MIB代理应实现MIB-II[MIB II]系统组中的所有对象，无论是否实现打印机MIB[print MIB]。
The Job Monitoring MIB agent SHALL implement all objects in the Interfaces Group of MIB-II [mib-II], whether the Printer MIB [print-mib] is implemented or not.
作业监控MIB代理应实现MIB-II[MIB II]接口组中的所有对象，无论是否实现打印机MIB[print MIB]。
If the agent is providing access to a device that is a printer, the agent SHALL implement all of the MANDATORY objects in the Printer MIB [print-mib] and all the objects in other MIBs that conformance to the Printer MIB requires, such as the Host Resources MIB [hr-mib]. If the agent is providing access to a server that controls one or more direct-connect or networked printers, the agent NEED NOT implement the Printer MIB and NEED NOT implement the Host Resources MIB.
如果代理提供对打印机设备的访问，则代理应实现打印机MIB[print MIB]中的所有强制对象以及符合打印机MIB要求的其他MIB中的所有对象，如主机资源MIB[hr MIB]。如果代理提供对控制一台或多台直连或联网打印机的服务器的访问，则代理不需要实现打印机MIB，也不需要实现主机资源MIB。
A conforming job monitoring application:
符合要求的作业监控应用程序：
1. SHALL accept the full syntactic range for all objects in all MANDATORY groups and all MANDATORY attributes that are required to be implemented by an agent according to Section 3.1.2 and SHALL either present them to the user or ignore them.
1. 应接受所有强制组中所有对象的完整语法范围，以及根据第3.1.2节要求由代理实现的所有强制属性，并应将其呈现给用户或忽略它们。
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 the PWG 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.7 entitled "IANA and PWG Registration Considerations".
2. 应接受所有属性的完整语法范围，包括本规范中规定的枚举值和位值，以及可能向PWG注册的其他属性，并应将其呈现给用户或忽略它们。特别是，当接收任何标准或注册的枚举或位值时，合格的作业监控应用程序不得出现故障。参见第3.7节“IANA和PWG注册注意事项”。
3. SHALL NOT fail when operating with agents that materialize attributes after the job has been submitted, as opposed to when the job is submitted.
3. 与提交作业时不同，提交作业后使用具体化属性的代理操作时，不应失败。
4. SHALL, if it supports a time attribute, accept either form of the time attribute, since agents are free to implement either time form.
4. 若支持时间属性，则应接受任一形式的时间属性，因为代理可以自由实现任一形式的时间。
The jmJobTable and jmAttributeTable contain objects and attributes, respectively, for each job in a job set. These first two indexes are: 1. jmGeneralJobSetIndex - which job set 2. jmJobIndex - which job in the job set
jmJobTable和jmAttributeTable分别包含作业集中每个作业的对象和属性。前两个指标是:1。jmGeneralJobSetIndex-哪个作业集为2。jmJobIndex-作业集中的哪个作业
In order for a monitoring application to quickly find that active jobs (jobs in the pending, processing, or processingStopped states), the MIB contains two indexes:
为了让监控应用程序快速找到活动作业（处于挂起、处理或处理停止状态的作业），MIB包含两个索引：
1. jmGeneralOldestActiveJobIndex - the index of the active job that has been in the tables the longest.
1. JMGeneralOldStactiveJobIndex—表中最长的活动作业索引。
2. jmGeneralNewestActiveJobIndex - the index of the active job that has been most recently added to the tables.
2. jmGeneralNewestActiveJobIndex—最近添加到表中的活动作业的索引。
The agent SHALL assign the next incremental value of jmJobIndex to the job, when a new job is accepted by the server or device to which the agent is providing access. If the incremented value of jmJobIndex would exceed the implementation-defined maximum value for jmJobIndex, the agent SHALL 'wrap' back to 1. An agent uses the resulting value of jmJobIndex for storing information in the jmJobTable and the jmAttributeTable about the job.
当代理提供访问权限的服务器或设备接受新作业时，代理应将jmJobIndex的下一个增量值分配给作业。如果jmJobIndex的增量值将超过实现为jmJobIndex定义的最大值，则代理应“包装”回1。代理使用jmJobIndex的结果值在jmJobTable和jmAttributeTable中存储有关作业的信息。
It is recommended that the largest value for jmJobIndex be much larger than the maximum number of jobs that the implementation can contain at a single time, so as to minimize the premature re-use of a jmJobIndex value for a newer job while clients retain the same ' stale' value for an older job.
建议jmJobIndex的最大值远大于实现一次可包含的最大作业数，以最大限度地减少对较新作业过早重复使用jmJobIndex值，同时客户端对较旧作业保留相同的“过时”值。
It is recommended that agents that are providing access to servers/devices that already allocate job-identifiers for jobs as integers use the same integer value for the jmJobIndex. Then management applications using this MIB and applications using other protocols will see the same job identifiers for the same jobs. Agents providing access to systems that contain jobs with a job identifier of 0 SHALL map the job identifier value 0 to a jmJobIndex value that is one higher than the highest job identifier value that any job can have on that system. Then only job 0 will have a different job-identifier value than the job's jmJobIndex value.
建议提供对已将作业标识符分配为整数的服务器/设备的访问权限的代理对jmJobIndex使用相同的整数值。然后，使用此MIB的管理应用程序和使用其他协议的应用程序将看到相同作业的相同作业标识符。提供对包含作业标识符为0的作业的系统的访问权限的代理应将作业标识符值0映射到jmJobIndex值，该值高于该系统上任何作业可以具有的最高作业标识符值。然后，只有作业0的作业标识符值与作业的jmJobIndex值不同。
NOTE - If a server or device accepts jobs using multiple job submission protocols, it may be difficult for the agent to meet the recommendation to use the job-identifier values that the server or
注意-如果服务器或设备使用多个作业提交协议接受作业，则代理可能难以满足使用服务器或设备提供的作业标识符值的建议
device assigns as the jmJobIndex value, unless the server/device assigns job-identifiers for each of its job submission protocols from the same job-identifier number space.
设备分配为jmJobIndex值，除非服务器/设备从相同的作业标识符编号空间为其每个作业提交协议分配作业标识符。
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 (though the agent SHALL assign the next incremental jmJobIndex value to the job).
每次代理提供访问权限的服务器或设备接受新作业并且该作业将处于“活动”（挂起、处理或处理停止，但不是挂起），代理都应将作业的jmJobIndex值复制到jmGeneralNewestActiveJobIndex对象。如果新作业处于“非活动”（pendingHeld状态），则代理不应更改jmGeneralNewestActiveJobIndex对象的值（尽管代理应将下一个增量jmJobIndex值分配给作业）。
When a job transitions from one of the 'active' job states (pending, processing, processingStopped) to one of the 'inactive' job states (pendingHeld, completed, canceled, or aborted), with a jmJobIndex value that matches the jmGeneralOldestActiveJobIndex object, the agent SHALL advance (or wrap) the value to the next oldest 'active' job, if any. See the JmJobStateTC textual-convention for a definition of the job states.
当作业从一个“活动”作业状态（挂起、处理、处理停止）转换为一个“非活动”作业状态（挂起、完成、取消或中止），且jmJobIndex值与JMGeneralOldStactiveJobIndex对象匹配时，代理应将该值提前（或包装）到下一个最早的“活动”作业（如果有）。有关作业状态的定义，请参阅JmJobStateTC文本约定。
Whenever a job transitions from one of the 'inactive' job states to one of the 'active' job states (from pendingHeld to pending or processing), the agent SHALL update the value of either the jmGeneralOldestActiveJobIndex or the jmGeneralNewestActiveJobIndex objects, or both, if the job's jmJobIndex value is outside the range between jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex.
每当作业从一个“非活动”作业状态转换到一个“活动”作业状态（从pendingHeld到pending或processing），代理应更新JMGeneralLDestativeJobindex或JMGeneralNewestativeJobindex对象的值，或同时更新这两个对象的值，如果作业的jmJobIndex值超出JMGeneralOldStativeJobIndex和JMGeneralNewStativeJobIndex之间的范围。
When all jobs become 'inactive', i.e., enter the pendingHeld, completed, canceled, or aborted states, the agent SHALL set the value of both the jmGeneralOldestActiveJobIndex and jmGeneralNewestActiveJobIndex objects to 0.
当所有作业变为“非活动”时，即进入pendingHeld、completed、Cancelled或aborted状态，代理应将JMGeneralOldStativeJobindex和JMGeneralNewStativeJobindex对象的值设置为0。
NOTE - Applications that wish to efficiently access all of the active jobs MAY use jmGeneralOldestActiveJobIndex value to start with the oldest active job and continue until they reach the index value equal to jmGeneralNewestActiveJobIndex, skipping over any pendingHeld, completed, canceled, or aborted jobs that might intervene.
注意-希望有效访问所有活动作业的应用程序可以使用JMGeneralNodeStativeJobIndex值从最旧的活动作业开始，然后继续，直到它们达到等于JMGeneralNewSetActiveJobIndex的索引值，跳过任何可能干预的挂起、完成、取消或中止的作业。
If an application detects that the jmGeneralNewestActiveJobIndex is smaller than jmGeneralOldestActiveJobIndex, the job index has wrapped. In this case, the application SHALL reset the index to 1 when the end of the table is reached and continue the GetNext operations to find the rest of the active jobs.
如果应用程序检测到JMGeneralNewSetActiveJobindex小于JMGeneralOldStativeJobindex，则作业索引已包装。在这种情况下，当到达表的末尾时，应用程序应将索引重置为1，并继续GetNext操作以查找其余的活动作业。
NOTE - Applications detect the end of the jmAttributeTable table when the OID returned by the GetNext operation is an OID in a different MIB. There is no object in this MIB that specifies the maximum value for the jmJobIndex supported by the implementation.
注意-当GetNext操作返回的OID是不同MIB中的OID时，应用程序会检测jmAttributeTable表的结束。此MIB中没有指定实现支持的jmJobIndex的最大值的对象。
When the server or device is power-cycled, the agent SHALL remember the next jmJobIndex value to be assigned, so that new jobs are not assigned the same jmJobIndex as recent jobs before the power cycle.
当服务器或设备通电时，代理应记住要分配的下一个jmJobIndex值，以便新作业不会被分配与通电前的最近作业相同的jmJobIndex。
Attributes are similar to information objects, except that attributes are identified by an enum, instead of an OID, so that attributes may be registered without requiring a new MIB. Also an implementation that does not have the functionality represented by the attribute can omit the attribute entirely, rather than having to return a distinguished value. The agent is free to materialize an attribute in the jmAttributeTable as soon as the agent is aware of the value of the attribute.
属性与信息对象类似，不同之处在于属性由枚举（而不是OID）标识，因此可以在不需要新MIB的情况下注册属性。另外，不具有该属性所表示的功能的实现可以完全忽略该属性，而不必返回可分辨的值。只要代理知道属性的值，代理就可以自由地具体化jmAttributeTable中的属性。
The agent materializes job attributes in a four-indexed jmAttributeTable:
代理在四个索引的jmAttributeTable中具体化作业属性：
1. jmGeneralJobSetIndex - which job set
1. jmGeneralJobSetIndex-哪个作业集
2. jmJobIndex - which job in the job set
2. jmJobIndex-作业集中的哪个作业
3. jmAttributeTypeIndex - which attribute
3. jmAttributeTypeIndex-哪个属性
4. jmAttributeInstanceIndex - which attribute instance for those attributes that can have multiple values per job.
4. jmAttributeInstanceIndex—每个作业可以有多个值的属性的哪个属性实例。
Some attributes represent information about a job, such as a file-name, a document-name, a submission-time or a completion time. Other attributes represent resources required, e.g., a medium or a colorant, etc. to process the job before the job starts processing OR to indicate the amount of the resource consumed during and after processing, e.g., pages completed or impressions completed. If both a required and a consumed value of a resource is needed, this specification assigns two separate attribute enums in the textual convention.
某些属性表示有关作业的信息，例如文件名、文档名、提交时间或完成时间。其他属性表示在作业开始处理之前处理作业或指示处理期间和之后消耗的资源量所需的资源，例如，介质或着色剂等，例如，完成的页面或完成的印象。如果同时需要资源的required值和consumered值，则本规范在文本约定中分配两个单独的属性枚举。
NOTE - The table of contents lists all the attributes in order. This order is the order of enum assignments which is the order that the SNMP GetNext operation returns attributes. Most attributes apply to all three configurations covered by this MIB specification (see
注意-目录按顺序列出了所有属性。此顺序是枚举分配的顺序，即SNMP GetNext操作返回属性的顺序。大多数属性适用于本MIB规范涵盖的所有三种配置（请参阅
section 2.1 entitled "System Configurations for the Job Monitoring MIB"). Those attributes that apply to a particular configuration are indicated as 'Configuration n:' and SHALL NOT be used with other configurations.
第2.1节“作业监控MIB的系统配置”）。适用于特定配置的属性表示为“配置n:”，不得与其他配置一起使用。
An agent SHALL implement any attribute if (1) the server or device supports the functionality represented by the attribute and (2) the information is available to the agent. The agent MAY create the attribute row in the jmAttributeTable when the information is available or MAY create the row earlier with the designated 'unknown' value appropriate for that attribute. See next section.
如果（1）服务器或设备支持该属性所表示的功能，并且（2）该信息可供代理使用，则代理应实现任何属性。当信息可用时，代理可以在jmAttributeTable中创建属性行，或者可以使用适用于该属性的指定“未知”值更早地创建该行。见下一节。
If the server or device does not implement or does not provide access to the information about an attribute, the agent SHOULD NOT create the corresponding row in the jmAttributeTable.
如果服务器或设备未实现或未提供对属性信息的访问，则代理不应在jmAttributeTable中创建相应的行。
Some attributes have a 'useful' Integer32 value, some have a 'useful' OCTET STRING value, some MAY have either or both depending on implementation, and some MUST have both. See the JmAttributeTypeTC textual convention for the specification of each attribute.
有些属性有一个“有用”的整数32值，有些属性有一个“有用”的八位字节字符串值，有些属性可能有一个或两个，具体取决于实现，有些属性必须两者都有。有关每个属性的规范，请参见JmAttributeTypeTC文本约定。
SNMP requires that if an object cannot be implemented because its values cannot be accessed, then a compliant agent SHALL return an SNMP error in SNMPv1 or an exception value in SNMPv2. However, this MIB has been designed so that 'all' objects can and SHALL be implemented by an agent, so that neither the SNMPv1 error nor the SNMPv2 exception value SHALL be generated by the agent. This MIB has also been designed so that when an agent materializes an attribute, the agent SHALL materialize a row consisting of both the jmAttributeValueAsInteger and jmAttributeValueAsOctets objects.
SNMP要求，如果由于无法访问某个对象的值而无法实现该对象，则合规代理应在SNMPv1中返回SNMP错误，或在SNMPv2中返回异常值。但是，该MIB的设计使得“所有”对象都可以并且应该由代理实现，因此代理不会生成SNMPv1错误或SNMPv2异常值。此MIB的设计还使得当代理具体化属性时，代理应具体化由jmAttributeValueAsInteger和jmAttributeValueAsOctets对象组成的行。
In general, values for objects and attributes have been chosen so that a management application will be able to determine whether a ' useful', 'unknown', or 'other' value is available. When a useful value is not available for an object, that agent SHALL return a zero-length string for octet strings, the value 'unknown(2)' for enums, a '0' value for an object that represents an index in another table, and a value '-2' for counting integers.
通常，选择对象和属性的值是为了让管理应用程序能够确定“有用”、“未知”或“其他”值是否可用。当一个对象没有可用的值时，该代理应为八位字节字符串返回零长度字符串，为枚举返回值“未知（2）”，为表示另一个表中索引的对象返回值“0”，为整数计数返回值“-2”。
Since each attribute is represented by a row consisting of both the jmAttributeValueAsInteger and jmAttributeValueAsOctets MANDATORY objects, SNMP requires that the agent SHALL always create an attribute row with both objects specified. However, for most attributes the agent SHALL return a "useful" value for one of the
由于每个属性都由一行表示，该行由jmAttributeValueAsInteger和jmAttributeValueAsOctets强制对象组成，因此SNMP要求代理始终创建一个属性行，并指定这两个对象。但是，对于大多数属性，代理应返回其中一个属性的“有用”值
objects and SHALL return the 'other' value for the other object. For integer only attributes, the agent SHALL always return a zero-length string value for the jmAttributeValueAsOctets object. For octet string only attributes, the agent SHALL always return a '-1' value for the jmAttributeValueAsInteger object.
对象，并应返回其他对象的“其他”值。对于纯整数属性，代理应始终为jmAttributeValueAsOctets对象返回长度为零的字符串值。对于仅八位字节字符串属性，代理应始终为jmAttributeValueAsInteger对象返回“-1”值。
A number of attributes are indexes in other tables. Such attribute names end with the word 'Index'. If the agent has not (yet) assigned an index value for a particular index attribute for a job, the agent SHALL either: (1) return the value 0 or (2) not add this attribute to the jmAttributeTable until the index value is assigned. In the interests of brevity, the semantics for 0 is specified once here and is not repeated for each index attribute specification and a DEFVAL of 0 is implied, even though the DEFVAL for jmAttributeValueAsInteger is -2.
许多属性是其他表中的索引。此类属性名称以“Index”一词结尾。如果代理尚未（尚未）为作业的特定索引属性分配索引值，则代理应：（1）返回值0或（2）在分配索引值之前不将此属性添加到jmAttributeTable。为了简洁起见，0的语义在这里只指定一次，并且不会对每个索引属性规范重复，并且会暗示deffal为0，即使jmAttributeValueAsInteger的deffal为-2。
Many attributes are sub-typed to give a more specific data type than Integer32 or OCTET STRING. The data sub-type of each attribute is indicated on the first line(s) of the description. Some attributes have several different data sub-type representations. When an attribute has both an Integer32 data sub-type and an OCTET STRING data sub-type, the attribute can be represented in a single row in the jmAttributeTable. In this case, the data sub-type name is not included as the last part of the name of the attribute, e.g., documentFormat(38) which is both an enum and/or a name. When the data sub-types cannot be represented by a single row in the jmAttributeTable, each such representation is considered a separate attribute and is assigned a separate name and enum value. For these attributes, the name of the data sub-type is the last part of the name of the attribute: Name, Index, DateAndTime, TimeStamp, etc. For example, documentFormatIndex(37) is an index.
许多属性都是子类型的，以提供比Integer32或八进制字符串更具体的数据类型。每个属性的数据子类型显示在描述的第一行。某些属性具有多个不同的数据子类型表示。当属性同时具有Integer32数据子类型和八位字符串数据子类型时，该属性可以在jmAttributeTable中的一行中表示。在这种情况下，数据子类型名称不包括在属性名称的最后一部分，例如documentFormat（38），它是枚举和/或名称。当数据子类型不能由jmAttributeTable中的一行表示时，每个这样的表示都被视为一个单独的属性，并被分配一个单独的名称和枚举值。对于这些属性，数据子类型的名称是属性名称的最后一部分：名称、索引、日期和时间、时间戳等。例如，documentFormatIndex（37）是一个索引。
NOTE: The Table of Contents also lists the data sub-type and/or data sub-types of each attribute, using the textual-convention name when such is defined. The following abbreviations are used in the Table of Contents as shown:
注意：目录还列出了每个属性的数据子类型和/或数据子类型，定义时使用文本约定名称。目录中使用了以下缩写，如图所示：
'Int32(-2..)' Integer32 (-2..2147483647) 'Int32(0..)' Integer32 (0..2147483647) 'Int32(1..)' Integer32 (1..2147483647) 'Int32(m..n)' For all other Integer ranges, the lower and upper bound of the range is indicated. 'UTF8String63' JmUTF8StringTC (SIZE(0..63)) 'JobString63' JmJobStringTC (SIZE(0..63)) 'Octets63' OCTET STRING (SIZE(0..63)) 'Octets(m..n)' For all other OCTET STRING ranges, the exact range is indicated.
‘Int32（-2..）’Integer32（-2..2147483647）’Int32（0..）’Integer32（0..2147483647）’Int32（1..2147483647）’Integer32（1..2147483647）‘Int32（m..n）’对于所有其他整数范围，会显示范围的下限和上限。’UTF8String63'JmUTF8StringTC（大小（0..63））'JobString63'JmJobStringTC（大小（0..63））'Octets63'八位字符串（大小（0..63））'Octets（m..n'）对于所有其他八位字符串范围，会显示精确的范围。
Most attributes have only one row per job. However, a few attributes can have multiple values per job or even per document, where each value is a separate row in the jmAttributeTable. Unless indicated with 'MULTI-ROW:' in the JmAttributeTypeTC description, an agent SHALL ensure that each attribute occurs only once in the jmAttributeTable for a job. Most of the 'MULTI-ROW' attributes do not allow duplicate values, i.e., the agent SHALL ensure that each value occurs only once for a job. Only if the specification of the ' MULTI-ROW' attribute also says "There is no restriction on the same xxx occurring in multiple rows" can the agent allow duplicate values to occur for the job.
大多数属性每个作业只有一行。但是，一些属性可以在每个作业甚至每个文档中具有多个值，其中每个值都是jmAttributeTable中的一个单独的行。除非在JMAttributeType描述中用“MULTI-ROW:”表示，否则代理应确保每个属性在作业的jmAttributeTable中仅出现一次。大多数“多行”属性不允许重复值，即代理应确保每个值在作业中仅出现一次。只有当“MULTI-ROW”属性的规范还表示“对同一个xxx在多行中出现没有限制”时，代理才能允许作业出现重复值。
NOTE - Duplicates are allowed for 'extensive' 'MULTI-ROW' attributes, such as fileName(34) or documentName(35) which are specified to be ' per-document' attributes, but are not allowed for 'intensive' ' MULTI-ROW' attributes, such as mediumConsumed(171) and documentFormat(38) which are specified to be 'per-job' attributes.
注意-允许重复“广泛的”“多行”属性，如指定为“每个文档”属性的文件名（34）或documentName（35），但不允许重复“密集的”“多行”属性，如指定为“每个作业”属性的mediumConsumed（171）和documentFormat（38）。
A number of objects and attributes record requirements for the job. Such object and attribute names end with the word 'Requested'. In the interests of brevity, the phrase 'requested' means: (1) requested by the client (or intervening server) in the job submission protocol and may also mean (2) embedded in the submitted document data, and/or (3) defaulted by the recipient device or server with the same semantics as if the requester had supplied, depending on implementation. Also if a value is supplied by the job submission client, and the server/device determines a better value, through processing or other means, the agent MAY return that better value for such object and attribute.
许多对象和属性记录作业的要求。此类对象和属性名称以“request”一词结尾。为了简洁起见，短语“请求”表示：（1）由作业提交协议中的客户端（或介入服务器）请求，也可以表示（2）嵌入在提交的文档数据中，和/或（3）由接收方设备或服务器默认，语义与请求者提供的相同，具体取决于实现。此外，如果作业提交客户端提供了值，并且服务器/设备通过处理或其他方式确定了更好的值，则代理可以为此类对象和属性返回该更好的值。
A number of objects and 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 consumption attribute specification and a DEFVAL of 0 is implied, even though the DEFVAL for jmAttributeValueAsInteger is -2.
许多对象和属性记录消耗。此类属性名称以单词“Completed”或“consumered”结尾。如果作业尚未消耗该资源正在计量的内容，则代理：（1）应返回值0或（2）在消耗开始之前不应将此属性添加到jmAttributeTable。为了简洁起见，这里只指定了一次0的语义，并且不会对每个消费属性规范重复该语义，并且暗示了deffal为0，即使jmAttributeValueAsInteger的deffal为-2。
This section specifies the job attributes.
本节指定作业属性。
In the following definitions of the attributes, each description indicates whether the useful value of the attribute SHALL be represented using the jmAttributeValueAsInteger or the jmAttributeValueAsOctets objects by the initial tag: 'INTEGER:' or ' OCTETS:', respectively.
在以下属性定义中，每个描述都指出了使用jmAttributeValueAsInteger还是JMAttributeValueAsActets对象分别通过初始标记：“INTEGER:”或“OCTETS:”来表示属性的有用值。
Some attributes allow the agent implementer a choice of useful values of either an integer, an octet string representation, or both, depending on implementation. These attributes are indicated with ' INTEGER:' AND/OR 'OCTETS:' tags.
某些属性允许代理实现者根据实现情况选择整数、八位字节字符串表示或两者的有用值。这些属性用“整数：”和/或“八位字节：”标记表示。
A very few attributes require both objects at the same time to represent a pair of useful values (see mediumConsumed(171)). These attributes are indicated with 'INTEGER:' AND 'OCTETS:' tags. See the jmAttributeGroup for the descriptions of these two MANDATORY objects.
极少数属性要求两个对象同时表示一对有用的值（请参见mediumConsumed（171））。这些属性用“整数”和“八位字节”标记表示。有关这两个必需对象的描述，请参见jmAttributeGroup。
NOTE - The enum assignments are grouped logically with values assigned in groups of 20, so that additional values may be registered in the future and assigned a value that is part of their logical grouping.
注意-枚举分配以20为一组进行逻辑分组，以便将来可以注册其他值，并分配一个作为其逻辑分组一部分的值。
Values in the range 2**30 to 2**31-1 are reserved for private or experimental usage. This range corresponds to the same range reserved in IPP. Implementers are warned that use of such values may conflict with other implementations. Implementers are encouraged to request registration of enum values following the procedures in Section 3.7.1.
2**30至2**31-1范围内的值保留供私人或实验使用。此范围对应于IPP中保留的相同范围。实现者被警告使用这些值可能与其他实现冲突。鼓励实施者按照第3.7.1节中的程序要求注册枚举值。
NOTE: No attribute name exceeds 31 characters.
注意：属性名称不超过31个字符。
The standard attribute types are:
标准属性类型包括：
jmAttributeTypeIndex Datatype
-------------------- --------
jmAttributeTypeIndex Datatype
-------------------- --------
other(1), Integer32 (-2..2147483647) AND/OR OCTET STRING(SIZE(0..63)) INTEGER: and/or OCTETS: An attribute that is not in the list and/or that has not been approved and registered with the PWG.
其他（1）、整数32（-2..2147483647）和/或八位字节字符串（大小（0..63））整数：和/或八位字节：不在列表中和/或未经PWG批准和注册的属性。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job State attributes (3 - 19 decimal)
+
+ The following attributes specify the state of a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job State attributes (3 - 19 decimal)
+
+ The following attributes specify the state of a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobStateReasons2(3), JmJobStateReasons2TC INTEGER: Additional information about the job's current state that augments the jmJobState object. See the description under the JmJobStateReasons1TC textual-convention.
jobStateReasons2（3），JmJobStateReasons2TC INTEGER：关于作业当前状态的附加信息，用于扩展jmJobState对象。请参阅JmJobStateReasons1TC文本约定下的说明。
jobStateReasons3(4), JmJobStateReasons3TC INTEGER: Additional information about the job's current state that augments the jmJobState object. See the description under JmJobStateReasons1TC textual-convention.
jobStateReasons3（4），JmJobStateReasons3TC INTEGER：关于作业当前状态的附加信息，该状态扩展了jmJobState对象。请参阅JmJobStateReasons1TC文本约定下的说明。
jobStateReasons4(5), JmJobStateReasons4TC INTEGER: Additional information about the job's current state that augments the jmJobState object. See the description under JmJobStateReasons1TC textual-convention.
jobStateReasons4（5），JmJobStateReasons4TC INTEGER：关于作业当前状态的附加信息，用于扩展jmJobState对象。请参阅JmJobStateReasons1TC文本约定下的说明。
processingMessage(6), JmUTF8StringTC (SIZE(0..63)) OCTETS: MULTI-ROW: A coded character set message that is generated by the server or device during the processing of the job as a simple form of processing log to show progress and any problems. The natural language of each value is specified by the corresponding processingMessageNaturalLangTag(7) value.
processingMessage（6），JmUTF8StringTC（大小（0..63））八位字节：多行：服务器或设备在作业处理过程中生成的编码字符集消息，作为处理日志的简单形式，以显示进度和任何问题。每个值的自然语言由相应的processingMessageNaturalLangTag（7）值指定。
NOTE - This attribute is intended for such conditions as interpreter messages, rather than being the printable form of the jmJobState and jmJobStateReasons1 objects and jobStateReasons2, jobStateReasons3, and jobStateReasons4 attributes. In order to produce a localized printable form of these job state objects/attribute, a management application SHOULD produce a message from their enum and bit values.
注意-此属性用于解释器消息等条件，而不是jmJobState和jmJobStateReasons1对象和jobStateReasons2、jobStateReasons3和jobStateReasons4属性的可打印形式。为了生成这些作业状态对象/属性的本地化可打印形式，管理应用程序应该从它们的枚举和位值生成消息。
NOTE - There is no job description attribute in IPP/1.0 that corresponds to this attribute and this attribute does not correspond to the IPP/1.0 'job-state-message' job description attribute, which is just a printable form of the IPP 'job-state' and 'job-state-reasons' job attributes.
注意-IPP/1.0中没有与此属性对应的职务描述属性，此属性与IPP/1.0“职务状态消息”职务描述属性不对应，后者只是IPP“职务状态”和“职务状态原因”职务属性的可打印形式。
There is no restriction for the same message occurring in multiple rows.
对于多行中出现的同一消息没有限制。
processingMessageNaturalLangTag(7), OCTET STRING(SIZE(0..63)) OCTETS: MULTI-ROW: The natural language of the corresponding processingMessage(6) attribute value. See section 3.6.1, entitled 'Text generated by the server or device'.
processingMessageNaturalLangTag（7），八位字节字符串（大小（0..63））八位字节：多行：对应processingMessage（6）属性值的自然语言。见第3.6.1节，标题为“服务器或设备生成的文本”。
If the agent does not know the natural language of the job processing message, the agent SHALL either (1) return a zero length string value for the processingMessageNaturalLangTag(7) attribute or (2) not return the processingMessageNaturalLangTag(7) attribute for the job.
如果代理不知道作业处理消息的自然语言，则代理应（1）为processingMessageNaturalLangTag（7）属性返回零长度字符串值，或（2）不为作业返回processingMessageNaturalLangTag（7）属性。
There is no restriction for the same tag occurring in multiple rows, since when this attribute is implemented, it SHOULD have a value row for each corresponding processingMessage(6) attribute value row.
对于出现在多行中的同一标记没有限制，因为在实现该属性时，每个对应的processingMessage（6）属性值行都应该有一个值行。
jobCodedCharSet(8), CodedCharSet INTEGER: The MIBenum identifier of the coded character set that the agent is using to represent coded character set objects and attributes of type 'JmJobStringTC'. These coded character set objects and attributes are either: (1) supplied by the job submitting client or (2) defaulted by the server or device when omitted by the job submitting client. The agent SHALL represent these objects and attributes in the MIB either (1) in the coded character set as they were submitted or (2) MAY convert the coded character set to another coded character set or encoding scheme as identified by the jobCodedCharSet(8) attribute. See section 3.6.2, entitled 'Text supplied by the job submitter'.
jobCodedCharSet（8），CodedCharSet INTEGER：代理用于表示“JmJobStringTC”类型的编码字符集对象和属性的编码字符集的MIBenum标识符。这些编码字符集对象和属性可以是：（1）由作业提交客户端提供，或者（2）在作业提交客户端省略时由服务器或设备默认。代理应在MIB中表示这些对象和属性，（1）在提交时以编码字符集表示，或（2）将编码字符集转换为另一个编码字符集或由jobCodedCharSet（8）属性标识的编码方案。见第3.6.2节，标题为“作业提交人提供的文本”。
These MIBenum values are assigned by IANA [IANA-charsets] when the coded character sets are registered. The coded character set SHALL be one of the ones registered with IANA [IANA] and the enum value uses the CodedCharSet textual-convention from the Printer MIB. See the JmJobStringTC textual-convention.
注册编码字符集时，这些MIBenum值由IANA[IANA字符集]分配。编码字符集应为IANA[IANA]注册的字符集之一，且枚举值使用打印机MIB中的CodedCharSet文本约定。请参阅JmJobStringTC文本约定。
If the agent does not know what coded character set was used by the job submitting client, the agent SHALL either (1) return the 'unknown(2)' value for the jobCodedCharSet(8) attribute or (2) not return the jobCodedCharSet(8) attribute for the job.
如果代理不知道作业提交客户端使用了什么编码字符集，代理应（1）返回jobCodedCharSet（8）属性的“未知（2）”值，或（2）不返回作业的jobCodedCharSet（8）属性。
jobNaturalLanguageTag(9), OCTET STRING(SIZE(0..63)) OCTETS: The natural language of the job attributes supplied by the job submitter or defaulted by the server or device for the job, i.e., all objects and attributes represented by the ' JmJobStringTC' textual-convention, such as jobName, mediumRequested, etc. See Section 3.6.2, entitled 'Text supplied by the job submitter'.
JobNaturAllangageTag（9），八位字节字符串（大小（0..63））八位字节：作业提交者提供的作业属性的自然语言，或作业服务器或设备默认的作业属性，即“JmJobStringTC”文本约定表示的所有对象和属性，如作业名称、请求的介质等。参见第3.6.2节，标题为“作业提交人提供的文本”。
If the agent does not know what natural language was used by the job submitting client, the agent SHALL either (1) return a zero length string value for the jobNaturalLanguageTag(9) attribute or (2) not return jobNaturalLanguageTag(9) attribute for the job.
如果代理不知道作业提交客户端使用的是哪种自然语言，则代理应（1）为JobNaturallangageTag（9）属性返回零长度字符串值，或（2）不为作业返回JobNaturallangageTag（9）属性。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Identification attributes (20 - 49 decimal)
+
+ The following attributes help an end user, a system
+ operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Identification attributes (20 - 49 decimal)
+
+ The following attributes help an end user, a system
+ operator, or an accounting program identify a job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobURI(20), OCTET STRING(SIZE(0..63)) OCTETS: MULTI-ROW: The job's Universal Resource Identifier (URI) [RFC1738]. See IPP [ipp-model] for example usage.
jobURI（20），八位字节字符串（大小（0..63））八位字节：多行：作业的通用资源标识符（URI）[RFC1738]。有关用法示例，请参见IPP[IPP型号]。
NOTE - The agent may be able to generate this value on each SNMP Get operation from smaller values, rather than having to store the entire URI.
注意-代理可以在每个SNMP Get操作中从较小的值生成此值，而不必存储整个URI。
If the URI exceeds 63 octets, the agent SHALL use multiple values, with the next 63 octets coming in the second value, etc.
如果URI超过63个八位字节，代理将使用多个值，接下来的63个八位字节将进入第二个值，以此类推。
NOTE - IPP [ipp-model] has a 1023-octet maximum length for a URI, though the URI standard itself and HTTP/1.1 specify no maximum length.
注意-IPP[IPP model]对于URI有1023个八位字节的最大长度，尽管URI标准本身和HTTP/1.1没有指定最大长度。
jobAccountName(21), OCTET STRING(SIZE(0..63)) OCTETS: Arbitrary binary information which MAY be coded character set data or encrypted data supplied by the submitting user for use by accounting services to allocate or categorize charges for services provided, such as a customer account name or number.
jobAccountName（21）、八位字节字符串（大小（0..63））八位字节：任意二进制信息，可以是提交用户提供的编码字符集数据或加密数据，供会计服务用于分配或分类所提供服务的费用，如客户帐户名或号码。
NOTE: This attribute NEED NOT be printable characters.
注意：此属性不需要是可打印字符。
serverAssignedJobName(22), JmJobStringTC (SIZE(0..63)) OCTETS: Configuration 3 only: The human readable string name, number, or ID of the job as assigned by the server that submitted the job to the device that the agent is providing access to with this MIB.
serverAssignedJobName（22）、JmJobStringTC（大小（0..63））八位字节：仅限配置3：由将作业提交给代理使用此MIB提供访问权限的设备的服务器分配的作业的可读字符串名称、编号或ID。
NOTE - This attribute is intended for enabling a user to find his/her job that a server submitted to a device when either the client does not support the jmJobSubmissionID or the server does not pass the jmJobSubmissionID through to the device.
注意-此属性用于在客户端不支持jmJobSubmissionID或服务器未将jmJobSubmissionID传递给设备时，使用户能够找到服务器提交给设备的作业。
jobName(23), JmJobStringTC (SIZE(0..63)) OCTETS: The human readable string name of the job as assigned by the submitting user to help the user distinguish between his/her various jobs. This name does not need to be unique.
jobName（23），JmJobStringTC（大小（0..63））八位字节：提交用户分配的作业的可读字符串名称，以帮助用户区分他/她的各种作业。此名称不需要是唯一的。
This attribute is intended for enabling a user or the user's application to convey a job name that MAY be printed on a start sheet, returned in a query result, or used in notification or logging messages.
此属性旨在使用户或用户的应用程序传递作业名称，作业名称可以打印在起始页上、在查询结果中返回或在通知或日志消息中使用。
In order to assist users to find their jobs for job submission protocols that don't supply a jmJobSubmissionID, the agent SHOULD maintain the jobName attribute for the time specified by the jmGeneralJobPersistence object, rather than the (shorter) jmGeneralAttributePersistence object.
为了帮助用户找到不提供jmJobSubmissionID的作业提交协议的作业，代理应该在jmGeneralJobPersistence对象指定的时间内维护jobName属性，而不是（较短的）jmGeneralAttributePersistence对象。
If this attribute is not specified when the job is submitted, no job name is assumed, but implementation specific defaults are allowed, such as the value of the documentName attribute of the first document in the job or the fileName attribute of the first document in the job.
如果提交作业时未指定此属性，则假定没有作业名称，但允许实现特定的默认值，例如作业中第一个文档的documentName属性值或作业中第一个文档的fileName属性值。
The jobName attribute is distinguished from the jobComment attribute, in that the jobName attribute is intended to permit the submitting user to distinguish between different jobs that he/she has submitted. The jobComment attribute is intended to be free form additional information that a user might wish to use to communicate with himself/herself, such as a reminder of what to do with the results or to indicate a different set of input parameters were tried in several different job submissions.
jobName属性与jobComment属性的区别在于，jobName属性旨在允许提交用户区分他/她已提交的不同作业。jobComment属性旨在提供用户可能希望用来与自己沟通的附加信息，例如提醒用户如何处理结果或指示在多个不同的作业提交中尝试了一组不同的输入参数。
jobServiceTypes(24), JmJobServiceTypesTC INTEGER: Specifies the type(s) of service to which the job has been submitted (print, fax, scan, etc.). The service type is bit encoded with each job service type so that more general and arbitrary services can be created, such as services with more than one destination type, or ones with only a source or only a destination. For example, a job service might scan, faxOut, and print a single job. In this case, three bits would be set in the jobServiceTypes attribute, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, respectively, yielding: 0x2C.
jobServiceTypes（24），JmJobServiceTypesTC INTEGER：指定作业提交到的服务类型（打印、传真、扫描等）。服务类型使用每个作业服务类型进行位编码，以便可以创建更通用和任意的服务，例如具有多个目标类型的服务，或者仅具有源或目标的服务。例如，作业服务可以扫描、传真和打印单个作业。在这种情况下，将在jobServiceTypes属性中设置三个位，分别对应于十六进制值：0x8+0x20+0x4，产生：0x2C。
Whether this attribute is set from a job attribute supplied by the job submission client or is set by the recipient job submission server or device depends on the job submission protocol. This attribute SHALL be implemented if the server or device has other types in addition to or instead of printing.
此属性是从作业提交客户端提供的作业属性设置的，还是由收件人作业提交服务器或设备设置的，取决于作业提交协议。如果服务器或设备除了打印之外还有其他类型或没有打印，则应实现此属性。
One of the purposes of this attribute is to permit a requester to filter out jobs that are not of interest. For example, a printer operator may only be interested in jobs that include printing.
此属性的目的之一是允许请求者筛选出不感兴趣的作业。例如，打印机操作员可能只对包含打印的作业感兴趣。
jobSourceChannelIndex(25), Integer32 (0..2147483647) INTEGER: The index of the row in the associated Printer MIB [print-mib] of the channel which is the source of the print job.
jobSourceChannelIndex（25），Integer32（0..2147483647）INTEGER：通道的关联打印机MIB[print MIB]中的行的索引，该行是打印作业的源。
jobSourcePlatformType(26), JmJobSourcePlatformTypeTC INTEGER: The source platform type of the immediate upstream submitter that submitted the job to the server (configuration 2) or device (configuration 1 and 3) to which the agent is providing access. For configuration 1, this is the type of the client that submitted the job to the device; for configuration 2, this is the type of the client that submitted the job to the server; and for configuration 3, this is the type of the server that submitted the job to the device.
jobSourcePlatformType（26），JmJobSourcePlatformTypeTC INTEGER：将作业提交给代理提供访问权限的服务器（配置2）或设备（配置1和3）的直接上游提交者的源平台类型。对于配置1，这是向设备提交作业的客户端的类型；对于配置2，这是向服务器提交作业的客户端的类型；对于配置3，这是向设备提交作业的服务器的类型。
submittingServerName(27), JmJobStringTC (SIZE(0..63)) OCTETS: For configuration 3 only: The administrative name of the server that submitted the job to the device.
submittingServerName（27），JmJobStringTC（大小（0..63））八位字节：仅用于配置3：将作业提交到设备的服务器的管理名称。
submittingApplicationName(28), JmJobStringTC (SIZE(0..63)) OCTETS: The name of the client application (not the server in configuration 3) that submitted the job to the server or device.
submittingApplicationName（28），JmJobStringTC（大小（0..63））八位字节：将作业提交到服务器或设备的客户端应用程序（不是配置3中的服务器）的名称。
jobOriginatingHost(29), JmJobStringTC (SIZE(0..63)) OCTETS: The name of the client host (not the server host name in configuration 3) that submitted the job to the server or device.
jobOriginatingHost（29），JmJobStringTC（大小（0..63））八位字节：将作业提交到服务器或设备的客户端主机的名称（不是配置3中的服务器主机名）。
deviceNameRequested(30), JmJobStringTC (SIZE(0..63)) OCTETS: The administratively defined coded character set name of the target device requested by the submitting user. For configuration 1, its value corresponds to the Printer MIB [print-mib]: prtGeneralPrinterName object. For configuration 2 and 3, its value is the name of the logical or physical device that the user supplied to indicate to the server on which device(s) they wanted the job to be processed.
deviceNameRequested（30），JmJobStringTC（大小（0..63））八位字节：提交用户请求的目标设备的管理定义的编码字符集名称。对于配置1，其值对应于打印机MIB[print MIB]：prtGeneralPrinterName对象。对于配置2和3，其值是用户提供的逻辑或物理设备的名称，用于向服务器指示他们希望在哪个设备上处理作业。
queueNameRequested(31), JmJobStringTC (SIZE(0..63)) OCTETS: The administratively defined coded character set name of the target queue requested by the submitting user. For configuration 1, its value corresponds to the queue in the device for which the agent is providing access. For configuration 2 and 3, its value is the name of the queue that the user supplied to indicate to the server on which device(s) they wanted the job to be processed.
queueNameRequested（31），JmJobStringTC（大小（0..63））八位字节：提交用户请求的目标队列的管理定义的编码字符集名称。对于配置1，其值对应于代理为其提供访问权限的设备中的队列。对于配置2和3，其值是用户提供的队列名称，用于向服务器指示他们希望在哪个设备上处理作业。
NOTE - typically an implementation SHOULD support either the deviceNameRequested or queueNameRequested attribute, but not both.
注意-通常情况下，实现应支持deviceNameRequested或queueNameRequested属性，但不能同时支持两者。
physicalDevice(32), hrDeviceIndex AND/OR JmUTF8StringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The index of the physical device MIB instance requested/used, such as the Printer MIB [print-mib]. This value is an hrDeviceIndex value. See the Host Resources MIB [hr-mib].
physicalDevice（32）、hrDeviceIndex和/或JmUTF8StringTC（大小（0..63））整数：多行：请求/使用的物理设备MIB实例的索引，例如打印机MIB[print MIB]。此值是hrDeviceIndex值。请参阅主机资源MIB[hr MIB]。
AND/OR
和/或
OCTETS: MULTI-ROW: The name of the physical device to which the job is assigned.
八位字节：多行：作业分配到的物理设备的名称。
numberOfDocuments(33), Integer32 (-2..2147483647) INTEGER: The number of documents in this job.
numberOfDocuments（33），整数32（-2..2147483647）整数：此作业中的文档数。
The agent SHOULD return this attribute if the job has more than one document.
如果作业有多个文档，则代理应返回此属性。
fileName(34), JmJobStringTC (SIZE(0..63)) OCTETS: MULTI-ROW: The coded character set file name or URI [URI-spec] of the document.
fileName（34），JmJobStringTC（SIZE（0..63））八位字节：多行：文档的编码字符集文件名或URI[URI spec]。
There is no restriction on the same file name occurring in multiple rows.
同一文件名出现在多行中没有限制。
documentName(35), JmJobStringTC (SIZE(0..63)) OCTETS: MULTI-ROW: The coded character set name of the document.
documentName（35），JmJobStringTC（大小（0..63））八位字节：多行：文档的编码字符集名称。
There is no restriction on the same document name occurring in multiple rows.
同一文档名出现在多行中没有限制。
jobComment(36), JmJobStringTC (SIZE(0..63)) OCTETS: An arbitrary human-readable coded character text string supplied by the submitting user or the job submitting application program for any purpose. For example, a user might indicate what he/she is going to do with the printed output or the job submitting application program might indicate how the document was produced.
jobComment（36）、JmJobStringTC（大小（0..63））八位字节：提交用户或作业提交应用程序出于任何目的提供的任意人类可读编码字符串。例如，用户可能会指示他/她将如何处理打印输出，或者作业提交应用程序可能会指示文档是如何生成的。
The jobComment attribute is not intended to be a name; see the jobName attribute.
jobComment属性不是一个名称；请参见jobName属性。
documentFormatIndex(37), Integer32 (0..2147483647) INTEGER: MULTI-ROW: The index in the prtInterpreterTable in the Printer MIB [print-mib] of the page description language (PDL) or control language interpreter that this job requires/uses. A document or a job MAY use more than one PDL or control language.
documentFormatIndex（37）、Integer32（0..2147483647）INTEGER:多行：此作业需要/使用的页面描述语言（PDL）或控制语言解释器的打印机MIB[print MIB]中PRTInterpertable中的索引。文档或作业可以使用多种PDL或控制语言。
NOTE - As with all intensive attributes where multiple rows are allowed, there SHALL be only one distinct row for each distinct interpreter; there SHALL be no duplicates.
注-与允许多行的所有密集属性一样，每个不同的解释器只能有一个不同的行；不得有副本。
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.
注意-此属性类型旨在与实现打印机MIB的代理一起使用，如果代理未实现打印机MIB，则不应使用此属性类型。此类代理应改为使用documentFormat属性。
documentFormat(38), PrtInterpreterLangFamilyTC AND/OR OCTET STRING(SIZE(0..63)) INTEGER: MULTI-ROW: The interpreter language family corresponding to the Printer MIB [print-mib] prtInterpreterLangFamily object, that this job requires/uses. A document or a job MAY use more than one PDL or control language.
documentFormat（38）、PrtInterpreterLangFamilyTC和/或八位字符串（大小（0..63））整数：多行：与此作业需要/使用的打印机MIB[print MIB]prtInterpreterLangFamily对象相对应的解释器语言族。文档或作业可以使用多种PDL或控制语言。
AND/OR
和/或
OCTETS: MULTI-ROW: The document format registered as a media type [iana-media-types], i.e., the name of the MIME content-type/subtype. Examples: 'application/postscript', 'application/vnd.hp-PCL', 'application/pdf', 'text/plain' (US-ASCII SHALL be assumed), 'text/plain; charset=iso-8859-1', and 'application/octet-stream'. The IPP 'document-format' job attribute uses these same values with the same semantics. See the IPP [ipp-model] 'mimeMediaType' attribute syntax and the document-format attribute for further examples and explanation.
八位字节：多行：注册为媒体类型[iana媒体类型]的文档格式，即MIME内容类型/子类型的名称。示例：“application/postscript”、“application/vnd.hp PCL”、“application/pdf”、“text/plain”（假定为US-ASCII）、“text/plain”；字符集=iso-8859-1'，和“应用程序/八位字节流”。IPP“document format”作业属性使用这些具有相同语义的相同值。有关更多示例和说明，请参见IPP[IPP模型]“mimeDiaType”属性语法和文档格式属性。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Parameter attributes (50 - 67 decimal)
+
+ The following attributes represent input parameters
+ supplied by the submitting client in the job submission
+ protocol.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Parameter attributes (50 - 67 decimal)
+
+ The following attributes represent input parameters
+ supplied by the submitting client in the job submission
+ protocol.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobPriority(50), Integer32 (-2..100) INTEGER: The priority for scheduling the job. It is used by servers and devices that employ a priority-based scheduling algorithm.
作业优先级（50），整数32（-2..100）整数：调度作业的优先级。它由采用基于优先级的调度算法的服务器和设备使用。
A higher value specifies a higher priority. The value 1 is defined to indicate the lowest possible priority (a job which a priority-based scheduling algorithm SHALL pass over in favor of higher priority jobs). The value 100 is defined to indicate the highest possible priority. Priority is expected to be evenly or 'normally' distributed across this range. The mapping of vendor-defined priority over this range is implementation-specific. -2 indicates unknown.
值越大，优先级越高。值1被定义为指示最低可能优先级（基于优先级的调度算法将优先于高优先级作业的作业）。值100被定义为指示可能的最高优先级。优先级预计将在该范围内均匀或“正常”分布。供应商定义的优先级在该范围内的映射是特定于实现的-2表示未知。
jobProcessAfterDateAndTime(51), DateAndTime (SNMPv2-TC) OCTETS: The calendar date and time of day after which the job SHALL become a candidate to be scheduled for processing. If the value of this attribute is in the future, the server SHALL set
jobProcessAfterDateAndTime（51），DateAndTime（SNMPv2 TC）八位字节：一天中的日历日期和时间，在此日期和时间之后，作业将成为计划处理的候选项。如果该属性的值是将来的，则服务器应设置
the value of the job's jmJobState object to pendingHeld and add the jobProcessAfterSpecified bit value to the job's jmJobStateReasons1 object. When the specified date and time arrives, the server SHALL remove the jobProcessAfterSpecified bit value from the job's jmJobStateReasons1 object and, if no other reasons remain, SHALL change the job's jmJobState object to pending.
将作业的jmJobState对象的值添加到pendingHeld，并将jobProcessAfterSpecified位值添加到作业的jmJobStateReasons1对象。当指定的日期和时间到达时，服务器应从作业的jmJobStateReasons1对象中删除jobProcessAfterSpecified位值，如果没有其他原因，则应将作业的jmJobState对象更改为pending。
jobHold(52), JmBooleanTC INTEGER: If the value is 'true(4)', a client has explicitly specified that the job is to be held until explicitly released. Until the job is explicitly released by a client, the job SHALL be in the pendingHeld state with the jobHoldSpecified value in the jmJobStateReasons1 attribute.
jobHold（52），JmBooleanTC INTEGER：如果该值为“true（4）”，则客户端已明确指定该作业将被保留，直到显式释放。在客户端显式释放作业之前，作业应处于pendingHeld状态，jmJobStateReasons1属性中具有jobHoldSpecified值。
jobHoldUntil(53), JmJobStringTC (SIZE(0..63)) OCTETS: The named time period during which the job SHALL become a candidate for processing, such as 'evening', 'night', ' weekend', 'second-shift', 'third-shift', etc., (supported values configured by the system administrator). See IPP [ipp-model] for the standard keyword values. Until that time period arrives, the job SHALL be in the pendingHeld state with the jobHoldUntilSpecified value in the jmJobStateReasons1 object. The value 'no-hold' SHALL indicate explicitly that no time period has been specified; the absence of this attribute SHALL indicate implicitly that no time period has been specified.
jobHoldUntil（53）、JmJobStringTC（大小（0..63））八位字节：指定的时间段，在此期间，作业将成为处理的候选对象，例如“晚上”、“晚上”、“周末”、“第二班”、“第三班”等（系统管理员配置的支持值）。有关标准关键字值，请参见IPP[IPP模型]。在该时间段到来之前，作业应处于pendingHeld状态，并在jmJobStateReasons1对象中具有JobHoldUntillSpecified值。“无保留”值应明确表示未规定任何时间段；缺少此属性将暗示未指定时间段。
outputBin(54), Integer32 (0..2147483647) AND/OR JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The output subunit index in the Printer MIB [print-mib]
outputBin（54）、Integer32（0..2147483647）和/或JmJobStringTC（SIZE（0..63））整数：多行：打印机MIB[print MIB]中的输出子单元索引
AND/OR
和/或
OCTETS: MULTI-ROW: the name or number (represented as ASCII digits) of the output bin to which all or part of the job is placed in.
八位字节：多行：作业全部或部分放置到的输出箱的名称或编号（以ASCII数字表示）。
sides(55), Integer32 (-2..2) INTEGER: MULTI-ROW: The number of sides, '1' or '2', that any document in this job requires/used.
边（55），整数32（-2..2）整数：多行：此作业中的任何文档需要/使用的边数，“1”或“2”。
finishing(56), JmFinishingTC INTEGER: MULTI-ROW: Type of finishing that any document in this job requires/used.
finishing（56），JmFinishingTC INTEGER:多行：此作业中的任何文档需要/使用的整理类型。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Image Quality attributes (requested and consumed) (70 - 87)
+
+ For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Image Quality attributes (requested and consumed) (70 - 87)
+
+ For devices that can vary the image quality.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
printQualityRequested(70), JmPrintQualityTC INTEGER: MULTI-ROW: The print quality selection requested for a document in the job for printers that allow quality differentiation.
printQualityRequested（70），JmPrintQualityTC INTEGER:多行：允许质量差异的打印机在作业中为文档请求的打印质量选择。
printQualityUsed(71), JmPrintQualityTC INTEGER: MULTI-ROW: The print quality selection actually used by a document in the job for printers that allow quality differentiation.
printQualityUsed（71），JmPrintQualityTC INTEGER:MULTI-ROW：作业中文档实际使用的打印质量选择，用于允许质量差异的打印机。
printerResolutionRequested(72), JmPrinterResolutionTC OCTETS: MULTI-ROW: The printer resolution requested for a document in the job for printers that support resolution selection.
printerResolutionRequested（72），JMPrinterResolutionC八位字节：多行：为支持分辨率选择的打印机的作业中的文档请求的打印机分辨率。
printerResolutionUsed(73), JmPrinterResolutionTC OCTETS: MULTI-ROW: The printer resolution actually used by a document in the job for printers that support resolution selection.
printerResolutionUsed（73），JMPrinterResolutionC八位字节：多行：作业中文档实际使用的打印机分辨率，用于支持分辨率选择的打印机。
tonerEcomonyRequested(74), JmTonerEconomyTC INTEGER: MULTI-ROW: The toner economy selection requested for documents in the job for printers that allow toner economy differentiation.
tonerEcomonyRequested（74），JmTonerEconomyTC INTEGER:多行：为允许碳粉经济性差异的打印机作业中的文档请求的碳粉经济性选择。
tonerEcomonyUsed(75), JmTonerEconomyTC INTEGER: MULTI-ROW: The toner economy selection actually used by documents in the job for printers that allow toner economy differentiation.
tonerEcomonyUsed（75），JmTonerEconomyTC INTEGER:多行：作业中文档实际使用的墨粉经济性选择，用于允许墨粉经济性差异的打印机。
tonerDensityRequested(76) Integer32 (-2..100) INTEGER: MULTI-ROW: The toner density requested for a document in this job for devices that can vary toner density levels. Level 1 is the lowest density and level 100 is the highest density level. Devices with a smaller range, SHALL map the 1-100 range evenly onto the implemented range.
tonerDensityRequested（76）整数32（-2..100）整数：多行：对于可以改变碳粉密度级别的设备，此作业中的文档请求的碳粉密度。1级为最低密度，100级为最高密度。范围较小的装置应将1-100范围均匀地映射到实施范围。
tonerDensityUsed(77), Integer32 (-2..100) INTEGER: MULTI-ROW: The toner density used by documents in this job for devices that can vary toner density levels. Level
tonerDensityUsed（77），Integer32（-2..100）INTEGER:多行：此作业中文档用于可改变碳粉密度级别的设备的碳粉密度。数量
1 is the lowest density and level 100 is the highest density level. Devices with a smaller range, SHALL map the 1-100 range evenly onto the implemented range.
1为最低密度，100级为最高密度。范围较小的装置应将1-100范围均匀地映射到实施范围。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Progress attributes (requested and consumed) (90-109)
+
+ Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative progress
+ to users. See section 3.4, entitled:
+ 'Monitoring Job Progress'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Job Progress attributes (requested and consumed) (90-109)
+
+ Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative progress
+ to users. See section 3.4, entitled:
+ 'Monitoring Job Progress'.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobCopiesRequested(90), Integer32 (-2..2147483647) INTEGER: The number of copies of the entire job that are to be produced.
jobCopiesRequested（90），Integer32（-2..2147483647）INTEGER：要生成的整个作业的副本数。
jobCopiesCompleted(91), Integer32 (-2..2147483647) INTEGER: The number of copies of the entire job that have been completed so far.
jobCopiesCompleted（91），Integer32（-2..2147483647）INTEGER：到目前为止已完成的整个作业的副本数。
documentCopiesRequested(92), Integer32 (-2..2147483647) INTEGER: The total count of the number of document copies requested for the job as a whole. If there are documents A, B, and C, and document B is specified to produce 4 copies, the number of document copies requested is 6 for the job.
documentCopiesRequested（92），Integer32（-2..2147483647）INTEGER：整个作业请求的文档副本数的总数。如果存在文件A、B和C，且文件B指定生成4份副本，则作业所需的文件副本数为6份。
This attribute SHALL be used only when a job has multiple documents. The jobCopiesRequested attribute SHALL be used when the job has only one document.
仅当作业具有多个文档时，才应使用此属性。当作业只有一个文档时，应使用jobCopiesRequested属性。
documentCopiesCompleted(93), Integer32 (-2..2147483647) INTEGER: The total count of the number of document copies completed so far for the job as a whole. If there are documents A, B, and C, and document B is specified to produce 4 copies, the number of document copies starts a 0 and runs up to 6 for the job as the job processes.
documentCopiesCompleted（93），Integer32（-2..2147483647）INTEGER：作业作为一个整体到目前为止完成的文档副本数的总数。如果存在文档A、B和C，并且文档B被指定为生成4份副本，则文档副本的数量将从0开始，并在作业处理时最多运行6份。
This attribute SHALL be used only when a job has multiple documents. The jobCopiesCompleted attribute SHALL be used when the job has only one document.
仅当作业具有多个文档时，才应使用此属性。当作业只有一个文档时，应使用jobCopiesCompleted属性。
jobKOctetsTransferred(94), Integer32 (-2..2147483647) INTEGER: The number of K (1024) octets transferred to the server or device to which the agent is providing access. This count is independent of the number of copies of the job or documents that will be produced, but it is only a measure of the number of bytes transferred to the server or device.
JobKocteTransferred（94），Integer32（-2..2147483647）INTEGER：传输到代理提供访问的服务器或设备的K（1024）个八位字节数。此计数与将生成的作业或文档的副本数无关，但它只是传输到服务器或设备的字节数的度量。
The agent SHALL round the actual number of octets transferred up to the next higher K. Thus 0 octets SHALL be represented as ' 0', 1-1024 octets SHALL BE represented as '1', 1025-2048 SHALL be '2', etc. When the job completes, the values of the jmJobKOctetsPerCopyRequested object and the jobKOctetsTransferred attribute SHALL be equal.
代理应将实际传输的八位字节数四舍五入到下一个更高的K。因此，0个八位字节应表示为“0”，1-1024个八位字节应表示为“1”，1025-2048应表示为“2”，等等。当作业完成时，jmJobKOctetsPerCopyRequested对象和jobKOctetsTransferred属性的值应相等。
NOTE - The jobKOctetsTransferred can be used with the jmJobKOctetsPerCopyRequested object in order to produce a relative indication of the progress of the job for agents that do not implement the jmJobKOctetsProcessed object.
注意-JobKocteTransferred可与jmJobKOctetsPerCopyRequested对象一起使用，以便为未实现jmJobKOctetsProcessed对象的代理生成作业进度的相对指示。
sheetCompletedCopyNumber(95), Integer32 (-2..2147483647) INTEGER: The number of the copy being stacked for the current document. This number starts at 0, is set to 1 when the first sheet of the first copy for each document is being stacked and is equal to n where n is the nth sheet stacked in the current document copy. See section 3.4 , entitled 'Monitoring Job Progress'.
sheetCompletedCopyNumber（95），整数32（-2..2147483647）整数：当前文档正在堆叠的副本数。此数字从0开始，在堆叠每个文档的第一份副本的第一页时设置为1，等于n，其中n是当前文档副本中堆叠的第n页。见第3.4节，标题为“监控工作进度”。
sheetCompletedDocumentNumber(96), Integer32 (-2..2147483647) INTEGER: The ordinal number of the document in the job that is currently being stacked. This number starts at 0, increments to 1 when the first sheet of the first document in the job is being stacked, and is equal to n where n is the nth document in the job, starting with 1.
sheetCompletedDocumentNumber（96），Integer32（-2..2147483647）INTEGER：作业中当前正在堆叠的文档的序号。此数字从0开始，在堆叠作业中第一个文档的第一张时递增为1，等于n，其中n是作业中的第n个文档，从1开始。
Implementations that only support one document jobs SHOULD NOT implement this attribute.
仅支持一个文档作业的实现不应实现此属性。
jobCollationType(97), JmJobCollationTypeTC INTEGER: The type of job collation. See also Section 3.4, entitled 'Monitoring Job Progress'.
jobCollationType（97），JmJobCollationTypeTC整数：作业排序规则的类型。另见第3.4节，标题为“监控工作进度”。
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Impression attributes (110 - 129 decimal)
+
+ See the definition of the terms 'impression', 'sheet',
+ and 'page' in Section 2.
+
+ See also jmJobImpressionsPerCopyRequested and
+ jmJobImpressionsCompleted objects in the jmJobTable.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Impression attributes (110 - 129 decimal)
+
+ See the definition of the terms 'impression', 'sheet',
+ and 'page' in Section 2.
+
+ See also jmJobImpressionsPerCopyRequested and
+ jmJobImpressionsCompleted objects in the jmJobTable.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
impressionsSpooled(110), Integer32 (-2..2147483647) INTEGER: The number of impressions spooled to the server or device for the job so far.
ImpressionSpooled（110），Integer32（-2..2147483647）INTEGER：到目前为止为作业假脱机到服务器或设备的印象数。
impressionsSentToDevice(111), Integer32 (-2..2147483647) INTEGER: The number of impressions sent to the device for the job so far.
ImpressionSentToDevice（111），Integer32（-2..2147483647）INTEGER：到目前为止发送到作业设备的印象数。
impressionsInterpreted(112), Integer32 (-2..2147483647) INTEGER: The number of impressions interpreted for the job so far.
ImpressionsExpressed（112），Integer32（-2..2147483647）INTEGER：迄今为止为作业解释的印象数。
impressionsCompletedCurrentCopy(113), Integer32 (-2..2147483647) INTEGER: The number of impressions completed by the device for the current copy of the current document so far. For printing, the impressions completed includes interpreting, marking, and stacking the output. For other types of job services, the number of impressions completed includes the number of impressions processed.
ImpressionCompletedCurrentCopy（113），Integer32（-2..2147483647）INTEGER：到目前为止，设备为当前文档的当前副本完成的印象数。对于打印，完成的印象包括解释、标记和堆叠输出。对于其他类型的工作服务，完成的印象数包括处理的印象数。
This value SHALL be reset to 0 for each document in the job and for each document copy.
对于作业中的每个文件和每个文件副本，该值应重置为0。
fullColorImpressionsCompleted(114), Integer32 (-2..2147483647) INTEGER: The number of full color impressions completed by the device for this job so far. For printing, the impressions completed includes interpreting, marking, and stacking the output. For other types of job services, the number of impressions completed includes the number of impressions processed. Full color impressions are typically defined as those requiring 3 or more colorants, but this MAY vary by implementation. In any case, the value of this attribute counts by 1 for each side that has full color, not by the number of colors per side (and the other impression counters are incremented, except highlightColorImpressionsCompleted(115)).
fullColorImpressionsCompleted（114），Integer32（-2..2147483647）INTEGER：到目前为止设备为此作业完成的全彩显示数。对于打印，完成的印象包括解释、标记和堆叠输出。对于其他类型的工作服务，完成的印象数包括处理的印象数。全色印模通常被定义为需要3种或更多着色剂的印模，但这可能因实施而有所不同。在任何情况下，对于具有全色的每一侧，该属性的值按1计数，而不是按每一侧的颜色数计数（并且其他印象计数器递增，除了highlightColorImpressionsCompleted（115））之外）。
highlightColorImpressionsCompleted(115), Integer32 (-2..2147483647) INTEGER: The number of highlight color impressions completed by the device for this job so far. For printing, the impressions completed includes interpreting, marking, and stacking the output. For other types of job services, the number of impressions completed includes the number of impressions processed. Highlight color impressions are typically defined as those requiring black plus one other colorant, but this MAY vary by implementation. In any case, the value of this attribute counts by 1 for each side that has highlight color (and the other impression counters are incremented, except fullColorImpressionsCompleted(114)).
highlightColorImpressionsCompleted（115），Integer32（-2..2147483647）INTEGER：迄今为止设备为此作业完成的高亮显示颜色印象数。对于打印，完成的印象包括解释、标记和堆叠输出。对于其他类型的工作服务，完成的印象数包括处理的印象数。突出显示颜色印象通常定义为需要黑色加上一种其他着色剂的印象，但这可能因实施而有所不同。在任何情况下，对于具有高光颜色的每一侧，该属性的值都按1计数（其他印象计数器递增，除了fullColorImpressionsCompleted（114））之外）。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Page attributes (130 - 149 decimal)
+
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Page attributes (130 - 149 decimal)
+
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
pagesRequested(130), Integer32 (-2..2147483647) INTEGER: The number of logical pages requested by the job to be processed.
pagesRequested（130），Integer32（-2..2147483647）INTEGER：作业请求处理的逻辑页数。
pagesCompleted(131), Integer32 (-2..2147483647) INTEGER: The number of logical pages completed for this job so far.
pagesCompleted（131），Integer32（-2..2147483647）INTEGER：迄今为止此作业已完成的逻辑页数。
For implementations where multiple copies are produced by the interpreter with only a single pass over the data, the final value SHALL be equal to the value of the pagesRequested object. For implementations where multiple copies are produced by the interpreter by processing the data for each copy, the final value SHALL be a multiple of the value of the pagesRequested object.
对于解释器仅通过一次数据传递生成多个副本的实现，最终值应等于页面请求对象的值。对于解释器通过处理每个副本的数据生成多个副本的实现，最终值应为页面请求对象值的倍数。
NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy.
注意-有关在每个文档副本上重置的属性，请参阅ImpressionCompletedCurrentCopy和pagesCompletedCurrentCopy属性。
NOTE - The pagesCompleted object can be used with the pagesRequested object to provide an indication of the relative progress of the job, provided that the multiplicative factor is taken into account for some implementations of multiple copies.
注意-pagesCompleted对象可与pagesRequested对象一起使用，以提供作业相对进度的指示，前提是在多个副本的某些实现中考虑了乘法因子。
pagesCompletedCurrentCopy(132), Integer32 (-2..2147483647) INTEGER: The number of logical pages completed for the current copy of the document so far. This value SHALL be reset to 0 for each document in the job and for each document copy.
pagesCompletedCurrentCopy（132），Integer32（-2..2147483647）INTEGER：到目前为止文档当前副本已完成的逻辑页数。对于作业中的每个文件和每个文件副本，该值应重置为0。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Sheet attributes (150 - 169 decimal)
+
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Sheet attributes (150 - 169 decimal)
+
+ See the definition of 'impression', 'sheet', and 'page'
+ in Section 2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
sheetsRequested(150), Integer32 (-2..2147483647) INTEGER: The total number of medium sheets requested to be produced for this job.
sheetsRequested（150），Integer32（-2..2147483647）INTEGER：请求为此作业生成的中页总数。
Unlike the jmJobKOctetsPerCopyRequested and jmJobImpressionsPerCopyRequested attributes, the sheetsRequested(150) attribute SHALL include the multiplicative factor contributed by the number of copies and so is the total number of sheets to be produced by the job, as opposed to the size of the document(s) submitted.
与jmJobKOctetsPerCopyRequested和jmJobImpressionsPerCopyRequested属性不同，sheetsRequested（150）属性应包括副本数量的乘法因子，以及作业生成的图纸总数，而不是提交的文件的大小。
sheetsCompleted(151), Integer32 (-2..2147483647) INTEGER: The total number of medium sheets that have completed marking and stacking for the entire job so far whether those sheets have been processed on one side or on both.
sheets completed（151），Integer32（-2..2147483647）INTEGER：到目前为止，已完成整个作业标记和堆叠的中页总数，无论这些中页是单面处理还是双面处理。
sheetsCompletedCurrentCopy(152), Integer32 (-2..2147483647) INTEGER: The number of medium sheets that have completed marking and stacking for the current copy of a document in the job so far whether those sheets have been processed on one side or on both.
sheetsCompletedCurrentCopy（152），Integer32（-2..2147483647）INTEGER：到目前为止，已为作业中文档的当前副本完成标记和堆叠的中页数，无论这些中页是在一侧还是在两侧进行处理。
The value of this attribute SHALL be 0 before the job starts processing and SHALL be reset to 1 after the first sheet of each document and document copy in the job is processed and stacked.
在作业开始处理之前，该属性的值应为0，并且在作业中的每个文档和文档副本的第一张被处理和堆叠之后，该属性的值应重置为1。
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) (170 - 189)
+
+ Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to
+ users, i.e., a 'thermometer'.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Resources attributes (requested and consumed) (170 - 189)
+
+ Pairs of these attributes can be used by monitoring
+ applications to show an indication of relative usage to
+ users, i.e., a 'thermometer'.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mediumRequested(170), JmMediumTypeTC AND/OR JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The type AND/OR OCTETS: MULTI-ROW: the name of the medium that is required by the job.
mediumRequested（170）、JmMediumTypeTC和/或JmJobStringTC（大小（0..63））整数：多行：类型和/或八位字节：多行：作业所需的介质的名称。
NOTE - The name (JmJobStringTC) values correspond to the name values of the prtInputMediaName object in the Printer MIB [print-mib] and the name, size, and input tray values of the IPP 'media' attribute [ipp-model].
注意-名称（JmJobStringTC）值对应于打印机MIB[print MIB]中prtInputMediaName对象的名称值以及IPP“media”属性[IPP model]的名称、大小和输入托盘值。
mediumConsumed(171), Integer32 (-2..2147483647) AND JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The number of sheets AND OCTETS: MULTI-ROW: the name of the medium that has been consumed so far whether those sheets have been processed on one side or on both.
mediumConsumed（171）、Integer32（-2..2147483647）和JmJobStringTC（SIZE（0..63））INTEGER:MULTI-ROW：工作表和八位字节数：MULTI-ROW：到目前为止已使用的介质的名称，无论这些工作表是在一侧处理还是在两侧处理。
This attribute SHALL have both Integer32 and OCTET STRING (represented as JmJobStringTC) values.
该属性应具有Integer32和八位字符串（表示为JmJobStringTC）值。
NOTE - The name (JmJobStringTC) values correspond to the name values of the prtInputMediaName object in the Printer MIB [print-mib] and the name, size, and input tray values of the IPP 'media' attribute [ipp-model].
注意-名称（JmJobStringTC）值对应于打印机MIB[print MIB]中prtInputMediaName对象的名称值以及IPP“media”属性[IPP model]的名称、大小和输入托盘值。
colorantRequested(172), Integer32 (-2..2147483647) AND/OR JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in the Printer MIB [print-mib] AND/OR OCTETS: MULTI-ROW: the name of the colorant requested.
colorantRequested（172）、Integer32（-2..2147483647）和/或JmJobStringTC（大小（0..63））INTEGER:多行：打印机MIB[print MIB]中的索引（prtMarkerColorantIndex）和/或八位字节：多行：请求的着色剂名称。
NOTE - The name (JmJobStringTC) values correspond to the name values of the prtMarkerColorantValue object in the Printer MIB. Examples are: red, blue.
注意-名称（JmJobStringTC）值与打印机MIB中prtMarkerColorantValue对象的名称值相对应。例如：红色、蓝色。
colorantConsumed(173), Integer32 (-2..2147483647) AND/OR JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The index (prtMarkerColorantIndex) in the Printer MIB [print-mib] AND/OR OCTETS: MULTI-ROW: the name of the colorant consumed.
着色剂消耗（173）、整数32（-2..2147483647）和/或JmJobStringTC（大小（0..63））整数：多行：打印机MIB[print MIB]中的索引（prtMarkerColorantIndex）和/或八位字节：多行：消耗着色剂的名称。
NOTE - The name (JmJobStringTC) values correspond to the name values of the prtMarkerColorantValue object in the Printer MIB. Examples are: red, blue
注意-名称（JmJobStringTC）值与打印机MIB中prtMarkerColorantValue对象的名称值相对应。例如：红色、蓝色
mediumTypeConsumed(174), Integer32 (-2..2147483647) AND JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The number of sheets of the indicated medium type that has been consumed so far whether those sheets have been processed on one side or on both AND OCTETS: MULTI-ROW: the name of that medium type.
mediumTypeConsumed（174）、Integer32（-2..2147483647）和JmJobStringTC（SIZE（0..63））INTEGER:MULTI-ROW：到目前为止已使用的指示介质类型的纸张数量，无论这些纸张是在一侧还是在两侧进行处理，以及OCTETS:MULTI-ROW：该介质类型的名称。
This attribute SHALL have both Integer32 and OCTET STRING (represented as JmJobStringTC) values.
该属性应具有Integer32和八位字符串（表示为JmJobStringTC）值。
NOTE - The type name (JmJobStringTC) values correspond to the type name values of the prtInputMediaType object in the Printer MIB [print-mib]. Values are: 'stationery', 'transparency', 'envelope', etc. These medium type names correspond to the enum values of JmMediumTypeTC used in the mediumRequested attribute.
注意-类型名称（JmJobStringTC）值与打印机MIB[print MIB]中prtInputMediaType对象的类型名称值相对应。值为：“信纸”、“透明度”、“信封”等。这些介质类型名称对应于mediumRequested属性中使用的JmMediumTypeTC的枚举值。
mediumSizeConsumed(175), Integer32 (-2..2147483647) AND JmJobStringTC (SIZE(0..63)) INTEGER: MULTI-ROW: The number of sheets of the indicated medium size that has been consumed so far whether those sheets have been processed on one side or on both AND OCTETS: MULTI-ROW: the name of that medium size.
mediumSizeConsumed（175）、Integer32（-2..2147483647）和JmJobStringTC（SIZE（0..63））INTEGER:MULTI-ROW：到目前为止已使用的所示中等大小的纸张数量，无论这些纸张是在一侧还是在两侧进行处理，以及OCTETS:MULTI-ROW：该中等大小的名称。
This attribute SHALL have both Integer32 and OCTET STRING (represented as JmJobStringTC) values.
该属性应具有Integer32和八位字符串（表示为JmJobStringTC）值。
NOTE - The size name (JmJobStringTC) values correspond to the size name values in the Printer MIB [print-mib] Appendix B. These size name values are also a subset of the keyword values defined by [ipp-model] for the 'media' Job Template attribute. Values are: 'letter', 'a', 'iso-a4', 'jis-b4', etc.
注意-尺寸名称（JmJobStringTC）值与打印机MIB[print MIB]附录B中的尺寸名称值相对应。这些尺寸名称值也是[ipp model]为“介质”作业模板属性定义的关键字值的子集。数值为：“字母”、“a”、“iso-a4”、“jis-b4”等。
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Time attributes (set by server or device) (190 - 209 decimal)
+
+ This section of attributes are ones that are set by the
+ server or device that accepts jobs. Two forms of time are
+ provided. Each form is represented in a separate attribute.
+ See section 3.1.2 and section 3.1.3 for the
+ conformance requirements for time attribute for agents and
+ monitoring applications, respectively. The two forms are:
+
+ 'DateAndTime' is an 8 or 11 octet binary encoded year,
+ month, day, hour, minute, second, deci-second with
+ optional offset from UTC. See SNMPv2-TC [SMIv2-TC].
+
+ NOTE: 'DateAndTime' is not printable characters; it is
+ binary.
+
+ 'JmTimeStampTC' is the time of day measured in the number of
+ seconds since the system was booted.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Time attributes (set by server or device) (190 - 209 decimal)
+
+ This section of attributes are ones that are set by the
+ server or device that accepts jobs. Two forms of time are
+ provided. Each form is represented in a separate attribute.
+ See section 3.1.2 and section 3.1.3 for the
+ conformance requirements for time attribute for agents and
+ monitoring applications, respectively. The two forms are:
+
+ 'DateAndTime' is an 8 or 11 octet binary encoded year,
+ month, day, hour, minute, second, deci-second with
+ optional offset from UTC. See SNMPv2-TC [SMIv2-TC].
+
+ NOTE: 'DateAndTime' is not printable characters; it is
+ binary.
+
+ 'JmTimeStampTC' is the time of day measured in the number of
+ seconds since the system was booted.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
jobSubmissionToServerTime(190), JmTimeStampTC AND/OR DateAndTime INTEGER: Configuration 3 only: The time AND/OR OCTETS: the date and time that the job was submitted to the server (as distinguished from the device which uses jobSubmissionTime).
jobSubmissionToServerTime（190）、JmTimeStampTC和/或DateAndTime整数：仅配置3：时间和/或八位字节：作业提交到服务器的日期和时间（区别于使用jobSubmissionTime的设备）。
jobSubmissionTime(191), JmTimeStampTC AND/OR DateAndTime INTEGER: Configurations 1, 2, and 3: The time AND/OR OCTETS: the date and time that the job was submitted to the server or device to which the agent is providing access.
jobSubmissionTime（191）、JmTimeStampTC和/或DateAndTime整数：配置1、2和3：时间和/或八位字节：作业提交到代理提供访问的服务器或设备的日期和时间。
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.
jobStartedBeingHeldTime（192）、JmTimeStampTC和/或DateAndTime整数：时间和/或八位字节：作业上次进入pendingHeld状态的日期和时间。如果作业从未进入pendingHeld状态，则该值应为“0”或该属性不在表中。
jobStartedProcessingTime(193), JmTimeStampTC AND/OR DateAndTime INTEGER: The time AND/OR OCTETS: the date and time that the job started processing.
jobStartedProcessingTime（193）、JmTimeStampTC和/或DateAndTime整数：时间和/或八位字节：作业开始处理的日期和时间。
jobCompletionTime(194), JmTimeStampTC AND/OR DateAndTime INTEGER: The time AND/OR OCTETS: the date and time that the job entered the completed, canceled, or aborted state.
jobCompletionTime（194）、JmTimeStampTC和/或DateAndTime整数：时间和/或八位字节：作业进入完成、取消或中止状态的日期和时间。
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.
jobProcessingCPUTime（195）整数32（-2..2147483647）单位“秒”整数：作业处于处理状态的CPU时间（秒）。如果作业进入ProcessingsStopped状态，则不应包括经过的时间。换句话说，当在同一设备上再次处理同一作业时，jobProcessingCPUTime值应该是相对可重复的。
The JmJobStateReasonsNTC (N=1..4) textual-conventions are used with the jmJobStateReasons1 object and jobStateReasonsN (N=2..4), respectively, to provide additional information regarding the current jmJobState object value. These values MAY be used with any job state or states for which the reason makes sense.
JmJobStateReasonsNTC（N=1..4）文本约定分别与jmJobStateReasons1对象和jobStateReasonsN（N=2..4）一起使用，以提供有关当前jmJobState对象值的附加信息。这些值可用于任何作业状态或原因有意义的状态。
NOTE - While values cannot be added to the jmJobState object without impacting deployed clients that take actions upon receiving jmJobState values, it is the intent that additional JmJobStateReasonsNTC enums can be defined and registered without impacting such deployed clients. In other words, the jmJobStateReasons1 object and jobStateReasonsN attributes are intended to be extensible.
注意-虽然无法将值添加到jmJobState对象中而不影响在接收jmJobState值时采取操作的已部署客户端，但其目的是可以定义和注册其他JmJobStateReasonsNTC枚举，而不影响此类已部署客户端。换句话说，jmJobStateReasons1对象和jobStateReasonsN属性是可扩展的。
NOTE - The Job Monitoring MIB contains a superset of the IPP values [ipp-model] for the IPP 'job-state-reasons' attribute, since the Job Monitoring MIB is intended to cover other job submission protocols as well. Also some of the names of the reasons have been changed from ' printer' to 'device', since the Job Monitoring MIB is intended to cover additional types of devices, including input devices, such as scanners.
注意-作业监控MIB包含IPP“作业状态原因”属性的IPP值[IPP模型]的超集，因为作业监控MIB也旨在涵盖其他作业提交协议。此外，一些原因的名称已从“打印机”更改为“设备”，因为作业监控MIB旨在涵盖其他类型的设备，包括输入设备，如扫描仪。
The following standard values are defined (in hexadecimal) as powers of two, since multiple values MAY be used at the same time. For ease of understanding, the JmJobStateReasons1TC reasons are presented in the order in which the reasons are likely to occur (if implemented), starting with the 'jobIncoming' value and ending with the ' jobCompletedWithErrors' value.
以下标准值（十六进制）定义为二的幂，因为可以同时使用多个值。为便于理解，JmJobStateReasons1TC原因按可能发生的顺序（如果已实现）显示，从“jobIncoming”值开始，以“jobCompletedWithErrors”值结束。
other 0x1 The job state reason is not one of the standardized or registered reasons.
其他0x1作业状态原因不是标准化或注册原因之一。
unknown 0x2 The job state reason is not known to the agent or is indeterminent.
未知0x2代理不知道或不确定作业状态原因。
jobIncoming 0x4 The job has been accepted by the server or device, but the server or device is expecting (1) additional operations from the client to finish creating the job and/or (2) is accessing/accepting document data.
jobIncoming 0x4作业已被服务器或设备接受，但服务器或设备期望（1）客户端执行其他操作以完成创建作业和/或（2）访问/接受文档数据。
submissionInterrupted 0x8 The job was not completely submitted for some unforeseen reason, such as: (1) the server has crashed before the job was closed by the client, (2) the server or the document transfer method has crashed in some non-recoverable way before the document data was entirely transferred to the server, (3) the client crashed or failed to close the job before the time-out period.
submissionInterrupted 0x8由于某些不可预见的原因，作业未完全提交，例如：（1）服务器在客户端关闭作业之前崩溃，（2）服务器或文档传输方法在文档数据完全传输到服务器之前以某种不可恢复的方式崩溃，（3）客户端崩溃或未能在超时期间之前关闭作业。
jobOutgoing 0x10 Configuration 2 only: The server is transmitting the job to the device.
jobOutgoing 0x10仅限配置2：服务器正在将作业传输到设备。
jobHoldSpecified 0x20 The value of the job's jobHold(52) attribute is TRUE. The job SHALL NOT be a candidate for processing until this reason is removed and there are no other reasons to hold the job.
jobHold指定0x20作业的jobHold（52）属性的值为TRUE。在该原因消除且无其他原因保留该职位之前，该职位不得作为处理候选人。
jobHoldUntilSpecified 0x40 The value of the job's jobHoldUntil(53) attribute specifies a time period that is still in the future. The job SHALL NOT be a candidate for processing until this reason is removed and there are no other reasons to hold the job.
jobHoldUntil指定0x40作业的jobHoldUntil（53）属性的值指定仍在未来的时间段。在该原因消除且无其他原因保留该职位之前，该职位不得作为处理候选人。
jobProcessAfterSpecified 0x80 The value of the job's jobProcessAfterDateAndTime(51) attribute specifies a time that is still in the future. The job SHALL NOT be a candidate for processing until this reason is removed and there are no other reasons to hold the job.
jobProcessAfterSpecified 0x80作业的jobProcessAfterDateAndTime（51）属性的值指定仍在未来的时间。在该原因消除且无其他原因保留该职位之前，该职位不得作为处理候选人。
resourcesAreNotReady 0x100 At least one of the resources needed by the job, such as media, fonts, resource objects, etc., is not ready on any of the physical devices for which the job is a candidate. This condition MAY be detected when the job is accepted, or subsequently while the job is pending or processing, depending on implementation.
ResourcesRenoTready 0x100作业所需的至少一个资源（如媒体、字体、资源对象等）未在作业作为候选对象的任何物理设备上就绪。此情况可能在接受作业时检测到，或随后在作业挂起或处理时检测到，具体取决于实现。
deviceStoppedPartly 0x200 One or more, but not all, of the devices to which the job is assigned are stopped. If all of the devices are stopped (or the only device is stopped), the deviceStopped reason SHALL be used.
DevicesToppedParty 0x200作业分配到的一个或多个（但不是全部）设备已停止。如果所有设备都停止（或只有一个设备停止），则应使用设备停止原因。
deviceStopped 0x400 The device(s) to which the job is assigned is (are all) stopped.
设备停止0x400分配作业的设备（全部）停止。
jobInterpreting 0x800 The device to which the job is assigned is interpreting the document data.
作业解释0x800分配作业的设备正在解释文档数据。
jobPrinting 0x1000 The output device to which the job is assigned is marking media. This value is useful for servers and output devices which spend a great deal of time processing (1) when no marking is happening and then want to show that marking is now happening or (2) when the job is in the process of being canceled or aborted while the job remains in the processing state, but the marking has not yet stopped so that impression or sheet counts are still increasing for the job.
作业打印0x1000分配作业的输出设备是标记介质。此值对于花费大量时间处理的服务器和输出设备非常有用（1）当没有标记发生时，然后希望显示标记正在发生；或（2）当作业处于处理状态时，作业处于取消或中止过程中，但是标记还没有停止，因此工作的印痕或纸张数量仍在增加。
jobCanceledByUser 0x2000 The job was canceled by the owner of the job, i.e., by a user whose name is the same as the value of the job's jmJobOwner object, or by some other authorized end-user, such as a member of the job owner's security group.
jobCanceledByUser 0x2000作业由作业的所有者（即名称与作业的jmJobOwner对象的值相同的用户）或其他授权最终用户（如作业所有者安全组的成员）取消。
jobCanceledByOperator 0x4000 The job was canceled by the operator, i.e., by a user who has been authenticated as having operator privileges (whether local or remote).
jobCanceledByOperator 0x4000操作员取消了作业，即，由已被验证为具有操作员权限（本地或远程）的用户取消了作业。
jobCanceledAtDevice 0x8000 The job was canceled by an unidentified local user, i.e., a user at a console at the device.
JobCanceledDevice 0x8000该作业被身份不明的本地用户（即设备控制台上的用户）取消。
abortedBySystem 0x10000 The job (1) is in the process of being aborted, (2) has been aborted by the system and placed in the 'aborted' state, or (3) has been aborted by the system and placed in the 'pendingHeld' state, so that a user or operator can manually try the job again.
abortedBySystem 0x10000作业（1）正在中止过程中，（2）已被系统中止并处于“中止”状态，或（3）已被系统中止并处于“挂起”状态，以便用户或操作员可以手动重试该作业。
processingToStopPoint 0x20000 The requester has issued an operation to cancel or interrupt the job or the server/device has aborted the job, but the server/device is still performing some actions on the job until a specified stop point occurs or job termination/cleanup is completed.
ProcessingToSupport 0x20000请求者已发出取消或中断作业的操作，或服务器/设备已中止作业，但服务器/设备仍在对作业执行某些操作，直到出现指定的停止点或作业终止/清理完成。
This reason is recommended to be used in conjunction with the processing job state to indicate that the server/device is still performing some actions on the job while the job remains in the processing state. After all the job's resources consumed counters have stopped incrementing, the server/device moves the job from the processing state to the canceled or aborted job states.
建议将此原因与处理作业状态结合使用，以指示服务器/设备仍在作业上执行某些操作，而作业仍处于处理状态。在作业的所有资源消耗计数器停止递增后，服务器/设备将作业从处理状态移动到已取消或中止的作业状态。
serviceOffLine 0x40000 The service or document transform is off-line and accepting no jobs. All pending jobs are put into the pendingHeld state. This situation could be true if the service's or document transform's input is impaired or broken.
serviceOffLine 0x40000服务或文档转换处于脱机状态，不接受任何作业。所有挂起的作业都被置于pendingHeld状态。如果服务或文档转换的输入受损或损坏，则这种情况可能是真实的。
jobCompletedSuccessfully 0x80000 The job completed successfully.
作业已成功完成0x80000作业已成功完成。
jobCompletedWithWarnings 0x100000 The job completed with warnings.
job completed WithWarnings 0x100000作业已完成，但出现警告。
jobCompletedWithErrors 0x200000 The job completed with errors (and possibly warnings too).
JobCompletedWitherErrors 0x200000作业已完成，但有错误（可能还有警告）。
The following additional job state reasons have been added to represent job states that are in ISO DPA [iso-dpa] and other job submission protocols:
添加了以下附加作业状态原因，以表示ISO DPA[ISO DPA]和其他作业提交协议中的作业状态：
jobPaused 0x400000 The job has been indefinitely suspended by a client issuing an operation to suspend the job so that other jobs may proceed using the same devices. The client MAY issue an operation to resume the paused job at any time, in which case the agent SHALL remove the jobPaused values from the job's jmJobStateReasons1 object and the job is eventually resumed at or near the point where the job was paused.
jobPaused 0x400000客户端发出挂起作业的操作，使其他作业可以使用相同的设备继续，从而无限期挂起作业。客户机可随时发出恢复暂停作业的操作，在这种情况下，代理应从作业的jmJobStateReasons1对象中删除jobPaused值，并最终在作业暂停点或其附近恢复作业。
jobInterrupted 0x800000 The job has been interrupted while processing by a client issuing an operation that specifies another job to be run instead of the current job. The server or device will automatically resume the interrupted job when the interrupting job completes.
jobInterrupted 0x800000客户端发出指定要运行的另一个作业而不是当前作业的操作时，作业被中断。当中断作业完成时，服务器或设备将自动恢复中断的作业。
jobRetained 0x1000000 The job is being retained by the server or device with all of the job's document data (and submitted resources, such as fonts, logos, and forms, if any). Thus a client could issue an operation to the server or device to either (1) re-do the job (or a copy of the job) on the same server or device or (2) resubmit the job to another server or device. When a client could no longer re-do/resubmit the job, such as after the document data has been discarded, the agent SHALL remove the jobRetained value from the jmJobStateReasons1 object.
jobRetained 0x1000000作业由服务器或设备与作业的所有文档数据（以及提交的资源，如字体、徽标和表单，如果有）一起保留。因此，客户端可以向服务器或设备发出操作，以（1）在同一服务器或设备上重新执行作业（或作业的副本），或（2）将作业重新提交到另一服务器或设备。当客户端无法再重新执行/重新提交作业时，例如在文档数据被丢弃后，代理应从jmJobStateReasons1对象中删除jobRetained值。
These bit definitions are the equivalent of a type 2 enum except that combinations of bits may be used together. See section 3.7.1.2. The remaining bits are reserved for future standardization and/or registration.
这些位定义与类型2枚举等效，只是位的组合可以一起使用。见第3.7.1.2节。剩余的位保留用于将来的标准化和/或注册。
The following standard values are defined (in hexadecimal) as powers of two, since multiple values MAY be used at the same time.
以下标准值（十六进制）定义为二的幂，因为可以同时使用多个值。
cascaded 0x1 An outbound gateway has transmitted all of the job's job and document attributes and data to another spooling system.
级联0x1出站网关已将作业的所有作业和文档属性以及数据传输到另一个假脱机系统。
deletedByAdministrator 0x2 The administrator has deleted the job.
deletedByAdministrator 0x2管理员已删除作业。
discardTimeArrived 0x4 The job has been deleted due to the fact that the time specified by the job's job-discard-time attribute has arrived.
DiscardTimeArrized 0x4由于作业的“作业丢弃时间”属性指定的时间已到，作业已被删除。
postProcessingFailed 0x8 The post-processing agent failed while trying to log accounting attributes for the job; therefore the job has been placed into the completed state with the jobRetained jmJobStateReasons1 object value for a system-defined period of time, so the administrator can examine it, resubmit it, etc.
后处理失败0x8后处理代理尝试记录作业的记帐属性时失败；因此，在系统定义的一段时间内，作业已被置于具有jobRetained jmJobStateReasons1对象值的已完成状态，因此管理员可以对其进行检查、重新提交等。
jobTransforming 0x10 The server/device is interpreting document data and producing another electronic representation.
作业0x10服务器/设备正在解释文档数据并生成另一个电子表示。
maxJobFaultCountExceeded 0x20 The job has faulted several times and has exceeded the administratively defined fault count limit.
MaxJobFaultCount超过0x20作业已多次出现故障，并且已超过管理定义的故障计数限制。
devicesNeedAttentionTimeOut 0x40 One or more document transforms that the job is using needs human intervention in order for the job to make progress, but the human intervention did not occur within the site-settable time-out value.
DeviceNeedAttentionTimeout 0x40作业正在使用的一个或多个文档转换需要人工干预才能使作业取得进展，但人工干预未在站点可设置的超时值内发生。
needsKeyOperatorTimeOut 0x80 One or more devices or document transforms that the job is using need a specially trained operator (who may need a key to unlock the device and gain access) in order for the job to make progress, but the key operator intervention did not occur within the site-settable time-out value.
needsKeyOperatorTimeOut 0x80作业正在使用的一个或多个设备或文档转换需要经过专门培训的操作员（可能需要钥匙解锁设备并获得访问权限）才能使作业取得进展，但在站点可设置的超时值内未发生钥匙操作员干预。
jobStartWaitTimeOut 0x100 The server/device has stopped the job at the beginning of processing to await human action, such as installing a special cartridge or special non-standard media, but the job was not resumed within the site-settable time-out value and the server/device has transitioned the job to the pendingHeld state.
jobStartWaitTimeOut 0x100服务器/设备已在处理开始时停止作业，等待人工操作，例如安装特殊盒式磁带或特殊非标准介质，但作业未在站点可设置的超时值内恢复，服务器/设备已将作业转换为pendingHeld状态。
jobEndWaitTimeOut 0x200 The server/device has stopped the job at the end of processing to await human action, such as removing a special cartridge or restoring standard media, but the job was not resumed within the site-settable time-out value and the server/device has transitioned the job to the completed state.
jobEndWaitTimeOut 0x200服务器/设备已在处理结束时停止作业，以等待人工操作，例如卸下特殊盒带或还原标准介质，但作业未在站点可设置的超时值内恢复，服务器/设备已将作业转换为完成状态。
jobPasswordWaitTimeOut 0x400 The server/device has stopped the job at the beginning of processing to await input of the job's password, but the password was not received within the site-settable time-out value.
jobPasswordWaitTimeOut 0x400服务器/设备已在处理开始时停止作业，以等待输入作业的密码，但在站点可设置的超时值内未收到密码。
deviceTimedOut 0x800 A device that the job was using has not responded in a period specified by the device's site-settable attribute.
deviceTimedOut 0x800作业正在使用的设备在设备的“站点可设置”属性指定的时间段内没有响应。
connectingToDeviceTimeOut 0x1000 The server is attempting to connect to one or more devices which may be dial-up, polled, or queued, and so may be busy with traffic from other systems, but server was unable to connect to the device within the site-settable time-out value.
ConnectionToDeviceTimeout 0x1000服务器正试图连接到一个或多个设备，这些设备可能是拨号、轮询或排队的，因此可能正忙于来自其他系统的通信，但服务器无法在站点可设置的超时值内连接到该设备。
transferring 0x2000 The job is being transferred to a down stream server or downstream device.
传输0x2000作业正在传输到下游服务器或下游设备。
queuedInDevice 0x4000 The server/device has queued the job in a down stream server or downstream device.
queuedInDevice 0x4000服务器/设备已将下游服务器或下游设备中的作业排入队列。
jobQueued 0x8000 The server/device has queued the document data.
jobQueued 0x8000服务器/设备已将文档数据排入队列。
jobCleanup 0x10000 The server/device is performing cleanup activity as part of ending normal processing.
jobCleanup 0x10000服务器/设备正在执行清理活动，作为结束正常处理的一部分。
jobPasswordWait 0x20000 The server/device has selected the job to be next to process, but instead of assigning resources and starting the job processing, the server/device has transitioned the job to the pendingHeld state to await entry of a password (and dispatched another job, if there is one).
jobPasswordWait 0x20000服务器/设备已选择下一个要处理的作业，但服务器/设备没有分配资源并开始作业处理，而是将作业转换为pendingHeld状态以等待输入密码（并调度另一个作业，如果有）。
validating 0x40000 The server/device is validating the job after accepting the job.
验证0x40000服务器/设备在接受作业后正在验证作业。
queueHeld 0x80000 The operator has held the entire job set or queue.
QueueHold 0x80000操作员已保留整个作业集或队列。
jobProofWait 0x100000 The job has produced a single proof copy and is in the pendingHeld state waiting for the requester to issue an operation to release the job to print normally, obeying any job and document copy attributes that were originally submitted.
jobProofWait 0x100000作业已生成一份校对副本，并处于pendingHeld状态，等待请求者发出操作以释放作业以正常打印，遵守最初提交的任何作业和文档副本属性。
heldForDiagnostics 0x200000 The system is running intrusive diagnostics, so that all jobs are being held.
HeldFordDiagnostics 0x200000系统正在运行侵入性诊断，因此所有作业都被保留。
noSpaceOnServer 0x800000 There is no room on the server to store all of the job.
noSpaceOnServer 0x800000服务器上没有空间存储所有作业。
pinRequired 0x1000000 The System Administrator settable device policy is (1) to require PINs, and (2) to hold jobs that do not have a pin supplied as an input parameter when the job was created.
pinRequired 0x1000000系统管理员可设置的设备策略是（1）要求使用pin，以及（2）在创建作业时保留没有作为输入参数提供pin的作业。
exceededAccountLimit 0x2000000 The account for which this job is drawn has exceeded its limit. This condition SHOULD be detected before the job is scheduled so that the user does not wait until his/her job is scheduled only to find that the account is overdrawn. This condition MAY also occur while the job is processing either as processing begins or part way through processing.
exceededAccountLimit 0x2000000提取此作业的帐户已超出其限制。在安排作业之前应检测到此情况，以便用户不会等到安排了作业后才发现帐户透支。在处理开始或部分处理过程中处理作业时，也可能出现这种情况。
heldForRetry 0x4000000 The job encountered some errors that the server/device could not recover from with its normal retry procedures, but the error might not be encountered if the job is processed again in the future. Example cases are phone number busy or remote file system in-accessible. For such a situation, the server/device SHALL transition the job from the processing to the pendingHeld, rather than to the aborted state.
HeldForry 0x4000000作业遇到一些服务器/设备无法通过正常重试过程恢复的错误，但如果将来再次处理作业，则可能不会遇到该错误。例如，电话号码占线或可访问的远程文件系统。对于这种情况，服务器/设备应将作业从处理状态转换为挂起状态，而不是中止状态。
The following values are from the X/Open PSIS draft standard:
以下值来自X/O标准草案：
canceledByShutdown 0x8000000 The job was canceled because the server or device was shutdown before completing the job.
canceledByShutdown 0x8000000作业已取消，因为服务器或设备在完成作业之前已关闭。
deviceUnavailable 0x10000000 This job was aborted by the system because the device is currently unable to accept jobs.
deviceUnavailable 0x10000000此作业已被系统中止，因为设备当前无法接受作业。
wrongDevice 0x20000000 This job was aborted by the system because the device is unable to handle this particular job; the spooler SHOULD try another device or the user should submit the job to another device.
错误设备0x20000000由于设备无法处理此特定作业，系统已中止此作业；后台处理程序应尝试其他设备，或者用户应将作业提交到其他设备。
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.
坏作业0x40000000此作业已被系统中止，因为此作业存在重大问题，例如格式错误的PDL；后台处理程序甚至不应该尝试其他设备。
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2.
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。见第3.7.1.2节。
This textual-convention is used with the jobStateReasons3 attribute to provides additional information regarding the jmJobState object. The following standard values are defined (in hexadecimal) as powers of two, since multiple values may be used at the same time:
此文本约定与jobStateReasons3属性一起使用，以提供有关jmJobState对象的附加信息。以下标准值（十六进制）定义为二的幂，因为可以同时使用多个值：
jobInterruptedByDeviceFailure 0x1 A device or the print system software that the job was using has failed while the job was processing. The server or device is keeping the job in the pendingHeld state until an operator can determine what to do with the job.
job Interrupted By device故障0x1处理作业时，作业使用的设备或打印系统软件出现故障。服务器或设备将作业保持在pendingHeld状态，直到操作员确定如何处理作业。
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2. The remaining bits are reserved for future standardization and/or registration.
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。见第3.7.1.2节。剩余的位保留用于将来的标准化和/或注册。
This textual-convention is used with the jobStateReasons4 attribute to provides additional information regarding the jmJobState object. The following standard values are defined (in hexadecimal) as powers of two, since multiple values MAY be used at the same time.
此文本约定与jobStateReasons4属性一起使用，以提供有关jmJobState对象的附加信息。以下标准值（十六进制）定义为二的幂，因为可以同时使用多个值。
None defined at this time.
此时未定义任何。
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2. The remaining bits are reserved for future standardization and/or registration.
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。见第3.7.1.2节。剩余的位保留用于将来的标准化和/或注册。
There are a number of objects and attributes for monitoring the progress of a job. These objects and attributes count the number of K octets, impressions, sheets, and pages requested or completed. For impressions and sheets, "completed" means stacked, unless the implementation is unable to detect when each sheet is stacked, in which case stacked is approximated when processing of each sheet completes. There are objects and attributes for the overall job and for the current copy of the document currently being stacked. For the latter, the rate at which the various objects and attributes count depends on the sheet and document collation of the job.
有许多用于监视作业进度的对象和属性。这些对象和属性统计请求或完成的K个八位字节、印象、工作表和页面的数量。对于印模和板材，“已完成”表示堆叠，除非实现无法检测每个板材何时堆叠，在这种情况下，当每个板材的处理完成时，堆叠近似。总体作业和当前正在堆叠的文档的当前副本都有对象和属性。对于后者，各种对象和属性的计数率取决于作业的工作表和文档排序规则。
Job Collation included sheet collation and document collation. Sheet collation is defined to be the ordering of sheets within a document copy. Document collation is defined to be ordering of document copies within a multi-document job. There are three types of job collation (see terminology definitions in Section 2):
作业排序包括工作表排序和文档排序。图纸排序是指文档副本中图纸的排序。文档排序定义为在多文档作业中对文档副本进行排序。作业排序有三种类型（参见第2节中的术语定义）：
1.uncollatedSheets(3) - No collation of the sheets within each document copy, i.e., each sheet of a document that is to produce multiple copies is replicated before the next sheet in the document is processed and stacked. If the device has an output bin collator, the uncollatedSheets(3) value may actually produce collated sheets as far as the user is concerned (in the output bins). However, when the job collation is the to a monitoring application between a device that has an output bin collator and one that does not.
1.未装订的纸张（3）-每个文件副本内的纸张没有整理，即，在处理和堆叠文件中的下一张纸张之前，复制要产生多份副本的文件的每张纸张。如果设备有一个输出箱装订器，则未装订的纸张（3）值实际上可能会产生用户所关心的已校对的纸张（在输出箱中）。但是，当作业排序是监控应用程序的首选项时，在具有输出箱排序器的设备和不具有输出箱排序器的设备之间进行排序。
2.collatedDocuments(4) - Collation of the sheets within each
document copy is performed within the printing device by making
multiple passes over either the source or an intermediate
representation of the document. In addition, when there are
multiple documents per job, the i'th copy of each document is
stacked before the j'th copy of each document, i.e., the
documents are collated within each job copy. For example, if a
job is submitted with documents, A and B, the job is made
available to the end user as: A, B, A, B, .... The '
collatedDocuments(4)' value corresponds to the IPP [ipp-model] '
separate-documents-collated-copies' value of the "multiple-
document-handling" attribute.
2.collatedDocuments(4) - Collation of the sheets within each
document copy is performed within the printing device by making
multiple passes over either the source or an intermediate
representation of the document. In addition, when there are
multiple documents per job, the i'th copy of each document is
stacked before the j'th copy of each document, i.e., the
documents are collated within each job copy. For example, if a
job is submitted with documents, A and B, the job is made
available to the end user as: A, B, A, B, .... The '
collatedDocuments(4)' value corresponds to the IPP [ipp-model] '
separate-documents-collated-copies' value of the "multiple-
document-handling" attribute.
If jobCopiesRequested or documentCopiesRequested = 1, then jobCollationType is defined as 4.
如果jobCopiesRequested或documentCopiesRequested=1，则jobCollationType定义为4。
3.uncollatedDocuments(5) - Collation of the sheets within each
document copy is performed within the printing device by making
multiple passes over either the source or an intermediate
representation of the document. In addition, when there are
multiple documents per job, all copies of the first document in
the job are stacked before the any copied of the next document in
the job, i.e., the documents are uncollated within the job. For
example, if a job is submitted with documents, A and B, the job
is mad available to the end user as: A, A, ..., B, B, .... The
'uncollatedDocuments(5)' value corresponds to the IPP [ipp-model]
'separate-documents-uncollated-copies' value of the "multiple-
document-handling" attribute.
3.uncollatedDocuments(5) - Collation of the sheets within each
document copy is performed within the printing device by making
multiple passes over either the source or an intermediate
representation of the document. In addition, when there are
multiple documents per job, all copies of the first document in
the job are stacked before the any copied of the next document in
the job, i.e., the documents are uncollated within the job. For
example, if a job is submitted with documents, A and B, the job
is mad available to the end user as: A, A, ..., B, B, .... The
'uncollatedDocuments(5)' value corresponds to the IPP [ipp-model]
'separate-documents-uncollated-copies' value of the "multiple-
document-handling" attribute.
Consider the following four variables that are used to monitor the progress of a job's impressions:
考虑以下四个变量，用来监控工作印象的进展：
1.jmJobImpressionsCompleted - counts the total number of impressions stacked for the job
1.jmJobImpressionsCompleted—统计为作业堆叠的印象总数
2.impressionsCompletedCurrentCopy - counts the number of impressions stacked for the current document copy
2.ImpressionCompletedCurrentCopy—统计当前文档副本的堆叠印痕数
3.sheetCompletedCopyNumber - identifies the number of the copy for the current document being stacked where the first copy is 1.
3.sheetCompletedCopyNumber—标识当前文档的副本编号，其中第一个副本为1。
4.sheetCompletedDocumentNumber - identifies the current document within the job that is being stacked where the first document in a job is 1. NOTE: this attribute SHOULD NOT be implemented for implementations that only support one document per job.
4.sheetCompletedDocumentNumber—标识正在堆叠作业中的当前文档，其中作业中的第一个文档为1。注意：对于每个作业只支持一个文档的实现，不应实现此属性。
For each of the three types of job collation, a job with three copies of two documents (1, 2), where each document consists of 3 impressions, the four variables have the following values as each sheet is stacked for one-sided printing:
对于三种作业排序类型中的每一种，即具有两个文档（1、2）的三份副本的作业，其中每个文档由三个印模组成，当每张纸张堆叠进行单面打印时，四个变量具有以下值：
Job Collation Type = uncollatedSheets(3)
作业排序规则类型=未排序的工作表（3）
jmJobImpressions Impressions sheetCompleted sheetCompleted Completed CompletedCurrent CopyNumber DocumentNumber Copy
jmJobImpressions印象表已完成表已完成当前副本号文档号副本
0 0 0 0 1 1 1 1 2 1 2 1 3 1 3 1 4 2 1 1 5 2 2 1 6 2 3 1 7 3 1 1 8 3 2 1 9 3 3 1 10 1 1 2 11 1 2 2 12 1 3 2 13 2 1 2 14 2 2 2 15 2 3 2 16 3 1 2 17 3 2 2 18 3 3 2
0 0 0 0 1 1 1 1 2 1 2 1 3 1 3 1 4 2 1 1 5 2 2 1 6 2 3 1 7 3 1 1 8 3 2 1 9 3 3 1 10 1 1 2 11 1 2 2 12 1 3 2 13 2 1 2 14 2 2 2 15 2 3 2 16 3 1 2 17 3 2 2 18 3 3 2
Job Collation Type = collatedDocuments(4)
作业排序规则类型=排序规则文档（4）
JmJobImpressions Impressions sheetCompleted sheetCompleted Completed CompletedCurrent CopyNumber DocumentNumber Copy
JmJobImpressions印象表已完成表已完成当前副本号文档号副本
0 0 0 0 1 1 1 1 2 2 1 1 3 3 1 1 4 1 1 2 5 2 1 2 6 3 1 2 7 1 2 1 8 2 2 1 9 3 2 1 10 1 2 2 11 2 2 2 12 3 2 2 13 1 3 1 14 2 3 1 15 3 3 1 16 1 3 2 17 2 3 2 18 3 3 2
0 0 0 0 1 1 1 1 2 2 1 1 3 3 1 1 4 1 1 2 5 2 1 2 6 3 1 2 7 1 2 1 8 2 2 1 9 3 2 1 10 1 2 2 11 2 2 2 12 3 2 2 13 1 3 1 14 2 3 1 15 3 3 1 16 1 3 2 17 2 3 2 18 3 3 2
Job Collation Type = uncollatedDocuments(5)
作业排序规则类型=未附加文档（5）
jmJobImpressions Impressions sheetCompleted sheetCompleted Completed CompletedCurrent CopyNumber DocumentNumber Copy
jmJobImpressions印象表已完成表已完成当前副本号文档号副本
0 0 0 0 1 1 1 1 2 2 1 1 3 3 1 1 4 1 2 1 5 2 2 1 6 3 2 1 7 1 3 1 8 2 3 1 9 3 3 1 10 1 1 2 11 2 1 2 12 3 1 2 13 1 2 2 14 2 2 2 15 3 2 2 16 1 3 2 17 2 3 2 18 3 3 2
0 0 0 0 1 1 1 1 2 2 1 1 3 3 1 1 4 1 2 1 5 2 2 1 6 3 2 1 7 1 3 1 8 2 3 1 9 3 3 1 10 1 1 2 11 2 1 2 12 3 1 2 13 1 2 2 14 2 2 2 15 3 2 2 16 1 3 2 17 2 3 2 18 3 3 2
There are a number of attributes that permit a user, operator or system administrator to identify jobs of interest, such as jobURI, jobName, jobOriginatingHost, etc. In addition, there is a jmJobSubmissionID object that is a text string table index. Being a table index allows a monitoring application to quickly locate and identify a particular job of interest that was submitted from a particular client by the user invoking the monitoring application without having to scan the entire job table. The Job Monitoring MIB needs to provide for identification of the job at both sides of the job submission process. The primary identification point is the client side. The jmJobSubmissionID allows the monitoring application to identify the job of interest from all the jobs currently "known" by the server or device. The value of jmJobSubmissionID can be assigned by either the client's local system or a downstream server or device. The point of assignment depends on the job submission protocol in use.
有许多属性允许用户、操作员或系统管理员识别感兴趣的作业，例如jobURI、jobName、jobOriginatingHost等。此外，还有一个jmJobSubmissionID对象，它是一个文本字符串表索引。作为一个表索引，监控应用程序可以快速定位和识别用户调用监控应用程序从特定客户端提交的感兴趣的特定作业，而无需扫描整个作业表。作业监控MIB需要在作业提交过程的两侧提供作业标识。主要标识点是客户端。jmJobSubmissionID允许监控应用程序从服务器或设备当前“已知”的所有作业中识别感兴趣的作业。jmJobSubmissionID的值可以由客户端的本地系统或下游服务器或设备分配。分配点取决于使用的作业提交协议。
The server/device-side identifier, called the jmJobIndex object, SHALL be assigned by the SNMP Job Monitoring MIB agent when the server or device accepts the jobs from submitting clients. The jmJobIndex object allows the interested party to obtain all objects desired that relate to a particular job. See Section 3.2, entitled ' The Job Tables and the Oldest Active and Newest Active Indexes' for the specification of how the agent SHALL assign the jmJobIndex values.
当服务器或设备接受来自提交客户端的作业时，SNMP作业监控MIB代理应分配称为jmJobIndex对象的服务器/设备端标识符。jmJobIndex对象允许相关方获得与特定作业相关的所有所需对象。有关代理如何分配jmJobIndex值的规范，请参见第3.2节，标题为“作业表和最旧的活动索引和最新的活动索引”。
The MIB provides a mapping table that maps each jmJobSubmissionID value to a corresponding jmJobIndex value generated by the agent, so that an application can determine the correct value for the jmJobIndex value for the job of interest in a single Get operation, given the Job Submission ID. See the jmJobIDGroup.
MIB提供了一个映射表，将每个jmJobSubmissionID值映射到代理生成的相应jmJobIndex值，以便应用程序可以在给定作业提交ID的情况下，在单个Get操作中为感兴趣的作业确定jmJobIndex值的正确值。请参阅jmJobIDGroup。
In some configurations there may be more than one application program that monitors the same job when the job passes from one network entity to another when it is submitted. See configuration 3. When there are multiple job submission IDs, each entity MAY supply an appropriate jmJobSubmissionID value. In this case there would be a separate entry in the jmJobSubmissionID table, one for each jmJobSubmissionID. All entries would map to the same jmJobIndex that contains the job data. When the job is deleted, it is up to the agent to remove all entries that point to the job from the jmJobSubmissionID table as well.
在某些配置中，当作业从一个网络实体传递到另一个网络实体时，可能有多个应用程序监视同一作业。请参阅配置3。当存在多个作业提交ID时，每个实体都可以提供适当的jmJobSubmissionID值。在这种情况下，jmJobSubmissionID表中将有一个单独的条目，每个jmJobSubmissionID对应一个条目。所有条目都将映射到包含作业数据的同一jmJobIndex。删除作业时，代理也可以从jmJobSubmissionID表中删除指向作业的所有条目。
The jobName attribute provides a name that the user supplies as a job attribute with the job. The jobName attribute is not necessarily unique, even for one user, let alone across users.
jobName属性提供了一个名称，用户将该名称作为作业的作业属性提供。jobName属性不一定是唯一的，即使对于一个用户，更不用说跨用户了。
This section specifies the formats for each of the registered Job Submission Ids. This format is used by the JmJobSubmissionIDTypeTC. Each job submission ID is a fixed-length, 48-octet printable US-ASCII [US-ASCII] coded character string containing no control characters, consisting of the following fields:
本节指定每个已注册作业提交ID的格式。此格式由JmJobSubmissionIDTypeTC使用。每个作业提交ID是一个固定长度、48个八位字节的可打印US-ASCII[US-ASCII]编码字符串，不包含任何控制字符，由以下字段组成：
octet 1: The format letter identifying the format. The US-ASCII characters '0-9', 'A-Z', and 'a-z' are assigned in order giving 62 possible formats. octets 2-40: A 39-character, US-ASCII trailing SPACE filled field specified by the format letter, if the data is less than 39 ASCII characters. octets 41-48: A sequential or random US-ASCII number to make the ID quasi-unique.
八位组1：标识格式的格式字母。US-ASCII字符“0-9”、“A-Z”和“A-Z”按顺序分配，给出62种可能的格式。八位字节2-40：如果数据少于39个ASCII字符，则由格式字母指定的39个字符的US-ASCII尾随空格填充字段。八位字节41-48：使ID准唯一的顺序或随机US-ASCII数。
If the client does not supply a job submission ID in the job submission protocol, then the agent SHALL assign a job submission ID using any of the standard formats that are reserved for the agent. Clients SHALL not use formats that are reserved for agents and agents SHALL NOT use formats that are reserved for clients, in order to reduce conflicts in ID generation. See the description for which formats are reserved for clients or for agents.
如果客户未在作业提交协议中提供作业提交ID，则代理应使用为代理保留的任何标准格式分配作业提交ID。客户不得使用为代理保留的格式，代理不得使用为客户保留的格式，以减少ID生成中的冲突。请参阅为客户端或代理保留的格式的说明。
Registration of additional formats may be done following the procedures described in Section 3.7.3.
可按照第3.7.3节所述程序注册其他格式。
The format values defined at the time of completion of this specification are:
本规范完成时定义的格式值为：
Format
Letter Description
------ ------------
'0' Job Owner generated by the server/device
octets 2-40: The last 39 bytes of the jmJobOwner object.
octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the agent.
This format is reserved for agents.
Format
Letter Description
------ ------------
'0' Job Owner generated by the server/device
octets 2-40: The last 39 bytes of the jmJobOwner object.
octets 41-48: The US-ASCII 8-decimal-digit sequential number
assigned by the agent.
This format is reserved for agents.
NOTE - Clients wishing to use a job submission ID that incorporates the job owner, SHALL use format '8', not format '0'.
注意-希望使用包含作业所有者的作业提交ID的客户应使用格式“8”，而不是格式“0”。
'1' Job Name octets 2-40: The last 39 bytes of the jobName attribute. octets 41-48: The US-ASCII 8-decimal-digit random number assigned by the client. This format is reserved for clients.
“1”作业名称八位字节2-40：作业名称属性的最后39个字节。八位字节41-48：客户端分配的US-ASCII 8位十进制随机数。此格式是为客户端保留的。
'2' Client MAC address octets 2-40: The client MAC address: in hexadecimal with each nibble of the 6 octet address being '0'-'9' or 'A' - 'F' (uppercase only). Most significant octet first. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients.
“2”客户端MAC地址八位字节2-40：客户端MAC地址：十六进制，6个八位字节地址的每个半字节为“0”-“9”或“A”-“F”（仅大写）。首先是最重要的八位组。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。
'3' Client URL octets 2-40: The last 39 bytes of the client URL [URI-spec]. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients.
“3”客户端URL八位字节2-40：客户端URL的最后39个字节[URI规范]。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。
'4' Job URI octets 2-40: The last 39 bytes of the URI [URI-spec] assigned by the server or device to the job when the job was submitted for processing. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the agent. This format is reserved for agents.
“4”作业URI八位字节2-40：提交作业进行处理时，服务器或设备分配给作业的URI[URI规范]的最后39个字节。八位字节41-48：代理分配的US-ASCII 8位十进制序列号。此格式为代理保留。
'5' POSIX User Number octets 2-40: The last 39 bytes of a user number, such as POSIX user number. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients.
“5”POSIX用户号八位字节2-40：用户号的最后39个字节，如POSIX用户号。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。
'6' User Account Number octets 2-40: The last 39 bytes of the user account number. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients.
“6”用户帐号八位字节2-40：用户帐号的最后39个字节。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。
'7' DTMF Incoming FAX routing number octets 2-40: The last 39 bytes of the DTMF incoming FAX routing number. octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients.
“7”DTMF传入传真路由号码八位字节2-40：DTMF传入传真路由号码的最后39个字节。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。
'8' Job Owner supplied by the client octets 2-40: The last 39 bytes of the job owner name (that the agent returns in the jmJobOwner object). octets 41-48: The US-ASCII 8-decimal-digit sequential number assigned by the client. This format is reserved for clients. See format '0' which is reserved for agents.
客户端八位字节2-40提供的“8”作业所有者：作业所有者名称的最后39个字节（代理在jmJobOwner对象中返回）。八位字节41-48：客户端分配的US-ASCII 8位十进制序列号。此格式是为客户端保留的。请参阅为代理保留的格式“0”。
'9' Host Name octets 2-40: The last 39 bytes of the host name with trailing SPACES that submitted the job to this server/device using a protocol, such as LPD [RFC1179] which includes the host name in the job submission protocol. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the job id generated by the submitting server (configuration 3) or the client (configuration 1 and 2), such as in the LPD protocol. This format is reserved for clients.
“9”主机名八位字节2-40：主机名的最后39个字节，带有尾随空格，使用协议将作业提交到此服务器/设备，如LPD[RFC1179]，其中包括作业提交协议中的主机名。八位字节41-48：提交服务器（配置3）或客户端（配置1和2）生成的作业id的US-ASCII 8位十进制前导零表示，如在LPD协议中。此格式是为客户端保留的。
'A' AppleTalk Protocol octets 2-40: Contains the AppleTalk printer name, with the first character of the name in octet 2. AppleTalk printer names are a maximum of 31 characters. Any unused portion of this field shall be filled with spaces. octets 41-48: '00000XXX', where 'XXX' is the 3-digit US-ASCII decimal representation of the Connection Id. This format is reserved for agents.
“A”AppleTalk协议八位字节2-40：包含AppleTalk打印机名称，名称的第一个字符位于八位字节2中。AppleTalk打印机名称最多31个字符。该字段的任何未使用部分应填充空格。八位字节41-48:'00000 XXX'，其中'XXX'是连接Id的3位US-ASCII十进制表示形式。此格式为代理保留。
'B' NetWare PServer octets 2-40: Contains the Directory Path Name as recorded by the Novell File Server in the queue directory. If the string is less than 40 octets, the left-most character in the string shall appear in octet position 2. Otherwise, only the last 39 bytes shall be included. Any unused portion of this field shall be filled with spaces. octets 41-48: '000XXXXX' The US-ASCII representation of the Job Number as per the NetWare File Server Queue Management Services. This format is reserved for agents.
“B”NetWare PServer八位字节2-40：包含Novell文件服务器在队列目录中记录的目录路径名。如果字符串小于40个八位字节，字符串中最左边的字符应出现在八位字节位置2。否则，仅应包括最后39个字节。该字段的任何未使用部分应填充空格。八位字节41-48:“000XXXXX”根据NetWare文件服务器队列管理服务，作业编号的US-ASCII表示形式。此格式为代理保留。
'C' Server Message Block protocol (SMB) octets 2-40: Contains a decimal (US-ASCII coded) representation of the 16 bit SMB Tree Id field, which uniquely identifies the connection that submitted the job to the printer. The most significant digit of the numeric string shall be placed in octet position 2. All unused portions of this field shall be filled with spaces. The SMB Tree Id has a maximum value of 65,535. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the File Handle returned from the device to the client in response to a Create Print File command. This format is reserved for agents.
“C”服务器消息块协议（SMB）八位字节2-40：包含16位SMB树Id字段的十进制（US-ASCII编码）表示形式，该字段唯一标识将作业提交到打印机的连接。数字串的最高有效位应置于八位位组位置2。该区域的所有未使用部分应填满空间。SMB树Id的最大值为65535。八位字节41-48：响应Create Print File命令，从设备返回给客户端的文件句柄的US-ASCII 8位十进制前导零表示。此格式为代理保留。
'D' Transport Independent Printer/System Interface (TIP/SI) octets 2-40: Contains the Job Name from the Job Control-Start Job (JC-SJ) command. If the Job Name portion is less than 40 octets, the left-most character in the string shall appear in octet position 2. Any unused portion of this field shall be filled with spaces. Otherwise, only the last 39 bytes shall be included. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the jmJobIndex assigned by the agent. This format is reserved for agents, since the agent supplies octets 41-48, though the client supplies the job name. See format '1' reserved to clients to submit job name ids in which they supply octets 41-48.
“D”传输独立打印机/系统接口（TIP/SI）八位字节2-40：包含作业控制启动作业（JC-SJ）命令中的作业名称。如果作业名称部分少于40个八位字节，字符串中最左边的字符应出现在八位字节位置2。该字段的任何未使用部分应填充空格。否则，仅应包括最后39个字节。八位字节41-48：代理分配的jmJobIndex的US-ASCII 8位十进制前导零表示。此格式保留给代理，因为代理提供八位字节41-48，而客户端提供作业名称。请参阅保留给客户机的格式“1”，以提交他们提供八位字节41-48的作业名称ID。
'E' IPDS on the MVS or VSE platform
MVS或VSE平台上的“E”IPD
octets 2-40: Contains bytes 2-27 of the XOH Define Group Boundary Group ID triplet. Octet position 2 MUST carry the value x'01'. Bytes 28-40 MUST be filled with spaces. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the jmJobIndex assigned by the agent. This format is reserved for agents, since the agent supplies octets 41-48, though the client supplies the job name.
八位字节2-40：包含XOH定义组边界组ID三元组的字节2-27。八位字节位置2必须带有值x'01'。字节28-40必须用空格填充。八位字节41-48：代理分配的jmJobIndex的US-ASCII 8位十进制前导零表示。此格式保留给代理，因为代理提供八位字节41-48，而客户端提供作业名称。
'F' IPDS on the VM platform octets 2-40: Contains bytes 2-31 of the XOH Define Group Boundary Group ID triplet. Octet position 2 MUST carry the value x'02'. Bytes 32-40 MUST be filled with spaces. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the jmJobIndex assigned by the agent. This format is reserved for agents, since the agent supplies octets 41-48, though the client supplies the file name.
VM平台八位字节2-40上的“F”IPD：包含XOH定义组边界组ID三元组的字节2-31。八位字节位置2必须带有值x'02'。字节32-40必须用空格填充。八位字节41-48：代理分配的jmJobIndex的US-ASCII 8位十进制前导零表示。此格式保留给代理，因为代理提供八位字节41-48，而客户端提供文件名。
'G' IPDS on the OS/400 platform octets 2-40: Contains bytes 2-36 of the XOH Define Group Boundary Group ID triplet. Octet position 2 MUST carry the value x'03'. Bytes 37-40 MUST be filled with spaces. octets 41-48: The US-ASCII 8-decimal-digit leading zero representation of the jmJobIndex assigned by the agent. This format is reserved for agents, since the agent supplies octets 41-48, though the client supplies the job name.
OS/400平台八位字节2-40上的“G”IPD：包含XOH定义组边界组ID三元组的字节2-36。八位字节位置2必须带有值x'03'。字节37-40必须用空格填充。八位字节41-48：代理分配的jmJobIndex的US-ASCII 8位十进制前导零表示。此格式保留给代理，因为代理提供八位字节41-48，而客户端提供作业名称。
NOTE - the job submission id is only intended to be unique between a limited set of clients for a limited duration of time, namely, for the life time of the job in the context of the server or device that is processing the job. Some of the formats include something that is unique per client and a random number so that the same job submitted by the same client will have a different job submission id. For other formats, where part of the id is guaranteed to be unique for each client, such as the MAC address or URL, a sequential number SHOULD suffice for each client (and may be easier for each client to manage). Therefore, the length of the job submission id has been selected to reduce the probability of collision to an extremely low number, but is not intended to be an absolute guarantee of uniqueness. None-the-less, collisions are remotely possible, but without bad consequences, since this MIB is intended to be used only for monitoring jobs, not for controlling and managing them.
注意-作业提交id仅在有限的一段时间内，即在处理作业的服务器或设备上下文中的作业生命周期内，在有限的一组客户端之间是唯一的。某些格式包括每个客户端唯一的内容和一个随机数，以便同一客户端提交的同一作业将具有不同的作业提交id。对于其他格式，如果保证每个客户端的部分id是唯一的，例如MAC地址或URL，则每个客户端都应具有一个序列号（而且每个客户可能更容易管理）。因此，选择作业提交id的长度是为了将冲突的概率降低到极低的数字，但并不是为了绝对保证唯一性。尽管如此，由于此MIB仅用于监视作业，而不是用于c，因此冲突是远程可能的，但不会产生不良后果控制和管理它们。
This section describes the internationalization considerations included in this MIB.
本节介绍此MIB中包含的国际化注意事项。
There are a few objects and attributes generated by the server or device that SHALL be represented using the Universal Multiple-Octet Coded Character Set (UCS) [ISO-10646]. These objects and attributes are always supplied (if implemented) by the agent, not by the job submitting client: 1. jmGeneralJobSetName object 2. processingMessage(6) attribute 3. physicalDevice(32) (name value) attribute
服务器或设备生成的一些对象和属性应使用通用多八位编码字符集（UCS）[ISO-10646]表示。这些对象和属性始终由代理提供（如果已实现），而不是由作业提交客户端提供：1。jmGeneralJobSetName对象2。processingMessage（6）属性3。physicalDevice（32）（名称值）属性
The character encoding scheme for representing these objects and attributes SHALL be UTF-8 as REQUIRED by RFC 2277 [RFC2277]. The ' JmUTF8StringTC' textual convention is used to indicate UTF-8 text strings.
表示这些对象和属性的字符编码方案应为RFC 2277[RFC2277]要求的UTF-8。“JmUTF8StringTC”文本约定用于指示UTF-8文本字符串。
NOTE - For strings in 7-bit US-ASCII, there is no impact since the UTF-8 representation of 7-bit ASCII is identical to the US-ASCII [US-ASCII] encoding.
注意-对于7位US-ASCII中的字符串，没有影响，因为7位ASCII的UTF-8表示与US-ASCII[US-ASCII]编码相同。
The text contained in the processingMessage(6) attribute is generated by the server/device. The natural language for the processingMessage(6) attribute is identified by the processingMessageNaturalLangTag(7) attribute. The processingMessageNaturalLangTag(7) attribute uses the JmNaturalLanguageTagTC textual convention which SHALL conform to the language tag mechanism specified in RFC 1766 [RFC1766]. The JmNaturalLanguageTagTC value is the same as the IPP [ipp-model] ' naturalLanguage' attribute syntax. RFC 1766 specifies that a US-ASCII string consisting of the natural language followed by an optional country field. Both fields use the same two-character codes from ISO 639 [ISO-639] and ISO 3166 [ISO-3166], respectively, that are used in the Printer MIB for identifying language and country.
processingMessage（6）属性中包含的文本由服务器/设备生成。processingMessage（6）属性的自然语言由processingMessageNaturalLangTag（7）属性标识。processingMessageNaturalLangTag（7）属性使用JMNaturAllangGetAgTC文本约定，该约定应符合RFC 1766[RFC1766]中指定的语言标记机制。JmNaturalLanguageTagTC值与IPP[IPP model]“naturalLanguage”属性语法相同。RFC1766指定由自然语言后跟可选国家/地区字段组成的US-ASCII字符串。这两个字段分别使用ISO 639[ISO-639]和ISO 3166[ISO-3166]中相同的两个字符代码，它们在打印机MIB中用于标识语言和国家。
Examples of the values of the processingMessageNaturalLangTag(7) attribute include: 1. 'en' for English 2. 'en-us' for US English 3. 'fr' for French 4. 'de' for German
processingMessageNaturalLangTag（7）属性值的示例包括：1英语二级en us“为我们英语3”法语四级德文
All of the objects and attributes represented by the 'JmJobStringTC' textual-convention are either (1) supplied in the job submission protocol by the client that submits the job to the server or device or (2) are defaulted by the server or device if the job submitting client does not supply values. The agent SHALL represent these
“JmJobStringTC”文本约定表示的所有对象和属性（1）由将作业提交到服务器或设备的客户端在作业提交协议中提供，或者（2）如果作业提交客户端不提供值，则由服务器或设备默认。代理人应代表这些公司
objects and attributes in the MIB either (1) in the coded character set as they were submitted or (2) MAY convert the coded character set to another coded character set or encoding scheme. In any case, the resulting coded character set representation SHOULD be UTF-8 [UTF-8], but SHALL be one in which the code positions from 0 to 31 is not used, 32 to 127 is US-ASCII [US-ASCII], 127 is not unused, and the remaining code positions 128 to 255 represent single-byte or multi-byte graphic characters structured according to ISO 2022 [ISO-2022] or are unused.
MIB中的对象和属性（1）在提交时在编码字符集中，或（2）可以将编码字符集转换为另一个编码字符集或编码方案。在任何情况下，生成的编码字符集表示应为UTF-8[UTF-8]，但应为不使用0到31的代码位置，32到127为US-ASCII[US-ASCII]，127未使用，剩余的代码位置128到255表示根据ISO 2022结构化的单字节或多字节图形字符[ISO-2022]或未使用。
The coded character set SHALL be one of the ones registered with IANA [IANA] and SHALL be identified by the jobCodedCharSet attribute in the jmJobAttributeTable for the job. If the agent does not know what coded character set was used by the job submitting client, the agent SHALL either (1) return the 'unknown(2)' value for the jobCodedCharSet attribute or (2) not return the jobCodedCharSet attribute for the job.
编码字符集应为IANA[IANA]注册的字符集之一，并应通过作业jmJobAttributeTable中的jobCodedCharSet属性进行标识。如果代理不知道作业提交客户端使用的编码字符集，则代理应（1）返回jobCodedCharSet属性的“未知（2）”值，或（2）不返回作业的jobCodedCharSet属性。
Examples of coded character sets which meet this criteria for use as the value of the jobCodedCharSet job attribute are: US-ASCII [US-ASCII], ISO 8859-1 (Latin-1) [ISO-8859-1], any ISO 8859-n, HP Roman8, IBM Code Page 850, Windows Default 8-bit set, UTF-8 [UTF-8], US-ASCII plus JIS X0208-1990 Japanese [JIS X0208], US-ASCII plus GB2312-1980 PRC Chinese [GB2312]. See the IANA registry of coded character sets [IANA charsets].
满足此标准用作jobCodedCharSet作业属性值的编码字符集示例有：US-ASCII[US-ASCII]、ISO 8859-1（拉丁语-1）[ISO-8859-1]、任何ISO 8859-n、HP Roman8、IBM代码页850、Windows默认8位集、UTF-8[UTF-8]、US-ASCII加JIS X0208-1990日语[JIS X0208]，US-ASCII加GB2312-1980中华人民共和国中文[GB2312]。请参阅编码字符集的IANA注册表[IANA字符集]。
Examples of coded character sets which do not meet this criteria are: national 7-bit sets conforming to ISO 646 (except US-ASCII), EBCDIC, and ISO 10646 (Unicode) [ISO-10646]. In order to represent Unicode characters, the UTF-8 [UTF-8] encoding scheme SHALL be used which has been assigned the MIBenum value of '106' by IANA.
不符合此标准的编码字符集示例有：符合ISO 646（US-ASCII除外）、EBCDIC和ISO 10646（Unicode）[ISO-10646]的国家7位字符集。为了表示Unicode字符，应使用UTF-8[UTF-8]编码方案，该方案已由IANA分配MIBenum值“106”。
The jobCodedCharSet attribute uses the imported 'CodedCharSet' textual-convention from the Printer MIB [printmib].
jobCodedCharSet属性使用从打印机MIB[printmib]导入的“CodedCharSet”文本约定。
The natural language for attributes represented by the textual-convention JmJobStringTC is identified either (1) by the jobNaturalLanguageTag(9) attribute or is keywords in US-English (as in IPP). A monitoring application SHOULD attempt to localize keywords into the language of the user by means of some lookup mechanism. If the keyword value is not known to the monitoring application, the monitoring application SHOULD assume that the value is in the natural language specified by the job's jobNaturalLanguageTag(9) attribute and SHOULD present the value to its user as is. The jobNaturalLanguageTag(9) attribute value SHALL have the same syntax and semantics as the processingMessageNaturalLangTag(7) attribute, except that the jobNaturalLanguageTag(9) attribute identifies the natural language of
文本约定JmJobStringTC表示的属性的自然语言由JobNaturallangegetag（9）属性标识（1），或者是美国英语中的is关键字标识（如IPP）。监控应用程序应尝试通过某种查找机制将关键字本地化为用户的语言。如果监视应用程序不知道关键字值，则监视应用程序应假定该值使用作业的JobNaturAllangeAg（9）属性指定的自然语言，并应按原样将该值呈现给用户。JobNaturallangetag（9）属性值应具有与processingMessageNaturalLangTag（7）属性相同的语法和语义，但JobNaturallangetag（9）属性标识
attributes supplied by the job submitter instead of the natural language of the processingMessage(6) attribute. See Section 3.6.1.
作业提交者提供的属性，而不是processingMessage（6）属性的自然语言。见第3.6.1节。
This MIB also contains objects that are represented using the DateAndTime textual convention from SMIv2 [SMIv2-TC]. The job management application SHALL display such objects in the locale of the user running the monitoring application.
此MIB还包含使用SMIv2[SMIv2 TC]中的DateAndTime文本约定表示的对象。作业管理应用程序应在运行监控应用程序的用户所在地显示此类对象。
This MIB does not require any additional registration schemes for IANA, but does depend on registration schemes that other Internet standards track specifications have set up. The names of these IANA registration assignments under the /in-notes/iana/assignments/ path:
此MIB不需要IANA的任何其他注册方案，但依赖于其他Internet标准跟踪规范设置的注册方案。在/in notes/IANA/assignments/path下的这些IANA注册分配的名称：
1.printer-language-numbers - used as enums in the documentFormat(38) attribute
1.printer-language-number-用作documentFormat（38）属性中的枚举
2.media-types - uses as keywords in the documentFormat(38) attribute
2.media-types-用作documentFormat（38）属性中的关键字
3.character-sets - used as enums in the jobCodedCharSet(8) attribute
3.字符集-用作jobCodedCharSet（8）属性中的枚举
The Printer Working Group (PWG) will handle registration of additional enums after approving this standard, according to the procedures described in this section:
打印机工作组（PWG）将在批准本标准后，按照本节所述程序处理其他枚举的注册：
This specification uses textual conventions to define enumerated values (enums) and bit values. Enumerations (enums) and bit values are sets of symbolic values defined for use with one or more objects or attributes. All enumeration sets and bit value sets are assigned a symbolic data type name (textual convention). As a convention the symbolic name ends in "TC" for textual convention. These enumerations are defined at the beginning of the MIB module specification.
本规范使用文本约定定义枚举值（enum）和位值。枚举（enum）和位值是定义用于一个或多个对象或属性的符号值集。所有枚举集和位值集都指定了符号数据类型名称（文本约定）。作为惯例，符号名称以“TC”结尾，表示文本惯例。这些枚举在MIB模块规范的开头定义。
The PWG has defined several type of enumerations for use in the Job Monitoring MIB and the Printer MIB [print-mib]. These types differ in the method employed to control the addition of new enumerations. Throughout this document, references to "type n enum", where n can be 1, 2 or 3 can be found in the various tables. The definitions of these types of enumerations are:
PWG定义了几种类型的枚举，用于作业监视MIB和打印机MIB[print MIB]。这些类型在用于控制添加新枚举的方法上有所不同。在本文件中，可在各种表格中找到对“n类枚举”的引用，其中n可以是1、2或3。这些枚举类型的定义如下：
Type 1 enumeration: All the values are defined in the Job Monitoring MIB specification (RFC for the Job Monitoring MIB). Additional enumerated values require a new RFC.
类型1枚举：所有值都在作业监视MIB规范（作业监视MIB的RFC）中定义。其他枚举值需要新的RFC。
There are no type 1 enums in the current document.
当前文档中没有类型1枚举。
Type 2 enumeration: An initial set of values are defined in the Job Monitoring MIB specification. Additional enumerated values are registered with the PWG.
类型2枚举：在作业监视MIB规范中定义了一组初始值。其他枚举值在PWG中注册。
The following type 2 enums are contained in the current document:
1. JmUTF8StringTC
2. JmJobStringTC
3. JmNaturalLanguageTagTC
4. JmTimeStampTC
5. JmFinishingTC [same enum values as IPP "finishing" attribute]
6. JmPrintQualityTC [same enum values as IPP "print-quality"
attribute]
7. JmTonerEconomyTC
8. JmMediumTypeTC
9. JmJobSubmissionIDTypeTC
10.JmJobCollationTypeTC
11.JmJobStateTC [same enum values as IPP "job-state" attribute]
12.JmAttributeTypeTC
The following type 2 enums are contained in the current document:
1. JmUTF8StringTC
2. JmJobStringTC
3. JmNaturalLanguageTagTC
4. JmTimeStampTC
5. JmFinishingTC [same enum values as IPP "finishing" attribute]
6. JmPrintQualityTC [same enum values as IPP "print-quality"
attribute]
7. JmTonerEconomyTC
8. JmMediumTypeTC
9. JmJobSubmissionIDTypeTC
10.JmJobCollationTypeTC
11.JmJobStateTC [same enum values as IPP "job-state" attribute]
12.JmAttributeTypeTC
For those textual conventions that have the same enum values as the indicated IPP Job attribute are simultaneously registered by the PWG for use with IPP [ipp-model] and the Job Monitoring MIB.
对于那些与指示的IPP作业属性具有相同枚举值的文本约定，PWG将同时注册以用于IPP[IPP model]和作业监控MIB。
Type 3 enumeration: An initial set of values are defined in the Job Monitoring MIB specification. Additional enumerated values are registered through the PWG without PWG review.
类型3枚举：在作业监视MIB规范中定义了一组初始值。其他枚举值通过PWG注册，无需PWG审核。
There are no type 3 enums in the current document.
当前文档中没有类型3枚举。
This memo contains the following type 2 bit value textual-conventions: 1. JmJobServiceTypesTC 2. JmJobStateReasons1TC 3. JmJobStateReasons2TC 4. JmJobStateReasons3TC 5. JmJobStateReasons4TC
此备忘录包含以下类型2位值文本约定：1。jmjobservicetypestc2。jmjobstates1tc3。jmJobstates2tc4。jmjobstates3tc5。JmJobStateReasons4TC
These textual-conventions are defined as bits in an Integer so that they can be used with SNMPv1 SMI. The jobStateReasonsN (N=1..4) attributes are defined as bit values using the corresponding JmJobStateReasonsNTC textual-conventions.
这些文本约定被定义为整数中的位，因此可以与SNMPv1 SMI一起使用。jobStateReasonsN（N=1..4）属性使用相应的JmJobStateReasonsNTC文本约定定义为位值。
The registration of JmJobServiceTypesTC and JmJobStateReasonsNTC bit values follow the procedures for a type 2 enum as specified in Section 3.7.1.2.
JmJobServiceTypesTC和JmJobStateReasonsNTC位值的注册遵循第3.7.1.2节中规定的类型2枚举程序。
In addition to enums and bit values, this specification assigns a single ASCII digit or letter to various job submission ID formats. See the JmJobSubmissionIDTypeTC textual-convention and the object. The registration of JobSubmissionID format numbers follows the procedures for a type 2 enum as specified in Section 3.7.1.2.
除了枚举和位值外，本规范还为各种作业提交ID格式指定单个ASCII数字或字母。请参阅JmJobSubmissionIDTypeTC文本约定和对象。JobSubmissionID格式编号的注册遵循第3.7.1.2节中规定的2类枚举程序。
The documentFormat(38) attribute has MIME type/sub-type values for indicating document formats which IANA registers as "media type" names. The values of the documentFormat(38) attribute are the same as the corresponding Internet Printing Protocol (IPP) "document-format" Job attribute values [ipp-model].
documentFormat（38）属性具有MIME类型/子类型值，用于指示IANA注册为“媒体类型”名称的文档格式。documentFormat（38）属性的值与相应的Internet打印协议（IPP）“document format”作业属性值[IPP model]相同。
All objects are read-only, greatly simplifying the security considerations. If another MIB augments this MIB, that MIB might accept SNMP Write operations to objects in that MIB whose effect is to modify the values of read-only objects in this MIB. However, that MIB SHALL have to support the required access control in order to achieve security, not this MIB.
所有对象都是只读的，大大简化了安全考虑。如果另一个MIB扩充此MIB，则该MIB可能会接受对该MIB中对象的SNMP写操作，其效果是修改此MIB中只读对象的值。但是，该MIB必须支持所需的访问控制，以实现安全性，而不是该MIB。
The security policy of some sites MAY be that unprivileged users can only get the objects from jobs that they submitted, plus a few minimal objects from other jobs, such as the jmJobKOctetsPerCopyRequested and jmJobKOctetsProcessed objects, so that a user can tell how busy a printer is. Other sites MAY allow all unprivileged users to see all objects of all jobs. This MIB does not require, nor does it specify how, such restrictions would be implemented. A monitoring application SHOULD enforce the site security policy with respect to returning information to an unprivileged end user that is using the monitoring application to monitor jobs that do not belong to that user, i.e., the jmJobOwner object in the jmJobTable does not match the user's user name.
某些站点的安全策略可能是，未经授权的用户只能从他们提交的作业中获取对象，再加上其他作业中的一些最小对象，如jmJobKOctetsPerCopyRequested和jmJobKOctetsProcessed对象，这样用户就可以知道打印机有多忙。其他网站可能允许所有非特权用户查看所有作业的所有对象。该MIB不要求也不指定如何实现此类限制。监控应用程序应强制执行站点安全策略，将信息返回给使用监控应用程序监控不属于该用户的作业的无特权最终用户，即jmJobTable中的jmJobOwner对象与该用户的用户名不匹配。
An operator is a privileged user that would be able to see all objects of all jobs, independent of the policy for unprivileged users.
操作员是特权用户，能够查看所有作业的所有对象，与非特权用户的策略无关。
This MIB does not specify any notifications. For simplicity, management applications are expected to poll for status. The jmGeneralJobPersistence and jmGeneralAttributePersistence objects assist an application to determine the polling rate. The resulting network traffic is not expected to be significant.
此MIB不指定任何通知。为简单起见，管理应用程序需要轮询状态。jmGeneralJobPersistence和jmGeneralAttributePersistence对象帮助应用程序确定轮询速率。由此产生的网络流量预计不会很大。
4 MIB specification
4 MIB规范
The following pages constitute the actual Job Monitoring MIB.
以下页面构成实际的作业监视MIB。
Job-Monitoring-MIB DEFINITIONS ::= BEGIN
Job-Monitoring-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, enterprises,
Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed to implement
-- certain attributes, but are not needed to compile this MIB.
-- They are provided here for convenience:
-- hrDeviceIndex FROM HOST-RESOURCES-MIB
-- DateAndTime FROM SNMPv2-TC
-- PrtInterpreterLangFamilyTC,
-- CodedCharSet FROM Printer-MIB
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, enterprises,
Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-- The following textual-conventions are needed to implement
-- certain attributes, but are not needed to compile this MIB.
-- They are provided here for convenience:
-- hrDeviceIndex FROM HOST-RESOURCES-MIB
-- DateAndTime FROM SNMPv2-TC
-- PrtInterpreterLangFamilyTC,
-- CodedCharSet FROM Printer-MIB
-- Use the enterprises arc assigned to the PWG which is pwg(2699).
-- Group all PWG mibs under mibs(1).
-- Use the enterprises arc assigned to the PWG which is pwg(2699).
-- Group all PWG mibs under mibs(1).
jobmonMIB MODULE-IDENTITY LAST-UPDATED "9902190000Z" ORGANIZATION "Printer Working Group (PWG)" CONTACT-INFO "Tom Hastings Postal: Xerox Corp. Mail stop ESAE-231 701 S. Aviation Blvd. El Segundo, CA 90245
jobmonMIB模块标识最后更新的“9902190000Z”组织“打印机工作组（PWG）“联系方式”Tom Hastings邮政：施乐公司邮件站ESAE-231 701加利福尼亚州塞贡多南航空大道90245
Tel: (301)333-6413 Fax: (301)333-5514 E-mail: hastings@cp10.es.xerox.com
电话：（301）333-6413传真：（301）333-5514电子邮件：hastings@cp10.es.xerox.com
Send questions and comments to the Printer Working Group (PWG) using the Job Monitoring Project (JMP) Mailing List: jmp@pwg.org
使用作业监控项目（JMP）邮件列表向打印机工作组（PWG）发送问题和意见：jmp@pwg.org
For further information, including how to subscribe to the jmp mailing list, access the PWG web page under 'JMP':
有关更多信息，包括如何订阅jmp邮件列表，请访问“jmp”下的PWG网页：
http://www.pwg.org/
http://www.pwg.org/
Implementers of this specification are encouraged to join the jmp mailing list in order to participate in discussions on any clarifications needed and registration proposals being reviewed
鼓励本规范的实施者加入jmp邮件列表，以便参与讨论所需的任何澄清和正在审查的注册提案
in order to achieve consensus." DESCRIPTION "The MIB module for monitoring job in servers, printers, and other devices.
为了达成共识，“说明”MIB模块用于监控服务器、打印机和其他设备中的作业。
Version: 1.0"
版本：1.0“
-- revision history REVISION "9902190000Z" DESCRIPTION " This version published as RFC 2707"
--修订历史版本“99021900000Z”说明“本版本发布为RFC 2707”
::= { enterprises pwg(2699) mibs(1) jobmonMIB(1) }
::= { enterprises pwg(2699) mibs(1) jobmonMIB(1) }
-- Textual conventions for this MIB module
--此MIB模块的文本约定
JmUTF8StringTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information taken from the ISO/IEC IS 10646-1 character set,
encoded as an octet string using the UTF-8 character encoding
scheme.
JmUTF8StringTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information taken from the ISO/IEC IS 10646-1 character set,
encoded as an octet string using the UTF-8 character encoding
scheme.
See section 3.6.1, entitled: 'Text generated by the server or device'." SYNTAX OCTET STRING (SIZE (0..63))
请参阅第3.6.1节，标题为：“由服务器或设备生成的文本”。“语法八位字节字符串（大小（0..63））
JmJobStringTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information using any coded character set registered by IANA as
specified in section 3.7. While it is recommended that the
coded character set be UTF-8 [UTF-8], the actual coded
character set SHALL be indicated by the value of the
jobCodedCharSet(8) attribute for the job.
JmJobStringTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate internationalization, this TC represents
information using any coded character set registered by IANA as
specified in section 3.7. While it is recommended that the
coded character set be UTF-8 [UTF-8], the actual coded
character set SHALL be indicated by the value of the
jobCodedCharSet(8) attribute for the job.
See section 3.6.2, entitled: 'Text supplied by the job submitter'." SYNTAX OCTET STRING (SIZE (0..63))
参见第3.6.2节，标题为：“作业提交人提供的文本”。“语法八位字符串（大小（0..63））
JmNaturalLanguageTagTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An IETF RFC 1766-compliant 'language tag', with zero or more
sub-tags that identify a natural language. While RFC 1766
specifies that the US-ASCII values are case-insensitive, this
MIB specification requires that all characters SHALL be lower
case in order to simplify comparing by management applications.
JmNaturalLanguageTagTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An IETF RFC 1766-compliant 'language tag', with zero or more
sub-tags that identify a natural language. While RFC 1766
specifies that the US-ASCII values are case-insensitive, this
MIB specification requires that all characters SHALL be lower
case in order to simplify comparing by management applications.
See section 3.6.1, entitled: 'Text generated by the server or device' and section 3.6.2, entitled: 'Text supplied by the job submitter'." SYNTAX OCTET STRING (SIZE (0..63))
请参阅第3.6.1节，标题为：“服务器或设备生成的文本”和第3.6.2节，标题为：“作业提交者提供的文本”。“语法八位字符串（大小（0..63））
JmTimeStampTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The simple time at which an event took place. The units are
in seconds since the system was booted.
JmTimeStampTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The simple time at which an event took place. The units are
in seconds since the system was booted.
NOTE - JmTimeStampTC is defined in units of seconds, rather than 100ths of seconds, so as to be simpler for agents to implement (even if they have to implement the 100ths of a second to comply with implementing sysUpTime in MIB-II[mib-II].)
注意-JmTimeStampTC是以秒为单位定义的，而不是以百分之一百秒为单位定义的，因此代理实现起来更简单（即使它们必须实现百分之一秒以符合在MIB-II[MIB II]中实现系统正常运行时间的要求）
NOTE - JmTimeStampTC is defined as an Integer32 so that it can be used as a value of an attribute, i.e., as a value of the jmAttributeValueAsInteger object. The TimeStamp textual-convention defined in SNMPv2-TC [SMIv2-TC] is defined as an APPLICATION 3 IMPLICIT INTEGER tag, not an Integer32 which is defined in SNMPv2-SMI [SMIv2-TC] as UNIVERSAL 2 IMPLICIT INTEGER, so cannot be used in this MIB as one of the values of jmAttributeValueAsInteger." SYNTAX INTEGER (0..2147483647)
注意-JmTimeStampTC定义为整数32，因此它可以用作属性的值，即jmAttributeValueAsInteger对象的值。SNMPv2 TC[SMIv2 TC]中定义的时间戳文本约定被定义为应用程序3隐式整数标记，而不是SNMPv2 SMI[SMIv2 TC]中定义为通用2隐式整数的整数32，因此不能在此MIB中用作jmAttributeValueAsInteger的值之一。“语法整数（0..2147483647）
JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The source platform type that can submit jobs to servers or
devices in any of the 3 configurations.
JmJobSourcePlatformTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The source platform type that can submit jobs to servers or
devices in any of the 3 configurations.
This is a type 2 enumeration. See Section 3.7.1.2. See also
这是一个类型2枚举。见第3.7.1.2节。另见
IANA operating-system-names registry."
SYNTAX INTEGER {
other(1),
unknown(2),
sptUNIX(3), -- UNIX
sptOS2(4), -- OS/2
sptPCDOS(5), -- DOS
sptNT(6), -- NT
sptMVS(7), -- MVS
sptVM(8), -- VM
sptOS400(9), -- OS/400
sptVMS(10), -- VMS
sptWindows(11), -- Windows
sptNetWare(12) -- NetWare
}
IANA operating-system-names registry."
SYNTAX INTEGER {
other(1),
unknown(2),
sptUNIX(3), -- UNIX
sptOS2(4), -- OS/2
sptPCDOS(5), -- DOS
sptNT(6), -- NT
sptMVS(7), -- MVS
sptVM(8), -- VM
sptOS400(9), -- OS/400
sptVMS(10), -- VMS
sptWindows(11), -- Windows
sptNetWare(12) -- NetWare
}
JmFinishingTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of finishing operation.
JmFinishingTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of finishing operation.
These values are the same as the enum values of the IPP 'finishings' attribute. See Section 3.7.1.2.
这些值与IPP“finishings”属性的枚举值相同。见第3.7.1.2节。
other(1), Some other finishing operation besides one of the specified or registered values.
其他（1），除了指定值或注册值之外的其他一些精加工操作。
unknown(2), The finishing is unknown.
未知（2），加工过程未知。
none(3), Perform no finishing.
无（3），不进行精加工。
staple(4), Bind the document(s) with one or more staples. The exact number and placement of the staples is site-defined.
装订（4），用一个或多个装订机装订文档。订书钉的确切数量和位置由现场确定。
punch(5), Holes are required in the finished document. The exact number and placement of the holes is site-defined. The punch specification MAY be satisfied (in a site- and implementation-specific manner) either by drilling/punching, or by substituting pre-drilled media.
冲头（5），成品文件中需要打孔。孔的确切数量和位置由现场确定。可通过钻孔/打孔或替换预钻孔介质来满足打孔规范（以特定于现场和实施的方式）。
cover(6),
封面（6），
Select a non-printed (or pre-printed) cover for the document. This does not supplant the specification of a printed cover (on cover stock medium) by the document itself.
为文档选择未打印（或预打印）的封面。这并不能取代文档本身对打印封面（封面库存介质）的说明。
bind(7) Binding is to be applied to the document; the type and placement of the binding is product-specific.
装订（7）装订适用于文件；装订的类型和位置是特定于产品的。
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
other(1),
unknown(2),
none(3),
staple(4),
punch(5),
cover(6),
bind(7)
}
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
other(1),
unknown(2),
none(3),
staple(4),
punch(5),
cover(6),
bind(7)
}
JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Print quality settings.
JmPrintQualityTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Print quality settings.
These values are the same as the enum values of the IPP 'print-quality' attribute. See Section 3.7.1.2.
这些值与IPP“打印质量”属性的枚举值相同。见第3.7.1.2节。
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
other(1), -- Not one of the specified or registered
-- values.
unknown(2), -- The actual value is unknown.
draft(3), -- Lowest quality available on the printer.
normal(4), -- Normal or intermediate quality on the
-- printer.
high(5) -- Highest quality available on the printer.
}
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
other(1), -- Not one of the specified or registered
-- values.
unknown(2), -- The actual value is unknown.
draft(3), -- Lowest quality available on the printer.
normal(4), -- Normal or intermediate quality on the
-- printer.
high(5) -- Highest quality available on the printer.
}
JmPrinterResolutionTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Printer resolutions.
JmPrinterResolutionTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Printer resolutions.
Nine octets consisting of two 4-octet SIGNED-INTEGERs followed
九个八位组，由两个四个八位组的带符号整数组成
by a SIGNED-BYTE. The values are the same as those specified in the Printer MIB [printmib]. The first SIGNED-INTEGER contains the value of prtMarkerAddressabilityXFeedDir. The second SIGNED-INTEGER contains the value of prtMarkerAddressabilityFeedDir. The SIGNED-BYTE contains the value of prtMarkerAddressabilityUnit.
通过一个有符号字节。这些值与打印机MIB[printmib]中指定的值相同。第一个有符号整数包含prtMarkerAddressabilityXFeedDir的值。第二个有符号整数包含prtMarkerAddressabilityFeedDir的值。带符号字节包含prtMarkerAddressabilityUnit的值。
Note: the latter value is either 3 (tenThousandsOfInches) or 4 (micrometers) and the addressability is in 10,000 units of measure. Thus the SIGNED-INTEGERs represent integral values in either dots-per-inch or dots-per-centimeter.
注：后一个值为3（十分之一英寸）或4（微米），可寻址性为10000测量单位。因此，有符号整数表示每英寸点数或每厘米点数的整数值。
The syntax is the same as the IPP 'printer-resolution' attribute. See Section 3.7.1.2." SYNTAX OCTET STRING (SIZE(9))
语法与IPP“打印机分辨率”属性相同。见第3.7.1.2节“语法八位组字符串（大小（9））
JmTonerEconomyTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Toner economy settings.
JmTonerEconomyTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Toner economy settings.
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2), -- unknown.
off(3), -- Off. Normal. Use full toner.
on(4) -- On. Use less toner than normal.
}
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2), -- unknown.
off(3), -- Off. Normal. Use full toner.
on(4) -- On. Use less toner than normal.
}
JmBooleanTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Boolean true or false value.
JmBooleanTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Boolean true or false value.
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2), -- unknown.
false(3), -- FALSE.
true(4) -- TRUE.
}
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2), -- unknown.
false(3), -- FALSE.
true(4) -- TRUE.
}
JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
JmMediumTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the type of medium.
“标识介质的类型。
other(1), The type is neither one of the values listed in this specification nor a registered value.
其他（1），类型既不是本规范中列出的值之一，也不是注册值。
unknown(2), The type is not known.
未知（2），类型未知。
stationery(3), Separately cut sheets of an opaque material.
文具（3），由不透明材料单独切割而成。
transparency(4), Separately cut sheets of a transparent material.
透明（4），由透明材料单独切割而成。
envelope(5), Envelopes that can be used for conventional mailing purposes.
信封（5），可用于常规邮寄目的的信封。
envelopePlain(6), Envelopes that are not preprinted and have no windows.
信封平面图（6），未预印且无窗口的信封。
envelopeWindow(7), Envelopes that have windows for addressing purposes.
信封窗口（7），具有用于寻址的窗口的信封。
continuousLong(8), Continuously connected sheets of an opaque material connected along the long edge.
continuousLong（8），沿着长边连接的不透明材料的连续连接板材。
continuousShort(9), Continuously connected sheets of an opaque material connected along the short edge.
continuousShort（9），沿着短边连接的不透明材料的连续连接板材。
tabStock(10), Media with tabs.
tabStock（10），带标签的介质。
multiPartForm(11), Form medium composed of multiple layers not pre-attached to one another; each sheet MAY be drawn separately from an input source.
多部件形式（11），由多个层组成的形式介质，这些层之间没有预先连接；每张图纸可以从输入源单独绘制。
labels(12), Label-stock.
标签（12），标签库存。
multiLayer(13) Form medium composed of multiple layers which are pre-attached to one another, e.g. for use with impact printers.
多层（13）形成由多层组成的介质，多层相互预先连接，例如用于冲击式打印机。
This is a type 2 enumeration. See Section 3.7.1.2. These enum
values correspond to the keyword name strings of the
prtInputMediaType object in the Printer MIB [print-mib]. There
is no printer description attribute in IPP/1.0 that represents
these values."
SYNTAX INTEGER {
other(1),
unknown(2),
stationery(3),
transparency(4),
envelope(5),
envelopePlain(6),
envelopeWindow(7),
continuousLong(8),
continuousShort(9),
tabStock(10),
multiPartForm(11),
labels(12),
multiLayer(13)
}
This is a type 2 enumeration. See Section 3.7.1.2. These enum
values correspond to the keyword name strings of the
prtInputMediaType object in the Printer MIB [print-mib]. There
is no printer description attribute in IPP/1.0 that represents
these values."
SYNTAX INTEGER {
other(1),
unknown(2),
stationery(3),
transparency(4),
envelope(5),
envelopePlain(6),
envelopeWindow(7),
continuousLong(8),
continuousShort(9),
tabStock(10),
multiPartForm(11),
labels(12),
multiLayer(13)
}
JmJobCollationTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This value is the type of job collation. Implementations that
don't support multiple documents or don't support multiple
copies SHALL NOT support the uncollatedDocuments(5) value.
JmJobCollationTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This value is the type of job collation. Implementations that
don't support multiple documents or don't support multiple
copies SHALL NOT support the uncollatedDocuments(5) value.
This is a type 2 enumeration. See Section 3.7.1.2. See also
Section 3.4, entitled 'Monitoring Job Progress'."
SYNTAX INTEGER {
other(1),
unknown(2),
uncollatedSheets(3), -- sheets within each document copy
-- are not collated: 1 1 ..., 2 2 ...,
-- No corresponding value of IPP
-- "multiple-document-handling"
collatedDocuments(4), -- internal collated sheets,
-- documents: A, B, A, B, ...
-- Corresponds to IPP "multiple-
-- document-handling"='separate-
-- documents-collated-copies'
uncollatedDocuments(5) -- internal collated sheets,
-- documents: A, A, ..., B, B, ...
-- Corresponds to IPP "multiple-
-- document-handling"='separate-
-- documents-uncollated-copies'
This is a type 2 enumeration. See Section 3.7.1.2. See also
Section 3.4, entitled 'Monitoring Job Progress'."
SYNTAX INTEGER {
other(1),
unknown(2),
uncollatedSheets(3), -- sheets within each document copy
-- are not collated: 1 1 ..., 2 2 ...,
-- No corresponding value of IPP
-- "multiple-document-handling"
collatedDocuments(4), -- internal collated sheets,
-- documents: A, B, A, B, ...
-- Corresponds to IPP "multiple-
-- document-handling"='separate-
-- documents-collated-copies'
uncollatedDocuments(5) -- internal collated sheets,
-- documents: A, A, ..., B, B, ...
-- Corresponds to IPP "multiple-
-- document-handling"='separate-
-- documents-uncollated-copies'
}
}
JmJobSubmissionIDTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the format type of a job submission ID.
JmJobSubmissionIDTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies the format type of a job submission ID.
Each job submission ID is a fixed-length, 48-octet printable US-ASCII [US-ASCII] coded character string containing no control characters, consisting of the fields defined in section 3.5.1.
每个作业提交ID是一个固定长度、48个八位字节的可打印US-ASCII[US-ASCII]编码字符串，不包含任何控制字符，由第3.5.1节中定义的字段组成。
This is like a type 2 enumeration. See section 3.7.3." SYNTAX OCTET STRING(SIZE(1)) -- ASCII '0'-'9', 'A'-'Z', 'a'-'z'
这类似于类型2枚举。见第3.7.3节“语法八位字符串（大小（1））--ASCII'0'-'9'，'A'-'Z'，'A'-'Z'
JmJobStateTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The current state of the job (pending, processing, completed,
etc.). The following figure shows the normal job state
transitions:
JmJobStateTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The current state of the job (pending, processing, completed,
etc.). The following figure shows the normal job state
transitions:
+----> canceled(7)
/
+---> pending(3) -------> processing(5) ------+------> completed(9)
| ^ ^ \
--->+ | | +----> aborted(8)
| v v /
+---> pendingHeld(4) processingStopped(6) ---+
+----> canceled(7)
/
+---> pending(3) -------> processing(5) ------+------> completed(9)
| ^ ^ \
--->+ | | +----> aborted(8)
| v v /
+---> pendingHeld(4) processingStopped(6) ---+
Figure 4 - Normal Job State Transitions
图4-正常作业状态转换
Normally a job progresses from left to right. Other state transitions are unlikely, but are not forbidden. Not shown are the transitions to the canceled state from the pending, pendingHeld, and processingStopped states.
通常，作业从左到右进行。其他状态转换不太可能，但也不被禁止。未显示从挂起、pendingHeld和processingStopped状态到取消状态的转换。
Jobs in the pending, processing, and processingStopped states are called 'active', while jobs in the pendingHeld, canceled, aborted, and completed states are called 'inactive'. Jobs reach one of the three terminal states: completed, canceled, or aborted, after the jobs have completed all activity, and all MIB objects and attributes have reached their final values for the job.
处于挂起、处理和处理停止状态的作业称为“活动”，而处于挂起、取消、中止和完成状态的作业称为“非活动”。作业完成所有活动，并且所有MIB对象和属性达到作业的最终值后，作业达到三种终端状态之一：已完成、已取消或已中止。
These values are the same as the enum values of the IPP 'job-state' job attribute. See Section 3.7.1.2.
这些值与IPP“作业状态”作业属性的枚举值相同。见第3.7.1.2节。
unknown(2), The job state is not known, or its state is indeterminate.
未知（2）、作业状态未知或其状态不确定。
pending(3), The job is a candidate to start processing, but is not yet processing.
挂起（3），作业是要开始处理的候选项，但尚未处理。
pendingHeld(4), The job is not a candidate for processing for any number of reasons but will return to the pending state as soon as the reasons are no longer present. The job's jmJobStateReasons1 object and/or jobStateReasonsN (N=2..4) attributes SHALL indicate why the job is no longer a candidate for processing. The reasons are represented as bits in the jmJobStateReasons1 object and/or jobStateReasonsN (N=2..4) attributes. See the JmJobStateReasonsNTC (N=1..4) textual convention for the specification of each reason.
pendingHeld（4），由于各种原因，该职位不是处理的候选人，但一旦原因不再存在，该职位将返回待定状态。作业的jmJobStateReasons1对象和/或jobStateReasonsN（N=2..4）属性应指明作业不再是处理候选对象的原因。原因以jmJobStateReasons1对象和/或jobStateReasonsN（N=2..4）属性中的位表示。有关每个原因的规范，请参见JmJobStateReasonsNTC（N=1..4）文本约定。
processing(5), One or more of:
处理（5），一个或多个：
1. the job is using, or is attempting to use, one or more purely software processes that are analyzing, creating, or interpreting a PDL, etc.,
1. 作业正在使用或试图使用一个或多个纯软件过程，这些过程正在分析、创建或解释PDL等。，
2. the job is using, or is attempting to use, one or more hardware devices that are interpreting a PDL, making mark on a medium, and/or performing finishing, such as stapling, etc., OR
2. 作业正在使用或试图使用一个或多个硬件设备，这些硬件设备正在解释PDL、在介质上做标记和/或执行修整，如装订等，或
3. (configuration 2) the server has made the job ready for printing, but the output device is not yet printing it, either because the job hasn't reached the output device or because the job is queued in the output device or some other spooler, awaiting the output device to print it.
3. （配置2）服务器已准备好打印作业，但输出设备尚未打印作业，原因可能是作业尚未到达输出设备，或者作业在输出设备或其他后台处理程序中排队，等待输出设备打印作业。
When the job is in the processing state, the entire job state includes the detailed status represented in the device MIB indicated by the hrDeviceIndex value of the job's physicalDevice attribute, if the agent implements such a device MIB.
当作业处于处理状态时，如果代理实现这样的设备MIB，则整个作业状态包括由作业的physicalDevice属性的hrDeviceIndex值指示的设备MIB中表示的详细状态。
Implementations MAY, though they NEED NOT, include
实现可能（尽管不需要）包括
additional values in the job's jmJobStateReasons1 object to indicate the progress of the job, such as adding the jobPrinting value to indicate when the device is actually making marks on a medium and/or the processingToStopPoint value to indicate that the server or device is in the process of canceling or aborting the job.
作业的jmJobStateReasons1对象中的其他值指示作业的进度，例如添加jobPrinting值指示设备何时在介质上进行标记和/或ProcessingToSupport值指示服务器或设备正在取消或中止作业。
processingStopped(6), The job has stopped while processing for any number of reasons and will return to the processing state as soon as the reasons are no longer present.
ProcessingsStopped（6），作业在处理过程中因各种原因而停止，并将在原因不再存在时立即返回到处理状态。
The job's jmJobStateReasons1 object and/or the job's jobStateReasonsN (N=2..4) attributes MAY indicate why the job has stopped processing. For example, if the output device is stopped, the deviceStopped value MAY be included in the job's jmJobStateReasons1 object.
作业的jmJobStateReasons1对象和/或作业的jobStateReasonsN（N=2..4）属性可能指示作业停止处理的原因。例如，如果输出设备停止，则deviceStopped值可能包含在作业的jmJobStateReasons1对象中。
NOTE - When an output device is stopped, the device usually indicates its condition in human readable form at the device. The management application can obtain more complete device status remotely by querying the appropriate device MIB using the job's deviceIndex attribute(s), if the agent implements such a device MIB
注-当输出设备停止时，设备通常在设备上以人类可读的形式指示其状态。管理应用程序可以通过使用作业的deviceIndex属性查询适当的设备MIB（如果代理实现这样的设备MIB），远程获取更完整的设备状态
canceled(7), A client has canceled the job and the server or device has completed canceling the job AND all MIB objects and attributes have reached their final values for the job. While the server or device is canceling the job, the job's jmJobStateReasons1 object SHOULD contain the processingToStopPoint value and one of the canceledByUser, canceledByOperator, or canceledAtDevice values. The canceledByUser, canceledByOperator, or canceledAtDevice values remain while the job is in the canceled state.
取消（7），客户端已取消作业，服务器或设备已完成取消作业，并且所有MIB对象和属性已达到作业的最终值。当服务器或设备取消作业时，作业的jmJobStateReasons1对象应包含ProcessingToSupport值和canceledByUser、canceledByOperator或CanceledDevice值之一。作业处于取消状态时，canceledByUser、canceledByOperator或CanceledDevice值将保留。
aborted(8), The job has been aborted by the system, usually while the job was in the processing or processingStopped state and the server or device has completed aborting the job AND all MIB objects and attributes have reached their final values for the job. While the server or device is aborting the job, the job's jmJobStateReasons1 object MAY contain the processingToStopPoint and abortedBySystem values. If implemented, the abortedBySystem value SHALL remain while the job is in the aborted state.
中止（8），作业已被系统中止，通常是在作业处于处理或processingStopped状态且服务器或设备已完成中止作业且所有MIB对象和属性已达到作业的最终值时。当服务器或设备中止作业时，作业的jmJobStateReasons1对象可能包含ProcessingToSupport和abortedBySystem值。如果实施，作业处于中止状态时，abortedBySystem值应保持不变。
completed(9) The job has completed successfully or with warnings or errors after processing and all of the media have been successfully stacked in the appropriate output bin(s) AND all MIB objects and attributes have reached their final values for the job. The job's jmJobStateReasons1 object SHOULD contain one of: completedSuccessfully, completedWithWarnings, or completedWithErrors values.
已完成（9）作业已成功完成，或在处理后出现警告或错误，并且所有介质已成功堆叠到相应的输出箱中，并且所有MIB对象和属性已达到作业的最终值。作业的jmJobStateReasons1对象应包含以下值之一：completedSuccessfully、completedWithWarnings或completedWithErrors值。
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2),
pending(3),
pendingHeld(4),
processing(5),
processingStopped(6),
canceled(7),
aborted(8),
completed(9)
}
This is a type 2 enumeration. See Section 3.7.1.2."
SYNTAX INTEGER {
unknown(2),
pending(3),
pendingHeld(4),
processing(5),
processingStopped(6),
canceled(7),
aborted(8),
completed(9)
}
JmAttributeTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of the attribute which identifies the attribute.
JmAttributeTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of the attribute which identifies the attribute.
NOTE - The enum assignments are grouped logically with values assigned in groups of 20, so that additional values may be registered in the future and assigned a value that is part of their logical grouping.
注意-枚举分配以20为一组进行逻辑分组，以便将来可以注册其他值，并分配一个作为其逻辑分组一部分的值。
Values in the range 2**30 to 2**31-1 are reserved for private or experimental usage. This range corresponds to the same range reserved in IPP. Implementers are warned that use of such values may conflict with other implementations. Implementers are encouraged to request registration of enum values following the procedures in Section 3.7.1.
2**30至2**31-1范围内的值保留供私人或实验使用。此范围对应于IPP中保留的相同范围。实现者被警告使用这些值可能与其他实现冲突。鼓励实施者按照第3.7.1节中的程序要求注册枚举值。
See Section 3.2 entitled 'The Attribute Mechanism' for a description of this textual-convention and its use in the jmAttributeTable. See Section 3.3.8 for the specification of each attribute. The comment(s) after each enum assignment specifies the data type(s) of the attribute.
有关此文本约定及其在jmAttributeTable中的使用的说明，请参见第3.2节“属性机制”。有关每个属性的规范，请参见第3.3.8节。每个枚举分配后的注释指定属性的数据类型。
This is a type 2 enumeration. See Section 3.7.1.2."
这是一个类型2枚举。参见第3.7.1.2节。”
SYNTAX INTEGER {
other(1), -- Integer32 (-2..2147483647)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
SYNTAX INTEGER {
other(1), -- Integer32 (-2..2147483647)
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- Job State attributes:
jobStateReasons2(3), -- JmJobStateReasons2TC
jobStateReasons3(4), -- JmJobStateReasons3TC
jobStateReasons4(5), -- JmJobStateReasons4TC
processingMessage(6), -- JmUTF8StringTC (SIZE(0..63))
processingMessageNaturalLangTag(7),
-- OCTET STRING(SIZE(0..63))
jobCodedCharSet(8), -- CodedCharSet
jobNaturalLanguageTag(9), -- OCTET STRING(SIZE(0..63))
-- Job State attributes:
jobStateReasons2(3), -- JmJobStateReasons2TC
jobStateReasons3(4), -- JmJobStateReasons3TC
jobStateReasons4(5), -- JmJobStateReasons4TC
processingMessage(6), -- JmUTF8StringTC (SIZE(0..63))
processingMessageNaturalLangTag(7),
-- OCTET STRING(SIZE(0..63))
jobCodedCharSet(8), -- CodedCharSet
jobNaturalLanguageTag(9), -- OCTET STRING(SIZE(0..63))
-- Job Identification attributes:
jobURI(20), -- OCTET STRING(SIZE(0..63))
jobAccountName(21), -- OCTET STRING(SIZE(0..63))
serverAssignedJobName(22), -- JmJobStringTC (SIZE(0..63))
jobName(23), -- JmJobStringTC (SIZE(0..63))
jobServiceTypes(24), -- JmJobServiceTypesTC
jobSourceChannelIndex(25), -- Integer32 (0..2147483647)
jobSourcePlatformType(26), -- JmJobSourcePlatformTypeTC
submittingServerName(27), -- JmJobStringTC (SIZE(0..63))
submittingApplicationName(28), -- JmJobStringTC (SIZE(0..63))
jobOriginatingHost(29), -- JmJobStringTC (SIZE(0..63))
deviceNameRequested(30), -- JmJobStringTC (SIZE(0..63))
queueNameRequested(31), -- JmJobStringTC (SIZE(0..63))
physicalDevice(32), -- hrDeviceIndex
-- AND/OR
-- JmUTF8StringTC (SIZE(0..63))
numberOfDocuments(33), -- Integer32 (-2..2147483647)
fileName(34), -- JmJobStringTC (SIZE(0..63))
documentName(35), -- JmJobStringTC (SIZE(0..63))
jobComment(36), -- JmJobStringTC (SIZE(0..63))
documentFormatIndex(37), -- Integer32 (0..2147483647)
documentFormat(38), -- PrtInterpreterLangFamilyTC
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- Job Identification attributes:
jobURI(20), -- OCTET STRING(SIZE(0..63))
jobAccountName(21), -- OCTET STRING(SIZE(0..63))
serverAssignedJobName(22), -- JmJobStringTC (SIZE(0..63))
jobName(23), -- JmJobStringTC (SIZE(0..63))
jobServiceTypes(24), -- JmJobServiceTypesTC
jobSourceChannelIndex(25), -- Integer32 (0..2147483647)
jobSourcePlatformType(26), -- JmJobSourcePlatformTypeTC
submittingServerName(27), -- JmJobStringTC (SIZE(0..63))
submittingApplicationName(28), -- JmJobStringTC (SIZE(0..63))
jobOriginatingHost(29), -- JmJobStringTC (SIZE(0..63))
deviceNameRequested(30), -- JmJobStringTC (SIZE(0..63))
queueNameRequested(31), -- JmJobStringTC (SIZE(0..63))
physicalDevice(32), -- hrDeviceIndex
-- AND/OR
-- JmUTF8StringTC (SIZE(0..63))
numberOfDocuments(33), -- Integer32 (-2..2147483647)
fileName(34), -- JmJobStringTC (SIZE(0..63))
documentName(35), -- JmJobStringTC (SIZE(0..63))
jobComment(36), -- JmJobStringTC (SIZE(0..63))
documentFormatIndex(37), -- Integer32 (0..2147483647)
documentFormat(38), -- PrtInterpreterLangFamilyTC
-- AND/OR
-- OCTET STRING(SIZE(0..63))
-- Job Parameter attributes:
jobPriority(50), -- Integer32 (-2..100)
jobProcessAfterDateAndTime(51), -- DateAndTime (SNMPv2-TC)
jobHold(52), -- JmBooleanTC
jobHoldUntil(53), -- JmJobStringTC (SIZE(0..63))
outputBin(54), -- Integer32 (0..2147483647)
-- AND/OR
-- Job Parameter attributes:
jobPriority(50), -- Integer32 (-2..100)
jobProcessAfterDateAndTime(51), -- DateAndTime (SNMPv2-TC)
jobHold(52), -- JmBooleanTC
jobHoldUntil(53), -- JmJobStringTC (SIZE(0..63))
outputBin(54), -- Integer32 (0..2147483647)
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
sides(55), -- Integer32 (-2..2)
finishing(56), -- JmFinishingTC
-- JmJobStringTC (SIZE(0..63))
sides(55), -- Integer32 (-2..2)
finishing(56), -- JmFinishingTC
-- Image Quality attributes:
printQualityRequested(70), -- JmPrintQualityTC
printQualityUsed(71), -- JmPrintQualityTC
printerResolutionRequested(72), -- JmPrinterResolutionTC
printerResolutionUsed(73), -- JmPrinterResolutionTC
tonerEcomonyRequested(74), -- JmTonerEconomyTC
tonerEcomonyUsed(75), -- JmTonerEconomyTC
tonerDensityRequested(76), -- Integer32 (-2..100)
tonerDensityUsed(77), -- Integer32 (-2..100)
-- Image Quality attributes:
printQualityRequested(70), -- JmPrintQualityTC
printQualityUsed(71), -- JmPrintQualityTC
printerResolutionRequested(72), -- JmPrinterResolutionTC
printerResolutionUsed(73), -- JmPrinterResolutionTC
tonerEcomonyRequested(74), -- JmTonerEconomyTC
tonerEcomonyUsed(75), -- JmTonerEconomyTC
tonerDensityRequested(76), -- Integer32 (-2..100)
tonerDensityUsed(77), -- Integer32 (-2..100)
-- Job Progress attributes:
jobCopiesRequested(90), -- Integer32 (-2..2147483647)
jobCopiesCompleted(91), -- Integer32 (-2..2147483647)
documentCopiesRequested(92), -- Integer32 (-2..2147483647)
documentCopiesCompleted(93), -- Integer32 (-2..2147483647)
jobKOctetsTransferred(94), -- Integer32 (-2..2147483647)
sheetCompletedCopyNumber(95), -- Integer32 (-2..2147483647)
sheetCompletedDocumentNumber(96),
-- Integer32 (-2..2147483647)
jobCollationType(97), -- JmJobCollationTypeTC
-- Job Progress attributes:
jobCopiesRequested(90), -- Integer32 (-2..2147483647)
jobCopiesCompleted(91), -- Integer32 (-2..2147483647)
documentCopiesRequested(92), -- Integer32 (-2..2147483647)
documentCopiesCompleted(93), -- Integer32 (-2..2147483647)
jobKOctetsTransferred(94), -- Integer32 (-2..2147483647)
sheetCompletedCopyNumber(95), -- Integer32 (-2..2147483647)
sheetCompletedDocumentNumber(96),
-- Integer32 (-2..2147483647)
jobCollationType(97), -- JmJobCollationTypeTC
-- Impression attributes:
impressionsSpooled(110), -- Integer32 (-2..2147483647)
impressionsSentToDevice(111), -- Integer32 (-2..2147483647)
impressionsInterpreted(112), -- Integer32 (-2..2147483647)
impressionsCompletedCurrentCopy(113),
-- Integer32 (-2..2147483647)
fullColorImpressionsCompleted(114),
-- Integer32 (-2..2147483647)
highlightColorImpressionsCompleted(115),
-- Integer32 (-2..2147483647)
-- Impression attributes:
impressionsSpooled(110), -- Integer32 (-2..2147483647)
impressionsSentToDevice(111), -- Integer32 (-2..2147483647)
impressionsInterpreted(112), -- Integer32 (-2..2147483647)
impressionsCompletedCurrentCopy(113),
-- Integer32 (-2..2147483647)
fullColorImpressionsCompleted(114),
-- Integer32 (-2..2147483647)
highlightColorImpressionsCompleted(115),
-- Integer32 (-2..2147483647)
-- Page attributes:
pagesRequested(130), -- Integer32 (-2..2147483647)
pagesCompleted(131), -- Integer32 (-2..2147483647)
pagesCompletedCurrentCopy(132), -- Integer32 (-2..2147483647)
-- Page attributes:
pagesRequested(130), -- Integer32 (-2..2147483647)
pagesCompleted(131), -- Integer32 (-2..2147483647)
pagesCompletedCurrentCopy(132), -- Integer32 (-2..2147483647)
-- Sheet attributes:
sheetsRequested(150), -- Integer32 (-2..2147483647)
sheetsCompleted(151), -- Integer32 (-2..2147483647)
sheetsCompletedCurrentCopy(152),-- Integer32 (-2..2147483647)
-- Sheet attributes:
sheetsRequested(150), -- Integer32 (-2..2147483647)
sheetsCompleted(151), -- Integer32 (-2..2147483647)
sheetsCompletedCurrentCopy(152),-- Integer32 (-2..2147483647)
-- Resource attributes:
--资源属性：
mediumRequested(170), -- JmMediumTypeTC
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
mediumConsumed(171), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
colorantRequested(172), -- Integer32 (-2..2147483647)
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
colorantConsumed(173), -- Integer32 (-2..2147483647)
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
mediumTypeConsumed(174), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
mediumSizeConsumed(175), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
mediumRequested(170), -- JmMediumTypeTC
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
mediumConsumed(171), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
colorantRequested(172), -- Integer32 (-2..2147483647)
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
colorantConsumed(173), -- Integer32 (-2..2147483647)
-- AND/OR
-- JmJobStringTC (SIZE(0..63))
mediumTypeConsumed(174), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
mediumSizeConsumed(175), -- Integer32 (-2..2147483647)
-- AND
-- JmJobStringTC (SIZE(0..63))
-- Time attributes:
jobSubmissionToServerTime(190), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobSubmissionTime(191), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobStartedBeingHeldTime(192), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobStartedProcessingTime(193), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobCompletionTime(194), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobProcessingCPUTime(195) -- Integer32 (-2..2147483647)
}
-- Time attributes:
jobSubmissionToServerTime(190), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobSubmissionTime(191), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobStartedBeingHeldTime(192), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobStartedProcessingTime(193), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobCompletionTime(194), -- JmTimeStampTC
-- AND/OR
-- DateAndTime
jobProcessingCPUTime(195) -- Integer32 (-2..2147483647)
}
JmJobServiceTypesTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Specifies the type(s) of service to which the job has been
submitted (print, fax, scan, etc.). The service type is
represented as an enum that is bit encoded with each job
service type so that more general and arbitrary services can be
created, such as services with more than one destination type,
JmJobServiceTypesTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Specifies the type(s) of service to which the job has been
submitted (print, fax, scan, etc.). The service type is
represented as an enum that is bit encoded with each job
service type so that more general and arbitrary services can be
created, such as services with more than one destination type,
or ones with only a source or only a destination. For example, a job service might scan, faxOut, and print a single job. In this case, three bits would be set in the jobServiceTypes attribute, corresponding to the hexadecimal values: 0x8 + 0x20 + 0x4, respectively, yielding: 0x2C.
或者只有一个来源或者只有一个目的地。例如，作业服务可以扫描、传真和打印单个作业。在这种情况下，将在jobServiceTypes属性中设置三个位，分别对应于十六进制值：0x8+0x20+0x4，产生：0x2C。
Whether this attribute is set from a job attribute supplied by the job submission client or is set by the recipient job submission server or device depends on the job submission protocol. With either implementation, the agent SHALL return a non-zero value for this attribute indicating the type of the job.
此属性是从作业提交客户端提供的作业属性设置的，还是由收件人作业提交服务器或设备设置的，取决于作业提交协议。对于任何一种实现，代理都将为此属性返回一个非零值，该值指示作业的类型。
One of the purposes of this attribute is to permit a requester to filter out jobs that are not of interest. For example, a printer operator MAY only be interested in jobs that include printing. That is why the attribute is in the job identification category.
此属性的目的之一是允许请求者筛选出不感兴趣的作业。例如，打印机操作员可能只对包含打印的作业感兴趣。这就是该属性位于职务标识类别中的原因。
The following service component types are defined (in hexadecimal) and are assigned a separate bit value for use with the jobServiceTypes attribute:
定义了以下服务组件类型（十六进制），并为其分配了单独的位值，以便与jobServiceTypes属性一起使用：
other 0x1 The job contains some instructions that are not one of the identified types.
其他0x1作业包含的某些指令不是标识的类型之一。
unknown 0x2 The job contains some instructions whose type is unknown to the agent.
未知0x2作业包含某些类型对代理未知的指令。
print 0x4 The job contains some instructions that specify printing
打印0x4作业包含一些指定打印的说明
scan 0x8 The job contains some instructions that specify scanning
扫描0x8作业包含一些指定扫描的说明
faxIn 0x10 The job contains some instructions that specify receive fax
传真在0x10中作业包含一些指定接收传真的指令
faxOut 0x20 The job contains some instructions that specify sending fax
传真输出0x20作业包含一些指定发送传真的指令
getFile 0x40 The job contains some instructions that specify accessing files or documents
getFile 0x40作业包含一些指定访问文件或文档的指令
putFile 0x80
putFile 0x80
The job contains some instructions that specify storing files or documents
该作业包含一些指定存储文件或文档的说明
mailList 0x100 The job contains some instructions that specify distribution of documents using an electronic mail system.
邮件列表0x100作业包含一些说明，用于指定使用电子邮件系统分发文档。
These bit definitions are the equivalent of a type 2 enum except that combinations of them MAY be used together. See section 3.7.1.2." SYNTAX INTEGER (0..2147483647) -- 31 bits, all but sign bit
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。请参阅第3.7.1.2节，“语法整数（0..2147483647）--31位，除符号位以外的所有位
JmJobStateReasons1TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The JmJobStateReasonsNTC (N=1..4) textual-conventions are used
with the jmJobStateReasons1 object and jobStateReasonsN
(N=2..4), respectively, to provide additional information
regarding the current jmJobState object value. These values
MAY be used with any job state or states for which the reason
makes sense. See section 3.3.9.1 for the specification of each
bit value defined for use with the JmJobStateReasons1TC.
JmJobStateReasons1TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The JmJobStateReasonsNTC (N=1..4) textual-conventions are used
with the jmJobStateReasons1 object and jobStateReasonsN
(N=2..4), respectively, to provide additional information
regarding the current jmJobState object value. These values
MAY be used with any job state or states for which the reason
makes sense. See section 3.3.9.1 for the specification of each
bit value defined for use with the JmJobStateReasons1TC.
These bit definitions are the equivalent of a type 2 enum except that combinations of bits may be used together. See section 3.7.1.2." SYNTAX INTEGER (0..2147483647) -- 31 bits, all but sign bit
这些位定义与类型2枚举等效，只是位的组合可以一起使用。请参阅第3.7.1.2节，“语法整数（0..2147483647）--31位，除符号位以外的所有位
JmJobStateReasons2TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual-convention is used with the jobStateReasons2
attribute to provides additional information regarding the
jmJobState object. See section 3.3.9.2 for the specification
of JmJobStateReasons2TC. See section 3.3.9.1 for the
description under JmJobStateReasons1TC for additional
information that applies to all reasons.
JmJobStateReasons2TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual-convention is used with the jobStateReasons2
attribute to provides additional information regarding the
jmJobState object. See section 3.3.9.2 for the specification
of JmJobStateReasons2TC. See section 3.3.9.1 for the
description under JmJobStateReasons1TC for additional
information that applies to all reasons.
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2." SYNTAX INTEGER (0..2147483647) -- 31 bits, all but sign bit
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。请参阅第3.7.1.2节，“语法整数（0..2147483647）--31位，除符号位以外的所有位
JmJobStateReasons3TC ::= TEXTUAL-CONVENTION
JmJobStateReasons3TC ::= TEXTUAL-CONVENTION
STATUS current DESCRIPTION "This textual-convention is used with the jobStateReasons3 attribute to provides additional information regarding the jmJobState object. See section 3.3.9.3 for the specification of JmJobStateReasons3TC. See section 3.3.9.1 for the description under JmJobStateReasons1TC for additional information that applies to all reasons.
状态当前描述“此文本约定与jobStateReasons3属性一起使用，以提供有关jmJobState对象的附加信息。有关JmJobStateReasons3TC的规范，请参见第3.3.9.3节。有关适用于所有原因的更多信息，请参见第3.3.9.1节JmJobStateReasons1TC下的说明。
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2. " SYNTAX INTEGER (0..2147483647) -- 31 bits, all but sign bit
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。见第3.7.1.2节。语法整数（0..2147483647）--31位，除符号位以外的所有位
JmJobStateReasons4TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual-convention is used in the jobStateReasons4
attribute to provides additional information regarding the
jmJobState object. See section 3.3.9.4 for the specification
of JmJobStateReasons4TC. See section 3.3.9.1 for the
description under JmJobStateReasons1TC for additional
information that applies to all reasons.
JmJobStateReasons4TC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual-convention is used in the jobStateReasons4
attribute to provides additional information regarding the
jmJobState object. See section 3.3.9.4 for the specification
of JmJobStateReasons4TC. See section 3.3.9.1 for the
description under JmJobStateReasons1TC for additional
information that applies to all reasons.
These bit definitions are the equivalent of a type 2 enum except that combinations of them may be used together. See section 3.7.1.2." SYNTAX INTEGER (0..2147483647) -- 31 bits, all but sign bit
这些位定义与类型2枚举等效，只是它们的组合可以一起使用。请参阅第3.7.1.2节，“语法整数（0..2147483647）--31位，除符号位以外的所有位
jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 }
jobmonMIBObjects OBJECT IDENTIFIER ::= { jobmonMIB 1 }
-- The General Group (MANDATORY)
--普通组（强制性）
-- The jmGeneralGroup consists entirely of the jmGeneralTable.
--jmGeneralGroup完全由jmGeneralTable组成。
jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 }
jmGeneral OBJECT IDENTIFIER ::= { jobmonMIBObjects 1 }
jmGeneralTable OBJECT-TYPE SYNTAX SEQUENCE OF JmGeneralEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
JmGeneralEntry MAX-ACCESS的jmGeneralTable对象类型语法序列不可访问状态当前描述
"The jmGeneralTable consists of information of a general nature that are per-job-set, but are not per-job. See Section 2 entitled 'Terminology and Job Model' for the definition of a job set.
jmGeneralTable包含每个作业集的一般性信息，但不是每个作业。有关作业集的定义，请参阅第2节“术语和作业模型”。
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmGeneral 1 }
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmGeneral 1 }
jmGeneralEntry OBJECT-TYPE SYNTAX JmGeneralEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a job set (queue).
jmGeneralEntry对象类型语法jmGeneralEntry MAX-ACCESS不可访问状态当前描述“有关作业集（队列）的信息”。
An entry SHALL exist in this table for each job set."
INDEX { jmGeneralJobSetIndex }
::= { jmGeneralTable 1 }
An entry SHALL exist in this table for each job set."
INDEX { jmGeneralJobSetIndex }
::= { jmGeneralTable 1 }
JmGeneralEntry ::= SEQUENCE {
jmGeneralJobSetIndex Integer32 (1..32767),
jmGeneralNumberOfActiveJobs Integer32 (0..2147483647),
jmGeneralOldestActiveJobIndex Integer32 (0..2147483647),
jmGeneralNewestActiveJobIndex Integer32 (0..2147483647),
jmGeneralJobPersistence Integer32 (15..2147483647),
jmGeneralAttributePersistence Integer32 (15..2147483647),
jmGeneralJobSetName JmUTF8StringTC (SIZE(0..63))
}
JmGeneralEntry ::= SEQUENCE {
jmGeneralJobSetIndex Integer32 (1..32767),
jmGeneralNumberOfActiveJobs Integer32 (0..2147483647),
jmGeneralOldestActiveJobIndex Integer32 (0..2147483647),
jmGeneralNewestActiveJobIndex Integer32 (0..2147483647),
jmGeneralJobPersistence Integer32 (15..2147483647),
jmGeneralAttributePersistence Integer32 (15..2147483647),
jmGeneralJobSetName JmUTF8StringTC (SIZE(0..63))
}
jmGeneralJobSetIndex OBJECT-TYPE SYNTAX Integer32 (1..32767) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value for each job set in this MIB. The jmJobTable and jmAttributeTable tables have this same index as their primary index.
jmGeneralJobSetIndex对象类型语法Integer32（1..32767）MAX-ACCESS不可访问状态当前描述“此MIB中每个作业集的唯一值。jmJobTable和jmAttributeTable表的此索引与其主索引相同。
The value(s) of the jmGeneralJobSetIndex SHALL be persistent across power cycles, so that clients that have retained jmGeneralJobSetIndex values will access the same job sets upon subsequent power-up.
jmGeneralJobSetIndex的值应在通电周期内保持不变，以便保留jmGeneralJobSetIndex值的客户端在随后通电时访问相同的作业集。
An implementation that has only one job set, such as a printer
只有一个作业集的实现，如打印机
with a single queue, SHALL hard code this object with the value 1.
对于单个队列，应使用值1硬编码此对象。
See Section 2 entitled 'Terminology and Job Model' for the
definition of a job set.
Corresponds to the first index in jmJobTable and
jmAttributeTable."
::= { jmGeneralEntry 1 }
See Section 2 entitled 'Terminology and Job Model' for the
definition of a job set.
Corresponds to the first index in jmJobTable and
jmAttributeTable."
::= { jmGeneralEntry 1 }
jmGeneralNumberOfActiveJobs OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of 'active' jobs in the jmJobIDTable,
jmJobTable, and jmAttributeTable, i.e., the total number of
jobs that are in the pending, processing, or processingStopped
states. See the JmJobStateTC textual-convention for the exact
specification of the semantics of the job states."
DEFVAL { 0 } -- no jobs
::= { jmGeneralEntry 2 }
jmGeneralNumberOfActiveJobs OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of 'active' jobs in the jmJobIDTable,
jmJobTable, and jmAttributeTable, i.e., the total number of
jobs that are in the pending, processing, or processingStopped
states. See the JmJobStateTC textual-convention for the exact
specification of the semantics of the job states."
DEFVAL { 0 } -- no jobs
::= { jmGeneralEntry 2 }
jmGeneralOldestActiveJobIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The jmJobIndex of the oldest job that is still in one of the 'active' states (pending, processing, or processingStopped). In other words, the index of the 'active' job that has been in the job tables the longest.
JMGeneralOldStactiveJobIndex对象类型语法整数32（0..2147483647）MAX-ACCESS只读状态当前描述“仍处于“活动”状态之一（挂起、处理或处理停止）的最旧作业的jmJobIndex。换句话说，作业表中最长的“活动”作业的索引。
If there are no active jobs, the agent SHALL set the value of this object to 0.
如果没有活动作业，代理应将此对象的值设置为0。
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes' for a description of the usage of
this object."
DEFVAL { 0 } -- no active jobs
::= { jmGeneralEntry 3 }
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes' for a description of the usage of
this object."
DEFVAL { 0 } -- no active jobs
::= { jmGeneralEntry 3 }
jmGeneralNewestActiveJobIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only
jmGeneralNewestActiveJobIndex对象类型语法整数32（0..2147483647）MAX-ACCESS只读
STATUS current DESCRIPTION "The jmJobIndex of the newest job that is in one of the 'active' states (pending, processing, or processingStopped). In other words, the index of the 'active' job that has been most recently added to the job tables.
STATUS current DESCRIPTION“处于“活动”状态之一（挂起、处理或处理停止）的最新作业的jmJobIndex。换句话说，最近添加到作业表中的“活动”作业的索引。
When all jobs become 'inactive', i.e., enter the pendingHeld, completed, canceled, or aborted states, the agent SHALL set the value of this object to 0.
当所有作业变为“非活动”，即进入pendingHeld、completed、Cancelled或aborted状态时，代理应将该对象的值设置为0。
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes' for a description of the usage of
this object."
DEFVAL { 0 } -- no active jobs
::= { jmGeneralEntry 4 }
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes' for a description of the usage of
this object."
DEFVAL { 0 } -- no active jobs
::= { jmGeneralEntry 4 }
jmGeneralJobPersistence OBJECT-TYPE SYNTAX Integer32 (15..2147483647) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum time in seconds for this instance of the Job Set that an entry SHALL remain in the jmJobIDTable and jmJobTable after processing has completed, i.e., the minimum time in seconds starting when the job enters the completed, canceled, or aborted state.
jmGeneralJobPersistence对象类型语法整数32（15..2147483647）单位“秒”最大访问只读状态当前说明“此作业集实例在处理完成后条目应保留在jmJobIDTable和jmJobTable中的最短时间（以秒为单位），即作业进入完成、取消或中止状态时开始的最短时间（以秒为单位）。
Configuring this object is implementation-dependent.
配置此对象取决于实现。
This value SHALL be equal to or greater than the value of
jmGeneralAttributePersistence. This value SHOULD be at least
60 which gives a monitoring or accounting application one
minute in which to poll for job data."
DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 5 }
This value SHALL be equal to or greater than the value of
jmGeneralAttributePersistence. This value SHOULD be at least
60 which gives a monitoring or accounting application one
minute in which to poll for job data."
DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 5 }
jmGeneralAttributePersistence OBJECT-TYPE SYNTAX Integer32 (15..2147483647) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION
jmGeneralAttributePersistence对象类型语法整数32（15..2147483647）单位“秒”最大访问只读状态当前说明
"The minimum time in seconds for this instance of the Job Set that an entry SHALL remain in the jmAttributeTable after processing has completed , i.e., the time in seconds starting when the job enters the completed, canceled, or aborted state.
“此作业集实例在处理完成后，条目应保留在jmAttributeTable中的最短时间（以秒为单位），即作业进入完成、取消或中止状态时开始的时间（以秒为单位）。
Configuring this object is implementation-dependent.
配置此对象取决于实现。
This value SHOULD be at least 60 which gives a monitoring or
accounting application one minute in which to poll for job
data."
DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 6 }
This value SHOULD be at least 60 which gives a monitoring or
accounting application one minute in which to poll for job
data."
DEFVAL { 60 } -- one minute
::= { jmGeneralEntry 6 }
jmGeneralJobSetName OBJECT-TYPE SYNTAX JmUTF8StringTC (SIZE(0..63)) MAX-ACCESS read-only STATUS current DESCRIPTION "The human readable name of this job set assigned by the system administrator (by means outside of this MIB). Typically, this name SHOULD be the name of the job queue. If a server or device has only a single job set, this object can be the administratively assigned name of the server or device itself. This name does not need to be unique, though each job set in a single Job Monitoring MIB SHOULD have distinct names.
jmGeneralJobSetName对象类型语法JmUTF8StringTC（大小（0..63））MAX-ACCESS只读状态当前描述“系统管理员分配的此作业集的可读名称（通过此MIB之外的方式）。通常，此名称应为作业队列的名称。如果服务器或设备只有一个作业集，则此对象可以是服务器或设备本身的管理分配名称。此名称不必唯一，但单个作业监控MIB中的每个作业集应具有不同的名称。
NOTE - If the job set corresponds to a single printer and the Printer MIB is implemented, this value SHOULD be the same as the prtGeneralPrinterName object in the draft Printer MIB [print-mib-draft]. If the job set corresponds to an IPP Printer, this value SHOULD be the same as the IPP 'printer-name' Printer attribute.
注意-如果作业集对应于单个打印机，并且实现了打印机MIB，则该值应与草稿打印机MIB[打印MIB草稿]中的prtGeneralPrinterName对象相同。如果作业集对应于IPP打印机，则此值应与IPP“打印机名称”打印机属性相同。
NOTE - The purpose of this object is to help the user of the job monitoring application distinguish between several job sets in implementations that support more than one job set.
注意-此对象的目的是帮助作业监视应用程序的用户区分支持多个作业集的实现中的多个作业集。
See the OBJECT compliance macro for the minimum maximum length
required for conformance."
DEFVAL { ''H } -- empty string
::= { jmGeneralEntry 7 }
See the OBJECT compliance macro for the minimum maximum length
required for conformance."
DEFVAL { ''H } -- empty string
::= { jmGeneralEntry 7 }
-- The Job ID Group (MANDATORY)
--作业ID组（必填）
-- The jmJobIDGroup consists entirely of the jmJobIDTable.
--jmJobIDGroup完全由jmJobIDTable组成。
jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 }
jmJobID OBJECT IDENTIFIER ::= { jobmonMIBObjects 2 }
jmJobIDTable OBJECT-TYPE SYNTAX SEQUENCE OF JmJobIDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The jmJobIDTable provides a correspondence map (1) between the job submission ID that a client uses to refer to a job and (2) the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring MIB agent assigned to the job and that are used to access the job in all of the other tables in the MIB. If a monitoring application already knows the jmGeneralJobSetIndex and the jmJobIndex of the job it is querying, that application NEED NOT use the jmJobIDTable.
jmJobIDTable对象类型jmJobIdentitry MAX-ACCESS的语法序列不可访问状态当前描述“jmJobIDTable提供客户端用于引用作业的作业提交ID与（2）之间的对应关系映射（1）作业监视MIB代理分配给该作业的jmGeneralJobSetIndex和jmJobIndex，用于访问MIB中所有其他表中的作业。如果监视应用程序已经知道它正在查询的作业的jmGeneralJobSetIndex和jmJobIndex，则该应用程序无需使用jmJobIDTable。
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmJobID 1 }
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmJobID 1 }
jmJobIDEntry OBJECT-TYPE SYNTAX JmJobIDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The map from (1) the jmJobSubmissionID to (2) the jmGeneralJobSetIndex and jmJobIndex.
JMJobIdentitry对象类型语法JMJobIdentitry MAX-ACCESS不可访问状态当前描述“从（1）jmJobSubmissionID到（2）jmGeneralJobSetIndex和jmJobIndex的映射。
An entry SHALL exist in this table for each job currently known
to the agent for all job sets and job states. There MAY be
more than one jmJobIDEntry that maps to a single job. This
many to one mapping can occur when more than one network entity
along the job submission path supplies a job submission ID.
See Section 3.5. However, each job SHALL appear once and in
one and only one job set."
INDEX { jmJobSubmissionID }
::= { jmJobIDTable 1 }
An entry SHALL exist in this table for each job currently known
to the agent for all job sets and job states. There MAY be
more than one jmJobIDEntry that maps to a single job. This
many to one mapping can occur when more than one network entity
along the job submission path supplies a job submission ID.
See Section 3.5. However, each job SHALL appear once and in
one and only one job set."
INDEX { jmJobSubmissionID }
::= { jmJobIDTable 1 }
JmJobIDEntry ::= SEQUENCE {
jmJobSubmissionID OCTET STRING(SIZE(48)),
jmJobIDJobSetIndex Integer32 (0..32767),
jmJobIDJobIndex Integer32 (0..2147483647)
}
JmJobIDEntry ::= SEQUENCE {
jmJobSubmissionID OCTET STRING(SIZE(48)),
jmJobIDJobSetIndex Integer32 (0..32767),
jmJobIDJobIndex Integer32 (0..2147483647)
}
jmJobSubmissionID OBJECT-TYPE
jmJobSubmissionID对象类型
SYNTAX OCTET STRING(SIZE(48)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A quasi-unique 48-octet fixed-length string ID which identifies the job within a particular client-server environment. There are multiple formats for the jmJobSubmissionID. Each format SHALL be uniquely identified. See the JmJobSubmissionIDTypeTC textual convention. Each format SHALL be registered using the procedures of a type 2 enum. See section 3.7.3 entitled: 'PWG Registration of Job Submission Id Formats'.
语法八位字节字符串（大小（48））MAX-ACCESS不可访问状态当前说明“一个准唯一的48个八位字节固定长度字符串ID，用于标识特定客户机-服务器环境中的作业。jmJobSubmissionID有多种格式。每种格式应唯一标识。请参阅JmJobSubmissionIDTypeTC文本约定。应使用2类枚举程序登记每种格式。见第3.7.3节，标题为：“工作提交Id格式的PWG注册”。
If the requester (client or server) does not supply a job submission ID in the job submission protocol, then the recipient (server or device) SHALL assign a job submission ID using any of the standard formats that have been reserved for agents and adding the final 8 octets to distinguish the ID from others submitted from the same requester.
如果请求者（客户端或服务器）未在作业提交协议中提供作业提交ID，则接收方（服务器或设备）应使用为代理保留的任何标准格式分配作业提交ID，并添加最后8个八位字节，以将ID与从同一请求者提交的其他ID区分开来。
The monitoring application, whether in the client or running separately, MAY use the job submission ID to help identify which jmJobIndex was assigned by the agent, i.e., in which row the job information is in the other tables.
监控应用程序，无论是在客户端还是单独运行，都可以使用作业提交ID来帮助识别代理分配了哪个jmJobIndex，即作业信息位于其他表中的哪一行。
NOTE - fixed-length is used so that a management application can use a shortened GetNext varbind (in SNMPv1 and SNMPv2) in order to get the next submission ID, disregarding the remainder of the ID in order to access jobs independent of the trailing identifier part, e.g., to get all jobs submitted by a particular jmJobOwner or submitted from a particular MAC address.
注意-使用固定长度，以便管理应用程序可以使用缩短的GetNext varbind（在SNMPv1和SNMPv2中）来获取下一个提交ID，而不考虑ID的其余部分，以便访问独立于尾随标识符部分的作业，例如。，获取由特定jmJobOwner提交或从特定MAC地址提交的所有作业。
See the JmJobSubmissionIDTypeTC textual convention.
See APPENDIX B - Support of Job Submission Protocols."
::= { jmJobIDEntry 1 }
See the JmJobSubmissionIDTypeTC textual convention.
See APPENDIX B - Support of Job Submission Protocols."
::= { jmJobIDEntry 1 }
jmJobIDJobSetIndex OBJECT-TYPE SYNTAX Integer32 (0..32767) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the value of the jmGeneralJobSetIndex for the job with the jmJobSubmissionID value, i.e., the job set index of the job set in which the job was placed when that server or device accepted the job. This 16-bit value in
jmJobIDJobSetIndex对象类型语法Integer32（0..32767）MAX-ACCESS只读状态当前描述“此对象包含具有jmJobSubmissionID值的作业的jmGeneralJobSetIndex值，即当服务器或设备接受作业时放置作业的作业集的作业集索引。此16位值在
combination with the jmJobIDJobIndex value permits the management application to access the other tables to obtain the job-specific objects for this job.
与jmJobIDJobIndex值的组合允许管理应用程序访问其他表以获取此作业的特定于作业的对象。
See jmGeneralJobSetIndex in the jmGeneralTable."
DEFVAL { 0 } -- 0 indicates no job set index
::= { jmJobIDEntry 2 }
See jmGeneralJobSetIndex in the jmGeneralTable."
DEFVAL { 0 } -- 0 indicates no job set index
::= { jmJobIDEntry 2 }
jmJobIDJobIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the value of the jmJobIndex for the job with the jmJobSubmissionID value, i.e., the job index for the job when the server or device accepted the job. This value, in combination with the jmJobIDJobSetIndex value, permits the management application to access the other tables to obtain the job-specific objects for this job.
jmJobIDJobIndex对象类型语法整数32（0..2147483647）最大访问只读状态当前说明“此对象包含具有jmJobSubmissionID值的作业的jmJobIndex值，即服务器或设备接受作业时该作业的作业索引。此值与jmJobIDJobSetIndex值结合使用，允许管理应用程序访问其他表以获取此作业的作业特定对象。
See jmJobIndex in the jmJobTable."
DEFVAL { 0 } -- 0 indicates no jmJobIndex value.
::= { jmJobIDEntry 3 }
See jmJobIndex in the jmJobTable."
DEFVAL { 0 } -- 0 indicates no jmJobIndex value.
::= { jmJobIDEntry 3 }
-- The Job Group (MANDATORY)
--工作组（必填）
-- The jmJobGroup consists entirely of the jmJobTable.
--jmJobGroup完全由jmJobTable组成。
jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 }
jmJob OBJECT IDENTIFIER ::= { jobmonMIBObjects 3 }
jmJobTable OBJECT-TYPE SYNTAX SEQUENCE OF JmJobEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The jmJobTable consists of basic job state and status information for each job in a job set that (1) monitoring applications need to be able to access in a single SNMP Get operation, (2) that have a single value per job, and (3) that SHALL always be implemented.
jmJobTable对象类型JmJobEntry MAX-ACCESS不可访问状态当前描述“jmJobTable包含作业集中每个作业的基本作业状态和状态信息，（1）监控应用程序需要能够在单个SNMP Get操作中访问，（2）每个作业具有单个值，以及（3）这一点应始终得到落实。
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmJob 1 }
The MANDATORY-GROUP macro specifies that this group is
MANDATORY."
::= { jmJob 1 }
jmJobEntry OBJECT-TYPE SYNTAX JmJobEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Basic per-job state and status information.
jmJobEntry对象类型语法jmJobEntry MAX-ACCESS不可访问状态当前描述“基本每个作业状态和状态信息”。
An entry SHALL exist in this table for each job, no matter what the state of the job is. Each job SHALL appear in one and only one job set.
无论作业的状态如何，此表中都应存在每个作业的条目。每个作业应仅出现在一个作业集中。
See Section 3.2 entitled 'The Job Tables'."
INDEX { jmGeneralJobSetIndex, jmJobIndex }
::= { jmJobTable 1 }
See Section 3.2 entitled 'The Job Tables'."
INDEX { jmGeneralJobSetIndex, jmJobIndex }
::= { jmJobTable 1 }
JmJobEntry ::= SEQUENCE {
jmJobIndex Integer32 (1..2147483647),
jmJobState JmJobStateTC,
jmJobStateReasons1 JmJobStateReasons1TC,
jmNumberOfInterveningJobs Integer32 (-2..2147483647),
jmJobKOctetsPerCopyRequested Integer32 (-2..2147483647),
jmJobKOctetsProcessed Integer32 (-2..2147483647),
jmJobImpressionsPerCopyRequested Integer32 (-2..2147483647),
jmJobImpressionsCompleted Integer32 (-2..2147483647),
jmJobOwner JmJobStringTC (SIZE(0..63))
}
JmJobEntry ::= SEQUENCE {
jmJobIndex Integer32 (1..2147483647),
jmJobState JmJobStateTC,
jmJobStateReasons1 JmJobStateReasons1TC,
jmNumberOfInterveningJobs Integer32 (-2..2147483647),
jmJobKOctetsPerCopyRequested Integer32 (-2..2147483647),
jmJobKOctetsProcessed Integer32 (-2..2147483647),
jmJobImpressionsPerCopyRequested Integer32 (-2..2147483647),
jmJobImpressionsCompleted Integer32 (-2..2147483647),
jmJobOwner JmJobStringTC (SIZE(0..63))
}
jmJobIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The sequential, monatonically increasing identifier index for the job generated by the server or device when that server or device accepted the job. This index value permits the management application to access the other tables to obtain the job-specific row entries.
jmJobIndex对象类型语法整数32（1..2147483647）MAX-ACCESS不可访问状态当前说明当服务器或设备接受作业时，该服务器或设备生成的作业的顺序的、单音递增的标识符索引。此索引值允许管理应用程序访问其他表以获取作业特定的行条目。
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes'.
See Section 3.5 entitled 'Job Identification'.
See also jmGeneralNewestActiveJobIndex for the largest value of
jmJobIndex.
See JmJobSubmissionIDTypeTC for a limit on the size of this
index if the agent represents it as an 8-digit decimal number."
::= { jmJobEntry 1 }
See Section 3.2 entitled 'The Job Tables and the Oldest Active
and Newest Active Indexes'.
See Section 3.5 entitled 'Job Identification'.
See also jmGeneralNewestActiveJobIndex for the largest value of
jmJobIndex.
See JmJobSubmissionIDTypeTC for a limit on the size of this
index if the agent represents it as an 8-digit decimal number."
::= { jmJobEntry 1 }
jmJobState OBJECT-TYPE SYNTAX JmJobStateTC MAX-ACCESS read-only STATUS current DESCRIPTION "The current state of the job (pending, processing, completed, etc.). Agents SHALL implement only those states which are appropriate for the particular implementation. However, management applications SHALL be prepared to receive all the standard job states.
jmJobState对象类型语法JmJobStateTC MAX-ACCESS只读状态当前描述“作业的当前状态（挂起、处理、完成等）。代理应仅实现适用于特定实现的状态。但是，管理应用程序应准备好接收所有标准作业状态。
The final value for this object SHALL be one of: completed,
canceled, or aborted. The minimum length of time that the
agent SHALL maintain MIB data for a job in the completed,
canceled, or aborted state before removing the job data from
the jmJobIDTable and jmJobTable is specified by the value of
the jmGeneralJobPersistence object."
DEFVAL { unknown } -- default is unknown
::= { jmJobEntry 2 }
The final value for this object SHALL be one of: completed,
canceled, or aborted. The minimum length of time that the
agent SHALL maintain MIB data for a job in the completed,
canceled, or aborted state before removing the job data from
the jmJobIDTable and jmJobTable is specified by the value of
the jmGeneralJobPersistence object."
DEFVAL { unknown } -- default is unknown
::= { jmJobEntry 2 }
jmJobStateReasons1 OBJECT-TYPE SYNTAX JmJobStateReasons1TC MAX-ACCESS read-only STATUS current DESCRIPTION "Additional information about the job's current state, i.e., information that augments the value of the job's jmJobState object.
jmJobStateReasons1对象类型语法JmJobStateReasons1TC MAX-ACCESS只读状态当前描述“有关作业当前状态的其他信息，即增加作业jmJobState对象值的信息。
Implementation of any reason values is OPTIONAL, but an agent SHOULD return any reason information available. These values MAY be used with any job state or states for which the reason makes sense. Since the Job State Reasons will be more dynamic than the Job State, it is recommended that a job monitoring application read this object every time jmJobState is read. When the agent cannot provide a reason for the current state of the job, the value of the jmJobStateReasons1 object and jobStateReasonsN attributes SHALL be 0.
任何原因值的实现都是可选的，但是代理应该返回任何可用的原因信息。这些值可用于任何作业状态或原因有意义的状态。由于作业状态原因将比作业状态更具动态性，因此建议作业监视应用程序在每次读取jmJobState时读取此对象。当代理无法提供作业当前状态的原因时，jmJobStateReasons1对象和jobStateReasonsN属性的值应为0。
The jobStateReasonsN (N=2..4) attributes provide further
additional information about the job's current state."
DEFVAL { 0 } -- no reasons
::= { jmJobEntry 3 }
The jobStateReasonsN (N=2..4) attributes provide further
additional information about the job's current state."
DEFVAL { 0 } -- no reasons
::= { jmJobEntry 3 }
jmNumberOfInterveningJobs OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of jobs that are expected to complete processing
before this job has completed processing according to the
implementation's queuing algorithm, if no other jobs were to be
submitted. In other words, this value is the job's queue
position. The agent SHALL return a value of 0 for this
attribute when the job is the next job to complete processing
(or has completed processing)."
DEFVAL { 0 } -- default is no intervening jobs.
::= { jmJobEntry 4 }
jmNumberOfInterveningJobs OBJECT-TYPE
SYNTAX Integer32 (-2..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of jobs that are expected to complete processing
before this job has completed processing according to the
implementation's queuing algorithm, if no other jobs were to be
submitted. In other words, this value is the job's queue
position. The agent SHALL return a value of 0 for this
attribute when the job is the next job to complete processing
(or has completed processing)."
DEFVAL { 0 } -- default is no intervening jobs.
::= { jmJobEntry 4 }
jmJobKOctetsPerCopyRequested OBJECT-TYPE SYNTAX Integer32 (-2..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The total size in K (1024) octets of the document(s) being requested to be processed in the job. The agent SHALL round the actual number of octets up to the next highest K. Thus 0 octets is represented as '0', 1-1024 octets is represented as '1', 1025-2048 is represented as '2', etc.
jmJobKOctetsPerCopyRequested对象类型语法整数32（-2..2147483647）MAX-ACCESS只读状态当前描述“文档的总大小（以K（1024）个八位字节为单位）被请求在作业中处理。代理应将八位字节的实际数量四舍五入到下一个最高K。因此，0个八位字节表示为“0”，1-1024个八位字节表示为“1”，1025-2048表示为“2”，以此类推。
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 and indicates the size of the document(s)
measured in K octets independent of the number of copies."
DEFVAL { -2 } -- the default is unknown(-2)
::= { jmJobEntry 5 }
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 and indicates the size of the document(s)
measured in K octets independent of the number of copies."
DEFVAL { -2 } -- the default is unknown(-2)
::= { jmJobEntry 5 }
jmJobKOctetsProcessed OBJECT-TYPE SYNTAX Integer32 (-2..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of octets processed by the server or device
jmJobKOctetsProcessed对象类型语法整数32（-2..2147483647）MAX-ACCESS只读状态当前说明“服务器或设备处理的八位字节总数
measured in units of K (1024) octets so far. The agent SHALL round the actual number of octets processed up to the next higher K. Thus 0 octets is represented as '0', 1-1024 octets is represented as '1', 1025-2048 octets is '2', etc. For printing devices, this value is the number interpreted by the page description language interpreter rather than what has been marked on media.
到目前为止，以K（1024）个八位组为单位测量。代理应将实际处理的八位字节数四舍五入到下一个更高的K。因此，0个八位字节表示为“0”，1-1024个八位字节表示为“1”，1025-2048个八位字节表示为“2”，等等。对于打印设备，该值是页面描述语言解释器解释的数字，而不是媒体上标记的数字。
For implementations where multiple copies are produced by the interpreter with only a single pass over the data, the final value SHALL be equal to the value of the jmJobKOctetsPerCopyRequested object. For implementations where multiple copies are produced by the interpreter by processing the data for each copy, the final value SHALL be a multiple of the value of the jmJobKOctetsPerCopyRequested object.
对于解释器仅通过一次数据传递生成多个副本的实现，最终值应等于jmJobKOctetsPerCopyRequested对象的值。对于解释器通过处理每个副本的数据生成多个副本的实现，最终值应为jmJobKOctetsPerCopyRequested对象值的倍数。
NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy.
注意-有关在每个文档副本上重置的属性，请参阅ImpressionCompletedCurrentCopy和pagesCompletedCurrentCopy属性。
NOTE - The jmJobKOctetsProcessed object can be used with the
jmJobKOctetsPerCopyRequested object to provide an indication of
the relative progress of the job, provided that the
multiplicative factor is taken into account for some
implementations of multiple copies."
DEFVAL { 0 } -- default is no octets processed.
::= { jmJobEntry 6 }
NOTE - The jmJobKOctetsProcessed object can be used with the
jmJobKOctetsPerCopyRequested object to provide an indication of
the relative progress of the job, provided that the
multiplicative factor is taken into account for some
implementations of multiple copies."
DEFVAL { 0 } -- default is no octets processed.
::= { jmJobEntry 6 }
jmJobImpressionsPerCopyRequested OBJECT-TYPE SYNTAX Integer32 (-2..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The total size in number of impressions of the document(s) submitted.
jmJobImpressionsPercopQuested对象类型语法整数32（-2..2147483647）MAX-ACCESS只读状态当前描述“提交的文档的总印象数大小。
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 and reflects the size of the document(s) measured in impressions independent of the number of copies.
在计算该值时，服务器/设备不应包括（1）文件副本数量和（2）作业副本数量的乘法因子，与设备是否可以处理作业或文档的多个副本而无需对作业或文档数据进行多次传递无关，也与是否整理输出无关。因此，服务器/设备的计算独立于实现，并反映了以印痕为单位测量的文档大小，与副本数量无关。
See the definition of the term 'impression' in Section 2."
参见第2节中“印象”一词的定义。”
DEFVAL { -2 } -- default is unknown(-2)
::= { jmJobEntry 7 }
DEFVAL { -2 } -- default is unknown(-2)
::= { jmJobEntry 7 }
jmJobImpressionsCompleted OBJECT-TYPE SYNTAX Integer32 (-2..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of impressions completed for this job so far. For printing devices, the impressions completed includes interpreting, marking, and stacking the output. For other types of job services, the number of impressions completed includes the number of impressions processed.
JMJobImpressionCompleted对象类型语法整数32（-2..2147483647）MAX-ACCESS只读状态当前说明他说:"到目前为止,这项工作已完成的印象总数,。对于打印设备，完成的印象包括解释、标记和堆叠输出。对于其他类型的工作服务，完成的印象数包括处理的印象数。
NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy.
注意-有关在每个文档副本上重置的属性，请参阅ImpressionCompletedCurrentCopy和pagesCompletedCurrentCopy属性。
NOTE - The jmJobImpressionsCompleted object can be used with the jmJobImpressionsPerCopyRequested object to provide an indication of the relative progress of the job, provided that the multiplicative factor is taken into account for some implementations of multiple copies.
注意-jmJobImpressionsCompleted对象可以与JMJobImpressionsPercopQuested对象一起使用，以提供作业相对进度的指示，前提是在多个副本的某些实现中考虑了乘法因子。
See the definition of the term 'impression' in Section 2 and
the counting example in Section 3.4 entitled 'Monitoring Job
Progress'."
DEFVAL { 0 } -- default is no octets
::= { jmJobEntry 8 }
See the definition of the term 'impression' in Section 2 and
the counting example in Section 3.4 entitled 'Monitoring Job
Progress'."
DEFVAL { 0 } -- default is no octets
::= { jmJobEntry 8 }
jmJobOwner OBJECT-TYPE SYNTAX JmJobStringTC (SIZE(0..63)) MAX-ACCESS read-only STATUS current DESCRIPTION "The coded character set name of the user that submitted the job. The method of assigning this user name will be system and/or site specific but the method MUST ensure that the name is unique to the network that is visible to the client and target device.
jmJobOwner对象类型语法JmJobStringTC（大小（0..63））MAX-ACCESS只读状态当前说明“提交作业的用户的编码字符集名称。分配此用户名的方法将是特定于系统和/或站点的，但该方法必须确保该名称对于客户端和目标设备可见的网络是唯一的。
This value SHOULD be the most authenticated name of the user submitting the job.
此值应该是提交作业的用户的最经过身份验证的名称。
See the OBJECT compliance macro for the minimum maximum length
有关最小最大长度，请参见对象符合性宏
required for conformance."
DEFVAL { ''H } -- default is empty string
::= { jmJobEntry 9 }
required for conformance."
DEFVAL { ''H } -- default is empty string
::= { jmJobEntry 9 }
-- The Attribute Group (MANDATORY)
--属性组（必需）
-- The jmAttributeGroup consists entirely of the jmAttributeTable.
--
-- Implementation of the objects in this group is MANDATORY.
-- See Section 3.1 entitled 'Conformance Considerations'.
-- An agent SHALL implement any attribute if (1) the server or device
-- supports the functionality represented by the attribute and (2) the
-- information is available to the agent.
-- The jmAttributeGroup consists entirely of the jmAttributeTable.
--
-- Implementation of the objects in this group is MANDATORY.
-- See Section 3.1 entitled 'Conformance Considerations'.
-- An agent SHALL implement any attribute if (1) the server or device
-- supports the functionality represented by the attribute and (2) the
-- information is available to the agent.
jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 }
jmAttribute OBJECT IDENTIFIER ::= { jobmonMIBObjects 4 }
jmAttributeTable OBJECT-TYPE SYNTAX SEQUENCE OF JmAttributeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The jmAttributeTable SHALL contain attributes of the job and document(s) for each job in a job set. Instead of allocating distinct objects for each attribute, each attribute is represented as a separate row in the jmAttributeTable.
jmAttributeTable对象类型JmAttributeEntry MAX-ACCESS的语法序列不可访问状态当前描述“jmAttributeTable应包含作业和文档的属性对于作业集中的每个作业。每个属性在jmAttributeTable中表示为一个单独的行，而不是为每个属性分配不同的对象。
The MANDATORY-GROUP macro specifies that this group is
MANDATORY. An agent SHALL implement any attribute if (1) the
server or device supports the functionality represented by the
attribute and (2) the information is available to the agent. "
::= { jmAttribute 1 }
The MANDATORY-GROUP macro specifies that this group is
MANDATORY. An agent SHALL implement any attribute if (1) the
server or device supports the functionality represented by the
attribute and (2) the information is available to the agent. "
::= { jmAttribute 1 }
jmAttributeEntry OBJECT-TYPE SYNTAX JmAttributeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Attributes representing information about the job and document(s) or resources required and/or consumed.
jmAttributeEntry对象类型语法jmAttributeEntry MAX-ACCESS不可访问状态当前描述“表示有关所需和/或消耗的作业和文档或资源的信息的属性。
Each entry in the jmAttributeTable is a per-job entry with an extra index for each type of attribute (jmAttributeTypeIndex) that a job can have and an additional index (jmAttributeInstanceIndex) for those attributes that can have
jmAttributeTable中的每个条目都是一个每个作业条目，每个作业可以具有的属性类型（jmAttributeTypeIndex）都有一个额外的索引，这些属性可以具有一个额外的索引（jmAttributeInstanceIndex）
multiple instances per job. The jmAttributeTypeIndex object SHALL contain an enum type that indicates the type of attribute (see the JmAttributeTypeTC textual-convention). The value of the attribute SHALL be represented in either the jmAttributeValueAsInteger or jmAttributeValueAsOctets objects, and/or both, as specified in the JmAttributeTypeTC textual-convention.
每个作业有多个实例。jmAttributeTypeIndex对象应包含指示属性类型的枚举类型（请参阅JmAttributeTypeTC文本约定）。根据JmAttributeTypeTC文本约定的规定，属性值应在jmAttributeValueAsInteger或jmAttributeValueAsOctets对象中表示，和/或两者都表示。
The agent SHALL create rows in the jmAttributeTable as the server or device is able to discover the attributes either from the job submission protocol itself or from the document PDL. As the documents are interpreted, the interpreter MAY discover additional attributes and so the agent adds additional rows to this table. As the attributes that represent resources are actually consumed, the usage counter contained in the jmAttributeValueAsInteger object is incremented according to the units indicated in the description of the JmAttributeTypeTC enum.
当服务器或设备能够从作业提交协议本身或文档PDL中发现属性时，代理应在jmAttributeTable中创建行。在解释文档时，解释器可能会发现其他属性，因此代理会将其他行添加到此表中。当表示资源的属性实际被消耗时，jmAttributeValueAsInteger对象中包含的使用计数器将根据JmAttributeTypeTC枚举描述中指示的单位递增。
The agent SHALL maintain each row in the jmAttributeTable for at least the minimum time after a job completes as specified by the jmGeneralAttributePersistence object.
代理应在作业完成后，按照jmGeneralAttributePersistence对象的规定，至少在最短时间内维护jmAttributeTable中的每一行。
Zero or more entries SHALL exist in this table for each job in a job set.
对于作业集中的每个作业，此表中应存在零个或多个条目。
See Section 3.3 entitled 'The Attribute Mechanism' for a
description of the jmAttributeTable."
INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex,
jmAttributeInstanceIndex }
::= { jmAttributeTable 1 }
See Section 3.3 entitled 'The Attribute Mechanism' for a
description of the jmAttributeTable."
INDEX { jmGeneralJobSetIndex, jmJobIndex, jmAttributeTypeIndex,
jmAttributeInstanceIndex }
::= { jmAttributeTable 1 }
JmAttributeEntry ::= SEQUENCE {
jmAttributeTypeIndex JmAttributeTypeTC,
jmAttributeInstanceIndex Integer32 (1..32767),
jmAttributeValueAsInteger Integer32 (-2..2147483647),
jmAttributeValueAsOctets OCTET STRING(SIZE(0..63))
}
JmAttributeEntry ::= SEQUENCE {
jmAttributeTypeIndex JmAttributeTypeTC,
jmAttributeInstanceIndex Integer32 (1..32767),
jmAttributeValueAsInteger Integer32 (-2..2147483647),
jmAttributeValueAsOctets OCTET STRING(SIZE(0..63))
}
jmAttributeTypeIndex OBJECT-TYPE SYNTAX JmAttributeTypeTC MAX-ACCESS not-accessible STATUS current DESCRIPTION "The type of attribute that this row entry represents.
jmAttributeTypeIndex对象类型语法JMAttributeTypec MAX-ACCESS不可访问状态当前描述“此行条目表示的属性类型。
The type MAY identify information about the job or document(s)
该类型可以标识有关作业或文档的信息
or MAY identify a resource required to process the job before the job start processing and/or consumed by the job as the job is processed.
或者可以标识在作业开始处理之前处理作业所需的资源和/或在处理作业时由作业消耗的资源。
Examples of job attributes (i.e., apply to the job as a whole) that have only one instance per job include: jobCopiesRequested(90), documentCopiesRequested(92), jobCopiesCompleted(91), documentCopiesCompleted(93), while examples of job attributes that may have more than one instance per job include: documentFormatIndex(37), and documentFormat(38).
每个作业只有一个实例的作业属性示例（即，应用于整个作业）包括：jobCopiesRequested（90）、documentCopiesRequested（92）、jobCopiesCompleted（91）、documentCopiesCompleted（93），而每个作业可能有多个实例的作业属性示例包括：documentFormatIndex（37）和documentFormat（38）。
Examples of document attributes (one instance per document) include: fileName(34), and documentName(35).
文档属性的示例（每个文档一个实例）包括：fileName（34）和documentName（35）。
Examples of required and consumed resource attributes include:
pagesRequested(130), mediumRequested(170), pagesCompleted(131),
and mediumConsumed(171), respectively."
::= { jmAttributeEntry 1 }
Examples of required and consumed resource attributes include:
pagesRequested(130), mediumRequested(170), pagesCompleted(131),
and mediumConsumed(171), respectively."
::= { jmAttributeEntry 1 }
jmAttributeInstanceIndex OBJECT-TYPE
SYNTAX Integer32 (1..32767)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A running 16-bit index of the attributes of the same type for
each job. For those attributes with only a single instance per
job, this index value SHALL be 1. For those attributes that
are a single value per document, the index value SHALL be the
document number, starting with 1 for the first document in the
job. Jobs with only a single document SHALL use the index
value of 1. For those attributes that can have multiple values
per job or per document, such as documentFormatIndex(37) or
documentFormat(38), the index SHALL be a running index for the
job as a whole, starting at 1."
::= { jmAttributeEntry 2 }
jmAttributeInstanceIndex OBJECT-TYPE
SYNTAX Integer32 (1..32767)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A running 16-bit index of the attributes of the same type for
each job. For those attributes with only a single instance per
job, this index value SHALL be 1. For those attributes that
are a single value per document, the index value SHALL be the
document number, starting with 1 for the first document in the
job. Jobs with only a single document SHALL use the index
value of 1. For those attributes that can have multiple values
per job or per document, such as documentFormatIndex(37) or
documentFormat(38), the index SHALL be a running index for the
job as a whole, starting at 1."
::= { jmAttributeEntry 2 }
jmAttributeValueAsInteger OBJECT-TYPE SYNTAX Integer32 (-2..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The integer value of the attribute. The value of the attribute SHALL be represented as an integer if the enum
jmAttributeValueAsInteger对象类型语法Integer32（-2..2147483647）MAX-ACCESS只读状态当前描述“属性的整数值。如果枚举
description in the JmAttributeTypeTC textual-convention definition has the tag: 'INTEGER:'.
JmAttributeTypeTC文本约定定义中的描述具有标记：“INTEGER:”。
Depending on the enum definition, this object value MAY be an integer, a counter, an index, or an enum, depending on the jmAttributeTypeIndex value. The units of this value are specified in the enum description.
根据枚举定义，此对象值可以是整数、计数器、索引或枚举，具体取决于jmAttributeTypeIndex值。此值的单位在枚举描述中指定。
For those attributes that are accumulating job consumption as the job is processed as specified in the JmAttributeTypeTC textual-convention, SHALL contain the final value after the job completes processing, i.e., this value SHALL indicate the total usage of this resource made by the job.
对于那些在按照JmAttributeTypeTC文本约定处理作业时累积作业消耗的属性，应包含作业完成处理后的最终值，即，该值应指示作业对该资源的总使用量。
A monitoring application is able to copy this value to a suitable longer term storage for later processing as part of an accounting system.
监控应用程序能够将该值复制到适当的长期存储器中，以便作为会计系统的一部分进行后续处理。
Since the agent MAY add attributes representing resources to this table while the job is waiting to be processed or being processed, which can be a long time before any of the resources are actually used, the agent SHALL set the value of the jmAttributeValueAsInteger object to 0 for resources that the job has not yet consumed.
由于代理可以在作业等待处理或正在处理时将表示资源的属性添加到此表中，这可能需要很长时间才能实际使用任何资源，因此对于作业尚未消耗的资源，代理应将jmAttributeValueAsInteger对象的值设置为0。
Attributes for which the concept of an integer value is meaningless, such as fileName(34), jobName, and processingMessage, do not have the 'INTEGER:' tag in the JmAttributeTypeTC definition and so an agent SHALL always return a value of '-1' to indicate 'other' for the value of the jmAttributeValueAsInteger object for these attributes.
对于整数值概念没有意义的属性，例如fileName（34）、jobName和processingMessage，在JmAttributeTypeTC定义中没有“integer:”标记，因此代理应始终返回值“-1”，以指示这些属性的jmAttributeValueAsInteger对象的值为“other”。
For attributes which do have the 'INTEGER:' tag in the
JmAttributeTypeTC definition, if the integer value is not (yet)
known, the agent either (1) SHALL not materialize the row in
the jmAttributeTable until the value is known or (2) 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."
DEFVAL { -2 } -- default value is unknown(-2)
::= { jmAttributeEntry 3 }
For attributes which do have the 'INTEGER:' tag in the
JmAttributeTypeTC definition, if the integer value is not (yet)
known, the agent either (1) SHALL not materialize the row in
the jmAttributeTable until the value is known or (2) 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."
DEFVAL { -2 } -- default value is unknown(-2)
::= { jmAttributeEntry 3 }
jmAttributeValueAsOctets OBJECT-TYPE SYNTAX OCTET STRING(SIZE(0..63)) MAX-ACCESS read-only STATUS current
jmAttributeValueAsOctets对象类型语法八位字节字符串（大小（0..63））最大访问只读状态当前
DESCRIPTION "The octet string value of the attribute. The value of the attribute SHALL be represented as an OCTET STRING if the enum description in the JmAttributeTypeTC textual-convention definition has the tag: 'OCTETS:'.
DESCRIPTION“属性的八位字节字符串值。如果JmAttributeTypeTC文本约定定义中的枚举描述具有标记：‘八位字节：’，则属性的值应表示为八位字节字符串。
Depending on the enum definition, this object value MAY be a coded character set string (text), such as 'JmUTF8StringTC', or a binary octet string, such as 'DateAndTime'.
根据枚举定义，此对象值可以是编码字符集字符串（文本），如“JmUTF8StringTC”，也可以是二进制八位字符串，如“DateAndTime”。
Attributes for which the concept of an octet string value is meaningless, such as pagesCompleted, do not have the tag 'OCTETS:' in the JmAttributeTypeTC definition and so the agent SHALL always return a zero length string for the value of the jmAttributeValueAsOctets object.
八位字节字符串值的概念没有意义的属性，例如pagesCompleted，在JmAttributeTypeTC定义中没有标记“OCTETS:”，因此代理应始终为jmAttributeValueAsOctets对象的值返回零长度字符串。
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."
DEFVAL { ''H } -- empty string
::= { jmAttributeEntry 4 }
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."
DEFVAL { ''H } -- empty string
::= { jmAttributeEntry 4 }
-- Notifications and Trapping
-- Reserved for the future
-- Notifications and Trapping
-- Reserved for the future
jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2 }
jobmonMIBNotifications OBJECT IDENTIFIER ::= { jobmonMIB 2 }
-- Conformance Information
--一致性信息
jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 }
jmMIBConformance OBJECT IDENTIFIER ::= { jobmonMIB 3 }
-- compliance statements
jmMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agents that implement the
job monitoring MIB."
MODULE -- this module
MANDATORY-GROUPS {
jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup }
-- compliance statements
jmMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agents that implement the
job monitoring MIB."
MODULE -- this module
MANDATORY-GROUPS {
jmGeneralGroup, jmJobIDGroup, jmJobGroup, jmAttributeGroup }
OBJECT jmGeneralJobSetName SYNTAX JmUTF8StringTC (SIZE(0..8)) DESCRIPTION "Only 8 octets maximum string length NEED be supported by the agent."
对象jmGeneralJobSetName语法JmUTF8StringTC（大小（0..8））说明“代理只需要支持8个八位字节的最大字符串长度。”
OBJECT jmJobOwner SYNTAX JmJobStringTC (SIZE(0..16)) DESCRIPTION "Only 16 octets maximum string length NEED be supported by the agent."
对象jmJobOwner语法JmJobStringTC（大小（0..16））说明“代理只需要支持16个八位字节的最大字符串长度。”
-- There are no CONDITIONALLY MANDATORY or OPTIONAL groups.
--没有条件强制或可选的组。
::= { jmMIBConformance 1 }
::= { jmMIBConformance 1 }
jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 }
jmMIBGroups OBJECT IDENTIFIER ::= { jmMIBConformance 2 }
jmGeneralGroup OBJECT-GROUP
OBJECTS {
jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex,
jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence,
jmGeneralAttributePersistence, jmGeneralJobSetName}
STATUS current
DESCRIPTION
"The general group."
::= { jmMIBGroups 1 }
jmGeneralGroup OBJECT-GROUP
OBJECTS {
jmGeneralNumberOfActiveJobs, jmGeneralOldestActiveJobIndex,
jmGeneralNewestActiveJobIndex, jmGeneralJobPersistence,
jmGeneralAttributePersistence, jmGeneralJobSetName}
STATUS current
DESCRIPTION
"The general group."
::= { jmMIBGroups 1 }
jmJobIDGroup OBJECT-GROUP
OBJECTS {
jmJobIDJobSetIndex, jmJobIDJobIndex }
STATUS current
DESCRIPTION
"The job ID group."
::= { jmMIBGroups 2 }
jmJobIDGroup OBJECT-GROUP
OBJECTS {
jmJobIDJobSetIndex, jmJobIDJobIndex }
STATUS current
DESCRIPTION
"The job ID group."
::= { jmMIBGroups 2 }
jmJobGroup OBJECT-GROUP
OBJECTS {
jmJobState, jmJobStateReasons1, jmNumberOfInterveningJobs,
jmJobKOctetsPerCopyRequested, jmJobKOctetsProcessed,
jmJobImpressionsPerCopyRequested, jmJobImpressionsCompleted,
jmJobOwner }
STATUS current
jmJobGroup OBJECT-GROUP
OBJECTS {
jmJobState, jmJobStateReasons1, jmNumberOfInterveningJobs,
jmJobKOctetsPerCopyRequested, jmJobKOctetsProcessed,
jmJobImpressionsPerCopyRequested, jmJobImpressionsCompleted,
jmJobOwner }
STATUS current
DESCRIPTION
"The job group."
::= { jmMIBGroups 3 }
DESCRIPTION
"The job group."
::= { jmMIBGroups 3 }
jmAttributeGroup OBJECT-GROUP
OBJECTS {
jmAttributeValueAsInteger, jmAttributeValueAsOctets }
STATUS current
DESCRIPTION
"The attribute group."
::= { jmMIBGroups 4 }
jmAttributeGroup OBJECT-GROUP
OBJECTS {
jmAttributeValueAsInteger, jmAttributeValueAsOctets }
STATUS current
DESCRIPTION
"The attribute group."
::= { jmMIBGroups 4 }
END
终止
5 Appendix A - Implementing the Job Life Cycle
5附录A-实施工作生命周期
The job object has well-defined states and client operations that affect the transition between the job states. Internal server and device actions also affect the transitions of the job between the job states. These states and transitions are referred to as the job's life cycle.
作业对象具有定义良好的状态和影响作业状态之间转换的客户端操作。内部服务器和设备操作也会影响作业状态之间的转换。这些状态和转换称为作业的生命周期。
Not all implementations of job submission protocols have all of the states of the job model specified here. The job model specified here is intended to be a superset of most implementations. It is the purpose of the agent to map the particular implementation's job life cycle onto the one specified here. The agent MAY omit any states not implemented. Only the processing and completed states are required to be implemented by an agent. However, a conforming management application SHALL be prepared to accept any of the states in the job life cycle specified here, so that the management application can interoperate with any conforming agent.
并非所有作业提交协议的实现都具有此处指定的作业模型的所有状态。此处指定的作业模型旨在成为大多数实现的超集。代理的目的是将特定实现的作业生命周期映射到此处指定的作业生命周期。代理可以省略任何未实现的状态。代理只需要实现处理状态和完成状态。但是，应准备一份合格的管理应用程序，以接受此处规定的工作生命周期中的任何状态，以便管理应用程序能够与任何合格代理进行互操作。
The job states are intended to be user visible. The agent SHALL make these states visible in the MIB, but only for the subset of job states that the implementation has. Some implementations MAY need to have sub-states of these user-visible states. The jmJobStateReasons1 object and the jobStateReasonsN (N=2..4) attributes can be used to represent the sub-states of the jobs.
作业状态旨在让用户可见。代理应使这些状态在MIB中可见，但仅适用于实现所具有的作业状态子集。一些实现可能需要这些用户可见状态的子状态。jmJobStateReasons1对象和jobStateReasonsN（N=2..4）属性可用于表示作业的子状态。
Job states are intended to last a user-visible length of time in most implementations. However, some jobs may pass through some states in zero time in some situations and/or in some implementations.
在大多数实现中，作业状态旨在持续用户可见的时间长度。但是，在某些情况和/或某些实现中，某些作业可能会在零时间内通过某些状态。
The job model does not specify how accounting and auditing is implemented, except to assume that accounting and auditing logs are separate from the job life cycle and last longer than job entries in the MIB. Jobs in the completed, aborted, or canceled states are not logs, since jobs in these states are accessible via SNMP protocol operations and SHALL be removed from the Job Monitoring MIB tables after a site-settable or implementation-defined period of time. An accounting application MAY copy accounting information incrementally to an accounting log as a job processes, or MAY be copied while the job is in the canceled, aborted, or completed states, depending on implementation. The same is true for auditing logs.
作业模型不指定如何实现记帐和审核，除非假定记帐和审核日志与作业生命周期分开，并且持续时间长于MIB中的作业条目。处于完成、中止或取消状态的作业不是日志，因为这些状态的作业可以通过SNMP协议操作访问，并且在站点可设置或实施定义的时间段后，应从作业监控MIB表中删除。会计应用程序可以将会计信息作为作业处理增量复制到会计日志中，也可以在作业处于取消、中止或完成状态时进行复制，具体取决于实现。审核日志也是如此。
The jmJobState object specifies the standard job states. The normal job state transitions are shown in the state transition diagram presented in Figure 4.
jmJobState对象指定标准作业状态。正常的作业状态转换如图4所示的状态转换图所示。
6 APPENDIX B - Support of Job Submission Protocols
6附录B-作业提交协议的支持
A companion PWG document, entitled "Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB" [protomap] contains the recommended usage of each of the objects and attributes in this MIB with a number of job submission protocols. In particular, which job submission ID format should be used is indicated for each job submission protocol.
一份名为“作业监控MIB的作业提交协议映射建议”的配套PWG文档[protomap]包含此MIB中每个对象和属性的推荐用法，以及许多作业提交协议。特别是，应为每个作业提交协议指定应使用的作业提交ID格式。
Some job submission protocols have support for the client to specify a job submission ID. A second approach is to enhance the document format to embed the job submission ID in the document data. This second approach is independent of the job submission protocol. This appendix lists some examples of these approaches.
一些作业提交协议支持客户端指定作业提交ID。第二种方法是增强文档格式，将作业提交ID嵌入文档数据中。第二种方法独立于作业提交协议。本附录列出了这些方法的一些示例。
Some PJL implementations wrap a banner page as a PJL job around a job submitted by a client. If this results in multiple job submission IDs, the agent SHALL create multiple jmJobIDEntry rows in the jmJobIDTable that each point to the same job entry in the job tables. See the specification of the jmJobIDEntry.
一些PJL实现将横幅页面包装为围绕客户端提交的作业的PJL作业。如果这导致多个作业提交ID，代理应在jmJobIDTable中创建多个JMJobIdentity行，每个行指向作业表中的同一作业条目。请参阅JMJobIdentity的规范。
7 References
7参考文献
[BCP-11] Bradner S. and R. Hovey, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[BCP-11]Bradner S.和R.Hovey，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。
[GB2312] GB 2312-1980, "Chinese People's Republic of China (PRC) mixed one byte and two byte coded character set"
[GB2312]GB 2312-1980《中华人民共和国单字节和双字节混合编码字符集》
[hr-mib] Grillo, P. and S. Waldbusser, "Host Resources MIB", RFC 1514, September 1993.
[hr mib]Grillo，P.和S.Waldbusser，“主机资源mib”，RFC 15141993年9月。
[iana] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994.
[iana]Reynolds，J.和J.Postel，“分配的数字”，标准2，RFC 1700，1994年10月。
[IANA-charsets] Coded Character Sets registered by IANA and
assigned an enum value for use in the CodedCharSet
textual convention imported from the Printer MIB.
See ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets
[IANA-charsets] Coded Character Sets registered by IANA and
assigned an enum value for use in the CodedCharSet
textual convention imported from the Printer MIB.
See ftp://ftp.isi.edu/in-
notes/iana/assignments/character-sets
[iana-media-types] IANA Registration of MIME media types (MIME
content types/subtypes). See
ftp://ftp.isi.edu/in-notes/iana/assignments/
[iana-media-types] IANA Registration of MIME media types (MIME
content types/subtypes). See
ftp://ftp.isi.edu/in-notes/iana/assignments/
[ipp-model] deBry, R., Hastings, T., Herriot, R., Issaacson, S. and P. Powell, "The Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, April 1999.
[ipp模型]deBry，R.，Hastings，T.，Herriot，R.，Issaacson，S.和P.Powell，“互联网打印协议/1.0：模型和语义”，RFC 2566，1999年4月。
[ISO-639] ISO 639:1988 (E/F) - Code for Representation of names of languages - The International Organization for Standardization, 1st edition, 1988.
[ISO-639]ISO 639:1988（E/F）-语言名称表示代码-国际标准化组织，第1版，1988年。
[ISO-646] ISO/IEC 646:1991, "Information technology -- ISO 7-bit coded character set for information interchange", JTC1/SC2.
[ISO-646]ISO/IEC 646:1991，“信息技术——信息交换用ISO 7位编码字符集”，JTC1/SC2。
[ISO-2022] ISO/IEC 2022:1994 - "Information technology -- Character code structure and extension techniques", JTC1/SC2.
[ISO-2022]ISO/IEC 2022:1994-“信息技术——字符代码结构和扩展技术”，JTC1/SC2。
[ISO-3166] ISO 3166:1988 (E/F) - Codes for representation of names of countries - The International Organization for Standardization, 3rd edition, 1988-08-15."
[ISO-3166]ISO 3166:1988（E/F）-国家名称表示代码-国际标准化组织，第3版，1988-08-15。”
[ISO-8859-1] ISO/IEC 8859-1:1987, "Information technology --
8-bit single byte coded graphic character sets -
Part 1: Latin alphabet No. 1, JTC1/SC2."
[ISO-8859-1] ISO/IEC 8859-1:1987, "Information technology --
8-bit single byte coded graphic character sets -
Part 1: Latin alphabet No. 1, JTC1/SC2."
[ISO-10646] ISO/IEC 10646-1:1993, "Information technology -- Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane, JTC1/SC2.
[ISO-10646]ISO/IEC 10646-1:1993，“信息技术——通用多八位编码字符集（UCS）——第1部分：体系结构和基本多语言平面，JTC1/SC2。
[iso-dpa] ISO/IEC 10175-1:1996 "Information technology --
Text and Office Systems -- Document Printing
Application (DPA) -- Part 1: Abstract service
definition and procedures. See
ftp://ftp.pwg.org/pub/pwg/dpa/
[iso-dpa] ISO/IEC 10175-1:1996 "Information technology --
Text and Office Systems -- Document Printing
Application (DPA) -- Part 1: Abstract service
definition and procedures. See
ftp://ftp.pwg.org/pub/pwg/dpa/
[JIS X0208] JIS X0208-1990, "Japanese two byte coded character set."
[JIS X0208]JIS X0208-1990，“日语双字节编码字符集。”
[mib-II] McCloghrie, K. and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
[mib II]McCloghrie，K.和M.Rose，“基于TCP/IP的互联网网络管理的管理信息库：mib-II”，STD 17，RFC 1213，1991年3月。
[print-mib] Smith, R., Wright, F., Hastings, T., Zilles, S. and J. Gyllenskog, "Printer MIB", RFC 1759, March 1995.
[print mib]史密斯，R.，赖特，F.，黑斯廷斯，T.，齐尔斯，S.和J.吉伦斯科格，“打印机mib”，RFC 1759，1995年3月。
[print-mib-draft] Turner, R., "Printer MIB", Work in Progress,
[打印mib草稿]特纳，R.，“打印机mib”，正在进行中，
[protomap] Bergman, R., "Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB", RFC 2708, November 1999.
[protomap]Bergman，R.，“作业监控MIB的作业提交协议映射建议”，RFC 2708，1999年11月。
[pwg] The Printer Working Group is a printer industry consortium open to any individuals. For more information, access the PWG web page: http://www.pwg.org
[pwg]打印机工作组是一个向任何个人开放的打印机行业联盟。有关更多信息，请访问PWG网页：http://www.pwg.org
[RFC1179] McLaughlin, L., III, "Line Printer Daemon Protocol", RFC 1179, August 1990.
[RFC1179]McLaughlin，L.，III，“线路打印机守护程序协议”，RFC1179，1990年8月。
[RFC1738] Berners-Lee, T., Masinter, L. and M., McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[RFC1738]Berners Lee，T.，Masinter，L.和M.，McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[RFC1766] Avelstrand, H., "Tags for the Identification of Languages", RFC 1766, March 1995.
[RFC1766]Avelstrand，H.，“语言识别标签”，RFC1766，1995年3月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Keywords for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于指示需求水平的关键字”，BCP 14，RFC 2119，1997年3月。
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and Languages", BCP 18, RFC 2277, January 1998.
[RFC2277]Alvestrand，H.，“IETF字符集和语言政策”，BCP 18，RFC 2277，1998年1月。
[RFC2278] Freed, N. and J. Postel, "IANA CharSet Registration Procedures", BCP 19, RFC 2278, January 1998.
[RFC2278]Freed，N.和J.Postel，“IANA字符集注册程序”，BCP 19，RFC 2278，1998年1月。
[SMIv2-SMI] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[SMIv2 SMI]McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“管理信息结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[SMIv2-TC] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[SMIv2 TC]McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[tipsi] IEEE 1284.1, Transport-independent Printer System Interface (TIPSI).
[tipsi]IEEE 1284.1，独立于传输的打印机系统接口（tipsi）。
[URI-spec] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI), Generic Syntax", RFC 2396, August 1998.
[URI规范]Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI），通用语法”，RFC 2396，1998年8月。
[US-ASCII] Coded Character Set - 7-bit American Standard Code for Information Interchange, ANSI X3.4-1986.
[US-ASCII]编码字符集-信息交换用7位美国标准代码，ANSI X3.4-1986。
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.
[UTF-8]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，RFC 2279，1998年1月。
8 Notices
8通知
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11 [BCP-11]. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11[BCP-11]。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
9 Authors' Addresses
9作者地址
Ron Bergman Dataproducts Corp. 1757 Tapo Canyon Road Simi Valley, CA 93063-3394
罗恩·伯格曼数据产品公司，加利福尼亚州西米谷塔波峡谷路1757号，邮编93063-3394
Phone: 805-578-4421 Fax: 805-578-4001 EMail: rbergma@dpc.com
电话：805-578-4421传真：805-578-4001电子邮件：rbergma@dpc.com
Tom Hastings Xerox Corporation, ESAE-231 737 Hawaii St. El Segundo, CA 90245
汤姆·黑斯廷斯施乐公司，ESAE-231 737夏威夷圣塞贡多，加利福尼亚州90245
Phone: 310-333-6413 Fax: 310-333-5514 EMail: hastings@cp10.es.xerox.com
电话：310-333-6413传真：310-333-5514电子邮件：hastings@cp10.es.xerox.com
Scott A. Isaacson Novell, Inc. 122 E 1700 S Provo, UT 84606
Scott A.Isaacson Novell，Inc.美国犹他州普罗沃南部122 E 1700，邮编84606
Phone: 801-861-7366 Fax: 801-861-4025 EMail: scott_isaacson@novell.com
电话：801-861-7366传真：801-861-4025电子邮件：scott_isaacson@novell.com
Harry Lewis IBM Corporation 6300 Diagonal Hwy Boulder, CO 80301
Harry Lewis IBM Corporation科罗拉多州博尔德市6300号对角公路80301
Phone: (303) 924-5337 EMail: harryl@us.ibm.com
电话：（303）924-5337电子邮件：harryl@us.ibm.com
Send questions and comments to the Printer Working Group (PWG) using the Job Monitoring Project (JMP) Mailing List: jmp@pwg.org
使用作业监控项目（JMP）邮件列表向打印机工作组（PWG）发送问题和意见：jmp@pwg.org
To learn how to subscribe, send email to: jmp-request@pwg.org
要了解如何订阅，请发送电子邮件至：jmp-request@pwg.org
Implementers of this specification are encouraged to join the jmp mailing list in order to participate in discussions on any clarifications needed and registration proposals for additional attributes and values being reviewed in order to achieve consensus.
鼓励本规范的实施者加入jmp邮件列表，以便参与讨论所需的任何澄清以及正在审查的其他属性和值的注册建议，以达成共识。
For further information, access the PWG web page under "JMP":
有关更多信息，请访问“JMP”下的PWG网页：
http://www.pwg.org/
http://www.pwg.org/
Other Participants:
其他与会者：
Chuck Adams - Tektronix Jeff Barnett - IBM Keith Carter, IBM Corporation Jeff Copeland - QMS Andy Davidson - Tektronix Roger deBry - IBM Mabry Dozier - QMS Lee Farrell - Canon Steve Gebert - IBM Robert Herriot - Sun Microsystems Inc. Shige Kanemitsu - Kyocera David Kellerman - Northlake Software Rick Landau - Digital Pete Loya - HP Ray Lutz - Cognisys Jay Martin - Underscore Mike MacKay, Novell, Inc. Stan McConnell - Xerox Carl-Uno Manros, Xerox, Corp. Pat Nogay - IBM Bob Pentecost - HP Rob Rhoads - Intel David Roach - Unisys Stuart Rowley - Kyocera Hiroyuki Sato - Canon Bob Setterbo - Adobe Gail Songer, EFI Mike Timperman - Lexmark Randy Turner - Sharp William Wagner - Digital Products Jim Walker - Dazel Chris Wellens - Interworking Labs Rob Whittle - Novell Don Wright - Lexmark Lloyd Young - Lexmark Atsushi Yuki - Kyocera Peter Zehler, Xerox, Corp.
Chuck Adams-Tektronix Jeff Barnett-IBM Keith Carter，IBM公司Jeff Copeland-QMS Andy Davidson-Tektronix Roger deBry-IBM Mabry Dozier-QMS Lee Farrell-Canon Steve Gebert-IBM Robert Herriot-Sun Microsystems Inc.Shige Kanemitsu-Kyocera David Kellerman-Northlake Software Rick Landau-Digital Pete Loya-HP Ray Lutz-Cognisys Jay Martin-Mike MacKay，Novell，斯坦·麦康奈尔公司-施乐卡尔·乌诺·曼罗斯公司，施乐公司，帕特·诺盖公司-IBM Bob Pentecost公司-惠普公司Rob Rhoads公司-英特尔公司大卫·罗奇公司-Unisys Stuart Rowley公司-京瓷公司佐藤广幸公司-佳能公司Bob Setterbo公司-Adobe Gail Songer公司，EFI Mike Timperman-Lexmark Randy Turner-Sharp William Wagner-数字产品Jim Walker-Dazel Chris Wellens-互通实验室Rob Whittle-Novell Don Wright-Lexmark Lloyd Young-Lexmark Atsushi Yuki-京瓷彼得·泽勒，施乐公司。
10 INDEX
10指数
This index includes the textual conventions, the objects, and the attributes. Textual conventions all start with the prefix: "JM" and end with the suffix: "TC". Objects all starts with the prefix: "jm" followed by the group name. Attributes are identified with enums, and so start with any lower case letter and have no special prefix.
该索引包括文本约定、对象和属性。文本约定都以前缀“JM”开头，以后缀“TC”结尾。对象都以前缀“jm”开头，后跟组名。属性由枚举标识，因此以任何小写字母开头，并且没有特殊前缀。
colorantConsumed, 40 colorantRequested, 40 deviceNameRequested, 30 documentCopiesCompleted, 35 documentCopiesRequested, 35 documentFormat, 31 documentFormatIndex, 31 documentName, 31 fileName, 31 finishing, 33 fullColorImpressionsCompleted, 37 highlightColorImpressionsCompleted, 37 impressionsCompletedCurrentCopy, 37 impressionsInterpreted, 37 impressionsSentToDevice, 37 impressionsSpooled, 36 jmAttributeInstanceIndex, 99 jmAttributeTypeIndex, 98 JmAttributeTypeTC, 78 jmAttributeValueAsInteger, 99 jmAttributeValueAsOctets, 100 JmBooleanTC, 72 JmFinishingTC, 70 jmGeneralAttributePersistence, 87 jmGeneralJobPersistence, 87 jmGeneralJobSetIndex, 85 jmGeneralJobSetName, 88 jmGeneralNewestActiveJobIndex, 86 jmGeneralNumberOfActiveJobs, 86 jmGeneralOldestActiveJobIndex, 86 JmJobCollationTypeTC, 74 jmJobIDJobIndex, 91 jmJobIDJobSetIndex, 90 jmJobImpressionsCompleted, 96 jmJobImpressionsPerCopyRequested, 95 jmJobIndex, 92 jmJobKOctetsPerCopyRequested, 94 jmJobKOctetsProcessed, 94 jmJobOwner, 96
已消耗的颜色、已请求的40种颜色、已请求的40种设备名称、已完成的30份文档副本、已请求的35份文档副本、35份文档格式、31份文档格式索引、31份文档名、31份文件名、31份整理、已完成的33份完整颜色印鉴、已完成的37份高亮颜色印鉴、已完成的37份印鉴当前副本、已解释的37份印鉴、，37个ImpressionSenttoDevice，37个ImpressionSpooled，36个jmAttributeInstanceIndex，99个jmAttributeTypeIndex，98个JmAttributeTypeTC，78个jmAttributeValueAsInteger，99个JMAttributeValueAsActets，100个JmBooleanTC，72个JmFinishingTC，70个jmGeneralAttributePersistence，87个jmGeneralJobPersistence，87个jmGeneralJobSetIndex，85个jmGeneralJobSetName，88个JMGeneralNewEstativeJobIndex，86个jmGeneralNumberOfActiveJobs，86个JMGeneralLoldStativeJobIndex，86个JmJobCollationTypeTC，74个jmJobIDJobIndex，91个jmJobIDJobSetIndex，90个JMJobImpressionsComprequested，96个jmJobIndex，92个JMJobKoctetsOpyRequested，94个jmJobOwner，96个
JmJobServiceTypesTC, 81 JmJobSourcePlatformTypeTC, 69 jmJobState, 92 jmJobStateReasons1, 93 JmJobStateReasons1TC, 83 JmJobStateReasons2TC, 83 JmJobStateReasons3TC, 83 JmJobStateReasons4TC, 84 JmJobStateTC, 75 JmJobStringTC, 68 jmJobSubmissionID, 89 JmJobSubmissionIDTypeTC, 74 JmMediumTypeTC, 72 JmNaturalLanguageTagTC, 68 jmNumberOfInterveningJobs, 93 JmPrinterResolutionTC, 71 JmPrintQualityTC, 71 JmTimeStampTC, 69 JmTonerEconomyTC, 72 JmUTF8StringTC, 68 jobAccountName, 27 jobCodedCharSet, 26 jobCollationType, 36 jobComment, 31 jobCompletionTime, 43 jobCopiesCompleted, 35 jobCopiesRequested, 35 jobHold, 33 jobHoldUntil, 33 jobKOctetsTransferred, 35 jobName, 28 jobNaturalLanguageTag, 27 jobOriginatingHost, 30 jobPriority, 32 jobProcessAfterDateAndTime, 32 jobProcessingCPUTime, 43 jobServiceTypes, 29 jobSourceChannelIndex, 29 jobSourcePlatformType, 29 jobStartedBeingHeldTime, 42 jobStartedProcessingTime, 43 jobStateReasons2, 25 jobStateReasons3, 25 jobStateReasons4, 25 jobSubmissionTime, 42 jobSubmissionToServerTime, 42 jobURI, 27 mediumConsumed, 40
JmJobServiceTypesTC，81 JmJobSourcePlatformTypeTC，69 jmJobState，92 JmJobStateReasons1TC，93 JmJobStateReasons1TC，83 JmJobStateReasons2TC，83 JmJobStateReasons4TC，84 JmJobStateTC，75 JmJobStringTC，68 JMJobSubmitionId，89 JMJobSubmitionIDtypeTC，74 JmMediumTypeTC，72 JMNaturalGuageAgTC，68个干预性工作，93 JMPrinterResolutionC、71 JmPrintQualityTC、71 JmTimeStampTC、69 JmTonerEconomyTC、72 JmUTF8StringTC、68 jobAccountName、27 jobCodedCharSet、26 jobCollationType、36 jobComment、31 jobCompletionTime、43 jobCopiesCompleted、35 jobCopiesRequested、35 JobHolding、33 JobKocteTransferred、35 jobName、28 jobNaturalLanguageTag、，27个jobOriginatingHost，30个jobPriority，32个jobProcessAfterDateAndTime，32个jobProcessingCPUTime，43个JobServiceType，29个jobSourceChannelIndex，29个jobSourcePlatformType，29个jobStartedBeingHeldTime，42个jobStartedProcessingTime，43个jobStateReasons2，25个jobStateReasons3，25个jobStateReasons4，25个jobSubmissionTime，42个jobURI，27中等消费，40
mediumRequested, 39 mediumSizeConsumed, 41 mediumTypeConsumed, 41 numberOfDocuments, 30 other, 25 outputBin, 33 pagesCompleted, 38 pagesCompletedCurrentCopy, 38 pagesRequested, 38 physicalDevice, 30 printerResolutionRequested, 34 printerResolutionUsed, 34 printQualityRequested, 34 printQualityUsed, 34 processingMessage, 25 processingMessageNaturalLangTag, 26 queueNameRequested, 30 serverAssignedJobName, 28 sheetCompletedCopyNumber, 36 sheetCompletedDocumentNumber, 36 sheetsCompleted, 39 sheetsCompletedCurrentCopy, 39 sheetsRequested, 39 sides, 33 submittingApplicationName, 29 submittingServerName, 29 tonerDensityRequested, 34 tonerDensityUsed, 34 tonerEcomonyRequested, 34 tonerEcomonyUsed, 34
请求的介质、消耗的介质大小39个、消耗的介质类型41个、文档数量41个、其他30个、输出BIN 25个、完成的33页、完成的38页当前副本、请求的38页、38个物理设备、请求的30个打印机解决方案、使用的34个打印机解决方案、请求的34个打印质量、使用的34个打印质量、处理的消息、，25 Processing Message NaturAllangtag，26 QueueName Requested，30 ServerAssigned JobName，28 SheetCompleted CopyNumber，36 SheetCompleted DocumentNumber，36 Sheets Completed，39 Sheets Completed CurrentCopy，39 Sheets Requested，39个侧面，33 Submitting Application Name，29 Submitting ServerName，29 Toner DensityRequested，34 Toner DensityUsed，要求的34色调，使用的34色调，使用的34色调
11 Full Copyright Statement
11完整版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。