Troubleshooting Make FCB

This topic contains solutions to common problems that you might experience with Make FCB.

See also:

FCB information is not being applied to print jobs

Solution 1

Cause: The value in the job's FCBNAME field might not match the names of the FCBs that have been created.

Solution: Be sure that you have created an FCB with a name that matches the job's FCBNAME. Make sure you follow the FCB naming conventions.

Solution 2

Cause: Instead of only specifying the base Resource folder path, the Resource folder path has been completely specified, including execution_node\sys1.imagelib (for example, \\BHCS\Resources\Default\Sys1.imagelib).

Solution: Change the path for the Resource folder on the Configuration Utility's Resource Folders tab and do not include the actual host library name or default library name. Only the base Resource folder path should be specified (for example, \\BHCS\Resources).

Solution 3

Cause: The Generic/Text Only printer driver was selected for ASCII data being sent through the parallel port (LPT1).

Solution: To send ASCII output to a printer attached to the parallel port and apply the FCB to the data, configure your printer to use the Barr ASCII - Printer Driver instead of Microsoft's Generic/Text Only printer driver.