Troubleshooting

T24Updater tool - TAFC

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.

© 2016 Temenos Headquarters SA - all rights reserved.

Troubleshooting - T24Updater tool (V3.0)

Table of Contents

Document History .................................................................................................................................... 4

Introduction.............................................................................................................................................. 6
Errors faced while installing updates ................................................................................................... 6
1. Permission denied ................................................................................................................ 6
i. In UNIX: ................................................................................................................................. 6
ii. In NT: .................................................................................................................................... 7
2. No zip files found in updates directory .................................................................................. 7
3. Cannot open <<update name>> ........................................................................................... 8
4. Updates failed for <update name>........................................................................................ 9
5. updater: updater: is a directory ........................................................................................... 10
6. Unable to open & file ........................................................................................................... 10
7. <<update name>> is unable to be resolved to what is on the machine ............................. 11
8. <<update name>> version <<XX>> is the same or lower than the installed ...................... 12
9. The system cannot find the path specified. ........................................................................ 13
10. Dependency error ............................................................................................................... 13
11. updater is not an identifier ................................................................................................... 14
12. Nothing found on Client module.......................................................................................... 14
13. Non-unique module ............................................................................................................. 15
14. RXX_ALL:EB_BrowserClient:Version:X is null. Check configuration file. .......................... 16
15. Update failed for <<update pack name>> .......................................................................... 20
i. SUBROUTINE_CALL_FAIL: ............................................................................................... 20
ii. TOO MANY CHARACTERS ............................................................................................... 21
iii. Update failed: Failed to get a return code from child process ............................................ 24
16. <<ComponentName>> branch <<BranchInfo>> does not match <<product>> branch
<<BranchInfo>> ............................................................................................................................. 25
17. <<ComponentName>> branch <<BranchInfo>> does not match <<product>> branch
<<BranchInfo without T24 release>> ............................................................................................. 27
18. Updater tool hangs without any progress. .......................................................................... 27
19. Updates not Successful ...................................................................................................... 28
20. Nothing found on client for module ..................................................................................... 30
21. BuildCatalog ........................................................................................................................ 31
Compatible Versions of Updater Tool: .................................................................................................. 33
Precautionary Steps to avoid frequent errors: ...................................................................................... 33
Java Errors faced during updates installation ....................................................................................... 38
1. Null pointer exception during updates installation .............................................................. 38
2. UnmarshallException during updates installation ............................................................... 39
3. XML is invalid premature end of file .................................................................................... 39
4. XML is invalid null ............................................................................................................... 41

Core Infra Temenos PACS 2

Troubleshooting - T24Updater tool (V3.0)

5. Xml is invalid Content is not allowed in trailing section. ..................................................... 45

6. Update failed: java: not found ............................................................................................. 47
7. Content is not allowed in prolog. ......................................................................................... 48
i. If the problem occurs for a particular update ...................................................................... 48
ii. If the problem occurs for T24Version .................................................................................. 49
8. Cannot run program - CreateProcess error=2 .................................................................... 50
9. Update failed: Can't load log handler "java.util.logging.FileHandler" .................................. 51
10. <<T24_HOME>>/updater/bin/updater[21]:<<JAVA_HOME>>/bin/java: not found ............ 52
Troubleshooting BNK/T24.UPDATES service ...................................................................................... 53
1. Failed Updates list .............................................................................................................. 53
2. WRONG ALPHANUMERIC CHAR and TOO MANY CHARACTERS error message ....... 55
3. Unable to open file TEMP.RELEASE/&SAVEDLISTS& ..................................................... 56
Conclusion:............................................................................................................................................ 58

Core Infra Temenos PACS 3

Troubleshooting - T24Updater tool (V3.0)

Document History

Author Version Date

Charles John 1 05-May-10

Charles John 1.1 21-Jun-10

Charles John 1.2 24-Jun-10

Charles John 1.3 11-Oct-10

Charles John 1.4 24-Nov-10

Laavanya R 1.5 02-Aug-11

Laavanya R 1.6 24-Aug-11

Laavanya R 1.7 07-Sep-11

Charles John 1.8 08-Sep-11

Charles John 1.9 10-Feb-11

Charles John 2 14-Aug-12

R Raghapriya 2.1 05-Aug-13

R Raghapriya 2.2 05-Dec-13

R Raghapriya 2.3 09-Dec-13

R Raghapriya 2.4 02-Feb-13

Lokaranjane 2.5 03-Feb-13

R Raghapriya 2.6 06-Feb-13

Charles John 2.7 22-Jul-14

Maria Priyanka D 2.8 26-Apr-16

Maria Priyanka D 2.9 18-Nov-16

Celine Seba Preeti L 3.0 25-Feb-17

Comments:

Core Infra Temenos PACS 4

Troubleshooting - T24Updater tool (V3.0)

Core Infra Temenos PACS 5

Troubleshooting - T24Updater tool (V3.0)

Introduction
The purpose of this document is to troubleshoot the errors faced while installing updates using
T24Updater tool in a TAFC environment.

Errors faced while installing updates

There are certain commonly faced errors for which the solutions are mentioned in this document.

1. Permission denied
i. In UNIX:

Error Message

Figure 1 – Error Message

This error message occurs in UNIX environment.

To resolve this

Execute updater from sh prompt instead of jsh prompt.

Figure 2 – Resolve

Error Message

Figure 3 – Error Message

To resolve this

Include $HOME/updater/bin path in PATH variable of .profile / remote.cmd

Error Message

jsh -->sh updater

Usage: updater <dir-path> <parent-pid> [working-dir callback args...] $

Figure 4 – Error Message

This error message occurs when the JAVA_HOME path is not pointing to jdk's bin.

Core Infra Temenos PACS 6

Troubleshooting - T24Updater tool (V3.0)

To resolve this

Set the JAVA_HOME path pointing to jdk\bin's path and run the updater again. E.g.: C:\Program
Files\Java\jdk1.6.0

ii. In NT:

Error Message

Figure 5 – Error Message

To resolve this

Execute updater as updater.bat as shown below

Figure 6 – Resolve

Error message

Figure 7 – Error Message

To resolve this

Include $HOME/updater/bin path in PATH variable of .profile / remote.cmd

2. No zip files found in updates directory

Error Message

Figure 8 – Error Message

Core Infra Temenos PACS 7

Troubleshooting - T24Updater tool (V3.0)

This error message occurs when the downloaded .zip file is not present inside
$HOME/updater/updates directory

To resolve this

Place the downloaded zip file inside $HOME/updater/updates and then execute updater from sh
prompt.

3. Cannot open <<update name>>

Error Message

Figure 9 – Error Message

This error message occurs in any of the below scenario:

a) gtar path is not mentioned in PATH variable of .profile.

To resolve this
Please include gtar path to PATH variable of .profile

set PATH=%PATH%:<<gtar path>>/bin

Figure 10 – Resolve

check for the working of gtar using the below command

jsh-->gtar

Figure 11 – gtar check

Core Infra Temenos PACS 8

Troubleshooting - T24Updater tool (V3.0)

b) TEMP.RELEASE path is not set properly

To resolve this

jsh R15 ~ -->JED SYSTEM TEMP.RELEASE

001 D
002 D:\Temenos\R15TAFC\bnk\bnk.run

Figure 12 – TEMP.RELEASE

The output of pwd should be the second line in the TEMP.RELEASE record.

c) The file R09_EB_Enquiry_1_AIX_5 might be corrupted.

To resolve this
Please download R09_EB_Enquiry_1_AIX_5 again from the website.

Note: gtar is used by T24Updater tool in UNIX and it is replaced by tar for NT

4. Updates failed for <update name>

Error Message

R12_EB_Browser_25_HPUX_IA64.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Update failed for R12_EB_Browser_25_HPUX_IA64.tar : Message: Update
R12_EB_Browser_25, Updates failed for R12_EB_Browser_25_HPUX_IA64

Figure 13– Error Message

This error message occurs while removing the t24lib and t24bin directories. While replacing t24lib and
t24bin directories, the existing directories will be removed and then new t24lib and t24bin will be copied.
The reported error message will occur if the existing t24lib and t24bin directories are not removed
properly.

