Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Print Server / Remote OUTQ ignoring copies

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Print Server / Remote OUTQ ignoring copies

    We have a romote OUTQ using a print server and we are not getting the number of copies specified. When I monitor the output using WRKSPLF, I see the number of copies specified as 2 when the status of the output is 'SND' but only one copy comes out. Any ideas / suggestions? Thanks
    Tags: None
  • #2
    Print Server / Remote OUTQ ignoring copies

    That's a feature of using a remote outq. You can change some of the spool file attributes of a spool file in a remote outq, but, number of copies and page range no worky.

    Comment

    • #3
      Print Server / Remote OUTQ ignoring copies

      Joe - End the writer and enter "CHGOUTQ outqname DESTOPT('XAUTOQ XAIX')". (XAUTOQ and XAIX must be in uppercase.) HTH, Steve

      Comment

      • #4
        Print Server / Remote OUTQ ignoring copies

        That worked great. Thanks. What did I do?

        Comment

        • #5
          Print Server / Remote OUTQ ignoring copies

          Joe - From IBM Knowledge Base - Destination options (DESTOPT) Specifies destination-dependent options. This is typically set to 'XAIX' (all uppercase) at R440 OS/400 and above and set to 'XAUTOQ XAIX' (all uppercase) at all previous versions of OS/400. The XAUTOQ value specifies that the remote writer is to save the *USERASCII data stream in an LPDxxxxx spooled file whenever the print server, PC or Unix server times out, then the LPDxxxxx spooled file can be sent without further transformation to ASCII once the writer makes another connection to the printer. The XAUTOQ processing is done automatically at R440 OS/400 and above. Without XAUTOQ processing, large OS/400 spooled files could stay in SND status indefinitely. The XAIX value specifies that the remote writer is to send the spooled file to the printer multiple times if the number of copies is greater than 1. It is recommended to use the XAIX value in the destination options (DESTOPT) parameter, but there are times when it should not be used. With XAIX specified, the remote writer opens the connection to the printer and sends down multiple copies of the print data and control file pair. Each control file contains one print command for the data file that preceded it. This method is required for printers, which start printing the data right away. However, there are some print servers which will close the connection after the first copy is sent. This is an unexpected close, resulting in retrying to send from the beginning which will cause the remote writer to loop forever and will cause the spooled file to be printed indefinitely. In this case, XAIX should not be used. When XAIX is not specified, the data file and control file will be sent once, but the control file will contain multiple print commands. This reduces network traffic, but can only be used with servers which can buffer all the data before knowing how many copies to print. Therefore, without XAIX specified, the print server may or may not print multiple copies of the OS/400 spooled file. Also, if you're interested in printing page ranges, download the SAVF from http://www.as400service.ibm.com/s_di...8386256624004b 527e?OpenDocument&ExpandSection=2 and follow the directions on the page. HTH, Steve

          Comment

          • #6
            Print Server / Remote OUTQ ignoring copies

            Thanx Steve. Looks like they have fixed the problems that I ran into. Glad to see that it works now.

            Comment

            Previous template Next
            Working...
            X