University Systems --> LPCR - Print Accounts --> --> LPCR Information for Faculty --> Multi-Device Queueing System (MDQS) Printing System Command Reference -->

Multi-Device Queueing System (MDQS) Printing System Command Reference

As of June 1, 2007, the printadmin login on the spooler has been retired. This page is a guide for using the Multiple Device Queueing System (MDQS) commands that replace printadmin. These commands can be used from a WAM or Glue prompt.

MDQS Quick Command Reference

  • A brief description of each command, including cross references to old printadmin commands

MDQS Commands

A detailed description of each command

  • qstat -- list queued print jobs and device status
  • qdev -- list detailed device status, modify device
  • qmod -- remove jobs in queue
  • hpstat -- ask device how it's doing (only HP's)

Permissions

The Office of Information Technology (OIT) Help Desk personnel have access to change all Laser Print Cost Recovery (LPCR) queues. Open Workstation Labs (OWL) lab managers, as well as users they authorize, have access to their own lab queues.

Any WAM or Glue user can view queues or devices but cannot make changes to them.

Are You WAM or Glue Authenticated?

Check WAM authenticated queues from a WAM account and Glue queues from a Glue account. Use the hesinfo queue qhost command to determine which is which; for example:

y:~% hesinfo chem qhost
neobank.umd.edu
y:~% hesinfo band qhost
avalon.eng.umd.edu

A rule of thumb is that WAM queues are spooled to neobank and Glue queues are not.

You can still use qstat and qdev for information about a printer from a different realm, however, you will not be able to modify anything.

A way to get around this is to have your ticket environment variable pointing to the ticket file for the correct realm for the printer, or write a script which does this for you automatically, for example:

A Note On Environment Variables

Pay attention to the $PRINTER environment variable. If the commands aren't working as you are expecting them to work, create a script that will automatically do this for you. See the example listed above for myqdev and myqstat.

For example, suppose you wanted to see a list of devices:

z:~% qdev
ccs            *Empty*  (Idle)
cit            *Empty*  (Idle)
sband          *Empty*  (Idle)
splash         *Empty*  (Idle)
band           *Empty*  (Idle)
boris          *Empty*  (Idle)
crab           *Empty*  (Idle)
shrimp         *Empty*  (Idle)
snowden        *Empty*  (Idle)
imfilter       *Empty*  (Idle)
psfilter       *Empty*  (Idle)
net            *Empty*  (Idle)
z:~% echo $PRINTER
band

The reason you don't see any of the WAM lab printers is that they are not spooled to the same spooler that band is.

z:~% setenv PRINTER pg2
z:~% qdev
hornbake-hp1   *Empty*  (Idle)
hornbake-hp2   *Empty*  Q00017.1371     18163 (Trying to open session to
hornbake-hp2.wam.umd.edu/9100)
pg2-hp1        *Empty*  (Idle)
pg2-hp2        *Empty*   Disabled (Idle)
    [...et cetera]

After $PRINTER is set to pg2, the qdev commands connects to its spooler and lists all of the printers spooled to it, including the other WAM lab printers.

You can define $PRINTER by using the setenv PRINTER queue command (where queue is the queue name). You can examine the value of printer by using echo $PRINTER.

The $PRINTER variable normally is set upon login time. If you are in a lab at a console, $PRINTER is set to the lab's printer.

How do I:
How are we doing? Comments on this page?
Office of Information Technology
Office of Information Technology Help Desk Web Site University of Maryland Web Site Office of Information Technology Web Site