Temenos T24™

Build Control

Reference Guide

Information in this document is subject to change without notice.

The procedures and steps given in this document are only suggestive and should not be taken as recommended
This is not a Temenos Qualified Document.
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

Date Version Changes By

2004-08-19 1.0 New – Draft Sathish PS
2005-04-19 1.0 Various Changes Sathish PS

2 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

About this Document

This document aims at explaining the functionality of a non-core T24 Software & Data deployment tool
– [Link] – a tool that facilitates saving programs, data, Local ref definitions, Standard
Selection Idescriptors and restoring programs, (compile or catalog), data, updating the Local ref table,
Idescriptors and automatic authorisation of restored records.

3 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

Table of Content
About this Document.............................................................................................................................. 3
Table of Content..................................................................................................................................... 4
1. Introduction.................................................................................................................................. 6
2. Product Overview........................................................................................................................ 6
3. Tables.......................................................................................................................................... 7
3.1 [Link].................................................................................................................... 7
4. Working with [Link]................................................................................................ 10
4.1 Save Activities........................................................................................................................ 10
4.2 Release Activities................................................................................................................... 10
4.3 SAVE...................................................................................................................................... 11
4.3.1 Main Screen.................................................................................................................... 12
4.3.2 To Save a Package, come here......................................................................................12
4.3.3 Programs........................................................................................................................ 12
4.3.4 DL DEFINE Units............................................................................................................ 13
4.3.5 Dict Items........................................................................................................................ 14
4.3.6 LOCAL REF.................................................................................................................... 14
4.3.7 New Tables to be Released............................................................................................ 15
4.3.8 Flat Files......................................................................................................................... 16
4.3.9 Results............................................................................................................................ 16
4.4 Package Checklist.................................................................................................................. 17
4.5 RELEASE............................................................................................................................... 18
4.5.1 Main Screen.................................................................................................................... 18
4.5.2 To Release a Package, Come here................................................................................19
4.5.3 Authorisation Priority....................................................................................................... 20
4.6 Output.................................................................................................................................... 21
4.6.1 Contents of a Build Control Unit......................................................................................21
4.6.2 [Link]........................................................................................................................... 22
4.6.3 SAVEDLISTS.................................................................................................................. 22
4.6.4 [Link].................................................................................23
4.7 RELEASE............................................................................................................................... 25
4.8 [Link]..................................................................................................................... 28
4.9 [Link]........................................................................................................................ 28
4.10 [Link].......................................................................................................... 28
5. Technical Details....................................................................................................................... 29
5.1 [Link].................................................................................................................. 29
5.1.1 [Link]........................................................................................................... 29
5.1.2 [Link]............................................................................................. 29

4 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

5.1.3 [Link].............................................................................................................. 29
5.2 [Link]....................................................................................................... 29
5.3 [Link]......................................................................................................... 29
5.4 [Link]........................................................................................................ 30
5.5 [Link]................................................................................................. 30

5 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

1. Introduction
[Link] is a T24 Package deployment tool – very similar to [Link] except that it also
updates [Link] definition, [Link] Idescriptors, Automatic restoration
of Data records (using [Link]) & Authorisation of records restored using [Link].

2. Product Overview
[Link] is a deployment tool that could be used to install Non-core T24 applications
and to move packages developed locally, on-site, from one environment to another.
The basic idea is the same as [Link]. Save the details in one environment and release
them in another.
Typically, in any implementation, the developments and configurations will be done in the
Build environment and then moved to master and UAT environments and hence the name
‘[Link]’.
It provides the user with the facility/ability to
 Save programs, data libraries, local ref table definitions, standard selection descriptors
and release them in another T24 environment.
 Automatic restoration of data libraries using [Link]
 Automatic authorisation of restored records using OFS
 Release Idescriptors
 Update [Link] with the saved definitions
 Compile/Catalog the programs released
The resultant package will be saved in the path given in [Link] field, along with an Index that will
be used for Release operations. The contents of the package will be similar to [Link].

6 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

3. Tables
The [Link] package consists of one table – [Link]

