|HP-UX Reference > L
lpstat(1)HP-UX 11i Version 3: February 2007
lpstat — report status information of the LP subsystem
lpstat [-drst] [-a [list]] [-c [list]] [-o [list]] [-p [list]] [-u [list]] [-v [list]] [-i] [ID]... [dest]...
The lpstat utility writes to standard output information about the current status of the LP subsystem.
If no arguments are given, lpstat writes the status of all requests made to lp by the user that are still in the output queue.
The lpstat utility supports the XBD specification, Section 10.2, Utility Syntax Guidelines, except the option-arguments are optional and cannot be presented as separate arguments.
Some of the options below can be followed by an optional list that can be in one of two forms: a list of items separated from one another by a comma, or a quoted list of items separated from one another by a comma or one or more blank characters. See EXAMPLES.
The omission of a list following such options causes all information relevant to the option to be written to standard output; for example:
writes the status of all output requests that are still in the output queue.
Operands and Arguments
Any arguments that are not options are assumed to be request ids (as returned by lp) or LP destinations. lpstat prints the status of requests corresponding to such request ids or the status of requests belonging to such destinations. options can appear in any order and can be repeated and intermixed with other arguments.
The following operands are supported:
Only users who have the lp subsystem authorization or the printqueue secondary subsystem authorization can view the entire queue. Unauthorized users can view only their own jobs whose sensitivity levels are dominated by the user's current sensitivity level.
The allowmacaccess privilege allows viewing jobs at higher sensitivity levels.
The following environment variables affect the execution of lpstat:
The standard output is a text file containing the information described Options, in an unspecified format.
The lpstat utility cannot reliably determine the status of print requests in all conceivable circumstances. When the printer is under the control of another operating system or resides on a remote system across a network, it need not be possible to determine the status of the print job after it has left the control of the local operating system. Even on local printers, spooling hardware in the printer may make it appear that the print job has been completed long before the final page is printed.
Check whether your job is queued:
Check the relative position of a queued job:
Verify that the job scheduler is running:
Obtain the status of two printers, the pathnames of two printers, a list of all class names and the status of the request named HiPri-33:
lpstat -plaser1,laser4 -v"laser2 laser3" -cHiPri-33
Obtain user print job status using the obsolescent mixed blank and comma form:
lpstat -u"ddg,gmv, maw"
cancel(1), enable(1), lp(1), rlpstat(1M).