To resolve this
Follow the procedure given under the section “TOO MANY CHARACTERS”

Core Infra Temenos PACS 9

Troubleshooting - T24Updater tool (V3.0)

5. updater: updater: is a directory

Error Message

Figure 14 – Error Message

To resolve this
This problem occurs when the variables JAVA_HOME and T24_HOME is not set in both UNIX and
WINDOWS environment. Also the path of $HOME/updater/bin should be appended to PATH variable
(of remote.cmd or .profile).

Note: The JAVA_HOME should point to the standalone java and not the one inside TAFC directory
(Example: usr/java1.6 and not $TAFC_HOME/java)

6. Unable to open & file

Error Message

R09_AC_Overridecodes_2_LINUX_ELF_AS5.tar
R09_AC_Errorcodes_1_LINUX_ELF_AS5.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Update failed for R09_EB_LocalReferences_1_LINUX_ELF_AS5.tar :
Message: Update R09_EB_LocalReferences_1, Unable to open & file

Output Summary:
1 files processed.
Updates not successful.
Errors/Warnings:
Exiting Updater...

Figure 15 – Error Message

To resolve this

a) Need to check for the presence of TEMP.RELEASE record and temp.release directory

Core Infra Temenos PACS 10

Troubleshooting - T24Updater tool (V3.0)

jsh ~ -->CT SYSTEM TEMP.RELEASE

TEMP.RELEASE
001 D
002 /glohd/HDareas/INfareas/intstj4/mbdemo/mbdemo.run

Figure 16.a – Resolve

b. Need to check for the presence of temp.release directory

jsh ~ -->ls
total 392
drwxrwxrwx 2 intstj4 hdin 256 Apr 22 02:23 &SAVEDLISTS&
drwxrwxrwx 2 intstj4 hdin 256 Apr 22 02:23 &SAVEDLISTS&]D
drwxrwxrwx 6 intstj4 hdin 256 Apr 22 02:49 .
drwxr-xr-x 197 intstj4 hdin 49152 Aug 03 09:26 ..
-rwxrwxrwx 1 intstj4 hdin 4 Apr 22 02:22 .jbase_header
drwxrwxrwx 2 intstj4 hdin 256 Apr 22 02:23 VOC
drwxrwxrwx 2 intstj4 hdin 256 Apr 22 02:23 VOC]D
jsh ~ -->ls
&SAVEDLISTS& &SAVEDLISTS&]D VOC VOC]D
jsh -->pwd
/glohd/HDareas/INfareas/intstj4/mbdemo/mbdemo.run

Figure 16.b – Resolve

7. <<update name>> is unable to be resolved to what is on the machine

Error Message

Output Summary:
0 files processed.
Updates not successful.
Errors/Warnings:
EB_Browser version 3 is unable to be resolved to what is on the
machine.
Exiting Updater...

Figure 17 – Error Message

Core Infra Temenos PACS 11

Troubleshooting - T24Updater tool (V3.0)

To resolve this
Set the field T24.SERVER to YES in EB_Browser of EB.COMPONENT application and authorise it as
shown below and run updater tool.

Figure 18 – Resolve

8. <<update name>> version <<XX>> is the same or lower than the

installed

Error Message

Output Summary:
0 files processed.
Updates not successful.
Errors/Warnings:
EB_BrowserVersion version 11 is the same or lower than the installed
version 11
Exiting Updater...

Figure 19 – Error Message

Error message says that R09_EB_BrowserVersion_11 is already installed in the environment and the
same have been updated in your SPF record.

Core Infra Temenos PACS 12

Troubleshooting - T24Updater tool (V3.0)

To resolve this
Since re-installation of same update version is not possible, we should re-generate SysDef.xml file
and download updates.

9. The system cannot find the path specified.

Error Message:

Figure 20 – Error Message

Reason:
JAVA_HOME is not set correctly.

To resolve this:
Set JAVA_HOME to a valid jdk installation path.

Figure 21 – Resolve

10. Dependency error

Error Message

Figure 22 – Error Message

To resolve this

Core Infra Temenos PACS 13

Troubleshooting - T24Updater tool (V3.0)

Since dependency check is made by the updater tool based on the update.xml file present inside the
tar file, the tool will not install the update if dependency check fails. Hence we should re-generate
SysDef.xml file and download updates.

This problem could occur when the .tar pack present inside the .zip file is removed or renamed.

11. updater is not an identifier

Error Message

jsh daubol ~ -->sh updater

updater[14]: =/t24_uatas3/bnk/bnk.run/../..: is not an identifier

Figure 23 – Error Message

To resolve this
Set the below variable in the .profile (or remote.cmd), and execute the updater command again

export T24_HOME=$HOME

Figure 24 – Resolve

12. Nothing found on Client module

This error occurs in the scenario when T24 updates are installed and its corresponding tag in
updater.xml file is commented

Figure 25 – updater.xml

Core Infra Temenos PACS 14

Troubleshooting - T24Updater tool (V3.0)

Error Message:

Figure 26 – Error Message

Solution:
Uncomment the corresponding tag in updater.xml file. In this case, as T24 updates are installed,
uncomment the below lines

Figure 27 – updater.xml

Note: similarly when Browser / ARC IB, TAFC, TAG updates are installed, their corresponding
tag should be un-commented in updater.xml file.

13. Non-unique module

Error Message:

This error occurs, when different (or equal) version of same component present inside the zip file. This
is more likely to occur when there are one or more zip file is placed inside the $HOME/updater/updates
directory.

Core Infra Temenos PACS 15

Troubleshooting - T24Updater tool (V3.0)

jsh test ˜ -->sh

sh-3.2$ updater

T24 Updater V2.1

Input Summary:
T24Updates-2012-8-6-057.zip
R10_EB_SystemTables_35_LINUX_ELF_AS5.tar
R10_SCO_SecurityMasterMaintenance_5_LINUX_ELF_AS5.tar
Non-unique module: R10_LINUX_ELF_AS5:EB_SystemTables:Version:34 found in
a zip file. Remove one of the zips from the updates dir and process one
at a time

Output Summary:
0 files processed.
Updates not successful.
Errors/Warnings:
Failed to move file
/usr/globus/bnk/bnk.run/updater/updates/T24Updates-2012-8-6-057.zip
Exiting Updater...
sh-3.2$

Figure 28 – Error Message

To resolve this
To resolve the problem, it should be made sure that there are no different versions of same component
present inside zip file(s) of $HOME/updater/updates directory.

14. RXX_ALL:EB_BrowserClient:Version:X is null. Check configuration file.

Error Message:

When this error is raised, we need to check whether the configuration setup for the installation of the
problematic update component is correct.

Core Infra Temenos PACS 16

Troubleshooting - T24Updater tool (V3.0)

Input Summary:
T24Updates-2011-12-22-942.zip
R09_DE_Outward_17_HPUX_IA64.tar
R09_SE_Test_16_HPUX_IA64.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Update successful for R09_DE_Outward_17_HPUX_IA64.tar : Message:
Update R09_DE_Outward_17, Sucessfully Installed
Update failed: Executable for module
R09_ALL:EB_BrowserClient:Version:6 is null. Check configuration
file.

Output Summary:
1 files processed.
Updates not successful.
Exiting Updater...

Figure 29 – Error Message

In this case, since the failed update is EB_BrowserClient, we need to check whether the browser link
specified in the updater.xml file (present in side $HOME/updater/config) is a valid browser link and the
tag itself is uncommented as shown below:

Figure 30 – updater.xml

Even if the browser link provided in the <url></url> tag is correct and this problem persists, kindly test
the working of browser link from the area where updates is installed by using the below java code.

import java.net.*;
import java.io.*;
import java.io.*;

Core Infra Temenos PACS 17

Troubleshooting - T24Updater tool (V3.0)

import java.net.*;

