Automatic digest processor <LISTSERV AT VM.MARIST DOT EDU>  writes:
>From:    Dominic Lancaster <landom AT DAS.GOV DOT AU>
>Subject: ADSM SERVER NAME
>
>I have a weird problem.
>When I installed my new production ADSM Server, I issued a 'SET SERV
ADSM_PROD'
>to keep it different from ADSM, my test system.
>However, when I change dsm.sys in /usr/lpp/adsm/bin to say
>SERVERNAME      ADSM_PROD
>
>I Get an error ANS5503E File '/usr/lpp/adsm/bin/dsm.sys', line 3,
>'SERVERNAME    ADSM_PROD' is not a valid option.
>
>Processing cannot continue
>When I change the servername to ADSM, it works, BUT, the servername
>in the Administration Panel says: Server: ADSM_PROD
>
>Has anyone got any clues on how this should work
>
>TIA
>
>Dominic
--
My under standing is that the SERVERNAME in the dsm.sys file has nothing to
My under standing is that the SERVERNAME in the dsm.sys file has nothing to
do with the actual server name on the ADSM server.  In the dsm.sys file you
can define multiple severs and the SERVERNAME is just a tag to be used on the
client.  Example.

ADSM SERVER 1's name is ADSM_PROD
ADSM SERVER 2's name is ADSM_TEST

on the Client in the dsm.sys file :

SERVERNAME=server1
   TCPServeraddress   adsm1.austin.ibm.com
   COMMmethod         TCPip
   ...[other flags left out]...

SErvername  ausadsm2
   TCPServeraddress   adsm2.dallas.ibm.com
   COMMmethod         TCPip
   ...[other flags left out]...

Now if I want to access server 1  I use the command
 dsmadmc -se=server1

and from here a 'q stat' shows I am on ADSM_PROD.  So as I said the SERVERNAME
option in the dsm.sys is strictly a local name on the client to be able to
group serve stanzas together.  Now why does the client think that ADSM_PROD
is invalid I don't know for sure.  I tested it on my system and when I took
out the '_' it worked just fine.  I guest the admin client does not like
underscores.

Chuck T.
(not ADSM support, just a user)