×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
