rfc2708.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.


RFC 2708            Job Submission Protocol Mapping        November 1999


 Notes:
 ------
   1. Every DPA attribute is tagged indicating the coded character set
      to be used for that attribute.
   2. jobStateReasonsN are three attributes (N=2, 3, 4).  The DPA
      condition may change one or more of the bits in one or more of
      these Job MIB items.  Also the DPA job-state-reasons is a multi-
      valued attribute with each value being an OBJECT IDENTIFIER (OID).
   3. The Job MIB sides attribute is an integer '1' or '2' while the DPA
      sides attribute has one of six OID values that includes plex.
   4. printerResolutionRequested has x and y resolution and is intended
      to override the resolution instruction in the document, if any,
      while the DPA default-printer-resolution is the same in x and y
      and only takes effect if the document does not contain a
      resolution instruction
   5. The DPA "copy-count" attribute is a per-document attribute, so the
      MIB value is the sum of the documents' "copy-count" values times
      the job's "results-profile.job-copies" value.
   6. The DPA "copies-completed" attribute is a per-document attribute,
      so the MIB value is the sum of the documents' "copies-completed"
      values times the job's "results-profile.job-copies" value.
   7. The DPA GeneratlizedTime data type is defined by ISO 8824 (ISO-
      8824) while the MIB DateAndTime is defined by SNMPv2-TC (SNMPv2-
      TC).

7.0  NOVELL DISTRIBUTED PRINT SERVICE (NDPS)

   Novell Distributed Print Services is a DPA based job submission
   protocol that conforms to configuration 3.

7.1  jmJobSubmissionID Mapped to NDPS

   NDPS supports the generation of a properly formatted
   jmJobSubmissionID for use in the Job MIB, via the attribute ndps-
   att-job-identifier.

7.2  jmJobIndex Mapped to NDPS

   NDPS defines the attribute ndps-att-job-identifier-on-printer that
   can be used to return the value of jmJobIndex to the NDPS client. See
   Section 1.0.










Bergman                      Informational                     [Page 14]

RFC 2708            Job Submission Protocol Mapping        November 1999


7.3  Other MIB Objects Mapped to NDPS

MIB Object                       | NDPS Parameter
---------------------------------+--------------------------------------
jmJobState                       | ndps-att-current-job-state (note 1)
jmJobStateReasons1               | ndps-att-job-state-reasons (note 2)
jmNumberOfInterveningJobs        | ndps-att-intervening-jobs
jmJobKOctetsPerCopyRequested     | ndps-att-total-job-octets (notes 3,4)
jmJobKOctetsProcessed            | ndps-att-octets-completed (note 3)
jmJobImpressionsPerCopyRequested | ndps-att-job-impressions-count
jmJobImpressionsCompleted        | ndps-att-impressions-completed
jmJobOwner                       | ndps-att-job-owner (note 5)

   Notes:
   ------
   1. Some of the NDPS job states must be represented by both a
      jmJobState and a jmJobStateReasons1 object or a jobStateReasonsN
      attribute (N=2, 3, 4).
   2. The NDPS job state reasons may be mapped to either the object
      jmJobStateReasons1 or the attribute jobStateReasonsN (N=2, 3, 4).
   3. jmJobKOctetsPerCopyRequested and jmJobKOctetsProcessed is in K
      octets while the NDPS ndps-att-job-total-octets and ndps-att-job-
      octets-completed is in octets and is 63-bits of significance.
   4. NDPS octets include the multiplication factor due to job and
      document copies, while the MIB values do not.
   5. The Job MIB object must be multiplied by the attribute
      jobCopiesRequested to obtain the NDPS attribute value, if multiple
      copies have been requested.

7.4  The Attribute Group Mapped to NDPS

   The following mappings are required if the listed PJL attribute or
   command option is provided.


















Bergman                      Informational                     [Page 15]

RFC 2708            Job Submission Protocol Mapping        November 1999


MIB attribute              | NDPS parameter               | Data type
---------------------------+------------------------------+-------------
jobStateReasonsN(N=2, 3, 4)| ndps-job-state-reasons       | Integer
jobAccountName             | ndps-att-job-owner           | Octet String
jobName                    | ndps-att-job-name            | Octet String
jobOriginatingHost         | ndps-att-job-originator      | Octet String
deviceNameRequested        | ndps-att-printer-name--      | Octet String
                           |  requested                   |
