Understanding the Screen Layout

Real Time Refreshing: All limbs of the selected (highlighted) branch of the tree are updated ‘real time.’  There may be a slight delay depending on how busy the server is.  You can make all printer status for a particular server update in real time by selecting the server.  The server is selected by default when entering the program, unless more than one server is specified.

Refreshing at Polling Interval: Any limbs that are not part of the selected branch are updated at the polling interval, which is 30 seconds by default.  Shortening the poll interval speeds the screen update but burdens the server more.  Loftware recommends that you leave the poll interval at 30 seconds and use the real time highlighting method described above.

Purge Level: Jobs in the context view remain until the next purge interval.  See the ‘Housekeeping Tab’ section of the LPS chapter for detailed information on file purging.

Jobs marked as Printed: When a job in the context view is marked as ‘Printed,’ the LPS has finished processing this job and it remains on the system until the next purge interval.  This type of job can be resent to the printer as described in one of the following examples:

Jobs marked as Pending: If the printer is in a busy or error state, new jobs that are requested of it are queued up and marked as ‘Pending.’  Pending jobs can be deleted by ‘right clicking’ on the job and choosing ‘Delete’ from the context menu.  Pending job files allow the LPS system to recover from critical errors and are not deleted during the purge process.

Keep the following points in mind when deleting a Pending job:

·      Depending on how busy the server is, there can be a considerable pause before the job is removed.

·      When you delete a Pending Job, the printer goes into an error state temporarily. Notifications go out if you are using the Agent. Normal printer operations resume after the next print request to that printer.

Jobs marked as Failed: If the LPS does not understand the request that has been made, it is marked as ‘Failed.’  This occurs when the request contains a syntax error or invalid information. Failed jobs usually occur when you first start debugging your system.  They should become rare or non-existent when your system is fully debugged.  You can “right click” on a failed job and choose ‘View File.’  If you see a syntax error, you may correct it and hit resend.

Jobs marked as Spooled:  These are jobs that have been processed by the LPS, and are being sent to the Web Listener for processing.  Once the job request has been sent back to the LPS by the Listener, the context view for that job is displayed as “Requested.”  Once the job has been printed or fails, it moves to the Printed or Failed directory.  Spooled jobs can be deleted by ‘right clicking’ on the job and choosing ‘Delete’ from the context menu.

Green icons on tree branches: A green icon indicates that the printer is accepting jobs and no errors have been detected.  This is not 100% accurate and we suggest you familiarize yourself with the ‘Device Status’ section of Chapter 2 in the LLM User’s Guide and the Printer Error Message section of the specific Printer Family in Appendix B in the LLM User’s Guide.

Red icons on tree branches: A red icon indicates that a printer is in an error state.  No new jobs are printed on this printer until the error is resolved.  The icon at the server level goes red if any of its printers (branches) have a problem.  This does not mean that the server is down; it simply is indicating that one of its printers needs attention.

Yellow icons on tree branches: Indicates that there was a Failed Job on that branch.  The reason it is yellow is that although there was a failed job, new jobs that do not have syntax errors are still able to print.  Like the red icon, the server icon goes yellow if one of its printers goes yellow.

As you can see from the discussion above, this program can provide a wealth of information.  Hundreds of printers being driven on multiple servers can be monitored simultaneously.  The best way to understand the information displayed in the Status application is by example.