public class TestBrowserLink {

public boolean visitWebPage(String UrlToVisit) {

boolean urlVisited = false;

try {
URL url = new URL(UrlToVisit);
URLConnection urlConnection = url.openConnection();
BufferedReader htmlPage = new BufferedReader(new
InputStreamReader(url.openStream()));

String line = "";

while((line = htmlPage.readLine()) != null) {
//do something with the html line
System.out.println(line);
}
htmlPage.close();
urlConnection = null;
urlVisited = true;
} catch(Exception e) {
urlVisited = false;
}
return urlVisited;
}
/**
* @param args the command line arguments
*/
public static void main(String[] args) {
TestBrowserLink urlVisit = new TestBrowserLink();
String url = null;
String commstart = " <!-- *********************** ";
String commend = " *********************** -->";
if (args[0] == null) {
url = "http://www.google.com";
} else {
url = args[0];
System.out.println(commstart + "Visiting "+ url + commend);
}

Core Infra Temenos PACS 18

Troubleshooting - T24Updater tool (V3.0)

if (urlVisit.visitWebPage(url)) {
System.out.println(commstart + url + " visited" + commend);
} else {
System.out.println(commstart + url + " Website not found" + commend);
}
}
}

Compiling and execution of the java code (in Windows environment)

Figure 31 – Output

Here we can see that similar xml output produced in browser using the same browser link is returned
in this java code. If this output is not returned in the java code, then we need to check the LAN
connection between the area where updates is installed with the area (IP address) where the webserver
is installed.

Figure 32 – XML Output

Core Infra Temenos PACS 19

Troubleshooting - T24Updater tool (V3.0)

15. Update failed for <<update pack name>>

When this error message is thrown while installing updates, refer the corresponding &COMO& record
for the exact error message. It could be either SUBROUTINE_CALL_FAIL error message or TOO
MANY CHARACTERS.

i. SUBROUTINE_CALL_FAIL:

Error Message

R09_CHQ_PaymentStop_1_LINUX_ELF_AS5.tar
R09_CHQ_Issue_1_LINUX_ELF_AS5.tar
R09_AI_ModelBank_1_LINUX_ELF_AS5.tar
R09_ACM_AccountClosure_1_LINUX_ELF_AS5.tar
R09_AC_Overridecodes_2_LINUX_ELF_AS5.tar
R09_AC_Errorcodes_1_LINUX_ELF_AS5.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Update failed for R09_EB_Logging_2_LINUX_ELF_AS5.tar
Output Summary:
1 files processed.
Updates not successful.

Figure 33 – Error Message

On checking the corresponding &COMO& record

029 Copying new t24lib eb_logging

030 [12:29:43]cp -r R09_EB_Logging_2_LINUX_ELF_AS5/t24lib/eb_logging
t24lib
031 Copied new t24lib.
032
033 No Records selected
034
035 ** Error [ SUBROUTINE_CALL_FAIL ] **
036 Unable to perform CALL to subroutine TEC.START.TIMER , Line 82 ,
Source F.READ
037 Press C to continue or Q to quit
038

Figure 34 – Updater COMO

Core Infra Temenos PACS 20

Troubleshooting - T24Updater tool (V3.0)

This error message occurs because the t24lib and t24bin used by T24Updater tool is replaced by itself
during the process of installation.

To resolve this

Point JBASE_PATH and JBCOBJECTLIST in .profile (or remote.cmd) to a different location other than
$HOME/t24bin and $HOME/t24lib as shown below:

Figure 35 – JBCOBJECTLIST variable

Figure 36 – JBASE_PATH variable

ii. TOO MANY CHARACTERS

Error Message

Figure 37 – Error Message

To resolve this:
This error is fixed in latest version of the updates EB_Upgrade and EB_SystemTables

Procedure to be followed:
1. Create folder in bnk.run as run1

Figure 38.a – Resolution step 1

Core Infra Temenos PACS 21

Troubleshooting - T24Updater tool (V3.0)

2. Now take a copy of the t24lib and t24bin from bnk.run and place them in run1

Figure 38.b – Resolution step 2

3. Edit your .profile/remote.cmd and ensure that JBASE_PATH and JBCOBJECTLIST is pointed
to the run1 directory

Figure 33.c – Resolution step 3

4. Ensure that VOC and SAVEDLISTS& are created as UD type directory in run1 (to resolve the
problem #1 “Unable to open & file“)

Figure 38.d – Resolution step 4

5. Setup the TEMP.RELEASE voc as

Figure 38.e – Resolution step 5

Core Infra Temenos PACS 22

Troubleshooting - T24Updater tool (V3.0)

Now, follow the below steps.

a) Take unzip the downloaded T24Updates<<YYYY-MM-DD-X-nn>>.zip and take the tar file -
R09_EB_Upgrade_X_OS.tar

Figure 38.f – Step 1

b) Untar the file: R09_EB_Upgrade_X_OS.tar. After untar, it produces the following:

t24lib
t24bin
update.xml
R09_EB_Upgrade_X

Figure 38.g – Step 2

c) Copy the bin objects (From the R09_EB_Upgrade_X_OS>t24bin>eb_upgrade) to

bnk.run/run1/t24bin.

d) Copy the lib (From the R09_EB_Upgrade_X_OS>t24lib>eb_upgrade) to bnk.run/run1/t24lib.

Core Infra Temenos PACS 23

Troubleshooting - T24Updater tool (V3.0)

e) Now run updater tool.

iii. Update failed: Failed to get a return code from child process

Error Screenshot:

Figure 39 – Error Message

&COMO& record

