HP OpenVMS Systems

LPD and (LPD_UNPRTR) unknown printer?

» close window

The Question is:

 
Trying to configure lpd client for VMS, here is my config:
 
Printcap.dat:
 
 
# LOCAL PRINTERS
 
TCPIP$LPD_QUEUE:\
        :lp=TCPIP$LPD_QUEUE:\
        :sd=TCPIP$LPD_SPOOL:
 
REVOPS_MINOLTA|revops_minolta|Billing Printer:\
        :lf=/SYS$SPECIFIC/TCPIP$LPD/REVOPS_MINOLTA.LOG:\
        :lp=REVOPS_MINOLTA:\
        :ps=lps:\
        :rm=revops-prt03:\
        :rp=CopierBW:\
        :sd=/SYS$SPECIFIC/TCPIP$LPD/REVOPS_MINOLTA:
 
 
I then define sys$print TCPIP$LPD_QUEUE and attempt to print, it errors like
 this:
 
Server queue TCPIP$LPD_QUEUE, idle, on SCORPI::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC
 /OWNER=[SYSTEM] /PROCESSOR=TCPIP$LPD_SMB
  /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR
 
  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    792  LS_PRODUCT      GPAYNE            8  Retained on error
       %NONAME-F-NOMSG, Message number 0764A07C
         Submitted  8-NOV-2001 13:53:05.69 /FORM=DEFAULT /PRIORITY=100
         File: _SCORPI$DRA2:[USERS.GPAYNE]LS_PRODUCT.LIS;2
         Completed  8-NOV-2001 13:53:05.76 on queue TCPIP$LPD_QUEUE.
 
The lpd service is running.
 
Any ideas, I'm completely out of patience with this thing. The printer is a
 Fiery Print Server with a Minolta i520 printer/copier.
 
 
 

The Answer is :

 
  The AlphaPC 164LX series platform is not supported by OpenVMS Alpha,
  and the "Fiery Print Server with a Minolta i520 printer/copier" is
  not supported by the TCP/IP Services product.  But the OpenVMS Wizard
  assumes you probably already knew about that.
 
  Is there anything interesting and relevent included in the specified
  printer log file? (REVOPS_MINOLTA.LOG)
 
  As for the error reported:
 
    $ set message sys$message:tcpip$msg.exe
    $ exit %x0764A07C
    %TCPIP-F-LPD_UNPRTR, unknown printer !AS
    $
 
  Try ping and other diagnostic tools, and check that the printer (or
  printer server) is known and accessable.  Also consider enabling and
  using the LPD diagnostic logical names TCPIP$LPD_RCV and TCPIP$LPD_DEBUG.
 
    $ define/system/executive TCPIP$LPD_RCV   15
    $ define/system/executive TCPIP$LPD_DEBUG 15
 
  Setting these two logical names as shown causes diagnostics to be logged
  into the file TCPIP$LPD_RCV_STARTUP.LOG.
 
  Check that the printer (or printer server) is configured to allow
  this host to print to it.
 
  Since you are attempting to serve the queue via LPD, you will also want
  to determine what the application proxy setting should be for the LPD
  service.  To disable use of the application proxy database, use the
  following sequence:
 
    SET SERVICE LPD/FLAGS=NOAPPLICATION_PROXY
    DISABLE SERVICE LPD
    ENABLE SERVICE LPD
 
  Potentially related topics include (1020) and (1143), and (2756).
 
 

  

     

     
answer written or last revised on ( 26-NOV-2001 )
     
» close window