LJ9200C-MIB: View SNMP OID List / Download MIB
VENDOR: HEWLETT-PACKARD
Home | MIB: LJ9200C-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
hp | 1.3.6.1.4.1.11 | |||
netPMLmgmt | 1.3.6.1.4.1.11.2.3.9.4.2 | |||
device | 1.3.6.1.4.1.11.2.3.9.4.2.1 | |||
device-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1 | |||
settings-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1 | |||
energy-star | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.1 |
Returns or changes the Energy Star sleep value. If the value is greater than zero, then the device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. A value of zero means Energy Star is disabled and the device will not go to sleep based on print engine idle time. The value must be non-negative. Additional information: Returns or changes the Energy Star sleep value. The device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. LaserJet 4550 and LaserJet 4100 supports values of 0, 60, 900, 1800, 3600, 7200, 14400 seconds. A value of 0 means never enter sleep mode based on the print engine idle time. Setting to an unsupported value causes the printer to substitute a value (listed below) and to return <noError> status. Setting this value when the printer is in sleep mode will not cause it to wakeup unless it is set to 0. The values are as follow: <=0 snap to 0 >=1 and <= 479 snap to 60 (1 minute) >=480 and <= 1349 snap to 900 (15 minutes) >=1350 and <= 2699 snap to 1800 (30 minutes) >=2700 and <= 5399 snap to 3600 (1 hour) >=5400 and <= 10799 snap to 7200 (2 hours) >=10800 snap to 14400 (4 hours). |
||
sleep-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.2 |
Returns eTrue if the device is in energy saving sleep mode, otherwise returns eFalse. Setting SLEEP-MODE to eFalse causes the device to wake up, if it is in sleep mode. Setting SLEEP-MODE to eTrue causes the device to go into sleep mode. Additional information: This object returns eTrue if the device is in energy saving sleep mode, otherwise it returns eFalse. Setting this object to eTrue while the printer is awake will not change the printers current state and will return <genErr> status. NOTE: This object should behave this way when the printer does not have an instant-on fuser. Setting this object to eTrue while printer is already in Sleep Mode will not change the printers current state and will return <noError> status. Setting this object to eFalse while printer is already awake will not change the printers current state and will return <noError> status. Setting this object to eFalse while the printer is asleep causes the device to wake up. |
||
date-display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.22 |
Controls front-panel date display format. Additional information: Controls front-panel date display format. |
||
status-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2 | |||
on-off-line | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.5 |
To bring the PDL processing sub-system on or off line. If the device is a printer, then the printer does not process print job data when the printer is off line. PML communication persists. Additional information: When the printer is in the Offline state, printing will stop as soon as possible (no more sheets of media are pulled from input trays). The I/O is taken offline also. Setting to eOnline has the following affect: Printer will immediately go to or remain in the Online state; <noError> status is returned. If the printers current state is Offline with a pending error condition that prevents the printer from going to the Online state, the printer will remain in the Offline state; <genErr> status is returned Setting to eOffline has the following affect: Printer will immediately go to or remain in the Offline state; <noError> status is returned. If pages are being printed, those pages will complete with the printer in the Offline state. Setting to eOfflineAtEndOfJob has the following affect: If not in a job or already in the Offline state, the printer will immediately go to or remain in the Offline state; <noError> status is returned. If in a job and the current state is Online, the printer will remain in the Online state, with the value of this object as eOfflineAtEndOfJob, until the end of the job; <noError> status is returned. At the end of the job, the printer goes to the Offline state and the value of this object becomes eOffline. Setting this object to eOffline or eOnline before the end of the job causes the action for that value to be taken immediately. |
||
continue | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.6 |
A device can support a class of errors called continuable errors. When a continuable error is encountered, the device requires a continue event to occur before the device will continue operation. One continue event is setting the CONTINUE object to eInitiateAction. Devices can support other continue events, like auto-continue. A continue event causes the continuable error to be acknowledged, thus allowing the device to continue. Each device needs to list the continuable errors. If the device doesnt currently have an unacknowledged continuable error, the response will contain <genErr>. Additional information: See the CLEARABLE-WARNING and AUTO-CONTINUE objects for the errors that this object will clear. |
||
auto-continue | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.7 |
Indicates if the device will automatically continue after encountering a continuable error. If AUTO-CONTINUE is set to eOn, the device will automatically generate continue event to acknowledge continuable errors. If AUTO-CONTINUE is set to eOff, then some other continue event will have to acknowledge the continuable error. Additional information: If this is set to eOn the device displays an error message and goes offline for ten seconds. After ten seconds the printer automatically returns to the online state. If this is set to eOff then the device displays an error message and goes offline. It remains offline until the operator presses the GO key or until the CONTINUE object is set. If the printer is not idle, the new value may not take effect until a job boundary is reached. If a get is done on this object before the job boundary is reached, the value last set will be returned. |
||
install-date | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.8 |
Identifies the date that the device was installed. The format of the string is YYYYMMDDHHmmZ. Where: YYYY is the year. MM is the month (1-12). DD is the day (1-31). HH is the hour of the day (0-23). mm are the minutes (0-59). Z designates Greenwich Mean Time; if Z not specified, value is local time. Device POS must specify the conditions for setting this object. Additional information: Setting the <<hidden>> object will enable setting this object. |
||
perm-store-init-occurred | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.10 |
This object will set the cAllPermDevices bit when a full perm storage initialization occurs (as would be the case for a brand new system or as a result of a powerup key sequence or PE-TEST-POWERUP-KEY-SEQUENCE object request). If only one device was initialized (as would be the case if a disk were added to an existing system or a formatter were swapped out), then only the appropriate collection bits will be returned. If there are no collection bits set then this indicates that no initialization took place. |
||
date-and-time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.17 |
A C structure containing the following fields: typedef struct { ubyte yr; /* year: 0 to 99 */ ubyte mon; /* month: 1 to 12 */ ubyte day; /* day: 1 to 31 */ ubyte wday; /* Day of week: 1 to 07 */ ubyte hr; /* hour: 0 to 23 */ ubyte min; /* minute: 0 to 59 */ ubyte sec; /* second: 0 to 59 */ } date_t; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte yr; /* year: 3 to 99 */ ubyte mon; /* month: 1 to 12 */ ubyte day; /* day: 1 to 31 */ ubyte wday; /* Day of week: 1 to 07 */ ubyte hr; /* hour: 0 to 23 */ ubyte min; /* minute: 0 to 59 */ ubyte sec; /* second: 0 to 59 */ } date_t; where ubyte is an unsigned byte (0-255). |
||
service-id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.19 |
A read of this object will return the current SERVICE ID value in the printer. The format is YYDDD where: YY = calendar year - 1990 DDD = (calendar month - 1) * 30 + (calendar day of the month or 30, if > 30) A write of this object will only succeed if the MANUFACTURING-CONTROL PML object has been set with the correct <<hidden>>. If the write operation is not allowed, this object will return an <genErr> status. Additional information: Setting the <<hidden>> object will enable setting this object. |
||
display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20 | |||
display-status | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20.1 | |||
show-address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20.1.3 |
If this object is set to eAuto, and the device has an IP address, the IP address of the device will be shown with the READY message. If this object is set to eOff, the IP address will not be shown. |
||
time-display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.28 |
Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display. Additional information: Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display. |
||
background-message | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37 | |||
background-message1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.1 | |||
background-status-msg-line1-part1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.1.1 |
The string displayed on the devices front panel in place of the printers built-in background status string. An example built-in background status string is 00 READY. Additional information: The display size for the LaserJet 8150 printers is 2 X 16. The value of this object and the current value of BACKGROUND-STATUS-MSG-LINE2-PART1 are displayed together on the 2-line display, but they must be set independently. If line 2 has been set, and the next message to be displayed only requires line 1, BACKGROUND-STATUS-MSG-LINE2-PART1 must be set to the null string to clear it. This object allows a message to be displayed when it is the highest priority message. Setting this object does not guarantee the message will be displayed; and reading it returns the value last written, not the currently displayed message (use prtConsoleDisplayBufferText to read the display). The priority assigned for displaying this message is one lower than the READY message. In other words, the only message that can be replaced by these objects is the READY message. To clear the message, write a null string to both this object and BACKGROUND-STATUS-MSG-LINE2-PART1. |
||
background-message2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.2 | |||
background-status-msg-line2-part1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.2.1 |
The string displayed on the devices front panel in place of the printers built-in background status string. An example built-in background status string is 00 READY. Additional information: See BACKGROUND-STATUS-MSG-LINE1-PART1 |
||
error-log-clear | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.38 |
Setting this object clears all the entries in the error log sub-tree. Additional information: Setting this object removes all errors that have been stored in the printers non-volatile memory. |
||
collated-originals-support | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.42 |
Indicates that the printer can create multiple, collated originals of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or mopies. This is the base functionality required by the other collection items. cProofAndHold - The printer saves a copy of the job while printing the first mopy. Later, this held job can be released and the rest of the mopies will print. cSecurityPrint - The printer spools the job and holds the job until the user releases the job by entering a password at the printers control panel. cAutoHighlight - The printer prints the job a number of times with a mail distribution list prepended to each job. A different mailing address is highlighted on each mopy. cCollatedAtSpeed - The printer can create multiple collated copies where all copies after the original are printed at engine speed. Additional information: Indicates that the printer can create multiple, collated originals of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or mopies. This is the base functionality required by the other collection items. Without disk, this object will not exist. This will be set at boot-up initialization. If the disk fails, in any way, then the disk error functionality will handle the situation. A color printer (LaserJet 4550) that only has a RAMDISK installed is treated like there is no disk and therefore this object will not exist. The value of this object will be: !cCollatedOriginals - Only FLASH installed cCollatedOriginals - IDE is installed combined with/without FLASH cCollatedOriginals - RAMDISK is On combined with/without FLASH |
||
localization-languages-supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.52 |
The list of languages supported by the device. The languages are primarily, but not limited to, two character codes from ISO 639, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationLanguage for details about each language value. |
||
localization-countries-supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.53 |
The list of countries supported by the device. The countries are primarily, but not limited to, two character codes from ISO 3166, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationCountry for details about each country value. |
||
host-application-available-memory | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.59 |
Returns the amount of memory, in bytes, that the device has available for job-related processing or resources. Also known as driver work space (DWS) memory. |
||
control-panel-button-press | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.60 |
Writing this object simulates pressing a button on the control panel. Reading it will return the last key pressed either on the control panel or via PML. The device POS will specify which keys are supported. |
||
control-panel-display-contents-change-counter | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.63 |
A counter which increments whenever the contents of the front panel display changes. This object is implemented as a 32-bit signed integer which rolls over to zero when it reaches a maximum value. |
||
control-panel-display-contents-crc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.64 |
Reading this object returns a 32-bit Cyclical Redundancy Check (CRC) which represents the current contents of the display. Additional information: This object has been implimented as an 8-bit CRC for this product. |
||
control-panel-display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.65 | |||
control-panel-display-graphical-contents | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.65.1 |
Reading this object returns a graphical file format image representing the current pixel content of the display. The device POS will specify the expected screen resolution, color depth of the display and graphics file format for a given product (eg. 160x64x1 GIF format OR 640x240x4 JPEG format). If the image is large enough that it needs to be returned in multiple objects then each array object will contain a portion of the image. The image will then need to be reconstructed by a host application. An application that needs to determine if their is an additional object to be retreived will need to perform a GETNEXT operation until there are no more objects in the sub-tree. Additional information: This object returns a GIF image that represents the current contents of the 160x64x1 control panel display. Most display images require more than one instance of this object in order to retreive the complete GIF image. |
||
control-panel-key-press | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.66 |
Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. Additional information: Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. The LaserJet 9000 implementation of this object supports the Unified Key Encoding Scheme which is documented at http://clbu.boi.hp.com/~kevino/GCPA/keycodes.doc NOTE: Chris is working on an updated version of this scheme which will be referenced once made available. |
||
id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3 | |||
model-number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.1 |
Identifies the device model number as listed in the HP corporate price list (e.g. C2121A for DeskJet 500C). The string is as specific as possible. Products should note in POS if the model number on the CPL changes but the device reports the previous model number. If the model number changes based on the installed options, the POS should indicate if only the base model number is returned, or if the device senses the installed options and returns the correct model number. If possible, encode the model number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: Identifies the device model number as listed in the HP corporate price list (e.g. C2121A for DeskJet 500C). The string is as specific as possible. The value of this object does not change based on the installed options. The default of this object is the same on all LaserJet 8150 printers. |
||
model-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.2 |
Identifies the device model name (e.g. DeskJet 1200C). The string is as specific as possible. Capitalization and spacing should match family naming conventions. Products should note in POS if the model name on the HP corporate price list changes but the device reports the previous device name. If the model name changes based on the installed options, the POS should indicate if only the base model name is returned, or if the device senses the installed options and returns the correct model name. If possible, encode the model name in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: Since the value of this object is frequently used in displaying a list of printers, it is kept relatively short in case systems have limited width for their display area. The model name does not change based on sensing of installed options. |
||
serial-number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.3 |
Identifies the serial number for the device. If the SERIAL-NUMBER object is set by the user, then setting the object does not need to be protected. If the SERIAL-NUMBER object is set at the factory, then the <<hidden>> object must be set correctly before the SERIAL-NUMBER object is writable. If this is a writable object, the POS should indicate the maximum supported string length. If possible, encode the serial number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: This value IS AFFECTED BY NVRAM resets, it is set to the default value of XXXXXXXXXX, when a NVRAM init is done. |
||
fw-rom-datecode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.5 |
Identifies the base system firmware date code. The date code will be encoded in the yyyymmdd format. There may be several versions of the base system firmware. The date code associated with the version of the base system firmware that is being used is reported. There may be other date code objects for other specific modules such as fonts, localization modules, etc.; these other datecode objects are device specific. |
||
fw-rom-revision | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.6 |
This identifies the system code firmware ROM revision code. The format for a revision is major_revision.minor_revision. There may be other ROM revision code objects for other specific ROMs such as font ROMs, localization ROMs, etc; these other ROM revision code objects are device specific. |
||
device-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.10 |
User defined device name. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <OKNearestLegal ValueSubstituted>.Additional information: The maximum supported string length is 32 characters. If the user entered string is too long, the device will store the first 32 characters and will return the <noError> status. |
||
device-location | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.11 |
User defined device location. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <OKNearestLegal ValueSubstituted>.Additional information: The maximum supported string length is 16 characters. If the user entered string is too long, the device will store the first 16 characters and will return the <noError> status. |
||
asset-number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.12 |
User defined asset number. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <OKNearestLegal ValueSubstituted>.Additional information: The maximum supported string length is 8 characters. If the user entered string is too long, the device will store the first 8 characters and will return the <noError> status. |
||
formatter-serial-number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.20 |
This object returns the formatter serial number for the device. The value returned from this object is the FORMATTERNUMBER system variable. If possible, encode the serial number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: This object returns the formatter serial number for the device. The value returned from this object is the FORMATTERNUMBER system variable. If possible, encode the serial number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. |
||
interface | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4 | |||
simm | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1 | |||
simm1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1 | |||
simm1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.4 |
Returns an indication of the type of option installed in SIMM slot 1. eEmpty means the device did not detect any option installed in the interface slot. eUnknown means the device doesnt recognize the installed option. eUnSupported means the device recognizes the installed option, but does not support the option. eReadOnlyMemory means the installed option contains ROM Ics. eVolatileRandomAccessMemory means the installed option contains RAM ICs that loose data when the power is turned off. eNonVolatileRandomAccessMemory means that the installed option contains RAM ICs that do not loose data when the power is turned off. eFlashMemory means that the installed option contains a type of non-volatile RAM that needs to be erased before it can be written. eDiskDrive means the installed option contains a disk drive. eRamRom means the installed option contains both volatile random access memory and read only memory. eInputPHD means the installed option is an input paper handling device. eOutputPHD means the installed option is an output paper handling device. eIOCard means the installed option is an I/O card. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 8150. eRamRom is used to denote LaserJet 8150s combo simm. |
||
simm1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.5 |
Returns an indication of the capacity of the SIMM installed in SIMM slot 1. The capacity is dependent on the type of option, as indicated by the SIMM1-TYPE object. This object has no meaning if the installed option type is eUnknown or eReadOnlyMemory. This object contains the size, in bytes, if the installed option type is eVolatileRandomAccessMemory, eNonVolatileRandomAccessMemory, eFlashMemory, or eDiskDrive. If the type of the installed option is eRamRom, this object contains the size, in bytes, of the random access memory. If the type of the installed option is eInputPHD, the capacity indicates the number of input trays supported by the installed option. If the type of the installed option is eOutputPHD, the capacity indicates the number of output bins supported by the installed option. If the type of the installed option is eIOCard, the capacity indicates the number of logical I/O ports supported by the I/O card. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM1-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned. |
||
simm1-bank | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6 | |||
simm1-bank1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.1 | |||
simm1-bank1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.1.1 |
Returns an indication of the type of option installed in Bank 1 of SIMM slot 1. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm1-bank1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.1.2 |
Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 1. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM1-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm1-bank2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.2 | |||
simm1-bank2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.2.1 |
Returns an indication of the type of option installed in Bank 2 of SIMM slot 1. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm1-bank2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.1.6.2.2 |
Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 1. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM1-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2 | |||
simm2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.4 |
Returns an indication of the type of option installed in SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 8150. eRamRom is used to denote LaserJet 8150s combo simm. |
||
simm2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.5 |
Returns an indication of the capacity of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 8150. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM2-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned. |
||
simm2-bank | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6 | |||
simm2-bank1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.1 | |||
simm2-bank1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.1.1 |
Returns an indication of the type of option installed in Bank 1 of SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm2-bank1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.1.2 |
Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM2-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm2-bank2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.2 | |||
simm2-bank2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.2.1 |
Returns an indication of the type of option installed in Bank 2 of SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm2-bank2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.2.6.2.2 |
Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM2-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3 | |||
simm3-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.4 |
Returns an indication of the type of option installed in SIMM slot 3. See SIMM1-TYPE for a description. |
||
simm3-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.5 |
Returns an indication of the capacity of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 8150. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM3-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the simm is returned. |
||
simm3-bank | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6 | |||
simm3-bank1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.1 | |||
simm3-bank1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.1.1 |
Returns an indication of the type of option installed in Bank 1 of SIMM slot 3. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm3-bank1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.1.2 |
Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM3-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm3-bank2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.2 | |||
simm3-bank2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.2.1 |
Returns an indication of the type of option installed in Bank 2 of SIMM slot 3. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm3-bank2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.3.6.2.2 |
Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM3-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4 | |||
simm4-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.4 |
Returns an indication of the type of option installed in SIMM slot 4. See SIMM1-TYPE for a description. |
||
simm4-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.5 |
Returns an indication of the capacity of the SIMM installed in SIMM slot 4. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 8150. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM4-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the simm is returned. |
||
simm4-bank | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6 | |||
simm4-bank1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.1 | |||
simm4-bank1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.1.1 |
Returns an indication of the type of option installed in Bank 1 of SIMM slot 4. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm4-bank1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.1.2 |
Returns an indication of the capacity of Bank 1 of the SIMM installed in SIMM slot 4. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM4-BANK1-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
simm4-bank2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.2 | |||
simm4-bank2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.2.1 |
Returns an indication of the type of option installed in Bank 2 of SIMM slot 4. See SIMM1-TYPE for a description. Additional information: This object is used for describing the type of DIMM banks. Each physical DIMM slot has up to 2 banks. |
||
simm4-bank2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.1.4.6.2.2 |
Returns an indication of the capacity of Bank 2 of the SIMM installed in SIMM slot 4. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed bank option in bytes. This object is not supported unless the SIMM4-BANK2-TYPE type is eReadOnlyMemory, eFlashMemory, eEDORandomAccessMemory, eSDRandomAccessMemory, eSRandomAccessMemory, or eFPMRandomAccessMemory. |
||
mio | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3 | |||
mio1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1 | |||
mio1-model-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.2 |
Returns product information identifying the I/O card. Example: XXXX. |
||
mio1-manufacturing-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.3 |
Returns information describing the manufacture of the I/O card installed in MIO/EIO slot 1. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string. |
||
mio1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.4 |
Returns an indication of the type of option installed in MIO/EIO slot 1. See SIMM1-TYPE for an explanation of the enumerations. |
||
mio2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.2 | |||
mio2-model-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.2.2 |
Returns product information identifying the I/O card. Example: XXXX. |
||
mio2-manufacturing-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.2.3 |
Returns information describing the manufacture of the I/O card installed in MIO/EIO slot 2. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string. |
||
mio2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.2.4 |
Returns an indication of the type of option installed in MIO/EIO slot 2. See SIMM1-TYPE for an explanation of the enumerations. |
||
mio3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.3 | |||
mio3-model-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.3.2 |
Returns product information identifying the I/O card. Example: XXXX. |
||
mio3-manufacturing-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.3.3 |
Returns information describing the manufacture of the I/O card installed in MIO/EIO interface 3. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string. |
||
mio3-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.3.4 |
Returns an indication of the type of option installed in MIO/EIO interface 3. See SIMM1-TYPE for an explanation of the enumerations. |
||
socket-ping | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.7 | |||
socket-ping-job-events-version | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.7.1 |
This object reports the current version of the Socket Ping Job Events capability. The version number is returned as a string in the format MAJOR.MINOR.SUB version. (eg. 1.0.1) If socket ping is not supported by this printer then the object is either not implemented or it returns a 0. |
||
test | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.5 | |||
self-test | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.5.1 |
Writing this object allows a device self test to be started. Reading this object provides an indication what self-test is currently executing, if any. Actual self-test operation is device specific. A self test may not be allowed at any arbitrary time. If the device supports the requested self test, but can not start the execution of the self test when requested, the device will respond with <genErr>. If a non-destructive self test is being started, the device will generate a response before the self test is completed. RECOMMENDATION: If the device is ready (i.e. the NOT-READY-PRINTER object does not contain any items, except maybe being off-line) and is idle (i.e. the NOT-IDLE object does not contain any items), this request should always succeed. This provides a mechanism for driver writers to always determine if the action will succeed or not. Additional information: The eNonDestructiveSelfTest performs limited testing on the printer and its attached paper handling devices. After the self-test is complete a configuration page is printed. The recommended way to cause a configuration page to be printed is to use the PRINT-INTERNAL-PAGE object. Setting this object to eNonDestructiveSelfTest results in a status of <noError> and a value of eNonDestructiveSelfTest being returned. If the printer is not idle (whether printing an external job or printing an internal page), this action will be delayed until the next job boundary. See the PRINT-INTERNAL-PAGE object for more details. |
||
print-internal-page | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.5.2 |
Writing this object to a value other than eNotPrintingAnInternalPage causes the device to attempt to print an internally generated page. Reading this object provides an indication what internally generated page is currently being printed, if any. The actual page is device specific. Some devices may support continuously printing an internally generated page. Setting this object to eNotPrintingAnInternalPage terminates continuously printing internally generated pages. An internally generated page may not be allowed to be printed at any arbitrary time; under what conditions it will succeed or fail is device specific. If the device supports the requested page, but can not start printing the page when requested, the device will respond with <genErr>. RECOMMENDATION: If the device is ready (i.e. the NOT-READY-PRINTER object does not contain any items, except maybe being off-line) and is idle (i.e. the NOT-IDLE object does not contain any items), this request should always succeed. This provides a mechanism for driver writers to always determine if the action will succeed or not. Additional information: Previous products used ePCLDemoPage1ConfigurationPage(300) for the Configuration or Self Test page. This product uses eDeviceDemoPage1ConfigurationPage(3). LaserJet 8150 does not support continuously printing a demo page. When this object is set to a valid value, the status returned is <noError> and the value returned is ePrintingAnUnknownInternalPage. If the printer is idle, the page will be printed immediately. If the printer is currently printing another job, the internal page requested will not print until that job is finished. Setting this object to a valid value causes the desired page to be formatted and put in the printers print queue. While the page is being formatted a get on this object will return the value ePrintingAnUnknownInternalPage. Once the page (or pages) is finished being formatted, this object returns a value of eNotPrintingAnInternalPage, even though the page may not have finished being printed. Setting this object multiple times will queue up the requests, but only a limited number will be queued. Once the queue is full, additional requests will be ignored. |
||
engine-self-diagnostic | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.5.7 |
The ENGINE-SELF-DIAGNOSTIC object reveals current engine failures; it returns a binary string of two-byte motor, clutch, solenoid, and sensor failure codes. Additional information: The ENGINE-SELF-DIAGNOSTIC object reveals current Engine Failures; it returns a BINARY string of two-byte Motor, Clutch, Solenoid and Sensor failure codes. |
||
job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6 | |||
settings-job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1 | |||
clearable-warning | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.1 |
Returns or controls how the device will track clearable warnings. A clearable warning indicates a transient event in the device. The device will continue after the transient event occurs. If CLEARABLE-WARNING is eOff, the device does not track clearable warnings. If CLEARABLE-WARNING is eOn, all clearable warnings will be tracked until cleared (acknowledged). If CLEARABLE-WARNING is eJob, a clearable warning generated due to an event that occurs because of the print job being processed will be automatically cleared when the device has finished processing the job. Example clearable warning events include the device altering resolution or page protection due to memory constraints. The POS will document what transient events are treated as clearable warnings. Additional information: If set to eOn, the warning is displayed until the GO key is pressed or the CONTINUE object is set. If set to eJob, the warning is displayed until the end of the job in which it was generated. |
||
cancel-job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.2 |
Cancels the print job whose ID matches the value written to the CANCEL-JOB object. The host first learns the job ID using the CURRENT-JOB-PARSING-ID command. If the printer has completely processed the job, the printer responds with <badValue>. If the value of the CURRENT-JOB-PARSING-ID is smaller than the value written to the CANCEL-JOB object, then the printer responds with <badValue>. When read, returns the value of the last job ID what was canceled, or -1 to indicate no job has been canceled. Additional information: If the value written matches the ID of a job that is currently being canceled (for any reason), the printer responds with <noError>. It uses job IDs in the range of -1..32767. Because the ID number can wrap to zero, CURRENT-JOB-PARSING-ID may be smaller than the value written to this object; when this occurs, no error will result as long as the ID is for a currently processing job. This object is write only, so the comment in the general description stating the job ID will be returned on a read does not apply. A -1 represents the current job |
||
job-info-change-id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.3 |
Returns the current value of an object in the job-info sub-tree whose value has changed. Define the object identifier for the object whose value has changed as job-info.required-field.optional-field.job-id. job-info represents the OID prefix of all objects in the job-info sub-tree. Required-field represents the OID field value that follows the job-info prefix. Since some objects in the job-info sub-tree have two OID fields between the job-info prefix and the job-id, the optional-field represents the OID field between the required-field and the job-id field, if present. Using this definition, the format for the JOB-INFO-CHANGE-ID binary value can be described as follows: Bytes 0-3 : required-field Bytes 4-7 : optional-field, or all zeros if there is no optional field Bytes 8-11: Job ID. Bytes 12-n : The value of the object job-info. required-field.optional-field.job-id. All multi-byte values stored in Motorola (big-endian) format, where the most significant byte occurs first. Additional information: LaserJet 8100 will use this object to report changes to the job-info-pages-printed and job-info-state objects. The required-field (bytes 0 through 3) will designate whether the change to be reported involves the pages printed (13) or job state (15). The optional-field (bytes 4 through 7) will always be zeroes. The value-field (bytes 12 through 15) will contain the new value for pages printed or job state cast to a 32-bit integer. Note: It is possible that traps generated by this object have the same value. This is caused by the architecture of LaserJet 8100. In the LaserJet 8100 System, it is highly probable that the object value will change so rapidly that when the trap is processed, PML will read the same value twice. This is timing related and will generally be seen at the end of a job. |
||
hold-job-timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.10 |
The time, in minutes, that the printer will wait before automatically deleting a held job. This allows the printer to automatically clean up jobs that have been forgotten (held but never released). Additional information: This only applies to temporary held jobs, i.e., HOLD=ON or PROOF. This is a global timer that only affects the jobs that are sent after it is set. A value of 0 means never delete the jobs. Setting it to an unsupported value causes the printer to substitute a value (listed below) and to return <noError> status. LaserJet 4600 supports values of 0, 60, 240, 1440, and 10080 The values are as follows: <=0 snap to 0 (disabled) >=1 and <=150 snap to 60 (60 minutes) >=151 and <=840 snap to 240 (4 hours) >=841 and <=2880 snap to 1440 (1 day) >=2881 snap to 10080 (1 week) |
||
active-print-jobs | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2 | |||
job-being-parsed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2.1 | |||
current-job-parsing-id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2.1.1 |
Contains the printer assigned job identification for the job currently being processed by the processing PDL sub-system. The job ID is a monotonically increasing number. The job ID may be reset to zero at power-up and may roll over to zero after reaching some maximum value. Additional information: A value of -1 is returned when the printer is not parsing a job. When data for a new job is detected, this object is updated (the job may or may not turn out to be a Null Job); however, the trap does not occur until the printer determines that it is not a Null Job. (A job is considered to be a null job if it has no name or job attribute, causes no pages to be printed, and consumes MIN_JOB_SIZE (9) or fewer bytes.) A trapped value will differ from the previous value by one or more. Some job-info- objects are created when the first data bytes are received. If the printer determines that the job is a Null Job, the job-info- objects related to the Null Job are deleted. LaserJet 8100 retains the job-info- objects for the MAX_JOBS_IN_LIST (32) most recent jobs that are not Null Jobs. The first job received after power-up will have job ID 1, and the job ID will increment to 2,147,483,647 before rolling to zero. To distinguish whether a power cycle or a rollover causes a reduction in the job ID value, the object prtGeneralConfigChanges can be watched and if it increments at the same time as the drop is observed in the value of CURRENT-JOB-PARSING-ID, then a power cycle is the most likely cause. |
||
job-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5 | |||
job-info-name1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.1 |
Contains the first part of this print jobs name. The last OID field for this dynamic object contains the job ID. Additional information: The job name is the string specified by the NAME= parameter of the @PJL JOB command which allows a maximum of 80 characters. The first 40 characters are in this object and the second 40 are in job-info-name2. The symbol set is Roman-8. When jobs are nested, the value assigned to this object is the name provided by the most recent @PJL JOB NAME= command. If no name is provided, a null string is returned. |
||
job-info-name2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.2 |
Contains the second part of this print jobs name. The last OID field for this dynamic object contains the job ID. Additional information: See job-info-name1. |
||
job-info-stage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.10 |
Indicates what printer sub-systems are currently processing this print job. The last OID field for this dynamic object contains the job ID. cSourceSubsystem - some of the job is in the printer I/O subsystem. cProcessingSubsystem - some of the job is in the printer imaging processing subsystem. cDestinationSubsystem - some of the job is being printed. Additional information: For LaserJet 8100, cSourceSubsystem and cProcessingSubsystem will always be set and cleared together. They are set when the beginning of the job is detected, and they are cleared when the end of the job is parsed. A non-printing job will never set cDestinationSubsystem. When a page is ready to be printed (the intermediate has been built and the page is `closed by the personality), cDestinationSubsystem will be set even if a page of a previous job is currently being printed. cDestinationSubsystem remains set until the last page of the job has finished printing. If a page requires extensive processing and allows all the previous pages of a job to complete printing, cDestinationSubsystem will remain set until the last page of the job has finished printing. |
||
job-info-io-source | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.11 |
Indicates which I/O source, the print job was received over. The value maps to port numbering scheme supported in the DEVICE/SOURCE-SUBSYSTEM/IO/PORTS sub-tree. |
||
job-info-pages-processed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.12 |
Indicates the number of pages processed by the processing subsystem. If neither the cSourceSubsystem or the cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages processed for this job. The last OID field for this dynamic object contains the job ID. Additional information: This object is incremented by one when a page is processed (`closed by the personality), regardless of the number of pages that are printed as a result of the single page processed. In other words, it does not matter how many identical copies of a page are printed or no pages may be printed if operating in silent run mode, this count is incremented exactly once. A page is considered processed when all of the input data has been processed for a page (that is, when the intermediate has been produced, and the personality has `closed the page. At this time, the image of the page is not necessarily completely formed.) |
||
job-info-pages-printed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.13 |
Indicates the number of pages printed by the destination subsystem. If none of the cSourceSubsystem, cProcessingSubsystem or cDestinationSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages printed for this job. This value may increase by two each time for duplex jobs. The last OID field for this dynamic object contains the job ID. Additional information: If multiple copies of a page are printed, each copy is counted individually. |
||
job-info-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.14 |
Indicates the number of bytes of data processed by the processing subsystem. If neither of the cSourceSubsystem or cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the size of this job, in bytes. The last OID field for this dynamic object contains the job ID. Additional information: This count may be incremented by values other than one as blocks of data are processed; blocks of data (which may be as large as 2K bytes) will be processed in a varying amount of time. During the processing of a job and even when a job completes, an exact count of the number of I/O bytes processed by the job is not necessarily to be expected. |
||
job-info-state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.15 |
Indicates the state of the job. The last OID field for this dynamic object contains the job ID. eAborted - the print job was aborted. eWaitingForResources - the print job requires resources that are not currently available. Example resources that can cause the job to wait include the print engine or PDL processor being unavailable. The print engine could be unavailable due to paper out, paper jam, staple out, stapler jam, marking agent low, output bin full, etc. The PDL processor could be unavailable due to an off-line condition. Each printer specific object specification should state which conditions cause a job to be waiting for resources and also state which objects can be retrieved by an application to determine the exact cause of a resource being unavailable. ePrinted - the job has printed. The related JOB-INFO- OUTCOME object indicates if any problems were encountered while the job was processed. eRetained - the job can be reprinted. eTerminating - the job was aborted or cancelled and is currently is terminating. eInterrupted - the job has been interrupted. The job can be continued. ePaused - the job has been paused. The job can be continuted. eCancelled - the job has been cancelled. eProcessing - the job is currently being printed normally. |
||
job-info-outcome | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.19 |
Indicates if any warning or error conditions were encountered while processing the assoicated job. The last OID field for this dynamic object contains the job ID. Additional information: In LaserJet 8100, warnings and errors are not recorded in this object. Although no meaningful information can be obtained from this object, it is kept around for the compatibility needs of existing software. |
||
job-info-outbins-used | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.20 |
Indicates which output bins this job has delivered printed pages to. The last OID field for this dynamic object contains the job ID. Additional information: The bins designated by this collection include the printers own output bins as well as the `logical output bins associated with any attached external paper handling devices. (The mapping of the physical output bins of an external paper handling device to its `logical output bins depends on the usage mode of the device. For instance, in `mailbox mode, there is one-to-one correspondence of `logical output bins to physical bins, whereas in `stacker mode, one `logical output bin may map to several physical bins.) Although LaserJet 4100 and LaserJet 4550 both come with two output bins -- a face-down bin on the top of the device and a face-up bin at the back of the device -- firmware will not provide a means of selecting between the two, nor will it report which of the two gets used. For this reason, bit 0 (cOutbin1) of this collection is being used to designate both of these bins together. |
||
job-info-physical-outbins-used | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.22 |
Indicates which physical output bins this job has delivered printed pages to. The last OID field for this dynamic object contains the job ID. Additional information: The output bins designated by the bits of this collection include the standard output bin(s) plus the physical bins of attached external paper handling devices. The configuration (if any) of external paper handling devices will determine the mapping of individual bits in this collection to the physical bins of the devices. For LaserJet 4100 and LaserJet 4550, the cOutbin1 is used for Face Down bin, cOutbin2 is used for Face Up bin, and 3-15 are used for the 13 optional output bins (12 plus an extension to the Face Up bin) for backwards compatibility with LaserJet 8000/LaserJet 8100 and forwards compatibility with LaserJet 8150. However, since they cannot distinguish output going to the Face Up or Face Down bin in the firmware because the diverter can only be moved manually, bit 0 (cOutbin1) is being used to designate both of these bits together. If an external paper handling output device is connected, then bit 2 (cOutbin3) will represent the devices first output bin (and so on). |
||
job-info-attribute | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23 | |||
job-info-attr-1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.1 |
Returns the value that was set in PJL via the SET JOBATTR= command. Attribute objects are saved sequentially, starting with 1, after the start of a job. If more attributes are set than there are objects to store them, the excess JOBATTR values are ignored. If the corresponding SET JOBATTR= command has not been received when a get is done for this object, a status of <noSuchName> will be returned. |
||
job-info-attr-2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.2 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.3 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.4 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.5 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.6 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.7 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.8 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.9 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.10 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.11 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.12 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.13 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.14 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.15 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-attr-16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.16 |
Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
||
job-info-requested-originals | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.24 |
The number of requested collated copies. The value was supplied with the job via PJL QTY variable, the PostScript Collate and NumCopies entries in the page device dictionary, or via some other mechansim. |
||
job-info-page-count-current-original | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.25 |
The page number being printed within the current copy of a collated multi-copy job. This value changes when the job-info-pages-printed changes. The job-info-pages-printed indicates the total number of pages printed in the job, while this object indicates the number of pages printed for this copy of a collated multi-copy job. Additional information: The number of pages in the current copy of a collated multi-copy job which have been completely printed and safely delivered to the output bin. |
||
job-info-pages-in-original | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.26 |
Number of pages in a single copy of a collated multi-copy job. |
||
job-info-printed-originals | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.27 |
Number of collated copies completely printed and delivered to the output bin at time of query. |
||
job-info-accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28 | |||
job-info-accounting-media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.1 |
Contains the media size of the printed job. The media size of the first page will decide the media size of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
||
job-info-accounting-media-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.2 |
Contains the media type of the printed job. The media type of the first page will decide the media type of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
||
job-info-accounting-finishing-options | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.3 |
Contains the finishing option used on the printed job. The finishing option specified for the first page will decide the finishing option of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
||
job-info-accounting-media-simplex-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.4 |
Contains the total number of simplex pages printed in a particular job. |
||
job-info-accounting-media-duplex-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.5 |
Contains the total number of duplex pages printed in a particular job. |
||
job-info-accounting-grayscale-impression-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.6 |
Contains the total number of monochrome pages printed in a particular job. |
||
job-info-accounting-color-impression-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.7 |
Contains the total number of color pages printed in a particular job. |
||
job-info-accounting-black-dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.8 |
Contains the total number of black pixels used in a particular job. |
||
job-info-accounting-yellow-dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.9 |
Contains the total number of yellow pixels used in a particular job. |
||
job-info-accounting-cyan-dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.10 |
Contains the total number of cyan pixels used in a particular job. |
||
job-info-accounting-magenta-dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.11 |
Contains the total number of magenta pixels used in a particular job. |
||
job-info-accounting-scanned-media-simplex-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.12 |
Contains the total number of simplex pages scanned, indexed by media size. For each media size that is scanned, there are 6 bytes of information in the following format. media-size number of scanned pages 01 2345 Bytes 0-1 contain a value from the media-size enum and bytes 2-5 contain the number of the media size scanned. For example if a 10 Letter pages are scanned followed by 5 Legal pages scanned, the pValue of the object would be 02000A030005 |
||
job-info-accounting-scanned-media-duplex-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.13 |
Contains the total number of duplex pages scanned, indexed by media size. For each media size that is scanned, there are 6 bytes of information in the following format. media-size number of scanned pages 01 2345 Bytes 0-1 contain a value from the media-size enum and bytes 2-5 contain the number of the media size scanned. For example if a 10 Letter pages are scanned followed by 5 Legal pages scanned, the pValue of the object would be 02000A030005 |
||
job-info-accounting-job-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.14 |
Keeps track of what type of job is processed. |
||
held-job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7 | |||
held-job-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1 | |||
held-job-user-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.1 |
User name that is obtained by the driver through some internal method or from user input. Additional information: The following is a general description for all the JOB-MANAGEMENT objects described below. These object describe the attributes of the dynamic list containing all the stored jobs on the disk available for printing or deleting via the job-management feature. The jobs on this list are not deleted from the disk unless explicitly specified by the user. A print job may be specified for retention by PJL commands in the data stream. Following is a list of the PJL commands (i.e. these comments describe the PJL implementation and in some cases do not reflect the PML implementation.): @PJL SET HOLD=OFF|ON|PROOF|STORE|PRINT GENERAL DESCRIPTION: This variable specifies the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. OFF: The job is printed but not retained on disk after printing. This is the default value. ON: This setting may be thought of as free proof-and-hold. The requested number of copies will be printed and the job will be temporarily stored on disk. The job will then be available for printing additional copies through the control panel and through PML. There will be a limit to the number of these temporary jobs that may be stored, and when the limit is exceeded the oldest job will be removed from the disk. PROOF: One copy of the job is printed and remaining copies are stored on disk. The job is then available to select for printing via the control panel menus or PML. The job will be deleted from the disk when the disk space is needed for another proof and hold job but only after the additional copies have been printed. It will also be deleted when the user sends down another proof and hold job with the same job name, or the user explicitly deletes the job. STORE: The job is not printed immediately but is retained on disk. The job is available to select for printing via the control panel DEFAULT VALUE: OFF The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET USERNAME=<80 bytes> GENERAL DESCRIPTION: Eighty-character user name that is obtained by the driver through some internal method or from user input. If the job stream does not contain a USERNAME the default value will be NO USER NAME. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. DEFAULT VALUE: NO USER NAME The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and, INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET JOBNAME=<80 bytes> GENERAL DESCRIPTION: Eighty-character job name that may be generated by the driver or obtained from user input. This value may be used in conjunction with the USERNAME to select a job from the front panel. If the job stream does not contain a JOBNAME, the printer will assume no job name; each subsequent job that is sent down by the same user would replace the users last job on disk. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. NOTE: The limit of 80 bytes is a PJL limit. The limit for PML will be 40 bytes. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDTYPE=PUBLIC|PRIVATE GENERAL DESCRIPTION: This variable specifies the privacy level of the job. PUBLIC: The job does not require a PIN in order to be released for printing. This is the default value. PRIVATE: The job requires a PIN in order to be released for printing. The PIN is specified by the HOLDKEY variable. If the HOLDTYPE is set to PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY is specified, the job will be considered PUBLIC. DEFAULT VALUE: PUBLIC The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDKEY=4 digits, 0000...9999 GENERAL DESCRIPTION: A 4-digit string, each digit 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. If a HOLDTYPE is PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY value is specified, a job will be considered PUBLIC. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. The format for the OID is as follows: 3.4.1.6.x.y <-----> | | | | \ / | job-id in the system / \ PML_JOB_MGNT_ROOT_OID \ job attribute 1..6 x values are 1..6: 1) user-name: user name that is obtained by the driver through some internal method or from user input. 2) job-name: job name may be generated by the driver or obtained from user input. 3) hold: indicates the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. There are 4 options: OFF: The job is printed but not retained on the disk. ON: The job is printed and stored temporarily on the disk. STORE: The job is not printed but stored on the disk. PROOF: One copy of the job is printed and the remaining copies are stored on the disk. 4) holdtype: The variable specifies the security level of the job. PUBLIC: The job does not require a PIN in order to release the job for printing. PRIVATE: The job requires a PIN in order to be released for printing. 5) quantity: number of copies to print. Valid values are 0..999. 6) pin: A 4 digit string, each digit is 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. y : an unsigned 32-bit number which uniquely identifies the job. The job id for the job remains the same for the job until it is deleted from the held jobs list. For example, the OID below is asking for the user name of the job whose id is 3. The application would issue: OID get 3.4.1.6.1.3 For example, the <getnext> OID values sequence is as follows: OID returned OID getnext 3.4.1.6 3.4.1.6.1.1 getnext 3.4.1.6.1.1 3.4.1.6.1.2 getnext 3.4.1.6.2.1 3.4.1.6.2.2 *** getnext 3.4.1.6.1.6 3.4.1.6.1.7 getnext 3.4.1.6.2.1 3.4.1.6.2.2 getnext 3.4.1.6.5.2828 3.4.1.6.6.1 NOTE: for example above, job id 2828 is the last job in the list of held jobs. *** Also supported is <getnext> on the job attributes: OID returned OID getnext 3.4.1.6.1 3.4.1.6.1.1 getnext 3.4.1.6.6 3.4.1.6.6.1 |
||
held-job-job-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.2 |
The job name may be generated by the driver or obtained from user input. |
||
held-job-retention | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.3 |
Indicates the retention classification of the job. The values indicate whether the job is printed immediately or stored. There are 4 options: eHoldOff: The job is printed but not retained on the disk. eHoldOn: The job is printed and stored temporarily on the disk. eHoldStore: The job is not printed but stored on the disk. eHoldProof: One copy of the job is printed and the remaining copies are stored on the disk. |
||
held-job-security | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.4 |
The variable specifies the security level of the job. eHoldTypePublic: The job does not require a PIN in order to release the job for printing. eHoldTypePrivate: The job requires a PIN in order to be released for printing. |
||
held-job-quantity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.5 |
Number of copies to print. |
||
held-job-pin | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.6 |
A string that is specified in the job stream and then required to be entered in order to release the job for printing. PIN stands for Personal Identification Number. Additional information: Must be a 4 digit string, each digit must be 0..9 or a null string if there is no pin. For security purposes, you can no longer get the value of the PIN. |
||
held-job-control | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2 | |||
held-job-print | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.1 |
Instructs the printer to schedule the specified held job for printing with the specified number of copies. The job-id is used to identify which job to print. A held job can also be printed from the control panel. Additional information: Bytes 0-3 is the job id of the job to print. Bytes 4-7 is the number of copies to print. Bytes 8-11 (optional) contain the PIN for a Private job. |
||
held-job-delete | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.2 |
Instructs the printer to delete the specified held job from the list. The job-id is used to identify which job to delete. A held job can also be deleted from the control panel. Additional information: Setting this to a value that is not a Held Job on the system or is a Private Held Job returns <ErrUnsupValue>. To delete a private Held Job, you must use the PML object HELD-JOB-PRINT with a quantity of 0 and supply the correct HELD-JOB-PIN with the request. (See HELD-JOB-PRINT) |
||
held-job-set-queue-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.3 |
Sets the maximum number of jobs which can be stored in the held job list. Additional information: Sets the size of the temporary job lists queue. |
||
held-job-enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.4 |
Enables or disables Job Retention (Job Hold). The valid values are eDisabled and eEnabled. (Specifying an invalid mode causes an <badValue> error to be returned.) When eDisabled is specified all Job Retention (Hold, Proof, Store, PIN Printing) is disabled. When eEnabled is specified, the Job Retention characteristics of a given job are defined by the PJL variable SET HOLD. Additional information: When disabled, held jobs are not removed, but must be explicitly removed through the Control Panel or the PML object HELD-JOB-DELETE. |
||
file-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10 | |||
settings-file-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1 | |||
file-system-max-open-files | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.2 |
The number of open files allowed at one time. Opening a file when the maximum number of files are currently open will fail. Additional information: Indicates the number of open files a personality (e.g. PCL or PostScript) is guaranteed to be able to open before the file system runs out of file handles. This object is between 1 and 500. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. |
||
file-system-set-system-partition-writeable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.6 |
This object allows the system partition to be written to. It consists of a C structure containing the following fields: typedef struct { ubyte password[8]; ubyte volumenumber; } fs_writeable_system_partition_t; which is described below: Bytes 0 - 7: contain the password Byte 8 : is the volume number Access to this command is controlled by the password. If the password supplied is incorrect the command will fail. The volumenumber is a volume number of an existing system partition. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Returns <badValue> if the password is incorrect or if the volume requested is not present. |
||
file-system-set-system-partition-readonly | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.7 |
Changes a system partition to be READ-ONLY. The value is the volume number to change. If the volume number specified is NOT a system partition an error is returned. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. Returns <badValue> if the volume requested is not present. |
||
file-system-delete-files | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.8 |
Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; which is described below: Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the Athentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the Authentication data used to verify access for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a regular expression that may match multiple files (e.g <path>/*.exe). Access to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values. Additional information: Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. This object is always present. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the authentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the authentication data used to verify access for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a file-type regular expression that may match multiple files (e.g., <path>/*.exe). Access to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values. |
||
file-system-security-access-password | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.9 |
This object acts as a gate keeper for write access to the PML objects FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE, and FILE-SYSTEM-WIPE-DISK. The object can be viewed as always being in one of 4 states: State 0 --> Un-initialized: FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string and a pmlget operation on the object will return the string 0. This will be the state after an NVRAM init which is the only way to set the object to the empty string. It cannot be set to the empty string through PML. In this state write access to FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE and FILE-SYSTEM-WIPE-DISK is disabled while write access to the object itself is enabled. A successful set operation on the object in this state will return the string SET and will result in a transition to State 3. State 1 --> The Password is set to a non-empty string: A pmlget operation on the object will return the string 1 regardless of the actual stored password value. In this state write access to FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE and FILE-SYSTEM-WIPE-DISK is disabled. The only string the object itself can be successfully set to while in this state is the current value of the password. Setting the object to its current value causes a transition to State 2 which is an authenticated state. The value returned from such a set operation will be the string OK. State 2 --> The password is in an authenticated state: The gate to write to the PML objects FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES, FILE-SYSTEM-ERASE-MODE, and FILE-SYSTEM-WIPE-DISK is open. One, and only one, write operation can be performed on one of these three objects. During such a write operation the object itself will transition to State 1 thus closing the gate. In State 2 a pmlset operation on the object will result in the password being set and a transfer to State 3. The value returned from a set operation in this state on FILE-SYSTEM-SECURITY-ACCESS-PASSWORD will be SET. A pmlget operation on the object will return the string 2 regardless of the actual password value. State 3 --> The password was just changed: A pmlget operation on the object will return the string 3. Otherwise behaviors in State 3 are exactly like in State 1. |
||
file-system-external-access-capabilities | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.10 |
This object is used to control access to the file system of the device. It is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string, and a successful write to that object with the current password has preceded the write to this object. In other words, the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must be in the authenticated state for a write on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES to succeed. After the object has successfully been written to, it becomes read-only, and the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD object exits the authenticated state. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES possible. cDisablePJLFileSystemAccess - All file system access through PJL will be disabled. cDisablePMLFileSystemWrite - All file-systems-related PML objects such as FILE-SYSTEM-DELETE-FILES or hrPartitionLabel become read-only. For objects that are normally write-only this means that no successful operations can now be performed on them. cDisableNFSFileSystemAccess - All NFS file system access will be disabled. cDisablePSFileSystemAccess - All file system access through PostScript will be disabled. cDisableEWSFileSystemAccess - All access to the file system by the Embedded Web Server will be disabled. |
||
file-system-erase-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.11 |
This object is used to control how file data is handled when files are deleted. It is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string or when a write to FILE-SYSTEM-SECURITY-ACCESS-PASSWORD with the current password has preceeded the write to the object. When FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string then this object becomes read-only after a successful write to it. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on the object possible. If the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is incorrectly set, this object becomes read-only until the password is correctly set. The logical settings for this object are: NonSecureFastErase - When a file is deleted, only the reference to it in the file system tables is removed. No file data is overwritten. This is the default setting. This is the setting when both bits in the collection are set to 0. SecureFastErase - File information is overwritten with identical, random character pattern when it is deleted. This is the setting when cEraseMode0 is set to 1 and cEraseMode1 is set to 0. SecureSanitizeErase - Secure, repetitive algorithm used to overwrite all deleted file information and remove any residual data persistence. A random character is written to all bytes of deleted sectors. Then the complement of that character and finally, another random character is written. This is the setting when cEraseMode0 is set to 0 and cEraseMode1 is set to 1. Note that an error will be returned for an attempt to set both bits of the collection to 1. |
||
file-system-wipe-disk | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.12 |
This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node whether the file system on the device is going to be erased according to the setting of the FILE-SYSTEM-ERASE-MODE referenced by the corresponding hrDeviceIndex. A file system will be overwritten on system reboot if this object is set to 1. It will be unchanged if this object is set to 0. If this objects value is -1 then the file system cannot be wiped. If the file system contains the permstore, the permstore will be saved off and restored after the file-system wipe is completed. This object is always readable. It is writable when FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is the empty string or when a write to FILE-SYSTEM-SECURITY-ACCESS-PASSWORD with the current password has preceeded the write to the object. When FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is not the empty string then this object becomes read-only after a successful write to it. FILE-SYSTEM-SECURITY-ACCESS-PASSWORD must then be written to again with the current password in order to make another write operation on the object possible. If the FILE-SYSTEM-SECURITY-ACCESS-PASSWORD is incorrectly set, this object becomes read-only until the password is correctly set. |
||
file-system-wipe-disk-status | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.13 |
This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node the status of a disk wipe in progress. A return value of -1 indicates that no disk wipe is in progress. A return value in the range of 0 to 100 indicates the percent done for a disk wipe in progress. All other values are illegal. |
||
file-systems | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3 | |||
file-system2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.2 | |||
file-system2-initialize-volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.2.6 |
Setting this object to eInitializing causes file system 2 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM2-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 1st device. |
||
file-system3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.3 | |||
file-system3-initialize-volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.3.6 |
Setting this object to eInitializing causes file system 3 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM3-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 2nd device. |
||
file-system4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.4 | |||
file-system4-initialize-volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.4.6 |
Setting this object to eInitializing causes file system 4 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage devices, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM4-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 3rd device. |
||
errorlog | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11 | |||
error1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1 | |||
error1-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1.1 |
Contains some sort of time stamp indicating when error 1 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: This item contains the engine page count when the error occurred. If there is currently no error entry for this object, a 0 will be returned. Note that 0 may also be returned when there is a valid error, but a current page count was unavailable. If ERROR1-CODE object also returns 0, then an error has not yet been logged for this object. See ERROR1-CODE for an explanation of the order used for storing errors. |
||
error1-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: Returns a device specific error code. If the error code returned is 0, then the printer has not yet logged an error for this object. When the maximum number of errors is reached (30 on Digital Sender printers), and a new error occurs, the error in ERROR1-CODE will be replaced by the one in ERROR2-CODE, and so on until the last error object will be given the value of the new error. The error number is returned in the upper 16 bits. If it is 68, 69, 79, or 80, then the sub code is returned in the lower 16 bits (eg. 68 001C, where the subcode is already a hexadecimal value). If the error number is any other number, then the 1st sub code (XX) will be in bits 15-8 and the 2nd sub code (YY) will be in bits 7-0 (eg. 55.04.02) where XX=04 and YY=02). Example: If the error is 68 001A, then the value returned will be 4456474. To break it down: 4456474 = 0x0044001A The upper 16 bits: 0x0044 = 68 The lower 16 bits: 0x001A = 001A Which is the error: 68 001A Example: If the error is 55.04.241, then the error code will be 3605745. To break it down: 3605745 = 0x003704F1 The upper 16 bits: 0x0037 = 55 The upper byte of the lower 16 bits: 0x04 = 04 The lower byte of the lower 16 bits: 0xF1 = 241 Which is the error: 55.04.241 |
||
error2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2 | |||
error2-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2.1 |
Contains some sort of time stamp indicating when error 2 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error2-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3 | |||
error3-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3.1 |
Contains some sort of time stamp indicating when error 3 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error3-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4 | |||
error4-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4.1 |
Contains some sort of time stamp indicating when error 4 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error4-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5 | |||
error5-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5.1 |
Contains some sort of time stamp indicating when error 5 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error5-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6 | |||
error6-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6.1 |
Contains some sort of time stamp indicating when error 6 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error6-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7 | |||
error7-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7.1 |
Contains some sort of time stamp indicating when error 7 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error7-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8 | |||
error8-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8.1 |
Contains some sort of time stamp indicating when error 8 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error8-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9 | |||
error9-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9.1 |
Contains some sort of time stamp indicating when error 9 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error9-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10 | |||
error10-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10.1 |
Contains some sort of time stamp indicating when error 10 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error10-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11 | |||
error11-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11.1 |
Contains some sort of time stamp indicating when error 11 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error11-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12 | |||
error12-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12.1 |
Contains some sort of time stamp indicating when error 12 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error12-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13 | |||
error13-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13.1 |
Contains some sort of time stamp indicating when error 13 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error13-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14 | |||
error14-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14.1 |
Contains some sort of time stamp indicating when error 14 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error14-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15 | |||
error15-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15.1 |
Contains some sort of time stamp indicating when error 15 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error15-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16 | |||
error16-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16.1 |
Contains some sort of time stamp indicating when error 16 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error16-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error17 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17 | |||
error17-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17.1 |
Contains some sort of time stamp indicating when error 17 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error17-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error18 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18 | |||
error18-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18.1 |
Contains some sort of time stamp indicating when error 18 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error18-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error19 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19 | |||
error19-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19.1 |
Contains some sort of time stamp indicating when error 19 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error19-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error20 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20 | |||
error20-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20.1 |
Contains some sort of time stamp indicating when error 20 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error20-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error21 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21 | |||
error21-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21.1 |
Contains some sort of time stamp indicating when error 21 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error21-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error22 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22 | |||
error22-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22.1 |
Contains some sort of time stamp indicating when error 22 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error22-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error23 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23 | |||
error23-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23.1 |
Contains some sort of time stamp indicating when error 23 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error23-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error24 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24 | |||
error24-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24.1 |
Contains some sort of time stamp indicating when error 24 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error24-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error25 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25 | |||
error25-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25.1 |
Contains some sort of time stamp indicating when error 25 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error25-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error26 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26 | |||
error26-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26.1 |
Contains some sort of time stamp indicating when error 26 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error26-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error27 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27 | |||
error27-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27.1 |
Contains some sort of time stamp indicating when error 27 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error27-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error28 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28 | |||
error28-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28.1 |
Contains some sort of time stamp indicating when error 28 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error28-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error29 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29 | |||
error29-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29.1 |
Contains some sort of time stamp indicating when error 29 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error29-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error30 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30 | |||
error30-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30.1 |
Contains some sort of time stamp indicating when error 30 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error30-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error31 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31 | |||
error31-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31.1 |
Contains some sort of time stamp indicating when error 31 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error31-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error32 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32 | |||
error32-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32.1 |
Contains some sort of time stamp indicating when error 32 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error32-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error33 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33 | |||
error33-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33.1 |
Contains some sort of time stamp indicating when error 33 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error33-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error34 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34 | |||
error34-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34.1 |
Contains some sort of time stamp indicating when error 34 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error34-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error35 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35 | |||
error35-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35.1 |
Contains some sort of time stamp indicating when error 35 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error35-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error36 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36 | |||
error36-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36.1 |
Contains some sort of time stamp indicating when error 36 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error36-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error37 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37 | |||
error37-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37.1 |
Contains some sort of time stamp indicating when error 37 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error37-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error38 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38 | |||
error38-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38.1 |
Contains some sort of time stamp indicating when error 38 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error38-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error39 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39 | |||
error39-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39.1 |
Contains some sort of time stamp indicating when error 39 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error39-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error40 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40 | |||
error40-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40.1 |
Contains some sort of time stamp indicating when error 40 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error40-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error41 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41 | |||
error41-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41.1 |
Contains some sort of time stamp indicating when error 41 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error41-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error42 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42 | |||
error42-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42.1 |
Contains some sort of time stamp indicating when error 42 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error42-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error43 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43 | |||
error43-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43.1 |
Contains some sort of time stamp indicating when error 43 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error43-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error44 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44 | |||
error44-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44.1 |
Contains some sort of time stamp indicating when error 44 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error44-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error45 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45 | |||
error45-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45.1 |
Contains some sort of time stamp indicating when error 45 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error45-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error46 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46 | |||
error46-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46.1 |
Contains some sort of time stamp indicating when error 46 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error46-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error47 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47 | |||
error47-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47.1 |
Contains some sort of time stamp indicating when error 47 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error47-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error48 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48 | |||
error48-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48.1 |
Contains some sort of time stamp indicating when error 48 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error48-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error49 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49 | |||
error49-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49.1 |
Contains some sort of time stamp indicating when error 49 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error49-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
error50 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50 | |||
error50-time-stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50.1 |
Contains some sort of time stamp indicating when error 50 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
||
error50-code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50.2 |
Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
||
resource-manager | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12 | |||
mass-storage-resources | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3 | |||
mass-storage-resource-change-counter | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3.1 |
A counter which changes when a mass storage based resource has been added or deleted. Additional information: The value of this counter changes each time the MASS-STORAGE-RESOURCE-CHANGED object is set to eTrue. The value also changes when the mass storage device is initialized. However, the value does not change when a mass storage device is removed and a different mass storage device is installed. Initializing all volumes sets this object back to the factory default value. A reboot sets this object back to the factory devalut value. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. |
||
mass-storage-resource-changed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3.2 |
Setting to eTrue causes MASS-STORAGE-RESOURCE-CHANGE-COUNTER to be incremented. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. |
||
remote-procedure-call | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13 | |||
settings-rpc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1 | |||
rpc-bind-protocol-address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1.2 |
Array of Berkeley sockets style protocol addresses used to bind RPC to a communications protocol family. Setting an instance of this array object to a zero length binary value disables the transport protocol indicated by that instance. All multi-bytes fields are in network (or big-endian) order. Bytes 1 and 2 indicate the transport protocol. Some of the transport protocol mapping information can be found in RFC 1010 Assigned Numbers. A list of interesting transport protocol number mappings include: <table> Protocol | Number ---------+------- UDP/IP | 17 IPX | 1000 MLC | 4660 </table> Bytes 3 and 4 indicate the address family. The address family uses the same mapping as the BSD sockets address family. A list of interesting address family mappings include: <table> Address Family | Number ---------------+------- Internet | 2 NetWare | 6 MLC | 22136 </table> The format the fifth and following bytes is dependent on the address family. For the Internet address family, bytes 5 and 6 contain the port number, bytes 7 through 10 contain the IP address, and the following eight bytes are unused. For NetWare, bytes 5 through 8 are the network number, bytes 9 through 14 are the node number, and bytes 15 and 16 are the socket number. Additional information: The length of the binary value is zero if the instance of an object in the rpc-bind-protocol-address array is not in use. Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. |
||
status-rpc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2 | |||
rpc-bound-protocol-address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2.3 |
An array of Berkeley sockets style protocol addresses that the NFS service has been bound to successful. The format is that same as the array of RPC-BIND-PROTOCOL-ADDRESS of objects. Additional information: Returns <noSuchName> status if attempting to access this object and there is no storage device is installed. |
||
mass-storage-block-driver | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15 | |||
settings-mass-storage-bd | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1 | |||
ram-disk-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1.1 |
Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eOn turns on the RAM disk functionality and creates a RAM disk whose size is controlled by the RAM-DISK-SIZE object. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on installed options and other memory related settings. Additional information: Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on the amount of installed memory. |
||
ram-disk-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1.2 |
Returns or controls the size of the RAM disk. The device POS specifies the minimum memory requirements. The object MAXIMUM-RAM-DISK-MEMORY specifies the maximum memory available for the RAM disk. Additional information: Returns the size of the RAM disk. |
||
status-mass-storage-bd | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.2 | |||
maximum-ram-disk-memory | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.2.1 |
This objects name is misleading. This object does not return the maximum configurable RAM disk size. Instead, it returns the maximum amount of memory, in bytes, that can used to increase the size of the RAM disk. Additional information: This object returns the maximum amount of additional memory that is available for increasing the size of the RAM disk. |
||
firmware-download | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18 | |||
firmware-download-write-status-supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.1 |
This object provides information on whether the printer has the ability to communicate the write-status of the firmware download while the download is taking place. |
||
firmware-download-write-time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.2 |
If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. Additional information: If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. The calculated time is expected to be 140 secs. However, this time may increase as high as 280 secs as the flash part nears the maximum flash count. |
||
firmware-download-write-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.3 |
Tells the number of times that firmware has been downloaded to the flash part. Additional information: Tells the number of times that firmware has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping. |
||
firmware-download-current-state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.4 |
Provides the current or last reportable state of the firmware download process. The current state may not necessarily be the current state, but could be the post-mortem state. |
||
firmware-download-maximum-write-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.5 |
Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. Additional information: Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves. |
||
firmware-download-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.6 |
This returns the name of the printer. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with the name returned then the image that we are attempting to download does not upgrade the printer firmware. Additional information: This object returns the HP name of the printer. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer is available to be upgraded. |
||
firmware-download-version | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.7 |
This object will return a string value representing the current revision of firmware that the printer is operating with. This is used to determine if code needs to be upgraded when an firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This objects will return the version string of the printer. |
||
operating-system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.19 | |||
os-execute-file | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.19.1 |
This objects input is a null-terminated string representing a fully-qualified path name for an executable file. This object causes the file to be executed by the OS. Additional information: This objects input is a null-terminated string of two or more whitespace-separated tokens. The first token is a path to a directory to make the current working directory. The second token is a path to an executable file to be executed. Any remaining whitespace-separated tokens are optional and will be passed as parameters to the executable. The paths to the directory and executable can be either PJL style (e.g., 1:\app\example) or UNIX-style (e.g., /hpmnt/dsk_ide1a/app/example). The executable is run in a separate process. |
||
upgradable-devices | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20 | |||
upgradable-devices-write-status-supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.1 |
This object provides information on whether the upgradable device has the ability to communicate the write-status of the upgrade while the upgrade is taking place. |
||
upgradable-devices-write-time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.2 |
If the design of the device upgrade implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the device will not be able to engage in PML communication. The time returned will depend upon what device is attempting to be upgraded. |
||
upgradable-devices-write-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.3 |
Tells the number of times that firmware for device X has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping. |
||
upgradable-devices-current-state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.4 |
Provides the current or last reportable state of the device upgrade process. The current state may not necessarily be the current state, but could be the post-mortem state. |
||
upgradable-devices-max-write-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.5 |
Reports the manufacturer specified number of times that firmware for device X can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that the firmware for device X can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves. |
||
upgradable-devices-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.6 |
This returns the name of the upgradable device. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with any of the names returned then the device that we are attempting to upgrade is unavailable for upgrading. Additional information: This object returns the HP name of the printer and the upgradable devices. There is one Name object per upgradable device. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer or device is available to be upgraded. |
||
upgradable-devices-version | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.7 |
This object will return a string value representing the current revision of firmware that device X is operating with. This is used to determine if code needs to be upgraded when a firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This internal object will return the current version string of the printer or device that it corresponds to. |
||
remote-upgrade-enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.8 |
Enables or disables the ability to upgrade the firmware associated with any device that is available to be upgraded. This will be set to on or off at the RFU level in that if this mode is on any available device can be upgraded and if this mode is off none of the devices can be upgraded. There is not an individual mode for each device. Trying to set this to a value other than eOn or eOff will cause an UnsupportedValue error to occur. |
||
source-subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.2 | |||
io | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1 | |||
settings-io | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1 | |||
io-timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1.1 |
The amount of time, in seconds, to wait for more print job data to be received before an I/O timeout occurs. The I/O channel being timed is the I/O channel that received the data associated with the current print job. If an I/O timeout occurs, the PDL processing sub-system assumes all the data associated with the current print job has been received, and processes the end of job in a PDL specific manner. The POS specifies the supported values. Additional information: If an I/O timeout occurs,the PDL processing sub-system will consider it an end of job condition only if there is data from another I/O subsystem waiting to be processed. The supported values are 5 to 300 seconds. Setting to a value outside the supported range returns <noError> status and the value will be snapped to the nearest supported value. |
||
io-switch | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1.2 |
Indicates if the device will switch between I/O channels when a job boundary is encountered and print job data is available on another I/O channel. |
||
ports | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3 | |||
port1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1 | |||
port1-parallel-speed | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1.4 |
Returns or changes the maximum parallel I/O port speed, for port 1. This object is only supported if this port is a parallel port. An eSlow setting causes a 10 us busy pulse per received byte of data. An eFast setting causes a 1.5 us busy pulse per received byte of data. In rare cases, setting this value to eFast can cause the parallel port to no longer transfer data reliably. Additional information: When the value of this object is changed, it takes effect immediately. It is recommended that the printer be offline and not in a job when this object is changed. |
||
port1-parallel-bidirectionality | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1.5 |
Returns or changes whether the parallel I/O port supports bidirectional communication for port 1. This object is only supported if this port is a parallel port. Additional information: A get on this object returns the current mode for the parallel port. Setting this object specifies whether or not bidirectional communications will be allowed. |
||
scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2 | |||
settings-scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1 | |||
scanner-accessory-adf-sheet-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.20 |
Total number of sheets that have been fed through the Automatic Document Feed (ADF) accessory. Additional information: The Automatic Document Feed (ADF) count is incremented each time a sheet feeds through the ADF. The value will be updated at the end of every scan job. |
||
scanner-accessory-flatbed-scan-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.21 |
Total number of scans performed by a flatbed scanner accessory. Additional information: The count is only incremented when a sheet is scanned on the FLATBED. The return value of this object will reset to the lower multiple of 10 at a power cycle. The value will be updated at the end of every scan job. |
||
scanner-accessory-dimm1-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.55 |
This object returns an indication of the type of option installed in DIMM slot 1 of the copy processor board. eEmpty means the device did not detect any option installed in the interface slot. eUnknown means the device doesnt recognize the installed option. eUnSupported means the device recognizes the installed option, but does not support the option. eReadOnlyMemory means the installed option contains ROM Ics. eVolatileRandomAccessMemory means the installed option contains RAM ICs that loose data when the power is turned off. eFlashMemory means that the installed option contains a type of non-volatile RAM that needs to be erased before it can be written. eRamRom means the installed option contains both volatile random access memory and read only memory (combo SIMM/DIMM). |
||
scanner-accessory-dimm2-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.56 |
This object returns an indication of the type of option installed in DIMM slot 2 of the copy processor board. eEmpty means the device did not detect any option installed in the interface slot. eUnknown means the device doesnt recognize the installed option. eUnSupported means the device recognizes the installed option, but does not support the option. eReadOnlyMemory means the installed option contains ROM Ics. eVolatileRandomAccessMemory means the installed option contains RAM ICs that loose data when the power is turned off. eFlashMemory means that the installed option contains a type of non-volatile RAM that needs to be erased before it can be written. eRamRom means the installed option contains both volatile random access memory and read only memory (combo SIMM/DIMM). |
||
scanner-accessory-dimm1-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.57 |
Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SCANNER_ACCESSORY-DIMM1-TYPE type is eFlashMemory, eVolatileRandomAccessMemory, or eRamRom. For eRamRom only the size of the Ram portion of the DIMM is returned. |
||
scanner-accessory-dimm2-capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.58 |
Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SCANNER_ACCESSORY-DIMM2-TYPE type is eFlashMemory, eVolatileRandomAccessMemory, or eRamRom. For eRamRom only the size of the Ram portion of the DIMM is returned. |
||
scanner-accessory-adf-one-sided-sheet-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.59 |
This item is incremented by 1 for each sheet that is scanned through the ADF in 1-sided scan mode. Additional information: The value will be updated at the end of every scan job. |
||
scanner-accessory-adf-two-sided-sheet-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.60 |
This item is incremented by 2 for each sheet that is scanned through the ADF in 2-sided scan mode. Additional information: The value will be updated at the end of every scan job. |
||
scanner-accessory-copy-job-scan-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.61 |
This relates to the number of pages scanned for copying. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job. |
||
scanner-accessory-send-job-scan-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.62 |
This relates to the number of pages scanned for fax/send. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job. |
||
scanner-accessory-total-copy-pages-printed | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.63 |
This relates to the number of copy pages printed on a device. The output sheet that is duplexed (made 2- sided) should be counted as 2 pages. Additional information: The value will be updated at the end of every scan job. |
||
scanner-accessory-digital-send-module-url | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.64 |
This item sets the URL pointer to the Digital Send Module that is servicing this accessory. |
||
scanner-accessory-digital-send-status | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.65 |
This item is used for detecting the status of the Digital Send component. A bit-mask indicates the status as follows: 0x00 = READY 0x01 = DIGITAL_SEND_GATEWAY_DOWN 0x02 = SMTP_GATEWAY_DOWN 0x04 = LDAP_GATEWAY_DOWN. |
||
default-scan-original-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.66 |
Contains the default size of the original to be scanned. Additional information: Contains the default size of the original to be scanned. |
||
default-scan-text-graphics-mix | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.67 |
Contains the mix between graphics and text on the scanned page. |
||
default-scan-job-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.68 |
Allows user to continue scanning more pages. The UI will prompt user for more pages if job mode is on. |
||
default-scan-background-removal | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.69 |
Background level for background removal. Additional information: Background level for background removal. |
||
default-scan-image-quality | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.70 |
Select default image quality. Additional information: Which image quality to use. |
||
default-scan-content-orientation | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.71 |
Contains the default content orientation for a scanned document. Additional information: Contains the default content orientation for a scanned document, i.e., the orientation of the page as the user would read it. |
||
default-scan-heavy-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.72 |
Sets the default heavy media scan mode on or off. Additional information: Sets the default heavy media scan mode to on or off. |
||
status-scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.2 | |||
not-ready-source-scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.2.1 |
Indicates whether and why the scanner is not ready. A set bit indicates a problem. |
||
scan-calibration-download | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.2.5 |
Returns or changes the state of the calibration operation. cScanCalibrationIdle - This indicates that the device is not currently processing a calibration request. The host should not set the object to this state. SCAN-CALIBRATION-ERROR state will reflect results of most recent calibration. cScanCalibrationStart - This state is set by the host to request factory mechanical calibration initiation. Device should not set to this state. The device will ignore this request, without error, if it is already in the active or the cone state. cScanFactoryCalibrationStart - This state is set by the host to request factory optical calibration initiation. This is the old method and will not be used on Laserjet 4300 MFP. cScanCalibrationActive - The device sets this state to indicate it is in calibration mode. The device will set SCAN-CALIBRATION-ERROR to eNoError(1) as a consequence of entering this state. cScanCalibrationAborted - This bit is not used. cScanCalibrationDone - The device sets to this state when it has successfully completed a calibration. The device will update SCAN-CALIBRATION-ERROR object before entering this state. The device will exit from this state to cScanCalibrationIdle when it is ready to process another cScanCalibrationStart request. cScanCalibrationOptical - This state is set by the host to request factory optical calibration initiation. The device should not set to this state. The device will ignore this request, without error, if it is already in the active or the done state. cScanCalibrationADFMechanical - This state is set by the host to request factory ADF mechanical calibration initiation. The device should not set to this state. The device will ignore this request, without error, if it is already in the active or the done state. cScanCalibrationFBMechanical - This state is set by the host to request factory flat bed mechanical calibration initiation. The device should not set to this state. The device will ignore this request, without error, if it is already in the Active or the Done state. The device will NOT print a calibration graph when calibration is complete. Additional information: Returns or changes the state of the calibration operation. cScanCalibrationIdle - indicates that the device is not currently processing a calibration request. The host should not set the object to this state. SCAN-CALIBRATION-ERROR state will reflect results of most recent calibration. cScanCalibrationStart This state is set by host to request factory \ mechanical calibration initiation. Device should not set to this state. The device will ignore this request, without error, if it is already in the Active or the Done state. CScanFactoryCalibrationStart - This state is set by host to request factory optical calibration initiation. This is the old method and will not be used on Laserjet 4300 MFP. cScanCalibrationActive The device sets this state to indicate it is \ in calibration mode. The device will set SCAN-CALIBRATION-ERROR to eNoError(1) as a consequence of entering this state. cScanCalibrationAborted Not used. cScanCalibrationDone The device sets to this state when it has successfully completed a calibration. The device will update SCAN-CALIBRATION-ERROR object before entering this state. The device will exit from this state to cScanCalibrationIdle when it is ready to process another cScanCalibrationStart request. cScanCalibrationOptical - This state is set by host to request factory optical calibration initiation. Device should not set to this state. The device will ignore this request, without error, if it is already in the Active or the Done state. cScanCalibrationADFMechanical - This state is set by host to request factory ADF mechanical calibration initiation. Device should not set to this state. The device will ignore this request, without error, if it is already in the Active or the Done state. cScanCalibrationFBMechanical - This state is set by host to request factory flat bed mechanical calibration initiation. Device should not set to this state. The device will ignore this request, without error, if it is already in the Active or the Done state. The device will NOT print a calibration graph when calibration is complete. |
||
scan-calibration-error | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.2.6 |
Error status of the most recent calibration session. eNoError(1) - The calibation was successful. eUnknownCalibrationError(2) - An unknown error occurred. eScannerFeederEmpty(3) - The feeder contained nothing to scan. eLowMemory(4) - Insufficient memory available to complete the calibration. eWriteFailed(5) - Write to NVRAM failure. eScannerBusy(6) - Scanner is busy. Detailed information about the cause and remedy for each error should be documented in the device POS. Additional information: Error status of the most recent calibration session. Only eNoError, eScannerBusy, and eUncorrectablePixels will be supported. The device will use eScannerBusy to indicate the calibration request occurred during a time that the device was not ready to perform calibration. The device will use eUncorrectablePixels to indicate that at least one pixel was not correctable on at least one of scanning sensors in the device (ADF or flatbed). |
||
spooler | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.4 | |||
settings-spooler | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.4.1 | |||
mopy-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.4.1.1 |
Controls or reports how mopies are generated. eOff turns off the mopy feature. eAuto allows the device to determine the best method for generating mopies based on the device configuration. eStandard spools the I/O data and replays the I/O data multiple times to generate the mopies. eEnhanced spools the rasterized page images and replays the rasterized data to generate the mopies. Typically, the rasterized data will be larger and will allow all but the first mopy to print at speed. If the job being mopied is not extremely complex, then the first mopy will print at speed also. |
||
processing-subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.3 | |||
pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3 | |||
settings-pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1 | |||
default-copies | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.4 |
Returns or changes default copies. Default copies is the default values used by the PDL to control the number of copies of each page in the print job that are printed. The print job can override this value. The list of supported values should be documented in the device POS. Additional information: The supported values are 1 through 32000. Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snaps are as follows: <1 snaps to 1 >999 snaps to 32000 |
||
form-feed | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.5 |
Instructs the PDL processing sub-system to finishing processing the current page of the current job. Form feed is also known as close page or eject page. If the PDL processing sub-system is in a FORM-FEED-NEEDED state, this causes the device to flush or finish processing the current page of the current job. If the device is not in the FORM-FEED-NEEDED state, an <genErr> will occur. |
||
default-vertical-black-resolution | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.8 |
Returns or changes the value of the default vertical black resolution. The units are dots per inch. Additional information: In LaserJet 8100 changing this OID also causes DEFAULT-HORIZONTAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: LaserJet 4100: 300, 600, 1200 LaserJet 4550: 600 LaserJet 9000: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: LaserJet 4100: 450 >= n < 900 snaps to 600 n >= 900 snaps to 1200 LaserJet 4550: n snaps to 600 LaserJet 9000: n < 450 snaps to 300 n >=450 snaps to 600 |
||
default-horizontal-black-resolution | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.9 |
Returns or changes the value of the default horizontal black resolution. The units are dots per inch. Additional information: In LaserJet 8100 changing this object also causes DEFAULT-VERTICAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: LaserJet 4100: 300, 600, 1200 LaserJet 4550: 600 LaserJet 9000: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: LaserJet 4100: n < 450 snaps to 300 450 >= n < 900 snaps to 600 n >= 900 snaps to 1200 LaserJet 4550: n snaps to 600 LaserJet 9000: n < 450 snaps to 300 n >=450 snaps to 600 |
||
default-page-protect | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.10 |
Returns or changes the default page protection behavior. If eOff, the device does not reserve memory for holding the entire raster form of a processed page. If eOn, then memory is reserved. If eAuto, the device determines the amount of memory to reserve. Additional information: Setting to eOn causes MET to be more conservative, but it will not allocate memory to hold an entire rasterized page. |
||
default-lines-per-page | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.11 |
Returns or changes the default number of lines per page. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return the <noError>. Additional information: The supported values in LaserJet 8150 are 5 to 128. Setting to an unsupported value causes the the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: <5 snaps to 5 >128 snaps to 128 |
||
default-vmi | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.12 |
Returns or changes the default vertical motion index. The unit of measure for VMI is centipoints per line. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return <noError>. |
||
default-media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.13 |
This indicates the default media size. A write of an unsupported value causes an <ErrorInvalidOrUnsupported Value>. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. (for a full list of media size enums see the end of this file) |
||
cold-reset-media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.19 |
Returns or sets the media size that is used as the DEFAULT-MEDIA-SIZE when a cold reset occurs. |
||
default-media-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.22 |
Returns or sets the media name that is used until the media name is changed by a print job command. Additional information: Returns or sets the media name that is used until the media name is changed by a print job command. This string must be one of the MEDIAn-NAME objects. This object is localized if the corresponding MEDIAn-NAME object is localized. The data for this object is stored in NVRAM. |
||
reprint | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.36 |
Returns or changes the reprint (jam recovery) setting. If eOn, then the device will reprint pages jammed pages. If eOff, the device will not attempt to reprint jammed pages. If eAuto, a device dependent algorithm (which should be documented in the POS) will be used to determine if the page gets reprinted. This object controls all PDLs, unless a specific PDL supports its own reprint control mechanism. To date, only PostScript has a PDL reprint control mechanism. |
||
default-bits-per-pixel | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.39 |
Controls the number of levels used (per pixel) when printing grayscale or color images. |
||
status-pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.2 | |||
form-feed-needed | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.2.2 |
Indicates if the PDL processing sub-system has made marks on the current page and the source subsystem has been idle for a device specific amount of time. Additional information: LaserJet 8150 will set this object to eTrue when it has made marks on the current page, the IO-TIMEOUT has expired while PCL was running in `backward-compatibility mode (which is caused by jobs consisting purely of PCL data with no prepended PJL commands), and no data is pending on another I/O. Once it is set to eTrue, more data on the same I/O will cause this object to be set to eFalse, until the above conditions are met again. |
||
pdl-pcl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3 | |||
pcl-total-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.5 |
Total number of PCL pages printed by the device. Additional information: In LaserJet 8150 the PCL page count is kept in NVRAM, and the NVRAM value is updated at least every 10 pages. NOTE: The value returned by this object will be incremented every page but if power is lost between NVRAM updates, up to 9 pages of the page count may be lost. The page count counter will be reset to zero after 16,777,215 (2^24-1) pages. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by two. |
||
pcl-default-font-height | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.13 |
Returns or changes the default PCL height. Height is an approximate measure of the body of the type in centipoints. A centipoint is 1/7200 inch. Height applies only to proportional fonts. Point size, in points, can be converted to font height, in centipoints, by multiplying the point size by 100. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return <noError>. Closest means the smallest absolute difference. Additional information: Supported values range from 400 to 99975, in increments of 25 units. Setting to an unsupported value causes the printer to substitute in a snap value and to return <noError> status. The snap values are as follow: <=400 snaps to 400 >=99975 snaps to 99975 Unsupported values in the range 400 to 99975 snap DOWN to the previous supported value (i.e 25293 snaps to 25275 or 75038 snaps to 75025). |
||
pcl-default-font-source | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.14 |
Returns or changes the value of the default font source variable in NVRAM. |
||
pcl-default-font-number | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.15 |
Returns or changes the value of the default font number variable in NVRAM. Writing an unsupported value causes the printer to generate an <badValue>. Additional information: Valid numbers or 0 - 255, but only font numbers that are included in the PCL FONT LIST are selectable. |
||
pcl-default-font-width | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.16 |
Returns or changes the default PCL font width. Width is expressed as the width of a character in centipoints. A centipoint is 1/7200 inch. Width applies only to fixed space fonts. Pitch, in character per inch, can be converted to font width, in centipoints, by dividing 7200 by the pitch. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return <noError>. Closest means the smallest absolute difference. Additional information: Setting to an unsupported value causes the printer to substitue in a snap value (listed below) and return <noError> status. The snap values for pitch are as follow: <=44 snaps to 44 >=9999 snaps to 9999 |
||
pdl-postscript | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4 | |||
postscript-total-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4.5 |
Total number of PostScript pages printed by the device. Additional information: This object is only supported if the PostScript option is installed. In LaserJet 8150 the count is kept in NVRAM, and the NVRAM value is updated at least every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages. |
||
postscript-print-errors | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4.11 |
Returns or changes the value of the print PostScript errors setting. If eOn, PostScript prints an error page showing the error encountered and the stack at the time of the error. Additional information: This object is only supported if the PostScript option is installed. |
||
pjl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.5 | |||
destination-subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.4 | |||
print-engine | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1 | |||
settings-prt-eng | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1 | |||
override-media-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.2 |
Sets a string identifying the media name that is to be used in place of the currently requested media. The substitution will continue until another media is selected. If set to a named media that is not currently available the requested media is not overridden. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired media name as set by the print job. This object should be set to a media name that is currently available in the printer. If a paper mount request is not pending, attempting to get or set this object will cause <noSuchName> to be returned. Setting this object to a string other than one of the MEDIAn-NAME objects (MEDIA-NAMES-AVAILABLE is applied) will cause a status of <badValue> to be returned. |
||
override-media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.3 |
Sets the media size that is to be used in place of the currently requested media size. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired size as set by the print job. This object should be set to a media size that is currently available to the printer. If a paper mount request is not pending, attempting to get or set this object will cause <noSuchName> to be returned. |
||
print-density | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.5 |
Returns or sets the print density setting. Print density is the instantaneous amount of marking agent applied to the paper while printing. A value of zero has the lowest print density, yielding a lighter page. A value of 10 has the highest print density, yielding a darker page. Each POS should document what values in the 0 to 10 range are supported. Additional information: When this value is written, the page pipeline will be flushed (all pages being printed are completed, no new ones are started), the new density setting is set and printing resumes. The acutal change in print density may be gradual over several pages. The supported values are 1 through 5. Setting to an unsupported value causes the printer to substitue in a a snap value and to return <noError> status. The snap values are as follows: <1 snaps to 1 >5 snaps to 5. |
||
marking-agent-density | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.9 | |||
marking-agent-density-setting | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.9.1 |
Returns or sets the marking agent density setting for each of the marking agents installed. The Marking Agent (aka Print) density is the instantaneous amount of marking agent applied to the media while printing. A value of zero has the lowest print density, yielding a lighter page. A value of 10 has the highest print density, yielding a darker page. The device POS will document what values are supported. Additional information: Returns or sets the print density setting. Print density is the instantaneous amount of marking agent applied to the paper while printing. A value of zero has the lowest print density, yielding a lighter page. A value of 10 has the highest print density, yielding a darker page. |
||
autocleaning-page-enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.10 |
When set to eEnabled this object will enable the periodic printing of a page designed to clean the fuser on an EP printing system. The interval between cleaning pages is determied by the setting of the AUTOCLEANING-PAGE-FREQUENCY object and the media size is determined by the AUTOCLEANING-PAGE-SIZE object. This object could also be used in the future to clean the inkjet heads on an inkjet system. Additional information: When set to eEnabled this object will enable the periodic printing of a page designed to clean the fuser on an EP printing system. The interval between cleaning pages is determied by the setting of the AUTOCLEANING-PAGE-FREQUENCY object and the media size is determined by the AUTOCLEANING-PAGE-SIZE object. This object could also be used in the future to clean the inkjet heads on an inkjet system. |
||
autocleaning-page-frequency | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.11 |
Controls the number of pages between printing of the auto cleaning page (if enabled). Any device specific snap behavior for this page interval will be specified in the device pos. Additional information: Controls the number of pages between printing of the auto cleaning page (if enabled). The legal values are 1000, 2000, 5000, 10000, and 20000. All other values will return OK_NEAREST_LEGAL_VALUE_SUBSTITUTED. |
||
autocleaning-page-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.12 |
Controls the size of paper used to print the auto cleaning page (if enabled). Additional information: Controls the size of paper used to print the auto cleaning page (if enabled). |
||
default-audible-feedback | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.14 |
Returns or sets the audible feedback function. The default value will be documented in the device POS. Additional information: Turns the audible feedback function on or off |
||
default-reset-send-timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.15 |
Returns or sets the period of time, specified in milliseconds, to wait before the digital send settings are reset to default values. The default will be specified in the device POS. Additional information: Contains the period, in milliseconds, of inactivity on the control panel before the digital send settings are reset to their default values. |
||
default-authentication-timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.16 |
Returns or sets the period of time, specified in milliseconds, to wait before an authentication becomes invalid. The default will be specified in the device POS. Additional information: Contains the period, in milliseconds, of inactivity on the control panel before the authentication becomes invalid. |
||
default-staple-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.17 |
Returns or sets the default staple mode. The device POS will specify the default and supported values. Additional information: Selects staple mode. |
||
status-prt-eng | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2 | |||
duplex-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.22 |
Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. The POS will indicate if the value is kept in NVRAM. Additional information: Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. This value is kept in NVRAM however the NVRAM value is only updated every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages. |
||
print-engine-revision | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.26 |
Print engine revision string. Additional information: Print engine revision string. The symbol set for this string is Roman-8. |
||
intray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3 | |||
settings-intray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1 | |||
input-tray-auto-select | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.2 |
Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray. Additional information: Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray. |
||
custom-paper-feed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.8 |
Sets the printers custom paper dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers custom paper dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of prtInputDimUnit. The valid range is engine-dependent and should be documented in the POS for each product. |
||
custom-paper-xfeed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.9 |
Sets the printers custom paper dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers custom paper dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of prtInputDimUnit. The valid range is engine-dependent and should be documented in the POS for each product. |
||
default-custom-paper-dim-unit | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.10 |
The units of measure used to specify the width and height of the printers default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches. Additional information: The units of measure used to specify the width and height of the printers default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches. |
||
default-custom-paper-feed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.11 |
Sets the printers default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. |
||
default-custom-paper-xfeed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.12 |
Sets the printers default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printers default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. |
||
input-tray-max-media-feed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.14 |
The maximum physical media size in the feed direction of this input device expressed in units of measure specified by INPUT- TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The maximum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
||
input-tray-max-media-xfeed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.15 |
The maximum physical media size across the feed direction of a particular input device expressed in units of measure specified by INPUT-TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The maximum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, f or more details in the original format of the Standard Printer MIB. |
||
input-tray-min-media-feed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.16 |
The minimum physical media size in the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The minimum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
||
input-tray-min-media-xfeed-dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.17 |
The minimum physical media size across the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Additional information: The minimum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies unlimited, a value of (-2) implies unknown. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
||
intrays | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3 | |||
intray1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1 | |||
tray1-media-size-loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1.1 |
Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. Additional information: Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the Media Size Table near the end of this document. |
||
tray1-phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1.12 |
Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
||
outbin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4 | |||
settings-outbin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.1 | |||
overflow-bin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.1.4 |
Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. Additional information: Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. The data for this object is stored in NVRAM. |
||
outbins | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3 | |||
outbin1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1 | |||
outbin1-override-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1.9 |
Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
||
imaging | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.6 | |||
default-ret | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.6.5 |
Returns or changes the Resolution Enhancement Technology setting. Devices that only support eOff and eOn should map all other values to eOn and always return the same non-eOff value to indicate on. The list of supported values should be documented in the device POS. Additional information: Setting this object may cause a status of <noError> to be returned, but the new value will not take effect until a job boundary is reached. If a get is done on object before the job boundary is reached, the value last set will be returned. The value of this object is saved over a powercycle. This object exists on monochrome printers only. |
||
default-print-quality | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.6.7 |
Returns or sets the default print quality. A value of zero has the lowest print quality. A value of 100 has the highest print quality. Each POS should document what values in the 0 to 100 range are supported. Additional information: In LaserJet 8100, the supported values are 0 and 100. A value of zero has the lowest print quality(ECONOMODE=ON), thus minimizes the amount of toner used to print a page. A value of 100 has the highest print quality (ECONOMODE=OFF), thus uses more toner to print a page. Setting to an unsupported value outside of the 0 to 100 range causes the printer to return <badValue> status. Setting to an unsupported value inside of the 0 to 100 range causes the printer to substitute in a snap value (listed below) and to return <noError> status. The snap values are as follow: 0 to 50 snap to 0 51 to 100 snap to 100 This object exists on monochrome printers only. |
||
print-media | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8 | |||
settings-print-media | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1 | |||
media-names-available | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1.1 |
The value of this object controls which of the MEDIAx-NAME objects are supported. If a bit is set to zero, then attempting to get or set the corresponding MEDIAx-NAME objects will return <noSuchName>. Additional information: Setting a bit to one will cause the corresponding MEDIAn- objects to be available (attempting to access an unavailable object will return <noSuchName>). MEDIA1- objects are always present, as this is the default media. If this object is set to a value that does not include cMediaName2Available, that bit will be set and a status of <noError> will be returned. |
||
north-edge-offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1.2 |
Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the observer. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the ob server. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. The value of this object is stored in NVRAM. |
||
media-info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3 | |||
media1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1 | |||
media1-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.1 |
Media 1 name. Additional information: The symbol set for this string is Roman-8. |
||
media1-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.2 |
Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the devices control panel. The device POS must state the maximum number of characters allowed. If the device also has a limitation on what characters in a character set can be used (e.g. only uppercase characters allowed), the POS should also state character restrictions. Additional information: Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the devices control panel. The maximum supported string length is 9 characters. If the user entered string is too long, the device will store the first 9 characters and will return the <noError> status. The characters must be in the range 20H to 7FH except 5C cannot be used. The default symbol set is Roman-8 for English; additional legal symbol sets are ISOLatin5, ISOLatin2 and Windows31J. Setting this object with characters outside of the range or of an illegal symbol set will cause an error status of <badValue> to be returned. This string is localized according to prtConsoleLocalization. If this object represents a standard type, and the user attempts to set the object, OK Nearest Legal Value Substituted will be returned, and the standard value is retained. If this object represents a user defined type, and the user attempts to set the object, then the set will be successfull. |
||
media1-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.3 |
Number of sheets of media 1 that have been printed. The device POS should state whether this value is lost across a power cycle or kept in NVRAM. Additional information: Number of sheets of media 1 that have been printed. This page count is saved in NVRAM after every 10 pages. The maximum value is 4,294,967,295 which will never be reached in normal operation. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by one. |
||
media1-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: The engine processing characteristics that are to be applied to this media type. Currently, engine processing characteristics denotes changes to fusing temperature and/or transfer roller voltage. The data for this object is stored in NVRAM. |
||
media2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2 | |||
media2-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.1 |
Media 2 name. Additional information: See MEDIA1-NAME. |
||
media2-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.2 |
Length restricted version of the media name 2. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media2-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.3 |
Number of sheets of media 2 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media2-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3 | |||
media3-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.1 |
Media 3 name. Additional information: See MEDIA1-NAME. |
||
media3-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.2 |
Length restricted version of the media name 3. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media3-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.3 |
Number of sheets of media 3 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media3-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4 | |||
media4-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.1 |
Media 4 name. Additional information: See MEDIA1-NAME. |
||
media4-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.2 |
Length restricted version of the media name 4. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media4-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.3 |
Number of sheets of media 4 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media4-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5 | |||
media5-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.1 |
Media 5 name. Additional information: See MEDIA1-NAME. |
||
media5-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.2 |
Length restricted version of the media name 5. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media5-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.3 |
Number of sheets of media 5 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media5-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6 | |||
media6-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.1 |
Media 6 name. Additional information: See MEDIA1-NAME. |
||
media6-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.2 |
Length restricted version of the media name 6. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media6-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.3 |
Number of sheets of media 6 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media6-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7 | |||
media7-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.1 |
Media 7 name. Additional information: See MEDIA1-NAME. |
||
media7-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.2 |
Length restricted version of the media name 7. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media7-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.3 |
Number of sheets of media 7 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media7-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8 | |||
media8-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.1 |
Media 8 name. Additional information: See MEDIA1-NAME. |
||
media8-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.2 |
Length restricted version of the media name 8. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media8-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.3 |
Number of sheets of media 8 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media8-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9 | |||
media9-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.1 |
Media 9 name. Additional information: See MEDIA1-NAME. |
||
media9-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.2 |
Length restricted version of the media name 9. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media9-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.3 |
Number of sheets of media 9 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media9-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10 | |||
media10-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.1 |
Media 10 name. Additional information: See MEDIA1-NAME. |
||
media10-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.2 |
Length restricted version of the media name 10. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media10-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.3 |
Number of sheets of media 10 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media10-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11 | |||
media11-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.1 |
Media 11 name. Additional information: See MEDIA1-NAME. |
||
media11-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.2 |
Length restricted version of the media name 11. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media11-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.3 |
Number of sheets of media 11 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media11-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12 | |||
media12-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.1 |
Media 12 name. Additional information: See MEDIA1-NAME. |
||
media12-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.2 |
Length restricted version of the media name 12. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media12-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.3 |
Number of sheets of media 12 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media12-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13 | |||
media13-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.1 |
Media 13 name. Additional information: See MEDIA1-NAME. |
||
media13-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.2 |
Length restricted version of the media name 13. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media13-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.3 |
Number of sheets of media 13 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media13-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14 | |||
media14-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.1 |
Media 14 name. Additional information: See MEDIA1-NAME. |
||
media14-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.2 |
Length restricted version of the media name 14. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media14-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.3 |
Number of sheets of media 14 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media14-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15 | |||
media15-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.1 |
Media 15 name. Additional information: See MEDIA1-NAME. |
||
media15-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.2 |
Length restricted version of the media name 15. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media15-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.3 |
Number of sheets of media 15 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media15-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16 | |||
media16-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.1 |
Media 16 name. Additional information: See MEDIA1-NAME. |
||
media16-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.2 |
Length restricted version of the media name 16. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media16-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.3 |
Number of sheets of media 16 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media16-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media17 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17 | |||
media17-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.1 |
Media 17 name. Additional information: See MEDIA1-NAME. |
||
media17-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.2 |
Length restricted version of the media name 17. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media17-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.3 |
Number of sheets of media 17 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media17-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media18 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18 | |||
media18-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.1 |
Media 18 name. Additional information: See MEDIA1-NAME. |
||
media18-short-name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.2 |
Length restricted version of the media name 18. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
||
media18-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.3 |
Number of sheets of media 18 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
||
media18-engine-media-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.4 |
The engine processing characteristics that are to be applied to this media. The processing characteristics are device specific. Additional information: See the description for MEDIA1-ENGINE-MEDIA-MODE. |
||
media-modes | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.4 | |||
engine-media-modes-supported1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.4.1 |
The list of engine media modes supported by the device. The modes are each separated by a comma character. An example string would be: Normal,Rough,Low,Vellum. Additional information: The list of engine media modes supported by the device. The modes are each separated by a comma character. An example string would be: Normal,Rough,Low,Vellum. |
||
media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5 | |||
media-size-west-edge-first-side-offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.2 |
Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the first printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the first printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. The values in the sub array index are from the media size table in the hpmib. This adjustment is done on a paper size by paper size basis. The standard PCL5 codes for paper size are used for the value used in the OID. Please see S_ARRAY_SUB1 for legal |
||
media-size-west-edge-second-side-offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.3 |
Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the second printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the second printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. The values in the sub array index are from the media size table in the hpmib. This adjustment is done on a paper size by paper size basis. The standard PCL5 codes for paper size are used for the value used in the OID. Please see S_ARRAY_SUB1 for legal values. The data for this object is stored in NVRAM. |
||
media-size-west-edge-side-offset-by-tray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.4 |
Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Each OID binding corresponds to a valid tray number for this product. There can be a maximum of 15 trays, a combination of internal and external trays. Products that support other combinations of trays will specify this information in the device pos. The data for this object is stored in NVRAM. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Each OID binding corresponds to a valid tray number for this product. There can be a maximum of 15 trays, a combination of internal and external trays. Products that support other combinations of trays will specify this information in the device pos. The data for this object is stored in NVRAM. |
||
media-counts | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.7 | |||
non-assured-oht-page-count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.7.1 |
This is a count of the number of invalid (non-HP Laser Jet) transparencies that have been printed on. This value is incremented every time an invalid OHT is printed on It is reset whenever the fuser count is set to 0. Additional information: This is a count of the number of invalid (non HP Laser Jet) transparencies that have been printed on. This value is incremented every time an invalid OHT is printed on. It is reset whenever the fuser count is set to 0. |
||
media-types | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.8 | |||
media-number-of-type-supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.8.1 |
Indicates the maximum number of supported media types. Additional information: Indicates the number of supported media type. This also indicates which bit in MEDIA-NAMES-AVAILABLE is significant |
||
copier | 1.3.6.1.4.1.11.2.3.9.4.2.1.5 | |||
settings-copier | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1 | |||
default-copier-media-size | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.9 |
Sets the default copy paper size. The device will scan and format the print data based on the value of this object. The device behavior when the scanned media or print media does not match the value of this object should be documented in the device POS. (for a full list of media size enums see the end of this file) |
||
default-copier-image-type | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.10 |
Specifies the dither matrix used when performing a copy operation. |
||
default-copy-duplex-mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.28 |
Returns or sets the duplex copying mode. Duplex printing is when printing occurs on both sides of a sheet of media. Long edge binding is also called vertical binding or book binding. Short edge binding is also called horizontal binding or calendar binding. eSimplexToSimplex: takes image data from only one side of the original document, and print only on one side of each copy. eSimplexToDuplexLongEdgeBinding: takes image data from only one side of the original document, and print to both sides of each copy. The images are rotated so that if the media is rotated along the axis of the long edge of the media, both images would appear as in the original. eSimplexToDuplexShortEdgeBinding: takes image data from only one side of the original document, and print to both sides of each copy. The images are rotated so that if the media is rotated along the axis of the short edge of the media, both images would appear as in the original. eDuplexToDuplex: takes image data from both sides of the original document, and print on both sides of each copy. eDuplexToSimplexLongEdgeBinding: takes image data from both sides of the original document, and prints to only one side of each copy. The images are rotated so that if the media is rotated along the axis of the long edge of the media, both images would appear as in the original. eDuplexToSimplexShortEdgeBinding: takes image data from both sides of the original document, and prints to only one side of each copy. The images are rotated so that if the media is rotated along the axis of the short edge of the media, both images would appear as in the original. |
||
default-copy-input-tray | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.29 |
This describes the default input tray to be used. The correspondence between enumerated values and actual trays is device defined (and device dependent). The supported writable enumerated values are device specific. |
||
default-copy-output-bin | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.30 |
This describes the default output bin to be used. The correspondence between enumerated values and actual bins is device defined (and device dependent). The supported writable enumerated values are device specific. |
||
default-copy-reset-timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.31 |
The time, in seconds, that the printer will wait before automatically reverting to default copy settings. Additional information: This value is saved over a powercycle. |
||
default-copier-quantity | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.32 |
This item configures the default copy quantity. Additional information: This value is saved over a powercycle. |
||
default-copier-flip-pages-up | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.33 |
This item configures the default for the copy flip-pages-up status. |
||
default-copier-pages-per-sheet | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.34 |
Selects a special digital copier mode as follows: eNone: This is the normal copy mode, which means none of the special features are in effect. eTwoUp : Scans in 2 pages and produces 2 rotated images on a single output page. eFourUpNOrder : Scans in 4 pages and produces 4 scaled down images on a single output page. Images are placed in top down, left to right order. eFourUpZOrder : Scans in 4 pages and produces 4 scaled down images on a single output page. Images are placed in left to right, top down order. |
||
default-copier-page-borders | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.35 |
Selects a page boarder mode as follows: eNone : This is the normal copy mode, which no boarder is drawn. eLine : A simple border box is drawn around each scanned image. |
||
default-copier-collate | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.36 |
This describes the default setting used to stack the output of a set of copies. eCollate : Copies are stacked 1st page of 1st copy, 2nd page of 1st copy, 3rd page of 1st copy, etc. eUncollate: Copies are stacked 1st page of 1st copy, 1st page of 2nd copy, 1st page of 3rd copy, etc. |
||
default-copier-contrast | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.37 |
This item configures the default Intensity (brightness/contrast) setting. The number of discrete units should be application dependent. |
||
default-copier-edge-to-edge | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.38 |
This item configures the default edge-to-edge setting for copy jobs. |
||
copy-job-scan-ahead | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.39 |
When eOn, this implements the no-wait scanning feature. Originals are scanned to disk while waiting for the printer to become available. Default is eOn. |
||
copy-job-auto-interrupt | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.40 |
When eOn, a walk-up job will automatically interrupt an already-printing mopy jobat a mopy boundary. Default is eOff. |
||
copy-job-interrupt-copy-jobs | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.41 |
When eOn, this prompts the user whether to interrupt an already-printing copy job when a new copy job is started. Default is eOff. |
||
copy-job-hold-off-print-jobs | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.42 |
Controls whether new or pending print jobs can begin while a walk-up user is setting up a job. That is, for copy jobs and scan jobs, when eOn this prevents print jobs from starting while a walk-up user is setting up a job. Default is eOn. |
||
copy-job-hold-time | 1.3.6.1.4.1.11.2.3.9.4.2.1.5.1.43 |
Prevents non-copy print jobs from starting for specified interval after copy job is completely printed. Defined in seconds. |
||
channel | 1.3.6.1.4.1.11.2.3.9.4.2.1.6 | |||
channelnumberofchannels | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.1 |
An indication of how many print data channels the I/O card supports. Additional information: This object is used by the IIO card to tell the peripheral firmware how many logical channels will be used by the card. This object can only be set once per physical channel. If an attempt is made to set it a subsequent time it is ignored and an return code of <ErrorActionCanNotBePerformedNow.is returned. If new firmware is dynamically downloaded to the Blazers Plus card, and if that firmware uses more logical channels, it is necessary to reset the printer. |
||
channelprinteralert | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.2 |
Identifies the values of prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, and prtAlertCode for the latest critical evnet in the prtAlertTable. The binary string is defined as following: <table> ----------------------------------------------------- Field | Filed | Description Offset | Length | ----------------------------------------------------- 0 | 4 | the value of prtAlertIndex 4 | 4 | the value of prtAlertSeverityLevel 8 | 4 | the value of prtAlertGroup 12 | 4 | the value of prtAlertGroupIndex 16 | 4 | the value of prtAlertLocation 20 | 4 | the value of prtAlertCode ------------------------------------------------------ </table> Each field is in Big Endian style. Additional information: This object is used to pass alert information from the peripheral to the IIO card. The standard printer MIB contains the following description: printerAlert TRAP-TYPE ENTERPRISE printerV1Alert VARIABLES { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, prtAlertCode } DESCRIPTION This trap is sent whenever a critical event is added to the prtAlertTable. In order to provide this information in the trap packet, the IIO card enables traps on channelPrinterAlert. When a critical alert is generated the peripheral fills the appropriate value into this object and sends it to the card. This object is a structure which contains 24 bytes of data. The structure is: struct structAlertInfo { sint32 prtAlertIndex; sint32 prtAlertSeverityLevel; sint32 prtAlertGroup; sint32 prtAlertGroupIndex; sint32 prtAlertLocation; sint32 prtAlertCode; } thisAlertData; |
||
channelTable | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3 | |||
1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1 | ||||
channeltype | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.2 |
Identifies the type of MIO print data channel. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the type of each of the channels. The type information is passed using the channelType object. Values are then saved by the peripheral and reported when users request the value of prtChannelType. |
||
channelprotocolversion | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.3 |
The version of the protocol used on this MIO print data channel. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the protocol version of each of the channels. The protocol version information is passed using the channelProtocolVersion object. Values are then saved by the peripheral and reported when users request the value of prtChannelProtocolVersion. |
||
channelstate | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.4 |
The state of this print data channel. The value determines whether control information and print data is allowed through this channel or not. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the state of each of the channels. The state can change from time to time. The state information is passed using the channelState object. Values are saved by the peripheral and reported when users request the value of prtChannelState. |
||
channelifindex | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.5 |
The value of ifIndex which corresponds to this channel. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the value of the IfIndex for each channel. The IfIndex is used as part of MIB-II. The values are saved by the peripheral and reported when users request the value of prtChannelIfIndex. |
||
channelstatus | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.6 |
Sub-unit status is reported in the entries of the principle table in the Group that represents the sub-unit. For sub-units that report a status, there is a status column in the table and the value of this column is always an integer formed in the following way. The SubUnitStatus is an integer that is the sum of 5 distinct values, Availability, Non-Critical, Critical, On-line, and Transitioning. These values are: Availability value Available and Idle 0 000b Available and Standby 2 010b Available and Active 4 100b Available and Busy 6 110b Unavailable and OnRequest 1 001b Unavailable because Broken 3 011b Unknown 5 101b Non-Critical No Non-Critical Alerts 0 Non-Critical Alerts 8 Critical No Critical Alerts 0 Critical Alerts 16 On-Line Intended state is On-Line 0 Intended state is Off-Line 32 Transitioning At intended state 0 Transitioning to intended state 64. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the status of each of the channels. The status can change from time to time. The status information is passed using the channelStatus object. Values are saved by the peripheral and reported when users request the value of prtChannelStatus. |
||
channelinformation | 1.3.6.1.4.1.11.2.3.9.4.2.1.6.3.1.7 |
Auxiliary information to allow a printing application to use the channel for data submission to the printer. An application capable of using a specific PrtChannelType should be able to use the combined information from the prtChannelInformation and other channel and interface group objects to bootstrap its use of the channel. prtChannelInformation is not intended to provide a general channel description, nor to provide information that is available once the channel is in use. The encoding and interpretation of the prtChannelInformation object is specific to channel type. The description of each prtChannelType enum value for which prtChannelInformation is defined specifies the appropriate encoding and interpretation, including interaction with other objects. For channel types that do not specify a prtChannelInformation value, its value shall be null (0 length). When a new prtChannelType enumeration value is registered, its accompanying description must specify the encoding and interpretation of the prtChannelInformation value for the channel type. prtChannelInformation semantics for an existing PrtChannelType may be added or amended in the same manner as described in section 2.4.1 for type 2 enumeration values. The prtChannelInformation specifies values for a collection of channel attributes, represented as text according to the following rules: 1. The prtChannelInformation is coded in the NVT ASCII character set. It is not affected by localization. 2. The prtChannelInformation is a list of entries representing the attribute values. Each entry consists of the following items, in order: a. a keyword, composed of alphabetic characters (A-Z, a-z), that identifies a channel attribute, b. an Equals Sign (=) to delimit the keyword, c. a data value, consisting of NVT ASCII graphics characters (codes 32-126), d. a Line Feed character (code 10) to delimit the data value. No other characters shall be present. Keywords are case-sensitive. Conventionally, keywords are capitalized (including each word of a multi-word keyword), and, since they occupy space in the prtChannelInformation, they are kept short. 3. If a channel attribute has multiple values, it is represented by multiple entries with the same keyword, each specifying one value. Otherwise, there shall be at most one entry for each attribute. 4. By default, entries may appear in any order. If there are ordering constraints for particular entries, these must be specified in their definitions. 5. The prtChannelInformation value may represent information that is not normally coded in textual form, or that is coded in a character set other than NVT ASCII. In these cases, whatever symbolic representation is conventionally used for the information should be used for encoding the prtChannelInformation. (For instance, a binary port value might be represented as a decimal number, Unicode would be represented in UTF-8 format.) 6. For each PrtChannelType for which prtChannelInformation entries are defined, the descriptive text associated with the PrtChannelType enumeration value shall specify the following information for each entry: Title: Brief description phrase, e.g.: Port name,Service Name, Keyword: The keyword value, eg: Port, Service Syntax: The encoding of the entry value, if it cannot be directly represented by NVT ASCII, Status: Mandatory, Optional, or Conditionally Mandatory, Multiplicity: Single or Multiple, to indicate whether the entry may be present multiple times, Description: Description of the use of the entry, other information required to complete the definition (e.g.: ordering contstraints, interactions between entries). Applications that interpret prtChannelInformation should ignore unrecognized entries, so they are not affected if new entry types are added. Additional information: After telling the peripheral how many logical channels will be used, the IIO card tells the printer the value of the information value of each of the channels. The information is auxiliary information used in conjunction with the channel Type. |
||
tables | 1.3.6.1.4.1.11.2.3.9.4.2.1.7 | |||
deviceChannelTable | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2 | |||
1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1 | ||||
channel-bytes-sent | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1.2 |
The low order 31 bits of the number of bytes sent from the printer to the host on this logical channel. |
||
channel-bytes-received | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1.3 |
The low order 31 bits of the number of bytes received by the printer from the host on this logical channel. |
||
channel-io-errors | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1.4 |
The low order 31 bits of the number of I/O errors which have occured on this logical channel. |
||
channel-jobs-received | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1.5 |
The low order 31 bits of the number of print jobs which have been received on this logical channel. |
||
channel-mio | 1.3.6.1.4.1.11.2.3.9.4.2.1.7.2.1.6 |
The number of the MIO card associated with this logical channel. If this logical channel is not associated with an MIO card a zero is returned. The value returned for each logical channel is the MIO cards physical slot number. The list of supported values should be documented in the device POS. Additional information: The value returned will be zero for channels 1..3. If an MIOA card is installed, channels 4..10 will return a value of one or two. If an MIOB card is installed, channels 11..17 will return a value of one or two but not the same as channels 4..10. When two IIO cards are installed, the value returned by any channel 4..17 may change after the printer is power cycled. |