Skip to Content
avatar image
Former Member

How do you print from SAP to Networkprinters ?

What is the prefered (best) way to print from SAP on i5/OS ?

Hi together,

I know all the discussions about printing.

I have read a lot of notes and I know about the difficulties to "U" and "S".

How do you spool to the printers?

"U" is not good, I know.

"C" is also not good, if the remote printer doesn't work fine. So always a operator has to take care that the printqueues are working.

We now plan to get "U" to a Windows print-server with all the printer Queues. This makes it possible for the enduser to look at the spooling queue, when the printer is the same, which is installed to his computer.

How do you sppol from SAP to Networkprinters?

Best regards,

Carsten Schulz

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Nov 04, 2008 at 06:38 AM

    Hi Carsten,

    most of my customers are "just" using U (the very bad option) !

    => It mostly runs very stable, is easy to configure and everybody is happy. If one or two printers per company do have issues, these ones are fixed with C or in exceptional cases with U to a Windows print server.

    If you use Windows print servers anyway, this is a pretty fine option 😉

    You just should make a decision if you want to install the Unix print services from Microsoft or perhaps better SAPsprint from SAP. Then you can use the preferred option S instead of U and you are better supported by SAP.

    If you use your printer as LPR in Windows, be aware of the famous "feature" of MS:


    Name: UseNonRFCSourcePorts

    Type: REG_DWORD

    Values: 0 = uses the Ports 721-731 only (that is the default if this key is missing) !!!!

    1 = uses the available Ports 1024 - 65535

    => MS knowledge base 179156:

    This caused 4 (?) minutes print delays at several of my customers, switching to Windows print servers ...


    Volker Gueldenpfennig, consolut international ag - -

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Volker,

      the first problem is to detemine which printers are effected to a hanging problem.

      If I change teh hanging devices to 'C' than I have perhaps some more operation overhead, if the remote print queue will not work proper. And we have tested remote 'queue'ing on our SAP iSeries als well as on our not SAP iSeries. We have several hangups to remote printqueues a week.

      And to find the printers who causes the spool-workprocess long waiting times, I have no idea how to do this.

      Especialy when I read this note:

      A characteristic of network access types 'U' and 'S' is that any network problems lead directly to the spool work process being interrupted. This interferes with the processing of print requests, with the consequence that printers which are not driven by a network access type but still linked to the same spool work process are also affected.

      (from Note 19706 Version 19 english.)

      And for the second: I think there is a difference from running an CI on iSeries or Windows. Because, if I use Windows as operatingsystem then I can use 'C' for using SAPSprint and on iSeries I need to use 'S' or 'U' to use a Windows printserver, or not?

      best regards,

      Carsten Schulz