T24 Enterprise Console

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.

Copyright 2002-2003 TEMENOS Holdings NV. All rights reserved.

T24 Enterprise Console

Table of Content
Table of Content ...................................................................................................................................... 1
Table of Content ...................................................................................................................................... 2
T24 Enterprise Console........................................................................................................................... 3
Application Overview ........................................................................................................................... 3
What does the tEC show me?.......................................................................................................... 3
Application Design ............................................................................................................................... 5
TEC.ITEMS ...................................................................................................................................... 5
TEC.PROFILE.................................................................................................................................. 7
TEC.ACTIVE.ITEMS ........................................................................................................................ 8
TEC.OUTPUT .................................................................................................................................. 9
Overview of Input and Processing ..................................................................................................... 11
Worked Example ............................................................................................................................ 11
Dynamic modification of active profile............................................................................................ 13
Monitoring custom items using tEC................................................................................................ 13
Monitoring GLOBUS using tEC...................................................................................................... 18
Sample TEC.ITEMS record............................................................................................................ 19
Enquiry TEC.DETAIL ..................................................................................................................... 20
Enquiry TEC.SUMMARY................................................................................................................ 21
Enquiry TEC.OVERVIEW............................................................................................................... 22
Enquiry TEC.PANEL ...................................................................................................................... 23

TEMENOS Confidential Page 2 of 23 Oct 2004

T24 Enterprise Console

T24 Enterprise Console

Application Overview
The T24 Enterprise Console (tEC) is a comprehensive system management framework, built to internet
standards, that provides a robust console, a rich set of tools, and the ability to detect, solve, and
simplify the full range of problems that can arise in any managed environment.

tEC is based upon a lightweight architecture with minimal impact to your T24 installation.
This allows T24 users to monitor every aspect of performance and behaviour of their T24 environments
by defining a monitoring profile that reports on the use and activity of the system, as well as the tools
to solve any exceptional behaviour.

Menus and graphical displays with full drilldown and investigative facilities ensure that the information
is easily accessible, and includes the ability to store this information historically for reporting purposes,
as well as the full help and documentation you would expect from T24.

What does the tEC show me?

The tEC allows us to monitor a number of items . Find below a sample of the kind of items that can be
monitored using the tEC.

Menu Item Description

Overview of T24 Health Overview T24 Health Overview
Performance Current Mode (active vs close of business)
Fiscal date, last working day, next working day
T24 system details (ip, T24 release, db, os version,
etc.)
COB progress indicator
Connected users
Response Time Execution response times and breakdowns
Overview
Wait Analysis Wait event information
Overview
I/O at a glance Top I/O statistics
Operating System Disk usage for j4
Overview CPU usage
Database overview Vital Oracle stats
Vital j4 stats
Response Times Avg Transaction The average response times for transactions (drill
Length down to Txn lengths by txn type)
Throughput rates Transaction throughput per time slice per txn type
Avg trans length per The average response times for transactions by user
user

TEMENOS Confidential Page 3 of 23 Oct 2004

T24 Enterprise Console

Wait events Top waits by time

waited
Wait event counts
I/O File write operations Write operations on a per file basis
File read operations Read operations on a per file basis
IO Rates IO per second
IO time Average time spent per IO operation
Locks Lock manager Overview of lock management
User locks Stats for user locks
Blocking locks Stats for blocking locks (collisions)
Queues Delivery queues Status, depth and progress of delivery queues
T24 connector Status, depth and progress of connector
Agents TSM Overview Status of all tSAs
TSA throughput Throughput per tSA
TSA Monitor Details of tSA progress
TSA Management control (start / stop / start-up type)
Interface management
Users User Population Current user population
Active users Current active users
Top active users Most active users
Sign on failures
User management Sign on reset, password reset, expiration dates, etc.
Close of Business Initiate COB
COB progress
COB timings
Database
Tec tEC Profile Modify the active monitoring profile
Configuration
Historic graphs Txn throughput by hour
Txn throughput by day
Db size increase

TEMENOS Confidential Page 4 of 23 Oct 2004

T24 Enterprise Console

Application Design
TEC.ITEMS
This is the main table where all the items that can be monitored are defined.

File Type : H File Classification : INT

Field Name Data Type Description

