Conference pamsrc::decmessageq

2840.0. "DMQ3.2 and PATHWORKS7.2" by CARDHU::GUY () Mon Apr 07 1997 10:14

    I tried to run DMQ320 ON WINDOWS05 and have installed PATHWORKS7.0
    When I try to attach to a permanent queue on the VMS server running
    DMQ3.2A I get the following trace file :
    
    Does DMQ3.2 work with PATHWORKS7.0 ?
    
    Thanks.
    
    Jean-Paul.
    
Mon Apr 07 15:02:54 ( 4294822639 ) DECmessageQ for Windows Client
Mon Apr 07 15:02:54 ( 4294822639 ) Version 3.2.32.003, Win32 DLL (Ix86), TCP/IP or DECnet using Windows Sockets 1.1
Mon Apr 07 15:02:54 ( 4294822639 ) DLL path: C:\DMQ320\BIN\DMQCL32.DLL
Mon Apr 07 15:02:54 ( 4294822639 ) << Entering pams_attach_q >>
Mon Apr 07 15:02:54 ( 4294822639 )   q_name_len: 13
Mon Apr 07 15:02:54 ( 4294822639 )   q_name: QUEUE1_RDBVIA
Mon Apr 07 15:02:54 ( 4294822639 ) CLBind_FindBinding
Mon Apr 07 15:02:54 ( 4294822639 ) ClSrv_GetServer, Default
Mon Apr 07 15:02:54 ( 4294822639 ) Using config file C:\DMQ320\BIN\dmq.ini
Mon Apr 07 15:02:54 ( 4294822639 ) ClServerCreate
Mon Apr 07 15:02:54 ( 4294822639 ) Created Server 5310012
Mon Apr 07 15:02:54 ( 4294822639 ) Default Server Info:
Mon Apr 07 15:02:54 ( 4294822639 )   Transport:	DECnet
Mon Apr 07 15:02:54 ( 4294822639 )   Hostname:	RDBVIA
Mon Apr 07 15:02:54 ( 4294822639 )   Endpoint:	6000
Mon Apr 07 15:02:54 ( 4294822639 ) ClSrv_GetServer, Failover
Mon Apr 07 15:02:54 ( 4294822639 ) Using config file C:\DMQ320\BIN\dmq.ini
Mon Apr 07 15:02:54 ( 4294822639 )   Automatic Failover is not enabled
Mon Apr 07 15:02:54 ( 4294822639 ) CLBind_BindToServer
Mon Apr 07 15:02:54 ( 4294822639 ) CLBindingCreate
Mon Apr 07 15:02:54 ( 4294822639 ) CLBindingCreate, created 5310112
Mon Apr 07 15:02:54 ( 4294822639 ) CLBind_AllocateBuffer, 32748 bytes
Mon Apr 07 15:02:54 ( 4294822639 ) Using config file C:\DMQ320\BIN\dmq.ini
Mon Apr 07 15:02:54 ( 4294822639 ) CLBind_ConnectToServer
Mon Apr 07 15:02:54 ( 4294822639 ) WSA Socket info:
Mon Apr 07 15:02:54 ( 4294822639 )   Description:     Microsoft Windows Sockets Version 1.1.
Mon Apr 07 15:02:54 ( 4294822639 )   Highest Version: 1,1
Mon Apr 07 15:02:54 ( 4294822639 )   System Status:  Running on Windows 95.
Mon Apr 07 15:02:54 ( 4294822639 )   MaxSockets:      256
Mon Apr 07 15:02:54 ( 4294822639 ) WSASetBlockingHook using DmqCL_BlockingHook
Mon Apr 07 15:02:54 ( 4294822639 ) Load DECnet library for NIO object: 510970
Mon Apr 07 15:02:54 ( 4294822639 ) 32-bit DECnet support is not available!
Mon Apr 07 15:02:54 ( 4294822639 ) Created NIoObject, 510970
Mon Apr 07 15:02:54 ( 4294822639 ) ClBind_ConnectToEndpoint at RDBVIA, DMQCLS_06000
Mon Apr 07 15:02:54 ( 4294822639 ) DECnet is not installed, or an unsupported DECnet operation was attempted.
Mon Apr 07 15:02:54 ( 4294822639 ) DECnet is not installed, or an unsupported DECnet operation was attempted.
Mon Apr 07 15:02:54 ( 4294822639 ) NIO_decnet_connect: getnodebyname error: RDBVIA not found
Mon Apr 07 15:02:54 ( 4294822639 ) NIO_decnet_connect: node RDBVIA not found
Mon Apr 07 15:02:54 ( 4294822639 ) Using config file: 
Mon Apr 07 15:02:54 ( 4294822639 ) ClBind_ConnectToEndpoint, server is not available on  at 0
Mon Apr 07 15:02:54 ( 4294822639 ) CLBindingDelete 5310112
Mon Apr 07 15:02:54 ( 4294822639 )   BindingObject hTask is 4294822639
Mon Apr 07 15:02:54 ( 4294822639 )   PUT_MSG: Total msgs sent 0, total bytes sent 0
Mon Apr 07 15:02:54 ( 4294822639 )   GET_MSG: Total msgs received 0, total bytes received 0
Mon Apr 07 15:02:54 ( 4294822639 ) CLBind_DisconnectServer on RDBVIA at endpoint 6000
Mon Apr 07 15:02:54 ( 4294822639 ) Disconnect link, 510970
Mon Apr 07 15:02:54 ( 4294822639 )   LINK: Total msgs sent 0, total bytes sent 0
Mon Apr 07 15:02:54 ( 4294822639 )   LINK: Total msgs received 0, total bytes received 0
Mon Apr 07 15:02:54 ( 4294822639 ) CLDelta_CancelTaskTimers
Mon Apr 07 15:02:54 ( 4294822639 ) call WSACleanup
Mon Apr 07 15:02:54 ( 4294822639 ) ClDelta_CancelAllTimers
Mon Apr 07 15:02:54 ( 4294822639 ) DmqAsyncTerminate
Mon Apr 07 15:02:54 ( 4294822639 ) Leaving CLBind_BindToServer, -278
Mon Apr 07 15:02:54 ( 4294822639 ) ClServerDelete
Mon Apr 07 15:02:54 ( 4294822639 ) << Exiting pams_attach_q, return status -278 >>
    

