Release Notes

Release R08

T24 Release Notes

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
Temenos Page 1 of 1 Holdings NV.

Copyright 2002-2006 TEMENOS Holdings NV. All rights reserved

Release Notes
Table of Contents

PRE-RELEASE INFORMATION .................................................................................................... 4

Important Information ................................................................................................................. 4
Minimum / Suggested system component requirements ........................................................... 4
Database Requirements ............................................................................................................. 5
Relational Data Base Management System ........................................................................... 5
Disk Space Requirements .......................................................................................................... 5
Data Changes ............................................................................................................................. 6
INSTALLATION OF THE SOFTWARE .......................................................................................... 6
Upgrading T24’s jBASE .............................................................................................................. 6
Copying new programs into place .............................................................................................. 7
Important..................................................................................................................................... 7
Pre-release ................................................................................................................................. 7
T24 release ................................................................................................................................. 8
CONVERSION ROUTINES ........................................................................................................... 8
Overview ..................................................................................................................................... 8
Conversion Routines .................................................................................................................. 8
PL Close out Changes................................................................................................................ 9
Summary ................................................................................................................................. 9
Reporting .................................................................................................................................... 9
POST CONVERSION ACTIONS ................................................................................................. 10
Authorise Standard Selections ................................................................................................. 10
Authorising / Modifying new and changed records .................................................................. 10
Record Authorisation ............................................................................................................ 10
Batch Record Authorisation .................................................................................................. 10
Batch records HELD ............................................................................................................. 10
Batch record LIVE ................................................................................................................. 10
Sequence of authorisation .................................................................................................... 11
REPGEN recompile .............................................................................................................. 11
Recompile local code ............................................................................................................ 11
Application/Module Specific ......................................................................................................... 12
Accounting ............................................................................................................................ 12
Browser ................................................................................................................................. 12
Desktop ................................................................................................................................. 12
Interest and Charges ............................................................................................................ 13
Mortgage ............................................................................................................................... 13
Non Deliverable Forwards .................................................................................................... 13
Reporting .............................................................................................................................. 14

Temenos Page 2 of 2
Release Notes
Securities .............................................................................................................................. 14
Syndicated Loans ................................................................................................................. 14
Installing a new product ............................................................................................................... 15
ARC-IB...................................................................................................................................... 15
SPECIAL ROUTINES .................................................................................................................. 15

Temenos Page 3 of 3
Release Notes

PRE-RELEASE INFORMATION

Important Information
This section outlines actions that must be made BEFORE installing a T24Server release. If you
are upgrading by two or more releases, then read and understand all the release information
details for each release before starting the installation.
The T24 Technical Highlights documentation should also be referenced. This will highlight any
changes of a technical nature that may impact local development.

Minimum / Suggested system component requirements

The following table shows the minimum components and release numbers which are designed to
run with T24.

T24 Component Release Platform

Browser / ARC IB R08.000 I.E. 7 and Firefox 2
Toolbox R08.000 Windows 2000, XP and VISTA
Desktop 1.5.032 Windows 2000, XP and VISTA
Temenos Application 5.0.9 Operating systems (Minimums)
Framework (jBASE)
Windows Server 2003
RedHat Linux AS5
AIX 5.2
Solaris 10
HPUX 11.11
Oracle Direct Connect Drivers: 3.2.3.1 Minimum and recommended release 10.2.0.3.
DB2 Direct Connect Drivers: 3.2.0 Minimum version 9.1, recommended 9.5, or 9.1 for
zSeries
MSSQL Direct Drivers: 3.2.1 Minimum and recommended SQL Server 2005 SP2
Connect (or latest service pack)
Temenos Connector 1.5.2
Conman 3.1

Temenos Page 4 of 4
Release Notes

Database Requirements
The database to be upgraded must be at the stage just before an end of day is set to run. Ensure
all message queues have been cleared and phantoms and services are stopped. The system
must be in a fully recoverable state. No one should be signed on except the person upgrading.
Once the upgrade process finished is a complete backup or checkpoint should be taken to ensure
recoverability.

Relational Data Base Management System

When using an RDBMS (Oracle, DB2 or MS SQL) as the database for T24 in conjunction with the
Direct Connect Database Drivers, it must be configured to use the UTF8 character set i.e. it needs
to be ‘internationalised’.

The following environment settings need to be configured:

export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
export JBASE_CODEPAGE=UTF8
export JBASE_I18N=1

The RDBMS Database character set must also be configured to ALU32UTF8 at creation /
installation time.

The T24 utility CONVERT.SYSTEM.UTF8.JBASE needs to be used to convert the initial T24
database at the time of installation. This is required to convert certain files than contain binary data
e.g. encrypted passwords in F.USERS.