3.1 [Link]
Given below, is a brief description on each of the fields in this table.
No. Field Name Description
@ID The only record allowed is SYSTEM
1 [Link] Description of the record
Mnemonic for the record key. No validations at the
2 MNEMONIC moment.
Could be one of SAVE, RELEASE, [Link],
3 ACTION [Link] or [Link]
4 RESERVED.4 Not used at the moment.
Path where the resultant BCON package will be
5 [Link] saved. Mandatory Input when ACTION is SAVE
Path where the resultant BCON package will be
Released. Mandatory Input when ACTION is not a
6 [Link] SAVE.
If programs are to be saved, this will be the BP from
which [Link] is expected to get the
programs. This could either be the source codes or in
case of releasing to client, then the $ files can be
7 [Link] selected and saved1
Criteria for selecting the programs from
8 [Link] [Link]
ID of the [Link] record that should be updated
with the programs Selected. This need not be an
existing [Link] record. If the record does not
exist, then it will be created by [Link] and
9 [Link] updated.
BP where the programs should be released in the
10 [Link] release environment.
Value of JBCDEV_LIB to be set when Compiling or
11 [Link] cataloging the programs in the Release environment
Value of JBCDEV_BIN to be set when Compiling or
12 [Link] cataloging the programs in the Release environment
If the lib itself is being created by [Link],
then this is the name to be added in the jLibDefinition
13 [Link] inside that new lib.
ID to another [Link] unit on which the
installation of this [Link] unit is
dependent on. This is only for information and basic
14 DEPENDENCY validation purposes.
15-17 RESERVED Reserved for future use
ID to [Link] ([Link] must be
18 [Link] GLOBUS), to authorise the restored data records.

1
Care should be taken to Transfer the [Link] unit in Binary mode, if the $ files are saved as part
of the delivery package.

7 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

19 XX<[Link] DL DEFINE to be saved

If the records in the [Link] are from a company
specific file, then the company from which the
20 XX>[Link] [Link] specified in Field 19 must be saved
ID of Local Ref Table. Associated with the subvalued
21 XX<[Link] field [Link]
ID to [Link]. Associated with the subvalued
field [Link]. This field, along with TABLE
ASSOC records the Local Ref definition for the
application specified in [Link] field.
When released, this definition will be updated in the
Local Ref table for that application and authorised
22 XX-XX<[Link] using OFS.
23 XX>XX>[Link] Sub valued field associated with [Link]
ID to [Link]. Associated with the
fields till [Link].41. Used to store Idescriptor
24 XX<[Link] details.
A valid I type USR Field in the Standard Selection
record specified in [Link] field. Once this
field is input, all the other fields like [Link],
[Link] etc. will be automatically populated
with the values in their corresponding fields in
25 [Link] [Link]
Equivalent of [Link] USR fields
automatically populated when [Link] is
26-37 SS FIELDS entered.
Multi valued fields associated with [Link]
38-41 [Link] Reserved for future use.
Names of tables for which a new
[Link] (and dictionary) need to be
42 [Link] built.
43-47 RESERVED Reserved for future use.
48-68 Currently not used.
If the package being released requires any flat files,
then the path of those flat files can be specified here.
While releasing, these files will be automatically
69 [Link] created.
Any special Shell Command to be invoked at the end
70 [Link] of SAVE or RELEASE actions.
Priority in which DL Restore records must be
authorised. For instance, ENQUIRY records may
need to be authorised before [Link]
71 [Link] records. Such a priority is entered in this field.
Special instructions while authorising – what should
be done if a Live record already exists. Allowed
72 [Link] values – OVERWRITE, LATEST or IGNORE
If the lib specified in [Link] does not exist, then
if this field is set to Y, the lib will be automatically
73 CREATE.LIB2 created.
74 CREATE.BIN3 If the bin specified in [Link] does not exist,
2
However, this lib has to be added to JBCOBJECTLIST in Login profile manually
3
However, this bin has to be added to PATH in Login profile manually

8 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

then if this field is set to Y, the bin will be

