The "unable to locate/open NLS mesage repository" problem is
described in APAR IC23017. This has been fixed as of the latest
Win32 client fixtest, IC22732Q (available on index.storsys.ibm.com
in the /adsm/fixtest/v3r1/win32 directory). (Please note that the
README.FTP file does not mention this APAR, as I was unaware of
the APAR at the time I put the package together.)

The problem is that dsmcutil uses the API, and that the API is
looking in ..\ADSM\API for the message file (*.txt). dscameng.txt
is installed in ..\ADSM\API, but if you install additional languages,
those files are not copied to the ..\ADSM\API directory. You can work
around this problem by copying the file from the ..\ADSM\BACLIENT
directory. For example, if you installed French language support,
copy the dscfra.txt file from ..\ADSM\BACLIENT to ..\ADSM\API. Then
dsmcutil should work okay.

The fixtest fixes this problem by installing the message file(s)
into the API directory as well as the BACLIENT directory.

Regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

 hello,

 i'm currently working on automatic install for the win32 adsm
client. targets are several (around 50) windows nt server, from
v3.51 sp5 to 4.0 sp4. everything should be full automatic.

 i first tryed to use the install shield recording capabilities
(setup -r -> setup.iss -> setup -s ...) but it doesn't work on
all version. i'm having a custom installation (only backup
client, no help, no admin stuff...) so from what i've heard
here, it's almost normal as the win32 client seems to be
broken in this area.

 so i'm buidling a custom install from a .cmd file:

 - creating a C:\Adsm directory
 - copying the files i need here
                             (xcopy /e /s ...)
 - copying some fileq in WINDIR\system32
                             (adsmv3.dll, odbc...)
 - importing registry stuff via regini or regedit
                             (HKLM\software\IBM...)
 - installing the services with dsmcutil

 almost everything works except i get a

"Error: Unable to locate/open NLS message repository"

 when using dsmcutil to install the services.

 i found an old message in the ml archive (1/98) stating it could
be because the dscameng.txt file is not in same dir than the
utility (..\baclient) or because of some DSI_DIR variable
pointing to a wrong location.

 problem is the is no DSI_DIR set and dscameng.txt is in the
..\baclient dir with dsmcutil executable. i could use the
/validate:no switch to avoid this error message, as despite
this error message, everything *seems* to work (still need some
tests here) but i'm curious to know where it comes from (some
registry missing perhaps ?)

 any thoughts/explanations are welcome.

 amicalement,
              fx

---
fx AT axa-franceassurance DOT fr | First snow, then silence.
fx AT axa-franceassurance DOT fr | First snow, then silence.
Networking & system stuff | This thousand dollar screen
  Axa France Assurances   | Dies so beautifully.