NDPS Object Classes
NDPS object classes fall into one of three categories:
Implemented Object Classes
For the following lists of object classes, there is at least one Novell component that implements an instance of the class:
ndps-oc-generic |
ndps-oc.0;"Generic" |
ndps-oc-job |
ndps-oc.1;"Job" |
ndps-oc-document |
ndps-oc.2;"Document" |
ndps-oc-printer |
ndps-oc.3;"Printer" |
ndps-oc-medium |
ndps-oc.4;"Medium" |
ndps-oc-scheduler |
ndps-oc.12;"Scheduler" |
The implemented NDPS objects that are based on printer MIBs follow:
ndps-oc-input |
ndps-oc.15;"Input" |
ndps-oc-output |
ndps-oc.16;"Output" |
ndps-oc-marker |
ndps-oc.25;"Marker" |
ndps-oc-media-path |
ndps-oc.26;"Media Path" |
ndps-oc-interpreter |
ndps-oc.28;"Interpreter" |
ndps-oc-markerSupplies |
ndps-oc.30;"MarkerSupplies" |
ndps-oc-markerColorant |
ndps-oc.31;"MarkerColorant" |
ndps-oc-cover |
ndps-oc.32;"Cover" |
ndps-oc-light |
ndps-oc.33;"Light" |
ndps-oc-buffer |
ndps-oc.34;"Buffer" |
ndps-oc-finisher-device |
ndps-oc37;"Finisher Device" |
ndps-oc-finisher-supply |
ndps-oc38;"Finisher Supply" |
The implemented NDPS objects that are not based on DPA or printer MIBs follow:
ndps-oc-manager |
ndps-oc.18;"Manager" |
ndps-oc-job-defaults |
ndps-oc.19;"Job Defaults" |
ndps-oc-doc-defaults |
ndps-oc.20;"Document Defaults" |
ndps-oc-job-limits |
ndps-oc.21;"Job Limits" |
ndps-oc-doc-limits |
ndps-oc.22;"Document Limits" |
ndps-oc-abstract-event |
ndps-oc.23;"Abstract Event" |
ndps-oc-retained-job |
ndps-oc.24;"Retained Job" Retained-job is not a real class. It is used only as a mechanism for managing jobs in the retained-job state. |
ndps-oc-accounting |
ndps-oc.36;"Accounting" |
ndps-oc-finisher-device |
ndps_oc.37;"Finisher Device" |
ndps-oc-finisher-supply |
ndps-oc.38;"Finisher Supply" |
ndps-oc-printer-pool |
ndps-oc.39;"Printer Pool" |
NDPS Object Classes Supported But Not Implemented
For the following lists of object classes, there is no Novell component that implements an instance of the class. Other add-on components can create objects of these classes which are supported in the protocol and in the MOD, but there is no default user interface (client or server) for accessing the data in the MOD. However, attribute values for the transfer method and notification method classes are implemented.
ndps-oc-font |
ndps-oc.5;"Font" |
ndps-oc-transfer-method |
ndps-oc.6;"Transfer Method" |
ndps-oc-delivery-method |
ndps-oc.7;"Delivery Method" |
ndps-oc-auxiliary-sheet |
ndps-oc.8;"Auxiliary Sheet" |
ndps-oc-imposition |
ndps-oc.11;"Imposition" |
ndps-oc-resource |
ndps-oc.14;"Resource" |
ndps-oc-auxiliary-sheet-package |
ndps-oc.17;"Aux. Sheet Package" |
ndps-oc-notification-method |
ndps-oc.29;"Notification Method" |
DPA Object Classes Not Supported
The following lists of object classes are not supported due to implementation differences among NDPS, DPA, and the Printer MIB.
output-method |
NDPS implements the Printer MIB output class rather than the DPA output-method class. |
initial-value-job |
NDPS implements job-defaults instead of the DPA initial-value-job class. |
initial-value-document |
NDPS implements doc-defaults instead of the DPA initial-value-document class. |
resource-context |
|
ndps-oc-finishing |
ndps-oc.9;"Finishing" |
The following table shows the unsupported NDPS objects that are based on printer MIBs:
channel |
The Printer MIB channel object class represents multiple print server protocol stacks and interfaces for a network-attached printer with an embedded Printer MIB. In NDPS, the protocol that is used for client access to the printer is the NDPS protocol. The NDPS protocol is described by attributes of the printer object in the MOD, so the channel class is not needed. |