TEC.ITEM.ID Key, 35 Id of the TEC.ITEMS file. Can contain any
Alphanumeric alphanumeric data
LL.DESCRIPTION Alphanumeric Description of the item
TYPE Alphanumeric The type of metric that needs to be recorded
Valid Values : TIME, SIZE, COUNT
XX<THRESHOLD.TYPE ID of Valid ID in the TEC.THRESHOLD file.
TEC.THRESHOLD
Predefined values : INFO, WARNING,
CRITICAL
XX>THRESHOLD Numeric For those types of SIZE, the value the item must
reach before it will fall into the associated
THRESHOLD.TYPE.

Sample Data
Field Name Value
TEC.ITEM.ID DELIVERY.CALL
LL.DESCRIPTION Count of call to Delivery
TYPE COUNT
XX<THRESHOLD.TYPE
XX>THRESHOLD

Field Name Value

TEC.ITEM.ID READ.RESPONSE
LL.DESCRIPTION Response times for record read
TYPE TIME
XX<THRESHOLD.TYPE
XX>THRESHOLD

Field Name Value

TEC.ITEM.ID READ.SIZE

TEMENOS Confidential Page 5 of 23 Oct 2004

T24 Enterprise Console

LL.DESCRIPTION Size of read records

TYPE SIZE
XX<THRESHOLD.TYPE
XX>THRESHOLD

TEMENOS Confidential Page 6 of 23 Oct 2004

T24 Enterprise Console

TEC.PROFILE
This is the table where we can specify the specific items that we wish to monitor and the list of users
for which they need to be monitored.

Once a record with the necessary items to be monitored are specified in the TEC.PROFILE, the
record needs to be verified in order for the record to be made as an active profile. Verifying a record in
the TEC.PROFILE will write the verified record into the TEC.ACTIVE.ITEMS file. It is this file that the
tEC will refer to in order to obtain the items to be monitored (active items).

File Type : W File Classification : INT

Field Name Type Details

TEC.PROFILE.ID Key, 35 A Any alphanumeric
LL.DESCRIPTION 35 A A description of the profile.
LOG.SETS Numeric The number of log sets to maintain
FLUSH.TIME Numeric The number of seconds after which the data will
be flushed from the memory to the disk
XX.ITEMS CHECKFILE TEC.ITEMS A valid item defined in the TEC.ITEMS file that
needs to be monitored.
XX.USERS CHECKFILE USER A valid user defined in the USER file for whom
the activities need to be monitored.
REFRESH.TIME Numeric The time after which the data for tEC enquiries
need to be rebuilt.
SESSION.MAX Numeric The maximum number of sessions.

Sample TEC.PROFILE record

Field Name Value
TEC.PROFILE.ID TEC.TRG.PROFILE
LL.DESCRIPTION TEC TRAINING PROFILE
LOG.SETS 5
FLUSH.TIME 60
XX.ITEMS READ.RESPONSE
XX.USER INPUTTER
REFRESH.TIME
SESSION.MAX 50

TEMENOS Confidential Page 7 of 23 Oct 2004

T24 Enterprise Console

TEC.ACTIVE.ITEMS
File Type : L File Classification : INT

This is the file that hols the currently active profile. This file is automatically updated when the
TEC.PROFILE is verified.

This file will have the following types of records

ACTIVE.PROFILE*TEC.PROFILE ID
SequenceNumber_TEC.ITEM ID_ _Thresholds( if any delimited by , )

Sequence Number : Multi value number of the item in the TEC.PROFILE table
Thresholds : The values specified in the TEC.ITEMS in the field THRESHOLD

Sample Data
ACTIVE.PROFILE*TEC.TRG.PROFILE
1_READ.RESPONSE_ _
2_WRITE.SIZE_ _1000,3000,
3_SELECT_ _1000,3000,
4_READ.SIZE_ _100000

TEMENOS Confidential Page 8 of 23 Oct 2004

T24 Enterprise Console

TEC.OUTPUT
File Type : L File Classification : INT

Field Name Description

ID ID
ITEM.TYPE The active item name
ITEM.DETAIL The names of the files that were read/written/selected by the activity
THRESHOLD
THRES.COUNT The number of times the activity has been invoked
THRESHOLD.TOTAL ID of the record read/written/executed
METRIC.COUNT
METRIC.TOTAL The total time taken in milliseconds to execute the activity
METRIC.AVG
METRIC.HIGH The highest time taken in milliseconds to execute the activity
TOP.KEY The ID of the record that took the highest time to be read/written/executed
TXN.REF ID of the record read/written
APPLICATION Application that triggered the activity
START.TIME Start time
END.TIME End time

