T24 Archiving

Release: R19 AMR

May 2019

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, for any purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.

© 2019 Temenos Headquarters SA - all rights reserved.

 T24 Archiving

Table of Contents
Introduction 3
Purpose of this Guide 3
Intended Audience 3
Overview 4
Setup 5
Configuring ARCHIVE Application 5
Setting Up ARC.GENERIC.REQUEST 8
Timing Of The Archiving Process 9
Backups 9
Post Archiving Actions 9
Segmentation 10
Reports 12
Accessing The Archived Information 12

2
T24 Archiving

Introduction
Purpose of this Guide
This document provides the details about Archiving historic data and moving them
to an Archive file, that can reside on a separate disk or machine.

Intended Audience
This User Guide is intended for the use of Internal Temenos users and Clients.

3 Introduction
 T24 Archiving

Overview
T24 Archiving reclaims valuable disk space by moving or removing historic data
that is no longer required from the live database. Archiving examines files for
records to be archived, writes the selected records (and related records, if spe-
cified) to a $ARC Archive file (ideally residing on a different disk, or a separate
machine accessible through a network) and then deletes these records from the
Live database. The user can also simply delete the data without Archiving it.

Overview 4
T24 Archiving

Setup
Configuring ARCHIVE Application
The files to be Archived must have an entry in ARCHIVE application. Create a record
in ARCHIVE, for each set of files which must be Archived.
There are four distinct sections in this record.
1. The first set of fields are PURGE.DATE, RETENTION.PERIOD, ARCHIVE.DATA
and $ARC.PATHNAME

l The ARCHIVE.DATA field is used to Archive or Delete the selected

records. Choose 'Y' to Archive and 'N/None' to Delete the record.
l The PURGE.DATE or RETENTION.PERIOD field is usedto specify
the records selection for Archiving. This is based on a date which
can either be specified in PURGE.DATE field (must be the first of
the month and for CATEG.ENTRY field must be before the last fin-
ancial year end) or RETENTION.PERIOD field. Records older than
this date are Archived (or deleted). Purge date is automatically
calculated from retention period at runtime. For example, if
today's date is 23/05/2012 and the retention period of three
months is specified (03M), three months is calculated from the
beginning of the month. Therefore, records dated before
1/2/2012 is Archived (or deleted).
l Specify the destination location of the $ARC Archive files in
$ARC.PATHNAME field. If this field is left null, then the $ARC files
are created in the Archive directory (BNK.arc).
The second set of fields (ARC.FILENAME to MODULUS) are related multi-value
fields, which describe the Archive files to be created.

5 Setup
 T24 Archiving

The ARC.FILENAME field indicates the names of all the $ARC files which are created
based on Type and Modulo specified. If Type and Modulo specification are not
present, then $ARC files inherits the same Type and Modulus; as the corresponding
LIVE files.
The third set (COMPANY.RUN.IN to TIME.ENDED) are related multi-value fields,
which are auto populated by the system after the Contracts are archived. They
maintain a history.

The fourth set comprises the GENERIC.METHOD, MAIN.FILE, FIELD.TO.CHECK,

FILTER.RTN, RELATED.FILES.RTN and ROUTINE fields.

Setup 6
T24 Archiving

The MAIN.FILE field accepts the file name that has to be Archived. For example,
FUNDS.TRANSFER$HIS.

The FIELD.TO.CHECK field indicates the date field in the Contract, which must be
compared with the Purge date for Archiving. If this field is left blank, then the stand-
ard DATE.TIME field is used for comparison. For example, to Archive the history
records of FUNDS.TRANSFER record, use the PROCESSING.DATE value of the Con-
tract.

Note: If the above MAIN.FILE field is multi-valued and populated with

two or more applications, the date field mentioned in FIELD.TO.CHECK
considers the application populated in the first multi-value set.

