Assuming there's a solid reason, here's a hack:
Create 2 books:
- one "rendering" book that has a single file for all of that content (named, say, .LOS, Lists Of Stuff).
- one "authoring" book that also has a .LOS (for correct page numbering) and generates the TOC/LOF/LOT (as the last 3 files in the book), and
The .LOS file imports the entire Flow A from the other 3 list files as text insets.
Print and render to PDF from the "rendering" file. Update by doing an Update Book in the authoring file, then also in the rendering file.
Never having done this, I do wonder if the list hypertext will go to the correct places ...
With FM11, you could do it using a single book file using Error's setup with the TOC/LOF/LOT as the last three files.
First Update the book to get the generated files and the .LOS inset file.
Then, use the Book Exclude option (right-click on the file and select Exclude) to prevent those files from being included in the output.
Once the files are excluded, you can print or create a PDF without them appearing (at the end).
Just remember to turn off the exclusion if you need to update the book again and then exclude them again for output.
You can't have all three directly in a single generated file as FM uses Text Frame flowname on the Reference pages to determine which generated file to create. It's hardwired to only do one type per file.
> With FM11, you could do it using a single book file ...
> Then, use the Book Exclude option ...
Cool. I'd guess it's still necessary to Update Book twice, to catch any changes in the TOC/LOF/LOT pagination that would result in LOS pagination. And I'd toss in some AMPs just in case.
FM doesn't recursively look for that sort of stuff in most operations, presumably due to infinite loop risks.