Scribd
Upload
1K views16 pages

TAFJ Code Conversion

Local code developed for the TAFC environment needs to be reviewed and refactored to work in the TAFJ environment. The document highlights areas of code that need changes such as removing CALLC, changing usages of F1 and F2 to actual field names, removing unsupported functions like DELETE with LOCKED, and replacing '//' concatenation with string concatenation functions. Refactoring is required to make the code compatible with the TAFJ platform.

Uploaded by

Zuhair Abdullah Fadhel
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
1K views16 pages

TAFJ Code Conversion

Local code developed for the TAFC environment needs to be reviewed and refactored to work in the TAFJ environment. The document highlights areas of code that need changes such as removing CALLC, changing usages of F1 and F2 to actual field names, removing unsupported functions like DELETE with LOCKED, and replacing '//' concatenation with string concatenation functions. Refactoring is required to make the code compatible with the TAFJ platform.

Uploaded by

Zuhair Abdullah Fadhel
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/ 16

TAFC-TAFJ Code Conversion

Adapted from Temenos Documentation


TAFJ Code Migration – Code Conversion
 Where source code for locally developed functions is available, there is
need to review code developed for TAFC environment to fit into TAFJ
environment.
 The following slides highlight such code that must be refactored and
changed.
Code Migration – INPUTERR
Code Migration – OPENSEQ/READSEQ
Code Migration – CHARX/SEQX
Code Migration – CALL C & CALLJ

 NO CALLC
Code Migration – EVAL

This does not work in TAFJ:


SELECT FBNK.ACCOUNT WITH DATE.TIME LIKE 140929... SAVING EVAL “@ID:’,’:
SHORT.TITLE:’,’: ARRANGEMENT.ID”
Code Migration – DELETE with LOCKED
Code Migration – Unsupported JQL Query
Code Migration – IF condition with multiple choices
Code Migration – ITYPE not supported
Code Migration – I-Descriptor Field in SELECT command
Code Migration – Using F1, F2 as condition in SELECT
 This does not work in TAFJ:

Examples:

1) EXECUTE "SELECT VOC WITH F1 LIKE 'F...' AND WITH F2 NE '' BY F2 SAVING F2"

2) "SELECT F.BATCH.STATUS WITH F1 LIKE '...processing...' "

 T24 core API never uses F1, F2 etc to select field definitions. Every select needs to have a
corresponding field name.

 The local code should be changed by replacing the F1, F2,… with field names in T24.

 F1 or F2 works only where VOC exists (Jbase or TAFC).


Code Migration – PRECISE DECIMAL
Code Migration – ‘//’ operator Concatenated as String in TAFJ
Code Migration – EXECUTE Keyword

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy