The preferred method of handling SCS spooled files that have an AFP overlay named in their associated printer file is to simply change the DEVTYPE parameter of the printer file used to create the original spooled file to *AFPDS. This will cause IBM® i to put the data into spool as *AFPDS, which is the most efficient way for Content Manager OnDemand to capture (load) this type of spooled data. However, making this change will require the original, production spooled file to be printed on an AFPDS printer. In most cases, if you really are printing it with an overlay, then this should not be a problem. However, if you are printing it on a line printer with preprinted forms, this approach will not work.
If, for some reason you cannot change the original printer file's DEVTYPE parameter to *AFPDS, Content Manager OnDemand can do the conversion to AFP automatically, allowing the spooled file to be viewed and printed with fidelity. (This method is more time-consuming than letting IBM i do it using the DEVTYPE parameter of the printer file.) To enable this conversion, simply specify both the data type and the DOCTYPE indexer parameter in the Content Manager OnDemand Application definition as AFP rather than SCS. When Content Manager OnDemand encounters an *SCS spooled file that has an overlay, and the Application definition and DOCTYPE indexer parameter both specify AFP as the data type, Content Manager OnDemand will convert the *SCS data to *AFPDS and store that newly created *AFPDS spooled file. Reprints out of Content Manager OnDemand will require an AFP-capable printer, but that should be expected due to the overlay. If you specify a data type of AFP in your Content Manager OnDemand Application definitions for any other type of non-AFP spooled file, the loading of the data will fail.
