Teradata is pleased to announce the Teradata Multi-System Manager (TMSM) 14.00 release effective May 23rd, 2012 (sorry, a little tardy on the release article).  This release is focused on customer enhancement requests, many of which were tied to extending the TMSM infrastructure to better suit customer environments and volume usage. The release includes focused performance improvements, portlet updates, enhancements to the API, and expanded browser support.

See below for the various improvements and feature additions within the Teradata Multi-System Manager 14.0 release which includes support for Teradata Database 14.0 as well. 

Performance Enhancements:

Improved performance of event throughput to support at least 500 events per second (using a TMSM server Model 435 or newer).  The server and client code has been optimized to enable TMSM to support a sending speed of over 500 events per second when using recent releases of the TMSM managed server.  Improvements in parallel processing of events in the TMSM client has increased event sending speed significantly when increasing concurrency of sending processes.

Improved response time for bulk clearing of alerts. TMSM alert clearing logic is complex and can take significant time when clearing large volumes of alerts. This improvement moves the heavy processing needed in clearing the events into the background. Log View portlet responsiveness and usability is improved by removing cleared alerts from the display in just a few seconds, while doing the cleanup work in the background.

Improved repository response for Process Health. Process Health portlet performance has been improved by optimizing internal storage of process events and historic execution data.  

Portlet Improvements:

Report Viewer portlet: A key enhancement to this portlet is to provide export of grid based report results to a CSV file for reporting or processing needs outside of Teradata Viewpoint. This also conforms to similar functions provided by other Viewpoint data grid-based portlets. This new capability is shown below.

Log Viewer portlet: This portlet now supports up to 20,000 rows extending the previous limit of 1,000 rows. The default setting will remain at 1,000 rows as increasing this limit can adversely affect portlet performance as it requires a longer cache table build process. 

API Enhancements:

Expanded “Unit of Work ID” to support customers requiring descriptive ID’s (from 50 to 300 characters).  A Unit of Work (UOW) ID is how TMSM uniquely identifies “work” on one or more systems. Typically it represents a unique set of data that is applied to one or more systems.  Common UOW ID names include file names or process names (with a cycle identifier such as timestamp, cycle id, date), tables and/or database names, databases, and business functions. TMSM uses this UOW ID to track and compare work across one or more systems.  Some implementations required a fully qualified name for their UOW ID, possibly identifying the country-business-workactivity-filename-date information that resulted in the UOW ID expansion.

Expanded “Health Amount” values to support customers requiring values up to 36 digits. This field has gone from an INTEGER datatype to DECIMAL (38,2) to allow for much larger numbers. The "Health Amount" field is used to communicate a broad range of metrics to TMSM so having a larger maximum value supports more use cases, including items such as checksum and activity counts. 

Simplified Auto-Registration as a new field has been added to the sendevent API to categorize the hardware type / usage which makes auto-registration of hardware in the ecosystem easier.  This feature allows the implementer to identify the hardware category during the TMSM client install avoiding the need to change the classification of hardware through TMSM setup in the Teradata Viewpoint Admin menus. By using this feature in custom command line sendevent calls, users can also pre-classify processes within TMSM.

Lastly, the TMSM sendevent API will now accept single and double quotes with table and database names.

Expanded Browser Support:

With the TMSM 14.0 release, the TMSM portlets within Viewpoint have completed full certification with Internet Explorer, Firefox, Safari, and Chrome versions. 


That is the TMSM 14.0 release! A nice mix of performance improvements, volume management, and customer-requested features. Enjoy.

 

 

Discussion
anils345 4 comments Joined 09/12
21 Sep 2012

Hi,

can you plz explain TASM and TDViewpoint?How TASM and Viewpoint works?What are the benefits by using TASM and Viewpoint?

Thanks&Regards,
Anil Kumar

vikrantdixit 3 comments Joined 06/11
27 Sep 2012

Hi Anil,

If you have Teradata University Credentials, please go through webcast "Introduction to Teradata Active System Management (TASM) from Gary Ryback. Hope this helps.

VD

gryback 130 comments Joined 12/08
27 Sep 2012

The question on TASM and Viewpoint would be more appropriate posted to the forums than an unrelated DevX article. So I'd suggest doing that. In short, TASM is Teradata Active System Management, Teradata's advanced workload management strategy so completely different than TMSM discussed in this article. Viewpoint is Teradata's Operational View Portal (SOV). There are many portlets that are available for Viewpoint including ones for TMSM or TASM to just name a few. Hope this helps. I'll explain more if you post your question to the Viewpoint forum.

ratnamch 3 comments Joined 06/12
11 Oct 2012

hi gryback,

i have a small confusion please claify it

.set record vartext ",";
.logon 127.0.0.1/rat,rat;
beginloading emp
errorfiles er_emp,uv_emp
checkpoint 1000;
record 2;
define
i_eid(varchar(20)),
i_ename(varchar(20)),
i_sal(varchar(20)),
i_dept(varchar(30))
file=c:\m\j.txt;
insert into rat.emp
values(
:i_eid,
:i_ename,
:i_sal,
:i_dept);
endloading;
.logoff;

this above fastload query is same to write the procedure how could you please send me same to procedure / any procedure format...

thank you ..............I am Ratnam

gryback 130 comments Joined 12/08
11 Oct 2012

Ratnam,

I think you should be posting this to a discussion forum as it doesn't really apply to the TMSM product. Sorry.

Gary

ratnamch 3 comments Joined 06/12
12 Oct 2012

thnk's gray

ratnam

spakala 1 comment Joined 02/12
19 Dec 2012

Hi,

I am interested in configuring query director routing through TMSM for an application defined in TMSM as active. Anyone knows the steps or has done it and it is working?

Sharada

You must sign in to leave a comment.