Howdy,

      Please look at the new TSM Wiki.  The TSM development team recognizes
that there are capabilities available with the V6.1 database that may be
beneficial to the TSM server that are just not yet documented or tested.

     The following is a link to the specific section of the wiki that is
intended to address or consider these types of issues:

http://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/TSM
+V6.1+Database+Capabilities+and+Considerations

( V6.1 FAQs->TSM V6.1 Database Capabilities and Considerations->...)

This is a work in progress at this point (as you would expect of a wiki)
but should help to get the discussions started or put forth a framework
from which the development team would like to approach this.  The main
point is we'd like to approach this as a collaborative community effort.
To the degree that new features or capabilities can be reviewed and
"approved" for use in production environments, we'd like to use the wiki as
the main clearinghouse for this.

        To comment on the cease and desist questions, the goal from the
development team is to take a conservative and measured approach to
functional enhancements or tuning/configuration changes to the database
with the focus being on data integrity and server availability.  If changes
are being considered or made to the server database that changes the schema
(DDL) or other operational characteristics then we're going to try to steer
folks away from these.  The main thing to consider about DDL changes or
otherwise is that the TSM server application is built on that DDL and those
database behaviors and the algorithms and such make specific assumptions or
decisions based on these.  Changes to the schema or database configuration
parameters can have unforeseen consequences ranging from performance to
more serious implications such as server down or data loss.

     Thanks in advance for the participation and discussion and for what
will hopefully be a lot of good information and consideration in the wiki
for this topic...

Thanks,
Colin
-----------------------------------------------------
Colin Dawson
colind AT us.ibm DOT com



  From:       "Allen S. Rout" <asr AT UFL DOT EDU>

  To:         ADSM-L AT VM.MARIST DOT EDU

  Date:       04/03/2009 10:02 AM

  Subject:    Re: [ADSM-L] TSM 6.1 : Database replication Feature






>> On Thu, 2 Apr 2009 13:24:31 -0700, "Clark, Robert A"
<Robert.Clark AT PROVIDENCE DOT ORG> said:

> If we put together a wiki or forum, and pull enough info together to
> make something like this work, would we get a cease-n-desist letter
> from IBM?

> Does anyone on the list have a feel for how tolerant IBM is with
> "Open Source" style projects when they interact this closely with
> TSM?


I'd say, edit articles on the official TSM wiki that IBM maintains
(and which was recently announced).  This should be the most intense
test of that tolerance, and will establish wether the wiki is ours,
even partially, or not.

If you know you're going off the reservation, then you have the
responsibility to let IBM know about that in whatever support
interactions you develop.  And you need to be prepared to accept "Go
away, you're in an unsupported config" with a cheerful smile.

It would be fun to see IBM legal send a C&D to IBM communications and
IBM customer care.  Like those coke commercials?  "I want to sue us,
for excessively good customer communcations.  It's making the other
divisions feel inadequate."


- Allen S. Rout