The full procedures for this process can be can be referenced in the jBASE Internationalization
user guide.

Disk Space Requirements

When you upgrade a T24 database, the size of the database will increase, especially if you are
installing new products. Please ensure you have sufficient disk space available.

Temenos Page 5 of 5
Release Notes

Data Changes

A few applications may still contain field numbers e.g. USER and others may be stored in
USER.EXTERNAL.FIELD. Please review these applications before beginning the upgrade to
determine if any corrections to field numbers are required.
Do not make changes until the conversions have been run.

It is important that there are no unauthorised STANDARD.SELECTION records before you take
the release and you do not authorise any released STANDARD.SELECTION records before
you run the conversions.

INSTALLATION OF THE SOFTWARE

Instructions on the transfer of the release from distribution medium and the actual upgrade
process are included in the System Administration section of the User Guide.

Upgrading T24’s jBASE

If you are not already running jBASE 5.0.9 you should install it.
Ensure no one else is logged in to the T24 account.
Now, to upgrade your T24 to your new jBASE release -

1. Change the “export JBCRELEASEDIR=” statement in the .profile file to point to the 5.0.9
release.
For example
export JBCRELEASEDIR=/usr/jbcxxxx   (where your jBASE 5.0.9 resides)
2. Check that TEMP.RELEASE refers to the correct directory (as below)
3. Run EB.COPY.GLOBUS.JBASE.
4. Log out and log in again
5. Run UpdateMD
6. Log out

You are now ready to follow any pre-release procedures described below and then sign on to T24
to run GLOBUS.RELEASE.

Upgrading jBASE from 4.1 to 5.0.9 requires that you recompile all routines. If you have local
routines concerned with sign-on then they will need to be recompiled immediately.

Temenos Page 6 of 6
Release Notes

Copying new programs into place

Ensure no one else is logged in to the T24 account.

In the jBase environment the following commands must be run at the jshell prompt (jsh ~ -->), after
the TEMP.RELEASE has been installed into the location specified in systemfile>TEMP.RELEASE,
before logging into T24 to run GLOBUS.RELEASE.

1. Check that TEMP.RELEASE refers to the correct directory

jsh ~ --> CT systemfile TEMP.RELEASE
(Assuming “systemfile” has the value of $JEDIFILENAME_SYSTEM)

2.Then copy the new versions of the T24 programs into place
jsh ~ --> EB.COPY.GLOBUS.JBASE

Note that EB.COPY.GLOBUS.JBASE, the routine that you use to put the new programs in place
completely replaces the contents of globusbin and globuslib. If this is where you keep any local
routines you will have to recompile them.
Also, if you use any of the T24 file layouts or common layouts in your local routines you will need
to recompile them. This is best done after GLOBUS.RELEASE when the source code for any file
or common layouts will be in place. If you have local routines concerned with sign-on then they will
need to be recompiled immediately.

Important
The installation of a new product must not be done at the same time as a system upgrade.
The preferred procedure would be to complete the upgrade first and only then change the SPF
and COMPANY records to include the new product.

Pre-release

Ensure no one else is logged in to the T24 account.

Run the program T24.PRE.RELEASE from jBASE after you have run the normal procedure of
EB.COPY.GLOBUS.JBASE.

This program will create missing files and writes details to a COMO File.
Log out of your session

Temenos Page 7 of 7
Release Notes

T24 release

Ensure no one else is logged in to the T24 account.

Start a new session with the Classic interface and sign on to T24. Invoke the application
GLOBUS.RELEASE. You will be asked to confirm the releases to be installed. When the release
is completed you will be advised to log out.

CONVERSION ROUTINES

Overview
This section outlines the conversion and other related routines to be run for this release. Read
through the whole chapter thoroughly before starting the conversion process: you may be required
to get information or data prior to starting the conversions.

Data, except where this document specifically states, must not be input, amended, or authorised
until all the conversion routines have been successfully completed.

Conversion Routines

Follow the instructions in the System Administration Guide. All CONVERSION.PGMS records
must be authorised first. The conversion routines should be run using the routine
RUN.CONVERSION.PGMS.
Do not authorise any STANDARD.SELECTION records before running.

Programs have been changed and files have been converted to work on the field name. This
renders the list of conversions which appeared at this point in previous releases no longer useful
as R05 will have converted field numbers to field names. If you have local program developments
then the recompilations will automatically cope with the record layout as field locations are
updated in the code inserts.
Note that the Asset Type is now available on the ACCOUNT record and is kept up to date on
line.

Temenos Page 8 of 8
Release Notes

PL Close out Changes

Summary