automatically created.
If [Link] doesn’t exist, then if this field is Y, it
75 [Link] will be created.
Path where [Link] will save Data Libraries.
When Saving, [Link] will call [Link]
to save each of the data libraries specified in the field
[Link] and then move those folders to the path
specified in [Link]. So, this path tells
[Link], where to look for the Saved data
76 [Link] libraries.
Path where [Link] has to release Data
Libraries. When releasing, [Link] will call
[Link] and subsequently [Link] to
release & restore the data libraries. So, this path tells
[Link], where to copy the data libraries to
77 [Link] be released, before calling [Link]
Operating System of the environment where this
78 [Link] package was saved.
If set to Y and committed, the details in the fields
79 [Link] ACTIVITY, [Link] will be cleared.
Multi valued field associated with [Link].
Updated during verification process, with the
progress of action specified – either SAVE or
80 XX<ACTIVITY RELEASE
81 XX>[Link] Progress information
If Y is entered in this field, the user has the option to
enter a Flat file name and a record in that file, to be
90 [Link] opened as a Report.

9 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4. Working with [Link]

Once the package has been installed, the version “[Link], MAIN” can be used for all the
actions – SAVE/RELEASE/[Link]/[Link]/[Link]
A Sample [Link] Unit has been delivered as part of this package, to try out and get
familiarised with the operations. To get started with [Link], go straight to Section 5.4 –
RELEASE, and release the sample package – [Link].
These units were saved in the same way explained in Section 5.14.
Before starting to work with Build Control on a T24 implementation site, it would help if
 A procedure is in place for Change management of developments
 A procedure is in place for moving developments from one environment (typically the dev or
build environment) to QA or UAT environment among others.
 A naming convention is in place for [Link] units that are saved and restored time to time
for a given package, to keep track of changes.

4.1 Save Activities

The Build Control system creates a package that includes Programs/Object Codes, [Link] units,
Local Ref definitions, Idesc Definitions, Flat File details, New tables to be released etc. Each of these
components are saved in a layered approach and the priority of these layers is as given below.
1. [Link] – Save [Link] units
2. [Link] – Refresh Idesc definitions from [Link]
3. CONSOLIDATE – Integrate all the DL DEFINE units from [Link] to [Link]/SAVE
4. PROGRAM – Use saved list or Select command to select programs and organise under
[Link]/SAVE
5. [Link] – Write a copy of [Link]
At the end of this process, a Build Control unit is created under the path specified in [Link] and
all the components are saved under that folder. A copy of [Link] is written to this folder, with the
name BCON_IDofBuildControl where IDofBuildControl is the ID to the Current [Link]
record being saved.

4.2 Release Activities

The Release/restore operation also follows a layered approach in restoring the components of the
Build Control Package. The order of these layers is as given below.
1. [Link] – Create any flat files defined
2. [Link] – Use DL PARAMETER RUN and DL DEFINE RUN to release/restore
[Link] units from [Link]/RELEASE
3. [Link] – Create RELEASE BP, if need be, Release programs, compile or catalog.
4. [Link] – Rebuild dictionary ([Link]) record for new tables.
5. [Link] – Release Dictionary definitions
6. [Link] – Authorise [Link] records if in IHLD and Release Local ref
definitions.

4
ID to [Link] follows the same convention as [Link].

10 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

7. [Link] – Not used currently

8. [Link] – Authorise records restored using [Link].

4.3 SAVE
 Enter [Link],MAIN5 at the Command Prompt.
 Enter the ID that you would like to give to your Build Control Package (Having a date
component will help)
 This will open up a set of associated versions as shown below.
 Commit the record.
 Open the record in V function and commit it. This will create a Build Control unit, similar to DL
DEFINE unit under the Build Control Save path.

5
Except for Release of Programs, [Link] supports operations from Browser. Where
Release of programs is involved, it must be done either in Desktop or Classic mode. After compilation,
however, tcserver needs to be stopped and restarted.

11 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.3.1 Main Screen

Use this screen to
 Enter the Action – SAVE/RELEASE/HOLD/[Link]/[Link]/DL.AUTH6
 Give a brief description on this package/in case of patch – what is the patch for
 Mnemonic – just some name – currently not used for any specific purpose.