[10;1HRELEASE NUMBER IS R09_SC_ModelBank_4

[12;1HSELECT LIST NAME IS REL.R09_SC_ModelBank_4.DATA
[23;9H[23;9H[526] List '0' is inactive.
Transferring F.BATCH>LTD/SC.SYS.END.OF.DAY
[24;2H
** FATAL ERROR IN (CDT) **
EB.RTN.DATE-132

No Records selected

Figure 40 – &COMO&

Solution:

The problem occurs when the updater tool transfers SC.SYS.END.OF.DAY record of BATCH
application. This problem is fixed in R09_EB_Updates_1. Hence, install R09_EB_Updates_1 before
installing R09_SC_ModelBank_4.

After successful installation of R09_EB_Updates_1, please copy t24lib and t24bin of

R09_EB_Updates_1 to respective folder inside run1 directory, this is because when executing
T24Updater tool, the variable JBCOBJECTLIST points to run1/t24lib, hence the fixed libraries should
be copied to run1 directory.

Core Infra Temenos PACS 24

Troubleshooting - T24Updater tool (V3.0)

jsh r9test ~ -->jshow -c T24.INSTALL.UPDATE

Subroutine: D:\Localhost\r9test\bnk\bnk.run\run1\t24lib\eb_updates\lib0.dll
jBC T24.INSTALL.UPDATE version 09.0 Mon Apr 12 11:01:03 2010
jBC T24.INSTALL.UPDATE source file R09_EB_Updates_1.SOURCE
jsh r9test ~ -->jshow -c T24Version
Executable: D:\Localhost\r9test\bnk\bnk.run\run1\t24bin\eb_updates\T24Version.dll
jBC main() version 09.0 Mon Apr 12 11:01:11 2010
jBC main() source file R09_EB
_Updates_1.SOURCE

Figure 41 – Jshow output

16. <<ComponentName>> branch <<BranchInfo>> does not match

<<product>> branch <<BranchInfo>>

Error message

Input Summary:
T24Updates-2011-7-25-635.zip
R10_FC_libTAFCjbase_6_HPUX_IA64.tar
R10_FC_libTAFCjcf_4_HPUX_IA64.tar
R10_FC_libTAFCjql_4_HPUX_IA64.tar
R10_FC_libTAFCmonitor_1_HPUX_IA64.tar
R10_FC_libTAFCfrmwrk_6_HPUX_IA64.tar
R10_FC_libTAFCutil_5_HPUX_IA64.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Output Summary:
0 files processed.
Updates not successful.
Errors/Warnings:
FC_libTAFCjcf branch R10_HPUX_IA64 does not match FC branch
PB201011_HPUX_IA64
Exiting Updater...

Figure 42 – Error Message

While trying to install non compatible version of TAFC updates, system will result in “does not match
XX branch” error.

Core Infra Temenos PACS 25

Troubleshooting - T24Updater tool (V3.0)

To resolve this

This problem will happen when “branch” in versionxml_jbase output and the “major” in jdiag output
and name of the update should match.

In the below case, the branch is PB201011_HPUX_IA64

<ivy-module version="1.0">
<info organisation="TEMENOS" branch="PB201011_HPUX_IA64" module="FC" />

<dependencies>
<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCcommon" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjcf" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjremote" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCmonitor" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjbase" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjql" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCfrmwrk" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjee" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCutil" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCtj" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCjrfs" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCxml" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCdrvrs" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCsql" rev="0" />

<dependency org="TEMENOS" branch="PB201011_HPUX_IA64" name="FC_libTAFCSQLSYS" rev="0" />

</dependencies>

</ivy-module>

Figure 43 – versionxml_jbase outuput

jdiag output shows the major is 201011.0.

JEDIFILEPATH : '/t24/cbalive/bnk/bnk.run'

JEDIFILENAME_MD : '/t24/cbalive/bnk/bnk.run/VOC'
JEDIFILENAME_SYSTEM : '/t24/cbalive/bnk/bnk.run/src/SYSTEM'

RELEASE Information : Major 201011.0 , Minor 0.0 , Patch (Change 91463)

Spooler dir (JBCSPOOLERDIR) : '/t24/cbalive/tafc/R10/jspooler'
JBCEMULATE : 'prime'

WARNING: Cannot access Executable path '/t24/cbalive/bnk/bnk.run/globusbin', error 2

Figure 44 – jDiag output

This is not matched with the name of the update (R10_FC_libTAFCutil_5_HPUX_IA64.tar)

Hence need to make sure that non-compatible TAFC updates are not installed in the environment and
the updates are downloaded from TCSP website using the latest SysDef.xml file.

Core Infra Temenos PACS 26

Troubleshooting - T24Updater tool (V3.0)

17. <<ComponentName>> branch <<BranchInfo>> does not match

<<product>> branch <<BranchInfo without T24 release>>

Error message:

Errors/Warnings:
ACM_AccountClosure branch R13_AIX_6 does not match T24 branch
_AIX_6
Exiting

Figure 45– Error Message

To resolve this:
This problem will occur when JAVA_HOME variable is not set in .profile/remote.cmd and it is only set
just before running updater tool.

In order to resolve the problem, set JAVA_HOME variable in .profile/remote.cmd

Also make sure that updater tool is executed from bnk.run directory as shown below.

In UNIX:

jsh-->./updater/bin/updater

In Windows:

jsh-->updater\bin\updater.bat

18. Updater tool hangs without any progress.

Error message

Core Infra Temenos PACS 27

Troubleshooting - T24Updater tool (V3.0)

Figure 46 – Updater hangs

<service name="T24" pathType="EXEC" updateType="AUTO">

<path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>

<installpath>[T24_HOME]</installpath>
<installprogram>[T24_HOME]/t24bin/eb_updates/T24.UPDATE.INSTALLER</installprogram>

</service>

Figure 47 – updater.xml

To resolve this

When the updater tool hangs, need to check the presence of T24.UPDATE.INSTALLER binary file
and specify it in updater.xml file.

Figure 48 – jshow output

<service name="T24" pathType="EXEC" updateType="AUTO">

<path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>
<installpath>[T24_HOME]</installpath>

<installprogram>[T24_HOME]/t24bin/eb_updatesrun/T24.UPDATE.INSTALLER</installprogram>
</service>

Figure 49 – Resolve

19. Updates not Successful

Error Message

Input Summary:
T24Updates-2014-1-13-921.zip
R10_EB_BrowserClient_182_ALL.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator

Output Summary:
0 files processed.

Figure 50 – Error Message

Core Infra Temenos PACS 28

Troubleshooting - T24Updater tool (V3.0)

To resolve this
Please perform the below steps:

1) Make sure that the browser link provided in updater.xml file is a valid browser link and the tags are
uncommented in .xml file

Example:

<service name="BROWSER" pathType="URL" updateType="MANUAL">

<url>http://localhost:8080/BrowserWebR09.60/servlet/BrowserServlet?command=version</url>
</service>

Figure 51.1 – Resolve step 1

2) Execute updater tool as shown below

jsh-->updater.bat -report

This should get the output similar to as shown below:

jsh R09 ~ -->updater.bat -report

T24 Updater

Loading Upgrader configuration from:

D:\Localhost\R09.000\R09\bnk\bnk.run\updater\config\updater.xml
Update Dir: D:\Localhost\R09.000\R09\bnk\bnk.run/updater/updates
Config Path: D:\Localhost\R09.000\R09\bnk\bnk.run\updater\config
$JBCRELEASEDIR: C:\TAFC\R09
$TAFJ_HOME: null
$T24_HOME: D:\Localhost\R09.000\R09\bnk\bnk.run
<ivy-module version="1.0"> <info organisation="TEMENOS"
branch="R09_ALL" module="EB_BrowserClient"
revision="60"/> <dependencies/></ivy-module>

T24 Updater V1.6

Input Summary:
No zip files found in updates directory
jsh R09 ~ -->

Figure 51.2 – Resolve step 2

NOTE: For UNIX, execute updater tool as shown below:

Core Infra Temenos PACS 29

Troubleshooting - T24Updater tool (V3.0)

jsh live ~ -->sh

sh-3.2$ updater -report

Figure 51.3 – updater execution

In the above sample output, you could notice that xml tag is fetched from browser url and displayed:

<ivy-module version="1.0"> <info organisation="TEMENOS"

branch="R09_ALL" module="EB_BrowserClient"
revision="60"/> <dependencies/></ivy-module>

This will make sure that the browser link is active and system is ready to install EB_BrowserClient
update.

If you could get the above output, please place the .zip file containing EB_BrowserClient update and
re-run updater tool.

NOTE: The above process will ONLY unzip the downloaded .zip file and place .tar file containing
EB_BrowserClient update in $HOME/updater/setup_files directory, later which the
BrowserClient need to be deployed manually. Hence we recommend you to manually unzip &
untar the downloaded .zip file and extract the BrowserClient.war file and deploy it manually in
webserver

20. Nothing found on client for module

Error Message

R09_TRE_GroupRateFixing_3_WIN64.tar
R09_TK_Foundation_1_WIN64.tar
R09_TT_ModelBank_4_WIN64.tar
R09_TT_Passbook_5_WIN64.tar
Nothing found on client for module: R09_WIN64:EB_Updates:Version:5

OutputSummary:
0 files processed.

Figure 52 – Error Message

To resolve this

Core Infra Temenos PACS 30

Troubleshooting - T24Updater tool (V3.0)

The reported problem occurs when the tags present in updater.xml are commented. In order to solve
this problem, while installing updates, based on the tar file present in the downloaded zip, the tags
should be uncommented in updater.xml.

For example, if T24 updates are installed, the corresponding T24 tag should be uncommented in
updater.xml file. Similarly, if TAFC related updates are being installed, then TAFC related tag should
be uncommented.

21. BuildCatalog

This utility is used to create a "master" xref file for the t24lib / t24bin directory. This significantly reduce
the time to start up a T24 program as it avoids scanning all the individual component directories
(Environment Admin should then unset JBASE_JBCOBJECTLIST_DIR to prevent this)

BuildCatalog program scan the t24lib / t24bin directory and for each component directory, it will build
up the subroutine xref table. It then creates a single file (t24SubDef.el/.def) that contains all the current
subroutines in t24lib / t24bin, with a single pre-built HASH table that TAFC will memory map.

Its supports sub-directories created by CATALOG (special .el/.def format, with many .so/.dll), and
jcompile (the .el/.def file format is a list of subroutines in the single so/dll). It is available from R11_SP1
and above releases.

The syntax to run BuildCatalog is,

jsh->BuildCatalog <<library directory>>

Figure 53 – Error Message

When BuildCatalog is executed the variable “JBASE_JBCOBJECTLIST_DIR“ in .profile is commented

in order to stop TAFC from scanning all component subdirectories. It will load the lib.def of all the
directories (present inside t24lib / t24bin) in a single file t24SubDef.def. Hence, after installing the
updates, the jshow of the routines will not point to the installed updates.

Error Screenshot:

Core Infra Temenos PACS 31

Troubleshooting - T24Updater tool (V3.0)

Figure 54 – Error Message

Figure 55 – jshow before installation of updates

Figure 56 – Installation of Updates

Core Infra Temenos PACS 32

Troubleshooting - T24Updater tool (V3.0) The jshow still points to the old
lib even after installing the
updates

Figure 57 – jshow after installation of updates

To resolve this

In order to resolve the problem, run BuildCatalog once again by which the routines point to the new
libraries (i.e., latest installed updates)

Figure 58 – Resolve

Compatible Versions of Updater Tool:

T24 Release T24 Updater Tool Version

R09 T24 Updater 1.6

R10 and above releases T24 Updater 2.7 and above

Precautionary Steps to avoid frequent errors:

When installing updates, it is always recommended to follow the below procedure:

1. Create run1 directory inside bnk.run

Core Infra Temenos PACS 33

Troubleshooting - T24Updater tool (V3.0)

Figure 59 – Step 1

2. Copy t24lib and t24bin from bnk.run to to $HOME/run1 directory

Figure 60 – Step 2

3. Copy R09_EB_Updates_1_AIX_5.tar and R09_EB_Upgrade_6_AIX_5.tar to local

directory

Figure 61 – Step 3

4. Extract R09_EB_Updates_1_AIX_5.tar

Core Infra Temenos PACS 34

Troubleshooting - T24Updater tool (V3.0)

Figure 62 – Step 4

5. Extract R09_EB_Upgrade_6_AIX_5.tar

Figure 63 – Step 5

6. Delete eb_upgrade and eb_updates directory from run1/t24lib and run1/t24bin

Core Infra Temenos PACS 35

Troubleshooting - T24Updater tool (V3.0)

Figure 64 – Step 6

7. Copy t24lib and t24bin of R09_EB_Updates_1_AIX_5 and R09_EB_Upgrade_6_AIX_5

to run1

Figure 65 – Step 7

8. Modify JBASE_PATH and JBCOBJECTLIST variable in .profile to point

$HOME/run1/t24bin and $HOME/run1/t24lib (or execute the same from jsh prompt)

Figure 66 – Step 8

9. Set TEMP.RELEASE record in SYSTEM to bnk.run directory (where VOC and

&SAVEDLISTS& exist with full permission as UD type directory)

Figure 67 – Step 9
10. Place downloaded zip file inside $HOME/updater/updates directory

Figure 68 – Step 10

Core Infra Temenos PACS 36

Troubleshooting - T24Updater tool (V3.0)

11. Uncomment (only) the below tags in updater.xml file (present inside
$HOME/updater/config directory, as we are going to install only T24 released
updates)

Figure 69 – Step 11

12. Execute updater from sh prompt

. Figure 70 – Step 12

From the above screenshot it is shown that on following the above procedure, all (207) updates have
successfully installed.

After successful installation of updates, run1 directory can be deleted from bnk.run

Note 1:

Core Infra Temenos PACS 37

Troubleshooting - T24Updater tool (V3.0)

If R09_EB_Updates_X and R09_EB_Upgrade_X (where X is the version of component installed), then

the point #3 to #7 can be skipped.

Note 2:
From R10 and above releases, follow the above given steps for the EB_UpdatesRun

Java Errors faced during updates installation

1. Null pointer exception during updates installation

R09_ST_CustomerMaintenance_4_SUN_X86.tar

R09_ST_RateParameters_4_SUN_X86.tar

java.lang.NullPointerException

at java.io.FileInputStream.<init>(FileInputStream.java:103)

at com.temenos.upgrader.Upgrader.processDir(Upgrader.java:1150)

at com.temenos.upgrader.Upgrader.loadUpdateXML(Upgrader.java:1025)

at com.temenos.upgrader.Upgrader.doIt(Upgrader.java:299)
at com.temenos.upgrader.Upgrader.main(Upgrader.java:157)

Figure 71 – Error Message

Solution:

This problem would occur if a tar file in the pack does not contain update.xml file. The java logging
should be enabled and the updater should be executed.

Ensure the below modifications are done in the logging.properties file which is found in
$JAVA_HOME/jre/lib to enable the java logging in the environment

handlers= java.util.logging.ConsoleHandler
.level= FINE
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter =
java.util.logging.SimpleFormatter

Figure 72 – logging.properties

After making the above setup, start a new jshell session to enable the changes

On executing the updater with the java logging enabled, the execution would throw NULL POINTER
exception when installing a problematic update. The corresponding problematic update should be
recompiled and given to the client.

Core Infra Temenos PACS 38

Troubleshooting - T24Updater tool (V3.0)

2. UnmarshallException during updates installation

SEVERE: Caught UnmarshalExceptionunexpected element (uri:"", local:"update"). Expected elements are

<{http://www.temenos.com/update/jaxb}update>
Error in: /T24A/bnk/bnk.run/updater/updates/tmp/R09_FC_libTAFCjbase_3_HPUX_IA64.tar. XML being written
to log file.
javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"update"). Expected elements are
<{http://www.temenos.com/update/jaxb}update>
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)

Figure 73 – Error Message

Solution:

The update.xml file of the corresponding update (in this case: R09_FC_libTAFCjbase_3_HPUX_
IA64.tar) is improper. The problematic update should be recompiled and given to the client.

3. XML is invalid premature end of file

installing class fr.jayasoft.ivy.url.IvyAuthenticator

Apr 4, 2010 8:03:51 PM com.temenos.versionutil.SystemDescription validateXML
SEVERE: Xml is invalid Premature end of file.
Warning: [[T24_HOME]/t24bin/eb_updates/T24Version] is not a valid xml
description of a system null

Figure 74 – Error Message

Core Infra Temenos PACS 39

Troubleshooting - T24Updater tool (V3.0)

Code to test the problem:

import java.io.*;

public class JavaRunCommand {

public static void main(String args[]) {

String s = null;

// To read the contents of LIBPATH

String Variable = System.getenv("LIBPATH");
System.out.println("Output of 'echo $LIBPATH' is : ");
System.out.println(Variable);

try {
Process p = Runtime.getRuntime().exec("/glotam1/Bankareas/cib-
test/bnk/bnk.run/t24bin/eb_updates/T24Version");

// To read the contents of "stdout" Standard Output terminal

BufferedReader stdInput = new BufferedReader(new InputStreamReader(p.getInputStream()));

// To read the contents of "stderr" Standard error terminal

BufferedReader stdError = new BufferedReader(new InputStreamReader(p.getErrorStream()));

// read the output from the command

System.out.println("Here is the standard output of the command:\n");
while ((s = stdInput.readLine()) != null) {
System.out.println(s);
}

// read any errors from the attempted command

System.out.println("Here is the standard error of the command (if any):\n");
while ((s = stdError.readLine()) != null) {
System.out.println(s);
}

System.exit(0);
}
catch (IOException e) {
System.out.println("Exception Happened - here's what I know: ");
e.printStackTrace();
System.exit(-1);
}

Figure 75 – Code

Core Infra Temenos PACS 40

 Troubleshooting - T24Updater tool (V3.0)

Note: highlighted line in the java code should be modified to a valid T24Version path.

Now compile the java program and execute it as shown below:

Figure 68 – Code

LIBPATH within java program

Problem is here, usr/lib is LIBPATH outside java program

prepended before LIBPATH.

Version of java is 1.6 SR3

Figure 76 – Code output

Solution:

This is bug in java 1.6. This is fixed in java version 1.6 SR6 (and above)

http://www.ibm.com/developerworks/java/jdk/aix/j664/Java6_64.fixes.html

153743 IZ55981 620700127 600 13/08/2009 N/A /USR/LIB IS PREPENDED TO THE LIBPATH

4. XML is invalid null

com.temenos.versionutil.SystemDescription validateXML
SEVERE: Xml is invalid null
Warning: [[T24_HOME]/t24bin/eb_updatesrun/T24Version] is not a valid xml
description of a system
null

Figure 77 – Error Message

Core Infra Temenos PACS 41

Troubleshooting - T24Updater tool (V3.0)

Code to test the problem:

import java.io.*;

public class JavaRunCommand {

public static void main(String args[]) {

String s = null;

// To read the contents of LIBPATH

String Variable = System.getenv("LIBPATH");
System.out.println("Output of 'echo $LIBPATH' is : ");
System.out.println(Variable);

try {
Process p = Runtime.getRuntime().exec("/glotam1/Bankareas/cib-
test/bnk/bnk.run/t24bin/eb_updates/T24Version");

// To read the contents of "stdout" Standard Output terminal

BufferedReader stdInput = new BufferedReader(new InputStreamReader(p.getInputStream()));

// To read the contents of "stderr" Standard error terminal

BufferedReader stdError = new BufferedReader(new InputStreamReader(p.getErrorStream()));

// read the output from the command

System.out.println("Here is the standard output of the command:\n");
while ((s = stdInput.readLine()) != null) {
System.out.println(s);
}

// read any errors from the attempted command

System.out.println("Here is the standard error of the command (if any):\n");
while ((s = stdError.readLine()) != null) {
System.out.println(s);
}

System.exit(0);
}
catch (IOException e) {
System.out.println("Exception Happened - here's what I know: ");
e.printStackTrace();
System.exit(-1);
}

Figure 78 – Code

Core Infra Temenos PACS 42

Troubleshooting - T24Updater tool (V3.0)

Note: highlighted line in the java code should be modified to a valid T24Version path.

Now compile the java program and execute it as shown below:

Output of the above code:

jsh ~ -->java JavaRunCommand

Figure 79 – Java Run

Output of 'echo $LD_LIBRARY_PATH' is:

/usr/jdk/instances/jdk1.6.0/jre/lib/sparc/server:/usr/jdk/instances/jdk1.6.0/jre/lib/sparc:/usr/jdk/i
nstances/jdk1.6.0/jre/../lib/sparc:/glosoft/TAFC_R13_GA/lib:/glotam1/Bankareas/smbdev1/bnk/b
nk.run/R13lib:/glosoft/TAFC_R13_GA/java/jre/lib:/glosoft/TAFC_R13_GA/jdk/jre/lib/platform:/op
t/solarisstudio12.3:/usr/lib:/glosoft/oracle/oracle11gR2/app/product/11.2.0/lib

Here is the standard error of the command (if any):

ld.so.1: T24Version: fatal: libstlport.so.1: open failed: No such file or directory

Execute the below commands, in order to find the actual path of libstlport.so.1

To find the path of “jsh”

jsh~ -->which jsh

/glosoft/TAFC_R13_GA/bin/jsh
List the path name of all
the dependencies

jsh ~ -->ldd /glosoft/TAFC_R13_GA/bin/jsh

libTAFCfrmwrk.so => /glosoft/TAFC_R13_GA/lib/libTAFCfrmwrk.so
libTAFCjbase.so => /glosoft/TAFC_R13_GA/lib/libTAFCjbase.so
libTAFCutil.so => /glosoft/TAFC_R13_GA/lib/libTAFCutil.so
libTAFCjee.so => /glosoft/TAFC_R13_GA/lib/libTAFCjee.so
libpthread.so.1 => /lib/64/libpthread.so.1
libm.so.2 => /lib/64/libm.so.2
libgen.so.1 => /lib/64/libgen.so.1
libcurses.so.1 => /lib/64/libcurses.so.1
libdl.so.1 => /lib/64/libdl.so.1

Core Infra Temenos PACS 43

Troubleshooting - T24Updater tool (V3.0)

libnsl.so.1 => /lib/64/libnsl.so.1

librt.so.1 => /lib/64/librt.so.1
libsocket.so.1 => /lib/64/libsocket.so.1
libTAFCtj.so => /glosoft/TAFC_R13_GA/lib/libTAFCtj.so
libstlport.so.1 => /opt/solarisstudio12.3/lib/stlport4/v9/libstlport.so.1
libCrun.so.1 => /usr/lib/64/libCrun.so.1
libthread.so.1 => /lib/64/libthread.so.1
libc.so.1 => /lib/64/libc.so.1
libicuuc.so.40 => /glosoft/TAFC_R13_GA/lib/libicuuc.so.40
libicui18n.so.40 => /glosoft/TAFC_R13_GA/lib/libicui18n.so.40
libTAFCjql.so => /glosoft/TAFC_R13_GA/lib/libTAFCjql.so
libTAFCcommon.so => /glosoft/TAFC_R13_GA/lib/libTAFCcommon.so
libTAFClogger.so => /glosoft/TAFC_R13_GA/lib/libTAFClogger.so
libACE.so.5 => /glosoft/TAFC_R13_GA/lib/libACE.so.5
libACE_SSL.so.5 => /glosoft/TAFC_R13_GA/lib/libACE_SSL.so.5
libTAFCjcf.so => /glosoft/TAFC_R13_GA/lib/libTAFCjcf.so
libmp.so.2 => /lib/64/libmp.so.2
libmd.so.1 => /lib/64/libmd.so.1
libscf.so.1 => /lib/64/libscf.so.1
libaio.so.1 => /lib/64/libaio.so.1
libicudata.so.40 => /glosoft/TAFC_R13_GA/lib/libicudata.so.40
libdoor.so.1 => /lib/64/libdoor.so.1
libuutil.so.1 => /lib/64/libuutil.so.1
/lib/sparcv9/../libm/sparcv9/libm_hwcap1.so.2
/platform/sun4v/lib/sparcv9/libc_psr.so.1
/platform/sun4v/lib/sparcv9/libmd_psr.so.1

Figure 80 – List of dependencies

From the above given output, we could see that the problematic lib libstlport.so.1 denotes the OS lib
path. Since, this path is not included in the environment variables, the system throws an error message
“T24Version: fatal: libstlport.so.1: open failed: No such file or directory”

Solution:

export
LD_LIBRARY_PATH=$TAFC_HOME/lib:$JBCDEV_LIB:$JRELIB:/opt/solarisstudio12.3:
/opt/solarisstudio12.3/lib/stlport4/v9:${LD_LIBRARY_PATH:-/usr/lib}

Core Infra Temenos PACS 44

Troubleshooting - T24Updater tool (V3.0)

export
LIBPATH=$TAFC_HOME/lib:$JRELIB:$JBCDEV_LIB:$JAVA_HOME/jre/bin:$JAVA_HOME/j
re/bin/classic:/opt/solarisstudio12.3/lib/stlport4/v9:${LIBPATH:-/usr/lib}

export
SHLIB_PATH=$TAFC_HOME/lib:$JBCDEV_LIB:$JRELIB:/opt/solarisstudio12.3/lib/s
tlport4/v9:${SHLIB_PATH:-/usr/lib}

5. Xml is invalid Content is not allowed in trailing section.

installing class fr.jayasoft.ivy.url.IvyAuthenticator

Oct 31, 2013 12:03:33 PM com.temenos.versionutil.SystemDescription validateXML
SEVERE: Xml is invalid Content is not allowed in trailing section.
Warning: [[T24_HOME]/t24bin/eb_updatesrun/T24Version] is not a valid xml
description of a system null

Figure 81 – Error Message

Solution:

Please follow the below steps in order to solve the problem.

Compile the below given program PRODUCE.T24Version

PROGRAM PRODUCE.T24Version
$INCLUDE T24.BP I_COMMON

$INCLUDE T24.BP I_EQUATE

EXECUTE "T24Version" CAPTURING OUTPUT

DIR.NAME = 'updater/config'

FILE.NM = 'T24Version.xml'

FV.FILE = ''
NEW.LINE = CHARX(010) ;*new line char

TAB = CHARX(009) ;* Tab char

OPEN DIR.NAME TO FV.FILE.PTR ELSE CRT "UNABLE TO OPEN ":DIR.NAME

CONVERT FM TO '' IN OUTPUT
CONVERT " " TO '' IN OUTPUT

CHANGE '><' TO '>':NEW.LINE:'<' IN OUTPUT ;*allign the response

CHANGE '<dependency' TO TAB:'<dependency' IN OUTPUT ;*allign the response

WRITE OUTPUT TO FV.FILE.PTR,FILE.NM SETTING ERROR.MSG

IF NOT(ERROR.MSG) THEN

CRT "T24Version.xml is successfully produced"

END
ELSE

CRT "CANNOT WRITE TO T24Version.xml"

Core Infra Temenos PACS 45

Troubleshooting - T24Updater tool (V3.0)

END
RETURN
END

Figure 82 – PRODUCE.T24Version

Modify updater.xml file as shown below:

<service name="T24" pathType="FILE" updateType="AUTO">

<path>[T24_HOME]/updater/config/T24Version.xml</path>
<installpath>[T24_HOME]</installpath>
<installprogram>[T24_HOME]/t24bin/eb_updatesrun/T24.UPDATE.INSTALLER</installpro
gram>
</service>

Figure 83 – updater.xml

Modify updater.bat / updater present inside $HOME/updater/bin as shown below:

"%HOME%/bin/PRODUCE.T24Version"

set CP="%T24_HOME%\updater\lib\updater.jar"

"%JAVA_HOME%\bin\java" -Xmx1024M -XX:MaxPermSize=256M -cp %CP%

com.temenos.upgrader.Upgrader %*

Figure 84 – updater.bat/updater

Full path or relative path of the program as shown in the below jshow output

jsh R10 ~ -->jshow -c PRODUCE.T24Version

Executable: d:\LocalHost\R10.000\Temenos\R10\bnk\bnk.run\bin\PRODUCE.T24Version.dll
jBC main() version 10.0 Tue Sep 13 12:39:40 2011
jBC main() source file ANALYSIS.BP
Executable(DUP!!):d:\LocalHost\R10.000\Temenos\R10\bnk\bnk.run\bin\PRODUCE.T24Version.exe
jBC main() version 10.0 Tue Sep 13 12:39:40 2011
jBC main() source file ANALYSIS.BP

Figure 85 – jshow

Core Infra Temenos PACS 46

Troubleshooting - T24Updater tool (V3.0)

In Unix environment, modify as "$HOME%/bin/PRODUCE.T24Version"

NOTE: If problem persists, kindly use the below code of PRODUCE.T24Version

PROGRAM PRODUCE.T24Version
$INCLUDE I_COMMON
$INCLUDE I_EQUATE

EXECUTE "T24Version" CAPTURING OUTPUT

DIR.NAME = './updater/config'
FILE.NM = 'T24Version.xml'
FV.FILE = ''
OPEN DIR.NAME TO FV.FILE.PTR ELSE CRT "UNABLE TO OPEN ":DIR.NAME
WRITE OUTPUT TO FV.FILE.PTR,FILE.NM SETTING ERROR.MSG
IF NOT(ERROR.MSG) THEN
CRT "T24Version.xml is successfully produced"
END
ELSE
CRT "CANNOT WRITE TO T24Version.xml"
END
RETURN
END

Figure 86 – PRODUCE.T24Version

6. Update failed: java: not found

R10_EB_Upgrade_7, Successfully copied the libraries and binaries.

Update successful for R10_ENT_Enquiries_4_AIX_5.tar : Message: Update
R10_ENT_Enquiries_4, Successfully copied the libraries and binaries.
Update failed: java: not found

Output Summary:
28 files processed.
Updates not successful.
Exiting Updater...

Figure 87 – Error Message

Solution:

Need to append $JAVA_HOME/bin to PATH variable of .profile as shown in the below example and re-
run updater tool in a restored environment.

Core Infra Temenos PACS 47

Troubleshooting - T24Updater tool (V3.0)

Example:

export
PATH=/DEV2_02/r10test/bnk.run/updater/bin:/usr/vac/bin:$JBCRELEASEDIR/bin:
$JAVA_HOME/bin:$JBCRELEASEDIR/config:$PATH:.:/usr/local/bin:$HOME/globuspa
tchbin:$HOME/bin:$HOME/t24bin:/usr/ccs/bin:/usr/ucb:/usr/aix/bin:$HOME/t24
/eb_interface:/usr/bin/gtar

7. Content is not allowed in prolog.

i. If the problem occurs for a particular update

Error Message:

Sep 7, 2011 2:28:19 PM com.temenos.upgrader.jaxb.JaxbUtil load

SEVERE: Caught UnmarshalExceptionnull

Error in: /globus/desupg07/bnk/bnk.run/updater/updates/tmp/R11_ACM_AccountOpening_5_SUN.tar. XML being written to log

file.

javax.xml.bind.UnmarshalException

- with linked exception:

[org.xml.sax.SAXParseException: Content is not allowed in prolog.]

at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:315)

at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:476)

at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:198)

at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:167)

at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)

Figure 88 – Error Message

Reason & Solution to the problem:

Figure 89 – Solution

Core Infra Temenos PACS 48

Troubleshooting - T24Updater tool (V3.0)

There could be a special character (non UTF8 character) present inside update.xml file of the
corresponding tar file. In this case, we need to re-cut R11_ACM_AccountOpening_5_SUN.tar.

ii. If the problem occurs for T24Version

Error Screenshot

Figure 90 – Error Message

Reason & Solution to the problem

The compatible java version to the T24Updater tool is java version 1.6 (and above) hence we request
you to contact your System administrator to upgrade the jdk1.6.0_18 or above.

After upgrading, kindly modify the PATH variable in .profile as shown below:

export JAVA_HOME=<<JAVA_HOME path>>

Figure 91 – JAVA_HOME

Example export JAVA_HOME=/opt/Java/jdk1.6.0_18

export PATH=$JAVA_HOME/bin:$PATH

Figure 92 – PATH

Core Infra Temenos PACS 49

Troubleshooting - T24Updater tool (V3.0)

8. Cannot run program - CreateProcess error=2

Error Screenshot

jsh EDGECONNECT ~ -->updater.bat

T24 Updater V2.4

Input Summary:
T24Updates-2014-1-31-536.zip
R09_AA_Account_42_WIN64.tar
R09_AA_Accounting_9_WIN64.tar
.
.
R09_TT_ModelBank_4_WIN64.tar
R09_TT_Passbook_5_WIN64.tar
installing class fr.jayasoft.ivy.url.IvyAuthenticator
Feb 3, 2014 4:28:49 PM
com.temenos.versionutil.ExecSystemDescription getXml
WARNING: Error executing command to retrieve system descrption
java.io.IOException: Cannot run program
"T:\Accounts\EDGECONNECT\bnk.run/t24bin/eb_updatesrun/T24Version":
CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)

Figure 93 – Error Message

Solution for this problem:

The reported problem occurs since the Updater tool V2.4 is not compatible in R09 release. The
compatible version of updater tool for R09 release is V1.6. However, in order to overcome this error,
kindly modify the updater.xml as shown below.

<service name="T24" pathType="EXEC" updateType="AUTO">

<path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>

<installpath>[T24_HOME]</installpath>

<installprogram>

[T24_HOME]/t24bin/eb_updatesrun/T24.UPDATE.INSTALLER</installprogram>

</service>

Figure 94 – updater.xml before

In the above, the tag <path> and <installprogram> should be modified as shown below:

Core Infra Temenos PACS 50

Troubleshooting - T24Updater tool (V3.0)

<service name="T24" pathType="EXEC" updateType="AUTO">

<path>[T24_HOME]/t24bin/eb_updates/T24Version</path>

<installpath>[T24_HOME]</installpath>

<installprogram>

[T24_HOME]/t24bin/eb_updates/T24.UPDATE.INSTALLER</installprogram>

</service>

Figure 95 – updater.xml after

9. Update failed: Can't load log handler "java.util.logging.FileHandler"

Error Message:

Can't load log handler "java.util.logging.FileHandler"

java.io.IOException: Couldn't get lock for %h/ParentInstaller%u.log
java.io.IOException: Couldn't get lock for %h/ParentInstaller%u.log
at java.util.logging.FileHandler.openFiles(FileHandler.java:389)
at java.util.logging.FileHandler.<init>(FileHandler.java:225)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:379)
at java.util.logging.LogManager$4.run(LogManager.java:809)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.loadLoggerHandlers(LogManager.java:802)
at java.util.logging.LogManager.initializeGlobalHandlers(LogManager.java:1406)
at java.util.logging.LogManager.access$1500(LogManager.java:148)
at java.util.logging.LogManager$RootLogger.accessCheckedHandlers(LogManager.java:1493)
at java.util.logging.Logger.getHandlers(Logger.java:1350)
at java.util.logging.Logger.log(Logger.java:612)
at java.util.logging.Logger.doLog(Logger.java:641)
at java.util.logging.Logger.log(Logger.java:664)
at java.util.logging.Logger.fine(Logger.java:1214)

at com.temenos.upgrader.Upgrader.doIt(Upgrader.java:296)
at com.temenos.upgrader.Upgrader.main(Upgrader.java:173)
R15_EB_Foundation_3_WIN64_VC100.zip
R15_EB_Foundation_3_WIN64_VC100.tar

Core Infra Temenos PACS 51

Troubleshooting - T24Updater tool (V3.0)

installing class fr.jayasoft.ivy.url.IvyAuthenticator

Update failed for R15_EB_Foundation_3_WIN64_VC100.tar : Message: Update
R15_EB_Foundation_3, Updates failed for R15_EB_Foundation_3_WIN64_VC

Figure 96 – Error Message

Reason & Solution to the problem

The T24Updater tool is internally executed as shown below:

"%JAVA_HOME%\bin\java" -Xmx1024M -XX:MaxPermSize=256M -

Djava.util.logging.config.file=%T24_HOME%\updater\config\logging.propertie
s -cp %T24_HOME%\updater\lib\updater.jar com.temenos.upgrader.Upgrader %*
Figure 97 – Updater tool

Here, the option “-D” creates ParentInstallerX.log.X (where X is the sequence number) inside C:\
directory.

The reported error will occur if the corresponding user who executes updater.bat file does not have
sufficient access rights to write C:\ directory.

Hence to suppress this error, please follow the below procedure:

1) Navigate to c:\Windows\System32\ and right click on cmd.exe and choose "Run as administrator"
option.

2) In the cmd opened as administrator, "cd" to bnk.run directory and execute remote.cmd and then
execute updater.bat

