How a Host Report is Generated and Processed

HostExplorer Print Services

How a Host Report is Generated and Processed

When you submit a batch job to the host, you can use Hummingbird HostExplorer as a terminal emulator, or use a terminal that is connected directly to the host.

The host then spools the batch job to a job queue, where it stays until it is able to run.
The job runs, generating a report intended for a host printer. The report is in EBCDIC (not ASCII). EBCDIC uses a system of printer controls that is different from the ASCII codes for line feed, carriage return, form feed, and so on.
Before the report is printed, the host spools the report to a print queue. For our scenario, reports intended for the Sales department are spooled to a print queue named SALESQ.

Reports in the print queue are printed on a host printer with the LU name. This host printer is normally a real printer (for example, an IBM 3287) if you are not using Print Services. In the scenario, print jobs in the SALESQ print queue are printed on the host printer with the LU name of SALES.

Note:

Your host system administrator is normally responsible for ensuring that a print queue is connected to the correct printer LU name and that reports are spooled to the correct print queue.