tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

RFC 2707

 
 
 

Job Monitoring MIB - V1.0

Part 5 of 5, p. 92 to 114
Prev RFC Part

 


prevText      Top      Up      ToC       Page 92 
jmJobEntry  OBJECT-TYPE
    SYNTAX      JmJobEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Basic per-job state and status information.

        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 }

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.

        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 }

Top      Up      ToC       Page 93 
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.

        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.

        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.

        The jobStateReasonsN (N=2..4) attributes provide further
        additional information about the job's current state."
    DEFVAL      { 0 }      -- no reasons
    ::= { jmJobEntry 3 }

Top      Up      ToC       Page 94 
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.

        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

Top      Up      ToC       Page 95 
        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.

        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.

        NOTE - See the impressionsCompletedCurrentCopy and
        pagesCompletedCurrentCopy attributes for attributes that are
        reset on each document copy.

        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.

        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.

        See the definition of the term 'impression' in Section 2."

Top      Up      ToC       Page 96 
    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.

        NOTE - See the impressionsCompletedCurrentCopy and
        pagesCompletedCurrentCopy attributes for attributes that are
        reset on each document copy.

        NOTE - The jmJobImpressionsCompleted object can be used with
        the 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.

        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.

        This value SHOULD be the most authenticated name of the user
        submitting the job.

        See the OBJECT compliance macro for the minimum maximum length

Top      Up      ToC       Page 97 
        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.

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.

        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.

        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

Top      Up      ToC       Page 98 
        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.

        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.

        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.

        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 }

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.

        The type MAY identify information about the job or document(s)

Top      Up      ToC       Page 99 
        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).

        Examples of document attributes (one instance per document)
        include: fileName(34), and documentName(35).

        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 }



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

Top      Up      ToC       Page 100 
        description in the JmAttributeTypeTC textual-convention
        definition has the tag: '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.

        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.

        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.

        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.

        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

Top      Up      ToC       Page 101 
    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:'.

        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'.

        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.

        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

jobmonMIBNotifications  OBJECT IDENTIFIER  ::= { jobmonMIB 2 }



-- Conformance Information

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 }

Top      Up      ToC       Page 102 
    OBJECT   jmGeneralJobSetName
    SYNTAX   JmUTF8StringTC (SIZE(0..8))
    DESCRIPTION
        "Only 8 octets maximum string length NEED be supported by the
        agent."

    OBJECT   jmJobOwner
    SYNTAX   JmJobStringTC (SIZE(0..16))
    DESCRIPTION
        "Only 16 octets maximum string length NEED be supported by the
        agent."

-- There are no CONDITIONALLY MANDATORY or OPTIONAL groups.

    ::= { jmMIBConformance 1 }


jmMIBGroups      OBJECT IDENTIFIER ::= { jmMIBConformance 2 }

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 }



jmJobGroup OBJECT-GROUP
    OBJECTS {
        jmJobState, jmJobStateReasons1, jmNumberOfInterveningJobs,
        jmJobKOctetsPerCopyRequested, jmJobKOctetsProcessed,
        jmJobImpressionsPerCopyRequested, jmJobImpressionsCompleted,
        jmJobOwner }
    STATUS  current

Top      Up      ToC       Page 103 
    DESCRIPTION
        "The job group."
    ::= { jmMIBGroups 3 }



jmAttributeGroup OBJECT-GROUP
    OBJECTS {
        jmAttributeValueAsInteger, jmAttributeValueAsOctets }
    STATUS  current
    DESCRIPTION
        "The attribute group."
    ::= { jmMIBGroups 4 }


END

Top      Up      ToC       Page 104 
5  Appendix A - Implementing the Job Life Cycle

   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.

   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.

   The jmJobState object specifies the standard job states.  The normal
   job state transitions are shown in the state transition diagram
   presented in Figure 4.

Top      Up      ToC       Page 105 
6  APPENDIX B - Support of Job Submission Protocols

   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.

   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.

   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.