10. <<T24_HOME>>/updater/bin/updater[21]:<<JAVA_HOME>>/bin/java: not

found

Error Message

jsh t24adm ~ -->updater

/appl/t24/t24env/bnk.run/updater/bin/updater[21]:
/usr/java71_64/bin/java: not found

Figure 98 – Error Message

Reason
This error would occur when "java" executable is not found inside $JAVA_HOME/bin directory
(JAVA_HOME variable which is set in .profile).

Core Infra Temenos PACS 52

Troubleshooting - T24Updater tool (V3.0)

Solution
Ensure that Java JDK installed in the environment and set JAVA_HOME variable in .profile
accordingly. It must be noted that JAVA_HOME should point to the Java JDK version instead of JRE.

Troubleshooting BNK/T24.UPDATES service

1. Failed Updates list

Error Message

_T24.UPDATES_T24.UPGRADE_2_30 OCT 2012_07:44:14_Failed Updates list

R12_AC_HighVolume_4-R12_CO_Contract_2-R12_FT_Clearing_1-R12_FX_Contract_3-
R12_IC_Config_3-R12_LC_Fees_5-R12_LD_Commitment_1-R12_LD_Schedules_2-
R12_LI_ModelBank_3-R12_MM_Contract_5-R12_MM_Fiduciary_1-
R12_PD_AccountLimit_2-R12_PD_Foundation_1-R12_PD_ModelBank_1-
R12_STM_AccountStatement_4

