You are on page 1of 22

TEMENOS

Enterprise Console

User Guide

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 2005 TEMENOS Holdings NV. All rights reserved.


Enterprise Console

Table of Contents
Introduction.............................................................................................................................................. 3
Feature Overview .................................................................................................................................... 3
Using TEC Monitor .................................................................................................................................. 4
Launching TEC Monitor ....................................................................................................................... 4
Customising TEC Monitor .................................................................................................................... 5
Introduction .......................................................................................................................................... 5
TEC.MONITOR.API ............................................................................................................................. 6
Configuration ........................................................................................................................................... 7
Introduction .......................................................................................................................................... 7
TEC.ITEMS.......................................................................................................................................... 7
TEC.THRESHOLD............................................................................................................................... 8
TEC.PROFILE ..................................................................................................................................... 8
TEC.ACTIVE.ITEMS............................................................................................................................ 8
TEC and Events................................................................................................................................... 9
Details of TEC.ITEMS........................................................................................................................ 10
Modifying profiles On the Fly........................................................................................................... 10
Application Design................................................................................................................................. 11
Data Production ................................................................................................................................. 11
TEC.OUTPUT .................................................................................................................................... 11
TEC.OUTPUT.HISTORY ................................................................................................................... 12
Worked Example................................................................................................................................ 13
TecPack................................................................................................................................................. 15
How does TecPack get built? ........................................................................................................... 15
What does TecPack contain? ............................................................................................................ 15
Sending TecPack Data to Temenos Support .................................................................................... 15
Appendices............................................................................................................................................ 16
Appendix 1 API Definitions ............................................................................................................. 16
Appendix 2 Worked example - Adding Custom Time Items to TEC ............................................ 17
Appendix 3 Worked Example Adding other custom items to TEC ............................................... 20

TEMENOS User Guide Page 2 of 22


Enterprise Console

Introduction
The T24 Enterprise Console (TEC) is a comprehensive system management framework, built to
internet standards, which 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, allowing 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.
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.
The TecPack extracts details on T24 performance, which are gathered automatically by the system,
and can be sent data back to Temenos for analysis. Temenos client services (support) can then
monitor T24 health and, therefore, be more pro-active in implementing solutions before the problem
becomes critical.
Standard T24 tools are used to build the TEC display. The composite screens, widgets, enquiries and
versions allow the features, display and workflow to be tailored to your requirements.

Feature Overview
Through the TEC monitor, the TEC offers a summary view of the T24 system in the following areas:

TEMENOS User Guide Page 3 of 22


Enterprise Console

Using TEC Monitor


Launching TEC Monitor
The TEC Monitor is a standard composite screen, named TEC.MONITOR, and hence is launched in
the standard way from browser using the command:
COS TEC.MONITOR
Of course, this command may be added to the standard T24 user experience mechanisms, e.g.
menus, enquiry drilldowns, etc.
The TEC Monitor is only available in T24s browser interface.

TEMENOS User Guide Page 4 of 22


Enterprise Console

Customising TEC Monitor

Introduction
The TEC Monitor uses the Workspace and Widgets functionality to define the content and layout of
the monitor. Content may be added from the TEC Monitor widget itself, or from the standard Widget
List.
Each Widget can be repositioned and resized by dragging and dropping the widget, or by grabbing the
resize handle at the bottom right of each widget. The whole screen automatically refreshes every
minute.
For full details, refer to the Workspaces and Widgets section of the Browser User Guide.

TEMENOS User Guide Page 5 of 22


Enterprise Console

TEC.MONITOR.API
In addition, the TEC monitor widget itself has a standard extension point (defined in EB.API) to add
items into the TEC monitor widget itself. An example is shown below:

SUBROUTINE TEC.MONITOR.API(responses,request)
!* Example TEC.MONITOR.API subroutine
* @return responses A dynamic array or items to add to TEC.MONITOR
* @param request Information passed in from TEC.SUMMARY.xml
*!
*--------------------------------------------------------------------------
$INSERT I_TEC.MONITOR.API
*--------------------------------------------------------------------------
responses = ''

response = ''
response<apiNames> = 'Custom Item' ; * The Name of the item to add
response<apiValues> = '27' ; * The value
response<apiDrills> = '' ; * Drilldown item, e.g. ENQ TEC.ITEM.DETAIL ITEM.TYPE EQ SECUIRTY
response<apiTypes> = '' ; * Type of the drilldown. Normally CMD
response<apiImages> = '' ; * Any Image to display with the item

responses<-1> = LOWER(response)

response = ''
response<apiNames> = 'Other Custom Item' ; * The Name of the item to add
response<apiValues> = '28' ; * The value
response<apiDrills> = ''
response<apiTypes> = '' ; * Type of the drilldown.
response<apiImages> = '' ; * Any Image to display with the item

responses<-1> = LOWER(response)
*--------------------------------------------------------------------------

