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

Bryan Dietz wrote:

would you happen to be TELNET'd to the target system?

When Telnet'd and you press the iSeries Access emulation print key (ctrl-pause) the output is on the source system.

not 100% sure why, but I know it has worked that way for a while.

THANKS. I *am* TELNET'd, and the print-key (in our emulator, it's a toolbar button, right next to "local print as text" and "local print as picture" buttons) spool files *ARE* showing up on the source system.

Hmm. Apparently, the AS/400 Telnet client is hard-coded to act like a terminal with the print key set to "local print" mode (rather than a "transmit 'Print' AID code" mode), with no way to change that setting, because they're screen scrapes, even in cases where the application itself (e.g., QuestView) responds to a "Print" AID code, the spool file is NOT what the application puts out.

Fascinating. Why in blazes would they set up their Telnet client to intercept the "Print" AID code instead of passing it, and then provide no way to override it. Real terminals don't do that, and neither do other TN5250 clients.

So now, we're back to troubleshooting why calling puts() in a batch job doesn't produce a spool file.

--
JHHL