TEMENOS T24

Data Library

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.

Data Library

Table of Contents
Overview.................................................................................................................................................. 3 
DL.DEFINE .......................................................................................................................................... 3 
Saving or exporting units to the Data Library ................................................................................... 5 
Restoring or Importing units from the Data Library .......................................................................... 5 
DL.PARAMETER ................................................................................................................................. 6 
Saving or Exporting the Data Library to tape ................................................................................... 6 
Copying units from one data library to another ................................................................................ 7 
Replacing sensitive data .................................................................................................................. 8 
Example ........................................................................................................................................... 8 

TEMENOS T24 User Guide

Page 2 of 11
Data Library

Overview

The T24 Data Library application facilitates the copying of data between different T24 databases on
one machine and also between different implementations of T24 (different machines or locations).
The Data Library applications provide a data import and export facility for T24.

Data is stored in the Data Library in logical units, for example, Dutch Bank Returns. Each unit is
defined on the data library definition file, DL.DEFINE, by listing all programs and data items that
make up that unit. Programs and data can be saved to the data library or restored from the data library
into the T24 unauthorised files by using the “V”erify mode in DL.DEFINE.

Data units can be copied between different versions of the data libraries (for example, from the data
library in a test account into the data library in the live account), by using the “V”erify mode in
DL.PARAMETER.

Accompanying the Data Library applications ‘ready to import’ data units are supplied with the T24
release. This data repository contains any data thought by implementers or users of T24 to be of use
to other sites.

Any T24 site can contribute to this repository by exporting required data units via the Data Library
application and saved accordingly. These data units can be sent to TEMENOS Development to be
merged into a central library. This central library is included in T24 upgrade releases, so that the
information is available to all sites. It is also included in new implementation releases, so that new
implementations have access to all the data.

N.B. Since the contents of the Data Library repository is not ‘owned’ by TEMENOS it can be
viewed ‘Shareware’ and as will all shareware, the distributor, in this case TEMENOS, does not
accept any liability for the data or programs contained in the Data Library - it is the user’s
responsibility to ensure that all data and programs being installed through the Data Library are
checked and tested thoroughly before being used in a live environment.

Setup
DL.DEFINE
The Data Library Definition file, DL.DEFINE, is used to define all the records and programs that
make up each unit. By running DL.DEFINE in “V”erify mode, units can either be saved to the Data
Library, by setting the OPERATION to “S” - Save, [EXPORT] or units can be restored from the data
library into the unauthorised T24 files, by setting the OPERATION to “R” – Restore [IMPORT].

TEMENOS T24 User Guide

Page 3 of 11
Data Library

Data Library Definition file: DL.DEFINE

DL.DEFINE field defs

• DESCRIPTION - Descriptions of the purpose of the unit and what it contains
• SHORT.DESC - Short description of the unit
• LANGUAGE/COUNTRY - The language or country the unit relates to. This field can be used for
selecting all the units relating to a particular country or language.
• INDICES - Keywords which can be used for selecting units relating to a particular function.
• OPERATION - “S” to Save [EXPORT] or “R” to restore [IMPORT] a saved unit.
• SELECT.LIST - If you have entered all the program/data items into a select list, enter the name
of the select list. This select list will then be used to populate the field FILE.NAME and
RECORD.NAME. Records should be entered in the select list as file_name>record_name, e.g
ENQUIRY>ENQ.POS1 or BP>ENQ.SUB1
• TOP.LEVEL.TYPE - For some data items, you can enter the TOP.LEVEL.TYPE and
TOP.LEVEL.ITEM. All associated data records and programs will be used to populate the
FILE.NAME and RECORD.NAME. Top level types which can be entered are: DELIVERY,
REPGEN, VERSION, ENQUIRY
• TOP.LEVEL.ITEM The name of a record on a top level file. This will be used to populate the
field FILE.NAME and RECORD.NAME (For DELIVERY the record is taken from DE.MESSAGE).

• FILE.NAME - The names of the files containing the records to be saved (e.g. ENQUIRY).
• RECORD.NAME - The names of the records to be saved (e.g. ENQ.POS1)
• RECORD.DESC - Description of each record in the unit