numberOfDocuments          | ndps-att-number-of-documents | Integer
fileName                   | ndps-att-document-file-name  | Octet String
documentName               | ndps-att-document-name       | Octet String
jobComment                 | ndps-att-job-comment         | Octet String
documentFormatIndex        | ndps-att-prtInterpreterIndex | Integer
documentFormat             | ndps-att-document-format     | Integer
jobPriority                | ndps-att-job-priority        | Integer
jobProcessAfterDateAndTime | ndps-att-job-print-after     | Octet String
outputBin                  | ndps-att-results-profile     | Integer
                           |  (note 1)                    |
sides                      | ndps-att-sides (note 2)      | Integer
finishing                  | ndps-att-job-finishing       | Integer
printQualityRequested      | ndps-att-print-quality       | Integer
printerResolutionRequested | ndps-att-default-printer--   |
                           |  resolution (note 3)         | Integer
printerResolutionUsed      | ndps-att-default-resolutions--
                           |  used                        | Integer
jobCopiesRequested         | ndps-att-results-profile     | Integer
                           |  (note 4)                    |
jobCopiesCompleted         | ndps-att-job-copies-completed| Integer
documentCopiesRequested    | ndps-att-copy-count (note 5) | Integer
documentCopiesCompleted    | ndps-att-copies-completed    | Integer
                           |  (note 6)                    |
sheetsRequested            | ndps-att-job-media--         |
                           |  sheet-count                 | Integer
sheetsCompleted            | ndps-att-media-sheets--      |
                           |  completed                   | Integer
mediumConsumed             | ndps-att-media-used          | Integer
jobSubmissionToServerTime  | ndps-att-submission-time     | Octet String
                           |  (note 7)                    |
jobSubmissionTime          | ndps-att-started-printing-time Octet String
                           |  (note 7)                    |
jobCompletionTime          | ndps-att-completion-time     | Octet String
                           |  (note 7)                    |
   Notes:
   ------
   1. The output-bin field in ndps-att-results-profile is to be used.
   2. The Job MIB sides attribute is an integer '1' or '2' while the
      NDPS sides attribute has one of six OID values that includes plex.




Bergman                      Informational                     [Page 16]

RFC 2708            Job Submission Protocol Mapping        November 1999


   3. printerResolutionRequested has x and y resolution and is intended
      to override the resolution instruction in the document, if any,
      while the ndps-att-default-printer-resolution is the same in x and
      y and only takes effect if the document does not contain a
      resolution instruction
   4. The job-copies field in ndps-att-results-profile is to be used.
   5. The NDPS "copy-count" attribute is a per-document attribute, so
      the MIB value is the sum of the documents' "copy-count" values
      times the job's "results-profile.job-copies" value.
   6. The NDPS "copies-completed" attribute is a per-document attribute,
      so the MIB value is the sum of the documents' "copies-completed"
      values times the job's "results-profile.job-copies" value.
   7. The NDPS GeneratlizedTime data type is defined by ISO 8824 (ISO-
      8824) while the MIB DateAndTime is defined by SNMPv2-TC (SNMPv2-
      TC).

8.0  PRINTER JOB LANGUAGE (PJL)

   PJL [PJL] has been developed by Hewlett-Packard to provide job
   control information to the printer and status information to
   applications, independent of the PDL.

8.1  jmJobSubmissionID Mapped to PJL

   PJL has defined the SUBMISSIONID option for the JOB command which
   indicates a properly formatted jmJobSubmissionID for use in the Job
   MIB.  The PJL JOB command is presented at the start of a print job
   with options that apply only the attached job.  The syntax for this
   command option is:

      @PJL JOB SUBMISSIONID = "id string"

   Driver software that implements this PJL command option must provide
   the "id string" in one of the client version formats specified in the
   Job MIB for jmJobSubmissionID.

   For drivers that are not able to create the SUBMISSIONID option, it
   is recommended that jmJobSubmissionID format 0 be created by the
   agent using the PJL attribute DocOwner or DocOwnerId.

   octet 1:   '0'

   octets 2-40:  Contains the string associated with DocOwner or
                 DocOwnerId.  If the string is less than 40 octets, the
                 left-most character in the string shall appear in octet






