Gary and Jeff,
Thanks for the two great postings. I have continued researching this problem and have narrowed it down to what is known as a "WRAPPER FILE". Which is pretty much what both of you are describing in your postings. A wrapper file is hard coded in XML and inside of it one needs to code all 150 xml files in a list as references that reflects the order you want your 150 XML files to output in as a PDF. Gary I think I follow with what you mention about selecting all tags (except to level tag) and then selecting the "Create File Entity from Selection" menu item in Arbortext. However, I hope you can clarify whether or not if it is still necessary for me to tweak the S1000D 4.01 Schema I'm using if I change all 150 of my XML files over to becoming Entities? It would be cool if I can avoid tweaking the Schema. Also once I have 150 entities created how do I wrap them so that Arbortext Print Compose sees all of the 150 entities as a single consolidated XML file that needs to be converted into a single PDF in a single print operation?
If anyone out there can please expand on how to code a WRAPPER file by posting some actual XML coding examples it will be much appreciated. Also examples on how to get it to work by relying in using Entities will be much appreciated. In short, any help will be tremendously appreciated because I need help. Thanks in advance.