Also known as K Mem Emulation, this client is used to store any
optional or loadable emulations, such as LN03 Plus or QUIC II.
Increasing this client's memory allows you to load more than one
optional emulation so that it doesn't have to be reloaded every time
the print job is sent.
If an emulation is loaded to process a print job and there is not
enough memory in the emulation client, another emulation already
loaded may be unloaded automatically to obtain enough memory. If
you notice a delay in printing between jobs that have different nonres-
ident emulations, it's possible that the emulations are having to reload
each time they're run. Adding to the emulation client may eliminate
the unloading and reloading of these emulations and, consequently,
increase throughput. It is recommended that you should add at least
1 MB of physical RAM to your printer and increase this memory client
by 1 MB for each additional emulation loaded. If your printer has an
optional hard disk and the disk swapping option is turned on then you
can increase the emulation memory client using this memory.
Size is returned in Kilobytes.
Note: You should add at least 1 MB to the emulation memory client for
each loadable emulation that your printer uses. Failure to add
memory to this client may prevent the printer from loading and using
the emulation. You should check the documentation accompanying
your loadable emulation for information on additional resource
requirements.
Also increase the emulation client if you're printing complex non-Post-
Script jobs that may require more memory to process correctly.
Parsed from file QMS-MIB.mib
Module: QMS-MIB
Vendor: QMS, Inc.
Module: QMS-MIB
[Automatically extracted from oidview.com]
qmsClientEmulation OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Also known as K Mem Emulation, this client is used to store any optional or loadable emulations, such as LN03 Plus or QUIC II. Increasing this client's memory allows you to load more than one optional emulation so that it doesn't have to be reloaded every time the print job is sent. If an emulation is loaded to process a print job and there is not enough memory in the emulation client, another emulation already loaded may be unloaded automatically to obtain enough memory. If you notice a delay in printing between jobs that have different nonres- ident emulations, it's possible that the emulations are having to reload each time they're run. Adding to the emulation client may eliminate the unloading and reloading of these emulations and, consequently, increase throughput. It is recommended that you should add at least 1 MB of physical RAM to your printer and increase this memory client by 1 MB for each additional emulation loaded. If your printer has an optional hard disk and the disk swapping option is turned on then you can increase the emulation memory client using this memory. Size is returned in Kilobytes. Note: You should add at least 1 MB to the emulation memory client for each loadable emulation that your printer uses. Failure to add memory to this client may prevent the printer from loading and using the emulation. You should check the documentation accompanying your loadable emulation for information on additional resource requirements. Also increase the emulation client if you're printing complex non-Post- Script jobs that may require more memory to process correctly." ::= { qmsMemory 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.480.1.5.1 | qmsMEMPhysical | 0 | 0 | Size of the physical memory in MB. |
| 1.3.6.1.4.1.480.1.5.2 | qmsMEMTotal | 0 | 0 | Size of the total virtual memory in MB. Note: If no hard disk is installed, this will be the size of physical memory. |
| 1.3.6.1.4.1.480.1.5.3 | qmsClientSystem | 0 | 0 | Also known as System Use, this non-configurable client is the amount of RAM used to run the printer's operating system. It's nev… |
| 1.3.6.1.4.1.480.1.5.4 | qmsClientSpool | 0 | 0 | Also known as Host Input and K Mem for Spool, this memory client stores incoming data from all the interfaces until the emulatio… |
| 1.3.6.1.4.1.480.1.5.6 | qmsClientHeap | 0 | 0 | Also known as K Mem PSHeap, Heap, PostScript VM, and Virtual Memory, this client holds downloaded fonts, PostScript operators, a… |
| 1.3.6.1.4.1.480.1.5.7 | qmsClientFontCache | 0 | 0 | Also known as K Mem PS Fonts and Font Cache, this memory client stores bitmapped representations of previously scaled PostScript… |
| 1.3.6.1.4.1.480.1.5.8 | qmsClientDisplayList | 0 | 0 | Also known as K Mem Display, this client stores compressed repre- sentations, or blocks, of the pages to be printed. It takes ap… |
| 1.3.6.1.4.1.480.1.5.9 | qmsClientFrameBuffer | 0 | 0 | The Frame Buffer memory client holds rasterized or bitmapped images of page faces which are ready to be sent to the print engine… |
| 1.3.6.1.4.1.480.1.5.10 | qmsClientEmulTemp | 0 | 0 | Also known as K Mem Emul Tmp and Emulation Temporary, this cli- ent sets the amount of system memory to be used by non-PostScrip… |
| 1.3.6.1.4.1.480.1.5.11 | qmsClientDisk | 0 | 0 | This memory client stores frequently used data in system memory instead of continually storing and retrieving it from a hard dis… |
| 1.3.6.1.4.1.480.1.5.13 | qmsClientColorMatching | 0 | 0 | The Color Matching memory client provides storage space for the control and operation of the Color Matching feature. The availa… |
| 1.3.6.1.4.1.480.1.5.14 | qmsClientHPStoragePool | 0 | 0 | Also known as K Mem HP Pool, HP Heap, HP VM, and Virtual Memory, this client holds downloaded fonts, and forms. Inefficiently cod… |