The ID of the TEC.OUTPUT table consists of the following:

SessionNumber.LogSetNumber.ItemName

Session Number : Whenever the user logs in, the initial initialisation process of the tEC environment
is performed. It loads the active profile from TEC.ACTIVE.ITEMS on to the memory and also reads the
F.LOCKING table with the id TEC.SESSION.NUMER. This record contains a sequence number,
which is incremented by one and written back into the F.LOCKING table. This incremented number is
the first part of the TEC.OUTPUT table. The field SESSION.MAX in the TEC.PROFILE table allows us
to set the maximum value that this session number can hold. For example, if this is set to 50, once the
session number crosses 50, it will automatically be reset to 1.

LogSetNumber : Making the TEC.OUTPUT file store all the activities for ever could be very
expensive on storage space. Therefore, the TEC.OUPUT file has been built with a self-cleaning
mechanism. There are 2 fields that control this in the TEC.PROFILE table namely, LOG.SETS (the
number of log sets to maintain) and FLUSH.TIME (the number of seconds after which the data will be
flushed from the memory to the disk).

TEMENOS Confidential Page 9 of 23 Oct 2004

T24 Enterprise Console

ItemName : Name of the item whose activity has been recorded.

TEMENOS Confidential Page 10 of 23 Oct 2004

T24 Enterprise Console

Overview of Input and Processing

The most important thing that we need to understand about the tEC is that it is not controlled by any
phantom. The tEC starts monitoring the activities only when a user logs in or when the COB is initiated
and stops monitoring when the user logs off of when the COB is over as the case may be.

Worked Example
Let us understand the working of the tEC using a simple example.
Assume that the following record is created in the TEC.PROFILE table and verified:

Field Name Value

TEC.PROFILE.ID TEC.TRG.PROFILE
LL.DESCRIPTION TEC TRAINING PROFILE
LOG.SETS 5
FLUSH.TIME 60
XX.ITEMS READ.RESPONSE
XX.USER INPUTTER
REFRESH.TIME
SESSION.MAX 50

So, the only item that we wish to monitor is the time taken for every F.READ to be executed.
When the user INPUTTER signs on, the active profile in the TEC.ACTIVE.ITEMS gets loaded on to
the memory. The load routine will then check to see if the current user needs to be monitored and
monitor only if the current signed on user name is specified in active profile (TEC.PROFILE record).

If the user performs an activity that invokes an F.READ, (e.g. typing CUSTOMER L), find below the
sample data that could be written on to the TEC.OUTPUT file for the READ.RESPONSE item.

Field Name Value Description

ID 1.1.READ.RESPONSE ID
ITEM.TYPE READ.RESPONSE The active item name
ITEM.DETAIL FBNK.CUSTOMER The names of the files that were
read/written/selected by the activity
THRESHOLD
THRES.COUNT 1 The number of times the activity has been
invoked
THRESHOLD.TOTAL ID of the record read/written/executed
METRIC.COUNT 1
METRIC.TOTAL 1001 The total time taken in milliseconds to execute

TEMENOS Confidential Page 11 of 23 Oct 2004

T24 Enterprise Console

the activity
METRIC.AVG
METRIC.HIGH 1001 The highest time taken in milliseconds to
execute the activity
TOP.KEY 100069 The ID of the record that took the highest time
to be read/written/executed
TXN.REF 100069 ID of the record read/written
APPLICATION CUSTOMER Application that triggered the activity
START.TIME 37685413 Start time
END.TIME 37716 End time

The ID of the TEC.OUTPUT table consists of the following:

SessionNumber.LogSetNumber.ItemName

Session Number : Whenever the user logs in, the initial initialisation process of the tEC environment
is performed. It loads the active profile from TEC.ACTIVE.ITEMS on to the memory and also reads the
F.LOCKING table with the id TEC.SESSION.NUMER. This record contains a sequence number,
which is incremented by one and written back into the F.LOCKING table. This incremented number is
the first part of the TEC.OUTPUT table. The field SESSION.MAX in the TEC.PROFILE table allows us
to set the maximum value that this session number can hold. In our case it is set to 50. Hence, once
the session number crosses 50, it will automatically be reset to 1.

