General description of Spool2XML
The normal printing process on the IBM i platform works like this:
The printing program use a printer file to print the final spooled file. The use of an external printer file is a prerequisite for Spool2XML.
When introducing Spool2XML the new process looks like this:
A short introduction to the individual parts:
The new Spool2XML printer file
A new printer file is needed to ‘fool’ the program into creating a different spooled file. This is created by the command: IFORMNG2/CVTPRTFXML. In the XML definition you define the
output queue in which the final, merged spooled file will be generated, and if it should be broken up into smaller print outs. The new printer file can be placed higher in the library list or it
can replace the previous printer file. It is recommended to create the new printer file in another library.
The new XML Spooled file
The XML spooled file contains the XML structure as it should be in the XML file. The XML data in the spooled file is written with a start and end tag for the record format printed and fields defined in the record format is written within start and end tags within this record format. So the XML structure is valid, but not structured in a heirarchy apart from this.
The output queue of the printer file must be one of the output queues, that is monitored by Spool2XML for automatic processing.
Convert the spooled file into XML
The XML definition sets the structure of the final XML (what format is a sub-format to another - or in XML: Which formats are considered as subtrees to other formats?). It also sets the level
breaks to determine e.g. when a new XML files should be created (as one spooled file can be split up into many XML files).
Process the XML file in InterFormNG2
The final step is to let InterFormNG merge the XML file with a template (selected in the XML definition) and create a new merged spooled file, a PDF, an email or whatever output you want.
Notice: Help Center Transition Update
As of January 13, 2025, we are excited to announce that our new Help Center is in the final stages of development. While the Knowledge Base is already accessible, our current JIRA system will continue to manage support tickets during this transition period. For assistance with InterForm Output Management Software, please refer to the Support for InterForm Output Management Software.
We appreciate your patience and understanding as we work to enhance your support experience. If you have any questions or encounter any issues, please do not hesitate to reach out via the existing support channels.
Best regards,
The InterForm Support Team
Related Articles
XML
XML is used widely in InterFormNG2 as both input and output payload in the workflow (and of course in the designer). Please notice, that some workflow components are listed as accepting only XML as input, where they actually also accept an IBM i ...Split spool (complex key)
A spooled file can be split into smaller files depending on the contents e.g. to split up a larger spooled file with many invoices into individual invoices. If the other spooled file split functions are not enough, then you can consider this workflow ...Rule-based XML validation
This advanced validation workflow component, Rule-based XML validation, can validate XML according to rules. The rules for rule-based validation can be used to validate documents in XML format. A suggestion for implementation can be found here. The ...Split spool (fixed key position)
If you want InterFormNG2 to process spooled files, that contains multiple documents e.g. multiple invoices within a single spooled file (e.g. generated by a batch invoice run), then you may want to split up the spooled file into multiple output PDF ...Split spool (dynamic key position)
As the split spooled file (fixed key position) component above, this component can be used to split a spooled file based on a key value. However, in this case the key value can be in variable positions on the page. You just need to be able to find ...