Exploiting lesser used PDF and VPF files in CA Bundl
search cancel

Exploiting lesser used PDF and VPF files in CA Bundl


Article ID: 14975


Updated On:




CA Bundl seems to be using only three of the available 10 PDF and 10 VPF files and those three are constantly filling up. 

How can I set up CA Bundl so that it uses all 10 of the available PDF and all 10 of the available VPF files instead of only using and filling up just those 3?


Component: BUNDL


Here's how CA Bundl works...


The Bundl DSF records are used to collect report data (Option 5.1 from the Bundl Admin screen).


When report data is initially "collected", it is written into the Bundl Page Data files (PDF's). 


Which specific PDF files will be utilized for writing collected report data into is dictated by these Bundl DSF collection records. 


On the "CA-BUNDL: DSF Detail Screen", you will see two particular fields as "Min PDF =>" and "Max PDF =>". These fields dictate the range of available PDF files that Bundl will use to write the collected report data into.


In order to exploit all of the available PDF files, you would need to update these DSF records with whatever range you want Bundl to use. For example, if you want Bundl to write to all 10 PDF files, you would specify "Min PDF=> 0  and Max PDF=> 9" in each of the appropriate DSF records.


Now, regarding the View Page Files (VPF's)...


The way Bundl works is that whichever "PDF" file the data is initially collected into, it's counter part "VPF" file will be used when the "distribution process" is run and the data is MOVED from the PDF files to the VPF files. Then at the end of the night, when the EOD process runs, the PDF files that were temporarily storing the collected report data get cleared out.


So, if a report gets collected into the PDF3 file, it will be moved to the VPF3 file when the distribution process is run. You don't have control over which VPF file Bundl will MOVE the data into.