As a former customer and MVS storage administrator myself, I certainly
wouldn't want my users modifying SMS policies, either directly or
indirectly. In the same fashion, I wouldn't want them modifying my TSM
policies. Allowing users to specify -mode=absolute from the client is
effectively doing just that. Also, if we were to allow users to modify the
MODE setting, then the precedent would be set: next, users will want to be
able to modify VEREXISTS, VERDELETED, RETEXTRA, FREQUENCY, etc. Then the
whole concept of policy-based storage management goes out the window.

Even if you don't want to modify your TSM policy settings, I still don't
see what functionality a "-mode=absolute" option would give you that you
don't already have today via the SELECTIVE command. But yes, if this is
still something you require, then the requirements route is the best way
to go.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/18/2001 22:51
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Future Share Requirement: W2K 4.2.1 Desktop Archive 
Client backs    up
files that are unmodified



Thanks for the response.

I plan to submit a requirement Share to make this work.  I will explain
why.
Coming from a mainframe background, we do not change configuration
parameters on the fly to direct software.  We typically use command
overrides.  So the requirement would be for the client node definition to
have a mode override authority (no or client) added to it and the
incremental command to allow a "-mode absolute" or "-mode modified" so
that
the customer can allow the client to override this parameter rather than
giving them authority to mess around with the entire management class or
more.  The other option is to have a new mode setup in the management
class
"client" which requires the client to specify or defaults to modified.

Even if the documentation is correct and development decides to fix the
code, I now recommend they rethink and some kind of variation of the
above.
Otherwise, they could break something.

I will talk to the Product Manager about this one.