Professional Documents
Culture Documents
TAFJ-Supported Commands
TAFJ-Supported Commands
Co m m a n d s
(TAFC-TAFJ M i g r a t i o n )
R20
TAFJ Suppo r t e d Com m a n d s
(TAFC- TAFJ Migr a tio n)
Amendment History:
Revisio
Date Amended Name Description
n
1 18th October 2019 TAFJ Team Initial Version
2 25th March 2020 Siranjeevi M R20 AMR Review
Page 2
TAFJ Suppo r t e d Com m a n d s
(TAFC- TAFJ Migr a tio n)
Contents
Copyright................................................................................................................................................ 4
Errata and Comments............................................................................................................................ 4
Introduction............................................................................................................................................. 4
EXECUTE key word............................................................................................................................... 4
In JBC, TAFJ - Supported Commands.................................................................................. 4
In JBC - TAFJ - Unsupported Commands............................................................................. 6
Page 3
TAFJ Suppo r t e d Com m a n d s
(TAFC- TAFJ Migr a tio n)
Copyri g h t
Copyright © Temenos Headquarters SA 2009-2020.
All rights reserved.
This document contains proprietary information that is protected by copyright. No part of this document may
be reproduced, transmitted, or made available directly or indirectly to a third party without the express
written agreement of TEMENOS UK Limited. Receipt of this material directly TEMENOS UK Limited
constitutes its express permission to copy. Permission to use or copy this document expressly excludes
modifying it for any purpose, or using it to create a derivative therefrom.
Intro d u c t i o n
TAFJ is not TAFC and in many cases does not accept some of the commands that TAFC
does. When a customer migrates from TAFC to TAFJ, customers need to know the
supported commands. This document aims at providing this information.
What goes between the quotes of an EXECUTE statement is translated into a SQL
statement in most cases. Therefore, one SHOULD NOT put OS commands in an EXECUTE
clause (although some are supported)
EXECUTE “ ”
Page 4
TAFJ Suppo r t e d Com m a n d s
(TAFC- TAFJ Migr a tio n)
EXECUTE “PHANTOM”
EXECUTE “BASIC”
EXECUTE “CATALOG” “ In effect does nothing in TAFJ as once a file is compiled, the
.class file is cataloged
EXECUTE “CLEARSELECT”
EXECUTE “SSELECT MYFILE etc” Where MYFILE is a valid file as a RECID in the
TAFJ_VOC table. If MYFILE is a UD, no WITH clause is allowed, ie only EXECUTE
“SSELECT MYFILE”.
Page 5
TAFJ Suppo r t e d Com m a n d s
(TAFC- TAFJ Migr a tio n)
EXECUTE “CREATE-FILE MYFILE Type=UD”This will create a UD file where the key
temn.tafj.runtime.directory.current points in the tafj.properties file
EXECUTE “SELECT MYFILE WITH etc” where MYFILE is a UD file (WE SHOULD NOT
BE USING UD FILES!!!)
Page 6