Figure 99 – Error Message

To Resolve this

1. Set the variable JEDIENABLEQ2Q in remote.cmd (for Windows environment) / .profile (for
Unix environment)

set JEDIENABLEQ2Q=1

Figure 100.1 – JEDIENABLEQ2Q

2. Set the VOC of SYSTEM as shown below:

jsh->CT VOC SYSTEM

001 Q
002 SYSTEM

Figure 100.2 – CT VOC SYSTEM

Core Infra Temenos PACS 53

Troubleshooting - T24Updater tool (V3.0)

3. Check whether the VOC entry of %F.SL as below.

jsh -->CT VOC %F.SL

001 Q

002 TEMP.RELEASE

003 &SAVEDLISTS&

Figure 100.3 – CT VOC %F.SL

4. Set the TEMP.RELEASE path as shown below:

jsh->CT SYSTEM TEMP.RELEASE

001 D
002 D:\localhost\R12\bnk\bnk.run

Figure 100.4 – CT SYSTEM TEMP.RELEASE

5. The second line of TEMP.RELESASE should be same as the pwd.

jsh->pwd

D:\localhost\R12\bnk\bnk.run

Figure 100.5 – PWD

Core Infra Temenos PACS 54

Troubleshooting - T24Updater tool (V3.0)

2. WRONG ALPHANUMERIC CHAR and TOO MANY CHARACTERS error

