Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

LPD PrintCap Changed in TCP/IP v5.4?

Robert Atkinson
Respected Contributor

LPD PrintCap Changed in TCP/IP v5.4?

Whilst testing an upgrade from TCP/IP 5.1 to 5.4, I noticed a problem with our LPD queues.

Trying to start a queue gives an 'invalid message' OPCOM message.

It seems to stem from the fact that the PRINTCAP file has changed :-


:sd=/SYS$SPECIFIC/TCPIP$LPD/FTG_START_LABAPPL2:

to

:sd=/TCPIP$LPD_ROOT/FTG_START_LABAPPL2:

Anyone else seen this and know where it's documented?

Also, the TCPIP$LPD_PRINTCAP logical no longer exists - is this normal?

Cheers, Rob.
2 REPLIES
Anton van Ruitenbeek
Trusted Contributor

Re: LPD PrintCap Changed in TCP/IP v5.4?

Robert,

Why on earth are you using LPD on OpenVMS ?
Are you only plain text printing and not using any /SETUP modules ? You cannot use /SETUP when using LPD printers.
We are using for more then 10 years TELNETSYM for printing. Yes we are using /SETUP modules.
Processor TCPIP$TELNETSYM and (for HP it is socket 9100, most HP compatible printers us also the same socketnumber) a socketnumber and you are up and running.

But you're question:
I think the logical TCPIP$LPD_ROOT isn't setup right or the corresponding directory doesn't exists.
The file is probably existing under the name .TEMPLATE . During the upgrade (If I'm recall correct) there is a message about it. We have this file also but we do keep this one anxious empty (only some header stuff etc.)

AvR
NL: Meten is weten, maar je moet weten hoe te meten! - UK: Measuremets is knowledge, but you need to know how to measure !
Robert Atkinson
Respected Contributor

Re: LPD PrintCap Changed in TCP/IP v5.4?

My error....

Although the default specification in PRINTCAP has changed, the real reason for the error is because the directories don't exist.

I'd been reading this through various threads, but my brain chose to ignore the obvious!

Rob.