HP OpenVMS Systems

Feature missing in TCP/IP V3.3?

» close window

The Question is:

 
$!
$! reverse telnet problem on VAX VMS 5.5-2 with UCX 3.3 ( YES this is very old )
$!
$! I would like to create a TNA device from a COM file.
$! None of the attempts below work.
$! What works is starting telnet from the $ prompt and creating it by hand
$! TELNET> create_session bzsv72 2003 123
$! The response is "%UCX-I-TELNET_CRSES, Session created on TN123"
$! On AXP VMS 7.1 systems running UCX 4.2 ECO 1 I can use the first attempt
$!
$! Is there any way to get it working the way I want on what I have ?
$!
$! Thank you for your asistance
$!
$! Jack Veraart
$! Veraart.Jack@PMIntl.ch
$!
$ set noon
$!
$! first attempt
$!
$ telnet /create_session bzsv72 2003 123
%DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placement
 \CREATE_SESSION\
$!
$! second
$!
$ create telnet_definitions.cmd
create_session bzsv72 2003 123
$ define sys$command telnet_definitions.cmd
$ define sys$input telnet_definitions.cmd
%DCL-I-SUPERSEDE, previous value of SYS$INPUT has been superseded
$ telnet
%SYSTEM-F-IVDEVNAM, invalid device name
$ deas sys$command
$ deas sys$input
$!
$! third
$!
$ tn:=="mcr sys$system:ucx$telnet.exe"
$ tn /create_session bzsv72 2003 123
%SYSTEM-W-NODEVAVL, no device available
%SMG-F-INVPAS_ID, invalid pasteboard-id
$!
$! 4th
$!
$ tn:=="$sys$system:ucx$telnet.exe"
$ tn /create_session bzsv72 2003 123
%SYSTEM-W-NODEVAVL, no device available
%SMG-F-INVPAS_ID, invalid pasteboard-id
$!
$! 5th
$!
$ run sys$system:ucx$telnet.exe -
	/input=telnet_definitions.cmd -
	/output=telnet_definitions.out
%RUN-S-PROC_ID, identification of created process is 000000E3
$ wait 00:00:03
$ type telnet_definitions.out
%SYSTEM-F-IVDEVNAM, invalid device name
 
 

The Answer is :

 
  Clearly, an upgrade would help -- it appears that the function
  you wish to do is not feasible or not available in the (antique)
  version of TCP/IP services in use here.
 
  If you cannot upgrade, please acquire the current (final) ECO
  kit for the TCP/IP Services version in use -- V3.3 -- and try
  using that.  (Though given the particular error reported, this
  ECO kit will probably not help.)
 

  

     

     
answer written or last revised on ( 27-APR-2000 )
     
» close window