message

The BNK/T24.UPDATES service hangs because of the error messages “WRONG APLAHNUMERIC
CHAR” and “TOO MANY CHARACTERS”

Error Message

_BNK/T24.UPDATES_T24.UPGRADE_2_07 NOV 2012_13:28:45_Releasing data items

R10_SCO_SecurityPositionUpdate_15

T24 SOFTWARE UPGRADE 13:28:45 07 NOV 2012

*********************************************

Building release lists ............

**...Program complete...** 13:28:45 07 NOV 2012

.[23;9H0R10_SCO_SecurityPositionUpdate_15 TOO MANY

CHARACTERS0.[10;1HRELEASE NUMBER IS R10_SCO_SecurityPositionUpdate_15
.[23;9H0 INVALID
CHARACTER0.[12;1HSELECT LIST NAME IS .
.[23;9H0 WRONG ALPHANUMERIC
CHAR.0.[23;9H.0.[23;9H0

Figure 101 – Error Message

To Resolve this

The reported error message will occur if the ID of the updates is more than 30 characters. In order to
get resolved with the error messages “WRONG ALPHANUMERIC CHAR” and “INVALID
CHARACTER”, install the latest version of the updates EB_Upgrades

To get resolved with the error “TOO MANY CHARACTERS”, install the latest version of the updates
EB_SystemTables.

Core Infra Temenos PACS 55

Troubleshooting - T24Updater tool (V3.0)

3. Unable to open file TEMP.RELEASE/&SAVEDLISTS&

The BNK/T24.UPDATES service hangs because of the error message “Error During Data Release
:EB.RTN.UNABLE.OPEN.FILE.2 TEMP.RELEASE/&SAVEDLISTS&”.

Error Message

Figure 102 – Error Message

To Resolve this
Below setup should be done in the system.

1) SYSTEM > TEMP.RELEASE does not point to bnk.run directory. Sample setup is provided below:

jsh R16TAFC ˜ -->pwd

D:\Temenos\ModelBank-R16-TAFC\bnk\bnk.run

jsh R16TAFC ˜ -->CT SYSTEM TEMP.RELEASE

TEMP.RELEASE
001 D
002 D:\Temenos\ModelBank-R16-TAFC\bnk\bnk.run

Figure 103.1 – TEMP.RELEASE

Here, both pwd output and 2nd line of TEMP.RELEASE is the same (pointing to bnk.run directory)

2) VOC entry of SYSTEM should be as below:

jsh R16TAFC ˜ -->CT VOC SYSTEM

SYSTEM
001 Q
002 SYSTEM

Figure 103.2 – CT VOC SYSTEM

Core Infra Temenos PACS 56

Troubleshooting - T24Updater tool (V3.0)

3) SYSTEM should present inside bnk.run as UD directory as mentioned in JEDIFILENAME_SYSTEM

variable:

jsh t24dev2e ˜ -->echo $JEDIFILENAME_SYSTEM

/opt/temenos/T24DEV2E/bnk/bnk.run/SYSTEM

Figure 103.3 – JEDIFILENAME_SYSTEM

4) JEDIENABLEQ2Q should be set to 1 in .profile / remote.cmd

export JEDIENABLEQ2Q=1

Figure 103.4 – JEDIENABLEQ2Q

Core Infra Temenos PACS 57

Troubleshooting - T24Updater tool (V3.0)

Conclusion:

The procedures suggested in the document will ensure that the errors mentioned will be resolved.

After installation of updates, all the INAU files, which are released in updates installation should be
authorised. If CONVERSION.DETAILS records are released, it should be authorised and verified, so
that the corresponding data conversion is done.

Core Infra Temenos PACS 58