Select your language


Q: We have a huge job which takes pretty long to print. As we have several printers (4) we would like to split any job with more then 100 pages in 4 jobs. So the print is taking about 1/4th time to being printed.

There are two solutions for splitting larger jobs into pieces for fast distributed printing:

  • Use ELPs and distribute the job to X queues, where the job can be split in variable portions, according the single printer speeds
  • When you have x printers with same speed, split into one queue with same portions and use the Windows pooling function, to let windows decide where to print.

In both cases only one ELP license is needed. An overview of different job distribution methods can be seen here.

A: The first solution is to use the Split_section method:

Work load balancing means, that several printers are available, maybe with different printer speeds, and one big job is distributed to those printers that all are printing one piece of the job, and that they finish at the same time. So time optimized printing.

Note: Currently ELP does not handle duplex jobs. This means a job can be split on the front page of the job, so the actual back page could become the front page of the split part. If this causes problems, please let the developers know.

The implementations needs minimum one ELP activated queue, which receives the incoming data. Instead of printing this data stream, it will be split into X pieces, depending upon the amount X of available printers.

Those split job receiving queues are normally NOT(!) ELP activated. If all printers to have the same speed, then one print queue is quite enough, but then the MS Windows function "printer pool" must be used. Meaning that in the real printing queues, in the driver properties - port definition simply select the "printer pool activation" mark. So MS Windows will distribute automatically any arriving job to the next free printer. The disadvantage is that not all printers might get the same work load. If this is needed do not use Pooling functionality.

Due to the expected huge print jobs, set the buffer handling to the maximum larges buffer size, otherwise a 200 MByte data stream could generate more then 100.000 input buffers, whose administration will eat a horrible portion of the available PC power. This is done through the key Max_ReadBuffer.

If printers with different printing speed are used, then the splitting function can split the job in different sized portions, so all printers will finish pretty much at the same time.

So please install now for every printing printer one queue including the definition of a share name. Install also an additional printer queue, which has to be ELP activated and will receive the incoming data. When this receiving queue does not print, set it to the local port NUL.


; calculates while reading the data stream the amount of pages


; Do not print this stream


; increase buffer for this kind of handling to increase speed by about 20%


; If the printing parts are supposed to have a cover sheet, use the key PortCoverSheet. This key has 2 arguments separated by semicolon:
; - A macro number which contains all collected variables who are supposed to help to sort the split job into the correct page order (ELP provides macro 22000).
; - Any needed initialization sequences for the cover sheet, that it is drawn out of the wished tray and put into the selected out-tray.


[If more then 100 pages split to 4 different printers]

; primary trigger is always true


; Secondary trigger, if true, then:


; Split the job according to this Workload balancing numbers:


; Collect all stuff and insert it in front of each part, that the part can be printed fully independently



; Tell the ELP split function which variable does have the total page count


; Then split to those printers: Instead of the #HOSTNAME# variable, you may use any UNC path and printer share name, or simply:


This example splits the job in 4 pieces and sends them into the same Windows printer queue which has the printer pooling function enabled with 4 defined ports to printers with the same speed defined.

Two keys advice ELP how to split the stream into X portions and sent to which printer:

SplitPageCounter tells ELP which pre-processor variable does contain the total amount of pages of this job
up to SPLIT=X
do inform ELP about the percentage of the strip size and the port (printer share name) the strip data is sent to. For the version where a printer pool is used, the port will always be the same, just the pooling activated receiving queue. So the key option is the maximum percentage of the strip size between 1 and 100 a semicolon and the definition of the share name of the printer which should print the strip.



  1. If the incoming queue will only get such big print jobs then just move the Split_Section key into the rule Global and erase the rest of the second section.
  2. In rare cases the key \\#HOSTNAME# does not work. You may substitute it with \\ or #PCNAME#
  3. According to the ELP license regulations this solution needs 4 licenses. Although the receiving queue must not be activated in ELP!
  4. If you have printers with different speeds then change the last rule to:



; The first queue shared as Printer1 has a printer with 100 pages per minute connected


; The other two queues have printer attached with 50 pages per minute.


The disadvantage of this first solution is that each part is restarted at the beginning and ends at the designate page. So the split jobs are getting larger and larger. But it is the cheapest solution. Just needs the Basic and the SND software module.


B. The second solution

Is speed and data stream optimized and uses the same pooling mechanism of the destination queue as first example above (printers need to have the same printing speed):




; Note: the data stream receiving queue should be connected to the default printer

; where all jobs below 100 pages are sent to


[Initialize the variables]

; Unfortunately the counter key is interpreted before the variable key

; so this rule moves the setting in front of the counter of next rule


; This rule is always true! So set the variables


[If more then 100 pages split to 4 different printers]


; Do not print this stream


; Split the job to the pooling queue (4 printers)


; this key assures that all jobs are printable on their own


; First page is spitted after 25% of total page size


; After 50%


; and after 75%


; Use the Forms-management command to add after those pages the file split command 3 splits result in 4 print files


Note:There are more possibilities for splitting data steams for Workload Balancing reasons:

a) Split in fixed print file size / page counters . Search in the manual the those 2 keys: Distribute_file size or Distribute_page count
b) It is also possible to split the job into archive files. Then a batch file (executed via call) might send the parts to the correct printer / printer queue.
c) If you wish to define a cover sheet on every newly generated job use the key PortCoverSheet=#### (#### is the macro number). The key provides also a possibility to set any additional escape sequences for example for paper in and output tray selection. Also the usage of any ELP variable is allowed in the initialization string.
The macro 22000 is available as a predefined cover sheet, but feel free to develop any own macro, using any predefined or any collected variables. Note: Using the ELP_Command EB#; does only print one cover sheet at the beginning of the print job! So it is NOT the same.


Related articles: Split Job To Staple, Distribute data streams


We use cookies

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.