A conversion is provided which will update BATCH records, and preset (as far as possible) the
new PL.CLOSE.PARAMETER records for each lead company, records will be placed on hold if
there is any discrepancy between the previously configured Batch run date for close out and the
COMPANY FINANCIAL.YEAR.END.
The FINANCIAL.YEAR.END field in COMPANY is now no-input (extern field) and is updated by
setting the date/frequency in the PL.CLOSE.PARAMETER file.
Accounting is produced during a ‘virtual’ year-end cob; this allows it to have its own journal,
reports and can keep the accounting updates segregated from the normal cob accounting.

After conversions completed:

Update the authorised (or IHLD) PL.CLOSE.PARAMETER record(s); there will be one for each
lead company. Set the year end date, which now controls the field on COMPANY and specify
any reports that will be produced to be checked when the system runs the close out process. Use
the CLOSE.HLT.PRCSS field to halt the system at the point where the
CONSOLIDATE.PRFT.LOSS records can be seen before they are rest for the next financial
year – and the reports produced can be viewed.
Check the ACCOUNT.CLASS records PLCLOSE, IACLOSE & LGCLOSE are present and default
internal ACCOUNT records are set in each lead company. If they are not present the system will
warn the user in the days leading up to the year end and will not allow the year end process cob to
be started without them.
The PL.CLOSE.PARAMETER file can also be set to group the PL entries into groups based on
the consol key parameters.
Existing BATCH records for the book level companies will be removed as the process is
performed at Lead company level.

Reporting
The following conversion must be run:
CONV.DELETE.OB.BATCHES.R08
This conversion removes the BATCH entries EB.ACCT.TRIAL.BAL and EB.PRINT.TRIAL.BAL.
Three new BATCH jobs have been introduced in this release.
TXN.JOURNAL.SORT: A multi threaded job at report stage that selects the data required for
printing.
TXN.JOURNAL.PRINT: A single threaded job at online stage that prints the report.
TXN.JOURNAL.CLEAR: A multi threaded job at online stage, executed after TXN.JOURNAL.PRINT,
which clears old TXN.JOURNAL keys.

Temenos Page 9 of 9
Release Notes

POST CONVERSION ACTIONS

Authorise Standard Selections

Authorise all STANDARD.SELECTION records for the release.

Authorising / Modifying new and changed records

Record Authorisation

If you have fully complied with the actions detailed in the pre-release information and release
notes, you can now authorise all the unauthorised records in all companies. Check the impact of
changes as you authorise each record to prevent any overwriting of local modifications.

Batch Record Authorisation

All BATCH records must be reviewed. You may have local differences from the released records.

Batch records HELD

Some BATCH records may be in HLD status. These records contain information in the data fields
that has been modified. You must review these records to ensure that your local data
specifications are not being overwritten.

Batch record LIVE

After initial installation, when running the next COB, the BATCH record TXN.JOURNAL.SORT must
have the value held in FREQUENCY set to “Daily”, subsequent to this the record needs to be
amended to set the FREQUENCY to “Ad-hoc” to reduce the processing overhead.
Should users wish to continue to utilise the existing TRANS.JOURNAL2 report they may do so by
reinstating the report in the BATCH EB.PRINT, this will, however, have an impact in the
performance of COB processing

Temenos Page 10 of 10
Release Notes

Sequence of authorisation

Authorise these records in the following applications first because of later dependencies:

STANDARD.SELECTION
ENQUIRY (any % records)
EB.PRODUCT
EB.SYSTEM.ID
SYSTEM.RECORD
VERSION
DE.MESSAGE
TRANSACTION
STMT.NARR.FORMAT
RE.STAT.REPORT.HEAD
RE.STAT.RANGE
EB.MESSAGE.CLASS
EB.ACTIVITY
EB.ADVICES
BROWSER.TOOLS
TSA.WORKLOAD.PROFILE

Some TSA.SERVICE records may be HLD as they need a user name entered.

REPGEN recompile

Use REPGEN.SOURCE to recompile all REPGENs or use RUN.REPGENS at the jBASE prompt
as described in the user guide.

Recompile local code

Recompile local code to pick up any changes in INCLUDED code.

Temenos Page 11 of 11
Release Notes

Application/Module Specific

Accounting

Before EB.FINANCIAL.SYSTEM record T24 can be authorised a CATEGORY code and

TRANSACTION code need to be entered on the record.

Browser

With this release T24 now supports Internet Explorer v7.0 and Firefox v2.0.
A minimum requirement is Browser release 2.0 Build 070511.

For EB.SELECTION.FAVOURITES, EB.ENQUIRY.GRAPH and ENQUIRY (drill down

expand/collapse) functionality the December 2007 browser release or higher must be configured.

