Migration considerations

These considerations apply when you migrate to Print Transforms from AFP:

.aokcinit file

If you install the transform daemons in a directory other than the default /usr/lpp/Printsrv/bin directory, make sure that the .aokcinit file is in the same directory. All the transforms that Print Transforms from AFP provides use this file. If the file is not in the same directory as the transform daemons, you receive this message in the Infoprint Server common message log:

AOP003E afpxps.dll: AOK03227E Transform Config File 
"/u/user/Printsrv/bin/.aokcinit"is inaccessible:
EDC5129I No such file or directory.

PDF encryption with passwords

The Print Transforms from AFP sample Password exit for the AFP to PDF transform is the same as the exit that Infoprint Transforms from AFP provides. However, the file names for the Password exit and the password database are new. Also, the default value for the AOP_PASSWORD_EXIT environment variables is the Print Transforms from AFP password exit. Table 23 shows the differences in the transform products.

Table 23. AFP to PDF Password exits in Infoprint Transforms compared to Print Transforms

Transform product	Password exit	Password database	AOP_PASSWORD_EXIT default
Infoprint Transforms from AFP	aoppdfexit.dll	aoppdfexit.db	/usr/lpp/Printsrv/lib/aoppdfexit.dll
Print Transforms from AFP	aokpdfexit.dll	aokpdfexit.db	/usr/lpp/Printsrv/lib/aokpdfexit.dll

If you have not customized the sample Password exit, you can use the sample Password exit that Print Transforms from AFP provides. To use the new Password exit, you can either omit the AOP_PASSWORD_EXIT environment variable, or specify:

AOP_PASSWORD_EXIT->/usr/lpp/Printsrv/lib/aokpdfexit.dll

If you have customized the Password exit, you can continue to use the customized exit. However, make sure that the AOP_PASSWORD_EXIT environment variable in the Infoprint Server transform configuration file (aopxfd.conf) specifies the full path name of the customized Password exit. For example:

AOP_PASSWORD_EXIT->/usr/lpp/Printsrv/lib/aoppdfexit.dll

DATACK JCL parameter

The DATACK JCL parameter is not supported. The AOP_TRAILER_ERROR_PAGE environment variable and the trailer-transform-error-page job attribute provide a similar but more comprehensive set of options than the options provided by the DATACK JCL parameter. Use the AOP_TRAILER_ERROR_PAGE environment variable or the trailer-transform-error-page job attribute to control whether or not a page of error, warning, or informational messages are attached to the output document.

Tip:

Set the Trailer error page field in the printer definition to avoid having to stop and restart the transform daemon, aopxfd.

Specify the PRTATTRS JCL parameter in the OUTPUT JCL statement to specify the trailer-transform-error-page job attribute. You can use the PRTATTRS JCL parameter as a replacement for the DATACK JCL parameter:

• To not attach a trailer page, specify PRTATTRS='trailer-transform-error-page=no'. This corresponds to the DATACK=BLOCK parameter.
• To attach a trailer page, set PRTATTRS='trailer-transform-error-page=warning'. This corresponds to the DATACK=UNBLOCK, DATACK=BLKCHAR, and DATACK=BLKPOS parameters.

If you do not want the transform to stop when an error occurs, set the AOP_FAIL_ON_ERROR -> no environment variable or specify the fail-on-transform-error=no job attribute.

AOP_FONTMAP_TABLE

When viewing the output PDF document, if the fidelity of the font characters is not as sharp as it was when using the previous transform product, you will need to include a font-mapping table. The reason for the fidelity loss might be that the transform is inserting raster font characters rather than outline font characters into the PDF document. For instructions on how to set up and use a font-mapping table, see Mapping raster fonts to outline fonts.