TEMENOS T24 User Guide

Page 4 of 11
Data Library

• SAVE.FORMAT - If you which to save the unit in an XML format then this should be set to “XML”.
If this field is left blank then units will be saved using the usual Data Library format. NOTE: if you
select “XML” then the resulting unit can only be Restored [IMPORTED] to the target T24 system
using the T24 Data Library component provided by the T24 ToolBox product.

Saving or exporting units to the Data Library

Once you have completed all work for a distinct function, the data records and programs (for example,
subroutines used in an ENQUIRY), can be saved to the Data Library into a unit. This is achieved by
entering a record into DL.DEFINE. Care should be taken in naming the unit, so that it will be
meaningful to others (e.g. NL.BANK.RETURNS). Once entered, the id is prefixed with your bank code
(the last seven digits from your license code on the SYSTEM record on the SPF), e.g. TMNS001-
NL.BANK.RETURNS.

To save the data from the T24 files to the Data Library, run DL.DEFINE in “V”erify mode. Once the
records have been successfully saved into a unit within the Data Library, the fields, SAVED.RELEASE
and SAVED.DATE on DL.DEFINE are updated, to maintain a history of when the unit was saved.

Restoring or Importing units from the Data Library

When the Data Library is delivered, either on an implementation tape, or updated through
GLOBUS.RELEASE, or units are copied from one data library to another using the “V”erify mode in
DL.PARAMETER with the OPERATION set to “R”estore [IMPORT], the corresponding definition
records will be updated on the Data Library definition file, DL.DEFINE. Therefore, you can examine
this file to determine if there are any units that may be of use to you. The description and indices
fields should aid your search of this file.

If there is a unit you wish to restore/import, run DL.DEFINE in “V”erify mode, with the operation set
to “R”estore. The following actions will be performed:

If a FILE.CONTROL record is contained in the unit, the file will be created, provided the product is
installed.

• Each data record listed in the unit selected will be copied into relevant unauthorised file, with the
status set to “IHLD”. The records are mapped taking into account the release at which the records
were saved and the release at which they are being restored. E.g. If the records were saved at
G9.1.04 and you are currently on release G9.0.06, the records will be mapped into the G9.0.06
layout. However, when you input/authorise the records, there may be fields which are now
mandatory which were not present when the record was originally created, which you may have to
enter.
• Programs will be copied into DL.BP, regardless of the BP from which they were originally saved.

The fields RESTORED.USER, RESTD.COMPANY, RESTD.RELEASE and RESTD.DATE on

DL.DEFINE will be updated to maintain a history of when the unit was restored.

TEMENOS T24 User Guide

Page 5 of 11
Data Library

Programs are not automatically compiled and catalogued by the Data Library restore. Use
EB.COMPILE to do this, once you are happy with the programs that have been released.
EB.COMPILE can either be run with an active select list, e.g.

SELECT DL.BP
EB.COMPILE DL.BP

Or with a program name, e.g.

EB.COMPILE DL.BP TEST.PROG

These commands should be run from the jBASE prompt. Remember to recompile the programs when
you upgrade to a new release because inserts may have changed.

DL.PARAMETER
The Data Library Parameter file, DL.PARAMETER, enables data units to be copied from one Data
Library to another, or for specific units or the whole library to be saved to tape. The data library
parameter file contains only one record with an id of SYSTEM.

Data Library Parameter file: DL.PARAMETER

Saving or Exporting the Data Library to tape

TEMENOS will maintain the central data library, i.e. it will be built and kept up to date with units which
T24 clients and TEMENOS staff have developed and sent back to be merged into the central library.
However, the data library will only be as good as the data that is sent back to TEMENOS to be

TEMENOS T24 User Guide

Page 6 of 11
Data Library

included in it. Therefore, if you have developed something that you feel may be of use to other clients
and would like to share this data; your data library should be sent to TEMENOS Development.

You have the choice to send either specific units or the whole data library. To save the data library,
run DL.PARAMETER in “V”erify mode, setting the following fields:

