Using DL.

DEFINE in T24

DateOf Issue Version Changes By

Dec 2004 1.0 Screen shots added Sara Cleur

and a old document
redone

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.
DL Define

Table of Content
Introduction........................................................................................................................................... 3
DL.DEFINE ....................................................................................................................................... 3
Sample Screen Shots........................................................................................................................ 5
Storing information using the DL.DEFINE application ..................................................................... 10
DL.PARAMETER ............................................................................................................................ 12
Summary ............................................................................................................................................ 17

TEMENOS Training Publications Page 2 of 17 December 2004

T2BTT R06 1.0
DL Define

Introduction
Implementation of the T24 banking suite is not a one step process. It involves customising the T24
core applications as well as local developments to bridge the gaps that we find in the software and the
banks requirement. At the implementation site, there is usually more than one T24 area situated on
the same machine or sometimes-different machines. For example: All initial development may take
place in an area called DEVELOPMENT, the testing stage may be done in an area called TESTING
and then when all is ready, data records and programs will be moved into the LIVE area of the bank.
T24a Data Library (this is what the DL signifies) allows us to move data records and programs
between areas without much hassle.
Lets look at the process in detail.

The main applications involved are

1. The DL.DEFINE application
2. The DL.PARAMETER application

DL.DEFINE
This is the application where we actually define the Data Library unit. We can specify what records
from which applications or what routines need to be sent as a unit. The screen shot of the DL.DEFINE
application will give you a clear picture.

TEMENOS Training Publications Page 3 of 17 December 2004

T2BTT R06 1.0
DL Define

ID The ID of the DL.DEFINE record can be a meaningful text E.g:

TRG.EXAMPLE the TMNS000 before the ID is defaulted by the system.

DESCRIPTION The first two fields hold a description about the records that are available in
the Data Library unit about to be created.

LANGUAGE The language / country is not mandatory input.

OPERATION The Operation field is important, it can take the value S Save or R Restore.
When we create a Data Library we must ensure that this is set to S, so that
the records are stored as a unit in the area and can be moved to another
where they will be R Restored.

INDICES These contain keywords about the DL DEFINE record that will make
searching for the record in the list easier.

SELECT LIST Name of the select list containing the names of records which make up the
unit. It must a record in the &SAVEDLISTS& directory. Each line will contain
one record that must be included in the data library, in the format
APPLICATION>RECORD.ID. After the select list has been entered, the fields
FILE.NAME and RECORD.NAME will be cleared, then populated with the
contents of the select list; the select list name will be removed from
SELECT.LIST.

TOP LEVEL TYPE Could be one of the following applications DELIVERY ENQUIRY MENU
REPGEN VERSION.

TOP LEVEL ITEM This is used with the TOP LEVEL TYPE field. For example, if TOP LEVEL
TYPE is DELIVERY and the ITEM is set to 360, then all delivery related files
where the ID is related to 360 is automatically populated in the FILE NAME
and RECORD NAME fields

FILE NAME A valid T24 application name or a valid directory

RECORD NAME A valid record ID from the application mentioned above or a valid routine from
the directory.

RECORD DESC Description of the record included in the Data Library

SAVED FROM We can mention where the data was saved from.

SAVE FORMAT We can save the Data Library in XML format if required

TEMENOS Training Publications Page 4 of 17 December 2004

T2BTT R06 1.0
DL Define

Sample Screen Shots

The screen shots below, will enable us to get a clear picture on how use the DL DEFINE application.

Screenshot 1: As mentioned earlier, the FILE.NAME must hold a valid T24 application name and the
RECORD NAME must be a valid record ID in that application, otherwise an error message is
displayed.

TEMENOS Training Publications Page 5 of 17 December 2004

T2BTT R06 1.0
DL Define

Screenshot 2: In this, the records are selected from a valid directory instead of from a T24 application.
If the routine is not present an error message is displayed.

TEMENOS Training Publications Page 6 of 17 December 2004

T2BTT R06 1.0
DL Define

As soon as the <ENTER> key is pressed, all DELIVERY related applications (Example:
DE.MESSAGE, DE.MAPPING, DE.FORMAT.PRINT etc) will be populated with the records whose ID
starts with 360 is populated. These two fields are then cleared. For this, refer to the screen shot below.

TEMENOS Training Publications Page 7 of 17 December 2004

T2BTT R06 1.0
DL Define

Let us now see a screen shot of how DL DEFINE record can be populated using a record from the
&SAVEDLISTS& file.

The screen shot below, shows the details stored in the record in the &SAVEDLISTS& file.

The ID is TRG.EXAMPLE.
The format used with the record is APPLICATION NAME>RECORD NAME

TEMENOS Training Publications Page 8 of 17 December 2004

T2BTT R06 1.0
DL Define

The next two screen shots, show us how the DL.DEFINE record is populated with this information
when the ID of the &SAVEDLISTS& record is entered in the SELECT LIST field.

On pressing <ENTER>, the values are populated into the FILE NAME and RECORD NAME fields and
the SELECT LIST field is cleared. Refer screen shot below.

TEMENOS Training Publications Page 9 of 17 December 2004

T2BTT R06 1.0
DL Define

Storing information using the DL.DEFINE application

We have seen so far the various ways of creating this DL.DEFINE record. To actually save this
information, we have to verify this DL.DEFINE record. We must ensure that the operation field is set to
S. The data is then stored in a separate directory called TMNS000-TRG.EXAMPLE under the
F.DL.DATA directory (which is available under the mbdemo directory).
Use the VERIFY function to save the information.

TEMENOS Training Publications Page 10 of 17 December 2004

T2BTT R06 1.0
DL Define

Once the record is committed, let us see how the data has been saved.

TEMENOS Training Publications Page 11 of 17 December 2004

T2BTT R06 1.0
DL Define

This folder must now be moved to the required area / server and placed in the .RUN directory or in the
F.DL.DATA directory to be R Restored when required.

Note: If it has to be moved across servers, do an ASCII FTP

DL.PARAMETER
This is the parameter file that is used only when a Data Library needs to be restored. There is only
one record in this file with ID SYSTEM. The SYSTEM record must be set up and VERIFIED for the
data library to be restored. Let us take a look at a few screen shots to get a better idea.

TEMENOS Training Publications Page 12 of 17 December 2004

T2BTT R06 1.0
DL Define

ID Is always SYSTEM
REPLACE CHARS We can replace characters in the data library during its creation, i.e: when the
DL.DEFINE record is VERIFIED with the operation S.

REPLACE WITH Must contain the characters that are going to be replaced as the Data Library
is saved. The number of characters here must be the same as the number
mentioned in the REPLACE CHARS field.

OPERATION Can be set to S Save or R Restore.

When this is set to Save and the record is verified, the Data Library is saved
to tape specified in the field TAPE.DEVICE. If values are entered in
SAVE.UNITS then only those units are saved to tape or else the whole of
F.DL.DATA is saved to tape.
When this is set to Restore and the record is verified, the unit(s) mentioned in
RESTORE UNITS in the path mentioned in FROM.FILE, are copied into the
F.DL.DATA so that they will be available for the DL.DEFINE application.

OVERWRITING Y If units exist in F.DL.DATA, they will be overwritten

N The units are not overwritten
L Units that have been changed lately are written into F.DL.DATA

RESTORE UNITS Units that must be restored

SAVE UNITS When operation is save, these units alone will be saved to the tape

TAPE DEVICE Specifies name of tape device. When the SYSTEM record is verified with
operation set to S, a shell script dl_save.sh is created to save the units
mentioned in SAVE UNITS or to save the entire F.DL.DATA.

Let us now see how to set up the DL.PARAMETER record in the second area, to restore the
TMNS000-TRG.EXAMPLE unit.

Things to remember to set up

1. Operation R
2. From File Path where the unit exists (in this case F.DL.DATA)
3. Overwriting L (Default)
4. Restore Units TMNS000-TRG.EXAMPLE

TEMENOS Training Publications Page 13 of 17 December 2004

T2BTT R06 1.0
DL Define

Now VERIFY this record.

Now look for a record with ID TMNS000-TRG.EXAMPLE in the DL.DEFINE application. This is
created when the DL.PARAMETER record is VERIFIED.

TEMENOS Training Publications Page 14 of 17 December 2004

T2BTT R06 1.0
DL Define

Notice that the record has been created with the OPERATION set to R while all other fields have
remained the same, just like when we created it earlier. The record can now be restored and the
records will be written into the $NAU files of the corresponding applications

It is important to note that

Data records are written into the $NAU files of the corresponding applications
Routines are written into a directory called DL.BP, from where they must be copied to an
appropriate directory by the bank

The DL.DEFINE record must now be VERIFIED for the Data Library to be restored.

TEMENOS Training Publications Page 15 of 17 December 2004

T2BTT R06 1.0
DL Define

Once the record is committed, lets take a look at the records that have been created in the
VERSION$NAU file.

TEMENOS Training Publications Page 16 of 17 December 2004

T2BTT R06 1.0
DL Define

From the screen shot above, it is clear the 4 version records from the DL DEFINE record have been
restored.

Thus we have successfully moved data records across areas. The same can be done for routines. A
data library can contain both data records from applications as well as routines.

Summary

Data Library in T24 is used to copy data records from applications and routines from one T24
account to another on the same machine.
DL.DEFINE is the application used to define all the records and programs which make up
each unit.
DL.DEFINE record needs to be verified to either Save the data records or to Restore them
Records restored from the data library are put into the unauthorised T24 files if they are
routines, they are saved in DL.BP.
DL.PARAMETER can be used to copy the whole F.DL.DATA or certain units to a tape device
or it can create a record in DL.DEFINE that can be verified and the units restored from one
area to another.

TEMENOS Training Publications Page 17 of 17 December 2004

T2BTT R06 1.0