I forwarded your note to the administrator who is having this problem, and
this was her response.


I receive this message.   "Message repository 'x:\baclient\dscameng.txt' has
an invalid control record".  Before I reboot the PC I change the set
dsm_config statement to point to a new folder (I'm consolidating the location
of opts - I used to have sub-folders for departments but this was unnecessary
and hard to maintain).  Set statement was:  set
dsm_config=x:\baclient\deptname\nodeid.opt.  Now it's: set
dsm_config=x:\opt\nodeid.opt.  I also create a new opt from the template
Betsy and I tweaked.   Then I reboot.  My PC then has a new drive letter
mapped.  (for example a new L:\...\adsmv2)  The mapping I change is still
connected x:\...\adsmv3.  The icons change properties to point to L:\ while
my autoexec.bat set statements still point to x:\.  I then change the icons
back to x: and everything runs great.  FYI, there is no L:\ drive mapping
before I reboot.  This drive letter is random.

Does that help?




ADSM-L AT VM.MARIST DOT EDU on 10/25/99 12:44:08 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: Ver3/Ver2 & NT Shares

Hi Betsy -

Can you tell me what the error is?

Thanks -
C

__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / TSM (ADSM)
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

        -----Original Message-----
        From:   Moir,Betsy [SMTP:betsy.moir AT ABBOTT DOT COM]
        Sent:   Monday, October 25, 1999 1:22 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Ver3/Ver2 & NT Shares

        I need some help from one of you ADSM/NT double gurus out there.

        One of my clients has ADSMV2 on an NT server and all the workstation
clients
        run ADSM from the server.  She has the subdirectory ADSMV2 defined
as a share
        (forgive me if my terminology is wrong) so that the path in the
properties
        portion of the desktop shortcut pointing to the ADSM executable
reads:

        X:\baclient\dsm.exe -optfile=myoptfile.opt

        She is in the processing now of upgrading to the version 3
workstation
        client.  She created a new subdirectory called ADSMV3 and created a
share for
        that subdirectory.  She also moved all the options files into
another folder.

        She disconnects the old mapped X: drive (and the ADSMV2 share) and
remaps to
        the X: drive and the ADSMV3 share.

        She Reboots the workstation.

        She updates the properties path to point to the new location for the
options
        files.  Executes the shortcut and gets an error.   When she checks
the
        properties for the shortcut they have "reverted" to the old path.
She
        changes them again and then everything works just fine.

        Mind you I haven't seen this happen and she may be leaving something
out in
        her explanation to me (or in my NT ignorance I may be
misrepresenting
        something here), but she's a pretty thorough, conscientious
administrator.
        Anybody have any ideas what might be going on here?