RETURN

TEMENOS User Guide Page 6 of 22


Enterprise Console

Configuration
Introduction
The TEC is not controlled by phantoms, services or other background processes, but is an inherent
part of the T24 code base. The TEC starts monitoring activities when a user logs in or when a service
is initiated and stops monitoring when the user logs off of when the service terminates.
The lowest level of configuration is the TEC.ITEMS table, where items that may be monitored are
defined. Multiple TEC.ITEMS are combined into a TEC.PROFILE to determine which metrics to
monitor. In addition, default TEC.ITEMS are automatically added to the TEC.PROFILE. To activate a
TEC.PROFILE, the record should be verified.
NB It is not necessary to define a TEC.PROFILE, as the default profile is always active.

TEC.ITEMS
This is the main table where all the items that may be monitored are defined. Here, the definition of the
severity of a particular item is defined.
In the below example, a response time of less than 1000 milliseconds will assign a severity of INFO,
and a response time of greater than or equal 1000 milliseconds, but less than 3000 will assign a
severity of WARNING. Response times of 3000 milliseconds or greater will be flagged as critical. The
severity levels are used in the various TEC reports and enquiries.

TEMENOS User Guide Page 7 of 22


Enterprise Console

TEC.THRESHOLD
This table defines severity levels that are used by TEC.ITEMS. There are three default records,
though additional thresholds may, of course, be defined. The standard thresholds are:
Information
Warning
Critical

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).

To make a given profile the active profile, the record should be verified:

TEC.ACTIVE.ITEMS
This is a work file that holds the currently active profile. This file is automatically updated when the
TEC.PROFILE is verified.

TEMENOS User Guide Page 8 of 22


Enterprise Console

TEC and Events


A simple but powerful eventing mechanism is built into the TEC. TEC.ITEMS allows a given threshold
to be flagged as raising an event, in which case the item is added to an event list and pushed out via
the standard T24 API mechanism (EB.API) to a defined API named TEC.EVENTS.
This API takes one argument, the EVENT.LIST, containing the list of events in the layout defined in
I_F.EB.EVENT:
Field Name Descriptions
APP.NAME The T24 application that was active when the event occurred
APP.TYPE The VERSION that was active when the event occurred
APP.ID The record key that was active when the event occurred
EVENT.TYPE The key to the TEC.ITEM that generated the event
SHORT.DESCR The key data supplied to TEC.RECORD.ACTIVITY
EVENT.SEVERITY The bucket position that the event metric fell into
EVENT.PRIORITY The TEC.THRESHOLD of the event, e.g. CRITICAL
EVENT.DESCRIPTION The detail and value data supplied to TEC.RECOR.ACTIVITY in the format:
DETAIL :: VALUE

TEMENOS User Guide Page 9 of 22


Enterprise Console

Details of TEC.ITEMS
TEC.ITEM Description Always on
API.RESPONSE Response time for API call
ENQ.RESPONSE Enquiry build response time
FILE.OPEN Count of file opens
FILE.SIZE Size of opened files
LOCK.COLLISION Count of Lock Collisions 9
READ.RESPONSE Response times for record read
READ.SIZE Size of read records that have been read 9
SELECT.RESPONSE Select response time
TXN.METRICS.BROWSER Response time for utility requests made to 9
T24 to service browser requests, e.g.
menu screens, enquiry selection screens,
etc.
TXN.METRICS.CLEARING Response time for clearing messages. 9
N.B. multiple clearings transactions per
message
TXN.METRICS.COMMIT Total response time (including OFS and all 9
processing) for a transaction commit. The
is a super set of the metric
TXN.RESPONSE
TXN.METRICS.ENQUIRY Total response time (including OFS and all 9
processing) for An enquiry request. The is
a super set of the metric ENQ.RESPONSE
TXN.METRICS.VALIDATE Total response time (including OFS and all 9
processing) for a transaction validate
requests
TXN.METRICS.SERVICE Throughput metrics for a given service 9
(either online or CoB) showing throughput
per minute.
TXN.METRICS.OTHER Total response time (including OFS and all 9
processing) for any other OFS requests.
TXN.METRICS.FRAMES.ACCESSED For j4 / JR database, the number of frames 9
accessed before the record was found.
Requires Jbase 5.
TXN.RESPONSE Transaction commit response time, i.e.
from commit processing until database
update. Does not include time spent in
OFS
WRITE.RESPONSE Response time for record write
WRITE.SIZE Size of written records

Modifying profiles On the Fly


The contents of the active profile, or indeed the switching of the active profile, may be achieved by
modifying the relevant record and verifying that TEC.PROFILE record. The active profile definition is
reloaded according to the flush time defined on the profile, so it may take a few seconds for the
changes to take affect in all connected sessions.

TEMENOS User Guide Page 10 of 22


Enterprise Console

Application Design
Data Production
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:

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

