dreport spools output to wrong printer

[Barry Wiseman]

Kenneth Brody wrote:
> Quoting Barry Wiseman (Fri, 29 Jul 2005 15:58:10 -0400):
> 
> 
>>Spent this afternoon pounding my head over a report that filePro was
>>stubbornly sending to the wrong printer.
> 
> [...]
> 
>>config file had (irrelevant entries omitted):
>>
>>printer7 = jeff,dr_hp3,lp -s -djeff,Jeff's printer
>>printer8 = mary,dr_hp3,lp -s -dmary,Accting printer
>>printer9 = dr_hp3,dr_hp3
>>
>>Output table had Printer name: dr_hp3
>>
>>With no -p on the command line, no value in LPDEST, no "printer"
>>statements in processing, I would expect the report to go to the default
>>printer, "hp8100".  Instead, it was going to "jeff".
> 
> 
> The output format had the printer name "dr_hp3".  Therefore, since
> printer7 is of type "dr_hp3", it went there.  (That is, "jeff".)
> 
> Why would you expect filePro to go to the default printer, when the
> output format specifies "dr_hp3"?
> 
> This is the expected, documented behavior.

I thought the "Printer name" in the output format refers to entries in 
the "Name" column in pmaint.  You're telling me "Printer name" specifies 
not printer name but printer type.  Silly me.

> It's still picking printer7 (the first "dr_hp3").  However, since
> this has no destination specified, it uses the default.

It does *not* use the default.  Whose default?  Filepro's?

	pfprinter = default
	printer1 = default,default,lp -s

Linux's?

	system default destination: hp8100
	device for hp8100: socket://192.168.1.4:9100
	device for jeff: socket://192.168.1.5:9100
	device for mary: socket://192.168.1.6:9100

Seems to me only by specifying printer name "jeff" (either in the output 
format or in processing) should filePro ever launch an "lp -djeff" command.

Let's render this more generically:

printer1 = foo,laser,lp -dprinter1
printer2 = bar,laser,lp -dprinter2
printer3 = laser,laser,lp

Doesn't this mean that 'printer name "foo"' would use printcode table 
"laser" and spool output to printer1?  And 'printer name "laser"' would 
again use printcode table "laser" but spool to the OS's default printer?

Problem seems to be the use of "laser" as both a printcode table name, 
and also a printer name.  Is this an unexpected event in filePro?

The possibly confused for many years
Barry Wiseman