AS/400 print job goes into a *SND state

Problem:

When attempting to print from the AS/400, the spool file immediately goes into a sending (*SND) status but does not print. No messages are logged in the RPM log when this happens.

Answer:

There are a number of settings on the remote AS/400 OUTQ that can result in this issue. To resolve, verify the OUTQ settings match the recommended settings on our AS/400 setup instructions.

To begin modifying the OUTQ, follow these instructions.

  1. From an AS/400 command prompt, issue this command, substituting your OUTQ name where appropriate: ENDWTR outq_name *IMMED. Press Enter.
  2. Wait 15 seconds, then issue this command, again substituting your OUTQ name where appropriate: CHGOUTQ outq_name. Press F4 to prompt. If you press the Enter key, start again from step 1.
  3. Press F9 to view all parameters, then compare your settings with our AS/400 setup instructions.

Also, verify the RPM host's IP address or DNS hostname are configured properly, and that there are no firewalls between the AS/400 and RPM that can be blocking the connection, including the Windows XP Service Pack 2 firewall. If the Windows Firewall is the cause, click here for assistance.

 

Article 101-02

Issue: Connectivity
Topic: AS/400 (i5/OS)

Did this information answer your question?

Your email address (optional):

Please provide additional comments. We welcome your feedback.

Case Studies
Satisfied customers using Brooks' software in their print environments to simplify document workflows.
 
 
IPDS Printing
Print IPDS files to any of your PCL-supported printers for ONLY $495!
 
 
Host to Windows
White Paper  Simple tools for connecting IBM-based data with the Windows® world
 
 
Print to File
RPM writes to disk incoming data from ANY host system, checks for duplicates...
 
 
AS400 Printing
RPM applies all the features of Windows printing to your AS/400 (iSeries / zSeries) spool files
 
 
UNIX to Windows
RPM enhances UNIX print services' ability to customize and control processing