4.3.2 To Save a Package, come here

Use this screen to define the path where
 [Link] Units will be saved
 [Link] will save the data (as in ../[Link])

What Happens
 SAVE – A new folder with the name same as the Record ID, is created under this path and the
build control unit is saved in this path (similar in function to [Link] Unit)
o In this case, a new folder [Link] will be created under
../[Link]/SAVE.

4.3.3 Programs
Use this screen to define
 the BP where the programs/object codes ($ Files) reside,
 the Selection criteria7 and
 the BP where the programs/object codes ($ Files) need to be restored in the destination
environment.
6
If the action is not SAVE, then enter the Action and go straight to Release tab ‘To Release a
package, come here’
7
This can either be a jQL statement or a Saved list prefixed by the key word ‘SL-‘.

12 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

 JBCDEV_LIB & JBCDEV_BIN to be set when Compiling/Cataloguing in the destination

environment8. Leaving these fields blank will result in the default JBCDEV_LIB and
JBCDEV_BIN, as defined in [Link] or .profile, being used.

What Happens
 SAVE – A new folder with the name same as the [Link] is created under Build
Control Unit Save path and the Saved list or the Select Command is used to Select the
[Link] and the records are copied to the Build Control path’s BP folder.
o In this case, a new folder [Link] will be created under
../[Link]/SAVE/[Link] and the selected
programs/object codes will be copied to that folder.
 RELEASE – The Release BP, if it doesn’t already exist, is created in the destination
environment and the contents of the BP in Build Control unit are copied to the Release BP.
After setting JBCDEV_LIB and JBCDEV_BIN to required values, the copied files – depending
on whether they are source or object codes, are either Compiled using [Link] or
Catalogued using CATALOG command.

4.3.4 DL DEFINE Units

Use this screen to
 Define the [Link] units that need to be saved as part of this package.
 Define the company from which the records defined in [Link] need to be saved, in
case there are FIN type file records

What Happens
 SAVE – The [Link] units are Saved by invoking [Link] and the resultant
[Link] units are copied into Build Control save path.
o In this case, the [Link] [Link] will be saved and the
resultant unit will be copied from ../[Link] to ../[Link]/SAVE/TMNS000-
[Link].

8
The path must be defined relative to Home directory – as in, $HOME/gdgitlib. While restoring, the
system will check if that path has been added to $JBCOBJECTLIST, else will return an error. Similarly,
JBCDEV_BIN path must have been included in $PATH.

13 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

 RELEASE – The DL DEFINE Unit [Link] from under

../[Link]/RELEASE/[Link], will be copied to
../[Link]/[Link] and [Link] and [Link] will be invoked
to release and restore the DL DEFINE records.

4.3.5 Dict Items

Use this screen to
 Define any Dictionary items – Idescriptor definitions that need to be saved as part of the
package.9

What Happens
 SAVE – The properties – like TYPE, FIELD NO, VAL PROG and all other Standard
Selection fields are saved in their corresponding fields in [Link] of [Link].
 RELEASE – The idesc name is checked in [Link] and updated with
the details from [Link]; the [Link] record is locked, updated and
written to $NAU. [Link] is used to authorise this
[Link] record and thereby rebuilding dictionary.

4.3.6 LOCAL REF

Use this screen to define
 the Local ref definitions for all the T24 applications that need to be part of this package10

What Happens
 SAVE – Nothing. The definitions are validated.
 RELEASE – based on the definitions and after ensuring that the Local ref fields are
available in [Link], the corresponding [Link] record is updated with
this definition. If the Local Ref is already attached to the application, then the Association
is overwritten with this definition.
9
Only enter the Standard Selection ID and the Idesc Name. The properties will automatically be
defaulted from [Link]. Every time the Build Control is Saved, these properties are
refreshed automatically from [Link].
10
Please note that the [Link] records being defined here must be present when the

14 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.3.7 New Tables to be Released

Use this screen to define
 New tables that are being released as part of this package, for which Standard Selection
