Technical article 110497

The Printer Manager, lpstat, and lpadmin functions fail to identify printers with SLS OSS497 installed.

OpenServer 5.0.5

Written · Last revised

Problem

The Printer Manager cannot retrieve the information about my remote
LPD/RLP printer(s).  It functions correctly for other printers after
I acknowledge the error.  The lpstat and lpadmin commands may also
fail.

An error message similar to this may appear while running the Printer Manager:

Unable to get complete data for 'Printer Manager on <hostname>' Failed to retrieve list of remote printers. General failure occurred in processing attribute remotePrinterHost Cannot find an entry for printer 'foo500' in /etc/printcap.

Cause

The Printer Manager in SCO OpenServer 5.0.5, with Support Level
Supplement (SLS) OSS497 (all versions), is unable to retrieve
information about the remote printer when the /etc/printcap "rp="
mnemonic (Remote Print Queue name) differs from the local queue
name (the first field of printcap).  See printcap(F) for more
information.

A printcap entry that may cause this problem will look similar to this:

foo200:\
      :lp=:rm=host.dom.com:rp=foo500:sd=/usr/spool/lpd/foo500:

(Note that the first field does not match the rp= field.)

Solution

This problem is fixed in SCO OpenServer Release 5.0.6.

For SCO OpenServer 5.0.5, you cannot edit the 'rp=' mnemonic and
use the Printer Manager, lpstat, and lpadmin functions for this
device.  If your print server or network card requires that you
use specific settings in this field, then it must match the name
of the print queue as it is known to the local (client) machine.
The local queue name must be unique.  This may prevent you from
using multiple ports of a multiport print device and multiple
print devices that require the same "rp=" value in /etc/printcap.
NOTE: This only applies to systems that have SLS OSS497 (all
versions) applied.  You may still edit the "rp=" value to
accommodate your print devices, but the printer manager, lpadmin,
and lpstat commands may fail.

From the Xinuos technical article database, record 110497. Reproduced with permission. The original is at www.sco.com/ta/110497, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.