The FILTER.RTN field is a hook routine to select or ignore a Contract for Archiving.
This field is used as an alternative to FIELD.TO.CHECK field.
The parameters of this routine are:
FILTER.RTN ( ID.CONTRACT, R.CONTRACT, CONTRACTARCHIVE.DATE, SKIP.FLAG, ', ')
l ID.CONTRACT (IN Parameter 1) - Record key of the contract
l R. CONTRACT (IN Parameter 2) – Entire contract record
l CONTRACTARCHIVE.DATE (OUT Parameter 1) – Date against which the purge
date set in the ARCHIVE record should be compared with.
For example, in FUNDS.TRANSFER the user can compare debit value date and
credit value date of the Contract and return a final date as the OUT para-
meter, that is compared with purge date finally for Archival.
l SKIP.FLAG (OUT Parameter 2) – Returns Value ‘1’ as the OUT parameter, to
skip the current Contract from Archiving. Value ‘1’ confirms that the current
Contract need not be Archived. (Logic to ignore the Contract must be avail-
able in the filter routine. So, the current Contract is skipped from being
Archived).
l Two Spare parameters for future expansion.
The RELATED.FILES.RTN field is a hook routine that returns the names of related
files that have to be Archived along with the main Archival record in a dynamic
array.

7 Setup
 T24 Archiving

The parameters of this routine are:

The RELATED.FILES.ROUTINE field has (ID.CONTRACT , R.CONTRACT, RELATED.FILES,
','
l ID.CONTRACT (IN Parameter 1) - Record key of the main Contract that is
ready to be Archived.
l R.CONTRACT (IN Parameter 2) – Entire Contract record.
l RELATED.FILES (OUT Parameter 1) – Information of related files to be
Archived in the format 'File name, File ID, Archival Flag separated by @VM'.
If there are multiple related files, each file information can be delimited by
@FM marker. For example, upon Archiving LOANS.AND.DEPOSITS records, its
balances file records must be Archived. So, pass the balances file name, its ID
and a ‘Y’ to the Archival flag.
l Two Spare parameters for future expansion.

GENERIC.METHOD
a. Specify 'Y' to execute generic Archival process. This allows Archival service
(ARC.GENERIC service) to take care of all selection and purging of records.
For example, FUNDS.TRANSFER, TELLER, STMT.ENTRY.DETAIL and so on; are
Archived using the generic Archival process based on the inputs provided in
MAIN.FILE, FIELD.TO.CHECK or FILTER.ROUTINE field.
b. To indicate 'No/None' when application specific Archival routine specified in
the ROUTINE field must be invoked.

ROUTINE
This field indicates a valid multi-threaded routine that is responsible for Archiving
the set of files specified in the ARCHIVE record. These are application specific
routines and should not be changed unless a site specific program is written. For
example, for FOREX, the routine is ARC.FOREX. This record routine is responsible to
decide on the Archival logic and to do Archiving. Separate ARC.FOREX.LOAD,
ARC.FOREX.SELECT routines must be available for opening and selecting all neces-
sary files for Archiving. However, it is not necessary to create a separate
ARC.FOREX service. It is the responsibility of ARC.GENERIC service to simply invoke
ARC.FOREX.LOAD, ARC.FOREX.SELECT, ARC.FOREX routines internally for Archiving
in the presence of ROUTINE field.

Setting Up ARC.GENERIC.REQUEST
Create a ‘SYSTEM’ record in ARC.GENERIC.REQUEST and specify the ARCHIVE ID for
Archival. Upon verification of this record, ARC.GENERIC service is started in the
background and in turn it reads the ARCHIVE record. Based on the Generic.Method
set-up or the application specific ROUTINE, the records are selected for Archival.
Ensure that TSM is already running.

Setup 8
T24 Archiving

Timing Of The Archiving Process

It is recommended that the Archiving process must be run after the COB, but
before the users are allowed to sign in. However, since Archiving removes the data
that is no longer used, it can be executed even when the system is Live.

Backups
The system in which Archiving must be run is fully backed up to tape.

Note: Archiving is a one-way process. Data cannot be restored after-

wards, except by fully restoring the database back to the point of pre-
archiving.

Back up the area as follows

From UNIX, change to the directory that is being backed up. For example, if the
area being backed up is BNK and the directory structure is /usr/T24/bnk/bnk.run;
then enter
$cd /usr/T24
$find bnk -print -depth | cpio -ovcB > /dev/zzz
Where zzz is the name of your backup device.
From UNIX verify the tape as follows:
$cpio -iBct < /dev/zzz
Where zzz is the name of your tape device.

Post Archiving Actions

Once the Archiving process is complete, the size of all the files involved (both ori-
ginal and $ARC where applicable) must be reviewed to take the new number of
records in the relevant files into account.

9 Setup
 T24 Archiving

Segmentation
Overview
Earlier, statement archiving was multi-threaded at an account level, that is, each
agent archives data specific to an account and if an account has a huge number of
entries to archive, archiving takes a long time to process as the multi-threading is
not at the stmt entry level. It also results in an enormous transaction boundary at
the database level resulting in DB (Database) failures.
To overcome this issue, ‘segmentation’ is introduced in statement archiving, which
is already a proven performance solution for SWIFT statements in Temenos Core
Banking.
Segmentation is the process of multi-threading the job processing by splitting the
entries between available agents.
The statement archiving process consists of the following ARCHIVE records:
1) STATEMENT - To archive records from the following tables
l ACCT.SMT.PRINT
l ACCT.STMT2.PRINT
l STMT.PRINTED
l STMT2.PRINTED
l STMT.ENTRY
l RE.CONSOL.STMT.ENT.KEY
l AC.STMT.HANDOFF$HIS
2) STMT.ENTRY.DETAIL - To archive records from the following tables
l STMT.ENTRY.DETAIL.XREF
l STMT.ENTRY.DETAIL
This statement archiving can be executed in the following two ways:
1) Run STATEMENT.ENTRY.DETAIL & STATEMENT archiving sequentially as two sep-
arate processes.
2) Set ARCHIVE (STATEMENT) > ARC.FILENAME to 'STMT.ENTRY.DETAIL$ARC’ and
run STATEMENT archive process alone. This in turn archives records from all the
above-mentioned tables including STMT.ENTRY.DETAIL.XREF & STMT.ENTRY.DETAIL
without having to run STMT.ENTRY.DETAIL archive separately.
Running both archives together gives better control over data being archived and
helps maintain referential integrity of statement tables. However, the cost of doing
so is the extremely large transaction it spans to archive all statement data relevant
to a particular account

