It looks like your printers are setup as devices on the as400. Change it to a remote outque. We had similar issues and after changing our printers from devices to remote outqueues we've not had this issue.
The root of the issue is how printer devices on the as400 handle hardware errors on the printer. If there is an error on the printer or perhaps the printer went into standby mode and stops accepting connections from the as/400, the as400 in reacts by shutting down the writer that is associated to the outqueue that is attached to the printer device. When this happens print jobs queue up in the outqueue and sit there with a *SND status..until the writer is either started manually or the some other action is taken to start the writer. Once that happens, things begin printing again.
Benefit of changing printer devices to remote outqueues is that if the as400 encounters the same scenario described above, it does not automatically stop the writer associated with the remote outqueue. The writer remains active and the system continues to try to send output. Once the error on the actual printer is resolved and communication is reestablished, the jobs start printing again because the writer is still active.
[ QUOTE ]
Thanks for the reply. I looked into the management central and wasn't able to find anything that monitors the queues for jobs stuck at snd status. If I cannot determine the root cause, I would like to at least be able to automatically hold the offending job so the remainder of the docs would be able to print....
[/ QUOTE ]