| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 7120.1 | DCPS is the product | NECSC::HARVEY | Printserver Support- America's Zone | Tue Mar 11 1997 12:59 | 8 |
| Renaud,
For VMS systems the product that supports the cpap protocol is DCPS
or DecPrint Supervisor. It only supports printing to LPS series/family
of printserver printers. The DCPS release notes and manuals go into
this support.
Renis
|
| 7120.2 | DCPS V1.4 will provide more TCP/IP connectivity | HANNAH::SCHULLMAN | Dan Schullman | Wed Mar 12 1997 02:06 | 18 |
| To head off some potential confusion...
I believe it was DCPS V1.1 that added support for communicating with
Digital PrintServer printers via TCP/IP. [Previously it was DECnet only.]
PrintServers utilize the CPAP protocol in either case, and no other printers
[to my knowledge] support CPAP.
DCPS T1.4, currently in field test, adds the ability to communicate with
desktop and workgroup printers (and NICs and print/terminal servers) that
support "raw TCP/IP sockets". If you're NOT talking about a Digital
PrintServer printer, this is the support you're probably asking about.
But note that DCPS V1.4 will NOT support the LPD nor Telnet protocols.
I suggest you see the latest DCPS release notes or SPD for more info.
[Pointers are in note 6.]
Hope that helps...
Dan S.
|
| 7120.3 | syntax about the command into dcps$startup | ULYSSE::CHAMEROY | | Wed Mar 12 1997 03:14 | 7 |
| I have put this command, is it Good or not ?
@sys$startup:dcps$execution_queue myqueue """tcpip/tcpiaddress""" dcps_lib "" "/noseparate " "" "" ""
thanks,
Renaud
|
| 7120.4 | reply .3 reformatted | NECSC::HARVEY | Printserver Support- America's Zone | Wed Mar 12 1997 12:14 | 20 |
|
Here is Renaud's reply formatted so that 80 character terminals can
read it:
I have put this command, is it Good or not ?
@sys$startup:dcps$execution_queue -
myqueue -
"""tcpip/tcpiaddress""" -
dcps_lib -
"" -
"/noseparate " -
"" -
"" -
""
thanks,
Renaud
|
| 7120.5 | CONNECT NO NETWORK OBJECT REJECTED | ULYSSE::CHAMEROY | | Thu Mar 13 1997 03:39 | 8 |
| HI,
When I use the previous command I have the error message
Connect to network object reject ????
Any idea ???
thanks renaud
|
| 7120.6 | It works with UCX | NECSC::HARVEY | Printserver Support- America's Zone | Thu Mar 13 1997 11:27 | 17 |
| Renaud,
I have setup DCPS queues using Digitals UCX produc. I make sure
that the ip hostname is set in the ucx database.
@sys$startup:dcps$execution_queue -
myqueue -
"tcpip/ip_hostname_of_printer" -
dcps_lib -
"" -
"/noseparate " -
"" -
"" -
""
Renis
|
| 7120.7 | Yes, the printers is defined on ucx . | ULYSSE::CHAMEROY | | Fri Mar 14 1997 04:57 | 0 |
| 7120.8 | What does the LPS printer think??? | NECSC::HARVEY | Printserver Support- America's Zone | Fri Mar 14 1997 14:57 | 12 |
| Renaud,
Yep UCX is the only supported method for DCPS printing to LPS
printer via IP. However what version of LPS software is loaded on the
printer and using the LPS$console utility what is the data from the
following commands:
version
config
permis
Renis
|
| 7120.9 | VERSION | ULYSSE::CHAMEROY | | Thu Mar 20 1997 04:20 | 6 |
| PRINTSERVER SOFTWARE V5.1-15
DCPS T1.4
VAXELN V4.5
Renaud
|
| 7120.10 | VMS node name? | SHRMSG::HOWARD | Whoever it takes | Thu Mar 20 1997 10:02 | 6 |
| I usually use nodename::"tcpip/ip_hostname_of_printer", e.g.,
TAY2P1::"tcpip/TAY22H8LP17.tay.dec.com". I don't know if this makes a
difference. In V1.4, the correct syntax is to specify DECnet nodes with
nodename::decnet/printername.
Ben
|
| 7120.11 | still need to know more details | REGENT::GALLAGHER | | Thu Mar 20 1997 18:17 | 10 |
|
Re: .9
Yes, but you still haven't determined if the *printer* has been
CONFIGURED to do IP printing. You need to answer all the questions
that Renis posted so we can help you figure that out.
|