hi,

I think the agent level you are using is 2.1.0.6 which is ADSM V2 based
application.

Basically rc=2221 is issued when you have an invalid option in your dsm.sys or
dsm.opt file.   Check to see whether you have any invalid options in those
files or not.
Another possibiblity is that if you are sharing the dsm.opt or dsm.sys file
with ADSM V3 b/a client and using V3 specific options in those files.

For 2.1.0.6 agent, make sure to define env vars DSMI_DIR, DSMI_CONFIG, and
DSMO_PSWDPATH.

ptf 2.1.0.7 is availble right now which is ADSM V3 code based.  If you are
using the agent with O8, you should use the new ptf.

regards,
Thiha



>Hi,
>we have installed a oracle connect agent for sun the first time (on aix
>over 30x)
>The agent starts and produced following messages:

>(17140) OBK-sbt: odsmkey: ReadLicense() rc=0
>(17140) OBK-sbt: odsminit: sbtinit call successful.
>(17140) OBK-sbt: sbtremove(): entry
>(17140) OBK-sbt: ADSM session init: Error in dsmInit. rc=2221
>>>>OBK-7085: Sbtremove: System error
>etc...

>What Problem we have ? In the profile all variables are set and the
>options parameter looks ok.


>I have a look in the api-book and find the rc number with

>DSM_RC_INVALID_KEYWORD (2221) A keyword specified in an options string
>is invalid.

>Can anybody help us ??

>regards
>michael garnebode