1753486 Members
4381 Online
108794 Solutions
New Discussion юеВ

Printer problem

 
Willem Grooters
Honored Contributor

Printer problem

My client has a number of PC's with (HP) printers attached in his network. These PC's arer used as printer server.
On a VMS cluster on one location, printer queues have been defined to access these printers from VMS.
On another (remote) and newer cluster, the same thing. All required files have been copied from the first cluster to the other, but renamed. The queue definitions reflect this namechange.

On both clusters is VMS 7.3-2, same TCPIP version (not sure which one), and, AFAIK, all relevant patches have been applied.

On the first cluster, printing from the VMS machine is correctly executed. Ifvthe same file is printed from the other cluster, lines are concatenated as if line ends (CR/LF) are not sent or recognized.
The funny thing though is that this excercise has been done with another cluster, and theer is no problem at all.

We've been thinking on forms not defined or not loaded but that seems all ok.

What are other alternatives?

Willem

Willem Grooters
OpenVMS Developer & System Manager
13 REPLIES 13
Craig A Berry
Honored Contributor

Re: Printer problem

These are LPD queues? You've probably done all this, but compare the results of these on the one that's working and the one that's not:

$ TCPIP SHOW SERVICE LPD/FULL
$ SHOW LOGICAL TCPIP$LPD*

and look at the configuration file (I think it's called TCPIP$LPD.CONF or something like that).

Willem Grooters
Honored Contributor

Re: Printer problem

No LPD queues.

The attachment shows one of the queues that show this behaviour, both old and new cluster.
10.21.8.154 is one of the PC's.

Willem Grooters
OpenVMS Developer & System Manager
Martin Vorlaender
Honored Contributor

Re: Printer problem

Okay, so these are Telnet queues. Do logicals TCPIP$TELNETSYM* show different values?

cu,
Martin
David B Sneddon
Honored Contributor

Re: Printer problem

Willem,

The obvious difference is the use of the
/SEPARATE=(RESET=(KYO_RESET)) and the use of
/NO_INITIAL_FF and DEFAULT=(FEED,FORM=)
Try setting them up EXACTLY alike and check
for any differences in the *TELNETSYM* logicals.


Regards
Dave
Willem Grooters
Honored Contributor

Re: Printer problem

$ SHO LOG TCPIP$TELNETSYM* - see attachment

One I could now think of is TCPIP$TELNETSYM_RAW_TCP, but the point is that another site has no problems, and so we cannot change this on the fly.

Willem

Willem Grooters
OpenVMS Developer & System Manager
Wim Van den Wyngaert
Honored Contributor

Re: Printer problem

Willem,

What is /PROCESSOR=TCPIP$TELNETSYM1 (1 ???)

Wim
Wim
Richard Hafke
New Member

Re: Printer problem

Hallo Wilhelm,

Ithink your printing happens on different Printers?? If so, are the printers configured identically for TCP/IP-Printing.
With our Kyocera-Printers we had the same affects, when they are not configured correctly.

Richard
Willem Grooters
Honored Contributor

Re: Printer problem

Thnaks Wim,
this is something to overlooked completely! What it is, I don't know, probably an old TELNETSYM version?

Client has been informed - He will start eliminating all differences.

Willem
Willem Grooters
OpenVMS Developer & System Manager
Art Wiens
Respected Contributor

Re: Printer problem

How about that you have renamed your form BBN_DEFAULT and your library BBN_PRINTLIB1 ... are these both identical defined on both clusters? The forms call the same setup modules which exist in both text libraries and are the same?

Art