user9976634 wrote:I mean to run the GENDAW32 manually from the windows command line. This is known as batching mode, or I'm wrong?
You mention that running on the "console" produces correct output. Are you referring to the Documaker Desktop (AFEMAIN.EXE) or something else when you say "console".
The AFGJOB you present has some unusual and perhaps some unnecessary things in it. Did you create this yourself?As I said before, this is a legacy application that uses the Documaker platform, also configured by the original developers.
I'm pretty sure the rules UpdatePOLFile and WriteOutput do exactly the same thing. Therefore you are probably writing you POL output twice with each transaction. This may not hurt anything other than performance and disk space, but is redundant.
You also have two different batching rules defined and although I suppose there could be a circumstance where you could use these two together, I'm going to guess that you don't need both. But since you have not complained about the batching, I suppose you can ignore that.Do yo mean to BatchingByPageCountPerRecipINI and BatchingByRecipINI rules?... there any way that this is related to the problem I have?... if not, what problem can generate?
Although you have defined the old misspelled version of the PaginateAndPropagate rule, it is fine and appears in the correct position. So, if you have overlapping sections, this would then make me think that perhaps your problem lies in either the size or attributes defined for the section that doesn't paginate properly.The problem persists in all documents generated (several hundred), so I don't think this could be related to specific sections attributes.
It is difficult to diagnose without actually seeing the setup in question, but I would start by reviwing whether this section is set as a background or has the "Fixed" attribute set on the origin.
If this section is flagged as a background section, it will not paginate off the page.
If you have said that the origin is "fixed" on the page, then the section won't move off the page either.
And finally, if the section is defined larger than a physical page, then it is not going to split across pages unless you happen to have a MLT field defined on the page that would format and cause this to span - assuming you have set the Can Span option.