Archives of the TeradataForum

Message Posted: Wed, 06 Jun 2001 @ 13:26:03 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

At this site, three response time programs are run. They are called "Canary Programs" (after a canary in a mine used to see if the air is breathable, or if the Teradata Systems are still alive, and the Canary is still chirping).

(1) NT Canary is scheduled by Teradata Manager to run a canned query every six (6) minutes through the LAN, and store the result in a Teradata Performance Database Table. Teradata Manager also runs daily a Canary 24 hour summary to produce 24 hourly average response times, and stores this in a second Teradata Performance Database Table. Actually this daily Canary summary also summarizes the other two Canary response times below.

(2) MVS Canary is scheduled on an IBM MVS mainframe system channel connected to the Teradata every fifteen (15) minutes, and store the result in a Teradata Performance Database Table.

(3) MP-RAS Canary is scheduled on one of the Teradata nodes by MP RAS chron six minutes and the result in a Teradata Performance Database Table.

(4) Canary Web page update: The 24-hour (Daily) Canary summary scheduled by Teradata Manager in (1) above, is exported into an execution of DMTEQ in the same MS DOS BAT file script to an ASCII text file, which is read and processed by an Excel Visual Basic Auto_Open() script into an HTML file, and posted to the company's internal performance web site. (Along with other performance data.) So when we come into work, our performance data, Canary included, for the prior year from yesterday is charted, graphed, staffed, and web published.

Three Canary programs are useful for comparing client channel response, network response, and Teradata RDBMS response directly from the NCR SMP node. Canary programs positioned at strategic points in the large and ever growing company intranet may be implemented.

	<Prev	Next>		<<First	<Prev	Next>	Last>>