record needs to be rebuilt.

What Happens
 SAVE – Nothing.
 RELEASE – A new record is locked and created in [Link], $NAU file,
on IHLD status. OFS GLOBUS MANAGER is used to authorise that record.
 Instead of saving the [Link] record for new tables as part of the
[Link], specify the name of the table here11.

11
This proves to be helpful when a new table is being released and an Idescriptor also needs to be
attached to that [Link]. Since the Authorisation of restored DL DEFINE records
happen after the activity of restoring Idesc definitions, there will be a run time error. However, by
specifying the table here, the [Link] is rebuilt even before Idesc activity is done
and hence restoring Idesc definitions will be successful.

15 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.3.8 Flat Files

Use this screen to define
 The path of flat files (Unix/NT directories – TYPE UD Files) that need to be created when
restoring this package

What Happens
 SAVE – Nothing
 RELEASE – The path, folders are created and a VOC pointer is created with ID as the last
part as the ID
o In this case, for instance, a folder in the path ../[Link]/ofs/[Link] will
be created and a VOC pointer will be created with ID as [Link].

4.3.9 Results
Once the Save operation is complete, the system will automatically display the results in the form of a
standard T24 Enquiry, as shown below.

16 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.4 Package Checklist

Use the enquiry [Link] to review the contents of the package.
 Shown below is a screen shot of this enquiry, running on a package called TMNS000-
[Link].

 Shown below is a screen shot of this enquiry, running on our sample package TMNS000-
[Link]

17 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.5 RELEASE
To release a package,
 Copy the [Link] unit under the Build Control Release path (typically
../[Link]/RELEASE)
 Launch [Link] and enter the name of the Build Control Unit as the ID (in this
case, [Link])
 Commit the record after following steps 5.4.1 and 5.4.2.
 Open the record in V function
 Commit the record and the package will be deployed12.

4.5.1 Main Screen

Use this screen to
 Enter the ACTION – RELEASE

12
If the deployment involves Compilation/Cataloguing of programs, then the system would prompt to
log off and login back before continuing with the rest of the restoration process and after the prompt, in
effect, will automatically log the user out of the session.

18 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.5.2 To Release a Package, Come here

Use this screen to
 Release a package – Enter the path where the Build Control unit has been copied to
o In this case, ../[Link]/RELEASE
o The system would check if there is a record BCON_IDofBuildControl is available
under the Release path/IDofBuildControl and if so, populate R.NEW13

 The path of DL DEFINE Restore path will automatically be defaulted from the Index
record. If that path does not exist, the system will return an error message.
 Define the [Link] record to be used by OFS GLOBUS MANAGER to authorise
Restored records.
o In this case, and all cases, by default, it will be [Link]
 The field ‘If a Live Record Exists’ is to tell the system what it should do when a record
released by DL DEFINE restoration, already exists in Live File
a) it should simply go ahead and authorise the restored DL DEFINE record
b) check which is the latest – the live or the restored and determine whether to authorise
or ignore based on that
c) Ignore the authorisation for that record.

13
Refer to Section 5.1 for the source of this Index

19 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.5.3 Authorisation Priority

 Define the priority of Authorisation for the restored records.
o The priority is to take care of dependency in authorising a record in a given
application, on another application. For example, a [Link] record
cannot be authorised until all the items defined in it (like VERSION, ENQUIRY)
are authorised.
o A default set of priority will automatically be populated by the system. The
operators can however, add/remove/change the priority.
o Prior to authorisation activity, all records restored as part of this package are
sorted based on the priority for their file names as defined here and the records
are authorised according to this priority.

20 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.6 Output
The following screen shot shows an example of a package saved by BUILD CONTROL14

4.6.1 Contents of a Build Control Unit

Shown below is the Content of the Build Control Unit [Link]
a) [Link] – Program BP
b) SAVEDLISTS – If a Saved list had been used instead of a Select Command, then that
Saved list will also be saved, under a folder SAVEDLISTS
c) [Link] – The DL DEFINE
d) BCON_TMNS000-[Link] – Index (Copy of [Link] to be used during
RELEASE Operations)

