Thanks. Really, I wish there was one code base for the dsmc client. As it is now, Windows-dsmc and unix-dsmc have different command-line options and other differences too.
And the cross-platform problem with dsmc makes it hard for us to do what we do (ie, restore testing across all platforms). (Cross-platform problem means: from a WINDOWS dsmc client, you can successfully connect to a TSM server, and use "-asnode=some-UNIX-node" to masquerade as another node; but then "query filespaces" comes back empty. And vice versa. ) Just grumbling. We dealt with it. Lindsay Morris Principal TSMworks Tel. 1-859-539-9900 lind...@tsmworks.com On Tue, Jan 5, 2010 at 11:42 AM, Nick Laflamme <dplafla...@gmail.com> wrote: > Got it in one, LIndsay, got it in one. > > Nick > > On Jan 5, 2010, at 10:37 AM, Lindsay Morris wrote: > > > Right, but then Nick has to keep dsm.sys files up to date on all his > > clients. > > Ick. > > > > What he wants is a central way to issue dsmc commands and point them to a > > different TSM server, with no client-side setup required. > > Right, Nick? > > > > We don't have a good answer for this either. > > > > Lindsay Morris > > Principal > > TSMworks > > Tel. 1-859-539-9900 > > lind...@tsmworks.com > > > > > > On Tue, Jan 5, 2010 at 11:34 AM, Howard Coles < > howard.co...@ardenthealth.com > >> wrote: > > > >> In UNIX use the -optfile= option and specify an opt file that points to > >> a separate Stanza in the dsm.sys file. Another way of doing the same > >> thing essentially. > >> > >> See Ya' > >> Howard Coles Jr. >
