Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: LPD and CPS software
From: Rick Pim <rick%qucdnee.bitnet@qucdn.queensu.ca>
Date: Sat, 29 Aug 1992 11:03 EST
Reply-To: Rick Pim <RICK%QUCDNEE.BITNET@QUCDN.QueensU.CA>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Envelope-To: cmu-tek-tcp@cmutek.cc.cmu.edu
X-Vms-To: IN%"cmu-tek-tcp@cmutek.cc.cmu.edu"

> are  hays%ponder.ponca.dupont.com@CARNEGIE.BITNET

>We are trying to use CMU-Tek's LPD function to print from a Sun to a VAX
>printer.  The VAX printer is a postscript printer that uses the CPS software.
>The file gets transferred to the VAX and gets queued to the proper queue just
>fine.  The problem is the /PARAMS information.  It has the DATA=ANSI or
>DATA=POSTSCRIPT information ok but it also has some extra information.
>Parameter 6 has the name of the file that was sent for printing and parameter 8
>has the name of the node it was sent from.

>The 6th and 8th parameters are giving the CPS software heartburn.  How can I
>turn this off?  Thanks for your help.

i asked a similar question this past spring; i received a few
suggestions.

joel elston said:
:I went into the symbiont code and
:no-op'd the extra parameters.  That solved my problem - maybe yours is
:similar.

  Herbert Hanewinkel said:
:This is an old problem, I discussed it with Art Stine, who worked on the
:lpr/lpd code at that time, over a year ago.
:
:He provided me a lpd version in which the whole parameter stuff is disabled.
:But this also disables lprm, because the information in the parameters 6-8 is
:used to identify the job and automatic Postscript/Ansi recognition.
:The modified lpd is on my server genmic.biochem.mpg.de.
:

i grapped it and played around for a while: the solution i used was this
lpd and a couple of generic queues. i'm using an old version of the
scriptprinter software; i assume things will be the same now.

my main scriptprinter queue is called "scriptprinter"; i defined two
generic queues, one for postscript and one for ansi:

$ @sys$startup:cps$generic_queue -      ! ANSI queue
        trio_ansi -                     ! P1 - Generic queue name
        scriptprinter -                 ! P2 - Execution queue name(s)
        "data=ansi"                     ! P3 - Default queue parameters
$
$ on error then continue
$ @sys$startup:cps$generic_queue -      ! PostScript queue
        trio_ps -                       ! P1 - Generic queue name
        scriptprinter -                 ! P2 - Execution queue name(s)
        "data=post"                     ! P3 - Default queue parameters

these two queues are the ones fed from the other sites; the patched LPD
removes all the parameters, but the defaults put the important ones back
in. this is a kludge, but it's all that we needed here.

rp
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rick Pim                                            bitnet:rick@qucdnee
Department of Electrical Engineering         rick@qucdnee.ee.queensu.ca
Queen's University, Kingston                     (bitnet:rick@qucdnast)
(613) 545-6772                               (rick@bill.phy.queensu.ca)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Meanwhile... the Carrot is using his keen but unorthodox crimefighting
techniques...
"Are you a gangster?"
                    -- Flaming Carrot
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek