ADSM-L

Re: 3rd Try: DSMCUTIL Utility Question

1999-09-30 20:02:35
Subject: Re: 3rd Try: DSMCUTIL Utility Question
From: Pete Tanenhaus <tanenhau AT US.IBM DOT COM>
Date: Thu, 30 Sep 1999 20:02:35 -0400
I can definitively answer this (I have the dubious distinction of having written
the dsmcutil utility).

The /COMMSERVER and /COMMPORT options are used to override values in the client
options
file used by the service.

The correspond to different client options depending on the communications
method being used
(and yes, there is /CommMethod dsmcutil option).

For tcp/ip, they correspond to -tcpServer and -tcpPort, respectively.

Note that as with other DSMCUTIL options this has two implications.

One is that they cause registry settings to be created/updated which will be
used by the client service
and will override anything in the client options files the service uses.

The other is that they will override any settings in the client options file
when the utility establishes an api
session with the server for password validation and updating.

Note that these options only work for the scheduler service, they do work for
the distributed services
(cad or remote agent).

I hope this answers your questions and please post again if you need further
clarification.

Pete Tanenhaus, ADSM Client Development




Pete Tanenhaus
ADSM Client Development
email: tanenhau AT us.ibm DOT com



---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 09/30/99
07:51 PM ---------------------------
07:51 PM ---------------------------

Joel Fuhrman <joelf AT CAC.WASHINGTON DOT EDU>@VM.MARIST.EDU> on 09/30/99 
06:10:49 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: 3rd Try: DSMCUTIL Utility Question



If you want IBM to respond, you will have to open a ticket with them; this
list is not an indirect path to them. A couple of IBM professionals use to
voluntarily monitor this list. Unfortunately, I haven't seen any input
from them for a while.

Can you try it yourself by putting an invalid server name in dsm.opt?  If
you connect, you will know that the IP format works.

On Thu, 30 Sep 1999, Ryan, Damian [NCSUS] wrote:

> Hello,
>
> This is my third try at this.  I'm surprised that no one has responded to
> this question.  IBM can you please respond?
>
> This is a very basic question.  However, I have not found any documentation
> so far that answers this question.
>
> In using the DSMCUTIL utility, there is an option called
> /COMMSERVER:SERVERNAME.  In the help file for the newest client software, it
> mentions that you can use the server name for this option.
>
> My question is this, can you use the TCP/IP address instead of the server
> name for this option?
>
> I would assume the answer is yes, because if this option is not used, the
> value specified in the dsm.opt file would be used.  Since there is no
> /COMMSERVER:SERVERNAME option in the dsm.opt client options file, I would
> assume IBM means the TCPServeraddress option.  Since TCP/IP address number
> can be used for this option it would logically follow that the DSMCUTIL
> /COMMSERVER:SERVERNAME option would be able to use the TCP/IP address number
> of the ADSM server.
>
> Can anyone help on this?
>
> Thank you,
>
> Damian Ryan
>
>
>
>
>
>
> Damian Ryan
>
<Prev in Thread] Current Thread [Next in Thread>