TAFJ (Temenos Application Framework Java) is a Pick BASIC runtime and compiler,

written in 100% java.

It allows compiling and running Pick BASIC programs.
TAFJ has been written specifically for T24 needs, and all tests and proof of
concepts have been done using T24. TAFJ also manage the connectivity on JDBC
compliant databases like jBASE J4, Oracle, MS SQL.

DataMigration:

Data migration is the process of converting data from one format to another.
It is typically performed to launch new or upgraded systems, services,
infrastructure, functions or features.
Before you begin the data migration process, identify what data you’re migrating,
what format it’s currently in, where it lives, and what format it should be in
post-migration.

Steps to Include in your Data Migration Plan

Identify the data format, location, and sensitivity.

Planning for the size and scope of the project.
Backup all data.
Assess staff and migration tool.
Execution of the data migration plan.
Testing of final system.
Follow-up and maintenance of data migration plan.

On the consumer end, you can think of the SWIFT network a bit like travelling from
one airport to another. It’s not always possible to take a direct flight. Which
means you may need to travel from one city to another via several connecting
flights. SWIFT works essentially the same way. Your money will travel from one
country to another, but to do that there are often intermediary/correspondent banks
involved.

The SWIFT network doesn’t actually transfer funds, but instead it sends payment
orders between institutions’ accounts, using SWIFT codes. It was SWIFT that
standardised IBAN (International Bank Account Numbers) and BIC (Bank Identifier
Codes) formats. SWIFT owns and administers the BIC system, meaning that it can
quickly identify a bank and send a payment there securely.

If the information that needs to be presented in an enquiry does not exist in a

single file, then the enquiry can me made to take information from routines. To do
this first let us understand the way in which enquiry subsystem works.

The enquiry subsystem first builds up a list of ids, then picks up each id and
constructs a record and then displays the records. If the information that needs to
be presented does not exist in a file then subroutines can be written to do the
task. Basically 2 routines needs to be written ? one which will construct a list of
ids and one which will accept the id and build the record based on the id.

If a field is specified in an enquiry the type and position of the field is

retrieved from the standard selection record of the file mentioned in the field
FILE.NAME.

Standard selection is an application that basically stores the dictionary for a

file. You could have data fields and logical fields (i.e. the information is a
calculated value for e.g. from a subroutine). However generally when you try to
input a standard selection record it will validate if a FILE.CONTROL record exists
for the file. The only exception to this is if the SS record id begins with ?
NOFILE?. So for our above requirement we will need to create an SS record with ID
starting with ?NOFILE?. In the record for the ID field make it a R type field and
attach a routine that would build a dynamic array of Ids that need to be displayed
in the enquiry.

I_ENQUIRY.COMMON, a common file that is used in enquiries ? defines a variable

called O.DATA which contains the ID of the record that is currently going to be
displayed. Another common variable called R.RECORD (a dynamic array) is used by the
enquiry subsystem to display the record. So you need to write a routine that would
use the id defined in O.DATA and populate R.RECORD.