Setup 10
T24 Archiving

This is now broken down into smaller manageable transactions by the use of ‘seg-
mentation’ processing without affecting the data referential integrity the solution
already provides.

Setup
Segmentation solution is initiated only if the following conditions are met:
l ARCHIVE (STATEMENT) > ARC.FILENAME is set to ‘STMT.ENTRY.DETAIL$ARC’
– So all statement related tables are archived just by running the STATEMENT
archive alone instead of running it along with STMT.ENTRY.DETAIL
l Segmentation value is set for STATEMENT archive in the field named
SEGMENT.VALUE in the format named SEG*<NNNNNNN> where NNNNNNN is
the number of entries to be grouped per agent.

Processing
Once the ARCHIVE record is setup as explained above, trigger the archiving process
by verifying the ARC.GENERIC.REQUEST according to the standard war.
If the SEGMENT.VALUE is set as SEG*5000, then each agent archives entries in
groups of 5000 entries each so the same account’s data gets archived in parallel
thereby resulting in a better performance.

11 Setup
 T24 Archiving

Reports
Information about the total number of records selected for processing and the total
number of records archived/deleted is stored in the respective ARCHIVE record for
reference.

Note: 497 Contracts were selected for Archival. 279 were deleted from
FUNDS.TRANSFER$HIS and archived in FUNDS.TRANSFER$ARCfile.

Accessing The Archived Information

The archived information is written to the files with the suffix $ARC. The $ARC files
uses the same layout as the files from which they are created. For example, the lay-
out of RE.CONSOL.SPEC.ENTRY$ARC is the same as RE.CONSOL.SPEC.ENTRY.

Creating Enquiries To View Archived Information

The archived files can be viewed using the T24 ENQUIRY utility, by creating an
enquiry to view the Archived file. This enquiry can be a copy of an enquiry on the
original file that was Archived, setting the FILE.NAME to the name of the Archived
file.
For example, an enquiry to view the CATEG.ENTRY$ARC file is based on the
CATEG.ENTRY enquiry, changing the FILE.NAME to CATEG.ENTRY$ARC.

Creating Enquiry on FUNDS.TRANSFER$ARC

Reports 12
T24 Archiving

13 Reports