The error listing typically includes a description of the problem, information about what resources were involved and the active printing environment. Typical problems are:
Often, for performance reasons, error reporting for some printer-detected error conditions may be disabled. The printer defaults can be overridden with an OUTPUT statement: see the description of the DATACK option.
Normally, a well-behaved AFP printer should not lose output, even under catastrophic circumstances. A print job is not normally reported as complete by the printer until the output is stacked. Some AFP emulation products may not exhibit this behaviour. There is a feature sometimes known as "early print complete" where a printer can report a job as complete before the output is actually delivered to the output bin; this can provide improved throughput but at the expense of reliability and recoverability.
The checkpoint interval specified in the printer's JES2/JES3 configuration specifies how frequently the status of an active print job is recorded for recovery purposes. Too small a checkpoint interval can result in performance issues; too large a checkpoint interval can mean that a larger number of pages are reprinted after a printer, network or system problem.
The ACIF utility can be used to combine print data with AFP resources. It can be useful as a diagnostic aid since it performs similar processing to PSF without actually communicating with a printer. It can detect problems related to missing or incorrect AFP resources.
SDSF can be useful for inspecting the datastream being generated by the application.
The NETSTAT command can be used to display active TCP/IP connections. For example,