FW: Landscape Printing

-----Original Message----- From: Melvin P'rez Cedano [mailto:cam@codetel.net.do] Sent: Jueves 22 de Abril de 1999 3:22 PM To: 'owner-informix-list@iiug.org' Subject: Landscape Printing Could you please help me with this? I'm trying to print landscape from Unix, to a HPLaserjet, attached to a print server. The print server type is Netport Express and uses "proprint" as the interface program. It seems that the program loses the parameters that I send, since it's using the interface program that the print server uses, and doens't print landscape. Thanks in advance, Karina Lorenzo

Marcos Mejia wrote: > > -----Original Message----- > From: Melvin Pérez Cedano [mailto:cam@codetel.net.do] > Sent: Jueves 22 de Abril de 1999 3:22 PM > To: 'owner-informix-list@iiug.org' > Subject: Landscape Printing > > Could you please help me with this? > > I'm trying to print landscape from Unix, to a HPLaserjet, attached > to a print server. > > The print server type is Netport Express and uses "proprint" as the > interface program. > > It seems that the program loses the parameters that I send, since > it's using the interface program that the print server uses, and > doens't print landscape. Context? I suspect I4GL, but it might be D4GL or NewEra or ISQL. Not that the answer differs very much, but at least if you give us a complete statement of the problem, we can help more reliably. Also, if you specify the version and the commands you are using, we can avoid making suggestions which you've already tried. How are you printing to the printer... If it is some variant of START REPORT repname TO PRINTER, then the command used defaults to 'lp' (or on some systems, 'lpr'). If you are using 'proprint' instead, you might be setting the environment variable DBPRINT='proprint'. Or you might be setting it to something more complex like 'proprint -l' where the hypothetical -l option is used to mean 'print landscape'. If you are specifying the arguments in the DBPRINT environment variable and they are being ignored, then you may have a bug, or you may simply not be setting the environment correctly. I'd debug by changing the value of DBPRINT to my own shell script that dumped the command line and the environment to a log file somewhere and then ran the proprint command. If you aren't using this, you are probably using a variant of START REPORT repname TO PIPE printcmd where printcmd is either a string variable or a string literal. If you are using a string literal and the literal contains the necessary arguments, then again you may have a bug. If you are using a variable, have you got enough space in the variable for the arguments too? A classic bug would be to have code like: DEFINE s CHAR(9) LET s = "proprint -l" START REPORT repname TO PIPE s Since s only stores 9 characters, the '-l' is omitted, leading to the symptoms you describe. Again, you can debug this by substituting your own shell script in place of the command you though you were running and logging the relevant info. An example of such a script is: ( echo date echo "Command: $0 $*" echo "Environment:" env ) > /tmp/debug.log.$$ exec proprint "$@" If none of these scenarios covers your problem, then you need to describe your problem in more detail. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>