Batching of AFP files fails if original jobs use same inline resource name with different content

For example, if two original jobs both include a code page named T1EX0000 but the content of the two code pages is different, the step attempting to build the print job fails.

Document composition software sometimes builds these inline resources with arbitrary names, reusing the same names for a resource for each AFP file they create; this practice makes the problem likely to occur. For example, a composition application builds a code page for each AFP file and places it inline. It always names the code page T1CODEPG, but it contains only the code points used for each file. So the first file built this way has an inline code page named T1CODEPG with 100 code points in it and a second file built by this application also has an inline code page named T1CODEPG with 150 code points in it. When the CreateAFPJobsFromDocuments, BuildAFPFromDocuments, or BuildAFPFromZip step attempts to build a single job containing documents from these two files, an error occurs because the two resources with the same names have different contents.

If possible, change a setting in the composition application to produce uniquely named inline resources. Or find a way to have the different input files point to the same external resource.

This problem can occur for any AFP resource type except form definitions. However, the medium maps specified for all the documents being batched into a single job must have the same setting for duplex and include the same values for the constant back parameter.