14
This screen shot is taken in a Windows environment. The folder structure will be the same in any
other platform too.

21 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.6.2 [Link]
This is the BP defined as [Link], from which programs were selected. Note that there were 2
programs in the Saved list [Link].PGMS15

4.6.3 SAVEDLISTS
If a Saved list had been mentioned in [Link] field, then that Saved list will be copied under this
folder. During RELEASE Operation, this will be copied over to &SAVEDLISTS& in the destination
environment.

15
Refer back to Section 5.3.3 for clarification.

22 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.6.4 [Link]
This is the [Link] to be saved part of the package 16. During RELEASE Operation, this will be
copied over to DL DEFINE restore path (typically, ../[Link]/[Link]) and restored/released
using [Link] and [Link].

16
Refer back to Section 5.3.4 for clarification

23 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

When verified, [Link] will create the resultant unit under [Link]/SAVE 17 (the
folder highlighted)

 The content of this [Link] Unit is shown below – 1 DL Unit of Data, 1 DL Unit of
Program and 1 File (BCON_TMNS000-[Link]) which will be the index used to
Load the release details during RELEASE Operation.

17
The screen shot shown here is from a T24 on jBASE NT environment. This directory structure holds
good for other platforms too.

24 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.7 RELEASE
 To test releasing a package, copy the [Link] unit [Link]
under [Link]/RELEASE.

 Sign into T24, Launch [Link],MAIN

 Open a new record with ID as [Link] (the system will automatically prefix it with
TMNS000-)
 In the ACTION field enter RELEASE18

 In the Release Tab, in the field ‘Release package is available under’, enter the path (only the
relative path – w.r.t the environment’s run directory) where the [Link] Unit has
been copied over.

 The system will, along with other details, default the path where DL Units need to be copied
(as in ../[Link]/[Link] or ../[Link]) which may not be the same in both
Save and Release environments. Manually change the value if the system raises an error.

18
DO NOT enter any value in the fields Package/Build Name or Mnemonic, during RELEASE
Operation.

25 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

 At field input, if the path is correct, then the system will load the record based on the index file
BCON_TMNS000-[Link] stored under the release path.
 Note, in the following 2 screen shots, that the system has populated the Release details.

26 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

 In the Release tab, in the field ‘OFS Source to be used for Authorising’ enter the ID of the
[Link] to be used for authorising the records. At this field input, the system will default
Authorisation Priority. The user can amend this priority as applicable.

 Commit the record

 Open the record again in V function and commit.
 The package will be installed19.
In a nutshell, to release a package, only 3 fields require Input from the user.
a) ACTION on the main tab
b) BUILD CONTROL Release path in the Release tab
c) OFS SOURCE Id to be used for Authorizing the Restored records.
To check if the package has been installed,
 Do a jshow –c in jbase for the program [Link]
 Check the status of [Link] record [Link], at the
command line.
 Check if a new I type field ‘[Link]’ is created in Standard Selection
record for [Link]

19
After releasing Programs, the system will prompt to be logged out and login again. After logging
back in, the Release process will continue from where it was left.

27 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

4.8 [Link]
With this action, [Link] releases all programs that are part of the DL Units specified in the
multi-valued field [Link].
Saving and Releasing Programs, works exactly the same way as RELEASE. To release a program,
the ACTION could be set to [Link] or RELEASE.
Since the sample [Link] unit [Link] contains programs, it can be
used for testing [Link] alone.
If the field [Link] is NULL, then programs will not be Compiled/Catalogued.
Note: If the user chooses to release using [Link], then, the Action must first be set to
[Link] and Verified first (so that the programs are restored). Subsequently, the Action can be
set to [Link] and Verified.

4.9 [Link]
With this action, [Link] restores all the data records part of the DL Units specified in the
multi-valued field [Link].
Since the sample [Link] unit [Link] also contains data records,
it can be used for testing [Link] alone.
When the ACTION is set to RELEASE, [Link] automatically copies the DL Units from
[Link]/RELEASE to the DL Restore path (as in, [Link]/[Link]), and then uses
[Link] & [Link] to release & restore those records.
However, when the Action is set to [Link], the system assumes that the required DL Units are
already present in the DL Restore path (as in [Link]/[Link] or ../[Link]). The
user has to move the DL Units manually under the DL Restore path before setting the Action to
[Link]