LogSetNumber : Making the TEC.OUTPUT file store all the activities for ever could be very
expensive on storage space. Therefore, the TEC.OUPUT file has been built with a self-cleaning
mechanism. There are 2 fields that control this in the TEC.PROFILE table namely, LOG.SETS (the
number of log sets to maintain) and FLUSH.TIME (the number of seconds after which the data will be
flushed from the memory to the disk).

In our case, these 2 fields have the following values

LOG.SETS : 5
FLUSH.TIME : 60

For the first time after the user signs on or when the COB is initiated, when activities gets recorded,
the log set number is set to 1 and therefore the records with the following ids will be formed:

SessionNumber.1.ItemName

Once the data gets flushed from the memory to the TEC.OUTPUT file, the log set number is
incremented (by one). Hence, the activities that get recorded after the first flush of data to the
TEC.OUTPUT table will have the following id:

TEMENOS Confidential Page 12 of 23 Oct 2004

T24 Enterprise Console

SessionNumber.2.ItemName

Since we have set the LOG.SETS to 5 in the TEC.PROFILE, once the log set number crosses 5, it
would get reset 1. Once the log set number gets reset to 1 data in the TEC.OUTPUT file will start
getting overwritten. What this means to us is, if we set LOG.SETS to 5 and FLUSH.TIME to 60, we
would at any point in time have the activities performed by an user in the last 5 minutes.

ItemName : Name of the item whose activity has been recorded.

Dynamic modification of active profile

It is possible for the active TEC.PROFILE to be updated whilst the user is logged in, so that the list of
active items to be monitored will be changed dynamically. However it is not possible to make a
different TEC.PROFILE the active one, as the active profile once loaded on to memory during sign
on/COB initialisation is reset only when the user signs off/COB is complete.

Monitoring custom items using tEC

TEC provides us with the flexibility to monitor custom items. The following example describes in detail
the steps to monitor a custom using tEC.

Monitoring custom items with metric type TIME

Scenario
Monitor the execution time of the following subroutine

SUBROUTINE TEC.CUSTOM.ITEM.TIME.TRAINING
$INSERT I_COMMON
$INSERT I_EQUATE
MSLEEP(1000) ; * Sleep for 1000 milliseconds (ie) 5 seconds
RETURN
END

Step 1
Create an item in the TEC.ITEMS file so that it can be used to monitor your subroutine.

Field Name Value

TEC.ITEM.ID TRAINING.TEST1
LL.DESCRIPTION Execution time of TEC.CUSTOM.ITEM.TRAINING routine
TYPE TIME

TEMENOS Confidential Page 13 of 23 Oct 2004

T24 Enterprise Console

XX<THRESHOLD.TYPE
XX>THRESHOLD

Step 2
Create a new record in TEC.PROFILE and add this item to it. Alternatively, you could add the custom
item to any one of the existing records in the TEC.PROFILE table.

Field Name Value

TEC.PROFILE.ID TEC.TRG.PROFILE1
LL.DESCRIPTION TEC TRAINING PROFILE
LOG.SETS 5
FLUSH.TIME 60
XX.ITEMS TRAINING.TEST1
XX.USER INPUTTER
REFRESH.TIME
SESSION.MAX 50

Step 3
In order to monitor the above-mentioned subroutine, the subroutine needs to call the
TEC.START.TIMER and the TEC.STOP.TIMER routines.
Change the above subroutine to include a call to TEC.START.TIMER and TEC.STOP.TIMER

TEC.START.TIMER and TEC.STOP.TIMER Routines

This API, together with TEC.STOP.TIMER, is used to log items that have a metric type of TIME.

TEC.START.TIMER (MY.TIMER.KEY, MY.TYPE)

TEC.STOP.TIMER (MY.TIMER.KEY, MY.TYPE, MY.DETAILS)

MY.TYPE Used to identify the TEC.ITEMS that is being logged. Can be left blank if the
routine is to be used to calculate the execution time of a routine. If it is going
to be used to calculate the read/write time per transaction, then it needs to
hold the transaction reference.
MY.TIMER.KEY Used to identify the item such that the timer can subsequently be stopped
using the TEC.STOP.TIMER API.
MY.DETAILS Will hold the detail level information on the item that you are recording.

