Hi,
My workaround for that is having an administrative dir (local or nfs shared if
you prefer) with the following contents:
* 1 dsm.sys file containing the minimum necessary dsmadmc configuration of all
the servers to be managed, like this:
[tico01]/tsms/zero/etc # cat dsm.sys
SErvername zero_server1
passwordaccess generate
passworddir /tsms/zero/etc
commmethod tcpip
tcpserveraddr aaa.bbb.ccc.ddd or fqdn
tcpport xxxx
errorlogretention 7 D
errorlogname /tsms/zero/log/server1_dsmerror.log
SErvername zero_server2
...
... and so on and so forth
...
SErvername zero_serverN
passwordaccess generate
passworddir /tsms/zero/etc
commmethod tcpip
tcpserveraddr aaa.bbb.ccc.ddd or fqdn
tcpport xxxx
errorlogretention 7 D
errorlogname /tsms/zero/log/serverN_dsmerror.log
* 1 link to the language files (you can place then there if you prefer)
[tico01]/tsms/zero/etc # ls -al en_US
lrwxrwxrwx 1 root root 36 Nov 14 2008 en_US ->
/opt/tivoli/tsm/client/ba/bin/en_US/
* Optionally, if you want to use different admin id's and passwords per server,
you can have a configuration file to feed a script that will launch dsmadmc
whith those id's.
* Launch dsmadmc manually on the sell or shell script, this way:
DSM_DIR=/tsms/zero/etc/ /usr/bin/dsmadmc -SErvername=zero_$TSM_SERVER
-dateformat=3 -numberformat=5 -id=$user -pass=$pass -outfile TSM_COMMAND
Just use or export "DSM_DIR=dir_with_the_admin_dsm_sys_file" so that dsmadmc
reads it, instead of reading the default client dsm.sys file.
Hope this helps.
Regards,
Justino Miguel Costa
Solution Specialist
_________________________________________________
Logica - Releasing your potential
Rua Particular EDP (à Rua Cidade de Goa), 11
2686-964 Sacavém - Portugal
M: +351 936 830 259
E: justino.co...@logica.com
E: datacenter.storage...@logica.com
W: http://www.logica.com/pt
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick
Laflamme
Sent: terça-feira, 5 de Janeiro de 2010 15:54
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Disparate Client Options
Does it annoy or hinder anyone else that the "tcpserver" and "tcpport" options
supported by the Windows version of dsmadmc aren't supported by the Unix
clients?
This seems to be a deliberate choice by IBM; the 5.5.2 levels of the client
make a point to quit with an error message if I try to use them; in the 5.5.1
level, my attempts to use them are merely ignored.
I want them so I can have scripts issue QUERY SERVER commands against a central
server and use that output to connect to new (or existing) TSM servers I
maintain. Apparently, in the Unix world, I'm supposed to keep dsm.sys up to
date on every Unix server on which I might run my scripts instead of
dynamically specifying these parameters. Part of it is because of the number of
servers on which I might access these scripts; part of is because we anticipate
rolling out waves of new servers in the future as we retire older servers.
Either way, the thought of keeping dsm.sys up to date just so I can run
administrative scripts is annoying, to put it mildly.
Anyone else with me on this?
Thanks,
Nick
Please help Logica to respect the environment by not printing this email /
Pour contribuer comme Logica au respect de l'environnement, merci de ne pas
imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie
so Logica dabei, die Umwelt zu schützen. / Por favor ajude a Logica a
respeitar o ambiente nao imprimindo este correio electronico.
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