It looks like you are using the wrong winsock.dll. Your log file shows the
following WinSock info:

    WSA Socket info:
    Description:     Microsoft Windows Sockets Version 1.1.

I haven't used PATHWORKS V7, but I would expect the description to say
something like "DEC PATHWORKS WinSock DLL..."

Do you have the PW winsock.dll on your system?

    Pat

    I Got winsock.dll in WIN95 directory not in PW directory, should I copy
    it over ?
    
    Thanks for your reply.
    
    Jean-Paul.
    

Pat,

I'm curious as to the anticipated flow of control using the current 
products in a WINSOCK 2 environment.  I want to learn if DMQV3.2 can work 
in this space (a personal curiousity/learning module, not a customer 
requirement).

According to what I'm reading in the DIGITAL PATHWORKS 32 Application 
Programming Interfaces book (AA-R3S2A-TE), Microsoft's WinSock 1.1 API 
implementor (Either WINSOCK.DLL [16bit] or WSOCK32.DLL [32bit]) handles a 
call from any WinSock V1.1 application (such as DMQV3.2).

Again, only from what I see in this reference, it appears that the WinSock 
1.1 API DLL calls WS2-32.DLL as part of the Winsock 2 architecture.  The 
last sequence (from Microsoft DLL's) is when WS2-32.DLL calls the transport 
vendor's (in this case DECnet's) socket programming interface [SPI].

The message from .0:

Mon Apr 07 15:02:54 ( 4294822639 ) 32-bit DECnet support is not available!

says to me that something in this chain of events is not happening properly 
and/or is being misunderstood by some component.

The aforementioned DLL files exist on my NT 4.0 system where I'm writing 
this reply and they are all provided by Microsoft as part of the base O/S.  
I have pieces of PATHWORKS 32 installed but I do not run DECnet on this 
system (and won't over IP, this system's native protocol) so I can't 
recreate the base-noter's experience here.

David

    I include below an extract of Pathworks7.0 Release notes
    
    The PATHWORKS 32 V7.0 product release includes all the parts of DECnet
    Winsock 2. However, this functionnality is not supported on
    Windows 95 systems until Microsoft officially ships the Winsock 2 SDK 
    for Windows 95.
    
    
    Jean-Paul.

re: .3

At the time the V3.2 Windows Client kit was released, PW did not support
32-bit DECnet apps on Windows 95. The PW 1.0 kit for Windows 95 only supported
16-bit DECnet WinSock apps. That's why you get the message "32-bit DECnet
support is not available!". Support for 32-bit DECnet WinSock apps won't be
available on Windows 95 until WinSock2 is available (ws2_32.dll) As .4
mentioned, PW32 includes the underlying DECnet support, but Microsoft has not
released WinSock2 for Windows 95. It should be available "soon".

It was also unclear how PW was going to support WinSock2. The information I
saw indicated that they were not going to use the DNETW.DLL which is used by
PW 4.0B for 32-bit support on Windows NT. Apparently they have changed their
plans, and will provide a DNETW.DLL for compatability with existing NT apps. 

We are working on a V3.2 ECO kit (V3.2-2) which will remove this restriction.
So when Microsoft releases ws2_32.dll for Windows 95 we will be able to
support 32-bit DECnet. Until then, we only support 32-bit DECnet apps on
Windows NT.

    Pat