Re: (see thread on RPG list) Re: Test program calls puts(), creates spool file here, but not on customer box

CRPence wrote:
. . .

That describes how those parameter values are set for a job, but as for the Host Print request, how those parameters are set for the job may be irrelevant. The host print request resolves spooling different than the job. Which Display File is active is foremost. That is, the active DSPF [with a file-level keyword] may define the printer file to be used for Host Print requests issued while that DSPF is open and active;

. . .

I didn't really follow a whole lot of this message (not that I was all that motivated, given that the immediate problem has been solved on all counts), but:

It is also entirely possible that the display file might be configured to simply pass the "Print" AID code to the application, in which case the application, rather than the operating system, processes it. In QuestView, for example, the Host Print key is captured, and instead of requesting a hardcopy of what's on the screen, it requests a report that is generally similar in format to what's shown on the screen, but takes advantage of the fact that a printed page has considerably more real estate than a terminal screen (e.g., where the multi-record mode of QuestView shows perhaps 20 records, the corresponding print-key output might show 60, assuming it's set to only print one page).

--
JHHL