Status Example 1 – Viewing Jobs

The figure below shows an LPS server.

·      There are 6 configured devices on this server.

·      At this moment in time, devices 1 to 5 are idle.  Device 6 has 12 jobs pending.

·      When the server root is selected at the top of the tree, the context view shows all pending and printed jobs for all printers on the selected server real time (as opposed to just the 1 printer).

·      If a branch is been expanded showing Printed/Pending/Spooled/Failed jobs, the branch refreshes ‘real time’, and all other branches refresh at the polling interval.

Read the section on Context Menus to see how to view a file, resend jobs, and delete jobs.

Figure 2-O:  Status Client showing one server and status of jobs

Status Example 2 – Context Menus

The next figure shows a view of an LPS server:

·      The number next to the name is the serial number of the LPS running on this server.

·      The count in parenthesis next to the printers reflects the number of pending jobs for that particular printer.

·      The context menu shown in this figure is displayed when an item in the context view is right clicked.  The choices in this menu are documented in the next section, “Menu Choices”:

·      The context view is for Device 4.

Figure 2-P: Status Client showing 6 printers and the context menu for one of the printed jobs

Status Example 3 – Monitoring Multiple Servers

The following figure shows the Status dialog connected to multiple servers.

·      Four LPS servers are shown in the tree.

·      Server ‘CRIANHARD-XP’ is expanded to show its General Queue and 1 idle device. The right column displays all the Printed, Pending and Spooled jobs for that server.

·      The LPS on the server named ‘ASALVADOR-XP’ is not running and is marked with a red icon and an ‘offline’ message.  This could also occur if the server was extremely busy or has hundreds of printers that need to be refreshed.  You may have to wait up to 30 seconds before the branch ‘goes green’.

Figure 2-Q: Monitoring multiple servers

Status Example 4 – Interpreting Error Conditions

This example shows a server named LANCELOT that has several configured devices.

·      A red exclamation point (!) icon to the left of the server name indicates that there is an error on one of its devices.

·      The icon to the left of Device 11 (Shipping Printer 1) is red because it is the printer with the error.

·      Note that the error message is given in both the tree and the context views.

·      When one of the icons changes to yellow, it denotes a critical failure.  Red denotes that a job did not print because of an error at the printer.

·      Note that Printer 11 has an alias defined.  This is helpful when reading the tree.  (See Chapter 2 in the LLM User’s Guide for information on creating alias names for your configured devices.)

Figure 2-R: Status Application showing a printer with an error condition