Hi John,
according to the manual, tcpclientaddress specifies the TCP/IP address of your
client node and you have to use this option only with the schedule command when
 you specify prompted as the schedule mode.
But, this is not my problem ...

Thanks anyway for your help
Valeriano Bassi               valeriano.bassi AT ssb DOT it

---------------------- Forwarded by Valeriano Bassi/SSB on 05/01/2001 09.23 
---------------------------
"Price, John" <john.price AT weyerhaeuser DOT com> on 04/01/2001 17.45.04
"Price, John" <john.price AT weyerhaeuser DOT com> on 04/01/2001 17.45.04

To:   Valeriano Bassi/SSB@SSB
cc:

Subject:  RE: ADSM and multiple TCP/IP



Bassi,

I use the TCPCLIENTAddress 10.33.17.05 in the dsm.opt file on NT or dsm.sys
on the HP-UX.

Does this help?

     ----------
     From:  Valeriano Bassi [SMTP:Valeriano.Bassi AT SSB DOT IT]
     Sent:  Thursday, January 04, 2001 2:17 AM
     To:  ADSM-L AT VM.MARIST DOT EDU
     Subject:  ADSM and multiple TCP/IP

     Hi there,
     I would like to know how (and if) it is possible to force an ADSM
client to use
     a specific TCP/IP stack
     when a system does provide more than ones.

     We are using an USS ADSM client on a system where 3 different TCP/IP
stacks are
     available.
     As far as I know, the only ADSM parameters used to create a
client-server
     connection are
     COMMethod and TCPServeraddress.
     In our installation, three different TCP/IP names are defined in the
BPXPRMxx
     member; one is defined
     as the default one and so is used by the ADSM client. Since we are
going to
     modify this default, I need
     to force the ADSM client to use a specific stack.
     I think that other Unix systems should have the possibility to
configure more
     than one TCP/IP and so,
     how this problem get solved?

     ADSM server 3.1.2.50 on OS/390 2.6
     ADSM USS client  3.1.0.5

     Thanks in advance for your help.
     Best regards

     Valeriano Bassi          valeriano.bassi AT ssb DOT it