Novell Home

My Favorites

Close

Please to see your favorites.

Does NDPS allow for load balancing of print jobs from a native NetWare queue?

(Last modified: 21Jun2002)

This document (10063697) is provided subject to the disclaimer at the end of this document.

goal

Does NDPS allow for load balancing of print jobs from a native NetWare queue?

What does the NDPSM /QLOADBALANCE switch do?

fact

NDPSM v2.20f dated 28AUG2000

NW50SP6A.EXE

NW51SP2A.EXE

symptom

NDPS printer agents are not able to load balance print jobs from a native NetWare queue.

If multiple printer agents are servicing a queue, the first printer agent will take all the print jobs out of the print queue.

change

NDPSM v2.20f and later support load balancing of print jobs from legacy print queues using the /QLOADBALANCE switch.

fix

The NDPS Manager now supports the ability to load balance print jobs from a legacy (NON-NDPS) print queues.  Please do the following steps to activate this new feature...

1.)  Make sure that you have NDPSM v2.20f or later for this functionality.  NDPSM v2.20f shipped with NW50SP6 and NW51SP2.

2.)  You will need to load NDPSM with the /QLOADBALANCE switch.  For example,

LOAD NDPSM ".NDPS-MGR.PRINT.NOVELL" /QLOADBALANCE

If you do not load the NDPS Manager with the /QLOADBALANCE switch, only one printer agent will service all the print jobs submitted to the print queue.

3.)  Determine which printer agents you want to service the queue.  Once that determination has been made, you will need to have each printer agent service the same queue.  Do the following to each printer agent you want to service the same queue...

  -- Run NWADMN32.
  -- Double click on the printer agent you want to service the print queue.
  -- Click on the "Jobs v" button and select "Spooling Configuration".
  -- Locate "Service Jobs From NetWare Queues".  Click on the "Add" button and add the queue that you want serviced.  Click the "OK" button and close the printer agent.
  -- Repeat adding the same queue to the other printer agents that you want to service the queue.

4.)  Notify your end users that multiple printers will be servicing their print jobs.

HOW IT WORKS:

The NDPS Manager checks the queue it is assigned to service every five to six seconds.  Without the /QLOADBALANCE switch enabled, the NDPS Manager will move all the jobs in a legacy print queue to the printer agent's spooling location.  It will then work on those print jobs until they have all been successfully completed.  If the printer actually has something happen to it (paper jam, I/O error), the NDPS Manager will continue to move jobs to that printer agent.  If there were multiple printer agents assigned to a print queue, only one queue will be picking up the jobs from that print queue.  Any other printer agents assigned to that queue won't receive any print jobs.

The way the /QLOADBALANCE switch works, the NDPS Manager will check the status of the printer agent before looking at the print queue.  If the printer agent is in an "Idle" state, then the NDPS Manager will take a single job out of the queue and move it to the printer agent's spooling location.  Once that printer agent returns to an "Idle" state, then another job will be taken out of the queue, if one is available for the printer agent to service.  The NDPS Manager will not take out any more jobs from the print queue if the status is not in an "Idle" state.  If a printer agent is in an "I/O Error", "Printing", "Shutdown", "Off-line" etc. state, then that printer agent will not receive any more jobs from the print queue.  This prevents a broken or busy printer from picking up any more jobs from the print queue.

One instance where the /QLOADBALANCE switch won't work is when the printer receiving the jobs has a hard drive installed to spool jobs on the printer.  In that case, the printer will start spooling print jobs and few, if any, other print jobs would make it to the other printers.  High end printers typically have hard drives installed (plotters, high volume laser printers, etc.).

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10063697
  • Solution ID: NOVL53611
  • Creation Date: 20Jul2001
  • Modified Date: 21Jun2002
    • NovellNetWare

Did this document solve your problem? Provide Feedback