James, Gyula, et. al,

First of all, thanks for all the info on the various facets of DB2 and ADSM.
Unfortunately I seem to be on a bit of an island with my NT (actually Windows 2000
Server) installation.

Question. The standard Microsoft implementation uses the dsm.opt file in the baclient
directory. Does the API  implementation require a second dsm.opt file that the
dsmi_config variable points too? If, as intimated below, you want separate nodenames 
for
the API and non-API data then that would seem to follow. Can anyone relate James'
excellent 'Quick Guide' notes to the MS environment? It would be a great help. My
interpretation is that a second dsm.opt file would live in the api directory with a
nodename distinct from the machine name.

3.  create a plain text file dsm.opt in /usr/tivoli/tsm/client/api/bin
  It only needs one line, the value for SERVERNAME is arbitrary, but
  must match the dsm.sys file
      SERVERNAME DB2
4.  create a plain text file dsm.sys in /usr/tivoli/tsm/client/api/bin
  It must contain at least the following.
      SERVERNAME DB2
      COMMMETHOD TCPIP
      TCPSERVERADDRESS xxx.xxx.xxx.xxx
      NODENAME DB2TSM
      PASSWORDACCESS GENERATE

Of course the fact that there is no DB2 administrator around doesn't make matters any
easier :-(

James Thompson wrote:

> Per some of the other responses to your question, you have two main choices
> for keeping API (DB2) data separate from your backup/archive client data.
> Either way you should use separate nodenames for these two types of data.
> Once you have two nodenames, you can have them belong to the same domain,
> but use the INCLUDE/EXCLUDE list to send API data to a management class with
> the desired retention (VERDEL=0 RETONLY=0).
>
> Or you can create a new domain and update the node that will be doing the
> API backups to be a member of this domain.  Then you just need one
> management class as the default and you don't have to worry about
> incorrectly setting the include statement.  I recommend using a second
> domain.
>
> James Thompson
>
> >From: "MC Matt Cooper (2838)" <[EMAIL PROTECTED]>
> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: 1 server with two policys?
> >Date: Mon, 4 Dec 2000 15:11:09 -0500
> >
> >Hello all,
> >         I am trying to get some more interesting servers setup on our new
> >TSM 4.1 system.  (TSM is new to our site, we are getting rid of STKs CAM
> >system).  I am dealing with an RS6000 with DB2 on it.  Most of the data for
> >the server should have an entirely different backup schedule and data
> >retention schedule than the DB2 data bases.  Can I have this server defined
> >to two differenet POLICIES?  Do I have to give it two differenet names?  I
> >am kind of lost with it.  Any help would be appreciated.
> >Matt
>
> _____________________________________________________________________________________
> Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884

Reply via email to