Customisation - Layering
Routines can be added or removed on the EB.ATTRIBUTES SYSTEM record, as required and
can be used singularly or in any combination. Interaction between them is a decision for the local
developer. Each routine will need the appropriate sub-routine to have been compiled and have a
record on EB.API application.

Desktop

Pre- Requisites for Installing Desktop on Windows Vista

Windows Vista includes a new security model known as User Account Control (UAC), which
represents a major shift from the traditional Windows user privilege model and affects nearly every
Windows user. UAC is designed to improve the least user (i.e. standard user) experience.
Under UAC, all Windows Vista users, including those with administrative rights, interact with their
PCs as standard users most of the time. The Windows standard user account continues to have
no administrative privileges, cannot access protected directories or registry entries.
When you attempt to perform a task that requires administrative privileges, such as installing
software or changing the status of the Windows firewall, Windows Vista explicitly prompts you to
supply permission or credentials before temporarily elevating you to the administrative level to
complete that single task.

Since Desktop utilises the System Registry during launching & execution it is necessary to Disable
Repetitive User Account Control Check for the Windows User.

Steps:
Launch the Windows Control Panel. Click on the ‘User Accounts’ application. Ensure that the ‘Use
User Account Control (UAC) to help protect your computer’ is UNCHECKED. Click OK.

Temenos Page 12 of 12
Release Notes

NOTE: If UAC is NOT disabled then Desktop will report a ‘Permission Denied’ or ‘Unexpected
Error’ when it is launched.

Interest and Charges

In this release the files SA.PERMIUM.INTEREST.WRK and SA.PRM.INTEREST.WRK have

become redundant and have been made obsolete. The conversion CONV.FILE.CONTROL.200708
deletes the FILE.CONTROL records for these files, but does not delete the files. The user may
wish to delete the file manually to keep their system tidy, though this is not necessary.

Mortgage

After upgrading, it should be ensured that a Close of Business is run without any new transactions
being entered.
During this first Close of Business new EB.CONTRACT.BALANCES records per contract and
RE.CONSOL.CONTRACT will be created. After this initial run new records will be created after
contract authorisation.

Non Deliverable Forwards

The ND module has now been brought under the FX fold. This has been achieved by reclassifying
the programs and data items (hitherto under ND) under the FX product name. The application
ND.DEAL will continue to be the template for inputting transactions, entries will still be raised
under the ND System ID, Transaction Journal will have a head for ND and GL can be set up under
system ID ND.
In other words, all the features previously available under the ND module including the set-up are
retained and the changes cover only the release mechanism where the buyer of the FX module
also gets the ND related routines and data items without needing a separate license code for the
latter.
For current users with ND already installed the SPF and COMPANY records must not be
amended to reflect this change.
The user guide for ND has now been merged with user guide for FOREX.

Temenos Page 13 of 13
Release Notes

Reporting

After upgrading, it should be ensured that a Close of Business is run without any new transactions
being entered.
During this first Close of Business new EB.CONTRACT.BALANCES records per existing Asset
and Liability contracts will be created. After this initial run new records will be created after
contract authorisation.

Securities

The application LIQ.TRADE has now been made obsolete; all reference to this application needs
to be removed from the COMPANY record.
The close of business job SC.EOD.UPD.SEC.MASTER should no longer be used due to
significant performance issues. It is planned to remove this job in R09. As such the job should be
made ad-hoc. The job is not required from a core perspective. Any local developments that use
the field SEC.POSN.EXISTS in SECURITY.MASTER should be reviewed and amended. There
is a core DAS select dasSecurityPositionSecurityNonZero which can be used to return a list of
non-zero security positions indicating that a security has been used in T24.

Syndicated Loans

After upgrading, it should be ensured that a Close of Business is run without any new transactions
being entered.
During this first Close of Business new EB.CONTRACT.BALANCES records per contract and
RE.CONSOL.CONTRACT will be created. After this initial run new records will be created after
contract authorisation.

Temenos Page 14 of 14
Release Notes

Installing a new product

ARC-IB
• Make sure that the upgraded release is installed.
• Obtain the licence codes for the AA, AI and AP modules.
• Install AA and then the AI and AP modules individually - see the upgrades guide for
details of installing a new product

Sequence for authorizing ARC-IB records.

EB.API
EB.ERROR
OVERRIDE
EB.COMPARISON.TYPE
AA.PROPERTY.CLASS
AA.PRODUCT.LINE
AA.ACTIVITY.CLASS
AA.PROPERTY
AA.PRODUCT.GROUP
EB.FORMAT.ENTRY
EB.LOOKUP
AA.MAPPING
EB.MAPPING.SOURCE
AA.PERIODIC.ATTRIBUTE.CLASS

SPECIAL ROUTINES
There are no special routines for this release.

Temenos Page 15 of 15