Bergman                      Informational                     [Page 17]

RFC 2708            Job Submission Protocol Mapping        November 1999


                 position 2.  Otherwise, only the last 39 bytes shall be
                 included.  Any unused portion of this field shall be
                 filled with spaces.  If DocOwner or DocOwnerId cannot
                 be obtained, this field shall be blank.


   octets 41-48:  Contains the value of jmJobIndex associated with the
                  job.  Leading zeros shall be inserted to fill the
                  entire 8 octet field.

8.2  jmJobIndex Mapped to PJL

   PJL does not provide a value that can be mapped to jmJobIndex.

8.3  Other MIB Objects Mapped to PJL

   MIB Object            | PJL Job attribute
   ----------------------+------------------------------------
   jobOwner              | DocOwner or DocOwnerId attribute

8.4  The Attribute Group Mapped to PJL

   The following mappings are required if the listed PJL attribute or
   command option is provided.

MIB attribute         | PJL attribute or command option  | Data type
----------------------+----------------------------------+--------------
serverAssignedJobName | DocName attribute or the command | Octet String
                      |  @PJL JOB Name = "string"        | Octet String
submittingServerName  | SrcServerName attribute          | Octet String
jobOriginatingHost    | SrcPort attribute                | Octet String
queueNameRequested    | SrcQ attribute                   | Octet String
fileName              | JobFName attribute               | Octet String
jobComment            | JobDesc attribute                | Octet String
jobSubmissionTime     | TimeSubmit attribute             | Octet String

9.0  POSTSCRIPT

   The PostScript PDL permits comment fields which can be used by
   application drivers to include job information.  Although there are
   no restrictions or requirements as to what information may be
   included, many drivers include job owner and/or document name.









Bergman                      Informational                     [Page 18]

RFC 2708            Job Submission Protocol Mapping        November 1999


9.1  jmJobSubmissionID Mapped to PostScript

   The use of a standard format job submission id comment string will
   allow interoperability of printers and drivers from multiple vendors.
   The following comment string format is recommended for use with
   PostScript level 1 and level 2 data streams.

      %%JMPJobSubmissionId:(id-string)

   where "id string" can be any jmJobSubmissionID format reserved for
   clients.

9.2  Other MIB Objects and Attributes Mapped to PostScript

   No Other mappings from PostScript comment strings are recommended,
   but many Job MIB objects and attributes can be defined using vendor
   unique comment strings.

10.0  NETWARE PSERVER

   The NetWare PServer job submission protocol is implemented in a
   client- server-printer system on the server to printer link as
   defined in configuration 3.

10.1  jmJobSubmissionID Mapped to PServer

   octet 1:   'B'

   octets 2-40:  Contains the Directory Path Name of the agent 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 decimal (ASCII coded) representation
                  of the Job Number as per the NetWare File Server Queue
                  Management Services.

10.2  jmJobIndex Mapped to PServer

   The job index (jmJobIndex) is assigned by the SNMP job monitoring
   agent and is independent of the Job Number assigned by the NetWare
   File Server Queue Management Services.  This will allow the SNMP
   agent to track jobs received from multiple sources.





Bergman                      Informational                     [Page 19]

RFC 2708            Job Submission Protocol Mapping        November 1999


10.3  Other MIB Objects Mapped to PJL

   MIB Object            | PServer Job attribute
   ----------------------+--------------------------------------------
   jobOwner              | Client Id Number

10.4  The Attribute Group Mapped to PServer

   The following mappings are required if the listed PServer parameter
   is provided in the Novell File Server queue directory.

MIB attribute              | PServer parameter           | Data type
---------------------------+-----------------------------+--------------
serverAssignedJobName      | Job File Name               | Octet String
queueNameRequested         | Queue Id                    | Integer
physicalDevice             | Server Id Number            | Integer
jobComment                 | Job Description             | Octet String
jobPriority                | (note 1)                    | Integer
jobProcessAfterDateAndTime | Target Execution Time       | Octet String
jobCopiesRequested         | Number of Copies            | Integer
mediumRequested            | Form Name                   | Octet String
jobSubmissionToServerTime  | Job Entry Time              | Octet String

   Notes:
   ------