I'm in the process of looking into making ADSM available to more of our
network users.  Right now, we are mainly using it for LAN servers and
a few PC's.  Instead of installing a copy of ADSM on each PC on the
network, I would like to try the following scenario:

ADSM code resides on a LAN server, in a r/o directory accessible by everyone
  on the server.
Individual options files are located in each user's LAN directory, but
  protected so they can't be altered by the user.
Log files such as DSMERROR.LOG would be placed in the user's LAN directory.

This scenario would give us control over the way the machines are being
backed up, and cut down on the amount of upgrades that will have to be done.
I, especially, like the last one because I'm the one doing the upgrades. %-)

Using an OS/2 workstation and an OS/2 LAN server, I have managed
to get ADSM to run with the code in one directory and the
options file in a different one without too much trouble.  Changing the
SET commands in the CONFIG.SYS did the trick.  However, I'm having problems
when I make the ADSM directory R/O.  DMSC (the linemode client) initiates
alright, then gives an error when you try to do the backup.  The error
is "ANS0110E LogMsg: Unable to open error log file 'dsmerror.log' for output."
This makes sense since DSMERROR.LOG is in the R/O directory.  Is there anyway
to redirect this file to a R/W directory in the user's path, or is it
required to be in the DSM_DIR directory?

The GUI gives the message: "Message Repository Error, Unable to open
message repository".  I suspect that this really is the same problem as the
DSMC, as the DSCAMENG.TXT file is fine.

Has anyone tried something similar to this or have suggestions?  Is it not
possible to do?

Martha