4.10 [Link]
With this action, [Link] authorises all the data records part of DL Units specified in the
multi-valued field [Link]
Since the sample [Link] unit [Link] also contains data records,
it can be used for testing [Link] alone.
This will enable Authorisation of Restored records. However, when Action is set to
[Link], the system assumes that the records have already been restored and will only
attempt to authorise them.
Note: If the user chooses to authorise using [Link], then, the Action must first be set to
[Link] and Verified (so that the programs/records are restored). Subsequently, the Action can
be set to [Link] and Verified.

28 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

5. Technical Details
This section covers some of the significant programs involved in the process.

Click here to see a diagrammatic representation of the process flow for [Link]

5.1 [Link]
This section covers an overview of Validations done at various stages, inside this template.

5.1.1 [Link]
 If Function is V and if being invoked from Browser and if the package installation involves
Program Release, an error message will be raised.
 Also, restriction on Opening a new record in Verify mode.

5.1.2 [Link]
 Immediately after [Link], this subroutine sets the enrichments to certain fields
which do not have an associated CHECKFILE.

5.1.3 [Link]
 This subroutine will be invoked when the Function is V.
 [Link] is again invoked inside this subroutine and subsequently,
[Link] is invoked.

5.2 [Link]
 Invoked from [Link] template, to load the Common variables used by
[Link] & [Link].

5.3 [Link]
 $RUN routine for [Link] template, called from CALL.$RUN in [Link]
 Based on the value in the field ACTION, it invokes either [Link] or
[Link].
 While invoking either of them, it also determines which Activity to be carried out by them using
2 common variables called C$[Link] and C$[Link], as
appropriate.

29 Aug 2004
Temenos T24

T24 Non-Core Package & Deployment Tool Reference Guide

5.4 [Link]
 Invoked from [Link], when the field ACTION is set to SAVE.
 There are, by default, 5 steps in the process of saving a [Link] Unit. This routine
is called by [Link] for each step. Each of these steps are defined as
[Link] in I_BCON.COMMON
 The sequence of events will be –
o Save the programs
o Save the [Link] Units
o Refresh the definition of descriptors from [Link], into [Link]
o Consolidate all the [Link] Units
o Build the Index File prefixed with BCON_.
 Every time a [Link] Unit is saved, the Unit, if it already exists in the [Link],
is deleted and recreated by this routine.
 When this routine is invoked with activity as ‘CONSOLIDATE’ and if V$FUNCTION is R, then
it will delete the Saved [Link] unit from the [Link].
 Calls [Link] with Operation set to ‘S’, for each [Link] Unit defined in the
[Link] multi-valued field.

5.5 [Link]
 Invoked from [Link], when the field ACTION is set to
RELEASE/[Link]/[Link]/[Link]
 There are, by default, 7 steps in the process of releasing a [Link] unit. This
routine is called by [Link] for each step, in the case of ACTION=RELEASE
or for just that Step in the case of ACTION = [Link] or [Link] or
[Link].
 Each of these steps are defined as [Link] in I_BCON.COMMON
 The sequence of events will be –
o Create any flat files defined in [Link] field
o Move, Release & Restore [Link] Units defined in the [Link] multi-valued
field
o Release Programs (Compile or Catalog)
o Release Dictionary Items (Idescriptors) and rebuild standard selection (using OFS)
o Authorise [Link] & Attach them to [Link], as per the definition
in [Link], [Link] & [Link] fields
o Authorise other records restored using [Link].
 Calls [Link] for releasing (creating [Link] records) for the [Link]
Units
 Every time a [Link] is released, the Unit, if it already exists in [Link], is deleted
and recreated.
 Calls [Link] with Operation set to ‘R’ for each [Link] Unit defined in the
[Link] multi-valued field.

30 Aug 2004