Title: | DEC TCP/IP Services for OpenVMS |
Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
Created: | Thu Nov 17 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 5568 |
Total number of notes: | 21492 |
Hi, I have a customer that is running UCX 4.0ECO 3 and would like to have a Telnet print queue associated with a TN port. We have done the following: $ telnet /create_session hostname 2008 99 $ init/queu/start/proc=ucx$telnetsym/on=tna99: pq %system-f-ivdevnam, invalid device name We can copy files to TNA99: without any problems. Can a telnet printer queue be setup this way? If so, how? Thanks, Mike
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5183.1 | Try working with a dummy LAT device | CSC32::R_WILLIAMS | Fri Jan 31 1997 15:46 | 11 | |
Mike, Outbound TNA devices are not ready yet for printing as they cannot be spooled. Have your customer create a dummy lta device and then associate the telnetsym to this device. $ mc latcp create port LTAnn: $ set device/spool=(yourtelnetsymquename, sys$sysdevice:) LTAnn: $ copy tobeprinted.stuff LTAnn: -Rick | |||||
5183.2 | UTRTSC::KNOPPERS | Oswald Knoppers | Mon Feb 03 1997 02:26 | 4 | |
If an outbound TN device is to be used for printing, you would not be using the telnet symbiont but probably the ordinary VMS print symbiont. Oswald | |||||
5183.3 | UCXAXP::GEMIGNANI | Tue Feb 04 1997 22:04 | 7 | ||
Agreed. The TELNETSYM is intended to create an outgoing (socket-based) connection to a remote printer. The TN approach is different and doesn't mix and match with TELNETSYM. A future release of UCX will include a really nice TN interface. |