ADSM-L

Re: TSM version 5.1.x and uniquetecevents not working

2003-06-04 12:47:26
Subject: Re: TSM version 5.1.x and uniquetecevents not working
From: Glen Hattrup <ghattrup AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 4 Jun 2003 09:31:47 -0700
--- Background & Current Availability... ---
"Unique TEC event" functionality was introduced / enabled with the 
following ADSM / TSM versions:
3.7.3
4.1.0
4.1.1

Due to performance problems on the TEC server, the unique TEC event per 
TSM message model was removed.  These problems were related to the size of 
the TSM baroc file and the processing time of incoming events.

To my knowledge, the TEC development team has since resolved the 
performance related problems.  TSM development accepted a change request 
to re-enable the unique TEC event functionality.  This function has been 
re-introduced at the following levels:
4.2.4
5.1.7
5.2.0

The "uniquetecevents" option was introduced to allow administrators to 
choose between the tsm_yyy_event model or the unique event model.  Default 
behavior is the tsm_yyy_event, which is the same as what 4.2 & 5.1 servers 
have already been doing.  In other words, there will be no change in event 
class format unless you specifically enable it.

Please note, there is an associated baroc file refresh with this change.

The server README's for  4.2.4, 5.1.7, and 5.2.0 have more information on 
implementing the unique TEC event model.

Also note, older versions of the TEC server will likely have the 
performance related issues.  If you notice that event processing time 
degrades significantly after activating the unique event baroc file, you 
should either upgrade your TEC server or revert to the standard 
tsm_yyy_event model.

--- Your specific question ---
As you're running TSM 5.1.6.5, the unique TEC event function is not 
available.  Please apply PTF 5.1.7 when it becomes available.  Your 
service representative (support) can give you a better approximation of 
when 5.1.7 will be availble.

As a side note - if you check the console or the activity log during 
server startup, you'll likely see a message stating that "uniquetecevents" 
is an unrecognized option.  Once you apply 5.1.7, it will be recognized as 
a valid option.

Glen Hattrup
IBM - Tivoli Systems
Tivoli Storage Manager




Przemysław Maciuszko <sal AT AGORA DOT PL> 
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/04/2003 12:37 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
TSM version 5.1.x and uniquetecevents not working






Some time ago we made an upgrade to version 5.1 because of 
'uniquetecevents'
functionality.
Everything worked fine for few weeks, but suddenly something happened and
TSM started to mark all TEC events as standard 'TSM_SERVER_EVENT' and
'TSM_CLIENT_EVENT'

I've doubled checked - required option (uniquetecevents yes) is in
dsmserv.opt

I've been using 5.1.6.4 - with no effect. Yesterday I did upgrade to 
5.1.6.5
- still no effect.
TSM server is running on AIX 4.3.3


-- 
Przemysław Maciuszko
Agora SA

<Prev in Thread] Current Thread [Next in Thread>