0 pts.
 Printing from AS/400 blocks sometimes.
Dear all, since we moved from the former S36 OS to the new native AS400 OS, we experience some printing problems. Now and then the printer (Lexmark T630) suddenly stops printing the job (no out of paper here!). We have a workaround to go into the old S36 OS and give the command: S P,(old printer-ID). The printer then resumes his task. Sometimes the whole job starts printing again from page 1. Anybody can help here? Thanks in advance!

Software/Hardware used:
ASKED: April 6, 2005  4:18 AM
UPDATED: April 7, 2005  8:29 AM

Answer Wiki:
I'm wondering if you are using the system 36 environment on the AS400 (i.e. legacy programs). There may be a conflict between the device description in the AS400 and it's counterpart in the S36 environment. There is a way to report said problems directly from the AS400 to IBM so that they can suggest a PTF or create one if one doesn't exist.
Last Wiki Answer Submitted:  April 6, 2005  8:50 am  by  Nfeliciano   200 pts.
All Answer Wiki Contributors:  Nfeliciano   200 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

As a former 36er (still running some 36e stuff), I can sympathize with you. But you should start using iseries printer commands. The sys36 had a more intuitive user interface for printing and spool commands, but the equivalent is on the as400.

First you have to determine why the job is stopping.

Use WRKOUTQ and it will show you all outq’s. You can enter a 9 for writer messages. If you enter 5, you can see the individual spool files. Enter a 2 to work with it to restart printing at a specific page, etc.

Also use the joblog to see if any error messages show up there.

You can WRKS36 to display the 36 environment and see how your printer names mapped to the as400 environment. When I add a new printer and give it an as400 name, the 36e gives it a 2 character workstation id. Make sure you know what outq belongs to what printer.

I remember when the AS400 was new to me I was frustrated that the easy to use sys36 spool commands became hidden and complicated. Not to mention I now had printers, printer files, writers, outqs and spool files.

Yeah, you can do more with as400 print/spool, but the basic day to day stuff was easier on the 36.

 0 pts.