MY.KEY = THE.TXN.REFERENCE
MY.TYPE = WHATEVER.IM.MEASURING

TEMENOS Confidential Page 14 of 23 Oct 2004

T24 Enterprise Console

CALL TEC.START.TIMER(MY.KEY, MY.TYPE)

CALL TEC.STOP.TIMER(MY.KEY, MY.TYPE,MY.DETAIL)

SUBROUTINE TEC.CUSTOM.ITEM.TIME.TRAINING
$INSERT I_COMMON
$INSERT I_EQUATE
Y.RETURNED.DETAILS =
CALL TEC.START.TIMER(,TRAINING.TEST1)
MSLEEP(1000)
CALL TEC.STOP.TIMER(,TRAINING.TEST1,Y.RETURNED.DETAILS)
RETURN
END

Step 4
Now verify the TEC.PROFILE record, log in, execute the routine (remember to make an entry in the
PGM.FILE with PGM.TYPE set to M in order to execute the routine as a mainline routine).
Check the TEC.OUTPUT to view the recorded activity.

Field Name Value

ID 1.1.TRAINING.TEST1
ITEM.TYPE
ITEM.DETAIL TRAINING.TEST1
THRESHOLD
THRESHOLD.COUNT 1
THRESHOLD.TOTAL
METRIC.COUNT 1
METRIC.TOTAL 1001
METRIC.AVG
METRIC.HIGH 1001
TOP.KEY
TXN.REF
APPLICATION TEC.CUSTOM.ITEM.TIME.TRAINING
START.TIME 37685413
END.TIME 37716

TEMENOS Confidential Page 15 of 23 Oct 2004

T24 Enterprise Console

Monitoring items with metric type SIZE

Scenario
In the following subroutine, the size of the selected list of ids needs to be monitored.

SUBROUTINE TEC.CUSTOM.ITEM.SIZE.TRAINING
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.CUSTOMER
FN.CUS = F.CUSTOMER
F.CUS =
SEL.LIST =
RET.CODE =
NO.OF.REC = 0
CALL OPF(FN.CUS,F.CUS)
SEL.CMD = SELECT :FN.CUS
CALL EB.READLIST (SEL.CMD,SEL.LIST,,NO.OF.REC,RET.CODE)
RETURN
END

Step 1
Create an item in the TEC.ITEMS file so that it can be used to monitor your subroutine.

Field Name Value

TEC.ITEM.ID TRAINING.TEST2
LL.DESCRIPTION Execution time of TEC.CUSTOM.ITEM.SIZE.TRAINING routine
TYPE SIZE
XX<THRESHOLD.TYPE
XX>THRESHOLD

Step 2
Create a new record in TEC.PROFILE and add this item to it. Alternatively, you could add the custom
item to any one of the existing records in the TEC.PROFILE table.

Field Name Value

TEC.PROFILE.ID TRAINING.TRG.PROFILE2
LL.DESCRIPTION 35A
LOG.SETS 5

TEMENOS Confidential Page 16 of 23 Oct 2004

T24 Enterprise Console

FLUSH.TIME 60
XX.ITEMS TRAINING.TEST2
XX.USERS INPUTTER
SESSION.MAX 50
REFRESH.TIME

Step 3
In order to calculate the size of the selected is the TEC.RECORD.ACTIVITY routine needs to be used.
Change the above subroutine to include a call to TEC.RECORD.ACTIVITY.

TEC.RECORD.ACTIVITY routine
This routine needs to be used when items of metric type SIZE need to be measured

TEC.RECORD.ACTIVITY(MY.TYPE,MY.KEY,MY.DETAILS,MY.VALUE)

MY TYPE Item name

MY.KEY Id of the record if the routine is used to measure the size of a
record/Descriptive String
MY.DETAILS Name of the file on which the read/write/select is being performed
MY.VALUE Size of the record/element being measured

Now modify the routine to call TEC.RECORD.ACTIVITY

SUBROUTINE TEC.CUSTOM.ITEM.SIZE.TRAINING
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.CUSTOMER
FN.CUS = F.CUSTOMER
F.CUS =
SEL.LIST =
RET.CODE =
NO.OF.REC = 0
CALL OPF(FN.CUS,F.CUS)
SEL.CMD = SELECT :FN.CUS
CALL EB.READLIST(SEL.CMD,SEL.LIST,,NO.OF.REC,RET.CODE)
CALL TEC.RECORD.ACTIVITY(TRAINING.TEST2,Size of selected list,FN.CUS,
LEN(SEL.LIST))
RETURN
END

