Scribd
Upload
104 views11 pages

Upgrade

This document outlines the phases of upgrading the T24 system. It discusses (1) converting local code to standardized programming practices and addressing changes in higher releases, (2) converting the desktop to a UXP browser, (3) performing a technical upgrade, (4) designing a new studio, and (5) updating documentation. The local code conversion process focuses on programming standards, obsolete changes, and changes required for the TAFJ technical architecture framework. Examples of changes include replacing APIs, softcoding fields, updating tax codes, and removing unsupported features. Care must be taken to ensure compatibility with the new TAFJ framework.

Uploaded by

Mahesh Chandra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
104 views11 pages

Upgrade

This document outlines the phases of upgrading the T24 system. It discusses (1) converting local code to standardized programming practices and addressing changes in higher releases, (2) converting the desktop to a UXP browser, (3) performing a technical upgrade, (4) designing a new studio, and (5) updating documentation. The local code conversion process focuses on programming standards, obsolete changes, and changes required for the TAFJ technical architecture framework. Examples of changes include replacing APIs, softcoding fields, updating tax codes, and removing unsupported features. Care must be taken to ensure compatibility with the new TAFJ framework.

Uploaded by

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

T24 Upgrade

Introduction

• Phase
1. Local Code Conversion.
2. Desktop to UXP Browser Conversion.

3. Technical Upgrade.
4. Design Studio.
5. Documentation.
Local Code Conversion
• This process has been classified in to 3 stages.

1. Programming Standardization.

2. Obsolete changes in Higher Releases.


3. TAFJ Changes.
Programming Standardization
• It helps us to provide Better performance, Better
understandability , Easy Maintenance & Support.
• API changes like

OPEN  OPF
READ  F.READ
WRITE  F.WRITE

DBR  F.READ
HARDCODED FILEDS  SOFTCODED
JOURNAL.UPDATE
Obsolete changes in Higher Releases
• All Local routines that uses Obsolete files should be converted to
read suitable files in higher releases to make the code work as same
as in Lower release.
• Its recommended to use EB.READ.HVT instead of F.READ to fetch
the details from below tables
 EB.CONTRACT.BALANCES
 ACCT.ACTIVITY
 ACCT.STMT.PRINT
 DATE.EXPOSURE
Obsolete changes in Higher Releases
• Increase in Tax Code Length

The Tax application @ID which is currently 2 digits has been extended to 4
digits to allow banks to configure upto 9999 records for TAX application.
• FT Replacement

Removal of PP.COMPANY replacement to this is PP.COMPANY.PROPERTIES.


• !HUSHIT()

API !HUSHIT() has been changed to HUSHIT() to support the TAFJ.


• I_IC.COB.COMMON have been removed and two new I_ files
I_IC.INTEREST.CAP.FILES.COMMON &
I_IC.ACCOUNT.INTEREST.FILES.COMMON are introduced with these removed
variables.
TAFJ Changes
• CALLC is not supported in TAFJ. Hence it is replaced by CALLJ.

• ‘IF’ condition with multiple choice of values in the same line will not work.
Hence, 'OR' should be added in between the multiple values.
• OPEN with ON ERROR – ELSE
• TAFJ don’t support any variable name prefix with @ in REMOVE
statements.
• ‘//’ is used for commenting any lines in a routine, it will throw error in TAFJ
because it is not supported , * should be used for commenting in TAFJ.
• TAFJ will not support Pre increment and decrement operators.
TAFJ Changes
• $INCLUDE to $INSERT

• There is no direct replacement for EVAL, coding has to be changed to


make it compatible with TAFJ.
• In local routines, CALL OPF and F.READ for DATES application can be
avoided as we have R.DATES common variable defined in I_COMMON.
• GET.LIST is not supported in TAFJ alternately we need to open and read
from the file &SAVEDLISTS&.
• Auto New content routine will not trigger using the reverse or deletion
should be achieved using Check Rec routine.
TAFJ Non-Supported Descriptor
• Descriptors are I-type expression or Joins defined on STANDARD.SELECTION
record for any application.
• Descriptors are not physical field of an application but computed field
whose values are manipulated dynamically whenever used by other
applications such as ENQUIRY, VERSION, USER, USER.SMS.GROUP etc..
• TAFJ supports only certain types of Descriptor in STANDARD.SELECTION .
• We have the automated utility used to perform SS clean-up and ENQUIRY
conversion in possible areas to reduce the manual effort.
• Usage of I-Desc fields in SELECT commands will not support in TAFJ.
Java source name
• Java doesn’t support all the characters BASIC allows.
 The ‘.’ are replace by the ’-’

 The ‘%’ are replace by the ’_p_’


 The ‘$’ are replace by the ’_d_’

 The ‘ ’ (space) are replace by the ’_s_’

 The ‘(’ are replace by the ’_l_’


 The ‘)’ are replace by the ’_r_’

 The ‘!’ are ignored.


Thank You

You might also like