Hello,

The correct "workaround" for this problem is to
copy the old ADSMV3.DLL (3.1 version) into the baclient
directory (or wherever DSMCUTIL.EXE is).
That way, DSMCUTIL.EXE will load that version.

The "small" ADSMV3.DLL in the system32 directory is
supposed to be small because the API is now
contained within the TSMAPI.DLL file (and no longer
in ADSMV3.DLL.)

The "stub" version of the ADSMV3.DLL file is still installed
with the new level of the API for applications that loaded
ADSMV3.DLL (like DSMCUTIL.EXE) and have not yet changed to
the new TSMAPI.DLL.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


Nathan King <nathan.king AT USAA DOT COM>@VM.MARIST.EDU> on 12/08/99 03:10:11 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: ADSMConnect Agent for Microsoft SQL Server v1.1.2



Neil see a previous post about this one.
The workaround is to copy across the old ADSMV3.DLL (installed with ADSM
3.1.0.7)

Nathan



        -----Original Message-----
        From:   Neil Schofield [SMTP:Neil.Schofield AT YORKSHIREWATER.CO DOT UK]
        Sent:   Wednesday, December 08, 1999 2:00 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        ADSMConnect Agent for Microsoft SQL Server v1.1.2

        Is the ADSMConnect Agent for Microsoft SQL Server v1.1.2 client
software
        compatible with the ADSM Windows NT client software v3.1.0.7?

        The Tivoli web-site

(http://www.tivoli.com/products/index/storage_mgt/adsm/adagent.htm#SQL)
        suggests that to use ADSM scheduling with the ADSMConnect Agent, I
can use
        any v2 or v3 NT client. However, I am having problems.

        I have installed the ADSM Windows NT client software v3.1.0.7f
(from
        IP21618) and then tried installing the SQL Connect Agent v1.1.2
(from
        IP21873). When I come to install the ADSM scheduler for the SQL
agent using
        the DSMCUTIL command, I get an error.

        Whenever I run DSMCUTIL (with or without options) I get the
following:
        "The ordinal 28 could not be located in the dynamic link library
        ADSMV3.DLL"
        This DLL exists in the C:\WINNT\SYSTEM32 directory and is dated
30th
August
        1999. It seems to have been installed by the latest SQL Agent
software and
        is more recent than the one which was installed by the ADSM Windows
NT
        client.

        I didn't want to upgarde to the TSM 3.7 client for Windows NT until
we've
        done some more testing of it in our environment. However the 1.1.2
SQL
        Agent gives us some features we need now. Does anybody know how I
can get
        it to work alongside the ADSM 3.1.0.7 client or do I need to go
back
to the
        1.1.1a SQL Agent?

        Neil Schofield


        The information in this e-mail is confidential and may also be
legally
        privileged. The contents are intended for recipient only and are
subject
        to the legal notice available at
http://www.keldagroup.com/email.htm
        Kelda Group plc and its subsidiaries, UK
        Registered in England and Wales No 2366627