TEMENOS User Guide Page 11 of 22


Enterprise Console

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).

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

TEC.OUTPUT.HISTORY
All items are automatically consolidated into the historic TEC data store. The layout of this data is:

Field Name Description


TEC.HISTORY.ID Session number . Julian Day . TEC.ITEM, e.g.
3.018.TXN.METRICS.COMMIT
METRIC.COUNT.HOUR Multi valued by hour, holds the total count of the items
METRIC.TOTAL.HOUR Multi valued by hour, holds the total value of the items
XX<TOP.KEY The top 20 keys for the day
XX>TOP.METRIC The corresponding top 20 metrics for the day

TEMENOS User Guide Page 12 of 22


Enterprise Console

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
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

TEMENOS User Guide Page 13 of 22


Enterprise Console

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:

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 a user in the last 5 minutes.

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

TEMENOS User Guide Page 14 of 22


Enterprise Console

TecPack
A COB job produces the file TecPack - which is a jBASE file (regardless of the target database for T24
data) stored in the main data account (specified in the SPF). It is overwritten everyday and contains
the following information:

Field Name Description


0 ID Unique ID (from ALLOCATE.UNIQUE.TIME)
1 TYPE Type of record SUMMARY, SPF, TEC, JOB, CORE, ERROR, REPORT
2-9 Spare Reserved fields
10 Key Key to main record (i.e. F.JOB.TIMES)
11-NN Data The actual record (various layouts)

How does TecPack get built?


BUILD.TEC.PACK is a new job in the COB to build the TEC Pack data. It runs in the O999 stage (last
job) at INT level. The .SELECT routine creates the TecPack file (or clears it if already there) as a j4 file
in the .data account.

What does TecPack contain?


The data file consists of the following specific records:
SUMMARY - a summary record Machine Date, Time, Bank Date, Site Name
SPF - a copy of the SPF record to the TecPack
JDIAG - jBASE jDIAG output
The contents of the following tables are also added:
F.TEC.OUTPUT.HISTORY (new file R07)
F.JOB.TIMES
F.REPORT.TIMES
F.SEAT.RESULTS
F.EB.EOD.ERROR
In addition, all core dumps in the main account are added to the data file.
NB No client specific, private or sensitive data is added to the TecPack.

Sending TecPack Data to Temenos Support


The entire TecPack file should be compressed and emailed to Help Desk when requested.

TEMENOS User Guide Page 15 of 22


Enterprise Console

Appendices
Appendix 1 API Definitions
TEC.START.TIMER and TEC.STOP.TIMER
These APIs are 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)

Where:
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.
Example:
MY.KEY = THE.TXN.REFERENCE
MY.TYPE = WHATEVER.IM.MEASURING
CALL TEC.START.TIMER(MY.KEY, MY.TYPE)
CALL TEC.STOP.TIMER(MY.KEY, MY.TYPE,MY.DETAIL)

TEC.RECORD.ACTIVITY
This API is used when items of any metric type other than time needs to be measured.

TEC.RECORD.ACTIVITY(MY.TYPE,MY.KEY,MY.DETAILS,MY.VALUE)
Where:
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

OFS Syntax
For full details refer to the OFS User Guide.

TEMENOS User Guide Page 16 of 22


Enterprise Console

Appendix 2 Worked example - Adding Custom Time Items to


TEC
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 (i.e.) 1 second
RETURN
END

TEC.ITEMS Creation
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
XX<THRESHOLD.TYPE
XX>THRESHOLD

TEC.PROFILE
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

TEMENOS User Guide Page 17 of 22


Enterprise Console

REFRESH.TIME
SESSION.MAX 50

Modify code
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.

SUBROUTINE TEC.CUSTOM.ITEM.TIME.TRAINING
$INSERT I_COMMON
$INSERT I_EQUATE

response =
CALL TEC.START.TIMER(,TRAINING.TEST1)
MSLEEP(1000)
CALL TEC.STOP.TIMER(,TRAINING.TEST1,response)
RETURN
END

Check Results
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

TEMENOS User Guide Page 18 of 22


Enterprise Console

METRIC.AVG

METRIC.HIGH 1001

TOP.KEY

TXN.REF

APPLICATION TEC.CUSTOM.ITEM.TIME.TRAINING

START.TIME 37685413

END.TIME 37716

TEMENOS User Guide Page 19 of 22


Enterprise Console

Appendix 3 Worked Example Adding other custom items to TEC


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

TEC.ITEMS Creation
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

TEMENOS User Guide Page 20 of 22


Enterprise Console

TEC.PROFILE
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
FLUSH.TIME 60
XX.ITEMS TRAINING.TEST2
XX.USERS INPUTTER
SESSION.MAX 50
REFRESH.TIME

Modify Code
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. 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 User Guide Page 21 of 22


Enterprise Console

Check Results
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

TEMENOS User Guide Page 22 of 22