Strictly from an OS/400 view, we've had this sort of thing happen when users changed an outq to print to a different writer. Generally it was users in a WRKWTR ASTLVL(*BASIC) who didn't understand the options. Ending and starting the writer resets it back to normal. That wouldn't really explain your held/release scenario unless someone was messing with it at the time you looked.
From: Jerry C. Adams
I have one heck of a flaky situation. First, about two weeks ago I connected a PC printer in our warehouse manager's office to our System i
(V5R1) via PC5250 printer emulation. Worked great - until yesterday.
The reports, documents, etc., for the two girls in the office started printing to this new printer (BB), even though the OCL or CL explicitly referenced a different printer. I even changed a procedure so that the report (a one-pager) would be put on Hold. The @#$% thing not only went to BB even though P6 was explicitly defined, but it was released. I ran the same procedure from my workstation and everything was cool.
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.