This solution is likely to be the most problematic in the long run.
This solution consists of a PC or Mac running software that allows it to accept Unix style lpd jobs and pass them directly to a connected printer.
IMPORTANT: The software MUST be running on the PC for print jobs to pass through the PC to the printer. This program is in ADDITION to the SAPGUI program used to access the AMS system. If the utility program is not running, print jobs will simply queue up waiting for your PC to accept them.
In the PC environment, the software is provided by SAP and is called SAPLPD. If you have the SAPGUI software to access the AMS system installed, then you already have SAPLPD.EXE. It should be located in the same directory as the SAPGUI.EXE. This is simply started in Windows and thats it. If you want it running all the time, then you must create an icon for it and put it in your Windows startup group or add it to the load= line of your win.ini. Note: In order to run SAPLPD you must either register the IP address of your workstation or add a line to your HOSTS file on your PC to associate a NAME to your IP address. I the default installation, use a text editor to edit C:\LWP\TCP\HOSTS which contains a few entries. Add a new one after the last entry that includes your IP address (SAPLPD reports your IP address when you try to start it) and a one word name for your PC. Save it and try SAPLPD again.
With SAPLPD, the “lpd hostname” is simply the IP address of your PC. The “lpd queue name” is simply the port that the printer is attached to. Usually LPT1.
In the Mac (Apple) environment, SAP does not provide an equivalent to SAPLPD. There are public domain versions of lpd for Mac. Some people are successfully using MACLPD on campus. Click here to download a BINHEX file containing maclpd and configuration files.
This solution is the cheapest because it is accomplished with free software.
I consider this the least stable solution because the printing is dependant on the configuration of the individual user PC or Mac. It is easy for people to change Windows or Mac configurations without understanding the dependancies. Moving their printer to a different port. Two printers on a switch box. Buying a new printer. These can all result in print problems that might be difficult to diagnose. Certainly it requires that the user be aware of the dependancy and the fact that a change in the print configuration at the PC might require a change in a configuration at the AMS system. Typically LAN administrators are aware of such things. Typically users are not.
For some users this may be the only alternative. For many this solution will work well. For others this will be a disaster.
This approach can also be used in a Novell environment for a very low cost solution. Take an old machine with a network card that is nearly useless for other tasks (a 386SX for example). Connect to a Novell server and capture up to 9 LPT ports to up to 9 Novell queues and then run Windows and SAPLPD to allow up to 9 lpd paths through to Novell queues. I cannot say for sure what kind of performance you could expect from this, but it does work.