Vikas,
 The ADSMPIPE uses the API. In the README.API it explains that the
API uses unique environment variables to locate the option files.
 Please check those.

 Betsy Colby



ADSM-L AT VM.MARIST DOT EDU on 05-18-98 02:21:26 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: ADSMPIPE


If I backup by dsmc, the backup goes through fine indicating that there is
no problem with dsm.sys or dsm.opt files

Please suggest if I can do something else.

Thanxs


Vikas





Betsy Colby
05-18-98 01:22 PM
To: adsm-l AT vm.marist DOT edu
cc:
Subject: ADSMPIPE


 There are some new option names in Ver 3. They are documented in the
Installing the Clients book, in the section Migrating from Earlier Versions of
ADSM.
 The option you may be having trouble with is NODENAME. In Ver 3,
when this is used in the dsm.opt file, it must now be VIRTUALNODENAME.

 Betsy Colby
 ADSM client development



ADSM-L AT VM.MARIST DOT EDU on 05-18-98 12:55:03 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: ADSMPIPE


Hi ,

We were using adsmpipe to backup some our database exports.  Once we
upgraded to Version 3 of the ADSM client adsmpipe stopped working and gives
a message

"error in dsmInit. rcMsg=ANS0220E (RC2013) An invalid option was found
during option parsing."

The same syntax works on a version 2 clients

Pleae let me know if anyone else has run into the same issues with
adsmpipe.

Thanxs

Vikas