[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:NAS Message Queuing Bus
Notice:KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:PAMSRC::MARCUSEN
Created:Wed Feb 27 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2898
Total number of notes:12363

2817.0. "net no link using Workgroups 3.11" by CARDHU::BOURAKOFF (MCS/STN-IM Switzerland 761-4820) Fri Mar 21 1997 05:48

    Using Windows 3.11
    Pathwork v6.0 on a PC (intel processor) 
    DMQ 3.0
    Decnet IV
    
    Under DOS the client can send messages to the server without problem.
    
    Same config but with WORKGROUPS 3.11
    
    No messages can be send the error is "net no link"
    
    Any idea ?
    Pierre
T.RTitleUserPersonal
Name		DateLines
2817.1DECWET::SIMONICHMake it look easyFri Mar 21 1997 11:195
I don't understand your problem description. Are you using the Windows Client
on WfW 3.11? Could you be more specific about which DmQ products (including
version numbers) are being used on the PC?

    Pat
2817.2dmq3.0 &PAthworksCARDHU::GUYTue Apr 01 1997 03:4620
    Found in a small textfile in PAMSRC kits directory
    
    "The SSB production candidate version of the DECmessageQ for Windows
    Client,
    Version 3.0 is available.
    
    
    The SSB candidate for August is Version 3.0.006
    
    
    
    To run this kit, you must have Pathworks V5.0A Client (TCP/IP or
    DECnet), or later.
    
    The DmQ Windows Client also runs on Windows for Workgroups using the
    Microsoft TCP/IP-32 stack."
    
    
    DOES THAT MEAN THAT DMQ3.0 WORKS ONLY WITH TCP/IP on WINDOWS for
    Workgroups.
2817.3DECWET::SIMONICHMake it look easyTue Apr 01 1997 11:563
It should also work with PW.

    Pat
2817.4Specific DLL for pathworksCARDHU::GUYWed Apr 02 1997 11:0111
    I found in PAMSRC::DMQ$KITS:[dmq030.windows] a zip file
    named DMQCL307.ZIP.
    
    This ZIP file contained a DLL DMQCLDN.DLL "used with PATHWORKS V5
    Decnet only"
    
    Do we need to  install this DLL to work with PATHWORKS 6.0 ?
    
    Thanks.
    
    Jean-Paul.
2817.5DECWET::SIMONICHMake it look easyWed Apr 02 1997 16:5626
The original Windows Client kit (3.0.006) supported both TCP/IP and DECnet.
The installation has a dialog that allows you to select the network protocol.
You can choose either "TCP/IP only" or "DECnet and TCP/IP". You must have
PATHWORKS installed to use the "DECnet and TCP/IP" option. It sounds like you
may have selected "TCP/IP only" when you wanted "DECnet and TCP/IP".

The DMQCL307.ZIP contains some updated DLL's to fix bugs in the 3.0.006 kit.
DMQCLDN.DLL provides support for apps using "DECnet and TCP/IP". See the
readme.txt file for installation instructions. Make sure you rename it to
dmqcl.dll before attempting to use it.

You can tell which transport is being used by looking at the DLL log file.
If you are using the 3.0.006 kit do the following:

1.  Exit Windows.
2.  Set the DMQCL_TRACE environment variable from DOS.
3.  Restart Windows and run your app or the dmqtestw program. This should
    create a file called dmqcldll.log.
4.  Look in dmqcldll.log for the WSA Socket info.

See the Troubleshooting section of the user guide for more details.

The 3.0.006 kit is pretty old. You might want to try the V3.2 kit. See note
4.79

    Pat
2817.6tracing dmqclCARDHU::GUYThu Apr 03 1997 05:106
    I had advised the customer to set DMQCL_TRACE and I am currently
    waiting for his logfile.
    
    Thanks so far for your help.
    
    Jean-Paul.