• OPERATION - “S” to save [EXPORT] the data library on a UNIX operating system.
• SAVE.UNITS - The names of the units to be saved. Leave this field blank to save the whole
data library.
• TAPE.DEVICE - The name of the tape device to save to (e.g. /jev/rmt0) on a UNIX operating
system.

Currently, the saving of Data Library to tape is not available on NT. If you are an NT user, you should
use the Windows Explorer to save the required unit.

Copying units from one data library to another

If you have created a unit in the data library in your test account for example, and wish to copy the unit
into your data library in the live account, sign onto T24 in the account you wish updated (in this case,
the live account).
You have the choice to restore either specific units or the whole data library. Additionally, you can
specify whether existing units are overwritten or not, or overwritten only if the unit on the “from” data
library has been saved more recently than on the “to” data library.

To restore units, run DL.PARAMETER in “V”erify mode, setting the following fields:

• OPERATION - “R” to restore [IMPORT] the data library/units.

• FORM.FILE - The UNIX pathname of the data library from which units are to be
restored/imported (e.g. /T24/test/F.DL.DATA)
• OVERWRITING - Specifies whether existing units are to be overwritten if they are being
copied from the data library:
“Y” – overwrite units
“N” – do not overwrite units
“L” – only overwrite units if the unit on the ‘from file’ has been saved more recently
than on the ‘to file’.
• RESTORE.UNITS - The names of the units to be restored. Leave this blank to restore the whole
data library.

TEMENOS T24 User Guide

Page 7 of 11
Data Library

Replacing sensitive data

When you save data to the data library, there may well be data that you want removed, so that other
clients do not use it by mistake, for example, the name of your bank, your VAT registration number,
etc. To ensure that such data is removed, enter the character strings you want replaced and the
character strings you want to replace them on the SYSTEM record on DL.PARAMETER:

• REPLACE.CHARS - Characters to be removed (e.g. ANY.BANK).

• REPLACE.WITH - The characters to be substituted (e.g. **BANK**).
The number of characters in the REPLACE.WITH must be the same as the
number of characters in the REPLACTE.CHARS.
If REPLACE.CHARS is entered and REPLACE.WITH is left blank,
REPLCAE.WITH will default to asterixes.

Example
The diagram below illustrates saving a Data Library unit, moving the unit from a test account to the live
account, then verifying the unit to update the T24 unauthorised files in the live account.

Example movement for a Data Library Unit

For example, in your test account, you have set up various delivery advices for Fiduciaries. You now
want to copy these into your live account.

Step 1
Sign onto T24 in the test account. Create a record on DL.DEFINE, containing all the records you
wish to be copied.

TEMENOS T24 User Guide

Page 8 of 11
Data Library

Create record defining all records to be copied

Inputting the record will merely create the definition record in DL.DEFINE. To save the enquiry
records to the data library, “V”erify the record (the OPERATION will automatically be set to “S” to save
[EXPORT] the records).

TEMENOS T24 User Guide

Page 9 of 11
Data Library

Save [EXPORT] the records to the data library

Step 2
Sign onto T24 in the live account. To update the data library in the live account with the ENQUIRY
records that were created in the test account, verify the SYSTEM record on DL.PARAMETER, to copy
the unit from one data library to another. The units specified in RESTORE.UNITS will be copied over
from the data library specified in FROM.FILE. If RESTORE.UNITS is left blank, all units will be copied
over.

Records from one data library to another

TEMENOS T24 User Guide

Page 10 of 11
Data Library

Step 3

Restore [IMPORT] the records from the data library in the live account to the unauthorised ENQUIRY
file. This is achieved by “V”erifying the DL.DEFINE record TMNS000-2000.ENQUIRY, which was
copied over from the test account when the DL.PARAMETER record was verified.

Restore [IMPORT] the records from the data library to the unauthorised ENQUIRY file

The records are now on the unauthorised ENQUIRY file, in IHLD status. Input and authorise the
records, making sure that the records validate correctly.

TEMENOS T24 User Guide

Page 11 of 11