Voodoovw
1720 pts. | Jul 11 2009 8:14AM GMT
You’ve only used the name for this printer ( The name given under Specify workstation ID when configured) once right. Sounds like part of the setup for this printers name might already be in use.
There may be an OUTQ with a writer started or a device (Maybe a print session on another PC with the same printer name) already started. Check your setup: www.qsecofr.ca/printers/printers_files/Page286.html
Slack400
1210 pts. | Jul 11 2009 9:00PM GMT
IPL’s and the like should not be needed. (I’ll admit there’s a 1 in a million chance that an IPL might help)
A virtual printer is most likely externally defined on a PC or server somewhere. You’ll need to troubleshoot from there. I’ve never had any luck troubleshooting virtual printers from the AS400. The spooky fact that you can actually stop and start a writer from the AS400 to a virtual printer is a bit of a joke. It never works.
Do this. From the AS400 end the writer and vary off the virtual printer.
Then rename the printer and output queue.
Then go to the PC/server that houses the device and stop/start the session. If that PC is working you should come back and see the new device back on the AS400. Then just move your spooled files back over.
I’ve seen this alot with non-client access emulators, especially older versions (pre V5R1 days).
Just because emulator products let you setup virtual printers on a desktop doesn’t mean it’s a good idea. I keep all critical printing functions away from virtual printers.
the AUTO CONFIGURATION system value on an AS400 doesn’t work for virtual printers. It’s the equivalent to the Plug and Play cabability in Windows. It only covers devices directly attached to your server.
Whoknows
125 pts. | Jul 13 2009 12:38PM GMT
An IPL cleans up your system but does little to correct printer error.
Here are a couple of things to think about.
1 Have you added new patches to your network,
2. Have you changed any drivers for the printer.
3. Has there been any changes to the router.
If the networking group states nothing has changed, try reconfiguring the printer. I have seen that error a couple of times and it makes reference to a configuration.
I do a couple of things for all printers. in order to try and avoid the reconfig at a later time. I have a library in the as400 and once I am happy with a config I do a retrive source, then I always have the original
Also, here is a URL you may find interesting, since most of us customize thru WSCST, this will tell you how to set your options rather than the guessing game. It has all printers.
<a href="http://www-01.ibm.com/support/docview.wss?uid=nas1b44a2cf4ba778d83862568250053649f" title="http://www-01.ibm.com/support/docview.wss?uid=nas1b44a2cf4ba778d83862568250053649f" target="_blank">http://www-01.ibm.com/support/docview.ws…</a>.
Regards,
Mark
TroyBekker
15 pts. | Jul 13 2009 4:49PM GMT
Thanks for the responses to this. I feel really stupid, but it turns out the remote writer had been stopped. I restarted it and everything started printing immediately.
Thanks again!






