This function is currently only implemented on Windows based platforms! Another method for job splitting is available using the OutArchiveDir key. An overview of different job distribution methods can be seen here.

ERP systems typically produce through their batch printing processes huge print jobs, like for example invoices. Sometimes it is needed to separate them into single jobs.

  • Staple each individual job, see Examples
  • Archive and search each individual jobs, see Examples
  • Send out each individual job as an e-mail or fax
  • Workload balancing for splitting huge jobs to several printers, of you like even with different speeds, so that the job is printed in minimum time. (see manual for detailed explanations and here)

The technology how ELP handles the print job splitting is pretty easy:

  • Receive the job on windows queue 1
  • Instead of printing the job to the printer, send it to another or tagged as the second pass to the same windows queue
  • Search for the last page of each individual job (first page search process is in development) and
  • Split it right after the next form feed by closing the out-writing and re-open the writing again. So a new job is generated in the receiving queue

Jobs with a fixed amount of pages per single document do not need to search for a fixed statement on the last page. There are other ways to do it: See below.

The supplied rule assistant way of splitting files does not work for jobs which have already the split escape sequence build in, See below:

Select in the drop down list the destination queue for splitting the job, but make sure, it is NOT the same queue which receives the files. Define the split method by single pages or search for a term. Maybe make sure with the function New Rule/Section that the search method Search_Windows can find the text. If not you may need to change the statement later to Search_:Windows_New.

Press the OK and the back button. 2 new rules are now available:

  • Split file using OutPort method
  • and the rule for the destination queue.

If you solutions requests to apply for all split jobs the same functions, you may add them now to the printer names rule. But if you need to develop several rules to the split jobs, generate a new file called split.ini in the folder c:\ProgramData\WELP and load it into the Control Center. An new ini file can be created by copying for example the convert.ini or simply create a new empty file with notepad.exe.

Technical backgrounds:

The fill options for this "Split a data stream" Window are:

 

Split into this destination queue

Here EP offers 2 options:

  1. \\#HOSTANME#\#PRINTERSHARENAME# will resend the splitted job to the same queue where it came from. This option is used when quite a number of printers are supported by ELP, they all need to split data streams and therfor it is too expensive to purchase a lot of additional licenses.
    Disadvantage: It may take a little longer for first page out.
  2. Any other queue which is shared on this server.

Notes:

  • This argument enters the OutPort key into your rule. If needed, change it later to other servers, or change the variable #HOSTNAME# to 127.0.01 (Local host)
  • When forwarding the jobs to a "Follow Me" system, please remember, that ELP needs to be licensed for any printer, the job may got to.
Don't initalize new split stream In very rare cases (rare especially windows data streams), the mail merge pages are generated in a way, that they can be printed fully stand alone. In that case you may set this option
Insert all fonts/macros/init. into all part jobs

Turned on, ELP automatically reinitialize the splitted jobs to the proper values, that the document is stand alone printable.

  • This includes setting the font in the new opened job to the last used font of the old strip. It is strongly recommended not to use any forms via ELP_Command while the splitting process. This may lead into wrong results. It can be applied later in the rules for the splitted parts.
  • ELP does support to collect downloaded fonts or characters as well as macros, which are already part of the data stream, and sets them in front of every splitted part. For example downloaded Windows TrueType fonts. This must be enables with the key: OutPortMode_ CollectFonts.
  • ELP does collect the general initialisation of the first and last page and automatically inserts the sequences in front of every splitted job.

In order to separate the jobs, ELP needs on each individual last page a trigger in form of an escape sequence, like <Esc>)s-997Z where <ESC> is ASCII 27 or hex1B, or using the Free-Escape featureof ELP: ~)s-997Z. If you can add this sequence already to the job, then no search is needed. You can apply the OutPort rule direct in the receiving rule and add EXIT=ON to finish the ini file analysis.

 

Every single page is separated The document has to be splitted after each page. An N page document will then lead into N+1 splitted documents.
There is one more document splitted, because after the last form feed
Always split after N pages The single document does have always exact N pages (2 and up). Then ELP will split the document using an ELP_Command:
C1:#F25997R0; where # is the amount of pages.  (Modul FOR is needed)
So on every # page the escape sequence \x1B)s-997Z is added by the ELP command F25997, which is a dummy macro and does only hold that ELP internal PCL command. The R command resets the page counter to 0, so that the next page is page 1. 
Split command Esc)s-997Z is already part of data stream The needed split command is already added by your application, e.g. MS Word.
Split before/after term If the amount of pages of the single document variate, and do not have the split sequence in, then search for a special expression in the data stream and add the split information using a rule.
Please use the test function to be sure that the expression/term is findable be ELP the new rule option and add them like the prototype below.
ELP can handel an indefinit amount of rules for searching ans spitting different data streams. You can add them later using the standard rule generator.
Test This button ensures, that the entered expression is found in the data stream. Before pressing the button, the data stream first needs to be stored or printed into a file. You can use the protocol option of ELP (file in_data.prn) or simply print the job to file.
See here for ways how to get the files outside from ELP.
This function is not only looking for the term, but also with which method it needs to be searched.
The search item is always on the .... first page : Means that the entered search expression is always on page one of each splitted document. ELP then does automatically insert the split command before the last formfeed. (The key Preparsing needs to be turned on in rule Global)
(The miscellaneous key: Preparsing=ON needs to be set in rule Global)
last page : Means that the entered search expression is always on the last page of each splitted document. This is the faster process method compared to first page. If search method is Binary, Windows or Text (not _new), preparsing can be turned OFF.
Erase search argument (if mode is less than 3 only)

If needed and if the search mode is Search_Binary, _Windows or _Text (not _New), the searched expression can be removed from the data stream.
This option is only accessable after the test function did hit the searched term with one of the 3 search methods above.

Mark print data stream for printing through ELP

When the splitted data stream returns to the same ELP queue, a marker needs to be in the returned document, that ELP has the chance to detect a second pass and apply the requested rules. Marked, the PPAdmin wizzard does add those 2 rules:

[Split same queue pass 1]

REM=Mark print data stream for printing through ELP
OutSearch_Binary=\x1B%-12345X
Add_Binary=@PJL COMMENT "ELP Splitted job"\x0D\x0A

[Split same queue pass 2]

REM=Use the following ini file for second pass through ELP
Search_Binary=@PJL COMMENT "ELP Splitted job"
INIFILE=#ELP_FORMS_PATH#split.ini 

NOTES:

  • The splitted jobs then are processed in the configuration file split.ini in the c:\ProgramData\WELP path. This file needs to be generated by you!
    All settings from rule Global and any other rule issued in the main convert.ini before the text marker is found, is still remembered and executed.
  • If the needed functionality, like stapling, forms management etc. can be defined in that second rule, REPLACE the IniFile key with EXIT=ON and add the commands there.
  • Using variables in the OutSearch statement indicating the document type, which are set before can help to pass the document type into the the re-entering single document process.

Technical aspects: Split mailmerge print files in their single documents; Additional technical information how streams are splitted can be found here.

More Examples: Split a big job into 50 pages pieces, as this is maximum amount of pages being stapled  Split a job to different out-trays and perform rules upon used input trays  New Rule/Section