Scribd
Upload
157 views15 pages

3.using DL Define in t24

1. DL.DEFINE is used to move data records and routines between T24 environments and store them to tape for backup. 2. The process involves defining a record in DL.DEFINE in the development environment, saving the units, restoring the units in the UAT environment by verifying DL.PARAMETER, and uploading the units using DL.DEFINE. 3. Key fields in DL.DEFINE include Operation (S for Save, R for Restore), File Name, Record Name, and Select List for automatically including routines. Verifying DL.PARAMETER makes the saved units available for restoration.

Uploaded by

Berihun Tsegaye
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
157 views15 pages

3.using DL Define in t24

1. DL.DEFINE is used to move data records and routines between T24 environments and store them to tape for backup. 2. The process involves defining a record in DL.DEFINE in the development environment, saving the units, restoring the units in the UAT environment by verifying DL.PARAMETER, and uploading the units using DL.DEFINE. 3. Key fields in DL.DEFINE include Operation (S for Save, R for Restore), File Name, Record Name, and Select List for automatically including routines. Verifying DL.PARAMETER makes the saved units available for restoration.

Uploaded by

Berihun Tsegaye
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

1

ADM1-Using DL DEFINE In T24-R14


Trainee notes

2
ADM1-Using DL DEFINE In T24-R14
1. DL.DEFINE is basically used to move the data records and routines
between different T24 areas
2. This also could be helpful in storing the data records and routines to a tape
as a way of backup

3
ADM1-Using DL DEFINE In T24-R14
1. For our understanding, we are trying to move the following data from the
development environment.
1.1 The version records created by us
1.2 The Enquiry records created by us
1.3 The newly developed subroutines under BP
1.4 The amended delivery related records of message type 320

2. All these data need to be moved to a UAT environment on a different


server

4
ADM1-Using DL DEFINE In T24-R14
1. The first step for performing this task would be to define a record in the
application DL.DEFINE in the development environment
2. The next step is to create a copy of all the data that we need to move from
the development environment. These are called units.
3. Then we move these units to the UAT environment and restore them by
verifying the DL.PARAMETER application in the UAT environment.
4. The final step is to upload the units in the UAT environment using
DL.DEFINE application.

5
ADM1-Using DL DEFINE In T24-R14
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 BP directory

Record Name valid ID from above mentioned application or directory (i.e


routine name )

Record Desc description of the record to be included

ADM1-Using DL DEFINE In T24-R14


1. When there are a number of routines under BP, we need not specify them
all explicitly.
2. If most of the routines under BP are to be exported to the UAT
environment, we could use a simple method rather entering all the routines
manually.
3. We could use the SELECT LIST field functionality
3.1 we could create a select list and store under &SAVEDLISTS&
3.2 Then we need to specify the name of the list in the field SELECT LIST of
the DL.DEFINE record.
3.3 When committing the record, the values in the select list would
automatically get populated.

7
ADM1-Using DL DEFINE In T24-R14
1. The select list for the routines under BP is created under &SAVEDLISTS&
. The values of the select list record should contain the file name and the
record name. The syntax is File Name > Record ID
2. The name of the select list should be specified in the SELECT.LIST field of
DL.DEFINE
3. On commit, the values in the select list will get automatically populated.

8
ADM1-Using DL DEFINE In T24-R14
1. In order to upload delivery related records we have got different options.
1.1 We could specify each of the records in every delivery related application
such as DE.MESSAGE,DE.MAPPING
1.2 Alternatively we could also use the field Top Level Type and Top Level
Item

2. TOP.LEVEL.TYPE field could hold any of the values like


DELIVERY,ENQUIRY,REPGEN,VERSION.MENU
3. TOP.LEVEL.ITEM field would hold the ID of the application mentioned in
TOP.LEVEL.TYPE. For example when TOP.LEVEL.ITEM is DELVIERY,
the ID could be a valid record ID of DE.MESSAGE say 20
4. Once these values are entered and validated, their record ID’s gets
populated automatically.

9
ADM1-Using DL DEFINE In T24-R14
1. The first step is to use the ‘V’ function and verify the record created in
DL.DEFINE application.
2. Before verifying the record, make sure the OPERATION field of
DL.DEFINE is set to Save
3. Once verified a directory by the name of the DL.DEFINE record is created
under F.DL.DATA directory of UD folder.
4. This directory will contain the data records and routines that were specified
in the DL.DEFINE record.
5. This directory will be transferred to the UAT environment and restored to
UAT.

10
ADM1-Using DL DEFINE In T24-R14
1. The units from the development environment are to be stored in the UAT
environment. Then the SYSTEM record of DL.PARAMETER is configured to point
the path of the units from the development environment and then the record is
verified.
2. This is to get the saved units of the development environment available for
restoration in the UAT environment.
3. When the SYSTEM record of the DL.PARAMETER application is verified, a record
in DL.DEFINE application is created with the RESTORE operation defaulted.
When this record is verified, the units gets restored to the respective applications.
DL.PARAMETER application :
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
From File The path of the DL.RESTORE directory where the units to be restored are
available
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

11
ADM1-Using DL DEFINE In T24-R14
Tape Device : Name of tape device

ADM1-Using DL DEFINE In T24-R14


1. When the SYSTEM record of DL.PARAMETER is verified, system
automatically creates a record in DL.DEFINE application.
2. The Operation field is set to R (restore) by default
3. When this record is verified(using ‘V’ function), all the data records gets
restored in IHLD status
4. All subroutines will get restored under the DL_BP directory. Copy to
appropriate directories, compile and catalogue in the UAT environment

12
ADM1-Using DL DEFINE In T24-R14
1. DL.DEFINE is required to move data records and routines between T24
areas; to store data records and routines to a tape.

2. Steps for working with DL.DEFINE


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

13
ADM1-Using DL DEFINE In T24-R14
14
ADM1-Using DL DEFINE In T24-R14

You might also like