This technical note describes support for HP and VT host-initiated printing in Reflection for the Web, and provides details on how to troubleshoot host-initiated print jobs.
Many HP or VT host applications can print to printers that are not attached to the host. This type of host-initiated printing may be called slave printing, log bottom printing, record mode printing, pass through printing, auto-print, or controller printing.
Usually, host-initiated printing involves a selection from a host menu. To send a print job, the host transmits escape sequences to the terminal or terminal emulator, which signal that the print job should be forwarded to a printer. Reflection for the Web supports host-initiated printing and will forward the print job to the printer specified in the end-userís default printer.
Some host applications send printer control codes (such as PCL commands), which are intended to tell the printer how to format the print job. The printer driver on the client computer may attempt to interpret or print these commands, resulting in strange characters printing, incorrect formatting, or no printing at all. If your host-initiated print job has one of these problems using your Reflection session's default print settings, follow the instructions in the sections below to correct the print job.
This section details how to configure Reflection to send the print job directly to the printer. Normally, Reflection should bypass the client computerís printer driver when necessary to preserve host formatting.
Note: Host-initiated print jobs are sent directly to the client machine's default printer.
Follow these steps to configure Reflection to send the host-initiated print job directly the printer.
If you are still having trouble, try the following:
When configuring a terminal session for your end users, you can either save the Reflection print settings in a custom session that you deploy to your users, or you can configure the session to allow the users to configure and save their own settings.
The Reflection print settings configured in the steps above can be saved while configuring a terminal session using the Session Manager in the Administrative WebStation. To save these settings in a custom session, follow the steps below:
If end users prefer to configure their own print settings, you can configure a session that allows end users to save their settings in a local preferences file.
To allow end users to save their printing preferences, follow the steps below:
If you are unable to solve the problem using the procedures listed above, contact Attachmate Technical Support; see http://support.attachmate.com/contact/.
When you contact technical support, be sure to have a trace file of your printing problem ready.
To capture a trace file of your printing problem, follow these steps: