Using DL DEFINE In T24

TEMENOS EDUCATION CENTRE

Warning: This document, is protected by copyright law and international treaties. 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 HEADQQATERS SA. Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the
maximum extent possible under applicable law. Information in this document is subject to change without notice.

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Version History
Version

Changes

1.0

Initial

2005

1.1

Changes

2007

B.Nandakumar

1.2

Total revamp, example

change, Browser
screen shots

2007

Alagammai

ADM1 2007.1

Date

Author

Reviewer

Copyright 2006 TEMENOS HEADQUARTERS SA

What You Will Learn In This session

What is DL.DEFINE and why do we need it?

Using the DL.DEFINE application
Setting up DL.PARAMETER

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Why Do We Need DL.DEFINE

To move data records and routines between T24 areas
To store data records and routines to a tape

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Task

On The Development Environment

Contains VERSION records that have been created
CUSTOMER,TRG

Contains ENQUIRY records that have been created

CUSTOMER.TRG.ENQ

Contains newly developed subroutines under TRG.BP

CUS.CHECK.TRG.RTN
AC.CHECK.TRG.RTN

Contains amended delivery related records

Message type 320

The above need to be moved to the UAT environment on a

different server

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

To Do

Define a record in DL.DEFINE application in the development

environment
Save the units on the development environment
Restore the units on to the UAT environment by verifying the
DL.PARAMETER application in the UAT environment
Upload the units in the UAT environment using DL.DEFINE
application

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Step 1 - Creating The DL.DEFINE Record In Development Env.

ID Holds the ID. ID will begin with the last 8 digits in the field
LICENSE.CODE in SPF
GB Description Holds a description about the records that are
available in the data library unit to be created
GB Short Desc Holds the short description if any
Operation can be S-save or R-restore. S in this case as we are
saving a unit which can be restored at any point in time
File Name T24 application or directory
Record Name valid ID from above mentioned application or
directory (i.e routine name )
Record Desc description of the record to be included

Delivery related records discussed later

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Step 1 - Alternatives

The list of routines under TRG.BP need not be specifed explicitly

Imagine a situation where most of the routines under TRG.BP
need to be exported to the UAT environemnt
Use the SELECT LIST field functionality
Create a select list and store under &SAVEDLISTS&
Specify the name of the select list in the field SELECT LIST in the
DL.DEFINE record
On pressing enter, the values in the select list will get automatically
populated

Syntax : File Name > Record ID

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Step 1 - Alternatives

Upload delivery related records

We could specify each of the records in every Delivery related
application such as DE.MESSAGE, DE.MAPPING etc
Or, we could use the fields Top Level Type and Top level Item

Top Level Type Delivery/Enquiry/Repgen/Version/Menu

Top Level Item ID of application mentioned in Top Level Type
On entering values in the above mentioned fields, all related files
and their record IDs will get automatically populated

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

Saving The Unit

Verify the DL.DEFINE record so that a unit gets saved.

Ensure that the field OPERATION is set to Save
Once verified, a directory TMNS000-TRG (ID of the DL.DEFINE
record) will get created under F.DL.DATA directory
This directory will contain all the data records and the routines that
we specified in the DL.DEFINE record

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

10

10

UAT Environment

Set up the DL.PARAMETER record

This is done to restore the saved unit from the development
environment. Verify the record
On verification, a record in the DL.DEFINE application is created
with ID TMNS000-TRG with Operation set to R
ID Always SYSTEM
Replace Chars and Replace With characters can be
replaced when the data library is stored
(DL.PARAMETER is verified with S operation)
Operation S or R
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 alone
overwritten
Restore Units Unit names to be restored
Save Units if blank, F.DL.DATA is saved
Tape Device Name of tape device

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

11

11

UAT Environment

Part of the DL.DEFINE record that has been created

automatically on verifying the DL.PARAMETER record
Note Operation is set to R
Verify this record. All data records will get restored in IHLD status
All subroutines will get restored under the DL.BP directory. Copy
to appropriate directories, compile and catalogue in the UAT
environment

ADM1 2007.1

Copyright 2006 TEMENOS HEADQUARTERS SA

12

12