Showing posts with label IBM AS/400. Show all posts
Showing posts with label IBM AS/400. Show all posts

Saturday, January 30, 2010

LPR/LPD Printing

What is LPR/LPD?

LPR/LPD is a printing protocol that runs over TCP/IP. Originally implemented for BSD UNIX, its use has spread into other platforms such as AS/400 and legacy mainframe systems. It has essentially become a de-facto industry standard for cross-platform and platform-independent printing, which is a huge advantage of LPR/LPD printing.

The specifications for LPR are defined by the Internet Engineering Task Force (IETF) in Request for Comment 1179 (RFC-1179).

LPR stands for Line Printer Request. It refers to the process that sends print jobs to a remote printer or print queue. It is requesting the service of a print server, so it is the client side of LPR/LPD, and thus is often called the 'LPR client'.

LPD stands for Line Printer Daemon. It refers to the process that accepts print jobs from the LPR client. It is providing a service, so it is the server side of LPR/LPD, and thus is often called the 'LPD server. A daemon is a process running on a UNIX machine, providing services.

How does LPR work?

LPR client sends a request to port 515, the standard port for the LPR/LPD protocol. And the LPD server listens on the same port 515.

When the LPR client sends a print job to the LPD server, it send two files: a data file (the actual data to be printed), a control file.

The data file contains the actual data to be printed. It can be binary of text, depending on the actual format of the print file, or the application that generates the print file.

The name of the data file should start with "dfA", followed by a three digit job number, then followed by the host name that has constructed the data file.

The control file contains information that describes the data file (such as the format of the print data file, e.g., postscript, plain text, FORTRAN carriage control, etc.) and what to do with the data file (such as printing banner page, delete after print, or email after print).

The control file is a plain text file, and its file name should start with "cfA", followed by a three digit job number, followed by the host name which has constructed the control file.

Obviously, the "d" in the "dfA" prefix means data, and the "c" in the "cfA" prefix means control.

RFC-1179 does not impose on the order of the two files to be sent; i.e., one can send the control file first, or the data file first. However, some implementations may stipulate one way or the other, e.g., data file first, followed by control file.

In the future, we will show you how to print from non-windows systems to windows systems using this LPR/LPD protocol.



Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.

 


Friday, August 28, 2009

UniPrint Host Edition licensing

UniPrint Host Edition enables user to print from host systems (such as Sun’s Solaris, IBM’s AS/400, Linux, etc.) to their Windows desktop machines.

UniPrint Host Edition uses a totally different licensing model from the core UniPrint SbC products or UniPrint VDI Edition. UNiPrint Host Edition uses per usage licensing, and the usage in the Host Edtition is number of pages printed.

You will need the following information to generate a UniPrint Host Edition license file:

  • The machine name on which UniPrint Host Server is be installed. (You need to install the Host Edition first prior to requesting a Host Edition license.)
  • The IP address of the machine above.
  • A serial number that you obtained from your supplier (a reseller, a distributor, or the vendor).
  • Install Code: This information is available only after you installed the software. So, you need to install the software first, and record the install code from the UniPrint management console.
  • The number of pages you are licensed to print.

As of writing, the initial value for the number of pages in a Host Edition license is 60,000 pages, and you can order additional bundles in increments of 10,000 pages.

All these values will be reset at the beginning of the calendar year. For example, let’s say you have a 60,000-page license and you used up 56,000 pages by December 31 of the year. Comes January 1 of next year, and you’ll get your full 60,000 pages back for the entire year. However, you cannot carry the remaining 4,000 pages into next year so that you can have 64,000 pages in your reserve.

You can set it up in the Host Edition management console so that you’ll receive notifications through emails when you approach within a certain percentages (e.g., 10%, 5%) of the limit of your license.


Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.