HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- LPD PrintCap Changed in TCP/IP v5.4?
Operating System - OpenVMS
1827855
Members
1671
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2005 01:11 AM
04-14-2005 01:11 AM
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.
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 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2005 02:46 AM
04-14-2005 02:46 AM
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
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 !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2005 02:49 AM
04-14-2005 02:49 AM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP