RE: read large pdf file and split into separate .pdf files

We use http://resolutions.ws/ to burst PDFs created by EnterpriseOne
(OneWorld) and fax/email them to various people.  Can burst based on
content or whatever factors you choose.  It is a 100% iSeries solution
so no outboard Windows/Linux server is necessary.  As we use it, the
product reads PDFs stored as members in a PF (the EnterpriseOne
PRINTQUEUE file) and results in PDFs stored in the IFS.  Those are then
emailed/faxed or downloaded via web server as desired.  It has a
comprehensive scripting language and report transform app.

I'm not sure on the pricing.

We've used this for a while.  It's the big brother to the JetForms
package that we've also used for like 7 or 8 years to convert spool
files to PCL & PDF documents in the JDE World environment. 

Personally, the products use more CPU than I'd prefer, but then we tend
to do interesting transforms on the spool files.  On the World/JetForms
side we take plain 'greenbar' spool files & convert them to color PDFs
with fancy elements like shaded regions and repositioning the fields to
match what our employees and clients want vs. what JDE produces.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Sunday, March 19, 2006 9:56 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: read large pdf file and split into separate .pdf files

I am receiving a .pdf file via ftp to the iSeries IFS containing many
pages, each page a different order,many customers within a file. 
Need to provide an iSeries IFS file web link to each order, so would
split the .pdf file into a separate .pdf for each page (and then do the
link). 
Later need to xmit all files for a single customer to their server.
Is there a Brad or Scott type RPGLE tool, maybe java, or just some specs
on how to read thru & dissect a .pdf file.  Too many records to handle
interactively (5,000 weekly)  - must be batch driven. Would like to stay
away from other server solutions. This is an all iSeries web process (so
far).
jim franz