HP OpenVMS Systems

DECnet Task Object?

» close window

The Question is:

 
We are currently converting fortran code from a Vax to Alpha platform. On the
 Vax there is an image that is defined as a decnet object (phase IV) that was
 accessed by another Vax. On the Alpha, which has decnet phase V, I defined
 that image as a session c
ontrol application, but when the Vax tries to access the application we are
 receiving "Network object is unknown at remote node". On the Vax side, I'm
 using  SYS$QIOW and in the statement we use a 'nodename::"TASK=application
 name"', is this correct when
going from Vax to Alpha?
 

The Answer is :

 
  DECnet-Plus supports the DECnet task object.
 
  The task object is typically a DCL procedure or executable image in
  the target username default directory for the incoming DECnet network
  connection -- you will want to parallel the FAL server, for instance.
 
  For a DCL example of using the task object, please see topic (159).
  Also see (6357) for a related discussion, and see the examples of
  a declared object or declared task as referenced in (7359) and as
  particularly described in the DECnet programming documentation.
 
  The OpenVMS Wizard would also look at a switch to the $qio interface
  for the TCP/IP Services (TCP) network protocol, as described in the
  TCP/IP Services programming documentation.

  

     

     
answer written or last revised on ( 16-JUL-2003 )
     
» close window