HP OpenVMS Systems

Net-Work and TCPware error?

» close window

The Question is:

 
We are currently using Net-Work V3.2.3 with Adabas V4.1.1 and Natural
 V4.1.2(SoftwareAG products) running on DEC VAX with OpenVMS V7.2 and TCPWare
 V5.3-2.
 
We have been using Net-work configured with the decnet protocol to communicate
 to Net-work on the mainframe. This has been working successfully over the
 years. We are now trying to configure Net-work with the TCP/IP protocol as we
 are trying not to use DE
CNET. We are being unsuccessful thus far on different versions of TCPWare.(see
 error below). I have loaded a trial copy of Digital's TCP/IP services and the
 transmissions works fine.
It seems that NET-WORK was written with Digitals UCX compatibility.
 
Is there anyone that can help me with this problem or do I need to get Digital
 TCP/IP services loaded on my VAX's. Thanking you in advance..
The message from the NET-WORK logfile
 
%LIB-E-ACTIMAGE, error activating image
 $1$DIA0:[SYS0.SYSCOMMON.][SYSLIB]UCX$ACCESS_SHR.EXE;
 
 
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000,
 PC=00000002, PSL=03C00000
 
          Context information
          00078220 :  322E3756
          00078224 :  20202020
          00078228 :  00000013
          0007822C :  00000003
          00078230 :  13000202
          00078234 :  00000000
          00078238 :  01D40000
          ...
 

The Answer is :

 
  For assistance with third-party packages such as TCPware, please
  contact the vendor -- TCPware is a Process Software product, and
  the OpenVMS Wizard is not familiar with NET-WORK.
 

  

     

     
answer written or last revised on ( 17-DEC-2003 )
     
» close window