TEMENOS Confidential Page 17 of 23 Oct 2004

T24 Enterprise Console

Step 4
Now verify the TEC.PROFILE record, log in, execute the routine (remember to make an entry in the
PGM.FILE with PGM.TYPE set to M in order to execute the routine as a mainline routine).
Check the TEC.OUTPUT to view the recorded activity.

Field Name Value

ID 1.1.TRAINING.TEST2
ITEM.TYPE
ITEM.DETAIL TRAINING.TEST2
THRESHOLD
THRESHOLD.COUNT 1
THRESHOLD.TOTAL
METRIC.COUNT 1
METRIC.TOTAL 250
METRIC.AVG
METRIC.HIGH 250
TOP.KEY
TXN.REF
APPLICATION TEC.CUSTOM.ITEM.SIZE.TRAINING
START.TIME 37685413
END.TIME 37716

Monitoring GLOBUS using tEC

There are a number of tEC enquiries that can be used to monitor the various activities that we have
specified in TEC.PROFILE. All these graphical enquiries are built into T24 and get installed when T24 is
installed.

The tEC enquiries build data from the TEC.DISPLAY file that has a similar structure to the
TEC.OUTPUT file. As the data in the TEC.OUTPUT file is bound to change rapidly, the tEC enquiries
transfer the data from the TEC.OUTPUT file to the TEC.DISPLAY file. The TEC.DISPLAY file is
always cleared before data is placed into it.
The controlling factor of the tEC enquiries is the REFRESH.TIME field in the TEC.PROFILE. This field
specifies the time with in which, if a tEC enquiry is executed, the data in TEC.DISPLAY will not be
rebuilt. The default value of this field is 15 seconds.

The tEC enquiries display data that correspond to the THRESHOLDs that we specify in the
TEC.PROFILE. Let us understand this with a simple example:

TEMENOS Confidential Page 18 of 23 Oct 2004

T24 Enterprise Console

Sample TEC.ITEMS record

Field Name Value

TEC.ITEM.ID WRITE.SIZE
LL.DESCRIPTION Size of record written
TYPE SIZE
XX<THRESHOLD.TYPE INFO
XX>THRESHOLD 30 (Records with size 0 30)

XX<THRESHOLD.TYPE WARNING
XX>THRESHOLD 100 (Records with size 31 100)
XX<THRESHOLD.TYPE CRITICAL
XX>THRESHOLD (Records with size 101 and above)

TEMENOS Confidential Page 19 of 23 Oct 2004

T24 Enterprise Console

Enquiry TEC.DETAIL
File on which the enquiry is based : TEC.DISPLAY
Build routine : TEC.PRODUCE.DISPLAY
Mandatory selection criteria : ITEM.TYPE
Details : Displays the activities of a particular type.

Figure 1 TEC.DETAIL Enquiry

Information
Warning
Critical

TEMENOS Confidential Page 20 of 23 Oct 2004

T24 Enterprise Console

Enquiry TEC.SUMMARY
File on which the enquiry is based : TEC.DISPLAY
Build routine : TEC.PRODUCE.DISPLAY
Mandatory selection criteria : METRIC TYPE
Details : Displays the consolidated position of the activities of
a particular metric type.

Figure 2 TEC.SUMMARY enquiry

TEMENOS Confidential Page 21 of 23 Oct 2004

T24 Enterprise Console

Enquiry TEC.OVERVIEW

File on which the enquiry is based : DATES

Build routine : -
Mandatory selection criteria : -
Details : Displays the details of the T24 DATES file.

Figure 3 TEC.OVERVIEW enquiry

TEMENOS Confidential Page 22 of 23 Oct 2004

T24 Enterprise Console

Enquiry TEC.PANEL

File on which the enquiry is based : TEC.DISPLAY

Build routine : TEC.PRODUCE.DISPLAY
Mandatory selection criteria : -
Details : Displays the list of activities with are either at
the
WARNING or CRITICAL level.

Click on the DETAILS button to obtain more

details about the activity.

Figure 4 TEC.PANEL enquiry

TEMENOS Confidential Page 23 of 23 Oct 2004