Yes. I've seen this problem occur. I believe there is an Open APAR for this
problem.
In every situation I have encountered the dr watson has occurred because
either...

the node has not yet been registered on the adsm server

or

the dsm.opt file has not been setup correctly to point at the adsm server
where the node is registered.

Thanks,

Nathan

        -----Original Message-----
        From:   Moreels Johan [SMTP:Moreels_Johan AT DELAWARE-COMPUTING DOT COM]
        Sent:   Thursday, April 01, 1999 7:48 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        SP 4 and adsm client version 3 release 1 level 06

        Hi ADSM users,

        Currently I'm investigating the ADSM client 3.1.06. with V3 server
on the
        mainframe

        I have it installed on a NT 4 Server with Service pack 4, and on a
NT4
        server with SP3.

        On the SP 3 version I don't have any problem.

        On the SP4 version I have encoutered problems with the scheduler
service.
        It, the DSMSVC.EXE,  causes a DR WATSON error.


        Does anyone had the same problem yet?

        If so, are there any solutions, patches, for it?

        Thanks for your quick response.

        Johan Moreels

                Delaware Computing Group
                Delaware Infrastructure Management
                Blokkestraat 29A
                B-8550 Zwevegem
                Phone   +32-56-76.76.00
                Direct     +32-56-76.75.69
                Fax     +32-56-76.77.93
                E-mail  Moreels_Johan AT delaware-computing DOT com
                URL     http://www.delaware-computing.com