Wayne McAlpine escribió:
Jerry, it almost sounds like a hardware issue, either the printer not
powered on or the printer cable disconnected. This would account for it
not going to a "varied on" status.
Sorry, but I'm afraid I cannot agree on that.
Printer sessions are nothing but a "logical hole in the dark" towards
Windows Spool services. When you configure your printer emulation
session you just give it a name, so iSeries will be able to display its
status, etc, and also give/assign the PC's "REAL_printer_name" to which
output should really be directed...
So, "printer_session" may appear as "vary on" and "ready" even if it's
really powered off.
It's just "Access" (ClientAccess or whichever version you call it) who
talks to iSeries and will "spool" output to Windows spool...
This is so, that if many printouts are sent continuously to a given
printer, to the iSeries it looks as if the printer is "damn_FAST", since
everything seems to be printed in just a second... (disappear from the
iSeries OUTQ... which means they gone, i.e. printed!!!) but they are
NOT printed yet, but are sitting in Windows spool waiting in its
queue... Now, if a new printout goes now from iSeries to the "emulated
printer", the iSeries THINKS the printer operator (usually the person
sitting at the PC) is ready to change forms... while it SHOULD NOT be
so, since there are, there may still be, still previous printous waiting
in the Windows spool to be printed! So the change forms may show up much
sooner than it should!.
Well, this is why I feel the problem may/must NOT be a hardware
problem, but something else...
A shot in the dark: Is this PC using a fixed IP address or connects via
DHCP? The printer session name would still be the same, nevertheless,
but wonder how iSeries would react to the fact that the PC's IP address
might have changed... until the operator does something to
"re-shake-hands"... Just a guess!
HTH
midrange.com