7  References

   [BCP-11]           Bradner S. and R. Hovey, "The Organizations
                      Involved in the IETF Standards Process", BCP 11,
                      RFC 2028, October 1996.

   [GB2312]           GB 2312-1980, "Chinese People's Republic of China
                      (PRC) mixed one byte and two byte coded character
                      set"

   [hr-mib]           Grillo, P. and S. Waldbusser, "Host Resources
                      MIB", RFC 1514, September 1993.

   [iana]             Reynolds, J. and J. Postel, "Assigned Numbers",
                      STD 2, RFC 1700, October 1994.

   [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/

Top      Up      ToC       Page 106 
   [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.

   [ISO-639]          ISO 639:1988 (E/F) - Code for Representation of
                      names of languages - The International
                      Organization for Standardization, 1st edition,
                      1988.

   [ISO-646]          ISO/IEC 646:1991, "Information technology -- ISO
                      7-bit coded character set for information
                      interchange", JTC1/SC2.

   [ISO-2022]         ISO/IEC 2022:1994 - "Information technology --
                      Character code  structure and extension
                      techniques", 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-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-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."

   [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.

Top      Up      ToC       Page 107 
   [print-mib]        Smith, R., Wright, F., Hastings, T., Zilles, S.
                      and J. Gyllenskog, "Printer MIB", RFC 1759, March
                      1995.

   [print-mib-draft]  Turner, R., "Printer MIB", Work in Progress,

   [protomap]         Bergman, R., "Job Submission Protocol Mapping
                      Recommendations for the Job Monitoring MIB", RFC
                      2708, November 1999.

   [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

   [RFC1179]          McLaughlin, L., III, "Line Printer Daemon
                      Protocol", RFC 1179, August 1990.

   [RFC1738]          Berners-Lee, T., Masinter, L. and M., McCahill,
                      "Uniform Resource Locators (URL)", RFC 1738,
                      December 1994.

   [RFC1766]          Avelstrand, H., "Tags for the Identification of
                      Languages", RFC 1766, March 1995.

   [RFC2026]          Bradner, S., "The Internet Standards Process --
                      Revision 3", BCP 9, RFC 2026, October 1996.

   [RFC2119]          Bradner, S., "Keywords for use in RFCs to Indicate
                      Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2277]          Alvestrand, H., "IETF Policy on Character Sets and
                      Languages", BCP 18, RFC 2277, January 1998.

   [RFC2278]          Freed, N. and  J. Postel, "IANA CharSet
                      Registration Procedures", BCP 19, RFC 2278,
                      January 1998.

   [SMIv2-SMI]        McCloghrie, K., Perkins, D. and J. Schoenwaelder,
                      "Structure of Management Information Version 2
                      (SMIv2)", STD 58, RFC 2578, April 1999.

   [SMIv2-TC]         McCloghrie, K., Perkins, D. and J. Schoenwaelder,
                      "Textual Conventions for SMIv2", STD 58, RFC 2579,
                      April 1999.

Top      Up      ToC       Page 108 
   [tipsi]            IEEE 1284.1, Transport-independent Printer System
                      Interface (TIPSI).

   [URI-spec]         Berners-Lee, T., Fielding, R. and  L. Masinter,
                      "Uniform Resource Identifiers (URI), Generic
                      Syntax", RFC 2396, August 1998.

   [US-ASCII]         Coded Character Set - 7-bit American Standard Code
                      for Information Interchange, ANSI X3.4-1986.

   [UTF-8]            Yergeau, F., "UTF-8, a transformation format of
                      ISO 10646", RFC 2279, January 1998.

8  Notices

   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.

   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.

Top      Up      ToC       Page 109 
9  Authors' Addresses

   Ron Bergman
   Dataproducts Corp.
   1757 Tapo Canyon Road
   Simi Valley, CA 93063-3394

   Phone: 805-578-4421
   Fax:  805-578-4001
   EMail: rbergma@dpc.com


   Tom Hastings
   Xerox Corporation, ESAE-231
   737 Hawaii St.
   El Segundo, CA   90245

   Phone: 310-333-6413
   Fax:   310-333-5514
   EMail: hastings@cp10.es.xerox.com


   Scott A. Isaacson
   Novell, Inc.
   122 E 1700 S
   Provo, UT   84606

   Phone: 801-861-7366
   Fax:   801-861-4025
   EMail: scott_isaacson@novell.com


   Harry Lewis
   IBM Corporation
   6300 Diagonal Hwy
   Boulder, CO 80301

   Phone: (303) 924-5337
   EMail: 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

   To learn how to subscribe, send email to:  jmp-request@pwg.org

Top      Up      ToC       Page 110 
   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.

   For further information, access the PWG web page under "JMP":

       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.

Top      Up      ToC       Page 111 
10 INDEX

   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.

   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

Top      Up      ToC       Page 112 
   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

Top      Up      ToC       Page 113 
   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

Top      Up      ToC       Page 114 
11  Full Copyright Statement

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   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.