[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

5414.0. "UCX-F-LPD_LONGPRCAP error" by CSC32::CAWOOD () Fri Apr 04 1997 14:21

    I can find no documentation whatsoever on the error (amoung other
    errors, but this the only one I'm concerned with now):
    
      UCX-F-LPD_LONGPRCAP
    
    I have a customer ( UCX 4.1 ECO 4) who has been seeing this.  It
    *appears* to be related to an incorrect queue name on an inbound
    printcap entry.
    
    Any direction on what this error means and what will cause it to be
    generated is appreciated.  Furthermore, is there a *complete* list of
    current UCX errors and what they mean/causes?
    
    Thanks in advance,
    Greg Cawood
    CSC MULTICOMM team (now supporting UCX LPD and TELNETSYM)
T.RTitleUserPersonal
Name		DateLines
5414.1Any info?CSC32::CAWOODMon Apr 21 1997 11:004
    Any info is appreciated.  Otherwise I will be IPMT'ing this.
    
    Thanks,
    Greg
5414.2seen itUTRTSC::KNOPPERSOswald KnoppersTue Apr 22 1997 02:2232
I assume you see this error in the UCX$LPD_RCV_STARTUP.LOG file? I have
seen this when incoming jobs arrive for a queue which is not configured
(with lprsetup) in the ucx$printcap.dat file.

The logfile ends with:

%%%%%%%%%%%%                   22-APR-1997 08:18:18.51  %%%%%%%%%%%%
%UCX-F-LPD_LONGPRCAP, Printcap entry too long




%UCX-F-LPD_LONGPRCAP, Printcap entry too long
  UCX_LPD      job terminated at 22-APR-1997 08:18:18.97

  Accounting information:
  Buffered I/O count:              86         Peak working set size:    1505
  Direct I/O count:                46         Peak page file size:      5946
  Page faults:                   4494         Mounted volumes:             0
  Charged CPU time:           0 00:00:04.53   Elapsed time:     0 00:00:06.71

And on the sending system we see:

%%%%%%%%%%%  OPCOM  22-APR-1997 08:18:20.03  %%%%%%%%%%%
Message from user SYSTEM on AUSSIE
%UCX-E-LPD_LOSTCONNTO, Lost connection to host !AS

Adding the destination queue in the printcap file solves this.

Hope this helps,

Oswald